Develop Bugs

Stuck in Boot Loop

I'm currently stuck in a boot loop, with no way to access my rom or recovery. I can only access bootloader. The boot loop began happening soon (around 2hrs) after flashing MIUI; The rom was running, and out of nowhere it just began cycling. Any ideas on how I can get out of this boot loop?
Edit: I'm no longer in a boot loop after installing a different full system PC36IMG.zip. Instead after the initial splash screen my evo goes black and vibrates 5 times, then my green LED starts flashing. It stays this way until I remove the battery.
So far I have tried:
Flashing RA's recovery image using fastboot. (The flash was successful)
Using RA's recovery PC36IMG.zip. (The installation was successful)
Using an RUU file renamed to PC36IMG.zip (The installation was successful)
Using a Sprint Lover's file renamed to PC36IMG.zip (The installation was successful)
For all of these the process of installing and flashing went fine. Yet when I would turn on my phone it would just go right back into the boot loop.
*I've been editing this post as I've tried new things, so you don't need to read through the thread to help me.
Anyways I'm at my wits end here, pretty worried, and phoneless, so any help would be amazing.

Have you tried ADB from bootlaoder or fastboot. May be able to get recovery that way.

I'm trying to do a bit of research, but am a little confused on what adb is. It's part of the android sdk? I can't seem to find it, or know how to launch it. Is there a thread somewhere that covers it? I'll keep doing my research, thanks for the tip.

Its a command terminal but if you are not familiar with it you probably wont get it right away! I am just starting to learn this myself. VERY VERY useful tool though! Here a link.......
http://forum.xda-developers.com/showthread.php?t=502010

I really appreciate you trying to help out. I'm trying to figure it out right now, but how do i get to the terminal? Theres a couple of different guides I see, but none seem to be while in bootloader. The thread you showed me seems to be mostly commands. Sorry for the hassle, I really appreciate you helping me. I wouldn't be quite so pestering if I wasn't without a phone, haha.
ahhh, also, if adb is an exe that opens up in cmd.exe (which i'm starting to think), its not included in my sdk.
edit 2: haha, ok i just found out i have to install adb through sdk, from a little txt file. sorry. i'll get back to ya soon!

thanamesjames said:
I really appreciate you trying to help out. I'm trying to figure it out right now, but how do i get to the terminal? Theres a couple of different guides I see, but none seem to be while in bootloader. The thread you showed me seems to be mostly commands. Sorry for the hassle, I really appreciate you helping me. I wouldn't be quite so pestering if I wasn't without a phone, haha.
ahhh, also, if adb is an exe that opens up in cmd.exe (which i'm starting to think), its not included in my sdk.
edit 2: haha, ok i just found out i have to install adb through sdk, from a little txt file. sorry. i'll get back to ya soon!
Click to expand...
Click to collapse
Jeez sounds like you have a better grasp on this than me already! LMAO

haha, well i'm not too sure. Have you gotten you're evo to be found? Right now while using adb, I'm just told "device not found." All my drivers should be properly installed because I had to install them when I used unrevoked. So I choose fastboot on my evo, and then it shows up on my computer as "android 1.0" under devices and printers... but adb doesn't find it.

I was told to get rid of my drivers and re install the recommended ones before starting. It recognized mine right away. YouTube also has nice how to videos on ADB.

Is there any way you can point me to the recommended drivers? I think that second link you gave me is the same as the first also.
Edit: Every single guide I see on the internet about adb, says use debug mode within the actual rom. However I'm obviously not in a rom, i'm in bootloader, and for the life of me can't get adb to find my phone.
Edit2: Ok, so maybe I can only use fastboot. Right now when trying fastboot it just says "waiting for device," even if it didn't say that, what would i need to do to get on the road to recovery?

So I'm starting to get scared. At first I figured this was something I could fix... and now I'm not positive it is. I've used fastboot from terminal, trying to flash recovery and it says "FAILED (remote: not allowed)" I'm starting to get desperate, does anyone have any ideas?

I'm sorry to bump this, but I'm really struggling here... because I'm phoneless and all , I worked at this for 5 hours last night from 9-2, and now I'm at it again... and very worried. I've read that theres almost no way to completely brick your phone, but I'm starting to feel like I did. It seems like no matter what I flash it just keeps boot cycling. Thanks for the help.

go to the bootloader and ruu it

I have... I took the ruu file and renamed it PC36IMG.zip, went into bootloader and it went through all the steps with "OK"s, rebooted, and went right back into the boot loop.
Specifically I used "RUU_SuperSonic_S_Sprint_WWE_3.70.651.1_Radio_2.15.00.11.19_NV_1.90_release_161482_signed.zip" from here,
http://goo-inside.me/evo/stock/RUU/
Is there a specific number version of RUU I should try? I just tried the most recent.

You have to use the ruu that matches your radios/software etc. How did this boot loop start? Give us all your phone info, rom, hboot version, radios etc.
Sent from my iphone slayer 4G

I flashed a CM7 nightly, from CM, about 2 weeks ago. Yesterday, still using the same nightly (build 1 or something) my phone seemingly out of nowhere rebooted - I wasn't even using it at the time. When it went back into CM7 it acted as if I had never linked a google account to my phone. The first thing that came up was the android google apps screen. Anyways, I decided I wouldn't stick with CM7 until at least an RC was out, so I wiped data, cache, and davlik and flashed MIUI. I used it for about two hours, didn't do anything out of the ordinary, and once again seemingly out of nowhere it rebooted... except when it did it went into a cycle and never reached MIUI, and wouldn't go into recovery, I could only access bootloader.
Anyways, I'll tell you what bootloader says my phone versions are, but I do believe the info all changed this morning when I flashed the ruu file.
SUPERSONIC EVT2-3 SHIP S-off
HBOOT-2.10.0001
MICROP-041f
TOUCH PANEL-ATMELC03_16ac
RADIO-2.15.00.11.19
Oct 15 2010, 12:07:00

Check your pm
Sent from my iphone slayer 4G

Are there any other thoughts on how to get on my feet?
In addition to booting an RUU file as PCIMG36 I've also tried a Sprint Lover's image as PCIMG36. Even though both installed properly, my phone still staid in the boot cycle afterwards for both.
I've been suggested, and have seen other users suggest on other threads, to try adb commands, but I don't know if i can access adb while the phone is in bootloader. I have however accessed fastboot, are there any commands that might help me? If not, can I use adb while in bootloader? Thanks.

Well I tried a new PC36IMG.zip file and I'm no longer stuck in a boot loop... instead as soon as the HTC EVO 4G splash disappears my phone goes black and vibrates 5 times, and my green LED flashes.
Good? Bad?

This would be the 300th something thread I've read on this subject and this is exactly were I'm at with my EVO minus the last post... I was using warms2p2 with the hdmi kernal everything working fine then I went to change my notification ringtone and bam went into boot loop and never came out. SOOO! it would be nice to save this unit... any help forum members would be great I've tried every RUU out there from fastboot from sd card nothing.
Very intesting that this thread ended this way... please share if you think you got this whooped. Thank you in advanced.

Love the revival of old threads...but did you try changing the kernel?
http://dl.dropbox.com/u/19699565/3.70 RUU Zip.zip 3.70 RUU, just rename to PC36IMG and flash in the bootloader if you want to run the RUU.

[Q] Recovering from unusual boot loop

Let me preface this by saying yes I know there are dozens if not more threads on boot loop problems. I have recovered from boot loops before. This is very different.
I rooted my incredible with unrevokedForever and had cyanogen 6 on it. Everything was fine until yesterday I woke up to it in a boot loop, but not the cyanogen boot animation, the white HTC Incredible screen. I can only get to HBOOT, once I try to enter recovery, use an update.zip, or anything after the HBOOT page it goes into its loop. Should I pursue the RUU and find a windows computer or will that not help me?
I think I may have to bite the bullet and buy a new phone. As obviously they will not replace an S-OFF phone. Any help is appreciated.

jenic said:
Let me preface this by saying yes I know there are dozens if not more threads on boot loop problems. I have recovered from boot loops before. This is very different.
I rooted my incredible with unrevokedForever and had cyanogen 6 on it. Everything was fine until yesterday I woke up to it in a boot loop, but not the cyanogen boot animation, the white HTC Incredible screen. I can only get to HBOOT, once I try to enter recovery, use an update.zip, or anything after the HBOOT page it goes into its loop. Should I pursue the RUU and find a windows computer or will that not help me?
I think I may have to bite the bullet and buy a new phone. As obviously they will not replace an S-OFF phone. Any help is appreciated.
Click to expand...
Click to collapse
As long as you can still get into HBOOT and Recovery, you should be okay. Your best bet is to get the RUU and go back to stock/s-on, then re-root/s-off (if you want). I had to do this once, and it's pretty straight forward. Just do a search for Bezerker7's Ultimate Get Back to Stock Thread. It has all the info you'll need on how to do it.

RMarkwald said:
As long as you can still get into HBOOT and Recovery, you should be okay. Your best bet is to get the RUU and go back to stock/s-on, then re-root/s-off (if you want). I had to do this once, and it's pretty straight forward. Just do a search for Bezerker7's Ultimate Get Back to Stock Thread. It has all the info you'll need on how to do it.
Click to expand...
Click to collapse
The problem is I can only get into HBOOT, not recovery. It would be a fairly simple matter if I had access to recovery features. Would RUU work without access to recovery?

jenic said:
The problem is I can only get into HBOOT, not recovery. It would be a fairly simple matter if I had access to recovery features. Would RUU work without access to recovery?
Click to expand...
Click to collapse
Looks like you'd need recovery to flash back to s-on first. First you could try flashing a recovery image using fastboot, go here for that information. You'd also need to find a 2.5.x.x recovery image, go here for the 2.5.1.2 image. Don't worry about renaming it, you won't have to do that here like the page says to.
Then, you could go here for instructions on using the RUU to flash back to stock.

RMarkwald said:
Looks like you'd need recovery to flash back to s-on first. First you could try flashing a recovery image using fastboot, go here for that information. You'd also need to find a 2.5.x.x recovery image, go here for the 2.5.1.2 image. Don't worry about renaming it, you won't have to do that here like the page says to.
Then, you could go here for instructions on using the RUU to flash back to stock.
Click to expand...
Click to collapse
Your concise post is most appreciated. I will do as you instruct and post results back here when finished.

RMarkwald said:
Looks like you'd need recovery to flash back to s-on first. First you could try flashing a recovery image using fastboot, go here for that information. You'd also need to find a 2.5.x.x recovery image, go here for the 2.5.1.2 image. Don't worry about renaming it, you won't have to do that here like the page says to.
Then, you could go here for instructions on using the RUU to flash back to stock.
Click to expand...
Click to collapse
Hit an unfortunate snag right away. fastboot (nor adb) is detecting the device. Screen is showing XC SHIP S-OFF as it should, it is in FASTBOOT USB mode and my computer detects the USB itself just fine.
dmesg output:
[346853.772041] usb 2-6: new high speed USB device using ehci_hcd and address 17
[346853.922917] usb 2-6: configuration #1 chosen from 1 choice
Click to expand...
Click to collapse
Thank you though that was a great suggestion! (Was very hopeful for a second there

I've never used the fastboot command before, but I seem to recall that sometimes my PC's don't report connection from ADB, but I haven't checked recently... Hmmm...
Just checked and it does report a device using ADB. Did you try typing the fastboot command to flash the recovery image file: fastboot flash recovery /path/to/<recovery.img file> anyways to see what happens? I am assuming if it isn't detecting the connection, it may fail...
EDIT: Did you pull the battery out, put it back in and try to get into recovery again? If you, try doing a user/factory reset + dalvik cache before trying to install a ROM from your SD card.

This may or may not help, but I had a similar issue of not having the phone recognized by fastboot while playing with a friends EVO Shift. I was able to use the program described in this thread to uninstall all HTC drivers. Then, when the phone was recognized and new drivers installed automatically, fastboot worked as expected.
http://forum.xda-developers.com/showthread.php?t=532719

RMarkwald said:
I've never used the fastboot command before, but I seem to recall that sometimes my PC's don't report connection from ADB, but I haven't checked recently... Hmmm...
Just checked and it does report a device using ADB. Did you try typing the fastboot command to flash the recovery image file: fastboot flash recovery /path/to/<recovery.img file> anyways to see what happens? I am assuming if it isn't detecting the connection, it may fail...
Click to expand...
Click to collapse
My ADB daemon would always recognize it in the past, when the phone was working. Yes I tried the command anyway, even though fastboot devices did not return anything. It hung there waiting for the device to be connected.
RMarkwald said:
EDIT: Did you pull the battery out, put it back in and try to get into recovery again? If you, try doing a user/factory reset + dalvik cache before trying to install a ROM from your SD card.
Click to expand...
Click to collapse
Yes, I pulled battery out multiple times, and when installing the rom I factory reset, cleared dalvik and normal cache through Clockwork. Cyanogen was working fine for weeks, this is a freak concurrence that happened without warning. I woke up to find it this way, or rather, it woke me up with its constant rebooting. lol.
cf9182 said:
This may or may not help, but I had a similar issue of not having the phone recognized by fastboot while playing with a friends EVO Shift. I was able to use the program described in this thread to uninstall all HTC drivers. Then, when the phone was recognized and new drivers installed automatically, fastboot worked as expected.
http://forum.xda-developers.com/showthread.php?t=532719
Click to expand...
Click to collapse
I appreciate the help however I am using Linux, and that seems to be a windows issue. I have not had issue detecting the device until this problem arouse. The sentiment is of course appreciated though, please do not feel that I am ungrateful! You have both been very supportive. I think I have just about resigned to dump money on a new phone. This time I will leave it stock for awhile and see if this occurs a third time.

jenic said:
My ADB daemon would always recognize it in the past, when the phone was working. Yes I tried the command anyway, even though fastboot devices did not return anything. It hung there waiting for the device to be connected.
Yes, I pulled battery out multiple times, and when installing the rom I factory reset, cleared dalvik and normal cache through Clockwork. Cyanogen was working fine for weeks, this is a freak concurrence that happened without warning. I woke up to find it this way, or rather, it woke me up with its constant rebooting. lol.
I appreciate the help however I am using Linux, and that seems to be a windows issue. I have not had issue detecting the device until this problem arouse. The sentiment is of course appreciated though, please do not feel that I am ungrateful! You have both been very supportive. I think I have just about resigned to dump money on a new phone. This time I will leave it stock for awhile and see if this occurs a third time.
Click to expand...
Click to collapse
This happened to me and many other people. It has nothing to do with the fact that you rooted as my replacement from verizon did the same thing even before I rooted. Finally on my 2nd replacement (my 3rd DINC), it has stopped happening.
You're going to have to take it to the store. The guy who looked at my phone looked right at the HBOOT (where it says s-OFF) and then said "we're going to have to send you another one."
So you may get lucky. Your other option (if you're nervous about the store seeing the s-OFF) is just to call Verizon and ask them to send you a replacement. My experience has been that the folks in the Verizon store have no idea what the f they're doing, and you'll probably be just fine taking it in.

jaba14 said:
This happened to me and many other people. It has nothing to do with the fact that you rooted as my replacement from verizon did the same thing even before I rooted. Finally on my 2nd replacement (my 3rd DINC), it has stopped happening.
You're going to have to take it to the store. The guy who looked at my phone looked right at the HBOOT (where it says s-OFF) and then said "we're going to have to send you another one."
So you may get lucky. Your other option (if you're nervous about the store seeing the s-OFF) is just to call Verizon and ask them to send you a replacement. My experience has been that the folks in the Verizon store have no idea what the f they're doing, and you'll probably be just fine taking it in.
Click to expand...
Click to collapse
That was definitely a laugh. Thank you I will see if I can get it replaced! I've been kinda just ignoring the fact that I do not have a phone all this time... Thankfully I had setup the phone to forward calls to google voice. It has been a lifesaver.

[Q] What do I do if I can't get into Recovery?

I was flashing a TrickDroid ROM just now, having had Jellytime 17.1 previously. I did a full backup and full wipe before attempting to flash the TrickDroid ROM.
I got distracted during the process, and when I came back to my phone, it was showing the Jellytime boot animation, but never gets to the UI.
OK, so I figure I can hold the power and volume down button and get into recovery. Nope. When I try to select Recovery from the boot loader, it doesn't do anything at all.
Am I hosed up for good here?

When you get into hboot does it do the normal check? After that it should let you choose.
If that doesn't work try pulling the battery for a few minutes and try again.
If you have adb you can type:
adb reboot recovery
Sent from a dream.

Teichopsia said:
When you get into hboot does it do the normal check? After that it should let you choose.
If that doesn't work try pulling the battery for a few minutes and try again.
If you have adb you can type:
adb reboot recovery
Sent from a dream.
Click to expand...
Click to collapse
It does do the check. When I select "recovery" or "factory reset", it just comes back to the bootloader menu without doing anything.
Mike

TheImpalaKid said:
It does do the check. When I select "recovery" or "factory reset", it just comes back to the bootloader menu without doing anything.
Mike
Click to expand...
Click to collapse
Perhaps you need to re-flash a recovery but let's wait for someone to double check and confirm.
But then you get the same issue with factory reset (which you shouldn't do).
Sent from a dream.

If it goes into the bootanimation then you can use ADB. Connect the phone to pc and let it go into the bootloop and then use "adb reboot recovery" from the command line on your pc.
If it stil doesn't work then you'll need to reflash your recovery. Download a recovery image like ClockWorkMod, go into bootloader while connected to pc. It should show "Fastboot USB" on the bootloader screen. Then use ""fastboot flash recovery [name of the image.img]" to flash a new recovery.
Try going into recovery again and see if it helps.

Teichopsia said:
Perhaps you need to re-flash a recovery but let's wait for someone to double check and confirm.
But then you get the same issue with factory reset (which you shouldn't do).
Sent from a dream.
Click to expand...
Click to collapse
I tried removing the battery for about 10 minutes, and then tried getting into recovery. The same thing happens when I select "recovery".
I let it sit for about 40 minutes with the JellyTime boot animation running, hoping it would complete, but it never did.
I guess AT&T can reflash it but then I'll have to root it again. I guess that's better than losing the whole thing.
Mike

Its strange though.. flashing a ROM doesn't tamper the recovery partition so it shouldn't have happened.
---------- Post added at 11:26 PM ---------- Previous post was at 11:25 PM ----------
TheImpalaKid said:
I tried removing the battery for about 10 minutes, and then tried getting into recovery. The same thing happens when I select "recovery".
I let it sit for about 40 minutes with the JellyTime boot animation running, hoping it would complete, but it never did.
I guess AT&T can reflash it but then I'll have to root it again. I guess that's better than losing the whole thing.
Mike
Click to expand...
Click to collapse
You won't need to give it to AT&T.. just run an RUU and root it again if it comes to it.

Just do what the previous member suggested. You both posted at the same time so you might not have seen it.
Sent from a dream.

Teichopsia said:
Just do what the previous member suggested. You both posted at the same time so you might not have seen it.
Sent from a dream.
Click to expand...
Click to collapse
Thanks, I hadn't seen that other reply.
I have been flashing ROMs for about a year, and had never run across this problem. I've never had anything happen that messed up recovery until now.
I will try this when I get home from work today. Thanks to both of you for the help and suggestions.
Mike

TheImpalaKid said:
Thanks, I hadn't seen that other reply.
I have been flashing ROMs for about a year, and had never run across this problem. I've never had anything happen that messed up recovery until now.
I will try this when I get home from work today. Thanks to both of you for the help and suggestions.
Mike
Click to expand...
Click to collapse
Ofcourse.. and It shouldn't have happened. ROM's don't mess with the recovery. Even if anything happened during flashing the ROM the recovery partition should not be affected. This is a strange situation indeed.. should be brought to attention of the 4ext recovery developer...

if4ct0r said:
Ofcourse.. and It shouldn't have happened. ROM's don't mess with the recovery. Even if anything happened during flashing the ROM the recovery partition should not be affected. This is a strange situation indeed.. should be brought to attention of the 4ext recovery developer...
Click to expand...
Click to collapse
I thought it was pretty weird, too. I've flashed ROMs a ton of times with no problems.
I am using ClockworkModRecovery.
Mike

TheImpalaKid said:
I thought it was pretty weird, too. I've flashed ROMs a ton of times with no problems.
I am using ClockworkModRecovery.
Mike
Click to expand...
Click to collapse
Oh.. my bad. I thought I read that you use 4EXT.. :silly:
In anycase.. All is well and solvable if you can reach the bootanimation Just use ADB.

if4ct0r said:
Oh.. my bad. I thought I read that you use 4EXT.. :silly:
In anycase.. All is well and solvable if you can reach the bootanimation Just use ADB.
Click to expand...
Click to collapse
I guess... I can't get my laptop to recognize the phone or load any drivers for it. So when I try to run adb, I get no devices.
I have a teenage son who I may sic on this problem.
Mike

You have HTC Sync installed? You have ADB as well? Make sure you have it installed. It installs connectivity drivers for your phone.
If you're indeed getting into bootanimation your phone should be recognized by ADB. After installing HTC Sync, try running "adb devices" if it shows no devices try running "adb kill-server" and then "adb devices" again. If all drivers are correctly installed it should recognize your phone.

Tips: You can get adb by running the advanced ace hack kit once

Update
My two sons were able to finally get the phone reset to factory spec sometime last night. :victory: So I'll have to re-root the phone and then I can restore my ROM from the backups.
One weird thing... the speaker/microphone doesn't work now. This is no big deal as I rarely receive or make calls.
I'm probably not your typical Android user in that I'm 55, and I love to try out the different ROMs that are available. Favorites are BlackIce, Trickdroid, and JellyTime.
Most of my peers have some sort of iPhone and really don't care anything about behind-the-scenes or jailbreaking, etc.
Thanks to everyone who's offered help and information.
Mike
TheImpalaKid

[Q] bootloop no recovery

Wife's Verizon Galaxy Nexus 4.2.2
Bone stock, completely un-tampered with, stuck in bootloop. If I try to access recovery I just get the Android dude with the red exclamation point sign, and eventually it reboots and back to the bootloop problem.
I need to save the data on the phone (pictures/videos). Flashing factory image erases all data, but could a person use Odin to flash the Verizon 4.2.2 OTA update? Is it possible or will Odin erase everything anyway?

That is stock recovery. Odin flash also wipes user data. Is the bootloader unlocked?
a maguro wrote this.

Oh, sorry for my ignorance, and the bootloader is locked.

You may try this awesome method: http://forum.xda-developers.com/showthread.php?t=2016628
The thread talks about GSM Nexus but may also work on your device (I think they have same CPU and bootloader). No warranties.

My Gnexi said:
You may try this awesome method: http://forum.xda-developers.com/showthread.php?t=2016628
The thread talks about GSM Nexus but may also work on your device (I think they have same CPU and bootloader). No warranties.
Click to expand...
Click to collapse
Exactly, do it at your own risk.
a manta wrote this.

Does seems like the most promising option at this point. Now if I can just find the OMAPFlash, the link is no longer good.

I think I have a copy on my laptop, will check later.
Edit: No need for my copy. The original post from gsmhosting.com by legija has a link that led me to http://d-h.st/XNv it's on dev-host and by efrant so it must be good

My Gnexi said:
I think I have a copy on my laptop, will check later.
Edit: No need for my copy. The original post from gsmhosting.com by legija has a link that led me to http://d-h.st/XNv it's on dev-host and by efrant so it must be good
Click to expand...
Click to collapse
Yes, its the same file.
a manta wrote this.

woohoo, it worked, I now have an unlocked bootloader. If I am correct I should now be able to flash a no-wipe recovery onto her device? I've been searching like crazy, but it seems like every other thread I find contradicts the previous so I'm still pretty lost.

hillbillymo said:
woohoo, it worked, I now have an unlocked bootloader. If I am correct I should now be able to flash a no-wipe recovery onto her device? I've been searching like crazy, but it seems like every other thread I find contradicts the previous so I'm still pretty lost.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1812959
You will be able to flash a custom recovery or even only boot a custom recovery through fastboot ('fastboot flash recovery recovery.img' for the first, 'fastboot boot recovery.img' for the latter). Read that first post on the thread I linked you to. It will teach you what is what and how to interact with the tools.

Amazing, I managed to load CWM, however it appears to me that all I will really be able to do from it is a factory reset, is that correct? Also do the fastboot flashes take even if USB Debugging is turned off?

hillbillymo said:
Amazing, I managed to load CWM, however it appears to me that all I will really be able to do from it is a factory reset, is that correct? Also do the fastboot flashes take even if USB Debugging is turned off?
Click to expand...
Click to collapse
USB debugging only has an effect when the OS is booted
Sent from my Galaxy Nexus

hillbillymo said:
Amazing, I managed to load CWM, however it appears to me that all I will really be able to do from it is a factory reset, is that correct? Also do the fastboot flashes take even if USB Debugging is turned off?
Click to expand...
Click to collapse
While on CWM, ADB/USB debugging is active.
Use 'adb pull /sdcard/' to pull all contents under /sdcard/.
a manta wrote this.

Success...kind of. The "adb pull /sdcard/" command did not work, for some reason it kept freezing on the first file it found. I then navigated to the Camera folder and pulled all the .jpg files, which is what I was primarily after. ADB did not like pulling .mp4 files so I just called it good there.
After that I tried using fastboot to flash boot, system, recovery, and even radio images, but phone was still in bootloop. I then ran the flash all batch file that came with the factory image I downloaded, everything went fine, but still no boot. Also tried Odin to flash factory image, but every time I clicked on "Start" I would get a "program stopped responding" error message(no matter what version of Odin I used).
At this point I believe the phone has a major problem that cannot be repaired with software, time to lock the bootloader and send it in I suppose. If anybody has any other ideas let me know, but I'm not very hopeful.
Thank you to everyone that contributed to my data recovery, this really is an awesome place, guess I'll stick around.

Stuck in download/recovery mode

It's been years since I used to root my OG HTC Evo, and I thought I would give it a go with my HTC One M9. I have TWRP flashed and S-On. I was hasty in flashing my SU.zip without a backup now I'm stuck, and I cannot remember what you need to do in this situation.
I can get my phone into download mode and fastboot is seeing the device, but I'm not sure if I need to flash a RUU and start all over or what. Any help would be appreciated.

toolongtospell said:
It's been years since I used to root my OG HTC Evo, and I thought I would give it a go with my HTC One M9. I have TWRP flashed and S-On. I was hasty in flashing my SU.zip without a backup now I'm stuck, and I cannot remember what you need to do in this situation.
I can get my phone into download mode and fastboot is seeing the device, but I'm not sure if I need to flash a RUU and start all over or what. Any help would be appreciated.
Click to expand...
Click to collapse
Details are always appreciated, if you've got them. So for instance:
- what is your current firmware version?
- what version of TWRP are you using?
- what SuperSU version did you attempt to flash?
- which ROM were you using?
- what is your MID?
- what is your CID?
If you can access TWRP, you can almost assuredly bring your phone to a usable state without a RUU. You may end up losing data, but the phone will work. If you can provide some more details (above), we'd be in a better position to offer meaningful advice.

It's been awhile... so I know about half of those things, so here's download mode info
***UNLOCKED***
htc_himawhl PVT S-ON
LK-1.0.0.0000
RADIO [email protected]
OPENDSP-15.5.1.00522.8994_1026
OS-3.41.651.4
Feb 3 2016, 13:49:48(695981)

Forgot to add
BETA-SuperSU-v2.75
TWRP-3.0.2.0-hima
I was trying to root and flashed the SuperSU and then I got stuck where I'm at now. it over-wrote my rom.

Okay, so you've got the himawhl, which is Sprint, right?
You're running the latest firmware (OS version 3.41.651.4), and you've got the matching TWRP version.
Have you tried flashing the stable version of SuperSU? I wonder if you've simply run afoul of some bug in the beta version.

Yes, I'm on Sprint. The problem with running the non-Beta SuperSU is that my stock rom is gone, thus why I'm stuck in a bootloop.

Okay so I sideloaded Android Revolution 20 through ADB but it never boots up, just sits on a white HTC screen with the security warning in red.
**edit** It finally progressed to the HTC One screen, crossing my fingers that it boots.
**edit 2** Welp, it would never boot to a usable rom, it would hang on a white HTC screen and I could hear notifications go off and I could use the volume controls and the power menu. I'll be wiping the phone again and trying a different ROM.

If I put a RUU file and name it 0PJAIMG.zip and sideload it via adb will it load the stock rom?

I'm not familiar with the SD card method, but you've got the executable RUU available to you (Windows required). That'll completely restore your phone to stock.

computerslayer said:
I'm not familiar with the SD card method, but you've got the executable RUU available to you (Windows required). That'll completely restore your phone to stock.
Click to expand...
Click to collapse
I started this whole process yesterday on my work computer (Windows 7) which it was seeing my phone via fastboot and adb but when I tried the RUU.exe at work it kept seeing that my phone was below 30% even though it wasn't.
Now that I'm home and on my computer (Windows 10) I've tried the RUU.exe but it's not seeing my phone. I guess I don't have the right drivers. Under Other devices it's showing as 0PJAIMG, which I think it should be showing as Android device.

toolongtospell said:
I started this whole process yesterday on my work computer (Windows 7) which it was seeing my phone via fastboot and adb but when I tried the RUU.exe at work it kept seeing that my phone was below 30% even though it wasn't.
Now that I'm home and on my computer (Windows 10) I've tried the RUU.exe but it's not seeing my phone. I guess I don't have the right drivers. Under Other devices it's showing as 0PJAIMG, which I think it should be showing as Android device.
Click to expand...
Click to collapse
A couple of things. I have terrible luck getting Windows to recognise my phone under normal circumstances (ie, Android booted normally). I recommend installing HTC's sync manager, which should cover any driver issues.
When you've done that, run the RUU with you phone in download mode when you connect it. That works for me every time.
---------- Post added at 02:49 PM ---------- Previous post was at 02:48 PM ----------
Here's the link to HTC's download page: http://htc.com/hsm/

computerslayer said:
A couple of things. I have terrible luck getting Windows to recognise my phone under normal circumstances (ie, Android booted normally). I recommend installing HTC's sync manager, which should cover any driver issues.
When you've done that, run the RUU with you phone in download mode when you connect it. That works for me every time.
---------- Post added at 02:49 PM ---------- Previous post was at 02:48 PM ----------
Here's the link to HTC's download page: http://htc.com/hsm/
Click to expand...
Click to collapse
That HTC Sync Manager was exactly what I needed to get my phone recognized by my computer. Unfortunately the RUU.exe is for some reason seeing my phone below 30% even though it's been charging on AC power for hours......

So I just figured out that the reason the RUU.exe was giving me the issue with the battery percentage was I was trying to run it in bootloader instead of download.
The RUU.exe kept giving me error 155 over and over like my bootloader was not locked, I kept running it over and over and it finally completed. I have a functioning phone. yey!

Woohoo! That's a great feeling - congratulations.