yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] kickthefreak:
hi all, i have backup my EFS using this tools but i cant restore it,

i have root and busybox ? any clue ? how to fix this cause i cant use my phone to make a call,

im running latest fw for i9300 int'l.

here is what i do before :

1. im flashing to stock 4.3 I9300XXUGNA5_I9300OLBGNB1_I9300DXUGNB1_HOME.tar.md5

2. making backup with EFS_Professional_2.1.47_Release

3. backup found on EFSProBackup and the file is GT-I9300_20140620_191902.tar.gz

4. why i backup my EFS cause i want to downgrade to 4.1.1 I9300XXDLJ1_I9300OLBDLJ1_I9300DXDLI5_HOME.tar.md5

5. after downgrade i cant register to my network and get emergency call only

6. so i tried to restore using EFSpro but my backup file wotn show up even i refresh so many time

7. and accidentally i click EFS Clear on restore section and make my phone into factory mode

8. so i try to get out from factory mode and success

9. i flashing again to 4.3 I9300XXUGNA5_I9300OLBGNB1_I9300DXUGNB1_HOME.tar.md5

10. still cant restore with EFS_Professional_2.1.47_Release, tried refresh but failed.

any clue how to fix my phone and get my signal back ?

thanks

--------

Fixed now, just extracting backup into efs.img and push from terminal.
[Galaxy S II Original Android Development] jay_993:
Hi, guys I feel someone here may be able to help me out.

I've a SGS2 with corrupted IMEI I believe. I happen to have efsdev-mmcblk0p1.img file and efsbackup.tar file on my internal storage with it's last edited date in 2012 so I got this back up LONG time ago.

Could anyone guide me how to restore my EFS please? I am aware that the OP states that any old backups can't be used after v2 but doesn't really state how we can restore for these older backups...

Any input would be appreciated.
[Galaxy S II Original Android Development] estevensv:
I doesnt recognize my galaxy s3, any ideias?
[Galaxy S II Original Android Development] lyriquidperfection:
Make sure you have authorised the adb connection.
[Galaxy S II Original Android Development] SAMPPLE:
I'm not sure

Hello guys I have a Samsung Galaxy SII and I need to backup my EFS, and I do this but, I'm not sure if I changed the good option for EFS backup...
[Galaxy S II Original Android Development] estevensv:
Thanks
[Galaxy S II Original Android Development] muppetmania:
Backing up and restore of IMEI using NV-Tools is possible without being rooted, is that a valid statement?
[Galaxy S II Original Android Development] lyriquidperfection:
Yes thats correct but its also worth backing up the partitions aswell to maintain device integrity.
[Galaxy S II Original Android Development] abrarabbu:
Sir, is there any way possible you can include support for S5 G900T qualcomm variant.

Thanks!!
[Galaxy S II Original Android Development] lyriquidperfection:
Have you not tried the app already?
[Galaxy S II Original Android Development] abrarabbu:
I have tried app.

it reads imei, when I try to write, it says susseful but there is actually no change in phone.

i am in qualcomm qpst tool.
[Galaxy S II Original Android Development] lyriquidperfection:
Thats because its only for repair purposes and that fact that it writes and doesnt change is because that is a secure nv item. You can only write back if you have wiped nv data.
[Galaxy S II Original Android Development] abrarabbu:
I really need to write imei.

Can you give me procedure on how to do it?

I have all tools ready, phone rooted, busy box installed.

let me know how it can be done. I am willing to take chance.
[Galaxy S II Original Android Development] lyriquidperfection:
Like I said, writing imei is for repair purposes only. Sorry. End of discussion.
[Galaxy S II Original Android Development] lyriquidperfection:
EFS Professional v2.1.73 has now been released!

Lots of changes and new features!

Enjoy! :)
[Galaxy S II Original Android Development] lyriquidperfection:
Full source code in VB.NET for the latest version is now up for grabs on ebay. If you are a developer and appreciate the 3+ years I have spent developing this app then please show your support.

Search for item number: 331245455868

Happy developing!
[Galaxy S II Original Android Development] Masami1975:
Can I make IMEI backup for Note 3 N9005? All efs partitions? Thank you
[Galaxy S II Original Android Development] lyriquidperfection:
Yes you can there is a Device Filter for Note 3 International Variant. Use this option when backing up.
[Galaxy S II Original Android Development] lyriquidperfection:
Thanks, this alot to digest. The md5 hash is only checked to ensure the whole data is extracted correctly. I cant do an md5 against the archive as I dont have anything to compare it to. It would also make the whole process slower if the archive was extracted and each file hashed. This is why md5 was added to the restore process. I know the whole process can seem a bit sloppy but its really for people that know what they are doing like yourself. As for the userdata md5 glitch, this may be a limitation of busybox but my app was only ever designed to backup important partitions only. The fact of being allowed to backup any and all partitions was simply a side effect from the device filter functionality being implemented. I will certainly try to improve hashing and implement further checks in a future release.
[Galaxy S II Original Android Development] lyriquidperfection:
[MENTION=5913721]bruzzy[/MENTION], just a thought, have you configured the storage location correctly in EFS Pro to reflect the fact you are using external storage? Its configured by default to use the internal storage: '/sdcard' which is probably why backup of the userdata partition is incomplete if there is insufficient storage space available.
[Galaxy S II Original Android Development] wangshin248:
SS note 3 N900A

hi everyone, i unlocked my phone when i were traveling outside the US, when i unlocked it, they changed my IMEI ( they didnt use unlock code ) so it's totally different with orginal IMEI, it worked with foreign networks. Everything was fine when i went back to the US, i kept using AT&T network, but now i changed to Tmobile, it has full bar signal. However, it said "emergency call only" i dont know why, it didnt ask me about entering unlock code or anything, but i cannot make a call or text, internet v..v.... it's seem so weird.

I just went to Tmobile, they told me maybe AT&T block my IMEI ( i bought it from Fry electronic, it's brand new fone ), but when i came to AT&T store, they said T-mobile have to setup their network on my phone. They are so fk crazy, useless.

I also rooted it, then update new Kitkat custom Rom, it works fine except that i cant make a call.

If i change my IMEI back to orginal, will it connect to Tmobile network ????

---------------------
[Galaxy S II Original Android Development] bruzzy:
Yes, I did. In my case it's /external_sd. All the files were written to that location by EFSPro.That was actually the first thing I've changed when I started testing EFSPro. I've been also monitoring the space used by EFSPro (calling df periodically) and with the 64GB card, it didn't look like there was too less freespace so that tar couldn't complete properly.
[Galaxy S II Original Android Development] lyriquidperfection:
Another thing to consider, were you extracting the archive contents to verify the file size or were you looking at the packed size? A compressed file from a 20MB partition for example can compress to as little as a few hundred kilobytes. This is possible because dd does an exact 1:1 copy of a partition which includes the free space giving its large size depending on the partition. Compressing magically turns this free space contained in an extracted partition file into virtually nothing. The resulting compressed file size is basically the size of the actual data taken up by the partition.
[Galaxy S II Original Android Development] lyriquidperfection:
Sounds like your phone was unlocked with a box. Take it back and make them finish the job. Your original imei should be reinstated and your 3G needs repairing also as this breaks during box unlocking.
[Galaxy S II Original Android Development] bruzzy:
I would even suggest to add the md5 hash(es) to the archive as well, e.g. in form of a txt file. The extracting and the final check could be done on the PC side (to accelerate it a bit). To avoid this extra "slow down" on every backup, you could add another option for switching that on or off.

Did you already have a thought on my feature request (dumping directly to PC instead of making temporary files on device's storage)? I know, it would be much slower, since the raw dump(s) have to be transferred via USB (which is much more bytes then the final archives). But on the over hand, you don't need to worry about the free space available on the device.
[Galaxy S II Original Android Development] lyriquidperfection:
The partition has to be dumped device side first as there is no possible way to dd direct from the device straight to the hard drive which is why the resulting archive always gets copied to the PC afterwards which means you get two copies for an extra safe backup.
[Galaxy S II Original Android Development] bruzzy:
I've extracted the archive and looked at the extracted data (see below).
[Galaxy S II Original Android Development] lyriquidperfection:
Did you interrupt during the dd of the userdata partition? And also did you use md5sum -t filename.img in the working directory as I found specifying path to file in md5sum can result in incorrect hash as it also takes the path into account.
[Galaxy S II Original Android Development] bruzzy:
Actually there is a way to dd dircetly from the device straight to the hard drive of the PC... Did you have a look to this thread: [GUIDE] How to make a nandroid backup directly to your computer without using sdcard (I've sent you the link in the PM already)? I know, it's different from your concept, but it's a way.
[Galaxy S II Original Android Development] lyriquidperfection:
I came across something very similar to this thread before in the past and thought it was alot easier to create the backup device side and then simply copy to pc giving to backups, one on device and one on pc. I didnt want to risk introducing more bugs and issues with users not being abke to open the required port etc or the file not transferring.
[Galaxy S II Original Android Development] bruzzy:
I let EFSPro do its job until it was finished with matching the md5 of the dump with the md5 of the partition and started tar. At this point I interrupted the USB connection, executed the tar command manually, copied it to the PC, extructed the dump, got the md5 hash of the extracted dump and this was exactly the same, which was calculated by EFSPro using md5sum on the partition and the dump on the device.

As I said, from my understanding, what I've done manually, was exactly the same as what was done by EFSPro. But for some reason, the outcome of the tar process initiated by EFSPro wasn't valid in this case. And it has something to do with the size of the partition, since it works fine for smaller ones.

---------- Post added at 11:57 AM ---------- Previous post was at 11:53 AM ----------

Well, I was thinking on "let the tool doing all of the necessary steps", since it's able to run commands locally on the PC side as well as on the device side (via adb). I'm not saying, it's an easy job. But it's a possible way...
[Galaxy S II Original Android Development] wangshin248:
It's impossible because i unlocked it outside the US, idk they used box :( any idea to repair it?????
[Galaxy S II Original Android Development] lyriquidperfection:
I am a strong believer in if it isnt broke, dont fix it but I will look into this a little more and conduct some testing to determine viability. Thanks alot for all your valued input.
[Galaxy S II Original Android Development] lyriquidperfection:
Yes you would need to use box again to repair.
[Galaxy S II Original Android Development] wangshin248:
your app cannot rewrite IMEI ???
[Galaxy S II Original Android Development] lyriquidperfection:
It can but only after an efs reset or if correct security patameters are passed.
[Galaxy S II Original Android Development] wangshin248:
can you show me how ? or i have to buy a ticket to get back to last country where i visited to repair it :( when i search some stores near here, they charge me more than 70$ for repairing, but i'm not sure that they can restore my original imei.

i know you can say it's illegal for changing imei, but i swear this is my phone, i dont buy it from any seller !!! please help me bro :(
[Galaxy S II Original Android Development] Murshad007:
I am getting error that " device is not perm rooted"

HELP pleaase

I have safe rooted and super Su 2.0 installed..
[Galaxy S II Original Android Development] wangshin248:
please help [MENTION=1834730]lyriquidperfection[/MENTION] :(
[Galaxy S II Original Android Development] AO7:
You must enable root access for ADB.
[Galaxy S II Original Android Development] themulvster:
Hello

When I connect my SGS3 i9300 to the laptop and run EFS Pro it says "Your device is NOT perm rooted"...

Does anyone know what this means?

I need to try and save my EFS due to a Rom issue and NEED this program to work :(

Cheers
[Galaxy S II Original Android Development] muppetmania:
It means your phone isn't rooted.
[Galaxy S II Original Android Development] themulvster:
I am running CM11 Rom so must be rooted :\
[Galaxy S II Original Android Development] lyriquidperfection:
You need to go into the settings for the built in superuser and set the access to apps + adb.
[Galaxy S II Original Android Development] themulvster:
Thanks for that, it worked. Only problem is the program cannot find any efs files.

I'm sure I can find some efs backup files in astro file manager...
[Galaxy S II Original Android Development] toto2011:
Mod Edit: Please don't quote the whole OP.

It shows failed to start adb server!please help
[Galaxy S II Original Android Development] lyriquidperfection:
Do you have something in your background processes already using an adb server instance or that might interfere with adb?
[Galaxy S II Original Android Development] lyriquidperfection:
You need an EFSProBackup folder in the storage location defined in EFS Pro and place your backups there.

They must be previous backups made by EFS Pro.
[Galaxy S II Original Android Development] themulvster:
Thanks mate, I don't have one sadly.

Looks like I have to try and restore to stock rom

Cheers for the advice
[Galaxy S II Original Android Development] AO7:
You need root access for this to work. If you have on stock ROM find a root guide for your version. If you are on CM simply enable root access for apps and adb in the developer options
[Galaxy S II Original Android Development] themulvster:
Thanks for the help.

In the end I had to re-flash the stock i9300 Rom using Odin, I flashed the o2 version which resulted in a boot loop, I think my i9300 must've been an unbranded one as I don't recall seeing the o2 bubbles on startup before.

So then I flashed CWM using Odin and then flashed FoxHound Rom and its brought my network back :D

I then restored my nandroid backup before the network lost and IMEI screw up and everything is now back to normal *sigh*

:D
[Galaxy S II Original Android Development] Darkshado:
[MENTION=4353736]toto2011[/MENTION] Do NOT quote the original post unless actually necessary, and only do so with the required parts.

If you think it's annoying to scroll past on the computer, you should know that it makes the mobile XDA app stutter, then slow down to a crawl.
[Galaxy S II Original Android Development] mocoyombiflash:
i love you this program rocks
[Galaxy S II Original Android Development] lyriquidperfection:
Im guessing it fixed your device then? :)
[Galaxy S II Original Android Development] emottier:
IMEI Repair Galaxy Note 1 N7000

Hi,

As I need to repair a null IMEI with my N7000 I tried your so usefull program.

I followed this Tuto:

http://www.forum-generationmobiles....e-la-partition-efs-imei-avec-efs-professional

Device has latest Samsung Stock Rom N7000XXLT9_N7000SWCLT4_SWC (SWC =Swisscom) (Android 4.1.2)

Phone is rooted.

I am on Windows 8.1

As Kies is installed I think drivers are ok.

And I encounter some pb.

ADB Server connect to device and is ok and main menu appear.

Backup works up to factory.ifs which fail with MD5 missmatch.

Then I started NV-Tools and msg saying cannot connect. Deactivate Device debugging and re-activate it makes connection ok.

Click connet on NV-Tools I receive msg "SPC was rejected by the phone".

I unclick Send SPC, click Connect receive msg (Sorry is in french):

L'index et la longueur doivent faire référence à un emplacement situé dans la chaîne. Nom du paramètre :length

But it connects, and if I click Read phone info, I receive same above msg : L'index et la longueur...

I click Secure Ops, check IMEI, enter my IMEI found Under the N7000 battery click Target Phone Write, receive msg "Selected byte data was written successfully!"

End program, reboot N7000 IMEI is always null!

What's wrong please?

Thank you for this helpfull program.

Eric
[Galaxy S II Original Android Development] halfbytecode:
[MENTION=1834730]lyriquidperfection[/MENTION] I have a nexus 5 in diagnostic mode. I was willing to repair my IMEI, but NV tools does not seem to write any values (reads values fine). I provide it with the correct SPC, which is accepted by the device.

I'm using LG United USB drivers, and kernel with diagnostic mode enabled. Could you tell me what I'm doing wrong?

By the way, the same happens with other tools QPST, DFS, CDMADevTerm, etc.
[Galaxy S II Original Android Development] lyriquidperfection:
Phone would also need to be in factory or low power mode. You can set this from the connection settings.
[Galaxy S II Original Android Development] halfbytecode:
I tried it with factory test mode, and it made the phone have "Unknown" baseband and IMEI as well.

With low power mode, it returned back to saying IMEI as 0 after writing back my original IMEI too.

I don't get what's going on. One thing I noticed is that by changing the connection mode, there was nothing else noticeable on the phone. It functioned normally.

Any help with this please?
[Galaxy S II Original Android Development] lyriquidperfection:
Not sure to be honest, the IMEI NV item is secure so although appears to write successfully, it needs to be properly unlocked and device in full factory programming mode somehow for the change to stick.
[Galaxy S II Original Android Development] halfbytecode:
Alright, I think that is the problem.

Is it normal for a device to accept any 16 digit diagnostic password for secure operations? My device does that.
[Galaxy S II Original Android Development] lyriquidperfection:
Yes because its mainly samsung that utilise that functionality.
[Galaxy S II Original Android Development] quebec1:
hello i have a question:

with the last version of efs i can use the last version of busybox or must i always use the busybox 1.20.2?

sorry for my english
[Galaxy S II Original Android Development] lyriquidperfection:
You should be able to use the latest busybox with latest version of EFS Pro
[Galaxy S II Original Android Development] emottier:
Is my question so sad (I know I am a noob) that I do not have the right to have a response?
[Galaxy S II Original Android Development] lyriquidperfection:
Please research a bit before posting and you will realise that the N7000 is not a qualcomm device and you cannot repair imei that way. You would need a service box to conduct a proper repair.
[Galaxy S II Original Android Development] emottier:
Ouuuuup! Iam very sorry, I did not see this.

My apologize.
[Galaxy S II Original Android Development] quebec1:
Ok il try.

I done this question because with old efs version when I launched the program and this did the bysibox check tell me that I must installed busybox 1.20.2

Sorry for my english
[Galaxy S II Original Android Development] OMG_VTEC:
hey ive been trying to message you for a few days now, theyre not showing up in my sent message inbox thing...are you getting them?

not being impatient, just want to make sure theyre actually sending
[Galaxy S II Original Android Development] mbmb8989:
I9505 nv_data repair

Hey guys ! I own a samsung galaxy s4 (i9505) and here is my question :

I've got real issues with signal ; signal is lost almost every time (sometimes i get one bar but it disappears so fast !).

I flashed latest samsung 4.4.2 stock firmware (including modem, bootloader, etc..) and it is the same.

I checked IMEI and it is okey so my friend (who works at a samsung service spot) told me this is certainly related to a corrupt nv_data.

Before taking it to samsung service to repair it (which will cost money), i'd like to give it a shot with EFS Professional (assuming there is a section in it to backup/restore and repair nv_data section)

So my question is ; is it possible to repair the nv_data section of my i9505 without having a backup ? (i've never did a backup of the nv_data since the phone were already having this issue when i got it)
[Galaxy S II Original Android Development] cdzo72:
I have a similar issue with my i9505... my signal sucks no matter what GSM modem I flash, even the one for my country and it never would pick up LTE when the phone next to me would... I'd love to know if you make any progress in this area...
[Galaxy S II Original Android Development] mbmb8989:
You can try to force your gsm to gsm only (in networks i think), maybe that can help you ; i've already tried it and no progress so far..
[Galaxy S II Original Android Development] cdzo72:
You tried to repair nv data or switching to GSM only. ..

I've tried GSM only but that does no good...
[Galaxy S II Original Android Development] mbmb8989:
I'll try the repair in a samsung centre and report here ! (after giving it a try with EFS Pro)
[Galaxy S II Original Android Development] lyriquidperfection:
You would need someone with a working I9505 to get a copy of the nv items then restore it via Qualcomm NV Tools.
[Galaxy S II Original Android Development] mbmb8989:
You think that this can solve the no-signal issues ?? I thought that the nv_data contained the imei so i would have to find a way to modify these files before restoring it ?
[Galaxy S II Original Android Development] lyriquidperfection:
They do contain imei but secure nv items like that wont get written unless booted in factory mode with uart. So just writing another phones backup should be fine. But back yours up anyway just in case so you can restore if something goes wrong.
[Galaxy S II Original Android Development] mbmb8989:
Ok thanks for the tip ! (i presume that the factory mode with uart would be the solution used in samsung service center)

I hope this can fix my no signal issues :crying:

Edit : I can use any nv_data file ? (must only be a i9505 right ?)
[Galaxy S II Original Android Development] lyriquidperfection:
Use an i9505 one to avoid issues.
[Galaxy S II Original Android Development] mbmb8989:
Okey ! Last question and i'm gone :D What are the files that i should copy from the other i9505 ? (just "nv_data.bin" using rootexplorer ?)

EDIT : I just have to do a nv_data backup with the other phone and use that backup right ?
[Galaxy S II Original Android Development] lyriquidperfection:
There is no nv_data.bin file. This was on older non Qualcomm models up until the S3. Your nv data and all nv items including imei are stored across 2 partitions called modemst1 and modemst2. Also backup the m9kefs1, m9kefs2 and m9kefs3 partirions in case something goes wrong. Connect the donor S4 to Qualcomm NV Tools and perform a full nv items backup then find item 550 and change to match imei on your phone. Then restore the modified backup. Imei must be in hex format in the modified file and you get the hex data from within the app.
[Galaxy S II Original Android Development] mbmb8989:
Thanks for the tip ! I'll let you know how if that worked with my issue.
[Galaxy S II Original Android Development] TinyPop:
Can you help me fix this
[Galaxy S II Original Android Development] lyriquidperfection:
You need to go on samsung tools and use the drop down list to set factory mode to user mode. Then there will be other options too to repair no signal and unknown baseband if necessary.