[HOWTO] install eOS GSI on a Treble device - new GSI added June 14th was the first source that I tried for the GSI process. I have followed the guide step by step and have already flashed vbmeta to the vbmeta partition. I probably should have mentioned that this was the original source material that I used. I initially didn’t mention it because it’s the boilerplate method of flashing roms.
(flashing vbmeta disables verify boot. it’s already disabled in all my cases but I flash it again for good measure)
This won’t work.
Why would replicating the process that you did not work?
So just to be clear: I am not inexperienced at flashing roms with android. Due to none of the GSIs/official ROMs from e.foundation working, I have resorted to a multitude of different experimentations. I have put more than 8 hours into trying to get this ROM installed. Here are some of the things I have tried:
- I started every flash on a clean advanced wipe.
- I always flash the official OEM android version (8,9 or 10 depending on the matched rom version) (after running out of options, I have also tried NOT flashing the stock android. but I dont see how that would be any different. but I have)
- I always format the data before the next step
- flashed every ROM (non-gsi) I could find on this site for pixel2/Taimen.
- flashed every GSI I could find on this site.
- after every failed attempt, I flashed my vbmeta (which is a blank file btw).
- after every failed attempt of the previous, I formatted my data and cleared cache/dalvik
During moments when I run out of options, I try crazy solutions like throwing in more formats, I reflash the roms again and try other rom sources to verify my technique.
Almost every single rom on xda-forums is flashable using my technique. My technique is the recommended technique for clean-installing roms. vbmeta is mentioned in almost every post for the taimen device, Im no stranger to vbmeta. It’s not the issue.
PS: e-pie-20190827-UNOFFICIAL-treble_arm64_beN.img did once work for me. I even backed up this file because it worked for me back in 2019. Some variable has changed causing it to no longer work on my phone. Does Android 10 mess with the boot loader? Does it restructure something?