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!
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.
Got HOX done a factory restore then update to 4.0.4 now i cant get a signal on any network...So contacted HTC to get replaced on warranty then discovered after booking it for repair the IEMI number for the phone has come back as a demo phone which was released before the actual release date....
So is there anything i can do to get my signal back it comes and goes most of the time nothing.. Can i flash a radio or some kind of image to get this back....
CID is 11111111
S-ON
UNLOCKED BOOT LOADER (Came like this)
Really want to get this fixed as i need the phone.....
stu1979 said:
Got HOX done a factory restore then update to 4.0.4 now i cant get a signal on any network...So contacted HTC to get replaced on warranty then discovered after booking it for repair the IEMI number for the phone has come back as a demo phone which was released before the actual release date....
So is there anything i can do to get my signal back it comes and goes most of the time nothing.. Can i flash a radio or some kind of image to get this back....
CID is 11111111
S-ON
UNLOCKED BOOT LOADER (Came like this)
Really want to get this fixed as i need the phone.....
Click to expand...
Click to collapse
Just contact HTC and tell them to ship you another phone.
but you do have SUPER CID...so lucky in some ways.
and since u do get signals sometime, maybe its a radio issue, try flashing a rom and radio. Should be easy since ur bootloader is unlocked already.
Just flash cwm recovery, the boot.img of a rom, and the rom itself. I recommend VIPERX.
hmilyyf said:
Just contact HTC and tell them to ship you another phone.
but you do have SUPER CID...so lucky in some ways.
and since u do get signals sometime, maybe its a radio issue, try flashing a rom and radio. Should be easy since ur bootloader is unlocked already.
Just flash cwm recovery, the boot.img of a rom, and the rom itself. I recommend VIPERX.
Click to expand...
Click to collapse
Done as above but with still no luck HTC said : As this this a demo handset it does have a warranty and you have to pay to have it repaired ???
stu1979 said:
done as above but with still no luck htc said : As this this a demo handset it does have a warranty and you have to pay to have it repaired ???
Click to expand...
Click to collapse
all done took casing of cleaned all contact points and all working again
IF I have unlocked bootloader, will RIFF BOX flash phone or I must relock it?
Why do u want to use the riff box
Sent from my Desire HD using xda premium
I thought you used riff boxes in unbricking
Sent from my Desire HD using xda premium
I will get DHD for a few days which stuck on HTC logo.
CWM showing errors cant opet/mount E:\... I was unable to flash boot, hboot, recovery (flash malfunction error) and gave phone on service...
Seller told after 35 days that phone is not fixed because it have unlocked bootloader but I thing that he lies to me and he do not know how to fix it.
He told me that he sent it on another service to flash it with RIFF BOX but I don't believe him for some reasons (that service don't have RIFF BOX)...
Now he will return me my DHD on Wed and I can try to relock bootloader and try flash official RUU (I didn't know that RUU won't flash if bootloader is not relocked/locked).
If I don't have luck, I will sent it to another sevice which will try to reflash it with RIFF BOX
It is just 6 monts old phone and it stopped to work before one month I get several FCs, reboot, and stuck at HTC logo...
Bricked or not, I don't know...
mikronac.ns said:
I will get DHD for a few days which stuck on HTC logo.
CWM showing errors cant opet/mount E:\... I was unable to flash boot, hboot, recovery (flash malfunction error) and gave phone on service...
Seller told after 35 days that phone is not fixed because it have unlocked bootloader but I thing that he lies to me and he do not know how to fix it.
He told me that he sent it on another service to flash it with RIFF BOX but I don't believe him for some reasons (that service don't have RIFF BOX)...
Now he will return me my DHD on Wed and I can try to relock bootloader and try flash official RUU (I didn't know that RUU won't flash if bootloader is not relocked/locked).
If I don't have luck, I will sent it to another sevice which will try to reflash it with RIFF BOX
It is just 6 monts old phone and it stopped to work before one month I get several FCs, reboot, and stuck at HTC logo...
Bricked or not, I don't know...
Click to expand...
Click to collapse
if u can boot into bootloader thn ur phone is not bricked u hv messed it up..
before u use the riff box did u try the RUU the PD98IMG.zip way?????
adilrenzu said:
if u can boot into bootloader thn ur phone is not bricked u hv messed it up..
before u use the riff box did u try the RUU the PD98IMG.zip way?????
Click to expand...
Click to collapse
Yes, I did, but when finish scaning PD98IMG.zip it skips flashing, it won't to continue.
But I didn't relock bootloader... Today or tommorow I will try to relock boot loader and try to flash with PD98IMG.zip.
mikronac.ns said:
Yes, I did, but when finish scaning PD98IMG.zip it skips flashing, it won't to continue.
But I didn't relock bootloader... Today or tommorow I will try to relock boot loader and try to flash with PD98IMG.zip.
Click to expand...
Click to collapse
Did you ever get that device un-bricked ?
No eMMC fried...
I bought One S...
Sent from my HTC One S
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