yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] lyriquidperfection:
From what ive seen, you changed the setting to massstorage,adb so adb communication should still work. Try changing the setting back to its original state and see if adb communication still works then. :)
[Galaxy S II Original Android Development] Phil3759:
Is it because i do not have an insecure kernel?
[Galaxy S II Original Android Development] masterpointer:
can't find phone

Hi

What am I missing?

I'm running Resurrection Remix 2.4 and when I connect the phone to the computer as usual, the app says that it can't find the phone!

I understand that the USB should be connected, but the problem is that if I connect the USB, it won't let me connect the phone to the computer at all. All the Roms I have tried will always prompt you to disconnect the USB before letting you connect.

Is there another way I can connect? Someone please advise, thanks
[Galaxy S II Original Android Development] ilovebytes:
thanks for your update - efs pro now recognizes my sgs 3 but wether i choose to make an img or a tar i always get a tar ?

and i am not able to save the backup to the pc - when i choose pc it says the dir where it should be but it does not make the dir and agains saves the tar to the sdcard.

how can i check if the tar made is alright an really backed up my efs ;) sould be sure for worst case :D
[Galaxy S II Original Android Development] lyriquidperfection:
Hi it really doesnt matter which method you choose. Its all down to preference.

Tar Archive is a good method as its filesize is small. Only 5Mb.

Partition Image is the reccomended method as its a full clone of the entire EFS partition and is md5 hashed for safety.

Hope this helps.:)
[Galaxy S II Original Android Development] gadget069:
I'm getting this error when trying ot use this on my S3.
[Galaxy S II Original Android Development] lyriquidperfection:
Okay I will have a look. Thanks for letting me know. :)
[Galaxy S II Original Android Development] coldbeermt:
I tried 1.6.8 with my Galaxy R (GT-i9103). I selected Galaxy S II as device profile because my efs partition is the same (mmcblk0p1, as shows the mount command for the efs partition). And it says "Device Partition Location appears to be invalid! Make sure you have selected the CORRECT Device Profile then try again!".

If I choose "Add Device..." button, I write "Galaxy R" for the Device Name and "mmcblk0p1" as the location and the response is "Partition Location is Invalid! Please try again a VALID Partition Location."

adb shell
$ mount
/dev/block/mmcblk0p1 on /efs type ext4 (rw,nosuid,nodev,noatime,barrier=1,data=ordered)
[Galaxy S II Original Android Development] lyriquidperfection:
I seeyoutyped the mount command from the user shell and not a root shell. Your device must be rooted or the partition location check will fail as it lists the partitions in the '/dev/block' folder.

Open a Terminal and type:

ls /dev/block

If mmcblk partitions are not in the list then this will be the problem. On ICS all partitions are visible but I think on GB they are hidden.

Let me know and ill release an update for EFS Pro.

Also I think on GB the partitions are stored in a sub folder in the '/dev/block' folder. Please check all sub folders and let me know please. Thanks.
[Galaxy S II Original Android Development] gadget069:
I'll wait to see if there is a fix before i start getting flash happy.

Thanks
[Galaxy S II Original Android Development] lyriquidperfection:
Hi Im already fixing this, I altered the code and forgot to put something back while testing. If your backup is 20mb, it can renamed to img.

Sorry for this bug and update will be released soon. :)
[Galaxy S II Original Android Development] gadget069:
Even though i had the error, i have 3 .tar files that are around 20mb each (i tried 3 times to see if it was user error).
[Galaxy S II Original Android Development] lyriquidperfection:
Hi, do me a favour and type the following into a Terminal Emulator and tell me waht the output is:

md5sum /dev/block/mmcblk0p3
[Galaxy S II Original Android Development] gadget069:
"not found"

There is a file with that name but it is empty, 0kb.
[Galaxy S II Original Android Development] lyriquidperfection:
Hang in there, ive updated EFS Pro and implemented auto detection of the efs folder which has now made device profiles redundant. Please wait and ill get it uploaded. It should fix your problem. :)
[Galaxy S II Original Android Development] lyriquidperfection:
EFS Pro v1.7.12 has now been released!
[Galaxy S II Original Android Development] gadget069:
Still having an issue, i also never get the supersu prompt (not sure if this is a problem not using superuser).
[Galaxy S II Original Android Development] lyriquidperfection:
Goto your Terminal and type:

busybox ls -1

Thats number one on the end not the letter L. Let me know if it prints one entry per line.
[Galaxy S II Original Android Development] lyriquidperfection:
Hi, try without the MD5 Hash option checked and see if the error still occurs.
[Galaxy S II Original Android Development] lyriquidperfection:
@ ilovebytes

Re-download EFS Pro and see if that makes a difference. I made a few changes in the code.
[Galaxy S II Original Android Development] ilovebytes:
dumb question do i need to have busybox on my sgs3 before using efs pro ? maybe thats the problem cause i thought its included into efs pro

i will try new version now

update with new version i got error message that no busybox is installed - installing right now
[Galaxy S II Original Android Development] gadget069:
Me too, says busybox not installed.
[Galaxy S II Original Android Development] lyriquidperfection:
Finally, looks like missing BusyBox was the culprit! :)
[Galaxy S II Original Android Development] coolmast3r:
i got the same problem with ilovebytes. can u help me? i have re-download the 'updated' file by you. still same problem. i'm using windows 7 64 bit.
[Galaxy S II Original Android Development] ilovebytes:
so now i installed busybox and efs pro starts without an error and that are the results i get with the various options:

tar save to pc with and without md5 hash

Checking Device Connection... Device Connected!
Checking ROOT Access... Okay.
Backing Up Device's '/efs' Folder, Please Wait...
Detected '/efs' Partition Location: sh: mountpoint: not
Creating EFS Backup TAR Archive... Okay.
EFS Backup Success!
Copying EFS Backup To PC Storage... Okay.
Copied: 4549 KB/s (5450240 bytes in 1.170s)
Deleting Temporary EFS Backup From Device... Okay!
Operation Finished!

i get a tar on pc with 5,2 Mb

same if i try tar on device with and without md5 hash also tar with 5,2 Mb

if i try img with md5 hash i get :

Checking Device Connection... Device Connected!
Checking ROOT Access... Okay.
Backing Up Device's '/efs' Folder, Please Wait...
Detected '/efs' Partition Location: sh: mountpoint: not
Creating EFS Backup Partition Image...
Verifying MD5 Checksum... Failed!
Device MD5 Hash: md5sum: can't open 'sh:': No suc
Backup Data MD5 Hash: md5sum: can't open '/sdcard/EFSP
Error: MD5 Checksum Mismatch!!!
DO NOT USE THIS BACKUP!!!
Operation Finished!

the same i get with img and md5 hash on device

with img and without md5 hash i get:

Checking Device Connection... Device Connected!
Checking ROOT Access... Okay.
Backing Up Device's '/efs' Folder, Please Wait...
Detected '/efs' Partition Location: sh: mountpoint: not
Creating EFS Backup Partition Image...
Copying EFS Backup To PC Storage... Okay.
Copied: remote object '/sdcard/EFSProBackup/EFS_2012622_215552.img' does not exist
Deleting Temporary EFS Backup From Device... Okay!
Operation Finished!

but there is no img file wether on pc nor on device

@coolmast3r you need to install busybox from play store first of all
[Galaxy S II Original Android Development] lyriquidperfection:
@coolmaster

@ilovebytes

@gadget069

Goto Terminal and type:

mountpoint -n /efs

Post back what it says. I have my suspicion that the mountpoint applet is not included with the busybox version you are using.

Please also state the full busybox version.
[Galaxy S II Original Android Development] coolmast3r:
Connected Device SN.: 0260000600000001

Device Manufacturer: SAMSUNG

Device Model: GT-I9100G

ROM Build: GT-I9100G-user 2.3.6 GINGERBREAD DZKL3 release-keys

Android Version: 2.3.6

BusyBox Version: 1.19.1-cm71

SU Binary Version: 3.0.3

result of mountpoint -n /efs :

UNKNOWN /efs

ok now after su, result of mountpoin -n /efs :

/dev/block/mmcblk0p1 /efs
[Galaxy S II Original Android Development] gadget069:
Mountpoint not found, busybox v1.20.1 stericson
[Galaxy S II Original Android Development] ilovebytes:
first of all thank you for not giving up on us ;)

i hope you mean the terminal on my s3 - for

mountpoint -n /efs

i get : /system/bin/sh: mountpoint not found

busybox is version 1.20.1 -stericson
[Galaxy S II Original Android Development] gadget069:
Yes thanks for the help, hopefully we can get this figured out.
[Galaxy S II Original Android Development] lyriquidperfection:
try typing:

busybox mountpoint -n /efs

And if you get the same result, remove that busybox version and install busybox 1.19.4-stericson.
[Galaxy S II Original Android Development] coolmast3r:
ok now after su, result of mountpoin -n /efs :

/dev/block/mmcblk0p1 /efs
[Galaxy S II Original Android Development] ilovebytes:
That gives mehr the following :

app_155@android:/ $ export PATH=/data/local/bin:$PATH

app_155@android:/ $ busybox mountpoint -n /efs

/dev/block/mmcblk0p3 /efs

app_155@android:/ $
[Galaxy S II Original Android Development] gadget069:
app_147@android:/ $ export PATH=/data/local/bin:$PATH

app_147@android:/ $ busybox mountpoint -n /efs

/dev/block/mmcblk0p3 /efs

app_147@android:/ $
[Galaxy S II Original Android Development] lyriquidperfection:
@ilovebytes

@gadget069

Now confirm if you get the same output by typing:

mountpoint -n /efs

If not ill modify the code again and reupload. :)
[Galaxy S II Original Android Development] lyriquidperfection:
Just noticed in a previous post of yours thatyou are running Gingerbread. On ICS the mountpoint command doesnt require su rights but looks like it does on gingerbread so ill modify the code and reupload in the next hour when ive heard back from ilovebytes and gadget069. :)
[Galaxy S II Original Android Development] ilovebytes:
export PATH=/data/local/bin:$PATH

app_155@android:/ $ export PATH=/data/local/bin:$PATH

app_155@android:/ $ busybox mountpoint -n /efs

/dev/block/mmcblk0p3 /efs

app_155@android:/ $ mountpoint -n /efs

/system/bin/sh: mountpoint: not found

127|app_155@android:/ $

still the same
[Galaxy S II Original Android Development] lyriquidperfection:
Cool ill pm you with more details in the morning. :)
[Galaxy S II Original Android Development] KennyLegend:
I'm up for it too
[Galaxy S II Original Android Development] bunnybash:
This has definitely piqued my interest, I am willing to help beta test too.
[Galaxy S II Original Android Development] lyriquidperfection:
Right to avoid any trouble, Out of the 3 Beta testers, im looking for 1 that must fit the following criteria:

They must already have two valid working EFS backups. One as a Partition Image (*.img) AND one as a Compressed Archive (*.tar). If your file extension is '.tar.gz' then just rename it to '.tar'.

You must have a device that already has a corrupt EFS folder. For example, Missing MAC addresses and / or missing or wrong IMEI.

This volunteer will be testing the Restore function of EFS Pro using both of the Backup types to confirm successful restore.

One volunteer for this task please and you must meet the above criteria.

Thanks! :)
[Galaxy S II Original Android Development] Bruce MJ:
Thank you 4 the effort. Il'll be looking for it when it's released.

Sent from HP touchpad CM7.1 using xda premium
[Galaxy S II Original Android Development] lyriquidperfection:
EFS Pro is nearly ready. I decided to take the plunge and do the testing on my device! :-)
[Galaxy S II Original Android Development] lockieio:
wow great man :)

i hope it will work perfectly...let us know when you are finish :)
[Galaxy S II Original Android Development] lyriquidperfection:
EFS Pro is ready! Ill upload in the afternoon (GMT) for everyone to try! :)
[Galaxy S II Original Android Development] lyriquidperfection:
EFS Pro V1.0.1 has been released! :)
[Galaxy S II Original Android Development] aceofclubs:
Great work mate.
[Galaxy S II Original Android Development] erickgoldner:
Hi... great work on the tool.

But i'm having a little trouble.

Im on I9100XWKI4 and just used CF-Root-SGS2_XW_NEE_KI4-42-v4.2-CWM4.tar to root it. I do have the CWM and Superuser apps, but when im trying to Backup the EFS folder it's giving me this :

Checking Device Connection...

Device Connected!

Restarting ADB Server...

Checking ROOT Access...

No PERM ROOT Access! Aborting...

Any ideas?

Thanks
[Galaxy S II Original Android Development] Apoena:
+1

I'm on I9199CEKI2 and used CF-Root-SGS2_CE_XEN_KI2-v4.2-CWM4 to root it. I also killed all KIES services running but comes up with the same "No PERM ROOT Access"
[Galaxy S II Original Android Development] SugarySnack:
Awesome tool. This should be stickied.
[Galaxy S II Original Android Development] 6pudu5:
I also have the problem of root is not allowed.

Construction XWKI8 and SiyahKernel 1.8.

Checking Device Connection...

Device Connected!

Restarting ADB Server...

Checking ROOT Access...

No PERM ROOT Access! Aborting...
[Galaxy S II Original Android Development] girishmukkattu:
good work

Hai lyriquidperfection ,

EFS pro Working very well...I have a corrupted efs file in my gs2.I just backedup efs with EFS pro and then restored it.Now I have baseband and IMEI. thank you so much...

I tried three times to get root access.
[Galaxy S II Original Android Development] Neo.:
Thank you
[Galaxy S II Original Android Development] lyriquidperfection:
There is a bug in EFS Pro for everyone using CF-Root. The bug is caused by insecure kernel that CF-Root uses. This results in the No Perm Root Error. A temporary work around is to flash a secure kernel back to your device while using EFS Pro. You will still retain Root permissions but CWM Recovery will be lost. This can be restored by flashing back the CF-Root Kernel when you have finished using EFS Pro. I will get this bug fixed asap. :)

BR

Gaz
[Galaxy S II Original Android Development] KennyLegend:
Is this for pc only or can it be used on the phone?
[Galaxy S II Original Android Development] Nyssa1104:
Thanks for your app :).
[Galaxy S II Original Android Development] lyriquidperfection:
EFS Pro runs on the PC but you need to make sure your phone is connected.
[Galaxy S II Original Android Development] gadget069:
app_147@android:/ $ mountpoint -n /efs

/system/bin/sh: mountpoint: not found

127|app_147@android:/ $
[Galaxy S II Original Android Development] lyriquidperfection:
Look closer!

Says not found when you type mountpoint on its own. Give me an hour and ill have it fixed! :)
[Galaxy S II Original Android Development] ilovebytes:
i meant the same as without the busybox command before

please take your time - you Don't need any sleep? ;)
[Galaxy S II Original Android Development] lyriquidperfection:
EFS Pro v1.7.13 released!

Hopefully busybox bugs are gone! :)
[Galaxy S II Original Android Development] gadget069:
Ill give a shot when I get home, thanks.
[Galaxy S II Original Android Development] gadget069:
We have success!!!!!! I'lll get a donation by the end of the weekend, thanks!!!!
[Galaxy S II Original Android Development] ilovebytes:
you sir are my hero - works like a charm now without any errors

both tar and img with md5 hash and saves perfectly to device and pc

tar is 5,2 MB

img is 20 MB

Thx a lot !!!
[Galaxy S II Original Android Development] -MB-:
This version still errors on load, and won't allow me to select a backup,

with re-scan just giving me the errors again.
[Galaxy S II Original Android Development] gadget069:
All i have is the .img file, supposed to have a .tar too?

Its telling me i don't have busy box installed again, weird. ** forget this forgot i had to restore to a nandroid, so busybox was not installed :/**
[Galaxy S II Original Android Development] garf02:
Backup not working for me.

i see this

View attachment 1149954

and this

View attachment 1149961
[Galaxy S II Original Android Development] soulbkd:
It's a great tool! Is it working on Samsung Galaxy W I8150 (rooted stock rom)?

Because I've downloaded EFS_Pro_1.7.13_Release.zip, but i can not find any backup created, neither on PC storage or SD Card...

Please help
[Galaxy S II Original Android Development] lyriquidperfection:
What superuser package are you using?
[Galaxy S II Original Android Development] lyriquidperfection:
Hi can you post a copy of the log output please?
[Galaxy S II Original Android Development] teuntje3:
I tryd this for my Nexus S, but it only worked for partition image .img but I can't find a file on my nexus s.

And if I want to make a tar it says it failed with unknownen error..
[Galaxy S II Original Android Development] lyriquidperfection:
Can you give me the device info from the log please?
[Galaxy S II Original Android Development] soulbkd:
here is the log output on EFS Pro Window:

Checking Device Connection... Device Connected!
Checking ROOT Access... Okay.
Backing Up Device's '/efs' Folder, Please Wait...
Detected '/efs' Partition Location: Usage: su [options] [LOGIN] Options: -c, --command COMMAND pass COMMAND to the invoked shell -h, --help display this help message and exit -, -l, --login make the shell a login shell -s, --shell SHELL use SHELL instead of the default in passwd -v, --version display version number and exit -V display version code and exit. this is used almost exclusively by
Creating EFS Backup Partition Image...
Verifying MD5 Checksum... Okay!
Device MD5 Hash: Usage: su [options] [LOGIN]

Backup Data MD5 Hash: Usage: su [options] [LOGIN]

Copying EFS Backup To PC Storage... Okay.
Copied: remote object '/sdcard/EFSProBackup/EFS_2012624_93356.img' does not exist
Operation Finished!

screenshot:

It says Copying EFS Backup To PC Storage... Okay.

but I can't find it in the application folder on PC.
[Galaxy S II Original Android Development] emptyragnarok:
It's not working.. :( not creating backup :(

I am also getting

remote object '/sdcard/EFSProBackup/EFS_2012624_93356.img' does not exist

this kind of error
[Galaxy S II Original Android Development] lyriquidperfection:
Is Mass Storage mounted?
[Galaxy S II Original Android Development] garf02:
I've tried with superuser ChainDD and SuperSU Chainfire, the result is same: backup dont' work.

With the old versione 1.6.8 the backup works without problems
[Galaxy S II Original Android Development] lyriquidperfection:
Can you post the log of your device info please and I will investigate further.
[Galaxy S II Original Android Development] garf02:
This is the log:

Connected Device SN.: 304D196FB83A715E

Device Manufacturer: SAMSUNG

Device Model: GT-I9100

ROM Build: GT-I9100-user 4.0.3 IML74K XWLPG release-keys

Android Version: 4.0.3

BusyBox Version: 1.19.4-cm9

SU Binary Version: 3.0.3.2

And this is error log of backup:

Checking Device Connection... Device Connected!

Checking ROOT Access... Okay.

Backing Up Device's '/efs' Folder, Please Wait...

Detected '/efs' Partition Location: Usage: su [options] [LOGIN] Options: -c, --command COMMAND pass COMMAND to the invoked shell -h, --help display this help message and exit -, -l, --login make the shell a login shell -s, --shell SHELL use SHELL instead of the default in passwd -v, --version display version number and exit -V display version code and exit. this is used almost exclusively by

Creating EFS Backup Partition Image...

Verifying MD5 Checksum... Okay!

Device MD5 Hash: Usage: su [options] [LOGIN]

Backup Data MD5 Hash: Usage: su [options] [LOGIN]

Copying EFS Backup To PC Storage... Okay.

Copied: remote object '/sdcard/EFSProBackup/EFS_2012624_175226.img' does not exist

Deleting Temporary EFS Backup From Device... Okay!

Operation Finished!
[Galaxy S II Original Android Development] lyriquidperfection:
It looks to me like an invalid command line parameter is being passed to the su binary but im not experiencing these problems myself.
[Galaxy S II Original Android Development] wruster:
On my Galaxy S3 now there is two efs folder :eek:
[Galaxy S II Original Android Development] lyriquidperfection:
That may be a problem!
[Galaxy S II Original Android Development] sagarwadhwa1:
The efs pro (1.7.13) does not save the .img file for galaxy R!

It says that it is successful however there isn't any .img file created, neither on sdcard, nor on pc. And i started the program using run as administrator.

this is the log for .img option:
Checking Device Connection... Device Connected!
Checking ROOT Access... Okay.
Backing Up Device's '/efs' Folder, Please Wait...
Detected '/efs' Partition Location: Usage: su [options] [LOGIN] Options: -c, --command COMMAND pass COMMAND to the invoked shell -h, --help display this help message and exit -, -l, --login make the shell a login shell -s, --shell SHELL use SHELL instead of the default in passwd -v, --version display version number and exit -V display version code and exit. this is used almost exclusively by
Creating EFS Backup Partition Image...
Verifying MD5 Checksum... Okay!
Device MD5 Hash: Usage: su [options] [LOGIN]

Backup Data MD5 Hash: Usage: su [options] [LOGIN]

Copying EFS Backup To PC Storage... Okay.
Copied: remote object '/sdcard/EFSProBackup/EFS_2012625_0344.img' does not exist
Operation Finished!

and yea, the .tar file isn't created, an error occurs :

Checking Device Connection... Device Connected!
Checking ROOT Access... Okay.
Backing Up Device's '/efs' Folder, Please Wait...
Detected '/efs' Partition Location: Usage: su [options] [LOGIN] Options: -c, --command COMMAND pass COMMAND to the invoked shell -h, --help display this help message and exit -, -l, --login make the shell a login shell -s, --shell SHELL use SHELL instead of the default in passwd -v, --version display version number and exit -V display version code and exit. this is used almost exclusively by
Creating EFS Backup TAR Archive... Failed!
Error: Unknown!
EFS Backup Failed!
Operation Finished!
[Galaxy S II Original Android Development] lyriquidperfection:
Can you post your device info from the log please?

EDIT: This issue has now been fully resolved!!!!

Please Download the NEW EFS Pro v1.7.14 Update!
[Galaxy S II Original Android Development] gadget069:
A small donation for your hard work, confirmation # 70Y86663MC293252P
[Galaxy S II Original Android Development] lyriquidperfection:
Please Download the EFS Pro v1.7.14 Update!

This fixes an issue regarding the ChainsDD su binary that can potentially cause Backup and Restore operations to fail!
[Galaxy S II Original Android Development] teuntje3:
After the update from a few days ago back up worked, thanks!
[Galaxy S II Original Android Development] ironia.:
so busybox is required on device?
[Galaxy S II Original Android Development] lyriquidperfection:
To use all functionality of EFS Pro, yes.
[Galaxy S II Original Android Development] teuntje3:
I don't have busybox installed, does the back up I made will work?

Verstuurd van mijn Nexus S met Tapatalk
[Galaxy S II Original Android Development] lyriquidperfection:
Yes your backup will still work. I made busybox a requirement as too many people were having issues and new features require busybox to be installed anyway. So you will need to install it if you want to restore your backup. :)
[Galaxy S II Original Android Development] ironia.:
i have busybox and using the tool i can backup efs in tar format successfully

after removed busybox from the phone, i open efs backup tool and i receive the messagge that busybox is required and the tool closed itself
[Galaxy S II Original Android Development] lyriquidperfection:
Busybox needs to be installed.
[Galaxy S II Original Android Development] lyriquidperfection:
Yes thats because you removed busybox. Dont remove it from your phone, theres no need to remove busybox anyway.
[Galaxy S II Original Android Development] ironia.:
So i have TO reinstall busybox....manual? With an app?:?

The last time i installed the phone was laggy at boot

Install TO bin or xbin??