unable to factory reset after having twrp and roms installed.. - Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot

Does anyone know what is wrong here? I wanted to get back to stock by flashing Amazon's stock .bin (changed to .zip) in twrp. I've done this before and had no issues. In twrp I wiped everything and then flashed the .zip. Then I booted into the Amazon OS and everything appeared fine. I'm on 14.3.2.5. For one, I cannot factory reset. After trying to do so, it reboots to the Kindle logo and just permanently hangs there. If I try to update it manually to 14.4.5.5, once again, it just hangs on the Kindle logo. It appears I have no recovery or something. What I don't understand is that I've done this in the past with no issue. Where I am now is that I am able to boot without issue into 14.3.2.5, but cannot update. What can I do?
edit: http://forum.xda-developers.com/showpost.php?p=55759790&postcount=204 fixed it. It restored my stock recovery and I was able to update and factory reset after doing it.

Related

Help with upgrading firmware through odin. Phone stuck on boot animation

Hi all,
I am trying to update my phone to a new firmware using odin. I am following the instructions in this thread. However after odin has done its thing, it displays "PASS!", my phone reboots but then hangs on the boot animation. I have left it for about 20 mins and tried reflashing the rom with no luck.
I have also tried another firmware, but its gets stuck in a half bootloop (repeating the boot animation)
Does anyone know what might be causing this and how I can fix it?
Thanks
Aaron
Boot to recovery and wipe cache see if that works, if it still bootloops you'll need to boot to recovery and do a factory reset.
I booted into recovery and wiped everything, and it works now.
Thanks

TWRP - wipe cache/dalvik/anything.... soft brick...

So I have been following the unofficial cm-10.2 ROM. I have dirty flashed probably 3 times without issue. I flash the ROM, a pinlock removal zip and gapps. Then wipe dalvik/cache and reboot. I started doing this with twrp 2.6.
So this morning I grab the latest update, backup, flash.l, reboot.... nothing.
Stuck at LG logo to a black screen. I can get into bootloader, blindly vol down twice and into recovery, now twrp 2.5, so I try to recover by backup, reboot.... black screen.
So I try wiping/factory reset, clean flash, reboot.... black screen...
Now I am a little concerned. I read up and find out about TeenyBin, so I setup my machine to flash the standard zip and that doesn't really work, it flashes fine, reboots but is stuck at LG logo and the tool reports disconnected, so the tool fails kind of. So I try the alternate, same sort of thing, but now it says Google instead of LG and is stuck there. I can get into bootloader, can see text now (nice!) and get into recovery, still 2.5. Tried restoring, wiping/flashing, nothing working..... stuck at Google logo.
So, then I went and formatted internal storage. Bingo! Now I can flash/restore/whatever and I can reboot and get into ROM!
Woah, woah, woah... Not so fast.
So now if I wipe anything, cache/dalvik/system/ANYTHING it soft bricks. I have to again format internal, then flash. That doesn't seem right to me. Sure, I have a functioning phone, but updating is a bigger ***** now that I have to completely format before flashing.
So my question to you all, how do I fix this? Do I need to completely go back to stock image and reroot? I appreciate all your suggestions.
daveerickson said:
So I have been following the unofficial cm-10.2 ROM. I have dirty flashed probably 3 times without issue. I flash the ROM, a pinlock removal zip and gapps. Then wipe dalvik/cache and reboot. I started doing this with twrp 2.6.
So this morning I grab the latest update, backup, flash.l, reboot.... nothing.
Stuck at LG logo to a black screen. I can get into bootloader, blindly vol down twice and into recovery, now twrp 2.5, so I try to recover by backup, reboot.... black screen.
So I try wiping/factory reset, clean flash, reboot.... black screen...
Now I am a little concerned. I read up and find out about tinyrom, so I setup my machine to flash the standard zip and that doesn't really work, it flashes fine, reboots but is stuck at LG logo and the tool reports disconnected, so the tool fails kind of. So I try the alternate, same sort of thing, but now it says Google instead of LG and is stuck there. I can get into bootloader, can see text now (nice!) and get into recovery, still 2.5. Tried restoring, wiping/flashing, nothing working..... stuck at Google logo.
So, then I went and formatted internal storage. Bingo! Now I can flash/restore/whatever and I can reboot and get into ROM!
Woah, woah, woah... Not so fast.
So now if I wipe anything, cache/dalvik/system/ANYTHING it soft bricks. I have to again format internal, then flash. That doesn't seem right to me. Sure, I have a functioning phone, but updating is a bigger ***** now that I have to completely format before flashing.
So my question to you all, how do I fix this? Do I need to completely go back to stock image and reroot? I appreciate all your suggestions.
Click to expand...
Click to collapse
Give CWM a shot and see if it does the same thing?

stuck in bootloop

First off I am on mdk and rooted and up until today have been running hd 10.2. I had been having some weird things happen with twrp 2502 so I went into goo and tried to update to the newest version of twrp. it downloaded and went through with everything and I rebooted into recovery. once I got into recovery it was showing I was still on 2502, but it was asking for a password which I had never seen before. I backed out and tried to boot into my rom again and it got stuck on the samsung custom screen. pulled the battery a few times and still kept getting stuck. went back into recovery and tried to restore a known good backup that I had restored before, but it keeps failing. I had rls12 on my phone so I tried installing it dirty since I cant wipe anything due to the whole password thing in twrp which said it was succesful but still gets stuck on the samsung custom screen. it sits there for about 10 seconds and loops. I tried about 10 more times to get my backup restored and it finally finished and booted into the rom. I left it this way for an hour or so and did some stuff with my phone, tried to update twrp again which did the same thing again and still shows 2502. after the reboot I am back to the same problem of not being able to do anything in twrp except restore or dirty flash, I cant get the usb to mount in twrp so I cant try putting another rom on the phone unless I go and buy a micro sd adapter.
I am in the process of downloading a stock mdk rom to try and flash in odin, but is there anything I can try before I go through with this, or is it pretty much my only option.
after some more research I think I figured out what caused all this. I wiped the data partition with the old version of twrp which screwed it up pretty bad. Apparently the older versions of twrp were known to have this problem. I kept trying to restore, but trying to restore kept failing on the data partition. After about 25 attempts of trying to restore just the data partition I was able to get it to work finally, and then I restored the the others and got it to boot back into the rom. like an idiot I rebooted the phone back into recovery after it finished and had the same problem again. another couple hours wasted trying to restore the data partition and it worked again and this time i was able to get twrp to update and then went back to recovery and formated the data partition again and it seems to have fixed the problem. Now to figure out why hd rls 12 wont install.

Rom install Gone Wrong - HTC One M8

Fixed the problem. Updated TWRP, enabled SU and root, re-flashed the boot image and re-installed the ROM. Did a factory reset and now the phone boots. I have a HTC One m8. Have unlocked the bootloader and installed TWRP. Tried installing crDroidAndroid-7.1.2-20170801-m8-v3.6.1. Didn't work out so well. Said it failed - unable to mount system. Then it rebooted and started to load but crashed at the CR Droid splash screen. Tried factory reset, various wipes. Don't know what to do next. Anyone have any ideas? Also, it won't turn off. just reboots.

[SOLVED] TWRP suddenly not recognizing my device as H932; stuck in recovery

Hey all, so I decided to go from stock rooted to a custom rom, and see the progress since I last tried it and I encountered the following problem:
I formatted data and factory reset, and then I installed the custom rom, followed by the GAPPS.
Twrp rebooted every time I tried installing Gapps, so I was confused.
The following error occurred when before Aroma started:
"E:Legacy environment property did not initialize successfully. Properties may not be detected"
The next thing I did was I rebooted recovery, no cigar. I tried reinstalling the recovery, no cigar.
I tried formatting data again, and got the error that /data can't be mounted now. This started to worry me lol.
So I tried repairing it and then rebooting, and I tried updating to a newer TWRP but even there, the twrp version won't update. Its still the same number.
I'm too afraid to reboot and see if the rom boots or not, but when trying to flash even a stock rom ZIP it tells me the following:
"This package is for "Joan,h932" devices; this is a ""."
so twrp doesn't know what phone I have?
I am trying right now to restore my TWRP backup but it doesn't want to restore the data, so I'm trying without.
If you can help I would appreciate it very much!!
Here are the screenshots https://imgur.com/a/SLCPdIQ
EDIT: I finally figured it out. Hitting the reboot menu did nothing, because it was for some reason stuck and just rebooted into the same recovery version with the glitch.
I had to do a hard reset, and the finger dance again, and now everything is fixed.

Categories

Resources