Now that we have root is there a way to back up EFS? I'm a noob and managed to get my GS2's efs folder corrupted after flashing a ROM don't want the same thing happening to my S4
cl_l said:
Now that we have root is there a way to back up EFS? I'm a noob and managed to get my GS2's efs folder corrupted after flashing a ROM don't want the same thing happening to my S4
Click to expand...
Click to collapse
just download GSII_Rapair form playstore... gl
Or... do it yourself.
Download and install Android Terminal Emulator from the play store. You will need to get to a root prompt (su enter).
The following assumes that the partition information posted by mohan_kr in the Android Development forum is accurate.
Code:
dd if=/dev/block/mmcblk0p10 of=/mnt/sdcard/efs.img
Also, since I don't have the s4 yet, I am assuming that the path to internal storage is /mnt/sdcard/ as it is on the s2 with 4.1.2. But use a file explorer to verify the path to internal storage.
Store this in a safe place. To restore the efs partition:
Code:
dd if=/mnt/sdcard/efs.img of=/dev/block/mmcblk0p10
So, before I do a firmware update (In this case 4.2.2 to 4.3 OTA) I do a Titanium backup and a TWRP backup and copy both sets of backup files to my PC; it obviously makes no sense to only have backups on the device you are backing up. I upgraded to TWRP 2.6.0.0, did a full backup, and as usual I went to copy my backup files over to my Windows 7 computer using Windows Explorer and I can only get a couple of the files to move over. No warning, no error, no nuttin. This has always worked before......Did something change, and if so, how do I fix it?
I see from another post that TWRP changed the permissions of the backup files in the latest version of the program, and in my case the location as well. The workaround is to a) change the permissions on all those backup files, which I could see the nightmare problems that could cause later on when doing a restore and/or the security issues or b) doing an adb pull.
SOLVED.
The adb pull did the trick. All files were transferred over to my PC.
I had several issues getting adb to work:
1) I had an old version of the SDK installed on my PC which was causing a devices not recognized problem or something similar.
2) I didn't notice the message about verifying the RSA on my phone, which once verified, fixed the phone "offline" problem.
3) The screen lock on my phone was coming on after its timeout and locking me out from seeing the phone.
reverted to twrp 2.5.0.0
Same problem here with Google Nexus i9250 / twrp 2.6.0.0 / win7 64bit. Tried to copy backup of (BOOT/SYSTEM/DATA) via MTP or ftp from Nexus to PC. Only the first two files (boot.emmc.win/-md5) were copied. After downgrading to twrp 2.5.0.0 everthing was fine.
I had the same problem. It is caused by strange suid permissions set by TWRP. Solved it using chmod 0664 /data/media/0/TWRP/... (as root)
I was not able to adb pull before changing the files' permissions.
More details here:
http://forum.xda-developers.com/showpost.php?p=44120545&postcount=14
(Google found that HTC One thread first, so I didn't search any further)
Type this in Terminal Emulator:
su
busybox chown - R 1023.1023 /data/media/*
That should solve all permissions problems.
I had no trouble at all by doing the following:
Access the sdcard from /data/media/0
Copy data.ext4.win and system.ext4.win to a temporary location.
(The "Set UID" and "Set GID" permissions were automatically removed. If not, you can change them from here.)
Copy the files to PC using MTP.
The remaining backup files from the TWRP directory can be copied normally.
Done
Note: You can instead just change the permissions on these two files inside the TWRP directory, but I did the temporary location copy just to be safe.
Mercado_Negro said:
Type this in Terminal Emulator:
su
busybox chown - R 1013.1023 /data/media/*
That should solve all permissions problems.
Click to expand...
Click to collapse
coming up with chown: unknown user -
is that a space between 1023 and /data?
daryllh said:
coming up with chown: unknown user -
is that a space between 1023 and /data?
Click to expand...
Click to collapse
I'm sorry, I made a mistake there. The correct command is:
su
busybox chown -R 1023.1023 /data/media/*
I wrote 1013.1023 and it's 1023.1023
Mercado_Negro said:
I'm sorry, I made a mistake there. The correct command is:
su
busybox chown -R 1023.1023 /data/media/*
I wrote 1013.1023 and it's 1023.1023
Click to expand...
Click to collapse
After I did this command, my pc can't detect the back up
handols said:
After I did this command, my pc can't detect the back up
Click to expand...
Click to collapse
Did you plug/unplug your device after running this command? There shouldn't be any problems. Furthermore, now you should be able to copy your TWRP and TiBu backups successfully to your computer. It's a pretty straight forward process.
Im on twrp 2.5.0.0 with Android 4.3. I cant copy the BACKUP folder directly to my PC with the default windows explorer because the backup isnt stored in /sdcard/TWRP. How can I fix this? I used to be able to do this without adb push/pull...
Mercado_Negro said:
I'm sorry, I made a mistake there. The correct command is:
su
busybox chown -R 1023.1023 /data/media/*
I wrote 1013.1023 and it's 1023.1023
Click to expand...
Click to collapse
Thanks for this. I'm able to backup TWRP folder to PC now :highfive:
Since my original post 3 months ago I updated all my programs to 4.3 friendly versions as each was released (superuser 1.0.2.1, Windows drivers, TWRP 2.6.3.0, etc.) and now I don't need to do adb pulls any more and I can just copy and paste files from my phone to my pc and all files are copied over without missing any of them. Now I see the updated programs are already starting to show up for Android 4.4; here we go again.
Now see 0 / legacy emulated
Mercado_Negro said:
I'm sorry, I made a mistake there. The correct command is:
su
busybox chown -R 1023.1023 /data/media/*
I wrote 1013.1023 and it's 1023.1023
Click to expand...
Click to collapse
Hi just wondering, Is there a way to cancel this command (just add a +R maybe) I did it on my phone and I think it may be the cause that I have a Legacy emulated 0 path problem Ive searched around and cant seem to find a solution. Thanks
NightCrawler504 said:
Hi just wondering, Is there a way to cancel this command (just add a +R maybe) I did it on my phone and I think it may be the cause that I have a Legacy emulated 0 path problem Ive searched around and cant seem to find a solution. Thanks
Click to expand...
Click to collapse
What's the problem? That's a valid path.
Legacy emulated 0
Mercado_Negro said:
What's the problem? That's a valid path.
Click to expand...
Click to collapse
I have an external sd (sdcard1) = /storage/sdcard1 so gr8 but then I have emulated (??) Storage/emulated/legacy and Storage/emulated/0 and sdcard0 storage/sdcard0 they were complety different folders been reading around seems to be a problem with cm when I go from 4.2 and over my phone is a e970 att, cant delete the emulated folder... already erased all my data previously, any help will do,I'm almost sure it had nothing to do with the chown command but had to give a try.
NightCrawler504 said:
I have an external sd (sdcard1) = /storage/sdcard1 so gr8 but then I have emulated (??) Storage/emulated/legacy and Storage/emulated/0 and sdcard0 storage/sdcard0 they were complety different folders been reading around seems to be a problem with cm when I go from 4.2 and over my phone is a e970 att, cant delete the emulated folder... already erased all my data previously, any help will do,I'm almost sure it had nothing to do with the chown command but had to give a try.
Click to expand...
Click to collapse
No, it doesn't have anything to do with this command since it's just a way to set different permissions.
Hi,
I want to create an updater-script file that copies /sdcard/data to /data,
How can i do this? dd and cp commands say 'cannot find /sdcard/data/*: no such file or directory'
I don't want to integrate files in the zip package
Is there a way or a command to do that?
I searched on the web, but seems i cannot a working solution, maybe you can anwser
Well your query is wrong.updater-script is for flashable zips and in your case you don't want to integrate the files in the zip right?
Try using this command via terminal :
#cp ~/sdcard/data/*your data /data
what are you trying to do?? o_0
files in sdcards have ownership system:sdcard_rw and permissions something like ----rwx-r-x
to copy files with cp to /data.. you need to be root on terminal/adb shell
the copy will change ownership to root:root while keeping permissions intact...
with such odd permissions and ownership for files in /data .. you are looking at a bootloop..
you'd have to fix permissions for each and every thing incase you really need to copy it
can you tell what are you trying to copy.. and what's in /sdcard/data :|
Hi, sorry for my late reply
I will try that command and post result, :good:
It worked, thanks
Hello,
My S4 is rooted, es3 cannot delete, move or change permission.
With a terminal under su, chmod or rm - Rf gives Access Denied.
The directory is a clockworkmod created by backup, named backup.
Suggestions ?
Hi there,
Please wait until mods will move this thread to the device specific forum for more relevant answers.
Stand by
[email protected] said:
Hello,
My S4 is rooted, es3 cannot delete, move or change permission.
With a terminal under su, chmod or rm - Rf gives Access Denied.
The directory is a clockworkmod created by backup, named backup.
Suggestions ?
Click to expand...
Click to collapse
I am on cm12 nightly.
On modern versions of CWM, you should always use the delete function within the backup and restore menu to remove nandroid backups. This is because CWM by default automatically does incremental backups whenever you make a nandroid. Manually deleting nandroid backups when CWM is set up for incremental backups is a really bad idea, as it screws up every single nandroid backup you have, including the master backup. Thus CWM protects the nandroid backup directory.
So, to recap, enter CWM, go to "backup and restore", then delete your nandroid backup from there. After that, go to "free unused backup data" and select it to have CWM restore access to the now freed space.
Thanks for the explanation.
Rom Manager is not installed at present. I am using TRWP manager instead.
I installed CWM Backup manager from Guimberg .
I could pull the backup to a new folder, but delete the original clockworkmod folder did not work.
Would I need to have a cwm recovery installed in order to delete cwm backups ?
You didn't mention you had replaced CWM with TWRP. So, before putting CWM back on to the S4 and using it to wipe away the directory, did you change permissions in ES File Explorer or execute a chmod 777 command in Terminal? Since permissions is the issue here you have to change them.
Being in su I used chmod 777 and rm -rf as well as trying with es3 to change permission but always got "access denied".
I also try with twrp recovery file manager.
I have busy box and sudo installed.
The directory is at /mnt/shell/emulated/
In a nutshell I cannot change permission.
Replace TWRP with CWM, delete the nandroid backups and free the space. Then restore TWRP and you should be good to go. If that doesn't work, your only other alternative is to reset.
I replaced and try, but the only change I could do is the rename of the bu and a zip. Delete was denied.
It is a minor isue since the file is only 255MB. I guess that their are some bits corrupted somewhere and therefore as you suggested a format will fix it.
I will wait for a better reason to do that and live with the bu files happily.
Thanks for your advises.
Didn't find the thanks button. I didn't not understood near the quote as the location for doing it?
Thanks button is on the left, at the bottom of each post under the user information.
Done
I finally managed to repair the damage caused by EFS and by when I go to the root explorer I had a clean empty folder EFS whatever I tried to install the new ROM moaning and costum and wipe reset Factory me is always the folder EFS empty my IMEI was correct as it was under the battery, the only thing I had a bad signal and wifi is deenergizes.
To repair the damage I'm desperate to be ordered from stock rom sammobil version 4.4.2 because my phone was slow I then ordered stoc 5.0 then I root the phone and ordered phils latest recover and then I went under the option to mount and put the mount seytem then I have connected phone to a PC and install the adb shell on the computer I Open cmd and typed it
adb shell
su
mke2fs /dev/block/mmcblk0p11 ( skip to next step if fail)
mount -w -t ext4 /dev/block/mmcblk0p11
reboot
This will create a generic EFS files on device
Root explorer/efs and delete factorymode(OFF) and replace with factorymode(ON)
reboot in recovery wipedata factory reset...don
This last what it says to me it was not necessary because I went in and looked exporer root file factorymode where it has been on only one I did factory reset and that's it I got back EFS files and I am so done with all programs EFS Bacup :good:
P : S: because I have a bad signal or should now install new modem in order to find the best signal
Yeah used to see that tutorial by nowy57.
Sent from my GT-N7000