Seeing as this is a old phone, which had to be replaced two times, I figured I may as well do something with it.
Its old, and the issues were so bad, that it just became unusable. I had to pay full price for my new Droid Bionic because this flaming bag of you know what was still under contract. The Dinc only had a 1 year warranty for replacement(I guess?) which had camera issues with the first, and this second had some MAJOR rebooting issues. It got so insanely hot it made the serial number, model number all that, come off the back of it. As I said, I got a new phone which is GREAT.
The issues with this old Dinc is:
1)rebooting loop, it WILL NOT enter the phone menus(main screen, etc). It will stay at the "HTC Incredible" white screen and just self-reboot over and over until it runs out of battery power.
2)I have replaced the battery, it did nothing for it.
3)In the HBoot menu, Factory reset, recovery does nothing(info for all those versions there will be posted later in this post).
4)I have all of the HTC/Android usb drivers installed, it does not pick up anything. No SD cards(if it does at that point?), nothing, but the Hboot menu does say "HBOOT USB" at the top.
HBoot information below
Code:
INCREDIBLEC XD SHIP S-ON
HBOOT-0.92.0000
MICROP-0417
TOUCH PANEL-ATMELC03_16ac
RADIO-2.15.00.07.20
JUL 23 2010, 18:06:51
was hard to read this small text, but there ya go.
Keep in mind, I CANNOT even get past the "HTC Incredible" white screen too turn on USB debugging. I have tried alot of methods, nothing has seemed to work. I'm starting to think I should have some fun with this thing, take it out back.
Also, I have never rooted, changed roms, flashed or anything to this phone. I don't do that to phones I am using, but seeming as this phone is not being used...why not?
Hmm, that is unusual. Do you think you could download the Froyo RUU under the subheading "Stock Images" from here:
www.pvillecomp.com
and install that via hboot? If this works, you should be able to boot into the phone to begin the rooting process if the phone functions fine.
SlimSnoopOS said:
Hmm, that is unusual. Do you think you could download the Froyo RUU under the subheading "Stock Images" from here:
and install that via hboot? If this works, you should be able to boot into the phone to begin the rooting process if the phone functions fine.
Click to expand...
Click to collapse
Connected the phone to the USB cable and I got an error, screenshot attached.
You can access hboot but doing anything via usb cable results in nothing. That said, could you use the bionic or some other phone to place that RUU onto the root of the sd card then place place that sd card back in the Incredible and try installing it the RUU from hboot?
Side question: when you boot into hboot normally, does the incredible check for any files on the sd card like it is supposed to?
SlimSnoopOS said:
You can access hboot but doing anything via usb cable results in nothing. That said, could you use the bionic or some other phone to place that RUU onto the root of the sd card then place place that sd card back in the Incredible and try installing it the RUU from hboot?
Side question: when you boot into hboot normally, does the incredible check for any files on the sd card like it is supposed to?
Click to expand...
Click to collapse
yeah, it wont even pick up the phone via usb from my computer.
The Bionic SD Card thing is a GREAT idea, I will try that. Gees, why didn't I think of that.
Related
I have an A8183 from Telstra Australia. I rooted it using the revoked method, following the Telus Desire HBoot 0.83 Root and Flash guide on these forums. (new member unable to link).
I had the Cyanogen mod installed on the phone but didn't really like it. I wanted the HTC sense ui back so I tried to run a few generic RUU to get it back to normal.
Of course I got the Error 130 (Model error) or whatever it was. So I tried the Telstra RUU. I then got Error 140 (Bootloader error) and read around and found out I needed to downgrade to bootloader 0.80. Obviously did not realise this would affect the SLCD screen and remove the display drivers for SLCD to work.
I now have a phone with no screen, it boots and I hear the noises, but no display - not even in the bootloader or recovery mode. I tried putting the FroYo OTA on my gold card, renaming it "update.zip" but it didn't work, probably because I think I have a custom recovery mod I got from following the thread I linked above. Can someone please give me a noob guide to fixing this?
Use your gold card and flash WWE RUU_Bravo_HTC_WWE_1.15.405.4_Radio_32.30.00.28U_4. 05.00.11_release_122704.exe
Your screen is going to come back(the above RUU is SLCD compatible) and then download your Telstra RUU and flash with your goldcard(make sure RUU is SLCD compatible)
I've tried lots of RUU's and it takes about an hour to download one. The ones you just linked look similar to the ones I've already tried. I'm currently downloading it, as well as the Froyo one.
Will post back in an hour or two as to what happens.
EDIT: It says there is a problem with the USB connection whenever I try to run the RUU...How do I fix that? My computer recognises there is something plugged in, and the charging light is on my phone.
I tried this:
1. Remove the battery
2. Insert the gold card
3. Hold down volume down then press power
4. Blindly press power again to get into fastboot???
5. Run: RUU_Bravo_HTC_WWE_1.15.405.4_Radio_32.30.00.28U_4.05.00.11_release_122704.exe
and/or Run: RUU_Bravo_Froyo_HTC_WWE_2.09.405.8_Radio_32.43.00.32U_5.09.00.20_release_140022_signed.exe
On step 4, windows recognises a USB device but fails to install the driver. I went into the device manager and there is "Android 1.0" listed there. I tried to update the drivers manually by using the ones in the AndroidSDK. I'm assuming this has something to do with what happens on step 5. *UPDATE* Installed HTC Sync with the driver, uninstalled HTC Sync, windows picked it up. Windows required a restart before I was able to flash any ROMs.
On step 5 it gets up to the screen where it says "Gathering information about your android device" (or something). It times out and says Error 170 - Usb connection error.
*UPDATE* restarting the RUU fixes the USB connection error, however ALL of them give Error 130 - Model invalid. The only RUU that works is RUU_Bravo_Telstra_WWE_1.15.841.14_R4_Radio_32.30.00.28U_4.05.00.11_123851.exe and unfortunately that has already been flashed onto the phone - so it does not fix the screen. If anyone knows of an RUU that will work with my phone? Or perhaps a Telstra one that actually works and restores my bootloader or something.
Someone pleeeeeeeeease help
From what you say, I think the LCD is bricked but the phone is working otherwise. Just to confirm power on the phone and let it boot normally. You should hear the boot sound and then after 2-3 mins try calling from another number to see if it rings.
Once it is at that stage, connect the mobile to PC via usb. Ensure htc sync software is installed (Not the drivers alone, but the full htc sync software). Then run the .exe that is compatible with SLCD. Your phone should get flashed. You cannot see anything on the mobile screen yet, but you can see the status on your computer.
I am not sure if RUU flashing will work from recovery/fastboot screen..... I am guessing you get the timeout error cos the phone is not booted. Give it a try.
Yes, Yes to all of that. Like I said, the only RUU that works is the Telstra one atm, and that is already on the phone. Like I said, I flashed that after downgrading to bootloader 0.80. All the other RUU's that I have tried to flash give a model id error.
If anyone can point me to an RUU from Telstra that enables use of the screen I would like a link please
I may be giving you a wrong advice, but have you tried to turn the phone on while pressing the back button? (not the volume down, the back button), and flash a compatible RUU?
Yea I've tried that with most of the RUU's that I've downloaded. It just gives model ID error. The only compatible RUU that I've come across is this one Telstra one that I've found on this forum. None of the other generic ones seem to work. I can't seem to find another Telstra RUU that will work. I have no idea if the phone is even still rooted, or what version the bootloader is (My guess is still 0.80 - even though it needs to be 0.83).
I'm unable to re-root the phone with a method like unrevoked because I can't enable USB debugging (can't see anything) and unrevoked doesn't find my phone.
At the moment I'm just playing around with flashing different RUU's remaking my gold card, installing/uninstalling HTC sync, flashing RUU in what I think is the bootloader screen, what I think is the fastboot screen, and when the phone is fully booted. (This would be a whole lot easier if I could see what was happening).
The only luck I've had is re-flashing the original Telstra RUU which does nothing to the screen...
(not the volume down, the back button)
Click to expand...
Click to collapse
- What does that do?
Turning the phone on with the volume down key pressed takes you to HBOOT menu
Turning the phone on with the back button pressed takes you to the fastboot menu directly, if I'm not recalling bad you need to be there to flash a RUU, It's worth the try...
I tried it with the back button - Same deal Error 130 - Model ID Error.
Apparently you can fix that with a new gold card. I read somewhere else to remake your gold card step by step. One of the steps requires USB debugging to be on your phone to record the serial numbers listed in the command prompt with the phone plugged in. I already have goldcard.img and have tried putting it on multiple microSD cards, I now have no more to try out.
Anything else I can try?? This is my only phone :S
I am not an expert on flashing, but I had bricked the LCD on my desire before. But mine was unbranded and flashing a unbranded RUU that got my phone and display working again.
What I would suggest is you can try flashing an unbranded WWE Froyo RUU that is compatible with the SLCD desire. If you have the gold card, you can flash any RUU to your phone (That is my understanding)
If you are not able to flash any other RUU, maybe the gold card is not proper. As far as I know, you should use the .img only on the sdcard which was in the mobile when you executed the commands. using .img generated with one card on another sd card will not work I think. At least it didnt for me.
Also the RUU is not bothered about the Hboot version on the phone. An RUU will have it's own bootloader and it will flash it onto the device over the existing bootloader
And above all, do not panic. The device can be recovered and restored. It is just a matter of time and patience and trying out a few things.
Edit: I forgot to ask, Do you have a nandroid backup done immediately after rooting?? If you have done it you could save yourself a lot of time by just restoring it.... If you have not backed up, then Lesson No 1 in rooting -> ALWAYS do a nandroid backup before you do things.
I think I have to agree. After about 20 hours of trawling forums I am 90% sure that I screwed up the initial gold card. (unrevoked doesn't require a gold card - so I thought it worked).
Is there a way to create a new gold card without an android phone? If you could point me to a guide that would be awesome. Obviously I'm prepared to buy a new microsd card to fix my $900 phone :S
Do you have USB debugging enabled?? If it is enabled, you just need the phone to be booted to create goldcard. Insert a formatted sd in the phone and boot it up, connect via adb and generate the CID numbers and try to make one.
If usb debugging is not enabled, then you can play "blind" game and try to enable it without the screen. It's tricky but certainly possible.
It was, but unfortunately the flash that ruined my screen returned it to default, which I assume would turn debugging "off". The blind game? never thought of that, I guess I could try look around for a youtube video of someone doing it or something. If anyones got spare time some STEP BY STEP exact instructions would be awesome
lordmitchell14 said:
It was, but unfortunately the flash that ruined my screen returned it to default, which I assume would turn debugging "off". The blind game? never thought of that, I guess I could try look around for a youtube video of someone doing it or something. If anyones got spare time some STEP BY STEP exact instructions would be awesome
Click to expand...
Click to collapse
If you search for lcd brick fixed, you should find a step by step guide to turn usb-debug on.
To flash a ruu, your phone needs to be booted in android normally, the ruu reboots it in fastboot itself. If you get an error flashing the ruu, try updating the android phone drivers. Even if Windows said it didn't update, try the ruu again. It worked for me with a friends phone.
Sent from my HTC Desire using XDA App
Well here are the steps..
1.Power on the phone and after 2-3 mins, press the power button to load the lock screen
2.Swipe down to unlock.
3.You should be in homescreen if device just booted. Press menu and then press the spot immediately above the search button. This should take you to settings screen
4.Now swipe long strokes with your finger "down to up" 4-5 times on the screen.. you are now swiping down the list.We need to make sure we reach the end of it.
5.Once you reach the settings list's end, the "Applications" link will be located just below the volume "+" key. about 5-7mm below the + mark. press the spot.
6.Now you should be inside the applications. Now keep swiping down on the trackpad. Do it for 10-15 times no problem. There are only 4 items in the list and doing it many times will ensure the selection is now on "Development" which is the last item in the list
7.Press the trackpad. The development should now get selected
8.Wait for a second. Press the trackpad again(No up/down). USB debugging will get selected.
9.Wait a second. Press the trackpad again. The popup "ok" button will get selected.
And you are good to go
Connect to PC and see if you can connect via abd.
This is assuming that Debugging is turned off. If it is already ON, then doing this will turn it off. So first check if you can connect via adb before attempting this.
I followed all the steps in this guide: http://forum.xda-developers.com/showthread.php?t=750852
I even spent an hour getting the debugging to turn on.
I managed to root my Desire again and got down to step 35. Unfortunately that RUU gave a model ID error. Just like all the rest.
Thanks for all your help guys, although this is driving me insane :S
*BEGIN DANCING*
thanks to the awesome guys at http://code.google.com/p/androidscreencast/
After playing the blind game and turning on USB debugging, I was able to use my computer as a screen which made things a whole lot easier.
After following the guide linked in the post above:
- I bought a new microSD
- re-made the gold card
- Followed steps 30 onwards...
- ran the RUU several times (it finally worked whilst in boot mode)
- AND MY SCREEN TURNED ON F*%K YEA!
Great to hear!!!
Now do a Nandorid backup and then you can go about trying out any mod/rom you want and you can always get back your original state with a simple nandroid restore.
And that ScreenCast looks interesting... will give it a try
Not sure what happened, but my Desire won't get past the logo boot screen any longer, and RECOVERY mode in HBOOT just reboots the phone (regardless whether the SD card is installed or not). I can get into FASTBOOT however. I tried communicating with the Desire via adb console on my Windows XP system (after ensuring that I have the latest version of HTC Sync installed). "adb" commands do not recognize the phone (error: device not found). "Fastboot" commands do recognize the phone. (The command "fastboot devices", gives me this in return: SH09ER801629). So I'm not sure if my USB drivers are okay with adb, but the fastboot success seems to suggest so. (Also, "MyHTC" shows up under "Android Devices" in Device Manager).
The phone was rooted with ClockWork Mod using UnRevoked, and had Teppic stock Froy v.2.10.405.2 initd as the OS. Originally, it had TELUS-branded Eclair. I've downloaded the TELUS Froyo RUU.exe, but don't know how to install it on the phone, if I can't access RECOVERY mode or adb console. I don't think I ever set up a Gold Card, to my recollection. Also, I've been out of the smartphone scene for 6 months, and did no mods, no flashes, no program installs to my phone in that time. So it's a mystery as to why this is happening. But the phone had been acting up lately, rebooting by itself during a call every so often.
HBOOT screen:
Bravo PVT-3 SHIP S-ON
HBOOT 0.83 0001
RADIO 5.10.05.30
Cyanoid said:
Not sure what happened, but my Desire won't get past the logo boot screen any longer, and RECOVERY mode in HBOOT just reboots the phone (regardless whether the SD card is installed or not). I can get into FASTBOOT however. I tried communicating with the Desire via adb console on my Windows XP system (after ensuring that I have the latest version of HTC Sync installed). "adb" commands do not recognize the phone (error: device not found). "Fastboot" commands do recognize the phone. (The command "fastboot devices", gives me this in return: SH09ER801629). So I'm not sure if my USB drivers are okay with adb, but the fastboot success seems to suggest so. (Also, "MyHTC" shows up under "Android Devices" in Device Manager).
The phone was rooted with ClockWork Mod using UnRevoked, and had Teppic stock Froy v.2.10.405.2 initd as the OS. Originally, it had TELUS-branded Eclair. I've downloaded the TELUS Froyo RUU.exe, but don't know how to install it on the phone, if I can't access RECOVERY mode or adb console. I don't think I ever set up a Gold Card, to my recollection. Also, I've been out of the smartphone scene for 6 months, and did no mods, no flashes, no program installs to my phone in that time. So it's a mystery as to why this is happening. But the phone had been acting up lately, rebooting by itself during a call every so often.
HBOOT screen:
Bravo PVT-3 SHIP S-ON
HBOOT 0.83 0001
RADIO 5.10.05.30
Click to expand...
Click to collapse
if i'm not mistaken you can run the ruu and it should see the device if connected to pc with fastboot loaded.
as for trying to get back without losing data i'm new to all this so no idea
if you had run ruu on the phone and it was wrong type (i.e gsm ruu on cdma phone or other way round) then that explains the lack of capability.
Thanks for the tip. I ran the Froyo TELUS RUU.exe (should be the right type, as I have a Telus phone). It wouldn't work (in both main HBOOT screen and FASTBOOT screen). Gave me an "error 170". It could not connect to the phone, despite that I'm on Windows XP, that it says "Android Bootloader Interface" in Windows Device Manager, that it says "HBOOT USB PLUG" on the HBOOT screen when connected via USB, and that I am able to issue FASTBOOT commands from the PC. But I can't issue adb commands, so it appears I can only "partially" communicate with the phone from the PC.
Should I try CLEAR STORAGE, or could that fully brick my phone?
On the HBOOT screen, these are the status messages that load:
Loading...[PB99DIAG.zip]
No Image!
Loading...[PB99DIAG.nbh]
No Image!
Loading...[PB99IMG.zip]
No Image!
Loading...[PB99DIMG.nbh]
No Image or wrong image!
waynestir said:
if i'm not mistaken you can run the ruu and it should see the device if connected to pc with fastboot loaded.
as for trying to get back without losing data i'm new to all this so no idea
if you had run ruu on the phone and it was wrong type (i.e gsm ruu on cdma phone or other way round) then that explains the lack of capability.
Click to expand...
Click to collapse
USB Brick
For me, it sounds like a typical usb brick :/ I hope you still have rooted ROM. Search through this forum for unbricking guide.
Put the ROM.zip from the RUU on your SDCard but name it PB99IMG.zip and then boot with volume down again to enter HBOOT, it should give you the option to flash your phone back to factory default then.
HTC Desire Stuck on HTC logo - Recovery not Working - SOLVED!!
madcr0w said:
Put the ROM.zip from the RUU on your SDCard but name it PB99IMG.zip and then boot with volume down again to enter HBOOT, it should give you the option to flash your phone back to factory default then.
Click to expand...
Click to collapse
Thanks! I just tried that on the advice of another poster on another forum (before reading your reply), and that's the one and only thing that worked!
Especially when, after the RUU.exe wouldn't install, RECOVERY mode wouldn't work, nor adb, nor HTC Sync. Yes, I've lost my root access, but small consideration, considering I haven't lost my $500 investment! I'm sticking with stock now, as I'd rather not risk having a brick in the future.
As for what went wrong, I can't say for sure. But considering it took months after I had installed a ROM or otherwise modified the phone for problems to show up, I'm guessing it was probably the overclocking heating the chips. Which led to eventual random reboots during phone calls, and the eventual freezing of the boot screen, and subsequent inability of HBOOT to load PB99IMG.ZIP.
xda rocks, thanks to you and all those who took the time to reply.
sorry for delayed responce. I'm sure you had already found a solution by now but in the off chance you didn't.
you have to load fastboot not hboot.
from a power off state hold back button and power on phone. this will load fastboot and ruu will find device when run.
Cyanoid said:
Thanks for the tip. I ran the Froyo TELUS RUU.exe (should be the right type, as I have a Telus phone). It wouldn't work (in both main HBOOT screen and FASTBOOT screen). Gave me an "error 170". It could not connect to the phone, despite that I'm on Windows XP, that it o Image!
Click to expand...
Click to collapse
Fastboot will only work in Fastboot. ADB will only work when phone is booted and USB Debugging is on.
I don't know that as fact, I only know it from personal experience.
Use Fastboot to flash a new ROM, or at least a new recovery image. If you can get into Fastboot, you 'should' be able to fix your phone.
expza said:
Fastboot will only work in Fastboot. ADB will only work when phone is booted and USB Debugging is on.
I don't know that as fact, I only know it from personal experience.
Use Fastboot to flash a new ROM, or at least a new recovery image. If you can get into Fastboot, you 'should' be able to fix your phone.
Click to expand...
Click to collapse
+1 There is a good guide to fastboot commands on the android wiki:
http://android-dls.com/wiki/index.php?title=Fastboot
Should be a case of wiping system, data, cache, then flashing recovery image. Then boot into that and restore a backup or flash a rom.
Cyanoid said:
Thanks! I just tried that on the advice of another poster on another forum (before reading your reply), and that's the one and only thing that worked!
Especially when, after the RUU.exe wouldn't install, RECOVERY mode wouldn't work, nor adb, nor HTC Sync. Yes, I've lost my root access, but small consideration, considering I haven't lost my $500 investment! I'm sticking with stock now, as I'd rather not risk having a brick in the future.
As for what went wrong, I can't say for sure. But considering it took months after I had installed a ROM or otherwise modified the phone for problems to show up, I'm guessing it was probably the overclocking heating the chips. Which led to eventual random reboots during phone calls, and the eventual freezing of the boot screen, and subsequent inability of HBOOT to load PB99IMG.ZIP.
xda rocks, thanks to you and all those who took the time to reply.
Click to expand...
Click to collapse
can u plz help me frm with post u solved ur probs....i m stuck too
1st Post, got my htc desire this morning and after researching for a long time already knew i wanted to root my device.I followed the instructions on this site.[HOWTO] Root Your Desire In 1 Click With UnrEVOked! *UPDATED 20/7* - xda-developers I used unrevoked3, and rooted the device. no trouble Ive backed up the device with titanium backup. Placed cyanogen onto the 4gb sd card which came with the phone.Power off the device. Rebooted whilst holding the volume down button. Got the options up. Navigated to recovery and selected it with the power button. The screen goes blank. The o2 screen comes up saying welcome and thats it, it freezes. I have to pull the battery out of the back in order to reset the device and then it starts up perfectly normal. Tried accessing recovery mode using the clockworkmod but i get the same result.All of the points on the link above were followed. Im pretty much right at the bottom! still researching the net for the answer but im now in need of additional
Does your phone get hot and overheated during the htc logo? It did so to me and it turned out to that my CPU had melted and overheated. Take it to your retailer and they will fix it for free because it's not your fault, it's the phone that overheated.
Try this:
-download this with ur pc and rename it a PB99IMG.zip (not PB99IMG.zip.zip ok?)
-then put it on the root of ur sdcard (not in some folder) through an sd card reader
-ensure the battery is charged much than 30%..better more
-with the phone off (remove battery and put again) press and HOLD the volume down key and press (still holding the volume down key) and hold the power button..hold both and wait to enter in the hboot
-there wait a bit, and it will ask to u if u want apply the update, select yes with the volume keys and confirm with power button
awayra said:
1st Post, got my htc desire this morning and after researching for a long time already knew i wanted to root my device.I followed the instructions on this site.[HOWTO] Root Your Desire In 1 Click With UnrEVOked! *UPDATED 20/7* - xda-developers I used unrevoked3, and rooted the device. no trouble Ive backed up the device with titanium backup. Placed cyanogen onto the 4gb sd card which came with the phone.Power off the device. Rebooted whilst holding the volume down button. Got the options up. Navigated to recovery and selected it with the power button. The screen goes blank. The o2 screen comes up saying welcome and thats it, it freezes. I have to pull the battery out of the back in order to reset the device and then it starts up perfectly normal. Tried accessing recovery mode using the clockworkmod but i get the same result.All of the points on the link above were followed. Im pretty much right at the bottom! still researching the net for the answer but im now in need of additional
Click to expand...
Click to collapse
Just go to my troubleshooting guide, you'll probably find an answer there.
Send it back for warranty repair.
Sent from my Motorola Startac running Atari 2600 software!
@nhrsak - you save me, thanks very much!!
Did you try getting s-off with Revolutionary?
I had problems when i was s-on, but when i s-offed, everything went fine.
Have you tried flashing recovery.img via AndroidFlasher(from XDA)?
Hello,
yesterday i tried to root my Desire, but i forgot to remove HTCsync, now the phone boots sometimes untill screenlock/pincode. then the phone resets itself, and just vibrates 7 times and boots/reset for aprox 3 or 4 times then it dies.
unrevoked worked fine until it was waiting for a reboot it never installed clockworkmod so i dont have a clue how to fix it, i tried to flash PB99IMG from different stock roms, the Desire was simlock free, but now it tells me wrong CID,
now i have:
BRAVO PVT1 SHIP S-ON
HBOOT-1.02.0001
MICROP-031d
TOUCHPANEL-SYNT0101
RADIO-5.11.05.27
Jul 22 2011,16:19:16
So i can go in to the first stage of recovery, (vol down plus powerbutton) but when i want to continue to RECOVERY the phone gets stuck in the white screen wit HTC logo and thats it.
thanks in advance,
best regards,
Marcel
Search for a user called 'bortak' and look for his troubleshooting guide, it should give you enough info to get your phone working again!
It sounds to me like you should have read and learned more before you did this. If you can press volume down + power and you get the Clockworkmod Recovery then you can stop worrying. Plug the phone into the PC via USB cable and then using the trackball or the volume +/- buttons scroll down to 'Mounts and storage' then press either the trackball or power button to select. Once there scroll to the bottom option, 'Mount USB storage'. Your PC will hopefully recognise it as a disk drive now.
Now go pick any ROM that will work with a stock hboot, they will quite clearly say 'stock'. I personally use LeeDroid 3.3.3 HD wotsit, Apps2SD. Runs well, battery life is good but don't feel that you have to copy my choice, any ROM with a 'stock' version will work.
Download it and copy it across to your phones SD card - you did remember to connect the phone as I detailed above right?
Ok, once done press the back button on the phone, press back again to get to the main menu then select factory reset, then wipe cache then select 'Advanced' and wipe Dalvik cache. Press back, install zip from SD card, select the file that you copied to it, let it do its stuff and click reboot when prompted.
Hopefully, you'll have a working phone.
A couple of caveats though :-
1) You will lose all apps and data and have to start afresh
2) You will lose all contacts and messages (unless already backed up to Google)
3) I am assuming that you have created an EXT partition on your SD card. If not then you have REALLY jumped into this too fast!
And finally, don't try flashing different hboots via the pb99.img method until you have a clue what you're doing.
Good luck.
Hi there thanks for the quick reply,
the problem is i can get in to fastboot, but when i try to go in to recovery the phone stays stuck in the white screen with the htc logo and thats it.
i already rooted a different desire and that went smooth. no probs what so ever.
So i repeated the same steps on this desire and everything went exactly the opposite
way that it should have been.
Volume down + Power on is not fastboot, that's recovery.
I'm out anyway, all of the answers are available.
You have to create a goldcard:
http://android.modaco.com/topic/308798-pc-application-goldcardtool/
You can this with another working desire as well, because goldcard is only connected to goldcard and has nothing to with the phone.
When done, put this in your desire and then flash ruu via PB99IMG.zip file again. The goldcard will avoid CID error.
will it work if i use my Legend for making the goldcard?
Don't see why not. Just give it a try.
vibrates 7 times... that's a bad sign :S
now i keep getting main version is older???
now i'm stuck with the htc logo and the for reclamation marks in every corner.
i cant use android flasher because i'm S-on
if i try to update i get : radio v2 failed.
then partition failed?
i have created a gold card without any problems. but now the phone doesnt even give me the chance to select fastboot or recovery, it only says RUU and then the 4 exclamation marks.
DAMA0707 said:
now i'm stuck with the htc logo and the for reclamation marks in every corner.
i cant use android flasher because i'm S-on
if i try to update i get : radio v2 failed.
then partition failed?
i have created a gold card without any problems. but now the phone doesnt even give me the chance to select fastboot or recovery, it only says RUU and then the 4 exclamation marks.
Click to expand...
Click to collapse
Could be radio brick. Hope for you that it is not!
Did you use the PB99IMG.zip method with your goldcard?
is it possible that the gold card i created with my htc legend doesnt work in my HTC desire?
Don't see why it shouldn't work. But not 100% sure.
Work colleague has nailed her Desire, only boots as far as the HBOOT screen, cant use volume rocker to select fastboot, recovery, clear storage or simlock.
Have followed various threads, downloaded Android SDK, AlphaRev etc etc which dont recognise the device has been connected, all tried without HTC sync drivers installed and uninstalled, even HTC Desire 2.3 RUU rom update attempted.
Colleague advises it is rooted, i suspect this is not the case, out of my comfort zone - will leave handset charging - will it take a charge from HBOOT menu using microusb mains charger ?
poweroff, hold back & power. It should boot into fastboot. then run the 2.3 RUU
Please try to keep subject lines descriptive. "Desire help" in a Desire help forum doesn't give much to go on. You may not attract helpful members as they want to know a brief synopsis of the issue before opening a thread.
I only opened the thread to type this tbh.
apologies, unable to use volume up or down to select
BRAVO PVT1 SHIP S-ON
HBOOT-0.93.001
MICROP-031d
RADIO-5.11.05.2
So looks like S-ON is enabled after all, ah well
Just to clarify, S-OFF and root are two different things.
It does sound like either a hardware of software issue, possibly the latter.
Like Bortak suggests, it may be worth running a RUU from fastboot (ROM Upgrade utility) from a PC to wipe and completely set everything as default.
If Hboot still broken, probably hardware but should be good for a warranty return.
Ok shes fessed up shes dropped it a few times lol
I suspect battery is not holding its charge unable to flash with HTC RUU constantly advises under 30% battery charge, stuck on bootloader screen.
Handset is missing the rear cover and has a dirty big scratch across the screen... yes my thoughts.
Unable to detect handset in linux environment (vmware)
Sometimes with certain issues, the battery does report that. Only other way is to get a PB99IMG.zip on the root of the SD card. Hboot prompts to install but you need volume button functionality to work.
I am betting it is a hardware issue though, due to accidental damage.
Hi, got a serious that I can't figure out, on day 8 with no change. Here's the details
SUPERSONIC EVT2-3 SHIP S-ON
HBOOT-2.16.0001
MICROP-041f
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.00.00808
Mar 8 2011, 17:02:15
The phone is unrooted. This is my sisters phone and I took out the battery without turning off the phone. (I do it all the time with my touchpro2, will never do it again!) I put my SD card in and turned it back on and now it's in a reboot loop. It starts up, shows the white screen with the htc EVO 4G then reboots to the same thing over and over. I could get into the bootloader. I tried all of the options. Recovery just goes to the white screen again with the htc evo 4g logo and starts the reboot loop. I did clear storage, and when it reboots it starts the loop too.
I tried loading the PC36img.zip file to a formatted sd card and the phone reads it but doesnt give me any prompts to install or anything, it just goes to the regular bootloader screen, and recovery still doesn't work. I tried loading some shipped roms but I think Im on the latest rom so it won't let me install any roms because I'm not rooted. I get an error 140 -bootloader version error. What else can I do? I am so stressed over this and my eyes are killing me from all of the seaching. I tried setting up sdk and adb but couldnt get it to work and don't think it would read my phone cause it won't start up to set up the debug mode.
nuffstylez said:
Hi, got a serious that I can't figure out, on day 8 with no change. Here's the details
SUPERSONIC EVT2-3 SHIP S-ON
HBOOT-2.16.0001
MICROP-041f
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.00.00808
Mar 8 2011, 17:02:15
The phone is unrooted. This is my sisters phone and I took out the battery without turning off the phone. (I do it all the time with my touchpro2, will never do it again!) I put my SD card in and turned it back on and now it's in a reboot loop. It starts up, shows the white screen with the htc EVO 4G then reboots to the same thing over and over. I could get into the bootloader. I tried all of the options. Recovery just goes to the white screen again with the htc evo 4g logo and starts the reboot loop. I did clear storage, and when it reboots it starts the loop too.
I tried loading the PC36img.zip file to a formatted sd card and the phone reads it but doesnt give me any prompts to install or anything, it just goes to the regular bootloader screen, and recovery still doesn't work. I tried loading some shipped roms but I think Im on the latest rom so it won't let me install any roms because I'm not rooted. I get an error 140 -bootloader version error. What else can I do? I am so stressed over this and my eyes are killing me from all of the seaching. I tried setting up sdk and adb but couldnt get it to work and don't think it would read my phone cause it won't start up to set up the debug mode.
Click to expand...
Click to collapse
Use 4.65 RUU
Try the latest 4.54 RUU and run it through FASTBOOT USB (click on fastboot with your phone connected to your computer.
http://www.filesonic.com/file/40834....15.00.0808_NV_2.15_release_220182_signed.exe
okay, I downloaded the latest RUU which is the one I am on now 4.54.651. Ran it and it loaded up and went through the whole process. I got so happy. When it finishes, it reboots and starts the loop again. I also put the correct PC36IMG file on my SD card and it found it and the phone loaded it. But still the same thing. I dunno what to do next. I also tried the UnlockBootloader thing from HTCDEV. But when I get to step 8 to enter the command, the phone gives an error. But the computer finds the phone in fastboot. Now I definitely see why people S-Off their phones
if the phone is under 1 year old then you have the warranty which is still good unless theres water damage or proof of you internally modifying the phone or intentionally broke it physically.. tell them it froze so you pulled the battery and it got in a loop and factory reset doesnt work
Yeah, pretty simple. it's an unrooted phone. Just trade it in
the phone shows water damage even though it works perfectly. From what I read, I think the boot file is corrupted but I can't load a new one. Why is it when I load a factory RUU, it doesnt load the new boot and recovery file to get the phone working again.
nuffstylez said:
the phone shows water damage even though it works perfectly. From what I read, I think the boot file is corrupted but I can't load a new one. Why is it when I load a factory RUU, it doesnt load the new boot and recovery file to get the phone working again.
Click to expand...
Click to collapse
When you loaded the factory RUU, it probably did flash a new boot image and the stock recovery (which is useless at this point). The RUU was a last resort (the reason why I said try it), and if it did not fix the issue, then the problem is more likely hardware related.
Is there anything I could do with a program I found online called CDMA workshop. Looks like it has lots of features to work with.
Update: I thought I got it fixed. I downloaded a 4.54 rom from scottsrom.com and put it on a SD card and renamed it PC36IMG. It actually loaded it up this time, then said Parsing... [SD ZIP] and had [1] RADIO_V2
[2] RECOVERY, all the way to [8] SYSTEM. This never happenend before. So I got all happy and it updated all 8. But when it rebooted, it still did the reloop over and over. I got so happy that I finally got it fixed but it didnt do anything. What could it be? If anyone is in Queens, NYC and could fix this for me, I am willing to pay.
At this point, it seems like you have the bad blocks error, which is not fixable