Related
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.
Hey there!
Before anyone asks, I have done the following.
Searched on google/XDA for solutions
Flashed different ROM's
Changed Kernels
Wiped all cache
Did factory Reset
I am currently having bad network problems with my phone.
I am running JellyBam 6.7.0 with default kernel.
Baseband: XXLQ6
Problem
I constently get No Service or "Emergency Calls only" in areas that I've never had emergency calls in. I am not aware of my old modem or RIL, and so am completely lost of what to go from here as I haven't found posts that could help my issue.
When I reboot my phone, turn airplane mode on, or just randomly it will go into the stage above, to where it will stay without signal for 10 minutes up to days (I've had it go for 2 days with no signal). When I try to search for networks (In places where there is 100% a network) it will say "error searching for network".
I have no idea what to do, and am rather scared. There have been 2 emergency situations to where I needed a phone, and yet mine had no signal.
My second question, is if I manage to get it back to stock ICS (4.0.4) and do all the updates through KIES, will I get the original modem + RIL back as well as the ROM? Or will I still need to flash that myself.
TLDR: If I reset it back completely to stock ICS, will everything that I have done (root, flash modems, flash kernels etc...) be erased.
Thanks so much for reading, I've got so much stress rigt now.
Are you getting no service all the time or only intermittently ? Also, check your IMEI in settings/about phone to see if it's the generic one (0049.....), whatever you do tho don't post your actual IMEI here. Just a yes/know answer to the 'is it the generic one' question will do.
If it's a constant thing, call your carrier to check if it's been IMEI blocked. If it's intermittent, flash a stock ICS rom as you'd suggested. You'll end up with whatever modem/baseband is attached to the rom you flash, and yes, you'll lose root & the kernel you're currently running will be replaced by the stock kernel in the rom you flash.
MistahBungle said:
Are you getting no service all the time or only intermittently ? Also, check your IMEI in settings/about phone to see if it's the generic one (0049.....), whatever you do tho don't post your actual IMEI here. Just a yes/know answer to the 'is it the generic one' question will do.
If it's a constant thing, call your carrier to check if it's been IMEI blocked. If it's intermittent, flash a stock ICS rom as you'd suggested. You'll end up with whatever modem/baseband is attached to the rom you flash, and yes, you'll lose root & the kernel you're currently running will be replaced by the stock kernel in the rom you flash.
Click to expand...
Click to collapse
Yes it's only intermittent, so not a problem with the IMEI.
So if I find, and download stock ICS to bring it to factory it should be fine? If I were to, let's say, flash the ICS onto the phone, is there any way to keep the RIL+ Baseband and flash back JB? Or when flashing JB, will it replace whatever RIL+Baseband is attached with the ROM.
Also, thanks for the quick reply. I was expecting days for a response.
Forget about JB/custom roms/anything else until or unless you get your phone working normally again. Flash an ICS stock rom for your region.
And forget about the current RIL/baseband. It sounds like it may well be the cause of the problems you're having; quite possible if you've been mucking around with different RIL's in particular. Pretty sure I said in my PP that you'll end up with whatever baseband is lumped in with the stock rom you flash.
Actually, you might want to stick with a stock rom specific to your carrier if there is one, at least that way you know the modem/baseband will more than likely have been tested by your carrier & is likely to work well with it unless there are other issues (carrier side connectivity issues or other problems with your phone).
As to whether doing this will fix your issues, no idea. At the moment, and in the absence of any clue as to what's causing your issues, it's the best option you've got. If it doesn't fix the problems, then it's probably a carrier-side issue (possible given it only happens at certain times/in certain locations) or a physical problem with the phone (less likely).
xxshabsxx said:
Yes it's only intermittent, so not a problem with the IMEI.
So if I find, and download stock ICS to bring it to factory it should be fine? If I were to, let's say, flash the ICS onto the phone, is there any way to keep the RIL+ Baseband and flash back JB? Or when flashing JB, will it replace whatever RIL+Baseband is attached with the ROM.
Also, thanks for the quick reply. I was expecting days for a response.
Click to expand...
Click to collapse
MistahBungle said:
Forget about JB/custom roms/anything else until or unless you get your phone working normally again. Flash an ICS stock rom for your region.
And forget about the current RIL/baseband. It sounds like it may well be the cause of the problems you're having; quite possible if you've been mucking around with different RIL's in particular. Pretty sure I said in my PP that you'll end up with whatever baseband is lumped in with the stock rom you flash.
Actually, you might want to stick with a stock rom specific to your carrier if there is one, at least that way you know the modem/baseband will more than likely have been tested by your carrier & is likely to work well with it unless there are other issues (carrier side connectivity issues or other problems with your phone).
As to whether doing this will fix your issues, no idea. At the moment, and in the absence of any clue as to what's causing your issues, it's the best option you've got. If it doesn't fix the problems, then it's probably a carrier-side issue (possible given it only happens at certain times/in certain locations) or a physical problem with the phone (less likely).
Click to expand...
Click to collapse
Thanks.
I'm having problems to what official ROM to use from the list.
The only one on the list is Optus, but my phone is with virgin (on the optus network) should that be fine?
The rom is I9100XWLP8
Once again many thanks! I'll update you with the progress.
Yep. Flash the Optus rom given you're effectively using their network & see what happens.
MistahBungle said:
Yep. Flash the Optus rom given you're effectively using their network & see what happens.
Click to expand...
Click to collapse
Thanks mate, you're a champion!
No probs Post here again if you have any dramas.
MistahBungle said:
No probs Post here again if you have any dramas.
Click to expand...
Click to collapse
Just downloaded it (Hotfile takes forever) and flashed through odin.
Worked fine after a factory reset. However, Kies won't update my phone.
Network seems to running smooth, so we'll see how it goes. The more things I do, I guess the more things I can rule out.
EDIT:
I updated the phone, and I get the message "Unfortunately, Application installer has stopped". What am I supposed to do?
Factory reset
Sent from the little guy
gastonw said:
Factory reset
Sent from the little guy
Click to expand...
Click to collapse
That didn't work.
Anyhow, I managed to track down a 4.0.4 variant of the ROM I was using, and made sure the CSC, PDA and Baseband all matched up with what Kies wanted, and flashed it. I think the error occured I was trying to update a ROM with the wrong CSC and Baseband to one with the correct ones and Kies didn't like that.
Hi, sorry if this has been answered, but I can't find it.
I recently combined two broken i9300's (one with a bricked motherboard (gets into download mode, product name blank, think it's SDS), the other with a smashed screen) by transferring the motherboard from the smashed one to the other.
It seemed to work fine for a while, but after a week the phone lost signal, showing no service. Rebooting the phone fixed this, however this has now been happening more and more often, and now doesn't have any service even after booting.
Does anyone know what the problem could be, and how to fix it?
Thanks.
EDIT: I managed to restore service again by flashing the stock ROM through Odin (was running stock already), but it lost it again after a few hours.
pnz said:
Hi, sorry if this has been answered, but I can't find it.
I recently combined two broken i9300's (one with a bricked motherboard (gets into download mode, product name blank, think it's SDS), the other with a smashed screen) by transferring the motherboard from the smashed one to the other.
It seemed to work fine for a while, but after a week the phone lost signal, showing no service. Rebooting the phone fixed this, however this has now been happening more and more often, and now doesn't have any service even after booting.
Does anyone know what the problem could be, and how to fix it?
Thanks.
EDIT: I managed to restore service again by flashing the stock ROM through Odin (was running stock already), but it lost it again after a few hours.
Click to expand...
Click to collapse
Check IMEI and serial if corrupted. If it shows your correct IMEI and serial then it's fine. Otherwise you may have an EFS problem.
Report back please.
Benko111 said:
Check IMEI and serial if corrupted. If it shows your correct IMEI and serial then it's fine. Otherwise you may have an EFS problem.
Report back please.
Click to expand...
Click to collapse
IMEI and serial are both fine (non-zero and non-null anyway). IMEI matches the label from the smashed phone. However, it's connected at the moment (just re-flashed the stock ROM again). Will update again the next time it loses service.
EDIT: Just lost service again. Only took about 10 minutes after flashing. IMEI and serial are still fine. I also forgot to mention that the motherboard I'm using is from a New Zealand phone, whereas the casing/screen is from a French phone. Don't know if that makes a difference. I tried flashing a French stock ROM, but that gave me an unknown baseband and null IMEI. Flashing the NZ ROM again fixed that.
EDIT2: And another correction. IMEI and serial showed fine after losing service, but I then rebooted the phone. Still no service, baseband is now unknown, IMEI is null and the serial number is non-zero but different than it was. However, I'm sure if I reflashed the ROM again I'd have service for a few minutes, so it doesn't seem like the EFS is entirely corrupt. I'm scratching my head a bit at this one.
pnz said:
IMEI and serial are both fine (non-zero and non-null anyway). IMEI matches the label from the smashed phone. However, it's connected at the moment (just re-flashed the stock ROM again). Will update again the next time it loses service.
EDIT: Just lost service again. Only took about 10 minutes after flashing. IMEI and serial are still fine. I also forgot to mention that the motherboard I'm using is from a New Zealand phone, whereas the casing/screen is from a French phone. Don't know if that makes a difference. I tried flashing a French stock ROM, but that gave me an unknown baseband and null IMEI. Flashing the NZ ROM again fixed that.
Click to expand...
Click to collapse
Judging from your last two sentences you actally have got an EFS problem. Just to clarify: you get generic IMEI & serial with every other ROM you flashed besides the original NZ stock?
Otherwise it might just be the modem not fitting the ROM, try another (if possible original 3-part stock firmware), but make a Nandroid backup or save your EFS otherwise in case you need it later.
Benko111 said:
Judging from your last two sentences you actally have got an EFS problem. Just to clarify: you get generic IMEI & serial with every other ROM you flashed besides the original NZ stock?
Otherwise it might just be the modem not fitting the ROM, try another (if possible original 3-part stock firmware), but make a Nandroid backup or save your EFS otherwise in case you need it later.
Click to expand...
Click to collapse
Not generic IMEI but null IMEI. Not sure about generic serial, not sure how to tell the difference. And I'm now seeing the same on the NZ stock firmware after a reboot.
Is a Philz Touch EFS backup sufficient? Anything else I should backup as well?
Well, since EFS is broken already it should be sufficient. To be on the safe site you can additionally save the EFS folder with Root Explorer.
If you have a working EFS you would need to save it with an EFS saving tool like 'Samsung Tool' in this forum somewhere.
Then you got to go through the EFS threads for i9300 and hope to be able to fix this.
Benko111 said:
Well, since EFS is broken already it should be sufficient. To be on the safe site you can additionally save the EFS folder with Root Explorer.
If you have a working EFS you would need to save it with an EFS saving tool like 'Samsung Tool' in this forum somewhere.
Then you got to go through the EFS threads for i9300 and hope to be able to fix this.
Click to expand...
Click to collapse
I've already gone through all the EFS threads I could find. Haven't seen anyone with the same problem (sometimes it works, briefly, then it stops). Everyone else with the baseband unknown, IMEI null/null problem seems to have that all the time. Was hoping someone would be able to tell me what's different with mine.
pnz said:
I've already gone through all the EFS threads I could find. Haven't seen anyone with the same problem (sometimes it works, briefly, then it stops). Everyone else with the baseband unknown, IMEI null/null problem seems to have that all the time. Was hoping someone would be able to tell me what's different with mine.
Click to expand...
Click to collapse
How should anybody know from the distance? We can just give hints and point you into directions, now you've got to read & google and if you're
persistent enough you will solve your problem - as long as it's not hardware related.
Another great but a bit chaotic resource:
http://forum.gsmhosting.com/vbb/
Benko111 said:
How should anybody know from the distance? We can just give hints and point you into directions, now you've got to read & google and if you're
persistent enough you will solve your problem - as long as it's not hardware related.
Another great but a bit chaotic resource:
http://forum.gsmhosting.com/vbb/
Click to expand...
Click to collapse
Sorry, just meant that I thought somebody might have seen this exact problem before.
I think I've solved this. Used the repair NV data option (to fix broken baseband) in EFS Professional, and it seems to be working fine. Will see if it's still working after a few days though.
My best guess is that this was a file permissions error.
pnz said:
I think I've solved this. Used the repair NV data option (to fix broken baseband) in EFS Professional, and it seems to be working fine. Will see if it's still working after a few days though.
My best guess is that this was a file permissions error.
Click to expand...
Click to collapse
No, not fixed. Worked fine for a few days then the problem came back. Just tried a non-stock ROM (Omega) and same thing. Trying a CM-based ROM now (ParanoidAndroid), but not too hopeful.
Still don't understand why it works for hours/days, then suddenly stops. Rebooting it fixes it the first few times, then that stops working as well (and I get baseband unknown at this point). Flashing a new ROM always fixes it, for a few hours/days anyway.
Sounds like a hardware issue, possibly nand memory becoming corrupt hence why it works for a while on a fresh install.
Sent from my GT-I9300 using Tapatalk
boomboomer said:
Sounds like a hardware issue, possibly nand memory becoming corrupt hence why it works for a while on a fresh install.
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
Any workarounds you can suggest? Just had the problem happen again on cyanogenmod, so that didn't fix it.
Try reading the freezing thread in general forum, see if the memory test tool will compete after a full wipe and fresh install of a stock firmware.
Other than that only a new motherboard, as the emmc chip is damaged.
Hello all,
My partner bought a Galaxy S3 (GT-i1900) International (I live in the UK) off a friend .
We noticed that the network connection periodically failed. I noticed that the software was some of the earliest on this phone, and so i thought I'd better update it, as it was suggested that sometimes if the phone is running some of it's earliest software it can cause problems with the network connection, and as it works 95% of the time, surely it can't be the antenna? I went to software update and tried to update it there, it's then I realised the phone had been rooted, and even Kies would not update it. I came to the conclusion that perhaps my friend had tried to mess with the phone some how, and may have caused this network problem, or perhaps was trying to cure it? Who knows
I decided to flash the latest stock rom (i9300XXUGMK6_I9300OXAGMK6_I9300XXUGMK6_HOME.tar.md5) I found on Sammobile. Everything went well, the phone booted up perfectly, the only minor worry being that the first screen was in Polish, quickly remedied by changing the language to English UK. All seemed fine, until we tried to make a call. it was then we realised that there was no network connection whatsoever. I tried other sim cards with other networks - still no connection. It only shows the signal bars.
I read the forums for a couple of days and tried:
Going in Network Settings and searching for my network, 3, which it found amongst all others. it said 'Registered on Network' but then immediately flashed up '3 network not connected' or similar. fail.
Installing CWM recovery, then flashing the 2 modem zips (DDEMG2 & XXDME4) all went fine, but the phone still says 'disconnected' under Device settings Mobile network state
Using the Ariza patch. I tried this, but on the last step where it says 'just click patch' mine gets stuck on a downloading state, possibly as I'm using a stock rom I read some kernel has to be changed first? - Beyond me.
It was then I decided to scrutinize every difference between my working S3, exactly same phone on same network, and my partners.
The IMEI number was correct, something I see people have problems with. The signal strength reading are the same, suggesting the antenna at least is fine.
The serial number - Now this is the ONLY thing I can see that seems to have been changed, from the correct format, to one starting with 4df1 ...... Is this the problem, that has made the phone not register with network? In the UK phones are not locked into a specific phone number /contract and so I don't see how the network would decline a differing serial number?
Anyway that's where I'm at a phone that has no network connection, with a differing serial number.
Any help would be GREATLY appreciated.
extra[/ATTACH]
Screenshots of the device status in case that helps . SCREENSHOTS REMOVED DUE TO PRIVATE INFO
I've noticed after Googling the baseband version, it says 'New modem DDEMG2 (16/07/13) India,Sri Lanka,Bangladesh'
I live in the UK and have a network free unlocked unbranded International S3!
Surely the steps I followed to flash the modems as stated above are incorrect?!
Do I need to flash the UK one?
Anyone know which one for 4.3?
How do I do it and where would I find it?
Any help greatly appreciated!
ricrea said:
extra[/ATTACH]
Screenshots of the device status in case that helps .
I've noticed after Googling the baseband version, it says 'New modem DDEMG2 (16/07/13) India,Sri Lanka,Bangladesh'
I live in the UK and have a network free unlocked unbranded International S3!
Surely the steps I followed to flash the modems as stated above are incorrect?!
Do I need to flash the UK one?
Anyone know which one for 4.3?
How do I do it and where would I find it?
Any help greatly appreciated!
Click to expand...
Click to collapse
Go to Samsungmobile and download 4.3 BTU ( it's for Uk,simfree phones.) Flash via Odin,maybe that will help
Sent from my GT-I9300 using XDA Free mobile app
thanks so much for the response!
Im sure that romwas the btu one? Does it not seem correct? I will check again.
ricrea said:
thanks so much for the response!
Im sure that romwas the btu one? Does it not seem correct? I will check again.
Click to expand...
Click to collapse
I don't think so since setup started in Polish
Sent from my GT-I9300 using XDA Free mobile app
Attached is the screenshot the latest 4.3 btu. It wants me to download. Ive just looked on the phone, and it is the same
name exactly, and this is where I got it from. What could have gone wrong?
many thanks
ricrea said:
Attached is the screenshot the latest 4.3 btu. It wants me to download. Ive just looked on the phone, and it is the same
name exactly, and this is where I got it from. What could have gone wrong?
many thanks
Click to expand...
Click to collapse
You mean Pda,Csc and Modem are the same? Or md5 is the same?
Sent from my GT-I9300 using XDA Free mobile app
YOU ARE CORRRECT. Im downloading and the file name is different. No idea what i did.
Thanks for your help.
ricrea said:
YOU ARE CORRRECT. Im downloading and the file name is different. No idea what i did.
Thanks for your help.
Click to expand...
Click to collapse
Report back if you get your network back:thumbup:
Sent from my GT-I9300 using XDA Free mobile app
ricrea said:
YOU ARE CORRRECT. Im downloading and the file name is different. No idea what i did.
Thanks for your help.
Click to expand...
Click to collapse
Hi couple of things first you have posted screen shots with your mobile no and Imei no on I would delete them
I am pretty sure flashing another rom won't fix your issue you can easily use roms from a different region and still have full network connection but you can give it a try as suggested above.
First thing first because you have upgraded your phone your efs as changed from efs v1 to efs v2 (which you probably already know) flashing the (DDEMG2 & XXDME4) modems would not work because you need a modem later than mg4 for 4.3 roms.
What you need to try is flash a patched mk6 modem and kernel from here >> https://drive.google.com/folderview...sharing&tid=0B6MIUd7HJudAbU5YaGkzOUowMG8#list << flash then reboot if you get stuck in a bootloop factory reset and wipe cache in recovery.You could also try this >> http://forum.xda-developers.com/gal...ii-network-problem-update-sn-t1918601/page199 << look at post 1984 this is basically the same thing with a rom included and as had some success.
If the patched modems do not work and you don't have a efs backup then I would suggest you need to send for repair.
tallman43 said:
Hi couple of things first you have posted screen shots with your mobile no and Imei no on I would delete them
I am pretty sure flashing another rom won't fix your issue you can easily use roms from a different region and still have full network connection but you can give it a try as suggested above.
First thing first because you have upgraded your phone your efs as changed from efs v1 to efs v2 (which you probably already know) flashing the (DDEMG2 & XXDME4) modems would not work because you need a modem later than mg4 for 4.3 roms.
What you need to try is flash a patched mk6 modem and kernel from here >> https://drive.google.com/folderview...sharing&tid=0B6MIUd7HJudAbU5YaGkzOUowMG8#list << flash then reboot if you get stuck in a bootloop factory reset and wipe cache in recovery.You could also try this >> http://forum.xda-developers.com/gal...ii-network-problem-update-sn-t1918601/page199 << look at post 1984 this is basically the same thing with a rom included and as had some success.
If the patched modems do not work and you don't have a efs backup then I would suggest you need to send for repair.
Click to expand...
Click to collapse
Thanks. I have absolutely no idea what EFS is or how to back up. I would never have usually played with a phone like this it's just my partner was getting fed up of the connection disapearing every now and again, forcing her to reset. I have about 12 hours worth of knowledge on root access, flashing and modifying phones. I am worried I'm going to completely brick the phone. Is there anyway I can make a back of the phone as it is so that if I mess things up I can some how reset it, as at the moment I have Nothing as such. I am going to read up on EFS, I suspect due to the fact the phone was already rooted when I bought it, yet still stuck on the original software and and not updated in anyway, with a pre-exsisting network connection issue, that the phone was already un fixable. I hope not.
I will try all the steps suggested and post results.
Thanks a lot people
ps i hardly have any experience of using forums so sorry if i'm making a mess of this
ricrea said:
Thanks. I have absolutely no idea what EFS is or how to back up. I would never have usually played with a phone like this it's just my partner was getting fed up of the connection disapearing every now and again, forcing her to reset. I have about 12 hours worth of knowledge on root access, flashing and modifying phones. I am worried I'm going to completely brick the phone. Is there anyway I can make a back of the phone as it is so that if I mess things up I can some how reset it, as at the moment I have Nothing as such. I am going to read up on EFS, I suspect due to the fact the phone was already rooted when I bought it, yet still stuck on the original software and and not updated in anyway, with a pre-exsisting network connection issue, that the phone was already un fixable. I hope not.
I will try all the steps suggested and post results.
Thanks a lot people
ps i hardly have any experience of using forums so sorry if i'm making a mess of this
Click to expand...
Click to collapse
Don't worry just take your time and read all the guides if you install a custom recovery you can do a nandroid backup which is basically a full backup of everything on your phone and will restore your phone to how it was before (if you do it right) I recommend using PhilZ recovery and flash it with Odin.
tallman43 said:
Don't worry just take your time and read all the guides if you install a custom recovery you can do a nandroid backup which is basically a full backup of everything on your phone and will restore your phone to how it was before (if you do it right) I recommend using PhilZ recovery and flash it with Odin.
Click to expand...
Click to collapse
I have cwm recovery will this suffice?
I'm using Samsungtool as we speak to back up the EFS folder.
ricrea said:
I have cwm recovery will this suffice?
I'm using Samsungtool as we speak to back up the EFS folder.
Click to expand...
Click to collapse
Yep that will do fine although you are backing up a partially corrupt efs that's the reason you are not getting a signal because the efs v2 can't read the modern correctly that's why you may need a patched modem & kernel to help read it.But back it up anyway in case the efs gets any worse and gets totally corrupt.
tallman43 said:
Yep that will do fine although you are backing up a partially corrupt efs that's the reason you are not getting a signal because the efs v2 can't read the modern correctly that's why you may need a patched modem & kernel to help read it.But back it up anyway in case the efs gets any worse and gets totally corrupt.
Click to expand...
Click to collapse
That was my thinking, the IMEI isn't corrupt yet so I thought best to back up what I have. Ive also backed up using CWM.
Im now trying to flash the proper version of 4.3 for my unlocked uK S3, so im at least using the correct os.
Im flashin zip from cwm, but when i select it on my sd card, it says the following:
Finding update package...
Opening update package...
Installing update...
Installation aborted.
Any ideas why it won't install? Iv'e been Googling it
for 2 hours.
cheers
update - I spent ten hours downloading the proper rom 4.3 btu uk unlocked one, finally flashed it using mobile odin.....
started in Polish again - with no network. I think that this is standard.
Next, I am going to try to flash the patched modem.
tallman43 - do you think my strange serial number needs to be corrected? Is this possible or necessary?
Many thanks - one very tired migraine creating finger-nail biter.
Update:
I finally got the phone to work by following the instructions on the page below;
http://forum.xda-developers.com/galaxy-s3/help/guide-fixing-gt-i9300-network-4-3-stock-t2609635
The patched kernel didn't work on it's own, but the kernel I installed from this thread, along with the other two files, seemed to work, and though the phone is now registered using a much better Android 4.3, it still disconnects every now and again forcing a restart. I really wish I could work out why it does this, I'm starting to believe it may be a hardware issue now.
Is there a program that I could use to test the part of the phone that malfunctions and loses signal completely, to try and work out what is happening when the phone suddenly loses all signal and shows only a circle with a line on it (no sign)
Many thanks to all the people who helped me with this I really appreciate it.
I want to close this thread now as what I require now is off topic from the original post so many thanks for your help people.
I have had stability issues on marshmallow. I flashed the 35B bootstack and upgraded to the Azadi marshmallow variant. It was working fine, but there had been more updates to the rom, so I flashed those as well (without flashing 35B again). I was getting occasional system reboots, so I switched to the stock 47A firmware (debloated using joshua70448 zip generator). I am still having the same issue - the system randomly reboots, sometimes twice in a row. Also sometimes when I power down, the phone will not power up again until I remove the battery.
I really cannot relate this to any particular situation - it seems to happen at completely random times.
Any help is greatly appreciated.
Did you try what I suggested at the bottom of the reply I sent in the other thread?
http://forum.xda-developers.com/showthread.php?p=66842422
roirraW "edor" ehT said:
Did you try what I suggested at the bottom of the reply I sent in the other thread?
http://forum.xda-developers.com/showthread.php?p=66842422
Click to expand...
Click to collapse
No. Somehow I lost that last sentence in your sig.
So wipe, flash TOT, flash 35B, flash ROM, ???, profit?
B00M! said:
No. Somehow I lost that last sentence in your sig.
So wipe, flash TOT, flash 35B, flash ROM, ???, profit?
Click to expand...
Click to collapse
Flash the 10B TOT, root using the Stump app, use TWRP Manager from the Play Store to install TWRP, wipe Cache, Dalvik/ART and Data, flash the 35B bootstack if you're going to flash a 35B or higher ROM, then flash the ROM.
If you're going to flash a ROM that had a lower version of Android, flash the corresponding Bootstack.
Ok. I will let you know how it turns out.
Is this going to repartition my device?
B00M! said:
Ok. I will let you know how it turns out.
Is this going to repartition my device?
Click to expand...
Click to collapse
I'm not sure what you mean by repartition. It will wipe everything including internal storage. It won't wipe external MicroSD. You'll be back on completely stock 10B, which is easiest to root and put TWRP on.
I thought I read somewhere that one of the updates changed some of the partition sizes, but I guess if that were true, you would know
I was mostly concerned about whether or not my internal storage would be wiped in the process.
Out of curiosity, why do you recommend TOT instead of KDZ method?
B00M! said:
I thought I read somewhere that one of the updates changed some of the partition sizes, but I guess if that were true, you would know
Click to expand...
Click to collapse
Maybe they did, I wouldn't necessarily have noticed.
Out of curiosity, why do you recommend TOT instead of KDZ method?
Click to expand...
Click to collapse
That's answered in my original reply to you in the other thread. Again, just the part at the bottom of my reply.
For anyone who follows this thread:
roirraW "edor" ehT said:
Doubtful, if it's the way you describe it. The only reason I tell people this is because some people ask for help determining when they can get away with not flashing the bootstack again.
It's far simpler to just flash whichever the appropriate bootstack is every time you flash a ROM or restore a TWRP backup. There's just no reason to avoid flashing the right one every time.
If you're experienced enough that you know you don't have to flash it again, then don't. If you're mistaken, you could end up with a temporary brick depending on the exact situation, but it's still not caused by the bootstack.
Also, the wrong bootstack doesn't cause stability issues or reboots. It can cause no signal, not being able to use Advanced/HD Calling and not being able to encrypt your SD card.
....
I recommend flashing the 10B TOT. TOTs flash more partitions than KDZs, as @xdabbeb taught me and I verified. I had a weird problem months ago that wouldn't go away no matter what ROM or KDZ I flashed until I flashed the TOT.
Click to expand...
Click to collapse
This unfortunately did not work. I think I have traced the initial problem to a particular situation. The first crash seems to always happen when I launch navigation. The phone will suddenly turn off and then reboot twice. After this inciting event, the system seems to become unstable and will reboot at random times when I am using it. Is there a way to track what is causing the crash using logcat or something? Any other ideas? I might just have to go back to LP, as I don't think I was having a problem running it.
B00M! said:
This unfortunately did not work. I think I have traced the initial problem to a particular situation. The first crash seems to always happen when I launch navigation. The phone will suddenly turn off and then reboot twice. After this inciting event, the system seems to become unstable and will reboot at random times when I am using it. Is there a way to track what is causing the crash using logcat or something? Any other ideas? I might just have to go back to LP, as I don't think I was having a problem running it.
Click to expand...
Click to collapse
What exactly do you mean by "launch navigation"? If you're on Azadi right now, I haven't used it so I can't particularly advise, although I'm curious if you'd have the problem on a less modified stock ROM, and also curious if you would be able to replicate the problem if you were completely stock unrooted.
Sounds very strange. I haven't had this issue among the ROMs I've used. Currently @xdabbeb 's stock 47A firmware (fully debloated). Previously his VS985 v2.0 (35B) ROM, and previous to that, several versions of JasmineROM up through 9.1 (35B).
I really have no experience with logcats so I can't advise you there.
It's possibly your battery is going bad, as that's been known to cause all sorts of weird issues.
By launch navigation, I mean start a new navigation in google maps. I get to the map just fine, searches just fine, but when I start the navigation, the phone goes black and reboots.
I have had this issue on Azadi as well as the stock 47A version (with debloating as I described in the other thread) both before and after the TOT install. I saved a stock rooted 47A TWRP version during this process, so I could unroot it and see if the problem persists. There does appear to be some relation to the battery, as it will crash and reboot and lose about 10% of the battery in the process. After I plug it in, the battery returns to its "precrash" level. Drain does not seem to be greatly different than before I transitioned to MM.
Again, I really appreciate your help and ideas.
B00M! said:
By launch navigation, I mean start a new navigation in google maps. I get to the map just fine, searches just fine, but when I start the navigation, the phone goes black and reboots.
I have had this issue on Azadi as well as the stock 47A version (with debloating as I described in the other thread) both before and after the TOT install. I saved a stock rooted 47A TWRP version during this process, so I could unroot it and see if the problem persists. There does appear to be some relation to the battery, as it will crash and reboot and lose about 10% of the battery in the process. After I plug it in, the battery returns to its "precrash" level. Drain does not seem to be greatly different than before I transitioned to MM.
Again, I really appreciate your help and ideas.
Click to expand...
Click to collapse
Unrooting a backed up version of 47A wouldn't be the same as actually running the full stock unrooted 47A, not unless you went to a tremendous amount of effort (meaning it's far simpler to flash a KDZ).
I use Maps all the time on stock fully debloated 47A and have done so recently without issue. I'm only saying this because I don't think the ROM is the issue.
I would definitely proceed further with the battery route. Unless there's some tiny piece of detail that I don't know, it's either that or just general hardware failure, but I doubt that.
Just for the heck of it, eject your MicroSD card and leave it out, reboot the phone and do what you can do to replicate the issue while the card's ejected. I hope you eventually solve this, sooner rather than later and hopefully not too much more paintfully.
Alright. Yeah. It has been a PITA trying to get back to a stable setup. I too do not think it is the ROM based on what has happend so far.
The only bit that I haven't mentioned is that the commands are set up through tasker (switches on Bluetooth, launches the apps and starts the navigation). I may try to run the stock, debloated, rooted, 47A rom without tasker next to see if the problem still occurs. This too does not seem like the issue, because sometimes tasker launches everything and it runs well without any crashes. I don't see that anyone is reporting a similar issue in the tasker Google group.
I will keep this thread updated to any progress.
After extensive testing, I am convinced this is a battery issue. New battery is on the way.
No issues after replacing the battery. Life is good again