• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root How to Root Nexus One on 2.3.4

See this thread, it has pretty good information though you should augment it with some research.

http://androidforums.com/nexus-all-...ndroid-2-3-3-seems-disable-superoneclick.html

At the very end of the thread, someone posts a new One Click method that purports to work, so you may want to try that first.

Always, always research. I don't do this stuff until I think I have a clear understanding of what to do and why. It doesn't matter if it turns out I'm wrong about something, if I have a framework, I can at least work back and figure out where my wrong assumption was.
 
Upvote 0
???? Lots of guys are running rooted stock 2.3.3 and 2.3.4. It's a Nexus - you don't need to use an exploit to achieve root, you just need to add a couple of files (su, busybox) to it.

Cool, nice to know I didn't know it 2.3.3 was rooted. Well it's not rootable with oneclick atleast there's that :D

As I know you can't just install crap if you don't have root, even on a nexus with it's ability to unlock the bootloader wich doesn't give you root.

But what do I know I run CyanogenMod since 2.1 came out.
 
Upvote 0
Cool, nice to know I didn't know it 2.3.3 was rooted. Well it's not rootable with oneclick atleast there's that

Sure, but since you can root a nexus by the simple expedient of unlocking the bootloader, flashing clockwork recovery, then flashing su.zip to the system folder there's really no need for something like oneclick except that it's three clicks instead of one. I've always been puzzled why such programs even exist for the nexus phones at all. The only thing I can think of is that they're probably what the exploit authors are using as development systems; finding the exploits that will be needed by non-nexus phones a year later when they finally get that version.
 
Upvote 0
Sure, but since you can root a nexus by the simple expedient of unlocking the bootloader, flashing clockwork recovery, then flashing su.zip to the system folder there's really no need for something like oneclick except that it's three clicks instead of one. I've always been puzzled why such programs even exist for the nexus phones at all. The only thing I can think of is that they're probably what the exploit authors are using as development systems; finding the exploits that will be needed by non-nexus phones a year later when they finally get that version.

Yeah you're right, everyone these days wants the phone rooted without being unlocked, I forgot about flashing CWM directly :D Dum Dum :D
 
Upvote 0
This method did not world for me, my drivers are up and running. But when i type fastboot devices nothing happens :(

You may want to try again. I am running 2.3.4 on my Nexus and these steps worked perfectly for me. Took a total of about 5 minutes to get rooted with these steps. "Fastboot devices" runs with no visible change, but the following fastboot command will push the recovery image.

Note: when in the Bootloader, you have to click "Bootloader", then click "Fastboot" in order for the fastboot command to run. They did not include that 2nd step in their instructions. Without going back, the fastboot command will just sit there waiting.
 
Upvote 0
You may want to try again. I am running 2.3.4 on my Nexus and these steps worked perfectly for me. Took a total of about 5 minutes to get rooted with these steps. "Fastboot devices" runs with no visible change, but the following fastboot command will push the recovery image.

Note: when in the Bootloader, you have to click "Bootloader", then click "Fastboot" in order for the fastboot command to run. They did not include that 2nd step in their instructions. Without going back, the fastboot command will just sit there waiting.

DO i need to have my bootloader unlocked in order to root?
 
Upvote 0
That looks like the easiest guide I've seen so far :) but yet it still manages to not work as smoothly as they make it seem.
Upon trying to run fastboot-oem unlock it returns the message "adbwinapi.dll is missing". A google search returned that that piece comes from having the Android SDK and AVD thing installed. Why does rooting seem like such the daunting task?
 
Upvote 0
What about my issue? Just got the SDK and AVD thing and it still gives me "adpwinapi.dll missing"
Not worried about whats on the phone, got all that backed up.

Are you invoking the fastboot command from the c:\fastboot folder or from the [path where you installed the SDK]\android-sdk-windows\tools folder? If you are using the c:\fastboot folder, the go to the tools folder of the SDK and copy the files "adb.exe", "AdbWinApi.dll" and "ddms.bat" to the fastboot folder. Then try it again.
 
Upvote 0
Thanks, how ever I'm booted on one of my three linux distros and trying it this way.
It gives me permission denied when doing "./fastboot-linux oem unlock" even when logged in as root.
Looks like I might have to go back to windows to give it a whirl with your tip.

You said you installed the Android SDK. Open a terminal window and change to the tools folder and try "./fastboot devices" to make sure the phone is listed. Then try "./fastboot oem unlock"
 
Upvote 0
How would I go about doing the devices command in Windows since that's where the SDK is installed, I don't see a "devices" in the tools folder just "fastboot" and it also gives me the adbwinapi.dll missing.
Maybe I should stick with Linux and keep looking into the permission denied? Has anyone here rooted their N1 in Linux?

This should be the contents of your tools folder in the SDK folders:

adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
android.bat
apkbuilder.bat
ddms.bat
dmtracedump.exe
draw9patch.bat
emulator.exe
emulator_NOTICE.txt
etc1tool.exe
fastboot.exe
hierarchyviewer.bat
hprof-conv.exe
layoutopt.bat
mksdcard.exe
monkeyrunner.bat
NOTICE.txt
source.properties
sqlite3.exe
traceview.bat
zipalign.exe

You'll notice that the files you are getting prompted are missing are listed.

There is no devices command it is an operator for fastboot. At the command line type:

Code:
c:\Users\jsmith\Desktop\android-sdk-windows\tools>[B]fastboot devices[/B]

You should see your device listed as a number.

That is assuming you installed the SDK to your desktop and that your username is "jsmith".
 
Upvote 0
Ok, I found and downloaded adbwinapi.dll from the intertoobs and put one each of it in my fasboot folder and sdk/tools folders. Now I can get a little farther, when typing in "fastboot-windows oem unlock" it returns "waiting for device". What am I supposed to do at that point? Is it a waiting game or should it quickly popup the warning on my phone?
 
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones