yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] jnwhiteh:
Can you please confirm if your bootloader version differs from mine for some reason? I'm using the same file on a 100% fresh SD card with nothing else on it and I'm getting 'Main Version is older!' still..
[Nexus One Android Development] jnwhiteh:
I can go to EPE76 on Shipped-roms. I'll see how the rest of the process goes and update this post. If ERD79 isn't working for you, let me be the guinea pig real quick =)
[Nexus One Android Development] mlevin:
Update: I rebooted into recovery and luckily it did not apply the already downloaded 91, so I think I'm safe for now as long as keep rejecting it (until I find the spare time to root, which I thought I'd have today).

I also noticed that in the stock recovery there's an option to wipe the cache partition. Would this simply have the effect of deleting the OTA that was already downloaded (but not yet applied)? I'm thinking this would just get rid of it, and if I then shut off my network connection temporarily, I'd avoid re-downloading it, right?
[Nexus One Android Development] jnwhiteh:
Rooted and booted. Smooth as silk. If you can't get to ERD79, go to EPE76 instead.
[Nexus One Android Development] uoY_redruM:
If I'm already on 91, I'm pretty much SOL, right?
[Nexus One Android Development] stealthopts17:
not sure what i'm doing wrong, but when I get to the step that says to press "ctrl-c" command prompt asks me "Terminate batch job (Y/N)?"

any ideas on why this is happening after performing that step?
[Nexus One Android Development] dasbooter:
Well thanks for being patient :) I was already thinking out my apology for asking such questions in this thread but hopefully your good answers will benefit others as much as they benefited me.I am going to review the tuts in the Q & A forum one more time then go ahead from the beginning.

I see some others are asking and I also want to know if there are any repercussions or extra steps to having pulled in the FRF91 update but having not applied it, by choosing the "apply later"option. Will I have to delete these update files or anything before going ahead.

It is kind of interesting watching the drama play out it seems others who updated to FRF91 have been able to flash back to older roms then do this process I think with there bootloaders still intact. If this is the case and FRF91 was meant to stop this it probably is a pretty shoddy piece of electronic counter-warfare.

All this so I can change my notification bar to black so it doesnt leave a ghost image (like burn in) and keep my warranty... dumb
[Nexus One Android Development] r0ark:
Just wanted to confirm that downgrading from FRF91 to EPE76 then upgrade to FRF85B works! This is for people (used to be me) who could not downgrade to ERD79 and/or get the message "Main version is older!"

Get EPE76 PASSIMG from Shipped-roms.

h**p://shipped-roms.com/shipped/Passion%20%28Nexus%20One%29/

Get FRF85B Universal from this thread, a few pages back.

good luck! :)
[Nexus One Android Development] gom4381:
You my friend are 'THE' MAN! It does work. I am so happy! Happy, happy, joy, joy!!!
[Nexus One Android Development] sosquidtaste:
It's supposed to happen, but just wasn't explicitly spelled out in the instructions. In case you haven't done so yet, go ahead and choose Yes :]
[Nexus One Android Development] Jizzle74:
When i get the loop part and i connect my phone to the computer and power into recovery i get a message that says "daemon not running. starting it now" But i never get an htc devices message like it states in the instructions. Can someone please help?
[Nexus One Android Development] Marine6680:
Well, I tried several PASSIMG files, none worked; rooting the normal way I guess. This did work for me on my GF's Nexus, she is playing with it right now. :D
[Nexus One Android Development] Constrabus:
Make sure you have working adb while the phone is booted normally.

For help check the link in the prerequisites.
[Nexus One Android Development] Espike:
Worked 100% for me. Started locked on OTA FRF91. PASSIMG to EPE76 then universal update to FRF85B and hack.
[Nexus One Android Development] Constrabus:
Would you mind pointing me to the passimg you used or where you got it from so that I can add FRF91 instructions in the OP?
[Nexus One Android Development] stealthopts17:
after a lot of trial and error, i finally got everything to work. i was originally running FRF91. i reverted back to EPE76, then applied the FRF85B universal update.

for some reason, i could not get steps 19 - 24 to work for me. instead, i did the following:

after performing step 18

type "flash_image recovery /sdcard/recovery-RA-nexus-v1.7.0.1.img" press enter.

type "reboot recovery" press enter. your phone will reboot at this point.

after the phone reboots, turn your phone off. you can then use your new recovery.
[Nexus One Android Development] yuhinso:
Hey guys, does this method applies on frf91? OTA has come to my phone.

Cheers
[Nexus One Android Development] sogo87:
I have read a lot of comments on the guide of how root the nexus without unlocking the bootloader and searched in other places but couldn't find a final answer to my question...

I've got at&t version nexus unrooted and I updated it to FRF91 OTA.

can I use this guide to root it without unlocking the bootloader?

If I can, how do I do it? some people wrote that I need to use Passimg.zip

but I think It's for T-mo version only because at&t's version doesn't have the erf79 (I hope I wrote it right).

anyway I'm really confused :confused:. can someone please explain?

thanks

P.S - sorry for being a noob :D
[Nexus One Android Development] Vonwesen:
hello! i'm blocked..

Sorry for my bad english...

i put my sd card (Sandisk 8go SDHC) in the slot, when the phone is on recovery...

"click"

i press power + vol + for enable recovery option...

i clic aplly update sd card...fail... normal at this step...

and when it's time to push flash image and update

CMD said : error: device not found

so, just for checking, i typed "adb devices"

==> List of devices attached

and nothing after...

So i'm blocked at this step...

juste in case... when i type "loop":

"c:\Android\tools>GOTO TOP

c:\Android\tools>adb devices

List of devices attached"

looping...again and again...

is it normal? thx for helping me!
[Nexus One Android Development] ExtraDas:
For those of you who have rooted using this method (as have I :P) and keep getting nagged about updating, just flash to a rooted 91.

The one I used is this

h**p://xdaforums.com/showthread.php?t=714184

Very good ROM, two options; black bar or normal and so far I haven't had any issues with it. It's deodexed so skinning it should be cake and it's generally stock with only a few very useful things already built in.

Do a NAND back-up prior to it so you can revert to what you have now if you don't like it or have problems.

That took care of the update pop-up as well as black status bar for me :P
[Nexus One Android Development] dasbooter:
So I am now rooted using this method from FRF85B. I had pulled in the FRF91 update but Never applied it. I was a little worried it would get applied somehow while going thru this procedure. I did a factory reset from settings-->privacy and when I saw the android dude unpacking the box, I freaked and removed the battery. I then rebooted the phone with the volume button down option and did a wipe from there also. Then I rebooted the phone went to system updates and checked and it said I was up to date but I still had FRF85b which was what I wanted. I also of course didnt set up the wireless so it was impossible for the updates to be pulled down again. So I dont know if all this was necessary especially removing the battery ... the little adroid guy was probably only restoring the system but nonetheless I have gotten root with a locked bootloader and have flashed the RA system recovery. I have now backed up the nand and I am hoping somebody can point me from here.

I am still new to the phone and dont need to do a bunch of stuff right now I want a stock rom I guess with just root and I need to change/get rid of the stock notification bar b4 I get anymore burn in from it.

Thanks a bunch and hopefully this helps out you guys who haven't wanted to try this procedure with the new update sitting on your phone waiting to be installed. :D
[Nexus One Android Development] Vonwesen:
ok sorry... drivers problem... done.
[Nexus One Android Development] _Sri_:
Hi, I am stuck with the same issue. I am running, Windows Vista. Can you please let me know what changes you made?

Regards,

-Sri
[Nexus One Android Development] Amdathlonuk:
I can't seem to get past the first step :(

I have a brand new N1 as my other had dust under the screen.

However my other was rooted and working fine on ADB.

This one is just not recognised when I type 'loop' the screen just keeps searching.

Can anyone help?

I'm on stock FRF91 update.
[Nexus One Android Development] Marine6680:
I'm not sure it works for everyone. I tried several PASSIMG files, all different sizes and versions, nothing; even the ones people linked and said worked. I am not sure why it did not work though, maybe that "universal" 85b update file flashed a new recovery version as well; the file was 85mb in size.
[Nexus One Android Development] dasbooter:
Hmm I just went to download this and apparently where on version 3... wonder whats up ;)
[Nexus One Android Development] cmstlist:
Suggesting to original poster or moderator: Update thread title to reflect that this method does *not* work with FRF91, and update the first post with that info too.

Add a link in the first post to this thread for questions about downgrading if you have FRF91 already:

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

And there are several threads about upgrading an already-rooted N1 with custom recovery to FRF91 without losing root.
[Nexus One Android Development] Midget010:
Did you have to wipe anything to update?

Also, does this still mean that the unlocked padlock won't show up when I boot?

Thanks.
[Nexus One Android Development] Vonwesen:
ok my problem been simple...

the drivers of the nexus one doesn't worked...

just test that :

windows + r

type : devmgmt.msc

search the "nexus" or "nexus one"

and install drivers...(let windows search in your android folder)

if you did'nt have the drivers==> go on sdk and download the package !

I hope help you ;)
[Nexus One Android Development] Amdathlonuk:
Okay, I've got a bit further after sorting out my drivers also.

However a new stumbling block and I've been on this for hours!!

Whilst trying to perform the last section of pushing the update.zip to the card I get

Finding update package..........

Opening update package.........

Verifying update package.........

E:failed to open /sdcard/update.zip (no such file or directory)

E:siganture verifiaction failed

Installation aborted

Can I also ask for clarification on the instruction below? Why would I push the OTA.zip to the SDCARD and change it to UPDATE.zip?

10) In your terminal type "adb push ota.zip /sdcard/update.zip" and hit Enter

Any help appreciated as I'm stuck. :confused:
[Nexus One Android Development] stealthopts17:
I came across the same problem. it should say ota.zip
[Nexus One Android Development] Constrabus:
No it shouldn't.

The tutorial is perfect.

The purpose is to replace update.zip with ota.zip by renaming it while flashing.
[Nexus One Android Development] nicdub:
Does anybody have a link to the universal 85b zip? The Google link is showing a file not found error. Trying to get back to 85b by flashing the ere27 then the 85b since I accidently updated to 91
[Nexus One Android Development] ExtraDas:
I did wipe before the update as that's always a cleaner install but I'm not sure if you have to. Bootloader is still locked so no change there. If you have your phone set-up to back-up your apps too, they all download back automatically.

Again, really make sure you do NAND back-up, just in case something happens that you don't like, should you chose to do this. As this doesn't unlock the bootloader, doing the NAND restore puts you back to exactly where you were...85b rooted and all.
[Nexus One Android Development] Amdathlonuk:
Okay, confused again....... I appreciate the help so far but I'm stumped, I keep getting so far and then hit another issue.

It says on your terminal type 'su'

However I now have FRF85B installed but no terminal available, I get the files across via adb and it all works when I hit the enter at the crucial stage, however when I boot into the system there is no terminal?

Please god help......otherwise I might be rooting via the old method I think :mad:

NEVERMIND: GOt it, but I think it should be noted that when typing 'adb shell' in terminal you get an 'access denied' message, however everything still seemed to work.

It wasn't flawless though and VERY frustration, I kept having to uninstall and re-install my USB drivers.....odd.

Thanks for the tutorial wouldn't have got where I am without it.
[Nexus One Android Development] cmstlist:
OTA.zip is a file that the N1 recognizes as a signed update.zip but doesn't contain the root hack. Then you push a second unsigned update.zip to replace it, and the N1 gets tricked into applying root. Bait & switch.
[Nexus One Android Development] mlevin:
Worked like a charm from FRF85B! Now I need to install a rooted FRF91 and I'll be all set...

Many thanks for the tutorial!

I did notice that a few times the "su" would fail and I'd have to try again even after I said "allow," but other than that it worked fine.
[Nexus One Android Development] RashaMatt:
I'm assuming this method will not work on FRF91?

(stock Nexus One direct from Google, using AT&T).
[Nexus One Android Development] _Sri_:
Hi, Thanks for your help.

I realized my mistake. I was on FRF91 :((. I downgraded it to EPE76 and in the process lost all my messages, bookmarks, apps :((.

Once i was on EPE76, I upgraded to FRF85B and then everything worked just fine as per the instructions :-)

B/w while i was on FRF91, I never got the "add devices" to recognize my phone in the recovery mode. Downgrading to FRF85B solved this problem.

I now have recovery-RA-nexus-v1.7.0.1 and waiting for CM 6 :-)

Regards,

-Sri
[Nexus One Android Development] bigasluna:
Hi, just made all correct and have FRF85B on board.

I'ts possible to solve the continuous OTA to FRF91 show message?

If i'll flash a custom rom FRF91 based, i'll solve?

Thank you.
[Nexus One Android Development] Constrabus:
Could you link me to what you used to downgrade to EPE76 and then upgrade to FRF85B so that I can add instructions for FRF91 rooting? Thank you.
[Nexus One Android Development] mlevin:
I think you can solve that by installing a rooted 91 and clearing the cache partition. At least that's what I'm about to try...
[Nexus One Android Development] bigasluna:
Ok, can you tell me if you lost root permission?
[Nexus One Android Development] clubs07:
thanks Constrabus for the great instructions. It worked like a charm at the first try. I used a battery I bought off ebay which came without the tab so no tempering with the original battery.

Also the same rooted FRF91 on the below link worked with no problems for me too after getting my Nexus 1 rooted on FRF85B with the instructions.
[Nexus One Android Development] bcpk:
These instructions worked perfectly for me, thank you so much!
[Nexus One Android Development] kos888:
I'm a complete newbie to this (as evidenced by this being my first post) but I managed to root my FRF91 following these steps. Quite tedious for sure but worth it!

Also, to all the other Mac users out there - not sure if it was because I had USB debugging off or what, but I had to create the loop shell script outlined earlier and run it in order to get adb to recognize the N1 in recovery mode.
[Nexus One Android Development] mlevin:
Not sure if this is "normal," but I can't "su" until the phone is fully booted into the launcher screen.

If I try to do an "adb shell" and then "su" while the phone is booting (showing the animation screen), I get errors:

C:\Windows\system32>adb shell
* daemon not running. starting it now *
* daemon started successfully *
error: device not found

C:\Windows\system32>adb shell
$ su
su
[1] Segmentation fault su
$ su
su
[1] + Stopped (signal) su
$ su
su
[2] Segmentation fault su
[1] Segmentation fault su
$

But after that it works fine:

$ su
su
#

Is this happening to anyone else?

Furthermore, even after the phone is fully booted, I can't do an "adb remount" at all:

C:\Windows\system32>adb remount
remount failed: Operation not permitted

C:\Windows\system32>

However, doing it in the shell works:

C:\Windows\system32>adb shell
$ su
su
# mount -o rw,remount /dev/block/mtdblock4 /system
mount -o rw,remount /dev/block/mtdblock4 /system
#

Finally,, I noticed that there's now an "adb root" option (the last time I rooted a phone was shortly after the G1 came out), so I never knew about this option. But I get an error using it with my newly-rooted Nexus One:

C:\Windows\system32>adb root
adbd cannot run as root in production builds

How can I get my Nexus One to behave like a "fully rooted" device?

Can anyone offer any insight and/or advice?

Thanks!
[Nexus One Android Development] Rusty!:
You need an insecure boot.img for adb remount to work.
[Nexus One Android Development] mlevin:
Thanks. After installing that root package from http://htcpedia.com/forum/showthread.php?p=67676#post67676, everything was fine.
[Nexus One Android Development] mlevin:
Nope, everything worked great!

Here's what I did:

Installed the FRF91 package from http://htcpedia.com/forum/showthread.php?p=67676#post67676

Without rebooting, installed the root package (also from http://htcpedia.com/forum/showthread.php?p=67676#post67676)

Using the Amon RA recovery menu, wiped the cache partition

Using "adb shell," did a "mount /system" and then renamed /system/etc/install-recovery.sh and /system/recovery-from-boot.p by appending ".DISABLED" to the filenames

Rebooted into Android

Confirmed that I was on FRF91 and that I was still rooted (I did)

Still got the "update available" alert once

Rebooted into recovery to confirm that I still had Amon RA (I did)

Rebooted into Android again and so far, haven't gotten that "update available" anymore
[Nexus One Android Development] dtosun:
Anybody try it for FRF91 unroot and locked?
[Nexus One Android Development] what25:
The process worked. I have a rooted N1 FRF83 without unlocking the bootloader. Sweet.

I like the ninja icon for the Superuser app. :)
[Nexus One Android Development] MishFdM:
Wich kind of SD did you use ?
[Nexus One Android Development] LordPhong:
I'm on FRF83. I already wiped my phone by accident. Then I reenabled the debugging mode but I'm still getting this permission denied. I'm using a paper slip instead of filing down my nexus. So, I pull the paper slip after ctrl-c and before vol+.

do you guys always get this message when selecting "apply sdcard:update.zip"?

E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)

i keep getting:

failed to copy 'flash_image' to '/sdcard/flash_image': Permission denied
[Nexus One Android Development] Constrabus:
If it helps, I used an A-Data 16gb Class 6. Although, I think you can do it with any, with the process in the first post.
[Nexus One Android Development] MishFdM:
If I understand, that is correct and you can go on with procedure.
[Nexus One Android Development] Constrabus:
To do a check, does it still say "recovery" if you run "adb devices" in the terminal after pulling the slip?

Also

I don't get that message.

I've only gotten that message when the SDcard was physically removed.

Make sure your SDcard is inserted properly.

Hopefully that paper slip didn't break your SDcard slot.

or

Maybe there is still a piece of paper stuck in the SDcard slot, blocking the contacts.

I would be careful with that paper:

1) Theres no way to be sure if it is working properly

2) It could damage the slot.
[Nexus One Android Development] MishFdM:
Thanks for your tutorial.

I don't understand exactly how to modify battery's tab
[Nexus One Android Development] LordPhong:
the slot is not damaged. I checked it by going into the OS and was able to see files in there. my device still can't seem to mount the sdcard when I try to apply the update.zip.
[Nexus One Android Development] :
a paper slip will not work. you must physically enter the sdcard. i believe the click of it entering the sd slot causes it to mount. ive tried with the slip many times and failed each time. filing down the battery lip and entering the sdcard after adb was recognized allowed me to root immediately
[Nexus One Android Development] LordPhong:
I do know about the click causing a mount. So what I did was insert the paper slip then the card so that it doesn't click. After that I carefully put the battery in. It still didn't work.

Frak it. Off goes the knob holding the sdcard and it works. I've wasted about 45 minutes with the paper slip. Someone should mention that in the first post so people don't repeat what i did. (if it's already said somewhere then I didn't do due diligence and search.)

Nevertheless, I'm rooted. :D
[Nexus One Android Development] Constrabus:
I've updated the initial post with a picture I threw together to further explain where to make the cut on the battery.
[Nexus One Android Development] Constrabus:
Congrats!! Glad it worked out.

Yes, I've been updating the first post every time someone has trouble with a certain section.

I added a picture and to avoid the paper slip method.

You do realize though that the guide said to use the battery trim method.

Shame on you! lol
[Nexus One Android Development] LordPhong:
Yes, I thought I was slick. hahahahaha
[Nexus One Android Development] navillos:
on the bottom front of the battery there is a small lip of plastic. just slice that little bit off and it works great the card goes in smooth. all you hear is the slight "click". i have to say this is the easiest rooting process i have ever done a htc phone. i used my good ole kingston 2gb micros SD (not SDHC just SD might be the issue with some of you guys) and it was still set up as a gold card for my old htc magic. everything went as smooth as a baby's ass.
[Nexus One Android Development] Tasqa:
You are awesome, i just got my nexus yesterday and wanted to root it.

And now I've done it without unlocking boot!!

you really made my day!

Thanks ALOT!
[Nexus One Android Development] lostinatlanta:
ROOTED!!! Thanks to the OP!

And I should mention, for everyone debating and trying to get around the whole "modding-the-battery" thing, just do it. It doesn't look as bad as you think it's going to. (In fact, with a sharp enough blade, it's flush, not even noticeable.)

Oh, and I kinda recall someone saying that they removed the black tab ON THE PHONE above the card!?!? Please guys, I believe this type of "phone hardware" mod WILL void your warranty, bootloader still locked or not. Mod the battery, not the phone.

Thanks again to the OP and his contributors!!!
[Nexus One Android Development] torchedlh:
So this is a very naive question....but is flashing a custom ROM a requirement of completing "root"? If I stop after flashing the Amon's recovery I can still flash whatever mods and use apps that require root (eg titanium backup etc)? I assume I'll have to install superuser?? Thanks
[Nexus One Android Development] what25:
The 4GB one that came with the phone.
[Nexus One Android Development] ziekrage:
I originally stopped at step 15) on FRF83 to get simple root, but I now want to go whole hog with custom recovery to avoid accidentally installing the FRF91 OTA.

This may be a non-issue, but in my nexus, /system is mounted from mtdblock3 instead of mtdblock4 (thats where my /cache comes from). Is this a problem?

Do I just remount /system with rw regardless of where it comes from, or was the intention of step 19) to mount the /cache partition (mtdblock4) under /system?
[Nexus One Android Development] kos888:
Worked for me!
[Nexus One Android Development] _Sri_:
Hi,

Apologies for the late reply :(.

I used the instructions from the following link: hxxp://xdaforums.com/showthread.php?t=717870

Thanks a ton for your help :-).

Regards,

-Sri