yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] jdmoore81:
It is works similar to one click but you need a PC android sdk installed then you just double click on superboot windows oh and you Need to be in fastboot a cmd window will pop up and when your phone reboots you will be rooted.
[Nexus One Android Development] emcwhite:
Thanks! I appreciate it!
[Nexus One Android Development] droiddv:
need username and password?
[Nexus One Android Development] Rusty!:
Chances are you wont, there's been a lot of leaked ROMs in the past and only a couple of them ever were released (AT&T and Voda build).
[Nexus One Android Development] ronjeremy11:
Is it safe to say that rooting is the only way to get rid of 33?
[Nexus One Android Development] ali3nfr3ak:
at this stage , i think the only way to rid of FRG33 is unlock the bootloader
[Nexus One Android Development] aarehmat:
ditto for me... thanks in advance
[Nexus One Android Development] moda0222:
So it's safe to say that this update is authentic?
[Nexus One Android Development] cmstlist:
If it weren't authentic, it would not load successfully via the PASSIMG.ZIP method on a locked bootloader. Only signed ROMs can be applied that way.

But that's not to say this update is bug-free. If you're unrooted on FRF91 and your bootloader isn't unlocked, I would highly recommend this upgrade path instead:

1-Click Root -> ROM Manager -> flash ClockworkMod recovery -> full nandroid backup -> apply Paul's repacked version as an update.zip.

This will allow you a simple roll-back pathway (i.e. boot into custom recovery and restore the backup). If you upgrade via the PASSIMG method, then according to reports on this thread you lose all possible return pathways short of unlocking the bootloader.
[Nexus One Android Development] DMaverick50:
when i flashed this i got it from the modaco link, i used the top one that indicated it was the full file but there were several ones below that were labeled, there were i think 2 different ones for rooted phones and 2 different ones for stock phones, and i think those were initially the ones we were supposed to use but they didnt work. were those supposed to have the modified build.prop?
[Nexus One Android Development] ali3nfr3ak:
I agree. I stupidly just flashed this and cannot downgrade, have tried several different options to downgrade but none have worked, have held off from unlocking the bootloader, hoping someone will come up with a miracle LOL
[Nexus One Android Development] moda0222:
Well I went the paasimg route because I have upgrade ocd...i needed you last week Hehe...thanks for the info...will use going forward.
[Nexus One Android Development] ronjeremy11:
This problem is compounded because afaik very few people flashed it and are now stuck with it and want to stay locked, like me. Since there isn't a lot of focus on it I'm not holding out too much hope for a fix. Stupid question - So the build.prop can't be modified and repackaged as a flashable zip in order to give us stock suckers access to our protected apps? Just curious
[Nexus One Android Development] ali3nfr3ak:
no i dont think you can as the flashable zip wont have htc/google signed code
[Nexus One Android Development] cmstlist:
I guess the only way the "stuck" folks can revert without unlocking is either to find a new root vulnerability, or to find some sort of master override that can load up an older official firmware version.
[Nexus One Android Development] stfl:
My friend's new nexus one is already FRG33 as it arrived, there is no way to use 1-click root.

I've tried to use new exploit from C skills and it did show "#". So I think it should do the trick.

I doesn't flash anything yet, therefore, this is for your reference.

C skills: h ttp://c-skills.blogspot.com/2010/08/please-hold-line.html

1. Get the exploit (executable file)

exploit: h ttp://stealth.openwall.net/xSports/RageAgainstTheCage.tgz

2. Extract the .tgz file to get the "rageagainstthecage-arm5.bin"

I put the file in d:\RageAgainstTheCage

3. Put exploit file to your N1

adb push d:\RageAgainstTheCage\rageagainstthecage-arm5.bin /data/local/tmp/rageagainstthecage

adb shell chmod 700 /data/local/tmp/rageagainstthecage

4. Enter adb shell

adb shell

5. Execute exploit (It will automatically close adb shell)

$cd /data/local/tmp

$./rageagainstthecage

6. Restart adb

adb kill-server

adb start-server

7. Enter adb shell again

# (Yes, my lord.)

I've found it may not success every time, if it doesn't, please go through steps 4~7 again.

If it still doesn't work, we need to wait a new way to root. Good luck.
[Nexus One Android Development] DMaverick50:
is there yet a proven way to root 33? Ive searched this site and thru google with no clear findings. I didnt want ot unlock my bootloader but i am so sick of 33 that now I want to do it but i dont want to just jump on board one of the methods if ill jack up my phone. The above instructions are really confusing, but they havent been confirmed either as i understand it. Thanks for any help, i cant get rid of 33 quick enough...
[Nexus One Android Development] cmstlist:
Very interesting, thank you! I assume this is largely same exploit that was originally published here:

http://xdaforums.com/showthread.php?t=736271

which has had various names applied to the individual files - freenexus, rageagainstthecage, exploid.

I had always assumed that the one-click root relied on exactly the same vulnerability as the "exploid" method. But perhaps FRG33 breaks only the 1-click and not the manual method?
[Nexus One Android Development] ali3nfr3ak:
F:\ADB>adb push rageagainstthecage-arm5.bin /data/local/tmp/rageagainstthecage
263 KB/s (5392 bytes in 0.020s)

F:\ADB>adb shell chmod 700 /data/local/tmp/rageagainstthecage

F:\ADB>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 64
[*] 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[at]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.
$
F:\ADB>adb kill-server

F:\ADB>adb start-server
* daemon not running. starting it now *
* daemon started successfully *

F:\ADB>adb shell
#
[Nexus One Android Development] ali3nfr3ak:
ok i did the steps outlined by stfl, and have

adb shell

#

ideas on next step please?
[Nexus One Android Development] cmstlist:
Okay so this gives you a root shell... but you don't have superuser and su loaded yet right? So I suggest taking a look at these instructions:

http://xdaforums.com/showthread.php?t=736271

with recognition that some file locations will be different because you're using a different version of the exploit. Your aim is to end up with busybox, su and superuser.apk in all the right places with all the right permissions.

If you can do this - you should then be able to run ROM Manager and grant it root access. Flash ClockworkMod recovery. If you had a nandroid backup from pre-upgrade, restore to it now. If you didn't have such a backup, then in ROM Manager go to Download ROM > Stock Images > Nexus One FRF91, pick the rooted or stock option.

Let us know how it goes and what you had to do... maybe someone who's more Linuxy can clarify this better =)
[Nexus One Android Development] DMaverick50:
i unlocked and used superboot 91, hopefully i can get rid of 33 now
[Nexus One Android Development] ali3nfr3ak:
Hey thanks for that, will give it a go and report back... =)
[Nexus One Android Development] DMaverick50:
i unlocked, rooted, flashed custom recovery. anytime i try to flash a rom or just stock frf 91, in recovery i get:

Welcome to CyanogenMod-6.0.0-N1!

assert failed: getprop ("ro.bootloader") == ".33.2012: and so on...

i found something about hboot when i searched but i still dont understand. i unlocked and rooted to get rid of 33, anyone know what im doing wrong? thanks
[Nexus One Android Development] ali3nfr3ak:
have a look here

http://xdaforums.com/showthread.php?t=726258
[Nexus One Android Development] ali3nfr3ak:
Yes !!! I did it. :D, I now have Ra-nexus-v1.8.0 as my recovery

HUGE PROPS to stfl for finding exploit, and cmstlist for direction

Basically i followed the instrucions stfl posted, but it dosent always work, just keep trying it will, i had to repeat it 3 times.

F:\ADB>adb push rageagainstthecage-arm5.bin /data/local/tmp/rageagainstthecage
263 KB/s (5392 bytes in 0.020s)

F:\ADB>adb shell chmod 700 /data/local/tmp/rageagainstthecage

F:\ADB>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 64[*] 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[at]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.
$
F:\ADB>adb kill-server

F:\ADB>adb start-server
* daemon not running. starting it now *
* daemon started successfully *

F:\ADB>adb shell
#

then did the steps in this thread http://xdaforums.com/showthread.php?t=736271

1. run freenexus.bat
2. adb shell
3. cd /data/local/tmp
4. ./freenexus ( i didnt bother toggling wifi ) it will hang and youll have to maunally close that command box and open a new one
5. C:\Users\Administrator>f:

F:\>cd adb

F:\ADB>adb shell
# cd /data/local/tmp
cd /data/local/tmp
# ./busybox cp busybox /system/bin
./busybox cp busybox /system/bin
# chmod 4755 /system/bin/busybox
chmod 4755 /system/bin/busybox
# busybox cp Superuser.apk /system/app
busybox cp Superuser.apk /system/app
# busybox cp su /system/bin
busybox cp su /system/bin
# chmod 4755 /system/bin/su
chmod 4755 /system/bin/su
# exit
exit

F:\ADB>adb shell
# su
su
# exit
exit

F:\ADB>adb push flash_image /data/local/tmp/flash_image
873 KB/s (76044 bytes in 0.085s)

F:\ADB>adb shell
# su
su
# mount -o rw,remount /dev/block/mtdblock /system
mount -o rw,remount /dev/block/mtdblock /system
# cd /data/local/tmp
cd /data/local/tmp
# chmod 755 flash_image
chmod 755 flash_image
# ./flash_image recovery /sdcard/recovery.img
./flash_image recovery /sdcard/recovery.img
#
F:\ADB>#

DO NOT POWER OFF PHONE DURING ANY STEPS OTHERWISE YOU WILL HAVE TO START AGAIN
[Nexus One Android Development] cmstlist:
Nice, I'm glad you managed to get custom recovery! Were you able to revert successfully to an earlier build?
[Nexus One Android Development] ali3nfr3ak:
I havent tried yet, i think my wife will punch me if i try that LOL, Ill report back tomorrow
[Nexus One Android Development] stfl:
Yes, you are correct. The 1-click author said he only used exploid(wifi exploit) method and he may add the rageagainstthecage(adb spwaning exploit) method some other day.

That's why 1-click root doesn't work on FRG33; only the manual method applies to FRG33 right now.
[Nexus One Android Development] cmstlist:
Interesting to know these details, thanks. On one hand it would be very useful to have the latter method in a 1-click root; on the other hand, Google will probably patch that one up in a future build anyways so it may be short-lived =)
[Nexus One Android Development] DMaverick50:
thanks, i did take a look at that, its pretty intimidating so i was hoping for an easier solution. Oh well, ive come this far, and i need those damned protected apps so ill see what i can do with those instructions.

Im also wondering if i could just flash the froyo radio? Would that bring along that older spl? I asked in another thread but the reply was a bit confusing, he said "not unless i use passimg" which seems simple enough to me, i just need to find the zip, i could only find the .img and im not sure if i can convert it. But that same reply indicated that if i dont use passimg, "radio will only touch radio, especially if i use fastboot", but i thought passimg would have to be thru fastboot wouldnt it?

The Kradio isnt working for me anyway so i want the froyo radio back, so if i could flash that in a way to also get the hboot that would be awesome.

Im asking a thousand questions because i cant afford to jack my phone up, and so far, the only thing about this that resembles my days of messing with the g1 are the terminal commands, lots of new ground for me to cover here. thanks for the help, im awfully close

Edit: flashed 91 radio successfully, it wouldnt passimg so i just flashed the zip from recovery, but hboot is still 35.0017
[Nexus One Android Development] ali3nfr3ak:
I'm not really that knowlegdeable about android stuff, but I'm sure the only way back to 0.33.0012 is by following those steps in the revert HBOOT thread,
[Nexus One Android Development] DMaverick50:
yeah i ended up following those (tried to anyway), got all the files downloaded and modified but cant get terminal to recognize my device. This is tough but its good practice. Maybe when its all said and done i can be glad i flashed this god forsaken 33
[Nexus One Android Development] AndroidPerson:
im at the same spot. I rooted and had to setup usb, AndroidSDK, and Fastboot, but when i do the terminal commands in the revert thread, it says it doesnt recognize the device. I looked at the thread about adb commands, but between that and a ton of google searches i cant find anything about initial steps to access the phone, to make it recognize the phone. the phone says fastboot usb in red, and terminal responds it doesnt recognize the device im sure i have the files in the right place, im typing in the correct commands. ive just done so much searching, and ive followed the instructions so closely. I cant think of anything else to try or anything else to search for
[Nexus One Android Development] ali3nfr3ak:
I have successfully reverted back to HBOOT-0.33.0012 :D

I used this rom after I achieved root http://xdaforums.com/showthread.php?t=714184

Then followed steps in this thread http://xdaforums.com/showthread.php?t=726258
[Nexus One Android Development] DMaverick50:
thanks for this, the rom works great. Somehow I missed that there was a 33 rom around. Im working through the same revert thread you used but I still cant get my "device detected" in terminal to finish it. But now that ive got this rom im in no hurry, paid apps are working fine, thanks again!
[Nexus One Android Development] ali3nfr3ak:
your phone has to be booted into operating system, not bootloader
[Nexus One Android Development] DMaverick50:
damn thank you, can you explain how to do that? I assume you dont mean just boot the phone up right? I know power down + power, and trackball+power but thats it. Whenever i did superboot i just ran commands in fastboot, i didnt realize there was another way to enter commands. Thanks

edit: oh wow thats exactly what you meant. Thanks im all set, it errored trying to find a file but im sure ill get it now that im in the right spot. thanks again
[Nexus One Android Development] ali3nfr3ak:
no worries :D, good luck
[Nexus One Android Development] Airbag888:
Would these instructions work from the Terminal app? That is without using adb?
[Nexus One Android Development] Devastatin:
no

10chars
[Nexus One Android Development] l0uisz:
i keep getting this...

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

l/tmp/rageagainstthecage

cannot stat 'rageagainstthecage-arm5.bin': No such file or directory

the file is in C:/android-sdk-windows/tools ? any ideas what i'am doing wrong?
[Nexus One Android Development] efrant:
There is something wrong with your directory structure. Your post above shows an ADB directory, which shouldn't be there...
[Nexus One Android Development] l0uisz:
i finally fixed that problem but now on to ANOTHER....

Microsoft Windows [Version 6.0.6002]

Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\Users\loulitohernandez>cd/android-sdk-windows/tools

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

l/tmp/rageagainstthecage

43 KB/s (5392 bytes in 0.120s)

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

thecage

The process cannot access the file because it is being used by another process.

C:\android-sdk-windows\tools>

what could have happened here? SCRATCH THAT i GOT THE # to come up ! =) now what after this has been completed? do i follow this post http://xdaforums.com/showthread.php?t=736271 ? or is there anything else specifically i must do?
[Nexus One Android Development] Rusty!:
Stop putting ADB> before each command for a start.

Probably wont help but you should really learn the right syntax for this stuff ;) What it's doing is creating a file called adb filled with the output of the command.
[Nexus One Android Development] fabler:
Are you running two instances of adb?
[Nexus One Android Development] l0uisz:
yea i was HEAD SMACK! LOL but i finally turned the $ into the rooted # but after this what next? do i have to follow any steps over here? http://xdaforums.com/showthread.php?t=736271
[Nexus One Android Development] fabler:
I am sorry.. I am out of conversation.. what are you upto?
[Nexus One Android Development] fabler:
try this if you want to root FRGxx builds.. http://xdaforums.com/showpost.php?p=8315805&postcount=2
[Nexus One Android Development] l0uisz:
well buddy i just finally COMPLETED this

1. Get the exploit (executable file)

exploit: h ttp://stealth.openwall.net/xSports/RageAgainstTheCage.tgz

2. Extract the .tgz file to get the "rageagainstthecage-arm5.bin"

I put the file in d:\RageAgainstTheCage

3. Put exploit file to your N1

adb push d:\RageAgainstTheCage\rageagainstthecage-arm5.bin /data/local/tmp/rageagainstthecage

adb shell chmod 700 /data/local/tmp/rageagainstthecage

4. Enter adb shell

adb shell

5. Execute exploit (It will automatically close adb shell)

$cd /data/local/tmp

$./rageagainstthecage

6. Restart adb

adb kill-server

adb start-server

7. Enter adb shell again

# (Yes, my lord.)

to get the # to come up.....but now what do i do next? because i went into my nexus one and tried to do a SCREEN SNAP SHOT ( which of course can only be done w/ ROOT ) and it tells me your phone has to be rooted...?
[Nexus One Android Development] l0uisz:
ooh no i want to keep my stock FRG83 build but just want ROOT.
[Nexus One Android Development] efrant:
Yes, you need to install busybox and su (and superuser.apk) before you are rooted. All you have now is a temporary root shell.
[Nexus One Android Development] fabler:
Try this http://xdaforums.com/showpost.php?p=8315805&postcount=2
[Nexus One Android Development] efrant:
:confused: That is what the quoted post does...
[Nexus One Android Development] fabler:
yeah right.

see ya tomorrow guys..
[Nexus One Android Development] l0uisz:
i already do from previous root....do i need to REinstall them?
[Nexus One Android Development] efrant:
If they are still there, probably not. You may want to check the permissions though.

Just to be sure, I would execute these commands from a root shell (i.e., at the # prompt) assuming the file are already there:

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

# cd /data/local/tmp

# chmod 4755 /system/bin/busybox

# chmod 4755 /system/bin/su

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

# exit
[Nexus One Android Development] l0uisz:
C:\android-sdk-windows\tools>adb shell

# ./busybox cp busybox /system/bin

./busybox cp busybox /system/bin

./busybox: not found

# 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

# chmod 4755 /system/bin/busybox

chmod 4755 /system/bin/busybox

Unable to chmod /system/bin/busybox: No such file or directory

#

busybox is no longer there...

BTW permissions DENIED, i checked.
[Nexus One Android Development] efrant:
You need to mount the partition as rw BEFORE you try copying busybox over...
[Nexus One Android Development] l0uisz:
okay so then it would be like this..? because i just recently started up on rooting again, its been awhile! so i'am RUSTY...

# mount,rw -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
[Nexus One Android Development] efrant:
Look at my post...
[Nexus One Android Development] l0uisz:
still confused..

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

# mount -o rw,remount /dev/block/stl9 /system

mount -o rw,remount /dev/block/stl9 /system

# exit

exit

C:\android-sdk-windows\tools>adb push <path to su>/su /system/bin/su

The system cannot find the file specified.

C:\android-sdk-windows\tools>

i tried using this post to help...http://xdaforums.com/showpost.php?p=8079243&postcount=51 but to No avail i wonder if iam still missing files....i see busybox and SU and superuser.apk in the tools folder of my SDK just dont have a clue.
[Nexus One Android Development] efrant:
You don't have a clue and are confused, because you are not reading what I post. The command you issued in NOT correct. Compare what you typed with what I had typed.

Secondly, why are you looking in the Samsung Fascinate forums? If you would look at the Nexus One forums (I am assuming you have an N1), you would see many threads with proper instructions.

Thirdly, do this from a command prompt in the /android-sdk-windows/tools directory, where all three files should be (and not in zip files):

adb push Superuser.apk /data/local/tmp/Superuser.apk

adb push su /data/local/tmp/su

adb push busybox /data/local/tmp/busybox

Then, from a ROOT shell:

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

# cd /data/local/tmp

# ./busybox cp busybox /system/bin

# chmod 4755 /system/bin/busybox

# busybox cp Superuser.apk /system/app

# busybox cp su /system/bin

# chmod 4755 /system/bin/su

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

# exit
[Nexus One Android Development] l0uisz:
C:\android-sdk-windows\tools>adb push Superuser.apk /data/local/tmp/Superuser.ap

k

24 KB/s (27688 bytes in 1.108s)

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

198 KB/s (26248 bytes in 0.129s)

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

672 KB/s (1926944 bytes in 2.798s)

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

# 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

#

alright so i tried it with busybox ALREADY installed in my phone FAILED, now i tried it again but uninstalled the previous busybox from the LAST root and still got the same message above..?
[Nexus One Android Development] efrant:
Well, I am all out of suggestions. Not sure why it's not working for you. Maybe someone more knowledgeable than I could chime in and help out.
[Nexus One Android Development] l0uisz:
thanks a bunch! =) definitely appreciated guess for now ill take a BREAK! my head is seeing everything in black and white lol.

OH HEY! btw do you know if there might be another 1 click root apk upcoming? or from now on itll be manual rooting processes?

OH i fixed the busybox problem i went into the market and installed the latest busybox and it asked me for root permissions! =) so i just iam ROOTED for good! to test this ill reboot and see if i still have it. THANKS!
[Nexus One Android Development] Rusty!:
Dunno if it will help, but instead of trying to use the not-yet-installed busybox to copy itself to system/bin, try this:

cd /system/bin
cat /data/local/tmp/busybox > busybox
chmod 4755 busybox
[Nexus One Android Development] l0uisz:
i dont know if you read my previous UPDATED post i got it to work i reinstalled busybox via the market and su permissions popped up for me! so im all set thanks for the extra info!