Database Users

(Help Needed) I think I BRICKED my phone

Hey guys,
I've been reading a lot of the threads and it's pretty awesome how helpful everyone is. Could someone try and help me?
Here's what I've done. I started with a new Evo.
**Rooting Method**
-downloaded PC36IMG.Zip & evorecovery from Toastcfh
-Copied PC36IMG.Zip to SD card on phone
-While in bootloader, I started the update and rebooted
-It powered on, I removed the PC36IMG.Zip file from the SD card
-I powered it off and back on.
**Auto Recovery Method**
-I donated money for the "ROM Manager" by ClockworkMod and installed
-Then I selected "reboot into Recovery" and Powered off the phone
-I powered back up and nothing seemed to be different about the phone. I don’t get how I’m supposed to know it’s rooted.
ANYWAYS THAT’S THE LEAST OF MY PROBLEMS NOW
I did the Auto Recovery Method steps again and now IT WON’T TURN ON NO MATTER WHAT MODE.
I tried:
Taking out the battery, taking out the SD card, tried starting it in bootloader (vol down + power).
IS MY PHONE A BRICK NOW?
If so how can I fix this and if I can’t fix it, how do I return it without showing I voided my warranty? I’d prefer fixing it if I can.

1st check and make sure your batt. Didn't die

slimm9969 said:
IS MY PHONE A BRICK NOW?
If so how can I fix this and if I can’t fix it, how do I return it without showing I voided my warranty? I’d prefer fixing it if I can.
Click to expand...
Click to collapse
if your phone doesn't doesn't turn on at all, there is no way to tell you voided the warranty. However, it is extremely difficult to brick these phones if you don't flash gsm roms/radios.
Make sure the battery isn't dead.

yes, and always do this stuff with the charger plugged in when flashing roms.

Does the Orange(not full)/ Green(Full) charing LED come on at the top of the phone when it is plugged in? If so charge it til green and try again.

moved to general forum.

so it won't even show the htc evo 4g bootscreern? try plugging it in the computer and try adb shell on it with EVO-recovery.zip to see if it connects. If it does, reboot recovery.

Use the RUU..

No lights at all. It's like there isn't a battery in the phone.
Someone suggested the battery might have went out. Shouldn't it still turn on or show an orange light with the plug. I think it should still turn on even without a battery when it's plugged in. ??

HOLD UP!!
WHILE I WAS DRIVING HOME i TOOK THE BATTERY OUT AND WHEN i GOT HOME i PUT IT BACK IN AND IT STARTED RIGHT UP. I STILL NEED TO FIX THE WHOLE ROOT THING.
How do I know if I rooted it (part 1)?

slimm9969 said:
WHILE I WAS DRIVING HOME i TOOK THE BATTERY OUT AND WHEN i GOT HOME i PUT IT BACK IN AND IT STARTED RIGHT UP. I STILL NEED TO FIX THE WHOLE ROOT THING.
How do I know if I rooted it (part 1)?
Click to expand...
Click to collapse
Try to boot the phone into recovery using the evo recover.zip in part one
Rename or remove the pci.img w.e from your sd
Turn the phone off hold down vol. Down and power let it check click down on volume then click power button and boot into recovery then.....
download it unzip it onto your desktop open it up right click on recovery.bat if you on Windows click run. as admin if the screen goes up and just goes away then just click on recovery.bat normally you may have to click on it a few times if it runs and doesn't boot into rec. The 1st time.

The reason it didn't boot is because the "internal memory" had to be "reset", the only "real" way to do that is to take out the battery and wait about 1 minute, then snap it back in and boot up. - Correct me if I'm wrong about that.
So... My theory would be that if It had not needed to been reset to boot up, then It didn't Root... ??

Ok, that sounds logit. But, if you can entertain my questions just a little longer?
What is the rooting going to do to my phone? And what is the NAND Uprotect going to do?

slimm9969 said:
Ok, that sounds logit. But, if you can entertain my questions just a little longer?
What is the rooting going to do to my phone? And what is the NAND Uprotect going to do?
Click to expand...
Click to collapse
Its going to let you run custom roms such as http://forum.xda-developers.com/showthread.php?t=698350

slimm9969 said:
Ok, that sounds logit. But, if you can entertain my questions just a little longer?
What is the rooting going to do to my phone? And what is the NAND Uprotect going to do?
Click to expand...
Click to collapse
Heres a list of roms http://forum.xda-developers.com/showthread.php?t=698044

slimm9969 said:
How do I know if I rooted it (part 1)?
Click to expand...
Click to collapse
Install Terminal Emulator from the Market (free). Launch the terminal, and enter 'su' and press enter. You should be at a root prompt (#). Confirm by typing 'id'; It should return 'uid=0(root) gid=0(root)'

slimm9969 said:
Ok, that sounds logit. But, if you can entertain my questions just a little longer?
What is the rooting going to do to my phone? And what is the NAND Uprotect going to do?
Click to expand...
Click to collapse
Why the HELL are you here trying to root your phone if you don't even know what it'll do?

MuzikJay said:
Why the HELL are you here trying to root your phone if you don't even know what it'll do?
Click to expand...
Click to collapse
I would assume it's so he can learn and progress like the rest of us.
Remember what mom said... If you don't have anything good to say, don't say anything at all.

DaveMW said:
I would assume it's so he can learn and progress like the rest of us.
Remember what mom said... If you don't have anything good to say, don't say anything at all.
Click to expand...
Click to collapse
Well if you're doing something that can potentially destroy your $550 dollar device, you should probably first figure out
A: How it's done
B: WHY YOU'RE DOING IT

MuzikJay said:
Well if you're doing something that can potentially destroy your $550 dollar device, you should probably first figure out
A: How it's done
B: WHY YOU'RE DOING IT
Click to expand...
Click to collapse
A. WHY YOURE DOING IT
and THEN
B. How it's done
i dunno i agree with you.. lol

[Q] MYT4G recovery mode

how do you put the myt4G in to recovery mode?

Wow not to be rude but did you try the search button......hold down the power button and the volume down button at the same time while the phone is off. The select recovery
Sent from my icy cold glacier freezing every phone in its path

i did and i tried search by looking up hbooting myt4g recovery mode couldn't find nothing i even googled it and found this method your giving me but for some reason when i hold down home and power then let go of power button it fastboots..

but now i realized its the vol button i was looking at the myt3G recovery...thank you.

this is not working for me BTW.... can anyone else help out?

l0uisz said:
this is not working for me BTW.... can anyone else help out?
Click to expand...
Click to collapse
You have to have fastboot unselected before it will work. I'm looking into rooting my wife's mt4g, and that took me forever to figure out.
I have a vibrant, so I'm new around these parts. Still doing my research before taking the plunge.

lol! wow thanks i wouldve never figured that out hah! yea well this is very helpful here http://forum.xda-developers.com/showthread.php?t=858996 hoping that you know how to use ADB of course =) now i am ready to root !
OH! btw how do you get off recovery mode ? do u just pull the batt out?

l0uisz said:
lol! wow thanks i wouldve never figured that out hah! yea well this is very helpful here http://forum.xda-developers.com/showthread.php?t=858996 hoping that you know how to use ADB of course =) now i am ready to root !
OH! btw how do you get off recovery mode ? do u just pull the batt out?
Click to expand...
Click to collapse
factory recovery image? that i am aware of, yes. but i might be incorrect on that.

bnielsen40 said:
You have to have fastboot unselected before it will work. I'm looking into rooting my wife's mt4g, and that took me forever to figure out.
I have a vibrant, so I'm new around these parts. Still doing my research before taking the plunge.
Click to expand...
Click to collapse
Please use the term quick boot when referring to the reboot option that does not fully restart the phone.
Use 'fastboot' to refer to the low level utility / protocol that allows image (ROM,etc) flashing via USB

l0uisz said:
lol! wow thanks i wouldve never figured that out hah! yea well this is very helpful here http://forum.xda-developers.com/showthread.php?t=858996 hoping that you know how to use ADB of course =) now i am ready to root !
Click to expand...
Click to collapse
No problem (clicky the thanks button ). I was actually leaning toward this method: http://forum.xda-developers.com/showthread.php?t=834225. I'm still trying to determine the difference between it and the one you linked. The main purpose will not be really to flash any roms (she likes the stock), but to resolve some minor issues she has w/ her device. For example, her market fc's every time it updates - it's getting old to have to uninstall updates before she can even access the market. So I'm wanting to root so I can use TB to freeze the market updater.
cal3thousand said:
Please use the term quick boot when referring to the reboot option that does not fully restart the phone.
Use 'fastboot' to refer to the low level utility / protocol that allows image (ROM,etc) flashing via USB
Click to expand...
Click to collapse
Aha...see this is the stuff I need to learn - I simply used that term b/c it's what was in the reboot option. So it sounds like "fastboot" is the same as Downloading mode on my vibrant, correct? In other words, roms can be flashed via either clockwork or a usb connection to a computer while the device is in fastboot...?
I need to find a tutorial that explains the basics for the mt4g. It's a pretty different animal than my vibrant. I'm creating my own flashable mods for my vibrant, yet I pick up my wife's mt4g and I'm back to square one. Fruustratting!

If you already flashed it, Power Off > Hold Vol Down + Power until booted > Vol Down to recovery and select

bnielsen40 said:
No problem (clicky the thanks button ). I was actually leaning toward this method: http://forum.xda-developers.com/showthread.php?t=834225. I'm still trying to determine the difference between it and the one you linked. The main purpose will not be really to flash any roms (she likes the stock), but to resolve some minor issues she has w/ her device. For example, her market fc's every time it updates - it's getting old to have to uninstall updates before she can even access the market. So I'm wanting to root so I can use TB to freeze the market updater.
Click to expand...
Click to collapse
thats what i want i don't want to deal with flashing roms and all that crap lol i just want ROOT and keep it stock i just better not forget to UNroot before accepting an OTA update lol

hey i'am successfully rooted now with stock ROM! with the link i gave you! i think you should use the one i gave you its more detailed that the one you linked to me...theres a few things missing there in your link.

[Q] Help I dont know what happen here

okay I been a G2 User for oh a few long months. I have had my phone Perm rooted with the shipped rom since the second day I had it. I have since bravely installed Clock world recovery and had no issues at all...flash many roms played around and enjoyed the many various versions out there...but last night my phone froze for no apparent reason, I had no choice but to pull the battery. When I installed the battery I can only get to either Hboot or Fastboot and wont go any further. Did plunty of hours of searching for an answer and with so many different things to try and me being someone a newbie I'm afraid to go any further than I have. I did download the OTA 2.3.4 recovery and did the following
Under the boot loader I can not slect anything using the track pad or volume keys.
1. Copied PC10Img.zip to the sd card
2. Fastboot the bootloadeder
3. Updated with no problems
4 Rebooted phone and still comes up to bootloader.
Downloaded ADB drivers to follow some things I read. I was able to see the phone using the fastboot and gave the command as follows fastboot-windows.exe reboot. Phone reboots and boots into Android however I dont have root and if I shut the phone off it powers back upto the bootloader again forcing me to adb command line reboot the phone again... I still have S-off but I suspect thats a false flag now, I'm lost as to what I need to do to get this darn phone in a working order ...dont care about the root stuff at this point ...
Any help suggestions links to what maybe already answered would be great.

try taking out ur memory card before powering up

smokeuout said:
try taking out ur memory card before powering up
Click to expand...
Click to collapse
tried that with no luck... ;-( still doing google and forum searches for answers to this...I'm in brazil for a few months so doing a warranty on this is not an option till I get back and it will still hopefully be under warranty when I do...I'm just stuck that it goes straight into the bootloader ....puzzles me

try the wiki...its the gospel truth for solving problems

Flash the 2.3.4 PC10IMG. Enjoy Brazil. Downgrade and reroot when you get back to the states.
Sent from my T-Mobile G2 using Tapatalk

smokeuout said:
try the wiki...its the gospel truth for solving problems
Click to expand...
Click to collapse
Amen.
Sent from my T-Mobile G2 using Tapatalk

Could be a busted emmc chip. If it is, nothing left to do but throw in the towel...
Sent from my HTC Vision using XDA Premium App

kpetrie77 said:
Flash the 2.3.4 PC10IMG. Enjoy Brazil. Downgrade and reroot when you get back to the states.
Sent from my T-Mobile G2 using Tapatalk
Click to expand...
Click to collapse
Well I did do the pc10img 2.3.4 and I can get it back to booting using the fastboot reboot command however I cant seem to find the downgrade pc10img if you know of a good link please shoot it my way.

Google "shipped roms PC10IMG_Vision_TMOUS_1.19.531.1_Radio_12.21.60.09b_26.02.01.15_M2_release_149459_signed.zip"
Sent from my T-Mobile G2 using Tapatalk

kpetrie77 said:
Google "shipped roms PC10IMG_Vision_TMOUS_1.19.531.1_Radio_12.21.60.09b_26.02.01.15_M2_release_149459_signed.zip"
Sent from my T-Mobile G2 using Tapatalk
Click to expand...
Click to collapse
Thanks I got it hopefully this works...However I notice today when i rebooted even though my S-off shows it does show a different Hboot version 082.008 and I dont recall if that the same one or a different one...Hopefully this doesnt create a big issue with downgrading this stupid phone..since this all occured I can get anything better than 2G when I had Edge out the skirts of town and HSPA when I was in town here in brazil even though doesnt matter which you get your still only going to get 256kpbs at best...Cell service here in Brazil really stinks to high heaven IMPO...anyways I let you know when this has been attempted and if it worked. I got my fingers crossed it works and again thank you for the assistance..

kpetrie77 said:
Google "shipped roms PC10IMG_Vision_TMOUS_1.19.531.1_Radio_12.21.60.09b_26.02.01.15_M2_release_149459_signed.zip"
Sent from my T-Mobile G2 using Tapatalk
Click to expand...
Click to collapse
***UPDate***
I did that update with what you listed above...It corrected a few things...it put the Hboot 082.000 with S-off still in effect. I got my edge connection back which is great however I'm still unable to do a straight boot without having to use the fastboot command "reboot" with my pc...however the phone doesnt appear to be as sluggish with the 2.3.4 version on it.. I still searching as we speak reading everything I can find to fix this problem if its fixable...
but regardless thanks again for giving me a heads up..

Lost all hope...

It seems that I was fiddling with my OTA and I lost my original build Kind of bummed out, and also the fact that I don't even know how to do a full backup. I did a nandroid backup which doesn't even work. I update to the new ICS firmware and messed up everything...Now I'm left in a gutter feeling utterly upset and don't know what to do. If there's anybody who pity's me, please help. It would be sincerely appreciated. I just want to start off fresh.

Mkami said:
It seems that I was fiddling with my OTA and I lost my original build Kind of bummed out, and also the fact that I don't even know how to do a full backup. I did a nandroid backup which doesn't even work. I update to the new ICS firmware and messed up everything...Now I'm left in a gutter feeling utterly upset and don't know what to do. If there's anybody who pity's me, please help. It would be sincerely appreciated. I just want to start off fresh.
Click to expand...
Click to collapse
So where are you at right now. What rom and what exactly have you done to your tab.

Mkami said:
It seems that I was fiddling with my OTA and I lost my original build Kind of bummed out, and also the fact that I don't even know how to do a full backup. I did a nandroid backup which doesn't even work. I update to the new ICS firmware and messed up everything...Now I'm left in a gutter feeling utterly upset and don't know what to do. If there's anybody who pity's me, please help. It would be sincerely appreciated. I just want to start off fresh.
Click to expand...
Click to collapse
Yeah, I share the pity with you Mate. You shouldn't have to look at that busted tab. Just put that shameful thing in a box and mail it to me, to help ease your pain. Heck, I'll toss in shipping so you won't suffer further insult and pain...
Seriously, though, there are plenty of tools and procedures here to bring it back to life.
First off, before you muck things up further, I would look in your nandroid backup, and get the UID number. Hopefully you wrote this down somewhere before you originally messed with things?
For starters, I would goto this link, and see if it works for you...
http://forum.xda-developers.com/showthread.php?t=1699277
The english steps are not the best in the world, but you will get the general idea.
MD

shaun298 said:
So where are you at right now. What rom and what exactly have you done to your tab.
Click to expand...
Click to collapse
At this moment right now, my a500 tab has that orange light on the bottom and it stays there, and when I turn on the tab it starts up normally like it would, and when it does it turns off. The strange thing is that orange charging light where the power button is, stays on even though I'm not even charging it.
I've tried changing the OTA, but after when it starts in the corner it says something like. " Not official blob" I'm not even sure I know what that even means....I have everything including nandroid backed up all the files into the SD card I had in my tab, I notice is there somewhere due to the amount of space it consumed on my SD.
So please! IF you know of any way to fix this I would be in great appreciation, also it's been a month since I've had this tab, as well I have a 2 year warranty.

Moscow Desire said:
Yeah, I share the pity with you Mate. You shouldn't have to look at that busted tab. Just put that shameful thing in a box and mail it to me, to help ease your pain. Heck, I'll toss in shipping so you won't suffer further insult and pain...
Seriously, though, there are plenty of tools and procedures here to bring it back to life.
First off, before you muck things up further, I would look in your nandroid backup, and get the UID number. Hopefully you wrote this down somewhere before you originally messed with things?
For starters, I would goto this link, and see if it works for you...
http://forum.xda-developers.com/showthread.php?t=1699277
The english steps are not the best in the world, but you will get the general idea.
MD
Click to expand...
Click to collapse
Hahaha funny guy! If you haven't seen my post its here and the reasons. Also I do have the UID saved on a text format on my pc...will that work??
So here is the issue are the current moment friend.
my a500 tab has that orange light on the bottom and it stays there, and when I turn on the tab it starts up normally like it would, and when it does it turns off. The strange thing is that orange charging light where the power button is, stays on even though I'm not even charging it.
I've tried changing the OTA, but after when it starts in the corner it says something like. " Not official blob" I'm not even sure I know what that even means....I have everything including nandroid backed up all the files into the SD card I had in my tab, I notice is there somewhere due to the amount of space it consumed on my SD.
So please! IF you know of any way to fix this I would be in great appreciation, also it's been a month since I've had this tab, as well I have a 2 year warranty.

Have you tried putting a stock update.zip on the root of your external sdcard and booting the tablet by holding the volume down button (left volume rocker) down while pressing the power button until the tablet finds the file and installs it. This should bring you back to unrooted stock ICS with locked bootloader and you can start over. Remember, this must be an update.zip file that is extracted from a stock RUU. You can't just rename a RUU file to update.zip.

Mkami said:
Hahaha funny guy! If you haven't seen my post its here and the reasons. Also I do have the UID saved on a text format on my pc...will that work??
So here is the issue are the current moment friend.
my a500 tab has that orange light on the bottom and it stays there, and when I turn on the tab it starts up normally like it would, and when it does it turns off. The strange thing is that orange charging light where the power button is, stays on even though I'm not even charging it.
I've tried changing the OTA, but after when it starts in the corner it says something like. " Not official blob" I'm not even sure I know what that even means....I have everything including nandroid backed up all the files into the SD card I had in my tab, I notice is there somewhere due to the amount of space it consumed on my SD.
So please! IF you know of any way to fix this I would be in great appreciation, also it's been a month since I've had this tab, as well I have a 2 year warranty.
Click to expand...
Click to collapse
Well, you get the orange light because your EC Pwr management is probably fubarred. That should be fixed when you install a stock rom as suggested in both mine and the other poster.
Considering you have your UID, you should be ok.
Of course I don't know if this is a 3.2 or an ICS UID. Best to have both. The sbk is the same, but the uid numbers differ.
If it's a 3.2., check the Q&A thread for a post I did for a guy earlier today.
But you should be able to follow the steps for the update I posted earlier.
Blob means Bootloader. And looks like you had an unlocked bootloader?
Try to roll back to 3.2. That's where I would start.
MD

cruise350 said:
Have you tried putting a stock update.zip on the root of your external sdcard and booting the tablet by holding the volume down button (left volume rocker) down while pressing the power button until the tablet finds the file and installs it. This should bring you back to unrooted stock ICS with locked bootloader and you can start over. Remember, this must be an update.zip file that is extracted from a stock RUU. You can't just rename a RUU file to update.zip.
Click to expand...
Click to collapse
What do you mean by RUU? Also I've tried a couple of the OTA updates, when I first got the tab it was on 3.1 HC didn't even update it or anything, just had a custom ICS ROM on it. Do you think you can post the steps or anything on how to do this properly and go fresh? It would be sincerely appreciate buddy.

Moscow Desire said:
Well, you get the orange light because your EC Pwr management is probably fubarred. That should be fixed when you install a stock rom as suggested in both mine and the other poster.
Considering you have your UID, you should be ok.
Of course I don't know if this is a 3.2 or an ICS UID. Best to have both. The sbk is the same, but the uid numbers differ.
If it's a 3.2., check the Q&A thread for a post I did for a guy earlier today.
But you should be able to follow the steps for the update I posted earlier.
Blob means Bootloader. And looks like you had an unlocked bootloader?
Try to roll back to 3.2. That's where I would start.
MD
Click to expand...
Click to collapse
Hmmm....I'm not even sure what I am doing wrong but whatever it is, it seems to be not working. I looked for you post for the earlier person that you did, but don't know what it is under. By the way when I first bought the tab it was under 3.1 HC and after getting flexreaper it became to ICS 4.0.3...
So like everytime I turn on the tab it shuts down instantly, as well every time I try to boot an update.zip file onto the SD card it shows this animation of the android with this circular sphere in it's stomach after that it falls over with a red caution sign.

Mkami said:
So like everytime I turn on the tab it shuts down instantly, as well every time I try to boot an update.zip file onto the SD card it shows this animation of the android with this circular sphere in it's stomach after that it falls over with a red caution sign.
Click to expand...
Click to collapse
In my experience the common cause for ending up with a caution sign is a corrupted update.zip (incomplete download, bad SD card, etc.). As for the tablet shutting down, my guess is that's related to the power management functions being broken.

im not THEE most savvy here but i do know a few methods and find it easy to discover lesser known ones, i feel bad for you . if you want you can skype video me and ill try talking it over and maybe a few methods? :highfive:
edit: ok from what i can tell your update was bad and your bootloader is causing problems, the power problems are probably arising from the bad power management as moscow desire told.
the tabs obviously rooted n all right? ok so how about flashing the v7 ics bootloader then trying a custom rom?......<-also recommended by moscow desire

lcd047 said:
In my experience the common cause for ending up with a caution sign is a corrupted update.zip (incomplete download, bad SD card, etc.). As for the tablet shutting down, my guess is that's related to the power management functions being broken.
Click to expand...
Click to collapse
You're right! I was able to fix it and boot up to the usual! Thanks mate!

chismay said:
im not THEE most savvy here but i do know a few methods and find it easy to discover lesser known ones, i feel bad for you . if you want you can skype video me and ill try talking it over and maybe a few methods? :highfive:
edit: ok from what i can tell your update was bad and your bootloader is causing problems, the power problems are probably arising from the bad power management as moscow desire told.
the tabs obviously rooted n all right? ok so how about flashing the v7 ics bootloader then trying a custom rom?......<-also recommended by moscow desire
Click to expand...
Click to collapse
Hi Chismay, well I thought I fixed the issue and the problem. Guess again I did not This I can't believed I used a leaked ICS OTA, kinda ruined most of the things in my tab. Lol just had it for a month and already messed it up by fooling around with it. But your help is greatly appreciated buddy! Would like to get a one on one instructions on what I should do.
Cheers!

Correct me if I'm wrong on this...
1. You originally had Honeycomb on your tablet.
2. You flashed FlexReaper on your tablet
3. You probably got a recent version of FlexReaper.
4. You never upgraded your bootloader.
5. You can still get access to recovery.
If all of these are correct, then I think I know what the problem is. It appears you flashed a rom that requires the ICS bootloader and not the Honeycomb bootloader.
This, I think, is an easy fix...
1. Download the following file: http://www.darktremor.info/files/FLEXREAPER-R12.5-ICS-1.031.00.zip (this is an older version I have on my Acer A500).
2. Put the file on your SD card.
3. Boot up into recovery (if you can't get there, stop here).
4. Once you are in recovery, flash the FlexReaper file you just put on your SD card.
5. Now try to boot and see if it works.
Let me know how it works either here, in a PM, or e-mail me at [email protected]. If you need further assistance, don't hesitate to contact me.
Mkami said:
Hi Chismay, well I thought I fixed the issue and the problem. Guess again I did not This I can't believed I used a leaked ICS OTA, kinda ruined most of the things in my tab. Lol just had it for a month and already messed it up by fooling around with it. But your help is greatly appreciated buddy! Would like to get a one on one instructions on what I should do.
Cheers!
Click to expand...
Click to collapse

tkirton said:
Correct me if I'm wrong on this...
1. You originally had Honeycomb on your tablet.
2. You flashed FlexReaper on your tablet
3. You probably got a recent version of FlexReaper.
4. You never upgraded your bootloader.
5. You can still get access to recovery.
If all of these are correct, then I think I know what the problem is. It appears you flashed a rom that requires the ICS bootloader and not the Honeycomb bootloader.
This, I think, is an easy fix...
1. Download the following file: http://www.darktremor.info/files/FLEXREAPER-R12.5-ICS-1.031.00.zip (this is an older version I have on my Acer A500).
2. Put the file on your SD card.
3. Boot up into recovery (if you can't get there, stop here).
4. Once you are in recovery, flash the FlexReaper file you just put on your SD card.
5. Now try to boot and see if it works.
Let me know how it works either here, in a PM, or e-mail me at [email protected]. If you need further assistance, don't hesitate to contact me.
Click to expand...
Click to collapse
Hahaha! Good job on guessing all that! I just followed your order from step to step and I was about to boot up normally! Everything might be erased and stuff, but hey at least I have my tablet working again :good: Case solved!

[GUIDE] How to unbrick desire hd

I am closing this thread because i think it is not appropriate for members to use it. Its too risky because it may hard-brick your device. So kindly mod close this thread

It's work???
Did u try it @@?
i have the same problems

binggu1996 said:
It's work???
Did u try it @@?
i have the same problems
Click to expand...
Click to collapse
yes it works

Ok, i will try it
Thank u!

binggu1996 said:
Ok, i will try it
Thank u!
Click to expand...
Click to collapse
Just hit the thanks button

was scancet
Sr, Why does it take so much time to read the Rom??

fortunately i have not (yet ) bricked my dhd.
thanks for taking the time to share this

i cant go into hboot mode ( (did press volume down + power button)
any help?

binggu1996 said:
i cant go into hboot mode ( (did press volume down + power button)
any help?
Click to expand...
Click to collapse
press volume down and power button for atleast 15 minutes

binggu1996 said:
i cant go into hboot mode ( (did press volume down + power button)
any help?
Click to expand...
Click to collapse
OP is incorrect in stating this method unbricks a DHD with a corrupted hboot.
Sent from my Telus HTC Desire HD using XDA Premium.

usman_fareed said:
Hi , today i will show you how to unbrick your desire hd which is bricked through flashing wrong rom or wrong h-boot or baseband or downgrading etc
First of all check weather it can be unbricked or not
Turn on your dead dhd and press power button for 5 minutes and see if it starts. When mobile turns on after 5 minutes it will start countinous vibration.
Plugin the charger and see that the charging light is turn on or not.
If both conditions are true than you can unbrick your dhd
Before doing any thing please charge your battery fully!
So lets get started
First of all download RUU http://shipped-roms.com/download.ph...60.29_26.14.04.28_M_release_225512_signed.exe
Now extract PD98IMG.zip from RUU by Following this guide http://forum.xda-developers.com/showthread.php?t=1672425 (only read 4. Flashing RUU manually > 4.1 Getting PG58IMG.zip from RUU) but note that when you rename the rom change it to PD98IMG.
Remove sd card insert it into pc and format it
Now place PD98IMG.zip into the sd card and insert into your mobile.
Press volume down + power Button for at least 15 minutes.
H-boot will appear now wait for the device to read PG98IMG from sd card. It will take 40 - 60 minutes or even more. You can plug in the charger at that time.
After that it will read and asks for permission press volume up button for yes and after that it will start flashing the rom.
When flash completes turn dhd on.
Thats it
cradits: kgs1992 for guide and to this thread for helping to unbrick http://forum.xda-developers.com/showthread.php?t=1723196
Dont forget to hit like
Click to expand...
Click to collapse
Just a few observations:
Your device is not bricked. If it were then there would not be anything to do with your phone but to put in the waste bin.
Your bootloader has been corrupted/messed by flashing ENG S-OFF or a froyo RUU in a Gingerbread device and therefore is in superslow motion but the phone boots after about 30 minutes which means that the devices is working.
Flashing a RUU is not always possible is you are not S-OFF or if there is no official RUU for your device and you have no goldcard.
Flashing a RUU with a messed bootloader could definitely brick your device.
Fix for the messed bootloader has long been in the Ace Think Tank thread, available for everybody.

glevitan said:
Just a few observations:
Your device is not bricked. If it were then there would not be anything to do with your phone but to put in the waste bin.
Your bootloader has been corrupted/messed by flashing ENG S-OFF or a froyo RUU in a Gingerbread device and therefore is in superslow motion but the phone boots after about 30 minutes which means that the devices is working.
Flashing a RUU is not always possible is you are not S-OFF or if there is no official RUU for your device and you have no goldcard.
Flashing a RUU with a messed bootloader could definitely brick your device.
Fix for the messed bootloader has long been in the Ace Think Tank thread, available for everybody.
Click to expand...
Click to collapse
this method works on that devices which are bricked through flashing wrong rom or degrading so pd98img.zip is the only thing which helps you to recover bootloader. BY the way thanks for your kind information.

usman_fareed said:
this method works on that devices which are bricked through flashing wrong rom or degrading so pd98img.zip is the only thing which helps you to recover bootloader. BY the way thanks for your kind information.
Click to expand...
Click to collapse
That is not a bricked device. Bricked literally means not working and non reparable. Soft bricks is what you are trying to say.
Sent from a dream.

Teichopsia said:
That is not a bricked device. Bricked literally means not working and non reparable. Soft bricks is what you are trying to say.
Sent from a dream.
Click to expand...
Click to collapse
oh now i get it its a soft brick

usman_fareed said:
this method works on that devices which are bricked through flashing wrong rom or degrading so pd98img.zip is the only thing which helps you to recover bootloader. BY the way thanks for your kind information.
Click to expand...
Click to collapse
Wrong. It seems that have not read what I wrote. Anyway, take into consideration that many devices are subject to get useless with this method. So, that is all the help that people is going to get from me.

glevitan said:
Wrong. It seems that have not read what I wrote. Anyway, take into consideration that many devices are subject to get useless with this method. So, that is all the help that people is going to get from me.
Click to expand...
Click to collapse
And to think you call me a grinch. :screwy:
Sent from a dream.

Teichopsia said:
And to think you call me a grinch. :screwy:
Sent from a dream.
Click to expand...
Click to collapse
I am not being a grinch, but lately anyone can state anything with no empirical evidence but their own oblivious of what recognized dev's state. So, I have no problem but will not provide any help in this cases.

I was installing a Custom ROM on my Inspire 3G and kept this thread at hand in a tab, it made me feel secure that incase I mess things up like my Galaxy Y, I will still have a way out! Thanks Fareed.

try next time ))

Soliddiesel said:
I was installing a Custom ROM on my Inspire 3G and kept this thread at hand in a tab, it made me feel secure that incase I mess things up like my Galaxy Y, I will still have a way out! Thanks Fareed.
Click to expand...
Click to collapse
You SHOULD NOT take this thread into consideration. If you have a messed bootloader issue you will have to fix it with the tool provided in the guide in my signature.
If you fail flashing a custom rom, then there is no need to flash a RUU, there are many other easier ways to sort the issue out. If you need help, find it in the right place (the thread in my signature)...:good: