Database Info

[Q] Help Desperately Needed - Need to reroot and USB doesn't work

I think I put myself in a bad situation here...
I spent all day trying to figure out how to root my 5 week old Nexus as it's tethering ability is my only access to the web.
So - step one, I did the one-click method, as the instructions I was finding for "the long way" were written by people who know what they're doing FOR people who know what they're doing.
Once that was accomplished, I downloaded Rom Manager. Unfortunately Rom Manager didn't seem to want to work with One-Click's style of rooting, locking me on the boot screen every time I tried using it.
So, I finally worked out how to root my phone the "normal" way and Rom Manager was working.
Here's where my mistake came in... I was one part frustrated from how long it took me to figure it all out, one part elated that I finally DID figure it out, so I immediately put Cyanogenmod on my phone... without backing it up. I played with it a bit, but realized my mistake, so downloaded the 2.3.3 Stock Rom.
That totally futzed things up for me... First, my USB connection isn't working anymore. The USB cable still powers my phone, and the USB ports on my PC still work, but I can't get a phone to pc connection through USB anymore.
Second, my cell radio isn't working anymore, I can only get anything over wifi. The OTA 2.3.4 update was pushed and installed to me that way (The current version my phone is on now...)
Third, apparently my phone was no longer rooted, so Rom Manager wouldn't work anymore for me. When I go to the bootloader menu and try to Recover, it brings me to an android with a triangle and exclamation point symbol.
Once there, some trial and error brought up a menu that I'd hoped would have let me reroot or reinstall a working Rom, but every one I try gives me a Signature Verification error and aborts the install...
So, I'm stuck... Without my USB connection working, I can reroot my phone, and without rerooting, I can't get a working ROM back in place. If ANYBODY can help me with this, it will be greatly appreciated. If any additional information is needed, I'll do my best to give it. Thank you...

Who is your carrier? Need to know which phone you have.
Also I assume that since you said you rooted the hard way eventually, that means you successfully used Fastboot to unlock your bootloader, yes?
The Android with exclamation point is just the stock Android recovery partition.
The key to fixing your problem will be to get USB connection between phone and PC.
Please plug in your phone to USB connected to your computer, then put your phone into Bootloader mode (Power on while holding Volume Up). On your computer, open a command prompt window and type "fastboot devices" and post what it says.

Can you see the phone in fast boot by usb also have you course factory reset and then try to flash
Sent from my Nexus S 4G using Tapatalk

The big problem is that I'm unable to make a USB connection anymore. My phone is not reading any kind of connection to allow for file transfers or debugging, but it still powers the phone.

TBoarder said:
The big problem is that I'm unable to make a USB connection anymore. My phone is not reading any kind of connection to allow for file transfers or debugging, but it still powers the phone.
Click to expand...
Click to collapse
Can you answer my question about fastboot? I want to help you.

matt2053 said:
Who is your carrier? Need to know which phone you have.
Also I assume that since you said you rooted the hard way eventually, that means you successfully used Fastboot to unlock your bootloader, yes?
The Android with exclamation point is just the stock Android recovery partition.
The key to fixing your problem will be to get USB connection between phone and PC.
Please plug in your phone to USB connected to your computer, then put your phone into Bootloader mode (Power on while holding Volume Up). On your computer, open a command prompt window and type "fastboot devices" and post what it says.
Click to expand...
Click to collapse
I did that and nothing came up.

TBoarder said:
I did that and nothing came up.
Click to expand...
Click to collapse
ok can you please install PDAnet on your computer?
http://junefabrics.com/android/download.php
This will ensure the proper must up to date drivers are installed for you. This is the best and most reliable way to get the correct drivers.
EDIT: Then try fastboot again and tell me the output for "fastboot devices"

matt2053 said:
ok can you please install PDAnet on your computer?
This will ensure the proper must up to date drivers are installed for you. This is the best and most reliable way to get the correct drivers.
EDIT: Then try fastboot again and tell me the output for "fastboot devices"
Click to expand...
Click to collapse
It was already installed, but I reinstalled it. I got to the end of the process where it asked me to go into USB Debugging mode and won't finish the install because it's not reading the USB connection.
(Sorry for any delays here... Being a newbie, I have a 5 minute delay between when I can post)

No worries, thanks for trying. If you have hardware failure you might be out of luck. USB connection is pretty crucial for this stuff.
Maybe you can try Odin. See here: http://forum.xda-developers.com/showthread.php?t=947950

matt2053 said:
No worries, thanks for trying. If you have hardware failure you might be out of luck. USB connection is pretty crucial for this stuff.
Maybe you can try Odin. See here:
Click to expand...
Click to collapse
I've been looking into Odin, to see if there's a way I can do it just by pushing the files I need to my phone's sdcard and going into recovery mode. Not looking likely, but I'll read through the thread you linked me and maybe something will pop up. Thank you...
On the plus side, I just contacted Sprint and I *might* be able to get my phone replaced... Much as I'd like to troubleshoot this myself, it's looking like my only option. Too bad getting a phone replaced this early in a contract, just out of the warranty period is a total pain in the neck...

TBoarder said:
I've been looking into Odin, to see if there's a way I can do it just by pushing the files I need to my phone's sdcard and going into recovery mode. Not looking likely, but I'll read through the thread you linked me and maybe something will pop up. Thank you...
On the plus side, I just contacted Sprint and I *might* be able to get my phone replaced... Much as I'd like to troubleshoot this myself, it's looking like my only option. Too bad getting a phone replaced this early in a contract, just out of the warranty period is a total pain in the neck...
Click to expand...
Click to collapse
Can you post a link to the stock image you installed?

Was there ever a 2.3.3 for the nexus s 4g? Seems like it shipped with 2.3.4
Sent from my SPH-P100 using XDA App

matt2053 said:
Can you post a link to the stock image you installed?
Click to expand...
Click to collapse
It was downloaded through ROM Manager.
And yes, if I could get back into ROM Manager, I'd warn people NOT to flash their ROM to that. Bad mojo there.

My suggestion is to try and use Odin to flash it back to stock, I don't think Odin needs any drivers to see the phone...
Sent from my Nexus S 4G using XDA Premium App

TBoarder said:
It was downloaded through ROM Manager.
And yes, if I could get back into ROM Manager, I'd warn people NOT to flash their ROM to that. Bad mojo there.
Click to expand...
Click to collapse
Yeah see the thing is there is no 2.3.3 for NS4G. If you flashed 2.3.3 that means you flashed a GSM Rom on your CDMA phone. Oops! not the first time it has happened I'm sure.
Sent from my Nexus S using XDA App

Which totally explains what went wrong... Wow. ROM Manager, I though, was supposed to only bring up ROMs that are compatible with your phone model. Any way somebody can either let the developer know about this, or at the very least put a comment in the 2.3.3 ROM that specifically says it won't work with Sprint's network? That way nobody else will go through the hell I put myself through...
I'm wondering, could the USB connection issue be connected, like the "program" that controls that is integrated with the radio? Just curious, is all. Thanks again for your help!

How did you find astock 233 rom in rom manager, I only see cyanogen nighties oxygen, peter alphonso, extras etc everything is for the nexus a 4g
Sent from my Nexus S 4G using Tapatalk

TBoarder said:
Which totally explains what went wrong... Wow. ROM Manager, I though, was supposed to only bring up ROMs that are compatible with your phone model. Any way somebody can either let the developer know about this, or at the very least put a comment in the 2.3.3 ROM that specifically says it won't work with Sprint's network? That way nobody else will go through the hell I put myself through...
I'm wondering, could the USB connection issue be connected, like the "program" that controls that is integrated with the radio? Just curious, is all. Thanks again for your help!
Click to expand...
Click to collapse
Yeah. I have the T-Mobile version. When I download through Rom Manager I get a popup that says "select your phone model" or something similar and then two choices: "Nexus S" or "Nexus S 4G". It would be really easy to mess that up.
The good news is that I believe your phone can still be recovered, you're definitely not the first person with this exact issue, and at worst, it sounds like you have a Sprint rep who is willing to work with you. I think Odin is your only chance for a software solution. I can't walk you through Odin though, because I've never used it myself.

Let me know what happens.
Sent from my Nexus S using XDA App

matt2053 said:
Let me know what happens.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
I just got my warranty replacement phone due to an abnormally long backorder. Thank you very much for your help (And well, I would've more appreciated it if you hadn't shown me that the problem was all my fault... ). Being my only phone and being poor, I won't be trying to root again, no matter what I learned from this problem. Anyway, thanks again, the help was, in all seriousness, greatly appreciated.

Help? qhsusb_dload When rooting Rogers 727R.

Well looks like I HARD Bricked my phone when I ran SuperOneClick v2.3.1 to Root my phone.. "its only 2 days old" the phone will not even power up now.. and when I plug it into my pc It just shows up as "qhsusb_dload" in my device manager.. rogers is going to send me a new phone overnight and I have to send back my bricked one.. do you think they will find out I was rooting the phone? they are just replace it as a power issue.

http://forum.xda-developers.com/attachment.php?attachmentid=631288&d=1308601930
See if these drivers will work for ya. If not, probably nothing you can do about it.
Sent from my SGH-I727 using Tapatalk

Yep tryed the drivers.. Odin will now see the phone but just sits a setting up connection... also the phone can been see with the battery in or out... Rogers is sending me a new one tomorrow or Monday.. .from what I seen there is no way for them to tell if I have rooted the phone or not since they will have to do a jtag flash.

They will probably just say it was a hardware failure of some sort. You should be fine.
Sent from my SGH-I727 using Tapatalk

well I got QPST to see my phone now I just need a hex file to flash to it... looks like its been wiped clean my phone... odin will not see it but qpst will.

Haven't played with qpst since I tried to "unlock" a cdma phone. What a joke that was. CDMA sucks so bad. Sorry for spamming your thread..
Sent from my SGH-I727R using XDA App

I saw your post in the dev thread that you got scolded for. Not sure if it's locked yet so I'm posting here.
I'm hard bricked as well, with a replacement on the way. I'd rather fix my phone if possible with QPST. Please report back if you're able to get that hex image or find another way to make the phone work again. (although I'd be looking for the AT&T image--not the Rogers version)
Thanks and good luck!

Yes I have been looking for both images AT&T and rogers but none to be found.. the good thing is if we hard brick our phones and it will not even power up. We can still access it with Qualcomm Product Support Tools (QPST).. Now I can't find an image but if someone would be nice enough to upload a hex image of their low level boot.. but then they have to know how to use qpst. and its not a very nice tool to use.

TriC_101 said:
Yes I have been looking for both images AT&T and rogers but none to be found.. the good thing is if we hard brick our phones and it will not even power up. We can still access it with Qualcomm Product Support Tools (QPST).. Now I can't find an image but if someone would be nice enough to upload a hex image of their low level boot.. but then they have to know how to use qpst. and its not a very nice tool to use.
Click to expand...
Click to collapse
Can you link me to QPST? I've got a similar situation to yours.
By the way,
Does your phone do anything at all to indicate it's been plugged in?
Have you tried opening ADB to see if it is recognized there?

Ya the phone will not power on at all, nothing on the screen but when I plug it into the PC it sees Qhsusb_dload. in the Device mannager and QPST will see the phone.. but its stuck in a mode waiting to download a hex or bin file from Qpst.. but the phone will not power up at all. so ADB will not work.. the phone is stuck in a very low programming level.. here is a link to the software
http://www.x-drivers.com/catalog/flash/mobile_phones/companies/qualcomm/models/qpst/12051.html

so what do we do now, my phone is bricked too :[

Does it power on?

Wow thats alot of bricks. Most ive ever seen in one forum. What did you all do. Try and flash something from a different device?

what i did was i'm trying to flash the rom from galaxy s2 tmobile with the conversion zip but it bootloop on me, so i went to odin, it gave me error failed, i make mistake at this step is that i took out the battery the download mode to goes away, which i should have press volume up or down to get out of the screen after i did some research but everything was to late, i only have the phone working for less than 24 hours
---------- Post added at 06:10 AM ---------- Previous post was at 06:09 AM ----------
JimmyStale said:
Does it power on?
Click to expand...
Click to collapse
no but i plug in my computer in does try to install the driver thou

silver03wrx said:
Wow thats alot of bricks. Most ive ever seen in one forum.
Click to expand...
Click to collapse
Perhaps we should build a house...
silver03wrx said:
. What did you all do. Try and flash something from a different device?
Click to expand...
Click to collapse
My phone got washed in the laundry and I'm trying to resurrect it.

even my skyrocket bricked any help please

silver03wrx said:
Wow thats alot of bricks. Most ive ever seen in one forum. What did you all do. Try and flash something from a different device?
Click to expand...
Click to collapse
Tried to flash a "rom" I made in dsixda's Android Kitchen http://forum.xda-developers.com/showthread.php?t=1390903
I'm pretty sure I followed the instructions completely, not sure where I went wrong. Maybe trying to flash a 2.3.5 over Alien 4 (which is 2.3.6)?
At any rate, not blaming the kitchen. I probably did something I shouldn't have.
Got a replacement yesterday, so I'm good now with a hard lesson learned. First hard brick ever!

One more....
i was chatting with whats app and then the phone reboots and black screen....
the important thing is that a friend purchased the phone in Canada and i have no invoice and also no HTC service in México...
bad way to start the year.

TriC_101 said:
well I got QPST to see my phone now I just need a hex file to flash to it... looks like its been wiped clean my phone... odin will not see it but qpst will.
Click to expand...
Click to collapse
you are right, i also can see my phone on QPST and it seems to be clean. I think we just need someone to backup their phone and boot image in hex to unbrick the phones....
Someone that want to help us to test this???
Greetings

xuvert said:
you are right, i also can see my phone on QPST and it seems to be clean. I think we just need someone to backup their phone and boot image in hex to unbrick the phones....
Someone that want to help us to test this???
Greetings
Click to expand...
Click to collapse
I wouldn't mind helping as it would possibly benefit me as well. I can't seem to get QPST to read my working 727. I can get it to recognize the device but it says "no phone".
If someone wants to point me in the right direction I'd be glad to help.

Brick?

Was on my phone when it froze, I hard rebooted (held power) now it wont turn on, and the led doesnt indicate its charging. Thoughts?

Stock, rooted, ROM, recovery, ect....?
Help us help you

Same exact thing happened to me recently. I had to get my device switched out. Apparently a partition got corrupted and the phone was in diagnostic mode and I couldn't recover it.
Sent from the Shadows.

baseballfanz said:
Stock, rooted, ROM, recovery, ect....?
Help us help you
Click to expand...
Click to collapse
Rooted running Trickdroid 6.2 & TWIRP

i was worried I might have to switch it out. I hope they still have S4 versions.

Co worker had a similar problem on a hox after she dropped it. Wouldn't turn on or have charging light indicator. Reseated the micro sim card and it came back on. Go figure...
Sent from my HTC VLE_U using xda premium

If your problem is TO access to sd-card try this guide
http://forum.xda-developers.com/showthread.php?t=1630459
Sent whit HTC ONE S

removed Micro SD, no luck. Put it back in. no luck.
I'll see if its recognized on ADB when I get home, but i dont feel positive about it.

familiarstranger said:
removed Micro SD, no luck. Put it back in. no luck.
I'll see if its recognized on ADB when I get home, but i dont feel positive about it.
Click to expand...
Click to collapse
This just happened to me running the same rom and custom recovery. I even created a thread... I hope you and I aren't in the same boat.
http://forum.xda-developers.com/showthread.php?p=29276808#post29276808

Might be in a sleep of death. Plug it into a computer and see if it enumerates as QHUSB_DLOAD.

I too have this problem but am really looking to avoid exchanging it. Any other options?

familiarstranger said:
removed Micro SD, no luck. Put it back in. no luck.
I'll see if its recognized on ADB when I get home, but i dont feel positive about it.
Click to expand...
Click to collapse
I'm assuming you really meant your Micro SIM? Anyways also check if fastboot recognizes it with fastboot devices, then you can try fastboot booting a recovery. If you have to have it replaced and get an S3 I've read that HTC will replace with the S4 if you complain, have no source for this though.

yes I meant Micro SIM. No luck with fastboot. I am going the repair route with HTC. Does anyone have experience with this? what is the turnaround like?
frdd said:
I'm assuming you really meant your Micro SIM? Anyways also check if fastboot recognizes it with fastboot devices, then you can try fastboot booting a recovery. If you have to have it replaced and get an S3 I've read that HTC will replace with the S4 if you complain, have no source for this though.
Click to expand...
Click to collapse

familiarstranger said:
yes I meant Micro SIM. No luck with fastboot. I am going the repair route with HTC. Does anyone have experience with this? what is the turnaround like?
Click to expand...
Click to collapse
It can get pretty bad, it can be just fine. Don't return it unless it registers as QHUSB_DLOAD mode on USB, because that's the only time your phone is really dead.

I think I'm lucky...
A colleague of mine returned his, as he had the same with his One S. However he was running Trickdroid 5.2, so I don't really think Trickdroid is the point here....though he was also running the Tweaks (which do little to governing which could be a cause, not the removal of stock apps).
I have been running 6.2 for a week or so now and haven't found any worry....did have to reflash it (as I accidentally installed Tweaks, causing it to bootloop).
My colleague did say he was deinstalling Ice Age 3 game...but guess that was nothing similar.

I have seen that most people, who are running trick droid, are getting bricked devices. Chances are there that there must a minor glitch or problem in the rom that might cause the devices to become bricked.
Sent from my icecreamed Xperia Arc S

HTC warranty states I had water damage. I dont ever remember getting my phone wet, but they sent me pics that supposedly show it. The repair quote was $325. I got the phone back today, so I'll be taking it apart and see if i cant fix it....

Can you help me. My one s villec2 , unlock bootlader ok, but when flash Recovery battery low and off phone, i change battery but can not go to fastboot.
Sent from my HTC One S using Tapatalk 2

[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