Hi all, had a search but nothing seems like my case, I'm writing because I think I've seriously bricked the phone.
Rom:LeeDrOiD HD V3.3.3-Port-R5
S-Off
Stock Hboot
Flashed a new radio, rebooted and nothing showed up for a long time, tried (stupid idea i know) to remove the battery then BAM! Phone dead, any button combination won't work, so no I don't have fastboot, and it doesen't even light up the led if connected it to the wall charger, also the pc doesen't see it.
It's better to bring it to HTC ? Could it be fixed by them ?
Many thanks
Regards
Emilio
I'll try to remove the battery for some hours, and also will try with another battery
Any suggestions?
I think you know the answer to this.. Never take out the battery when flashing radios, the radio gets properly flashed upon first boot. If its corrupted, its bricked. Did you check md5? Can you? Can you get into bootloader? Or connect fast boot? if you can't get into fast boot, its back to htc. How did you flash? Recovery? pb99img our fast boot is the best.
When you flash a new radio, the hardware gets updated. If there something goes wrong, you desire is completely hard-bricked (and so nothing more than an expensive paperweight). And I am pretty sure, even HTC cannot fix a radio damage. Even if they can, they won't do it because you lost your warranty.
MatDrOiD said:
When you flash a new radio, the hardware gets updated. If there something goes wrong, you desire is completely hard-bricked (and so nothing more than an expensive paperweight). And I am pretty sure, even HTC cannot fix a radio damage. Even if they can, they won't do it because you lost your warranty.
Click to expand...
Click to collapse
Well..im not completely sure..if u are still in warranty period, you can try say they that you was applying an ota (for example one about the froyo update) and it failed..the ota also contain radio updates sometimes..and as the phone is bricked they can't know if he is s-off etc..
andQlimax said:
Well..im not completely sure..if u are still in warranty period, you can try say they that you was applying an ota (for example one about the froyo update) and it failed..the ota also contain radio updates sometimes..and as the phone is bricked they can't know if he is s-off etc..
Click to expand...
Click to collapse
good plan, id go with this.
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!
Hi folks,
i´ve a problem with a Desire Z from a friend.
Every time when the phone boots, it stops at the HTC Logo.
I think it´s bricked
Is there any possible to flash the Rom (like Odin on Samsung Android Phones)
Thanks
If you power the phone off, then holding down the volume button, press the power button. Does the Hboot screen come up?
Also, you don't give a heck of a lot of info. Is the phone rooted, and/or S-Off? If not, then no, you can't flash a custom ROM.
But you may be able to flash the official ROM from Hboot.
the H Boot screen is this with "bootloader, reboot" and something with the 3 androids ?
when its that, i come into the hboot screen .. i did try the "factory reset" but it hangs on the 3 androids at the middle of the screen
EDIT: The Phone is not rooted, S-on stands there
but how can i flash a official ROM ?
i found one, but it recognize the phone
Since you are not rooted and S-On, you need to use the official ROM that matches your carrier ID (CID).
What ROM did you try?
If you want help, you need to supply as much information as possible. Not just "I tried a ROM".
Seeing as the phone is unrooted, it's unlikely that it's bricked from a user error.
At a guess, it's a Hardware issue, there's a thread here about it.
I had this same issue with my phone, it started freezing completely, and I had to do a battery pull to restart and it would just hang at the htc logo.
Seeing as you don't have clockwork mod though, you won't be able to see the Cache mounting errors, though you should be able to run the adb commands to find the name of your eMMC card if you have adb installed.
-Nipqer
redpoint73 said:
Since you are not rooted and S-On, you need to use the official ROM that matches your carrier ID (CID).
What ROM did you try?
If you want help, you need to supply as much information as possible. Not just "I tried a ROM".
Click to expand...
Click to collapse
okay, it´s a free phone without branding.
where can i read the CID !?
Nipqer said:
Seeing as the phone is unrooted, it's unlikely that it's bricked from a user error.
At a guess, it's a Hardware issue, there's a thread here about it.
I had this same issue with my phone, it started freezing completely, and I had to do a battery pull to restart and it would just hang at the htc logo.
Seeing as you don't have clockwork mod though, you won't be able to see the Cache mounting errors, though you should be able to run the adb commands to find the name of your eMMC card if you have adb installed.
-Nipqer
Click to expand...
Click to collapse
Where can i get adb mode ? the hboot or at the HTC LOGO !?
I have this problem too but i rooted and s-offed. What should i do now. Same things as him.
Nipqer said:
At a guess, it's a Hardware issue, there's a thread here about it.
Click to expand...
Click to collapse
Its possible, but also highly speculative. Damage to the ROM, or the ROM missing may also cause the same issue (stuck on boot splash).
bboy2000 said:
I have this problem too but i rooted and s-offed. What should i do now. Same things as him.
Click to expand...
Click to collapse
You're in (possibly) better shape then the OP. Try flashing any known good ROM from Hboot/recovery. Preferably a rooted ROM, if you want to stay rooted.
But its possible you may have something more going on than a bad ROM file, like mentioned in post #5 above.
i couldn´t find a tutorial how to flash the desire Z im H-Boot mode ?
can u give me a tutorial !?
Hi,
I had made a major mistake for being impatient. I tried to flash this radio: 32.56.00.32U_5.17.05.08 because im trying to use Leedroid HD V3.3.3 for the first time and it recommended that radio. I flashed the radio via recovery and it rebooted into a blank screen. From what i read from forums, it is supposed to reboot into a screen with an arrow to process the radio update and since that did not happen, i waited for a minute or two and popped out the battery.
Now what i got is vibrations 7 times and a blank screen every time i want to power on my phone. I tried every key combination; Vol- & Power, Back & Power, but it still gives me the the 7 times vibrations. ADB and Fastboot does not work via PC, does not detect phone at all.
I tried to do a blind flash using PB99IMG.ZIP method guided by youtube video but im not quite sure if it the bootloader actually loaded or not since it vibrates 7 times on everything i tried, but so far no success.
If the answer to my problem is my phone is bricked and nothing can be done, then i have a few questions:
1- I am still under warranty, but my phone is currently S-OFF by AlphaRev and using custom ROM (Leedroid HD).
What are the chances that the engineers over the customer service center can actually restore my radio via some techniques that i don't know of and found out that i actually S-OFF my phone and using custom ROM? because if they found out, my warranty will be void.
2- Is there any other method that can only used by official engineers to restore bricked phones? Methods using special hardware tools that are not made available to the public?
Hope somebody can help me soon.
Congrats! You have succesfully bricked your phone.
You should never pull out the battery when messing with radios... But its kinda late now...
...aes eht rednu
peed morf tneS
But in bricked state, does the engineer/technician for the official service center can do anything about it? Or atleast check if I S-OFF and use custom rom to invalidate my warranty?
tablighs said:
But in bricked state, does the engineer/technician for the official service center can do anything about it? Or atleast check if I S-OFF and use custom rom to invalidate my warranty?
Click to expand...
Click to collapse
Thats a bit difficult... Because radio is the essential part that communicates between the os and the hardware. When that is messed up, your phone is obviously dead, cause the hardware its self doesnt know what to do....In such occasions it might be difficult even for htc to revive it... But you could risk it and say to htc that you were applying an ota update when that happened. Dont mention that you pulled the battery and you might be lucky... But no word for root/s-off/custom rom
...aes eht rednu
peed morf tneS
Okay thanks!
Im sending it to htc in around 2 weeks time (currently in overseas). Hope the repair guy is lazy to try much and just give me a new phone , wish me luck!
Hi, Did you send your phone to HTC? I have the same problem, the phone is s-off but it does not boot so im unsure if HTC will notice this.
Thanks
A simple JTAG session would easily restore it.
Hi guys,
Since a few days my touchscreen is not working properly anymore. It automatically presses certain points on the screen, without me even touching the phone. This means I can't even type a whatsapp message propertly without my phone randomly typing gibberisch.Sometimes, when I haven't touched the phone for a while, it works perfectly well.. And then after some usage the touchscreen starts acting on its own again. I also think the issues happen on the lowest 1cm of the screen (where your quickbar is with the icons of dialing etc). That part is unresponsive most of the times.
I tried several solutions (other rom, other kernel etc.) that didn't work. Since this morning, I upgraded my hboot to 1.39 (release keys 3.20.401.3) and the problem still persists. Even in my recovery (Philz recovery 5.0.5) the touchscreen automatically presses certain points on the screen.
Any of you guys have any idea on how to fix this? I am clueless right now .
Phone details:
International HTC One X
Hboot 1.39
Software: 3.20.401.3
CID: HTC__E11
Baseband: 5.1204.162A.29
If it ain't a software problem, it's gonna to the hardware that's at fault here!
I would suggest to get your phone back to full stock and then send it to HTC under warranty...!
vin4yak said:
If it ain't a software problem, it's gonna to the hardware that's at fault here!
I would suggest to get your phone back to full stock and then send it to HTC under warranty...!
Click to expand...
Click to collapse
Will they accept it? Since I totally rooted it . And which RUU should I use to go back to stock?
Is it a hardware related issue then? Ive read many posts of people complaining about the touchscreen.. That would be a coincidence, wouldnt it?
EDIT: Sometimes, when I haven't touched the phone for a while, it works perfectly well.. And then after some usage the touchscreen starts acting on its own again.. Maybe that might change your view a bit
EvertorN said:
Will they accept it? Since I totally rooted it . And which RUU should I use to go back to stock?
Is it a hardware related issue then? Ive read many posts of people complaining about the touchscreen.. That would be a coincidence, wouldnt it?
EDIT: Sometimes, when I haven't touched the phone for a while, it works perfectly well.. And then after some usage the touchscreen starts acting on its own again.. Maybe that might change your view a bit
Click to expand...
Click to collapse
Post the result of fastboot getvar version-main
We will find a suitable RUU or nandroid backup for your device...
All I can say is: If you have the latest JB Hboot, all roms should work fine. and you've also tried flashing multi roms... Can't be that all roms have the same problem... So it's gotta be hardware related...
Now you can try one last time... Fully wipe (data/cache/dalvic/format system) the device in recovery... flash the boot.img via fastboot and then flash the rom via recovery and see if it fixes it...
if everything else fails... Return to stock (rom+ recovery), lock your bootloader and send it for warranty!
EvertorN said:
Will they accept it? Since I totally rooted it . And which RUU should I use to go back to stock?
Is it a hardware related issue then? Ive read many posts of people complaining about the touchscreen.. That would be a coincidence, wouldnt it?
EDIT: Sometimes, when I haven't touched the phone for a while, it works perfectly well.. And then after some usage the touchscreen starts acting on its own again.. Maybe that might change your view a bit
Click to expand...
Click to collapse
Not coincidence but a design issue. I'm currently having trouble with the touch buttons. The symptoms are similar to yours in that it's an intermittent problem. I'm sure it's a hardware fault, I was just hoping it was a loose cable or something inside that I could fix myself. But having fiddled with all the cables already and not had any improvement I've pretty much conceded that this isn't going to be the case.
Sent from my HTC One X using xda app-developers app
vin4yak said:
Post the result of fastboot getvar version-main
We will find a suitable RUU or nandroid backup for your device...
All I can say is: If you have the latest JB Hboot, all roms should work fine. and you've also tried flashing multi roms... Can't be that all roms have the same problem... So it's gotta be hardware related...
Now you can try one last time... Fully wipe (data/cache/dalvic/format system) the device in recovery... flash the boot.img via fastboot and then flash the rom via recovery and see if it fixes it...
if everything else fails... Return to stock (rom+ recovery), lock your bootloader and send it for warranty!
Click to expand...
Click to collapse
Just ran the fastboot command, it returned version-main: 3.20.401.3.
Pff, I think I'm kinda done with HTC and their crappy designs . This is the second HTC phone I'm having issues with. Guess my next phone will be a Samsung.. I guess I can live with TouchWiz over Sense, though I think Sense is a lot better..
EvertorN said:
Just ran the fastboot command, it returned version-main: 3.20.401.3.
Pff, I think I'm kinda done with HTC and their crappy designs . This is the second HTC phone I'm having issues with. Guess my next phone will be a Samsung.. I guess I can live with TouchWiz over Sense, though I think Sense is a lot better..
Click to expand...
Click to collapse
Well you just unlucky m8! I'm sure once you've used HTC phones, you wouldn't find sammy's plastic finish phones attractive
ahh so your on the latest base is it? (3.20.401.3)... No RUU for your device, you will need to restore a nandroid backup.. However, no nandroid backup is available for that base but 3.20.401.1 backup would surely work afaik! So if you tell your device's cid, fastboot oem readcid I would give the correct backup for your region as well...
vin4yak said:
Well you just unlucky m8! I'm sure once you've used HTC phones, you wouldn't find sammy's plastic finish phones attractive
ahh so your on the latest base is it? (3.20.401.3)... No RUU for your device, you will need to restore a nandroid backup.. However, no nandroid backup is available for that base but 3.20.401.1 backup would surely work afaik! So if you tell your device's cid, fastboot oem readcid I would give the correct backup for your region as well...
Click to expand...
Click to collapse
Yep I tried every possible update to fix the issues , so Im on the latest base.
My CID is HTC__E11, as stated in OP
So once I restored that nandroid and relocked my phone, it will be ready to be send to HTC?
EvertorN said:
Yep I tried every possible update to fix the issues , so Im on the latest base.
My CID is HTC__E11, as stated in OP
So once I restored that nandroid and relocked my phone, it will be ready to be send to HTC?
Click to expand...
Click to collapse
Sorry didn't read it! here's the backup : https://mega.co.nz/#!tsYj0DSK!T65wiGBygge4w-AOwEjxvUcZ2ytvdxhj2EKXgOT7Oao
Yes... flash boot.img.. wipe everything in recovery and then restore the backup... After that flash this stock recovery : https://www.dropbox.com/s/xzshnnuz3jdcodv/stock recovery 3.14.img and then finally lock the bootloader!
It will be full stock (rom + recovery) with locked bootloader... Yes, you can send it to HTC after doing these things but there's always the chance of warranty getting void because of the **Relocked** bootloader... But worth a try! Besides, there's nothing you can do...
vin4yak said:
Sorry didn't read it! here's the backup : https://mega.co.nz/#!tsYj0DSK!T65wiGBygge4w-AOwEjxvUcZ2ytvdxhj2EKXgOT7Oao
Yes... flash boot.img.. wipe everything in recovery and then restore the backup... After that flash this stock recovery : https://www.dropbox.com/s/xzshnnuz3jdcodv/stock recovery 3.14.img and then finally lock the bootloader!
It will be full stock (rom + recovery) with locked bootloader... Yes, you can send it to HTC after doing these things but there's always the chance of warranty getting void because of the **Relocked** bootloader... But worth a try! Besides, there's nothing you can do...
Click to expand...
Click to collapse
Thanks a lot mate.. Seems my phone has less frequent issues atm. So I'll try if I can manage with it. If not, I'll go back to stock, see if the problem still persists and then send it back to HTC..
Hmmm ohkk ! Do keep us posted! :good:
Alright it has been a few days since I created this post.. Phone seems to have stabilized a bit. Yesterday I experienced the weird behavior 1 time and today I didn't experience it at all. However, I think I might have found some kind of pattern in the strange behavior. Whenever I have had my phone with me in my pocket for a while, the problems seem to start. Also when my phone is in my car holder, so basically any vertical position. When my phone is on my desk all day, I don't have any problems at all...
So yea.. Most likely a hardware related issue..
I was also fond of HTC and their phones, but with the One X, they kind of ruined my positive view.. I totally love Sense, but the build quality of the One X is far, far below my expectations. For my next phone, I am seriously considering changing to Samsung, depending on the issues with the HTC One (since my contract ends next year, I will probably get a next generation phone)..
What's is your opinion on HTC nowadays?
Hi
I don't think it's the hardware problem, because TOO MANY people have this problem. So do I. I already did post this issue before http://forum.xda-developers.com/showthread.php?p=41820803 (see the video what my phone does) but all I got was "return it to HTC"
After I did dig a little I found some posts where people say I should downgrade the touch panel firmware - http://forum.xda-developers.com/showthread.php?t=2159863
I can't do S-OFF I always get stuck at error 99 no matter what I do.. maybe you should try downgrading the touch panel and see if that fixes the problem.. do please let me know.. thanks..
another guy I messaged wrote to me I should try ViperXL ROM, he also could not get his phone to S-OFF:
"ViperXL rom is based on telus HTC one x, (HOX evita), which works fine on all US and Canadian hox phones. It has all the firmware and everything else required including sense, so it will work on your phone. I was in the worst situation as there was no OS on my phone and I could not find the original OTA, but this rom worked like a charm. Give it a shot."
so I think I'm gonna try the ViperXL..and see..
EvertorN said:
Alright it has been a few days since I created this post.. Phone seems to have stabilized a bit. Yesterday I experienced the weird behavior 1 time and today I didn't experience it at all. However, I think I might have found some kind of pattern in the strange behavior. Whenever I have had my phone with me in my pocket for a while, the problems seem to start. Also when my phone is in my car holder, so basically any vertical position. When my phone is on my desk all day, I don't have any problems at all...
So yea.. Most likely a hardware related issue..
I was also fond of HTC and their phones, but with the One X, they kind of ruined my positive view.. I totally love Sense, but the build quality of the One X is far, far below my expectations. For my next phone, I am seriously considering changing to Samsung, depending on the issues with the HTC One (since my contract ends next year, I will probably get a next generation phone)..
What's is your opinion on HTC nowadays?
Click to expand...
Click to collapse
An Evita rom won't work on a tegra device. Nor downgrading the touchpanel without s-off
so no luck again.. thanks
xichtiq said:
so no luck again.. thanks
Click to expand...
Click to collapse
I can't watch your video.. it's private .. I still think this is a hardware related problem, as it happened to me in recovery as well. The reason many people experience this issue, is because of the crappy design by HTC I guess.
vin4yak said:
Sorry didn't read it! here's the backup : https://mega.co.nz/#!tsYj0DSK!T65wiGBygge4w-AOwEjxvUcZ2ytvdxhj2EKXgOT7Oao
Yes... flash boot.img.. wipe everything in recovery and then restore the backup... After that flash this stock recovery : https://www.dropbox.com/s/xzshnnuz3jdcodv/stock recovery 3.14.img and then finally lock the bootloader!
It will be full stock (rom + recovery) with locked bootloader... Yes, you can send it to HTC after doing these things but there's always the chance of warranty getting void because of the **Relocked** bootloader... But worth a try! Besides, there's nothing you can do...
Click to expand...
Click to collapse
I did this earlier tonight and it looks like the touchscreen issues are gone! . I'll report back in a day or so to notify whether the issues are permanently solved, but looking good so far!.
What could possibly the cause of this issue? Touchscreen driver in the kernel? If we find a solution, maybe rom developers can add it to their roms, so people with similar issues and I can start using custom roms again
EDIT: Problems started again today . Seems like I have to send it to HTC...
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