Modem Backup - Asus Padfone X and S

Can someone with a padfone x on att rom backup the modem / radio with efs professional and post?
http://forum.xda-developers.com/gal...ol-updated-09-06-14-efs-professional-t1308546
in efs pro you need to be rooted.
select efs pro in the menu then select backup
then in device filters select all partitions
check modem modemst1 and modemst2 uncheck all others and post the tar.gz file?
Thanks

Related

help...Restore Galaxy s3 imei no?

Hello
I have a China Mobile galaxy gs3 i9308, and the imei no. was changed to 0000000000000/null because of rom flashing (I think).
Now I am not registered on the network, so I have to change the imei no. back.
I tried several tutorials online, but seems like they're only for the galaxy s.
I tried the 9 step guide but I can't find the .nv_data file in my efs folder.
Can anyone help me or point me in the right direction?
Thank you
http://www.youtube.com/watch?v=JqLK_2I-SBM
check may be it helps
vegeta1 said:
http://www.youtube.com/watch?v=JqLK_2I-SBM
check may be it helps
Click to expand...
Click to collapse
Thanks for the quick reply. But I followed the written version of the guide and it only works for galaxy s? Because in my nv_data.bin file there's no line 00188008 in hex editor.
this is the link to that thread: http://forum.xda-developers.com/showthread.php?t=881162
The video poster also said it only worked for galaxy s.
Any other ideas?
hey, I have the same problem, SGS3 with wrong imei 0049.... i lose my efs file, someone can help us?
You could try flashing stock rom, heard that this sometimes restores imei, not sure if it works on s3
Also, check if the rom or kernel you flashed created a eggs backup, some do
Sent via TCP/IP
Please help
i have the same problem i cant fix my imei, after flashing the phone it changed to 00499.. it made no backups and no nv_data.bin.bak
If the efs folder havent been backed up, what can i do? I tried changing the nv_data file like some tutorials here explain, but no luck(tried couple of times, it defently not compatible with my galaxy s3), i believe these tutorials are for erlier galaxies.
Please help!
Thank you
Sent from my GT-I9300 using xda app-developers app
Flashing a stock rom works then root again it worked for me using a UK 3 official rom
Sent from my GT-I9300 using xda premium
dazzztom said:
Flashing a stock rom works then root again it worked for me using a UK 3 official rom
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
it shouldn't work for restoring IMEI on the S3
tomniu said:
Hello
I have a China Mobile galaxy gs3 i9308, and the imei no. was changed to 0000000000000/null because of rom flashing (I think).
Now I am not registered on the network, so I have to change the imei no. back.
I tried several tutorials online, but seems like they're only for the galaxy s.
I tried the 9 step guide but I can't find the .nv_data file in my efs folder.
Can anyone help me or point me in the right direction?
Thank you
Click to expand...
Click to collapse
Try this : http://forum.xda-developers.com/showthread.php?t=1801997
Did you back up the efs folder before you flash your device?
I understood that imei numbers were hardwired into the phone. And changing them n having the equipment was illegal. This is what the networks use to bar your phone if it gets stolen.
Sent from my GT-I9300 using xda app-developers app
eddydo said:
Did you back up the efs folder before you flash your device?
Click to expand...
Click to collapse
I don't know about international S3 but here in USA IMEI is not located in EFS folder.
chris170569 said:
I understood that imei numbers were hardwired into the phone. And changing them n having the equipment was illegal. This is what the networks use to bar your phone if it gets stolen.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
This program was created not to spoof IMEI just to restore if you have problem with it.
How to restore your IMEI number on SGS3 (GT-i9300)
I deleted my IMEI number when flashing roms a few days ago and it was showing as 000000...
I searched everywhere for a recipe of how to restore it and could not find one that would work. The closest that I got was a brilliant post (see link below) describing how to restore the IMEI on a SGS2 i9100. After following this recipe, I was able to restore my IMEI number to 0049 .... which is just as useless as 0000....
It took me a couple of days of research (and HUGE thanks to everybody whose previous research I was able to use) and I finally succeeded in restoring my IMEI using the 9 step process that I describe below. I can't guarantee that it will work and I do not know if it will work on any device besides the SGS3 GT-i9300 (international SGS3), because this is the only device that I have and was able to test the process on.
Links:
Restore IMEI on SGS2: http://forum.xda-developers.com/showthread.php?t=1264021
Download EFS PRO: http://forum.xda-developers.com/showthread.php?t=1308546
Download your original firmware using check fus downloader (http://forum.xda-developers.com/showthread.php?t=1032437&page=18)
You need:
-EFS PRO, a brilliant little program for Windows used to backup / restore the efs folder as well as recover / repair the nv_data*.bin files.
-Windows
-Windows USB drivers
-Rooted SGS3
-Root explorer.apk
-Original phone firmware (actually, you only need the modem.bin file, so once you download your firmware package, you can just extract the modem.bin file).
-Odin or Heimdall
Your phone's IMEI number is stored in the ".nv_data" file in the original shipped efs folder.
Process:
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
Good luck and let me know how it goes
Leahcim
do i have to delete the .nv_core.bak and the .nv_core.bak.md5
---------- Post added at 04:10 PM ---------- Previous post was at 04:04 PM ----------
and which nv_data file do i have to copy i got 7 of them
but if this will not fix my phone, can samsung fix it without replacing the motherboard
---------- Post added at 08:36 PM ---------- Previous post was at 08:35 PM ----------
my imei change sudden when i try to unlock my phone with messing the efs folder but i didn't backup it :crying:so now i dont have network
i have managed to follow all your steps and managed to get my IMEI back.
when i pressed *#06# i was able to see a series of numbers so i guess i got it right.
but i am still not connected to any network. please help!!
leahcim_za said:
I deleted my IMEI number when flashing roms a few days ago and it was showing as 000000...
I searched everywhere for a recipe of how to restore it and could not find one that would work. The closest that I got was a brilliant post (see link below) describing how to restore the IMEI on a SGS2 i9100. After following this recipe, I was able to restore my IMEI number to 0049 .... which is just as useless as 0000....
It took me a couple of days of research (and HUGE thanks to everybody whose previous research I was able to use) and I finally succeeded in restoring my IMEI using the 9 step process that I describe below. I can't guarantee that it will work and I do not know if it will work on any device besides the SGS3 GT-i9300 (international SGS3), because this is the only device that I have and was able to test the process on.
Links:
Restore IMEI on SGS2: http://forum.xda-developers.com/showthread.php?t=1264021
Download EFS PRO: http://forum.xda-developers.com/showthread.php?t=1308546
Download your original firmware using check fus downloader (http://forum.xda-developers.com/showthread.php?t=1032437&page=18)
You need:
-EFS PRO, a brilliant little program for Windows used to backup / restore the efs folder as well as recover / repair the nv_data*.bin files.
-Windows
-Windows USB drivers
-Rooted SGS3
-Root explorer.apk
-Original phone firmware (actually, you only need the modem.bin file, so once you download your firmware package, you can just extract the modem.bin file).
-Odin or Heimdall
Your phone's IMEI number is stored in the ".nv_data" file in the original shipped efs folder.
Process:
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
Good luck and let me know how it goes
Leahcim
Click to expand...
Click to collapse
IMEI restore on SGS 3 (GT-i9300)
ronaldshi said:
i have managed to follow all your steps and managed to get my IMEI back.
when i pressed *#06# i was able to see a series of numbers so i guess i got it right.
but i am still not connected to any network. please help!!
Click to expand...
Click to collapse
Hi there
You need YOUR IMEI number back (which is not 00000... or 0049...) it is the one under your battery.
If you followed all the steps, then it should have worked.
One extra thing that you can try is if you did not flash your original phone firmware (and you only flashed the original modem.bin file) then do this step first.
And then work through the 9 step process, ignoring the step where you flash your original firmware (because you will have already done it).
Good luck and let me know when it works
---------- Post added at 12:16 PM ---------- Previous post was at 12:10 PM ----------
lobird said:
but if this will not fix my phone, can samsung fix it without replacing the motherboard
---------- Post added at 08:36 PM ---------- Previous post was at 08:35 PM ----------
my imei change sudden when i try to unlock my phone with messing the efs folder but i didn't backup it :crying:so now i dont have network
Click to expand...
Click to collapse
Hi there
Good news is that it will work - even if you did not back up your efs folder before you messed with it!
Give it a try and let me know when it is fixed.
Good luck
Procedure not work!
leahcim_za said:
I deleted my IMEI number when flashing roms a few days ago and it was showing as 000000...
I searched everywhere for a recipe of how to restore it and could not find one that would work. The closest that I got was a brilliant post (see link below) describing how to restore the IMEI on a SGS2 i9100. After following this recipe, I was able to restore my IMEI number to 0049 .... which is just as useless as 0000....
It took me a couple of days of research (and HUGE thanks to everybody whose previous research I was able to use) and I finally succeeded in restoring my IMEI using the 9 step process that I describe below. I can't guarantee that it will work and I do not know if it will work on any device besides the SGS3 GT-i9300 (international SGS3), because this is the only device that I have and was able to test the process on.
Links:
Restore IMEI on SGS2: http://forum.xda-developers.com/showthread.php?t=1264021
Download EFS PRO: http://forum.xda-developers.com/showthread.php?t=1308546
Download your original firmware using check fus downloader (http://forum.xda-developers.com/showthread.php?t=1032437&page=18)
You need:
-EFS PRO, a brilliant little program for Windows used to backup / restore the efs folder as well as recover / repair the nv_data*.bin files.
-Windows
-Windows USB drivers
-Rooted SGS3
-Root explorer.apk
-Original phone firmware (actually, you only need the modem.bin file, so once you download your firmware package, you can just extract the modem.bin file).
-Odin or Heimdall
Your phone's IMEI number is stored in the ".nv_data" file in the original shipped efs folder.
Process:
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
Good luck and let me know how it goes
Leahcim
Click to expand...
Click to collapse
Thanks a lot for the advice regarding SG3 IMEI restoring, but this prosedure doesn't change IMEI !!!
EFS PRO actions was Ok.
Can you help me? Pleeeeeease.
P.S. I know original IMEI numbers
in step 2 you say efs but delete the folder, but when I do that I reboot and I get a message telling me the whole time the camera is null and void wi fi all the options, it is this?
pd. sorry for my English (I'm using google translate)
leahcim_za said:
Hi there
You need YOUR IMEI number back (which is not 00000... or 0049...) it is the one under your battery.
If you followed all the steps, then it should have worked.
One extra thing that you can try is if you did not flash your original phone firmware (and you only flashed the original modem.bin file) then do this step first.
And then work through the 9 step process, ignoring the step where you flash your original firmware (because you will have already done it).
Good luck and let me know when it works
Click to expand...
Click to collapse
I do not remember my previous version, only the update when I asked him to put kies, I can use this firmware?
I9300BVBLG2_I9300TMUBLG1_TMU
I just do not see the ". nv_data"

[GUIDE] Backup/Restore LG Optimus G EFS Partitions

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.

[Q] How to restore EFS folder [empty folder]

I made the silly mistake of not doing a complete backup of my EFS folder before flashing my cellphone with a custom ROM:crying:
and now my EFS folder is empty;if I delete it with ES File Manager (my phone is rooted) as soon as I reboot the phone, the EFS folder is created again,
but it is empty.I'm able to make and receive phone calls,send and receive sms,use wireless,bluetooth and gps,but if I dial *#06# my IMEI is blank.
With Galaxy Tool Box (the Rom installed it) --> Device Information I can see my correct IMEI (same number write in the battery slot).
I have a CWM backup and these files are in the backup folder: .android_secure.vfat.tar / boot.img / cache.rfs.tar / data.rfs.tar / nandroid.md5 / system.rfs.tar
Could one of these files help me restore my EFS folder (with all the files ofc)? Even the Product code is gone (KIES doesn't recognize the device)
I've got the the original stock firmware for my italian GT-S 5830i ,and I've tried to flash it with ODIN (PDA/MODEM/CSC) but that was pointless.
Thanks in advance for your time and consideration.
Have a nice day.
[email protected] said:
I made the silly mistake of not doing a complete backup of my EFS folder before flashing my cellphone with a custom ROM:crying:
and now my EFS folder is empty;if I delete it with ES File Manager (my phone is rooted) as soon as I reboot the phone, the EFS folder is created again,
but it is empty.I'm able to make and receive phone calls,send and receive sms,use wireless,bluetooth and gps,but if I dial *#06# my IMEI is blank.
With Galaxy Tool Box (the Rom installed it) --> Device Information I can see my correct IMEI (same number write in the battery slot).
I have a CWM backup and these files are in the backup folder: .android_secure.vfat.tar / boot.img / cache.rfs.tar / data.rfs.tar / nandroid.md5 / system.rfs.tar
Could one of these files help me restore my EFS folder (with all the files ofc)? Even the Product code is gone (KIES doesn't recognize the device)
I've got the the original stock firmware for my italian GT-S 5830i ,and I've tried to flash it with ODIN (PDA/MODEM/CSC) but that was pointless.
Thanks in advance for your time and consideration.
Have a nice day.
Click to expand...
Click to collapse
The EFS Partition doesn't contain any files, it only contains raw HEX Data so it is normal for it to be empty. I recommend you install a custom kernel then flash the stock ROM via Odin as this has worked for me in the past.

Android Non-Volatile location?

I was wondering if the so called NV 'memory' is actually stored on the file system as well. It is normally shortened as NV or NV-items.
I see there is /efs in the file system. So the question is, is NV stored somewhere in file system too?
idoit said:
I was wondering if the so called NV 'memory' is actually stored on the file system as well. It is normally shortened as NV or NV-items.
I see there is /efs in the file system. So the question is, is NV stored somewhere in file system too?
Click to expand...
Click to collapse
You can check with many imei or EFS or partitions backup tool developers, NV Items are stored in modemst1 and modemst2 partitions for MSM89xx. It is changed to mdm9kefs1 mdm9kefs2 and mdm9kefs3 for APQ80xx +MDM96xx based models. Sammy android userdata have very litmited items mapping with "efs", only BT and WiFi mac address are too far from hundreds of NV items for a normal android phone.
Thank you @Azlun.
So now a simple question: How come I can read and write on modemst1 and modemst2 partitions without having root access? (My phone is absolutely untouched).
No,I think no way in generally in case you have a locked bootloader and unrooted.
Even,in some case, you are lucky to own a motorola phone, and know its SPC, then you can use PC tools such as QPST to read/write NV items by items after boot from bootloader BP tool mode. No other workaound as my knowlege since partition s are only accessable by root user.

How to create a full backup of the device (with all partitions) for img file ???

How to create a full backup of the device (with all partitions) for img file?
To do flash via odin for example.
Backup
jrs007 said:
How to create a full backup of the device (with all partitions) for img file?
To do flash via odin for example.
Click to expand...
Click to collapse
To take backup as you say for all img you have to flash TWRP recovery then go to backup menu then select partitions which you want to then switch to backup
But note that backup will not small at least 5 to 10 gb it will if you include Data partition also

Categories

Resources