It's been a week or so that my phone freezes. If I leave it for some 20-30 minutes, it resumes normal operation. However these freezes are very frequent. This is happening on all ROMs I'm flashing. I even tried flashing pure stock ROM (ZSEMA1), and the freeze is still happening. Before I take it to the dealer (I live in a country where Samsung is not present, and the dealer will most probably need to ship it away for fixing), I'm trying to see if this happened with anyone else and how they managed to fix it. Also, other than resetting the flash counter, what do I need to do in order to take it back to complete stock?
Hi! I have the same problem. I rooted my phone and loaded clockwork recovery and flashed the camera app from 4.2
Now my phone randomly freezes (always when in sleep so I can't turn it back on). Only way to get it to start is to remove battery or soft reset. Any one else have this?
Is your phone around 6mths old, by the accident? Did it started recently?
I do not want to be bad news trumpet, but please read symptoms in this thread...
spamtrash said:
Is your phone around 6mths old, by the accident? Did it started recently?
I do not want to be bad news trumpet, but please read symptoms in this thread...
Click to expand...
Click to collapse
I had checked it, and indeed my phone's eMMC is VTU00M. However even the XXELLA ROMs are still freezing.
Have the same issue, random lockups. I have the SDS eMMC so Im giving the XXELLA flash a try...
vikeor said:
Have the same issue, random lockups. I have the SDS eMMC so Im giving the XXELLA flash a try...
Click to expand...
Click to collapse
I have tried Omega 38. Now I'm back on stock, XXELLA, and still getting lockups.
pushrodv8 said:
I have tried Omega 38. Now I'm back on stock, XXELLA, and still getting lockups.
Click to expand...
Click to collapse
Remove Ext SD Card .
Wipe phone / format sd card through CWM recovery .
Flash correct stock firmware via Odin .
Install no apps and test > fails return to service centre .
jje
pushrodv8 said:
I had checked it, and indeed my phone's eMMC is VTU00M. However even the XXELLA ROMs are still freezing.
Click to expand...
Click to collapse
You know, if your eMMc is already failed - new ROMs are unable to do anything. The nature of so called "fix" is the prevention only, there are several threads about SDS AFTER flashing XELLA/XELLC in General section.
SOLVED
Ok so since I'm in Qatar I flashed the United Arab Emirates stock ROM (XXELLB) and it's been 1 day without any hiccups. This is the longest the phone has gone without hanging, and I must say the it's REALLY VERY RESPONSIVE. Crossing fingers.
Related
My phone started rebooting several times. At first I thought it was the custom ROM, but it started happening in ALL roms I tested, specially when I try to test GPS: it just NEVER works. And that also happended with completely different basebands (Tested .49, .52, .54 and .58), 2.1, 2.2 and 2.3 ROMs.
My last attempt was to a clean Froyo FreeX10 beta install. Bb .54, Full wipe, etc etc.. For a few hours everything was normal but when I tried GPS (Google app) it restarted and ended up in a boot loop. Removed battery but it continues into loop.
Should I flash SE original ROM again (using SEUS?) to see if works? I'm out of ideas right now, please help!
Arrrgh! It's even worst than I thought. I tried flash Generic version 2.1update1 build 2.1.A.0.435 and the random reboots persists.
Also I noticed some weird things using Wifi, downloads on Marked just doesn't start, get paused like forever... HELP!!!!
I suppose force a repair with seus.and if that doesn't fix it then it might be some hardware issue :/
Sent from my Delorean using a flux capacitor!
Thanks. I even formatted my SD Card but still with problems, I'm thinking about buy a bigger/faster one and maybe another battery, but if it's the phone itself the problem then I'm in trouble.
PS: I tried SEUS but no go :S
sounds like the same problem i and other users have faced, tell me when the phone reboots take the battery out and give the phone a smell, does it smell like burning? mobo has gone
I say remove the GPS app using adb. Then flash a new ROM from scratch. Then install another GPS app.
lolman2810 said:
sounds like the same problem i and other users have faced, tell me when the phone reboots take the battery out and give the phone a smell, does it smell like burning? mobo has gone
Click to expand...
Click to collapse
Ouuuuch! It does! I thought it was the battery dying but in this case should I flash back to stock and use my warranty?
kozxmartt said:
I say remove the GPS app using adb. Then flash a new ROM from scratch. Then install another GPS app.
Click to expand...
Click to collapse
Thanks, didn't even know it was possible, will give it a try but now I think its the mobo
what is moboo?
mobo = mother board
Just FYI, my phone is on technical assistance right now and they informed it will take long because many X10 are having the same issue, it will probably be escalated to SE and I will probably receive a new one
Now let's wait, will report back later.
Hi, I'm having a really difficult time with my S3. I've rooted and flashed it with Supernexus 3 (4.3) however it has been constantly locking up and freezing randomly. Approximately 15 times a day. I have now reset/data wipe the phone and reflashed the ROM but same issues. I have also tried CM10 Official nightly build and it still locks up. I have tried it with and without restoring user apps + data. What could the problem be anyone? Any help would be appreciated.
The problem could be your custom set up, factory reset and flash a stock 4.1.2 rom to test.
If it still freezes on stock then you probably have bad memory blocks, go read the 'unusual freezing' thread in the general forum.
boomboomer said:
The problem could be your custom set up, factory reset and flash a stock 4.1.2 rom to test.
If it still freezes on stock then you probably have bad memory blocks, go read the 'unusual freezing' thread in the general forum.
Click to expand...
Click to collapse
Thanks for reply. Will check that tonight. How do I know what's thet stock ROM for my handset? I have a sim free s3 and based in UK.
If it doesn't freeze on stock then what would you suggest?
See sammobile.com for stock roms .
No freeze on stock bad rom faulty flash a bad file wrong instructions etc etc .
jje
boomboomer said:
The problem could be your custom set up, factory reset and flash a stock 4.1.2 rom to test.
If it still freezes on stock then you probably have bad memory blocks, go read the 'unusual freezing' thread in the general forum.
Click to expand...
Click to collapse
JJEgan said:
See sammobile.com for stock roms .
No freeze on stock bad rom faulty flash a bad file wrong instructions etc etc .
jje
Click to expand...
Click to collapse
So i've been on stock rom for the whole day whilst also rooting again and haven't had any freezes whatsoever. Even when restoring apps using Titanium Backup there were no freezes. Under custom setup there were multiple freezes alone whilst restoring apps. I doubt I have followed instructions incorrectly (don't mean to sound like a [email protected] ) but I have flashed ROMs multiple times before with no issues, and hey, even managed to flash back to custom ROM successfully. I just don't get how I can have the same locking/freezing issues on 2 separate ROMs (CM10, Supernexus) but not have it on stock ROM.
I had a look at the unusual freezing thread and I thought it may have applied to me as my phone has been fixed to repair the 'Sudden death' fault but after flashing stock rom, I have had no freezes.
Any ideas? I have put back my Nova Launcher configuration however it just feels clunky with stock rom. And oh, it's still 4.1.2.
I want 4.3 Supernexus
I rooted my S3 about a year ago, when I got it first using CF-Root. Had zero problems.
Gave it to the girlfriend a month ago. Did a factory reset etc, but left it rooted. I did however take out my sd card(which probably has something to do with the problem?)
Anyways, 3 days ago, the wifi suddenly stopped working on it all of a sudden. The wifi tab is kind of greyed out and wont turn on or scan for any networks. (see photos below)
I tried turning the phone on/off, taking out the battery etc. Nothing worked.
I then flashed the same ROM back onto it and the problem disappeared for a day, but then all of a sudden reappeared! I thought I had fixed it, but no!
I put back in a sd card,I then downloaded and flashed another Rom(CM 10.2) using Rom manager from the sd card, and the problem disappeared again.
But after 12 hours both the wifi and the 3G stopped functioning
I've no idea what is the problem. Can anyone help me out with this? Could it be the kernel that's causing the problem? I'm not very tech savvy guys. I know how to root the phone, but I've had to deal with any issues.
I'd really appreciate any help, as we need access to the net from our phones. I've included photos below so that you can see the rom and kernal and other details that may help ye decipher the problem.
http://imageshack.com/a/img856/1443/c3ow.jpg
http://imageshack.com/a/img46/1797/euiv.jpg
http://imageshack.com/a/img196/4737/drsa.jpg
Did you check logcat for any clue?
Stop running nighties. Problem solved.
hberntsen said:
Did you check logcat for any clue?
Click to expand...
Click to collapse
No idea what that is?
xclub_101 said:
Stop running nighties. Problem solved.
Click to expand...
Click to collapse
Problem was present before I flashed the CM nighties, so that doesn't mean it's the issue!
chicoelnino said:
I rooted my S3 about a year ago, when I got it first using CF-Root. Had zero problems.
Gave it to the girlfriend a month ago. Did a factory reset etc, but left it rooted. I did however take out my sd card(which probably has something to do with the problem?)
Anyways, 3 days ago, the wifi suddenly stopped working on it all of a sudden. The wifi tab is kind of greyed out and wont turn on or scan for any networks. (see photos below)
I tried turning the phone on/off, taking out the battery etc. Nothing worked.
I then flashed the same ROM back onto it and the problem disappeared for a day, but then all of a sudden reappeared! I thought I had fixed it, but no!
I put back in a sd card,I then downloaded and flashed another Rom(CM 10.2) using Rom manager from the sd card, and the problem disappeared again.
But after 12 hours both the wifi and the 3G stopped functioning
I've no idea what is the problem. Can anyone help me out with this? Could it be the kernel that's causing the problem? I'm not very tech savvy guys. I know how to root the phone, but I've had to deal with any issues.
I'd really appreciate any help, as we need access to the net from our phones. I've included photos below so that you can see the rom and kernal and other details that may help ye decipher the problem.
Click to expand...
Click to collapse
Have you tried flashing it back to a pure stock ROM (or maybe a stock derived ROM like WanamLite or Imperium) ?
hundred_miles_high said:
Have you tried flashing it back to a pure stock ROM (or maybe a stock derived ROM like WanamLite or Imperium) ?
Click to expand...
Click to collapse
No, I haven't. Simply because I'm not sure which ROM is suitable for me.
Could you point me towards a link to that ROM(a version that works on my phone, or does it matter?)
I'm lost with all the different ROM's etc at this stage, and all I want is for the phone to be back working - whether that's with or without root access. It's for my girlfriend, so she hasn't a clue about root etc.
Thanks for any help you can provide.
chicoelnino said:
No idea what that is?
Click to expand...
Click to collapse
Via logcat you can see messages from android's internal logging system. A lot of times the internal errors you don't see can be obtained via logcat. Look at http://www.xda-developers.com/android/help-your-developers-pull-a-logcat-when-issues-arise/ and https://www.xda-developers.com/tag/logcat/ for more info.
Can anyone just suggest to me a way to get the phone back to it's original state either rooted or unrooted...I don't care.
I just need to get the phone fixed so that my g.friend has a phone that has wifi working properly.
Do I need a different kernel or something? I'm lost, so any help as to what direction to that is appreciated.
Its all posted in the fff Faqs and Guides .
Please read how to return to stock for warranty post .
Hy everybody. I'm here to took with you about a common problem on samsung s3. One week ago i notice that i can't receive calls, messages etc and i found the "not registered on network" problem. What actually i want to say, is the fact that it appear suddenly, my phone always have 4.3, i didn't upgrade nothing....the problem persist, i changed sim, modem.bin, flash 4.1, modified network connections from setting....nothing work!!! I always have signal but that's all....what can i do more? (and my imei has changed to this: 00499*******
international variant
Perseus said:
Can you please let us know if you have international variant or US Variant ? If US then which carrier please ?
Click to expand...
Click to collapse
My phone is a international variant, made in Vietnam, i also tryed to flash 4.1.2 I9300XXEMG4, so then i can flash MG4 modem which can still read the modified EFS...if it is modified, but didn't work.., i think i need to send the phone to a gsm/service, but maybe you guys can help me without cost me money..
Perseus said:
I will request to have your thread moved to appropriate forum.
Click to expand...
Click to collapse
thx man, i hope someone knows how can i solve the problem.
What had you done before you got to this issue of no cellular signal?
Did you flash a custom ROM etc..? Which version were you on before? 4.3?
What did you do after you found out about this issue? Did you by any chance flash an older version?
Because that tends to do that, atleast that's what happened to me.
I had a wrong/fake IMEI ("0049..."), which caused that I had no cell reception and couldn't use the phone to call or send/receive sms etc...
I googled a lot and I tried some of the TUT on the web, but nothing helped. Until I found a thread on the xda that said one could try to flash a newer stock ROM (don't know the exact thread).
So I went ahead and checked the version I was on...luckily it was 4.0.4
I then downloaded a newer stock ROM 4.3 for my region and flashed that using ODIN...once it passed I went to recovery: wiped cache and factory reset.
and voila...when I checked the IMEI code again, it was back to the original one.
If that doesn't help check the following thread on xda: here
I suspect he allowed the battery to run out, which corrupted the efs partition, as he says his phone was on 4.3 and didn't change anything until after the problem happened.
Flashing latest stock firmware is the first step, as suggested above, but I think the OP may have to pay for a repair. Make sure it works on 4.3 before you accept the bill.
I forgot to say, my battery got bigger before that happened, i can't fit it in my phone, is double than a normal one, i buy other battery, have this something to deal with the problem?
Sent from my GT-I9300 using XDA Free mobile app
contactmsd said:
What had you done before you got to this issue of no cellular signal?
Did you flash a custom ROM etc..? Which version were you on before? 4.3?
What did you do after you found out about this issue? Did you by any chance flash an older version?
Because that tends to do that, atleast that's what happened to me.
I had a wrong/fake IMEI ("0049..."), which caused that I had no cell reception and couldn't use the phone to call or send/receive sms etc...
I googled a lot and I tried some of the TUT on the web, but nothing helped. Until I found a thread on the xda that said one could try to flash a newer stock ROM (don't know the exact thread).
So I went ahead and checked the version I was on...luckily it was 4.0.4
I then downloaded a newer stock ROM 4.3 for my region and flashed that using ODIN...once it passed I went to recovery: wiped cache and factory reset.
and voila...when I checked the IMEI code again, it was back to the original one.
If that doesn't help check the following thread on xda: here
Click to expand...
Click to collapse
I was on 4.3 version, i didn't do nothing, i even not installed the root/cwm....the problem appeared from nothing...right before i change my battery. I tried with my region stock rom (4.1.2;romania) and with 4.3 stock ROM but didn't work.
Today i let the phone on a service....i told her what is the problem and i hope there's nothing to do with motherboard. Anyway, please let me know if there's something else to do while i wait 3-4 days for the answer
Spike97 said:
I forgot to say, my battery got bigger before that happened, i can't fit it in my phone, is double than a normal one, i buy other battery, have this something to deal with the problem?
Sent from my GT-I9300 using XDA Free mobile app
Click to expand...
Click to collapse
That's not good...bulging/expanding battery is a very bad thing and should be replaced asap.
Why it happens, is another thing...could be due to various reason such as thermal runaway or even acid leakage.
Fix that first before you move to any flashing and/or other stuff...
contactmsd said:
That's not good...bulging/expanding battery is a very bad thing and should be replaced asap.
Why it happens, is another thing...could be due to various reason such as thermal runaway or even acid leakage.
Fix that first before you move to any flashing and/or other stuff...
Click to expand...
Click to collapse
I already replaced it.
Fixed
Hi everybody, i finally sent the phone to service and they fixed it for 17€; everything ok, no problem occurred...i flashed stock 4.3 ROM, then CWM and SU, but....then....after one day of use, i forgot to shut down the phone and, again, removed the battery with the screen on....i connected quickly the battery and the phone started without press any button.....and then, surprise!!! Me trying to make a phone call: "Not registered to network"...fu**...but IMEI was still alright(w t f?). Third day i sent again the phone to the service and they told me that i am playing whit the soft (what man? just because i flashed CWM and SU? damn), i told them again what i do with the battery and they said is not true (now what i am supposed to do? they don't trust me) but fixed it again free..for first and last time. Now here is the question: what i need to back up in case that will happen again? It can't be fixed with a backup of IMEI/Modem file...
Go read the sticky thread in general forum.
Samsung Galaxy 3 SPH l710 d2spr
running aicp_d2spr_mm-11.0-NIGHTLY-20160709
last Saturday while using GPS the phone shut down.
later it started crashing. It would not get beyond the splash screen.
I could get into recovery(Philz) with no issues, but It was giving me root broken or
missing error mssg.
Tried to reflash recovery with no luck. Later I tried restoring defaults which seemed to fix the problem since i wasn't getting that error anymore. Thinking my problem might have to do with file corruption, I reflashed the ROM. Still crashing. I decided to return to stock, but the problem persists. I get to the Sprint logo and the phone crashes. It's been someowhat inconsistent. Sometimes I get to the launcher before it
crashes, but since I've gone back to stock.
Apart from Flashing last monday, I have not made any changes.
Suspecting a hardware issue. Any ideas?
P.S Did Factory rest with both installs. no luck
You can flash a firmware with PIT-file to rewrite partitions. If this doesn't help, it's the hardware (battery?).
rp158 said:
You can flash a firmware with PIT-file to rewrite partitions. If this doesn't help, it's the hardware (battery?).
Click to expand...
Click to collapse
Are you suggesting the problem might be something like bad sectors? and are you suggesting that maybe the battery is either dead or not holding a charge? If I put it into recovery it stays on. Only when I try to reach the launcher do I run into problems.
Thanks for the response
@sp1ke0kill3r: for suggesting anything your report is too unprecise. If firmware runs unstable, you can qua software only do one more basic step: repartition (if partition-table is ill, you mostly cannot boot - so unlikely here). Battery with instable voltage can cause such behaviour too. You'll have to try...
rp158 said:
@sp1ke0kill3r: for suggesting anything your report is too unprecise. If firmware runs unstable, you can qua software only do one more basic step: repartition (if partition-table is ill, you mostly cannot boot - so unlikely here). Battery with instable voltage can cause such behaviour too. You'll have to try...
Click to expand...
Click to collapse
What does qua software mean? Any way to determine if PITfile is ill? And where can I find information on using a pit file to repartition?
@sp1ke0kill3r: qua means concerning. PartitionTable may be damaged, not PIT-file. But as I said, it's unlikely, if phone boots fine. Firmware for repartition you'll find by xda-search
rp158 said:
@sp1ke0kill3r: qua means concerning. PartitionTable may be damaged, not PIT-file. But as I said, it's unlikely, if phone boots fine. Firmware for repartition you'll find by xda-search
Click to expand...
Click to collapse
Thanks, RP!!