[Tools][How-To][Guides] Backup & Restore EFS + Get out from Permanent Safe mode - Galaxy S 4 i9505 Android Development

Note to forum managers: Please make it a Sticky Thread, It should help to all users and there is no use for this tutorial if it is in page 3
Hello XDA Users,
I think some people here know who I am, so I will jump on the "Introduction of myself" for now.
Recently, I have faced many questions & problem of fake IMEI, of damaged EFS folder. So I made a little experiment on my device(GN2).
First, I backuped my EFS folder in 2 types - one is .img and the second is tar.gz.
Then, I deleted my EFS folder using ES Root Explorer. Which made my device to be on somethine called "Permanent Safe Mode" - You can not get out untill you fix your EFS folder and change some values.
This is permanent safe mode:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After I did my "research" I have managed to make several methods to backup & restore EFS, which should make your life easier and better.
First of all, Disclaimer:
I'm not responsible for any damage caused by using these methods, all methods tested by me, so it should work on your device too.
This is for I9505 Only!!!!!!!
Let's continue.
What you must have:
Latest base with latest modem and latest kernel - very important since in the latest versions samsung prevented the option to install old modems/kernels, so if you install old kernell/modem it can show you wrong IMEI.
Rooted device with the latest Super User
Latest busybox
PhilZ Recovery
Terminal Emulator
Root explorer - Can be ES File Explorer with working root option or just a root explorer from the market
A working EFS backup(In order to restore it...)
Time & Patient.
Important Notes:
When installing/downgrading firmwares, several people suffered from Fake IMEI. This is because the new firmware messed up your EFS folder, which means that you can not restore EFS backup until you are on the latest version, latest modem and latest stock kernel, recommended is XXUBMH1(right to 05/09/2013)
Some custom roms include modem installation in their rom installer. Due to modem flashing in recovery, some devices might get Fake IMEI. My recommendation is before even starting to use this guide, please try to install the latest modem via odin from this thread:
http://forum.xda-developers.com/showthread.php?t=2192025
When installing modem via odin, make sure you select PHONE and not PDA
You will find at least one method that works on your device, so don't give up after one method.
Read all guide and pay attention to all small details.
Backup methods
Method 1 - .img backup
First method, is an automatic backup/restore software.
Special thanks to A.S._id for his software.
The software:
I9505 EFS Backup / Restore
Help to preserve and restore the image of EFS partition:
* Need Root
For Windows
* Extract from the archive, connect the device to the USB debugging mode (System settings/Developer options/USB debugging) and run selected .bat (depending on the backup or restore)
* To retain the image of efs.img must be in a folder with Restore_EFS.bat
* Extract from the archive, connect the device to the USB debugging mode (System settings/Developer options/USB debugging) and run RUN_ME into terminal (double click), select option...
What is EFS, Why it is necessary to backup
Click to expand...
Click to collapse
Method 2 - .img backup
Method number 2 will create you efs.img backup on your internal sd. After that you can copy it to your computer.
What you have to do is this:
Open terminal emulator
Write the following:
Code:
su
Then click enter. It will ask for super user permission, give it permissions.
Then write:
Code:
dd if=/dev/block/mmcblk0p10 of=/sdcard/efs.img bs=4096
Then click enter.
When it finishes, check if you have efs.img on your phone memory. If so, copy it to comupter, if not, you did something wrong try again.
Click to expand...
Click to collapse
Method 3 - .tar.gz backup
This method will compress your efs folder into tar.gz file. This method is the same as choosing backup EFS folder in my rom(PhoeniX ROM)/Omega/Wanam/etc.
A tar.gz backup should look like this(On some devices there might be more files, but this picture was taken from Note II N7100 backup and it fully works):
What you have to do is this:
Download this and copy it to your device:
http://d-h.st/SaK
Reboot into recovery
Flash the zip
Reboot your device.
Connect your device to your pc, and copy the backup in "efs_backup" folder.
Click to expand...
Click to collapse
Restore methods
Now the fun begins
You will have to restore your backup when you have one or more of the folowing problem:
Fake IMEI (usually 004999010640000) or "null" IMEI
Blinking SIM card icon on the top tray… ETC
Unable to unlock your SIM card using your PIN
Fake Serial Number (usually 0000000) or "null" Serial
Unable to register to the network (usually comes with Fake IMEI & Fake Serial so check them.)
Attention please,
If you are 100% that your EFS folder is damaged and you have a working EFS backup with the right IMEI number, my recommendation is this:
With root explorer, go to your efs folder and delete all files inside
Long press on power button will turn off your device.
Then turn on the device, you will be in "Permanent Safe Mode".
Continue to one of the following methods.
Click to expand...
Click to collapse
Method 1 - restore .img backup
First method, is an automatic backup/restore software.
Special thanks to A.S._id for his software.
The software:
I9505 EFS Backup / Restore
Help to preserve and restore the image of EFS partition:
* Need Root
For Windows
* Extract from the archive, connect the device to the USB debugging mode (System settings/Developer options/USB debugging) and run selected .bat (depending on the backup or restore)
* To retain the image of efs.img must be in a folder with Restore_EFS.bat
* Extract from the archive, connect the device to the USB debugging mode (System settings/Developer options/USB debugging) and run RUN_ME into terminal (double click), select option...
What is EFS, Why it is necessary to backup
Click to expand...
Click to collapse
Method 2 - Restore .img backup
Method number 2 will restore your efs.img backup from your internal sd.
What you have to do is this:
Put your efs.img on your phone memory(not external sd card!) in the main memory, not inside folder.
Open terminal emulator
Write the following:
Code:
su
Then click enter. It will ask for super user permission, give it permissions.
Then write:
Code:
dd if=/sdcard/efs.img of=/dev/block/mmcblk0p10 bs=4096
Then click enter.
Now, reboot your device. If you still don't have IMEI/You are still in Safe Mod, reboot again.
In the second reboot, the bootanimation might stuck and the device will reboot automatically again. Don't worry, it is ok because it installs your efs.img.
Click to expand...
Click to collapse
Method 3 - restore .tar.gz backup
This method will restore .tar.gz backup.
A tar.gz backup should look like this(On some devices there might be more files, but this picture was taken from Note II N7100 backup and it fully works):
If you have like this, continue to the guide:
Create on your Phone Memory(Not Extrenal sd!!) a folder called "efsbackup"(without quotes)
Copy all files & folders from the EFS backup into "efsbackup" folder(The files are like in the picture)
Download this script & copy it to your device:
http://d-h.st/zwR
Reboot into recovery
Go to mount section and click on(Very important!):
Mount /efs
Click to expand...
Click to collapse
Now install the script you have downloaded.
After it finishes, reboot.
Now everything should be fixed, of course if your backup is 100% ok.
If it doesn't work, try method 4.
Click to expand...
Click to collapse
Method 4 - restore .tar.gz backup
This method will restore .tar.gz backup.
A tar.gz backup should look like this(On some devices there might be more files, but this picture was taked from Note II N7100 backup and it fully works):
If you have like this, continue to the guide:
Create on your Phone Memory(Not Extrenal sd!!) a folder called "efsbackup"(without quotes)
Copy all files & folders from the EFS backup into "efsbackup" folder(The files are like in the picture)
Using root explorer, go to "efsbackup folder, select all files & folders there, and click Copy.
Still in root explorer, go to "efs" folder of your device(It is located where all main folders like data, system, etc.).
In "efs" folder, click paste. It will ask you if you want to replace your files, select replace to all files(So all your files from "efsbackup" folder will be in "efs" folder)
Now open terminal emulator
Write the following:
Code:
su
Then click enter. It will ask for super user permission, give it permissions.
Now write:
Code:
busybox chown 1001:1001 /efs/nv_data.bin
Then click enter.
Now write:
Code:
busybox chmod 06755 /efs/nv_data.bin
Then click enter.
Reboot device. Now everything should work.
Click to expand...
Click to collapse
Exit "Permanent Safe Mode"
When you in "Permanent Safe Mode" situation, it means that your EFS folder is broken.
If you succeeded in restoring your IMEI and you still stuck in this Safe Mode, use this guide:
Method 1
Open root explorer.
Navigate to /efs/FactoryApp/
Open "factorymode" file as Text and edit it:
Change this:
Code:
OFF
To:
Code:
ON
Open "keystr" file as Text and edit it:
Change this:
Code:
OFF
To:
Code:
ON
Reboot device.
Click to expand...
Click to collapse
Method 2
Open Terminal emulator
Write the following:
Code:
su
Then click enter. It will ask for super user permission, give it permissions.
Write the following & click enter:
Code:
rm /efs/FactoryApp/keystr
Write the following & click enter:
Code:
rm /efs/FactoryApp/factorymode
Write the following & click enter:
Code:
echo -n ON >> /efs/FactoryApp/keystr
Write the following & click enter:
Code:
echo -n ON >> /efs/FactoryApp/factorymode
Write the following & click enter:
Code:
chown 1000.1000 /efs/FactoryApp/keystr
Write the following & click enter:
Code:
chown 1000.1000 /efs/FactoryApp/factorymode
Write the following & click enter:
Code:
chmod 0744 /efs/FactoryApp/keystr
Write the following & click enter:
Code:
chmod 0744 /efs/FactoryApp/factorymode
Reboot your device
Click to expand...
Click to collapse
This is all I can do for you friends, Worked alot on these methods to give you the best information.
Each method was tested by me and fully works.
If this helped you please press the "Thanks" button & Rate this thread 5 Stars.
If you like & appreciate my work please consider a donation!
Credits:
shnizlon
Candanga
A.S._id
dhiru1602
UtkarshGupta
P.M If you think that I forgot you
XDA:DevDB Information
Backup & Restore EFS + Get out from Permanent Safe mode - I9505, a Tool/Utility for the Samsung Galaxy S 4
Contributors
tamirda
Version Information
Status: Stable
Created 2013-09-05
Last Updated 2013-09-05

Amm i guess no one need it?

they do need it and i for one would like to thank you for the guide and time and effort in sharing ..mods and fixes are always welcome on xda thanks man:thumbup::thumbup:
Sent from my GT-I9505 using XDA Premium 4 mobile app

port76 said:
they do need it and i for one would like to thank you for the guide and time and effort in sharing ..mods and fixes are always welcome on xda thanks man:thumbup::thumbup:
Sent from my GT-I9505 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks first real comment in the thread
Sent from my GT-N7100 boosted by PhoeniX ROM

:thumbup:its ok any time my friend ....iv told my friends about the fix and I'm sure they will pop into this very useful and informative thread .. Thanks again iv added it to my subscribed topics and I'm sure people will be popping in to view and post on the thread thanks :thumbup::thumbup:
Sent from my GT-I9505 using XDA Premium 4 mobile app

Nice guide, the command line is the best! :good:

Will heimdall work as an alternative to restore the efs.img? Like this: heimdall flash --efs efs.img ?
It is used from download mode, like odin, so would work even if you cannot boot.

This Method, in Moto x?
tamirda said:
Note to forum managers: Please make it a Sticky Thread, It should help to all users and there is no use for this tutorial if it is in page 3
Hello XDA Users,
I think some people here know who I am, so I will jump on the "Introduction of myself" for now.
Recently, I have faced many questions & problem of fake IMEI, of damaged EFS folder. So I made a little experiment on my device(GN2).
First, I backuped my EFS folder in 2 types - one is .img and the second is tar.gz.
Then, I deleted my EFS folder using ES Root Explorer. Which made my device to be on somethine called "Permanent Safe Mode" - You can not get out untill you fix your EFS folder and change some values.
This is permanent safe mode:
After I did my "research" I have managed to make several methods to backup & restore EFS, which should make your life easier and better.
First of all, Disclaimer:
I'm not responsible for any damage caused by using these methods, all methods tested by me, so it should work on your device too.
This is for I9505 Only!!!!!!!
Let's continue.
What you must have:
Latest base with latest modem and latest kernel - very important since in the latest versions samsung prevented the option to install old modems/kernels, so if you install old kernell/modem it can show you wrong IMEI.
Rooted device with the latest Super User
Latest busybox
PhilZ Recovery
Terminal Emulator
Root explorer - Can be ES File Explorer with working root option or just a root explorer from the market
A working EFS backup(In order to restore it...)
Time & Patient.
Important Notes:
When installing/downgrading firmwares, several people suffered from Fake IMEI. This is because the new firmware messed up your EFS folder, which means that you can not restore EFS backup until you are on the latest version, latest modem and latest stock kernel, recommended is XXUBMH1(right to 05/09/2013)
Some custom roms include modem installation in their rom installer. Due to modem flashing in recovery, some devices might get Fake IMEI. My recommendation is before even starting to use this guide, please try to install the latest modem via odin from this thread:
http://forum.xda-developers.com/showthread.php?t=2192025
When installing modem via odin, make sure you select PHONE and not PDA
You will find at least one method that works on your device, so don't give up after one method.
Read all guide and pay attention to all small details.
Backup methods
Method 1 - .img backup
First method, is an automatic backup/restore software.
Special thanks to A.S._id for his software.
The software:
Method 2 - .img backup
Method number 2 will create you efs.img backup on your internal sd. After that you can copy it to your computer.
What you have to do is this:
Method 3 - .tar.gz backup
This method will compress your efs folder into tar.gz file. This method is the same as choosing backup EFS folder in my rom(PhoeniX ROM)/Omega/Wanam/etc.
A tar.gz backup should look like this(On some devices there might be more files, but this picture was taken from Note II N7100 backup and it fully works):
What you have to do is this:
Restore methods
Now the fun begins
You will have to restore your backup when you have one or more of the folowing problem:
Fake IMEI (usually 004999010640000) or "null" IMEI
Blinking SIM card icon on the top tray… ETC
Unable to unlock your SIM card using your PIN
Fake Serial Number (usually 0000000) or "null" Serial
Unable to register to the network (usually comes with Fake IMEI & Fake Serial so check them.)
Attention please,
If you are 100% that your EFS folder is damaged and you have a working EFS backup with the right IMEI number, my recommendation is this:
Method 1 - restore .img backup
First method, is an automatic backup/restore software.
Special thanks to A.S._id for his software.
The software:
Method 2 - Restore .img backup
Method number 2 will restore your efs.img backup from your internal sd.
What you have to do is this:
Method 3 - restore .tar.gz backup
This method will restore .tar.gz backup.
A tar.gz backup should look like this(On some devices there might be more files, but this picture was taken from Note II N7100 backup and it fully works):
If you have like this, continue to the guide:
Method 4 - restore .tar.gz backup
This method will restore .tar.gz backup.
A tar.gz backup should look like this(On some devices there might be more files, but this picture was taked from Note II N7100 backup and it fully works):
If you have like this, continue to the guide:
Exit "Permanent Safe Mode"
When you in "Permanent Safe Mode" situation, it means that your EFS folder is broken.
If you succeeded in restoring your IMEI and you still stuck in this Safe Mode, use this guide:
Method 1
Method 2
This is all I can do for you friends, Worked alot on these methods to give you the best information.
Each method was tested by me and fully works.
If this helped you please press the "Thanks" button & Rate this thread 5 Stars.
If you like & appreciate my work please consider a donation!
Credits:
shnizlon
Candanga
A.S._id
dhiru1602
UtkarshGupta
P.M If you think that I forgot you
XDA:DevDB Information
Backup & Restore EFS + Get out from Permanent Safe mode - I9505, a Tool/Utility for the Samsung Galaxy S 4
Contributors
tamirda
Version Information
Status: Stable
Created 2013-09-05
Last Updated 2013-09-05
Click to expand...
Click to collapse
Mr Tamirda
The method this, made in terminal, working in one moto x? it's my question

Pika71 said:
Mr Tamirda
The method this, made in terminal, working in one moto x? it's my question
Click to expand...
Click to collapse
?????

slugthru said:
Will heimdall work as an alternative to restore the efs.img? Like this: heimdall flash --efs efs.img ?
It is used from download mode, like odin, so would work even if you cannot boot.
Click to expand...
Click to collapse
You can try and share your experiences.
From my personal experience with another device the dd method in terminal works just fine

Sorry but null IMEI isn't fake IMEI
Difference:
Null IMEI means you don't even have any data for the IMEI oh and it's bad!
fake IMEI means you do have a data which is corrupt. Nothing more only digits has been changed.
There's a different between those
I remember having null IMEI and my backup didn't help at all service center was forced to swap motherboard to get IMEI working.
---------- Post added at 02:26 PM ---------- Previous post was at 02:26 PM ----------
Pika71 said:
Mr Tamirda
The method this, made in terminal, working in one moto x? it's my question
Click to expand...
Click to collapse
It depends if it uses same permission. Also there is a way to fix a corrupt IMEI while in recovery
Also don't quote whole op

My brothers phone is in safe mode could i backup my efs folder and restore onto his device?

ok, i am stuck in factory mode but none of the methods described work because there is nothing in my efs folder - it is empty so there are no files to actually edit.

Related

Cannot connect to mobile network???

Hello, this is really weird. In fact, when I insert the SIM to my Note 2 N7100 and turn it on, it allows me to make emergency call, but I cannot use it to make any others and it doesn't show the carrier name (it shows Emergency call only). And when I try to use it to make normal phone calls, it says that I am not registered to a mobile network. I try to factory reset my phone, but the problem remains. I then try to remove the SIM card, and it says that I need to insert a SIM card (that means that it is not a hardware problem since it recognizes the card). I then try to go to the mobile network setting to try to connect to the network manually, it connects me but it shows me a warning which says that the mobile network service is not available (and the Emergency call only label remains). However, I am sure that this is not the problem of the card neither since when I insert the card to my Moto MB860, I can make calls as usual. So, what is the problem ??? It seems to me that the problem happens spontaneously since it works perfectly until yesterday. And all other wireless function works fine including wifi , Bluetooth and GPS and the only thing goes wrong is 3g and 2g.
Additional information:
ROM: Omega v.16
Carrier: Fido Canada (as you can see)
Thanks.
First of all, check whether you can see the IMEI of the device. If you can see.
1. Contact your network operator and check whether your IMEI is blacklisted or not.
If you cannot see the IMEI
1.Restore the efs and persist backups (if you have one)
2. flash the device again with the modem image (download the firmware of your device from samfirmwares.com, delete everything from the .tar file except modem.bin, and then flash this file to the phone with Odin (you can get Odin and instructions from that site or from here)
2. maybe your nv_data.bin file or /efs directory got corrupted, make a backup of the folder, then simply delete nv_data.bin, it will be recreated for you.
For this, you’ll need root. If you have a root-enabled kernel, you only have to install the Superuser app and Busybox on the phone, download the Android SDK to your PC, install platform-tools in the SDK manager, go to the platform-tools directory and start adb shell.
In the shell, type su, wait for the Superuser prompt to appear on the phone (if it does not appear, open the Superuser app and try executing su again), enable root access for the command. Now go to /efs, copy everything to for example /sdcard/efs, then rm nv_data.bin.
Reflashing the device with a kernel and checking “phone EFS clear” in Odin also works (make sure you made a backup of the EFS folder just in case).
3. you can try changing the CSC: enter *#272*imei# on the phone tab.
Try this . I'm not sure it works. Just give it a try on yourself.
Trying the above mentioned methods could be vulnerable to your phone if it not done properly. So do it carefully. If you have any doubts feel free to ask me or search elsewhere. But, don't blame me for a fully dead phone. I am not at all responsible for any...
Noob 1st post......have had similar problems with koodo CDN
Not gonna give such an in depth suggestion as above.....he's something simple to try.
I live in a dead zone and often my phone ( galaxyAce) will switch to no service. Even after refreshing and selecting network under settings, it says it's connected, but isn't. A simple apk that always fixes the problem for me is Network Signal Booster @ theplaystore
jabrif said:
First of all, check whether you can see the IMEI of the device. If you can see.
1. Contact your network operator and check whether your IMEI is blacklisted or not.
If you cannot see the IMEI
1.Restore the efs and persist backups (if you have one)
2. flash the device again with the modem image (download the firmware of your device from samfirmwares.com, delete everything from the .tar file except modem.bin, and then flash this file to the phone with Odin (you can get Odin and instructions from that site or from here)
2. maybe your nv_data.bin file or /efs directory got corrupted, make a backup of the folder, then simply delete nv_data.bin, it will be recreated for you.
For this, you’ll need root. If you have a root-enabled kernel, you only have to install the Superuser app and Busybox on the phone, download the Android SDK to your PC, install platform-tools in the SDK manager, go to the platform-tools directory and start adb shell.
In the shell, type su, wait for the Superuser prompt to appear on the phone (if it does not appear, open the Superuser app and try executing su again), enable root access for the command. Now go to /efs, copy everything to for example /sdcard/efs, then rm nv_data.bin.
Reflashing the device with a kernel and checking “phone EFS clear” in Odin also works (make sure you made a backup of the EFS folder just in case).
3. you can try changing the CSC: enter *#272*imei# on the phone tab.
Try this . I'm not sure it works. Just give it a try on yourself.
Trying the above mentioned methods could be vulnerable to your phone if it not done properly. So do it carefully. If you have any doubts feel free to ask me or search elsewhere. But, don't blame me for a fully dead phone. I am not at all responsible for any...
Click to expand...
Click to collapse
I tried a simple way which is format everything and flash another ROM but the problem remains.
TRS_80 said:
Noob 1st post......have had similar problems with koodo CDN
Not gonna give such an in depth suggestion as above.....he's something simple to try.
I live in a dead zone and often my phone ( galaxyAce) will switch to no service. Even after refreshing and selecting network under settings, it says it's connected, but isn't. A simple apk that always fixes the problem for me is Network Signal Booster @ theplaystore
Click to expand...
Click to collapse
I don't know that we are in the same situation since at home I often got a good signal and this happened to me only since yesterday.
jabrif said:
First of all, check whether you can see the IMEI of the device. If you can see.
1. Contact your network operator and check whether your IMEI is blacklisted or not.
If you cannot see the IMEI
1.Restore the efs and persist backups (if you have one)
2. flash the device again with the modem image (download the firmware of your device from samfirmwares.com, delete everything from the .tar file except modem.bin, and then flash this file to the phone with Odin (you can get Odin and instructions from that site or from here)
2. maybe your nv_data.bin file or /efs directory got corrupted, make a backup of the folder, then simply delete nv_data.bin, it will be recreated for you.
For this, you’ll need root. If you have a root-enabled kernel, you only have to install the Superuser app and Busybox on the phone, download the Android SDK to your PC, install platform-tools in the SDK manager, go to the platform-tools directory and start adb shell.
In the shell, type su, wait for the Superuser prompt to appear on the phone (if it does not appear, open the Superuser app and try executing su again), enable root access for the command. Now go to /efs, copy everything to for example /sdcard/efs, then rm nv_data.bin.
Reflashing the device with a kernel and checking “phone EFS clear” in Odin also works (make sure you made a backup of the EFS folder just in case).
3. you can try changing the CSC: enter *#272*imei# on the phone tab.
Try this . I'm not sure it works. Just give it a try on yourself.
Trying the above mentioned methods could be vulnerable to your phone if it not done properly. So do it carefully. If you have any doubts feel free to ask me or search elsewhere. But, don't blame me for a fully dead phone. I am not at all responsible for any...
Click to expand...
Click to collapse
Some updates;
- IMEI is checked.
- I do not have any efs backup
- nv_data.bin has been deleted and recreated
- trying to register for the firmware
- My phone is always rooted.
Dan Law 001 said:
Some updates;
- IMEI is checked.
- I do not have any efs backup
- nv_data.bin has been deleted and recreated
- trying to register for the firmware
- My phone is always rooted.
Click to expand...
Click to collapse
Results..??
Sent from my GT-I9001 using xda premium
jabrif said:
Results..??
Sent from my GT-I9001 using xda premium
Click to expand...
Click to collapse
I need to get the firmware first... since I already passed the download quota for today... need to wait until tomorrow...
Mmm... I heard that you mentioned clearing the EFS in your given procedure, but I do not think that I modified that folder... However, about few days ago, since I want to gain better control on the volume on my headphone remotes, I did modify the file called Generic.kl in system/usr/keylayout, but I restore it after since it didn't work. However, I don't think that this modification will trigger something in the efs folder since it has different directory. By the way, I did some research online and they say that the efs contains information about the carrier on the phone, so will there's a greater chance that the problem is caused by the possible modification on the efs than any other factor and will there also something else that possibly trigger the similar effects?
Sent from my GT-N7100 using xda premium
Still nothing

[Tools][How-To][Guides] Backup & Restore EFS + Get out from Permanent Safe mode

Note to forum managers: Please make it a Sticky Thread, It should help to all users and there is no use for this tutorial if it is in page 3
Hello XDA Users,
I think some people here know who I am, so I will jump on the "Introduction of myself" for now.
Recently, I have faced many questions & problem of fake IMEI, of damaged EFS folder. So I made a little experiment on my device(GN2).
First, I backuped my EFS folder in 2 types - one is .img and the second is tar.gz.
Then, I deleted my EFS folder using ES Root Explorer. Which made my device to be on somethine called "Permanent Safe Mode" - You can not get out untill you fix your EFS folder and change some values.
This is permanent safe mode:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After I did my "research" I have managed to make several methods to backup & restore EFS, which should make your life easier and better.
First of all, Disclaimer:
I'm not responsible for any damage caused by using these methods, all methods tested by me, so it should work on your device too.
This is for I9500 Only!!!!!!!
Let's continue.
What you must have:
Latest base with latest modem and latest kernel - very important since in the latest versions samsung prevented the option to install old modems/kernels, so if you install old kernell/modem it can show you wrong IMEI.
Rooted device with the latest Super User
Latest busybox
CWM / PhilZ Recovery
Terminal Emulator
Root explorer - Can be ES File Explorer with working root option or just a root explorer from the market
A working EFS backup(In order to restore it...)
Time & Patient.
Important Notes:
When installing XWUBMG5, several people suffered from Fake IMEI. This is because the new firmware messed up your EFS folder, which means that you can not restore EFS backup until you are on older version, recommended is XXUBMG9(right to 05/08/2013)
Some custom roms include modem installation in their rom installer. Due to modem flashing in recovery, some devices might get Fake IMEI. My recommendation is before even starting to use this guide, please try to install the latest modem via odin from this thread:
http://forum.xda-developers.com/showthread.php?t=2192025
You will find at least one method that works on your device, so don't give up after one method.
Note II & S4 has the same EFS partition (mmcblk0p3), All methods were checked by me on my Note II and fully work. So it should work on S4 too. At least 90% of them
Read all guide and pay attention to all small details.
Backup methods
Method 1 - .img backup
First method, is an automatic backup/restore software.
Special thanks to A.S._id for his software.
Original thread:
http://forum.xda-developers.com/showthread.php?t=2430177&nocache=1&styleid=19
The software:
A.S._id said:
SAMSUNG_I9500_EFS_BACKUP_RESTORE_AUTOMATIC
Instructions:
! Need for backup Root access, debugging USB and busybox
1. Extract from the zip and run. Bat file
2. Is okay to your PC and follow the menu
Automatically create a text file of all the parameters of the device at the time of the copy
Automatic backup of efs:
* Odin flash file. Tar.md5,
* raw.img
* Tar.gz archive
Automatic naming of files and backup archive version of the firmware
Restore to choose from archives and backup images
Automatic start of Odin and the transition to the flashing mode when selecting Odin Restore
DOWNLOAD
Thanks to:
shoma_81, tester99,
For help and assist in the creation of tool
p.s. * Deposit assured recovery - to have the device firmware version corresponding to the backup copy
Click to expand...
Click to collapse
Method 2 - .img backup
Method number 2 will create you efs.img backup on your internal sd. After that you can copy it to your computer.
What you have to do is this:
Open terminal emulator
Write the following:
Code:
su
Then click enter. It will ask for super user permission, give it permissions.
Then write:
Code:
dd if=/dev/block/mmcblk0p3 of=/sdcard/efs.img bs=4096
Then click enter.
When it finishes, check if you have efs.img on your phone memory. If so, copy it to comupter, if not, you did something wrong try again.
Click to expand...
Click to collapse
Method 3 - .tar.gz backup
This method will compress your efs folder into tar.gz file. This method is the same as choosing backup EFS folder in my rom(PhoeniX ROM)/Omega/Wanam/etc.
A tar.gz backup should look like this(On some devices there might be more files, but this picture was taken from Note II N7100 backup and it fully works):
What you have to do is this:
Download this and copy it to your device:
http://d-h.st/f4I
Reboot into recovery
Flash the zip
Reboot your device.
Connect your device to your pc, and copy the backup in "efs_backup" folder.
Click to expand...
Click to collapse
Restore methods
Now the fun begins
You will have to restore your backup when you have one or more of the folowing problem:
Fake IMEI (usually 004999010640000) or "null" IMEI
Blinking SIM card icon on the top tray… ETC
Unable to unlock your SIM card using your PIN
Fake Serial Number (usually 0000000) or "null" Serial
Unable to register to the network (usually comes with Fake IMEI & Fake Serial so check them.)
Attention please,
If you are 100% that your EFS folder is damaged and you have a working EFS backup with the right IMEI number, my recommendation is this:
With root explorer, go to your efs folder and delete all files inside
Long press on power button will turn off your device.
Then turn on the device, you will be in "Permanent Safe Mode".
Continue to one of the following methods.
Click to expand...
Click to collapse
Method 1 - restore .img backup
First method, is an automatic backup/restore software.
Special thanks to A.S._id for his software.
Original thread:
http://forum.xda-developers.com/showthread.php?t=2430177&nocache=1&styleid=19
The software:
A.S._id said:
SAMSUNG_I9500_EFS_BACKUP_RESTORE_AUTOMATIC
Instructions:
! Need for backup Root access, debugging USB and busybox
1. Extract from the zip and run. Bat file
2. Is okay to your PC and follow the menu
Automatically create a text file of all the parameters of the device at the time of the copy
Automatic backup of efs:
* Odin flash file. Tar.md5,
* raw.img
* Tar.gz archive
Automatic naming of files and backup archive version of the firmware
Restore to choose from archives and backup images
Automatic start of Odin and the transition to the flashing mode when selecting Odin Restore
DOWNLOAD
Thanks to:
shoma_81, tester99,
For help and assist in the creation of tool
p.s. * Deposit assured recovery - to have the device firmware version corresponding to the backup copy
Click to expand...
Click to collapse
Method 2 - Restore .img backup
Method number 2 will restore your efs.img backup from your internal sd.
What you have to do is this:
Put your efs.img on your phone memory(not external sd card!) in the main memory, not inside folder.
Open terminal emulator
Write the following:
Code:
su
Then click enter. It will ask for super user permission, give it permissions.
Then write:
Code:
dd if=/sdcard/efs.img of=/dev/block/mmcblk0p3 bs=4096
Then click enter.
Now, reboot your device. If you still don't have IMEI/You are still in Safe Mod, reboot again.
In the second reboot, the bootanimation might stuck and the device will reboot automatically again. Don't worry, it is ok because it installs your efs.img.
Click to expand...
Click to collapse
Method 3 - restore .tar.gz backup
This method will restore .tar.gz backup.
A tar.gz backup should look like this(On some devices there might be more files, but this picture was taken from Note II N7100 backup and it fully works):
If you have like this, continue to the guide:
Create on your Phone Memory(Not Extrenal sd!!) a folder called "efsbackup"(without quotes)
Copy all files & folders from the EFS backup into "efsbackup" folder(The files are like in the picture)
Download this script & copy it to your device:
http://d-h.st/XcL
Reboot into recovery
Go to mount section and click on(Very important!):
Mount /efs
Click to expand...
Click to collapse
Now install the script you have downloaded.
After it finishes, reboot.
Now everything should be fixed, of course if your backup is 100% ok.
If it doesn't work, try method 4.
Click to expand...
Click to collapse
Method 4 - restore .tar.gz backup
This method will restore .tar.gz backup.
A tar.gz backup should look like this(On some devices there might be more files, but this picture was taked from Note II N7100 backup and it fully works):
If you have like this, continue to the guide:
Create on your Phone Memory(Not Extrenal sd!!) a folder called "efsbackup"(without quotes)
Copy all files & folders from the EFS backup into "efsbackup" folder(The files are like in the picture)
Using root explorer, go to "efsbackup folder, select all files & folders there, and click Copy.
Still in root explorer, go to "efs" folder of your device(It is located where all main folders like data, system, etc.).
In "efs" folder, click paste. It will ask you if you want to replace your files, select replace to all files(So all your files from "efsbackup" folder will be in "efs" folder)
Now open terminal emulator
Write the following:
Code:
su
Then click enter. It will ask for super user permission, give it permissions.
Now write:
Code:
busybox chown 1001:1001 /efs/nv_data.bin
Then click enter.
Now write:
Code:
busybox chmod 06755 /efs/nv_data.bin
Then click enter.
Reboot device. Now everything should work.
Click to expand...
Click to collapse
Exit "Permanent Safe Mode"
When you in "Permanent Safe Mode" situation, it means that your EFS folder is broken.
If you succeeded in restoring your IMEI and you still stuck in this Safe Mode, use this guide:
Method 1
Open root explorer.
Navigate to /efs/FactoryApp/
Open "factorymode" file as Text and edit it:
Change this:
Code:
OFF
To:
Code:
ON
Open "keystr" file as Text and edit it:
Change this:
Code:
OFF
To:
Code:
ON
Reboot device.
Click to expand...
Click to collapse
Method 2
Open Terminal emulator
Write the following:
Code:
su
Then click enter. It will ask for super user permission, give it permissions.
Write the following & click enter:
Code:
rm /efs/FactoryApp/keystr
Write the following & click enter:
Code:
rm /efs/FactoryApp/factorymode
Write the following & click enter:
Code:
echo -n ON >> /efs/FactoryApp/keystr
Write the following & click enter:
Code:
echo -n ON >> /efs/FactoryApp/factorymode
Write the following & click enter:
Code:
chown 1000.1000 /efs/FactoryApp/keystr
Write the following & click enter:
Code:
chown 1000.1000 /efs/FactoryApp/factorymode
Write the following & click enter:
Code:
chmod 0744 /efs/FactoryApp/keystr
Write the following & click enter:
Code:
chmod 0744 /efs/FactoryApp/factorymode
Reboot your device
Click to expand...
Click to collapse
This is all I can do for you friends, Worked alot on these methods to give you the best information.
Each method was tested by me and fully works.
If this helped you please press the "Thanks" button.
If you like & appreciate my work please consider a donation!
Credits:
shnizlon
Candanga
A.S._id
dhiru1602
UtkarshGupta
P.M If you think that I forgot you
XDA:DevDB Information
Backup & Restore EFS + Get out from Permanent Safe mode I9500, a Tool/Utility for the Samsung Galaxy S 4
Contributors
tamirda
Version Information
Status: Stable
Created 2013-09-05
Last Updated 2013-09-05
Awesome my friend 5 stars hit, I will link you in my post.
I hope people read in detail and take precautions
Hugs
Sent from my GT-I9500
Crash 1976 said:
Awesome my friend 5 stars hit, I will link you in my post.
I hope people read in detail and take precautions
Hugs
Sent from my GT-I9500
Click to expand...
Click to collapse
Thank you my friend,
In my note II I did like 20 backups before I deleted my EFS folder around 20 times ahah.
People should be aware that samsung is trying to mess up our devices.
Thank you Tarmida, This is the best userful topic ever for my S4 :good:. This will saving many lives of XDA member :good:
Excellent my friend tamirda! :good:
regards!
5 stars! and sticky please!
great topic and guide tamir.5 stars from me :thumbup: will help me a lot if i get stuck with any prob like before arghhhh
Sent from my GT-N7000 using Tapatalk 2
galza said:
great topic and guide tamir.5 stars from me :thumbup: will help me a lot if i get stuck with any prob like before arghhhh
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
I am happy to help you any time
» Arrow « said:
Excellent my friend tamirda! :good:
regards!
5 stars! and sticky please!
Click to expand...
Click to collapse
Thank you friend!
bafknight said:
Thank you Tarmida, This is the best userful topic ever for my S4 :good:. This will saving many lives of XDA member :good:
Click to expand...
Click to collapse
Thank you friend, and yes this can be very useful for alot of users.
Sent from my GT-N7100 using xda app-developers app
@tamirda
Hi I'm using crash rom 5.5
I made full wipe and flash MG5
By odin and now I have fake imei
I restore crash rom 5.5 backup from cwm and the problem still exsist
I don't make EFS backup before
How to fix it ?
Sent From my i9500 With Crash Rom
--------------------------------
ادعوا لي بالتوفيق في امتحاناتي
wish me good luck for my exams
AL_IRAQI said:
@tamirda
Hi I'm using crash rom 5.5
I made full wipe and flash MG5
By odin and now I have fake imei
I restore crash rom 5.5 backup from cwm and the problem still exsist
I don't make EFS backup before
How to fix it ?
Sent From my i9500 With Crash Rom
--------------------------------
ادعوا لي بالتوفيق في امتحاناتي
wish me good luck for my exams
Click to expand...
Click to collapse
Hello,
It seems that crash backuped your Fake IMEI.
Something that I thing it might help, helped for some other, download latest modem from here:
http://forum.xda-developers.com/showthread.php?t=2192025
install it as a Phone in Odin.
it is importand to mark phone, and flash via odin.
Then try..
If you don't have any other backup, I think you might have to use your warranty.
When I backup the rom I forget my phone in flight mode maybe this the reason why I lost my imei ?
And my baseband now is
I9500DDUBMF8
+Edit
I found these in my internal storage
The First One From Crash Rom 5.0
And The Second From Stock MG5 Where I have fake imei
Sent From my i9500 With Crash Rom
--------------------------------
ادعوا لي بالتوفيق في امتحاناتي
wish me good luck for my exams
AL_IRAQI said:
When I backup the rom I forget my phone in flight mode maybe this the reason why I lost my imei ?
And my baseband now is
I9500DDUBMF8
Sent From my i9500 With Crash Rom
--------------------------------
ادعوا لي بالتوفيق في امتحاناتي
wish me good luck for my exams
Click to expand...
Click to collapse
I don't think there is connection between these two.
Downlaod this:
http://d-h.st/esG
Open odin, Select Phone, select the modem's tar, connect phoen and flash.
After that check if you have IMEI.
If not, Try to install stock XXUBMG9 or XXUBMG5 - If you had MG5 before, it seems that you can not downgrade your phone, so try to install MG5.
If after MG5 there is still no IMEI,
Flash again as Phone via odin this modem:
http://d-h.st/Xxk
If still there is no IMEI, try to restore your current EFS backup.(Make sure you have Root and busybox and all I asked in the main thread)
If after that no IMEI,
Restore to stock and use warranty( make a story that you woke up one morning and you couldn't conect to your network, and you tried to mnake factory reset and still it didn't help)
Good luck
tamirda said:
I don't think there is connection between these two.
Downlaod this:
http://d-h.st/esG
Open odin, Select Phone, select the modem's tar, connect phoen and flash.
After that check if you have IMEI.
If not, Try to install stock XXUBMG9 or XXUBMG5 - If you had MG5 before, it seems that you can not downgrade your phone, so try to install MG5.
If after MG5 there is still no IMEI,
Flash again as Phone via odin this modem:
http://d-h.st/Xxk
If still there is no IMEI, try to restore your current EFS backup.(Make sure you have Root and busybox and all I asked in the main thread)
If after that no IMEI,
Restore to stock and use warranty( make a story that you woke up one morning and you couldn't conect to your network, and you tried to mnake factory reset and still it didn't help)
Good luck
Click to expand...
Click to collapse
Thanks I'll Try These Method
If not working I'll use my warranty
EDIT
I directly flash I9500_UBUBMG9_MODEM
And know it's work fine with me
I Should Try it before ask sorry for that
this is the first time I have this problem
Thank you very much
Sent From my i9500 With Crash Rom
AL_IRAQI said:
Thanks I'll Try These Method
If not working I'll use my warranty
EDIT
I directly flash I9500_UBUBMG9_MODEM
And know it's work fine with me
I Should Try it before ask sorry for that
this is the first time I have this problem
Thank you very much
Sent From my i9500 With Crash Rom
Click to expand...
Click to collapse
Hi mate,
First of all,
I am more than happy that I helped you.
Second, this is ok to ask questions, that is why I am here.
Now backup at leat 5 times your EFS .img & tar.gz.
Enjoy!
tamirda said:
Hi mate,
First of all,
I am more than happy that I helped you.
Second, this is ok to ask questions, that is why I am here.
Now backup at leat 5 times your EFS .img & tar.gz.
Enjoy!
Click to expand...
Click to collapse
I backup 3 times with every method
Thanks
Sent From my i9500 With Crash Rom
--------------------------------
ادعوا لي بالتوفيق في امتحاناتي
wish me good luck for my exams
Awesome guide.
Burned up whole weekend over the issue and now fixed my issue following the guide.
Cannot thank you enough man!
Regards,
Pdash
pdash79 said:
Awesome guide.
Burned up whole weekend over the issue and now fixed my issue following the guide.
Cannot thank you enough man!
Regards,
Pdash
Click to expand...
Click to collapse
I am happy to help & hear that you succeed in restoring IMEI.
Sent from my GT-N7100 using xda app-developers app
I read your post, all most the method use terminal emulator, so what is that ?, and can you give me link of that ?
thanks you very much
daogiahieu said:
I read your post, all most the method use terminal emulator, so what is that ?, and can you give me link of that ?
thanks you very much
Click to expand...
Click to collapse
Linux command line shell on Android. Here's it, mate https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=vi
Thanxs @tamirda
I could see everyday a new post related to messed up EFS folder.
It would surely help people out
Anyhow i had already backed up mine using the EFS professional Software. Is it enough or should i backup using your methods also?
manu44 said:
Thanxs @tamirda
I could see everyday a new post related to messed up EFS folder.
It would surely help people out
Anyhow i had already backed up mine using the EFS professional Software. Is it enough or should i backup using your methods also?
Click to expand...
Click to collapse
I think it is enough, depands on your feeling

modem DME4, DMF1

Hello everyone I have a problem with note 2
he flashed the modem DMF1, DME4 and recognizes them with the restore efs folder but when I reboot is imei null and baseband unknown
Solutions?
héllo
in first sorry for my english :silly:
backup your efs file
I made a RAR file with the 2 modem inside
unzip it on the pc or the phone
put the zip files in the sd card
flash via recovery
DMF1_MODEM modem_XXDME4 rar
jioan62 said:
héllo
in first sorry for my english :silly:
backup your efs file
I made a RAR file with the 2 modem inside
unzip it on the pc or the phone
put the zip files in the sd card
flash via recovery
DMF1_MODEM modem_XXDME4 rar
Click to expand...
Click to collapse
thanks for the reply
I will try to flash them, she takes it but when I restart then returns null imei
I do not understand why
mysterionTM said:
thanks for the reply
I will try to flash them, she takes it but when I restart then returns null imei
I do not understand why
Click to expand...
Click to collapse
I already discuseed this, you need to restore your EFS backup after you flash the ROM that you made the backup with.
so flash XXDMF1 with ROM XXDME6 (or DXDMF1) and then restore EFS.
if that didn't work. then flash XXDME4 then OTA update will give you XXDMF1.
If you can't recieve OTA updates and you have Root, then tell me so I send you my XXDMF1 and DME6. (dr.ketan has DXDMF1 which you must try first).
After every flash restore efs then restart to see if it is fixed.
thethiny said:
I already discuseed this, you need to restore your EFS backup after you flash the ROM that you made the backup with.
so flash XXDMF1 with ROM XXDME6 (or DXDMF1) and then restore EFS.
if that didn't work. then flash XXDME4 then OTA update will give you XXDMF1.
If you can't recieve OTA updates and you have Root, then tell me so I send you my XXDMF1 and DME6. (dr.ketan has DXDMF1 which you must try first).
After every flash restore efs then restart to see if it is fixed.
Click to expand...
Click to collapse
if you can put him I would be grateful
but then there is no way to have permanent XXDME4?
With the other note 2 had managed to get it going with this I can not
@mysterionTM
hello
take this and flash via odin pc and updates via OTA or KIES but after do backup efs file
/N7100XXDMB6_N7100OXADMB1_XEF.zip
mysterionTM said:
if you can put him I would be grateful
but then there is no way to have permanent XXDME4?
With the other note 2 had managed to get it going with this I can not
Click to expand...
Click to collapse
first of all make sure your phone is rooted. then download mobile odin Pro (you need Pro version to maintain root or simply root again). then download this file:
http://www.mediafire.com/download/ena68zhyjhwpc78/update.zip
Edit: this will make your mobile a french mobile, so don't flash it just get someone to convert it to a modem.bin or modify it for your country.
now open mobile odin pro and flash the Stock ROM XXDME6.
after it finishes open mobile odin pro again and go to update file, and choose the file you downloaded above. then flash it.
you you have build number XXDME6 and buildbase XXDMF1
now restore EFS by using this app: https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=en
Code:
Put your EFS file on your mobile (External SD Card is preferred on the Root of the Card, so its location should be /storage/extSdCard/efs.img).
name it efs.img for easier use (if it was an img file).
now in the terminal type this:
SU
then grant it superuser permissions.
then type this:
dd if=/storage/extSdCard/efs.img of=/dev/block/mmcblk0p3 bs=4096
it will show you numbers if it was done correctly.
then reboot your phone and everything should work correctly. Reboot again to make sure.
In case it didn't work, then Flash the DME6 ROM, it should come with DXDMF1 , then try restoring EFS again.
tell me what happens with you.
@mysterionTM
what is your configuration of your phone? (your rom)
I put thanks to you both
thethiny said:
first of all make sure your phone is rooted. then download mobile odin Pro (you need Pro version to maintain root or simply root again). then download this file:
http://www.mediafire.com/download/ena68zhyjhwpc78/update.zip
Edit: this will make your mobile a french mobile, so don't flash it just get someone to convert it to a modem.bin or modify it for your country.
now open mobile odin pro and flash the Stock ROM XXDME6.
after it finishes open mobile odin pro again and go to update file, and choose the file you downloaded above. then flash it.
you you have build number XXDME6 and buildbase XXDMF1
now restore EFS by using this app: https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=en
Code:
Put your EFS file on your mobile (External SD Card is preferred on the Root of the Card, so its location should be /storage/extSdCard/efs.img).
name it efs.img for easier use (if it was an img file).
now in the terminal type this:
SU
then grant it superuser permissions.
then type this:
dd if=/storage/extSdCard/efs.img of=/dev/block/mmcblk0p3 bs=4096
it will show you numbers if it was done correctly.
then reboot your phone and everything should work correctly. Reboot again to make sure.
In case it didn't work, then Flash the DME6 ROM, it should come with DXDMF1 , then try restoring EFS again.
tell me what happens with you.
Click to expand...
Click to collapse
excellent guide compliments
but to have the modem DME4 there is no permanent way?
jioan62 said:
@mysterionTM
what is your configuration of your phone? (your rom)
Click to expand...
Click to collapse
DME6
your CSC ?
jioan62 said:
your CSC ?
Click to expand...
Click to collapse
ITVDMF1
go here
http://forum.xda-developers.com/showthread.php?t=1896696
jioan62 said:
go here
http://forum.xda-developers.com/showthread.php?t=1896696
Click to expand...
Click to collapse
I saw it but I was looking for a way to install the modem DME4
I do not understand why it goes and then restart imei returns null
should be something inherent in the nv_data.bin or nv_data.bin.md5
I was looking for a way to fix the folder efs
ITV N7100XXDME6 is this your rom ?
flash via odin pc
download this your stock rom http://hotfile.com/dl/229491057/c20905b/ITV-N7100XXDME6-20130605085627.zip.html
mysterionTM said:
I put thanks to you both
excellent guide compliments
but to have the modem DME4 there is no permanent way?
Click to expand...
Click to collapse
what do you mean permanent way? why would you need DME4 if you have a higher better one?
you can flash DME4 (it comes with ROM DMB4) modem alone and keep it permanently, but if your EFS backup was when you had anything other than DME4 then you can't use it anymore, you have to recover EFS everytime.
just use XXDMF1 (since your CSC is DMF1) and restore EFS. don't see any reason to use an old modem.
jioan62 said:
ITV N7100XXDME6 is this your rom ?
flash via odin pc
download this your stock rom http://hotfile.com/dl/229491057/c20905b/ITV-N7100XXDME6-20130605085627.zip.html
Click to expand...
Click to collapse
yes, it is my rom
but by flashing the stock rom does not solve anything......
thethiny said:
what do you mean permanent way? why would you need DME4 if you have a higher better one?
you can flash DME4 (it comes with ROM DMB4) modem alone and keep it permanently, but if your EFS backup was when you had anything other than DME4 then you can't use it anymore, you have to recover EFS everytime.
just use XXDMF1 (since your CSC is DMF1) and restore EFS. don't see any reason to use an old modem.
Click to expand...
Click to collapse
you're right but with the other note 2 that I had was in the same condition and and I managed to do it !
with this I can not ....
I was leaving the modem DMF1 and I was able to go to the modem DME4 without any problems
mysterionTM said:
yes, it is my rom
but by flashing the stock rom does not solve anything......
you're right but with the other note 2 that I had was in the same condition and and I managed to do it !
with this I can not ....
I was leaving the modem DMF1 and I was able to go to the modem DME4 without any problems
Click to expand...
Click to collapse
on your other phone , you had EFS backup on DME4. on this phone, your backup is on DMF1. DMF can read DME backups, but DME can't read DMF backups because samsung changed the EFS read type on DMF1. so once you go DMF1, your EFS partition is changed permanently!
thethiny said:
on your other phone , you had EFS backup on DME4. on this phone, your backup is on DMF1. DMF can read DME backups, but DME can't read DMF backups because samsung changed the EFS read type on DMF1. so once you go DMF1, your EFS partition is changed permanently!
Click to expand...
Click to collapse
you're wrong
I was only backup on DMF1 on the other note 2
I followed this procedure and are able to put DME4 :
1. make a copy of your EFS folder using root explorer and store it somewhere safe (on your SD card and external SD card should do it).
2. delete the EFS folder from the root of your phone using root explorer.
3. reboot the phone
4. open root explorer and go to the EFS folder (yes, it is still there! The Android OS has generated a new one for us) and delete the following files:
nv_data.bin
nv_data.bin.md5
nv.log
.nv_data.bak
.nv_data.bak.md5
nv_data.bin.bak
and the entire IMEI folder.
5.Now go to your backed up EFS folder on your sd card and copy the IMEI folder and the " .nv_data" file (note the dot) to your new EFS folder.
6.Make another copy of the ".nv_data" file in your new EFS folder. Rename one of them to "nv_data.bin" and the other one to "nv_data.bin.bak".
7. Connect your phone to your PC and start up EFS PRO. After your phone has been detected, press the "Repair nv data" button to correct the ownership and permissions.
8. Reboot your phone into recovery mode using the three botton combo and flash the original modem firmware (the modem.bin file that you extracted earlier) to your phone using Odin (use the "phone" button for the upload) or Heimdall (use the "radio" partition for the modem.bin file upload).
9. Reboot the phone normally and your IMEI number will be restored and you will be able to connect to your mobile network again
but on this note I can not!
mysterionTM said:
you're wrong
I was only backup on DMF1 on the other note 2
I followed this procedure and are able to put DME4 :
1. make a copy of your EFS folder using root explorer and store it somewhere safe (on your SD card and external SD card should do it).
2. delete the EFS folder from the root of your phone using root explorer.
3. reboot the phone
4. open root explorer and go to the EFS folder (yes, it is still there! The Android OS has generated a new one for us) and delete the following files:
nv_data.bin
nv_data.bin.md5
nv.log
.nv_data.bak
.nv_data.bak.md5
nv_data.bin.bak
and the entire IMEI folder.
5.Now go to your backed up EFS folder on your sd card and copy the IMEI folder and the " .nv_data" file (note the dot) to your new EFS folder.
6.Make another copy of the ".nv_data" file in your new EFS folder. Rename one of them to "nv_data.bin" and the other one to "nv_data.bin.bak".
7. Connect your phone to your PC and start up EFS PRO. After your phone has been detected, press the "Repair nv data" button to correct the ownership and permissions.
8. Reboot your phone into recovery mode using the three botton combo and flash the original modem firmware (the modem.bin file that you extracted earlier) to your phone using Odin (use the "phone" button for the upload) or Heimdall (use the "radio" partition for the modem.bin file upload).
9. Reboot the phone normally and your IMEI number will be restored and you will be able to connect to your mobile network again
but on this note I can not!
Click to expand...
Click to collapse
oh, you followed the folder method! then yeah it works, but not recommended as it messed up permissions.
I was speaking about the mmcblk0p3 method.
how to know which modem i need? Im on stock firmware 4.4.2, Malaysia. Have the imei issue/corrupted efs and no backup

[TUT] [ROOT] Backup restore IMEI manually

Automatic Backup Restore IMEI TOOL by Sector1369 is HERE .
(Only Require Custom recovery)
Automatic backup restore CMD script added by "deadlyindian" at Post#5
(Require PC ,ADB drivers & Root permissions )
If you still want to do this manually, look below
IMEI backup of redmi 1s
Require ROOT permissions
We all known that EFS partition holds the imei,sn ,wifi mac & other important data.
In Snapdragon the EFS partition are modemst1 ,modemst2 & FSG partitions. so it's important to take backup of these partitions.
1.connect your phone to PC , adb debugging enabled & goto adb shell by,
Code:
adb shell su
OR
Open terminal emulator app in your phone & take super user permissions, by
Code:
su
2.type following commands to backup imei partitions.
Code:
dd if=/dev/block/mmcblk0p16 of=/sdcard/mmcblk0p16_modemst1
dd if=/dev/block/mmcblk0p17 of=/sdcard/mmcblk0p17_modemst2
dd if=/dev/block/mmcblk0p20 of=/sdcard/mmcblk0p20_fsg
also these are some important partition you should consider to backup.
modem, fsc, bk1, ddr.
Code:
dd if=/dev/block/mmcblk0p23 of=/sdcard/mmcblk0p23_modem
dd if=/dev/block/mmcblk0p9 of=/sdcard/mmcblk0p9_DDR
dd if=/dev/block/mmcblk0p12 of=/sdcard/mmcblk0p12_bk1
dd if=/dev/block/mmcblk0p18 of=/sdcard/mmcblk0p18_fsc
Now the backup is stored in you internal storage ,store these files in safe place.
in case u get invalid imei or unknown, restore these partitions.
To restore these partitions,
Code:
dd if=/sdcard/mmcblk0p16_modemst1 of=/dev/block/mmcblk0p16
dd if=/sdcard/mmcblk0p17_modemst2 of=/dev/block/mmcblk0p17
dd if=/sdcard/mmcblk0p20_fsg of=/dev/block/mmcblk0p20
dd if=/sdcard/mmcblk0p23_modem of=/dev/block/mmcblk0p23
dd if=/sdcard/mmcblk0p9_DDR of=/dev/block/mmcblk0p9
dd if=/sdcard/mmcblk0p12_bk1 of=/dev/block/mmcblk0p12
dd if=/sdcard/mmcblk0p18_fsc of=/dev/block/mmcblk0p18
Working on Aroma EFS backup restore tool..
NOTE:-
Don't use tools or commands from other device because different devices has different partition address, that will result in wrong backups.
To use this method to backup other phones EFS , u should find your partition info.
Redmi 1s Partition tables can be found HERE
ENJOY,
Thanks man...it would be alot helpful if i gone to any trouble [emoji7]
But the problem with lost imei is for Redmi with MediaTek processor. Redmi Qualcomm don't suffer from this problem.
pgreed said:
But the problem with lost imei is for Redmi with MediaTek processor. Redmi Qualcomm don't suffer from this problem.
Click to expand...
Click to collapse
i know but it's always better to take bakup,who knows what 'll happen...
there is no way to generate imei,wifi mac data for qualcomm (as far as i know) ...
so it will come handy...
Auto IMEI Backup & Restore Tool
Backup restore IMEI Automatically
FIRST INSTALL THE ADB DRIVERS FOR THE 1S ► GO HERE ◄
Requires Phone to be ROOTED & USB Debugging turned ON
This is for Xiaomi Redmi 1S Only
I've created a CMD script that will automatically backup the IMEI & Also Restore it back again if you want to...
Backed Up files are inside MYIMEI folder of your selected backup storage.
NOTE : Enable root access for adb if you're on Custom ROM based on CyanogenMod
to do that ► Open Settings ► Superuser ► Superuser Access ► Select Apps and ADB ► done
► Download it from attachment
► Extract it
► Run R1SBAR.exe & follow instructions.
While restoring make sure the backed up files are inside the MYIMEI folder of either Internal Memory or External or it wont work.
If you face any error do tell me!
AGAIN ITS ONLY FOR REDMI 1S
deadlyindian said:
Backup restore IMEI Automatically
Requires Phone to be ROOTED & USB Debugging turned ON
This is for Xiaomi Redmi 1S Only
I've created a CMD script that will automatically backup the IMEI & Also Restore it back again if you want to...
Backed Up files are inside MYIMEI folder of your selected backup storage.
► Download it from attachment
► Extract it
► Run R1SBAR.exe & follow instructions.
While restoring make sure the backed up files are inside the MYIMEI folder of either Internal Memory or External or it wont work.
If you face any error do tell me!
AGAIN ITS ONLY FOR REDMI 1S
Click to expand...
Click to collapse
It working perfectly.Thank you.
pgreed said:
It working perfectly.Thank you.
Click to expand...
Click to collapse
You're Welcome :good:
[Backup restore IMEI Automatically] works like charm. thanks :good:
lavizta said:
[Backup restore IMEI Automatically] works like charm. thanks :good:
Click to expand...
Click to collapse
im glad it help :good:
deadlyindian said:
Backup restore IMEI Automatically
Requires Phone to be ROOTED & USB Debugging turned ON
This is for Xiaomi Redmi 1S Only
I've created a CMD script that will automatically backup the IMEI & Also Restore it back again if you want to...
Backed Up files are inside MYIMEI folder of your selected backup storage.
► Download it from attachment
► Extract it
► Run R1SBAR.exe & follow instructions.
While restoring make sure the backed up files are inside the MYIMEI folder of either Internal Memory or External or it wont work.
If you face any error do tell me!
AGAIN ITS ONLY FOR REDMI 1S
Click to expand...
Click to collapse
Great work :good::good:
None of the usual ROM / kernel flashing result in loss of these partitions .
If someone is able to screw up partitions, chances are that he will remove the partition table too ..
and with that he will not be able to fastboot anymore , to use backups made here.
Don't get me wrong, but its of little use imo.
Sector1369 said:
Code:
dd if=/dev/block/mmcblk0p23 of=/sdcard/mmcblk0p23_modem
dd if=/dev/block/mmcblk0p9 of=/sdcard/mmcblk0p9_DDR
dd if=/dev/block/mmcblk0p12 of=/sdcard/mmcblk0p12_bk1
dd if=/dev/block/mmcblk0p18 of=/sdcard/mmcblk0p18_fsc
ENJOY,
Click to expand...
Click to collapse
kapil.git said:
None of the usual ROM / kernel flashing result in loss of these partitions .
If someone is able to screw up partitions, chances are that he will remove the partition table too ..
and with that he will not be able to fastboot anymore , to use backups made here.
Don't get me wrong, but its of little use imo.
Click to expand...
Click to collapse
U never know when sh*t happens there is no harm in taking the backup. Had personally lost imei on couple of Samsung phone while flashing roms and was able to restore it with the efs backup.
rkkaranrk said:
U never know when sh*t happens there is no harm in taking the backup. Had personally lost imei on couple of Samsung phone while flashing roms and was able to restore it with the efs backup.
Click to expand...
Click to collapse
I mean backing up DRM keys and TA partitions made sense since they are wiped in some bootloader unlocking..
You almost make it sound like, I can restore someone else's IMEI too :silly: ..
I still have my old nokia phones with me of which I can rob their identities ?
Some random Redmi dev can give surprise to actually make an app for this..
Chinese phones have already been a pain in a$$ for Indian Govt due to lack / duplicate of this IMEI modules.
kapil.git said:
I mean backing up DRM keys and TA partitions made sense since they are wiped in some bootloader unlocking..
You almost make it sound like, I can restore someone else's IMEI too :silly: ..
I still have my old nokia phones with me of which I can rob their identities ?
Some random Redmi dev can give surprise to actually make an app for this..
Chinese phones have already been a pain in a$$ for Indian Govt due to lack / duplicate of this IMEI modules.
Click to expand...
Click to collapse
I'm pretty sure u have been using a Sony phone and have limited knowledge so don't jump and compare the phones with the same thing.
As for the imei take help of google and search for z3x/cyclone/nspro/magma what are they used for:silly:
it might come in handy or it might not
nevertheless i'm putting it in safekeeping.
thanks for the work & effort.
:good:
rkkaranrk said:
I'm pretty sure u have been using a Sony phone and have limited knowledge so don't jump and compare the phones with the same thing.
Click to expand...
Click to collapse
Yes you are correct , been using Sony for a while
As for the imei take help of google and search for z3x/cyclone/nspro/magma what are they used for:silly:
Click to expand...
Click to collapse
mmmkaay..
@deadlyindian,
Thanks for providing the automated script to back up imie.
I did go through your post and did as per the instructions mentioned step by step. However, I am unable to proceed after getting the message "Please connect usb cable now" after running R1SBAR. I do have root access(checked from root checker app) and have also enabled USB Debugging. I also inserted cable after getting the message.
Does it take a lot of time(more than 5 mins) to backup imei cause I continued till 5 mins before closing the cmd prompt.
Hope you can help me here.
PS: I am using MIUI v45 global version "JHCCNBH45.0 (V5) " in case if you need.
ADB Drivers & instructions...
fanboy_android said:
@deadlyindian,
Thanks for providing the automated script to back up imie.
I did go through your post and did as per the instructions mentioned step by step. However, I am unable to proceed after getting the message "Please connect usb cable now" after running R1SBAR. I do have root access(checked from root checker app) and have also enabled USB Debugging. I also inserted cable after getting the message.
Does it take a lot of time(more than 5 mins) to backup imei cause I continued till 5 mins before closing the cmd prompt.
Hope you can help me here.
PS: I am using MIUI v45 global version "JHCCNBH45.0 (V5) " in case if you need.
Click to expand...
Click to collapse
Have you installed the ADB drivers for the 1S? ► ADB Drivers ◄
After installing Run R1SBAR.exe & follow the below screens
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
deadlyindian said:
Have you installed the ADB drivers for the 1S? ► ADB Drivers ◄
After installing Run R1SBAR.exe & follow the below screens
Click to expand...
Click to collapse
Yes, it seems adb drivers were missing after which I was able to successfully backup my IMIE. Thanks for your help.
Perhaps you could add this link in your earlier post as a pre-requisite so that newcomers won't face this issue. Just a suggestion
Kudos and keep rocking.
fanboy_android said:
Yes, it seems adb drivers were missing after which I was able to successfully backup my IMIE. Thanks for your help.
Perhaps you could add this link in your earlier post as a pre-requisite so that newcomers won't face this issue. Just a suggestion
Kudos and keep rocking.
Click to expand...
Click to collapse
Done!!

[Guide] IMEI Fix For Devices On Custom Rom.

Hey Guys,
Yep, I know there are a whole lot of threads for imei problem fix, but I've seen a lot of threads with solutions only working either for stock rom, or there is some random imei showing up on your device. This is a thread on fixing imei problem working for custom ROMs. Yes! . I have tried this AOSP Extended and Resurrection Remix OS 5.8.3 both by mohancm and I'm pretty sure it will work on any custom ROM. This fix is based on partitions backup from your stock rom, so there will be no issues.
This solution was given by Senior Member @KaMyKaSii, so all thanks to him! Lets get started!
Requirements:
1) Your device ( Obviously )
2) Stock ROM Marshmallow.
3) Rooted Device
4) Maui Meta 3G/ SN Write Tool (Optional)
Procedure:
1) If you are on Custom Rom, flash marshmallow stock ROM (Search the forums, there a lot of threads), using SP Flash Tools.
2) After going to stock rom, next step is unlocking bootloader, there are many threads on doing this, but I'll sum it up here if you
want:
i) Go to Developer Settings>OEM Unlocking. Enable the option. Also enable USB Debugging Mode.
ii) Connect to a computer and open adb on it. Check if the device is connected using the command
Code:
adb devices
iii) now use the command
Code:
adb reboot-bootloader
In fastboot use this command to unlock bootloader
Code:
fastboot oem unlock
Do as it says and reboot.
iv) Now again after rebooting go to bootloader and flash TWRP.
3) Root your device by flashing MagiskSU or SuperSU.
4) Now, download and install FX File Explorer from play store, Open it and enable Root Access from Settings>Add-Ons And
Themes in file explorer.
5) Now go back and open System (Root) folder in file explorer.
Note: If you haven't already restored, restore your imei, bluetooth address and serial number using Maui Meta or SN Write Tool.
6) In system root, grant Root permissions, and go to dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name folder.
7) In that folder, copy the files mentioned below:
Code:
expdb
nvdata
nvram
proinfo
protect1
protect2
secro
8) Copy these files in some place where it is safe ( I have copied it to Internal Storage in a folder named PartitionsBackup)..
9) Next, go back to root folder again, and open data/nvram/md/NVRAM/NVD_IMEI and copy the MP0B_001 file to internal storage. Do Not copy this file in the same place as the previous files, but remember where you have copied this file.
These are all the partitions that store the device's IMEI .
10) After copying everything mentioned, Reboot to recovery and flash the desired Custom Rom.
11) Make sure the rom is rooted, and again install FX File Explorer from play store, enable root access as above.
Do Not Forget To Backup Everything Before Doing Anything!
12) Now select the files that you have copied in internal storage (Assuming PartitionsBackup). And copy those files. ( Note: Do Not Copy the MP0B_001 file!)
13) Now open root folder, go to dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name folder and paste all the files you have copied, and if asked select Merge/Overwrite files.
14) Reboot.
15) Now go back to internal storage, copy the MP0B_001 file where you have saved it. Go back to root folder and open data/nvram/md/NVRAM/NVD_IMEI and copy the file, select Merge/Overwrite. Now long press the file and select Security, update permissions as Read, Write for both root and radio. Dis-select everything else.
16) Reboot aand Done! Voila ! You should get back the IMEI for your device :victory:
I know its a long post, but it works for Custom ROMs.!
Hope it helps!
Hit Thanks If you feel it works! :highfive:
can you please help me on step 13 because every time i reboot the device the by-name folder contents reset to the original value. my by-name folder backup is 72 mb while when i look in the folder after i reboot it is only 170 bytes
---------- Post added at 06:12 AM ---------- Previous post was at 06:07 AM ----------
also when i wait for a while after rebooting for like 4-6 hours when i looked at my baseband and imei it is not unknown anymore
and my sim is restored but when i reboot again the baseband value and imei is set back to unknown. this happened even before im not following your solution. can it be a hardware issue? would really appreciate any help thx
Cyteezy said:
can you please help me on step 13 because every time i reboot the device the by-name folder contents reset to the original value. my by-name folder backup is 72 mb while when i look in the folder after i reboot it is only 170 bytes
---------- Post added at 06:12 AM ---------- Previous post was at 06:07 AM ----------
also when i wait for a while after rebooting for like 4-6 hours when i looked at my baseband and imei it is not unknown anymore
and my sim is restored but when i reboot again the baseband value and imei is set back to unknown. this happened even before im not following your solution. can it be a hardware issue? would really appreciate any help thx
Click to expand...
Click to collapse
I didn't get you. Do not backup the whole by-name folder. Just copy the files mentioned above. And when you go into the custom ROM, just restore the files copied in the same by-name folder.
No. It might not be a hardware problem.
PraneethMv said:
Hey Guys,
Yep, I know there are a whole lot of threads for imei problem fix, but I've seen a lot of threads with solutions only working either for stock rom, or there is some random imei showing up on your device. This is a thread on fixing imei problem working for custom ROMs. Yes! . I have tried this AOSP Extended and Resurrection Remix OS 5.8.3 both by mohancm and I'm pretty sure it will work on any custom ROM. This fix is based on partitions backup from your stock rom, so there will be no issues.
This solution was given by Senior Member @KaMyKaSii, so all thanks to him! Lets get started!
Requirements:
1) Your device ( Obviously )
2) Stock ROM Marshmallow.
3) Rooted Device
4) Maui Meta 3G/ SN Write Tool (Optional)
Procedure:
1) If you are on Custom Rom, flash marshmallow stock ROM (Search the forums, there a lot of threads), using SP Flash Tools.
2) After going to stock rom, next step is unlocking bootloader, there are many threads on doing this, but I'll sum it up here if you
want:
i) Go to Developer Settings>OEM Unlocking. Enable the option. Also enable USB Debugging Mode.
ii) Connect to a computer and open adb on it. Check if the device is connected using the command
Code:
adb devices
iii) now use the command
Code:
adb reboot-bootloader
In fastboot use this command to unlock bootloader
Code:
fastboot oem unlock
Do as it says and reboot.
iv) Now again after rebooting go to bootloader and flash TWRP.
3) Root your device by flashing MagiskSU or SuperSU.
4) Now, download and install FX File Explorer from play store, Open it and enable Root Access from Settings>Add-Ons And
Themes in file explorer.
5) Now go back and open System (Root) folder in file explorer.
Note: If you haven't already restored, restore your imei, bluetooth address and serial number using Maui Meta or SN Write Tool.
6) In system root, grant Root permissions, and go to dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name folder.
7) In that folder, copy the files mentioned below:
Code:
expdb
nvdata
nvram
proinfo
protect1
protect2
secro
8) Copy these files in some place where it is safe ( I have copied it to Internal Storage in a folder named PartitionsBackup)..
9) Next, go back to root folder again, and open data/nvram/md/NVRAM/NVD_IMEI and copy the MP0B_001 file to internal storage. Do Not copy this file in the same place as the previous files, but remember where you have copied this file.
These are all the partitions that store the device's IMEI .
10) After copying everything mentioned, Reboot to recovery and flash the desired Custom Rom.
11) Make sure the rom is rooted, and again install FX File Explorer from play store, enable root access as above.
Do Not Forget To Backup Everything Before Doing Anything!
12) Now select the files that you have copied in internal storage (Assuming PartitionsBackup). And copy those files. ( Note: Do Not Copy the MP0B_001 file!)
13) Now open root folder, go to dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name folder and paste all the files you have copied, and if asked select Merge/Overwrite files.
14) Reboot.
15) Now go back to internal storage, copy the MP0B_001 file where you have saved it. Go back to root folder and open data/nvram/md/NVRAM/NVD_IMEI and copy the file, select Merge/Overwrite. Now long press the file and select Security, update permissions as Read, Write for both root and radio. Dis-select everything else.
16) Reboot aand Done! Voila ! You should get back the IMEI for your device :victory:
I know its a long post, but it works for Custom ROMs.!
Hope it helps!
Hit Thanks If you feel it works! :highfive:
Click to expand...
Click to collapse
Can anyone help me in restoring IMEI in stock ROM?
While flashing using SN writer or maui meta tool it says "Have been in meta mode. Long press power button to normal reboot". After that nothing. It boots back and I still see the INVALID IMEI message.
MisledMew said:
Hey Guys,
Yep, I know there are a whole lot of threads for imei problem fix, but I've seen a lot of threads with solutions only working either for stock rom, or there is some random imei showing up on your device. This is a thread on fixing imei problem working for custom ROMs. Yes! . I have tried this AOSP Extended and Resurrection Remix OS 5.8.3 both by mohancm and I'm pretty sure it will work on any custom ROM. This fix is based on partitions backup from your stock rom, so there will be no issues.
This solution was given by Senior Member @KaMyKaSii, so all thanks to him! Lets get started!
Requirements:
1) Your device ( Obviously )
2) Stock ROM Marshmallow.
3) Rooted Device
4) Maui Meta 3G/ SN Write Tool (Optional)
Procedure:
1) If you are on Custom Rom, flash marshmallow stock ROM (Search the forums, there a lot of threads), using SP Flash Tools.
2) After going to stock rom, next step is unlocking bootloader, there are many threads on doing this, but I'll sum it up here if you
want:
i) Go to Developer Settings>OEM Unlocking. Enable the option. Also enable USB Debugging Mode.
ii) Connect to a computer and open adb on it. Check if the device is connected using the command
iii) now use the command
In fastboot use this command to unlock bootloader Do as it says and reboot.
iv) Now again after rebooting go to bootloader and flash TWRP.
3) Root your device by flashing MagiskSU or SuperSU.
4) Now, download and install FX File Explorer from play store, Open it and enable Root Access from Settings>Add-Ons And
Themes in file explorer.
5) Now go back and open System (Root) folder in file explorer.
Note: If you haven't already restored, restore your imei, bluetooth address and serial number using Maui Meta or SN Write Tool.
6) In system root, grant Root permissions, and go to dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name folder.
7) In that folder, copy the files mentioned below:
Can anyone help me in restoring IMEI in stock ROM?
While flashing using SN writer or maui meta tool it says "Have been in meta mode. Long press power button to normal reboot". After that nothing. It boots back and I still see the INVALID IMEI message.
Click to expand...
Click to collapse
SN write tool can be a little complicated to do. I personally prefer Maui Meta 3G. You can search for guides on SN write tool. There are many....
Facing problem with maui meta 3g
On my mobile it shows its in "Have been in meta mode. Long press power button to normal reboot".
it won't work ahead .... some error like kernel checksum and no permission grant type.. rather i installed drivers of mediatek its not working...
plz help out
Ni$hant said:
On my mobile it shows its in "Have been in meta mode. Long press power button to normal reboot".
it won't work ahead .... some error like kernel checksum and no permission grant type.. rather i installed drivers of mediatek its not working...
plz help out
Click to expand...
Click to collapse
Do you have all drivers installed correctly? ADB, VCOM, USB Drivers?
Also, That message screen is Meta Mode. From that screen only you can do the IMEI process.
Note: This Only works for stock rom. Use this guide.
https://forum.hovatek.com/thread-12328.html
For custom Roms, use my guide.
Device: Lenovo A2016a40 (MY6735M) also known as Lenovo vibe b
Android Version - 6.0 Marshmallow
I can't find any folder named 'nvram' on 'data' directory of root folder

Categories

Resources