Database Users

TWRP Recovery installation through KF Utility bricked my Kindle

Hello, brand new to the Kindle. I rooted my device just fine last night and decided to use Kindle Fire Utility to install TWRP. ADB was recognizing the device perfectly and the script seemed to be running fine until it rebooted the Kindle. At that point the script said "reboot: operation not permitted waiting for device" for an extended period of time. After waiting awhile, at this point I did something I probably shouldn't have, I unplugged the Kindle and rebooted it using the power button. It's been getting stuck at the "kindle fire" boot animation ever since. I haven't gotten a screen with a triangle and fire logo.
I tried following the instructions in the sticky but it seems adb no longer recognizes the device, so I can't push zergRush or anything past that.
Is it permanently bricked or is there a method to fix my problem yet?
Thanks for any help.
_______________________
Update: kindle was fixed by uninstalling drivers, reinstalling as android composite usb device, and switching it out of fastboot. not permanently bricked.

sounds like its in fast boot.
open the utility again, check if its in fast boot, if it is run the install command again. if u can't get it installed, use utility to change boot mode back to 4000.

I had the same problem this method worked for me http://forum.xda-developers.com/showpost.php?p=20509949&postcount=245 http://forum.xda-developers.com/showpost.php?p=20421225&postcount=222

Thanks for the fast replies!
When I try to change the bootmode using the fastboot it just says waiting for device and never progresses. KindleFireUtility shows ADB Online, Boot status at 4002, and fastboot as offline. Device manager doesn't show a Kindle, just an android adb interface with a yellow ! triangle.
I did restart the PC once and the kindle a few times. No luck yet.
I installed the ADB Composite driver again for the device and got this error (attached)

I had the same issue. It turned out that I had forgotten to update my computer with the drivers needed for TWRP install after copying them to the Android and .Android folders. I was able to get to the first reboot.. waiting for device and then checked device manager when it wouldn't progress. I found that the the driver was unrecognized. After updating the drivers in device manager, TWRP completed install successfully and I was able to backup my FW6.2 and then flash CM7.

uninstall the driverand use the driverin the utility thread? someone said leaving ur kindle connected to ur pc and rebooting ur pc will reboot the kindle? if it works su with terminal and change bootmode back to 4000
sent from my kindle fire

Alright everyone, I got it working after uninstalling the driver for the Android device, shutting down, starting up again, and plugging in and reinstalling the driver, then changing the bootmode using the instructions previously posted. Thank you all SO MUCH for helping as much as you could. Now to try this again!

terracode said:
I had the same issue. It turned out that I had forgotten to update my computer with the drivers needed for TWRP install after copying them to the Android and .Android folders. I was able to get to the first reboot.. waiting for device and then checked device manager when it wouldn't progress. I found that the the driver was unrecognized. After updating the drivers in device manager, TWRP completed install successfully and I was able to backup my FW6.2 and then flash CM7.
Click to expand...
Click to collapse
Now I'm wondering what you mean by making sure the drivers are installed for TWRP to install correctly. Obviously I missed a step the first time, what do I do to make sure I don't miss it again? Right now when I try to install TWRP again it says "The system cannot find the filepath specified" several times.

would recomend to use following:
http://forum.xda-developers.com/showthread.php?t=1399889
download the utility and prepare according:
http://forum.xda-developers.com/showthread.php?p=20574755#post20574755
change bootmode, install twrp or whatever with the utility

Got twrp on it last night successfully and flashed CM7.

My question is somewhat related to this thread...
I'm on 6.2 (wifi turned off) and was already rooted and am trying to update to the 6.2.1 secured update with root installed update found on XDA. I'm using Kindle Fire Utility v.6, and to the best of my knowledge using the drivers included with the KF Utility program.
In the utility I show...
ADB Status: Online
Boot Status: 4000
Fastboot Status: Offline
Question is I'm not familiar with fastboot and unclear if I have everything configured in order to (safely) install TWRP. In a command prompt when I type 'fastboot devices' nothing is displayed ("adb devices" shows the device). Combined with the fact I've never seen anything but "Offline" for the Fastboot Status, I'm a little concerned I'm missing a piece of the puzzle and hesitant to install TWRP until I know better.
Any help/advice would be appreciated. Thanks!

look at my post on page 1 of this thread !

@Stevebro: I believe if you are using KF Utility v.6, then you should be good to go. As long as you installed and updated the usb Drivers and then ran zergRush, you should be at the point where you can install TWRP. Just make sure you are using the latest version of KF Utility and it should go pretty smoothly.

... After you install TWRP, I'd recommend going back to your KF OS and do a Titanium Backup of your apps and then doing a TWRP backup. When you flash to CM7 you can restore all your apps easily and painlessly using Titanium backup to restore with the Batch restore option.

Couple nervous moments, reboots and switching out of fastboot mode in the utility... but it all went well. Thanks for the help!!

glad to hear everything is fine ...

Glad to hear everything worked out. I myself sat staring at the "yellow triangle" for a couple of hours. lol, but I just kept working through it and tried not to panic and I got everything working again.
I think OP should edit the first post, or get a mod to edit the title. I keep reading random posts about "lot's of people permanently bricking their Kindle Fires" while I cannot recall a single instance of someone bricking and having to return one and it is getting tiresome.

How I was able to unbrick my Kindle Fire

Hi everyone.
I managed to brick my kindle fire within an hour of purchasing it, but using the suggestions on this forum, I was able to get it back up and running in a few hours.
The method that I had to use involved suggestions grabbed from several threads, so I wanted to provide instructions on exactly how I managed to fix mine in case someone ends up in the same situation as me.
For starters, I had just updated my Kindle Fire to 6.2.1 and I was messing around with trying to get the google app manager installed. I rooted the device, and I was changing permissions in the /system/app directory when the device crashed and became stuck on the boot animation. I did not have TWRP installed at the time.
So if you are like me, or in a similar situation, this may be applicable.
These instructions assume that you have adb on your computer.
First, ensure that you are able to communicate with your device using ADB. Verify this by using the command:
adb devices
Click to expand...
Click to collapse
or by using the kindle fire utility and ensuring that the status is online.
If you are not able to communicate with your device AND have the boot animation (right to left reflection across the "Kindle Fire" logo text), you likely have a driver issue.
Several possible ways to resolve this. First, I recommend going to device manager and unistalling the driver for the android phone adb interface. Unplug the kindle fire and plug it in again. The device should show up without a driver as "kindle". Manually apply the proper driver again and check the adb connection. If this does not work, uninstall the driver again and add 0x18d1 at the end of adb_usb.ini on a line underneath "0x1949" and reapply the driver. Toss in a few shutdowns in between some of these steps if you are still having trouble. Hopefully you now have a connection to your device.
If you are not able to communicate with your device AND do not have the boot animation (right to left reflection across the "Kindle Fire" logo text), your kindle fire is in the wrong bootmode (likely fastboot).
To fix this, download fastboot.exe (if you don't already have it) and run the following command, even if you don't have an adb connection)
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
Click to expand...
Click to collapse
or if that doesn't work
fastboot -i 0x18d1 oem idme bootmode 4000
fastboot -i 0x18d1 reboot
Click to expand...
Click to collapse
Your kindle fire should restart and now be stuck at the logo with animation, and you should have the ability to communicate with your device through adb now.
Now, you should download the kindle fire firmware (6.2.1 as of the time of writing this) from http://www.amazon.com/gp/help/customer/display.html?nodeId=200790620. Rename this to update.zip and drop it in the same directory as adb.exe on your pc. Execute the following command.
adb push update.zip /sdcard/
Click to expand...
Click to collapse
Now, you need to use fbmode to enable the fastboot mode, per pokey9000's instructions at http://forum.xda-developers.com/showthread.php?p=20755810
Assuming that that was able to complete successfully, you need to flash TWRP 2.0 per pyrostic's instructions at http://rootzwiki.com/topic/12363-ho...our-kindle-fire/page__pid__301703#entry301703
You now should be stuck at a screen with a yellow triangle. Pressing the power button several times until it turns orange should bring you into the recovery screen. Do the following:
Wipe cache
Wipe dalvik cache
Factory reset
Go back to the home screen and select install -> update.zip
And when that's done, you can tell it to reboot.
It'll think for a minute or two at the kindle fire boot, and then it will go into the initial setup screen. You're now the proud owner of a working fact0ry default kindle fire!
Quick note: I wrote this from memory quickly to try to help anyone experiencing problems. I'm no android expert, so if there are ways to improve on this or corrections to be made, please let me know so that the community can benefit.
And I don't want to appear to take undue credit for any of these instructions. I did not come up with anything on this guide on my own, everything came from various threads on this forum. These are just the steps that I followed to successfully bring my kindle fire back from death.

Man, My Kindle Fire does not even get detected by my PC

Now, you need to use fbmode to enable the fastboot mode, per pokey9000's instructions at http://forum.xda-developers.com/show...php?p=20755810
Assuming that that was able to complete successfully, you need to flash TWRP 2.0 per pyrostic's instructions at http://rootzwiki.com/topic/12363-how...03#entry301703
You now should be stuck at a screen with a yellow triangle. Pressing the power button several times until it turns orange should bring you into the recovery screen. Do the following:
Wipe cache
Wipe dalvik cache
Factory reset
Go back to the home screen and select install -> update.zip
And when that's done, you can tell it to reboot.
It'll think for a minute or two at the kindle fire boot, and then it will go into the initial setup screen. You're now the proud owner of a working fact0ry default kindle fire!
****When I run the fbmode I am getting stuck on the boot logo screen. Can someone please help me??

that is normal - you are in fastboot mode now - adb commands don't work in this mode - fastboot commands do - resume with the description ...

Thanks for your post.
I also "bricked" my kindle the day I got it but my issue was not having the correct drivers installed when I started the rooting process. My drivers would recognize the Kindle when it was booted normally but when it went into fastboot mode the Kindle would just show as "Unknown Device" in device manager. In windows you can't remove the drivers for unknown device so I had no way of backing out the old drivers.
What I ended up doing was grabbing my other laptop and making sure I had the correct drivers installed, then connected the kindle and was able to back it out of fastboot mode.
---------- Post added at 09:05 AM ---------- Previous post was at 09:04 AM ----------
umarsl said:
Man, My Kindle Fire does not even get detected by my PC
Click to expand...
Click to collapse
Does it show up as "unknown Device" in device manager?

you can uninstall the drivers
win 7:
http://www.petri.co.il/removing-old-drivers-from-vista-and-windows7.htm
xp:
http://www.techrepublic.com/article/removing-unused-device-drivers-from-windows-xp-machines/6017628

Just wanted to say thanx for the post. I ran into the exact same condition that the op did where I inadvertently screwed up the permissions on the /system/app directory which caused the kf to wig out and brick. I wished I had seen your post earlier because I ended up going to many posts and piecing together the information which was a little confusing at times. The op is great and I just wanted to point out two observations that seemed to me the most confusing working through the issue and getting it unbricked and hopefully will bring some clarity for folks.
1. Understanding the different states of the "kindle fire" logo.
- Shimmering animation and appears to loop = normal boot mode and is the state that you should be able to communicate with adb. This is the state where you can push files to the kf like twrp and fbmode which is what is needed to get kf in fastboot mode when bricked like this.
- The logo is static and does not "wink" out or loop = fastboot mode. This is when you use fastboot commands on your PC to change boot modes and also execute files such as twrp to get it installed once you pushed it to the kf with adb.
2. USB Drivers.
- This can be a real killer. After playing with this for hours, the one thing that I found that helped the most was when the driver stopped working I would unplug the kf from the PC and then hard reboot the kf (hold on/off ~20 seconds) then just plug back in, don't use on/off. Keep the device manager open on the PC and watch. You will soon start to see a pattern when you have the right driver and do this a few times.
Once these things are ironed out all eventually works out. BTW, this occurred after my kf was upgraded to 6.2.2. So the instructions and tools and everything else you will find still works. Good luck to anyone working through this issue. Just remember, if you can communicate with it, it's almost certain there is a way to recover it.

Arrow [Q] Kindle fire bricked, adb : device not found

Hello,
I know there are many similar threads but i have a slightly different issue: I was editing /system/build.prop and did a reboot and i got stuck, right after the Kindle Fire logo pops up it goes black at the time the animation is supposed to start, computer reads it fine but ADB nor Fastboot will pick it up.KWRP also doesn't work, Any help?
IMPORTANT:
I have a backup of a TESTED and WORKING build.prop, if i can mount the Kindle in windows i will be able to apply the backup and fix it that way.
FYI:
I don't exactly care about keeping my data anymore, I just want it to turn on and be usable...

When you first try to power on the device and the amazon logo is still being displayed have you tried to get adb shell rooted or set it to recovery mode boot? Without the firefirefire bootloader it is going to be difficult to use adb unless you can at some point get adb to connect. Just out of curiosity, why didn't you also flash the boot loader instead of just flashing twrp? All I know to try is either kfu and keep hitting 0 to recheck device status and maybe you will get an Online+Rooted read out at some point before the system attempts to load & crashes.

linuxsociety said:
When you first try to power on the device and the amazon logo is still being displayed have you tried to get adb shell rooted or set it to recovery mode boot? Without the firefirefire bootloader it is going to be difficult to use adb unless you can at some point get adb to connect. Just out of curiosity, why didn't you also flash the boot loader instead of just flashing twrp? All I know to try is either kfu and keep hitting 0 to recheck device status and maybe you will get an Online+Rooted read out at some point before the system attempts to load & crashes.
Click to expand...
Click to collapse
I try to get into recovery mode, I'm not sure why i didn't use FireFireFire, this is my first tinker with an android device, I tried KFU from the instant i pressed power button to the black screen and its just unknown device. Is it broke for good?

I have a crazy idea and i have no idea if it will work, but it's worth a shot:
After reading the Kindle Fire breakdown, I think i can take the kindle apart and get access to it's internal SD, my questions is this: can I somehow plug it into a computer?

superbomb17 said:
I try to get into recovery mode, I'm not sure why i didn't use FireFireFire, this is my first tinker with an android device, I tried KFU from the instant i pressed power button to the black screen and its just unknown device. Is it broke for good?
Click to expand...
Click to collapse
So KFU is reporting unknown device? Sounds like you need to install the kindle fire USB drivers again. Is this on linux or on windows? unknown device means that it is recognizing a device, just doesn't know what device it is.. You need the correct drivers installed for the Kindle Fire, be sure to re-install those and try again.

When I was stuck on Fastboot I just reinstalled the Drives and then changed the boot over KFU.

Hausschuh said:
When I was stuck on Fastboot I just reinstalled the Drives and then changed the boot over KFU.
Click to expand...
Click to collapse
Did you try plugging it into another PC to see if that PC detects it?

superbomb17 said:
Hello,
I know there are many similar threads but i have a slightly different issue: I was editing /system/build.prop and did a reboot and i got stuck, right after the Kindle Fire logo pops up it goes black at the time the animation is supposed to start, computer reads it fine but ADB nor Fastboot will pick it up.KWRP also doesn't work, Any help?
IMPORTANT:
I have a backup of a TESTED and WORKING build.prop, if i can mount the Kindle in windows i will be able to apply the backup and fix it that way.
FYI:
I don't exactly care about keeping my data anymore, I just want it to turn on and be usable...
Click to expand...
Click to collapse
The fact that it goes black right after the kindle fire logo makes me think it's not stuck in fastboot (would be unlikely in a build prop edit) which is why you can't get fastboot to recognize; at the same time depending on where it's failing during the boot init adb won't load either.
superbomb17 said:
I have a crazy idea and i have no idea if it will work, but it's worth a shot:
After reading the Kindle Fire breakdown, I think i can take the kindle apart and get access to it's internal SD, my questions is this: can I somehow plug it into a computer?
Click to expand...
Click to collapse
First off; I seriously doubt you would be able to mount the sd from your PC properly. Rather than cracking the device I would try booting it from a factory cable, it should hopefully force fastboot mode at which point you should be able to resolve your issues.

Acer Iconia A500 Stuck "Black Screen"

Hi,
I have an Acer A500 that I'm trying to resurrect after my son tried to root the device. I'm new to this and have checked many sites in search for a solution to this issue (if possible). I'm not sure what all my son did to this device so please bear with me. After reviewing several posts I find my issue unique where as some members may have simular issues I still have not been able to isolate my issues.
The issue: The device is stuck in APX mode with a black screen.
1) The Power Button does illuminate when powered "On" but the screen is "black". There is NO vibration when turned on.
2) The Battery life is good on this device.
3) When the device is powered "On" and connected to my PC the "Blackthund3r A500 manager" display "A500 connected in APX mode. Please Install drivers!"
4) Using Ubuntu I was able to get the "CPUID" and with "SBCalc_v1.1" I was able to get the "SBK".
5) Performing a startup utilizing reset button and On button has no effect
6) Going to "On" with the Vol + pressed has no effect
7) Using "AfterOTA 1.09" on the first "Info" tab under "Tablet Information" it displays Driver "OK driver installed", under USB it displays "ERROR - connect USB cable and enable USB debugging". Everything else displays "waiting for connection". Pressing "Reconnect Tablet" has no effect.
So far that's all I have been able to do to this unit with NO success. I welcome any feedback on this issue.

bricked tablet
best bet is to use babsector
it will install recovery and unlocked bootloader and format all the partions back to default
then you can flash updated recoveries roms etc, from there

freightyard said:
best bet is to use babsector
it will install recovery and unlocked bootloader and format all the partions back to default
then you can flash updated recoveries roms etc, from there
Click to expand...
Click to collapse
Thanks for your response. I'm not familiar with that with that program. Will it work even though the other programs show the device not being connected? (I've Used several USB cords with the same result). Where can I get that program?

you will need to install the acer usb drivers to your pc
if it's win 8/10 then you will need to first disable signature enforcement
http://forum.tegraowners.com/viewtopic.php?f=10&t=2196
babsector is a simple forum search

I complied with the driver settings and still no joy. The device stays in the APX mode and nothing seems to helps on connecting the tablet to the PC. Is there any script that will manipulate the tablet setting for connecting using Ubuntu?

can you give the steps you used to obtain the cpuid? im stuck with a black screen. have ubuntu installed on a virtual system, when i run the command for apx the file that comes back does not have the cpuid.

cpuid
Drcharles24 said:
can you give the steps you used to obtain the cpuid? im stuck with a black screen. have ubuntu installed on a virtual system, when i run the command for apx the file that comes back does not have the cpuid.
Click to expand...
Click to collapse
You can recover the CPUID by following the instructions at this link http://forum.xda-developers.com/showthread.php?t=2096826
You can then convert your CPUID to SBK with the app here http://forum.xda-developers.com/showthread.php?t=1810618

tower107 said:
You can recover the CPUID by following the instructions at this link http://forum.xda-developers.com/showthread.php?t=2096826
You can then convert your CPUID to SBK with the app here http://forum.xda-developers.com/showthread.php?t=1810618
Click to expand...
Click to collapse
thanks for the reply. i was already trying out all of those guides. it didn't work at first but i changed a few lines of coding and it worked!!! i was using a 32bit ubuntu, made the suggested changes and also added a different line elsewhere. if anyone needs the apx.c file i used with all the changes already made. let me know.

Trying to unlock kindle fire hd 8 8th gen

Hello all,
I'm at my wits end. Been trying for hours to unlock my new kindle fire hd 8 8th gen. Tried to do the mtk-su method which didn't work because my firmware is 6.3.1.4 Also tried the short circuit method and for some reason everytime I run the ./bootrom-step.sh nothing happens. I know I'm being very thorough with the instructions but I get stuck at this step. The prompt always starts at "Waiting for bootrom" I have no idea why it's being difficult with the HD8 when hours ago I unlocked the kindle fire 7 9th gen just fine using the short circuit method as well. Am I doing something wrong? Please help. Thanks in advance

Yes i have one of these too...
Are you running the bootrom-step, then shorting the clk to ground (shield), while plugging in the usb? When you plug it in, does it just boot up or does it go blank screen?
Just to clarify, you should have
"waiting for bootrom" on the PC
Then short the clk to ground
Plug in USB
Seems like a few people had to use a different USB port sometimes

Michajin said:
Yes i have one of these too...
Are you running the bootrom-step, then shorting the clk to ground (shield), while plugging in the usb? When you plug it in, does it just boot up or does it go blank screen?
Just to clarify, you should have
"waiting for bootrom" on the PC
Then short the clk to ground
Plug in USB
Seems like a few people had to use a different USB port sometimes
Click to expand...
Click to collapse
I run the bootrom-step, short the CLK while plugging the usb. When plugged, it doesn't boot up it just goes black screen. Every so often it will boot up but it's rather rare (while im performing the short)
Other than that, the kindle will boot up normally but not when I NEED it to :crying:

Reiixas said:
I run the bootrom-step, short the CLK while plugging the usb. When plugged, it doesn't boot up it just goes black screen. Every so often it will boot up but it's rather rare (while im performing the short)
Other than that, the kindle will boot up normally but not when I NEED it to :crying:
Click to expand...
Click to collapse
It should stay black when in the bootrom. What linux are you using? is it a live disk or Virtual disk? run lsusb (you should see MediaTek Inc. MT6227 phone) I have seen issues with this. I personally have been using this ...
https://github.com/amonet-kamakiri/fireiso/releases
It was developed for the firestick 4k but is all set up to run.
It could be a driver issue that isn't recognizing your hd8

Michajin said:
It should stay black when in the bootrom. What linux are you using? is it a live disk or Virtual disk? run lsusb (you should see MediaTek Inc. MT6227 phone) I have seen issues with this. I personally have been using this ...
https://github.com/amonet-kamakiri/fireiso/releases
It was developed for the firestick 4k but is all set up to run.
It could be a driver issue that isn't recognizing your hd8
Click to expand...
Click to collapse
I'm using Linux Mint live disk. Will look into that and let you know. Thank you for your help

Michajin said:
It should stay black when in the bootrom. What linux are you using? is it a live disk or Virtual disk? run lsusb (you should see MediaTek Inc. MT6227 phone) I have seen issues with this. I personally have been using this ...
https://github.com/amonet-kamakiri/fireiso/releases
It was developed for the firestick 4k but is all set up to run.
It could be a driver issue that isn't recognizing your hd8
Click to expand...
Click to collapse
Sorry to bother again, kind of a noob. What am I supposed to do with that fireiso?

Reiixas said:
Sorry to bother again, kind of a noob. What am I supposed to do with that fireiso?
Click to expand...
Click to collapse
Burn it to a USB flash drive. I use etcher to make a live disk...
https://www.balena.io/etcher/
Once complete reboot select removable media as a boot device.
---------- Post added at 11:38 AM ---------- Previous post was at 11:29 AM ----------
BTW, if you run lsusb from a command prompt you should see "MediaTek Inc. MT6227 phone" this is the bootrom, if you see "MediaTek Inc. MT65xx Preloader" you need to short it again. If the screen is black after you plug in, chances are you in preloader or the bootrom.

Michajin said:
Burn it to a USB flash drive. I use etcher to make a live disk...
https://www.balena.io/etcher/
Once complete reboot select removable media as a boot device.
---------- Post added at 11:38 AM ---------- Previous post was at 11:29 AM ----------
BTW, if you run lsusb from a command prompt you should see "MediaTek Inc. MT6227 phone" this is the bootrom, if you see "MediaTek Inc. MT65xx Preloader" you need to short it again. If the screen is black after you plug in, chances are you in preloader or the bootrom.
Click to expand...
Click to collapse
Hello,
Thank you for the help. I'm running the FireOS iso you sent. However, I'm stuck now on the fastboot step. Whenever I run ./fastboot-step.sh I get this output:
[[email protected] ~/Downloads/amonet]# ./fastboot-step.sh
fastboot: core/libsparse/sparse.cpp:131: int write_all_blocks(struct sparse_file *, struct output_file *): Assertion `pad >= 0' failed.
./fastboot-step.sh: line 5: 2468 Aborted (core dumped) fastboot flash boot bin/recovery-inj.img
[[email protected] ~/Downloads/amonet]#
Also, the kindle has the amazon logo , nothing else.

Reiixas said:
Hello,
Thank you for the help. I'm running the FireOS iso you sent. However, I'm stuck now on the fastboot step. Whenever I run ./fastboot-step.sh I get this output:
[[email protected] ~/Downloads/amonet]# ./fastboot-step.sh
fastboot: core/libsparse/sparse.cpp:131: int write_all_blocks(struct sparse_file *, struct output_file *): Assertion `pad >= 0' failed.
./fastboot-step.sh: line 5: 2468 Aborted (core dumped) fastboot flash boot bin/recovery-inj.img
[[email protected] ~/Downloads/amonet]#
Also, the kindle has the amazon logo , nothing else.
Click to expand...
Click to collapse
I've fixed this by running a debian based linux. I'm officially rooted. THANK YOU!
By any chance is there any lineage OS thread for this HD8 8th gen?

Reiixas said:
I've fixed this by running a debian based linux. I'm officially rooted. THANK YOU!
By any chance is there any lineage OS thread for this HD8 8th gen?
Click to expand...
Click to collapse
LineageOS for Fire HD 8 (2018):
7.1.2 Nougat: https://forum.xda-developers.com/hd8-hd10/orig-development/lineageos-14-1-fire-hd8-2018-t3936242
9 Pie: https://forum.xda-developers.com/hd8-hd10/orig-development/rom-lineage-16-0-t3981685
Can you flash it from TWRP.

Reiixas said:
I've fixed this by running a debian based linux. I'm officially rooted. THANK YOU!
By any chance is there any lineage OS thread for this HD8 8th gen?
Click to expand...
Click to collapse
Awesome.. Give me a few thanks for the help please...
I would recommend for stable build
[ROM][unlocked][karnak] Lineage-14.1 [02 JAN 2020]
https://forum.xda-developers.com/hd8-hd10/orig-development/lineageos-14-1-fire-hd8-2018-t3936242
I wouldn't do anything with 16.0 as the OP is getting close to having a good LOS 17.1 and 16 is still pretty buggy.
Don't forget- Make a backup before you do anything to give you a safe place to restore to.

Help for root/ unlock HD8
Hi! I am newbie in here. I am find the way how to root HD8 ( 8th generation) fire os 6.3.1.4 and Install Android OS. Can anyone help me?
Thank you very much!

Alesksel said:
Hi! I am newbie in here. I am find the way how to root HD8 ( 8th generation) fire os 6.3.1.4 and Install Android OS. Can anyone help me?
Thank you very much!
Click to expand...
Click to collapse
Start here
Fire HD 8 (2018 ONLY) unbrick, downgrade, unlock & root
https://forum.xda-developers.com/hd...fire-hd-8-2018-downgrade-unlock-root-t3894256
You will have to do the hardware method (it's easy)
Software method - Amazon Fire HD 8 2018 -- up to Fire OS 6.3.0.1 only
Read the thread if you have questions, I can try and help if you need it....

<Yet another snip>