Hey, new to the forums and not very familiar with anything related to rooting, ROMs, or anything like that on these devices. I'm here because I'm pretty much stuck in a situation where if I don't update my Kindle OS the only app I use will become unusable (this kindle uses Fire OS 4.5.5.2 or Android KitKat 4.4 according to wikipedia)- the app I use will soon require Android 5.0 or higher- I'm already getting warning messages and I can't manually download the new versions of the app without errors. The exact model of my Kindle is HDX 8.9 (3rd gen) 4.5.5.2 OS, everything works fine.
I looked at some previous posts and saw some outdated information or info for people that already knew what they were doing. I got scared because I hear some people bricked their devices trying these things. So my question is, as a noob, should I attempt to install a new Android ROM or is it more advisable for me to just sell the tablet(s) and get something newer? Also, I'd like to add, I have 3 of these tablets for my business so this decision would apply 3x over.
MadixV said:
Hey, new to the forums and not very familiar with anything related to rooting, ROMs, or anything like that on these devices. I'm here because I'm pretty much stuck in a situation where if I don't update my Kindle OS the only app I use will become unusable (this kindle uses Fire OS 4.5.5.2 or Android KitKat 4.4 according to wikipedia)- the app I use will soon require Android 5.0 or higher- I'm already getting warning messages and I can't manually download the new versions of the app without errors. The exact model of my Kindle is HDX 8.9 (3rd gen) 4.5.5.2 OS, everything works fine.
I looked at some previous posts and saw some outdated information or info for people that already knew what they were doing. I got scared because I hear some people bricked their devices trying these things. So my question is, as a noob, should I attempt to install a new Android ROM or is it more advisable for me to just sell the tablet(s) and get something newer? Also, I'd like to add, I have 3 of these tablets for my business so this decision would apply 3x over.
Click to expand...
Click to collapse
Changing ROMs is the easy part. Preparing your device (specifically temperamental HDXs) to accept a custom ROM (rooting; unlocking the bootloader; dealing w/fastboot; etc) is not for the faint of heart. Suggest identifying someone in your business who has some experience tethering Android devices and/or rooting. With that advantage updating your portfillo should be fairly easy. Otherwise I would look for something else.
Related
I recently bought a Kindle Fire HDX 7" and have had it about a week now. With all the Amazon Bloat and lack of Google apps I need more out of it. I am not a beginner with flashing roms and such, my HTC One is Rooted, CyanogenModed, and has a boot loader, anyways...
I have spent the last couple days reading up on the ways to do it on the HDX 7 and heard many warnings and bricks of this device, but some of the posts are a little bit older. I can't really tell which method of Rooting/Flashing is the safest out of all the different ones. My current OS version is 13.3.2.1. Using the Safestrap looks pretty easy and from what I understand is that even if you do brick it you can recover the original?
My question is... Is it any safer to flash a Rom lately (due to the updating problems?), and how safe is just rooting it for the time being? Also, what method/tools would you suggest to use? I don't like the FireOS and would like to get it close the a standard Android and/or CyanogenMod.
Thanks for your time. Edit: unintentional double post.
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
Playing around with my kindle Fire hd X 7 (NOT HD7!!) I managed to brick the device, but got a replacement from Amazon in no time. So I will be more cautious in the future. What did I do? Kingrooted the device in no time and without any problems (FireOS 4.5.5.1), threw away some Amazon "trash" and then decided to go for a factory reset. No ADB, no developers options activated, no backup. Well - my fault, I admit.
After looking for quite a while into these forums and trying out couple of "non root" Google Play installation routines (they all did not work, although the apk's were installed properly) I am under the impression that I either must roll back to some previous OS version, then root and after that upgrade to Android 5.x or even 6.x - steps that in view of my experiences I do not fully appreciate. Especially not since I am in doubt about a fully compatible backup of the device: Amazon likely will not get me yet another refurbished HDX7...
I could do with 4.5.5.1 (as of today (Mar 4, 2016) still some Amazon people claim that there will be an update of the OS) but the lack of Google Playstore access is increasingly hard to tolerate, since some apps do not work properly under 4.5.5.1 and others need quite some care (like substitution of the carousel icons) and this after each sideload.
This said, I wonder whether
1) just (king)rooting the device but NOT disabling OTA upgrades will brick the device if Amazon at some point gets us FireOS 5 also for the HDX7 and the upgrade is automatically downloaded/installed
2) rooting the device plus installation of the respective apk's will render the HDX7 FULLY compatible with Google Play, i.e. even allow for installation of PAID apps I am running on my other Android devices?
Thanks a lot for helpful hints.
PS: The HDX 7 is a nice device, both with respect to size and with respect to hardware. I can't understand why Amazon kind of dropped it...
gefluegelt said:
Playing around with my kindle Fire hd X 7 (NOT HD7!!) I managed to brick the device, but got a replacement from Amazon in no time. So I will be more cautious in the future. What did I do? Kingrooted the device in no time and without any problems (FireOS 4.5.5.1), threw away some Amazon "trash" and then decided to go for a factory reset. No ADB, no developers options activated, no backup. Well - my fault, I admit.
After looking for quite a while into these forums and trying out couple of "non root" Google Play installation routines (they all did not work, although the apk's were installed properly) I am under the impression that I either must roll back to some previous OS version, then root and after that upgrade to Android 5.x or even 6.x - steps that in view of my experiences I do not fully appreciate. Especially not since I am in doubt about a fully compatible backup of the device: Amazon likely will not get me yet another refurbished HDX7...
I could do with 4.5.5.1 (as of today (Mar 4, 2016) still some Amazon people claim that there will be an update of the OS) but the lack of Google Playstore access is increasingly hard to tolerate, since some apps do not work properly under 4.5.5.1 and others need quite some care (like substitution of the carousel icons) and this after each sideload.
This said, I wonder whether
1) just (king)rooting the device but NOT disabling OTA upgrades will brick the device if Amazon at some point gets us FireOS 5 also for the HDX7 and the upgrade is automatically downloaded/installed
2) rooting the device plus installation of the respective apk's will render the HDX7 FULLY compatible with Google Play, i.e. even allow for installation of PAID apps I am running on my other Android devices?
Thanks a lot for helpful hints.
PS: The HDX 7 is a nice device, both with respect to size and with respect to hardware. I can't understand why Amazon kind of dropped it...
Click to expand...
Click to collapse
FireOS v4 and Google Play Service/Store do not play nice together. You best option is to install Safestrap v4 (a psudo recovery environment) and then replace FireOS with either CM-11 or Nexus v4. Both are KitKat (Android 4.4) based roms that fully support Google Play services. At present there is NO path to upgrade to Lollipop (Android 5.x) or Marshmallow (Android 6.x) due to compatibility issues with software components that can not be upgraded on a locked device (your device can not be unlocked).
Give it some thought. You will be giving up FireOS but gaining a far more capable/compatible tablet.
HDX7/KitKat
Davey126 said:
FireOS v4 and Google Play Service/Store do not play nice together. You best option is to install Safestrap v4 (a psudo recovery environment) and then replace FireOS with either CM-11 or Nexus v4. Both are KitKat (Android 4.4) based roms that fully support Google Play services. At present there is NO path to upgrade to Lollipop (Android 5.x) or Marshmallow (Android 6.x) due to compatibility issues with software components that can not be upgraded on a locked device (your device can not be unlocked).
Give it some thought. You will be giving up FireOS but gaining a far more capable/compatible tablet.
Click to expand...
Click to collapse
Hi Davey,
Thanks for your suggestions/clarifications. I will give it a thought, that's for sure. I was not aware of the "locked/unlocked" issue. Interesting! From your reply I assume that Safestrap v4 will get me a usable backup of FireOS 4.5.5.1 just in case things go wrong. Or do I still have to roll back to an earlier FireOS version? I faintly remember some posts about dark territory with kingrooted 4.5.5.1 and Safestrap.
gefluegelt said:
Hi Davey,
Thanks for your suggestions/clarifications. I will give it a thought, that's for sure. I was not aware of the "locked/unlocked" issue. Interesting! From your reply I assume that Safestrap v4 will get me a usable backup of FireOS 4.5.5.1 just in case things go wrong. Or do I still have to roll back to an earlier FireOS version? I faintly remember some posts about dark territory with kingrooted 4.5.5.1 and Safestrap.
Click to expand...
Click to collapse
Thankfully the days of rolling back FireOS along with the associated work effort/risks are over! Safestrap v4 is fully compatible with FireOS 4.5.5.1. There are paths back to FireOS should you wish to return. My guess is you won't given Amazon has no plans to update FireOS on 3rd gen devices. If you want full Play Store compatibility Safestrap + CM11/Nexus is the only option.
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.
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.