Related
Hello,
I have the following problem on my desire and would appreciate your help.
I used to have 2.1 and just upgraded to Paul's 2.2 r8 version. There were some strange restarts so I decided to start from scratch, create the gold card again, root, etc etc.
I used the unlocker.com as a guide to do all those and here is what happens when I try to root the phone. I also want to mention that right now the phone doesnt boot up and I am stuck in the "triangle" screen, but this one looks different than the one that I knew with the triangle in the middle; it just says htc in the middle and there are 4 small triangles in the corners.
I run the step 1 batch file from unlocker and there are no errors; however, there is a progress bar on the phone's screen that is normally green and for a quick second it turns red and then back to green. I was able to see that this happens when the radio is being written (as per the progress in cmd).
When I pull the cable to the pc off, it gets to a RUU white "screen" and there isnt any button that will have an effect; once I plug back the cable it goes back to the triangles screen with htc in the middle.
ADB is not working even though I reinstalled the drivers, etc. only fastboot works. (by working I mean that the device doesnt show in adb, but it shows in fastboot)
Bootloader is 0.80 and the version that I get using fastboot is 1.21.405.1
Any clue on how to access recovery and just flash a ROM that will be fine? Must be something related to the recent rom upgrade to Paul's r8 Froyo I guess, but I dont know where I messed it up.
Thanks a ton guys and sorry for the long post but it is a strange one and tried to explain somehow the symptoms.
Re-install using a RUU (Can be done from fastboot screen I think), then use unrEVOked to root, no messing with batch files.
Hi again,
I tried running different RUUs, both 2.1 and 2.2, but I get the same error at the end of the install wizard: Error 110: file open error (The rom update utility cannot open the requested files or the files are damaged...)
The thing is that the install wizard seems to go through all the steps (checking signature, updating system, radio, recovery, etc.) and only at the end this error comes up.
One other aspect is that again the progress bar on the phone screen is green but flashes red when the radio is being written on the phone (as per the install wizard); then it goes back green when writing recovery, system, etc and there is another triangle with ! showing up on the right side of the progress bar (is not there when it starts).
The info showing up in the RUU "menu" on the phone (the only one I can see when the phone is not plugged to the pc) is showing a bootloader version of .9x after RUUing the froyo's and changes back to .8x after using the 2.1 RUUs. The only thing that remains the same is the radio version that still shows 4.06.00.02_2 irrespectible of the RUU that I try to install (2.1 or 2.2), hence I believe that there is something wrong around the radio part. I remember that Paul mentioned on the thread where I got the r8 froyo pre-baked zip file originally that it includes a radio version 5.10.x while the froyo RUUs that I tried to flash are having 5.09.x, maybe this is the problem as it might be that one cant flash an older RUU than what the phone has, but its strange since the bootloader is "upgraded" and downgraded without problems.
Any other suggestions on what can I do further? (right now I only have access to the RUU menu when I turn on the phone and to fastboot commands in cmd...the phone doesnt start so I cant access anything else as per my current understanding).
Thanks again for the help guys!
So you can acces hboot and bootloader only??
And when you tried to enter to recovery get stuck on htc logo screen??
Volume up/down button work ok?
nope, buttons are not working at all, only power up when the phone is off.
here is the sequence providing the phone is off and has a valid gold card in it (I dont get the CID error); doesnt matter if the cable is connected to the pc or not:
1. push power button, phone starts up to a screen showing the following: HTC in the middle (with some water shade under it) and the 4 small triangles in the screen corners (they have a ! mark inside).
- any combination of power + back or + vol down dont start the phone
- when I first rooted the phone having 2.1 there was just 1 triangle (bigger) with the same ! mark in the middle of the screen, that's it and of course all the hboot and recovery menus were ok
2. plug cable to pc and run RUU.... .exe, install starts on pc and also on phone there is a green progress bar under "HTC". bar goes red for a second when the pc app shows something like writing radio. bar gets back to green when the pc apps writes system, bootloader, etc., but there is another small triangle showing up at the end of the progress bar on the phone.
3. error shows on the pc app, error 130 above, then the phone shuts down and if restarted it gets back to the same triangle screen with htc in the middle like it was before the ruu attempt.
- if when I power up the phone (after pulling up the battery) and then remove the pc cable, the screen changes into a white background one with something that I would call a RUU menu; looks just like the one that you get when you power up pressing "back" on the phone, but only with RUU as an option (like you have in the oter Recovery, Restart, etc etc and you navigate with vol up/down and select with power). here no button works, or any buttons combination.
- the screen changes back to the "triangles" one as soon as I plug the pc cable into the phone and switches back again and so on when I pull out the cable from the phone.
- te bootloader version that I can see on the RUU "menu" when I plug out the cable is changing acording to the RUU that I try to write and it goes above 0.8xx and comes back under it easily...the firmware version and radio remain the same though (radio is 4.06.xx, firmware 1.21.xx)
- via cable I can use only fastboot command in cmd, as adb doesnt list the device (I tried reinstalling the drivers). firmware in fastboot is the same as the one that the pc app "sees" on the phone when trying to install the RUU, and the device shows up using fastboot command
That's it...kind of strange, at least to my knowledge at the moment.
And to ask to your questions I dont have access to recovery and not to hboot I believe, only to that one showing RUU as the only option...
Those 4 triangles in each corners look familiar to me. You forgot to give the most important information: HBOOT, radio, etc.
A few minutes on Google gave me this: Google is your best friend. Keywords were: htc desire triangle corner error. Here is the link to the search page: Google is your friend
it's not a triangle in the corner...there are more but that's not the point.
hboot is above 0.80xx and radio 4.06xx, but again, as mentioned the hboot version changes depending on the RUU that I try to write, radio and firmware not.
thanks for the link though, added a reply maybe something happened in the mean time...
and btw, google is everybody's friend
popepope said:
it's not a triangle in the corner...there are more but that's not the point.
hboot is above 0.80xx and radio 4.06xx, but again, as mentioned the hboot version changes depending on the RUU that I try to write, radio and firmware not.
thanks for the link though, added a reply maybe something happened in the mean time...
and btw, google is everybody's friend
Click to expand...
Click to collapse
I think you miss something here: if I recall properly, those 4 triangles in ALL for corners appear when you try to root a SLCD Desire with a AMOLED rom, thus 'killing' your screen. Try the downgrade HBOOT 0.83-0.92 to HBOOT 0.80 root method and you'll safe. You have to root your phone according to the HBOOT and downgrade it if you need to.
hmm...the thing is that i rooted the phone before with the same approach as I had now, so same rom and it behaves different now versus the first time; but it worked then so not sure if it is related to the amoled vs slcd screens.
I am already on hboot 0.80xx so the downgrade wont help, right? i am not able to access hboot menu irrespectible of the bootloader version that I see in the RUU menu (I mentioned that based on the RUU that I try to write the hboot version changes up and then also down just by attempting to write a RUU). plus, adb comms are not working, only fastboot...
i think the amoled vs slcd issue was that the screen is not working, but the phone is booting up, etc.
would appreciate some more help pls
I have read other posts here about the 4 triangle thing - never saw how any of them turned out though. I'm not having a crack at you here for not searching, but have you had a look here to see whether you can find someone who has had similar problems? With so many members, you can almost bet that someone else has had the same problem as you in the past....
Good luck in getting things sorted.
tried to contact via PM the users having the same problem, but no reply as of now. will post the solution when found for sure, but at the moment I still cannot get adb functionality, so completely out of ideas, waiting for others
Hey Popepope - did you manage to fix this issue? I have exactly the same problem as you have described, and I can see the boot screen after removing the cable following the RUU error and it says "Radio_V2 - Fail-PU". I get the same red progress bar when it is updating the radio. Something is clearly broken here...did you manage to fix yours or did you send off for a replacement?
Is your screen a SLCD one or a Amoled one? If it is a SLCD one, flash a SLCD RUU. If its a Amoled one then PM me and ill see if I can help you with a problem as I ran a Tuition a few days ago. As you say that the error you get at the end is dew to a damaged file or something, can you try downloading the RUU from a mirror? Again if you need a mirror, pm me and ill post on on my dropbox. The method I used for flashing Ruin was much better and easier so you can hope to find a fix. Pm me. Good Luck anyway!
I managed to fix the issue by leaving the phone to charge overnight, running the same RUU that failed before on a full battery and it worked! I now have a working phone
I ran the update on win 7 64 so it shouldnt matter what operating system you use - if you have the same issue as I did just make sure the battery is fully charged before running the RUU. Still having reboot loop issues though :E
Hey Popepope did your problem solve i have the same 4 triangle each side with HTC logo in middle tried most i can but didn't find solution here is the screenshot i had attached
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)?
Hi,
Let me start with my device info.
HTC Desire
- Bravo PVT4 SHIP S-ON
- HBOOT-0.93.0001
- MICROP-051d
- Touch panel-synw0101
- radio-5.09.05.30_2
- Aug 10 2010,17;52;18
Current image version
RUU_Bravo_Froyo_Chunghwa Taiwan carriers (version: 2.10.751.4)
I'm running Windows Vista x86
That's all I got.
Now, the problem.
Everytime I turn the device on, it get stuck at the White HTC Windows and vibrates several times, I think this is a pretty common problem, so I won't stress this issue too much.
The solutions that I found are.
As my device is S-ON my options are limited. I can't boot recovery, so..
I download the latest RUU_Bravo_Froyo_HTC_WWE_2_29_405_5_Radio_32_49_00_32U_5_11_05_27_release_159811_signed_2
Now, I run the ruu until ask to connect, I connect my device, the ruu recognize and identify my device, it ask to update, everything good. Updating process start and suddenly stops and tells me, "error 131, customer id error"
and that I need to use the right RUU utility.?
So I decided to avoid the USB connection and try to flash it directly from the SDCARD, I extracted the rom.zip from the above file, change the name to PB99IMG.ZIP, put it on my device, volume + power, but nothing.
so thinking that something is missing, I select fast boot, the device shows some text in green, even shows the PB99IMG.ZIP file, and is back to the bootloader screen and nothing happens.
What else can I do to bring to life my device, if I choose recovery with the PB99IMG file in the sdcard, the device shows a black screen with a red triangle.
I think is something with that taiwanes RUU, but maybe not.
Could any one please put me in the right direction
Thanks in advance
Sovius
As my device is S-ON my options are limited. I can't boot recovery, so..
Click to expand...
Click to collapse
Can you boot into fastboot? Using revolutionary.io will give you S-OFF and then you can flash a recovery - since you are PVT4, then AmonRa or newest CWM recommended.
You need a goldcard to RUU with that RUU. Download the 2.3.3 RUU from htcdev.com. this should resolve the Id issue.
Sent from my HTC Desire using xda premium
Thanks for you replays
This is what happen now.
davebugyi
In tried to S-Off with Revolutionary, I remove HTC Sync and install the drivers required. > Back + Power > the device is in fastboot screen > connect the USB cable and the device seems to be recognized by the computer but no notification of that is given, except for a beep (like when you plug a USB flashdrive) but no letter is assign to the device or anything. > I double click revolutionary and the program said "waiting for device", I left it for 30min, but nothing.
As I cannot get inside the device, the problem might be that revolutionary requires my device to have "USB debugging on" I don't know if is on or not.
rootSU
How do I create a Gold Card, if I can't get inside the device to set everything up?. Can I use another Gold card or they are exclusive of each device.?.
Your recommendation are Welcome, Please let me know if you need anything from me to have a much clear understanding about what's going on.
I'll make a video to show you exactly what happening and what I'm doing
Cheers
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.