Hi,
So a while back(couple years ago), I successfully rooted my kindle fire hdx and installed cynogenmod(i think cm11) using safestrap because I think I remember reading something about how this specific kindle could not install twrp. Everything was running fine and my root was working. Anyways, fast forward to now I discovered that certain apps that detect root such as banking apps do not allow use on rooted devices. I found something called Magisk which is an alternative root that is hidden from apps. I then downloaded the Magisk manager and tried to install it directly using the app without first unrooting my current SuperSU root.
My device is now stuck in a bootloop with the kindle fire logo. I have tried resetting to factory defaults but it did not help. Does anyone know how to solve this problem? Thanks.
yumsty said:
Hi,
So a while back(couple years ago), I successfully rooted my kindle fire hdx and installed cynogenmod(i think cm11) using safestrap because I think I remember reading something about how this specific kindle could not install twrp. Everything was running fine and my root was working. Anyways, fast forward to now I discovered that certain apps that detect root such as banking apps do not allow use on rooted devices. I found something called Magisk which is an alternative root that is hidden from apps. I then downloaded the Magisk manager and tried to install it directly using the app without first unrooting my current SuperSU root.
My device is now stuck in a bootloop with the kindle fire logo. I have tried resetting to factory defaults but it did not help. Does anyone know how to solve this problem? Thanks.
Click to expand...
Click to collapse
Bootloop was 100% assured regardless of what you did with SuperSU. You'll need to intentionally 'brick' (not entirely accurate) and unlock you device to recover. Upside is you will score a more versatile gizmo that can run a newer version of Android. Downside is procedure is not for the faint of heart. You'll receive little assistance along the way as these devices have fallen out of favor despite being superior to most other <$200 USD Android tablets on the market today. Good luck.
https://forum.xda-developers.com/kindle-fire-hdx/general/how-to-root-unlock-hdx-noobies-t3916167
https://forum.xda-developers.com/kindle-fire-hdx/general/multi-platform-1-click-bootloader-t3241014
Related
First let me say thank you to all of the developers on here who work so hard to help everyone, and give us resources to get the most out of our devices. I've been lurking on this forum for a while, and it's enabled me to root my last two Kindles, and two smartphones over the last couple of years.
I had to finally register because I need some help with my Kindle Fire HDX 8.9". Like many recently, I was able to root my device with towelroot, I installed rootchecker (which confirmed root) and SuperSU, as well as the Google Play Store. So all was great, but when I went to run the toolkit so I could block OTA updates that's where I couldn't succeed. Whenever I tried to disable updates or check root status it just kept giving errors and saying device not found, and asking me to please allow root to my device.
I made sure ADB was enabled, but I still couldn't get the toolkit to do anything. So, I lost root today because of the latest kindle update. What am I doing wrong that's not allowing the toolkit to disable updates?
i faced same issue of device not found while using toolkit
here follow this
https://developer.amazon.com/appsan...etting-up-your-kindle-fire-tablet-for-testing
Try rerooting
Try rerooting your device with the tool and then try again to disable updates. This might work. What version are you on now?
blade22 said:
i faced same issue of device not found while using toolkit
here follow this
Click to expand...
Click to collapse
Just what I needed, thanks!!
Hello,
I have browsed XDA for some time now(S4 launch), but this is the first time I have not been able to get my problem solved without posting directly.
As such, I'm not quite sure if this is the correct place to post this and I sincerely apologize if I am in the wrong here.
Specs:
Android Version 5.0.2.
Baseband Version G925VVRU1AOE2
Kernal Version 3.10.61 Dated May 12, 2015
Hardware G925V.04
KNOX 2.4
The biggest issue is ping pong root not working for my device. I think if I can get this to work, my issues would be solved.
-Yes, it is in the supported devices section
-- I have searched [ROOT] PingPongRoot ***S6 & S6 Edge Root Tool*** Android 5.0.2 OC3/OE2 Only!!! extensively for this specific issue to no avail
--- I follow all steps and still get "device not supported, stay tuned"
---- using the search function within the thread, I looked for anything relating to G925VVRU1AOE2 and also tried a number of tricks that weren't build specific.
----- I have flashed G925VVZW1AOC3 and rooted with ping pong root with no issues. Flashing AOE2 back on gives the same error I had before.
------ Once upon a time I rooted with ping pong root on AOE2... This was shortly after it was supported.
My ultimate goal is to install a custom ROM. I was thinking Extreme Syndicate V8
For this, I need to be rooted on AOE2 via ping pong root.. Like I mentioned before, AOC3 root works fine and I have no issues with using that, except I need AOE2 + flashfire for this ROM.
I have never installed a custom ROM before, but I would like to start. If this ROM is a bad choice, I am open to suggestions. The extreme debloat is what drew me here.
All that said and done, I'll provide a little more in depth history.
I mentioned I originally rooted AOE2 with ping pong root in the past.
Shortly after that I was using XMODGAMES and somehow ended up downloading KINGROOT. Not sure what it did to my device but I could never uninstall kingroot completely. It would reinstall on reboot even after uninstalling with kingroot.
Eventually I came across SuperSUme and used that to successfully remove kingroot and switch over to SuperSU.
All was well and good (on my Stock AOE2 ROM)
About 2 days ago my google services framework crashed. I was able to identify Google+ not syncing properly as the cause... However I could not locate a fix. Through my tinkering I lost the google play store. So I decided to just do a full factory reset, hoping it would be simpler than trying to fix the issues I was having.
That brings us to today. I have so far flashed AOE2 - > AOC3 -> AOE2, with around 5 hard resets in between.
I figured I could just use kingroot to get rooted, then SuperSUme to get back to SuperSU and that should allow me to use flashfire.
WRONG. SuperSUme never asks for root permission(or kingroot automatically blocks it idk). So SuperSUme doesn't work. I tried this with kingroot 4.9, then 4.1 and I think 4.5 (not exactly sure what the last one was)
I looked for a more complex rooting method since it appears the one touch ones weren't going to get the job done, but couldn't find anything.
If anybody could point me in the right direction to getting rooted with SuperSU, it would be greatly appreciated.
Thank you for your time.
Or do we have another way to unlock bootloader without root?
Is downgrading still possible for out of warranty device?
kkcheong said:
Or do we have another way to unlock bootloader without root?
Is downgrading still possible for out of warranty device?
Click to expand...
Click to collapse
- FireOS 4.5.5.2 can be downgraded to 3.2.8 and rooted w/towelroot (procedure)
- once rooted bootloader unlock proceeds as described here
- it is *essential* WiFi be disabled while on 3.2.8 except for the few seconds needed for rooting
- recommend engaging airplane/flight mode as an additional precaution
- failure to observe the above cautions will (with great certainty) result in an unrecoverable brick if an OTA update is downloaded/installed
Thanks. I thought only 4.5.5.1 supported based on first page of the downgrade thread. Upon reading, seems like work on 4.5.5.2 too.
Davey126 said:
- FireOS 4.5.5.2 can be downgraded to 3.2.8 and rooted w/towelroot (procedure)
- once rooted bootloader unlock proceeds as described here
- it is *essential* WiFi be disabled while on 3.2.8 except for the few seconds needed for rooting
- recommend engaging airplane/flight mode as an additional precaution
- failure to observe the above cautions will (with great certainty) result in an unrecoverable brick if an OTA update is downloaded/installed
Click to expand...
Click to collapse
Davey126 said:
- FireOS 4.5.5.2 can be downgraded to 3.2.8 and rooted w/towelroot (procedure)
- once rooted bootloader unlock proceeds as described here
- it is *essential* WiFi be disabled while on 3.2.8 except for the few seconds needed for rooting
- recommend engaging airplane/flight mode as an additional precaution
- failure to observe the above cautions will (with great certainty) result in an unrecoverable brick if an OTA update is downloaded/installed
Click to expand...
Click to collapse
Wait are you saying that towelroot works with 4.5.5.2? Or do you mean that towelroot works after using the downgrade file?
bigboolean said:
Wait are you saying that towelroot works with 4.5.5.2? Or do you mean that towelroot works after using the downgrade file?
Click to expand...
Click to collapse
TowelRoot only works with FireOS v3. However, it is more reliable than KingRoot on FireOS v4 so worth the downgrade effort IMO.
Davey126 said:
TowelRoot only works with FireOS v3. However, it is more reliable than KingRoot on FireOS v4 so worth the downgrade effort IMO.
Click to expand...
Click to collapse
Can you explain the differences and reliability issues with Kingroot FireOS V4?
Archangel1183 said:
Can you explain the differences and reliability issues with Kingroot FireOS V4?
Click to expand...
Click to collapse
- TowelRoot typically roots within seconds; KingRoot can take many iterations
- KingRoot modifies various system files and installs additional components (crapware) without permission
- KingRoot actively resists uninstallation with each revision being increasingly difficult to remove
- TowelRoot is only effective against FireOS 3.x (Android 4.2 based); Kingroot works on a much wider range of Android builds and at present is the only reliable root solution for FireOS v4 and v5
I just rooted my Kindle HDX 7 firmware version 4.5.5.2 with Kingroot v. 4.9.2. You just have to be "VERY PERSISTENT" because it root will fail over and over again but eventually the firmware will give up and let Kingroot root your tablet. I took me 3 hours to root mine so be persistent. Now I'm working on blocking Amazon firmware updates.
RMNDGGG said:
... but eventually the firmware will give up and let Kingroot root your tablet. I took me 3 hours to root mine so be persistent. Now I'm working on blocking Amazon firmware updates.
Click to expand...
Click to collapse
It's not Amazon's firmware somehow resisting rooting; KingRoot's vulnerability detection and exploit matching algorithm is (generously) unsophisticated. Not much better than trial and error with a short fuse.
Also consider unlocking the bootloader and installing a custom ROM (ie: pure Android) to fully liberate your device. You'll probably want to do this anyhow to remove the malware like detritus KingRoot leaves behind.
RMNDGGG, I just installed kingroot 5.0.1 after reading your message and ran it. It looks like my hdx rooted successfully. I double checked it with a root checker and it also said that it's rooted.
Now I need to install Android. I'll search for instructions, but if anyone has a link, can you shoot it over? Thanks
Archangel1183 said:
RMNDGGG, I just installed kingroot 5.0.1 after reading your message and ran it. It looks like my hdx rooted successfully. I double checked it with a root checker and it also said that it's rooted.
Now I need to install Android. I'll search for instructions, but if anyone has a link, can you shoot it over? Thanks
Click to expand...
Click to collapse
You will need to unlock the bootloader first: https://forum.xda-developers.com/kindle-fire-hdx/general/thor-unlocking-bootloader-firmware-t3463982
I renamed 2 OTAupdated files to prevent it from auto updating and turned it off. When I turned it back on, I got a message saying "Updating applications" and it loaded on to a black screen where the home screen should be. I restarted it several times and now it just gets stuck on the "Kindle Fire" loading screen.
Archangel1183 said:
I renamed 2 OTAupdated files to prevent it from auto updating and turned it off. When I turned it back on, I got a message saying "Updating applications" and it loaded on to a black screen where the home screen should be. I restarted it several times and now it just gets stuck on the "Kindle Fire" loading screen.
Click to expand...
Click to collapse
Likely reamed the wrong file(s). If you haven't unlocked the bootloader it's pretty much game over. You can try a 'factory reset' from the stock recovery menu but that rarely fixes system problems. Stock recovery does not offer the ability to reload or repair FireOS. Sorry ...
Yeah, I think I did one too many files. The post I read only mentioned one file but I found two with similar names. I'll try a factory reset later. Thanks, Davey.
I used the Kindle Fire Unbrick Utility V1.1 that I found on the forums. I tried a couple different options offered in the tool and it seemed like none of them were doing anything. They kept saying "Device not found". I knew the computer was detecting it because I installed the drivers a couple weeks back and it was showing "Fire" in device manager. I was done with the tool and was going to use this unbricking method (forum.xda-developers.com/showthread.php?t=2793253), when my kindle suddenly went passed the boot screen into my lock screen. I unlocked it and again got a black screen. I wanted to get into ES File explorer to rename the 2nd file back to the original name, but I couldn't see any app icons. I accidentally swiped up from the bottom and a menu with app icons popped up. I was then able to get into ES File explorer and rename the file. I exited the app and wooot.... no more black screen.
For anyone reading this..... DO NOT Rename DeviceSoftwareOTAContracts.apk or you will get a black home screen without any apps. I renamed DeviceSoftwareOTA.apk to DeviceSoftwareOTAold (no apk) and it's working fine. So far my Kindle fire HDX 7 is still rooted.
Someone on another forum posted that this version of Kingroot, apparently updated 1/22/17 (v 5.0.3), works for the last update of Fire OS on Thor (4.5.5.2). Has anyone tried this out? I want it to be true, because I lost root on the last update, but I don't want to brick my device or open myself up to any other issues if it's some sort of trojan. At some point I was going to try a rollback and then root, but I would much prefer to use a one and done apk if possible. Can anyone confirm that this works?
Vanb85 said:
Someone on another forum posted that this version of Kingroot, apparently updated 1/22/17 (v 5.0.3), works for the last update of Fire OS on Thor (4.5.5.2). Has anyone tried this out? I want it to be true, because I lost root on the last update, but I don't want to brick my device or open myself up to any other issues if it's some sort of trojan. At some point I was going to try a rollback and then root, but I would much prefer to use a one and done apk if possible. Can anyone confirm that this works?
Click to expand...
Click to collapse
All KingRoot builds use the same cloud database to scan for vunerabalities and match up with known exploits. The various KingRoot clients may sequence tests differently and clutter your device with varying 'gifts'... especially the v5 series. I would go the rollback and root path. It's safe, easy and fast. Only caveat is the device must maintain network isolation (WiFi off; airplane mode engaged) while the device is on FireOS 3.2.8. If the device takes an OTA update while on 3.2.8 it will brick with no possible recovery.
Davey126 said:
All KingRoot builds use the same cloud database to scan for vunerabalities and match up with known exploits. The various KingRoot clients may sequence tests differently and clutter your device with varying 'gifts'... especially the v5 series. I would go the rollback and root path. It's safe, easy and fast. Only caveat is the device must maintain network isolation (WiFi off; airplane mode engaged) while the device is on FireOS 3.2.8. If the device takes an OTA update while on 3.2.8 it will brick with no possible recovery.
Click to expand...
Click to collapse
KingRoot is basically how I was planning on rooting my device anyway. Is there any real advantage, in terms of "safety" with applying KingRoot after I've done the rollback as opposed to before doing one? And can KingRoot even be don on 4.5.5.2? I've been told ad naseum that this version of Fire OS cannot be rooted, but it looks as though it can now. If I'm going to be taking a risk with KingRoot anyway, wouldn't it be better to do so without the rollback and possible bricking of my device? Has there been any confirmation that KingRoot can in fact root 4.5.5.2 now?
eta: And just to be clear, this is KingRoot that we're talking about, right, not KingORoot?
Yes, I used Kingroot 4.8.1 to root 4.5.5.2. It took a couple of retries, but eventually it was successful.
Vanb85 said:
KingRoot is basically how I was planning on rooting my device anyway. Is there any real advantage, in terms of "safety" with applying KingRoot after I've done the rollback as opposed to before doing one? And can KingRoot even be don on 4.5.5.2? I've been told ad naseum that this version of Fire OS cannot be rooted, but it looks as though it can now. If I'm going to be taking a risk with KingRoot anyway, wouldn't it be better to do so without the rollback and possible bricking of my device? Has there been any confirmation that KingRoot can in fact root 4.5.5.2 now?
eta: And just to be clear, this is KingRoot that we're talking about, right, not KingORoot?
Click to expand...
Click to collapse
KingRoot is borderline malware but gets the job done (eventually; often takes multiple attempts) and carries no additional liabilities if the device is going to be immediately unlocked and wiped. 4.5.X -> 3.2.8 rollback is not unduly risky if network isolation is maintained on 3.2.8. TowelRoot is the tool of choice on FireOS v3; fast and reliable. Ultimately the choice is yours. Good luck.
Davey126 said:
KingRoot is borderline malware but gets the job done (eventually; often takes multiple attempts) and carries no additional liabilities if the device is going to be immediately unlocked and wiped. 4.5.X -> 3.2.8 rollback is not unduly risky if network isolation is maintained on 3.2.8. TowelRoot is the tool of choice on FireOS v3; fast and reliable. Ultimately the choice is yours. Good luck.
Click to expand...
Click to collapse
Another quick newbie question. Does KingRoot have to stay on your device in order to maintain root access? Can I use it to root and then uninstall it and still maintain root access? Is that what you mean by "unlocked and wiped?"
Vanb85 said:
Another quick newbie question. Does KingRoot have to stay on your device in order to maintain root access? Can I use it to root and then uninstall it and still maintain root access? Is that what you mean by "unlocked and wiped?"
Click to expand...
Click to collapse
Uninstalling KingRoot (KingUser) via conventional means also removes root. There are methods for transitioning a different root manager (eg: SuperSU) if you plan to stay on FireOS. SuperSume is one such tool. Does not seem to be effective against more recent KingRoot builds which actively resist removal.
Unlocking refers to the bootloader; wiping is a recommended prerequisite for cleanly replacing FireOS with a custom ROM. Wiping also removes KimgRoot detritus.
Anatinae said:
Yes, I used Kingroot 4.8.1 to root 4.5.5.2. It took a couple of retries, but eventually it was successful.
Click to expand...
Click to collapse
Have you tried installing SuperSu or another root manager as a replacement since rooting with KingRoot?
I unlocked the bootloader and installed LineageOS. Using the default root included with the latest unofficial build.
Anatinae said:
I unlocked the bootloader and installed LineageOS. Using the default root included with the latest unofficial build.
Click to expand...
Click to collapse
I see. So you replaced KingRoot with the default root manager that came with the LineageOS build?
Update: I did install KingRoot. And I installed the Google Play Store after that. I was unable to replace KingRoot with SuperSu. So, I uninstalled KingRoot, and of course, it took root access with it. But I got what I wanted, for the most part, which was to be able to install the Google Play Store on my HDX. It appears to be working fine even without root access. I would have preferred to keep root access, but I don't really trust KingRoot enough to keep it on my device. Now, I just need to block updates so Amazon doesn't mess with GPS.
Can anyone tell me if it's okay that I moved the DeviceSystemOTA.apk to another folder? It wouldn't allow me to rename it, so I cut and paste it into another folder to rename it with the intention of moving it back to the system folder. I realized after it wouldn't allow me to put the file back that I can't do anything with the system folder (can't rename things, can't add files) now that I don't have root. It only let me remove the file. Is it okay that the file is just not in the system folder? I was essentially going to make it inoperable by renaming it and removing "apk" from it anyway. @Davey126?
Vanb85 said:
Can anyone tell me if it's okay that I moved the DeviceSystemOTA.apk to another folder? It wouldn't allow me to rename it, so I cut and paste it into another folder to rename it with the intention of moving it back to the system folder. I realized after it wouldn't allow me to put the file back that I can't do anything with the system folder (can't rename things, can't add files) now that I don't have root. It only let me remove the file. Is it okay that the file is just not in the system folder? I was essentially going to make it inoperable by renaming it and removing "apk" from it anyway. @Davey126?
Click to expand...
Click to collapse
Should not be a problem provided you remember where it resides should you wish to enable OTA updates at a later time. Note there are other system files containing the characters "OTA" that should not be moved or renamed.
Davey126 said:
Should not be a problem provided you remember where it resides should you wish to enable OTA updates at a later time. Note there are other system files containing the characters "OTA" that should not be moved or renamed.
Click to expand...
Click to collapse
Good to know. Yeah, it was just the one file. Thanks so much for your help.
Took delivery of a couple of HDX tablets today. I got a chance to try a "Replace Kingroot with SuperSU script" I modded for the HDX. The script was taken from supertools which also used chainfires root.sh script.
Anyway it seems to have worked perfect, I've two HDX on 4.5.5.2 with SuperSU on them instead of Kingroot 4.8.2 which was used in the script. That kingroot version rooted on the 2nd attempt on both tablets, both factory reset and unregistered.
Files attached feel free to modify as required.
any ideas
so im rooted , ota are turned off, and safe strap is installed and here comes the but... it lets me install recovery but when i hit reboot to recovery it reboots and then powers up like normall?? it doesnt let me go into a recovery mode??? o and 4.5.5.2 is what is running
thumper_ss said:
so im rooted , ota are turned off, and safe strap is installed and here comes the but... it lets me install recovery but when i hit reboot to recovery it reboots and then powers up like normall?? it doesnt let me go into a recovery mode??? o and 4.5.5.2 is what is running
Click to expand...
Click to collapse
Please don't cross post; responded in other thread.
Davey126 helped me fix my Kindle Fire HDX 7 that was stuck as No OS when I accidentally wiped and formatted it via twrp and now I am running Thor (Android version 4.4.4). I want to return my Kindle to the FireOS and I have tried flashing it via twrp but it says error updating binary in zip. I also tried the "full unroot" option in supersu and it just deleted SuperSU from my app list. I reflashed the Thor via twrp to get SuperSU back in case I needed it to unroot and return to FireOS 4.2.2.1. I am trying to get it back to stock because my WI-FI stopped working on it and I believe it is the antenna but not sure and when I went to Amazon for help they need my tablet's original serial number and other information and I can't access the things they need with it rooted and running Thor. I am hoping to get this fixed but I know they won't help me if they know it is rooted. If you could point me in the right direction for accomplishing this unroot I would be eternally grateful.
Heatherb90 said:
Davey126 helped me fix my Kindle Fire HDX 7 that was stuck as No OS when I accidentally wiped and formatted it via twrp and now I am running Thor (Android version 4.4.4). I want to return my Kindle to the FireOS and I have tried flashing it via twrp but it says error updating binary in zip. I also tried the "full unroot" option in supersu and it just deleted SuperSU from my app list. I reflashed the Thor via twrp to get SuperSU back in case I needed it to unroot and return to FireOS 4.2.2.1. I am trying to get it back to stock because my WI-FI stopped working on it and I believe it is the antenna but not sure and when I went to Amazon for help they need my tablet's original serial number and other information and I can't access the things they need with it rooted and running Thor. I am hoping to get this fixed but I know they won't help me if they know it is rooted. If you could point me in the right direction for accomplishing this unroot I would be eternally grateful.
Click to expand...
Click to collapse
A couple terminology clarifications:
- "Thor" refers to the device type (7" third gen HDX) independent of ROM
- Your device is currently running Fire Nexus which is based on Android 4.4.x
Unfortunately, there is no (reasonable) way to return your device to pure stock. You can replace Fire Nexus with a special build of FireOS and remove root but it will always be 'custom'. Amazon bears part of the blame for this as they did not provide a mechanism for reloading FireOS on 3rd and 4th gen devices.
Your device is out of warranty. Amazon will not be able to help with a hardware problem even if you supplied the requested info. It's also unlikely the antenna would spontaneously go bad...especially given the way in which it is internally routed.
Can you provide more details on when WiFi stopped working? Guessing this is a setting/software issue although a hardware fault is not out of the question.
I have been on CM11 for years now and wish to revert back to FIRE OS. How can this be done? I looked around but didn't see how.
EDIT: I found how. Sorry to bother you.
https://forum.xda-developers.com/kindle-fire-hdx/help/return-hdx-7-c9r6qm-to-stock-kindle-t3544483