Normally, I wouldn't ask for help with a problem like this, but I'm rather concerned and could use assistance. Several days ago, I attempted to unlock and root my Verizon GS3. I followed the instructions from the XDA article, along with the ones provided in DroidModd3rX's YouTube video exactly on my VZW GS3, build JZO54K. I hard bricked my phone after flashing the VRALEC bootchain. It only showed up in the Device Manager on Windows 8 as QHSUSB_DLOAD. It was stuck like that as soon as I flashed the bootchain. Is there something I've done wrong that I could have done differently to prevent it from happening? I had just purchased it the day before, so I was able to get a replacement, but I'm highly interested in rooting my device (I've successfully rooted every other phone I've had) and want to ensure this doesn't happen again. Is it a problem with Windows 8, is it the build my phone is running on, or is it perhaps because I had USB Debugging checked on? I just find it odd that I've had this problem when I followed all the proper protocol. And yes, I did check the MD5, it was fine.
Can you get into Odin mode or download mode? If you can, follow this thread. http://forum.xda-developers.com/showthread.php?t=1974114
Sent from my SCH-I535 using xda premium
darthsentinel said:
Normally, I wouldn't ask for help with a problem like this, but I'm rather concerned and could use assistance. Several days ago, I attempted to unlock and root my Verizon GS3. I followed the instructions from the XDA article, along with the ones provided in DroidModd3rX's YouTube video exactly on my VZW GS3, build JZO54K. I hard bricked my phone after flashing the VRALEC bootchain. It only showed up in the Device Manager on Windows 8 as QHSUSB_DLOAD. It was stuck like that as soon as I flashed the bootchain. Is there something I've done wrong that I could have done differently to prevent it from happening? I had just purchased it the day before, so I was able to get a replacement, but I'm highly interested in rooting my device (I've successfully rooted every other phone I've had) and want to ensure this doesn't happen again. Is it a problem with Windows 8, is it the build my phone is running on, or is it perhaps because I had USB Debugging checked on? I just find it odd that I've had this problem when I followed all the proper protocol. And yes, I did check the MD5, it was fine.
Click to expand...
Click to collapse
Just so you know, it isn't the USB debugging. I just did the same procedure using Windows 7 and Odin 3.07 with debugging on, and it worked first shot. Could be Windows 8, but I can't say for certain.
m-cat said:
Can you get into Odin mode or download mode? If you can, follow this thread. http://forum.xda-developers.com/showthread.php?t=1974114
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Nope, it was quite literally hard bricked. No getting it into anything.
a.demarco said:
Just so you know, it isn't the USB debugging. I just did the same procedure using Windows 7 and Odin 3.07 with debugging on, and it worked first shot. Could be Windows 8, but I can't say for certain.
Click to expand...
Click to collapse
Hrmm, well that is annoying, as I don't have access to a Windows 7 Computer to try it again... But thanks for the heads-up!
Are you SURE you followed DroidmodderX's instructions to the T? I've seen this happen from flashing the file in the wrong slot in Odin. Did you make sure to put it in the PDA slot?
I too used this method to root and unlock a while back. I would feel confident using it again if I needed to.
nicholi2789 said:
Are you SURE you followed DroidmodderX's instructions to the T? I've seen this happen from flashing the file in the wrong slot in Odin. Did you make sure to put it in the PDA slot?
I too used this method to root and unlock a while back. I would feel confident using it again if I needed to.
Click to expand...
Click to collapse
Yes, I was very sure to put it in the PDA slot. In fact, I remember double-checking that I did that because I thought it was unusual.
darthsentinel said:
Yes, I was very sure to put it in the PDA slot. In fact, I remember double-checking that I did that because I thought it was unusual.
Click to expand...
Click to collapse
Hmm. Are you sure you got a good download of the bootchain?
nicholi2789 said:
Hmm. Are you sure you got a good download of the bootchain?
Click to expand...
Click to collapse
Almost completely positive. At the very least, the MD5 Matched.
darthsentinel said:
Almost completely positive. At the very least, the MD5 Matched.
Click to expand...
Click to collapse
Okay. So you've installed the correct drivers for your phone as well right? It shows up as SCH-I535 on your computer?
Sent from my MOAR'D Galaxy S3 via tapatalk 2
nicholi2789 said:
Okay. So you've installed the correct drivers for your phone as well right? It shows up as SCH-I535 on your computer?
Sent from my MOAR'D Galaxy S3 via tapatalk 2
Click to expand...
Click to collapse
Yes, it does indeed.
Did you uncheck Auto Reboot when you were supposed to?
darthsentinel said:
Normally, I wouldn't ask for help with a problem like this, but I'm rather concerned and could use assistance. Several days ago, I attempted to unlock and root my Verizon GS3. I followed the instructions from the XDA article, along with the ones provided in DroidModd3rX's YouTube video exactly on my VZW GS3, build JZO54K. I hard bricked my phone after flashing the VRALEC bootchain. It only showed up in the Device Manager on Windows 8 as QHSUSB_DLOAD. It was stuck like that as soon as I flashed the bootchain. Is there something I've done wrong that I could have done differently to prevent it from happening? I had just purchased it the day before, so I was able to get a replacement, but I'm highly interested in rooting my device (I've successfully rooted every other phone I've had) and want to ensure this doesn't happen again. Is it a problem with Windows 8, is it the build my phone is running on, or is it perhaps because I had USB Debugging checked on? I just find it odd that I've had this problem when I followed all the proper protocol. And yes, I did check the MD5, it was fine.
Click to expand...
Click to collapse
I have always followed the guide here. Not sure what version of the OS you have but I odin my phone back to the original factory and then run the root posted here http://forum.xda-developers.com/showthread.php?t=1762709
Super Interesting
I just received two phones from verizon and I followed the same exact instructions, on the first phone it worked like a charm. And on the second phone - at the very same step - it just blinked off and that was all she wrote. I tried a full power cycle, charging all night, and using the USB > PC connection to maybe kick it out of its funk. All I got was the QHSUSB_DLOAD popup when I plugged it in. Searching for that turns up a few things, but mostly for HTC phones. I also installed Keis and tried to redo all the driver junk with that, still nothing. So sad.
I have to ask the most obvious. Hows your battery? I thought I had hard bricked my device too one time and it was just a dead battery.
Sent from my SCH-I535 using xda premium
m-cat said:
I have to ask the most obvious? Hows your battery? I thought I had hard bricked my device too one time and it was just a dead battery.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
The battery was charging all night, I had meant to put this in an edit but had to wait five minutes and wandered off . I also forgot to add that it was a VZW SGS 3 running 4.1.2. I followed these (youtube DOT com SLASH watch?v=K4b9hcWHrW8) instructions. As I said before, it worked fine with the first phone. Second one died on the first step.
Anyways, my friend convinced me to just send it back. I'm not worried as the ROM and everything is stock.
a.demarco said:
Did you uncheck Auto Reboot when you were supposed to?
Click to expand...
Click to collapse
I didn't get to the point, it was hard bricked as soon as I flashed the VRALEC bootchain, which still said it needed auto-reboot checked.
khymbote said:
I have always followed the guide here. Not sure what version of the OS you have but I odin my phone back to the original factory and then run the root posted here http://forum.xda-developers.com/showthread.php?t=1762709
Click to expand...
Click to collapse
The version of the OS I had at the time was 4.1.2. Are you able to flash an earlier version of the OS through Odin?
m-cat said:
I have to ask the most obvious. Hows your battery? I thought I had hard bricked my device too one time and it was just a dead battery.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Sounds like the other guy here had the same problem. My battery was full at the time of flashing. And QHUSB_DLOAD is pretty much a sure sign of a hard brick and not a battery issue as far as I can tell.
Delete thanks
The version of the OS I had at the time was 4.1.2. Are you able to flash an earlier version of the OS through Odin?
Yes I have the OS from the initial release of the phone back in July of last year. I keep it just in case I need to factory restore my phone.
Related
I tried going back to gingerbread using Heimdall 1 click and it gives me a kernel error and failed. Now phone won't boot past the rogers logo. Any suggestions? No samsung screen. No green battery indicator when plugged in. Heimdall does detect the phone, and I've tried all USB ports and cords at my disposal. I use a mac so no access to odin. This is the first brick I haven't been able to get myself out of. Any help you would be appreciated
I am a gt i9000 owner, but can you get into download mode?
Sent by Santa Clause
If you can get download mode, then flash a gingerbread stock rom, even if it means you will lose root still do it, then flash a new rom of your choice, if you can get into download mode then you haven't got a brick
Sent by Santa Clause
Been bricked more than once...you have?
Embarking on a fresh new ROM without educating oneself can be very frustrating....since your on a Mac..with in the one click you say it reading your phone...can you get to download mode?
Pull battery
Plug in USB to phone
Hold both volume button
Pop battery back in
Do you see...the yellow Android digging?
http://forum.xda-developers.com/showthread.php?t=1293751
bigjoe2675 said:
Been bricked more than once...you have?
Embarking on a fresh new ROM without educating oneself can be very frustrating....since your on a Mac..with in the one click you say it reading your phone...can you get to download mode?
Pull battery
Plug in USB to phone
Hold both volume button
Pop battery back in
Do you see...the yellow Android digging?
Click to expand...
Click to collapse
I can get into download mode.heimdall detects my phone. I tried both qksters and adam outlers 1 click. neither would take. If I upgrade heimdall version (as it tells me its out of date) it wont get through the initial connection to the phone. if I use with out upgrade it continues to fail on kernel download.
This is my second brick (first one was when trying to root it on my mac) First brick was fixed through odin at my work. Unfortunately I don't want to wait till monday to have a functioning phone
teknhard said:
I can get into download mode.heimdall detects my phone. I tried both qksters and adam outlers 1 click. neither would take. If I upgrade heimdall version (as it tells me its out of date) it wont get through the initial connection to the phone. if I use with out upgrade it continues to fail on kernel download.
This is my second brick (first one was when trying to root it on my mac) First brick was fixed through odin at my work. Unfortunately I don't want to wait till monday to have a functioning phone
Click to expand...
Click to collapse
Hummmm..ok
Let's step back here does out prompt you for drivers?
....you might have to make a stop at your office..
Try different USB ports, I used heimdall yesterday to go back to gingerbread (so I could get the boot loaders) and I had the same problem as you, I finally got it to work with a different USB port and even then it kept failing...but I just kept trying and eventually it went through
(Pull battery, place battery back in, hold volume up and down, plug USB in-should put you in download mode...even if you can't see anything on your screen you can still enter download mode)
Sent from my SGH-I997 using XDA
DOesnt prompt me for drivers. It detects my phone and says ready to flash. I see the download mode screen. so its not completey screwed. Just can't get past the rogers logo.. I only have two USB on my macbook.. tried both quite a few times guess i'll mess with it some more. see if I can get it going. Thanks for the tips. ANy others ideas would also be appreciated
Alright, here it is:
I encountered the same problems yesterday, heimdall doesn't work when flashing back to stock from ics, from what I've found, you must use gtg's ultimate unbrick, the pit repartitions everything and also resets your binary counter (cha-ching! ). Once completed, your phone will reboot and be stuck at "...installing default apk files..." for a few minutes, don't panic, let it run its course. From there on, you can do the usual root/flash cwm deal. .
Sent from my SGH-I997 using Tapatalk 2 Beta-5
theROMinator said:
Alright, here it is:
I encountered the same problems yesterday, heimdall doesn't work when flashing back to stock from ics, from what I've found, you must use gtg's ultimate unbrick, the pit repartitions everything and also resets your binary counter (cha-ching! ). Once completed, your phone will reboot and be stuck at "...installing default apk files..." for a few minutes, don't panic, let it run its course. From there on, you can do the usual root/flash cwm deal. .
Sent from my SGH-I997 using Tapatalk 2 Beta-5
Click to expand...
Click to collapse
Funny I just did that yesterday using qkster heimdall after running the ics for the day....no issues utilizing it...so i say it does work...
theROMinator said:
Alright, here it is:
I encountered the same problems yesterday, heimdall doesn't work when flashing back to stock from ics, from what I've found, you must use gtg's ultimate unbrick, the pit repartitions everything and also resets your binary counter (cha-ching! ). Once completed, your phone will reboot and be stuck at "...installing default apk files..." for a few minutes, don't panic, let it run its course. From there on, you can do the usual root/flash cwm deal. .
Sent from my SGH-I997 using Tapatalk 2 Beta-5
Click to expand...
Click to collapse
I went back to stock from ics yesterday using heimdall...just took a long time and a lot of tries
I really think it depends on the computer though, for some Odin works best...for others heimdall works best
Sent from my SGH-I997 using XDA
bigjoe2675 said:
Funny I just did that yesterday using qkster heimdall after running the ics for the day....no issues utilizing it...so i say it does work...
Click to expand...
Click to collapse
I did not mean to be misleading, as you both have said, either or may work, I simply wanted to share my experience
mg2195 said:
I went back to stock from ics yesterday using heimdall...just took a long time and a lot of tries
I really think it depends on the computer though, for some Odin works best...for others heimdall works best
Sent from my SGH-I997 using XDA
Click to expand...
Click to collapse
Sent from my SGH-I997 using Tapatalk 2 Beta-5
mg2195 said:
I went back to stock from ics yesterday using heimdall...just took a long time and a lot of tries
I really think it depends on the computer though, for some Odin works best...for others heimdall works best
Sent from my SGH-I997 using XDA
Click to expand...
Click to collapse
Agreed. On my desktop (quad core 6 gb ram, watercooled blablablabl) can't run heimdal nor Odin to save its life.
My netbook (single core atom) took me back from CM9 with Odin like it was nothing.
My 7 year old laptop (running Ubuntu) works great using Heimdal (just run the .jar file as an executable)
theROMinator said:
I did not mean to be misleading, as you both have said, either or may work, I simply wanted to share my experience
Sent from my SGH-I997 using Tapatalk 2 Beta-5
Click to expand...
Click to collapse
No ... understood..no worries...there are some many that have never flashed or much less read anything regarding flashing are having so many prob`s...when this ics it's still bring birthed...for the infuse.
Instead of going to the dev section and doing some home work...understanding the basic info....they see ICS and have pictures of Sunday treats....in their mind...having no clue about the current ROM they are on now...Then the questions pop up...from individuals...after wards yelling SOS...But hey it's their phone.
bigjoe2675 said:
No ... understood..no worries...there are some many that have never flashed or much less read anything regarding flashing are having so many prob`s...when this ics it's still bring birthed...for the infuse.
Instead of going to the dev section and doing some home work...understanding the basic info....they see ICS and have pictures of Sunday treats....in their mind...having no clue about the current ROM they are on now...Then the questions pop up...from individuals...after wards yelling SOS...But hey it's their phone.
Click to expand...
Click to collapse
I've flashed lots of roms and never had any issues. Also looked through the forum and know the basics about getting back to stock. I'm no expert, but I have a decent idea what I'm doing. I do appreciate a forum you can ask questions though and have people help out when your stumped. I did what i could from the tools I have at my disposal here, and ran into some problems. I'm not yelling SOS, just asking for some tips as what I have tried hasn't worked. All the same I do appreciate everyones opinions and help they provide. THat's what makes this forum great.
why would you need to heimdall if you are on a rogers infuse? Isn't that for AT&T phones only?
teknhard said:
I've flashed lots of roms and never had any issues. Also looked through the forum and know the basics about getting back to stock. I'm no expert, but I have a decent idea what I'm doing. I do appreciate a forum you can ask questions though and have people help out when your stumped. I did what i could from the tools I have at my disposal here, and ran into some problems. I'm not yelling SOS, just asking for some tips as what I have tried hasn't worked. All the same I do appreciate everyones opinions and help they provide. THat's what makes this forum great.
Click to expand...
Click to collapse
I apologize wasn't directed to you just in general and your correct this forum is great...
Then reflash ics lol
Sent from my SGH-I997 using xda premium
threi_ said:
why would you need to heimdall if you are on a rogers infuse? Isn't that for AT&T phones only?
Click to expand...
Click to collapse
Because I don't have access to a PC for Odin, and the at&t should work to get me out of brick state. I currently can't get past rogers boot screen
GoSooners345 said:
Then reflash ics lol
Sent from my SGH-I997 using xda premium
Click to expand...
Click to collapse
I don't have recovery.. otherwise I certainly would have
Hi,
My captivate is totally bricked, HF bricked, doesn't response to any key, no light, no screen, nothing.
The sequence of events:
Former rom: myui ics - bad performance: freezing, FC
Flashed gingerbread 2.3.3 (I897UCKF1 Odin-1-Click) - worked fine.
Flashed speedmod-kernel-i897-k13e-500hz to get cm recovery full options - finished successfully but phone wouldnt go beyond samsung boot screen (before AT&T logo). I took off battery and went into recovery mode:
Installed perception rom zip file.
finished successfully,
reboot,
never woke up ever since.
Nothing helped.
I figured it's hard bricked so I tried the unbrick HW method specified here:
http://forum.xda-developers.com/showthread.php?t=1206216
I did it in professional lab exactly like the instructions.
nothing changed - the phone doesn't respond to anything.
Is there anything in the sequence I specified above which can explain what happened?
Is there any method which will unbrick the phone?
So you are saying.. turning on the power or plugging the phone in causes nothing to show up?
korockinout13 said:
So you are saying.. turning on the power or plugging the phone in causes nothing to show up?
Click to expand...
Click to collapse
Nothing.
Nada.
Sent from my GT-I9100 using XDA
There is no way that flashing a ROM zip HARD bricked your phone. That isn't possible, CWM doesn't have access to the bootloaders on any SGS device...
eitan123 said:
Nothing.
Nada.
Sent from my GT-I9100 using XDA
Click to expand...
Click to collapse
The unbrickablemod you linked to is the only way. Did you follow the directions on running it? http://forum.xda-developers.com/showthread.php?t=1242466
Swyped from my ICS Samsung Captivate
korockinout13 said:
The unbrickablemod you linked to is the only way. Did you follow the directions on running it? http://forum.xda-developers.com/showthread.php?t=1242466
Swyped from my ICS Samsung Captivate
Click to expand...
Click to collapse
I've tried the windows one click soft unbrick - it didnt' recognize the phone.
http://forum.xda-developers.com/showthread.php?t=1153310
I've also tried the method mentioned above throug linux and almost ended up burning my pc.
The first time in my life I got thermal trip was with this crappy ubuntu (worked for 30 minutes and almost got my proccessor on fire).
Not to mention I wasn't able to install Java.
But I did find a one click version for windows - It didnt work.
BTW, is it possible that I dont even see any charging animation?
I remember there was such animation when the phone was off.
eitan123 said:
....
BTW, is it possible that I dont even see any charging animation?
I remember there was such animation when the phone was off.
Click to expand...
Click to collapse
That means you are Hard Bricked. It will require other means than Odin or Heimdall to recover it.
Since we are not supposed to link to paid services/sites I'll just put this here:
http://lmgtfy.com/?q=Samsung+Captivate+UnBrickable+MOD+++Repair
Red_81 said:
That means you are Hard Bricked. It will require other means than Odin or Heimdall to recover it.
Since we are not supposed to link to paid services/sites I'll just put this here:
http://lmgtfy.com/?q=Samsung+Captivate+UnBrickable+MOD+++Repair
Click to expand...
Click to collapse
He's already applied that. He just needs to run the resurrector on Linux.
You cannot flash anything else. It won't work. You NEED to revive the phone first
Swyped from my ICS Samsung Captivate
Wow.... I really need more coffee today. I apologize.
korockinout13 said:
He's already applied that. He just needs to run the resurrector on Linux.
You cannot flash anything else. It won't work. You NEED to revive the phone first
Swyped from my ICS Samsung
So, is there a point running the ressurector from Linux?
What do you mean by revive it first?
I'm having hard times installing Linux and then java in it.
And I'm working in Linux environment.
Sent from my GT-I9100 using XDA
Click to expand...
Click to collapse
eitan123 said:
korockinout13 said:
He's already applied that. He just needs to run the resurrector on Linux.
You cannot flash anything else. It won't work. You NEED to revive the phone first
Swyped from my ICS Samsung
So, is there a point running the ressurector from Linux?
What do you mean by revive it first?
I'm having hard times installing Linux and then java in it.
And I'm working in Linux environment.
Sent from my GT-I9100 using XDA
Click to expand...
Click to collapse
Based on the directions, it seems that you need Linux. I find it really easy to use the Ubuntu windows installer. It doesn't mess with partitions and is easy to uninstall. What are you having problems with?
All I'm trying to say about reviving is the fact that Odin or Heimdall will do nothing until you run the unbrickablemod program
Swyped from my ICS Samsung Captivate
Click to expand...
Click to collapse
Maybe I'm missing something.
I booted from Linux CD and ran resscuration.
It didn't recognize the phone.
An I doing it correctly?
Btw, out was easy installing Ubuntu.
The problem was I got CPU thermal trip and forced shut down.
Sent from my GT-I9100 using XDA
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
Just rooted my new SGS3 using New Root Method Released for Verizon’s Galaxy S3, No Odin Required. i did the data & kelvic wipe then install Clean Rom 5.0. All progressed without a hitch. Even backed up with CWM prior to flash.
I rebooted into the new rom and got this: System software not authorized by Verizon Wireless... rebooted several time with same result.
What can I do now? Thanks for your help.
Just a wild guess, but me thinks your bootloader is still locked! But I'm not sure that will even apply because I rooted my device before unlocking the bootloader. But I rooted my device via ODIN first.
You can try EZ-Unlock via the Market. The GUI is still very buggy and will show the status as unknown but the internal workings of the app works good.
You got nothin to loose in trying. Go back to stock and give it another whirl after you've unlocked the bootloader.
Of that fails then I would suggest using the tried and true method..ODIN.
G'luck!
yup your bootloader is still locked
check the downloads thread and use version 1.2.
That means your boatloader is locked. You now must Odin back to stock and start over. Droid style has a guide stickied in the development thread. Follow section 6 of it.
Next time use ez unlock version 1.2 to unlock you boatloader.
Sent from my SGS3 running Eclipse 2.1
downloads list
http://forum.xda-developers.com/showthread.php?t=1850506
tekrhino said:
Just a wild guess, but me thinks your bootloader is still locked! But I'm not sure that will even apply because I rooted my device before unlocking the bootloader. But I rooted my device via ODIN first.
You can try EZ-Unlock via the Market. The GUI is still very buggy and will show the status as unknown but the internal workings of the app works good.
You got nothin to loose in trying. Go back to stock and give it another whirl after you've unlocked the bootloader.
Of that fails then I would suggest using the tried and true method..ODIN.
G'luck!
Click to expand...
Click to collapse
Thanks. I can't get past the warning dialogue screen. Pulled the battery, no good. PC can't see the phone with USB.
Prophotog said:
Thanks. I can't get past the warning dialogue screen. Pulled the battery, no good. PC can't see the phone with USB.
Click to expand...
Click to collapse
Yikes, ok
You have to get into DOWNLOAD MODE.. Power+ Volume Down+ Home key at the same time after a fresh battery pull.
Do a search on the Development forum to set up Odin on your PC.
YOU Must FOLLOW directions EXACTLY our you will have very expensive BRICK!
This forum could help:
http://forum.xda-developers.com/showthread.php?t=1762709
Or even better, this one:
http://forum.xda-developers.com/showthread.php?t=1840030
tekrhino said:
Yikes, ok
You have to get into DOWNLOAD MODE.. Power+ Volume Down+ Home key at the same time after a fresh battery pull.
Do a search on the Development forum to set up Odin on your PC.
YOU Must FOLLOW directions EXACTLY our you will have very expensive BRICK!
This forum could help:
http://forum.xda-developers.com/showthread.php?t=1762709
Or even better, this one:
http://forum.xda-developers.com/showthread.php?t=1840030
Click to expand...
Click to collapse
Thanks to everyone!! Looks to be a long night. :>)
tekrhino said:
Yikes, ok
You have to get into DOWNLOAD MODE.. Power+ Volume Down+ Home key at the same time after a fresh battery pull.
Do a search on the Development forum to set up Odin on your PC.
YOU Must FOLLOW directions EXACTLY our you will have very expensive BRICK!
This forum could help:
http://forum.xda-developers.com/showthread.php?t=1762709
Or even better, this one:
http://forum.xda-developers.com/showthread.php?t=1840030
Click to expand...
Click to collapse
I lol'ed at your post. A little dramatic, don't you think? He's not even close to bricked. Just Odin from download mode back to stock, and redo the steps with bootloader unlock.
Here is a gift (working ez-unlock v1.2)
http://dl.dropbox.com/u/42057363/com.mmmeff.ez.unlock_3.apk
@Techsavvy
Yeah, perhaps a tad overdone on the theatricals.
Cut me some slack, I'm taking acting classes..lol
And... I know... I know..don't quit my day job!
Still having issues. I "think" I am in the download mode. Screen says Downloading.... It has Odin in red in top left corner. Device connects with Odin. BUT I am not getting a PASS message when flashing VRALEC bootchain. Last text line in Odin is: <OSM> Leave CS...
I have tried several attempts.
Suggestions?
Prophotog said:
Still having issues. I "think" I am in the download mode. Screen says Downloading.... It has Odin in red in top left corner. Device connects with Odin. BUT I am not getting a PASS message when flashing VRALEC bootchain. Last text line in Odin is: <OSM> Leave CS...
I have tried several attempts.
Suggestions?
Click to expand...
Click to collapse
No need to do the boot chains. Just follow section 5 of this guide and I recommend root 66 for the ROM you flash
http://forum.xda-developers.com/showthread.php?p=28530394
Sent from my SGS3 running Eclipse 2.1
tekrhino said:
@Techsavvy
Yeah, perhaps a tad overdone on the theatricals.
Cut me some slack, I'm taking acting classes..lol
And... I know... I know..don't quit my day job!
Click to expand...
Click to collapse
I appreciate the theatricals...however, I am having issues with Odin. Can't get the Pass message. I assume the "Downloading..." text means I'm in the download mode. Tried several attempts. I AM glad I'm not close to bricked too! Can't afford $600 or a divorce. Might have to sell a camera instead.
Prophotog said:
Just rooted my new SGS3 using New Root Method Released for Verizon’s Galaxy S3, No Odin Required. i did the data & kelvic wipe then install Clean Rom 5.0. All progressed without a hitch. Even backed up with CWM prior to flash.
I rebooted into the new rom and got this: System software not authorized by Verizon Wireless... rebooted several time with same result.
What can I do now? Thanks for your help.
Click to expand...
Click to collapse
And just for future reference, it's Dalvik, not Kelvic
Sent from my SCH-I535 using xda app-developers app
Prophotog said:
I appreciate the theatricals...however, I am having issues with Odin. Can't get the Pass message. I assume the "Downloading..." text means I'm in the download mode. Tried several attempts. I AM glad I'm not close to bricked too! Can't afford $600 or a divorce. Might have to sell a camera instead.
Click to expand...
Click to collapse
Just a heads up. You can get a real brick with Odin and easy. Follow the guide I linked earlier to a t and you'll be fine
Sent from my SGS3 running Eclipse 2.1
kintwofan said:
Just a heads up. You can get a real brick with Odin and easy. Follow the guide I linked earlier to a t and you'll be fine
Sent from my SGS3 running Eclipse 2.1
Click to expand...
Click to collapse
You are a scholar and a gentleman!! THANK YOU very much. You can have a portrait session on me any time. Name the time and place.
Prophotog said:
You are a scholar and a gentleman!! THANK YOU very much. You can have a portrait session on me any time. Name the time and place.
Click to expand...
Click to collapse
Cool, I take it you're up and running again. Just make sure you use ez unlock 1.2 next time. And the positive is you're an Odin pro now!
Sent from my SGS3 running Eclipse 2.1
Hi, I have a Verizon S3 flashed to Boost Mobile. I tried to gain root by flashing a stock rooted Rom and messed up the flash. I had to take it back to be flashed again  Now I'm more cautious before hand. I should have backed it up before attempting it, I know I know lol can anyone shed some light on how to update a flashed phone as well as how to root it. I could really use the help 
Also after I messed up the boost flash I paniced and flashed a sprint kernel hoping this would fix the problem. Since then anything that I've tried to view including taking camera shots and web browsing if done in landscape mode will be upside down, any remedy for this problem? I know now... root first, flash later. 
Sent from my SPH-L710 using XDA HD
Alex0826 said:
Hi, I have a Verizon S3 flashed to Boost Mobile. I tried to gain root by flashing a stock rooted Rom and messed up the flash. I had to take it back to be flashed again  Now I'm more cautious before hand. I should have backed it up before attempting it, I know I know lol can anyone shed some light on how to update a flashed phone as well as how to root it. I could really use the help 
Also after I messed up the boost flash I paniced and flashed a sprint kernel hoping this would fix the problem. Since then anything that I've tried to view including taking camera shots and web browsing if done in landscape mode will be upside down, any remedy for this problem? I know now... root first, flash later. 
Sent from my SPH-L710 using XDA HD
Click to expand...
Click to collapse
Sprint kernel is causing the inversion. Flash a vzw kernel. Read first flash later.
Sent from my SCH-I535 using xda app-developers app
Who ever did your flash might not done it right cause ya not supposed to lose a flash like that unless he didn't do things right. I can factory reset mine and I wont loose flash
Sent from my SPH-L900 using Tapatalk 2
Before you post, "BLAKDSKF READ OTHER FORUMS BLUSDFLU!!!!!!!111!!!", please, PLEASE, read the whole post. I am not illiterate or a fool. I've spent the last few days researching similar posts, both on xda and other sites, and as far as I've found, this is the only post of this kind on the Verizon SGSIII forums, though there are some that are somewhat similar in the other SGSIII forums (though I think the root of the problem is different). If you can prove me wrong, please redirect.
The Long Story:
ok. SO. I was trying to root my SGSIII, unlock the bootloader, and install CM10. Simple enough, right? Not so. I got through the rooting tutorial at Link 1 relatively smoothly. For the record, I did the composite root and bootloader combo, and I installed CWM Touch Recovery, as per the guide. I also restored the Jellybean Bootchain. I think it was at this point I downloaded Titanium Backup (because forethought is not my forte) and backed up all my apps. I also made a backup with CWM Recovery, but there were errors. I forget the reason, but it aborted backup. I then tried to make a backup onto my external sd card, and some other errors popped up. Mainly that it couldn't find /android.secure (something along those lines) or /sd-ext (might have been something else. I'm going off memory) and skipped them. It still made the backup, so my illiterate, foolish self decided to roll with it and go ahead.
I then went ahead to Link 2, and with it being 2 AM, I stupidly decided to screw trying to figure out how to use Heimdall 1.4rc1 and continue to use ODIN for flashing. After all what's the difference, I thought. One flashing program is the same as another. I flashed the first two files. Well, in truth, I'm not sure if I flashed the first file. Since I just made a single folder for all the SGSIII Verizon flashing stuff, I had two files with similar names at the time. One from Link 1 and one from Link 2. The only difference was one was a boot chain, the other was a boot loader. Also, one ended with .md5 while the other ended with .tar. Sadly I tiredly picked one and flashed it. I think it was the .md5 one, but I'm not sure. Around this point, my micro sd card reader broke, so I decided to just use my other phone (Motorola Photon 4g running Joker's CM9) as a reader of sorts. I swapped them, used my phone to put the zip from Link 2 on it, and swapped them back. I say this because I'm not sure if that is what broke my md5sums or not (more on that in a sec).
Well, surprise, surprise, my phone got stuck on the animated, colorful "4G LTE" boot screen, except it was fully black, though the noise was playing. I think to myself, "No biggie. I'll just restore my previous backup," so I go back to restore it when I get the error 'md5sum mismatch'. I look up the problem, and after extensive, 3AM research (read: clicked the first link on google and blindly followed), I went with one guys advice, which was to create a blank nandroid.md5 file to force the restore. I figured, "Hey. This is pretty risky. I think I'll just restore the bootloader instead of the whole restore." Or at least that's what was going through my head as I went through with restoring the whole backup. Lo and behold, /system was corrupted, I assume, and it aborted restoring it. I reboot my phone only to find out that my phone gets stuck on the SGSIII boot logo. This is where I am now. I would go through with flashing a stock rom onto it to undo everything I've done, but ODIN won't recognize my phone anymore. I can still get into Download and Recovery Mode. All my backups are useless at the moment.
In Short:
I tried to root, unlock the bootloader, and flash CM10 on it
I messed up and ended up restoring a broken backup, md5sums be screwed.
Now ODIN won't recognize my phone and it's stuck at the SGSIII boot screen.
Is there any way to fix this or at least return it back to stock so I can start again?
If there's any other information you need, just ask. I'd be happy to give it. :laugh: This is my first post on these forums, so I'm not sure what information is standard. If you have any idea of what it might be, please drop a comment or something rather than just leaving. I'd like to know that people are actually reading this post.
And on an unrelated note, every time I try to flash with Heimdall, I get an error about there not being a certain .dll file, even though I downloaded the package from Link 2. Am I doing something wrong?
EDIT: I've already tried factory resetting and wiping the cache/dalvik cache. Most of my info is backed up anyway.
Links:
Link 1: http://forum.xda-developers.com/showthread.php?t=2046439
Link 2: http://wiki.cyanogenmod.org/w/Install_CM_for_d2vzw
What happens when you plug your phone into your PC? Have you tried deleting the drivers then reinstalling them either from Samsung or from the Kies program? You really have to try to mess up this phone and it seems like you definitely tried very hard in this regard.
Edit: Idk anything about Heimdall, I use Odin only so I can't help you there.
SlimSnoopOS said:
What happens when you plug your phone into your PC? Have you tried deleting the drivers then reinstalling them either from Samsung or from the Kies program? You really have to try to mess up this phone and it seems like you definitely tried very hard in this regard.
Edit: Idk anything about Heimdall, I use Odin only so I can't help you there.
Click to expand...
Click to collapse
I hadn't noticed before, but my phone doesn't even show a charge screen when plugged in, but that might just be the settings on the phone pre-root. I'm not sure because I left the phone on to see if it was just a time thing. The phone died and I have to recharge it.
After goofing around with the phone while on the charger for a while, I can get a charge screen to show up for a second. The standard "battery with a loading circle" type symbol for this type of error.
I just reinstalled the drivers. I'll let the phone charge for about 10 minutes or so, then test the phone.
dudeman9199 said:
I hadn't noticed before, but my phone doesn't even show a charge screen when plugged in, but that might just be the settings on the phone pre-root. I'm not sure because I left the phone on to see if it was just a time thing. The phone died and I have to recharge it.
After goofing around with the phone while on the charger for a while, I can get a charge screen to show up for a second. The standard "battery with a loading circle" type symbol for this type of error.
I just reinstalled the drivers. I'll let the phone charge for about 10 minutes or so, then test the phone.
Click to expand...
Click to collapse
Well if it died you should leave it on the charger longer than ten minutes if it is charging. If Odin recognizes it, your first step would be to try flashing a stock image.
SlimSnoopOS said:
Well if it died you should leave it on the charger longer than ten minutes if it is charging. If Odin recognizes it, your first step would be to try flashing a stock image.
Click to expand...
Click to collapse
Thanks. It would seem that it now recognizes the phone, from what I can tell. As soon as I get a stock rom, I'll flash it and post an update.
dudeman9199 said:
Thanks. It would seem that it now recognizes the phone, from what I can tell. As soon as I get a stock rom, I'll flash it and post an update.
Click to expand...
Click to collapse
Great! Use Droidstyle's guide or MrRobinson's thread for the proper images. Should be a good starting point.
Sent from my SCH-I535 using xda app-developers app
I just wanted to add that THIS is how you do a first post or any help needed post! Great details and is obvious you researchedyour problem as well.
The errors in cwm are actually normal. I think the corrupt backups are unrelated.
Sent from my SCH-I605 (AKA NOTE 2)
SlimSnoopOS said:
Great! Use Droidstyle's guide or MrRobinson's thread for the proper images. Should be a good starting point.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Thanks. I've finally booted up into the setup wizard. I guess from here on I can re-root, unlock the bootloader, and *hopefully* get a working backup and eventually flash CM10.
I guess this means Problem Solved? Again, Thanks.
kintwofan said:
I just wanted to add that THIS is how you do a first post or any help needed post! Great details and is obvious you researchedyour problem as well.
The errors in cwm are actually normal. I think the corrupt backups are unrelated.
Sent from my SCH-I605 (AKA NOTE 2)
Click to expand...
Click to collapse
Thanks. I'm just gonna assume that the problems stemmed from swapping the sd card and leave it at that.
dudeman9199 said:
Thanks. I've finally booted up into the setup wizard. I guess from here on I can re-root, unlock the bootloader, and *hopefully* get a working backup and eventually flash CM10.
I guess this means Problem Solved? Again, Thanks.
Thanks. I'm just gonna assume that the problems stemmed from swapping the sd card and leave it at that.
Click to expand...
Click to collapse
Perfect! Which thread did you end up using btw?
Sent from my SCH-I535 using xda app-developers app
SlimSnoopOS said:
Perfect! Which thread did you end up using btw?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I used droidstyle's thread for getting the stock rom.