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.
Related
I am on rooted Thor with 13.3.2.4, with the Nexus Rom installed via safestrap. I have been reading all the threads on unlocking the bootloader and find all of the steps to be very scary. I would like to wait until there was some kind of "toolkit" for this rather than having to first downgrade and then use python through adb etc which I am somewhat uncomfortable with. Will there ever be such a simpler solution?
The bootloader unlock procedure is a no brainer, can't mess up anything there. Downgrading is a little risky, but you're on 3.2.4, thus you can even use the rollback images for Safestrap, take a look at this thread (page 1 is about 3.2.5/3.2.6 users who can NOT use the downgrade images). I'm afraid it won't get any easier than that.
If you don't want to use Python, just execute the adb commands to get your ID and serial (post them here, or PM me if you don't want anyone to see them), I'll create the .unlock file for you then. Downgrading and (actual) unlocking are tasks you have to do yourself though.
I think I might try it this weekend. Thanks for the help.
Cl4ncy said:
The bootloader unlock procedure is a no brainer, can't mess up anything there. Downgrading is a little risky, but you're on 3.2.4, thus you can even use the rollback images for Safestrap, take a look at this thread (page 1 is about 3.2.5/3.2.6 users who can NOT use the downgrade images). I'm afraid it won't get any easier than that.
If you don't want to use Python, just execute the adb commands to get your ID and serial (post them here, or PM me if you don't want anyone to see them), I'll create the .unlock file for you then. Downgrading and (actual) unlocking are tasks you have to do yourself though.
Click to expand...
Click to collapse
I have successfully downgraded to 13.3.1.0, but I am confused about how to install TWRP. Since I have not enabled wifi and registered, I can't install flashify or cwm, or even install a file explorer apk to access my storage, and I don't know how to get the twrp.img file (which I guess I can only install via adb?) Where do I get the correct twrp.img file? I'm kind of stuck....
kbs24 said:
I have successfully downgraded to 13.3.1.0, but I am confused about how to install TWRP. Since I have not enabled wifi and registered, I can't install flashify or cwm, or even install a file explorer apk to access my storage, and I don't know how to get the twrp.img file (which I guess I can only install via adb?) Where do I get the correct twrp.img file? I'm kind of stuck....
Click to expand...
Click to collapse
I am by no means an expert but I just went through this process myself yesterday and it was relatively simple. Check this thread. It has a number of helpful posts in it, including my questions from yesterday.
The correct TWRP image is here. Just follow the instructions in that thread. It's super simple if you use the minimal adb and fastboot linked by Cl4ncy in the first thread I linked. If you have any other questions I'll do my best to help you.
kbs24 said:
I have successfully downgraded to 13.3.1.0, but I am confused about how to install TWRP. Since I have not enabled wifi and registered, I can't install flashify or cwm, or even install a file explorer apk to access my storage, and I don't know how to get the twrp.img file (which I guess I can only install via adb?) Where do I get the correct twrp.img file? I'm kind of stuck....
Click to expand...
Click to collapse
Sorry for the late reply, @muunkin pointed you in the right direction already.
Be sure to (re-)root 3.1.0 and disable OTA via HDX ToolKit, and enable USB debugging in Fire OS, hope you installed minimal adb and fastboot, then copy the TWRP image for your HDX (Thor = 7", Apollo = 8.9") to the root of the sdcard (which is the directory you'll see in Explorer after connecting the HDX to your PC, i.e. don't open another directory), open a DOS box, change dir to the adb directory (enter cd\adb) and enter the commands mentioned in the TWRP thread. This will flash the TWRP image to the recovery parition.
Do a backup of your Fire OS in TWRP before you flash any custom ROM, and copy it to your PC, also look for the TWRP backup of the stock recovery (I think TWRP does a backup somewhere), and move that to your PC as well.
In case you don't know how to access TWRP: with the HDX powered off, you press and hold volume up, then press and hold the power button, release both when the grey Kindle Fire logo appears on screen. Some ROMs (e.g. CM12) offer the advanced reboot in developer options, this will add options to reboot into recovery, bootloader or a soft (quick) reboot to the power menu.
Cl4ncy said:
Sorry for the late reply, @muunkin pointed you in the right direction already.
Be sure to (re-)root 3.1.0 and disable OTA via HDX ToolKit, and enable USB debugging in Fire OS, hope you installed minimal adb and fastboot, then copy the TWRP image for your HDX (Thor = 7", Apollo = 8.9") to the root of the sdcard (which is the directory you'll see in Explorer after connecting the HDX to your PC, i.e. don't open another directory), open a DOS box, change dir to the adb directory (enter cd\adb) and enter the commands mentioned in the TWRP thread. This will flash the TWRP image to the recovery parition.
Do a backup of your Fire OS in TWRP before you flash any custom ROM, and copy it to your PC, also look for the TWRP backup of the stock recovery (I think TWRP does a backup somewhere), and move that to your PC as well.
In case you don't know how to access TWRP: with the HDX powered off, you press and hold volume up, then press and hold the power button, release both when the grey Kindle Fire logo appears on screen. Some ROMs (e.g. CM12) offer the advanced reboot in developer options, this will add options to reboot into recovery, bootloader or a soft (quick) reboot to the power menu.
Click to expand...
Click to collapse
Thank you both @muunkin and @Cl4ncy for guiding me through this. It is clear now that I have to flash TWRP via adb. Unfortunately I did, however, last night briefly turn on wifi in order to get es file explorer, and very quickly the OS ugraded itself to 13.3.2.3. Then, stupidly, I decided to go back to Nexus rom 2.0.2, which I did by reinstalling safestrap. And, Nexus rom is installed on the Stock Rom slot, and I did NOT backup the 13.3.2.3 stock rom. SO, since I am on Nexus rom, do I understand correctly that I need to begin again by downgrading to 13.3.1.0? Right? (After printing out all of these threads and printing out a lot of it and carefully reading, it looks to me like if I had stayed on stock 13.3.2.3 I would not have had to downgrade.....but too late now anyway.) I do have the minimal adb and fastboot installed, and my device is recognized, so eventually this will work I'm pretty sure. I appreciate the help!
kbs24 said:
Thank you both @muunkin and @Cl4ncy for guiding me through this. It is clear now that I have to flash TWRP via adb. Unfortunately I did, however, last night briefly turn on wifi in order to get es file explorer, and very quickly the OS ugraded itself to 13.3.2.3. Then, stupidly, I decided to go back to Nexus rom 2.0.2, which I did by reinstalling safestrap. And, Nexus rom is installed on the Stock Rom slot, and I did NOT backup the 13.3.2.3 stock rom. SO, since I am on Nexus rom, do I understand correctly that I need to begin again by downgrading to 13.3.1.0? Right? (After printing out all of these threads and printing out a lot of it and carefully reading, it looks to me like if I had stayed on stock 13.3.2.3 I would not have had to downgrade.....but too late now anyway.) I do have the minimal adb and fastboot installed, and my device is recognized, so eventually this will work I'm pretty sure. I appreciate the help!
Click to expand...
Click to collapse
No, 13.3.2.3 is ok for both TWRP and unlocking the bootloader, i.e. no need to flash 3.1.0 again - a firmware below 3.2.4 is enough.
Cl4ncy said:
No, 13.3.2.3 is ok for both TWRP and unlocking the bootloader, i.e. no need to flash 3.1.0 again - a firmware below 3.2.4 is enough.
Click to expand...
Click to collapse
Even if I am not running on the stock rom? I can adb install TWRP while on Nexus rom?
kbs24 said:
Even if I am not running on the stock rom? I can adb install TWRP while on Nexus rom?
Click to expand...
Click to collapse
Hm, I'm not exactly sure about this - @ggow's answer here seems to point out that you really have to do it all over again.
Why did you install Safestrap again anyway? ADB-flashing TWRP and unlocking the bootloader before you install a custom ROM would've been the next steps. Also I told you to create a backup of your stock slot before you flash any custom ROM, didn't I?
Cl4ncy said:
Hm, I'm not exactly sure about this - @ggow's answer here seems to point out that you really have to do it all over again.
Why did you install Safestrap again anyway? ADB-flashing TWRP and unlocking the bootloader before you install a custom ROM would've been the next steps. Also I told you to create a backup of your stock slot before you flash any custom ROM, didn't I?
Click to expand...
Click to collapse
Yes you sure did, and that's why I said "stupidly" about me putting safestrap back and nexus rom. I was overanxious and acted impulsively, not having a recovery installed was freaking me out. Bad habit. About doing the backup, there did not appear to be enough room on the internal storage. Sorry. We'll start over no problem. Again thanks.
kbs24 said:
Yes you sure did, and that's why I said "stupidly" about me putting safestrap back and nexus rom. I was overanxious and acted impulsively, not having a recovery installed was freaking me out. Bad habit. About doing the backup, there did not appear to be enough room on the internal storage. Sorry. We'll start over no problem. Again thanks.
Click to expand...
Click to collapse
I'm also not sure how to do this now. You don't have any Safestrap 3.2.3 Fire OS backup to restore, you shouldn't use the 3.2.4 rollback image, as you're not on 3.2.4, so what do you want to flash to the stock slot now? Or did I miss anything?
Cl4ncy said:
I'm also not sure how to do this now. You don't have any Safestrap 3.2.3 Fire OS backup to restore, you shouldn't use the 3.2.4 rollback image, as you're not on 3.2.4, so what do you want to flash to the stock slot now? Or did I miss anything?
Click to expand...
Click to collapse
I was going to look for a stock 3.2.3 to flash. If can't find, I do have a backup of stock 3.2.4 on the card which I would flash, thus requiring the downgrade.
kbs24 said:
I was going to look for a stock 3.2.3 to flash. If can't find, I do have a backup of stock 3.2.4 on the card which I would flash, thus requiring the downgrade.
Click to expand...
Click to collapse
I haven't seen a 3.2.3 Safestrap flashable Image, good luck. Regarding the 3.2.4 backup I'm not sure whether it works with the 3.2.3 bootloader.
Cl4ncy said:
I haven't seen a 3.2.3 Safestrap flashable Image, good luck. Regarding the 3.2.4 backup I'm not sure whether it works with the 3.2.3 bootloader.
Click to expand...
Click to collapse
Yeah, I am probably screwed. But we'll see. I'm pretty sure I understand what the process should be at least.
kbs24 said:
Yeah, I am probably screwed. But we'll see. I'm pretty sure I understand what the process should be at least.
Click to expand...
Click to collapse
Not sure how far you got with this but you *should* be able to flash TWRP from Nexus provided the version of FireOS was 3.2.3.2 or lower prior to the installation of Safestrap v3. The customized version of twrp leverages a vulnerability in the HDX bootloader that is installed with FireOS. Neither Safestrap nor Nexus mess with the bootloader so the prerequisites should remain intact. I say should as interactions are complex - further complicated by a fussy device with limited recovery capability should something go wrong. To the best of my knowledge no one has attempted a twrp flash from Nexus while Safestrap v3 is installed.
Thoughts:
- grab flashify from the play store or here; make a backup of your current recovery environment (this step will also help to familiarize you with flashify)
- download the HDX customized version of twrp (here); use ES File Explorer to verify MD5
- use flashify to install twrp (can also be done via adb commands as shown in the twrp op)
Options:
- unlock the bootloader before attempting other remedial steps. Unlocking is a frustrating but low/no risk activity that yields substantially improved recovery capabilities once completed. Yep - you can do this without twrp (unlocking before flashing twrp is the recommended path according to several devs - although I prefer the opposite).
[-or-]
- flash 3.1.0 from here to the stock slot and then attempt to remove Safestrap v3. If successful you can proceed with flashing twrp unlocking, etc in the normal manner. As with any flash there is a risk something will go wrong or FireOS will not start up properly. To help mitigate the latter suggest installing a fallback version of Nexus v2 in a secondary slot. Don't forget to remove this slot before uninstalling SS.
The above is only an outline. Give it some thought and post any questions BEFORE taking action. I also suggest you let this post sit for a few days in case some of the rational is fatally flawed. Lots of smart people in the community who will jump in if my guidance is misdirected (which it has been shown to be on occasion). Don't risk a brick by acting too quickly. Proper preparation is essential for a successful outcome.
Sorry for sounding like your mum ... :angel:
Davey126 said:
Not sure how far you got with this but you *should* be able to flash TWRP from Nexus provided the version of FireOS was 3.2.3.2 or lower prior to the installation of Safestrap v3. The customized version of twrp leverages a vulnerability in the HDX bootloader that is installed with FireOS. Neither Safestrap nor Nexus mess with the bootloader so the prerequisites should remain intact. I say should as interactions are complex - further complicated by a fussy device with limited recovery capability should something go wrong. To the best of my knowledge no one has attempted a twrp flash from Nexus while Safestrap v3 is installed.
Thoughts:
- grab flashify from the play store or here; make a backup of your current recovery environment (this step will also help to familiarize you with flashify)
- download the HDX customized version of twrp (here); use ES File Explorer to verify MD5
- use flashify to install twrp (can also be done via adb commands as shown in the twrp op)
Options:
- unlock the bootloader before attempting other remedial steps. Unlocking is a frustrating but low/no risk activity that yields substantially improved recovery capabilities once completed. Yep - you can do this without twrp (unlocking before flashing twrp is the recommended path according to several devs - although I prefer the opposite).
[-or-]
- flash 3.1.0 from here to the stock slot and then attempt to remove Safestrap v3. If successful you can proceed with flashing twrp unlocking, etc in the normal manner. As with any flash there is a risk something will go wrong or FireOS will not start up properly. To help mitigate the latter suggest installing a fallback version of Nexus v2 in a secondary slot. Don't forget to remove this slot before uninstalling SS.
The above is only an outline. Give it some thought and post any questions BEFORE taking action. I also suggest you let this post sit for a few days in case some of the rational is fatally flawed. Lots of smart people in the community who will jump in if my guidance is misdirected (which it has been shown to be on occasion). Don't risk a brick by acting too quickly. Proper preparation is essential for a successful outcome.
Sorry for sounding like your mum ... :angel:
Click to expand...
Click to collapse
Thanks for your input. I am still on the nexus rom, but I am fairly sure that Safestrap was installed while on 13.3.2.4. Is there a way to tell? It is safestrap 3.75, based on twrp 2.7.
I had some time today to work on this, and after looking over the ideas from all of you (thank you very much!) it seemed that my only option is to restore my backup which will get me back to the Nexus 2.0.2 rom. So I did this successfully. Being on Nexus rom, I was then able to use the 13.3.2.4 rollback file to get back to 13.3.0.9. Then ran into trouble......the system update to 13.3.1.0 was not successful. the .bin file was located, but all that happened was a "validating update file" followed by forced reboot. I remain stuck on 13.3.0.9. There are threads discussing editing build.prop but I know I did not have to do this when I first did a rollback a few days ago. Not sure whether to give up or maybe someone has another idea how to get the system to use that .bin file? Should I turn on wifi and wait for an ota or is that too risky, will it jump me all the way up to the most current build? Will it maybe go incrementally?
kbs24 said:
Thanks for your input. I am still on the nexus rom, but I am fairly sure that Safestrap was installed while on 13.3.2.4. Is there a way to tell? It is safestrap 3.75, based on twrp 2.7.
Click to expand...
Click to collapse
(Also as you suggested, I did try flashing the zip 3.1.0 and it did not work, never rebooted successfully. So went back again to 3.0.9.)
kbs24 said:
I had some time today to work on this, and after looking over the ideas from all of you (thank you very much!) it seemed that my only option is to restore my backup which will get me back to the Nexus 2.0.2 rom. So I did this successfully. Being on Nexus rom, I was then able to use the 13.3.2.4 rollback file to get back to 13.3.0.9. Then ran into trouble......the system update to 13.3.1.0 was not successful. the .bin file was located, but all that happened was a "validating update file" followed by forced reboot. I remain stuck on 13.3.0.9. There are threads discussing editing build.prop but I know I did not have to do this when I first did a rollback a few days ago. Not sure whether to give up or maybe someone has another idea how to get the system to use that .bin file? Should I turn on wifi and wait for an ota or is that too risky, will it jump me all the way up to the most current build? Will it maybe go incrementally?
Click to expand...
Click to collapse
Glad you were able to make some progress. I believe you could have flashed twrp from Nexus as I believe you successfully downgraded/upgraded to 13.3.2.3 which would then be the base version when you reininstalled Safestrap. But you found another path which is just fine.
It is possible the 13.3.1.0 is invalid (possibly corrupt). You can use ES File Explorer to validate the MD5 (c49c0363de4d8dfa5c87c1bdb88aa2ba) or download a fresh copy here. You can also upgrade directly to 13.3.2.3 instead of hopscotching through 13.3.1.0 and then applying the 13.2.3.3 bootloader update.
I strongly suggest you NOT connect to WiFi as it is unpredictable if/when you will receive at OTA and what version will be downloaded. Options for getting files onto you device:
- use HDX toolkit to root and block OTA on 13.3.0.9; you can then enable WiFi
- tether your device and drop files into "Internal Storage"
- use 'adb push' to transfer files
You should not need to mess with build.prop as the 3.2.4->3.0.9 rollback should have handed that. It's quite easy to brick your device if you get any of the edits or permissions wrong.
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!
Hey there, everybody! Just got a 201 as a "parts only" tablet... turns out it just needed a trickle charge, so i'm off to the races. Wanted to put KatshMallow on here like I have on my tf300... Finally found out that in order to flash the hairybean stuff (so i can actually flash katshmallow) I needed twrp 2.5.0.0 first. So, upon discovering this, I downloaded the proper twrp image and went to flash the recovery via fastboot.
did 'fastboot devices' to make sure it saw the tablet... all good there.
did the 'flash' command, posted the [sending] and [receiving] steps, all said OK
did the 'adb reboot' command just to get things established and boot into the recovery...
but i don't get a recovery prompt, just a dead android with the 'x'. :/
now i don't even have a recovery module. I downloaded the proper package, but went and downloaded elsewhere just to be sure, and got the same result. I *was* going to ask if someone would post a nandroid from a tf201 that already had katshmallow running and try and establish myself that way, but again, no recovery at all. What do I do from here? anybody happen to know what the last twrp version for the 201 that works with JB 4.1.1? i can try to flash a 2.6.x or 2.7.x if either of those will work.
edit: stock os still running fine, jicyw.
Edit #2: went ahead and rooted with that Chinese apk (forgot the name, but ya'll know the one), then installed rashr, thinking maybe my usb connection was to blame for the bad flash, but i have the same result flashing recovery img with rashr: claims success, but dead andy when trying to open recovery console. Boo!
monogwai said:
Hey there, everybody! Just got a 201 as a "parts only" tablet... turns out it just needed a trickle charge, so i'm off to the races. Wanted to put KatshMallow on here like I have on my tf300... Finally found out that in order to flash the hairybean stuff (so i can actually flash katshmallow) I needed twrp 2.5.0.0 first. So, upon discovering this, I downloaded the proper twrp image and went to flash the recovery via fastboot.
did 'fastboot devices' to make sure it saw the tablet... all good there.
did the 'flash' command, posted the [sending] and [receiving] steps, all said OK
did the 'adb reboot' command just to get things established and boot into the recovery...
but i don't get a recovery prompt, just a dead android with the 'x'. :/
now i don't even have a recovery module. I downloaded the proper package, but went and downloaded elsewhere just to be sure, and got the same result. I *was* going to ask if someone would post a nandroid from a tf201 that already had katshmallow running and try and establish myself that way, but again, no recovery at all. What do I do from here? anybody happen to know what the last twrp version for the 201 that works with JB 4.1.1? i can try to flash a 2.6.x or 2.7.x if either of those will work.
edit: stock os still running fine, jicyw.
Edit #2: went ahead and rooted with that Chinese apk (forgot the name, but ya'll know the one), then installed rashr, thinking maybe my usb connection was to blame for the bad flash, but i have the same result flashing recovery img with rashr: claims success, but dead andy when trying to open recovery console. Boo!
Click to expand...
Click to collapse
come on, peoples... i know someone out there must have some kind of advice. nobody ever responds to anything i post. ya'll are making me feel like i have the xda forums' equivalent of digital herpes. clean bill of health here, folks, I promise! :laugh:
wow, rough crowd. Can't help, sorry. Trying to solve a problem myself :<
Phil
Does the TF201 have it's bootloader unlocked?
NP
So, complete tutorial is here when tab is working : https://forum.xda-developers.com/tr...uide-tutorial-asus-transformer-prime-t3486237
Flashing TF201 is not like TF300.
It is why NVIDIA Download mode is used to backup files.
So, you talk of flashing an apk. How did you do if your tab is down ?
System working ? Download working ? Recovery working ?
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.
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.