Develop Bugs

[Q] Sudden Hardbrick

My phone hardbricked for no apparent reason, and I'm not sure what to do. Battery was at about 50% yesterday, it turned off and wouldn't turn back on. I did a soft reset, and it turned on. I watched it go as far as the logo and then had to walk away. When I came back, the phone was black again. And it hasn't turned on since. No logo, nothing. I've tried a soft reset, plus multiple other reset combinations. I plugged my phone to the computer, I get the normal connecting 'ding', but then it says that driver's device cannot be found.
I'm running stock firmware, no mods. No history of battery issues (except the normal slow decline). I've had the phone for a year and three weeks, so I'm out of warranty too. I called T-mobile and they said it sounds like a hardbrick and are willing to switch it out for $20 since I'm out of warranty. I can't do that since I'm out of the country for the next 1.5 months, so I was wondering if anyone out there had any suggestions on what to do or why this even happened?
Thanks!

goeundiane said:
My phone hardbricked for no apparent reason, and I'm not sure what to do. Battery was at about 50% yesterday, it turned off and wouldn't turn back on. I did a soft reset, and it turned on. I watched it go as far as the logo and then had to walk away. When I came back, the phone was black again. And it hasn't turned on since. No logo, nothing. I've tried a soft reset, plus multiple other reset combinations. I plugged my phone to the computer, I get the normal connecting 'ding', but then it says that driver's device cannot be found.
I'm running stock firmware, no mods. No history of battery issues (except the normal slow decline). I've had the phone for a year and three weeks, so I'm out of warranty too. I called T-mobile and they said it sounds like a hardbrick and are willing to switch it out for $20 since I'm out of warranty. I can't do that since I'm out of the country for the next 1.5 months, so I was wondering if anyone out there had any suggestions on what to do or why this even happened?
Thanks!
Click to expand...
Click to collapse
does it respond to plugging in to charge? im not 100% but if its responding at all when it gets plugged in its not hardbricked only softbricked so go from there. when i hardbricked my first s2 due to a corrupt kernel file i flashed it would not react to anything at all. complete dead weight

U stated that when u plugged it into ur computer u got a ding then says driver device not found. Sounds to me that ur not in a hard birck when I bricked mine I didn't even get that. Check out the link it well help.
http://galaxys2root.com/t-mobile-ga...ck-t-mobile-galaxy-s2-sgh-t989-android-2-3-6/
on my t989 enjoying sith3, thank u to all

Thanks for everyone's help. I ended up sending in my phone to a Samsung service center (while I was in Korea). They confirmed that it is a hardbrick. They opened it up and said it looked like there was a short and it fried the motherboard. They couldn't tell me what caused the short--they said maybe some water got into the phone through the charging port, but I know that isn't true... I had it plugged into an old power strip and maybe that's why? :crying:
Either way, I was told my only option was to get the motherboard replaced which would be $200. I told them no thanks and that I'd just get a replacement phone from T-mobile for $20.

sounds like another " I swear i didn't do anything.. it just happened" story.. classic..
Sent from my SAMSUNG-SGH-T989 using xda app-developers app

PJcastaldo said:
sounds like another " I swear i didn't do anything.. it just happened" story.. classic..
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
I know my story sounds unlikely, but it's the truth. Isn't this forum around to help fellow users? I have no reason to lie here. I actually take very good care of my phone and (after almost losing a laptop to a water spill) am extremely cautious about liquids around my electronic devices. You don't have to believe me since I'll get my phone replaced regardless. I just thought I would share the information in case someone else ends up facing the same problem.
Even now, the only cause I can come up with still is the old power strip frying the motherboard. *shrug* I would love to hear any other explanations.

[Q] Bricked GS3, phone is powered off and unresponsive

Think I just borked by AT&T Galaxy S3, and yes it is completely my fault. This is probably a dead end, buy I figured I'd ask as a last resort.
I've got a lot of experience rooting and flashing ROMS and flashing custom recoveries and was rushing a proceedure when the problem occurred. I was trying to flash the CWM touch recovery using the instructions here: http://forum.xda-developers.com/showthread.php?t=1739426
I tried to do all this through my phone using Terminal Emulator and typed in the portion "mmcblk0p18" one letter off from what I should have (I think I typed in "mmcblk0p08" ... sick sinking feeling my stomach right now). The code went through as I started to power down the phone as I was looking at the code I wrote. Noticed the mispelled line of code right as the screen was powering off. Now my phone is completely unresponsive, after I rebooted. The phone does not power on, cannot boot into recovery mode, and worst of all seemingly will not boot into download mode. I've had boot loops before and am familiar with how to traditionally boot into Download mode via POWER + Vol Down + Home Button and used Odin to flash a fix.
Are there any other options, short of taking it to a repair shop, that I can try? I'm guessing it's completely bricked, but I just wanted to see if there were any options I was missing that are worth trying.
About to start calling repair shops to see if they can take a look at it as well.

Warranty replacement. Just say you don't know why it won't turn on. I did this after dropping my rooted phone and they asked no questions.

On the phone now, I'll let you know if they're able to assist with troubleshooting or otherwise.

I did the same thing.... I had insurance through att reported the phone lost... I repeat lost not stolen.. Got a replacement in 2 days brand new white and used that to pull the stock rom and flash it to my old phone. The then turned around and sold the replacement phone
Sent from my SGH-I747M using xda premium

That doesn't make sense why the phone won't even turn on, were you trying to flash on a low battery?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2

Mphill46 said:
That doesn't make sense why the phone won't even turn on, were you trying to flash on a low battery?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
I agree that it doesn't make sense. It's behaving almost as if the battery is just flat out dead. I have a spare battery, but when I tried that one it made no difference. I plugged the phone into a couple of different chargers while the AT&T rep was helping me troubleshoot and the charging light wouldn't turn on. The phone was not responding to anything at all, no matter what we tried.
They declared it hardware failure and are sending a replacement, as part of the original warranty. It did not have any physical damage, scratches, no water damage, etc.
Let this be a lesson to others: Be very very VERY careful with ADB and read your commands carefully. Those warnings about bricking your phone are real and shouldn't be taken lightly. I've rooted 6 devices and flashed what I'd estimate as over 60 ROMs over all my Android devices. I let my guard down and rushed things, and really my carelessness is all to blame at this point.

[Q] My Note 2 has died. Help?

My Note 2 has just died It was getting surprisingly laggy at odd moments in the past week, but I didn't think anything was wrong. I was updating a lot of applications one after another tonight (music was playing but it was jumpy, i think because apps were updating so i stopped music) and people were messaging me on the facebook app so I could see the notification light flash green. I was busy on my laptop, so I ignored the phone about 10 mins.
The green light kept flashing, but the screen wouldn't turn on when i pressed home or power key. so i took the battery out from the back and reinserted it. It wouldn't switch on at all, no SGS Note 2, no Samsung logo. nothing at all except a little red light flashing where the infrared light is everytime i tried to turn it on.
I tried connecting it to my computer. nothing happened. recovery mode bootup also failed. I tried charging the phone, even though the battery wasn't empty, still wouldn't switch on during charger plugged in or pulled out. Took out SD/Sim, no effect. A new battery didn't help. The phone doesn't charge either, the charger makes a funny electrical whining noise and the infrared red light flashes every so often.
It's basically dead. What can I do? The phone is also rooted, I can't remember how (think it's original chainfire root? i got my phone last oct). Will Samsung be able to switch on my phone and discover it's rooted? Also I read somewhere that legally speaking if rooting didn't cause the failure, you're still covered by EU law?
I am in the UK, bought Note 2 off a 3rd party reseller (Buymobilephones) who provided a handset, and T-Mobile for the contract.
Thanks

jeanclaudevandamme said:
My Note 2 has just died It was getting surprisingly laggy at odd moments in the past week, but I didn't think anything was wrong. I was updating a lot of applications one after another tonight (music was playing but it was jumpy, i think because apps were updating so i stopped music) and people were messaging me on the facebook app so I could see the notification light flash green. I was busy on my laptop, so I ignored the phone about 10 mins.
The green light kept flashing, but the screen wouldn't turn on when i pressed home or power key. so i took the battery out from the back and reinserted it. It wouldn't switch on at all, no SGS Note 2, no Samsung logo. nothing at all except a little red light flashing where the infrared light is everytime i tried to turn it on.
I tried connecting it to my computer. nothing happened. recovery mode bootup also failed. I tried charging the phone, even though the battery wasn't empty, still wouldn't switch on during charger plugged in or pulled out. Took out SD/Sim, no effect. A new battery didn't help. The phone doesn't charge either, the charger makes a funny electrical whining noise and the infrared red light flashes every so often.
It's basically dead. What can I do? The phone is also rooted, I can't remember how (think it's original chainfire root? i got my phone last oct). Will Samsung be able to switch on my phone and discover it's rooted? Also I read somewhere that legally speaking if rooting didn't cause the failure, you're still covered by EU law?
I am in the UK, bought Note 2 off a 3rd party reseller (Buymobilephones) who provided a handset, and T-Mobile for the contract.
Thanks
Click to expand...
Click to collapse
I wish you a Good luck then.

jeanclaudevandamme said:
My Note 2 has just died It was getting surprisingly laggy at odd moments in the past week, but I didn't think anything was wrong. I was updating a lot of applications one after another tonight (music was playing but it was jumpy, i think because apps were updating so i stopped music) and people were messaging me on the facebook app so I could see the notification light flash green. I was busy on my laptop, so I ignored the phone about 10 mins.
The green light kept flashing, but the screen wouldn't turn on when i pressed home or power key. so i took the battery out from the back and reinserted it. It wouldn't switch on at all, no SGS Note 2, no Samsung logo. nothing at all except a little red light flashing where the infrared light is everytime i tried to turn it on.
I tried connecting it to my computer. nothing happened. recovery mode bootup also failed. I tried charging the phone, even though the battery wasn't empty, still wouldn't switch on during charger plugged in or pulled out. Took out SD/Sim, no effect. A new battery didn't help. The phone doesn't charge either, the charger makes a funny electrical whining noise and the infrared red light flashes every so often.
It's basically dead. What can I do? The phone is also rooted, I can't remember how (think it's original chainfire root? i got my phone last oct). Will Samsung be able to switch on my phone and discover it's rooted? Also I read somewhere that legally speaking if rooting didn't cause the failure, you're still covered by EU law?
I am in the UK, bought Note 2 off a 3rd party reseller (Buymobilephones) who provided a handset, and T-Mobile for the contract.
Thanks
Click to expand...
Click to collapse
How long ago did you buy the phone?
If you were rooted, were you on stock rom?
If yes, than which build were you on, do you remember?
I have heard of phones dying from sds, were you on an older rom. If that is the case, and if you have hard bricked your phone, AND if you are under warranty you need not fear...the guys at samsung wouldn't be able to open your phone either to check whether its rooted or not, you are covered. Your phone would require a motherboard rwplacement 8n that case. I hope you had backups.
Sent from my GT-N7100 or the Nexus 10, heaven knows.
Those who help noobs go to heaven. True story.

SacGuru said:
How long ago did you buy the phone?
If you were rooted, were you on stock rom?
If yes, than which build were you on, do you remember?
I have heard of phones dying from sds, were you on an older rom. If that is the case, and if you have hard bricked your phone, AND if you are under warranty you need not fear...the guys at samsung wouldn't be able to open your phone either to check whether its rooted or not, you are covered. Your phone would require a motherboard rwplacement 8n that case. I hope you had backups.
Sent from my GT-N7100 or the Nexus 10, heaven knows.
Those who help noobs go to heaven. True story.
Click to expand...
Click to collapse
I bought it at end of last october, 1st gen/batch of Note 2s to hit the UK (IMEI starts with 354.....
I was rooted. The first auto-root Chainfire method via Odin.
Stock samsung rom. Very earliest versions of software.
I basically bought the phone last year when it first came out, rooted it as soon as possible and then did nothing else except enjoying my phone and install new apps. Whatever people were rooting/flashing/roms/kernels etc at the end of last october when the note 2 first came out in the uk is what I would have been on. Never updated since.
I might sound a bit stupid, but does a motherboard change means you lose everything in internal storage? ie photos, texts, contacts etc. I have no backups of anything. my fault I know. And Samsung wont' detect root after motherboard has been changed?
When you say "hardbricked", do you just mean it wont' physically and electrically turn on? Because i didn't interrupt rooting/flashing etc.
I googled SDS for the Note 2. Seems there is an issue I can't think how else my phone would just die.

jeanclaudevandamme said:
I bought it at end of last october, 1st gen/batch of Note 2s to hit the UK (IMEI starts with 354.....
I was rooted. The first auto-root Chainfire method via Odin.
Stock samsung rom. Very earliest versions of software.
I basically bought the phone last year when it first came out, rooted it as soon as possible and then did nothing else except enjoying my phone and install new apps. Whatever people were rooting/flashing/roms/kernels etc at the end of last october when the note 2 first came out in the uk is what I would have been on. Never updated since.
I might sound a bit stupid, but does a motherboard change means you lose everything in internal storage? ie photos, texts, contacts etc. I have no backups of anything. my fault I know. And Samsung wont' detect root after motherboard has been changed?
When you say "hardbricked", do you just mean it wont' physically and electrically turn on? Because i didn't interrupt rooting/flashing etc.
I googled SDS for the Note 2. Seems there is an issue I can't think how else my phone would just die.
Click to expand...
Click to collapse
I think we know the cause now, its sds. Only roms and kernels which have been developed after January 2013 are free of this problem. As you had rooted very early you would not have recieved stock updates from samsung. And as you had not flashed anything new, the rom/kernel you used had the sds problem. Had you recieved stock updates or had you flashed any latest rom your device would most probably be working.
Now the good news is, as I said, samsung has no way of learning whether your phone was rooted or not. A soft brick is when your phone is in a bootloop. A hardbrick means it wont't turn on, won't do anything at all. Your phone is hardbricked in a way. So a samsung engineer would be as powerless to turn your phone on in this condition as you are. And thus, you would be under warranty.
The bad news is, yes, all the data on your internal storage is gone. The phone you would be provided would be a new factory reset model altogether. That is of course, if the problem is sds, as it seems right now. Even if the problem is different, something smaller, a factory reset is what you will get in all probability, so no chance of saving the data.
I am really sorry for your data, and I know it doesn't help when I play Captain Hindsight, but you should have made a titanium and nandroid backup at the very least. Do that for your next phone regularly. It is the most useful aspect of rooting your phone if you ask me.
Of course, I could be wrong here. The problem could be something smaller. I suggest you throw this problem @dr.ketan on this thread
http://forum.xda-developers.com/showthread.php?t=1896696
He knows a lot more than I do and can confirm this.
Also, do press thanks if I helped
Sent from my GT-N7100 or the Nexus 10, heaven knows.
Those who help noobs go to heaven. True story.

[Q] I think it's bricked?

So my phone running CM 10.1, turned off randomly. So I tried to reboot but kept getting stuck on the Samsung boot logo. I rebooted to CWM recovery mode, wiped cache and dalvik and rebooted which I thought would fix the problem somehow which it did. However, when it said "Android upgrading, optimizing apps", my phone lost battery (thought the phone charger was plugged in). When I plugged it in the outlet properly this time, I got through the battery charging logo. But when I tried turning it on afterwards, nothing. The phone doesn't respond when I tried to turn it on. Took the battery off, placed it back and when I plug it into the outlet, there is no more battery charging logo and I can no longer reboot. How can I fix this? Somehow, the phone might be trying to continue to turn on but is not responding when I try to actually turn it on. When I plug the charger, take off the battery, unplug and replug charger, the battery charging led lights up for 5 minutes (which is weird cause I disabled the indicator led when charging in the system settings). I allowed it to be plugged in to the charger overnight and when I checked this morning, nothing. No symptoms that it was charging; no heat on the phone. Is not being able to charge a symptom of a bricked phone. I have yet to try using another battery.

If you can't power on or get to DL mode or anything and none of the buttons respond it could be a hard brick
Check here:
http://forum.xda-developers.com/showthread.php?t=2369125
Sent from my SPH-L710 using xda app-developers app

I checked at a Sprint store and the device they have couldn't make a reading off my battery meaning it was most likely dead. I'm gonna try with a new battery and hopefully my phone isn't actually bricked.

Best of luck sir
Sent from my SPH-L710 using xda app-developers app

Ah, just my luck. A Sprint representative placed another battery on it (I didn't see it though) and told me that the phone still won't turn on and told me he can open and check the phone if I pay. So, I think it is hard bricked. :crying: How did I brick it? Ugh..I'm just dismayed on the information and data I lost. What are my options? I heard Mobiletechvideos.com does a jtag brick repair with an option for internal sd card recovery?

bonsly16 said:
Ah, just my luck. A Sprint representative placed another battery on it (I didn't see it though) and told me that the phone still won't turn on and told me he can open and check the phone if I pay. So, I think it is hard bricked. :crying: How did I brick it? Ugh..I'm just dismayed on the information and data I lost. What are my options? I heard Mobiletechvideos.com does a jtag brick repair with an option for internal sd card recovery?
Click to expand...
Click to collapse
I had to get a JTAG when I flashed a wrong kernel. Although when I got it back I had lost nothing still had custom ROM and recovery and all my data and apps were there. If its hard bricked its because something happened to the bootloader
Sent from my SPH-L710 using xda app-developers app

IDontKnowMang said:
I had to get a JTAG when I flashed a wrong kernel. Although when I got it back I had lost nothing still had custom ROM and recovery and all my data and apps were there. If its hard bricked its because something happened to the bootloader
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
How can I know if I need a JTAG or my phone need an eMMC Chip Repair Replacement. What if my phone experienced a sudden death. If it's the latter, it's expensive as the website lists it for $150, almost the price of a new two-year contract phone.
Oh well, I'll send it in anyways for a jtag. Hopefully they can fix it.

bonsly16 said:
How can I know if I need a JTAG or my phone need an eMMC Chip Repair Replacement. What if my phone experienced a sudden death. If it's the latter, it's expensive as the website lists it for $150, almost the price of a new two-year contract phone.
Oh well, I'll send it in anyways for a jtag. Hopefully they can fix it.
Click to expand...
Click to collapse
Its kind if hard to say if this was a brick or not. Usually sudden death is out of the blue, as far as I know the only way to achieve a hard brick is flashing a bad or international zip file
What's 150$ though? The emmc or the jtag
Sent from my SPH-L710 using xda app-developers app

I just experienced a similar problem as OP, and I didn't even flash a new ROM or international ROM. Since January, I've been using the ICS version of FreeGS3, stock kernel.
http://forum.xda-developers.com/showthread.php?t=1748818
I haven't flashed any new ROM's since January 2013 and have not experienced any problems until now.
This morning, however, when I woke up, I discovered that my Sprint S3 was stuck on the "Samsung Galaxy S III" logo. I pulled the battery and powered up, and it got stuck on the same logo again. I repeated this process several times and the same thing happened. After looking at some XDA threads, I went into recovery and decided to wipe cache and dalvik to see if that fixed anything. Again, the phone booted up and got stuck on the "Samsung Galaxy S III" logo again.
However, when I tried to boot into recovery again, I wasn't able to do so. I tried several times without any luck. I decided to see if I could put the phone into download mode. I did, and it was successful. I didn't do anything just yet because I needed to research more fixes before seeing what needed to be done. I put the phone into download mode several times without doing anything, but then later, the phone itself wouldn't power on.
No matter what combination of buttons I pressed, the phone simply wouldn't power on. I even tried other batteries which I knew were fully charged. When I put the phone on the charger or plug it into my PC, no charging lights light up. However, when I pull the battery an plug the phone into my PC, the charging light lights up and it the PC seems to try to install drivers. However, despite the charging light lighting up with the battery pulled, but phone plugged into the PC, I still can't get the phone to power on at all and therefore can't get into recovery or download mode.
It's similar to the problem the person in this video is having where he uses a jig to get back into download mode.
http://youtu.be/FdrdWqaXUBE
I have a jig on the way, so hopefully that helps fix my problems, but I don't really understand how the phone got bricked in the first place; First it was soft bricked when it got stuck on the "Samsung Galaxy S III" logo, but I was still able to get into recovery and download mode. Then, it was hard bricked when it wouldn't even power on to get into recovery or download mode. Did it get hard bricked because I went into download mode too many times? What might have caused it to be soft bricked. The thread for my ROM is now closed, so I don't know where else to ask these questions. I'll update you as I try to fix this problem. Any other suggestions are welcome.

Your device is not bricked your device doesn't even have a software failure. What you are describing is SDS sudden death syndrome.
Your power button has failed. It's defective and the manufacturer knows it. It fails at the motherboard not the physical button itself. Since you where able to get into download mode I suggest you return the device to stock unrooted, do a triangle away function and take it to Sprint. They usually repair of exchange it for you.
Have a great day!

edfunkycold said:
Your device is not bricked your device doesn't even have a software failure. What you are describing is SDS sudden death syndrome.
Your power button has failed. It's defective and the manufacturer knows it. It fails at the motherboard not the physical button itself. Since you where able to get into download mode I suggest you return the device to stock unrooted, do a triangle away function and take it to Sprint. They usually repair of exchange it for you.
Have a great day!
Click to expand...
Click to collapse
Hmm...I suggest you are talking about the other poster since I am not able to power it on at all (Recovery nor Download mode). I don't have insurance nor have warranty, I don't think Sprint would be able to fix it without me paying an incredibly huge amount. I was hoping that my data would be recovered but now that you mention the possibility of sudden death syndrome, there's no way I can recover the data if it is. A sudden death syndrome would require a replacement of the eMMC which is rather costly.

@bonsly16 My apologies yes my reply was to Lawyerman... But you do have an alternative option, http://forum.xda-developers.com/showthread.php?p=43724690 many have had success and in many cases everything was there for them.
Have a great day!

[Q] tried flasing rom and phone is dead..

i got a samsung gs3 yesterday, i loved everything but battery life, lastnight i used George Holtz's "towel root" and rooted my phone, added super user and rom toolbox, upgraded my recovery to clockwork mod basic, and proceded to flash to "flashingdroid version 2.2" it went thru everything and installed the rom, when it tried to reboot, it went black... now it does nothing, computer tries to recognize it, abut i cant get it to download mode, and i cant get it into recovery mode... it does not show charge picture when plugged in and if i take the battery out, plug it in, then insert the battery i get a red light... PLEASE HELP!!!!!!!

noobbrokes3 said:
i got a samsung gs3 yesterday, i loved everything but battery life, lastnight i used George Holtz's "towel root" and rooted my phone, added super user and rom toolbox, upgraded my recovery to clockwork mod basic, and proceded to flash to "flashingdroid version 2.2" it went thru everything and installed the rom, when it tried to reboot, it went black... now it does nothing, computer tries to recognize it, abut i cant get it to download mode, and i cant get it into recovery mode... it does not show charge picture when plugged in and if i take the battery out, plug it in, then insert the battery i get a red light... PLEASE HELP!!!!!!!
Click to expand...
Click to collapse
What model is your phone? You flashed a i9300 ROM, this is the sub-forum for the i747.

its the i747, i before looking today never knew there were more than 1 model of the GS3, is it possible to fix it?

This may help:
http://forum.xda-developers.com/showthread.php?t=2549068

audit13 said:
This may help:
http://forum.xda-developers.com/showthread.php?t=2549068
Click to expand...
Click to collapse
my problem is my phone does NOT vibrate when power button is pressed, it isnt doing ANYTHING at ALL, the red charging light only comes on when battery is left out and the phone is plugged in, light turns off after a minute or so of the battery being installed, to me it seems like less rom flash related, and more failure in the board, but im not good at this stuff so im probably wrong, i bought a verizon one (i535) for 50 bucks (pretty banged up touchscreen is cracked in several places i got it without a back cover,but it works,) to get me by but i miss my 4g on straight talk =( i wish i had just left it alone, it was clean just 1 crack in the touch screen wires ans such for lcdanddigitizer got cut by accient while trying to modify midframe for verizon board, i sure as hell cant afford the att version for a while 150-260 for a decent i747, is it possible that a JTAG service would be able to bring it to life or even one of those dongles to force recovery?

noobbrokes3 said:
my problem is my phone does NOT vibrate when power button is pressed, it isnt doing ANYTHING at ALL, the red charging light only comes on when battery is left out and the phone is plugged in, light turns off after a minute or so of the battery being installed, to me it seems like less rom flash related, and more failure in the board, but im not good at this stuff so im probably wrong, i bought a verizon one (i535) for 50 bucks (pretty banged up touchscreen is cracked in several places i got it without a back cover,but it works,) to get me by but i miss my 4g on straight talk =( i wish i had just left it alone, it was clean just 1 crack in the touch screen wires ans such for lcdanddigitizer got cut by accient while trying to modify midframe for verizon board, i sure as hell cant afford the att version for a while 150-260 for a decent i747, is it possible that a JTAG service would be able to bring it to life or even one of those dongles to force recovery?
Click to expand...
Click to collapse
It could be a board failure but it happened right after you flashed the ROM which leads me to believe it is software related.
A dongle is not going to help since the phone won't even power up. A jtag service would be your best and quickest option. You should try and find a shop that will guarantee to revive the phone or you pay nothing.
This might help with your current phone: http://www.xda-developers.com/android/how-to-make-your-verizon-galaxy-s-iii-a-world-phone/

noobbrokes3 said:
my problem is my phone does NOT vibrate when power button is pressed, it isnt doing ANYTHING at ALL, the red charging light only comes on when battery is left out and the phone is plugged in, light turns off after a minute or so of the battery being installed, to me it seems like less rom flash related, and more failure in the board, but im not good at this stuff so im probably wrong, i bought a verizon one (i535) for 50 bucks (pretty banged up touchscreen is cracked in several places i got it without a back cover,but it works,) to get me by but i miss my 4g on straight talk =( i wish i had just left it alone, it was clean just 1 crack in the touch screen wires ans such for lcdanddigitizer got cut by accient while trying to modify midframe for verizon board, i sure as hell cant afford the att version for a while 150-260 for a decent i747, is it possible that a JTAG service would be able to bring it to life or even one of those dongles to force recovery?
Click to expand...
Click to collapse
Flashing an i9300 rom is guaranteed to hard brick the device and cause exactly what you described. If you follow the instructions in the thread linked in an above post it probably has a 90% chance of fixing it.
I am 99% certain it is not a hardware failure. Others have done the exact same thing and were able to fix it by using the instructions in that thread.

audit13 said:
It could be a board failure but it happened right after you flashed the ROM which leads me to believe it is software related.
A dongle is not going to help since the phone won't even power up. A jtag service would be your best and quickest option. You should try and find a shop that will guarantee to revive the phone or you pay nothing.
This might help with your current phone: http://www.xda-developers.com/android/how-to-make-your-verizon-galaxy-s-iii-a-world-phone/
Click to expand...
Click to collapse
i found one on ebay, full refund short of a 5 dollar shipping cost for return shipping, once i have money that i can spend ill sure as hell be giving it a shot

Or you can attempt to fix it for free.....but I suppose that is up to you.

DocHoliday77 said:
Or you can attempt to fix it for free.....but I suppose that is up to you.
Click to expand...
Click to collapse
either way its gonna cost me a little cash, i dont have a 16 gig sd card, forgive me for being so noob but the sd card trick CAN work for my case?? i know for a fact i cant do anythingto my phone right now as it wont even power on, but if you BELIEVE it will work ill gove it a try

Unless you updated with the kk ota, you are probably on 4.3 firmware. I cannot guarantee it will work, but I believe the chances are pretty good that it will.
Just remember, if it doesn't work, dont give up on the first try. Many have had to run through the process several times before it would actually boot up again.
The only other tip I can think to give is to make sure you buy a decent sd card. It doesn't have to be top of the line, but there are tons of fake ones out there that would be less likely to work. If you can, try to buy one from an authorized dealer for whatever brand you are considering. This greatly reduces the chance of getting a bad card.

DocHoliday77 said:
Unless you updated with the kk ota, you are probably on 4.3 firmware. I cannot guarantee it will work, but I believe the chances are pretty good that it will.
Just remember, if it doesn't work, dont give up on the first try. Many have had to run through the process several times before it would actually boot up again.
The only other tip I can think to give is to make sure you buy a decent sd card. It doesn't have to be top of the line, but there are tons of fake ones out there that would be less likely to work. If you can, try to buy one from an authorized dealer for whatever brand you are considering. This greatly reduces the chance of getting a bad card.
Click to expand...
Click to collapse
4.0.x was the last firmware, i never got to update it. i bought a PNY 16gb microSD HC class 4, it was 25 bucks at the local drug store, i was hoping for a class 6 - 10 but i believe it is a good quality card, maybe you would know better?

I won't lie, I am not a big fan of PNY, but as long as its the real thing, I think it should work. Class 6 or better is recommended, but it has worked on class 4 cards too. At this point, the only thing left to do is give it a shot. Good luck!