Hey. Can anybody tell me the difference between those two ? I know it's recommended to backup them before os migration. I read that both of them stores information about imei, mac etc. Do I need both of them to safely migrate to new os'es?
The short of it is that your Persist holds the key files needed to create your IMEI, and it is used to construct your EFS. EFS effectively works as a cache. If you wipe EFS, then as long as you have an intact Persist, your EFS will be reconstructed, and you will keep your IMEI.
Credits to this thread for working out the relationship between Persist and IMEI (it is talking about the investigation into how to restore IMEI when it is 0 after flashing Oreo custom roms):
https://forum.xda-developers.com/g5-plus/how-to/dev-fixing-baseband-t3806064
Even though it is for potter (G5 Plus), it still applies to Sanders.
doubt
NZedPred said:
The short of it is that your Persist holds the key files needed to create your IMEI, and it is used to construct your EFS. EFS effectively works as a cache. If you wipe EFS, then as long as you have an intact Persist, your EFS will be reconstructed, and you will keep your IMEI.
Credits to this thread for working out the relationship between Persist and IMEI (it is talking about the investigation into how to restore IMEI when it is 0 after flashing Oreo custom roms):
https://forum.xda-developers.com/g5-plus/how-to/dev-fixing-baseband-t3806064
Even though it is for potter (G5 Plus), it still applies to Sanders.
Click to expand...
Click to collapse
if i have someone else persist the imei not reconstructing with their value why...??
they are keeping some values somewhere else ...
5P4RT0N said:
if i have someone else persist the imei not reconstructing with their value why...??
they are keeping some values somewhere else ...
Click to expand...
Click to collapse
The files that store the information, dhob.bin,etc, are encrypted and can only be decrypted by the device they were made for.
So my question is : Persist is just a 2nd safety measure, which can help if we loose EF? So can I do those backups from custom softs and there will be no difference if i did it from official soft? My imei's are not lost.
Edit 1
I backed up persist with TWRP from this topic https://forum.xda-developers.com/moto-g5s-plus/help/how-to-persist-partion-moto-g5s-t3830442
How do I know if its allright ?
osemoka said:
So my question is : Persist is just a 2nd safety measure, which can help if we loose EF? So can I do those backups from custom softs and there will be no difference if i did it from official soft? My imei's are not lost.
Click to expand...
Click to collapse
There's a little bit more to it than that. OTAs normally wipe the EFS on install, so it's not that persist is a safety measure, it is the primary means of getting your IMEI. Additionally, there are certain folders that are used when using things like 4G, Volte, etc. A number of other things get stored there, such as files for widevine (DRM), calibration for sensors, etc. That's why it is so important.
osemoka said:
Edit 1
I backed up persist with TWRP from this topic https://forum.xda-developers.com/moto-g5s-plus/help/how-to-persist-partion-moto-g5s-t3830442
How do I know if its allright ?
Click to expand...
Click to collapse
I can't tell what that specific version of TWRP does to backup persist, but if it's done as an image it will be about 32MB, or if it's done as 'files only' it will be around 3-400KB.
Related
My Mobile is I-9000, I installed an Arabic version JPJPM 2.2.1 on Uk version and mobile restart normally with IMIE & Phone version readable after I closed and restarted the mobile not recognized the phone version and IMIE and give unknown.
I make a recover using the three bottoms and restart the mobile reads Phone Version and IMIE No. and when close and start the mobile back to give phone version and IMIE unknown.
In some forums give the solution to check clear EFS and boot loader update like you see or Download EZbase and flash
I am afraid to do that, please tell me the solution
Read the post .
http://forum.xda-developers.com/showthread.php?t=881162
jje
Reading
I hope to find the solution there
Not working
Please help
Where are the experienced people to tell the right solution to follow
check clear EFS & boot loader and upgrade or Only check EFS
Please help
You can find imei under the battery.
ayman_salah said:
Where are the experienced people to tell the right solution to follow
check clear EFS & boot loader and upgrade or Only check EFS
Please help
Click to expand...
Click to collapse
I am not 100 percent sure, but I see no reason to mess with the bootloaders. Flash the new ROM with Clear EFS checked, and I THINK it will restore your IMEI. It has done so with others.
At this point, you have nothing to lose by trying.
do not clear your efs without making a backup of your efs first.
Just flash the rom from your carrier (www.samfirmware.com) that the phone came with, and you should have proper iemi.
fooman123 said:
do not clear your efs without making a backup of your efs first.
Click to expand...
Click to collapse
His efs is already fragged...so silly to back it up. He is trying to restore it.
Don't clear your EFS. You might still have the backup files in there. If you open your efs in root explorer or an adb shell and have .bak files you need to delete the nv_data.bin and nv_data.bin.md5 files, reboot the phone and it should recreate the files from the backups.
Flash CM7. It's been reported to regenerate IMEI, but ONLY if you keep on using CM7 or MIUI. Any attempt to go back to stock will remove the IMEI.
It does not sound like is efs is totally fragged from his original post. Backing up /efs is easy -- after clearing efs there is no way to regenerate the nv_data.bin (that I know of) without a backup.
rschenck said:
I am not 100 percent sure, but I see no reason to mess with the bootloaders. Flash the new ROM with Clear EFS checked, and I THINK it will restore your IMEI. It has done so with others.
At this point, you have nothing to lose by trying.
Click to expand...
Click to collapse
I will try to do that as you said above "It has done so with others"
Wish me luck
ayman_salah said:
I will try to do that as you said above "It has done so with others"
Wish me luck
Click to expand...
Click to collapse
Good luck, though the consensus of I am sure smarter types than I seems to be that you should take a copy of your efs folder before doing anything...and that seems wise to me, just in case.
I have managed to corrupt the /efs on two i9000 handsets. A ROM I installed used a base that had a bug in it that caused this. I do not have a backup of the data that was in /efs
The phone reports the dummy IMEI number 004999010640000 in the settings menu.
Every guide I've found basically says "This is how to recover using your backup". I have been unable to find any information regarding recovery of the data if you do not have a backup.
Is it really the case that if you lose your efs data, there is no way to recover the hardware? That seems very strange to me.
Some clarity on this matter would be great.
Thanks,
- Naz.
mrnaz said:
Some clarity on this matter would be great. .
Click to expand...
Click to collapse
check out efs solutions on My Android Solutions
From what I understand the EFS contains some device specific information? Here is a blurb I read:
"But What is EFS?
Now that I have your attention about EFS, you might be curious to know what is EFS? EFS is a System Directory, that contains some important information about IMEI, Wireless MAC Address, baseband version, Product Code, System ID and NV Data. Usually your EFS data remain safe no matter what happens, but its corruption occurs when you try to install any Custom ROM and Got this error."
So if we share a TWRP back up that includes EFS and someone else restores that EFS, what will be the out come? Possible wrong IMEI, mac address, no connection?
It's a bad as crossing the streams- total protonic reversal. Try to imagine all life as we know it stopping instantaneously and every molecule in your body exploding at the speed of light.
It would be bad.
_MetalHead_ said:
It's a bad as crossing the streams- total protonic reversal. Try to imagine all life as we know it stopping instantaneously and every molecule in your body exploding at the speed of light.
It would be bad.
Click to expand...
Click to collapse
I figured so. I thought I would put the question out there for more experienced people to verify. I just noticed TWRP allows me to back up my EFS stuff, and I seen someone share theirs in a twrp backup for others to flash. Looked like bad news.
drolgnir said:
I figured so. I thought I would put the question out there for more experienced people to verify. I just noticed TWRP allows me to back up my EFS stuff, and I seen someone share theirs in a twrp backup for others to flash. Looked like bad news.
Click to expand...
Click to collapse
Yeah I honestly have no idea exactly what would happen, I just know that if your EFS gets lost/corrupted you are pretty screwed, unless you have a backup. I'd imagine that flashing someone else's EFS wouldn't be the smartest thing to do.
drolgnir said:
I figured so. I thought I would put the question out there for more experienced people to verify. I just noticed TWRP allows me to back up my EFS stuff, and I seen someone share theirs in a twrp backup for others to flash. Looked like bad news.
Click to expand...
Click to collapse
Unless I'm mistaken, only Samsung devices have the EFS issue. Here's a thread on the Moto X forum acc to which the X doesn't have the EFS issue (LINK). Most likely this device doesn't either. So using another's TWRP backup wouldn't be a problem.
That would be cool if it didn't. I seen our twrp version makes a backup of a EFS partition of sorts. Your link seems to refer to the 1st gen moto x? Hopefully your right, who wants to worry about EFS corruption.
Is there any method that I can back up the device completely so that I can venture into other roms including imei in case of losing
TWRP does a full backup. It does NOT backup your user files though on the SD Card. Just make sure that after you make the full backup that you go to the SD Card and copy off the TWRP Folder to a PC or if you have a Duo Thumb drive like me, plug it in and set it as the save location when you are backing up with TWRP.
drtweak said:
TWRP does a full backup. It does NOT backup your user files though on the SD Card. Just make sure that after you make the full backup that you go to the SD Card and copy off the TWRP Folder to a PC or if you have a Duo Thumb drive like me, plug it in and set it as the save location when you are backing up with TWRP.
Click to expand...
Click to collapse
but backup twrp does not work with imei
jakson7474 said:
but backup twrp does not work with imei
Click to expand...
Click to collapse
Works
Efs backup (it's imei partition)
jakson7474 said:
but backup twrp does not work with imei
Click to expand...
Click to collapse
Ah I see these guys have the imei issue. I'm only day 3 with the G5S Plus lol. didn't have these issues with the Turbo
drtweak said:
Ah I see these guys have the imei issue. I'm only day 3 with the G5S Plus lol. didn't have these issues with the Turbo
Click to expand...
Click to collapse
They lose their imei cuz they don't know what they are doing and follow a lot of bad advice given by others that don't know what they are doing - classic case of blind leading the blind. I've run almost every rom, restored stock a couple times, never lost imei.
Phazmos said:
They lose their imei cuz they don't know what they are doing and follow a lot of bad advice given by others that don't know what they are doing - classic case of blind leading the blind. I've run almost every rom, restored stock a couple times, never lost imei.
Click to expand...
Click to collapse
Same?
Idk,why people lost them imei
Hi all, I've seen that there are a few threads in this and other forums that are saying that using a particular other persist will help restore IMEI, Volte, or other lost functionality after installing a custom Rom and reverting back to stock nougat. As this sort of suggestion has resulted in many devices being permanently broken, I'm sharing a thread I made in potter.
Fix Persist, resolve IMEI=0, Explanation, Requirements
Now, the most important thing here is to NEVER EVER flash another device's persist. Your persist contains key files that have your IMEI data (in encrypted form), and it will not work with another device (or vice versa). In the thread above, I explain what has been happening, how to detect it, what can be done to fix (note - this may differ from device to device - I recommend not applying the fix until after other who have 'fully working devices' can confirm key details, such as the "rfs" user), and why other persist files gave the appearance of working (but were actually causing permanent damage).
Also note that the fix is for stock nougat. I have already seen in the cedric devices that the upcoming Oreo may apply the same type of fix on boot (i.e. changing ownership of key folders and files).
Happy to answer any questions if people ask. Please keep questions for this device in this thread.
Is there any hope to fix IMEI 0?
Himanshu.Shukla said:
Is there any hope to fix IMEI 0?
Click to expand...
Click to collapse
It all depends on what you have or haven't done. If you flashed another persist, you're out of luck. If you haven't flashed another persist, back it up now and save it to the cloud so you never lose it. Then the principles in the guide may help. You can see if you are affected or not by following the section 1), as long as you are on a stock nougat rom.
NZedPred said:
Hi all, I've seen that there are a few threads in this and other forums that are saying that using a particular other persist will help restore IMEI, Volte, or other lost functionality after installing a custom Rom and reverting back to stock nougat. As this sort of suggestion has resulted in many devices being permanently broken, I'm sharing a thread I made in potter.
Fix Persist, resolve IMEI=0, Explanation, Requirements
Now, the most important thing here is to NEVER EVER flash another device's persist. Your persist contains key files that have your IMEI data (in encrypted form), and it will not work with another device (or vice versa). In the thread above, I explain what has been happening, how to detect it, what can be done to fix (note - this may differ from device to device - I recommend not applying the fix until after other who have 'fully working devices' can confirm key details, such as the "rfs" user), and why other persist files gave the appearance of working (but were actually causing permanent damage).
Also note that the fix is for stock nougat. I have already seen in the cedric devices that the upcoming Oreo may apply the same type of fix on boot (i.e. changing ownership of key folders and files).
Happy to answer any questions if people ask. Please keep questions for this device in this thread.
Click to expand...
Click to collapse
Dude , thank you so much for that thread and Info. Finally someone is starting to explain the root cause of this IMEI/4G/Volte mess in our devices. Unfortunately I got my phone second hand and the dude had flashed a lineage ROM on it. He had mentioned radio problems but has said he had flashed the wrong modem and fixed it. The phone was 100% operational with the Lineage ROM he had on it so I didn't think much of and I figured since I've been rooting/flashing my phones since the day I got my first android, I could deal with it anyway. In any case, I soon went to flash an 8.1 ROM and discovered my IMEI gone. Eventually I found a few 8.1 ROMs that worked and I'm completely happy with AEX 5.2 which I'm on now. I have the EFS and Persist backups as of the moment I acquired the phone. I wondering though if there is a way to tell if my persist is the one that is supposed to be there or if the owner flashed a different persist? Also when I input the terminal command from your post it returns a list of folder within persist but no ownership tags as shown in your post.
jesslegentil said:
Dude , thank you so much for that thread and Info. Finally someone is starting to explain the root cause of this IMEI/4G/Volte mess in our devices. Unfortunately I got my phone second hand and the dude had flashed a lineage ROM on it. He had mentioned radio problems but has said he had flashed the wrong modem and fixed it. The phone was 100% operational with the Lineage ROM he had on it so I didn't think much of and I figured since I've been rooting/flashing my phones since the day I got my first android, I could deal with it anyway. In any case, I soon went to flash an 8.1 ROM and discovered my IMEI gone. Eventually I found a few 8.1 ROMs that worked and I'm completely happy with AEX 5.2 which I'm on now. I have the EFS and Persist backups as of the moment I acquired the phone. I wondering though if there is a way to tell if my persist is the one that is supposed to be there or if the owner flashed a different persist? Also when I input the terminal command from your post it returns a list of folder within persist but no ownership tags as shown in your post.
Click to expand...
Click to collapse
I think the only way to tell if the persist is definitely the one for the phone is to revert to stock nougat, follow the guide (I did find that one of the posters in the thread tried it on their sanders device and it worked for them - fortunately there is enough consistency so that the guide applies to many phones) to fix the folder ownership, then erase EFS and reboot. If your IMEI comes back, you're in luck. If it doesn't, hold onto your EFS backup for the rest of your phone's life!
(Also note that reverting to stock nougat should be done carefully. Don't downgrade the bootloader, otherwise you'll run into other problems..)
Also, just to emphasize, the output from the commands that list ownership is taken from nougat. Oreo has changed things, so it's not surprising if you get different things. E.g. Cedric's Oreo appears to not have an rfs user, instead it is using something like oem_2903.
Just wanted to chime in and say that this has fixed my phone! I've had iffy VoLTE and other issues since going back to stock and couldn't even use custom ROMs since it wouldn't allow me to search for a network. This seems to have cleared it all up. Thanks!
thanks a lot. I've had no lte data since the day I got the phone, but thanks to this it is fixed.
edit: for verizon peoples who only had 3g, I can confirm that lte still works after flashing at least msm xtended so probably other roms too.
any solution to this problem, i installed this rom and now baseband is not found and imei zero
sanders-twrp-flashable-OPS28.49-2.zip
jakson7474 said:
any solution to this problem, i installed this rom and now baseband is not found and imei zero
sanders-twrp-flashable-OPS28.49-2.zip
Click to expand...
Click to collapse
Folks, the rom above was a test version of the Oreo soak test that I made. Unfortunately it seems the is an issue on the build. I have pulled it for now. Hoping that a downgrade to stock nougat will help fix it. Goodness knows I'm trying to help with the IMEI issue, not contribute to it *facepalm*
Edit: user got everything back by flashing a nougat twrp flashable build. So issue was definitely just in that particular Oreo build
Can anyone confirm if this should work on the g5s plus with those commands? It doesnt seem to for me
Nyvia said:
Can anyone confirm if this should work on the g5s plus with those commands? It doesnt seem to for me
Click to expand...
Click to collapse
I can confirm it worked on my xt1806.
Back up the EFS, run these commands, then run the fastboot commands to wipe your modem. It will rebuild and you should have imei back
Nyvia said:
Can anyone confirm if this should work on the g5s plus with those commands? It doesnt seem to for me
Click to expand...
Click to collapse
Can you check if you have a file dhob.bin.bak after running the find command in the post? Many people who don't have success with the guide are missing that file.
I have successfully executed this procedure and I got a hd calling option or an hd calling icon..is that correct??. Then I backed up the efs and again i got to custom ROM then and flashed the efs partition but no sign of volte or can't make call from Jio...
The question is can I use the efs partition which I recovered through this on a custom ROM?
subinsrk said:
I have successfully executed this procedure and I got a hd calling option or an hd calling icon..is that correct??. Then I backed up the efs and again i got to custom ROM then and flashed the efs partition but no sign of volte or can't make call from Jio...
The question is can I use the efs partition which I recovered through this on a custom ROM?
Click to expand...
Click to collapse
Answer as per the other thread:
Yes, I get an H+ icon on my phone, so that would be what you'd want if the procedure worked. If Volte doesn't work on the custom rom, then it's a custom rom issue.
my volte worked without restoring the efs... just fixed permissions from stock, flashed rom, everything worked.
xtasquee said:
my volte worked without restoring the efs... just fixed permissions from stock, flashed rom, everything worked.
Click to expand...
Click to collapse
Bro how you can fix the volte can you tell me?
just flashed stock and fixed the permissions like op said. when i rebooted everything was fixed and still works with at least gzosp-based roms and probably others too. no tricks needed.
Thank you bro...it's worked backuped the efs and persist partion on the stock ROM and again flashed pe ROM and reflashed the efs and persist volte is now working fine thanks....
is there a way to get this post pinnedor something?
Hi guys. Reported success earlier in the thread but my issues came back. IMEI is there, everything functions properly in stock, but in non-stock I get an "error searching for network" that I didn't get before I flashed a broken gapps file that edited my persist file.
I know my persist partition is currently stock, and I'd like a copy of a working persist file from an xt1806 that I can copy my known good persist data to. Thanks!