Several months ago, I rooted my wife's SGSIII (SPH-L710), running stock...
She charges it overnight, but this morning when she started using it, it rebooted itself. However, it would not boot past the Galaxy S3 logo. She took it to the Sprint store and they tried to do a hard reset and I think they tried to reflash the firmware. Afterward, they asked her if it had been rooted and she told them yes. They gave it back to her once they heard this.
Since then, I have been trying to re-flash the stock ROM per Question 2 in the Sprint Galaxy S3 FAQ.
I can get the phone into download mode, and I have a good USB cable. Odin (v3.06) recognizes the phone, but errors out with the message "Complete(Write) operation failed." I have tried other versions of Odin, different computers and cables, but no combination has got this far. I have searched the forums for a similar situation, but have had no luck. At this point, I could really use some help.
Some questions
1. Could the Sprint tech have hard-bricked the phone by flashing stock firmware?
2. In trying to resolve this, I have seen mention of flashing a Partition Information Table (PIT) file. Could this file be corrupt and is there a how-to on restoring it on the Sprint variant of the SGSIII?
3. I am starting to wonder if my only options are the guide, Unbrick a Hard Bricked SPRINT Galaxy S3 (Without JTAG) or worst-case, a JTAG fix. Does anyone think it has come to this?
[UPDATE 1] OK, I got it to work. Thanks to this post.
[UPDATE 2] Was able to get it to boot into the home screen, but it shut off after a few seconds. It did this a few times, but now it won't come on at all.
The phones power button has failed.. That's what went wrong with it, that's why it shuts off. It's known as SDS sudden death syndrome. Common issue with S3 it's a defect. If you can get it all flashed to stock take it to sprint hey usually replace it.
Sent from the future via Tapatalk 4
I was unable to power on the phone. We rolled the dice and took it to the Sprint store. Fortunately, the tech was unable to get the phone to work either. So, it was covered by the insurance. At first, the salesman said they'd have to order a refurbished phone as a replacement, but they were on backorder at the warehouse. So he gave us a new SGSIII. Maybe I should have bought a lottery ticket too.
Sent from my Nexus 7 using XDA Premium 4 mobile app
You lucky duck.
Related
Hey guys,
I did some searching but I couldn't find anything 100%
So I bricked my phone last week and I got my replacement in this week.
The error I got was regarding the "qualcom interface drivers"
I dont remember the specific error, I just remember texting that to my friend.
From my searches it shows that im SOL on that error. So that's why I got a replacement.
I can't get it to download mode, I can't get it to charge, I can't get the computer to recognize it.
Should I worry about resetting my counters and getting it back to stock rom?
I bricked mine by trying to install a ROM from the "euro" galaxy sII, and had no problems or charge back. I'm not sure they really care, so long as it's physically in good condition; that easy the just re-load the stock firmware then sell it as a reman.
Sent from my SGH-T989 using xda premium
Thanks for the reply zak, thats what I figured since they sent me a refurb anyways.
Hey guys,
Kind of an interesting question here. I've had my GS3 since summer and it's been running great. I was on a custom ROM with root (done without tripping binary), so it still says Samsung official and 0 flashes on the download screen, but it does say "custom" on the system status. Anyway, I hadn't done anything with flashing in several months. But the other day my phone just shut off and wouldn't turn back on. When I try, it vibrates, goes to the samsung splash screen, then shuts back down. Doesn't matter what I do, it won't get further than this. Can't boot into recovery or download mode with the button combos either. Won't read it on the computer or anything either. So I went out today and made a jig, thinking this would help. Well, it kind of did. It boots it into download for about five seconds, then shuts back off. So it's not enough time for me to get it to the computer and flash the stock ROM through Odin. I was thinking about trying to send it in to Samsung for warranty claim, because I had seen that people had luck with this when this was happening to a lot of GS3s in December. On several forums people said that Samsung was doing it no questions asked, regardless of root because they knew it was a hardware problem. So my question was just whether anyone here had any experience with it/Samsung? Or whether you guys thought I would be smarter to try and do it with AT&T? Anyway, thanks a lot for your time and input.
xThaNaturalx said:
Hey guys,
Kind of an interesting question here. I've had my GS3 since summer and it's been running great. I was on a custom ROM with root (done without tripping binary), so it still says Samsung official and 0 flashes on the download screen, but it does say "custom" on the system status. Anyway, I hadn't done anything with flashing in several months. But the other day my phone just shut off and wouldn't turn back on. When I try, it vibrates, goes to the samsung splash screen, then shuts back down. Doesn't matter what I do, it won't get further than this. Can't boot into recovery or download mode with the button combos either. Won't read it on the computer or anything either. So I went out today and made a jig, thinking this would help. Well, it kind of did. It boots it into download for about five seconds, then shuts back off. So it's not enough time for me to get it to the computer and flash the stock ROM through Odin. I was thinking about trying to send it in to Samsung for warranty claim, because I had seen that people had luck with this when this was happening to a lot of GS3s in December. On several forums people said that Samsung was doing it no questions asked, regardless of root because they knew it was a hardware problem. So my question was just whether anyone here had any experience with it/Samsung? Or whether you guys thought I would be smarter to try and do it with AT&T? Anyway, thanks a lot for your time and input.
Click to expand...
Click to collapse
Did you get a new battery? Worth a try. AT&T might get you one on the spot to try at a corporate store. Otherwise I doubt AT&T will be able to tell if you rooted if you can't boot up.
aybarrap1 said:
Did you get a new battery? Worth a try. AT&T might get you one on the spot to try at a corporate store. Otherwise I doubt AT&T will be able to tell if you rooted if you can't boot up.
Click to expand...
Click to collapse
Absolutely true, but if its not the battery the atat rep will point you to an atat service center for assistance and its a safe bet that they have a few more tools at their disposal to troubleshoot the phone. If they somehow see any system modification, you are capital F****d. Do you have the wireless insurance with atat? I just dealt with this except I dropped the phone, shattered the screen and it would only power on for 10 mins at a time and then reboot. I paid my $$$ deductable and sent the broken phone to the insurance provider and yes the system still showed as being "modified" when I sent it to them.
Sent from my Atat S3 that now thinks its a Galaxy Nexus........
I would send your s3 to Samsung if it still under warranty. I sent over my bricked s3 and they fixed it.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Ok so, I just did a trade on Craigslist recently and got an S3 from Verizon, clean ESN and all, it just had a cracked screen. Well the guy had already bought a replacement he just didn't know how to do it. Did the trade, got home and completed the screen repair. Works great, well it boots up, but here are my problems....
1. Phone is PIN locked and I don't know it and he can't get a hold of the guy he got it from.
2. It will not boot into anything but normal, no Download mode, no Recovery, nothing.
3. Windows doesn't recognize it. At one point in my 100+ times of connecting and disconnecting it, it did recognize it and was going to install the drivers for it and then it said device unplugged, which it hadn't been.
So now I come to the great world of XDA and see if we can't solve this issue together. Anyone have any ideas? I have tried 4 different USB cables as well. All of which work with my current S3.
Tried this over at the Verizon xda forums and have gotten little response...thought I would try here as well.
Only other thing I can think of is to make a JIG and hope for the best...
Thanks
If it is Pin locked I don't think there is nothing you can do. You should try to contact the seller and return it to him and get a refund. The original owner could claim Stolen phone and you are stuck with a paper weight.
Post this in the Verizon section. You have a different device model than is covered by this forum.
Make sure you're using the Verizon instructions to enter recovery, they are different.
Sent from my SGH-T999 using xda app-developers app
I have a 9 month old S3 (T999/Canadian/Mobilicity Variant)
I had a ROM on there since day 2, but recently *this week* had a lot of hard lock ups. I could manage a reboot if I pulled the battery.
I tried 3 diff roms CM10, AOKP, and a recent 4.1.1 (all without apps) all worked but still caused the hard lock requiring a reboot.
It was annoying as you know what, but I was testing diff options wondering if the lockups were the OS/an app/or hardware.
Last night the phone was working on AOKP 4.2.2 while on the charger. I woke up and noticed it was hard locked, so I batt pulled, rebooted and went to sleep.
Now (this morning) it wont boot at all. I thought maybe it was the charger or the battery. I swapped batteries with a different S3, mine still does not boot.
So. What now?
Time for S4 and lose a $600 phone? Time to go to a Samsung or Carrier shop?
Have you tried Odin? Plug it into a computer see if things register if so go further with Odin.
I'd say that and see if it persist while on a stock then don't install your apps, if problem still persist call Samsung or whom ever and see about that. Or get it up and running and if steady put on Craigslist then get s4....
T-Mobile SGS III
mt3g said:
Have you tried Odin? Plug it into a computer see if things register if so go further with Odin.
I'd say that and see if it persist while on a stock then don't install your apps, if problem still persist call Samsung or whom ever and see about that. Or get it up and running and if steady put on Craigslist then get s4....
T-Mobile SGS III
Click to expand...
Click to collapse
It used to be that when connected to PC Device man said: SGH-T999
Now the phone is connected via usb cable, but isnt booted and it says: QHSUSB_DLOAD
AMRivlin said:
It used to be that when connected to PC Device man said: SGH-T999
Now the phone is connected via usb cable, but isnt booted and it says: QHSUSB_DLOAD
Click to expand...
Click to collapse
Google search that piece "QHSUSB_DLOAD" and see what it is. I've never seen that. Install Odin (in the dev section) and see what happens (read that thread) I'm at work on mobile or I'd give you links. Just a little reading and no panicking and you might get out of this alive lol.
T-Mobile SGS III
mt3g said:
Google search that piece "QHSUSB_DLOAD" and see what it is. I've never seen that. Install Odin (in the dev section) and see what happens (read that thread) I'm at work on mobile or I'd give you links. Just a little reading and no panicking and you might get out of this alive lol.
T-Mobile SGS III
Click to expand...
Click to collapse
QHSUSB_DLOAD means your need JTAG. Because it's bricked.
mt3g said:
Google search that piece "QHSUSB_DLOAD" and see what it is. I've never seen that. Install Odin (in the dev section) and see what happens (read that thread) I'm at work on mobile or I'd give you links. Just a little reading and no panicking and you might get out of this alive lol.
T-Mobile SGS III
Click to expand...
Click to collapse
That is found on XDA and the interwebs as a bricked device. it applies to captivate/HTC/s3 others.
I downloaded odin, but I can't get into download mode Power+Home+VDown (Nothing happens)
I didn't flash an incorrect ROM, since my phone was working, it bricked itself over night? Power Surge?
Aerowinder, if I am under warranty, can i take it to my carrier/samsung for repair? I can't get into Download mode.
Call them up and find out. It might be failing/tired internals/hardware... Did you have your phone over clocked at all in the 9 months, just curious?
T-Mobile SGS III
AMRivlin said:
Aerowinder, if I am under warranty, can i take it to my carrier/samsung for repair? I can't get into Download mode.
Click to expand...
Click to collapse
I had the exact same problem and was still under the warranty and they exchanged it. I just told them that I plugged my phone before going to bed and when I woke up I wasn't able to turn it back on.
I actually remember this now. This a bug not common but its here for users on all D2 SIII decices... They've publically admitted it
T-Mobile SGS III
No over clocking.
Jan-April 30th Touchwiz 4.1.1 (Frosty ROM) Lockups Started monday (No Changes)
May 1 AOPK 4.2.2 ROM (Hard Lock/Brick today)
Time to find a receipt
AMRivlin said:
No over clocking.
Jan-April 30th Touchwiz 4.1.1 (Frosty ROM) Lockups Started monday (No Changes)
May 1 AOPK 4.2.2 ROM (Hard Lock/Brick today)
Time to find a receipt
Click to expand...
Click to collapse
Ya I suggest just avoiding the headache of trying to fix, tell them you plugged it in over night to charge and now its completely dead and that its been acting weird for a while before. You should be good.
T-Mobile SGS III
rener78 said:
I had the exact same problem and was still under the warranty and they exchanged it. I just told them that I plugged my phone before going to bed and when I woke up I wasn't able to turn it back on.
Click to expand...
Click to collapse
Not sure how this is going to turn out. The carrier refused to do the warranty, and gave me the # to samsung canada. I went to the Samsung Canada store, where they took the phone and gave me a GNexus (loaner)
So... lets hope they dont see the romming, my triangle should be 0.
If they do figure out my romming and their quote to fix is absurd, I will get HTC1 and repair the S3 on my own time.
I prefer Apple's warranty to be honest.
Does anyone know how much 3rd party Brick repair should cost? In the crap chance Samsung gets me for ROMing
AMRivlin said:
Does anyone know how much 3rd party Brick repair should cost? In the crap chance Samsung gets me for ROMing
Click to expand...
Click to collapse
Mobiletechvideos does it for $60.
http://mobiletechvideos.mybigcommerce.com/
Sent from my SGH-T999 using xda premium
Update:
7 days after submitting for service, the phone came back from a 3rd party repair shop in Burnaby, BC. PBA replaced due to bad BGA (Ball Grid Array)
So I guess they couldn't boot it to see the root.
Working fine. The new phone came back carrier locked, original unlock # worked again.
Da Kine said:
Mobiletechvideos does it for $60.
http://mobiletechvideos.mybigcommerce.com/
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Some kijiji advertisements are charging $49.99 same day repair.
ysr84 said:
Some kijiji advertisements are charging $49.99 same day repair.
Click to expand...
Click to collapse
Managed to get it repaired under warranty.
can u help me out
AMRivlin said:
Managed to get it repaired under warranty.
Click to expand...
Click to collapse
Did you buy the warranty when u bought the phone?
I have the same issue. But not sure where to send the galaxy too?
Please help coz the local stores were not able to help
JBn
Help
AMRivlin said:
I have a 9 month old S3 (T999/Canadian/Mobilicity Variant)
I had a ROM on there since day 2, but recently *this week* had a lot of hard lock ups. I could manage a reboot if I pulled the battery.
I tried 3 diff roms CM10, AOKP, and a recent 4.1.1 (all without apps) all worked but still caused the hard lock requiring a reboot.
It was annoying as you know what, but I was testing diff options wondering if the lockups were the OS/an app/or hardware.
Last night the phone was working on AOKP 4.2.2 while on the charger. I woke up and noticed it was hard locked, so I batt pulled, rebooted and went to sleep.
Now (this morning) it wont boot at all. I thought maybe it was the charger or the battery. I swapped batteries with a different S3, mine still does not boot.
So. What now?
Time for S4 and lose a $600 phone? Time to go to a Samsung or Carrier shop?
Click to expand...
Click to collapse
I Hard Bricked my Samsung Galaxy S3 and if you dont mention anything about rooting they will give you a new one no questions asked. Now if you dont have a warranty or some type of insurance then call samsung and see what you can do about it. i did a warranty exchange and i got a new one. As long as you dont mention brick or root you will be find they will right it down as defective.
I have been using this phone since 2 weeks of the initial release of the galaxy note 2. For years, there has been no problem whatsoever. A few weeks ago this happened:
1. Phone suddenly powered off and factory resetted. I was in the middle of using it. The only thing I installed recently at that time was pokemon GO, and uninstalled it a few days later (Because i have no friends to play with, lol). Luckily, i have backed up data before.
2. Phone started working normally again, then a few days later it just powered off again with no warning. I just left it for 5 minutes and that happened. It is now stuck on the "Galaxy Note II" screen. I haven't been able to get past that screen anymore.
3. I tried charging the phone, the only thing that popped up was the battery logo with the loading circle. No 5 dots at the bottom, no green battery.
What I have tried to fix this:
1. Factory resetting using Power+Menu+Volume up.
2. Flashing the stock ROM.
3. Using samsung kies.
4. Taking the phone to a samsung service center.
When i took it to the service center, the guy said that there is a "part" of it that is broken and needed to be replaced. That guy didn't specify what part it is and asked $180 for repairs. I said no, because that is the same as buying a used one right now. Also, the guy said that this is caused by using the phone while charging. Is this true?
Also, i found out that this might be caused by eMMC failure or something like that. Can you help me go through this?
TheSpartaGod said:
I have been using this phone since 2 weeks of the initial release of the galaxy note 2. For years, there has been no problem whatsoever. A few weeks ago this happened:
1. Phone suddenly powered off and factory resetted. I was in the middle of using it. The only thing I installed recently at that time was pokemon GO, and uninstalled it a few days later (Because i have no friends to play with, lol). Luckily, i have backed up data before.
2. Phone started working normally again, then a few days later it just powered off again with no warning. I just left it for 5 minutes and that happened. It is now stuck on the "Galaxy Note II" screen. I haven't been able to get past that screen anymore.
3. I tried charging the phone, the only thing that popped up was the battery logo with the loading circle. No 5 dots at the bottom, no green battery.
What I have tried to fix this:
1. Factory resetting using Power+Menu+Volume up.
2. Flashing the stock ROM.
3. Using samsung kies.
4. Taking the phone to a samsung service center.
When i took it to the service center, the guy said that there is a "part" of it that is broken and needed to be replaced. That guy didn't specify what part it is and asked $180 for repairs. I said no, because that is the same as buying a used one right now. Also, the guy said that this is caused by using the phone while charging. Is this true?
Also, i found out that this might be caused by eMMC failure or something like that. Can you help me go through this?
Click to expand...
Click to collapse
Hello
Im newbie
Try flashing stock ROM using Odin
Also you better use custom ROM like me I'm using cm13 right now , no problem at all
My phone got bricked before once I reset it
Try re flashing custom recovery
It might because of that .
The factory reset progress not finished
I flashed cwm then my phone boot up
After it works I'm using twrp instead
Sorry for my bad English hope you understand
Sent from my Samsung GT-N7100 using XDA Labs