yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] unnamedsoul91:
step 6 when i enter

it say that file exists

it say permission denied

OMG, "Sorry! the process com.android.phone has stopped unexpected. please try again"

ah, this is problem with the SIM, I change it and my phone work perfectly :D. thanks all.

now, I'm in 2.1, I want to up to 2.2, do I need do step by step again to unlock?
[Captivate Android Development] berean:
This worked like a charm for me. The batch files are great. I downloaded them from the communityhosting link on page 1, and followed the instructions. The second batch file ran into several problems, but each time at the end it asked me if there were any problems. When pressing y, then they ran more processes, and when it was all done my phone booted into recovery and I was told to delete the cache. When I rebooted it was unlocked.

Many thanks to the developers of this and for reposting it on XDA. Thank you!

I am running Phoenix 2.0 and have run many other roms since stock. I am glad this all worked.
[Captivate Android Development] airmin98:
I completed all the steps from OP, but when I booted up with a different SIM, it shows "Phone locked", then asked me to enter unlock code. I failed twice already, both tried were using 00000000 as unlock code.

And I think I didn't push the "new" nv_data.bin back to the phone, and I just pushed the original nv_data.bin which pulled from the phone. If that's the case, what should I do? simply delete the efs/nv_data.bin, then push the "new" nv_data.bin??

what command do i use with ADB, sorry, I am not good at the linux/unix command. thanks

edit: Also, I don't see an option to wipe the cache, I only see an option to delete the cache, are they the same?

Ben
[Captivate Android Development] NWolf:
As long as you maintain a backup of your original nv_data.bin file, you can push the new one to the phone, yes.

Wipe and delete are synonymous in this instance.
[Captivate Android Development] airmin98:
Btw, is there any size different btw the original nv_data.bin and the new nv_data.bin? the original one is about 2MB.

Also, how do i make sure that i am pushing the right (new) nv_data.bin to the /efs? Do I first go to the directory that store the new nv_data.bin, then run the adb push nv_data.bin /efs?

Thanks,
[Captivate Android Development] NWolf:
Some people seem to have a 10MB nv_data.bin file for some reason. The new one is usually 2MB.

Make sure you have only the new nv_data.bin file in the directory you're pushing from is the only way to be sure you're pushing the right nv_data.bin.

Some people aren't able to push directly into the /efs directory, so you might need to put it somewhere else that you have write access to on the phone then copy it into the /efs directory manually.
[Captivate Android Development] cantooz:
Hey guys, I have read through the entire thread but I am not nearly as knowledgeable as all of you on this. Two questions before I even begin to try it:

- It looks like some people had some success with unlocking the Rogers Captivate with 2.1 using the method described in this thread (or maybe with slight modifications). I know that this method was designed for 2.2, but just to be safe I am going to ask anyway, is there any reason to expect that this would not work on my Rogers Captivate that I recently upgraded to 2.2?

- I understand that the phone needs to be rooted before I can do this. I see that there have been a few different options for rooting mentioned. What would you recommend for a novice as the easiest effective rooting method?

Thank you very much!
[Captivate Android Development] akuru:
Saved the day!

After hours spent with trying one-click tools, hex editing, flashing custom and stock ROMs with no success, this method literally saved the day for the Captivate I've bought from eBay! Thanks to the devs of this alternative method, I'm now able to use my device with our local service providers :)

I can happily confirm that this method works flawlessly with Darky's v8.1, which is based on Froyo v2.2.1.
[Captivate Android Development] G-Man.:
If you do a search on the market for ' Helroz ' it will bring up his unlock app that does all this for you - all you need is root and this app. Follow it step by step and it works like a charm... eliminates alot of confusion. I've unlocked one captivate manually via instructions on this thread, and my new captivate with Helroz's app - the app from Helroz is most definately the easiest way.
[Captivate Android Development] ippon:
it looks like the Helroz method worked on my Rogers GS Cap.

i only had an OLD at&t sim to test it, but it's been inactive, and probably deactivated by at&t for years, so i can't confirm 100%, but the 'Personalizatiob Status' shows all the locks to be off, via *#7465625#.
[Captivate Android Development] delugeofspam:
I just tried this method repeatedly and for some reason I can't unlock my phone.

Using *7465625*638*# and locking to a different network claims to be "successful" but then booting with my ATT SIM doesn't seem to bother my phone at all. If I enter #7465625*638*# a dialog opens asking me for the unlock code but won't accept the one that this app gave me.

Downloading the Helroz tool now.

LIKE A CHARM!
[Captivate Android Development] movielover76:
Thank you

the helroz app works great, thanks alot

it unlocked my AT&T cappy, running Perception 10.4 with UGJL2 modem

perfectly.
[Captivate Android Development] movielover76:
Actually strange side effect that forced me relock my phone with a regular attend SIM the one I always use internet and calls worked perfectly fine, but gps would not lock in any app when outside , tryied deleting gps data, rebooting restoring the eps. Data and relocking was the only thing that fixed it and I'm using the Google server in my settings

Anyone else experience this?
[Captivate Android Development] Dave the Knave:
I have never heard of that before. This should have nothing to do with GPS as nv_data.bin is a file and not a modem. The only adverse effect I've seen from this myself is a slight loss of cell reception in some areas.
[Captivate Android Development] shust82:
k, got my nv_data.bin file on my pc, but everytime i try to get the new file generated, the tool says "There was an error uploading the file."

This is using http://www.communityhosting.net/sgsunlock/

anybody else get this?
[Captivate Android Development] goob1284:
How do you get around the ffffffffff thing? I downloaded helroz app and it diesnt work. Im running phoenix the js5 version
[Captivate Android Development] phantom92:
i cant take it anymore!!!!... ive done this procedure 2 times already.. non of the times i get any errors on ADB.. i pull the nv_data.bin upload and download the new one.. then push again and do some adb shell commands get su

and finally reboot tried *#7465625#

and still says (network lock) [ON].. but everything else is off.. i have firefly ROM 2.2

what am i doing wrong.. ive even tried the apk from the market the unlock one.. and it says sorry no codes found.. help
[Captivate Android Development] jayjr1105:
I flashed my cap back to stock using odin and master cleared... rooted, installed busybox (make sure you actually install it), install galaxy unlock, run through the 3 step process in the galaxy unlock app, power down phone after step 3. insert new sim, and when the phone powers up be PATIENT and wait. My phone took a good 3 minutes to grab the Tmobile signal. Now if someone could answer this question for me... If I flash a custom rom now, will I lose the unlocked status of the phone? because I really don't want to leave my phone at stock even though my wife is using it.

*edit* got my answer
[Captivate Android Development] darkamikaze:
anyone tried this on a cm7 build :P
[Captivate Android Development] tahrang:
Hi

this method changed my IMEI, so I locked the phone again. With other unlock method, I get FFFFFF at code. Any help here please?

thanks
[Captivate Android Development] Probaholic1:
Well after every other method didn't work this finally did. I think the problem that happens is when you update your Cappy to Froyo for most part it messes with the nv_data.bin file therefore not allowing any of the methods to really be effective. So rebuilding this folder looks to have resolved that? but I could be wrong.
[Captivate Android Development] klaxhu:
LG Thrive

Hi Guys,

I have a AT&T LG Thrive (P506) with Froyo 2.2

I have managed to root it succesfully, have superuser and Busybox on it.

I can run the commands and don't get any access denied messages, BUT if I go manually or even if I use Root Explorer I cannot find the EFS folder/files.

So basically when I run : adb pull /efs/nv_data.bin - I get : "remote object </efs/nv_data.bin> does not exist"

What can I do next?

Andy
[Captivate Android Development] yadava:
Discovered a way to do the entire procedure in a few clicks!

Since I already upgraded my kernel to 2.2, I was not able to get the code directly from the nv_data.bin since 2.2 wipes it off. So I decided to use this procedure, but just before that, I checked the marked to see if I can find an app that does this procedure automatically. And wallah! got it working on my samsung captivate 2.2 froyo. The app is called "Galaxy_S Unlock", by Helroz.

I am not 100% sure if the app follows the EXACT same procedure, but they looked VERY similar.

So, to unlock,

1. root your phone with super one click, the app needs su and busybox

2. Run the app, Step1, Step2 , Step3, restart and done!
[Captivate Android Development] mav814:
I type in this command and get "permission denied". I am rooted for sure and have made it this far. I think something is wrong with my busybox because I had to work around the last command that used "busybox cp". Please help.

Rooted 2.2 using kernal swapping to JI6.
[Captivate Android Development] Dave the Knave:
Why on earth would you run JI6? It's a pre-release Froyo beta that was buggy as hell. We have official Froyo (KB1) and even a Captivate Gingerbread release.
[Captivate Android Development] mav814:
Apologies, I actually am running KB1 rooted. Any help?
[Captivate Android Development] Dave the Knave:
Give this a try. https://market.android.com/details?id=com.boiteoutilssgshelroz&feature=search_result

Helroz is the one who came up with the method that I posted about in my OP.
[Captivate Android Development] mav814:
Thanks. I tried this app and it kept telling me I was having busybox problems.

I explain my situation here: http://xdaforums.com/showthread.php?t=1136269

I would appreciate your input.
[Captivate Android Development] pwnerman:
Hey I was just looking on this thread for ****s and giggles so i said what the hell and typed in the number code and my Personalizatiob Status looks the exact same as the one in the OP and I didnt even do anything to my phone
[Captivate Android Development] Dave the Knave:
Is your phone rooted? Have you tried downloading the busybox installer from the market? (Just search busybox)

Interesting... Are you the original owner of your phone?
[Captivate Android Development] pwnerman:
Interesting... Are you the original owner of your phone?[/QUOTE]

o yea the other guy was on t-mobile he must have did it to the phone before i bought it i guess after you do this its permeant cuz ive gone back to stock and flashed atleast 50 roms lol

also im on gingerbread so i guess it works if you upgrade if anyone is wondering lol
[Captivate Android Development] Dave the Knave:
Once unlocked, the phone stays unlocked regardless of your rom.

Sent from my Captivate
[Captivate Android Development] pwnerman:
That's a plus if I ever wanna sell it lol

Sent from Captivate
[Captivate Android Development] siemensfun1:
i unlock my captivate i897 but only incoming call-s is accepted.

also i can use data conection, internet and all feautures but a can not make a phone call.

when i am trying to call somewhere is shows me call ended and i can not call :(
[Captivate Android Development] Dave the Knave:
The unlock will not affect your ability to make or receive calls. Something else is wrong with your phone.
[Captivate Android Development] CatalystWon:
Thanks to everyone that helped put this together! :)

At the moment I do not have a Captivate but am trying to purchase a 5-month old pre-owned AT&T unit. The female owner doesn't know about unlocking/rooting so the phone will be AT&T stock. I don't yet know what android version, but I must unlock the phone so I can use it on Fido (Rogers).

What would be the correct sequence

: unlock first, or root first. It seems some posts say root first, other posts say unlock first. Or do I even need to root first just to get the unlock code (depending on the procedure). I am so confused. :confused:

One thing is clear: BACKUP everything before doing any changes using Titanium, and backup the EFS folder also.

I will do a RESET before anything so its all clean. I presume that won't affect the unlock-code files. I'll be using Windows XP Pro SP3. While I don't know Linux/Unix, as a former ibm mainframe software engineer I am able to follow clear instructions.

Also, while this thread pertains to 2.2, some posts say 2.2 wipes the unlock codes. More confusion for me.

Any help is warmly appreciated. Thank you in advance. :)
[Captivate Android Development] Dave the Knave:
You are quite right about backing up. That is very important, but to do that you have to root. That's the first step. If this phone is completely stock however, there's an easier method. There's a couple apps in the market that will similar unlock this phone. These will probably only work if the phone you buy is running the stock JF6 2.1 firmware. If its been updated to JH7 2.1 it KB1 2.2 the codes have most likely been wiped. Once.you get your phone, you'll have a better idea of what you'll need to do. post back when you get the phone. I'll help you from there

Sent from my Captivate
[Captivate Android Development] CatalystWon:
Thank you miztaken1312.:)

Are you able to give me re-assurance that we can unlock such an AT&T Captivate with stock 2.2 ,even if the codes are wiped? I'd hate to get stuck with a Captivate that can't be unlocked. That is my big worry at the moment.
[Captivate Android Development] Dave the Knave:
Its always possible to unlock. But if the codes have been wiped, its just becomes a more involved process.

Sent from my Captivate
[Captivate Android Development] CatalystWon:
Thank you miztaken1312.

Then I shouldn't worry if its got stock AT&T 2.2 on it. I'm assuming I would have to go by your original OP method. One thing I have just learned: it would be advantageous to get a unit wit 2.1 but that is hard to predict or control when getting a pre-owned unit.
[Captivate Android Development] Skv012a:
Guys, any idea if this same thing could be applied to infuse?
[Captivate Android Development] Dave the Knave:
Be my guest to try

Sent from my Captivate
[Captivate Android Development] FroztIkon:
I can verify that it works on captivate, non stock 2.2 rom. I mean non stock, cause it didn't come from AT&T or Samsung, but its supposed to be.
[Captivate Android Development] Dave the Knave:
cp -d -r /efs /mnt/sdcard/efs_good

Edit: If you look at the quote I have in the OP, it has the directions correctly. I changed what was wrong ahead of time half-expecting someone to make a mistake.

For everyone else, if you're following the directions on the website, and something doesn't work, please come back to my OP and pick up from where you left off in my quote.
[Captivate Android Development] sourkrawt:
Thanks for the clarification. That was my bad as I should have checked the instructions more closely, at first blush they looked to be identical.
[Captivate Android Development] Dave the Knave:
No problem. Was your unlock successful? Did your imei match?

Sent from my Captivate
[Captivate Android Development] sourkrawt:
Unlock was successful and imei #s matched.
[Captivate Android Development] twisted99:
I just wanted to say thanks. This worked great on cog 2.3.3.
[Captivate Android Development] bazald:
Same. I hoped someone would come through with something for those of us who failed to make good on the previous SGS Unlock. Thanks to all involved.
[Captivate Android Development] love_xda_devs:
Working Froyo

Worked as written w/vanilla killer23d's Doc's Froyo XWJPA V7.6.2 r1 Captivate Edition (new member can't post links)

I was worried though after first (cache clearing) reboot I got black screen with an unresponsive pattern unlock and "No Service" at top of phone. Adb reboot recovery into CWM which detected settings changes -> continue with backup and restore then rebooted from CWM and all was well.

Thank you!

Also, not that it matters but I think i did adb shell, su, cp /efs/nv_data.bin /mnt/sdcard/ and then adb pulled file from there instead of chmoding the original nv_data.bin to transfer (after permission denied on attempt to adb pull /efs/nv_data.bin)
[Captivate Android Development] Dave the Knave:
If you get permission denied when pulling a file, just change the permissions. "Chmod 777 /efs" I do think that's in the directions somewhere.

Sent from my Captivate
[Captivate Android Development] BumRush:
Can I just use root explorer and copy the nv_data.bin file to my computer? Or will that not work?
[Captivate Android Development] Dave the Knave:
Yes that will work too.

Sent from my Captivate
[Captivate Android Development] iqtidar:
guys im having problem with step 7.. how do i do this?
[Captivate Android Development] Dave the Knave:
Does it say permission denied? If so type:

adb shell

su

chmod 777 /efs

exit

exit

adb push nv_data.bin /efs

It should work after that.
[Captivate Android Development] iqtidar:
no it says push not found.
[Captivate Android Development] Dave the Knave:
You need to exit the shell...
[Captivate Android Development] iqtidar:
and then?...
[Captivate Android Development] Dave the Knave:
Then type adb push nv_data.bin
[Captivate Android Development] iqtidar:
thanks man....
[Captivate Android Development] Dave the Knave:
No problem
[Captivate Android Development] iqtidar:
hey man, i have another problem.

for this command in step 10,

cp -d -r /efs/efs_good efs

it says: no such files or directory
[Captivate Android Development] Dave the Knave:
Read the OP!
[Captivate Android Development] laoban:
IT'S WORKS !! GO FOR IT!

I can comfirm the SIM unlock method is WORKING on my Captivate. I flashed my original 2.1 ROM to the leaked stock JI6 - Froyo 2.2. My Captivated has been unlocked and tested to be working. IMEI number remains the same. Now you don't have to beg AT&T to give you the unlock code or pay somebody for unlock code!

TIPS:

For those who have problem of "file not found" when executing the CP command per instruction, I suggest you add "busybox" before CP command. Assume your phone has been rooted and busybox app installed.

su

mkdir /sdcard/efs_backup

busybox cp -d -r /efs /sdcard/efs_backup

rm /efs/nv*

rm /efs/.nv*

Also, if you have problem executing "adb push nv_data.bin /efs", you can work around like:

adb push d:\nv_data.bin /mnt/sdcard/nv_data.bin

adb shell

su

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

Good Luck.

:)
[Captivate Android Development] Fifthfreedom31:
Quick question, I unlocked my Vibrant running 2.1 with Helroz's method that was posted on the forums. I want to get 2.2 Froyo, will it relock my phone or will it remain unlocked? If anyone knows that'd be great. Thanks.
[Captivate Android Development] Dave the Knave:
It should remain unlocked. If not just do this all over. Time consuming, yes. Pain in the butt, yes. Worth it? You choose.

Sent from my Captivate
[Captivate Android Development] Fifthfreedom31:
Alright much appreciated. I unfortunately lost my damned USB cable so I have to get another one and I was wondering what would happen if I got 2.2 on the vibrant. I love using AT&T's network on this thing, works great.

You've saved me the trouble of guessing what may happen thanks alot.
[Captivate Android Development] PuffinNugz:
Pardon my ignorance, but what are the actual benefits to unlocking the phone? I know about using it for another carrier, but I also have seen something about the ability to use it overseas. How does that work? For two weeks over Christmas, my family and I are going on a trip to Rome, including a cruise stopping in Tunisia around to Greece. Would it be to my benefit to unlock the phone? And how would I use different networks?
[Captivate Android Development] NWolf:
The benefit to you is if you want to use your phone while in Rome. When I travel over sees, I purchase a pre-paid SIM card with a data plan, which is usually pretty cheap. The voice calls are usually pricey, anywhere from 14c - 75c a minute, depending on the country and the pre-paid SIM you get, plus a flag fall of 25c or more... so it sucks for voice calls, but the data plans are usually enough for the brief time you're there to be extremely useful. With the new Wifi calling option, it's doubly useful to take your phone with you as well. If you think you can get by with Wifi only, then there may be no need to get a SIM in the country you are going to.

I like to have data access wherever I am, though, so I keep a Worldsim with me and then a local sim for the country I am in.
[Captivate Android Development] DJNgoma:
As the phone is unlocked it means you can use any carrier SIM card. So it's as easy as buying a SIM card and some prepaid credit to use for calls. The benefit is cheaper calls in the country in , unless you haven't heard of roaming fees ;)?
[Captivate Android Development] PuffinNugz:
Thanks, guys. Kind of what I thought but wasn't sure. All I know is, it's time to unlock my phone.
[Captivate Android Development] Pariah86:
Neewb question..

Ok I ran ADB shell with no problem but when I try to type

su

chmod 777 /efs

exit

exit

I get a 'su not found' error. What went wrong?
[Captivate Android Development] Dave the Knave:
You aren't rooted. You need to be rooted to do this

Sent from my Captivate
[Captivate Android Development] Pariah86:
Thanks for the reply, yes after more looking around I realized I needed to be rooted. I believe I have successfully rooted now. I have access to su however I am getting chmod /efs/nv_data.bin: operation not permitted... after entering the command from adb shell.. Is there a possibility I am not rooted even though I have the su application? Any help is appreciated, thanks!
[Captivate Android Development] Dave the Knave:
You forgot the 777 after chmod.

adb shell

su

chmod 777 /efs/nv_data.bin
[Captivate Android Development] Pariah86:
sorry for the confusion.. this is what i did.

adb shell

su

chmod 777 /efs/nv_data.bin

exit

exit

This is what it showed.

Permission denied

$ Unalbe to chmod /efs/nv_data.bin: Operation not permitted

$
[Captivate Android Development] Dave the Knave:
The only thing I can think of is that you aren't rooted properly... Otherwise, that operation goes off without a hitch.
[Captivate Android Development] Pariah86:
I have tried the rooting methods posted on this forum and here androidforums.com/captivate-all-things-root/190589-rooting-captivate-froyo-update.html[/url]

Apparently without success.. The method show on the above web page appeared to work until now. All other update files I tried to use would give me a signature error of some kind after the phone rebooted into recovery mode. Is there something I need to do differently with Froyo? It seems nothing is working as it should.
[Captivate Android Development] robotlover:
I can verify this works perfectly on Cognition 2.4.

it's very important to realize that you must have the proper SU command.

if you used some sort of one-click instant root you may not.
[Captivate Android Development] Dave the Knave:
You can't root Froyo with any of the update.zip methods anymore. Go into Google and search for "XDA superoneclick". You're looking for a thread and app made by CLShortFuse. Read the directions and you should be rooted without any major problems. If not, pm me and I'll work out a solution for you

Sent from my Captivate