Hello!
I have a pretty bad situation going on with my phone. A couple of days ago I got a new battery for it off eBay, and I also flashed ParanoidAndroid 3.97. Around this time the phone kept crashing, the screen would freeze and then nothing. I tried doing a factory reset, and this fixed it for a while. Today it froze, so I turned it off, and it wouldn't boot back into android. I reflashed the ROM, and a load of other ones, but it refuses to boot at all. The closest it gets is the "finishing boot" stage of Android is upgrading and then it just reboots. I am now at a loss.
Any help would be greatly appreciated. I can provide extra details if you need it.
George
First what model phone is it .
Second read the faqs and guides .
Third read the Freezing thread .
jje
JJEgan said:
First what model phone is it .
Second read the faqs and guides .
Third read the Freezing thread .
jje
Click to expand...
Click to collapse
It's a GT-I9300, I've read everything there is - I know how you guys hate to be bothered by noobs who can't read.
George
Use the original battery, not ebay one. Flash an official stock 4.1.2 rom then factory reset before booting, check for any error messages in recovery.
If it still freezes before booting finishes then probably needs a new motherboard.
Also, don't pull battery or turn off while it's frozen -it's usually trying to deal with bad memory blocks and should resume if left long enough.
boomboomer said:
Use the original battery, not ebay one. Flash an official stock 4.1.2 rom then factory reset before booting, check for any error messages in recovery.
If it still freezes before booting finishes then probably needs a new motherboard.
Also, don't pull battery or turn off while it's frozen -it's usually trying to deal with bad memory blocks and should resume if left long enough.
Click to expand...
Click to collapse
Thanks for the advice. Is it possible that motherboard issues could have been caused by plugging it into my ASUS TF700 wall charger? I can't believe that Samsung would let that be a thing that could damage it and I only did it once but still.
Will try out your tips ASAP
Thanks
George
EDIT: No dice Thanks for trying
No, a charger would not damage the motherboard.
Related
Hi everyone,
Complete Noob here, and not proud of it.
I've been searching through your awesome forum now for the past few days trying to get an answer to a problem I have with my GT-I9300, but unfortunately i just seem to keep coming up with more and more problems. So begrudingly I have come to beg for help in the form of a new thread.
I had the phone running rooted with CWM and Cyanogen 10.1 with a fair amount of problems, it kept locking up.
So i was advised one of the best solutions would be to use a more stable version of Cyanogen so re flashed with 9. It worked pretty brilliantly up until some apps were updating and it just completely froze, at the time this was not a strange occurance because of the previous freezing issues i had. So i just restarted the phone.
I then get a message that the firmware has become corrupted and i need to re-install emergency firmware with Kies, tried this. nothing happened.
It has now come to only allowing me to boot into download mode, if i attempt a standard boot, or a recovery boot it goes into a white screen, which almost looks like static on an old analogue TV.
I am at my complete end with this phone, I have tried many re-flashes and versions of PDA files via ODIN and nothing has worked, I always seem to get a PIT Partition error.
I have now been trying to get this to work for at least 20 hours of my life and its finally enough, I would just be incredibly thankful if someone could let me know the problem and if there is a solution to this, I am yet to find anyone else suffering with this white static picture on boot.
When i boot into download mode, i get the red ODIN MODE setting, no product name, no custom binary download, the current binary is 'Samsung official' and the system status is custom.
I have tried reflashing to samsung stock, and that even fails.
Many thanks in advance. Any help will be greatly appreciated.
Reads as you need a service centre either damaged PIY or more likely damaged Nand .
jje
JJEgan said:
Reads as you need a service centre either damaged PIY or more likely damaged Nand .
jje
Click to expand...
Click to collapse
Agreed.
Please people, don't go back to ICS! It is unable to prevent your eMMC from death.
I heard that version 9 doesn't have the sudden death fix :/ Sorry mate you gotta take to to repair center.
Sent from my GT-I9300 using xda app-developers app
cheers everyone. I think deep down i knew that this would be the case.
Big expensive bill for me coming up i imagine.
Thanks again.
Service centre say my phone wont boot i this the sudden death syndrome .
Is what i would ask and just look dumb .
jje
coop_80 said:
cheers everyone. I think deep down i knew that this would be the case.
Big expensive bill for me coming up i imagine.
Thanks again.
Click to expand...
Click to collapse
Sudden death :/
Hey guys,
I see that there are a few incidents of this occurring having read the forum and Google. Some advise the device needs 'j-tagged' others seem to have been able to eventually gain access to the Recovery mode.
Here's the low down; S3 was flashed with Cyanogenmod 10.1 and was working fine for months. Last night, as normal, I switched over batteries to a fully charged one. On restarting the phone I was presented with warning about a firmware upgrade that went wrong (can't remember the exact wording as it was late and I was in bed at this stage).
On seeing the warning I tried restarting the phone but same again and then I set it down to deal with it today. Woke up to a white screen and grey lines. I can't get into Recovery mode.
Now I didn't try to upgrade the firmware or anything else, this message just appeared upon changing the batteries and therefore a power cycle.
Odin seems to see the device on Com 5 but after that I am not sure what else to do.
How can I flash a new ROM without Recovery access? Any ideas?
Thanks in advance guys,
Reply to identical question .
Read the stickied basic faqs and guides .
Flash a stock rom via Odin .
JJEgan said:
Reply to identical question .
Read the stickied basic faqs and guides .
Flash a stock rom via Odin .
Click to expand...
Click to collapse
Cheers mate.
OP, there was no reason to post this thread twice. Please in the future 1. search before posting. 2. Post only once, not multiple times
Please take a moment to review the forums Rules
Problem sorted. Thanks
Al Bino said:
Problem sorted. Thanks
Click to expand...
Click to collapse
Just an update for those that may have the same issue.
Sent the phone back to Samsung and they replaced the motherboard ("PBA MAIN") and LCD ("OCTA LCD SVC/RW").
Not sure why they replaced the LCD unless they damaged it replacing the motherboard? Either way phone was returned in new condition as I had originally had a few marks on the chrome strip around the phone, now gone. So well pleased.
Hey guys,
I have a galaxy s3 (I9300) and I've had it rooted for some time now. I started using CyanogenMod 10.2 nightlies a few months ago and they've mostly been fine. The odd issue comes up but I've been able to work it out. So, a few hours ago my phone just turned off of its own accord and started to bootloop, but on the "Samsung Galaxy S3 GT-19300" screen, not the CyanogenMod screen (to clarify, this screen comes up first then the cyanogenmod one usually). I've tried booting into recovery (CWM 6) but it just shows the CWM boot logo thing (that cog with the hat) and then loops back to the galaxy s3 page. I've also tried putting it in download mode, and it seems to stay on the warning page longer than it does anywhere else, but it wont let me actually put in it download mode from there.
I had a look around google and saw people have had the same problem, but everything I could find was when people had flashed a new rom/kernel etc. and something had gone wrong in the process. The weird thing about mine is that I haven't changed anything, even downloaded any new apps, for maybe a week, so it's not like something suddenly changed. I also wasn't using it when it started, it was just sitting on the table next to me.
Usually I can work these things out, but I'm stumped here. Any help would be really appreciated.
Thanks in advance!
danielbollom said:
Hey guys,
I have a galaxy s3 (I9300) and I've had it rooted for some time now. I started using CyanogenMod 10.2 nightlies a few months ago and they've mostly been fine. The odd issue comes up but I've been able to work it out. So, a few hours ago my phone just turned off of its own accord and started to bootloop, but on the "Samsung Galaxy S3 GT-19300" screen, not the CyanogenMod screen (to clarify, this screen comes up first then the cyanogenmod one usually). I've tried booting into recovery (CWM 6) but it just shows the CWM boot logo thing (that cog with the hat) and then loops back to the galaxy s3 page. I've also tried putting it in download mode, and it seems to stay on the warning page longer than it does anywhere else, but it wont let me actually put in it download mode from there.
I had a look around google and saw people have had the same problem, but everything I could find was when people had flashed a new rom/kernel etc. and something had gone wrong in the process. The weird thing about mine is that I haven't changed anything, even downloaded any new apps, for maybe a week, so it's not like something suddenly changed. I also wasn't using it when it started, it was just sitting on the table next to me.
Usually I can work these things out, but I'm stumped here. Any help would be really appreciated.
Thanks in advance!
Click to expand...
Click to collapse
can you at least enter download mode after a long time you said? if not, try pulling out the battery for 5 minutes or more and re-insert and enter download mode. i hope it's not sds! good luck
sriram231092 said:
can you at least enter download mode after a long time you said? if not, try pulling out the battery for 5 minutes or more and re-insert and enter download mode. i hope it's not sds! good luck
Click to expand...
Click to collapse
Nope, if I press the volume up button to go into it, it just goes back to the bootloop. I'll try the battery thing though, thanks!
Nope, it didnt work, I left it out for maybe half an hour and nothings changed :/ anyone else got any ideas?
SDS thread and BootLoop identical questions posted .
What does Product Code say in download mode .
But if you cannot get to download mode then you need a service centre repair .
looks like u are facing SDA but a bit diffrend than a normal SDS.. mine still can go into download mode with blank product name..
If product name is blank in download mode then you got sudden death, consider a phone as a brick. Nothing will help, including repartitioning.
You need to contact service centre.
I'll check it in a minute, but if it is bricked, will any service center actually help me seeing as it's rooted and all?
danielbollom said:
I'll check it in a minute, but if it is bricked, will any service center actually help me seeing as it's rooted and all?
Click to expand...
Click to collapse
AFAIK if it's sudden death then it's not possible to detect root and other modified things, or in other words - nobody has money to prove that you have been using unofficial firmware .
JustArchi said:
AFAIK if it's sudden death then it's not possible to detect root and other modified things, or in other words - nobody has money to prove that you have been using unofficial firmware .
Click to expand...
Click to collapse
Ahhhh, well that is handy then
In terms of a service centre, will samsung have a list of them somewhere so I can find one near me?
So I contacted samsung and they gave me the link to book into a service centre etc, but I just realised that when I try to go into recovery mode, the CWM recovery logo comes up before going back to bootloop. Is there any way to get rid of that so that my root is completely untraceable?
danielbollom said:
So I contacted samsung and they gave me the link to book into a service centre etc, but I just realised that when I try to go into recovery mode, the CWM recovery logo comes up before going back to bootloop. Is there any way to get rid of that so that my root is completely untraceable?
Click to expand...
Click to collapse
If you can't flash anything with Odin (stock software) then you're screwed. Eventually you can try to enter recovery and flash "eraser" of recovery, but this requires working recovery... So if you actually can enter recovery then you can also flash anything, which will literally delete everything.
In other case, no, no way. But if you're lucky enough you may break it just by leaving your phone on for some hours in bootloop, haha.
JustArchi said:
If you can't flash anything with Odin (stock software) then you're screwed. Eventually you can try to enter recovery and flash "eraser" of recovery, but this requires working recovery... So if you actually can enter recovery then you can also flash anything, which will literally delete everything.
In other case, no, no way. But if you're lucky enough you may break it just by leaving your phone on for some hours in bootloop, haha.
Click to expand...
Click to collapse
Is there any way to wipe it with magnets or anything? hahah I'm clutching at straws now, but otherwise I'm just left with an expensive paperweight so I'm trying to find anything I can
danielbollom said:
Is there any way to wipe it with magnets or anything? hahah I'm clutching at straws now, but otherwise I'm just left with an expensive paperweight so I'm trying to find anything I can
Click to expand...
Click to collapse
To be honest think twice before physically crashing your internal memory, as it may void your warranty at all.
I'd try flashing stock firmware through odin, if it doesn't work I'd try flashing anything through recovery. If both of these methods fail just leave your phone in bootloop and hope that it'll automatically destroy everything... :laugh:
Seriously though, you can either physically destroy internal memory or leave it in bootloop and hope for the best, eventually send them device in current status. Up to you, because you won't have a possibility to do anything else.
JustArchi said:
To be honest think twice before physically crashing your internal memory, as it may void your warranty at all.
I'd try flashing stock firmware through odin, if it doesn't work I'd try flashing anything through recovery. If both of these methods fail just leave your phone in bootloop and hope that it'll automatically destroy everything... :laugh:
Seriously though, you can either physically destroy internal memory or leave it in bootloop and hope for the best, eventually send them device in current status. Up to you, because you won't have a possibility to do anything else.
Click to expand...
Click to collapse
If I send it back to them as it is now it'll take them about 20 seconds I reckon before they see the CWM logo, realise its rooted and send it straight back, so I dont know what I'm gonna do hahah
Hi,
last night my phone went out of battery and in the morning I put it in charge when I looked back at it was frozen on charging logo(the logo wasn't moving)
I had to take the battery out and after that if I put the battery in early it turns on by itself, If I keep the battery out for a moment and then plug it init keeps being off until turn it on and then freezes with s3 logo.
I tried hard reset it gives me an error of "failed to mount system invalid argument"
My phone is normal s3 I9300 with all automatic updates installed.
I had installed no programs recently just did an update of softwares earlier during the day.
Regards
Reza
Please go first to the FAQS and Guides and read the FREEZING thread and the SDS thread .
http://forum.xda-developers.com/showthread.php?t=2133401
My phone is stock at the booting logo, and doesn't even show the recharging animation. the thread here is about phones freezing and then unfreezing themselves
aldrinmcmie said:
http://forum.xda-developers.com/showthread.php?t=2133401
Click to expand...
Click to collapse
SDS thread
this threat is about old androids as far as I know I had the latest firmware released for S3 installed.
any ideas?
Read the faqs and guides or take the phone to a service centre
raymound said:
My phone is stock at the booting logo, and doesn't even show the recharging animation. the thread here is about phones freezing and then unfreezing themselves
SDS thread
this threat is about old androids as far as I know I had the latest firmware released for S3 installed.
any ideas?
Click to expand...
Click to collapse
Enter recovery mode (hold home + volume up + power)
choose wipe data / factory reset
raymound said:
My phone is stock at the booting logo, and doesn't even show the recharging animation. the thread here is about phones freezing and then unfreezing themselves
SDS thread
this threat is about old androids as far as I know I had the latest firmware released for S3 installed.
any ideas?
Click to expand...
Click to collapse
why olds? As you can read, people even with newest Android version has SDS issue, 'cause newest Android version can't make you safe 100% from SDS because it's hardware issue.
Hi guys. I have seen and read through plenty of the same problems regarding the bootloop issue on the forum. I seem to be stuck somewhere different so I post this question. I hope someone can help.
I have a standard S3 I-9305 LTE in South Africa. Not rooted before or any mods. But somehow it started bootlooping a couple of weeks ago. I read and implemented the Recovery Mode- Cleared the cache and then rebooted, and it worked, plenty of times.
But now it has gone into a solid bootloop and i cannot access recovery mode. So read up about Download mode and installed Odin, Kies and the Cf Root file on my PC.
Now when I enter Download mode on the phone, and continue( press Volume Up) after the warning, the device restarts again. This I have done a hundred times and each time removing battery and waiting a couple of minutes. So essentially I cannot get Download mode to function but I do have access to it.
So this I know, this is a software , possible ROM problem, NOT hardware as the device worked perfectly after bootloop issue started.
I did the latest Firmware Upgrade to Android 4.2( i think, i r noob in this) yesterday. This was done on the phone itself under About-check-firmware. The Phone worked fine afterwards but then went into this never ending tormenting bootloop without yielding.
I live far from a proper service centre and I need my phone for work, thus very urgent.
I also have checked if the power button is stuck but it is not.
I am prepared to root the device and install any other ROM, Flash anything that can get me back on.
Any advice please?
Thanks in advance
Report your own post and ask a moderator to move it to the i9305 q&a forum.
Sounds like the emmc chip is corrupt or damaged, you may require a new motherboard.
Try plugging your phone into pc before you access download mode, remove the battery before you press volume up.
Sent from my GT-I9300 using Tapatalk
Caution and thanks
boomboomer said:
Report your own post and ask a moderator to move it to the i9305 q&a forum.
Sounds like the emmc chip is corrupt or damaged, you may require a new motherboard.
Try plugging your phone into pc before you access download mode, remove the battery before you press volume up.
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
Hi Boom,
I have seen you have diligently answered many queries, please to be cautious saying it is a motherboard or hardware issue, it makes peoples heart sink before trying other avenues first. But don't get me wrong, the fact that you took the time to answer me makes you my hero. :good: And thanks.
I will try the other option you gave as I know the phone is fine the answer is just a few tries away.