Safestrap/TWRP/Gapps - Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot

I've got my 4.5.5.1 setup rooted but I was unable to get gapps working... got everything installed but the Play Store just force closes any time I try to open it, even after rebooting. I eventually got past that to where I should sign in but it's saying there's an error contacting Google, even though the internet works fine for other apps like Facebook. Snapchat, which I installed via 1Mobile, requires GPS, and that's also not letting me sign in.
I've been getting tired of the hassle and I'm thinking of going the Safestrap/CM route to get more reliable Google Play experience. The Safestrap thread says I have to be on 4.5.2, though... is that still accurate, or can I do it with a rooted (Kingroot) 4.5.5.1? I had tried installing it on 4.5.5.1 but it didn't seem to take, nothing showed up when I rebooted, and the option to reboot from the app to recovery was still greyed out. I'm also seeing that the safestrap dev dropped support a while back, should I look at rolling back to 3.2.8 and going with TWRP instead? What's the best/most recommended method at this point?
Thanks.

You can NOT install TWRP, downgrading to 3.2.8, and then updating to 4.5.2, root, and using Safestrap v4 with either CM11 or Nexus for Safestrap v4 would be your options. CM12, CM13 and SlimLP are NOT Safestrap compatible!
You can NOT downgrade below 3.2.8 due to rollback protection by Amazon, attempt would brick the device!
Note that you must disable WLAN/keep flight mode active during the down- and update procedure! Getting updated OTA by Amazon while on the downgrade-3.2.8 will brick the device!
Also note that you should use the stock slot in Safestrap v4, ensure you understand the risks of using the stock slot before you flash anything to it! Also create a backup of the stock slot and move it to your PC before you flash anything to it.
And always remember: Never restore a backup of a secondary slot to the stock slot! Would overwrite Safestrap files and brick the device.

Related

[Q] 13.3.2.1 - Using device and securing Custom ROM possibility

Hi Guys,
i just got my HDX (7" - Thor) this week and was trying to get the Thor GAPPS ROM by Cpasjuste to work. Having found nothing specific for FireOS version 13.3.2.1 i went ahead and tried my luck with the "old" version of the ROM (thor-gapps-13.3.0.0-v2.zip).
Unfortunately i couldn't get it to work and am back to factory defaults. Which is good, since it's not a brick. So now i'm trying to play it safe and wait for the developer's magic to happen
i'm eager to play around with the device, but don't want to risk losing my chances of running a custom ROM in the future. i already own the first Kindle Fire and wouldn't want to miss the near stock Android on that.
So, finally, my question:
If i use the HDX Toolkit to root and disable OTA updates, i assume it will be safe to use the device until the bootloader gets unlocked or some other magic happens. Am i correct with this assumption?
Edit1 [2014-07-09 - 21:21]: sorry for the soonish edit, but i just prepared the device in case someone confirms, that it is more or less safe to use it with OTA disabled.
Upon disabling OTA, i get a few rows of "killed" messages in the HDX toolkit. When i first disabled OTA i saw that some services were being disabled or uninstalled. Is "killed" a confirmation that the components are already killed? i have already factory resetted, as i cannot find a way to do a full wipe. The result is the same.
Thanks in advance.
umm
kobayashimaru said:
Hi Guys,
i just got my HDX (7" - Thor) this week and was trying to get the Thor GAPPS ROM by Cpasjuste to work. Having found nothing specific for FireOS version 13.3.2.1 i went ahead and tried my luck with the "old" version of the ROM (thor-gapps-13.3.0.0-v2.zip).
Unfortunately i couldn't get it to work and am back to factory defaults. Which is good, since it's not a brick. So now i'm trying to play it safe and wait for the developer's magic to happen
i'm eager to play around with the device, but don't want to risk losing my chances of running a custom ROM in the future. i already own the first Kindle Fire and wouldn't want to miss the near stock Android on that.
So, finally, my question:
If i use the HDX Toolkit to root and disable OTA updates, i assume it will be safe to use the device until the bootloader gets unlocked or some other magic happens. Am i correct with this assumption?
Edit1 [2014-07-09 - 21:21]: sorry for the soonish edit, but i just prepared the device in case someone confirms, that it is more or less safe to use it with OTA disabled.
Upon disabling OTA, i get a few rows of "killed" messages in the HDX toolkit. When i first disabled OTA i saw that some services were being disabled or uninstalled. Is "killed" a confirmation that the components are already killed? i have already factory resetted, as i cannot find a way to do a full wipe. The result is the same.
Thanks in advance.
Click to expand...
Click to collapse
Never factory reset stock slot if you have run the OTA blocker the utility also has a eNAble option for the OTA blocker always uninstall xposed framework and modules before factory reset also .. Always returning the unit to as close to factory as you can before doing a factory reset in factory recovery. Otherwise you risk breaking your device.. If you look around you will find ways to do a manual update to a slightly newer firmware just not the newest and your ROMs will work.
jimyv said:
Never factory reset stock slot if you have run the OTA blocker the utility also has a eNAble option for the OTA blocker always uninstall xposed framework and modules before factory reset also .. Always returning the unit to as close to factory as you can before doing a factory reset in factory recovery. Otherwise you risk breaking your device.. If you look around you will find ways to do a manual update to a slightly newer firmware just not the newest and your ROMs will work.
Click to expand...
Click to collapse
Thanks. i will look for the update method you mentioned. i might have already read it on Friday, but didn't think it would apply to my version.
i have removed everything related to modding before factory resetting from the FireOS settings. At that point, there was only safestrap left, which i uninstalled.
If i decided to stay on FireOS after all, until a better method comes up, is there a way for me to check, if the OTA blocker is actually working?
lol
kobayashimaru said:
Thanks. i will look for the update method you mentioned. i might have already read it on Friday, but didn't think it would apply to my version.
i have removed everything related to modding before factory resetting from the FireOS settings. At that point, there was only safestrap left, which i uninstalled.
If i decided to stay on FireOS after all, until a better method comes up, is there a way for me to check, if the OTA blocker is actually working?
Click to expand...
Click to collapse
It works. Just open settings go device,system updates ,check for updates, should fail immediately..if it stars to dl. kill wifi
jimyv said:
It works. Just open settings go device,system updates ,check for updates, should fail immediately..if it stars to dl. kill wifi
Click to expand...
Click to collapse
Thanks, i'm always scared with such new devices.
"Update failed". Perfect.
i got the Thor GAPPS working by now, so i'll try using that for now.

[Solved] Manual install CM11 & Original Thread: How to install CM 11.1 on Fire HDX 7?

[Solved] Manual install CM11 & Original Thread: How to install CM 11.1 on Fire HDX 7?
Hello,
as I just managed to install CM 11 on my Fire HDX 7 (3rd Gen) (thanks a lot to @Cl4ncy, @Davey126 and @EncryptedCurse) I want to share the information I got during the process.
Note: This manual might be outdated if you read it. So check if there is a newer manual You could break your device if you dont do everything correctly. I am not responsible for breaking your device! If you have a question just ask! It could be that i forgot something.
When I started my Fire HDX 7" had Fire OS 4.5.5.
Note: CM 12 is not available yet for Safestrap v4. If you want CM 12 you need an unlocked bootloader. You can't do it if your version is above Fire OS 3.2.3.2. And you are not able to downgrade below 3.2.8 due to rollback protection by Amazon.
Some preperations:
- connect your Fire HDX to your PC (if your PC doesnt recognize your Fire HDX then install the USB drivers. If that doesn't work deinstall the actual Fire HDX driver and try it again.)
- copy every folder from the Fire HDX storage to your PC (backup music, ....)
- install (Holo Backup and click on every Backup Button (in my version there were 5 buttons))
- install minimal adb + fastboot
Download these files and save them on your PC:
- ES Explorer
- KingRoot
- Safestrap v4
- a Safestrap v4 compatible ROM (CM11 or Nexus v4)
- SuperSU if you want root - Download the .zip file from here: https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip //Check if there is a newer Version
- GApps if you want the Google Apps (the right things should be already selected. If not select: ARM, 4.4, nano) -> the name should be sth like: "arm 4.4 nano 30 September 2015"
Thanks to @Davey126 and @Cl4ncy:
- Turn Wifi Off and flightmode on (you might need to enable Wifi, when you root your device with KingRoot)
- rollback to FireOS 3.2.8
// you do that by copying the file into the 'Internal storage folder' of your Fire HDX (not in a subfolder, just copy it where the DCIM, Document, Download, kindle, ... folder are.). Now wait a few minutes and go to Settings -> Device -> System Updates -> Tap Update
- upgrade to FireOS 4.5.2
// do it as before
- install ES Explorer and KingRoot with minimal ADB + Fastboot
- make sure that only the Fire HDX 7" is connected
- run this Code to see the connected devices
Code:
adb devices
- install the ES Explorer and KingRoot by using minimal ADB + Fastboot
- replace "C:\users\p-4\es.apk" with your own path and do the same for KingRoot
Code:
adb install C:\users\p-4\es.apk
- root with KingRoot or another method (i didn't find another one) //if it doesn't work directly just try it again (I tried it 10 times). If it still doesn't work just try another Wlan (that nothing gets blocked) or wait a week.
- block OTA (over-the-air updates) - only step#1 //you don't have to install the GApps because you will flash them with the ROM
- install Safestrap v4
- Copy the installation files (ROM, SuperSU, Gapps) to your Fire HDX into the /sdcard folder. (There the files won't get deleted if you wipe). If there folder isn't available then create one. But normally there should be one. Make sure you have your Fire HDX rooted. Only then you can see the folder with ES Explorer. In my case the "/sdcard" folder was the normal one, where i stored my Music, Documents, ... so had didn't have to do sth.
- Reboot
- Make a backup of the 'Stock-Slot'
- Copy the backup to your PC
- flash a Safestrap v4 compatible ROM to the ROM-Slot-1 , 2, 3 or 4 (currently CM11 or Nexus v4)
Safestrap v4 Tutorials:
(https://www.youtube.com/watch?v=K6fPF5UZsWw) General Safestrap usage
(https://www.youtube.com/watch?v=xR0WXCITq2Q) Specifically how to install a custom ROM
Notes: If you use a secondary slot the biggest possible Data Size is 16GB and your battery won't last long. You have to charge the Fire HDX very often.. If you use the Stock Rom Slot you will have the whole storage of your device.
Congratulations you successfully installed CM11 if you did everything right.
But as I mentioned before the performance is not very good, because the ROM is installed on a secondary slot.
--------------------------------------------------------------------------------------------------------------------------------------
To get the best performance and a very good battery life you have to install the ROM on the 'stock-slot'.
Thanks to @Cl4ncy and @Davey126 :
For that just:
- Reboot and go to the Safestrap Menu
- check if the installation files (ROM, Gapps, SuperSU) are in the "/sdcard" folder press "..." in the installtion menu to go up the path. There should be the "/sdcard" folder.
- Delete the secondary ROM-Slots
- Go into the Wipe Menu and Swipe to perform a factory reset (only a simple one - no advanced wipe)
- Go to install and add the ROM File
- add Gapps
- add SuperSU if you want root
- perform the flash
- if it was successfull Reboot otherwise DON'T Reboot. Just wipe again and flash the files again.
Note: If something went wrong with the stock-ROM don't reboot directly. Just install a ROM on a secondary slot and reboot then.
// The Original Post:
Hello,
since it is possible to download prime videos on any android device i would like to install Cyanogenmod 12.1 on my fire hdx 7.
I found this Cm 12.1 Port.
Is there a step by step manual how to install such a rom, because i never did that before and i have heard that if you do something wrong your device is broken.
Because I neither know how to get an unlock bootloader or what a TWRP is. Furthermore i also dont know how to flash the ROM.
In some forum posts i read, that it is possible to go from Cyanogenmod back to FireOS (unbrick). For now i dont want to go back from Cyanogenmod to FireOS, but i think it would be good to have such a possibility.
Do I have to take precautions for that?
And how do I make backups?
Info:
Kindle Fire HDX 7" (3. Generation): Fire OS 4.5.5
Thanks a lot
p-4
You can NOT use CM12 - all current builds require an unlocked bootloader. You can NOT unlock the bootloader of Fire OS versions above 3.2.3.2, thus you can NOT use CM12. You can also NOT use TWRP recovery.
Reason: Rollback protection by Amazon, preventing downgrading to Fire OS versions below 3.2.8
Good you asked first.
Your options would be to downgrade to 3.2.8, then update to 4.5.2, install Safestrap v4 and use either Nexus v4 for Safestrap v4 or CM11 for Safestrap v4.
@Davey126 gave a good overview here, so read all the info and ask before you brick your HDX! If you don't follow the procedure 100% correctly, you will brick your HDX! @tropicallazerbeams also linked to YouTube videos about Safestrap usage and installation of custom ROMs. Regarding the ROMs, read the installation requirements carefully!
Thanks for this answer
Cl4ncy said:
You can NOT use CM12 - all current builds require an unlocked bootloader. You can NOT unlock the bootloader of Fire OS versions above 3.2.3.2, thus you can NOT use CM12.
Good you asked first.
Your options would be to downgrade to 3.2.8, then update to 4.5.2, install Safestrap v4 and use either Nexus v4 for Safestrap v4 or CM11 for Safestrap v4.
@Davey126 gave a good overview here, so read all the info and ask before you brick your HDX! If you don't follow the procedure 100% correctly, you will brick your HDX! @tropicallazerbeams also linked to YouTube videos about Safestrap usage and installation of custom ROMs. Regarding the ROMs, read the installation requirements carefully!
Click to expand...
Click to collapse
Thanks for this answer,
what is the difference between Nexus v4 and CM11. Which one should i install?
CM 11 for Safestrap v4? Because i want to get CM12?
Can I use TWRP with 4.5.2?
Thanks
p-4
p-4 said:
Thanks for this answer,
what is the difference between Nexus v4 and CM11. Which one should i install?
CM 11 for Safestrap v4? Because i want to get CM12?
Can I use TWRP with 4.5.2?
Thanks
p-4
Click to expand...
Click to collapse
You can NOT use TWRP (see above), TWRP is available for Fire OS below 3.2.4 only. You must use Safestrap v4 (i.e. NOT Safestrap v3.72/3.75!).
I can't give you any recommendation, but you can try Nexus and CM11 after you installed Safestrap v4. You can even (depending on the size of your sdcard/storage) set up secondary slots and use dual boot with Safestrap installed.
But you should focus on downgrading to 3.2.8, then updating to 4.5.2, rooting, disabling OTA, and installing Safestrap first - that will be difficult and risky enough for the time being.
And note that CM12 is not an option for you. This could change in the future, but I wouldn't count on it.
And one other thing:
If you've Safestrap installed, NEVER use the factory reset in Amazon's stock recovery! You will most likely brick your HDX.
p-4 said:
Thanks for this answer,
what is the difference between Nexus v4 and CM11. Which one should i install?
CM 11 for Safestrap v4? Because i want to get CM12?
Can I use TWRP with 4.5.2?
Thanks
p-4
Click to expand...
Click to collapse
Nexus is basically an AOSP-based ROM (i.e. stock, just like Google intended).
CM11 should be self-explanatory.
I was able to successfully downgrade to 13.3.2.8.
Can I now downgrade to 3.2.3.2 (from here) to be able to get an unlocked bootloader?
Because CM 12.1 would be really nice
But for CM11 I also need an unlocked bootloader, dont I? (click).
Or is it possible, after I installed CM 11, to upgrade to CM12? (Has Cyanogenmod an Over the Air update possibility?)
p-4 said:
I was able to successfully downgrade to 13.3.2.8.
Can I now downgrade to 3.2.3.2 (from here) to be able to get an unlocked bootloader?
Because CM 12.1 would be really nice
But for CM11 I also need an unlocked bootloader, dont I? (click).
Click to expand...
Click to collapse
No, you can NOT downgrade below 3.2.8 due to rollback protection by Amazon (sorry I forgot to mention the reason, added it to my first reply above). Attempting to downgrade further will brick the HDX!
You can use the CM11 you linked to with either Safestrap v4 or an unlocked bootloader. You can NOT unlock (see above), thus you have to use it with Safestrap v4.
In order to install Safestrap v4 you must update to 4.5.2. Keep WLAN off/flight mode active! Kingroot probably requires a short moment of WLAN connection, be sure to enable flight mode right away, you don't want to get updated by Amazon to 4.5.5! After rooting disable OTA, then install Safestrap and make a backup of your Fire OS before you flash any custom ROM!
Cl4ncy said:
No, you can NOT downgrade below 3.2.8 due to rollback protection by Amazon (sorry I forgot to mention the reason, added it to my first reply above). Attempting to downgrade further will brick the HDX!
You can use the CM11 you linked to with either Safestrap v4 or an unlocked bootloader. You can NOT unlock (see above), thus you have to use it with Safestrap v4.
In order to install Safestrap v4 you must update to 4.5.2. Keep WLAN off/flight mode active! Kingroot probably requires a short moment of WLAN connection, be sure to enable flight mode right away, you don't want to get updated by Amazon to 4.5.5! After rooting disable OTA, then install Safestrap and make a backup of your Fire OS before you flash any custom ROM!
Click to expand...
Click to collapse
I successfully upgraded to 4.5.2.
Can I somehow install kingroot or es explorer without WLAN?
I got the apk on the device but I cant install it without es explorer, which I would download via the amazon app store. Can i enable Wifi for that time?
p-4 said:
I successfully upgraded to 4.5.2.
Can I somehow install kingroot or es explorer without WLAN?
I got the apk on the device but I cant install it without es explorer, which I would download via the amazon app store. Can i enable Wifi for that time?
Click to expand...
Click to collapse
Enable USB debugging, install Minimal ADB and fastboot, put the kingroot.apk into the adb directory, open a DOS box, change dir (cd) to your adb directory (e.g. enter cd\adb), then enter "adb install kingroot.apk" (without the quotes). This will install Kingroot on your HDX. Then do the same with ES Explorer.
The HDX must be connected to your PC by USB of course (should be obvious).
Thanks for that tip. Now i got these apps on my Fire HDX.
But Kingroot had some problems with the internet connection and now the Update Fire OS 4.5.4 is downloaded and could be installed. (Which i wont do).
Can I go ahead (with a better internet connection) to root the Fire HDX (it is not rooted yet). Or to I have to roll back to 3.2.8 and then update to 4.5.2 again?
p-4 said:
Thanks for that tip. Now i got these apps on my Fire HDX.
But Kingroot had some problems with the internet connection and now the Update Fire OS 4.5.4 is downloaded and could be installed. (Which i wont do).
Can I go ahead (with a better internet connection) to root the Fire HDX (it is not rooted yet). Or to I have to roll back to 3.2.8 and then update to 4.5.2 again?
Click to expand...
Click to collapse
As long as you're still on 4.5.2 you can try to root, just ensure 4.5.4 won't be installed. After successful root you can disable OTA, and delete the update file. Also ensure you have the latest Kingroot version - 4.50.902 I believe.
Now I tried to root the device with kingroot and a working internet connection but it failed :/
Is there an alternative method to root a kindle fire hdx.
I just tried the app rootGenius but i didnt understand what the app wants from me (the language is chinese or japanese).
Now i tried to root the Fire HDX 7 with 2 different apps. Do I have to reset the device? Or is uninstalling enough?
p-4 said:
Now I tried to root the device with kingroot and a working internet connection but it failed :/
Is there an alternative method to root a kindle fire hdx.
I just tried the app rootGenius but i didnt understand what the app wants from me (the language is chinese or japanese).
Now i tried to root the Fire HDX 7 with 2 different apps. Do I have to reset the device? Or is uninstalling enough?
Click to expand...
Click to collapse
I'm not sure why it failed. Kingroot should work with 4.5.2 - you sure the 4.5.4 update didn't start?
Probably wasn't a good idea to try another root app. I'm afraid you can not unroot in Kingroot, because the root attempt was unsuccessful?
Don't try a factory reset by using Amazon's stock recovery yet. May be just try Kingroot again? I think there was another report where it required a second attempt.
Cl4ncy said:
I'm not sure why it failed. Kingroot should work with 4.5.2 - you sure the 4.5.4 update didn't start?
Probably wasn't a good idea to try another root app. I'm afraid you can not unroot in Kingroot, because the root attempt was unsuccessful?
Don't try a factory reset by using Amazon's stock recovery yet. May be just try Kingroot again? I think there was another report where it required a second attempt.
Click to expand...
Click to collapse
At first I tried the kingroot 3 times and it always failed. Then i tried the other method which failed at 93%. Then I tried kingroot again, and it failed.
Is there another possibility to root it?
p-4 said:
At first I tried the kingroot 3 times and it always failed. Then i tried the other method which failed at 93%. Then I tried kingroot again, and it failed.
Is there another possibility to root it?
Click to expand...
Click to collapse
I'm afraid no.
Kingroot fails always between 53% and 55%. Once I got over 60%.
Should I upgrade to 4.5.5. And downgrade to 4.5.2 again? And try the kingroot again?
Could i try this one: http://www.gizmag.com/how-to-root-kindle-fire-hdx/30513/ ?
Or will I break my device then?
p-4 said:
Should I upgrade to 4.5.5. And downgrade to 4.5.2 again? And try the kingroot again?
Could i try this one: http://www.gizmag.com/how-to-root-kindle-fire-hdx/30513/ ?
Or will I break my device then?
Click to expand...
Click to collapse
That's an old root method not available for 4.5.x!
I'm not sure whether it's ok to update after a failed root attempt - again: you don't get any option to un-root in Kingroot?
You actually don't need to update 4.5.5 though, the 4.5.4 update would be enough, because you can downgrade to 3.2.8 from 4.5.4, too.
Keep flight mode active if you try it, so you won't get updated again. And keep the connection you must have during Kingroot as short as possible, so it won't download the entire 4.5.4 update again.
Cl4ncy said:
That's an old root method not available for 4.5.x!
I'm not sure whether it's ok to update after a failed root attempt - again: you don't get any option to un-root in Kingroot?
You actually don't need to update 4.5.5 though, the 4.5.4 update would be enough, because you can downgrade to 3.2.8 from 4.5.4, too.
Keep flight mode active if you try it, so you won't get updated again. And keep the connection you must have during Kingroot as short as possible, so it won't download the entire 4.5.4 update again.
Click to expand...
Click to collapse
Once I got the option to unroot but there i pressed FIX. At the moment I have WLAN the whole time active. 4.5.4 is already downloaded but not installed yet. I think i will upgrade to 4.5.4 now to downgrade and then do the whole stuff again.
p-4 said:
Once I got the option to unroot but there i pressed FIX. At the moment I have WLAN the whole time active. 4.5.4 is already downloaded but not installed yet. I think i will upgrade to 4.5.4 now to downgrade and then do the whole stuff again.
Click to expand...
Click to collapse
Ok, enable flightmode to avoid getting updated further to 4.5.5 then.
And good luck, I'm really not sure about this.
Does someone know if this root app works normally? (click)
After a few tries I can now locate to /system/priv-app/DeviceSoftwareOTA.apk but I am not able to rename this apk.
Can I also try these ways to root the Fire HDX 7" or will i brick my device then? (click)
//edit I just enabled wrong locations and it worked with kingroot
// edit now i got cm11 installed Can I also try other roms like CM12 and insert them in the Rom-slot 2? If it fails, my device isn't bricked, because i only have to restart and load rom-stock or rom slot 1, right?
The only big problem I noticed so far is the battery. After 8 hours in sleeping mode (only screen off) the battery status sank from 90% to 55%. How can I fix this problem?

Possible to unlock bootloader on HDX 8.9" (apollo)

Heres the deal I have a kindle fire HDX 8.9" (Apollo) On firmware version 14.3.2.4_user_324002120 and was wondering if it is possible to unlock the bootloader.
Montisaquadeis said:
Heres the deal I have a kindle fire HDX 8.9" (Apollo) On firmware version 14.3.2.4_user_324002120 and was wondering if it is possible to unlock the bootloader.
Click to expand...
Click to collapse
Yes. Procedure involves a rollback to FireOS 14.3.1.x, installation of TWRP recovery, updating the native bootloader and then working through the unlock procedure (tedious for some). Once complete you can flash several HDX compatible roms including Nexus v4, CM11, two lollipop variants (CM12, SlipLP) or stick with FireOS provided you don't want to install gapps.
If needed I can post an outline and link to contributor supplied guides in a day or so ... or perhaps someone will jump in with the gory details. Or you also can browse through the forums. I'd wait for more info as it's pretty easy to brick your device (no recovery) if you go off script. In no case should you tweak build.prop or flash different versions of FireOS without specific instructions.
"If needed I can post an outline and link to contributor supplied guides in a day or so..."
This would be highly appreciated! Thanks!
fabische said:
"If needed I can post an outline and link to contributor supplied guides in a day or so..."
This would be highly appreciated! Thanks!
Click to expand...
Click to collapse
With 3.2.4 you could use the rollback images provided by @ggow. Check page 2 of this thread (page 1 is about 3.2.5/3.2.6 users, who can NOT use the rollback images!).
This would require rooting with HDX Toolkit and installing Safestrap 3.75. With Safestrap v3.7x note that factory reset means standard wipe only! Do NOT open advanced wipe menu, and especially do NOT wipe system! Keep WLAN off/flightmode active to avoid getting updated by Amazon, (re-)root and disable OTA via HDX Toolkit after downgrade, then flash TWRP, update 3.2.3.2 bootloader via TWRP, unlock bootloader and flash ROM of your choice - be sure do create a backup of your Fire OS in TWRP and move it to your PC before you flash any custom ROM!
Read the info, and ask first if you have questions, i.e. before you brick your HDX.
Cl4ncy said:
With 3.2.4 you could use the rollback images provided by @ggow. Check page 2 of this thread (page 1 is about 3.2.5/3.2.6 users, who can NOT use the rollback images!).
This would require rooting with HDX Toolkit and installing Safestrap 3.75. With Safestrap v3.7x note that factory reset means standard wipe only! Do NOT open advanced wipe menu, and especially do NOT wipe system! Keep WLAN off/flightmode active to avoid getting updated by Amazon, (re-)root and disable OTA via HDX Toolkit after downgrade, then flash TWRP, update 3.2.3.2 bootloader via TWRP, unlock bootloader and flash ROM of your choice - be sure do create a backup of your Fire OS in TWRP and move it to your PC before you flash any custom ROM!
Read the info, and ask first if you have questions, i.e. before you brick your HDX.
Click to expand...
Click to collapse
cheers mate! Just wonder how I can rollback my Apollo from 14.4.5.2 to 14.3.2.4 which is required to unlock the bootloader.
All the instructions that I can find state that you cannot rollback below 14.3.2.8....
fabische said:
cheers mate! Just wonder how I can rollback my Apollo from 14.4.5.2 to 14.3.2.4 which is required to unlock the bootloader.
All the instructions that I can find state that you cannot rollback below 14.3.2.8....
Click to expand...
Click to collapse
You can't. Any attempt to rollback below 3.2.8 will brick your device (anti-rollback protection). There is no way to unlock the bootloader on a device that has been upgraded (or began life) above 3.2.6.
However, with 4.5.2 you can root, install Safestrap v4 and then have a choice of CM11 or Nexus v4. Post back if you need assistance.
Davey126 said:
You can't. Any attempt to rollback below 3.2.8 will brick your device (anti-rollback protection). There is no way to unlock the bootloader on a device that has been upgraded (or began life) above 3.2.6.
However, with 4.5.2 you can root, install Safestrap v4 and then have a choice of CM11 or Nexus v4. Post back if you need assistance.
Click to expand...
Click to collapse
Thanks for the quick reply! Basically, I have constant issues with GAPPS running on my rooted 4.5.2 Apollo. For the last six months I have simply blocked any updates of Google Play Services (+chattr command). This was fine for a while, however, meanwhile apps like Google+ & Photos are working less than satisfying. I have updated Google Play Services today which eventually killed my Google Play Store. I managed to get back to the previous so-so state because I had backed up the Google Apps files with Titanium backup. Though my "simple" aim remains to have a working Gapps package on my system. However, the safestrap method, for some strange reason, is currently no option: when I install safestrap 4.1 and try to enter recovery the system goes into a black screen.
To cut a long story short my longterm plan now is to rollback to 3.2.8 again, upgrade to 4.5.2., root and reinstall Gapps manually (or is there a quicker option?). Possibly, Safestrap will work again then too.
Does this make any sense to you?
cheers!
fabische said:
THowever, the safestrap method, for some strange reason, is currently no option: when I install safestrap 4.1 and try to enter recovery the system goes into a black screen.
To cut a long story short my longterm plan now is to rollback to 3.2.8 again, upgrade to 4.5.2., root and reinstall Gapps manually (or is there a quicker option?). Possibly, Safestrap will work again then too.
Does this make any sense to you?
cheers!
Click to expand...
Click to collapse
You are in a tricky situation. If Safestrap v4 won't boot the contents in one of the native Amazon partitions (boot, recovery or system) may be damaged. You need some of these components to rollback or upgrade. If attempted outcomes can range from refusing to process the rollback/update file to an unrecoverable brick. You sometimes see this in a pure stock device. Working fine then bricks after receiving an OTA.
Thoughts:
- it is possible to 'refresh' the recovery partition with Flashify but you will need to find a compatible 4.5.2 recovery image
- suggest you upgrade to 4.5.5 first. Based on limited feedback the risk of a minor FireOS v4 upgrade is less than rolling back.
- if the upgrade is successful you can then attempt a rollback to 3.2.8 followed by upgrade to 4.5.2 (keep WiFi off!!)
- you should uninstall GAaps before upgrading/downgrading.
- there is increased risk if you previously changed permissions on system files to block OTA, etc.
- you will need to reenable OTA (hopefully just a file rename) to up/downgrade.
- I believe Safestrap v4 will install and run correctly if you successfully rollback and upgrade to 4.5.2.
Davey126 said:
You are in a tricky situation. If Safestrap v4 won't boot the contents in one of the native Amazon partitions (boot, recovery or system) may be damaged. You need some of these components to rollback or upgrade. If attempted outcomes can range from refusing to process the rollback/update file to an unrecoverable brick. You sometimes see this in a pure stock device. Working fine then bricks after receiving an OTA.
Thoughts:
- it is possible to 'refresh' the recovery partition with Flashify but you will need to find a compatible 4.5.2 recovery image
- suggest you upgrade to 4.5.5 first. Based on limited feedback the risk of a minor FireOS v4 upgrade is less than rolling back.
- if the upgrade is successful you can then attempt a rollback to 3.2.8 followed by upgrade to 4.5.2 (keep WiFi off!!)
- you should uninstall GAaps before upgrading/downgrading.
- there is increased risk if you previously changed permissions on system files to block OTA, etc.
- you will need to reenable OTA (hopefully just a file rename) to up/downgrade.
- I believe Safestrap v4 will install and run correctly if you successfully rollback and upgrade to 4.5.2.
Click to expand...
Click to collapse
Thanks, davey126. Before I set off for this next adventure: what is your guess that we will see an unlocked bootloader for current fire OS versions in the future? (this might save a lot of trouble)
fabische said:
Thanks, davey126. Before I set off for this next adventure: what is your guess that we will see an unlocked bootloader for current fire OS versions in the future? (this might save a lot of trouble)
Click to expand...
Click to collapse
Close to (effectively) zero. A new vulnerability would have to be discovered followed by an exploit to leverage it. 3rd gen devices have been discontinued; we don't even have root for 4th gen devices. I suspect few resources are being expended on this device. All the (Amazon) excitement surrounds the new $50 USD tablets that have been rooted and have a selection of custom roms. HDX is quickly becoming a beautiful dinosaur. Hi specs are out, cheap is in.
Davey126 said:
You are in a tricky situation. If Safestrap v4 won't boot the contents in one of the native Amazon partitions (boot, recovery or system) may be damaged. You need some of these components to rollback or upgrade. If attempted outcomes can range from refusing to process the rollback/update file to an unrecoverable brick. You sometimes see this in a pure stock device. Working fine then bricks after receiving an OTA.
Thoughts:
- it is possible to 'refresh' the recovery partition with Flashify but you will need to find a compatible 4.5.2 recovery image
- suggest you upgrade to 4.5.5 first. Based on limited feedback the risk of a minor FireOS v4 upgrade is less than rolling back.
- if the upgrade is successful you can then attempt a rollback to 3.2.8 followed by upgrade to 4.5.2 (keep WiFi off!!)
- you should uninstall GAaps before upgrading/downgrading.
- there is increased risk if you previously changed permissions on system files to block OTA, etc.
- you will need to reenable OTA (hopefully just a file rename) to up/downgrade.
- I believe Safestrap v4 will install and run correctly if you successfully rollback and upgrade to 4.5.2.
Click to expand...
Click to collapse
Am I in serious trouble now?
I have followed to downgrade path by first updating (my 3rd Gen Apollo) from 4.5.2 to 4.5.4 and then to 4.5.5. Next was the 3.2.8-downgrade file:
mod-update-kindle-apollo-14.3.2.8_user_714328020.bin
However, starting this downgrade always results in a "Last update failed" message.
It turns out that there are two different 4.5.5 update files.
update-kindle-22.4.5.5_user_455001820
update-kindle-14.4.5.5_user_455001320
I have updated to the more recent "455001820" which actually refuses the downgrade to 14.3.2.8.
Seems I am stuck now?
Can I at least root update-kindle-22.4.5.5_user_455001820?
Thanks!
UPDATE:
Stuck where I was, I allowed my apollo to go online again. It found a newer 4.5.5 Fire os update and I let it download and run through. It now seems that I am on the latest version of 4.5.5. However, with this setup I am still unable to downgrade to 3.2.8. Every attempt to do so delivers a "Last update failed" message...
AFTERTHOUGHT
Could it make any difference if I factory reset the device (i.e. with regards to the downgrading process)? I have also noticed that I did not uninstall GAPPs before updating Fire OS to 4.5.5. However, I did manage to uninstall Google Apps and then also deleted google related files by searching with ES Explorer.
fabische said:
Am I in serious trouble now?
I have followed to downgrade path by first updating (my 3rd Gen Apollo) from 4.5.2 to 4.5.4 and then to 4.5.5. Next was the 3.2.8-downgrade file:
mod-update-kindle-apollo-14.3.2.8_user_714328020.bin
However, starting this downgrade always results in a "Last update failed" message.
It turns out that there are two different 4.5.5 update files.
update-kindle-22.4.5.5_user_455001820
update-kindle-14.4.5.5_user_455001320
I have updated to the more recent "455001820" which actually refuses the downgrade to 14.3.2.8.
Seems I am stuck now?
Can I at least root update-kindle-22.4.5.5_user_455001820?
Thanks!
UPDATE:
Stuck where I was, I allowed my apollo to go online again. It found a newer 4.5.5 Fire os update and I let it download and run through. It now seems that I am on the latest version of 4.5.5. However, with this setup I am still unable to downgrade to 3.2.8. Every attempt to do so delivers a "Last update failed" message...
AFTERTHOUGHT
Could it make any difference if I factory reset the device (i.e. with regards to the downgrading process)? I have also noticed that I did not uninstall GAPPs before updating Fire OS to 4.5.5. However, I did manage to uninstall Google Apps and then also deleted google related files by searching with ES Explorer.
Click to expand...
Click to collapse
I do not think the different subversion of 14.4.5.5 are significant in your situation although good to know they exist.
Yes - I would try a factory reset as others have reported success when update (rollback) files fail to process. This is one of the few cases where benefits of a factory reset outweigh risks. Make sure usb debugging is enabled as it may prove beneficial if your device has trouble restarting after the reset.
Davey126 said:
I do not think the different subversion of 14.4.5.5 are significant in your situation although good to know they exist.
Yes - I would try a factory reset as others have reported success when update (rollback) files fail to process. This is one of the few cases where benefits of a factory reset outweigh risks. Make sure usb debugging is enabled as it may prove beneficial if your device has trouble restarting after the reset.
Click to expand...
Click to collapse
Thanks, davey126. I have made factory reset on my device. I will try to downgrade later today. With regard to unlocking the 4.5.5. bootloader there has been an interesting development: a couple of days ago somebody managed to crack the 4.5.5 bootloader - unfortunately for the Kindle HD 7 (3rd Gen, 2013) only. What is your guess: could this prove useful for the HDX? Could this become a Safestrap alternative? Is it worth the wait?
http://forum.xda-developers.com/kin...ment/unlock-kfsowi-bootloader-unlock-t3262770
fabische said:
Thanks, davey126. I have made factory reset on my device. I will try to downgrade later today. With regard to unlocking the 4.5.5. bootloader there has been an interesting development: a couple of days ago somebody managed to crack the 4.5.5 bootloader - unfortunately for the Kindle HD 7 (3rd Gen, 2013) only. What is your guess: could this prove useful for the HDX? Could this become a Safestrap alternative? Is it worth the wait?
http://forum.xda-developers.com/kin...ment/unlock-kfsowi-bootloader-unlock-t3262770
Click to expand...
Click to collapse
Aside from sharing a generational identifier the two tabs have little in common. It's possible there is some similar code in the bootloader...but that seems unlikely. The real issue imo is the number people working on HDX vs HD variants. Only a few talented devs (I'm not one of them) tinkering with the former which is now discontinued.
Installing Safestrap does not decisively close the door to leveraging future BL exploits should one become available. I also think we may see some progress on a LP/MM rom for SS over time. Fingers crossed!
Davey126 said:
Aside from sharing a generational identifier the two tabs have little in common. It's possible there is some similar code in the bootloader...but that seems unlikely. The real issue imo is the number people working on HDX vs HD variants. Only a few talented devs (I'm not one of them) tinkering with the former which is now discontinued.
Installing Safestrap does not decisively close the door to leveraging future BL exploits should one become available. I also think we may see some progress on a LP/MM rom for SS over time. Fingers crossed!
Click to expand...
Click to collapse
Thanks again, Davey126. All is well now.
It all turned out as you predicted: downgrading 3.2.8 was possible after I made a factory reset on 4.5.5.
The rest was easy: upgrading back to 4.5.2 and rooting.
Your second prediction also proved correct: Safestrap 4.0.1 was not working properly on my fire os stock ROM. However, by going through this whole down- and upgrading process again Safestrap couldn't run smoother as it runs now. Finally, a working Safestrap opened the road (Hallelujah!!) to GET RID OF FIRE OS ONCE AND FOR ALL. I am now on rooted CM11 with GAPPS and starting to explore a new, liberated tablet! One more reason to celebrate!
fabische said:
Thanks again, Davey126. All is well now.
It all turned out as you predicted: downgrading 3.2.8 was possible after I made a factory reset on 4.5.5.
The rest was easy: upgrading back to 4.5.2 and rooting.
Your second prediction also proved correct: Safestrap 4.0.1 was not working properly on my fire os stock ROM. However, by going through this whole down- and upgrading process again Safestrap couldn't run smoother as it runs now. Finally, a working Safestrap opened the road (Hallelujah!!) to GET RID OF FIRE OS ONCE AND FOR ALL. I am now on rooted CM11 with GAPPS and starting to explore a new, liberated tablet! One more reason to celebrate!
Click to expand...
Click to collapse
Excellent - glad everything went as hoped. I suggest you glance through previous posts to make sure everything is configured to give you the best experience.
Enjoy your liberated HDX.

[Help Needed] Flashed 4.5.2 cant update update failed

I flashed 4.5.2 Apollo on my 8.9 HDX from CM11 now Im stuck it doesnt update just says update failed I removed the recovery didnt fix the problem either. Is there a flashable 4.5.5.1 apollo zip? I tried changing the bin to a zip and flashing didnt work said apollo_full instead of apollo as error. Anyone know how to fix it just downloads the update fully then says update failed...
DroidDogg said:
I flashed 4.5.2 Apollo on my 8.9 HDX from CM11 now Im stuck it doesnt update just says update failed I removed the recovery didnt fix the problem either. Is there a flashable 4.5.5.1 apollo zip? I tried changing the bin to a zip and flashing didnt work said apollo_full instead of apollo as error. Anyone know how to fix it just downloads the update fully then says update failed...
Click to expand...
Click to collapse
Be happy 4.5.5.1 didn't take when SafeStrap recovery was installed; device would have bricked. Assume you used the Safestrap compatible variant of 4.5.2 (here). After flashing that (stock slot only; never use secondary slots in SS v4) reboot device and remove Safestrap recovery via SS app. Power down and boot into stock recovery via <power>+<vol-up> and perform a factory reset (you'll loose all apps/data). Reboot again and initialize FireOS. It should then accept OTA updates.
Be 100% sure Safestrap recovery is uninstalled prior to doing a factory reset.
Curious - why to you want 4.5.5.1? Offers no advantage over 4.5.2 if running custom ROMs. Nor will it automatically update to FireOS v5 as Amazon has no plans to release a v5 update for 3rd gen devices.
Ok I went back to 4.5.2 > installed kingroot > went to safestrap > uninstalled recovery > rebooted to stock recovery and factory reset . Its still doing the same thing it downloads to 100 and doesnt do anything...
I might be selling the device and going to a Nexus 9 so I have to make sure it can update or Im going to lose money on the sale.
DroidDogg said:
Ok I went back to 4.5.2 > installed kingroot > went to safestrap > uninstalled recovery > rebooted to stock recovery and factory reset . Its still doing the same thing it downloads to 100 and doesnt do anything...
Click to expand...
Click to collapse
DroidDogg said:
I might be selling the device and going to a Nexus 9 so I have to make sure it can update or Im going to lose money on the sale.
Click to expand...
Click to collapse
IDK - should work. You can try downloading the latest version of FireOS here; installation instructions here. Also verify OTA apk is installed and properly named (here).
It's likely 4.5.x is the terminal release of FireOS for 3rd gen devices; potential buyers will not be severely disadvantaged on 4.5.2.
OK I tried to update to 4.5.5.1 from 4.5.2 (said it was invalid update) do I need to update sequentially like 4.5.3 first?
Update 1: Tried 4.5.3 said update file not valid again. I'm beginning to think this restore file I found on here that was Safestrap 4.5.2 might be the wrong zip for this device even though it installs...
Update 2: Tried another TWRP 4.5.5, it installed, then I did the same thing again removed SafeStrap. Then factory reset...
Why can't I update to 4.5.5.1 after returning from CM11 this is so frustrating.
DroidDogg said:
OK I tried to update to 4.5.5.1 from 4.5.2 (said it was invalid update) do I need to update sequentially like 4.5.3 first?
Update 1: Tried 4.5.3 said update file not valid again. I'm beginning to think this restore file I found on here that was Safestrap 4.5.2 might be the wrong zip for this device even though it installs...
Update 2: Tried another TWRP 4.5.5, it installed, then I did the same thing again removed SafeStrap. Then factory reset...
Why can't I update to 4.5.5.1 after returning from CM11 this is so frustrating.
Click to expand...
Click to collapse
As previously posted - IDK and I do not think anyone else does either. What I do know is every flash (some which appear questionable) presents another failure opportunity that could yield an unrecoverable device. Keep experimenting and posting results; others will learn from your efforts. Just recognize the risk and know when to say 'good enough'. Pushing from 4.5.2 to 4.5.5.1 buys you no additional capability/functionality/stability at this time.
DroidDogg said:
OK I tried to update to 4.5.5.1 from 4.5.2 (said it was invalid update) do I need to update sequentially like 4.5.3 first?
Update 1: Tried 4.5.3 said update file not valid again. I'm beginning to think this restore file I found on here that was Safestrap 4.5.2 might be the wrong zip for this device even though it installs...
Update 2: Tried another TWRP 4.5.5, it installed, then I did the same thing again removed SafeStrap. Then factory reset...
Why can't I update to 4.5.5.1 after returning from CM11 this is so frustrating.
Click to expand...
Click to collapse
Do you checked if the DeviceSoftwareOTA.apk is there? (which @Davey126 mentioned above).
I was in the same situation and had to rename it back, which I'd renamed before as described in the OTA blocking tutorial. http://forum.xda-developers.com/showpost.php?p=59160158&postcount=1
DroidDogg said:
OK I tried to update to 4.5.5.1 from 4.5.2 (said it was invalid update) do I need to update sequentially like 4.5.3 first?
Update 1: Tried 4.5.3 said update file not valid again. I'm beginning to think this restore file I found on here that was Safestrap 4.5.2 might be the wrong zip for this device even though it installs...
Update 2: Tried another TWRP 4.5.5, it installed, then I did the same thing again removed SafeStrap. Then factory reset...
Why can't I update to 4.5.5.1 after returning from CM11 this is so frustrating.
Click to expand...
Click to collapse
did you ever figure this out? i'm in the same boat right now, except i don't even know how to remove the recovery. i'm running safestrap 4.01 and fire rom 4.5.2. I saw another post here http://forum.xda-developers.com/showpost.php?p=49687774&postcount=9 but i'm not quite sure if it will work ( i just don't want to brick my kindle). I got it unrooted but that is about it
mzk1 said:
did you ever figure this out? i'm in the same boat right now, except i don't even know how to remove the recovery. i'm running safestrap 4.01 and fire rom 4.5.2. I saw another post here http://forum.xda-developers.com/showpost.php?p=49687774&postcount=9 but i'm not quite sure if it will work ( i just don't want to brick my kindle). I got it unrooted but that is about it
Click to expand...
Click to collapse
Ignore that post; dangerous to futz with build.prop on this device. Try the following:
- reroot (yes, this is necessary)
- browse to /system/priv-app/ and search for DeviceSoftwareOTA.???, where '???' is likely 'bak' but could be any series of characters
- rename above file to DeviceSoftwareOTA.apk (this is the app {likely one of several} that handles OTA updates on FireOS v4)
- reboot again
- verify device is registered with Amazon
- check every 10-15 min for availability of OTA update; it will almost certainly be 4.5.5.1; allow the update to proceed
Davey126 said:
Ignore that post; dangerous to futz with build.prop on this device. Try the following:
- reroot (yes, this is necessary)
- browse to /system/priv-app/ and search for DeviceSoftwareOTA.???, where '???' is likely 'bak' but could be any series of characters
- rename above file to DeviceSoftwareOTA.apk (this is the app {likely one of several} that handles OTA updates on FireOS v4)
- reboot again
- verify device is registered with Amazon
- check every 10-15 min for availability of OTA update; it will almost certainly be 4.5.5.1; allow the update to proceed
Click to expand...
Click to collapse
Thanks for the steps but I've tried that already. The kindle does find the update but only to 4.5.3. It downloads it and then does nothing. just stays there. It might give an error after a while and go back to where it checks for updates. I tried to side load the newest rom which I have manually downloaded from amazon, the tablet recognized it at first but then gave me an error. Is it crucial to remove the recovery in order to obtain the update?
mzk1 said:
Thanks for the steps but I've tried that already. The kindle does find the update but only to 4.5.3. It downloads it and then does nothing. just stays there. It might give an error after a while and go back to where it checks for updates. I tried to side load the newest rom which I have manually downloaded from amazon, the tablet recognized it at first but then gave me an error. Is it crucial to remove the recovery in order to obtain the update?
Click to expand...
Click to collapse
If you are referring to Safestrap v4 recovery then absolutely yes. The app itself can stay but recovery must be removed (uninstalled). Lucky you didn't score a brick trying to update FireOS with Safestrap recovery installed.
Davey126 said:
If you are referring to Safestrap v4 recovery then absolutely yes. The app itself can stay but recovery must be removed (uninstalled). Lucky you didn't score a brick trying to update FireOS with Safestrap recovery installed.
Click to expand...
Click to collapse
I got to the step where everything is ready to go. the device has been reset to factory default, safestrap recovery has been uninstalled. the device got registered in amazon store and found an update 4.5.3 but it still can't flash it after downloading. I copied the newest 4.5.5 bin file to the tablet, but when i tried to hit update I got a message: unable to complete update because the update file is not valid. please try downloading file again. Right now I'm on the 13.4.5.2 rom which I got here http://forum.xda-developers.com/kindle-fire-hdx/development/hdx-stock-images-pre-rooted-updates-t2911954. Is there any other ideas on how to make update to work?
should I just edit buildprop for downgrade? i will need root for that. Can you advise, please
mzk1 said:
I got to the step where everything is ready to go. the device has been reset to factory default, safestrap recovery has been uninstalled. the device got registered in amazon store and found an update 4.5.3 but it still can't flash it after downloading. I copied the newest 4.5.5 bin file to the tablet, but when i tried to hit update I got a message: unable to complete update because the update file is not valid. please try downloading file again. Right now I'm on the 13.4.5.2 rom which I got here http://forum.xda-developers.com/kindle-fire-hdx/development/hdx-stock-images-pre-rooted-updates-t2911954. Is there any other ideas on how to make update to work?
should I just edit buildprop for downgrade? i will need root for that. Can you advise, please
Click to expand...
Click to collapse
Four choices:
- Modify build.prop, attempt a downgrade and brick your device. Go ahead, I'll wait ...
tip: relying on uncollaborated guidance in a three year old post is rarely best practice
- Root, reinstall Safestrap v4 + CM/Nexus and leave well enough alone. Your device works. Upgrading is not all it's cracked up to be. Kinda like that sweet looking honey/hunk in the bar on a foggy Saturday night.
- As above but reflash the Safestrap compatible (no other) version of FireOS 13.4.5.2. Possible something didn't go well the first time around which is preventing OTAs from being processed correctly. AFAIK - OTA is the only path to 4.5.5.1 as Amazon only offers 4.5.5 for download.
- Attempt a rollback to 3.2.8 followed by an immediate upgrade to 13.4.5.2 as documented here. This path is both the riskiest and the one most likely to clear whatever is blocking OTA updates. If you choose this option be sure to follow instructions exactly including linked files (not others you may have lying around). It is essential WiFi remain off (airplane/flight mode engaged) during the brief window your device is on 13.3.2.8. If an OTA update arrives on this version the device will hard brick with NO possible recovery.
Davey126 said:
Four choices:
- Modify build.prop, attempt a downgrade and brick your device. Go ahead, I'll wait ...
tip: relying on uncollaborated guidance in a three year old post is rarely best practice
- Root, reinstall Safestrap v4 + CM/Nexus and leave well enough alone. Your device works. Upgrading is not all it's cracked up to be. Kinda like that sweet looking honey/hunk in the bar on a foggy Saturday night.
- As above but reflash the Safestrap compatible (no other) version of FireOS 13.4.5.2. Possible something didn't go well the first time around which is preventing OTAs from being processed correctly. AFAIK - OTA is the only path to 4.5.5.1 as Amazon only offers 4.5.5 for download.
- Attempt a rollback to 3.2.8 followed by an immediate upgrade to 13.4.5.2 as documented here. This path is both the riskiest and the one most likely to clear whatever is blocking OTA updates. If you choose this option be sure to follow instructions exactly including linked files (not others you may have lying around). It is essential WiFi remain off (airplane/flight mode engaged) during the brief window your device is on 13.3.2.8. If an OTA update arrives on this version the device will hard brick with NO possible recovery.
Click to expand...
Click to collapse
thanks for the solutions. I figured since it is such a pain to get it to work I'll just stick with Nexus ROM now.
mzk1 said:
thanks for the solutions. I figured since it is such a pain to get it to work I'll just stick with Nexus ROM now.
Click to expand...
Click to collapse
Yep - that would be my choice too. Take note there are two Nexus builds, one for devices that have a 4.5.5.1 kernel, the other for older kernels. Try the former first as it as actively maintained and has a broader feature set. Links below:
old: http://forum.xda-developers.com/kindle-fire-hdx/development/rom-hdx-nexus-v4-0-1-t3125808
new: http://forum.xda-developers.com/kindle-fire-hdx/orig-development/rom-fire-nexus-rom-ktu84q-t3322931

3rd Gen Apollo can't re-enable OTA

I haven't touched this tablet in almost a year and cannot remember how i went about disabling OTA updates. Im on 4.5.2 rooted and safestrap installs fine but will not boot into recovery. So per another thread i was going to update to 4.5.5.1, root, and try to reinstall safestrap. I tried the hdx toolkit but when enabling it says "killed" a bunch of times and never really looks like it does anything but says its re-enabled. it is not enabled. Any ideas on how to re-enable OTA updates if that toolkit will not work. I was going to manually update but there is no internal storage folder when i plug in the tablet. So that isn't working either.
cpiddy said:
I haven't touched this tablet in almost a year and cannot remember how i went about disabling OTA updates. Im on 4.5.2 rooted and safestrap installs fine but will not boot into recovery. So per another thread i was going to update to 4.5.5.1, root, and try to reinstall safestrap. I tried the hdx toolkit but when enabling it says "killed" a bunch of times and never really looks like it does anything but says its re-enabled. it is not enabled. Any ideas on how to re-enable OTA updates if that toolkit will not work. I was going to manually update but there is no internal storage folder when i plug in the tablet. So that isn't working either.
Click to expand...
Click to collapse
There are two methods; will post details shortly (within 24 hours) along with thoughts on avoiding 4.5.5.2 which may not be rootable. Brain is a bit mushy after taxing day; want to make sure I get it right. Sorry for the wait.
cpiddy said:
I haven't touched this tablet in almost a year and cannot remember how i went about disabling OTA updates. Im on 4.5.2 rooted and safestrap installs fine but will not boot into recovery. So per another thread i was going to update to 4.5.5.1, root, and try to reinstall safestrap. I tried the hdx toolkit but when enabling it says "killed" a bunch of times and never really looks like it does anything but says its re-enabled. it is not enabled. Any ideas on how to re-enable OTA updates if that toolkit will not work. I was going to manually update but there is no internal storage folder when i plug in the tablet. So that isn't working either.
Click to expand...
Click to collapse
Davey126 said:
There are two methods; will post details shortly (within 24 hours) along with thoughts on avoiding 4.5.5.2 which may not be rootable. Brain is a bit mushy after taxing day; want to make sure I get it right. Sorry for the wait.
Click to expand...
Click to collapse
To restore OTA update functionality on FireOS 4.5.2 (one or both methods may have been used):
- navigate to /system/priv-app/ and search for DeviceSoftwareOTA.??? where '???' is likely 'bak' or 'apk_'; rename to 'DeviceSoftwareOTA.apk'
- navigate to /system/etc/security/ and search for otacert.zip.orig (or something similar); rename to 'otacert.zip'
Reboot device and check for updates. If FireOS 4.5.5.1 is pending allow it to download/install. If greater than 4.5.5.1 (eg: 4.5.5.2) immediately sever network connections (WiFi off; airplane mode engaged) and reboot your device to delete any partial downloads. Then grab FireOS 4.5.5.1 from this post. Note the image is not there at the moment (4.5.5 and 4.5.5.1 are different beasts). I'm hoping @ONYXis sees this post and updates the repository with the following links:
http://kindle-fire-updates.s3.amazo...Czd/update-kindle-13.4.5.5_user_455002120.bin (Thor)
http://kindle-fire-updates.s3.amazo...CgW/update-kindle-14.4.5.5_user_455002120.bin (Apollo)
Regardless of how FireOS 4.5.5.1 was obtained once installed you should root (Kingroot) and reblock OTA updates using one of the above methods before enabling network connectivity.
Davey126 said:
To restore OTA update functionality on FireOS 4.5.2 (one or both methods may have been used):
- navigate to /system/priv-app/ and search for DeviceSoftwareOTA.??? where '???' is likely 'bak' or 'apk_'; rename to 'DeviceSoftwareOTA.apk'
- navigate to /system/etc/security/ and search for otacert.zip.orig (or something similar); rename to 'otacert.zip'
Reboot device and check for updates. If FireOS 4.5.5.1 is pending allow it to download/install. If greater than 4.5.5.1 (eg: 4.5.5.2) immediately sever network connections (WiFi off; airplane mode engaged) and reboot your device to delete any partial downloads. Then grab FireOS 4.5.5.1 from this post. Note the image is not there at the moment (4.5.5 and 4.5.5.1 are different beasts). I'm hoping @ONYXis sees this post and updates the repository with the following links:
http://kindle-fire-updates.s3.amazo...Czd/update-kindle-13.4.5.5_user_455002120.bin (Thor)
http://kindle-fire-updates.s3.amazo...CgW/update-kindle-14.4.5.5_user_455002120.bin (Apollo)
Regardless of how FireOS 4.5.5.1 was obtained once installed you should root (Kingroot) and reblock OTA updates using one of the above methods before enabling network connectivity.
Click to expand...
Click to collapse
Thank you! That worked perfectly. Now i am having issues installing safestrap. Successfully rooted with king root, downloaded correct version for apollo, but when i go to install it prompts for root access then it gets to 50% mentions busy box, gets to 60% says installing, gets to 90% says cleaning up and then its finished. But nothing is installed and reboot to boot loader is greyed out. Have uninstalled and reinstalled multiple times, not sure what the deal is.
cpiddy said:
Thank you! That worked perfectly. Now i am having issues installing safestrap. Successfully rooted with king root, downloaded correct version for apollo, but when i go to install it prompts for root access then it gets to 50% mentions busy box, gets to 60% says installing, gets to 90% says cleaning up and then its finished. But nothing is installed and reboot to boot loader is greyed out. Have uninstalled and reinstalled multiple times, not sure what the deal is.
Click to expand...
Click to collapse
Quick checks:
- rebooted device after rooting
- messages you receive occur when installing Safestrap Recovery, not the app itself
Davey126 said:
Quick checks:
- rebooted device after rooting
- messages you receive occur when installing Safestrap Recovery, not the app itself
Click to expand...
Click to collapse
I missed the restart after rooting. Did that and was able to successfully install and boot into safe strap. Here's where I get a little confused. I have read through several threads with no real tutorial being available. So when safe strap boots, I want to select slot 1, this asks me to verify sizes, is there any preference here? Second, I'm assuming then I select the rom (cm11) then gapps, then choose to boot to slot 1?
cpiddy said:
I missed the restart after rooting. Did that and was able to successfully install and boot into safe strap. Here's where I get a little confused. I have read through several threads with no real tutorial being available. So when safe strap boots, I want to select slot 1, this asks me to verify sizes, is there any preference here? Second, I'm assuming then I select the rom (cm11) then gapps, then choose to boot to slot 1?
Click to expand...
Click to collapse
Do not create any additional slots. Unlike other Safestrap variants all activity takes place in the STOCK slot on HDX builds. In short you will be overlaying FireOS with CM11.
Secondary slots in Safestrap v4 are a disaster. A few of the liabilities:
- Nexus and FireOS will only run in the stock slot
- CM11 will only utilize 2 of the 4 CPU cores
- those two cores will run at 100% all the time
- device will not enter deep sleep when a secondary slot rom is active
- significant brick risk if backups are restored to a different slot
Davey126 said:
Do not create any additional slots. Unlike other Safestrap variants all activity takes place in the STOCK slot on HDX builds. In short you will be overlaying FireOS with CM11.
Secondary slots in Safestrap v4 are a disaster. A few of the liabilities:
- Nexus and FireOS will only run in the stock slot
- CM11 will only utilize 2 of the 4 CPU cores
- those two cores will run at 100% all the time
- device will not enter deep sleep when a secondary slot rom is active
- significant brick risk if backups are restored to a different slot
Click to expand...
Click to collapse
Awesome! everything successfully installed. Thank you again Davey for all of your help, it is greatly appreciated!

Categories

Resources