Develop Bugs

I've bricked my flatmate's Desire? [FIXED, thanks]

NOTE: THIS ISSUE HAS BEEN FIXED, See this post #97 by "teppic74" for how I fixed the phone
My flatmate recently got a Desire from Vodafone, it's got their latest ROM on it with all their bloatware.
I told him I could debrand it, but the goldcard method didn't work because he had bootloader 0.83.
So I followed a thread to this site on how to downgrade the bootloader:
http://www.tolxdorff.net/tutorials/?step=2
So I did step 4... and then the screen went blank. I left it for a while, I thought it may be installing...
After a long time, I pulled the battery out and rebooted the phone ... I'm pretty nervous by this point LOL
Anyway, the phone reboots and I can hear the annoying HTC chime, which never happened on the Voda rom...
But I can't see anything. It appears that the phone is booting up, but the screen is not working.
Anyone got any advice on what I might do to fix this or am I toast? Grateful for any advice.

Have you try it again or download a original rom (maybe on vodafone...on my o2site it give a original rom and also here on xda)...or have you tried unrevoked...what say the h boot now..?????
with kind regards...Alex

Unforunately that's the problem... the phone is working and booting up, but the screen is blank... so I can't see anything.
I'll try to find and flash the voda rom, that's a good idea

mmm_ok said:
Unforunately that's the problem... the phone is working and booting up, but the screen is blank... so I can't see anything.
I'll try to find and flash the voda rom, that's a good idea
Click to expand...
Click to collapse
so you cant even get into recovery?

mmm_ok said:
Unforunately that's the problem... the phone is working and booting up, but the screen is blank... so I can't see anything.
I'll try to find and flash the voda rom, that's a good idea
Click to expand...
Click to collapse
you have no acsess to bootloader or recovery.....??
try vol down (hold it) and phone on (power)...

Well... I think I can get into recovery... it's just I can't tell because the screen is not showing anything...
if I was to make a noob guess at what's wrong, and this is unsubstantiated, it's that it's a new desire with SLCD screen and that it's get the driver for the AMOLED screen installed when I downgraded...

Two more people over at modaco at reporting the same issue, I think:
http://android.modaco.com/content/h...o-com/315329/ive-bricked-my-flatmates-desire/
http://android.modaco.com/content/htc-desire-desire-modaco-com/315332/borked-recovery-image/

Test your theory.
Pull out the battery and put it back in.
Press and hold volume down and birefly press power on.
Keep volume down pressed for 5 seconds, then release it.
Count 20 seconds, then press the power key briefly once more.
You should now be in fastboot.
Connect your phone to the USB port and it should list it self when you execute fastboot devices.
If see it listed, you can restore the original ROM via the vodafone RUU file.

mmm_ok said:
Well... I think I can get into recovery... it's just I can't tell because the screen is not showing anything...
if I was to make a noob guess at what's wrong, and this is unsubstantiated, it's that it's a new desire with SLCD screen and that it's get the driver for the AMOLED screen installed when I downgraded...
Click to expand...
Click to collapse
have you try phone on...wait 3-5 min and flash the original rom....or maybe a original ota with h boot 092...maybe windows recognizes the phone

georgemv said:
Test your theory.
Pull out the battery and put it back in.
Press and hold volume down and birefly press power on.
Keep volume down pressed for 5 seconds, then release it.
Count 20 seconds, then press the power key briefly once more.
You should now be in fastboot.
Connect your phone to the USB port and it should list it self when you execute fastboot devices.
If see it listed, you can restore the original ROM via the vodafone RUU file.
Click to expand...
Click to collapse
not bad...that is what i think too
edit: but better explained

mmm_ok said:
Two more people over at modaco at reporting the same issue, I think:
Click to expand...
Click to collapse
Correct that's me.
I tried a normal boot, unrevoked found the phone but got stuck waiting for boot loader.

I did follow the test you mentioned regarding fastboot.
Windows did make a bleep bleep sound when i plugged it in, but when I ran adb devices (is that what you meant when you asked "is it listed"?), there were no devices listed.
The phone does make the annoying htc sound on normal boot... just no screen

mmm_ok said:
I did follow the test you mentioned regarding fastboot.
Windows did make a bleep bleep sound when i plugged it in, but when I ran adb devices (is that what you meant when you asked "is it listed"?), there were no devices listed.
The phone does make the annoying htc sound on normal boot... just no screen
Click to expand...
Click to collapse
nothing in the list also not unknown...?

Alex-V said:
have you try phone on...wait 3-5 min and flash the original rom....or maybe a original ota with h boot 092...maybe windows recognizes the phone
Click to expand...
Click to collapse
Thanks I did try to flash an original ROM... but I get the same problem I had before when running the RUU (error 140)
If I find a .92 ROM, i'm not sure I can install it without seeing what's on the screen though...

Alex-V said:
nothing in the list also not unknown...?
Click to expand...
Click to collapse
Nah, it just says "List of devices attached" and then nothing

mmm_ok said:
I did follow the test you mentioned regarding fastboot.
Windows did make a bleep bleep sound when i plugged it in, but when I ran adb devices (is that what you meant when you asked "is it listed"?), there were no devices listed.
The phone does make the annoying htc sound on normal boot... just no screen
Click to expand...
Click to collapse
ADB will not find your phone in fastboot. You need to download fastboot binary and run fastboot devices to list devices in fastboot mode. If you use windows, you also need to install the fastboot windows driver. (I think you can find that in the android SDK)

I no longer even get the startup beep. Think I am totally screwed?

georgemv said:
ADB will not find your phone in fastboot. You need to download fastboot binary and run fastboot devices to list devices in fastboot mode. If you use windows, you also need to install the fastboot windows driver. (I think you can find that in the android SDK)
Click to expand...
Click to collapse
Thanks for your help. I'm working on it. Get back to ya soon.

SavageCore said:
I no longer even get the startup beep. Think I am totally screwed?
Click to expand...
Click to collapse
I'm getting the bleep bleep cause I tried to install the generic rom... you're probably not getting it because you only tried to root the existing rom, is that correct?

yeah i used this driver...open attached htm file (if you have download unrevoke...its also in) adb

[Q] Phone dropped into water, can I RUU back?

Hey guys!
I need a little help: my phone has rebelled against the law of physics and somehow slipped from the side of the bath into the hot water. Basically everything works, but the screen's touch.
No problem, I've made a contract with my carrier for such case.
But I'm running Cyanogenmod 10. I'd like to RUU it back to Sense. Should I try it before I take it to the carrier? Do I have to interract with the screen during the process of RUU?
I've connected my phone in fastboot mode, my computer recignizes it perfectly.
Thanks for your help!

Bump.

You're phone will not be repaired if its water damaged.
Its beyond "economic Repair"
Sorry :/

Wilks3y said:
You're phone will not be repaired if its water damaged.
Its beyond "economic Repair"
Sorry :/
Click to expand...
Click to collapse
I know, but as I had stated I have made +warranty with this device for such cases with the carrier.
Nvmd, starting to RUU back.

Since it is obviously not a software failure i don't think you have to revert back to stock. I am pretty sure it will work to go back as far as "fastboot devices" and "adb devices" gives you back an adequate info.
If it was me and i had some spare time i'd revert it anyway, just to be sure.
regards

two_handed said:
Since it is obviously not a software failure i don't think you have to revert back to stock.
If it was me and i had some spare time i'd revert it anyway.
regards
Click to expand...
Click to collapse
Ok, thanks.

I got an error during the instalation, and now I only have black screen with a HTC logo on it, can't enter download mode.
Can anyone help?

What Error? Black Screen with HTC-Logo is some sort of a download mode - its RUU"downloadmode". normally u do an h-boot upgrade in it.

two_handed said:
What Error? Black Screen with HTC-Logo is some sort of a download mode - its RUU"downloadmode". normally u do an h-boot upgrade in it.
Click to expand...
Click to collapse
it only said something like error occured, installation stops. Phone keeps rebooting itself
Edit: managed to connect it to pc, and "fastboot devices" command and "fastboot getvar version-main" works. Will try to run the RUU again
Edit 2: Error [170]: Usb connection error.

be sure to follow the correct how to step by step. also remember you cant downgrade h-boot if you upgraded once.

two_handed said:
be sure to follow the correct how to step by step. also remember you cant downgrade h-boot if you upgraded once.
Click to expand...
Click to collapse
I was following this: http://forum.xda-developers.com/wik...ashing_a_RUU_to_completely_restore_your_phone
How do I know if had upgraded hboot before?
Edit: Ok, it seems the main problem it got disconnected is because the phone keeps rebooting itself.
Edit2: ruu_log: https://dl.dropbox.com/u/17916569/RUU_121112T104648.log
https://dl.dropbox.com/u/17916569/RUU_121112T110331.log

Silgrond said:
I was following this: http://forum.xda-developers.com/wik...ashing_a_RUU_to_completely_restore_your_phone
How do I know if had upgraded hboot before?
Edit: Ok, it seems the main problem it got disconnected is because the phone keeps rebooting itself.
Click to expand...
Click to collapse
Howto is ok. Stick to it. Plug in the phone to your wall charger first to make sure you have got enough power. In the fastboot bootloader you can see your current H-Boot but not if you upgraded it. If you can't remember doing anything to your H-Boot you didn't upgrade i guess...

two_handed said:
Howto is ok. Stick to it. Plug in the phone to your wall charger first to make sure you have got enough power. In the fastboot bootloader you can see your current H-Boot but not if you upgraded it. If you can't remember doing anything to your H-Boot you didn't upgrade i guess...
Click to expand...
Click to collapse
The battery should be around 90%. How can I stop from constantly rebooting it? I can't even turn it off.
By the way the only thing I remember is that I have upgraded a few months through OTA, and I needed to get a newer RUU. Not sure if the hboot got upgraded or not.

Silgrond said:
The battery should be around 90%. How can I stop from constantly rebooting it? I can't even turn it off.
By the way the only thing I remember is that I have upgraded a few months through OTA, and I needed to get a newer RUU. Not sure if the hboot got upgraded or not.
Click to expand...
Click to collapse
I only have one idea to turn it off is to throw it to water. -.-

Maybe it is more defective than we thought. Try pressing the power button really long and or.press volume up to enter fastboot. Otherwise just send it in, if it constantly reboots the Tec guys can't to much, too.
Remember to press the thank you button..!
Sent from my EndeavorU using xda app-developers app

two_handed said:
Maybe it is more defective than we thought. Try pressing the power button really long and or.press volume up to enter fastboot. Otherwise just send it in, if it constantly reboots the Tec guys can't to much, too.
Remember to press the thank you button..!
Sent from my EndeavorU using xda app-developers app
Click to expand...
Click to collapse
Aye, that's it. Thanks for your help

Unable to get into bootloader or recovery mode, stuck at white HTC logo screen

Hey everyone,
I have read the various topics with a similar title but none helped.
Here is my problem, I bought a used HTC Desire on eBay. It booted just fine on the first start, then I did a factory reset (from within the Android system menu).
Since then, I'm stuck at the white screen with the green HTC logo. I have tried to get into bootloader mode by removing the battery, holding vol down and power, but it just goes straight to the white screen again.
Also connected the phone to the pc, but adb isn't picking up anything...
Any ideas?

Try Power+Back button.

just got one step further:
I can get into fastboot mode with BACK + POWER. But volume keys doesn't work, is that a known issue that I can solve somehow?

Goddchen said:
just got one step further:
I can get into fastboot mode with BACK + POWER. But volume keys doesn't work, is that a known issue that I can solve somehow?
Click to expand...
Click to collapse
So you bought a Desire with broken volume keys.
Are you s-off?

abaaaabbbb63 said:
So you bought a Desire with broken volume keys.
Are you s-off?
Click to expand...
Click to collapse
looks like...
in fastboot mode it shows that it is s-on.

Goddchen said:
looks like...
in fastboot mode it shows that it is s-on.
Click to expand...
Click to collapse
Then you'll have to flash a RUU to make it work.
http://forum.xda-developers.com/showthread.php?t=1772499
It's official HTC Firmware. Your phone will boot after this.
So:
1. Install HTC Sync.
2. Download and extract the RUU.exe from the zip (It's somewhere in there)
3. Run the exe while you connect your phone in fastboot (Power+Back)
4. Wait for it to install
5. Boot

abaaaabbbb63 said:
Then you'll have to flash a RUU to make it work.
http://forum.xda-developers.com/showthread.php?t=1772499
It's official HTC Firmware. Your phone will boot after this.
So:
1. Install HTC Sync.
2. Download and extract the RUU.exe from the zip (It's somewhere in there)
3. Run the exe while you connect your phone in fastboot (Power+Back)
4. Wait for it to install
5. Boot
Click to expand...
Click to collapse
Thanks for the advice, I downloaded the 2.3 RUU and it starts the process, sais
rebooting to bootloader
erasing data
sending...
and after ~30 seconds it just shows me a screen that sais "ERROR_UNKNOWN"
On the phone I see a black screen with a silver HTC logo during the process and when I unplug the USB cable after the error it shows the hboot screen that now sais "update failed".

right before the error is shown it display "updating signature"

Goddchen said:
right before the error is shown it display "updating signature"
Click to expand...
Click to collapse
It only says "Error_Unknown"? No error number, anything?
Weird.
This may be the reason:
Now, that may not sound too bad to some of you, but there's more: the 2.3 RUU update is limited regionally, as well. It's not available to users in Germany, North America, South America, South Korea, or Japan.
Click to expand...
Click to collapse
You live in Germany, right?
Use this guide then:
Section 2, S-on
http://forum.xda-developers.com/showthread.php?t=1275632

yes I am in Germany,
made some progress (or not?)
I noticed that the device was "unlocked", so I did "fastboot oem lock" and it was "relocked".
Then the RUU update went through - nearly. At the very end if failed again and now I am stuck at a black screen with the silver HTC logo and triangles in every corner.

AW: Unable to get into bootloader or recovery mode, stuck at white HTC logo screen
Sent from my Nexus 4 using xda app-developers app

wtf... tried again flashing the 2.3 RUU, this time it worked, YEAY
But now I have a bootloop, device starts, vibrates 1 time, waits for 3 seconds, and then vibrates 7 times. And restarts...

Ok. Tests are done.
According to the screenshot above and the 7 vibrations, you have a radio brick. It's a brick that can hardly be overcome.
The only solution is flashing the RUU and hoping that the phone will eventually boot.
That's why I don't buy second hand phones.
This thread might help:
http://forum.xda-developers.com/showthread.php?t=1793369

abaaaabbbb63 said:
Ok. Tests are done.
According to the screenshot above and the 7 vibrations, you have a radio brick. It's a brick that can hardly be overcome.
The only solution is flashing the RUU and hoping that the phone will eventually boot.
That's why I don't buy second hand phones.
This thread might help:
http://forum.xda-developers.com/showthread.php?t=1793369
Click to expand...
Click to collapse
freecer did it, was able to flash the 2.3 RUU again successfully. But now I'm back at the bootloop, but now, it simply does vibrate once (no more 7 vibrations) and reboots after some seconds.
So what can I do now? RUU flashed successfully, I'm running out of ideas...

and again the freezer did it, put it in, normally started via POWER button, it booted right through into Android.
Well, let's see if it keeps running now or if this overheating issue also exists in normal operation mode...
Thanks so much for you help so far, the freezer hint saved this device and hopefully will make my gf very happy tomorrow

Hold on I thought it was some pvt1 devices that had overheating issues.
Thought it was fixed on your newer ones. Then again I've never had a problem with my pvt1 desire flashed both hboot and find countless times.
Sent from my GT-I9100 using xda app-developers app

dethrat said:
Hold on I thought it was some pvt1 devices that had overheating issues.
Thought it was fixed on your newer ones. Then again I've never had a problem with my pvt1 desire flashed both hboot and find countless times.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
it is a PCT3 device.
but the overheating-reboot issue is rendering it useless. I can use it just fine outside (-2° currently) but as soon as I'm inside, boot-loop...
Anything I can do from a hardware perspective to fix that? Sending it in for repair/replacement is not an option, it's simply not worth the cost.

do you think installing a custom rom of any kind might help?

Goddchen said:
it is a PCT3 device.
but the overheating-reboot issue is rendering it useless. I can use it just fine outside (-2° currently) but as soon as I'm inside, boot-loop...
Anything I can do from a hardware perspective to fix that? Sending it in for repair/replacement is not an option, it's simply not worth the cost.
Click to expand...
Click to collapse
It's a motherboard fault. If you don't send it to repair, you just got yourself an "Ice-Phone", or a very complex paper holder.

i think a custom rom would help a small bit, like the rom in abaaaabbbb63 sig (mildwild redux) because its small and lite unlike a sense rom. therefor it mite not overheat as quick or as often. but thats only a guess. the only dodgy thing is trying to get ur phone s-off or rooted because if ur phone overheats in the middle of the s-off/rooting progress u could brick ur phone. plus charge ur phone using ur computer coz it uses less power and the phone does'nt heat up as much as plugging into the wall.

HTC Desire HD won't boot.. help!

Ok guys, I definitively need your help now.
This morning I woke up, i toke my phone (already on) and I saw that keyboard didn't work anymore, so I rebooted it and appeared the white screen with HTC LOGO, then three or four vibrations and BUM... FREEZED.
The phone is rooted, with custom rom. S-OFF.
The problem is that i can't enter into RECOVERY of the phone anymore, but I can still enter into BOOTLOADER. I tried to do a FACTORY RESET, but doesn't work (the display show again the htc logo with some vibrations before the freeze).
There is some way to format/repair with the help of PC ? Like when i changed my RADIO some weeks ago... or.. I don't know.
Thanks.

DjMatrix619 said:
Ok guys, I definitively need your help now.
This morning I woke up, i toke my phone (already on) and I saw that keyboard didn't work anymore, so I rebooted it and appeared the white screen with HTC LOGO, then three or four vibrations and BUM... FREEZED.
The phone is rooted, with custom rom. S-OFF.
The problem is that i can't enter into RECOVERY of the phone anymore, but I can still enter into BOOTLOADER. I tried to do a FACTORY RESET, but doesn't work (the display show again the htc logo with some vibrations before the freeze).
There is some way to format/repair with the help of PC ? Like when i changed my RADIO some weeks ago... or.. I don't know.
Thanks.
Click to expand...
Click to collapse
That sounds like a fried motherboard. Try flashing a RUU from fastboot usb. If after the flashing the phone keeps not booting, then your motherboard needs to be replaced.
If you need help with the flashing read the guide in my signature to find out how to perform that stuff. :victory:

glevitan said:
That sounds like a fried motherboard. Try flashing a RUU from fastboot usb. If after the flashing the phone keeps not booting, then your motherboard needs to be replaced.
If you need help with the flashing read the guide in my signature to find out how to perform that stuff. :victory:
Click to expand...
Click to collapse
Sorry what guide i need to follow, and where I can find this "RUU" for my phone? Thanks ^^

DjMatrix619 said:
Sorry what guide i need to follow, and where I can find this "RUU" for my phone? Thanks ^^
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=30020025&postcount=7

glevitan said:
http://forum.xda-developers.com/showpost.php?p=30020025&postcount=7
Click to expand...
Click to collapse
Ok, installed RUU in my phone, but it's still vibrating 7 times. No other chances I suppose... right?

DjMatrix619 said:
Ok, installed RUU in my phone, but it's still vibrating 7 times. No other chances I suppose... right?
Click to expand...
Click to collapse
Check or volume rocker/keys. On the mytouch 4g, when u press volume up and power key while phone is off, it vibrates and the notification light blinks red. So maybe or volume up key is stuck.
Sent from my Desire HD using xda app-developers app

M9 maybe total brick after stock flash

My htc m9 upgraded to 6.0 i tried to downgrade with official
5.0 the flashing process went faster than usual
It asked me to reboot and it never came back to live
No charging led nothing and my pc does not even feel it when
I connect it
Please i appreciate any help thx

Not sure if tried or not.... Have you tried simply holding down Power and both volume keys to force a restart? Seems odd that it would brick the phone.
Normally when an RUU sees that your phone has a newer software it would just fail and the phone would be fine. Unless you're S-OFF in which case it would flash it anyways.
We need more details.
1. Did it successfully upgrade to 6.0 and you had no issues prior to trying to downgrade?
2. How did you try flashing it? Was it the RUU wizard on Windows, or the rom.zip via a command prompt/terminal

Pique91 said:
My htc m9 upgraded to 6.0 i tried to downgrade with official
5.0 the flashing process went faster than usual
It asked me to reboot and it never came back to live
No charging led nothing and my pc does not even feel it when
I connect it
Please i appreciate any help thx
Click to expand...
Click to collapse
Can you boot to the bootloader from power off state (POWER+VOLDOWN)? If so, hope is not lost.

Pique91 said:
My htc m9 upgraded to 6.0 i tried to downgrade with official
5.0 the flashing process went faster than usual
It asked me to reboot and it never came back to live
No charging led nothing and my pc does not even feel it when
I connect it
Please i appreciate any help thx
Click to expand...
Click to collapse
Are u downgrade using 0PJAIMG RUU zip? If yes so sad for you.
OMJ said:
***WARNING, BRICK RISK*** ONLY FLASH A 0PJAIMG RUU TO UPGRADE, DOWNGRADING MAY RESULT IN BRICK!!!
Click to expand...
Click to collapse

I suspect you are hardbricked (why on earth did you downgrade?) but it's possible the flash got confused somehow. Try holding down all three buttons while the phone is plugged in for at least minute. If that does nothing, leave it plugged in overnight and try it again. If it's still dead, you have a brick. Next time, be more careful about flashing random stuff you find via Google.

Tachi91 said:
Not sure if tried or not.... Have you tried simply holding down Power and both volume keys to force a restart? Seems odd that it would brick the phone.
Normally when an RUU sees that your phone has a newer software it would just fail and the phone would be fine. Unless you're S-OFF in which case it would flash it anyways.
We need more details.
1. Did it successfully upgrade to 6.0 and you had no issues prior to trying to downgrade?
2. How did you try flashing it? Was it the RUU wizard on Windows, or the rom.zip via a command prompt/terminal
Click to expand...
Click to collapse
I flashed via rom.zip on sdcard iam S-OFF and super CID
the upgrade to 6.0 was oki
I tried to hold all the button combination in the world
I disassembled the phone the battery is oki i recalibrated it to 4.2V
Still dead

iElvis said:
I suspect you are hardbricked (why on earth did you downgrade?) but it's possible the flash got confused somehow. Try holding down all three buttons while the phone is plugged in for at least minute. If that does nothing, leave it plugged in overnight and try it again. If it's still dead, you have a brick. Next time, be more careful about flashing random stuff you find via Google.
Click to expand...
Click to collapse
I tried holding every button combination
I leaved it over night
I flashed certified rom
0PJAIMG_HIMA_UHL_L50_SENSE70_HTC_EUROPE_1.32.401.17_RADIO_01.01_U11440261_56.02.50306G_2_F_RELEASE_429340_SIGNED

Pique91 said:
I tried holding every button combination
I leaved it over night
I flashed certified rom
0PJAIMG_HIMA_UHL_L50_SENSE70_HTC_EUROPE_1.32.401.17_RADIO_01.01_U11440261_56.02.50306G_2_F_RELEASE_429340_SIGNED
Click to expand...
Click to collapse
What type of M9 do you have? Is it a generic GSM model or something else?"
If it's generic, you may have gotten a corrupted download. Did you check the MD5 before flashing?

iElvis said:
What type of M9 do you have? Is it a generic GSM model or something else?"
If it's generic, you may have gotten a corrupted download. Did you check the MD5 before flashing?
Click to expand...
Click to collapse
i guess it's generic and i didn't check the md5
but i flashed this firmeware few weeks ago on the same device and it worked just fine

Pique91 said:
i guess it's generic and i didn't check the md5
but i flashed this firmeware few weeks ago on the same device and it worked just fine
Click to expand...
Click to collapse
The exact same file?
Downgrading can be tricky. It doesn't always work exactly right. If your phone is still dead after this, something went wrong with the flash. It can happen.

Sounds like a bad flash. Double check file sizes and md5 hashcheck to be sure the rom was complete.
If the phone won't even show any sign of life you may as well call it dead. If you live in USA you could try the uh-oh policy that htc implemented. They promise to replace the device one time only no questions asked.
Sent from my HTC One M9 using Tapatalk

iElvis said:
The exact same file?
Downgrading can be tricky. It doesn't always work exactly right. If your phone is still dead after this, something went wrong with the flash. It can happen.
Click to expand...
Click to collapse
thanks for keeping with me
iam still trying to recalibrate battery and other dissberate trys