<RESOLVED> [HELP]N7100_IMEI 0049xx_SN 0000.._Service State "out of service"
Hi Guys. I got this issue after upgrading my Note II to the latest OMEGA ROM v17. After doing the upgrade I was able to use it for a couple of hours and then I realized though there is a signal I am not receiving any internet data (internet icon was gone). I restarted the phone, switch to flight mode back and forth, switch on/off data, but still no luck. I soon realized also that I am not receiving any SMS or call. I thought it was just my carrier so I called them and made a complaint like hell. They said that my line should be fine. From there I started reading for all possible reasons why I am getting this issue. I then found out that my IMEI that is showing on the phone is different on the sticker attached on the battery compartment. Serial number on the phone is 000000000. Service state is "Out of service" though it detects from which network my SIM is. I have tried to flash different custom ROMs and several stock ROMs, but with no go. Tried also different methods on restoring EFS and still no luck. Stupid me, I don't have any backup EFS file or a copy of a nand backup. I was able to get out of the factory mode, wifi and everything else are working except for not receiving any call or SMS because of the bad IMEI, SN, and the Service state "Out of service". I have read some fixes on other threads from a different android phones, but with no avail in fixing mine. I know there's a lot of thread of the same issue, but I want to create my own so I can make sure that people who got ideas on how to fix this is just referring to my "own" issue which will be easier for me to monitor the thread.
So I have tried the following:
- flashed different custom ROMs - no good
- flashed several stock ROMs - no good
- tried EFS Professional.exe - no good
- tried N7100_EFS_Backup_Restore_WIN - no good
- tried ARIZAPatch.apk - no good
- tried SGS tools - no good
- tried com.helroz.GSII_Repair_102.apk - no good
- tried NV-items_reader_writer.exe - I don't know how to make it work
- restored old EFS Backup - no good
- able to find an old NANDroid backup (when it was still working before), flashed it - no good
They say helps the modem from the topic http://forum.xda-developers.com/showthread.php?t=2333216
### --- XXDME4 modem --- ### fix IMEI - -unknown modem
on the XXDME6 base - you can not install old modems,
because it will cause for unknown modem & imei status.
Solution flash - XXDME4 modem
XXDME4 modem
flash via TWRP / CWM
ATTACHED FILES
modem XXDME4 .zip - [Click for QR Code] (4.84 MB, 1209 views)
Click to expand...
Click to collapse
tried that still no go
red_hanks said:
...
Click to expand...
Click to collapse
Read this
victorator said:
Read this
Click to expand...
Click to collapse
Tried that mate but no luck.
in /efs folder contains files *.bak?
aaleo said:
in /efs folder contains files *.bak?
Click to expand...
Click to collapse
yup
move the following files in a backup folder somewhere to your internal SD card
.nv_core.bak,
.nv_core.bak.md5,
.nv_data.bak,
.nv_data.bak.md5,
nv_data.bin,
nv_data.bin.md5
moving them they will be deleted from the efs folder
Reboot.
Now you will have the generic IMEI.
aaleo said:
move the following files in a backup folder somewhere to your internal SD card
.nv_core.bak,
.nv_core.bak.md5,
.nv_data.bak,
.nv_data.bak.md5,
nv_data.bin,
nv_data.bin.md5
moving them they will be deleted from the efs folder
Reboot.
Now you will have the generic IMEI.
Click to expand...
Click to collapse
I have tried that method but it just made my note2 switch to factory mode. Sorry to ask but have you tried that method on your own or you just copy pasted that from somewhere showing that you're willing to help but no certainty if that really works or will just mess up something?
I did it. I did not have IMEI (0000000000) I think you can help it. The last thing that comes to mind to flash the original firmware from sammobile.com through odin.
---------- Post added at 04:39 PM ---------- Previous post was at 04:23 PM ----------
You can restore files via adb
Code:
adb shell
su
mount -o rw,remount /dev/block/mmcblk0p3 /efs
cp /mnt/sdcard/.nv_core.bak /efs/.nv_core.bak
cp /mnt/sdcard/.nv_core.bak.md5 /efs/.nv_core.bak.md5
cp /mnt/sdcard/.nv_data.bak /efs/.nv_data.bak
cp /mnt/sdcard/.nv_data.bak.md5 /efs/.nv_data.bak.md5
cp /mnt/sdcard/nv_data.bin /efs/nv_data.bin
cp /mnt/sdcard/nv_data.bin.md5 /efs/nv_data.bin.md5
aaleo said:
I did it. I did not have IMEI (0000000000) I think you can help it. The last thing that comes to mind to flash the original firmware from sammobile.com through odin.
---------- Post added at 04:39 PM ---------- Previous post was at 04:23 PM ----------
You can restore files via adb
Code:
adb shell
su
mount -o rw,remount /dev/block/mmcblk0p3 /efs
cp /mnt/sdcard/.nv_core.bak /efs/.nv_core.bak
cp /mnt/sdcard/.nv_core.bak.md5 /efs/.nv_core.bak.md5
cp /mnt/sdcard/.nv_data.bak /efs/.nv_data.bak
cp /mnt/sdcard/.nv_data.bak.md5 /efs/.nv_data.bak.md5
cp /mnt/sdcard/nv_data.bin /efs/nv_data.bin
cp /mnt/sdcard/nv_data.bin.md5 /efs/nv_data.bin.md5
Click to expand...
Click to collapse
Just tried original firmware but same thing. I am getting frustrated now..
Stupid idea. Maybe it's in the sim card is broken. There is another test for?
aaleo said:
Stupid idea. Maybe it's in the sim card is broken. There is another test for?
Click to expand...
Click to collapse
SIM card is ok. Read my explanation on post #1.
Was able to find an old EFS backup of mine dated January 2013. Tried to restore it but still same issues.
red_hanks said:
Was able to find an old EFS backup of mine dated January 2013. Tried to restore it but still same issues.
Click to expand...
Click to collapse
Read this: http://forum.xda-developers.com/showthread.php?t=2332913
The Stability update on which is based the rom has some changes in the kernel and the efs folder. Maybe that thread can help you out....hope it does....:good:
red_hanks said:
Tried that mate but no luck.
Click to expand...
Click to collapse
Just wondering, did you tried Kies Emergency restore???
Sent from my GT-N7100 using xda premium
find someone who has a SGN2 ,back up the image of efs partition 20mb , open it with a compiler on your pc, change the IMEI to same as yours on the box , recompile and restore.
hagba said:
find someone who has a SGN2 ,back up the image of efs partition 20mb , open it with a compiler on your pc, change the IMEI to same as yours on the box , recompile and restore.
Click to expand...
Click to collapse
Wow sounds complicated lol hope this don't happen to me!
Sent from my GT-N7100 using xda app-developers app
glevitan said:
Read this: http://forum.xda-developers.com/showthread.php?t=2332913
The Stability update on which is based the rom has some changes in the kernel and the efs folder. Maybe that thread can help you out....hope it does....:good:
Click to expand...
Click to collapse
Done with this with no luck.
aspot72 said:
Just wondering, did you tried Kies Emergency restore???
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
Not sure how to do that, never use Kies before
hagba said:
find someone who has a SGN2 ,back up the image of efs partition 20mb , open it with a compiler on your pc, change the IMEI to same as yours on the box , recompile and restore.
Click to expand...
Click to collapse
Like what I have said, found an old backup of mine and it doesn't work. So it's pointless to try this.
I was sleepless (haha) trying to find solution for this. I came across this site and tried the app there. But as you can see on the image below, the button to change the IMEI is grayed out. There is not clear instructions on the site so it is kinda hard what to do in times like that. The app might be for a specific device but if it recognized the IMEI on my phone then it should be able to change it.
Related
My details are as follows:
pda i9000ddjg4
phone i9000ddjg4
I downloaded Kalpik and Doc rom and flashed with clockworkmod. I was not satisfied with it and moreover it changed my product code. In Kies I used to get message that my firmware cannot be upgraded. Therefore I copied two files from my original backed up efs folder to the new Efs folder. The files were copied using busybox and terminal emulator. The files were nv_data.bin and nv_data.bin.md5. I got the original product code after rebooting but instead of the phone operator symbol now I get a blue circle . Again I restored, using rom manager, my phone from a previous backup(from my original firmware). But again the same problem. I used Odin and flashed the ddjg4 firmware. That also has not helped. Can somebody guide me how to get back the phone fuction?
Check this thread out:
http://forum.xda-developers.com/showthread.php?t=780509
**IF YOUR SIMCARD DOESN'T WORK AFTER THIS, EXECUTE THE FOLLOWING**
- adb shell
- su
- busybox chown 1001:1001 /efs/nv_data.bin
- reboot
You can also do this from the Terminal Emulator if you don't have ADB on your PC! Like this:
-su
-chown 1001:1001 /efs/nv_data.bin
-reboot
I hope it's easy to follow my steps, it works guaranteed.
Click to expand...
Click to collapse
It worked a charm. My Simcard now works. Thanks a million.
Oh I did not see that when I lost phone functionality when I did it.
Can I use this method to trick KIES?
Although the regedit hack would be easier I guess.
RambJoe said:
Oh I did not see that when I lost phone functionality when I did it.
Can I use this method to trick KIES?
Although the regedit hack would be easier I guess.
Click to expand...
Click to collapse
The hack only tricks Kies, your phone still has the wrong productcode after flashing. Mine did at least. Went from european JM2 to JM8 and then to scandinavian JP6. Had some troubles with it so used the registry hack to go back to the official european JM2. It worked, but in the registry it still listed as a scandinavian JM2. Don't know what the difference is (except for different Samsung Apps).
I just wanted to share a story of woe and redemption so that it doesn't happen to you.
As background, I had sim unlocked my phone using helroz's method a while back, and my phone has been working fine from team whiskey's early days till now. Recently, I was flashing my phone as most of us do. I noted that after flashing the dead horse kernel, my market was not working properly, so I decided to odin back to JFD. From there, I flashed Bionix, but afterward, noted that I wasn't getting any cell reception. After some investigation and several odins, I looked at my software info and found that my baseband was unknown. I flashed back to JFD however, and it worked fine. In fact, this was the only rom where the cell worked. The phone otherwise was functioning flawlessly, including wifi.
Further investigation showed that this has happened to others, and anecdotally, people have fixed it by odining over and over or doing some magic with their sim card. I did just that but to no avail. After some thinking, it occurred to me that maybe my /efs data was bad, so I took a look. Hitting *#06# showed the generic samsung IMEI while in JFD (it did not work in other versions as the baseband was not working), not my normal IMEI. That's odd. I still had the backup from trying to sim unlock it months ago. I tried to overwrite the /efs folder w/ my own, but I could not write it due to 'not enough space.'
Further investigation showed that indeed, my efs partition had been borked, and so I could not write data to it (I could copy however). The only way to fix this is by flashing/odin'ing a new partition. This only works if you have a backup, which I didn't. Basically, I had a fancy media player at this point.
I went ahead and looked on craigslist and found a vibrant w/ a broken screen, figuring I could swap out the guts. I immediately backed up the /efs folder and partition of the broken phone, just in case. On a whim, I tried to flash the efs partition from the broken phone to my phone. Lo and behold, the baseband came back. I was now able to write to that partition, so overwrote the /efs folder w/ my backup from before. My IMEI came back afterwards, and so now, I have 2 functioning vibrants. I'm not sure what data is stored in /dev/block/stl3, but I do know I was able to fix my phone using another phone's data. They both work w/ my sim, though I am unsure if they can connect simultaneously using different sims or if they are somehow cloned, but the IMEIs are different for sure.
The moral of the story is that this phone is nigh unbrickable and even when it doesn't boot, you can always try the jig. The only part of the phone you can't fix w/ a routine odin it seems, is the efs partition, so I would encourage everyone to make a backup and keep it safe. This is not done standard as an initiation into rooting and roms and such, but it should be. Normally, odin'ing a rom does not write to this area, but even w/o screwing with this, frequent flashing and odins can apparently corrupt it, leaving you high and dry. With this backup and odin, you could probably fix your phone from any jam.
Here are the relevant threads on how to do this:
http://forum.xda-developers.com/showthread.php?t=882039
http://forum.xda-developers.com/showthread.php?t=859914
Keep those backups safe!
Thank you for sharing ur experience, I recently noticed that my data speeds have gone down after unlocking my vibrant using the method you mentioned above.Damn, I get edge speeds when I am on a HSPA network. Dunno whats the problem,called up simple mobile,am not data throttled.Sigh..
Sent from my SGH-T959 using XDA App
man this is scary, but your phone still works at JFD right?
Sent from my SGH-T959 using XDA App
It didn't for a while. Now, both phones are fully functional. I had a copy of the /efs folder of my old phone, but not an image of the partition. The problem is, when the partition gets screwed, you can't write to it, making the /efs useless.
That's why I'm trying to get people to make the backup. It takes a few minutes, but can be a lifesaver. I do believe you can flash a foreign stl3 partition and overwrite the /efs like I did, but unless you had a friend, no one would share it w/ you as it contains their imei info. Better to just back up your own. And if you lose your /efs, game over.
How exactly do you back up a partition?
Very cool of you to post this up. Is there any reason to back up your efs partition if you have no reason to unlock?
<---backing it up anyway.
It's not the unlocking. It seems that over time, some people (such as myself) screwed up the efs partition by just flashing/odin'ing various roms. It shouldn't happen, but it does. Consider that no roms write to the stl3 layer, yet mine was working one day, then one odin later, it didn't. I'm sure the number of people this happens to is quite small, but when it happens, it happens. It's like a 6 mb backup which isn't that big of a deal.
It's better to be safe than sorry.
I did an experiment on my Galaxy Tab, that I move the /efs folder to memory card.
Soon I found the reception goes way worse (at least 10dBm less) and the serial number changed to 00000000, then I immediately copied (restore) the folder and everything was back to normal.
I tried to examine the files with hex editor but I found nothing spectular.
vnamee said:
It's not the unlocking. It seems that over time, some people (such as myself) screwed up the efs partition by just flashing/odin'ing various roms. It shouldn't happen, but it does. Consider that no roms write to the stl3 layer, yet mine was working one day, then one odin later, it didn't. I'm sure the number of people this happens to is quite small, but when it happens, it happens. It's like a 6 mb backup which isn't that big of a deal.
Click to expand...
Click to collapse
That's really weird. I've never really looked into the occurrence because I always assumed it was isolated only to those that did some weird hacking in an attempt to unlock, or to those that were developing and found themselves doing some nasty, nasty things.
I just created efs_dev-block-st13.img and efs-backup.tar.gz so hopefully I'm all safe and sound now.
Thanks again! Once I get beyond GPS stuff I find myself clueless.
draikz said:
How exactly do you back up a partition?
Click to expand...
Click to collapse
You need to read the two links in the OP and download adb. You also need root and busybox.
all you need is to root your phone, such as w/ superoneclick which will put busybox on there. Then all you need is adb.exe.
Open up a command prompt where adb.exe is located. You can adb su or just go adb shell and then su.
The only commands you need are:
cat /dev/block/stl3 > /sdcard/stl3.bin (backs up sector management layer of partition)
cat /dev/block/bml3 > /sdcard/bml3.bin (backs up block management layer of partition)
tar zcvf /sdcard/efs-backup.tar.gz /efs (tars /efs folder)
cp stl3.bin efs.rfs (just makes copy of stl3.bin to new name efs.rfs)
tar -cf efs.tar efs.rfs (makes an odin flashable tar of partition)
I kept a copy of stl3.bin, bml3.bin, efs-backup.tar, and efs.tar.
vnamee said:
all you need is to root your phone, such as w/ superoneclick which will put busybox on there. Then all you need is adb.exe.
Open up a command prompt where adb.exe is located. You can adb su or just go adb shell and then su.
The only commands you need are:
cat /dev/block/stl3 > /sdcard/stl3.bin (backs up sector management layer of partition)
cat /dev/block/bml3 > /sdcard/bml3.bin (backs up block management layer of partition)
tar zcvf /sdcard/efs-backup.tar.gz /efs (tars /efs folder)
cp stl3.bin efs.rfs (just makes copy of stl3.bin to new name efs.rfs)
tar -cf efs.tar efs.rfs (makes an odin flashable tar of partition)
I kept a copy of stl3.bin, bml3.bin, efs-backup.tar, and efs.tar.
Click to expand...
Click to collapse
I've got backups of stl3.bin, bml3.bin and efs-backup.tar.gz
When I try to make the partition an odin flashable tar it tells me: "No such file or directory".
You have to cd into the directory, or else it should be:
cp /sdcard/stl3.bin /sdcard/efs.rfs (just makes copy of stl3.bin to new name efs.rfs)
tar -cf /sdcard/efs.tar /sdcard/efs.rfs (makes an odin flashable tar of partition)
This is kind of old news, but nevertheless important.
Months ago in the Q&A section there were two threads about the importance of the EFS, and how a corrupted nv_data.bin and EFS can cause many problems including losing the ability to use a different carriers sim, yet nobody paid attention to those threads, but I thought the info was vital.
Would using ROM Manager and backing up your current rom, also backup the /efs?
vnamee said:
You have to cd into the directory, or else it should be:
cp /sdcard/stl3.bin /sdcard/efs.rfs (just makes copy of stl3.bin to new name efs.rfs)
tar -cf /sdcard/efs.tar /sdcard/efs.rfs (makes an odin flashable tar of partition)
Click to expand...
Click to collapse
Yeah, I did. I'll do it again and post up exactly what I type and put in. Maybe it's just operator error.
Here ya go.
It might have been operator error because that time I watched efs.tar get written to /sdcard
It should be efs.rfs, not efs/rfs. It's a file, not a directory.
SamsungVibrant said:
Would using ROM Manager and backing up your current rom, also backup the /efs?
Click to expand...
Click to collapse
Nandroid does not back up the /efs partition, at least not that I can tell. All those files in the backup folder are of the various partitions, and efs partition is not part of it.
The reason I made this thread to begin with is because when I had this problem, I looked high and low, and found scant info. In the future, if someone else has this problem, this will come up in a search and won't have some lame magical fix that may or may not work.
vnamee said:
It should be efs.rfs, not efs/rfs. It's a file, not a directory.
Click to expand...
Click to collapse
Pinky slip!!! For whatever reason, it took 3 tries but I finally got it to backup. Thanks for the help! I would never think to back this stuff up. Everyone does Nandroid's like crazy, which is good, but losing this stuff is losing your phone!
Excellent write-up vnamee thank you..........
I tried to delete nv_data.bin and nv_data.bin.md5 in order to recover original version from .nv_data.bak and .nv_data.bak.md5 after reboot but failed.
Firstly I remounted efs partition with -w flag:
Code:
mount -w -t ext4 /dev/block/mmcblk0p1 /efs
First file've been deleted but for second message 'read-only system' shows up. And when i unmount and then mount again first file appears again.
I tried to do these from terminal emulator, adb shell from booted phone and in recovery mode (with CF4 installed).
My firmware version XWKE7. I bought phone as sim free at clove.co.uk
Can anyone suggest what can i do?
From what I have read from the SGS forum if your efs folder is missing your imei your stuck, only thing to do is flash some stock FW from odin and return it, hope you can return it under warranty mate.
Sent from my GT-I9100 using XDA Premium App
wow, seriously unlucky try pushing it through adb?
EDIT: nevermind
try restoring & wiping everything, then rooting, then try and push it through adb ?
You could try the backup and restore efs post from dev section if you have not already .
jje
JJEgan said:
You could try the backup and restore efs post from dev section if you have not already .
jje
Click to expand...
Click to collapse
Yes, but it only works if he backed up his efs folder before he lost his imei.
Sent from my GT-I9100 using XDA Premium App
Kstarz said:
Yes, but it only works if he backed up his efs folder before he lost his imei.
Sent from my GT-I9100 using XDA Premium App
Click to expand...
Click to collapse
I know but may be more help their than elsewhere .
Restore IMEI post on SGS1 forum from memory as well .
Lost mine on SGS1 but a simple stock rom install restored it .
jje
I have root my S4 and will make a backup from efs/imei but EFS Professional not working with the S4. How can i backup efs?
is it so hard to get a copy of ur EFS folder to safe place ?
You can use TWRP recovery to get a EFS backup
Gesendet von meinem GT-I9505 mit Tapatalk 2
You can back up a whole partition with Terminal Emulator from Play Store.
This is example made for I9505 ONLY!!!!
For I9500 use mmcblk0p3 and efs.img instead!!!
Download it , and run it, then type:
Code:
su
dd if=/dev/block/mmcblk0p10 of=/mnt/sdcard/efs.img.ext4
and it will dump whole partition into one file efs.img.ext4 on your internal SD card
or
Code:
su
dd if=/dev/block/mmcblk0p10 of=/mnt/extSdCard/efs.img.ext4
to save it on external SD.
If something goes wrong and you need to restore it:
Code:
su
dd if=/mnt/sdcard/efs.img.ext4 of=/dev/block/mmcblk0p10
or
Code:
su
dd if=/mnt/extSdCard/efs.img.ext4 of=/dev/block/mmcblk0p10
Keep it safe and enjoy
djembey said:
You can back up a whole partition with Terminal Emulator from Play Store.
Download it , and run it, then type:
Code:
su
dd if=/dev/block/mmcblk0p10 of=/mnt/sdcard/efs.img
and it will dump whole partition into one file efs.img on your internal SD card
or
Code:
su
dd if=/dev/block/mmcblk0p10 of=/mnt/extSdCard/efs.img
to save it on external SD.
If something goes wrong and you need to restore it:
Code:
su
dd if=/mnt/sdcard/efs.img of=/dev/block/mmcblk0p10
or
Code:
su
dd if=/mnt/extSdCard/efs.img of=/dev/block/mmcblk0p10
Keep it safe and enjoy
Click to expand...
Click to collapse
With all respect to your post, I would like to warn people that this is not working for all the models/devices. Although it might look fine when executing the commands, it might not have made a backup of EFS, but of something else... What I know for sure is that it will not work for atleast the international i9505-model of the S4, as the partition layout is different.
In my post below, more details are given on this partition id.
http://forum.xda-developers.com/showthread.php?t=2276599
While executing your commands does not affect the device, it does not always give the people a backup they expect it to be, depending on their device/model. In my case you are able to verify which 'mmcblk' is actually efs on your device. It also gives a TAR backup as option.
Mr_Q said:
With all respect to your post, I would like to warn people that this is not working for all the models/devices. Although it might look fine when executing the commands, it might not have made a backup of EFS, but of something else... What I know for sure is that it will not work for atleast the international i9505-model of the S4, as the partition layout is different.
In my post below, more details are given on this partition id.
http://forum.xda-developers.com/showthread.php?t=2276599
While executing your commands does not affect the device, it does not always give the people a backup they expect it to be, depending on their device/model. In my case you are able to verify which 'mmcblk' is actually efs on your device. It also gives a TAR backup as option.
Click to expand...
Click to collapse
Mate... I've added that it is for I9505!!!!
I9500 have EFS located @ mmcblk0p3...........
thanks
I used GS2 repair from play store. It went through the usual process and I can see the back up file on the sd card. Can anybody more qualified confirm if this app works on S4?
Sent from my GT-I9505 using xda premium
djembey said:
Mate... I've added that it is for I9505!!!!
I9500 have EFS located @ mmcblk0p3...........
thanks
Click to expand...
Click to collapse
Great. You are right, in my case it's mmcblk0p10 as well, as mentioned correctly in my guide already.
Thank you for updating.
HANDSY said:
I used GS2 repair from play store. It went through the usual process and I can see the back up file on the sd card. Can anybody more qualified confirm if this app works on S4?
Sent from my GT-I9505 using xda premium
Click to expand...
Click to collapse
The best thing is to check it with the developer. I do not know what file has been created, although I expect it to be a raw copy using dd. The best thing is to do it manually. Or by the instructions given by djembey, or by the more detailed step-by-step instructions in the thread of my previous post here.
Hey, I managed to backup the EFS folder. Is there any way to modify the backup file and restore it after the modification? I want to change the IMEI number but unfortunately I have no box / cables available to do so. There must be a solution?! I am currently living in Turkey and they restrict western mobile phone usage for foreign people.
thanks a lot
cheers,
ralf
,
ralfa1234 said:
Hey, I managed to backup the EFS folder. Is there any way to modify the backup file and restore it after the modification? I want to change the IMEI number but unfortunately I have no box / cables available to do so. There must be a solution?! I am currently living in Turkey and they restrict western mobile phone usage for foreign people.
thanks a lot
cheers,
ralf
Click to expand...
Click to collapse
Same here with me
i9505 imei null
please can somebody help me,what ever I try not working.Unfortynately everything working,but always show imei null and not have baseband,of course and network too.I am install with Odin few different fabrics roms or how you call that.Last is this one with 4 files inside
I9505XXUGNG8_I9505OXXGNG2_I9505XXUGNG8_HOME.tar.Everything going fine,but havent imei like on start.I am also try few different things with EFS_Professional.but cannot fix my problem.Also I am try to erase EFS,but folder cannot erase,just files inside,and trying other one downloaded from net,but not going.Every time after reboot,EFS be back automatics,Can you help me ,please
If I am write inside EFS folder must be a file nv_data.bin ,I dot have that.Have lots of,but dont see that.I have inside few folders,like imei and etc.. And inside imei folder I have mps_code.dat.I am hope somebody can understand my problem.Can somebody sent to me that file,and can I take from other phone.Is that my solution,or what.HELP PLEASE
this is in function to my i9505,but not help me to solve problem.Somehow I not have file nv_data.bin on my phone in efs folder,and backup and restore not help me.Please do you no some solutions?
So after lots of flashing of different roms on my Moto G 2nd gen (XT1068) I ended up unable to turn WIFI on in any rom, including stock!
Thing is, after days of breaking my head with this, I figured out I was missing the WCNSS_qcom_wlan_factory_nv.bin file from the /Persist folder.
How did that file go missing and why it was not restored when restoring to stock or flashing roms? Dam good question, I don't have an answer to that yet, BUT, I have a fix.
Simply download the attached .rar, unzip it, and manually put the WCNSS_qcom_wlan_factory_nv.bin file in your /Persist folder using any root explorer / file manager on your device and reboot!
Such a simple little thing gave me so much trouble, hope this will help future users who might face the same problem, as I already saw around that other people are also having the same issue.
This should work for any Moto G version, even the 2013 model, XT1063, XT1064, XT1068, XT1069, all share the same WIFI file.
Happy surfing on your now working WIFI!
Nice Work!
I have that file in /persists but still no WiFi.
Obagleyfreer said:
I have that file in /persists but still no WiFi.
Click to expand...
Click to collapse
Most likely its the perms issue. If you have 'adb' and can connect to the phone using adb, do this:
adb logcat -d -v time | grep "avc: denied"
right after a fresh start. If the file shows up in that grep, it means that you are running into permissions issue. And it can be fixed if you have root.
Where cn i find persist folder... ??? I m using CM12
Sent from my Moto G 2014 using XDA Premium 4 mobile app
immy8796 said:
Where cn i find persist folder... ??? I m using CM12
Sent from my Moto G 2014 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Root of your device,
/persist
Exelios said:
Root of your device,
/persist
Click to expand...
Click to collapse
Found it... Thanx.. bt which permission i hv to give that .bin file.. ???
Sent from my Moto G 2014 using XDA Premium 4 mobile app
immy8796 said:
Found it... Thanx.. bt which permission i hv to give that .bin file.. ???
Sent from my Moto G 2014 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Mine is 777, read write execute to everyone, probably not the right cmod, but it works
after try like 5 kernels and almost start to crying i found this post
AND WORKS!!!!
Thanks you so much!!
ZenKeep said:
after try like 5 kernels and almost start to crying i found this post
AND WORKS!!!!
Thanks you so much!!
Click to expand...
Click to collapse
O yeah I know the feeling, went trough the same, glad I helped!
Also pressing the tnx button on my post would help me!
I already have persist folder and file in root directory and overwrite it with rw-r-r permission but still not working plz help.
HELP!
I have restored to stock firmware, and my wifi just turns off when i turn it on. I think i am missing this file but as im on stock I dont have root access. How can i install this file if i dont have root access.
A quick reply would be amazing!
Thanks
mrangryoven said:
I have restored to stock firmware, and my wifi just turns off when i turn it on. I think i am missing this file but as im on stock I dont have root access. How can i install this file if i dont have root access.
A quick reply would be amazing!
Thanks
Click to expand...
Click to collapse
You could just root again. Using super su you can unroot using the super su app after you finish the fix.
Sent from my XT1064 using Tapatalk
still have the same issue. stock rom and stellar kernel
Thank you man, this really worked!!! You saved my ass!
PS: I have another problem similar to this one. I can' t acces to my mobile network, I have them turned on, but when I press on Network operators, a message pops up saying "Error while searching for networks ". Have you ever encountered this problem? Because I can' t find an answer
sumit227 said:
I already have persist folder and file in root directory and overwrite it with rw-r-r permission but still not working plz help.
Click to expand...
Click to collapse
I also tried to reload the stock boot.iso but that did not help me in this case. In the end what fixed this issue for me was to wipe the phone and load cyanogen mod 12.1.
I downloaded the following files to my phones SDCARD before starting the process below.
cm-12.1-20150816-NIGHTLY-titan-recovery.img
cm-12.1-20150816-NIGHTLY-titan.zip
gapps-5.1-arm-2015-07-17-13-29.zip
0) reboot into fastboot
1) fastboot flash recovery cm-12.1-20150816-NIGHTLY-titan-recovery.img (this was done from the command line on my Mac, and that file was on my Mac at the time)
2) reboot into recovery
3) choose "Wipe data / Factory Reset"
4) choose "Apply Update" -> "Choose From SDCARD1 -> "cm-12.1-20150816-NIGHTLY-titan.zip"
at this point I rebooted but could have probably installed GAPPS right away. The wifi was working again at this point!
5) choose "Apply Update" -> "Choose From SDCARD1 -> "gapps-5.1-arm-2015-07-17-13-29.zip"
I think I will stick with CM for now. I've used it in the past and it was fine.
jreeve0805 said:
I also tried to reload the stock boot.iso but that did not help me in this case. In the end what fixed this issue for me was to wipe the phone and load cyanogen mod 12.1.
I downloaded the following files to my phones SDCARD before starting the process below.
cm-12.1-20150816-NIGHTLY-titan-recovery.img
cm-12.1-20150816-NIGHTLY-titan.zip
gapps-5.1-arm-2015-07-17-13-29.zip
0) reboot into fastboot
1) fastboot flash recovery cm-12.1-20150816-NIGHTLY-titan-recovery.img (this was done from the command line on my Mac, and that file was on my Mac at the time)
2) reboot into recovery
3) choose "Wipe data / Factory Reset"
4) choose "Apply Update" -> "Choose From SDCARD1 -> "cm-12.1-20150816-NIGHTLY-titan.zip"
at this point I rebooted but could have probably installed GAPPS right away. The wifi was working again at this point!
5) choose "Apply Update" -> "Choose From SDCARD1 -> "gapps-5.1-arm-2015-07-17-13-29.zip"
I think I will stick with CM for now. I've used it in the past and it was fine.
Click to expand...
Click to collapse
This also worked for me, loaded the latest CM nightly and Wifi came back. Previous steps outlined in this thread did not work.
Had issues with Moto G2 wifi after rooting.. wotks fine after Blisspop
Tom flash
Sent from my SM-T231 using XDA Free mobile app
pls help
persist folder gets removed every time i put it there using root explorer... when i click add new folder into the / (persist is not there) and type in persist it creates a folder with the files already there then i quit the explorer and come back only to find out the the folder is not shown there anymore but if i created again is gets in there and has all the files but again when i quit it disappears...
---------- Post added at 08:48 PM ---------- Previous post was at 08:25 PM ----------
Tel864 said:
You could just root again. Using super su you can unroot using the super su app after you finish the fix.
Sent from my XT1064 using Tapatalk
Click to expand...
Click to collapse
pls help me i have the folder but its not shown in the explorer it only shows when i add new folder and name it persist but then it disappears again
WiFi turns off instantly I try to turn it on
I have the same issue like you guys, and i've already try to copy the file to the /persist folder, with all the permissions... and nothing but error message pop ups (I can't modify the files in the folder, but accidently I erase one of the WCNSS files. It doesn't make any sense)
I've also tried to install the stock firmware to my XT1068, several ROMs with LP 5.0.2, 5.1, etc (everytime doing wipe cache and data); and the issue is still going.
What can I do? Downgrade to KK can restore all the missing files?
Maybe I can copy a /persist folder entirely with all the files... I don't know.
I'm running out of ideas! And I don't want to live with the idea of 'no-wifi' in such an excellent phone! :crying:
Thanks for your time, guys!