/EFS partition contains a lot of information about your phone, f.e: wifi/bt mac address and your IMEI (nv_data.bin).
It's highly recommended to backup the whole partition, or at least copy the files from the efs directory.
CORRUPTED OR NOT?
You can check if the efs is mounted or completly damaged with this command:
adb shell
mount
You will see something like this:
{
"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"
}
Red part means /efs is mounted.
IF YOUR PHONE HAVE CORRECT EFS PARTITION:
1, Root your phone - there are several methods to do this.
2, Install root explorer or Estrongs file explorer and copy /efs dir to your sdcard - this will copy the files.
or
2, Make a backup from the whole partition -this is better if you flash a phone with wrong ops, the only way to restore using this backup.
Backup:
adb shell
su
dd if=/dev/block/stl4 of=/sdcard/efs.rfs
Restore:
Add efs.rfs to and unix compatible tar and flash with odin as efs file:
IF YOUR PHONE /EFS IS CORRUPTED:
Flash the included /efs tar with odin:
This will remount your efs partition and (if you have a backup or fixed nv_data.bin) you just need to overwrite files with a file explorer.
what is the point to copy the other thread?
http://forum.xda-developers.com/showthread.php?t=888193
Related
Is there a way to backuo my efs data on the 7+ yet?
MacZzang said:
Is there a way to backuo my efs data on the 7+ yet?
Click to expand...
Click to collapse
Method with EFS Pro - For Samsung Android Devices ;http://forum.xda-developers.com/showthread.php?t=1308546
Method with Android Terminal Emulator ;
1 Install the Google Android Play Terminal Emulator.https://play.google.com/store/apps/...251bGwsMSwxLDEsImphY2twYWwuYW5kcm9pZHRlcm0iXQ..
Will allow us to manually launch the commands to backup.
2 Start Android Terminal Emulator.
Type the command on and give enter.
{
"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"
}
3 You will be prompted that allows the application to obtain the rights to root (if it has never been done).
4 Type the following command respecting all spaces and any capitals:
busybox tar zcvf /sdcard/efs-backup.tar.gz /efs
5 After a few seconds the operation comes to an end. The procedure can be considered complete
6 The command does nothing but create a compressed archive called efs-backup.tar.gz within memory /sdcard. We recommend that you make a copy of transfer even on your pc.
7 Always to be sure of the success of the operation, open the archivo compressed (by phone through file manager or from your pc using winrar, 7zip or the like) and make sure they are present especially the nv_data.bin and nv_data.bin.md5 .
On the behalf of everyone here I solute u my friend they should make this post a sticky in the development section. Efs corruption is a serious issue.. it happened to me on my sgs2 and I couldn't get it back.. and I couldn't find someone with a box to restore it.. I had to buy a box for 260$ online
Sent from my GT-P6200 using XDA Premium HD app
EFS BACKUP AND RESTORE APPfor i9105P and i9105
Developed by xenon92
An app to help you backup your EFS Partition and Restore it if necessary.
No Terminal and No Commands.
Simple taps on the screen.
* ROOT PERMISSIONS NEEDED *
Even though I developed this app for Galaxy Grand i9082 and i9082L users, this app will work with i9105P and i9105 too. Thanx to @fmehdi for testing and pointing it out.
EFS partition blocks of i9105P, i9105 and i9082 are same. See the links below and the EFS partition blocks in the device trees.
i9082 - LINK
i9105P - LINK
i9105 - LINK
Why you need to backup your EFS?
>> READ THIS <<
INSTRUCTIONS
BACKUP
Tap Backup. That's all.
You'll find 'efs.img' in the folder 'EFS_Backup' in your storage memory.
Copy it to your PC or Cloud to be safe.
RESTORE
Open the app once. Exit the app.
Place 'efs.img' in the folder 'EFS_Backup' in your memory. (Folder will be automatically made at first run of the app).
Tap Restore.
WARNING: Do Not RESTORE your EFS until absolutely necessary. If everything is working fine, just BACKUP, don't RESTORE. Read more about it in the link above.
{
"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"
}
CLICK HERE TO DOWNLOAD FROM ORIGINAL THREAD
DISCLAIMER: I am not responsible if you mess up your phone using this app. The functioning of this app is the same as I have explained in the link above. Restoring EFS is dangerous. If you feel unsafe, use the guide I have made in the link above and use Terminal Commands. This app simply implements those Terminal commands in a user friendly way to backup and restore EFS.
Reserved...
Good :good:
I have a rooted device Xiaomi Poco X3 Pro.
I am copying the the file to /system/bin.
The file stays only until I reboot device. The same with TWRP recovery.
What's the correct way to solve this problem?
What I figured out so far the path /system/bin is using tmpfs system. This would explain why changes do not stay. How can I modify it?
{
"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"
}
fastman92 said:
I have a rooted device Xiaomi Poco X3 Pro.
I am copying the the file to /system/bin.
The file stays only until I reboot device. The same with TWRP recovery.
What's the correct way to solve this problem?
What I figured out so far the path /system/bin is using tmpfs system. This would explain why changes do not stay. How can I modify it?
View attachment 5440407
Click to expand...
Click to collapse
[GUIDE] How to make your System RW / Super R/W read/write-able
Welcome to the one and only, the original, universal SystemRW / SuperRW feat. MakeRW / ro2rw by lebigmac This script removes the read-only lock of all partitions embedded in the super partition of your stock firmware. This allows you to mount...
forum.xda-developers.com
Thanks, I may try it later.
I have read about the system-on-root.
Because the file should be copied by other users as well and executed it will make better sense to put this file under /data instead.
Hi,
i just bought my gf a samsung evo 128gb sd card for her Nokia 5.3. At first it said its damaged and the formatting in android didnt do anything. So then i tried to use PC and saw that there was no file system at all, but even after formatting it it didnt work. Then i tried using adb to force it to format which kinda worked.
{
"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"
}
I read online both to use the id you get from list-disks aswell as those you get from list-volumes.
What did work was the volume id (179,64). However using "sm partition disk:179,64 mixed 90" was the highest number that worked, since sm partition disk:179,64 private" didnt work at all. The device simply didnt recognize the sd anymore.
And even now the device claims that most of the storage is already being used, despite the card still being empty.
What can i do to fix it and have the entire sd as internal storage??
When a SD-card is accepted as adoptable storage, the Android OS deletes the contents and writes a GUID partition table that defines two partitions:
A small empty android_meta partition reserved for future use. The GUID of the partition type is 19A710A2-B3CA-11E4-B026-10604B889DCF.
A large android_ext partition encrypted with dm-crypt and formatted with either ext4 or f2fs depending on kernel capabilities. The GUID of the partition type is 193D1EA4-B3CA-11E4-B075-10604B889DCF.
I have an old Galaxy Grand Prime (SM-S920L) and I decided to do something about this old phone. I flashed TWRP and LineageOS Go.
However, when I go to phone app and type dialer code *#06#, there is no IMEI listed and phone app will crash. Any dialer code will crash also.
I looked in About Phone menu, and I see IMEI listed as Unknown.
How can I repair the IMEI?
{
"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"
}
If I'm right then EFS ( read: Encrypted File System ) is a partition housed on device's eMMC ( read: embedded MultiMedia Card ) memory module (where all Android partitions are stored ) , whereas NVRAM ( read: Non-Volatile Random Access Memory) is an extra memory module what is independant of eMMC.
It depends on OEM where IMEI is stored.
So the question: Have you taken a backup of NVRAM and/or EFS partition before flashing LOS?
jwoegerbauer said:
If I'm right then EFS ( read: Encrypted File System ) is a partition housed on device's eMMC ( read: embedded MultiMedia Card ) memory module (where all Android partitions are stored ) , whereas NVRAM ( read: Non-Volatile Random Access Memory) is an extra memory module what is independant of eMMC.
It depends on OEM where IMEI is stored.
So the question: Have you taken a backup of NVRAM and/or EFS partition before flashing LOS?
Click to expand...
Click to collapse
I didn't make a backup of the NVRAM, and I just did a Wipe excluding /data/media.