Database Info

Trying to restore with Odin killed my phone

Actually, not my phone but a friend's. I was trying to restore it to stock with Odin in order to flash Cyanogen, however Odin was being a real PITA. Through numerous attempts, Odin would refuse to finish the restoration process, often hanging at sbl.bin or Setting PIT file. I tried at least ten times to get it to flash correctly. The final time I decided to let it sit overnight and flash, just in case. When I got up this morning though, it was still hung up. I unplugged the phone and pulled the battery like I had done multiple times the night before, so that I coould give it one last try before I went to work. But this time, the phone wouldn't go into download mode. I had been using the USB and 3 button combo method, but nothing this time. The phone shows no signs of life at this point, and I really don't have anything short of a JTAG left to try on it. Now I have to buy my friend a new phone.
Has anyone else experienced this kind of terrible performance from ODIN? And is there anything other than JTAG I can try. If there is someone out there that can fix it with JTAG, I would also pay money for that. I don't have the soldering skills necessary to fix this thing.

They sell the pre made jigs you can buy, just search for it and you will find plenty
Sent from my SGH-I897 using XDA App

The battery doesn't charge in download mode, the battery could very well just be dead. Pull the battery, reinsert it and plug in the phone to charge it, if all it does is get really hot and never shows any sign of life that is a brick. Check your PM.

super coffee said:
Through numerous attempts, Odin would refuse to finish the restoration process, often hanging at sbl.bin or Setting PIT file. I tried at least ten times to get it to flash correctly.
Click to expand...
Click to collapse
Can't really blame anyone but yourself for that one.. If it hung at sbl.bin and you managed to not brick it, you dodged a bullet.
Anyway, sounds like you dodged several bullets and then the inevitable happened. A jig won't help, and you're correct in your assumption that JTAG is your only way out. Fortunately for you, one of our fellow captivaters is still offering (at least to my knowledge) a free JTAG service. You should contact him to see if he'd be willing to restore your device, his name is connexion2005.
For future reference, don't flash back to stock unless you really need to. And when you do, don't flash an image that includes bootloaders. If you have bootloaders that work (3 button combo enabled on 2.2- bootloaders or 2.3 bootloaders), use a non one-click odin with an image that doesn't include sbl.bin or boot.bin; otherwise you're just taking unnecessary risks.

little8020 said:
They sell the pre made jigs you can buy, just search for it and you will find plenty
Sent from my SGH-I897 using XDA App
Click to expand...
Click to collapse
I got one off eBay for 10 bucks. Probably the best investment I've made as I have encountered about every brick situation you could imagine.

This may sound stupid, but maybe trying to flash GB bootloaders with ODIN(not one-click) could work? Exhausting all options before sending your phone in or having somebody JTAG would be preferable.

+1...they are well worth the money if you do any ROM flashing!

I have same problems before. 3 button combo method didn't work at all. No JTAG at that time.
When you plug your phone to computer, make sure it still can detect "SAMSUNG Android USB composite Device", but not "Unknown devices".
Even I wasn't on download mode or recovery mode, the odin able detect my phone as COM port then I was using Odin3 v1.8. then I put "galaxys-bootloader-JVB.tar.md5" to bootloader since I already have 2.3.3 rom before.

Another "dad, my friend has this problem" thread!?

For future reference, use Heimdall and read instructions thoroughly and multiple times. I just started using Heimdall when I made my move to flash gingerbread again when the KF1 ROM came out and I love it. Regardless how well a program works though, it's only as good as the person operating it. There are TONS of people here far more educated than me when it comes to flashing anything, but I have never bricked, or soft bricked even (yet) and I flash a decent amount.

If all else fails, I did have good luck with Josh @ mobiletechvideos (haven't posted enough times to be allowed to post the link, but he's on youtube. He's also here as connexion2005) he was able to unbrick my phone for $50. The post office does not seem to like to deliver mail from him to me, but I'm typing this on the phone he unbricked.
Sent from my GT-I9000 using XDA App

Josh @ mobiletechvideos rocks!
He unbricked my Captivate!

There is not a problem with odin! Why do people always say don't use odin because it will brick your phone. You have to use it correctly. Make sure before you even open odin that the computer recognizes your phone and you have all of the correct drivers, etc. installed BEFORE even messing with odin. Also be sure to connect to a usb port that is connected to your hard drive to limit the chance of the computer not recognizing your device.

megatronisabeast said:
Also be sure to connect to a usb port that is connected to your hard drive to limit the chance of the computer not recognizing your device.
Click to expand...
Click to collapse
Your hard drive has usb ports?
You mean motherboard?

cappysw10 said:
Your hard drive has usb ports?
You mean motherboard?
Click to expand...
Click to collapse
Yes, the motherboard! Was in the middle of a tech class when I posted that! Guess I can't multi task! Thanks!

Thanks for the feedback guys. I'm here when you need the impossible done to your Captivate...

megatronisabeast said:
There is not a problem with odin! Why do people always say don't use odin because it will brick your phone. You have to use it correctly. Make sure before you even open odin that the computer recognizes your phone and you have all of the correct drivers, etc. installed BEFORE even messing with odin. Also be sure to connect to a usb port that is connected to your hard drive to limit the chance of the computer not recognizing your device.
Click to expand...
Click to collapse
I've had odin fail a few times in a row on me when flashing gb bootloaders for i897. I had odin flashed countless times on multiple devices and computers. I'm pretty sure Odin isn't foolproof. Not everything can be contributed to pebcak, although the vary majority of problems posted on xda are...

kimchi0400 said:
I've had odin fail a few times in a row on me when flashing gb bootloaders for i897. I had odin flashed countless times on multiple devices and computers. I'm pretty sure Odin isn't foolproof. Not everything can be contributed to pebcak, although the vary majority of problems posted on xda are...
Click to expand...
Click to collapse
everytime odin has 'failed' for me, it's been a user error on my part. you need to follow the steps sequentially otherwise you have a higher probability of failure/brickage.

rmal0 said:
everytime odin has 'failed' for me, it's been a user error on my part. you need to follow the steps sequentially otherwise you have a higher probability of failure/brickage.
Click to expand...
Click to collapse
I honestly think that a lot of information here on XDA is only partial and this will get some into trouble. I know people say "search for it, it's here" and it is but the problem is that 10% of the time the information that someone is looking for is buried in a thread and the other 90% the search results list the same question being asked and answered with "it's here search" or "Did you search??"
There honestly should be posting guidelines, for everyone, I mean people take all the time to write disclaimers why not proper directions? Is there a standard Template? If I'm missing it please feel free to point it out.
For example:
This is a 9000/897/896 based ROM
This ROM needs the following bootloaders: ....
This ROM contains Bootloaders: Yes/No
This ROM will change your product code: Yes/No
This ROM requires a Davlik wipe to work: Yes/No
This Kernel is 9000/897/896 based
blah blah blah.......
If the information is readily and easily available then the amount of "dumb" question should go down dramatically and then there will be a "standard"
But then again it's Android/Linux, being fragmented is half the fun..
</rant>Just needed to vent...

True Brick...QHSUSB_DLOAD

Hey guys...As a few of you know, my phone met its demise last night for (seemingly) no reason. I had recently backed up my ROM through Rom Manager and tried out a few themes from the market.
Anyways, when I plugged my phone into my computer, I see that it tried to install some drivers and then I see "QHSUSB_DLOAD" as my phone.
Ive noticed that all TRULY bricked phones (not just the sensation) all have this "QHSUSB_DLOAD" in common. No one has yet to figure out what this is or how to fix this.
Tmobile chalked it up to hardware failure and has a new (likely refurbished ) on its way.
I think we need to figure out what the heck this is. A few mentioned a connection between Rom Manager, CWM, and QHSUSB_DLOAD. I, for one, will make dang sure that Rom Manager stays off my phone...Any other ideas?
Until this is worked out, its VERY likely that rooting COULD randomly cause the dreaded true brick, QHSUSB_DLOAD style.
Matt

Just swayed my decision on wether to root or not.

So does it turn on? You are a bit unclear about your situation. Does it charge, when you charge it. And does the PC recognize it when you connect it to the PC?

Actually this is well documented. You are in Qualcomm high speed USB download mode. It is typically caused by a problem with your processor and or it's software. Either it is crapping out or more likely something corrupted the software, either by flashing a custom kernel that isn't 100% stable with the hardware (since kernel source for this phone is incomplete this IS possible) or it's just bad luck. Voltage tweaks can have a long term detrimental effect on hardware.

Hey guys, it is dead as a door knob.
http://forum.xda-developers.com/showthread.php?t=1321110
That ought to sum things up...
Im sure its bricked...I just want to look more into this as I have yet to find a single case where this was solved. It just gets pushed aside since no one knows.

Behold_this said:
Actually this is well documented. You are in Qualcomm high speed USB download mode. It is typically caused by a problem with your processor and or it's software. Either it crapped out or more likely you corrupted the software, either by flashing a custom kernel that isn't 100% stable with the hardware since kernel source for this phone is incomplete this IS possible. Voltage tweaks can have a long term detrimental effect on hardware.
Click to expand...
Click to collapse
I was using cm7, build 9 and fauxs kernel build 8. I dont do UVing or OVing and have kept the CPU speed to 1.18Ghz.
My computer told me that it failed to install whatever it felt it needed.
So this is known? Am I correct in thinking that this is a 100% brick then, or is there anything, save from tearing it open, that can be done to fix it?
Although I have a new one coming, Id like to get to the bottom of this for everyone else.
Matt

Well, yes...and no. For all intensive purposes it is bricked, however, if it's just software HTC (or anyone with a leaked loader) could recover it easily. If it's hardware then nothing can be done. You can find the Qualcomm drivers online but still need the loader (all I've found are motorola sbf's nothing for HTC). Basically you did the only thing you can at this point, but now you have a little more info on it.

Behold_this said:
Well, yes...and no. For all intensive purposes it is bricked, however, if it's just software HTC (or anyone with a leaked loader) could recover it easily. If it's hardware then nothing can be done. You can find the Qualcomm drivers online but still need the loader (all I've found at motorola sbf's nothing for HTC). Basically you did the only thing you can at this point, but now you have a little more info on it.
Click to expand...
Click to collapse
Someone could get an XDA style Nobel prize for coming out with something that could fix this phone when this happens.
Im guessing that is what a JTAG does? Would be great once warranty time is over!
I am suspicious this could be another build quality issue with HTC...Day one with this phone had the same sort of thing happen, but it eventually booted. Perhaps this was just waiting to happen?
Or, I wonder if it is related to CWM and Rom Manager? This seems to be a RARE occurance considering how many people flash the above mentioned ROM and kernel without this happening. The last thing I did before charging was backing up in Rom Manager.

Jtag is a little extreme as it involves soldering and messing with internal components, plus don't think it's been done on this chip set, but I could be wrong. The ROM is usually less of a concern then custom kernels are. Also ROM manager sucks and many times is very buggy. It is safer to do all those kinds of things through recovery. Uninstall ROM manager and forget it ever existed (just my opinion).

Behold_this said:
Jtag is a little extreme as it involves soldering and messing with internal components, plus don't think it's been done on this chip set, but I could be wrong. The ROM is usually less of a concern then custom kernels are. Also ROM manager sucks and many times is very buggy. It is safer to do all those kinds of things through recovery. Uninstall ROM manager and forget it ever existed (just my opinion).
Click to expand...
Click to collapse
Okay, how about this...I intend to S-off and reinstall CWM the SECOND I get my new phone. LOL...Should I erase my ROMs+kernels from the SD card and start over from scratch, or can I just boot up again like nothing happened?
I guess its safer to start over, huh?
EDIT: I have been reading over stories involving a hard brick and QHSUSB_DLOAD. It seems it ALL came from SD card partitioning in CWM. I was also in recovery that day restoring my ROM when I accidentally touched the screen and the phone rebooted. (After restoring) I thought it was just rebooting recovery. I wonder if something else happened? The phone booted up fine and worked for some time after. The last thing done was charging the phone via wall charger, seeing it was done, and then unplugging.
Matt

it may not be necessary, but I would. I'd just redownload all the software I plan on loading from the start and give it a clean slate, but that's just me. Also be very careful with resorting apps and data since we really don't know the total cause of your issue. All in all you probably won't have to deal with this again as long as you minimize your risk.

nice. maybe there are aliens inside your phone! Just a thought as it seems everyone seems to just turn around when they see this problem. some of the brave ones got taken by the aliens too for snooping out too much

vitusdoom said:
nice. maybe there are aliens inside your phone! Just a thought as it seems everyone seems to just turn around when they see this problem. some of the brave ones got taken by the aliens too for snooping out too much
Click to expand...
Click to collapse
Im the alien!
Yea, I never saw this happening to me. I read carefully before I do anything and have never tried anything fancy.
Im guessing that QHSUSB_DLOAD lets you know the phone is fully erased and waiting for something to be flashed the elite way? (From the factory via their gadgets). To date, NO ONE has recovered from this.
Man Id love to be the one to recover! I crapped myself when I saw QHSUSB_DLOAD mentioned on my computer. Its the kiss of death.
I also have to wait till next week to get my replacement despite me opting for the fastest most $$$ method of shipping. UPS Express is the fastest and will take till monday (which means tuesday since no one will be around to sign for it).
Ugg..
Matt

Doh! that just sucks Matt. but then again, thats way better than having some hardware issue and being fixed (anything with hardware issue fixed surely ends up going back to the guys that fixed it. they seem to put some time bomb in there so you'll go back crying to fix it again and again. lol) haven't had this issue ever since.(was flashing my phones way back then) maybe im just lucky. hopefully i will not encounter this. (the only thing I bricked was my brand new PSP2002. just bought it from US and im way over in NZ mate - didn't have a option to return it. )
where does this QHSUSB_DLOAD appear? would this come up when you turn the device on? because i've seen some devices that are bricked, they just lit up and goes off and never charges and can't go to bootloader. thinking this is 100% bricked or this QHSUSB thingy is the pure brick?

vitusdoom said:
Doh! that just sucks Matt. but then again, thats way better than having some hardware issue and being fixed (anything with hardware issue fixed surely ends up going back to the guys that fixed it. they seem to put some time bomb in there so you'll go back crying to fix it again and again. lol) haven't had this issue ever since.(was flashing my phones way back then) maybe im just lucky. hopefully i will not encounter this. (the only thing I bricked was my brand new PSP2002. just bought it from US and im way over in NZ mate - didn't have a option to return it. )
where does this QHSUSB_DLOAD appear? would this come up when you turn the device on? because i've seen some devices that are bricked, they just lit up and goes off and never charges and can't go to bootloader. thinking this is 100% bricked or this QHSUSB thingy is the pure brick?
Click to expand...
Click to collapse
The message QHSUSB_DLOAD appears the first time I tried to connect via USB to my computer. It showed up on my computer down where usb notifications occur. After it told me it couldnt install hardware, that was it. No more action from either the phone or the computer. Its like the world just passed right by my poor phone.
Maybe I will get lucky and get a phone free of dust as well! I was waiting on calling in that care package for later...Oh well.
Matt

Oooh nice! so the device really has a black screen and that message appeared on driver installation on you computer.
most of the people in the net just mentions that this driver is missing. If the driver is missing, maybe it did really get corrupted(software because of rom-manager not pointing to this ) but yeah, could also be hardware failure. did it say on your computer that it was installing some drivers for that QHSUSB_DLOAD? and it failed? what about HTC? did you see anything from HTC about this?

vitusdoom said:
The message QHSUSB_DLOAD appears the first time I tried to connect via USB to my computer. It showed up on my computer down where usb notifications occur. After it told me it couldnt install hardware, that was it. No more action from either the phone or the computer. Its like the world just passed right by my poor phone
Click to expand...
Click to collapse
this is the EXACT problem im having! on my tmobile SGS2

not sure if this has already been mentioned but what do you guys think of this?
http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-ii-jtag-brick-repair/

Hey guys,
I'm in the same situation too.... I've been flashing hundreds of roms and all kind of software on a lot of different android phones...but this is the first time ever I came across something like that where I feel that this is the end of it!!!! I made a mistake...by not paying attention flashing an HD2 rom to my sensation!!! You know some time s**t happens... and here we go...I got a completely dead bricked sensation with nothing i can do, even I've been searching and reading for 2 days with no luck what so ever...so I guess no one is able to find a solution for this issue yet!!!!Which is too bad: confused: .I wish I was able to find some solution to this problem so I can get my phone back to life and help every one else who might end up with this issue. Because I think a lot of people might be in this situation!!!. I tried every thing I can possibly do with m y knowledge and the results was all dead ends. I just hope that this issue will be taken to the next level by some one...like all the other phones that it can be unbricked...so why not the sensation!!!?. Any one can come up with and ideas for this please help us as a community to get pass by this dead end on our Htc sensations.

Guys i have absolutely same problem with my sensation, i believe there must be a way how to bring our phones back to life. Im sure that on my phone its just software problem caused by backing to s-on(got bricked right after adb rebootbootloader). So if some1 find out how to unbrick, PLEASE post it. I dont want to solve it by warrany, because its little far for me :-(

totally bricked sgs2?

I've tried a few different roms on my SGS2 but I'm definately not an expert. I tried going from cyano to darkys but ran into some trouble. I googled around and found that I needed the "resurrection edition" as a middle man.
The instructions told me to flash with odin with the re-partition box checked, something I've not done before. Odin appeared to hang on "setting parition" (or similar) so I left it for an hour or so. Unfortunately still there when I came back.
I pulled the battery and was going to try without re-parition checked. The only problem is that now I can't do anything, at all. I don't get a charging icon on the screen, had the battery our for an hour now and still can't get anything to happen.
Have I irrevocably bricked the phone? It's still within the warranty period but of course they'll probably reject that on the grounds that I've fiddled too much.
I'm praying someone can help me with this or I'm gonna be one sad panda.

Yeah I'm similar to you, doing this stuff as a noob. It's not a good idea. If none of your buttons work, there are some tricks that can get it back into download mode browse the android forums for that a swell, otherwise try USB jig. Your phone seems pretty hard-bricked most likely will have to send yours to the manufacturer when you **** up like this.

can get into download mode? if you can then your safe
a couple questions
:what op is your pc win7 win vista mac linux
:can you get into download mode vol down>power>home button press and hold
:is odin correct for your pc?
:you dont know odin your ment to do stuff with odin b4 cwm
:if all fails try getting into download mode with a usb cable plugged in
if nothing works try the usb jig you can hunt around on utube
if not send it to samsung saying kies update failed and you get the jist
hope ive helped
oh by the way wrong thread

Thanks for the replies guys,
I'm running Windows7 64bit
Nothing happens with any keypresses at all
I've used that version of odin to flash the phone before, just not with the re-partition box ticked
I've since read that using the re-partition box is a big nono. Unfortunately I must have been following instructions written by someone as nooby as me From some other posts etc it does seem like it needs jtag to fix it.
Just called my operator who I also have insurance with, told them that kies ran an update but the phone never rebooted. I was all ready for a fight with them but he instantly said that he'd have a replacement sent out within 24 hours. Very surprised it was that easy, they'll be getting some wine at xmas
thanks

iwasinnamuknow said:
Thanks for the replies guys,
I'm running Windows7 64bit
Nothing happens with any keypresses at all
I've used that version of odin to flash the phone before, just not with the re-partition box ticked
I've since read that using the re-partition box is a big nono. Unfortunately I must have been following instructions written by someone as nooby as me From some other posts etc it does seem like it needs jtag to fix it.
Just called my operator who I also have insurance with, told them that kies ran an update but the phone never rebooted. I was all ready for a fight with them but he instantly said that he'd have a replacement sent out within 24 hours. Very surprised it was that easy, they'll be getting some wine at xmas
thanks
Click to expand...
Click to collapse
lool oh well maybe you can unbrick your sgs2 and have 2 sgs2s:

hehe well once i've got the new phone going (so I'm not losing business), maybe i'll play around with the old one. Wouldn't be the first "spare" sgs2 I've managed to get

Help (if possible)! think my phone is done :(

This is going to be long!
If anyone has insight to this would be appreciated
Precursor: I am on CM9 nightly (7-27-12) with 6.0.1.0 non touch recovery (NS4G)
So last night I go to open my opera web browser and it would flash like it would open and instant close (no error message). I say OK thats weird and decide to reboot. Upon rebooted I am greeted with never ending amount of FC's from every app and service imaginable. I again say OK EXTREMELY weird and decide its time to restore my backup from yesterday.
I reboot in recovery and what do I get greeted with? Unable to mount /sdcard! Long story short after scouring google for about an hour I find that if I do a fastboot oem lock/unlock I should get back up and running. Thankfully that works and I install the newest 7/31 CM9 nightly.
I wake up today without my phone alarm going off when it should. Weird huh? I go to open the clock and get a FC from the clock application. Reboot and it works just fine. OK weird again.
Go to work and leave my phone on the counter to help a customer. I come back to the desk and my phone is in recovery mode? Uhhh what? I reboot the phone and it says "encryption unsuccessful" and the phone needs to wipe data and reboot to continue use...
I decide WTF why not, not like I can use it. At this point I'm worried though. The phone reboots to recovery and I guess does a data wipe (takes 3-5 mins) and reboots. Now I am stuck on the CM9 bootscreen and won't go past.
I have some ideas as to get the phone (hopefully) back up and running. Just curious what this sounds like to anyone more knowledgeable then me (especially the part where it tried to encrypt my phone without me touching it!)
Any thoughts or help is appreciated!
Edit: I tried copying files to sdcard from recovery using mount usb storage. The files copy over and as soon as I leave the mount menu and go to install the zip files WHICH I SAW ON THE SDCARD they ARE NOT THERE anymore.
Edit2: It still lets me install the CM9 7/31 nightly which I had saved on the phone yesterday. Even after wiping everything and reinstalling the ROM I can't get past the CM9 bootscreen
Edit3: Tried fastboot, odin, nothing works. Even after odin I still get the CM9 boot screen. Pretty sure something is messed up to the point of I need a new phone. FML!

YESS!!!
YES I WANT ATTENTION.
I Have exactly the same. Mother of smartphones Somebody help us!
Its the internal Memory thats messed up yes, But Please somebody fix this Bullcrap. We don't have the knowledge but I will gladly donate to you who fixes it!
I just bought a brand new screen for my phone and I don't freaking want to buy a new Phone At the moment, So if you find a way to help us then let us know since that could be lifesaving right now.

Pretty sure I've given up. Everything I've tried has failed... looks like it might be gnex time.

NYYFan325 said:
Pretty sure I've given up. Everything I've tried has failed... looks like it might be gnex time.
Click to expand...
Click to collapse
Have you tried just going back to the stock rom/recovery/bootloader with the samsung application?

ronnygunz said:
Have you tried just going back to the stock rom/recovery/bootloader with the samsung application?
Click to expand...
Click to collapse
I would Love to get an link to that. if it helps us out i'd sh1t goldbricks. seriously.

Moonystorm said:
I would Love to get an link to that. if it helps us out i'd sh1t goldbricks. seriously.
Click to expand...
Click to collapse
I couldn't post the link because I have less than 10 posts here so I pm'd you. At least I hope I did. Let me know if you didn't get it.

Can you send me the PM as well. I know of the tool you are referring to but can't seem to find it anymore

NYYFan325 said:
Can you send me the PM as well. I know of the tool you are referring to but can't seem to find it anymore
Click to expand...
Click to collapse
I tried to send it, I hope it worked but it doesn't show up in my sent messages so I am in the dark.

Stock ROM. All the way back to Gingerbread.
http://forum.xda-developers.com/showthread.php?t=1572307

Well nothing officially works
The samsung simple dl tool just says "error" when I hit "start download" nearly immediately. Now I have no recovery or anything. Going to sprint right after I get out of work to get a gnex

NYYFan325 said:
Well nothing officially works
The samsung simple dl tool just says "error" when I hit "start download" nearly immediately. Now I have no recovery or anything. Going to sprint right after I get out of work to get a gnex
Click to expand...
Click to collapse
Ugh... I'm sorry people Who will get to our problem. Paid samsung services can Help. Nothing else. I be a smart guy and do like NYYFan here and get a galaxy nexus. thank You everyone for help. i set up 48hours for anybody to help me or i get a new device. Might sound rude but its a choice i made.
-Moon

I HAD THIS SAME EXACT PROBLEM
Temporary solution: heat the phone up with a hair blow dryer. get it hot but not so hot that it melts things. it will be able to boot up and work. I used this method so i could copy my sd card to my computer and wipe everything off
Permanent solution: turn your phone in for repair. there is no remedy to fixing this. apparently the circuit board or chip is bad and you can't fix it.
Luckily I had best buy black tie protection and I am waiting on my new replacement phone.

NicholasQ said:
I HAD THIS SAME EXACT PROBLEM
Temporary solution: heat the phone up with a hair blow dryer. get it hot but not so hot that it melts things. it will be able to boot up and work. I used this method so i could copy my sd card to my computer and wipe everything off
Permanent solution: turn your phone in for repair. there is no remedy to fixing this. apparently the circuit board or chip is bad and you can't fix it.
Luckily I had best buy black tie protection and I am waiting on my new replacement phone.
Click to expand...
Click to collapse
I work in a computer repair shop and going by that solution...sounds like a problem I may be able to repair using a similar method as some of the board-level repairs I do pretty often...anyone want to send me a dead lab rat? Lol
Sent from my Nexus S 4G using xda premium

Xaelius said:
I work in a computer repair shop and going by that solution...sounds like a problem I may be able to repair using a similar method as some of the board-level repairs I do pretty often...anyone want to send me a dead lab rat? Lol
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
You can have mine lol x) And Yep i fix computers for friends and so on their friends and this sounds like Nvidia was behind the chip... xD

It wouldn't matter who actually makes a chip if the heating it up is a temporary fix. That is a OEM issue. Basically think xbox360 rrod with the warped boards the solder melting/failing and the chips get loose etc.
Unless heating up failed flash storage temporarily makes it work. Which I doubt is the case but don't actually know. Brings back memories of putting failing HDD drives in the freezer though.

Well this is my official goodbye to the Nexus S forums (not like anyone cares haha). Just got my shiny new Galaxy Nexus. Have a great night everyone and happy modding!

NYYFan325 said:
Well this is my official goodbye to the Nexus S forums (not like anyone cares haha). Just got my shiny new Galaxy Nexus. Have a great night everyone and happy modding!
Click to expand...
Click to collapse
Ugh. Congraz. xD

Try Adam outler unbrickable mod for nexus s
Sent from my Nexus S 4G using xda premium

http://forum.xda-developers.com/showthread.php?t=1397393
Sent from my Nexus S 4G using xda premium

Unfortunately that is good only if software screwed up your phone. In my case and I'm sure others when it is hardware failure, that won't work :\

[Q] Will USB Jig work?

Hello, so here is the story the best I can tell it. I have done quite a bit of work on Iphones, Ipods, and roms on my own phones, because of this my friends son asked if I had ever JTag'd a phone before, which I had never heard of at the time. Apparently a friend of his was trying to load a custom ROM on his Verizon Galaxy S3 and something went wrong. Unfortunatly, I have no idea what ROM he tried loading or how he tried loading it. All I do know is, there is no response on the phone at all, the screen stays black. When you plug it into the computer, the computer recognizes a device but asks for a qhsusb_dload driver. I have read that this is a hard brick, and needs Jtag service, however I have also read that it is really hard to actually hard brick a phone, and this is actually more of a soft brick. Can anyone confirm this, and is it possible that just a USB jig will work to force it into download mode? I have ordered a Jig and it should be here next week, but I wanted to ask some questions in the mean time. Thanks for your help.

pedenspeed said:
Hello, so here is the story the best I can tell it. I have done quite a bit of work on Iphones, Ipods, and roms on my own phones, because of this my friends son asked if I had ever JTag'd a phone before, which I had never heard of at the time. Apparently a friend of his was trying to load a custom ROM on his Verizon Galaxy S3 and something went wrong. Unfortunatly, I have no idea what ROM he tried loading or how he tried loading it. All I do know is, there is no response on the phone at all, the screen stays black. When you plug it into the computer, the computer recognizes a device but asks for a qhsusb_dload driver. I have read that this is a hard brick, and needs Jtag service, however I have also read that it is really hard to actually hard brick a phone, and this is actually more of a soft brick. Can anyone confirm this, and is it possible that just a USB jig will work to force it into download mode? I have ordered a Jig and it should be here next week, but I wanted to ask some questions in the mean time. Thanks for your help.
Click to expand...
Click to collapse
Good luck. That qhsusb tag denotes a hard brick.

pedenspeed said:
Hello, so here is the story the best I can tell it. I have done quite a bit of work on Iphones, Ipods, and roms on my own phones, because of this my friends son asked if I had ever JTag'd a phone before, which I had never heard of at the time. Apparently a friend of his was trying to load a custom ROM on his Verizon Galaxy S3 and something went wrong. Unfortunatly, I have no idea what ROM he tried loading or how he tried loading it. All I do know is, there is no response on the phone at all, the screen stays black. When you plug it into the computer, the computer recognizes a device but asks for a qhsusb_dload driver. I have read that this is a hard brick, and needs Jtag service, however I have also read that it is really hard to actually hard brick a phone, and this is actually more of a soft brick. Can anyone confirm this, and is it possible that just a USB jig will work to force it into download mode? I have ordered a Jig and it should be here next week, but I wanted to ask some questions in the mean time. Thanks for your help.
Click to expand...
Click to collapse
That sucks, that my friend, is a hardbrick, fixable, but its a process and tedious.
Sent from my Secret Base in Outer Space

I had the same thing happen to me. See here http://forum.xda-developers.com/showthread.php?t=1770341
I pushed a corrupt ROM and it borked. Contrary to your post, it is easy to brick this S3. I've hard bricked twice.... Just be sure the files you flash are for your variation of the S3 (ie don't flash an ATT rom onto a VZW fone) and make sure you got a good download by checking the md5.
FWIW, Josh over at MobileTechVideos.com has JTAG'd me back both times. Fair price and quick service. I believe he's the only dude in the US doing it...
Sent from my SCH-I535 using xda app-developers app

hi there, unfortunately i flash the wrong rom, and the result is the same of the first poster
what i can do? what is jtag?
i have bought a j usb someone have used it? it works?

what is "jtag?"

It's a debugging port that can be used to push firmware onto memory. Mostly used for diagnostics and initial programming since it allows debugging after the first cpu instruction.

UnEZ said:
It's a debugging port that can be used to push firmware onto memory. Mostly used for diagnostics and initial programming since it allows debugging after the first cpu instruction.
Click to expand...
Click to collapse
i have bought the jig usb, i'll try, if download mode starts, then what i should do? follow this guide? http://forum.xda-developers.com/showthread.php?t=1840030

Interested to see if you are able to get the jig to work. I have not heard of a jig working on a hard brick. Yes if you get back into download mode just start the process over with Odin
Sent from my SCH-I535 using xda premium

arkas90 said:
i have bought the jig usb, i'll try, if download mode starts, then what i should do? follow this guide? http://forum.xda-developers.com/showthread.php?t=1840030
Click to expand...
Click to collapse
Hey arkas90 did JIG work for you i am in the same boat trying to revive my s3 . Please let us all know if that works