ADB for 3rd Gen Fire HDX - Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot

I'm a noob to the club here and to many things discussed on the forums. I have a 3rd Gen Fire HDX 13.4.5.2 that I bought for my soon to be wife. I feel horrible that she doesn't like it as is. My bad. ADB is up and running well on my laptop. I even managed to reboot the device using such commands but don't want to brick it. But I realize that I know just enough to be dangerous. I haven't seen any threads on fast boot commands by which I can boot into TWRP and command the device into a custom ROM with Super SU and Gapps. Ibut I am still ignorant as to which .zip files need to be loaded into the device and the cable doesn't appear necessary. I have seen a thread on how to do this but it appears to be on a 1st Gen device when things were much more simple. I would like for he to use it for more than a table coaster! I stopped while I was ahead! A factory fast boot cable may get me directly into Recovery know that this may seem to simple to you, the Developers from which I'm asking but it is a hurdle I can't leap myself. I managed this on my Android phone, however this seems at least, monumentally more challenging. If I'm incorrect that this is possible, by all means, tell me but please be kind, as I'm learning and tell me the best way to achieve the desired results and not stop at making me feel any more stupid than I am feeling. I'm counting on you. She won't marry me until I fix it. Save a marriage! LOL!!!

Sandman1210 said:
I'm a noob to the club here and to many things discussed on the forums. I have a 3rd Gen Fire HDX 13.4.5.2 that I bought for my soon to be wife. I feel horrible that she doesn't like it as is. My bad. ADB is up and running well on my laptop. I even managed to reboot the device using such commands but don't want to brick it. But I realize that I know just enough to be dangerous. I haven't seen any threads on fast boot commands by which I can boot into TWRP and command the device into a custom ROM with Super SU and Gapps. Ibut I am still ignorant as to which .zip files need to be loaded into the device and the cable doesn't appear necessary. I have seen a thread on how to do this but it appears to be on a 1st Gen device when things were much more simple. I would like for he to use it for more than a table coaster! I stopped while I was ahead! A factory fast boot cable may get me directly into Recovery know that this may seem to simple to you, the Developers from which I'm asking but it is a hurdle I can't leap myself. I managed this on my Android phone, however this seems at least, monumentally more challenging. If I'm incorrect that this is possible, by all means, tell me but please be kind, as I'm learning and tell me the best way to achieve the desired results and not stop at making me feel any more stupid than I am feeling. I'm counting on you. She won't marry me until I fix it. Save a marriage! LOL!!!
Click to expand...
Click to collapse
Your best option is to root, install Safestrap v4 and then replace FireOS with either Nexus v4 or CM-11. That will transform the device into something akin to a Nexus 7 which will probably be more appealing to the intended recipient.
You can not install TWRP or a custom ROM on this device without the help of Safestrap as the bootloader is locked with no ability to unlock. Nor do you want to commingle GAaps (Google Play Framework/Service/Store in particular) with FireOS as they don't play well together on v4. FireOS v5 is much more accommodating but that is not an option for 3rd gen devices.
Set aside thoughts of layering on components via ADB and recovering with a factory/fastboot cable if things go bad. HDXs are sensitive devices that are easy to brick and nearly impossible to recover. Factory cables are useless on this device as is the fastboot environment with a locked bootloader.
Hopefully you have stayed of WiFi to prevent an auto-upgrade to FireOS 4.5.5. Device must be on 4.5.2 to run Safestrap v4. Rolling back from 4.5.5 -> 4.5.2 is not straight forward and entails some risk if instructions are not followed.
Path forward:
- as mentioned stay off WiFi until OTA (over-the-air) updates are blocked
- root with Kingroot. You will need to enable WiFi for a brief period. Watch for OTAs when connected. Once rooted immediately reboot tablet to flush the partially downloaded update. If you have a fast internet connection you may want to root from location with pokey public WiFi such as a coffee shop or library. You don't want the full 4.5.5 update to download while you are rooting.
- sideload ES File Explorer via 'adb install' and use it to block OTA by renaming DeviceSoftwareOTA.apk in /system/priv-app/ to something benign. Once complete you can safely reenable WiFi.
- install Safestrap v4. Once Safestrap is installed NEVER perform a factory reset from the native device recovery menu; your device will brick.
- from Safestrap recovery (which looks a lot like twrp) backup your existing FireOS installation
- download and flash either Nexus v4 or CM11
There are several threads and hundreds of posts covering the details associated with each step. Unfortunately, no guides or how-to videos. Suggest reading through the Safestrap v4, CM11 and Nexus v4 threads to get started. You'll also find related posts in the HDX General and Q&A forums. Ask questions as your knowledge evolves. Have a plan, know the expected (and unexpected) outcomes of each action, never assume or guess. The answer to "what could it hurt" is "everything".
Good luck.

Related

[Q] Got a replacement Apollo

I just recieved a replacement Unit for my malfunktioning HDX 9.8. Current version on this thing is 14.3.0.2_user_302075320. I have just started it up to check the version and have not yet registered it or even connected it to a network. This time around I would like to be in control of things! What would be the appropriate thing to do with this version, if I want to :
1. Root it and keep it from auto-updating.
2. getting it safestrapped to be able to...
3. ...flash custom roms safely in the future,
Ive been looking around these forums to find out myself but information is scrambled and depending on version numbers and other things. The learning curve sure is steep here
/sebastian
My humble suggestion is to install TWRP (here) followed by the ROM of your choice. Each has pros/cons....stock is also an option. You will need to do some reading, plan carefully and be prepared for the unexpected. Keep that pup in 'airplane' mode to prevent debilitating OTA updates until you identify and apply an appropriate blocker. I think you will find the community quite willing to help with specific questions but you probably won't get a start-to-finish recipe. Lots of reading ahead but the rewards are worth it IMO. Good luck!
Thanks for the reply! Good to hear that airplane mode can be a temporary update blocker! I'll do some more reading up on TWRP to begin with then.
Device Manager said:
Thanks for the reply! Good to hear that airplane mode can be a temporary update blocker! I'll do some more reading up on TWRP to begin with then.
Click to expand...
Click to collapse
Be carefull and dont use airplane mode to block updates while in stock! At least one user reported that amazon can update your kindle even with airplane mode on! If you setup your wifi already, just turn-off / forget your wifi while in stock, or use OTA blocker ...
Forgetting all WiFi networks is good advise indeed! I have seen Kindle readers pop out of airplane mode on occasion; suppose the same could happen on Fire/HDX tablets although I have not personally experienced this. OTA blocker is great (what I use) but obviously requires root.
OK, thanks everyone!
I'm good so far! I first rooted with towelroot then went for the toolkit. Installed the ADB drivers, then SU, then OTA blocker. After that I Installed safestrap, made a backup and a new rom-slot, to which I restored the recovery. So now I should be OTA blocked and have a stock ROM recovery option. I hope I haven't made any terrible mistakes yet
I'm a happy camper! (as of yet
Now I will do som reading up on HDXposed and custom roms I guess. Does anyone have any suggestions? Is the Nexus rom a good option?
Thanks again!
Ok Iplayed around some and read up some more. Now I can definitely see the benefits of going for the custom recovery! I have a few remaining questions about the specifics about flashing TWRP that I cant seem to find the answer to. Hope somewone would be kind enough to help or point me in the right direction.
Do I need to uninstall safestrap before (or after) flashing TWRP?
Is "Copy image to SD-card root" the same as copying it to the device file system root? As in draging and dropping in windows perhaps?
What is the tool for issuing the commands mentioned in the TWRP install guide? (I have used ADB but only via the Toolkit aplication and I havent seen a command prompt for this around).
Sorry for lacking in some fundamentals on this... (being a noob on android stuff)
Never mind the above. All sorted. Up and running HDX Nexus 2.0.5. Great stuff!

[Q] I think I've got it? (from root to rom)

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.

Safest way to root KFHDX 7" 2013 (thor)?

I do not want to brick this device. Could someone give/list me steps that would root it using the 'safest' (aka hardest to mess up), install TWRP, and maybe then install a good ROM (CM13?)
Also, fire os 4.5.5
ADB works.
GameExpertNetwork said:
I do not want to brick this device. Could someone give/list me steps that would root it using the 'safest' (aka hardest to mess up), install TWRP, and maybe then install a good ROM (CM13?)
Also, fire os 4.5.5
ADB works.
Click to expand...
Click to collapse
Starting from 4.5.5 you can not install 'native' twrp or unlock the bootloader. Nor is their any path to allow this due due anti-rollback protections. Your safest path (which still holds risks) is to rollback to 3.2.8, upgrade to 4.5.2, root, install Safestrap v4 followed by one of two kitkat based roms: Nexus v4 or CM11. At present you can not install CM12 (lollipop) or CM13 (marshmallow) under Safestrap v4.
There are many posts detailing the above process; a few recent ones can be found here, here and here. Scroll through the entire thread for other examples along with a diary of user experiences.
Key points:
- be sure to keep wifi off (airplane/flight mode engaged) while passing through 3.2.8 and 4.5.2 until OTA is block. Receiving an update on 3.2.8 will brick your device. The consequences on 4.5.2 are less severe but still unpleasant.
- suggest downloading everything you need to your device in advance; put each component into a separate folder to be extracted/renamed as needed
- read, read and read some more before attempting anything. Ask questions as needed; never guess or assume. Make sure you know the expected outcome, potential consequences and fallback options for each step before executing
- Kindles in general and HDX models in particular are unforgiving relative to other devices. Tough to mod, easy to brick, nearly impossible to recover. If not 100% confident in your abilities enjoy your device as is (or be mentally prepared to toss it in the trash).
Davey126 said:
Starting from 4.5.5 you can not install 'native' twrp or unlock the bootloader. Nor is their any path to allow this due due anti-rollback protections. Your safest path (which still holds risks) is to rollback to 3.2.8, upgrade to 4.5.2, root, install Safestrap v4 followed by one of two kitkat based roms: Nexus v4 or CM11. At present you can not install CM12 (lollipop) or CM13 (marshmallow) under Safestrap v4.
There are many posts detailing the above process; a few recent ones can be found here, here and here. Scroll through the entire thread for other examples along with a diary of user experiences.
Key points:
- be sure to keep wifi off (airplane/flight mode engaged) while passing through 3.2.8 and 4.5.2 until OTA is block. Receiving an update on 3.2.8 will brick your device. The consequences on 4.5.2 are less severe but still unpleasant.
- suggest downloading everything you need to your device in advance; put each component into a separate folder to be extracted/renamed as needed
- read, read and read some more before attempting anything. Ask questions as needed; never guess or assume. Make sure you know the expected outcome, potential consequences and fallback options for each step before executing
- Kindles in general and HDX models in particular are unforgiving relative to other devices. Tough to mod, easy to brick, nearly impossible to recover. If not 100% confident in your abilities enjoy your device as is (or be mentally prepared to toss it in the trash).
Click to expand...
Click to collapse
So, from my assumptions, there are 2 major ways to mess up
1. OTA update.
2. Low battery
And IF I ever do this, I will click the 'forget' button on the wifi network AND set it into airplane mode, and also have it fully charged overnight and STILL plugged in,
What are some other risks that I can try to "eliminate"
GameExpertNetwork said:
So, from my assumptions, there are 2 major ways to mess up
1. OTA update.
2. Low battery
And IF I ever do this, I will click the 'forget' button on the wifi network AND set it into airplane mode, and also have it fully charged overnight and STILL plugged in,
What are some other risks that I can try to "eliminate"
Click to expand...
Click to collapse
There are risks throughout the process - a comprehensive detailing would never be complete. Your best defense is carefully reading instructions, understanding what is suppose to happen at each step (expected outcomes) and avoiding 'gotchas' which are well documented. Most disasters are the result of poor preparation, impatience and experimentation. Like anything else the work is relatively easy with manageable risk if do your homework. Keep reading until comfortable.
Add to your list:
- using files obtained from sources other than listed in the relevant threads (eg: stock 3.2.8 vs rollback file)
- performing a native factory reset (from the stock recovery menu) unless recommended by an experienced contributor
- performing a native factory reset after Safestrap v4 is installed (instant brick)
- activating/using secondary slots in Safestrap v4 and then attempting to swap backup images between slots
- flashing unsupported roms in Safestrap v4 (CM12/CM13, stock FireOS, etc)
- manually twiddling file permissions or messing with build.prop after obtaining root (there's an app for that if needed)
Davey126 said:
There are risks throughout the process - a comprehensive detailing would never be complete. Your best defense is carefully reading instructions, understanding what is suppose to happen at each step (expected outcomes) and avoiding 'gotchas' which are well documented. Most disasters are the result of poor preparation, impatience and experimentation. Like anything else the work is relatively easy with manageable risk if do your homework. Keep reading until comfortable.
Add to your list:
- using files obtained from sources other than listed in the relevant threads (eg: stock 3.2.8 vs rollback file)
- performing a native factory reset (from the stock recovery menu) unless recommended by an experienced contributor
- performing a native factory reset after Safestrap v4 is installed (instant brick)
- activating/using secondary slots in Safestrap v4 and then attempting to swap backup images between slots
- flashing unsupported roms in Safestrap v4 (CM12/CM13, stock FireOS, etc)
- manually twiddling file permissions or messing with build.prop after obtaining root (there's an app for that if needed)
Click to expand...
Click to collapse
I bricked a nextbook tablet with that last way (build.prop messing)
Will factory resetting from a custom ROM brick my device?
And don't worry, I won't be flashing stock fire OS.
Also, sorry if i'm asking too much, but since I don't see a place where the info is all together in one thread and not links to many others, could you either link me to a step-by-step tutorial or list them out yourself? Thank you
GameExpertNetwork said:
I bricked a nextbook tablet with that last way (build.prop messing)
Will factory resetting from a custom ROM brick my device?
And don't worry, I won't be flashing stock fire OS.
Also, sorry if i'm asking too much, but since I don't see a place where the info is all together in one thread and not links to many others, could you either link me to a step-by-step tutorial or list them out yourself? Thank you
Click to expand...
Click to collapse
As previously mentioned never do a factory reset from the native Kindle Fire recovery menu with Safestrap v4 installed. It will destroy the Safestrap environment and everything running within it regardless of rom.
Post #3 contains several links that should prove helpful. You'll need to do some reading.

Removing FireOS 5.1.2 and replacing with stock Lollipop?

Hi there,
I've been cruising these forums for a while and have managed to root my device, get adb setup, and TWRP installed. An unfortunate bit seems to be that you cannot leave TWRP installed and actually boot the device. I managed to get stuck in a boot loop having not restored the 5.4.1 bootloaders. I turned the device off and rebooted into TWRP, flashed the 5.4.1 bootloaders, rebooted, and I'm golden. However, this doesn't really get me anywhere.
So my goal here is to just wipe all this FireOS crap and turn this tablet into a normal android tablet. I've seen plenty of posts about it but cannot seem to find any single post that would achieve this for my specific device and software version. So I'm coming here for help.
Mostly, what I have done so far has come from this thread: http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950
Unfortunately, from what I can tell, this process does not remove FireOS and replace it with stock Lollipop, it just updates you to 5.1.2 (which I'm already at) and installs GAPPS. It does not really have a "pure" Android install and it somehow retains the FireOS as the primary OS.
Now, please correct me if I am wrong here with any of the above (this is not a hobby of mine) but since I've rooted a few devices before I figured I could handle it. It seemed like a bargain getting this Fire HD 7 used for like $64... if only I can get it onto stock Android. I'm basically trying to make it a Nexus 7.
Since I CAN get into TWRP, I figure I should just be able to flash a custom ROM right? I've just been having a really hard time finding a stock Lollipop ROM specifically for my device. From what I've heard, flashing the new ROM is the most error-prone part of this type of stuff and can totally brick the device if it were not meant for it. If that did happen, I would need to be able to boot the device back up, get an adb connection, run the scripts that flash the correct bootloaders (post #2, section 101, from the link above) so I can reboot into TWRP and fix it. Perhaps understandably so, I've been very hesitant to just go trying things willy-nilly that I don't fully understand.
Could anyone offer any assistance? Perhaps just point me in the right direction? I've probably read most of the threads you'll likely link, so a short bit of context to how something pertains to my specific device as well as the link could help me significantly. The guides that people write usually contain updates and are quite difficult to follow to the "T" and half the time I'm not even sure something I'm doing actually pertains to my device.
[EDIT] I found this video (https://www.youtube.com/watch?v=_c5hHSCO_o8) but it looks like he's doing that on a previous generation Fire so, again, I'm not sure it will work and don't want to try and then brick it.
nedwards said:
Hi there,
I've been cruising these forums for a while and have managed to root my device, get adb setup, and TWRP installed. An unfortunate bit seems to be that you cannot leave TWRP installed and actually boot the device. I managed to get stuck in a boot loop having not restored the 5.4.1 bootloaders. I turned the device off and rebooted into TWRP, flashed the 5.4.1 bootloaders, rebooted, and I'm golden. However, this doesn't really get me anywhere.
So my goal here is to just wipe all this FireOS crap and turn this tablet into a normal android tablet. I've seen plenty of posts about it but cannot seem to find any single post that would achieve this for my specific device and software version. So I'm coming here for help.
Mostly, what I have done so far has come from this thread: http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950
Unfortunately, from what I can tell, this process does not remove FireOS and replace it with stock Lollipop, it just updates you to 5.1.2 (which I'm already at) and installs GAPPS. It does not really have a "pure" Android install and it somehow retains the FireOS as the primary OS.
Now, please correct me if I am wrong here with any of the above (this is not a hobby of mine) but since I've rooted a few devices before I figured I could handle it. It seemed like a bargain getting this Fire HD 7 used for like $64... if only I can get it onto stock Android. I'm basically trying to make it a Nexus 7.
Since I CAN get into TWRP, I figure I should just be able to flash a custom ROM right? I've just been having a really hard time finding a stock Lollipop ROM specifically for my device. From what I've heard, flashing the new ROM is the most error-prone part of this type of stuff and can totally brick the device if it were not meant for it. If that did happen, I would need to be able to boot the device back up, get an adb connection, run the scripts that flash the correct bootloaders (post #2, section 101, from the link above) so I can reboot into TWRP and fix it. Perhaps understandably so, I've been very hesitant to just go trying things willy-nilly that I don't fully understand.
Could anyone offer any assistance? Perhaps just point me in the right direction? I've probably read most of the threads you'll likely link, so a short bit of context to how something pertains to my specific device as well as the link could help me significantly. The guides that people write usually contain updates and are quite difficult to follow to the "T" and half the time I'm not even sure something I'm doing actually pertains to my device.
[EDIT] I found this video (https://www.youtube.com/watch?v=_c5hHSCO_o8) but it looks like he's doing that on a previous generation Fire so, again, I'm not sure it will work and don't want to try and then brick it.
Click to expand...
Click to collapse
You seem to have the gist of it, which is that what you want to do can't be done. There is only one ROM for this device--CM11, here: http://forum.xda-developers.com/fire-hd/orig-development/rom-cm-11-kindle-hd6-t3270138 --and it is not fully working. No one's ever posted here about successfully installing a ROM for a different device, only about bricks as a result of trying.
@xSentinel has been disabling all possible apps, while still keeping the device running. His goal may be the same as yours(?). He started a thread here, but has since got a lot more disabled: http://forum.xda-developers.com/fire-hd/help/5-1-2-bloatware-safe-to-remove-apps-2014-t3355167. Might want to post there and see what he's up to.
DoLooper said:
You seem to have the gist of it, which is that what you want to do can't be done. There is only one ROM for this device--CM11, here: http://forum.xda-developers.com/fire-hd/orig-development/rom-cm-11-kindle-hd6-t3270138 --and it is not fully working. No one's ever posted here about successfully installing a ROM for a different device, only about bricks as a result of trying.
@xSentinel has been disabling all possible apps, while still keeping the device running. His goal may be the same as yours(?). He started a thread here, but has since got a lot more disabled: http://forum.xda-developers.com/fire-hd/help/5-1-2-bloatware-safe-to-remove-apps-2014-t3355167. Might want to post there and see what he's up to.
Click to expand...
Click to collapse
Ah, that is unfortunate. At least you've helped me to understand that my goal cannot be fully realized. I probably should have done a bit more research before purchasing the Fire tablet. I'm really just looking to set up an in-car tablet to handle Torque guages, navigation, and music. Perhaps I should just return the Kindle and shell out the extra cash for a Nexus 7. I think I could probably get a refurbished one for a price similar to what I paid for the Fire. I'll poke around xSentinel's thread a bit and see what I'm up against first though. If it comes down to it, the headache of dealing with Amazon's locked down devices might just outweigh the extra money/hassle of a Nexus 7 and a return.
nedwards said:
Ah, that is unfortunate. At least you've helped me to understand that my goal cannot be fully realized. I probably should have done a bit more research before purchasing the Fire tablet. I'm really just looking to set up an in-car tablet to handle Torque guages, navigation, and music. Perhaps I should just return the Kindle and shell out the extra cash for a Nexus 7. I think I could probably get a refurbished one for a price similar to what I paid for the Fire. I'll poke around xSentinel's thread a bit and see what I'm up against first though. If it comes down to it, the headache of dealing with Amazon's locked down devices might just outweigh the extra money/hassle of a Nexus 7 and a return.
Click to expand...
Click to collapse
You also might check out the Fire forums. (I got a refurb for $30.) They have a few ROMs and are doing interesting things. Also, lots of activity over there.
Some people may strive to be "purists", but remaining pragmatic is a recipe for relatively happy life
Because the bootloaders are locked, there are very limited options on what to boot. There was some lucky bug in the earlier bootloaders that gifted us with the ability to boot an unsigned TWRP using 4.5.3 bootloaders. But boot.img always had to be signed, or it would not boot.
To create a custom OS, one needs to match the custom ROM to the existing boot.img from a given version of FireOS. Kind of pain in the @ss, don't you agree ?
Instead, however, one can just keep FireOS 5, and tweak it to behave like almost a pure Android. And it's not hard ! So why chase the unicorns when all you want is right in front of you !
I'm currently working on completing a CM11 port - as someone else mentioned it needs to use the stock boot.img though, so I have to heavily modify CM code in order to get it to work with full functionality. CM11 does run very well on the device though, and it's much snappier than Fire OS imo.
In theory this device could use something like safestrap to boot unsigned boot images, however I probably won't bother writing something like that until I have CM11 at 100% functionality (currently my build is at about 60% if I were to estimate).
I think the guy who posted the first CM11 port is now working on porting CM12, although it's a massive pain to test.
nedwards said:
Ah, that is unfortunate. At least you've helped me to understand that my goal cannot be fully realized. I probably should have done a bit more research before purchasing the Fire tablet. I'm really just looking to set up an in-car tablet to handle Torque guages, navigation, and music. Perhaps I should just return the Kindle and shell out the extra cash for a Nexus 7. I think I could probably get a refurbished one for a price similar to what I paid for the Fire. I'll poke around xSentinel's thread a bit and see what I'm up against first though. If it comes down to it, the headache of dealing with Amazon's locked down devices might just outweigh the extra money/hassle of a Nexus 7 and a return.
Click to expand...
Click to collapse
Just so you know it can be done, I am running Torque on a Fire HD 6 and still running thr Fire O.S. There is also a similar app to Torque Pro in the Amazon app store - search for OBD and it should see it (sorry I can't give the name, soft bricked the device and won't be near a computer for another 4 days) It is similar in capabilities to Torque Pro, and runs around the same price.

Clarification

Warning: Potentially long post ahead with mini-intro/rant
Hi XDA! I'm a noob new user/newbie when it comes to rooting. I have some (little) experience with jailbreaking my iPhone previously (It turned out very well), when the guy I paid to do so practically bricked my old one (SHEESH, you can't count on other people to do these things, better do them yourself) but have not tackled rooting Android devices yet.
I have a 3rd gen Kindle Fire HDX 7" (Thor).
Don't get me wrong, I love my Kindle. It's been an awesome pal for the past two years, aside from the loose charging port, the lack of interesting stuff on the Amazon appstore, and the inability to change or customize YOUR device, I decided it was time to "get my feet wet". I've been coming back to these forums over the past few months, in hopes of finding a root for 4.5.5.2 but I'd always chicken out in fear of bricking it. Eventually, I learned that to root, I need to rollback to a certain firmware.
OKAY, so I've done a little reading here and there in the past two hours (or more) and have gathered the following information so far (if there's something worth clarifying or expounding, please do!):
Point 1: The steps are, in order: Rollback to 3.2.8, upgrade to 4.5.2, root, block OTA, install Safestrap v4, and (optional) flash custom ROM.
My options are CM11 and Nexus 4 as of the moment (from what I've seen on these forums, but CM11 has been discontinued[????] and there's a newer version of HDX Nexus ROM v4 called Fire Nexus ROM somewhere if I'm not mistaken)
Question: Which do you suggest? CM11 or Nexus 4? What are the pros and cons of each?
Point 2: I understand that I need to download everything in advance and store them in a unique folder so that it'd be easier for me later on.
Question: Do you recommend that I factory reset my Kindle before anything else and THEN download everything I need in preparation? Won't these downloads be deleted/removed if I rollback my device to 3.2.8? I'm planning on creating a backup of these files on my PC in case something goes wrong or missing.
Point 3: I saw something that said
It was only tested with 14.4.5.2, but should also work with 13.4.5.2.
Click to expand...
Click to collapse
Question: What's the difference between 14.4.5.2 and 13.4.5.2? I haven't dug deep enough in the forums to know if there's an answer to the question, but I made this thread to clear up everything I'm unsure of.
Point 4: Before anything, I know I've got to understand the basics of ADB before even attempting any of this (like commands and such). In one of the threads, I saw this:
"Install minimal adb + fastboot......"
Click to expand...
Click to collapse
Question: What's the difference between minimal adb versus the whole package/thing? Shouldn't it be better to just download or install the full thing (no matter how big the file/program/application is)? What are the pros and cons?
YES, I know I have to understand what USB debug means and/or how to enable it. (I bookmarked an article for further reading soon, but already have enabled the setting within my device).
Other things I've gathered so far:
-Always have a copy of ES File Explorer along with other important files.
Never perform a factory reset unless specifically advised to do so by someone experienced with HDX devices....
Click to expand...
Click to collapse
-Use a Windows PC/laptop. I'm using a mac, which is basically useless for games and the like not ideal when rooting. (Tiny question. Do I really need to install Linux/Ubuntu even if I can use someone's Windows PC/lappy to root?
-To root successfully, I've got to enable mock locations from developer options (already did).
-Before installing/flashing custom ROMS, I need to make a backup of the stock ROM.
CONCERNS:
Known issues regarding safestrap include secondary slots which boot but the WiFi module doesn't load (Which means I have to flash Nexus v4 to the STOCK SLOT for now [?????] is there any workaround for this? Because from what I've read so far, tampering with the stock is a big NO-NO unless you know what you're doing or in this case, "...unless I know what I'm doing.".) Or at least any reassurance? A safe, fool-proof way of doing this without at least bricking my device (likely)?
That's all I've got so far. I've compiled everything the basic things I need to know in a notepad, from steps and instructions, to tuts and download links.
Apologies for my english, this is not my native language
Thanks to whoever can answer some of my questions! Cheers and good day :laugh:
Don't even think about using safestrap, it might as well be a death trap if u brick ur device ur screwed. The best thing u could do is downgrade to 3.2.8 https://forum.xda-developers.com/kindle-fire-hdx/general/rollback-13-3-2-8-rollback-ota-captured-t3046204 unlock your bootloader https://forum.xda-developers.com/kindle-fire-hdx/general/thor-unlocking-bootloader-firmware-t3463982 (maybe get a tech savvy friend to help u with that one) it looks hard but it's actually very simple the way he explains it makes it more difficult than it really is. And if you want a stable rom with good user customization I'd get cm11. Also u don't really have to upgrade to 4.5.2 everything works great starting out from 3.2.8
CocoBun said:
Don't even think about using safestrap, it might as well be a death trap if u brick ur device ur screwed. The best thing u could do is downgrade to 3.2.8 https://forum.xda-developers.com/ki...lback-13-3-2-8-rollback-ota-captured-t3046204 unlock your bootloader https://forum.xda-developers.com/kindle-fire-hdx/general/thor-unlocking-bootloader-firmware-t3463982 (maybe get a tech savvy friend to help u with that one) it looks hard but it's actually very simple the way he explains it makes it more difficult than it really is. And if you want a stable rom with good user customization I'd get cm11. Also u don't really have to upgrade to 4.5.2 everything works great starting out from 3.2.8
Click to expand...
Click to collapse
Agreed. Be sure to stay off the network while on 3.2.8; if the device takes an OTA update it WILL brick with no possible recovey. Use TowelRoot to root; quick/reliable on FireOS v3. No need to update to 4.5.2; doing so adds risk/complexity with no corresponding benefit.
KingOroot PC edition (yes KingORoot not Kingroot) will root 4.5.5.2 in less than a minute, used it very recently having previously rooted 4.5.5.1 with Kingroot. In both case unlock the bootloader flashed twrp and put nexus ROM on without issue
Mr McBoatface said:
KingOroot PC edition (yes KingORoot not Kingroot) will root 4.5.5.2 in less than a minute, used it very recently having previously rooted 4.5.5.1 with Kingroot. In both case unlock the bootloader flashed twrp and put nexus ROM on without issue
Click to expand...
Click to collapse
Yes, kingOroot was previously identified as a potential root solution for 4.5.5.2. Sometimes it works...other times not. Kinda like KingRoot on the 5th gen Fire. When it fails the leftovers can be onerous to deal with on unrooted device. If root is secured I recommend immediately unlocking the bootloader following by a comprehensive wipe before flashing a custom ROM. KingOroot does not enjoy a stellar reputation.

Categories

Resources