Related
Hey Guys,
Got the phone bricked issue when I installed CM9 AOSP (formatting memory card issue)
I'm thinking of sending it back to HTC for an RMA. Will they repair or not? considering everything on the internal of the phone has been wiped due to this?
I've been so lucky as to never had to RMA anything before so any advice would be great.
Thank you.
I believe it is possible to unbrick it yourself,
http://forum.xda-developers.com/showthread.php?t=1522351
I don't think they'll do it, once you Root your phone, your warranty will be voided. You have to unroot it and change back to stock.
That method unfortunately does not work for AOSP sd card format bricks. Otherwise I would have done it myself.
bump
It's properly dead. They should no way of knowing you caused it.
It will be rmaed fine. Just say an update bricked it
Sent from my HTC Sensation using xda premium
Lovely lads. Cheers!
I just said during the ICS OTA update the thing went all black and wouldnt come back on lol
I had sudden unresponsive Sensation that apparently has been fixed / replaced by HTC. I still don't know if this is a hardware or software problem since there seem to be many incidents of these happening on the forum.
In any case, just want some advice...do we think these "unresponsive" issue is related to rooting/ROM...even though it seems to be happening with various ROM. I just wonder if I should try to reroot the repaired phone again.
Also, will the guide for rooting be still valid with maybe some newer firmware/Bootloader that HTC might have reinstalled onto the phone now? I am picking it up today...but I need to unlock the phone to use in Canada..which I did with the guide here before....but I am a little weary about doing it again after what happened!
newr said:
I had sudden unresponsive Sensation that apparently has been fixed / replaced by HTC. I still don't know if this is a hardware or software problem since there seem to be many incidents of these happening on the forum.
In any case, just want some advice...do we think these "unresponsive" issue is related to rooting/ROM...even though it seems to be happening with various ROM. I just wonder if I should try to reroot the repaired phone again.
Also, will the guide for rooting be still valid with maybe some newer firmware/Bootloader that HTC might have reinstalled onto the phone now? I am picking it up today...but I need to unlock the phone to use in Canada..which I did with the guide here before....but I am a little weary about doing it again after what happened!
Click to expand...
Click to collapse
Maybe it was the rom or some certain thing that you did causing the slow response. Rooting will never ever ever ever lag a phone, custom rims on the other hand usually don't but there's the new ones which still have work to be done. When you get your phone back, boot into bootloader and tell me the hboot version. If its ics I don't think that you can as I think juopuntbear only works on pre rooted phones.
It does seem like the phone itself had some problems.
Sent from my HTC Sensation Z710e using XDA
sensation lover said:
Maybe it was the rom or some certain thing that you did causing the slow response. Rooting will never ever ever ever lag a phone, custom rims on the other hand usually don't but there's the new ones which still have work to be done. When you get your phone back, boot into bootloader and tell me the hboot version. If its ics I don't think that you can as I think juopuntbear only works on pre rooted phones.
It does seem like the phone itself had some problems.
Sent from my HTC Sensation Z710e using XDA
Click to expand...
Click to collapse
Well.. the phone came back as HBOOT 1.18...I had to go through the rooting process as I needed to unlock the SIM. So my phone is S-off, rooted, clockwork 5.0.2.0, and super CID.
I am scared to try to install an ICS custom ROM on it now as I am not sure if that process caused the phone to die and there are many phones dying on here running that.
I am thinking maybe I should just update to the official update when it comes out. Hope it's possible with the phone being rooted and S-off etc..
newr said:
Well.. the phone came back as HBOOT 1.18...I had to go through the rooting process as I needed to unlock the SIM. So my phone is S-off, rooted, clockwork 5.0.2.0, and super CID.
I am scared to try to install an ICS custom ROM on it now as I am not sure if that process caused the phone to die and there are many phones dying on here running that.
I am thinking maybe I should just update to the official update when it comes out. Hope it's possible with the phone being rooted and S-off etc..
Click to expand...
Click to collapse
Ok, just tell what happened, what rom you flashed and how, I'll be able to tell you how to do it properly
Sent from my Sensation using XDA
I did a bad, bad thing. I thought I understood the process much better than I actually did and quickly found myself in over my head. Now I'm worried that I have a permanently bricked, very expensive paperweight on my hands. Is there any hope for recovering my Sensation?
My goal was to install CM9.
These are the steps that led to this problem:
Did the HTC Dev Unlock through the HTC website.
I used the KGS Utility v6.6 to root the device. The script told me it was successful, but I opened a terminal on the phone and couldn't tell if I had root priveleges.
Tried Juopunutbear to S-Off, but the script said it couldn't find device. “Connect Device and Install Drivers.”
Stupidly following directions I found online, I used the One X All In One Kit v1.0. I thought this was specifically for the Sensation at the time. I hit the button to flash the kernal and that's where my troubles begin. Couldn't get past HTC loading screen.
Power Button + Down volume to get into boot loader, instead. “Recovery” and “Factory Setting” in Fastboot wouldn't load anything at all.
Tried using Fastboot in a command line. I attempted to install a recovery image, but it wouldn't take. The bootloader was in “relocked” mode.
An online thread I found said that you can't flash a recovery unless your bootloader is unlocked. I took the advice in that thread and told Fastboot to use the Unlock_code.bin file once again. The phone said it was about to unlock. Then it completely shut off.
The phone will not turn on, and I can't even get it to boot into recovery mode.
Is there any hope for me? Thanks in advance for your help.
(HTC Sensation 4G, T-Mobile, US, Was Running Stock ICS)
S-Off, Was trying to get S-On.
Thats a brick all right. You can always try the unbricking method by dexter in the dev section but for this specific case, dont get your hopes up because I dont think it will work but its worth a try.
If it doesnt work the only way to unbrick is to find someone who can JTAG it
Jonny said:
Thats a brick all right. You can always try the unbricking method by dexter in the dev section but for this specific case, dont get your hopes up because I dont think it will work but its worth a try.
If it doesnt work the only way to unbrick is to find someone who can JTAG it
Click to expand...
Click to collapse
Thank you.
That's unfortunate, but I didn't even know about JTAG until today. It's good to know at least that there is a silver lining. I was worried that there were no possible solutions to get it back up and running.
Sad Sensation said:
Thank you.
That's unfortunate, but I didn't even know about JTAG until today. It's good to know at least that there is a silver lining. I was worried that there were no possible solutions to get it back up and running.
Click to expand...
Click to collapse
One thing I will say about JTAG is dont do it yourself, it is too easy to get it wrong and besides the jtag box costs a lot of money so its cheaper to send it to someone who does it for buisness than to buy the hardware
Wow now thats crazy
Sent from my HTC Sensation 4G using xda premium
---------- Post added at 08:06 PM ---------- Previous post was at 07:55 PM ----------
Can atleast boot in to boot loader
Sent from my HTC Sensation 4G using xda premium
First and foremost, contact HTC. They don't check bricked devices.
Also, it doesn't matter if you bought the phone used because the warranty is traced by the serial number of the device.
Contact them & say that the phone randomly switched off & never came back on.
If they find the device to be in warranty, which is most likely, then they will replace the mobo on the phone.
You shouldn't have any hardware modified on the phone & all the warranty stickers should be present.
Try using dexters HTC sensation unbrick tool, if that doesn't work then try looking for a jtagging service. If your from the UK then try fonefunshop.com
Sent from my Sensation XE with Beats Audio Z715e using xda app-developers app
kgs1992 said:
First and foremost, contact HTC. They don't check bricked devices.
Also, it doesn't matter if you bought the phone used because the warranty is traced by the serial number of the device.
Contact them & say that the phone randomly switched off & never came back on.
If they find the device to be in warranty, which is most likely, then they will replace the mobo on the phone.
You shouldn't have any hardware modified on the phone & all the warranty stickers should be present.
Click to expand...
Click to collapse
I used the HTC Dev Unlock tool through their website. I was under the impression that doing that voids your warranty? Does anyone happen to know?
Also, a question about JTAG-ing the phone. Does that process also restore the operating system or just get you into Hboot? Just curious if I'll end up with a fully functional phone through a JTAG service (in case HTC can't help).
Sad Sensation said:
I used the HTC Dev Unlock tool through their website. I was under the impression that doing that voids your warranty? Does anyone happen to know?
Also, a question about JTAG-ing the phone. Does that process also restore the operating system or just get you into Hboot? Just curious if I'll end up with a fully functional phone through a JTAG service (in case HTC can't help).
Click to expand...
Click to collapse
I don't think you will have problems.. With htc-dev unlock... As it said it may void the warranty but not it Will void the warranty.. Also your issue seems like hardware side.. So hardware issues will not be voided even if you do htc-dev unlock afaik
Sent from my HTC Sensation 4G using xda premium
Sad Sensation said:
I used the HTC Dev Unlock tool through their website. I was under the impression that doing that voids your warranty? Does anyone happen to know?
Also, a question about JTAG-ing the phone. Does that process also restore the operating system or just get you into Hboot? Just curious if I'll end up with a fully functional phone through a JTAG service (in case HTC can't help).
Click to expand...
Click to collapse
JTAG forces the correct files onto the partitions of your phone however it wont do it for boot, system or data partitions because that would make the resurector dll enormous to download, as it is the resurecter is already over 15mb.
After JTAG then I would suggest flash an RUU or custom ROM immediately because after JTAG phone boots but is unstable.
source, riffbox site and my own experiance
Jonny said:
After JTAG then I would suggest flash an RUU or custom ROM immediately because after JTAG phone boots but is unstable.
Click to expand...
Click to collapse
Not sure if anyone would know this, but do JTAG services (such as mobiletechvideos.com) typically do that for you?
And again, just want to say thanks for everyone's comments so far. I truly appreciate all of the help.
Sad Sensation said:
Not sure if anyone would know this, but do JTAG services (such as mobiletechvideos.com) typically do that for you?
And again, just want to say thanks for everyone's comments so far. I truly appreciate all of the help.
Click to expand...
Click to collapse
Doubt it but dont know for certain
Have you tried flashing a kernel or original software through a PG58IMG.zip?
Sent from my HTC Sensation 4G using xda premium
How can he thought that toolkit for One X is specifically for Sensation is beyond me.
Odoslané z HTC Sensation XE with Beats Audio Z715e cez Tapatalk 2
JTAG will not solve any hardware faults & this seems like a hardware fault. Remember, once you try JTAG, warranty is void even if you had it before.
Talk to HTC support first. They will not check anything at all on the phone. If you don't try, it's your loss.
There's no need to mention anything about what happened. Just say it happened randomly.
kgs1992 said:
JTAG will not solve any hardware faults & this seems like a hardware fault. Remember, once you try JTAG, warranty is void even if you had it before.
Talk to HTC support first. They will not check anything at all on the phone. If you don't try, it's your loss.
There's no need to mention anything about what happened. Just say it happened randomly.
Click to expand...
Click to collapse
sorry but I disagree, he flashed something meant for One X which seems to have messed the partitions up so its not a hardware issue therefore JTAG should fix it. Ofcouse he could always try contacting HTC aswell...
i would send it to htc first before i do anything , if you are still in waranty, sorry this happened to you better read and concentration needed when doing this sort of things but than again it happens....
Jonny said:
sorry but I disagree, he flashed something meant for One X which seems to have messed the partitions up so its not a hardware issue therefore JTAG should fix it. Ofcouse he could always try contacting HTC aswell...
Click to expand...
Click to collapse
The phone bricked after flashing the unlock token. The one x kernel has nothing to do with it.
Sent from my HTC Sensation XE with beats audio
kgs1992 said:
The phone bricked after flashing the unlock token. The one x kernel has nothing to do with it.
Sent from my HTC Sensation XE with beats audio
Click to expand...
Click to collapse
Yes but the unlock token is still software, not hardware and from what I can gather the One X kernel thing is flashed to a different partition on the eMMC chip than a sensation kernel so this looks to me (I could be wrong if course) that a kernel was flashed to a partition containing other data which resulted in that data being erased/overwritten
Jonny said:
JTAG forces the correct files onto the partitions of your phone however it wont do it for boot, system or data partitions because that would make the resurector dll enormous to download, as it is the resurecter is already over 15mb.
After JTAG then I would suggest flash an RUU or custom ROM immediately because after JTAG phone boots but is unstable.
source, riffbox site and my own experiance
Click to expand...
Click to collapse
OK. I have this JTag Device. Link. I know it jumps samsung phones into download mode. Does it work for any other manufacturer? What about HTC?
My phone basically took a dump a couple weeks ago. It was stock and unrooted and got stuck in a boot loop. Everthing I have tried including installing custom roms and installing a ruu has been unable to fix the problem. Phone will not boot into a recovery or preform a factory reset, the only option from the bootloader that works is fastboot. The fact I unlocked the boatloader trying to fix the problem means htc won't cover it under warranty.
My problem appears to be software related but any software fix I try has no effect so I'm thinking it's more related to a hardware fault stopping it from booting.
I'm wondering how much of the phone is included in the motherboard? I'm assuming the. CPU, ram and storage is built into the motherboard? If I was to buy a cheap banged up functional one s from eBay with a broken screen or whatnot would changing the motherboard be the ultimate repair?
My phone is only a month old and is in mint condition other then the booting problem. I'm kind of hesitant to give up on it and just buy a new phone as I'd hate to have such an expensive paper weight. If I can fix it for a decent amount I'd prefer to do that...
Only a month old? Does it not have a warranty?
Sent from my HTC VLE_U using xda app-developers app
Is it water damaged? If yes, htc won't fix it under warranty
--------------
If you are new to xda please watch this video it'll help you out )
https://www.youtube.com/watch?v=JmvCpR45LKA&feature=youtube_gdata_player
Have you tried a factory reset in HBOOT?
I think the camera is also on the motherboard, not sure though
Sent from my HTC One S using Tapatalk 2
Did u try to relock bootloader then use RUU? Coz unlocked bootloader will ignore the RUU.
Good luck!
Sent from my HTC One S using xda premium
ReichMann said:
Did u try to relock bootloader then use RUU? Coz unlocked bootloader will ignore the RUU.
Good luck!
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
Since when?
Sent from my HTC One S using Tapatalk 2
Htc won't cover it because the bootloader was unlocked.
Yes I've tried a ruu and it installs fine but doesn't fix the problem. I ended up selling it for parts and my new one s is in the mail. I found a bnib one s for $250 so it's not a huge loss. The original phone I bought new off Craigslist minus the price I got for selling my broken one for parts and then adding the new phone I'm still below the retail price so I guess I'm technically coming out on too. Here's hoping this one doesn't take a dump...
Just to let you know a lot of people are buyine the 1s new with a "relocked" bootloader so if you can get everything back to stock with a relocked relocked bootloader you shouldn't have trouble. Don't ask me why some ship new with a relocked bootloader but I've read it in a few places and its a mystery to me.
Ladies and Gents,
I made sure I chose the correct RUU based on my CID (CWS__001)
I relocked my phone and attempted to install "RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_ 0.24p.32.09.06_10.130.32.34_release_signed.exe". After the RUU finished my phone seems to be hard bricked.
Won't Boot.
No power lights.
I knew this could happen when flashing an international version. AFTER getting owned I also found this post http://forum.xda-developers.com/showthread.php?t=2181929. Which was blatantly in the beginning of the forum. Has anyone found a fix for this issue, or is my only option JTAG repair?
Thanks,
Ryan
ryan9316 said:
Ladies and Gents,
I made sure I chose the correct RUU based on my CID (CWS__001)
I relocked my phone and attempted to install "RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_ 0.24p.32.09.06_10.130.32.34_release_signed.exe". After the RUU finished my phone seems to be hard bricked.
Won't Boot.
No power lights.
I knew this could happen when flashing an international version. AFTER getting owned I also found this post http://forum.xda-developers.com/showthread.php?t=2181929. Which was blatantly in the beginning of the forum. Has anyone found a fix for this issue, or is my only option JTAG repair?
Thanks,
Ryan
Click to expand...
Click to collapse
You could take your phone back and tell them it won't boot etc.
If you can't get it to boot neither can they, so no-one will know it's been unlocked/rooted.
Some people will say this is fraudulent, but hey, if you can live with yourself who cares what anyone else thinks?
Pft I returned mine to Telus when the same thing happened to me. The way I see it, it was HTC's RUU that bricked my phone, not me. Like you, I did not have supercid and was S-ON.
You could try the unbrick Evita thread. If you make it past step 3 you can save your phone.
You'll need to boot to Linux.
Sent from my One X using xda app-developers app
exad said:
Pft I returned mine to Telus when the same thing happened to me. The way I see it, it was HTC's RUU that bricked my phone, not me. Like you, I did not have supercid and was S-ON.
You could try the unbrick Evita thread. If you make it past step 3 you can save your phone.
You'll need to boot to Linux.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
I saw this and will give it a try, thank you for the advice!
ryan9316 said:
I saw this and will give it a try, thank you for the advice!
Click to expand...
Click to collapse
I bricked my phone trying to install elementalx and phone wouldn't boot at all and no lights. sent it in for jtag and they told me emmc controller was unresponsive and sent it back to me. looks like I may have to trash the phone... or make a few bucks on ebay.
mkalbarc said:
I bricked my phone trying to install elementalx and phone wouldn't boot at all and no lights. sent it in for jtag and they told me emmc controller was unresponsive and sent it back to me. looks like I may have to trash the phone... or make a few bucks on ebay.
Click to expand...
Click to collapse
Did they refund you? I was going to send it into mobiletechvideos for JTAG. I don't see the phones selling for more than 100$ on ebay.
ryan9316 said:
Did they refund you? I was going to send it into mobiletechvideos for JTAG. I don't see the phones selling for more than 100$ on ebay.
Click to expand...
Click to collapse
If the emmc controller isn't responding, it's worth even less than that.
Sent from my One X using xda app-developers app
ryan9316 said:
Did they refund you? I was going to send it into mobiletechvideos for JTAG. I don't see the phones selling for more than 100$ on ebay.
Click to expand...
Click to collapse
they did refund. minus the cost of shipping and something else, however. it was worth a try though... All I know though is I will never touch an elemental kernel again... not worth it that's for sure...
mkalbarc said:
they did refund. minus the cost of shipping and something else, however. it was worth a try though... All I know though is I will never touch an elemental kernel again... not worth it that's for sure...
Click to expand...
Click to collapse
Just curious about your situation. Did the kernel flash successfully and then just not boot? What ROM were you flashing it over? Tons of people, myself included, have flashed that kernel without issue so I'm interested in what exactly happened.
pside15 said:
Just curious about your situation. Did the kernel flash successfully and then just not boot? What ROM were you flashing it over? Tons of people, myself included, have flashed that kernel without issue so I'm interested in what exactly happened.
Click to expand...
Click to collapse
Sure, I too have used their kernels and have never had an issue until this time. So I started to install the kernel and it froze at I believe 60%? Then it sat... It said the flash could take awhile so to just wait so I did... For 2 hours. I knew something wasn't right because no elemental flash has taken my phone longer than a few minutes before this one so without thinking i'd hurt anything I held the buttons to hard power off the phone. After it shut off it's been completely dead since. No charge lights, no sign of any life at all other then the QHSUSB_DLOAD under device manager when plugged into my PC. the rom that I had flashed was the latest cleanrom. super bummed but i'll get over it. the worst part about this was I had pics of my kids that I had not backed up that are now lost.
mkalbarc said:
Sure, I too have used their kernels and have never had an issue until this time. So I started to install the kernel and it froze at I believe 60%? Then it sat... It said the flash could take awhile so to just wait so I did... For 2 hours. I knew something wasn't right because no elemental flash has taken my phone longer than a few minutes before this one so without thinking i'd hurt anything I held the buttons to hard power off the phone. After it shut off it's been completely dead since. No charge lights, no sign of any life at all other then the QHSUSB_DLOAD under device manager when plugged into my PC. super bummed but i'll get over it. the worst part about this was I had pics of my kids that I had not backed up that are now lost.
Click to expand...
Click to collapse
That does suck about the pictures. That would upset me more than the phone as well. I went and looked at the thread after I saw your post and saw a couple of other bricks aside from yours in the last couple of hundred posts. Very unfortunate that flashing a kernel bricked it. I try to stay away from anything that uses the Aroma Installer unless there are no other options, not saying that was the problem, but I've had numerous issues with it previously. After seeing multiple bricks from a basic kernel flash I'm going to definitely be more cautious about what I flash from now on. I'd be totally screwed if I bricked this phone. Anyway, hope you end up with something better out of this, like the HTC One.
pside15 said:
That does suck about the pictures. That would upset me more than the phone as well. I went and looked at the thread after I saw your post and saw a couple of other bricks aside from yours in the last couple of hundred posts. Very unfortunate that flashing a kernel bricked it. I try to stay away from anything that uses the Aroma Installer unless there are no other options, not saying that was the problem, but I've had numerous issues with it previously. After seeing multiple bricks from a basic kernel flash I'm going to definitely be more cautious about what I flash from now on. I'd be totally screwed if I bricked this phone. Anyway, hope you end up with something better out of this, like the HTC One.
Click to expand...
Click to collapse
Funny thing about the One... I was thinking about getting it but after this issue I will never look at another phone that doesn't have a removable sd card...
I think a key thing to note here is that you are flashing software that has been altered by someone you don't know and you can never be sure that things will work out. There's huge risks associated with rooting/unlocking your phone. If there wasn't HTC would warrant your phone regardless of what you do.
If you don't have an answer to the question "What will I do when I brick my phone?" don't root. Whenever modding anything, consoles, phones, set top boxes, I always assume that I will render it unusable. If that doesn't sit well with me, I don't modify it. That should be the general rule of thumb to follow.
Sent from my One X using xda app-developers app
3 words: Dropbox Camera Upload.
exad said:
I think a key thing to note here is that you are flashing software that has been altered by someone you don't know and you can never be sure that things will work out. There's huge risks associated with rooting/unlocking your phone. If there wasn't HTC would warrant your phone regardless of what you do.
If you don't have an answer to the question "What will I do when I brick my phone?" don't root. Whenever modding anything, consoles, phones, set top boxes, I always assume that I will render it unusable. If that doesn't sit well with me, I don't modify it. That should be the general rule of thumb to follow.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Very well said... I always get a little nervous when screwing with a new $500+ device.
Sent from my HTC One X using xda app-developers app
iElvis said:
3 words: Dropbox Camera Upload.
Click to expand...
Click to collapse
Thank you for the advice! I will remember that with my next phone.
I just use g+ to instantly upload my photos. Unlimited space is hard to argue with
Sent from my One X using xda app-developers app
phone not able to boot
guys please help me out I flashed stock root JB ROM after that my device wont boot just white screen with HTC logo. The phone boots into recovery but I wiped the sd card SD card mount error is being returned.
Clockworkmod recovery v6.0.3.1 S off
anuj.sherawat said:
guys please help me out I flashed stock root JB ROM after that my device wont boot just white screen with HTC logo. The phone boots into recovery but I wiped the sd card SD card mount error is being returned.
Clockworkmod recovery v6.0.3.1 S off
Click to expand...
Click to collapse
Install twrp 2.3.3.1 and reformat sd card with a pc. Move Rom to sd and reflash. And also what hboot? I know you said s-off bit did you fastboot the boot.img and see is that helped?
Sent from my HTC One X using xda app-developers app
31ken31 said:
Install twrp 2.3.3.1 and reformat sd card with a pc. Move Rom to sd and reflash. And also what hboot? I know you said s-off bit did you fastboot the boot.img and see is that helped?
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
thanks first of all I was on CMW, formatted the drive as computer prompted, lost the data but was able to flash the ROM and fastboot the boot image to phone.
Now only one problem the phone restarts and then goes to boot loop everytime I have to fastboot the boot image file.
DO I need to change the recovery and is there any way to by pass the fastboot process? Sorry for noob question