[Q] Bootloop, recovery won't load and restore mod turns off - Sprint Samsung Galaxy S III

Trying to fix my daughters SGIII Sprint phone.
This morning it started going into a bootloop.
What I've tried:
1) Attempted CWM recovery by pressing (VOLUP+HOME+POWER). The screen flashing "SAMSUNG" with in small blue font in upper left "Reocery Starting..." And then the phone shuts off right away.
2) Attempted ODIN recovery by pressing (VOLDOWN+HOME+POWER). Once in download screen in ODIN I try and flash KIES_HOME_L710VPBLJ7_L710SPRBLJ7_329968_REV03_user_low_ship.tar.md5 but after a few seconds the phone just shuts off.
All in all I think if I can just get the phone to stop shutting down while in download mode I can at least flash something and this thing back up.

rattfink said:
Trying to fix my daughters SGIII Sprint phone.
This morning it started going into a bootloop.
What I've tried:
1) Attempted CWM recovery by pressing (VOLUP+HOME+POWER). The screen flashing "SAMSUNG" with in small blue font in upper left "Reocery Starting..." And then the phone shuts off right away.
2) Attempted ODIN recovery by pressing (VOLDOWN+HOME+POWER). Once in download screen in ODIN I try and flash KIES_HOME_L710VPBLJ7_L710SPRBLJ7_329968_REV03_user_low_ship.tar.md5 but after a few seconds the phone just shuts off.
All in all I think if I can just get the phone to stop shutting down while in download mode I can at least flash something and this thing back up.
Click to expand...
Click to collapse
Okay, so I had this problem and at the end of the day I had to turn it in to Samsung for warranty purposes because the phone would automatically turn off when on and then restart the boot process and turn off again. However, I found a temporary fix, if you pull out the battery wait for a while (like an hour) and put it back in, the phone should stay on longer so you can flash through Odin. The phone will no longer turn on normally because once you start the flash with Odin the boot.img has been flashed but it's a broken flash due to the fact that the phone turned off in the process.
Here are simple steps:
Take out the battery and leave it out for an hour or so (longer won't hurt)
Get the USB plug and make sure it's in the computer and Odin is started with the correct tar file already selected so that you can flash it quicker
Put the battery back in and start the phone in download mode
Connect the phone and just let it sit for a couple second to make sure it stays on
If it does stay on for more than 15-20 seconds then you can begin the flashing process
If it turns off while in download mode you can take out the battery and put it back in (you don't need to wait)
It's really all just a matter of patience because eventually, the phone should turn on for long enough
Once flashed, the phone should work for a while
So after following that process, I got the phone to work for about 2 months but the issue reoccurred. I was eventually able to flash the stock rom but the problem persisted. So I called in to Samsung to turn it in for the warranty. So far, they have "Replaced a component" in my phone. I SHOULD have it back by Monday. :fingers-crossed:

Thanks, for the response. Battery is out now so I'll try later this evening after it sits for awhile.

I hope it works for you. Just as an update, Samsung has fixed the problem and my phone has shipped as of today! So I guess it's an error on their part.

No luck yet.. Going to leave battery out overnight and try again in morning.

Related

T999 Won't boot/start

Didn't find anything similar on here so I had to post. My T999 no longer boots except for a vibrate when the battery is removed and re-inserted. Occasionally it will get to the CM boot logo and then the screen goes off. If I time the button presses right, I get to the Download screen but before I can hit the Up button to confirm download mode the screen shuts off. This happened all of a sudden yesterday, the last activity being to shut off the Alarm. Tried charging but it will not get past the initial battery icon before the screen goes off. Tried replacing the battery but that didn't help. I also tried to follow the debrick instructions but it didn't help. I was running Vanir AOSP 4.4.4 with no issues until yesterday. The device does not register when connected to the PC using USB and the charger LED does not light up when plugged into charger/PC. My feeling is that something went wrong with the boot but I am unable to get into any usable screen to do anything. I had managed to brick a Samsung Vibrant before but I didn't have to struggle as much to debrick and ODIN back to stock. Any help would be greatly appreciated, I'm now without a phone .
Mine is also acting like that. It wont boot to any rom even stock ones. But i noticed that if i connect my charger it will boot to the homescreen. Sounds like a battery issue right? I also thought that but when i go to recovery, it did not shutdown after leaving it for a couple of minutes. I'm also baffled why it wont boot. I'll try to borrow other battery to test if it still the same.
maelstromm said:
Didn't find anything similar on here so I had to post. My T999 no longer boots except for a vibrate when the battery is removed and re-inserted. Occasionally it will get to the CM boot logo and then the screen goes off. If I time the button presses right, I get to the Download screen but before I can hit the Up button to confirm download mode the screen shuts off. This happened all of a sudden yesterday, the last activity being to shut off the Alarm. Tried charging but it will not get past the initial battery icon before the screen goes off. Tried replacing the battery but that didn't help. I also tried to follow the debrick instructions but it didn't help. I was running Vanir AOSP 4.4.4 with no issues until yesterday. The device does not register when connected to the PC using USB and the charger LED does not light up when plugged into charger/PC. My feeling is that something went wrong with the boot but I am unable to get into any usable screen to do anything. I had managed to brick a Samsung Vibrant before but I didn't have to struggle as much to debrick and ODIN back to stock. Any help would be greatly appreciated, I'm now without a phone .
Click to expand...
Click to collapse
Remove battery snd put back in. Does the device try to turn on by itself? If so you probably have a bad power button.
LarsonJayz said:
Mine is also acting like that. It wont boot to any rom even stock ones. But i noticed that if i connect my charger it will boot to the homescreen. Sounds like a battery issue right? I also thought that but when i go to recovery, it did not shutdown after leaving it for a couple of minutes. I'm also baffled why it wont boot. I'll try to borrow other battery to test if it still the same.
Click to expand...
Click to collapse
Boot download mode and flash stock or root66 firmware with Odin. (You may need to factory reset too)
DocHoliday77 said:
Boot download mode and flash stock or root66 firmware with Odin. (You may need to factory reset too)
Click to expand...
Click to collapse
Done this using root66 but still the same. Now my phone went to worse. It wont get past the S3 logo in the boot screen and just shuts down followed by a vibrate. But if i connect my charger, it will continue and run as normal. My suspect might be a bad battery but the thing is it doesn't auto shutdown when is download mode or in recovery mode. Will try to borrow other battery and update if this fixes the problem.
This is pretty strange. Woke up to my phone with the Galaxy s3 boot logo. And it wouldn't go past it. Tried flashing different backups I had but none of them let me go past the boot logo. Flashed CM10 since my version of TWRP recovery is so old that it can't flash anything higher up, and it goes past the boot logo finally after 2 hours then goes to the cyanogen boot logo but doesn't go past that. I'm going to try with ODIN tonight.
Seems very strange that there are others that had this happen to them to. My phone has never done this before, and it happened randomly.
What does it mean if my phone doesn't boot past the logo with an odin to root66 file?
Edit: Nevermind seems to have worked... for now.
Edit 2: Okay so now it's stuck in an infinite loop where it boots past the logo, shows the android mascot then does an android is upgrading app 1 of 169 then goes back all over again. This is fun! Can anyone help?
Edit 3: Okay so I had to do a factory reset. Got it working now. Starting to get sick of the things I have to do to get updated firmware. Samsung needs to get their crap together!
LarsonJayz said:
Done this using root66 but still the same. Now my phone went to worse. It wont get past the S3 logo in the boot screen and just shuts down followed by a vibrate. But if i connect my charger, it will continue and run as normal. My suspect might be a bad battery but the thing is it doesn't auto shutdown when is download mode or in recovery mode. Will try to borrow other battery and update if this fixes the problem.
Click to expand...
Click to collapse
Hopefully its just the battery.
Download mode may work because of how the battery reports to the os. If its going bad and reporting incorrectly that its low, it may trigger a shutdown. Whereas in download mode the os isn't running so its not reading the battery info the same way. Just a guess.
crazexr7 said:
What does it mean if my phone doesn't boot past the logo with an odin to root66 file?
Edit: Nevermind seems to have worked... for now.
Edit 2: Okay so now it's stuck in an infinite loop where it boots past the logo, shows the android mascot then does an android is upgrading app 1 of 169 then goes back all over again. This is fun! Can anyone help?
Edit 3: Okay so I had to do a factory reset. Got it working now. Starting to get sick of the things I have to do to get updated firmware. Samsung needs to get their crap together!
Click to expand...
Click to collapse
Just for future reference, factory resetting solves about 98% of boot hangs.
Still for both of you, id take this as a sign that you should make sure your backups are up to date. If something is failing you'll be glad you did!
DocHoliday77 said:
Just for future reference, factory resetting solves about 98% of boot hangs.
Still for both of you, id take this as a sign that you should make sure your backups are up to date. If something is failing you'll be glad you did!
Click to expand...
Click to collapse
Yeah factory reset unfortunately didn't work for me when I needed it before I had to ODIN to root66. But I was able to do a nandroid after I couldn't get it to boot and extract my sms from Titanium backup. What an awesome app, super thankful to that dev for making it.
DocHoliday77 said:
Hopefully its just the battery.
Download mode may work because of how the battery reports to the os. If its going bad and reporting incorrectly that its low, it may trigger a shutdown. Whereas in download mode the os isn't running so its not reading the battery info the same way. Just a guess.
Click to expand...
Click to collapse
Turns out it was the battery sir. I've tested it with another battery from 2 different phones and it worked fine. While the phone i tested with the defective battery didn't event get passed the samsung logo. I've suspected it might be having the low voltage causing the phone to shut down.
Anyways, after that i bought a new battery immediately and everything seems ok. thanks for the reply doc.
DocHoliday77 said:
Remove battery snd put back in. Does the device try to turn on by itself? If so you probably have a bad power button.
Click to expand...
Click to collapse
I can confirm that it is likely a bad power button, I have tried everything including dismantling it and seeing if I could dislodge any dirt that may be causing the problem but it didn't work. Looks like I have to find a local repair shop or ebay to get it resolved. Anyone recommend a good place to get this fixed. Funds are limited
Im not sure exactly how difficult the repair is most people seem so do it themselves and have given indications that its pretty easy. You can find the part online for a few bucks.

[Q] Stuck in Boot Loop

Hello
Have a GS3 running Rootbox 4.2. Was running stable for probably around 6 months, no issues at all except for the occasional random reboot which seems to plague all S3s.
Felt it vibrate in my pocket, assumed I had a message. But when I looked it was restarting. It gets to the rom loading screen then abruptly restarts.
Now it even doesn't get that far. The samsung screen shows up and the phone restarts in a loop.
Cannot stay booted into recovery. CWM recovery screen shows for about 2-3 secs then phone restarts.
Download mode through odin works, but I'd like to avoid wiping everything if at all possible.
thank you for any help.
an easy try to fix is to pull battery , wait a couple minutes and then either just hold power button till vibrate or do button combo to get to recovery.
"all i can really do , is stay out of my own way and let the will of heaven be done"
Try re-flashing an updated version of CWM via Odin and see if you can remain in recovery mode.
Thanks for the replies
Tried pulling battery for few mins (actually a few days since I did not have time to mess with phone) - No good, phone gets partway through the rom load screen then reboots.
Tried the odin suggestion - home +vol. down+ power opens download mode, but download mode stays open for around 10-15 sec before the phone restarts itself.
I have tried swapping back to the oem battery since i have an extended battery and the problem still remains.
Sounds like a hardware problem to me since you can access download and recovery but it turns itself off. You've tried a couple of batteries so that kind of rules out any software issues.
Did you try booting the phone with a de-brick image from XDA?

Galaxy tab s 10.5 Stock Firmware Bricked me

Hey guys, I could REALLY use some help with this. So i had my tablet Rooted. Then after a while my google play store wouldn't respond and I couldn't update any apps. So I decided to revert back to stock firmware. This was the file I had used.
(T800XXU1BOJ1_T800XAR1BOJ1_HOME.tar.md5)
I have the Tab S 10.5 bronze.
So I installed it with Odin and I noticed on Odin it said (Succeeded 0/ Failed 0) and the tablet didn't reboot itself. so I thought okay... it must not have worked. Let me reboot the tablet myself. Mind you the screen on the tablet was still in Odin (Download) Mode. After I reboot it, it went into the same bootloop with the TEAMWIN icon popping up over and over again. So I reboot it again to try and put back into download mode. Well it wouldn't. It just popped up with the Samsung Galaxy Tab S Icon and kept repeating that spot. So once again I turned it off to try and get it into Odin mode, and now it wont turn on at all.
Okay. As i was typing this, i have the tablet connected to the computer and it just randomly turned itself on and now its in the TEAMWIN bootloop again. I don't wanna touch it until I get someones opinion on what to do next...
AWESOME it bootlooped itself again but this time when the samsung logo popped up I held the volume button and got it into Odin Mode! now.... what to do next? I dont want to try the same Stock FIrmware. Idk if it was the problem or not.
alright so here is what I just did..
The tablet rebooted itself while I was typing that message while it was plugged into the PC. It turned itself on but when it was at the Samsung Logo I quickly pressed the Volume button and had gotten it into Odin Mode. I disconnected it from the PC, loaded up the Stock firmware from the first post. Plugged in the Tablet while it was in the Downloading Odin Mode. Hit start on Odin and it did the rest. Now the issue is it reboot, samsung logos popped up and went away. the Samsung logo with the little blips of light/stars around it came up. then it said Installing Applications with a loading bar. That lasted about 2 seconds then went back to the samsung logo with the stars. Then the tablet shut off and now i cant get it back on again.....
Hold POWER + VOL DOWN
Yeah. I know that. That's how I got it into Odin mode.. Thanks for four word incredibly helpful post...
Are you sure you downloaded the correct software for your device? You could try another region's firnware or re-download the one you used.
Since you still see the Teamwin icon I guess it didn't install the firmware correctly or all of it since your recovery should be the stock one again after flashing. Or did you remove items from the .tar file you try to flash?
M1LLER_LITE said:
Yeah. I know that. That's how I got it into Odin mode.. Thanks for four word incredibly helpful post...
Click to expand...
Click to collapse
I'm telling you how to reset your device not boot into download mode smart mouth!

Another M9 bootloop

Hi everyone, had the phone for few years, one day it died and never booted again. Nothing was flashed at the time, my son was using it and I read that some phones, if they got hot enough playing games, the nand will get erased and the phone is borked.
All I get is the white HTC screen.
If I hold the volume + and - I will get to the screen attached.
If I select download mode, the phone will reboot and a black HTC screen will appear, but then the phone will reboot after 1-2 seconds, back to the white HTC screen.
Same with bootloader mode.
I have downloaded 0PJAIMG_HIMA_UL_N70_SENSE80_ATT_MR_NA_Gen_Unlock_4.30.617.2.zip and copied it to a 32GB sd card, and tries to get it to flash via download mode using the process above, but nothing happens and the phone reboots within 1-2 seconds.
Is there any way I can revive this phone? or just throw it in the trash?
Thanks!
shpitz461 said:
Hi everyone, had the phone for few years, one day it died and never booted again. Nothing was flashed at the time, my son was using it and I read that some phones, if they got hot enough playing games, the nand will get erased and the phone is borked.
All I get is the white HTC screen.
If I hold the volume + and - I will get to the screen attached.
If I select download mode, the phone will reboot and a black HTC screen will appear, but then the phone will reboot after 1-2 seconds, back to the white HTC screen.
Same with bootloader mode.
I have downloaded 0PJAIMG_HIMA_UL_N70_SENSE80_ATT_MR_NA_Gen_Unlock_4.30.617.2.zip and copied it to a 32GB sd card, and tries to get it to flash via download mode using the process above, but nothing happens and the phone reboots within 1-2 seconds.
Is there any way I can revive this phone? or just throw it in the trash?
Thanks!
Click to expand...
Click to collapse
Don't trash it yet!
Do you have a custom recovery?
If not you can "RAM" boot TWRP. While in the bootloader screen do this:
Code:
./fastboot.exe boot twrp-3.0.2-0-hima.img
Then with MTP enabled you should at least be able to look at your files (assuming not HOT deleted like you mentioned).
There's something called "RUU" we can try next, it's a (HTC) way to bring your phone back to stock. But try to save your files first!
Thanks, I will give it a try.
I don't care about any data on the phone, just trying to make it function again.
I let the battery drain over-night, I'll see if I can do anything with it.
Thanks for your input!
Note it doesn't look like the RUU files are hosted on HTC anymore.
Here's the full filenames I have downloaded and used in the past.
- RUU_HIMA_UL_M60_SENSE70_TMUS_MR_TMOUS_3.39.531.7.exe
- RUU_HIMA_UL_N70_SENSE80_TMUS_MR_TMOUS_4.27.531.6
A quick google should let you find them but a little frustrating to not get it direct from HTC (security risk anyone?).
I was messing with it last night, after I let it completely drain it won't charge anymore. If i connect it to a charger, or to a pc, it will turn on for 1-2 seconds, then turn back off, and do the same again and again.
Thanks for your help but looks like I can't do anything to it at this point. Not sure if the battery can be charges externally.

S20+ VZW stuck in download and Odin fails

So the other day I woke up and my S20+ wouldn't power on. I tried every key combo, I even pulled the back glass to make sure the battery didn't somehow get bumped loose. It had sat on the charger all night before it did this. I left it on the charger the whole next day while I got my old Note 10 updated to use until its fixed. Every few hours I would go over and try to start it, and finally when it did, it sent me to the blue screen saying it was flashed with unauthorized firmware and that it was locked. The phone has never been flashed with anything other than OTA updates. I managed to get it into download mode but every flash I've tried from Odin fails. Im at a loss here. I cant get into recovery mode and when I power it down to get out of download mode, it just keeps flashing the Galaxy S20+ screen over and over again, so i have to put it in download mode and let it sit until it shuts off on its own. Does anyone have any input on this?

Categories

Resources