elidoperezmd

Hi all, i uodated manually to 2.3.4 and want to root but cant find a guide, how can i do this?

Thanks for your help, and time!

mkrmec

2.3.3 cannot be rooted on Nexus, why do you think 2.3.4 can

If it's rooted somebody will post the exploit. Untill now it hasn't happened yet.

mparker762

???? 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.

Hook

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

Gingerbread (Android 2.3.3) seems to disable SuperOneClick

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.

mkrmec

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

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.

sun428

This method works for both 2.3.3 and 2.3.4.

Root Nexus One with Android 2.3.3 Gingerbread

elidoperezmd

Wow... i did not expect this many replies, ill get to it right now and post my experience rooting afterwards, thanks very much

mparker762

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.

Last edited by mparker762; May 5th, 2011 at 07:42 PM.

mkrmec

Yeah you're right, everyone these days wants the phone rooted without being unlocked, I forgot about flashing CWM directly Dum Dum

Kabulldust

Just use GingerBreak 1.2 roots 2.3.3 very simply.

elidoperezmd

GingerBreak 1.2 did not work to root 2.3.4. Ill try the other options above and will report

elidoperezmd

This method did not world for me, my drivers are up and running. But when i type fastboot devices nothing happens

Shanton01

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.

Last edited by Shanton01; May 9th, 2011 at 08:21 PM. Reason: typo

elidoperezmd

DO i need to have my bootloader unlocked in order to root?

weirdoooxp

I followed this guide when I unlocked/rooted my N1: [Complete guide with Images] Unlock Bootloader and Root Google Nexus One [Mac, Windows, Linux] | iLikeMyGooglePhone. Hopefully it can be of some help to you.

N1nja

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?

lunatic59

Yep. And unlocking the bootloader will wipe all data from your phone.

__________________
_
If the information is useful, Like the post, if the person was helpful, Thank the member.
RULES: Lest we forget | This part of signature intentionally left blank.
______________________________________________

Support Breast Cancer Research: BabyBlues Breast Cancer Pledge

N1nja

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.

lunatic59

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.

N1nja

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.

Last edited by N1nja; June 15th, 2011 at 10:42 PM.

lunatic59

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"

N1nja

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?

lunatic59

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

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:

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".

N1nja

"fastboot devices" returns the adbwinapi.dll is missing.
Thanks for all the help thus far. Normally I can figure stuff out fairly easy but for some reason when it comes to tinkering with this phone it just gets me.

N1nja

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?

lunatic59

You must put your phone into fastboot mode by turning it off, then hold down the track ball and press the power button. I don't know if it makes a difference if the phone is plugged in to the USB cable prior to entering fastboot mode or if yu plug it in after. I don't think it does.

Before you type the unlock command, type "fastboot devices" and make sure the phone is recognized by your PC.

N1nja

I had it in fastboot mode and tried plugging it in before and after with the same result of waiting for device. Fastboot -s devices also just returns waiting for device, I let it sit at that for around 10minutes. Ivevgot the adpwinapi issue fixed, and all the drivers installed. Would you happen to have aim?

lunatic59

Unfortunately, I haven't used aim for year and even if I could remember my credentials, i doubt the account is still active. I do have yahoo messenger and Windows Live accounts.

If you hang up on waiting for device, it means the device is not recognized. Try removing the drivers and reinstalling them.

Try using these drivers.

N1nja

I have yahoo, *******.
I put a command prompt into the superboot folder and did "fastboot-windows devices" and it returned a serial number and fastboot after it. Can I just run "fastboow-windows oem unlock" from there?

Last edited by lunatic59; June 16th, 2011 at 02:45 PM. Reason: removed personal info

lunatic59

yes, you may. If you still don't have success, I'll log into yahoo

Last edited by lunatic59; June 16th, 2011 at 02:44 PM.

N1nja

Sweet! It worked from running it in superboot.
Now, how do I get CM on here?

lunatic59

CyanogenMod for Nexus One

N1nja

How do I go about rooting the phone after getting the bootloader unlocked? Is this necessary for flashing a custom ROM? Will I have the full potential of the phone with no root and a custom ROM?
>>>>>
Did some reading(like I should have before) and ran the install superboot.bat or whatever, command prompt said Okay on it all, and now its stuck at the logo screen before it starts the animation.
Did I b0rk it or is there some simple step I managed to skip?

Last edited by N1nja; June 16th, 2011 at 07:00 PM.

N1nja

Just when I thought it was all done and running I went and broke it.
I tried installing the google apps zip from the CM wiki to get the market and now its stuck in a crazy boot loop. It does the Cyangen splash and then goes to the base Android first screen where it says to touch the Android to begin and then goes back to the Cyanogen splash.
I wiped the data and cache again, reinstalled CM zip from sd and its doing the same thing still.

Hook

Have you tried Ironass's suggestion in this thread o wiping everything, including formatting the SD card?

CyanogenMod 7 (Gingerbread) now a Release Candidate

I never had to do that, but I may have just been lucky.

N1nja

I ended up getting it to work after deciding to just try an older version of CM and when it booted into CM6 I just went back and installed CM7 again and all is good in the hood now.
Is there another way to get the gapps on my phone other than flashing since that's how I b0rked it last night? Like would one of you rooted guys be able to send me the market apk? All my other backed up apps installed and work fine except market

Hook

Did you use the correct version of Gapps for the Nexus One and CM7? I would not restore the apps from backup, particularly the Market. Or did I misunderstand what you meant?

N1nja

I did infcy restore a few apps that were backed up and they work perfectly on CM. I got gapps working now as well, did it from the phone with ROM manager. Looking back at the whole process now it really wasn't all that hard, just troubleshooting and reading with some help from you great guys.

phlojo

Is your phone totally different now? Was it all worth it?

N1nja

Totally worth it, still feels like Android but with more options and things to customize than you can shake a stick at. I like to tinker and having my phone rooted allows just that.
My battery life is considerably longer and can be made more so, which is one of only complaints I had about the N1. Seeing as I came from a bberry curve I was used to charging my phone once or twice a week.

atamatics

N1nja, I'm stuck at exactly the same place - I got the bootloader unlocked but after I tried to root my phone I'm stuck at the logo screen with the unlocked padlock. I am freaking out I bricked my phone and I am not sure what to do next?

atamatics

I eventually proceeded with installing the CGM7 which made my phone working again. I suspect the recovery I tried initially had old versions of some of the files which created the problem in the first place. Lesson learned...