[Q] HTC Droid Incredible Boot Loop - Droid Incredible Q&A, Help & Troubleshooting

Incredible XD Ship S=On
Hboot- 0.92.0000
Microp-0417
Touch Panel- ATMEL224_16ab
Radio-2.15.10.07.07
July 23 2010, 18:06:51
Droid incredible turns on but stays on white incredible screen
there is no water damage
phone is not rooted and has not been tampered with ever
How can I fix this? Ive tried doing a search and downloading PB31IMG.zip but it tells me that it is too old..

Try this one. http://dinc.does-it.net/Stock_Images/4.06.605.3/PB31IMG.zip
If that dosent work you should try this ruu exe with a pc. http://dinc.does-it.net/Stock_Image...0_Incredible_C_hboot_1.02.0000_4.08.605.2.exe

cmlusco said:
Try this one. http://dinc.does-it.net/Stock_Images/4.06.605.3/PB31IMG.zip
If that dosent work you should try this ruu exe with a pc. http://dinc.does-it.net/Stock_Image...0_Incredible_C_hboot_1.02.0000_4.08.605.2.exe
Click to expand...
Click to collapse
niether of those worked
keeps saying to old
and the ruu says the phone isnt plugged in is there some type of mode i have to put it in?
i can get into the fastboot menu so i hoping there is a waay to fix it.

sexykika said:
niether of those worked
keeps saying to old
and the ruu says the phone isnt plugged in is there some type of mode i have to put it in?
i can get into the fastboot menu so i hoping there is a waay to fix it.
Click to expand...
Click to collapse
Phone should be in charge only mode, and you have to have htc sync installed on your pc to have the correct drivers.
Try this PB31IMG.zip http://dinc.does-it.net/Stock_Images/4.08.605.2/PB31IMG.zip

cmlusco said:
Phone should be in charge only mode, and you have to have htc sync installed on your pc to have the correct drivers.
Try this PB31IMG.zip http://dinc.does-it.net/Stock_Images/4.08.605.2/PB31IMG.zip
Click to expand...
Click to collapse
how would i put it in charge only mode?
the phone doesnt fully turn on,
i know i have the correct drivers they installed correctly.

sexykika said:
how would i put it in charge only mode?
the phone doesnt fully turn on,
i know i have the correct drivers they installed correctly.
Click to expand...
Click to collapse
Oh yeah i forgot you need to be able to boot to do an ruu exe, been a long time since ive done one. What about that last PB file i posted?

cmlusco said:
Oh yeah i forgot you need to be able to boot to do an ruu exe, been a long time since ive done one. What about that last PB file i posted?
Click to expand...
Click to collapse
im still getting a bootloop it did accept the update but the phone stays on the htc incredible white screen
now when i go to the fastboot menu up on top highlighted in purple it says
*** LOCKED (OOW) ***

so i figured id try and root this phone
i got the bootloader unlocked no problem
i flashed the rcovery image as well but now when i'm in recovery and I try to mount the usb storage or sd card it says
E:Unable to write to ums lunfile (no such file or directory)
or
Error mounting /sdcard!

sexykika said:
so i figured id try and root this phone
i got the bootloader unlocked no problem
i flashed the rcovery image as well but now when i'm in recovery and I try to mount the usb storage or sd card it says
E:Unable to write to ums lunfile (no such file or directory)
or
Error mounting /sdcard!
Click to expand...
Click to collapse
Try this.
Boot into the bootloader and make sure it says FASTBOOT in the middle highlighted in red.
Open command prompt and type
“fastboot oem enableqxdm 0″ without the quotation marks of course. That should resolve the sd card not being mountable.
Then follow this thread http://forum.xda-developers.com/showthread.php?t=1506258 to get root and true s-off if desired. Just skip the parts you have already done.

yeah thats the tutorial i was following
by the way great write up really easy to understand
okay i will do that but in order to get s-off i need the phone to turn on?? Right??
So if i root and can get into cwm recovery and get the sd card to mount I should be able to flash a rom correct???

that is not working i'm in fastboot mode
but it says fastboot is not recognized as an internal or external command operable program or batch file

sexykika said:
that is not working i'm in fastboot mode
but it says fastboot is not recognized as an internal or external command operable program or batch file
Click to expand...
Click to collapse
Do you have fastboot.exe installed on your pc, if so after opening the cmd prompt navigate to where fastboot.exe is and then trt the command.

I don't know whether this is still an option now that you've unlocked the bootloader but it is worth a try. This is a link to a guide I wrote for easily getting s-off and rooting your phone and if you would like, flashing a new ROM. Since you had this crash without having ever tampered with the phone, you might be in a tough situation but go ahead and start from the beginning of the guide and see where it gets you. Good luck!
http://forum.xda-developers.com/showpost.php?p=26146567&postcount=15

so i had a similar situation on my dinc. it would bootloop at the red droid snapdarogon processor screen and that is as far as it would go then just keep rebooting to that point. i did the htcdev website and got the bootloader unlocked. i got clockwork recovery installed and have a rom running on it now. but every app i try to open just force closes. the only thing i can do is text and make phone calls on it. the phone still says s-on but says unlocked on top. when i try to use onrevoked to gain root it fails and says "is your firmware to new?". anyone have any ideas on this? thanks. didn't mean to crowd someone elses post.

scoobntaz1996 said:
so i had a similar situation on my dinc. it would bootloop at the red droid snapdarogon processor screen and that is as far as it would go then just keep rebooting to that point. i did the htcdev website and got the bootloader unlocked. i got clockwork recovery installed and have a rom running on it now. but every app i try to open just force closes. the only thing i can do is text and make phone calls on it. the phone still says s-on but says unlocked on top. when i try to use onrevoked to gain root it fails and says "is your firmware to new?". anyone have any ideas on this? thanks. didn't mean to crowd someone elses post.
Click to expand...
Click to collapse
Did you wipe everything before flashing the rom? If not that may be the cause of your problem.
To gain true s-off you must first fastboot flash a froyo misc img, then downgrade to froyo with an ruu, and then use unrevoked 3.22. Follow this guide here skipping the steps you have already done. http://forum.xda-developers.com/showthread.php?t=1506258

Since you have clockwork you could flash superuser though clockwork to gain superuser and use unrevoked forever to gain s-off, if you so desire.
link to superuser: http://androidsu.com/superuser/
I'm guessing your ROM is gingerbread or ICS so you want to use Superuser-3.0.7-efghi-signed.zip
and unrevoked forever is here: http://unrevoked.com/rootwiki/doku.php/public/forever

Similar Situation
I have a Dinc that is also unrooted and has never been tampered with. I did the recent software update and the phone has not started since then. It only gets to the white screen that says HTC Incredible. I have tried the solutions proposed in this thread. I don't mind rooting if i need to but I am having absolutely no luck. Any ideas?
EDIT: So after hours of messing with this stupid phone, I left the battery out for about 5 minutes and while putting it back in i accidentally turned the phone back on.... and magically it started up just fine. I'm not sure what fixed it... Weird.

Can you help me fix the boot loop...?
sexykika said:
so i figured id try and root this phone
i got the bootloader unlocked no problem
i flashed the rcovery image as well but now when i'm in recovery and I try to mount the usb storage or sd card it says
E:Unable to write to ums lunfile (no such file or directory)
or
Error mounting /sdcard!
Click to expand...
Click to collapse
I have a droid incredible and having the same rebooting issue as you all have. I tried to use the image given but that did not solve the problem as well.The phone boots up goes to the HTC incredible white boot screen logo and continues rebooting.
I cannot go pass the white screen boot logo.
Could you please be able to tell me how you managed to unlock the boot loader?

prasannarupan said:
I have a droid incredible and having the same rebooting issue as you all have. I tried to use the image given but that did not solve the problem as well.The phone boots up goes to the HTC incredible white boot screen logo and continues rebooting.
I cannot go pass the white screen boot logo.
Could you please be able to tell me how you managed to unlock the boot loader?
Click to expand...
Click to collapse
What is your phones current status?
S-on/off, hboot version, android version?
Download and place this file http://dinc.does-it.net/Stock_Images/4.08.605.15/PB31IMG.zip on your sdcard, in no folders. Then boot to hboot and it should find the file and prompt to press vol up to update. That should get you back to stock and working.
You can unlock the bootloader on the htcdev site. http://htcdev.com/bootloader

still rebooting
cmlusco said:
What is your phones current status?
S-on/off, hboot version, android version?
Hi,
Thank you very much for responding to my question. I tried to do the steps above but it ended up with the same result still after updating and rebooting to the stock image you gave above.
I also now see something like ******Locked ****** in the boot loader screen.
phone current status
S-ON
hboot version -1.07.0000
android version - i cannot figure that out yet since i cant fully bootup the os. i think i had froyo
prior to the update i had hboot version as something like 0.92.0000
why can't i still boot to the stock image and it still keeps rebooting?
I really appreciate your help.
Click to expand...
Click to collapse

Related

Stuck in bootloader, S-ON, clockworkmod can't mount sdcard....bricked?

I've been running CM7 on my phone for quite some time along with SOS and recently the latest CM7 from here. Somehow my phone appears to be bricked. Perhaps from a faulty nandroid that I restored? It goes into bootloader but I can't do much there. When I select recovery I get the 5 vibes of death and black screen. I can get to CWM with USB connected, but CWM can't mount the sdcard. And somehow I noticed I have S-ON. I originally rooted with unrevoked. Can anyone offer any advice on how to proceed?
Flash Amon Ra. CWM is just not a good recovery with the Evo, but even so, with AR, I've had my recovery get corrupted twice with the same error you're having (Both times were after the only 2 times I ran a superwipe) and had to reflash my recovery, which fixed it.
And I can do that by getting a copy of Amon Ra in the PC36IMG.zip format, like here?
ogp said:
And I can do that by getting a copy of Amon Ra in the PC36IMG.zip format, like here?
Click to expand...
Click to collapse
Yes.This is a good site to get what you need.
ogp said:
And I can do that by getting a copy of Amon Ra in the PC36IMG.zip format, like
Click to expand...
Click to collapse
not bricked
Your recovery is corrupted. Just place the PM36IMG in the root of the SD Card and as soon as you PWR+Vol- your phone will rub the update package and you will then be able to enter recovery. If you phone turns on, it's not bricked. There is always a way to fix it. Message me at any step you get to and if your phone won't go any farther I will message you back with the solution.
Ok, so I've copied that file to my sdcard and booted. hboot sees the file and it appears to load with a vertical blue indicator to the right. But I never get any prompts to install. Once the indicator completes, it goes back to the hboot menu. Will this not install because I have S-ON?
Ahh, well, yeah, I didn't know you were S-on. You have to be S-off to flash a custom recovery
Ok. I'm not sure how I got S-ON. I'm pretty sure it was off so I could flash CM7 and CWM, etc. Anyway, can I easily turn it off?
I've got hboot 2.10.0001
Radio 2.15.00.11.19
I can get it to boot into CM7 but it won't recognize the sdcard.
I can't seem to get my phone working with adb. I have adb enabled and when I connect my usb cable to my phone and laptop, the phone says debugging enabled but my laptop can't talk to it via adb. I also tried to ensure hboot drivers are installed and I still show android bootloader interface in device manager. When I boot into bootloader and select hboot usb and then connect my usb cable, it shows hboot usb plug but adb devices still shows nothing connected. So my sdcard and usb seem to not be working properly.
What can I load via hboot with S-ON? I've tried to update the radio as well as loading a rooted stock rom by loading the files on my sdcard as PC36IMG.zip. hboot sees them and loads/checks them, but I never get the option to install. I even tried stock 1.32.651.1 and it loads and checks but I still don't get the option to install.
Nothing. You need to run the RUU, either via pc36img or by the exe on your computer, re-root, and then flash recovery
Could there be something wrong with my bootloader? I tried to run this RUU and it definitely gets loaded and checked, but I never get the option to install. It just goes back to the bootloader menu. Any ideas why I don't get the option to install? Is the RUU version too old for my phone/bootloader version? I don't think I can run the .exe since I'm having a difficult time getting my phone to talk to my pc via USB.
So I was able to get it to show up in adb by booting into bootloader and selecting hboot usb and then going into recovery. When I try to run unrevoked3 I get the error Device "/sbin/sh: getprop: not found" is not supported at this time.
I think you'll need to run Revolutionary, although it's been so long since I rooted, or follwed rooting processes, I'm not sure, based on your Hboot version, but that determines which root process you'll need to use.
Sorry this is dragging on so long.
Also, jump on IRC, Freenode #htc-evo.
Those guys are great at helping people out
My phone is still rooted, it just has S-ON for some reason. I looked at Revolutionary but wasn't sure that applied since my hboot version, 2.10.0001, isn't listed in the options and I'm having trouble talking to my phone via usb/adb.
HipKat said:
I think you'll need to run Revolutionary, although it's been so long since I rooted, or follwed rooting processes, I'm not sure, based on your Hboot version, but that determines which root process you'll need to use.
Sorry this is dragging on so long.
Also, jump on IRC, Freenode #htc-evo.
Those guys are great at helping people out
Click to expand...
Click to collapse
No one on IRC seems to have an input....
ogp said:
No one on IRC seems to have an input....
Click to expand...
Click to collapse
First, you have the wrong drivers installed to run any RUU (not PC36IMG). You need Fastboot drivers, not Hboot drivers from here. (INSTALL IT TO YOUR COMPUTER).
http://www.4shared.com/get/InLGg_UI/HTCDriver300007.html
Second, you have the wrong PC36IMG file (not RUU) for your Hboot 2.10.
Either one of these files should work for you to unroot since they each have the same Hboot 2.10.
http://shipped-roms.com/download.ph...15.00.11.19_NV_1.90_release_161482_signed.exe
http://goo-inside.me/stock/superson...15.00.11.19_NV_1.90_release_161482_signed.zip
Third, you will need those Hboot USB drivers you installed in Hboot USB to run unrevoked (the reflash program) from your computer, not recovery. Make sure when you go to Hboot USB (by clicking on Hboot in the bootloader and observing "Hboot USB" highlighted in blue, not just "Hboot" highlighted) with your phone connected to your computer, that your device manager still reads "Android Bootloader Interface", or you will have to reinstall them (in "Hboot USB").
The unrevoked reflash program (not unrevoked-forever) can be found from this link.
http://downloads.unrevoked.com/recovery/3.32/reflash_package.exe
Reboot back into your phone's operating system, then run the unrevoked program, and you should be OK.
Thanks!
I was able to flash the stock .zip and get back to stock. hboot usb shows Android Bootloader Interface. I boot into stock I enable usb debugging. My computer then tries to load drivers for new hardware "Qualcomm CDMA Technologies MSM" and the screen goes black and the phone vibrate 5 times. Any ideas?
ogp said:
Thanks!
I was able to flash the stock .zip and get back to stock. hboot usb shows Android Bootloader Interface. I boot into stock I enable usb debugging. My computer then tries to load drivers for new hardware "Qualcomm CDMA Technologies MSM" and the screen goes black and the phone vibrate 5 times. Any ideas?
Click to expand...
Click to collapse
Try pulling the battery. Can you get into the bootloader, and also, can your computer still read the phone after a battery pull and trying to boot into the bootloader or trying to boot into the operating system?
ogp said:
Thanks!
I was able to flash the stock .zip and get back to stock. hboot usb shows Android Bootloader Interface. I boot into stock I enable usb debugging. My computer then tries to load drivers for new hardware "Qualcomm CDMA Technologies MSM" and the screen goes black and the phone vibrate 5 times. Any ideas?
Click to expand...
Click to collapse
Uh-oh. You might need to end up doing this:
http://forum.xda-developers.com/showthread.php?p=21765954#post21765954

Bootloop, Recovery loop!!! ADB/FASTBOOT/HBOOT HELP!

Hey guys,
Here's the basic situation. I got this phone from a friend who knows nothing about flashing/rooting/etc. And yet he had flashed the phone with MUIU and ended in a bootloop. I fixed it for him. A month later my friend decided to flash it from Verizon to Frawg. Apparently a customer rep did the whole thing for him, long story short, it is stuck in a boot loop with the white HTC screen.
I figure the boot.img is corrupt. It also goes straight to a the white HTC screen loop whenever you select recovery or factory reset from HBOOT.
I have tried PB31IMG.zip flashing (multiple stock/recovery imgs/ROMS with no luck) - its S-ON btw.
I have tried fastboot adb which I am fairly knowledgable in, I know the environmental paths, and the drivers are correct, it all works with my other androids.
When flashing any ROM/recovery image/anything, I always get a failure message stating its missing signatures. This occurs when using fastboot recovery (path) commands to flash individual recovery images as well as the fastboot boot and fastboot update PB31IMG.zip commands.
I have tried to S-Off using HTCDEV method. But even when attempting the fastboot oem get_identifier_token I get a failure bootrom message <bootrom> [ERR] Command error!!!
RUU is no luck... even charged it says I have less than 30%battery error, when I get it to work after erasing cache on adb, it will say resetting bootloader, and once it has reset the phone, the phone ends up connecting via USB with a black screen as CDMA technologies to my pc. RUU then says USB has been disconnected. I can only access the USB driver while in HBOOT and FASTBOOT.
So basically the microsd flash method, adb flash method, and RUU are no goes at this point unless there's something I am doing wrong (I have been researching so many different forums, and discussions and have found a handful like my situation with no solution.
This is a last cry before I render my friends phone a paperweight. Thank you for anything! :good:
SPECS:::
INCREDIBLEC XC SHIP S-ON
HBOOT-0.92.0000
MICROP-0417
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.10.07.07
JULY 23 2010,10:06:51
ragus15 said:
Hey guys,
Here's the basic situation. I got this phone from a friend who knows nothing about flashing/rooting/etc. And yet he had flashed the phone with MUIU and ended in a bootloop. I fixed it for him. A month later my friend decided to flash it from Verizon to Frawg. Apparently a customer rep did the whole thing for him, long story short, it is stuck in a boot loop with the white HTC screen.
I figure the boot.img is corrupt. It also goes straight to a the white HTC screen loop whenever you select recovery or factory reset from HBOOT.
I have tried PB31IMG.zip flashing (multiple stock/recovery imgs/ROMS with no luck) - its S-ON btw.
I have tried fastboot adb which I am fairly knowledgable in, I know the environmental paths, and the drivers are correct, it all works with my other androids.
When flashing any ROM/recovery image/anything, I always get a failure message stating its missing signatures. This occurs when using fastboot recovery (path) commands to flash individual recovery images as well as the fastboot boot and fastboot update PB31IMG.zip commands.
I have tried to S-Off using HTCDEV method. But even when attempting the fastboot oem get_identifier_token I get a failure bootrom message [ERR] Command error!!!
RUU is no luck... even charged it says I have less than 30%battery error, when I get it to work after erasing cache on adb, it will say resetting bootloader, and once it has reset the phone, the phone ends up connecting via USB with a black screen as CDMA technologies to my pc. RUU then says USB has been disconnected. I can only access the USB driver while in HBOOT and FASTBOOT.
So basically the microsd flash method, adb flash method, and RUU are no goes at this point unless there's something I am doing wrong (I have been researching so many different forums, and discussions and have found a handful like my situation with no solution.
This is a last cry before I render my friends phone a paperweight. Thank you for anything! :good:
SPECS:::
INCREDIBLEC XC SHIP S-ON
HBOOT-0.92.0000
MICROP-0417
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.10.07.07
JULY 23 2010,10:06:51
Click to expand...
Click to collapse
Try this ruu its the newest officially signed ruu, so it will work with s-on. http://dinc.does-it.net/Stock_Images/4.08.605.15/PB31IMG.zip Place it on your sdcard in no folders and boot to hboot. It should find the file and prompt to press vol up to install. If it errors or dosent find it backup and format your sdcard fat32 with a pc and try again.
The reason the fastboot identifier dosent work is because you need to be on the 1.02 or 1.07 hboot to be able to unlock it. The ruu above will give you 1.07.
From there you can unlock the bootloader, fastboot flash recovery, and flash su thru recovery, then you will be rooted. Then if desired you can downgrade and get s-off.
I'm having a similar problem, but after using the PC-side RUU program, the PC reported the installation as failed while the phone hung on black screen with a full progress bar and 'htc', along with a single exclamation point at the end of the bar. When I unplugged the phone from the computer, it returned to the HBOOT screen where there were a number of phone elements and 'OK' in blue text, above a partition error and write failed message.
I did a battery pull to try the RUU's 'advanced recovery', and the phone now no longer boots.
I have no idea what shenanigans this is. No kernel screen, HBOOT is inaccessible, no charging light while plugged in, I've tried different SD cards and without any... I can't get it to respond at all.
Halp?
Trygon said:
I'm having a similar problem, but after using the PC-side RUU program, the PC reported the installation as failed while the phone hung on black screen with a full progress bar and 'htc', along with a single exclamation point at the end of the bar. When I unplugged the phone from the computer, it returned to the HBOOT screen where there were a number of phone elements and 'OK' in blue text, above a partition error and write failed message.
I did a battery pull to try the RUU's 'advanced recovery', and the phone now no longer boots.
I have no idea what shenanigans this is. No kernel screen, HBOOT is inaccessible, no charging light while plugged in, I've tried different SD cards and without any... I can't get it to respond at all.
Halp?
Click to expand...
Click to collapse
Sorry but it sounds like the phone is bricked, and unrecoverable. If it wont boot, or boot to hboot, there really is no way to even try anything. Does it turn on at all?
cmlusco said:
Sorry but it sounds like the phone is bricked, and unrecoverable. If it wont boot, or boot to hboot, there really is no way to even try anything. Does it turn on at all?
Click to expand...
Click to collapse
Holy cow, props on the quick reply. You're pretty much confirming my fears. I've tried a few combinations of battery and usb connections, but there's no vibration nor ADB signal.
I can't say I've ever seen a stock utility behave this way, so user beware. It's also worth noting that I have no history on this phone's modifications - Just that it was S-ON and locked when I got it, in bootloops between kernel and ROM, and attempting to access recovery looped it too.
cmlusco said:
Try this ruu its the newest officially signed ruu, so it will work with s-on. Place it on your sdcard in no folders and boot to hboot. It should find the file and prompt to press vol up to install. If it errors or dosent find it backup and format your sdcard fat32 with a pc and try again.
The reason the fastboot identifier dosent work is because you need to be on the 1.02 or 1.07 hboot to be able to unlock it. The ruu above will give you 1.07.
From there you can unlock the bootloader, fastboot flash recovery, and flash su thru recovery, then you will be rooted. Then if desired you can downgrade and get s-off.
Click to expand...
Click to collapse
Good news and bad news,
Good news: upgrade worked, and I was able to unlock the boot-loader via HTCDEV.
Bad news: I can flash recoveries all day long, boot images, etc via fast-boot and it shows the bars when flashing on my phone. But when I click recovery, I still get a white HTC splash screen. I think that the NV.img was messed up being that they flashed Frawg or Straight talk over to the network. What can I do? As far as I know there is no way for me to S-OFF, am I softbricked? Maybe there is a way to repair the kernel? IDK, any suggestions at this point would be amazing.
ragus15 said:
Good news and bad news,
Good news: upgrade worked, and I was able to unlock the boot-loader via HTCDEV.
Bad news: I can flash recoveries all day long, boot images, etc via fast-boot and it shows the bars when flashing on my phone. But when I click recovery, I still get a white HTC splash screen. I think that the NV.img was messed up being that they flashed Frawg or Straight talk over to the network. What can I do? As far as I know there is no way for me to S-OFF, am I softbricked? Maybe there is a way to repair the kernel? IDK, any suggestions at this point would be amazing.
Click to expand...
Click to collapse
The ruu should have flashed a correct nv img. Have you tried flashing amon ra recovery, or did you see if you could access the stock recovery after you did the ruu?
cmlusco said:
The ruu should have flashed a correct nv img. Have you tried flashing amon ra recovery, or did you see if you could access the stock recovery after you did the ruu?
Click to expand...
Click to collapse
I can retry the RUU to make sure it was correctly downloaded. After the 1st RUU attempt, I still had a straight to white htc screen loop when choosing the recovery. I have tried Clockwork, stock, and Amon Ra recoveries via the fastboot flash recovery recovery.img method and also the fastboot boot recovery.img methods.
ragus15 said:
I can retry the RUU to make sure it was correctly downloaded. After the 1st RUU attempt, I still had a straight to white htc screen loop when choosing the recovery. I have tried Clockwork, stock, and Amon Ra recoveries via the fastboot flash recovery recovery.img method and also the fastboot boot recovery.img methods.
Click to expand...
Click to collapse
Did you try erasing recovery before flashing?
fastboot erase recovery
Then
fastboot flash recovery recovery.img
Can you boot to the os or no?
cmlusco said:
Did you try erasing recovery before flashing?
fastboot erase recovery
Then
fastboot flash recovery recovery.img
Can you boot to the os or no?
Click to expand...
Click to collapse
I have tried fastboot erase recovery followed by the flash and still get the white HTC image. I am not able to boot the os... i get white HTC splash image over and over, and the USB driver that tries to mount to my desktop in the bootloop is not Android 1.0, it is CMDA technologies. I have no idea what that is or if that has to do with the previous frawg/straight talk flash attempts.

[Q] Bricked- 3 Vibrates, LED flash on boot. Hboot 2.10, amonRA working - Please help!

Hey everyone.. any help on this would be greatly appreciated, has caused a lot of stress.
The phone was successfully downgraded to hboot 2.10 from hboot 2.18 a while back, s-off was achieved, all things were working perfectly with gingerbread roms and the sort.
I decided I wanted an ICS rom as my main boot-up, but was having difficulties installing it and finding a cooperable kernal/radio to get it to flash..
(looking back this probably wasn't the real issue as to why the ROM wouldn't load, and this base ICS rom that I was drawn to was not at all the one I should have been getting conclusion/direction from)
Anyways, I see now that I was trying to flash an Evo V 4G ICS rom, and in install this rom led me to update an EVO V 4g radio.
This was the rom I was trying to install:
http://androidforums.com/evo-v-4g-a...om-harmonia-3-17-17nov12-ics-sense-3-6-a.html
And in reading up on that lead me to this link
http://androidforums.com/evo-v-4g-all-things-root/648747-update.html
where I flashed the 'OTA_Shooter_ICS_35_S_Sprint_WWE_VM_1.14.652.0-1.13.652.2_release_291083f0wrax77ry0w073p' update.
Soon thereafter I found myself back with S-ON (previously was s-off), with no roms able to install.
I can get adb/sd functionallity in fastboot/hboot and have amonRA 2.3 installed as my recovery that I can get too.
In fact, in amonRA gingerbread roms say they install correctly, and I also have a nandroid backup of 'system' 'restore' 'data' 'cache' 'boot' which I believe I performed before the radio update.
They both say installed/updated correctly (new rom flash/nandroid), but upon rebooting the system, the evo 4G just vibrates 3 times, flashes its LED, and that's it. Blank screen - nothing.
Please, any help on this?
To sum it up:
I flashed the above incompatible radio in attempt to get a rom working which on foresight was for the EVO V 4G instead of the EVO 4G.
Upon doing this my hboot stayed the same (2.10), but it reverted my from S-OFF back to S-ON.
Confusing enough my radio on the hboot menu says '2.15.00.08.08', which is the latest EVO 4G radio according to here:
http://forum.xda-developers.com/showthread.php?t=715485
Hboot 2.10 USB boots fine with vol down + power, have ADB capabilities to it, and recovery boots fine to amonRA.
Much thanks in advance, I really want to get this running again!
echoedge said:
Hey everyone.. any help on this would be greatly appreciated, has caused a lot of stress.
The phone was successfully downgraded to hboot 2.10 from hboot 2.18 a while back, s-off was achieved, all things were working perfectly with gingerbread roms and the sort.
I decided I wanted an ICS rom as my main boot-up, but was having difficulties installing it and finding a cooperable kernal/radio to get it to flash..
(looking back this probably wasn't the real issue as to why the ROM wouldn't load, and this base ICS rom that I was drawn to was not at all the one I should have been getting conclusion/direction from)
Anyways, I see now that I was trying to flash an Evo V 4G ICS rom, and in install this rom led me to update an EVO V 4g radio.
This was the rom I was trying to install:
http://androidforums.com/evo-v-4g-a...om-harmonia-3-17-17nov12-ics-sense-3-6-a.html
And in reading up on that lead me to this link
http://androidforums.com/evo-v-4g-all-things-root/648747-update.html
where I flashed the 'OTA_Shooter_ICS_35_S_Sprint_WWE_VM_1.14.652.0-1.13.652.2_release_291083f0wrax77ry0w073p' update.
Soon thereafter I found myself back with S-ON (previously was s-off), with no roms able to install.
I can get adb/sd functionallity in fastboot/hboot and have amonRA 2.3 installed as my recovery that I can get too.
In fact, in amonRA gingerbread roms say they install correctly, and I also have a nandroid backup of 'system' 'restore' 'data' 'cache' 'boot' which I believe I performed before the radio update.
They both say installed/updated correctly (new rom flash/nandroid), but upon rebooting the system, the evo 4G just vibrates 3 times, flashes its LED, and that's it. Blank screen - nothing.
Please, any help on this?
To sum it up:
I flashed the above incompatible radio in attempt to get a rom working which on foresight was for the EVO V 4G instead of the EVO 4G.
Upon doing this my hboot stayed the same (2.10), but it reverted my from S-OFF back to S-ON.
Confusing enough my radio on the hboot menu says '2.15.00.08.08', which is the latest EVO 4G radio according to here:
http://forum.xda-developers.com/showthread.php?t=715485
Hboot 2.10 USB boots fine with vol down + power, have ADB capabilities to it, and recovery boots fine to amonRA.
Much thanks in advance, I really want to get this running again!
Click to expand...
Click to collapse
You're going to need to upgrade your device to the latest available RUU version (4.67.651.3), unlock your bootloader with HTCDev, flash a custom recovery, root your device, and then downgrade your misc partition (again). That should normalize your device (if one of the earlier steps doesn't do it).
echoedge said:
Hey everyone.. any help on this would be greatly appreciated, has caused a lot of stress.
The phone was successfully downgraded to hboot 2.10 from hboot 2.18 a while back, s-off was achieved, all things were working perfectly with gingerbread roms and the sort.
I decided I wanted an ICS rom as my main boot-up, but was having difficulties installing it and finding a cooperable kernal/radio to get it to flash..
(looking back this probably wasn't the real issue as to why the ROM wouldn't load, and this base ICS rom that I was drawn to was not at all the one I should have been getting conclusion/direction from)
Anyways, I see now that I was trying to flash an Evo V 4G ICS rom, and in install this rom led me to update an EVO V 4g radio.
This was the rom I was trying to install:
http://androidforums.com/evo-v-4g-a...om-harmonia-3-17-17nov12-ics-sense-3-6-a.html
And in reading up on that lead me to this link
http://androidforums.com/evo-v-4g-all-things-root/648747-update.html
where I flashed the 'OTA_Shooter_ICS_35_S_Sprint_WWE_VM_1.14.652.0-1.13.652.2_release_291083f0wrax77ry0w073p' update.
Soon thereafter I found myself back with S-ON (previously was s-off), with no roms able to install.
I can get adb/sd functionallity in fastboot/hboot and have amonRA 2.3 installed as my recovery that I can get too.
In fact, in amonRA gingerbread roms say they install correctly, and I also have a nandroid backup of 'system' 'restore' 'data' 'cache' 'boot' which I believe I performed before the radio update.
They both say installed/updated correctly (new rom flash/nandroid), but upon rebooting the system, the evo 4G just vibrates 3 times, flashes its LED, and that's it. Blank screen - nothing.
Please, any help on this?
To sum it up:
I flashed the above incompatible radio in attempt to get a rom working which on foresight was for the EVO V 4G instead of the EVO 4G.
Upon doing this my hboot stayed the same (2.10), but it reverted my from S-OFF back to S-ON.
Confusing enough my radio on the hboot menu says '2.15.00.08.08', which is the latest EVO 4G radio according to here:
http://forum.xda-developers.com/showthread.php?t=715485
Hboot 2.10 USB boots fine with vol down + power, have ADB capabilities to it, and recovery boots fine to amonRA.
Much thanks in advance, I really want to get this running again!
Click to expand...
Click to collapse
have you tried running a RUU yet? it should restore your phone back to stock radio hboot system and a few other things
Okay, I will try to get the latest RUU up and running.
I see them listed here
http://wiki.rootzwiki.com/HTC_EVO_4G_Downloads
but all the links are dead -- will look for a mirror right now.
I see there are three different methods for flashing the RUU - an update.zip I can flash in amonRA, a PC36IMG I can flash in hboot and an radio.img file I can do in fastboot adb..
I also find a .exe file
RUU_SuperSonic_GB_Sprint_WWE_4.67.651.3_Radio_2.15.00.12.19_NV_2.33_release_234563_signed.exe
but it's an .exe file?
and they all seem to differentiate in size from a like 10mg PC36IMG to a 220mb version as the .exe is..
so many different choices, what's my best option for the situation
Thanks a bunch for the quick replies!
echoedge said:
Okay, I will try to get the latest RUU up and running.
I see them listed here
http://wiki.rootzwiki.com/HTC_EVO_4G_Downloads
but all the links are dead -- will look for a mirror right now.
I see there are three different methods for flashing the RUU - an update.zip I can flash in amonRA, a PC36IMG I can flash in hboot and an radio.img file I can do in fastboot adb..
I also find a .exe file
RUU_SuperSonic_GB_Sprint_WWE_4.67.651.3_Radio_2.15.00.12.19_NV_2.33_release_234563_signed.exe
but it's an .exe file?
and they all seem to differentiate in size from a like 10mg PC36IMG to a 220mb version as the .exe is..
so many different choices, what's my best option for the situation
Thanks a bunch for the quick replies!
Click to expand...
Click to collapse
The RUU is run from the PC while you're in fastboot mode. That'll work fine. Or you can use the PC36IMG from here and flash in HBOOT (bootloader).
Cool, thanks.
Okay, I downloaded the .zip and .exe-- ended up using Captain's link to HBoot the RUU by renaming it to PC36IMG.zip
So then booted up in hboot, it detected the PC36IMG -- went through the list.. check, check, check, check, completed and done.
Rebooted the phone, now instead of just a black screen with the 3 vibrations and led flashes, it goes to the "EVO 4G" white screen loader, then 5-10 seconds later, goes blank and does the 3 vibration thing again.
Back to HBoot.
Noticed the only change was the radio oversion now says 2.15.00.11.19 now
So now my next step is to do the HTCDev method I assume?
Fastboot USB'd- phone detected by W7 just fine.
I type in 'fastboot devices' and it detects the phone and gives the serial number, so fastboot seems to be in working order.
I then type in the command 'fastboot oem get_identifier_token'
and am getting the error
C:\Android>fastboot oem get_identifier_token
... INFO[ERR] Command error !!!
OKAY [ 0.008s]
finished. total time: 0.008s
Click to expand...
Click to collapse
and seem to be stuck here.. tried re-installing my htc sync, redid the get_identifier_token command and the same error persists.
Any suggestions?
echoedge said:
Cool, thanks.
Okay, I downloaded the .zip and .exe-- ended up using Captain's link to HBoot the RUU by renaming it to PC36IMG.zip
So then booted up in hboot, it detected the PC36IMG -- went through the list.. check, check, check, check, completed and done.
Rebooted the phone, now instead of just a black screen with the 3 vibrations and led flashes, it goes to the "EVO 4G" white screen loader, then 5-10 seconds later, goes blank and does the 3 vibration thing again.
Back to HBoot.
Noticed the only change was the radio oversion now says 2.15.00.11.19 now
So now my next step is to do the HTCDev method I assume?
Fastboot USB'd- phone detected by W7 just fine.
I type in 'fastboot devices' and it detects the phone and gives the serial number, so fastboot seems to be in working order.
I then type in the command 'fastboot oem get_identifier_token'
and am getting the error
and seem to be stuck here.. tried re-installing my htc sync, redid the get_identifier_token command and the same error persists.
Any suggestions?
Click to expand...
Click to collapse
What does your bootloader screen say? S-ON or S-OFF? What are your HBOOT and radio versions? Because it doesn't sound like the zip file finished installing. It should reboot once during the process, and then continue on flashing for around 10 minutes. Did it do that?
Captain_Throwback said:
What does your bootloader screen say? S-ON or S-OFF? What are your HBOOT and radio versions? Because it doesn't sound like the zip file finished installing. It should reboot once during the process, and then continue on flashing for around 10 minutes. Did it do that?
Click to expand...
Click to collapse
Yes, it did that.. went through all the checkmarks with success down to WiMax I believe was the last one.
It did reset once during the process.. I remember because I was confused, didn't know if it turned off or what, then it turned itself back on, continued with the process and installed the rest of it.
The only thing that changed was the radio version from 2.15.00.08.08 to 2.15.00.11.19 after the RUU/Hboot/PCIMG36 img flash.
Bootloader says... I'll type it all out
SUPERSONIC EVT2-3 SHIP S-ON
HBOOT-2.10.0001
MICROP-041f
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.00.11.19
Oct 15 2010, 12:07:00
Click to expand...
Click to collapse
Should I try re-flashing again using the .exe file, does everything seem right on the bootloader?
Okay, I think I might have put the wrong PC36IMG file directing towards 11.19
(too many files in my Downloads folder )
Lemme try again.. I see the radio version should be 12.19, which is what Captain's link provided
Okay, I used the proper 12.19 PCIMG36 file this time,
now the bootloader says
*** LOCKED (OOW) ***
SUPERSONIC EVT2-3 SHIP S-ON
HBOOT-2.18.0001
MICROP-041f
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.00.12.19
Dec 21, 2011, 12:50:32
Click to expand...
Click to collapse
Looks like it's back to its original state
I'm assuming it works now, still updating as I type this, will try the token and the other steps to get it back down to 2.10 with s-off and back to where it should be
Thanks for the help guys.
I'll let you know if it works, I'm assuming it will and I know the steps to perform at this stage.
One more question though which got me into this original mess,
do I need to update the kernal/radio/anything in order to get an ICS rom loaded on the Evo 4G?
Or was that issue mute just because I was trying to flash an Evo V 4g/incompatible rom?
Thanks again!!
Okay.. all is going well, but there seems to be something strange going on, don't think it's normal.
After I flashed superuser, I restarted it and it once again went to the black screen with the 3 vibrations.
Took out the battery, put it back in, powered on. Booted to sprint stock.
Enabled USB debugging/disabled Fast Boot.
Then put the USB in, and the notification sound popped up on my computer detecting the phone.. but the phone itself did nothing. It isn't even charging (battery indicator at top stays still).. my settings are set to 'charge only' and 'pop-up and ask me' on connection settings.
Pressed power button, went to restart, and it powered down and again went to black screen with the three vibrations.
Took the battery out, put it back in, turned it on.. went back to sprint stock.
Plugged USB cable in again-- same thing, no pop-up on phone that it's connected, although my computer notifies me that it is.
Tried on two different computers with different USB cables, no luck.
ADB shell doesn't work, no devices found if I try it anyways.
Help
Thanks
echoedge said:
Okay.. all is going well, but there seems to be something strange going on, don't think it's normal.
After I flashed superuser, I restarted it and it once again went to the black screen with the 3 vibrations.
Took out the battery, put it back in, powered on. Booted to sprint stock.
Enabled USB debugging/disabled Fast Boot.
Then put the USB in, and the notification sound popped up on my computer detecting the phone.. but the phone itself did nothing. It isn't even charging (battery indicator at top stays still).. my settings are set to 'charge only' and 'pop-up and ask me' on connection settings.
Pressed power button, went to restart, and it powered down and again went to black screen with the three vibrations.
Took the battery out, put it back in, turned it on.. went back to sprint stock.
Plugged USB cable in again-- same thing, no pop-up on phone that it's connected, although my computer notifies me that it is.
Tried on two different computers with different USB cables, no luck.
ADB shell doesn't work, no devices found if I try it anyways.
Help
Thanks
Click to expand...
Click to collapse
Just as I suspected. Your misc partition is corrupted, causing your sd card to not be recognized, and ADB to be broken. I've been there before, and this is fixable. First, to get your SD card working, you'll need to boot into fastboot (so that your display reads FASTBOOT USB), and from the command prompt on your computer, from the folder where your fastboot.exe resides, type the following command (taken from here - thanks to Calkulin):
Code:
fastboot oem enableqxdm 0
After that completes, boot into recovery. I'd like to check and see if adb will work in recovery - that'll be easier than the alternative, which is flashing a ROM with Wireless ADB enabled, and using those commands to flash the misc partition from the computer. After you get recovery booted, type
Code:
adb devices
at the command prompt and let us know if your device shows up in recovery mode.
Tried going back into hboot.. plugged it in,
was detected, but had to re-install drivers on my w7 machine I noticed.
after i figured out that hboot usb worked, went to recovery, went to restart now.
went to black screen and noticed it is vibrating 5 times now (before it was 3)
took out battery, turned back on, back to sprint stock. still no usb capabilities within the rom.
btw my bootloader now says
** unlocked **
s-on
hboot-2.18.0001
radio-2.15.00.12.19
also,
tried going back into recovery, and re-flashed the superuser file. installed fine.
this time instead of going to 'reboot now' went to shut down.. it shut down fine. I turned it back on, turned on fine.
It only seems to be doing the black-screen and 5 vibrations when I reboot.
Tried plugging it in again to pc, checked settings - nothing.
Am confused now, not sure what's wrong
EDIT:
okay, just read Capt. Throwback's reply AFTER posting this, will give that ago. Thanks CT
Captain_Throwback said:
Just as I suspected. Your misc partition is corrupted, causing your sd card to not be recognized, and ADB to be broken. I've been there before, and this is fixable. First, to get your SD card working, you'll need to boot into fastboot (so that your display reads FASTBOOT USB), and from the command prompt on your computer, from the folder where your fastboot.exe resides, type the following command (taken from here - thanks to Calkulin):
Code:
fastboot oem enableqxdm 0
After that completes, boot into recovery. I'd like to check and see if adb will work in recovery - that'll be easier than the alternative, which is flashing a ROM with Wireless ADB enabled, and using those commands to flash the misc partition from the computer. After you get recovery booted, type
Code:
adb devices
at the command prompt and let us know if your device shows up in recovery mode.
Click to expand...
Click to collapse
I remember having to do that command because my SD card wasn't detected before I flashed the RUU and making this thread.
This is because it was very noticable my SD card wasn't being detected.. any PC36IMG file in hboot wouldn't be detected, and recovery wouldn't mount nor find an sd card. After doing that command above the SD card worked.
But anyways, ADB worked in hboot and I successfully did that command.
ADB did not work in recovery unfortunately.
Are you sure it's an issue of my sd card being detected? My misc partition is probably corrupted I assume which is giving me these errors, but SD card even before doing that above command in hboot and recovery worked fine (was able to browse my sd card/mount it.. flashed superuser on it. I only say that because before when I had to do that command to get the SD working in the beginning of all this the SD card had no access to anything at all, and in recovery would give me a can't mount mnt/mmc*** (or something like that).., that's when I googled the error and found that solution that Calkulin provided.
But i'm not sure.. what are my options now?
echoedge said:
I remember having to do that command because my SD card wasn't detected before I flashed the RUU and making this thread.
This is because it was very noticable my SD card wasn't being detected.. any PC36IMG file in hboot wouldn't be detected, and recovery wouldn't mount nor find an sd card. After doing that command above the SD card worked.
But anyways, ADB worked in hboot and I successfully did that command.
ADB did not work in recovery unfortunately.
Are you sure it's an issue of my sd card being detected? My misc partition is probably corrupted I assume which is giving me these errors, but SD card even before doing that above command in hboot and recovery worked fine (was able to browse my sd card/mount it.. flashed superuser on it. I only say that because before when I had to do that command to get the SD working in the beginning of all this the SD card had no access to anything at all, and in recovery would give me a can't mount mnt/mmc*** (or something like that).., that's when I googled the error and found that solution that Calkulin provided.
But i'm not sure.. what are my options now?
Click to expand...
Click to collapse
You're going to need to flash a ROM with Wireless ADB enabled, or manually use Terminal Emulator to flash the misc partition, as per the instructions in my "Downgrade HBOOT" thread. If you still have the flash_image and mtd-eng.img on your SD card, Terminal might be the easiest way to do it (hopefully it'll let you). If not, we'll have to go the Wireless ADB route, as I did here.
Okay, i'm not sure if it worked or not.
I su'd into terminal and did the commands.
the terminal froze though so I had to take the battery out, but that was after I pressed enter on the three commands..
I noticed in my bootloader it says *** LOCKED ***
and it also says I'm S-OFF..
Now I'm trying to flash over the 11.19 radio PC36IMG.zip but now it seems the bootloader is not detecting my sd card..
I tried the command to get sd working again. That worked okay.
I booted into recovery, and my sd card is mounted and in there I can browse my SD card contents.
But in hboot it tries to detect the PC36IMG.zip and just passes it by.
Did the misc partition commands work properly, what's messing with it now?
I'm still able to ADB/fastboot USB in hboot by the way, it just isn't detecting my PC36IMG file.
Should I try to manually do it, or am I missing something?
Also I booted into the sprint stock rom, plugged in the USB and now that functionality is working fine.. prompts up, charge only, etc.
Seems I'm almost there... :fingers-crossed:
echoedge said:
Okay, i'm not sure if it worked or not.
I su'd into terminal and did the commands.
the terminal froze though so I had to take the battery out, but that was after I pressed enter on the three commands..
I noticed in my bootloader it says *** LOCKED ***
and it also says I'm S-OFF..
Now I'm trying to flash over the 11.19 radio PC36IMG.zip but now it seems the bootloader is not detecting my sd card..
I tried the command to get sd working again. That worked okay.
I booted into recovery, and my sd card is mounted and in there I can browse my SD card contents.
But in hboot it tries to detect the PC36IMG.zip and just passes it by.
Did the misc partition commands work properly, what's messing with it now?
I'm still able to ADB/fastboot USB in hboot by the way, it just isn't detecting my PC36IMG file.
Should I try to manually do it, or am I missing something?
Click to expand...
Click to collapse
If you're back to S-OFF, you might be okay. Try flashing the 4.67 PC36IMG.zip in HBOOT again. After you do that, you should still be S-OFF, if everything is working properly, and hopefully everything else will be working too.
It's also possible that the misc partition flash was incomplete. Since you're now S-OFF, and presumably ADB is working, you should be able to run the commands over USB.
Okay, I had to put in a bigger SD card for it to detect the PC36IMG to detect- installed perfectly.
Also had to reflash amonRA recovery.
I was already S-OFF for whatever reason so yup, after that I was good to go! :good:
Booted to recovery, made a backup, wiped data/factory reset, an flashed an ICS rom. Just booted up, everything is working great
Thanks a bunch everyone (esp Capt. Throwback) for getting this resolved quick and painlessly
Am very relieved to get this working once again as normal, wasn't sure if I would be able
Thanks again!!

[Q] Stuck At Recovery

Hi,
I always power off my phone at night and yesterday morning it booted to recovery so I thought that I must had pressed the vol key but it was frozen, removed/replaced the battery, booted into recovery again, still frozen.
Pressing the volume keys won't change the selection, pressing power will not make the device do anything. I believe that it is somewhat working because HBOOT will change to HBOOT USB PLUG when plugging it.I can also see it looking for "P98IMG" for a little moment.
If I connect it to my PC, it will be detected as "Android 1.0". I did install the drivers as specified at : http://forum.xda-developers.com/showthread.php?t=737728 I have Androik SDK installed & working (I am a developer).
The phone is detected by fastboot as :
HT12NTZ00637 fastboot
but I was not able to do anything with it.
Code:
fastboot reboot
rebooting...
finished. total time: 0.000s
The phone doesnt do anything
Code:
fastboot -w
erasing 'userdata'...
FAILED (status malformed (1 bytes))
finished. total time: 0.000s
I've discovered Ace Think Tank post while searching the forums : http://forum.xda-developers.com/show....php?t=1824379
I was running ViperDHD1.1.0 if it makes any difference.
Thanks for helping me out.
HTC Desire HD (Telus)
ACE PVT SHIP S-OFF
HBOOT-0.85.0007
MICROP-0438
RADIO-26.06.04.06_M
eMMC-boot
Oct 11 20120, 12:47:02
Tried to put PD98IMG.zip from this post on my SD : http://forum.xda-developers.com/showpost.php?p=20203105&postcount=5
It looks like the phone is trying to install it however once the "blue loading bar" finishes, I see all the folder such as bootloader, boot, recovery, system, ... but it has been displaying this for 4 hours now. I thought it could take a while but I really doubt that this is every gonna finish.
Any help?
SOuellet said:
Tried to put PD98IMG.zip from this post on my SD : http://forum.xda-developers.com/showpost.php?p=20203105&postcount=5
It looks like the phone is trying to install it however once the "blue loading bar" finishes, I see all the folder such as bootloader, boot, recovery, system, ... but it has been displaying this for 4 hours now. I thought it could take a while but I really doubt that this is every gonna finish.
Any help?
Click to expand...
Click to collapse
well, it seems that you failed to read...why being S-OFF you flashed a RUU? was that RUU froyo? Sounds like you might have messed the bootloader.
glevitan said:
well, it seems that you failed to read...why being S-OFF you flashed a RUU? was that RUU froyo? Sounds like you might have messed the bootloader.
Click to expand...
Click to collapse
First, I'm going to thank you for being the only person to try to answer but it seems that you did failed to read too as the phone was stuck in HBOOT before I tried this out. If I remove the SD card, the phone will act the same as described earlier as the install does nothing.
Any other suggestions?
SOuellet said:
First, I'm going to thank you for being the only person to try to answer but it seems that you did failed to read too as the phone was stuck in HBOOT before I tried this out. If I remove the SD card, the phone will act the same as described earlier as the install does nothing.
Any other suggestions?
Click to expand...
Click to collapse
Why not flashing a rom from recovery? If your phone is not flashing anything in fastboot or hboot, then might be a hardware issue.
Sent from my GT-N7000 using xda app-developers app
glevitan said:
Why not flashing a rom from recovery?
Click to expand...
Click to collapse
I wish I could go into recovery but I'm stuck into HBOOT and to quote myself :
Pressing the volume keys won't change the selection, pressing power will not make the device do anything
Click to expand...
Click to collapse
SOuellet said:
I wish I could go into recovery but I'm stuck into HBOOT and to quote myself :
Click to expand...
Click to collapse
have you tried navigating without the sdcard?? power the device off and take the sdcard out...then boot in hboot..
glevitan said:
have you tried navigating without the sdcard?? power the device off and take the sdcard out...then boot in hboot..
Click to expand...
Click to collapse
Yes I did, I am no SIM, no SD, even tried a different SD...
SOuellet said:
Yes I did, I am no SIM, no SD, even tried a different SD...
Click to expand...
Click to collapse
You mean that you can not move in hboot nor select anything? then it seems to be a hardware issue...
glevitan said:
You mean that you can not move in hboot nor select anything? then it seems to be a hardware issue...
Click to expand...
Click to collapse
Exactly, pressing vol up / vol up / power buttons won't make the selection change. The display will change from HBOOT to HBOOT USB PLUGwhen plugging/removing USB cable tho so it's not completely frozen...
In the mean time, I have been trying to do a couple things, like fastboot update bleh.zip but it'll give
Code:
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
I thought that I could try flashing with a RUU so I got this file :
http://goo.im/ruu/RUU_Ace_Sense30_S...60.29_26.14.04.28_M_release_225512_signed.exe
but it doesn't work. If I remove/replace the battery from the phone and plug it in the USB, my PC will not find any drivers for my phone and it'll be detected as "Android Phone", trying to run the RUU will fail because it will not recognize the phone. If power it up before trying the RUU, it will say that my battery is less than 30% even if the green led (fully charged) was on.
Any ideas or maybe I'm just doing something wrong?
Thanks a lot for taking the time to help me out.
Found the Telus image T : http://shipped-roms.com/download.ph...60.25_26.10.04.03_M_release_194001_signed.exe
extracted recovery.img as another post points out but no success so far, after typing this command :
Code:
fastboot flash recovery recovery.img
my cpu stays at 100%, and even after 2 hours and got no feedback whatsoever.
trying to update using fastboot update telus.zip will result in :
Code:
Whoops: didn't find expected signature
read_central_directory_entry failed
╗±ýpïð7'@=z«▼Gñ▼äò̪¦╝WDÙh¬Ð秬)↓ø┌温§h█←àV*PѲ╠╗[ø×e┐§¨v╗ÚY}╬áDƒ▒ýrÙ®│E█¸ÄÝÐþ\
é·\ËÜÈ⌂▓☼ÐÌõ╬PO↑pm5üå饧sÌéä]ÚâÍ▒á▼ÈØ░▼üÐ↑ggGÊè¯ãÿuÛ¸0uÁ¿Ã¾´Éë♠S%¹ ¸÷u$,gRÛÐ─3X/
═ÀE╬⌂¢↕J▄½u'LÃoáK▀Ò¥L8┴rÞ/³┌öò©7qg▀⌂¢r÷ñxrX²o¦ÆDGb8Ê☼ï■ÍÁóSR¶q¥8A_YƒKË?♦´å(E¹╩ðÄ
î/█t¬÷³4yÛ÷*←█├9▒}®Ò´m4s▓║╝Ã]╬¨ÞÞH¼
ܨXâ¨'
Yes, all the weird chars were outputted to console.
I also copied the zip to my SD, renamed it to PD98IMG.ZIP but it looks like doing the same at the other ROM I've tried earlier, the blue progress bar will complete, then when a "directory parsing" appears, it will stays there _forever_.
Hope these details can help you find a solution.
Since I haven't found any solutions yet, I am willing to offer a monetary compensation if anyone can help.
would appreciate if somebody can help, i've exactly the same problem here
Have you (both) flash a froyo RUU or ENG S-OFF and you were running Gingerbread?
I was running ICS (ViperDHD 1.1.0) and I wasn't able to flash anything as it freezes as explained in previous posts.
What happens if you just try running the RUU in hboot? I mean, connecting your phone to the computer and running the exe.
SOuellet said:
I was running ICS (ViperDHD 1.1.0) and I wasn't able to flash anything as it freezes as explained in previous posts.
Click to expand...
Click to collapse
Sorry, have you also tried with the sim card out?
Question :
sashank said:
What happens if you just try running the RUU in hboot? I mean, connecting your phone to the computer and running the exe.
Click to expand...
Click to collapse
Answer :
SOuellet said:
I thought that I could try flashing with a RUU so I got this file :
http://goo.im/ruu/RUU_Ace_Sense30_S...60.29_26.14.04.28_M_release_225512_signed.exe
but it doesn't work. If I remove/replace the battery from the phone and plug it in the USB, my PC will not find any drivers for my phone and it'll be detected as "Android Phone", trying to run the RUU will fail because it will not recognize the phone. If power it up before trying the RUU, it will say that my battery is less than 30% even if the green led (fully charged) was on.
Click to expand...
Click to collapse
I also did try a Telus image : http://shipped-roms.com/download.ph...60.25_26.10.04.03_M_release_194001_signed.exe
Maybe Ì'm just doing it wrong? or wrong image? or ...
glevitan said:
Sorry, have you also tried with the sim card out?
Click to expand...
Click to collapse
Yep, tried to flash w/ SIM, w/o SIM, w/ SD, w/o SD (from PC)
It seems to always give the same result...
SOuellet said:
Question :
Answer :
I also did try a Telus image : http://shipped-roms.com/download.ph...60.25_26.10.04.03_M_release_194001_signed.exe
Maybe Ì'm just doing it wrong? or wrong image? or ...
Click to expand...
Click to collapse
If you are S-OFF and have superCID, any RUU should be flashing. I am afraid that it can be a hardware issue...
glevitan said:
If you are S-OFF and have superCID, any RUU should be flashing. I am afraid that it can be a hardware issue...
Click to expand...
Click to collapse
Wow, quick reply.
I believe that I am S-OFF as it is displayed at the top of the screen : ACE PVT SHIP S-OFF. I don't really know about the superCID.
When looking for one of my previous posts to quote myself, I figured that I didn't explicitly said that when I plugged my phone turned off in my PC, I had no drivers for "Android Phone". If powered on, it will use the Google ADB drivers.

[Q] DHD woes

Hi all,
Been having problems with my DHD for ages now - got myself a GS3 after a while so had kind of given up on it but now I really want to get it back to life as a backup (and for a temp replacement for my gf who got her phone driven over yesterday!). I've seen loads of similar problems to mine, but after searching here for months and following several soutions to one point or another, I always seem to get some kind of error that no-one else is getting and from there it branches off into new problems/methods. Kind of getting sick of going in circles so here I am asking for some DHD justice!
The problem is this:
A few months back the DHD started freezing/restarting intermittently (something to do with Sense I think, but tried the goldcard method of rooting it a few weeks before which failed, not sure if this could have affected things but it didnt seem to have any noticable effect for a while anyway) then eventually got either stuck in a loop on the carriers logo animation or hanging at the white background/green HTC logo screen. Couldn't get any further. Did a factory reset but the problem persisted. After a few weeks I came back to it and found that very occasionally I could get the phone to start up and get on the home screen. I can do a few things (like enabling USB debugging luckily) there but get DOZENS of notifications that various processes are failing and eventually the phone reboots or jumps to the HTC logo screen again. Either this happens before I can do very much on the phone or some process fails and nothing happens. So really I need a solution thats mostly PC based - but pretty much every program or command line operation fails to actually see the phone. I'm assuming here what I need to do it flash a new ROM to replace what I also assume is a corrupt existing one? I've tried RUU .exe type fixes - which don't see the phone. Most of the command line instructions fail to see the phone either. The phone isn't rooted so I'm guessing this would need to be done to flash a new ROM (a working version of the stock one would be fine for what I need it for but having a custom one would be nice). I've got nowhere with trying to flash ROMs as is (not rooted, S-ON), and also nowhere with various root/s-off tools. TBH I'm not really sure which stage of the process I need to be trying first. The other day the phone suddenly booted ok without the notifications and worked for around 6 hours before something made it reboot and return to the boot loop.
On the HBOOT screen I have the following:
ACE PVT SHIP S-ON RL
HBOOT-0.85.0024
MICROP-0438
RADIO-26.09.04.28_M2
eMMC-boot
Trying to boot into recovery just gets me the red triangle screen. Trying a new image from SD doesnt work as it doesnt see the card mounted.
Thanks for taking the time to read my tale of woe. Anyone got an idea where to start with this?
MerkyBlud said:
Hi all,
Been having problems with my DHD for ages now - got myself a GS3 after a while so had kind of given up on it but now I really want to get it back to life as a backup (and for a temp replacement for my gf who got her phone driven over yesterday!). I've seen loads of similar problems to mine, but after searching here for months and following several soutions to one point or another, I always seem to get some kind of error that no-one else is getting and from there it branches off into new problems/methods. Kind of getting sick of going in circles so here I am asking for some DHD justice!
The problem is this:
A few months back the DHD started freezing/restarting intermittently (something to do with Sense I think, but tried the goldcard method of rooting it a few weeks before which failed, not sure if this could have affected things but it didnt seem to have any noticable effect for a while anyway) then eventually got either stuck in a loop on the carriers logo animation or hanging at the white background/green HTC logo screen. Couldn't get any further. Did a factory reset but the problem persisted. After a few weeks I came back to it and found that very occasionally I could get the phone to start up and get on the home screen. I can do a few things (like enabling USB debugging luckily) there but get DOZENS of notifications that various processes are failing and eventually the phone reboots or jumps to the HTC logo screen again. Either this happens before I can do very much on the phone or some process fails and nothing happens. So really I need a solution thats mostly PC based - but pretty much every program or command line operation fails to actually see the phone. I'm assuming here what I need to do it flash a new ROM to replace what I also assume is a corrupt existing one? I've tried RUU .exe type fixes - which don't see the phone. Most of the command line instructions fail to see the phone either. The phone isn't rooted so I'm guessing this would need to be done to flash a new ROM (a working version of the stock one would be fine for what I need it for but having a custom one would be nice). I've got nowhere with trying to flash ROMs as is (not rooted, S-ON), and also nowhere with various root/s-off tools. TBH I'm not really sure which stage of the process I need to be trying first. The other day the phone suddenly booted ok without the notifications and worked for around 6 hours before something made it reboot and return to the boot loop.
On the HBOOT screen I have the following:
ACE PVT SHIP S-ON RL
HBOOT-0.85.0024
MICROP-0438
RADIO-26.09.04.28_M2
eMMC-boot
Trying to boot into recovery just gets me the red triangle screen. Trying a new image from SD doesnt work as it doesnt see the card mounted.
Thanks for taking the time to read my tale of woe. Anyone got an idea where to start with this?
Click to expand...
Click to collapse
1. S-off your device
2. Use android flasher
3. AND easily flash flash recovery thorough this software....
Sent from my HTC Desire HD using xda premium
MaratabHashmi said:
1. S-off your device
2. Use android flasher
3. AND easily flash flash recovery thorough this software....
Sent from my HTC Desire HD using xda premium
Click to expand...
Click to collapse
S-off requires rooting it first, am I right? Not having much luck with that - HTC Quickroot claims its been done but none of the apps such as SuperUser are present when it reboots...
Suggestions anyone? efforts to S-OFF not working so far...:fingers-crossed:
You don't need to root if all you want to do is run a RUU. Are you trying to do it through ADB or fastboot? Is the RUU you're trying compatible with your phone's region?
bananagranola said:
You don't need to root if all you want to do is run a RUU. Are you trying to do it through ADB or fastboot? Is the RUU you're trying compatible with your phone's region?
Click to expand...
Click to collapse
I'm trying running the .exe file from the pc, I'm 99.9% sure its the correct region (3UK stock). It gets as far as bringing up a screen with a grey HTC logo while the PC says 'waiting for bootloader' before I get an error message saying the USB connection is lost (tried 3 different cables and there is no issue with faulty cables, or either end being unplugged, ). ADB doesnt see the phone as connected. Fastboot doesnt seem to do much as usually when the phone reboots as part of the process it freezes or goes back into bootloop. I've tried putting ROMs on the sd card and updating from the recovery menu but the phone doesnt see the card as mounted in this mode (when it does boot and run ok for a few minutes it does eventually see the card).
I'm confused. You have a recovery menu? Is your phone's bootloader unlocked?
Sorry, I mean the menu accessed through power on + vol down. No, tried unlocking it through the HTC site but no joy.
That's the bootloader. What procedure are you using for fastboot?
Via ADB commands - havent tried with fastboot methods recently though so I forget which particular guide I was using. I'm sure there are all kinds of noob alarms and flashing lights going off somewhere
You cannot run a RUU from adb. Only fastboot.
Where do I start with this then? I have the fastboot pc files installed already but didn't get anywhere, seem to remember the phone rebooting from a command and then just going back to the logo bootloop before it could progress - very possibly doing something wrong though.
Update: Tried the following:
Ran the RUU.exe until the wizard comes up. While the RUU wizard was open, found the temporary folder it created.Found ROM.zip. Opened it, extracted recovery.img. Put it in the location where Android SDK tools is installed. Booted the phone into bootloader, gone to FASTBOOT USB. Opened a command prompt, navigated to the folder with Android SDK tools. Entered:
fastboot flash recovery recovery.img
BUT still getting an error: "'fastboot' is not recognized as an internal or external command, operable program or batch file." :S
MerkyBlud said:
Where do I start with this then? I have the fastboot pc files installed already but didn't get anywhere, seem to remember the phone rebooting from a command and then just going back to the logo bootloop before it could progress - very possibly doing something wrong though.
Update: Tried the following:
Ran the RUU.exe until the wizard comes up. While the RUU wizard was open, found the temporary folder it created.Found ROM.zip. Opened it, extracted recovery.img. Put it in the location where Android SDK tools is installed. Booted the phone into bootloader, gone to FASTBOOT USB. Opened a command prompt, navigated to the folder with Android SDK tools. Entered:
fastboot flash recovery recovery.img
BUT still getting an error: "'fastboot' is not recognized as an internal or external command, operable program or batch file." :S
Click to expand...
Click to collapse
You need to change to the correct folder on your PC where your fastboot.exe file is, thats why your getting your error.
Why you trying to flash stock recovery? Unless I missed it, From what I can see on your posts your still s-on, so you can't flash anything like that from fastboot anyway.
Sent from my GT-I9505 using xda app-developers app
The error you're getting is that your computer can't find the fastboot file. It's not an error from fast out itself. Open the folder with fastboot in it, shift-rightclick, and choose "open command window here." Also, I thought you were running a RUU, not actually using fastboot to flash images. If you want to flash stuff you need to unlock bootloader.
bananagranola said:
The error you're getting is that your computer can't find the fastboot file. It's not an error from fast out itself. Open the folder with fastboot in it, shift-rightclick, and choose "open command window here." Also, I thought you were running a RUU, not actually using fastboot to flash images. If you want to flash stuff you need to unlock bootloader.
Click to expand...
Click to collapse
Yeah, I was initially trying to run the RUU.exe but that method wasn't working as I mentioned, so I tried extracting the rom it created and flashing that via fastboot.(Didn't know that shift/rightclick thing, thanks). As for s-off I haven't found a way of doing that without rooting, hence why I thought I couldn't get anywhere without rooting the phone first.
When I try and unlock the bootloader ( at http://www.htcdev.com/bootloader/ruu-downloads) , it wants to update the HBOOT first, this is how far I get with the process:
"BEFORE beginning the Unlock Bootloader process your product requires that you update the ROM to the version listed in the table below first, then download the RUU next to it to enable the unlocking capability.
To install the RUU, simply follow these instructions:
On your phone, enable USB debugging. (From the Home screen, MENU > Settings > Applications > Development > Check USB debugging)
Connect your phone to the computer using the USB cable that came with your phone. Wait a moment for your computer to identify your phone, this may take a few minutes. After your computer has found your phone, double click on the RUU to start the process"
I get as far as bringing up a screen with a grey HTC logo while the PC says 'waiting for bootloader' before I get an error message saying the USB connection is lost (so exactly the same problem trying to update the HBOOT as trying to run the RUU.exe) so I'm not sure how I'm going to unlock the bootloader if this method isn't working - direct .exe method doesnt work, and the process I need to unlock the bootloader so I can flash via fastboot doesnt work for the same reason.
Have you tried booting into bootloader and choosing fastboot before trying the RUU?
Yep. Same USB connection error despite having 'FASTBOOT USB' showing....
Type "fastboot devices." What does it say? Do you have your drivers from HTC Sync installed?
Hi all, had the phone working ok for a while, it wanted to do a software update which froze at 12%, however after cancelling it the phone seems to be problem free. Dont really get this as surely the incomplete update wouldnt take..? but something must have changed. The phones been ok for over a week now although I havent rebooted it or let the battery run flat...still dont trust it entirely!

Categories

Resources