The 4.5.5 OTA should effectively yield the 'factory reset' you were seeking. Note there is always a small risk with OTAs even those performed on unaltered devices. Amazon offers a one time non-hassle exchange should something happen (assuming it is still under warranty).
I found this video and a recovery is included in the description, would it work? https://www.youtube.com/watch?v=HYwn9xWpDNw
Sorry for your situation. I am not screwing with you. If there was a 'straight up', 100% guaranteed, absolutely foolproof way to accomplish what you are seeking I would have offered it in the first response. Kindles are finicky devices. While the steps I have suggested should be safe there are no assurances.I'm still really confused, if you could answer these questions to clear things up that would be awesome.
I previously had a problem with the hdx 7 a couple years back and went through three broken refurbished ones until they gave me a full refund. I then got the one I have now, and the warranty has run out, so any brick will basically screw me. This was a gift and i really don't want to screw it up, that's why I'm asking so many questions
1. Is it possible to have a straight up answer, is it possible to revert this back to how it would be if it was brand new?
2. Is it possible to look at the download of the gapps, and remove everything that's there from the kindle, revert it to 3.2.8 or some other version, and then ota it to 4.5.5 and it would be good as new?
I think I'll do the OTA update, it's just that the thing holding me back is that the first thing stated in this post is to disable OTA immediately or else it will brick the device: http://forum.xda-developers.com/kin...lback-13-3-2-8-rollback-ota-captured-t3046204
That post (with accurate guidance) pertains to a 3.2.8 rollback. You are working through minor upgrade. See here (step #1) for name of OTA file.I want to thank you first of all for staying with me this whole time
I really want to do it though. Do you know what the normal name of the ota file is? I renamed it so it wouldn't do an update but I don't remember the original one.
Yep-if executing a standard apk was all that was done and no system files were modified (often times not but maybe in this case).
I'll take a break, forget about it, and tomorrow hopefully my mind will be cleared like you said, and all will be good! Thanks for all of the help Davey, I really do appreciate it!
Assuming your device is in flight/airplane mode with wifi disabled. Also assuming you did not disable OTA via HDX toolkit. You can check the 4.5.2 bin file integrity by installing ES File Explorer via adb and verifying md5 (update-kindle-13.4.5.2_user_452004220.bin -> 5fdc986f362796a6c5a817b0e22e4bcd). Verify name and location ("internal storage"; root of sdcard) of 4.5.2 bin file then reboot device. Wait 10-15 min and check for update. Hopefully will find it. If not download the 4.5.2 file again and repeat previous steps. If still unrecognized try enabling WiFi radio while keeping airplane mode engaged. Important: do NOT allow your kindle to establish a wireless connection; an OTA from Amazon will irreversibly brick your device. Wait a few minutes to see if it recognizes the update file. If none of the above works you can attempt a factory reset from the Kindle recovery menu (accessed via power + vol-up from a cold start). Note this is a dangerous 'last resort' action as it has the potential to trigger startup problems, some which can be difficult/impossible to resolve. At minimum you should root 3.2.8 (via HDX Toolkit) and enable USB debug before attempting a factory reset.
No. Responses will help shape response:
The images in this thread can not be flashed (they also contain stock components you don't want - bootloader, recovery, etc). Use the ones from this thread. However, you will likely loose root and have to take additional steps to regain it:
Reloading FireOS is not the answer.i have nexus v4 now, and unlocked bootloader, but apps crash continuosly, Skype, firefox....
thank you so much, now work fine; i think it was old bootloader.
thank you so much, now work fine; i think it was old bootloader.
Nope - use these (understand consequences):
