yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] efrant:
Your phone IS connected properly. It's just that you are NOT rooted.

Now that you are rooted, you can flash a custom recovery (like ClockworkMod or Amon_RA) and then flash whaever ROM you want.
[Nexus One Android Development] henryr934:
hey u remember where u extract the folder i need help too thanks
[Nexus One Android Development] efrant:
Put everything in the /android-sdk-windows/tools directory...
[Nexus One Android Development] henryr934:
both folders
[Nexus One Android Development] efrant:
Do I really have to answer that? Put the files in the tools directory which is in the android-sdk-windows directory ...
[Nexus One Android Development] HossJT:
When I got to the

F:\ADB>adb kill-server

F:\ADB>adb start-server

steps I got this: The process cannot access the file because it is being used by another process.

I rebooted the phone and killed the adb process, started over and continue to get the error. Any ideas?

Thanks.
[Nexus One Android Development] firechaos:
Ok erm. can u give me a more detailed insturction? When i key the thing in (from the 1st post) It shows "device not ready". So what should i do?

I know its an easy thing to do. But Im really inexperienced. I nid help
[Nexus One Android Development] firechaos:
I also got permission denied. I seriously need help. Anyone nice enough?
[Nexus One Android Development] HossJT:
Figured it out...was running ADB twice
[Nexus One Android Development] firechaos:
Can u tell me detailed instructions on what to do ? (from the beginning)
[Nexus One Android Development] henryr934:
how do i get the F:\ on mine is showing C:/ i have to mount something??? help
[Nexus One Android Development] henryr934:
C:\>cd android-sdk-windows

C:\android-sdk-windows>cd tools

C:\android-sdk-windows\tools>

then how do i get the F:\ help
[Nexus One Android Development] HossJT:
Everything before the '>' is the directory you are in. If you have all the files in C:\android-sdk-windows\tools, continue with the commands after the '>'.
[Nexus One Android Development] efrant:
This thead has all the detailed instructions one needs.

If you are asking these questions, you need to take a step back and do some reading first. the directions in this thread work. Questions like "how do I get the F:" have nothing to do with rooting or flashing or phones at all. If you don't know what C: and F: are (which is basically saying that you don't know that windows assigns different letters to logical drive, and it makes no difference, as long as you are in the tools directory), how can you expect to be able to root a phone manually? Just do a little bit of reading first, and you will see with a bit of knowledge, things will go a lot more smoothly.
[Nexus One Android Development] henryr934:
hey sorry but i got it now but when i get to the part of the busybox it say file not found any idea thanks my friend
[Nexus One Android Development] snovvman:
Hi guys, I'm asking for help here becuase the N1 folks seem to be, at times, more helpful than the Evo folks.

For my N1, I first unrooted using [Tutorial] Root Without Unlocking (Alternative way for all ROMs Vodafone,Korean,US).

With it, I was still able to download and update OTA with 2.2.1. After that, I lost root and re-gained root using the method described in this thread.

I have an Evo as well and would like to root (don't want custom ROM, just want Apps2SD, restart, etc.). As I read the procedures here: [GUIDE] How to root Android 2.2 on the EVO 4G, I see that the procedures are similar.

It seems like "rageagainstthecage" is the key that performs the exploit, thus making the root?

Questions: With the Evo procedure, can I simply stop at the # prompt and gain root? I assume I DO NOT have load the PC36IMG image?

Please enlighten me.

Thanks.
[Nexus One Android Development] cmstlist:
We have no idea what will or won't help you out. It's a totally different phone. However the instructions you've linked to are deprecated. The new version of unrevoked3 should suit your Evo needs.

http://unrevoked.com/rootwiki/doku.php/public/unrevoked3
[Nexus One Android Development] snovvman:
Thank you for replying. I was hoping to find a manual step-by-step method, where it gives me the minimally desired root functions, and not having to load a new recovery image. I don't care to load custom ROMs.

I like the idea of maintaining the OTA update ability.
[Nexus One Android Development] henryr934:
here is a step by step solution

hey i found a video is for a droid but i use the same to do my nexus one u can used i was able to downgrade to 2.2 here the link http://www.youtube.com/user/gigafide#p/u/1/zdmtkHkrgLE
[Nexus One Android Development] cmstlist:
If you really want, you can locate a copy of the stock recovery.img for EVO. Run UnrEVOked3 once to root the phone (and unlock NAND if you wish), and then run it again using the option where it lets you select your own recovery.img. Put the stock one back in and you should be able to get future OTAs.

Good for you, but be very wary about using root guides for one phone on another. You could seriously damage a phone that way.

And now for something completely different...

getting back on topic

. :)
[Nexus One Android Development] zuberio:
**I'm a new user - so I can't post external links ... just wanted to thank the poster from page 2 :D

I followed these steps and it worked :D

Just a quick note - The Superusers Permissions app will force-close on you until it has at least one app that has asked for SU permission in it's list. At least that's what happened on my Nexus One (stock FRG).
[Nexus One Android Development] astron46:
stuck near the end

So here is as far as I get

# mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system

mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system

# cd /data/local/tmp

cd /data/local/tmp

# ./busybox cp busybox /system/bin

./busybox cp busybox /system/bin

./busybox: permission denied

Anyone have any ideas of how to go on from here? I've tried starting from scratch but end up at the same spot. Anybody seen and solved this one?
[Nexus One Android Development] nexusdue:
1) Get rageagainstthecage-arm5.bin

http://stealth.openwall.net/xSports/RageAgainstTheCage.tgz

2) Get Superuser.apk, busybox,su

http://dl.dropbox.com/u/1327667/freenexus.zip

3) Get the Android SDK (ADB)

http://dl.google.com/android/android-sdk_r07-windows.zip

4a) Unzip android SDK (e.g. so that the tools folder is F:\ADB\)

4b) connect Nexus One with with "applications=>development=>USB debug enabled" (and install USB driver if necessary)

5) Unzip/unrar files within RageAgainstTheCage.tgz to F:\ADB\

6) Unzip/unrar files within freenexus.zip to F:\ADB\

7) Open command prompt go to F:\ADB

[7b) Verify that your nexus one is connected and responding - type "adb devices" it should list your N1

8) Now within the command prompt do the following (commands in bold - the rest gives you an indication of the results)

(Note: if you get $ instead of #, just go back and repeat the instructions from where it says $ ./rageagainstthecage. Worked like a charm on the second try for me.)
[Nexus One Android Development] XodoX:
I don't mean to highjack this thread, especially not since this is my very first post on here, but I just wanted to say thank you to all of you who provided detailed information on how to obtain root with FRG83.

I'm a complete noob and spent the last few days reading up on all the necessary information on how to root my Nexus One. I've seen many people state that everything you need to know is contained within these forums and I can confirm that is indeed the case.

So to any other newbies out there... listen to the pros and take the time to read the detailed HowTo's and guides. You'll benefit from it in the long run.

As for me, now that I obtained root on my N1 I'll move on to bigger and better things and try out some custom rom's but not without studying the pro's instructions first. :)

Thanks again for all the info and keep up the great work!
[Nexus One Android Development] astron46:
Thanks from a noobe

Just wanted to add my thanks to all those experts who helped, especially nexusdue for his clear instructions.

I may be the only one this happened to but I spent a day trying to do this in fastboot mode before I finally figured out that I just had to boot the phone normally to use ADB.

The other thing I found was that I could not get a working copy of rageagainstthecage from any of the links on this site. I finally found one that was only 5K on another site. I'm probably not allowed to post links but if others are stuck on this you can google rageagainstthecage-arm5.bin and look for a link that has JoeyKrim in it.

Once again thanks to all. I'll be more careful the next time I take an update from google.:)
[Nexus One Android Development] cardellino:
This work perfectly for me,my nexus one is FRF91 Vodafone Italia > FRG33(via passimg.zip) FRG83 via OTA
[Nexus One Android Development] andynx1:
Hi all,

Was rooted (1click) with superuser ap and busybox installed, then upgraded to 2.2.1. Busybox ap still says "rooted", although clearly Im not.

I'm about to re-root as described, but Busybox installer and superuser aps are still installed but not working. Should I still follow all the instructions including the superuser and Busybox bits?

Tia! Andy
[Nexus One Android Development] nexusdue:
I just re-did it which is why I included the superuser and Busybox bits in my instructions.
[Nexus One Android Development] neoxz:
just continue from here.. works for me

F:\ADB>adb shell

# chmod 4755 /system/bin/busybox

# chmod 4755 /system/bin/su

# exit

F:\ADB>adb shell

# su

su

#mount -o remount,ro -t yaffs2 /dev/block/mtdblock3 /system

# exit

exit
[Nexus One Android Development] jaenizzo:
hey i cant

hey can someone help i cant get this root method to work i tried about ten times and still get this error.

Microsoft Windows XP [Version 5.1.2600]

(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\briyanna>cd..

C:\Documents and Settings>cd..

C:\>cd android-sdk-windows\tools

C:\android-sdk-windows\tools>adb devices

List of devices attached

HT07HP800423 device

C:\android-sdk-windows\tools>adb push rageagainstthecage /data/local/tmp/rageaga

instthecage

640 KB/s (0 bytes in 51200.000s)

C:\android-sdk-windows\tools>adb shell chmod 700 /data/local/tmp/rageagainstthec

age

C:\android-sdk-windows\tools>adb shell

$ cd /data/local/tmp

cd /data/local/tmp

$ ./rageagainstthecage

./rageagainstthecage

./rageagainstthecage: 1: Syntax error: "(" unexpected

$
[Nexus One Android Development] nexusdue:
You did not follow the instructions!

rage is obviously not in your tools folder!
[Nexus One Android Development] jaenizzo:
i did follow instructions

Its inside my android-sdk-windows\tools folder and it not working
[Nexus One Android Development] efrant:
What is the name of the file? Is it rageagainstthecage or is it rageagainstthecage-arm5.bin ?

You have to have the correct file name...
[Nexus One Android Development] jaenizzo:
O

The file I got is just rageagainstthecage.
[Nexus One Android Development] efrant:
Try using the one found in this .zip file: http://www.4shared.com/file/SY__sCo_/Droid2Root.html

Extract it to your tools directory, and rename it to rageagainstthecage then push it to your device and change the permissions like you did before.
[Nexus One Android Development] jaenizzo:
the file work but

the file work but at this one part at the end i keep getting the $ sign instead of the #sign.

C:\android-sdk-windows\tools>adb push rageagainstthecage-arm5.bin /data/local/tm

p/rageagainstthecage

337 KB/s (0 bytes in 5392.000s)

C:\android-sdk-windows\tools>adb push Superuser.apk /data/local/tmp/Superuser.ap

k

865 KB/s (0 bytes in 27688.000s)

C:\android-sdk-windows\tools>adb push su /data/local/tmp/su

546 KB/s (0 bytes in 26248.000s)

C:\android-sdk-windows\tools>adb push busybox /data/local/tmp/busybox

1204 KB/s (0 bytes in 1926944.001s)

C:\android-sdk-windows\tools>adb shell chmod 700 /data/local/tmp/rageagainstthec

age

C:\android-sdk-windows\tools>adb shell

$ cd /data/local/tmp

cd /data/local/tmp

$ ./rageagainstthecage

./rageagainstthecage

[*] CVE-2010-EASY Android local root exploit (C) 2010 by 743C

[*] checking NPROC limit ...

[+] RLIMIT_NPROC={3084, 3084}

[*] Searching for adb ...

[+] Found adb as PID 6032

[*] Spawning children. Dont type anything and wait for reset!

[*]

[*] If you like what we are doing you can send us PayPal money to

[*] 7-4-3-C@web.de so we can compensate time, effort and HW costs.

[*] If you are a company and feel like you profit from our work,

[*] we also accept donations > 1000 USD!

[*]

[*] adb connection will be reset. restart adb server on desktop and re-login.

$

C:\android-sdk-windows\tools>adb kill-server

C:\android-sdk-windows\tools>adb start-server

* daemon not running. starting it now on port 5037 *

* daemon started successfully *

C:\android-sdk-windows\tools>adb shell chmod 755 /data/local/tmp/busybox

C:\android-sdk-windows\tools>adb shell

$
[Nexus One Android Development] efrant:
Try running rageagainstthecage again. I had to do it 3 times before I got root.
[Nexus One Android Development] jaenizzo:
hey thanks

Thank u so much for your help im back to root it took exactly three times to work but im back thanks again
[Nexus One Android Development] CLShortFuse:
I made a GUI

http://xdaforums.com/showthread.php?t=803682
[Nexus One Android Development] the_KIT:
Hi, can u unroot with the program as well?

Thks!
[Nexus One Android Development] efrant:
For those of you asking if you can unroot, do you really need an app to delete three files off your device? Just delete su, busybox and Superuser.apk. Restart and you no longer have root.
[Nexus One Android Development] refthemc:
Might give a shot on the nexus today, thank you OP
[Nexus One Android Development] CLShortFuse:
In the next version it will (and yes, two files. SU and SuperUser.APK)
[Nexus One Android Development] cardellino:
Hi,after the rooting si possible to delete the file in the directory \tmp?
[Nexus One Android Development] gregferns:
Hi. Sorry, just didn't think of that. TX.
[Nexus One Android Development] @rj*n:
THANKS

Super-Duper Thank You mate- works like a charm!

1 Click Done :D
[Nexus One Android Development] o_ssie:
Doesn't work on the Rogers Captivate up in Canada.. I'ts stuck in a loop :(
[Nexus One Android Development] cmstlist:
This is a Nexus One thread. Completely different architecture. You'll want to seek help in the appropriate forum.
[Nexus One Android Development] cmstlist:
By the way, has anyone tested VISIONary root on stock Nexus 2.2.1? I suspect it might work if it's using the same vulnerability.
[Nexus One Android Development] efrant:
rageagainstthecage should work for any device, as it is really an exploit in the function of the adb.
[Nexus One Android Development] cmstlist:
True but if you brick your SGS while trying to root it, you'll get better help from other SGS users than in the Nexus One forum. Also there are other root exploits than this one for the SGS.
[Nexus One Android Development] efrant:
Yeah, you're right, he'll get better help in the SGS forum. But let's not get carried away now - he's not going to brick his phone while trying to root it this way...

Really? I was only aware of the Wi-Fi exploit (which was patched with Android version 2.2.1) and the local root exploit (i.e., rage). I'd be very interested in learning of some new ones if you know of any.
[Nexus One Android Development] cmstlist:
This is really falling off topic... but I'm under tyhe impression that SGS users largely are still on Eclair so the previous on device one click root still works. Also many root guides use an update.zip, which suggests that the SGS recovery doesn't actually check that the file is genuinely from Samsung. But I don't know if any of this has been deprecated by subsequent Samsung patches because I don't own one.
[Nexus One Android Development] efrant:
Ok, so getting back on topic (i.e., [HOW-TO] Root FRGxx builds without unlocking bootloader), does ANYONE know of any other exploits besides the local root exploit (rageagainstthecage) that can root Froyo 2.2.1 on a Nexus One (or any other device for that matter) without flashing a pre-rooted image? And no, packaging up the exploit into a "1-click" or any other package does not make it a different exploit - it's still rageagainstthecage...
[Nexus One Android Development] cmstlist:
If anyone is aware of a different vulnerability, I would forgive them for keeping it secret. This one will eventually be patched. Why waste another root exploit now only to see that one get fixed too?
[Nexus One Android Development] efrant:
I only asked the question because I thought you were (in the first quoted post) pointing the poster to other exploits and I wasn't, and am still not, aware of any other ones besides the two I mentioned ( wi-fi, and local root escalation). I apologize for asking.
[Nexus One Android Development] cmstlist:
Right there's the wi-fi vulnerability (exploid) and the local root escalation vulnerability (rageagainstthecage). But the third more general vulnerability is to flash a rooted update.zip (not a pre-rooted ROM, just a script that roots the phone) in the stock SGS recovery. Don't know if this is the case for all SGS phones but at least for the T-Mo Vibrant and the international i9000, and it's independent of OS version unless Samsung pushes a less vulnerable recovery partition in a new update. This is an option that is not available on stock N1, nor on most newer HTC and Motorola devices anymore. Anyway, if we feel like discussing this more, we're always free to create a thread that explains the differences between N1 and SGS hacking experiences ;)
[Nexus One Android Development] efrant:
Thanks for the info. Although I wasn't really asking about the SGS in specific (as I don't own one) - was asking more of a general Android question, as any Android exploit that works for a particular version of Android on a specific device would work on all Android devices (without an NAND lock). Was trying to keep it related to the topic on how to root a N1.
[Nexus One Android Development] thecircuitbox:
The front page should be updated, with the details from "nexusdue" (page 9 - post 88).

By the way this worked great.
[Nexus One Android Development] dt9394:
this one work for JPP and JPA rom. jailbreak is legal. either u use exploit or recompile the kernel with su it still archive the same goal. That is the reason i support open source project :D
[Nexus One Android Development] cmstlist:
CONFIRMED: VISIONary root app works on stock FRG83. Suddenly this becomes much easier!
[Nexus One Android Development] c3k:
just tested. work on a stock frg83 Nexus, but the root is temporary, you have to check autorun option into the app if you want a full root.
[Nexus One Android Development] cmstlist:
Interesting, and strange. I don't see why it shouldn't last to the next reboot on a Nexus One, seeing as it's just using the same technique we use for permanent root.

In any case you can use VISIONary plus ROM Manager as a quick two step route to custom recovery, and it should suffice if you were intending anyway to flash a new ROM.
[Nexus One Android Development] Mactagonist:
using that quick and easy method (VISIONary + using ROM Manager to flash a ROM) will root access still be available once the N1 boots up with the new ROM?
[Nexus One Android Development] cmstlist:
Yes it should be, if the ROM is pre rooted.
[Nexus One Android Development] c3k:
Yes, until the rom you'll flash is pre-rooted
[Nexus One Android Development] cmstlist:
Also if VISIONary fails to give perm root, but you want to stay stock, here is a possible solution...

1) VISIONary

2) ROM Manager

3) From ROM Manager or custom recovery, flash this update.zip which confers permanent root on N1: http://www.multiupload.com/Q4V1FW105J
[Nexus One Android Development] Mactagonist:
Thanks to you both!
[Nexus One Android Development] leem01:
Where is the su file kept and are you saying to remove them while logged in as su via terminal?
[Nexus One Android Development] efrant:
Well, if you followed the instructions in this thread, then su is located in /system/bin. And yes, you need to be logged in with root access in a terminal (or via an adb shell).
[Nexus One Android Development] leem01:
Not sure what instructions you are talking about since the OP updated this Thread with " EDIT: Great news! We have an on-device one-click root again! ". All I did was follow the step to install VISIONary and everything was done. Now, my su is only found in system/xbin. Can you tell me why that is? I am just trying to understand the back-out plan for VISIONary. Thanks for your help.
[Nexus One Android Development] efrant:
I was talking about the instructions on how to root your device found in the second post of this thread. It is easier to learn by going through all those steps (for those who don't have a good understanding of how rooting works). Using a one-click type app doesn't teach you anything (obviously the case).

If visionary puts su in /system/xbin, then delete it from there. Nothing more to it than that. You would need to delete Superuser.apk as well (assuming you don't want that icon to appear in your apps). Not sure what other files visionary copies over to your system partition, but you would have to remove those as well if you want to remove all traces of your device being rooted... By the way, why would you want to un-root your device anyway?
[Nexus One Android Development] leem01:
Awesome, so this thread did have multiple agenda's. I really appreciate you clarifying this. And yes, you are right the one-click method doesn't really help you understand the different methodologies behind each root. To answer your question about the back out... some times I just dont have time to keep up with every update google pushes and how to re-root. No excuses. Thanks again.

Just an FYI, the whole xbin directory was created when I did the one-click. I checked the time-date stamp. So, I guess the whole dir can be removed.
[Nexus One Android Development] decoyjoe:
I am a nexus one owner. Back when I had 2.2, FRF91 I used a one click root app and gained root access on my nexus one. However, then I mistakenly updated to FRG83 while I was rooted. So after the update to 2.2.1, I obviously lost my root access. Now when trying to use VISIONAry, it says that I am already rooted, but that is not the case as I dont have any superuser rights. And I am unable to undo root with the universal androot. So I am stuck with my phone saying that I already have root access when I dont.

Any ideas on how to fix/resolve this and regain my root access?

Thanks
[Nexus One Android Development] cmstlist:
I suspect this is because Superuser.apk or su is still in your system partition, but the OTA fiddled with the permissions. You'll have to go through the manual route instead of VISIONary.
[Nexus One Android Development] Philderbeast:
visionary worked a treat on my HTC desire (telstra 2.2 rom)

just what i have been looking for!
[Nexus One Android Development] efrant:
See post #2 of this thread for instructions on how to root...
[Nexus One Android Development] decoyjoe:
Does the manual method explained in post #2 unlock the bootloader or void the warranty in any way?
[Nexus One Android Development] efrant:
1. The only way to unlock the bootloader on a Nexus One is by issuing the fastboot oem unlock command from an ADB console. Since you are not doing that, it does not unlock your bootloader. And besides, if you (or a binary) issues that command, you will see a confirmation dialog on your device, which you will need to click to confirm...

2. Making changes to the /system partition (which is what rooting by ANY METHOD does) technically voids your warranty. HOWEVER, since you can reverse those changes, you can restore the system partition to how it was before rooting and, hence, you can still use your warranty. This is not the case with unlocking the bootloader, as that is not reversable (for most Nexus Ones).

3. Having said that, some XDA members have reported HTC honoring the warranty despite having an unlocked bootloader.