FORUMS
Remove All Ads from XDA

[REF] How to restore original product code!

52 posts
Thanks Meter: 2
 
By Methyldioxide, Member on 11th September 2010, 12:31 PM
Post Reply Email Thread
Hi,

So i coulden't wait and had to try out JPC firmware. Personally i didn't like it at all, so i went back to JM7. 1 thing i did not like is my product code changed from XEN to KOR.

And here is how to fix that easly:

I tested this on 2.1 cause i was on JM7 when i found this out, but this works with JPC/JPH also.
this fix is for those who do not have (correct) .bak files in the /efs/ directory!


- First make sure you are ROOT and install a Terminal Emulator (can be found in the market)
- Now open the Terminal, enter ''su'' to gain root access
- Enter: cp /efs/nv_data.bin /sdcard/
- Connect you're SGS to the usb and download ''nv_data.bin'' to your computer
- Open ''nv_data.bin'' with notepad or wordpad and search for ''KOR'' change this to the product code matching your country (red marked text should be changed). Im dutch, so mine is XEN. The line looks like this:
Code:
ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿMP 0.800  ÿKOR    GT-I9000HKDKOR
- Now simply save your changes.
- Connect your SGS with usb, upload ''nv_data.bin'' to internal sdcard.
- Disconnect USB !
- Open Terminal Emulator and enter ''su''
- Now enter: cp /sdcard/nv_data.bin /efs/nv_data.bin
Also enter: rm -rf /efs/nv_data.bin.md5
- Close terminal, Reboot Phone. And Voila!!! Product Code restored!!

**IF YOUR SIMCARD DOESN'T WORK AFTER THIS, EXECUTE THE FOLLOWING**
- adb shell
- su
- busybox chown 1001:1001 /efs/nv_data.bin
- reboot

You can also do this from the Terminal Emulator if you don't have ADB on your PC! Like this:

-su
-chown 1001:1001 /efs/nv_data.bin
-reboot

I hope it's easy to follow my steps, it works guaranteed.


UPDATE - 13/09

Some people say you don't have to create a new md5, just remove the old one on the phone. kaffre and i tested this, the phone recreates the md5 file for you. So i've updated the steps in my tutorial, to make it even more easy!

UPDATE - 15/09

Simcard fix added. Thanks to tokinux
The Following 2 Users Say Thank You to Methyldioxide For This Useful Post: [ View ] Gift Methyldioxide Ad-Free
 
 
11th September 2010, 12:59 PM |#2  
Member
Thanks Meter: 2
 
More
I`d suggest using a hex editor instead of any wordpad/notepad editor ...
11th September 2010, 01:19 PM |#3  
Senior Member
Thanks Meter: 0
 
More
Quote:
Originally Posted by Methyldioxide

Hi,

So i coulden't wait and had to try out JPC firmware. Personally i didn't like it at all, so i went back to JM7. 1 thing i did not like is my product code changed from XEN to KOR.

So f*ck that and here is how to fix that easly:

I tested this on 2.1 cause i was on JM7 when i found this out, but im 99% sure this works with JPC also.

- First make sure you are ROOT and install a Terminal Emulator (can be found in the market)
- Now open the Terminal, enter ''su'' to gain root access
- Enter: cp /efs/nv_data.bin /sdcard/
- Connect you're SGS to the usb and download ''nv_data.bin'' to your computer
- Open ''nv_data.bin'' with notepad or wordpad and search for ''KOR'' change this to the product code matching your country. Im dutch, so mine is XEN. The line looks like this:

Code:
ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿMP 0.800  ÿKOR    GT-I9000HKDKOR
- Now simply save your changes.
- Download a md5 creator tool, i use MD5SUMMER
- Create a MD5 file using ''nv_data.bin" and save this as ''nv_data.bin.md5''
- Open ''nv_data.bin.md5'' with notepad and delete all the lines beside the line wich is similar to this one: 4ba37998243f14158884c5f464933398 (ofcourse your line of numbers is different ! ) Save the md5 file.
- Now your md5 file should be exactly 32bytes (this is the same size of the md5 file used by samsung, so please follow this step carefully)

- Connect your SGS with usb, upload ''nv_data.bin.md5'' and ''nv_data.bin'' to internal sdcard.
- Disconnect USB !
- Open Terminal Emulator and enter ''su''
- Now enter: cp /sdcard/nv_data.bin.md5 /efs/nv_data.bin.md5
cp /sdcard/nv_data.bin /efs/nv_data.bin
- Close terminal, Reboot Phone. And Voila!!! Product Code restored!!

I hope it's easy to follow my steps, it works guaranteed.

editing those files is there a risk of changing the IMEI in 004999010640000 ??

i think something similar happened to me and now i'm with XXXXXXX as product code and that fake IMEI.......
11th September 2010, 02:21 PM |#4  
OP Member
Thanks Meter: 2
 
More
Quote:
Originally Posted by Narcissus85

editing those files is there a risk of changing the IMEI in 004999010640000 ??

i think something similar happened to me and now i'm with XXXXXXX as product code and that fake IMEI.......

My imei did never change, also not after product code restore
11th September 2010, 02:54 PM |#5  
Senior Member
Flag Wilhelmshaven
Thanks Meter: 147
 
Donate to Me
More
For me it seems to be easier to do it with the *#272*hhmm#* solution.
Read about this here: http://forum.xda-developers.com/showthread.php?t=779580

Its doing also a hardreset.. so backup you data!

In case you dont want a hard-reset, this manual solution is much better! So Thx, Methyldioxide for your work and sharing with us!
11th September 2010, 03:39 PM |#6  
Member
Thanks Meter: 1
 
More
Quote:
Originally Posted by Donald Nice

For me it seems to be easier to do it with the *#272*hhmm#* solution.
Read about this here: http://forum.xda-developers.com/showthread.php?t=779580

Its doing also a hardreset.. so backup you data!

In case you dont want a hard-reset, this manual solution is much better! So Thx, Methyldioxide for your work and sharing with us!

but his doesnt change the product code! i did it and still is KOR.
what is true is that putting the right csc is making my phone act like a normal one so at the end having a KOR phone gives me no problems at the moment...
11th September 2010, 04:10 PM |#7  
OP Member
Thanks Meter: 2
 
More
Quote:
Originally Posted by Donald Nice

For me it seems to be easier to do it with the *#272*hhmm#* solution.
Read about this here: http://forum.xda-developers.com/showthread.php?t=779580

Its doing also a hardreset.. so backup you data!

In case you dont want a hard-reset, this manual solution is much better! So Thx, Methyldioxide for your work and sharing with us!

*#272*hhmm#* only changes the CSC settings indeed, not the actual product code. With warrenty this can be an issue. So i preffer my original product code
11th September 2010, 05:35 PM |#8  
Junior Member
Flag Portsmouth
Thanks Meter: 0
 
More
Did this actually change the product code or did your Galaxy S replace the changed nv_data.bin file from the backup .nv_data.bak file?

The default action is to use the bak file to write a new nv_data.bin if the original is missing or corrupt. If your original .nv_data.bak still had the original code in it this could be what happened.
11th September 2010, 06:18 PM |#9  
Senior Member
Thanks Meter: 8
 
Donate to Me
More
I´ve copied my original nv_data.bin and nv_data.bin.md5 to my pc und used md5summer to check if the md5 hash stored in nv_data.bin.md5 is a normal md5 hash of the filesize.
The Hash generated with md5summer didn´t match!!!

Seems to be not an normal md5 hash of the filesize. There must be more.

If i do steps from OP the product code of my phone changes to XXXXXXXX.
Have used an Hex Editor and md5summer. Also tried WinMD5, same ****.
11th September 2010, 06:23 PM |#10  
OP Member
Thanks Meter: 2
 
More
Quote:
Originally Posted by Aery

I´ve copied my original nv_data.bin and nv_data.bin.md5 to my pc und used md5summer to check if the md5 hash stored in nv_data.bin.md5 is a normal md5 hash of the filesize.
The Hash generated with md5summer didn´t match!!!

Seems to be not an normal md5 hash of the filesize. There must be more.

If i do steps from OP the product code of my phone changes to XXXXXXXX.
Have used an Hex Editor and md5summer. Also tried WinMD5, same ****.

You dont read proper, plz read the steps carefully and you will create the correct md5 hash. I think your problem is that you did not open nv_data.bin.md5 after you generated it and deleted all lines beside the HASH line. This all is stated clearly in my steps, and you shouldent have any issue.

EDIT: The nv_data.bin.md5 you generated should be exactly 32bytes! else you did not follow my steps properly
11th September 2010, 06:28 PM |#11  
OP Member
Thanks Meter: 2
 
More
Quote:
Originally Posted by ghostgull

Did this actually change the product code or did your Galaxy S replace the changed nv_data.bin file from the backup .nv_data.bak file?

The default action is to use the bak file to write a new nv_data.bin if the original is missing or corrupt. If your original .nv_data.bak still had the original code in it this could be what happened.

Nope, i wish it was that easy for me This works only if you backup up your rom with Clockworks for example.
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes