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.
I have a Z5C(E5803) that was originally able to unlock the bootloader and let me flash ROMs, specifically the Cyanogen ROM that CTXz has been working on. I ran out of power and got stuck in some kind of nasty bootloop yesterday that prompted me to re-flash boot.img and TWRP.
After I did these things I left it charging for a few hours and it was able to boot into TWRP where I then restored it to a backup of the basic Xperia pre-loaded ROM.
This all worked fine, thought I could boot into TWRP and just flash the Cyanogen zip again. I can get into TWRP just fine but I attempt to flash Cyanogen I get an "ERROR 7"
I have since done several wipes, gotten into the bootloader settings by entering that code in the dialer and have seen that bootloader unlock = no. I distinctly remember bootloder unlocking being allowed the first time I installed CM on my device, what could have caused this?
I was able to use it with fastboot anyway and install CM13 again, maybe this was a bug?
When I tried using oem unlock command with fastboot it said my device was already rooted even though I had just restored from a backup, and then I just proceeded normally from there.
use CM13 official Recovery to FLASH CM13.
also i don't think so twrp3.0.2 is out there for z5c. are you using any other variants Twrp? (YUGA ? )
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 !
I'm having major problems with TWRP, and I need help.
I have a Samsung Galaxy S4 with a properly unlocked bootloader (MDL), rooted, that has had a working version of TWRP 2.8.7.0 and running an older version of Cyanogen.
I'm overhauling the phone, so the first thing I tried to do was to update TWRP.
Since TWRP v2.8.7 supports flashing itself, I booted into recovery and flashed the TWRP update (v3.2.1.0) directly through TWRP. No errors that I saw.
But when I try to boot into recovery, I now get "System Software Not Authorized By AT&T Has Been Found On Your Phone". Fortunately, I can still boot normally - it's only recovery that I'm locked out of.
In trying to fix this, I tried re-flashing TWRP with three different methods:
1. I tried to flash TWRP again through the TWRP app. But I get "Flash Failed".
2. I tried Odin and got "FAIL! (Auth)"
3. I tried flashing v3.2.2.0 using the dd method. This I was able to do without any errors, but I'm still locked out of recovery mode with that same "System Software Not Authorized By AT&T Has Been Found On Your Phone" error.
Help?
Try connect to computer and execute:
adb reboot bootloader
fastboot flash recovery twrp-xxxx-xxx.img
Everything should be good to go.
Note: ALL TWRP settings will be reset.
HippoInWindow said:
Try connect to computer and execute:
adb reboot bootloader
fastboot flash recovery twrp-xxxx-xxx.img
Everything should be good to go.
Note: ALL TWRP settings will be reset.
Click to expand...
Click to collapse
ADB works fine for me, but fastboot does not. It says "waiting for any device". From what I understand, this is a common issue with Samsung phones. I'm using Windows 10, if that helps.
However, I came across a bug report for TWRP here, that reports the exact same problem from 3.0.0.0, and it's still open. That tells me that this may be a general issue with TWRP that they never bothered to fix.
So on a hunch, I tried re-flashing v2.8.7 using the dd method (since that's the only one I can get to work). And SUCCESS! I can now boot into recovery again!
So here's what I need to know:
1. Is there any way to get the latest version of TWRP to work on this phone?
2. Is it safe to flash a current version of LineageOS using this version of TWRP (v2.8.7)?
I'm really wary about that second question, because the last thing I want to do is brick my phone because an old version of TWRP doesn't know how to work with a new version of Lineage/Android. (This phone currently has KitKat on it)
You need Rashr to do this. You can find this app on the Google Play Store which can flash images in your system.
1. This version of TWRP should be able to flash modern LineageOS.
2. Using the above method provided should get you up and running the latest TWRP.
HippoInWindow said:
You need Rashr to do this. You can find this app on the Google Play Store which can flash images in your system.
1. This version of TWRP should be able to flash modern LineageOS.
2. Using the above method provided should get you up and running the latest TWRP.
Click to expand...
Click to collapse
I finally found an explanation and solution - it would appear that TWRP 3.x does not have the Loki exploit applied. So nothing 3.0+ will work unless it's been Lokied.
Fortunately, the current versions can be Loki patched, so once that's done, they'll install and work properly. Whew!