yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] klone96:
i cant seem to install the sdk/adb.. but thats not my question.. i tryed rooting my sns using this method can some one tell me if its real or just some easy way to brick my device !? tia..
[Nexus S Android Development] aref9200:
Hi dear Koush

I need you to help me to solve my problem.I rooted my nexus s i couldn't install the ROM via clockwork recovery and I cant boot the main ROM.is there any way to flash ROM or moving file to SD via fastboot?
[Nexus S Android Development] mzalan:
I'm just getting my Nexus S tomorrow. Is flashing the recovery image necessary to execute su on the device?

I'm asking because I will want to tether it to my laptop to use a wired internet connection, and I read here that I'll have to setup the usb0 interface on the phone, which is executed either from ADB shell or the terminal emulator on the phone, the latter of which includes a su. Will I be able to do this from ADB without installing the recovery image?

Thanks in advance!
[Nexus S Android Development] ceyad:
same problem.

rooted and custom recovery but can't instal custom ROM.

ur device i9023?
[Nexus S Android Development] flow68:
Woow I think I'm gonna wait before rooting this time, I purchased a new SNS yesterday and don't want this to happend.

It is a i9023 and I can't find somebody who rooted it properly without problems
[Nexus S Android Development] Bandis710:
I think you have misread our remarks .. I own a 9023 and rooted it without problems , also installing custom roms is no problem .. The only problem is that you can not use rom manager , because it installs an incompatible cwm .. If you follow the thread rooting your nexus s 9023 only you will be fine .. Just be sure to pick the latest cwm.img from the 3.0.2.4 cwm thread .

So if you have a 9023 nexus s , follow the instructions in this thread :http://xdaforums.com/showthread.php?t=1007782

in the lasest step it links to an old cwm.img so instead of that one get the newest one from this thread : http://xdaforums.com/showthread.php?t=988686 , right now the newest is : 3024v3-i9023.img

You will have a 9023 compatible cwm then and will be able to flash custom roms etc without problem
[Nexus S Android Development] mntbkr:
I have a question: I will be getting the sns (cdma, wimax) when its released on Sprint. I understand some of the hardware will be different(mainly radios), is it safe to assume that the rooting process will differ from the (gsm, hspda) version? Also is cwmr the only recovery available? I prefer Amon on my evo as cwmr has always has issues on that device. Thanks for any info you guys can provide.
[Nexus S Android Development] dovid:
B"H

I am doing exactly as told:

-Fastboot oem unlock

-fastboot flash recovery 3024v3-i9023.img

-Reboot into bootloader to get superuser loaded

-Reboot the phone - adb install rootexplorer.apk

-Rename image-recovery.sh -> image-recovery.sh.old

-reboot into fastboot

-fastboot flash recovery 3024v3-i9023.img again (incase it was replaced)

-reboot into recovery

-update from zip file : 233-stock-deodexed-root.zip

ALWAYS GET THE FOLLOWING ERROR:

assert failed: write_raw_image("/tmp/boot.img","boot")

E:error in /sdcard/Stock-233-Deodexed-Root.zip (Status 7)

Installation Aborted

PLEASE HELP????
[Nexus S Android Development] ogdobber:
in clockwork recovery choose "install zip from sdcard" then "choose zip from sdcard"

you will get it then;)
[Nexus S Android Development] dovid:
B"H

Thanks for the tip, but that is what I am doing already.

The zip install is executing ... but failing.

I've tried this on two phones already, with same results.

Please help.
[Nexus S Android Development] Jwtiyar:
when entered fastboot oem unlock in command prompt it say fastboot : command not found .

i have linux/ubuntu ,.

thanks.
[Nexus S Android Development] martin0285:
Screw the Galaxy S!!! the N1!!!!
[Nexus S Android Development] joedon3:
Google is going to push an offical release to the N1 probably tomorrow or something. let the SGS folks get some love! we're so neglected by Samsung....:(
[Nexus S Android Development] rajendra82:
Koush is selling his N1. Abandon ship.
[Nexus S Android Development] kensdavid:
Awesome work Koush, you are a legend.

Those fastboot commands are to be entered via ADB?

Can you provide instructions without ADB?
[Nexus S Android Development] skyline247:
Faster than a speeding bullet, koush you da man. Thanks bro. God I love XDA Developers!
[Nexus S Android Development] TheBiles:
Ok, so I unlocked the bootloader (then rebooted), installed ClockworkMod, flashed the SU zip, then installed the rooted boot image. How come any time I attempt to run a root-required app it tells me that I don't have root?
[Nexus S Android Development] Michael.B.:
I am having the same exact issue.

Flashed and now have the ClockworkMod recovery, and then flash the zip file from superuser. It installs that, and I reboot, but do not have SU access.
[Nexus S Android Development] godsfilth:
same here i have SU in ADB but not where it matters for easy use you know on th phone itself i tried to "su" in a terminal and it said permission denied and didnt popup the super user app
[Nexus S Android Development] D_Rob:
Thanks Koush, you have saved my tail like twice. I get to Googl'infg and my answer are usually in your post.
[Nexus S Android Development] avetny:
thank you sir !
[Nexus S Android Development] ale0crysis:
Awesome, give to Galaxy S the crown NOW!!!11 :D
[Nexus S Android Development] ITABruto:
When I connect the device and do:

adb devices

I get:

List of devices attached

but no device is listed, any other device I have works, vibrant and mytouch.

Any idea?
[Nexus S Android Development] TheBiles:
Did you install the drivers?
[Nexus S Android Development] demo23019:
Worked perfectly thank you
[Nexus S Android Development] clubtech:
So do i need to install the superuser.zip OR the insecure booth image?

Or do i need to install BOTH?

From what i remember from the N1 days - only insecure boot img is needed.

Can someone please confirm?
[Nexus S Android Development] ITABruto:
Yes, drivers revision 4.

I can see the sdcard, but cannot see the phone on the device list.
[Nexus S Android Development] godsfilth:
figured out how to get around my issue (not the cause but hey a step forward) anyone thats having trouble with the .zip not working adb into system/bin and see if su is actually there for whatever reason it wasnt in mine i pushed it and "chmod 6755" now it works just wish i knew why it didnt in the first place
[Nexus S Android Development] Michael.B.:
That is exactly what I saw. I already pushed and am doing the chmod now.
[Nexus S Android Development] Michael.B.:
Worked perfectly.
[Nexus S Android Development] nxt:
I would like to know this too, do we NEED to push the insecure boot image?
[Nexus S Android Development] hansmrtn:
Works great! Thanks Koush!
[Nexus S Android Development] TheBiles:
That did it! Thanks!
[Nexus S Android Development] slowz3r:
Im tempted to do this, but i think ill keep it stock for a while. until we see what CM 6.9999 has to offer. or CM7
[Nexus S Android Development] nxt:
How/where do I put su-2.3.6.1-ef-signed.zip?

I put it on my "sdcard" but clockwork mod can't see it?
[Nexus S Android Development] Michael.B.:
I put it right on the main folder and installed it while navigating to it in recovery.
[Nexus S Android Development] nsavani:
cant get root access. i got the recovery working and when i tried to install superuser via recovery it installed but didnt work. i looked in system/bin and su wasnt there so i pushed it via adb successfully. i see su in system/bin and have superuser installed but still cant get apps to get root access.
[Nexus S Android Development] Michael.B.:
You need to adjust the chmod on su.

Do a remount and adb shell, then cd to /system/bin then type: chmod 6775 su

You should now be able to type su and it should work.
[Nexus S Android Development] nsavani:
thanks, worked great
[Nexus S Android Development] zomer86:
Anybody in here that can make a movie tutorial, i'll pay you for it.
[Nexus S Android Development] ITABruto:
Anybody else lost the task manager when holding home?

I see only recent application, no more task manager.
[Nexus S Android Development] nxt:
Please help me out here.

I did fastboot oem unlock jsut fine, wiped my phone. flashed clockworkmod just fine. boot up phone, turned off, went back to recovery, flashed su-2.3.6.1-ef-signed (is this the right one?) that flashed fine.

boot phone back up, i see no superuser app/icon?

Now what?

I tried downloading superuser app from market, doesn't work.

I'm trying to do this:

------

You need to adjust the chmod on su.

Do a remount and adb shell, then cd to /system/bin then type: chmod 6775 su

You should now be able to type su and it should work.

------

What do I remount? what's the exact command?

i know how to adb shell, then cd to /system/bin, and type chmod 6775 su, but doesn't work, i dont know what the remount command is.

THanks.
[Nexus S Android Development] ITABruto:
adb remount didn't work for me, permission denied.

So what you need to do is restart in recovery:

adb reboot recovery

then use the +/-volume keys to mount the file system

extract su-2.3.6.1-ef-signed.zip

then

push <location where you extracted the file>\system\bin\su /system/bin/

push <location where you extracted the file>\app\SuperUser.apk /system/app

then

adb shell

cd /system/bin

chmod 6775 su

then restart the phone.
[Nexus S Android Development] Anderdroid:
Rooting wouldn't work for me. Had to go in the recovery to "mounts and storage" then mount /system. Then flash the zip and then it worked. Should add this to the steps.
[Nexus S Android Development] bblanski:
This worked perfect. Thanks
[Nexus S Android Development] nxt:
thank you, it worked!
[Nexus S Android Development] rsfaze:
why port when we have the source? :eek:
[Nexus S Android Development] r0adki111:
Ok so maybe I'm dumb, but is there an option I need to select once inside the bootloader? I have adb working, and can see my nexus one with fastboot, but the nexus s does not show up when I type

fastboot devices

Again I am just doing this in the main menu after pressing volume up and power. Thank you.
[Nexus S Android Development] DKYang:
Perhaps you are missing the Android 1.0 driver need for fastboot to work. Go to this thread and follow the instructions about installing PDAnet: http://xdaforums.com/showthread.php?t=875580

Once you see the device. Just enter the command to flash recovery. Then use volume buttons and select recovery. Then mount /system/, install superuser, then chmod it.
[Nexus S Android Development] miguelrodas:
I'm having the very same issue and I have the Android 1.0 driver from PDAnet installed. what should I do?
[Nexus S Android Development] r0adki111:
Ok what I did to get fastboot working on Nexus S is this:

In device manager, right click on Android 1.0 I think it was, and click update driver. Browse for a driver and click "let me pick from a list..." Click on "Samsung Android Composite ADB Interface. and click next.

This worked for me. Now as far as actually having "su" that is another story, so far I can't get it.
[Nexus S Android Development] miguelrodas:
I did figured out how to do it but now I don't have the "Samsung Android Composite ADB Interface" option. I think I have all the necessary drivers or do I need to get something else from samy's site?

Thanks
[Nexus S Android Development] blunden:
Probably same as always. Unyaffs

If you run linux/bsd you will know how to compile it. As simple as it can be.

If you run Windows you can use the binary I compiled in Cygwin when I needed it in Windows.

EDIT: Just remembered that the NS might not use yaffs2 at all. You should be able to see that in 'mount'.

EDIT 2: Sure enough, didn't work. What is the system partition mounted as?
[Nexus S Android Development] r0adki111:
Sorry I am unsure on that part. Hopefully someone else knows.

I got su working on it though, for some reason Titanium Backup says it is not getting root priveledges even though I have accepted it when superuser asked. I can also su in terminal.
[Nexus S Android Development] blunden:
The usb-drivers in the SDK should probably have the Nexus S hardware id added in them. If not, you could always add it manually to the inf and then install them.
[Nexus S Android Development] miguelrodas:
I assume you are talking about the drivers called "revision 4" or something like that in the SDK. I've removed them and reinstalled it several time but is not working. I guess I'll try again on my windows netbook when I get home as I'm doing it on my work computer now.

Thanks for your help
[Nexus S Android Development] GrandMstrBud:
When going to run the fastboot command I get the following window that pops up. It says "fastboot.exe - Unable to locate component" and in the dialog box it says "This application has failed to start because AdbWinApi.dll was not found. Re-installing the application may fix the problem". Yes I do have the latest SDK installed and also the google USB drivers. What do I need to do to get this thing working? I got it on 2 different computers and it's driving me crazy. I've never had any issues getting this to work on other phones.
[Nexus S Android Development] cnrock:
congratulations:)
[Nexus S Android Development] k0mpresd:
here is the file it says you are missing. place in directory with fastboot: http://mycarbl0ws.com/abd.rar
[Nexus S Android Development] nerdrum:
I can't get fastboot to work on OSX. any suggestions?
[Nexus S Android Development] sstang2006:
I don't know if you guys know this already but adb.exe moved from c:\android-sdk-windows\tools\ folder to c:\android-sdk-windows\platform-tools\

I was having problem with adb not found and that was the problem.

cd c:\android-sdk-android\platform-tools

adb devices
[Nexus S Android Development] b16a2smith:
anyone successful getting the rom manager to flash the recovery?
[Nexus S Android Development] distortedloop:
Are you in the proper directory or have the fastboot exe in your path?? Are you putting "./fastboot" instead of just "fastboot"?
[Nexus S Android Development] nerdrum:
I'm using an old nexus one fastboot file I had from my old phone. I'm doing ./fastboot-mac oem unlock exactly how I did it on the nexus.
[Nexus S Android Development] GrandMstrBud:
I found the file in another directory and copied it to the right one and now when I do fastboot devices it does not show anything. Boy this is frustrating.
[Nexus S Android Development] soulashell:
what if I do a format system on clockworkmod recovery? does it revert it back to stock?
[Nexus S Android Development] delirial:
I've got a question. I managed to execute the commands. The Superuser install (ef) seemed to have run successfully. If I do 'adb shell', I'm automatically in root. However, if I run an app that requires root like say, Titanium, I get an error because it was not able to acquire root.

Is it supposed to be that way? Root for the shell, but not for the apps?

Regards,

del
[Nexus S Android Development] b16a2smith:
no. no. no.
[Nexus S Android Development] ogdobber:
no, check in your system/bin and see if su is in there.
[Nexus S Android Development] mprziv:
I'm in the same position. I checked...su is not there. It IS under /getroot on the phone. What steps do I need to take in order to get root. Thanks for your help.

I'm using osx, so I think the commands may be slightly different.
[Nexus S Android Development] delirial:
It's not in /system/bin. I installed 'su-2.3.6.1-ef-signed.zip' via clockwork recovery. Did I get the wrong file?
[Nexus S Android Development] jroid:
I have NO idea why my phone isn't rooted. first, I flash the rooted boot.img didn't work. Then i flashed cw recovery and the su zip but yet again no root. I then attempted to manually root and push all the files su to /system/xbin superuser.apk to /system/app and busybox to /system/xbin and set su and busybox executable with chmod 0655. I'm getting annoyed..
[Nexus S Android Development] ogdobber:
-you need to delete your superuser (if is shows up in your apps)(on your phone)

-then go to chains thread on the op and download the zip

-extract the zip to your tools folder

-adb push superuser.apk /system/app/superuser.apk

-adb push su /system/bin/su

-now do a adb remount

-then adb shell

-then cd to /system/bin

-then type- chmod 6775 su

-the type- su

-done
[Nexus S Android Development] mprziv:
Same here...except I got an error when I installed "su-2.3.6.1-ef-signed.zip" through clockwork. It said "bad"...couldn't install. Any help is very appreciated.
[Nexus S Android Development] mprziv:
When I extract the zip to my tools folder, I am extracting a folder called "su-2.3.6.1-ef-signed" the superuser.apk is in that folder, under "su-2.3.6.1-ef-signed/system/app"

Would that change my adb push commands?

I also seem to be getting an error.

failed to copy 'superuser.apk' to '/system/app/superuser.apk': Read-only file system

Thanks for your help, I appreciate it.
[Nexus S Android Development] jroid:
lol. you don't need to extract the zip to the tools folder. It's not a binary file that u can cd to and execute
[Nexus S Android Development] mprziv:
Ok, do you think you could help me out?
[Nexus S Android Development] jroid:
u need to remount your /system as read/writable type this:

adb shell
mount -o rw,remount /dev/block/mmcblk0p2 /system

you should get a

#
[Nexus S Android Development] jroid:
got it. where your su is it needs to be executed with 6775 instead of 0655 as I previously thought.

su can be pushed to either /bin or /xbin

but I also installed busybox to where I had su installed, which in my case, was /system/xbin/

I noticed the su zip from chainsDD doesn't include busybox in the zip so I pushed it
[Nexus S Android Development] ajftl:
Lol good one
[Nexus S Android Development] jroid:
Busybox

Here is busybox that can be pushed to either /bin or /xbin
[Nexus S Android Development] mprziv:
That worked, i then exited shell, and

./adb push superuser.apk /system/app/superuser.apk

2352 KB/s (196521 bytes in 0.081s)

Now, when I try to push su /system/bin/su I get an error.

./adb push su /system/bin/su

cannot stat 'su': No such file or directory
[Nexus S Android Development] delirial:
Is anyone having problems with bluetooth after loading the recovery and rootboot.img?

I also made an attempt with supercurio's kernel.

Just wondering if it's just me. This is my second Nexus S today. The first one had faulty softkeys. Now I'm not sure if it's kernel-related, or if I got another lemon.
[Nexus S Android Development] jroid:
you need to specify the directory to where your su file is, or if your're on a mac just:

./adb push (drag file into terminal window which auto generates the path) /system/app/
[Nexus S Android Development] mprziv:
phew, got it to go...finally have root.

Thanks for your help guys.
[Nexus S Android Development] jroid:
glad you got it :D feels good huh lol
[Nexus S Android Development] DKYang:
Just bumping up this method. :)

Anderdroid's method works fine also. Once you mount /system and flashed the superuser zip. Go to terminal/command prompt and enter the following commands (while still in clockworkmod recovery) to finish it:

adb shell

cd /system/bin

chmod 6775 su
[Nexus S Android Development] mprziv:
Sure does.

Has quadrant been crashing for anyone else during the 3d tests?

The 3d test with the planets is in black and white too...weird.
[Nexus S Android Development] GrandMstrBud:
Finally rooted, has anyone been able to get ROM manager to work? I can't download the recovery because it says something about my internet connection which of course I have.
[Nexus S Android Development] ikon8:
Koush said Rom Manager support is coming shortly.
[Nexus S Android Development] mazodude:
Rom manager support is out now

https://twitter.com/#!/clockworkmod/status/15538695239114752
[Nexus S Android Development] jroid:
doesn't crash on mine, but wasn't asking to do the report at the end. I was getting 1657 stock and I now get 2250 after the voodoo kernel. I will be flashing back to stock kernel to test if it's causing my audio to not play through my headset while connected
[Nexus S Android Development] jroid:
you can flash the recovery via fastboot. Just download koush's recovery.img and flash it directly without rom manager. His server is having issues apparently
[Nexus S Android Development] mazodude:
In a twitter update he said it was fixed

https://twitter.com/#!/clockworkmod/status/15547089282924544
[Nexus S Android Development] mprziv:
Are any of your 3d graphics tests appearing in black and white?
[Nexus S Android Development] johnxjets:
was missing the 1.0 driver
[Nexus S Android Development] AdamHart612:
Awesome. Am root like a tree. Thanks koush you rock for supporting this beast!
[Nexus S Android Development] miguelrodas:
Ok, I was finally able to unlock the bootloader but now I cannot flash the recovery image. I get "error: cannot load recovery-clockwork-herring.img"

The recovery image is supposed to be in the tools folder of the SDK where fastboot is, right? What am I doing wrong?
[Nexus S Android Development] jroid:
no. recovery img doesn't go in /tools it's what you're flashing
[Nexus S Android Development] Michael.B.:
Make sure that you cd (Change current directory) to the same directory as the img file and the fastboot file.
[Nexus S Android Development] liorry:
Great work! Now I only need to wait 4 days for my device :-)

One question though, is there a way to get root without unlocking the bootloader, like they managed to do with the N1?

Thanks!
[Nexus S Android Development] IConrad01:
Needs more nines.
[Nexus S Android Development] Z51:
I completely suck at this ADB ****

who an help me?

i cant get fastboot or adb to work

its driving me crazy!
[Nexus S Android Development] mazodude:
have you downloaded the android sdk?
[Nexus S Android Development] Z51:
yes i downloaded the sdk the drivers and everything

I cant get ADB to recognize anything....

im having trouble unlocking the damn bootloader...

do u have a messenger?
[Nexus S Android Development] ogdobber:
why? with the NS you can re-lock the bootloader just as easily as un-locking it
[Nexus S Android Development] Z51:
K i figured it out.

thanks!
[Nexus S Android Development] AdamHart612:
No one helped you yet you thank the forum lol.

If you need any help figuring crap out PM me.
[Nexus S Android Development] Lootes:
I have a question, I did the fastboot OEM unlock, pushed the recovery image and installed Superuser, however when I run an application like screenshot or AdFree that needs root but it says my device is not rooted. Any thoughts? Did I miss a step?
[Nexus S Android Development] chabsie:
I'm having the same problem!! Its driving me nuts... superuser is granting root permissions to titanium backup but it still says it cant access root. Other apps are running with root access without a problem
[Nexus S Android Development] kalagas:
Maybe you must wait for an update of Titanium Backup app... or maybe try uninstall and re-install Titanium Backup...

Maybe it's the app's itselfe problem and not a generic problem, as you say other apps and su command works properly...
[Nexus S Android Development] mazodude:
@chabsie and @ALuton have a look a couple of pages back (maybe 2nd page or 3rd)

and there is a solution

edit: here is your answer http://xdaforums.com/showpost.php?p=9869323&postcount=47
[Nexus S Android Development] Bamdroid:
Beer is on the way my friend...

It was good walking out of Best Buy, signing into my new X/S, then seeing you already rooted this *****!!
[Nexus S Android Development] lmerega:
Guys, warranty problems with this procedure?

Can you relock?

TIA :)
[Nexus S Android Development] distortedloop:
Not sure about warranty problems, but yes, you can relock with the "fastboot oem lock" command.

Warranty's dependent on jurisdiction: where I live (California), users are allowed to modify products without voiding warranty service responsibilities of the manufacturer as long as the mods didn't cause the issue.

Example. You root your phone, and then a week later the screen loses pixels. Root doesn't cause that, warranty still valid. YMMV!
[Nexus S Android Development] Mr.zeus:
wich one should i use? there isn't any file for android 2.3