Related
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, I've got a noob question here: How do I properly remove Super User from my GSM Galaxy Nexus?
I used Wugs Root Toolkit and it applied some "permanent" superuser method. My question is, how can I go about deleting the files so that the APK is no longer on my phone? I don't mind rooting again if that's what is required to remove it.
I searched around and didn't find an answer--that said if this has already been answered somewhere before I apologize--maybe I just all around fail! I saw some posts that related to the Hero but yeah... pretty sure it doesn't apply to the GNex.
Thanks! Oh, and don't ask me why I want to do this, yeah yeah, I know I must be out of my mind. A follow-up question though, would be that if I decide to root again after this, is there a method of pushing superuser where it will be removed whenever the stock ROM is updated?
Thanks again!
Just use root explorer to delete it from system/ app
Sent from my Galaxy Nexus using Tapatalk 2
I was under the impression that, that would not completely work? Isn't there another file somewhere that has to be removed as well? Thanks for the response!
shadrage said:
Hi, I've got a noob question here: How do I properly remove Super User from my GSM Galaxy Nexus?
I used Wugs Root Toolkit and it applied some "permanent" superuser method. My question is, how can I go about deleting the files so that the APK is no longer on my phone? I don't mind rooting again if that's what is required to remove it.
I searched around and didn't find an answer--that said if this has already been answered somewhere before I apologize--maybe I just all around fail! I saw some posts that related to the Hero but yeah... pretty sure it doesn't apply to the GNex.
Thanks! Oh, and don't ask me why I want to do this, yeah yeah, I know I must be out of my mind. A follow-up question though, would be that if I decide to root again after this, is there a method of pushing superuser where it will be removed whenever the stock ROM is updated?
Thanks again!
Click to expand...
Click to collapse
This is another example of the pitfalls of trying to take shortcuts by using toolkits. Toolkits are fine to save time for those that understand what the toolkit is doing, but if you don't have that knowledege base, yo really should do things manually first, in order to learn. (In school, they don't let you use a calculator until you can add/sub/mult/div for a reason).
Take a look at this post, specifially method 2. See if you can figure out what those commands are actually doing.
I will help you out: you are essentially mounting the system partition as read-write, copying two files to the system, changing permission on the system, and then mounting the system as read-only.
So, in order to remove root, you need to mount the system as read-write, remove those two files (command is rm) and mount the system as read-only. [EDIT: depending on where the toolkit you used place su, it could be somewhere else than /system/bin, like /system/xbin or /system/sbin -- yet another reason not to use toolkits...]
Toolkits don't teach you that.
And for you follow-up question, the answer is no (if you are talking about updates). If you update using an OTA update, the update does not delete those two files, but it does change the permissions on them to disable root access.
Thanks Efrant! I'll try this out. Yeah, being lazy definitely didn't help me here
I used to flash my Vibrant all the time, but I got the Nexus so that hopefully I wouldn't need anything besides stock (for which I love the experience), so I'm just trying to stay as pure as possible
Thanks again, appreciate it!
shadrage said:
Thanks Efrant! I'll try this out. Yeah, being lazy definitely didn't help me here
I used to flash my Vibrant all the time, but I got the Nexus so that hopefully I wouldn't need anything besides stock (for which I love the experience), so I'm just trying to stay as pure as possible
Thanks again, appreciate it!
Click to expand...
Click to collapse
Give it a shot, and if you are having issues, post here and I'll guide you through it.
Appreciate it! I'll be fiddling around with it either tomorrow or the next day--pretty slammed this week.
Thanks again.
Let me know
shadrage, let me know what you figure out, and how you went about it, I'm stuck trying to figure out the same thing. If I figure it out, I'll give you instructions here.
nodnerb said:
shadrage, let me know what you figure out, and how you went about it, I'm stuck trying to figure out the same thing. If I figure it out, I'll give you instructions here.
Click to expand...
Click to collapse
It's very simple. If you still have root, just use root explorer and delete two files:
1) /system/app/Superuser.apk
2) the second file is su, and it could be in one of three places, depending on how you rooted:
/system/bin/su OR
/system/sbin/su OR
/system/xbin/su
That's it.
If you do not have root, go to the dev section and find an insecure boot image for the version of Android that you are running, download it, rename it to boot.img (if it isn't already), and place it in the same directory on your PC as you fastboot.exe and adb.exe files. Then boot into fastboot mode, plug your phone into your PC and type the following:
fastboot boot boot.img (wait for the device to boot)
adb remount
adb shell
rm /system/app/Superuser.apk
rm /system/bin/su
rm /system/sbin/su
rm /system/xbin/su
Done.
Now if you do not have root, and your bootloader is locked (and you are running 4.0.4), then you are out of luck. You will need to unlock your bootloader (which will wipe your data), and do the second method above/
Thanks
Thanks Efrant.
I'm trying to learn the ins and outs of adb, and it confuses me to no end. I'm slowing remembering playing with my dad's DOS computer when I was a kid, so command prompt and shell type work is coming back, but not easily.
efrant said:
This is another example of the pitfalls of trying to take shortcuts by using toolkits. Toolkits are fine to save time for those that understand what the toolkit is doing, but if you don't have that knowledege base, yo really should do things manually first, in order to learn. (In school, they don't let you use a calculator until you can add/sub/mult/div for a reason).
. . .
Click to expand...
Click to collapse
Exactly!
And how to only remove Superuser data?
I mean, I want Superuser to ask me again if I grant or not superuser-permision.
I need this because I have in Superuser 5 times Titanium Backup.
All has the same id but only one has the Titanium Backup icon and the other doesn't.
And if I try deleting the app from the list... the app just go to "Denied" but still there.
So, I want to delete the whole data so I get a clean list of apps.
Thanks!
settings >> apps >> all apps >> super user
clear cache, clear data
3rdstring said:
settings >> apps >> all apps >> super user
clear cache, clear data
Click to expand...
Click to collapse
Thanks man! I cannot believe I did not try that before.
Thanks!
efrant said:
If you do not have root, go to the dev section and find an insecure boot image for the version of Android that you are running, download it, rename it to boot.img (if it isn't already), and place it in the same directory on your PC as you fastboot.exe and adb.exe files. Then boot into fastboot mode, plug your phone into your PC and type the following:
fastboot boot boot.img (wait for the device to boot)
adb remount
adb shell
rm /system/app/Superuser.apk
rm /system/bin/su
rm /system/sbin/su
rm /system/xbin/su
Done.
Now if you do not have root, and your bootloader is locked (and you are running 4.0.4), then you are out of luck. You will need to unlock your bootloader (which will wipe your data), and do the second method above/
Click to expand...
Click to collapse
Having the same issue (I'm about to return the phone for a replacement so I want Superuser gone).
Can you maybe possibly kindly point me toward a good boot version of the file you're talking about? I'm running a Verizon Galaxy Nexus and I'm on version 4.0.4 Build IMM76K.
I found this link: http://forum.xda-developers.com/showthread.php?t=1631796 ...but I'm unsure what I should be downloading, renaming and throwing into my fastboot folder.
I understand I'll have to unlock the bootloader, but I'm going to wipe anyway since I'm sending it back. Any help with that part would be appreciated too.
Sorry if this is an unauthorized thread resurrection.
USA Prime Credit Peggy said:
Having the same issue (I'm about to return the phone for a replacement so I want Superuser gone).
Can you maybe possibly kindly point me toward a good boot version of the file you're talking about? I'm running a Verizon Galaxy Nexus and I'm on version 4.0.4 Build IMM76K.
I found this link: http://forum.xda-developers.com/showthread.php?t=1631796 ...but I'm unsure what I should be downloading, renaming and throwing into my fastboot folder.
I understand I'll have to unlock the bootloader, but I'm going to wipe anyway since I'm sending it back. Any help with that part would be appreciated too.
Sorry if this is an unauthorized thread resurrection.
Click to expand...
Click to collapse
Follow the instructions in this thread. It will take you back to stock, and there are instructions on re-locking the bootloader as well.
Had to restock my Nexus as well. but my USB didnt work so I decided to take my losses and just return it, rooted with Superuser.
I had spend 2 days trying to restock it. and then this Tech Guy from my Carrier Tells me...
O you have rooted your Phone. Well that might be a problem with the insurance... unless you got a Nexus Device.
I was like what do you mean.
wel with all nexus devices you are allowed to root your phone.
So I think this is the best Solution there is . just take it back and save yourself some time.
this really works!!!!
shadrage said:
Hi, I've got a noob question here: How do I properly remove Super User from my GSM Galaxy Nexus?
I used Wugs Root Toolkit and it applied some "permanent" superuser method. My question is, how can I go about deleting the files so that the APK is no longer on my phone? I don't mind rooting again if that's what is required to remove it.
I searched around and didn't find an answer--that said if this has already been answered somewhere before I apologize--maybe I just all around fail! I saw some posts that related to the Hero but yeah... pretty sure it doesn't apply to the GNex.
Thanks! Oh, and don't ask me why I want to do this, yeah yeah, I know I must be out of my mind. A follow-up question though, would be that if I decide to root again after this, is there a method of pushing superuser where it will be removed whenever the stock ROM is updated?
Thanks again!
Click to expand...
Click to collapse
1. after you have or have not unrooted, search up superuser on playstore
2. click uninstall, if it says uninstalling........, ignore that and go to home page
3. go to folder and delete cwm-root thingy(the zip file you copied to your folder when you rooted) and delete that(seriously, thats important)
4. make sure you have the root remover file in your external sd card
5. turn off device, reboot by holding power and down/left
6. select install zip from sd card and install the root remover file
7. reboot and superuser should be gone lol
keep in mind that i did this on my galaxy tab 2 10.1 so it will definitely work on that
should work with any device
hope this helped
lol
wow, old thread...
I have use root explorer to delete the Superuser.apk and system/bin/su
but once i restart my device, those two thing happen again and again.
Help!!!
Okay so I can't find a clear guide on how to root the Sprint Gnex on a Mac. I know it is simple but there is no clear guide on how to do so. I have searched on XDA and Googled it, Can someone please tell me how they rotted their's or if you know of an easy way to do so.
Thanks
Urge
Exact same as windows, except all of the commands are in Terminal instead of Command Prompt, and you put "./" before the commands.
Ex:
Code:
./adb devices
Here's the Mac ADB and Fastboot that I've used countless times attached. Unzip to your home folder and put any images or files you're gonna need for flashing in that folder. I'll assume you know how to navigate Terminal well enough to find the folder.
martonikaj said:
Exact same as windows, except all of the commands are in Terminal instead of Command Prompt, and you put "./" before the commands.
Ex:
Code:
./adb devices
Here's the Mac ADB and Fastboot that I've used countless times attached. Unzip to your home folder and put any images or files you're gonna need for flashing in that folder. I'll assume you know how to navigate Terminal well enough to find the folder.
Click to expand...
Click to collapse
I am trying to root my gs3 will this guide be along the same lines for my device and also how do I go about using the terminal to root it?
moderntech- said:
I am trying to root my gs3 will this guide be along the same lines for my device and also how do I go about using the terminal to root it?
Click to expand...
Click to collapse
What the hell? Why did you bump a thread that is like more than 5 months old?
Sent from my i9250
bk201doesntexist said:
What the hell? Why did you bump a thread that is like more than 5 months old?
Sent from my i9250
Click to expand...
Click to collapse
This thread has the closest information that I need to root, and instead of starting a new thread and potentially not having someone answer my question I am contacting you, the one that provided said information to pick your brain.
moderntech- said:
This thread has the closest information that I need to root, and instead of starting a new thread and potentially not having someone answer my question I am contacting you, the one that provided said information to pick your brain.
Click to expand...
Click to collapse
This is the Google Galaxy Nexus forums!
sent from my Google Galaxy Nexus
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
I have been trying for 3 days straight now to modify this phone. So far I have been able to get temp root using king root, and am able to us ADB as su. That's as far as I've gotten. Neither CWM nor TWRP are compatible with my phone. I was going to attempt to manually port CWM to my phone, but I have no idea how to dump the recovery image. I would really like to install some custom firmware on this thing, but it is seeming to be impossible. How can i pull the recovery image off my phone? I've tried using a dozen apps now to try and backup my recovery image but none are doing what I need.The lack of any information or support online is making me rage hard.Wtf dude. Someone please help me.
Please forgive me for double posting. But I could really use some help dumping the rom. I've tried everything. All the guides I'm finding are 2-3 years old.
try this
stock system.img, boot.img, & recovery.img from someone who has not yet installed TWRP or supersu. To do this, install kingroot 4.5 and terminal emulator and run kingroot to get temp root. Then open terminal emulator and enter the following commands without the ""
"su"
"cd /dev/block/platform/7824900.sdhci/by-name"
"dd if=boot of=/sdcard/boot.img"
"dd if=recovery of=/sdcard/recovery.img"
"dd if=system of=/sdcard/system.img"
You will need to make sure you have at least 3GB of internal storage space before doing this just to be safe. The system.img will probably be about 1.5GB I did this and I got all three files saved to the root of my sd card. it would be easier for you do do this your self I am over my data cap so I cant upload the file
Anyone ever find a working root? I just got this phone a week ago and it is pretty dam good phone for the money. I need root so I can tether.
I also am waiting for root this phone is beast and I want compile a custom kernel for it but with root and a source I can't do jack sqwat.