I finally got Odin to install recovery-e-1.7-s-20230111250406-dev-gta4xlwifi.img by renaming it to recovery.img and tar’ing it. Then used Odin 3.12 to install it. (Because I couldn’t get zadig/heimdall to recognize the device properly.)
So I was able to adb reboot recovery into /e recovery.
However when trying to adb sideload e-1.7-s-20230111250406-dev-gta4xlwifi (sha256 matches), at 47% progress, the install stops with “failed to verify whole-file signature”.
Any ideas on how I can get past this verification error?
Happens even if I try with microglineage’s recovery and lineage-19.1-20221218-microG-gta4xlwifi. Same at 47% progress, it fails with the “failed to verify whole-file signature” error.
Reboot into TWRP (have to hold down POWER+VOL-UP+while_cable_is_connected_to_computer). Yay!
I copied e-1.7-s-20230111250406-dev-gta4xlwifi onto a SD card and used TWRP Install: reboot into recovery, format data. Install /e rom. Then reboot into TWRP recovery. Then wipe cache/dalvik.
Then reboot into system -->> bouncing e logo forever.
Is there a way to tell if TWRP flashed the /e rom properly (which in this case I don’t think so), by looking at the TWRP Advanced File Manager?
That is, is /data supposed to have the normal Android directory that we can see when we plug an Android device into a computer (Alarms, Android, DCIM, Documents, etc)?
Is it the case that you never ran the First start wizard ?
If First start wizard never happened … ensure battery is >70%, go to TWRP and Factory reset. If /e/OS failed first boot, this will provide a second opportunity.
From the first attempt and not being able to get past the bouncing /e logo, I had to reflash a stock Android 12 Samsung ROM (since Android 12 was on the tablet when I got it).
Can I reflash a stock Android 11 Samsung ROM and then try again with gta4xlwifi/e-1.7-s-20230111250406-dev-gta4xlwifi.zip?