[solved] Radio_V2 failure - Desire Q&A, Help & Troubleshooting

Ok, I bought this phone from market in June means that I am not bound to any operator or carrier. I have Hboot 0.92 and radio 5.09.05.30_2
I have rooted this phone long time before, and because of rooting, I couldn't update my phone when phone checks for operating system updates periodically.
Now I tried to update my phone to latest available ROM here (Froyo (2.09.405.8) update - Windows not required). I renamed and copied the zip file in formatted card (only that .zip file in whole card) and tried to update my phone.
Everything seems to go fine but they went down the hill when RADIO_V2 starts to update. I get this error.
RADIO_V2 - Fail-PU
...
...
Partition update fail!
Update fail!
Now since the update is failure so I can't use my phone now. If I normal restart it then phone just hangs on HTC logo with 7 vibrations
Any suggestions?

Ok, now I have new problem:
Now I get either a white screen (as below) where neither of the buttons seem to work or a black screen with HTC logo in the middle with exclamation marks in the four corners of the screen.
**Screenshot is attached in the post because I can't use external URL due to account restrictions for new account.**

Going to have to bite the bullet and run an RUU...get it here:
http://shipped-roms.com/shipped/Bra...00.32U_5.09.05.30_2_release_142828_signed.exe
Boot into FASTBOOT (hold back button and press power) and once connected via USB (FASTBOOT USB on screen) run the RUU...should get you back to normal, albeit with wiped data

Thanks Eddie for your reply.
I tried this but the green update bar gets an exclaimation sign, and I see Error 110. I have downloaded this file many times in case if I have corrupt download problem.

anyone? or is my phone dead?
Edit: solved the problem..thanks everyone

Hi, can you please detail how you got the phone back to life?
Thanks!

If you've fixed the issue you need to let people know how you did it so future issues can be resolved for other users...

Hi, I have exactly the same issue and am wondering how you managed to fix it! Please let us know

oombongo said:
anyone? or is my phone dead?
Edit: solved the problem..thanks everyone
Click to expand...
Click to collapse
Hi,
I have the same issue , how did you fix it ??
Anyone??? please help ...

i hate it when people just make the questions just to do their job.
as long as you made it work you should post the steps to help others in similar conditions as you were.
think about it cause this is a community. we don't expect from HTC or others to help us but WE do expect from eachother!!!

sorry for my late reply. I wasn't visiting this forum and Internet much due to some problems in life.
Ok, here is what I did:
1. You MUST, MUST and MUST use x86 operating system. If you are using 64-bit then you are screwed.
2. 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.
Hopefully it helps

1. Not true, I've got Windows 7 x64 and can run RUUs without issues

I have Windows 2008 RC2 x64 and I had problems with it. The phone wouldn't update. The update progress bar was stopping at 70% or something

Might be an issue with the Server version...

Thanks! I'll try that...

I recently had a problem with a very new Desire on Orange UK - PVT4 - S-ON, hboot 0.93. I didnt have an orange sim and wanted to use my O2 sim. The sim worked when unlocked (my wife paid for an unlock code), but the wifi and data simply wouldnt work (seems to be a common problem)
Basically, I tried to write a new rom but kept digging myself deeper and deeper into a big black hole of bricked phone...
Eventually, after unsuccessfully trying to root, unlock, use a goldcard, use unrevoked 3 and downgrade to android 2.1 I ended up with a black screen with exclamation marks in each corner. I could only use RUU exe files to flash, so I started flashing random ROMS.
Each time it would fail with the green status bar flashing red, the phone vibrating and when it finally failed, I'd unplug the USB and see the screen saying it'd failed at step 2.
I looked for the most recent ROM I could find, and came across this one:
www dot mediafire dot com/?bbb7m2b4t5jejhm (i cant post external links)
RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00.32U_5.11.05.27_release_159811_signed.exe
It worked! I now have a totally unbranded froyo, with newer radio and still have S-ON (which seems to be impossible!) and all my data (wifi + cellular) works fine
I really dont know what I did to get to this point, but everything I did failed. I'm hoping that this post might help someone with a newer Orange UK branded Desire, but since I'm writing it all down a couple of days after I fixed it, i'm not sure how helpful it will be!
At least the wife's happy now she has her new phone working (and i can go back to my simple world of HD2 + wp7 + nandroid)

i did same but no luck
check
http://forum.xda-developers.com/showthread.php?t=1000385&page=10
please help me.
P.S : Sorry, i know this is old thread.

any other sollution!!
i tried this but no luck
i've same problem withHTC from Orange UK also but didn't work for me
radio_v2 fail-pu
thx
j0ff said:
I recently had a problem with a very new Desire on Orange UK - PVT4 - S-ON, hboot 0.93. I didnt have an orange sim and wanted to use my O2 sim. The sim worked when unlocked (my wife paid for an unlock code), but the wifi and data simply wouldnt work (seems to be a common problem)
Basically, I tried to write a new rom but kept digging myself deeper and deeper into a big black hole of bricked phone...
Eventually, after unsuccessfully trying to root, unlock, use a goldcard, use unrevoked 3 and downgrade to android 2.1 I ended up with a black screen with exclamation marks in each corner. I could only use RUU exe files to flash, so I started flashing random ROMS.
Each time it would fail with the green status bar flashing red, the phone vibrating and when it finally failed, I'd unplug the USB and see the screen saying it'd failed at step 2.
I looked for the most recent ROM I could find, and came across this one:
www dot mediafire dot com/?bbb7m2b4t5jejhm (i cant post external links)
RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00.32U_5.11.05.27_release_159811_signed.exe
It worked! I now have a totally unbranded froyo, with newer radio and still have S-ON (which seems to be impossible!) and all my data (wifi + cellular) works fine
I really dont know what I did to get to this point, but everything I did failed. I'm hoping that this post might help someone with a newer Orange UK branded Desire, but since I'm writing it all down a couple of days after I fixed it, i'm not sure how helpful it will be!
At least the wife's happy now she has her new phone working (and i can go back to my simple world of HD2 + wp7 + nandroid)
Click to expand...
Click to collapse

Related

[Q] I think I've bricked my Desire - HELP PLEASE

Let me see if I can explain.
I was running Opendesire 4.0.15 (had been rooted using Revoked on a Mac).
I had modified the recovery using Revoked using amon-ra's ps3 image so I have no proper recovery.
I notices using OD Updater that OD 4.0.16 was available, downloaded that and let it flash it itself.
Now the phone doesn't boot properly, I get the O2 splash screen then what looks like a dark grey screen with very thin vertical coloured bands then back to O2 splash.
It occasionally show the Android screen but not much else.
Once it got to the setup screen with the Touch Android to begin picture and the animated finger. However there was a FC on screen and the touchscreen didn't work, so I couldn't progress.
I can get into fast boot and even the modified recovery but I can't see what to do to get a rom onto it or get it to boot up so I can re revoke it for a proper recovery.
It seems if I leave it long enough it gets to the setup screen but no touch screen working. Then it re-boots.
Can anyone suggest how to get a proper recovery file on at least??
Any help gratefully received.
Edit
From Hboot I can see
BRAVO PVT3 SHIP S-ON
HBOOT-0.83.0001
MICROP-051d
TOUCH PANEL-SYNT0101
RADIO-5.10.05.17_2
Jun 10 2010,12.12.05
So it's an SLCD then?
Please help I can't afford another phone.
Thank you.
I can see the device from fastboot, (fastboot devices lists it by it's serial number)
is there any way for get either a new rom or even just recovery onto it from this commandline?
Anyone?
Please
this is what I get, any clues?
c:\android-sdk-windows\tools>fastboot flash system od.zip
sending 'system' (65463 KB)... OKAY [ 11.219s]
writing 'system'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 20.547s
RUU see's it, (when I have it in bootloader) but when it runs through and reboots the phone, the phone sticks on an H T C screen and the pc is counting looking for bootloader but never sees it.
OK, got the HTC screen, unplugged USB, plugged it back in, ran RUU again, started uploading, green bar moving across screen, then it rebooted, waiting for bootloader, RUU then failed, black screen on phone now, no bootloader, no splashscreen nothing.
It vibrates if I hold power button, it doesn't if I hold back button or VOL down with power button.
Now it's dead.
lininjim said:
RUU see's it, (when I have it in bootloader) but when it runs through and reboots the phone, the phone sticks on an H T C screen and the pc is counting looking for bootloader but never sees it.
OK, got the HTC screen, unplugged USB, plugged it back in, ran RUU again, started uploading, green bar moving across screen, then it rebooted, waiting for bootloader, RUU then failed, black screen on phone now, no bootloader, no splashscreen nothing.
It vibrates if I hold power button, it doesn't if I hold back button or VOL down with power button.
Now it's dead.
Click to expand...
Click to collapse
what RUU did you flash it with?
sounds like you flashed it with a pre slcd screen RUU
the only O2 one I could find on here
RUU_Brav2_UK_1.20.207.1_Radio_32.36.00.28U_4.06.00.02_2_release_124865.exe
Now I can still get bootloader / fastboot working, I see it in my device manager and the fastboot command sees it again, is there anything I can do from there?
(damn thing is only 3 weeks old).
Thanks for reply btw
Managed to get a newer Froyo RUU to run to the same stage as I had before so now got a display back , hBoot 093 still for the borked recovery
is there anything I can do other than send it back to HTC?
thanks for reading, really really stuck here.
with files on sd card (pb999.img etc) it now checks those then says CID incorrect
where is it getting stuck now?
is this a branded device? (if unbranded was it branded before)
what did you flash it with?
Is your gold card present?
what os are you using to flash it?
Have you tried using the downgrade utility to flash it back to a version of 2.1? http://forum.xda-developers.com/showthread.php?t=768256
Hello again )
ok it now just goes to the white screen with the 3 androids skateboarding I have have hboot or fastboot, I don't know the significance of those.
if I select recovery it goes to amonra's poc-psfreedom so I can't even reflash it from there
it was originally an O2 UK phone so has the O2 bubbles on screen
I don't have a gold card :i(
I run a mac but I have installed xp on bootcamp to try to resolve this.
I can see the phone is device manager as Android USB Device - My HTC
It boots to the white screen now when I plug in the usb cable
it had been running happily on OpenDesire 4.0.15 with no problem, but when I called the updater to bring it to 4.0.16 it turned into this mess.
the downgrade utility requires a gold card doesn't it? I don't have one (
edit - more info
the RUU file I have tried again is
RUU_Bravo_Froy2_UK_2.14.207.1_Radio_32.44.00.32U_5.09.05.30_2_release_144166_signed.exe
it tells me it will go from image version 1.20.207.3
to image version 2.14.207.1
it starts and brings a black screen onto the phone with HTC on it, starts working then fails with erroe 171 usb connection error. (perhaps I need a different usb driver installed?)
edit again - if I unplug the usb cable I get the white screen but only RUU but pull battery and get fastboot hboot back
Hold the press
I think I've recovered it now.
Using that RUU, everytime it stalled out and said waiting for bootloader I tapped the power button and it continued, flashed the whole thing now I seem to have an official O2 Froyo!
Thanks for your input mate.
i dont know how you uninstall that psfreedom stuff, people should just buy the dongle and not risk bricking their mobile phones.
Try intalling the latest version of htc sync or use a pure windows pc rather than bootcamp see if that rectifies it.
its not hard to create a goldcard if you have a microsd slot, I do recommend you make one using the tool from modaco. and try using the downgrader. it could be that the psnation tool is conflicting the the bootloader now its .93
EDIT: was on a call mid type and posted this while you have replied.
Glad its sorted
It's sorted now, thank you.
Dongle is in the post mate.
I really appreciate your input there, I was feeling kinda lonely!
Now it's on what appears to be O2 official Froyo, means no root, DOH!
Cheers fella.
you can use the downgrader tool to downgrade hboot and firware.
then you can root and flash a rooted 2.2 405 rom like the one teppic made
it would then be on the latest 2.2 for EU and be rooted with a compatible hboot
im on hboot 93, im waiting for unrevoked. they seem to be taking an age
You are a genius, I'll have a play tonight.
Thanks mate. - SUPERSTAR -
lininjim said:
I think I've recovered it now.
Using that RUU, everytime it stalled out and said waiting for bootloader I tapped the power button and it continued, flashed the whole thing now I seem to have an official O2 Froyo!
Thanks for your input mate.
Click to expand...
Click to collapse
Hi lininjim ,
I have the same issue as you mention. i get to hboo screen and nothing works beyond that. how did you get your phone to recognize with RUU. coz mine just stays in htc logo and RUU does not recognize it at all...
Vinod
1. Posting in a thread that's one year old is not very useful.
2. Look in troubleshooting guide.
Sorry to say it worked exactly as I posted mate and I got rid of the Android phones back in March.
Sorry I can't help.

3 Mobile UK RUU Bricked. Help needed.

Hi guys, Well after trawling through the wealth of information on this site and reading till my eyes bleed I honestly cant seem to fix this.
I was hoping and preying some amazingly talented expert here could maybe point me in the right direction.
Ok so heres whats going on. Got my HTC Desire, Told me there was a system update. So I chose to install ofcourse. Then BAM! for no reason half way through installation the phone dies. Vibrates 7 times and black screen (Searched this too) - nothing.
So pulled battery, waited for a few minutes and put in, power on. Phone gets to HTC (white screen) the freezes. Or even sometimes just switches off and vibrates 7 times again!
So I found An RUU for 3 mobile - RUU_Bravo_H3G_UK_1.22.771.1_Radio_32.36.00.28U_4.06.00.02_2_release_127568_signed
Tried running it with the phone in fastboot usb
All was going well then reached about 80% and gave me an error code 110. Telling me to download a complete RUU for my device.
Now when I power on the screen is just black, however I know it still has some functionality as I can hear the sound for device connection in Windows when I Power on holding down Vol-
now I thought I would be clever and seeing as whilst my phone was working it downloaded the "correct" update. So checked the sd card and found it in the Downloads folder. Renamed it to PB99IMG and tried booting the phone holding down the back key. But still nothing.
By the way the phone isnt rooted and is very very very new. On 3 mobile UK network.
Can anybody please give me some pointers on how I may be able to go about fixing this? Im sure there has to be some way as it still has "some functionalty" (I think lol)
Also tried the adb method of connecting or re-flashing but device is not found.
Cheers all
Sounds like the RUU is corrupt - what is the file size?
Also, is that the one your Desire came with? If not, that won't work anyway
Also, an OTA shouldn't be named PB99IMG as that's only for RUU files - you rename an OTA update.zip and flash it in recovery. Looks like you've not read enough
Hi, thanks for the quick reply.
The RUU I tried installing that failed was from:
http://forum.xda-developers.com/showthread.php?t=695667
RUU_Bravo_H3G_UK_1.22.771.1_Radio_32.36.00.28U_4.06.00.02_2_release_127568_signed.exe
Filesize is 153mb. It matched the version number that my htc shipped with and even says when running the RUU that both versions are the same. But as it failed I tried the Update from my network provider that I found on the SD card by renaming to PB99IMG.zip and holding Back and Power down.
Looks like Im buggered I suppose. Im still trying to get my phones CID as Im guessing then I can install any RUU for my phone?
I just cant access anything to get the CID
The PB99IMG can ONLY be used when extracting it from an RUU
The one you got OTA (Over The Air) isn't a full ROM - it's just a 30MB-odd update
Download the RUU from here:
http://www.4shared.com/get/t2SsuYNF...sionid=2D4E782FB44E2CF020622A15F76C1A5A.dc278
(Shipped-ROMs.com can lead to corrupt downloads)
And then follow the guide I attached to this post - it's how to extract the PB99IMG from an RUU:
http://forum.xda-developers.com/showpost.php?p=10509780&postcount=102
Thank you so much! Will try now and let you know how it goes.
Thanks again
Still no good. Its tricky as I cant see the screen to select the options. But Ive followed the guide allowing it enough time to load before choosing yes etc and still no joy. Im not even sure the PBIMG99.zip is loading.
I've even tried running the RUU again from the PC after Holding vol - and Power down and waiting for the sound in windows that its connected. But gives me error code 110 again saying it cannot read files.
Loos like Im going to have to send it back to my supplier. Although Im sure they will blame me for everything and refuse me a new handset! lol
Once you have the correct PB99IMG file, you copy it onto the root of the SD card (not in any folders) and then turn the phone on holding volume down. You don't have to do anything else as it'll find the file and ask if you want to use it
To try the RUU turn the phone on holding the BACK button to get into FASTBOOT, connect to the PC and when it says FASTBOOT USB on the screen of the phone run the RUU
Out of interest, when you boot into HBOOT when info do you see at the top of screen?
Thats the problem. My screen is blank. I used to be able to get into Hboot and fastboot and see the screen. Now I dont see anything. But Im sure its still going into hboot etc as I hear the connection sound windows makes when holding vol and power.
Hope that makes sense?
Edit. I do know that before all went wrong I had hboot 93 or something like that.
Right, sounds like you've flashed a ROM for an AMOLED Desire onto an SLCD one...
Oh! poooooooh. Well thanks for trying. I never even got to use the stupid thing! lol
There is a thread on here to try and use to sort it out - look through the Q&A section
have u fixed it please ?? I got the same problems now......
thx
SK
vyeshaun said:
Hi guys, Well after trawling through the wealth of information on this site and reading till my eyes bleed I honestly cant seem to fix this.
I was hoping and preying some amazingly talented expert here could maybe point me in the right direction.
Ok so heres whats going on. Got my HTC Desire, Told me there was a system update. So I chose to install ofcourse. Then BAM! for no reason half way through installation the phone dies. Vibrates 7 times and black screen (Searched this too) - nothing.
So pulled battery, waited for a few minutes and put in, power on. Phone gets to HTC (white screen) the freezes. Or even sometimes just switches off and vibrates 7 times again!
So I found An RUU for 3 mobile - RUU_Bravo_H3G_UK_1.22.771.1_Radio_32.36.00.28U_4.06.00.02_2_release_127568_signed
Tried running it with the phone in fastboot usb
All was going well then reached about 80% and gave me an error code 110. Telling me to download a complete RUU for my device.
Now when I power on the screen is just black, however I know it still has some functionality as I can hear the sound for device connection in Windows when I Power on holding down Vol-
now I thought I would be clever and seeing as whilst my phone was working it downloaded the "correct" update. So checked the sd card and found it in the Downloads folder. Renamed it to PB99IMG and tried booting the phone holding down the back key. But still nothing.
By the way the phone isnt rooted and is very very very new. On 3 mobile UK network.
Can anybody please give me some pointers on how I may be able to go about fixing this? Im sure there has to be some way as it still has "some functionalty" (I think lol)
Also tried the adb method of connecting or re-flashing but device is not found.
Cheers all
Click to expand...
Click to collapse
The thread Eddy referred to, was probably this..You should be able to do it even if blindfolded

[Q] FOR ATTENTION OF: DROIDZONE (and anyone else!)

A few weeks ago you posted a guide on one of my threads about how to reflash my Desire using a goldcard which worked great for me and I was able to reflash and reroot my Desire - I only followed your guide up to and including Step 2. as once I had a working phone again I wan't too bothered about the additional steps to take it back to stock ROM.
Since flashing a custom ROM (LeeDroid 2.3d) and a LOT of apps on a 16gb MicroSD card, the phone worked fine. However, over the last few days it started randomly rebooting and has gotten progressively worse.
I decided to reflash back to stock again using your guide (post #14 http://forum.xda-developers.com/showthread.php?t=892064&page=2).
The process completes but there is an error on one of the steps (step 6). After the reflash the screen shows the following :-
[1] BOOTLOADER - OK
[2] RADIO_V2 - OK
[3] RADIO_CUST - OK
[4] BOOT - OK
[5] RECOVERY - OK
[6] SYSTEM - Fail-PU
[7] USERDATA - OK
[8] SPLASH1 - OK
[9] SPLASH2 - OK
Partition update fail!
Update Fail!
Do you want to reboot device?
<VOL UP> Yes
<VOL DOWN> No
Presumably, the PU in 'Fail-PU' means Partition update. The only thing is, I am flashing the PB99IMG.zip file from a goldcard as per the Droidzone guide - there is no partition on the goldcard.
Do you (or anyone else reading this) have any idea why it might be failing at step 6? The phone does actually boot up after the reflash but HTC Sense just goes into a repeated 'Force Close' loop. Is there a different ROM image I can try when using your process with the goldcard?
Since the reflash process does complete and the phone boots up (albiet with the HTC Sense 'force close' issue) I'm guessing it shouldn't be too difficult an issue to solve...I just need to know how to solve it.
I have downloaded the PB99IMG.zip file again just in case the original was corrupt, but I got the same result.
Any help or guidance you or anyone else can give is much appreciated.
Thanks,
Rich
Leave it a bit and do it again, should be fine. I had the same issue with the radio part but 30 mins later I was back to stock
Already tried
EddyOS said:
Leave it a bit and do it again, should be fine. I had the same issue with the radio part but 30 mins later I was back to stock
Click to expand...
Click to collapse
Thanks for the tip Eddy, but I've already tried a few times with no luck.
Any other ideas still welcome.
anyone?
*** BUMP ***
Still trying to fix Desire
*** bump again ***
babblerx said:
*** bump again ***
Click to expand...
Click to collapse
your best bet would be to use an exe file like this and see if that helps. Ensure that you are on a computer on which HTC sync / other android drivers have never been used before:
http://www.htc.com/au/SupportViewNews.aspx?dl_id=1048&news_id=787
is my desire dead?
I've tried to reflash my Desire several times using Droidzone's guide over the last few days. Each time I was getting the Fail-PU message at when it was trying to install the System (step 6).
However, today things took a turn for the worse...I tried reflashing using the using the .exe file via fastboot. It appeared to be working until the end when it reported a fail and dropped into the HTC rom boot screen (black with 'htc' in big letters in the middle of the screen) with a small white triangle and exclamation mark in each corner of the screen.
No matter what I try I can get to the recovery screen.
Can anyone please help????
Please don't bump threads, they'll get answered as and when someone has time
Apologies
Sorry Eddy.
I know I 'bumped' twice. Things have got worse now though....desparate for help!
babblerx said:
I've tried to reflash my Desire several times using Droidzone's guide over the last few days. Each time I was getting the Fail-PU message at when it was trying to install the System (step 6).
However, today things took a turn for the worse...I tried reflashing using the using the .exe file via fastboot. It appeared to be working until the end when it reported a fail and dropped into the HTC rom boot screen (black with 'htc' in big letters in the middle of the screen) with a small white triangle and exclamation mark in each corner of the screen.
No matter what I try I can get to the recovery screen.
Can anyone please help????
Click to expand...
Click to collapse
Try this:
press vol up and power and you get a small menu where you can delete recovery.img (assuming you're rooted).
Then install a RUU
Find your RUU here: www.shipped-roms.com
babblerx said:
I've tried to reflash my Desire several times using Droidzone's guide over the last few days. Each time I was getting the Fail-PU message at when it was trying to install the System (step 6).
Click to expand...
Click to collapse
Are you using the original USB cable shipped with your desire? I know from experience that the non-originals cause problems.
cs
That didn't work
celestialspring said:
Try this:
press vol up and power and you get a small menu where you can delete recovery.img (assuming you're rooted).
Then install a RUU
Find your RUU here: www.shipped-roms.com
Click to expand...
Click to collapse
Thanks Celestialspring, but that didn't work because after following Droidzone's original guide (to step 2) the phone isn't rooted. The only screen I can get is the black screen with with the HTC lettered logo in the middle and a triangled exclamation in each corner. The phone will recognise RUU exe's via USB from this screen, but non of the RUUs work.
Hoping you might have some other ideas.
Will I be able to do anything via ADB (not that I've used it, but willing to try just about anything now)? I've also got a goldcard, not that I can get into recovery to use it.
By the way, sorry about the duplicate post, but I don't know how to edit the original title of the thread.
babblerx said:
Hoping you might have some other ideas.
Will I be able to do anything via ADB (not that I've used it, but willing to try just about anything now)? I've also got a goldcard, not that I can get into recovery to use it.
.
Click to expand...
Click to collapse
see if the steps here solve your problem:
http://theunlockr.com/2010/06/07/how-to-unroot-the-htc-desire/
some more on the same topic using your gold card:
http://android.modaco.com/content/htc-desire-desire-modaco-com/307683/howto-unroot-your-htc-desire/
Hey did you try this??
http://forum.xda-developers.com/showthread.php?t=831734
still no joy...
celestialspring said:
see if the steps here solve your problem:
http://theunlockr.com/2010/06/07/how-to-unroot-the-htc-desire/
some more on the same topic using your gold card:
http://android.modaco.com/content/htc-desire-desire-modaco-com/307683/howto-unroot-your-htc-desire/
Click to expand...
Click to collapse
I've tried the unlockr method. The RUU shows the current image version on the phone as 2.29.405.2. The RUU exe I've tried to flash is the original T-Mobile stock (RUU_Bravo_TMO_UK_1.21.110.4_Radio_32.36.00.28U_4.06.00.02_2_release_127570_signed.exe). This appears to complete the first 4 stages of a ROM flash but then reports an error at the 'Sending' stage - ERROR [140]: BOOTLOADER VERSION ERROR.
I've also tried the above with what I believe to be the latest non branded stock rom (RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00.32U_5.11.05.27_release_159811_signed.exe) - 2.29.405.5 obviously being newer than 2.29.405.2 which RUU reports as being already on the phone. This time I get ERROR [131]: CUSTOMER ID ERROR.
I then tried the Modaco steps (your second link). This time, the RUU process went through all the steps but at the end brought up ERROR [152]: IMAGE UPDATE ERROR. This time though, the RU utility gives the option to start a 'Recover' process. There are 4 steps to the Recover process.
There is a ReadMe file available when I get error 152 which states:
4. Q: During the update, the progress bar is moving. If the error message (ERROR [150], [151]…[159]) appears, what should I do?
A: This may occur when the connection is lost, power is lost, the computer host is down, or due to other unexpected reasons. You will see some information on the Android phone’s screen. If the progress bar is moving, it means the update is processing, and your Android phone will reboot automatically and the update is successful. If your Android phone's screen shows exclamation marks in four corners, it means the update has failed. The Android phone will not be able to go into the Android screen. This problem usually can be recovered. You need to follow the instructions in the error message box, which is to reset the Android Phone and run the RUU again.
This seems to indicate the problem is to do with the connection between the phone and the PC. So I'm goning to perservere.
I have a couple of things still to try but am off to the football, I will update you later after I've tried these other things (including a different USB cable)
In the meantime, if you have any other suggestions I'd be happy to hear them. (I did look at the link in your post #14, but it refers to SLCD screens and mine is AMOLED, so reluctant to try that yet).
Thanks for the help, advice and tips so far,
Rich
babblerx said:
This seems to indicate the problem is to do with the connection between the phone and the PC. So I'm goning to perservere.
Rich
Click to expand...
Click to collapse
Did u try a different pc?
still no luck
celestialspring said:
Did u try a different pc?
Click to expand...
Click to collapse
Haven't tried a different PC yet. Have tried a different USB cable on the same PC as I've been using up to now, but that didn't work.
Will try a different PC tonight, though I don't really understand how that would work as the drivers, USB cable and ROM image will still be the same. Still going to give it a go though...at this stage I'll try just about anything.
If you've heard of any other fixes, then I'd love to hear them.
By the way, I tried the vol up and power button combo, but it didn't do anything. The only combo I know is vol down and power to bring up recovery menu. With black recovery screen with exclamation mark in each corner, none of the key combos do anything.
[UPDATE] Tried a different PC and, as I suspected, it didn't work
Rich
I think I've exhausted all options
After trying all of the hints and tips I've been given so far and a few I've found myself, I ve come to the conclusion the only way to fix the phone will be with a newer version of the ROM already installed (though I've tried one and that didn't work) or wait for an official T-mobile Gingerbread release (though I'm not sure they will do that).
It's all really annoying when all I really wanted to root for was to enable more storage on my phone - let's face it the storage space for apps on stock android phones is pathetic! If the manufacturers actually gave more storage for apps then I wouln'd feel the need to root.
Anyway, if anyone still has any (reasonable) suggestions after all of this then I'm still happy to hear them.
sorry mate, thats all I have for you.
Thanks anyway
celestialspring said:
sorry mate, thats all I have for you.
Click to expand...
Click to collapse
Cheers anyway CelestialSpring. I might wait to see if Doridzone resurfaces with any other suggestions (I've emailed him a few days ago, but no reply).
Failing that I might have to bite the bullet and send it to HTC for a (paid for,due to void warranty) fix.
Rich

[Q] HELP: Flashing with S-ON

Hello
First off: I'm not an D Inc user myself (i'm an x10) but I am trying to fix a friends verizon dInc
Second: I have tried searching for hours(plus yesterday) and have not come up with a solution.
My problem: The phone was in a bootloop that was stuck in the HTC Incredible splash screen.
Research/Tried Methods:
- I have tried hboot: it is version .92 and radio is 2.0.15 S-ON
- I have used doug piston's original BP31IMG stock rom on hboot
- Have tried RUU but won't recognize the device at all because i can't really turn the phone on
- Have tried to flash CWM recovery 2.5 and 3.0 but its just stuck on "Checking BP31IMG.zip" using hboot and still nada ( Could i be using the wrong files? )
-hboot problem: Phone finds the BP31IMG.zip checks, parses, and asks me to "Update" --> i press vol+ to yes...
I then see a blue dot on [1]Bootloader then quickly after BLACKSCREEN
The phone doesnt boot after that. I've tried it multiple times but to no avail.
Can anyone please point me to the proper steps.
Thank you very much!
-
From past experience, I know that you can use the RUU in hboot. If you haven't yet, give that a whirl.
just attempted your pointer
But now that i boot into hboot, the setup from where it left off is continuing.
EXCEPT: Radio_V2 FAILED...this doesn't sound good but scared to stop the setup
EDIT: Said Partition Update Failed
Perhaps try pulling the battery and retrying. After just throwing my own phone into hboot, I realized that it was actually fastboot that I meant to say works (first option in hboot). But if not that, I'd say something is fried. Did your friend mess up a radio update because thats a sure way to brick a phone.
Edit: After a little googling, here is something a person with a desire said fixed it for them.
http://forum.xda-developers.com/showthread.php?t=767749
KyleBS said:
Perhaps try pulling the battery and retrying. After just throwing my own phone into hboot, I realized that it was actually fastboot that I meant to say works (first option in hboot). But if not that, I'd say something is fried. Did your friend mess up a radio update because thats a sure way to brick a phone.
Edit: After a little googling, here is something a person with a desire said fixed it for them.
http://forum.xda-developers.com/showthread.php?t=767749
Click to expand...
Click to collapse
That won't work fastboot option only allow you to reboot on the Dinc...Make sure that the Pb31Img is @176mb and it should ask you to update after it reads the file
yup im sure its @176MB from doug pistons site
it did ask me to update..everything worked except radio_v2 which failed
rendering the whole update a fail
and now it wont even boot hboot :'(

Stuck on HBOOT screen :/, some help please :)

UPDATE TO MY PREVIOUS POST. I HAVE INCLUDED MUCH MORE DETAIL AS TO WHAT IS WRONG NOW. ANY HELP PLEASE?:
I am stuck in HBOOT currently, Ship s-off and of course my phone is rooted. What happened was my battery died sometime on the weekend and i tried turning it on to see the HBOOT screen. None of the buttons were responding when being pressed, not even the Vol. down + Power button was working... It randomly after a day decided to turn back on, then the next day i was at college and my battery went dead again and i'm now back at the HBOOT screen. I should have kept a check on it but i wasn't aware it would happen for a second time. Anyway...
I downloaded the PD98IMG.zip file and placed it on my goldcard (i'm on T-mobile) and attempted to re flash my device via the phone and left it for 6 hours or so whilst sleeping last night as it said it was parsing files. It sat on the same screen for the whole of the time. Tried flashing via my mac with instructions from a previous thread followed everything correct apart from putting into fastboot as i couldn't select it and thought it was worth a shot anyway Anyway, I came back with a message in terminal saying 'sending 'radio' (24960 KB)... FAILED (status malformed (1 bytes))'... As you could see it said failed. quite fed up now after looking for solutions since monday and i was hoping someone could come up with a fix :/.
If anyone knows whats going on with my DHD let me know ASAP. I am 95% sure its not bricked as its charging and turning on to HBOOT.
THANKS!!!!!
have you pulled the battery? thats what I normally do
Have you switched it back on without the charger plugged in?
Well i eventually got it working some how just after i posted this, but now it has just gone off again! It seems to be every time my battery goes completely dead. I plug it in, turn it on and Hboot screen pops up and repeats the same process each time, i dont know how to stop it doing this and i generally don't know how to get it back on.
I tried the ideas suggested but i've tried these previously and tried them again but no luck... One thing now though, my volume down button doesn't respond. If there is no fix i guess i'll just have to watch my battery usage but if anyone can suggest anything i can do to get it straight back on that would be great
I actually really need my phone to work right now , it ain't happening though, its been on hboot all day once again, it happens when the battery runs out, i press the power button and doesn't even vibrate or anything of the sort, just sits there and then pops up with the green writing after like 5 seconds saying:
SD Checking...
No image
Loading... (PD98IMG)
No image or wrong image
It says something like that, its only very briefly though. If anyone knows what i mean.... my phones on t-mobile so i made a goldcard so i could flash some roms, would that have anything to do with it?
THANKS!
Hi,
What info do you see in bootloader.
SHIP S-ON/OFF or ENG S-OFF
And have you performed Radio S-OFF?
andyharney said:
Hi,
What info do you see in bootloader.
SHIP S-ON/OFF or ENG S-OFF
And have you performed Radio S-OFF?
Click to expand...
Click to collapse
Yea i have ship s-off, which is shown. I can't press the volume buttons on the h-boot screen to scroll through menu either just to add... DO you actually have any clue what this may be?
Yeah, you've messed up your handset.
Letting your battery run completely flat will damage your battery. It shouldn't however harm your handset.
What I'd recommend doing, as you already have a goldcard, download the 1.32.405.6 PD98IMG.zip put that on your card and boot into bootloader. Follow the prompts and restore your handset.
Oh my battery is fine, i know for future reference to not let it run completely dry! will that mean i won't have the rom, which i previously flashed? Do i put the PD98IMG file on the goldcard or on my normal sd that i am currently using?
There is something wrong with your phone. When your battery dies your handset shouldn't lock you in HBOOT.
Put the PD98IMG.zip on your goldcard. You will lose everything that is not backed up.
Its your call, stay stuck in HBOOT or try to recovery it.
I'll give it a try and let you know the out come, thabks! By the way, after this wht should i do to get miui back up and running, the sme as what i previously did ?
I'll go for the recovery of course haha... Thanks anyway though, i'll give it a shot and see how it goes down . I'll let you know if i have any success!
How long does it take for it to Parse the package? it automatically started doing it so.
Update: Well I have had this going for quite some time now and its continued to show the following...
Parsing...(SD ZIP)
Bootloader
Boot
Recovery
System
UserData
Splash1
Splash2
TP
TP
TP
TP
Radio_V2
Radio_Cust
Would really appreciate any help ASAP as to why this has just been in the same position for quite some time, obviously something is not right?
Im guessing this isn't very common is it? nobody seems to know what to do
wow.. stuck in the same situation... ive rooted and unlocked my partners DHD from telus... just about a week ago, it just suddenly went to the white HBOOT screen. Since then, ive been able to somehow get into clockwork by pulling the battery out, plugging in the usb cable, then inserting the batter, it would somehow take me to the clockwork mods menu screen. I was using an outdated version tho. I would be able to reboot from that menu which would start regularly booting the phone. One interesting thing tho is that the volume - button stopped working around that time.... Ive been pulling my hair out trying to make a goldcard (did it once, but havent been able to do it since i started trying again) so i can reflash the stock telus ruu. For some reason, the goldcard program im using isnt finding the mm2... just the mm1 and mm0... any ideas why? im formating a 8gb class 4 micro sd card... fat32, ive tried 32 and 64kb sector sizes... any suggestions?
Aidanio said:
How long does it take for it to Parse the package? it automatically started doing it so.
Update: Well I have had this going for quite some time now and its continued to show the following...
Parsing...(SD ZIP)
Bootloader
Boot
Recovery
System
UserData
Splash1
Splash2
TP
TP
TP
TP
Radio_V2
Radio_Cust
Would really appreciate any help ASAP as to why this has just been in the same position for quite some time, obviously something is not right?
Click to expand...
Click to collapse
I´m in the same situation.I think the PD98IMG file don´t match with previously installed ROM (radio,hboot?)...I come from a MIUI ROM,android 2.3.4 version.
I´m proudly to inform you that I did it!
All the thing was (I think) the ROM manager who flashed a wrong recovery.
How I recovered it?
Without adb drivers,without goldcard,without downgrade.
Simply I downloaded a PD98IMG file,I unzipped it and I changed the recovery.img with a 3.0.2.6 recovery version.Ahh,I deleted the radio.img,too(I don´t know if matter or not).After this,I zipped the files again and I renamed the file to PD98IMG.Copy to sdcard,wait to process PD98IMG and finally the power and volume buttons revives!
Good bye!

Categories

Resources