Database Users

[TUT/FIX] Fix the Boot Loop on Kindle Fire HDX 7"

KINDLE FIRE HDX 7" [THOR ONLY] BOOT LOOP FIX​
Hello everyone,
At first, sorry for my bad English! I'm a german, not an american!!
I made it! I had the Problem with the Boot Loop, but now, I get it fixed. I don't know if this fix the Kindle Fire 8.9" too!
1. Go to System
2. Open devices and printer
3. Turn Kindle on and wait for the Boot Loop
4. On the PC, there will be a device what named MTP
5. Delete the Kindle driver on this (NO REBOOT)
6. Install adb driver
7. Open CMD
8. Go to the adb folder
9. Look for you Kindle with "adb devices"
10. When you get your Kindle at the CMD, push the Stock Rom in the adb folder
11. Push the Rom to the Kindle ---> "adb push [Rom-Name].zip /sdcard"
12. Rom on the Kindle? Go to the recovery and install the Stock Rom
13. Restart the Kindle
Finish! Now, your Kindle should start!
Should be any problems, say it

--reserved--
:d :d :d

I get "error: device not found" while doing this. Maybe I set it up wrong? I'm on win7 64

"adb devices" not found my device
oOFrAnzOo said:
KINDLE FIRE HDX 7" [THOR ONLY] BOOT LOOP FIX​
Hello everyone,
At first, sorry for my bad English! I'm a german, not an american!!
I made it! I had the Problem with the Boot Loop, but now, I get it fixed. I don't know if this fix the Kindle Fire 8.9" too!
1. Go to System
2. Open devices and printer
3. Turn Kindle on and wait for the Boot Loop
4. On the PC, there will be a device what named MTP
5. Delete the Kindle driver on this (NO REBOOT)
6. Install adb driver
7. Open CMD
8. Go to the adb folder
9. Look for you Kindle with "adb devices"
10. When you get your Kindle at the CMD, push the Stock Rom in the adb folder
11. Push the Rom to the Kindle ---> "adb push [Rom-Name].zip /sdcard"
12. Rom on the Kindle? Go to the recovery and install the Stock Rom
13. Restart the Kindle
Finish! Now, your Kindle should start!
Should be any problems, say it
Click to expand...
Click to collapse
After No.9 not attched my Kindle device.did you know this problem fix?

Same.. not adb.. only mtp device
i tried to delete MTP driver.
but i cant.. and still mtp.
i tried to delete Window media player11
and i did. but same ,
i will reply after do it again on Window XP PC.
(Now 8 64bit PC)

How to install stock ROM from the recovery?
I've uploaded original ROM with changing the extension from bin to zip.
I've rebooted with 'adb reboot recovery' but the recovery from ROM is not available there.
Code:
Kindle Fire System Recovery
Your Kindle doesn't seem to be able to boot.
Resetting your device to Factory defaults may
help you to fix this issue.
Volume up/down to move highlight;
power button to select.
---------------------------------------------
Reboot your Kindle
Reset to Factory Defaults
---------------------------------------------
I can't find the source code of this particular part of recovery and I can't find even the recovery in stock ROM.

CrashThump said:
How to install stock ROM from the recovery?
I've uploaded original ROM with changing the extension from bin to zip.
I've rebooted with 'adb reboot recovery' but the recovery from ROM is not available there.
Code:
Kindle Fire System Recovery
Your Kindle doesn't seem to be able to boot.
Resetting your device to Factory defaults may
help you to fix this issue.
Volume up/down to move highlight;
power button to select.
---------------------------------------------
Reboot your Kindle
Reset to Factory Defaults
---------------------------------------------
I can't find the source code of this particular part of recovery and I can't find even the recovery in stock ROM.
Click to expand...
Click to collapse
Same problem

How to connect adb??
May I Question?
i have win7 and ubuntu 13.10 os and install latest sdk but my computer is recognized MTP by win7 and adb devices blank at ubuntu how did you tell me connect adb?? what your os? please tell me ...

Well... Any help with
12. Rom on the Kindle? Go to the recovery and install the Stock Rom
This is my second boot loop...

@oOFrAnzOo, so how did you installed the snapshot from the recovery?
I want to rollback and I don't have the su on the new firmware (and there is no way to get the root) so now this is a really critical step for me.
Could you please clarify?

Who can help me install ADB Driver for my Kindle ?

Sorry guys that i don't write reply's, but i haven't got enough time I hope that i find a way to help you!
I try to customize the ASOP Rom (not the GAPPS Rom), but it's very hard for a noob like me
For all who ask: I use Windows 7 Home Premium.

Hold on there...
CrashThump said:
How to install stock ROM from the recovery?
I've uploaded original ROM with changing the extension from bin to zip.
I've rebooted with 'adb reboot recovery' but the recovery from ROM is not available there.
Code:
Kindle Fire System Recovery
Your Kindle doesn't seem to be able to boot.
Resetting your device to Factory defaults may
help you to fix this issue.
Volume up/down to move highlight;
power button to select.
---------------------------------------------
Reboot your Kindle
Reset to Factory Defaults
---------------------------------------------
I can't find the source code of this particular part of recovery and I can't find even the recovery in stock ROM.
Click to expand...
Click to collapse
DO NOT FACTORY RESET without doing a lot of reading first and understand the implications. In many circumstances, that is a quick way to make the problem worse. It could remove SU and ADB communication.

lawnnewm said:
DO NOT FACTORY RESET without doing a lot of reading first and understand the implications. In many circumstances, that is a quick way to make the problem worse. It could remove SU and ADB communication.
Click to expand...
Click to collapse
Well, this advice is useless for me because new firmware removes SU too
TS has made a tutorial which works only for him and he doesn't providing any comments to reproduce his tutorial.
Can this topic be closed / removed?

thienthanh1122 said:
Who can help me install ADB Driver for my Kindle ?
Click to expand...
Click to collapse

@thienthanh1122, what's the issue? Did you downloaded the correct drivers from Amazon? Is your Kindle in boot loop?
Please provide more information.

CrashThump said:
@thienthanh1122, what's the issue? Did you downloaded the correct drivers from Amazon? Is your Kindle in boot loop?
Please provide more information.
Click to expand...
Click to collapse
My kindle can't boot because i wipe this system , i can't connect my kindle with my computer you can see in picture my attach

Give me pictures
I dont know what you are talking about but, can you give me pictures on how you fix it?, with a citation?

[Root] Using Tethered TWRP to root Android 6.0.1 ZE551ML with locked bootloader

**** This is a modified post with detailed explanation and different files. The original post was made by @samcjtasi at here. *****
If you installed Android 6 from locked Lollipop Bootloader or forgot to unlock the bootloader before the installation and all you need is to root the device, this is a guide for you.
I did unlocked my Bootloader when I was on 168 with Asus unlock app. I flashed 194 raw file via Asus Flash tool which locked my bootloader. I installed MM via adb sideload and I had MM with Locked bootloader. I used this method to root my phone.
I am sure you'd already known that rooting the phone (acquiring the administrative rights for your own phone) will void the phone warranty.
With this method,
1. You do not need to downgrade your MM bootloader to Lollipop, unlock it, install twrp and root the phone, and then upgrade back to MM.
2. You do not need to install the TWRP. You will be running the TWRP from the tethered mode so your stock recovery will be intact.
3. SuperSu initial installation will modify some files in your boot partition in order to re-direct the system request to the SuperSu, as such In case you want to receive an OTA file later, do
**REMEMBER to FLASH BACK TO STOCK Android 6.0 BOOT.IMG** to unroot before upgrading to official Android 6.0.
4. Make sure your phone has battery 80% or more.
Requirements:
1. USB drivers for Asus have to be installed in the computer and your computer should recognize and can do the file transfers between the computer and your phone. You can get the drivers here. You will need to allow the file transfer from your phone when prompt.
2. Android debug bridge (ADB) has to be installed in your computer. I used ADB version 1.0.32. Some knowledge in using DOS and ADB is a plus.
3. Your phone should have the developer option enable and usb debugging should be checked in the developer option tab.
4. You need to know how to use the TWRP. There are a couple videos on youtube explaining about using TWRP.
The Files you need for the root.
1. TWRP - you can download the latest twrp file from here. The latest is ver 3.0.20. You could use older 2.8 versions if you want it.
2. SuperSu installer - I did try with latest SuperSu without success as such use the SuperSu patched by @shakalaca . Get the BETA-SuperSU-v2.74-2-20160519174328-patch-by-shakalaca-for-zenfone2-6.0.zip file here.
Steps:
1. Copy the downloaded TWRP to the directory that you install the ADB. (If you do not want to type long file name in adb, rename it to twrp.img. )
2. Connect your phone to the computer and copy the SuperSu installer to the phone internal memory or the external SD card.
3. Open the command prompt windows with administrative rights. (Without admin right ADB will not work properly).
4. Go to the ADB directory using the cd command. (e.g. cd\, cd adb, etc...)
5. Start the ADB environment by typing "adb start-server" . (without the quotation marks of course). You should see ****the demon started successfully*** message.
6. If you want to check your phone connection in adb, you can type "adb devices" to see your phone is recognized in ADB environment. You should see your phone serial no. and status .
7. Boot the phone to bootloader by typing "adb reboot-bootloader". The phone should vibrate and go into the fastboot mode. Wait till your phone get in the fastboot mode before you proceed.
8. Give the command to boot the phone to the twrp by typing "fastboot boot twrp.img". (If you did not change the name of the image file you need to type or copy and paste the whole file name).
You will see the message saying like-
"downloading 'boot.img' .....
OKAY [0.668s]
booting.....
OKAY [0.450s]
finished. total time: 1.120s "
The phone will vibrate twice and the Asus Logo with black splash screen will appear. The phone is start booting with TWRP image.
9. Unplug the phone from the computer. (If within 30 sec your phone should not start booting to TWRP. you can press and release the power button to go to the normal boot mode or press and release the volume-up key to go to the recovery mode. The TWRP should start by then.)
10. In TWRP install the SuperSu file by tapping install option. (I am sure you remember where you put the SuperSU installer zip file)
11. When the SuperSu installation is completed you will see the message saying like " You will see the your phone has failed verification message and reboot a couple times". Please remember that.
12. Clear the Dalvik cache and then reboot the phone. (You can reboot the phone without clearing the dalvik cache if you want).
Your phone will reboot and you will see the triangle saying like "your phone has failed verification" message and then automatically reboot the phone, showing up the message again. It would happen two to three times and you phone will be booted to the system. (You will not see that error message anymore in the upcoming boots).
Now your phone is rooted. You can check it by installing and running the app like root-chekcer.
Good luck.

Even with the command to boot into twrp from fast boot mine still boots into stock recovery
Sent from my ASUS_Z00AD using Tapatalk

sci05 said:
Even with the command to boot into twrp from fast boot mine still boots into stock recovery
Sent from my ASUS_Z00AD using Tapatalk
Click to expand...
Click to collapse
It should not be go to stock recovery. The command is to boot with twrp.img.
Did you see message "booting ok finsihed" in the adb window?
Once you see that message, you can unplug the phone from the computer and twrp should be boot within 30 sec.

I finally found the time to update, everything went smooth but I'm having problems booting the twrp
I've tried several twrp from the guides but none worked
In cmd it says
Downloading boot.img
Okay
Booting...
Okay
Finished
C:\
The phone reboots but it goes to the dead droid screen.
I'm using adb and fastboot from adb-setup-1.4.3
IntelAndroidDriver1.10.0 and I've selected this version for the device in device manager.
The so is win 10 prof, I'm starting cmd as administrator.
I tried unplugging the phone and leaving it connected.
Also I'm using the 550 version, I've tried twrps from several threads for 550 and 551 (even tho twrp has merged both phones)
Am I missing something?
A little ot :
I need root 'couse adaway but I thought I would just use the twrp file manager to swap the default hosts file with the one I had in L.
It should work, right?
Sent from my ASUS_Z008D

sway8966 said:
It should not be go to stock recovery. The command is to boot with twrp.img.
Did you see message "booting ok finsihed" in the adb window?
Once you see that message, you can unplug the phone from the computer and twrp should be boot within 30 sec.
Click to expand...
Click to collapse
Yup says boot ok bit it boots into the dead android which is the load screen of the stock recovery. Press vol up and power and stock recovery menu appears.
Sent from my ASUS_Z00AD using Tapatalk

Acca85 said:
I finally found the time to update, everything went smooth but I'm having problems booting the twrp
I've tried several twrp from the guides but none worked
In cmd it says
Downloading boot.img
Okay
Booting...
Okay
Finished
C:\
The phone reboots but it goes to the dead droid screen.
I'm using adb and fastboot from adb-setup-1.4.3
IntelAndroidDriver1.10.0 and I've selected this version for the device in device manager.
The so is win 10 prof, I'm starting cmd as administrator.
I tried unplugging the phone and leaving it connected.
Also I'm using the 550 version, I've tried twrps from several threads for 550 and 551 (even tho twrp has merged both phones)
Am I missing something?
A little ot :
I need root 'couse adaway but I thought I would just use the twrp file manager to swap the default hosts file with the one I had in L.
It should work, right?
Sent from my ASUS_Z008D
Click to expand...
Click to collapse
The guide was written from the experience working with 551ML but it should work for the 550ML I think.
I am also using the Win10 Prof and my adb has a date of 3/30/2015.
I downloaded the latest twrp from the teamwin site. I did not use the twrp mentioned in this forum because they did not work for me. (The purpose of this guide is to use TWRP as temporary and not to install on the phone as such we do not need the signed TWRP ).
In the original thread some mentioned about going to the stock recovery (dead droid with red triangle) as such I put the instruction to press the power button or press the volumn-up button to go to the recovery mode. Actually, they are not required. If everything works, your phone should start booting with the twrp image.

sci05 said:
Yup says boot ok bit it boots into the dead android which is the load screen of the stock recovery. Press vol up and power and stock recovery menu appears.
Sent from my ASUS_Z00AD using Tapatalk
Click to expand...
Click to collapse
If you saw the message booting .... and ok your phone should be start booting to TWRP not the recovery. The command was to boot the phone with TWRP image. Try to download the TWRP image again from the teamwin site.

If someone just need root for Adaway, just don't, it is not required anymore since you can use other adblocker without root. Just install Block this and you're on: https://block-this.com
Sent from my Asus Zenfone 2 using XDA Labs
---------- Post added at 02:05 AM ---------- Previous post was at 02:03 AM ----------
Will this root method unlock definitely the boot loader as the other methods around here for MM?
Sent from my Asus Zenfone 2 using XDA Labs

sway8966 said:
If you saw the message booting .... and ok your phone should be start booting to TWRP not the recovery. The command was to boot the phone with TWRP image. Try to download the TWRP image again from the teamwin site.
Click to expand...
Click to collapse
I used the latest twrp. Should I use a different one?
Sent from my ASUS_Z00AD using Tapatalk

sci05 said:
I used the latest twrp. Should I use a different one?
Sent from my ASUS_Z00AD using Tapatalk
Click to expand...
Click to collapse
If you are using latest twrp directly downloaded from the teamwin site and if you are following the steps that I mentioned you should be OK. The only thing different could be the ADB version. Try different adb version or try this on the different computer.

Thanks. I got systemless root by this method.

fred_gaou said:
If someone just need root for Adaway, just don't, it is not required anymore since you can use other adblocker without root. Just install Block this and you're on: https://block-this.com
Sent from my Asus Zenfone 2 using XDA Labs
---------- Post added at 02:05 AM ---------- Previous post was at 02:03 AM ----------
Will this root method unlock definitely the boot loader as the other methods around here for MM?
Sent from my Asus Zenfone 2 using XDA Labs
Click to expand...
Click to collapse
Thanks for the reminder, I'm using this until I get twrp to boot.
I tried adb 1.0.36 that should be the latest but it didn't work. I'll try on win7 or something.
If someone that succeeded could do
Adb version
Fastboot --version
And report here I'd be grateful.
Edit:
I've tried win 7 too but without luck.
Sent from my ASUS_Z008D

I confirm - it doesn't work. I have too "dead droid" and "No command" below.
Windows 10 Pro, ADB 1.4.3. Asus Zenfone 2 ZE551ML 4GB/32GB/Z3580 stock firmware 4.21.40.134.

ok, so how to install xposed framework?

Hi,
Does it reset the phone (apps, documents, accounts,...) ?
Tks !

This will probably not work. In other for it to work and be able to boot into twrp, I had to unlock the bootloader first, because the "fastboot boot twrp.zip" command wouldn't work unless I did so

CBT38 said:
Hi,
Does it reset the phone (apps, documents, accounts,...) ?
Tks !
Click to expand...
Click to collapse
No it does not. The procedure is to boot with twrp image temporarily.

jman0 said:
This will probably not work. In other for it to work and be able to boot into twrp, I had to unlock the bootloader first, because the "fastboot boot twrp.zip" command wouldn't work unless I did so
Click to expand...
Click to collapse
It work for me though. If you unlocked your bootloader you do not need this method. You can simply install the twrp to your recovery partition.

I can confirm it does not work with a locked bootloader, it boots into the dead droid screen.

Can i install Xposed with threded recovery

Thor & 4.5.5.2 : Easy to root and Unlock Bootloader

Finally I got myself to root and unlock bootloader of my Thor Kindles. I've been lurking for few years. Here is the steps:-
1. Install Kingroot from Kingroot website (https://kingroot.net/) and root the phone. I got it first try. But some people are saying they need 8 tries to work. Some even report success after 20 tries.
2. Flash TWRP and Unlock bootloaders. Instruction in https://forum.xda-developers.com/ki...r-firmware-t3463982/post70881555#post70881555. Instruction in this post is better than the first post (OP) in the thread. The step is:-
a) install ADB driver and install Kindle Fire USB driver
b) put get_code.bat and unlock.bat in adb.exe directory. Put aboot and cubed twrp in /sdcard/
b) create unlock.code with get_code.bat
c) flash aboot and cubed twrp with this command in DOS command prompt in adb.exe directory:-
adb shell
su
dd if=/sdcard/twrp_cubed.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
dd if=/sdcard/aboot_vuln.mbn of=/dev/block/platform/msm_sdcc.1/by-name/aboot
Click to expand...
Click to collapse
d) make sure check the Android ADB Composite driver is properly install in Device Manager
e) execute unlock.bat
f) reboot, press UP + power to boot into TWRP
g) wipe, then flash your ROM using adb sideload or normal flashing if you already have the rom in your device earlier. Then wipe again.
Tips:-
1. Make sure the driver is Android ADB Composite Driver is properly install or the unlock bootloader (unlock.bat) won't work
2. Installing Rom, press UP+POWER to go into TWRP, download the ROM to PC, then enable ADB side in TWRP, follow up with ADB sideload command in PC. Wipe before and after. :-
https://forum.xda-developers.com/kindle-fire-hdx/orig-development/rom-fire-nexus-rom-ktu84q-t3322931
3. Safe Strap is not supported in 4.5.5.2
4. Copy ROM zip file to /sdcard/ before doing the above to skip the adb sideload step and you can directly flash the rom from TWRP only.
5. Can't boot into 4.5.5.2 after unlock bootloader. I've tried issuing "fastboot -i 0x1949 oem idme bootmode 4000" and then "fastboot -i 0x1949 reboot" command but it does not work.
Added another instructions from another forumer who think my instructions is not complete:-
1. Install the moto driver and then plug in your device while running normal
2. Run the get_code.bat (from this link)
3. once unlock.code file is created, run "adb reboot bootloader". It will show [Fastboot] with the kf logo.
4. Once bootloader comes up, change driver in device manager for "Other Android" to use the Android -> Mot Adb Composite Driver. It should say "Ready" on the KF
5. Run the stuff from this post (do the bottom steps with fastboot erase first)
6. After you are done in bulk mode, hold the power button for 15 secs to reboot. It will automatically boot into Fastboot
7. When you run the unlock command, use the "unlock.code" file.. not the "0xmmssssssss.unlock" example from that link.
8. Now unplug and hold power again to shut down. Hold VolUp + Power. About 3 secs after you see the KF logo, you can let go of the power button (possibly both buttons) and you get TWRP
From here you can flash CM and gapps (5.1).
Click to expand...
Click to collapse

just wondering is it important to be on os 4.5.5.2 before rooting and unlocking boodloader? I am on OS 13.3.2.1 and I just have no idea what path to do. All I want is to not have OTA and have google play store working

BatmanDC said:
just wondering is it important to be on os 4.5.5.2 before rooting and unlocking boodloader? I am on OS 13.3.2.1 and I just have no idea what path to do. All I want is to not have OTA and have google play store working
Click to expand...
Click to collapse
You do not need to be on 4.5.5.2 or any specific version of FireOS for that matter. Is the device rooted?

BatmanDC said:
just wondering is it important to be on os 4.5.5.2 before rooting and unlocking boodloader? I am on OS 13.3.2.1 and I just have no idea what path to do. All I want is to not have OTA and have google play store working
Click to expand...
Click to collapse
As Davey said, no. The reason I created this thread because 4.5.5.2 is the last OTA. My point is even last OTA can root and unlock bootloader.

kkcheong said:
As Davey said, no. The reason I created this thread because 4.5.5.2 is the last OTA. My point is even last OTA can root and unlock bootloader.
Click to expand...
Click to collapse
I'd like to add that you don't even need root to unlock.
Personally, I'd stay away from Kingroot, unless that was the only option.
Thankfully, it is not.

draxie said:
I'd like to add that you don't even need root to unlock.
Personally, I'd stay away from Kingroot, unless that was the only option.
Thankfully, it is not.
Click to expand...
Click to collapse
are those instructions as daunting as they sound?
it seems if you kingroot and wipe everything it negates any malware?

barrist said:
...it seems if you kingroot and wipe everything it negates any malware?
Click to expand...
Click to collapse
Correct. KingRoot is a borderline malware but does not appear to harvest personal info during the rooting process and is completely irradiated by a wipe of the system and data partitions.

draxie said:
I'd like to add that you don't even need root to unlock.
Personally, I'd stay away from Kingroot, unless that was the only option.
Thankfully, it is not.
Click to expand...
Click to collapse
Davey126 said:
Correct. KingRoot is a borderline malware but does not appear to harvest personal info during the rooting process and is completely irradiated by a wipe of the system and data partitions.
Click to expand...
Click to collapse
Thanks
just picked up a used HDX off Kijiji, so i'm looking forward to tinkering.. can you suggest an initial stable rom to try? the KK based Nexus seems to be the safer one i'm gathering?

barrist said:
Thanks
just picked up a used HDX off Kijiji, so i'm looking forward to tinkering.. can you suggest an initial stable rom to try? the KK based Nexus seems to be the safer one i'm gathering?
Click to expand...
Click to collapse
There are no bad/unstable HDX ROMs. Fire Nexus has the advantage for those needed full Bluetooth and/or LTE support. Otherwise LineageOS 14.1 is a solid choice. Regardless of direction you'll want to unlock the bootloader and wipe the device immediately after rooting if KingRoot is utilized. Also know Amazon devices have their own set of quirks and don't behave like a typical Android gizmo.

Thanks maybe I'll give lineage a shot as I don't really don't need LTE or bt .. just hoping for stable app support and wifi

draxie said:
I'd like to add that you don't even need root to unlock.
Personally, I'd stay away from Kingroot, unless that was the only option.
Thankfully, it is not.
Click to expand...
Click to collapse
Thanks for the awesome info. But noob like me would prefer Kingroot because it give the illusion of zero risk :laugh:

nice, instructions worked, running lineage 14.1 and no problems so far!

kkcheong said:
Thanks for the awesome info. But noob like me would prefer Kingroot because it give the illusion of zero risk :laugh:
Click to expand...
Click to collapse
No problem.
Given that you wipe 'data' (which I prefer not to, because I'm too lazy to make backups),
you should be fine with KingRoot, it just takes much longer, but that's your choice.
The real risk is making a mistake when flashing aboot and TWRP, which is the same on both paths.

kkcheong said:
Finally I got myself to root and unlock bootloader of my Thor Kindles. I've been lurking for few years. Here is the steps:-
1. Install Kingroot from Kingroot website (https://kingroot.net/) and root the phone. I got it first try. But some people are saying they need 8 tries to work.
2. Flash TWRP and Unlock bootloaders. Instruction in https://forum.xda-developers.com/ki...r-firmware-t3463982/post70881555#post70881555. Instruction in this post is better than the first post (OP) in this thread. The step is:-
a) install ADB driver and install Kindle Fire USB driver
b) put get_code.bat and unlock.bat in adb.exe directory. Put aboot and cubed twrp in /sdcard/
b) create unlock.code with get_code.bat
c) flash aboot and cubed twrp with this command in DOS command prompt in adb.exe directory:-
d) make sure check the Android ADB Composite driver is properly install in Device Manager
e) execute unlock.bat
f) reboot, press UP + power to boot into TWRP
g) wipe, then flash your ROM using adb sideload or normal flashing if you already have the rom in your device earlier. Then wipe again.
Tips:-
1. Make sure the driver is Android ADB Composite Driver is properly install or the unlock bootloader (unlock.bat) won't work
2. Installing Rom, press UP+POWER to go into TWRP, download the ROM to PC, then enable ADB side in TWRP, follow up with ADB sideload command in PC. Wipe before and after. :-
https://forum.xda-developers.com/kindle-fire-hdx/orig-development/rom-fire-nexus-rom-ktu84q-t3322931
3. Safe Strap is not supported in 4.5.5.2
4. Copy ROM zip file to /sdcard/ before doing the above to skip the adb sideload step and you can directly flash the rom from TWRP only.
5. Can't boot into 4.5.5.2 after unlock bootloader. I've tried issuing "fastboot -i 0x1949 oem idme bootmode 4000" and then "fastboot -i 0x1949 reboot" command but it does not work.
Click to expand...
Click to collapse
I tried to follow all steps but cannot go beyond Step 2c. When I try to flash cubed and aboot, i get "cannot access file : file or directory not present" error. How should I proceed?

xyluss0 said:
I tried to follow all steps but cannot go beyond Step 2c. When I try to flash cubed and aboot, i get "cannot access file : file or directory not present" error. How should I proceed?
Click to expand...
Click to collapse
Have you put both file in the adb directory?

Yes I did. Also, I tried to go ahead on the next step and run unlock.bat but I got the error "incorrect unlock code".

xyluss0 said:
Yes I did. Also, I tried to go ahead on the next step and run unlock.bat but I got the error "incorrect unlock code".
Click to expand...
Click to collapse
Please print screen. Did you cd to ADB directory?

Root hdx 7 (3rd Gen.), FireOS 4.5.5.2 with towelroot
Hi,
I am wondering if the towelroot rooting process is working with the 4.5.5.2 version of the fireOS.
Do you recommend the usage of APK-versions of Kingroot or Towelroot over the use of Windowsversion esp. for Kingroot.
Do i need working internet connection during rooting process with APKs ?
Thx in advance
Achimbub

Root fails
kkcheong said:
Finally I got myself to root and unlock bootloader of my Thor Kindles. I've been lurking for few years. Here is the steps:-
1. Install Kingroot from Kingroot website (https://kingroot.net/) and root the phone. I got it first try. But some people are saying they need 8 tries to work.
2. Flash TWRP and Unlock bootloaders. Instruction in https://forum.xda-developers.com/ki...r-firmware-t3463982/post70881555#post70881555. Instruction in this post is better than the first post (OP) in this thread. The step is:-
a) install ADB driver and install Kindle Fire USB driver
b) put get_code.bat and unlock.bat in adb.exe directory. Put aboot and cubed twrp in /sdcard/
b) create unlock.code with get_code.bat
c) flash aboot and cubed twrp with this command in DOS command prompt in adb.exe directory:-
d) make sure check the Android ADB Composite driver is properly install in Device Manager
e) execute unlock.bat
f) reboot, press UP + power to boot into TWRP
g) wipe, then flash your ROM using adb sideload or normal flashing if you already have the rom in your device earlier. Then wipe again.
Tips:-
1. Make sure the driver is Android ADB Composite Driver is properly install or the unlock bootloader (unlock.bat) won't work
2. Installing Rom, press UP+POWER to go into TWRP, download the ROM to PC, then enable ADB side in TWRP, follow up with ADB sideload command in PC. Wipe before and after. :-
https://forum.xda-developers.com/kindle-fire-hdx/orig-development/rom-fire-nexus-rom-ktu84q-t3322931
3. Safe Strap is not supported in 4.5.5.2
4. Copy ROM zip file to /sdcard/ before doing the above to skip the adb sideload step and you can directly flash the rom from TWRP only.
5. Can't boot into 4.5.5.2 after unlock bootloader. I've tried issuing "fastboot -i 0x1949 oem idme bootmode 4000" and then "fastboot -i 0x1949 reboot" command but it does not work.
Click to expand...
Click to collapse
I am on Fire OS 4.5.5.2 (HDX 8.9 Apollo) and Kingroot can not root(both apk and windows versions). I tried both ten times. What can I do to root this device now?

achimbub said:
Hi,
I am wondering if the towelroot rooting process is working with the 4.5.5.2 version of the fireOS.
Do you recommend the usage of APK-versions of Kingroot or Towelroot over the use of Windowsversion esp. for Kingroot.
Do i need working internet connection during rooting process with APKs ?
Thx in advance
Achimbub
Click to expand...
Click to collapse
- TowelRoot is ineffective on FireOS v4
- recommend desktop version of KingRoot for 4.5.5.2 (still may not work)
- device does not need an active internet connection with desktop version
---------- Post added at 04:58 AM ---------- Previous post was at 04:55 AM ----------
bobcat131 said:
I am on Fire OS 4.5.5.2 (HDX 8.9 Apollo) and Kingroot can not root(both apk and windows versions). I tried both ten times. What can I do to root this device now?
Click to expand...
Click to collapse
KingOroot is the only other tool that reportedly works on 4.5.5.2. It also has a reputation for screwing up devices. Risky choice.

Reflash HD 10 to remove root etc?

My Kindle Fire HD10 has dead pixels so Amazon sent me a replacement and i need to send the old one back.
I rooted it, replaced launcher and disabled automatic updates.
I am on Firmware 5.6.1.0 and i was wondering, is there a simple way to jut reflash the device with a firmware and easily have it back to stock?
Thanks in advance!

IndigoHD said:
My Kindle Fire HD10 has dead pixels so Amazon sent me a replacement and i need to send the old one back.
I rooted it, replaced launcher and disabled automatic updates.
I am on Firmware 5.6.1.0 and i was wondering, is there a simple way to jut reflash the device with a firmware and easily have it back to stock?
Thanks in advance!
Click to expand...
Click to collapse
Hi, you may try the steps below,
#-Click here to download the stock firmware, version 5.6.1.0 for Fire HD 10 (7th Generation)
#-Place the downloaded .bin file in your ADB installed folder
#-Reboot the Fire to recovery (Power+Vol. Down) or 'adb reboot recovery'
#-Move and select 'apply update from ADB'
#-Then copy the name of the update .bin with the .bin (I think update-kindle-40.6.0.5_user_605485120.bin) and,
adb sideload *paste*
Replace paste with the copied name, like,
adb sideload update-kindle-40.6.0.5_user_605485120.bin
Then after it finishes, it should reboot to recovery again, and wipe the data (optional but highly recommended because you are returning it) without leaving the recovery. 'wipe data/factory reset'
#-And then choose 'reboot system now'
Good Luck!

Supersonic27543 said:
Hi, you may try the steps below,
#-Click here to download the stock firmware, version 5.6.1.0 for Fire HD 10 (7th Generation)
#-Place the downloaded .bin file in your ADB installed folder
#-Reboot the Fire to recovery (Power+Vol. Down) or 'adb reboot recovery'
#-Move and select 'apply update from ADB'
#-Then copy the name of the update .bin with the .bin (I think update-kindle-40.6.0.5_user_605485120.bin) and,
adb sideload *paste*
Replace paste with the copied name, like,
adb sideload update-kindle-40.6.0.5_user_605485120.bin
Then after it finishes, it should reboot to recovery again, and wipe the data (optional but highly recommended because you are returning it) without leaving the recovery. 'wipe data/factory reset'
#-And then choose 'reboot system now'
Good Luck!
Click to expand...
Click to collapse
I will try that! Thank you very much!

All i did in the end was restore the default launcher and then reset it to factory default. That was enough for me.

With this tutorial, I just put an update my Fire HD 8 (7th gen) with firmware 5.4.0.0 (i was in 5.3.6).
I 'wipe data/factory reset' .
But can not restart my tablet.
Even staying 20 seconds press power

[HOWTO] UNROOT Fire TV 2 with pre-rooted ROM and twrp

After reading posts all over of how to unroot the FTV2 with a prerooted ROM I decided to give it a go this is the procedure I followed to get back to non-root stock and remove twrp.
You will need a computer or phone for ADB and plenty of time.
I was on the latest (5.2.7.0) pre-rooted
1) factory reset
2) using twrp install second newest pre-rooted ROM (5.2.6.9)
3) wait until installed and reboot
4) using twrp wipe cache
5) wait until complete and booted and reboot
6) setup normally to get into settings
7) enable ADB in settings
8)
Code:
adb connect [IP]
adb shell
su
pm unhide com.amazon.device.software.ota
pm enable com.amazon.device.software.ota (said denied!)
manage_recovery (said STOCK!)
9) back into settings to do another update, and reboot
10) repeating step 7 you maybe stuck in loop downloading latest stock download but doesnt install!!!!
11) go to settings and re-enable adb debugging (if required)
12)
Code:
adb connect [IP]
adb shell
su
manage_recovery (now says NOT STOCK - so type 'yes')
su pm enable com.amazon.device.software.ota (just to be sure, now says enabled)
13) back to settings to do another update
14) then click Install update
15) let it do the update install takes while, then it reboots to opitimize
16) reboots into stock fireTV, settings update again, then install update (keep doing this step until we are up to date!)
17) once up to date you can perform one last factory reset.
Now you're as good as new. no more twrp and no more root.
I'm sure a lot of this isn't necessary but I couldn't find a quicker solution online and this was written as I was trying it!

For additional info, if you are on a Pre-rooted FW prior to 5.2.6.7, you must install Rbox's sloane-5.2.6.7-rooted_r2.zip image first, otherwise you will not receive the new OTA updates to remove root.
Install sloane-5.2.6.7-rooted_r2.zip via TWRP, then follow the steps in the OP:
adb connect [IP]
adb shell
su
manage_recovery (It should say "NOT STOCK" so type "yes" ENTER)
pm unhide com.amazon.device.software.ota
pm enable com.amazon.device.software.ota
Then you can install the latest OTA, via Settings, My Fire TV, About, Check For Updates.

gazdaman. said:
For additional info, if you are on a Pre-rooted FW prior to 5.2.6.7, you must install Rbox's sloane-5.2.6.7-rooted_r2.zip image first, otherwise you will not receive the new OTA updates to remove root.
Install sloane-5.2.6.7-rooted_r2.zip via TWRP, then follow the steps in the OP:
adb connect [IP]
adb shell
su
manage_recovery (It should say "NOT STOCK" so type "yes" ENTER)
pm unhide com.amazon.device.software.ota
pm enable com.amazon.device.software.ota
Then you can install the latest OTA, via Settings, My Fire TV, About, Check For Updates.
Click to expand...
Click to collapse
Hey I was looking for this. I am currently on 5.2.6.8 and want to unroot, hope it works out!

Any clue if this is working on a fire stick TV 2 ?
tocUK said:
After reading posts all over of how to unroot the FTV2 with a prerooted ROM I decided to give it a go this is the procedure I followed to get back to non-root stock and remove twrp.
You will need a computer or phone for ADB and plenty of time.
I was on the latest (5.2.7.0) pre-rooted
1) factory reset
2) using twrp install second newest pre-rooted ROM (5.2.6.9)
3) wait until installed and reboot
4) using twrp wipe cache
5) wait until complete and booted and reboot
6) setup normally to get into settings
7) enable ADB in settings
8)
Code:
adb connect [IP]
adb shell
su
pm unhide com.amazon.device.software.ota
pm enable com.amazon.device.software.ota (said denied!)
manage_recovery (said STOCK!)
9) back into settings to do another update, and reboot
10) repeating step 7 you maybe stuck in loop downloading latest stock download but doesnt install!!!!
11) go to settings and re-enable adb debugging (if required)
12)
Code:
adb connect [IP]
adb shell
su
manage_recovery (now says NOT STOCK - so type 'yes')
su pm enable com.amazon.device.software.ota (just to be sure, now says enabled)
13) back to settings to do another update
14) then click Install update
15) let it do the update install takes while, then it reboots to opitimize
16) reboots into stock fireTV, settings update again, then install update (keep doing this step until we are up to date!)
17) once up to date you can perform one last factory reset.
Now you're as good as new. no more twrp and no more root.
I'm sure a lot of this isn't necessary but I couldn't find a quicker solution online and this was written as I was trying it!
Click to expand...
Click to collapse
did anyone tested it on a fire stick TV 2 ? This would be wonderful as I would like to go back to stock rom.

On the second to most recent rooted rom, the above process doesn't work. Updates don't get installed. Instead I downloaded the latest stock rom from here, renamed the .bin to .zip, and flashed the recent stock rom. This worked for me so sharing for others that might need an alternative:
[UNLOCK][ROOT][TWRP][UNBRICK] FireTV 2 (sloane)
Read this whole guide before starting. This is for the 2nd gen Fire TV (sloane) Current relase: amonet-sloane-v1.1 NOTE: This process does not require you to open your device if you're already rooted or you have TWRP. NOTE: If something goes...
forum.xda-developers.com
I'm really glad this thread came up as it certainly gave me an option to try and the unlock root twrp unbrick post with the stock images was really hard to find. So hope this helps someone.