yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] radionerd:
adb.exe and conhost.exe are running twice in Task Manager. I started killing the smaller instance of ADB.EXE, End process of the 900k adb.exe, then it starts to work for me. I did a complete backup, but had to end process on the smaller adb.exe at every step, about 20 times.

I also pasted the latest ADB "platform-tools" folder into EFS Professional folder. Renamed ADB folder to ADB_old, then renamed "platform-tools" to ADB. I don't know if this was required, but it worked.

I have "Android Developer appd" installed

Update: bootlopped after trying NV Backup on Qualcom tab
[Galaxy S II Original Android Development] starbucks2010:
I confirm that killing the "small" adb process let the EFS Pro starts.
[Galaxy S II Original Android Development] radionerd:
I was able to confirm on a second computer, with two phones. Had to repeatedly kill the smaller adb until it hooked, then . Tried S2 skyrocket and note 3, same behavior on both win7 pro computers..

Unfortunately I put my Note 3 into bootloops, after clicking "NV backup" on the Qualcom tab. My efs folder is now missing, My old tricks haven't recovered it yet, efs folder goes away on reboot.

Thanks,

Alan
[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.

what do i do?

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] lyriquidperfection:
Okay i am working on a new update and alot of the framework is going to be rewritten. All known bugs and issues should be ironed out. Also support will be added for all qualcomm devices. Not just samsung! How about that eh!? ☺
[Galaxy S II Original Android Development] Bob Simons:
That would be pretty slick. I bet a lot of us would be happy to hear that. Do you have an idea about what's causing the bootloops a few are mentioning?
[Galaxy S II Original Android Development] lyriquidperfection:
Not sure but the qualcomm side of my application uses standard qualcomm nv protocol so if something messes up its either samsung or qualcomm that has got an issue.
[Galaxy S II Original Android Development] radionerd:
My bad

My SM-N900V DE efs folder was already "empty" before my current misadventure. This caused an annoyance "Factory Mode" No lock screen or power menu. Now after persistent brute force killing adb in EFS Pro, I borked it up good. 2 days of Bootloops. I suspect my corruption is in mmcblk0p11, 12, or 13. I might have messed up my PIT too. I think different Note 3 models use different efs blocks. I rebuild efs folder from block12, but it doesn't stick on reboot. efs folder goes away. oden mode: e:/failed to mount efs (invalid argument)

Does anyone here have a clean PIT file for a SM-900V Developer Edition?

My sketchy read from EFS Pro was MD5 c2489a5f3448062832484b9ac8936cab (only 3856bybes) before I broke it.

I found the stock HLTE_USA_VZW_32G.PIT, not sure if it's same for DE MD5 cc7da3a79307599a34a5492b676bba0b (4112bites).

Thanks
[Galaxy S II Original Android Development] ephidor:
I have backed up my phone and have a tar file saved

How do I go about restoring this ?, the phone is running 4.1.2 and is rooted

do I need to re flash a rom after restoring ?
[Galaxy S II Original Android Development] kirokko:
Hello! I'm sorry because some of my question may be very simple and primitive, but it's my first Samsung device so some question are very hard to find even if read a lot already.

* Model: Samsung Galaxy Tab 3 8.0 SM-T310 16GB

* BusyBox: 1.20.2-stericson (beacuse this version was recomended by EFS Pro app)

* Android: 4.2.2

* ROM: Stock

* Prompted for and confirmed RSA fingerprint request: Yes

I can't find instruction which partitions I need to backup. Do I need to make my own Device Filter list? I selected from Device List "*** All Partitions ***" and it's about 10 partitions in the list. Do I need to backup only EFS or something else?

Also, it there an instruction how to make my own Device Filter? I didn't find any guide.

Thanks for any help!
[Galaxy S II Original Android Development] ephidor:
on filter list you click the phone that you are backing up

ie i9300 international
[Galaxy S II Original Android Development] kirokko:
But there's no my phone/tablet in the list. I have Galaxy Tab 3 8.0 as I described earlier.
[Galaxy S II Original Android Development] syrisara:
+1

Rooted

Stock 4.3

Latest Busybox

I9300 int.

Hangs at connecting to device, killed all apps on phone, small adb.exe trick not working.
[Galaxy S II Original Android Development] emmanueldmc:
The same for me...i have a s4 i337m with 4.3 official, and rooted 0x0, ...i don´t know why this happens, a few months ago i had a Note 3 ... and this tool worked well with android 4.3 :(
[Galaxy S II Original Android Development] radionerd:
Still trying to recover SM-N900V brick. I found my EFS Blocks were in a sub folder of "/dev/block":

/dev/block/platform/msm_sdcc.1/mmcblk0pXX

Since it is encrypted I can't just move them into /dev/block/mmcblk0pXX

Looking for a way to move them and make them stick.

Edit: I guess I don't need to put "/platform/msm_sdcc.1" in. I was able to send 11, 12, and 13 to ext_SD

adb shell
su
dd if=/dev/block/mmcblk0p11 of=/storage/sdcard1/mmcblk0p11
dd if=/dev/block/mmcblk0p12 of=/storage/sdcard1/mmcblk0p12
dd if=/dev/block/mmcblk0p13 of=/storage/sdcard1/mmcblk0p13

mmcblk0p11 14MB Edit: This is Developer Edition's EFS)

mmcblk0p12 3MB

mmcblk0p13 3MB

efs folder is gone, and I can't figure out how to rebuild it ??? Edit: Found it, now trying to make it stick after reboot. EFS folder disappears on reboot. Also got conformation that the PIT file is same for VZW retail and Developer Edition
[Galaxy S II Original Android Development] terminator1983:
Can someone share nvitmes of Samsung S4 i9505 without imei.

Thanks
[Galaxy S II Original Android Development] radionerd:
Bad Magic number

I let the magic out on /mmcblk0p13

~ # e2fsck -n /dev/block/mmcblk0p13
e2fsck 1.41.14 (22-Dec-2010)
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/block/mmcblk0p13

The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>

~ # e2fsck -n /dev/block/mmcblk0p11
e2fsck -n /dev/block/mmcblk0p11
e2fsck 1.41.14 (22-Dec-2010)
/dev/block/mmcblk0p11: clean, 11/3584 files, 581/14336 blocks

~ # e2fsck -n /dev/block/mmcblk0p12
e2fsck -n /dev/block/mmcblk0p12
e2fsck 1.41.14 (22-Dec-2010)
/dev/block/mmcblk0p12: clean, 11/768 files, 126/3072 blocks
[Galaxy S II Original Android Development] rtrotsky:
when i plug my phone i get stuck in "connecting device". my i9300 is rooted and usb debugging is enabled. nothing shows up on the phone asking to let efs do anything. am i missing something?

edit1. i was using archidroid 2.3.6. i think there was some incompatibility. after i flashed an original samsung firmware, efs detected my phone. i will try to find out the problem, since i need to use efs with custom roms.
[Galaxy S II Original Android Development] M@zik:
Stuck at "connecting to device"

I am trying it on Galaxy Note GT-N7000 running Omni ROM @ Android 4.4.2 and Windows 8.1 x64.

Thanks
[Galaxy S II Original Android Development] marv101:
I'm also stuck at "connecting to device"
[Galaxy S II Original Android Development] dead soul:
Extract IMEI alone

Hi, my phone was stolen and i want law enforcement to track it down. but i didnt record my IMEI and my original box/receipt are kinda misplaced/missing

the only way to know my IMEI i believe is through the EFS folder ?? how can i extract it ? or is there any suggestion u guys might hjave i could find out my IMEI ? from a backed up ROM maybe ? or a common cloud service would display my IMEI ??

need help urgently !!
[Galaxy S II Original Android Development] ermacwins:
I got a S3 with 4.3 stock rom and want to flash an aosp 4.4.2 based rom. I take it this tools can backup the efs folder, but first it needs to be rooted?
[Galaxy S II Original Android Development] lyriquidperfection:
Okay guys, I have managed to find out what was causing the connection issues on various devices with EFS Professional. Its due to a very unstable adb shell function implementation that I used for checking root. I have now removed this function and moved over to a more reliable implementation. After some more testing, I will release the update in due course. Hang tight folks!
[Galaxy S II Original Android Development] lyriquidperfection:
EFS Professional v2.0.91 has now been released!

Issues surrounding users being unable to connect or EFS Pro hanging on initialization have now been resolved.

Enjoy! :)
[Galaxy S II Original Android Development] Zombii:
I'm getting a problem where my phone is not showing up in the COM Ports list, and I am therefore unable to use the Qualcomm tools. I believe it's because my phone is not in diag mode, however, I am unable to enter diag mode through any of the phone menus, as my phone appears to simply not have them, I believe they may have somehow been lost when my IMEI got wiped.

Is there any way to entire diag mode without the PhoneUtil/HiddenMenu?
[Galaxy S II Original Android Development] lyriquidperfection:
Yes you can change phone mode on the Qualcomm tab from the mode list.
[Galaxy S II Original Android Development] Zombii:
Per your advice, I changed USB mode to DIAG+MODEM+ADB, EFS gave me a "Switched to 'DIAG+MODEM+ADB' successfully!' message, but then when I launch Qualcomm Tools it still does not appear in the COM ports list, and it doesn't appear in QPST either.
[Galaxy S II Original Android Development] lyriquidperfection:
Are your USB drivers installed correctly?
[Galaxy S II Original Android Development] Zombii:
I'm assuming they are, I can transfer files back and forth fine, and the computer is recognizing the phone, adb works as well.

EDIT: It was a USB port problem, it is being detected on another computer. However, now I get a Microsoft Runtime Error when trying to connect. Will update .NET Framework and report back.

Nope, that wasn't the issue. Here's the error:

It also looks like there's a smaller dialog box underneath the .NET Framework error, but I can't interact with it because the .NET Framework error is forcing itself on top of other windows and refuses to be interacted with. In addition, the Qualcomm Tools window says it has successfully connected, but I can't interact with it.
[Galaxy S II Original Android Development] radionerd:
I can connect, and read my SM-N900V DE. Only hitch so far is the SD storage folder is sdcard0 or sdcard1 on my Note 3.

Any way to change save location?

Edit: The program popup reports it can't save, but the save is in "sdcard" folder.

Thanks
[Galaxy S II Original Android Development] Zombii:
An update to my own story: I don't get the error when I de-tick "Send SPC", however, if I leave "Read phone" checked, then I get a "Lost connection to device!" message as soon as it connects. If I don't check either box, then it works fine, but when I attempt to write my IMEI, it gives me both a "Connection to device lost!" and "Successfully wrote IMEI!" messages, but it does not write my IMEI successfully, my phone still reads as unknown (after a reboot, yes).
[Galaxy S II Original Android Development] quebec1:
now the program it's ok when j star efspro i read:

Checking application environment...

Initializing ADB server... Okay.

ADB server is running!

Searching for device... Okay.

Connecting to device... Okay.

Checking device status... Okay.

-----------------------------------

Performing device checks...

-----------------------------------

Root status: Perm Rooted

SU binary version: 1.93:SUPERSU

-----------------------------------

BusyBox present: True

BusyBox binary version: 1.22.1-Stericson

-----------------------------------

EFS Professional is ready for use.

-----------------------------------

But the program tell me to downgrade busybox to 1.20.2

now i have installed on the phone omega rom v56 and the rom is deodexed + rooted + zipaligned and i want to know:

1) why do I have to downgrade?

2) how do you downgrade the busybox?

3) if I do the backup with busybox that I currently have on the cell what happens?

sorry for my english
[Galaxy S II Original Android Development] jamesd1085:
I have a vzw galaxy s4...imei and all services are good...but I have factory mode problems...my efs folder is completely empty and can't edit files that are supposed to be there...will this tool fix this and can I get a bit of help getting through this...I'm worried I could make the situation worse seeing as this is new to me
[Galaxy S II Original Android Development] TweeMee:
I'm trying to restore my IMEI with Qualcomm NV Tools but it doesn't recognize my phone as COM Port.

My Phone is a european GT-I9300. Can someone help me? :crying::confused::rolleyes:
[Galaxy S II Original Android Development] lyriquidperfection:
Let me put you out of your misery. The I9300 is an exynos based device not Qualcomm so you would need to back up the /efs partition instead.
[Galaxy S II Original Android Development] Zibri:
Do you know that EFS can be read using qualcomm subsys commands too?

You could use that to do a backup of non rooted phones.

Just my 2c.
[Galaxy S II Original Android Development] salluhassan:
Hey lyriquid,

Hi again, i just bought samsung galaxy s3 but korean s3 with model as shv-e210s from SK telecom .with the following specs, and with exynos processor and LTE , can i back up using your latest EFS_Professional_2.0.91_Release , please guide me properly because i already lost pantech vega r3 having unknown baseband and imei . Can you make steps in your thread http://xdaforums.com/gala...ional-t1308546 , please clearly mention that its only for rooted phone, well for my phone i may have the CF-autoroot method for rooting, will it create problems? please help me

- quad-core Samsung Exynos 4412 with CPU clocked @ 1.4GHz

- 2GB of RAM

- 4.8-inch Super AMOLED HD screen

- 4.82 ounces (136.5 grams)

- 0.35 inches (9mm)

Thanks lyriquid perfection
[Galaxy S II Original Android Development] robert1030:
My Device is SM-N9005 (Note3 LTE version)

Product Code is XME

Rom version:N9005XXUDMJ7

I don't see this comment: "NV Backup and NV Restore options to utilise Samsung's built in 'reboot nvbackup' and 'reboot nvrestore' functions. (Intended for US device variants only)."

So I use "NV Backup" of EFS Professional v2.0.91 on my SM-N9005. My N9005 become "lose basedband" "lose IMEI information", and it will auto reboot after boot completly.

How can I do? let my SM-N9005 can return to normal, Thanks a lot.

I have use EFS Professional v2.0.91 backup modemst1, modemst2, efs.img.ext4 of my SM-N9005.
[Galaxy S II Original Android Development] insanehadi:
Bro please I need your help I used your tool I clicked qualcomm nv backup .. my phone restarted and now I am left with no signal! I tried restarting my phone and restoring via NV restore but still nothing please help me !

NOTE LTE Variant
[Galaxy S II Original Android Development] radionerd:
I did the same thing

That's how i screwed mine up too. Clicked on Qualcomm NV backup, SM-N900V DE immediately rebooted into bootloops.

I thought I was just backing NV up. I think the program might have send the command "NV reboot" instead. IMEI is missing.
[Galaxy S II Original Android Development] insanehadi:
Were you able to fix it ?
[Galaxy S II Original Android Development] lyriquidperfection:
You need to be very careful with the options you use. Its recommended to always use the Qualcomm NV Tools interface for qualcomm based devices and backup the nv items.
[Galaxy S II Original Android Development] insanehadi:
is that all you have to say? How about help all the users who lost their imeis and basebands using this tool? that would be nice
[Galaxy S II Original Android Development] lyriquidperfection:
Samsung are always moving the goalposts and changing things with every device that comes out. More than 2 years have gone into making this including updates. There are lots of warnings in this app and you should be careful which functiins you use.

The buttons on the right of the qualcomm tab that are for samsung US device variants simply issue the commands 'reboot nvbackup' or 'reboot nvrestore'. As I cannot test on all physical devices it makes it harder to implement things properly for all devices as sometimes im purely relying on research. As far as im aware the above commands backup from fsg to backup prtition and restore from backup to fsg partition. Samsung may have changed this on the Note 3 however. I am already looking into this and im working to figure out what is causing the loss of IMEI.
[Galaxy S II Original Android Development] Klaus4:
is it possible to repair i9505 Imei and SN cause ist damaged? sorry for not reading all the Posts

Thanks

Klaus

Keep on this good work
[Galaxy S II Original Android Development] radionerd:
I've been trying to restore IMEI for over a month, then I sent it to Samsung, they found KNOX flag trip. Their policy is if it has been rooted it is "Not economical to repair". I should have my broken $750 developer device back tomorrow.

Try to backup all your mounts so you don't get stuck with it worse while trying to repair. In the last month I have made it worse, then recovered back to here.

Search; "reboot nvbackup" I think this is what happened to our phones.

I will be updating my thread when I get the phone back. http://xdaforums.com/showthread.php?t=2657519
[Galaxy S II Original Android Development] en11gma:
i just tried to use the backup feature on my us cellular note 3 SM-N900R4 with android 4.4.2 stock touchwiz rom.

i selected the top settings that selects all partitions (25 i think)

it kept having problems where it couldnt write on some of the partitions so i would re-run the backup with the check mark UN-Checked on the ones i had problems with.

probably took about 10 attempts of hitting backup (each time having to uncheck a different box but i did get it to complete)

i then went to try to qualcom nv tools but it kept saying my spc of 000000 was incorrect.

turns out i really got some major problems

someone probably knows what i got going on here.

i can boot up but i stuck at activation screen ( i did factory data reset and ##768#) and i even odin over the stock NAB (android 4.4.2) again but i got major problems.

if someone can please help me out i would appreciate it

thanks

i can make it past the activation screen but if i do anything in dialpad that wants my SPC when i enter 000000 it dont do anything

it dont tell me its wrong or incorrect or anything.

i can hit ok 1000 times at the 000000 box but it dont do anything

i am root

should i try to "restore" the backup i made?

in dfs cdma tools port box it is showing my device name as "[]" and device id "00000000"

just read ""reboot nvbackup" I think this is what happened to our phones."

yep i did that too

so that is where it went wrong?

do we restore the backup we made with efs prof?

my backup was not smooth. i kept having to do it over and over until i cleared the checkmarks where it was hanging

when i goto try to restore it copies the 5GB file to device ok but it cant restore because there is no partitions i can select for it to restore too.

re-installed busybox

---------- Hardware Information ----------

Connected Device SN.: 746e5dca

Device Manufacturer: SAMSUNG

Device Model: SM-N900R4

Product Code: Unknown

Hardware Version: Unknown

---------- Firmware Information ----------

PDA Version: N900R4TYUCNAB

Baseband Version: Unknown

CSC Version: N900R4USCCNAB

---------- Software Information ----------

Kernel Release: 3.4.0-447319

Kernel Version: #1 SMP PREEMPT Tue Jan 28 20:32:28 KST 2014

ROM Build: hlteusc-user 4.4.2 KOT49H N900R4TYUCNAB release-keys

Android Version: 4.4.2

BusyBox Version: 1.22.1-Stericson

SU Binary Version: 1.93:SUPERSU

i can now see all the partitions that i created before i did the nv backup where it rebooted and messed things up.

what do i do at this point?

any info would be great help
[Galaxy S II Original Android Development] en11gma:
"NV Backup" option on SM-N900R4

what exactly does that do?

how can it mess it up if it is only reading the nv?

my phone i dont think is to messed up (well at least i hope)

anyone here that can help me locate what went wrong?

i have my /efs copied to my desktop (used dfs cdma tools) efs tab (read efs2) and highlight / and select save

can i just copy that to an sd card and then use es file manager to copy that dir over the old corrupt /efs directory?

or

since i backed up all the partitions that i could with efs pro 2.0.91 can i just restore the partition that got corrupted when i ran nv backup option when phone rebooted?
[Galaxy S II Original Android Development] en11gma:
SM-N900R4 (cdma Note 3) Android 4.4.2 Official Stock Rom

Rooted and SuperSU

i was set to NV_Only

i then used EFS Pro 2.0.91 to backup all 25 partitions (tried too)

sometimes it would stop on some partitions so i would uncheck the partition it stopped on and re-run the backup again

there were probably close to 8-10 times where i had to uncheck a partition and re-run but it did finally make a backup

AFTER THAT i then tried to do a NV_Backup (not with qualcom tools) and phone rebooted

i did not have the constant rebooting because i was set to NV_Only Subscription mode. not RUIM/SIM like most of you.

i then odin over the NAB (android 4.4.2) stock touchwiz rom from samsung and this will reboot at the Activation Screen if it does not activate

which it will not as this phone had bad esn with us cellular

so i then RESTORED my TWRP Backup of the same stock touchwiz (rooted and supersu) that i had right before i used efs pro 2.0.91

which was set to NV_Only Subscription mode so i do not reboot anymore

i put phone in airplane mode

i can use wifi ok

ok so anyhow

i did not WRITE anything with EFS Pro 2.0.91

i did NOT RESTORE anything

is there a way to fix this since i do have a backup of some of the partitions that i made BEFORE i used nv backup?

i extracted the backup file that was created so i could look at what got backed up with efs pro 2.0.91

some of the files do not look like the correct size.

can i restore and of the partitions?

if so which partitions should i be looking at to restore?

i do not want to restore all the partitions unless i have to.

i can help troubleshoot if you want

thanks

can provide screenshots id you want but this should not be to hard to figure out.

i never wrote anything and only did backups

thanks again

just checked and my BT and WIFI both work fine

also checked my /efs directory to a copy i had made before and its the same. as far as files in it.

havent done any md5 checks or anything