LG Optimus G EFS Backup/Restore
Every rooted Optimus G user should backup their EFS partitions! Included in this thread is a flashable EFS backup script and terminal/adb commands if you want to do it manually. The script automates the entire backup of all 3 EFS partitions and then packs the files into a flashable zip for easy restoring later. Place this zip somewhere safe other than your sdcard!
Thanks goes to toastcfh for the script help and everyone in #lg-optimus-g that helped out with EFS testing.
Original Optimus G EFS Thread(ZERO EFS) - HERE
I have received an ATT EFS backup from an ATT user and will be attempting to create a ZERO EFS zip for ATT devices. This thread will be updated if I'm successful.
Background
You never know when your NV/EFS may stop working correctly. Restoring your WORKING EFS may save the day. A few users in the #lg-optimus-g IRC channel have run into issues and found their phone unusable, myself included. Our issues could have been fixed if an EFS backup was made while the phone was still in working order.
m9kefs1 seems to be radio related
m9kefs2 contains your unique phone identifiers: IMEI, phone number, etc
m9kefs3 seems to be blank 00s
Backing up EFS
It's easiest to run the Optimus_G_Create_Flashable_EFS.zip attached to this thread. Run in recovery. Optimus_G_Create_Flashable_EFS.zip creates a flashable zip backup of your EFS in /sdcard/EFS_Backup/(instead of just a .tar). Confirmed working on TWRP 2.3.2.3/2.4.1.0 and CWM 6.0.2.7. Confirmed NOT working on CWM 6.0.1.5. Please check to make sure the backup zip worked and actually made a .zip file in /sdcard/EFS_Backup. Any issues please list what recovery and version you are using and please post the recovery.log.
If you don't like convenience this can also be done manually with adb or terminal with the commands below.. root required.
Code:
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/m9kefs1 of=/sdcard/m9kefs1.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/m9kefs2 of=/sdcard/m9kefs2.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/m9kefs3 of=/sdcard/m9kefs3.img
Restoring EFS
To restore your original EFS just boot into recovery and flash the efsbackupflash.zip in your /sdcard/EFS_Backup folder.
If you don't like convenience this can also be done manually with adb or terminal with the commands below. Adjust the "dd if=/sdcard/" command depending on where your backup EFS .img files are located.
Code:
su
dd if=/sdcard/m9kefs1.img of=/dev/block/platform/msm_sdcc.1/by-name/m9kefs1
dd if=/sdcard/m9kefs2.img of=/dev/block/platform/msm_sdcc.1/by-name/m9kefs2
dd if=/sdcard/m9kefs3.img of=/dev/block/platform/msm_sdcc.1/by-name/m9kefs3
Code:
[B]Changelog[/B]
[I]v1 EFS backup zip[/I]:
backed up m9kefs1.img and m9kefs2.img then .tar'd them.
[I]v2 EFS backup zip[/I]:
backed up EFS then creates a flashable .zip containing the EFS partitions.
[I]v3 EFS backup zip[/I]:
zip script is now "safer" and should work on all Optimus G variants.
[I]v4 EFS backup zip[/I]:
backup zip now backs up m9kefs3. this is for "completeness" only.
I believe m9kefs3 contains no worthwhile data.
Does this work on any of the Canadian variants?
on stock rooted firmware i run zip but the backup tar in nowhere to be found
sucsss said:
Does this work on any of the Canadian variants?
Click to expand...
Click to collapse
I know that the Telus version will work. I'd assume both Bell and Rogers have the same m9kefs1/m9kefs2 partitions as well.
Going to confirm then I will make a thread in the Canadian section as well.
pinkster said:
on stock rooted firmware i run zip but the backup tar in nowhere to be found
Click to expand...
Click to collapse
Hmm.. I've had confirmation from ATT users that this works... even received some EFS backups from them for further testing.
The zip no longer makes a .tar. You should have an EFS_Backup folder on your INTERNAL /sdcard containing both efs partitions as well as a flashable .zip backup. Please check the internal card and not the external. If there is still no backup to be found please post the recovery.log file after you flash Optimus_G_Create_Flashable_EFS.zip
All of my personal tests were done while using TWRP 2.4.1.0 . Can't confirm older TWRP versions or CWM.. but I see no reason why they shouldn't work as well.
*UPDATE*
The above issue was fixed after updating CWM. CWM 6.0.1.5 is no good. Upgrade.. or better yet.. switch to TWRP.
The latest cwm works perfectly, that's what I used.
Sent from my LG-E970 using Tapatalk 2
autoprime said:
I know that the Telus version will work. I'd assume both Bell and Rogers have the same m9kefs1/m9kefs2 partitions as well.
Going to confirm then I will make a thread in the Canadian section as well.
Hmm.. I've had confirmation from ATT users that this works... even received some EFS backups from them for further testing.
The zip no longer makes a .tar. You should have an EFS_Backup folder on your INTERNAL /sdcard containing both efs partitions as well as a flashable .zip backup. Please check the internal card and not the external. If there is still no backup to be found please post the recovery.log file after you flash Optimus_G_Create_Flashable_EFS.zip
All of my personal tests were done while using TWRP 2.4.1.0 . Can't confirm older TWRP versions or CWM.. but I see no reason why they shouldn't work as well.
Click to expand...
Click to collapse
I've got the E971. need any help to confirm?
sucsss said:
I've got the E971. need any help to confirm?
Click to expand...
Click to collapse
can u run this in adb/terminal: ls -la /dev/block/platform/msm_sdcc.1/by-name/
post output.. or at least confirm that you have an m9kefs1, m9kefs2 and m9kefs3. could you also post the actual locations of the 3.. like.. do they use /dev/block/mmcblk0p12 and /dev/block/mmcblk0p13 and /dev/block/mmcblk0p14 ?
Used the .zip in TWRP 2.3.2.3 and it successfully created backups of m9kefs1 & 2 it looks like.
{
"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"
}
Sent from my Nexus 7 using Tapatalk HD
autoprime said:
can u run this in adb/terminal: ls -la /dev/block/platform/msm_sdcc.1/by-name/
post output.. or at least confirm that you have an m9kefs1, m9kefs2 and m9kefs3. could you also post the actual locations of the 3.. like.. do they use /dev/block/mmcblk0p12 and /dev/block/mmcblk0p13 and /dev/block/mmcblk0p14 ?
Click to expand...
Click to collapse
lrwxrwxrwx root root 1970-04-22 03:41 m9kefs1 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-04-22 03:41 m9kefs2 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-04-22 03:41 m9kefs3 -> /dev/block/mmcblk0p14
interesting note, why are the dates like that?
sucsss said:
lrwxrwxrwx root root 1970-04-22 03:41 m9kefs1 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-04-22 03:41 m9kefs2 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-04-22 03:41 m9kefs3 -> /dev/block/mmcblk0p14
interesting question, why are the dates like that?
Click to expand...
Click to collapse
thanks for the update.. this confirms what i suspected.. its just like all the other Optimus G devices and the backup efs zip will work! I will post a new thread in the Canadian Dev forums so that it catches everyones eye.
i forget the technical reason for the date issue.. but its something with recovery not reporting the time correctly. it's the same with my device. sorry i dont have a better answer
nymica said:
The latest cwm works perfectly, that's what I used.
Sent from my LG-E970 using Tapatalk 2
Click to expand...
Click to collapse
Same here.
Well if latest you mean Sk8s CWMRTouch 6.0.2.7 14.4.7
I apologize for this noob question but what is the difference between this and making a nandroid backup or the one created in let us say twrp?
yhe2x said:
I apologize for this noob question but what is the difference between this and making a nandroid backup or the one created in let us say twrp?
Click to expand...
Click to collapse
as far as i know.. a nandroid doesn't backup the efs partition. a nandroid contains android data and system stuff.
*edit*
TWRP recovery should now have EFS backup in the "Backup" option when using an LG OG(this feature is not in all devices).
clorbag said:
so do i go into twrp and choose install zip to use this ?
Click to expand...
Click to collapse
If you dont want to use TWRP to backup EFS then yes, you can flash my zip in recovery.. just the the OP states.
DraginMagik said:
Can you elaborate on how we would know when we'd need to restore the EFS partition?
What would cause a problem with the EFS partition?
Sent from my Optimus G using xda premium
Click to expand...
Click to collapse
here's a bit more info on possible efs issues - http://forum.xda-developers.com/showpost.php?p=38350918&postcount=4
EFS is much more important on a CDMA device(what I use).. but its also good practice to do it on GSM devices. Example... Any time someone lost their IMEI and can't fix it no matter what modem/baseband they flash... restoring your EFS could maybe fix that.
autoprime said:
as far as i know.. a nandroid doesn't backup the efs partition. a nandroid contains android data and system stuff.
Click to expand...
Click to collapse
so do i go into twrp and choose install zip to use this ?
Can you elaborate on how we would know when we'd need to restore the EFS partition?
What would cause a problem with the EFS partition?
Sent from my Optimus G using xda premium
So rooting the phone isn't enough to use this flashable Zip, we should be on a customer Kernel that has either TWRP or Clockwork Mod, that is what I am getting from this so would I be correct? Thanks. I am more intimately familiar with the AT&T SGS2 SGH 777 and new to LG.
WarEagleUS said:
So rooting the phone isn't enough to use this flashable Zip, we should be on a customer Kernel that has either TWRP or Clockwork Mod, that is what I am getting from this so would I be correct? Thanks. I am more intimately familiar with the AT&T SGS2 SGH 777 and new to LG.
Click to expand...
Click to collapse
This device doesn't have recoveries baked into the kernel like the i777. They are flashed independently.
Sent from my Optimus G using Tapatalk 2
WarEagleUS said:
So rooting the phone isn't enough to use this flashable Zip, we should be on a customer Kernel that has either TWRP or Clockwork Mod, that is what I am getting from this so would I be correct? Thanks. I am more intimately familiar with the AT&T SGS2 SGH 777 and new to LG.
Click to expand...
Click to collapse
After rooting the boot loader must be unlocked with FreeGee app from play store. I think the latest version only has option to install twrp, but you can use that to flash cwm if you prefer it.
lg optimus G radio not working..helpp
autoprime said:
LG Optimus G EFS Backup/Restore
Every rooted Optimus G user should backup their EFS partitions! Included in this thread is a flashable EFS backup script and terminal/adb commands if you want to do it manually. The script automates the entire backup of all 3 EFS partitions and then packs the files into a flashable zip for easy restoring later. Place this zip somewhere safe other than your sdcard!
Thanks goes to toastcfh for the script help and everyone in #lg-optimus-g that helped out with EFS testing.
Original Optimus G EFS Thread(ZERO EFS) - HERE
I have received an ATT EFS backup from an ATT user and will be attempting to create a ZERO EFS zip for ATT devices. This thread will be updated if I'm successful.
Background
You never know when your NV/EFS may stop working correctly. Restoring your WORKING EFS may save the day. A few users in the #lg-optimus-g IRC channel have run into issues and found their phone unusable, myself included. Our issues could have been fixed if an EFS backup was made while the phone was still in working order.
m9kefs1 seems to be radio related
m9kefs2 contains your unique phone identifiers: IMEI, phone number, etc
m9kefs3 seems to be blank 00s
Backing up EFS
It's easiest to run the Optimus_G_Create_Flashable_EFS.zip attached to this thread. Run in recovery. Optimus_G_Create_Flashable_EFS.zip creates a flashable zip backup of your EFS in /sdcard/EFS_Backup/(instead of just a .tar). Confirmed working on TWRP 2.3.2.3/2.4.1.0 and CWM 6.0.2.7. Confirmed NOT working on CWM 6.0.1.5. Please check to make sure the backup zip worked and actually made a .zip file in /sdcard/EFS_Backup. Any issues please list what recovery and version you are using and please post the recovery.log.
If you don't like convenience this can also be done manually with adb or terminal with the commands below.. root required.
Code:
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/m9kefs1 of=/sdcard/m9kefs1.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/m9kefs2 of=/sdcard/m9kefs2.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/m9kefs3 of=/sdcard/m9kefs3.img
Restoring EFS
To restore your original EFS just boot into recovery and flash the efsbackupflash.zip in your /sdcard/EFS_Backup folder.
If you don't like convenience this can also be done manually with adb or terminal with the commands below. Adjust the "dd if=/sdcard/" command depending on where your backup EFS .img files are located.
Code:
su
dd if=/sdcard/m9kefs1.img of=/dev/block/platform/msm_sdcc.1/by-name/m9kefs1
dd if=/sdcard/m9kefs2.img of=/dev/block/platform/msm_sdcc.1/by-name/m9kefs2
dd if=/sdcard/m9kefs3.img of=/dev/block/platform/msm_sdcc.1/by-name/m9kefs3
Code:
[B]Changelog[/B]
[I]v1 EFS backup zip[/I]:
backed up m9kefs1.img and m9kefs2.img then .tar'd them.
[I]v2 EFS backup zip[/I]:
backed up EFS then creates a flashable .zip containing the EFS partitions.
[I]v3 EFS backup zip[/I]:
zip script is now "safer" and should work on all Optimus G variants.
[I]v4 EFS backup zip[/I]:
backup zip now backs up m9kefs3. this is for "completeness" only.
I believe m9kefs3 contains no worthwhile data.
Click to expand...
Click to collapse
need helpp...i was on stock ics in optimus g e970, i tried flashing korean kdz onto it via R n D tool and messed it up...when i went back to stock via lgnpst, lost my radio (network signal).....now i have tried soooooooooo many things but no use....i guess this efs is the last left procedure and hope for me...helpp please....
i didnt backup my efs file and deleted everything.....now no radio, no sim working
You LGNPST'd a KOREAN FIRMWARE FFS. You richly deserve your misfortune. Your actions might constitute the most incredible "derp" that I've seen since migrating to this device.
Related
I have included a script in a initd script segment to create a file called efs.autobackup.img
The forum is filled withon how to creating the .img file but i couldnt find about how to restore.Ktool doesnt work on this.
I am asking this in behalf of a fellow xda member.He got a factory efs files in some old Indian firmware, flashed it by using clear phone efs in odin and now he has some generic IMEI.How to extract the files inside the .img file atleast??
Atleast he can use the files to change his IMEI using nv_data.bin and nv_data.bin.md5
If it's a raw .img (20MB in size) kTool should work fine.
Just rename the file to "efs.img" and put it to /sdcard (root of the internal storage when mounted to the PC).
Then run a restore via kTool (be sure to use latest version).
HellcatDroid said:
If it's a raw .img (20MB in size) kTool should work fine.
Just rename the file to "efs.img" and put it to /sdcard (root of the internal storage when mounted to the PC).
Then run a restore via kTool (be sure to use latest version).
Click to expand...
Click to collapse
Yes its 20MB size!!Ohk hellcat.Am PMing him.he is a new user and he his too terified
Thank god he had flashed my ROM,The wickedrom v1.1 which had auto efs script.
I will ask him to report here.
One thing he has fake IMEI now.This should work right?
Doing a search uncovers a ton of threads/posts about restoring efs
chetan_mohanty said:
I have included a script in a initd script segment to create a file called efs.autobackup.img
The forum is filled withon how to creating the .img file but i couldnt find about how to restore.Ktool doesnt work on this.
I am asking this in behalf of a fellow xda member.He got a factory efs files in some old Indian firmware, flashed it by using clear phone efs in odin and now he has some generic IMEI.How to extract the files inside the .img file atleast??
Atleast he can use the files to change his IMEI using nv_data.bin and nv_data.bin.md5
Click to expand...
Click to collapse
MistahBungle said:
Doing a search uncovers a ton of threads/posts about restoring efs
Click to expand...
Click to collapse
I have been trying to help him with zillions of links from xda.Nothing has worked.I am not a noob man
I do the homework before posting
chetan_mohanty said:
I have been trying to help him with zillions of links from xda.Nothing has worked.I am not a noob man
I do the homework before posting
Click to expand...
Click to collapse
If the .img is OK and not already of a broken EFS, or the image itself is corrupted (all these things can happen, sadly) then it can surely be restored.
HellcatDroid said:
If the .img is OK and not already of a broken EFS, or the image itself is corrupted (all these things can happen, sadly) then it can surely be restored.
Click to expand...
Click to collapse
He is saying that restoring with efs.img makes his phone go to unknown baseband and IMEI.
I have asked him again to post it in this thread
Is there any way to extract that .img file???
chetan_mohanty said:
Is there any way to extract that .img file???
Click to expand...
Click to collapse
In a shell, type:
Code:
su
mkdir /sdcard/mnt
mount -t ext4 /sdcard/efs.img /sdcard/mnt
Then use your fav. filemanager to go to "mnt" on the internal storage.
If the mount command gives you an error, it's likely the .img is corrupted.
I got an EFS.tar backup
I got Odin
I got Heimdall
I got YP-G1 stock.tar.md5
I just don't know how put it all together.
Back on GB roms, I would just wipe everything via CWM, use Odin to flash stock, and then wipe once again.
But this is ICS. Surely it's different, right?
I wrote out instructions in either the LinICS or the Nebula thread (I can't remember it was several weeks ago), also the files are in the Restore to stock thread from Zaclimon. you gonna have some issues in that your efs backup is an efs.tar instead of an efs.rfs
Oh!
I also have a cwm recovery image of stock, if that matters at all
Doesn't seem like a quick restore job either though
theplasmastorm said:
Oh!
I also have a cwm recovery image of stock, if that matters at all
Doesn't seem like a quick restore job either though
Click to expand...
Click to collapse
IT DOESN'T, when you go to LinICS or any of the CM9 ROMs your player is converted from RFS partitions to MTD ones and you HAVE TO use HEIMDALL with a PIT file to reparttion the player back to RFS as you flash the stock ROM.
Totally lost on what to do. I don't know where to begin or anything. I need someone to hold my hand step by step like a baby.
I've read the recovery thread and did some searches around the place, but I don't really understand a thing. I have a US YP-G1
Alright after some fiddling around I got back to stock but the usual blank efs issues are there. I still don't understand how to restore my efs.tar. Could someone help me please?
I also can't mount efs and have no idea what to do with the blankefs.img in the recovery thread
Okay after some more fiddling around I was able to restore my EFS. The efs bugs are still there though so I'm suspecting that the automatic backup that CM9 did is utterly useless and I lost my efs forever. Well I guess I'm going back to linaro <_<
theplasmastorm said:
Okay after some more fiddling around I was able to restore my EFS. The efs bugs are still there though so I'm suspecting that the automatic backup that CM9 did is utterly useless and I lost my efs forever. Well I guess I'm going back to linaro <_<
Click to expand...
Click to collapse
Did you have content on your efs.tar?
Yes my efs.tar has stuff in it
What I did was...
wipe data
restore stock via heimdall. add in blankefs.img in the efs spot.
flashed terra via odin
went to cwm recovery. got on adb shell
cd /efs
ls -l. nothing was in it except what blankefs did
tar -x -f /sdcard/efs.tar
ls -l. tar successfully extracted
got off adb shell and restarted the player
the efs issues still presist
so then i got on adb shell again and checked the efs folder and everything was still there
So I don't know
theplasmastorm said:
Yes my efs.tar has stuff in it
What I did was...
wipe data
restore stock via heimdall. add in blankefs.img in the efs spot.
flashed terra via odin
went to cwm recovery. got on adb shell
cd /efs
ls -l. nothing was in it except what blankefs did
tar -x -f /sdcard/efs.tar
ls -l. tar successfully extracted
got off adb shell and restarted the player
the efs issues still presist
so then i got on adb shell again and checked the efs folder and everything was still there
So I don't know
Click to expand...
Click to collapse
one thing that works, atleast the method I used to solve it, once you've copied the contents back into the EFS folder on the player, then flash the Dream Ultra ROM from CWM, then after booting the ROM up shutdown and wipe data/factory reset, then use Odin to flash the stock GB.tar through odin.
Roms at these links.
http://forum.xda-developers.com/showthread.php?t=1719685&highlight=dream+ultra
http://forum.xda-developers.com/showthread.php?t=1512331&highlight=stock+rooted+4+0
Oh snap that worked. Aroma installer to the rescue.
theplasmastorm said:
Oh snap that worked. Aroma installer to the rescue.
Click to expand...
Click to collapse
Now make a a proper EFS.rfs backup using the method described here http://forum.xda-developers.com/showthread.php?t=1632376&highlight=efs+backup that way next time you need to revert back from an ICS ROM you can flash the efs.rfs to the efs section instead of the blankefs.img and not have to go through this again.
FYI the method listed can be done on the player using terminal emulator just go into it and type su to gain superuser then type the the part for making an efs backup and your done, then copy that file to your PC.
Well when I first flashed linaro there was no mention of efs backup or anything in the topic post and that is why I got in the predicament in the first place.
And then when I watched your vid on how to flash it there was no mention of efs backup either.
Well all that is in the past. I know better now.
I already made a backup as soon as I got back to stock
theplasmastorm said:
Well when I first flashed linaro there was no mention of efs backup or anything in the topic post and that is why I got in the predicament in the first place.
And then when I watched your vid on how to flash it there was no mention of efs backup either.
Well all that is in the past. I know better now.
I already made a backup as soon as I got back to stock
Click to expand...
Click to collapse
Sorry, it was in my older videos that I did, forgot to mention it in that one, guess I'm not the only one to goof up if it's not in the OP either.
theplasmastorm said:
Yes my efs.tar has stuff in it
What I did was...
wipe data
restore stock via heimdall. add in blankefs.img in the efs spot.
flashed terra via odin
went to cwm recovery. got on adb shell
cd /efs
ls -l. nothing was in it except what blankefs did
tar -x -f /sdcard/efs.tar
ls -l. tar successfully extracted
got off adb shell and restarted the player
the efs issues still presist
so then i got on adb shell again and checked the efs folder and everything was still there
So I don't know
Click to expand...
Click to collapse
Whenever I try to do these steps before flashing dream ultra rom it tells me "tar not found" I have a efs.tar on my sd card for certain.
WARNING!
I AM NOT RESPONSIBLE IF YOU BRICK YOUR PHONE!
I've decided to create this little tutorial thread to show how can you backup some important device specific data like IMEI, WiFi/BT mac address, modem (RIL) specific data and configuration files.
If the baseband version or IMEI number gets damaged you will face with some serious network issues like dropping the network signal, no 3G, no mobile data, no roaming - so the phone is basically useless.
Special thanks to:
@fluffi444 for his help to indentify the the correct partitions: [HOW-TO] Recover FULL GT-I8160P if flashed to GT-I8160 (non-P)
@Shaaan for Temporary CWM Recovery: [JB] CWM Recovery 6
REQUIREMENTS:
Rooted phone
ADB tool for do this on PC or Terminal Emulator from Google Play
CWM recovery - only if you want to use the .zips
BEFORE STARTING
Before starting the backup/restore process flash back to your Official Stock Firmware!
IMEI null/null, Unknown Baseband and other issues not always caused by corrupted NV Data!
To get root permission you have to enter "su" command for every terminal/adb shell session!
There are 3 dd commands for every partition, first is for GB (2.3.6) second is for JB (4.1.2) and the third is for recovery mode - the only difference is that External SDCard is mounted to different location.
If you used vold.fstab mod to swap internal/external storage check the correct path and use it to External SDCard (possibly /sdcard)
BE AWARE! To restore broken IMEI/Serial number you must have backups from ALL 3 partitions and you must restore all of them!
Create nv_backup folder manually on your external SD-card or use this command from ADB shell / terminal:
GB/JB:
Code:
mkdir /sdcard/external_sd/nv_backup
mkdir /storage/extSdCard/nv_backup
From Recovery (if says device busy, sdcard is already mounted):
Code:
mount -t vfat -o rw /dev/block/mmcblk1p1 /sdcard
mkdir /sdcard/nv_backup
EFS partition
This partition contains: product code, BT/WiFi mac address, RIL calibration files, DRM info and some other data like language, timezone set by your provider.
NOTE: Our phone (and I guess all phones with NovaThor SoC) doesn't store IMEI and SimLock information on EFS partition (no nv_data.bin).
Create a backup from EFS partition:
In ADB/Terminal emulator enter this:
Code:
dd if=/dev/block/mmcblk0p7 of=/sdcard/external_sd/nv_backup/efs.bin
dd if=/dev/block/mmcblk0p7 of=/storage/extSdCard/nv_backup/efs.bin
dd if=/dev/block/mmcblk0p7 of=/sdcard/nv_backup/efs.bin
Restoring EFS partition:
Code:
dd if=/sdcard/external_sd/nv_backup/efs.bin of=/dev/block/mmcblk0p7
dd if=/storage/extSdCard/nv_backup/efs.bin of=/dev/block/mmcblk0p7
dd if=/sdcard/nv_backup/efs.bin of=/dev/block/mmcblk0p7
NOTES:
On i8160 EFS partition is the 7th partition
efs.bin will be exactly a 10 MB file which contains every information and files from the EFS partition
ModemFS partition:
If you got unknown baseband or XXXX as baseband (modem/phone version) you probably have problems with this one...
This partition contains: RIL calibaration files the same from /efs, and other configuration files created by the RIL.
Also the STE modem for "everyday" operations uses this partition instead of efs and cspsa, therefore the chance to loose your imei is much lower compared to other Samsung phones (because there is always a working backup from the files on efs and cspsa).
Create a backup from ModemFS partition:
In ADB/Terminal emulator enter this:
Code:
dd if=/dev/block/mmcblk0p2 of=/sdcard/external_sd/nv_backup/modemfs.bin
dd if=/dev/block/mmcblk0p2 of=/storage/extSdCard/nv_backup/modemfs.bin
dd if=/dev/block/mmcblk0p2 of=/sdcard/nv_backup/modemfs.bin
Restoring ModemFS partition:
Code:
dd if=/sdcard/external_sd/nv_backup/modemfs.bin of=/dev/block/mmcblk0p2
dd if=/sdcard/storage/extSdCard/nv_backup/modemfs.bin of=/dev/block/mmcblk0p2
dd if=/sdcard/nv_backup/modemfs.bin of=/dev/block/mmcblk0p2
NOTES:
On i8160 ModemFS partition is the 2nd partition
modemfs.bin will be exactly a 16 MB file which contains every information and files from the MODEMFS partition
CSPSA partition:
This partition contains: RIL calibaration files, IMEI, SimLock data, serial number.
Also on every system start there is a synchronization between CSPSA and Modemfs.
Create a backup from CSPSA partition:
In ADB/Terminal emulator enter this:
Code:
dd if=/dev/block/mmcblk0p6 of=/sdcard/external_sd/nv_backup/cspsa.bin
dd if=/dev/block/mmcblk0p6 of=/storage/extSdCard/nv_backup/cspsa.bin
dd if=/dev/block/mmcblk0p6 of=/sdcard/nv_backup/cspsa.bin
Restoring CSPSA partition:
Code:
dd if=/sdcard/external_sd/nv_backup/cspsa.bin of=/dev/block/mmcblk0p6
dd if=/sdcard/storage/extSdCard/nv_backup/cspsa.bin of=/dev/block/mmcblk0p6
dd if=/sdcard/nv_backup/cspsa.bin of=/dev/block/mmcblk0p6
NOTES:
On i8160 CSPSA partition is the 6th partition
cspsa.bin will be exactly a 1.5 MB file which contains every information from the CSPSA partition
PHONE/BASEBAND "UNKNOWN":
You flashed a wrong modem.img.md5, f.e. you can't flash i8160P/L modem on i8160.
Create a tar from phone part (modem.img.md5) extracted from roms built for your model (i8160/L/P) and flash just the phone.tar with odin.
Or write modem.bin.md5 (not the tar!) directly to modem/phone partition using terminal/adb (requires rooted phone):
If doesn't solves the problem flash a rom made for your model!
Code:
su
dd if=/sdcard/external_sd/modem.bin.md5 of=/dev/block/mmcbk0p13
or
dd if=/storage/extSdCard/modem.bin.md5 of=/dev/block/mmcbk0p13
reboot
If you are using a custom rom copy your original /system/lib/tee folder to the custom roms /system/lib/tee folder!
Automated ZIPs for CWM RECOVERY
only tested with JB and Temp. CWM
extract nv_backup_restore.rar to you sdcard, including the empty nv_backup folder and the 2 zips.
nv_backup.zip/nv_restore.zip will backup/restore all (EFS/MODEMFS/CSPSA) partitions from External SD Card/nv_backup folder.
NOTES:
I highly recommend to do backup/restore from recovery with update.zips or using ADB, it's much safer when the phone is not completly booted.
This method will not give you/change your imei, only creates a backup from the original and restores from an already created (and working) partition image!
There is no sollution to SimUnlock the phone, but the simlock data is on CSPSA_FS.
Sometimes IMEI will stays null/null or shows nothing, flash a JB firmware again might solve the issue.
After a complete JB flash there will be a log file in /efs/pre_recovery.log - the phone writes it when checks and restores IMEI.
The CSPSA and MODEMFS backup must be created from the same state, f.e: a cspsa backup from GB and a MODEMFS backup from JB (or possible even from different GB build) will NOT work!
If your phone's RIL needs to be replaced with a new one old backups will NOT work, you have to create new backups for the new STE MODEM, that could caused by the encryption algorithm.
Nice tutorial, it exactly the problem that I am facing with I8160L version of this ace 2
Please explain if its method could be applied in my case:
I have a I8160L version from brazil, i tried to install custom ROMs fro Kyrillos and Messi, but after update always occurs the same problem that u described. I would like to know if I can apply this method to replace the files and get back my IMEI with european ROMs or, in my case, is a different problem.
Thanks in advance.
I don't think you can bring back your imei now, because it's stored on unknown location.
If you still have that rom which caused the error then flash back to a stock i8160L rom (I think you flashed a wrong modemfs.img.md5 with rom).
Or if you are on a stock L rom and still don't have imei, then dial *#197328640# choose COMMON -> NVREBUILD and after reboot check your imei again.
If doesn't help send the phone back to Samsung and they will fix it.
luigisvc said:
Nice tutorial, it exactly the problem that I am facing with I8160L version of this ace 2
Please explain if its method could be applied in my case:
I have a I8160L version from brazil, i tried to install custom ROMs fro Kyrillos and Messi, but after update always occurs the same problem that u described. I would like to know if I can apply this method to replace the files and get back my IMEI with european ROMs or, in my case, is a different problem.
Thanks in advance.
Click to expand...
Click to collapse
I will post back soon, my phone is also an I8160L. I will attempt to upgrade to KryillosV5 then post back. Wish me luck =3
Read the "How to install (v5)" section carefully he described how to install if you have different i8160.
I think you flashed the european i8160 modem to your i8160l, flashing back to a stock i8160l rom will solve the issue.
Szaby59 said:
I don't think you can bring back your imei now, because it's stored on unknown location.
If you still have that rom which caused the error then flash back to a stock i8160L rom (I think you flashed a wrong modemfs.img.md5 with rom).
Or if you are on a stock L rom and still don't have imei, then dial *#197328640# choose COMMON -> NVREBUILD and after reboot check your imei again.
If doesn't help send the phone back to Samsung and they will fix it.
Click to expand...
Click to collapse
I reflashed stock rom and my phone is working now, but i never tried to install custom ROM again, because I was affraid of permanent damage.
I tried JB, but I can´t go further because o PIT file missing for no european phones.
But now I have a hope to install others ROM and replace the files that u mentioned.
I think you will need to replace the kernel.img.md5 too and that could be a problem because some custom roms have their own custom kernel and there is a good chance it will not work with stock kernels.
No luck. In *#1234# I get PHONE: Unknown. Baseband in About is also unknown. Maybe modem as well? Could you write how to do that too?
Re: [HOW-TO] Repair Baseband (XXXX/unknown) and backup some device specific data
You cant use eu roms on i8160l, try fashing l kernel and modem only or a full stock rom.
Sent from my GT-I8160 using xda app-developers app
In fact I´m using HD custom kernel, it is the only custom file that worked. Only ROM´s get in problems.
I have I8160L too.
I try to flash custom rom such as [ROM][GB-XXLL2] KYRILLOSv5 **Fast n' Lite**.
After flash this rom ... my phone can't detect sim card and lost imei.
then I found this post ...
I try 1.creating&restoring backup from EFS partition
2.create&restoring backup from MODEMFS partition
3.write modem.bin.md5 (not the tar) directly to modem/phone partition using terminal (I extract from I8160L Stock Rom)
but my phone can't detect sim card and lost imei.
I've tried everything I know but fail.
I want you guys some help. I want to use custom rom or I should sell my I8160L phone.
Thank you everyone
(sorry for my english)
theresth said:
I have I8160L too.
...
Click to expand...
Click to collapse
How do flashed an img.md5 with odin ? First you have to make a tar.
Flash back a full L rom to see if it solves the problem.
Szaby59 said:
How do flashed an img.md5 with odin ? First you have to make a tar.
Flash back a full L rom to see if it solves the problem.
Click to expand...
Click to collapse
Sorry ----> 3.write modem.bin.md5 (not the tar) directly to modem/phone partition using terminal (I extract from I8160L Stock Rom)
I can flash back to I8160L Rom and it solves the problem.
But I don't want use stock I8160L rom then I try to flash with I8160 Customrom but fail.
I don't know how to flash my I8160L with custom rom of I8160
please help me please
That's doesn't belong to this topic.
There could be several modifications (kernel, build prop, drivers) why doesn't work with different model, ask on the custom roms own topic.
Szaby59 said:
That's doesn't belong to this topic.
There could be several modifications (kernel, build prop, drivers) why doesn't work with different model, ask on the custom roms own topic.
Click to expand...
Click to collapse
But I doubt why I9300T can use custom rom of I9300.
Here's what I did! ( kyrillos v5 didn't detect sim)
I found a custom ROM which detects my sim!
Replaced the tee folder ( found in /lib) with the tee folder from the rom which worked and then flashed it!
Kyrillos v5 then detected my sim
loof13 said:
Here's what I did! ( kyrillos v5 didn't detect sim)
I found a custom ROM which detects my sim!
Replaced the tee folder ( found in /lib) with the tee folder from the rom which worked and then flashed it!
Kyrillos v5 then detected my sim
Click to expand...
Click to collapse
Its work. Thank you guys for this tip. :good::good::good:
Finally I can flash I8160 custom rom to my I8160L ---> My phone can detect sim card and doesn't lose imei.
I tried only Gingerbread custom rom ---> It's work.
But I doub if i flash jelly Bean rom with the same way ... It's still work ???
(Sorry for my english)
loof13 said:
Here's what I did! ( kyrillos v5 didn't detect sim)
I found a custom ROM which detects my sim!
Replaced the tee folder ( found in /lib) with the tee folder from the rom which worked and then flashed it!
Kyrillos v5 then detected my sim
Click to expand...
Click to collapse
Hell YES!! Thank you! I finally managed to get Kyrillos V5 on my I8160L!
Although it doesnt say Im the 'L' model in the settings
{
"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"
}
Now we just need a way to get Jelly bean to work on it!
is this the tee folder the entire /lib folder with all folders inside?
I don´t understand this part.
thanks
luigisvc said:
is this the tee folder the entire /lib folder with all folders inside?
I don´t understand this part.
thanks
Click to expand...
Click to collapse
Inside the lib folder, there will be a folder called tee!
Problem solved!
**********************
I think my problem happened because a flashed a ROM with MG4 baseband, and then flashed UltimaROM with another baseband which caused my baneband to corrupt.
I tried to flash Stock ROM and install different baseband but non of this worked.
finally I flashed BTU stock ROM (Which comes with MG4) but the problem still here.
Then I installed root, deleted the efs folder and replaced all the files with the files in the backup - restart and everything is working! my IMEI returned to normal.
**********************
Original question
Hello devs,
I have Siyah kernel which auto backup my EFS, i have backup named "efs_28Aug2013-1852.tar.gz"
I want to restore from this backup because I lost my IMEI when I flashed UltimaROM
I renamed it to "efsbackup.tar.gz" and put it in the root of the sdcard
then I started adb shell & run the code
Code:
su
umount /efs
mke2fs /dev/block/mmcblk0p1
mount -w -t ext4 /dev/block/mmcblk0p1 /efs
busybox tar zxvf /sdcard/ efsbackup.tar.gz -C /
I granted ADB shell root access
then i went to recovery and run the command (because I can't run umount /efs while device's running it gives resource busy message)
However when I run the first command "su" in gives me this message
Code:
/sbin/sh: su: not found
so I skipped to the next command
but I get the message
Code:
umount: can't umount /efs: Invalid argument
Please guys any help appreciated
Click to expand...
Click to collapse
Unzip it with a file manager and use a root explorer to replace manually
Sent from my GT-I9300 using Tapatalk 4
.
I've backup my efs with adb but how do you have a file on tar format, i've got a file on .img, it's normal ?
There's about nine different ways to backup the efs, .img is fine but a little on the large side at 20mb. A .tar of the same is only 5mb.
rootSU said:
Unzip it with a file manager and use a root explorer to replace manually
Sent from my GT-I9300 using Tapatalk 4
Click to expand...
Click to collapse
Thank you for your reply, I did as you said but this only changed my IMEI from "Unknown" to the generic IMEI "004999..."
Is there something wrong in the method or my backup may be corrupt
Sent from my Nexus 7 using Tapatalk 2
Read the imei / efs thread in general.
Sent from my GT-I9300 using Tapatalk 4
Thank you again, I read the thread in the past but it looks like it has been updated recently.
I think my problem happened because a flashed a ROM with MG4 baseband, and then flashed UltimaROM with another baseband which caused my baneband to corrupt.
I tried to flash Stock ROM and install different baseband but non of this worked.
finally I flashed BTU stock ROM (Which comes with MG4) but the problem still here.
Then I installed root, deleted the efs folder and replaced all the files with the files in the backup - restart and everything is working! my IMEI returned to normal.
Thank you RootSU for your help.
hey bro,
i am stuck
help me out
- my efs(folder) is blank
- i installed stock with pit file but no help!
- right now my cell is in bootloop!
- it goes to recovery, download mode.
i have efs.tar.gz file and a folder named efs in my ext sd
how do i copy that to int memory?
can't even create a cwm flashable zip file of the same?????
help me bro.....
You are posting in a thread that tells you how to restore an efs backup, how much more could you possibly need?
Go to recovery, factory reset.
Get the phone to boot, unpack the .tar file and follow the instructions in the OP.
boomboomer said:
You are posting in a thread that tells you how to restore an efs backup, how much more could you possibly need?
Go to recovery, factory reset.
Get the phone to boot, unpack the .tar file and follow the instructions in the OP.
Click to expand...
Click to collapse
Dear boomboomer,
i am sorry, but my phone is in "bootloop" how am i suppose to delete the "EFS" ? that s what i am asking!!!!!
i have both efs.tar.gz and extracted folder ready in my ext-sd......
i wonder if somebody can help me with creating a cwm.zip from the .tar file
thanks ....
try to install stock again via odin but this time install a diffrent version (for example if you installed INU this time try INS).. before that factory reset your phone and wipe cache via recovery mode.. don't lose your efs backup it's very important copy it to your PC in case something wrong happens
i already did so
almousawi said:
try to install stock again via odin but this time install a diffrent version (for example if you installed INU this time try INS).. before that factory reset your phone and wipe cache via recovery mode.. don't lose your efs backup it's very important copy it to your PC in case something wrong happens
Click to expand...
Click to collapse
bro, thanks for your help recently i tried cm 10 also but nothing happened.
believe me i tried everything now the only option is left that is
to restore efs backup from efs.tar.gz (which is about 12 MB)
OR
create a cwm flashable zip from the efs folder which is about 22 MB)
OR
take my phone to download mode and try to push whole "efs" folder to the location with help of "ADB"
hello
mikks said:
bro, thanks for your help recently i tried cm 10 also but nothing happened.
believe me i tried everything now the only option is left that is
to restore efs backup from efs.tar.gz (which is about 12 MB)
OR
create a cwm flashable zip from the efs folder which is about 22 MB)
OR
take my phone to download mode and try to push whole "efs" folder to the location with help of "ADB"
Click to expand...
Click to collapse
hello nobody is here to help......??????
mikks said:
hello nobody is here to help......??????
Click to expand...
Click to collapse
Correct this is not a paid for service .
Suggest you take it to a service centre .
know that i did that already....
JJEgan said:
Correct this is not a paid for service .
Suggest you take it to a service centre .
Click to expand...
Click to collapse
thanks for the reply, respect to your reply and interest no disrespect ...
i took that to the center but they failed and by the way they come to me in some cases... so they give me free service...
my phone is in boot loop, i have efs.tar.... can i use phills recovery ????? or can i use someone elses backup... just to boot up my device ...then i'll be good .... i just need to get my device booted up.....
Nexus 5 Modems
All modems are in .zip and .img format. Flash .zip in custom recovery(TWRP/CWM/etc). Flash .img in bootloader/fastboot.
Fun fact: The D820 and D821 modems have matching md5 sums. They are the same modem byte for byte.
This means there are no "D820 modems" or "D821 modems".. there are just "Nexus 5 modems"
And no!! Flashing, for example, a D821 modem to a D820 will NOT give your D820 the D821 LTE bands.
To dump your modem to the root of your internal sdcard:
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/modem of=/sdcard/modem.img
D820
GSM: 850/900/1800/1900 MHz
CDMA: Band Class: 0/1/10
WCDMA: Bands: 1/2/4/5/6/8/19
LTE: Bands: 1/2/4/5/17/19/25/26/41
D821
GSM: 850/900/1800/1900 MHz
WCDMA: Bands: 1/2/4/5/6/8
LTE: Bands: 1/3/5/7/8/20
[See HERE to Enable LTE Bands 3/8 on D820 and LTE Bands 2/4 on D821]
KFS78N (4.4)
M8974A-1.0.25.0.12
AAAAANAZQ1025010
QUALCOMM Incorporated Sept 27 2013
KQS81M (4.4)
M8974A-1.0.25.0.13
AAAAANAZQ1025015
QUALCOMM Incorporated Sept 30 2013
KRT01B (4.4)
M8974A-1.0.25.0.15
AAAAANAZQ1025019
QUALCOMM Incorporated Oct 29 2013
KRT16M (4.4)
M8974A-1.0.25.0.17
AAAAANAZQ1025019
QUALCOMM Incorporated Oct 11 2013
KOT49E (4.4.1)
M8974A-1.0.25.0.23
AAAAANAZQ1025019
QUALCOMM Incorporated Nov 19 2013
KTU84M (4.4.3)
M8974A-2.0.50.1.13
AAAAANAZQ20500017.1
QUALCOMM Incorporated May 7 2014
KTU84P (4.4.4)
M8974A-2.0.50.1.16
AAAAANAZQ20500017.1
QUALCOMM Incorporated Jun 4 2014
KTU84Q (4.4.4 Release 2)
M8974A-2.0.50.1.17
AAAAANAZQ20500017.1
QUALCOMM Incorporated Jun 9 2014
LPV79 (L Preview)
M8974A-2.0.50.2.08
AAAAANAZQ20500018
QUALCOMM Incorporated May 7 2014
LPX13D (L Preview)
M8974A-2.0.50.2.21
AAAAANAZQ20500024
QUALCOMM Incorporated Oct 1 2014
LRX22C (5.0.1)
M8974A-2.0.50.2.22
AAAAANAZQ20500024
QUALCOMM Incorporated Nov 17 2014
LMY47D (5.1)
M8974A-2.0.50.2.25
AAAAANAZQ20500024
QUALCOMM Incorporated Jan 14 2015
LMY48B (5.1.1)
M8974A-2.0.50.2.26
AAAAANAZQ20500024
QUALCOMM Incorporated Mar 26 2015
MRA58K (6.0)
M8974A-2.0.50.2.27
AAAAANAZQ20500024
QUALCOMM Incorporated Jun 24 2015
MMB29K (6.0.1)
M8974A-2.0.50.2.28
AAAAANAZQ20500024
QUALCOMM Incorporated Oct 20 2015
DOWNLOAD MODEMS FROM CODEFIRE HERE
EFS Backup
The Nexus 5 has no built in EFS backup partitions. EFS contains things like your MEID or IMEI... your data profiles.. radio settings. The EFS cannot be replaced... it is unique to your phone only... backing up your OWN EFS is highly recommended.
I want to point out... if using TWRP to backup EFS... try to have an original backup and save that off the device somewhere. Down the road you may end up with lots of EFS backups(if you backup via TWRP each time) and somewhere along the line you could mess your EFS up.. perhaps worse over the course of a month. If you get into the habit of only saving your most recent EFS backup... that recent EFS backup may already be partially damaged. I'm not saying don't make frequent backups.. just have the very first one tucked away somewhere.
DO NOT RESTORE EFS BACKUPS TO ANYTHING OTHER THAN THE ORIGINAL PHONE.
Backing up EFS
In TWRP, flash the Nexus5_Flash2BackupEFS.zip linked below. Nexus5_Flash2BackupEFS.zip creates a flashable zip backup of your EFS in /sdcard/EFS_Backup/. Please check to make sure the backup zip worked and actually made a .zip file. If you can't find it under /sdcard/EFS_Backup/... try /data/media/0/EFS_Backup/ instead.
Flashable EFS Backup Zip = HERE
To manually backup EFS:
Code:
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/modemst1 of=/sdcard/modemst1.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/modemst2 of=/sdcard/modemst2.img
Backup your Nexus5_EFS_Flashable_Restore.zip or EFS partitions somewhere else besides your internal SD!!! Email.. cloud.. PC..
Restoring EFS
To restore your original EFS just boot into recovery and flash the Nexus5_EFS_Flashable_Restore.zip in your /sdcard/EFS_Backup/ folder.
To manually restore EFS:
Code:
adb shell
su
dd if=/sdcard/modemst1.img of=/dev/block/platform/msm_sdcc.1/by-name/modemst1
dd if=/sdcard/modemst2.img of=/dev/block/platform/msm_sdcc.1/by-name/modemst2
This is one of the most valuable posts for hammerhead yet. Everyone should take 2 minutes and do this.
autoprime said:
Don't see your modem version? If you have a D821 please PM me.
Click to expand...
Click to collapse
Great work!
I have a D821 (international), i've copied the modem file from /dev/block/platform/msm_sdcc.1/by-name/modem to my sdcard using rootexplorer.
Is this the file you're looking for?
Great work. Thanks for the piece of mind
Sent from my SGH-I337M
Here it is in script format. Not recovery flashable, not directly restorable. Requires busybox.
Code:
echo "";
echo "Creating backup directory: /storage/sdcard0/EFS Backup.";
mkdir -p "/storage/sdcard0/EFS Backup/temp/";
cd "/storage/sdcard0/EFS Backup/temp/";
echo "Commencing backup...";
echo "Copying mmcblk0p12: modemst1";
dd if=/dev/block/mmcblk0p12 of=p12_modemst1.img > /dev/null 2>&1;
echo "Copying mmcblk0p13: modemst2";
dd if=/dev/block/mmcblk0p13 of=p13_modemst2.img > /dev/null 2>&1;
datetime=$(date +'%Y%m%d_%H%M');
echo "Compressing backup (backup_$datetime.tar.gz)...";
tar -chzf "/storage/sdcard0/EFS Backup/backup_$datetime.tar.gz" *;
echo "Cleaning up...";
rm -rf "/storage/sdcard0/EFS Backup/temp/";
echo "Backup complete!";
echo "";
What's efs?
Sent from my Nexus 5 using Tapatalk
This is what I've been waiting for. Well this and my device. lol Thanks.
Can these be pulled with adb? I wrote a script to dump everything using adb. It should be the same end result, right?
So efs isn't getting backed up with regular twrp system, data, boot options checked? I'm guessing we keep the back up separate--just a "just in case" thing, am I right? In general, we should be able to backup, flash, and restore without ever losing efs, correct?
Thanks all.
Nexus 5--That is all.
What's up Killa long time. Thanks for providing bro. How's philly treating you? Need to come hit Pats or Ginos.
Sent from my Nexus 7 using Tapatalk 4
gee one said:
Can these be pulled with adb? I wrote a script to dump everything using adb. It should be the same end result, right?
Click to expand...
Click to collapse
yes, tho id suggest using adb while in recovery and not while the phone is booted if possible.
pathtologos said:
So efs isn't getting backed up with regular twrp system, data, boot options checked? I'm guessing we keep the back up separate--just a "just in case" thing, am I right? In general, we should be able to backup, flash, and restore without ever losing efs, correct?
Thanks all.
Nexus 5--That is all.
Click to expand...
Click to collapse
yes it's a just in case thing.. tho suggested if you're flashing stuff around. Never know when it may come in handy.
TWRP should be adding an EFS backup option.. you will soon see an EFS box to check along with the usual Boot, Data, System options.
pathtologos said:
So efs isn't getting backed up with regular twrp system, data, boot options checked? I'm guessing we keep the back up separate--just a "just in case" thing, am I right? In general, we should be able to backup, flash, and restore without ever losing efs, correct?
Thanks all.
Nexus 5--That is all.
Click to expand...
Click to collapse
Yea... essentially just in case it happens. Was a known and fairly common occurrence on the Galaxy S3. Believe the issue was that that the IMEI number and such was stored essentially in an accessible part of storage, and there was a chance that performing a factory reset and flashing a new ROM could have wiped out the IMEI number stored on the phone... resulting in a tedious process of having to go in and manually re-enter it i believe through ADB somehow. It actually happened to my GS3, but thankfully i had actually performed said backup a month or a few prior to it happening, so getting it back was a breeze.
casonswag said:
What's efs?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Did you read the OP?
EFS Backup
The Nexus 5 has no built in EFS backup partitions. EFS contains things like your MEID or IMEI... your data profiles.. radio settings. The EFS cannot be replaced... it is unique to your phone only... backing up your OWN EFS is highly recommended.
grneyez said:
Did you read the OP?
EFS Backup
The Nexus 5 has no built in EFS backup partitions. EFS contains things like your MEID or IMEI... your data profiles.. radio settings. The EFS cannot be replaced... it is unique to your phone only... backing up your OWN EFS is highly recommended.
Click to expand...
Click to collapse
Um i didnt understand it thays why i was asking n was gonna ask do we have to back it up but i see u say recommended
Sent from my Nexus 5 using Tapatalk
I would highly recommend you doing so, its very easy and can save you a lot of headaches if the EFS gets screwed up somehow.
Sent from my Nexus 5 using Tapatalk
What is Modems and EFS backup?
A noob question
What is flashable Modem and EFS backup means?
Thanks in advance
Does this mean that the modems can be interchanged - made from D820 model D821?
Regards
So with the backup if we want to go back flash the modem then backup or vise versa?
Sent from my Nexus 5 using Tapatalk
casonswag said:
So with the backup if we want to go back flash the modem then backup or vise versa?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
root/unlock bootloader... install twrp.. backup efs... store efs backup off the device somewhere... flash modems/roms/anything you want.
autoprime said:
root/unlock bootloader... install twrp.. backup efs... store efs backup off the device somewhere... flash modems/roms/anything you want.
Click to expand...
Click to collapse
What about going back to normal modem i had flash the latest modem then the backup?
Sent from my Nexus 5 using Tapatalk