Related
Hi,
My HDX 7" was bought last year and I immediately found a thread about SafeTrap recovery, so that I could flash a custom ROM to my HDX 7" I followed the instructions carefully and it successfully worked
But then my friend borrowed it, he didn't know about the SafeTrap and seemed to wipe all of my ROM slots. He gave it back to me when the device was still on SafeTrap. I plugged it to my laptop and found that ADB was still working, tried to push a ROM to it, but I couldn't, the storage showed 0MB so it couldn't store the ROM files.
I decided to turn it off, and when turned on, SafeTrap was gone, my HDX showed Kindle Fire logo forever.
I knew that it was hard bricked and left it until now, I thought there would be a way to restore my HDX in the future
Is there anyway to bring it back again?
Or it will be bricked forever?
Thanks!
trungamox34 said:
Hi,
My HDX 7" was bought last year and I immediately found a thread about SafeTrap recovery, so that I could flash a custom ROM to my HDX 7" I followed the instructions carefully and it successfully worked
But then my friend borrowed it, he didn't know about the SafeTrap and seemed to wipe all of my ROM slots. He gave it back to me when the device was still on SafeTrap. I plugged it to my laptop and found that ADB was still working, tried to push a ROM to it, but I couldn't, the storage showed 0MB so it couldn't store the ROM files.
I decided to turn it off, and when turned on, SafeTrap was gone, my HDX showed Kindle Fire logo forever.
I knew that it was hard bricked and left it until now, I thought there would be a way to restore my HDX in the future
Is there anyway to bring it back again?
Or it will be bricked forever?
Thanks!
Click to expand...
Click to collapse
do you remember what firmware it was on?could he give you any insight into what he had done?did it have gapps with the xposed framework installed?
jimyv said:
do you remember what firmware it was on?could he give you any insight into what he had done?did it have gapps with the xposed framework installed?
Click to expand...
Click to collapse
I don't remember the firmware, I tried flashing another custom ROM, with some Gapps and no Xposed right after bringing it home I just wanted to make the experience like the general Android device with Google Play Store and services
trungamox34 said:
I don't remember the firmware, I tried flashing another custom ROM, with some Gapps and no Xposed right after bringing it home I just wanted to make the experience like the general Android device with Google Play Store and services
Click to expand...
Click to collapse
Not to be rude but first thing's first if anybody here is going to help you you're going to have to know details and exactly what you had prior to your current state .ie answer any questions with as much detail as possible . And if it all possible find out what they did to your device . If you cannot provide any of this .I cannot provide a help . I don't know anybody that has a crystal ball I can borrow LOL
The question was had you installed xposed framework on your stock slot?
What your original firmware was?
Then you might want to add exactly what rhomb you attempted to flash?
What error did it show. Can you or can you not still get into safestrap?
First guess though I would venture to say you have a paperweight and less you can get them to warrantee it for you. Personally I would have uninstalled safe strap recovery and lock root access out before I loan my device to anybody period but that's just me
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?
After doing a decent amount of research I have not been able to find information concerning my situation.
About six months ago I rooted and installed the Kindle hdx Nexus rom with no problems. Then suddenly while playing Minecraft pe the device shuts off. I restart and it goes to the nexus boot with the four dots exchanging genetic material(lol) It got stuck at this point whenever I tried to restart. I hadn't changed and settings or software it just crashed
I am able to boot into safestrap recovery so I tried to reinstall stall the Thor rom since I still had the file on the Kindle. Theni got the boot loop from the colored dots stage and sometimes the boot would go to "initializing apps 1 of 50) or somthing like that and then it would loop.
I tried to restore to whatever previous back up and version I had and one of them must have been from the stock rom bc the loading "kindle logo" was the stock yellow and white... all I got was a loop so I reinstalled the Thor rom...
I probably should not have but at this point I tried to remove some apps via the safe strap file manager bc i know in my experience with phones certain apps can cause problems and my device was too full to preform backup via recovery
And in my last desperate attempt to not loose some of the things not backed up on the Kindle I connected to my computer to find out my computer can't recognize the device at this point...
I checked the plugins I checked the versions for compatability
I tried to use safestrap side load and came up with command not recognized for internal or external device (somthing like that)
Are there any other options for me? Does this mean it's a hard brick and what could have went wrong?
I think my mistake originally was I didn't create a separate rom slot before flashing(I don't think that bit of information was in the write up I followed)
Side note: for the record I did try to connect to my computer earlier than I stated with the device not being recognized while off or from ss recovery to try save some files
Zavxda said:
After doing a decent amount of research I have not been able to find information concerning my situation.
About six months ago I rooted and installed the Kindle hdx Nexus rom with no problems. Then suddenly while playing Minecraft pe the device shuts off. I restart and it goes to the nexus boot with the four dots exchanging genetic material(lol) It got stuck at this point whenever I tried to restart. I hadn't changed and settings or software it just crashed
I am able to boot into safestrap recovery so I tried to reinstall stall the Thor rom since I still had the file on the Kindle. Theni got the boot loop from the colored dots stage and sometimes the boot would go to "initializing apps 1 of 50) or somthing like that and then it would loop.
I tried to restore to whatever previous back up and version I had and one of them must have been from the stock rom bc the loading "kindle logo" was the stock yellow and white... all I got was a loop so I reinstalled the Thor rom...
I probably should not have but at this point I tried to remove some apps via the safe strap file manager bc i know in my experience with phones certain apps can cause problems and my device was too full to preform backup via recovery
And in my last desperate attempt to not loose some of the things not backed up on the Kindle I connected to my computer to find out my computer can't recognize the device at this point...
I checked the plugins I checked the versions for compatability
I tried to use safestrap side load and came up with command not recognized for internal or external device (somthing like that)
Are there any other options for me? Does this mean it's a hard brick and what could have went wrong?
I think my mistake originally was I didn't create a separate rom slot before flashing(I don't think that bit of information was in the write up I followed)
Side note: for the record I did try to connect to my computer earlier than I stated with the device not being recognized while off or from ss recovery to try save some files
Click to expand...
Click to collapse
No, creating a separate rom slot is not problem/solution (explicitly not recommended). What symptoms is your device exhibiting now? Which version of Safestrap?
Davey126 said:
No, creating a separate rom slot is not problem/solution (explicitly not recommended). What symptoms is your device exhibiting now? Which version of Safestrap?
Click to expand...
Click to collapse
Ok thanks good to know.:highfive: I thought I read somewhere some people do that.
Ss 4.01 (TWRP v2.7.1.0)
Basically the same as before, bootloop at the four loading dots not recognized by the computer
Zavxda said:
Ok thanks good to know.:highfive: I thought I read somewhere some people do that.
Ss 4.01 (TWRP v2.7.1.0)
Basically the same as before, bootloop at the four loading dots not recognized by the computer
Click to expand...
Click to collapse
Safestrap v4 has no native ability to communicate with the outside world. Not recognized via tether is expected with a non functioning rom. Suggest the following:
- perform a 'factory reset' from the Wipe menu (slider at bottom)
- reinstall Nexus rom using zip resident on the device
If symptoms persist it suggests corruption in the system partition which can not be wiped in Safestrap (option exists but is ignored behind then scenes as it would also destroy Safestrap recovery). Not much you can do about that short of replacing boards.
Note: There is an untested option that *may* work with a secondary slot. Try the above first and report back results.
Where would the nexus rom be located?
Davey126 said:
Safestrap v4 has no native ability to communicate with the outside world. Not recognized via tether is expected with a non functioning rom. Suggest the following:
- perform a 'factory reset' from the Wipe menu (slider at bottom)
- reinstall Nexus rom using zip resident on the device
If symptoms persist it suggests corruption in the system partition which can not be wiped in Safestrap (option exists but is ignored behind then scenes as it would also destroy Safestrap recovery). Not much you can do about that short of replacing boards.
Note: There is an untested option that *may* work with a secondary slot. Try the above first and report back results.
Click to expand...
Click to collapse
Well anyway doing factory reset and reinstalling the rom zip was not working... now when I go to restore or install option no rom file comes up
Zavxda said:
Well anyway doing factory reset and reinstalling the rom zip was not working... now when I go to restore or install option no rom file comes up
Click to expand...
Click to collapse
A zip file doesn't just disappear unless the file system is damaged. Look around with the Safestrap file manager. Without a rom zip on board your options are very limited.
Davey126 said:
A zip file doesn't just disappear unless the file system is damaged. Look around with the Safestrap file manager. Without a rom zip on board your options are very limited.
Click to expand...
Click to collapse
Yeah seems like it's missing... i think it went away after one of the factory resets I did...
I have this exact same issue - I can boot into Recovery, but I have no way of getting a ZIP onto the device to flash a ROM? Is there a way?
skoop99 said:
I have this exact same issue - I can boot into Recovery, but I have no way of getting a ZIP onto the device to flash a ROM? Is there a way?
Click to expand...
Click to collapse
Nope - no file transfer capability without a functioning ROM or custom recovery (requires an unlocked bootloader)
Zavxda said:
Yeah seems like it's missing... i think it went away after one of the factory resets I did...
Click to expand...
Click to collapse
Davey126 said:
Nope - no file transfer capability without a functioning ROM or custom recovery (requires an unlocked bootloader)
Click to expand...
Click to collapse
I actually managed to use ADB PUSH to transfer a ROM zip to the device - but after flashing it, the device still fails to boot. I'll try again with a different ROM...
skoop99 said:
I actually managed to use ADB PUSH to transfer a ROM zip to the device - but after flashing it, the device still fails to boot. I'll try again with a different ROM...
Click to expand...
Click to collapse
Update - I have now successfully pushed another ROM to the device, using:
ADB push <path to rom zip> /sdcard
Flashed said ROM, booted OK. Then re-installed the device in Windows as a "normal" Kindle portable device again, to enable drag & drop file transfers. Dropped Gapps zip on it, rebooted into Recovery, flashed Gapps. All good again!
So, Safestrap 4.xx DOES allow ADB connectivity to a device. As long as you can still boot into Recovery.
skoop99 said:
Update - I have now successfully pushed another ROM to the device, using:
ADB push <path to rom zip> /sdcard
Flashed said ROM, booted OK. Then re-installed the device in Windows as a "normal" Kindle portable device again, to enable drag & drop file transfers. Dropped Gapps zip on it, rebooted into Recovery, flashed Gapps. All good again!
So, Safestrap 4.xx DOES allow ADB connectivity to a device. As long as you can still boot into Recovery.
Click to expand...
Click to collapse
Whoa!! This is new and potentially great news for those with 'bricked' devices with a bootable Safestrap v4 recovery installed. I believe this was attempted in the past w/o success. Something changed or earlier tests were flawed.
Although it may not matter can you answer a few questions:
- Apollo or Thor?
- which rom was installed in the STOCK slot when the inadvertent wipe took place?
- what was the base version of FireOS (4.5.2 or 4.5.5.1) when Safestrap v4 recovery was first installed?
- ROM currently installed (the one that booted after adb push)?
- anything else unusual about the device or its history?
Again, this is a nice find a casts a shadow over previous statements, many made by me, that there was no resolution to this dilemma.
skoop99 said:
I actually managed to use ADB PUSH to transfer a ROM zip to the device - but after flashing it, the device still fails to boot. I'll try again with a different ROM...
Click to expand...
Click to collapse
Davey126 said:
Whoa!! This is new and potentially great news for those with 'bricked' devices with a bootable Safestrap v4 recovery installed. I believe this was attempted in the past w/o success. Something changed or earlier tests were flawed.
Although it may not matter can you answer a few questions:
- Apollo or Thor?
- which rom was installed in the STOCK slot when the inadvertent wipe took place?
- what was the base version of FireOS (4.5.2 or 4.5.5.1) when Safestrap v4 recovery was first installed?
- ROM currently installed (the one that booted after adb push)?
- anything else unusual about the device or its history?
Again, this is a nice find a casts a shadow over previous statements, many made by me, that there was no resolution to this dilemma.
Click to expand...
Click to collapse
- Thor
- Nexus: http://forum.xda-developers.com/kindle-fire-hdx/development/rom-hdx-nexus-v4-0-1-t3125808
- 4.5.2
- CM11: http://forum.xda-developers.com/kin...-cm-11-safestrap-20150628-unofficial-t3145547
- Nope.
Bootloader is also still locked.
I only figured this out when I noticed that device manager DID detect the device, but couldn't find a driver. So I installed the ADB driver, and hey presto: ADB DEVICES sees it.
C:\Users\KoopS\Dropbox\Downloads\android-sdk-windows\platform-tools>adb devices
List of devices attached
D070A0A0348300GD recovery
Hope it helps someone else. Again, though - you need to be able to boot into Recovery...
skoop99 said:
- Thor
- Nexus: http://forum.xda-developers.com/kindle-fire-hdx/development/rom-hdx-nexus-v4-0-1-t3125808
- 4.5.2
- CM11: http://forum.xda-developers.com/kin...-cm-11-safestrap-20150628-unofficial-t3145547
- Nope.
Bootloader is also still locked.
I only figured this out when I noticed that device manager DID detect the device, but couldn't find a driver. So I installed the ADB driver, and hey presto: ADB DEVICES sees it.
C:\Users\KoopS\Dropbox\Downloads\android-sdk-windows\platform-tools>adb devices
List of devices attached
D070A0A0348300GD recovery
Hope it helps someone else. Again, though - you need to be able to boot into Recovery...
Click to expand...
Click to collapse
Freaking amazing! Such an obvious and simple solution that has gone undetected for years. There are some tentative caveats (device type, older ROMs) but not sure any of it matters for basic adb access. Time will tell as others stumble into this situation.
For clarity, which recovery are you referencing? Stock or Safestrap? If the former adb access may offer a small measure of hope for those with other types of soft 'bricks'.
I unlocked the bootloader and flashed TWRP on all my HDX devices long ago and haven't loaded Safestrap for testing in months. Just continued to reference previous (mis)understandings around recovery capabilities which was generally bad news. I will likely create a new thread referencing you findings for those who may have shelved their romless but still functioning devices.
Thanks again for sharing. @skoop99 is the man of the day!
See pic. This is my KFHDX...
Wow this is fantastic news! has anyone else here had a chance to try this? I can't remember if the PC responded at all when I plugged in the Kindle
What was the first ROM you tried that didn't work?
Is there a reason you didn't flash the Nexus ROM again?
Zavxda said:
Wow this is fantastic news! has anyone else here had a chance to try this? I can't remember if the PC responded at all when I plugged in the Kindle
Click to expand...
Click to collapse
I'll try this soon. I have a Kindle HDX 7 (that I retrieved from the bin after reading this) that will boot to safe strap, but has no rom, and no zip file of a rom to install.
I'm guessing I need to download and use ADB devices?
Does this work with windows 10?
HDX is too nice to throw away, I hope this works....
Nagoyablue73 said:
I'll try this soon. I have a Kindle HDX 7 (that I retrieved from the bin after reading this) that will boot to safe strap, but has no rom, and no zip file of a rom to install.
I'm guessing I need to download and use ADB devices?
Does this work with windows 10?
HDX is too nice to throw away, I hope this works....
Click to expand...
Click to collapse
- works with Win 10
- you may need to install drivers (although Win 10 often gets it right)
- also consider Minimal ADB and Fastboot (here)
So, I pushed the zip of CM11 unofficial to my HDX. And installed it. I'm pushing the GAPPS now....
---------- Post added at 07:06 PM ---------- Previous post was at 07:05 PM ----------
And cyanogenmod is booting up! It works! My Kindle fire HDX 7 is saved! Amazing.
Background: My kindle hdx 8.9 3rd gen was running FireOS 4.5.1 , then installed the kingroot, after that safestrap v4. Having the SS recovery installed, i make attempt to replace kingroot with supersu by flasing supersu v2. 46. It got stuck at logo white-yellow. I do a manufactory reset but still no hope.
Stupid me for not backing up the stock rom since i was confidence in the past was able to do it flawlessly.
Right now:
SS Recovery is accessible
ADB/Fastboot is accessible
Locked bootloader.
Any help would be appriciated.
firebird21 said:
Background: My kindle hdx 8.9 3rd gen was running FireOS 4.5.1 , then installed the kingroot, after that safestrap v4. Having the SS recovery installed, i make attempt to replace kingroot with supersu by flasing supersu v2. 46. It got stuck at logo white-yellow. I do a manufactory reset but still no hope.
Stupid me for not backing up the stock rom since i was confidence in the past was able to do it flawlessly.
Right now:
SS Recovery is accessible
ADB/Fastboot is accessible
Locked bootloader.
Any help would be appriciated.
Click to expand...
Click to collapse
- boot into Safestrap recovery
- use 'adb push' to copy the Fire Nexus install zip (here) to your device
- flash/install Nexus to the STOCK slot (includes GAaps and SuperSU)
You can switch to CM11 later if desired (overwrite Nexus in the STOCK slot) or move forward with unlocking the bootloader for access to the full suite of HDX roms.
Davey126 said:
- boot into Safestrap recovery
- use 'adb push' to copy the Fire Nexus install zip (here) to your device
- flash/install Nexus to the STOCK slot (includes GAaps and SuperSU)
You can switch to CM11 later if desired (overwrite Nexus in the STOCK slot) or move forward with unlocking the bootloader for access to the full suite of HDX roms.
Click to expand...
Click to collapse
Thank you for the quick answer.
Would install original stock OS be possible? in case i want to return it to amazon? Just bought it a week ago.
firebird21 said:
Thank you for the quick answer.
Would install original stock OS be possible? in case i want to return it to amazon? Just bought it a week ago.
Click to expand...
Click to collapse
Yes - but start with Nexus to get the device up and running with minimal risk. Reinstalling FireOS presents a few challenges given your previous actions. Post back if/when ready. Guessing you will want to stay on Nexus or go further and unlock the bootloader.
Davey126 said:
Yes - but start with Nexus to get the device up and running with minimal risk. Reinstalling FireOS presents a few challenges given your previous actions. Post back if/when ready. Guessing you will want to stay on Nexus or go further and unlock the bootloader.
Click to expand...
Click to collapse
It seems like the nexus has the same symptom. It's stucked at the loading logo.
firebird21 said:
It seems like the nexus has the same symptom. It's stucked at the loading logo.
Click to expand...
Click to collapse
Return to Safestrap recovery and perform a factory reset from the wipe menu (slider at bottom). Then reflash Nexus ROM.
Davey126 said:
Return to Safestrap recovery and perform a factory reset from the wipe menu (slider at bottom). Then reflash Nexus ROM.
Click to expand...
Click to collapse
Yes, this time it works.
firebird21 said:
Yes, this time it works.
Click to expand...
Click to collapse
Great. Enjoy your liberated HDX!
Davey126 said:
Great. Enjoy your liberated HDX!
Click to expand...
Click to collapse
Since the ROM was installed in Stock slot, should i be precautious of doing anything in future? I read the safestrap v4 thread that wifi will not work in second slot right, any update on this?
firebird21 said:
Since the ROM was installed in Stock slot, should i be precautious of doing anything in future? I read the safestrap v4 thread that wifi will not work in second slot right, any update on this?
Click to expand...
Click to collapse
No special precautions as some earlier limitations have been lifted. Avoid performing a factory reset from the native (not Safestrap) recovery menu as it can yield an unresponsive device that occasionally can not be recovered. Also try to keep a rom zip on the device at all times for emergency recovery.
Safestrap v4 is a special build for HDX with primary emphasis on allowing custom ROMs to run on a locked device running the native FireOS v4 kernel. There was never a need or intent to leverage secondary slots as was the case with Safestrap v3; in hindsight the developer probably should have disabled them. Aside from WiFi/BT radio issues processor management is also whacked. Only 2 of 4 processors will go online and both operate at maximum frequency. As a result the device never sleeps, performs poorly and has lousy battery life. None of these problems arise in the STOCK slot.
Keep in mind all 3rd gen devices can now be unlocked eliminating the need for Safestrap and opening the door to the full suite of custom ROMs including KitKat, Lollipop and Marshmallow variants. Unfortunately, the process is a bit involved as most steps are manual and require some technical experience.
Enjoy Nexus for now; it's a fine ROM that is fast, lean and energy efficient. Not to mention full access to Google Play Store/Services/apps and the ideal platform for Xposed extensions if you want even greater control over the hardware and user interface.
Davey126 said:
No special precautions as some earlier limitations have been lifted. Avoid performing a factory reset from the native (not Safestrap) recovery menu as it can yield an unresponsive device that occasionally can not be recovered. Also try to keep a rom zip on the device at all times for emergency recovery.
Safestrap v4 is a special build for HDX with primary emphasis on allowing custom ROMs to run on a locked device running the native FireOS v4 kernel. There was never a need or intent to leverage secondary slots as was the case with Safestrap v3; in hindsight the developer probably should have disabled them. Aside from WiFi/BT radio issues processor management is also whacked. Only 2 of 4 processors will go online and both operate at maximum frequency. As a result the device never sleeps, performs poorly and has lousy battery life. None of these problems arise in the STOCK slot.
Keep in mind all 3rd gen devices can now be unlocked eliminating the need for Safestrap and opening the door to the full suite of custom ROMs including KitKat, Lollipop and Marshmallow variants. Unfortunately, the process is a bit involved as most steps are manual and require some technical experience.
Enjoy Nexus for now; it's a fine ROM that is fast, lean and energy efficient. Not to mention full access to Google Play Store/Services/apps and the ideal platform for Xposed extensions if you want even greater control over the hardware and user interface.
Click to expand...
Click to collapse
That sounds good. You have been a great help to me.
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.