Hey all,
I have a HTC Desire (PB99200) which won't switch on, recognise a charger/ connection to a PC or enter recovery etc. This was failed update, think I used the wrong RRU as I didn't know about the different versions SLCD/AMOLED.
So as far as I know the device is dead in the water, what I want to know is can it be salvaged?
I'm basically a noob but any help would be greatful
bortak's troubleshooting guide stickied to the top of Q&A, point [5]
If that RUU doesn't work, I recommend find and flash the 2.3.3 GB RUU from shipped ROMs
Thanks for your reply but point 5 doesn't open as page cannot be displayed.
I'm also not sure if u have read my post but it did say it was not being detected by my PC or anything else which would make reflashing stock rom impossible
robbiejuk08 said:
Thanks for your reply but point 5 doesn't open as page cannot be displayed.
I'm also not sure if u have read my post but it did say it was not being detected by my PC or anything else which would make reflashing stock rom impossible
Click to expand...
Click to collapse
Mite sound like a stupid question, but did u try pulling battery out for a min then put back in then try getting into bootloader(volume down + power)
jmcclue said:
Mite sound like a stupid question, but did u try pulling battery out for a min then put back in then try getting into bootloader(volume down + power)
Click to expand...
Click to collapse
Did this and still nothing, even the RRU software can't see it
robbiejuk08 said:
Did this and still nothing, even the RRU software can't see it
Click to expand...
Click to collapse
The only options i can think of is a phone repair shop that has jtag, maybe they can save it but ud probably get a new motherboard off ebay for bout 15 quid which would be cheaper.
jmcclue said:
The only options i can think of is a phone repair shop that has jtag, maybe they can save it but ud probably get a new motherboard off ebay for bout 15 quid which would be cheaper.
Click to expand...
Click to collapse
I might be tempted to do just that, its a shame cos I know the hardware is fine.
Not sure what the price would be to take it to a repair shop here in the UK. Thanks anyway
robbiejuk08 said:
I might be tempted to do just that, its a shame cos I know the hardware is fine.
Not sure what the price would be to take it to a repair shop here in the UK. Thanks anyway
Click to expand...
Click to collapse
Sorry I read your post too quickly
So nothing comes up on screen at all when you try to get to bootloader?
I'm trying to remember whether bootloader is actually 'there', but just not visible if you flashed an SLCD RUU on an AMOLED desire or vice versa.
If it's actually there, then it may be possible to flash the RUU via PB99IMG.zip method, not tried it this way blind but worth a shot before you take it for repair.
- Try the 2.3.3 RUU from here (thanks to @jmcclue)
- Put the zip as it is on the root of the sdcard (not inside any folder), then attempt to boot to bootloader (vol down + power)
- Wait at least 30 seconds - 1 minute for it to scan and load the file, then press volume up to accept the RUU.
- Wait for it to flash, pray that it works!
Also have a look here, you're following this procedure without the screen basically.
Reread my original post in full
robbiejuk08 said:
Reread my original post in full
Click to expand...
Click to collapse
I have [emoji6]
It still comes down to flashing wrong RUU.
Was the device working beforehand ie charging?
Flashing the ruu should not break the usb port so i believe it's still charging even though doesn't look like it.
The software should still turn on, just not the screen.
Therefore the above method has a chance of working as long as you have a card reader to copy the PB99IMG.zip to the root of the sdcard. The video explains what it should look like. Plug it in to ac charger after booting to bootloader to ensure it doesn't die while flashing
Anyway no harm in giving it a go. Nothing to lose by trying it!
eddiehk6 said:
I have [emoji6]
It still comes down to flashing wrong RUU.
Was the device working beforehand ie charging?
Flashing the ruu should not break the usb port so i believe it's still charging even though doesn't look like it.
The software should still turn on, just not the screen.
Therefore the above method has a chance of working as long as you have a card reader to copy the PB99IMG.zip to the root of the sdcard. The video explains what it should look like. Plug it in to ac charger after booting to bootloader to ensure it doesn't die while flashing
Anyway no harm in giving it a go. Nothing to lose by trying it!
Click to expand...
Click to collapse
The phone was working/charging fine before I screwed up the RUU. I am following the instructions you have me and the YouTube video as well but there is no way of knowing if this will work or what its even doing if anything. all I can do it wait through a process I am unsure is working
Since the problem started, it doesn't charge, switch on, respond to PC connection nothing.
robbiejuk08 said:
The phone was working/charging fine before I screwed up the RUU. I am following the instructions you have me and the YouTube video as well but there is no way of knowing if this will work or what its even doing if anything. all I can do it wait through a process I am unsure is working
Since the problem started, it doesn't charge, switch on, respond to PC connection nothing.
Click to expand...
Click to collapse
So if it was working fine before, I doubt the RUU has broken the charging capability.
The only way I guess is to try the PB99IMG.zip watching the video at the same time plus waiting a few seconds longer just in case. Think you have to press volume up or power at the end to reboot can't remember, or battery pull and hope it turns on afterwards.
No guarantee it will work, though I've seen many people in these forums recover 'black screen after ruu' issue. Still worth exhausting this method before repair
Related
I have flashed my at&t tilt 2 with core cell evo v1.2 & it was working fine for awhile but now my screen is just black i can hear the phone make sounds and all but can't see the screen at all i really need help fixing this as this is the only phone i have any help or suggestions will be greatly appreciated thanks in advance.
i may be wrong but from what u have described... ur having a Sleep of Death (SOD) problem. have u tried takin out the battery or soft reseting the phone?
heres a link to a potential problem solver. Try to stay away from CHT lock and auto update apps!
sagarc88 said:
i may be wrong but from what u have described... ur having a Sleep of Death (SOD) problem. have u tried takin out the battery or soft reseting the phone?
Click to expand...
Click to collapse
yes i have done both and after the phone reboots i can hear sounds but i am still unable to see anything on the screen
Edit - I take that back, if it's still not working after a reboot
Have you tried entering the bootloader and re-flashing with the stock ROM?
If you can't see anything at all on the screen, no splash screens etc, even after soft-reset or entering the bootloader, then it sounds like you have a hardware problem (screen failure).
steviewevie said:
If you can't see anything at all on the screen, no splash screens etc, even after soft-reset or entering the bootloader, then it sounds like you have a hardware problem (screen failure).
Click to expand...
Click to collapse
i can't even tell if i can enter the bootloader screen because i can't see anything on the screen is there any way to tell if it's in the bootloader screen without being able to see the screen at all & if i do have a hardware problem (screen failure) how can i put stock spl & stock rom back on the phone to get it serviced
steviewevie said:
Edit - I take that back, if it's still not working after a reboot
Click to expand...
Click to collapse
if its still not working after a reboot then what? please help me i need a solution to fix this because if i can't even fix this how can i even send it in to get fixed i won't be able to because it has been flashed & has hardspl on it
"PLEASE HELP"
It's a tricky situation. So if you hold down Volume Down (and keep it held down) and press the reset button, then you still don't have anything come up on the screen ?
How about if you try a hard reset, does anything come up then ? You can hear the phone making sounds, so it seems like it's just the screen ?
Putting the charger in doesn't help, does it ?
You could try flashing a stock ROM from SD card and seeing what happens.
You might well have to send it back under warranty with HardSPL still on. In that case, if it was me, then if they tried to say the warranty was void just because of HardSPL I would argue very strongly against that and ask them to prove it - e.g. how can HardSPL stop your screen working ? I don't know what country you're in, but in the UK I think our consumer protection laws would have something to say about that.
steviewevie said:
It's a tricky situation. So if you hold down Volume Down (and keep it held down) and press the reset button, then you still don't have anything come up on the screen ?
How about if you try a hard reset, does anything come up then ? You can hear the phone making sounds, so it seems like it's just the screen ?
Putting the charger in doesn't help, does it ?
You could try flashing a stock ROM from SD card and seeing what happens.
You might well have to send it back under warranty with HardSPL still on. In that case, if it was me, then if they tried to say the warranty was void just because of HardSPL I would argue very strongly against that and ask them to prove it - e.g. how can HardSPL stop your screen working ? I don't know what country you're in, but in the UK I think our consumer protection laws would have something to say about that.
Click to expand...
Click to collapse
how can i flash anything if i can't see the screen?
Doo Doo said:
how can i flash anything if i can't see the scrren?
Click to expand...
Click to collapse
I've never flashed via SD, so I could be wrong on this. But I thought it was still possible. I see that the instructions (in the sticky on flashing ROMs) say to put it into the bootloader and "follow the on-screen instructions". I wonder if it's possible to just wait for a while and then press the appropriate key ? Though I don't know what the "appropriate key" is.
Perhaps someone who has flashed via SD can comment further, e.g. as to whether it's possible to do this without seeing the screen ?
steviewevie said:
I've never flashed via SD, so I could be wrong on this. But I thought it was still possible. I see that the instructions (in the sticky on flashing ROMs) say to put it into the bootloader and "follow the on-screen instructions". I wonder if it's possible to just wait for a while and then press the appropriate key ? Though I don't know what the "appropriate key" is.
Perhaps someone who has flashed via SD can comment further, e.g. as to whether it's possible to do this without seeing the screen ?
Click to expand...
Click to collapse
man i really need to fix this maybe you can ask around for me since i'm new here & really don't know anybody on this board
I know it's frustrating, I'd be kinda worried if I had an apparently-non-working screen too. But please be patient, and wait for more people to see your posting. The folks in the US will be coming online around this sort of time, so there will be more people looking in and hopefully someone can help further.
Flash without seeing the screen
Enter boot loader even if you can not see the screen. You can flash your phone to stock then enter boot loader again and hard spl. I had a similar situation and was able to complete the process and warranty repair with AT&T no problems, or you can pay to have it fixed at an outside shop. I was quoted 150 and refused to spend that muck so I flashed the phone without seeing the screen...
I saw your post over on Sergio's thread but decided to answer you here.
You do have a blown screen, no doubt there. How that happened is not really relevant.
My best advise is to connect your phone to your PC and wait for the activesync connection to come up. Once that happens you know you have a good connection and can flash. Run the RUU (or exe) for your stock ROM, the on screen (PC Screen) prompts will let you know if it can't proceed. Once the stock ROM is back on it, follow the same procedure and put the stock SPL back. Then send it off to get the screen replaced.
Hope that helps
Russ
Russ741 said:
I saw your post over on Sergio's thread but decided to answer you here.
You do have a blown screen, no doubt there. How that happened is not really relevant.
My best advise is to connect your phone to your PC and wait for the activesync connection to come up. Once that happens you know you have a good connection and can flash. Run the RUU (or exe) for your stock ROM, the on screen (PC Screen) prompts will let you know if it can't proceed. Once the stock ROM is back on it, follow the same procedure and put the stock SPL back. Then send it off to get the screen replaced.
Hope that helps
Russ
Click to expand...
Click to collapse
well when i plug my phone to the computer activesync is not popping up what can i do to get activesync to recognize my phone
can somebody please help me i need to reflash my phone but i am unable to see anything on my screen when i plug it up to my computer activesync is not working so what can i do please i really need help with this
Flashing witout screen
Step 1
Enter boot loader mode (* Remove the back cover from the phone.
* Hold the Volume Down button.
* Use the stylus to press the reset hole.
* Or if the device was powered off, press the power button whilst holding down the Volume Down button.)
and attach to computer. (wait 30 to 60 seconds)
Step 2
Check device manager for HTC mobile sync under mobile devices.(Active sync will not work in boot loader mode)
Step 3
Flash using Rhodium CustomRUU on your PC. (use original ROM from At&T.
Step 4 repeat for Radio
Step 5 Use Stock_SPL_Restore_087.zip from http://forum.xda-developers.com/showthread.php?t=550131 repeat the process with it.
This should work it did for me. Let me know if you run into problems.
I just rooted my HTC Desire and installed CM7 on it (loved it on my HTC Legend). But suddenly today, after I turned Wifi on, it started rebooting all the time, couldn't do anything to stop it. I thought "Hey, there was the radio flash thing in the tutorial that I didn't do yet, I'll try that out" so I flashed the radio. Then I chose reboot system, but it just booted to a logo with an android coming out of a trash can, and looked kinda stuck there. So I took out the battery and plugged back in. Now if I try to turn it on, it'll just vibrate 7 times - no picture or anything. Also there's no LED when I plug it to the charger.
I had those 7 vibrates too.
Happened after i flashed the cm7 hboot over my stock hboot while trying to enter recovery. After i re-flashed my recovery using fastboot, everything worked again. What happens if you try to power up while holding down vol- ? Did you use fastboot or your phones recovery mode to install the radio?
I am not able to start in recovery or anything. I tried vol. down + power and back + power and no matter what I try, it just vibrates 7 times. I used the recovery mode to install the radio.
You could try to connect your phone via usb and check if fastboot discovers your device. If yes, flash hboot and recovery using fastboot. If not, well... i dont have a clue. Sorry :/
Computer discovers nothing when I plug in the phone.
Bad news when u pulled battery u interrupt the process n u now have a bricked device I would b very surprised if u managed to do anything
Pulling battery when doin a radio update is a BIG NO NO I'm sorry but ur stuck with a 400+ mirror now
Please look at this link
http://www.google.co.uk/m/search?site=images&client=ms-android-htc&hl=en&gl=uk&source=mog&aq=&oq=&aqi=&fkt=&fsdt=&cqt=&rst=&htf=&his=&maction=&q=android+radio+update#i=95
If that the image u saw when u pulled battery ur defo screwed
The Best Things Come To Those Who Wait
Your link doesn't work.. I found a picture of what was showing when I unplugged the battery, but I'm not allowed to post links to other sites on these forums yet.
U need to copy the link for some reason its not showing up
Pm the link u have
The Best Things Come To Those Who Wait
Inrego said:
Your link doesn't work.. I found a picture of what was showing when I unplugged the battery, but I'm not allowed to post links to other sites on these forums yet.
Click to expand...
Click to collapse
inrego
yes the image u just sent me is correct
the image showing would of ment it was installing the radio and because u pulled battery u have corrupt the flash and unfortuntly bricked ur device
i will look for a solution on the net but im not sure if ill find anythink sorrry
Inrego said:
Your link doesn't work.. I found a picture of what was showing when I unplugged the battery, but I'm not allowed to post links to other sites on these forums yet.
Click to expand...
Click to collapse
heres a few thread about some pulling battery on radio flash
http://android.modaco.com/content/g...m/304368/can-the-nexus-one-be-bricked/#entry0
http://android.modaco.com/content/h...50/help-cannot-turn-on-after-flash-new-radio/
i cant find anythink about fixin the issue sorry
Well thanks alot for trying. At least it seems like it shouldn't be too hard to get a replacement unit..
Inrego said:
Well thanks alot for trying. At least it seems like it shouldn't be too hard to get a replacement unit..
Click to expand...
Click to collapse
all depends on if ur on warranty if u have receipt and warranty then all is ok with out them u stuck basically
sorry couldn't help more hopefully lesson learnt playing with radio is risky business
Yea got warranty and reciept and all that, so np there
Inrego said:
Yea got warranty and reciept and all that, so np there
Click to expand...
Click to collapse
nice one then just make up a bull**** reason ok well hope u get a replacement
Wait a minute...
Inrego said:
Well thanks alot for trying. At least it seems like it shouldn't be too hard to get a replacement unit..
Click to expand...
Click to collapse
For the record to help some of you out who ended up here Googling: I had a similar issue. My HTC Desire SV did not boot, and when charging, only had an orange flashing light, and the phone vibrated 7 times. I did 2 things that got it back up:
1) left the phone off for say 10 minutes (I read about overheating issues in general, although the phone did not feel hot).
2) removed the battery for a couple of minutes.
VERY IMPORTANT: for step 2: make sure to have the battery removed long enough to drain internal charge. I removed and installed the battery in a second or so at first, and still the phone did not boot. After leaving out the battery long enough, it booted again. It appears to me that the issue in my case was a rather big internal charge capacity which kept internal state (memory and/or CPU?) from booting. Hope this helps...
hey
i am trying the whole day to fix my phone. but i guess it is almost imposible :/
i can't get in recovery mode (nothing happens) and can't turn in on (only vibrates once, black screen)
i have been told to download to download
OTA_Bravo_Froyo_HTC_WWE_2.29.405.5-2.29.405.2_releasedauhl6jhok5cmdm6.zip
and rename it to PB99IMG.zip and put it on sd, which i did, but how can i flash it if my recovery mod can't start up?
please help?
ANY suggestions???? please heeelp! :/
It would be helpful it you told us what you did to get your phone into this state.
Can you get into fastboot? (power on while pressing back-button)
Tillus said:
It would be helpful it you told us what you did to get your phone into this state.
Click to expand...
Click to collapse
i installed
RUU_Bravo_HTC_Europe_1.15.405.1_Radio_32.30.00.28U _4.05.00.11_release_121684.exe
via fastbooth
do you know what to do... please say yes
Tillus said:
It would be helpful it you told us what you did to get your phone into this state.
Can you get into fastboot? (power on while pressing back-button)
Click to expand...
Click to collapse
no i can't get into fast boot... ://
I suggest you read the notice from jcase... I'm guessing you were runiing gb?
Sent from my ADR6400L using XDA Premium App
you ruu was too old - this version doesn't have the required drivers for SLCD.
That means, you phone probably does work, but the screen is black.
I don't know how to solve this (probably by flashing the newer RUU, Version 2.29....) exactly, but hopefully this gives you a clue where to look for a fix.
There were many people experiencing this after Froyo was available. They did the ota-update, then noticed, that it wasn't possible to root with the new bootloader (Version 0.93ish) at that time, which was installed along with the froyo-ota, so they tried to downgrade back to 2.1 and ended up where you are. (bootoader .80 instead of .83ish).
Richpopski123 said:
I suggest you read the notice from jcase... I'm guessing you were runiing gb?
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
jcase??
i had this rom
http://forum.xda-developers.com/showthread.php?t=1040121
which didn't work and because of it i couldn't restore any of my previous roms. that is why i had to flash a rom from my computer fastbooth
have u any suggestions what should i do?
Tillus said:
you ruu was too old - this version doesn't have the required drivers for SLCD.
That means, you phone probably does work, but the screen is black.
I don't know how to solve this (probably by flashing the newer RUU, Version 2.21....) exactly, but hopefully this gives you a clue where to look for a fix.
There where many people experiencing this after Froyo was available. They did the ota-update, then noticed, that it wasn't possible to root with the new bootloader (Version 0.93ish) at that time, which was installed along with the froyo-ota, so they tried to downgrade back to 2.1 and ended up where you are. (bootoader .80 instead of .83ish).
Click to expand...
Click to collapse
yes... that makes sense. but does really no one have any clue what to do?? i worked the whole summer for this phone and now is gone
http://forum.xda-developers.com/showthread.php?t=748498
Probably the easiest and safest way ist to boot into fastboot although you don't see it and flash the newsest ruu,
so:
1) make sure, phone is off (i.e. pull battery and put back in)
2) push and hold "back" and hit power.
3) wait 30 seconds or so, to be on the safe side
4) connect phone to pc via usb
5) run RUU on PC, version 2.29.405... (RUU, not OTA!)
And make sure to have some juice in your battery
Here you can get the RUU:
RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00.32U_5.11.05.27_release_159811_signed.exe
Its on >>Shipped Roms<< , 7th from top.
btw. am I assuming correctly that your phone is unbranded?
btw2: Do it all on your own risk. I'm trying to help, but I dont want to be held resposible, if something goes wrong, so maybe wait for someone else to confirm
Tillus said:
Here you can get the RUU:
RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00.32U_5.11.05.27_release_159811_signed.exe
Its on >>Shipped Roms<< , 7th from top.
btw. am I assuming correctly that your phone is unbranded?
btw2: Do it all on your own risk. I'm trying to help, but I dont want to be held resposible, if something goes wrong, so maybe wait for someone else to confirm
Click to expand...
Click to collapse
how do i know that?
can u please stick with me... i will try to do that now
i apriciate your help... i think that nothink worse can be done to my phone, so i will try
did you see any provider logo during startup? Or any preinstalled apps or bookmarks which point into a provider's direction? Where did you buy it? And did you need a goldcard for rooting?
if you answer is no on every question, you're probably not branded.
Did you write down the version number before you did anything to your phone (when you have a .405. in your version number, your phone is definitely not branded).
Edit: but I really recommend to read the linked thread. My device is unbranded amoled so I never did any of this myself (apart from running a RUU), so always think twice before following my steps
Tillus said:
did you see any provider logo during startup? Or any preinstalled apps or bookmarks which point into a provider's direction? Where did you buy it? And did you need a goldcard for rooting?
if you answer is no on every question, you're probably not branded.
Did you write down the version number before you did anything to your phone (when you have a .405. in your version number, your phone is definitely not branded).
Edit: but I really recommend to read the linked thread. My device is unbranded amoled so I never did any of this myself (apart from running a RUU), so always think twice before following my steps
Click to expand...
Click to collapse
i hope its not branded
do i need to click od hold power button?
like you do, when you power on. The important part is to hold "back" while powering on
Tillus said:
like you do, when you power on. The important part is to hold "back" while powering on
Click to expand...
Click to collapse
do i have to hold down like 30 sec? no right?
i think this won't work
if i go to the sotre and give the device back... what would be a good excuse for phone not working?
jann32 said:
do i have to hold down like 30 sec? no right?
Click to expand...
Click to collapse
no. You have booted into recovery before, didn't you? Now you do the same but use "back" instead of vol- , because you want to boot into fastboot.
All I wanted to say with this 30 seconds is to give it some time to boot into fastboot, thats all. Press and hold "back", press "power", release power, wait 3 seconds, release "back", wait 10 seconds and plug in usb, start ruu.
Thats all I wanted to say with my previous post. Sry, if it was confusing
Tillus said:
no. You have booted into recovery before, didn't you? Now you do the same but use "back" instead of vol- , because you want to boot into fastboot.
All I wanted to say with this 30 seconds is to give it some time to boot into fastboot, thats all.
Click to expand...
Click to collapse
will try again
will the phone vibrate?
YES YES YES its upadatinjg.... hope this works
...my screen is back... but hopefully it finishes correctly... and doesn't go black again
what will happen if the phone is branded?
can i unbrand it?posebly not? cause its bricked ight? :/
no.
10charrrrr
If it is branded, you get a cid-error, so ruu wont finish. But your phone probably isn't branded, otherwise you would have come across problems during flashing custom roms or/or radios (-->goldcard). And because this doesn't seem to be the case, your device is not branded.
When the RUU is done, you phone is completely back to stock and you can do whatever you like to it...
Tillus said:
no.
10charrrrr
Click to expand...
Click to collapse
my phone works!!
i can not tell u how greatfull i am
THANK U
thank u for sticking with me again
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.
Long story short my friend gave me a T mobile HTC G2 because it didn't turn on. I opened the phone to find the part where the battery connects to the phone came off the mother board so i solder it back on put the phone back together and turned it on. It booted up normal and came to the lock screen nothing worked the touch wasn't responding so i push power button to turn screen off and then again to turn it back on and the screen worked. I tried guessing his pattern five time and it didnt work it asked me to sign in to my Google account when the screen came up the phone rebooted and it kept doing it every time i turned it on. So i looked on xda how to restore it tried it and im not sure if it restored or not but it strated boot looping. I tried the flashing the pc10img.zip from the root of the sd card it usually says something like version to new or to old or something it didn't work. My phone is not rooted and i don't think usb debugging is on. Any info you guys want just ask. What can i do? How can i fix it? Please help
I'm going to take a guess, that if the battery connection to the motherboard 'broke off', then it's possible you have other physical issues such as the ribbon cable connecting the screen/digitizer to the rest of the phone.
If it were me I would have sent the phone into HTC for hardware warranty (which you can't do now since you soldered it.).
Can you provide some specific information about the phone, can you get into the boot loader, and if so what exact information do you have there? (USB debugging would be easily turned on under system settings, if you can get into it via the screen).
kbeezie said:
I'm going to take a guess, that if the battery connection to the motherboard 'broke off', then it's possible you have other physical issues such as the ribbon cable connecting the screen/digitizer to the rest of the phone.
If it were me I would have sent the phone into HTC for hardware warranty (which you can't do now since you soldered it.).
Can you provide some specific information about the phone, can you get into the boot loader, and if so what exact information do you have there? (USB debugging would be easily turned on under system settings, if you can get into it via the screen).
Click to expand...
Click to collapse
Thanks for replying i don't think anything else is wrong with the phone all the cables were fine. To begin with warranty was already finished. "Yes", i can get into the boot loader/H boot. I can turn on usb debugging because the phone doesn't boot all the way in to android. When you say information what exactly are you looking for?
helstonrampersad said:
Thanks for replying i don't think anything else is wrong with the phone all the cables were fine. To begin with warranty was already finished. "Yes", i can get into the boot loader/H boot. I can turn on usb debugging because the phone doesn't boot all the way in to android. When you say information what exactly are you looking for?
Click to expand...
Click to collapse
Mainly the info that shows up on hboot, and which recovery you have (or 'had') so that might be able to advise some additional steps.
helstonrampersad said:
Long story short my friend gave me a T mobile HTC G2 because it didn't turn on. I opened the phone to find the part where the battery connects to the phone came off the mother board so i solder it back on put the phone back together and turned it on. It booted up normal and came to the lock screen nothing worked the touch wasn't responding so i push power button to turn screen off and then again to turn it back on and the screen worked. I tried guessing his pattern five time and it didnt work it asked me to sign in to my Google account when the screen came up the phone rebooted and it kept doing it every time i turned it on. So i looked on xda how to restore it tried it and im not sure if it restored or not but it strated boot looping. I tried the flashing the pc10img.zip from the root of the sd card it usually says something like version to new or to old or something it didn't work. My phone is not rooted and i don't think usb debugging is on. Any info you guys want just ask. What can i do? How can i fix it? Please help
Click to expand...
Click to collapse
when you first had the phone it won't boot right? but when you tried fixing the battery connection thingy (sorry I don't know whats it called )
it booted and ran again?
have you tried doing a factory reset?
Power button+volume rocker down (volume down button) to boot into bootloader mode then do a factory reset maybe that would work ?
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
OR
or sending the phone to HTC would help bud but you have to pay them for that if they get to fix it you got yourself a new toy!
kbeezie said:
Mainly the info that shows up on hboot, and which recovery you have (or 'had') so that might be able to advise some additional steps.
Click to expand...
Click to collapse
This is the boot loader screen that i see
VISION PVT SHIP S-ON
HBOOT-0.82.0000
MICROP-26.13.04.19_M
eMMC-boot
Apr 13 211, 14:51:54
Im pretty sure the phone was never rootded before
The Android Manual said:
when you first had the phone it won't boot right? but when you tried fixing the battery connection thingy (sorry I don't know whats it called )
it booted and ran again?
have you tried doing a factory reset?
Power button+volume rocker down (volume down button) to boot into bootloader mode then do a factory reset maybe that would work ?
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
OR
or sending the phone to HTC would help bud but you have to pay them for that if they get to fix it you got yourself a new toy!
Click to expand...
Click to collapse
Its ok im not certain of what its called either but just to be sure its the part where the battery touches and it has metal prongs like. As for trying to restore it, i already tried didnt work it boot loops when i try that.
I don;t know what to do
helstonrampersad said:
Its ok im not certain of what its called either but just to be sure its the part where the battery touches and it has metal prongs like. As for trying to restore it, i already tried didnt work it boot loops when i try that.
Click to expand...
Click to collapse
ryin
sorry bro I'm no dev so I don't know that much when you were tryin to flash the "stock rom" did you flash the one for the G2 or the Desire Z?
The Android Manual said:
ryin
sorry bro I'm no dev so I don't know that much when you were tryin to flash the "stock rom" did you flash the one for the G2 or the Desire Z?
Click to expand...
Click to collapse
I still appreciate your help bro and i was trying to flash the stock rom for the g2, i made sure of it.
helstonrampersad said:
I still appreciate your help bro and i was trying to flash the stock rom for the g2, i made sure of it.
Click to expand...
Click to collapse
Would probably have to stick to the original Stock RUU update since you're S-ON (would need S-OFF for any kind of custom recovery, kernel, unsigned packages, etc), so would have to use a signed full package from T-Mobile, I don't know much bout that because I usually have my phones rooted and away from stock as fast as I can.
What stock rom did you find before? links?
kbeezie said:
Would probably have to stick to the original Stock RUU update since you're S-ON (would need S-OFF for any kind of custom recovery, kernel, unsigned packages, etc), so would have to use a signed full package from T-Mobile, I don't know much bout that because I usually have my phones rooted and away from stock as fast as I can.
What stock rom did you find before? links?
Click to expand...
Click to collapse
http://shipped-roms.com/index.php?category=android&model=Vision
Thats is the above link i used and i used all the ones that start with "PC10" I rename them to PC10IMG.zip so the phone can recognize it and it did. The only problem is that after it tries to install is say something along the lines of version is older or newer since i tried multiple packages. One package was going through the process and after that it didn't do anything, it didnt say failed or reboot or anything like that. Ive been trying to fix this for like a week and a half now. Ive even flashed custom PC10IMG.zip to see if it could help but nothing the furthest ive gotten is the phone boots for like 2 seconds the screen is blurry and the shuts off and there is an orange light in top right that wasn't lighting up before. Here are the links for the custom packages
http://forum.xda-developers.com/showpost.php?p=10583834&postcount=33
http://forum.xda-developers.com/showpost.php?p=10966727&postcount=63
Cant thank you enough for helping me this is really frustrating
kbeezie said:
Would probably have to stick to the original Stock RUU update since you're S-ON (would need S-OFF for any kind of custom recovery, kernel, unsigned packages, etc), so would have to use a signed full package from T-Mobile, I don't know much bout that because I usually have my phones rooted and away from stock as fast as I can.
What stock rom did you find before? links?
Click to expand...
Click to collapse
If what i explained above is not what you were referring to then let me know your way
helstonrampersad said:
If what i explained above is not what you were referring to then let me know your way
Click to expand...
Click to collapse
You would have to much it to your exact carrier/phone, Just flashing whatever you get your hands on can be very very risky.
For example for me being on T-Mobile with a T-Mobile branded G2, I would grab PC10IMG_Vision_TMOUS_1.19.531.1_Radio_12.21.60.09b_26.02.01.15_M2_release_149459_signed.zip from http://forum.xda-developers.com/showthread.php?t=971109
(noting the *.15 is the original radio my device was shipped with, though I've upgraded to the newer *.19)
I of course have no intention to returning to complete stock, but it's usually the only course of action for most people stuck with S-ON (and then would look into exploiting/unlocking/rooting again from there).
kbeezie said:
You would have to much it to your exact carrier/phone, Just flashing whatever you get your hands on can be very very risky.
For example for me being on T-Mobile with a T-Mobile branded G2, I would grab PC10IMG_Vision_TMOUS_1.19.531.1_Radio_12.21.60.09b_26.02.01.15_M2_release_149459_signed.zip from http://forum.xda-developers.com/showthread.php?t=971109
(noting the *.15 is the original radio my device was shipped with, though I've upgraded to the newer *.19)
I of course have no intention to returning to complete stock, but it's usually the only course of action for most people stuck with S-ON (and then would look into exploiting/unlocking/rooting again from there).
Click to expand...
Click to collapse
I know it can be risky but im desperate for a fix. Ill try the package you linked. I download it and rename it to PC10IMG.zip? Ill get back after im done if you have any other suggestion please let me know.
kbeezie said:
You would have to much it to your exact carrier/phone, Just flashing whatever you get your hands on can be very very risky.
For example for me being on T-Mobile with a T-Mobile branded G2, I would grab PC10IMG_Vision_TMOUS_1.19.531.1_Radio_12.21.60.09b_26.02.01.15_M2_release_149459_signed.zip from http://forum.xda-developers.com/showthread.php?t=971109
(noting the *.15 is the original radio my device was shipped with, though I've upgraded to the newer *.19)
I of course have no intention to returning to complete stock, but it's usually the only course of action for most people stuck with S-ON (and then would look into exploiting/unlocking/rooting again from there).
Click to expand...
Click to collapse
Im confused on which one to flash I have a T-Mobile HTC G2 which one will i flash?
choose the latest one for the g2, reading your thread I feel you will have little luck with this. try logging onto freenode #g2root, you'll get real time help here
Sent from my HTC Vision using xda premium
demkantor said:
choose the latest one for the g2, reading your thread I feel you will have little luck with this. try logging onto freenode #g2root, you'll get real time help here
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
I am new to XDA how can i do that?
helstonrampersad said:
I am new to XDA how can i do that?
Click to expand...
Click to collapse
I'm new so I can't post links, but copy and paste this url: http://webchat.freenode.net/?channels=g2root
EDIT - Oh, I can post links.
eboy_gb said:
I'm new so I can't post links, but copy and paste this url: http://webchat.freenode.net/?channels=g2root
EDIT - Oh, I can post links.
Click to expand...
Click to collapse
Though ideally using an actual IRC client will work much nicer than a web chat one.
Same problem, but desire z S-ON
Hey guys.
I have the same problem with the boot loop /semi brick. Expect I never had any problem before, with the phone. I have tried taking out the sd card, starting it agian. I have tried without simcard. I have tried to flash the ROM with RUU_Vision_Gingerbread_S_HTC_WWE_2.42.405.2_Radio_12.56.60.25_26.10.04.03_M_release_199043_signed
via Hboot Fastboot USB PLUG mode (which was the only mode the aplication was progressing in until it want to restart the phone in bootloader), but the phone frezzes and the aplication on the computer just keep working, without progress.
The factory reset just frezzes the phone.
The only thing reali seem to not frezze the phone is the revocery option. Here the phone react with restart showing a image of a phone with two green arrows bent around, over the phone. then it turns off the display and vibrate 4-5 times, og stays turn off not reacting to anything other then taking out the battery and you can start the phone once again.
VISION PVT SHIP S-ON
HBOOT-0.85.0013
MICROP-26.10.04.19_M
eMMC-boot
Apr 11 2011, 23:36:27
Have no idea but the version of android. I know that usb debugging is NOT on Any hjelp is a big help. I'm a noob, And I have been searching for 3 days for a solution, so I just hope you can help my, otherwise it is going for a repair at the place I bought it.
Thanks