Hello~
First of all I know that this has probably been asked before but bear with me please ^_^
I flashed a kernel on my GT-i9505.
It caused a whole bunch of FC on Google Framework Service and other key services.
Anywho I decided to restore the backup I made before flashing the kernel.
It stopped the FC but now I have no baseband, IMEI, IMEI SV or Phone number and I cannot connect to any mobile network as it does not detect my SIM.
I tried restoring my EFS backup in CWM and flashing the modem.tar and modem.bin in mobile odin, still with no success.
Short of re flashing my ROM what can I do to fix this.
It's stock Sammy TW 4.3 rom with root.l and I still have WiFi access.
Also on an unrelated note, how do I install custom boot animations? Any I try show up with a black screen. Weird.
Anywho if anyone can help I would be most appreciative~~!
Thankie in advance.
Sent from my GT-I9505 using Tapatalk
Related
Hey guys, few months ago I got the not registered on network issue after flashing 4.2.2 firmware
I think it changed the efs to v2 and is not compatible with italian modem firmwares.
so I tried:
- ariza patch, kernel and custom baseband modem
- odin flash with some old and new firmware
- kies initialize
- downgrade to 4.1.2 and update via kies
- flash modems
now...is out there a fu%&£*g genius that has another suggestion? lol
my imei is ok
Efs corruption is the usual cause of network connection issues, unless you have a backup then you will need an expert repair -to wipe the efs, flash a blank then code your imei and serial number back in.
Sent from my GT-I9300 using Tapatalk
i actually had this just today too. read somewhere in google the following, and it worked for me.
flash an aroma rom (i chose stock archi), tick the flash modem option in the custom install settings.
once flashed i got my data and carrier back. hope that works for you too
Hi guys, I must have read a hundred posts about this issue to no avail.
I recently rooted an old S3 GT I9300 using CF-Auto-Root and Odin. I was sure I backed up the EFS folder, but it would appear I didnt. Now I am runnning the Paranoid Android 3.0 ROM on the device with absolutley no mobile network/signal and although i have the IMEI written down the S/N seems to have changed to a generic 15 digit number as opposed to the original RCF**** or whatever it should be.
Ive tried Kies and re-installing a stock ROM which is both hard to get hold of and doesnt seem to want to unzip from CWM Recovery even after cl;earing the Caches and doing a factory reset. I've also tried re-writting the bin file using a hex code app and terminal with no luck, and EFS Pro only seems to make me think ive restored the EFS by backing up the already corrupt one and restoring that....
It is possible to rectify my EFS issue (nv_data.bin file I assume) with only a written down IMEI and no serial?? if so please advise... as Im seriously stuck and although ive considered using a friends efs folder im sure this is probably illegal...
HELP, Thankyou
oh..and...
It occurs to me that the guy to talk to is spocky12, yet i have yet to pm him pending your advice.... thankyou for any help i may receive..
Hi im also in the same position ive tried loads of stock roms for the UK as thats where i am... to no avail ive tried the original 4.0.1 rom all the way up to the latest 4.4.2 rom and each time the imei number is 0000999......... ive tried modem patches most of which are from looking through the xda site but nothing seems to work.... i could never back the efs up as when i had the phone it was in a constant loop so never knew which software/modem/firm it actually had on it as i could not get past the samsung logo. but since i have flashed latest android for the phone it will boot in fine just wont connect to a network and imei number is wrong ive been days trying to figure this out :crying::crying: Please Help!
dejay89 said:
Hi im also in the same position ive tried loads of stock roms for the UK as thats where i am... to no avail ive tried the original 4.0.1 rom all the way up to the latest 4.4.2 rom and each time the imei number is 0000999......... ive tried modem patches most of which are from looking through the xda site but nothing seems to work.... i could never back the efs up as when i had the phone it was in a constant loop so never knew which software/modem/firm it actually had on it as i could not get past the samsung logo. but since i have flashed latest android for the phone it will boot in fine just wont connect to a network and imei number is wrong ive been days trying to figure this out :crying::crying: Please Help!
Click to expand...
Click to collapse
Hi Dejay, its good to know im not the only one. have you tried using the Kies program to reinstall stock firmware, did that change anything? Also not sure if you tried this http://www.youtube.com/watch?v=JqLK_2I-SBM method but it didnt work for me, the HEx lines he refers to dont exist in my nv-data.bin.
Coincidentally, thats exactly how i acquired this issue, it stopped booting so i factory reset deviced, then backedup and rooted, then installed custom ROM and somehow lost backed up /efs .Im now showing an 000049 IMEI and tried modem patches, stock roms etc. and no luck. my serials all messed up too and i cant connect to any form of mobile network.
I just changed ROM again as i couldnt get the right Gapps to flash with Paranoid Android Rom 3.0 - now flashing Dirty Unicorns v3.8 from here and all working beautifully except no signal, wrong IMEI and S/N - I am by no means a PRO at all this and so im rather stuck like yourself..
Hopefully we'll be saved?!
I have a I9300 that is not getting any network, the IMEI is 0049... and the serial number is a string of zeros. It was previously running stock 4.1.2 but I wanted to upgrade to at least the latest official ROM - 4.3 and thats how I ended up in this situation.
I've been a Linux user forever and I've owned and flashed a few Android phones in the past but this is my first Samsung Android handset and so the first time I've been bitten by efs. I did lots of reading before attempting the upgrade so I knew to backup the efs partition before doing any flashing. I did this with ktool but restoring my efs backup to various ROMs hasn't restored my network connectivity.
I'm on the 3 network in the UK so when I've been using Odin to restore stock ROMs (I've tried restoring both 4.3 and 4.1.2) I've been using the BTU versions ie
I9300XXUGMK6_I9300OXAGMK6_BTU
I9300XXEMG4_I9300OXAEMG4_BTU
I have now spent four full days reading and trying various solutions suggested in an array of threads on this forum, I've read all the stickies in http://forum.xda-developers.com/galaxy-s3/general/samsung-galaxy-s3-sticky-roll-thread-t2344125 plus many more threads and now I've just about given up. I've tried flashing various unofficial ROMs too like CM 10.2, 11 and RevolutionS5 but they all have no network.
My phone is not in factory mode and I've tried zuluman's patched kernel/modem with 4.3 without any luck. I've tried factory resets, deleting /efs, changing the permissions of and editing nv_data.bin with a hex editor amongst other tricks. No go.
So it seems my only remaining option is to take / send my phone to be repaired or fork out for one of these hardware devices that claim to be able to repair IMEI issues. Problem is then I'm back to square one, I've not learned what I wanted to about my phone (how to safely reflash/upgrade it) and I'll be stuck on whatever the repair shop leave me with.
I'd much, much rather fix this myself as then that opens the doors to experimentation, it will prolong the (so far all too brief) life of my phone and be much more satisfying. Until now I thought the SGS3 was (is?) a class phone and I think its much better than the Nexus 4 I had previously, despite inferior specs in many respects.
I'm sure its possible to recover from this without buying dedicated hardware or at least it should be..
I bought my phone 2nd hand less than three months ago but its no longer under any warranty. Another thing that could be an issue is that I was sold it without a box and there is no IMEI printed under or on the battery.
Thanks for your help!
It would seem from my experimentation that reflashing stock ROMs with Odin on the I9300 doesn't affect the efs partition, or at least the stock ROMs I've been flashing don't repair/recreate efs.
I'd be perfectly happy using the Samsung generic IMEI if it will let me connect to my phone network. If anyone knows how might enable that, please speak up!
Same problem encountered before until now...
This are when the problem starts.
My GS3 International had CynagenMod stable build.
1. I've noticed one morning that my GS3 is stuck in a bootloop.
2. Tried reflashing the stable CM ROM, but still stuck n the bootloop.
3. Tried flashing my stock rooted firmware from my TWRP backup.
- after this, I've noticed that only emergency calls and not registered on network always appears.
- my IMEI becomes now generic with 0049...00 but with serial number.
4. Tried sending it for repair in our local cellphone repair shop. Network signal is fixed now but it always ask for permission for the radio. So battery drain is massive.
5. I didn't send it back. Tried to fix it myself. Installed the stock firmware 4.3 using jellybean. To my surprise, the IMEI and serial number comes back. But still no network signal (emergency calls only).
Lastly, still looking for a fix. If anyone had a fix for this one this will be a great help. Also tried restoring/updating through Kies. All the process I took had failed.
Not sure if the problem was the EFS/IMEI or the modem or radio install from the firmware I just installed.
For now, I'm using the stock 4.3 firmware. The only problem now is the network signal. Any suggestions or fix is a great help. TIA!
I have read of people fixing the no network by flashing a known good efs image but I suppose it would have to contain a working generic IMEI. Please PM me if you have such an image for a i9300. I'll have to find such a thread again and get PM'ing.
I've been disappointed by a few things in trying to upgrade my SGS3.
* There is no well documented fix for this EFS/IMEI/no network issue
* This issue seems to be very common for SGS3 owners who have attempted an upgrade to 4.3 or flashing alternate ROMs yet there is no mention of any of this on
http://wiki.cyanogenmod.org/w/Known_Issues_page_for_i9300
and
http://wiki.cyanogenmod.org/w/SGS3FAQ
There needs to be.
* It doesn't seem Heimdall is able to flash a tar.md5 in one hit like Odin can which is a shame for us Linux and OSX users
Great phone but not for hackers and tweakers it seems.
Sounds like the efs was already corrupt before you tried the upgrade, probably a previous botched repair which only worked on 4.1
Take it to a repair centre and pay for them to recode it for you, there is no other fix. Make sure it connects on 4.3 before you pay.
Suggestion: flash a firmware older than MG4 and let it update OTA or by KIES. Generating the efs-v2-data may solve.
the battle rages on...
rp158:
That sounded like a good suggestion to me so I used Odin to install I9300XXELL4_I9300OXAELL4_BTU, which predates MG4. Because the aim was to try an OTA update, I did not root or flash a custom recovery as I know they don't like that.
Like all the ROMs I've tried since my prob, it installed fine but I get no network. After connecting to wifi I first tried OTA via Settings -> About Device -> Software update -> Update but it just says "Failed to update firmware due to network or server problem". I can browse the internet fine so could this be a problem with Three (my telco)? I've heard of some providers blocking OTA.
So next I tried Kies (not Kies 3) under Windows 8. I went to Tools -> Firmware Upgrade and Initialisation but I just get the error 'GT-I9300 does not support initialising'. Fail, fail and fail!
I've yet to run 'Triangle away' and so I have several flash count points listed on the download screen. Could this stop OTA from working? Is there a limit to the number of flashes you can perform before something nasty happens? I presume its just something retailers check before they refund or repair phones.
Something else I noticed while fighting my phone today was that recovery says the CSC code is now KOR. Could that stop OTA working?
Likes me a good idea to run 'Triangle away': I think there is no max. count for flashes, but perhaps counter>0 and status=custom block the update-procedure. So try after unroot both methods again. (CSC-code I down't know.)
Whilst still running I9300XXELL4_I9300OXAELL4_BTU, I rooted it then successfully ran Triangle Away to clear the flash counter before running csc changer to change my CSC to BTU (from KOR). I would've changed it to XEU but that wasn't an option. I checked that worked fine, which it did, and running CSC changer also (conveniently, in my case) un-roots your phone.
After that I tried updating via both Kies and 'About Device' software update but both just gave me the same errors as before so scratch another idea off my very long list then.
Then go to #5
rp158 said:
Then go to #5
Click to expand...
Click to collapse
?
Do you mean Odin flash I9300XXEMB5, which I think is the last release before MG4?
pfmdan said:
?
Click to expand...
Click to collapse
Sorry, too short. Post 5 = repair by Samsung.
So, if I choose to get my phone fixed, has this proven that I will be unable to flash any alternate ROMs on it without losing my network/IMEI/serial again?
Maybe I should've backed up my EFS with philz recovery or dd insteal of ktool, then I might not have ended up in this situation?
Maybe the US/Qualcomm models of the S3 are safe to flash with alternate ROMS whilst the Exynos-based models aren't?
Can anyone recommend a good repair service in the UK if my local repair shops can't help?
Thanks for your suggestions rp158!
pfmdan said:
So, if I choose to get my phone fixed, has this proven that I will be unable to flash any alternate ROMs on it without losing my network/IMEI/serial again?
Click to expand...
Click to collapse
No, that's unnormal. But read before flashing, what users say (some beta's or nightlies are buggy).
Maybe I should've backed up my EFS with philz recovery or dd insteal of ktool, then I might not have ended up in this situation?
Click to expand...
Click to collapse
Probably. I suggest Philz, TWRP or by TerminalEmulator.
Can anyone recommend a good repair service in the UK if my local repair shops can't help?
Click to expand...
Click to collapse
Official Samsung repair-service.
I thought Philz was the only recovery that gave you the option of backing up EFS? I didn't think TWR supported EFS backup/restore? CWM doesn't.
TWRP can, of course.
A corrupted efs can also effect the stability and use of wifi as mac address etc is also stored there.
Check if there is a backup of your efs. Some roms make a backup of it also - neatrom for example. Try flashing xxemg4 or later baseband to see if it fixes it because after having the later bb you also have efs v2
FIXED
Thanks to everyone who made suggestions in trying to get my phones connection back. Its working again now. My 0049 IMEI has gone, my real IMEI come back and my serial number has returned so I can make and receive calls again!
The thing that was preventing my connection and leaving me to suffer the dreaded 'Emergency Calls Only' and 'Not registered on network' errors was nothing to do with EFS but because I had an incorrect CSC. I had flashed stock BTU roms instead of H3G, which is what I should've used being on Three. As soon as I flashed a rom with the correct CSC, my IMEI and serial numbers both returned and this allowed the zuluman patched modem / kernel combo to work. I'm now happily running 4.3 whereas I was previously on a rooted stock 4.1.2.
There are literally 100's of threads on the S3 forums here with S3 owners ending up with a generic IMEI and no serial after attempting a 4.3 upgrade and the standard response is nearly always 'your EFS is probably corrupt' or 'your EFS in the wrong format'. That will be the case sometimes but I'd bet that more often than not the EFS is fine (if updated) and users have flashed a CSC for the wrong region for their telephone network.
Key tools in getting this prob fixed that hardly get any mention are the csc changer app (downloadable via Play but requires root and also factory resets/unroots when run) and A.S_id's rescue firmware
http://forum.xda-developers.com/galaxy-s3/general/odinfirmware-sgsiii-i9300-prerooted-t1825272/
I'd recommend I9300 users flash A.S._id's ROM if they can't find a firmware with the correct CSC for their network and/or csc changer doesn't restore their IMEI and serial.
Lets fix these forums by getting this info into the FAQs in both the general and QA stickies because I know it to be missing hence the endless invalid IMEI / no network postings.
I'll be back shortly wth more details and suggested additions to the S3 FAQs / stickies.
Thanks all!
I've ended up running A.S._id's 4.3 deodexed 'stock' ROM w/ Boeffla 5.3 kernel and zuluman's patched XXUGMK6 modem.
When I used zuluman's patched XXUGMK6 kernel, I would experience small but frequent glitches in 3G streamed audio. I don't have this problem with Boeffla 5.3.
I'd also highly recommend stock TW users turn off smart screen to massively increase your battery life very easily.
Hey i have a problem my nerwork always give me emergency call only i tried all fix from xda but nothing sloved im back to 4.3 from 4.4.2 ana backup the efs and flash via odin in 4.4.2 still same problem any solution plz help
tareq-hakeem said:
Hey i have a problem my nerwork always give me emergency call only i tried all fix from xda but nothing sloved im back to 4.3 from 4.4.2 ana backup the efs and flash via odin in 4.4.2 still same problem any solution plz help
Click to expand...
Click to collapse
Depends on what you have tried more details/list of what you have tried "all fix" doesn't really help. If not you will get lots of replies from people suggesting things you have already done.
There is what i did:
-Try alot of patched modem
-flash 4.3 stock backup efs then restore in 4.4.2
-tried different custom rom
-changed csc to be compitable with my country BTW i live in middle east
And another thing i select my network manually
tareq-hakeem said:
There is what i did:
-Try alot of patched modem
-flash 4.3 stock backup efs then restore in 4.4.2
-tried different custom rom
-changed csc to be compitable with my country BTW i live in middle east
Click to expand...
Click to collapse
Looks like you have tried all the obvious solutions sorry I can't understand your first post about 4.3 have you connectivity on 4.3 stock rom?
Yes and in 4.4.2 but i get random emergency call only and still no connectivity must restart phone to get network back
tareq-hakeem said:
Yes and in 4.4.2 but i get random emergency call only and still no connectivity must restart phone to get network back
Click to expand...
Click to collapse
If you are getting network/calls in 4.3 without any problems then your efs and modem are correct and have been upgraded to efs v2 unless you are on a patched modem and this is what is making your 4.3 rom work . If you are getting partial calls/internet in 4.4.2 but then have to reboot then something else is going on.Are you sure your apn settings are correct for you region? If they are then I am at a loss to what's going on,the patched modems and kernels that are in the forum are for 4.3 roms only not 4.4 so are you on a patched modem and kernel at the moment?maybe that's interfering with 4.4.
Try another sim card.
Thx for help still happening to me
If this error is happening on totally stock 4.3, before you install or restore any settings or apps, but works normally sometimes then it's probably a hardware failure.
Now im using back to noot v5 it seem the problem is fixed i donno
Hello everyone,
First of all i want to thank you for all this guides that i was trying to use here
So here's my story.
I got Samsung Galaxy S3 I9300 with bootloop issue so i decide to fix this by myself.
I was trying to install fimware using KIES but i doesn't fix my issue.
Then i was trying to search for right rom on several websites.
The right one and only working one was 4.0.4 with orange brand logo.
So i was excited that its finally working
Then i realize that my imei is null and my sim card is not working.
So i was trying to restore EFS using several tools and methods.
Finally i got it default IMEI 0049 but it was still not working.
My phone is not qualcomm based model so i cannot use nv item reader writer as it's required to edit IMEI
Even after applying phonutil patch my device is not being recognize as Qualcomm one.(because it's not)
So i was still looking for another way to change my imei manually as i have my original one on the box and under battery.
Finally I realized that i cannot make even Emergency calls it comes with message Out of service area.
So i was trying to apply few modem and radio updates to my phone but none of them are helping.
Anyone have similiar issue?
I have another Galaxy S3 that is working can i copy imei or whole system to my not working phone?
I know that after that i cannot use other device, but thats ok if its possible.
Rockafella71 said:
Hello everyone,
First of all i want to thank you for all this guides that i was trying to use here
So here's my story.
I got Samsung Galaxy S3 I9300 with bootloop issue so i decide to fix this by myself.
I was trying to install fimware using KIES but i doesn't fix my issue.
Then i was trying to search for right rom on several websites.
The right one and only working one was 4.0.4 with orange brand logo.
So i was excited that its finally working
Then i realize that my imei is null and my sim card is not working.
So i was trying to restore EFS using several tools and methods.
Finally i got it default IMEI 0049 but it was still not working.
My phone is not qualcomm based model so i cannot use nv item reader writer as it's required to edit IMEI
Even after applying phonutil patch my device is not being recognize as Qualcomm one.(because it's not)
So i was still looking for another way to change my imei manually as i have my original one on the box and under battery.
Finally I realized that i cannot make even Emergency calls it comes with message Out of service area.
So i was trying to apply few modem and radio updates to my phone but none of them are helping.
Anyone have similiar issue?
I have another Galaxy S3 that is working can i copy imei or whole system to my not working phone?
I know that after that i cannot use other device, but thats ok if its possible.
Click to expand...
Click to collapse
Have you tried patched modem and kernel? Did you read the guides on xda >> http://forum.xda-developers.com/galaxy-s3/general/ref-imei-efs-stuff-i9300-including-t2393289 << and no you cannot copy imei from another phone.
tallman43 said:
Have you tried patched modem and kernel? Did you read the guides on xda >> http://forum.xda-developers.com/galaxy-s3/general/ref-imei-efs-stuff-i9300-including-t2393289 << and no you cannot copy imei from another phone.
Click to expand...
Click to collapse
I tried everything from this guide.
Regarding patch:
4.0.4-I9300BVALE4 firmware is the only one working on my Samsung
Patched modem and kernel that i found and try it are XXUGMK6.
Maybe they are different one or dedicated to my firmware
Rockafella71 said:
I tried everything from this guide.
Regarding patch:
4.0.4-I9300BVALE4 firmware is the only one working on my Samsung
Patched modem and kernel that i found and try it are XXUGMK6.
Maybe they are different one or dedicated to my firmware
Click to expand...
Click to collapse
The reason you can't make calls is because at some point your phone software was on 4.3 this means your efs as changed to efs v2. Now because your current firmware is at 4.0.4 then your efs can't read this because 4.0.4 is efs v1. So you need to get a 4.3 stock rom onto your phone (I know you said only 4.0.4 works) but what are you using install firmware are you using Odin? If so what errors are you getting installing with Odin.
The patched modems and kernels are for 4.3 so they won't work on 4.0.4 or any other apart from 4.3
I was trying so many of them but its always ends with samsung logo loop it doesn' matter if i'm
do things like wipe cache, factory settings etc everytime its not working.
Even on 4.0.4 only this one rom is working.
Im always using ODIN, with KIES its always ends with samsung logo loop.
Rockafella71 said:
I was trying so many of them but its always ends with samsung logo loop it doesn' matter if i'm
do things like wipe cache, factory settings etc everytime its not working.
Even on 4.0.4 only this one rom is working.
Im always using ODIN, with KIES its always ends with samsung logo loop.
Click to expand...
Click to collapse
Ok a couple of things you could try (if you haven't already) I presume you have a custom recovery? Try flashing a custom stock 4.3 with recovery I suggest this >> http://forum.xda-developers.com/galaxy-s3/general/rom-sammys-stock-deodexed-rooted-t2585670 << This is as close to stock as possible but can be flashed with a custom recovery like Cwm,PhilZ,Twrp etc. You will also need to flash a 4.3 modem for this which is included in the thread. If the modem in the thread does not give you a signal (presuming the rom boots ) then keep the same custom rom but flash a patched modem and kernel on top with your custom recovery.
Don't forget to factory reset after flashing!
If none of that works you can always try the rescue firmware here >> http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6 << obviously flash the 4.3 one. Hope that helps
Thank you very much for your help i will try this and let know here if it's working
Rockafella71 said:
Thank you very much for your help i will try this and let know here if it's working
Click to expand...
Click to collapse
So it's me again.
I have good news and bad news.
So i was able to install both of firmware with success.
After applying patched modem everything was still working.
But when im calling 112 for example im still having "out of service area" and my imei is still 004999...
So issue is still exist.
I can discover any network when i choose network its even says"registred on network" but then if im trying to choose some number im having error message that im not registred or if emergency call "out of service area".
Any ideas what still can i try ?