I recently came across an issue where TWRP recovery would hang and then cause the bootloader to be stuck trying to boot into a broken recovery. The only way I could fix it was to reflash the recovery.img with fastboot, boot into the freshly flashed android recovery through VOL- method, and then power-off device from within recovery menus.
No other method I tried broke the bootloader-looping-while-trying-to-unsuccessfully-initialize-recovery cycle.
Only downside is that I am really not sure actions cause(d) TWRP to hang on init (the "curtain" logo never began to raise to the top of the screen) the three times I have caused it.
Just a little helpful info for people that experience(d) this.
disynthetic said:
I recently came across an issue where TWRP recovery would hang and then cause the bootloader to be stuck trying to boot into a broken recovery. The only way I could fix it was to reflash the recovery.img with fastboot, boot into the freshly flashed android recovery through VOL- method, and then power-off device from within recovery menus.
No other method I tried broke the bootloader-looping-while-trying-to-unsuccessfully-initialize-recovery cycle.
Only downside is that I am really not sure actions cause(d) TWRP to hang on init (the "curtain" logo never began to raise to the top of the screen) the three times I have caused it.
Just a little helpful info for people that experience(d) this.
Click to expand...
Click to collapse
It could be a bad memory sector.
Has this happened with any other recovery?
Sent from my MB860 using xda premium
d3athsd00r said:
Has this happened with any other recovery?
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
Not in my extensive cowboy-flashing (aka potentially jacking things up). I have used multiple versions of Clockwork, TWRP, and Clockwork touch.
It was mostly a puzzle about how to proceed and I wanted to share it with others. I say that because I see a lot of "is my device bricked?!?"-type posts. It seems to me that the only way to actually brick most devices is during direct firmware flashes using RSD (in the case of the Atrix) or some other equivalent like you see with NVidia Tegra interfaces.
The first time I experienced it I did have an "oh ****" moment or two, mostly because of having to reboot without having a functioning recovery partition.
In short I would say that touch-type recoveries carry an additional level of risk over hardware-key recoveries like CWM. The moral of the story for newbies is to RTFM and follow directions, especially when flashing a .sbf on the Atrix through RSD.
Related
I just bricked my device I guess.
First off flashed:
http://forum.xda-developers.com/showthread.php?t=1162302
TouchWiz UX for 10.1
- Cleared all (factory reset)
Which was working nicely, but then I needed some extra kernel modules, so I installed:
http://forum.xda-developers.com/showthread.php?t=1175299
3.1 Galaxy Tab Wifi OC1.6
- Cleared all (factory reset)
It booted at first, but then rebooted and eventually went to black screen. Now powering up won't work.
So yes it really won't come to life out of it's own.
-------------
My first step: Hang it to a PC
Well it recognized the tab, and was asking for the APX driver, which I found over here: http://forum.xda-developers.com/showpost.php?p=11901016&postcount=75
Which installed correctly, and is recognizing my device (for now).
Who can help me further (it is possible to backup and restore using nvflash)
-- Update 0x4 error...
NVFlash seems to be a dead end. You can't use it without sbk, which we don't have. Any more suggestions?
Use Odin to flash CWM recovery (if you haven't already), then reinstall a ROM using Clockwork Mod.
sassafras
Could be "sleep of death" there are other threads on here about it. There are various ideas about waking it up, but just letting the battery discharge and then charging it worked for my (unmodded) tab. Admittedly that is a little tricky when you can't power it on in the first place!
Sent from my GT-I9000 using XDA App
sassafras_ said:
Use Odin to flash CWM recovery (if you haven't already), then reinstall a ROM using Clockwork Mod.
sassafras
Click to expand...
Click to collapse
Been there, done that... I've flashed all through CWM recovery, always made a backup, but it doesn't go through the bootloader anymore, so I can't access the recovery, nor the download mode (for Odin flashing).
The only thing I can access at the moment is that stupid NVFlash, and since my device is I/O locked, I can't flash anything.
tmbk said:
Could be "sleep of death" there are other threads on here about it. There are various ideas about waking it up, but just letting the battery discharge and then charging it worked for my (unmodded) tab. Admittedly that is a little tricky when you can't power it on in the first place!
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
I will check on this. It's the only way to fully reset my device. Since it is I/O locked, it can't have harmed my bootloader or CWM recovery.
I made sure before flashing that the MD5 checksum was right (which it was). The only thing it flashed was a kernel. Well I will drain my battery and check if it is possible to boot it up after that. Else I buy a new one
Exact same thing happened to me.. ran poitee kernel over OTA update.. killed everything but nvflash + all black screen.
Cannot get it to flash w/ bootloader.. Have 2 days to RMA and I really don't want my data out there in the event this thing comes back up after the battery dies.
PS- My unit was bootloader unlocked and rooted.
OK heres the deal. I have done tons of searching and it looks like I SHOULD be able to get out of this, but I cant figure it out and I may have gone to far(by unrooting with 4.24 and bootloader 2.16).
So long story short, my launch day evo got lost about a month after I got it. Got a replacement from Sprint(or whoever their insurance is), my original Evo got found about a month or so after that. It has not been powered on since then(a year realistically) with no battery or SD card in it. I got bored and decided to power it up and update everything(because I cant do **** with my new Evo3d, yet since im on a Mac and have no access to a PC). Here are where things went bad.
Phone was rooted with the very original Toast method including S-off with the .76 Eng boot loader. I was running some form of CM6 on it when I lost it.
-Went to power it up and it boot looped at the white Evo4g screen.
-Went into bootloader and tried to get into recovery(had Amon RA 1.7 I think). No go.
-Flashed the new TWRP recovery and got into recovery just fine.
-Flashed the CM7.1.0-RC1
-reboot into a boot loop
-battery pull and a reboot and it loaded, but after about 30 seconds, reboot into a boot loop.
-Thought maybe TWRP didnt like the phone so I flashed Amon RA 2.3
-went into recovery just fine. Did complete wipes of everything using Calkulin Wipe all.zip
-re-flashed CM7.1.0 RC1
-boot loop
-flashed latest radios
-rebooted back into recovery
-reflashed cm7.1.0 rc1
-boot loop
During all of the reboots I would occasionally get the CM7 splash screen and then a reboot into boot loops. I THINK everything was flashing ok.
At this point I was frustrated and was thinking it was something I was doing that was jacked up so I decided to unroot and I flashed the newest RUU(which obviously removes root, S-off, .76 boot loader, etc...) so I did it. Figured I was just trying to get the phone running to sell anyway. Flashed was successful, chose to reboot and guess what. Boot loop. I pulled the battery out for about 10 minutes and it boots into the rom, runs for about 10-15 seconds in the rom and then reboots, back into the rom at least, but only about 10-15 seconds later, another reboot.
Every thread I read on these infinite boot loops were guys saying they couldnt even get into recovery or flash anything, which I had no problem doing(obviously cant really do that anymore with losing root and s-off). So I am stuck.
So current state of the phone is boot loader 2.16 S-on with 4.24.651.1 with all current radios, etc... flashed(as far as I can tell) from the RUU posted on Goo-inside.me.
Does anybody have any ideas for me to try? It seems like I am so close to getting it running because it will run for about 60 seconds but then reboot. I am guessing a hardware issue, but I honestly at this point have no clue.
Sounds like a hardware issue to me.
Sent from my PC36100 using XDA Premium App
Rem3Dy said:
Sounds like a hardware issue to me.
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
Thats what I am leaning towards, but why, if a hardware issue, will the phone run in the boot loader or recovery for basically forever without rebooting? It will also successfully(or did) flash everything I asked it to. I would think it would always reboot around that 60 second time frame if it was a hardware issue.
damn, too bad you ran RUU & lost s-off. now you couldn't do anything to test/troubleshoot even if you wanted to.
drdrewdown said:
damn, too bad you ran RUU & lost s-off. now you couldn't do anything to test/troubleshoot even if you wanted to.
Click to expand...
Click to collapse
I know. I probably should have posted up and waited, but I got impatient and thought that was a last ditch effort anyway since I tried everything else I knew to try.
rjacobs said:
but why, if a hardware issue, will the phone run in the boot loader or recovery for basically forever without rebooting? It will also successfully(or did) flash everything I asked it to. I would think it would always reboot around that 60 second time frame if it was a hardware issue.
Click to expand...
Click to collapse
because in the boot loader and recovery menu I'm sure the phone is not accessing radios, audio components, gps, and all manner of other hardware components that get activated once the phone tries to boot up for real.
It sounds like according to this thread: http://forum.xda-developers.com/showthread.php?t=805612&page=4
That my NV is FUBAR, but since I ran RUU and lost S-off, I cant do the fix. Oh well, I am sure eventually somebody will crack the boot loader and then I can fix it. Otherwise I have to send it off to HTC and I am sure pay them to fix it.
Just to clarify. The thread you linked to is for people who wrote nv items to their device.
What I'm afraid you are experiencing is the bootloop commonly complained about by those running CM roms.
I have yet to find a solution to the CM bootloop and all signs point to hardware failure.
Sent from my Evo using XDA Premium App
I used Cyanogen's downgrade and rooting process. Seems to work great. However,,,,
I've been searching the MT4G boards on booting into clockwork recovery. I'm still struggling with this. I've tried hboot (hold volume down + power), and that doesn't take me anywhere. I do get a couple of haptic bumps. I also tried volume up + return key + power key. It seems to occasionally get me to hboot, but I think I keep factory resetting, because I loose my google log-in and my root. Note, it does say S=Off on this screen, when I can get to it. The last time, I think I flashed the PD15IMG.zip file when I got into hboot, but honestly I'm not exactly sure. It reloaded several functions and took about 10 minutes, so I think it did.
I can re-root. Once I figure this out, I will go through the perma-root process, but I'm just getting started on my wife's old MyTouch 4G. I've rooted my G1, my Galaxy S2, my G2x, now I'm trying to root and try some customer ROMs for my wife's old and no longer used MT4G.
Can anyone help me out here? Maybe point me to some obvious threads or websites? Bottom line, I want to get into Recovery once I root my phone. I can't seem to get there, except through ROM Manager, which is not very dependable, particularly if I screw something up, or get into an infinite bootloop, like I did flashing AOKP ICS.
TU Homer said:
I used Cyanogen's downgrade and rooting process. Seems to work great. However,,,,
I've been searching the MT4G boards on booting into clockwork recovery. I'm still struggling with this. I've tried hboot (hold volume down + power), and that doesn't take me anywhere. I do get a couple of haptic bumps. I also tried volume up + return key + power key. It seems to occasionally get me to hboot, but I think I keep factory resetting, because I loose my google log-in and my root. Note, it does say S=Off on this screen, when I can get to it. The last time, I think I flashed the PD15IMG.zip file when I got into hboot, but honestly I'm not exactly sure. It reloaded several functions and took about 10 minutes, so I think it did.
I can re-root. Once I figure this out, I will go through the perma-root process, but I'm just getting started on my wife's old MyTouch 4G. I've rooted my G1, my Galaxy S2, my G2x, now I'm trying to root and try some customer ROMs for my wife's old and no longer used MT4G.
Can anyone help me out here? Maybe point me to some obvious threads or websites? Bottom line, I want to get into Recovery once I root my phone. I can't seem to get there, except through ROM Manager, which is not very dependable, particularly if I screw something up, or get into an infinite bootloop, like I did flashing AOKP ICS.
Click to expand...
Click to collapse
Settings>Power>Turn off fast boot.
Power off your phone.
Hold VOLUME DOWN BUTTON + POWER BUTTON.
Now select Recovery.
crazykas said:
Settings>Power>Turn off fast boot.
Power off your phone.
Hold VOLUME DOWN BUTTON + POWER BUTTON.
Now select Recovery.
Click to expand...
Click to collapse
How long? Until after the first bump?
I re-rooted. Can't seem to get there except through ROM Manager...
If you hold vol down and while booting, the phone should boot directly to bootloader. If it doesn't, there may be something wrong with one of the buttons. You have to have the button held down early, though.
You can also use terminal emulator:
su
reboot recovery
Or in adb:
adb reboot recovery
estallings15 said:
If you hold vol down and while booting, the phone should boot directly to bootloader. If it doesn't, there may be something wrong with one of the buttons. You have to have the button held down early, though.
You can also use terminal emulator:
su
reboot recovery
Or in adb:
adb reboot recovery
Click to expand...
Click to collapse
Much thanks for your help.
I cannot boot directly into recovery. It simply doesn't work. Occasionally, I can reset my phone and boot directly into hboot, though I'm not sure what the process actually is. I've only done it twice, and I was just dicking around and didn't track my button sequence. I'm trying to track this methodically, but I really think the process works intermittently, which masks the appropriate process.
I gain SU status in terminal, but I cannot reboot into recovery. I can get in via ADB, so that works.
Two processes into recovery: ROM Manager and ADB.
My issue is I've tried to flash an ICS ROM, in this case Ice Cold Sandwich AOKP 8.5 Final Edition. It gets caught in bootloop. Twice. Can't seem to load up properly.
Could my phone simply be dorked? Maybe I need to push a new recovery file?
Start with something easy like Cyanogenmod 7.2. Make sure you wipe cache, data, and system partitions.
Ok. I got everything working. I think your perception that my down button is non-functioning is the first culprit. Also, I'm not sure why I just boot-looped. I did this for both CM7.1 and for ICS. One other issue is I could not reboot into recovery from stock. I could, however, adb into recovery.
I first loaded CM7.1 plus GAPPs. This just bootlooped. I then got back into recovery via ADB and just flashed CM7.1. This worked. From here, I could use terminal to reboot into recovery. I could also use the CM reboot option right into recovery. At this stage, I flashed GAPPs and that was fine. I then upgraded to ICS and it is working great. My down button still doesn't work, so the only method of getting into recovery in an emergency is via ADB. I can, however, use the reboot option into Recovery from my working phone.
Strange. I might dig deeper to see if I can correct the lingering issues, but it seems to work well, and I finally figured out how to get around with this old phone that's been collecting dust for over a year. Not a bad daily driver. ICS seems very stable, compared with my G2X.
Again, thanks for your help.
Well, progress is always good. Congrats.
I'm not sure if you already did this or not but take the PD15IMG.zip out of the root directory on your SD card. After you remove/move it and get to hboot you should be able to go to recovery. From there you could recover a backup (which hopefully you made before trying to flash a new rom).
Sent from my Dark Unicorn Resurrected v4.1 using xda app-developers app
Good advice. I'll do that.
Sent from my HTC Glacier using xda app-developers app
Hello,
I have tried searching but haven't been able to find a similar issue for any android devices (amazing right?). My nexus 7 will not respond to any soft reboot. From power menus to terminal to factory reset (yes including from ROM recovery and the like). It will reboot from the 10second press, but as we know that is pretty ineffective considering the nexus 7 has that bug where you can't access recovery from boot loader. I have tried connecting to a PC to force recovery, Nada.
So now I am out of idea. Also, for the next 2 weeks I don't have a PC, only a gnex and nexus 7...
Any help appreciated.
update your bootloader and recovery, that bug has been fixed. what rom are you running, every single reboot/power off option works here.
I can't update it without being able to reboot. And I know its not a common issue.. hense why I ask for help... I am not reporting a issue, I am asking for ideas... thanks for the tremendous comprehension though
Oh, I forgot an important bit of info. It started happening after a kernel update (to fauxs latest) and now most programs that require root will be laggy or crash. And every 10sec reboot I do, apps "optimize" every time and every action, including downloaded files are missing since the last boot. (ie, I am always at the exact same point of the first boot after the kernel flash)
MatAuc12 said:
I can't update it without being able to reboot.
Click to expand...
Click to collapse
Are you saying that you can't get into fastboot by long-hold power and then hold vol down as soon as the device restarts?
Sent from my HTC Desire S
MatAuc12 said:
Oh, I forgot an important bit of info. It started happening after a kernel update (to fauxs latest) and now most programs that require root will be laggy or crash. And every 10sec reboot I do, apps "optimize" every time and every action, including downloaded files are missing since the last boot. (ie, I am always at the exact same point of the first boot after the kernel flash)
Click to expand...
Click to collapse
let the battery die and power itself off, then charge it. flash another kernel for sure.
simms22 said:
let the battery die and power itself off, then charge it. flash another kernel for sure.
Click to expand...
Click to collapse
I did let it die for cold boot and again, understanding my problem means since I can't initiate a reboot or get into recovery I cannot flash anything
BillGoss said:
Are you saying that you can't get into fastboot by long-hold power and then hold vol down as soon as the device restarts?
Sent from my HTC Desire S
Click to expand...
Click to collapse
Exactly. That is extremely strange behavior and complexes me even more than a soft brick even though the device works
MatAuc12 said:
Exactly. That is extremely strange behavior and complexes me even more than a soft brick even though the device works
Click to expand...
Click to collapse
boot pressing volume down while pressing the power button into the bootloader, flash a different kernel via fastboot. you can flash franco kernel in fastboot, since it is in boot.img form, or extract the stock boot.img from a stock rom and fastboot flash that. ive had similar behaviors with test kernels, faux forgot something in the kernel. then download and flash the newest bootloadee to fix your recovery from bootloader bug.
Try simms22 approach first.But if you can't get into fastboot and you can boot into the ROM- then you could try rewriting the boot.img. Get the boot.img/kernel you want and use the dd command to write it.
Warning: you can do serious damage with the dd command.
If you need some help with this, let me know. But I accept no responsibility if things go terribly wrong.
Sent from my Nexus 7
HI all,
I flashed CWM recovery to my Tegra Note 7 tablet and it's upside down. Is there a way to invert it right side up or is there an updated version that fixes that issue?
On a side note: I'm new to development, but I would like to learn how to pull the bootloader from the device and edit it so that the red warning is removed and the device can be sent back under warranty if needed. Does anyone know which partition the bootloader is located in?
Thanks for any help you can provide.
You are just holding the tablet the wrong way around
but no, no fix yet. its normal.
I would recommend not even touching the boot loader. Changing any code in the boot loader can lead to the device not even turning on. I don't think even apx mode can save you if the boot loader is messed up.
Sent from my TegraNote-P1640 using XDA Premium 4 mobile app
Heh, too late! Already installed the CWM recovery, but I can restore the original recovery quite easily though. The bigger question is whether I can keep root with a stock recovery. Then again I might as well as go ahead and find out in the morning.
EDIT: I flashed stock recovery back and root still works. Can also boot into stock recovery without a problem.