My Samsung Galaxy S3 i9300 was running fine with CM11 (i think I had clockwork recovery).
After a sudden reboot, it kept in the boot loop only showing the Samsung logo. I did not do any updates, since the last snapshot in January, nor any app installaions - I was just using the device as usual.
Now I can not access the recovery, as it keep rebooting all the time. The only thing I get for one or two seconds is the download mode, but it reboots immediately.
I tried fastboot and adb to connect, but the tools don't find anything.
Is there any chance to recover the device or is it bricked?
Do you have any hints what I could do?
Related
Hello
I have been using my int Gs3 for sometime and decided to root and explore the mods and custom fw world. I have started with getting to root access and after that install CWM.
Then I try to install nightly cyanogenmod 10. It didnt work and boot back to normal GS3 Touchwiz interface. After that I tried the GooManager and when the phone is restarted it went to bootloop. I removed the battery and put it back. The problem started there.
The phone does not boot to any OS, I only can see the galaxy s3 9300 black splash screen and awatis there. I can go into download mode, but when I go into recovery mode, I can see the Android robot, and it dies The screen is too fast but what I can see it cannot mount EFS, System and any folder.
So I have tried several different methods
- Tried to flash with original rom, different roms, CWM and what I can find suitable for international model. But everytime I got stucked in Nand Write part. In some of them, the flash started and stucked in installing some parts(passes the cache and hidden and stuck after that)
- Tried with bricked phone roms, different PIT files and Bootloader Vralec methods.
- When I am trying these, I have tried with 3 different PC's with/without KIES and Samsung drivers installed. When I plug the phone in Download mode, the PC recognizes it as Generic device.
- I manage to flash the CWM but when it restarts it does not go any further than the first splash screen, but in Odin, some time later it turns to pass. Funny, when the phone is on Galasy S3 black splash screen, the pc recognizes the phone and starts to install the driver.
So, here is an interesting flashing story of mine. I really would appreciate your valuable comments and suggestions.
Thanks in advance.
cugami said:
Hello
I have been using my int Gs3 for sometime and decided to root and explore the mods and custom fw world. I have started with getting to root access and after that install CWM.
Then I try to install nightly cyanogenmod 10. It didnt work and boot back to normal GS3 Touchwiz interface. After that I tried the GooManager and when the phone is restarted it went to bootloop. I removed the battery and put it back. The problem started there.
The phone does not boot to any OS, I only can see the galaxy s3 9300 black splash screen and awatis there. I can go into download mode, but when I go into recovery mode, I can see the Android robot, and it dies The screen is too fast but what I can see it cannot mount EFS, System and any folder.
So I have tried several different methods
- Tried to flash with original rom, different roms, CWM and what I can find suitable for international model. But everytime I got stucked in Nand Write part. In some of them, the flash started and stucked in installing some parts(passes the cache and hidden and stuck after that)
- Tried with bricked phone roms, different PIT files and Bootloader Vralec methods.
- When I am trying these, I have tried with 3 different PC's with/without KIES and Samsung drivers installed. When I plug the phone in Download mode, the PC recognizes it as Generic device.
- I manage to flash the CWM but when it restarts it does not go any further than the first splash screen, but in Odin, some time later it turns to pass. Funny, when the phone is on Galasy S3 black splash screen, the pc recognizes the phone and starts to install the driver.
So, here is an interesting flashing story of mine. I really would appreciate your valuable comments and suggestions.
Thanks in advance.
Click to expand...
Click to collapse
GO here : http://forum.xda-developers.com/showthread.php?t=1993044
I'm just about at my wits end!
I have the T959. I was running Cyanogenmod 10 with no problems for a long time. Then overnight an application crashed and when I closed it in the morning my phone shutdown. After that it wouldn't boot (stuck at Vibrant logo) and won't enter recovery mode.
Following the Cyanogenmod Wiki I attempted to flash Clockworkmod to get back into recovery. It appeared to work but I still couldn't access recovery.
Failing all other solutions with the Cyanogenmod community I attempted to reset it to Stock setting using Odin. That appeared to work as well (I actually did it several times) but now it shows the vibrant logo and then goes black. Before it at least stayed at the Vibrant logo.
I've tried the "one click unbrick" application as well.
I can't find any other options. Is there any way to get my phone functional again, even at stock settings?
My phone is a verzon note 2 on deodox 4.3 with twrp recovery. The phone only boots to teamwin logo and flickers on and off. my computer will not recognize my phone either at this point.This is what happened. Ive been having some 4g lte loss and unstable wifi issues to i decided to do a factoty reset. when i rebooted into recovery i was stuck at the twrp logo and it would constantly bootloop the twrp logo.. I restarted my phone and did a factory reset from under the general setting. At that point it rebooted int the twrp but continued to just stay at the logo and would not go into recovery. I pulled the battery and restarted the phone but from that point on it would only boot into the twrp logo and stay there. I can get into download mode but my pc (win7) no longer recognizes the phone so i cant attempt to fix this in odin. Im not sure what to do to get this phone to work properly at this point.
yoda254 said:
My phone is a verzon note 2 on deodox 4.3 with twrp recovery. The phone only boots to teamwin logo and flickers on and off. my computer will not recognize my phone either at this point.This is what happened. Ive been having some 4g lte loss and unstable wifi issues to i decided to do a factoty reset. when i rebooted into recovery i was stuck at the twrp logo and it would constantly bootloop the twrp logo.. I restarted my phone and did a factory reset from under the general setting. At that point it rebooted int the twrp but continued to just stay at the logo and would not go into recovery. I pulled the battery and restarted the phone but from that point on it would only boot into the twrp logo and stay there. I can get into download mode but my pc (win7) no longer recognizes the phone so i cant attempt to fix this in odin. Im not sure what to do to get this phone to work properly at this point.
Click to expand...
Click to collapse
My guess is that when you rooted with CASUAL, it changed the Samsung device driver on your computer and you need to reinstall the Samsung driver to get the computer to recognize the phone again in download mode.
Underneath step 7 of section 1b on Droidstyle's restore guide, he discusses issue with CASUAL replacing the Samsung driver... and he gives a link to Jeremy Loper's fix... "If odin no longer recognizes your device, most likely Casual killed the driver for odin!! follow this tutorial for restoring the driver: http://www.youtube.com/watch?v=zzghcV8HVVk"
Once the computer recognizes the phone again, you should be able to use ODIN to restore back to 4.1.2 so you can root/unlock again with CASUAL. After you get the phone restored with Odin, I would recommend booting into Stock Recovery and wiping cache/doing factory reset before running Casual again... this would enure you are starting over with a totally clean slate.
If the above doesn't work, then here's a thread where I tried to help someone else who couldn't get their computer to recognize the phone.... maybe some of those ideas will help - http://forum.xda-developers.com/showthread.php?p=55833998
Good luck!!
1 step forward two steps back. I got my pc /odin to recognizes my note 2(changed usb cords). Then tried to odin back to stock 4.1.2. At first odin kept saying (odin not responding) and would ask to close the program,after several attemps i final got it to flash the 4.1.2 file. When i flashed the file and was at the point where it reboots, it would not get past the samsung note 2 logo and continued to flicker and not boot up even when i tried to put it into download mode like it said to in this thread. http://forum.xda-developers.com/showthread.php?t=2024207. When i tried to reflash the file it failed. when i attempted again it just hangs at setupconnection. Tried again and it failed. Btw thanks for the help mattnmag.
Got it working! i simply forgot to place the sch-i605 pit. into the pit section of odin when i flashed the 4.1.2 rom.
Similar problems
I was running AllianceROM 26. My phone had been spontaneously rebooting for a bit recently. Today, it started to spontaneously reboot again, but this time, it never got past the Galaxy Note 2 screen. After pulling the battery, I tried to boot into TWRP. It just hangs on the twrp boot screen for a few minutes but never goes into twrp.
I figured I would try taking it back to stock. So, I used ODIN to try and put 4.1.2 on it and a new PIT file. That appeared to work fine. I got no errors in ODIN. However, I still cannot get this thing to get past these boot screens, either the Galaxy Note 2 one or TWRP when I try that there. I have tried this twice now, once with re-partition checked and another time with re-partition unchecked (saw conflicting instructions on that so I figured I would try it both ways). I still am not getting past the boot screen.
Any help or ideas are appreciated as right now, my phone appears to be bricked and I am out of ideas.
so what was the solution to the teamwin flashing on and off after a factory reset? this is certainly not a solution, having to reflash the phone...
Hi, today I tried to downgrade my Galaxy S3 from Cyanogen 12 to stock firmware (So from Lollipop to Jellybean) but now it's stuck on the bootsceen and I can't access the recovery mode, I can just access download mode.
Hi Hencick - Welcome to XDA.
I'll just naturally assume that you're familiar with flashing roms...
Were you running a custom kernel with CM?
Can you access adb functions with a pc?
I have a similar problem on my phone I discovered today. I just get the Samsung logo on screen, it goes off, then comes back (bootloader loop i guess).
It was just sitting on charge. It hasn't done anything for a while other than updates, now when I come to it, it's like this.
I can't get into recovery mode, adb mode, download mode or anything. Just the Samsung logo flashing up, then going and coming back up.
Is this recoverable?
As it it keeps powering up, then off, then back up I'm not even sure I can use Odin on it.
TIA.
Edit: Ok, I can get it into download mode it seems. Only, now I'm not sure what to do! lol
I know this is a known issue, but the thing is that most solutions i have found regard looking into the phone's settings.
The thing is I can't even boot my phone any more. The moment I get the Galaxy SIII GTI9300 logo the phone simply freezes there forever.
It's been like hours like this. I even tried removing the battery for half an hour and put it back. It just won't boot any more.
I didn't install a custom ROm after rooting, the phone was freshly rooted and didn't got to that step yet.
I rooted the device by using the toolkit http://forum.xda-developers.com/gal...msung-galaxy-s3-unified-toolkit-v8-0-t1703488
which surprisingly worked pretty fast and I was able to confirm that my phoen was rooted by installing a root-only app (Root Uninstaller)
then i got a message asking me to update the SU binary and when i accepted the update the phoen restarted never to boot again.
I didn't even get the chance to get the ClockworkMod yet.
Now I don't even have ClockworkMod's menu at the beginning, i have nothing. only the classic boot mode that allows me to download software via Odin (which always fails no matter what package I try)
please help me, i have no other device than that right now....
Download-Mode
Hello and good morning,
have you tried to boot into download mode ?
It's the same like s3
Take the battery out for a few seconds . put it back in and boot into download mode again and it should work