Related
Titanium Backup says "error could not acquire root", yet I "am" rooted???
Ok, so my v2.1 evo was rooted using Unrevoked 3.21, I install Titanium Backup this morning and when I launch it an error comes up that says "Sorry, I could not acquire root privileges. This application will not work. Please verify that your rom is rooted and includes busy box and try again."
Whats the deal wit this error? Unrevoked said it was succesful.
did you download busybox? when you open TB hit the problems? button. download busy box and try again.
you can also verify root by downloading terminal emulator and opening it. when its open type SU and hit enter. # means root. $ means no root.
Be weary. I used unrevoked3 for mac on a froyo Evo. I'm having some issues currently. Be careful before you proceed. You should download ROM manager as well. Once you download busybox perform your backup. A friend recommended Appbrain over Titanium Backup. Once your done with your back up, reboot into the bootloader and try to go into recovery to perform a nandroid backup. If you select recovery and it takes you to the htcevo 4g white screen and nothing happens, you're having the same issue as i am. I wouldn't recommend flashing any radios or roms yet. I'm working with some other members to try to figure this issue out. Apparently this is why other experts don't like unrevoked3.
There might be a missing pc36img or unrevoked forever might need to be install, but I don't want to lock my phone into root with unrevoked. From my understanding, if you use unrevoked forever, you wont be able to unroot.
jontorres said:
Ok, so my v2.1 evo was rooted using Unrevoked 3.21, I install Titanium Backup this morning and when I launch it an error comes up that says "Sorry, I could not acquire root privileges. This application will not work. Please verify that your rom is rooted and includes busy box and try again."
Whats the deal wit this error? Unrevoked said it was succesful.
Click to expand...
Click to collapse
[highlight]Mod Edit: If you have nothing useful to say, say nothing at all. The question in the correct section this time.[/highlight]
jontorres said:
Ok, so my v2.1 evo was rooted using Unrevoked 3.21, I install Titanium Backup this morning and when I launch it an error comes up that says "Sorry, I could not acquire root privileges. This application will not work. Please verify that your rom is rooted and includes busy box and try again."
Whats the deal wit this error? Unrevoked said it was succesful.
Click to expand...
Click to collapse
What about any other app requesting root? Like setCPU or ShootMe? I'd install one of those to confirm root. If it works then you might you need to reinstall TB if not well then root was not properly achieved.
TruSlide said:
did you download busybox? when you open TB hit the problems? button. download busy box and try again.
you can also verify root by downloading terminal emulator and opening it. when its open type SU and hit enter. # means root. $ means no root.
Click to expand...
Click to collapse
Thanks for the suggestions, will try those out and report back what happened.
Sporkman said:
take the time to read the info it tales you have to fix said issue
Click to expand...
Click to collapse
MOD PM'd, apparently you are following my threads now to post the same "ignorant" response, your sanction from the mod will follow, enjoy.
Everyone else, thanks for actually offering helpful suggestions.
TruSlide said:
did you download busybox? when you open TB hit the problems? button. download busy box and try again.
you can also verify root by downloading terminal emulator and opening it. when its open type SU and hit enter. # means root. $ means no root.
Click to expand...
Click to collapse
Ok, so I did update BusyBox, and now Titanium Backup doesnt show the error, also installed Terminal Emulator when you launch it the 1st line of text says"
$ export PATH=/data/local/bin:$PATH
$
On the 2nd line where the $ i typed SU and hit enter and it goes to the next line and displays # is this what its suppose to do?
Thanks
Ok, here is some things for you to try.
1. Make sure you are using the latest version of TB.
2. Make sure you hit Problems? and download Busybox 1.60 (whether or not the ROM you have is using 1.60 or not, do it anyhow.)
I assume you did those two based on what I read. So here is what else to try.
Upgrade Superuser to the latest version, then update the binary. Make sure Titanium backup is not blocked by going to Superuser and there should be a green circle next to TB, if it is red that means it is blocked. If it still doesn't work, remove it from Superuser and then have it ask for permissions again.
If STILL not working, take out your battery for around 10 seconds, plug it back in and try again. Lastly, uninstall and reinstall TB then do these steps all over again.
That is a bunch of stuff to try, see what happens and hope this helps
jontorres said:
Ok, so I did update BusyBox, and now Titanium Backup doesnt show the error, also installed Terminal Emulator when you launch it the 1st line of text says"
$ export PATH=/data/local/bin:$PATH
$
On the 2nd line where the $ i typed SU and hit enter and it goes to the next line and displays # is this what its suppose to do?
Thanks
Click to expand...
Click to collapse
That's exactly what it's supposed to do. $ is the prompt you get when you are a regular user. You get # when you are root.
If you type 'id' (without the quotes) now, you should get:
uid=0(root) gid=0(root)
ricsim78 said:
Upgrade Superuser to the latest version, then update the binary. Make sure
Click to expand...
Click to collapse
I launched Superuser, the one with the little niña guy, and it showed TB and the emulator both with green on the right side, but no idea how to "update" superuser, seeing as all appears to be ok should I still update it? If so, hoe would I do that? If not then I guess now my next step s finding the best 2.2 ROM that still keeps HTC Sense, any recommendations?
timdsmith72 said:
That's exactly what it's supposed to do. $ is the prompt you get when you are a regular user. You get # when you are root.
If you type 'id' (without the quotes) now, you should get:
uid=0(root) gid=0(root)
Click to expand...
Click to collapse
the prompt b4 I typed anything was $, after typing SU and enter it went to #
jontorres said:
the prompt b4 I typed anything was $, after typing SU and enter it went to #
Click to expand...
Click to collapse
Yep. That's what is supposed to happen. You are root when you have the # prompt.
Problem
I just flashed CM 7.1 stable version, i cant launched TB couldt aquire root privileges i read this post and typed SU in the terminal emulator and it came up with a $ sign. So that means im not rooted?
Any cure to get my phone rooted again but i want to keep CM 7.1 what should i do?
aks1081 said:
I just flashed CM 7.1 stable version, i cant launched TB couldt aquire root privileges i read this post and typed SU in the terminal emulator and it came up with a $ sign. So that means im not rooted?
Any cure to get my phone rooted again but i want to keep CM 7.1 what should i do?
Click to expand...
Click to collapse
Flash the super user zip from http://androidsu.com/superuser/
Should fix you up, not sure how you lost it, but this souls fix it nevertheless.
If on Recovery, it says S-ON, is that a Problem?
triumphantpower said:
If on Recovery, it says S-ON, is that a Problem?
Click to expand...
Click to collapse
If it says S-ON, you don't have permaroot. Did you follow the guide in the wiki?
Sent from my T-Mobile G2 using XDA App
I watched a Video from BlackPrince310. I got far into it, until I had to use the Terminal. I'm not sure what Wiki are you talking about.. Link?
(Thank You for the speedy reply btw)
triumphantpower said:
I watched a Video from BlackPrince310. I got far into it, until I had to use the Terminal. I'm not sure what Wiki are you talking about.. Link?
(Thank You for the speedy reply btw)
Click to expand...
Click to collapse
YouTube *really* shouldn't be the go to for things like this, unless you like bricks. This guide is by the folks who actually engineered the hack: http://forum.xda-developers.com/wik...sion#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD
Sent from my T-Mobile G2 using XDA App
oh alright, Thank You OriginalGabriel.
But is rage an adb command or an app from the Market?
and where would the HTC G2 Drivers have to be installed?
triumphantpower said:
and where would the HTC G2 Drivers have to be installed?
Click to expand...
Click to collapse
If you've used adb (eg. you have the SDK installed on your computer), then you have the drivers already installed. Otherwise, unzip the file and when you plug your computer into your phone, point the hardware wizard to the folder that you unzipped
Rage is an included binary in gfree_temp-root.zip
Got it Thank You.
I got to where I have to use ADB, and while trying to $ adb push su /sdcard/su
It won't let allow me, it'll say access denied. (I've even put adb shell before that command)
I type in adb shell:
*daemon not running. starting it now on port 5037*
*daemon started successfully* and then any other command I type after that is Denied
triumphantpower said:
I type in adb shell:
*daemon not running. starting it now on port 5037*
*daemon started successfully* and then any other command I type after that is Denied
Click to expand...
Click to collapse
on your phone be sure you have menu>settings>applications>development>usb debugging checked (on)
I do. Using this Tutorial: http://forum.xda-developers.com/wik...sion#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD
I got all the way to the Permaroot Section. When I have to issue these commands:
# cd /data/local
# chmod 777 gfree
# ./gfree -f
#sync
my phone reset before I got to type sync.
And before I got the chance to type the next lines of text, I had to turn on my phone issued them and got an error message of file exists and something else. I Booted my phone and it still says SHIP S-ON
triumphantpower said:
I do. Using this Tutorial: http://forum.xda-developers.com/wik...sion#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD
I got all the way to the Permaroot Section. When I have to issue these commands:
# cd /data/local
# chmod 777 gfree
# ./gfree -f
#sync
my phone reset before I got to type sync.
And before I got the chance to type the next lines of text, I had to turn on my phone issued them and got an error message of file exists and something else. I Booted my phone and it still says SHIP S-ON
Click to expand...
Click to collapse
After you do the temp root, shut down adb (I am using a windows machine so I ctrl alt del and find it in task manager and shut it down that way) It should restart by itself when you do the perm root commands. ( you probably know this, but don't enter the # sign, it should be there by itself)
Thank You sooo much! I got the S-Off now finally, thank you very much!
Is there anything else I should do before I decided to Install a Custom ROM? Can I install a ROM from this Recovery? or Do I need to do a further step. According to the Tutorial I have Perm Root now but I've never used this Recovery before
triumphantpower said:
Thank You sooo much! I got the S-Off now finally, thank you very much!
Is there anything else I should do before I decided to Install a Custom ROM? Can I install a ROM from this Recovery? or Do I need to do a further step. According to the Tutorial I have Perm Root now but I've never used this Recovery before
Click to expand...
Click to collapse
Download ROM manager from the market, spend the few bucks for the upgrade and then install clockworkmod recovery through ROM Manager (if you haven't done this already). Then, do some more reading about doing a Nandroid backup and you're ready to go! Now, the fun begins....lol!
I don't mind buying ROM Manager Premium but can I do that with the Free Version? I downloaded the Free Version of ROM Manager v3.0.0.7 and when I selected Flash Clockwork Mod Recovery it gave me "an error occurred while attempting to run privileged commands!". Does the Paid Version go past that or am I missing something?
triumphantpower said:
I don't mind buying ROM Manager Premium but can I do that with the Free Version? I downloaded the Free Version of ROM Manager v3.0.0.7 and when I selected Flash Clockwork Mod Recovery it gave me "an error occurred while attempting to run privileged commands!". Does the Paid Version go past that or am I missing something?
Click to expand...
Click to collapse
do you have the superuser app now in your applications drawer?
edit: Also, disconnect the phone from the USB. That might give ROM manager a problem accessing your sd card if you're still connected.
yeah I have Superuser Permissions but it FC's when you try to open it
triumphantpower said:
yeah I have Superuser Permissions but it FC's when you try to open it
Click to expand...
Click to collapse
Try uninstalling ROM Manager and after that see if you still get a force close when you try to open Superuser.
Interesting Idea. I tried it, and still the same. Superuser FC's @[email protected]
triumphantpower said:
Interesting Idea. I tried it, and still the same. Superuser FC's @[email protected]
Click to expand...
Click to collapse
what happens when, in ROM Manager, you select "fix permissions"?
About 3 hours ago, I won a Desire Z (wheeey!) at the HTC London meetup. Naturally, I came straight here after the help I got in January rooting my Desire.
I used the Visionary method and obtained temp root status, and then attempted perm root, which seemed to work. All of the guides I have read include a bunch of steps after this, one of which included deleting Visionary, which I then did. I just turned the phone off, took the battery out for a bit and then turned it back on. I still have the Superuser icon and the Terminal Emulator indicates that I have root access... is that it then? It's that simple?
Please tell me if I've done anything wrong, as I don't want to flash Cyanogen and Clockwork Recovery if it's all going to go to hell on me. Any advice or confirmation on whether or not I've obtained perm root would be lovely.
Oh, my firmware version is 1.34.405... etc. Is this simply the last version which allows for such easy root?
Arconaught said:
About 3 hours ago, I won a Desire Z (wheeey!) at the HTC London meetup. Naturally, I came straight here after the help I got in January rooting my Desire.
I used the Visionary method and obtained temp root status, and then attempted perm root, which seemed to work. All of the guides I have read include a bunch of steps after this, one of which included deleting Visionary, which I then did. I just turned the phone off, took the battery out for a bit and then turned it back on. I still have the Superuser icon and the Terminal Emulator indicates that I have root access... is that it then? It's that simple?
Please tell me if I've done anything wrong, as I don't want to flash Cyanogen and Clockwork Recovery if it's all going to go to hell on me. Any advice or confirmation on whether or not I've obtained perm root would be lovely.
Oh, my firmware version is 1.34.405... etc. Is this simply the last version which allows for such easy root?
Click to expand...
Click to collapse
Having the SuperUser icon just means the app is installed, open up terminal and type 'su' to see if it throws up any errors
Sent from my HTC Vision using XDA App
I should have mentioned that I did that and got the # symbol, am I good to go?
Arconaught said:
I should have mentioned that I did that and got the # symbol, am I good to go?
Click to expand...
Click to collapse
In theory, yes; in practice, no. Visionary (with the G2/Desire Z, at least) is known to be a bit buggy. You shouldn't have any issues installing custom ROMs but, I would recommend using the wiki method to root.
Sent from my HTC Vision using XDA App
OriginalGabriel said:
In theory, yes; in practice, no. Visionary (with the G2/Desire Z, at least) is known to be a bit buggy. You shouldn't have any issues installing custom ROMs but, I would recommend using the wiki method to root.
Click to expand...
Click to collapse
My understanding, if he already used Visionary to root, and it worked than he should be good to go. Either it works, or it doesn't. The risk with Visionary is that it sometimes corrupts some partitions, which causes the phone to not boot. I haven't read any conclusive reports on Visionary causing long term issues (correct me if I'm wrong).
redpoint73 said:
My understanding, if he already used Visionary to root, and it worked than he should be good to go. Either it works, or it doesn't. The risk with Visionary is that it sometimes corrupts some partitions, which causes the phone to not boot. I haven't read any conclusive reports on Visionary causing long term issues (correct me if I'm wrong).
Click to expand...
Click to collapse
This is my understanding as well, though I'd probably still use GFREE to get S-OFF if I were OP.
That's my next question, I'm using this guide ( http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2 ) to try and get S-Off to flash Cyanogen and I'm wondering what step to start on, assuming from your replies that I'm rooted already.
I know it's a bit of a dumb question, but I just don't wanna fudge my new phone.
Arconaught said:
That's my next question, I'm using this guide ( http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2 ) to try and get S-Off to flash Cyanogen and I'm wondering what step to start on, assuming from your replies that I'm rooted already.
I know it's a bit of a dumb question, but I just don't wanna fudge my new phone.
Click to expand...
Click to collapse
I used the wiki method myself, those that used other methods (like Visionary) and were told to root via the wiki seem to have all just started at the beginning, from what I've read.
Sent from my HTC Vision using XDA App
Arconaught said:
That's my next question, I'm using this guide ( http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2 ) to try and get S-Off to flash Cyanogen and I'm wondering what step to start on, assuming from your replies that I'm rooted already.
I know it's a bit of a dumb question, but I just don't wanna fudge my new phone.
Click to expand...
Click to collapse
Whoa the Wiki method is completely different, looks like it was rewritten on 04/01.
You can completely ignore the temp rooting steps and concentrate on the gfree steps
From the "Necessary Files" section you need gfree, flash_image and ClockWorkMod Recovery
I would use the latest ClockWorkMod recovery rather than the one listed on the Wiki:
http://mirrorbrain.cyanogenmod.com/cm/recoveries/recovery-clockwork-3.0.2.4-vision.img (of course it's only the latest as of the time of this writing)
From step 2 you need to use:
Code:
$ adb push gfree /data/local/tmp/
$ adb push flash_image /data/local/tmp/
From step 2.a you need to use:
Code:
$ adb push recovery-clockwork-3.0.2.4-vision.img /data/local/tmp/recovery.img
Again note that the file name for CWM will depend on the version of CWM you are using.
Skip to step 4.b you need to use:
Code:
# cd /data/local/tmp
# ./gfree -f
# ./flash_image recovery recovery.img
# sync
Continue on as normal from here.
I skipped the temp root and perm root sections as you are already perm root.
I also skipped the ENG HBOOT parts, since that's not strictly necessary and the most risky part of the whole process (one mistake can result in a brick). If you want to flash the ENG HBOOT you would need to follow steps 4.a instead of 4.b, (you would also need the necessary HBOOT of course) the only command you need to omit from 4.a or 4.b is "# ./root_psn" which is the script which establishes permanent root.
Thanks a lot so far man, but I'm still stuck. I have adb, when I open it in the SDK, it flows for a bit, then closes. This is right, right? I'm meant to do all of these prompts via the cmd window?
OK, I've now sorted adb, but I can't get anything to work past that. Nothing will transfer to my phone and I'm going to kill... somebody.
Arconaught said:
OK, I've now sorted adb, but I can't get anything to work past that. Nothing will transfer to my phone and I'm going to kill... somebody.
Click to expand...
Click to collapse
You say you've sorted adb, but can you be more specific please ? What works and what doesn't work exactly ?
Ah, yeah, sorry. I got to the point where when I type in "adb devices" in the command window, it shows me my phone, with the serial number and whatnot. However, whenever i try the command:
$ adb push gfree /data/local/tmp/
It just won't work. I have all the files together in my desktop at the moment, having moved them from the downloads folder on my laptop. Is there a specific place I should have the stuff I need to send to my phone?
There is a great write up here about getting adb working. It sounds like either you didn't set up a "path" to use those commands anywhere or if you don't want to do that make sure your files are in the same folder as your adb.
Sent from my HTC Vision using XDA App
Arconaught said:
Ah, yeah, sorry. I got to the point where when I type in "adb devices" in the command window, it shows me my phone, with the serial number and whatnot. However, whenever i try the command:
$ adb push gfree /data/local/tmp/
It just won't work. I have all the files together in my desktop at the moment, having moved them from the downloads folder on my laptop. Is there a specific place I should have the stuff I need to send to my phone?
Click to expand...
Click to collapse
You need to have the files (extracted from the ZIP files you downloaded) in the same folder you run the ADB commands, if your ADB is in your path you should be able to run ADB commands from any folder.
To summarize you need to extract all the zips you downloaded under necessary files, all to the same folder. The open a command prompt and CD to that folder before you start using your adb push commands.
shortlived said:
There is a great write up here about getting adb working.
Click to expand...
Click to collapse
Yeah, steviewevie wrote it:
http://forum.xda-developers.com/showthread.php?t=865685
But it looks like he is willing to give the OP some personalized help.
Right, thanks guys, I think I'm making some progress.
ADB is all set up, and as far as I'm aware, having:
program files > android sdk > platform tools
on my path should mean I can open adb from anywhere right? I have all of the extracted files in platform tools, where adb is, in my program files... is this right, or have I completely missed the point here?
I keep getting "cannot stat 'gfree':: No such file or directory"
Sorry, I seem really stupid concerning this whole thing, but I'm sure it's something equally obvious that I'm just not seeing.
New problem. I worked out what I'd done wrong there, and got everything onto my phone. However, when trying to change the directory to /data/local/tmp, I keep getting "The system cannot find the path specified"
Now what am I doing wrong?
Arconaught said:
New problem. I worked out what I'd done wrong there, and got everything onto my phone. However, when trying to change the directory to /data/local/tmp, I keep getting "The system cannot find the path specified"
Now what am I doing wrong?
Click to expand...
Click to collapse
Remember you are running those commands (everything in that section) from an ADB shell, not from the Windows command prompt.
Excuse my ignorance, but what exactly do you mean by that? What should I do?
Hi everyone, I`m getting the "Main Version is older! Update Fail!" message and have run into a brick wall. Can anybody help? Hopefully the screen grab of the cmd has attached correctly so one of you clever people may be able to see it and know what is wrong.... I have not got a clue!
Too bad you didn't scroll down before you took the screen shot.
Agoattamer said:
Too bad you didn't scroll down before you took the screen shot.
Click to expand...
Click to collapse
That was it dude! Below Exploiting Device, it just went back to the start C:Users...ect. There was nothing else of interest.
Anybody know what went wrong?
Dazblink said:
That was it dude! Below Exploiting Device, it just went back to the start C:Users...ect. There was nothing else of interest.
Anybody know what went wrong?
Click to expand...
Click to collapse
If i remember correctly fre3vo exploits and then exits the shell.
If you use "adb shell" again, you should have root on your phone.
I followed the guide in the cyanogenmod wiki and it worked, so maybe have a look at that:
http://wiki.cyanogenmod.com/wiki/HTC_Desire_HD:_Firmware_Downgrade_(Gingerbread)
Your error sound like you didn't use misc_version.
Dlog said:
If i remember correctly fre3vo exploits and then exits the shell.
If you use "adb shell" again, you should have root on your phone.
I followed the guide in the cyanogenmod wiki and it worked, so maybe have a look at that:
http://wiki.cyanogenmod.com/wiki/HTC_Desire_HD:_Firmware_Downgrade_(Gingerbread)
Your error sound like you didn't use misc_version.
Click to expand...
Click to collapse
yeah i think that's right, i think you will exit shell after the exploit. if you type adb shell and you get a # you're root. if you get a $, try typing su then hit enter and if you get a # you're root
i followed the guide that Dlog linked to and it worked well so i would definitely do that. but i guess that's what you're doing anyway?
it is because the update package in your sdcard is older than your device running right now,
that's why after fre3vo and got root in adb shell (the # sign), you run this command
./misc_version -s 1.31.405.6 , to make your DHD think the update package is newer, and do the update from the IMG file in your sdcard
after update complete (downgrade), you can now use visionary+ to root .
BTW, what's your build number ?
Sorted it cheers! Typed in abd shell again and got the #
Thanks for the replies!
Hi guys I have been trying to unlock my Samsung Galaxy S I9000 for some time now with no luck. I have tried two (samsung unlock and the xda) methods and both has failed. There is a problem generating the codes. Maybe I did too much flashing in the begining I don`t know . Can anyone help me with this please? I have added a jpeg to see if that helps.
sirgen said:
Hi guys I have been trying to unlock my Samsung Galaxy S I9000 for some time now with no luck. I have tried two (samsung unlock and the xda) methods and both has failed. There is a problem generating the codes. Maybe I did too much flashing in the begining I don`t know . Can anyone help me with this please? I have added a jpeg to see if that helps.
Click to expand...
Click to collapse
you get permission denied error ..
do this in terminal
Code:
adb shell
su
chmod 777 /efs/nv_data.bin
exit
exit
after this you can
Code:
adb pull /efs/nv_data.bin
ruscan.calin said:
you get permission denied error ..
do this in terminal
Code:
adb shell
su
chmod 777 /efs/nv_data.bin
exit
exit
after this you can
Code:
adb pull /efs/nv_data.bin
Click to expand...
Click to collapse
Thanks for the quick response. but bare with me cause I don`t understand the instructions. How do I go about doing it in terminal?
I unlocked my SGS by using an app called Galaxy_S unlock by Helroz from the play store.
If it doesn't work try downgrading to froyo as I unlocked mine when I was on 2.2.
Sent from my GT-I9000 using XDA
sirgen said:
Thanks for the quick response. but bare with me cause I don`t understand the instructions. How do I go about doing it in terminal?
Click to expand...
Click to collapse
It seems you have adb.exe tool already installed but you get error because you do not have enough rights on your phone so get the rights by these lines..
by terminal here I mean cmd.exe from Windows
so enter cmd Start/Run/cmd.exe
then to start adb server enter this
Code:
adb devices
then in cmd enter
"adb shell" press Enter (in fact this is "terminal" - a way to get access on your phone and enter commands)
then "su" press Enter
and so on..
Code:
adb shell
su
chmod 777 /efs/nv_data.bin
exit
exit
lastly enter
Code:
adb pull /efs/nv_data.bin
now you get nv_data.bin on your PC check for this file in the folder where adb.exe is located usually ~\android-sdk\platform-tools\adb.exe
You have the advantage of a well-known phone so there are solutions for everything
by example look here for a tutorial to unlock your phone
If you do not understand something let me know about
This is the case you want to work from scratch the easy way is to search on Market/ Google Play for an app to unlock this phone
Wow it is not easy to get past this image verification at all. Anywho............ So I have properly installed the SDK and I also installed a stock rom (I9000XXJP2) and rooted it and Now I get this result displayed in the attached pic. I have tried to follow the instructions given by ruscan.calin (and thanks for the "look here for a tutorial to unlock your phone" link) but I again I am back at a dead end.
sirgen said:
Wow it is not easy to get past this image verification at all. Anywho............ So I have properly installed the SDK and I also installed a stock rom (I9000XXJP2) and rooted it and Now I get this result displayed in the attached pic. I have tried to follow the instructions given by ruscan.calin (and thanks for the "look here for a tutorial to unlock your phone" link) but I again I am back at a dead end.
Click to expand...
Click to collapse
It seems you are the right way now you have an unlocked nv_data.bin
replace on phone and give rights follow that tutor
I can help you but give me more details because I don't have this phone
what did you do ?
ruscan.calin said:
It seems you are the right way now you have an unlocked nv_data.bin
replace on phone and give rights follow that tutor
I can help you but give me more details because I don't have this phone
what did you do ?
Click to expand...
Click to collapse
I installed the SDK and put in the path for the ADB folder. Then I installed a stock rom (I9000XXJP2) and rooted it although I think I did not have to root it. I then used the "Generate_Code" script from XDA. But I still don`t get the NCK and Freeze codes. Should I try another rom?
sirgen said:
I installed the SDK and put in the path for the ADB folder. Then I installed a stock rom (I9000XXJP2) and rooted it although I think I did not have to root it. I then used the "Generate_Code" script from XDA. But I still don`t get the NCK and Freeze codes. Should I try another rom?
Click to expand...
Click to collapse
root is very important if not you can not play with nv_data.bin file...
what link ? and how did you do what steps I can't guess show me some logs screenshots anyway more info !
[QUOTE su
chmod 777 /efs/nv_data.bin
exit
exit
Then from the DOS command prompt:
adb pull /efs/nv_data.bin
Step 5: Select the file on the main Samsung Galaxy S Unlocker & Repair page
Step 6: Enter your desired Unlock and Unfreeze Codes and click the SUBMIT button
Step 7: Download the new file that is generated for you
Step 8: From ADB shell (Type "adb shell" at the DOS command prompt) or a terminal on your phone, enter the following commands to backup your current EFS related files, in case something goes wrong. ![/QUOTE]
After I have followed the instructions up to "steps 4" I am not sure what I should do for steps 5,6, and 7. I don`t know where "the main Samsung Galaxy S Unlocker" is. I included two pics of tmy adb shell (adb pull /efs/nv_data.bin)
I also copied an efs folder from my phone onto my pc.
sirgen said:
After I have followed the instructions up to "steps 4" I am not sure what I should do for steps 5,6, and 7. I don`t know where "the main Samsung Galaxy S Unlocker" is.
Click to expand...
Click to collapse
here is it http://www.communityhosting.net/sgsunlock/
ruscan.calin said:
here is it http://www.communityhosting.net/sgsunlock/
Click to expand...
Click to collapse
Brilliant!!!! My SGS is unlocked . Thank you ever so much ruscan.calin for helping me to do this and putting up with me too. I am truly grateful.
problem solved
sirgen said:
Brilliant!!!! My SGS is unlocked . Thank you ever so much ruscan.calin for helping me to do this and putting up with me too. I am truly grateful.
Click to expand...
Click to collapse
I like your answer this is like 100 thanks for me !
also as Vertron said there are apps in Market to unlock this well-known phone
Vertron said:
I unlocked my SGS by using an app called Galaxy_S unlock by Helroz from the play store.
If it doesn't work try downgrading to froyo as I unlocked mine when I was on 2.2.
Sent from my GT-I9000 using XDA
Click to expand...
Click to collapse
My sincere apologies to you my friend. I was able to unlocked my SGS after I followed your advice of downgrading to froyo and then I continued with the tutorial I got through Member ruscan.calin. So excess amount of thanks to you both. I will make sure to properly BACKUP my SGS3 before I touch it. I have learnt my lesson. Thanks again.
aarlene said:
Hi,
You can unlock your Samsung Galaxy S I9000 using unlock codes!! Unlocking using codes is easy and also safe!! You can get the codes from your service provider or from reliable online sites!!!Personally, I would suggest prounlocking.com , here they provide accurate codes at reasonable price!!!
Click to expand...
Click to collapse
Thanks for the heads up, but I did it with the help of XDA
Vertron said:
I unlocked my SGS by using an app called Galaxy_S unlock by Helroz from the play store.
If it doesn't work try downgrading to froyo as I unlocked mine when I was on 2.2.
Sent from my GT-I9000 using XDA
Click to expand...
Click to collapse
Thanks