Download the normal unlock files before you do anything!!! You can find them in the forum.
KIES needs to be off...
1 - You need your phoned to be rooted
2 - Put your phone in usb debug mode
3 - Plug in the usb cable (don't use kies or storage mode)
4 - In the run window type CMD
5 - Go to the folder where you extracted the unlock files. Example c:\Generate Unlock Windows\Generate Unlock Windows
Type dir , you should see a file called adb.exe
6 - Type adb kill-server
Type adb shell
Type su (on your phone you should see the root explorer asking if you want to allow access, choose yes xD duh)
Type cp /efs/nv_data.bak /sdcard !!!IF this doesn't work type this!!!!----> cp /efs/.nv_data.bak /sdcard
Type cp /efs/nv_data.bak.md5 /sdcard !!!IF this doesn't work type this!!!!----> cp /efs/.nv_data.bak.md5 /sdcard
7 - Closed the window.
8 - The file with the code is now on your sdcard, start storage mode and copy the files to the c:\Generate Unlock Windows\Generate Unlock Windows folder (in windows xD)
Be sure that the nv_data.bak and nv_data.bak.md5 are in the same folder as sgux.exe
9 - Edit the Generate_Code.bat
Delete all the code and paste this:
@echo off
cls
echo ===============================================================
echo ===============================================================
echo Generate unlock code for any Samsung Galaxy S
echo ===============================================================
echo ===============================================================
echo Extract code
.\sgux .\.nv_data.bak
.\sgux .\nv_data.bak
echo ===============================================================
echo ===============================================================
echo Please donate to DagentooBoy for the script
echo Please donate to rbnet.it and marcopon for the SGUX utility used in the script
echo ===============================================================
echo ===============================================================
echo Script complete!
pause
10 - Your codes should appear! Save them and send them to you gmail account so you have them for life!
I TAKE NO CREDIT FOR THIS!!!! Just want to help!
Can you please Help me?
I flash & reflash several times, and still can´t resolve this.
I don't have any file with *bak* at this moment.
the files that I have:
# find /efs
find /efs
/efs
/efs/.android
/efs/.android/testAndroid1.bin
/efs/.android/testAndroid2.bin
/efs/.android/testAndroid3.bin
/efs/nv_data.bin
/efs/.imei
/efs/imei
/efs/imei/mps_code.dat
/efs/imei/bt.txt
/efs/imei/.nvmac.info
/efs/nv_data.bin.md5
/efs/.nv_state
/efs/nv_data.jpc
/efs/nv_data.jpc.md5
and de result to nv_data.bin:
E:\Generate Unlock Windows>sgux2 nv_data.bin
SGUX v0.92b (C) 2010 By Mark0 & rbnet
Samsung Galaxy Unlock code eXtractor
(based on info by rhcp0112345 & RazvanG)
Opening file <nv_data.bin>...
Searching code block...
Found.
Searching codes...
Network Control Key: 00000000
E:\Generate Unlock Windows>sgux2 nv_data.jpc
SGUX v0.92b (C) 2010 By Mark0 & rbnet
Samsung Galaxy Unlock code eXtractor
(based on info by rhcp0112345 & RazvanG)
Opening file <nv_data.jpc>...
Searching code block...
Found.
Searching codes...
Network Control Key: 00000000
I've tried to get the code with : .nv_data.bak, nv_data.bin, nv_jpc and bml3.bak. In each case, I got the code 00000000.
I found this in a forum hope this will help
quiron said:
I flash & reflash several times, and still can´t resolve this.
I don't have any file with *bak* at this moment.
the files that I have:
# find /efs
find /efs
/efs
/efs/.android
/efs/.android/testAndroid1.bin
/efs/.android/testAndroid2.bin
/efs/.android/testAndroid3.bin
/efs/nv_data.bin
/efs/.imei
/efs/imei
/efs/imei/mps_code.dat
/efs/imei/bt.txt
/efs/imei/.nvmac.info
/efs/nv_data.bin.md5
/efs/.nv_state
/efs/nv_data.jpc
/efs/nv_data.jpc.md5
and de result to nv_data.bin:
E:\Generate Unlock Windows>sgux2 nv_data.bin
SGUX v0.92b (C) 2010 By Mark0 & rbnet
Samsung Galaxy Unlock code eXtractor
(based on info by rhcp0112345 & RazvanG)
Opening file <nv_data.bin>...
Searching code block...
Found.
Searching codes...
Network Control Key: 00000000
E:\Generate Unlock Windows>sgux2 nv_data.jpc
SGUX v0.92b (C) 2010 By Mark0 & rbnet
Samsung Galaxy Unlock code eXtractor
(based on info by rhcp0112345 & RazvanG)
Opening file <nv_data.jpc>...
Searching code block...
Found.
Searching codes...
Network Control Key: 00000000
Click to expand...
Click to collapse
same result here, followed the procedure, ended up with network code 00000000. any help?
If you need help on unlocking a 2.2 device. Please contact me.
can anybody post a link to which normal unlock files are needed, there are too many unlock files in the forum
rhcp0112345 said:
If you need help on unlocking a 2.2 device. Please contact me.
Click to expand...
Click to collapse
Yes I need it, and I am certainly not the only one.
Can you publish a guide how to proceed ?
I did manage to get rid of this bloody unlocking problem after 9 hours of struggle. I followed the advice here:
http://forum.xda-developers.com/showthread.php?p=7946031#post7946031
I don't know how it worked, I don't care how it worked, its just that now i have a full working sgs with jp3 froyo software installed.
Next rom will definitely be official froyo, no more flic-flacs for me till then.
Fallback after a KOR productcode modification by firmware JPC
I've found a solution to my KOR problem after a JPC firmware upgrade :
History:
I've upgraded my SGS to JPC firmware (2.2). My phone product code has been changed to GT-I9000HKDKOR. Since my phone is simlocked, my local SIM (SFR in France) is not the same model than the phone (KOR), so it asked me an unlock code. I found no code to remove the simlock protection (sgux computed a 00000000 unlock code).
Solution I found :
- Downgrade the SGS to the firmware JM6 (2.1).
- Downloade the file /efs/nv_data.bin to your PC/LINUX/MAC (your phone need to be rooted !).
- Open it in a hexeditor -in fact I've used Windows' notepad++- and search for the "KOR" sequence. This sequence appears 2 times in the bin file. These are nearby each others.
- Change back the KOR sequence to your original product code (this can be found in regedit CURRENT USER / Software / Samsung / Kies / DeviceDB / [a number] / ProductCode). For my personal case, it is a SFR (France) phone, my product code is GT-I9000HKDSFR and a few chars before change KOR by SFR (or whatever your op. code is).
- Then you have to compute a md5sum on the modified nv_data.bin and store the md5 in a file called nv_data.bin.md5. Make sure your md5 file is exactly 32 bytes long, there is no CR/LF at the end of the line. md5sum is available for any plateform, for myself I did it on my Linux box which is my SAN.
- Next step : push back these 2 files in your /efs/ directory and reboot.
To make sure nothing is altered during the reboot process, I've removed the battery to switch off the phone. At the next reboot, no more SIM unlock code request. I've been able to place a call, my phone is back to life !
Can someone takes some time to do this trick on a 2.2 froyo JPC firmware ?
Hope this will help others...
gouroufr2000 said:
I've found a solution to my KOR problem after a JPC firmware upgrade :
History:
I've upgraded my SGS to JPC firmware (2.2). My phone product code has been changed to GT-I9000HKDKOR. Since my phone is simlocked, my local SIM (SFR in France) is not the same model than the phone (KOR), so it asked me an unlock code. I found no code to remove the simlock protection (sgux computed a 00000000 unlock code).
Solution I found :
- Downgrade the SGS to the firmware JM6 (2.1).
- Downloade the file /efs/nv_data.bin to your PC/LINUX/MAC (your phone need to be rooted !).
- Open it in a hexeditor -in fact I've used Windows' notepad++- and search for the "KOR" sequence. This sequence appears 2 times in the bin file. These are nearby each others.
- Change back the KOR sequence to your original product code (this can be found in regedit CURRENT USER / Software / Samsung / Kies / DeviceDB / [a number] / ProductCode). For my personal case, it is a SFR (France) phone, my product code is GT-I9000HKDSFR and a few chars before change KOR by SFR (or whatever your op. code is).
- Then you have to compute a md5sum on the modified nv_data.bin and store the md5 in a file called nv_data.bin.md5. Make sure your md5 file is exactly 32 bytes long, there is no CR/LF at the end of the line. md5sum is available for any plateform, for myself I did it on my Linux box which is my SAN.
- Next step : push back these 2 files in your /efs/ directory and reboot.
To make sure nothing is altered during the reboot process, I've removed the battery to switch off the phone. At the next reboot, no more SIM unlock code request. I've been able to place a call, my phone is back to life !
Can someone takes some time to do this trick on a 2.2 froyo JPC firmware ?
Hope this will help others...
Click to expand...
Click to collapse
You sir are brilliant... back to O2U here! ) I only needed to change one key entry as could find only the one KOR in my nv_data.bin... but otherwise... perfect! )
Thank you SOOOO much... had started worrying that I'd not get my product code back!
It also means that a simlocked phone can be used with another SIM by modifying the same way the nv_data.bin...
Anyway I wont update this phone to JPC. I'll await the next one... JPD seems to be online but no infos yet on the status of this firmware.
in which line did you find the KOR?
i cant find it? >_<
Greg82uk said:
You sir are brilliant... back to O2U here! ) I only needed to change one key entry as could find only the one KOR in my nv_data.bin... but otherwise... perfect! )
Thank you SOOOO much... had started worrying that I'd not get my product code back!
Click to expand...
Click to collapse
I'm clueless here, would you mind posting a step by step including the software used?
gouroufr2000 said:
I've found a solution to my KOR problem after a JPC firmware upgrade :
History:
I've upgraded my SGS to JPC firmware (2.2). My phone product code has been changed to GT-I9000HKDKOR. Since my phone is simlocked, my local SIM (SFR in France) is not the same model than the phone (KOR), so it asked me an unlock code. I found no code to remove the simlock protection (sgux computed a 00000000 unlock code).
Solution I found :
- Downgrade the SGS to the firmware JM6 (2.1).
- Downloade the file /efs/nv_data.bin to your PC/LINUX/MAC (your phone need to be rooted !).
- Open it in a hexeditor -in fact I've used Windows' notepad++- and search for the "KOR" sequence. This sequence appears 2 times in the bin file. These are nearby each others.
- Change back the KOR sequence to your original product code (this can be found in regedit CURRENT USER / Software / Samsung / Kies / DeviceDB / [a number] / ProductCode). For my personal case, it is a SFR (France) phone, my product code is GT-I9000HKDSFR and a few chars before change KOR by SFR (or whatever your op. code is).
- Then you have to compute a md5sum on the modified nv_data.bin and store the md5 in a file called nv_data.bin.md5. Make sure your md5 file is exactly 32 bytes long, there is no CR/LF at the end of the line. md5sum is available for any plateform, for myself I did it on my Linux box which is my SAN.
- Next step : push back these 2 files in your /efs/ directory and reboot.
To make sure nothing is altered during the reboot process, I've removed the battery to switch off the phone. At the next reboot, no more SIM unlock code request. I've been able to place a call, my phone is back to life !
Can someone takes some time to do this trick on a 2.2 froyo JPC firmware ?
Hope this will help others...
Click to expand...
Click to collapse
Looks promising!
Does it have to be JM6 or can JM7 work as well ?
Can anyone with JPC and a locked phone try this and report if it works ?
If we go back to JM6 do the editing and fix the product code then back it up on the PC, update to JPC and push this back to the phone this should work right ?
Any news if its possible to restore the IMEI ?
Ok I'm stupid and I can't make a md5 file of 32 bytes with md5summer for windows, somebody can help me?
edit de file with notepad and delete the 1st 3 lines and the count 32 bytes and delete all the rest.
I tried with JM7 with CSC_I9000TMNJM1 and there is no KOR sequence in nv_data.bin FILE. instead was already TMN, but still asking me for de unlock code.
I tried with JPC and still don't work .
quiron said:
I tried with JM7 with CSC_I9000TMNJM1 and there is no KOR sequence in nv_data.bin FILE. instead was already TMN, but still asking me for de unlock code.
I tried with JPC and still don't work .
Click to expand...
Click to collapse
It means your phone is configured as TMN (dont know which country it is) but if it asks you for unlock code => your SIM is not TMN.
Change TMN to whatever your SIM is... Check in regedit for a history. Anyway downgrade to a previous firmware because JPC is suspected of breaking the nv_data.bin
I don't know if this trick works with another firmware, but theorically it should works the same way...
Nb: do not delete any line in your nv_data.bin ! This is a stupid remark, it can brick your phone.
the solution to 00000000 unlock code
finaly the solution to 00000000 unlock code
http://forum.xda-developers.com/showpost.php?p=7957950&postcount=10
or
http://forum.xda-developers.com/showthread.php?p=7957950&posted=1#post7957950
works to me.
Related
This NEEDS to be stickied in here so everyone can use it.
I copied this from the i9000 forum.
Ok before we get started I need to make this REALLY clear. This did not work for my i9000 at first…. I cannot guarantee you will find your code…. If your device freezes (to many attempts) I am sorry but I cannot be held responsible.
Using ADB
Step 1. – Get the file
You need to have root
Code:
adb shell
su
dd if=/dev/block/bml3 of=/sdcard/bml3.bak
mount USB storage and copy the file off the internal SD card
Step 2. – Find the code
Try this
Originally Posted by rbnet.it
Try this: http://www.multiupload.com/2IAYWWGF8A
It's a win32 executable. Run the program from command line with the blockdevice backup as parameter:
c:\sgux.exe bml3.bak
IT returns the unlock code fory your phone.
It's based on the tip posted on this thread by rhcp0112345.
It's works with european sgs.
Click to expand...
Click to collapse
OR
Open the file in a HEX editor
Search for SSNV
At the end of this block of data there should be a string of numbers
(my unlock code started at 0x18005a)
The format will be numbers.unlockcode.numbers
Step 3. – Enter the code
As far as I know the *#0111*code# and #7465625*638*Code# codes don’t work so you MUST
Power down your phone
Put in a SIM card from another carrier
Power up your phone
When it boots up it will ask for the unlock code that you found above
Step 4. – Flash back (IF THE CODE DIDN'T WORK)
Flash back to an older firmware (I9000XXJF7 with 513.pit worked for me)
Now enter the unlock code you generated in Step 2.
PLEASE give credit to
rhcp0112345 for finding the file and giving me (and others) a place to start
rbnet.it and marcopon for the cool utility to extract it
galaxysguy for starting the other thread and confirming that I was looking at the right code
Click to expand...
Click to collapse
Think this is the 3rd post I've seen on this, but this has been CONFIRMED to work!
sweet, just unlocked mine!! thanks guys!
ill make sure this gets stickied
Hi,
I have used this procedure but was unsuccessful since I don't have the SIM from another carrier? Which method did you use? also I am currently running JH3 firmware.
thanks
TZ
tzones said:
Hi,
I have used this procedure but was unsuccessful since I don't have the SIM from another carrier? Which method did you use? also I am currently running JH3 firmware.
thanks
TZ
Click to expand...
Click to collapse
you NEED another sim from another carrier to invoke the message to enter the unlock code.
Error: unable to find file <bml3.bak>. can some1 help? thx
i had sgux.exe and bml3.bak copy to drive c: "windows 7"
Yep, put an old no longer working TMobile sim in, it asked for my code and voila! worked like a champ.
file not found on JH3
_____________________
did a direct copy and paste of string from thread and it copied properly.
Unlocked successfully from JH3!!!!
Yeah *****es!!!!
akachay said:
Error: unable to find file <bml3.bak>. can some1 help? thx
i had sgux.exe and bml3.bak copy to drive c: "windows 7"
Click to expand...
Click to collapse
Krad said:
file not found on JH3
Click to expand...
Click to collapse
Remember after opening adb, type su enter
then
cat /efs/nv_data.bin >> /sdcard/nv_data.bin
mount your card, and transfer nv_data.bin along with sgux.exe to your c :\ drive
then open command prompt, and cd C:\ [ENTER]
C:\sgux.exe nv_data.bin [ENTER] and you should get your code.
Make sure you have su (superuser) working, you can tell if there's a #in the adb prompt
If there's no # in the adb prompt, then open adb, type su [ENTER] look at your phone, and wait for the Super User prompt to pop and enable/give permissions.
The Bishop said:
Yep, put an old no longer working TMobile sim in, it asked for my code and voila! worked like a champ.
Click to expand...
Click to collapse
Thanks for this mail since I was under the impression that it requires a working SIM. Can't believe that my phone is unlocked!!
nice guide... but why are there so many different unlock guides lol
Honestly, I just found a guide that I thought had the best instructions and made a thread about it, hoping that it would be stickied, becasue this does not need to fade away off the first page. If it were stickied, it'd be even better. I contacted the person over this board, but they have yet to reply.
Extracting the unlock code on Ubuntu
Once you get the file off of your phone you can use hexdump and grep to find the unlock code easily:
cat bml3.bak | hexdump -C | grep -A 10 SSN
Ideally we could figure out how to do this directly on the phone using busybox, but I haven't figure that out yet.
Bad ass! worked like a charm on JH3.
i need help, i havent been able to get my phone unlocked.
I've tried all the methods (except Paying for a code) and none have worked !!!
I tried this one and it gave me the code but when i put in the TMO sim and entered "the code" it came back as no good.
Now, sgux.exe states looking for code and then it moves to the next command line (as if it was finished) but it doesnt find the code.
Help me plz !!
PS: I got the files out of the phone, both the bml3.bak and the nv_data.bin !
for those of u having a very very hard time trying to unlock the phone after flashing the JPC rom , u must do this :
7. My Phone asks me for a Unlock Code. Product Code has changed to KOR. What to do?
- Your Phone have to be rooted! Busybox is required!
- Start->Run-> cmd
- Change to your SDK\tools Directory e.g cd C:\Program Files (x86)\Android SDK\tools
- adb shell
- su
- cd /efs
- ls -al
If now nv_data.bak AND nv_data.bak.md5 are displayed, do the next few steps marked with (a)
If now .nv_data.bak AND .nv_data.bak.md5 are displayed (dot before filenames), do the next few steps marked with (b).
(a)- mv nv_data.bin nv_data.jpc
(a)- mv nv_data.bin.md5 nv_data.jpc.md5
(a)- mv nv_data.bak nv_data.bin
(a)- mv nv_data.bak.md5 nv_data.bin.md5
(a)- reboot
(b)- mv nv_data.bin nv_data.jpc
(b)- mv nv_data.bin.md5 nv_data.jpc.md5
(b)- mv .nv_data.bak nv_data.bin
(b)- mv .nv_data.bak.md5 nv_data.bin.md5
(b)- reboot
Now your Phone shouldn´t ask for a Code.
after that u can unlock ur phone with the methods shown in this thread . even the unlock android apk works ! very good job developers ty. BAD BAD samsung setting us such a trap.
For me this method didn't work. following exact steps in (b), still asking Network Code, 00000000 was the extracted code but didn't work though.
So after 2 days of struggling this is what I did:
Note that some users warned that if the bak files are corrupted the system will recreate empty files, probably losing IMEI, but this was not my case
1. Flash by Odin to JM7 (I don't think the version matters as long is 2.1)
2. at this time Product code change back from KOR to original ORO, but still asking code
3. root
4. moving back /efs files active to bak, the system will recreate new ones due to moving, so no more active files
mv nv_data.bin .nv_data.bak
mv nv_data.bin.md5 .nv_data.bak.md5
at this time I can see a new nv_data.bin with a smaller size
5. reboot
now working, not asking code
Thanks for the Thread... Might just need it in a few hours
adi_g_s said:
For me this method didn't work. following exact steps in (b), still asking Network Code, 00000000 was the extracted code but didn't work though.
So after 2 days of struggling this is what I did:
Note that some users warned that if the bak files are corrupted the system will recreate empty files, probably losing IMEI, but this was not my case
1. Flash by Odin to JM7 (I don't think the version matters as long is 2.1)
2. at this time Product code change back from KOR to original ORO, but still asking code
3. root
4. moving back /efs files active to bak, the system will recreate new ones due to moving, so no more active files
mv nv_data.bin .nv_data.bak
mv nv_data.bin.md5 .nv_data.bak.md5
at this time I can see a new nv_data.bin with a smaller size
5. reboot
now working, not asking code
Click to expand...
Click to collapse
and did you manage to get the JPC back and unlocked then? I have managed to fix the SIM Network Unlock code problem in a similar way, but using a MoDaCo modded froyo ROM, based on JP3. Now I am considering getting back to JPC, because I saw some nice things in there, but afraid I might get into the same problem. How can we fix this problem and STILL be on JPC?
NOTE: I have tried to use the .apk to get the unlock code now in JP3 rom and with no network unlock and the result is:
Unlock code: NULL
Unfreeze code: NULL
Probably that means that my sgs is unlocked, but how can we find the unlock code, so we can use it in JPC after flash?
ionutz6 said:
and did you manage to get the JPC back and unlocked then? I have managed to fix the SIM Network Unlock code problem in a similar way, but using a MoDaCo modded froyo ROM, based on JP3. Now I am considering getting back to JPC, because I saw some nice things in there, but afraid I might get into the same problem. How can we fix this problem and STILL be on JPC?
Click to expand...
Click to collapse
I think you can use JPC as long as you keep it rooted. If it gets locked, you can do the above procedure (adb shell) and restore the nv_data files
If you need to know how to flash it already rooted, check the "JPC root inside" thread or the "Doc's RomMod JPC" thread. I'm going to test this myself tonight or tomorrow
Cheers m8s
Phk
Phk said:
I think you can use JPC as long as you keep it rooted. If it gets locked, you can do the above procedure (adb shell) and restore the nv_data files
If you need to know how to flash it already rooted, check the "JPC root inside" thread or the "Doc's RomMod JPC" thread. I'm going to test this myself tonight or tomorrow
Cheers m8s
Phk
Click to expand...
Click to collapse
I have tried pretty much ALL things found here in XDA related to JPC last night, in the 10-hour period when I was struggling to bring my sgs back to life. I have upgraded to JPC, rooted it, tried to use several methods to find the unlock code, tried the FAQ#7 from the HOWTO thread, did 1000 other things, nothing worked, Unlock code still present. Perhaps I missed some steps although I don;t think so. I've also downgraded to 2.1 JM6 and tried to get the unlock code here, no go. Still SIM Unlock Code required. Finally I have solved it by upgrading it to a froyo modded rom from modaco, already rooted and then applying the FAQ#7 instructions. Now I am in froyo JP3 (the modded rom from modaco) and pretty scared to try anything else, although I would very much like to get to JPC, since I saw some pretty nice enhancements.
Any thoughts based on this painful story?
adi_g_s said:
For me this method didn't work. following exact steps in (b), still asking Network Code, 00000000 was the extracted code but didn't work though.
So after 2 days of struggling this is what I did:
Note that some users warned that if the bak files are corrupted the system will recreate empty files, probably losing IMEI, but this was not my case
1. Flash by Odin to JM7 (I don't think the version matters as long is 2.1)
2. at this time Product code change back from KOR to original ORO, but still asking code
3. root
4. moving back /efs files active to bak, the system will recreate new ones due to moving, so no more active files
mv nv_data.bin .nv_data.bak
mv nv_data.bin.md5 .nv_data.bak.md5
at this time I can see a new nv_data.bin with a smaller size
5. reboot
now working, not asking code
Click to expand...
Click to collapse
so should i understand that you are now on JM7? How do you get back to JPC?
ionutz6 said:
and did you manage to get the JPC back and unlocked then? I have managed to fix the SIM Network Unlock code problem in a similar way, but using a MoDaCo modded froyo ROM, based on JP3. Now I am considering getting back to JPC, because I saw some nice things in there, but afraid I might get into the same problem. How can we fix this problem and STILL be on JPC??
Click to expand...
Click to collapse
yes now i am on jpc ,and if it decides to ask for a code i have the codes now.
ionutz6 said:
so should i understand that you are now on JM7? How do you get back to JPC?
Click to expand...
Click to collapse
yes I'm on JM7, now the unlock.apk gives me Unlock Code:NULL
I'm hoping that my phone is unlocked now, so Froyo will not ask the code anymore
but IMEI was rewritten by with value 004999... and I have trouble with Market, cannot download.
how to recover my IMEI now?
Many many many thanks
adi_g_s said:
For me this method didn't work. following exact steps in (b), still asking Network Code, 00000000 was the extracted code but didn't work though.
So after 2 days of struggling this is what I did:
Note that some users warned that if the bak files are corrupted the system will recreate empty files, probably losing IMEI, but this was not my case
1. Flash by Odin to JM7 (I don't think the version matters as long is 2.1)
2. at this time Product code change back from KOR to original ORO, but still asking code
3. root
4. moving back /efs files active to bak, the system will recreate new ones due to moving, so no more active files
mv nv_data.bin .nv_data.bak
mv nv_data.bin.md5 .nv_data.bak.md5
at this time I can see a new nv_data.bin with a smaller size
5. reboot
now working, not asking code
Click to expand...
Click to collapse
Finaly I have my phone back. just had to do something else.
I have to edit the file efs/imei/mps_code.dat and change de "KOR" to "TMN". Then I rename the files as mentioned, and my phone came to life.
adi_g_s you're a hero.
adi_g_s said:
yes I'm on JM7, now the unlock.apk gives me Unlock Code:NULL
I'm hoping that my phone is unlocked now, so Froyo will not ask the code anymore
but IMEI was rewritten by with value 004999... and I have trouble with Market, cannot download.
how to recover my IMEI now?
Click to expand...
Click to collapse
I have the exact same behaviour, with Unlock code: NULL, IMEi starting with 004999.. etc. The only thing is that download from market is working ok.
would you care to upgrade now to JPC and see if it requests the unlock code again? I don;t believe that the fact that it looks unlocked now will mean after installing JPC you will have the same condition. Mine was unlocked before trying JPC, as far as I know.
man, i am confused...
I want to give the method by adi_g_s a try but im afraid if I reflash back to JPC it might forever lock my phone.. the unlock APK also sees it as null/null. Right now im with JPC and its unlocked..
adi_g_s said:
For me this method didn't work. following exact steps in (b), still asking Network Code, 00000000 was the extracted code but didn't work though.
So after 2 days of struggling this is what I did:
Note that some users warned that if the bak files are corrupted the system will recreate empty files, probably losing IMEI, but this was not my case
1. Flash by Odin to JM7 (I don't think the version matters as long is 2.1)
2. at this time Product code change back from KOR to original ORO, but still asking code
3. root
4. moving back /efs files active to bak, the system will recreate new ones due to moving, so no more active files
mv nv_data.bin .nv_data.bak
mv nv_data.bin.md5 .nv_data.bak.md5
at this time I can see a new nv_data.bin with a smaller size
5. reboot
now working, not asking code
Click to expand...
Click to collapse
If i flash back to 2.1 and I still get the KOR product code.. I wont be doing the other extra steps right ?
and If i flash back to JPC, should I expect my phone to be asking for an unlock code again ?
EDIT:
and I made a backup of my:
nv_data.bak
nv_data.bin
nv_data.bin.md5
nv_data.jpc
nv_data.jpc.md5
all of these are from POST JPC, so I guess im ready to screw around and flash to JM7 and see if i can get my product code back and if not I can just relfash to JPC again and restore these files so it wont be asking for an unlock code anymore right ?
adi_g_s said:
yes I'm on JM7, now the unlock.apk gives me Unlock Code:NULL
I'm hoping that my phone is unlocked now, so Froyo will not ask the code anymore
but IMEI was rewritten by with value 004999... and I have trouble with Market, cannot download.
how to recover my IMEI now?
Click to expand...
Click to collapse
There is a file in /efs/imei/ folder that contains the imei. if you have a original box perhaps you find there imei written, and that way you can try editing that file and place your original IMEI.
If you updated with the beta froyo 2.2 your PRODUCTCODE may have changed.
you can verify this with SGS tools (rooted of course)
or when your phone is plugged in and kies mini running (most likely with the error unregistered device) open regedit and look under
HK_current_user\Software\Samsung\KiesMini\FUS
PRODUCTCODE SHOULD READ SGH-I897ZKAATT not SGH-I897ZKAKOR
FOR THIS BE VERY CAREFULL MAKE BACKUPS !!!!!!!!
to fix this you need to pull /efs/nv_data.bin with ADB or copy it with root explorer
open nv_data.bin with a handy hex editor and change SGH-I897ZKAKOR to SGH-I897ZKAATT
if you have .nv_data.bak you should check that too.
hey guys
when i double click on Generate_Code.bat
than it show me this error..
===========================================================================
===========================================================================
AUTO-Extract Un-FREEZE
'Network' is not recognized as an internal or external command,
operable program or batch file.
===========================================================================
===========================================================================
__________________________________________________________
Copy nv_data.bin
* daemon not running. starting it now *
* daemon started successfully *
failed to copy '/efs/nv_data.bin' to './nv_data.bin': Permission denied
Extract code
SGUX v0.92b (C) 2010 By Mark0 & rbnet
Samsung Galaxy Unlock code eXtractor
(based on info by rhcp0112345 & RazvanG)
* Error: unable to find file <.\nv_data.bin>
===============================================================================
===============================================================================
Please donate to RazvanG for this script file
Please donate to rbnet.it and marcopon for the SGUX2 utility used in the script
===============================================================================
===============================================================================
Script complete!
Press any key to continue . . .
is there any wrong steps??
i have rooted my phone but still same..
is there any nv_data.bin file needed?? and where get that file and where to put that file??
and my usb debbugging is on
reply and help me for unlock my 2.2 galaxy s
Why dont you PM RazvanZ?
Sent from my GT-I9000 using XDA App
i get the same message, I have no idea what goes wrong... I tried the app and the windows generator on 4 different firmwares on my new galaxy S (2.1, 2.2, 2.2.1)
It doesn't work on my I9000
Well it don't work on froyo.
**Using my own JPX kernel, z4mod, 345MB Ram and ext2 filesystem**
Is it possible it won't work on modified ROMs?
I unlocked my SGS last week when I was on the stock Bell JL2 (Froyo) ROM. Here is the nv_data.bin file from my phone. I have no idea if this file is phone specific, but if you find out it will work, use it.
http://www.filedude.com/download/5CgOd4aq1i1ac09cf150
Read this tutorial on unlocking the SGS.
http://forum.cyanogenmod.com/topic/4999-howto-sim-unlock-your-vibrant-galaxy-s/
Ian
CAN ANYONE HELP ME UNLOCK MY T MOBILE GALAXY FOR THE NETWORK PASS CODE KEY TO USE WITH DIFFERENT SERVICE.....MAYBE WITH THE USB CORD WAY 1ST
helroz said:
keep the backup is a safety
If you have froyo on your phone, only solution: (or samsung for repair)
http://perso.numericable.fr/helroz/Perso/repair_nv_data.zip
this method give informations in your bad nv_data.bin (imei, Model, product code) and insert this in a new nv_data.bin (sim unlocked).
After this new nv_data.bin (sim unlocked with your informations) is inserted in your phone, at restart, your phone create nv_data.bin.md5 and batch file create .nv_data.bak and .nv_data.bak.md5 and save your new efs folder.
Your phone is unlocked
It's possible to made this on froyo but not advised and not really tested (I repair codes at the same time but at the first start froyo change codes by FFFFFFFF)
Thanks to Mikiya on Frandroid to made "Reparation_nv_data.jar" at my demand
Thanks to vnamee for detailled instructions:
Just did this on my phone and it works great. The SGS unlock tool gave me a number that did not work no matter what firmware I used. Here are the steps to perform the unlock.
You will need root and busybox and something to edit the root, such as Root Explorer or ADB. You will need Java on your PC as well.
1) Copy the EFS folder with Root Explorer or ADB to back up
2) In /efs, delete:
nv_data.bin.md5
.nv_data.bak
.nv_data.bak.md5
nv_data.JPC (you may not have this)
nv_data.JPC.md5 (you may not have this)
.nv2.bak
.nv2.bak.md5
3) Reboot your phone and navigate to /efs to see if nv_data.bin.md5 is created. If it is, you are good to go. If you go there right after the phone boots, it may not have been created yet.
4) Put your phone in USB debug mode and connect via USB to computer.
5) Run step 2.bat (this will extract nv_data.bin to your computer)
6) Run reparation_nv_data.jar (I guess you just enter any 8 digit number in the boxes that will be your unlock code. I had entered '00000000' and SGS unlock couldn't find anything afterward, so I'm not sure if this number will be needed at any point in the future. This will edit the nv_data.bin).
7) Run Step 4.bat (this will upload the files to your phone. Make sure the phone is on and when you run it, make sure to keep pressing 'allow' so the program has root access to push the files to your root).
8) After this is done, you can answer 'n' if there were no errors and it should reboot your phone. Phone should be unlocked.
Phone must have nv_data in /efs folder, with all firmware, if at start you don't have nv_data, phone create it, but generic with no imei.
Click to expand...
Click to collapse
here is the thread for that, http://forum.xda-developers.com/showthread.php?t=822008
Or the simple way, use this app to unlock
https://market.android.com/details?id=com.helroz.galaxysunlock&feature=search_result
Make sure you read through the instructions.
check here
u should check here it helped me unlock my phone last week
http://forum.xda-developers.com/showthread.php?t=761045
it was confusing at first for me but it was pretty simple all the instructions are there if u have any problems u can leave a post and some will help out
I just used this application, worked fine. I rooted my phone first just to let you know.
https://market.android.com/details?id=com.clarkehackworth.SamsungGalaxySUnlock&feature=search_result
iynfynity said:
here is the thread for that, http://forum.xda-developers.com/showthread.php?t=822008
Click to expand...
Click to collapse
This method helped me unlock my phone when the sgs unlocker failed to extract the unlock code. It kept saying "unlock codek". The above method maybe a lilttle tricky for beginners, first back up your efs folder and try it.
MilkPudding said:
Or the simple way, use this app to unlock
https://market.android.com/details?id=com.helroz.galaxysunlock&feature=search_result
Make sure you read through the instructions.
Click to expand...
Click to collapse
This didn't work for me
m4r10 said:
This didn't work for me
Click to expand...
Click to collapse
Ya it won't work if you didn't read through the instructions.