Hi, I rooted my Phone yesterday and installed TouchWiz Revolution, it installed ok, and is all working apart from the fact that I cannot make any calls or send any texts. Can anyone help me fix this?
I have tried to flash the stock firmware by using ODIN, but no matter what I do and how many drivers I install, it doesn't work. I also tried using the Busy Box and Azira patch method, but the .apk wouldn't install (yes I have unknown sources checked)
I'm very new to this territory, and feel that I am very out of my depth, any help would be greatly appreciated
(p.s I have my IMEI number written down somewhere, I don't know if that helps, as the box comes up blank on my phone)
you will have to flash the stock rom via odin
PRESS THANKS IF I HELPED
SamuelGTeague said:
Hi, I rooted my Phone yesterday and installed TouchWiz Revolution, it installed ok, and is all working apart from the fact that I cannot make any calls or send any texts. Can anyone help me fix this?
I have tried to flash the stock firmware by using ODIN, but no matter what I do and how many drivers I install, it doesn't work. I also tried using the Busy Box and Azira patch method, but the .apk wouldn't install (yes I have unknown sources checked)
I'm very new to this territory, and feel that I am very out of my depth, any help would be greatly appreciated
(p.s I have my IMEI number written down somewhere, I don't know if that helps, as the box comes up blank on my phone)
Click to expand...
Click to collapse
I think you have damaged your efs partition. Your efs partition contains your IMEI number. Unless you have a backup of your efs, your only solution is to go to Samsung Service Centre. Here is a thread to know more about efs and IMEI,
IMEI / EFS - Know this stuff - including "no network"
Hope I Helped
I think I'm just calling it quits :/ I get a new phone next Monday, so I've just gone and bought a £15 Unlocked phone to tide me over 'till then. Thanks for all your help!
SamuelGTeague said:
I think I'm just calling it quits :/ I get a new phone next Monday, so I've just gone and bought a £15 Unlocked phone to tide me over 'till then. Thanks for all your help!
Click to expand...
Click to collapse
Flash custom kernel..then u can get your imei back...
Sent from my GT-S5830i using Tapatalk 2
SamuelGTeague said:
Hi, I rooted my Phone yesterday and installed TouchWiz Revolution, it installed ok, and is all working apart from the fact that I cannot make any calls or send any texts. Can anyone help me fix this?
I have tried to flash the stock firmware by using ODIN, but no matter what I do and how many drivers I install, it doesn't work. I also tried using the Busy Box and Azira patch method, but the .apk wouldn't install (yes I have unknown sources checked)
I'm very new to this territory, and feel that I am very out of my depth, any help would be greatly appreciated
(p.s I have my IMEI number written down somewhere, I don't know if that helps, as the box comes up blank on my phone)
Click to expand...
Click to collapse
Ok...don't worry you can flash "Rafael Kernal" and flash rom again and after that flash kernel's modules
Related
Error: “Not Registered on Network”
SGS III have JB 4.1.1 (I9300XXDLI8) ROM/baseband, rooted with CF-Root/TWRP.
I was running the above ROM with some sort of (probably) Soft unlocking done by a local mobile repair shop. Anyway, recently I decided to try out one of the custom ROM i.e. Omega 32.1 (JB 4.1.1) and before proceeding any further I made a full backup on SD card with TWRP.
I downloaded and flashed Omega 32.1, thinking that I can always go back if something doesn’t work out. Anyway, long and the short of it, when I restored my S3 through TWRP restore, I found out that it isn’t connecting with my mobile network i.e. Warid Tel with the error “Not Registered on Network”.
By the way I also happen to have the factory unlock code for this SGS3, but unfortunately all the USSD codes I've tried to enter it, doesn't work.
Although, I guess I can take it back and get it re-unlocked again, but that isn’t going to allow me to install custom roms.
Can anyone guide me how to fix this situation, any tips, help, will be highly appreciated.
Regards
Babur
Megneto said:
Error: “Not Registered on Network”
SGS III have JB 4.1.1 (I9300XXDLI8) ROM/baseband, rooted with CF-Root/TWRP.
I was running the above ROM with some sort of (probably) Soft unlocking done by a local mobile repair shop. Anyway, recently I decided to try out one of the custom ROM i.e. Omega 32.1 (JB 4.1.1) and before proceeding any further I made a full backup on SD card with TWRP.
I downloaded and flashed Omega 32.1, thinking that I can always go back if something doesn’t work out. Anyway, long and the short of it, when I restored my S3 through TWRP restore, I found out that it isn’t connecting with my mobile network i.e. Warid Tel with the error “Not Registered on Network”.
By the way I also happen to have the factory unlock code for this SGS3, but unfortunately all the USSD codes I've tried to enter it, doesn't work.
Although, I guess I can take it back and get it re-unlocked again, but that isn’t going to allow me to install custom roms.
Can anyone guide me how to fix this situation, any tips, help, will be highly appreciated.
Regards
Babur
Click to expand...
Click to collapse
Check your IMEI number.
Has it changed?
eggman89 said:
Check your IMEI number.
Has it changed?
Click to expand...
Click to collapse
No it hasn't changed.
The problem was the original "soft unlock"
Megneto said:
...
I was running the above ROM with some sort of (probably) Soft unlocking done by a local mobile repair shop. Anyway, recently I decided to try out one of the custom ROM i.e. Omega 32.1 (JB 4.1.1) and before proceeding any further I made a full backup on SD card with TWRP.
...
Click to expand...
Click to collapse
The problem was the original "soft unlock" - some of those (I believe even some early that were made by NSPro) are rather poor and are based on flashing a special modem binary. You will be able to fix it if you search around for the fix posted by Ariza (even if I believe something happened to the original post).
I am trying to find the fix by Ariza, but so far nothing has turned up. Also, if I search for the user "Ariza" it doesn't help either. Do you remember exact member alias?
Also, does that fix result in permanent resolution of the issue?
Or, is it better to get rid of this SGS3, and get factor unlocked version?
Thanks for your help and patience.
Edit:
I forgot to mention in OP that it correctly identifies the network when I check Status of the device.
Edit 2:
I was able to get hold of the guy who actually did the 'soft' unlocking in the first place, and he confirmed that it was done using NSPro (through Dongle) and is willing to do it again.
But the issue is, it will restrict me to JB 4.1.1 and I can't install any custom ROM.
Hmm ...
Megneto said:
I am trying to find the fix by Ariza, but so far nothing has turned up. Also, if I search for the user "Ariza" it doesn't help either. Do you remember exact member alias?
Also, does that fix result in permanent resolution of the issue?
Or, is it better to get rid of this SGS3, and get factor unlocked version?
Thanks for your help and patience.
Edit:
I forgot to mention in OP that it correctly identifies the network when I check Status of the device.
Edit 2:
I was able to get hold of the guy who actually did the 'soft' unlocking in the first place, and he confirmed that it was done using NSPro (through Dongle) and is willing to do it again.
But the issue is, it will restrict me to JB 4.1.1 and I can't install any custom ROM.
Click to expand...
Click to collapse
The thread was this:
http://forum.xda-developers.com/showthread.php?t=1918601
(in a post towards end I have some of the stuff from the forum where you had to register in order to get the files, and you might still recover some of those links - apparently those are patched versions of the corresponding stock modems which no longer check some of the information from nv_data.bin; you will need to add that modem after each major ROM change).
If you only plan to use 4.1.1 and not upgrade then NsPro should be OK, otherwise you either need a "subscription" to the services of that guy
Thank you for the help. I will go through that thread soon.
I've have also looked at this thread http://forum.xda-developers.com/showthread.php?t=1705650 by UpInTheAir. I have installed android SDK for Winx64 and successfully extracted modem.bin (as a test). I think I'll get the phone back to that guy, so he can patch the modem with NSPro again, once that is done, I'll extract the modem, repackage it so I can install it with CWM and test whether that can eventually help me in experimenting with other ROMs.
I will keep you posted on my progress.
Again thank you for your valued help.
Kind regards.
Babur
Having tried the method mentioned in my previous post, I finally gave up and took the phone for repair.
What transpired from thereon is interesting and confusing. As according to Mr. Repair 'serial number and IMEI' were repaired, nothing more. In fact I extracted the modem and compared it with the one I have, they are exactly same no patch applied.
However, both IMEI and serial number were showing correctly prior to the repair, and even after repair they are same (I double checked those with the original invoice/phone box etc.). So I am not sure how they were damaged when they were showing correctly.
Update:
I've sold the unit question, as I felt not to take any more risks with it, and bought an factory unlocked SGS3. Hopefully I will not face any problems with playing around with custom ROMs from hereon in.
Thank you and kind regards to all.
Babur
Hi
Im really hoping someone can help me here. I have a samsung GT-I9300 the battery has been failing and recently it stopped booting.
I couldnt do anything with it tried using KIES but it didnt recognise the device.
I couldnt not get into it at all so did not back up the EFS folder.
I then had it working with 4.3 after alot of trial and error regarding the PIT file and creating a new partition.
I then reverted to 4.1.2 to try to upgrade it via KIES again but it still doesnt get recognised.
I now have the actual phone working but it cannot make calls as the imei number is 004999010640000/01.
I have a note of the correct imei but cannot change it is there anything i can do to fix this,as i mentioned i do not have a backup of the efs folder.
Any help is much appreciated im pulling my hair out with this.
baldrat61 said:
Hi
Im really hoping someone can help me here. I have a samsung GT-I9300 the battery has been failing and recently it stopped booting.
I couldnt do anything with it tried using KIES but it didnt recognise the device.
I couldnt not get into it at all so did not back up the EFS folder.
I then had it working with 4.3 after alot of trial and error regarding the PIT file and creating a new partition.
I then reverted to 4.1.2 to try to upgrade it via KIES again but it still doesnt get recognised.
I now have the actual phone working but it cannot make calls as the imei number is 004999010640000/01.
I have a note of the correct imei but cannot change it is there anything i can do to fix this,as i mentioned i do not have a backup of the efs folder.
Any help is much appreciated im pulling my hair out with this.
Click to expand...
Click to collapse
What version android do you currently have on it? You basically need 4.3 or higher.
If that doesn't solve your issue you will need to take it to a repair center.
http://forum.xda-developers.com/showthread.php?t=2393289
I currently have 4.1.2 im on the ee service in the uk but am unsure which 4.3 i need
Since you upgraded your efs your early 4.1.2 cannot read it.
Read that link I gave you. Your need a 4.3 rom or modem XXEMG4or newer.
Here is a 4.3 rom for you.
http://www.sammobile.com/firmwares/1/?model=GT-I9300&pcode=EVR#firmware
No joy all works but i still have the stock imei number,i dont seem to be able to flash without a pit file using this each time make a difference?
baldrat61 said:
No joy all works but i still have the stock imei number,i dont seem to be able to flash without a pit file using this each time make a difference?
Click to expand...
Click to collapse
What does odin say when it fails?
It doesnt fail it installs it but the imei number remains the same
baldrat61 said:
It doesnt fail it installs it but the imei number remains the same
Click to expand...
Click to collapse
Opps It seems I didn't read it properly.
If the 4.3 flashed ok and you still have generic imei then you need to take it to a service center for repair.
Hello People
Again, I'm with problems with my S3 since the one time decided to test a custom ROM which turned out to screw my IMEI and got to it back working with BOX in repair service.
I n order to see if the BOX fix did actually solve my signal problem, it was suggested to me in a previous post that I flash the same stock rom via ODIN. Before that, I backed up current EFS as well.
Unfortunately, it seems the problem wasn't entirely solved. Same as before: both my IMEI and S/N are untouched (S/N does not coincide with S/N in the back of phone) and though it says I have a full signal, I'm not registered in network and i can't make or receive calls, sms, etc. Even though I restored the EFS folder, nothing happens.
I really wish not to go back to repair service again. What else can I do about this? Many thanks and excuse my rant. Hope I was thorough and clear on the problem. I also have a EFSv2_basebands_opt4.zip file I downloaded somewhere in xda . Would that help?
Many thanks.
rhrs1987 said:
Hello People
Again, I'm with problems with my S3 since the one time decided to test a custom ROM which turned out to screw my IMEI and got to it back working with BOX in repair service.
I n order to see if the BOX fix did actually solve my signal problem, it was suggested to me in a previous post that I flash the same stock rom via ODIN. Before that, I backed up current EFS as well.
Unfortunately, it seems the problem wasn't entirely solved. Same as before: both my IMEI and S/N are untouched (S/N does not coincide with S/N in the back of phone) and though it says I have a full signal, I'm not registered in network and i can't make or receive calls, sms, etc. Even though I restored the EFS folder, nothing happens.
I really wish not to go back to repair service again. What else can I do about this? Many thanks and excuse my rant. Hope I was thorough and clear on the problem. I also have a EFSv2_basebands_opt4.zip file I downloaded somewhere in xda . Would that help?
Many thanks.
Click to expand...
Click to collapse
Flash a patched modem and kernel from here >> https://drive.google.com/folderview...sharing&tid=0B6MIUd7HJudAbU5YaGkzOUowMG8#list << see if that works if it doesyou will always need to use the patched files.
Thanks tallman43! I'll try that. Also, I noticed now that the EFS folder is EMPTY :/. and the backup .tar I made with CWM says it's 0 bytes? wtf?
still, in phone info, imei and s/n are there. weird?
THANK YOU
Flash a patched modem and kernel from here >> https://drive.google.com/folderview?...kzOUowMG8#list << see if that works if it doesyou will always need to use the patched files.
Click to expand...
Click to collapse
Your recommendation worked like a charm. My signal is up and running normally. MANY THANKS tallman43.
Lastly, even if I sometime I decide to try out a custom ROM (unlikely at the moment, but who knows?), I still have to flash patched kernel&modem? or in case of factory reset (I will be selling the phone soon) ?That custom really messed up my phone...
rhrs1987 said:
Your recommendation worked like a charm. My signal is up and running normally. MANY THANKS tallman43.
Lastly, even if I sometime I decide to try out a custom ROM (unlikely at the moment, but who knows?), I still have to flash patched kernel&modem? or in case of factory reset (I will be selling the phone soon) ?That custom really messed up my phone...
Click to expand...
Click to collapse
Yes you will always need them.
tallman43 said:
Flash a patched modem and kernel from here >> https://drive.google.com/folderview...sharing&tid=0B6MIUd7HJudAbU5YaGkzOUowMG8#list << see if that works if it doesyou will always need to use the patched files.
Click to expand...
Click to collapse
tallman43 said:
Yes you will always need them.
Click to expand...
Click to collapse
I would still like to solve the problem at its roots: to fix the "not registered in network" problem whenever factory reset or stock ROM flash via odin is done. That is simply not normal. I might be selling the phone soon and the new user won't most probably know he/she would have to apply a patched kernel or etc.. ( let alone about rooting the phone).
Basically, bring the phone back to it's original sound state before I tried out the custom ROM. What can I do about that?
Hope I'm not being annoying.. just trying to get to the bottom of things
rhrs1987 said:
I would still like to solve the problem at its roots: to fix the "not registered in network" problem whenever factory reset or stock ROM flash via odin is done. That is simply not normal. I might be selling the phone soon and the new user won't most probably know he/she would have to apply a patched kernel or etc.. ( let alone about rooting the phone).
Basically, bring the phone back to it's original sound state before I tried out the custom ROM. What can I do about that?
Hope I'm not being annoying.. just trying to get to the bottom of things
Click to expand...
Click to collapse
There is nothing you can do without your original efs backup.Only a service repair can fix it.
tallman43 said:
There is nothing you can do without your original efs backup.Only a service repair can fix it.
Click to expand...
Click to collapse
Understood. I think I have the original EFS in my SD, though I tried replacing it once and it didn't work out... I suppose I'll have to make do. Thanks for everything man
Flashing modem with Ariza patch was bad idea. Your efs folder is screwed up now and you are addicted to constantly flash this dirty workaround.
If anyone have problems with registering in network please check your device serial number first. It must be the same as on the sticker under battery. If it's not then type *#0011# and check info under IMEI CERT. If there is FAIL info then you should use any box ie Z3X to correct phone's serial number. It takes only few minutes and is cheap. It's better long-term way than patching and permanently destroying your efs informations.
If you have backup then you should flash normal modem and restore original efs partition. Then find any GSM service center with box and tell them to fix serial number. It shouldn't cost more then 5-10 dollars.
____________________________________________
P3110 / I9300 / I9100 / NEXUS 5 / iPAD2
SirKunon said:
Flashing modem with Ariza patch was bad idea. Your efs folder is screwed up now and you are addicted to constantly flash this dirty workaround.
If anyone have problems with registering in network please check your device serial number first. It must be the same as on the sticker under battery. If it's not then type *#0011# and check info under IMEI CERT. If there is FAIL info then you should use any box ie Z3X to correct phone's serial number. It takes only few minutes and is cheap. It's better long-term way than patching and permanently destroying your efs informations.
If you have backup then you should flash normal modem and restore original efs partition. Then find any GSM service center with box and tell them to fix serial number. It shouldn't cost more then 5-10 dollars.
____________________________________________
P3110 / I9300 / I9100 / NEXUS 5 / iPAD2
Click to expand...
Click to collapse
I have never flashed the Ariza patch nor have I even mentioned it on my previous posts explaining the problem. Fixing the s/n issue is indeed adviseable, but paying to correct s/n using box here where I live is ASTRONOMICALLY expensive. They should answer for never having fixed it, but they won't. Here is a hell of a lot more than 5-10 dollars, unfortunately.
Believe me , I'm no happier in applying this sorry fix every time I want to factory reset or upgrade, etc; it's the only option I have left at the moment.
Those files you have flashed, I mean kernel and modem are patched with Ariza's method. It is called Ariza patch and it is latest solution you should take to resurrect your phone because it is a destructive one.
Sorry to hear that you can't repair it as it should be especially if you want to sell this device.
____________________________________________
P3110 / I9300 / I9100 / NEXUS 5 / iPAD2
SirKunon said:
Flashing modem with Ariza patch was bad idea. Your efs folder is screwed up now and you are addicted to constantly flash this dirty workaround.
If anyone have problems with registering in network please check your device serial number first. It must be the same as on the sticker under battery. If it's not then type *#0011# and check info under IMEI CERT. If there is FAIL info then you should use any box ie Z3X to correct phone's serial number. It takes only few minutes and is cheap. It's better long-term way than patching and permanently destroying your efs informations.
If you have backup then you should flash normal modem and restore original efs partition. Then find any GSM service center with box and tell them to fix serial number. It shouldn't cost more then 5-10 dollars.
____________________________________________
P3110 / I9300 / I9100 / NEXUS 5 / iPAD2
Click to expand...
Click to collapse
SirKunon said:
Those files you have flashed, I mean kernel and modem are patched with Ariza's method. It is called Ariza patch and it is latest solution you should take to resurrect your phone because it is a destructive one.
Sorry to hear that you can't repair it as it should be especially if you want to sell this device.
____________________________________________
P3110 / I9300 / I9100 / NEXUS 5 / iPAD2
Click to expand...
Click to collapse
oh... well, that I didn't know :$ SirKunon. I understand and totally agree with you on everything. I'll see maybe if I can find some place cheaper for getting it repaired... Many thanks
hi i was wondering if you guys can help me,i have your problem but i have an efs backup,but i cant seem to be able to restore my imei,i tried Ktool,efs professional,nothing seems to work,i should mention that the efs backup was from a Samsung 4.1.2 stock now my phone is on CM11
thanks
rhrs1987 said:
Hello People
Again, I'm with problems with my S3 since the one time decided to test a custom ROM which turned out to screw my IMEI and got to it back working with BOX in repair service.
I n order to see if the BOX fix did actually solve my signal problem, it was suggested to me in a previous post that I flash the same stock rom via ODIN. Before that, I backed up current EFS as well.
Unfortunately, it seems the problem wasn't entirely solved. Same as before: both my IMEI and S/N are untouched (S/N does not coincide with S/N in the back of phone) and though it says I have a full signal, I'm not registered in network and i can't make or receive calls, sms, etc. Even though I restored the EFS folder, nothing happens.
I really wish not to go back to repair service again. What else can I do about this? Many thanks and excuse my rant. Hope I was thorough and clear on the problem. I also have a EFSv2_basebands_opt4.zip file I downloaded somewhere in xda . Would that help?
Many thanks.
Click to expand...
Click to collapse
May i ask a few questions about your problem?
Which version were you using when you desided to use a custom rom?
Was your phone ever rooted before installing a custom rom (when you were on official)
Did you upgrade your phone before? (Official via ota or odin)
thewalekk said:
May i ask a few questions about your problem?
Which version were you using when you desided to use a custom rom?
Was your phone ever rooted before installing a custom rom (when you were on official)
Did you upgrade your phone before? (Official via ota or odin)
Click to expand...
Click to collapse
I was on 4.2.2 leaked version ROM some guy installed at a repair service some time ago when the phone belonged to my mother. I was actually rooted using the CF AutoRoot method, with Philz CWM recovery. I decided to change to a custom 4.3 without having changed first to a stock 4.3.
The problem came when, within the custom ROM's aroma installer, I ticked an option to upgrade the modem to some build I can't remember now and my signal became screwed up. I informed this in the developer's custom rom discussion thread about the issue to which he replied that the problem was that the EFS folder tried to convert from v1 to v2 and failed (this was when I learned of the whole efs version folder change since build XXX (don't remember).
I download a stock unbranded 4.3 ROM and flashed it via ODIN, believing that would solve the issue; it didn't. Finally, I became desperate and took it to a repair service where they used box. Apparently, late did I notice s/n was not the same as the one in the back of phone. I'm guessing that would solve the problem? I don't know.
i am sorry for your loss . i wish you had all that info you learned before a try and fail. now that your imei number is a clon number, and once a box tempers with that you cant go back even if you have your orijinal efs folder or backup. you should always have that 2 patched modem and kernel files on your sd card just incase. you can use custom 4.3 with the patched files and get a signal but you will always have some lags after some time because of the kernel. and lucky you samsung stopped updating s3 officially because patched files are only for 4.3. if you dont have a desire to use custom 4.4.4 kitkat roms then you are good to go and when it comes to sell the device, the price will be much lower then an original s3.
thewalekk said:
May i ask a few questions about your problem?
Which version were you using when you desided to use a custom rom?
Was your phone ever rooted before installing a custom rom (when you were on official)
Did you upgrade your phone before? (Official via ota or odin)
Click to expand...
Click to collapse
thewalekk said:
i am sorry for your loss . i wish you had all that info you learned before a try and fail. now that your imei number is a clon number, and once a box tempers with that you cant go back even if you have your orijinal efs folder or backup. you should always have that 2 patched modem and kernel files on your sd card just incase. you can use custom 4.3 with the patched files and get a signal but you will always have some lags after some time because of the kernel. and lucky you samsung stopped updating s3 officially because patched files are only for 4.3. if you dont have a desire to use custom 4.4.4 kitkat roms then you are good to go and when it comes to sell the device, the price will be much lower then an original s3.
Click to expand...
Click to collapse
Well, actually, IMEI didn't get cloned; of that I'm certain. IMEI is just the same as it was before I took it for the first time to repair service. It was the S/N that got changed somehow. Should I get them to correct the S/N, and use the original EFS folder (I found it, i think), would that correct all problems?
S/N number is the same with imei number as when you dial *#06# . And as i said before you cant go back even if you have your original efs folder. Dial *#06# and check your imei number from an " imei check site " you can find on google search. That will tell you what i mean.
There are: IMEI, device serial number and Android serial number. First two numbers are on the sticker in battery Bay. They must be correct because are used to authorize IMEI certificate.
Samsung's IMEI begins from 35.....
Serial number usually from RF......
If you see serial number in HEX format in phone's info section, something like f1abcadef1.. than it is android not device serial number and this mean troubles with authorize SIM card in operator network, even if it shows proper signal power.
I don't know there is any secret code to display serial number but there is plenty of phone's info apps in playstore which displays this alphanumeric string.
____________________________________________
P3110 / I9300 / I9100 / NEXUS 5 / iPAD2
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?
Ok so recently I was successful to root my SM-J110F (Vodafone, AUS).
I had found a forum on xda for a custom ROM for SM-J110M.
(link) - https://forum.xda-developers.com/android/software/rom-cleanertlite-os-j1-ace-t3585567
I flashed the ROM using TWRP and it worked.
However sadly, the ROM isn't really that great. The IMEI shows it's "null / null"
so I cannot fix it. The forum hasn't been active so I cannot get a response from the person who made it.
I was wondering if there is any way to fix it and I know I have a custom ROM for SM-J110M but I just want to know if it can be fixed.
Also, since I installed the ROM, the phone says it is a SM-J110M. I was wondering if I could flash in a stock SM-J110M ROM from SamMobile. I tried flashing it using ODIN, but it didn't work.
I really need your help, because I want to stay in 5.1.1. otherwise I'm just going to have to go back to 4.4.4. which is really old.
Problem can be solved and to fix that problem you need manualy to write IMEI and Serial number .
To write IMEI , and S/N you can use Octoplus but Changing IMEI or S/N number which doesn't belong to you is Ilegal so do at your own.
Here is steps for you to follow.
https://www.youtube.com/watch?v=F5k-jKCruv8