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.

[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.

Can't get Vibrant to enter Recovery or Download mode after Odin Flash

Hey well, to start things off I was trying to unlock my T-Mobile SGS4G to work with AT&T but it turns out it needs to be rooted first. I have rooted before and this is the first time I have ran into a problem.
What I did first:
I used Heimdall in an attempt to flash CWM Recovery so I can gain root access. For some reason the zImage was bad (?) and my phone could only get to the T-Mobile logo and then freeze.
Recovery and Download DID work
What I did second:
I used odin3 to flash back a stock T-Mobile rom in hope to fix things... and it did everything succesfully but now it's stuck in a real boot loop.
Can't get into Recovery, nor Download. It's really depressing to keep seeing that battery show over and over again.
Any ideas on how to get my computer to detect my phone again?
Thanks.
Edit:
I did every button combination + usb plug combination known to man. I uninstalled and installed the files again.
Did my phone brick because I ticked the partition tab on odin?
PLEASE help.

Our phone IS NOT the Vibrant. Hopefully someone can help you, but... I don't know. If you flashed OUR stock rom, with bootloaders... you're screwed. But, the fact you have images on your screen, should give you some hope.

Yea, I saw that, but the title says he has a vibrant. I don't know....

Head to the vibrant forum there are some un-brick tools over there...you need to get it in download mode use odin to flash stock froyo vibrant rom.. Should get it back up and running
Sent from my SGH-T959V using xda premium

Kingarabian said:
T-Mobile SGS4G
Click to expand...
Click to collapse
Just to verify, pull out your battery and check if you have the SGH-T959V

One of the "download jigs" may help once you are certain which phone you have and what firmware and ROM you need to flash. You can make your own with a resistor and a microUSB plug, I bought one for $8.00, delivered, (I now see they have them on Amazon for $4, Super Saver eligible) and others have had good luck with even cheaper ones on eBay.
Also: http://forum.xda-developers.com/showthread.php?p=9403915

Jigs are cheap and unless you got the right resistor lying around buy a ready made one. Also if the phone shows up in odin you can download something whatever picture shows up on the screen. Raver has a thread about using heimdall to fix the boot files but its about six months old. Worked for me once. It might even be indexed in the bible under development.
Sent from my SGH-T959V using xda premium

[Q] Phone will not turn on

My Galaxy S3 will not respond to any combination of button presses, and the device is identified as QHSUSB_DLOAD in Device Manager. If I take out the battery and plug it in, the light turns red for ~10 seconds, and then turns off. (Device Manager is refreshed at this time, but still reads it out as QHSUSB_DLOAD). It does not respond to home+power+vol down or up.
To get to this result, I had booted into recovery mode in order to install a new ROM, but the installation failed. I chose the reboot option and this is how I ended up. Looking back, I probably should've restored the device prior to booting...

x04a said:
My Galaxy S3 will not respond to any combination of button presses, and the device is identified as QHSUSB_DLOAD in Device Manager. If I take out the battery and plug it in, the light turns red for ~10 seconds, and then turns off. (Device Manager is refreshed at this time, but still reads it out as QHSUSB_DLOAD). It does not respond to home+power+vol down or up.
To get to this result, I had booted into recovery mode in order to install a new ROM, but the installation failed. I chose the reboot option and this is how I ended up. Looking back, I probably should've restored the device prior to booting...
Click to expand...
Click to collapse
You most likely need to go into Odin mode and flash back to stock using Odin. Just follow the steps in this guide:
http://forum.xda-developers.com/showthread.php?t=1762709
Also, dumb question, but is your battery dead? I know I had this problem coming from a completely dead battery once, took a bunch of tries to get it to start charging and turn back on. But I wasn't coming off of a bad flash, of course.

dontsayeta said:
You most likely need to go into Odin mode and flash back to stock using Odin. Just follow the steps in this guide:
http://forum.xda-developers.com/showthread.php?t=1762709
Also, dumb question, but is your battery dead? I know I had this problem coming from a completely dead battery once, took a bunch of tries to get it to start charging and turn back on. But I wasn't coming off of a bad flash, of course.
Click to expand...
Click to collapse
The battery was at ~60% when I was flashing.
ALSO: I can't get into ODIN mode as the device doesn't respond to any type of button combination.

Deleted.

dontsayeta said:
Ok. I don't know what steps you have taken so far, but do a battery pull and then try to get into Odin mode.
Click to expand...
Click to collapse
I don't know if you read the OP or not but I did in fact already do what you stated. It does not work. I have: Battery pull+attach to USB, Battery pull+battery back in. Neither work to get back into ODIN mode.

Yeah, sorry, I did read that right after my post, but I couldn't go back and edit it fast enough because I have these new user restrictions on my account.

dontsayeta said:
Yeah, sorry, I did read that right after my post, but I couldn't go back and edit it fast enough because I have these new user restrictions on my account.
Click to expand...
Click to collapse
I understand, I have the same restriction. However, I think that the device is simply bricked and cannot be recovered. If no solution is posted then I will be heading to the VZW store tomorrow I suppose.

x04a said:
My Galaxy S3 will not respond to any combination of button presses, and the device is identified as QHSUSB_DLOAD in Device Manager. If I take out the battery and plug it in, the light turns red for ~10 seconds, and then turns off. (Device Manager is refreshed at this time, but still reads it out as QHSUSB_DLOAD). It does not respond to home+power+vol down or up.
To get to this result, I had booted into recovery mode in order to install a new ROM, but the installation failed. I chose the reboot option and this is how I ended up. Looking back, I probably should've restored the device prior to booting...
Click to expand...
Click to collapse
Your phone is hard bricked. I'm gonna guess you were flashing a non Verizon ROM, probably an international.
The only fix at this point is a JTAG service. Also, unfortunately you would not have been able to restore before leaving recovery anyways. I'll try to find the popular website people use for that service.
Sent from my SGS3 running Eclipse 2.1 build 4

Yep, sounds like you flashed a ROM not made for the Verizon S3. Be a little more careful next time.
Check out mobile tech videos for a JTAG.

Zalithian said:
Yep, sounds like you flashed a ROM not made for the Verizon S3. Be a little more careful next time.
Check out mobile tech videos for a JTAG.
Click to expand...
Click to collapse
Thanks I couldn't remember the site.
Sent from my SGS3 running Eclipse 2.1 build 4

I'm not trying to be a ****, but how/why do people flash roms not made for Verizon GS3? Is it really that easy to make the mistake? Where are they getting the roms from??
Just curious

josh995 said:
I'm not trying to be a ****, but how/why do people flash roms not made for Verizon GS3? Is it really that easy to make the mistake? Where are they getting the roms from??
Just curious
Click to expand...
Click to collapse
Probably just google about flashing roms, find a youtube video and follow instructions. Wonder if a lot of videos don't have a warning, or if people ignore it.

josh995 said:
I'm not trying to be a ****, but how/why do people flash roms not made for Verizon GS3? Is it really that easy to make the mistake? Where are they getting the roms from??
Just curious
Click to expand...
Click to collapse
I'm just an idiot, and jumped the gun on this flash.

josh995 said:
I'm not trying to be a ****, but how/why do people flash roms not made for Verizon GS3? Is it really that easy to make the mistake? Where are they getting the roms from??
Just curious
Click to expand...
Click to collapse
Well, back in the days before quadcore... the roms that were made for the international HTC Desire HD also worked on the us version the HTC Inspire 4G. . . I fell right into the pitfall after getting used to that.

[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