Hi there, please help.
I update to 19300XXEMC3 but it keep on software updating (2 more time) and it download the latest one, which turn out to be I9300XXEMG4. Now it can't make any more calls, only emergency calls and no date. I read something about the EFS partition, members were talking about saying something about the IMEI not reading and you cant downgrade back to an older Firmware, but when enter *#06# the IMEI shows up normal. Is there any way to fix this problem or do I have to wait for an update like 4.2.0, etc? or Is there any ways I can make data/calls work on XXEMG4? or Is there any ways I can go back to my stock Firmware 4.0.4 I9300XXBLH1?
Thank you in advance.
hawjz said:
Hi there, please help.
I update to 19300XXEMC3 but it keep on software updating (2 more time) and it download the latest one, which turn out to be I9300XXEMG4. Now it can't make any more calls, only emergency calls and no date. I read something about the EFS partition, members were talking about saying something about the IMEI not reading and you cant downgrade back to an older Firmware, but when enter *#06# the IMEI shows up normal. Is there any way to fix this problem or do I have to wait for an update like 4.2.0, etc? or Is there any ways I can make data/calls work on XXEMG4? or Is there any ways I can go back to my stock Firmware 4.0.4 I9300XXBLH1?
Thank you in advance.
Click to expand...
Click to collapse
It's better to instal CWM on your phone adn then flash any Stock Custom Roms. May be then your prob gets solved.
hawjz said:
Hi there, please help.
I update to 19300XXEMC3 but it keep on software updating (2 more time) and it download the latest one, which turn out to be I9300XXEMG4. Now it can't make any more calls, only emergency calls and no date. I read something about the EFS partition, members were talking about saying something about the IMEI not reading and you cant downgrade back to an older Firmware, but when enter *#06# the IMEI shows up normal. Is there any way to fix this problem or do I have to wait for an update like 4.2.0, etc? or Is there any ways I can make data/calls work on XXEMG4? or Is there any ways I can go back to my stock Firmware 4.0.4 I9300XXBLH1?
Thank you in advance.
Click to expand...
Click to collapse
Please read the faqs and guides first.
EFS
/IMEI is very important .
Hi there I have a I9300 (International Version) of S3
So I'm just getting straight to the point
I had bought a s3 from a private seller from ebay and it was running 4.1.2.
I have a bit of experience in using Odin and I had downloaded some UK BTU android 4.3 version from sammobile.com which I usually use to update my phone.
But today if went wrong
I never did root because I never did like it and never made an efs backup
I had flashed I9300XXUGMK6_I9300OXAGMK6_I9300XXUGMK6_HOME.tar.md5 file to my phone and everything went perfectly fine
BUT THEN!
I tried calling some of my friends and I noticed that my sim wasn't being recognised
It didn't take long until I realised that my IMEI number had been to some random 0049***** number (I had found out that this was generic and was'nt my real IMEI Number)
I had then checked the IMEI number on the back of the phone and it did not match what was said in my phone settings
I have now clocked that it was the 4.3 android which was screwing me up
I have never installed any custom roms .etc and have only ever installed official ones from sammobile
So why would my phone's EFS get f***ed up and I also did'nt do any in Odin like phone efs clear
My phone had also ran out of warranty so I can't play dumb either
I have researched and found that it is possible to edit the nv_data file.etc like on http://forum.xda-developers.com/showthread.php?t=1804117
I have also tried downgrading but now odin wont allow but probably has something to do with samsung (downgrading policy)
I have also NOW made a backup of my efs folder and my phone is fully functional but my IMEI AND my SERIAL NUMBER was changed
Be honest do I have a realistic chance of recovering my phone or would I have to shell out of repairs and if so how much would it cost?
@mizzeeboy,
Try this?
~ RazorMC
Hey
U can try this too http://forum.xda-developers.com/showthread.php?t=2544109
RazorMC said:
@mizzeeboy,
Try this?
~ RazorMC
Click to expand...
Click to collapse
I have unfortunately tried this and I have realised that some of the phone data in the s2 is different compared to the s3
Also just one question if I could downgrade back to 4.1 would I get my IMEI back?
mizzeeboy said:
I have unfortunately tried this and I have realised that some of the phone data in the s2 is different compared to the s3
Also just one question if I could downgrade back to 4.1 would I get my IMEI back?
Click to expand...
Click to collapse
Sorry for the wrong link.
Maybe this?
- Try to reflash latest 4.3 for your country (this will most likely solve the issue if your efs is not broken)
- You can also try the methods in the link (there are many)
In my limited experience; downgrading to 4.1.2 after 4.3 gave me bootloop and it can't read efs2 (from 4.3)
~ RazorMC
Flash this modem through Odin (http://www.mediafire.com/download/s79zs955sok085h/modem.bin) it's MK6, it should fix the problem for you.
Saad_ said:
Flash this modem through Odin (http://www.mediafire.com/download/s79zs955sok085h/modem.bin) it's MK6, it should fix the problem for you.
Click to expand...
Click to collapse
Thanks I have tried this before and I have unfortunately failed along with your same file.
it was previously on 4.1.2.
I flashed Omni 2.4 on s3.
It was not showing signals of network (In Pakistan)
went to sammobiles.com for new firmware.
it is international version so i took for south africa (as phone came from south africa) flashed that rom and it is stucked on BOOTLOOP.
i want to go on official 4.3/4.4.
tries searching on google but failed
if someone can help to make it run back
prefered 4.4 or 4.3 with network signals in Pakistan.
Forums says goto recovery . Volup+Home+Power is not working for me
i just can enter into download mode
Regards
Get a stock .tar.md5 package from www.sammobile.com and flash it using Odin. Then boot into recovery, restore to factory defaults, and clear cache then reboot. Everything should be working properly. If you lost network flash the latest NA8 modem file.
Saad_ said:
Get a stock .tar.md5 package from www.sammobile.com and flash it using Odin. Then boot into recovery, restore to factory defaults, and clear cache then reboot. Everything should be working properly. If you lost network flash the latest NA8 modem file.
Click to expand...
Click to collapse
there are so many roms for different countries for pakistan is not present when i write i9300 in firmware search.
which one should i install??
saadtariq73 said:
there are so many roms for different countries for pakistan is not present when i write i9300 in firmware search.
which one should i install??
Click to expand...
Click to collapse
Any country it doesn't matter as long as not a one for a specific carrier.
solved this problem now i m not able to receive calls it says that NOT REGISTERED ON NETWORK,IMEI IS OK.
any solution to that
saadtariq73 said:
solved this problem now i m not able to receive calls it says that NOT REGISTERED ON NETWORK,IMEI IS OK.
any solution to that
Click to expand...
Click to collapse
Do you have a modem (baseband) compatible with your region?
If yes, is your phone unlocked (to be used with any carrier)?
Think about this last question carefully. Unlocking through software (like the galaxy sim unlock app) can be lost when flashing latest firmwares because of the efs format change. That might be why you get not registered on network.
If your phone was unlocked through imei (with a code provided by the carrier) or if it was factory unlocked (never locked in the first place) then I don't know whats wrong with it, sorry.
Hi guys i really need your help.
yesterday i updated my S3 from CM M7 to M8 version,since then i get emergency calls only
my imei is ok,and yet i recover it again. i did system restore,flashed other rom,burned with Odin 3 versions of Samsung original firmware,replaced sim but nothing doesn't work
anyone can think about another option?
Flash latest stock firmware for your country with Odin, not original.
If the imei or serial number is still not being read then restore your efs backup. If you don't have a backup then pay for a repair, make sure the phone works on 4.3 before you pay.
boomboomer said:
Flash latest stock firmware for your country with Odin, not original.
.
Click to expand...
Click to collapse
iv'e already did that :/
Hey guys,
Sorry in advance for what is no doubt something that's came up a few times in the past (as is clearly evident by the posts). I've spent a long time trying to get around the issues with this thing so hopefully I can explain what I've done so far which might help.
So, basically -
My brother had an S3. The screen broke (glass only) and he asked me to repair it. This was a few months ago. Inbetween he moved to using a Windows phone and had the S3 sitting around until he eventually decided to hand me it to repair a couple of days ago.
Now, the phone was working flawlessly prior to him turning it off and switching over to the Windows phone. The S3 sat dormant for a few months, battery out.
When I went to turn it on to test the screen and buttons to ensure that's the only fault, it wouldn't get past the boot screen.
No huge deal there.
Upon checking in recovery it was unable to mount the EFS partition. I managed to get round that.
It still wouldn't boot, so I flashed a new ROM and it booted up fine however was in "Factory mode" with IMEI starting 0049.
I've done a fair amount of searching and came to a few conclusions but essentially :
How I don't know but his EFS folder was competely corrupt and essentially contained few files, none of which were IMEI related. I have no clue how this has happened but it has.
I've managed to get the phone working ALMOST flawlessly by restoring a stock EFS backup IMG using kTool, I HAVE the phone's IMEI and serial which are printed on the phone itself. Only issue now is that the phone can't connect to any networks - because the IMEI is a default.
So, I've dug around in the stock EFS backup IMG that I was able to find (which has got the phone working great, minus mobile networks) and found that the IMEI folder contained a file "mps_code.dat". Upon opening this file it's basically empty. I assume this is because it's a stock EFS I located.
Does anyone have any clue how I can input the IMEI into this file? I tried to decompile the IMG, type it into the file and save, then recompile the IMG however kTool doesn't recognise the newly created IMG file and crashes, then restores the phone. Is there a specific tool I should be using to make the IMG and can someone root into their "mpd_code.dat" and tell me the format that it needs to be in? (I don't need or want any IMEI numbers, just the format that the file is. Just open it in a text editor through Root Explorer (root\efs\imei) and star out the IMEI if you can).
Just to clarify before anyone jumps on it - I'm NOT looking for the file(s) OR the IMEI numbers on anyones phone with that request. Simply the format in which it should be in. I'm simply trying to put the IMEI for the phone ONTO the phone so it'll recognise networks and work as it should. Everything else is absolutely fine now.
So just to clarify the options I've boiled down to :
Recompile the efs.img with the correct IMEI within - if someone can tell me how that'd be great - then restore it on kTool.
OR
Edit the on-phone mps_code.dat with the correct IMEI but I need the format (if someone could peek at theirs that'd be great).
Thank you in advance all and sorry for the story! If I manage to get this to work I'll upload a tutorial with all the relevent files required which I know will help a lot of people.
Cheers
Mine mps_code.dat have 3 letters in it i-e 'TNL' which is csc i think. And imei is in efs1 and efs2 partition you can see in pit analysis thread google it if you don't know anout this thread.
Only thing which you can do is give phone to repair shop they have boxes and tools which can write imei. Or take backup of efs1 efs2 and efs of other phone and restore it in your phone.you do backup/restore using partition backup app in playstore by wanam.
Thanks for your reply. I will try to locate someone else I know with an S3 and pull their EFS - hopefully something will happen that's of benefit.
In the meantime, I'll focus on this as hard as I can to get it sorted. I've managed to go from having the IMEI reading as a random 0049 one, to "Null/Null" which means it HAS been written to (or does in my mind), just with nothing rather than the correct number.
If I get anywhere I'll update this thread, and if im successful in the repair I'll create a How-To based on what I did.
Cheers
I can repair your device. Had the same problem with my mothers phone.
The problem is that samsung changed the style of the efs format years ago and the S3 was falling in this time.
So if you need help, i can help.
konsolen said:
I can repair your device. Had the same problem with my mothers phone.
The problem is that samsung changed the style of the efs format years ago and the S3 was falling in this time.
So if you need help, i can help.
Click to expand...
Click to collapse
Hey mate,
Want me to PM you?
Thanks
I had the same problem days ago and I couldn't connect to sim network.
What I did was flash stock rom using odin and then a custom modem and a custom kernel I found in the internet. At the end it gave me a normal imei number (not the [email protected]%) but it wasn't my original imei... nevertheless it can connect now without any issues .
jairolas said:
I had the same problem days ago and I couldn't connect to sim network.
What I did was flash stock rom using odin and then a custom modem and a custom kernel I found in the internet. At the end it gave me a normal imei number (not the [email protected]%) but it wasn't my original imei... nevertheless it can connect now without any issues .
Click to expand...
Click to collapse
Hey bro,
Do you remember specifically what ROM, kernel and modem you flashed? Ive tried this with no luck so interested in trying your combination.
Cheers
Ok guys this is exactly what I did:
1- backup all your data.
2- download a stock 4.3 jellybean rom from sammobile (I used the Trinidad and Tobago version because I live in Mexico but that shouldn't matter), autoroot cf for i9300 4.3 from their website and twrp 2.8 recovery, again from their website.
3- download this especial kernel and this modem:
https://www.dropbox.com/s/4cawyqzg8zo1vot/Patched_XXUGMK6_kernel.zip.zip?dl=0
https://www.dropbox.com/s/tky93zds14kt1hz/Patched_XXUGMK6_modem.zip.zip?dl=0
4- Proceed to flash stock 4.3 rom using odin 3.07.
5- After stock rom is installed flash the root cf file and recovery tar using odin.
6- Now that you have a rooted stock rom with custom recovery proceed to flash both the especial kernel zip and the modem zip using twrp recovery.
7- You should now be able to connect network.
Good luck.
jairolas said:
Ok guys this is exactly what I did:
1- backup all your data.
2- download a stock 4.3 jellybean rom from sammobile (I used the Trinidad and Tobago version because I live in Mexico but that shouldn't matter), autoroot cf for i9300 4.3 from their website and twrp 2.8 recovery, again from their website.
3- download this especial kernel and this modem:
https://www.dropbox.com/s/4cawyqzg8zo1vot/Patched_XXUGMK6_kernel.zip.zip?dl=0
https://www.dropbox.com/s/tky93zds14kt1hz/Patched_XXUGMK6_modem.zip.zip?dl=0
4- Proceed to flash stock 4.3 rom using odin 3.07.
5- After stock rom is installed flash the root cf file and recovery tar using odin.
6- Now that you have a rooted stock rom with custom recovery proceed to flash both the especial kernel zip and the modem zip using twrp recovery.
7- You should now be able to connect network.
Good luck.
Click to expand...
Click to collapse
Thanks bro, will try that in the morning!
Hey mate,
I started the process of this today, using a stock samsung FW that I updated to using Kies.
Unfortunately the end result is the same, 0049 IMEI number.
What I'll do is I'll download the T&T 4.3 from Sammobile and see if that makes any difference.
Thanks again,
jairolas said:
Ok guys this is exactly what I did:
1- backup all your data.
2- download a stock 4.3 jellybean rom from sammobile (I used the Trinidad and Tobago version because I live in Mexico but that shouldn't matter), autoroot cf for i9300 4.3 from their website and twrp 2.8 recovery, again from their website.
3- download this especial kernel and this modem:
https://www.dropbox.com/s/4cawyqzg8zo1vot/Patched_XXUGMK6_kernel.zip.zip?dl=0
https://www.dropbox.com/s/tky93zds14kt1hz/Patched_XXUGMK6_modem.zip.zip?dl=0
4- Proceed to flash stock 4.3 rom using odin 3.07.
5- After stock rom is installed flash the root cf file and recovery tar using odin.
6- Now that you have a rooted stock rom with custom recovery proceed to flash both the especial kernel zip and the modem zip using twrp recovery.
7- You should now be able to connect network.
Good luck.
Click to expand...
Click to collapse
yetep said:
Hey mate,
I started the process of this today, using a stock samsung FW that I updated to using Kies.
Unfortunately the end result is the same, 0049 IMEI number.
What I'll do is I'll download the T&T 4.3 from Sammobile and see if that makes any difference.
Thanks again,
Click to expand...
Click to collapse
Hey hey,
Right unfortunately all of the above doesnt solve any issues im having with the IMEI.
What I'm ultimately trying to do is find out a way to fix this, without having to use third-party hardware or a samsung service station.
The real reason is that I don't think the average user should have to go that extent to fix this - it's ultimately Samsung's fault.
Android is designed to be customisable allowing users to go up/down versions as they please (provided it's compatible with the hardware of their phone).
Just a thought -
is there any possible way to "bake" the old style EFS into a newer rom?
yetep said:
Hey mate,
I started the process of this today, using a stock samsung FW that I updated to using Kies.
Unfortunately the end result is the same, 0049 IMEI number.
What I'll do is I'll download the T&T 4.3 from Sammobile and see if that makes any difference.
Thanks again,
Click to expand...
Click to collapse
Hey All (that are viewing this).
The above procedure didn't work. I have managed to get the IMEI to change from 0049 to NULL/NULL and back again at will using a blank EFS restore file that I've got, however can't figure out what and how to change the files WITHIN the EFS restore to the correct IMEI etc.
I'll continue my search and if I come across anything, I'll let you all know on here and create a How-To.
Cheers
Hey all - just a quick question on this.
Does anyone know how to modify the server to which a program points to check for user credits etc? There's clear reason I'm asking for this, however for obvious reasons I won't elaborate further right now.
Cheers
Hello there! Is the problem fixed? Couple of days ago i fixed someones i9300 whos having this kind of error. Pm me ill help
lyxtian said:
Hello there! Is the problem fixed? Couple of days ago i fixed someones i9300 whos having this kind of error. Pm me ill help
Click to expand...
Click to collapse
I have sent you a pm.
konsolen said:
I can repair your device. Had the same problem with my mothers phone.
The problem is that samsung changed the style of the efs format years ago and the S3 was falling in this time.
So if you need help, i can help.
Click to expand...
Click to collapse
I have a samsung galaxy s7 sm-G930F which is bricked. no imei anymore and no efs backup. can u help me fix it?