Hi guys,
I've ordered a new, unlocked i9300 from eBay, and I had some adventures with it:
I've unpacked it, inserted my SIM, powered it on, and found out that the phone always thinks that I'm roaming. Instead of trying to understand what's going on, I though: "I'll just install CyanogenMod and everything will be good".
I've installed CyanogenMod 10.2 (latest stable build), only to find out that my SIM is not being detected at all. It says that Baseband is unknown, IMEI and related are unknown as well.
After trying lots of stuff, I gave up and decided to return to stock ROM (4.3). While trying to do that, I bricked my phone, and the only thing I could do is enter Odin mode.
After reading dozens of tutorials and trying lots of stuff, I ended up flushing GT-I9300_mx_20120329.pit, and that unbricked my phone.
I successfully flashed Android 4.3. This version detected my SIM, displayed the Baseband/IMEI, but it didn't connect to the cellular network. I could scan for available networks, but when I chose my network manually, it said "Selected network not available ".
I tried to flush alternative modems, but all it did is making things worse. Usually it made the phone behave like with CyanogenMod, i.e. Baseband/IMEI are unknown.
Again, after trying lots of stuff, I tried to flush Android 4.1.2. That made no change until I've stumbled on this thread. Flushing Patched_Modem_I9300XXEMG4.zip made my networking work again, and restored it to behave exactly like it did initially. Again, the phone thinks that I'm roaming all the time, but at least it works.
So currently, I have two issues:
My phone always thinks I'm roaming. Is there a fix for it?
And more important: currently, I cannot install anything other than Android 4.1.2!
Could you please shed some light on the situation? What happens with my phone? Why does it think I'm roaming? Why does the SIM work only with Patched_Modem_I9300XXEMG4? How can I make other ROMs (e.g. CyanogenMod) work?
Thanks, any help is much appreciated!
9999 :) said:
Hi guys,
I've ordered a new, unlocked i9300 from eBay, and I had some adventures with it:
I've unpacked it, inserted my SIM, powered it on, and found out that the phone always thinks that I'm roaming. Instead of trying to understand what's going on, I though: "I'll just install CyanogenMod and everything will be good".
I've installed CyanogenMod 10.2 (latest stable build), only to find out that my SIM is not being detected at all. It says that Baseband is unknown, IMEI and related are unknown as well.
After trying lots of stuff, I gave up and decided to return to stock ROM (4.3). While trying to do that, I bricked my phone, and the only thing I could do is enter Odin mode.
After reading dozens of tutorials and trying lots of stuff, I ended up flushing GT-I9300_mx_20120329.pit, and that unbricked my phone.
I successfully flashed Android 4.3. This version detected my SIM, displayed the Baseband/IMEI, but it didn't connect to the cellular network. I could scan for available networks, but when I chose my network manually, it said "Selected network not available ".
I tried to flush alternative modems, but all it did is making things worse. Usually it made the phone behave like with CyanogenMod, i.e. Baseband/IMEI are unknown.
Again, after trying lots of stuff, I tried to flush Android 4.1.2. That made no change until I've stumbled on this thread. Flushing Patched_Modem_I9300XXEMG4.zip made my networking work again, and restored it to behave exactly like it did initially. Again, the phone thinks that I'm roaming all the time, but at least it works.
So currently, I have two issues:
My phone always thinks I'm roaming. Is there a fix for it?
And more important: currently, I cannot install anything other than Android 4.1.2!
Could you please shed some light on the situation? What happens with my phone? Why does it think I'm roaming? Why does the SIM work only with Patched_Modem_I9300XXEMG4? How can I make other ROMs (e.g. CyanogenMod) work?
Thanks, any help is much appreciated!
Click to expand...
Click to collapse
When the phone gets upgraded from 4.1 to 4.3 your efs changes from efs v1 to efs v2 sometimes this upgrade does not go smoothly (as in your case) so then you need to always use a patched modem from version mg4 onwards (not a normal one) if you flash a rom which changes the baseband to anything less than 4.3 then it will not work.You need to keep on mg4 or later to keep signal and because your efs is not fully upgraded properly you need to always use a patched modem and preferably kernel as well.
I am not sure about the roaming issue but if you try patched modem and patched kernel together that might help.Take a look here for some patched modems and kernels and remember you always need to use them >> https://drive.google.com/folderview...sharing&tid=0B6MIUd7HJudAbU5YaGkzOUowMG8#list << You should also be able to use 4.3 roms as long as you use the patched files above ie baseband and kernel.
In general, It would be great if I could use CyanogenMod 10.2.
Should I proceed in the following order? Flush CM -> flush patched kernel -> flush patched modem.
Which of the patched versions should I choose?
Also, what do these versions change? What functionality was patched in these files? Can I read about it somewhere?
Thanks for the help.
9999 :) said:
In general, It would be great if I could use CyanogenMod 10.2.
Should I proceed in the following order? Flush CM -> flush patched kernel -> flush patched modem.
Which of the patched versions should I choose?
Also, what do these versions change? What functionality was patched in these files? Can I read about it somewhere?
Thanks for the help.
Click to expand...
Click to collapse
No the kernel will only work for 4.3 roms not CyanogenMod roms but the patched modems will work.You can try flashing CyanogenMod then the patched modem but CyanogenMod does not include a modem so whatever modem you where on when you flashed CyanogenMod you will keep.
tallman43 said:
No the kernel will only work for 4.3 roms not CyanogenMod roms but the patched modems will work.You can try flashing CyanogenMod then the patched modem but CyanogenMod does not include a modem so whatever modem you where on when you flashed CyanogenMod you will keep.
Click to expand...
Click to collapse
I tried installing CyanogenMod, then flushing some of the patched modems you've linked. Unfortunately, nothing changes - Baseband/IMEI are always unknown.
9999 :) said:
I tried installing CyanogenMod, then flushing some of the patched modems you've linked. Unfortunately, nothing changes - Baseband/IMEI are always unknown.
Click to expand...
Click to collapse
You mean flash not flush.
Also you should be careful to by things like this off ebay, There is a very high chance you brought the phone broken like this but did not notice straight away.
Don't hang around on 4.1.2 as you might get SDS.
Upgrade to 4.3 stock of higher using custom roms with a patched modem of mg4 or higher as stated by tallman43.
Read here for what you or the previous owner has done. Also on stock make sure your csc is correct.
http://forum.xda-developers.com/galaxy-s3/general/ref-imei-efs-stuff-i9300-including-t2393289
If you cannot get it to work you need to take it in for repair. Make sure it works on 4.3 before paying.
Related
I run CM 10.1 on my phone, which had original specs: PDA:KG3 / PHONE:KE7 / CSC:KG1 (VNZ). I've been running those CM nightlies since about November 2012 with few problems, updating to new nightlies every few weeks to a month. I'd never flashed new radios - just the CM rom.
Starting a couple of months ago, I began to see a problem where my phone would drop cell service (no bars + empty triangle in the cell signal indicator) and rebooting was the only way to bring the cell signal back. This happened every couple of days, so was bearable. I figured something in the nightlies had caused a weird problem and that the CM devs/community would find and fix this.
After flashing a nightly last week, my phone wouldn't hold cell signal for more than an hour - sometimes not even that. Reboots fixed this but never permanently. I started to read about radios, modems, and RILs. hawkerpaul's post here was a great help. I found that my phone had the original KE7 radio but had a RIL of I9100XXLS8(2) - I presume from the CM rom? I flashed some new radios and have now gone through a series of the (matched) modem + RIL files in hawkerpaul's post above. In most cases I see the following behaviour:
Phone successfully finds network (Vodafone NZ) on boot
Trying to manually select a mobile operator fails (error when searching for networks)
Unable to successfully call out! Dialling stalls, and I can't hang up - only fixed by a reboot
How do I fix this immediate problem of not being able to call/receive calls? Seems like maybe I'm using a radio that doesn't work with Vodafone NZ - but I haven't seen any posts on what DOES work well with that network. I have the modem file to flash the original KE7 back again, but what should I do about the RIL file then? Not sure I have found an RIL for KE7 yet in my travels. Any help would be appreciated - and thanks!
To help me figure out where I went wrong, do the CM builds include the RIL, or is that something that could only get updated somewhere else? I know the rom doesn't change the modem but I suspect that XXLS8(2) RIL had to come from CM.
1) Don't mess with RIL's (You'll make it 'worse').
2) Check stock roms released by your telco. Find out which modems were bundled with those stock roms. Try those modems. If they don't help, look for stock roms released by other carriers which sold the the I9100T world-wide (check Samfirmware). Try the modems bundled with these roms. If they don't help, try any & every modem you can get your hands on.
If you've already flashed RIL's, you may well have created a bigger problem for yourself. You might want to do a clean install of stock as well for good measure if that's the case. The reason I stopped using CM9 (and never bothered with CM10) was similar issues that seem to have gotten introduced with a particular nightly & never went away (a fix was tried which benefited a very few problems who were having RIL problems but created problems for even more people who previously had no problems).
MistahBungle said:
2) Check stock roms released by your telco. Find out which modems were bundled with those stock roms. Try those modems. If they don't help, look for stock roms released by other carriers which sold the the I9100T world-wide (check Samfirmware). Try the modems bundled with these roms. If they don't help, try any & every modem you can get your hands on.
...You might want to do a clean install of stock as well for good measure...
Click to expand...
Click to collapse
I'm just about at this point. If I reinstall stock, will that reset my modem as well?
Thanks for the help - looks like I did definitely make things worse.
You'll end up with whatever modem is bundled with the stock rom, so probably use the most recent released by your carrier, then you can try other modems released by your carrier as per my PP. The rationale with that is you'd hope your carrier has tested the modems they bundle with their stock roms so they work in most places/at most times with their network. Doing a clean install of stock should fix anything funky messing around with RIL's may have done as well.
If you get no joy from those, proceed as per my PP (You might get other suggestions from other people as well).
Thanks for the help. I was able to flash the latest stock rom, which included baseband I9100XXLS8. This worked fine for making and receiving calls. I lasted a couple of hours with that stock Samsung firmware before I started to get itchy for Android 4.2 again, so I've now rooted and am going to try CM10 again, but at least this time I know not to touch the modem - and I'm confident I can get back to stock again if I have any problems! Many thanks!
Glad you've got connectivity back You can flash modems as much as you want, I'd just be wary of messing with RIL's unless it's as an absolute last resort (I.E you have no connectivity & you've tried every single modem. Too many people try them when their connectivity is fine in the mistaken belief they're going to get 8Mbps instead of 7.8Mbps downloads, I.E it wasn't broke in the first place), even then a clean install of stock & choosing the right modem will often fix the problems.
You're welcome Any dramas post to this thread again & I'm sure someone will help.
Similar problems with modem or radio
MistahBungle said:
Glad you've got connectivity back You can flash modems as much as you want, I'd just be wary of messing with RIL's unless it's as an absolute last resort (I.E you have no connectivity & you've tried every single modem. Too many people try them when their connectivity is fine in the mistaken belief they're going to get 8Mbps instead of 7.8Mbps downloads, I.E it wasn't broke in the first place), even then a clean install of stock & choosing the right modem will often fix the problems.
You're welcome Any dramas post to this thread again & I'm sure someone will help.
Click to expand...
Click to collapse
Hi and thanks in advance. I have a galaxy i9100 which shows the following information: PDA: i9100xwlsd - Phone i9100xxls8 - Csc i9100vnzls9. I installed via odin Android version 4.1.2 which made the phone work really well except that it kept dropping network service and signal strength. I replaced the sim which did seem to help but did not fix the problem totally. I also notice that the GPS will not find any satellites and just keeps searching for as long as I would let it. I have read various threads and it appears that this may be a modem problem? I have found that Vodafone NZ has released a modem which is i9100xxls9? Should I flash the modem file only in Odin and do you really think this would fix the problem. How would I flash the modem file. Would I do this through odin? Any help gratefully received.
Yes, first step is definitely to flash the modem which was released by your carrier for your region. If you can find a file which is Odin flashable then yes, try it. However most of the files are for flashing via CWM. Are you rooted? If not they won't work for you, in which case you'll have to search around for an Odin flashable version of LS9.
Just to check, you do have an i9100? Not an i9100t etc? Some variants require different modems.
Sent from a galaxy far, far away
Thanks again
Hopper8 said:
Yes, first step is definitely to flash the modem which was released by your carrier for your region. If you can find a file which is Odin flashable then yes, try it. However most of the files are for flashing via CWM. Are you rooted? If not they won't work for you, in which case you'll have to search around for an Odin flashable version of LS9.
Just to check, you do have an i9100? Not an i9100t etc? Some variants require different modems.
Sent from a galaxy far, far away
Click to expand...
Click to collapse
Thanks for the response. How do I know if a file is odin flashable? How do you flash via cwm (whatever that is). You can see I am a little bit or a lot of a novice on this. The unfortunate thing is I enjoy it. I think the phone is rooted and it says the phone is: Model GT- i9100. The phone was purchased in UAE and I have flashed the android 4.1.2 which was a vodafone NZ system. Everything works fine except the GPS and the phone signal drops out all the time showing no service when there is service? Thanks again for your help on this. I have just found that the phone may not be rooted? I tried to install root manager but it indicated phone was not rooted?
Ok so no offence, you need to do a lot of reading for yourself. Reading is the key to successful (ie without bricking) modification of your phone.
For a start, if you've flashed stock then of course you will not have root. You don't need to have root to flash a modem. Have a look here:
http://forum.xda-developers.com/showthread.php?t=1656005
I'm not saying to flash that modem file. But that's how you do it, now you just need to find your file and flash it.
Sent from a galaxy far, far away
This might help someone having these no service/ no sim card no GPS fix issues with the galaxy SGSIII i9300, that might have to do with efs folder change and IMEI corruption.
Okay so i solved these no service issues and ill share my experience so maybe someone will find it helpful.
So the issue has to do with the famous efs folder conundrum, though tbh im not a developer so i cant say exactly what was the issue or even be a 100% sure it was the efs folder.
So I got me a used malfunctioning i9300 which i then repaired at a lab and proceeded to install a new TW based ROM, my first mistake was not backing up efs folder and creating a nandroid, but i havnt realized that yet. After flashing, I noticed that i have no GPS, but i didnt know if the GPS was working with original firmware because i neglected to check that or back it up, so i decided to put a pin in it for the time being and went on to check out some ROMs.
At first, I flashed couple of JB tw based roms, all was well (except for the gps), then i started to check out some KK roms, those didnt play well with my device, I got no service in every single rom i tried, You name it ive tried it, none fixed the service issue. Moreover i also tried a few JB AOSP based ROMs, among them the 4.3 JB PAC-man ROM, those had the same no service/no sim issues. Meanwhile whenever i un-root and flash with odin back to stock or restore a nandroid i made while on 4.3 foxhound ROM (with service working and a supposedly good copy of the efs folder) service is restored. I would also mention that I had more backups of the efs from the working “foxhound” i made with different tools and when i restored these folders when on a ROM with no service it didnt fix the issue.
Here are the solutions ive encountered and tried that didnt work:
-restoring efs with efs pro, samsung tool, efs backup -restore cmd tool.
-flashing latest firmware and flashing back to KK
-flashing all kinds of modems (those pre efs folder change (XXEMG4) and those after)
-flashing latest TWRP/CWM recovery
-flashing kernels
-trying to edit “nv_data.bin” with hex editor
-some more ways in trying to manipulate the efs folder.
-using samsung service codes on stock, which i found regarding this issue, except from the *#06# code, for imei, pretty much none worked for me.
Its important to mention that when on stock firmware or a JB TW based ROM i would see my baseband version in settings and when I tried the *#06# code for checking my imei it gave me a serial number with many digits that I assumed was indeed my correct IMEI number, and when i was on KK ROMs or non TW JB ROMs i would get the same popup with no numbers and in settings i would see “unknown baseband” .
To add to that, whenever i rooted and installed a KK ROM or a JB non TW ROM and tried to restore efs with efs professional i would get a message the device is not perm rooted (but thats neither here nor there).
This research took me about 5-6 days and the end of which i was ready to give up on having a KK rom or a non TW rom for that matter, NOTHING seemed to fix the problem. I just had some fight in me for one more hopeless attempt. I read somewhere that a flashing of cm 10.1 and then going to settings -> more and there change some network stuff from this to that would help -
(Originally Posted by Goose306 on s3forums.com)
"flash back to another AOSP 4.2 ROM (CM10.1, Liquid, etc.)
Got to Network settings. You need to change Roaming to automatic and CDMA settings to RUIM/SIM (I *think* that is the name of it, I'm actually on TW temporarily as I'm troubleshooting some SDcard issues of my own)
Reboot and you should be back in business. Touchwiz doesn't have a way of changing of those settings which is why ODIN/stock doesn't fix it"
I said what the heck thats simple enough. I flashed CM 10.1.3 for i9300 and went into the settings but the options i read about werent the same as the settings i saw in my case,
so i did move one settings around in the settings-> more section, cant remember what it was and im on a different ROM by now,
it was nothing i knew about anyway (but you should give it a go and have a look, there are few options to choose from so you can eliminate your way to what makes sense).
I then went on to recovery to flash carbon rom 4.4 and to my enormous surprise i had service and connection and to my astonishment i also got back the GPS as a bonus ! yay ! I bet you forgot about that too by now…
This ends on a weird note though, though everything is at working order now and the IMEI number i get is the same as the one i get when on stock rom,
it does not match the number on the back of the phone under the battery. well mehh.. as long is its working.
Hope this helps someone.
You didnt mention that exact step. Changing "something from this to that" doesn't really count as being helpful.
Thanks for the post anyways.
~ RazorMC
RazorMC said:
You didnt mention that exact step. Changing "something from this to that" doesn't really count as being helpful.
Thanks for the post anyways.
~ RazorMC
Click to expand...
Click to collapse
Youre right, i couldnt find the thread that had the suggestion to install the 10.1 cm but my point was it didnt even apply to my situation because the options in "Setting -> more" werent compatible with what was suggested in the thread so i had to improvise and I just changed some setting i cant remember in "Settings -> More" but I realise that it would be more helpfull to say what i changed there exactly, but im not on cm 10.1 anymore and cant see what in there now.. the good news is that there werent many options to change there.
But i did went out and looked for the original comment that made me try this an it says -
(Originally Posted by Goose306 on s3forums.com)
"flash back to another AOSP 4.2 ROM (CM10.1, Liquid, etc.)
Got to Network settings. You need to change Roaming to automatic and CDMA settings to RUIM/SIM (I *think* that is the name of it, I'm actually on TW temporarily as I'm troubleshooting some SDcard issues of my own)
Reboot and you should be back in business. Touchwiz doesn't have a way of changing of those settings which is why ODIN/stock doesn't fix it"
so in my case i didnt see these exact same options so i changed what seemed to me the most related to the issue at hand.
I dont think i had to touch the roaming, again i dont have CM 10.1 installed so i dont recall exactly what were my options.
is it a solution mostly for Qualcomm chipset based I9300 ? someone can say ? European providers use different frequencies I guess hence different chipsets and parameters.
Olek94 said:
is it a solution mostly for Qualcomm chipset based I9300 ? someone can say ? European providers use different frequencies I guess hence different chipsets and parameters.
Click to expand...
Click to collapse
mine is the international version but as i mentioned it didnt work like described but the end result was the same. I f you have the LTE version Im not sure which option youre going to get in CM 10.1 settings -> more , but if youre having trouble with service and GPS and stuff like that i do suggest you try flashing CM 10.1 (compatible with LTE - not sure how it goes with CM and LTE compatibility) and check if you got the same options to make the changes to, if not, try and improvise based on what makes even a little sense, thats what i did.
It might be that the flashing of CM 10.1 itself is what fixes the problem, so if you change nothing it might help still, anyway this is pretty simple and quick to do so better start here than starting with other messier solutions.
help
hi i was on stock 4.1.2 then i rooted flashed twrp recovery using toolkit and flashed revolutionary 5 4.3 straight away i didn't backup efs i know it was dump thing to do but i was new to galaxy s3 flashing so basically i f***k up. then i flashed official 4.3 firmware using odin.now i have a network reception but can't make or attend calls.i was thinking to go back to 4.1.2 in hope of getting things to work. please help n reply asap!! thanks
5668892 1021
jabirrockzzz said:
hi i was on stock 4.1.2 then i rooted flashed twrp recovery using toolkit and flashed revolutionary 5 4.3 straight away i didn't backup efs i know it was dump thing to do but i was new to galaxy s3 flashing so basically i f***k up. then i flashed official 4.3 firmware using odin.now i have a network reception but can't make or attend calls.i was thinking to go back to 4.1.2 in hope of getting things to work. please help n reply asap!! thanks
Click to expand...
Click to collapse
I believe I shared every bit of helpful information i can share with you about this issue and my process of handling it in the main message of the thread, Read the entire thing and the comments followed, then follow my suggestion, if you wish to do so.
samuelaviv said:
mine is the international version but as i mentioned it didnt work like described but the end result was the same. I f you have the LTE version Im not sure which option youre going to get in CM 10.1 settings -> more , but if youre having trouble with service and GPS and stuff like that i do suggest you try flashing CM 10.1 (compatible with LTE - not sure how it goes with CM and LTE compatibility) and check if you got the same options to make the changes to, if not, try and improvise based on what makes even a little sense, thats what i did.
It might be that the flashing of CM 10.1 itself is what fixes the problem, so if you change nothing it might help still, anyway this is pretty simple and quick to do so better start here than starting with other messier solutions.
Click to expand...
Click to collapse
Thank you, I was suspecting that you have a similar version than me. Well, in desperate cases anything can be tested (But some have told me not to mess with US versions as there is a risk of burning something )
Anyway the last version I could not flash , the CM 10.1 it was ejected with a file error soon despite 3 downlowd.
I will try with another more compatible version with Cyanogen.
Have a nice day
samuelaviv said:
This might help someone having these no service/ no sim card no gps fix issues with the galaxy s3 i9300, that might have to do with efs folder change and IMEI corruption.
Okay so i solved these no service issues and ill share my experience so maybe someone will find it helpful.
So the issue has to do with the famous efs folder conundrum, though tbh im not a developer so i cant say exactly what was the issue or even be a 100% sure it was the efs folder.
So I got me a used malfunctioning i9300 which i then repaired at a lab and proceeded to install a new TW based rom, my first mistake was not backing up efs folder and creating a nandroid, but i havnt realized that yet. After flashing, I noticed that i have no gps, but i didnt know if the gps was working with original firmware because i neglected to check that or back it up, so i decided to put a pin in it for the time being and went on to check out some roms.
At first, I flashed couple of JB tw based roms, all was well (except for the gps), then i started to check out some KK roms, those didnt play well with my device, I got no service in every single rom i tried, You name it ive tried it, none fixed the service issue. Moreover i also tried a few JB AOSP based roms, among them the 4.3 jb pac-man rom, those had the same no service/no sim issues. Meanwhile whenever i un-root and flash with odin back to stock or restore a nandroid i made while on 4.3 foxhound rom (with service working and a supposedly good copy of the efs folder) service is restored. I would also mention that I had more backups of the efs from the working “foxhound” i made with different tools and when i restored these folders when on a rom with no service it didnt fix the issue.
Here are the solutions ive encountered and tried that didnt work:
-restoring efs with efs pro, samsung tool, efs backup -restore cmd tool.
-flashing latest firmware and flashing back to kk
-flashing all kinds of modems (those pre efs folder change (xxemg4) and those after)
-flashing latest twrp/cwm recovery
-flashing kernels
-trying to edit “nv_data.bin” with hex editor
-some more ways in trying to manipulate the efs folder.
-using samsung service codes on stock, which i found regarding this issue, except from the *#06# code, for imei, pretty much none worked for me.
Its important to mention that when on stock firmware or a JB TW based rom i would see my baseband version in settings and when I tried the *#06# code for checking my imei it gave me a serial number with many digits that I assumed was indeed my correct IMEI number, and when i was on kk roms or non tw JB roms i would get the same popup with no numbers and in settings i would see “unknown baseband” .
To add to that, whenever i rooted and installed a kk rom or a jb non tw rom and tried to restore efs with efs professional i would get a message the device is not perm rooted (but thats neither here nor there).
This research took me about 5-6 days and the end of which i was ready to give up on having a KK rom or a non TW rom for that matter, NOTHING seemed to fix the problem. I just had some fight in me for one more hopeless attempt. I read somewhere that a flashing of cm 10.1 and then going to settings -> more and there change some network stuff from this to that would help -
(Originally Posted by Goose306 on s3forums.com)
"flash back to another AOSP 4.2 ROM (CM10.1, Liquid, etc.)
Got to Network settings. You need to change Roaming to automatic and CDMA settings to RUIM/SIM (I *think* that is the name of it, I'm actually on TW temporarily as I'm troubleshooting some SDcard issues of my own)
Reboot and you should be back in business. Touchwiz doesn't have a way of changing of those settings which is why ODIN/stock doesn't fix it"
I said what the heck thats simple enough. I flashed CM 10.1.3 for i9300 and went into the settings but the options i read about werent the same so i did move one settings around in the more section, cant remember what it was but it was nothing i knew about anyway, then went on to recovery to flash carbon rom 4.4 and to my enormous surprise i had service and connection and to my astonishment i also got back the GPS as a bonus ! yay ! I bet you forgot about that too by now…
This ends on a weird note though, though everything is at working order now and the IMEI number i get is the same as the one i get when on stock rom it does not match the number on the back of the phone under the battary.
Hope this helps someone.
Click to expand...
Click to collapse
:crying: :crying: :crying: :crying: :crying: Dude!!!!! I understand!!!!
I had a similar experience only I also tried flashing CM 10.1 and it did not work. Although I have another imei, I have all my services running on the Stock 4.3. Now the only problem is that if I change to any other rom, does not connect to the wifi network.
I found something like this: http://forum.xda-developers.com/showthread.php?t=839367&page=4
But neither worked. Yesterday I tried to repartition the phone and almost killed. I spent two weeks looking for a solution, and tried them all, but did not work, I think I will draw on the last and the only thing I think work ... The box.
The octopus box (or similar).
KK roms are beautiful ... but no matter what, I have no wifi in another rom than the stock 4.3 lol.
Thank you for your contribution! as you say: I hope you serve someone else.
VIOShero said:
:crying: :crying: :crying: :crying: :crying: Dude!!!!! I understand!!!!
I had a similar experience only I also tried flashing CM 10.1 and it did not work. Although I have another imei, I have all my services running on the Stock 4.3. Now the only problem is that if I change to any other rom, does not connect to the wifi network.
I found something like this: http://forum.xda-developers.com/showthread.php?t=839367&page=4
But neither worked. Yesterday I tried to repartition the phone and almost killed. I spent two weeks looking for a solution, and tried them all, but did not work, I think I will draw on the last and the only thing I think work ... The box.
The octopus box (or similar).
KK roms are beautiful ... but no matter what, I have no wifi in another rom than the stock 4.3 lol.
Thank you for your contribution! as you say: I hope you serve someone else.
Click to expand...
Click to collapse
yeah thats some BS those signal and issues on the i9300.. they really did a number on that one.
sorry my thing didnt help, i too tried everything and got nothing.
Maybe try flashing CM 10.1.3 and changing those options in settings-> more, Might be that just flashing CM 10.1 wont do it, I did change something ther but cant remember what it was, i wrote in my post what someone else had ther in the options but i had different ones but I still changed one option there ( what i thought might be connected to the issue ).
anyway dude i feel you its crying shame whole thing, and so many are posting about these issues all the time, im kinda hating on samsung cause they always seem to mess up like that.
Hope you solve this somehow..
Hello everyone,
I read countless cases in communities on this subject and I have tried almost everything, I am quite at a loss,
My case is like this:
I used SLIMBEAM version 4.2 or 4.3 (can not remember ...)
Yesterday I decided to upgrade to version 4.4.2 (now it is called SLIMKAT),
Somehow I got stuck in a loop of the BOOT screen when I tried to just install as I did,
Then i FLASH again to CWM latest version and then installation worked properly. (At the middle of the road I tried things - I've done FLASH to STOCK)
Even when I did the FLASH to the STOCK and the new CWM , I noticed that I have no connection/emergency calls only,
I tried installing a few different ROMs and some old and new versions of the STOCK and all the same.
What I saw on that network after upgrade is a bug regarding losing IMEI or serial number, but in my case when I went to the ABOUT -> the IMEI is correct (as written at the back of the phone) and serial No is not 0000 ....
I forgot to mention that for all installations I did -> I played with all kinds of modems also (Every time I tried something else someone said helped him in various guides on the net ...)
Any ideas how I can solve it?
Thank you.
[update] also tried the "ARIZA Patch" and nothing works.
deception8888 said:
Hello everyone,
I read countless cases in communities on this subject and I have tried almost everything, I am quite at a loss,
My case is like this:
I used SLIMBEAM version 4.2 or 4.3 (can not remember ...)
Yesterday I decided to upgrade to version 4.4.2 (now it is called SLIMKAT),
Somehow I got stuck in a loop of the BOOT screen when I tried to just install as I did,
Then i FLASH again to CWM latest version and then installation worked properly. (At the middle of the road I tried things - I've done FLASH to STOCK)
Even when I did the FLASH to the STOCK and the new CWM , I noticed that I have no connection/emergency calls only,
I tried installing a few different ROMs and some old and new versions of the STOCK and all the same.
What I saw on that network after upgrade is a bug regarding losing IMEI or serial number, but in my case when I went to the ABOUT -> the IMEI is correct (as written at the back of the phone) and serial No is not 0000 ....
I forgot to mention that for all installations I did -> I played with all kinds of modems also (Every time I tried something else someone said helped him in various guides on the net ...)
Any ideas how I can solve it?
Thank you.
[update] also tried the "ARIZA Patch" and nothing works.
Click to expand...
Click to collapse
Which version of stock rom did you use?
If you were on 4.3 before then 4.1.2 will get network problems.
For SlimKat, you can try patched modems. Links are available in efs thread.
deception8888 said:
Hello everyone,
I read countless cases in communities on this subject and I have tried almost everything, I am quite at a loss,
My case is like this:
I used SLIMBEAM version 4.2 or 4.3 (can not remember ...)
Yesterday I decided to upgrade to version 4.4.2 (now it is called SLIMKAT),
Somehow I got stuck in a loop of the BOOT screen when I tried to just install as I did,
Then i FLASH again to CWM latest version and then installation worked properly. (At the middle of the road I tried things - I've done FLASH to STOCK)
Even when I did the FLASH to the STOCK and the new CWM , I noticed that I have no connection/emergency calls only,
I tried installing a few different ROMs and some old and new versions of the STOCK and all the same.
What I saw on that network after upgrade is a bug regarding losing IMEI or serial number, but in my case when I went to the ABOUT -> the IMEI is correct (as written at the back of the phone) and serial No is not 0000 ....
I forgot to mention that for all installations I did -> I played with all kinds of modems also (Every time I tried something else someone said helped him in various guides on the net ...)
Any ideas how I can solve it?
Thank you.
[update] also tried the "ARIZA Patch" and nothing works.
Click to expand...
Click to collapse
Try this post 1984 >> http://forum.xda-developers.com/gal...ii-network-problem-update-sn-t1918601/page199 <<
Hi I solved it :
installed a K6 modem (cant post a link since im a new user)
just when i thought i tried every modem seems like i havnt tried this one... thanks for the help
Imei
The thing that I tell you since you the imei number intact is reset the phone to the original before being even worse things, find a guide on restoring the Terminal in XDA there are many and then you can again install whatever you want but first make a backup of the folder EFS.
I have a I9300 that is not getting any network, the IMEI is 0049... and the serial number is a string of zeros. It was previously running stock 4.1.2 but I wanted to upgrade to at least the latest official ROM - 4.3 and thats how I ended up in this situation.
I've been a Linux user forever and I've owned and flashed a few Android phones in the past but this is my first Samsung Android handset and so the first time I've been bitten by efs. I did lots of reading before attempting the upgrade so I knew to backup the efs partition before doing any flashing. I did this with ktool but restoring my efs backup to various ROMs hasn't restored my network connectivity.
I'm on the 3 network in the UK so when I've been using Odin to restore stock ROMs (I've tried restoring both 4.3 and 4.1.2) I've been using the BTU versions ie
I9300XXUGMK6_I9300OXAGMK6_BTU
I9300XXEMG4_I9300OXAEMG4_BTU
I have now spent four full days reading and trying various solutions suggested in an array of threads on this forum, I've read all the stickies in http://forum.xda-developers.com/galaxy-s3/general/samsung-galaxy-s3-sticky-roll-thread-t2344125 plus many more threads and now I've just about given up. I've tried flashing various unofficial ROMs too like CM 10.2, 11 and RevolutionS5 but they all have no network.
My phone is not in factory mode and I've tried zuluman's patched kernel/modem with 4.3 without any luck. I've tried factory resets, deleting /efs, changing the permissions of and editing nv_data.bin with a hex editor amongst other tricks. No go.
So it seems my only remaining option is to take / send my phone to be repaired or fork out for one of these hardware devices that claim to be able to repair IMEI issues. Problem is then I'm back to square one, I've not learned what I wanted to about my phone (how to safely reflash/upgrade it) and I'll be stuck on whatever the repair shop leave me with.
I'd much, much rather fix this myself as then that opens the doors to experimentation, it will prolong the (so far all too brief) life of my phone and be much more satisfying. Until now I thought the SGS3 was (is?) a class phone and I think its much better than the Nexus 4 I had previously, despite inferior specs in many respects.
I'm sure its possible to recover from this without buying dedicated hardware or at least it should be..
I bought my phone 2nd hand less than three months ago but its no longer under any warranty. Another thing that could be an issue is that I was sold it without a box and there is no IMEI printed under or on the battery.
Thanks for your help!
It would seem from my experimentation that reflashing stock ROMs with Odin on the I9300 doesn't affect the efs partition, or at least the stock ROMs I've been flashing don't repair/recreate efs.
I'd be perfectly happy using the Samsung generic IMEI if it will let me connect to my phone network. If anyone knows how might enable that, please speak up!
Same problem encountered before until now...
This are when the problem starts.
My GS3 International had CynagenMod stable build.
1. I've noticed one morning that my GS3 is stuck in a bootloop.
2. Tried reflashing the stable CM ROM, but still stuck n the bootloop.
3. Tried flashing my stock rooted firmware from my TWRP backup.
- after this, I've noticed that only emergency calls and not registered on network always appears.
- my IMEI becomes now generic with 0049...00 but with serial number.
4. Tried sending it for repair in our local cellphone repair shop. Network signal is fixed now but it always ask for permission for the radio. So battery drain is massive.
5. I didn't send it back. Tried to fix it myself. Installed the stock firmware 4.3 using jellybean. To my surprise, the IMEI and serial number comes back. But still no network signal (emergency calls only).
Lastly, still looking for a fix. If anyone had a fix for this one this will be a great help. Also tried restoring/updating through Kies. All the process I took had failed.
Not sure if the problem was the EFS/IMEI or the modem or radio install from the firmware I just installed.
For now, I'm using the stock 4.3 firmware. The only problem now is the network signal. Any suggestions or fix is a great help. TIA!
I have read of people fixing the no network by flashing a known good efs image but I suppose it would have to contain a working generic IMEI. Please PM me if you have such an image for a i9300. I'll have to find such a thread again and get PM'ing.
I've been disappointed by a few things in trying to upgrade my SGS3.
* There is no well documented fix for this EFS/IMEI/no network issue
* This issue seems to be very common for SGS3 owners who have attempted an upgrade to 4.3 or flashing alternate ROMs yet there is no mention of any of this on
http://wiki.cyanogenmod.org/w/Known_Issues_page_for_i9300
and
http://wiki.cyanogenmod.org/w/SGS3FAQ
There needs to be.
* It doesn't seem Heimdall is able to flash a tar.md5 in one hit like Odin can which is a shame for us Linux and OSX users
Great phone but not for hackers and tweakers it seems.
Sounds like the efs was already corrupt before you tried the upgrade, probably a previous botched repair which only worked on 4.1
Take it to a repair centre and pay for them to recode it for you, there is no other fix. Make sure it connects on 4.3 before you pay.
Suggestion: flash a firmware older than MG4 and let it update OTA or by KIES. Generating the efs-v2-data may solve.
the battle rages on...
rp158:
That sounded like a good suggestion to me so I used Odin to install I9300XXELL4_I9300OXAELL4_BTU, which predates MG4. Because the aim was to try an OTA update, I did not root or flash a custom recovery as I know they don't like that.
Like all the ROMs I've tried since my prob, it installed fine but I get no network. After connecting to wifi I first tried OTA via Settings -> About Device -> Software update -> Update but it just says "Failed to update firmware due to network or server problem". I can browse the internet fine so could this be a problem with Three (my telco)? I've heard of some providers blocking OTA.
So next I tried Kies (not Kies 3) under Windows 8. I went to Tools -> Firmware Upgrade and Initialisation but I just get the error 'GT-I9300 does not support initialising'. Fail, fail and fail!
I've yet to run 'Triangle away' and so I have several flash count points listed on the download screen. Could this stop OTA from working? Is there a limit to the number of flashes you can perform before something nasty happens? I presume its just something retailers check before they refund or repair phones.
Something else I noticed while fighting my phone today was that recovery says the CSC code is now KOR. Could that stop OTA working?
Likes me a good idea to run 'Triangle away': I think there is no max. count for flashes, but perhaps counter>0 and status=custom block the update-procedure. So try after unroot both methods again. (CSC-code I down't know.)
Whilst still running I9300XXELL4_I9300OXAELL4_BTU, I rooted it then successfully ran Triangle Away to clear the flash counter before running csc changer to change my CSC to BTU (from KOR). I would've changed it to XEU but that wasn't an option. I checked that worked fine, which it did, and running CSC changer also (conveniently, in my case) un-roots your phone.
After that I tried updating via both Kies and 'About Device' software update but both just gave me the same errors as before so scratch another idea off my very long list then.
Then go to #5
rp158 said:
Then go to #5
Click to expand...
Click to collapse
?
Do you mean Odin flash I9300XXEMB5, which I think is the last release before MG4?
pfmdan said:
?
Click to expand...
Click to collapse
Sorry, too short. Post 5 = repair by Samsung.
So, if I choose to get my phone fixed, has this proven that I will be unable to flash any alternate ROMs on it without losing my network/IMEI/serial again?
Maybe I should've backed up my EFS with philz recovery or dd insteal of ktool, then I might not have ended up in this situation?
Maybe the US/Qualcomm models of the S3 are safe to flash with alternate ROMS whilst the Exynos-based models aren't?
Can anyone recommend a good repair service in the UK if my local repair shops can't help?
Thanks for your suggestions rp158!
pfmdan said:
So, if I choose to get my phone fixed, has this proven that I will be unable to flash any alternate ROMs on it without losing my network/IMEI/serial again?
Click to expand...
Click to collapse
No, that's unnormal. But read before flashing, what users say (some beta's or nightlies are buggy).
Maybe I should've backed up my EFS with philz recovery or dd insteal of ktool, then I might not have ended up in this situation?
Click to expand...
Click to collapse
Probably. I suggest Philz, TWRP or by TerminalEmulator.
Can anyone recommend a good repair service in the UK if my local repair shops can't help?
Click to expand...
Click to collapse
Official Samsung repair-service.
I thought Philz was the only recovery that gave you the option of backing up EFS? I didn't think TWR supported EFS backup/restore? CWM doesn't.
TWRP can, of course.
A corrupted efs can also effect the stability and use of wifi as mac address etc is also stored there.
Check if there is a backup of your efs. Some roms make a backup of it also - neatrom for example. Try flashing xxemg4 or later baseband to see if it fixes it because after having the later bb you also have efs v2
FIXED
Thanks to everyone who made suggestions in trying to get my phones connection back. Its working again now. My 0049 IMEI has gone, my real IMEI come back and my serial number has returned so I can make and receive calls again!
The thing that was preventing my connection and leaving me to suffer the dreaded 'Emergency Calls Only' and 'Not registered on network' errors was nothing to do with EFS but because I had an incorrect CSC. I had flashed stock BTU roms instead of H3G, which is what I should've used being on Three. As soon as I flashed a rom with the correct CSC, my IMEI and serial numbers both returned and this allowed the zuluman patched modem / kernel combo to work. I'm now happily running 4.3 whereas I was previously on a rooted stock 4.1.2.
There are literally 100's of threads on the S3 forums here with S3 owners ending up with a generic IMEI and no serial after attempting a 4.3 upgrade and the standard response is nearly always 'your EFS is probably corrupt' or 'your EFS in the wrong format'. That will be the case sometimes but I'd bet that more often than not the EFS is fine (if updated) and users have flashed a CSC for the wrong region for their telephone network.
Key tools in getting this prob fixed that hardly get any mention are the csc changer app (downloadable via Play but requires root and also factory resets/unroots when run) and A.S_id's rescue firmware
http://forum.xda-developers.com/galaxy-s3/general/odinfirmware-sgsiii-i9300-prerooted-t1825272/
I'd recommend I9300 users flash A.S._id's ROM if they can't find a firmware with the correct CSC for their network and/or csc changer doesn't restore their IMEI and serial.
Lets fix these forums by getting this info into the FAQs in both the general and QA stickies because I know it to be missing hence the endless invalid IMEI / no network postings.
I'll be back shortly wth more details and suggested additions to the S3 FAQs / stickies.
Thanks all!
I've ended up running A.S._id's 4.3 deodexed 'stock' ROM w/ Boeffla 5.3 kernel and zuluman's patched XXUGMK6 modem.
When I used zuluman's patched XXUGMK6 kernel, I would experience small but frequent glitches in 3G streamed audio. I don't have this problem with Boeffla 5.3.
I'd also highly recommend stock TW users turn off smart screen to massively increase your battery life very easily.
hey guys!
I have samsung galaxy s2 gt-I9100. Whenever I install a custom rom, everythings works fine but i am not able to use mobile network and i received "Error while searching for networks" when I go to settings>>Mobile networks>>network operators. The IMIE number is fine.
I have tried many roms including:
--cm-10.1.3-i9100
--cm-11-20140804-SNAPSHOT-M9-i9100
--pa_i9100-4.42-20140708
--pa_i9100-4.45-20140729
--Slim-i9100-4.4.4.build.9.0-OFFICIAL-8301
The last rom which worked fine was RootBox-JB-i9100-V4.0. All roms released after this rom have this issue.
I have searched for issue on google and tried various solutions but so far no success.
Please Help!
And can you guys suggest me any rom which is not based on CM?
Go to settings-->about phone and look for "Baseband version"
If it says "unknown" or similar you may need to reflash the modem before you flash the rom.
Or even worse you might need to do a reboot (it actually worked once).
Also do emergency calls work? If yes then it might be a problem with your sim card or you contract (or just bad luck).
ruleh said:
Go to settings-->about phone and look for "Baseband version"
If it says "unknown" or similar you may need to reflash the modem before you flash the rom.
Or even worse you might need to do a reboot (it actually worked once).
Also do emergency calls work? If yes then it might be a problem with your sim card or you contract (or just bad luck).
Click to expand...
Click to collapse
The Baseband version is visible and a valid one. Also my sim works on stock rom or any other phone.
SInce I have no idea what the cause could be, here are some random things to try out, of which one might work:
-make sure you're not in airplane mode
-do a full complete wipe
-try a different sim (and see if it works)
-make sure the sim is not upside down
-fully shutdown the phone (e.g remove battery for a day [maybe not that long])
-clean contacts between sim and phone (how? no idea)
-try (even-) more roms (if there are any left)
-test a few kernels
-maybe look through the logcat (if it actaully outputs something worthwhile)
As you can see none of these "soloutions" are based on.....uhmm....anything(?). But at least....if none of them work, you know what not to do.
faizi97 said:
The Baseband version is visible and a valid one. Also my sim works on stock rom or any other phone.
Click to expand...
Click to collapse
Perhaps you could flash back to stock rom then flash custom rom again, that way all modem files and network related files can be fixed/re-installed. By any chance have you tried changing modems? It might not help you but it's a suggestion.