Database Users

Restoring a dd backup with Odin (A fix for a badly broken EFS)

I was reading rotohammer's post about an easy on-device backup method (using dd) that can restore data at a bit more of a lower level (Odin) than a nandroid backup. (EFS partitions, etc.)
It's possible to get your EFS partition in such a state that the /dev/block/bml3 and /dev/block/stl3 devices are no longer exposed on the device at all. This results in such nice behavior as the Cellular portion of the device not functioning at all. Providing you made a dd backup of all bml and stl devices (i.e. you have a backup of stl3 specifically,) you can recover from this situation.
Odin can recognize any file defined in the .pit file, when they are flashed to the PDA slot in a .tar, and place them in their proper partitions. One benefit to this is that if you get the EFS partition to a place where the device nodes aren't exposed to the OS anymore, you can restore it to working functionality.
These are the possible filenames that Odin recognizes: (from 512.pit, other .pits may have differing partition schemes.)
Code:
ries.pit
efs.rfs (this is the file we are going to restore to fix a broken EFS with a dd backup)
sbl.bin
param.lfs
zImage (kernel and recovery)
factoryfs.rfs
dbdata.rfs
cache.rfs
modem.bin
Any of these files are flashable by Odin3 1.7 if you place them in a .tar and put in the PDA slot.
rotohammer's post details which device matches up with which filename, in this case what we want to do is name the /dev/block/stl3 backup efs.rfs, and add it to a tar file (efs.tar) then flash it.
Assuming you have adb installed, and the stl3.bin file in the current folder:
adb push stl3.bin /sdcard/efs.rfs
adb shell
$ su
#
# cd /sdcard
# tar -cf efs.tar efs.rfs
# exit
$ exit
adb pull /sdcard/efs.tar
Now, get into download mode, open odin, stick efs.tar in PDA slot, and press start. Bam! EFS fixed
Note that in normal conditions you won't need a backup this extreme (copies of the files inside will be ok) but i've seen a number of users who have gotten their phones into this state (and did it myself during testing!) - This works with all the partitions you back up with dd that have support in your .pit file.
I've also used this to make an odin backup of my ROM, and flash it back later. This way you can have a pre-lagfixed ROM, for example
Dedicated to cerjam

how to obtain stl3 and bml3
in adb
adb shell
su (allow the root access)
cat /dev/block/stl3 > /sdcard/stl3.bak
cat /dev/block/bml3 > /sdcard/bml3.bak
rename .bak by .bin
sorry for my english.

Da_G said:
I was reading rotohammer's post
I've also used this to make an odin backup of my ROM, and flash it back later. This way you can have a pre-lagfixed ROM, for example
Dedicated to cerjam
Click to expand...
Click to collapse
How can I make ODIN back of my ROM, a little guide would help. Thanks in advance for your response.

trip007in said:
How can I make ODIN back of my ROM, a little guide would help. Thanks in advance for your response.
Click to expand...
Click to collapse
hi please use the search button , you will easily find how to , this is a 5 month old thread ....

Gonna go out on a limb and assume they are using search, hence the 5 month old post bump.

whiteguypl said:
Gonna go out on a limb and assume they are using search, hence the 5 month old post bump.
Click to expand...
Click to collapse
I dunno how they used it but htere s a 2 weeks old post by darky in the i9000 section .

can someone upload efs.rfs?efs.tar?
i screwd mine and i dont have backup

Every device has there own efs folder (IMEI and stuf).
So if you don't have a backup I don't know what to tell you...

thats not nv_data.bin or imei and product code stuffi want efs partition structure
wich come from stl3.bin

This thread may be almost a year old, but it just saved my Infuse.
Once again it just proves that if you serach, read, try and search, read and try somemore, you can find the answers.

Truckerglenn said:
This thread may be almost a year old, but it just saved my Infuse.
Once again it just proves that if you serach, read, try and search, read and try somemore, you can find the answers.
Click to expand...
Click to collapse
Someone gets it lolz .
Sent from my SAMSUNG-SGH-I897 using xda premium

moeinf said:
thats not nv_data.bin or imei and product code stuffi want efs partition structure
wich come from stl3.bin
Click to expand...
Click to collapse
Sorry im late...but adamoutler was going to post a blank efs partition in another thread . Dont know what happenwd to it tho.
Sent from my SAMSUNG-SGH-I897 using xda premium

Da_G said:
I was reading rotohammer's post about an easy on-device backup method (using dd) that can restore data at a bit more of a lower level (Odin) than a nandroid backup. (EFS partitions, etc.)
It's possible to get your EFS partition in such a state that the /dev/block/bml3 and /dev/block/stl3 devices are no longer exposed on the device at all. This results in such nice behavior as the Cellular portion of the device not functioning at all. Providing you made a dd backup of all bml and stl devices (i.e. you have a backup of stl3 specifically,) you can recover from this situation.
Odin can recognize any file defined in the .pit file, when they are flashed to the PDA slot in a .tar, and place them in their proper partitions. One benefit to this is that if you get the EFS partition to a place where the device nodes aren't exposed to the OS anymore, you can restore it to working functionality.
These are the possible filenames that Odin recognizes: (from 512.pit, other .pits may have differing partition schemes.)
Code:
ries.pit
efs.rfs (this is the file we are going to restore to fix a broken EFS with a dd backup)
sbl.bin
param.lfs
zImage (kernel and recovery)
factoryfs.rfs
dbdata.rfs
cache.rfs
modem.bin
Any of these files are flashable by Odin3 1.7 if you place them in a .tar and put in the PDA slot.
rotohammer's post details which device matches up with which filename, in this case what we want to do is name the /dev/block/stl3 backup efs.rfs, and add it to a tar file (efs.tar) then flash it.
Assuming you have adb installed, and the stl3.bin file in the current folder:
adb push stl3.bin /sdcard/efs.rfs
adb shell
$ su
#
# cd /sdcard
# tar -cf efs.tar efs.rfs
# exit
$ exit
adb pull /sdcard/efs.tar
Now, get into download mode, open odin, stick efs.tar in PDA slot, and press start. Bam! EFS fixed
Note that in normal conditions you won't need a backup this extreme (copies of the files inside will be ok) but i've seen a number of users who have gotten their phones into this state (and did it myself during testing!) - This works with all the partitions you back up with dd that have support in your .pit file.
I've also used this to make an odin backup of my ROM, and flash it back later. This way you can have a pre-lagfixed ROM, for example
Dedicated to cerjam
Click to expand...
Click to collapse
If I could Ill kiss you! Thank you it really did the trick!

[guide] backup and restore efs partitions

Hi Folks!
It is a simple guide to backup and restore efs and others partitions in your device, i use to backup IMEI and avoid " emergency calls only ".
Requirements:
Terminal Emulator
EFS Professional Backup - thanks a lot @lyriquidperfection for the great program!
BusyBox
Drivers update
USB Debugging ON
Root
Guide (BACKUP):
Open EFS Professional Backup and wait to check some requirements, then go to Backup tab;
In "Devices Filters" select 'All partitions';
In "Devices Partitions" choose: modem, efs, modemst1, modemst2, fsg, fsc, backup, dbi, ddr and pad [modemst1 and modemst2 for dual sim devices];
Then press backup button and save this file .
Guide (RESTORE):
To restore just find file in "Backup Archives" and press restore button.
Method 2 thanks for @jackeagle:
Open terminal emulator and write: su
Allow root permission if asked
Write this: dd if=/dev/block/mmcblk0p11 of=/sdcard/efs.img bs=4096
Look at your internal storage for efs.img (14 mb)
If saved your device don't forgot press thanks button

Hy, has maybe anyone a EFS file for a S5 mini duos? I would be very happy... tnx

zippyzippy said:
Hy, has maybe anyone a EFS file for a S5 mini duos? I would be very happy... tnx
Click to expand...
Click to collapse
Do not use other Device EFS Partition .. IMEI is unique for every device and every device which is manufactured will be given different IMEI no hence you cannot use any other device IMEI its against the law... if you have not done backup of efs partition then you may have to take your device to your Samsung Service Center and they will repair it for you ..

Each device has unique efs, then make backup by yourself

heloo , my problem
In "Devices Partitions" choose: modem, efs, modemst1, modemst2, fsg, fsc, backup, dbi, ddr and pad [modemst1 and modemst2 for dual sim devices];
My phone has only this item :
bota0
bota1
efs
m9kefs1
m9kefs2
m9kefs3
carrier
param
boot
recovery
ota
cdma-radio
tombstones
tdata
persdata
reserved2
system
cach
hidden
userdata
Where I have a problem ?
I do not see why modem, efs, modemst1, modemst2, fsg, fsc, backup, dbi, ddr and pad ?
thx you for your help

[GUIDE/INVESTIGATION] Back up your EFS

TL;DR ... please skip to the bottom for a step-by-step how-to.
It is still a bit of a mystery on how easy it is for someone to lose their EFS data (including baseband/IMEI). It has happened a few times (judging by the forum activity). Even for more reason, especially since this data cannot be replaced without warranty work, it is always best to protect yourself.
So I took the task of backing up all my partitions (some through TWRP, others through shell/dd), and then pulling the dd'd partitions to my PC. Best practice is to back up everything...there may be something else lost that you may need in the future.
My old theory (based on grep'ping the images) targeted p16 and p18. According to /dev/block/by-name, mmcblk0p16 translates to the APD partition (which is related to the demo program), and mmcblk0p18 the system partition ...
Code:
lrwxrwxrwx root root 2015-07-07 16:40 ADF -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2015-07-07 16:40 APD -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2015-07-07 16:40 boot -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2015-07-07 16:40 boot-one-shot -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2015-07-07 16:40 cache -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2015-07-07 16:40 config -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2015-07-07 16:40 data -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2015-07-07 16:40 factory -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2015-07-07 16:40 fastboot -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2015-07-07 16:40 misc -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2015-07-07 16:40 panic -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2015-07-07 16:40 persistent -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2015-07-07 16:40 ramdump -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2015-07-07 16:40 recovery -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2015-07-07 16:40 reserved -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2015-07-07 16:40 silentlake -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2015-07-07 16:40 splashscreen -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2015-07-07 16:40 system -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2015-07-07 16:40 userkeystore -> /dev/block/mmcblk0p8
...however, the location within system is elusive (no common files between the search terms, except "/system/usr/srec/en-US/hmm_symbols", which doesn't seem to count)...
...please note, I have redacted my IMEI segments for protection.
Code:
[email protected]:~/Build/ArchiKitchen-master/PROJECT_070815_181336$ grep -c -r -a abcd * | grep -v :0
system/lib/arm/libcrypto.so:1
system/lib/libstagefright.so:1
system/lib/libcrypto.so:1
system/tts/lang_pico/en-GB_kh0_sg.bin:1
system/tts/lang_pico/es-ES_zl0_sg.bin:1
system/app/ASUSBrowser/ASUSBrowser.apk:2
system/app/LiveWallpapers/LiveWallpapers.apk:1
system/priv-app/GmsCore/lib/x86/libsslwrapper_jni.so:1
system/priv-app/FileManager2/x86/FileManager2.odex:1
system/priv-app/AsusZenUIServices/x86/AsusZenUIServices.odex:1
system/usr/icu/icudt53l.dat:1
system/usr/srec/en-US/hmm_symbols:1
system/usr/xt9/databases/ldb/ZHsbUNps_GB18030_xt9_big.ldb:1
system/bin/wpa_supplicant:1
system/bin/hostapd:1
[email protected]:~/Build/ArchiKitchen-master/PROJECT_070815_181336$ grep -c -r -a efgh * | grep -v :0
system/etc/security/cacerts/ccc52f49.0:1
system/etc/catalog/V1_7260/audiocomms_config/parameter-framework/Settings/Audio/AudioConfigurableDomains.xml:35
system/etc/catalog/V1_DSDA/audiocomms_config/parameter-framework/Settings/Audio/AudioConfigurableDomains.xml:29
system/framework/x86/boot.oat:1
system/usr/srec/en-US/hmm_symbols:1
system/usr/xt9/databases/ldb/ENubUN_xt9.ldb:1
system/usr/xt9/databases/ldb/ESusUN_xt9.ldb:1
system/vendor/lib/libWVStreamControlAPI_L1.so:1
[email protected]:~/Build/ArchiKitchen-master/PROJECT_070815_181336$ grep -c -r -a ijkl * | grep -v :0
system/etc/security/cacerts/d16a5865.0:2
system/tts/lang_pico/en-GB_kh0_sg.bin:1
system/app/MYuppyHK_Medium/MYuppyHK_Medium.apk:6
system/app/YouTube/YouTube.apk:1
system/app/Newsstand/x86/Newsstand.odex:1
system/usr/srec/en-US/hmm_symbols:1
system/usr/xt9/databases/ldb/ITusUN_xt9.ldb:1
[email protected]:~/Build/ArchiKitchen-master/PROJECT_070815_181336$
Just recently, user noviardi did a real world test with two devices...one with a working baseband, the other with a borked EFS. Noviardi managed to get device number two working by cloning p14 (also known as the config partition). Please note there are consequences, that with this solution, only one device can be "online" at a time, or the functioning IMEI will get blacklisted (then neither devices will have cell access). Which is the least of the problems. Hence, why I do not share my EFS data (neither should anyone else), or even snippets.
So, if you want to back up your EFS for personal resuce, your best shot is to back up the mmcblk0p14 / Config partition. But if you are paranoid (like me ), might as well back up everything.
Here's how to do it:
Connect the device to your PC
Turn on USB debugging (if not already)
From your PC, fire up a terminal/command prompt
Type "adb shell" (without the quotes - may need to add "sudo" to the front depending on your situation)
Run these commands:
Code:
su
dd if=/dev/block/mmcblk0p14 of=/storage/MicroSD/mmcblk0p14.img
Repeat the last line for any other partitions to back up (changing both numbers)
Type "exit", press enter (and repeat to close adb shell)
Run the following command:
Code:
adb pull /storage/MicroSD/mmcblk0p14.img .
Repeat for any other partitions to copy to your PC
Close out terminal, unplug USB cable.
Also, there is at least one version of TWRP (TheSSJ's release) that will back up your Config partition for you, as Config is also responsible for connectivity issues (not related to IMEI) switching between ROM's.
Hope this helps on how to protect your IMEI, with a big thanks to noviardi.

Mines showing that too..emei of abcdefgh........and not number sometimes...its weird.

pato2015 said:
Mines showing that too..emei of abcdefgh........and not number sometimes...its weird.
Click to expand...
Click to collapse
I clarified my text above.
I masked my IMEI (with abcd...) in the code boxes as I did not want even part of my IMEI known (for personal security reasons). My actual terminal I used the numbers in groups of four obtained from dialing *#06#.
If you are getting letters after dialing *#06#, I must ask - can you dial out? Did you do any modifications to the phone since you got it (e.g. root, unlock bootloader, etc)?

joel.maxuel said:
I clarified my text above.
I masked my IMEI (with abcd...) in the code boxes as I did not want even part of my IMEI known (for personal security reasons). My actual terminal I used the numbers in groups of four obtained from dialing *#06#.
If you are getting letters after dialing *#06#, I must ask - can you dial out? Did you do any modifications to the phone since you got it (e.g. root, unlock bootloader, etc)?
Click to expand...
Click to collapse
Im still on stock due , i join the asus beta program on going ....change imei only appears abcd change imei only appears during when im on recovery mode...when pound number sign asterisk it imei appears the original imei on my side.

pato2015 said:
Im still on stock due , i join the asus beta program on going ....change imei only appears abcd change imei only appears during when im on recovery mode...when pound number sign asterisk it imei appears the original imei on my side.
Click to expand...
Click to collapse
Doesn't sound corrupted then, just boatloader is being protective.
Or at worst, bug in boatloader.
Sent from my ASUS ZenFone 2

I haven't heard of any easier way or any potential issues, but as always, better safe than sorry with this stuff .

Hi,
I tried to copy the blocks from a terminal emulator on the device itself, and it took a long time and I cancelled it. How big are the blocks, and how long should the copy take?

BobboVilla said:
Hi,
I tried to copy the blocks from a terminal emulator on the device itself, and it took a long time and I cancelled it. How big are the blocks, and how long should the copy take?
Click to expand...
Click to collapse
mmcblk0p16 is about 300MB, so will take a couple minutes (one to dd it, the other to adb pull it). mmcblk0p18 (which I don't think carries EFS as I was able to grep the individual files in the system partition and no common files came up) is ~2.3GB and will (probably) take over 10 minutes.
Also, my procedure above assumes you have a MicroSD card inserted. Don't know the outcome if one ran the commands without one (probably an out of space error).

joel.maxuel said:
mmcblk0p16 is about 300MB, so will take a couple minutes (one to dd it, the other to adb pull it). mmcblk0p18 (which I don't think carries EFS as I was able to grep the individual files in the system partition and no common files came up) is ~2.3GB and will (probably) take over 10 minutes.
Also, my procedure above assumes you have a MicroSD card inserted. Don't know the outcome if one ran the commands without one (probably an out of space error).
Click to expand...
Click to collapse
Thanks. Although I'm not an android developer, I am a programmer, so I can understand code/scripting, and I realized that the command assumed I had an SD card .
I'll do it again and this time let it finish .

mmmm i tried this procedure (also used for oneplus one) and works well.
Type "adb shell" (without the quotes - may need to add "sudo" to the front depending on your situation)
Run these commands for backup efs:
su
dd if=/dev/block/mmcblk0p10 of=/sdcard/modemst1.bin bs=512
dd if=/dev/block/mmcblk0p11 of=/sdcard/modemst2.bin bs=512
Modemst1.bin and Modemst2.bin are saved in internal storage
for restore use fastboot
fastboot flash modemst1 modemst1.bin
fastboot flash modemst2 modemst2.bin
Bye.

fosseperme said:
mmmm i tried this procedure (also used for oneplus one) and works well.
Type "adb shell" (without the quotes - may need to add "sudo" to the front depending on your situation)
Run these commands for backup efs:
su
dd if=/dev/block/mmcblk0p10 of=/sdcard/modemst1.bin bs=512
dd if=/dev/block/mmcblk0p11 of=/sdcard/modemst2.bin bs=512
Modemst1.bin and Modemst2.bin are saved in internal storage
for restore use fastboot
fastboot flash modemst1 modemst1.bin
fastboot flash modemst2 modemst2.bin
Bye.
Click to expand...
Click to collapse
Keep in mind that procedure backs up "reserved" and "panic" for this device, as this one does not have modemst1/2 partitions.
It is still a hunting match.
Sent from my ASUS_Z00AD

if I could get a copy of mmcblk0p16 ? whether it is contained individual device's IMEI number ?

omgwtf19924 said:
if I could get a copy of mmcblk0p16 ? whether it is contained individual device's IMEI number ?
Click to expand...
Click to collapse
I wouldn't recommend that. Because it is the phone's unique identity like someone's fingerprints, services like cell providers will have difficulty distinguishing one from the other, and I think the policy in that case is to shut both devices down (blacklist the IMEI). So now, you would have two unusable devices.
I got your PM also, reconstructing that partition (that is your EFS) is a taboo topic, mostly because it is illegal in many countries. I wouldn't recommend that either.
Best course of action is servicing. Even if you voided your warranty, ASUS won't say no, it's just be prepared to pay (more). Of course, in this case you could pretend the warranty is still good, go back to unrooted stock, and play unaware...
Just curious, how did you hurt your IMEI? Just to see if there is a pattern of events that can cause that (and ultimately be prevented for someone else).

This happened so that, for some time I could not enter into a standard recovery, update your phone through the built-in program ended in failure, and at the entrance to recovery tried to update the phone and soon jumped mistake. Restore factory settings did not help, full unroot nothing distance, upload the new system did not help ... at the end I installed a temporary CWM used for root and reformatted /factory , /config, /cache, /ADP, /ADF and probably in one of them sat a match for IMEI ... oh well, I contacted ASUS service center and wait for a response. Currently, it is not detected SIM1 and SIM2 work and logs on to the network, both have the same IMEI and should have separate.
EDIT: Phone service reported to ASUS, after returning once the makings copies of files on the future ...

efs problem....help
i lost my asus zenfone 2 ze550ml's efs file so its showing only one dummy imei number,
But i have system backup which i took using temporary recovery
tell me if there is a way to recover efs from system backup?
thanks.
i havnt unlocked bootloader yet!

psurve01 said:
i lost my asus zenfone 2 ze550ml's efs file so its showing only one dummy imei number,
But i have system backup which i took using temporary recovery
tell me if there is a way to recover efs from system backup?
thanks.
i havnt unlocked bootloader yet!
Click to expand...
Click to collapse
I'm pretty sure it's the APD (mmcblk0p16) partition at this point.
You can try to restore system, I just don't think it would be fruitful.
Always curious with this sort of thing, what (do you think) happened that you lost your EFS?

The actual partition that keep imei is on mmcblk0p14 named Config
i got 2 phone with one dead baseband chip to tried out.
the mmcblk0p16 that you mention doesn't contain imei at all..
best luck

noviardi said:
The actual partition that keep imei is on mmcblk0p14 named Config
i got 2 phone with one dead baseband chip to tried out.
the mmcblk0p16 that you mention doesn't contain imei at all..
best luck
Click to expand...
Click to collapse
I was considering this one a while back. There was just no search matches to back that theory up.
If you have successfully revived one EFS with the partition (#14) from the other device, that not only makes sense with the problems I have had with config in the past, also means we have something more solid to go by than just block searches.
Will update in a little bit, with attribution. Thanks!

OfficerJimLahey said:
I was considering this one a while back. There was just no search matches to back that theory up.
If you have successfully revived one EFS with the partition (#14) from the other device, that not only makes sense with the problems I have had with config in the past, also means we have something more solid to go by than just block searches.
Will update in a little bit, with attribution. Thanks!
Click to expand...
Click to collapse
yes sir.
as we now confirmed that the imei is containing in the #14..
let hope some expert will extract the importance imei from that 64mb partition..
the backup command should be
adb shell
su
dd if=/dev/block/mmcblk0p14 of=/storage/MicroSD/mmcblk0p14.img
and restore whole 14 partition from the adb shell
with this command
adb shell
su
dd if=/storage/MicroSD/mmcblk0p14.img of=/dev/block/mmcblk0p14

Recently I tried to root the phone and successfully did it via CWM Temporary Recovery.
I used Exposed Framework, Intelli3G module, greenify etc. My phone was running well except I needed to turn flight mode on and off each time after booting or restarting my phone to get network on sim 1. But it was going well until one day when there was a new OTA update available. I just had forgotten the issue of OTA update on a rooted device.
After updating my rooted device it went into bootlops. I am not so geeky so I was looking for a solution. Then I restored a previous NANDROID backup via CWM but the it was showing error after restoration when the device rebooted.
So then again I went to CWM recovery mode and FORMATTED ALL THE PARTITIONS INCLUDING EFSthen I flashed some downgraded recovery.img, droidboot.img etc and updated my phone with the lattest official stock firmware via CWM
I was lucky to unbrick my phone as it started well
But then the real problem started
THERE'S NO NETWORK ON SIM 1
I reflashed my phone but it was same then I took it to a servicing store they said I have IMEI problem in my phone, the phone is now in the servicing shop,
Isn't there any way to restore my imei???
How about Zenfone Rescue tool kit(by Aztech)??

[needed]persist backup of moto g5 plus which is not bricked yet

Hey guys as you know that we are able to get back volte successfully in Moto g5 plus by restoring PERSIST BACKUP.
So I think MAYBE persist partition got corrupted during flashing back stock.
But that backup is from MOTO G4 PLUS ,and some user facing a problem that whenever they reboot volte and imei again gone,and Everytime they have to restore efs (maybe because of that persist partition)so I am requesting you ,can someone please pull out persist backup of STOCK MOTO G5 PLUS WITH WORKING VOLTE (OR G5 PLUS WHICH IS NOT BRICKED YET).
I AM ATTACHING A TWRP FOR TAKING BACKUP WHICH IS MADE BY DEVELOPER.
SO YOU HAVE TO JUST GO IN TO BACKUP AND TAKE BACKUP OF PERSIST PARTITION
You can download twrp from below link.
https://potterroms.ddns.net/TWRP/twrp-3.2.1-1-potter_persist.img
I am not responsible for any brick/damage caused during you taking backu

Alright, so I got a Persist backup using the partition backup & restore app. I don't use VoLTE, but my IMEI hasn't become zero. I'm on Oreo. It's saved as a .img file. If this is helpful I'll upload the file. @akshu2697

thedr34m13 said:
Alright, so I got a Persist backup using the partition backup & restore app. I don't use VoLTE, but my IMEI hasn't become zero. I'm on Oreo. It's saved as a .img file. If this is helpful I'll upload the file. @akshu2697
Click to expand...
Click to collapse
I would definitely love to give it a go. I've had to restore my EFS every reboot since I tried installing Pixel Experience. I'd love to not have to remember anymore!
telegram @bcraw

thedr34m13 said:
Alright, so I got a Persist backup using the partition backup & restore app. I don't use VoLTE, but my IMEI hasn't become zero. I'm on Oreo. It's saved as a .img file. If this is helpful I'll upload the file. @akshu2697
Click to expand...
Click to collapse
Yes,it will be helpful,can you please upload that file.?

akshu2697 said:
Yes,it will be helpful,can you please upload that file.?
Click to expand...
Click to collapse
There you go.

thedr34m13 said:
There you go.
Click to expand...
Click to collapse
i will try ,
thank you so much brother

akshu2697 said:
i will try ,
thank you so much brother
Click to expand...
Click to collapse
No problem. Happy to help. If there's a way to get a better backup, tell me and I'll try.

thedr34m13 said:
No problem. Happy to help. If there's a way to get a better backup, tell me and I'll try.
Click to expand...
Click to collapse
sorry brother ,
i tried your backup,but this backup isn't working,
we need twrp persist backup as i have posted on the thread of volte.

akshu2697 said:
sorry brother ,
i tried your backup,but this backup isn't working,
we need twrp persist backup as i have posted on the thread of volte.
Click to expand...
Click to collapse
Not sure how to backup persist in twrp. Couldn't find instructions anywhere. If you find instructions, tell me and I'll upload the backup.

thedr34m13 said:
Not sure how to backup persist in twrp. Couldn't find instructions anywhere. If you find instructions, tell me and I'll upload the backup.
Click to expand...
Click to collapse
sure,i'll do

DELETED

With a lot of research, I was able to dump the persist partition using adb. My dump will do no good, as I have only been able to get persist back by OP's method. We need someone to dump who has not flashed an oreo rom. Ok, that being said, here is how.
Make sure your phone is rooted.
Make sure usb debugging is enabled.
Boot phone into recovery.
Open adb with phone connected to pc.
Code:
adb devices
You should see your device listed.
Code:
adb shell
You should get ~# and something like a backward arrow [6N. That was mine yours may differ. If you have ~$ instead of ~# you are not rooted properly. If you used magisk you may have to add the sudo module.
Code:
ls -al /dev/block/platform/soc/7824900.sdhci/by-name
This will give you a list of all partitions. Look through them and find one described as persist. Mine was this:
Code:
lrwxrwxrwx 1 root root 21 Jan 1970 persist -> /dev/block/mmcblk0p30
We are interested in the address /dev/block/mmcblk0p30.
We need to type in
Code:
dd if=/yourMountingPoint of=/yourDestination/partitionType
where /yourMounting point is the persist address, if like mine /dev/block/mmcblk0p30. /your destination will be where you want to save it, and partition type should be persist.img.
My command was this
Code:
dd if=/dev/block/mmcblk0p30 of=/external_sd/persist.img
This will give us a proper persist .img file.

Here it is.
I clean flash stock rom (potter_NPNS25.137-93-4) before getting the persist file, was on crDroid 7.1 before. I don't know if volte is working because we don't have it on my country, but I never flashed Oreo before and never lost imei or 4g/lte, so it should be fine.
Hope it helps us and use at your own risk.
https://drive.google.com/drive/folders/1bqdxheka3jKG76AXdEExIdhG81D3agLM

[email protected] said:
With a lot of research, I was able to dump the persist partition using adb. My dump will do no good, as I have only been able to get persist back by OP's method. We need someone to dump who has not flashed an oreo rom. Ok, that being said, here is how.
Make sure your phone is rooted.
Make sure usb debugging is enabled.
Boot phone into recovery.
Open adb with phone connected to pc.
Code:
adb devices
You should see your device listed.
Code:
adb shell
You should get ~# and something like a backward arrow [6N. That was mine yours may differ. If you have ~$ instead of ~# you are not rooted properly. If you used magisk you may have to add the sudo module.
Code:
ls -al /dev/block/platform/soc/7824900.sdhci/by-name
This will give you a list of all partitions. Look through them and find one described as persist. Mine was this:
Code:
lrwxrwxrwx 1 root root 21 Jan 1970 persist -> /dev/block/mmcblk0p30
We are interested in the address /dev/block/mmcblk0p30.
We need to type in
Code:
dd if=/yourMountingPoint of=/yourDestination/partitionType
where /yourMounting point is the persist address, if like mine /dev/block/mmcblk0p30. /your destination will be where you want to save it, and partition type should be persist.img.
My command was this
Code:
dd if=/dev/block/mmcblk0p30 of=/external_sd/persist.img
This will give us a proper persist .img file.
Click to expand...
Click to collapse
How to restore this file brother.?

N1vBruno said:
Here it is.
I clean flash stock rom (potter_NPNS25.137-93-4) before getting the persist file, was on crDroid 7.1 before. I don't know if volte is working because we don't have it on my country, but I never flashed Oreo before and never lost imei or 4g/lte, so it shoud be fine.
Hope it helps us and use at your own risk.
https://drive.google.com/drive/folders/1bqdxheka3jKG76AXdEExIdhG81D3agLM
Click to expand...
Click to collapse
Thank you sooo much brother.
Thank you for your support.

akshu2697 said:
How to restore this file brother.?
Click to expand...
Click to collapse
Aren't you the OP of this? I thought you needed a way to dump the original partitions, and I provided the method with step by step to do so. I've never coded for android systems, but I'm very familiar with close cousin linux, so I suppose I could investigate and learn. However I would think whomever developed the G4 plus method could use the above dump for our phone. I guess I assumed it was you who discovered this method. I'll dig into it further when I get some time, but getting the clean persist dump was what was asked to do.

I was able to write the above persist.img file by:
1. transfer persist.img to my external_sd
2. booting into twrp
3. opening terminal
4. entering
Code:
dd if=/external_sd/persist.img of=/dev/block/mmcblk0p30
However, this placed my EMEI to 0, and I had to restore my saved efs with moto g4 + persist to get signal back. But remember, I had problem with efs every time I reboot, so my case may not be typical of those of you whose moto g4+ persist was working fine for. I would be curious if N1vBruno's persist was at the same address as mine, namely
Code:
/dev/block/mmcblk0p30

Guys who have restored their VoLTE, does your IMEI match the one that came with your phone or has it changed to something else?
I'm just being curious as I thought using someone else's persist backup would restore his IMEI to your phone, or was it efs?
Please correct me if I'm wrong.

psychopac said:
Guys who have restored their VoLTE, does your IMEI match the one that came with your phone or has it changed to something else?
I'm just being curious as I thought using someone else's persist backup would restore his IMEI to your phone, or was it efs?
Please correct me if I'm wrong.
Click to expand...
Click to collapse
It is efs.

[email protected] said:
I would be curious if N1vBruno's persist was at the same address as mine, namely
Code:
/dev/block/mmcblk0p30
Click to expand...
Click to collapse
Yes,
Code:
persist -> /dev/block/mmcblk0p30
psychopac said:
I'm just being curious as I thought using someone else's persist backup would restore his IMEI to your phone, or was it efs?
Click to expand...
Click to collapse
I hope not lol

Restore Persist.img

After a failed update and some flashing my 4G Connection is gone (sim is locked, no baseband).
Howeever I made a backup of persist.img, modemst1.img and modemst2.img months ago.
Couldn't figure out so far how to restore the files, could someone tell me how to do?

Code:
dd if=/path/to/persist.img*modemst1.img of=/path/to/persist*modemst1-partition

Thanx for the reply, so do I need to do this step 3 Times for all 3 Files?
dd if=/path/to/persist.img*modemst1.img of=/path/to/persist*modemst1-partition
would that mean then for modemst2:
dd if=/path/to/persist.img*modemst2.img of=/path/to/persist*modemst2-partition ???
Do I need another command for the persist.img too?
Sorry for asking, but I don't wanna mess up even more with my persist file.

How did you backup these partitions?
A .img file is a bit to bit copy of a partition or a drive.
Are you sure you have a backup ending with .img? That's very important for the way you restore your backup!!
If you have .img backups then you will restore them like this:
First copy your .img files to /sdcard (internal storage).
persist.img:
Code:
dd if=/sdcard/persist.img of=/dev/block/by-name/persist
modemst1.img
Code:
dd if=/sdcard/modemst1.img of=/dev/block/by-name/modemst1
modemst2.img
Code:
dd if=/sdcard/modemst2.img of=/dev/block/by-name/modemst2
Restart your device!

Thanx for the reply,
My files are definately .img files, I backed them up months ago when starting with the Custom Rom Stuff, too be (hopefully) save.
Backed them up with this 3 commands
dd if=/dev/block/mmcblk0p2 of=/sdcard/modemst1.img
dd if=/dev/block/mmcblk0p3 of=/sdcard/modemst2.img
dd if=/dev/block/mmcblk0p4 of=/sdcard/persist.img
Was long ago so I couldn't remember exactly everything in Detail.
One Question left, setting the Commands while in Bootloader, TWRP or normal in system?

Dave-C said:
Thanx for the reply,
My files are definately .img files, I backed them up months ago when starting with the Custom Rom Stuff, too be (hopefully) save.
Backed them up with this 3 commands
dd if=/dev/block/mmcblk0p2 of=/sdcard/modemst1.img
dd if=/dev/block/mmcblk0p3 of=/sdcard/modemst2.img
dd if=/dev/block/mmcblk0p4 of=/sdcard/persist.img
Was long ago so I couldn't remember exactly everything in Detail.
One Question left, setting the Commands while in Bootloader, TWRP or normal in system?
Click to expand...
Click to collapse
Are you sure you backed up mmcblk0p2/3/4?? Because these partitions are definitively not the persist or modemst ones! If you execute the commands above you will override your partitions with the wrong data!!

WoKoschekk said:
Are you sure you backed up mmcblk0p2/3/4?? Because these partitions are definitively not the persist or modemst ones! If you execute the commands above you will override your partitions with the wrong data!!
Click to expand...
Click to collapse
Yes backed up with these 3 Commands, found them somewhere in this board.
Had these commands saved on my PC, so definately used them but probably good that I didn't used them yet.
Howeever, I also have a TWRP Backup with EFS and persist files (efs1.emmc.win, efs2emmc.win, persist.ext4.win).
How could I use them, simply via TWRP or better way to do this?

Can't Believe it....
After lots of flashing (Back to Stock etc.) I got my 3G/4G/Baseband Connections back!
Could you tell me the right Commands to backup the Persist/EFS/Modem Parts?
Anyways thank you so much for patiently helping me through this.
Thanx!

Use the TWRP backups. They're perfect!

Did the TWRP Backups now.
In case you know the commands for the img output, i'd still like to know.
I'd like an independent solution, since I had two TWRP Backups each with the EFS/Partition Backup, while 1 of them was somehow not working (error output).
So i'd like to be as secure as possible.

You need the dd command to create an image of each partition. The partitions on your device are numbered consecutively:
persist= /dev/block/mmcblk0p38
modemst1= /dev/block/mmcblk0p34
modemst2= /dev/block/mmcblk0p35
Open a terminal app and type:
for persist:
Code:
dd if=/dev/block/[B]mmcblk0p38[/B] of=/sdcard/persist.img
if= input file (partition)
of= output file (.img backup)

Hello, I am having the same problem but only with a backup with no IMEI. Does anyone know how to solve this? Or to merge these two backups to form one with IMEI and stable signal. The backups are encrypted I guess because nothing makes sense in them

juampapo546 said:
Hello, I am having the same problem but only with a backup with no IMEI. Does anyone know how to solve this? Or to merge these two backups to form one with IMEI and stable signal. The backups are encrypted I guess because nothing makes sense in them
Click to expand...
Click to collapse
What kind of backup do you have?? What is a backup with no IMEI?

WoKoschekk said:
What kind of backup do you have?? What is a backup with no IMEI?
Click to expand...
Click to collapse
TWRP backup of persist and efs
When I made the backup I had no IMEI but the wifi was working (I actuall made the backup after the signal drop issue)

juampapo546 said:
TWRP backup of persist and efs
When I made the backup I had no IMEI but the wifi was working (I actuall made the backup after the signal drop issue)
Click to expand...
Click to collapse
If you don't have a backup of /persist with a IMEI then you won't be able to restore it.
https://forum.xda-developers.com/g5-plus/how-to/fix-persist-resolve-imei0-explanation-t3825147

WoKoschekk said:
If you don't have a backup of /persist with a IMEI then you won't be able to restore it.
https://forum.xda-developers.com/g5-plus/how-to/fix-persist-resolve-imei0-explanation-t3825147
Click to expand...
Click to collapse
But isn't there a way to edit the backup or merge both backups I have?
(However when I erase modemst1 and 2 IMEI comes back but with the signal drop, a fix for that would also help me)

For the right understanding:
You have two different TWRP backups for /persist and /efs. The first one restores IMEI but signal is lost and the other one restores your signal without IMEI??

WoKoschekk said:
For the right understanding:
You have two different TWRP backups for /persist and /efs. The first one restores IMEI but signal is lost and the other one restores your signal without IMEI??
Click to expand...
Click to collapse
I am so sorry I answered this late, yes that is correct and I have been using my phone with WiFi only for months now

Try to merge them manually if you know the corresponding files. I've no idea how to figure them out...
TWRP won't merge your backups.