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
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.
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.
Hi everyone.
I have some questions about the necessary steps for an update to mm_nexus-rom from my HDX 7 with Safetrap 4.x.x and kk_nexus-rom.
In the forum are too much information and I do not know which of them are still current and which instructions should not be used.
My original HDX 7 had the latest Fire OS 4.5.5.x Version. I used Kingroot and Safetrap 4. to install the kk-nexus-rom. So my bootloader is still locked.
Now i want to update to the mm-fire-nexus-rom withour breaking it, for this i need to unlock my bootloader.
Are the following steps correct?
1: Roll back to 3.2.4 with the steps from .3.2.4 Rollback Images
(Qustion to step 7. Copy the .3.1.0 stock update file to the root of your sdcard: Where do i Find the stock 3.1.0 updatefile)
2: User Flashify to install TWRP 3.0.2.0 from [RECOVERY][UNLOCKED BL] TWRP 3.0.2.0
3: Install mm-nexus-rom from TWRP
Or do i have to use :
[Thor][Apollo] Unlocking bootloader with any firmware
blackson2c said:
Hi everyone.
I have some questions about the necessary steps for an update to mm_nexus-rom from my HDX 7 with Safetrap 4.x.x and kk_nexus-rom.
:
[Thor][Apollo] Unlocking bootloader with any firmware
Click to expand...
Click to collapse
Above procedure is relevant as you can now unlock the bootloader on ANY rooted 3rd gen HDX including those currently running Safestrap v4; risky rollbacks are no longer required. Be aware your device will be wiped during the unlock procedure (not always true but assume it will). Read through the unlock thread; ask questions as needed.
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?
Just got my new to me hdx 7 in the mail, decided to root and install nougat..
Downgraded to 4.5.2 and installed root via kingroot.
Was having problems unlocking the bootloader so I found a method to install cm11 withoutunlockijg bootloader. I got safestrap installed, and installed lineage 14 instead of cm11, and then got stuck in recovery loop, tried factory reset (mistake), and all the unbrick utilities I could find... im so frustrated with this can anyone help please?
updates
adb devices shows
+
D0FBA0A034540445 recovery
keep getting su not found so im assuming the root is no longer good.. please anyone??
SOLVED
Ok I was able to fix this with searching and trial and error, it took me about 5 hours total but all i did was adb push 4.5.5.1 stock rom and it works now.. making backups for now on!!!! thanks anyway !