Bonjour,
Je viens d’avoir deux modèles décrits dans le titre. Je viens d’y installer twrp avec difficulté, j’ai du supprimer le mode no-reboot. et directement faire la combinaison de touche. Puis-je installer eOS? La version 2.3 est-elle fonctionnelle?
Regain your privacy! Adopt /e/OS the deGoogled mobile OS and online services
Hello @CyrMatt
je ne trouve pas la réponse sur le forum, pourquoi ne pas essayer ?
et rendre compte..
Merci Piero, jai commencé par la 1. tout fonctionne sauf la sim… Elle est reconnu mais on ne s’entend pas entre contact. Je teste la 2.3.
Très grosse déception! Tout s’installe très bien, mais la sim n’est pas détectée dans aucune des entrées (double sim) c’est donc pire qu’avec la 1 qui détecte au moins la sim. Y aurait-il un solution? LOS fonctionne-t-il avec?
e-0.17-q-20210606-UNOFFICIAL-j5xnlte
Download link:
.
here
https://xdaforums.com/t/roms-list-of-unofficial-e-os-builds-by-me.4651630/post-90382132
we can read
e-2.3-r-20240906-UNOFFICIAL-j5xnlte.zipworks fine.
OK j’essaye. C’est quoi le kernel source?
en français : les sources du noyau
.
.
.
Where case of call sound issues, one can try using “Simple Dialer”
.
.
Set up Linux environment
curl https://raw.githubusercontent.com/Galaxy-J5-Unofficial-LineageOS-Sources/Manifest/lineage-20.0-enforcing-Vanilla/Scripts/environment.sh > environment.sh
sh environment.sh
Initialize repo:
mkdir -p ~/android/lineage
cd ~/android/lineage
repo init -u https://github.com/Galaxy-J5-Unofficial-LineageOS-Sources/Manifest.git -b lineage-20.0-enforcing-Vanilla
Download latest manifest:
mkdir -p .repo/local_manifests
curl https://raw.githubusercontent.com/Galaxy-J5-Unofficial-LineageOS/Manifest/lineage-20.0-enforcing-Vanilla/Manifests/manifest.xml > .repo/local_manifests/manifest.xml
curl https://raw.githubusercontent.com/Galaxy-J5-Unofficial-LineageOS/Manifest/lineage-20.0-enforcing-Vanilla/Manifests/gapps.xml > .repo/local_manifests/gapps.xml
how to build /e/ and not Lineage, using that customisations ?
.
my test build is designed to run from the External SDcard so it keep AndroidOS untouched in the Internal Memory, only a boot.img have to be flashed to switch between both OSes as a Dual-Boot.
.
sources and troubleshotings :
Samsung Galaxy J5 2016 (samsung-j5x) - postmarketOS Wiki
Qualcomm Snapdragon 410/412 (MSM8916) - postmarketOS Wiki
downloads :
custom android builds - Browse /PostmarketOS/j5xnlte at SourceForge.net
Default username: user, Default password: 147147
.
it allow running PostmarketOS from an External SD card and let AndroidOS running from the Phone Internal Memory as usual.
We will inserate a piece of software between the Stock Bootloader (Odin mode / Download mode) and the usual Android-BOOT partition,
in fact, a second Bootloader called Lk2nd that act as a Fastboot mode unlike on other Samsung devices.
On devices with lk2nd the boot image is loaded from an ext2 boot partition either on EMMC or SD card. Since lk2nd keeps backwards compatibility with android boot images, you can flash your android boot.img via lk2nd and it will boot that image unless an SD card with postmarketOS is inserted.
lk2nd “secondary” bootloader intended for devices where existing firmware cannot be replaced easily (most smartphones and tablets). In this configuration, lk2nd does not replace the stock bootloader. Instead, it is packed into an Android boot image, which is then loaded by the stock bootloader just like the original Android image. The real operating system can be placed in the boot partition with 512 KiB offset or stored in a ext2 file system. It does not have to be Android or even Linux, any kind of kernel can be packed into an Android boot image.
.
.
lsblk
make sure it is the right one as you will overwrite everything on it. Use a path without partition number at the end, such as /dev/mmcblk0, or /dev/sdd
xz --decompress --stdout path-to-pmos-samsung-espresso7.img.xz | sudo dd of=/dev/name-of-your-SDcard bs=4M status=progress
Wait until the command completes and eject the SD card. (you can now manage partitions size using tool like gparted)
.
lk2nd-21.0-msm8916.img (available from the releases page on Github)and flash it using the stock flashing interface :
Boot your phone to bootloader (Odin/Download) mode
by holding Volume Down and Home while powering up.
heimdall flash --BOOT lk2nd.img
.
lk2nd provides the standard Android fastboot protocol for flashing/booting Android boot images.
Press Volume Down while booting to enter Fastboot mode. Press Volume Up while booting to boot into Recovery mode.
If your stock bootloader uses the same key combinations, you need to wait a bit before pressing the volume keys. Usually, waiting until the screen turns on and/or the device vibrates should be enough to make the stock bootloader ignore the keys.
fastboot flash lk2nd lk2nd.img
can be used to update lk2nd directly from its fastboot interface.
.
fastboot flash boot boot.img
will flash the actual boot image with 512 KiB offset into the boot partition. This is done to avoid replacing lk2nd (since it is also booted from the boot partition).
Other fastboot commands work normally.
.
.
Enfin une bonne nouvelle, avec la version 0.17 la sim fonctionne il faut que je teste le reste.
Je vais donc me contenter de 0.17 ce qui me semble déjà très bien.
Merci Piero, mais je ne sais pas ce que c’est un dirty flash, pouvez-vous m’en dire d’avantage je suis prêt a essayer. Maintenant c’est déjà génial de passer à android 10.
en français : flasher grossièrement (sans rien effacer)
Ok donc je reinstalle la nouvelle version 2.3 par exemple sans wiper avant c’est bien ça? Toujours en passant par le recovery?
please use a translator when needed as example DeepL traducteur
D’accord, donc, pour ne pas faire de bêtise je récapitule. Je dois installer lineage os 19 ou 20 (j’imagine là en faisant le wipe) puis je réinstalle eos sans faire le wipe. C’est bien ça?
je pense que LineageOS 19 ou 20 basées respectivement sur android 12 et 13 devraient poser problème pour installer /e/OS basée sur android 11
pour vérifier le commentaire de @sethdot, la plus “propre” des procedures serait :
mais
devrait suffire
La version 18 de lineage os ne propose que nlte et non xnlte. Est-ce tout de même compatible?
en suivant les liens fournis par Ronnz98, on trouve
.
pour e-1.17-q :
.
https://xdaforums.com/t/rom-10-0-j5-2016-lineageos-17-1-for-galaxy-j5-2016-unofficial.4120243/
.
.
.
pour e-2.3-r :
.
Galaxy J5 | LineageOS · GitHub
.
Release Lineage-18.1-August-UNOFFICIAL · Galaxy-J5-Unofficial-LineageOS-Sources/Releases · GitHub
here
https://xdaforums.com/t/roms-list-of-unofficial-e-os-builds-by-me.4651630/post-90382132
about e-2.3-r we can read
Unfortunately, the camera doesn’t work properly (either the builtin app, or Open Camera):
- Looking through the viewfinder (or barcode scanners) works fine
- Actually taking/saving a picture doesn’t work: the app screen freezes (not the whole app, though) and no picture is taken
Also, there’s no Gallery app, and even if I install one (e.g. Fossify Gallery), camera apps still display “No gallery app available” when I tap the in-app gallery button.
Could those issues be related?
