yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] catalinu:
I tried to execute it in adb and I hope that the results tell you something because for me is totally chinese:

busybox ls -la /efs/

total 4184

drwxrwxr-x 6 1000 1001 4096 Dec 30 03:51 ←[1;34m.←[0m

drwxr-xr-x 17 0 0 0 Dec 30 13:37 ←[1;34m..←[0m

drwxrwxr-x 2 1013 1000 4096 Jan 1 2011 ←[1;34m.android←[0m

drwxrwxr-x 5 0 0 4096 Jan 1 2011 ←[1;34m.files←[0m

-rwx------ 1 1001 1001 1048576 Dec 31 2010 ←[1;32m.nv_core.bak←[0m

-rwx------ 1 1001 1001 32 Dec 31 2010 ←[1;32m.nv_core.bak.md5

←[0m

-rwx------ 1 1001 1001 2097152 Dec 30 03:51 ←[1;32m.nv_data.bak←[0m

-rwx------ 1 1001 1001 32 Dec 30 03:51 ←[1;32m.nv_data.bak.md5

←[0m

-rw-rw-rw- 1 1001 1001 1 Dec 31 2010 ←[0;0m.nv_state←[0m

-rw------- 1 1001 1001 2 Dec 22 06:00 ←[0;0m.nwksimpin←[0m

-rw-rw-rw- 1 1000 1000 6 Jan 1 2011 ←[0;0mcalibration_data←

[0m

-rw-r--r-- 1 1000 1000 9 Jan 1 2011 ←[0;0mcryptprop_applied

_result←[0m

-rw-r--r-- 1 0 0 5 Dec 30 13:37 ←[0;0mcryptprop_onetime

boot←[0m

-rw-r--r-- 1 0 0 1 Jan 1 2011 ←[0;0mcryptprop_rebootM

ode←[0m

-rw-r--r-- 1 0 0 5 Jan 1 2007 ←[0;0mcryptprop_sdcard←

[0m

-rw-r--r-- 1 0 0 3 Dec 30 13:37 ←[0;0mcryptprop_securew

ipedata←[0m

drwx------ 3 1000 1000 4096 Jan 1 2011 ←[1;34mdmp←[0m

-rw------- 1 1000 1000 112 Jan 1 2011 ←[0;0medk_p←[0m

-rw------- 1 0 0 1 Jan 1 2007 ←[0;0messiv←[0m

drwxrwxr-x 2 1001 1001 4096 Nov 13 07:18 ←[1;34mimei←[0m

-rwx------ 1 1001 1001 2932 Dec 30 03:51 ←[1;32mnv.log←[0m

-rwx------ 1 1001 1001 2097152 Dec 30 13:38 ←[1;32mnv_data.bin←[0m

-rwx------ 1 1001 1001 32 Dec 30 13:38 ←[1;32mnv_data.bin.md5←

[0m

-rwxrw-r-- 1 1001 1001 880 Jan 1 2011 ←[1;32mredata.bin←[0m

-rw-rw-r-- 1 1000 1000 2 Dec 29 20:03 ←[0;0mslideCount←[0m
[Galaxy S I9000 Android Development] catalinu:
In the file nv.log I see something like "restoring from secondary backup" each time a md5 file is not valid or the nv_data.bin is missing... Where it stores that secondary backup it I have no idea...

If I modify the unlock bit but keep the md5, on boot I find in the log the "expected" md5 and the calculated one that does not match, so it will recover from secondary backup again. If the "expected" value of md5 are usefull for you in any way (or the content of the nv.log) I can post them
[Galaxy S I9000 Android Development] dagentooboy:
I think you need to backup and rm nv_core.bak, nv_data.bak, .nv_data.bak, .nv_core.bak
[Galaxy S I9000 Android Development] catalinu:
If I delete the .nv_core.bak and it's md5 (it is no nv_core.bak, only .nv_core.bak) and the 4 files nv_data (.bin, .bak and their's md5), the phone will unlock. A new file nv_data.bin will be created, but with "generic" or "almost dummy" data. The drawback is that the IMEI is replaced with 004999010640000, which I understood that it is a generic one. But at least I was able to put another SIM (Bell) and make calls.

It seems that the files nv_data are re-created based on .nv_core.bak.

What I found is that on .nv_core.bak, at adress 081468 it has FF 01, which will be used to create the new file nv_data.bin at adress 181468. I changed it to FF 00 on .nv_core.bak but this will invalidate it's md5, so the system will not use it to re-create a new valid nv_data file with the correct IMEI.
[Galaxy S I9000 Android Development] dagentooboy:
Don't delete the nv_data.bin file.... That and nv_state are the only nv_ files that should be left.
[Galaxy S I9000 Android Development] catalinu:
I don't think that it can work:

I deleted .nv_core.bak and it's md5. I deleted .nv_data.bak and it's md5.

I kept keep the original nv_data.bin, deleted it's md5 and modified the address 181468 to ff 00.

At reboot it saw that md5 is missing of the nv_data.bin so it invalidated the nv_data.bin, so it wanted to re-create one from .nv_core.bak. But the file was missing so it creates a ÈgenericÈ nv_data.bin wich invalidates the IMEI (used the generic one).

So still unlocked with the generic IMEI.
[Galaxy S I9000 Android Development] degrasubs:
my first post so pls. go easy on me.

ended up getting t-mo locked vibrant just today w. 2.2.1 and bumped it to 2.3.6.

tried couple of unlock options which didn't do any good and ended up w. the following directory structure under /efs:

# busybox ls -al

busybox ls -al

total 2

drwxr-xr-x 1 0 0 0 Jan 1 2005 ←[1;34m.android←[0m

-rw------- 1 1001 1001 2 Jan 5 21:43 ←[0;0m.nwksimpin←[0m

drwxrwxr-- 1 1001 1001 0 Jan 5 21:27 ←[1;34mimei←[0m

-rwx------ 1 1001 1001 438 Jan 5 21:26 ←[1;32mnv.log←[0m

drwxr-xr-x 1 0 0 0 Apr 5 2011 ←[1;34mroot←[0m

-rw-rw-rw- 1 0 0 0 Jan 5 21:26 ←[0;0mupdated_filesyste

m←[0m

Any changes to directory structure or did I mess up something basic (a more likely option) ?

TIA.

---------- Post added at 11:44 PM ---------- Previous post was at 11:34 PM ----------

pls.disregard my previous post. should have been looking under vibrant forum. my bad.
[Galaxy S I9000 Android Development] durkaya:
no this does not work on galaxy s plus. because there is no visible nv_data.bin file anywhere in efs folder. there should be some other unlocking method.with given script i unlocked many friends' galaxy s but s plus no.
[Galaxy S I9000 Android Development] b-reezy:
I have a USA t-mobile vibrant and when I go to edit the hex the line you are referencing does not exist in my NV data just a bunch of FF
[Galaxy S I9000 Android Development] bestjsg:
will the custom rom I am using makes the unlocking with the app fail ?
[Galaxy S I9000 Android Development] roland23:
No, it will work just fine. I'm also on custom ROM and no problem.
[Galaxy S I9000 Android Development] dagentooboy:
email me your nv_data and I will take a look.
[Galaxy S I9000 Android Development] iSilens:
I've tried both manually editing nv_data and using Galaxy S Unlock, but when I insert a different SIM I still get No Service and it does not ask me for an unlock password. Is there anything I can do?
[Galaxy S I9000 Android Development] dagentooboy:
Does your IMEI match what is under the battery?
[Galaxy S I9000 Android Development] iSilens:
Yeah, they're the same. And I've checked the IMEI online and it's not blocked or anything.
[Galaxy S I9000 Android Development] dagentooboy:
so the original carriers SIM still works but not the new one? sounds like you are in need of a factory reset or maybe even a different ROM.
[Galaxy S I9000 Android Development] phissionkorps:
I've read around half of this thread and have yet to find an answer to my questions.

First of all, I am on a US Vibrant running MIUI. Does this method not work with CM/MIUI ROMs?

I tried the generate_code.bat and it absolutely does not work. I get:

searching code block

found.

searching codes...

then it says script complete....and never shows me a code.

Trying to run sgux also does not work, and of the dozen or so links to download sgux2, not a single one of them is still functioning.

I did finally go and do the hex editing method in the first post, navigating to 00181468 and changing to all 00 but leaving the 46 46, then followed the rest of the instructions and didn't get any error messages.

[I tried SGS Unlocker from the market. At first it said it couldn't find codes. Now after using the hex editing method described in the first post, it returns results:

output from scan

found codes!

unlock code :null

unfreeze code :null

is that proof of hex method working...or just gibberish due to incompatibility with MIUI?]

My question is if I used the hex editing method and didn't error out, is it more or less guaranteed to work? I cannot check with *#7465625# because it says "USSD code running....connection problem or invalid MMI code". I've searched high and low and apparently that and a few other codes don't work on CM/MIUI and no one has found any sort of fix. I've seen posts going to back to 2009 about this problem with android in general with still no fix. I unfortunately don't have access to another SIM card until I leave the country in a few weeks, and at that point I will not be bringing my computer with me, so I would like to know if this is working or if I need to buy a different phone to take with me or what.

I don't want to have to flash back to stock and lose everything just to see that it is working, just to flash back to MIUI and lose all that time setting everything back the way it was. Or to flash back to MIUI, have it relock somehow, and not be able to enter to proper codes since a lot of the codes entered through dialer will not work.

If this won't work with CM/MIUI ROMs, what will it work with? Stock ROM only? Or will I even be able to use any type of custom ROM at all?
[Galaxy S I9000 Android Development] dagentooboy:
The best way to be sure is to flash back to a stock rom... unlock... and then flash back to CM. It should still work because the modem is what is actually pulling that data. The looking for codes stuff only works with i9000s built in the first few months of production. The hex hack is the only way to get it to work right now.

To check if it worked try another carriers SIM card and make sure your IMEI matches what is under the battery.
[Galaxy S I9000 Android Development] Freaky_Friday:
Unlocking T-Mobile Vibrant w/CM7

Hi there, I'm having the same problem with my T-Mobile Vibrant (C. Tried searching for the referenced hex location in the nv_data.bin and it's just not there.
[Galaxy S I9000 Android Development] dagentooboy:
MAKE BACKUPS!!!!!

then you could try the guide for the Vibrant 4G (in my sig)
[Galaxy S I9000 Android Development] jesuita:
Does anyone have the sgux2 utility and could upload it please?

Cant find it anywhere..
[Galaxy S I9000 Android Development] dagentooboy:
It should still be in the .zip attached to the first post in this thread. Just so you know that hasn't worked since the first run of i9000s. The hex hack is the only thing that works now.
[Galaxy S I9000 Android Development] maddy_in65:
It is not working for me. I have NTT Docomo galaxy S. I tried editing nv_data.bin but cant fine required text. I downloaded Windows unlocker and after running batch file nothing works. Please help me.
[Galaxy S I9000 Android Development] dagentooboy:
The Docomo version is the one exception to the rule. use google to look for the service codes. You are going to need to lock the phone to whatever carrier you want to use.
[Galaxy S I9000 Android Development] sosodemi:
cant unlock my i9001 :(

witch is the best method ? if there is one for s plus.
[Galaxy S I9000 Android Development] dagentooboy:
The HEX hack is the ONLY method that works right now. What is in the /efs/ folder on your i9001?
[Galaxy S I9000 Android Development] astrah:
Just after some advice.

tried all the methods in the first post, paid for the SGS Unlock Pro, said phone was unlocked so tried relock, restarted phone, then unlock - restarted phone put Vodafone UK sim in, still no network, it seems the phone will only work with 3 UK and T-Mobile UK? any ideas.

I tried rolling back to an earlier firmware, details are:

Model - GT-I9001

Firmware - 2.3.4

Baseband - I9001XXKP4

Kernel - 2.6.35.7-perf

root@DELL148 #1

Tried custom roms and now back on stock. When I copy over the nv_data.bin file from terminal it is 'empty' although it has a file size of 1.50MB.

Also tried Generate_Unlock_Windows but that didn't find any codes!
[Galaxy S I9000 Android Development] gio25:
Problems

I did this method and did not work. I have a I9000T locked for Claro Puerto Rico and I want to unlock it for T-Mobile but even when I run the tool and says the network lock is off , reboot the phone with the T-Mobile SIM, it says network locked. My phone has Gingerbread 2.3.3 and is rooted. Help!!!
[Galaxy S I9000 Android Development] dagentooboy:
Sounds like an APN issue. See if you can look up and manually add the APN settings for Vodafone.
[Galaxy S I9000 Android Development] dagentooboy:
Can you send me a before and after /efs folder zipped up and emailed? You can use my paypal email in my sig.
[Galaxy S I9000 Android Development] astrah:
When I put the vodafone sim in and go into APN, Vodafone Contract WAP is selected but still I get Emergency Calls only, I have sort of double posted this because afetr I posted the question above I figured it could possibly be software fault and not an unlock issue, the question I posted may be a bit more explanitary.

link to other thread - HERE #850
[Galaxy S I9000 Android Development] dagentooboy:
Make sure you have a good modem and the APN settings are correct.
[Galaxy S I9000 Android Development] Dude Random21:
Hey I'm trying to do this on my brother's t-mo vibrant but there seems to be a problem the string of bytes "ff 01 00 00 00 00 46 46" well on his phone the string comes out "ff 01 00 00 00 00 39 37" and I'm not sure if I should just leave it like that while just changing the "01" for a "00" or if I should also change the "39 37" to "46 46" anyone had this problem before??
[Galaxy S I9000 Android Development] gio25:
Sad

Thanks to dagentooboy for the help, but sadly after everything I tried nothing worked. If someone has made it work or have some advice for me it would be greatly appreciated.
[Galaxy S I9000 Android Development] dagentooboy:
just change the 01 to 00. That is what actually makes the change. Not sure why that part is different.
[Galaxy S I9000 Android Development] pure_energy1:
Need help.

I have a BELL i9000m on 2.3.3 (I9000UGKG3).

Unlocked it using the Helroz unlocker so that my girlfriend could use it on Koodo (Telus).

The phone works, but there is no Data.

I tried manually configuring the APN using the info from Telus' website. Still doesn't work.

I should note that I was not required to enter the unlock code when I inserted her Koodo SIM card.

Did I miss a step somewhere? Can someone guide me to setting up DATA on the phone please?

Cheers.
[Galaxy S I9000 Android Development] pure_energy1:
Woops my bad... I assumed I had to use the Telus APN when I had to use the koodo apn.

All good now
[Galaxy S I9000 Android Development] RoRo1990:
I bought your app and tried the unlock function the phone vibrates twice then I get a force close message. Running I9000m with 2.2
[Galaxy S I9000 Android Development] dagentooboy:
Hmmm. I haven't tested it on an OS that old. Maybe you should upgrade first and try again.
[Galaxy S I9000 Android Development] blablable:
Works with I9000 ICS?
[Galaxy S I9000 Android Development] dagentooboy:
I tested it on my vibrant with ICS so it SHOULD work... no promises.
[Galaxy S I9000 Android Development] alexis!:
I tried to open nv_data.bin file with HexEditor (running Windows 7) and all lines are 0.

I mean all columns and rows are 0.

Maybe something wrong?

Thanks!

PD: Running a non official version of CM9 on GT-I9001. Maybe it`s important, but i can revert to Gingerbread ROMs.

PD2: Think GT-I9001 doesn´t have such file :( No unlocking method yet.
[Galaxy S I9000 Android Development] dagentooboy:
You can delete that file... that is a bug that I need to work on.
[Galaxy S I9000 Android Development] Hakkaboy:
nvm

i downloaded the app from the market and it works on my bell i9000m w/ ICS 4.04

thanks!
[Galaxy S I9000 Android Development] lalocolin:
I have almost the same problem, with the difference that when you dial *#7465625# to see the network lock status it already says Off, but when I change the sim card it asks for the network code, I already tried some methods to get it, including Generate Unlock Windows.bat and the sgux2.exe+blm3.bak, and also tried manually by opening blm3bak in a hex editor and when I go to the part where the codes are supposed to be it only shows random things as it if they were coded. Hope you can guide me to successfully unlock my phone.
[Galaxy S I9000 Android Development] Lisali:
Hi guys,

Do any of the methods from this thread work on Samsung Captivate Glide?

Thanks!
[Galaxy S I9000 Android Development] dagentooboy:
Possibly... I haven't seen any files from the Captivate Glide yet. If you want to email me a .zip of your /efs I can look at it.
[Galaxy S I9000 Android Development] Lisali:
Thanks so much, that is very kind of you! Have PMd you. :)
[Galaxy S I9000 Android Development] apater:
I9000T unlock code

Galaxy S Unlock gave me the following codes once the I900T from Claro had root: Unlock: 30713747 Unfreeze: 64649592.

How did you convince your phone to prompt for the code? What firmware are you using?
[Galaxy S I9000 Android Development] dagentooboy:
just change the sim card. If it doesn't prompt you then it is probably already unlocked.
[Galaxy S I9000 Android Development] Lisali:
@Dagentooboy - I have PMd you but not sure how to attach the zipped EFS folder to the PM?
[Galaxy S I9000 Android Development] CodeJACK:
Hi,

Any reports of this working with Galaxy S Advance ?

Comes shipped with 2.3.6 but just wondering if anyone could confirm its worked.

Did a search of the thread but could not find success story.

Tried UnlockUnit.com but after a week they refunded me and said no unlock codes were possible as the phone was too new !
[Galaxy S I9000 Android Development] dagentooboy:
that looks like an S2 model. If you want to email me a zipped copy of the /efs folder I can take a look but so far we haven't found anything for the S2.
[Galaxy S I9000 Android Development] Lisali:
Hey dagentooboy - have messaged you, not sure if you got my PM?

Thanks!
[Galaxy S I9000 Android Development] CodeJACK:
Ah, no problem, I read this wrong.

Thought it was root for any Galaxy S inc the 2 and all other models :-)

Thanks for the offer but I wont waste your time.

Ill have to wait a little longer for this phone to be usable.
[Galaxy S I9000 Android Development] apater:
Doesn't work on the I9000T from Telcel/Claro. I found we also need to replace the bootloaders (so called 3 button fix), otherwise we are stuck on the Network Lock screen with no way to enter the code.
[Galaxy S I9000 Android Development] CB620:
How bout the Blaze 4G T769? Keeps saying i don't have a nv_data.bin but when i search my efs in rootexplorer its right there. Any way to make it work for my device. The Blaze 4G section needs some love.
[Galaxy S I9000 Android Development] dagentooboy:
can you email me the /efs/ folder zipped up and I will look at it.
[Galaxy S I9000 Android Development] lalocolin:
I had trouble unlocking my SGS, the codes were FFFFFF and the app did not worked, then I read here that the problem were my files inside the EFS folder, I followed this steps to repair them and now my phome is unlocked.
[Galaxy S I9000 Android Development] nripin:
Worked on my Captivate today !!!

Thanks guys This worked on my Captivate today !!!
[Galaxy S I9000 Android Development] gtangas:
cant fin bin file

Hi

I tried to run the app but it said that cant find the bin file....

Can you guys help me?

thx
[Galaxy S I9000 Android Development] dagentooboy:
If you are on the S2 or the note it doesn't work.
[Galaxy S I9000 Android Development] Lisali:
Hi all,

Just an update to those affected. I have been trying to get help here with unlocking my Captivate Glide for a while now. Never got any reply :(

So I bought an unlock code online which has unlocked the phone. However, every now and then, randomly, it will ask for the code again when I restart the phone. The code is accepted again, but it's very annoying.

Why would this be happening?

Thanks!
[Galaxy S I9000 Android Development] gtangas:
unlock

No my SGS is the gt-i9000

i have the 2.3.3 xwjvn

and no root
[Galaxy S I9000 Android Development] dagentooboy:
you will need root for it to work... you can email me (use my paypal email in my sig) your /efs/ folder and I can look at it for you.
[Galaxy S I9000 Android Development] dagentooboy:
Since the glide is a very different phone I am not sure if any of this will work. You can email me a zipped copy of your /efs/ folder and I can see what I can do (use my paypal email in my sig).
[Galaxy S I9000 Android Development] gtangas:
I cant copy the efs folder!

I can see it on an explorer of the phone but... nothing

I tried to make a zip file, copy but it tells me that i dont have permission

My phone is on a ginger stock version of optimus-portugal and i havent root the phone.... yet!

Can you give a hint on this?

thx
[Galaxy S I9000 Android Development] dagentooboy:
You must root first. Then use a root enabled explorer.
[Galaxy S I9000 Android Development] sevenfolds:
man i got a confusing one.

the SGS i use is I9000 Europe version (TMobile) version 2.2.1

i already used it for a couple of days

but one day i removed my battery and sim card

and then i put it back, says network lock control key

so i got no idea, i tried to upgrade the firmware, saw the latest

i used 2.3.6 and flashed it via odin, i rooted it, install busybox and galaxy_s unlock

it worked for 1 time

but it goes back to network lock control key

what should i do man?

maybe you can give me tips

aside from the online buying of codes,

i don't have a credit card that's why

thanks in advance
[Galaxy S I9000 Android Development] dagentooboy:
Did you try the hex hack on the first post?
[Galaxy S I9000 Android Development] sevenfolds:
i'll try that one

and if it doesn't still unlocks the network

i'll downgrade the firmware

and do that both

then upgrade it
[Galaxy S I9000 Android Development] b-george:
If i unlock my s3 with Voodoo Galaxy S III SIM Unlock app from market, will i lost my warranty. I know i have to unroot to get warranty back.

Because even if i unroot, my will still be sim unlocked.
[Galaxy S I9000 Android Development] dabrain23:
Hey.

I have a korean SGS (M110S) on the newest WC13 firmware. unfortunately none of the options work. i tried copying the nv_data.bin, but i can't locate the correct address. it strangely doesnt exist?!?! your free tool from the market doesnt work either.

can you help out?

my nv_data.bin

http://www.mediafire.com/?lrq5qe4tew6xvh2
[Galaxy S I9000 Android Development] dagentooboy:
There are only 2 places with the FF FF FF 01 00 00 00 00 combination. You might try changing one place from 01 to 00 and put it in /efs/ and delete nv_data.bin.md5 and reboot. Check the locks and if that doesn't work switch it back and try the other.
[Galaxy S I9000 Android Development] chleoj:
will this work for unlocking samsung corby II? thanks :)

EDIT: i'm sorry, wrong thread!
[Galaxy S I9000 Android Development] McCasian:
Good job

Very good work. If nothing work for your galaxy s, try manual hex edit. Only manual hex editing works for me. Sorry for my english :P
[Galaxy S I9000 Android Development] saintetienne:
Run- generate code.bat - works and says code found - but dont see it - where would I find/see it ?

thanks
[Galaxy S I9000 Android Development] unibombz:
No luck with this method to unlock a Samsung i9000m (bell) (SG1) I have tried everything over xda to unlock this phone, no method works..... who is having success with unlocking ? Is there something I am missing ?

My phone is rooted, no scripts, exes, market apps work to unlock the phone, should I just pay to have it unlocked ?
[Galaxy S I9000 Android Development] the-weatherman:
What Android version? Did you use the Hex hack? It works fine on the regular i9000 on Jelly Bean.

Just make sure to delete the nv_data.bin.md5 after copying the hacked nv_data.bin file. Also, check your permissions, on mine they are 777 and the owner is root:root.

I did it using Root Explorer. Good luck!
[Galaxy S I9000 Android Development] MeMoM&aVirusTI:
Hi ....cool it seems it works on my GS2 .....ok so lately Samsung Galaxy series devices are relocking from the 4.1.2 XXLSJ leak ...i managed to fully re-unlock using GalaxSim Unlock

But on my quest for a working PC code generator ...I tried this app & ran it just to see if it would do anything at all

I guess it detected that my device is already unlocked & generated only a MCC/MNC 5 digit Lock code :)

So its safe to assume that if my device sim was locked it would generate an unlock code ??

I am tempted to try the lock code it generated ..to see if it locks the sim ..