Originally Posted by helroz

for information:

galaxy s unlock work because lockbites are a the same adress (on I9000 and I9100).

lockbites adress of I9000 on the first page is wrong.

Thats because they are not lockbites as you call them (lock flags) they are unlock code HASH (SHA1) locations. Not make stupid comments if you not know what you are talking about. Lock flags are at 0x181469 - 0x18146d, but here we deal in real solution, not just bit flipping.

if i make stupid comments, see my program on the market, i unlock galaxy s since 08/2010 and i unlock galaxy s II with the same method (and exactly same command lines) and it work.....

my rate is at 4,5/5 on the market with +100.000 downloads and worked comments on new I9100 (without unlock solution).

This is not the most natural method but it work fine.

but sure... i'm really stupid....

---------- Post added at 01:37 PM ---------- Previous post was at 01:17 PM ----------

This is a link of screen of I9000 nv_data.bin:



see if at 18154b you have anything....


but this is a i9100 section, i stop to speak to I9000 here


Edit:

If you want to made an unlock without "change lockbite", test this, it's work on I9000 and possibly work on I9100:

- Save your efs folder
- Delete your nv_data.bin, .nv_data.bak and md5 files associated
- Reboot (your phone create generic nv_data.bin file unlocked and his md5)
- Extract your crypted imei and product code of your nv_data.bin saved and insert it in your nv_data.bin "generic" and delete generic md5.
- Reboot
- Rename nv_data.bin and his md5 to. nv_data.bak and his md5.
- Reboot

after you have really unlocked files without any lockbite change or needeed unlock code...

But i'm not sure this method work on I9100, only tested on I9000.

Originally Posted by helroz

if i make stupid comments, see my program on the market, i unlock galaxy s since 08/2010 and i unlock galaxy s II with the same method (and exactly same command lines) and it work.....

my rate is at 4,5/5 on the market with +100.000 downloads and worked comments on new I9100 (without unlock solution).

This is not the most natural method but it work fine.

but sure... i'm really stupid....

---------- Post added at 01:37 PM ---------- Previous post was at 01:17 PM ----------

This is a link of screen of I9000 nv_data.bin:



see if at 18154b you have anything....


but this is a i9100 section, i stop to speak to I9000 here


Edit:

If you want to made an unlock without "change lockbite", test this, it's work on I9000 and possibly work on I9100:

- Save your efs folder
- Delete your nv_data.bin, .nv_data.bak and md5 files associated
- Reboot (your phone create generic nv_data.bin file unlocked and his md5)
- Extract your crypted imei and product code of your nv_data.bin saved and insert it in your nv_data.bin "generic" and delete generic md5.
- Reboot
- Rename nv_data.bin and his md5 to. nv_data.bak and his md5.
- Reboot

after you have really unlocked files without any lockbite change or needeed unlock code...

But i'm not sure this method work on I9100, only tested on I9000.

helroz, we seem to be in a battle here and that was not my intention, when I said stupid comment I was refering to your mix of lock flags and lock hashes. I have no doubt your bit flipping solution works, but Samsung incorporated a system to enter unlock codes and generating these codes is the real solution.

I have attached 2 screendumps to show the hash location on I9000 with new simlock protection, here you can also see the 8x 46 which is the hash migration data marker. One image has been edited because it gives out too much information.

About deleting all nv_data and copies and allowing the modem to create default, then injecting back the secure info (I say secure info because its not just crypted IMEI), it would probably work, but what happened to the radio calibration data? It got lost when default nv_data was used, again not a real solution.

I already know how to put any Samsung Android phone into factory mode and can reprogram it, this can be used to fix defaulted IMEI etc, I also have a very good understanding of the nv_data file.

Originally Posted by lilizblack

I found other methods to unlock the S2 if Odia's method or Chainfire's app fails.

I had the problem that the app and Odia's method couldnt find a code in the phone.

This is what i did and I tested on five S2 before posting and they all worked! Similar to the vibrant. NOTE: Claro PR users with S2 must re flash a stock debrand version because claro's programming doesnt allow to unlock phone via code. I havent tried this method directly from Claros original programming. I Always flash the phone to debrand firmwares.

1. After root open command prompt and navigate to the Android sdk folder.

cd (location to the android sdk folder)

2. Now enter the following code one by one to ensure its working!

adb shell
su (this will ask for permission on the phone so keep the screen on. if not reboot the phone and start again)
cat /efs/nv_data.bin >> /sdcard/nv_data.bin

Dont close CMD Prompt yet!

3. Mount SD card. MAKE A COPY OF THE NV_DATA.BIN. Next use a hex editor and search for SSNV. Scroll down untill you see address 00181460h (or something similar). In there you will see FF FF FF and then it will change from FF to 01 00 00 00 etc. Change the 01 to 00 and save.

4. Unmount SD card and go back to command prompt and enter one by one:

su
rm /efs/nv_data.bin
cat /sdcard/nv_data.bin >> /efs/nv_data.bin
chmod 755 /efs/nv_data.bin
chown radio.radio /efs/nv_data.bin || chown 1001.1001 /efs/nv_data.bin
reboot

5. After reboot if it ask for unlock code. Go back to command prompt:

adb shell
su
rm /efs/nv_data.bin
reboot

6. Dance! At reboot it will no longer ask for code and will start searching for network!

As i said Ive try this almost an entire week on my work when the Searching Unlock code Fails or when unlock code is invalid. Sorry for my spelling mistakes^^

When i write the cd promt and after hit the enter it says HOME nost set. What now?

With astro file manager i find the nv data.bin file, copied and with a hexeditor i changed the code where the ff turns to 01...now I have to copy this file to the efs folder, which is empty but i cant copy it...help me

Originally Posted by materijalmen

When i write the cd promt and after hit the enter it says HOME nost set. What now?

With astro file manager i find the nv data.bin file, copied and with a hexeditor i changed the code where the ff turns to 01...now I have to copy this file to the efs folder, which is empty but i cant copy it...help me

Use galaxy s unlock from market. It is compatible with sgs2 and will save you a lot of work and i can confirm it does the job too

Sent from my GT-I9100 using xda premium

Originally Posted by zylor

Use galaxy s unlock from market. It is compatible with sgs2 and will save you a lot of work and i can confirm it does the job too

Sent from my GT-I9100 using xda premium

Works for my GS2 too from Bell network.

ok... new nv_data have other informations, i don't have this one.

i don't search to launch a battle, i prefer the unlock by code but if you find "the code" and samsung change it, this is a chain without end...

it's not possible to unlock phones one by one, at the end you have 100 mails/day for help "tested by me at the begining"

If you search any solution, search a universal solution, this only one is good...

All people don't test 1,2,3,4 program, if one work, all users use this one and for most people the time is really important.

Modify phone in factory mode is a good idea but need to create a automatic method, if you don't made this 1 user/10 brick his phone.


Flip lockbite is not natural, but it's universal and it's work without any problem.
Ok i don't use the code and the window but the result is not good? (phones don't have any problem).

Originally Posted by zylor

Use galaxy s unlock from market. It is compatible with sgs2 and will save you a lot of work and i can confirm it does the job too

Sent from my GT-I9100 using xda premium

No, for me doesnt work because mine is probably with the new lock code. But i told in my post, that i found the nv data.bin file, fliped with hexeditor the 01 to 00, but i my efs folder is EMPTY.
I asked, how to install the android sdk, because probably i have something to copy from that to my phone...

Or something similar. Not all phone shows the exact thing. As long as you see the numbers 181460 in one address and you'll see the ffffff line and a 01 00 00 etc.

Sent from my Nexus S 4G using XDA App

Originally Posted by lilizblack

Or something similar. Not all phone shows the exact thing. As long as you see the numbers 181460 in one address and you'll see the ffffff line and a 01 00 00 etc.

Sent from my Nexus S 4G using XDA App

what????i just wonder why i didnt get still any help....