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.
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've a Kindle Fire HDX 8.9 with Software 14.3.1.0 (This device is rootet, the bootloader is unlocked, OTA is disabled and it never was connected to the WLAN)
Now i want to install TWRP. Therefore stock image 14.3.2.3.2 is neccessary.
I've downloaded update-kindle-14.3.2.3.2_user_323001720.bin from Amazon website put this to my "internal storage" folder. (rights 755)
But if i go to device -> system updates thers just a button to check for updates. If i click on this one the kindle wants to connect to the internet (got to wlan settings)
Can anyone tell me how to update my Kindle to 14.3.2.3.2
Best reagards
quaker
Actually you can install TWRP on 3.1.0 already, and I'd recommend it, too.
Then you can update the 3.2.3.2 bootloader via TWRP, no need to flash the entire update. Note that you will have to unlock the bootloader again, as both the Fire OS update and the 3.2.3.2 bootloader are not unlocked, at least AFAIR.
And be sure to backup your Fire OS in TWRP and move the backup to your PC before you flash any custom ROM.
OK. Thanks for that. Installation of TWRP on 3.1.0 works. Update bootloader to 3.2.3.2 also.
Hi,
I followed the wrong instructions to root my HDX 7. I hope there is a way to undo my idiotic mistakes.
I have a HDX 7" with Fire OS 4.5.2 rooted with KingRoot. Flashify installed.
I followed [Root] OS 4, 5.0.n and Install Lollipop & Gapps ("Newbie Friendly") to root my kindle, but I only got to step A.
When I followed [How To] Install TWRP on OS 4.5.3 and Boot Recovery (newbie friendly) to try to install TWRP, I couldn't get it to boot in TWRP recovery, it would be stuck in the grey logo forever. I could still boot OS though.
Apparently the instructions are not meant for my device but for HD 6 and 7, but I only realized I was following the wrong thread after the problem occurred.
I am not sure how serious the problem is. I hope you guys can help me fix the problem.
Thank you very much!
snakelam26 said:
Hi,
I followed the wrong instructions to root my HDX 7. I hope there is a way to undo my idiotic mistakes.
I have a HDX 7" with Fire OS 4.5.2 rooted with KingRoot. Flashify installed.
I followed [Root] OS 4, 5.0.n and Install Lollipop & Gapps ("Newbie Friendly") to root my kindle, but I only got to step A.
When I followed [How To] Install TWRP on OS 4.5.3 and Boot Recovery (newbie friendly) to try to install TWRP, I couldn't get it to boot in TWRP recovery, it would be stuck in the grey logo forever. I could still boot OS though.
Apparently the instructions are not meant for my device but for HD 6 and 7, but I only realized I was following the wrong thread after the problem occurred.
I am not sure how serious the problem is. I hope you guys can help me fix the problem.
Thank you very much!
Click to expand...
Click to collapse
You cannot flash lollipop or twrp to hdx 7 as the bootloader is perma locked. The most you can do is use safestrap and flash cm 11 or fire nexus Rom which are both based off 4.4.2 as the kernel is untouchable and can only run these versions. Your attempt at flashing twrp should have had no affect seeing as the it us perma locked so that shouldn't matter
How can I install CWM for the Fire HD 7 (4th gen.)? (KFASWI - Fire HD 6 / 7 - Fire OS 5.1.2)
My Fire has no recovery at all (if I try to boot into recovery it boots normally) and I can't boot into fastboot either (it boots normally).
How can I install CWM? If I try to install TWRP I get no TWRP on reboot.
Please help, I want to install Xposed on it!
CreeperBombCraft said:
How can I install CWM for the Fire HD 7 (4th gen.)? (KFASWI - Fire HD 6 / 7 - Fire OS 5.1.2)
My Fire has no recovery at all (if I try to boot into recovery it boots normally) and I can't boot into fastboot either (it boots normally).
How can I install CWM? If I try to install TWRP I get no TWRP on reboot.
Please help, I want to install Xposed on it!
Click to expand...
Click to collapse
Just follow this :
http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950
Post #2 will get you into TWRP, so you can flash Xposed. Then you'll lose TWRP as you go back into FireOS 5, but can repeat this any time in the future !
bibikalka said:
Just follow this :
http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950
Post #2 will get you into TWRP, so you can flash Xposed. Then you'll lose TWRP as you go back into FireOS 5, but can repeat this any time in the future !
Click to expand...
Click to collapse
That **** called xposed bricked my fire into a bootloop, only after 1 year I could unbrick it using the tutorial from bibi
:fingers-crossed:
As a long-time user, no-time developer on XDA, I appreciate "ClockWorldMod"... sounds like something I would have said in 2010, which really takes me back
FYI ClockWORKMod is the recovery you are referring to, I assume. And TWRP dominates since about 2012 or 2013 (correct me if I'm wrong, I'm no dev), so I certainly back the recommendation to use that tutorial.