yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] foxwolfblood:
Thanks for this tut!

made rooting my nexus so much easier. now to overclocking :D
[Nexus One Android Development] :
Problem!!

Hi,

I have a problem with Step 19. After I type in su, cmd says Permission denied and my N1 reboots. When it restarts there is no Superuser in the apps home page.

What do I do?

Thanks
[Nexus One Android Development] ultraviolet74:
I did everything ok but when I type:

adb shell

su

always:

"Permission denied"

But devices is rooted, I tried to install Titanium backup and it gain root

but I can't install recovery Amon_RA,

plese help!

Additinal information:

Nexusone PVT SHIP S-ON

HBOOT-0.33.0012

MICROP-0b15

TOUCH PANEL-SYNT0103

RADIO-5.08.00.04

Dec 17 2009, 13:05:23

Android 2.2

32.41.00.32U_5.08.00.04

2.6.32.9-27227-g3c98b0d

haley@m4-dev #1

N°Build

FRF91
[Nexus One Android Development] ultraviolet74:
SOLVED!!!!!!!
[Nexus One Android Development] Franky124578:
Cant get past $ ./freenexus

everytime I type in ./freenexus, it will tell me ./freenexus not found. I ve checked that there is no "Freenexus" folder and all the other steps have worked up to that one. Anything that i could be doing wrong!?

Update. k so never mind I got passed that...now i m on step where you have to type in rootshell but when I type that in it says premission denied. I ve checked and I did not have -dw thing I do have an r there but it still doenst allow me to root
[Nexus One Android Development] SharpIS03:
Sharp IS03

The bolded part is the part I'm interested in. My phone is totally different, but I tried this method anyways. I got as far as step 14, but when I run rootshell, I get permission denied.

Anyways, my system partition is on mtdblock4 with yaffs2. How does that change things as far as running the code is concerned? Is it a big or small change?

I'm sorry if my questions don't make sense, I'm still grasping this kind of stuff as I read all these different forums.

Thanks for your time.
[Nexus One Android Development] flip3547:
MTD3

I just purchased a wopad tablet, I've tried every root method I can find. Only one has worked and has only temp rooted. My system partition is at mtdblock4, I wonder how this could be adjusted in a way for it to work with this partition scheme?
[Nexus One Android Development] Jemjemejeremy:
Do I have to wipe data after rooting a stock N1? Will my contacts and SMS be saved?
[Nexus One Android Development] tanclo:
Thanks for this very useful and comprehensive post - I rooted Froyo using the wifi exploit method described. I was given a power button failed Korean CID Nexus One by a student who was told by Service center that the mainboard was broken. Without the ability to unlock the bootloader (power button is required to confirm fastboot oem unlock), I downgraded to Korean Android 2.3.3 using PASSIMG method: renamed PASSION-KR-FRF91 to PASSIMG.zip - The ROM must be an official version for the device (same region) otherwise the PASSIMG process will fail. Nexus One official ROMS can be found here http://www.mediafire.com/n1passion

The linux commands in this post worked FLAWLESSLY and I was rooted in no time. I used ROM Manager to install custom CWM. Installed root explorer and searched for

/system/etc/install-recovery.sh

/system/recovery-from-boot.p

but I didn't see those in there. I didn't require the stock rom after a reboot anyway so I continued to download CM7 and installed using ROM Manager. All is good now!!

MUCH APPRECIATION - doing things without a windows bash script via VirtualBox is still and always will be the best method!
[Nexus One Android Development] pseudoheld:
worked like a charm for me! thank you ever so much!
[Nexus One Android Development] AlessandroIT:
I've succesfully rooted my N1 running VF FRF91!

Awesome work man!

Then i was trying to revert to HBOOT 0.33 following the thread you linked but i have a question..

Since our bootloader is locked, will it allow us to flash EPF30 PASSIMG (which is a previous version than current frf91..)?

Thanks
[Nexus One Android Development] PSeeCO:
If you were on VF FRF91 you should already be on 0.33
[Nexus One Android Development] AlessandroIT:
Was previously on Korean, then flashed the Vodafone FRF91 using PASSIMG..

Still stuck on HBOOT 0.35.0017

Didn't tryied yet the method in the linked topic cause i think it will fail as it request to use EPF30 PASSIMG which is an older version that current rom, and since my bootloader is still locked, it won't allow me to flash it :\
[Nexus One Android Development] jivemaster:
I can confirm this also worked for me, running a Nexus One T-Mobile version here, now with root, and with warranty/bootloader intact ;)

Many many many many thanks to the OP.
[Nexus One Android Development] dolomiti7:
@AllesandroIT:

yes, you can flash EPF30 with the HBOOT downgrade method. The only thing you need for that is root - which you have now.

In easy words: after the "flash_image misc mtd0.img" command from the HBOOT tutorial you force the HBOOT version to 0.22. At that point the bootloader will accept every PASSIMG.zip. At least I think so, as I didn't try them all, but it will definitely work with EPF30. The above root method is also working on EPF30, so there shouldn't be a problem. Just flash EPF30, root again, custom recovery,CM6.

Before I wrote the tutorial I tested this way:

Korean FRF91->root->HBOOT-downgrade->EPF30->root->CM6

Edit: to be precise:

Korean FRF91->root->HBOOT-downgrade->EPF30->root->Froyo radio->CM6
[Nexus One Android Development] fc_themaster:
Excuse me, I'm still a newbie on android.

I want to install CM6.

I've done this steps. I have rooted phone with your guide, i've installed Rom Manager and Clockwork Recovery. Can I install safely CM6 now? I've no idea what is this HBoot...

I have to do other processes or can I proceed with the Cyano?

thanks and excuse my english.
[Nexus One Android Development] dolomiti7:
you can check your HBOOT and radio version by holding down the trackball while turning on the phone with the power button. In the second line you will see the HBOOT version. Edit: Somewhere below is also the radio version.

0.33.xx : CM6 will work

0.35.xx : CM6 RC1 won't work. (need to downgrade first)

CM6 RC2 maybe? didn't test it

CM6 final will probably work, but not for sure.

Before installing CM6 you definitely need a froyo radio version.

I think 4.06.00.12_7 is the minimum, but I am not sure. See CM6 tutorials for that.

I added a link to the latest radio thread at the end of the tutorial.
[Nexus One Android Development] fc_themaster:
Without downgrade i still have HBOOT 0.33.0012 and Radio 5.08.00.04.

Can I Proceed with Cyano?

Another question: I've seen in the Rom Manager the tool for the partitioning of SD card. If I do this tool I'll lose Superuser?
[Nexus One Android Development] dolomiti7:
In that case there should be no problem to proceed with Cyanogen. Think about creating a Nandroid Backup from the recovery before installing CM6.

There is currently no reason or benefit to partition the SD card with CM6. For CM5 it was a good idea to create an Ext-Partition for apps2sd. CM6 uses the standard froyo apps2sd which is using the standard FAT32 partition. Partitioning would be waste of space. And no, this has nothing to do with root rights.
[Nexus One Android Development] fc_themaster:
OK I proceed with Cyano! :D:D
[Nexus One Android Development] karl ghega:
You have no idea how much trouble you have saved to many of us. The "recovey" method was driving us crazy by adb not properly recognizing the device on the final step.

This was smooth like silk.

Donation on it's way....well deserved !!!
[Nexus One Android Development] fc_themaster:
I've installed CM6 RC2, after i've done restore of my backup for recovery and now i've still original FRF91!!! How it is possible?
[Nexus One Android Development] dolomiti7:
Well, if you did a full restore of your Nandroid Backup then of course you are back to the point where you have been before installing CM6. But at least you should still have root rights. The Nandroid backup is just meant as a fallback in case something doesn't work properly with CM6 or other roms you try out.

If you want CM6 you need to start from scratch (full wipe) or use other methods to backup and restore your settings, apps, etc. after CM6 installation.

But this is getting a bit off-topic. Maybe you will find more help in the CM6 thread.
[Nexus One Android Development] fc_themaster:
Loool sorry...I thought that it was a backup of my settings and apps...
[Nexus One Android Development] dolomiti7:
:-) but still it is a good idea to keep this backup - just in case...

By the way: a full nandroid backup does restore nearly everything, but it doesn't touch the radio. If you play around with different radio versions, you have to flash them before restoring a nandroid backup.
[Nexus One Android Development] futango:
Confirmed this is working. Just finished the process on Stock ATT N1. Thanks for the easy steps.
[Nexus One Android Development] PSeeCO:
Finally done (successfully) on my N1 vodafone!
[Nexus One Android Development] azazel673:
thks again, we try on a stock nexus one with android 2.1 on Smartphonefrance, work great

as i say you i will try with a desire as soon as possible, and Drake (from smartphonefrance again) will give you all info about his nexus before rooting, tomorrow i hope ;)

many thanks from France ;)

zaraki (on smartphonefrance)

azazel673 here :D

Edit : will try also on a 2.2 korean rom soon :D
[Nexus One Android Development] brandont218:
if i use this without flashing a custom rom, will i still be able to receive android OS updates? also, this doesn't unlock the bootloader, so does it mean that my warranty is still valid?
[Nexus One Android Development] mobiousdigital:
Yes and Yes... Just rooted mine via this method and it is flawless and painless! :-)
[Nexus One Android Development] PSeeCO:
There's something i must do before i'll be able to flash a recovery? I get this error:

sending 'recovery' (3948 KB)... OKAY

writing 'recovery'... INFOsignature checking...

FAILED (remote: signature verify fail)
[Nexus One Android Development] brandont218:
worked great. im rooted. took me about 5 minutes. thanks a lot!

but now that im rooted.. i dont know what i wanna do.. i don't really wanna get CM on it because i want OTA updates.. i can't get trackball alerts cuz i dont have a custom ROM.. :(

what else can i do with a rooted nexus one?
[Nexus One Android Development] ilostchild:
SWEET I BEEN WAITING FOR SOMETHING LIKE THIS!!

lol sorry excited i been wanting root for my n1 long time now i do thanks bunch and workd flawless! lol
[Nexus One Android Development] lemon seltzer:
Sorry if this is a noob question, but I'm not able to get custom recovery to "stick" with rom manager after rooting with this method. After every flash, I can reboot to custom recovery only once. after that it's back to stock recovery. I've tried flashing multiple times in rom manager with clockword and amon_ra and I get the same result every time. Something I'm doing wrong? Or is there an alternate/better way to flash recovery after rooting with this method?
[Nexus One Android Development] jivemaster:
You can do anything you like. For me I like stock froyo so I have kept it for now. I did however use the newly acquired root access to install the fixed wifi driver (to remove screen off disconnection problem), as well as to install some ad blocking apps, and to make nand backups of my os. I am going to try the 720p froyo record mod too once it's released soon.

I may try a desire rom later once the major bugs are fixed.

Anyone have a suggestion for trackball notification mods on stock froyo? Trackball alert only supports cm.
[Nexus One Android Development] futango:
I was having a hard time getting the recovery to stick too. But I follow these instructions in the other rooting without unlocking bootloader and u got my own customized amon_ra recovery on here.

16) Download the following to the root of your SDcard

- recovery-RA-nexus-v1.7.0.1.img: http://rapidshare.com/files/39326736...s-v1.7.0.1.img

- Note: UnMount your SDcard after copying these files, but keep your phone plugged in

17) In your terminal type "adb shell" and hit Enter

18) In your terminal type "su" and hit Enter

- Tip: At this point, it will hang until you choose "Allow" on your phone with the SuperUser app pop-up

- Tip: $ should now be replaced with #

19) In your terminal, type "mount -o rw,remount /dev/block/mtdblock4 /system" and hit Enter

20) In your terminal, type "cat /sdcard/flash_image > /system/bin/flash_image" and hit Enter

21) In your terminal, type "chmod 775 /system/bin/flash_image" and hit Enter

22) In your terminal, type "flash_image recovery /sdcard/recovery-RA-nexus-v1.7.0.1.img" and hit Enter

23) In your terminal, type "rm /system/etc/install-recovery.sh" and hit Enter

24) In your terminal, type "rm /system/recovery-from-boot.p" and hit Enter

You will need the Attached file from this thread. The Root FRF83. upzip it and take the flash_image from it and put it in your sd card also along with the recovery file.

http://xdaforums.com/showthread.php?t=710842
[Nexus One Android Development] jivemaster:
Yeah those steps 23 and 24 are important, otherwise when you reboot the recovery gets wiped and you left with nothing to recover to. So I recommend checking you can get into recovery from a fresh boot to ensure it's there when you decide screwing around with roms/hacking.
[Nexus One Android Development] dolomiti7:
Regarding the recovery problem:

Flashing the recovery manually is always more transparent (and maybe more reliable) than using ROM Manager. I have added a link to the old rooting method thread and a download link for "flash_image" in the tutorial now. Somehow only some devices run into this problem while others are working fine with flashing through ROM Manager recovery.
[Nexus One Android Development] BakaPhoenix:
Ever tried Blink? it work also on stock frf91 (with no root) but doesn't offer mail notification
[Nexus One Android Development] PSeeCO:
I think you're right but i can't use the fastboot metod for the problem i mentioned above!
[Nexus One Android Development] dolomiti7:
Maybe this will help:

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

=Manually boot into recovery and install it via adb. Also check if the downloaded files aren't corrupted.
[Nexus One Android Development] razers:
..facing the same issue.. :( Anyone!?

Thanks in advance.
[Nexus One Android Development] PSeeCO:
I tried that way yesterday, i got a FAILED (remote: not allow) error, as soon as i get home i'll try the flash_image way ;)
[Nexus One Android Development] dolomiti7:
Try flashing recovery manually like described in the old rooting thread. I added the neccessary links to my tutorial.
[Nexus One Android Development] daemondemise:
works flawless on US TMOB N1

this should be called the 5min Root Method. Freak'n genius. thank you!

US T-Mobile N1 fr91 +rooted
[Nexus One Android Development] PSeeCO:
Ok, i'm done with my recovery flashing, finally! I've used the "Alternatively try these slightly adapted steps (without remount of system partition, should work, I haven't tested it though):" but changing two lines:

3) In your terminal type "adb push flash_image /data/local/tmp/flash_image" and hit Enter

into

3) In your terminal type "adb push flash_image /system/bin/flash_image" and hit Enter

and

cd /data/local/tmp

into

cd /system/bin

All worked flawlessly ;) thank you all guys!
[Nexus One Android Development] dolomiti7:
Congratulations,

but your way will only work if sytem partition is still mounted in read-write mode. so it will work directly after rooting, but should not work after a reboot.

Anyway I tested now myself with /data/local/tmp as described in my tutorial and it worked for me. Why didn't it work that way for you? Did you get any error messages? In case other people run into problems with /data/local/tmp I added your way to the tutorial and I also switched the old method to alternatively.

Edit:

You were right, there was a small mistake in the commands. if you push it to data/local/tmp you need to run ./flash_image not flash_image. I guess that is why it didn't work for you and you had to go over system/bin. I corrected that in the tutorial
[Nexus One Android Development] black jack:
I'm having a problem. Everything is fine until the last step, when i finally enter "su" i get the message "access denied" and do not get any prompt from the superuser app on the phone.

I am on UK voda frf91 which i flashed to from the korean frf91. I still have the .35 h boot. anyone have any ideas? thanks:confused:
[Nexus One Android Development] jivemaster:
I am currently using blink, but it's no where near as powerful or customizable as trackball alert. So nothing exists that you can flash and is customizable from the settings screen?
[Nexus One Android Development] dolomiti7:
did you get the "#" prompt before? once you have that prompt you have root. if this doesnt work it is most likely that you have done something wrong after that point. and also do you see the superuser app on your phone when opening the apps drawer. in the worst case just try to reboot and repeat the procedure. keep an eye on possible error messages when entering the commands from the tutorial. if something strange appears post it here.
[Nexus One Android Development] thunder2k:
Just another feedback: it worked fine on my FRF91 USA stock Froyo.

Really thanks, I was not so happy to break my battery for rooting my N1

;)
[Nexus One Android Development] jivemaster:
I'm seriously surprised this is not a sticky. It is without a doubt the best way to root the nexus without harming your boot loader. Especially since no down grade or battery mod is needed. You don't even have to open the phone to do it.
[Nexus One Android Development] lemon seltzer:
Thanks for that. I'm still having some problems here though. After using this method to flash the recovery all was well for one night, I rebooted multiple times into amon RA recovery without problems. Then this afternoon I rebooted into recovery and found stock recovery again. Any suggestions? Something I may have done wrong? Should I flash again using same method?
[Nexus One Android Development] futango:
Did you run the last 2 commands? You should try flashing it again. Wouldnt hurt i dont think. The flash_image is already in the system. I havent had any problems here. been messing with different roms at least 6. Still get to recovery fine. I had the stock amon_ra 1.7.0.1 recovery first. Then i used the recovery customizer and change some images and progress bar and flash that one. had no problem redoing these steps. just do the

adb shell

su

flash_image recovery /sdcard/(name of recovery.img)

reboot recovery
[Nexus One Android Development] black jack:
thanks for the reply.

I don't remember any errors and I do have the super user app on the phone. I'll try it again when i get home and if it doesn't go through i'll have some more info later.

thanks again
[Nexus One Android Development] jivemaster:
I do have one issue - Android Commander reports I do not have root, and thus wont allow me to mess around in system, etc. I had a horrible time trying to copy over the wifi fix, and had to do it all from a terminal app on the phone.

I clearly do have root access, because I can accept app requests on the phone and root only apps work fine. Any ideas?
[Nexus One Android Development] pseudoheld:
this should definitely be stickied!

best root version working for all roms!
[Nexus One Android Development] krohnjw:
Worked to a T.
[Nexus One Android Development] UNICORN025:
how long after step

11. run "./freenexus"

12. toggle wifi

should you see this,

13. you should see something like that:

[*] Android local root exploid (C) The Android Exploid Crew[*] Modified by ak for HTC Nexus One

does it take a while or is it immediate?
[Nexus One Android Development] MonkeyMe:
hi everyone, just have a little trouble here

does anyone get the error ./freenexus: permission denied?

if so how would i resolve this?

thanks in advance!
[Nexus One Android Development] futango:
You should see it immediately.
[Nexus One Android Development] mortzz:
On US stock FRF91, whenever I try to run freenexus I get permission denied.

Any ideas?
[Nexus One Android Development] dolomiti7:
I just reinstalled US Stock FRF91 to test it again,

(EPE76->Update FRF85b->Update FRF91)

Build and Kernel: FRF91 2.6.32.9-27227-g3c98b0d android-build@apa26 #1

I ran into no problems. This is what I saw:

C:\android-sdk-windows\tools>adb shell
$ cd /data/local/tmp
cd /data/local/tmp
$ ls -l ..
ls -l ..
drwxrwx--x shell shell 2010-07-29 22:25 tmp
$ ls -l
ls -l
-rwxr-xr-x shell shell 1926944 2010-03-22 20:29 busybox
-rw-rw-rw- shell shell 26248 2010-07-22 10:20 su
-rw-rw-rw- shell shell 27688 2010-07-22 10:19 Superuser.apk
-rwxr-xr-x shell shell 11917 2010-07-26 20:00 freenexus
$ ./freenexus
./freenexus

[*] Android local root exploid (C) The Android Exploid Crew

[*] Modified by ak for HTC Nexus One
[+] Using basedir=/data/local/tmp, path=/data/local/tmp/freenexus
[+] opening NETLINK_KOBJECT_UEVENT socket
[+] sending add message ...

[*] Try to invoke hotplug now, clicking at the wireless

[*] settings, plugin USB key etc.

[*] You succeeded if you find /system/bin/rootshell.

[*] GUI might hang/restart meanwhile so be patient.

$ rootshell
rootshell
Password (echoed):freenexus
freenexus
#

I added 2 ls commands. If you do the same you should see exactly the same files with the same permissions. Especially

-rwxr-xr-x shell shell 11917 2010-07-26 20:00 freenexus

If you don't see that you have done something wrong before.

@UNICORN: just read carefully. You will see the message of freenexus immediately after you executed it. It will hang 3 seconds before it returns to the prompt. In this 3 seconds you will have to turn on wifi.
[Nexus One Android Development] mortzz:
Oh, sorry, I should have specified I'm on a Mac.

Edit: nevermind, I can't read.

This is what I get:

$ ls -l
-rwxr-xr-x shell shell 1926944 2010-03-22 20:29 busybox
-rw-rw-rw- shell shell 26248 2010-07-22 10:20 su
-rw-rw-rw- shell shell 27688 2010-07-22 10:19 Superuser.apk
-rwxr-xr-x shell shell 11917 2010-07-26 20:00 freenexus
[Nexus One Android Development] dolomiti7:
once you are in adb shell it doesn't matter if you are on a Mac or Windows or whatever.

It is the letter "L" not a One

ls -l

not ls -1
[Nexus One Android Development] mortzz:
Yeah, I'm a bit slow today lol.

Thanks for all the help, went through flawlessly!
[Nexus One Android Development] lemon seltzer:
OK cool I flashed again and it seems like everything's all good now. I'm wondering if using rom manager to reboot into recovery only may have screwed with it? I used rom manager's reboot into recovery option out of pure laziness before. I'm too noobish to know really lol but that's the only thing I can think of that I did differently this time. I reflashed, removed rom manager completely, and have had amon ra sitting there for one night and one afternoon so far.
[Nexus One Android Development] futango:
I think that might be. Use quick boot on the market.
[Nexus One Android Development] ilostchild:
QuickBoot is a good app to use to get into Recovery or bootloader realy quick and can easily place short cuts on home screen too
[Nexus One Android Development] dolomiti7:
Why not going the classical way: holding the volume-down button while booting?

or "adb reboot recovery" if the phone is debug-connected.
[Nexus One Android Development] ilostchild:
To do that you would have to turn off the phone then hold, this you can do with a touch and it does it on its one...i have always used quickboot

So i got couple questions lol...

I want to use a modified Phone.apk(cytowns) but i want to know if it will work with the stock rom or would i actually have to flash a custom ROM, i asked there but thats in the G1 threads, which pretty sure not many would know about.. so came back here and asked in the N1 threads..