Related
[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?
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.
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
Or do we have another way to unlock bootloader without root?
Is downgrading still possible for out of warranty device?
kkcheong said:
Or do we have another way to unlock bootloader without root?
Is downgrading still possible for out of warranty device?
Click to expand...
Click to collapse
- FireOS 4.5.5.2 can be downgraded to 3.2.8 and rooted w/towelroot (procedure)
- once rooted bootloader unlock proceeds as described here
- it is *essential* WiFi be disabled while on 3.2.8 except for the few seconds needed for rooting
- recommend engaging airplane/flight mode as an additional precaution
- failure to observe the above cautions will (with great certainty) result in an unrecoverable brick if an OTA update is downloaded/installed
Thanks. I thought only 4.5.5.1 supported based on first page of the downgrade thread. Upon reading, seems like work on 4.5.5.2 too.
Davey126 said:
- FireOS 4.5.5.2 can be downgraded to 3.2.8 and rooted w/towelroot (procedure)
- once rooted bootloader unlock proceeds as described here
- it is *essential* WiFi be disabled while on 3.2.8 except for the few seconds needed for rooting
- recommend engaging airplane/flight mode as an additional precaution
- failure to observe the above cautions will (with great certainty) result in an unrecoverable brick if an OTA update is downloaded/installed
Click to expand...
Click to collapse
Davey126 said:
- FireOS 4.5.5.2 can be downgraded to 3.2.8 and rooted w/towelroot (procedure)
- once rooted bootloader unlock proceeds as described here
- it is *essential* WiFi be disabled while on 3.2.8 except for the few seconds needed for rooting
- recommend engaging airplane/flight mode as an additional precaution
- failure to observe the above cautions will (with great certainty) result in an unrecoverable brick if an OTA update is downloaded/installed
Click to expand...
Click to collapse
Wait are you saying that towelroot works with 4.5.5.2? Or do you mean that towelroot works after using the downgrade file?
bigboolean said:
Wait are you saying that towelroot works with 4.5.5.2? Or do you mean that towelroot works after using the downgrade file?
Click to expand...
Click to collapse
TowelRoot only works with FireOS v3. However, it is more reliable than KingRoot on FireOS v4 so worth the downgrade effort IMO.
Davey126 said:
TowelRoot only works with FireOS v3. However, it is more reliable than KingRoot on FireOS v4 so worth the downgrade effort IMO.
Click to expand...
Click to collapse
Can you explain the differences and reliability issues with Kingroot FireOS V4?
Archangel1183 said:
Can you explain the differences and reliability issues with Kingroot FireOS V4?
Click to expand...
Click to collapse
- TowelRoot typically roots within seconds; KingRoot can take many iterations
- KingRoot modifies various system files and installs additional components (crapware) without permission
- KingRoot actively resists uninstallation with each revision being increasingly difficult to remove
- TowelRoot is only effective against FireOS 3.x (Android 4.2 based); Kingroot works on a much wider range of Android builds and at present is the only reliable root solution for FireOS v4 and v5
I just rooted my Kindle HDX 7 firmware version 4.5.5.2 with Kingroot v. 4.9.2. You just have to be "VERY PERSISTENT" because it root will fail over and over again but eventually the firmware will give up and let Kingroot root your tablet. I took me 3 hours to root mine so be persistent. Now I'm working on blocking Amazon firmware updates.
RMNDGGG said:
... but eventually the firmware will give up and let Kingroot root your tablet. I took me 3 hours to root mine so be persistent. Now I'm working on blocking Amazon firmware updates.
Click to expand...
Click to collapse
It's not Amazon's firmware somehow resisting rooting; KingRoot's vulnerability detection and exploit matching algorithm is (generously) unsophisticated. Not much better than trial and error with a short fuse.
Also consider unlocking the bootloader and installing a custom ROM (ie: pure Android) to fully liberate your device. You'll probably want to do this anyhow to remove the malware like detritus KingRoot leaves behind.
RMNDGGG, I just installed kingroot 5.0.1 after reading your message and ran it. It looks like my hdx rooted successfully. I double checked it with a root checker and it also said that it's rooted.
Now I need to install Android. I'll search for instructions, but if anyone has a link, can you shoot it over? Thanks
Archangel1183 said:
RMNDGGG, I just installed kingroot 5.0.1 after reading your message and ran it. It looks like my hdx rooted successfully. I double checked it with a root checker and it also said that it's rooted.
Now I need to install Android. I'll search for instructions, but if anyone has a link, can you shoot it over? Thanks
Click to expand...
Click to collapse
You will need to unlock the bootloader first: https://forum.xda-developers.com/kindle-fire-hdx/general/thor-unlocking-bootloader-firmware-t3463982
I renamed 2 OTAupdated files to prevent it from auto updating and turned it off. When I turned it back on, I got a message saying "Updating applications" and it loaded on to a black screen where the home screen should be. I restarted it several times and now it just gets stuck on the "Kindle Fire" loading screen.
Archangel1183 said:
I renamed 2 OTAupdated files to prevent it from auto updating and turned it off. When I turned it back on, I got a message saying "Updating applications" and it loaded on to a black screen where the home screen should be. I restarted it several times and now it just gets stuck on the "Kindle Fire" loading screen.
Click to expand...
Click to collapse
Likely reamed the wrong file(s). If you haven't unlocked the bootloader it's pretty much game over. You can try a 'factory reset' from the stock recovery menu but that rarely fixes system problems. Stock recovery does not offer the ability to reload or repair FireOS. Sorry ...
Yeah, I think I did one too many files. The post I read only mentioned one file but I found two with similar names. I'll try a factory reset later. Thanks, Davey.
I used the Kindle Fire Unbrick Utility V1.1 that I found on the forums. I tried a couple different options offered in the tool and it seemed like none of them were doing anything. They kept saying "Device not found". I knew the computer was detecting it because I installed the drivers a couple weeks back and it was showing "Fire" in device manager. I was done with the tool and was going to use this unbricking method (forum.xda-developers.com/showthread.php?t=2793253), when my kindle suddenly went passed the boot screen into my lock screen. I unlocked it and again got a black screen. I wanted to get into ES File explorer to rename the 2nd file back to the original name, but I couldn't see any app icons. I accidentally swiped up from the bottom and a menu with app icons popped up. I was then able to get into ES File explorer and rename the file. I exited the app and wooot.... no more black screen.
For anyone reading this..... DO NOT Rename DeviceSoftwareOTAContracts.apk or you will get a black home screen without any apps. I renamed DeviceSoftwareOTA.apk to DeviceSoftwareOTAold (no apk) and it's working fine. So far my Kindle fire HDX 7 is still rooted.
Hi guys,
I have KFHDX 7 3rd generation I rooted and installed custom rom long time ago. Now I wanted to get back to fire os and update to 4.5.4. I deleted the custom rom which was installed in slot 2 then unistalled safetrap and unblocked OTA then the update started downloading but every time it reaches 100% it says updatig failure I tried to restart then It took to safetrap recovery ! I'm sure I deleted it !
Please help me befre I brick the device.
Thx
i_a7mdona said:
Hi guys,
I have KFHDX 7 3rd generation I rooted and installed custom rom long time ago. Now I wanted to get back to fire os and update to 4.5.4. I deleted the custom rom which was installed in slot 2 then unistalled safetrap and unblocked OTA then the update started downloading but every time it reaches 100% it says updatig failure I tried to restart then It took to safetrap recovery ! I'm sure I deleted it !
Please help me befre I brick the device.
Thx
Click to expand...
Click to collapse
I'll respond to this in the next 12-24 hours; sorry for the delay (too many irons in the fire).
Davey126 said:
I'll respond to this in the next 12-24 hours; sorry for the delay (too many irons in the fire).
Click to expand...
Click to collapse
Thanks,
I'm looking forward to your reply.
i_a7mdona said:
Hi guys,
I have KFHDX 7 3rd generation I rooted and installed custom rom long time ago. Now I wanted to get back to fire os and update to 4.5.4. I deleted the custom rom which was installed in slot 2 then unistalled safetrap and unblocked OTA then the update started downloading but every time it reaches 100% it says updatig failure I tried to restart then It took to safetrap recovery ! I'm sure I deleted it !
Please help me before I brick the device.
Click to expand...
Click to collapse
Two critical questions:
- what version of Safestrap is currently installed (v3 or v4)?
- what ROMs and versions are/were installed in the stock slot and slots 1 & 2?
Be aware that rooting the device may have destroyed the ability to receive OTA updates. At present that is the only way to receive FireOS 4.5.4 short of rolling your own flashable update which is not for the faint of heart. Third gen devices do not have the ability to install or even refresh FireOS via stock recovery; OTA is the only way to receive updates (thanks, Amazon).
Davey126 said:
Two critical questions:
- what version of Safestrap is currently installed (v3 or v4)?
- what ROMs and versions are/were installed in the stock slot and slots 1 & 2?
Be aware that rooting the device may have destroyed the ability to receive OTA updates. At present that is the only way to receive FireOS 4.5.4 short of rolling your own flashable update which is not for the faint of heart. Third gen devices do not have the ability to install or even refresh FireOS via stock recovery; OTA is the only way to receive updates (thanks, Amazon).
Click to expand...
Click to collapse
Safestrap v 4.01 was installed and I deleted it but the device still boots to the recovery and I had nexus rom in slot 2 the stock slot wasn't touched at all when I unblocked the OTA it started to download 4.5.4 but it stuck at 100% I just want to get rid of safestrap and update to 4.5.4 plus I deleted nexus rom already.
i_a7mdona said:
Safestrap v 4.01 was installed and I deleted it but the device still boots to the recovery and I had nexus rom in slot 2 the stock slot wasn't touched at all when I unblocked the OTA it started to download 4.5.4 but it stuck at 100% I just want to get rid of safestrap and update to 4.5.4 plus I deleted nexus rom already.
Click to expand...
Click to collapse
- boot into FireOS (stock slot)
- reinstall Safestrap apk from here (important: be sure to use the correct build for your device)
- boot into Safestrap recovery
- verify slot 2 (and 1 if it exists) has been DELETED
- reboot into FireOS
- launch Safestrap app
- from within Safestrap app delete Safestrap recovery (likely the part you forgot to do before)
- exit Safestrap app
- reboot device; it should now go straight to FireOS without displaying Safestrap 'robot' prompt
- delete Safestrap app
Congratulations! You are now on pure FireOS.
Davey126 said:
- boot into FireOS (stock slot)
- reinstall Safestrap apk from here (important: be sure to use the correct build for your device)
- boot into Safestrap recovery
- verify slot 2 (and 1 if it exists) has been DELETED
- reboot into FireOS
- launch Safestrap app
- from within Safestrap app delete Safestrap recovery (likely the part you forgot to do before)
- exit Safestrap app
- reboot device; it should now go straight to FireOS without displaying Safestrap 'robot' prompt
- delete Safestrap app
Congratulations! You are now on pure FireOS.
Click to expand...
Click to collapse
Apearntly I lost the rooting. do I have to worry about OTA not blocked with safestrap installed? Cause I reinstall ES abd tried to block OTA but it won't let me it won't let me activate root explorer either. Do I have to do somethig before installing safestrap again?
i_a7mdona said:
Apearntly I lost the rooting. do I have to worry about OTA not blocked with safestrap installed? Cause I reinstall ES abd tried to block OTA but it won't let me it won't let me activate root explorer either. Do I have to do somethig before installing safestrap again?
Click to expand...
Click to collapse
SafeStrap app will reinstall regardless of root status. However, you will not be able to remove Safestrap​ Recovery if the host ROM (presumably FireOS 4.5.2 or 4.5.5.1) is not rooted. KingRoot is the only reliable method for rooting most versions of FireOS including those mentioned above.
OTA status is uncertain give previous update attempt. However, an 'official' update likely will not be processed with SafeStrap v4 recovery installed and may trigger a bootloop.
You may have to abandon efforts to restore stock FireOS environment...
Davey126 said:
SafeStrap app will reinstall regardless of root status. However, you will not be able to remove Safestrap​ Recovery if the host ROM (presumably FireOS 4.5.2 or 4.5.5.1) is not rooted. KingRoot is the only reliable method for rooting most versions of FireOS including those mentioned above.
OTA status is uncertain give previous update attempt. However, an 'official' update likely will not be processed with SafeStrap v4 recovery installed and may trigger a bootloop.
You may have to abandon efforts to restore stock FireOS environment...
Click to expand...
Click to collapse
I reinstalled safestrap, rooted my device using kingroot and, unistalled safestrap recovery, unblocked OTA and unistalled safestrap & kingroot. I l restarted the device it goes straight to the stock fire os but unfortunately I don't recieve the update "last update failed".
i_a7mdona said:
I reinstalled safestrap, rooted my device using kingroot and, unistalled safestrap recovery, unblocked OTA and unistalled safestrap & kingroot. I l restarted the device it goes straight to the stock fire os but unfortunately I don't recieve the update "last update failed".
Click to expand...
Click to collapse
Yep - common occurrence once rooted. Unfortunately, restoring pure stock is nearly impossible. You could install a vulnerable bootloader and TWRP (both fairly easy) and flash a customized build of FireOS 4.5.2 which is the latest available as of this writing. Still doesn't provide a path to 4.5.4 but likely close enough.
Davey126 said:
Yep - common occurrence once rooted. Unfortunately, restoring pure stock is nearly impossible. You could install a vulnerable bootloader and TWRP (both fairly easy) and flash a customized build of FireOS 4.5.2 which is the latest available as of this writing. Still doesn't provide a path to 4.5.4 but likely close enough.
Click to expand...
Click to collapse
If I have stcok 4.5.2. Why should I go for customized 4.5.2? Is it any different?
i_a7mdona said:
If I have stcok 4.5.2. Why should I go for customized 4.5.2? Is it any different?
Click to expand...
Click to collapse
No difference. I did not know what version you currently have and referenced 4.5.2 as the highest flashable build available given 4.5.4 was the stated goal.
To the best of my knowledge there are no functional difference between 4.5.2 and 4.5.4; only minor security updates.
Davey126 said:
No difference. I did not know what version you currently have and referenced 4.5.2 as the highest flashable build available given 4.5.4 was the stated goal.
To the best of my knowledge there are no functional difference between 4.5.2 and 4.5.4; only minor security updates.
Click to expand...
Click to collapse
Thanks a lot for the help. What if I perform manufacture reset or flash a new fire stcok I'm afraid that it will ask me to update to able to use kindle fire features.
i_a7mdona said:
Thanks a lot for the help. What if I perform manufacture reset or flash a new fire stcok I'm afraid that it will ask me to update to able to use kindle fire features.
Click to expand...
Click to collapse
Factory reset only removes personal data; operating system (FireOS) remains untouched. 3rd gen HDX devices are EOL - there won't be any further updates beyond the occational security patch.
Davey126 said:
Factory reset only removes personal data; operating system (FireOS) remains untouched. 3rd gen HDX devices are EOL - there won't be any further updates beyond the occational security patch.
Click to expand...
Click to collapse
Guess what! After I signed in into amazon and I really hopless it started to download the update as usual but this time it installed it and succeeded. I guess I should've done that before. Anyway thanks a lot for everything and I'm really sorry for taking much of your precious time.
i_a7mdona said:
Guess what! After I signed in into amazon and I really hopless it started to download the update as usual but this time it installed it and succeeded. I guess I should've done that before. Anyway thanks a lot for everything and I'm really sorry for taking much of your precious time.
Click to expand...
Click to collapse
Yikes - sorry I didn't think of that and led you down a merry path of misinformation based on experiences from others. Yes, signing into Amazon is an OTA enabler albeit not always a prerequisite. I have seen updates take place without registering with Amazon (often to the dismay of the device owner!) and no OTA activity until signed in. Appears your device fell into the latter category. Not sure what all of the behind-the-scenes triggers are.
Most important, you got the FireOS updates you were seeking. Glad it all worked out. Enjoy your refreshed device!