Develop Bugs

no access to recovery & OS not starting up

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

[Q] Fix for Desire that reboots vibrating 7 times or suddenly after booting ?

Hi,
I have a Desire here that was from a German o2 contract and now shows very strange behaviour. When normally turned on it is sometimes possible to boot the device normally into Android 2.2 when it then suddenly resets itself.
Also using the software reset from within the system did not work to improve this.
The next step was to use the CLEAR STORAGE option in the stock Recovery menu but also this did not fix the the problem.
Sometimes the phone when turned on does not boot at all and just he white backgrond with the green htc is there after one time vibrate.
Sometimes after this he phone vibrates 7 times and does not boot.
And then again after removing the battery it might come up and start the normal registration process with the language selecting and after some time reboot suddenly to show one of the other behaviours again.
The details from the recovery screen HBOOT menu (Holding down VOLUME DOWN followed by a short keypress POWER):
BRAVO PVT1 SHIP S-ON
HBOOT-09.93.0001
MICROP-031d
TOUCH PANEL-SYNT0101
RADIO-5.09.05.30_2
Aug 10 2010,17:52:10
FASTBOOT
RECOVERY
CLEAR STORAGE
SIMLOCK
I have read in another thread http://forum.xda-developers.com/showthread.php?t=660770 that by installing a fresh ROM again this could be solved. I am just not so sure anymore that this can be a software problem only.
My next steps would be to read out the CID of the SD Card on another Android phone to create a Goldcard and try and reflash because I cannot boot into the system to enable USB Debug to root or use some root explorer or adb shell to read out the CID reliably with this device.
Any other suggestions or tips ?

Download the latest RUU, run it and let it finish. It will update Froyo to the latest version and your radio too. Should fix any problems that your having. If at all you get an error which is something to do with the CID, create a Goldcard.

Overheating
I'm afraid these are the very same symptoms I had last year. The reboots are caused by overheating in most cases.
There isn't much you can do. I advise you to return your phone and have it repaired. If they do a proper job, they will replace the motherboard, and all problems are gone.
You should test if it really is overheating by:
Turn your phone off and keep it off for like 15 minutes, to make it cool down.
Turn your phone on, let it boot normal, and wait like 5 minutes after it finished booting.
When it is still working, turn on navigation, or try to watch a flash movie on a website. -Do this while you are CHARGING the phone-. This will dramatically increase the temperature of your phone, and if the cause really is overheating, the phone will try to reboot.
ps. The reboot almost never boots completely, because when it restarts the phone is still too hot, so it freezes at the HTC screen.

HTC Flyer stuck on boot screen after 3.2 upgrade

Today there was an update 3.2 for my HTC FLYER so I downloaded it and started the install process. ( This was an official update as my rom is official )
So I started the install process and after some time it installed, and it started booting.
When it came to the HTC booting screen ( green HTC logo with white background) it stopped there and never booted to the Home Screen. I kept it like that for aprox. an hour but it didn't move from there.
Every time I rebooted it , kept stucking on the same point and never loaded on the home screen.
I tried factory restoring, through HBOOT but it kept transfering me to the HTC boot screen and kept staying there without going to the home screen.
My device was already S OFF .
I also tried connecting it to my PC with the USB cable but it didn't want to install the drivers. It failed every single time. I tried running HTC Sync but also it never recognizes the device.
Can anyone please help me? I can't even turn the device off, it keeps restarting to the boot screen and stays there for an unlimited amount of time.
With regards,

BUMP : Anyone???

I got the same problem. Anyone has a solution?

eric
got the same problem,can't even get the device to reset to factory,and the power light just keep blinking orange color,can't root to another OS either.
have tried the adb method and can't find the device.so can't do the RUU way.
anyone got any ideals?

I am in the same situation right now since last night... badly need to go back to the S-Off and phone feature running....

I've read about this problem in a german community. This workaround may work for you, but you do this at your own risk. I'm not responsible for any malfunctions or damages on your device! also note, that your sd-card will be completely wiped!
If you read the bold text above, you can try this:
plug in your flyer with your HTC AC charger
enter hboot
jump to "factory reset" with vol-down
HOLD vol-down AND power for ~30sec (after ~15sec the screen will be black with background-light, still hold down both buttons!)
after ~30sec the screen will be completely black
now you should see the green "arrow-ring", only now release vol-down and power
wait up to 10min and your flyer will boot properly

Got the same problem.
It's frozen: nothing works.
How do you connect it to the electrical grid?
Can you let it until the battery runs out?
Please help.
Thanks in advance,
DD47

DonalDuck47 said:
Got the same problem.
It's frozen: nothing works.
How do you connect it to the electrical grid?
Can you let it until the battery runs out?
Please help.
Thanks in advance,
DD47
Click to expand...
Click to collapse
Just plug in your HTC AC-power plug.
If you do that, your battery won't run out.

Edit: Removed, because question was answered above.
Thanks, woggly4
DD47

boot the htc flyer
If you plug in the AC-adapter it won't run out of power but you need to power it on to use it.
First download the recovery.img file for your flyer.
Then you need to setup the android SDK in your computer.
Boot it into the fastboot mode.
And then you run this commands from your command line
"cd C:\"the path where you have the fastboot file"
"fastboot flash recovery "the path where you have the recovery".img

[Q] Dinc 2 flashing red light, won't boot

I got this Dinc 2 used. When it's plugged into the charger the red light flashes 8-10 times quickly, then after awhile (more than 5 minutes) the "HTC" white screen shows up, then goes back to black. Pressing PWR and Vol- doesn't do anything.
The battery reads about 2.8v and doesn't seem to be charging (that is, the red light goes out after the initial flashes). Will this unit boot with a bad battery?
Do you think there's any hope for this unit? Externally it's in almost perfect shape. The previous owner says he did the HTC unlock.

tgreenstein said:
I got this Dinc 2 used. When it's plugged into the charger the red light flashes 8-10 times quickly, then after awhile (more than 5 minutes) the "HTC" white screen shows up, then goes back to black. Pressing PWR and Vol- doesn't do anything.
The battery reads about 2.8v and doesn't seem to be charging (that is, the red light goes out after the initial flashes). Will this unit boot with a bad battery?
Do you think there's any hope for this unit? Externally it's in almost perfect shape. The previous owner says he did the HTC unlock.
Click to expand...
Click to collapse
could be the battery vould also be the charging port.. bot repairs under $10 a piece. Buy/replace battery first and go from there. phone will not boot without battery..

OK, so I got a new battery and now I can get to the fastboot screen. However, I can't reboot into anything; all I get is the white "HTC" screen for a few seconds, then the screen goes dark, and ten or fifteen seconds later I get the "HTC" screen again, etc. etc. etc.
The HBOOT version was 0.98 something. I was able to run the CRC check, if that information is useful.
osb1: 0x0
amss: 0x60652FC
hboot: 0xC7661188
recovery: 0xE012D109
system: 0xCCE69132
I can't leave the battery in the unit because it will continuously reboot and the battery eventually starts to overheat (I'm guessing that's what happened to the original battery).
Any suggestions?

tgreenstein said:
OK, so I got a new battery and now I can get to the fastboot screen. However, I can't reboot into anything; all I get is the white "HTC" screen for a few seconds, then the screen goes dark, and ten or fifteen seconds later I get the "HTC" screen again, etc. etc. etc.
The HBOOT version was 0.98 something. I was able to run the CRC check, if that information is useful.
osb1: 0x0
amss: 0x60652FC
hboot: 0xC7661188
recovery: 0xE012D109
system: 0xCCE69132
I can't leave the battery in the unit because it will continuously reboot and the battery eventually starts to overheat (I'm guessing that's what happened to the original battery).
Any suggestions?
Click to expand...
Click to collapse
find the latest RUU for the Vivow(thats our phone) and use the RUU on it... Happened to my old ladies phone (Holiday) and that was the only way to get it back... Dont worry you will have to reroot the thing...:silly:

FordNate said:
find the latest RUU for the Vivow(thats our phone) and use the RUU on it... Happened to my old ladies phone (Holiday) and that was the only way to get it back... Dont worry you will have to reroot the thing...:silly:
Click to expand...
Click to collapse
No joy on flashing the RUU. I used
RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_5.10.605.9_Radio_1.09.01.1111_NV_VZW1.92_release_225831_signed
renamed it to PG32IMG.ZIP, placed it in the root directory of my sd card, went into HBOOT. Seemed to read the .zip file, then gave two error messages, something about "no image or wrong image". Then it returns the main HBOOT screen.
It also seemed to be looking for PG32DIAG.ZIP. Is that something that needs to be flashed first?
Any other suggestions?

tgreenstein said:
No joy on flashing the RUU. I used
RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_5.10.605.9_Radio_1.09.01.1111_NV_VZW1.92_release_225831_signed
renamed it to PG32IMG.ZIP, placed it in the root directory of my sd card, went into HBOOT. Seemed to read the .zip file, then gave two error messages, something about "no image or wrong image". Then it returns the main HBOOT screen.
It also seemed to be looking for PG32DIAG.ZIP. Is that something that needs to be flashed first?
Any other suggestions?
Click to expand...
Click to collapse
when i did my ladies holiday it was an .exe file i ran on my pc while her phone was plugged into it.. everything else sorry cant help on. wish i could though

flash this
tgreenstein said:
No joy on flashing the RUU. I used
RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_5.10.605.9_Radio_1.09.01.1111_NV_VZW1.92_release_225831_signed
renamed it to PG32IMG.ZIP, placed it in the root directory of my sd card, went into HBOOT. Seemed to read the .zip file, then gave two error messages, something about "no image or wrong image". Then it returns the main HBOOT screen.
It also seemed to be looking for PG32DIAG.ZIP. Is that something that needs to be flashed first?
Any other suggestions?
Click to expand...
Click to collapse
Here download this (just copy and past in your address bar add www if required and be sure to remove any spaces)
androidruu.com/getdownload.php?file=Vivo_VivoW/RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_5.10.605.9_Radio_1.09.01.1111_NV_VZW1.92_release_225831_signed.exe connect your phone to pc via data cable and run this

ArslanQureshi said:
Here download this (just copy and past in your address bar add www if required and be sure to remove any spaces)
androidruu.com/getdownload.php?file=Vivo_VivoW/RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_5.10.605.9_Radio_1.09.01.1111_NV_VZW1.92_release_225831_signed.exe connect your phone to pc via data cable and run this
Click to expand...
Click to collapse
What mode should my phone be in (FASTBOOT, HBOOT, etc.)? I can't boot the phone normally, and when I run the RUU it doesn't recognize my phone.

Fastboot...i think
tgreenstein said:
What mode should my phone be in (FASTBOOT, HBOOT, etc.)? I can't boot the phone normally, and when I run the RUU it doesn't recognize my phone.
Click to expand...
Click to collapse
fastboot would be appropriate I think best of luck :good:

[Q] Is this Hardware death?

EDIT: I got past the original issue. Please see post #4 instead,
I'm trying to determine if my hardware has gone bunk or whether it's repairable system errors.
_____________________________________________________
Original post:
Hi guys,
I see several recent posts about similar topics but I can't begin to troubleshoot because I can't get past the bootloader.
Here are my specs from the bootloader screen:
INCREDIBLEC XC SHIP S-OFF
HBOOT-0.92.0000
MICROP-0417
TOUCH PANEL-ATMELC03_16ac
RADIO-2.15.10.07.07
Jul 23, 2010, 18:06:51
I use ClockworkMod recovery, but I can't remember the last ROM I had installed, it might have been MIUI 2.3.2.
___________
When I try to start the phone normally it just hangs at the first white "htc Incredible" screen. Tried without an SD card inserted: same behavior.
If I boot into hboot instead and try to launch Recovery, it goes to the white "htc Incredible" screen and hangs indefinitely, whether SD card is in or out.
If instead, from hboot, I try to Factory Reset, it goes to the white "htc Incredible" screen and hangs indefinitely, whether SD card is in or out.
At this point I can't get past the white "htc Incredible" screen no matter what I do.
____________
I issued the "oem enableqxdm 0" command through fastboot to ensure the SD card could be mounted, then took a fresh SD card and loaded the Stock_inc_4.08.605.15 image from dinc.does-it.net and flashed it in hboot. It loaded the image, went to "Parsing…" for a few seconds, then reset to the main hboot screen (not sure if that means it was successful). Still the same outcome: stuck on the first white "htc Incredible" screen, whether simply powering on, launching recovery, or trying to factory reset.
The phone had some previous issues I can describe if anyone thinks it would help (bootlooping unless I held the phone in the freezer long enough to launch AnTuTu and underclock the CPU way down, suggesting a heat issue).
Really I would just like to get some data off of a few saved Nandroids, if I can get the phone working again as a toy for tinkering with that would just be a bonus.
Can anyone tell what my problem is?

Sounds like your recovery is borked somehow. Try fastboot flashing your recovery again (I recommend latest TWRP), and start over.

PonsAsinorem said:
Sounds like your recovery is borked somehow. Try fastboot flashing your recovery again (I recommend latest TWRP), and start over.
Click to expand...
Click to collapse
Thanks for the reply.
I tried flashing the stock recovery image (4.08.605.2) through fastboot but I kept getting the "FAILED (remote: not allowed)". I was able to load it as a .zip through the bootloader though. After rebooting and entering recovery through hboot the recovery partition would flash open, then immediately restart to the white "htc Incredible" screen again where it would hang as long as I let it.
I did notice it was getting really hot just sitting at that white screen so I popped it in the freezer to cool off for a minute. When I opened the freezer a minute later BOOM it's sitting at the home screen, fully booted. Keeping the phone in the freezer, I've since been able to reflash CWM 5.0.2.0 recovery and load my saved Nandroids. As soon as the phone is out of the freezer for 1-2 minutes it does and goes back to the white "htc Incredible" screen and either hangs or bootloops.
So right now I'm running back and forth between the freezer and the charger trying to load each of about a dozen Nandroids, backup my photos, call and sms logs, and move on to the next one. Seems like this method will at least allow me to get my saved data out of the Nandroid backups even if it takes all night.
Two questions:
1) It seems like the phone has a hardware overheating issue. After rescuing my data, I'll probably try to load an undervolted/underclocked kernel to see if it will stay alive under a reduced load...any input on the best choice for such a ROM & kernel?
2) To access my nandroid backups, do I need to load them on to this specific phone? Is there a runtime environment or can BlueStacks or something allow me to virtually load a nandroid backup from my dinc for purposes of getting the data off?
Thanks again.

Here's the situation now:
EDIT: phone went in the trash, life is less stressful.