Hi all,
This is my first post i have a Samsung galaxy s3 gt i9305 4,3 jellybean which I flashed to 4.1.1 using Odin and then unlocked it using the service mode method that i found on here http://forum.xda-developers.com/galaxy-s3/help-i9305/sim-card-unlock-samsung-galaxy-s3-gt-t2185866 , it was on the EE network UK. I then brought triangle away to reset the binary download so i could system update, which didn't work and the counter is saying 1 so i cant update the system and a box comes up saying this device has been modified. My main problem is when ever i try and dial out it says mobile network not available. The phone is definitely unlocked as it doesn't ask for the unlock code anymore. When i first unlocked it GiffGaff came up but went again and i cant use data, text or phone.
Any help in solving this would be greatly appreciated it is driving me nuts and i just cant figure out what to do.
bella35 said:
Hi all,
This is my first post i have a Samsung galaxy s3 gt i9305 4,3 jellybean which I flashed to 4.1.1 using Odin and then unlocked it using the service mode method that i found on here http://forum.xda-developers.com/galaxy-s3/help-i9305/sim-card-unlock-samsung-galaxy-s3-gt-t2185866 , it was on the EE network UK. I then brought triangle away to reset the binary download so i could system update, which didn't work and the counter is saying 1 so i cant update the system and a box comes up saying this device has been modified. My main problem is when ever i try and dial out it says mobile network not available. The phone is definitely unlocked as it doesn't ask for the unlock code anymore. When i first unlocked it GiffGaff came up but went again and i cant use data, text or phone.
Any help in solving this would be greatly appreciated it is driving me nuts and i just cant figure out what to do.
Click to expand...
Click to collapse
You were on 4.3 which uses EFS V2 and flashed back 4.1.2 which uses EFS V1. I think, you have corrupted your EFS, that is the reason there is no mobile connection. Do you have a EFS backup???, if not, please try to flash 4.3 again, take a EFS backup using tools available in xDA(search) and once back up is taken, you can flash back 4.1.2 and reflash your EFS. But why do you want to go back to 4.1.2? we have lot of wonderfull rom's of 4.3 and even 4.4....:good:
cooljay5 said:
You were on 4.3 which uses EFS V2 and flashed back 4.1.2 which uses EFS V1. I think, you have corrupted your EFS, that is the reason there is no mobile connection. Do you have a EFS backup???, if not, please try to flash 4.3 again, take a EFS backup using tools available in xDA(search) and once back up is taken, you can flash back 4.1.2 and reflash your EFS. But why do you want to go back to 4.1.2? we have lot of wonderfull rom's of 4.3 and even 4.4....:good:
Click to expand...
Click to collapse
Hey thanks for your reply i will try that out and see if it makes a difference you are a super star thanking you kindly, sorry if i didn't make myself clear i do want to upgrade back to 4.3 after i have sorted everything else out for sure. I was on 4.3 but flashed to 4.1.1 to unlock the phone. I do not have a EFS back up which i have actually just been trying to educate myself on and now realise how important that part was, i just didn't know.
Why not ring EE to unlock?
f0xy said:
Why not ring EE to unlock?
Click to expand...
Click to collapse
Because that would be to easy i'd like to try and do it myself and learn and educate myself on how these things work but obviously when your trading blind sometimes you need steering in the right direction.
Related
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.
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?
It's been a while my S3 has been dead now, virtually rendering it into a WiFi tablet. Let me give a backstory.i had originally bought the phone and it was running 4.0.4, rooted. I wanted to go onto a different software so I came across Cyanogenmod. I flashed it with the automatic tool on pc. It had been quite some time I was running it, until I decided that I wanted to go back to stock. I was a complete noob back then, and where I may now a lot more stuff about phones now, there is still alot to learn. Anyway, I decided to flash a rom called "Back to noot", using twrp. The flash had gone successfully however I booted up to find that I had the infamous circle with the line through it, where the signal should be. I did some more digging and had concluded that my efs had been corrupted. As I was a complete noob, I didn't know what the efs partition was and I hadn't made a backup of it. So I was without a phone basically. Recently though I flashed the latest stock 4.3 rom onto it. My IMEI and baseband are back. However my IMEI isn't correct, the last couple of digits are incorrect, resulting in me having to face the "not registered on network". This is where I am now. I'm without my correct IMEI. Can anyone please help me restore my original IMEI? I have seen on some forums where some people have flashed down to 4.0.4 to successfully recover their phone. However sammobile now requires a premium account to download a 4.0.4 rom for the i9300, weirdly. Can anyone help me to restore the IMEI? Thanks.
You can download firmware for the i9300 on fw.updato.com . Search for the i9300 and filter by version to find the one you want. I am not sure if it is possible to restore your imei without an efs backup though. Good luck
Are you referring to the digits after the "/"?
I've never heard that dowgrading the stock ROM would change the imei.
audit13 said:
Are you referring to the digits after the "/"?
I've never heard that dowgrading the stock ROM would change the imei.
Click to expand...
Click to collapse
The entire IMEI is correct until I reach a certain point.
After the 3rd dash on the back of the phone, the digits follow "182/9". However when dialing *#06# on the phone itself the digits "4344/15". This is what I feel is causing the "not registered on network" error. I never knew downgrading can restore the phone. Ive seen on a forum that someone had recovered their phone by rolling from a higher firmware down to 4.0.4
Sent from my S6 Edge+ using XDA Labs
Was the phone purchased brand new, used, or refurbished?
If the phone is running a stock 4.3 ROM, you can't flash an older ROM as the phone will not allow flashing an older bootloader.
audit13 said:
Was the phone purchased brand new, used, or refurbished?
If the phone is running a stock 4.3 ROM, you can't flash an older ROM as the phone will not allow flashing an older bootloader.
Click to expand...
Click to collapse
The phone was purchased used. If I cannot flash an older version of Android does this mean it's no hope?
Sent from my S6 Edge+ using XDA Labs
It's very unusual that the imei would change on its own. It would be even more unusual for the imei to change when flashing one stock ROM over another. I suppose it is possible but I have never come across a situation where such a thing has happened.
Since the imei on the label does not match the imei in the phone and it was a used purchase, I tend to believe the phone is a "frankenphone" in that it was put together with parts from different phones.
Did you check to see if the imei from dialling *#06# belongs to an s3?
audit13 said:
It's very unusual that the imei would change on its own. It would be even more unusual for the imei to change when flashing one stock ROM over another. I suppose it is possible but I have never come across a situation where such a thing has happened.
Since the imei on the label does not match the imei in the phone and it was a used purchase, I tend to believe the phone is a "frankenphone" in that it was put together with parts from different phones.
Did you check to see if the imei from dialling *#06# belongs to an s3?
Click to expand...
Click to collapse
Actually I haven't checked to see if it does. Do you know how I can?
Sent from my S6 Edge+ using XDA Labs
Type the imei #s in here: https://swappa.com/esn?ref=mobilenations&data1=UUwpUvbUpU2855846YYw
Sent from my S6 Edge+ using XDA Labs
ABADAZZPLAYER said:
Not sure if it's been done properly but that's what came up
Sent from my S6 Edge+ using XDA Labs
Click to expand...
Click to collapse
Please remove your imei from the post. Enter the first 15 numbers.
audit13 said:
It's very unusual that the imei would change on its own. It would be even more unusual for the imei to change when flashing one stock ROM over another. I suppose it is possible but I have never come across a situation where such a thing has happened.
Since the imei on the label does not match the imei in the phone and it was a used purchase, I tend to believe the phone is a "frankenphone" in that it was put together with parts from different phones.
Did you check to see if the imei from dialling *#06# belongs to an s3?
Click to expand...
Click to collapse
Not if he flashed a firmware or rom based earlier than 4.3 and the phone has been 4.3. Efs changed at 4.3 and going backwards kills the efs partition because 4.2 or earlier can't read the new encryption.
There is a possibility that flashing earlier firmwares can write the imei back in, I've read something about this before. If all else fails then why not try it.. Its borked anyway.
Kies emergency recovery is another method but won't work if the phone was rooted.
I think have an efs of a now dead phone. It was a btu i9300 https://drive.google.com/file/d/1MiFFyCCeh1PFuQVZa-M4woreaofcDmrb/view?usp=drivesdk
shivadow said:
Not if he flashed a firmware or rom based earlier than 4.3 and the phone has been 4.3. Efs changed at 4.3 and going backwards kills the efs partition because 4.2 or earlier can't read the new encryption.
There is a possibility that flashing earlier firmwares can write the imei back in, I've read something about this before. If all else fails then why not try it.. Its borked anyway.
Kies emergency recovery is another method but won't work if the phone was rooted.
I think have an efs of a now dead phone. It was a btu i9300 https://drive.google.com/file/d/1MiFFyCCeh1PFuQVZa-M4woreaofcDmrb/view?usp=drivesdk
Click to expand...
Click to collapse
Is this efs dead or working?
Sent from my S6 Edge+ using XDA Labs
How you use it, no clue. I've never had to. It's from a phone that was eventually killed in an accident.
The files are as they were extracted. I zipped them up myself. It is not in anyway suitable to be flashed as is but if you can get the os working and root it you can copy the files to the correct folder, set the permissions and see what happens..
I thought seeing as I have no use for it someone else can, if they can.
shivadow said:
How you use it, no clue. I've never had to. It's from a phone that was eventually killed in an accident.
The files are as they were extracted. I zipped them up myself. It is not in anyway suitable to be flashed as is but if you can get the os working and root it you can copy the files to the correct folder, set the permissions and see what happens..
I thought seeing as I have no use for it someone else can, if they can.
Click to expand...
Click to collapse
I'll give this a try. Who knows maybe this could work. If it does , lots of thanks to you lol
Sent from my S6 Edge+ using XDA Labs
The phone was successfully recovered by flashing the XXUGMK6 ROM, then flashing the Patched UGMK6 Kernal and Baseband that zuluman had given. However the phone only accepted one SIM card from a couple that I had tried, and the phone thought I was in a roaming state, meaning I couldn't use mobile data. Other than that the text message and phone calling functionality, which was the main focus of the repair, has been successful.
Sent from my S6 Edge+ using XDA Labs