Develop Bugs

[Q] evo stuck at 4 triangle screen/ bad ruu

whilst attempting to unroot my phone via ruu the other day i hit a brick wall
on a fully charged battery, the process halted and gave me an error 120 (main battery low) the phone rebooted and now all i am left with is 2 screens- one is with a black screen that says htc and has triangles with exclamation points in corners (usb cable connected), the other is a white screen that looks like a fastboot screen but only says ruu and it is unselectable.
I have tried to ruu again, always get battery power error ( have tried several different batteries)
I have installed and unistalled htc sync, removed and reinstalled drivers
i have tried to boot into recovery with power and vol down ( does not work, brings to black htc screen)
tried my best with adb, but cant get it to "see" the phone
(funny enough if i connect it to my laptop pda net sees the phone and tries to connect but cannot)
Ive scoured this forum for solutions, and tried as many as i found all to no avail
I ask you, is my phone bricked? or is there hope still?
i was running koni elite rom,
my hboot is 2.10.0001

Try uninstalling pdanet and anything else that might try to connect to the phone automatically that you don't need for unrooting, like HTC Sync. It could be interrupting the connection somehow. I know that you're getting a low battery error, but it's worth trying.
Even though you cannot get into hboot, try putting a PC36IMG of the RUU on your SD card. Perhaps it'll detect it from the kindasortafastboot screen.
I don't know that either of these things will help, but it's all I've got.
Sent from my Evo + MIUI using Tapatalk!

I truly don't understand why people try to unroot their phones....

have to return phone to sprint, it is still under warranty.

falconlb45 said:
have to return phone to sprint, it is still under warranty.
Click to expand...
Click to collapse
So flash a stock ROM, remove any apps, including SU, and take it back. Is still have yet to see that they busted anyone with S-Off on Hboot. And the good news is, they refurbish it and send out already rooted to someone else.

Can you get into HBOOT after a battery pull and replace without connecting your phone to your computer? If so, you are likely not bricked.
Sent from my PC36100 using XDA Premium App

[Q] Dead phone after update, any way to bring it back

Hi guys, need very quick help from you, as I think I have bricked the phone which suppose to be a Christmas gift for may son. I was trying to revert phone from root and custom rom to stock. I've downloaded older OTA update (one of very first ones with android 2.2) an installed it in bootloader. Phone booted fine, and I went for official update. It showed to me there is update available to android 2.3. I have downloaded it and phone rebooted in to update mode. After progress bar gone to the end it disappeared and phone stayed in that update mode (logo with phone and green arrows shaped it to circle) for nearly half an hour. I though, some thing had to vent wrong so I decided to turn off phone, but power button gave no effect, so I pulled battery out for few seconds. After I have putted it back phone never turned on again. I mean is completely not responding. Pressing power button for even minute doesn't wake it up, it is not possible to go to the bootloader. There is no characteristic vibration when it turns on. Basically it behaves like there is no battery in socket but there is, and it is fully loaded as I charged it before updating. When phone plugged to AC or computer LED is not lighting as well whatsoever.
Please, can any one help with this one? I in rush as phone is a Christmas present for my son who lives in Italy and I supposed to ship this today to make it arrive b4 Christmas. This is why I can not spend to much time on searching forums.
Thank you

Check battery pins
hedeon said:
Hi guys, need very quick help from you, as I think I have bricked the phone which suppose to be a Christmas gift for may son. I was trying to revert phone from root and custom rom to stock. I've downloaded older OTA update (one of very first ones with android 2.2) an installed it in bootloader. Phone booted fine, and I went for official update. It showed to me there is update available to android 2.3. I have downloaded it and phone rebooted in to update mode. After progress bar gone to the end it disappeared and phone stayed in that update mode (logo with phone and green arrows shaped it to circle) for nearly half an hour. I though, some thing had to vent wrong so I decided to turn off phone, but power button gave no effect, so I pulled battery out for few seconds. After I have putted it back phone never turned on again. I mean is completely not responding. Pressing power button for even minute doesn't wake it up, it is not possible to go to the bootloader. There is no characteristic vibration when it turns on. Basically it behaves like there is no battery in socket but there is, and it is fully loaded as I charged it before updating. When phone plugged to AC or computer LED is not lighting as well whatsoever.
Please, can any one help with this one? I in rush as phone is a Christmas present for my son who lives in Italy and I supposed to ship this today to make it arrive b4 Christmas. This is why I can not spend to much time on searching forums.
Thank you
Click to expand...
Click to collapse
After reading what you said i think that you placed battery wrong. Check the pins inside the phone with battery pins.

whiperhack said:
After reading what you said i think that you placed battery wrong. Check the pins inside the phone with battery pins.
Click to expand...
Click to collapse
That was my first idea too but, no m8, battery is placed ok....

Try pressing volume down+power button for a while then leave the power button while still pressing the voulme key. You should boot into the bootloader.

if4ct0r said:
Try pressing volume down+power button for a while then leave the power button while still pressing the voulme key. You should boot into the bootloader.
Click to expand...
Click to collapse
Tried that too, still dead

Try connecting you DHD to the PC.
Download one of these Stock RUU's : http://shipped-roms.com/index.php?category=android&model=Ace
Run the installer from PC. See if it detects the device.

if4ct0r said:
Try connecting you DHD to the PC.
Download one of these Stock RUU's : http://shipped-roms.com/index.php?category=android&model=Ace
Run the installer from PC. See if it detects the device.
Click to expand...
Click to collapse
I understand I should not be worried that all of these RUU's are listed as for model: ACE?

Not at all. 'Ace' is the codename HTC gave to Desire HD/Inspire. Just choose the RUU that fits your location(i.e. WWE stands for WorldWide Edition).

if4ct0r said:
Not at all. 'Ace' is the codename HTC gave to Desire HD/Inspire. Just choose the RUU that fits your location(i.e. WWE stands for WorldWide Edition).
Click to expand...
Click to collapse
OMG! I was previously looking for stock roms and everytime I ended up on that site from your link I was annoyed that someone is giving a wrong link to roms for wrong phone. Silly me!
I am downloading right now.

if4ct0r said:
Try connecting you DHD to the PC.
Download one of these Stock RUU's : http://shipped-roms.com/index.php?category=android&model=Ace
Run the installer from PC. See if it detects the device.
Click to expand...
Click to collapse
No it says phone not connected (error[170])

hedeon said:
No it says phone not connected (error[170])
Click to expand...
Click to collapse
My idea is to double check again the battery position in the socket and if it is ok try to leave it 5 minutes alone on the AC adapter. If this will not give good results, go to the appropriate HTC representative.

when you connected it to your computer... did it ask you to install qload drivers?
if not, go into device manager on your computer, then plug in your phone. If you see an unknown device that shows as qload something or other, then sorry to say, its bricked.
The only way to recover it now is via jtagging or replacing the mainboard (which generally is what they do when you send it in for warranty repair)

whiperhack said:
My idea is to double check again the battery position in the socket and if it is ok try to leave it 5 minutes alone on the AC adapter. If this will not give good results, go to the appropriate HTC representative.
Click to expand...
Click to collapse
Yes, I thought about it as phone behave like it has no power at all. But this is not the case, as I have been flipping that and another battery in every possible position. And I know which one is correct as I can see where pins are in battery pocket. I left it alone under charging and other time with no battery at all hoping that will hard reset phone. No effect at all .
JSLEnterprises said:
when connected to your computer... did it ask you to install qload drivers?
if not, go into device manager on your computer, then plug in your phone. If you see an unknown device that shows as qload something or other, then its bricked, sorry to say
Click to expand...
Click to collapse
I had drivers previously installed. But I am not entirely sure are we talking about same thing as I don't know what QLOAD is. Anyway comp doesn't see any recognised or unrecognised device that could be my phone...
I am not worrying about damn phone as if it is hard bricked tech guys in service will not probably spot that it was rooted. So they will replace, or if not I will go to insurance company. Problem is it takes to much time, I wont make it b4 Christmas.
Thank you guys,
anyone has some other ideas? Please...

desperation bump

Sorry.. It really seems to be beyond software-repair, If it cannot boot in the bootloader or be recognized by PC there's really not much we can do. We need the device to start in some way.
Although one last thing that we haven't tried and can try is to see if it can be accessed via adb or fastboot. (Although I highly doubt it since the RUU also wasn't working).
I've attached the adb and fastboot files required to test that. Extract it, double-click on StartHere.bat and type "fastboot reboot" or "adb reboot". If it returns an error citing device not found then this too has failed.
(This probably wont work.. desperate action)
Another silly thing that might be tried is to try to put your phone on charging via a charger(not USB via PC) and then try to switch it on. Try normal switching, switching on to bootloader(volume down press)...
If these don't work then you really should give it to the repair center.. you're right that they wont probably realise that it was rooted and would probably change the main board.

if4ct0r said:
Sorry.. It really seems to be beyond software-repair, If it cannot boot in the bootloader or be recognized by PC there's really not much we can do. We need the device to start in some way.
Although one last thing that we haven't tried and can try is to see if it can be accessed via adb or fastboot. (Although I highly doubt it since the RUU also wasn't working).
I've attached the adb and fastboot files required to test that. Extract it, double-click on StartHere.bat and type "fastboot reboot" or "adb reboot". If it returns an error citing device not found then this too has failed.
(This probably wont work.. desperate action)
Another silly thing that might be tried is to try to put your phone on charging via a charger(not USB via PC) and then try to switch it on. Try normal switching, switching on to bootloader(volume down press)...
If these don't work then you really should give it to the repair center.. you're right that they wont probably realise that it was rooted and would probably change the main board.
Click to expand...
Click to collapse
Sigh... I got "waiting for device" forever in CMD... As you said, it's dead. Gonna send it to HTC in Monday...
Thank you all, appreciate your time

Hello hedeon,
I have the same experience today, as you state in the first post in this thread.
Did you, and how solve the problem?
Is there people with the same problem? This morning I receive notification about system update for my HTC Desire HD. The rest is exactly same problem from the top of this story = death + death + death.....

The problem is that you PULLED THE BATTERY WHILE UPDATING! Have some paitience. I switched on my DHD after 3 months and it needed updating. Takes around 20 mins to complete update
Sent from my HTC Desire HD A9191 using xda premium

GuyInTheCorner said:
The problem is that you PULLED THE BATTERY WHILE UPDATING! Have some paitience. I switched on my DHD after 3 months and it needed updating. Takes around 20 mins to complete update
Sent from my HTC Desire HD A9191 using xda premium
Click to expand...
Click to collapse
May be, but updating started with downloading, then resetting, and then green line was growing up to 1/3 of total size, and at that size stay more then 20 min. Then I try to to push every button, and every combination of buttons, and after 10 minutes more I had pull battery out.
Was it too impatient ?

What was the Android version before you rooted if you can remember and which tool did you use to root?
From what you wrote earlier, it asked you for a 2.3 update which means you probably flashed a Froyo RUU as stock, to bring the phone back to stock ofc.
However, if your DHD came with stock Gingerbread, flashing a Froyo RUU will most definitely screw the phone. I'm not sure if it's beyond repair atm or not, but if that was the case, even if you didn't mess with the battery, chances are the phone would never boot anyway.
Look into AAHK thread, I think there is a good how to there.

Screen black in HBOOT, Recovery, and won't boot

Hello, I know that there have been posts in the past to address this, but I haven't found one yet that has valid links to the files needed.
I was following the instructions in this thread, and the problem occurred when I followed the instructions linked in step 3.
Does anybody know of a location where I can get the files and good instructions for fixing this brick?

If you cant get into hboot, im afraid there isnt anything you can do, the phone is bricked. Does it vibrate or do anything att all.
There is a known issue where flashing a wrong clockworkmod recovery to the wrong screen type can leave the phone functional but without the screen working. That is probably what you were thinking of. If you didnt flash an older version of cwm right before trying to enter hboot to do the ruu, then this is not your issue.

I can get the phone to vibrate like it's turning on by holding the poer button down, but nothing else. I did not flash any new recoveries, I've been on the latest CWM for a while.

Just for anybody else who might need it, I finally found a PB31IMG.zip that works to get back to stock 2.3.4
Link

Thanks
Sent from my Incredible using XDA App

Droid Incerdible 1 vibrate when turned on but black screen
I'm new to the site and maybe this has been answered. But I have a droid incredible rooted. It will charge and the orange light will appear but when I attempt to turn on the phone it will vibrate once but the screen remains black, when connected to a computer and the power the phone on and it vibrates once the computer can detect it.
I do not have any of the files need for the phone on my sd card due to old one being lost so I know I need them, as well as the proper htc sync software. If someone could point me in the right direction that would be awesome

Boostedk said:
I'm new to the site and maybe this has been answered. But I have a droid incredible rooted. It will charge and the orange light will appear but when I attempt to turn on the phone it will vibrate once but the screen remains black, when connected to a computer and the power the phone on and it vibrates once the computer can detect it.
I do not have any of the files need for the phone on my sd card due to old one being lost so I know I need them, as well as the proper htc sync software. If someone could point me in the right direction that would be awesome
Click to expand...
Click to collapse
See the link in cmlusco's sig, above. You should be able to find all the files you need and more there.

boot loop - probably bricked

Hello,
I wanted to debrand my htc wildfire s, and after many unsuccessful attempts (main version older) following other tutorials on the forums, I finally went to this one:
http://forum.xda-developers.com/showthread.php?t=1162971
Followed it step by step, everything was as expected until the flash in the end finished and the phone, instead of booting, entered boot loop.
Now when I try to boot it or to enter bootloader, the backlight turns on for a second, turns off after that, then again turns on for a second, off... and etc. It doesn't even show the HTC screen. When I turn it off and connect it to usb - it charges.
I am already assuming the worse, but if anyone has any ideas, it will be great, as this is my girlfriend's phone and I can already see the tears in her eyes when she understands the phone is dead... :'(

Can you get the phone into hboot?
Pull battery,
then put it back in,
then hold volume down and press power while still holding volume down
If luck is on your side you should be in hboot

Unfortunately I have tried that already - still the same backlight on / off / on ... loop. :-/

Try battery out, back in, connect USB, then try to boot into bootloader. See if your PC picks it up. If it does try to issue the fastboot command "fastboot reboot recovery" and see if it goes.
Also does it vibrate when its having its flashy seziure?
sent from my android powered beast!

Hi,
Thanks for the suggestion. Tried that also - unfortunately - no vibration (qualcom diagnostics seems to not be the case - unfortunately).
Connecting it to usb brings the orange "charging" light for a 5-10 secs, after that the phone tries to boot and enters the bootloop again.
I think after 5 HTC phones, I will finally have one matching my avatar... :'-(

Hmm. Does the PC pick it up at all?
sent from my android powered beast!

No, it doesn't
I am probably going to go buy a new identical phone today afternoon...

try going into recovery, wipe data and cache and try again the process

simaka said:
No, it doesn't
I am probably going to go buy a new identical phone today afternoon...
Click to expand...
Click to collapse
Whoa, I wouldn't be so hasty. Try taking your old one to a service first, it'll cost you a lot less

@johnnyspritz
I am thinking about sending it back to repair, the phone is still under the 2 years warranty. However if they find a way to read the contents of the boot or system partition (JTAG?), they might have some arguments against applying the warranty :-D

Hi Simaka,
Like you my phone is in the same boot loop....
Can't access to Bootloader, no HTC Logo.
I have try to contact HTC, but the mail they send me was out of context ....
If you find any solution, please share it ;-)

Hi, for sure I will. For now I will try to return it in the shop where I bought it as it is still s-on and locked bootloader, so they might agree to take it back. I checked the possibility to buy JTAG connection equipment, but it amoints to 150€ with shipping, plus probably a month or 2 of troubleshooting...
One interestimg thing to note is that during the procedure described on the link above the current rom version in misc.img before editing it was 9.9.9.9
I believe this was a way of artificially imposed restriction so any attempt to update would fail...
Sent from my HTC Desire using xda premium

Phone is bricked due to radio malfunction. Idk if there is a way to fix it but other than that ur bricked

Hi, I had a phone call from HTC.
They cannot say if its broken, I have to send it to the support.

I also got phone call from my service - they are looking into it
Sent from my HTC Desire using xda premium

Just a final update, i got a new phone that was easy to unlock boot. The end
Sent from my HTC Desire using xda premium

Phone Dead After Recent OTA Update

Hi All,
First of all I'm not a native english speaker and I'm a noob in this stuff o rom's .
I recently bought a phone and on update it to JB 4.1.1 with Sense 4+ . Everything went ok and the phone apparently was working ok.
The next day I just noticed that the bluetooth was not 100% because I had some cuts in the sound when connected to a bluetooth headset. Because of this I looked for another OTA update and it found one that said somethink like "General System Improvement" or something like that.
I've installed it but this update didn't went till the end since I get stucked on the "red sign" indicating some fail. I try to reboot the phone but apparently he was dead.
After a lots of tries and key combinations I was able to enter the boot mode and choose to restore to factory mode, but apparently it was not successful. Then I tried and option to check for CRC of img files I think (not sure because don't remeber). It check for 3 images files showing the CRC code, then I think the phone get stucked on one because I still have the waiting message but nothing else happens.
I pressed power button again trying to reboot the phone but since then then phone died completly. The only sign of life is when I connect to the PC windows emits the sound of detecting something but gives an error related to the drives.
Sometimes I get a message saying that a ARX device was found but not anymore.
Tried almost everything that I could read on this forum but nothing seems to work...I think the phone is looping on the boot or doesn't have any battery...not sure.
I've tried some RRU but they fail to find the phone saying not connected or not detected.
Any help will be greatly appreciated, Thanks
Johny

Sent it back for warranty repair as soon as you can this is a known fault as it happened to me recently.
Similar problems: http://forum.xda-developers.com/showthread.php?t=2075862
Getting out of APX mode

Your bootloader isn't locked right? Or were you ever rooted? If the answer is no, just send it to HTC and your warranty will do the rest.
Sent from my HTC One X using xda app-developers app