Develop Bugs

[Q] Stuck in Bootloop, cannot get into recovery either.

I have searched all over and am still coming up empty on this one. Phone was working with Cyanogen earlier today, then rebooted itself and never stopped. When I try to boot into recovery it simply goes to the white evo splash screen and reboots again.
The only thing I can do is hboot/flashboot. I could not get adb shell to load at all connected to my mac. Under windows when I select flashboot it does appear on device manager under Android USB Devices->HTC Bootloader.
I have tried RUU, connection error.
I have access to both a PC and a Mac and am open to any suggestions.
SUPERSONIC EVT2-3 SHIP S-OFF
HBOOT-0.93.000
MICROP-041f
TOUCH PANEL-ATMELC03_16ac
RADIO-2.15.00.11.19
Jul 23 2010, 16:41:47

carlbeck said:
I have searched all over and am still coming up empty on this one. Phone was working with Cyanogen earlier today, then rebooted itself and never stopped. When I try to boot into recovery it simply goes to the white evo splash screen and reboots again.
The only thing I can do is hboot/flashboot. I could not get adb shell to load at all connected to my mac. Under windows when I select flashboot it does appear on device manager under Android USB Devices->HTC Bootloader.
I have tried RUU, connection error.
I have access to both a PC and a Mac and am open to any suggestions.
SUPERSONIC EVT2-3 SHIP S-OFF
HBOOT-0.93.000
MICROP-041f
TOUCH PANEL-ATMELC03_16ac
RADIO-2.15.00.11.19
Jul 23 2010, 16:41:47
Click to expand...
Click to collapse
Sounds like you wish to unroot to solve your problems? If that is the case I can promise you that with patience you can get the RUU to work. If your computer is seeing your phone then you probably have all the drivers. Try to reboot your computer and then plug your phone in, go into bootloader and select the fastboot option I believe it is, whichever one lets you make connection to your computer. I would say to use the reboot bootloader option a few times to refresh then connection then trying to run the RUU.

I've tried doing hboot usb (it changes to hboot usb plug, shows in device manager) and fastboot (it shows fastboot usb and also recognizes in device manager). Cannot get RUU to work at all, period.
Do I want to RUU? No, not really. Just trying to find any way I can get the phone back up and working.

I've never done anything in hboot except by following the recovery instructions, so I am not expert.
If I was stuck in your situation I would follow the root instructions HERE. You will have copy the files to the SD card with your windows computer if that is working. If not find one of the micro SD card adapters and use a computer to put the files on the card and use hboot to flash the new recovery.
Actually go to THIS thread and follow the instruction for via bootloader. Again, if you can't connect to the SD card through usb, take it out and put it in a computer.

Flashed that new Recovery you linked via the bootloader using the PC36IMG method, still bootloops over and over again. Can't get into recovery nor anything other than the boot loader.
Seems like it is something more serious? Bad hardware perhaps? Anything I can do from here to make it seem like the device was not rooted and swap it out at a sprint store?

Is it boot looping at the Cyanogen boot screen or at the white screen that says HTC EVO 4g? Does the hboot screen still say s-off?
If the new recovery flashed successfully it should work.
If you are highlighting recovery and then hitting power and it is bootlooping you have a problem that is over my head.

White EVO screen. Still showing S-OFF, yes. If I highlight recovery and hit power, yes.. still bootloops.

Do what fazulka reccomends and put your sd card in an adapter . Sounds like your recovery got borked,
Search for your recovery of choice
Put on root of sd card and try again
You can find a .img recovery to load up and update/flash a new one thru hboot
Swyped from a galaxy far far away......

Got the RUU to recognize the phone now. When updating it starts by rebooting to bootloader, where I get a darker screen with HTC in the middle. Then not so long after it gives me another connection error 170 and quits.
Edit: Jimdog, I have flashed a new recovery using hboot. Still gives me a bootloop.

Ran the RUU, it finally finished updating this time. Guess what? Still bootloops. Gets to the white evo screen when booting regular or to the recovery, then reboots. Every time.
Still showing S-OFF, is there any way to get this to S-ON so I can take this into a Sprint store for a swap out?

Try sprintlovers.
This may fix it.
go HERE.
The first link that says download it the one you want. When you download it it will be named PC36IMG.zip put that on the root of your sd card. Boot into recovery. Recovery will find the file and ask if you want to use it. I believe volume up is yes. There is long waits then it will ask you if you want to reboot, press up for yes
Should boot (note, first boot is LONG)
Also, it may seem like it is freezing in recovery a few time, look to the top righ and there will be a small loading bar. Some of the actions are pretty slow.

I cannot boot into recovery. It reboots over and over no matter if I try to boot normally or boot into recovery. The ONLY thing I can do is anything in hboot, i.e. flash things using a PC36IMG.
I tried flashing a new recovery, I tried flashing sprintlovers. I successfully ran a RUU even. It still bootloops during the white evo screen.
I think something is physically wrong with the phone at this point, but I am affraid since I cannot get S-ON back without flashing unrevoked in recovery that I will not be able to swap out the phone at sprint under warranty.

[Q] USB-bricked Desire

This is my first time rooting my phone and I managed to USB brick it (SD and carrier work). I've read many threads on how to fix a USB-brick Desire but I still haven't managed to fix mine. Here's what I've done:
I ran the latest Unrevoked3, which gave me root and put Clockworkmod 2.5.0.7 on the phone. I tried to go into this and run a backup but the backup failed. From my research I think this is because it's a PVT4 phone or possibly because it has HBOOT 0.93, i.e. it is a brand new Desire.
I tried to run Unrevoked again with a custom IMG which was a newer Clockworkmod, 3.0.0.5. This didn't work, when it rebooted it stayed on the fastboot screen, I eventually got through it but I was still on Clockworkmod 2.5.0.7. I cancelled out of this, after that booted and all seems fine except that USB doesn't work.
I tried following two different guides to unbricking USB, the first involved putting a special updates.zip on and applying it from recovery mode. This didn't work, I don't know why but my guess is that Clockworkmod 2.5.0.7 can't correctly apply the update onto the phone.
So far I have been unable to get adb/fastboot to work from my Linux machine, with adb running, running "adb devices" does not show it even when it's plugged in and has USB debugging on and everything. I also tried rebooting into the fastboot screen and "adb devices" still returns nothing.
I'd like (1) to get my USB back and (2) to replace Clockworkmod 2.5.0.7 with something that actually works, so that I can run a nandroid backup and eventually try other ROMs. However I'm not sure how to do this since I can't use Unrevoked and I can't seem to get fastboot to work either (am I correct in thinking that fastboot has to run over USB? or can I type fastboot commands directly into the phone?). I do seem to have root, if that makes things any easier. I'm stuck on the stock 2.2 OS.
Any help greatly appreciated.

If you want to use fastboot you need to actually use it, so not "adb" but "fastboot". Also try to follow the modaco guide on fixing usb brick.
Sent from my HTC Desire using XDA App

[Q] stock cant reboot nd recovery plz help

I did root my evo 4g hboot 2.18 radio 2.15.0012.19 and i try to downgrade but i get stock... cant do anything and i have no backup... icant get into the recovery and i cant reboot onle the htc evo 4g logo plz help to solve this problem. How Ido to fixed plz help..

eddi2004 said:
I did root my evo 4g hboot 2.18 radio 2.15.0012.19 and i try to downgrade but i get stock... cant do anything and i have no backup... icant get into the recovery and i cant reboot onle the htc evo 4g logo plz help to solve this problem. How Ido to fixed plz help..
Click to expand...
Click to collapse
Try this:
1. power down
2. remove battery
3. press and hold power button for 10 sec.
4. reinstall battery
5. press and hold the volume down button
6. press the power button to turn the phone on but DO NOT release the volume button until you can see the boot screen.
when you are in the boot screen one of the options in the list should say recovery. use the volume button to navigate down to that option and press the power button to select it. your phone should then boot into recovery and you will get the recovery screen and choices.

thanks
i did it but when i get into recovery i see the phone with the sing and then i reboot get stock in htc evo 4g logo if u have any idea how to get into the phone to flash any rom would b perfect tnx

Sounds like it could be a USB brick. This has happened to me before. I remember when that happened to me and couldn't get into recovery. For some reason when I plugged in the micro usb to the phone it would let me boot into recovery. Give that a shot and try searching usb brick. Also my sd card could not be recognized once I booted into recovery.

How did you try to downgrade?
Sent from my PC36100 using xda premium

ok well i flash 2 programs 1 flash_image 2 mtd-eng then run the pc36img but nothing happen it says cant roll back hboot n i reboot the phone n i went to the bootloader n it was locked n i try to enter to the recovery n show me the phone w/ the sing...

any idea where can i get an usb brick??

I'm not familiar with a USB brick, but I believe that your computer can still read your phone through USB. I see that you were trying to S-OFF the phone. Looks like something went wrong when you flashed the misc partition, which locked your bootloader once again.
You should try running an RUU file from your computer with your phone connected which can be found here.
http://goo.im/stock/supersonic/ruu/...15.00.12.19_NV_2.33_release_234563_signed.exe
But first, you will need to install the Fastboot drivers to your computer which can be found here
http://unrevoked.com/rootwiki/doku.php/public/revolutionary
You need to run the RUU from your phone's bootloader from FASTBOOT USB (click on Fastboot then run the RUU from your computer).
If that works, that should at least get your phone back going again (unrooted of course).

i did but w/ the ruu doesnt work too appears error 155 unknow problem n stops i dont know what else to do

Just checking, did you run the RUU in FASTBOOT USB which should have been highlighted in red from your bootloader after clicking FASTBOOT? Also, with your phone connected to your computer while in FASTBOOT USB, check your computer's device manager from the control panel and see do you see anything under Android USB devices.
And too, which PC36IMG file did you try to run?

Sounds like you tryed to downgrade your hboot to the Eng hboot. If that is what you did, then congradulations! You have successfully bricked your device! Hboots are generally NOT downgradable...especially 2.18 to eng

{ParanoiA} said:
Sounds like you tryed to downgrade your hboot to the Eng hboot. If that is what you did, then congradulations! You have successfully bricked your device! Hboots are generally NOT downgradable...especially 2.18 to eng
Click to expand...
Click to collapse
Yea, I was afraid that the wrong PC36IMG file was indeed used. Generally on the newer phones, any downgrade of the Hboot below 2.02 is a guaranteed brick. That's why Captain Throwback only recommends PC36IMG files down to Hboot 2.10 (the 2.02 ones don't work with S-ON phones). On the older hardware however, the Hboot can be downgraded to anything, including 0.76 from 2.18. I've done it on mines. You just have to know which hardware version and partition erasesize your phone has.

the one that i get from evohacks pc36img i think i need one way to flash a rom

the one i get from a post in htcevohacks
is the pc36img
if i brick my phone is there any way to unbrick

eddi2004 said:
the one i get from a post in htcevohacks
is the pc36img
if i brick my phone is there any way to unbrick
Click to expand...
Click to collapse
The best advice that I can give you is to reboot the phone into FASTBOOT USB (connect it to your computer, then go to your bootloader and click on FASTBOOT), then go back to the HTCdev site, start over and try to re-unlock your bootloader. If you can do that, then I may have a workaround for you If not, there might not be much else that you can do.

ok i did everything that u tell me n now i rename the zip (ss_stock_4.67.651) in PC36IMG n then reflash recovery-RA-supersonic-v2.3 now i can get into the recovery menu n i flash the rename (ss_stock_4.67.651) PC36IMG n i have a rom from sprint but now i still cant use adb command so what else shuld i do to recovery to normal n there r many issues that cant load like mail that is forced to sptop unexpected n thank u for all ur help!!

in the command window type:
Code:
fastboot oem enableqxdm 0and then:
Code:
fastboot reboot

eddi2004 said:
in the command window type:
Code:
fastboot oem enableqxdm 0and then:
Code:
fastboot reboot
Click to expand...
Click to collapse
Oh no. I don't know which tutorial you got those instructions from.
I'm also lost with your description of what happened. I hope you unlocked your bootloader, and can now boot into the operating system. If so, you were not suppose to rename the ss_stock_4.67 file to PC36IMG. You were suppose to flash that through RECOVERY as is. If I were you, I would go back to RECOVERY, and wipe All Factory/Reset (or whatever it says) and Dalvik-cache, then reflash the ss_stock file or another ROM.
Second, the adb commands only work from the operating system, not FASTBOOT. You need to be inside the operating system with your phone connected to your computer and USB Debugging enabled under Settings/Applications.

ok here i am
i change the name cos the bootloader let me flash the recovery amon ra 2.3 then i can see the recovery menu n i flash the rom named pc36img n give me the sprint w/ errors now i download another rom that i flash n now my computer can read the sdcard but im still locked n i dont know if im still rooted so the what i think is i have a usb brick so i need to unbrick my usb to use the adb command so i apreciate ur help w/ this thanks all of u for ur help

[Q] HTC Droid Incredible Boot Loop

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

[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!!