Related
Hello,
I'm hoping that someone can help me out with this.
Last December i bought a Fire HDX 7 (Thor). I immediatley followed the procedure to install Safestrap and the Thor Nexus ROM v2.0.1. Shortly after that my device got lost. Just last week I found it because my parents moved. After this I started looking around the internet to check if there are any 5.0 or 5.1 ROMs available. I found out they are indeed available.
What I want to do now is get rid of Safestrap, unlock the bootloader and install TWRP to be able to flash new ROMs. I want to start using TWRP because I'm used to working with TWRP.
The problem is that I can't seem to find a way to get this done, despite searching for it on this page for several hours. Can anyone help me on the right track? Would be very much appreciated.
Timmetjuh said:
Hello,
I'm hoping that someone can help me out with this.
Last December i bought a Fire HDX 7 (Thor). I immediatley followed the procedure to install Safestrap and the Thor Nexus ROM v2.0.1. Shortly after that my device got lost. Just last week I found it because my parents moved. After this I started looking around the internet to check if there are any 5.0 or 5.1 ROMs available. I found out they are indeed available.
What I want to do now is get rid of Safestrap, unlock the bootloader and install TWRP to be able to flash new ROMs. I want to start using TWRP because I'm used to working with TWRP.
The problem is that I can't seem to find a way to get this done, despite searching for it on this page for several hours. Can anyone help me on the right track? Would be very much appreciated.
Click to expand...
Click to collapse
Your options are determined by the current version of Amazon firmware installed on your device. I assume you retained Fire OS in the base slot. Boot into that and poke around settings until you find the version number (should be 13.x.x plus some other gibberish). Post what you find and we'll go from there.
Caution: You should disable wifi immediately after booting into Fire OS to prevent an automatic update from Amazon from spoiling your day. At minimum an update will limit future options. I can also brick your device depending on firmware level and other previous mods (including safestrap). Disabling wifi in Nexus is not sufficient as the two roms operate independently.
Davey126 said:
Your options are determined by the current version of Amazon firmware installed on your device. I assume you retained Fire OS in the base slot. Boot into that and poke around settings until you find the version number (should be 13.x.x plus some other gibberish). Post what you find and we'll go from there.
Caution: You should disable wifi immediately after booting into Fire OS to prevent an automatic update from Amazon from spoiling your day. At minimum an update will limit future options. I can also brick your device depending on firmware level and other previous mods (including safestrap). Disabling wifi in Nexus is not sufficient as the two roms operate independently.
Click to expand...
Click to collapse
Could it be that I somehow deleted the Fire OS back then? Don't really remeber what I did exactly..
Timmetjuh said:
Could it be that I somehow deleted the Fire OS back then? Don't really remeber what I did exactly..
Click to expand...
Click to collapse
Quite possibly. Enjoy Nexus; it's a good rom. Alternatively, follow the directions to see if you still have Fire OS installed. If at/below v3.2.6 then Lollipop is possible albeit with a lot of work and significant risk to your device. Otherwise you are limited to Fire OS and Nexus.
Seriously, if you don't recall what you did and can't figure out how start Safestrap in recovery mode be happy with what you have. There are no step-by-step guides. You have to read (a lot) and be prepared for numerous setbacks including an unrecoverable brick of your now working Kindle.
Davey126 said:
Quite possibly. Enjoy Nexus; it's a good rom. Alternatively, follow the directions to see if you still have Fire OS installed. If at/below v3.2.6 then Lollipop is possible albeit with a lot of work and significant risk to your device. Otherwise you are limited to Fire OS and Nexus.
Seriously, if you don't recall what you did and can't figure out how start Safestrap in recovery mode be happy with what you have. There are no step-by-step guides. You have to read (a lot) and be prepared for numerous setbacks including an unrecoverable brick of your now working Kindle.
Click to expand...
Click to collapse
Sorry for my late response.. I just started Safestrap and can only find 1 ROM slot, the Stock ROM slot which probably means that I deleted the original OS.
I did find some files on my laptop that brought some memories back. What I did back then is downgrade the original software to version 13.3.2.6 and than to 13.3.1.0. Does this create any new possibilities?
I just managed to create a new ROM slot and succesfully installed stock 13.3.2.6 on it, so now running on Nexus ROM and stock 13.3.2.6.
Timmetjuh said:
Sorry for my late response.. I just started Safestrap and can only find 1 ROM slot, the Stock ROM slot which probably means that I deleted the original OS.
I did find some files on my laptop that brought some memories back. What I did back then is downgrade the original software to version 13.3.2.6 and than to 13.3.1.0. Does this create any new possibilities?
Click to expand...
Click to collapse
Timmetjuh said:
I just managed to create a new ROM slot and succesfully installed stock 13.3.2.6 on it, so now running on Nexus ROM and stock 13.3.2.6.
Click to expand...
Click to collapse
Warning: Do NOT allow Fire OS to auto-update. Doing so will likely brick your device. Short term the best way to prevent this is to only boot into Nexus. If necessary I can walk you through blocking OTA. Seriously - stay out of Fire OS for now.
I am no Safestrap expert but I believe the rom in the 'base' slot becomes the default when you uninstall Safestrap. So you may have some shuffling to do. Another concern is whether removing/reinstalling Fire OS will impact the ability to recognize the OS once Safetrap is gone. You need a functioning version of Fire OS (and recovery) to follow the 'standard' rollback/update/flash procedures.
However, there may be a shortcut. If 13.3.1.0 was the base rom just prior to installing Nexus and wiping out Fire OS you then should be able to flash twrp without further prep. That would give you access to both Nexus variants and CM11. Unfortunately, there is no easy way to determine the bootloader version which is the component that really matters. It should match the last version of Fire OS that was natively installed before you overwrite it with Nexus.
Unfortunately, the recent install of 13.3.2.6 into a safestrap slot complicates matters. I believe installs within Safestrap leaves the bootloader untouched. But I can't be sure. A misstep can leave your device in an unrecoverable condition; don't go experimenting.
Let's see which recovery you have installed. Power down the device then restart holding power + vol-up. When the grey Kindle logo appears release the power key; vol-up can be released a few seconds later. What happens after the grey logo disappears?
Davey126 said:
Warning: Do NOT allow Fire OS to auto-update. Doing so will likely brick your device. Short term the best way to prevent this is to only boot into Nexus. If necessary I can walk you through blocking OTA. Seriously - stay out of Fire OS for now.
I am no Safestrap expert but I believe the rom in the 'base' slot becomes the default when you uninstall Safestrap. So you may have some shuffling to do. Another concern is whether removing/reinstalling Fire OS will impact the ability to recognize the OS once Safetrap is gone. You need a functioning version of Fire OS (and recovery) to follow the 'standard' rollback/update/flash procedures.
However, there may be a shortcut. If 13.3.1.0 was the base rom just prior to installing Nexus and wiping out Fire OS you then should be able to flash twrp without further prep. That would give you access to both Nexus variants and CM11. Unfortunately, there is no easy way to determine the bootloader version which is the component that really matters. It should match the last version of Fire OS that was natively installed before you overwrite it with Nexus.
Unfortunately, the recent install of 13.3.2.6 into a safestrap slot complicates matters. I believe installs within Safestrap leaves the bootloader untouched. But I can't be sure. A misstep can leave your device in an unrecoverable condition; don't go experimenting.
Let's see which recovery you have installed. Power down the device then restart holding power + vol-up. When the grey Kindle logo appears release the power key; vol-up can be released a few seconds later. What happens after the grey logo disappears?
Click to expand...
Click to collapse
I see the following:
Kindle Fire System Recovery
Your Kindle doesn't seem to be able to boot. Resetting your device to Factory defaults may help you to fix this issue.
Then I get the options to Reboot or to reset to Factory Default.
Oh, the Fire OS is not connected to any networks so it won't be able to update.
Timmetjuh said:
I see the following:
Kindle Fire System Recovery
Your Kindle doesn't seem to be able to boot. Resetting your device to Factory defaults may help you to fix this issue.
Then I get the options to Reboot or to reset to Factory Default.
Oh, the Fire OS is not connected to any networks so it won't be able to update.
Click to expand...
Click to collapse
Ok - a working stock recovery. That's good.
I am conflicted on next steps. The scripted approach would have you uninstall Safestrap (assuming Fire OS had remained in slot 0), rollback to 3.1.0 and then install twrp. However, since slot 0 now contains Nexus I do not feel removing Safestrap is wise. Nor to I think reinstalling Fire OS in the base slow will yield a functioning system once Safestrap is gone.
The 'shortcut' would have you flash twrp recovery (via adb or Flashify) since your bootloader *should*_be at the right level due to a previous 3.1.0 rollback. However, if that is not correct you will end up with a borked recovery which is difficult to rectify.
In your shoes I would probably do nothing given the device is fully functional. The developer of the Nexus rom is working on a KitKat 'upgrade' which is close to being released; a Safestrap variant will hopefully follow. There's no shame in running Nexus. Upgrade to v4.4, add a few Xposed modules and you have fully supported, near AOSP environment that's only lacking a few eye candy elements from Lollipop.
Davey126 said:
Ok - a working stock recovery. That's good.
I am conflicted on next steps. The scripted approach would have you uninstall Safestrap (assuming Fire OS had remained in slot 0), rollback to 3.1.0 and then install twrp. However, since slot 0 now contains Nexus I do not feel removing Safestrap is wise. Nor to I think reinstalling Fire OS in the base slow will yield a functioning system once Safestrap is gone.
The 'shortcut' would have you flash twrp recovery (via adb or Flashify) since your bootloader *should*_be at the right level due to a previous 3.1.0 rollback. However, if that is not correct you will end up with a borked recovery which is difficult to rectify.
In your shoes I would probably do nothing given the device is fully functional. The developer of the Nexus rom is working on a KitKat 'upgrade' which is close to being released; a Safestrap variant will hopefully follow. There's no shame in running Nexus. Upgrade to v4.4, add a few Xposed modules and you have fully supported, near AOSP environment that's only lacking a few eye candy elements from Lollipop.
Click to expand...
Click to collapse
It's not that I don't like the Nexus ROM, I just like to experiment with these things..
So I just installed TWRP with Flashify (started Flashify from NEXUS) and now I seem stuck at the grey Kindle fire logo. I'm just going to leave it alone for a few hours, hopefully it boots later today.
Davey126 said:
Ok - a working stock recovery. That's good.
I am conflicted on next steps. The scripted approach would have you uninstall Safestrap (assuming Fire OS had remained in slot 0), rollback to 3.1.0 and then install twrp. However, since slot 0 now contains Nexus I do not feel removing Safestrap is wise. Nor to I think reinstalling Fire OS in the base slow will yield a functioning system once Safestrap is gone.
The 'shortcut' would have you flash twrp recovery (via adb or Flashify) since your bootloader *should*_be at the right level due to a previous 3.1.0 rollback. However, if that is not correct you will end up with a borked recovery which is difficult to rectify.
In your shoes I would probably do nothing given the device is fully functional. The developer of the Nexus rom is working on a KitKat 'upgrade' which is close to being released; a Safestrap variant will hopefully follow. There's no shame in running Nexus. Upgrade to v4.4, add a few Xposed modules and you have fully supported, near AOSP environment that's only lacking a few eye candy elements from Lollipop.
Click to expand...
Click to collapse
It still boots after a very long time, however I don't know if I get the possibility to enter recovery because it takes several hours to boot. Any more ideas?
Timmetjuh said:
It still boots after a very long time, however I don't know if I get the possibility to enter recovery because it takes several hours to boot. Any more ideas?
Click to expand...
Click to collapse
Power down device and attempt to enter recovery by pressing power + vol-up. Release the power button after the grey logo appears; vol-up can be released after a few seconds. What happens next? Likely one of the following (good -> bad):
- blue screen followed by twrp recovery
- stock recovery with only two options: factory reset and reboot
- continuation of grey kindle logo
Davey126 said:
Power down device and attempt to enter recovery by pressing power + vol-up. Release the power button after the grey logo appears; vol-up can be released after a few seconds. What happens next? Likely one of the following (good -> bad):
- blue screen followed by twrp recovery
- stock recovery with only two options: factory reset and reboot
- continuation of grey kindle logo
Click to expand...
Click to collapse
I'm stuck at the grey Kindle logo..
Did it! Managed to flash the stock bootloader, rollback and install TWRP. Now ready to flash CM11. Thanks for you help!
Timmetjuh said:
Did it! Managed to flash the stock bootloader, rollback and install TWRP. Now ready to flash CM11. Thanks for you help!
Click to expand...
Click to collapse
Congrats! Had a bad feeling after your earlier post; glad that was misplaced. Enjoy CM11 and all the goodness that comes from a liberated HDX.
At some point you should consider unlocking the bootloader. That will provide an important fail safe should things go wrong and opens the door to newer roms. Unlike previous flashes there is little/no risk in unlocking. It will either work or not with no adverse consequences. Unlocking can be a frustrating ride as the process involves multiple steps in unfamiliar territory but ultimately the benefits outweigh the effort IMO. Nothing that needs to be tackled right away but keep it on your radar ... especially if you plan to experiment with other roms.
Unlock bootloader
Hello davey,
I am also interested in getting from safestrap v4 to an unlocked bootloader in order to use a lollipop ROM. My 3rd gen hdx 7 started on 4.5.5 so I did OTA rollback to 3.2.8, upgraded to 4.5.2, then rooted and safestrapped. Unfortunately I lost my stock ROM, but I current have both CM11 and HDZ nexus v4 on 2 different ROM slots. What would be my best way to proceed? From my research so far, it would appear I need to flash hdx nexus 2.0, then flash rollback image to get to modified 3.2.4, and from there 3.1.0 stock update with will allow me to use python method to unlock BL. Is this all correct?
Thanks in advance for your guidance
slothdabski said:
Hello davey,
I am also interested in getting from safestrap v4 to an unlocked bootloader in order to use a lollipop ROM. My 3rd gen hdx 7 started on 4.5.5 so I did OTA rollback to 3.2.8, upgraded to 4.5.2, then rooted and safestrapped. Unfortunately I lost my stock ROM, but I current have both CM11 and HDZ nexus v4 on 2 different ROM slots. What would be my best way to proceed? From my research so far, it would appear I need to flash hdx nexus 2.0, then flash rollback image to get to modified 3.2.4, and from there 3.1.0 stock update with will allow me to use python method to unlock BL. Is this all correct?
Thanks in advance for your guidance
Click to expand...
Click to collapse
No. You can NOT unlock the bootloader! You can NOT downgrade to 3.2.4 and then further to 3.1.0/3.2.3.2! DON'T attempt to do so, you will brick your HDX!
Your only available option is to stay on 4.5.2 and use Safestrap v4 with either Nexus and/or CM11.
slothdabski said:
Hello davey,
I am also interested in getting from safestrap v4 to an unlocked bootloader in order to use a lollipop ROM. My 3rd gen hdx 7 started on 4.5.5 so I did OTA rollback to 3.2.8, upgraded to 4.5.2, then rooted and safestrapped. Unfortunately I lost my stock ROM, but I current have both CM11 and HDZ nexus v4 on 2 different ROM slots. What would be my best way to proceed? From my research so far, it would appear I need to flash hdx nexus 2.0, then flash rollback image to get to modified 3.2.4, and from there 3.1.0 stock update with will allow me to use python method to unlock BL. Is this all correct?
Thanks in advance for your guidance
Click to expand...
Click to collapse
Unfortunately, you can not unlock your bootloader. Amazon introduced anti-rollback protection that will hard brick the device if rolled back below 3.2.8. Sorry, mate.
Davey126 said:
Unfortunately, you can not unlock your bootloader. Amazon introduced anti-rollback protection that will hard brick the device if rolled back below 3.2.8. Sorry, mate.
Click to expand...
Click to collapse
Thanks Davey, you have been very helpful replying to me in another thread also. My reason for seeking a ROM other, than Nexus v4 or CM11, is the kitkat bluetooth tether/VPN bug documented at code.google.com/p/android/issues/detail?id=62714 (sorry for no direct link, xda won't let me post them yet). A "work around" is to establish a wifi connection, even if it doesnt have internet access. This, for whatever reason, allows kitkat to forward the packets to apps on the kindle. I probably could get away with plugging in an old access point at work to enable the sharing sharing of my phones data connection with my safestrap kitkit kindle, but this isn't practical outside of my workplace.
FYI, I cant share my phone's connection via wifi because its an ATT note 4 with lollipop, a locked bootloader, and no permaroot available. I doubt there's a way to tether between 2 android devices via microUSB; but i'd be open to that too!
Thanks again for your wisdom and expertise!
slothdabski said:
Thanks Davey, you have been very helpful replying to me in another thread also. My reason for seeking a ROM other, than Nexus v4 or CM11, is the kitkat bluetooth tether/VPN bug documented at code.google.com/p/android/issues/detail?id=62714 (sorry for no direct link, xda won't let me post them yet). A "work around" is to establish a wifi connection, even if it doesnt have internet access. This, for whatever reason, allows kitkat to forward the packets to apps on the kindle. I probably could get away with plugging in an old access point at work to enable the sharing sharing of my phones data connection with my safestrap kitkit kindle, but this isn't practical outside of my workplace.
FYI, I cant share my phone's connection via wifi because its an ATT note 4 with lollipop, a locked bootloader, and no permaroot available. I doubt there's a way to tether between 2 android devices via microUSB; but i'd be open to that too!
Thanks again for your wisdom and expertise!
Click to expand...
Click to collapse
I actually just got it working by running the following as SU in terminal emaulator
# ip route add default dev tun0 scope link
Not sure yet if I have to do this every time I tether, but if so, i think i can just make a script to execute automatically?
Hi guys,
I got my Kindle Fire HDX 8.9" and my first goal is obviously to get rid of the Fire OS...
My device is currently running 14.3.2.2
I directly started to KFHDX+ Toolkit 0.95 to get root, ota blocker and HDXposed.
But now I'm stuck and need to ask what is now the best way to get CM11 on my apollo.
So let's begin...
I seem to have two choices. Either installation of safestrap or TWRP.
While TWRP sound more complicated, but having more possibilities.
So I have the following two problems
a) Safestrap - it seems it requires XX.4.5.2
I have an older version, so I better not try to install Safestrap on it.
b) TWRP - seems to require .3.2.3.2 and I should unlock my bootloader
Slightly different version from what I use. But I'm not sure if it's compatible anyway... and I have no unlocked bootloader yet. So better not giving it a try
So should I upgrade by ota to the latest Amazon firmware and can use safestrap then? (is xx.4.5.2 the latest?)
Or is there an instruction how to update to .3.2.3.2 and unlock my bootloader as preconditions for TWRP?
Thanks for helping a 8.9 " newbie.
Always interesting to explore a new device, but sometimes hard to understand the simplest things
I'd suggest to update to 3.2.3.2 and use TWRP, it gives you more options, you probably will miss, if you'd update to 4.5.2 and use Safestrap.
I've Thor though, so I'm not exactly sure where you can find 3.2.3.2 for Apollo atm, the bootloader unlock procedure is described here, TWRP Installation here.
If you get stuck at the bootloader unlock procedure with "Waiting for device" in the fastboot prompt, and "Ready" on the HDX, you need to install the correct drivers (check device manager, the HDX is probably there with a yellow exclamation mark then - you're on Windows?).
Before you do anything be sure you have all correct files, and if in doubt ask first (i.e. before you brick your HDX).
Thanks for the link to this great explaination from ceyo14. I found the original post in the same thread, but it was hard to understand what to do. This is much more simpler than expected. I'm running windows.
Since I could not wait yesterday I also already started an experiment to go for 4.5.2 and use safestrap.
My bad is that it did not work. I was trapped in a bootloop and was glad to escape by holding volume down and power. Close call... So I removed safestrap again and I'm back to 0% progress but with 4.5.2.
So I think my next blocking point is the downgrade because I will not follow up the safestrap variant any more. I hope it's possible at all to downgrade and will search later for a tutorial. I assume it's not just copying 3.2.3.2 to internal storage and execute the update via settings
messiah said:
Thanks for the link to this great explaination from ceyo14. I found the original post in the same thread, but it was hard to understand what to do. This is much more simpler than expected. I'm running windows.
Since I could not wait yesterday I also already started an experiment to go for 4.5.2 and use safestrap.
My bad is that it did not work. I was trapped in a bootloop and was glad to escape by holding volume down and power. Close call... So I removed safestrap again and I'm back to 0% progress but with 4.5.2.
So I think my next blocking point is the downgrade because I will not follow up the safestrap variant any more. I hope it's possible at all to downgrade and will search later for a tutorial. I assume it's not just copying 3.2.3.2 to internal storage and execute the update via settings
Click to expand...
Click to collapse
Hm, that was probably a bad idea, I don't think you can downgrade to 3.2.3.2 anymore. You will most likely brick your HDX. So no more unlocked bootloader and TWRP for you, sorry.
You must use the new Safestrap with 4.5.2, and read the requirements carefully!
Cl4ncy said:
Hm, that was probably a bad idea, I don't think you can downgrade to 3.2.3.2 anymore. You will most likely brick your HDX. So no more unlocked bootloader and TWRP for you, sorry.
You must use the new Safestrap with 4.5.2, and read the requirements carefully!
Click to expand...
Click to collapse
@Cl4ncy is correct. You'd better block OTA (or stay off WiFi) or your device will be pushed to 4.5.4 which present a whole new set of headaches. Word of advice: Read up before taking chances. If you 'can not wait' and start trying stuff at random save yourself some time and just toss your device in the trash now (sorry for the harsh comment).
Hi, no problem I will get a another one and will return the current
For safestrap 4.0.1 I rooted the device and have 4.5.2 - pre conditions fulfilled. Boot loop anyway. So I don't now what else should I do...
The strange string is that my device is showing version 14.3.0.0, even I installed 4.5.2 - that must be a remaining of a script I executed to force the Kindle HDX to update to 4.5.2 (http://forum.xda-developers.com/showpost.php?p=55759790&postcount=204)
(My HDX 8.9 did not take the 4.5.2 update)
messiah said:
Hi, no problem I will get a another one and will return the current
For safestrap 4.0.1 I rooted the device and have 4.5.2 - pre conditions fulfilled. Boot loop anyway. So I don't now what else should I do...
The strange string is that my device is showing version 14.3.0.0, even I installed 4.5.2 - that must be a remaining of a script I executed to force the Kindle HDX to update to 4.5.2 (http://forum.xda-developers.com/showpost.php?p=55759790&postcount=204)
(My HDX 8.9 did not take the 4.5.2 update)
Click to expand...
Click to collapse
Upgrade did not fully complete as evidenced by the mismatch between build.prop version and those shown elsewhere. Who knows what else might be missing. FrankenKindle.
flashed a second device sucessfully to CM 12.1 with unlocked bootloader, thanks for the help!
Hello, hoping one you experienced Kindle fire HDX 8.9 users can help me. Ok, my kindle fire HDX is running a stock factory rom/ software. The current firmware is 14.3.10. I rooted it a year ago with one of the programs I found on the net.
I kept getting the add pop-ups, so I used sql editor to change one or two of the fields to stop the add pop-ups as per instructions on the net. What ever root program I used, also disabled OTA updates. I installed the common files for getting the google playstore on the device. So over time, the playstore crashed, kept getting the error most people get about playstore has stopped working. I went in and uninstalled the playstore files. Then I decided to do a factory restore. BIG MISTAKE!!
Kindle fire HDX reset, and put me back to the registration screen. I was able to re-register it, then it went to the grey language screen. I choose English. So the problem is: It keeps looping to the language screen. I can choose English, then ok at the bottom of the screen, but it just goes back to the language screen. I can power it down, and back up. I get my unlock screen, and I can see the icon screen, and even go into the settings for about 20 to 30 seconds before it loops to the grey language screen. The kindle does not do any auto re-booting, it just stays stuck on the language screen until I power it down and back up.
Next, I can connect it to my PC through the USB cable, and the kindle is recognized. I have downloaded the program from XDA developers KFHD SRT 2.0. I can start that program, and it recognizes the Kindle , and it will put it into Fastboot mode. The kindle says fastboot and ready on the screen. I'm not sure what to do at this point. I dont want to jack up my kindle anymore than it already is. I read somewhere, that I may have to order a special USB cable for fastboot. I'm not sure if this is true. I never installed any recovery software on the Kindle, nor did I make a back up that I know of.
So what is the easy fix to get it back to stock and get it out this soft loop. I'm sure it can be repaired being I still have some access. I Thank any of you who will take the time to guide me through the process or point me to the right programs and files needed to get it working again.
Thanks
All you need to do is temporarily re-enable OTA updates (HDX Toolkit?)
rlkellyjr said:
Hello, hoping one you experienced Kindle fire HDX 8.9 users can help me. Ok, my kindle fire HDX is running a stock factory rom/ software. The current firmware is 14.3.10. I rooted it a year ago with one of the programs I found on the net.
I kept getting the add pop-ups, so I used sql editor to change one or two of the fields to stop the add pop-ups as per instructions on the net. What ever root program I used, also disabled OTA updates. I installed the common files for getting the google playstore on the device. So over time, the playstore crashed, kept getting the error most people get about playstore has stopped working. I went in and uninstalled the playstore files. Then I decided to do a factory restore. BIG MISTAKE!!
Kindle fire HDX reset, and put me back to the registration screen. I was able to re-register it, then it went to the grey language screen. I choose English. So the problem is: It keeps looping to the language screen. I can choose English, then ok at the bottom of the screen, but it just goes back to the language screen. I can power it down, and back up. I get my unlock screen, and I can see the icon screen, and even go into the settings for about 20 to 30 seconds before it loops to the grey language screen. The kindle does not do any auto re-booting, it just stays stuck on the language screen until I power it down and back up.
Next, I can connect it to my PC through the USB cable, and the kindle is recognized. I have downloaded the program from XDA developers KFHD SRT 2.0. I can start that program, and it recognizes the Kindle , and it will put it into Fastboot mode. The kindle says fastboot and ready on the screen. I'm not sure what to do at this point. I dont want to jack up my kindle anymore than it already is. I read somewhere, that I may have to order a special USB cable for fastboot. I'm not sure if this is true. I never installed any recovery software on the Kindle, nor did I make a back up that I know of.
So what is the easy fix to get it back to stock and get it out this soft loop. I'm sure it can be repaired being I still have some access. I Thank any of you who will take the time to guide me through the process or point me to the right programs and files needed to get it working again.
Thanks
Click to expand...
Click to collapse
Careful what you read on the "net"; fastboot (special USB) cables are useless on a HDX. KFHD SRT is for a different device. Factory resets on a HDX often result in more harm than good as you discovered.
Stock launcher is likely hosed. Common fix is to sideload a third party launcher (recommend Apex or Nova) to regain temporary control over your device and then repair the problem. The latter is best accomplished by allowing FireOS to upgrade (thus replacing the botched components) but that may create to further headaches given the extensive modifications already made to FireOS and lack of detail around exactly what was done.
You'll need to learn some adb commands to install Apex/Nova via USB tether. A slimmed down version of ADB can be found here (Windows host).
Given your firmware version I suggest flashing TWRP (here) which will give your a 'real' recovery. From there you can install Nexus v2 (new rom) which frees your device from the limitations of FireOS and supports full access to the world of Google including the play store. You can stay on Nexus v2 or take the next step and unlock the bootloader which will open the door to additional roms including Nexus v4, CM11 (both KitKat) and CM12 (lollipop). Note the above is not an Rx; I have left out several steps in the interest if brevity. Will fill in the details as needed.
If you want to keep FireOS then you have to unblock OTA (suggest HDX toolkit) and upgrade to a newer version of FireOS (suggest 3.2.6). There is some risk involved but safer than tinkering with your current install which you lead to an unrecoverable situation.
Update !!!
Thanks for your help. I used HDX tool kit to re-enable updates. The kindle took and update, so it is at 4.5.2. But now it wants to install the newer update as soon as I power it on. What should I do?? Is the newer update (4.5.3 or higher / unknow at this time) still going to allow root.
rlkellyjr said:
Thanks for your help. I used HDX tool kit to re-enable updates. The kindle took and update, so it is at 4.5.2. But now it wants to install the newer update as soon as I power it on. What should I do?? Is the newer update (4.5.3 or higher / unknow at this time) still going to allow root.
Click to expand...
Click to collapse
You'll need to root via adb. You can then disable OTA updates by renaming a system file.
- enable adb via settings -> device -> enable ADB
- tether via standard USB cable
- install minimal adb and fastboot (Windows host)
- open command window, switch to adb directory and issue command 'adb devices'. If no responses install drivers, reboot Windows and try again
- (optional) some lite reading on adb command
- grab kingroot apk, place in adb folder and then issue command 'adb install <package-name>.apk'
- install ES File Explorer in a similar manner
- run kingroot from your HDX. If it requests Internet connectivity enable WiFi briefly (<30 sec) until it completes then immediately disable (or place in airplane mode)
- replace Kinguser with SuperSU (here)
- enable root support in ES File Explorer via toggle in left side panel navigate to /system/priv-app/ and search for DeviceSoftwareOTA.apk
- use ES File Explorer to rename DeviceSoftwareOTA.apk to DeviceSoftwareOTA.old (or whatever name you want provided it does not end in .apk)
At this point you can safely enable WiFi. I strongly suggest installing Safestrap v4 before making any other changes to your device. This tool offers:
- enhanced recovery capability (it is not a full recovery but better than Amazon's tools)
- ability to make a complete backup of your device; essential should something go wrong
- ability to install other roms including Nexus v4 or CM11
Good luck.
final steps in re-rooting and preventing update
What file do I need to rename to prevent the pending update from installing. My kindle is powered off currently, if I turn it on its going to go straight to the kindle fire screen and state installing the update. What do I need to rename the file to? I'm assuming I can do all that you tell me to do thru windows 7 , with the kindle connected via USB and it being powered off????
Thank you for your time in helping me getting it going again.
rlkellyjr said:
What file do I need to rename to prevent the pending update from installing. My kindle is powered off currently, if I turn it on its going to go straight to the kindle fire screen and state installing the update. What do I need to rename the file to? I'm assuming I can do all that you tell me to do thru windows 7 , with the kindle connected via USB and it being powered off????
Thank you for your time in helping me getting it going again.
Click to expand...
Click to collapse
Assuming you missed my prior post given close timestamps. Details here. Kindle must be powered on to issue adb commands. To prevent and immediate OTA either: 1) place device in airplane mode; or 2) move to an area where it can not connect to WiFi.
Follow up, needing help still
Davey126 said:
Assuming you missed my prior post given close timestamps. Details here. Kindle must be powered on to issue adb commands. To prevent and immediate OTA either: 1) place device in airplane mode; or 2) move to an area where it can not connect to WiFi.
Click to expand...
Click to collapse
Thank you Sir. I guess I need to clarify what I meant by update. My kindle has already downloaded the update, so it is trying to install or apply the update upon start up. So I just press and held the power button to power it off. However as soon as I power it back on, the kindle will go back to the screen where it's trying to install the update. Is there a way to stop it from applying the update, and still accomplish what you suggested.
Thank you for any help that you can provide.
rlkellyjr said:
Thank you Sir. I guess I need to clarify what I meant by update. My kindle has already downloaded the update, so it is trying to install or apply the update upon start up. So I just press and held the power button to power it off. However as soon as I power it back on, the kindle will go back to the screen where it's trying to install the update. Is there a way to stop it from applying the update, and still accomplish what you suggested.
Thank you for any help that you can provide.
Click to expand...
Click to collapse
Well that's a problem. Are you certain it is trying to process fully downloaded OTA upate to FireOS (likely 4.5.5) vs completing the 4.5.2 install? The messages look a bit similar. If it is trying to update to a higher version I would let it complete as the risk of interrupting the update mid-stream could leave you in a worse state. You would then need to perform the 3.2.8 rollback / 4.5.2 update again. Or just stay with 4.5.5 depending on your passion around root and/or running an alternate rom (via Safestrap) on this device.
Davey126 said:
Well that's a problem. Are you certain it is trying to process fully downloaded OTA upate to FireOS (likely 4.5.5) vs completing the 4.5.2 install? The messages look a bit similar. If it is trying to update to a higher version I would let it complete as the risk of interrupting the update mid-stream could leave you in a worse state. You would then need to perform the 3.2.8 rollback / 4.5.2 update again. Or just stay with 4.5.5 depending on your passion around root and/or running an alternate rom (via Safestrap) on this device.
Click to expand...
Click to collapse
I think it might be trying to install the 4.5.5. Could be wrong?? So if you suggest, I will let it finish what it's trying to do. But I do want to obtain root again, and install the playstore. I'm not sure if these most recent updates lock the bootloader, where I can not install another custom OS. Or if a roll back will re-enable it. I'm still new to the Kindle. It's been rooted for over a year, and I never had a reason to mess with it, until the start of this thread.
Thank You.
rlkellyjr said:
I think it might be trying to install the 4.5.5. Could be wrong?? So if you suggest, I will let it finish what it's trying to do. But I do want to obtain root again, and install the playstore. I'm not sure if these most recent updates lock the bootloader, where I can not install another custom OS. Or if a roll back will re-enable it. I'm still new to the Kindle. It's been rooted for over a year, and I never had a reason to mess with it, until the start of this thread.
Thank You.
Click to expand...
Click to collapse
If there is no way to stop the installation, then I might as well power it back on , and let it finish. Is there not a way to make it do a factor reset, or boot loader menu I could put it in, providing a little time to modify a the update file to prevent it from updating??
Thanks
rlkellyjr said:
I think it might be trying to install the 4.5.5. Could be wrong?? So if you suggest, I will let it finish what it's trying to do. But I do want to obtain root again, and install the playstore. I'm not sure if these most recent updates lock the bootloader, where I can not install another custom OS. Or if a roll back will re-enable it. I'm still new to the Kindle. It's been rooted for over a year, and I never had a reason to mess with it, until the start of this thread.
Click to expand...
Click to collapse
Updating to 4.5.2 eliminated the path to an unlocked bootloader. However, there is an alternate solution (Safestrap v4) that permits loading other KitKat based roms (currently Nexus and CM11) but you must be running FireOS 4.5.2 first. Note 4.5.5 can not be rooted at present.
I strongly discourage layering gapps onto FireOS. Amazon and Google components don't play nice; you can get it to work (mostly) but maintenance is a nightmare as each version change seems to bring new headaches. A better solution is to use one of the previously mentioned roms which turns your HDX into a 'normal' Android tablet with full access to the Playstore.
As previously mentioned keep WiFi off until your tablet completes whatever updates it is trying to apply. Post back the final version number which will dictate future steps.
Davey126 said:
Updating to 4.5.2 eliminated the path to an unlocked bootloader. However, there is an alternate solution (Safestrap v4) that permits loading other KitKat based roms (currently Nexus and CM11) but you must be running FireOS 4.5.2 first. Note 4.5.5 can not be rooted at present.
I strongly discourage layering gapps onto FireOS. Amazon and Google components don't play nice; you can get it to work (mostly) but maintenance is a nightmare as each version change seems to bring new headaches. A better solution is to use one of the previously mentioned roms which turns your HDX into a 'normal' Android tablet with full access to the Playstore.
As previously mentioned keep WiFi off until your tablet completes whatever updates it is trying to apply. Post back the final version number which will dictate future steps.
Click to expand...
Click to collapse
Ok, its sitting at 4.5.4 airplane mode is on. So what is my next step from here.
Thanks
rlkellyjr said:
Ok, its sitting at 4.5.4 airplane mode is on. So what is my next step from here.
Click to expand...
Click to collapse
To secure root and Safestrap v4 you will need to rollback to 4.5.2 via 3.2.8 (there is no direct path). There is risk involved; procedures need to be followed carefully to avoid permanently bricking your device. Don't take that lightly; new causalities are reported with surprising frequency from individuals who skipped steps or simply made a mistake. Amazon devices are unforgiving. Also note there are no step-by-step guides or videos. It's your responsibility to understand the end-to-end process and associated procedures.
First have a read through this thread. Everything you need is there but like most of the forums it is disorganized and full of off-topic commentary.
Before starting I recommend downloading the following into the suggested folders (you'll need to create these; name them as you wish):
- 3.2.8 rollback file for Apollo (here) -> 328RB folder
- 4.5.2 update file for Apollo (here) -> 452UD folder
- ES File Explorer (here) -> Tools folder
- Kingroot (here) -> Tools folder
Thoughts:
- keep above files in respective folders until needed
- make sure you can see/communicate with your device via USB tether. Vital for transferring files and performing certain functions should things go wrong.
- keep WiFi off at all times unless instructed otherwise. Keep airplane mode engaged (on). If possible stay away from open hotspots; skip WiFi setup when prompted
- WARNING: If you device takes an OTA update during rollback it will almost certainly brick with no chance of recovery. OTA updates are delivered via WiFi.
- WARNING: Never perform a 'factory reset' from the HDX recovery menu unless specifically instructed to do so.
Ask questions if unsure. Good luck.
Thanks for your help
Davey126 said:
To secure root and Safestrap v4 you will need to rollback to 4.5.2 via 3.2.8 (there is no direct path). There is risk involved; procedures need to be followed carefully to avoid permanently bricking your device. Don't take that lightly; new causalities are reported with surprising frequency from individuals who skipped steps or simply made a mistake. Amazon devices are unforgiving. Also note there are no step-by-step guides or videos. It's your responsibility to understand the end-to-end process and associated procedures.
First have a read through this thread. Everything you need is there but like most of the forums it is disorganized and full of off-topic commentary.
Before starting I recommend downloading the following into the suggested folders (you'll need to create these; name them as you wish):
- 3.2.8 rollback file for Apollo (here) -> 328RB folder
- 4.5.2 update file for Apollo (here) -> 452UD folder
- ES File Explorer (here) -> Tools folder
- Kingroot (here) -> Tools folder
Thoughts:
- keep above files in respective folders until needed
- make sure you can see/communicate with your device via USB tether. Vital for transferring files and performing certain functions should things go wrong.
- keep WiFi off at all times unless instructed otherwise. Keep airplane mode engaged (on). If possible stay away from open hotspots; skip WiFi setup when prompted
- WARNING: If you device takes an OTA update during rollback it will almost certainly brick with no chance of recovery. OTA updates are delivered via WiFi.
- WARNING: Never perform a 'factory reset' from the HDX recovery menu unless specifically instructed to do so.
Ask questions if unsure. Good luck.
Click to expand...
Click to collapse
Thank you for all your help.
A tad more info needed
rlkellyjr said:
Thank you for all your help.
Click to expand...
Click to collapse
Can I apply the downgrade with 4.5.4, or do I need to let the kindle update to 4.5.5 before attempting the downgrade. ???
Thanks again.
can rollback be done with firmware 4.5.4 ?
rlkellyjr said:
Thank you for all your help.
Click to expand...
Click to collapse
can the roll back be applied to 4.5.4? or do I need to update all the way to 4.5.5 before doing the roll back. Thanks..
rlkellyjr said:
can the roll back be applied to 4.5.4? or do I need to update all the way to 4.5.5 before doing the roll back. Thanks..
Click to expand...
Click to collapse
rlkellyjr said:
Can I apply the downgrade with 4.5.4, or do I need to let the kindle update to 4.5.5 before attempting the downgrade. ???
Thanks again.
Click to expand...
Click to collapse
You can begin the rollback from any variant of FireOS v4 including 4.5.4.
Hi all,
I've been reading a fair bit, but I'm still not quite certain what the best path is for me with my device.
Current state: I did the rollback from 4.5.2 to 13.3.2.8_user_328003120. I installed Safestrap 3.75 and GGOW's excellent Nexus v1.0.1.
Kindle ROM is sitting in STOCK slot, and Nexus 1.0.1 is in Slot 1. It is rooted. I have not installed the OTA block, but the device is in airplane mode.
I have no data that I'm interested in preserving.
What I'd like to do is get the device to a point where I can install GGOW's newer version of Nexus ROM, and/or the CM series of ROMs. The tablet is used primarily for gaming, and some of the newer games won't run on the older version of Nexus ROM anymore.
SO - it seems to me that I have to go to a newer version of Safestrap (v4) to make this happen. Is this so? If that is so, what's the correct upgrade/migration path to make this happen? Again - I'm not worried about losing all of my data, but I would like to avoid brick, and (ideally), it would be nice to have good recovery options for the future.
Thanks for any help you can provide me!
CanadaDave77 said:
Hi all,
I've been reading a fair bit, but I'm still not quite certain what the best path is for me with my device.
Current state: I did the rollback from 4.5.2 to 13.3.2.8_user_328003120. I installed Safestrap 3.75 and GGOW's excellent Nexus v1.0.1.
Kindle ROM is sitting in STOCK slot, and Nexus 1.0.1 is in Slot 1. It is rooted. I have not installed the OTA block, but the device is in airplane mode.
I have no data that I'm interested in preserving.
What I'd like to do is get the device to a point where I can install GGOW's newer version of Nexus ROM, and/or the CM series of ROMs. The tablet is used primarily for gaming, and some of the newer games won't run on the older version of Nexus ROM anymore.
SO - it seems to me that I have to go to a newer version of Safestrap (v4) to make this happen. Is this so? If that is so, what's the correct upgrade/migration path to make this happen? Again - I'm not worried about losing all of my data, but I would like to avoid brick, and (ideally), it would be nice to have good recovery options for the future.
Thanks for any help you can provide me!
Click to expand...
Click to collapse
You best (really only path) is to upgrade to 4.5.2, root (use Kingroot), install Safestrap v4 and then flash either Nexus v4 or CM11 to the STOCK slot (not a secondary slot as was recommended with Safestrap v3). This will overwrite FireOS but it can be restored from the backup you create or from a 'custom' build of 4.5.2 if you forget/loose the all important backup.
Safestrap v4 provides a modest improvement in recovery options - but it is not nearly as robust as 'native' TWRP or fastboot with an unlocked bootloader (neither are options for you). You can still brick your device with a simple mistake or by going 'off script'. Many folks have gained a false sense of confidence with Safestrap installed. Think of SS v4 as an enabler for CM11 or Nexus v4, not a recovery or multi-boot tool.
Note CM12 and SlimLP can NOT be flashed under Safestrap v4. Only the two KitKat roms referenced above (or a custom version of FireOS should you want to return to stock).
My suggestion is your read through the Safestrap v4 thread (300+ posts!) to expand your knowledge of the process and become familiar with individual procedures. Look for excellent posts from @Cl4ncy and other experienced contributors. When you are ready to take the plunge post a succinct outline of the steps you plan to follow. Any 'gotchas' will quickly be identified by a member of the community.
Got it - thanks.
I've been through about half of that thread so far. The process is a bit long, so I'd like to break it up into a few chunks if I could.
Here's what I'm thinking my "cookbook" would look like to start. Note that I don't have any data that I wish to preserve at all in either the 3.2.8 FireOS or the Nexus ROM 1.0.1. Also note that my current state is that I have 3.2.8 in the stock slot and the Nexus ROM in Slot 1.
1) Ensure I'm in airplane mode (which I am)
2) Download the 4.5.2 stock rom here and put it in the root /sdcard.
3) Boot up 3.2.8 from the stock slot, go into "check for updates" and it should appear there.
4) Allow the update to take effect.
5) Boot into the 4.5.2 OS, ensuring that airplane mode is still on.
6) Uninstall Safestrap 3.75 by going into the "settings" area and uninstalling the package.
7) Reboot - this will take me into 4.5.2 in a "clean" state.
I think the biggest question is the uninstallation of Safestrap. I'm feeling like I might be doing that in the wrong order?
My next steps (and the second chunk of the cookbook) would be to root 4.5.2 using Kingroot, install the new version of Safestrap, back up 4.5.2 to a file on my PC, move 4.5.2 to one of the other ROM slots and install the new Nexus ROM in the stock slot, but I want to make sure I'm taking this slowly so not to brick the device, so I don't want to tackle that until the cookbook is done.
I know it's not of a ton of value compared to the work you do here, Davey, but once I'm done, I'll post the tutorial for everyone who is in my situation in a "clean" format once this is all done and working well so that people have a good starting point. I know a lot of people did the 3.2.8 rollback for Nexus 1.0.1, so they may be in a similar state.
Excellent post here: http://forum.xda-developers.com/showpost.php?p=61531925&postcount=52
Does my process look correct so far?
CanadaDave77 said:
Got it - thanks.
I've been through about half of that thread so far. The process is a bit long, so I'd like to break it up into a few chunks if I could.
Here's what I'm thinking my "cookbook" would look like to start. Note that I don't have any data that I wish to preserve at all in either the 3.2.8 FireOS or the Nexus ROM 1.0.1. Also note that my current state is that I have 3.2.8 in the stock slot and the Nexus ROM in Slot 1.
1) Ensure I'm in airplane mode (which I am)
2) Download the 4.5.2 upgrade file from here and put it in the root /sdcard.
3) Boot up 3.2.8 from the stock slot, go into "check for updates" and it should appear there.
4) Allow the update to take effect.
5) Boot into the 4.5.2 OS, ensuring that airplane mode is still on.
6) Uninstall Safestrap 3.75 by going into the "settings" area and uninstalling the package.
7) Reboot - this will take me into 4.5.2 in a "clean" state.
My next steps (and the second chunk of the cookbook) would be to root 4.5.2 using Kingroot, install the new version of Safestrap, back up 4.5.2 to a file on my PC, move 4.5.2 to one of the other ROM slots and install the new Nexus ROM in the stock slot, but I want to make sure I'm taking this slowly so not to brick the device, so I don't want to tackle that until the cookbook is done.
I know it's not of a ton of value compared to the work you do here, Davey, but once I'm done, I'll post the tutorial for everyone who is in my situation in a "clean" format once this is all done and working well so that people have a good starting point. I know a lot of people did the 3.2.8 rollback for Nexus 1.0.1, so they may be in a similar state.
Does my process look correct so far?
Click to expand...
Click to collapse
Almost (good detail/research!). Thoughts:
- You should remove all secondary slots and uninstall Safestrap recovery prior to upgrading to FireOS v4. SS v3 will not function properly under FireOS v4; results are unpredictable. Be sure to boot into FireOS v3 at least once prior to cleaning house to insure it remains functional. Then return to SS recovery, backup one or both slots (as a precaution should something go wrong) as space permits and then delete all secondary slots. Reboot to FireOS and uninstall Safestrap recovery via the SS app. Then uninstall SS v3 itself (keep a copy of the apk if possible). The above reflect a very conservative path; you may choose to skip/consolidate some steps. Just be sure Safestrap v3 recovery is not installed prior to upgrading to FireOS v4.
- Do not preform any type of 'wipe' or 'factory reset' in Safestrap v3. Not needed and potentially dangerous.
- Download any apks you may need immediately after upgrading before going to 4.5.2. Suggest Kingroot, ES File Explorer and SuperSU (latter as a precaution). Leave all in internal storage (root of SDCARD) which should remain untouched during the upgrade.
- After upgrading to 4.5.2 (with airplane mode engaged) perform the following steps: enable USB debug (settings menu), root with Kingroot, block OTA, install Safestrap v4, boot into SS recovery, take a backup of the stock slot, reboot into 4.5.2 and copy backup directory/contents to your PC. I'll leave it as an exercise to research the details behind those steps.
- Kingroot requires a brief network connection (less than 30 sec). Be aware Amazon may attempt to push an OTA update while connected to the network. Be sure to reenable airplane mode after Kingroot finishes and whack the partially downloaded OTA file if needed.
BTW - not trying to make things difficult; I feel there is significant value in the suggested 'homework' assignment as it will build your confidence, reduce the chance of mistakes (some of which can have dire consequences) and facilitate self-help should something go wrong.
Thanks for the props; what I 'do' simply reflects a regurgitation of info gleaned from others. They are the ones who make all this possible (@ggow in particular). That said, I am sure many will appreciate a 'how to' guide should you decide to publish.
LOL - I certainly didn't think you were trying to make things difficult by suggesting the homework! I want the device to work after I'm done monkeying around with it - and, honestly, it's a matter of pride to feel like I can at least partially feed myself.
Ironically, it took your help to help me feed myself... so, thanks.
Anyway - I've had some very good success! I'm now updated to 4.5.2, Kingrooted, ES File Explorer, Safestrap 4.01 installed, and a backup has been run.
What I did see was that it was trying to download an update during the Kingroot process, and that got to 80%. I'd like to kill that update file before I proceed any further, just in case wireless somehow gets turned back on. I don't see the file in the root of /sdcard, though - do you know where that file goes?
CanadaDave77 said:
LOL - I certainly didn't think you were trying to make things difficult by suggesting the homework! I want the device to work after I'm done monkeying around with it - and, honestly, it's a matter of pride to feel like I can at least partially feed myself.
Ironically, it took your help to help me feed myself... so, thanks.
Anyway - I've had some very good success! I'm now updated to 4.5.2, Kingrooted, ES File Explorer, Safestrap 4.01 installed, and a backup has been run.
What I did see was that it was trying to download an update during the Kingroot process, and that got to 80%. I'd like to kill that update file before I proceed any further, just in case wireless somehow gets turned back on. I don't see the file in the root of /sdcard, though - do you know where that file goes?
Click to expand...
Click to collapse
Congrats on progress to date! You're through the tough hurdles and almost ready for some real fun.
OTA updates are written to the root of sdcard. The partial may have been deleted when the connection severed.
Thoughts:
- The partial OTA, if present, will likely be large. Do a deep search for .bin in ES File Explorer. Make sure 'show hidden files' is enabled.
- You can block further OTA updates in FireOS v4 by renaming DeviceSoftwareOTA.apk to DeviceSoftwareOTA.bak
- There is no need for the above action if you intend to immediately flash cm11 or Nexus v4 to the stock slot in Safestrap which replaces FireOS and associated ota mechanisms.
Hi fellows,
My kindle fire HD 6 - 4th Gen recently updated itself to 5.1.1. It worked well for a few days and one fine morning, it was stuck with a future date - Feb 10, 2036, yes the year 2036.
I've tried all sorts of things to fix it - factory reset, changed my wifi router (cos it says it gets the time from there), hooked onto my friends wifi, talked to Amazon support (useless anyway) but there hasn't been a resolution. Its day 10 today and the date has moved to Feb 19, 2036.
Because of this year mismatch, the kindle considers all the SSL certificates from present year to be obsolete and doesn't connect to anything which is over SSL - HTTPS, Sync, Apps, nothing works. HTTP sites work as expected, no issues at all.
I was wondering if reinstalling the 5.1.1 update manually would help and that is pretty much my last option, any ideas what else I could try apart from trying to root it ?
How wonderfully bizarre! Are you sure you can't adapt to it . There must be some advantage to a device existing 20 years in the future!
I read some posts a while back in Amazon discussions about fixing time problems with the wifi advanced options (long press network name>modify network>advanced options>ip=static), but you'll need to search for required changes unless you, or someone else here, knows exactly what settings to use.
Systemwise, you can download 5.1.1 from here, put it in /sdcard (not in a folder) and see if it will reinstall by pressing Update Now in Device Options. I don't think that works when you're up-to-date, but worth a try. If no luck, you'll need to root to reinstall 5.1.1 in TWRP. @bibikalka reveals it all here.
EDIT: @crankdoofus, just assumed you'd messed around with manually changing time zone in settings, then changing back to auto. You did, right?
Thanks for reply DoLooper. For now, I think its a sign from my future self to connect to time travel portal, only that I don't know the URL
regarding the trials ..
1. I downloaded the update offline and forced update, but it refused saying its already running equal or higher
2. I tried to use the advanced options in wireless connections .. it doesn't seem to have many only a proxy address and option to provide static IP/DHCP
3. Turning of WiFi, Automatic timezone, rebooting and factory reset and all kind of combinations of these four haven't yielded any positive results
Strangely enough, I have a nexus 7 tablet with the same "use network settings" and it seems to having the correct time all this while.
Any other suggestions before I root it ?
crankdoofus said:
Thanks for reply DoLooper. For now, I think its a sign from my future self to connect to time travel portal, only that I don't know the URL
regarding the trials ..
1. I downloaded the update offline and forced update, but it refused saying its already running equal or higher
2. I tried to use the advanced options in wireless connections .. it doesn't seem to have many only a proxy address and option to provide static IP/DHCP
3. Turning of WiFi, Automatic timezone, rebooting and factory reset and all kind of combinations of these four haven't yielded any positive results
Strangely enough, I have a nexus 7 tablet with the same "use network settings" and it seems to having the correct time all this while.
Any other suggestions before I root it ?
Click to expand...
Click to collapse
Probably a factory reset will fix this.
Another option is to update everything to nice rooted Lollipop, and do factory reset during the process. Root first, install TWRP. Then before installing Lollipop format /data first as fat, then back to ext4 . This should clear everything real good, including /sdcard. Without reboot, from TWRP follow the guide to install Lollipop. This should have the cleanest system you can have, with the exception of some small partitions (which could become a problem for you). See what this gets you.
bibikalka said:
Probably a factory reset will fix this.
Another option is to update everything to nice rooted Lollipop, and do factory reset during the process. Root first, install TWRP. Then before installing Lollipop format /data first as fat, then back to ext4 . This should clear everything real good, including /sdcard. Without reboot, from TWRP follow the guide to install Lollipop. This should have the cleanest system you can have, with the exception of some small partitions (which could become a problem for you). See what this gets you.
Click to expand...
Click to collapse
Thanks for the suggestions bibikalka and here is the update.
A factory reset doesn't help. Its still the same.
I tried these steps .. root using kingroot, used gscript (and 453_key_images.zip and flash453.zip) to get into recovery - TWRP. There I formatted /data as fat, then back as ext4. Everything seemed to work OK, no error messages. Then I put back 5.4.1_1133_stock_recovery_uboot to get the recovery back to stock so I could get back in.
After reboot, it spent about 10 minutes optimizing apps, but the problem still remains.
Recovery logs indicate quite a few of these messages, if its of any help...
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
What else can I try :
1. Another ROM perhaps ? - CM11 by ggow ?
2. Downgrade from 5.1.1 to 4.5.3 ?
Any suggestions are welcome, currently this is not a brick but pretty much useless.
crankdoofus said:
Thanks for the suggestions bibikalka and here is the update.
A factory reset doesn't help. Its still the same.
I tried these steps .. root using kingroot, used gscript (and 453_key_images.zip and flash453.zip) to get into recovery - TWRP. There I formatted /data as fat, then back as ext4. Everything seemed to work OK, no error messages. Then I put back 5.4.1_1133_stock_recovery_uboot to get the recovery back to stock so I could get back in.
After reboot, it spent about 10 minutes optimizing apps, but the problem still remains.
Recovery logs indicate quite a few of these messages, if its of any help...
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
What else can I try :
1. Another ROM perhaps ? - CM11 by ggow ?
2. Downgrade from 5.1.1 to 4.5.3 ?
Any suggestions are welcome, currently this is not a brick but pretty much useless.
Click to expand...
Click to collapse
It's all a mystery, but anyway ... A good bet is to downgrade to 4.5.3, and see if FireOS 4 also has the time screwed up. If it becomes OK, try updating to 5.1.1 . If not, I guess you could try CM11, no harm.
bibikalka said:
It's all a mystery, but anyway ... A good bet is to downgrade to 4.5.3, and see if FireOS 4 also has the time screwed up. If it becomes OK, try updating to 5.1.1 . If not, I guess you could try CM11, no harm.
Click to expand...
Click to collapse
So here is the update
Quick update - got it fixed by running an app to sync the time, it just needed root access to do it.
Long update - I saw that 5.1.2 was out, so I thought it might help. Downloaded and updated offline, didn't help. Worse, now I had lost root and Kingroot said it didn't know how to root it - tried about 7 times.
Booted into recovery, lollipop recovery has sideload options. So I setup adb and drivers (thanks to detailed posts by @DoLooper), and side loaded 4.5.3. Rebooted, date still wasn't fixed. But now kingroot was helpful and I chanced upon this app called ClockSync, which needed root access to sync system time with one of the NTP servers worldwide. And now I am upgrading to 5.1.1 to get back where I was but in the present tense. I intend to keep it rooted and keep the ClockSync app handy.
All this nonsense with Amazon yielded a 30$ store credit which should come in handy now
and thanks a lot for your help guys, @DoLooper and @bibikalka, your replies were just enough for me to prod on.
crankdoofus said:
So here is the update
Quick update - got it fixed by running an app to sync the time, it just needed root access to do it.
Long update - I saw that 5.1.2 was out, so I thought it might help. Downloaded and updated offline, didn't help. Worse, now I had lost root and Kingroot said it didn't know how to root it - tried about 7 times.
Booted into recovery, lollipop recovery has sideload options. So I setup adb and drivers (thanks to detailed posts by @DoLooper), and side loaded 4.5.3. Rebooted, date still wasn't fixed. But now kingroot was helpful and I chanced upon this app called ClockSync, which needed root access to sync system time with one of the NTP servers worldwide. And now I am upgrading to 5.1.1 to get back where I was but in the present tense. I intend to keep it rooted and keep the ClockSync app handy.
All this nonsense with Amazon yielded a 30$ store credit which should come in handy now
and thanks a lot for your help guys, @DoLooper and @bibikalka, your replies were just enough for me to prod on.
Click to expand...
Click to collapse
This is interesting! Did you run 5.1.2 rootless, downgraded to 4.5.3, and then upgraded to 5.1.1 from 4.5.3 using my guide ? So your bootloaders now are 5.1.1 (meaning you did not do anything special regarding bootloaders when you went from 5.1.2 to 4.5.3 to 5.1.1 ) ? And everything is working now ?
bibikalka said:
This is interesting! Did you run 5.1.2 rootless, downgraded to 4.5.3, and then upgraded to 5.1.1 from 4.5.3 using my guide ? So your bootloaders now are 5.1.1 (meaning you did not do anything special regarding bootloaders when you went from 5.1.2 to 4.5.3 to 5.1.1 ) ? And everything is working now ?
Click to expand...
Click to collapse
Yes, once I had 5.1.2, I lost root. Kingroot could not root it even after multiple attempts. The only option was to try out sideload. A sideload with 4.5.3 binaries worked. Then I moved on to 5.1.1 using your guide.
After sideloading 4.5.3, the boot loader was also over written with older one (verified by booting into recovery). After upgrade to 5.1.1, now my boot loader is at 5.1.1 stage.
Everything with regards to kindle is working, tried multiple reboots to be sure. I had a glitch with su though.
Supersu, for some reason complains that it needs to be upgraded, but it stays on the screen indefinitely while upgrade (i tried sideload as well, no luck). An adb shell su -v or adb shell su -V returns kingsroot user. So I'm guessing there are some remains of kingsroot still there although I did a wipe at the end as per your procedure. There seems to be partial root as esexplorer can access /sys, etc very well. Adb shell su fails.
I can help with more diagnostics if you need any. Really thankful for the good job that you're doing here !
Further to my investigations with messed up supersu, I realized that kingroot installs root in a strange manner and supersu doesn't seem to like it. In my opinion, supersu will never work till kingroot is incharge (I may be wrong, this is based on my experience). It keeps saying that it needs to be updated, but never gets done.
So while looking for ways to get rid of kingroot (sorry I don't trust that app other than for rooting my device) and installing supersu, I landed at this thread..http://forum.xda-developers.com/general/general/lenovo-k4-note-replace-kingroot-supersu-t3314955.
If you follow the instructions, it works. So now I'm kingroot free, but still rooted with my favorite su binary.
I'm just putting it here for the benefit of others who might want to do the same. @bibikalka, my suggestion is to include this step in your guide instead of flashing the supersu.zip to end up with a neat and clean kingroot free system. Thanks again for supporting us.
crankdoofus said:
Further to my investigations with messed up supersu, I realized that kingroot installs root in a strange manner and supersu doesn't seem to like it. In my opinion, supersu will never work till kingroot is incharge (I may be wrong, this is based on my experience). It keeps saying that it needs to be updated, but never gets done.
So while looking for ways to get rid of kingroot (sorry I don't trust that app other than for rooting my device) and installing supersu, I landed at this thread..http://forum.xda-developers.com/general/general/lenovo-k4-note-replace-kingroot-supersu-t3314955.
If you follow the instructions, it works. So now I'm kingroot free, but still rooted with my favorite su binary.
I'm just putting it here for the benefit of others who might want to do the same. @bibikalka, my suggestion is to include this step in your guide instead of flashing the supersu.zip to end up with a neat and clean kingroot free system. Thanks again for supporting us.
Click to expand...
Click to collapse
This is a fair point, but of somewhat narrow interest. The TWRP install wipes out Kingroot, so it's not really an issue. People like Kingroot to get them root, but then they all of a sudden become super suspicious And for that reason if you get TWRP, you can install fresh copy of FireOS, which has no Kingroot traces.
This worked for me !!
crankdoofus said:
Hi fellows,
My kindle fire HD 6 - 4th Gen recently updated itself to 5.1.1. It worked well for a few days and one fine morning, it was stuck with a future date - Feb 10, 2036, yes the year 2036.
I've tried all sorts of things to fix it - factory reset, changed my wifi router (cos it says it gets the time from there), hooked onto my friends wifi, talked to Amazon support (useless anyway) but there hasn't been a resolution. Its day 10 today and the date has moved to Feb 19, 2036.
Because of this year mismatch, the kindle considers all the SSL certificates from present year to be obsolete and doesn't connect to anything which is over SSL - HTTPS, Sync, Apps, nothing works. HTTP sites work as expected, no issues at all.
I was wondering if reinstalling the 5.1.1 update manually would help and that is pretty much my last option, any ideas what else I could try apart from trying to root it ?
Click to expand...
Click to collapse
Hi, I had the same issue. I didn't want to root my kindle fire so contacted the Amazon support for help. Since my tablet was out of warranty all they could offer was a discount on a new one. This is after collecting all log reports and updating to OS 5.3.2.0 So I did the following which fixed my date and time issue.
Step 1. Enable developer options and turn on ADB. Search and install ADB drivers for your PC/MAC
Step 2. Download the amazon fire 5th generation super tool by root junkie. http://www.rootjunky.com/amazon-fire-5th-gen-supertool/
Step 3. Connect the tablet and run the super tool. Choose option 2. install google play store.
Once this is done, midway through the process it will correct the date and time. once this is done, you can choose to continue to install play store or stop the process.
Don't try to root, there are several warnings all over the forums that it'll brick the device.