Related
Hello,
I'm hoping that someone can help me out with this.
Last December i bought a Fire HDX 7 (Thor). I immediatley followed the procedure to install Safestrap and the Thor Nexus ROM v2.0.1. Shortly after that my device got lost. Just last week I found it because my parents moved. After this I started looking around the internet to check if there are any 5.0 or 5.1 ROMs available. I found out they are indeed available.
What I want to do now is get rid of Safestrap, unlock the bootloader and install TWRP to be able to flash new ROMs. I want to start using TWRP because I'm used to working with TWRP.
The problem is that I can't seem to find a way to get this done, despite searching for it on this page for several hours. Can anyone help me on the right track? Would be very much appreciated.
Timmetjuh said:
Hello,
I'm hoping that someone can help me out with this.
Last December i bought a Fire HDX 7 (Thor). I immediatley followed the procedure to install Safestrap and the Thor Nexus ROM v2.0.1. Shortly after that my device got lost. Just last week I found it because my parents moved. After this I started looking around the internet to check if there are any 5.0 or 5.1 ROMs available. I found out they are indeed available.
What I want to do now is get rid of Safestrap, unlock the bootloader and install TWRP to be able to flash new ROMs. I want to start using TWRP because I'm used to working with TWRP.
The problem is that I can't seem to find a way to get this done, despite searching for it on this page for several hours. Can anyone help me on the right track? Would be very much appreciated.
Click to expand...
Click to collapse
Your options are determined by the current version of Amazon firmware installed on your device. I assume you retained Fire OS in the base slot. Boot into that and poke around settings until you find the version number (should be 13.x.x plus some other gibberish). Post what you find and we'll go from there.
Caution: You should disable wifi immediately after booting into Fire OS to prevent an automatic update from Amazon from spoiling your day. At minimum an update will limit future options. I can also brick your device depending on firmware level and other previous mods (including safestrap). Disabling wifi in Nexus is not sufficient as the two roms operate independently.
Davey126 said:
Your options are determined by the current version of Amazon firmware installed on your device. I assume you retained Fire OS in the base slot. Boot into that and poke around settings until you find the version number (should be 13.x.x plus some other gibberish). Post what you find and we'll go from there.
Caution: You should disable wifi immediately after booting into Fire OS to prevent an automatic update from Amazon from spoiling your day. At minimum an update will limit future options. I can also brick your device depending on firmware level and other previous mods (including safestrap). Disabling wifi in Nexus is not sufficient as the two roms operate independently.
Click to expand...
Click to collapse
Could it be that I somehow deleted the Fire OS back then? Don't really remeber what I did exactly..
Timmetjuh said:
Could it be that I somehow deleted the Fire OS back then? Don't really remeber what I did exactly..
Click to expand...
Click to collapse
Quite possibly. Enjoy Nexus; it's a good rom. Alternatively, follow the directions to see if you still have Fire OS installed. If at/below v3.2.6 then Lollipop is possible albeit with a lot of work and significant risk to your device. Otherwise you are limited to Fire OS and Nexus.
Seriously, if you don't recall what you did and can't figure out how start Safestrap in recovery mode be happy with what you have. There are no step-by-step guides. You have to read (a lot) and be prepared for numerous setbacks including an unrecoverable brick of your now working Kindle.
Davey126 said:
Quite possibly. Enjoy Nexus; it's a good rom. Alternatively, follow the directions to see if you still have Fire OS installed. If at/below v3.2.6 then Lollipop is possible albeit with a lot of work and significant risk to your device. Otherwise you are limited to Fire OS and Nexus.
Seriously, if you don't recall what you did and can't figure out how start Safestrap in recovery mode be happy with what you have. There are no step-by-step guides. You have to read (a lot) and be prepared for numerous setbacks including an unrecoverable brick of your now working Kindle.
Click to expand...
Click to collapse
Sorry for my late response.. I just started Safestrap and can only find 1 ROM slot, the Stock ROM slot which probably means that I deleted the original OS.
I did find some files on my laptop that brought some memories back. What I did back then is downgrade the original software to version 13.3.2.6 and than to 13.3.1.0. Does this create any new possibilities?
I just managed to create a new ROM slot and succesfully installed stock 13.3.2.6 on it, so now running on Nexus ROM and stock 13.3.2.6.
Timmetjuh said:
Sorry for my late response.. I just started Safestrap and can only find 1 ROM slot, the Stock ROM slot which probably means that I deleted the original OS.
I did find some files on my laptop that brought some memories back. What I did back then is downgrade the original software to version 13.3.2.6 and than to 13.3.1.0. Does this create any new possibilities?
Click to expand...
Click to collapse
Timmetjuh said:
I just managed to create a new ROM slot and succesfully installed stock 13.3.2.6 on it, so now running on Nexus ROM and stock 13.3.2.6.
Click to expand...
Click to collapse
Warning: Do NOT allow Fire OS to auto-update. Doing so will likely brick your device. Short term the best way to prevent this is to only boot into Nexus. If necessary I can walk you through blocking OTA. Seriously - stay out of Fire OS for now.
I am no Safestrap expert but I believe the rom in the 'base' slot becomes the default when you uninstall Safestrap. So you may have some shuffling to do. Another concern is whether removing/reinstalling Fire OS will impact the ability to recognize the OS once Safetrap is gone. You need a functioning version of Fire OS (and recovery) to follow the 'standard' rollback/update/flash procedures.
However, there may be a shortcut. If 13.3.1.0 was the base rom just prior to installing Nexus and wiping out Fire OS you then should be able to flash twrp without further prep. That would give you access to both Nexus variants and CM11. Unfortunately, there is no easy way to determine the bootloader version which is the component that really matters. It should match the last version of Fire OS that was natively installed before you overwrite it with Nexus.
Unfortunately, the recent install of 13.3.2.6 into a safestrap slot complicates matters. I believe installs within Safestrap leaves the bootloader untouched. But I can't be sure. A misstep can leave your device in an unrecoverable condition; don't go experimenting.
Let's see which recovery you have installed. Power down the device then restart holding power + vol-up. When the grey Kindle logo appears release the power key; vol-up can be released a few seconds later. What happens after the grey logo disappears?
Davey126 said:
Warning: Do NOT allow Fire OS to auto-update. Doing so will likely brick your device. Short term the best way to prevent this is to only boot into Nexus. If necessary I can walk you through blocking OTA. Seriously - stay out of Fire OS for now.
I am no Safestrap expert but I believe the rom in the 'base' slot becomes the default when you uninstall Safestrap. So you may have some shuffling to do. Another concern is whether removing/reinstalling Fire OS will impact the ability to recognize the OS once Safetrap is gone. You need a functioning version of Fire OS (and recovery) to follow the 'standard' rollback/update/flash procedures.
However, there may be a shortcut. If 13.3.1.0 was the base rom just prior to installing Nexus and wiping out Fire OS you then should be able to flash twrp without further prep. That would give you access to both Nexus variants and CM11. Unfortunately, there is no easy way to determine the bootloader version which is the component that really matters. It should match the last version of Fire OS that was natively installed before you overwrite it with Nexus.
Unfortunately, the recent install of 13.3.2.6 into a safestrap slot complicates matters. I believe installs within Safestrap leaves the bootloader untouched. But I can't be sure. A misstep can leave your device in an unrecoverable condition; don't go experimenting.
Let's see which recovery you have installed. Power down the device then restart holding power + vol-up. When the grey Kindle logo appears release the power key; vol-up can be released a few seconds later. What happens after the grey logo disappears?
Click to expand...
Click to collapse
I see the following:
Kindle Fire System Recovery
Your Kindle doesn't seem to be able to boot. Resetting your device to Factory defaults may help you to fix this issue.
Then I get the options to Reboot or to reset to Factory Default.
Oh, the Fire OS is not connected to any networks so it won't be able to update.
Timmetjuh said:
I see the following:
Kindle Fire System Recovery
Your Kindle doesn't seem to be able to boot. Resetting your device to Factory defaults may help you to fix this issue.
Then I get the options to Reboot or to reset to Factory Default.
Oh, the Fire OS is not connected to any networks so it won't be able to update.
Click to expand...
Click to collapse
Ok - a working stock recovery. That's good.
I am conflicted on next steps. The scripted approach would have you uninstall Safestrap (assuming Fire OS had remained in slot 0), rollback to 3.1.0 and then install twrp. However, since slot 0 now contains Nexus I do not feel removing Safestrap is wise. Nor to I think reinstalling Fire OS in the base slow will yield a functioning system once Safestrap is gone.
The 'shortcut' would have you flash twrp recovery (via adb or Flashify) since your bootloader *should*_be at the right level due to a previous 3.1.0 rollback. However, if that is not correct you will end up with a borked recovery which is difficult to rectify.
In your shoes I would probably do nothing given the device is fully functional. The developer of the Nexus rom is working on a KitKat 'upgrade' which is close to being released; a Safestrap variant will hopefully follow. There's no shame in running Nexus. Upgrade to v4.4, add a few Xposed modules and you have fully supported, near AOSP environment that's only lacking a few eye candy elements from Lollipop.
Davey126 said:
Ok - a working stock recovery. That's good.
I am conflicted on next steps. The scripted approach would have you uninstall Safestrap (assuming Fire OS had remained in slot 0), rollback to 3.1.0 and then install twrp. However, since slot 0 now contains Nexus I do not feel removing Safestrap is wise. Nor to I think reinstalling Fire OS in the base slow will yield a functioning system once Safestrap is gone.
The 'shortcut' would have you flash twrp recovery (via adb or Flashify) since your bootloader *should*_be at the right level due to a previous 3.1.0 rollback. However, if that is not correct you will end up with a borked recovery which is difficult to rectify.
In your shoes I would probably do nothing given the device is fully functional. The developer of the Nexus rom is working on a KitKat 'upgrade' which is close to being released; a Safestrap variant will hopefully follow. There's no shame in running Nexus. Upgrade to v4.4, add a few Xposed modules and you have fully supported, near AOSP environment that's only lacking a few eye candy elements from Lollipop.
Click to expand...
Click to collapse
It's not that I don't like the Nexus ROM, I just like to experiment with these things..
So I just installed TWRP with Flashify (started Flashify from NEXUS) and now I seem stuck at the grey Kindle fire logo. I'm just going to leave it alone for a few hours, hopefully it boots later today.
Davey126 said:
Ok - a working stock recovery. That's good.
I am conflicted on next steps. The scripted approach would have you uninstall Safestrap (assuming Fire OS had remained in slot 0), rollback to 3.1.0 and then install twrp. However, since slot 0 now contains Nexus I do not feel removing Safestrap is wise. Nor to I think reinstalling Fire OS in the base slow will yield a functioning system once Safestrap is gone.
The 'shortcut' would have you flash twrp recovery (via adb or Flashify) since your bootloader *should*_be at the right level due to a previous 3.1.0 rollback. However, if that is not correct you will end up with a borked recovery which is difficult to rectify.
In your shoes I would probably do nothing given the device is fully functional. The developer of the Nexus rom is working on a KitKat 'upgrade' which is close to being released; a Safestrap variant will hopefully follow. There's no shame in running Nexus. Upgrade to v4.4, add a few Xposed modules and you have fully supported, near AOSP environment that's only lacking a few eye candy elements from Lollipop.
Click to expand...
Click to collapse
It still boots after a very long time, however I don't know if I get the possibility to enter recovery because it takes several hours to boot. Any more ideas?
Timmetjuh said:
It still boots after a very long time, however I don't know if I get the possibility to enter recovery because it takes several hours to boot. Any more ideas?
Click to expand...
Click to collapse
Power down device and attempt to enter recovery by pressing power + vol-up. Release the power button after the grey logo appears; vol-up can be released after a few seconds. What happens next? Likely one of the following (good -> bad):
- blue screen followed by twrp recovery
- stock recovery with only two options: factory reset and reboot
- continuation of grey kindle logo
Davey126 said:
Power down device and attempt to enter recovery by pressing power + vol-up. Release the power button after the grey logo appears; vol-up can be released after a few seconds. What happens next? Likely one of the following (good -> bad):
- blue screen followed by twrp recovery
- stock recovery with only two options: factory reset and reboot
- continuation of grey kindle logo
Click to expand...
Click to collapse
I'm stuck at the grey Kindle logo..
Did it! Managed to flash the stock bootloader, rollback and install TWRP. Now ready to flash CM11. Thanks for you help!
Timmetjuh said:
Did it! Managed to flash the stock bootloader, rollback and install TWRP. Now ready to flash CM11. Thanks for you help!
Click to expand...
Click to collapse
Congrats! Had a bad feeling after your earlier post; glad that was misplaced. Enjoy CM11 and all the goodness that comes from a liberated HDX.
At some point you should consider unlocking the bootloader. That will provide an important fail safe should things go wrong and opens the door to newer roms. Unlike previous flashes there is little/no risk in unlocking. It will either work or not with no adverse consequences. Unlocking can be a frustrating ride as the process involves multiple steps in unfamiliar territory but ultimately the benefits outweigh the effort IMO. Nothing that needs to be tackled right away but keep it on your radar ... especially if you plan to experiment with other roms.
Unlock bootloader
Hello davey,
I am also interested in getting from safestrap v4 to an unlocked bootloader in order to use a lollipop ROM. My 3rd gen hdx 7 started on 4.5.5 so I did OTA rollback to 3.2.8, upgraded to 4.5.2, then rooted and safestrapped. Unfortunately I lost my stock ROM, but I current have both CM11 and HDZ nexus v4 on 2 different ROM slots. What would be my best way to proceed? From my research so far, it would appear I need to flash hdx nexus 2.0, then flash rollback image to get to modified 3.2.4, and from there 3.1.0 stock update with will allow me to use python method to unlock BL. Is this all correct?
Thanks in advance for your guidance
slothdabski said:
Hello davey,
I am also interested in getting from safestrap v4 to an unlocked bootloader in order to use a lollipop ROM. My 3rd gen hdx 7 started on 4.5.5 so I did OTA rollback to 3.2.8, upgraded to 4.5.2, then rooted and safestrapped. Unfortunately I lost my stock ROM, but I current have both CM11 and HDZ nexus v4 on 2 different ROM slots. What would be my best way to proceed? From my research so far, it would appear I need to flash hdx nexus 2.0, then flash rollback image to get to modified 3.2.4, and from there 3.1.0 stock update with will allow me to use python method to unlock BL. Is this all correct?
Thanks in advance for your guidance
Click to expand...
Click to collapse
No. You can NOT unlock the bootloader! You can NOT downgrade to 3.2.4 and then further to 3.1.0/3.2.3.2! DON'T attempt to do so, you will brick your HDX!
Your only available option is to stay on 4.5.2 and use Safestrap v4 with either Nexus and/or CM11.
slothdabski said:
Hello davey,
I am also interested in getting from safestrap v4 to an unlocked bootloader in order to use a lollipop ROM. My 3rd gen hdx 7 started on 4.5.5 so I did OTA rollback to 3.2.8, upgraded to 4.5.2, then rooted and safestrapped. Unfortunately I lost my stock ROM, but I current have both CM11 and HDZ nexus v4 on 2 different ROM slots. What would be my best way to proceed? From my research so far, it would appear I need to flash hdx nexus 2.0, then flash rollback image to get to modified 3.2.4, and from there 3.1.0 stock update with will allow me to use python method to unlock BL. Is this all correct?
Thanks in advance for your guidance
Click to expand...
Click to collapse
Unfortunately, you can not unlock your bootloader. Amazon introduced anti-rollback protection that will hard brick the device if rolled back below 3.2.8. Sorry, mate.
Davey126 said:
Unfortunately, you can not unlock your bootloader. Amazon introduced anti-rollback protection that will hard brick the device if rolled back below 3.2.8. Sorry, mate.
Click to expand...
Click to collapse
Thanks Davey, you have been very helpful replying to me in another thread also. My reason for seeking a ROM other, than Nexus v4 or CM11, is the kitkat bluetooth tether/VPN bug documented at code.google.com/p/android/issues/detail?id=62714 (sorry for no direct link, xda won't let me post them yet). A "work around" is to establish a wifi connection, even if it doesnt have internet access. This, for whatever reason, allows kitkat to forward the packets to apps on the kindle. I probably could get away with plugging in an old access point at work to enable the sharing sharing of my phones data connection with my safestrap kitkit kindle, but this isn't practical outside of my workplace.
FYI, I cant share my phone's connection via wifi because its an ATT note 4 with lollipop, a locked bootloader, and no permaroot available. I doubt there's a way to tether between 2 android devices via microUSB; but i'd be open to that too!
Thanks again for your wisdom and expertise!
slothdabski said:
Thanks Davey, you have been very helpful replying to me in another thread also. My reason for seeking a ROM other, than Nexus v4 or CM11, is the kitkat bluetooth tether/VPN bug documented at code.google.com/p/android/issues/detail?id=62714 (sorry for no direct link, xda won't let me post them yet). A "work around" is to establish a wifi connection, even if it doesnt have internet access. This, for whatever reason, allows kitkat to forward the packets to apps on the kindle. I probably could get away with plugging in an old access point at work to enable the sharing sharing of my phones data connection with my safestrap kitkit kindle, but this isn't practical outside of my workplace.
FYI, I cant share my phone's connection via wifi because its an ATT note 4 with lollipop, a locked bootloader, and no permaroot available. I doubt there's a way to tether between 2 android devices via microUSB; but i'd be open to that too!
Thanks again for your wisdom and expertise!
Click to expand...
Click to collapse
I actually just got it working by running the following as SU in terminal emaulator
# ip route add default dev tun0 scope link
Not sure yet if I have to do this every time I tether, but if so, i think i can just make a script to execute automatically?
Actually i am not an experienced person, Just get some help from youtube and this forum & rooted my Kindle fire HDX 7 using KFHDX toolkit to install google apps. Its perfectly done and i download number of apps. Then i tried to install Kitkat (thor) on it. During all this activity i go to recovery option and press the Wipe button "Cache and Dalvik Cache". after that my Kindle fire HDX 7 boot and stuck on Kindle fire starting Grey logo. I tried to factory reset but still keep stuck on start logo. While connected to PC, only hear one connectivity beep with PC but no device shows in my computer. Tried many trouble shoot find on google and this forum but issue still there. Please assist any solution. As already mentioned that i am not an experienced person. So please assist step by step.. Thanks in advance
How did you flash the ROM? Did you already have TWRP installed?
Also, do you have adb running? Do you know what version of the kindle os you had before flashing the Rom?
I had installed android 4.2.2 (thor) before and had installed TWRP. I flashed new rom 4.0.1 through TWRP and then immediately Nexus gapps v2.1. After that tablet stuck in grey logo. Unfortunately I haven't running abd now.
tishotch said:
I had installed android 4.2.2 (thor) before and had installed TWRP. I flashed new rom 4.0.1 through TWRP and then immediately Nexus gapps v2.1. After that tablet stuck in grey logo. Unfortunately I haven't running abd now.
Click to expand...
Click to collapse
With a vocubulary that includes 'flash' and 'twrp' it would appear you are more experienced than the average Kindle owner . However, you didn't read the cautions/prerequisites for installing 4.0.1. Bootloader must be unlocked (here). Not easy/intuitive but if you get through it 4.0.1 will boot just fine.
You can reflash Nexus v2 to restore functionality while working on the bootloader unlock. Our simply restore your system from the backup you made before flashing 4.0.1. To access TWRP directly press power and vol-up from a cold start. Release the power button when the grey logo appears; vol-up can be release a few seconds later.
Caveat: I assume you are not referencing the Safestrap variant of twrp. If that's the case then you are in a whole 'nother world of hurt ...
When I press power and vol-up from a cold start, It open only stock recovery (not TWRP). After reset to factory ( second options)...the result is the same - stuck logo.
tishotch said:
When I press power and vol-up from a cold start, It open only stock recovery (not TWRP). After reset to factory ( second options)...the result is the same - stuck logo.
Click to expand...
Click to collapse
Then you had Safestrap installed which emulates twrp but provides few real protections. You likely overwrote key portions of your device when flashing Nexus v4 which is incompatible with safestrap and has other prerequisites (ie: unlocked bootloader) which you ignored. There is no known recovery. Sorry, mate.
Thanks for the explanation, despite the bad news
Whether my Amazon warranty is valid in this case ?
tishotch said:
Thanks for the explanation, despite the bad news
Whether my Amazon warranty is valid in this case ?
Click to expand...
Click to collapse
Amazon is pretty good about providing replacements/refurbs during the warranty period which is typically 1 year from the date of purchase. I would not mention safestrap, twrp, nexus, rooting or any other 'key word' that suggest you were using your device in a manner other than Amazon intended. If honored the replacement will likely be more difficult to root and probably will not permit the installation of Safestrap v3 without some risky gymnastics. Safestrap v4 is in development but not yet ready for prime time (no pun intended).
Good luck.
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.
What do I do to avoid permanently bricking this?
Story: Had Cyanogen mod installed on my HDX 8.9"; everything was rosy. Cyanogen kept pestering me with new nightly updates; thought "why not? can't cause any harm now everything's sorted!" Lo and behold, it soft bricked the device. Managed to recover to TWRP. What are my steps from here to get back to the Cyanogen ROM I had before, where everything was perfect (yes, I'm an idiot)?
Just reflash the ZIP you downloaded from XDA.
EncryptedCurse said:
Just reflash the ZIP you downloaded from XDA.
Click to expand...
Click to collapse
I tried; it says failed. Any thoughts?
Edit: Also, if I reinstall the ROM I had, will I have to reconfigure blocking the autoupdates from Amazon? Or will that still all be configured?
BRPW said:
I tried; it says failed. Any thoughts?
Edit: Also, if I reinstall the ROM I had, will I have to reconfigure blocking the autoupdates from Amazon? Or will that still all be configured?
Click to expand...
Click to collapse
Looking through previous posts it appears you have native twrp recovery (not safestrap) with a locked bootloader. If accurate try a factory reset from within twrp (slider under wipe option). This will wipe cache, dalvik and data partitions. You will loose personal data; might want to backup first. Do not wipe system unless instructed.
OTA will remained blocked if you reinstall a previous version of FireOS that was backed up via twrp. If you opt for a fresh install you must use a custom variant that has components removed that could brick your device.
Nexus v4 is a better choice IMO if you can't get CM to work. Avoids the hassles/risks associated with FireOS.
Davey126 said:
Looking through previous posts it appears you have native twrp recovery (not safestrap) with a locked bootloader. If accurate try a factory reset from within twrp (slider under wipe option). This will wipe cache, dalvik and data partitions. You will loose personal data; might want to backup first. Do not wipe system unless instructed.
OTA will remained blocked if you reinstall a previous version of FireOS that was backed up via twrp. If you opt for a fresh install you must use a custom variant that has components removed that could brick your device.
Nexus v4 is a better choice IMO if you can't get CM to work. Avoids the hassles/risks associated with FireOS.
Click to expand...
Click to collapse
Davey, you helped me install this originally; thank you for that!
So just so I'm clear; perform a factory wipe (no personal data that I care about on here), avoiding the wipe of the system partition. I can from that point, install the file on there labelled something akin to 'cm-apollo-nightly05032015.zip" right? And that will bring me back to where I was before this happened.
Edit: If I wipe the data partition, won't that wipe the cm-nightly.zip and other .img's etc?
BRPW said:
Davey, you helped me install this originally; thank you for that!
So just so I'm clear; perform a factory wipe (no personal data that I care about on here), avoiding the wipe of the system partition. I can from that point, install the file on there labelled something akin to 'cm-apollo-nightly05032015.zip" right? And that will bring me back to where I was before this happened.
Click to expand...
Click to collapse
I can not speak to the nightly referenced above. The most recent variant that was prepared/tested for your device is located here. If you browse through the full tread some individuals had luck with more recent nighties while others encountered difficulties.
BRPW said:
Edit: If I wipe the data partition, won't that wipe the cm-nightly.zip and other .img's etc?
Click to expand...
Click to collapse
Likely not as those images should be located in 'Internal Storage' (sdcard) which is a separate partition. You can verify this by locating the images in twrp file manager (under advanced). Use caution while in File Manager and you can mess your system if you accidentally delete/move critical file and folders. Like you mum use to say ... look but don't touch
Comment: Keep in mind you have opted not to unlock your bootloader which leaves your device vulnerable should something go wrong. Also, the build of CM11 you are using is not regularly updated for HDX devices as other cm variants and roms have become available. However, those either require an unlocked bootloader or Safestrap v4. If your are considering the latter be aware there are mandatory steps required to prepare your device for Safestrap v4. In your shoes I would seriously consider unlocking once the current problem is resolved. Risks are negligible (a failed unlock attempt has no adverse consequences) but does involve a bit of work.
Davey126 said:
I can not speak to the nightly referenced above. The most recent variant that was prepared/tested for your device is located here. If you browse through the full tread some individuals had luck with more recent nighties while others encountered difficulties.
Likely not as those images should be located in 'Internal Storage' (sdcard) which is a separate partition. You can verify this by locating the images in twrp file manager (under advanced). Use caution while in File Manager and you can mess your system if you accidentally delete/move critical file and folders. Like you mum use to say ... look but don't touch
Comment: Keep in mind you have opted not to unlock your bootloader which leaves your device vulnerable should something go wrong. Also, the build of CM11 you are using is not regularly updated for HDX devices as other cm variants and roms have become available. However, those either require an unlocked bootloader or Safestrap v4. If your are considering the latter be aware there are mandatory steps required to prepare your device for Safestrap v4. In your shoes I would seriously consider unlocking once the current problem is resolved. Risks are negligible (a failed unlock attempt has no adverse consequences) but does involve a bit of work.
Click to expand...
Click to collapse
Davey,
thanks again for the help so far; got back to CM11. Howevger, did so and realized I haven't installed the gapps.zip with it. Now, I think I'm being a total tool but I can't boot back into TWRP. Any idea how to do so? Sure I'm doing something wrong...
BRPW said:
Davey,
thanks again for the help so far; got back to CM11. Howevger, did so and realized I haven't installed the gapps.zip with it. Now, I think I'm being a total tool but I can't boot back into TWRP. Any idea how to do so? Sure I'm doing something wrong...
Click to expand...
Click to collapse
You can access TWRP with the HDX powered off this way: press and hold volume up, then press and hold the power button, release both when the grey Kindle Fire logo appears on screen.
BRPW said:
Thanks again for the help so far; got back to CM11. Howevger, did so and realized I haven't installed the gapps.zip with it. Now, I think I'm being a total tool but I can't boot back into TWRP. Any idea how to do so? Sure I'm doing something wrong...
Click to expand...
Click to collapse
Just for clarification, you are not able to access TWRP recovery after powering down your device (full shutdown...not sleep), holding [power]+[vol-up] buttons together and then releasing after the grey logo appears? What happens?
Cl4ncy said:
You can access TWRP with the HDX powered off this way: press and hold volume up, then press and hold the power button, release both when the grey Kindle Fire logo appears on screen.
Click to expand...
Click to collapse
Davey126 said:
Just for clarification, you are not able to access TWRP recovery after powering down your device (full shutdown...not sleep), holding [power]+[vol-up] buttons together and then releasing after the grey logo appears? What happens?
Click to expand...
Click to collapse
I was just pressing buttons in the wrong way. I was getting frustrated because I knew I was doing it wrong, heh. Thanks guys! So regarding unlocking the bootloader, do you have some resources I can follow to fully unlock and perhaps find a Lollipop ROM, keep up with the times!
BRPW said:
I was just pressing buttons in the wrong way. I was getting frustrated because I knew I was doing it wrong, heh. Thanks guys! So regarding unlocking the bootloader, do you have some resources I can follow to fully unlock and perhaps find a Lollipop ROM, keep up with the times!
Click to expand...
Click to collapse
I assume you have Minimal ADB and Fastboot installed, so you should grab these drivers, download the software and follow the procedure mentioned here. Requires a little knowledge about the usage of command prompts. Any questions just ask.
Regarding Lollipop check this, or this ROM, note that both are in beta stage. Regarding the first one the 20150814 ROM seems to have issues regarding WLAN only (reboot required to re-enable it), the 20150815 ROM has some issues regarding sound and auto-rotation on some devices (rotation works perfect on my Thor).
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!