yashsingh1/xdaforums huggingface dataset:
[Nexus S General] kenvan19:
Hey distorted...I doubt you'll have an answer or that there even is an answer other than "use a different computer" but I seem to have gotten myself into a bind: I decided to make a backup of stock 2.3.2 (I never updated my stock image) so I used the nandroid on the forums here without thinking that it might not be rooted. Now my issue is that my mac has never been able to recognize my phone in ADB (on either windows or mac partitions) so I've always used someone else's but now I'm in the midst of a bit of a storm and can't get to another computer lol my bootloader is still unlocked and all of that but I can't get root back. Any ideas?

EDIT: So I was finally able to get into stock recovery (had to mash a lot of buttons before anything actually came up) and tried to just flash the superuser zip but no luck...I didn't really think it would work but I had hoped. Now I've uninstalled all of the windows sdk and I'm going to try to reinstall the drivers as I've read that sometimes that helps some people. Gaaaaah why did I decide to do this lol
[Nexus S General] distortedloop:
You don't need adb to root. You should be able to just boot to fastboot mode as described in the guide, then fastboot flash or fastboot boot the clockwork recovery - this assumes that fastboot can communicate with the phone even though you're having issues with adb talking to it. I'll take further conversation of this to the thread you started in the Q&A section.
[Nexus S General] stennett:
does this method work with the 2.3.3 update? I'm unsure as some people say it won't some people have been saying it might not?

If not is there a way to manually update to 2.3.3 and re-root with out having to unlock the bootloader?

thanks in advance!
[Nexus S General] AllGamer:
you can volunteer to be our live test subject :p

the only way to know for sure is to do it

just backup all your stuff then do it
[Nexus S General] stennett:
I'll get back in my corner, it was weeks before I bulit up the courage to root the damn thing! lol
[Nexus S General] fabio008:
it does not work anymore for me. I've just updated to 2.3.3 and you cannot "fastboot boot" as it says you can only do it with the unlocked bootloader, meaning you'll have to erase everything to unlock it

anybody else has alternatives?
[Nexus S General] hmanxx:
I manage to keep the root for 2.3.3 with the flashing sequence listed below.

From Android 2.3.2 /rooted/locked bootloader

1) Fastboot boot recovery.img..to boot into recovery CW recovery screen

2) Apply 2.3.3 update.zip ..

=>After applying update DO NOT REBOOT ,as this 2.3.3 has Bootloader change that disable fastboot boot for locked bootloader.

3) Without rebooting , mount system, apply su.zip

=> This step is to reapply Superuser.apk permission setting

4) Reboot..

For the details inter steps, you can refer to post #1
[Nexus S General] kenvan19:
Good call!
[Nexus S General] distortedloop:
Do me a favor. If you're still in the situation you mentioned above (locked bootloader and not rooted with 2.3.3 applied).

Follow the steps in the guide in the first post, BUT instead of

fastboot boot recovery.img

please try

fastboot flash recovery recovery.img

(replace recovery.img with the proper name of your clockwork recovery image file).

Then try booting into recovery from the fastboot menus on the phone. If you get into Clockwork, you're good to go.

I don't know if the fastboot flash will work on a 2.3.3 locked bootloader - we debated it a bit in a thread this morning, but I haven't had a chance to return to that to see if the debate had a conclusive answer.

Trying this won't put you in any worse a state than you already are and may help.
[Nexus S General] stennett:
Has anyone else tried hmanxx's way?

Also where do titanium backups store? under what folder name? As I may give the method a try!

Also will having a custom kernel affect anything?
[Nexus S General] Jonathon Grigg:
I would try but my bootloader is unlocked. I am available for anyone to help test rooting methods if they need someone. Currently running CM7 rc1 with netarchy but I can change back to 2.3.2 easily if needed.

Titanium stores its backups on your SD card in a folder called TitaniumBackup.

It appears that some kernels may be affected by the update, with some users reporting that Netarchy 1.2.4 isn't working with 2.3.3. Not sure about other kernels. Netarchy amongst others said that there has been some changes in the kernel for 2.3.3 (possibly NFC?) so most kernels will probably need to be updated.
[Nexus S General] Jonathon Grigg:
So you're on 2.3.2 currently? Can you please let us know what command you type in and the full result? I have a feeling you may need to rename it to update.zip but that's probably just for ease of use in the command line.
[Nexus S General] fabio008:
Yeah, I actually tried that too yesterday when I realized I had lost root, but it did not work either, it gives the same message that I need to unlock my bootloader.

I ended up unlocking it anyway, but I think the posts with the alternative of not booting after the 2.3.3 in CWM really works, too bad I had already rebooted once.
[Nexus S General] aviramsegal:
confirmed to work

booted to CWM

flashed the update

flashed su

now i'm on 2.3.3 with root, bootloader locked
[Nexus S General] distortedloop:
Another suggestion is to look for a full img file of the original bootloader.img. We could use Odin to push that bootloader back on the phone and remove the unlocking requirement.
[Nexus S General] kongkkm:
Can anyone give me a link to download recovery-clockwork-3005-crespo.img? Thank in advance...
[Nexus S General] Jonathon Grigg:
Sorry, ignore the update.zip part its not relevant. Have you checked the download against the checksum if given? Maybe try again with a new copy.

But after hearing reports with Netarchy I think it might be best to revert to stock kernel just to remove any possible extra issues. Kernels will probably need to be updated for 2.3.3
[Nexus S General] distortedloop:
Your problem is that you're using the Trinity kernel. The updater-script runs a checksum against the boot partition (aka the kernel) and if it doesn't match what Google expects, the update is failed.

Restore a stock 2.3.2 kernel and you should be okay if you've made no other mods to the /system/apps partition or boot images.
[Nexus S General] distortedloop:
removed duplicate
[Nexus S General] DumbUglyDragon:
No longer works with 2.3.3. Must have unlocked boot loader now :(
[Nexus S General] benrees21:
So how do I root with 2.3.3 on my phone?

Sent from my Nexus S using stock Android 2.3.3 and XDA App.
[Nexus S General] AtomicPC:
While I'm sure they are working on a no wipe version of this, the only way to do it now is to do the fastboot oem unlock. After that then you can root with this method. If you were lucky enough to root before and titanium back up then you at least have a way to get back to where you were before you had to wipe with oem unlock. That's what I did.
[Nexus S General] DumbUglyDragon:
Exactly.

Root>Titanium back up>Copy backups to PC>Update>Fastboot oem unlock>boot clockwork>Install Super User>Fast boot oem lock(if you care about seeing the little lock>Restore using Titanium back up.
[Nexus S General] distortedloop:
Yes, that's the situation I am in. Trinity modded several /system files and library files. I'm looking this morning for a 2.3.2 image with the unmodded files to push back with adb. I've got a pre-trinity nandroid of my phone I could restore to clean 2.3.2, but I've just been so busy to bother with it (or 2.3.3) yet.

Then I'm going to mod the OTA update to maintain root so that people flashing it won't lose root and won't have to bother with installing it from clockwork, though that's really trivial to do anyways, so I haven't been in a rush to get this done.
[Nexus S General] zmalach:
Root Nexus One 2.3.3 without unlock the Boatloader

Please can some one explain to us step by step how to root Nexus One with Gingerbread 2.3.3 installed?

I rooted my phone using Superoneclick 1.65 before before the the Gingerbread update and I was happt using the MIUI roms but I have unroot to install 2.3.3, I didn't like it and wanted to go back to MIUI again but Superoneclick doesn't work anymore...please help
[Nexus S General] distortedloop:
Wouldn't you be better off asking this in the Nexus ONE forums? This is the Nexus S forum...
[Nexus S General] zmalach:
Ok will post it in the Nexus One forum..Thanks :-)
[Nexus S General] kassemalaa:
Recovery question

hey, great guide, followed it and got my phone rooted in less than 5 minutes. Then i renamed the recovery.sh to recovery.sh.old and flashed clockwork recovery using rom manager. My question is, do i need to rename that .sh file each time i flash a new rom if i want to keep cwm recovery? thanks!
[Nexus S General] xfile087:
I'm on stock 2.3.1 and there is no install-recovery.sh file? I'm confused lol
[Nexus S General] distortedloop:
Shouldn't have to with most custom or modded ROMS. Any stock ROM might retain the file, though.

You looked in /etc? If I recall correctly it was added in the 2.3.1 OTA.
[Nexus S General] xfile087:
Yep I looked there and other places but nothing. The phone came with 2.3.1 as I only got it recently so it wasn't an OTA. I don't know if that's why? I would have thought have pre-installed or OTA update it should still be there?
[Nexus S General] FuzzyBunnyFeet:
Details please

Never mind. This is a Nexus S thread, not a Nexus One thread.
[Nexus S General] r00main:
Question

Hi,

This method work pretty well on my nexus S.

However I have a question, how do you create the valid su signed zip ?

I want to try to add another file, I will be happy to know how to create valid zip with my binary.

Thank you.
[Nexus S General] distortedloop:
There's a guide and template in one of the forums here. You should be able to ferret it out with a little Google searching.

I can't/won't go into details beyond describing the basic concept here. But what you do is add the file you want to install complete with proper path to the zip file (ie., in su zip he's got a folder with /system/app/superuser.apk and /system/bin/su in it), and then you edit the /META-INF/com/google/android/updater-script file to do what you want done with it.

It doesn't have to be signed to use with Clockwork, btw.
[Nexus S General] kenvan19:
Distortedloop, I'm sure by now you know I think you're very smart...I'm just confused as to why this got moved and stickied in general considering it no longer works lol...seems to me a mac guide would have made more sense =/
[Nexus S General] distortedloop:
Beats me.

Whoever moved it also changed the title...I'd edited it in the Dev section to indicate it only worked on 3.2.2 & below.

Thanks for the kind words, btw.
[Nexus S General] salomaocohen:
Hello all! Please, I have updated to 2.3.3, unrooted. Is there any chance of this method (root without unlocking) be available to 2.3.3 someday? I want to root, but not unlock bootloader.

Thanks for the info
[Nexus S General] AllGamer:
my bad, you're right, forgot 2.3.3 Google changed it to locked security so that is no longer possible
[Nexus S General] stennett:
how do I rename the recovery in order to get clockwork to stick? I've tried root explorer and long press then rename but its says it's a read only file?
[Nexus S General] kenvan19:
No it will not. They made it so you cannot execute the necessary commands.
[Nexus S General] distortedloop:
You get clockwork to stick by renaming the file /etc/install-recovery.sh to something else, then flashing clockwork again. That shell script file rewrites stock each time you boot, so renaming it stops it from doing that.
[Nexus S General] stennett:
what programme can I use to do this? I can find the file using Root explore, However it won't let me rename it as it's read only.

Edit: Just to confirm, I Updated to 2.3.3 via Clockwork Mod and installed Superuser before reboot and it worked. I'm running 2.3.3 rooted with a locked bootloader. (In case anyone cares? lol)
[Nexus S General] distortedloop:
In Root Explorer, you have to hit the button at that top that Mounts R/W to remount the /system partition as writable. THEN you can change the name with RE. ;)
[Nexus S General] Vandam500:
Just to verify. I just bought a NS and am on 2.3.1. Will this guide still work for it?
[Nexus S General] noj78:
Should work no problem :)
[Nexus S General] kenvan19:
It will work but if/when you update to 2.3.3 or higher you will have to unlock the bootloader to re-root.
[Nexus S General] distortedloop:
Correct, unless he uses a nandroid image to update!

Also, I believe that if you took the OTA file from Google and deleted the new bootloader from it, and the instruction in the updater-script file that actually flashes it, that you could update to 2.3.3 without locking the bootloader and worrying about.

Of course, the reason Google replaced the bootloader was because the original one represents a security hole on the phone. The wipe of the phone on an unlock was to prevent someone from nabbing your phone and flashing something to it that let them see your data (like say Clockwork recovery) without wiping that data; now if you lose your phone and someone can't crack the lockscreen, they won't be able to flash a custom recovery and get adb access to all your private data (unless of course you run around with the bootloader unlocked).
[Nexus S General] Vandam500:
I see. I definitely want to unlock the bootloader to avoid having issues with flashing certain files. So I'm guessing this will be the best way? http://xdaforums.com/showthread.php?t=895545
[Nexus S General] kenvan19:
If you're on a Win machine. If you're on a mac you can check the link in my sig.
[Nexus S General] Vandam500:
Yeah I'm a Windows guy :p, thanks again.
[Nexus S General] kenvan19:
Lol Ah I see. Well, I would be too but I prefer not having to fuss around with drivers. Thanks to distortedloop, I was able to get my mac root guide down to needing only 4 files to root and no SDK installing either. Its pretty quick :D
[Nexus S General] androidrox:
Unable to boot into recovery

Hi guys,

I followed this guide and rooted without unlock -> updated to 2.3.3 -> flashed Cyanogenmod 7 RC2 and it all went fine.

Then my phone crashed and when I rebooted it, it kept popping up with com.android process not functioning every second. I managed to stop it popping up by putting it in airplane mode. Now I would like to do a nandroid but I am unable to boot into recovery!

When I type fastboot boot recovery.img it says

"downloading 'boot.img' ...

OKAY [ 0.629s]

booting....

FAILED (remote: Bootloader Locked - Use "fastboot oem unlock" to Unlock)

finished. total time: 0.630s

Then if I try to fastboot flash recovery recovery.img it says

sending 'recovery' (3980 KB)...

OKAY [ 0.633s]

writing 'recovery'...

FAILED (remote: Bootloader Locked - Use "fastboot oem unlock" to Unlock)

finished. total time: 0.634s

I was like :eek: ! Any ideas on how to overcome this? Thanks in advance guys!

Best regards,

androidrox
[Nexus S General] distortedloop:
By upgrading to 2.3.3 you overwrote the bootloader image with Google's new one, which has had the security bug that allowed this method to work patched.

The only thing you can do now is fastboot oem unlock the phone. That will wipe EVERYTHING! But since you have a nandroid, you could restore it.

Do so at own risk, but you might also be able flash the older bootloader image (if you can find it) that lets you flash unsigned recovery images. That's risky business, though, not recommended.
[Nexus S General] fangorious:
I have an i9020, never unlocked or rooted, with 2.3.3. I'm interested in CM 7 but would like to have a full backup of my app data first. As I understand the current state of affairs I'm SOL. Either lose my data or stay with locked stock. Is there something I've missed somewhere that would let me get a full backup?
[Nexus S General] distortedloop:
Do so at own risk, but you might be able flash the older bootloader image (if you can find it) that lets you flash unsigned recovery images. That's risky business, though, not recommended.

Once on the old bootloader, you can flash clockwork without wiping the phone.

I don't recall which thread, but I remember someone posting the old bootloader around here a while back.
[Nexus S General] jitzbox:
I am new to android and was reluctant to root, since it wipes off all the data. With your guide i have already gained super user access and doing a full clockwork backup, will first upgrade to 233 and then try Titanium backup.

One question, is Nandroid backup, same as "Backup" option in "Backup and Restore"?
[Nexus S General] distortedloop:
Yes, in Clockwork, the Backup option is commonly called a "nandroid" backup.

Sounds like you're on the right path.

I would do a Titanium backup BEFORE upgrading to 2.3.3. Then restore just apps with data after you wipe and upgrade.
[Nexus S General] jitzbox:
Thanks for correcting that. Have my backup, both Titanium and Nandroid. Time to upgrade, i presume i will have to completely wipe everything and do a complete 233 install and not incremental upgrade after 232.

Would be great if you can add this to your guide.
[Nexus S General] jitzbox:
Ok... just used the wipe and factory reset option in clockwork recovery... and back to stock 232. Will upgrade now..
[Nexus S General] distortedloop:
If you're really completely stock 2.3.2, the incremental upgrade will work; but since you're going to end up having to wipe the phone to unlock the bootloader once you go to 2.3.3, you might as well use the full upgrade file and be worry free about any of the patches not working correctly.

re: updating the guide, not sure what you wanted added... This guide's still relevant for some it seems, but with the new bootloader not many people will be able to follow it.
[Nexus S General] jitzbox:
Messed up with some files and it didn't allowed incremental upgrade, so used full to move to 233.

Since i started with this thread itself, was looking at some basics, but nevermid found those details on 233 update link.
[Nexus S General] androidrox:
Heyo distortedloop,

Sorry for the late reply. Did not receive any notifications by email. It seems I got into recovery by using an older version (3.0.0.0) and solved the problem. So I am now back at 2.3.2. Do you recommend me unlocking the bootloader before continuing on to upgrade to 2.3.3? Or is there another way to remain locked?

If I unlock the bootloader then upgrade to 2.3.3 will I still be able to go into recovery?

Thanks for everything. The locked bootloader was really cool while it lasted! Good job.

Best regards,

rox
[Nexus S General] distortedloop:
If I were on 2.3.2 right now, I would root/install CWM via the method in the OP. Then run a titanium backup of all my apps and app data, and then make nandroid of the system. If you already have all of that, there's no benefit to unlocking the bootloader before going to 2.3.3, because the 2.3.3 update will lock the bootloader. At that point you have wipe the phone to get root anyways, so that's where the titanium backup comes in; makes it a bit less painful.

Don't forget, the wipe from unlocking 2.3.3 bootloader will wipe your sdcard (music and camera pics, etc) too, so back them up!
[Nexus S General] androidrox:
Thanks again dude.

I think I saw you asking around on methods to avoid the locked bootloader in 2.3.3 somewhere else, any luck with that?

It's a shame that they decided to implement this in the latest update, I would rather have my bootloader remain locked for warranty purposes. Is it still possible to unlock and relock it with this new update?

I think I can get away with using the older CWM on 2.3.3 for the moment. Haven't given up on this root method yet!
[Nexus S General] glmrckr:
I don't mean to sound rude but if this method doesn't work for the current version of Android why is it stickied in general? I'm a mac user and I had to search through the development section to find a guide for the most recent update. Why do us mac users not get any love? :(
[Nexus S General] jspookss:
Because it still works for those of us who dont want to jump to 2.3.3 yet.

Also Macs.. Nah.. not gonna start a flame war or anything..
[Nexus S General] distortedloop:
Yes, you can still re-lock as far as I know. The only change is that the security hole that allowed the method in this thread to work in the first place was patched. That hole was that you could flash a custom recovery without unlocking the bootloader; now you can't once you go to 2.3.3 if you let it update the bootloader. You're phone's more secure this way, just less convenient to root.
[Nexus S General] jspookss:
So if you flash the 2.3.3 update and then flash the su.zip to gain root before you reboot, can you use the clockwork app to flash the recovery from the market?
[Nexus S General] Fitchman:
Gingerbreak works!

I just installed Gingerbreak on a completely stock Nexus S using these instructions on rootwiki.com

http://rootzwiki.com/wiki/index.php/Gingerbreak

Worked great on my 2.3.3, no need to unlock bootloader, no need to do a fastboot oem unlock.

I installed it by using a direct download to my phone, ran it.

It took about 15 minutes and I even thought I screwed it up because the phone went to sleep and I relaunched the app and it didn't have the "wait" dialog. However, after a bit of time, it just rebooted, and came back with SuperUser installed and it works great.

I'm ecstatic, I think the next step is just to get ROM Manager, get a custom recovery, and get modding.

However, I don't know yet if I can really install a custom recovery yet. Backing up my data first.
[Nexus S General] Fitchman:
Yup, got CM7 installed without OEM Unlock on 2.3.3

Gingerbreak

reboot

install ROM Manager from Market

Run ROM Manager

in Settings for ROM Manager, choose Erase Recovery

Flash ClockworkMod Recovery

Reboot into Recovery to make sure it worked

Reboot from Recovery

go back to ROM Manager, flash an OLD ClockworkMod Recovery (at the bottom), then the new one AGAIN (because I didn't do this and it rebooted into stock recovery, but booted back to Android and re-flashed Recovery)

Download ROM → CyanogenMod → Latest CM + Google apps

Backup, as well as wipe

Enjoy CM7!
[Nexus S General] benrees21:
Nice work. ;-)

Sent from my Nexus S running NSCollab, Cyanbread Theme and OC'd to 1.2ghz (I'm not that brave lol)
[Nexus S General] fishmong3r:
Hi Guys!

I`m unable to start clockwork.

`C:\cs\android\NexusS>fastboot boot recovery-clockwork-3.0.0.5-crespo.img

downloading 'boot.img'... OKAY [ 0.631s]

booting... FAILED (remote: Bootloader Locked - Use "fastboot oem unlock" to Unlock)

finished. total time: 0.633s`

Obviously I don`t want an OEM unlock, this is all about.

I have 2.3.4. Do you have any idea how to solve this?

Thanks in advance.
[Nexus S General] androidrox:
Use an older clockwork... mine worked with 3.0.0.0... download it from rom manager and you should be able to go into recovery... hope this helps
[Nexus S General] Dunhamzzz:
Anyone worked out a way to root 2.3.4 ?
[Nexus S General] fishmong3r:
Finally I decided to unlock bootloader as it turned out that locking back is very easy.

So I've used this guide

http://xdaforums.com/showthread.php?t=1007782

Locking bootloader again, so no warranty issues with almost the same command....

unlock -> fastboot oem unlock

lock -> fastboot oem lock
[Nexus S General] briggs1337:
Worked very well thanks !
[Nexus S General] air2345:
i try to following this step and using recovery-clockwork-3.0.2.4-crespo.img

but i came with error like this

C:\Program Files\android\tools>fastboot boot recovery.img

downloading 'boot.img'...

OKAY [ 0.501s]

booting...

FAILED (remote: Bootloader Locked - Use "fastboot oem unlock" to Unlock)

finished. total time: 0.505s

what should i do?
[Nexus S General] steviee7:
will something like this work with the newest 2.3.5? i want to root but i dont want to lose all my apps and data
[Nexus S General] VillainousVivi:
I had the same error with mine. I'm trying to boot to the recovery image without having to lose my data so I can make a full backup first. I'm using a stock Nexus S from AT&T that I purchased this weekend, trying to avoid losing data at first, if possible.
[Nexus S General] churro7:
does gingerbreak work on 2.3.5