Related
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.
Hi.
I have a problem with my DHD, and have been browsing these forums for a solution. Im new to this so i need some confirmation, a url, and some explanation.
This happend:
I tried to root my desire HD with visionary+ r14. I did temproot, got back into the app just fine, checked for "set system r/w after root", and clicked attemt permroot. The phone booted, and got stuck in a bootloop. My Hboot menu sais S-ON on top. Tried reseting factory settings nothing helps. Since i didnt get the phone rooted, no clockword recovery installed...
Phone details:
The phone had the factory 1.32 build on it.
other info that might be valid:
Hboot: 0.85.0007
microp-0438
radio-26.03.02.26_M
eMMC-boot
oct 11. 2010
1. From searching and reading, it seems i need a RUU stock image build 1.32, can anyone provide me with an URL for the correct image?
2. Can i use the bootloader on the phone to do this? ..and how?
Hope u have some time to spare, and help this niblet :=)
Thnx for reading
PS:
Before i did this, the phone was rooted, with the same visionary pluss file. I tried to install clockword recovery mod, but it wouldnt "take". I then factory reset the phone in the android recovery menu, and the rest is listed above.
Download your RUU from here: http://xdafil.es/index.php?path=DesireHD/RUU/
How do i know i have the right drivers on the pc? Do i get those drivers from installing the HTC sync program?
sirreal1988 said:
How do i know i have the right drivers on the pc? Do i get those drivers from installing the HTC sync program?
Click to expand...
Click to collapse
If you install HTC sync (download it from their website or it is also in your sdcard unless you have not removed it ), you get all the necessary drivers...
Hm, i have installed HTC sync, but as my phone is stuck on the blackscreen and red triangle, HTC sync does not detect my phone.
When i try to run the exe file "RUU_Ace_HTC_WWE_1.32.405.6_Radio_12.28b.60.140e_26.03.02.26_M_release_155891_signed", it gives me an error [170], USB connection error.
Is there a way to run this file from the bootloader?
Try to push a PD98IMG.zip (this is stock HTC 1.32 rom from this thread unrooted, hboot s-on) to the sd card, boot into bootloader and flash "new" rom
with adb:
Code:
adb push directory/to/your/PD98IMG.zip /sdcard/
adb reboot bootloader
or if adb doesn't work, put the stock rom into the top of your sdcard, reboot the phone while holding the vol-down button.
follow the instructions on the device(normally it search for the PD98IMG.zip and ask you to install it)
How importanat is the last part of the filename of the RUU file "_2 6.03.02.26_M_release_155891_signed". As the phone is not bootable i cant check find that info on the phone anymore.
"Radio_12.28b.60.140e_2 6.03.02.26_M" it's the radio version.
At the bottom of this site is the USB Driver try it.
Thnx to both of u. Everything now working like a charm.
Good that you got it sorted. Can you edit the tag and put [solved]?
sirreal1988 said:
Thnx to both of u. Everything now working like a charm.
Click to expand...
Click to collapse
could you give me for detail how you solved this problem bro? because i have some problem like u (my dhd only black screen with red triangle warning since i was unsuccessfull root my dhd).
soni.setia said:
could you give me for detail how you solved this problem bro? because i have some problem like u (my dhd only black screen with red triangle warning since i was unsuccessfull root my dhd).
Click to expand...
Click to collapse
with an unbranded device it should be easy, download the driver and the image in the posts above, install the driver and run the exe.
On linux/unix you can download the sdk (intructions to install on the site) and then you are able to use the adb commands with the PD98IMG.img also in the posts above.
with a branded device it can be more complicated take a look at this but i don't know how far your system is online and if you are able to use adb.
As the guy above me mentioned, it's quite easy to recover your phone if it's unbranded.
Download a WWE RUU from the link someone postet before. Then boot into the bootloader and connect your DHD to your pc. If you have htc sync installed, it should recognise your phone. Then run the RUU on you pc and everything should be fine now.
hi guys i have acquired this fone from a mate. Says if i can fix it i can have it. lol won't boot just locks on htc screen.
stats are as follows
Bravo PVT3 SHIP S-ON
HBOOT-0.93.0001
MICROP-051d
TOUCH PANEL-SYNT0101
RADIO-5.11.05.27
AUG 10 2010
Apparently its from Italy(so HTC tell me in their e-mail).
Was bought from expansys
Managed to flash
RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00.32U_5.11.05.27_release_159811_signed
on it but would still do nothing. extracted the Radio from the RUU in the temp folder and tried to flash it on HBOOT still wont boot.
made a goldcard for it
is it possible to fix?
I'm a SE x10i man so this HTC stuff is pretty foreign to me.
What do you mean it does not boot?
Hangs on HTC Logo? Or What screen does it hang?
You should:
1. Install HTC SYNC
2. Then install Unrevoked USB Drivers.
Boot your phone into fastboot mode (holding down BACK+POWER, when it is turned off).
3. If it says Fastboot USB, Run the .exe for the RUU from your PC.
Then report back.
P.S. If you made a cgoldcard for it, it is recommended to run the RUU from there.
Thanks for the quick reply. Yeah hangs on the HTC logo. just came up with an error : ERROR [152]: IMAGE UPDATE ERROR
What can not be updated? The Radio? Or what part?
thats a screeny of the error. i read last night about puttin it in the freeze for 5 mins. tried it last night it worked? [email protected]#s me how :s just unplugged it and it says that the RADIO_V2 - FAIL-PU i'll try again and let ya know
ok the freezer trick worked :/ phone just did its reboot and hangs on the HTC screen again but it vibrated 8 times. :/
Try extracting the Rom.zip from the RUU. Then rename it to the PB99IMG.zip put it onto your SD card (not into folders, just to the root).
When it finds PB99IMG.zip, it starts to load it (13 secs after you press the Vol- & power key)
It gives the update/install options after 2min 20seconds (for the WWE 2.29 RUU) from the initial key press of Vol- and Power key.
FASTBOOT mode
Back+Power key:
· Bootloader (For running PB99IMG.zip)->Choose with Power key (This loads the Bootloader/Hboot mode)
in fastboot now. just selected bootloader and now its loadin the img.zip. so vol up to let it do the update?
Yes. Vol up to confirm.
RADIO_V2 Fail-PU again :/tried a 3rd time with the freezer and i got a goer. i take it as i have to reboot now?
still hangs on boot on the HTC screen. :/
Make a goldcard again (sometimes it won't work):
Use these steps.
And falsh the Rom again via the PB99IMG.zip method again.
If problem persists, try with another RUU Here.
and you should check out this method as well: http://forum.xda-developers.com/showpost.php?p=9154577&postcount=45
You need Android SDK installed on your PC and phone booted into Fastboot (FASTBOOT USB).
Maximus Rockstar said:
still hangs on boot on the HTC screen. :/
Click to expand...
Click to collapse
Before you run your update, make sure you wipe out the data and cache memories.
Seems to cure some issues.
@ Moscow Desire oes not apply for the RUU.
BTW, you did not tell me if you are using a custom recovery/rooted.
However if you said, that you've managed to flash the RUU. I think you not anymore.
hey sorry for long reply been away from PC. non rooted no recovery app installed. just about to make a new gold card and try RUU file again. if not will try another RUU then will let ya know on results.
davebugyi said:
@ Moscow Desire oes not apply for the RUU.
BTW, you did not tell me if you are using a custom recovery/rooted.
However if you said, that you've managed to flash the RUU. I think you not anymore.
Click to expand...
Click to collapse
Believe it or not, 5 months ago, tried to update RUU (before root and custom), and it failed. (loss of wifi, b\tooth, etc). Downloaded stock froyo, failed (needed goldcard). Tried again, failed. Wiped cache's, success. Go figgure......
Okay, but as he stated before, he has no custom recovery, so no choice for that (unless with commands in fastboot).
made the gold card with the program you posted. success
attempted to download RUU's from the that link you gave me (shipped Roms) Fail partial download
downloaded a Europe Ruu. failed due to compatibility
Re-atempted to flash the Ruu i originally posted completed fine but still no boot. locks in htc screen
starting to believe this device is quietly f#$%ed. really wann beat this thing though :/
is there another website for Current RUU's that work?
Try this http://ship.ibeta.org/shipped/Bravo/
Try this: http://www.multiupload.com/LEJCW182AH
It is the same version you've flahsed
RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00. 32U_5.11.05.27_release_159811_signed
Click to expand...
Click to collapse
and
Install HTC Sync but close the sync program from taskbar before you start to use RUU. HTC Sync has drivers which you need so you have no other choice but to install it.
Click to expand...
Click to collapse
P.S. : Take out the memory card and see if it boots. And run the RUU as administrator.
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!!
Dear all,
I have been looking around the forums and downloaded a few things and looked at various solutions, but I am stuck at the first hurdle.
I have been given an htc Desire Bravo that just will not boot. I do not know how it failed originally but I can only get it into the boot screens, either the fastboot/hboot logon ot the 5 buzzes and the htc logo lock. Also it takes about 30 minutes with the battery out after every failed boot attempt to restart the boot screen.
I have run adb but it cannot tell me a cid number, I have a micro sd card in it but it does not have the pb99diag.zip on it. When I put such a file on the sd card it does not find it. Communication via adb and the phone has varied success. I suspect it is drivers and what I read is an old adb bug where server is out of date.
I have never done this before this weekend so please be gentle with me!
If I can get it to work, even to use it like a wifi tablet without phone I would be happy. I am in the UK and if we have real success I would get it on tesco PAYG
I get the "cannot find pb99diag.zip etc" dialogue when going into hboot.
The logon says
BRAVO PVT-1 SHIP S-ON
HBOOT-0.93.0001
MICROP-031d
TOUCH PANEL-SYNT0101
RADIO 5.11.05.27
AUG 10 2010, 17:52.18
Can someone suggest where to start? I have tried a number of guides on the forum but no success so far. Even just getting an os running would be success. I will be looking at this each evening so apologies if I seem slow to respond
Thanks
Adrian
First make S-Off. I forgot how but if i think right, you must it do via revolutionary, If it success, then download 4ext recovery.IMG and flash it via fastboot and reboot in bootloader in your recovery
Sent from my HTC Desire using XDA Free mobile app
battlekaier said:
First make S-Off. I forgot how but if i think right, you must it do via revolutionary, If it success, then download 4ext recovery.IMG and flash it via fastboot and reboot in bootloader in your recovery
Sent from my HTC Desire using XDA Free mobile app
Click to expand...
Click to collapse
Thank you battlekaier, I will try this out tonight when I get home and will report back.
A
ukubuntu said:
Thank you battlekaier, I will try this out tonight when I get home and will report back.
A
Click to expand...
Click to collapse
After you s off u can flash hboot the easy way but first s off.
Sent from my HTC Desire using XDA Free mobile app
If u phone does not boot then u can NOT s-off, ur phone needs to be booted.. also if ur s-on and not rooted then all u can do is flash a ruu.
Did u try factory reset from bootloader menu? Try that first, u never know but chances r ul prob need to ruu a ruu.
jmcclue said:
If u phone does not boot then u can NOT s-off, ur phone needs to be booted.. also if ur s-on and not rooted then all u can do is flash a ruu.
Did u try factory reset from bootloader menu? Try that first, u never know but chances r ul prob need to ruu a ruu.
Click to expand...
Click to collapse
Hi jmcclue,
Thanks for the comments. I can boot to the HBoot and Fastboot screens, thats how I could find the S-ON and version data. If I get it to reboot, I get either a white screen with just "htc" on it, or 5 buzzes and a screen with no life at all. I am hopeful to get it to S-OFF as I have had some communication through the usb to pc connection. I am not sure if I can do an RUU update as I don't seem to have a CID. I do not have a factory reset option on the HBOOT screen. I have tried clear storage but that has no effect. Perhaps I need the S-OFF first.
Cheers again,
A
Use the 2.3gb update ruu its wwe (world wide english) so dont worry bout cid. U can find it in bortaks troubleshooting guide in resources section and its naned 2.3.3 ruu. U will find it easy enough in google aswell. Search for "htc desire 2.3gb update" its a exe file so just boot ur phone into fastboot, plug in ur phone and run the ruu, hopefully it willvwork. Im a bit worried tho about the 5 vibrations u get, maybe a sign of hardware failure. But try that ruu anyway. And again u can not get s-off unless ur phone is fully working/booted.
jmcclue said:
Use the 2.3gb update ruu its wwe (world wide english) so dont worry bout cid. U can find it in bortaks troubleshooting guide in resources section and its naned 2.3.3 ruu. U will find it easy enough in google aswell. Search for "htc desire 2.3gb update" its a exe file so just boot ur phone into fastboot, plug in ur phone and run the ruu, hopefully it willvwork. Im a bit worried tho about the 5 vibrations u get, maybe a sign of hardware failure. But try that ruu anyway. And again u can not get s-off unless ur phone is fully working/booted.
Click to expand...
Click to collapse
Many thanks
Well that was a bit wierd
If anyone can see where I went wrong, feel free to say.
I could not seem to get the link between the phone and the pc so I removed the htc sync and restarted the pc. I could then connect to the phone in some way as abd gave a command error when I sent a fastboot oem readcid which it normally does. So leaving it in fastboot with usb I ran the wwe~.exe file and it all seemed to be doing installing. There were tens of installations going to the phone I guess each reaching 100%. Suddenly I had a web page popup in my browser s.rev2pub.com/ul_cb/player.html?a=19471543&context=c23573548&size=800x600&rt=popunder&ci=10&cb=[CACHEBUSTER] recommending I download latest drivers. The wwe ruu vanished and I have no continuing processes in Task manager that I can see.
So, should I have installed in hboot? Thankfully I can still get the phone to power on. What should happen after the exe file installs?
I am able to get some response from the phone as adb devices returns the phone device number. So I hope I can try again.
Any thoughts?
Many thanks
Revolutionary S-OFF and recovery
ukubuntu said:
Dear all,
I have been looking around the forums and downloaded a few things and looked at various solutions, but I am stuck at the first hurdle.
I have been given an htc Desire Bravo that just will not boot. I do not know how it failed originally but I can only get it into the boot screens, either the fastboot/hboot logon ot the 5 buzzes and the htc logo lock. Also it takes about 30 minutes with the battery out after every failed boot attempt to restart the boot screen.
I have run adb but it cannot tell me a cid number, I have a micro sd card in it but it does not have the pb99diag.zip on it. When I put such a file on the sd card it does not find it. Communication via adb and the phone has varied success. I suspect it is drivers and what I read is an old adb bug where server is out of date.
I have never done this before this weekend so please be gentle with me!
If I can get it to work, even to use it like a wifi tablet without phone I would be happy. I am in the UK and if we have real success I would get it on tesco PAYG
I get the "cannot find pb99diag.zip etc" dialogue when going into hboot.
The logon says
BRAVO PVT-1 SHIP S-ON
HBOOT-0.93.0001
MICROP-031d
TOUCH PANEL-SYNT0101
RADIO 5.11.05.27
AUG 10 2010, 17:52.18
Can someone suggest where to start? I have tried a number of guides on the forum but no success so far. Even just getting an os running would be success. I will be looking at this each evening so apologies if I seem slow to respond
Thanks
Adrian
Click to expand...
Click to collapse
Hey Adrian, I had the same problem as you did, hopefully I can be of help.
First, like everyone else is saying you will need S-OFF.
To do this head to this site on your PC revolutionary.io hit download for windows or Linux or whatever your pc is running, then you will need to fill out information about your device (see attached screenshot). Device, HBoot number, and serial number, (the serial number can be found behind the battery of your device). Once you have done that, click "Generate Key". it will give you a key, remember it or write it down.
Then, open the file that was downloaded, and extract the contents to your documents and Run the revolutionary( should look like the screenshot attached). Plug your device in (assuming you have the drivers) and it should ask you to enter the beta key we had before. Enter that and hit enter. it will then S-off your Desire and soon ask if you would like to install a custom recovery. hit Y and then enter, once that is finished, unplug your device and in HBoot go to "Recovery". Now you can flash a ROM of your choice.
Hopefully I made sense!
Best of luck
Neibaf97 said:
Hey Adrian, I had the same problem as you did, hopefully I can be of help.
First, like everyone else is saying you will need S-OFF.
To do this head to this site on your PC revolutionary.io hit download for windows or Linux or whatever your pc is running, then you will need to fill out information about your device (see attached screenshot). Device, HBoot number, and serial number, (the serial number can be found behind the battery of your device). Once you have done that, click "Generate Key". it will give you a key, remember it or write it down.
Then, open the file that was downloaded, and extract the contents to your documents and Run the revolutionary( should look like the screenshot attached). Plug your device in (assuming you have the drivers) and it should ask you to enter the beta key we had before. Enter that and hit enter. it will then S-off your Desire and soon ask if you would like to install a custom recovery. hit Y and then enter, once that is finished, unplug your device and in HBoot go to "Recovery". Now you can flash a ROM of your choice.
Hopefully I made sense!
Best of luck
Click to expand...
Click to collapse
Thank you Neibaf97
Can I confirm that I can do this from the HBOOT screen or the fastboot screen? Also where jmmclue said if I can't boot then I can't S-Off, does that mean boot to the HBOOT screen or into Android? Then if I want to load say WWE, do I put that on a microSD to get it to recover?
thanks again
A
ukubuntu said:
Thank you Neibaf97
Can I confirm that I can do this from the HBOOT screen or the fastboot screen? Also where jmmclue said if I can't boot then I can't S-Off, does that mean boot to the HBOOT screen or into Android? Then if I want to load say WWE, do I put that on a microSD to get it to recover?
thanks again
A
Click to expand...
Click to collapse
He means into android.
Sent from my HTC Desire using XDA Free mobile app
lilsafbig said:
He means into android.
Sent from my HTC Desire using XDA Free mobile app
Click to expand...
Click to collapse
Thanks lilsafbig, that was a little too ambiguous to understand, but I have a few developments.
I am able to communicate to some degree with adb between phone and pc. Before I was unable to get anything back but now with the right syntax I have got back the CID as HTC_001 and the device number. But when I run revolutionary from the fastboot USB screen the revolutionary continues to wait for the device to show. Is it likely that USB degugging was off prior to the failure, is there a way to get it on. I suggest this as when I connect it to my pc it recognizes the device and shows in the device manager as an htc unspecified device (this is progress). As I cannot boot android it does not show as an additional drive in file manger. when I try some of the fastboot oem commands I get bad command errors, whilst fastboot getvars is ok. Could this be why I cannot get revolutionary to S-OFF!
Thanks
additional info, when usb is in an in fastboot usb, the device manager sees it as android 1.0
ukubuntu said:
additional info, when usb is in an in fastboot usb, the device manager sees it as android 1.0
Click to expand...
Click to collapse
also tried "fastboot oem writecid 11111111" and got "FAILED(remoteartition is not existed).."
ukubuntu said:
also tried "fastboot oem writecid 11111111" and got "FAILED(remoteartition is not existed).."
Click to expand...
Click to collapse
So..... does this mean I am bricked?
BUMP!
ukubuntu said:
So..... does this mean I am bricked?
Click to expand...
Click to collapse
If you can still get to bootloader / fastboot screen, then you are rarely ever bricked.
1. Ignore anything and everything to do with revolutionary and fastboot for now. I'm afraid the first few posts while trying to be helpful have been misleading. Get your phone booting up into Android OS first, i.e. into a stock ROM using an RUU
2. Use the 2.3.3. GB RUU, nothing else, it doesn't need a goldcard or care about CID etc.
3. Download it from the bottom here, then use Bortak's troubleshooting guide stickied to the top of Q&A, Point [7] to run it as a PB99IMG.zip from the root of your sdcard. That way you don't need to run it through USB or care about what drivers are installed.
Thank you Eddie, I will try that. I did try flash a PB99IMG.zip before with no success but I will try again.
I found it here Official Stock Sense Gingerbread_v1.2 GB-2.3.3_A2SD – http://androidba.se/J7 for desire (neophyte)
I hope it can work out ok. I guess I format the sd card to fat32 not ext4
Will let you know how it goes.
Thanks,
A
ukubuntu said:
Thank you Eddie, I will try that. I did try flash a PB99IMG.zip before with no success but I will try again.
I found it here Official Stock Sense Gingerbread_v1.2 GB-2.3.3_A2SD – http://androidba.se/J7 for desire (neophyte)
I hope it can work out ok. I guess I format the sd card to fat32 not ext4
Will let you know how it goes.
Thanks,
A
Click to expand...
Click to collapse
That's a custom rom.
Here's the link for the 2.3.3 ruu.
http://www.theandroidsoul.com/downl...uu-now-to-update-to-to-the-latest-android-os/
Sent from my HTC Desire using XDA Free mobile app
ukubuntu said:
I did try flash a PB99IMG.zip before with no success but I will try again.
I found it here Official Stock Sense Gingerbread_v1.2 GB-2.3.3_A2SD – http://androidba.se/J7 for desire (neophyte)/
Click to expand...
Click to collapse
That did not work because the file is not an RUU...it is a stock rooted custom ROM with A2SD (the clue is in the name). It is designed to flashed in recovery like any other ROM. Renaming it to PB99IMG.zip won't do anything.
Use the actual shipped roms RUU link provided.
Reformat your sdcard to a single FAT32 partition if necessary, then follow Method [7] of the guide, place only the PB99IMG.zip on the root of the sdcard (not in any folder)