Develop Bugs

Desire un-responsive - Please Help

I've seen a couple of threads such as this with no real solution.
I've been happily using my Desire for months without changing roms or whatever (CM7 and s-off) until last night I opened my Dolphin browser and before it loaded the homepage it froze, totally un-responsive. I took the battery out, and to my horror, it was still totally un-responsive. Wouldn't respond to pressing the power button, pressing volume down+power, charger, or usb.
The battery at the time was about 50%, I've had the battery in and out about 100 times now, trying things like leaving the battery out and then trying again, keeping it on 'charge' for a while and trying to get it booted, with no response at all.
This was until an hour ago, I hopefully tried to boot the phone after the battery, sim and sd card had been out for a while and I got a vibration, and then it hung on the flash screen. I had to remove the battery, then tried to boot again with no response, so I left it a while again, put the battery in and got to the bootloader, thought I'd get into recovery and try a nandroid or something, only when I selected recovery it hung on the slash screen again.
Does anyone have any ideas what this is, or how this could be fixed? Damn I hate not being able to use my previously awesome phone!
I apologise for the long post, I'm just trying to give a good explanation of things. I just couldn't see the problem being my battery, only the day before the problem I was telling my friend how great the battery life on my phone is, and that he should give rooting a go and use CM7, this probably hasn't swayed his decision to root his phone.

stevoh84 said:
I've seen a couple of threads such as this with no real solution.
I've been happily using my Desire for months without changing roms or whatever (CM7 and s-off) until last night I opened my Dolphin browser and before it loaded the homepage it froze, totally un-responsive. I took the battery out, and to my horror, it was still totally un-responsive. Wouldn't respond to pressing the power button, pressing volume down+power, charger, or usb.
The battery at the time was about 50%, I've had the battery in and out about 100 times now, trying things like leaving the battery out and then trying again, keeping it on 'charge' for a while and trying to get it booted, with no response at all.
This was until an hour ago, I hopefully tried to boot the phone after the battery, sim and sd card had been out for a while and I got a vibration, and then it hung on the flash screen. I had to remove the battery, then tried to boot again with no response, so I left it a while again, put the battery in and got to the bootloader, thought I'd get into recovery and try a nandroid or something, only when I selected recovery it hung on the slash screen again.
Does anyone have any ideas what this is, or how this could be fixed? Damn I hate not being able to use my previously awesome phone!
I apologise for the long post, I'm just trying to give a good explanation of things. I just couldn't see the problem being my battery, only the day before the problem I was telling my friend how great the battery life on my phone is, and that he should give rooting a go and use CM7, this probably hasn't swayed his decision to root his phone.
Click to expand...
Click to collapse
did you try rebooting it without sdcard?

If you manage to get it running , try to flash a shipped ROM - it should unroot you and fix any software problems . Try taking it back to your carrier as that sounds more like a hardware problem.

you are stuck on HTC screen are you not? Then this is the exact same situation is it not?
bortak's Troubleshooting Guide said:
S-ON
"I'm S-ON, I can't boot recovery, and my phone doesn't boot "
This is a bit of a worse situation, as you cannot flash system critical parts such as the recovery image and just restore a backup. This unfortunately means that you will lose all of your data when you attempt to fix the phone.
[STEP1]- Make sure that you have a goldcard. If not, create one from the tutorial.
[STEP2]- Battery pull. Hold the BACK button and the POWER button to boot into FASTBOOT mode.
[STEP3]- Download the latest WWE RUU from here
[STEP4]- Run the RUU and wait for completion WARNING: DO NOT, BY ANY CIRCUMSTANCES INTERRUPT THE PROCESS - THIS WILL MORE THAN LIKELY END UP WITH A BRICKED PHONE - NOT EVEN IF GOD HIMSELF TELLS YOU TO DO SO, OR IF THE US PRESIDENT THREATENS YOU WITH THERMO-NUCLEAR WAR
[STEP5]- Once the phone is booted, you are now returned completely to stock. You will need to re-root again, and I'd recommend S-OFF
Click to expand...
Click to collapse
P.S. Remember to read disclaimer on the thread.

kmaq said:
did you try rebooting it without sdcard?
Click to expand...
Click to collapse
I have tried booting without sdcard with no luck.

Walter1115 said:
If you manage to get it running , try to flash a shipped ROM - it should unroot you and fix any software problems . Try taking it back to your carrier as that sounds more like a hardware problem.
Click to expand...
Click to collapse
I would love to try that, only I can't boot the phone at all, not even into recovery.
bortak said:
you are stuck on HTC screen are you not? Then this is the exact same situation is it not?
P.S. Remember to read disclaimer on the thread.
Click to expand...
Click to collapse
I've changed the HTC screen to a Google one, but yes, formally the HTC screen.
I will try and get to the bootloader/fastbootagain, only I have not been able to get to that today. I'm going to download an RUU, and try and flash it, although I'm not sure how if I can't get into recovery? Any help there?

stevoh84 said:
I would love to try that, only I can't boot the phone at all, not even into recovery.
I've changed the HTC screen to a Google one, but yes, formally the HTC screen.
I will try and get to the bootloader/fastbootagain, only I have not been able to get to that today. I'm going to download an RUU, and try and flash it, although I'm not sure how if I can't get into recovery? Any help there?
Click to expand...
Click to collapse
[STEP2]- Battery pull. Hold the BACK button and the POWER button to boot into FASTBOOT mode.
Click to expand...
Click to collapse
you don't need recovery

bortak said:
you don't need recovery
Click to expand...
Click to collapse
Made a noob error there and didn't have the udb plugged in. Got fastboot up, and downloading an RUU, will let you know how I get on, thanks for the help.
Would you advise, running my previous nandroid, once I get up and running again?

stevoh84 said:
Made a noob error there and didn't have the udb plugged in. Got fastboot up, and downloading an RUU, will let you know how I get on, thanks for the help.
Would you advise, running my previous nandroid, once I get up and running again?
Click to expand...
Click to collapse
up to you, doesn't make a difference

Thanks for the help, unfortunately when I got the RUU downloaded and the bootloader downgrader I now can't get the phone into fastboot! Rather gutted, as I could get it there the other day, now I may have to accept defeat!

What happens when you try to get to fastboot mode? How do you do it? Try to boot into hboot, then press power button and you should be in fastboot mode.

stevoh84 said:
Thanks for the help, unfortunately when I got the RUU downloaded and the bootloader downgrader I now can't get the phone into fastboot! Rather gutted, as I could get it there the other day, now I may have to accept defeat!
Click to expand...
Click to collapse
NEVER accept defeat with Android. Try my guide for help.

MatDrOiD said:
What happens when you try to get to fastboot mode? How do you do it? Try to boot into hboot, then press power button and you should be in fastboot mode.
Click to expand...
Click to collapse
I can't get into any sort of boot mode, I've tried leaving it for days and trying the button sequences, I've tried having it plugged in for a day, and then trying, with no luck!
bortak said:
NEVER accept defeat with Android. Try my guide for help.
Click to expand...
Click to collapse
I will have a look, I will try anything really! just need some more ideas....

bortak said:
NEVER accept defeat with Android. Try my guide for help.
Click to expand...
Click to collapse
I may have to accept defeat, but I don't think I will be blaming Android, more than likely a drop of the phone in the past that has taken it's toll or something.
Sadly nothing in the contents of your quite excellent guide jumped out at me as relating to my problem.
But, thanks for helping and your advice.

stevoh84 said:
I may have to accept defeat, but I don't think I will be blaming Android, more than likely a drop of the phone in the past that has taken it's toll or something.
Sadly nothing in the contents of your quite excellent guide jumped out at me as relating to my problem.
But, thanks for helping and your advice.
Click to expand...
Click to collapse
Ahh well that's a shame, get HTC to fix it for you

bortak said:
Ahh well that's a shame, get HTC to fix it for you
Click to expand...
Click to collapse
I have been onto them. The response from HTC was amazing, after detailing in an email my phone is dead, won't respond and won't turn on.
I was told, 'while the phone is on, remove the battery and sim and perform a soft reset, if this fails, perform a factory reset, through settings'
I replied asking them how much it will be for them to fix it, they haven't replied! Maybe they don't do weekend!
So if I send it off to them, are they going to frown upon me for fiddling with the phone and rooting etc?

[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.

my phone doesn't charge/boot... probably dead

i already searched a lot, but i didn't find anything useful so i post here hoping that someone can help me. i really need my phone so before send it to htc service i have to try to get it back working.
simply yesterday my phone went off because of low battery. when i got back home i try to charge it, but nothing happened. so i tried using pc in order to see if something happen, and led started to blink slow (orange led). so i turned it on, and it worked. then i was using it (connected to the wall charger) and it frozed, at 9% battery. so i tried to restart it (by pressing power and vol down), but nothing happened... it was completely dead, i tried:
-wall-charger;
-pc-usb;
-change different charger/different usb cables);
-i left it the night connected to the charger);
-no adb, and obviously i can't get the phone in recovery/bootloader/fastboot...
i was on hboot 1.3x... don't remember which number cause i updated the hboot a few days ago. i was on viper rom and i was using the tripndroid kernel based on official nvidia sources (really like their works )
hoping that someone can help me
however in the next days i will send it back to htc but i need to try something cause i really need my phone in those days and i have no replacement. will htc repair my phone for free? (remember that i unlocked it)

Crazy thing. U can't put the phone in bootloader mod?

no i can't...
completely dead, i think i should just stop trying to fix it

Iacopo91 said:
no i can't...
completely dead, i think i should just stop trying to fix it
Click to expand...
Click to collapse
Try this tutorial if it helps:
http://forum.xda-developers.com/showthread.php?t=1609190

can't boot in bootloader neither recovery... it's just like an expensive paperweight

Iacopo91 said:
can't boot in bootloader neither recovery... it's just like an expensive paperweight
Click to expand...
Click to collapse
And u can't charge either?

finally got a sign from my phone.... it entered in APX.... no way to get out from this mode??

Iacopo91 said:
finally got a sign from my phone.... it entered in APX.... no way to get out from this mode??
Click to expand...
Click to collapse
Sorry, but what is APX?

Iacopo91 said:
finally got a sign from my phone.... it entered in APX.... no way to get out from this mode??
Click to expand...
Click to collapse
That means your phone is broken. It needs a new motherboard.
Nobody has recovered from that. Some people have managed to get the phone working after APX, but it seems to go back to APX mode.
Sorry. Back to HTC it goes...

ok thanks... it is and hardware fault or it's because of the custom rom/kernel?

hardcore4ever said:
Sorry, but what is APX?
Click to expand...
Click to collapse
APX mode is a sort of nvidia recovery partition, as far as i know...

APX mode:
http://forum.xda-developers.com/wiki/APX_mode

[Q] Samsung t989 Galaxy S II - Bootloop HELP please :(

I downloaded the Jedi Mind Trick JB 2 ROM and installed it via clocwork mod recovery .. That went fine but it took me a few days to realize I didnt have a working video camera anymore on my phone.. so I thought to flash a stock ROOTed rom instead...
Then I found this threat about an updated version of Jedi Mind Trick's ROM labled JB 3.. So I wiped as much as I could in recovery and chose to format all the options it gave me in recover , Format system , data , cache , emms(or something) .. and now when I boot the phone , it shows the first flash screen , and the samsung logo starts to shimmer then it reboots back to the splash screen and repeats this process everal times before just going black and sitting there..
So I've successfully bootlooped my phone doing this..
MY PROBLEM -- I don't know how to charge my phone or connect to it to install anything else..
Is this a serious problem? How can I charge my phone to continue troubleshooting it? It still has some battery to try some things but I don't know how to hook it up to transfer any other roms to it via USB cable and PC in it's current state..
I'm very computer savvy but I'm trying to learn this phone modding stuff and I realy hope I didn't brick my phone in this process.
Can someone please help me out here? I'll be on the forums religiously until I figure this out.
What should I start doing first??
Any help would be greatly appreciated!! Thanks!

still working at it
I think I'm at the point of having to use ODIN to flash a new rom since i cannot simply copy this rom to the sdcard to use clockwork to flash it .. Am I correct on this ?
For some reason this rom I found (should be stock rooted tmobile gSII rom) does not want to open from ODIN's PDA button cause its in .zip and not .tar or anything... I'm not sure how to flash this rom with ODIN ( I'm not even 100% sure this is how its supposed to go) Any suggestions ?

phew
UPDATE - So I managed to research enough to find out that there is no way to flash a CUSTOM rom with ODIN.. SO I had to download a stock (presumably rooted) t-mobile rom and flash THAT ...
Now I'm back up with a rooted rom and will begin re-installing clockwork and then my custom deodexed rooted rom afterward.
Thanks for all who almost kinda tried to care to reply in this past 2 hours =) -- As previously mentioned.. I am a nerd.. I just suck at phone modding. Haha
So , looks like I'm in the clear now and don't need any more support on this particular topic yet.

zarklon said:
UPDATE - So I managed to research enough to find out that there is no way to flash a CUSTOM rom with ODIN.. SO I had to download a stock (presumably rooted) t-mobile rom and flash THAT ...
Now I'm back up with a rooted rom and will begin re-installing clockwork and then my custom deodexed rooted rom afterward.
Thanks for all who almost kinda tried to care to reply in this past 2 hours =) -- As previously mentioned.. I am a nerd.. I just suck at phone modding. Haha
So , looks like I'm in the clear now and don't need any more support on this particular topic yet.
Click to expand...
Click to collapse
Is this true? Through a recommendation (haven't done anything to my phone from rooting/flashing KANGSJUGGERNAUT2 years ago), I tried to flash CM10 and ended up with a bootloop myself. Tried flashing through ODIN but it kept crashing; does anyone know why?
Afterward, I tried to reflash it through CWM and from then on bootloops into a installation process that never completes.
For some reason my CWM turned super slow, freezes/hangs and reboots after a few minutes.
I gave the phone to a friend who does this stuff on the regular but he said my initial flash wasn't complete cause in download mode says I'm still running official? No clue.
I was told this via email/chat: "No luck, it won't even boot anymore, I think I'll just bring it back tmrw morn
10:43 PM
Sorry I'm at a wedding (yea I know random) I left my phone with coat check
OK I've narrowed down the reason but not the solution, you had an AOKP based ROM which fundamentally is based on CyanogenMod, but it wasn't correctly flashed as the phone still thought it has factory ROMs still running
11:10 PM
Clockworkmod(even though it was working before) wasn't accessing the partitions of the phone correctly so it wasn't properly wiping or flashing properly.
11:12 PM
So basically from the first time you flashed cwm it didn't flash properly then the next time you flashed using the new recovery it didn't flash anything it was supposed to do itself properly , so basically it was a chain of events in addition to a bad boot loader, that's why it never went to recovery or download mode correctly
11:13 PM
That's something that had to do with the way the phone was built meaning you may of had a bad bootloader from the very begin and are now feeling the synptoms
Basically, and I would hate to be the reason or partially the reason you have a dead phone, basically it was a matter of coincedencr that it happened as this could of happened at anytime, once you have a bad boot loader its pretty much down hill from there"
Any helpful insight as how I can rectify this? is my phone truly dead? Sorry about the quoted format, it was copied and pasted.

If I were in your boat, I'd use Odin and flash the stock 4.1.2 ROM.
Sent from my Nexus 7 using Tapatalk 4 Beta

tronmech said:
If I were in your boat, I'd use Odin and flash the stock 4.1.2 ROM.
Sent from my Nexus 7 using Tapatalk 4 Beta
Click to expand...
Click to collapse
The phone won't turn on, unable to go into recovery and download mode; plugged in usb (hear connection beep but pressing power button plays disconnect button) to no avail. What can I do to unbrick?
Stock 4.1.2? Possible over a hardbricked T989 with old 2.3.6?

JahJahLoO said:
The phone won't turn on, unable to go into recovery and download mode; plugged in usb (hear connection beep but pressing power button plays disconnect button) to no avail. What can I do to unbrick?
Stock 4.1.2? Possible over a hardbricked T989 with old 2.3.6?
Click to expand...
Click to collapse
sorry but i have to assume that you are not doing the 3 button recovery or download mode right.
Pull battery, put battery back in, hold power button & Vol +/- untill you see SAMSUNG on the screen ---> let go off power button(keep holding
Vol +/- button) .....u will see recovery. (assuming you did flash cwm before).
Let me know.
hit thanks.

sam.balia1012 said:
sorry but i have to assume that you are not doing the 3 button recovery or download mode right.
Pull battery, put battery back in, hold power button & Vol +/- untill you see SAMSUNG on the screen ---> let go off power button(keep holding
Vol +/- button) .....u will see recovery. (assuming you did flash cwm before).
Let me know.
hit thanks.
Click to expand...
Click to collapse
I believe I am doing it correct, I have been entering recovery and download mode many times, right before I soft bricked it.
And sorry, no, I've tried many times, many methods and my phone is confirmed as entirely hard bricked.
SUPAR SAD, but thank you!

dont give up
JahJahLoO said:
I believe I am doing it correct, I have been entering recovery and download mode many times, right before I soft bricked it.
And sorry, no, I've tried many times, many methods and my phone is confirmed as entirely hard bricked.
SUPAR SAD, but thank you!
Click to expand...
Click to collapse
you can try using adb and put the phone in dl mode.
sometimes its as easy as pull battery and wait awhile (20 min or more) and try again.
if you've exhausted all possibilities, you can use a jig to force a dl mode.
let me know

sam.balia1012 said:
you can try using adb and put the phone in dl mode.
sometimes its as easy as pull battery and wait awhile (20 min or more) and try again.
if you've exhausted all possibilities, you can use a jig to force a dl mode.
let me know
Click to expand...
Click to collapse
I don't know what adb is, or how to use it; I have, however seen my friend RDP to my desktop and do something and used the term 'adb' in his attempt to code through the phone.
I've done that battery waiting period, for nearly an hour and still no result.
After doing some researching, I have found that many people have stated a USB JIG would not be applicable to a 'hard bricked' phone. I really wanted to try as it looked like the most, simple and inexpensive solution.

JahJahLoO said:
I don't know what adb is, or how to use it; I have, however seen my friend RDP to my desktop and do something and used the term 'adb' in his attempt to code through the phone.
I've done that battery waiting period, for nearly an hour and still no result.
After doing some researching, I have found that many people have stated a USB JIG would not be applicable to a 'hard bricked' phone. I really wanted to try as it looked like the most, simple and inexpensive solution.
Click to expand...
Click to collapse
If you know for a fact that you bricked your s2, maybe wrong rom or kernel that u flashed by accident then.....
contact these guys.... http://brickedmyphone.com/contact-me/
good like and click thanks if you agree.

sam.balia1012 said:
If you know for a fact that you bricked your s2, maybe wrong rom or kernel that u flashed by accident then.....
contact these guys.... http://brickedmyphone.com/contact-me/
good like and click thanks if you agree.
Click to expand...
Click to collapse
Lols, you're really fishing for them "Thanks"; you got it buddy. Very swift responses. :cyclops:
Anyway, I'm still searching the net for anymore possible solutions.
Thanks.

JahJahLoO said:
Lols, you're really fishing for them "Thanks"; you got it buddy. Very swift responses. :cyclops:
Anyway, I'm still searching the net for anymore possible solutions.
Thanks.
Click to expand...
Click to collapse
fishing for them ???????
what the hell does that even mean? it seems that brick did hit u in the head!!!

sam.balia1012 said:
fishing for them ???????
what the hell does that even mean? it seems that brick did hit u in the head!!!
Click to expand...
Click to collapse
It might as well have... :crying:

[Q] HTC Desire Bricked/Dead

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