yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] Pariah86:
Ok I figured out what happened. The instructions at the link worked great for rooting. What happened was after I type "su" the phone asks whether to grant permission to the user and you click yes obviously. I did not notice the request on the phones display so it would automatically reject the su command. Thanks for all your help. Oh and the superoneclick program did not work for me I got the signature error.. I had to enter all commands manually from the cmd prompt to make it work.

Edit: Ok I was mistaken it was not superoneclick that I tried to root with it was a different program. Superoneclick works as well.
[Captivate Android Development] arcangels03:
Captivate Cognition 2.3

1) Flashed Odin Stock 2.1 Rom (Master Clear, Format SD Card)

2) Flashed Odin Leaked Stock 2.2 ROM JI6

3) Superoneclick root,busybox,su

4) Followed adb su commands

5) Root Explorer nv_data.bin due to permission errors

6) Applied /system/bin "Busybox cp" instead of just "cp" command

7) Odin to Cognition 2.3 over stock 2.2 kernel.

8) Stable, Fast, Unlocked, done until Gingerbread gets ported over to galaxy s.

Thank you very much life saver, posted steps i made to help anyone a little lost.
[Captivate Android Development] jrior001:
worked great on cog2.3b3. Took a second reboot for the md5 files to rebuild themselves but other that that ....perfection!:D
[Captivate Android Development] spores:
I just did this, works on the Rogers SGH-I896 stock rom with root.
[Captivate Android Development] tonie972:
...........
[Captivate Android Development] space_eyes:
Did you have to do anything different?
[Captivate Android Development] AtariBorn:
Sweet! Finally got this sucker unlocked!
[Captivate Android Development] Pariah86:
It worked! Thank you so much.. I was just a neewb poking around.. Took me all evening, because of stupid mistakes.. But it worked and I love it!
[Captivate Android Development] Keithyv`:
:) :) :) :)

Now if somebody could automate it... I am really not familar ADB
[Captivate Android Development] spores:
Nope. Just follow the instructions. I think this is the only way rogers stock rom can be unlocked.
[Captivate Android Development] Dave the Knave:
It's not really that hard once you get into it. The commands have already been prescripted for you. As long as you follow them, nothing will go wrong, and even then if you tremendously screw things up, just reflash!
[Captivate Android Development] seekerm2:
I thought I was permanently locked when a upgrade got rid of the codes in nv_data.bin and this thread was a lifesaver! works and IMEI number matches. THANK YOU
[Captivate Android Development] Dave the Knave:
You're welcome. Glad to see it working for so many people

Sent from my Captivate
[Captivate Android Development] heojihoon:
My captivate att sim card doesnt work now!

I just unlocked my captivate and now the network lock is off but my sim card for ATT doesnt work! What did i do wrong?

Cheers
[Captivate Android Development] Dave the Knave:
Try rebooting the phone without the SIM in it, and then rebooting with the SIM in it. If that doesn't work, do a backup real fast with Titanium Backup, do a master reset, and if it works again, restore your backup.

Also, I've seen a few threads pop up now with people saying their IMEI has changed, I cannot stress how important it is that you

BACKUP YOUR EFS FOLDER BEFORE YOU START MODIFYING ANYTHING.

That way if your IMEI changes you can at least return your phone back to it's original SIM locked condition with the proper IMEI.
[Captivate Android Development] space_eyes:
Yeah I'm starting to think so too, it almost seems like they just completely removed any unlock codes and anything that has to do with it from the phone. Found all sorts of logs and stuff everywhere on the damn thing. Did you know they even record where you touch on your screen...

I've gotten the "unlock" codes from cellunlocker.net, and still doesn't work. Hopefully I get a refund... But I'll eat the 8 bucks if I have to...
[Captivate Android Development] modest_mandroid:
It "worked" for me (not really). I followed the steps and the phone reports that it is unlocked, but my friend's tmobile sim doesn't work in my phone. I tried rebooting multiple times with and without the sim card, but it still only works with my ATT sim. Has anyone tested this with a sim from a different carrier and had success?
[Captivate Android Development] Keithyv`:
EDIT: Issue is fixed i896 can be unlocked. Please see my post on the next page.

KV
[Captivate Android Development] zoro23:
Galaxy S Fascinate

Hey my phone is Galaxy S Fascinate (from telus) code SGH-T959D and i was looking everywhere to unlock it but could not able to find any solutions.

Does this method also apply to my phone or do i need to wait for alternative option.

Thanks
[Captivate Android Development] Dave the Knave:
There was somebody who successfully got their i896 unlocked in this thread. Try PMing him and asking what he did.

Sent from my Captivate
[Captivate Android Development] Dave the Knave:
I'm not sure if this would work for you. You're more then welcome to try it though and report back to us

Sent from my Captivate
[Captivate Android Development] sshvetsov:
Ditto for me. Unlocked my rooted stock Rogers SGH-I896. IMEI stayed the same.

It appears so...

Did you root your phone first? What root method did you use? Did you install Samsung drivers? Did you set up Android SDK? Did you get any error messages at all? You don't provide any info, so it's hard to diagnose your problem.
[Captivate Android Development] X2Board:
Worked perfectly (good thing, since I only read the first page)

Donation made.

Thanks,

M.
[Captivate Android Development] cocteau2x:
I am at step 9 and I do not have a nv_data.bin.md5 file.

But, when I type *#7465625# in to my phone I get a screen

Network Lock, Network Subset Lock, SP Lock, and CP Lock are all OFF ... ????

Am I good? ..

Captivate i897
[Captivate Android Development] sshvetsov:
Did you already reboot and there's still no .md5 file? If you executed steps correctly the reboot should have regenerated the md5 file (the md5 checksum) based on the newly patched nv_data.bin file you pushed. It is possible it didn't if nv_data.bin is corrupt or permissions/ownership of the file are incorrect. What does ls -l -a /efs show?
[Captivate Android Development] cocteau2x:
Yep rebooted ...

all steps went very well ..

ls -l -a /efs Shows this .. :p

C:\android-sdk-windows\tools>adb shell

$ su

su

# ls -l -a /efs

ls -l -a /efs

drwxrwxrwx root root 2010-01-01 00:00 .android

-rwxr-xr-x radio radio 2097152 2010-11-17 19:00 nv_data.bin

-rw-rw-rw- radio radio 15 2010-11-17 18:47 .imei

drwxrwxrwx radio radio 2010-07-17 08:46 imei

-rw------- radio radio 2 2010-11-11 13:03 .nwksimpin
[Captivate Android Development] Keithyv`:
Yeah phone rooted otherwise I wouldn't have been able to perform the superuser commands

I installed the SDK no probs... worked in the ADB shell no probs.... no errors while performing the commands.

The only thought that I had was that i pushed the original nv_data.bin instead of modified nv_data.bin, but I don't think that this is the case. I made sure to move the original out of the ADB directory and put the modified in instead.

Wierd huh? I guess I will try it again and see if it works this time.

EDIT: I am an idiot I must have pushed the original nv_data.bin file please disregard my previous posts everything works as it should i896 can be unlocked and my IMEI number has stayed the same.
[Captivate Android Development] Keithyv`:
What ROM are you using?
[Captivate Android Development] cocteau2x:
The one that came with the [STOCK ROM] Odin3 One-Click Downloader

My Phone says .... (don't know if this is what you are asking) :o

Model number SAMSUNG-SGH-I897

Firmware Version 2.1 -update1

Baseband version I897UCJF6

Kernel version 2.6.29

jetaek.lee@sep-11 #2
[Captivate Android Development] Dave the Knave:
If you're not getting that md5 file, then something just isn't right... I suggest starting from scratch using the original nv_data.bin you pulled off the phone in the first place.
[Captivate Android Development] space_eyes:
F*** Yeah! Was able to unlock properly this time without bricking my phone, nearly anyways. Thanks greatly appreciated will be looking to donate soon.

Key Word: Unlock Rogers I896 Samsung Captivate Galaxy S Canada, unlock code wont work, doesn't work

edit: tested with telus sim card, everything A OK. However seems that if I try to enter the unlock manually it stays "requesting unlock" unlock code incorrect. So with that being said, this method does still unlock the phone, but I think the "new" method to disable unlocking is still in effect I think even if you "freeze" the phone your sol. Within the nv_log file it does show the removal of the NCK being applied in in the nv bin file itself is replace back with the "FFFFFFFF" and other changes that are applied.
[Captivate Android Development] dhemke17:
Tested with a T-mobile SIM that I got my hands on. Worked great. Wondering if I use ODIN to flash back to stock if the phone will be re-locked.
[Captivate Android Development] Dave the Knave:
I've heard mixed results on that. Worst case scenario is that you just have to do this all over again if it relocks. I'm not sure if flashing rewrites the /efs directory.
[Captivate Android Development] p4bus800:
thanks, I'll try with my Captivate :D
[Captivate Android Development] rush_exmachina:
newbie here with a quick question. after I input "adb pull /efs/nv_data.bin", Step 3 says "Select the file on the main Samsung Galaxy S Unlocker & Repair page", I've been looking all over for the nv_data.bin file, where is it?
[Captivate Android Development] Dave the Knave:
Its in the directory you are running adb from

Sent from my Captivate
[Captivate Android Development] rush_exmachina:
thanks, I'll try again.
[Captivate Android Development] rush_exmachina:
finally got it and unlocked! thanks so much. imma enjoy this for a bit then probably update to leaked froyo 2.2! unless its available already, I'm deployed right now so I dont know whats going on with Kies, ATT, or Samsung.
[Captivate Android Development] Dave the Knave:
Glad to hear it. Don't count on getting the official 2.2 until much later this year, if at all.

Sent from my Captivate
[Captivate Android Development] flareblitz007:
Has anyone gotten this unlock to work on their Rogers Captivate (SGH-I896)?
[Captivate Android Development] Dave the Knave:
Yes there were a couple guys in previous posts.
[Captivate Android Development] flareblitz007:
Thanks, sorry I didnt check thoroughly.

Question: For the Unlock and Freeze codes, are these just arbritrary #s? Where do I get these from? What should I be entering?
[Captivate Android Development] Dave the Knave:
Any 8 digit code you want them to be.
[Captivate Android Development] flareblitz007:
I was able to successfully perform the unlock by following the posted instructions to a T. Thanks for all the help and quick responses!
[Captivate Android Development] nv83:
Success following the steps on Cognition 2.4

The only problems I ran into were sometimes getting permission denied when copying files...chmod 777 on said files fixed that and am now showing unlocked.
[Captivate Android Development] space_eyes:
If for some reason you needed to re-lock the phone. If you try returning an unlocked phone I think you get the run around.

But keep in mind to keep your backed up files.
[Captivate Android Development] jaycaijay:
I'm really new to this, so I want to ask some questions before I start the process.

My version is JI6.

Which root method do you recommand? One Click Root/UnRoot ?

Is rooting the only thing I need to do before start the process?

Thank you so much.
[Captivate Android Development] Dave the Knave:
Since you're new, I recommend searching for SuperOneClick by CLShortFuse. Rooting is all that is needed before trying this.

Sent from my Captivate
[Captivate Android Development] jaycaijay:
On step 2, when I type

su

chmod 777 /efs/nv_data.bin

exit

exit

it says permission denied.

I wasn't able to root the phone with superOneClick, so I rooted it with One Click Root/UnRoot by TGA_Gunnman. Is it going to make any difference?

Thanks for the help.
[Captivate Android Development] Dave the Knave:
If you have 2.2 the only one click method is SuperOneClick. The one click from Gunman doesn't work on 2.2. Also if you're actually rooted and you type su in the shell and it says permission denied, make sure you check your phone after hitting enter as you may have a popup on the phone asking your permission to give super user access.

Sent from my Captivate
[Captivate Android Development] jaycaijay:
I have 2.1.

I don't see any thing happen on the phone when I hit enter.

It says permission denied even I just enter su.

Thank you for the help.

edit...

Thanks for all your works and helps.

Donation made.. Confirmation number: 7AH98817TK455322E.
[Captivate Android Development] Dave the Knave:
Much appreciated and I'm glad it worked for you.

Sent from my Captivate
[Captivate Android Development] jaycaijay:
Too bad, it hasn't worked for me yet.

I'm still on step two, don't know what to do for the permission denied.

Do you think i should unroot it and try other root method ?
[Captivate Android Development] Dave the Knave:
I think you need to try and reroot. If you get permission denied after typing su, that's the problem. Use Gunnmans one click and try it again

Sent from my Captivate
[Captivate Android Development] jaycaijay:
I tried for several times, didn't work. I was able to root it with Gunmans one click root. It generate a Superuser Permission app after the root, however, it says the application permissions(process com.noshufou.android.su) has stopped unexpectedly. The only choice is to force close the application.

Is that has something to do with the problem of unlocking?

thanks.
[Captivate Android Development] Dave the Knave:
I've never seen that error before.. when I get home I can look up more info for you

Sent from my Captivate
[Captivate Android Development] Dave the Knave:
Just thought of something else. Unroot your phone using Gunnmans method and then search the market for z4root and try that method. Lemme know how it goes from there.

Sent from my Captivate
[Captivate Android Development] PoIsonLord:
I have the same problem and didn`t work with z4root for temporary root, i`ll tri now the other option and come back with an edit. I don`t know why i can`t grand su in adb shell...

Permanent rood didn`t work as well. I can`t gain root acces in adb shell
[Captivate Android Development] olwe:
Hi there..

This guide worked for me and unlocked the phone. However, when I mounted the phone and looked into the sd folder, the efs_good folder is empty. Is there a way I can back that up again?
[Captivate Android Development] Dave the Knave:
Its not empty. If you view it with Root Explorer the files are there. Any other file manager will show an empty folder.

Sent from my Captivate
[Captivate Android Development] PoIsonLord:
I tryed all the root methods i found upp, onclick lag fix, voodoo, gunman, z4root same thing can`t grant root access in adb shell what should i do ?
[Captivate Android Development] jaycaijay:
I was able to pass step two.

But there's something going on on step 9.

su

ls -l -a /efs

If there is an nv_data.bin.md5 file in the directory, all is well. You should continue with these commands:

i typed the ls -l -a/efs command, and I see a list of files which includes nv_data.bin.md5 and .nv_data.bak

then I type this command:

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

and it says cp: not found...

any idea??
[Captivate Android Development] PoIsonLord:
how did you manage to pass step two ?
[Captivate Android Development] jaycaijay:
try to install the Superuser after you root with z4root

the superuser will ask for your permission ON THE PHONE when you type su on the adb shell, just click remember and allow..
[Captivate Android Development] Dave the Knave:
Type busybox before you type cp. So your command should look like this:
[Captivate Android Development] jaycaijay:
thanks for the respond

for Step 10: Last step! Create a directory on your /sdcard called "efs_good" and copy the /efs files into it. This can be done via ADB shell ("adb shell" at the DOS command prompt) or in a terminal with:

su

mkdir /sdcard/efs_good

cp -d -r /efs/efs_good efs

reboot recovery

not able to do cp -d -r /efs/efs_good efs

even i add busybox ... it says cp: can't stat '/efs/efs_good' : no such file or direcotry
[Captivate Android Development] Dave the Knave:
Jay, I'm gonna refer you to my op which has the corrected steps for our phone in it

Sent from my Captivate
[Captivate Android Development] jaycaijay:
nvm... I used this command instead.... "cp -d -r /efs /sdcard/efs_good"

and now Im unlocked...

thank you so so so much miztaken1312....
[Captivate Android Development] Dave the Knave:
No problem. Glad it finally worked out for ya! Lol

Sent from my Captivate
[Captivate Android Development] PoIsonLord:
Can you explain what shoud i do on step 3,4 and 5 cause i don`t really get it

understood no need :)
[Captivate Android Development] jaycaijay:
Will the phone lock it back when I upgrade it to official 2.2.

Also did a donation for NWolf to thank him.

Confirmation number:	0ED808961U450914J
[Captivate Android Development] Dave the Knave:
For step 3: You will find the NV_data.bin file in the directory you are running adb from. Most likely it will be C:/android-sdk/tools

For step 4: enter any 8 digit number you want for your unlock and unfreeze codes. Click submit or enter or whatever it says

For step 5: read the following page you are presented with. It will tell you to download the file from the link provided at the bottom of the page. Download that and proceed with step 6

Sent from my Captivate
[Captivate Android Development] PoIsonLord:
Anothe problem in step 10. I can`t mkdir /mnt/sdcard/efs_good no such files or directory, can`t mkdir /sdcard/efs_good read-only file sistem

YEY i had to turn of storage, i did it yay many thanks
[Captivate Android Development] X2Board:
I just noticed my IMEI number is different since the unlock, how do I get it back to the original number? I do have a backup of the original /efs folder, where I can see a subfolder named /imei, with two files in it, bt.txt and mps_code.dat. Do I just copy the two files to the current /efs folder?
[Captivate Android Development] edgevision:
So, problem. (original post here http://xdaforums.com/showthread.php?t=855939)

I have a Rogers i896. I followed these steps and unlocked my phone, great (all from stock Rogers 2.1 ROM).

Inserted a Telus SIM. Everything worked great - except for the fact that my reception sucked. Like really bad. Often dropping out or 1 bar. I know this isn't the unlockers fault - probably need to enable 850 band or something.

So I flashed a 2.2 ROM via CWM.

Since the flash of the 2.2 ROM my phone does not read the SIM card and says my IMEI is null.

I have a backup of my original nv_data.bin (which is like 10MB I think? vs the 2MB one I downloaded from Wolf? can anyone on Rogers confirm this?).

What do I do?
[Captivate Android Development] johan8:
My phone come with unlocked.

How to lock again ?

Because I don't know mine Control Key, I can lock it again.
[Captivate Android Development] Dave the Knave:
Sent from my Captivate
[Captivate Android Development] el_venga:
i have kind of a problem. captivate bricked/boot killed while downgrading so i did jtag on it and repaired it then flashed JF6, phone got stuck on restart loop so i flashed JI6 and that was fixed. later on i realized phone was not reading sim card, baseband info is now Unknown, imei is null/null and no lock info(*#7465625#). i have messed with Vibrant JI6 before just to unlock it so i figured nv_data must be corrupted but i dont have original nv_data. any ideas on what to do? i have original nv_data from my last Vibrant locked and unlocked with wrong imei.
[Captivate Android Development] X2Board:
ARRRGGGHHHH!!! Copied everything back, but lost network unlock after that. I'll run through and restore just the imei folder next time.
[Captivate Android Development] Capeachy:
Rogers Captivate V2.1

Followed these unlocked instructions and it worked for my Rogers Captivate on stock v2.1.

Before following this guide I used:

- z4root to root the phone

- busybox installer to install busybox (required for the cp command to work)

Both of those can be found on the Android Market.

There are also a couple of exceptions to this guide that I found on my phone:

1. I could not complete step 7, 'adb push nv_data.bin /efs' due to a "permission denied" error. I had to perform a 'chmod 777 /efs' and 'chown root.root /efs' to allow write permissions to the directory. After the phone restarts in step 9, the OS automatically reverted the /efs folder to 771 and owner as "radio radio".

To check that, just run 'ls -l -a' in the root directory when you're in adb shell.

2. The sdcard directory on version 2.1 is /sdcard and not /mnt/sdcard. This affects step 10 to backup the working /efs configuration.

Hope that helps!

Edit: Rogers v2.1 needs this method since the unlock code isn't stored on the phone unlike the AT&T counterpart. SGS unlock will never work on a Rogers phone.
[Captivate Android Development] Dave the Knave:
Just reflash. You never need to touch the IMEI folder.

Sent from my Captivate
[Captivate Android Development] X2Board:
I'm on Froyo, so I don't want to go through all that hassle. I found that I can simply overwrite the /efs folder from my backups, to swap between locked with valid IMEI and unlocked with bogus IMEI. I don't need unlocked mode at home, so international travel is the only time I will use unlock mode. I'm in the Dominican Republic this week and it's working great. :D
[Captivate Android Development] Dave the Knave:
What hassle? Backup with TiBu, use the one click Odin for JI6, root, restore backups, and go at it again. Most of the process is automated anyway now

Sent from my Captivate
[Captivate Android Development] X2Board:
The hassle of flashing to stock, then back to Froyo. I'm happy with the phone as it is, all it takes is a quick overwrite of the /efs folder to swap between locked/unlocked.

Thanks!!
[Captivate Android Development] esprito:
Hi I get to this stage

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

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

and get the following error: cp: not found

Any ideas?
[Captivate Android Development] esprito:
This post saved me.

Just unlocked 2x Captivates!! I ****ing LOVE you guys :D :cool:
[Captivate Android Development] africanizedkiller:
Worked great, thanks

Just wanted to report that it worked fantastically on Cog 2.3b7, thanx. IMEI is the same.

Wouldn't generate md5 in JF6, and cp wasn't included (had to install busybox). Why mv/rm in system/bin but no cp stock? Licensing/gnu issue or something?

Started over and flashed to Cog 2.3b7. Everything worked out. Still, though, when I swap to a Telcel 3g (Mexican) sim, it freezes up on the unlock screen (black background), the same one seen during the intermediate step when you check md5 generation. Anyway, I just reboot into recovery, wipe cache, and reboot to get back to AT&T.

Other notes:

/efs was 771, so I had to chmod 777 to push, but not on the way back (reverted to 771 automatically)

Also had the same noob issue with missing the "su allow" prompt on the device. Wish it played a sound or something.

Also: thought I was screwed too when I got the black/unlock screen after 1st reboot.

Thanks again,

AK
[Captivate Android Development] test2try:
working

Hi , I just want to thanks you for the steps , works perfectly on my new telus fascinate with 2.1. There is no mnt folder and the copy command do not work but that was the only differences.

thanks again
[Captivate Android Development] Dave the Knave:
That's cause you're on 2.1. This tutorial is for 2.2 Captivates. But glad it worked for you as well :)
[Captivate Android Development] freakma:
Works 100%

At first I was doubtful but it works I am very pleased congrats on the method I have to field test this puppy......Thanks In a Billion Wait for Donations Soon !!!:D