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.
Related
Q&A for [RECOVERY] TWRP Recovery 2.8.1.0 - Apollo
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [RECOVERY] TWRP Recovery 2.8.1.0 - Apollo. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
droiduzr2 said:
My device is "bricked". I screwed up safestrap install and my device just boots to the grey kindle screen.
Click to expand...
Click to collapse
Just to clarify: does your device
get stuck forever at
spontaneously restart after
get stuck forever at a blank screen after
the "grey kindle screen"?
I managed to recover from the third alternative, but then I had adb access while the screen was blank...
draxie said:
Just to clarify: does your device
get stuck forever at
spontaneously restart after
get stuck forever at a blank screen after
the "grey kindle screen"?
I managed to recover from the third alternative, but then I had adb access while the screen was blank...
Click to expand...
Click to collapse
my device boots up and stays at grey kindle screen
nothing happens after
That doesn't tell us anything.
How can I check if recovery is installed successfully? I could rollback to 309 and update with stock 310. Then I had to root and followed the instructions in the first post. Adb showed something with in and out, I rebooted and nothing seemed to have changed.
Wher I start with vol + It shows only reboot and factory reset.
Bruder Torgen said:
How can I check if recovery is installed successfully? I could rollback to 309 and update with stock 310. Then I had to root and followed the instructions in the first post. Adb showed something with in and out, I rebooted and nothing seemed to have changed.
Wher I start with vol + It shows only reboot and factory reset.
Click to expand...
Click to collapse
If you're not booting into TWRP, then it probably didn't install.
Try using Flashify.
Great, I had to sideload Flashify apk and install it via adb install, then it worked , I could see the difference
Till now all seems great although the way to reach it is not described perfectly (as I normally have only to do with windows systems, too many steps I had to find out by myself and I never knew if the tablet will be still alive after the next step )
Pretty Good Work , thanks a lot for all your effort !!!!
Factory Reset?
droiduzr2 said:
my device boots up and stays at grey kindle screen
nothing happens after
Click to expand...
Click to collapse
I see... I suppose you have checked, and adb doesn' t work..
(Otherwise, although a long shot, it may be worth double-checking.)
BUT, you say you can get into recovery (Power+VolumeUp, I assume):
droiduzr2 said:
I can get into that weird looking recovery that does not allow fastboot.
Click to expand...
Click to collapse
The Amazon stock recovery should have a 'Factory Reset' option.
Have you tried that one? (WARNING: all your data will likely be gone; not sure if it helps with the OS, though...)
BTW, do you remember _how_ exactly messing up SafeStrap happened?
If you provide details, someone with a more intimate understanding of how SafeStrap works
may have an idea how you might go about getting your device back to life again.
draxie said:
I see... I suppose you have checked, and adb doesn' t work..
(Otherwise, although a long shot, it may be worth double-checking.)
BUT, you say you can get into recovery (Power+VolumeUp, I assume):
The Amazon stock recovery should have a 'Factory Reset' option.
Have you tried that one? (WARNING: all your data will likely be gone; not sure if it helps with the OS, though...)
BTW, do you remember _how_ exactly messing up SafeStrap happened?
If you provide details, someone with a more intimate understanding of how SafeStrap works
may have an idea how you might go about getting your device back to life again.
Click to expand...
Click to collapse
Thank you for the detailed response.
Yes, I did install safestrap. I admit I did not fully understand what I was doing. I thought I would just wipe everything to have a clean system as we usually do for most devices. I wiped the system also which deleted the system rom.
Upon reboot it just sits at the grey kindle screen never booting past. I played around with the buttons and stumbled upon the power and vol+.
I got into Kindle system recovery and did the wipes but nothing boots up because I deleted the system os.
Would ADB work from the Kindle recovery screen?
Remember I have no OS on the device now.
Please let me know what to do now?
Where are the Kindle drivers for Win7 which has ADB driver for it. The problem is windows will not recognize the device I don't think.
14.3.2.4 can have twrp?
I want to install the nuxus rom into my HDX 8.9 with twrp.
I just wonder if I can install the twrp to my 14.3.2.4 version HDX.
Can I ?
by the way, I cannot find a step-by-step twrp install procedure.
If someone posts a youtube video, it will be awesome.
vandy_andy said:
I want to install the nuxus rom into my HDX 8.9 with twrp.
I just wonder if I can install the twrp to my 14.3.2.4 version HDX.
Can I ?
by the way, I cannot find a step-by-step twrp install procedure.
If someone posts a youtube video, it will be awesome.
Click to expand...
Click to collapse
No, you need to downgrade to a firmware version older than x.3.2.4.
http://forum.xda-developers.com/showthread.php?t=2782159
EncryptedCurse said:
No, you need to downgrade to a firmware version older than x.3.2.4.
http://forum.xda-developers.com/showthread.php?t=2782159
Click to expand...
Click to collapse
Thank you for the answer.
So , so far no easy way.
Apollo first release of TWRP started at .0 flashed renamed files each increment up to and including .2.4 I know I can redo the downgrade and anything else I need to do once I get a usable ui
well like a dumbA I tried to upgrade via rename bin to zip got to .2.4 lost any recovery and black screen.... I do have root and adb shell permission and it does boot ,charge etc. Just no display for most part like any launcher .. ( I still got super user prompt for ADB shell )...I also wiped data for all user and system apps via titanium backup not sure if that made black screen or not .... need to flash stock .2.4 recovery? To fix black screen? Or do I need to push a Specific file ? That of which I do not know the details of . Because I don't know which files would have been deleted by titanium backup . The device has been sitting for a few weeks now I figure it's time to get it up and running any help would be appreciated thanks
jimyv said:
Apollo first release of TWRP started at .0 flashed renamed files each increment up to and including .2.4 I know I can redo the downgrade and anything else I need to do once I get a usable ui
well like a dumbA I tried to upgrade via rename bin to zip got to .2.4 lost any recovery and black screen.... I do have root and adb shell permission and it does boot ,charge etc. Just no display for most part like any launcher .. ( I still got super user prompt for ADB shell )...I also wiped data for all user and system apps via titanium backup not sure if that made black screen or not .... need to flash stock .2.4 recovery? To fix black screen? Or do I need to push a Specific file ? That of which I do not know the details of . Because I don't know which files would have been deleted by titanium backup . The device has been sitting for a few weeks now I figure it's time to get it up and running any help would be appreciated thanks
Click to expand...
Click to collapse
Well, if you have adb access and root, you can try this
jeryll said:
Well, if you have adb access and root, you can try this
Click to expand...
Click to collapse
actually I had seen this and had thought I might give that a shot but I do not have any recovery the flash of. 2.4 borked the recovery ..I know this because I tried to boot into it several times before flashify geek out on my paid subscription because my Google stopped working. That's why I attempted to wipe the data for all the apps. So I can attempt to use flashify to restore stock recoveryI believe it was when I picked option in Titanium Backup to wipe all data for system and user apps. Not really because of the fact I did not have a functioning recovery. I do not believe because I had rebooted the serval times and still had a working system until I wiped the data. Maybe if I had a copy of the stock image recovery I could attempt to flash it then try that...? I did extract the .2.4 files but didn't spot recovery image
jimyv said:
actually I had seen this and had thought I might give that a shot but I do not have any recovery the flash of. 2.4 borked the recovery ..I know this because I tried to boot into it several times before flashify geek out on my paid subscription because my Google stopped working. That's why I attempted to wipe the data for all the apps. So I can attempt to use flashify to restore stock recoveryI believe it was when I picked option in Titanium Backup to wipe all data for system and user apps. Not really because of the fact I did not have a functioning recovery. I do not believe because I had rebooted the serval times and still had a working system until I wiped the data. Maybe if I had a copy of the stock image recovery I could attempt to flash it then try that...? I did extract the .2.4 files but didn't spot recovery image
Click to expand...
Click to collapse
if you need recovery.img for Thor here is one, confirmed its working here
if you need stock recovery.img for Apollo here is one + md5 file here, its for 14.3.1.0 (md5 hash: acb175637241e6ecaf6dfef5ba7f343b)
jeryll said:
if you need recovery.img for Thor here is one, confirmed its working here
if you need stock recovery.img for Apollo here is one + md5 file here, its for 14.3.1.0 (md5 hash: acb175637241e6ecaf6dfef5ba7f343b)
Click to expand...
Click to collapse
Apollo first release of TWRP started at (.0) flashed renamed files each increment up to and including( .2.4 )I know I can redo the downgrade and anything else I need to do once I get a usable ui
not unless the recovery is black screen also. What is strange is when it is booted and I tried adb shell I did get su prompt ,,, just no launcher or notification bar etc..this is what I'm thinking let me know if I am mistaken. I should grab and flash a stock recovery image via the same as flashing this recovery with PC. Push. 3.2 build prop file to system then try this. http://forum.xda-developers.com/show....php?t=2793253 with .2.4 WiFi was off before black screen and OTA had been re- enabled I believe.and this is probably important to I do actually have a lock screen. And poweroff menu I am going to try that command now..
access denied going to reboot everything and try again
this is double posted in main thread with @ggow
Maybe a silly or noob question, but I have no answer (maybe I missed it although I read this thread) ..
I'm on TWRP 2.8.1.0 (and have Nexus 2.0.5). Is there an easy update way to 2.8.5.0 ? I can't imagine that I've to go back to stock rom ?!
Bruder Torgen said:
Maybe a silly or noob question, but I have no answer (maybe I missed it although I read this thread) ..
I'm on TWRP 2.8.1.0 (and have Nexus 2.0.5). Is there an easy update way to 2.8.5.0 ? I can't imagine that I've to go back to stock rom ?!
Click to expand...
Click to collapse
It's as simple as flashing the new image.
This is no different than any other device.
I thought the root for 4.5.2 and there's no root for 4.5.3 this is why I didn't update and disabled OTA. How can this method is for 4.5.3 only and it requires root? I think I miss something here. Please, help me to get it
I am on rooted Thor with 13.3.2.4, with the Nexus Rom installed via safestrap. I have been reading all the threads on unlocking the bootloader and find all of the steps to be very scary. I would like to wait until there was some kind of "toolkit" for this rather than having to first downgrade and then use python through adb etc which I am somewhat uncomfortable with. Will there ever be such a simpler solution?
The bootloader unlock procedure is a no brainer, can't mess up anything there. Downgrading is a little risky, but you're on 3.2.4, thus you can even use the rollback images for Safestrap, take a look at this thread (page 1 is about 3.2.5/3.2.6 users who can NOT use the downgrade images). I'm afraid it won't get any easier than that.
If you don't want to use Python, just execute the adb commands to get your ID and serial (post them here, or PM me if you don't want anyone to see them), I'll create the .unlock file for you then. Downgrading and (actual) unlocking are tasks you have to do yourself though.
I think I might try it this weekend. Thanks for the help.
Cl4ncy said:
The bootloader unlock procedure is a no brainer, can't mess up anything there. Downgrading is a little risky, but you're on 3.2.4, thus you can even use the rollback images for Safestrap, take a look at this thread (page 1 is about 3.2.5/3.2.6 users who can NOT use the downgrade images). I'm afraid it won't get any easier than that.
If you don't want to use Python, just execute the adb commands to get your ID and serial (post them here, or PM me if you don't want anyone to see them), I'll create the .unlock file for you then. Downgrading and (actual) unlocking are tasks you have to do yourself though.
Click to expand...
Click to collapse
I have successfully downgraded to 13.3.1.0, but I am confused about how to install TWRP. Since I have not enabled wifi and registered, I can't install flashify or cwm, or even install a file explorer apk to access my storage, and I don't know how to get the twrp.img file (which I guess I can only install via adb?) Where do I get the correct twrp.img file? I'm kind of stuck....
kbs24 said:
I have successfully downgraded to 13.3.1.0, but I am confused about how to install TWRP. Since I have not enabled wifi and registered, I can't install flashify or cwm, or even install a file explorer apk to access my storage, and I don't know how to get the twrp.img file (which I guess I can only install via adb?) Where do I get the correct twrp.img file? I'm kind of stuck....
Click to expand...
Click to collapse
I am by no means an expert but I just went through this process myself yesterday and it was relatively simple. Check this thread. It has a number of helpful posts in it, including my questions from yesterday.
The correct TWRP image is here. Just follow the instructions in that thread. It's super simple if you use the minimal adb and fastboot linked by Cl4ncy in the first thread I linked. If you have any other questions I'll do my best to help you.
kbs24 said:
I have successfully downgraded to 13.3.1.0, but I am confused about how to install TWRP. Since I have not enabled wifi and registered, I can't install flashify or cwm, or even install a file explorer apk to access my storage, and I don't know how to get the twrp.img file (which I guess I can only install via adb?) Where do I get the correct twrp.img file? I'm kind of stuck....
Click to expand...
Click to collapse
Sorry for the late reply, @muunkin pointed you in the right direction already.
Be sure to (re-)root 3.1.0 and disable OTA via HDX ToolKit, and enable USB debugging in Fire OS, hope you installed minimal adb and fastboot, then copy the TWRP image for your HDX (Thor = 7", Apollo = 8.9") to the root of the sdcard (which is the directory you'll see in Explorer after connecting the HDX to your PC, i.e. don't open another directory), open a DOS box, change dir to the adb directory (enter cd\adb) and enter the commands mentioned in the TWRP thread. This will flash the TWRP image to the recovery parition.
Do a backup of your Fire OS in TWRP before you flash any custom ROM, and copy it to your PC, also look for the TWRP backup of the stock recovery (I think TWRP does a backup somewhere), and move that to your PC as well.
In case you don't know how to access TWRP: with the HDX powered off, you press and hold volume up, then press and hold the power button, release both when the grey Kindle Fire logo appears on screen. Some ROMs (e.g. CM12) offer the advanced reboot in developer options, this will add options to reboot into recovery, bootloader or a soft (quick) reboot to the power menu.
Cl4ncy said:
Sorry for the late reply, @muunkin pointed you in the right direction already.
Be sure to (re-)root 3.1.0 and disable OTA via HDX ToolKit, and enable USB debugging in Fire OS, hope you installed minimal adb and fastboot, then copy the TWRP image for your HDX (Thor = 7", Apollo = 8.9") to the root of the sdcard (which is the directory you'll see in Explorer after connecting the HDX to your PC, i.e. don't open another directory), open a DOS box, change dir to the adb directory (enter cd\adb) and enter the commands mentioned in the TWRP thread. This will flash the TWRP image to the recovery parition.
Do a backup of your Fire OS in TWRP before you flash any custom ROM, and copy it to your PC, also look for the TWRP backup of the stock recovery (I think TWRP does a backup somewhere), and move that to your PC as well.
In case you don't know how to access TWRP: with the HDX powered off, you press and hold volume up, then press and hold the power button, release both when the grey Kindle Fire logo appears on screen. Some ROMs (e.g. CM12) offer the advanced reboot in developer options, this will add options to reboot into recovery, bootloader or a soft (quick) reboot to the power menu.
Click to expand...
Click to collapse
Thank you both @muunkin and @Cl4ncy for guiding me through this. It is clear now that I have to flash TWRP via adb. Unfortunately I did, however, last night briefly turn on wifi in order to get es file explorer, and very quickly the OS ugraded itself to 13.3.2.3. Then, stupidly, I decided to go back to Nexus rom 2.0.2, which I did by reinstalling safestrap. And, Nexus rom is installed on the Stock Rom slot, and I did NOT backup the 13.3.2.3 stock rom. SO, since I am on Nexus rom, do I understand correctly that I need to begin again by downgrading to 13.3.1.0? Right? (After printing out all of these threads and printing out a lot of it and carefully reading, it looks to me like if I had stayed on stock 13.3.2.3 I would not have had to downgrade.....but too late now anyway.) I do have the minimal adb and fastboot installed, and my device is recognized, so eventually this will work I'm pretty sure. I appreciate the help!
kbs24 said:
Thank you both @muunkin and @Cl4ncy for guiding me through this. It is clear now that I have to flash TWRP via adb. Unfortunately I did, however, last night briefly turn on wifi in order to get es file explorer, and very quickly the OS ugraded itself to 13.3.2.3. Then, stupidly, I decided to go back to Nexus rom 2.0.2, which I did by reinstalling safestrap. And, Nexus rom is installed on the Stock Rom slot, and I did NOT backup the 13.3.2.3 stock rom. SO, since I am on Nexus rom, do I understand correctly that I need to begin again by downgrading to 13.3.1.0? Right? (After printing out all of these threads and printing out a lot of it and carefully reading, it looks to me like if I had stayed on stock 13.3.2.3 I would not have had to downgrade.....but too late now anyway.) I do have the minimal adb and fastboot installed, and my device is recognized, so eventually this will work I'm pretty sure. I appreciate the help!
Click to expand...
Click to collapse
No, 13.3.2.3 is ok for both TWRP and unlocking the bootloader, i.e. no need to flash 3.1.0 again - a firmware below 3.2.4 is enough.
Cl4ncy said:
No, 13.3.2.3 is ok for both TWRP and unlocking the bootloader, i.e. no need to flash 3.1.0 again - a firmware below 3.2.4 is enough.
Click to expand...
Click to collapse
Even if I am not running on the stock rom? I can adb install TWRP while on Nexus rom?
kbs24 said:
Even if I am not running on the stock rom? I can adb install TWRP while on Nexus rom?
Click to expand...
Click to collapse
Hm, I'm not exactly sure about this - @ggow's answer here seems to point out that you really have to do it all over again.
Why did you install Safestrap again anyway? ADB-flashing TWRP and unlocking the bootloader before you install a custom ROM would've been the next steps. Also I told you to create a backup of your stock slot before you flash any custom ROM, didn't I?
Cl4ncy said:
Hm, I'm not exactly sure about this - @ggow's answer here seems to point out that you really have to do it all over again.
Why did you install Safestrap again anyway? ADB-flashing TWRP and unlocking the bootloader before you install a custom ROM would've been the next steps. Also I told you to create a backup of your stock slot before you flash any custom ROM, didn't I?
Click to expand...
Click to collapse
Yes you sure did, and that's why I said "stupidly" about me putting safestrap back and nexus rom. I was overanxious and acted impulsively, not having a recovery installed was freaking me out. Bad habit. About doing the backup, there did not appear to be enough room on the internal storage. Sorry. We'll start over no problem. Again thanks.
kbs24 said:
Yes you sure did, and that's why I said "stupidly" about me putting safestrap back and nexus rom. I was overanxious and acted impulsively, not having a recovery installed was freaking me out. Bad habit. About doing the backup, there did not appear to be enough room on the internal storage. Sorry. We'll start over no problem. Again thanks.
Click to expand...
Click to collapse
I'm also not sure how to do this now. You don't have any Safestrap 3.2.3 Fire OS backup to restore, you shouldn't use the 3.2.4 rollback image, as you're not on 3.2.4, so what do you want to flash to the stock slot now? Or did I miss anything?
Cl4ncy said:
I'm also not sure how to do this now. You don't have any Safestrap 3.2.3 Fire OS backup to restore, you shouldn't use the 3.2.4 rollback image, as you're not on 3.2.4, so what do you want to flash to the stock slot now? Or did I miss anything?
Click to expand...
Click to collapse
I was going to look for a stock 3.2.3 to flash. If can't find, I do have a backup of stock 3.2.4 on the card which I would flash, thus requiring the downgrade.
kbs24 said:
I was going to look for a stock 3.2.3 to flash. If can't find, I do have a backup of stock 3.2.4 on the card which I would flash, thus requiring the downgrade.
Click to expand...
Click to collapse
I haven't seen a 3.2.3 Safestrap flashable Image, good luck. Regarding the 3.2.4 backup I'm not sure whether it works with the 3.2.3 bootloader.
Cl4ncy said:
I haven't seen a 3.2.3 Safestrap flashable Image, good luck. Regarding the 3.2.4 backup I'm not sure whether it works with the 3.2.3 bootloader.
Click to expand...
Click to collapse
Yeah, I am probably screwed. But we'll see. I'm pretty sure I understand what the process should be at least.
kbs24 said:
Yeah, I am probably screwed. But we'll see. I'm pretty sure I understand what the process should be at least.
Click to expand...
Click to collapse
Not sure how far you got with this but you *should* be able to flash TWRP from Nexus provided the version of FireOS was 3.2.3.2 or lower prior to the installation of Safestrap v3. The customized version of twrp leverages a vulnerability in the HDX bootloader that is installed with FireOS. Neither Safestrap nor Nexus mess with the bootloader so the prerequisites should remain intact. I say should as interactions are complex - further complicated by a fussy device with limited recovery capability should something go wrong. To the best of my knowledge no one has attempted a twrp flash from Nexus while Safestrap v3 is installed.
Thoughts:
- grab flashify from the play store or here; make a backup of your current recovery environment (this step will also help to familiarize you with flashify)
- download the HDX customized version of twrp (here); use ES File Explorer to verify MD5
- use flashify to install twrp (can also be done via adb commands as shown in the twrp op)
Options:
- unlock the bootloader before attempting other remedial steps. Unlocking is a frustrating but low/no risk activity that yields substantially improved recovery capabilities once completed. Yep - you can do this without twrp (unlocking before flashing twrp is the recommended path according to several devs - although I prefer the opposite).
[-or-]
- flash 3.1.0 from here to the stock slot and then attempt to remove Safestrap v3. If successful you can proceed with flashing twrp unlocking, etc in the normal manner. As with any flash there is a risk something will go wrong or FireOS will not start up properly. To help mitigate the latter suggest installing a fallback version of Nexus v2 in a secondary slot. Don't forget to remove this slot before uninstalling SS.
The above is only an outline. Give it some thought and post any questions BEFORE taking action. I also suggest you let this post sit for a few days in case some of the rational is fatally flawed. Lots of smart people in the community who will jump in if my guidance is misdirected (which it has been shown to be on occasion). Don't risk a brick by acting too quickly. Proper preparation is essential for a successful outcome.
Sorry for sounding like your mum ... :angel:
Davey126 said:
Not sure how far you got with this but you *should* be able to flash TWRP from Nexus provided the version of FireOS was 3.2.3.2 or lower prior to the installation of Safestrap v3. The customized version of twrp leverages a vulnerability in the HDX bootloader that is installed with FireOS. Neither Safestrap nor Nexus mess with the bootloader so the prerequisites should remain intact. I say should as interactions are complex - further complicated by a fussy device with limited recovery capability should something go wrong. To the best of my knowledge no one has attempted a twrp flash from Nexus while Safestrap v3 is installed.
Thoughts:
- grab flashify from the play store or here; make a backup of your current recovery environment (this step will also help to familiarize you with flashify)
- download the HDX customized version of twrp (here); use ES File Explorer to verify MD5
- use flashify to install twrp (can also be done via adb commands as shown in the twrp op)
Options:
- unlock the bootloader before attempting other remedial steps. Unlocking is a frustrating but low/no risk activity that yields substantially improved recovery capabilities once completed. Yep - you can do this without twrp (unlocking before flashing twrp is the recommended path according to several devs - although I prefer the opposite).
[-or-]
- flash 3.1.0 from here to the stock slot and then attempt to remove Safestrap v3. If successful you can proceed with flashing twrp unlocking, etc in the normal manner. As with any flash there is a risk something will go wrong or FireOS will not start up properly. To help mitigate the latter suggest installing a fallback version of Nexus v2 in a secondary slot. Don't forget to remove this slot before uninstalling SS.
The above is only an outline. Give it some thought and post any questions BEFORE taking action. I also suggest you let this post sit for a few days in case some of the rational is fatally flawed. Lots of smart people in the community who will jump in if my guidance is misdirected (which it has been shown to be on occasion). Don't risk a brick by acting too quickly. Proper preparation is essential for a successful outcome.
Sorry for sounding like your mum ... :angel:
Click to expand...
Click to collapse
Thanks for your input. I am still on the nexus rom, but I am fairly sure that Safestrap was installed while on 13.3.2.4. Is there a way to tell? It is safestrap 3.75, based on twrp 2.7.
I had some time today to work on this, and after looking over the ideas from all of you (thank you very much!) it seemed that my only option is to restore my backup which will get me back to the Nexus 2.0.2 rom. So I did this successfully. Being on Nexus rom, I was then able to use the 13.3.2.4 rollback file to get back to 13.3.0.9. Then ran into trouble......the system update to 13.3.1.0 was not successful. the .bin file was located, but all that happened was a "validating update file" followed by forced reboot. I remain stuck on 13.3.0.9. There are threads discussing editing build.prop but I know I did not have to do this when I first did a rollback a few days ago. Not sure whether to give up or maybe someone has another idea how to get the system to use that .bin file? Should I turn on wifi and wait for an ota or is that too risky, will it jump me all the way up to the most current build? Will it maybe go incrementally?
kbs24 said:
Thanks for your input. I am still on the nexus rom, but I am fairly sure that Safestrap was installed while on 13.3.2.4. Is there a way to tell? It is safestrap 3.75, based on twrp 2.7.
Click to expand...
Click to collapse
(Also as you suggested, I did try flashing the zip 3.1.0 and it did not work, never rebooted successfully. So went back again to 3.0.9.)
kbs24 said:
I had some time today to work on this, and after looking over the ideas from all of you (thank you very much!) it seemed that my only option is to restore my backup which will get me back to the Nexus 2.0.2 rom. So I did this successfully. Being on Nexus rom, I was then able to use the 13.3.2.4 rollback file to get back to 13.3.0.9. Then ran into trouble......the system update to 13.3.1.0 was not successful. the .bin file was located, but all that happened was a "validating update file" followed by forced reboot. I remain stuck on 13.3.0.9. There are threads discussing editing build.prop but I know I did not have to do this when I first did a rollback a few days ago. Not sure whether to give up or maybe someone has another idea how to get the system to use that .bin file? Should I turn on wifi and wait for an ota or is that too risky, will it jump me all the way up to the most current build? Will it maybe go incrementally?
Click to expand...
Click to collapse
Glad you were able to make some progress. I believe you could have flashed twrp from Nexus as I believe you successfully downgraded/upgraded to 13.3.2.3 which would then be the base version when you reininstalled Safestrap. But you found another path which is just fine.
It is possible the 13.3.1.0 is invalid (possibly corrupt). You can use ES File Explorer to validate the MD5 (c49c0363de4d8dfa5c87c1bdb88aa2ba) or download a fresh copy here. You can also upgrade directly to 13.3.2.3 instead of hopscotching through 13.3.1.0 and then applying the 13.2.3.3 bootloader update.
I strongly suggest you NOT connect to WiFi as it is unpredictable if/when you will receive at OTA and what version will be downloaded. Options for getting files onto you device:
- use HDX toolkit to root and block OTA on 13.3.0.9; you can then enable WiFi
- tether your device and drop files into "Internal Storage"
- use 'adb push' to transfer files
You should not need to mess with build.prop as the 3.2.4->3.0.9 rollback should have handed that. It's quite easy to brick your device if you get any of the edits or permissions wrong.
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!
Dear forum,
I had installed the Nexus Custom ROM with TWRP on my Kindle HDX which worked out fine so far. Then I and wanted to go to CM11. Probably because my device was still locked and/or because I wiped too many things in the wipe-menu, my kindle is stuck in the Boot loop and stops loading while displaying the grey kindle logo. I am still able to access TWRP and the device is found by windows.
I would like to go back to the stock rom and read a lot of threads in the forum but I am not really sure where to start without making my situation worse. I tried to install back my backup (several *.win files) but that does not work. Can you please help me what I need to do?
Kind regards,
Aldaris001
Aldaris001 said:
Dear forum,
I had installed the Nexus Custom ROM with TWRP on my Kindle HDX which worked out fine so far. Then I and wanted to go to CM11. Probably because my device was still locked and/or because I wiped too many things in the wipe-menu, my kindle is stuck in the Boot loop and stops loading while displaying the grey kindle logo. I am still able to access TWRP and the device is found by windows.
I would like to go back to the stock rom and read a lot of threads in the forum but I am not really sure where to start without making my situation worse. I tried to install back my backup (several *.win files) but that does not work. Can you please help me what I need to do?
Kind regards,
Aldaris001
Click to expand...
Click to collapse
TWRP or Safestrap (version)? They are not the same thing. Makes a big difference in the potential solution set.
Thanks for your swift reply! I have TWRP 2.8.6.0 installed.
Aldaris001 said:
Thanks for your swift reply! I have TWRP 2.8.6.0 installed.
Click to expand...
Click to collapse
Strongly recommend unlocking bootloader with 1-click utility (here). Otherwise you run the risk of permanently bricking your device if the recovery partition holding TWRP becomes damaged/unbootable. Once unlocked you can flash a modified build of FireOS 4.5.5 from here
Of course, once unlocked you could flash a higher version of Nexus, CM 11 (both KitKat based), CM 12.1 (Lollipop), CM 13 (Marshmallow) or several other rom variants. Each is a heck of a lot better than Stock FireOS v4.
At some point you should also consider moving to the latest version of TWRP (here).
Hi Davey,
Thanks a lot for the hint! I have tried the 1-click bootloader but running in an issue that the ADB device is not recognized. The drivers seem to work though. Do I need to activate ADB in TWRP somewhere or is it activated by default? The ADB sideload option seem to be something else, right?
Aldaris001 said:
Hi Davey,
Thanks a lot for the hint! I have tried the 1-click bootloader but running in an issue that the ADB device is not recognized. The drivers seem to work though. Do I need to activate ADB in TWRP somewhere or is it activated by default? The ADB sideload option seem to be something else, right?
Click to expand...
Click to collapse
Drivers are always a PiTA with Windows and Amazon devices. You'll need to fight through it taking clues from various posts on the topic. Some tips:
- nothing needs to be enabled in TWRP
- drivers need to work in both ADB and Fastboot modes
- cleanest approach IMO:
>> launch windows device manager, tether device, see what shows up in device manager, uninstall those device(s), disconnect, reboot both devices (important), reconnect and then guide windows to the drivers of your choosing
Thanks a lot for your help, I got it running again! In the end it did not work with the 1-click method but manually I could unlock the bootloader and flashed CM 12.1.
Aldaris001 said:
Thanks a lot for your help, I got it running again! In the end it did not work with the 1-click method but manually I could unlock the bootloader and flashed CM 12.1.
Click to expand...
Click to collapse
Thanks for the update. Glad you got things sorted; manual unlocking isn't that bad with a little patience. CM 12.1 is solid (probably my next stop; still rocking Nexus) but keep an eye on CM 13 as the dev team hammers out a few final issues. Enjoy your liberated HDX!