Hi! I have a problem with efs partition of a Galaxy S7 (g930f)
In practice I flashed an efs (do not ask me why) corrupted in the same partition through an app I do not remember the name. Now it does not start anymore, it goes directly to recovery with 3 same mistakes "failed to mount / efs (invalid argument)" I tried installing a 4-file stock rom, successfully flashed with Odin but the problem persists. Before doing this stupid thing I fortunately backed up the radio and efs partition, but I do not know how to restore it!
The device only goes into recovery and download mode. I also flash autoroot and supersu through TWRP recovery to launch commands with adb type "adb shell" and "su" (which do not work, probably isn't good rooted or not enabled debug mode that I can't turn it on )
Fastboot fails to recognize the device.
I tried to flash the .tar backup file via Odin (I also have it .img, unfortunately it's not possible to flash it via Twrp) placing it in AP but it returns Fail. For the rest I tried to do all the possible wipe by deleting the entire OS and reflashing the stock with Odin by activating "re-partition" and "efs clean" but without solving, always the usual error in recovery.
What do you suggest me to do?
ElPocho796 said:
Hi! I have a problem with efs partition of a Galaxy S7 (g930f)
In practice I flashed an efs (do not ask me why) corrupted in the same partition through an app I do not remember the name. Now it does not start anymore, it goes directly to recovery with 3 same mistakes "failed to mount / efs (invalid argument)" I tried installing a 4-file stock rom, successfully flashed with Odin but the problem persists. Before doing this stupid thing I fortunately backed up the radio and efs partition, but I do not know how to restore it!
The device only goes into recovery and download mode. I also flash autoroot and supersu through TWRP recovery to launch commands with adb type "adb shell" and "su" (which do not work, probably isn't good rooted or not enabled debug mode that I can't turn it on )
Fastboot fails to recognize the device.
I tried to flash the .tar backup file via Odin (I also have it .img, unfortunately it's not possible to flash it via Twrp) placing it in AP but it returns Fail. For the rest I tried to do all the possible wipe by deleting the entire OS and reflashing the stock with Odin by activating "re-partition" and "efs clean" but without solving, always the usual error in recovery.
What do you suggest me to do?
Click to expand...
Click to collapse
Hi mate
I know you said "dont ask me why" but why you flashed someone else EFS? , the only reason I can think of is to change the IMEI...........
I you have your old EFS partition backup use the same tool you used before to restore, usually tool work both ways, what utillity you used to backup your EFS?
You cant use Odin for that.....can you get in download mode? flash a stock firmware again , make sure it boots now try to restore YOUR EFS backup with the same utility you made it
Thank you for the reply. For backup I used an app with the function to save and restore partitions, I could not use it to restore because it is an app that should be installed and used with the device started while i was in bootloop.
I resolved through the terminal of the TWRP with the following string, inserting backup efs.img into the internal sd:
dd if=/sdcard/efs.img of=/dev/block/platform/155a0000.ufs/by-name/EFS
ElPocho796 said:
Thank you for the reply. For backup I used an app with the function to save and restore partitions, I could not use it to restore because it is an app that should be installed and used with the device started while i was in bootloop.
I resolved through the terminal of the TWRP with the following string, inserting backup efs.img into the internal sd:
dd if=/sdcard/efs.img of=/dev/block/platform/155a0000.ufs/by-name/EFS
Click to expand...
Click to collapse
Hi
So is back in working order then? Great
ElPocho796 said:
Thank you for the reply. For backup I used an app with the function to save and restore partitions, I could not use it to restore because it is an app that should be installed and used with the device started while i was in bootloop.
I resolved through the terminal of the TWRP with the following string, inserting backup efs.img into the internal sd:
dd if=/sdcard/efs.img of=/dev/block/platform/155a0000.ufs/by-name/EFS
Click to expand...
Click to collapse
can you help me please. I have the same problem with my G930F. I had the superman-rom.zip and installed it through the manual on xda and now I have an unknown imei / Baseband and no sim. I saw that you had restored a backup and started working on it. I see an EFSbackup folder with efs.img and build.prop files. I could also put it back.
Related
OK so I know we don't have superoneclick to root any more so I need to download CM7, install it on my sd card and flash CWM via NV flash. I also know that I need to backup before clearing data and installing cm7.
My question is after to flashing CWM via NV flash can I boot up the phone and copy my backup to my pc before clearing data and installing CM7?
I am kind of a nonrisk taker and would like to have a copy of the backup on my pc in case I screw this process up and screw up my sd card at the same time.
If you have clockwork recovery installed, do a backup. Then on your sdcard you'll have a directory called clockworkmod, and backup under there. You can copy that to your pc if you're super paranoid about messing something up. Just keep in mind when you do a restore it checks the md5 sums, so do not rename anything, and when you put it back on your sdcard, make sure the pathname is the exact same as before. (Example clockworkmod/backup/12.31.2121blahblah.
Thanks, I think I got the copying part, but what I am asking is whether its ok to power up the phone after flashing CWM via NV flash and creating a backup but before installing CM7? Please tell me if this is a dumb question. I'm a lawyer, I'm used to being told I ask dumb questions.
Of course. CWM sits on a partition that's normally used for the reset to stock recovery. After you install it, and do a backup, your rom is still there. You can boot to it like normal, copy stuff to the computer, and then reboot again into recovery to install cm7.
Thank you kind sir.
I'm having trouble copying the nandroid backup from the old device to the new one - is there a trick.
So far I've:
Fastboot oem unlocked new device
Fastboot flashed same version (latest) of TWRP on new device
Copied TWRP backup to my computer
Tried to copy TWRP to new device via MTP in TWRP, but getting write errors. Also, TWRP can't seem to mount the /cache partition and wiping doesn't work.
Would appreciate some help.
Thanks,
Ryan
Update: here's what worked after-all
-Old device: nandroid from TWRP, copy all sd card contents to PC with USB 3 and check that they all made it over okay (usb 2 had more failures, but even with 3 it just stopped copying sometimes)
-New device here forward: For some reason I had to flash the factory image from Google to the RMA device - in addition to it removing the errors I was having, it made me not have to wait for the OTA updates to install.
-Fastboot oem unlock then fastboot flash TWRP recovery
-Nandroid from TWRP to create new folder in SD card with appropriate serial number
-Copy sd contents from pc to new device
-From PC in SD card, in TWRP folder, move the backup from the old device serial number folder to the new device serial number folder (if you skip this step, the nandroid won't show up)
-Restore backup from TWRP
Enjoy
ryanwalexander said:
I'm having trouble copying the nandroid backup from the old device to the new one - is there a trick.
So far I've:
Fastboot oem unlocked new device
Fastboot flashed same version (latest) of TWRP on new device
Copied TWRP backup to my computer
Tried to copy TWRP to new device via MTP in TWRP, but getting write errors. Also, TWRP can't seem to mount the /cache partition and wiping doesn't work.
Would appreciate some help.
Thanks,
Ryan
Click to expand...
Click to collapse
I achieved this using these steps:
fastboot oem unlock
fastboot flash recovery
fastboot bootloader
boot to recovery
create nandroid backup
reboot device
transfer contents of original phone via pc to new phone, making sure to put previous TWRP backips in the new TWRP backup folder
do NOT transfer any EFS backups
reboot to recovery
restore TWRP backup from previous device
I reflashed the factory image and was then able to copy over the TWRP backup to the appropriate location on the SD card, however the backup isn't showing up in TWRP to restore from.
Thanks - I'll try to copy all the contents over. I never check EFS in the backups, but thanks for the reminder. Would that pooch my phone?
justbabu said:
I achieved this using these steps:
fastboot oem unlock
fastboot flash recovery
fastboot bootloader
boot to recovery
create nandroid backup
reboot device
transfer contents of original phone via pc to new phone, making sure to put previous TWRP backips in the new TWRP backup folder
do NOT transfer any EFS backups
reboot to recovery
restore TWRP backup from previous device
Click to expand...
Click to collapse
Yes. Efs is tied to a specific imei
I'm still copying the contents of the phone over via Windows but it seems to stop (with no error) before it can do it all. Is there a trick or is this a problem with MTP or something?
justbabu said:
I achieved this using these steps:
fastboot oem unlock
fastboot flash recovery
fastboot bootloader
boot to recovery
create nandroid backup
reboot device
transfer contents of original phone via pc to new phone, making sure to put previous TWRP backips in the new TWRP backup folder
do NOT transfer any EFS backups
reboot to recovery
restore TWRP backup from previous device
Click to expand...
Click to collapse
ryanwalexander said:
I'm still copying the contents of the phone over via Windows but it seems to stop (with no error) before it can do it all. Is there a trick or is this a problem with MTP or something?
Click to expand...
Click to collapse
I found transferring via USB 3 would work far better than USB 2. I had in the past experienced Windows just stopping with USB 2.
Thanks. I'll give that a shot. I remember it transferring fine before - Now that I think about it, I'm pretty sure I was using USB 3 for that.
I'm still having trouble getting the backup from the old device to show up in TWRP. I even made a test backup with the new device to make sure it was going in the right folder.
justbabu said:
I found transferring via USB 3 would work far better than USB 2. I had in the past experienced Windows just stopping with USB 2.
Click to expand...
Click to collapse
ryanwalexander said:
Thanks. I'll give that a shot. I remember it transferring fine before - Now that I think about it, I'm pretty sure I was using USB 3 for that.
I'm still having trouble getting the backup from the old device to show up in TWRP. I even made a test backup with the new device to make sure it was going in the right folder.
Click to expand...
Click to collapse
Good luck. Just remember that TWRP will only look for backups in the folder it creates. It will be different on the new device.
justbabu said:
Good luck. Just remember that TWRP will only look for backups in the folder it creates. It will be different on the new device.
Click to expand...
Click to collapse
In other words, when you take a backup, TWRP creates /sdcard/TWRP/BACKUPS/<your serial number>
You may have to initiate a backup on the new device first to create the <your serial number> folder. That's no bad thing anyway. Always good to have a full backup of your new device including efs just in case.
Then, copy the backup from the <your serial number> folder to <your serial number> on your new phone AMD you should be good.
Everything worked out... For other readers trying to do the same thing here's the summary:
-Old device: nandroid from TWRP, copy all sd card contents to PC with USB 3 and check that they all made it over okay (usb 2 had more failures, but even with 3 it just stopped copying sometimes)
-New device here forward: For some reason I had to flash the factory image from Google to the RMA device - in addition to it removing the errors I was having, it made me not have to wait for the OTA updates to install.
-Fastboot oem unlock then fastboot flash TWRP recovery
-Nandroid from TWRP to create new folder in SD card with appropriate serial number
-Copy sd contents from pc to new device
-From PC in SD card, in TWRP folder, move the backup from the old device serial number folder to the new device serial number folder (if you skip this step, the nandroid won't show up)
-Restore backup from TWRP
Enjoy
hello guys,
i have a problem with restoring my nandroid backup.
so the digitzer of my s3 mini is broken and does not work partially. e.g. i cant enter my pin to unlock screen lock and i cant use twrp. so i used cwm (i guess it was 6.0.2.8.) to backup everything to my ext sd card. i dont know exactly if the backup was successfull but i cant remember any error messages and my backup is about 3,5gb big and there r following files:
boot.img
cache.ext4.tar
cache.ext4.tar.a
data.ext4.tar
data.ext4.tar.a
data.ext4.tar.b
data.ext4.tar.c
data.ext4.tar.d
nandroid.md5
recovery.img
system.ext4.tar
system.ext4.tar.a
now i wanted to restore only data on a new device: moto g peregrine via cwm. i installed cm12.1 on my moto, the backup comes from cm12.1 too.
error: md5 checksum mismatch -> i cutted nandroid.md5 and created an empty file named nandroid.md5 and copied it into the backup folder. then cwm restored. well... it says it was restored. but when i start android no data is restored.
so i tried to restore it via tatanium backup. this app finds my backup, but only system apps r listed. no user apps. (i just tried it again, no apps at all)
then i tried to open/browse the tar archives with a shell extension in windows. they are empty.
then i wanted to extract them with appextractor but it doesnt find a backup to extract.
then i tried nandroid manager. it finds the backup, it says, its 3,44gb big. when i browse the data.ext4.tar its empty. then i click on restore nandroid backup. it boots into recovery but then it says:
sd card marker not found
.....
E: unknown volume for path [/mnt/sdcard1/clockworkmod/backup/2012-01-01.00.00.35]
cant mount backup path
im using cwm 6.0.4.8
so can sum1 plz help how to restore it? or is it broken? is everything gone?
and another question: twrp has adb sideload-support. i could make a twrp backup via the openrecovery adb script but my internal storage has not enough space. if i could tell twrp to backup on the ext sd card perhaps it works
greetz
daemonicvs said:
hello guys,
i have a problem with restoring my nandroid backup.
so the digitzer of my s3 mini is broken and does not work partially. e.g. i cant enter my pin to unlock screen lock and i cant use twrp. so i used cwm (i guess it was 6.0.2.8.) to backup everything to my ext sd card. i dont know exactly if the backup was successfull but i cant remember any error messages and my backup is about 3,5gb big and there r following files:
boot.img
cache.ext4.tar
cache.ext4.tar.a
data.ext4.tar
data.ext4.tar.a
data.ext4.tar.b
data.ext4.tar.c
data.ext4.tar.d
nandroid.md5
recovery.img
system.ext4.tar
system.ext4.tar.a
now i wanted to restore only data on a new device: moto g peregrine via cwm. i installed cm12.1 on my moto, the backup comes from cm12.1 too.
error: md5 checksum mismatch -> i cutted nandroid.md5 and created an empty file named nandroid.md5 and copied it into the backup folder. then cwm restored. well... it says it was restored. but when i start android no data is restored.
so i tried to restore it via tatanium backup. this app finds my backup, but only system apps r listed. no user apps. (i just tried it again, no apps at all)
then i tried to open/browse the tar archives with a shell extension in windows. they are empty.
then i wanted to extract them with appextractor but it doesnt find a backup to extract.
then i tried nandroid manager. it finds the backup, it says, its 3,44gb big. when i browse the data.ext4.tar its empty. then i click on restore nandroid backup. it boots into recovery but then it says:
sd card marker not found
.....
E: unknown volume for path [/mnt/sdcard1/clockworkmod/backup/2012-01-01.00.00.35]
cant mount backup path
im using cwm 6.0.4.8
so can sum1 plz help how to restore it? or is it broken? is everything gone?
and another question: twrp has adb sideload-support. i could make a twrp backup via the openrecovery adb script but my internal storage has not enough space. if i could tell twrp to backup on the ext sd card perhaps it works
greetz
Click to expand...
Click to collapse
You can connect a USB mouse and keyboard to navigate and select whatever you need to select or do in CWM or TWRP, it will work with either recovery.
As for transferring user installed apps and their data, you can try backing them up to your google account and then restoring them from google on the new device. Or use the USB mouse/keyboard along with ES File Explorer to go to your /data/app folder and create copies of your installed apps, the backups will be in your backup/app folder on internal, copy them to PC then go your Android folder on the device and copy the app data for those apps to PC, then transfer the app copies to the internal on the new device and install them or use adb to sideload each of those apk files to the new device, then transfer the copied app data for those apps to the Android folder on the new device, then boot to recovery and wipe only cache, do not factory reset in recovery then reboot.
I DO NOT GIVE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
hi,
You can connect a USB mouse and keyboard to navigate and select whatever you need to select or do in CWM or TWRP, it will work with either recovery.
Click to expand...
Click to collapse
but for this i need a special otg adapter cause the s3 mini doesnt support otg originally. and dont i need to install an app or something on my device and confirm a message on my screen? like u wanna do an adb backup. havent tried it yet. i will do i i guess.
As for transferring user installed apps and their data, you can try backing them up to your google account and then restoring them from google on the new device. Or use the USB mouse/keyboard along with ES File Explorer to go to your /data/app folder and create copies of your installed apps, the backups will be in your backup/app folder on internal, copy them to PC then go your Android folder on the device and copy the app data for those apps to PC, then transfer the app copies to the internal on the new device and install them or use adb to sideload each of those apk files to the new device, then transfer the copied app data for those apps to the Android folder on the new device, then boot to recovery and wipe only cache, do not factory reset in recovery then reboot.
Click to expand...
Click to collapse
this presumes that i can unlock my lockscreen. doesnt it?
i will try to backup my data with cwm again. perhaps the backup is corrupted. and i will try to do an adb backup and control the phone via keyboard and mouse if i can unlock the screen and/or confirm a popup message.
can anyone say if i can make a twrp backup to my ext sd oder pc via adb shell? i know the command "twrp backup <options> <foldername>" but can i change the path where the backup will be stored?
thx for your reply
daemonicvs said:
hi,
but for this i need a special otg adapter cause the s3 mini doesnt support otg originally. and dont i need to install an app or something on my device and confirm a message on my screen? like u wanna do an adb backup. havent tried it yet. i will do i i guess.
this presumes that i can unlock my lockscreen. doesnt it?
i will try to backup my data with cwm again. perhaps the backup is corrupted. and i will try to do an adb backup and control the phone via keyboard and mouse if i can unlock the screen and/or confirm a popup message.
can anyone say if i can make a twrp backup to my ext sd oder pc via adb shell? i know the command "twrp backup " but can i change the path where the backup will be stored?
thx for your reply
Click to expand...
Click to collapse
You can use adb to remove lockscreen. There's a couple different ways using adb, research them.
As for OTG capability, you can try adb side loading an app called Stickmount by Chainfire if you can find a way to enable it after installing it.
Sent from my SCH-I535 using Tapatalk
ok thx.
i wanna use the openrecovery script with "adb shell twrp backup DO" but it says not enough space. so i want to store the backup on my ext sd. but how can i change the backup location to my ext sd? i only can specify a foldername within the backup path. but noch path :/
like here
http://www.pocketables.com/2014/10/using-twrps-new-adb-interface.html
hope sum1 can help me
I am a newbie!
So I wanted to start flashing custom ROMS on my device...
So I flashed the Custom Recovery(TWRP) and downloaded compatible Custom ROM...
Ok so by following some blogs and videos I took the system backup of boot, system.
And yes I am able to restore it...
I also read about Android Partitions(https://forum.xda-developers.com/general/general/android-partitions-explained-t3657183)
But when taking the Backup I saw a System Image partition there.
So I am wondering what is its use and should I backup that for pure Stock ROM Backup?
And also does it include the boot partition files or I also need to backup the boot partition with it?
And if I create this file using which option can I install this type of Backup?
Thanks in Advance
Tanmay_B said:
I am a newbie!
So I wanted to start flashing custom ROMS on my device...
So I flashed the Custom Recovery(TWRP) and downloaded compatible Custom ROM...
Ok so by following some blogs and videos I took the system backup of boot, system.
And yes I am able to restore it...
I also read about Android Partitions(https://forum.xda-developers.com/general/general/android-partitions-explained-t3657183)
But when taking the Backup I saw a System Image partition there.
So I am wondering what is its use and should I backup that for pure Stock ROM Backup?
And also does it include the boot partition files or I also need to backup the boot partition with it?
And if I create this file using which option can I install this type of Backup?
Thanks in Advance
Click to expand...
Click to collapse
It isnt complicated, just boot into TWRP, then choose the "Backup" option, the default partitions that TWRP automatically selects to backup are all you "need" to backup. TWRP backs up the boot partition, recovery partition and system partition by default, that is all you need.
To restore the backup, just boot into TWRP then select the "Restore" option, then restore the backup file.
The "system.img" backup creates a backup of the complete system.img, it is effectively the same thing as using adb shell to dump the system.img to obtain a copy, it contains everything involved with the system partition, including boot.img and kernel(zimage). This system.img backup can restored by using fastboot flash system command, adb shell with dd command, terminal emulator with dd command or by using the option in TWRP that allows flashing .img files.
Another option for devices that are rooted is to use apps like Flashify to flash the system.img, but these apps are risky and don't always flash correctly.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
It isnt complicated, just boot into TWRP, then choose the "Backup" option, the default partitions that TWRP automatically selects to backup are all you "need" to backup. TWRP backs up the boot partition, recovery partition and system partition by default, that is all you need.
To restore the backup, just boot into TWRP then select the "Restore" option, then restore the backup file.
The "system.img" backup creates a backup of the complete system.img, it is effectively the same thing as using adb shell to dump the system.img to obtain a copy, it contains everything involved with the system partition, including boot.img and kernel(zimage). This system.img backup can restored by using fastboot flash system command, adb shell with dd command, terminal emulator with dd command or by using the option in TWRP that allows flashing .img files.
Another option for devices that are rooted is to use apps like Flashify to flash the system.img, but these apps are risky and don't always flash correctly.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Thank You Bro So Much for explaining this:laugh:
Ok So I can keep the backup of the system image if I want a complete stock rom backup, right?
But what about the other partitions like Recovery, IMEI, FRP, Pinfo, Logo?
I mean to say if I clear all these partitions for eg IMEI, will my device's IMEI number be deleted?
Or after flashing the system img these partitons will be regenerated?
And yes I am using the default TWRP backup and I am able to restore my android backup...
Tanmay_B said:
Thank You Bro So Much for explaining this[emoji23]
Ok So I can keep the backup of the system image if I want a complete stock rom backup, right?
But what about the other partitions like Recovery, IMEI, FRP, Pinfo, Logo?
I mean to say if I clear all these partitions for eg IMEI, will my device's IMEI number be deleted?
Or after flashing the system img these partitons will be regenerated?
And yes I am using the default TWRP backup and I am able to restore my android backup...
Click to expand...
Click to collapse
The default TWRP backup is all you really need. It will completely backup everything you need to backup/restore your ROM, the system.img backup isn't necessary. It is no different than the system.img that can be extracted from your stock firmware file.
As for IMEI, the method of backing up and restoring IMEI doesn't involve TWRP, there are other tools for that. Do a Google search for:
"How to backup and restore IMEI"
I suggest that you don't mess with any of the other partitions
Sent from my SM-S767VL using Tapatalk
Droidriven said:
It isnt complicated, just boot into TWRP, then choose the "Backup" option, the default partitions that TWRP automatically selects to backup are all you "need" to backup. TWRP backs up the boot partition, recovery partition and system partition by default, that is all you need.
To restore the backup, just boot into TWRP then select the "Restore" option, then restore the backup file.
The "system.img" backup creates a backup of the complete system.img, it is effectively the same thing as using adb shell to dump the system.img to obtain a copy, it contains everything involved with the system partition, including boot.img and kernel(zimage). This system.img backup can restored by using fastboot flash system command, adb shell with dd command, terminal emulator with dd command or by using the option in TWRP that allows flashing .img files.
Another option for devices that are rooted is to use apps like Flashify to flash the system.img, but these apps are risky and don't always flash correctly.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Droidriven said:
The default TWRP backup is all you really need. It will completely backup everything you need to backup/restore your ROM, the system.img backup isn't necessary. It is no different than the system.img that can be extracted from your stock firmware file.
As for IMEI, the method of backing up and restoring IMEI doesn't involve TWRP, there are other tools for that. Do a Google search for:
"How to backup and restore IMEI"
I suggest that you don't mess with any of the other partitions
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
OK Thanks Bro...
I lost the funcionality Phone in my N8000. I think i lost the imei e someone more else. How can i restore my efs? I have a backup of my efs in format zip and format tar made 5 years ago ( i dont remember what application i used) , but i can not install via Odin or via Twrp, said Invalid Zip format on checking Digest File. I think the problem is checking the md5 generation that is not compatible with Odin and Twrp.
Someone can help me to restore the /efs partition with old backup. Thanks
see your identical post .
I resolved this situation, using Solid Explorer and Qute Terminal with root.
Credits
http://androidadvices.com/restore-imei-efs-folder-galaxy-s3-details/
Thanks
It is not solved, when reboot the system, the imei of phone, N8000 is another, is from another file from i used to recover.
Manually from my backup what files and permissions i have to copy to the /efs in root of my N8000? First i copy nv_data.bin, nv_data.bin.md5 and the folder /imei and works. I do not known the original permissions of the files, perhaps now the problem is this.
Someone can help me?
Thanks
With this guide "[GUIDE] Recover your IMEI in 9 steps. " https://forum.xda-developers.com/galaxy-s2/general/guide-recover-imei-9-steps-t1264021 , i resolved my problem with imei, no problems with reboot, but now i did not have access to Wifi, i can not connect to my Wifi Network.
Someone can help me, how can activate wifi? What files i need to copy from my backup? Before clean the /efs i made a backup the old efs.
Thanks
Flash stock rom .
I flash the stock rom and now i did not have any problems