[Captivate General] itsjustaphone:
Translated by google chrome

Here is how to unlock a phone that has missed its flash Froyo JPC (request for unlock code and displays the correct imei)

New semi automated method available here: http://forum.frandroid.com/forum/viewtopic.php?id=27019

Beware if the imei is not good before you start, it will not be at the end.

This method can also be used to modify the Product Code for those interested

All that was done on'm Android 2.1 since Froyo modifies the files to his liking (I advise to do New JM1, it works very well).

Thank you for everything you read, do not fly the tutorial is very important !!!!! I could not be responsible for those who are mishandling

Before anything else, save the file efs /, we will play with:

http://forum.frandroid.com/forum/viewtopic.php?id=25668

Need to be root, busybox, android sdk available here:

http://developer.android.com/sdk/index.html

(In windows) we decompress the ZIP, it renames the file "android-sdk-windows" to "android" short and placed in c: \ (the name and location to the sdk is placed are important to commands typed by hand later)

Extracting a nv_data.bin:

Plug the phone in usb mode enabled USB debugging

Start => Run => cmd (a DOS window will open)

Tapper to space by:

cd ..

cd ..

cd android

cd tools

adb pull / efs / nv_data.bin

Close the DOS window

The file will appear in the nv_data.bin réperoire c: \ android \ tools.

Edit the file with a hex editor nv_data.bin (EditHexa available in my example here: ... http://www.logitheque.com/logiciels/win a_9903.htm):

188 021 offset (page 3137) to "XEF" (ca will recognize the phone as "naked") (thus change the product code)

Offset 18146E (page 3,083) to "00000000" (ac will put the network unlock code 00000000)

We backup ^ ^

Then we go back in adb ^ ^

Start => Run => cmd (a DOS window will open)

Tapper and point in space by:

cd ..

cd ..

cd android

cd tools

adb shell mkdir / sdcard / efs "

adb push nv_data.bin / sdcard / efs

adb shell

su

mv / efs / .nv_data.bak / efs / .nv_data.bakk

mv / efs/.nv_data.bak.md5 / efs/.nv_data.bakk.md5

rm / efs / nv_data.bin

rm / efs/nv_data.bin.md5

rm / efs/.nv2.bak

rm / efs/.nv2.bak.md5

cp busybox / sdcard / efs / nv_data.bin / efs / nv_data.bin

chmod 755 / efs / nv_data.bin

chown radio.radio / efs / nv_data.bin

If he ever put the radio user does not exist, try "chown 1001:1001 / efs / nv_data.bin" instead and yes for some it is still not the same ....( thank you Froyo JPC / JPH )

There may be errors on. Nv2.bak and md5 (they do not exist at all)

I renamed the. Bak. BAKK to set aside the time everything is finished, they will be erased later.

do: ctrl + c

unplug the phone, remove the battery without turning the phone 30 seconds.

restart (on or before this point we must put the sim)

The network will unlock code: 00000000, it will the code is good but not unlock it anyway. If its not working properly and restart the phone again.

once functional, * # 06 # displays the correct imei

After there are bugs that require reflashing, reflash in New JM1 via Odin with re-partition active (I did not test other firmwares)

Must rooter again (the busybox normally installs with the root) ... and yes again ^ ^

reboot (so the normally nv_data.bin.md5 must have recreated)

Creating the. Bak

plug the phone into USB debugging mode enabled

We return under adb ^ ^

Start => Run => cmd (a DOS window will open)

Tapper and point in space by:

cd ..

cd ..

cd android

cd tools

adb shell

su

rm / efs / .nv_data.bakk

rm / efs/.nv_data.bakk.md5

busybox cp / efs / nv_data.bin / efs / .nv_data.bak

busybox cp / efs/nv_data.bin.md5 / efs/.nv_data.bak.md5

chown radio.radio / efs / .nv_data.bak

chown radio.radio / efs/.nv_data.bak.md5

Ctrl + c

Unplug your phone

and it finally finished your phone is unlocked and working again all operators ... remember to save them now ^ ^

A big thank you to Rickou who brought me on a platter chown radio.radio Chaineau who was missing.

And has Reve40 with whom I studied nv_data.

And Hideki Jis26 who tested the method before it is online.

A remark Hideki:

hideki wrote:

Otherwise I just add details about my case.

So personally I stopped before the stage flashing in JM1 because I had no problem and my bak files were recreated itself at startup.

I tried the following reredémarrer my imei and no problems still, no application code. And like bin files are recreated at each boot from bak, I concluded that my bak was so good .

What greatly simplify the procedure .

This was not the case for me and therefore Jis26 peus be that after the Roma moved to the base, we could have some small variations, I can not say more.

Last edited by helroz (25-09-2010 1:50:37 p.m.)