Database Info

What exactly bricks a Captivate?

Hi, I've had the glorious captivate for a few weeks now and I constantly read this forum. I am now ready to flash my phone and while I am not really afraid to do it, since I used to flash my Nokia 5800 every week, I wonder what is it during the process of flashing and loading a new rom that can cause the phone to get bricked? Are some parts riskier than others? Is there some common mistake or error or something people usually forget that kills it?
I'd appreciate some answers, since I love my phone and would hate to brick it.
Thank you very much! XDA rules!
Sent from my SAMSUNG-SGH-I897 using XDA App

rufex2001 said:
Hi, I've had the glorious captivate for a few weeks now and I constantly read this forum. I am now ready to flash my phone and while I am not really afraid to do it, since I used to flash my Nokia 5800 every week, I wonder what is it during the process of flashing and loading a new rom that can cause the phone to get bricked? Are some parts riskier than others? Is there some common mistake or error or something people usually forget that kills it?
I'd appreciate some answers, since I love my phone and would hate to brick it.
Thank you very much! XDA rules!
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
If you test the phone to make sure it can accept the button combinations to go into download mode (almost all do, except for a batch of faulty ones), there is almost nothing you can do that will truly "brick" the phone. A bad or interrupted flash will result in a boot loop, which you can recover from by forcing download mode, and using Odin to reflash back to stock.

Flashing the first and second bootloaders would be the most dangerous, which is why the Odin one-click flasher is so bad. Also, the USB connection is a prime source of failure which is another reason to avoid Odin. So, if you have working button combos you are pretty unlikely to brick the phone as long as you avoid unnecessarily using any version of Odin.
Note: DesignGears includes sbl.bin (the second bootloader) in his ROMs, but since you aren't flashing it via USB it's relatively safe and it does have the side-effect of fixing you button combos if they aren't working. On the other hand, if you aren't using the one-click then you probably already have a good sbl.bin and so it's not needed.

Basically what causes a brick in any electronic equipment is from an interruption/error in any boot critical files. The item does not have the proper/complete instruction to turn on. You could say it is like starting a car being told to first put the key in
Sent from my SAMSUNG-SGH-I897 using XDA App

If you can use the 3 button combos to get into download or recovery mode, you are good to go. The only danger would be a bad Odin flash, but even so you'll have a chance to recover it by making a cheap USB jig (3 100k Ohm resistors into pins 3 and 4, I think, of the usb port) or buying one. This will boot the phone straight into Download mode.
When using Odin, there is only one stage where you can brick your phone for good, during the bootloader copy process, which probably takes less than a second.

Thanks for the replies! I just tried it and I got the 3 button into download mode combo, so that's great! Now, what other options do I have for flashing besides Odin? Apparently Odin is not the safest, huh? And is there a way to make the bootloader writing stage less risky?
Also, my Captivate is a 1007 build. Is that a good thing or a bad thing?
Thanks, again!
Sent from my Samsung Captivate using the XDA App

rufex2001 said:
Thanks for the replies! I just tried it and I got the 3 button into download mode combo, so that's great! Now, what other options do I have for flashing besides Odin? Apparently Odin is not the safest, huh? And is there a way to make the bootloader writing stage less risky?
Also, my Captivate is a 1007 build. Is that a good thing or a bad thing?
Thanks, again!
Sent from my Samsung Captivate using the XDA App
Click to expand...
Click to collapse
My Cappy is a 1007 build, too. I've soft bricked my phone more times than I can count, but Odin hasn't had anything to do with it. It can do it, though.
At one time in my life I flashed a new ROM every day, and I used Odin every time before I flashed.
On a side note, back when I flashed my first ROM, I pulled the battery during the first boot, dropped it, and then flashed another ROM without using Odin, and it never bricked it, so that should give you a good idea of how hard it is to brick these phones. Lol

Stupidity.
Sent from my Captivate.

opcow said:
Flashing the first and second bootloaders would be the most dangerous, which is why the Odin one-click flasher is so bad. Also, the USB connection is a prime source of failure which is another reason to avoid Odin. So, if you have working button combos you are pretty unlikely to brick the phone as long as you avoid unnecessarily using any version of Odin.
Note: DesignGears includes sbl.bin (the second bootloader) in his ROMs, but since you aren't flashing it via USB it's relatively safe and it does have the side-effect of fixing you button combos if they aren't working. On the other hand, if you aren't using the one-click then you probably already have a good sbl.bin and so it's not needed.
Click to expand...
Click to collapse
I didn't realize Odin one click was so bad. I have been using Odin3 one click routinely now for a couple weeks as I flash back and forth trying out all these great ROMs to see what I like and so far (knock on wood I guess?) I haven't had any problems at all.
So, now that I have used Odin one click many times over, does my Cappy now have a bad sbl.bin?

No odin really is not that bad just don't unplug it while it is running. You would not want to unplug your computer when flashing a new bios
Sent from my SAMSUNG-SGH-I897 using XDA App

Right, so if not Odin, what can I use for flashing? Can I do it all with the sdk using adb?
Also, I've been going through the guides and other stickies and apparently Odin is necessary only to flash back to stock. For rooting and installing new roms only the update.zip file and clockwork recovery are necessary. Could you do the same procedure to flash back to stock?
Sorry for any dumb or repeated question I may be asking.
Sent from my SAMSUNG-SGH-I897 using XDA App

Pierce533 said:
I didn't realize Odin one click was so bad. I have been using Odin3 one click routinely now for a couple weeks as I flash back and forth trying out all these great ROMs to see what I like and so far (knock on wood I guess?) I haven't had any problems at all.
So, now that I have used Odin one click many times over, does my Cappy now have a bad sbl.bin?
Click to expand...
Click to collapse
Odin isn't bad so much as an unnecessary risk. There are a lot of potential causes of failure: user error, accidents, flakey USB ports or software from other vendors that interferes with your drivers. The there the fact that people use the one-click and lose their button combos or brick their phone by using the one-click on a 1010+ build. I can safely odin flash all day if I need to, but there's just no reason to. And if you look around these forums you will see a lot of people crying after an odin mishap.

rufex2001 said:
Right, so if not Odin, what can I use for flashing? Can I do it all with the sdk using adb?
Also, I've been going through the guides and other stickies and apparently Odin is necessary only to flash back to stock. For rooting and installing new roms only the update.zip file and clockwork recovery are necessary. Could you do the same procedure to flash back to stock?
Click to expand...
Click to collapse
I keep a CWM update.zip on my sdcard for reinstalling CWM and I flash my ROMs with CWM. I also keep a couple of spare know good ROM zips on the sdcard to go back to in case something goes wrong with a new install.

opcow said:
Odin isn't bad so much as an unnecessary risk. There are a lot of potential causes of failure: user error, accidents, flakey USB ports or software from other vendors that interferes with your drivers. The there the fact that people use the one-click and lose their button combos or brick their phone by using the one-click on a 1010+ build. I can safely odin flash all day if I need to, but there's just no reason to. And if you look around these forums you will see a lot of people crying after an odin mishap.
Click to expand...
Click to collapse
Thanks for the info. Is there a stock I897UCJF6 ROM that can be flashed with CWM? I haven't been able to find one and if there is one I would like to have one around to use. Thanks for taking the time to answer my questions.

opcow said:
I keep a CWM update.zip on my sdcard for reinstalling CWM and I flash my ROMs with CWM. I also keep a couple of spare know good ROM zips on the sdcard to go back to in case something goes wrong with a new install.
Click to expand...
Click to collapse
That is exactly the sort of thing I had in mind! So I guess I could keep a CWM update.zip and a stock rom update.zip and some custom roms and just do everything directly from the phone and without Odin, right? Or am I missing something?
Sent from my SAMSUNG-SGH-I897 using XDA App

Guns don't kill people

opcow said:
Odin isn't bad so much as an unnecessary risk. Then there the fact that people use the one-click and lose their button combos or brick their phone by using the one-click on a 1010+ build.
Click to expand...
Click to collapse
Yep. I have build 1008 that has always had the 3-button combo and lost it after using ODIN 1-click (I restored the combo with a later flash).
I believe opcow and others when they say that flashing back to stock is unnecessary. I just don't understand why the authors of some of these ROMs leave this as part of their installation guide.
Sent using XDA App

Pay close attention to the options in recovery when you are using a custom rom. It's part of the custom kernal, and of used properly can help you avoid odin. I avoid it because I have a mac and odin won't run on anything but windows. Custom recovery will allow you to format every part of the OS but the sbl.bin. Also in some custom recoveries there is an option to mount usb. This will allow you to format the internal sd then copy a new rom.zip and flash if you really want a clean flash. If your doing this make sure you are able to mount your sd before you format anything. Avoid stock 2.2 kernals because they have 3e recovery. There are ways around that but they have to be in play before you end up in a bootloop.
3e recovery + bootloop= odin recovery "only option".
Make sure lag fix for rom kernal A understands lag fix for rom kernal B. Also usually only a concern for stock 2.2 kernal. Other than that really hard to brick this phone.
Sent from my SAMSUNG-SGH-I897 using XDA App

As long as you keep a CWM update.zip and a ROM on your internel sdcard at all times, I see no reason why you would ever have to use odin 1-click.
I get bootloops all the time, just pull the battery and then use vol up + vol down + pow to enter recovery to flash the ROM back. Make sure it's a wipe ROM.
If it's not a soft-brick, then you will need odin.

ryude said:
As long as you keep a CWM update.zip and a ROM on your internel sdcard at all times, I see no reason why you would ever have to use odin 1-click.
I get bootloops all the time, just pull the battery and then use vol up + vol down + pow to enter recovery to flash the ROM back. Make sure it's a wipe ROM.
If it's not a soft-brick, then you will need odin.
Click to expand...
Click to collapse
Could you please explain what a wipe ROM is? Thanks

From bricked to fixed.

I was caught in a boot loop and tried to re flash, when in my haste I forgot that Odin will recheck partition when loading .Pit files (pretty lame feature)
Still it was my fault for clicking start in haste.
**phone was partitioned, and would not go into download mode, it was stuck in a screen that said "Firmware update error, please restore in Kies", but it wouldn't connect to kies**
I sent my phone to XDA member Connexion2005
http://forum.xda-developers.com/member.php?u=1602851
I haven't got it in my hands yet, but he just told me it was fixed, I can't wait to get it back and leave it the hell alone (until someone makes CM7 or better work on it)
anyhow, this is out there so if you do what I did (DON'T) there's a solution. Set me back $50 plus shipping to TX from NYC but still, I didn't have to get a whole new phone.

for 50 bucks im sure k0nane would have made an uberfixit tar :/

shabbypenguin said:
for 50 bucks im sure k0nane would have made an uberfixit tar :/
Click to expand...
Click to collapse
Absolutely.

shabbypenguin said:
for 50 bucks im sure k0nane would have made an uberfixit tar :/
Click to expand...
Click to collapse
Please elaborate. Not finding much info on this "uberfixit", but it sounds like it's some method of re-creating the stock filesystem that's flashable in odin?

I was putting this out there, because I'm not the only one that this will happen to.

yea it happens when you repartition, an uberfixit requires a complete dump of the phone and quite a bit of time, but will completely fix what you described
the problem with repartitioning is that it wipes the phone clean and then starts to reinstall everything, problem is neither one of teh tars has the full dump (we do it for the sake of saving actual bricks)
knowing someone who can jtag is great we have had a few epic 4g touches that crashed and burned and were saved via jtag.

shabbypenguin said:
yea it happens when you repartition, an uberfixit requires a complete dump of the phone and quite a bit of time, but will completely fix what you described
the problem with repartitioning is that it wipes the phone clean and then starts to reinstall everything, problem is neither one of teh tars has the full dump (we do it for the sake of saving actual bricks)
knowing someone who can jtag is great we have had a few epic 4g touches that crashed and burned and were saved via jtag.
Click to expand...
Click to collapse
You may not remember, but I did go onto your IRC and spoke with you regarding this issue.

oh sorry, the irc channel we have is for a bunch of devices currently we house blaze 4g, attain 4g, conenct 4g, lucid and optimus m+ owners. so i probably thought you were an attain owner since we have had a good number of attain owners repartition as well :/

shabbypenguin said:
oh sorry, the irc channel we have is for a bunch of devices currently we house blaze 4g, attain 4g, conenct 4g, lucid and optimus m+ owners. so i probably thought you were an attain owner since we have had a good number of attain owners repartition as well :/
Click to expand...
Click to collapse
it's all good, bottom line is I f'd up my device, but now its fixed.

um...yeah...
So i did the exact same thing as you... Been trying to find anyone who can help me out. Is there anyway I can fix it myself? I haven't found a single place in my whole state that can fix the problem. If at all possible, I'd like to avoid sending it out for repair.

So how do I get this uberfixit?
I stupidly re-partitioned using Odin, also: I did not realize that Odin re-checked the check box -even after unchecking- when a new pda file was loaded. My bad. Totally though it was bricked until i was able to flash this stock gingerbread rom, but now kies says that my Blaze S does not qualify for upgrades... Did the re-partitioning do this?
I can no longer get to the recovery screen, although if I restart my blaze while connected to a pc via usb, it does allow the "re-install OS?" page to display, and I can get to recover from there: But absolutely no more access to the recovery "menu" which allows me to wipe cache/restore to factory/etc.

Just Odin cwm back then flash away
Sent from my SAMSUNG-SGH-T769 using xda app-developers app

Thanks for the quick reply; I will try that right now: My fingers are crossed.
2vivid said:
Just Odin cwm back then flash away
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
Click to expand...
Click to collapse

thomassino said:
Thanks for the quick reply; I will try that right now: My fingers are crossed.
Click to expand...
Click to collapse
It's just a soft brick, I have done that at least 10 times.

Will you make this?
k0nane said:
Absolutely.
Click to expand...
Click to collapse
Hi, k0nane I too have bricked my phone due to not unchecking re-partition. Now no matter what I do the phone displays the "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again. It is frustrating. I will certainly pay you if you make a fix for this that I can flash in odin! I don't care if it wipes my phone completely as I was trying to flash a new rom anyways. Please reply I'm desperate to get this thing working again.

runboyrun said:
Hi, k0nane I too have bricked my phone due to not unchecking re-partition. Now no matter what I do the phone displays the "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again. It is frustrating. I will certainly pay you if you make a fix for this that I can flash in odin! I don't care if it wipes my phone completely as I was trying to flash a new rom anyways. Please reply I'm desperate to get this thing working again.
Click to expand...
Click to collapse
That's a soft brick.
No need to pay anyone lol just pull the battery and go back to download mode (for Odin) again and revert back to stock. A quick search through 'bricked' type threads would have netted this info :thumbup:
Sent from my SGH-T769 using xda app-developers app

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

Help!!! I forgot to unlock bl

I just tried to flash Jellywiz for the first time. I forgot to unlock the bootloader prior to flashing the rom. I know.........So Stupid.
Anyway. I've tried the odin trick but my phone just has the yellow triangle with the message that the system software in not authorized by VZE. I can't boot into recovery to restore my backup. Odin doesn't seem to work. I'm trying to follow the instructions http://forum.xda-developers.com/showthread.php?t=1840030 But I'm not getting the "PASS" message.
Please help... I'm freaking out.

Are you booting into download mode before connecting to Odin?

Oh, no I wasn't. I'm now going through the Odin process in Download mode. Thanks for the tip. Hope this works

dbow32 said:
Oh, no I wasn't. I'm now going through the Odin process in Download mode. Thanks for the tip. Hope this works
Click to expand...
Click to collapse
folks...i will say it again, you dont need to use puremotives guide to recover in this situation. just flash a stock rom in odin and be done. there is no need to flash bootchains...use section 6 of my guide, then if that does not work use puremotives guide. not trying to take anything away from pures great writeup, but its intended for devices that are actually soft bricked. i only recomend flashing bootchains if absolutely necessary because if anything fails during the flash, you get a hardbrick....then its jtag time!

droidstyle said:
folks...i will say it again, you dont need to use puremotives guide to recover in this situation. just flash a stock rom in odin and be done. there is no need to flash bootchains...use section 6 of my guide, then if that does not work use puremotives guide. not trying to take anything away from pures great writeup, but its intended for devices that are actually soft bricked. i only recomend flashing bootchains if absolutely necessary because if anything fails during the flash, you get a hardbrick....then its jtag time!
Click to expand...
Click to collapse
Ok, I'll try that. Thanks for every ones help. I'll let you guys know if it works.

I'm up and running. Thank you all so much... especially droidstyle for the tutorial. I tried looking for a "Donate" button on the tutorial but couldn't find one. I'll keep looking and send some cash your way. Again, thank you VERY much.
Dave

dbow32 said:
I'm up and running. Thank you all so much... especially droidstyle for the tutorial. I tried looking for a "Donate" button on the tutorial but couldn't find one. I'll keep looking and send some cash your way. Again, thank you VERY much.
Dave
Click to expand...
Click to collapse
donate link up! i never really thought to put up a link, but actually there have been quite a few folks wanting to make a donations...thx and glad your back up and running!

Droidstyle what are boot chains? I came from sprint and never saw them before and a Google search doesn't give an answer. Could u please shed some light on it for me. Thanks bro
Sent from my SCH-I535 using xda premium

musclehead84 said:
Droidstyle what are boot chains? I came from sprint and never saw them before and a Google search doesn't give an answer. Could u please shed some light on it for me. Thanks bro
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
bootchains are the order of operations for the boot process(aka bootloader). some folks have had thier devices emmc internal memory get corrupted during a cwm session causing the system permissions to read only. since no data can be written on boot, your device is stuck in a bootloop. reflashing the bootchain followed by the stock rom restores the proper boot sequence and read/write permissions allowing the device to boot. the kicker is you want to make sure nothing goes wrong when flashing a bootchain or its brick city. hopefully this makes sense lol

droidstyle said:
bootchains are the order of operations for the boot process(aka bootloader). some folks have had thier devices emmc internal memory get corrupted during a cwm session causing the system permissions to read only. since no data can be written on boot, your device is stuck in a bootloop. reflashing the bootchain followed by the stock rom restores the proper boot sequence and read/write permissions allowing the device to boot. the kicker is you want to make sure nothing goes wrong when flashing a bootchain or its brick city. hopefully this makes sense lol
Click to expand...
Click to collapse
Yes it does. Thank you so much. I have never seen these used before so it was new to me. Thanks again.
Sent from my SCH-I535 using xda premium

I wonder how many times droidsytles howto has saved people, im sure its in the thousands, thanxs droidstyle! I known it saved me a couple times
Sent from my SCH-I535 using xda app-developers app

[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