yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] radionerd:
Glad your making headway!

I had the same experience with my note 3. "NV backup" did the same to my SM-N900V DE: ESN 7EA13701 MEID unknown. PRL version Unknown.

Clicked "NV Backup" and screen goes black then Quick flash of 2 blue lines of text at the top of the screen, and bootloops to follow. Looking at the flash of text it looks like line one of blue text says "copy mmcblk0p11 to FSG". FSG is the "Golden" copy of EFS.

In my case, mmcblk0p11 had been corrupted a few months earlier by doing a restore with TWRP. The phone worked OK, just stuck in "factory mode". So I think "NV Backup" wrote my corrupt block 11 into FSG. I can't read line 2 of blue text but it did copy mmcblk0p12 to ???.

Maybe OP could chime in, I wonder if you had a good copy of your FSG (maybe mmcblk0p18 on your phone 14MB) you might be able to "dd" it back into your phone, then "NV restore"? (Hope that wasn't the block you couldn't backup).

I have been comparing the blocks in HxD hex editor with a know good phone, and my old backups. I look at: mmcblk0p11, 12 ,13 and FSG 18 (don't know if your PIT is the same though).
[Galaxy S II Original Android Development] exwan:
i cant do a backup with your newest vesion. im on Kit kat rom. tried reinstalling busybox to your suggested version. still give me the same error.

archive failed.

s3 mini.
[Galaxy S II Original Android Development] lyriquidperfection:
EFS Professional v2.0.103 has now been released!

reboot nvbackup and reboot nvrestore functions have now been removed as this actually breaks newer Samsung devices.

support for backup and restore of 'fsg' and 'backup' partitions on Qualcomm devices has now been implemented and is recommended to include these in your backup.
[Galaxy S II Original Android Development] en11gma:
yea thanks for using us as beta testers for your software

when we clicked the (non qualcom) "nv backup" option in EFS Pro 2.0.91 on our CDMA/LTE Note's can you tell us exactly what happened?

are our devices completely ruined now?

is there any way we can fix them?

thanks and i hope you understand we are not very happy with the 1st post when you say it works with Note 3's

you really need to make the text alot bigger and put BREAKS CDMA/LTE Note 3's and other devices that you might want to add

any app that can totally leave you in a bricked state really needs a bigger and i mean BIGGER Warning

thanks again and please dont leave us hanging

you are the developer of this app so you know whats going on
[Galaxy S II Original Android Development] banziitox24:
Hey PLEASE PLEASE HELP ME I'm having this error when I hit connect to the device it shows me this error ''Public member 'TransmitData' on type 'CommandQueue' not found. Don't know how to fix it and i need to return this to the client today, I'm trying to write original IMEI because i restored a qnc file from a good device to fix a call problem when you unlock them.

Device: Galaxy Mega I527 AT&T

Version: 4.2.2

SELinux : Permissive

Baseband: I527UCUAMK2
[Galaxy S II Original Android Development] en11gma:
i was in NV_Only mode when i ran you full backup of the 25 partitions it auto detected which it did not let me back them all up

the important ones /fsg and /fcg were not backed up

that is not the area (to my understanding) that messes up our phones

it was when i then clicked "NV BACKUP" (not the qualcom one)

what exactly does your program do when you hit NV BACKUP
[Galaxy S II Original Android Development] ankiboy:
Hi I'm a little lost too

though this may not strictly pertain to no GS3 instruments but is there a similar solution for GS1 i9003 phone.. I have a no nv phone lying for past one year coz Ive been told the only way round is to get the motherboard changed..

Thanks in advance. :good:
[Galaxy S II Original Android Development] lyriquidperfection:
EFS Professional v2.0.104 has been released!

Qualcomm NV Tools is now working again!
[Galaxy S II Original Android Development] xmyszka:
Still can not repair imei on i9505 :( !!!

When i ckilck on write my original imei:

"Error Parsing NV Item"

than...

"Error decoding command output! "

...and imei is not writen :(

????
[Galaxy S II Original Android Development] lyriquidperfection:
Sounds like that NV item is not writable. Have you sent the SPC? It may require further privledges but I would have to look into that.
[Galaxy S II Original Android Development] xmyszka:
Yes i sent the SPC... :(

I have root acces with SuperSU v1.93 and newest custom recovery philz_touch_6.15.4 and stock firmware rom i9505XXUFNB8

Maby i must frash custom rom like Omega or WanamLite... ?
[Galaxy S II Original Android Development] lyriquidperfection:
You may need 16 digit password if it is a cdma device but thats not yet implemented into efs pro.
[Galaxy S II Original Android Development] xmyszka:
It is standard European LTE Galaxy S4 i9505 model.

I repaired Note 3 N9005 standard European LTE android 4.4.2 without any problems but this Galaxy S4 i can not repair :( Read is no problem but Write make errors. Maby i must downgrade modem ... ? I repaired another device i9505 but with rom 4.3 not new 4.4.2
[Galaxy S II Original Android Development] DF5JT:
"IMEI written successfully"

I had so hoped that this would be the solution for my 0 IMEI problem that I evenwent through the pain of booting Windows XP.

Got the tool running, the phone connected and NV Tools gave me the option of writing the IMEI that is behind the battery.

It said "IMEI written successfully", clicked OK twice, rebooted - and my IMEI was still 0.

I guess my phone (I9505) is a brick, right?
[Galaxy S II Original Android Development] banziitox24:
N900A

Have you tried this tool or someone to repair IMEI on Note 3 N900A
[Galaxy S II Original Android Development] radionerd:
Samsung's reboot NVbackup toxic command

I lost my IMEI after sending command "reboot nvbackup" over 6 weeks ago. I was able to get everything working again today after restoring FSG, and empty backup mounts.

I will do a more detailed writeup in my thread, link below. This problem effects some of the latest Note 3's. Mine is a verizon model SM-N900V Developer device. A friend of mine bought a DE and sent me his FSG and backup partitions. (mmblk0p17 and 18 on my phone) I could not find any of his data in the folders, and backup was empty. My FSG was corrupted with efs backup, so I simply put them into my /dev/block/ folder replacing the overwritten corrupt ones. I didn't even have to reboot, the MEID, PRL, and MIN all showed up in my status screen.

This is a specific problem caused by performing "reboot nvbackup" on newer Samsung phones that use FSG differently. For those that entered this command and there phone immediately rebooted into endless boot loops this procedure might work to get your IMEI back too. I am guessing that the Verizon note 3 FSG is the same for all Verizon note3's. Clean FSG MD5 221daabe2e089699626e4b22606ad621

I will be updating more info here: http://xdaforums.com/showthread.php?t=2657519
[Galaxy S II Original Android Development] lyriquidperfection:
Good find! This will help alot of people get their phones back to normal. I spent a few hours on IRC the other night trying to help en1gma get his note 3 back by dd the partitions.

I always understood that the efs structure was contained in modemst1 and modemst2 partitions amd the fsg partition was the golden backup of efs. This could be a clean template efs thats copied to the above 2 partitions then modified somehow for each specific phone. If thats the case, then fsg could possibly be the same for all devices.

I encountered a similar problem back on the S3 snapdragon where users had a zero imei which turned out to be a corrupt param partition. As this was the same for all devices, I uploaded my working copy as an Odin flashable package and voilla, their imei was back!
[Galaxy S II Original Android Development] en11gma:
i just wanted to tell everyone that lyriquidperfection spent alot of time with me trying to fix this problem 2 or 3 nights ago i forget.

he did actually take his time out and one on one with me for a good hour at least

we didnt make to much progress and i actually put my phone up on ebay and someone bought it for $290

i was going to ship it off in the morning

it was all factory reset and boxed up

then i seen i had a message from radionerd saying that he fixed his phone

i immediately asked for help and explained my urgency

check out his thread here on how to fix!

http://xdaforums.com/showthread.php?t=2657519

i now have my imei and meid back

omg i still got to tell the guy who bought my phone i cant send it

hope he dont leave my bad feedback and understands
[Galaxy S II Original Android Development] Masami1975:
please on a Note 3 N9005 efs backup will save also IMEI? Thank you!
[Galaxy S II Original Android Development] lyriquidperfection:
Yes as long as you include modemst1, modemst2, fsg and backup partitions.
[Galaxy S II Original Android Development] banziitox24:
Hi i tried to use thr Qualcomm NV Tool for a Note 3 N900A ATT and when i try to write IMEI to device a window opens with a lot of numbers firts are 26 something and then is a bunch of zeros after that says Parsing NV failed what can that be?
[Galaxy S II Original Android Development] lyriquidperfection:
Can you send me a screenshot?
[Galaxy S II Original Android Development] banziitox24:
Here's the screenshot of the first thing that pop ups and it's when i hit connect(EFS Error) second is when i hit write to device(NV Parsing Error) and the third when i hit ok on the NV Parsing error
[Galaxy S II Original Android Development] zetlorf:
Hi, i need a big help:

i lost my imei trying to flash modems forth and back.

On other topic, lyriquidperfection tell me that i need a working FSG and backup partitions (i have a saved efs & modem partition with other tool.)

So, can someone send me his good FSG and backup partitions for N9005?

Thanks in advance.
[Galaxy S II Original Android Development] radionerd:
Post your MD5 Sum from mmblk0p18. EFS Pro will display the MD5 as you backup.

I have a thread about this fix, but we need to verify that FSG is actually corrupt before throwing partitions at it blindly.
[Galaxy S II Original Android Development] banziitox24:
Can you help me with this problem
[Galaxy S II Original Android Development] zetlorf:
Hi,

my MD5 for mmcblk0p18: ff358c73c88f25c01c2c53199bbcbff8.
[Galaxy S II Original Android Development] lyriquidperfection:
EFS Professional v2.0.110 has been released!

Bug fix update.
[Galaxy S II Original Android Development] banziitox24:
What bug fixes? The error problem that show to you? Or another thing
[Galaxy S II Original Android Development] lyriquidperfection:
Those were other bugs. The problem you are having with the error parsing nv item is not a bug.
[Galaxy S II Original Android Development] banziitox24:
Oh alright and can you help me fix it I will really appreciate it and other user that may have the same problem that I have
[Galaxy S II Original Android Development] lyriquidperfection:
Are you running stock or custom rom?
[Galaxy S II Original Android Development] banziitox24:
Yes complete stock rom and rooted version 4.3
[Galaxy S II Original Android Development] Klaus20:
solved

My Problem is solved.
[Galaxy S II Original Android Development] simo_scorpion:
hello

i8262 supported
[Galaxy S II Original Android Development] xmyszka:
Hi

I repaired IMEI on S4 i9505 with rom 4.4.2 by downgrading modem to XXUBMGA and then use EFS Pro than normal upgrade modem to XXUFNB8...

Thanx lyriquidperfection :)
[Galaxy S II Original Android Development] banziitox24:
On what device you did the IMEI repair by downgrading the modem?
[Galaxy S II Original Android Development] someonexh:
So after hours of searching and coming up to this thread which included about another hour of installing things along with rooting a phone I just purchased....

I am trying to modify the IMEI code. The phone I purchased is blacklisted (without my knowledge) and I have a working (older 4g) phone that I would like to use that IMEI and flash it to this Galaxy S4 I just purchased. IS this possible? I have the Qualcomm NV Tools connected to the phone when I click Connect I have to uncheck "Send SPC" in order for it to actually connect. When I do Read IMEI from Device it's always 0000000000000000 which I am not sure why... read SPC and Read Lock Code come up with things so it definitely seems like it's connected....

anyways, I type in the IMEI code I want the phone to use and click Write To:device "Write" it pops up a box and says write successful twice.... on reboot the IMEI is still the old one. Is this possible to do?

Thanks in advance...

phone is a Galaxy S4 Verizon I545VRUEMK2
[Galaxy S II Original Android Development] FlanjeUK:
Who, what, where, why, when, how... doesn't matter. Good luck
[Galaxy S II Original Android Development] exwan:
still getting the same error with latest version.

unable to create archive. im on 4.4.2 carbon rom s3 mini.
[Galaxy S II Original Android Development] lyriquidperfection:
Change your busybox version to 1.20.2 as there are problems with the tar applet on later versions of busybox which make the archive fail to create in EFS Professional.
[Galaxy S II Original Android Development] exwan:
Im am using 1.20.2, i dont know what else is the problem.
[Galaxy S II Original Android Development] lyriquidperfection:
What are the mount locations for your phones storage? Do you have a /sdcard folder on your device?
[Galaxy S II Original Android Development] exwan:
Yes i do have /sdcard folder.

I dont have big understanding on android. But here is a screenshot of my folder. And when the first time i use the software. It says unable to read pit file. Then i clear log, tried to backup again. The error change to unable to write.
[Galaxy S II Original Android Development] lyriquidperfection:
Are you trying to back up all partitions or just efs? If you try to backup all it may cause you to run out of space.
[Galaxy S II Original Android Development] exwan:
Only efs. The error was unable to create archive. All i did was select the default block available in the program.
[Galaxy S II Original Android Development] lyriquidperfection:
What build of busybox do you have? Is it the stericsson build or another build? Should tell you in efs pro under the device info.
[Galaxy S II Original Android Development] exwan:
I tried jrummy busybox which stated cm9. Then i tried strericson. But unfortunately, i use free version and could only have 1.22.1 install.

Is it because of the pit file? In the efs pro folder in my desktop. It is only 5kb. I think the program did not pull full pit file?
[Galaxy S II Original Android Development] lyriquidperfection:
Ah right, I will improve compatibility with latest busybox in next release.
[Galaxy S II Original Android Development] exwan:
Thank you. So that means it has nothing to do with the pit file? Looks to me like it werent full copied of pit file with only 5kb size. Im sorry if im talking nonsense.
[Galaxy S II Original Android Development] salluhassan:
liquid perfection, i need source code of this to make it a little bit efficient regarding backups of /dev/block/mmcblk0p3 for my own learning of this and hey bro it took almost an hour to get this response but in the end it says md5 checksum error as shown in these attached pic, i use busy box pro, should i uncheck this md5 checksum? but why it took almost an hour to read and write ?, i am using proxyme cooked in the stock rom for rooting purpose. yeah you are right it ran out of space too for backing up all partitions even though i have 23 GB free usage but in sdcard0.what options should i select?, its an LTE Phone but what can you say international or not? its from skt telecom. i am using korean variant of galaxy s3 that is shv-e210s with 32GB storage.
[Galaxy S II Original Android Development] lyriquidperfection:
You will fail on the MD5 as the system is live while you are backing up so data and system will change. You need to run the backup while in recovery mode to avoid the error.
[Galaxy S II Original Android Development] salluhassan:
how can i do that in recovery, ? see the attached picture . i cannot do that even though apply update from adb shell commands
[Galaxy S II Original Android Development] KrAzYtHeBoY:
Support to SM-G900F in next update? galaxy s5
[Galaxy S II Original Android Development] lyriquidperfection:
Will support it anyway!
[Galaxy S II Original Android Development] KrAzYtHeBoY:
In select device model select "internatiomal lte variants"? For work on g900F?

Enviado desde mi GT-I9505 mediante Tapatalk
[Galaxy S II Original Android Development] lyriquidperfection:
EFS Professional v2.1.5 has now been released!

BIG Update!

See first page in this thread for more details!
[Galaxy S II Original Android Development] Bringer1:
Same question for me.

I have used the Backup Options: ***all Partitions*** and start to make a backup.

But there is no option to make/save the Backup on my Computer. On Phone, I have only 8GB free and this is not enough to make a Backup with all Device-Partitions.

Makes me angry...

Please make it possible to save the Backup directly to my PC (or to the Sd-Card).
[Galaxy S II Original Android Development] lyriquidperfection:
This is not possible as the backups must be made on the device first then copied to the pc.
[Galaxy S II Original Android Development] Bringer1:
Ok. And can you make it possible to save the Backup to the ext.SD ?
[Galaxy S II Original Android Development] lyriquidperfection:
Yes I will add this in the next release.
[Galaxy S II Original Android Development] lyriquidperfection:
EFS Professional v2.1.8 has now been released!

Now you can specify your own device storage path for backup of partitions! This means you can now use external storage rather than just being restricted to internal storage if you don't have enough free space available.

Enjoy!
[Galaxy S II Original Android Development] lyriquidperfection:
Could someone please confirm if busybox versions newer than 1.20.2 now work correctly. Thanks in advance.
[Galaxy S II Original Android Development] ausduckz:
I've performed a backup of the /efs partition, but the program seems to be hanging at the stage "Creating EFS Backup Parition Image..."

Should I just leave it and see if something happens, or close the program?

EDIT: Well I ended up force closing the program, and I checked my sdcard, and the backup was there. Whether it was complete, I'm guessing not, as I force closed the program. Just 1 question though. Typically, how big is the /efs partition? As I checked the details of the backup before deleting it off my sdcard, and it was 2.8GB.
[Galaxy S II Original Android Development] Jade Eyed Wolf:
Is it possible with this tool to swap IMEI's from two devices? Say, swap the IMEI of my Note fir the IMEI of my SGS2? Or will this just case the corrupted IMEI to show on both devices?
[Galaxy S II Original Android Development] kxnzxmori:
Img file should be around 20+mb. And tar file around 5+mb.
[Galaxy S II Original Android Development] ratcom:
wonder if this program would work for the galaxy nexus ;)
[Galaxy S II Original Android Development] lyriquidperfection:
Dont see why not because samsung uses the same folder structure. :)
[Galaxy S II Original Android Development] akashsgpgi:
i want to try it but im confused that in which mode do i connect my GTi9003 ?

in kies mode?
[Galaxy S II Original Android Development] lyriquidperfection:
No you need to connect your device with USB debugging enabled. This stops the device from connecting in Kies mode. Hope this helps. :)
[Galaxy S II Original Android Development] mjbri0613:
i have i9003 and back it up through adb can i use this to restore my imei?

do i need to flash back to froyo where i created the /efs back up?
[Galaxy S II Original Android Development] justinblaine23:
Anybody know if this will work on the Att version?
[Galaxy S II Original Android Development] nitinvaid:
Stuck at creating efs backup
[Galaxy S II Original Android Development] zrzhu:
thanks. This is great!
[Galaxy S II Original Android Development] bcatlock:
program stuck after clicking backup button,with backup to pc ticked,

so i ticked both options,"backup to pc"+"backup to sdcard" it then worked perfect.

thank you
[Galaxy S II Original Android Development] nat510:
your screen must be on:(
[Galaxy S II Original Android Development] Snizzoop:
I'm also getting stuck at "Creating EFS Backup Partition Image..." My screen IS on, and nothing came up with regards to superuser access.

I was able to create the .TAR no problem.

I'm running on 2.3.6 (JVU) rooted with CF Root. If you need any other info, let me know.

Do I NEED the .IMG if I have the .TAR?

*EDIT* On a i9000.
[Galaxy S II Original Android Development] mahanddeem:
Does my phone needs to be rooted to use this ?

thanks
[Galaxy S II Original Android Development] Caesarea038:
Thanks for the guide!
[Galaxy S II Original Android Development] hiroprotagonist:
Can anyone email me a working efs backup for sgs2 i9100? I dont have a backup that contains nv_data.bin file... No imei or baseband. I would be eternally grateful
[Galaxy S II Original Android Development] Bmsone:
I don't think you can use a backup from another phone, it will have their imei number and not yours...
[Galaxy S II Original Android Development] lyriquidperfection:
Just to let everyone know, I am now back with a Galaxy S II so will be working on an update for EFS Pro to be released soon. Thanks for your interest. :)
[Galaxy S II Original Android Development] Squeck94:
Will this work on a Nexus S?
[Galaxy S II Original Android Development] exwan:
Tried it. First unable to to read pit file error pop out. Then i tried again i says successfull. But the file size is only 20byte. Seems like a failed backup? Or that is normal?
[Galaxy S II Original Android Development] lyriquidperfection:
What version of busybox are you using?
[Galaxy S II Original Android Development] exwan:
Busybox X apps. 1.21.1
[Galaxy S II Original Android Development] Android-Andi:
Also failed on S3 mini (I8190).

Using EFS_Pro_1.12.6_Release worked.

Busybox 1.20.2-cm9
[Galaxy S II Original Android Development] lyriquidperfection:
I am currently in the middle of adding support for non Samsung devices so I will need to rewrite the backup and restore engine. It will hopefully address the issues with I8190 devices.
[Galaxy S II Original Android Development] banziitox24:
I there a way that you can add in the Qualcomm NV tools to restore IMEI on HTC devices at least the latest ones
[Galaxy S II Original Android Development] bromhexine:
i9300 ive got a backup of my efs folder from before. Is there anything else i need to do other than copy over the new folder on the phone to get out of the test mode and unknown phone and h/w screen?
[Galaxy S II Original Android Development] lyriquidperfection:
Yes I could do that but would need to find out the bytes to send to unlock the NV memory.
[Galaxy S II Original Android Development] banziitox24:
Alright cool what you need for that tell me in what I can help

---------- Post added at 03:23 PM ---------- Previous post was at 03:21 PM ----------

I'm looking for the HTC One M7 the new M8 if you can from ATT mostly
[Galaxy S II Original Android Development] Sedat:
no connection to qualcomm nv tools

no more need