when u installed /e/, did u wipe any of those partitions?
Marty
when u installed /e/, did u wipe any of those partitions?
Marty
Yes, I also wiped āDalvik / ART Cacheā and āSystemā
How about u, ChrisRG-same thing?
Marty
Short answer, yes. But Iām no good at short answers, sorry. Recently I have deliberately been using the eRecovery to install eOS. Why not? Itās simpler. Less options. Iām not saying donāt use twrp. This is just a pointer to an easy install of eOS
Installing eOS on XA2 I would highly recommend the procedure below. Follow all the steps (unless they donāt apply; for example your bootloader is already unlocked, etc).
Eos is a fork of Lineage and so are their installation instructions (scroll down to the bottom of the page and have alook: it says so there); but why are they so different? Answer: they have not managed to get it together yet; thatās all. But it causes huge problems of confusion for newcomers. This is not to knock e in any way, it is constructive criticism which I am sure they would agree to.
Oh yes, and another thing. Ask yourself why eOS instructions point to twrp when they have their own recovery. Itās an admin thing. Paperwork.
The /e/ recovery is missing 2 things that TWRP has. The first is the ability to make a backup. The second is the ability to wipe specific partitions which seems to have gotten me in trouble so maybe thatās not a good thing to have anyway.
Marty
Cool, I think Iām going to try this tomorrow (itās getting late here in Vienna).
Would you recommend installing Android first using Emma? If so, I will install Android 9.
Also, I did not get the note on point 5 in the āTemporarily booting a custom recovery using fastbootā section on the Lineage OS install instructions.
To install on boot_a do I type fastboot flash boot_a <lineage_recovery_filename>.img
?
Yes. Thought you were going to do that anyway. Much as I dislike windows, Emma is best/easiest for me. Pick the right one: Full content erase or whatever it is
When you see < and > : they are just placeholders, or brackets, for yo to put the info of your choice into.
If you were going to install e-0.14-q-20210204100103-dev-pioneer.zip, you would type:
fastboot flash boot recovery-e-0.14-q-20210204100103-dev-pioneer.img
After that the screen stays black, in fastboot mode. Pull plug, rest, then manual reboot recovery by holding pwr/vol down (sorry for obvious repetitions). Plug back in again before sideloading OS zip.
Donāt worry if you forget to plug back in. Command will fail and remind you. Just plug back in then re-enter command.
Let us know if Emma works. Iāve never tried it because I mainly use Linux but I do have an old Win PC.
Marty
Emma is so easy, and itās Sony. Ive been on Linux last ten years, but got windows on old laptop just for Emma. Had to be above windows 7 though.
I think I have Win 10. It probably finds official stock Roms and I doubt mine was since it was mislabeled.
Marty
Emma works fine on Win 10. I found two Roms using Emma. One is Android 8 and the other Android 9. The one with the higher number is Android 10.
I think you misunderstood my question. I am confused on how to boot explicitly on slot A.
The note in the llineage install instructions:
Note: Newer fastboot releases dropped legacy A/B support, so it might attempt to flash to
boot__a
/boot__b
rather thanboot_a
/boot_b
if you try to flashboot
. In this case, you must manually specify which slot to flash to based on what slot fastboot failed to flash to. For example, if fastboot fails to flash toboot__a
, you must flash toboot_a
.
So, do I rename the recovery partition to something like recovery-e-0.14-q-20210204100103-dev-pioneer_a.img
to boot it to slot a?
I think it is not important as I will use the copy-partition script anyways but nevertheless I would like to understand how to explicitly boot an image to a specific slot.
Some useful info for you:
There is no recovery partition as such on A/B slot devices. The recovery is flashed into the boot partition temporarily.
eOS operating system zip comes with itās own recovery (e-recovery) which as the OS installs will overwrite whatever recovery.img you used for the installation process. So if you use twrp to install by the time you have finished and booted up e, twrp will have been overwritten.
To specify which slot you want to boot the recovery to you can either specify in the command like so:
fastboot flash boot_a <recovery.img>
or you can see what slot you are on in fastboot mode with fastboot command:
fastboot getvar current-slot
If you were on slot b, say,change with:
fastboot --set-active=a
When you boot a recovery on whichever slot to install a rom , the system will boot onto the other slot.
If you are going to install eOS from stock android 9 you donāt need to do any of this if you follow the steps in my post #24 further up this thread. eOS will install to slot b and when booted you will see an OTA update to download in the system updater. Install that on- device and it will go to slot a.
Hope this helps.
Great, sound is working now
@chrisrg Thank you for sharing your know-how!
What I did:
Now I have /e/ with media sound Still need to do an OTA after lunch
Successfully did the OTA update as well. Media sound is still working!
Excellent!
Nice clean install with e on both slots; good job
Interesting though that I have same e-versions on both slots having installed over android 8.
Some interesting news to report. As you know I flashed stock android 8 onto my phone followed by flashing eOS Q to test this issue. And there turned out to be no problem with sound. What I didnāt say was that I had flashed the āoldestā Q version from the downloads page.: e-0.14-q-20210204100103-dev-pioneer.zip
The benefit of flashing older version first is that one can try out OTA updates. Downloaded the update in the system updater and followed the prompts to have it install on-device in the background. Now phone has e-0.14-q-20210204100104-dev-pioneer on the other slot and guess what? Sound not working properly.Iām assuming you flashed the most recent version?
You could try flashing the older version on yours. Might be an idea to flash over your current version as it may possibly throw errors otherwise; to do with trying to install an older version than what you already have. To do this you would have to make sure you were temporary booting recovery on the opposite slot to your current slot.
Nice-that did occur to meā¦youāre right, I did install the most recent ROM. Iāll try to flash the older Q ROM over this.
Marty
I donāt like the idea of going backwards even in same Android version. Iām gonna wipe this thing and do a fresh install of e-0.14-q-20210204100103-dev-pioneer.zip and then do OTA update if the sound in media works again.
Marty
Good plan. What I was getting at by booting twrp on inactive slot (if youre using twrp that is, I was kind of assuming thatās what you wanted to do) you can wipe system from there: and it would be wiping system on the other slot. Same with e-recovery.
Itās not a big deal anyway because wiping of system happens when the installation takes place.
Data though: thatās a shared partition.