Hello,
I have a big issue with my i9300. I flashed PDA: I9300UBUGNK1 Brasil version and I decided to root it using CF-Auto-Root-m0-m0xx-gti9300 .
After root the phone was perfectly working, but I uninstalled some pre-installed games which come with that Brasil version from sammobile and after I woke up after several hours I've noticed that there is no signal. In settings > phone info it says BASEBAND VERSION : unknown and IMEI : null.
I tried to flash again, I've flashed different version, nothing can help. The phone is fully functional WIFI works, only no signal, null imei and unknown baseband version. What the heck I can do before smashing it with a hammer?
And I'm talking about home fixes, as I don't have jig & other professional tools
There is no home fix for imei problems, unless you have an efs backup to restore. Take it to a repair centre and pay them to recode it for you, make sure it works on 4.3 before you accept it back.
boomboomer said:
There is no home fix for imei problems, unless you have an efs backup to restore. Take it to a repair centre and pay them to recode it for you, make sure it works on 4.3 before you accept it back.
Click to expand...
Click to collapse
As long as the phone is not bricked there should be a home fix... Hopefully
Nobody??
Managed to make it working using an efs backup from a different phone. Now I have to figure out how to put my correct imei instead of that one
Imei now shows 0049
This thread should be closed, indeed a very friendly and helpful community over here ....
A mod, please close this thread
Stop whining, you got the right answer the same day you asked.
Cloning your phone by using the efs backup from another phone is illegal and won't fix the problem anyway.
boomboomer said:
Stop whining, you got the right answer the same day you asked.
Cloning your phone by using the efs backup from another phone is illegal and won't fix the problem anyway.
Click to expand...
Click to collapse
I didn't wanted to clone another phone and hijack it, please let's remain serious. I just wanted to fix ny efs and that's why I used a backup made from a phone which was broken and was sold by parts.
Now everything was fixed at service
Just a question about k-tool backup
After doing a backup with it I have 2 files
efs.img - 20mb and
efs.tar.gz which has 0 bytes and appear to be damaged as I cannot open it.
Is that efs.img enough in case I lose my imei again after a flash or what?
Hello guys, I had this same problem 2 days ago after flashing the GlamourS4 ROM onto my friend's S3. The flashing failed as it was flashing the modem with an "Assert failed" error, however it still reported that the flashing was successful. On booting the phone it had a null/null IMEI and the baseband was also unknown. I even posted about it on xda.. Yesterday, I found a way to fix both the nul/null IMEI and the unknown baseband. I figured that if I flashed modems onto the phone that the baseband "unknown" message would be fixed, and in the process also fix the IMEI. I therefore searched for patched kernels and modems for it. I came across this page that had patched modems and kernels for the S3 running Android 4.3. I flashed the modems and kernels found on the page with CWM 6.0.4.7 one by one. I went through 6 zipped files before the seventh one fixed my IMEI null/null and baseband "unknown" errors. The one that fixed it was "Patched_XXEMC2_Modem.zip". The six I tried at first changed the IMEI from null to 0049XXXXXXXXXXXXX/XX. The seventh one fixed both problems well. IMEI is well now and the baseband is too. Try flashing the kernels and your phone shall be OK like mine.
Null or 0044....... imei, only repair on service with box and tools... In Serbia, cost 10 euro. Good luck
Sent from my GT-I9300 using XDA Free mobile app
Related
Hi. I recently had some trouble with ROMs, and had to reflash CF-Root with Odin. Now I don't have any signal anymore. Flashed a new kernel, ROM and new modem, and I still can't connect to a network. I can find available networks, however, just not connect to them. Does anyone know the problem? Possibly a broken EFS? I did create backups of my EFS, both by copying the folder to my SD card and with an app. I think I used kTool as that app, but I am not completely sure. I'm a bit afraid to restore it with kTool, though. It says it is dangerous in red letters.
Just restore it with ktool. You can't get in a worse position I mean you're already up for warranty claim if you don't try
Sent from my maguro using Tapatalk 2
It still isn't working. Maybe I should manually move the EFS folder that I backed up? I also used root explorer to copy it, but root explorer says that / is read only.
Did you reboot? Hit the little R/W button up the top for root explorer to be able to paste it.
On another note can you go to setting>about device>status
Can you see an imei number
Sent from my maguro using Tapatalk 2
Is your IMEI correct .
As you have flashed multiple stuff why not flash the correct stock rom for your location and network .Making sure the modem is the right one .
Have you entered your network connections .
Is your Sim Card faulty .
jje
I never removed my SIM card, it shouldn't be faulty. I do see an IMEI number, but how do I know if it is correct?
Amanoo said:
I never removed my SIM card, it shouldn't be faulty. I do see an IMEI number, but how do I know if it is correct?
Click to expand...
Click to collapse
Its on the box >>> its under the battery might even be on your invoice .
jje
IMEI: ***************, which is the same as on the box
IMEI SV: 01, no idea if this is correct
Your IMEI is correct, but you need remove it from here.
It's personnal information. Lot of people search valid IMEI to repair their wrong one.
Then what could the problem be?
EDIT: Now that I think of it, aroudn this time they would give me my new subscription, maybe my SIM card got invalidated.
You have correct IMEI so you should not try to restore your EFS backup. I think it's not the problem.
You should try to flash your phone with the latest official signed stock ROM available in our country (sammobile.com for firmware download).
Then, check if CSC is correct for your area (dial *#272*yourimei# to do that).
You're ok in regards to your ers check your slim is working in another phone
Sent from my maguro using Tapatalk 2
I have the same problem, i flashed differents roms but nothing, i tried to change kernels, change modems, all wipes, but nothing.....
I think i only have last option....SAT.:banghead:
On monday i'll go to shop and send it.
Enviado desde mi Samsung Galaxy S3.
I have same problem. I upgraded via kies and i was unable to connect to network. I can see my imei, csc, baseband but still have problem.
the only problem i have is i can not see th product code and serial number. I restored NV_data.bak but still no improvement.
I am stuck and out of ideas.
can you see your baseband OP? i had this issue and my imei showed up, along with all other info, but my baseband was unknown, i fixed it by using the EFS pro app and restoring my nv_data with it.
Hey guys, I have a rather weird problem.
After flashing UltimaRom with the thought that I backed my EFS as I usually do, I installed the MGM4 modem.
Turns out my EFS backup was removed the previous day and the new MGM4 modem isnt working for me at all.
My IMEI got changed to 00499010640000 which afaik is a fake IMEI that other people get too.
I tried reverting to my previous modem - XELLA - doesn't work - same IMEI.
I tried http://forum.xda-developers.com/showthread.php?t=2437839 ; I tried flashing a MGM4 VVT 4.1.2 Samsung stock rom and it also failed.
I'm open to your ideas.
P.S is there a way something similar like this (http://forum.xda-developers.com/showthread.php?t=881162) would exist? I searched everywhere to find a similar thread but the method explained there isn't viable for i9300 it seems.
syndbg said:
Hey guys, I have a rather weird problem.
After flashing UltimaRom with the thought that I backed my EFS as I usually do, I installed the MGM4 modem.
Turns out my EFS backup was removed the previous day and the new MGM4 modem isnt working for me at all.
My IMEI got changed to 00499010640000 which afaik is a fake IMEI that other people get too.
I tried reverting to my previous modem - XELLA - doesn't work - same IMEI.
I tried http://forum.xda-developers.com/showthread.php?t=2437839 ; I tried flashing a MGM4 VVT 4.1.2 Samsung stock rom and it also failed.
I'm open to your ideas.
P.S is there a way something similar like this (http://forum.xda-developers.com/showthread.php?t=881162) would exist? I searched everywhere to find a similar thread but the method explained there isn't viable for i9300 it seems.
Click to expand...
Click to collapse
the 0049 IMEI isn't fake. It's a generic code given to such devices with either changed or corrupt efs.
See this thread for more info http://forum.xda-developers.com/showthread.php?t=2393289 there are some methods there that should help you to restore your IMEI.
Take your phone to a service centre paid for repair is the easy way .
jje
syndbg said:
Hey guys, I have a rather weird problem.
After flashing UltimaRom with the thought that I backed my EFS as I usually do, I installed the MGM4 modem.
Turns out my EFS backup was removed the previous day and the new MGM4 modem isnt working for me at all.
My IMEI got changed to 00499010640000 which afaik is a fake IMEI that other people get too.
I tried reverting to my previous modem - XELLA - doesn't work - same IMEI.
I tried http://forum.xda-developers.com/showthread.php?t=2437839 ; I tried flashing a MGM4 VVT 4.1.2 Samsung stock rom and it also failed.
I'm open to your ideas.
P.S is there a way something similar like this (http://forum.xda-developers.com/showthread.php?t=881162) would exist? I searched everywhere to find a similar thread but the method explained there isn't viable for i9300 it seems.
Click to expand...
Click to collapse
If you done have EFS Backup before you upgrade to MG4, you must flash modem to lower release and then restore your previous EFS backup.
As I said, I didn't have my previous EFS backup saved. It got deleted.
And sending it to repair is not an option since the closest repair center is 300km away.
Stick with the mg4 modem.
Reflash ultima, choosing the non-stock kernel option.
Failing that, flash back to full stock mg4.
Failing that, pay for 300km postage
I'm assuming with the above, you've not used "ariza patch". If my assumption is wrong, let me know
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
My brother's SIII Was on android 4.0.4 i updated it to 4.3 with odin everything was fine, i could see the network bars but when i try calling it says "not registered on Network"! I searched the internet for hours and i realized people who had this issue had a problem with their efs partition and a wrong imei is observed; but when i type the imei code everything is fine i don't get a "0000" or "004". I even tried hundreds of roms countless modem files and still nothing! Please i need your help to fix this issue i cannot have this phone spoiled so soon please!!:crying:
wildechap said:
My brother's SIII Was on android 4.0.4 i updated it to 4.3 with odin everything was fine, i could see the network bars but when i try calling it says "not registered on Network"! I searched the internet for hours and i realized people who had this issue had a problem with their efs partition and a wrong imei is observed; but when i type the imei code everything is fine i don't get a "0000" or "004". I even tried hundreds of roms countless modem files and still nothing! Please i need your help to fix this issue i cannot have this phone spoiled so soon please!!:crying:
Click to expand...
Click to collapse
Just restore your backup efs! (Or let me guess you did not back it up)
Seriously though have you used the patched modem mg4 that is floating about I presume you have?
Here is a couple of links to look at >> http://forum.xda-developers.com/galaxy-s3/help/solved-upgrade-to-4-3-network-fixed-t2547450 << >> http://forum.xda-developers.com/showpost.php?p=43946365&postcount=15 <<
Also there is a efs thread I suggest posting your question in there.
Thank you but i had to downgrade back to 4.0.4 before applying the XEMG4. I also wish to know what causes this and if i am condemned to stay on 4.0.4?
Your efs folder is corrupted or incompatible with later firmwares that require efs v2. Only solution is restore a backup or a competent repair.
Sent from my GT-I9300 using Tapatalk
Hi, sorry if this has been answered, but I can't find it.
I recently combined two broken i9300's (one with a bricked motherboard (gets into download mode, product name blank, think it's SDS), the other with a smashed screen) by transferring the motherboard from the smashed one to the other.
It seemed to work fine for a while, but after a week the phone lost signal, showing no service. Rebooting the phone fixed this, however this has now been happening more and more often, and now doesn't have any service even after booting.
Does anyone know what the problem could be, and how to fix it?
Thanks.
EDIT: I managed to restore service again by flashing the stock ROM through Odin (was running stock already), but it lost it again after a few hours.
pnz said:
Hi, sorry if this has been answered, but I can't find it.
I recently combined two broken i9300's (one with a bricked motherboard (gets into download mode, product name blank, think it's SDS), the other with a smashed screen) by transferring the motherboard from the smashed one to the other.
It seemed to work fine for a while, but after a week the phone lost signal, showing no service. Rebooting the phone fixed this, however this has now been happening more and more often, and now doesn't have any service even after booting.
Does anyone know what the problem could be, and how to fix it?
Thanks.
EDIT: I managed to restore service again by flashing the stock ROM through Odin (was running stock already), but it lost it again after a few hours.
Click to expand...
Click to collapse
Check IMEI and serial if corrupted. If it shows your correct IMEI and serial then it's fine. Otherwise you may have an EFS problem.
Report back please.
Benko111 said:
Check IMEI and serial if corrupted. If it shows your correct IMEI and serial then it's fine. Otherwise you may have an EFS problem.
Report back please.
Click to expand...
Click to collapse
IMEI and serial are both fine (non-zero and non-null anyway). IMEI matches the label from the smashed phone. However, it's connected at the moment (just re-flashed the stock ROM again). Will update again the next time it loses service.
EDIT: Just lost service again. Only took about 10 minutes after flashing. IMEI and serial are still fine. I also forgot to mention that the motherboard I'm using is from a New Zealand phone, whereas the casing/screen is from a French phone. Don't know if that makes a difference. I tried flashing a French stock ROM, but that gave me an unknown baseband and null IMEI. Flashing the NZ ROM again fixed that.
EDIT2: And another correction. IMEI and serial showed fine after losing service, but I then rebooted the phone. Still no service, baseband is now unknown, IMEI is null and the serial number is non-zero but different than it was. However, I'm sure if I reflashed the ROM again I'd have service for a few minutes, so it doesn't seem like the EFS is entirely corrupt. I'm scratching my head a bit at this one.
pnz said:
IMEI and serial are both fine (non-zero and non-null anyway). IMEI matches the label from the smashed phone. However, it's connected at the moment (just re-flashed the stock ROM again). Will update again the next time it loses service.
EDIT: Just lost service again. Only took about 10 minutes after flashing. IMEI and serial are still fine. I also forgot to mention that the motherboard I'm using is from a New Zealand phone, whereas the casing/screen is from a French phone. Don't know if that makes a difference. I tried flashing a French stock ROM, but that gave me an unknown baseband and null IMEI. Flashing the NZ ROM again fixed that.
Click to expand...
Click to collapse
Judging from your last two sentences you actally have got an EFS problem. Just to clarify: you get generic IMEI & serial with every other ROM you flashed besides the original NZ stock?
Otherwise it might just be the modem not fitting the ROM, try another (if possible original 3-part stock firmware), but make a Nandroid backup or save your EFS otherwise in case you need it later.
Benko111 said:
Judging from your last two sentences you actally have got an EFS problem. Just to clarify: you get generic IMEI & serial with every other ROM you flashed besides the original NZ stock?
Otherwise it might just be the modem not fitting the ROM, try another (if possible original 3-part stock firmware), but make a Nandroid backup or save your EFS otherwise in case you need it later.
Click to expand...
Click to collapse
Not generic IMEI but null IMEI. Not sure about generic serial, not sure how to tell the difference. And I'm now seeing the same on the NZ stock firmware after a reboot.
Is a Philz Touch EFS backup sufficient? Anything else I should backup as well?
Well, since EFS is broken already it should be sufficient. To be on the safe site you can additionally save the EFS folder with Root Explorer.
If you have a working EFS you would need to save it with an EFS saving tool like 'Samsung Tool' in this forum somewhere.
Then you got to go through the EFS threads for i9300 and hope to be able to fix this.
Benko111 said:
Well, since EFS is broken already it should be sufficient. To be on the safe site you can additionally save the EFS folder with Root Explorer.
If you have a working EFS you would need to save it with an EFS saving tool like 'Samsung Tool' in this forum somewhere.
Then you got to go through the EFS threads for i9300 and hope to be able to fix this.
Click to expand...
Click to collapse
I've already gone through all the EFS threads I could find. Haven't seen anyone with the same problem (sometimes it works, briefly, then it stops). Everyone else with the baseband unknown, IMEI null/null problem seems to have that all the time. Was hoping someone would be able to tell me what's different with mine.
pnz said:
I've already gone through all the EFS threads I could find. Haven't seen anyone with the same problem (sometimes it works, briefly, then it stops). Everyone else with the baseband unknown, IMEI null/null problem seems to have that all the time. Was hoping someone would be able to tell me what's different with mine.
Click to expand...
Click to collapse
How should anybody know from the distance? We can just give hints and point you into directions, now you've got to read & google and if you're
persistent enough you will solve your problem - as long as it's not hardware related.
Another great but a bit chaotic resource:
http://forum.gsmhosting.com/vbb/
Benko111 said:
How should anybody know from the distance? We can just give hints and point you into directions, now you've got to read & google and if you're
persistent enough you will solve your problem - as long as it's not hardware related.
Another great but a bit chaotic resource:
http://forum.gsmhosting.com/vbb/
Click to expand...
Click to collapse
Sorry, just meant that I thought somebody might have seen this exact problem before.
I think I've solved this. Used the repair NV data option (to fix broken baseband) in EFS Professional, and it seems to be working fine. Will see if it's still working after a few days though.
My best guess is that this was a file permissions error.
pnz said:
I think I've solved this. Used the repair NV data option (to fix broken baseband) in EFS Professional, and it seems to be working fine. Will see if it's still working after a few days though.
My best guess is that this was a file permissions error.
Click to expand...
Click to collapse
No, not fixed. Worked fine for a few days then the problem came back. Just tried a non-stock ROM (Omega) and same thing. Trying a CM-based ROM now (ParanoidAndroid), but not too hopeful.
Still don't understand why it works for hours/days, then suddenly stops. Rebooting it fixes it the first few times, then that stops working as well (and I get baseband unknown at this point). Flashing a new ROM always fixes it, for a few hours/days anyway.
Sounds like a hardware issue, possibly nand memory becoming corrupt hence why it works for a while on a fresh install.
Sent from my GT-I9300 using Tapatalk
boomboomer said:
Sounds like a hardware issue, possibly nand memory becoming corrupt hence why it works for a while on a fresh install.
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
Any workarounds you can suggest? Just had the problem happen again on cyanogenmod, so that didn't fix it.
Try reading the freezing thread in general forum, see if the memory test tool will compete after a full wipe and fresh install of a stock firmware.
Other than that only a new motherboard, as the emmc chip is damaged.
I have a I9300 that is not getting any network, the IMEI is 0049... and the serial number is a string of zeros. It was previously running stock 4.1.2 but I wanted to upgrade to at least the latest official ROM - 4.3 and thats how I ended up in this situation.
I've been a Linux user forever and I've owned and flashed a few Android phones in the past but this is my first Samsung Android handset and so the first time I've been bitten by efs. I did lots of reading before attempting the upgrade so I knew to backup the efs partition before doing any flashing. I did this with ktool but restoring my efs backup to various ROMs hasn't restored my network connectivity.
I'm on the 3 network in the UK so when I've been using Odin to restore stock ROMs (I've tried restoring both 4.3 and 4.1.2) I've been using the BTU versions ie
I9300XXUGMK6_I9300OXAGMK6_BTU
I9300XXEMG4_I9300OXAEMG4_BTU
I have now spent four full days reading and trying various solutions suggested in an array of threads on this forum, I've read all the stickies in http://forum.xda-developers.com/galaxy-s3/general/samsung-galaxy-s3-sticky-roll-thread-t2344125 plus many more threads and now I've just about given up. I've tried flashing various unofficial ROMs too like CM 10.2, 11 and RevolutionS5 but they all have no network.
My phone is not in factory mode and I've tried zuluman's patched kernel/modem with 4.3 without any luck. I've tried factory resets, deleting /efs, changing the permissions of and editing nv_data.bin with a hex editor amongst other tricks. No go.
So it seems my only remaining option is to take / send my phone to be repaired or fork out for one of these hardware devices that claim to be able to repair IMEI issues. Problem is then I'm back to square one, I've not learned what I wanted to about my phone (how to safely reflash/upgrade it) and I'll be stuck on whatever the repair shop leave me with.
I'd much, much rather fix this myself as then that opens the doors to experimentation, it will prolong the (so far all too brief) life of my phone and be much more satisfying. Until now I thought the SGS3 was (is?) a class phone and I think its much better than the Nexus 4 I had previously, despite inferior specs in many respects.
I'm sure its possible to recover from this without buying dedicated hardware or at least it should be..
I bought my phone 2nd hand less than three months ago but its no longer under any warranty. Another thing that could be an issue is that I was sold it without a box and there is no IMEI printed under or on the battery.
Thanks for your help!
It would seem from my experimentation that reflashing stock ROMs with Odin on the I9300 doesn't affect the efs partition, or at least the stock ROMs I've been flashing don't repair/recreate efs.
I'd be perfectly happy using the Samsung generic IMEI if it will let me connect to my phone network. If anyone knows how might enable that, please speak up!
Same problem encountered before until now...
This are when the problem starts.
My GS3 International had CynagenMod stable build.
1. I've noticed one morning that my GS3 is stuck in a bootloop.
2. Tried reflashing the stable CM ROM, but still stuck n the bootloop.
3. Tried flashing my stock rooted firmware from my TWRP backup.
- after this, I've noticed that only emergency calls and not registered on network always appears.
- my IMEI becomes now generic with 0049...00 but with serial number.
4. Tried sending it for repair in our local cellphone repair shop. Network signal is fixed now but it always ask for permission for the radio. So battery drain is massive.
5. I didn't send it back. Tried to fix it myself. Installed the stock firmware 4.3 using jellybean. To my surprise, the IMEI and serial number comes back. But still no network signal (emergency calls only).
Lastly, still looking for a fix. If anyone had a fix for this one this will be a great help. Also tried restoring/updating through Kies. All the process I took had failed.
Not sure if the problem was the EFS/IMEI or the modem or radio install from the firmware I just installed.
For now, I'm using the stock 4.3 firmware. The only problem now is the network signal. Any suggestions or fix is a great help. TIA!
I have read of people fixing the no network by flashing a known good efs image but I suppose it would have to contain a working generic IMEI. Please PM me if you have such an image for a i9300. I'll have to find such a thread again and get PM'ing.
I've been disappointed by a few things in trying to upgrade my SGS3.
* There is no well documented fix for this EFS/IMEI/no network issue
* This issue seems to be very common for SGS3 owners who have attempted an upgrade to 4.3 or flashing alternate ROMs yet there is no mention of any of this on
http://wiki.cyanogenmod.org/w/Known_Issues_page_for_i9300
and
http://wiki.cyanogenmod.org/w/SGS3FAQ
There needs to be.
* It doesn't seem Heimdall is able to flash a tar.md5 in one hit like Odin can which is a shame for us Linux and OSX users
Great phone but not for hackers and tweakers it seems.
Sounds like the efs was already corrupt before you tried the upgrade, probably a previous botched repair which only worked on 4.1
Take it to a repair centre and pay for them to recode it for you, there is no other fix. Make sure it connects on 4.3 before you pay.
Suggestion: flash a firmware older than MG4 and let it update OTA or by KIES. Generating the efs-v2-data may solve.
the battle rages on...
rp158:
That sounded like a good suggestion to me so I used Odin to install I9300XXELL4_I9300OXAELL4_BTU, which predates MG4. Because the aim was to try an OTA update, I did not root or flash a custom recovery as I know they don't like that.
Like all the ROMs I've tried since my prob, it installed fine but I get no network. After connecting to wifi I first tried OTA via Settings -> About Device -> Software update -> Update but it just says "Failed to update firmware due to network or server problem". I can browse the internet fine so could this be a problem with Three (my telco)? I've heard of some providers blocking OTA.
So next I tried Kies (not Kies 3) under Windows 8. I went to Tools -> Firmware Upgrade and Initialisation but I just get the error 'GT-I9300 does not support initialising'. Fail, fail and fail!
I've yet to run 'Triangle away' and so I have several flash count points listed on the download screen. Could this stop OTA from working? Is there a limit to the number of flashes you can perform before something nasty happens? I presume its just something retailers check before they refund or repair phones.
Something else I noticed while fighting my phone today was that recovery says the CSC code is now KOR. Could that stop OTA working?
Likes me a good idea to run 'Triangle away': I think there is no max. count for flashes, but perhaps counter>0 and status=custom block the update-procedure. So try after unroot both methods again. (CSC-code I down't know.)
Whilst still running I9300XXELL4_I9300OXAELL4_BTU, I rooted it then successfully ran Triangle Away to clear the flash counter before running csc changer to change my CSC to BTU (from KOR). I would've changed it to XEU but that wasn't an option. I checked that worked fine, which it did, and running CSC changer also (conveniently, in my case) un-roots your phone.
After that I tried updating via both Kies and 'About Device' software update but both just gave me the same errors as before so scratch another idea off my very long list then.
Then go to #5
rp158 said:
Then go to #5
Click to expand...
Click to collapse
?
Do you mean Odin flash I9300XXEMB5, which I think is the last release before MG4?
pfmdan said:
?
Click to expand...
Click to collapse
Sorry, too short. Post 5 = repair by Samsung.
So, if I choose to get my phone fixed, has this proven that I will be unable to flash any alternate ROMs on it without losing my network/IMEI/serial again?
Maybe I should've backed up my EFS with philz recovery or dd insteal of ktool, then I might not have ended up in this situation?
Maybe the US/Qualcomm models of the S3 are safe to flash with alternate ROMS whilst the Exynos-based models aren't?
Can anyone recommend a good repair service in the UK if my local repair shops can't help?
Thanks for your suggestions rp158!
pfmdan said:
So, if I choose to get my phone fixed, has this proven that I will be unable to flash any alternate ROMs on it without losing my network/IMEI/serial again?
Click to expand...
Click to collapse
No, that's unnormal. But read before flashing, what users say (some beta's or nightlies are buggy).
Maybe I should've backed up my EFS with philz recovery or dd insteal of ktool, then I might not have ended up in this situation?
Click to expand...
Click to collapse
Probably. I suggest Philz, TWRP or by TerminalEmulator.
Can anyone recommend a good repair service in the UK if my local repair shops can't help?
Click to expand...
Click to collapse
Official Samsung repair-service.
I thought Philz was the only recovery that gave you the option of backing up EFS? I didn't think TWR supported EFS backup/restore? CWM doesn't.
TWRP can, of course.
A corrupted efs can also effect the stability and use of wifi as mac address etc is also stored there.
Check if there is a backup of your efs. Some roms make a backup of it also - neatrom for example. Try flashing xxemg4 or later baseband to see if it fixes it because after having the later bb you also have efs v2
FIXED
Thanks to everyone who made suggestions in trying to get my phones connection back. Its working again now. My 0049 IMEI has gone, my real IMEI come back and my serial number has returned so I can make and receive calls again!
The thing that was preventing my connection and leaving me to suffer the dreaded 'Emergency Calls Only' and 'Not registered on network' errors was nothing to do with EFS but because I had an incorrect CSC. I had flashed stock BTU roms instead of H3G, which is what I should've used being on Three. As soon as I flashed a rom with the correct CSC, my IMEI and serial numbers both returned and this allowed the zuluman patched modem / kernel combo to work. I'm now happily running 4.3 whereas I was previously on a rooted stock 4.1.2.
There are literally 100's of threads on the S3 forums here with S3 owners ending up with a generic IMEI and no serial after attempting a 4.3 upgrade and the standard response is nearly always 'your EFS is probably corrupt' or 'your EFS in the wrong format'. That will be the case sometimes but I'd bet that more often than not the EFS is fine (if updated) and users have flashed a CSC for the wrong region for their telephone network.
Key tools in getting this prob fixed that hardly get any mention are the csc changer app (downloadable via Play but requires root and also factory resets/unroots when run) and A.S_id's rescue firmware
http://forum.xda-developers.com/galaxy-s3/general/odinfirmware-sgsiii-i9300-prerooted-t1825272/
I'd recommend I9300 users flash A.S._id's ROM if they can't find a firmware with the correct CSC for their network and/or csc changer doesn't restore their IMEI and serial.
Lets fix these forums by getting this info into the FAQs in both the general and QA stickies because I know it to be missing hence the endless invalid IMEI / no network postings.
I'll be back shortly wth more details and suggested additions to the S3 FAQs / stickies.
Thanks all!
I've ended up running A.S._id's 4.3 deodexed 'stock' ROM w/ Boeffla 5.3 kernel and zuluman's patched XXUGMK6 modem.
When I used zuluman's patched XXUGMK6 kernel, I would experience small but frequent glitches in 3G streamed audio. I don't have this problem with Boeffla 5.3.
I'd also highly recommend stock TW users turn off smart screen to massively increase your battery life very easily.