FORUMS

OnePlus 2 Announced: Specs, Price and Details

The OnePlus 2 has just had its Virtual Reality Launch event, and at the XDA Office we all … more

A Helpful Guide to Music Streaming Services

With the launch of Apple Music, music streaming services have recently gained a lot of … more

An Inside Look at the Redesign of Business Calendar

The much-acclaimed calendar app, Business Calendar, underwent a major design … more

New Android One Device Dead On Arrival

Today, Google announced the second generation of Android One devices, with the new Lava Pixel … more

[HOWTO] GT-I9100 Free SIM Unlock via nv_data.bin by Odia

662 posts
Thanks Meter: 775
 
By Odia, Guest on 5th May 2011, 05:33 PM
Post Reply Subscribe to Thread Email Thread
7th May 2011, 05:54 PM |#21  
pulser_g2's Avatar
Developer Admin / Senior Recognized Developer
Thanks Meter: 11,363
 
More
OK. Is anyone there with an SGS II and bored, wanting to try something out (your own risk obviously, though this seems safe as someone has tested parts of it already)

It seems to be safe to modify this file, so long as you take a backup of anything you are about to mess with. I would suggest taking 2 backups, just in case...

If so, get a hex editor and look at address 0x181468 (that is in hex). If you are locked, you should see "FF 01". If you are unlocked, you should see "FF 00".

1) Can people confirm this to be true? In my limited sample, it's true.

2) If you change that to "FF 00", and replace the file (with backup), does it work as unlocked, or does it just not recognise the radio?

3) If not working, restore the file you created, and delete the nv_data.md5 file (be sure to back it up as well before doing anything). Again see if it works.

4) If you don't get your unlock sorted (if you do, free unlock and congrats, please let us know what you did), then restore the old files and you should be back to normal.

Also... If you feel really bored, how about dumping the nv_data.bin BEFORE and AFTER flashing a kernel via ODIN, such that the counter on download mode increments. The idea being to see if this file changes when flashed... Obviously you need to label the before and after clearly, and give the value of the number for before and after

For emailing any nv_data files to me, my email is:
 
 
7th May 2011, 06:25 PM |#22  
dh2311's Avatar
Senior Member
Flag Liverpool
Thanks Meter: 278
 
Donate to Me
More
Right.

Cant confirm 1) as mine is locked

As for 2 edited ff 01 to ff 00 and sim is undetected like before (get no service). Pushed backup back and it worked


I have removed the .md5 and i hope it still works (forgot to back up)

EDIT: Works after deleting.

As for unlock. I might buy a code, then run a comarison check between my old nv data and new one and look for all edits
7th May 2011, 07:00 PM |#23  
pulser_g2's Avatar
Developer Admin / Senior Recognized Developer
Thanks Meter: 11,363
 
More
Quote:
Originally Posted by dh2311

Right.

Cant confirm 1) as mine is locked

As for 2 edited ff 01 to ff 00 and sim is undetected like before (get no service). Pushed backup back and it worked


I have removed the .md5 and i hope it still works (forgot to back up)

EDIT: Works after deleting.

As for unlock. I might buy a code, then run a comarison check between my old nv data and new one and look for all edits

That would be interesting to get a before/after.

You did double check you did the RIGHT offset changing 01 to 00, given there are a number of FF FF FF FF FF 01 00 00 00 blocks in the file? Just double checking

The md5 should be re-generated after a boot (normally)

How many times have you flashed your device, and do you fancy another flash to see if we can spot this counter? It's a long-shot, so if you aren't planning to flash anything, there's little point in testing it tbh...
7th May 2011, 07:01 PM |#24  
pulser_g2's Avatar
Developer Admin / Senior Recognized Developer
Thanks Meter: 11,363
 
More
Quote:
Originally Posted by dh2311

Right.

Cant confirm 1) as mine is locked

As for 2 edited ff 01 to ff 00 and sim is undetected like before (get no service). Pushed backup back and it worked


I have removed the .md5 and i hope it still works (forgot to back up)

EDIT: Works after deleting.

As for unlock. I might buy a code, then run a comarison check between my old nv data and new one and look for all edits

Also, to clarify, I meant to delete the md5sum file if you couldn't get it working with the modified file. I was thinking that the MD5 was being checked due to unlock status changing? Just a long-shot...
7th May 2011, 08:14 PM |#25  
dh2311's Avatar
Senior Member
Flag Liverpool
Thanks Meter: 278
 
Donate to Me
More
Quote:
Originally Posted by pulser_g2

Also, to clarify, I meant to delete the md5sum file if you couldn't get it working with the modified file. I was thinking that the MD5 was being checked due to unlock status changing? Just a long-shot...

Ohh.. I was doing that anyway, I followed the tut for the origional galaxy s to do it coz thats how i unlocked my sgs.


as for bootloader count, seems random to be stored in nv_data, but I'll flash supercurios kernel again and do a comparison, see if anything differs. Will keep em both and email to you if theres anything to look at
7th May 2011, 08:15 PM |#26  
pulser_g2's Avatar
Developer Admin / Senior Recognized Developer
Thanks Meter: 11,363
 
More
Quote:
Originally Posted by dh2311

Ohh.. I was doing that anyway, I followed the tut for the origional galaxy s to do it coz thats how i unlocked my sgs.


as for bootloader count, seems random to be stored in nv_data, but I'll flash supercurios kernel again and do a comparison, see if anything differs. Will keep em both and email to you if theres anything to look at

Thanks. I have been told by Mathieulh on IRC that it is stored in that file, but it might be encrypted...
7th May 2011, 08:20 PM |#27  
Senior Member
Thanks Meter: 149
 
More
Quote:
Originally Posted by pulser_g2

Thanks. I have been told by Mathieulh on IRC that it is stored in that file, but it might be encrypted...

Oh one of the famous PSP crackers. Didn't know he was in android phones!
7th May 2011, 08:47 PM |#28  
dh2311's Avatar
Senior Member
Flag Liverpool
Thanks Meter: 278
 
Donate to Me
More
Done a comparison using HXD, only one set of changes, between lines 0003C800 and 0003C840.

First one showed all F's after flash all changed, but nothing related to flash count
7th May 2011, 08:53 PM |#29  
pulser_g2's Avatar
Developer Admin / Senior Recognized Developer
Thanks Meter: 11,363
 
More
Quote:
Originally Posted by dh2311

Done a comparison using HXD, only one set of changes, between lines 0003C800 and 0003C840.

First one showed all F's after flash all changed, but nothing related to flash count

Right. We believe if you restore the backup, the flash count will reduce again. You want to try that?
7th May 2011, 08:58 PM |#30  
dh2311's Avatar
Senior Member
Flag Liverpool
Thanks Meter: 278
 
Donate to Me
More
I had the same thought before seeing that post. Doesnt work. Still at the same count (6)
7th May 2011, 09:13 PM |#31  
Senior Member
Flag Surrey
Thanks Meter: 13
 
More
**DO THIS AT YOUR OWN RISK**

there's something else you may want to try, but it's kinda dangerous. I did this with the original SGS when I got a unit that the unlocker couldn't find an unlock code for.

back up nv_data.bin and the md5 somewhere safe (you do not want to lose this!)
delete it nv_data.bin
reboot the phone
the phone will generate a new nv_data.bit with new strings and a dummy IMEI
plug in a sim and the phone should be unlocked

if you need to send in the phone for anything, just restore original nv_data.bin.

**DO THIS AT YOUR OWN RISK**
Last edited by aridoasis; 7th May 2011 at 09:16 PM.

Read More
Post Reply Subscribe to Thread

Tags
galaxy s2, rom
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes