Trouble with the fast boot. - Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot

hello i am using fire hdx 3rd gen, I am on fire os 4.5.5.3, I am trying to install TWRP, i can do adb devices and find my device, when I use 'fastboot flash recovery twrp.img, the kindle restarts and goes to a screen showing fastboot ready, but I still see 'waiting for device' on my pc. Please help.

bluejaysrs said:
hello i am using fire hdx 3rd gen, I am on fire os 4.5.5.3, I am trying to install TWRP, i can do adb devices and find my device, when I use 'fastboot flash recovery twrp.img, the kindle restarts and goes to a screen showing fastboot ready, but I still see 'waiting for device' on my pc. Please help.
Click to expand...
Click to collapse
There are so many things unstated/wrong it's hard to know where to start.
- rooted?
- vulnerable aboot/bootloader installed?
- using twrp image w/forged signature?
- experience dealing with windows driver issues?
Transforming this Amazon device into a generic Android gizmo is technically challenging and not for the faint of heart. You'll need to so your homework (likely hours of reading) as no one here is going to handhold as you stumble through the basics.
Start here; follow suggested links:
https://forum.xda-developers.com/kindle-fire-hdx/help/bootloader-unlock-twrp-guides-t3802443
I recommend these drivers:
https://motorola-global-en-aus.custhelp.com/app/answers/prod_detail/a_id/86934/p/154,4222

Davey126 said:
There are so many things unstated/wrong it's hard to know where to start.
- rooted?
- vulnerable aboot/bootloader installed?
- using twrp image w/forged signature?
- experience dealing with windows driver issues?
Transforming this Amazon device into a generic Android gizmo is technically challenging and not for the faint of heart. You'll need to so your homework (likely hours of reading) as no one here is going to handhold as you stumble through the basics.
Start here; follow suggested links:
https://forum.xda-developers.com/kindle-fire-hdx/help/bootloader-unlock-twrp-guides-t3802443
I recommend these drivers:
https://motorola-global-en-aus.custhelp.com/app/answers/prod_detail/a_id/86934/p/154,4222
Click to expand...
Click to collapse
Thanks for guiding me through the required documentation. I have successfully followed the below link and did bootloader unlock and did get twrp and flashed a custom ROM, could you please guide me to any Oreo based custom ROM for my device? Thanks.
https://forum.xda-developers.com/showpost.php?p=75284993&postcount=1006

bluejaysrs said:
Thanks for guiding me through the required documentation. I have successfully followed the below link and did bootloader unlock and did get twrp and flashed a custom ROM, could you please guide me to any Oreo based custom ROM for my device? Thanks.
https://forum.xda-developers.com/showpost.php?p=75284993&postcount=1006
Click to expand...
Click to collapse
Nougat only at present. My preference is AEX but many like Lineage. Can't go wrong with either choice.

Related

Stuck in fastboot trying to install CM

Hey everyone I have a kindle fire 3rd gen HDX 7" and my ultimate goal is to install a CyanogenMod OS instead of the stock fire OS. I have been following a youtube guide on installing CM and I was able to get it rooted. The guide instructed that I use an app called "fireflash" to flash TWRP, then install CM from there. Unfortunately I was unable to get fireflash to work, so I downloaded an app called "flashify" to flash "TWRP" as the recovery partition and "U-Boot" as the boot partition, as per the video's instructions.
Once I hit the flash button, the kindle for some reason booted into fastboot mode and it has been there ever since. After some research, I have tried to interact with my device in fastboot mode, but only commands that begin with “fastboot -i 0x1949” will work, and will not boot back into the stock OS, but instead gives the error message “FAIL: oem idme not allowed for locked hw.” When I give the command “adb devices”, nothing shows up. Also, when I try to flash TWRP, the command prompt simply tells me that the recovery image cannot be loaded. I am assuming that I need to unlock my bootloader to proceed, but I would appreciate it if someone could confirm this.
Sorry if this is a little long, but I wanted to be thorough. Can anyone suggest a way to either get back into stock fire os so I can start over, or proceed to install TWRP and CM in fastboot mode?
tropicallazerbeams said:
Hey everyone I have a kindle fire 3rd gen HDX 7" and my ultimate goal is to install a CyanogenMod OS instead of the stock fire OS. I have been following a youtube guide on installing CM and I was able to get it rooted. The guide instructed that I use an app called "fireflash" to flash TWRP, then install CM from there. Unfortunately I was unable to get fireflash to work, so I downloaded an app called "flashify" to flash "TWRP" as the recovery partition and "U-Boot" as the boot partition, as per the video's instructions.
Once I hit the flash button, the kindle for some reason booted into fastboot mode and it has been there ever since. After some research, I have tried to interact with my device in fastboot mode, but only commands that begin with “fastboot -i 0x1949” will work, and will not boot back into the stock OS, but instead gives the error message “FAIL: oem idme not allowed for locked hw.” When I give the command “adb devices”, nothing shows up. Also, when I try to flash TWRP, the command prompt simply tells me that the recovery image cannot be loaded. I am assuming that I need to unlock my bootloader to proceed, but I would appreciate it if someone could confirm this.
Sorry if this is a little long, but I wanted to be thorough. Can anyone suggest a way to either get back into stock fire os so I can start over, or proceed to install TWRP and CM in fastboot mode?
Click to expand...
Click to collapse
Unfortunately, there is little chance of recovery given the steps taken and symptoms exhibited. Fireflash is not compatible with HDX devices and almost always yields a brick. Sorry to break the news.
Hey thanks for the reply, I was afraid of the whole brick thing, but i will be more careful next time. I have learned my lesson! Luckily for me, I just got off the phone with Amazon customer support and they are willing to send me a new one. They didnt even ask if I had rooted it or anything, just whether or not I had dropped it or poured anything on it. So that being said, does anyone know of an accepted, working method to install CM on a Kindle Fire HDX 7" Thor that would be willing to provide a link or two? Thanks!
tropicallazerbeams said:
Hey thanks for the reply, I was afraid of the whole brick thing, but i will be more careful next time. I have learned my lesson! Luckily for me, I just got off the phone with Amazon customer support and they are willing to send me a new one. They didnt even ask if I had rooted it or anything, just whether or not I had dropped it or poured anything on it. So that being said, does anyone know of an accepted, working method to install CM on a Kindle Fire HDX 7" Thor that would be willing to provide a link or two? Thanks!
Click to expand...
Click to collapse
Yep - CM11, CM12 and/or Nexus v4 can be installed on most HDX models. You need to do some prep work up front the nature and magnitude determined by the version of FireOS on your replacement unit. Post back when you get it and someone will guide you through the process.

Have TWRP but not root HDX 8.9 3rd gen

I got a new Motherboard and daughterboard in my HDX Apollo. I was able to get TWRP on it, but it keeps saying i dont appear to have root. I tried installing the latest supersu but it apparently didnt work. Anyway, i have realized that i just keep getting myself into trouble playing with root. All i want is to get my 3rd gen back to 4.5.5.1 fire os and wait for the fire os 5 update for it(hopefully) Any help on how i can do that? Ive tried downloading the latest Kindle update for apollo, renaming the .bin to update.zip and transferring it over and installing it but it never boots further than the 'kindle' screen.
Thanks for your help, sorry to be a pain
If you're on Fire OS 4.x you don't have TWRP, but Safestrap v4. After what you've done, do you still have access to Safestrap? Installing an amazon update with Safestrap installed, or even just rooted could easily mess up the device, i.e. brick it.
I don't think it's fire os 4x then. It does boot into the twrp interface and is fully functional but when you go to reboot into a different recovery it says something like "it appears you do not have root. Would you like to install supersu?" Even if I say yes it acts like it installs but apparently doesn't. I can post pics later
Sent from my SM-G920V using XDA-Developers mobile app
Cl4ncy said:
If you're on Fire OS 4.x you don't have TWRP, but Safestrap v4. After what you've done, do you still have access to Safestrap? Installing an amazon update with Safestrap installed, or even just rooted could easily mess up the device, i.e. brick it.
Click to expand...
Click to collapse
Oh and I'm not sure what the new board had on it. It never fully booted. That's why I installed twrp. Thanks for the reply though!
Sent from my SM-G920V using XDA-Developers mobile app
mhuck0625 said:
I don't think it's fire os 4x then. It does boot into the twrp interface and is fully functional but when you go to reboot into a different recovery it says something like "it appears you do not have root. Would you like to install supersu?" Even if I say yes it acts like it installs but apparently doesn't. I can post pics later
Click to expand...
Click to collapse
mhuck0625 said:
Oh and I'm not sure what the new board had on it. It never fully booted. That's why I installed twrp. Thanks for the reply though!
Click to expand...
Click to collapse
- how did you "install" TWRP (method)?
- how are you accessing TWRP - just pressing the power button or some key combination (yes, it's important)?
- does a graphic vaguely resembling Frankenstein appear when you power up the device?
Davey126 said:
- how did you "install" TWRP (method)?
- how are you accessing TWRP - just pressing the power button or some key combination (yes, it's important)?
- does a graphic vaguely resembling Frankenstein appear when you power up the device?
Click to expand...
Click to collapse
I installed TWRP using the method instructed here: http://forum.xda-developers.com/kin...-to-unbrick-kindle-fire-hdx-firmware-t3277197
When i want to get to TWRP i press and hold Power + Vol UP until it rebootes into the Teamwin screen and TWRP. It is version 2.8.7.0 now(the instructions got 2.8.5.0 installed then i upgraded)
I dont remember what the graphic looked like when booting into TWRP but i know it said TeamWin. I can check when i get it charged back up enough to turn on. Ive had it sitting unplugged for days and the battery ran dead. I hope this is enough info to help get me pointed in the right direction. Thanks!
Ok, if it's the real TWRP which it seems to be, Safestrap has no TeamWin logo at boot, I'd suggest you leave it be. Currently you can use all available ROMs, so if there'll be a future version of Fire OS you could use a TWRP flashable version of it. I doubt there will be a Fire OS 5 update for the "old" Thor/Apollo line though.
You would destroy the possibilities you currently have by updating to Fire OS 4.5.5.1.
Meanwhile you can unlock your bootloader (if you haven't already), and update TWRP to 3.0.0-1 (requires unlocked bootloader).
Don't I need root though? How can I unlock my bootloader from the stage I'm at now? I'm just a bit afraid of proceeding in case I brick it again
Sent from my SM-G920V using XDA-Developers mobile app
Cl4ncy said:
Ok, if it's the real TWRP which it seems to be, Safestrap has no TeamWin logo at boot, I'd suggest you leave it be. Currently you can use all available ROMs, so if there'll be a future version of Fire OS you could use a TWRP flashable version of it. I doubt there will be a Fire OS 5 update for the "old" Thor/Apollo line though.
You would destroy the possibilities you currently have by updating to Fire OS 4.5.5.1.
Meanwhile you can unlock your bootloader (if you haven't already), and update TWRP to 3.0.0-1 (requires unlocked bootloader).
Click to expand...
Click to collapse
Don't I need root though? How can I unlock my bootloader from the stage I'm at now? I'm just a bit afraid of proceeding in case I brick it again
Sent from my SM-G920V using XDA-Developers mobile app
There's no risk in unlocking, the bootloader either unlocks or it errors/fails. Try the one-click-solution first (might require the PDANet drivers). It's recommended to update the bootloader to 3.2.3.2 (do it only, if the unlock worked ok).
TWRP can be updated from TWRP itself, so I'd recommend doing it that way. Just be sure to flash the TWRP image to the recovery partition.
Cl4ncy said:
There's no risk in unlocking, the bootloader either unlocks or it errors/fails. Try the one-click-solution first (might require the PDANet drivers). It's recommended to update the bootloader to 3.2.3.2 (do it only, if the unlock worked ok).
TWRP can be updated from TWRP itself, so I'd recommend doing it that way. Just be sure to flash the TWRP image to the recovery partition.
Click to expand...
Click to collapse
Tried 1-Click. In both Linux(Ubuntu 16.04) and Windows(10.1 x64) i get an error saying ADB is not enabled on the device. Ive tried booting into fastboot(with fastboot cable) tried using the regular cable and booting into TWRP. Any combination of boot modes and cables i can think of wont work. Where should i go from here?
Thanks
mhuck0625 said:
Don't I need root though? How can I unlock my bootloader from the stage I'm at now? I'm just a bit afraid of proceeding in case I brick it again
Click to expand...
Click to collapse
Root is irrelevant at this stage as nothing has been flashed to the system partition (where ROMs live).
Davey126 said:
Root is irrelevant at this stage as nothing has been flashed to the system partition (where ROMs live).
Click to expand...
Click to collapse
Ok, so i will need root to install ROMs then? How do i solve my problem unlocking the bootloader?
mhuck0625 said:
Tried 1-Click. In both Linux(Ubuntu 16.04) and Windows(10.1 x64) i get an error saying ADB is not enabled on the device. Ive tried booting into fastboot(with fastboot cable) tried using the regular cable and booting into TWRP. Any combination of boot modes and cables i can think of wont work. Where should i go from here?
Thanks
Click to expand...
Click to collapse
Lack of a functioning ROM could prove problematic if ADB is not enabled. I do not recall if the version of TWRP you installed provides native support for MTP which is essential for moving files onto the device. You may need to go the manual route to unlock bootloader which still requires tethered access but only at the fastboot level.
Nearing the edge of my pay grade on this topic; looking for others with more recent experience to jump in...
Davey126 said:
Lack of a functioning ROM could prove problematic if ADB is not enabled. I do not recall if the version of TWRP you installed provides native support for MTP which is essential for moving files onto the device. You may need to go the manual route to unlock bootloader which still requires tethered access but only at the fastboot level.
Nearing the edge of my pay grade on this topic; looking for others with more recent experience to jump in...
Click to expand...
Click to collapse
I do have mtp access and can transfer files easily. Should I try installing a Rom to see if I get adb access? What's a good Rom to try
Sent from my SM-G920V using XDA-Developers mobile app
Davey126 said:
Lack of a functioning ROM could prove problematic if ADB is not enabled. I do not recall if the version of TWRP you installed provides native support for MTP which is essential for moving files onto the device. You may need to go the manual route to unlock bootloader which still requires tethered access but only at the fastboot level.
Nearing the edge of my pay grade on this topic; looking for others with more recent experience to jump in...
Click to expand...
Click to collapse
Just curious on one thing. Whenever i see a ROM to download it says i need to unlock the bootloader and have root before i can do that. In MY case i do NOT have either, yet i was able to flash a new recovery(TWRP) How is this possible? How would i go about installing a new ROM or unlocking the bootloader?
Is there a way to flash the stock recovery back so i can reinstall fireOS and start from scratch?
Is there a way to tell what bootloader i have from within TWRP?
I realize i probably should have done a little more reading before i started messing with it :/ I do appreciate all the help you have been able to provide so far!
mhuck0625 said:
I do have mtp access and can transfer files easily. Should I try installing a Rom to see if I get adb access? What's a good Rom to try
Click to expand...
Click to collapse
mhuck0625 said:
Just curious on one thing. Whenever i see a ROM to download it says i need to unlock the bootloader and have root before i can do that. In MY case i do NOT have either, yet i was able to flash a new recovery(TWRP) How is this possible? How would i go about installing a new ROM or unlocking the bootloader?
Is there a way to flash the stock recovery back so i can reinstall fireOS and start from scratch?
Is there a way to tell what bootloader i have from within TWRP?
I realize i probably should have done a little more reading before i started messing with it :/ I do appreciate all the help you have been able to provide so far!
Click to expand...
Click to collapse
- traveling; response will be brief
- suggest flashing cm11 as it does not require an unlocked bootloader nor GAaps for basic functionality
- include SuperSU in flash package to secure root
- follow flashing directions in cm11 OP
- report back results; will go from there
Davey126 said:
- traveling; response will be brief
- suggest flashing cm11 as it does not require an unlocked bootloader nor GAaps for basic functionality
- include SuperSU in flash package to secure root
- follow flashing directions in cm11 OP
- report back results; will go from there
Click to expand...
Click to collapse
Downloaded CM11 and installed via this thread
http://forum.xda-developers.com/kin...-cm-11-safestrap-20150628-unofficial-t3145547
Copied it as well as the latest SuperSu(v2.65) to the Kindle Fire
Went to Install, saw both Zip files. Selected them(CM11 first, then Supersu second) Swipe to install, rebooted and nothing came up. Rebooted into TWRP and repeated the process after wiping dalvik/cache. Still nothing
mhuck0625 said:
Downloaded CM11 and installed via this thread
http://forum.xda-developers.com/kin...-cm-11-safestrap-20150628-unofficial-t3145547
Copied it as well as the latest SuperSu(v2.65) to the Kindle Fire
Went to Install, saw both Zip files. Selected them(CM11 first, then Supersu second) Swipe to install, rebooted and nothing came up. Rebooted into TWRP and repeated the process after wiping dalvik/cache. Still nothing
Click to expand...
Click to collapse
Makes sense. Likely no kernel. Will probably need to install a full version of FireOS for underlying components. Need to have a think about which build to maximize results, minimize rework. More later....
Davey126 said:
Makes sense. Likely no kernel. Will probably need to install a full version of FireOS for underlying components. Need to have a think about which build to maximize results, minimize rework. More later....
Click to expand...
Click to collapse
You have no idea how much i appreciate the help!
I look forward to hearing what you come up with!!
I would be happy just going straight back to full fire os - Stock EVERYTHING and not even worrying about running another OS. I just want to have a usable tablet again!

Kindle HDX Stuck in Boot Loop - TWRP and connection to PC working

Dear forum,
I had installed the Nexus Custom ROM with TWRP on my Kindle HDX which worked out fine so far. Then I and wanted to go to CM11. Probably because my device was still locked and/or because I wiped too many things in the wipe-menu, my kindle is stuck in the Boot loop and stops loading while displaying the grey kindle logo. I am still able to access TWRP and the device is found by windows.
I would like to go back to the stock rom and read a lot of threads in the forum but I am not really sure where to start without making my situation worse. I tried to install back my backup (several *.win files) but that does not work. Can you please help me what I need to do?
Kind regards,
Aldaris001
Aldaris001 said:
Dear forum,
I had installed the Nexus Custom ROM with TWRP on my Kindle HDX which worked out fine so far. Then I and wanted to go to CM11. Probably because my device was still locked and/or because I wiped too many things in the wipe-menu, my kindle is stuck in the Boot loop and stops loading while displaying the grey kindle logo. I am still able to access TWRP and the device is found by windows.
I would like to go back to the stock rom and read a lot of threads in the forum but I am not really sure where to start without making my situation worse. I tried to install back my backup (several *.win files) but that does not work. Can you please help me what I need to do?
Kind regards,
Aldaris001
Click to expand...
Click to collapse
TWRP or Safestrap (version)? They are not the same thing. Makes a big difference in the potential solution set.
Thanks for your swift reply! I have TWRP 2.8.6.0 installed.
Aldaris001 said:
Thanks for your swift reply! I have TWRP 2.8.6.0 installed.
Click to expand...
Click to collapse
Strongly recommend unlocking bootloader with 1-click utility (here). Otherwise you run the risk of permanently bricking your device if the recovery partition holding TWRP becomes damaged/unbootable. Once unlocked you can flash a modified build of FireOS 4.5.5 from here
Of course, once unlocked you could flash a higher version of Nexus, CM 11 (both KitKat based), CM 12.1 (Lollipop), CM 13 (Marshmallow) or several other rom variants. Each is a heck of a lot better than Stock FireOS v4.
At some point you should also consider moving to the latest version of TWRP (here).
Hi Davey,
Thanks a lot for the hint! I have tried the 1-click bootloader but running in an issue that the ADB device is not recognized. The drivers seem to work though. Do I need to activate ADB in TWRP somewhere or is it activated by default? The ADB sideload option seem to be something else, right?
Aldaris001 said:
Hi Davey,
Thanks a lot for the hint! I have tried the 1-click bootloader but running in an issue that the ADB device is not recognized. The drivers seem to work though. Do I need to activate ADB in TWRP somewhere or is it activated by default? The ADB sideload option seem to be something else, right?
Click to expand...
Click to collapse
Drivers are always a PiTA with Windows and Amazon devices. You'll need to fight through it taking clues from various posts on the topic. Some tips:
- nothing needs to be enabled in TWRP
- drivers need to work in both ADB and Fastboot modes
- cleanest approach IMO:
>> launch windows device manager, tether device, see what shows up in device manager, uninstall those device(s), disconnect, reboot both devices (important), reconnect and then guide windows to the drivers of your choosing
Thanks a lot for your help, I got it running again! In the end it did not work with the 1-click method but manually I could unlock the bootloader and flashed CM 12.1.
Aldaris001 said:
Thanks a lot for your help, I got it running again! In the end it did not work with the 1-click method but manually I could unlock the bootloader and flashed CM 12.1.
Click to expand...
Click to collapse
Thanks for the update. Glad you got things sorted; manual unlocking isn't that bad with a little patience. CM 12.1 is solid (probably my next stop; still rocking Nexus) but keep an eye on CM 13 as the dev team hammers out a few final issues. Enjoy your liberated HDX!

Please help me, Kindle fire HDX 8.9"

Hi all,
I have problem when I up Rom on HDX 8.9". Now It can't be boot, only show Kindle fire. So I don't know what to do. Please help me
http://i42.photobucket.com/albums/e311/ngoctrongda/19046577_10213989916917163_1609891189_n.jpg
sunflowervn said:
Hi all,
I have problem when I up Rom on HDX 8.9". Now It can't be boot, only show Kindle fire. So I don't know what to do. Please help me
http://i42.photobucket.com/albums/e311/ngoctrongda/19046577_10213989916917163_1609891189_n.jpg
Click to expand...
Click to collapse
- which ROM and how was it installed (TWRP, safestrap, fastboot)?
- did you unlock the bootloader?
- can you boot into recovery? If so is it 'stock' or TWRP?
I have exactly the same problem with my HDX 8.9" a few months ago. The screen shows "kindle fire" like sunflowervn's photo for a minute or so, disappears for a few seconds and "kindle fire" appears again. The cycle kept on repeating and I cannot use the tablet. I haven't installed any other ROM and cannot boot into recovery mode.
newbie2018 said:
I have exactly the same problem with my HDX 8.9" a few months ago. The screen shows "kindle fire" like sunflowervn's photo for a minute or so, disappears for a few seconds and "kindle fire" appears again. The cycle kept on repeating and I cannot use the tablet. I haven't installed any other ROM and cannot boot into recovery mode.
Click to expand...
Click to collapse
HDX devices running FireOS are susceptible to this type of bootloop. Typically happens after a botched update although there can be other triggers. There may be a way out if the device can be coaxed into 'bulk mode' which may not be easy. Proceeding from there also requires some experience and patience working in terminal mode. There is no step-by-step guide; you'll to do some reading to work through inevitable obstacles. All personal data will be erased. The end result will be an unlocked device that can load a custom ROM. While returning to FireOS is technically possible it is not a practical path for most.
While the above process sounds ominous dozens have made the journey. It really boils down to personal commitment. People in the forums can point to resources but you'll have to do the heavy lifting.
Davey126 said:
- which ROM and how was it installed (TWRP, safestrap, fastboot)?
- did you unlock the bootloader?
- can you boot into recovery? If so is it 'stock' or TWRP?
Click to expand...
Click to collapse
I have unlock bootloader and install safestrap 4.0
I think I have flash rom in Stock partition, but it has failed. I try press both Power and volume up, I can log in System recovery (http://i42.photobucket.com/albums/e311/ngoctrongda/27747057_10214009730732496_2093684281_o.jpg), But I reset to Factory Default, It has no change when reboot.
Are there any software which I can connect with kindle in fastboot ?
sunflowervn said:
I have unlock bootloader and install safestrap 4.0
I think I have flash rom in Stock partition, but it has failed. I try press both Power and volume up, I can log in System recovery (http://i42.photobucket.com/albums/e311/ngoctrongda/27747057_10214009730732496_2093684281_o.jpg), But I reset to Factory Default, It has no change when reboot.
Are there any software which I can connect with kindle in fastboot ?
Click to expand...
Click to collapse
If you're asking how to connect in fastboot then I doubt the bootloader is unlocked. Also makes no sense to install SafeStrap with an unlocked bootloader.
Really not sure how to help as you've created quite a mess. To recover you'll have to place the device in 'bulk mode' and rebuild it from there. Messy procedure for noobs.
Davey126 said:
If you're asking how to connect in fastboot then I doubt the bootloader is unlocked. Also makes no sense to install SafeStrap with an unlocked bootloader.
Really not sure how to help as you've created quite a mess. To recover you'll have to place the device in 'bulk mode' and rebuild it from there. Messy procedure for noobs.
Click to expand...
Click to collapse
Can you show me steps to do, I think I can.
Thank you.
sunflowervn said:
Can you show me steps to do, I think I can.
Thank you.
Click to expand...
Click to collapse
Information is disorganized and scattered across multiple threads. You can start here and see where that takes you. Suggest you read, research and understand before taking any action as you'll likely end up in worse spot just 'trying stuff'. Good luck.

Newest bootloader unlock/TWRP guides?

I've been doing a lot of research and following some guides and I Have searched some posts here, but there's insutrctions burried inside of threads that are 75+ pages long and I hate to jump in the middle of a thread when I don't know any context.
I'm trying to flash LineageOS on a 3rd gen 8.9" (apollo) kindle. It's rooted and I'm running software 4.5.5.3.
I have done firmware flashing before, so I'm not new to this. My primary OS is linux and I just used ADB and fastboot there to fix my phone. I have a windows machine with fastboot and all the tools as well. I just need access to the proper instructions.
That's the keyword, PROPER Instructions. I don't want to jump in the middle of a thread with some instructions from an older software release that will brick my kindle.
RNZL3R said:
I've been doing a lot of research and following some guides and I Have searched some posts here, but there's insutrctions burried inside of threads that are 75+ pages long and I hate to jump in the middle of a thread when I don't know any context.
I'm trying to flash LineageOS on a 3rd gen 8.9" (apollo) kindle. It's rooted and I'm running software 4.5.5.3.
I have done firmware flashing before, so I'm not new to this. My primary OS is linux and I just used ADB and fastboot there to fix my phone. I have a windows machine with fastboot and all the tools as well. I just need access to the proper instructions.
That's the keyword, PROPER Instructions. I don't want to jump in the middle of a thread with some instructions from an older software release that will brick my kindle.
Click to expand...
Click to collapse
Appreciate the upfront legwork.
HDX bootloader must be unlocked to install a non-KitKat based custom ROM. Fortunately, that's an easy task given your familiarity with Linux. PM the OP in the linked thread for a copy of the 1-click unlock script. Same tool can also flash an appropriate TWRP image which is the preferred method for flashing custom ROM on this device. Bounce back with any immediate questions.
https://forum.xda-developers.com/kindle-fire-hdx/general/multi-platform-1-click-bootloader-t3241014
Davey126 said:
Appreciate the upfront legwork.
HDX bootloader must be unlocked to install a non-KitKat based custom ROM. Fortunately, that's an easy task given your familiarity with Linux. PM the OP in the linked thread for a copy of the 1-click unlock script. Same tool can also flash an appropriate TWRP image which is the preferred method for flashing custom ROM on this device. Bounce back with any immediate questions.
https://forum.xda-developers.com/kindle-fire-hdx/general/multi-platform-1-click-bootloader-t3241014
Click to expand...
Click to collapse
I did read through the first few pages of that thread. Why doesn't the Op just post the link up instead of dealing with PMs? I found that sketchy
RNZL3R said:
I did read through the first few pages of that thread. Why doesn't the Op just post the link up instead of dealing with PMs? I found that sketchy
Click to expand...
Click to collapse
Members don't read, misuse the tools, fain rage and demand support. There's always the manual approach if you prefer not to engage OP. I rarely post my work (here) for similar reasons.
Davey126 said:
Members don't read, misuse the tools, fain rage and demand support. There's always the manual approach if you prefer not to engage OP. I rarely post my work (here) for similar reasons.
Click to expand...
Click to collapse
I got the 1-click file, and...well....it isn't detecting my kindle. Developer options is enabled, and ADB is on. It's plugged in and fully charged. yet, 1-click says there's no device detected.
RNZL3R said:
I got the 1-click file, and...well....it isn't detecting my kindle. Developer options is enabled, and ADB is on. It's plugged in and fully charged. yet, 1-click says there's no device detected.
Click to expand...
Click to collapse
Have you validated the Linux host can see and communicate with the HDX when 'manually' tethered? Obviously that's a prerequisite. If not try a different cable (often the culprit!) along with different USB ports. Avoid external hubs. If still no joy try tethering to a different host (regardless of OS) to rule out a bad port on the tablet.
Davey126 said:
Have you validated the Linux host can see and communicate with the HDX when 'manually' tethered? Obviously that's a prerequisite. If not try a different cable (often the culprit!) along with different USB ports. Avoid external hubs. If still no joy try tethering to a different host (regardless of OS) to rule out a bad port on the tablet.
Click to expand...
Click to collapse
The tablet is definitely detected and I can browse the storage. It just doesn't get detected by the 1click.
Are there any other ways to unlock the boot loader and flash a Rom?
RNZL3R said:
The tablet is definitely detected and I can browse the storage. It just doesn't get detected by the 1click.
Click to expand...
Click to collapse
Reach out to the 1-click developer; he's pretty knowledgeable/resourceful and can probably help.
RNZL3R said:
Are there any other ways to unlock the boot loader and flash a Rom?
Click to expand...
Click to collapse
Linked 3 posts back.
I have followed this guide from @ReichMann and successfully unlock bootloader, install TWRP and get my HDX run both Apollo and Thor running Nougat in 1st try with no problem, he also attached all the file you'll need:
https://forum.xda-developers.com/showpost.php?p=75284993&postcount=1006
RNZL3R said:
The tablet is definitely detected and I can browse the storage. It just doesn't get detected by the 1click.
Are there any other ways to unlock the boot loader and flash a Rom?
Click to expand...
Click to collapse
I had some issues with Virtual box on Ubuntu. In case you are using a similar setup, check this post:https://forum.xda-developers.com/showpost.php?p=76730389&postcount=346

Categories

Resources