I have been doing a lot of indepth reading regarding the whole process of loading Lollipop on a Kindle Fire HDX 7.
I thought I had the process understood but have realised I might have a problem. It seems that there is a loop where you need to ROOT the Kindle in order to rollback the ROM, but all the rooting methods seem to rely on having a 13.3.2 or earlier ROM in order to ROOT it.
It seems that the vulnerabilities which allowed the zergRush root method have been fixed, as have the TowelRoot vulnerabilities. These are the only two methods I have found so far after extensive searching.
I am not certain which ROM my Kindle will have since I have ordered it as present for my wife off of Ebay. It maybe that its got an old ROM and all will be OK, but I would rather not waste my time and possibly brick the Kindle by trying outdated fixes.
I have loaded Android-SDK and Android-Tools onto my Opensuse system, but I understand that I can only "adb push" a rollback ROM if I have already ROOTed the Kindle.
Any guidance to avoid a horrible mistake would be much appreciated.
Stephen
What version of FireOS are you on?
EncryptedCurse said:
What version of FireOS are you on?
Click to expand...
Click to collapse
Wont know until it arrives at the weekend. Will post details then.
Looking at Kingroot as a possible option.
Stephen
Shoog03 said:
Wont know until it arrives at the weekend. Will post details then.
Looking at Kingroot as a possible option.
Stephen
Click to expand...
Click to collapse
Make sure that you don't connect to WiFi.
Your tablet may very well come with an older firmware that'll allow you to unlock the bootloader and install TWRP (allowing access to Lollipop or Marshmallow ROMs).
EncryptedCurse said:
Make sure that you don't connect to WiFi.
Your tablet may very well come with an older firmware that'll allow you to unlock the bootloader and install TWRP (allowing access to Lollipop or Marshmallow ROMs).
Click to expand...
Click to collapse
Yep, will switch off WIFI first thing and then try pushing out the mod-update-kindle-thor-13.3.2.8_user_713328020.bin rollback ROM using adb or gMTP (a Linux utility).
Definately want to go down the TWRP route. Am I to assume that if its a later ROM then accessing the bootloader and installing TWRP is permanently blocked ?
Fingers crossed that this has been sat lingering in a cupboard for the last year and a half.
Stephen
Shoog03 said:
Yep, will switch off WIFI first thing and then try pushing out the mod-update-kindle-thor-13.3.2.8_user_713328020.bin rollback ROM using adb or gMTP (a Linux utility).
Definately want to go down the TWRP route. Am I to assume that if its a later ROM then accessing the bootloader and installing TWRP is permanently blocked ?
Fingers crossed that this has been sat lingering in a cupboard for the last year and a half.
Stephen
Click to expand...
Click to collapse
Don't get ahead of yourself. You should check what firmware it comes with first, and only then evaluate your options; you shouldn't just blindly push the 3.2.8 update.
In order to unlock the bootloader, you'll need FireOS 3.2.3.2 or below. With the more recent versions, Amazon has included anti-rollback protection, which will permanently brick your device if you try to downgrade to anything past 3.2.8. Logically, this means that you'll be out of luck should your device come with FireOS 4 — at most, you'll be able to run a Kit Kat ROM on Safestrap, and others options will be, unfortunately, out of reach.
EncryptedCurse said:
Don't get ahead of yourself. You should check what firmware it comes with first, and only then evaluate your options; you shouldn't just blindly push the 3.2.8 update.
In order to unlock the bootloader, you'll need FireOS 3.2.3.2 or below. With the more recent versions, Amazon has included anti-rollback protection, which will permanently brick your device if you try to downgrade to anything past 3.2.8. Logically, this means that you'll be out of luck should your device come with FireOS 4 — at most, you'll be able to run a Kit Kat ROM on Safestrap, and others options will be, unfortunately, out of reach.
Click to expand...
Click to collapse
Thats good to know.
There are so many redundant instruction sets out there that it is very confusing.
Will post the OS when I get it and hopefully get a good pointer to the right strategy.
Stephen
EncryptedCurse said:
Don't get ahead of yourself. You should check what firmware it comes with first, and only then evaluate your options; you shouldn't just blindly push the 3.2.8 update.
In order to unlock the bootloader, you'll need FireOS 3.2.3.2 or below. With the more recent versions, Amazon has included anti-rollback protection, which will permanently brick your device if you try to downgrade to anything past 3.2.8. Logically, this means that you'll be out of luck should your device come with FireOS 4 — at most, you'll be able to run a Kit Kat ROM on Safestrap, and others options will be, unfortunately, out of reach.
Click to expand...
Click to collapse
Further elaboration: If the device arrives with FireOS 3.2.6 or lower you can rollback and unlock the bootloader. The exact path depends which version is on the device. 3.2.7 (rare) is effectively the same as 3.2.8. As noted keep WiFi off (or airplane/flight mode engaged) as an OTA can push and unwanted update and further restrict your options.
Davey126 said:
Further elaboration: If the device arrives with FireOS 3.2.6 or lower you can rollback and unlock the bootloader. The exact path depends which version is on the device. 3.2.7 (rare) is effectively the same as 3.2.8. As noted keep WiFi off (or airplane/flight mode engaged) as an OTA can push and unwanted update and further restrict your options.
Click to expand...
Click to collapse
Great.
Is the OTA switch off method where you delete the DeviceSoftwareOTA.apk file still working ?
Stephen
Shoog03 said:
Great.
Is the OTA switch off method where you delete the DeviceSoftwareOTA.apk file still working ?
Click to expand...
Click to collapse
Depends on FireOS version. Renaming (don't delete) DeviceSoftwareOTA.apk works fine on v4. FireOS v3 seemed to have a more elaborate mechanism. Best use HDX Toolbox to kill OTA and related services.
You may not need to kill OTA at all if your intent is to root, rollback, unlock and flash a custom ROM. Depends on the version of FireOS on the device.
Davey126 said:
Depends on FireOS version. Renaming (don't delete) DeviceSoftwareOTA.apk works fine on v4. FireOS v3 seemed to have a more elaborate mechanism. Best use HDX Toolbox to kill OTA and related services.
You may not need to kill OTA at all if your intent is to root, rollback, unlock and flash a custom ROM. Depends on the version of FireOS on the device.
Click to expand...
Click to collapse
There is another one of those Catch 22 situations going on here. Assuming I cannot start by rolling back the first thing I will need to do is load up a version of ES File Manager. However this is available through the Amazon App store, but in order to install it I will have to enable the WIFI to download it - which runs the risk of a OTA kicking in at the same time. So I would rather use adb to push the APK of ES File manager out to the Kindle - but here is the second catch I need a file manager to install the pushed APK. I have been digging into using adb install but what I have found so far suggests that it wont install the ES File Manager. See this for a person asking a similar question (and not getting an answer):
http://forum.xda-developers.com/kin...help-installing-es-file-explorer-adb-t3018469
It seems the only way to get started is to engage WIFI, and that runs the distinct risk of taking me to a bad place through OTA.
Stephen
Shoog03 said:
There is another one of those Catch 22 situations going on here. Assuming I cannot start by rolling back the first thing I will need to do is load up a version of ES File Manager. However this is available through the Amazon App store, but in order to install it I will have to enable the WIFI to download it - which runs the risk of a OTA kicking in at the same time. So I would rather use adb to push the APK of ES File manager out to the Kindle - but here is the second catch I need a file manager to install the pushed APK. I have been digging into using adb install but what I have found so far suggests that it wont install the ES File Manager. See this for a person asking a similar question (and not getting an answer):
http://forum.xda-developers.com/kin...help-installing-es-file-explorer-adb-t3018469
It seems the only way to get started is to engage WIFI, and that runs the distinct risk of taking me to a bad place through OTA.
Click to expand...
Click to collapse
No catch 22 - "adb install app.apk" works fine for ES File Explorer. Skip the Amazon store; grab a copy from here.
Bigger challenge will be rooting if it arrives with FireOS v4 as the most popular tool (Kingroot) requires a brief internet connection to perform its magic. But the process is manageable if carefully monitored; dozens/hundreds have done it.
Again - let's see what version of FireOS is on the device. That will determine next steps and clarify any obstacles you may face.
Davey126 said:
No catch 22 - "adb install app.apk" works fine for ES File Explorer. Skip the Amazon store; grab a copy from here.
Bigger challenge will be rooting if it arrives with FireOS v4 as the most popular tool (Kingroot) requires a brief internet connection to perform its magic. But the process is manageable if carefully monitored; dozens/hundreds have done it.
Again - let's see what version of FireOS is on the device. That will determine next steps and clarify any obstacles you may face.
Click to expand...
Click to collapse
OK thanks, so all I have to do is
adb install <path to app on kindle>app.apk
In my specific case the full instructions will go:
adb kill-server
adb start-server
adb devices <confirm kindle present>
adb push /home/stephen/Desktop/Fire_HDX_7/ES-File-Explorer-4.0.4.1.apk /sdcard/Download/
adb install /sdcard/Download/ES-File_Explorer-4.0.4.1.apk
adb kill-server
Cheers
Stephen
Shoog03 said:
OK thanks, so all I have to do is
adb install <path to app on kindle>app.apk
Click to expand...
Click to collapse
adb install <path to app on PC>app.apk
I find it easier to copy the apk into the directory where minimal adb and fastboot lives. Streamlines installs/pushes as no path is needed. (I actually employ symlinks to an apk repository but that's another topic).
Davey126 said:
adb install <path to app on PC>app.apk
I find it easier to copy the apk into the directory where minimal adb and fastboot lives. Streamlines installs/pushes as no path is needed. (I actually employ symlinks to an apk repository but that's another topic).
Click to expand...
Click to collapse
So it finally arrived (only took about 3 weeks thanks to Ebays ****ty GSP delivery fraud).
It looks brand new, so might be a reconditioned unit. Its a third generation Thor running OS 4.5.5.1 with a Build date of 13 November 2015 (which seems very late and may present an issue in itself).
The roll back thread seems to indicate that it is possible to roll-back the 4.5.5.1 using the mod-update-kindle-thor-13.3.2.8_user_713328020.bin image. I have plugged the Kindle into my Linux box and it appears as an android device, and I dragged and dropped the rollback image to the Download folder. However it will not allow me to check for updates since it requires a working Internet connection to proceed.
I have attempted to place the bin file straight into the sd card next to the Internal Storage folder, but this is root privileged and I have not yet rooted the device.
So its seems it back to the situation that the first step has to be rooting - which means switching on the WIFI to run Kingroot.
So wanting to be extremely cautious at this stage is there any advice as to how to proceed.
I also pushed out a copy of ES_File manager and tried to install using adb install but got this
[email protected]:~> adb devices
List of devices attached
D0FBA0A034530BHD unauthorized
[email protected]:~> adb install /sdcard/Download/ES-File-Explorer-4.0.4.1.apk
Invalid APK file: /sdcard/Download/ES-File-Explorer-4.0.4.1.apk
[email protected]:~> adb install /Internal storage/Download/ES-File-Explorer-4.0.4.1.apk
Invalid APK file: storage/Download/ES-File-Explorer-4.0.4.1.apk
[email protected]:~> adb install /Download/ES-File-Explorer-4.0.4.1.apk
Invalid APK file: /Download/ES-File-Explorer-4.0.4.1.apk
Click to expand...
Click to collapse
Stephen
OK, I didn't follow the instructions for the rollback precisely. I placed the rollback file into the internal storage folder and it found it straight away and is currently installing and doing its first reboot.
Stephen
So i am now running the rollback 13.3.2.8
What next ?
Best root method and then install safestrap and Kitkat and call it a day ?
Stephen
Managed to sideload ES_File_explorer by copying the file into my adb folder and running adb install.
Now I am downloading the update ROM 4.5.2
Will then sideload cve20147911.apk
Stephen
Successful upgraded to 4.5.2
So I installed Superuser and unlocked the root, but when I try to use ES_File_explorer to access the root it prompts with needs ES-permissions manager plugin. It offers to download it but that means switching on WIFI. I have tried to get the .apk file but don't find a good candidate, does anyone have any pointers.
Don't want to switch on the WIFI until OTA is disabled for which I need the permissions manger plugin.
Stephen
Shoog03 said:
Successful upgraded to 4.5.2
So I installed Superuser and unlocked the root, but when I try to use ES_File_explorer to access the root it prompts with needs ES-permissions manager plugin. It offers to download it but that means switching on WIFI. I have tried to get the .apk file but don't find a good candidate, does anyone have any pointers.
Don't want to switch on the WIFI until OTA is disabled for which I need the permissions manger plugin.
Stephen
Click to expand...
Click to collapse
Took the long rollback/upgrade road - 4.5.5.1 can be directly rooted with Kingroot. Assuming you secured root there is no need to tweak permissions. Simply rename DeviceSoftwareOTA.apk (details).
Related
Guy's the HDX is a fairly new device, the complete line has not even begun shipping yet & development is in it's infancy.
Currently, you can root your device, but it is HIGHLY recommended that you WAIT.
Currently, there are NO, ZERO, NONE, utilities or consistent fixes for soft bricked devices. This is not good, as currently there are several things that can soft brick this device.
In no circumstances should you do any of the following:
Remove apps or any files from the system folder or any sub-directory.
Restore previous veersions of Kindle apps from a Fire HD.
Make any modifications to any of the build.prop settings, or add any lines to the build.prop
Working but not advised at this time:
Adding any files or apks to the system partition or any sub-directory
There are numerous instances of modifications causing bootloops, soft bricks & KILLING ADB access. To my knowledge, I am the only person that has successfully recovered ADB access & for all the money in the world, I could not tell you how.
If you are not extremely proficient with reverse engineering software, or you don't know all the relevant ADB commands because you have been hacking devices for years, I STRONGLY suggest you wait to even root until further development progress has been made.
If you ignore this warning, you are likely going to be on your own in trying fix it, or you may be waiting months for a consistent fix to be found.
If you like taking risk & tinkering & you like to burn hundred dollar bills just for the pretty orange flame, well, by all means, go right ahead. Just realize right now, there may not ever be a recovery for your particular dilemma & in all likelihood by ignoring this warning, you've already made your warranty null & void.
Well said buddy.
I consider myself a fairly advanced android and linux user and I've customised the heck out of my n4 but I'm leaving my hdx as it is for now.
Good advise there.
Now if only mayday had a pro feature to help with rooting... haha
Can we set jcase up with a webcam? Lol
Sent from my Nexus 4 using Tapatalk
GSLEON3 said:
Currently, you can root your device, but it is HIGHLY recommended that you WAIT.
Currently, there are NO, ZERO, NONE, utilities or consistent fixes for soft bricked devices. This is not good, as currently there are several things that can soft brick this device.
Click to expand...
Click to collapse
Safestrap! Safestrap!
http://forum.xda-developers.com/showthread.php?t=2556677
Firstly, this was posted before SafeStrap. Plus, I highly doubt even Hashcode would recommend new users mess with SafeStrap right now. I'm by no means a master developer, but I've been around a long time & I've participated in some pretty cool low level hacking with some of the old timers & I'll be the first to say that there is some funky stuff going on in the HDX. Amazon has not exactly gone out of their way to make modding safe or easy. Plus there's not a whole lot out there yet that requires an custom recovery. It may be fine for you or I, but it can open a whole other host of issues if used improperly.
Sent from my KFJWA using XDA Premium HD app
Hey there I am new to this forums! Got a kindle yesterday (as a gift) and moved straight to xda to see what's cooking unfortunately I was a bit disappointed because there is no "cooking" at all. I hope this has to do with the fact that it's a new device and nobody has tried to make some roms for it yet... Nevertheless I am quite happy with it, although this fire os is a pretty pain in the eyes. Thank God I have managed to get the YouTube app sync with my Google account, plus some other gapps like drive. Well that's it for the moment, I just didn't want to make a new thread so I posted in here. So what do you think, will there be some good roms for this device? And/or maybe we could use those for the kindle fire hd?
Sent from beneath my cloak of magic
Thanks for the info I'm super new at this but was thinking buying one of these. But now that I am acquainted with Flashing ROMs and stuff it's sort of a deal breaker if it's not being done. If I can't modify it, whats the point?
HDX rooting?
I bought a Fire HDX 7" to replace a Nook HD+ for better HW. I thought I read you could root it or at least get the google play store on it, but it appears that is not the case. I guess I misunderstood what I read. Really disappointed now.
Any new news on rooting these things?
blackfox003 said:
I bought a Fire HDX 7" to replace a Nook HD+ for better HW. I thought I read you could root it or at least get the google play store on it, but it appears that is not the case. I guess I misunderstood what I read. Really disappointed now.
Any new news on rooting these things?
Click to expand...
Click to collapse
Patience good people. Each day a few qualified devs get a little closer ... all on their own free time. A crack might be right around the corner.
Well, it's almost June and development for the Kindle tablets seem to still be very slow, what's the story?
blackfox003 said:
I bought a Fire HDX 7" to replace a Nook HD+ for better HW. I thought I read you could root it or at least get the google play store on it, but it appears that is not the case. I guess I misunderstood what I read. Really disappointed now.
Any new news on rooting these things?
Click to expand...
Click to collapse
You can get root and the Google Play Store on an older firmware, just not any of the newest couple. Yet (I hope).
Good to go: I was able to use hdx-toolkit with my router blocking
Hey everyone.
In case this helps, I was able to ensure that my kindle didn't update by blocking all Internet access at my firewall (Verizon FiOS router) for the device. I looked up its MAC address under "Wireless" -> "Wi-Fi" and configured a rule to block all access.
I confirmed my device version via Apps -> Settings -> System Updates -> Current Version: 13.3.1.0 (factory fresh!)
Then, using my PC I ran the hdx-toolkit 0.94 and after resolving an initial snag (the toolkit couldn't access my device) I was able to do steps 1 (driver), 5 (check if rooted which also checks connectivity), 8 (towelroot), 2 (SuperSU), 5 (confirm root), 4 (block OTA) from the toolkit menu.
Note, the toolkit doesn't want to run from a network share. I copied it down onto my computer's local hard disk first.
My specific issue preventing the ADB setup was I didn't realize the Microsoft driver (to make the device show up as a USB phone device) was blocking the ADB driver from coming up. After uninstalling the Microsoft driver (under device manager - Portable devices for the device "kindle") and installing the device driver for Android Composite ADB Interface, I was able to get the ADB driver to install without error. Symptom of the driver conflict was the end of the installer sequence said "driver not installed correctly or need to reboot".
I am using Windows 8 on a Dell desktop
sabasc said:
Hey everyone.
In case this helps, I was able to ensure that my kindle didn't update by blocking all Internet access at my firewall (Verizon FiOS router) for the device. I looked up its MAC address under "Wireless" -> "Wi-Fi" and configured a rule to block all access.
I confirmed my device version via Apps -> Settings -> System Updates -> Current Version: 13.3.1.0 (factory fresh!)
Then, using my PC I ran the hdx-toolkit 0.94 and after resolving an initial snag (the toolkit couldn't access my device) I was able to do steps 1 (driver), 5 (check if rooted which also checks connectivity), 8 (towelroot), 2 (SuperSU), 5 (confirm root), 4 (block OTA) from the toolkit menu.
Note, the toolkit doesn't want to run from a network share. I copied it down onto my computer's local hard disk first.
My specific issue preventing the ADB setup was I didn't realize the Microsoft driver (to make the device show up as a USB phone device) was blocking the ADB driver from coming up. After uninstalling the Microsoft driver (under device manager - Portable devices for the device "kindle") and installing the device driver for Android Composite ADB Interface, I was able to get the ADB driver to install without error. Symptom of the driver conflict was the end of the installer sequence said "driver not installed correctly or need to reboot".
I am using Windows 8 on a Dell desktop
Click to expand...
Click to collapse
I'm sorry I missed this. Great advise though.
A default Microsoft driver was blocking the Amazon ADB driver from coming up. After uninstalling the Microsoft driver (under device manager - Portable devices for the device "kindle") and installing the device driver for Android Composite ADB Interface, I was able to get the ADB driver to install. --Win8/Win8.1
Click to expand...
Click to collapse
The toolkit needs to be run locally because well the adb connection won't go through your share to your computer.
GSLEON3 said:
Guy's the HDX is a fairly new device, the complete line has not even begun shipping yet & development is in it's infancy.
Currently, you can root your device, but it is HIGHLY recommended that you WAIT.
Currently, there are NO, ZERO, NONE, utilities or consistent fixes for soft bricked devices. This is not good, as currently there are several things that can soft brick this device.
In no circumstances should you do any of the following:
Remove apps or any files from the system folder or any sub-directory.
Restore previous veersions of Kindle apps from a Fire HD.
Make any modifications to any of the build.prop settings, or add any lines to the build.prop
Working but not advised at this time:
Adding any files or apks to the system partition or any sub-directory
There are numerous instances of modifications causing bootloops, soft bricks & KILLING ADB access. To my knowledge, I am the only person that has successfully recovered ADB access & for all the money in the world, I could not tell you how.
If you are not extremely proficient with reverse engineering software, or you don't know all the relevant ADB commands because you have been hacking devices for years, I STRONGLY suggest you wait to even root until further development progress has been made.
If you ignore this warning, you are likely going to be on your own in trying fix it, or you may be waiting months for a consistent fix to be found.
If you like taking risk & tinkering & you like to burn hundred dollar bills just for the pretty orange flame, well, by all means, go right ahead. Just realize right now, there may not ever be a recovery for your particular dilemma & in all likelihood by ignoring this warning, you've already made your warranty null & void.
Click to expand...
Click to collapse
Is this still the case? Just wondering if this thread needs to be updated because some of what's written here seem to contradict what I've read people are doing with their hdx.
my 8.9HD ver. 8.5.1
Is my kindle an HDX?
ant17 said:
Is my kindle an HDX?
Click to expand...
Click to collapse
No, you can find anything related to your kindle here
Hello,
Just to make sure I understood all the info published around:
A Kindle Fire HDX running FireOS 4.5.2 cannot be brought to a state where it can be jailbroken and and alternate ROM installed.
Even the downgrade performed by Amazon operators is to a version too high to allow jailbreaking and installing other ROM.
Am I correct with this assessment?
hfpop said:
Hello,
Just to make sure I understood all the info published around:
A Kindle Fire HDX running FireOS 4.5.2 cannot be brought to a state where it can be jailbroken and and alternate ROM installed.
Even the downgrade performed by Amazon operators is to a version too high to allow jailbreaking and installing other ROM.
Am I correct with this assessment?
Click to expand...
Click to collapse
to an extent yes,most custom roms cannot be installed but if you rolled back you can still root and instal the hdx nexus 2.0.2 rom which is pretty much most of what the device needs
@Davengerr: I understand that I can rollback to 3.2.8 and need at most 3.2.6 to install nexus 2.0.2. No?
hfpop said:
@Davengerr: I understand that I can rollback to 3.2.8 and need at most 3.2.6 to install nexus 2.0.2. No?
Click to expand...
Click to collapse
i have it on 3.2.7 on my device and this here lists what you can do with a 3.2.8
http://forum.xda-developers.com/kin...o-13-3-2-7-t2993089/post58150015#post58150015
@Davengerr: Thank you. All worked out greatly.
I have tried numerous things with the HDX to get it rooted again, SuperOneClick and numerous other one click root applications that failed, of course. The best way to get root, I figured, is to downgrade the OS. I have the .BIN file and, as the Amazon website states (for upgrade, of course) that we must stick it to internal storage, then do the usual upgrade business. However, the downgrade doesn't work. The is a file somewhere on the system that prevents it, and I wonder if we could find it and delete it, using the PC if necessary. Thanks for your cooperation.
ferrouskid said:
I have tried numerous things with the HDX to get it rooted again, SuperOneClick and numerous other one click root applications that failed, of course. The best way to get root, I figured, is to downgrade the OS. I have the .BIN file and, as the Amazon website states (for upgrade, of course) that we must stick it to internal storage, then do the usual upgrade business. However, the downgrade doesn't work. The is a file somewhere on the system that prevents it, and I wonder if we could find it and delete it, using the PC if necessary. Thanks for your cooperation.
Click to expand...
Click to collapse
I'm just curious as to if you never had root or lost root.
zXiC said:
I'm just curious as to if you never had root or lost root.
Click to expand...
Click to collapse
Yes I did have root, I used AOSP ROM, and made it almost pure android. I found a nice tool called "Android Commander" that has the ability to access the system files from the pc. I was attempting to flash the previous version of Mojito OS using the casebook utility but failed, and as far as I figured I might just be able to extract and maybe delete the file the check for automatic updates, and thus do a manual update on the kindle, which literally requires dropping in the .BIN file into internal storage and the lb upgrade it. Then use the old root method, so if you are interested you could help me locate that file
Kindle Fire HDX 7" 3rd Generation
Fire OS 4.5.5
Rooted Stock ROM
So here's where I'm at:
I'm stuck in the Settings screen, still have root access, but have no on screen buttons to get out or even open up a home replacement.
Here's every step I can think of since Rooting & junk using several XDA Forums
-Rooted w/ KingRoot
-Installed Gapps w/ no problems
-Changed Names(Not Delete) of the System files using ES File Explorer
-com.amazon.otaverifier
-com.amazon.settings.systemupdates &
-com.amazon.device.software.ota) using ES File Explorer
-Froze Ads app (com.amazon.kindle.kso)
THEN My Battery died last night, Recharged at work this morning and got stuck in boot loop. I should have stopped right there and come to the forums, but like an idiot, I hit reset to factory, foolishly thinkin "hey, that KingRoot was easy enough, I'll root it by lunch time and be good to go"...
I have attempted everything I can think of and can't seem find a solution anywhere, but here's the basics of what I've done so far to try and fix...
1) Installed Nova Launcher in ADB to bypass the Kindle launcher loop but I have NO BUTTONS on my screen to bring up the app selector for "Default Launcher".
2) Used ADB Command to force a Home Key Press with no luck, which leads me to believe the Launcher App isn't running at all?
3) Attempted to Install missing Amazon .apks, and run them using ADB
4) Installing new Launcher, attempt to Force run through command to start Launcher/Home. No luck
5)The last attempt at fixing this thing was using THIS Tutorial to get back to a Stock Fire OS, so I could just start from scratch, but clearly, I have changed the names of the apps letting me do so, as well as had failure to write/copy to my Kindle because it said "permission denied", which I don't understand having root access otherwise...
KingRoot is still installed after Factory Reset as well, so it's still rooted?
I apologize, that's a lot of info, but I figured the most details I can throw out there from the start, might help pinpoint or help find a solution. And Yes, I have scoured XDA for hours for fixes with no results.
Thanks ahead of time everyone!
Mcfinnipoop said:
Kindle Fire HDX 7" 3rd Generation
Fire OS 4.5.5
Rooted Stock ROM
So here's where I'm at:
I'm stuck in the Settings screen, still have root access, but have no on screen buttons to get out or even open up a home replacement.
Here's every step I can think of since Rooting & junk using several XDA Forums
-Rooted w/ KingRoot
-Installed Gapps w/ no problems
-Changed Names(Not Delete) of the System files using ES File Explorer
-com.amazon.otaverifier
-com.amazon.settings.systemupdates &
-com.amazon.device.software.ota) using ES File Explorer
-Froze Ads app (com.amazon.kindle.kso)
THEN My Battery died last night, Recharged at work this morning and got stuck in boot loop. I should have stopped right there and come to the forums, but like an idiot, I hit reset to factory, foolishly thinkin "hey, that KingRoot was easy enough, I'll root it by lunch time and be good to go"...
I have attempted everything I can think of and can't seem find a solution anywhere, but here's the basics of what I've done so far to try and fix...
1) Installed Nova Launcher in ADB to bypass the Kindle launcher loop but I have NO BUTTONS on my screen to bring up the app selector for "Default Launcher".
2) Used ADB Command to force a Home Key Press with no luck, which leads me to believe the Launcher App isn't running at all?
3) Attempted to Install missing Amazon .apks, and run them using ADB
4) Installing new Launcher, attempt to Force run through command to start Launcher/Home. No luck
5)The last attempt at fixing this thing was using THIS Tutorial to get back to a Stock Fire OS, so I could just start from scratch, but clearly, I have changed the names of the apps letting me do so, as well as had failure to write/copy to my Kindle because it said "permission denied", which I don't understand having root access otherwise...
KingRoot is still installed after Factory Reset as well, so it's still rooted?
I apologize, that's a lot of info, but I figured the most details I can throw out there from the start, might help pinpoint or help find a solution. And Yes, I have scoured XDA for hours for fixes with no results.
Thanks ahead of time everyone!
Click to expand...
Click to collapse
Appears you have done your homework and have tried most of the solutions I might have suggested. FireOS is intolerant of component name/permission changes (aside from one file dealing with OTA). Best option is to contact Amazon for a one time courtesy exchange if still in warranty.
As a last ditch effort you could try installing Safestrap v4 via adb. If you can get the recovery component installed (requires launching the installed Safestrap app) you *might* be able to flash another rom or repair FireOS. Long shot at best that could leave you with a brick. If you go this path know a factory reset/restore from the native recovery menu *will* brick the device (so don't do that).
Sorry for the bleak prognosis.
Davey126 said:
Appears you have done your homework and have tried most of the solutions I might have suggested. FireOS is intolerant of component name/permission changes (aside from one file dealing with OTA). Best option is to contact Amazon for a one time courtesy exchange if still in warranty.
As a last ditch effort you could try installing Safestrap v4 via adb. If you can get the recovery component installed (requires launching the installed Safestrap app) you *might* be able to flash another rom or repair FireOS. Long shot at best that could leave you with a brick. If you go this path know a factory reset/restore from the native recovery menu *will* brick the device (so don't do that).
Sorry for the bleak prognosis.
Click to expand...
Click to collapse
Thanks man. Yeah, I'm not new to the whole rooting/linux thing, however KINDLE FIRE OS IS The most garbage version of Android I've ever dealt with. I read numerous warnings about bricking, but decided to try anyways.
I tried many more things last night and actually had some luck with pushing commands through ADB to start ES File Explorer from the settings screen, I was able to open apps through ES and manged to get a lot done, however I couldn't get the softkeys/ui keys to appear no matter what I did.
I could power the screen down and it would open back up to ES or whatever App I had opened before "locking" the screen, but Once again I hit a Wall. I checked it this morning, and somehow I got stuck at a black screen when I hit the power button, and now Im stuck in recovery with no option to fastboot.
The Fire is recognized as "Fire" in Device Manager, however I can't seem to get it recognized in ADB to use a Recovery tool or push the Stock OTA rom to the system.
Is there any way of accessing ADB, or enabling USB via Recovery screen?
OR is there a tool similar to ODIN I can use to rebuild, fix up my current OS using adb or usb as mentioned above?
Mcfinnipoop said:
Thanks man. Yeah, I'm not new to the whole rooting/linux thing, however KINDLE FIRE OS IS The most garbage version of Android I've ever dealt with. I read numerous warnings about bricking, but decided to try anyways.
I tried many more things last night and actually had some luck with pushing commands through ADB to start ES File Explorer from the settings screen, I was able to open apps through ES and manged to get a lot done, however I couldn't get the softkeys/ui keys to appear no matter what I did.
I could power the screen down and it would open back up to ES or whatever App I had opened before "locking" the screen, but Once again I hit a Wall. I checked it this morning, and somehow I got stuck at a black screen when I hit the power button, and now Im stuck in recovery with no option to fastboot.
The Fire is recognized as "Fire" in Device Manager, however I can't seem to get it recognized in ADB to use a Recovery tool or push the Stock OTA rom to the system.
Is there any way of accessing ADB, or enabling USB via Recovery screen?
OR is there a tool similar to ODIN I can use to rebuild, fix up my current OS using adb or usb as mentioned above?
Click to expand...
Click to collapse
Sorry - afraid I can't be of much help. The latest situation is not uncommon after a reboot on a borked device. There is no way to enable adb via stock recovery; would be a security risk even if available. Amazon devices are unique beasts; many common recovery tools/techniques don't work due to component selection and a restrictive bootloader. Even if you did regain limited control pushing an OTA image via ADB would not cause it to be processed as you would need a higher version of FireOS than what's already on your device (4.5.5.1); none exist at present aside from v5. With one exception lower (rollback) versions are summarily dismissed.
Mcfinnipoop said:
Kindle Fire HDX 7" 3rd Generation
Fire OS 4.5.5
Rooted Stock ROM
So here's where I'm at:
I'm stuck in the Settings screen, still have root access, but have no on screen buttons to get out or even open up a home replacement.
Here's every step I can think of since Rooting & junk using several XDA Forums
-Rooted w/ KingRoot
-Installed Gapps w/ no problems
-Changed Names(Not Delete) of the System files using ES File Explorer
-com.amazon.otaverifier
-com.amazon.settings.systemupdates &
-com.amazon.device.software.ota) using ES File Explorer
-Froze Ads app (com.amazon.kindle.kso)
THEN My Battery died last night, Recharged at work this morning and got stuck in boot loop. I should have stopped right there and come to the forums, but like an idiot, I hit reset to factory, foolishly thinkin "hey, that KingRoot was easy enough, I'll root it by lunch time and be good to go"...
I have attempted everything I can think of and can't seem find a solution anywhere, but here's the basics of what I've done so far to try and fix...
1) Installed Nova Launcher in ADB to bypass the Kindle launcher loop but I have NO BUTTONS on my screen to bring up the app selector for "Default Launcher".
2) Used ADB Command to force a Home Key Press with no luck, which leads me to believe the Launcher App isn't running at all?
3) Attempted to Install missing Amazon .apks, and run them using ADB
4) Installing new Launcher, attempt to Force run through command to start Launcher/Home. No luck
5)The last attempt at fixing this thing was using THIS Tutorial to get back to a Stock Fire OS, so I could just start from scratch, but clearly, I have changed the names of the apps letting me do so, as well as had failure to write/copy to my Kindle because it said "permission denied", which I don't understand having root access otherwise...
KingRoot is still installed after Factory Reset as well, so it's still rooted?
I apologize, that's a lot of info, but I figured the most details I can throw out there from the start, might help pinpoint or help find a solution. And Yes, I have scoured XDA for hours for fixes with no results.
Thanks ahead of time everyone!
Click to expand...
Click to collapse
ok this may sound silly but there were 2 things i did to fix a friends kindle stuck on the settings screen as u describe, I went to applications and under that went to the default silk web browser then to most visited , and yahoo link which allowed me to get to the internet and download and install custom notification apk can be found here https://globalapk.co/apk/1/9085-custom-notification-ex-v221 from there it opened and i was able to place the alternate launcher i had adb installed as a shortcut in notification area which allowed me to navigate, and open the alternate launcher and had some control on device, I also think that simply going to an apk site you trust and installing an alternate launcher like that should also work it should pop right up after install depending on how bad your situation is or what was done with the specific kindle, just thought id give some suggestions for alternate way to perhaps fix it gain control over system again it may not work though, hope that helps.
Hopefully this will work
Not sure you have this working yet but I had the same issue, spend most of Saturday trying to fix it, and finally did.
Hopefully the below will help
First need to download cm 11 and gapps on you pc
If you have 7” inch you need the Thor things
Cm 11: Thor ROM http://click.xda-developers.com/api...Amazon Kindle Fire HDX 7" & 8.9"&txt=Thor ROM
Gapps: http://opengapps.org (remember take the 4.4 apps)
Check md 5 hashes on both files
I renamed my files cm-11.zip and gapps.zip
The copied them into my adb folder and
adb push gapps.zip /sdcard/Download
adb push cm-11.zip /sdcard/Download
Once this is done we need to launch silk via adb so
adb shell am start -n com.amazon.cloud9/.browsing.BrowserActivity
We then need to get SuperSU installed I went too
http://www.apkmirror.com/wp-content/themes/APKMirror/download.php?id=64309
Download and then you should get the dialog to install, you should get the pop-up to open once it installs do this. You should get the kingroot pop-up to give it root access obviously click grant/yes.
Once this is done, go to settings menu on the Kindle (which you should still be able to get too. ) then apps, all apps, then uninstall kingroot.
Now we need to get to silk again so on your PC
adb shell am start -n com.amazon.cloud9/.browsing.BrowserActivity
Next we need to get safestrap
Link to the Thor apk
http://click.xda-developers.com/api...dle Fire HDX 7" & 8.9"&txt=Safestrap for THOR
Do the same as SuperSU install, then open through the pop-up
Accept the root pop up
Then click on install recovery, then reboot to recovery
Now fingers crossed it should reboot into safestrap recovery.
Do the normal ROM install (wipe, install cm-11.zip from the /sdcard/Download, same with gapps, wipe cache/dalvik)
Then reboot and keep everything crossed and it should boot to cm-11.
Sorry about the poor write up as I have Ms and today is not a good day.
Really hope this helps and works. Cm-11 is buttery smooth on the hdx.
trinityschild said:
Not sure you have this working yet but I had the same issue, spend most of Saturday trying to fix it, and finally did.
Hopefully the below will help
First need to download cm 11 and gapps on you pc
If you have 7” inch you need the Thor things
Cm 11: Thor ROM http://click.xda-developers.com/api...Amazon Kindle Fire HDX 7" & 8.9"&txt=Thor ROM
Gapps: http://opengapps.org (remember take the 4.4 apps)
Check md 5 hashes on both files
I renamed my files cm-11.zip and gapps.zip
The copied them into my adb folder and
adb push gapps.zip /sdcard/Download
adb push cm-11.zip /sdcard/Download
Once this is done we need to launch silk via adb so
adb shell am start -n com.amazon.cloud9/.browsing.BrowserActivity
We then need to get SuperSU installed I went too
http://www.apkmirror.com/wp-content/themes/APKMirror/download.php?id=64309
Download and then you should get the dialog to install, you should get the pop-up to open once it installs do this. You should get the kingroot pop-up to give it root access obviously click grant/yes.
Once this is done, go to settings menu on the Kindle (which you should still be able to get too. ) then apps, all apps, then uninstall kingroot.
Now we need to get to silk again so on your PC
adb shell am start -n com.amazon.cloud9/.browsing.BrowserActivity
Next we need to get safestrap
Link to the Thor apk
http://click.xda-developers.com/api...dle Fire HDX 7" & 8.9"&txt=Safestrap for THOR
Do the same as SuperSU install, then open through the pop-up
Accept the root pop up
Then click on install recovery, then reboot to recovery
Now fingers crossed it should reboot into safestrap recovery.
Do the normal ROM install (wipe, install cm-11.zip from the /sdcard/Download, same with gapps, wipe cache/dalvik)
Then reboot and keep everything crossed and it should boot to cm-11.
Sorry about the poor write up as I have Ms and today is not a good day.
Really hope this helps and works. Cm-11 is buttery smooth on the hdx.
Click to expand...
Click to collapse
This is a nice write-up that will likely help someone in a similar situation. Thanks for posting
You can help me?
trinityschild said:
Not sure you have this working yet but I had the same issue, spend most of Saturday trying to fix it, and finally did.
Hopefully the below will help
First need to download cm 11 and gapps on you pc
If you have 7” inch you need the Thor things
Cm 11: Thor ROM http://click.xda-developers.com/api...Amazon Kindle Fire HDX 7" & 8.9"&txt=Thor ROM
Gapps: http://opengapps.org (remember take the 4.4 apps)
Check md 5 hashes on both files
I renamed my files cm-11.zip and gapps.zip
The copied them into my adb folder and
adb push gapps.zip /sdcard/Download
adb push cm-11.zip /sdcard/Download
Once this is done we need to launch silk via adb so
adb shell am start -n com.amazon.cloud9/.browsing.BrowserActivity
We then need to get SuperSU installed I went too
http://www.apkmirror.com/wp-content/themes/APKMirror/download.php?id=64309
Download and then you should get the dialog to install, you should get the pop-up to open once it installs do this. You should get the kingroot pop-up to give it root access obviously click grant/yes.
Once this is done, go to settings menu on the Kindle (which you should still be able to get too. ) then apps, all apps, then uninstall kingroot.
Now we need to get to silk again so on your PC
adb shell am start -n com.amazon.cloud9/.browsing.BrowserActivity
Next we need to get safestrap
Link to the Thor apk
http://click.xda-developers.com/api...dle Fire HDX 7" & 8.9"&txt=Safestrap for THOR
Do the same as SuperSU install, then open through the pop-up
Accept the root pop up
Then click on install recovery, then reboot to recovery
Now fingers crossed it should reboot into safestrap recovery.
Do the normal ROM install (wipe, install cm-11.zip from the /sdcard/Download, same with gapps, wipe cache/dalvik)
Then reboot and keep everything crossed and it should boot to cm-11.
Sorry about the poor write up as I have Ms and today is not a good day.
Really hope this helps and works. Cm-11 is buttery smooth on the hdx.
Click to expand...
Click to collapse
I try to do what you write in this tutorial. But when i reboot in recovery after i installed the safetrap, my kindle go reboot, and display kindle fire for a long, and nothing happen.
Another problem, when i instal de supersu, after i try to remove kingroot and not work, i have only force stop, clear data and clear cache allowed to press.
Thank you
Hello Mcfinnipoop,
I encountered the same problem as you, have you resolved the problem yet? I would appreciate it if you could tell me how to fix it.
Thanks!
VoadekS said:
I try to do what you write in this tutorial. But when i reboot in recovery after i installed the safetrap, my kindle go reboot, and display kindle fire for a long, and nothing happen.
Another problem, when i instal de supersu, after i try to remove kingroot and not work, i have only force stop, clear data and clear cache allowed to press.
Thank you
Click to expand...
Click to collapse
trinityschild said:
Not sure you have this working yet but I had the same issue, spend most of Saturday trying to fix it, and finally did.
Hopefully the below will help
First need to download cm 11 and gapps on you pc
If you have 7” inch you need the Thor things
Cm 11: Thor ROM http://click.xda-developers.com/api...Amazon Kindle Fire HDX 7" & 8.9"&txt=Thor ROM
Gapps: http://opengapps.org (remember take the 4.4 apps)
Check md 5 hashes on both files
I renamed my files cm-11.zip and gapps.zip
The copied them into my adb folder and
adb push gapps.zip /sdcard/Download
adb push cm-11.zip /sdcard/Download
Once this is done we need to launch silk via adb so
adb shell am start -n com.amazon.cloud9/.browsing.BrowserActivity
We then need to get SuperSU installed I went too
http://www.apkmirror.com/wp-content/themes/APKMirror/download.php?id=64309
Download and then you should get the dialog to install, you should get the pop-up to open once it installs do this. You should get the kingroot pop-up to give it root access obviously click grant/yes.
Once this is done, go to settings menu on the Kindle (which you should still be able to get too. ) then apps, all apps, then uninstall kingroot.
Now we need to get to silk again so on your PC
adb shell am start -n com.amazon.cloud9/.browsing.BrowserActivity
Next we need to get safestrap
Link to the Thor apk
http://click.xda-developers.com/api...dle Fire HDX 7" & 8.9"&txt=Safestrap for THOR
Do the same as SuperSU install, then open through the pop-up
Accept the root pop up
Then click on install recovery, then reboot to recovery
Now fingers crossed it should reboot into safestrap recovery.
Do the normal ROM install (wipe, install cm-11.zip from the /sdcard/Download, same with gapps, wipe cache/dalvik)
Then reboot and keep everything crossed and it should boot to cm-11.
Sorry about the poor write up as I have Ms and today is not a good day.
Really hope this helps and works. Cm-11 is buttery smooth on the hdx.
Click to expand...
Click to collapse
It works for me. Thanks!
Hello ive not done any guides before but since i had to search all over to try find out what i was looking for and stumbled across a lot of good information and thought id share it. None of this was my findings but there isn't anything clear on how to actually accomplish this on a Fire stick.
Im going to attempt to share how i have managed.
This guide assumes you already know how to transfer files to your stick.
First off, current Fire stick os is 5.2.1.0 and is rootable with Kingoroot.
https://root-apk.kingoapp.com
1. Download Kingoroot and ADB to your Fire stick, do this whichever way you normally get apk/files onto your Fire stick.
2. Download Kingoroot superuser and ADB to your Fire stick.
3. Run the Kingoroot tool and let it finish, when you have root, install Kingo roots Superuser. (If you install this before rooting it wont make any difference).
Now you should have a rooted Fire stick on 5.2.1.0 with Kingoroots SuperUser.
Now its time to downgrade your Fire stick. This file was provided by AFTVnews over at another thread and cuki3r3k83bln accomplished downgrade on the thread also so please leave thanks for them as before he posted the file and information i had no idea it was possible. Im suggesting to download the 5.0.5 file as i did because this was when firestarter worked with home button detection.
Download Fire Stick os 5.0.5
http://amzdigitaldownloads.edgesuit...te-kindle-montoya-54.5.3.7_user_537174420.bin
Once you have it downloaded rename the downloaded file to update.bin.
Im going to explain how i did it, i know there is many other variations on how to accomplish this and im not too familiar with adb commands but the way i will show is the way it worked for me.
We need to transfer the downloaded and renamed update.bin to the Fire stick so if you would like to transfer it with apps to fire or through command or any other variation thats fine but ill show commands used from windows laptop using adbLink.
Please note, if your using a different method to transfer you will have to slightly modify step 5 on where your update.bin is stored so cd /sdcard/download. if your update.bin is stored in download folder.
Another note is to make sure your file name is correct, mine was named update.bin.bin rather than update.bin this was fine just make sure to name it correctly or you will have to modify step 6 and step 8.
1. Open up adbLink and connect your device.
2. Push the update.bin to the sdcard. (this takes quite alot of time as your pushing 311mb file so be patient)
3. Once pushed you need to open up ADB Shell.
4. Run the command: su
5. Run the command: cd /sdcard
6. Run the command: mv ./update.bin /cache/
If you get an error about no space on device do the following:
Run the command rm -f /cache/*.bin
Run the command rm -f /cache/*.zip
Run the command exit
Run the command exit then reopen ADB Shell in adbLink repeat step 6.
7. Run the command cd /cache/recovery
8. Run the command echo --update_package=/cache/update.bin > command
9. Run the command reboot recovery
Your Fire stick should automatically start the downgrade and take 10 minutes or so.
As soon as its finished go back to your Kingoroot app and re-root your Fire stick. Then block updates (method 1) using AFTVnews guide at:
http://www.aftvnews.com/how-to-block-software-updates-on-the-amazon-fire-tv-or-fire-tv-stick/
You should now be on 5.0.5 rooted and have updates blocked
All your apps should be still intact. Make sure you uninstall appstarter/firestopper and reinstall firestarter 3.2.3 (if you use it)
Then follow AFTVnews guide on how to re-enable it here:
http://www.aftvnews.com/how-to-cont...v-and-fire-tv-stick-software-version-5-0-5-1/
Please give the credit deserved to @AFTVnews.com and @cuki3r3k83bln
Its suggested all over to hold off before doing anything that could brick the device until rbox releases a recovery.
Please do not use any type of Su modifying tool/script/apk eg: SuperSume as these do not work and you will end up with a small brick.
Also its been pointed out to me by @deanr1977 that if your going to use this guide and decide to update Fire Stick os in the future, it maybe safer to unroot it first.
With that out of the way please excuse the bad layout of the guide as im no expert and would like to just share my experience.
Would I be able to go back to 5.2.1.0 once custom recovery and rom is released?
FireTho1 said:
Would I be able to go back to 5.2.1.0 once custom recovery and rom is released?
Click to expand...
Click to collapse
i cant see any reason why not, either grab the 5.2.1.0 .bin file and follow the guide using that or let it automatically update after re-enabling updates.
Are there any reasons for downgrading to 5.0.5? Does it have any advantages?
Bierfreund said:
Are there any reasons for downgrading to 5.0.5? Does it have any advantages?
Click to expand...
Click to collapse
As far as im aware upto now, it seems that Firestarter home button detection works as it should, and firmware after this Firestarter will not work with home button detection.
Which is a big thing for me personally as i only use Firestick for netflix and kodi and its much easier to launch from within Firestarter.
Its good to know that the process of upgrading/downgrading is applicable to Fire stick as you never know what Amazon will try to take from you.
You sir are my hero. Kudos for the tutorial!
sconnyuk said:
i cant see any reason why not, either grab the 5.2.1.0 .bin file and follow the guide using that or let it automatically update after re-enabling updates.
Click to expand...
Click to collapse
Its not recommended to let it auto update from root, unroot first then re-enable the update progress.
Also please can you note in your guide that its not recommended to try to swap the Su for Chainfires Su with the Super Sume or Super Sumepro app because so many people on this forum have bricked with this method & if any new users try your way & after want to unroot/swap method after the first boot they could have a non working device.
Ive not tried this guide myself (i dont need too) but if its working fine this info would be good to have here.
deanr1977 said:
Its not recommended to let it auto update from root, unroot first then re-enable the update progress.
Also please can you note in your guide that its not recommended to try to swap the Su for Chainfires Su with the Super Sume or Super Sumepro app because so many people on this forum have bricked with this method & if any new users try your way & after want to unroot/swap method after the first boot they could have a non working device.
Ive not tried this guide myself (i dont need too) but if its working fine this info would be good to have here.
Click to expand...
Click to collapse
Fair point about pointing out about the brickable and dangerous su swapping methods with supersu me etc.
I will add a mention about it after the line that reads:
'Its suggested all over to hold off before doing anything that could brick the device until rbox releases a recovery.'
As for not recommended to auto update while rooted, ive had 2 sticks and a Fire Tv 2 auto update from 5.0.5 to 5.0.5.1 and then to 5.2.1.0 when my router was reset, (im sure im not the only one from what ive read either).
But since im a helping type of guy ill add this also.
Ok mate, just going by what's been said from the AFTVNews & Amazon Firestick forums. Glad you are including this thanks, Its just some only skim through the threads & read only the parts they want to so if this is included it may cut down on the "I've bricked my Amazon device please help threads" which clog up the forum.
Sent from my SM-G900F using Tapatalk
i'm trying to downgrade to the point where display mirroring worked on windows devices, this is before 5.0.5, can i use this method to downgrade to another bin before 5.0.5?
sins07 said:
i'm trying to downgrade to the point where display mirroring worked on windows devices, this is before 5.0.5, can i use this method to downgrade to another bin before 5.0.5?
Click to expand...
Click to collapse
Id take a stab and say if your stick originally came with a firmware below 5.0.5 but I honestly do not know as ive not tried but I cant see why it wouldnt work. You can go from 5.2.1.0 to 5.0.5.1 or to 5.0.5 so id imagine so.
What features have been removed by 5.0.5? Im interested myself and may try this myself if there is features I could use.
Amazing! I can't believe this was hard to find as all the news out there say you can only root the stick using a hardware mod.
I downgraded and rooted both my Sticks. Installed Firestarter 3.2.3, installed Seeder, removed unneeded processes from running and these things are super quick now. You still have to load the crappy slow Amazon launcher to keep the settings but oh well. Nicely done, now I hope a recovery option comes out and I can mess around further . Heatsink and overclocking anyone? lol
@vulcan4d recovery & prerooted rom is being worked on at the moment by rbox in this forum
Sent from my SM-G900F using Tapatalk
vulcan4d said:
Amazing! I can't believe this was hard to find as all the news out there say you can only root the stick using a hardware mod.
I downgraded and rooted both my Sticks. Installed Firestarter 3.2.3, installed Seeder, removed unneeded processes from running and these things are super quick now. You still have to load the crappy slow Amazon launcher to keep the settings but oh well. Nicely done, now I hope a recovery option comes out and I can mess around further . Heatsink and overclocking anyone? lol
Click to expand...
Click to collapse
Can I ask what processes you removed/stopped and how you accomplished this?
Id like to do the same on 2 of my sticks.
sconnyuk said:
Can I ask what processes you removed/stopped and how you accomplished this?
Id like to do the same on 2 of my sticks.
Click to expand...
Click to collapse
I would like to give credit to this post for removing unneeded services:
http://forum.xda-developers.com/fire-tv/help/root-disabling-apps-services-bloat-t3325333
I only found a few from the list but that list was meant for a Fire TV so I'm sure there is more running. Just launch ADB Shell in ADBFire/Link and type pm disable <service_name>
vulcan4d said:
I would like to give credit to this post for removing unneeded services:
http://forum.xda-developers.com/fire-tv/help/root-disabling-apps-services-bloat-t3325333
I only found a few from the list but that list was meant for a Fire TV so I'm sure there is more running. Just launch ADB Shell in ADBFire/Link and type pm disable <service_name>
Click to expand...
Click to collapse
Thanks ive disabled them as per the guide you linked to. Can I further ask what the program seeder does and whether to have it set to aggressive or not?
Thanks for the info.
@sconnyuk i've downgraded successfully kingo root'ed stick 5.2.1->5.0.5 . But funny thing was under root shell command "wipe data " .It wiped device clean but root still stays on . Got OTA disabled and my other king root 5.0.5 stick will have similar treatment .
nicefile said:
@sconnyuk i've downgraded successfully kingo root'ed stick 5.2.1->5.0.5 . But funny thing was under root shell command "wipe data " .It wiped device clean but root still stays on . Got OTA disabled and my other king root 5.0.5 stick will have similar treatment .
Click to expand...
Click to collapse
You will need to unroot it for root to go.
Kingoroot has the option to do this if its what you want.
You need mouse toggle for fire tv to navigate to the 'in app' menu icon if not plug fire stick into pc and run Windows version of Kingoroot to unroot.
Interesting, I just bought a 3rd Amazon stick to root. After running KingRoot, I've noticed I did not need to install KingUser at all. If you launch KingRoot again it allows you to launch KingoUser which is the same thing. I'm assuming that KingUser is just an updated version of what KingRoot already installs.
Sconnyuk, I checked all the boxes and chose Moderate. This was also mentioned in the XDA forums however sadly I cannot find the post anymore. Seeder is an application that has been around for a while which improves the response time on Android devices. There is a lot of technical details into how it works, but the point is the Amazon stick is not the fastest thing in the world and anything helps. Give it a try and see for yourself.
sconnyuk said:
Id take a stab and say if your stick originally came with a firmware below 5.0.5 but I honestly do not know as ive not tried but I cant see why it wouldnt work. You can go from 5.2.1.0 to 5.0.5.1 or to 5.0.5 so id imagine so.
What features have been removed by 5.0.5? Im interested myself and may try this myself if there is features I could use.
Click to expand...
Click to collapse
Miracast display mirroring became non-compliant with windows systems, it still works fine with android.
Hello Fire users
I am not really a newbie but until today I have worked only with Samsung devices.
My daughter got an Fire HD 6 in the christmas days and we started to play around and we have done all updates up to 5.3.1.1. But it's not running perfectly for my wishes. I have read thats it's possible to root the tablet incl. TWRP, xposed framework and go with this up to 5.3.1.1 but it's hard to read out what I have exactly to do because there are many warnings when to do something and when not.
Could you please help what to do exactly? ADB is running and phone is recognizing on Mac and Windows...
Thanks for your help ?
cuki3r3k83bln said:
Hello Fire users
I am not really a newbie but until today I have worked only with Samsung devices.
My daughter got an Fire HD 6 in the christmas days and we started to play around and we have done all updates up to 5.3.1.1. But it's not running perfectly for my wishes. I have read thats it's possible to root the tablet incl. TWRP, xposed framework and go with this up to 5.3.1.1 but it's hard to read out what I have exactly to do because there are many warnings when to do something and when not.
Could you please help what to do exactly? ADB is running and phone is recognizing on Mac and Windows...
Thanks for your help
Click to expand...
Click to collapse
From latest news, OS 5.3.1 can't be rooted(directly). You'll need to downgrade to 4.5.3, root, and go back to 5.3.1 as explained here
If you want to feel android experience, you can either install custom launcher and Play Store from here or just totally install Cyanogenmod 11 from here
Killa8 said:
From latest news, OS 5.3.1 can't be rooted(directly). You'll need to downgrade to 4.5.3, root, and go back to 5.3.1 as explained here
If you want to feel android experience, you can either install custom launcher and Play Store from here or just totally install Cyanogenmod 11 from here
Click to expand...
Click to collapse
@Killa8, as I mentioned HERE in more detail, the procedure for downgrading to 4.5.3 doesn't appear to be explained in the linked tutorial. Any help would be greatly appreciated! I'm trying to root and install CM on my daughter's tablets as they find Android to be far more intuitive than FireOS. Many thanks!!!
Downgrade to 4.5.3 and root as seen here (skip step 1): https://forum.xda-developers.com/fire-hd/general/how-to-downgrade-to-4-5-3-root-device-t3139351
Jump down to the 2nd post here: https://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950 and install TWRP on your device.
Then go to post 1 where it says "1) boot into TWRP, and, in a single session (!!!!!)" and follow the directions. MAKE SURE YOU USE THE RIGHT BOOTLOADERS!!
Enjoy rooted FireOS 5.3.1
RadRacer said:
Downgrade to 4.5.3 and root as seen here (skip step 1): https://forum.xda-developers.com/fire-hd/general/how-to-downgrade-to-4-5-3-root-device-t3139351
Jump down to the 2nd post here: https://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950 and install TWRP on your device.
Then go to post 1 where it says "1) boot into TWRP, and, in a single session (!!!!!)" and follow the directions. MAKE SURE YOU USE THE RIGHT BOOTLOADERS!!
Enjoy rooted FireOS 5.3.1
Click to expand...
Click to collapse
Thank you for this! I was having the same issue as the OP and this solved it.:good:
geoyou said:
Thank you for this! I was having the same issue as the OP and this solved it.:good:
Click to expand...
Click to collapse
Can you tell me how you installed TWRP? the 2nd post of the page is confusing to me.
NVM i found a video tutorial
I've seen too many threads mentioning 5.3.1 and implying that 5.3.1.1 is the same.
Even if that is the case, all the tutorials I have read left me scratching my head at various points. So here is a walkthrough of what I just went through to root my Kindle fire HD 6
It's now running 5.3.1.0 and will stay there for the time being (unless I can get solid answers on 5.3.1.1).
I started with this tutorial thread but I found it easy to make mistakes and I ended up bricking my device (fortunately the unbrick iso is very good and the tutorial video is excellent).
So here is my procedure. Doing this on Windows is probably less involved thanks to the bat file in one of the steps.
Start by getting the stuff you will need together.
You will need ROMs from here.
Specifically, the 4.5.3 and 5.3.1.0 ROMs.
The 4.5.3 file name is update-kindle-20.4.5.3_user_453011120.bin
The 5.3.1.0 file name is update-kindle-20.5.5.2_user_552153420.bin
Note: The version number on that second file makes no sense to me, and I made a mistake trying to flash the wrong one in TWRP. Here is the correct name for reference. You might change the file names to reflect the version number.
Go ahead and change the extension of the 5.3.1.0 bin file to zip instead. TWRP will need it this way.
Download the stock recovery image. There is a link at the bottom of the second post in the tutorial thread I linked above. Or you can just click here.
Grab the WindowsAutoTWRP_v03.zip from the tutorial thread (or click here).
It has the Windows ADB executable and drivers in it so it will save you some hassle on a Windows machine.
For Macs, I found a video from RootJunkie.com that linked to tools at http://rootjunkysdl.com/files/?dir=Adb%20Fastboot%20Files. I was able to do everything from my Mac with these.
As a side note, the video I found these on was https://www.youtube.com/watch?v=iv0VcNM8IAw, but it's not important to watch.
It will help to gather zips and APK files you will need right now as well.
Get a copy of ES file explorer, Kingroot (I used the APK, but if you have a windows system, it might be easier to use the Windows version instead), and an android launcher of some sort.
For additional images, you will need the following:
From the tutorial thread: make_space_v02.zip
Supersu.zip linked at https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
Xposed which if you follow the link from the tutorial through the forum thread should lead you here: http://dl-xda.xposed.info/framework/sdk22/arm/. I grabbed xposed-v87-sdk22-arm.zip
flash Pico (Uni) GAPPS for 5.1 which again, if you follow all the links, will take you here: https://basketbuild.com/filedl/devs?dev=osm0sis&dl=osm0sis/gapps/tk_gapps-modular-pico%28uni%29-5.1.1-20150920-signed.zip.
Make sure you have all the files gathered in one place, it's really helpful.
If you are using a Mac, you will also need Android File Transfer at https://www.android.com/filetransfer/.
Something optional that might help is a USB OTG cable or one of those USB drives that support USB OTG with its own micro USB connector. It's not necessary but it might help if you need to get files to your tablet in TWRP.
At this point, I'm going to go into Mac instruction mode. If you know that the Windows command prompt is sort of like the terminal application on OS X, that you don't use ./ path specifies on windows, etc, you should be able to come up with some
Once you have everything in place, shut down your Kindle Fire 6.
On your computer, open a terminal window and get to where you unzipped your ADB tools.
The simple way is to type cd followed by a space then drag the folder with your tools from finder to the terminal widow so you get something like cd /users/me/abd
The actual path will be dependent on your system.
This terminal window should remain open for the entire process. It will make life easier.
Hold volume up and turn the Kindle Fire on. You should enter recovery.
Back at your computer type ./adb devices
Your kindle should show up there. When it does, go back to your tablet and select "apply update from ADB".
Then, from the terminal, enter ./adb sideload 4.5.3 file name is update-kindle-20.4.5.3_user_453011120.bin
If you just type ./adb sideload then drag the file into the terminal window, it will fill the name and path out for you.
Note that this all seems kind of like the video I linked above but we are downgrading to 4.3.5 instead as the tutorial thread says we should.
Once that's done, you end up back at the recovery screen. I went ahead and did a wipe data/factory reset. I don't know if this is necessary though.
When you get into 4.5.3, you need to shut down wifi if you are not prompted through new device setup.
If you are prompted, just skip it.
You may need to enable debugging. Go to setting, device options, find the serial number field and tap it 7 times.
Open the now revealed developer console and toggle "enable ADB" so it's on.
Install the APKs you downloaded earlier.
Use ./adb install <name of ES file explorer apk>
If you're on Windows, you can go ahead and run the Windows root util.
If you are on a Mac, install the Kingroot APK using the ./adb install command.
If you go the APK route, Kingroot requires a wifi connection. This will expose you to Amazon's OTA updates. You will need to watch your Kindle carefully at this point.
The download with probably download but as long as you don't let it sleep, it should not reboot and install.
Kingroot may take a couple of tries to get root.
As soon as it does, turn off wifi!
After that, open ES file explorer, give it root permissions, then navigate to the root folder, then to cache. Look for a bin file there. If there is nothing, you didn't get the OTA update pushed to you. If you did, delete it. See post 5 in this thread: https://forum.xda-developers.com/kindle-fire-hdx/help/deleting-downloaded-update-t3100573
To prevent any OTA relapses until we can go further, use ES file explorer to rename /system/etc/security/otacerts.zip. I replaces the first o and last p with _ characters.
It should be safe to turn on wifi at this point.
If you deleted a bin file in /cache, you aren't out of the woods yet. The Kindle could still reboot on you and it will give you the red ! but I found booting into recovery then just rebooting the Kindle caused it to work itself out after a couple tries.
We should be good to go for TWRP at this point.
In the terminal type ./adb shell
When the shell opens type su
Grant the shell permissions on the Kindle
Type exit twice.
On a Mac, we cannot run the bat file included in the WindowsAutoTWRP_v03.zip file.
But here are the commands to enter manually:
./adb devices
./adb install gscript-android.apk
./adb shell "mkdir /sdcard/gscript"
./adb push gscript /sdcard/gscript/
./adb shell "cp /sdcard/gscript/flash_453_stay.sh /data/local/tmp/"
./adb shell "ls /data/local/tmp/"
./adb shell "su -c 'chmod 777 /data/local/tmp/flash_453_stay.sh'"
./adb shell "su -c 'sh /data/local/tmp/flash_453_stay.sh'"
Once complete open ES file explorer again
DELETE sdcard/gscripts/s5.4.1_113_stock_recovery_uboot.zip!!!!!!!
It's too easy to mistakenly flash this in TWRP and it WILL brick your kindle.
We will now copy those zip files we downloaded earlier onto the Kindle.
I used the Android file transfer unity to put them in the scripts folder but copying them to Downloads on the Kindle might be easier.
If you are a command line type of person, you can also use the adb push command.
You want to copy over the following:
The 5.3.1.0 file name is update-kindle-20.5.5.2_user_552153420.bin
5.5.2_1534_stock_recovery_uboot.zip
UPDATE-SuperSU-v2.46.zip (or whatever the current version you downloaded is)
make_space_v02.zip
xposed-v87-sdk22-arm.zip (or whatever the version you downloaded is. The version could have changed after I wrote this.)
tk_gapps-modular-pico(uni)-5.1.1-20150920-signed.zip (again, based on what version was available when you downloaded it)
It might be a good time to sideload that extra launcher you downloaded earlier. I didn't need it, but you might.
Again the command is ./adb install <apk file name>
In the terminal, type ./adb reboot recovery.
You *should* end up in TWRP.
These next steps are important to do in one go. Don't exit TWRP until you have installed all the zip files you copied over.
The order in the tutorial thread is the 5.3.1.0 system image, the recovery image, the make_space zip, the Supersu zip, the xposed zip, and the tk_gapps-modular-pico(uni)... zip.
Do all this from the Install menu in TWRP. I did not try to queue up all the zip files at once, I don't know if that would work.
If you forgot to copy a file, TWRP should allow you to copy files via a USB cable to your tablet.
If you do this on a Mac and Android file transfer craps out on you as it did with me, that is where the USB OTG cable comes in handy. But lets hope you copied everything or that the USB connection doesn't crap out on you.
Select the wipe menu, then advanced wipe. Check the cache and dalvik cache. Once done use the back arrow and swath the "swipe to factory reset" slider.
If you are brave, you can just reset and wait through the fire logo.
If you are trying to follow along with the tutorial I linked, reboot while holding volume up to see what recovery you land in. If it's not TWRP, proceed.
When you finally get to Android, you can use ES file explorer as one way to check for root privileges. I'm sure there are others.
I'm no expert, but if you run not problems with the Kindle Fire HD 6 (4th gen) and you started with 5.3.1.1, I can tell you some of the pitfalls I ran into and how I got out of them.
Excellent guide, thanks elementcarbon12!
I'm a total new comer to rooting and getting my hands dirty with android (although I am a long time linux user), and i made it work, and now have a fire hd 6 that I can sort the way I want it!
I did encounter a few problems though, first, I did not do a factory reset /data wipe after the downgrade and ended up in a boot loop. This was easily sorted by using the "adb reboot recovery" command, doing the data wipe/reset and then holding down power for 20 sec.
Everything was smooth sailing again until the reboot out of TWRP after installing the ZIP files. I did the wimps reboot to recovery to make sure I didn't get TWRP, which I didn't, so rebooted to get into android, however I entered a boot loop again. This time a simple hold the power for 20 sec and then turn on worked and the system started it's 'optimization'.
Upon completion, i still had root, although ES and my chosen launcher had gone, so had to reinstall them. No problems there though.
So thank you very much for collection all of the information and links from other pages into this one easy to follow post!
hi guys i have a question I'm on cm11 on fire hd 6 i also have a android backup of 4.5.3 my question is I'm note sure what boot loader i have at one point it did have 5xxx on it but not sure what version can i just side load 5.4.0 and be okay since the stock rom was put back to 4.5.3 thats how i installed cm11 or does it need boot loader from a 5xxx rom