Someone released this thing, firerooter, https://plus.google.com/app/basic/communities/115612726860884592519, to root the new kindle fire hd7 KFSOWI on fireos 4.5.2. It appears to work. I know the HDX is unsupported, as the author says... but are the versions of fire is on each device that different? It is open source, so I guess some coder could figure out what exploit is being used and port it to the of hdx 7. It might work out of the box, but I don't want to brick my device. I know it is done through fastboot, I was just wondering if anyone had looked at it or tried it yet
Sent from my KFTHWI using XDA Premium 4 mobile app
the link you refer to does not exist. Could you possibly upload fireoot for general access?
Is this what you are talking about? GitHub link is on the main page.
https://peniscorp.com/firerooter/
Claims it can root any FireOS version. Haven't tried anything myself.
Nope does not work.
jmw03j said:
Is this what you are talking about? GitHub link is on the main page.
https://peniscorp.com/firerooter/
Claims it can root any FireOS version. Haven't tried anything myself.
Click to expand...
Click to collapse
Just tried on my Kindle with Fire OS 4.5.2
AlexZap said:
Someone released this thing, firerooter, https://plus.google.com/app/basic/communities/115612726860884592519, to root the new kindle fire hd7 KFSOWI on fireos 4.5.2. It appears to work. I know the HDX is unsupported, as the author says... but are the versions of fire is on each device that different? It is open source, so I guess some coder could figure out what exploit is being used and port it to the of hdx 7. It might work out of the box, but I don't want to brick my device. I know it is done through fastboot, I was just wondering if anyone had looked at it or tried it yet
Sent from my KFTHWI using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Probably won't ever work. What happens (I'm fairly certain) is that it sends a modified, rooted, stock system image through fastboot. If it wasn't so easy to root the Kindle Fire HDs (not to be confused with the new ones), this would have worked on those as well. The HDXs aren't supported because it is not possible to flash via fastboot with a locked bootloader. You'll get the message "not allowed for locked hw" or something similar. With an unlocked bootloader (which is possible, somehow), this would work.
r3pwn said:
Probably won't ever work. What happens (I'm fairly certain) is that it sends a modified, rooted, stock system image through fastboot. If it wasn't so easy to root the Kindle Fire HDs (not to be confused with the new ones), this would have worked on those as well. The HDXs aren't supported because it is not possible to flash via fastboot with a locked bootloader. You'll get the message "not allowed for locked hw" or something similar. With an unlocked bootloader (which is possible, somehow), this would work.
Click to expand...
Click to collapse
Thanks for the info! I thought it didn't matter if the boot loader was locked or not as to if you could flash a through fastboot. I thought flashing always verified the image signature and that is what kept this from being done with this HDX (flashing a modified system image).
This is a big change on Amazon's part if this is the case if they are allowing unsigned images to be flashed to their new devices. If the boot loader is unlocked, you could probably flash TWRP, or some other custom recovery and root that way. I'd be much more comfortable rooting my device that way then someone's provided modified system image... but whatever...
I guess this means that there is no exploit to speak of, and it is just a tool that makes it easier... oh well. The author talks like it could be ported to other fire is devices, but it sounds like that is not the case.
Sent from my KFTHWI using XDA Premium 4 mobile app
AlexZap said:
Thanks for the info! I thought it didn't matter if the boot loader was locked or not as to if you could flash a through fastboot. I thought flashing always verified the image signature and that is what kept this from being done with this HDX (flashing a modified system image).
This is a big change on Amazon's part if this is the case if they are allowing unsigned images to be flashed to their new devices. If the boot loader is unlocked, you could probably flash TWRP, or some other custom recovery and root that way. I'd be much more comfortable rooting my device that way then someone's provided modified system image... but whatever...
I guess this means that there is no exploit to speak of, and it is just a tool that makes it easier... oh well. The author talks like it could be ported to other fire is devices, but it sounds like that is not the case.
Sent from my KFTHWI using XDA Premium 4 mobile app
Click to expand...
Click to collapse
That's not exactly correct. Amazon has never allowed flashing unsigned images on any of their devices, including the Kindle Fire HD line; it's just that people have found a way to unlock the bootloader.
Anyways, we should be expecting TWRP and all that good stuff very soon thanks to vortox: http://forum.xda-developers.com/showpost.php?p=57767482&postcount=27
EncryptedCurse said:
That's not exactly correct. Amazon has never allowed flashing unsigned images on any of their devices, including the Kindle Fire HD line; it's just that people have found a way to unlock the bootloader.
Anyways, we should be expecting TWRP and all that good stuff very soon thanks to vortox: http://forum.xda-developers.com/showpost.php?p=57767482&postcount=27
Click to expand...
Click to collapse
Yep. He must have misunderstood my post. System partitions aren't ever signature checked because they're just too damn large. It would take an eternity.
The HDX is a different beast entirely that doesn't use fastboot and the boot loader is totally locked down.
Best case scenario: the program does nothing.
Worst case scenario: bricked HDX
Anyone is working on finding a root method for 4.5.2 ? (I'm biting my hands every time I remember that first thing after powering my kindle on, was to upgrade it)
lol...me too..gutted..
Well then...
All I need to do is to install a custom Rom (Cynogenmod, cuz fire OS sucks) via TWRP, so if he can actually make that exploit work, I would be very happy that I can actually customize my kindle and use it to its full potential. The hardware is good, the OS, not so much.
FireOS is great actually... but the desire is to have Google Play as well.
Ask amazon yo roll it back. Explain you are getting random shutdowns and the OS is lagging. That's what I done.
veaceslav said:
Anyone is working on finding a root method for 4.5.2 ? (I'm biting my hands every time I remember that first thing after powering my kindle on, was to upgrade it)
Click to expand...
Click to collapse
Not sure about 4.5.2, but you CAN downgrade:
http://forum.xda-developers.com/kindle-fire-hdx/general/rollback-to-devices-upgraded-to-4-x-t2946946
Then root using Towelroot(what I did) or the HDX toolkit.
Tried it, it works with the 2 FIreOS versions (11.3.2.5 and 11.4.5.2) (for Amazon Kindle Fire 7 HD SOHO [2013, 3rd Gen])
Only issues I have with FireOS 4.5.2 is that even with XPosed Modules to block OTA Updates and System Updates, it still continues to download the 4.5.4 update (tho it never installs it) .... Secondly with 4.5.2, the wall papers have mysteriously disappeared from the framework-res.apk ....
11.3.2.5 is the way to go, albeit stone age vs 11.4.5.2. With 3.2.5, I can modify all the wallpapers, the lockscreen ad, the bootup logo, and not have to worry about it downloading system updates. I say 3.2.5 is the way to go because if you just want to root it for Wallpapers, you don't need all the extra stuff and really don't need the newer OS.
_RumRunner_ said:
Tried it, it works with the 2 FIreOS versions (11.3.2.5 and 11.4.5.2) (for Amazon Kindle Fire 7 HD SOHO [2013, 3rd Gen])
Only issues I have with FireOS 4.5.2 is that even with XPosed Modules to block OTA Updates and System Updates, it still continues to download the 4.5.4 update (tho it never installs it) .... Secondly with 4.5.2, the wall papers have mysteriously disappeared from the framework-res.apk ....
11.3.2.5 is the way to go, albeit stone age vs 11.4.5.2. With 3.2.5, I can modify all the wallpapers, the lockscreen ad, the bootup logo, and not have to worry about it downloading system updates. I say 3.2.5 is the way to go because if you just want to root it for Wallpapers, you don't need all the extra stuff and really don't need the newer OS.
Click to expand...
Click to collapse
Wrong forum; look here. Firerooter does not work with HDX devices.
ahhh yeah... i thought was just a general question if firerooter worked at all... my apologies.
Its nice to get a response though, considering the 2 I've posted that no one seems to know anything about
again my apologies!
Related
From many many different threads and frankly confusing instructions I think I have puzzled together the following solid guideline for my kindle fire hdx from basic root to custom rom. Currently my firmware is 13.3.1.0.
Could someone take a look at this and tell me if I got this right or if I need to do stuff differently (or could do them better)? Don't assume that something is obvious, if it isn't written down, don't be shy to mention it. I would be ever so grateful .
Edit: I'm updating my experience as I move along the list and get more info just in case this might be useful to someone who is just as lost as I was in the beginning
Obligatory disclaimer: this is just a step-by-step guideline that worked for me. I'm not responsible if you chose to follow any of these steps and damage or brick your device.
Guideline:
-Download firmware version 3.2.3.2 and upgrade directly from any of the previous version by putting the file into the internal storage of the kindle, going to settings>device>system update on the kindle and installing the update from there.
-Root with Towelroot in the HDX toolkit downloaded from here (Edit: I got various error messages at this step but got it to work in the end. The 3rd post here shows what I did to get it working after getting error message 2 and 3 at various times)
-block OTA also with the tool in the HDX toolkit (is there a way to safely check that this worked? Edit: It worked )
-connect to wifi and install Flashify from the playstore (Edit: I ended up installing File Expert and flashify on another android device, backing up the flashify apk and sideloading it with ES File Explorer from the amazon app store to the kindle, I guess I could have also download the apk somewhere but I have trust issues.)
-download the img of TWRP 2.8.5.0. and put it in internal storage of kindle (had no problems)
-use flashify to save original stock recovery (had no problems)
-Use flashify to flash TWRP (had no problems)
- Boot into recovery mode via flashify to see if it worked (had no problems)
Now either A)
-download CM11 image and gapps and put the zip files on internal storage
-Edit: disconnect Kindle from USB afterwards
- go into TWRP recovery mode (by powering off kindle and then pressing power and volume at the same time)
- make backup of original stockrom under backups and save copy on your Computer
- wipe system, data, cache and dalvik cache under wipe/advanced (all except internal)
- flash cm11 image and gapps (under install and then find them in the files)
- reboot
-Edit: I had the wifi not connecting problem that some people have with CM11 but a reboot took care of it.
-Edit 2: I couldn't get the kindle app to work on CM11 (it wouldn't synch my books, the device wasn't recognized by amazon and it would crash every time I logged in.) so I ended up replacing it with the Nexus rom. If the chance of this happening doesn't bother you then CM11 seems to still be a good choice.
or B)
- download HDX thor nexus rom and gapps and put the zip files on internal storage
- go into TWRP recovery mode (by powering off kindle and then pressing power and volume at the same time)
- make backup of original stockrom under backups and save copy on your Computer
- wipe system, data, cache and dalvik cache under wipe/advanced (all except internal)
- Edit: disconnect Kindle from USB afterwards
- flash nexus rom and gapps (under install and then find them in the files)
- reboot
- Edit: I'm very happy with it, it works flawlessly. Since it's based on Jelly Bean I may try replacing it with another rom sometime in the future, but I'm in no hurry
Mostly correct, you can update directly to 3.2.3.2 no need for incremental steps. The only way to know if ota blocker worked is to check for update but there's really no need, as soon as you've run towel root just disable WiFi as it won't be needed anymore.
Where is unlock bootloader? As I know, you cannot flash TWRP without unlocking bootloader?!
uhraman said:
Where is unlock bootloader? As I know, you cannot flash TWRP without unlocking bootloader?!
Click to expand...
Click to collapse
You can flash a cuber signed TWRP on a locked bootloader, as long as you're below 3.2.4.
derpadoodle said:
You can flash a cuber signed TWRP on a locked bootloader, as long as you're below 3.2.4.
Click to expand...
Click to collapse
Thanks for your replies! Is the method uhraman hinted at the better one?
snorklm said:
Thanks for your replies! Is the method uhraman hinted at the better one?
Click to expand...
Click to collapse
Fully unlocking your bootloader is definitely worthwhile but it's quite a complicated endeavour and not required for running the current custom recoveries and ROMs. I'd recommend you stick with your current method and read up on the unlocking process once you're more conformable working with this device.
derpadoodle said:
Fully unlocking your bootloader is definitely worthwhile but it's quite a complicated endeavour and not required for running the current custom recoveries and ROMs. I'd recommend you stick with your current method and read up on the unlocking process once you're more conformable working with this device.
Click to expand...
Click to collapse
Could I bother you to give me a few examples on *why* it is worthwhile? Thanks!
snorklm said:
Could I bother you to give me a few examples on *why* it is worthwhile? Thanks!
Click to expand...
Click to collapse
- more robust recovery options when recovery (TWRP) is damaged/inaccessible; better chance of reviving a bricked device
- some custom roms install/operate better with unlocked BL (technically should not be needed but sometimes seen in early builds)
- some DRM aware apps on custom roms work better with unlocked BL(eg: playstore, prime)
Guidance form derpadoodle is sound. Enjoy what you have achieved thus far; revisit BL unlock when you are more comfortable with device/technique.
Davey126 said:
- more robust recovery options when recovery (TWRP) is damaged/inaccessible; better chance of reviving a bricked device
- some custom roms install/operate better with unlocked BL (technically should not be needed but sometimes seen in early builds)
- some DRM aware apps on custom roms work better with unlocked BL(eg: playstore, prime)
Guidance form derpadoodle is sound. Enjoy what you have achieved thus far; revisit BL unlock when you are more comfortable with device/technique.
Click to expand...
Click to collapse
Thanks for the sound advice, I will probably never feel comfortable enough for that , especially because I haven't achieved much at all yet. I haven't even flashed TWPR yet.
Yay, I did it. CM11 seems to be working as intended! Thanks again for everyone who replied and also to everyone who put so much work into making and improving all the tools and software necessary to make this kind of thing even possible, I appreciate it!
What firmware were you on to begin your process mate... ?
B3NJY said:
What firmware were you on to begin your process mate... ?
Click to expand...
Click to collapse
I was on 3.0.5 when I got the device. Amazon didn't upgrade the firmware at all before sending it out, then I upgraded to 13.3.2.3. Why do you ask?
Hmm, I have now noticed that the kindle app is not working properly. I can sign in (though every time I sign in or deregister my account the app crashes) but it's not synching any of my books. They don't show up at all. The device (named android device 2 in the kindle app settings) does also not show up under my devices on amazon. Anyone know what the problem could be because this is a bit frustrating. Is this a bug with CM11 or with the amazon app?
snorklm said:
Hmm, I have now noticed that the kindle app is not working properly. I can sign in (though every time I sign in or deregister my account the app crashes) but it's not synching any of my books. They don't show up at all. The device (named android device 2 in the kindle app settings) does also not show up under my devices on amazon. Anyone know what the problem could be because this is a bit frustrating. Is this a bug with CM11 or with the amazon app?
Click to expand...
Click to collapse
Can't say definitively but I would lean towards CM11 as all Amazon apps (kindle/prime/shopping/video) work fine with the Nexus ROM (v2.0.5) which is layered on the same hw/fw base as CM11. Don't get me wrong; CM11 (and the devs who adapted to the HDX) are great! But there may still be a few hiccups with native Amazon apps.
Davey126 said:
Can't say definitively but I would lean towards CM11 as all Amazon apps (kindle/prime/shopping/video) work fine with the Nexus ROM (v2.0.5) which is layered on the same hw/fw base as CM11. Don't get me wrong; CM11 (and the devs who adapted to the HDX) are great! But there may still be a few hiccups with native Amazon apps.
Click to expand...
Click to collapse
Thanks for the opinion! I couldn't find any solution to the problem anywhere online and therefore just finished replacing CM11 with the Nexus rom, now the kindle app works perfectly fine and I'm very satisfied with what I've got. I will keep an eye out on rom development but for now I'm resting on my laurels :victory:. Considering that I was helplessly lost when I first came to the board I'm very happy with how smoothly everything went. But I really needed that step-by-step list I made and the assurance from the pros that it was correct, otherwise I would have probably made a careless mistake :silly:. Maybe it will be useful to a few other newbies as well. Not sure I will ever dare to fully unlock the bootloader like some suggested I might want to do at a later point in time, but we will see . Thanks again for the help!
snorklm said:
Thanks for the opinion! I couldn't find any solution to the problem anywhere online and therefore just finished replacing CM11 with the Nexus rom, now the kindle app works perfectly fine and I'm very satisfied with what I've got. I will keep an eye out on rom development but for now I'm resting on my laurels :victory:. Considering that I was helplessly lost when I first came to the board I'm very happy with how smoothly everything went. But I really needed that step-by-step list I made and the assurance from the pros that it was correct, otherwise I would have probably made a careless mistake :silly:. Maybe it will be useful to a few other newbies as well. Not sure I will ever dare to fully unlock the bootloader like some suggested I might want to do at a later point in time, but we will see . Thanks again for the help!
Click to expand...
Click to collapse
Glad to hear everything is working well! My daily driver is on Nexus and I could not be happier. Everything works as it should. No need to unlock the bootloader unless you plan to do more modding. Enjoy your device!
Nice. I think everybody needs this kind of guide. Whenever a question is asked it just kind of trails off most of the time.
I'm still working on the downgrade piece.
johnwaters said:
Nice. I think everybody needs this kind of guide. Whenever a question is asked it just kind of trails off most of the time.
I'm still working on the downgrade piece.
Click to expand...
Click to collapse
Agreed, I was overwhelmed by all the different threads and possibilities at first. I ended up approaching it like any other research project for a paper or presentation and dumped every solid (and recent) piece of good advice into Evernote and sorting it out there. But writing and updating guides (especially with the fast development I have observed) would be a lot of work, I understand completely why no one would volunteer to do it and everybody would rather answer questions on a case by case basis.
First of all thank you very much! I was looking for something like this, since i am also new to rooting devices and this stuff...
I got a new fire hdx 7 with 13.3.02
I haven't tried anything yet, I am still reading threads and i got some questions here:
http://forum.xda-developers.com/kindle-fire-hdx/general/update-1314-4-1-1-probably-sangria-t2901813
-> I can only find 3.2.3.2 here, which is the firmware u used? Or did you mean another one?
http://forum.xda-developers.com/show....php?t=2665683
-> the second link for hdx toolkit isnt working
How do i get the playstore on my device?
are there anywhere more informations regarding flashify? since i have no idea what this is...
thank you!
dynein said:
First of all thank you very much! I was looking for something like this, since i am also new to rooting devices and this stuff...
I got a new fire hdx 7 with 13.3.02
I haven't tried anything yet, I am still reading threads and i got some questions here:
http://forum.xda-developers.com/kindle-fire-hdx/general/update-1314-4-1-1-probably-sangria-t2901813
-> I can only find 3.2.3.2 here, which is the firmware u used? Or did you mean another one?
http://forum.xda-developers.com/show....php?t=2665683
-> the second link for hdx toolkit isnt working
How do i get the playstore on my device?
are there anywhere more informations regarding flashify? since i have no idea what this is...
thank you!
Click to expand...
Click to collapse
First thing you want to do is block OTA (over the air updates) or your device may be upgraded by Amazon to a level that gives you less options. Suggest using HDX Toolkit (here) to both root and block OTA. Then install twrp (here). From there you can opt to replace Fire OS will several different roms including Nexus, CM11 or CM12.
Flashify is an app that allows flashing recovery and roms from from within Android vs adb or a recovery environment. You can grab it from the Play store or another market. It's a dangerous tool; use with extreme caution.
Be aware that any of the above actions, if executed incorrectly, can permanently brick your device with little/no hope of recovery (guess that's the definition of permanent). Read, read and read some more before taking any action. Be sure to keep WiFi off on your device until OTA is blocked to prevent auto-updates.
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?
I am thinking of buying Kindle Fire HDX 8.9 off ebay that says unable to register with Amazon . As i do not want it as a Kindle and would root and put custom rom on it would this be a problem in any other way?
bbthebeard said:
I am thinking of buying Kindle Fire HDX 8.9 off ebay that says unable to register with Amazon . As i do not want it as a Kindle and would root and put custom rom on it would this be a problem in any other way?
Click to expand...
Click to collapse
You don't have enough information to know whether it can be rooted or accept a custom ROM. Only firmware versions 4.5.2 and below can be rooted. The bootloader can only be unlocked with firmware 3.2.6 and below (ideally 3.2.3 or below). Between those versions you can install Safestrap and a limited selection of ROMs. Be aware Kindles in general and HDX models in particular are not like other android devices. Difficult to tame and easy to brick. The normal suite of advanced tools and recovery techniques don't work with Kindles including 'factory' cables and most fast boot commands. Make a simple mistake and you'll have an expensive door stop.
One has to question any device that can not be registered with Amazon. Why is that? A factory reset should allow the device to be registered to either the previous or new owner.
I,ll give it a miss
Davey126 said:
You don't have enough information to know whether it can be rooted or accept a custom ROM. Only firmware versions 4.5.2 and below can be rooted. The bootloader can only be unlocked with firmware 3.2.6 and below (ideally 3.2.3 or below). Between those versions you can install Safestrap and a limited selection of ROMs. Be aware Kindles in general and HDX models in particular are not like other android devices. Difficult to tame and easy to brick. The normal suite of advanced tools and recovery techniques don't work with Kindles including 'factory' cables and most fast boot commands. Make a simple mistake and you'll have an expensive door stop.
One has to question any device that can not be registered with Amazon. Why is that? A factory reset should allow the device to be registered to either the previous or new owner.
Click to expand...
Click to collapse
Thanks for reply, Having already got a kindle fire hd i thought the hdx would be no problem rooting , Having read your thoughts and other peoples comments i think i will steer clear and definitely give dodgy ebay listing a miss
I have a Kindle Fire HDX 8.9 4th Generation (Saturn) which is rooted (Kingroot) everything works fine on the device however I can't seem to manually or automatically install the latest or any for that matter system updates. Automatic - Device options --> System updates --> check now sees and downloads the update but then fails. If I manually download the update and install it the system reboots and I get a Kindle Fire Fastboot screen. Please help. I love my tablet and really would like to be able to update it. Any help is greatly appreciated.
bnbliss
bnbliss said:
I have a Kindle Fire HDX 8.9 4th Generation (Saturn) which is rooted (Kingroot) everything works fine on the device however I can't seem to manually or automatically install the latest or any for that matter system updates. Automatic - Device options --> System updates --> check now sees and downloads the update but then fails. If I manually download the update and install it the system reboots and I get a Kindle Fire Fastboot screen. Please help. I love my tablet and really would like to be able to update it. Any help is greatly appreciated.
bnbliss
Click to expand...
Click to collapse
This seems to be an artifact of rooting with Kingroot. Not enough information (yet) to understand what happens. I assume you took no steps to manually block OTA updates.
Updating a rooted device, especially Fires, carries an increased risk of bad outxomes. I suggest using Super-SUme (paid app) to remove Kinguser and install SuperSU. While your device will remain rooted there is a better understand of how SuperSU operates on this device.
Guessing you are on FireOS v4.5.5.1 and looking to update to FireOS v5. Correct?
I am on 4.5.3 I downloaded and paid for Super-SUme doesn't seem to run on my Kindle for some reason. I have a sneaky suspicion that permissions may have gotten messed up on whatever folder recovery image goes to
Davey126 said:
This seems to be an artifact of rooting with Kingroot. Not enough information (yet) to understand what happens. I assume you took no steps to manually block OTA updates.
Updating a rooted device, especially Fires, carries an increased risk of bad outxomes. I suggest using Super-SUme (paid app) to remove Kinguser and install SuperSU. While your device will remain rooted there is a better understand of how SuperSU operates on this device.
Guessing you are on FireOS v4.5.5.1 and looking to update to FireOS v5. Correct?
Click to expand...
Click to collapse
bnbliss said:
I am on 4.5.3 I downloaded and paid for Super-SUme doesn't seem to run on my Kindle for some reason. I have a sneaky suspicion that permissions may have gotten messed up on whatever folder recovery image goes to
Click to expand...
Click to collapse
Probably too late now but you can usually snag a refund on Super-SUme within a couple hours of purchase. Small potatoes in the grand scheme of a misbehaving Saturn.
Do you have an in-warranty return/exchange option? Messing with FireOS permissions is above my pay grade on this device given limited recovery options should something go wrong.
Recovery lives in a dedicated partition that is risky to modify, not to mention finding the correct image for this device. You can't just drop in anything (eg: cw/twrp). It must be a signed Amazon image appropriate for this device.
Davey126 said:
Probably too late now but you can usually snag a refund on Super-SUme within a couple hours of purchase. Small potatoes in the grand scheme of a misbehaving Saturn.
Do you have an in-warranty return/exchange option? Messing with FireOS permissions is above my pay grade on this device given limited recovery options should something go wrong.
Recovery lives in a dedicated partition that is risky to modify, not to mention finding the correct image for this device. You can't just drop in anything (eg: cw/twrp). It must be a signed Amazon image appropriate for this device.
Click to expand...
Click to collapse
Thanks for reaching out with your suggestions. For now it looks like I'm stuck on 4.5.3 and can't upgrade or restore.
bnbliss said:
Thanks for reaching out with your suggestions. For now it looks like I'm stuck on 4.5.3 and can't upgrade or restore.
Click to expand...
Click to collapse
Given the device is rooted check to make sure the app overseeing OTA updates has not been renamed; see here for details.
Hey guys. I have a bone stock HDX 8.9 that is stuck on fastboot. I'm very familiar with Android and previously this meant that the OS was corrupted and needed reinstall. Does that sound right in this case?
If so, how do I reinstall the OS on this thing?
rudeguy said:
Hey guys. I have a bone stock HDX 8.9 that is stuck on fastboot. I'm very familiar with Android and previously this meant that the OS was corrupted and needed reinstall. Does that sound right in this case?
If so, how do I reinstall the OS on this thing?
Click to expand...
Click to collapse
You can't from fastboot as it has been crippled by Amazon (locked bootloader). Do you know the generation of HDX (3rd/4th) and what version of FireOS was installed? There are a few unbrick techniques but they only work with older models.
Davey126 said:
You can't from fastboot as it has been crippled by Amazon (locked bootloader). Do you know the generation of HDX (3rd/4th) and what version of FireOS was installed? There are a few unbrick techniques but they only work with older models.
Click to expand...
Click to collapse
Thanks for the reply.
I do not know which Gen or what OS was on it. I am doing this for a friend since I figured it would be similar to other android tabs where I just fire up Odin and call it good. I still think I could get it working if I could get the drivers to install but I'm not having any luck with any of the solutions so far.
Do these things have a stock recovery I can boot it into?
rudeguy said:
Thanks for the reply.
I do not know which Gen or what OS was on it. I am doing this for a friend since I figured it would be similar to other android tabs where I just fire up Odin and call it good. I still think I could get it working if I could get the drivers to install but I'm not having any luck with any of the solutions so far.
Do these things have a stock recovery I can boot it into?
Click to expand...
Click to collapse
You have much to learn about Amazon devices in general and HDX models in particular. They are not conventional and lack much of the standardization and recovery capability of other phones/tabs. Tools like Odin and FlashFire do not work on HDX devices. Likely perma-bricked it.
There is a crippled recovery environment (<power>+<vol+up>) but it won't do you any good as no sideload support and the hopeful looking 'factory reset' only wipes cache, dalvik and data; the system partition remains untouched. Can't flash or boot a custom recovery like twrp. Unless the bootloader is unlocked the device is an island without a functioning rom.
Welcome to Amazon.
Davey126 said:
You have much to learn about Amazon devices in general and HDX models in particular. They are not conventional and lack much of the standardization and recovery capability of other phones/tabs. Tools like Odin and FlashFire do not work on HDX devices. Likely perma-bricked it.
There is a crippled recovery environment (<power>+<vol+up>) but it won't do you any good as no sideload support and the hopeful looking 'factory reset' only wipes cache, dalvik and data; the system partition remains untouched. Can't flash or boot a custom recovery like twrp. Unless the bootloader is unlocked the device is an island without a functioning rom.
Welcome to Amazon.
Click to expand...
Click to collapse
Thanks again for the reply.
So should I not waste anymore time on this thing? Just call it junked?
rudeguy said:
Thanks again for the reply.
So should I not waste anymore time on this thing? Just call it junked?
Click to expand...
Click to collapse
There's an outside possibility the bootloader can be unlocked (key to everything) but it would be a difficult trek. Not knowing what was on it before is a killer as only certain devices can be unlocked, mostly early Gen 3s that were never updated to FireOS v4.
Just to add to the misery: fastboot cables don't work on HDX devices. Amazon should include a packet of K-Y with every purchase.