[Root Locked Bloader]Nexus One Easy Rooting Toolkit (DoomLord's via Zergrush Exploit)

[jhenards]

Thanks much for this tut! I had rooted my recently bought n1!

thank you guyz!

 

[thefascinater]

Noob

sorry but i am a complete noob here.
So can anyone plz guide me through step by step process.
Would greatly appreciate that.
using nexus one 2.3.4 stock not rooted

 

[Unlogic.se]

Worked like a charm on my N1 with 2.3.6, took only a few seconds to complete.

 

[thefascinater]

sorry but i am a complete noob here.
So can anyone plz guide me through step by step process.
Would greatly appreciate that.
using nexus one 2.3.4 stock not rooted

Yeah i figured it out !! done with rooting in less than a minute.

 

[Kojo62]

Thanks for this thread. Just rooted my Nexus One for the first time, and this really made it easy. Very much appreciated!

 

[n1newbie]

Thanx a ton. Rooted my nexy 2.3.3 in less than a min :thumbup:

Sent from my Nexus One using Tapatalk

 

[krazichinaman]

Totally new to rooting any device but I've followed the instructions to a T.

Phone is a 100% stock Tmobile USA nexus one running 2.3.6 build GRK39F.

I've downloaded Android SDK and updated the phone driver.


Under: Control Panel = > Device Manager=> Android Phone => It shows Android Composite ADB Interface.

I am assuming that I installed the USB drivers correctly and my computer recognizes my phone?

I follow the instructions on East Rooting Toolkit v3.0 to a T but I know I must be missing a real obvious face palm step. The program is extracted to my desktop.

When I follow the instructions and hit the space bar, it shows
"Waiting for device"
Then a whole ton of:
"The system cannot find the path specified."
Then the ALL DONE!!! Press any key to continue.

What obvious step am I missing here as I know this should work for my device ?

Forgot to add I don't get message on step 6 from the instructions. When I plug in my phone I don't get the "PC Companion Software" prompt on device. Unless this is referring to the "Turn on USB storage" message.

 

[bassmadrigal]

No clue for sure on this, but are you running the program with administrator priveledges? (Right click on the icon and select "Run as administrator")

 

[krazichinaman]

Every time I plug in my phone it shows it as a removable G drive. Guessing my computer recognizes my phone as just a memory drive and not a phone?

---------- Post added at 01:48 AM ---------- Previous post was at 01:46 AM ----------

No clue for sure on this, but are you running the program with administrator priveledges? (Right click on the icon and select "Run as administrator")

Just tried this with the same results. Appreciate the suggestion !

 

[bassmadrigal]

Every time I plug in my phone it shows it as a removable G drive. Guessing my computer recognizes my phone as just a memory drive and not a phone?

Well, according to your last post, since it shows up as a valid adb device, then your computer should recognize it as both a memory drive and an adb composite device.

What happens if you type in adb devices in the command prompt? (you either need to be in the same directory as adb or have that directory included in your PATH)

 

[krazichinaman]

Well, according to your last post, since it shows up as a valid adb device, then your computer should recognize it as both a memory drive and an adb composite device.

What happens if you type in adb devices in the command prompt? (you either need to be in the same directory as adb or have that directory included in your PATH)

When I type in adb devices I get the same message as before

'adb' is not recognizes as an internal or external command,
operable program or batch file.

I found this video and followed the same steps but was unable to find the device via the command prompt, but it shows under my device manager.
http://www.youtube.com/watch?v=Bg-cGTZE2XI&feature=related

 

[bassmadrigal]

You need to be in the same directory as the adb file to verify it is working. This will be somewhere under the Android SDK folder (I think platform\tools).

You could also do a search for adb.exe if you can't find it.

 

[krazichinaman]

You need to be in the same directory as the adb file to verify it is working. This will be somewhere under the Android SDK folder (I think platform\tools).

You could also do a search for adb.exe if you can't find it.

Had some luck. I am now able to get
C:\android\platform-tools>adb devices
List of devices attached
HTXXXXXXXXXXXXXX device

But when I run the script it still says the same thing. The actual runme file is also in the same folder C:\android\platform-tools

When I run in command prompt or click on the file it gives the same message
"The system cannot find the patch specified."

 

[dionix05]

Worked like a charm on a stock 2.3.6 Nexus One. Cheers!

Sent from my Nexus One using xda premium

 

[bassmadrigal]

Had some luck. I am now able to get
C:\android\platform-tools>adb devices
List of devices attached
HTXXXXXXXXXXXXXX device

But when I run the script it still says the same thing. The actual runme file is also in the same folder C:\android\platform-tools

When I run in command prompt or click on the file it gives the same message
"The system cannot find the patch specified."

You need to have all included files in the same folder. Otherwise the script won't know where to find the patches.

 

[krazichinaman]

This whole time I made the BIGGEST FACEPALM mistake possible. Thanks to your last post I figured it out and was rooted within a minute.

Thank You so much bassmadrigal for putting up with my noob questions.

 

[bassmadrigal]

This whole time I made the BIGGEST FACEPALM mistake possible. Thanks to your last post I figured it out and was rooted within a minute.

Thank You so much bassmadrigal for putting up with my noob questions.

We all have our moments... Glad you got it working

 

[rojackjr]

I used your directions on my Nexus one ver. 2.3.6. As I'm still a newbie at much of this my first try was unsuccessful. I had misunderstood what was meant by step 1: "You need to have your phone's drivers installed for adb to work". A quick search and these results made clear what I needed (see: http://forum.xda-developers.com/showthread.php?t=613217) [THANKS TH3FALLEN]. I downloaded the file the link provided and followed Th3fallen's instructions. THEN, I followed your steps and SUCCESS!!! MANY THANKS!!!

 

[wmhilton]

Thanks! I needed to root b/c I was low on app storage. You've given my phone new life!

 

[Nodzor01]

Works, but stuck at the next step

OK noob questions coming up, can't find the answer!

This method works for me to root my N1 (2.3.6), although I have to do the rm ... /boomsh if I run it more than once, and it loses root on reboot.

I am doing it manually using zergRush exploit rather than the other link, as I am on a mac and would like the experience anyway. Maybe this is where I'm going wrong!
When I finish the root my SD card seems to unmount itself; my computer can't see the drive, but I can still adb; I can reattach the card, is that just me?

I am aiming to get to cyanogenmod in the long run, so I believe the next step (as posted on their site) is to install a custom recovery file (going for clockworkmod).

However, it sounds like I need su, which would come along with any root method that involves a bootload unlock but which I don't have? So not sure if I need to push that to the SD card/where to. I got for these problems trying to do so (I put all the files in the one folder platform tools btw)

doms-laptop:platform-tools user$ ./adb push su /system/bin
failed to copy 'su' to '/system/bin/su': Read-only file system

and

doms-laptop:platform-tools user$ ./adb install Superuser.apk
1111 KB/s (785801 bytes in 0.690s)
	pkg: /data/local/tmp/Superuser.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]

I installed the Rom manager app in case they could install superuser rights or clockworkmod from my current rooted stage but no joy, using RomManager to flash clockworkmod recovery fails "while running privileged commands." [That'll be no su then]



EDIT:
So now i booted windows, installed adb drivers, and rooted with the kit, simples... Rom Manager working fine Thanks chaps