GT-I9300 (international version) (FCC A3LGTI9300A)
Never rooted, just applied official OTA patches when delivered.
Been experiencing random reboots now and then (more rarely than once a week) Some of them seems to have been "softer" than others because I did not need to enter PIN when it started up again.
Then a couple of hours ago, when waking it up (screen turned on but froze before displaying unlock function) it rebooted again and got stuck in boot loop.
When I power it on the first screen (Samsung Galaxy SIII GT-I9300) shows and then it goes to the "fun part"
The blue/purple "Circle"
SAMSUNG logo
blueish glow behind SAMSUNG logo (two short vibrations near the end)
black screen
repeat ad infinitum
Managed to get into recovery to clear cache but that did not help.
I guess factory reset is the next step to try but if there is any chance of anything else working I would prefer not to have to reset.
try reflashing the ROM you had through Odin. And don't ask how, there are tons of guides
Thanks for your quick reply!
Would it have to be the exact same version, or is any 4.1.2 for my model "close enough" to hopefully avoid factory reset?
Every ROM should do the job. But when it works you should save the data you want to keep and do a reset afterwards and flash the ROM again. Just to make sure no issues come up. What you could also try is to hold down the Volume Down button while rebooting and look if you can boot into safe mode. There you could save every neccessary data and do a reset/wipe afterwards.
Try to flash modem depending on your region, it worked for me
Sent from my GT-I9300 using xda app-developers app
Thanks for your tips, unfortunately no luck so far, one more rom file to try before resorting to factory reset...
Update, unfortunately still no luck. For a little while (after going from 4.1.1 to 4.1.2) I was feeling optimistic as the "updating apps" screen appeared when booting, but when it was finished it went back to bootlooping. I am now considering rooting/custom recovery to try to mount partitions so I at least can recover data from internal sdcard-partition.
Didn't want to risk triggering flashcounter if I still would not be able to boot and run TA.
Ended up doing factory reset from stock recovery and phone booted up just fine, guess there was something bad in my data or apps.
Hi everyone,
I have a Galaxy S II from Bell Canada and it was recently updated via Kies to Android 4.1.2 a couple weeks ago. I've been having all sorts of problems with it since the update, including random freezing, crashing, and so on, so I intended to backup and factory reset this weekend. Before I could do that however, it shutdown and now I can't boot it back up.
Symptoms:
- The phone gets past the Samsung Galaxy S II animation, but then goes immediately to the glowing SAMSUNG logo and stays that way for several minutes before shutting down.
- Battery power is not an issue. Half-full to full battery makes no difference.
- Connecting it to my PC allows Windows 7 to install most of the needed drivers, except it fails on 'MTP USB device failed'. This might simply be because the phone doesn't fully boot.
What I've tried:
- Multiple reboots (shutdown and restart)
- Removing the SD card and multiple reboots
- Wiping the cache partition several times and booting via the stock recovery menu (reached by Volume + Home + Power)
I have backups but from several months ago, so anything I can do to flash the firmware and retain my data would be appreciated. I've looked at other threads but many users seem to have slightly different issues or are with other carriers. I haven't played around with flashing or anything since getting the phone two years ago, so I don't know how much of a difference their steps would be from mine.
The phone is either just inside the warranty period or just outside... I don't have the exact date if that makes a difference here.
Any help tracking down the issue or helping to get it back to functional would be appreciated.
Firstly, from your post it looks your phone is not rooted. If that is the case then i am afraid we are left with not much options to try.
I would advise, if u want to come out of this issue and data is not the concdrn then do a hard reset by getting into the recovery console.
And, if you are rooted than simply reinstall the rom without resetting anything. This will bring back the rom and you will also not loose any data.
Sent from my GT-I9100 using xda premium
vishal11in said:
Firstly, from your post it looks your phone is not rooted. If that is the case then i am afraid we are left with not much options to try.
I would advise, if u want to come out of this issue and data is not the concdrn then do a hard reset by getting into the recovery console.
And, if you are rooted than simply reinstall the rom without resetting anything. This will bring back the rom and you will also not loose any data.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
That's correct, the phone isn't rooted. I'd like to exhaust all other options before attempting something that will wipe the data... is it possible to determine the exact problem some other way?
Nope. If it were me I'd be doing a wipe (and this wouldn't faze me because I back my stuff up regularly).
toast_tcg said:
That's correct, the phone isn't rooted. I'd like to exhaust all other options before attempting something that will wipe the data... is it possible to determine the exact problem some other way?
Click to expand...
Click to collapse
Looks difficult to save the data. But you may try, i am not sure it will work.
find out a compatible rooted kernel. Get into the download mode and with the help of odin flash this kernel. (ensure its *.tar file ).
Once done try to boot the phone. if no luck, clear the cache and then again try. Still no luck, then i am afraid you have to hard reset.
Best of luck.
Well, my problems with recoveries are sorta of a jokle by now, but I still feel compeled to share my experiences so maybe anyone can tell me what the hell is happening on my phone....
So as I said some time ago, I experienced problems with the PhilZ recovery, which I solved swapping to CWM version 6.0.3.2. The problem was the infinite bootloop of the Samsung Galaxy GT-I9300 logo, the black screen, which did not allow me to access to the recovery. But inmediatly after flashing to the old CWM the problem was gone away. Also, in a case of a possible kernel panic due to doing some stuff with Xposed modules CWM was the only recovery I could get access into.
Now, the problem is the following. Yesterday I installed the CWM Touch version 6.0.4.7, which I got from this thread http://forum.xda-developers.com/showthread.php?t=2052091. After installing it everything was normal. However, after one hour or so the phone screen wouldnt turn off when I pressed the Power Button. In fact the Power Menu appeared, but the screen, as I said, dindt get to sleep mode. To top that, after freezing for a second the phone suddenly turned off, and then get to the infamous black screen with the model logo looping and looping.
Fortunately, after pressing Volume Up+Menu+Power I could get to the Recovery, but not after quite some seconds pressing these three buttons. And in some times it would not get me to the recovery, but instead completely rebooting the phone and working again. Just to, in half an hour, freezing and looping again and again and again.
This problem happened to me with virtually every ROM I installed, being Neat ROM, Archi, and even CM11 from Temasek. Nothing would solve that problem. The only remedy I had was a temporary one, which consisted on uninstalling and reinstalling again the kernel (I used boeffla) and the problem would not disappear that way. Also, when wiping data, for some weird reason it gave an error message while wiping the /preload partition, in the Mounts and Storage menu.
Until I got home today, and then flashed through Odin the old CWM Touch version 6.0.3.2, that finally stopped the problems. I tested it by pressing the Power buton again and again and it hadnt redirected me to the black bootloop screen. Seriously, I am wakelocking my phone on an intensive basis and nothing has happened for now, and I think it probably wont happen again. Maybe it takes three seconds, maybe the Power Menu displays again, but no bootloop again.
So I ask to you, what is happening on my phone that it wont run recoveries younger than my old 6.0.3.2
IMPORTANT EDIT: THE PROBLEMS ARE NOT SOLVED YET
Some hours ago, I was chatting using Whatsapp while charging the phone on an USB charger, when it suddenly suffered the black screen bootloop again. This time was unexpected, since I was using the CWM Touch 6.0.3.2, the one supposed to work fine. So for now I feel completely finished. My phone is officialy into a unsolvable problem.
But, thinking about it, there were some things that might help you:
-This time I did not uninstall and reflash the kernel: When I got to the recovery menu, I just selected "reboot", as such, without flashing anything else, and the phone then worked as fine, booting into the ROM bootanimation screen (this time the Neat ROM bootanimation). So basically a manual reboot through Recovery got me out of this. Also, I kept using the phone until now and there werent more problems, at least for now.
-As far as I can recall, these problems started some weeks ago, when I accidentally formated the internal SDcard. I was using PhilZ Touch Recovery and flashing a ROM as usual, when I selected without knowledge the option "Format /data and /data/media (sdcard)" in the Mounts and Storage menu. I did this after doing the usual Full Wipe before flashing an new ROM, and after that I had to turn off the phone in order to insert a ROM in the external SD card to flash it through the recovery to make the phone working again. But when I wanted to get back to the recovery, I couldnt. I had to flash CWM 6.0.3.2 because it was the only recovery that let me access to the recovery menu-the already installed PhilZ wont allow me to access to the recovery menu. So in CWM I got to the External SD card and flashed a Neat ROM, and got the phone working again. And after that I reflashed PhilZ. But since then the phone started to experiment these freezes, reboots and bootloops. One happened to me when in College, and couldnt get out of it because PhilZ wont respond to the Manual Recovery command. I had to wait to get home, to reflash the CWM 6.0.3.2 recovery through Odin because that Recovery was the only responding. And in that moment it did well, and didnt have more reboot problems. Until I flashed 6.0.4.7, which is why I am here.
-Lastly, about the reason I trust in CWM 6.0.3.2: Some time ago, when flashing Blackbox ROM 2.0.2, I downloaded the Gravity Box module from Xposed, and installed it alongside with other modules, which, supposedly, caused a kernel panic problem that sent my phone into the dreaded black bootloop again. I was using PhilZ recovery, and as you may expect now, I couldnt get access to it, so I flashed the CWM 6.0.3.2 recovery, which let me access to a recovery. I too flashed TWRP, but it accessed for one second to the recovery menu, and then faded away, returning to the bootloop logo screen. So basically PhilZ and TWRP failed me during that kernel panic problem, while CWM stood the problem. And thats why I turn to this recovery when everything else fails.
And thats why I am troubled now, because this recovery is showing signs of failure
Try cwm 6.0.4.4 as I've used this for all sorts of Roms and have no problems
andrewwright said:
Try cwm 6.0.4.4 as I've used this for all sorts of Roms and have no problems
Click to expand...
Click to collapse
I used 6.0.4.7 and I had the problems previously described....I mean, I used a more updated version than the one you propose. Do you believe its gonna work better?
And thats why I will stick to 6.0.3.2 until someone tells me whats happening. If an updated version of 6.0.4.4 gives me problems...well, go imagine.
I can confirm that 6.0.4.4 works. I Also tested it for nandroid bk up and restore and it works. I have flashed the latest tw 4.3 and the old 4.1.2 and aokp/cm/aosp 4.4.2 and all flashes with no errors. I have 6.0.4.7 but not tested it this is why I said to you to use 6.0.4.4
Only thing I haven't tested is adb.
andrewwright said:
I can confirm that 6.0.4.4 works. I Also tested it for nandroid bk up and restore and it works. I have flashed the latest tw 4.3 and the old 4.1.2 and aokp/cm/aosp 4.4.2 and all flashes with no errors. I have 6.0.4.7 but not tested it this is why I said to you to use 6.0.4.4
Only thing I haven't tested is adb.
Click to expand...
Click to collapse
Interesting. And where do I get the 6.0.4.4? I dont see it neither in the new CWM thread nor in the old one.
Look down
here. zip so just flash in recovery
andrewwright said:
here. zip so just flash in recovery
Click to expand...
Click to collapse
I apreciate your help, but now some new problems have emerged, and I need more help, because maybe I might have a corrupted partition or such, who knows.
With this quote, I too try to bump the thread, in order to gain more attention to my new problems
If anyone is interested, please look the OP, as it has been edited to describe the new problems.
Best thing to do now is go bk to stock firmware with Odin and see if any problems persist. Totally stock for a few days.
andrewwright said:
Best thing to do now is go bk to stock firmware with Odin and see if any problems persist. Totally stock for a few days.
Click to expand...
Click to collapse
I will try that in a few weeks, I am a bit busy by now to test anything...
Fortunately, the CWM 6.0.3.2, while not infallible, works better than the other recoveries...today I only had one bootloop problem, solved by simply rebooting from the recovery....I can keep it for one week or two, it doesnt worry me for now.
Also, there is a guide to reflash stock? Sometimes I reflashed stock, but it kept bootlooping on the Samsung animation...probably because I didnt know how to wipe data while reflashing stock. Thats a little problem I have with reflashing stock, any help is appreciated.
Odin wipes the phone while flashing. What rom are you on? Custom
Well, I have to bump this post again because I am having the same problems again.
I am using CWM 6.0.3.2 as my current recovery. Today, I was browsing the Facebook app when I pressed the Power Button. Then, a lag of 2 seconds happened, the Power Menu displayed on screen, and the phone got into the black boot screen again. But this time I could not get to the recovery. Whenever I pressed Volume up+Power+Menu there appeared a black screen featuring the CWM logo and then it returned again to the black boot screen again. So what I did was to remove the battery, then eject the Exterior SD Card (A Lexar, 32 gb) and put again the battery in its place. The phone started all normal again, and when I put again the SD Card it continued to work normally.
So, what do you think its happening? Not even my old recovery, the one which works better for me, is reliable anymore. Could this be a component of my phone failing? Particulary the emmc chip? Or its not a hardware problem? Should I sent the phone to reparation?
How much data do you have on ext sd? Maybe phone is scanning ext sd and if alot of data is there that maybe the cause of the reboots. Try a different sd for a few days or none at all. See if you have the problem.
andrewwright said:
How much data do you have on ext sd? Maybe phone is scanning ext sd and if alot of data is there that maybe the cause of the reboots. Try a different sd for a few days or none at all. See if you have the problem.
Click to expand...
Click to collapse
I have almost 29 gb on the sd, but I had that data since the very first day I bought the card....thats more than one year ago. And I started having the problems since february of this year....
The problem has not reappeared. But what I still have is an insane battery consumption. See, I use apps like Facebook and Twitter, but I too use Greenify to hibernate them. It even drains too much battery by using the web browser. And I repeat, those problems trace back to February...which is the month when I accidentaly formatted the internal SD Card...
One year old + battery using Facebook and twitter and all the rest of them very power hungry apps are no good for battery life. Greenify uses battery, people forget that too. Remove all the apps above and test. Also if anything formatting int SD will speed up the phone not slow it down. It get rid if all the bit left over from ROMs/Recovery's/kernel's. Formatting int sd is good for the phone once in a while. Just remember to back up data first
andrewwright said:
One year old + battery using Facebook and twitter and all the rest of them very power hungry apps are no good for battery life. Greenify uses battery, people forget that too. Remove all the apps above and test. Also if anything formatting int SD will speed up the phone not slow it down. It get rid if all the bit left over from ROMs/Recovery's/kernel's. Formatting int sd is good for the phone once in a while. Just remember to back up data first
Click to expand...
Click to collapse
Thanks! Whenever I can, I will try those tips for battery saving.
But what still puzzles me is the "Sudden reboot problem". It vaguely happens, but when it does I am basically screwed, and each time the reboots seems to get worse from recovering....Also, the reboot problems started after formatting the int sd card for first time. And, after that, I remember that, when I wiped data for installing a new ROM, it gave me "(E: unknown volume for path [/sd-ext])" or, something similar. Does this help you for identifying my problem?
OK, now I am royally screwed
I have suffered another sudden bootloop problem, and this time, even by removing the ext SD Card, phone doesnt restarts. Also, I cant access to the Recovery Menu. It does appear for a while and then fades away. But the worst part is that I cannot get into the Download Menu. When I get to the select screen, when I cant choose between Continue and Cancel, the Volume buttons doesnt work. I can not get into Continue button. And then it restarts.
So this time I can not even access to the Download Menu.
I am using the same ROM as before: Neat ROM 6.7 with CWM Touch 6.0.3.2 and Boeffla Kernel
I dont know if I can even send the phone to repair, as seen that I may have the Binary Counter...and I cant even access to Download.
Please, really, help me to get out of this, so I can factory reset this.
Take the battery out then hold buttons for download mode and while holding these buttons put the battery back in and pray mate. Not being able to get into download/recovery mode as you know is really not good. Maybe a jig to force it to download mode.
andrewwright said:
Take the battery out then hold buttons for download mode and while holding these buttons put the battery back in and pray mate. Not being able to get into download/recovery mode as you know is really not good. Maybe a jig to force it to download mode.
Click to expand...
Click to collapse
I did that, and I got into the Download Menu. But the menu was frozen as usual. I could not access to the Odin Menu. It didnt matter which option I chosed, since both of them didnt work and the menu would still be frozen, and then restarting the phone a few seconds later. I mean, I got to the screen where you can choose to get to Download Mode or to restart the phone, and it still was a stuck screen, no matter what I chose, the options did not work, and then the phone restarted again.
And I have no jig next to me. So, I am screwed. For real.
Im going to take it to the store where I bought it, which is near where I live...To see if they can do something. Otherwise...I think I will throw away this phone. Its been almost 2 years, and recently it started to fail, probably because of a crappy emmc chip...that store sells the Moto G, which is great, since I dont plan to waste a lot of money on a new phone, watching how this has ended.
And it sucks that I can not recover the data in the Internal SD
Hello!
Having a problem with i9300 device.(4.3 rom)
The phone starts up. Can use device for approx. 2 minutes, then freezes,screen goes blank and phone restarts automatically.
Recovery mode does not hang but is kind of slow and does not always reply to pushing volume up/down.
Have tried setting usb debugging on to flash but no use,if phone freezes so fast.
Also tried several times recovery mode-wiping and restoring to factory, but it doesn´t help. Phone still freezes after 1-2 minutes.
May You please offer a solution I could try?
Thanks!
rom?
original rom. phone has never been modded,used only latest update by samsung.I can write exact rom version in the evening.
Boot into download mode and see it happens there. If not then flash the latest stock firmware for your country with odin, factory reset in recovery before first boot.
If the phone freezes or reboots while in download mode then you have a hardware fault.
boomboomer said:
Boot into download mode and see it happens there. If not then flash the latest stock firmware for your country with odin, factory reset in recovery before first boot.
If the phone freezes or reboots while in download mode then you have a hardware fault.
Click to expand...
Click to collapse
I will try that in evening and will let You know how it worked out. :good:
Tried latest firmware with odin. Download mode works fine and goes all the way to the end. but after finishing and first boot, setting up android language etc. for the first time, it hangs about 1 minute again.
hardware faulty then?
Yes, it sounds like it -something is breaking down after a little use.
if some part of hardware is faulty, is there maybe some kind of diagnostic tool that I can run without booting android fully up? then I could get to know what kind of system part is problematic. If I'd find out problematic part, maybe there would be a change to modify android rom, so the problematic part of system would be turned off always?
just an idea
I doubt it, even Samsung don't bother with component diagnostic -they just replace the motherboard.
My wife had a similar problem with her phone. I downloaded Dummy File Generator from the Play Store n ran the application. Been more than 6 months now with no lag.
Hey guys, I just f***ed my phone up.
This is what happened
First of all, I'm sorry for my bad english, as I'm not a native speaker
I'm using Archi Droid v3.0.2, while playing a game my phone suddenly rebooted, I thought it was just overheated, but I got a bootloop, I tried to wipe cache & dalvik, reboot my phone... bootloop. I made it to the lockscreen though, but after 5 seconds it will reboot again. I'm wiping my phone through Philz & clean install the Archi Droid ROM, aanndd, still, bootloop. So I tried to restore my Lollipop backup (I downgraded my device to Kitkat because Lollipop is not as sweet as Xposed & A.D. ) and ... I can boot, BUT I CAN'T connect to the Internet, everytime my phone got "H+" signal on the top of the screen, the screen will flicker and signal will be lost (over and over). I can still make calls & sms though (if i turned the mobile data off). Then I tried to factory reset my Lollipop, and at first boot, it says "Installing Apps (or something) ... of 98" I thought it wouldn't install or upgrade any apps after factory reset. THEN I got bootloop again. I gave up, flashed stock firmware via Odin, succeeded. Going through setup & realized I still got this network problem, so i factory reset my stock 4.3 rom & after it finished... Planning to setup my phone and after 10 seconds I got bootloop again. I got a feeling (my feeling sucks) that this is a partition problem. So I tried to flash .pit file with samsung 4.3 stock firmware, and I'm stuck at "NAND WRITE START!!" in Odin. After praying for 1 hour I decided to remove the battery and disconnect my phone from the PC. Now everytime I flash something via odin, it will always stuck at "NAND WRITE START!!"
I want to try this (http://forum.xda-developers.com/galaxy-s3/help/solved-pit-bricked-dead-problem-gt-t2535367) though, but I'm afraid to mess my phone up even more.
Now I'm unable to flash ANYTHING into my phone, I need some (a lot of) help here. I'm going to university and asking for a new phone will get me into trouble (they will give me a $10 phone for sure). Thanks in advance
FonDwiputra said:
Hey guys, I just f***ed my phone up.
This is what happened
First of all, I'm sorry for my bad english, as I'm not a native speaker
I'm using Archi Droid v3.0.2, while playing a game my phone suddenly rebooted, I thought it was just overheated, but I got a bootloop, I tried to wipe cache & dalvik, reboot my phone... bootloop. I made it to the lockscreen though, but after 5 seconds it will reboot again. I'm wiping my phone through Philz & clean install the Archi Droid ROM, aanndd, still, bootloop. So I tried to restore my Lollipop backup (I downgraded my device to Kitkat because Lollipop is not as sweet as Xposed & A.D. ) and ... I can boot, BUT I CAN'T connect to the Internet, everytime my phone got "H+" signal on the top of the screen, the screen will flicker and signal will be lost (over and over). I can still make calls & sms though (if i turned the mobile data off). Then I tried to factory reset my Lollipop, and at first boot, it says "Installing Apps (or something) ... of 98" I thought it wouldn't install or upgrade any apps after factory reset. THEN I got bootloop again. I gave up, flashed stock firmware via Odin, succeeded. Going through setup & realized I still got this network problem, so i factory reset my stock 4.3 rom & after it finished... Planning to setup my phone and after 10 seconds I got bootloop again. I got a feeling (my feeling sucks) that this is a partition problem. So I tried to flash .pit file with samsung 4.3 stock firmware, and I'm stuck at "NAND WRITE START!!" in Odin. After praying for 1 hour I decided to remove the battery and disconnect my phone from the PC. Now everytime I flash something via odin, it will always stuck at "NAND WRITE START!!"
I want to try this (http://forum.xda-developers.com/galaxy-s3/help/solved-pit-bricked-dead-problem-gt-t2535367) though, but I'm afraid to mess my phone up even more.
Now I'm unable to flash ANYTHING into my phone, I need some (a lot of) help here. I'm going to university and asking for a new phone will get me into trouble (they will give me a $10 phone for sure). Thanks in advance
Click to expand...
Click to collapse
Lots of threads on this problem: Search results
josephiskandar said:
Lots of threads on this problem: Search results
Click to expand...
Click to collapse
Fixed the problem by using this, Rescue Firmware . Flashed 4.3 rescue firmware with pit file, it worked.
The battery caused boot loop on my phone, guess it's solved then