Database Info

[Q] Busted Phone Suggestions

So yesterday my phone fell from about OptiPlex height right onto the USB port with a cable plugged in. The plugged torqued a bit, and the result is that it won't connect to any computer, though it seems to charge fine.
I want to see if T-Mo will replace it, but I figure I should get Valhalla off it first. My questions are 2:
1) Is there a way to get it back to stock, including recovery, without USB?
2) Does T-Mo really check that I haven't rooted and ROM'ed the phone?
Does anybody have any experience like this to share?

brutuspa said:
So yesterday my phone fell from about OptiPlex height right onto the USB port with a cable plugged in. The plugged torqued a bit, and the result is that it won't connect to any computer, though it seems to charge fine.
I want to see if T-Mo will replace it, but I figure I should get Valhalla off it first. My questions are 2:
1) Is there a way to get it back to stock, including recovery, without USB?
2) Does T-Mo really check that I haven't rooted and ROM'ed the phone?
Does anybody have any experience like this to share?
Click to expand...
Click to collapse
Obtain a micro SD to SD converter
Place the micro SD into the converter, plug it into your computer
Open the SD and place the ROM zip onto the SD
Put the SD back into your phone
Boot to recovery, flash ROM from zip
Here is a stock zip i found for you: http://forum.xda-developers.com/showthread.php?t=1062847
Also I know this isn't going to help too much, but I once "bricked" an optimus (I now know it wasn't bricked, but I was dumb n00b and deleted the launcher XD) and returned it within the 14day window... they never even asked a question...

tehgyb said:
Obtain a micro SD to SD converter
Place the micro SD into the converter, plug it into your computer
Open the SD and place the ROM zip onto the SD
Put the SD back into your phone
Boot to recovery, flash ROM from zip
Here is a stock zip i found for you: http://forum.xda-developers.com/showthread.php?t=1062847
Also I know this isn't going to help too much, but I once "bricked" an optimus (I now know it wasn't bricked, but I was dumb n00b and deleted the launcher XD) and returned it within the 14day window... they never even asked a question...
Click to expand...
Click to collapse
Thanks for the link, I'll definitely grab that ROM.
However, how can I Odin it without a working USB? I can deal with any CWM ROMs, but I'd be returning the device without stock recovery and rooted. I am probably being overly paranoid, but I could get by using the phone without USB, just flashing whatever GB or, dare I say, ICS ROMs that our benevolent devs make available.
See my dilemma?

Wait, so is the problem your USB cable or the actual USB plug on your phone?
If it's the former, you could get any Micro USB cable. I found that my SGS4G can charge with the BlackBerry cables.

bkoon1218 said:
Wait, so is the problem your USB cable or the actual USB plug on your phone?
If it's the former, you could get any Micro USB cable. I found that my SGS4G can charge with the BlackBerry cables.
Click to expand...
Click to collapse
No, it's the latter. Sorry, in trying to brief I wasn't clear.
Ordinarily to return a phone I assume I would need to track down a stock image, Odin it, and then SuperOneClick unroot, if necessary. I would imagine both of those steps would require a working data connection via USB. Mine only charges, it now doesn't connect on three computers that used to mount it with no problem.
I can pull the MicrosSD or transfer via WiFi and load anything through CWM (ICBINB, Valhalla, KI*, KJ*...) and have been. But if I want to turn it over to T-Mo for a replacement, I imagine it has to look like I haven't rooted and ROMed it with every GB release that has seen the light of day the past 2 months. Even if I CWM a stock KB5 or KD1, I'll still have a warranty-violating Recovery and it will be rooted.

brutuspa said:
Thanks for the link, I'll definitely grab that ROM.
However, how can I Odin it without a working USB? I can deal with any CWM ROMs, but I'd be returning the device without stock recovery and rooted. I am probably being overly paranoid, but I could get by using the phone without USB, just flashing whatever GB or, dare I say, ICS ROMs that our benevolent devs make available.
See my dilemma?
Click to expand...
Click to collapse
That link is a cwmable zip of stock without root. I would think that'd do the trick, no?
Sent from my SGH-T959V using XDA App

My bad, I assumed it was Odin only.

brutuspa said:
My bad, I assumed it was Odin only.
Click to expand...
Click to collapse
Unless I misread something... :X
Sent from my SGH-T959V using XDA App

I'll let you know after Titanium finishes. Wish me luck

tehgyb said:
Unless I misread something... :X
Sent from my SGH-T959V using XDA App
Click to expand...
Click to collapse
It's an Odin ROM, from what I'm reading. I haven't taken the time to download it and check myself though.

bkoon1218 said:
It's an Odin ROM, from what I'm reading. I haven't taken the time to download it and check myself though.
Click to expand...
Click to collapse
OK, I'll hold off on that then.

For what it's worth, T-Mobile pointed out that I had "weird" software on my phone, and said they couldn't help. I tried to say yes, but if I revert to stock what could you do? They didn't go for it.
Sent from my SGH-T959V using XDA App

brutuspa said:
For what it's worth, T-Mobile pointed out that I had "weird" software on my phone, and said they couldn't help. I tried to say yes, but if I revert to stock what could you do? They didn't go for it.
Sent from my SGH-T959V using XDA App
Click to expand...
Click to collapse
Damn, that really sucks. You really shouldn't admit to rooting and flashing custom ROMs, since that already voids your warranty. Reverting back to stock doesn't legally unvoid your warranty, I believe.
Sorry, but I think you just might be SoL in this case.
If you have insurance, a crazy idea could be to purposely hard brick your device and say that your phone completely screwed up after you dropped it. You should probably get more suggestions about this idea first though.
Another less crazy idea would be for you to open up your phone and see if you can set it back in place properly.

bkoon1218 said:
Damn, that really sucks. You really shouldn't admit to rooting and flashing custom ROMs, since that already voids your warranty. Reverting back to stock doesn't legally unvoid your warranty, I believe.
Sorry, but I think you just might be SoL in this case.
If you have insurance, a crazy idea could be to purposely hard brick your device and say that your phone completely screwed up after you dropped it. You should probably get more suggestions about this idea first though.
Another less crazy idea would be for you to open up your phone and see if you can set it back in place properly.
Click to expand...
Click to collapse
Technically I didn't admit anything. She said "let me take it in back and try it on our computer". 5 minutes later she was showing me the About phone screen and calling me out for it. I'll try a different T-Mo store, and hope she didn't note my account.
Then my troubles got worse, but now are better.
I ended up hosing the whole thing. I couldn't get back to recovery - only download. Then I tried Odin, while jiggling the USB, and was able to get it to connect and accept KD1, but it failed halfway through. I kept monkeying with the USB and saw a little flash and then it powered off completely. Battery pull got it back to the failed firmware - try Kies prompt, but Odin could see it. Pushed KD1 again while not even breathing on the phone and it finished.
I now have a phone that looks stock. It definitely has a bad USB. I know a shop that replaced my Blackberry Curve's USB for about $70. That will be my next step if T-Mo marked my account with a scarlet letter.
Let's see how long I can stand stock
PS at least my WiFi works better than GB
PPS A different store arranged for a replacement for a $20 processing fee. It arrives Thursday.

Bricked Phone after flashing Steve0007's img

I was one of the unlucky testers before Steve0007 closed the thread. Did anyone figure out how to save our Sensation after the bad flash? My phone does not light up or respond to any button presses but when plugged into the computer it is recognized as an "unrecognized device."
I guess this is the risk we run being early testers. Hopefully someone figures it out otherwise I've got myself very expensive paper weight.

I assume no two button rescue? And this should be in q/a or general
Can you get to the bootloader?
Sent from my Sensation using xda premium

what did he brick people's phones with what was it supposed to be?

Wrong section. And that happened to me when i got an hd2 and i bricked it. Luckily it was 2 days after i bought it so tmobile gave me another because they thought something was wrong with it. But next time please post in the right section. Thanks.

nba1341 said:
what did he brick people's phones with what was it supposed to be?
Click to expand...
Click to collapse
Its probably only a soft brick
Sent from my Sensation using xda premium

Thank god I didn't flash it, I just finished downloading it when people started reporting issues.
Anyway, I'm sure he didn't mean for it to happen. If you have a spare battery, have you tried putting that one in?

These things are usually flash at your own risk.
I would never flash a ruu, unless it's official it could cause problems.
Sent from my Sensation using Tapatalk

Also, if it doesnt work and if you have tmo. Tell them bs and they will get you one. Just some advice and please dont flame me.

tried spare battery. same result. And i'm sure he didn't do it maliciously I've flashed many of his things before with no problem. Just hoping to get some help. Phone doesn't respond. Can't get to bootloader. Only sign of life is windows recognizing that i plugged something into the usb slot.

Yes as I said, this happened to me exactly when i had a tmo HD2 and flashed a european ruu and it was dead. I tried everything. You will have better luck to talk to your insurance company.

Have you got ADB installed on your pc? If not start downloading and installing it. I will find some links, in just a sec.
Edit:
New to ADB CLICK HER
More to set up path CLICK HERE

http://www.mediafire.com/?rrwi4f258lie1r7
Extract to system 32 or sysWOW64 (64bit)
Try 3 finger salute (VOL UP,VOL DOWN + POWER) with your phone plugged into pc and pc volume up see if it makes a sound like a device has connected.
Whats was this RUU anyway?
if you just need ADB you dont need all of the stuff above or to set up a path if its extracted to those folders

duychau said:
tried spare battery. same result. And i'm sure he didn't do it maliciously I've flashed many of his things before with no problem. Just hoping to get some help. Phone doesn't respond. Can't get to bootloader. Only sign of life is windows recognizing that i plugged something into the usb slot.
Click to expand...
Click to collapse
This is excatly what happened to me.Computer wont see the phone though,so no adb fix can be applied.Mnn i'm so pissed as i dont have insurance.

usually blagging HTC will do the trick for a repair,dont mention XDA, ROOT, ICS or basically anything except your phone said update was available and the battery died
Click to expand...
Click to collapse
roflcopter is 10chars

duychau said:
tried spare battery. same result. And i'm sure he didn't do it maliciously I've flashed many of his things before with no problem. Just hoping to get some help. Phone doesn't respond. Can't get to bootloader. Only sign of life is windows recognizing that i plugged something into the usb slot.
Click to expand...
Click to collapse
What does it recognize it as?

unrecognized usb device

Ok guys, it looks like the firmware that I posted to another thread from 3.06 bricked few devices. I have flashed it and it worked fine, so i tried again with the package i posted and indeed it is corrupted as it bricked also mine
My device does not respond, so I would think it is dead
I feel sorry for those who have bricked also theirs based on the package i posted.
I am closing my Rom thread and starting now my Rom developments will be for my own use. I will not publish anymore my work.
Again I feel sorry for those who have lost their devices.
Steve

ok so now his rom thread is closed. Why not keep it open and work together to help those with bricked devices attempt to restore them to a working state?
That way you keep your reputation rather than running away after bricking devices?

Arrrggghhhh,This could not have come at a worse time

nba1341 said:
ok so now his rom thread is closed. Why not keep it open and work together to help those with bricked devices attempt to restore them to a working state?
That way you keep your reputation rather than running away after bricking devices?
Click to expand...
Click to collapse
Because as far as I know no way to get them back

Is this fixable?

First off, I am a veteran of flashing and have a decent amount of experience fixing up bricked phones, but this time nothing is working.
I flashed a Jellybean rom to my one x this morning, and now nothing is working. Literally. I can't access bootloader, in fact, I can't even get the screen to turn on. I have tried holding down the power button, as well as entering recovery etc... But nothing is working. Am I missing something simple or am I really in trouble?

Doesn't sound good. Any notification light when you plug the wall charger in?
What were the exact steps you've done to flash? You have unlocked bootloader, installed a custom recovery, then flashed a ROM? Which ROM specifically? Hopefully you didn't flash a ROM ment for the international (Tegra) version to a Snapdragon (AT&T, Roger, etc.) version phone.
At what point did the ROM flash fail? any error messages from recovery?

Did you flash an international one X ROM? Just wondering to get that scenario out of the way.
Sent from my One X using xda app-developers app

redpoint73 said:
Doesn't sound good. Any notification light when you plug the wall charger in?
What were the exact steps you've done to flash? You have unlocked bootloader, installed a custom recovery, then flashed a ROM? Which ROM specifically? Hopefully you didn't flash a ROM ment for the international (Tegra) version to a Snapdragon (AT&T, Roger, etc.) version phone.
Click to expand...
Click to collapse
The steps were in the same order, the rom is this one: http://forum.xda-developers.com/showthread.php?t=1763240. Looking at it, I think there is a good chance that is the problem. Anything I could do to fix it?

teswolf96 said:
The steps were in the same order, the rom is this one: http://forum.xda-developers.com/showthread.php?t=1763240. Looking at it, I think there is a good chance that is the problem. Anything I could do to fix it?
Click to expand...
Click to collapse
It is 100% the problem. If the phone is not recognized when plugging into your PC, I think you're hosed (but maybe others may know more and correct me on this). If it is recognized, get the RUU for your phone and run it.
I ask again, any notification (charging light) come on when you plug the wall charger in?
For the AT&T (Snapdragon) version of the One X, only flash things in this specific forum:
http://forum.xda-developers.com/forumdisplay.php?f=1541
Want to see everything in an organized compilation, go here:
http://forum.xda-developers.com/showthread.php?t=1671237

redpoint73 said:
It is 100% the problem. If the phone is not recognized by fastboot, I think you're hosed. Any notification (charging light) come on when you plug the wall charger in?
Click to expand...
Click to collapse
Nope - Should I just take it back to AT&T and see if I can get a replacement?

teswolf96 said:
Nope - Should I just take it back to AT&T and see if I can get a replacement?
Click to expand...
Click to collapse
Warranty replacements are for defects by HTC, not for damage that you caused.
If you are asking if you can lie about what happened, and get a replacement, than I'm not going to dignify that question with a response.

Well, I bricked my phone once and went straight to LG, they fixed it for me? Maybe HTC might fix it for you?
Sent from my LG-P930 using xda premium

It's likely your phone is screwed. Strange though that it just died
Sent from my One X using xda premium

Connect the phone to your computer, and see if adb can see it. Of it can't, and the phone won't even show any lights when connected to the charger, I think you're screwed.
Also, leave it on the charger for several hours, and see if there is any change. There is a possibility if just got stuck in a bootloop on on the splash screen, and you killed the battery that way. But you haven't provided enough information for us to really know (what step it stalled on, what was on the screen, etc.).

[Q] Hard Bricked GS3

Hello, I just got my new GS3 yesterday. Eager to root and ROM and all the fun stuff. I rooted and unlocked, and used Odin to flash CWM Recovery. Flashed the latest version of Android Revolution HD 16. I wiped cache, dalvik, the whole 9 yards. I did not WIPE boot.img though. Flashed Android Revolution 16, it all went good. Clicked Reboot Phone in CWM Recovery and nothing. No LED light on when plugged into USB or via wall charger. No Download mode, or recovery. Nothing, like nothing at all. Anything you guys suggest?
EDIT: I am not sure if it is Hard Bricked. When I plug it into my PC, it makes a sound. Also tries to install a driver and fails every time.
EDIT2: Okay guys, my fault. Downloaded a ROM that was meant for a different model/type GS3 forum when I have a Verizon GS3 (SCH-1535). Anyone know how to fix this problem? Please disregard this incorrect forum post.

If you flashed anything related to the international S3, Google search J-tag! Or return the device and play dumb...

droidstyle said:
Google search J-tag! Or return the device and play dumb...
Click to expand...
Click to collapse
I am paying for full coverage every month too, and okay, couldn't I also get a Usb JIG to force download mode?

T Greezy said:
I am paying for full coverage every month too, and okay, couldn't I also get a Usb JIG to force download mode?
Click to expand...
Click to collapse
No read my edited post. You most likely hardbricked your device, meaning you no longer have download mode.

droidstyle said:
No read my edited post. You most likely hardbricked your device, meaning you no longer have download mode.
Click to expand...
Click to collapse
Well, I NOW have a red LED on my phone when it is plugged into the PC without battery, sd card, or sim card. Is that a good sign?

T Greezy said:
Well, I NOW have a red LED on my phone when it is plugged into the PC without battery, sd card, or sim card. Is that a good sign?
Click to expand...
Click to collapse
No that verifies what i previously posted.

droidstyle said:
No that verifies what i previously posted.
Click to expand...
Click to collapse
I have faith, thought. I can maybe push something using ADB you think?

You need J-tag.
If there was a way to fix it yourself, nobody on here would worry about bricked phones.
Gotta be super careful and read every single word of a ROM thread and if you aren't sure if it will work for your phone or not, just ask and someone will say either yes or no
Sent from my SCH-I535 using xda app-developers app

josh995 said:
You need J-tag.
If there was a way to fix it yourself, nobody on here would worry about bricked phones.
Gotta be super careful and read every single word of a ROM thread and if you aren't sure if it will work for your phone or not, just ask and someone will say either yes or no
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I guess so. I read something about plugging the phone into the pc without the battery so the red light would come on. Then, you would hold a combination of buttons, and while you're still holding them, put the battery back in while you're still holding them. I guess J-Tag is the only way? Where can I get this? Someone link me. Thanks!

T Greezy said:
I guess so. I read something about plugging the phone into the pc without the battery so the red light would come on. Then, you would hold a combination of buttons, and while you're still holding them, put the battery back in while you're still holding them. I guess J-Tag is the only way? Where can I get this? Someone link me. Thanks!
Click to expand...
Click to collapse
Look like I'm going to drop 60 bucks for a JTAG service? Anyone please stop me if this is not the only way to fix this
email me at [email protected]!

No one is going to stop you. You flashed an international ROM on an s3. This is a known method of hard bricking your s3.
Sent from my SCH-I535 using xda app-developers app

T Greezy said:
Look like I'm going to drop 60 bucks for a JTAG service? Anyone please stop me if this is not the only way to fix this
email me at [email protected]!
Click to expand...
Click to collapse
That sounds about right. Luckily it's $60 and not $600 for a new phone
Sent from my SCH-I535 using xda app-developers app

Same thing happened to me. Needed a j-tag but risked calling Verizon told them my phone wouldn't come on all they asked me was if I damaged it with water or heat. (Either Verizon doesn't care or actually they just scrap the phone) I was rooted and unlocked but flashed the wrong carrier rom. Now I have a replacement phone that cost me $0.
They sent me the 16g and not the 32g by mistake I figured I've pushed my luck enough
Sent from my SCH-I535 using Tapatalk 2

First go to Get.cm download a d2vzw rom. Put it on your sd card. Put the sd card into phone
If you have ADB on your computer do
Code:
adb reboot recovery
You should boot in Clockwork Recovery.
From there flash the D2VZW Rom, Wipe Data,
That should save you.

ericerk said:
First go to Get.cm download a d2vzw rom. Put it on your sd card. Put the sd card into phone
If you have ADB on your computer do
Code:
adb reboot recovery
You should boot in Clockwork Recovery.
From there flash the D2VZW Rom, Wipe Data,
That should save you.
Click to expand...
Click to collapse
How do you figure? How can you adb recovery when the device wont turn on? The device is hardbricked plain and simple...your advice is simply false hope.

I do have a question for the op and the other guy who flashed an international ROM. Were did you get them and how did you find then ( like was it a site you googled?) I've noticed a lot of these lately and am wondering if it's something that can be avoided (besides the obvious read what you're flashing)
To the adb guy there us no recovery on his phone it was overwritten by part of the international ROM. he needs to JTAG his phone, don't call Verizon. You did this to your own phone, pay the 60 and learn your lesson.
Sent from my SGS3 running Eclipse 2.1

droidstyle said:
How do you figure? How can you adb recovery when the device wont turn on? The device is hardbricked plain and simple...your advice is simply false hope.
Click to expand...
Click to collapse
One day someone is going to find a way to unbrick the hard brick, lol. Eventually. Anyways, if it was "dead" then why would it show my S3 as "QHSUSB_DLOAD"? and attempts to install a driver. I'm gonna try to find the right driver to manually install, and troubleshoot from there. I mean come on guys, be optimistic. How great if this problem was RESOLVED? Also, the download mode got wiped/overwritten from a different ROM for a different model of the GS3. What about the Recovery? CWM? If I can just magically, somehow, maybe even push some type of command. Even maybe ADB? Or something in the terminal. I'm really trying to find a solution. So in the future, we will have a SOLUTION.
Anyways, I'm going to be shipping my GS3 Monday or Tuesday for Samsung to repair (If they can) or replace for no charge!
Wish me luck guys, gonna be really thinking out of the box.

Hope you can figure it out. But someone had a way to fix a hard brick.... The JTAG
Sent from my SGS3 running Eclipse 2.1

Okay guys, I've actually have gotten some good progress, I hope! I came across a thread that a guy named (therockk) he also, hard bricked his S3. Sent him a PM, and he told me he got ODIN to recognize his hard bricked S3 "WITHOUT" download mode. He said he found a driver for QHSUSB_DLOAD and manually applied the driver update. His PC, then recognized his S3 as a ID CODE: COM10 - I do not know what that means, I asked around. Some people say that it is the code for when your phone is connected in Download Mode? Nevertheless, this is good in my eyes. The phone as now, recognized as COM10 in ODIN, in its hard-bricked stage. This could be that also, maybe, the phone will be recognized in ADB/Fastboot commands. Maybe we can get something going here guys! I'm trying to look on the bright side. I'll keep you posted.
EDIT: Okay guys, was looking at some screenshots of the CODE ID's. Like I said, my buddy "therockk" said he got ODIN to recognize his phone as a COM10, while being hard-bricked. I am guessing there are different CODE ID's for each model/version of the S3. I did make an observation that he, has a different model S3 ( i747 ) and he got his to see COM10. Which means it was Added!! - My Verizon S3 (SCH-1525) should come up as COM4 when the PC recognizes it. When I do get my PC to recognize my S3, I will confirm that my SCH-1535 phone comes up as COM4, if not, I will confirm the correct CODE ID. therockk's i747 came up as a COM10, that is confirmed.
EDIT 2: Okay guys! Updated the driver successfully! QSHUSB_DLOAD is now Qualcomm HS-USB QDLoader 9008 (COM8). I feel like we're getting closer. Now to see if Odin will pick it up!

I can probably help you through this problem after work tonight if you are still having trouble. Just pm me around 10pm est
Sent from my SCH-I535 using xda app-developers app

[Q] Hard Bricked? Don't see how....

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