I was playing with my splash screen and boot animation, and I changed the PB31IMG file on my sd card to a custom splash image. I went to hboot (.92 i think) and it gave me the error "no image found" or something like that. I turned off the phone, and tried to boot up into hboot again by holding volume down+power. As soon as I did, my phone vibrated maybe four times and stayed at a black screen. I can't turn the phone on now, or boot into recovery. Has this happened to anyone else? More importantly, does anyone know how to fix it?
Just to add more information (Im really not sure what's relevant), I was running virtuous 2.6 with hydra #1, 2.15 radio. Also, the image error happened before when I was trying out a different splash screen. That time I deleted the file and re-transfered it my sd card. Hboot was able to recognize it as a splash screen when I rebooted it that time. I'm not sure, but my phone might have booted into clockwork recovery after hboot checked the img file.
One other thing that might be a problem was that I might've been running low on battery. I didn't check, but it was the end of the day and I'm usually almost dead by the time I charge it again.
Never mind.
(Unrevoked forever wiki)
When I try to get into Fastboot by pressing VOLUME UP and booting the phone, my phone instead buzzes three times and acts dead. What happened?
The S-OFF update also enables Qualcomm Diagnostics mode on your phone, which is entered by doing what you just did. You can exit this mode (and boot normally) by removing the battery and USB cable.
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
Hello There!
I have a desire without root access and i have the problem with the white htc screen with the logo... i got it after i tried to install an OTA update yesterday night (i dont remember exactly the version no.)... i tapped on install, phone rebooted and now i s*cked up with the logo... okay, i tried to remove and back the battery, still the same... after that i tried without sim, without memcard nothing happened... after that i tried hard reset with vol.down+pow, erease all data nothing happened... wtf, is it bricked by an official update?! its non-contract phone.
please if you can, help me.
Roland
Run the official RUU manually while your phone is connected via your PC.
You should be able to download it from here via shipped-roms.com
EDIT: Ah.. just read what you mentioned about it being stuck in a bootloop.
Once you download the RUU, like to your Desktop, power off your phone (pull out the battery, and put it back in) (this will switch off your phone)
Hold volume down button. and while holding it press the power button. When the white screen (Bootloader) appears that means you are on the right track (if it doesnt, do the same thing again, power off your phone, and try again)
Now plug in your phone to your pc. (With usb cable) and on the phone it should say HBOOT USB PLUG (white letters with blue background behind the letters)
Press Power button again. Just a short press)
Now there should be "FASTBOOT USB" (white letters with red background behind the letters)
Don't touch the phone anymore
On your PC, start the file you downloaded, and follow the on screen instructions. This installation will take some time, like 15minutes.
thanks for the help, it worked well! after installing the official rom it is booting again. Thanks!
hrace said:
thanks for the help, it worked well! after installing the official rom it is booting again. Thanks!
Click to expand...
Click to collapse
Ok, no problem. Thanks for the response.
I have same problem but when i run the update it completes but goes back to the htc screen and stays there.
I appoligise if this has been asked before.
I have a HTC Desire Z which I have rooted using the Cyanogen Wiki Method which i believe was successful, I wanted to check whether I was S-Off before loading custom roms.
wiki.cyanogenmod.com/index.php?title=HTC_Desire_Z:_Rooting
I read on a forum you should bootload to check, so i held power and VOL up on restart however now i have a black screen with a flashing red led at the top and am unable to get out of this mode does anyone have any advise what I need to do?
Anything would be helpful I'm in the UK military currently deployed on OPS this is my only means of comms to family. Thanks in advance.
Crap, so you're stuck in bootloader huh? Well if you have a PC with you then thats good news. Cause you can just flash something via your bootloader if you have ADB set up.
Wait, you said it has a red led lit right?... the battery might have died on you in all honesty because that's the only time a red/amber led would come on. If this is the case just leave it charging for like 20 minutes before try to turn it on.
Anyways, if that isn't the issue try getting the screen onto that bootloader page. As soon as you get to that you can start fixing it. It should say FASTBOOT_USB or something similar to that. Now on your pc start up your CMD Prompt (Run > 'cmd'). From there try typing Fastboot devices and it should list your device as HT########. If you can get to that then we're doing well.
BEFORE you try this, just note I've never fastboot flashed a ROM and I only posted this because you seem to need it urgently. If you can wait, then post what you've actually done to the phone so I can provide you with a more tailored solution that will work. (post whether the phone is rooted, s-off or superCID or just the guides and where you got stuck)
Now what you need to do is plug your microSD into your laptop and do this:
Aegishua said:
Before you do this please do the following:
1a. Download the RUU I’ve linked (it should be a ~300mb exe file)
1b. Run the setup until you get to the screen with the tick boxes
1c. Goto C:\Users\<your account name>\AppData\local\temp. Then right click and Sort By Date Modified. Look for the most recently created folder which should look like {xxxxxxx-xxxxxx-xxxxxxxx}. Then navigate into it and its parent folder. Look for rom.zip and copy that to your goldcard/memory card.
1d. Rename the rom.zip on your memory card to PC10IMG.zip
1e. Mount your sd card back onto your phone.
Click to expand...
Click to collapse
In this case you want it to be called update.zip. Now you can pop the microSD back into your phone and from there get back into your bootloader and switch to fastboot. Now when it says fastboot_usb you can run this on your PC's CMD Prompt. fastboot update /sdcard/update.zip
did you try something as simple as a battery pull? also, I noted you said power + vol up, you need to do power + vol down to enter bootloader. I seem to remember something similar happening to me back in the day.
chances are it's fine. I'd do a battery pull and boot it normally just to make sure, then power off and enter bootloader to ensure you are s-off by pressing power + vol down.
It is supposed to be volume DOWN + power, I just tried volume up, my phone vibrated 3 times and an orange light flashed continuously, but it was solved by a battery pull, and it was back to normal
Sent from my HTC Desire Z using XDA App
only charge led shows lifesigns.
**moved to new post**
What possibly went wrong (you can skip it if you guys like, I'm not entirely sure if it'll be helpful but I just wanted to be thorough.)
My G2 was working fine for the past year and I had it rooted and running CM since I can remember having it. No problems have ever occurred for me on this phone until today. I woke up and was checking my email on the gmail and yahoo mail app but the yahoo mail app kept crashing so I decided to force close it with Manage Applications and tried to reopen it, but then my phone froze. This was all going on while some of my other apps were updating. I waited for a good 30 minutes but nothing happened so I decided to pull the battery out.
My issues and what I've tried:
So my issue now is that whenever I boot my phone up again the HTC logo would show up like usual but when it transitions to the Cyanogenmod logo with the arrow circling around the Droid icon it becomes a black screen instead or it might be that the phone turns off (I cant tell but to be more specific no lights are on when this happens such as the home or menu button, etc.).
The next thing I tried is to boot into Hboot and do a recovery, but when I run recovery the same thing happens as above. The HTC screen shows up and then it goes into a black screen (I'm almost certain this isnt a hardware issue because I've never damaged my phone enough for the screen to have issues).
Seeing that recovery was hopeless, in a desperate attempt I tried to factory reset the phone through hboot, but it restarts my phone and just hangs at the HTC logo screen indefinitely. On top of all this, whenever I plug the phone to an outlet, the orange led light lights up for a few seconds and then turns off which indicates my phone isnt charging or loses connection with the cable so maybe it's a hardware issue after all?
I've spent the past 4-5 hours trying to find posts with people who've had similar situations, but either the issue was unresolved or the solution provided wasn't specific enough for me to follow (I am next to clueless with software mods). Please help me, I cannot afford a new phone at the moment and will be pretty screwed if I don't get this fixed by Monday. Thank you guys so much in advance!
A little info:
I'm running Cyanogenmod 7.2 I believe, it's the recently updated one.
This is what I see (excluding the options like fastboot, etc.) when I boot my phone while holding vol-
Vision pvt eng s-off
hboot-0.76.2000 (pc1010000)
microp-0425
radio-26.02.01.15_m2
eMMC-boot
Aug 20 2010, 16:51:01
see if you can pull a logcat while booting lopping/black screen
also you can try fastboot. try this
you need fastboot.exe from sdk (in tools or wherever)
open cmd from here (windows hold shift then right click in that folder)
in cmd type
fastboot devices
if your phone pops up you good to proceed if you get waiting for device we need to test some more
if good, continue (in the same folder as fastboot.exe have a recovery image, name it recovery.img)
in cmd type
fastboot -w
then
fastboot flash recovery recovery.img
then
fastboot reboot bootloader
(maybe its fastboot reboot-bootloader)
any way once back to hboot on your phone see if recovery works
Sent from my HTC Vision using xda premium
I'm pretty sure I tried this already, but I just tried it again. Rebooting bootloader makes my phone hang at the HTC screen. I used the img from the clockworkmod site directly and everything worked fine up until the reboot so I guess technically nothing worked :/.
I pulled the battery out and booted into Hboot and then recovery. It still becomes a black screen. Thanks for your help though. I would make a log but I dont know how, mind showing me the steps? Also I'm not 100% sure, so correct me if I'm wrong, but my case isn't with boot loops right? My phone doesnt restart over and over again by itself, it just sort of goes into a black screen and stays there for eternity. It's probably a distinction without a difference though, nothing works.