yashsingh1/xdaforums huggingface dataset:
[Nexus One Q&A, Help & Troubleshooting] flibbertigibbet007:
With my OTA update failing, due to deleted apps I believe, I decided to manually update. Didn't realize theres no rooting yet (without unlocking the boot loader). Although I'm almost at the point of saying screw it to unlocking, and just do it.

The question at hand is, is anyone working on a way to do it? (more of a question to have people actually come out and say, here I am.)

Secondly, these one click apps to do the rooting without knowledge of adb is irritating only because you guys make these apps for windows only. Is anyone thinking of the few that run linux? ;-) Even if it's just a script.

I know how to use adb, and the shell, it just bugs me to have to do it for rooting. Because I don't like being forced to find a machine to get windows on, etc... I'm just airing my suggestion, don't forget about the little people.
[Nexus One Q&A, Help & Troubleshooting] danger-rat:
You can passimg to an earlier version of android, root and install a rooted version of 2.3.3...
[Nexus One Q&A, Help & Troubleshooting] flibbertigibbet007:
Wouldn't I still need to have the boot loader unlocked for this? For a custom recovery?
[Nexus One Q&A, Help & Troubleshooting] danger-rat:
Nope!

passimg to an earlier version, which can be rooted without unlocking the bootloader. Once rooted you can install a custom recovery, and use that recovery to install a rooted version of 2.3.3...
[Nexus One Q&A, Help & Troubleshooting] flibbertigibbet007:
Any instructions somewhere? I know I should probably search. :-D
[Nexus One Q&A, Help & Troubleshooting] danger-rat:
The wiki on this site for how downgrade - unroot/restore, use the passimg method with FRG33.

Root with this method:

http://www.nexusoneforum.net/forum/...mple-sdk-setup-manual-root-guide-windows.html

This will wipe your date, so backup first (MyBackup)...
[Nexus One Q&A, Help & Troubleshooting] flibbertigibbet007:
Oh wiping. Yeah that's already a negative. Ill wait. I was debating a factory reset before upgrading to gb. And the magic 8 ball said all signs point to no.
[Nexus One Q&A, Help & Troubleshooting] danger-rat:
It's really not that bad if you backup...
[Nexus One Q&A, Help & Troubleshooting] dnlsmy:
What's there to really back up if your stock? MyBackup for apps+data, Google Sync for contacts, or use a Contacts to sdcard app to back them up. All downloads should be on the SDcard already anyway, and wallpapers stay even after wipe...
[Nexus One Q&A, Help & Troubleshooting] flibbertigibbet007:
Honestly? Text messages. I can't find a good enough app that backs up all my texts to a text file per contact. Not just one big backup file.
[Nexus One Q&A, Help & Troubleshooting] peterocc:
SMS Backup on the Marketplace. (Free) You can scheduled and it stores it into an XML on your SD.
[Nexus One Q&A, Help & Troubleshooting] krad1992:
How to get root back after flashing official Gingerbread

Hey guys I updated my nexus one to official gingerbread update. Now I'm wondering how can I root my N1 with su.zip, I have done some research but I got no luck.

Do any of you guys can guide me on how can I get my root back?

Thanks
[Nexus One Q&A, Help & Troubleshooting] flibbertigibbet007:
I have discovered mybackup pro. For 5 bucks. Plus I can review the stuff online. So I may look into the rooted gb.. but I'm still on the edge of doing it. Debating on deleting my root apps tomorrow.
[Nexus One Q&A, Help & Troubleshooting] adunski:
You'll have to load a custom recovery first. Then you can find and flash an su.zip to give you superuser privileges. Mount /system before you flash the su.zip. I've seen it floating around on other threads.

My boot screen locked up at one point. I was able to flash the OTA update again to get it back with all of my settings saved.
[Nexus One Q&A, Help & Troubleshooting] isvaffel1200:
How to

Well here you have the method i used:

fastboot oem unlock

then i flashed a custom recovery(via fastboot), and flashed a rooted gingerbread ROM... (via custom recovery)

Simple!
[Nexus One Q&A, Help & Troubleshooting] GldRush98:
This is the proper way, and I believe only way right now.
[Nexus One Q&A, Help & Troubleshooting] derfo:
I concur.

10 char
[Nexus One Q&A, Help & Troubleshooting] danger-rat:
The alternative approach is to passimg back to an older version, root, and then install a pre-rooted version (if you don't want to unlock the bootloader)...
[Nexus One Q&A, Help & Troubleshooting] MitchRapp:
well, can't wait for GingerBreak. I'm all for the 1-click approach :)
[Nexus One Q&A, Help & Troubleshooting] pIxiLatEd:
You guys need to stop relying on one-clicks and just grow a pair.

My phone was unlocked and rooted, but I had to send it off to HTC for repairs due to a cracked digitizer - $55 and 3 days later (yes, only three days), I got my phone back with the bootloader still unlocked but they flashed it with a non-rooted Froyo.

Once I fired it up, I immediately was prompted for the OTA update to Gingerbread. I installed it and in one easy step, I got Gingerbread, the new radio, and the new hboot.

I then downloaded the FRG83-nexusone-superboot.zip, extracted it to my HD, rebooted the phone while holding the trackball and then plugged it into the usb port. Double clicked the .bat file and now have root. When the phone rebooted, it hung on the static X screen. I let it sit for a while and then I just pulled the battery, unplugged the device from the PC and fired it back up.

I am now running a rooted OTA Gingerbread on my Nexus. Simple.

You can follow these instructions. If you already have the bootloader unlocked, than you can just skip to step2.

http://mindmirror007.blogspot.com/2011/01/guide-install-gingerbread-on-your-nexus.html
[Nexus One Q&A, Help & Troubleshooting] pIxiLatEd:
I am going to add that at this point you should vet a recovery installed and then move to an actual rooted rom. For simplicities sake, go get ROM manager.
[Nexus One Q&A, Help & Troubleshooting] user024:
Now, if you do not want to use superboot and change your custom recovery, but you have already unlocked the bootloader before, you can run e.g. amon-RA' s recovery without flashing it, just by renaming the amon-RA image file to recovery.img

and typing through the terminal:

fastboot boot recovery.img

when in fastboot (part 3 of the guide above)

In my case, I then took a nandroid backup of my stock rom and recovery and another one without the stock recovery (I like back ups... :P), and then flashed the su.zip from the SD card.

(Oh I forgot to take a backup again :P)

I now have root with stock rom and stock recovery (so I can flash another recovery if I want to) and can use my root pre-requesting applications.

I wouldn't be certain that it works in every case, be cautious, but I can not think of a reason that it could cause a trouble.

I repeat, I had already an unlocked bootloader and my root and custom recovery was lost after the OTA flashing, without running the su.zip when I should.

I hope that could help someone.

I would love to have known about that some days before.

:)
[Nexus One Q&A, Help & Troubleshooting] smoovebert:
thank you for putting it so plainly/quickly. helped me out a lot.
[Nexus One Q&A, Help & Troubleshooting] ͘Jan:
So gingerbreak isn't coming out any time soon?
[Nexus One Q&A, Help & Troubleshooting] danwerneck:
My bootloader is unlocked and i'm running GRI40 Stock.

I want root my N1 and I was follow this steps on wiki:

1. Download Amon_RA's Recovery from one of the versions above.

2. Rename Amon_Ra's Recovery Image to simply recovery.img.

3. Download this file - Stock Recovery Remover - and copy it to the root of SD card.

4. Toggle on USB Debugging (Settings » Applications » Development). Power off the Nexus One.

5. Boot into bootloader mode. (Hold volume down & power button until you see white screen with skateboarding androids)

6. Connect the Nexus One to the computer.

7. On the computer... Open a command prompt/terminal & navigate to the Android SDK Tools folder.

8. Type in the following commands:

fastboot flash recovery recovery.img

fastboot reboot recovery

But, the CMD show me: error: Cannot load 'recovery.img'

I renamed the file name correctly to recovery.img (not recovery.img.img)

I'm navigating to android SDK tools correctly:

cd\program files\android-sdk-windows\tools

Anyone know where am i wrong?
[Nexus One Q&A, Help & Troubleshooting] danger-rat:
Have you tried typing "fastboot devices" to confirm that your phone is connected?
[Nexus One Q&A, Help & Troubleshooting] danwerneck:
Yes Yes ...
[Nexus One Q&A, Help & Troubleshooting] danger-rat:
Then your recovery image may be corrupt. Have you done an MD5 check?
[Nexus One Q&A, Help & Troubleshooting] danwerneck:
No .. How Can I do this?
[Nexus One Q&A, Help & Troubleshooting] danger-rat:
Are you getting the error after "fastboot flash recovery..." or "fastboot boy recovery"?
[Nexus One Q&A, Help & Troubleshooting] danwerneck:
After the first command: fastboot flash recovery recovery.img
[Nexus One Q&A, Help & Troubleshooting] danger-rat:
You'll need a program that can calculate MD5 values for files (either on your pc, or on your phone). Compare the value the program gives you with the value listed where you downloaded the file from. If they are the same, the file is good, if they are different, the file is corrupt...
[Nexus One Q&A, Help & Troubleshooting] danwerneck:
I'll googling about this program and i'll try install a amon_ra recovery again. thanks!
[Nexus One Q&A, Help & Troubleshooting] efrant:
Did you put the recovery.img file in the \program files\android-sdk-windows\tools directory?
[Nexus One Q&A, Help & Troubleshooting] danwerneck:
Thanks, man! This was the problem .. I was putting recovery.img on \program files\android-sdk-windows
[Nexus One Q&A, Help & Troubleshooting] ͘Jan:
I was waiting until gingerbreak comes out, I thought the dev just waited until more devices had gingerbread on it. We already upgraded my brother's N1 to Gingerbread, but I'm keeping mine on Froyo until the Gingerbreak that roots the phone without unlocking bootloader or messing around with custom roms comes out.
[Nexus One Q&A, Help & Troubleshooting] efrant:
Why are you waiting? If you are rooted on froyo, you can go to rooted. Stock gingerbread with a locked bootloader.
[Nexus One Q&A, Help & Troubleshooting] ͘Jan:
I thought it involved custom recoveries and roms, that might erase some data, text messages, application setting/accountdata . After updating the other N1 through OTA the su command lost it's 4755 permission(sticky bit?), so can you link to the post to upgrade a rooted froyo to upgrade while keeping the permission or at least the filesystem to read/write with root? Anyone has an idea how gingerbreak is supposed to work?
[Nexus One Q&A, Help & Troubleshooting] efrant:
I can't link to any post, but I can tell you how to do it. You do, however, need to flash a custom recovery (not ROM), but it is only temporary, it will get automatically flashed back to stock when you do the update. I will give you the general steps, and if you need more details, just ask.

1. Flash a custom recovery using flash_image. Use Amon_RA v1.9.0 (which can be found in my signature), as it has signature verification set to off by default.

2. Download the proper Gingerbread update (for the version of Froyo you have installed) from Google's server to the root of your sdcard. There are links everywhere.

3. Download ChainsDD's Superuser zip (also found in my signature) to the root of your sdcard. (Use the Eclair-Froyo version.)

4. Reboot into recovery.

5. Select the flash update from zip, or whatever the menu is called.

6. Select the Gingerbread update file and flash.

7. Now, VERY VERY IMPORTANT, DO NOT reboot.

8. Re-read step #7. I am repeating this, because if you reboot before you flash the next file, you lose root, and you are stuck. Nio way to get root unless you unlock the bootloader or wait for gingerbreak...

9. Select ChainsDD's file and flash that.

10. Now reboot into your ROM, and presto, stock Gingerbread ROM, rooted, with all you data still there, and stock recovery is back, and your bootloader is still locked.

EDIT: If you want to retain your custom recovery, just flash this between steps 9 and 10.
[Nexus One Q&A, Help & Troubleshooting] ͘Jan:
Thanks, that worked. Almost thought it was rebooting by itself. So now I have a rooted gingerbread, although now my OTA update still sits there in the taskbar.

I had to download and push flash_image because my Froyo didn't had it. I think that fastboot flash might have worked too.
[Nexus One Q&A, Help & Troubleshooting] efrant:
Not sure why your OTA notification is still in the taskbar. Maybe try checking-in to see if it goes away. Go to your dialer and dial *#*#2432546#*#* and once it connects, go to settings->about phone->system updates. If that doesn't work, I'll search around, as I'm sure there is a way to get rid of it.

As for your second point, fastboot flash would not have worked, as you need an unlocked bootloader for that command to work. The only way to flash a recovery with a locked bootloader is with flash_image (which is not included with a stock Android ROM, so you have to download it).
[Nexus One Q&A, Help & Troubleshooting] Majesty00:
Hi efrant,

I just read your post and I wanted to know if your method wipes the data?

See, I already have Gingerbread on my Nexus One. I thought of downgrading to Froyo, root it, and then update with an already rooted Gingerbread's image.

Would your method work for me?

Thanks!

Edit: Just re-read your post and I **need** to downgrade to Froyo, which will wipe my data. Without root, I can't backup with Titanium. So, I guess I'll have to wait for Gingerbreak. :-/
[Nexus One Q&A, Help & Troubleshooting] danger-rat:
Downgrading to Froyo will wipe your data, but you can backup quite a lot with MyBackup...
[Nexus One Q&A, Help & Troubleshooting] efrant:
Not sure exactly what you are asking/trying to do? What I had posted was a way to upgrade to rooted STOCK Gingerbread from rooted STOCK Froyo with a LOCKED bootloader, while not losing any data. If you downgrade to Froyo, or flash a Gingerbread ROM, you will lose all your data (unless you backed it up previously of course).
[Nexus One Q&A, Help & Troubleshooting] brettbellaire:
If I wasn't so hasty to update the minute I saw the file, this would have been a really easy way to stay rooted without losing anything. Thanks for the info anyway, right now I'm waiting for a oneclick I guess....:(
[Nexus One Q&A, Help & Troubleshooting] danger-rat:
Passimg back to an older version and root...
[Nexus One Q&A, Help & Troubleshooting] brettbellaire:
Yeah I know, but then you lose data right? And I can't really do a full Titanium backup because it needs root access (I think...).

Next week I will have some time and I might give it a shot anyway.
[Nexus One Q&A, Help & Troubleshooting] danger-rat:
You can back up a lot with MyBackup...
[Nexus One Q&A, Help & Troubleshooting] brettbellaire:
Yeah, like I said, I might give it a try next week when I have more time to screw things up and fix them.

Thanks
[Nexus One Q&A, Help & Troubleshooting] ͘Jan:
Well, the OTA got away after a while, and now system updates shows up to date. I wonder that when a minor OTA update comes out, it might change the permissions of su(just like the update to froyo did). So we may have to repeat the same thing then.

I backed up my recovery image with dd(you probably need root for that), but they say you can't create a usable system image with it. I tried to use romdump but that gave a segmentation fault.
[Nexus One Q&A, Help & Troubleshooting] efrant:
Yes, every time you flash an OTA update, it will reset the permission on su, and you will lose root access.

There is no need to keep a stock recovery. Just flash Amon_RA 1.9 again using the same method. Then you can backup your entire ROM using the recovery.
[Nexus One Q&A, Help & Troubleshooting] ͘Jan:
You mean Amon_RA doesn't stay as recovery image permanently after it is flashed to the recovery partition?
[Nexus One Q&A, Help & Troubleshooting] Jack_R1:
Yes it does, until it's overwritten (for example, by stock recovery installed by OTA updates).
[Nexus One Q&A, Help & Troubleshooting] efrant:
Once you flash an OTA update, it re-flashes the stock recovery automatically. What you need to do is delete two files: /system/recovery-from-boot.p and /system/etc/install-recovery.sh (those two files are responsible for re-flashing the stock recovery on every boot) and then re-flash Amon_RA
[Nexus One Q&A, Help & Troubleshooting] danger-rat:
You can flash this from recovery to delete the two files, also...

http://db.tt/cp7De8G
[Nexus One Q&A, Help & Troubleshooting] hmanxx:
I am on stock 2.3.3 with my nexus one , can I run rom manager to reboot in custom recovery then mount system and apply su.zip.?

I manage to root on another nexus S which was on 2.3.2 prior to manual update. I boot into cwm recovery apply manual update of 2.3.3 then without rebooting, mount system then applying su.zip

The step above work ..
[Nexus One Q&A, Help & Troubleshooting] efrant:
How are you going to run ROM Manager (to flash a custom recovery) without root?
[Nexus One Q&A, Help & Troubleshooting] skearon:
Thank you, appeared to work, however upon reboot no root (according to titantium backup)

Phone was running custom rom and then back to stock and received 2.3.3 over the air, bootloader is unlocked

EDIT: Was wrong, forgot to install Busybox! Again thanks for your original post
[Nexus One Q&A, Help & Troubleshooting] danger-rat:
Did you do step 8?

What results did it show?

You can also test root by typing "su" into the terminal emulator (the $ should change to #)...
[Nexus One Q&A, Help & Troubleshooting] k45p3r:
root the nexus one,android 2.3

just got the N1 and installed gingerbread update.I would like to root this phone but too much old info on how to do it,what is the easier way as i am not great with command lines and Linux.looking for good tutorials,video or just links. i read about gingerbreak but until then do i wate
[Nexus One Q&A, Help & Troubleshooting] addam360:
Thanks I flashed an unrooted 2.3.3 rom but still have custom recovery so this should work for me if it did for you.
[Nexus One Q&A, Help & Troubleshooting] anangphatak:
Used to have root and recovery, gingerbread took it away

I used to have both root and recovery. After gingerbread update, root is gone. The phone cannot boot into CWM recovery. It just goes into a screen with triangle and exclaimation mark with an android digging something (like a grave?)
[Nexus One Q&A, Help & Troubleshooting] rjmohit:
had the same problem, superoneclick 1.9.1 worked for me. try googling it.
[Nexus One Q&A, Help & Troubleshooting] efrant:
That's because EVERY OTA update disables root access and reflashes the stock recovery (which is the triangle and exclaimation mark)...

SuperOneClick does not work for 2.3.4. There is no way to get root on 2.3.4 without unlocking your bootloader, or downgrading the ROM. Both methods will wipe your device...
[Nexus S General] kenvan19:
Mods any chance we can get this stickied to replace the old one? There seems to be some confusion about using the old version to root.
[Nexus S General] jlevy73:
Nicely done.
[Nexus S General] J__:
any guides to root 2.3.3 for windows?
[Nexus S General] kenvan19:
Honestly, its a very similar process. Just download a different version of the SDK and make sure you put the recovery image in the folder of the installed SDK called tools. Then when you get to executing the commands do this:

cd *remove the asterisks and type the file path to the directory for the tools folder of your SDK folder in program files*

Then remove the

desktop/adb-fastboot/

and just type the other parts.
[Nexus S General] kenvan19:
You think its enough of a difference to switch this with the other stickied thread on rooting for a mac jlevy?
[Nexus S General] owlmatt:
im getting this error message "cannot load 'recovery-clockwork-3.0.0.5-crespo.img'"

so stuck on step 6. any advice?

thanks

Also, curious because now I have an unlocked bootloader but nothing else has been done. This shouldn't be an issue I assume.....
[Nexus S General] kenvan19:
I've never heard of someone having that issue. Try the command fastboot flash recovery recovery-clockwork-3.0.0.5-crespo.img

Sent from my MattedBlues CM7 Google Nexus S!
[Nexus S General] jlevy73:
I don't think it's enough but it would make a great add-on to the original rooting for mac thread.
[Nexus S General] owlmatt:
-bash: fastboot: command not found

Is what it staid after trying that. Not sure what I am doing wrong. Have rooted several phones before.
[Nexus S General] kenvan19:
Did you install the android SDK? I'm a little lost, I'm not sure what could be going wrong...I used this method to root both my and my wife's phones with no issues.
[Nexus S General] owlmatt:
This could be the place I screwed up. I've never used the SDK on a mac and don't have a pc. I downloaded the files, used eclipse and loaded up everything it asked me to do.

I will look around for others guides on this maybe.

Maybe I need to learn more about android SDK, but I tried to follow all the instructions. One thing that was a problem was using the newest version of eclipse. It wouldn't install any add ons so I went to the older 3.4 version.

I would go to help, install new software, click on development tools, sign the terms then always get an error loading the software. This step does work on version 3.4. I guess I'm a real new noob at SDK.
[Nexus S General] kenvan19:
Oh no! I see where I screwed up in my guide...I'm sorry I see it clearly now...don't know how I missed it before.

instead of

~/Desktop/androidsdk/tools/fastboot boot recovery-clockwork-3.0.0.5-crespo.img

type

~/Desktop/adb-fastboot/fastboot boot recovery-clockwork-3.0.0.5-crespo.img
[Nexus S General] owlmatt:
Still the same result for me. Sucks. I had moved the recovery image into the SDK to match you code, previously as I i've been trying everything I know.
[Nexus S General] kenvan19:
Okay I have one last idea...I'll grab the link then edit this with the stuff...brb

Download this SDK http://www.box.net/shared/ljhg8t5sjh it should have everything including an older version of CWM which should still work (again unzip it to your desktop) and try using this command:

~/Desktop/androidsdk/tools/fastboot flash recovery ~/Desktop/androidsdk/tools/recovery-clockwork-3.0.0.0-crespo.img

If it works you can flash the newest version of CWM through rom manager later.
[Nexus S General] owlmatt:
I AM ROOTED!!! How do I buy you a beer?
[Nexus S General] kenvan19:
Haha don't worry about it man! Just glad you're rooted now ;)
[Nexus S General] owlmatt:
Happy to if you change your mind. Just post your paypal. Otherwise Thanks again. I hit thanks on the site as well a bunch of times.

Time to start flashing and overclocking.
[Nexus S General] kenvan19:
If you really want to do something, I'd suggest buying the XDA Premium app from the market and help support XDA as a whole. :)
[Nexus S General] owlmatt:
Consider it done.
[Nexus S General] kenvan19:
Also, if you want some information on Roms, themes, and kernels you can check out my guide to that here. Its a little daunting to look at but its a complete list of everything you can flash on your Nexus S hehe
[Nexus S General] kenvan19:
I changed one of the commands used in the guide from

fastboot boot

to

fastboot flash recovery

While the fastboot boot command worked perfectly for me and my wife, I've seen a few people who have issues with it and in both cases having them use the fastboot flash recovery seems to fix it entirely, so I've made the change.
[Nexus S General] carlost24:
This is a very well detailed guide I was wondering if it works for 2.3.2 ive been waiting to get the 2.3.3 update so I can use this guide to root but the update taking taking longer than I would like so that's why I ask if it works with 2.3.2
[Nexus S General] kaimyn:
Yes
[Nexus S General] rscaramelo:
What if I'm getting "error: device not found"? I have updated the SDK. I am thoroughly frustated. Tried on pc and mac.
[Nexus S General] mustafa_000000:
I couldn't find Mount R/W in the etc. folder,

any help ?