Database Users

[Q] Trouble rooting Nexus 10

I've been following zedomax's Linux method to unlock the bootloader and root the Google Nexus 10 but after I type
sudo ./fastboot-linux oem unlock
Click to expand...
Click to collapse
I get
sudo: unable to execute ./fastboot-linux: No such file or directory
Click to expand...
Click to collapse

Have you installed fastboot-tools and adb-tools from you Linux distro's repos? If not, then you need to do that. Forget that other stuff.
After you install your distro's fastboot-tools you put your tablet in recovery mode (vol-up & vol-down & power on). In a terminal on your Linux box, type either su if you have su privileges OR sudo fastboot devices to see that your tablet is indeed in mode to accept fastboot commands. Then type fastboot oem unlock if you are su, else type sudo fastboot oem unlock.
--
Neal

He5aid said:
Have you installed fastboot-tools and adb-tools from you Linux distro's repos? If not, then you need to do that. Forget that other stuff.
After you install your distro's fastboot-tools you put your tablet in recovery mode (vol-up & vol-down & power on). In a terminal on your Linux box, type either su if you have su privileges OR sudo fastboot devices to see that your tablet is indeed in mode to accept fastboot commands. Then type fastboot oem unlock if you are su, else type sudo fastboot oem unlock.
--
Neal
Click to expand...
Click to collapse
I wish I read what you said earlier. I used wugfresh's nexus 10 toolkit and successfully unlocked my nexus 10 only to get into a boot loop. I managed to get CWM running but when I try to sideload the latest nightly of Cyanogemod I get a * cannot 'read' sideload error *

Can you post all input/output from terminal here, start with
adb devices

demkantor said:
Can you post all input/output from terminal here, start with
adb devices
Click to expand...
Click to collapse
I got it fixed using wugfresh's toolkit on windows. Thanks everyone for the help.

Hi,
Just in case, in this thread I've posted a guide about unlocking N10 Bootloader, Rooting and Restoring to Stock guides for Linux. I think you might find useful for future reference, even though your problem in this thread was solved...
http://forum.xda-developers.com/showthread.php?t=2670400
~Lord
"Time is too short to cry, long enough to try." - March of Time (Helloween)
Sent from my KitKat Nexus 10

XxLordxX said:
Hi,
Just in case, in this thread I've posted a guide about unlocking N10 Bootloader, Rooting and Restoring to Stock guides for Linux. I think you might find useful for future reference, even though your problem in this thread was solved...
http://forum.xda-developers.com/showthread.php?t=2670400
~Lord
"Time is too short to cry, long enough to try." - March of Time (Helloween)
Sent from my KitKat Nexus 10
Click to expand...
Click to collapse
Thanks man I appreciate it.

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.

[2017] Root Kindle Fire HD 6 4th gen tutorial

Hi,
This is my first post here but I have gotten so much help I wanted to give back. I have been working on rooting my Kindle fire HD 6 over the last couple days and after searching multiple tutorials I have successfully rooted with these steps.
To begin:
1. You MUST backup any data on your device before starting this process
2. Download all the files from here and Fire OS 5.4.0.0 here
3. Get your downgrade here
3. Follow the instructions below (modified from user @marathonjon reply here https://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950/page54)
Here we go for the install:
1. Enable ADB on your device and set up ADB on your computer
2. Download 4.5.3 firmware (you should already have it from the download above)
3. Connect device to computer and run "adb reboot recovery" (assuming you have adb enabled on your tablet)
4. Use volume keys and power button to navigate to "Apply update from ADB"
5. From computer type "adb sideload update-kindle-20.4.5.3_user_453011120.bin" (the files need to be added to the same folder your terminal is currently running or you can specify the file path)
6. From tablet select "wipe data/factory reset" (this is why we did the backup earlier)
7. From tablet select "reboot system"
8. Complete setup (do not connect to a wifi network yet, this is very important!)
9. Disable OTA updates ( adb shell ; pm block com.amazon.dcp or "Debloater"), I used the above jmz Kindle fire tools to disable the OTA, just sideload it and you are good to go.
10. Sideload Kingroot & let it root (this can take a while, just let it go)
11. Flash openrecovery-twrp-2.8.6.0-ariel.img TWRP image via Flashify (backup stock recovery first, again very important!!) (you will need to sideload the included Flashify APK)
12. Download all files above and place them in the Download directory of your kindle
13. Boot into TWRP, flash 4.5.3_twrp_recovery_full_ariel_string.zip. (use adb reboot recovery for this)
14. Do factory reset using the default TWRP wipe settings
15. Flash FireOS 5.4.0.0 (rename *bin to *zip so that TWRP can recognize it)
16. Flash 5.5.2_1534_stock_recovery_uboot.zip, this will put the required 5.3.1 bootloader back(PLEASE MAKE SURE TO DO THIS STEP!!)
17. DO NOT REBOOT YET! If you do you will probably lose root!
18. Flash Supersu.zip (included in the download
19. Clear cache/dalvik in TWRP
20. Reboot to recovery: adb reboot recovery. This will be stock recovery now because TWRP doesn’t boot with 5.x bootloaders.
21. Reboot to FireOS (could take ~15 minutes, it might seem like it is stuck in a boot loop but it will go)
The above instructions served me well, as with all posts on this site PLEASE USE AT YOUR OWN RISK! And post any questions below

I just followed your tutorial and it worked for me... Amazon has FireOS 5.4.0.1 for the update file now and it still worked following your steps. Thank you!

Could I keep root without updating to 5.4?
---------- Post added at 06:42 AM ---------- Previous post was at 06:26 AM ----------
Also Kingroot fails. Was the exploit is uses patched?

Bricked Device(unbricked it with DoLooper tutorial) improvising,Step 9 says sideload JMZ Tools how do you do that without connection? only way i can think is es explorer which you have to have connection to install

Any news on this? Thinking of attempting

I attempted this to downgrade from rooted 5.12 to 4.53 so that I could install twrp and get to the latest load.
I am stuck on step 8. After I flashed 4.5.3 and wiped, I attempted to sideload kingroot and the jmz utility but they did not install. I imagined that it failed because they are from unknown sources and that setting is disabled once 4.5.3 is loaded. So I rebooted with wifi off, attempted to adb reboot recovery, and I got to a recovery menu with 2 options, none of which are adb sideload.
How can I proceed? If I enable wifi to download kingroot, it will attempt to update, correct?
EDIT - I enabled wifi to download kingroot apk since I can't sideload it, and surely enough an update to 4.5.5 downloaded. Damn.
RE-EDIT--I just caught my initial mistake. I used the command adb sideload for kingroot and jmz instead of adb install. Another damn. I am downloading kingroot and rooting while the update to 4.5.5 awaits installation, which I won't do.

It boot me into kids edition...?

jcarcinogen said:
I just followed your tutorial and it worked for me... Amazon has FireOS 5.4.0.1 for the update file now and it still worked following your steps. Thank you!
Click to expand...
Click to collapse
Glad to hear! I have had a blast with a rooted kindle, including installing google and using root required apps.

demoncamber said:
Any news on this? Thinking of attempting
Click to expand...
Click to collapse
It worked great for me, considering that that the tablet cost me $60 brand new I took the risk. It is up to you whether this is something that you want.

I have a kindle fire hd 7 4th gen, running 5.6.0.1. Will this work for me?

Will this work for my hd 7 4th gen running fire os 5.6.0.1?
@marathonjon
@RobbotCC
@jcarcinogen
Please I really want to get root to install a android rom or cyanagen mod.

RobbotCC said:
Hi,
This is my first post here but I have gotten so much help I wanted to give back. I have been working on rooting my Kindle fire HD 6 over the last couple days and after searching multiple tutorials I have successfully rooted with these steps.
To begin:
1. You MUST backup any data on your device before starting this process
2. Download all the files from here and Fire OS 5.4.0.0 here
3. Get your downgrade here
3. Follow the instructions below (modified from user @marathonjon reply here https://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950/page54)
Here we go for the install:
1. Enable ADB on your device and set up ADB on your computer
2. Download 4.5.3 firmware (you should already have it from the download above)
3. Connect device to computer and run "adb reboot recovery" (assuming you have adb enabled on your tablet)
4. Use volume keys and power button to navigate to "Apply update from ADB"
5. From computer type "adb sideload update-kindle-20.4.5.3_user_453011120.bin" (the files need to be added to the same folder your terminal is currently running or you can specify the file path)
6. From tablet select "wipe data/factory reset" (this is why we did the backup earlier)
7. From tablet select "reboot system"
8. Complete setup (do not connect to a wifi network yet, this is very important!)
9. Disable OTA updates ( adb shell ; pm block com.amazon.dcp or "Debloater"), I used the above jmz Kindle fire tools to disable the OTA, just sideload it and you are good to go.
10. Sideload Kingroot & let it root (this can take a while, just let it go)
11. Flash openrecovery-twrp-2.8.6.0-ariel.img TWRP image via Flashify (backup stock recovery first, again very important!!) (you will need to sideload the included Flashify APK)
12. Download all files above and place them in the Download directory of your kindle
13. Boot into TWRP, flash 4.5.3_twrp_recovery_full_ariel_string.zip. (use adb reboot recovery for this)
14. Do factory reset using the default TWRP wipe settings
15. Flash FireOS 5.4.0.0 (rename *bin to *zip so that TWRP can recognize it)
16. Flash 5.5.2_1534_stock_recovery_uboot.zip, this will put the required 5.3.1 bootloader back(PLEASE MAKE SURE TO DO THIS STEP!!)
17. DO NOT REBOOT YET! If you do you will probably lose root!
18. Flash Supersu.zip (included in the download
19. Clear cache/dalvik in TWRP
20. Reboot to recovery: adb reboot recovery. This will be stock recovery now because TWRP doesn’t boot with 5.x bootloaders.
21. Reboot to FireOS (could take ~15 minutes, it might seem like it is stuck in a boot loop but it will go)
The above instructions served me well, as with all posts on this site PLEASE USE AT YOUR OWN RISK! And post any questions below
Click to expand...
Click to collapse
Does this work on the Fire OS 5.6.0.1 that was sent out this year?

Provided said:
I have a kindle fire hd 7 4th gen, running 5.6.0.1. Will this work for me?
Click to expand...
Click to collapse
IDK, it has been awhile since I ran this and I have not stayed up to date on the latest firmware. As always you can try it at your own risk and post any questions here. I will do my best to answer.
I do not recommend trying this if you rely on the tablet for anything, things can go wrong and you could lose everything including the tablet.
Have Fun!

On step 15, does it have to be 5.4.0.0? I'm having trouble finding a download for it since the link in OP leads to 5.6.0.1
edit: found a link (https://forum.xda-developers.com/hd8-hd10/general/fire-hd-8-2017-downgrade-to-5-4-0-0-5-6-t3719639) but it's for FIre HD 8. Will that work or does it need to be specifically for the HD 6?
edit2: nevermind, didn't look hard enough, found it here https://forum.xda-developers.com/fire-hd/general/fire-hd-rom-links-t3173102

liebherk said:
On step 15, does it have to be 5.4.0.0? I'm having trouble finding a download for it since the link in OP leads to 5.6.0.1
Click to expand...
Click to collapse
Yes, that is the latest version that is still root-able I believe.

Still works with update 5.6.1.0
Still works thanks alot!

Yup, worked for me as well. Thanks @RobbotCC from another CMH kindle newbie

Stuck on step #13
My KF HD 6 gen 4 shows it is running OS 4.5.3. I can boot into TWRP. ADB sees my device. I need to add ".\adb" before ADB commands.
The problem I'm having is that I cannot flash the TWRP 4.5.3 recovery. When I have the TWRP launcher showing and type " .\adb reboot recovery" the system reboots right into the TWRP launcher. When I power off then on, it boots right into the Fire OS. I never see the system recovery screen, so I can't flash the recovery zip file.
Help? Any ideas would be greatly appreciated.
Thanks.

LeoDaQ said:
My KF HD 6 gen 4 shows it is running OS 4.5.3. I can boot into TWRP. ADB sees my device. I need to add ".\adb" before ADB commands.
The problem I'm having is that I cannot flash the TWRP 4.5.3 recovery. When I have the TWRP launcher showing and type " .\adb reboot recovery" the system reboots right into the TWRP launcher. When I power off then on, it boots right into the Fire OS. I never see the system recovery screen, so I can't flash the recovery zip file.
Help? Any ideas would be greatly appreciated.
Thanks.
Click to expand...
Click to collapse
Flash the recovery file using twrp?
The whole process worked for me on my kf hd 7 Ariel now I have rooted 5.6.1.0.

Provided said:
Flash the recovery file using twrp?
The whole process worked for me on my kf hd 7 Ariel now I have rooted 5.6.1.0.
Click to expand...
Click to collapse
did you use the same files in the first thread? for hd 7 ? or should we download specific downgrade file?

How to revert back to stock FireOS from Lineage 16 on Fire HD 8 karnak (8th generation)?

Hello, quick question: How do I revert back to stock FIreOS from lineage 16. I read that it is just a matter of going to TWRP, wipe ccaches, install FireOS bin (renamed as .zip)...however my question is since I am on Lineage 16 with android version 9, which FireOS version I should install to go back to stock and avoid bootloops?
FireOS 6, I think is android version 8 and FireOS 7 is android version 9. Can I install any of them directly? Or it has to be one specific? Or do I need to downgrade?
Thank you in advance,

adtamez said:
Hello, quick question: How do I revert back to stock FIreOS from lineage 16. I read that it is just a matter of going to TWRP, wipe ccaches, install FireOS bin (renamed as .zip)...
Click to expand...
Click to collapse
You may want to wipe data too...
adtamez said:
however my question is since I am on Lineage 16 with android version 9, which FireOS version I should install to go back to stock and avoid bootloops?
FireOS 6, I think is android version 8 and FireOS 7 is android version 9. Can I install any of them directly? Or it has to be one specific? Or do I need to downgrade?
Click to expand...
Click to collapse
Installing a stock rom based on FireOS 6 will work and remain unlocked...
but the fireOS7 stock rom will bootloop on an unlocked device.

Sus_i said:
You may want to wipe data too...
Installing a stock rom based on FireOS 6 will work and remain unlocked...
but the fireOS7 stock rom will bootloop on an unlocked device.
Click to expand...
Click to collapse
Thank you.
I want to send it back to Amazon as part of a trade in for a newer tablet. How do I lock it (I'm assuming you are taking about the bootloader?) If you don't mind telling me a short summary of the steps to revert back to stock I appreciate it. Just to make sure that I am following the steps correctly and I am not missing anything.
Regards,

adtamez said:
How do I lock it (I'm assuming you are taking about the bootloader?) If you don't mind telling me a short summary of the steps to revert back to stock I appreciate it. Just to make sure that I am following the steps correctly and I am not missing anything.
Click to expand...
Click to collapse
You may follow the go-to-stock section from the unlock guide:
[UNLOCK][ROOT][TWRP][UNBRICK] Fire HD 8 2018 (karnak) amonet-3
Read this whole guide before starting. This is for the 8th gen Fire HD8 (karnak). Current version: amonet-karnak-v3.0.1.zip This is based on xyz`s original work, but adds some features such as reboot to hacked BL. It also intends to simplify...
forum.xda-developers.com
Code:
Going back to stock
Extract the attached zip-file "amonet-karnak-return-to-stock.zip"
into the same folder where you extracted "amonet-karnak-v3.0.1.zip"
and open a terminal in that directory.
Then run:
sudo ./return-to-stock.sh
Your device should reboot into Amazon Recovery.
Use adb sideload to install stock image from there.
(Make sure to use FireOS 6.3.0.0 or newer, otherwise you may brick your device)

Sus_i said:
You may follow the go-to-stock section from the unlock guide:
[UNLOCK][ROOT][TWRP][UNBRICK] Fire HD 8 2018 (karnak) amonet-3
Read this whole guide before starting. This is for the 8th gen Fire HD8 (karnak). Current version: amonet-karnak-v3.0.1.zip This is based on xyz`s original work, but adds some features such as reboot to hacked BL. It also intends to simplify...
forum.xda-developers.com
Code:
Going back to stock
Extract the attached zip-file "amonet-karnak-return-to-stock.zip"
into the same folder where you extracted "amonet-karnak-v3.0.1.zip"
and open a terminal in that directory.
Then run:
sudo ./return-to-stock.sh
Your device should reboot into Amazon Recovery.
Use adb sideload to install stock image from there.
(Make sure to use FireOS 6.3.0.0 or newer, otherwise you may brick your device)
Click to expand...
Click to collapse
thank you...so in order to do so, I need to use a Linux system, correct? I vaguely remember using this instruction to unlock it and had to use a usb stick with ubuntu. To go back to stock I need it again, correct?

Sus_i said:
You may follow the go-to-stock section from the unlock guide:
[UNLOCK][ROOT][TWRP][UNBRICK] Fire HD 8 2018 (karnak) amonet-3
Read this whole guide before starting. This is for the 8th gen Fire HD8 (karnak). Current version: amonet-karnak-v3.0.1.zip This is based on xyz`s original work, but adds some features such as reboot to hacked BL. It also intends to simplify...
forum.xda-developers.com
Code:
Going back to stock
Extract the attached zip-file "amonet-karnak-return-to-stock.zip"
into the same folder where you extracted "amonet-karnak-v3.0.1.zip"
and open a terminal in that directory.
Then run:
sudo ./return-to-stock.sh
Your device should reboot into Amazon Recovery.
Use adb sideload to install stock image from there.
(Make sure to use FireOS 6.3.0.0 or newer, otherwise you may brick your device)
Click to expand...
Click to collapse
Hi, so I'm trying to back to stock per the instructions but I have a problem. First I cannot run sudo ./return to stock because it shows on the computer terminal "waiting for device" but once I get into bootloader on the tablet the script runs. So I'm assuming it is made for the bootloader and it is just missing from the instructions.
But the problem is that the script runs, it tries to install boot.bin but it fails, the error states: "FAILED (remote: 'Flashing is not allowed in Lock State')". So I'm assuming I have the bootloader locked but how is that possible? Every instruction to be and to install lineage unlocks the bootloader and install TWRP. Which I have both. I have lineage and TWRP as recovery.
What do I do? Is it possible that I locked the bootloader after installing lineage? Is that even possible? I just don't remember what I did.
Any suggestions are very much welcomed.
Thanks

adtamez said:
Any suggestions are very much welcomed.
Click to expand...
Click to collapse
You can use the boot-fastboot script to get into the hacked fastboot (instead of the locked one), then you can run the script... or extract and flash the images out of the back2stock file by hand via fastboot flash...

Sus_i said:
You can use the boot-fastboot script to get into the hacked fastboot (instead of the locked one), then you can run the script... or extract and flash the images out of the back2stock file by hand via fastboot flash...
Click to expand...
Click to collapse
Thank you Sus, I figured that out as well. Unfortunately I keep getting problems as i move along on the process. So right now, I have the tablet turn on and connected to a live Ubuntu system. ADB recognizes de device and everything works, also adb reboot bootloader works. But in order to get to the hacked fastboot when I run the script: sudo ./boot-fastboot.sh this errors present and the tablet doesn't do anything:
[email protected]:/cdrom/amonet/amonet$ sudo ./boot-fastboot.sh
[2022-07-20 16:43:44.336269] Waiting for preloader
Traceback (most recent call last):
File "handshake2.py", line 17, in <module>
dev.find_device(True)
File "/cdrom/amonet/amonet/modules/common.py", line 63, in find_device
log("Waiting for preloader")
File "/cdrom/amonet/amonet/modules/logger.py", line 7, in log
with open("amonet.log", "a") as fout:
OSError: [Errno 30] Read-only file system: 'amonet.log'
What can I do? this is beyond my expertise. Is it saying that the preloader it is not found? What preloader is talking about and what can I do about this errors?
Thank you so much. Hopefully this thread will help other as well.

adtamez said:
Thank you Sus, I figured that out as well. Unfortunately I keep getting problems as i move along on the process. So right now, I have the tablet turn on and connected to a live Ubuntu system. ADB recognizes de device and everything works, also adb reboot bootloader works. But in order to get to the hacked fastboot when I run the script: sudo ./boot-fastboot.sh this errors present and the tablet doesn't do anything:
[email protected]:/cdrom/amonet/amonet$ sudo ./boot-fastboot.sh
[2022-07-20 16:43:44.336269] Waiting for preloader
Traceback (most recent call last):
File "handshake2.py", line 17, in <module>
dev.find_device(True)
File "/cdrom/amonet/amonet/modules/common.py", line 63, in find_device
log("Waiting for preloader")
File "/cdrom/amonet/amonet/modules/logger.py", line 7, in log
with open("amonet.log", "a") as fout:
OSError: [Errno 30] Read-only file system: 'amonet.log'
What can I do? this is beyond my expertise. Is it saying that the preloader it is not found? What preloader is talking about and what can I do about this errors?
Thank you so much. Hopefully this thread will help other as well.
Click to expand...
Click to collapse
Preloader is the first boot stage after the SOCs bootrom, you can see the current stage via lsusb command.
Make sure that you extract the amonet zip file on the ubuntu desktop (avoid any fat/exfat/ntfs devices), or download it again via ubuntu and extract it there... otherwise all permissions are gone and the script fails...

(Solved) TWRP Recovery mess

Hello XDA,
I flashed my Fire HD 8 (2018) from FireOS to LineageOS 17 using this guide ( https://forum.xda-developers.com/t/rom-unlocked-karnak-lineage-17-1-17-july-2020.4134829/ ).
Installation went great, TWRP/LineageOS was working fine. Later as I began to setup the tablet I became unsatisfied with the ROM because the camera and proximity sensor were not working properly for me. I then decided it would be better to flash to a previous Lineage ROM to get better performace/support ( https://forum.xda-developers.com/t/rom-testing-suez-lineage-16-0-05-july-2022.4232785/ )
At this point is when things went wrong. I tried to overwrite/upgrade TWRP from within TWRP using the IMG file posted in the LineageOS 16 guide with this method - https://www.droidwin.com/update-twrp-recovery-android/ (skip to step 4)
Now whenever I try to boot into Recovery Mode all I see is the Amazon Logo, I cannot get the tablet to boot into TWRP recovery. As bad as that is I can still boot into LineageOS 17 which is a relief. I've tried doing the fastboot recovery method but I get the message "FAILED (remote: 'the command you input is restricted on locked hw')"
At this point I'm stuck and reluctant to try too much more, but I'd still like to try the LineageOS 16 ROM.

G4_PITA said:
Hello XDA,
I flashed my Fire HD 8 (2018) from FireOS to LineageOS 17 using this guide ( https://forum.xda-developers.com/t/rom-unlocked-karnak-lineage-17-1-17-july-2020.4134829/ ).
Installation went great, TWRP/LineageOS was working fine. Later as I began to setup the tablet I became unsatisfied with the ROM because the camera and proximity sensor were not working properly for me. I then decided it would be better to flash to a previous Lineage ROM to get better performace/support ( https://forum.xda-developers.com/t/rom-testing-suez-lineage-16-0-05-july-2022.4232785/ )
At this point is when things went wrong. I tried to overwrite/upgrade TWRP from within TWRP using the IMG file posted in the LineageOS 16 guide with this method - https://www.droidwin.com/update-twrp-recovery-android/ (skip to step 4)
Now whenever I try to boot into Recovery Mode all I see is the Amazon Logo, I cannot get the tablet to boot into TWRP recovery. As bad as that is I can still boot into LineageOS 17 which is a relief. I've tried doing the fastboot recovery method but I get the message "FAILED (remote: 'the command you input is restricted on locked hw')"
At this point I'm stuck and reluctant to try too much more, but I'd still like to try the LineageOS 16 ROM.
Click to expand...
Click to collapse
If you're lucky enough you might be rooted. If you are, brick the PL header with ADB (make sure your tablet can access bootrom mode) and re-run amonet.​

Rortiz2 said:
If you're lucky enough you might be rooted. If you are, brick the PL header with ADB (make sure your tablet can access bootrom mode) and re-run amonet.​
Click to expand...
Click to collapse
Thank you for replying....Unfortunately it looks like I'm not rooted.
I installed the "Root Chcker" app through the Play Store and when I click "verify root" it says "Sorry! Root access is not properly installed on this device".
Any advice on how best to proceed?

G4_PITA said:
Thank you for replying....Unfortunately it looks like I'm not rooted.
I installed the "Root Chcker" app through the Play Store and when I click "verify root" it says "Sorry! Root access is not properly installed on this device".
Any advice on how best to proceed?
Click to expand...
Click to collapse
Well, it's possible that you have a root shell regardless of what the root checker reports. Try running adb root and see what it returns.​

Rortiz2 said:
Well, it's possible that you have a root shell regardless of what the root checker reports. Try running adb root and see what it returns.​
Click to expand...
Click to collapse
When I run the command "adb root" and command line spits out "adbd is already running as root". So it looks like I'm good here...
When you say 'bootrom mode' are you talking about fastboot? I'm still able enter into fastboot mode, thats when I get the error message listed in the 1st post.
When you say 'brick the PL header with ADB' do you mean to follow this guide? - https://forum.xda-developers.com/t/unlock-root-twrp-unbrick-fire-hd-8-2018-karnak-amonet-3.3963496/

G4_PITA said:
When I run the command "adb root" and command line spits out "adbd is already running as root". So it looks like I'm good here...
When you say 'bootrom mode' are you talking about fastboot? I'm still able enter into fastboot mode, thats when I get the error message listed in the 1st post.
When you say 'brick the PL header with ADB' do you mean to follow this guide? - https://forum.xda-developers.com/t/unlock-root-twrp-unbrick-fire-hd-8-2018-karnak-amonet-3.3963496/
Click to expand...
Click to collapse
bootrom is USBDL mode, the mode that is accessed when the PCB pins are shorted. Anyway, don't worry about that. Just run adb root and then ./fireos-step.sh from the thread you linked and you should be able to access TWRP again.​

Rortiz2 said:
bootrom is USBDL mode, the mode that is accessed when the PCB pins are shorted. Anyway, don't worry about that. Just run adb root and then ./fireos-step.sh from the thread you linked and you should be able to access TWRP again.​
Click to expand...
Click to collapse
After running 'adb root' it produces the same result as before, 'adbd is already running as root'.
When I run 'sudo ./fireos-step.sh', it then produces "functions.inc: line 39: dos2unix: command not found".
I can't find an immediate answer on how to handle this..

G4_PITA said:
After running 'adb root' it produces the same result as before, 'adbd is already running as root'.
When I run 'sudo ./fireos-step.sh', it then produces "functions.inc: line 39: dos2unix: command not found".
I can't find an immediate answer on how to handle this..
Click to expand...
Click to collapse
Code:
sudo apt update
sudo add-apt-repository universe
sudo apt install python3 python3-serial adb fastboot dos2unix

Rortiz2 said:
Code:
sudo apt update
sudo add-apt-repository universe
sudo apt install python3 python3-serial adb fastboot dos2unix
Click to expand...
Click to collapse
Thank you for the help, that worked.
I'm now having a different issue when running "./fireos-step.sh'". The result it produces is "This is only for the "karnak" - Amazon Fire HD 8 (2018 / 8th gen) - , your device is a "lineage_karnak".
I'm not sure where to find the correct file for "lineage_karnak".

G4_PITA said:
Thank you for the help, that worked.
I'm now having a different issue when running "./fireos-step.sh'". The result it produces is "This is only for the "karnak" - Amazon Fire HD 8 (2018 / 8th gen) - , your device is a "lineage_karnak".
I'm not sure where to find the correct file for "lineage_karnak".
Click to expand...
Click to collapse
Open fireos-step.sh with a text editor and remove the following line:
Code:
check_device "karnak" " - Amazon Fire HD 8 (2018 / 8th gen) - "

Rortiz2 said:
Open fireos-step.sh with a text editor and remove the following line:
Code:
check_device "karnak" " - Amazon Fire HD 8 (2018 / 8th gen) - "
Click to expand...
Click to collapse
I removed "check_device "karnak" " - Amazon Fire HD 8 (2018 / 8th gen) -"" from fireos-step.sh and now I'm getting a root access error shown below
Code:
Testing root access...
/system/bin/sh: su: inaccessible or not found
Trying to use mtk-su to get temp root...
No mtk-su found, you can get it here: https://forum.xda-developers.com/hd8-hd10/orig-development/experimental-software-root-hd-8-hd-10-t3904595
I then downloaded mtk-su and placed it into the working directory hoping it could find the file by itself but that didn't work unfortunately. I thought I had root access already, not sure why it's producing this error.

Rortiz2 said:
Open fireos-step.sh with a text editor and remove the following line:
Code:
check_device "karnak" " - Amazon Fire HD 8 (2018 / 8th gen) - "
Click to expand...
Click to collapse
So I removed the "get root" line from fireos-step.sh and it produces the following result -
Code:
* daemon not running; starting now at tcp:5037
* daemon started successfully
PL version: 5 (5)
LK version: 1 (1)
TZ version: 258 (258)
Flashing PL
bin/preloader.bin: 1 file pushed. 4.5 MB/s (142928 bytes in 0.030s)
/system/bin/sh: su: inaccessible or not found
According to these results It looks I'm not rooted. If this is true why when I run 'adb root' it returns 'adbd is already running as root'?

ttt...still no solution. If anyone can offer some good advice I'd be greatful. Thanks

G4_PITA said:
ttt...still no solution. If anyone can offer some good advice I'd be greatful. Thanks
Click to expand...
Click to collapse
Two things you can do/try...
First one is to use the boot-fastboot script out of the amonet folder, in order to boot into hacked fastboot mode. Just run the boot-fastboot script with sudo and connect the tablet (powered off). Then run fastboot devices, if your device is there. If yes, you can run the fastboot-step if you like, which will flash the old TWRP image. Maybe thats enough to boot into TWRP.
In case that won't help, you can also use hacked fastboot to brick the preloader (like @Rortiz2 suggested), to get into bootrom mode, which will prevent you from open-up the tablet. Follow #2 from the unbrick thread, i.e. unbrick with shorting. You can also use the same guide and use the 'open-up the tablet' thing, to short the special point and re-run amonet from scratch. Good luck.

Sus_i said:
Two things you can do/try...
First one is to use the boot-fastboot script out of the amonet folder, in order to boot into hacked fastboot mode. Just run the boot-fastboot script with sudo and connect the tablet (powered off). Then run fastboot devices, if your device is there. If yes, you can run the fastboot-step if you like, which will flash the old TWRP image. Maybe thats enough to boot into TWRP.
In case that won't help, you can also use hacked fastboot to brick the preloader (like @Rortiz2 suggested), to get into bootrom mode, which will prevent you from open-up the tablet. Follow #2 from the unbrick thread, i.e. unbrick with shorting. You can also use the same guide and use the 'open-up the tablet' thing, to short the special point and re-run amonet from scratch. Good luck.
Click to expand...
Click to collapse
Thanks for your help, when I get a chance I'll try this and report the results.

Sus_i said:
Two things you can do/try...
First one is to use the boot-fastboot script out of the amonet folder, in order to boot into hacked fastboot mode. Just run the boot-fastboot script with sudo and connect the tablet (powered off). Then run fastboot devices, if your device is there. If yes, you can run the fastboot-step if you like, which will flash the old TWRP image. Maybe thats enough to boot into TWRP.
In case that won't help, you can also use hacked fastboot to brick the preloader (like @Rortiz2 suggested), to get into bootrom mode, which will prevent you from open-up the tablet. Follow #2 from the unbrick thread, i.e. unbrick with shorting. You can also use the same guide and use the 'open-up the tablet' thing, to short the special point and re-run amonet from scratch. Good luck.
Click to expand...
Click to collapse
Finally got TWRP back!! The solution was so intuitive I feel ridiculous for not trying it first.
So I took the advice of Sus_i and ran the two files out of the karnak's amonet folder; bootrom-step.sh & fastboot-step.sh. This is exactly what I did initially to root the tablet and install LineageOS in the first place!! I posted a link to the solution in the first post of this thread!! For anyone wanting more info on the steps I took there's a video tutorial which shows what's required to get TWRP working again -
This video tutorial also shows how to install LineageOS onto a Fire HD 8 Tablet. I overwrote LineageOS 17 with LineageOS 16 Karnak. The camera is working in this version of Lineage but the proximity sensor is still lacking.
A big THANK YOU to users - Sus_i & Rortiz2 for helping me out, I'm very thankful for your knowledge and generosity.