trying to get the backup of one phone (4.3) onto another (4.0.4). when backup is restored to the second phone the wifi scans but wont connect (auth error). sim card not registering either. on the board it looks like the same model of i9300 as well the dates on the board of manufacture. one is from dubai and one from bulgaria. wondering if this is fixable by flashing another radio or is there more to it than that? when restoring to the original (4.0.4)it does get signal.
I think the problem is because of identical MAC address when you restored from another cwm backup.
try google and search for how to backup mac address and restore that file after resoring from cwm...
intoxic8 said:
I think the problem is because of identical MAC address when you restored from another cwm backup.
try google and search for how to backup mac address and restore that file after resoring from cwm...
Click to expand...
Click to collapse
thanks for the idea but it cant be the mac address since i was able to connect to everything just fine when i restored to my old backup. Also installed a new version of 4.3 (android revolution hd) which connects fine to everything. I was just hoping to avoid reinstalling everything when i have a perfectly good backup from another seemingly identical I9300.
It appears the imei has changed. but why? how? after restoring now it will not connect to any sim network now. but wifi is fine. all i can think of is flashing more modem files and see if that helps?
bromhexine said:
It appears the imei has changed. but why? how? after restoring now it will not connect to any sim network now. but wifi is fine. all i can think of is flashing more modem files and see if that helps?
Click to expand...
Click to collapse
Network IMEI EFS
http://forum.xda-developers.com/showthread.php?t=2393289
Downgrade and network problems .
http://forum.xda-developers.com/showthread.php?t=2531221
JJEgan said:
Network IMEI EFS
http://forum.xda-developers.com/showthread.php?t=2393289
Downgrade and network problems .
http://forum.xda-developers.com/showthread.php?t=2531221
Click to expand...
Click to collapse
thanks for the links. problem solved by a visit to samsung. nice fellas fixed at no charge while i waited.
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.
Was using CM10 Nightlys, when the infamous RIL Crash plagued my device
Reverted to CM9 Stable, No respite, Flashed Stock now
Tried Various modems DDLPA, XXLPS, XXLQ6, XXKI4
I get network outdoors, but there is no/ very very low network indoors
also even outdoors it randomly drops network (ril crash?), and says not registered on network sometimes
Searched various threads over here no solution seem to have worked, so far
What should I do? please help me save my device from becoming an expensive mp3 player.
Being a bit hysterical aren't we ?
nighh said:
-SNIP-
please help me save my device from becoming an expensive mp3 player.
Click to expand...
Click to collapse
nighh said:
Was using CM10 Nightlys, when the infamous RIL Crash plagued my device
Reverted to CM9 Stable, No respite, Flashed Stock now
Tried Various modems DDLPA, XXLPS, XXLQ6, XXKI4
I get network outdoors, but there is no/ very very low network indoors
also even outdoors it randomly drops network (ril crash?), and says not registered on network sometimes
Searched various threads over here no solution seem to have worked, so far
What should I do? please help me save my device from becoming an expensive mp3 player.
Click to expand...
Click to collapse
Have you only flashed the modem(.bin) file, or the corresponding RIL files too?
Have a look here => http://forum.xda-developers.com/showthread.php?t=1881304
If flashing modem and RIL files does not help, check your IMEI (and EFS folder), maybe it is corrupted.
If you have a backup of your EFS folder, try to restore it.
If that does not help either, try to flash the whole ROM again.
Maybe you have to wipe data/do a factory reset in recovery.
Good luck !
MistahBungle said:
Being a bit hysterical aren't we ?
Click to expand...
Click to collapse
I have tried everything, been spending whole last week trying different modems, I have tried everything I came across on ril crashes
Last thing to do is Visit the local customer care (which I would like to Avoid till I have no hopes left, they are pathetic)
It_ler said:
Have you only flashed the modem(.bin) file, or the corresponding RIL files too?
Have a look here => http://forum.xda-developers.com/showthread.php?t=1881304
If flashing modem and RIL files does not help, check your IMEI (and EFS folder), maybe it is corrupted.
If you have a backup of your EFS folder, try to restore it.
If that does not help either, try to flash the whole ROM again.
Maybe you have to wipe data/do a factory reset in recovery.
Good luck !
Click to expand...
Click to collapse
Thanks for the help
wipe data/do a factory reset is already done
I have flashed the .zip file, I guess it contains the ril too, also checked weather the modem and ril match after flashing by using GetRil
IMEI seems intact, I can see it, Will try to restore it, I have an old efs backup as well
It_ler said:
Have you only flashed the modem(.bin) file, or the corresponding RIL files too?
Have a look here => http://forum.xda-developers.com/showthread.php?t=1881304
If flashing modem and RIL files does not help, check your IMEI (and EFS folder), maybe it is corrupted.
If you have a backup of your EFS folder, try to restore it.
If that does not help either, try to flash the whole ROM again.
Maybe you have to wipe data/do a factory reset in recovery.
Good luck !
Click to expand...
Click to collapse
Restored EFS too, IMEI was ok and after restore IS ok, still no respite.
Any other solutions i might try?
Im in a very similar situation. Something went terribly wrong with one of the cm10 nightly's and my phone got HW bricked. Since that ive swapped out the motherboard and am know encountering this problem too. My efs is probably not as unadulterated as it could be but my IMEI is correct.
However with the sim in, About phone shows mobile network is disconnected, signal strength is 0, does not even know my own phone number. Cant find any networks when i search for them.
Any advice? OP what methods had you tried?
Gajselva said:
Im in a very similar situation. Something went terribly wrong with one of the cm10 nightly's and my phone got HW bricked. Since that ive swapped out the motherboard and am know encountering this problem too. My efs is probably not as unadulterated as it could be but my IMEI is correct.
However with the sim in, About phone shows mobile network is disconnected, signal strength is 0, does not even know my own phone number. Cant find any networks when i search for them.
Any advice? OP what methods had you tried?
Click to expand...
Click to collapse
My EFS was clean, never touched it, still restored a backup, nothing happened
Things I have tried are:
go to CM9 Stable (Wipe/Factory Reset from recovery)
Go to Stock
Try Various modems (try which go with your country and firmeare(tough they can be mix matched))
GSII Repair
Check for matching ril and modem using GetRil
fix permissions
I would suggest you to try GetRil first to check weather the modem and ril match
Give some time for modem to get adjusted to your network.
be extra careful with the efs.
Any Solutions Anyone?
Hi,
My S3's baseband is XXELL4. Recently I have tried Echoe Rom (4.3), which had a note that it wont alter modems, and if I lose network, I should flash MG4 modem to restore network. But after flashing, my IMEI was intact and I was able to get signals but when try to make calls, it shows "Not registered on network" error. Tried restoring my backup but again the same error for my previously working backups.
Since all the workarounds mentioned here did not workout for me (Including flashing stock 4.1.2 XXELL4 firmware and EFS restoration), I did a master wipe, restored XXELL4 modem first, then restored my EFS backup and flashed Fusion 4.4. Now everything was back to normal again.
So my question is how do I convert my EFS v1 modem to EFS v2 without losing network communications. I am interested to try modified stock 4.3 ROMs, as my primary requirements are fluidity with more juice for the day. So I need to flash a 4.3 stock based ROM and how do I do it without facing the same issue agian.
Any help from experts will be very much appreciated.
Downgrade and network problems .
http://forum.xda-developers.com/showthread.php?t=2531221
JJEgan said:
Downgrade and network problems .
http://forum.xda-developers.com/showthread.php?t=2531221
Click to expand...
Click to collapse
Thanks for the help. So if I flash this patched modem over XXELL4, will my network will still be working. Sorry for too many questions since my requirement would be hassle free switching between ROMs without losing network communications
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.