yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] xhenga:
Hey guys, I'm using Galaxy SIII GT-I9305 with latest official stock 4.3. Ever since I installed the update I had troubles connecting EFS Pro with my phone, it gets stuck on ADB initialization. I first thought it was due to outdated version of adb, because I couldn't connect to adb via cmd without the EFS Pro, but I downloaded the lastest sdk with new adb, and adb itself works, I can connect, but program is still crashing. I even copied the new adb and dlls to adb folder of the program, still no luck...any ideas on what can I do?

EDIT; Is it due to adb root failing to initialize?

D:\Phone\XDA\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>adb root

adbd cannot run as root in production builds
[Galaxy S II Original Android Development] themadba:
I'm the same as previous posters, I've tried v2.0.70 and v2.0.72 and both get stuck at initializing ADB server, even though I have .NET 4, busybox, samsung drivers, root, USB debugging and adb works (adb devices shows my i9505). So I have no idea what's going on :confused:
[Galaxy S II Original Android Development] dhangejr:
Me Too!

I am on 4.1.2

running efs pro 2.0.72...in the backup options>device filter my device (t889) is not listed

SO, I tried ***all Partitions****

It said,

"chucksum mismatch!!! DO NOT USE THIS BACKUP!!! operation failed"

if anyone can tell me which "device filter to select" or maybe how to "create new" in the "manage" section. I read else where that is hwat I need to do. And that is what I tried (create new) with the all partitions option.

It should be pretty easy based on the beautiful GUI in this app!

Thanks!
[Galaxy S II Original Android Development] xclub_101:
Hmm, I think I can confirm, it seems to be a problem with 4.3 ROMs, I also have an i9300 that has a dual-boot between Samsung 4.1.2 and Samsung 4.3 and while "adb devices" (or "adb shell") works in both systems only the 4.1.2 version seems to get past "initialing adb service".
[Galaxy S II Original Android Development] Jaistah:
EFS BAkup for Note 3. try this link i used:

http://www.xda-developers.com/android/easily-backup-the-efs-partition-on-the-samsung-galaxy-note-3/
[Galaxy S II Original Android Development] kramiel16:
thank you
[Galaxy S II Original Android Development] adnan7khan:
Samsung Galaxy S II i9100 "operation Failed"

Having this issue

Checking device connection... Device is connected!

Checking for block device: '/dev/block/mmcblk0'... Okay.

Extracting PIT from device for mapping... Skipped, already exists.

Checking backup folder location... Okay.

Backing up selected partition(s)...

EFS - read: /dev/block/mmcblk0p1 - write: efs.img... Okay.

20971520 bytes transferred in 0.179 secs (117159329 bytes/sec)

Verifying MD5 Checksum... Okay.

Device MD5 Hash: 1a6eeabb452d7ef29a500f189e0b5c3a

Backup Data MD5 Hash: 1a6eeabb452d7ef29a500f189e0b5c3a

SBL1 - read: /dev/block/mmcblk0p2 - write: Sbl.bin... Okay.

1310720 bytes transferred in 0.051 secs (25700392 bytes/sec)

Verifying MD5 Checksum... Okay.

Device MD5 Hash: ad6a2fe8d5ac597d674ec666f79620aa

Backup Data MD5 Hash: ad6a2fe8d5ac597d674ec666f79620aa

SBL2 - read: /dev/block/mmcblk0p3 - write: ...

Operation failed!
[Galaxy S II Original Android Development] lyriquidperfection:
You need to downgrade your busy box to v1.20.2.
[Galaxy S II Original Android Development] adnan7khan:
Thankx Man.. I'll Report after trying that :)
[Galaxy S II Original Android Development] kanyonkritter:
anyone have a link to efs pro that doesnt take you to all sorts of other bs like kingstranslate and livid?...i hate that fodder
[Galaxy S II Original Android Development] playermty:
can you add support for galaxy note 3 n900w8?

many thanks in advance
[Galaxy S II Original Android Development] GraphixLemz:
Support for Gt-N7100

can i use this to repair EFS, Unknown IMEI and Baseband on Gt-N7100 Indian carrier?

Pliz reply

Thank you
[Galaxy S II Original Android Development] revized:
I am going to try this one a n900t (Tim Lee mobile note 3)

I successfully used *[IMEI][efs] SAMSUNG NOTE 3 EFS BACKUP/RESTORE, and did a nandroid backup

and then I read all the post and ppl says both ways can't backup any qualcomm efs and I was like okee?

So I see something about qualcomm support in your title :D

I read I needs busybox version v1.20.2

My busy box is v.10.5

.bz2 and bz2.sign?

How does someone install these files?
[Galaxy S II Original Android Development] quebec1:
hello i installed omega rom v53 android 4.3 with busybox 1.21. i started efs pro 2.0.72m but this dosen't work.

so i changed busybox from 1.21 to 1.20.2 with busybox free but the phone has become unstable and efs has continued to not get working. certainly i have done something wrong in changing busybox

how do i change the busybox?

sorry for my english
[Galaxy S II Original Android Development] revized:
How did you change from 1.21 to 1.20.2?
[Galaxy S II Original Android Development] quebec1:
i changed with busybox free and the phone became unstable

sorry for my english
[Galaxy S II Original Android Development] JulioQc:
The tool is unable to read PIT file nor find any other partition then the EFS one (mmcblk0p21) nor create a backup of that partition, all that on my SGH-i717D... :(

Any advice? Known issue? Bug?

Checking device connection... Device is connected!
Checking for block device: '/dev/block/mmcblk0'... Okay.
Extracting PIT from device for mapping... Skipped, already exists.
Checking backup folder location... Okay.
Backing up selected partition(s)...
Creating archive: SGH-I717D_20140112_093352.tar.gz...
Operation failed!
[Galaxy S II Original Android Development] PastaBatman:
Same here. ADB can see my device, but EFS Professional 2.0.72 just sits on 'Initializing ADB server...'. I can see ADB running in task manager, but it doesn't get beyond that.
[Galaxy S II Original Android Development] djsolidsnake86:
device not connected! what do for fix this?
[Galaxy S II Original Android Development] lyriquidperfection:
With the device screen on, unplug and re plug the usb cable and accept the rsa fingerprint if you are running jellybean.
[Galaxy S II Original Android Development] starbucks2010:
The app always sit on "Initializing ADB server ...". There is no rsa fingerprint asking. Something is wrong with the app.

I'm on Win 7 64bit running as administrator with an I9505 JB 4.3.

PS. I installed Busybox 1.20.2, 1.21.2, 1.22.0 and still not passing the ADB message.

Best regards.
[Galaxy S II Original Android Development] damastah:
I'm a cell phone tech. I deal with many phones with... messed up IMEI's from people being irresponsible and messing with their phones. For example, I have a Samsung Galaxy S4 AT&T Rooted and it reads the everything just fine. Can I hit write to save the changes on the phone? Is there a risk of permanent damage? It's running 4.3
[Galaxy S II Original Android Development] d_ce:
I AM stucked here guys, i get this message

it stays like that and never change
[Galaxy S II Original Android Development] starbucks2010:
This is not working. WIll you please fix the ADB problem?

Thank you.
[Galaxy S II Original Android Development] lyriquidperfection:
Hi I have an I9505 running Android 4.3 and it works fine. The only issue I have is sometimes the fingerprint confirmation request doesn't always appear but simply unplugging and re plugging the usb cable works around this.
[Galaxy S II Original Android Development] Jdgp42:
Can I use this app to write the original IMEI that is on the sticker and box of my i9500 octa core, don't know why the imei on the phone is diferent from the one in the sticker
[Galaxy S II Original Android Development] lyriquidperfection:
No sorry it only works for writing on snapdragon based chipsets.
[Galaxy S II Original Android Development] marcel19:
hello all.

i hope this is the solution for my problem.

i have a samsung galaxy s4 GT-I9505 with android kitkat 4.4.2. when i cal *#06# i get for imei: null/null

i have downloaded the program and rooted my phone.

when i start the program and connect my phone in the usb port.

the phone ask for root acces ( i granted the root acces )

after that the program stays on:

Checking application environment... Okay.

Initializing ADB server...

can someone help me out?
[Galaxy S II Original Android Development] marcel19:
no one?
[Galaxy S II Original Android Development] cdzo72:
Reflash the LTE and GSM modems for your firmware with ODIN
[Galaxy S II Original Android Development] marcel19:
any idea where i can get those files?
[Galaxy S II Original Android Development] cdzo72:
Google Search...

If you don't have the initiative to look for those files on your own you definitely have no business rooting and modifying your phone
[Galaxy S II Original Android Development] marcel19:
i have the initiative to look for those files, the only thing i'm facing is multiply files and get them appart.

so i asked you, mayby you have a direct link.

sorry for asking.

asking makes people smarter, not dumber.
[Galaxy S II Original Android Development] cdzo72:
Dude if you can't sort out TWO (2) then you have a more serious problems... spoonfeeding slackers makes no one smarter
[Galaxy S II Original Android Development] starbucks2010:
try to search here http://xdaforums.com/showthread.php?t=2192025

take care to the new bootloaders when flashing the LTE modem

---------- Post added at 10:59 PM ---------- Previous post was at 10:57 PM ----------

do you have an idea how can I force the fingerprint confirmation request?

thank you
[Galaxy S II Original Android Development] Truckermal:
What modem can I use that works with EFS pro?? Must it be one matching the firmware as mine dont seem to work.

Cheers.

I have a GT-9505 BTW..
[Galaxy S II Original Android Development] starbucks2010:
I tried everything and is not passing the ADB checking. How can I force this fingerprint request to appear on the screen?

Thank you.
[Galaxy S II Original Android Development] dahiLLL:
Really, really Thank YOU! I have backed-up the S2(I9100) EFS partition and most important, I have successfully write my Original IMEI in the Galaxy Gio (S5660) that I have put away after losing IMEI, after installed a MIUI Rom! I ADORE YOU!
[Galaxy S II Original Android Development] Bob Simons:
another N900T user unable to get past initializing ADB server

This is a stock N900T with the de la Vega Root and everything else is normal. Win 7, 64, stock cable, it never asks for any permissions or fingerprint settings, there are only two mass storage modes and I tried both but it's at camera instead of mass storage, administrator does nothing. Is there anything that I can do?

Has it worked for anyone with a N900T with a stock recovery? I wanted a backup before changing the recovery and then installing CM11.
[Galaxy S II Original Android Development] quebec1:
hello I installed the latest rom-based omega v55 firmware xxugna5, and even in this case when I start the program efs pro hangs on written adb server initializing. What do i do?

sorry for my english
[Galaxy S II Original Android Development] Pris0n:
I'll have an SG-S3 GT I9300 and I am also stuck at the adb initializing. I already accepted the fingerprint on the phone and adb has superuser rights. Nothing happens.
[Galaxy S II Original Android Development] lyriquidperfection:
Hi everyone, I am looking into this issue to see what causes the hang but I may need some to help test with a special internal version of EFS Pro.
[Galaxy S II Original Android Development] quebec1:
What should I do to help?

sorry for my english
[Galaxy S II Original Android Development] Pris0n:
I flashed back to 4.1.2 and now your tool works. Unluckily I did not manage to restore my IMEI.

Since I got the phone used, I do not know what the former owner did to **** everything up and what was the original firmware.

If you need help with testing let me know.
[Galaxy S II Original Android Development] starbucks2010:
Just PM me with a link and I'll test it for you.
[Galaxy S II Original Android Development] rockinandroid:
new to this but mine just sits on Initializing ADB server... and does nothing else...what am i missing.....thanks for any help...
[Galaxy S II Original Android Development] Deep Nox:
sch-i800

Is there a .bin file available for my tab?
[Galaxy S II Original Android Development] Deep Nox:
Sent from galaxy tab sch-i800. cdma.
[Galaxy S II Original Android Development] Bob Simons:
Are you looking for users who get stuck at the initialization stage such as what I describe above? Do you want to contact us or have us contact you?
[Galaxy S II Original Android Development] lyriquidperfection:
Anyone having this issue if they could post here with the following info please:

* Device Model

* BusyBox Version

* Android Version

* Custom or Stock ROM

* Prompted for and confirmed RSA fingerprint request (Yes/No)

Thanks in advance.
[Galaxy S II Original Android Development] Bob Simons:
how to get busybox version number?

(a) T-Mo SG-N900T, with APN changes to use on AT&T with an unlock code and AT&T SIM

(b) don't know how to tell but Terminal Emulator shows that it is installed: whatever is installed with DLV root

(c) 4.3, N900TUVUBM17

(d) Stock but rooted with De la Vega, which is slightly modified stock(?)

(e) not prompted, just sits there at the SDB initializing prompt forever

If you can tell me a command to get the version, or do I dig around with a root explorer and get details on the file?
[Galaxy S II Original Android Development] lyriquidperfection:
The RSA fingerprint prompt should appear on your devices screen and to get the busybox version just simply type busybox in terminal emulator and you should see the version near the top.
[Galaxy S II Original Android Development] quebec1:
I have always the problem initializing adb server.....

1) galaxy s3 i9300

2) busybox version 1.22.1-stericson

3) android 4.3

4) custom rom omega v56 xxugna7

5) Prompted for and confirmed RSA fingerprint request (Yes/No) don't understud
[Galaxy S II Original Android Development] lyriquidperfection:
EFS Professional v2.0.80 has been released.

If you have been having issues with being stuck on Initializing ADB Server stage then please try this version.

If you have not confirmed your PC's RSA fingerprint on the device you will get a message on your PC saying the device is offline. If you still dont see the RSA fingerprint request on your device then unplug and re-plug the USB cable and then click OK on your PC to retry. If you still have problems then its either a driver issue or a ROM issue.

I have tested this and previous versions on my I9505 on 4.3 Jelly-Bean Stock ROM and all works okay.

Also make sure you are using BusyBox 1.20.2 otherwise you may experience issues when performing backups. Archive may fail to create depending on version.

Thank you and good day to you all! :)
[Galaxy S II Original Android Development] Bob Simons:
I now get to connecting to device...

Still nothing about fingerprints: don't even know what you're talking about.

The screen says:

Checking application environment... Okay.

Initializing ADB server... Okay.

ADB server is running!

Searching for device... Okay.

Connecting to device...

and now sits there.. three more lines than before but still dead.
[Galaxy S II Original Android Development] lyriquidperfection:
Sounds more like a driver issue if you are not getting a request on your device to confirm your PCs RSA fingerprint. If this doesn't happen then the ADB connection is simply refused.
[Galaxy S II Original Android Development] Bob Simons:
does it matter that Odin works and Kies is installed...

So how do I check for drivers? is the fingerprint process something that I do in preparation of using your software? I see something about installing an SDK but it's not clear if this on Windows or on the phone, nor what to do nor where to get it..

---------- Post added at 04:00 PM ---------- Previous post was at 03:48 PM ----------

just got a window labeled Prevention information with the following text

An application has been forced to stop for an unauthorized attempt to access system in your device. It may be safe to delete an application obtained from an unauthorized route. Check now? Cancel/OK.

---------- Post added at 04:19 PM ---------- Previous post was at 04:00 PM ----------

I don't understand this RSA fingerprint stuff at all but when I Google it I see mentions of Google's Android Studio. Is this a necessary pre-condition for using EFS Pro?
[Galaxy S II Original Android Development] lyriquidperfection:
If you are using SuperSU, make sure that she'll commands are not blocked. You would need to check in SuperSU and the RSA fingerprint stuff is an android security feature.
[Galaxy S II Original Android Development] Bob Simons:
SuperSU is set for ADB Shell to grant access

SuperSU is set correctly.

Everything I see about RSA fingerprints suggest that it only occurs with ADB set up which in turn comes from setting up the Android SDK, which you would have but I would not. Is this correct? If so, then I need to install the Android SDK which makes me hit a wall trying to set up the Java JDK. The JRE is easy. Can you tell me if I'm on the right or wrong track here?
[Galaxy S II Original Android Development] lyriquidperfection:
No basically what happens is when you connect your phone to your pc and issue ADB commands it will ask you on your device to authorise the connection from the pc. This is the RSA fingerprint prompt I am talking about.
[Galaxy S II Original Android Development] quebec1:
I tried new version and now when i stard efs i see this on the pc:

also after starting efs,on the phone I read adb shell has obtained superuser permission for an interactive shell

Checking application environment... Okay.

Initializing ADB server... Okay.

ADB server is running!

Searching for device... Okay.

Connecting to device...

this is the configuration of my phone

1) galaxy s3 i9300

2) busybox version 1.22.1-stericson

3) android 4.3

4) custom rom omega v56 xxugna7

sorry for my english
[Galaxy S II Original Android Development] Bob Simons:
installed ADB and related items but still no joy

I know this post is somewhat scrambled so I apologize in advance. It's late...

So I install the SDK and ADB and then get the fingerprint OK but immediately get a popup saying that security software has stopped an illegal action. It almost certainly is Knox judging by the filled-in icon which appears in the notification bar. The message is the same one I described earlier when I had not gotten the fingerprint message:

Window title: Prevention information with the following text

An application has been forced to stop for an unauthorized attempt to access system in your device. It may be safe to delete an application obtained from an unauthorized route. Check now? Cancel/OK.

Is the question is whether Knox can be frozen? Can you tell me if you are successful on Knox systems sometimes and if so, if you've ever been successful on T-Mo phones. On a thread that I can't recall (and can't give credit where it is due, he said this approach would never be successful because of the SELinux status of "enforcing" and not permissive. I lack the knowledge to take this any further. Does this mean anything to you? It seems to say that Knox prohibits permissive mode and this in turn causes restrictions which may be relevant? Look at the post below and let me know if it seems relevant.

https://www.xda-developers.com/android/easily-change-your-android-selinux-mode/
[Galaxy S II Original Android Development] br46:
the same for me

stop at connecting device when MTP+ADB or RMNET+DM+MODEM

at this step, all is blocked

qualcomm NV tools is running with rmnet+dm+modem

br46
[Galaxy S II Original Android Development] Deep Nox:
Any files for a galaxy tab ach-i800? I connect the tab, all goes well--checking root,adb etc. When i try to make a backup, there is no gtab available in the drop down box to populate the box on the left. Any .bin files out there?
[Galaxy S II Original Android Development] syedkamal92:
it stuck on Connecting to device... ???? whyy...
[Galaxy S II Original Android Development] Bob Simons:
much more to report but still no joy or EFS backup

Every time I tried to run EFS Pro, I'd get a security warning about an illegal process and never got the RSA Fingerprint popup so I looked to find out which unnamed application was bringing up this window. It had no name but there was a silhouette of an icon which looked like a shield. My Note 3 has two such programs, Knox and Lookout. Neither can be disabled though Android settings. Looking further the constant advice was to freeze it with Ti Backup.

I ran Titanium Backup Pro and froze everything related to Knox and to the "Lookout" malware program. See both

http://www.makeuseof.com/tag/uninstall-apps-android-phone/ and

http://tips.techzene.com/2013/11/how-to-disable-knox-security-service.html

Still no popup so I looked up RSA Fingerprint and got instrucitons about installing the ADB package. So I install the ADB windows package,

adt-bundle-windows-x86_64-20131030.

From within the ADB download, I ran the setup and I installed the various packages. from an administrator CMD window I ran the <adb devices> command and get a list of attached devices with an 8 character hex address and a name, "device." But still no popup.

So I run the command <adb kill-server> and then restart EFS Pro and then I do get the popup. I guess that's a few improvements, But EFS pro still stalls at:

Checking application environment... Okay.

Initializing ADB server... Okay.

ADB server is running!

Searching for device... Okay.

Connecting to device...

Any ideas? This thing is mighty resistant to giving up an EFS backup.
[Galaxy S II Original Android Development] terminator1983:
Thanks , for such a great program i have successfully backup my efs but now i am having problems to restore the partition bcoz when i am in the restore tab i don't see the backup that efs made in "EFSProBackup" folder i have tried to refresh it many times but still i can't see the backup i also tried to place backup in the main folder where efs is located but still no luck.
[Galaxy S II Original Android Development] Pris0n:
I flashed Archdroid for my SG I9300 today and I am also stuck at the Device not connected. There was no fingerprint question.
[Galaxy S II Original Android Development] Bob Simons:
I was successful with another tool

Which suggests that there isn't something about the Note 3 that makes it impossible. This tool has an entry for a specific N9005 version, and that one requests root and then creates a 14 MB IMG file. His regular v2 tool claims that it has root without asking for it and then creates a 512k file which obviously is no good.

Still curious why EFS Pro doesn't work. I don't know if this works to restore because I don't want to take the chance without need.

Tool here: http://xdaforums.com/showthread.php?t=2602325
[Galaxy S II Original Android Development] Egeli:
I used for s-5660 gio for imei correction. When I attempt to wnite original imei the error occurs: "Error error parsing nv item"
[Galaxy S II Original Android Development] starbucks2010:
Different messages from .72 but the same problem. I'm on Foxhound ROM v3.6 (Android 4.3 ML6) and no RSA Fingerprint request.
[Galaxy S II Original Android Development] radionerd:
SM-N900V Factory Mode

I have a SM-N900V Developer Edition that boot-looped after trying to restore from original TWRP 2.6.3.0 Backup (2.6.3.0 had an efs bug). I got the phone functioning again after finding Note 3 EFS thread from Steve Lazarus

Phone works now, but EFS folder is blank, and it's stuck in Factory Mode. This only causes a few annoyances; Cant access the power menu or the lock-screen.

Can this tool rebuild just my efs folder so I will have efs sub folders; /factoryapp, HiddenMenu, and others? I do have the original TWRP backup, which is most likely corrupted.

* SM-N900V DE

* BusyBox v1.22.0.git

* Android 4.3

* JellyBeans v6

* RSA fingerprint request No

Thanks,