Hello, guys
I've successfully bricked my desire hd about 20 minutes ago by following:
via adb on pc:
adb push boot.img /data/local
via terminal on phone:
su
dd if=/data/local/boot.img of=/dev/block/mmcblk0p18
Now, I'm going to tell you why i did it - of course, it wasn't intentional..
I wanted to use http://forum.xda-developers.com/showthread.php?t=835449 boot image, but I had opened this: http://www.dkszone.net/install-hboot-htc-desire-hd-engineering tutorial too and the commands i used were from this instead of the first one
If you guys can tell me how I can repair my HBOOT bricked device ...you will probably save my life... i'm very sad now and I believe that any xda member will try to help me, that's why I don't panic for now
once more.. thanks for anything, for any answers
Nice one, mate.. That is almost the one and only command that can brick a DHD.
If you have not rebooted, use my ENG S-OFF tool. It will repair your hboot. Tick the "I have radio s-off" -box.
You have to send your phone to HTC, they will repair it. It will probably cost something.
jkoljo said:
Nice one, mate.. That is almost the one and only command that can brick a DHD.
If you have not rebooted, use my ENG S-OFF tool. It will repair your hboot. Tick the "I have radio s-off" -box.
You have to send your phone to HTC, they will repair it. It will probably cost something.
Click to expand...
Click to collapse
hm I think that they wont bother to check what's wrong if it's already impossible now to turn on the device. They will replace mobo and that's all I think
And in English, Mike means that the device will be under warranty. Then the repair process would be free
ehheh, yes i have warranty, but how can i fix it now with your ENG S-OFF tool ?
ahh.. you say if i not rebooted i see... i understand.. omg i am stupid
but when i can brick the phone, how can i unbrick it.. can i open dhd and do it manually or how ?
btw i need the phone to the tomorrows test lol
You cannot repair it easily yourself, brick is a brick, beyond repair. Only HTC can revive your phone now.
blueeyeblue said:
ehheh, yes i have warranty, but how can i fix it now with your ENG S-OFF tool ?
ahh.. you say if i not rebooted i see... i understand.. omg i am stupid
but when i can brick the phone, how can i unbrick it.. can i open dhd and do it manually or how ?
btw i need the phone to the tomorrows test lol
Click to expand...
Click to collapse
i'm assuming if you got to the point of flashing an engineering hboot, that you ran gfree and your phone is radio s-off
this being the case, it is actually fixable.
the trick is i don't know exactly how to do it yet. better off just warrantying it.
but if you boot it up with volume-up i believe, it should vibrate 3 times, give you a black screen and enumerate as a qualcomm device to your computer.
scotty2
Sorry this is of no help, but why use that really outdated Kendon thing, when most kernels now support what it does?
because i was too curious what it can do
can you tell me how htc repair this without opening the phone ? i think as mike said.. they will just give me new or am i wrong ?
and when they give me new, will i have to buy xtc clip to downgrade to 1.32, i mean to make it s-off, or is goldcard enough ? please don't smile to this.. because i'm flashing fan xD
I read somewhere, that there are two types of BOOT, but maybe i'm wrong..
there should be initial boot loader and secondary boot loader or something, i hope the initial is unflashable so I have successfully flashed only the secondary one, I hope there must be way to fix it.. even htc wouldn't disassemble it ..i hope
jkoljo said:
You cannot repair it easily yourself, brick is a brick, beyond repair. Only HTC can revive your phone now.
Click to expand...
Click to collapse
KK, thanks last question to you is what I should tell them when I will go tomorrow to the HTC.
If you feel like it, you can say that the device just stopped working, and you do not know what could possibly be wrong with it. "It just does not turn on anymore".
Then the other option is to tell the truth, that you messed up and now it does not work. Then it will cost you to get it repaired.
jkoljo said:
If you feel like it, you can say that the device just stopped working, and you do not know what could possibly be wrong with it. "It just does not turn on anymore".
Then the other option is to tell the truth, that you messed up and now it does not work. Then it will cost you to get it repaired.
Click to expand...
Click to collapse
I still think that they can't repair it without disassembling, do you ?
So if I tell them truth I will have to pay like almost for new phone, because they will have to replace NAND chip. I think I will say, that I changed the SIM card and my device just stopped working and I will try to pretend like a n00bzor (as I am) xD
I really don't know how I could did it, I thought it's related with it.. the dev folder under system, but when I went there over ROOT explorer or QtADB it has 0kBs..
So once more.. thank you very much guys, and jkoljo I already used the tool.. I already use your tool, it's good, but.. mmh I am stupid
Hi, guys
by the way I forgot to ask you why it got brick
is and difference between this:
su
dd if=/data/local/boot.img of=/dev/block/mmcblk0p18
and this:
fastboot flash boot boot.img
commands ?
is boot different from HBOOT ?
I found on this forum android flasher 1.5.5 and there is option to flash HBOOT ?
what is initial boot loader - is it boot or HBOOT, please tell me, cuz I'm little confused :/ thanks
I think boot.img us the kernel as far as I am aware
Sent from my Desire HD using XDA Premium App
okay, thanks
Yep, you replaced your device's bootloader with kernel, which obviously results in a mess.
It is like replacing your PC's bios with scrap data.
So, is this officially the first truly bricked DHD on XDA?
Yep, that is right.
Related
Ok, you can get into BL, flash roms, but no recovery and the phone doesnt boot, basicly a boot loop. Now if i RMA this phone and they go into bootloader and see the S-Off flag, will this more than likely void my warrenty or would they have any clue about this? If so, i guess i could flash a radio and pull the battery during the flash to ensure they cant read that lol.
Any help/info is appreciated, thanks
K, guess no one has a answer for wether or not HTC Service & Repair center will know what S-Off means if they put my phone in bootloader when i send them back a phone that wont boot so i cant reverse the unrevoked forever as far as i know, if im wrong, maybe someone can correct me. Would hate to have them not warrenty the phone due to being able to see the S-Off flag in bootloader.
I guess i could brick it bad enough they cant get into bootloader, just was hoping for some feedback so i didnt have to damage the phone more than it already is lol.
anderd said:
K, guess no one has a answer for wether or not HTC Service & Repair center will know what S-Off means if they put my phone in bootloader when i send them back a phone that wont boot so i cant reverse the unrevoked forever as far as i know, if im wrong, maybe someone can correct me. Would hate to have them not warrenty the phone due to being able to see the S-Off flag in bootloader.
I guess i could brick it bad enough they cant get into bootloader, just was hoping for some feedback so i didnt have to damage the phone more than it already is lol.
Click to expand...
Click to collapse
There is an S-ON tool on the Unrevoked Forever page. You can use that.
If you used Toast's method, all you have to do is get back to a SHIP bootloader. You can do that easily by running an RUU.
anderd said:
Ok, you can get into BL, flash roms, but no recovery and the phone doesnt boot, basicly a boot loop. Now if i RMA this phone and they go into bootloader and see the S-Off flag, will this more than likely void my warrenty or would they have any clue about this? If so, i guess i could flash a radio and pull the battery during the flash to ensure they cant read that lol.
Any help/info is appreciated, thanks
Click to expand...
Click to collapse
Your phone boots -> it is not bricked. Don't RMA it until you try to resolve the problem.
To answer your question.....yes if they figure out you put unapproved firmware on the phone they do have the right to void your warranty..yes its legal now but htc or sprint can choose to void..that being said like jerryparid mentioned if it boots its not bricked so try to fix, do some searching you might just find an answer that helps.....also I'd get your flame suit on because it might get hot in here.
jerryparid said:
Your phone boots -> it is not bricked. Don't RMA it until you try to resolve the problem.
Click to expand...
Click to collapse
He's right. If your phone boots at all, even if it's just into the bootloader then it is fixable.
There may be better ways of doing it but I would suggest you download the ENG HBOOT from toasts rooting part 2 thread, put it on the root of your sdcard and boot into your bootloader and just let it run. You'll have to set everything back up, including updating your recovery image but at this point there is no reason to have it replaced just yet.
Let us know how it goes, if you need any help bringing your phone back to life we're here for ya!
User Name
Ok let me try and clarify this...
I can get into bootloader, i can flash a rom, radio, hell even RUU from PC, all complete 100%, can not get into recovery, even if i flash a recovery image. The phone DOES NOT BOOT, starts at white HTC start up screen, stay on for about 4 seconds, reboots. You can clear storage, reload roms, radios, none of that gets the phone to boot or do anything other than reboot every 4 seconds.
So nothing i can think of will fix this, ive tried roms loaded via SD card, via RUU from PC when phones in bootloader, reflashing radios, reflashing recovery, nothing works. Phone continuesly reboots after first 4 seconds of being powered on. Never boots past HTC screen. I guess i should just try and brick it 100% so they cant get into boot loader and see the S-Off flag.
Damn phones.. lol...
** EDIT **
In short i guess basicly all im saying in the above, is ive tried everything already mentioned so far prior to my post and none of that did jack squat for me... lol.
How are you flashing roms from the bootloader?
And if you cant get into recovery how are you "clearing storage"?
No offense, I understand your frustration but I have to think you're not doing something right.. You'd be the first (not saying it's impossible) person to have a phone that gets into the bootloader but is not fixable..
nebenezer said:
How are you flashing roms from the bootloader?
And if you cant get into recovery how are you "clearing storage"?
No offense, I understand your frustration but I have to think you're not doing something right.. You'd be the first (not saying it's impossible) person to have a phone that gets into the bootloader but is not fixable..
Click to expand...
Click to collapse
Ok, yet again, a clarification, i cant get into a Custom Recovery, power+vol down, all that works fine, can flash rom (load the zip on the sd card, detects, lets you flash via zip) or via RUU in windows this method, now if you scroll down to "recovery" on the menu and click on it, it starts to load then phone reboots and back to square one. Sorry if my hboot/bootloader/recovery understandings are slightly off or differ from anyone elses.
** EDIT **
Ill see if i can make a youtube video with my crappy webcam here in a bit and upload it and maybe that will make it easier to understand whats going on. I had also taken it to a sprint repair center and they couldnt figure it out themselfs lol. So if i can fix it myself, im going to get it to HTC before i my luck runs out some how and they wont fix it lol. THanks for the help guys, i appreciate the replys and help so far!
I was trying to Hboot different table and some radio and I accidently brick my phone.
When I try to turn it on it just vibrates for a second and nothing shows up just blank black screen. Help ME Please !
I have managed to show the info in the fastboot commander. I can flash radio h-boot spl and recovery here. I can shut down phone from this software and it shows charging light as well.
But still blank on boot. Can any body help me to make it usable
Sorry to say, but I think you bricked it. You can't flash GSM radios and partition tables to the CDMA Desire.
Is there any way that I can unbrick it ?
Shabihbhai said:
Is there any way that I can unbrick it ?
Click to expand...
Click to collapse
Hmm... i dont know when its CDMA.but i think this may fix it. Okay you need to download fastboot commander from here: http://forum.xda-developers.com/showthread.php?t=1193915
then you need to download official htc desire RUU it may work for CDMA too (i think) http://forum.xda-developers.com/showthread.php?t=1193915 download the "HTC Desire Android 2.3 Upgrade"
Allright now you got the downloads. You also need Java and the HTC driver if you dont got that. Pull battery out of your phone and set it back again. Connect your phone to your pc (dont turn it on you shold just hear that sound when windows found your device) open fastboot commander program on your pc and go to the tab "boot, sys and userdata" mark all the stuff you can and press remove or something like that
Your phone is only a black screen when you turn it on, dont worry. Open the RUU program now and follow the instructions to revert to android 2.3. I hope that helpe if not let me know what didnt worked and i may help you a little more.
Shabihbhai said:
Is there any way that I can unbrick it ?
Click to expand...
Click to collapse
Not if its really bricked, such as a radio brick, which you more than likely have.
You can try flashign a CDMA RUU like suggested above, but keep your fingers crossed.
I'm pretty sure even flashing a different SPL from alpharev would've done a great job of bricking it...
Yes it probably would
Sent from my HTC Desire using xda premium
Before doing anything that u guyz have suggested would this thing help that i got? This is RUU_Bravo_C_Froyo_USCC_WWE_2.11.573.5_Radio_2.15.00.11.16_release_168495_signed.exe which is sized 171mb. I dounloaded it. What is this thing anyway. Could anyone explain ?
I got it from http://forum.xda-developers.com/showthread.php?t=947961
its an RUU (Rom Upgrade Utility) to upgrade the rom.
What was a guy who doesnt know what an RUU is, doing flashing Hboots?
will u tell me if it has to do anything to make my phone work ?
Like we said earlier, you can try. We can't tell you if it will work o not as your phone may be bricked. However, it should give you failure codes, which may give us more information.
Theres no harm in trying. It probably is bricked anyway.
Good thing about Alpharev hboot is that they lock it so that one doesnt accidentally flash a wrong hboot.. See if you can get into hboot mode (Vol- Power)...If it's still black, use the PB99IMG.zip method of flashing RUUs.. I wont elaborate. They are a dozen threads on it do/
Don't flash an ruu now.
I'm not sure how to fix your problem but I don't believe it's bricked. It is sooo hard to brick these things. I have thought a million times that mine was bricked, just be patient search forums (not just xda) and read a lot. That's the beautiful thing about the internet. You are bound to find many people that have gone through what you are and have fixed it. I will look a little for you but i'm not on that much so I don't know how much help that can be. If your search doesn't provide useful information try changing your keywords. I'll post again later tonight with what I have found if you haven't figured it out already. Good luck.
This RUU is giving me error 110 Cant open file when it is on 60-70 %. I downloaded it forn HTC support the other time and againg the same error. Then I tried to do another RUU from alltel but this gave me error that this was not supported. Help !
Did you flash RUU via computer or via SD card?
SwiftKeyed from dGB with Transparent XDA App
Was your HBOOT previous S-OFF?
MatDrOiD said:
Did you flash RUU via computer or via SD card?
SwiftKeyed from dGB with Transparent XDA App
Click to expand...
Click to collapse
Through PC
heavymetalmage said:
Was your HBOOT previous S-OFF?
Click to expand...
Click to collapse
1.06 it was S-OFF
jclare85 said:
I'm not sure how to fix your problem but I don't believe it's bricked. It is sooo hard to brick these things.
Click to expand...
Click to collapse
Unfortunately the OP has done 2 things which are both known to definitely brick his phone....
OP, I'm not holding out much hope for you...
So, some more trouble with my Desire
I flashed a new ROM, it was stuck at the end of the boot anim
Tried RUU-ing, since this worked the last time this happened
RUU worked
When the phone booted, it came to the lockscreen, but then restarted itself and now it's doing the same;
boot>boot logo>boot anim>lockscreen>reboot>repeat
I can't go to bootloader, fastboot or recovery, because FastBoot is activated by default on 2.3.3 HTC
So, what do I do?
I *think* I've got adb, the phone has S-OFF (doesn't have a recovery though, because the RUU deleted it).
Can't run RUU again, can't go to recovery
Any suggestions?
EDIT: Found a way to enter fastboot and bootloader, I guess that 'clear data' thing might be useful?
EDIT2: Running RUU again, hope it helps!
Run 2.3 ruu from bootloader or fastboot. I think it should work from fastboot.
Sent from my HTC Desire using Flashes and Thunders
Thanks, did that and phone is back to normal
But for some reason, the RUU detects the battery is <30% if on Bootloader, so I have to run it from fastboot... Weird...
Aaaa, now i see, it's you again...
Yup, get used of me asking dumb noob questions
After all, this is how professionals are made...
Or, did you learn everything by yourself? O.O
In both cases, you're full of knowledge (which I will soon obtain, if I keep destroying my phone)
someone755 said:
Yup, get used of me asking dumb noob questions
After all, this is how professionals are made...
Or, did you learn everything by yourself? O.O
In both cases, you're full of knowledge (which I will soon obtain, if I keep destroying my phone)
Click to expand...
Click to collapse
Or..... Read on how to do things properly in the first place lol
Sent from my HTC Desire
someone755 said:
Yup, get used of me asking dumb noob questions
After all, this is how professionals are made...
Or, did you learn everything by yourself? O.O
In both cases, you're full of knowledge (which I will soon obtain, if I keep destroying my phone)
Click to expand...
Click to collapse
It' won't be destroyed until you start repairing it with hammer (srpski alat )...
nlooooo said:
repairing it with hammer (srpski alat )...
Click to expand...
Click to collapse
Haha
Sent from my HTC Desire
jmcclue said:
Or..... Read on how to do things properly in the first place lol
Click to expand...
Click to collapse
That's not how I do things, apparently...
How I do things:
1.Start doing something
2.Mess up
3.Try to repair and make it worse than it was
4.Make a new thread here
5.Partially figure the answer out
6.Read someone's reply on how to REALLY repair it
7.Repeat
The hammer idea is good, it'll be useful someday when I fully brick the poor thing (hopefully not soon)
P.S.
i figured out why the phone did that, with the 'stuck at boot' thing
My Ext4 partition wasn't aligned perfectly and it was about 10% of the size it should've been -.-'
Talk about newb
someone755 said:
That's not how I do things, apparently...
How I do things:
1.Start doing something
2.Mess up
3.Try to repair and make it worse than it was
4.Make a new thread here
5.Partially figure the answer out
6.Read someone's reply on how to REALLY repair it
7.Repeat
The hammer idea is good, it'll be useful someday when I fully brick the poor thing (hopefully not soon)
P.S.
i figured out why the phone did that, with the 'stuck at boot' thing
My Ext4 partition wasn't aligned perfectly and it was about 10% of the size it should've been -.-'
Talk about newb
Click to expand...
Click to collapse
Hahaha atleast ur honest
U should partition ur sdcard with abuntu or 4ext recovery. Iv always used 4ext to partition and never had a problem.
Sent from my HTC Desire
Yeah, almost everyone on this forum is telling me to get 4EXT (which I already got, right after the last crash...)
It's even better than I expected, after reading how CWM is 'all mighty' and stuff...
Hey Guys,
Hope you can help me, I have searched the threads and cannot find an answer.
I have got my hands on DHD, currently it is all stock on 3UK.
It has not been unlocked, but it's stuck in a bootloop and I cannot work out how to fix it.
When I have tried booting into the stock recovery it flashed up a message saying
E: Cant mount/cache/recovery/command - then the phone vibrates 7 times.
I have also tried a factory reset from the bootloader menu but that hasn't worked either?
This is what the phone shows in bootloader
ACE PVT SHIP S-ON RL
HBOOT-2.00.0027
MICROP-0438
RADIO-26.14.04.28_M
eMMC-boot
Sep 7 2011,19:06:24
Anyone got any ideas how i can sort this out?
Cheers
I couldn't figure out what the problem is ,due to you haven't explained what you were doin when this problem occured
Can you try using "Easy Ace Root Tool" maybe it will help to unlock ,root and flash a rom
here is the link
http://forum.xda-developers.com/showthread.php?t=2169515
I hope you'LL solve your problem
Hi,
I wasn't trying to do anything, I know how to unlock, flash recovery, root and use fastboot to flash boot.img
But this has got me stumped, I can't unlock the phone and flash a ROM as USB debugging is not on, but I can get into fast boot.
Sent from my Xperia S, made awesome by XDA.
sudd1976 said:
Hi,
I wasn't trying to do anything, I know how to unlock, flash recovery, root and use fastboot to flash boot.img
But this has got me stumped, I can't unlock the phone and flash a ROM as USB debugging is not on, but I can get into fast boot.
Sent from my Xperia S, made awesome by XDA.
Click to expand...
Click to collapse
Try this:
First donload rom from this site http://shipped-roms.com/index.php?ca...roid&model=Ace
After you download it:
1) conect phone to pc, run instalation ruu
2) during instalation process find in win/temp folder rom.zip
3) copy this file into folder with adb and fastboot files
4) cancel instalation
5) in phone run bootloader than fastboot
6) run command prompt in folder with adb, fastboot and rom files, than run "fastboot oem rebootRUU"
7) wait a few minute until phone goes in ruu install mode (you will see black screen with HTC logo)
8) than from command prompt run "fastboot flash zip room.zip"
9) when it's done if it stay in ruu mode type "fastboot reboot bootlader" and do factory reset
10) reboot and now phone should be repaired
Dude,
Thanks for the instructions.
I followed them but the phone won't go into ruu mode.
After reading some other posts on Xda, I think the motherboard is fried.
I called HTC to find out how much the repair might be they said £25.00 to diagnose the problem and up to £150.00 for parts and installation. FFS !!
Going to search eBay and see if I can find a Dhd to use as a donor and replace the motherboard.
Cheers for your help.:thumbup
Sent from my Xperia S, made awesome by XDA.
sudd1976 said:
Dude,
Thanks for the instructions.
I followed them but the phone won't go into ruu mode.
After reading some other posts on Xda, I think the motherboard is fried.
I called HTC to find out how much the repair might be they said £25.00 to diagnose the problem and up to £150.00 for parts and installation. FFS !!
Going to search eBay and see if I can find a Dhd to use as a donor and replace the motherboard.
Cheers for your help.:thumbup
Sent from my Xperia S, made awesome by XDA.
Click to expand...
Click to collapse
Yes, it is assumed that it's a problem with eMMC on motherboard not working correctly.
But before changing motherboard I would try to change rom.zip to PD98IMG.zip put it on root of micro SDcard.
When your phone is powered off put SD in phone and than power on phone in hboot.
After a while waiting it should ask you to press volume UP to start installation of ROM.
If you get errors like - Fail-PU, than it's obviously that you can repair it only with Riff-box, any other Jtag, og by changing the motherboard.
Sorry for my bad english.
Dude,
I will give the the PD98IMG.zip fix a try, if it works I will let you know.
If not I have found somewhere that will Jtag my DHD for £25, will update you if this works or not. :fingers-crossed:
Dude,
Managed to get a motherboard from eBay for £16.00 all fixed and running Cm11 now
Sent from my Xperia S, made awesome by XDA.
sudd1976 said:
Dude,
Managed to get a motherboard from eBay for £16.00 all fixed and running Cm11 now
Sent from my Xperia S, made awesome by XDA.
Click to expand...
Click to collapse
I want you to answer a question for me. was your old desire hd made in taiwan?
You can check it by removing the battery cover. Its wirtten there.
Mickey why taiwan?
Gussta said:
Mickey why taiwan?
Click to expand...
Click to collapse
I have seen two taiwan made devices that have developed the exact same problem. I never saw a made in china dhd with that problem.
I am trying to do some kind of survey.
And if my guesses are right, then it means those with made in taiwan devices have a very high possibility of brick.(QHSUSB_DLOAD brick).
Made in ?????
Hi Mickey,
My original DHD was from Taiwan, the donor DHD was from China.
I think a survey would be a good idea, I mean if (and it's a big if) it's a design flaw with the Taiwanese devices then HTC might have to do a recall.
It will be interesting to see some results.
sudd1976 said:
Hi Mickey,
My original DHD was from Taiwan, the donor DHD was from China.
I think a survey would be a good idea, I mean if (and it's a big if) it's a design flaw with the Taiwanese devices then HTC might have to do a recall.
It will be interesting to see some results.
Click to expand...
Click to collapse
Ryt... I am going to try a make a survey.
Which of the threads do you think i should put the survey??
Dude,
if your gonna do a survey, I would post it in the general section, that seems the best one to me.
Sent from my Xperia S, made awesome by XDA.
Hi all,
I have a big problem
I think that my HTC Wildfire got hardbricked, My friend was trying to install custom rom but it went wrong
My wildfire doesnt turn on and my battery is working I tried my battery with a other wildfire so its not the battery..
Is there a way to unbrick my wildfire ??
Wildfire64 said:
Hi all,
I have a big problem
I think that my HTC Wildfire got hardbricked, My friend was trying to install custom rom but it went wrong
My wildfire doesnt turn on and my battery is working I tried my battery with a other wildfire so its not the battery..
Is there a way to unbrick my wildfire ??
Click to expand...
Click to collapse
OK let's figure this out. Gonna need specific information from you.
Is the phone s-on or s-off? If s-off how was this done?
What procedure was used to flash the ROM?
What state is the phone in now? Won't turn on at all, or sits on the HTC screen, or only vibrates?
And has your friend done this before?
Sent from my HTC Desire S using Tapatalk
heavy_metal_man said:
OK let's figure this out. Gonna need specific information from you.
Is the phone s-on or s-off? If s-off how was this done?
What procedure was used to flash the ROM?
What state is the phone in now? Won't turn on at all, or sits on the HTC screen, or only vibrates?
And has your friend done this before?
Sent from my HTC Desire S using Tapatalk
Click to expand...
Click to collapse
I think the phone was s-on
the phone doesnt turn on , no vibrate , no led by charging just nothing..
my friend has flashed many roms but this time it went wrong and he tryed to fix it but i think he hardbricked it now..
Wildfire64 said:
I think the phone was s-on
the phone doesnt turn on , no vibrate , no led by charging just nothing..
my friend has flashed many roms but this time it went wrong and he tryed to fix it but i think he hardbricked it now..
Click to expand...
Click to collapse
Hmmmm. If it was s-on then HTC safeguards would have prevented a hard brick. Is it possible the hardware has been damaged?
Sent from my HTC Desire S using Tapatalk
Try hard reset through youtube
Sent from my GT-S5570 using xda app-developers app
My advice is to flash an RUU and revert back to stock.
This is only because it's hard bricked, plus it happened to me before. I thought to give it a go, and it worked.
After that I just re root my phone, and install CWM recovery, and then flash a new ROM. It's simple
Just follow my leads and it'll work.
P.S Your hardware hasn't damaged at all. Why do users say these things?
1. Download an RUU from the buzz forums
2. Install and revert back to stock with RUU
3. After the process is done, enable adb in settings [Applications]
4. re root your device, and install CWM
5. Flash any custom ROM and follow the instructions 'fully'.
I had to rush this, I hope you understand what i'm saying.
Users if you think i'm wrong then correct me as you wish.
But this all managed to work for me, when my device was hard bricked xD
Stone. Cold said:
My advice is to flash an RUU and revert back to stock.
This is only because it's hard bricked, plus it happened to me before. I thought to give it a go, and it worked.
After that I just re root my phone, and install CWM recovery, and then flash a new ROM. It's simple
Just follow my leads and it'll work.
P.S Your hardware hasn't damaged at all. Why do users say these things?
1. Download an RUU from the buzz forums
2. Install and revert back to stock with RUU
3. After the process is done, enable adb in settings [Applications]
4. re root your device, and install CWM
5. Flash any custom ROM and follow the instructions 'fully'.
I had to rush this, I hope you understand what i'm saying.
Users if you think i'm wrong then correct me as you wish.
But this all managed to work for me, when my device was hard bricked xD
Click to expand...
Click to collapse
Hey @Stone Cold, the confusion people are having here is between hard bricked and soft bricked. A "hard brick" can only occur in 2 situations which are
1: the bootloader is corrupted/damaged/deleted and the device cannot boot. This can Only be fixed by using a JTAG. A ruu will not work as the ruu is flashed by the hboot(bootloader) and if it won't function then its dead.
2: that hardware has been damaged so much that the device cannot physically boot.
Depending on the damage this can sometimes be fixed.
All other forms of "bricking" are "soft bricks" or software bricks. These include bootlooping, trapped at the splash screen etc. These can be fixed as the bootloader and or custom recovery still function. If either of these still function you are not hard bricked. If a ruu worked then you were soft bricked.
Now this user states that his device was s-on so bootloader corruption is massively unlikely as nand protection is still active. This coupled with the owner stating that the device will not boot and shows no signs of life a hardware failure is the most likely option.
Sent from my HTC Desire S using Tapatalk
heavy_metal_man said:
Hey @Stone Cold, the confusion people are having here is between hard bricked and soft bricked. A "hard brick" can only occur in 2 situations which are
1: the bootloader is corrupted/damaged/deleted and the device cannot boot. This can Only be fixed by using a JTAG. A ruu will not work as the ruu is flashed by the hboot(bootloader) and if it won't function then its dead.
2: that hardware has been damaged so much that the device cannot physically boot.
Depending on the damage this can sometimes be fixed.
All other forms of "bricking" are "soft bricks" or software bricks. These include bootlooping, trapped at the splash screen etc. These can be fixed as the bootloader and or custom recovery still function. If either of these still function you are not hard bricked. If a ruu worked then you were soft bricked.
Now this user states that his device was s-on so bootloader corruption is massively unlikely as nand protection is still active. This coupled with the owner stating that the device will not boot and shows no signs of life a hardware failure is the most likely option.
Sent from my HTC Desire S using Tapatalk
Click to expand...
Click to collapse
Oh, so I was wrong.
Thought it was that way though, anyway thanks. This makes more sense now
Cheers
Stone. Cold said:
Oh, so I was wrong.
Thought it was that way though, anyway thanks. This makes more sense now
Cheers
Click to expand...
Click to collapse
That's no problem pal it's good to keep these terms clear, so many people have misinterpreted them in the past. That being said thank you for reminding me of the black screen hboot issue. It's been ages since I've heard of that happening. Its good to keep notes
But back on topic, OP do you or your friend have a working fastboot path? If so try to boot into hboot with volume down and power, wait 30 seconds then push power. Then on the PC issue the command
Fastboot devices
If nothing happens its toast :/
Sent from my HTC Desire S using Tapatalk