Stuck in download/recovery mode - One (M9) Q&A, Help & Troubleshooting

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.

Related

[Q] USB Bricked DI. Believe the cause is the misc partition. Help?

Hey all, I'm having a big issue with my Droid incredible. I've been trying to root it, ended up SERIOUSLY messing everything up [had problems rooting with unrevoked at first, CID error] then i temp rooted it and tried to install clockwork, which is where i think i usb bricked it. Which none of that matters, because this is my current problem.
If the phone is charging, it boots up and runs fine. It cant see any SD card or internal memory however. The second you unplug it, it reboots and gets stuck in a boot loop, never going past the HTC bootscreen.
Im aware that i should try and reflash the misc.img file? According to some of the desire forums. However when you plug it into the PC, it shows that usb device has malfunctioned, and adb cant see my DI. So i cant do much there. My phone's NOT rooted either.
Any help with this guys? I'd much appreciate it.
Richard
What does the output from this say?
Code:
"cat /dev/mtd/mtd0"
You try wiping it?
Sent from my Incredible using XDA App
Chevelle, I don't know how you want me to do that. I'm not rooted, so I dont have terminal emulator, and the USB doesnt work so I cant use ADB....
And yes, I've wiped it at least 10 times now, I've used a RUU to go back down to 2.1 [which corrupted my screen drivers, smh], then ruu back up to 2.2, with no change whatsoever. Im pretty sure that the misc partition does not reinstall with ruu's, if I've read correctly. So I don't have USB connection, I dont have root, and so my options are limited it seems. In my mind I'd have to flash something from hboot, considering thats the only thing that runs correctly anymore, that would reinstall misc. And also when hboot is up, my computer sees android bootloader. So its not hardware, I guarantee that much.
Okay guys, so its safe to say that im going to HAVE to somehow flash a mtd0.img file onto my incredible to get it back working, correct? Now I just need help with this, how to go about it without root and without adb, through hboot. Any suggestions? My CID is VZW__001 if that makes a difference.
Update: Found out how to use flashboot, i did fastboot oem enableqxdm 0 , and my SD card AND internal storage is working again!! =D
USB connectivity is still a No-go. Is there a way to flash an image to a particular partition through fastboot? If ya'll could give any help, it would be MUCH appreciated. Thank you.
You sound like all the people who have had the 5/3 vibrate black screen. USB stops working, adb driver wont show up, phone boots fine with USB connected. Somehow you got the phone somewhat working again which would confirm that its an issue with root/recovery. Except for your USB not working. This I thought was a hardware issue which caused the rest of the issues but I have no clue. I wonder if the root has anything to do with the USB chip on the phone.
Chevelle1768 said:
What does the output from this say?
Code:
"cat /dev/mtd/mtd0"
Click to expand...
Click to collapse
I am having a similar problem... I got the 5 vibe and green light of death... did a bunch of voodoo and got it working but with no USB connectivity.
I have been able to root and restore from my nand backup.
I entered your command and got this as a reply:
Code:
SPCS_001DeviceWarmBootICE Serial InUseDebug Cable EnaCE USB# cat /dev/mtd/mtd0
HELP!!!
Im having the same problem, but the thing is that i updated to GingerBread, and now i can´t do the z4Root procedure Because Gingerbread is not compatible with it, so now im stuck, (With NO USB, Gingerbread 2.3.4 (Wich means NO Z4ROOT), man im fu....k´up, can anyone help me, Please, i feel like an asshole, by upgrading to 2.3.4....
Any Help will be Apreciated....
Ps: Sorry for my bad English....
What hboot version, abdroid version, and radio version are you guys on?
Well, im actually in a bad situation .....
INCREDIBLEC XD SHIP S-ON
HBOOT-0.92.0000
MICROP-0417
TOUCH PANEL-ATMEL224_10aa
RADIO-2.15.10.07.07
IM NOT ROOTED, AND I STUPIDLY INSTALLED 2.3.4 (i was desperate looking for a solution) i though it could fix that, but it didnt, and now i founded some kind of solution but i have to be on 2.2 to flash the "mtd0.img" file again....
Can anyone tell me what its mtd0.img for?
it controls the USB Connetions?
Also my Computer recognize the Phone (but i cannot transfer files to the Phone, or even root it with Unrevoked) im trying everything and no response from the phone.....
HELP!!
---------- Post added at 02:41 AM ---------- Previous post was at 02:31 AM ----------
Can i downgrade rom 2.3.4 to 2.2 Using the RUU.exe, when in fastboot?
No, it tells me "problem with the bootloader", and if i unplug the phone
it remains on the hboot saying "MAIN VERSION IS OLDER"
so i was wondering if i could rewrite the androi-info.txt from the PB31IMG.zip
in the Sdcard it could help me flashing again 2.2 (Froyo), but no it says abut the signature, and what if we copy the signature of the "PB31IMG.zip" and apply it to another file it could flash back to 2.2?
hackrxz said:
Well, im actually in a bad situation .....
INCREDIBLEC XD SHIP S-ON
HBOOT-0.92.0000
MICROP-0417
TOUCH PANEL-ATMEL224_10aa
RADIO-2.15.10.07.07
IM NOT ROOTED, AND I STUPIDLY INSTALLED 2.3.4 (i was desperate looking for a solution) i though it could fix that, but it didnt, and now i founded some kind of solution but i have to be on 2.2 to flash the "mtd0.img" file again....
Can anyone tell me what its mtd0.img for?
it controls the USB Connetions?
Also my Computer recognize the Phone (but i cannot transfer files to the Phone, or even root it with Unrevoked) im trying everything and no response from the phone.....
HELP!!
---------- Post added at 02:41 AM ---------- Previous post was at 02:31 AM ----------
Can i downgrade rom 2.3.4 to 2.2 Using the RUU.exe, when in fastboot?
No, it tells me "problem with the bootloader", and if i unplug the phone
it remains on the hboot saying "MAIN VERSION IS OLDER"
so i was wondering if i could rewrite the androi-info.txt from the PB31IMG.zip
in the Sdcard it could help me flashing again 2.2 (Froyo), but no it says abut the signature, and what if we copy the signature of the "PB31IMG.zip" and apply it to another file it could flash back to 2.2?
Click to expand...
Click to collapse
how did you install gingerbread? if it was OTA then do a factory reset. should rebuild the system. you WILL lose everything but it should get you in working order.
Will that bring me back to 2.2?
im gonna try .. thk anyways
i have same problem! but when i connect my inc to pc it works only like a charger!
i phone can't use internal memory! i can see files on phone only with file manager. and in recovery when i mount USB it's doesn't work. pc have htc sync driver
can you help me? where i can find the mtd0.img? and can it help me?
inc wont recognize usb connections at the computer
well i think it can help you, but I'm not really sure about what's going on with your Inc, but if you flash the “mtd0.Img" it will restore your USB connection
first at all, are you rooted?
if you do, just flash mtd0.img
if not, witch android version are you running?
i can give you some better instructions if you post your email address
add me or send me an email at: [email protected]
i will be glad to help you as someone did when i was in the same situation
---------- Post added at 10:58 PM ---------- Previous post was at 10:46 PM ----------
sinisterwolf, no
i just flashed the PB31img.zip by my self
and as you know it just took me to stock 2.3 all over again
i fixed my problem by
1- unlocking the bootloader at htcdev
2- then flashing a custom recovery (clockworkmod recovery)
3- flashed “su.zip" (Super User)
my phone got super user access back again, yeah!!!
4- after that i installed terminal emulator from Google play
5- i flashed mtd.img from my SDcard
i don't exactly remember the lines i typed to flashed right now but if you wanna know how, send me an email [email protected]
hackrxz said:
well i think it can help you, but I'm not really sure about what's going on with your Inc, but if you flash the “mtd0.Img" it will restore your USB connection
first at all, are you rooted?
if you do, just flash mtd0.img
if not, witch android version are you running?
i can give you some better instructions if you post your email address
add me or send me an email at: [email protected]
i will be glad to help you as someone did when i was in the same situation
---------- Post added at 10:58 PM ---------- Previous post was at 10:46 PM ----------
sinisterwolf, no
i just flashed the PB31img.zip by my self
and as you know it just took me to stock 2.3 all over again
i fixed my problem by
1- unlocking the bootloader at htcdev
2- then flashing a custom recovery (clockworkmod recovery)
3- flashed “su.zip" (Super User)
my phone got super user access back again, yeah!!!
4- after that i installed terminal emulator from Google play
5- i flashed mtd.img from my SDcard
i don't exactly remember the lines i typed to flashed right now but if you wanna know how, send me an email [email protected]
Click to expand...
Click to collapse
Can you or anybody on this post a link to download mtd0.img? I am having the same issue where when plugged into my pc, the phone treats it as a regular charger. It's weird because when I have it plugged into my car charger it thinks its a pc.
jarryd999 said:
Can you or anybody on this post a link to download mtd0.img? I am having the same issue where when plugged into my pc, the phone treats it as a regular charger. It's weird because when I have it plugged into my car charger it thinks its a pc.
Click to expand...
Click to collapse
Fastboot flash thishttp://dinc.does-it.net/Guide_Root_New_Hboot/mtd0.img, then do the froyo ruu.

[Q] Stuck in recovery boot loop HTC Desire GSM ~ ASSISTANCE APPRECIATED!!

Severe panic!!
I rooted my Desire which was running 2.2 Froyo on the O2 UK network using unrevoked and it worked fine without any issues. Custom recovery by ClockworkMod.
The next day I then decided i needed to turn S-off so found a guide and tried installing unrevoked forever from a zip on the root of the SD and i got 'installation aborted error 42'. Tried again the next day but before i got started i decided to give myself re-assurance that i wouldnt lose anything on the device so i entered recovery and chose restore.
Big mistake! My handset then rebooted and got to the O2 splash screen. It wont move from there. Pulled battery out and tried again. Same. I assume i havent bricked the device and it is just stuck in a boot loop?
Since then i have removed all my user data from the SD card and 'cleared storage'. Tried installing an miui rom and again 'installation aborted'.
Can anyone clarify why this is happening and point me in the right direction?
I am a noob and would appreciate any help on this.
TannyBhoy said:
Severe panic!!
I rooted my Desire which was running 2.2 Froyo on the O2 UK network using unrevoked and it worked fine without any issues. Custom recovery by ClockworkMod.
The next day I then decided i needed to turn S-off so found a guide and tried installing unrevoked forever from a zip on the root of the SD and i got 'installation aborted error 42'. Tried again the next day but before i got started i decided to give myself re-assurance that i wouldnt lose anything on the device so i entered recovery and chose restore.
Big mistake! My handset then rebooted and got to the O2 splash screen. It wont move from there. Pulled battery out and tried again. Same. I assume i havent bricked the device and it is just stuck in a boot loop?
Since then i have removed all my user data from the SD card and 'cleared storage'. Tried installing an miui rom and again 'installation aborted'.
Can anyone clarify why this is happening and point me in the right direction?
I am a noob and would appreciate any help on this.
Click to expand...
Click to collapse
Try to bring you phone to stock.
Download RUU .
Turn your phone on in fastboot (hold back button and press power - when your phone is off).
You have to have HTC Sync installed.
Run the exe file.
After that repeat the rooting and s-off-ing procedure.
Can the RUU be flashed in clockwork mod recovery or does it have to go through HTC Sync?
If it cannot be flashed in Clockwork Mod, I presume he has to
Connect phone via USB to PC,
boot into Fastboot as you mentioned
run HTC Sync
and then run the Ruu.exe file (does HTC Sync recognise this filetype and then do it's thing?)
And that's it? (Just that it seems too simple!)
OriginalThinking said:
Can the RUU be flashed in clockwork mod recovery or does it have to go through HTC Sync?
If it cannot be flashed in Clockwork Mod, I presume he has to
Connect phone via USB to PC,
boot into Fastboot as you mentioned
run HTC Sync
and then run the Ruu.exe file (does HTC Sync recognise this filetype and then do it's thing?)
And that's it? (Just that it seems too simple!)
Click to expand...
Click to collapse
You might need a goldcard. Try without one for now.
Right I'll let him know to give that a go. If it doesn't work I might pick your brains around the goldcard option.
Massive thanks so far for your advice!
Dude thanks for that. Im going to give that a bash and let you know how i get on!
Much appreciated!
Haven't tried this but it's worth giving it a shot. http://www.addictivetips.com/mobile...gold-card-for-htc-desire-without-hex-editing/
Or this: http://www.nazriawang.com/2010/04/how-to-create-goldcard-with-ubuntu.html
TannyBhoy said:
The next day I then decided i needed to turn S-off so found a guide and tried installing unrevoked forever from a zip on the root of the SD and i got 'installation aborted error 42'. Tried again the next day but before i got started i decided to give myself re-assurance that i wouldnt lose anything on the device so i entered recovery and chose restore.
Click to expand...
Click to collapse
Hello. I think you wanted to say you chose back-up, otherwise you couldn't have chosen the restore option since you don't have any restore points.
So if you hit back-up and your phone stuck in the boot loop it is normal. This is a problem because of the root and the fact that making a nandroid back-up will mess something in the NAND. But restoring the back-up you just made should resolve all the problems. I had the same issue and by only restoring the back-up I've just made got me working back, and still had the ROOT.
I don't think you need to run a RUU just for this.
UsManyDead said:
Hello. I think you wanted to say you chose back-up, otherwise you couldn't have chosen the restore option since you don't have any restore points.
Click to expand...
Click to collapse
I should have made clearer sorry. After i rooted successfully i entered recovery and hit backup option and it told me it had created a backup successfully. I had been using the phone as normal for another day before deciding to s-off and at that point i thought to 'test' my backup to make sure it had done it so i chose restore thinking anything i have downloaded on the phone since the back up will disappear and was expecting the restore to bring my phone back to the settings i had the previous day but the restore failed and thats when it got stuck in the boot loop.
Mine did the same thing except, instead of trying to s-off it just decided at one point that it felt like it, literally, I wasnt even using it at the time it was just charging. I did downloaded the stock ruu, it was linked earlier. Put it in fastboot, run the ruu and boom, however i did it on my goldcard, so make one if it doesnt work without it. Good luck.
paul.c said:
Try to bring you phone to stock.
Turn your phone on in fastboot (hold back button and press power - when your phone is off).
You have to have HTC Sync installed.
Run the exe file.
After that repeat the rooting and s-off-ing procedure.
Click to expand...
Click to collapse
BACK IN BUSINESS!! Dude you are the man! The RUU didnt install as it was a different boot version so from the site you suggested i used the Froyo version and its now working! Many thanks.
P.s. What's the easiest way to s-off? Also whats the correct way to create a complete back up restore point and then actually restore to that point without getting to this stage again?
paul.c said:
Try to bring you phone to stock.
Turn your phone on in fastboot (hold back button and press power - when your phone is off).
You have to have HTC Sync installed.
Run the exe file.
After that repeat the rooting and s-off-ing procedure.
Click to expand...
Click to collapse
BACK IN BUSINESS!! Dude you are the man! The RUU didnt install as it was a different boot version so from the site you suggested i used the Froyo version and its now working! Many thanks.
P.s. What's the easiest way to s-off? Also whats the correct way to create a complete back up restore point and then actually restore to that point without getting to this stage again?
TannyBhoy said:
BACK IN BUSINESS!! Dude you are the man! The RUU didnt install as it was a different boot version so from the site you suggested i used the Froyo version and its now working! Many thanks.
P.s. What's the easiest way to s-off? Also whats the correct way to create a complete back up restore point and then actually restore to that point without getting to this stage again?
Click to expand...
Click to collapse
Easiest way to s-off is alpharev:
http://alpharev.nl
***NEW ISSUE***
Since i have my phone back to it's original state and have lost root access. The idea is to root again via Unrevoked, which requires me to update the Android 1.0 driver (in device manager under other devices) to the Android Bootloader Interface. However, DM now does not say 'other devices - Android 1.0' and instead it says 'Android Devices - MY HTC'. So i decided to completely uninstall HTC Sync and all it's drivers and then rebooted PC, reinstalled SYNC and then uninstalled again but this time leaving the drivers in. Rebooted again and repeated the process but it still recognises the device as 'MY HTC' instead of 'Android 1.0'.
Could it be that this is fine, it's just the new way since i am using the updated version of HTC sync now? Or is this going to cause an issue? I am now playing it a lot safer to avoid anymore issues and quite happy to try something you may suggest...
TannyBhoy said:
***NEW ISSUE***
Since i have my phone back to it's original state and have lost root access. The idea is to root again via Unrevoked, which requires me to update the Android 1.0 driver (in device manager under other devices) to the Android Bootloader Interface. However, DM now does not say 'other devices - Android 1.0' and instead it says 'Android Devices - MY HTC'. So i decided to completely uninstall HTC Sync and all it's drivers and then rebooted PC, reinstalled SYNC and then uninstalled again but this time leaving the drivers in. Rebooted again and repeated the process but it still recognises the device as 'MY HTC' instead of 'Android 1.0'.
Could it be that this is fine, it's just the new way since i am using the updated version of HTC sync now? Or is this going to cause an issue? I am now playing it a lot safer to avoid anymore issues and quite happy to try something you may suggest...
Click to expand...
Click to collapse
Same here. But everything is working fine.
So put phone in usb debug mode and "only charge" mode, start abd, connect phone via usb to pc and type
Code:
adb devices
. If your desire's serial number is shown, everything is fine.
MatDrOiD said:
Same here. But everything is working fine.
So put phone in usb debug mode and "only charge" mode, start abd, connect phone via usb to pc and type
Code:
adb devices
. If your desire's serial number is shown, everything is fine.
Click to expand...
Click to collapse
Hey man thanks for the advice. If yours is working fine, ive no reason not to try it!
As i am a noob, can you clarify "start abd" ??
Also, type code "adb devices", where to type?
TannyBhoy said:
Hey man thanks for the advice. If yours is working fine, ive no reason not to try it!
As i am a noob, can you clarify "start abd" ??
Also, type code "adb devices", where to type?
Click to expand...
Click to collapse
To start adb issue: "adb start-server" command without the quotes
To stop it: "adb kill-server"
Here is the complete list: http://developer.android.com/guide/developing/tools/adb.html
TannyBhoy said:
***NEW ISSUE***
Since i have my phone back to it's original state and have lost root access. The idea is to root again via Unrevoked, which requires me to update the Android 1.0 driver (in device manager under other devices) to the Android Bootloader Interface. However, DM now does not say 'other devices - Android 1.0' and instead it says 'Android Devices - MY HTC'. So i decided to completely uninstall HTC Sync and all it's drivers and then rebooted PC, reinstalled SYNC and then uninstalled again but this time leaving the drivers in. Rebooted again and repeated the process but it still recognises the device as 'MY HTC' instead of 'Android 1.0'.
Could it be that this is fine, it's just the new way since i am using the updated version of HTC sync now? Or is this going to cause an issue? I am now playing it a lot safer to avoid anymore issues and quite happy to try something you may suggest...
Click to expand...
Click to collapse
Thanks for the suggestions surrounding ADB but i guess im too much of a noob for that part, it seems massively complicated, im sure it doesnt to you guys. Isnt there an easier way? Or considering my above quote, can i just assume that its all working fine and go ahead with the root or should it really need to have 'Android 1.0' in device manager?
Im pretty certain this all happened becuase the first time i rooted i had followed instructions and uninstalled HTC Sync (not the drivers) which had been on my system since i got the phone lat year. Since i had to reinstall to flash the RUU im certain its an updated version of HTC Sync thats causing this issue. But is it really an issue?
TannyBhoy said:
Hey man thanks for the advice. If yours is working fine, ive no reason not to try it!
As i am a noob, can you clarify "start abd" ??
Also, type code "adb devices", where to type?
Click to expand...
Click to collapse
Here you have a nice guide about adb:
http://androidforums.com/desire-all...fastboot-windows-updated-1st-june-2011-a.html
This should answer all your questions.

Incredible won't boot into CM7 or Recovery

I've look around for over an hour and can't find anything quite like this. I didn't try to change anything or put on a new rom - nothing - it just stopped working.
I've been running CM7 for months just fine. I've had to re-install it a few times due to various random errors and whatnot but for the most part it has been fine.
Phone was working fine. I plugged it in and went to bed.
I woke up this morning to my phone getting to the white HTC Incredible page and then perpetually rebooting.
I can't get past that either to get into recovery or CM7.
I can get into hboot but I have no idea what to do there.
What the hell could have happened over night?
Any chance this can be fixed or is it bricked?
This is a known issue. This happened to my phone and 2 subsequent replacements before I got one that it didn't happen to.
I'd call Verizon or take it in - hopefully you're still in your warranty.
thumpernc24 said:
I've look around for over an hour and can't find anything quite like this. I didn't try to change anything or put on a new rom - nothing - it just stopped working.
I've been running CM7 for months just fine. I've had to re-install it a few times due to various random errors and whatnot but for the most part it has been fine.
Phone was working fine. I plugged it in and went to bed.
I woke up this morning to my phone getting to the white HTC Incredible page and then perpetually rebooting.
I can't get past that either to get into recovery or CM7.
I can get into hboot but I have no idea what to do there.
What the hell could have happened over night?
Any chance this can be fixed or is it bricked?
Click to expand...
Click to collapse
If you can get into hboot. you should be able to RUU to stock and re root.
synisterwolf said:
If you can get into hboot. you should be able to RUU to stock and re root.
Click to expand...
Click to collapse
tried to do that too at the hboot menu and I get the same problem.
I have the extended warranty from Verizon but are they going to check if it is rooted?
thumpernc24 said:
tried to do that too at the hboot menu and I get the same problem.
I have the extended warranty from Verizon but are they going to check if it is rooted?
Click to expand...
Click to collapse
if you can get into hboot they will see at the top it says S=off. you might want to try to get it back to S=on
synisterwolf said:
if you can get into hboot they will see at the top it says S=off. you might want to try to get it back to S=on
Click to expand...
Click to collapse
any clues how to do that?
i've been looking around like crazy and can't seem to figure it out.
Feel dumb - I just need to get this done so I can take it in and get a new phone - it is driving me insane!
In order to get s-on you will need a custom recovery installed and then use the s-on tool provided by unrevoked. So you will need to flash a custom recovery thru hboot and then flash the s-on tool thru recovery, and then ruu either thru hboot with a PB31IMG.zip, or with a ruu.exe with your pc. You can get the recovery image and ruus from here http://www.pvillecomp.com. You can get the s-on tool from the unrevoked forever site.
thumpernc24 said:
any clues how to do that?
i've been looking around like crazy and can't seem to figure it out.
Feel dumb - I just need to get this done so I can take it in and get a new phone - it is driving me insane!
Click to expand...
Click to collapse
same way you got it off.
unrevoked.com has this info see link below. i also quoted the area you need to look but read it all please.
http://unrevoked.com/rootwiki/doku.php/public/forever
Installation Instructions
To install unrevoked forever on your phone, perform the following steps.
If your phone does not already have a custom recovery, use unrevoked3 to root your phone.
The installation process cannot take place if the phone does not have a custom recovery installed.
Download the most recent ''unrevoked-forever.zip'' to a temporary location on your computer.
The update can be installed like any custom .zip file. Simply flash it from your custom recovery. Both Amon_RA and Clockworkmod Recoveries support custom .zip installs from the sdcard.
Either select the option to install a .zip from your SD card, or apply it as an update.zip as follows:
Place the update.zip file into the root of your SD card. You can do this with adb with the command: adb push unrevoked-forever.zip /sdcard/update.zip
Reboot your phone into recovery mode. You can do this by removing your phone's battery, holding down the VOLUME DOWN button, and inserting the battery; at the menu, press VOLUME DOWN to highlight recovery, then press POWER to select it.
Did you read the important safety information above?
Do so now before continuing.
Select apply sdcard:update.zip from the menu.
Press VOLUME DOWN until Yes is highlighted, then select it.
Review the output to determine if there were any errors.
If messages beginning in E: appear, stop! If possible, join IRC for support.
Restart the phone normally, then reboot the phone into the bootloader. This can be done by holding VOLUME DOWN while powering the system up. Observe at the top that S-OFF appears.
Optional, but recommended: show your support (and your S-OFF bootloader) by flashing a custom splash screen!
"How can this be removed or undone if I need to take my phone in for service?
Download the latest ''S-ON'' tool to a temporary location and follow the installation instructions above to run it. Once your phone is S-ON, you may lose root permanently if you install an official update."
---------- Post added at 12:10 PM ---------- Previous post was at 12:01 PM ----------
i also found this video for you. i hope it helps.
http://androidforums.com/incredible...ideo-howto-unroot-incredible-downgrading.html
I tried that and it didn't work
I followed the video and now my phone is even more messed up.
Won't get past bootloader, still have s-off.
now when i power on it boots straight into bootloader so it's really obvious. Wonderful. fml.
I obviously can't fix it and I need a phone. I'm going to the verizon store and see what they say
thumpernc24 said:
I tried that and it didn't work
I followed the video and now my phone is even more messed up.
Won't get past bootloader, still have s-off.
now when i power on it boots straight into bootloader so it's really obvious. Wonderful. fml.
I obviously can't fix it and I need a phone. I'm going to the verizon store and see what they say
Click to expand...
Click to collapse
So you can get into hboot and your s-off, but you cant get clockwork recovery to flash as a PB31IMG.zip? What does it say when it auto searches for the file? You say you cant get into recovery, what exactly happens when you select recovery in hboot?
Same thing it does when it tries to regular boot.
Well - it did before i tried to apply that PB file in Hboot. Now it doesn't do anything at all period.
Verizon didn't really look at it and just said they would warranty it for me. Woo!
thumpernc24 said:
Same thing it does when it tries to regular boot.
Well - it did before i tried to apply that PB file in Hboot. Now it doesn't do anything at all period.
Verizon didn't really look at it and just said they would warranty it for me. Woo!
Click to expand...
Click to collapse
Well if they cant get into hboot they cant check if you are rooted so your good to go. once it gets to factory they just plug it into a machine and it reflashes everything so they dont check it.
as I said before - when I select recovery it does the same thing as when i tried to normal boot (well now the recovery option isn't even there anymore)
But what it did was go to the white HTC Incredible screen and then just start rebooting over and over....
similar problem
i flashed the new cyanogen 7.1.0 stable earlier today and did a complete wipe. 3g wouldn't work no matter what i tried. suddenly, the phone is now in a boot loop (just rebooted on it's own). I get one vibrate, the white "HTC Incredible" screen and it reboots, rinse, repeat. I do have access to hboot (0.92).
I have attempted to flash what appears to be every available option for recoveries including clockwork, RA, and stock. it says everything installs fine and i reboot. still unable to access recovery in any way, just starts the same boot loop.
attempted RUU both via PC and .zip extraction. PC method says i'm not connected via usb despite proper drivers and phone recognition by window 7 and .zip acts as if everything applies appropriately then produces the same boot loop.
I have tried everything I can find over the last 6 hours of searching various forums. Anyone have an idea on a potential fix or a way to get s-on without being able to access recovery?
I'm about to exercise my insurance plan and put this phone under my tires and slowly back up...all replies are greatly appreciated

[Q] Boot loop can't get into recovery mode [Fixed]

Hi
I'm an idiot, and this is what I've done.
Used AAHK successfully.
Backed up my stock ROM.
Flashed new ROM (Revolution HD, latest version)
All ok up to this point. Aware that I need to update my radio, I accidentally re run AAHK (the full thing, menu 1)
AAHK, gets stuck after radio downgrade.
When I power on the phone, it vibrates once and I get the HTC Logo - it gets stuck at this point.
I can get into the boot menu (Power+Vol down) If I select recovery, the phone reboots and shows a red exclamation mark.
I hope this can be resolved. Help please.
Thanks
Alright. Plug your phone into your computer, leaving the phone on. Check the adb by running adb devices in the terminal. If you still see the device Serial #, re run the hack kit.
But
What you MIGHT need to do is pull out the battery, and put it back in. HOLD down volume and TAP the power button. This should get you to bootloader. Once there, plug in your USB to the computer and go to "Fastboot USB". After that, download the ATT RUU, and run that. This will return you to stock, and then re run the hack kit.
^ This might be the long way out but it WILL recover your phone.
EDIT: You're on the Desire HD, my bad. Download your stock RUU and run that, not the ATT RUU. My bad, I'm in the United States on ATT
Hi
Thanks for the reply. I tried the command line, but couldn't get the Serial #
I did wonder about ATT, thanks for the edit. I'm a bit nervous about which stock to choose.
I was previously on an Orange UK Gingerbread firmware. Can I just choose a vanilla Gingerbread RUU. Does it matter which version?
Thanks
Which Orange ROM was shipped with your phone? If you can't get the serial number you're going to have to download the RUU and Reinstall. And then re-root the phone.
It doesn't matter which RUU you run, so long as its the official Carrier version.
Hopefully this helps!
---------- Post added at 03:37 AM ---------- Previous post was at 03:27 AM ----------
Follow this link, and about halfway down is the Orange shipped ROM:
http://www.filefactory.com/f/efa28fefafc4af9c/
Thanks for the reply.
I found that page before I saw your post. That Orange package looked like Froyo version? and I was worried about doing GB to Froyo downgrade (memory maps etc) Maybe the RUU doesn't care about that?
So I chose a GB RUU that looked suitable, this one:
RUU_Ace_Gingerbread_S_HTC_WWE_2.50.405.2_Radio_12.54.60.25_26.09.04.11_M2_release_199042_signed.exe
It's very simple, just click click click and my phone is back
So thanks again
Just flash recovery again.
Then from recovery flash a ROM.
ADB can't work in bootloader but fastboot yes.
Your problem is easy to solve, do not worry.
You're not an idiot... this is called 'learning'
Edit: too late. Next time you will know how to do:
The first white backgrounded menu is the bootloader
The one after is Recovery (black background with orange or blue text).
Fastboot works in bootloader, ADB in recovery.

Incredible 2 Issue!

So. I run a Galaxy Nexus now, gave the wife the Dinc2. Been rooted and rom'd since AlpharevX was available. Had to get an insurance phone. Downgraded Hboot etc, ran Revolutionary. Had been running CM7 but decided to give Liquid a go. Wiped it and fired it up. Worked for about two weeks and bootlooped. No biggie, I will just nand back. Can't. I get the E:/cant mount /cache/recovery/command along with the logs. Ok. I will RUU. Got a stock image. It bypasses bootloader and gets stuck on boot. Says updating. Forever. Battery pull. Ok. I will use adb and try to push files to it. No go. Doesn't see the device. It will see it if its looping or if I am in recovery and I can restart the bootloader but once it gets to fastboot....won't see the device again.
Looking on the net I see tons of conflicting info so I decided to post up and see if anyone has ideas.
Wait, can you still get into recovery?
I can get into recovery...briefly. It will reboot if it sits too long. I have tried restoring a nand and it reboots. Tried to factory reset and same deal, starts and reboots.
What recovery are you using?
Forgot to hit post.....ooops. Anyway I am running Clockwork.....
Did the phone get exposed to water at any time in the past?
No water damage.....
try reflashing the clockwork mod image. You can find the instructions in guide #6 in my sig.
Problem is I can't see the device in adb.
Even if you put it into fastboot?
Nope. Its weird. I can get it to see the device when its bootlooping. Or in recovery.
Wait, when it's in fastboot, you are using:
fastboot devices
to check and see if the phone is recognized?
Hmmm. No. Adb devices
Well, there's your problem. You need these commands to make it work. First, put your phone into fastboot. Then go:
Code:
cd [insert location of android sdk here]/tools
fastboot devices
---------- Post added at 09:05 PM ---------- Previous post was at 09:01 PM ----------
Then you should see your device pop up. Then follow the steps in my guide #6 for flashing recovery.
Yep. Wrong command. Thanks. It sees it. but I have tried to push the recovery to it before and it sends it okay but then sits on writing forever. Really appreciate the help!
I'll look into it some more and let you know.
Again. Appreciate it. I typically don't even post for help. Just scour until I find a solution but this one has me baffled.
If it helps. I can push to my GN without issue. Wiped last night and had to push Clockwork Touch to it. Went off without a hitch.
Quick update. I even tried going through my old Windows Netbook Ugh. Windows. Anyway. Tried to run a HTC rom update exe. It sees the phone in fastboot but as soon as it tries to push the rom update it tries to reboot to bootloader and hangs......
JMac024 said:
Quick update. I even tried going through my old Windows Netbook Ugh. Windows. Anyway. Tried to run a HTC rom update exe. It sees the phone in fastboot but as soon as it tries to push the rom update it tries to reboot to bootloader and hangs......
Click to expand...
Click to collapse
JMac,
have you tried using the fastboot oem RUU command? could be something hanging in the cache that didn't finish writing completely.
You said you can see the phone with fastboot right?
Try "fastboot erase cache" ??
Personally I would re download attn1's tool and try and downgrade again, his tool is awesome because it flashes the RUU using the oem fastboot.
Try this again from the beginning and see what it does.
http://rootzwiki.com/topic/14785-inc2guide-got-234-its-not-too-late-for-s-off/
Or just go here and download his script, run as admin in windows. See what that does for you
http://forum.xda-developers.com/showthread.php?t=1298990

Categories

Resources