Related
Hi
Newbie here. We bought a kindle which turnout to be blacklisted so we can't register it. Obviously it is useless as we can only use internet.
My kindle was running on latest firmware which meant I couldn't root it. Thanks to one of you xda geniuses. I was able to rollback to firmware 13.3.2.8
I change oat filed to avoid upgrades. I installed es explorer.
I then rooted my kindle and did root checked which confirms it is rooted on Kfthwi android 4.2.2
I installed su super user. Seems to work fine
After that I tried to install boot loader fireflash but it keeps stopping
I finally managed to install and launch Rashr but when I boot recovery with twrp or any other files my kindle boots and stops saying can't boot and offers me to do factory reset or starts again as if nothing happened. I haven't chosen factory reset as I don't think this will help.
I have added su super users to system hoping this would help but no success.
I have also tried loads of kfu from pc but although adb is ok it says boot status unknown and fails every time as if it can't find the path or something...
I have ran out of ideas. I don't know what to do anymore
My aim is to install cm12 or other versions... anything to make this kindle become android
Please help me!
Thanks
worldita said:
Hi
Newbie here. We bought a kindle which turnout to be blacklisted so we can't register it. Obviously it is useless as we can only use internet.
My kindle was running on latest firmware which meant I couldn't root it. Thanks to one of you xda geniuses. I was able to rollback to firmware 13.3.2.8
I change oat filed to avoid upgrades. I installed es explorer.
I then rooted my kindle and did root checked which confirms it is rooted on Kfthwi android 4.2.2
I installed su super user. Seems to work fine
After that I tried to install boot loader fireflash but it keeps stopping
I finally managed to install and launch Rashr but when I boot recovery with twrp or any other files my kindle boots and stops saying can't boot and offers me to do factory reset or starts again as if nothing happened. I haven't chosen factory reset as I don't think this will help.
I have added su super users to system hoping this would help but no success.
I have also tried loads of kfu from pc but although adb is ok it says boot status unknown and fails every time as if it can't find the path or something...
I have ran out of ideas. I don't know what to do anymore
My aim is to install cm12 or other versions... anything to make this kindle become android
Please help me!
Thanks
Click to expand...
Click to collapse
Sorry - will not provide assistance for a blacklisted device. Read the forums.
Davey126 said:
Sorry - will not provide assistance for a blacklisted device. Read the forums.
Click to expand...
Click to collapse
Hi I am sorry I misunderstood the terms. It is NOT blacklisted. It is unregistered.
We have called Amazon and it does not belong to anyone. We don't know how it happened we bought it second hand. The tablet is not letting registered but it is not blacklisted. Can you still help ?
You can NOT unlock the bootloader, use TWRP and CM12 anyway. You'd need 3.2.3.2 or lower for that, and you can NOT downgrade below 3.2.8.
Ok thanks for replying to me and for the info. So no more hope? I should just bin it?
So sad.... was supposed to be for my kids.
I guess this shows you really can't buy these tablets second hand!
Thanks again for your time.
worldita said:
Ok thanks for replying to me and for the info. So no more hope? I should just bin it?
So sad.... was supposed to be for my kids.
I guess this shows you really can't buy these tablets second hand!
Thanks again for your time.
Click to expand...
Click to collapse
You likely toasted the device by installing stuff that is not valid for a HDX.
Wow Davey126 thank you so much for all your positive feedback.
So helpful
worldita said:
Wow Davey126 thank you so much for all your positive feedback.
So helpful
Click to expand...
Click to collapse
Sorry for the prickly response. Reacting to: 1) device that will not register which is a bright red flag waving; and 2) installing fireflash which is for a different model and likely destroyed your device. You can not install twrp on a HDX that has been upgraded past 3.2.6 and you can not rollback to any version below 3.2.8 from any version above 3.2.6. A little reading would have quickly revealed the sensitivity of HDX models to 'hacks' other than the limited suite described in the forums. Your device joins countless others in the tower of bricks created by owners failing to research proper procedures.
Hi all.
Just brought my Mrs a Amazon fire hdx 7, from eBay never been used or opened box.
The rom info is saying i have 13.3.0.5
I would like some help on unlock the bootloader so I can custom rom it for her, but also wondering if there was a way of running Amazon fire OS just in case she would prefer that is.
I'm not sure how I can unlock the bootloader, read info but getting confused on where to even start.
Any help please.
Much appreciated, thank you.
Ok, if you don't know what you're doing, ask first, i.e. before you brick you HDX!
If you haven't done it yet get HDX Toolkit to root and disable OTA updates.
Afterwards you should install TWRP, and update the bootloader to 3.2.3.2 via TWRP.
Then try the one click solution to unlock the bootloader. Could require these drivers, you probably will need if the one-click solution doesn't work for you, and we've to do it the hard way (i.e. manually).
Before you flash any custom ROM be sure to create a backup of your current Fire OS, and move it to your PC!
Thanks for the advise I'll have a butchers at it after I finish work. Fingers cross I can do it.
Thanks again.
@Cl4ncy
thank you so much for your advice, i have managed to unlock root and flash cm13. Mrs will be well pleased managed to a 7inch tab way faster then current sammy tab4 7
again thanks to all the devs and support xda has to offer and make this possible for us little ppl in the community.
You're welcome. Enjoy the 'free' HDX.
I got a new Motherboard and daughterboard in my HDX Apollo. I was able to get TWRP on it, but it keeps saying i dont appear to have root. I tried installing the latest supersu but it apparently didnt work. Anyway, i have realized that i just keep getting myself into trouble playing with root. All i want is to get my 3rd gen back to 4.5.5.1 fire os and wait for the fire os 5 update for it(hopefully) Any help on how i can do that? Ive tried downloading the latest Kindle update for apollo, renaming the .bin to update.zip and transferring it over and installing it but it never boots further than the 'kindle' screen.
Thanks for your help, sorry to be a pain
If you're on Fire OS 4.x you don't have TWRP, but Safestrap v4. After what you've done, do you still have access to Safestrap? Installing an amazon update with Safestrap installed, or even just rooted could easily mess up the device, i.e. brick it.
I don't think it's fire os 4x then. It does boot into the twrp interface and is fully functional but when you go to reboot into a different recovery it says something like "it appears you do not have root. Would you like to install supersu?" Even if I say yes it acts like it installs but apparently doesn't. I can post pics later
Sent from my SM-G920V using XDA-Developers mobile app
Cl4ncy said:
If you're on Fire OS 4.x you don't have TWRP, but Safestrap v4. After what you've done, do you still have access to Safestrap? Installing an amazon update with Safestrap installed, or even just rooted could easily mess up the device, i.e. brick it.
Click to expand...
Click to collapse
Oh and I'm not sure what the new board had on it. It never fully booted. That's why I installed twrp. Thanks for the reply though!
Sent from my SM-G920V using XDA-Developers mobile app
mhuck0625 said:
I don't think it's fire os 4x then. It does boot into the twrp interface and is fully functional but when you go to reboot into a different recovery it says something like "it appears you do not have root. Would you like to install supersu?" Even if I say yes it acts like it installs but apparently doesn't. I can post pics later
Click to expand...
Click to collapse
mhuck0625 said:
Oh and I'm not sure what the new board had on it. It never fully booted. That's why I installed twrp. Thanks for the reply though!
Click to expand...
Click to collapse
- how did you "install" TWRP (method)?
- how are you accessing TWRP - just pressing the power button or some key combination (yes, it's important)?
- does a graphic vaguely resembling Frankenstein appear when you power up the device?
Davey126 said:
- how did you "install" TWRP (method)?
- how are you accessing TWRP - just pressing the power button or some key combination (yes, it's important)?
- does a graphic vaguely resembling Frankenstein appear when you power up the device?
Click to expand...
Click to collapse
I installed TWRP using the method instructed here: http://forum.xda-developers.com/kin...-to-unbrick-kindle-fire-hdx-firmware-t3277197
When i want to get to TWRP i press and hold Power + Vol UP until it rebootes into the Teamwin screen and TWRP. It is version 2.8.7.0 now(the instructions got 2.8.5.0 installed then i upgraded)
I dont remember what the graphic looked like when booting into TWRP but i know it said TeamWin. I can check when i get it charged back up enough to turn on. Ive had it sitting unplugged for days and the battery ran dead. I hope this is enough info to help get me pointed in the right direction. Thanks!
Ok, if it's the real TWRP which it seems to be, Safestrap has no TeamWin logo at boot, I'd suggest you leave it be. Currently you can use all available ROMs, so if there'll be a future version of Fire OS you could use a TWRP flashable version of it. I doubt there will be a Fire OS 5 update for the "old" Thor/Apollo line though.
You would destroy the possibilities you currently have by updating to Fire OS 4.5.5.1.
Meanwhile you can unlock your bootloader (if you haven't already), and update TWRP to 3.0.0-1 (requires unlocked bootloader).
Don't I need root though? How can I unlock my bootloader from the stage I'm at now? I'm just a bit afraid of proceeding in case I brick it again
Sent from my SM-G920V using XDA-Developers mobile app
Cl4ncy said:
Ok, if it's the real TWRP which it seems to be, Safestrap has no TeamWin logo at boot, I'd suggest you leave it be. Currently you can use all available ROMs, so if there'll be a future version of Fire OS you could use a TWRP flashable version of it. I doubt there will be a Fire OS 5 update for the "old" Thor/Apollo line though.
You would destroy the possibilities you currently have by updating to Fire OS 4.5.5.1.
Meanwhile you can unlock your bootloader (if you haven't already), and update TWRP to 3.0.0-1 (requires unlocked bootloader).
Click to expand...
Click to collapse
Don't I need root though? How can I unlock my bootloader from the stage I'm at now? I'm just a bit afraid of proceeding in case I brick it again
Sent from my SM-G920V using XDA-Developers mobile app
There's no risk in unlocking, the bootloader either unlocks or it errors/fails. Try the one-click-solution first (might require the PDANet drivers). It's recommended to update the bootloader to 3.2.3.2 (do it only, if the unlock worked ok).
TWRP can be updated from TWRP itself, so I'd recommend doing it that way. Just be sure to flash the TWRP image to the recovery partition.
Cl4ncy said:
There's no risk in unlocking, the bootloader either unlocks or it errors/fails. Try the one-click-solution first (might require the PDANet drivers). It's recommended to update the bootloader to 3.2.3.2 (do it only, if the unlock worked ok).
TWRP can be updated from TWRP itself, so I'd recommend doing it that way. Just be sure to flash the TWRP image to the recovery partition.
Click to expand...
Click to collapse
Tried 1-Click. In both Linux(Ubuntu 16.04) and Windows(10.1 x64) i get an error saying ADB is not enabled on the device. Ive tried booting into fastboot(with fastboot cable) tried using the regular cable and booting into TWRP. Any combination of boot modes and cables i can think of wont work. Where should i go from here?
Thanks
mhuck0625 said:
Don't I need root though? How can I unlock my bootloader from the stage I'm at now? I'm just a bit afraid of proceeding in case I brick it again
Click to expand...
Click to collapse
Root is irrelevant at this stage as nothing has been flashed to the system partition (where ROMs live).
Davey126 said:
Root is irrelevant at this stage as nothing has been flashed to the system partition (where ROMs live).
Click to expand...
Click to collapse
Ok, so i will need root to install ROMs then? How do i solve my problem unlocking the bootloader?
mhuck0625 said:
Tried 1-Click. In both Linux(Ubuntu 16.04) and Windows(10.1 x64) i get an error saying ADB is not enabled on the device. Ive tried booting into fastboot(with fastboot cable) tried using the regular cable and booting into TWRP. Any combination of boot modes and cables i can think of wont work. Where should i go from here?
Thanks
Click to expand...
Click to collapse
Lack of a functioning ROM could prove problematic if ADB is not enabled. I do not recall if the version of TWRP you installed provides native support for MTP which is essential for moving files onto the device. You may need to go the manual route to unlock bootloader which still requires tethered access but only at the fastboot level.
Nearing the edge of my pay grade on this topic; looking for others with more recent experience to jump in...
Davey126 said:
Lack of a functioning ROM could prove problematic if ADB is not enabled. I do not recall if the version of TWRP you installed provides native support for MTP which is essential for moving files onto the device. You may need to go the manual route to unlock bootloader which still requires tethered access but only at the fastboot level.
Nearing the edge of my pay grade on this topic; looking for others with more recent experience to jump in...
Click to expand...
Click to collapse
I do have mtp access and can transfer files easily. Should I try installing a Rom to see if I get adb access? What's a good Rom to try
Sent from my SM-G920V using XDA-Developers mobile app
Davey126 said:
Lack of a functioning ROM could prove problematic if ADB is not enabled. I do not recall if the version of TWRP you installed provides native support for MTP which is essential for moving files onto the device. You may need to go the manual route to unlock bootloader which still requires tethered access but only at the fastboot level.
Nearing the edge of my pay grade on this topic; looking for others with more recent experience to jump in...
Click to expand...
Click to collapse
Just curious on one thing. Whenever i see a ROM to download it says i need to unlock the bootloader and have root before i can do that. In MY case i do NOT have either, yet i was able to flash a new recovery(TWRP) How is this possible? How would i go about installing a new ROM or unlocking the bootloader?
Is there a way to flash the stock recovery back so i can reinstall fireOS and start from scratch?
Is there a way to tell what bootloader i have from within TWRP?
I realize i probably should have done a little more reading before i started messing with it :/ I do appreciate all the help you have been able to provide so far!
mhuck0625 said:
I do have mtp access and can transfer files easily. Should I try installing a Rom to see if I get adb access? What's a good Rom to try
Click to expand...
Click to collapse
mhuck0625 said:
Just curious on one thing. Whenever i see a ROM to download it says i need to unlock the bootloader and have root before i can do that. In MY case i do NOT have either, yet i was able to flash a new recovery(TWRP) How is this possible? How would i go about installing a new ROM or unlocking the bootloader?
Is there a way to flash the stock recovery back so i can reinstall fireOS and start from scratch?
Is there a way to tell what bootloader i have from within TWRP?
I realize i probably should have done a little more reading before i started messing with it :/ I do appreciate all the help you have been able to provide so far!
Click to expand...
Click to collapse
- traveling; response will be brief
- suggest flashing cm11 as it does not require an unlocked bootloader nor GAaps for basic functionality
- include SuperSU in flash package to secure root
- follow flashing directions in cm11 OP
- report back results; will go from there
Davey126 said:
- traveling; response will be brief
- suggest flashing cm11 as it does not require an unlocked bootloader nor GAaps for basic functionality
- include SuperSU in flash package to secure root
- follow flashing directions in cm11 OP
- report back results; will go from there
Click to expand...
Click to collapse
Downloaded CM11 and installed via this thread
http://forum.xda-developers.com/kin...-cm-11-safestrap-20150628-unofficial-t3145547
Copied it as well as the latest SuperSu(v2.65) to the Kindle Fire
Went to Install, saw both Zip files. Selected them(CM11 first, then Supersu second) Swipe to install, rebooted and nothing came up. Rebooted into TWRP and repeated the process after wiping dalvik/cache. Still nothing
mhuck0625 said:
Downloaded CM11 and installed via this thread
http://forum.xda-developers.com/kin...-cm-11-safestrap-20150628-unofficial-t3145547
Copied it as well as the latest SuperSu(v2.65) to the Kindle Fire
Went to Install, saw both Zip files. Selected them(CM11 first, then Supersu second) Swipe to install, rebooted and nothing came up. Rebooted into TWRP and repeated the process after wiping dalvik/cache. Still nothing
Click to expand...
Click to collapse
Makes sense. Likely no kernel. Will probably need to install a full version of FireOS for underlying components. Need to have a think about which build to maximize results, minimize rework. More later....
Davey126 said:
Makes sense. Likely no kernel. Will probably need to install a full version of FireOS for underlying components. Need to have a think about which build to maximize results, minimize rework. More later....
Click to expand...
Click to collapse
You have no idea how much i appreciate the help!
I look forward to hearing what you come up with!!
I would be happy just going straight back to full fire os - Stock EVERYTHING and not even worrying about running another OS. I just want to have a usable tablet again!
Dear forum,
I had installed the Nexus Custom ROM with TWRP on my Kindle HDX which worked out fine so far. Then I and wanted to go to CM11. Probably because my device was still locked and/or because I wiped too many things in the wipe-menu, my kindle is stuck in the Boot loop and stops loading while displaying the grey kindle logo. I am still able to access TWRP and the device is found by windows.
I would like to go back to the stock rom and read a lot of threads in the forum but I am not really sure where to start without making my situation worse. I tried to install back my backup (several *.win files) but that does not work. Can you please help me what I need to do?
Kind regards,
Aldaris001
Aldaris001 said:
Dear forum,
I had installed the Nexus Custom ROM with TWRP on my Kindle HDX which worked out fine so far. Then I and wanted to go to CM11. Probably because my device was still locked and/or because I wiped too many things in the wipe-menu, my kindle is stuck in the Boot loop and stops loading while displaying the grey kindle logo. I am still able to access TWRP and the device is found by windows.
I would like to go back to the stock rom and read a lot of threads in the forum but I am not really sure where to start without making my situation worse. I tried to install back my backup (several *.win files) but that does not work. Can you please help me what I need to do?
Kind regards,
Aldaris001
Click to expand...
Click to collapse
TWRP or Safestrap (version)? They are not the same thing. Makes a big difference in the potential solution set.
Thanks for your swift reply! I have TWRP 2.8.6.0 installed.
Aldaris001 said:
Thanks for your swift reply! I have TWRP 2.8.6.0 installed.
Click to expand...
Click to collapse
Strongly recommend unlocking bootloader with 1-click utility (here). Otherwise you run the risk of permanently bricking your device if the recovery partition holding TWRP becomes damaged/unbootable. Once unlocked you can flash a modified build of FireOS 4.5.5 from here
Of course, once unlocked you could flash a higher version of Nexus, CM 11 (both KitKat based), CM 12.1 (Lollipop), CM 13 (Marshmallow) or several other rom variants. Each is a heck of a lot better than Stock FireOS v4.
At some point you should also consider moving to the latest version of TWRP (here).
Hi Davey,
Thanks a lot for the hint! I have tried the 1-click bootloader but running in an issue that the ADB device is not recognized. The drivers seem to work though. Do I need to activate ADB in TWRP somewhere or is it activated by default? The ADB sideload option seem to be something else, right?
Aldaris001 said:
Hi Davey,
Thanks a lot for the hint! I have tried the 1-click bootloader but running in an issue that the ADB device is not recognized. The drivers seem to work though. Do I need to activate ADB in TWRP somewhere or is it activated by default? The ADB sideload option seem to be something else, right?
Click to expand...
Click to collapse
Drivers are always a PiTA with Windows and Amazon devices. You'll need to fight through it taking clues from various posts on the topic. Some tips:
- nothing needs to be enabled in TWRP
- drivers need to work in both ADB and Fastboot modes
- cleanest approach IMO:
>> launch windows device manager, tether device, see what shows up in device manager, uninstall those device(s), disconnect, reboot both devices (important), reconnect and then guide windows to the drivers of your choosing
Thanks a lot for your help, I got it running again! In the end it did not work with the 1-click method but manually I could unlock the bootloader and flashed CM 12.1.
Aldaris001 said:
Thanks a lot for your help, I got it running again! In the end it did not work with the 1-click method but manually I could unlock the bootloader and flashed CM 12.1.
Click to expand...
Click to collapse
Thanks for the update. Glad you got things sorted; manual unlocking isn't that bad with a little patience. CM 12.1 is solid (probably my next stop; still rocking Nexus) but keep an eye on CM 13 as the dev team hammers out a few final issues. Enjoy your liberated HDX!
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.