Originally Posted by stunts513
That probably won't fix it, I asked around and twrp basically checks the cache for a zip and a open recovery script, when you factory reset it it should have wiped the cache, you can still do that from advanced while if you want but I believe the culprit is your bootmode defaulting to the wrong value. I can't verify this without you wiping internal storage and flashing a amazon os zip from the dev section though.
If you flash back to amazon os I highly recommend not connecting to WiFi, an ota would be very bad if it got rid of second bootloader because Idk if you could force /system to boot. And that flashable zip I'm thinking of might be a kfhd7 zip which would be bad... Not sure if there is one for kf2.
Sent from my Amazon Tate using Tapatalk
Judging from the first part of your message, flashing a zip file to update through TWRP won't fix the bootmode value. But overall, this is still a theory unless I flash an amazon os?
About the second half of your post, I kinda get the ota through WiFi will most likely mess things up and how it might erase the second bootloader. But I have no idea which flashable zip you are talking about.
In conclusion, a possible solution to the bootmode issue is to update through the device itself and not flashing a zip of it? And if the device messes up again with booting into TWRP recovery only, I can try to fix it with wiping internal storage and flashing the rom and gapp again like before? Also, if I am brave enough and got nothing to do, another possible way to solve my problem is flashing back to amazon os?
Other than that, the safest option is to do nothing, leave it alone as it is, and enjoy having android on a kindle fire?