I have a Galaxy SIII, was using it today, and suddenly it turned off. I thought it ran out of battery, but when I plugged it in and tried turning it on, it went through the start-up process, and just looped with the Samsung logo flashing with the blue in the background. I can get into recovery and download modes, and I tried both using Odin and doing a stock reset in the stock recovery mode. This phone has never been rooted, and the only custom thing that I used is an SD Card and a Mybat 2100 mAh Battery. I had another Galaxy S3 a few months ago that got hard bricked due to custom software, but thanks to AT&T's 9 month warranty, I was able to get that replaced. I really don't want to go through that whole process again, so any help will be awesome.
Related
I'm running stock ICS, no roms, no root, just the regular version of Android that game on my Verizon Wireless Galaxy Nexus. Last night the battery drained and I recharged it while I slept using the charger that came with the phone. When I woke up I turned my phone on. The Google logo came up, it vibrated, and then the colors boot animation started. After a few seconds, the animation froze and then the Google logo came back up, it vibrated, and the colors boot animation started again, then froze. It keeps doing this over and over.
I can enter recovery mode and download mode. I made a video of my problem and posted it on YouTube:
Bah! new users can't post outside links >:-(
watch?v=OrrGNMtU8Lc
Is there anyway I can get my phone bootable without wiping the memory? Is there anyway I can access the contents of the phone on my computer while it is in this non-bootable state?
If not, then what is the best way for me to get my phone back to a bootable state? I have never messed around with rooting or roms for Android so I would need to know the best place to start. I have messed with custom roms for my old Treo and some game consoles, so I have some experience following tutorials.
Hi guys, i have a problem with my gnex D:. what has happened is i have downloaded the gnex root toolkit and tried to unlock my phone, then my gnex turned off while the program said it was restarting the phone into bootloader and then poof my phone has a black screen and nothing happens. then after this my phone is now in a state where if i turn it on it will vibrate and show the google logo like normal but after that it has a black screen and well.... nothing and the only way to turn the phone back on is to pull out the battery make sure the charger isn't plugged in and then put the battery back in the phone and either boot up the phone so it'll do the soft brick thing with the google screen or boot into bootloader where to my knowledge nothing can be done to fix the problem. someone please help cause i just got it back from waiting 3 weeks for repairs then coming home and capoot it's dead :'(
EDIT: Sorry forgot to mention it is a samsung galaxy nexus running jellybean 4.3 JWR66Y GSM
EDIT 2: problem resolved, turns out it was just a simple corrupted boot.img file
I recently flashed a Pacman 4.3 ROM and today decided to restore my phone back to my stock/rooted Nandroid file that I made beforehand. Used CWM and, after it said the restore was completed, I went to reboot and have been unable to get past the "Samsung Galaxy Note II" bootscreen. It'll go to that screen for a bit and then the entire screen will go black, requiring me to take out and reinsert the battery to do anything else. I can get it into recovery mode and download mode and have tried using factory resets, cache clears, and Odin to try and reset everything back to the original stock firmware, but so far nothing has worked. Every time, I wind up looking at the "Samsung Galaxy Note II" screen for a bit and then the entire screen shuts off.
Can this phone be saved or am I SOL?
Edit: If I take the battery out and put it back in and don't try to turn on the phone, I can plug my phone into my charger and I get a visual on the screen saying the battery is charging and the LED lights up red. For what it's worth.
cptcliche said:
I recently flashed a Pacman 4.3 ROM and today decided to restore my phone back to my stock/rooted Nandroid file that I made beforehand. Used CWM and, after it said the restore was completed, I went to reboot and have been unable to get past the "Samsung Galaxy Note II" bootscreen. It'll go to that screen for a bit and then the entire screen will go black, requiring me to take out and reinsert the battery to do anything else. I can get it into recovery mode and download mode and have tried using factory resets, cache clears, and Odin to try and reset everything back to the original stock firmware, but so far nothing has worked. Every time, I wind up looking at the "Samsung Galaxy Note II" screen for a bit and then the entire screen shuts off.
Can this phone be saved or am I SOL?
Edit: If I take the battery out and put it back in and don't try to turn on the phone, I can plug my phone into my charger and I get a visual on the screen saying the battery is charging and the LED lights up red. For what it's worth.
Click to expand...
Click to collapse
This is gonna sound like a long shot, but are you sure your battery has juice? I had something very similar to what happened to you on a tablet I owned. I thought the device was messed up, but it was just really low on battery somehow. Left it sitting on the charger for a few hours and it came back.
cptcliche said:
I recently flashed a Pacman 4.3 ROM and today decided to restore my phone back to my stock/rooted Nandroid file that I made beforehand. Used CWM and, after it said the restore was completed, I went to reboot and have been unable to get past the "Samsung Galaxy Note II" bootscreen. It'll go to that screen for a bit and then the entire screen will go black, requiring me to take out and reinsert the battery to do anything else. I can get it into recovery mode and download mode and have tried using factory resets, cache clears, and Odin to try and reset everything back to the original stock firmware, but so far nothing has worked. Every time, I wind up looking at the "Samsung Galaxy Note II" screen for a bit and then the entire screen shuts off.
Can this phone be saved or am I SOL?
Edit: If I take the battery out and put it back in and don't try to turn on the phone, I can plug my phone into my charger and I get a visual on the screen saying the battery is charging and the LED lights up red. For what it's worth.
Click to expand...
Click to collapse
Charge up phone....
Try this.
http://forum.xda-developers.com/showthread.php?t=2618447
Thanks for the help guys, I managed to fix it. What I did was download the stock ROM file from here: (can't post the URL for some reason) and then opened Odin, put it in the PDA slot, put my phone into Download Mode, connected it to my computer, and ran it. Phone rebooted back to a factory reset version.
The link I used is from a site called "Stockroms" and, after typing stockroms, add the following to the URL: .net/file/GalaxyNote2/SGH-I317/I317UCAMA4_I317ATTAMA4_ATT.zip
cptcliche said:
Thanks for the help guys, I managed to fix it. What I did was download the stock ROM file from here: (can't post the URL for some reason) and then opened Odin, put it in the PDA slot, put my phone into Download Mode, connected it to my computer, and ran it. Phone rebooted back to a factory reset version.
The link I used is from a site called "Stockroms" and, after typing stockroms, add the following to the URL: .net/file/GalaxyNote2/SGH-I317/I317UCAMA4_I317ATTAMA4_ATT.zip
Click to expand...
Click to collapse
Excellent. Congrats
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
My Galaxy S3 keeps shutting off during boot. I encountered this problem while running Cmod 11. Was using poweramp playing music off my 64gb exFat microsd card, and suddenly Poweramp encounters "Error too many files" and promptly shuts the phone down. (Poweramp has been giving me strange problems before this, like that error just mentioned, and scanning for changes when there are none, but this is the first time the error caused the phone to shut down).
After rebooting it, The S3 gets to the boot screen and upon opening an app, promptly shuts down again. Further attempts result in the phone shutting off during the boot animation, and finally now the phone simply shuts down right before the boot animation. (note: it doesn't reboot. It turns itself off).
I thought it might be a problem with Cmod, so I wiped everything and using CWM, installed slimkat. Same problem. so I went and installed stock android using Odin, and now I'm back to stock. STILL same problem.
When I have the phone plugged into a computer, it seems to get further than the boot animation before shutting down (sometimes it gets to the lockscreen before shutting down again).
Any idea what's causing this problem? I have no problems with erratic shutdowns during recovery and download mode.
How old is your battery? Might be time to replace it.
This is the same battery the phone came with since a couple years ago. Assuming it is a problem with the battery, why does recovery and download mode still work fine?
cheezyphil said:
This is the same battery the phone came with since a couple years ago. Assuming it is a problem with the battery, why does recovery and download mode still work fine?
Click to expand...
Click to collapse
They're not as heavy to load.
Was any modification done to your phone (software) about when that started happening?
The s3's been on and off custom roms for a year now
cheezyphil said:
The s3's been on and off custom roms for a year now
Click to expand...
Click to collapse
I mean before it started happening. Or were you on the same ROM/version of that ROM for a while when it happened.
Been on cmod for a year before it happened. Reverted to stock rom about a month ago to unlock it, and then straight back to cmod. A couple days after coming back to cmod, this happens.
cheezyphil said:
Been on cmod for a year before it happened. Reverted to stock rom about a month ago to unlock it, and then straight back to cmod. A couple days after coming back to cmod, this happens.
Click to expand...
Click to collapse
Well if you can get in recovery, I would suggest doing a clean flash. But chances are that it's your battery giving out.
If you want to test, borrow a battery from another S3. I know with T-Mobile you can go to a store and they usually have a device on hand that you can borrow one from to test it out before spending money on it. I imagine you can do this at AT&T stores as well.
had the same problem with my atnt galaxy s3
i have the same problem,,i am using cm12 ryt now,,i tried to put every single rom and same thing happens,,i also brought it back to its stock firmware,,and still the problem occurs... did u find any solution for it,already?
:crying:
Hello All,
I recently found a Sprint Samsung Galaxy S3 (SPH-710T) that cannot boot to its custom ROM, CyanogenMod. The only thing I vaguely remember is a few years back when a coworker of mine had pulled out the battery when the phone was either rebooting or installing an update. The phone still boots to download mode, but when I do the combonation for recovery mode (Volume Up, Power, and Home), it shows the startup logo and blue text at the upper right corner, but then immediately shuts off. I have tries using download mode to install TWRP, but every time I do it, the program on my computer says that the process was successful, but the phone shows no sign of the program being installed. I have also been successful when downloading CF-Root to the phone, but the attempts at installing TWRP after that yeild the same result. I saw a video detailing a de-bricking SD card, but got scared after I learned that the card were not interchangeable between models. I am here for any questions you might ask and I will happily try any of the solutions provided by people.
Thanks so much for all of your help,
Max