I tried to do a clean factory reset and activated the stock rom to do so (dumb idea, I guess).
Now it's stuck on the "Deleting..."-screen with the Kindle Fire logo visible.
Tried to hard reset device to access safestrap and restore the backup stock rom, but Safestrap doesn't show up anymore. Instead it shows the "Deleting..."-screen again.
Have I screwed up my Kindle by trying to reset my device with stock rom activated? Or is there any way to access safestrap again?
jsboy said:
I tried to do a clean factory reset and activated the stock rom to do so (dumb idea, I guess).
Now it's stuck on the "Deleting..."-screen with the Kindle Fire logo visible.
Tried to hard reset device to access safestrap and restore the backup stock rom, but Safestrap doesn't show up anymore. Instead it shows the "Deleting..."-screen again.
Have I screwed up my Kindle by trying to reset my device with stock rom activated? Or is there any way to access safestrap again?
Click to expand...
Click to collapse
Which version of safestrap recovery is installed on your kindle? By hard factory reset you mean factory reset in FireOS recovery? Or did you use advanced wipe in safestrap and wipe /system?
jeryll said:
Which version of safestrap recovery is installed on your kindle?
Click to expand...
Click to collapse
I think it was 3.75. I intended to update it to 4.01.
jeryll said:
By hard factory reset you mean factory reset in FireOS recovery? Or did you use advanced wipe in safestrap and wipe /system?
Click to expand...
Click to collapse
I did it via FireOS (ver 3.2.4).
EDIT: Now it went on and rebooted the Kindle Fire HDX. Everything fine now, Safestrap shows up again at startup.
But now I have got the Problem that the Kindle does not recognize the update file for 3.2.5. I put it in the \sdcard folder.
EDIT2: Alright... Figured this one out meanwhile. For anyone with the same problem: The Kindle not detecting the update file. If you disabled OTA via "Kindle Fire HDX Toolkit 0.95" you need to re-enable OTA in KFHDX Toolkit even if you did a factory reset. Otherwise it will block any update files - both over the air from Amazon and locally on your \sdcard folder.
jsboy said:
I think it was 3.75. I intended to update it to 4.01.
I did it via FireOS (ver 3.2.4).
EDIT: Now it went on and rebooted the Kindle Fire HDX. Everything fine now, Safestrap shows up again at startup.
But now I have got the Problem that the Kindle does not recognize the update file for 3.2.5. I put it in the \sdcard folder.
Click to expand...
Click to collapse
I'm glad it's booting... Try put update file to root directory, should recognize it...
If you're on 3.2.4 you sure you want to upgrade? Why not downgrade to 3.2.3.2 and use TWRP? You should stay on 3.2.4 then though, and use the downgrade images provided by ggow.
And DO NOT wipe System in Safestrap v3.x! V4 prevents to do so.
Cl4ncy said:
If you're on 3.2.4 you sure you want to upgrade? Why not downgrade to 3.2.3.2 and use TWRP? You should stay on 3.2.4 then though, and use the downgrade images provided by ggow.
And DO NOT wipe System in Safestrap v3.x! V4 prevents to do so.
Click to expand...
Click to collapse
I wanted to install CM-11. I thought this requires Safestrap v4.01 which requires a rooted 4.5.2. Or am I wrong?
jsboy said:
I wanted to install CM-11. I thought this requires Safestrap v4.01 which requires a rooted 4.5.2. Or am I wrong?
Click to expand...
Click to collapse
This ROM? Well, as it's mentioned there, it will work with TWRP and an unlocked bootloader as well.
I can see that the procedures to downgrade, install TWRP and unlock the bootloader are risky, so you decide. If in doubt ask first, i.e. before you brick your HDX.
Cl4ncy said:
This ROM? Well, as it's mentioned there, it will work with TWRP and an unlocked bootloader as well.
I can see that the procedures to downgrade, install TWRP and unlock the bootloader are risky, so you decide. If in doubt ask first, i.e. before you brick your HDX.
Click to expand...
Click to collapse
Yes, that's the one I would like to install. So do you have a link, where the whole downgrade, installing TWRP and unlocking Bootloader is explained?
jsboy said:
Yes, that's the one I would like to install. So do you have a link, where the whole downgrade, installing TWRP and unlocking Bootloader is explained?
Click to expand...
Click to collapse
So you're still on 3.2.4? Then you can use the rollback Images provided by ggow. Read the description carefully!
On 3.1.0 you can install TWRP, if you haven't done already you should install minimal ADB and fastboot on your PC, you will need it for TWRP Installation (if you don't want to use Flashify), and the bootloader unlock procedure. After the Installation of TWRP you should backup your Fire OS from TWRP and move it to your PC.
Then update to 3.2.3.2 (you can do this in TWRP), then unlock your bootloader, the description is here. Again: if in doubt ask first.
After that you should backup your 3.2.3.2 FireOS and move it to your PC, then you can install the CM11 ROM via TWRP.
Cl4ncy said:
So you're still on 3.2.4? Then you can use the rollback Images provided by ggow. Read the description carefully!
On 3.1.0 you can install TWRP, if you haven't done already you should install minimal ADB and fastboot on your PC, you will need it for TWRP Installation (if you don't want to use Flashify), and the bootloader unlock procedure. After the Installation of TWRP you should backup your Fire OS from TWRP and move it to your PC.
Then update to 3.2.3.2 (you can do this in TWRP), then unlock your bootloader, the description is here. Again: if in doubt ask first.
After that you should backup your 3.2.3.2 FireOS and move it to your PC, then you can install the CM11 ROM via TWRP.
Click to expand...
Click to collapse
Thank you very much for these detailed instructions!
jsboy said:
Thank you very much for these detailed instructions!
Click to expand...
Click to collapse
Tapeinos gave the info that if you install TWRP on 3.1.0 and update to 3.2.3.2 afterwards, you have to re-root (that should be obious, 'cause the 3.2.3.2 update is the official UNrooted Amazon file), but you probably have to re-install TWRP, too. So suggestion would be to update from 3.1.0 to 3.2.3.2, root, disable OTA/stay off WLAN, and install TWRP then, so you don't have to install TWRP twice.
Cl4ncy said:
Tapeinos gave the info that if you install TWRP on 3.1.0 and update to 3.2.3.2 afterwards, you have to re-root (that should be obious, 'cause the 3.2.3.2 update is the official UNrooted Amazon file), but you probably have to re-install TWRP, too. So suggestion would be to update from 3.1.0 to 3.2.3.2, root, disable OTA/stay off WLAN, and install TWRP then, so you don't have to install TWRP twice.
Click to expand...
Click to collapse
By cause I already did it exactly the way you describe it. It worked very well, I'm on CM11 now with an unlocked bootloader.
jsboy said:
By cause I already did it exactly the way you describe it. It worked very well, I'm on CM11 now with an unlocked bootloader.
Click to expand...
Click to collapse
Wow, thanks for the info, you didn't hesitate at all, huh? Great it worked, enjoy CM11.
Related
Hello good people of XDA.
I have managed to get my HDX stuck in a bootloop by trying to install CM11 for safestrap 4 whilst running safestrap 3.75 and am hoping someone can help me unbrick it
- Was running update-kindle-13.3.2.4_user_324002120.bin rooted with Safestrap-Thor-3.75-os3.2.4-B02 installed
- Attempted to install [ROM] [STABLE] CM-11 for Safestrap v4 2015/07/26 on stock ROM slot from within safestrap. All appeared to install OK
- Upon reboot NO SAFESTRAP and does not go past grey kindle fire logo (no animation)
- Device reboots after 40 seconds
- After much faffing around with drivers I DO have adb access (for 40 seconds until device reboots) and can send adb reboot bootloader to the device to get fastboot. Fastboot commands work and device does not reboot when in fastboot
- Can get to stock recovery if i issue adb reboot recovery or power+vol up
- I (foolishly I now realise) did do a "reset to factory defaults" at the stock recovery
- Unsure if I still have root - dont think so though due to doing factory reset
- Cannot flash a system update because the file is 849mb and the device reboots before the transfer is complete and I get a "protocol error". Also possible lack of root may cause this not to work even if i could copy it across
- Tried to flash signed-thor-twrp-2870.img but got FAILED (remote: flashing not allowed for locked hw) when trying to copy to the SDCard
Looks like I have managed to overwrite the safestrap recovery and for whatever reason the CM11 ROM is not loading.
As I understand it, the general process for unbricking a device is:
- get fastboot access [OK]
- flash a recovery [HELP stuck on this]
- Install a ROM from recovery [will be ok with this once I get a recovery working]
I THINK I need to unlock the bootloader so that I can flash a recovery image but I need root to do that which I think I have lost. Is there a way to check? Is there a way to get root back from adb/fastboot? I have tried KFHDX Toolkit to root the device but get "Kindle Fire HDX 7 (cm_thor-userdebug 4.4.4 KTU84Q 8680464d7c test-keys) is not supported" so it is seems to be recognising it as CM11?
I would really appreciate any guidance anyone could give me
Why didn't you read first and ask first before you did all that?
It says CM11 for Safestrap v4! You did NOT have v4! You can NOT install TWRP on 3.2.4, you Need 3.10 - 3.2.3.2 for this. And I don't think you can unlock the 3.2.4 bootloader either.
This looks very bad for you.
So you should have downgraded to 3.2.3.2, install TWRP, unlock bootloader, and flash CM11. Now it seems you don't have a working system anymore.
Cl4ncy said:
Why didn't you read first and ask first before you did all that?
It says CM11 for Safestrap v4! You did NOT have v4! You can NOT install TWRP on 3.2.4, you Need 3.10 - 3.2.3.2 for this. And I don't think you can unlock the 3.2.4 bootloader either.
This looks very bad for you.
So you should have downgraded to 3.2.3.2, install TWRP, unlock bootloader, and flash CM11. Now it seems you don't have a working system anymore.
Click to expand...
Click to collapse
Yeah I realise all of this now. Thought safestrap would protect me if there was a problem.
So, anyone know if there is anything I can do to salvage my device? Was hoping I would be OK since I have fastboot.....
stragen001 said:
Yeah I realise all of this now. Thought safestrap would protect me if there was a problem.
So, anyone know if there is anything I can do to salvage my device? Was hoping I would be OK since I have fastboot.....
Click to expand...
Click to collapse
Amazon's neutered fastboot environment is useless with a locked bootloader (and next to useless when unlocked). "Factory cables" are totally ineffective on an HDX. You can not unlock your bootloader without downgrading which is impossible without a working system AND functioning recovery. There is an outside chance you might be able to root using HDX toolkit (look for it in the Android Development forum) but not sure what that will accomplish given your device is fully borked. You can not flash a new rom with locked bootloader. You can not flash a 'real' recovery with a locked bootloader or bootloader version vunerable to the signature exploit (3.2.4 is not). Ditto for the bootloader itself. I could go on but the point should be obvious.
Hello. I have Kindle Fire HDX with NexusROM firmware (1.4.3), Anroid version: 4.2.2, Kernel version: 3.4.0, Safestrap Recovery v3.72(TWRP v2.7.0.0) and my ROM slot is stock
I want to upgrade my firmware to CM13 without bricking my device.
The steps are:
1) Rollback to .3.2.4 (.3.2.4 Rollback Images) (replace stockrom slot?)
2) Install .3.1.0 stock update firmware. (But where can i take it?)
3) Unlock bootloader with 1-Click bootloader.
4) Install TWRP 3.0.2.0 using Flashify
5) Flash CM13
Does this steps are correct?
n1cklan said:
Hello. I have Kindle Fire HDX with NexusROM firmware (1.4.3), Anroid version: 4.2.2, Kernel version: 3.4.0, Safestrap Recovery v3.72(TWRP v2.7.0.0) and my ROM slot is stock
I want to upgrade my firmware to CM13 without bricking my device.
The steps are:
1) Rollback to .3.2.4 (.3.2.4 Rollback Images) (replace stockrom slot?)
2) Install .3.1.0 stock update firmware. (But where can i take it?)
3) Unlock bootloader with 1-Click bootloader.
4) Install TWRP 3.0.2.0 using Flashify
5) Flash CM13
Does this steps are correct?
Click to expand...
Click to collapse
Looks good, however use 14.3.2.3.2 instead of 14.3.1.0. The reason been graphical glitches, installation issues etc can be avoided.
Let me know if you can't find the stock firmware. I can post it when i am at my PC next time.
ggow said:
Looks good, however use 14.3.2.3.2 instead of 14.3.1.0. The reason been graphical glitches, installation issues etc can be avoided.
Let me know if you can't find the stock firmware. I can post it when i am at my PC next time.
Click to expand...
Click to collapse
Thanks for reply!
How do you know that I have Apollo device?)
I found 14.3.2.3.2 firmware in Stock firmwares for Kindle Fire HDX (Thor-Apollo).
So, i need wipe all partition, then install 14.3.2.4 firmware in my safestrap?
n1cklan said:
Thanks for reply!
How do you know that I have Apollo device?)
I found this firmware in Stock firmwares for Kindle Fire HDX (Thor-Apollo).
So, i need wipe all partition, then install .3.2.4 firmware in my safestrap?
Click to expand...
Click to collapse
Jedi mind trick ?
Just used the 14. Prefix accidentally.
I did a data wipe accidentally in TwRP. Meant to just get cache. Now I lost root/TWRP apparently. Just recently updated to 20c. I have no recovery when I reboot but I still get the unlocked bootloader info when rebooting. Any ideas/help is greatly appreciated.
Jjavitable22 said:
I did a data wipe accidentally in TwRP. Meant to just get cache. Now I lost root/TWRP apparently. Just recently updated to 20c. I have no recovery when I reboot but I still get the unlocked bootloader info when rebooting. Any ideas/help is greatly appreciated.
Click to expand...
Click to collapse
I don't see how wiping data would remove TWRP, but the way I'd reestablish TWRP once it's gone would be to LGUP the Tungkick 10d tot file and then use that TWRP to flash the 20c zip by Autoprime. Flash SuperSU one way or another and then have a blast. I'm sure there are other ways to accomplish all this, but this way is easy and has been reliable for me.
It seems that you can still boot the phone.
If you still have valid bootloader the issue is not that tricky.
Just do a "adb reboot bootloader" and reflash twrp, like how you installed them in the first place.
I'm not sure which exact version of twrp is compatible with v20*, but that should be easy to find anyway.
Then boot into twrp and flash supersu/magisk/any other thing you need.
ReVanTis said:
It seems that you can still boot the phone.
If you still have valid bootloader the issue is not that tricky.
Just do a "adb reboot bootloader" and reflash twrp, like how you installed them in the first place.
I'm not sure which exact version of twrp is compatible with v20*, but that should be easy to find anyway.
Then boot into twrp and flash supersu/magisk/any other thing you need.
Click to expand...
Click to collapse
So I did a factory reset from the settings menu. Now it boots back into TWRP. Weird. But that's it. No OS. Just the recovery. So I guess I'll try and flash a ROM and see if I can get that back. Thanks for trying to help.
Bulkang U. Antibop said:
I don't see how wiping data would remove TWRP, but the way I'd reestablish TWRP once it's gone would be to LGUP the Tungkick 10d tot file and then use that TWRP to flash the 20c zip by Autoprime. Flash SuperSU one way or another and then have a blast. I'm sure there are other ways to accomplish all this, but this way is easy and has been reliable for me.
Click to expand...
Click to collapse
Wasn't sure if I could do any 10s coming from 20C. I got into TWRP recovery but now I have no OS. Thanks for helping out.
Jjavitable22 said:
Wasn't sure if I could do any 10s coming from 20C. I got into TWRP recovery but now I have no OS. Thanks for helping out.
Click to expand...
Click to collapse
Yeah, as long as the ARB is the same (ANTIROLLBACK 01) you can flash 10 after 20. I don't think 10a qualifies, but 10d should be okay from 20a or 20c.
It's a quirk of the G5 that TWRP can only be accessed from boot by factory reset of the phone. If you are already up and rooted, you can use a command or program AFTER boot to access TWRP without factory reset. But, for now, that's our doorway into TWRP from power-off.
Now that you're in TWRP you can sideload a ROM onto your SD and flash it, just remember to also flash the latest superSU zip afterward to ensure root (unless your ROM is pre-rooted.)
So do I need to downgrade or what? How do I root kindle fire os 5.3.3.0? My kindle fire is hd 6 4th gen
Yep. There's a thread around here somewhere outlining the process. The basics are: Set up ADB on Kindle and PC. Sideload Fire OS 4.5.3 to your Kindle via ADB. Block OTA updates. Root via your preferred method. Install TWRP. Use TWRP to flash 5.3.3.0 bootloader and ROM back to your Kindle. Done.
I know it's a pain in the arse to go through all that, and in the end you don't even get to keep TWRP, but as far as I know it's the only possible way to get root on the HD 6 and 7 4th gen right now. At least until Kingroot is updated.
You can't flash twrp right after flashing 5.3.3.0? Or will the kindle not boot?
Sent from my VS990 using Tapatalk
No. Your Kindle would still boot, you just wouldn't have a recovery anymore. For whatever reason TWRP doesn't play well with bootloaders above 4.5.x. So if you were to flash TWRP in 5.x, you overwrite the stock recovery. Upon reboot, TWRP won't work since you have 5.x bootloaders, and your stock recovery is gone since it was overwritten by TWRP. So you're in the nasty situation of having no recovery and no way to get one back.
Somewhere in the rooting thread there is mention of an automated script that will flash 4.5 bootloaders for you and then boot into TWRP. Once you're done just flash your 5.x bootloaders back and reboot. Not a permanent fix, but at least it's all done on the Kindle itself (no need for a PC once it's set up) and there's no chance of ending up without a recovery since TWRP is ran in memory and not flashed so your stock recovery stays intact.
There's a detailed tutorial that I've updated and simplified for 5.3.3.0 here: https://forum.xda-developers.com/showpost.php?p=72466867&postcount=540
Hi all, sorry to jump in here, but does Fire HD 6 have OTG support for flash drive?
I recently upgraded to Nougat 7.1.1 from Marshmallow via Flashfire. I flashed the factory image because it did not automatically recognize the downloaded OTA, and I was concerned that I'd have to go through several incremental OTA upgrades to get where I wanted. I told it to leave my recovery alone (was using TWRP 2.8.6.0 with no problems) and Flashfire went OK. My tablet updated fine, SuperSU 2.82 SR4 (systemless) root was installed, Root Checker says device is rooted and device is reporting in regular recovery that bootloader as unlocked. When I boot into custom recovery, TWRP is still asking for a password (easily bypassed by hitting Cancel), shows none of the file partitions I want, and on reboot system says my "device does not appear to be rooted, install SuperSU now?". I press "Do Not Install" and the tablet boots OK and Root Checker STILL reports the device as being rooted! SuperSU, Titanium, stickmount, etc. all work fine as well.
Are there some settings in TWRP that I need to change? Do I need to upgrade TWRP to 3.1.1.0 flounder? Is it because "Enable OEM unlocking" in Developer Options is off? I looked like crazy last night and can't find a solution . PLEASE HELP!
You will need the latest TWRP to be able to decrypted your device.
Ignore the message from the old version of TWRP about root, it is not detecting the latest root method(systemless).
As for "Enable OEM unlocking" I would advise to enable it, in case of future problems. Is your bootloader unlocked?
Also this months factory image is probably the last version for the device (we might get one more to patch KRACK).
Have you consider backing up apps and switching to a custom rom?
corkiejp said:
You will need the latest TWRP to be able to decrypted your device.
Ignore the message from the old version of TWRP about root, it is not detecting the latest root method(systemless).
As for "Enable OEM unlocking" I would advise to enable it, in case of future problems. Is your bootloader unlocked?
Also this months factory image is probably the last version for the device (we might get one more to patch KRACK).
Have you consider backing up apps and switching to a custom rom?
Click to expand...
Click to collapse
Why is the latest TWRP (3.1.1.0) have "flounder" in it? I thought the Nexus 9 was "volantis". Can I install this latest TWRP image on my tablet without bricking it? Oh, and I can't flash a custom ROM until I get this TWRP crap figured out. Sideloading is not my bag .
Joe_6pak said:
Why is the latest TWRP (3.1.1.0) have "flounder" in it? I thought the Nexus 9 was "volantis". Can I install this latest TWRP image on my tablet without bricking it? Oh, and I can't flash a custom ROM until I get this TWRP crap figured out. Sideloading is not my bag .
Click to expand...
Click to collapse
flounder is just another code name for the device.
You can flash the latest TWRP with fastboot or Install an image from your old TWRP.
Changing TWRP version should not cause a bootloop/bricking.
THANK YOU!
THANK YOU!
THANK YOU!
THANK YOU!
THANK YOU!
THANK YOU!
THANK YOU!
THANK YOU!
THANK YOU!
BTW, thank you!