yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] gom4381:
Can someone else who has more experience try this out and tell me I am wrong about this? I hope I didn't do it right. But I did it right the first time from frf85b stock. Then I rebooted and was able to flash custom kernels and everything. Can't do any of that anymore. I just was trying to get familiar with restoring the phone back to stock with no root. I don't want to unlock the bootloader(everyone should be specific when discussing these things as newbies like me get confused) and void the warranty. I found rooting the phone to be safe for me as I like living on the edge, not the bleeding edge. So if this method is lost I am mad. If not I am happy. I bought the setcpu app and can't use it. Well.... I may unlock the bootloader.

P.S.

Has anybody sent their phone in for insurance purposes and got back a Nexus One? From Assurion not Google or HTC. Like you dropped it in water or it fell and cracked the screen. I heard they may try to send out a mytouch 3g.
[Nexus One Android Development] Marine6680:
Ugh, I updated to FRF91 manually today just for the heck of it..... Now I can not downgrade my phone. I got the PASSIMG.zip and can not get it to downgrade. Not even using fastboot flash command. Anyone know how to downgrade?
[Nexus One Android Development] Rusty!:
You can't downgrade without an unlocked bootloader.

Or with a rooted phone and flash_image to flash the indivdual partitions.
[Nexus One Android Development] Marine6680:
I hope that someone somewhere knows something... For the life of me I can't get adb to see the thing in recovery. Been several hours of both trying, then trying to downgrade.

I have the full frf85b (82mb) ROM as well.... still no dice.
[Nexus One Android Development] Rusty!:
Does adb see the phone in recovery without the SD card?
[Nexus One Android Development] thomasgatt:
This tutorial is still valid for FRF91 ?
[Nexus One Android Development] JThreads:
+1 for me :D
[Nexus One Android Development] xanium4332:
+1 for me as well. Hopefully it's still possible, although I have a feeling the FRF91 update was probably released to fix the hole...

Now I'm annoyed at myself for not waiting...
[Nexus One Android Development] gom4381:
This tutorial does not apply for frf91. Don't update if you want to keep root and a locked bootloader.
[Nexus One Android Development] gom4381:
No adb unless the phone is on in a functional state. Like you have to be able to make a phone call for the phone to show up. No more recovery.
[Nexus One Android Development] Rusty!:
That explains 'security update' then.
[Nexus One Android Development] mlevin:
OK, I'm still on a stock N1 with FRF85.

If I want to root and KEEP root, but eventually get FRF91, what's my best course of action?

Root now with the steps listed in this thread, then update to FRF91?

If I install a custom recovery using the methods in this thread, while still on FRF85, then accept the OTA update to FRF91 (or apply it manually in the form of an update.zip), will that be OK? Or will that lose root?
[Nexus One Android Development] Rusty!:
Root now, flash custom recovery (very important) and install an repackaged version of FRF91.
[Nexus One Android Development] mlevin:
Cool, thanks for the quick reply. So is this (below) the one I want to flash after I root my FRF85 and install a custom recovery?

http://xdaforums.com/showthread.php?t=715799
[Nexus One Android Development] Rusty!:
Yeah that'll do it.
[Nexus One Android Development] gom4381:
Don't use the official FRF91 update because you will lose root and your custom recovery. Wait for a rooted version or use cyanogenmod. To answer your questions, no that will not be okay.
[Nexus One Android Development] J.L.C.:
I'm still leary of that one. The package contains recovery-from-boot.p and install-recovery.sh - which I "think" might install the stock frf91 recovery on reboot.

________________________

N1 w/ XDA App
[Nexus One Android Development] mlevin:
Hmm... so if it does, then I'm screwed, right? I won't be able to re-root on FRF91 (unless someone comes up with another clever approach) -- although I could *always* unlock the bootloader...
[Nexus One Android Development] Cal-El:
When I try to unlock the bootloader I get ???????????? devices at the fastboot devices screen. I have tried all the driver install options. Anyone else having this problem, I just want to unlock my bootloader but the other thread says 2.1 and my girlfriend (so nicely) installed this mornings 91 update. :mad: Any ideas anyone. Can I get back to stock 2.1 without an unlocked bootloader?

EDIT: Got it and I am stupid. Sorry for the clutter.
[Nexus One Android Development] J.L.C.:
Were you able to get back to stock 2.1 or FRF85B after the FRF91 update?

Or were you able to see your phone by ADB with it in recovery?

If so, please tell us how :)
[Nexus One Android Development] J.L.C.:
I'm not entirely sure. But, I do know that removing or renaming those 2 files is important for the "invisible" root method.

So if those files are replaced, with the FRF91 versions, I think it could mean problems for those of us who are currently rooted but with the bootloader still locked.
[Nexus One Android Development] Cal-El:
I just unlocked the bootloader and flashed the recovery img, then flashed the froyo rooter through the recovery menu. I should be able to just downgrade to 2.1 now right? Or is there a radio conflict? ADB worked for me right away, I just updated my SDK files and it was good from there.
[Nexus One Android Development] blisk:
I'm on 85B getting OTA update notifications on my nexus and already hit the update once (luckily you get 10 seconds to cancel) so I need to update before I somehow lose root on this through the update.

Has anyone tried this FRF91 rom?:

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

It's been stated by someone in there that I should be able to flash that and keep root but I wanted to know if anyone has done it yet.

Thanks.
[Nexus One Android Development] J.L.C.:
Ahhhh

Yeah, everything is different and anything is possible once you unlock the bootloader.

It's those of us who rooted without unlocking that this update is targeting I think.
[Nexus One Android Development] alexh3791:
So, does anyone have a repackaged (but otherwise totally stock) version of FRF91 that will allow us to keep root (using this tutorial), but still update?

I'm still running EPE54B (but downloading the FRF85B update since I've grown impatient waiting for the OTA), and I'd like to get up to date but still have root and a warranty (locked bootloader)...
[Nexus One Android Development] blisk:
Would like to know that as well. I'm trying a nonstock - with just some minor additions - FRF91 that should let me keep root. I'll let ya know how it goes.
[Nexus One Android Development] J.L.C.:
You can manually update to FRF85B, then use this method to get root and install a custom recovery. From there you have a lot of freedom, but I think updating to FRF91 might be risky (those recovery files I listed) if your bootloader is still locked.

That's where I am currently, and I think I will just stay with this configuration until CM6 comes out. It really looks like FRF91 was to target and "patch" this root-with-warranty technique.

I don't know if manually deleting recovery-from-boot.p and install-recovery.sh from the rooted update would be sufficient to keep this method working or not. Maybe, but I don't have the knowledge or the courage to find out :p
[Nexus One Android Development] alexh3791:
Thanks! Let me know. I've found one in XDA that claims to be what we want, but it apparently doesn't include Amazon MP3, which makes it a no-go for me...
[Nexus One Android Development] alexh3791:
I can understand; I don't want to ruin my chances of acquiring root while keeping a warranty either.

Unless someone can find (or build) a stock (yet patched for this tutorial) build of FRF91, I guess I'll just have to sit back and be happy with FRF85B...
[Nexus One Android Development] mlevin:
Couldn't I (or anyone) unpack that update.zip, remove those 2 offending files and then re-zip and re-sign? Since it doesn't matter what key is used, couldn't I just make my own key?
[Nexus One Android Development] J.L.C.:
Quite possibly!

I just don't know how to do that in order to try. I also don't know if those are the only offending files, there's also an "otacerts.zip" in the /etc/security/ directory.
[Nexus One Android Development] alexh3791:
As long as the locked bootloader will still accept it, I would think that would work, but I know nothing about how the flashing/update process works... I'd still be a bit nervous to be the first to try it.

I would really like to get all of this working, and if I can get FRF91 while keeping root using this method (to get the gMail security updates that FRF91 provides / to keep from accidentally installing the "bad" FRF91), that would be ideal.

(I guess I could always just suck it up and unlock my bootloader, but $530 is a lot of money for a "poor college student" if something happened to my Nexus that wasn't my fault. :D )
[Nexus One Android Development] Rusty!:
Even if it does, as long as you have root you can reflash custom recovery and remove/rename the 2 offending files.
[Nexus One Android Development] J.L.C.:
That's the problem though, this method of gaining root does not work with FRF91. So if you lose root, there is no reflashing recovery or anything else.

Once FRF91 is installed it appears the phone can not longer be detected by ADB while in recovery (which is the key for this root method).
[Nexus One Android Development] Marine6680:
We need to find a way to force a downgrade. There has to be a way for the repair techs to do it, so we should be able as well.
[Nexus One Android Development] mlevin:
I've been thinking about that and I'm tempted to just do it. There have been plenty of threads that would seem to indicate that HTC is being reasonable and is honoring the warranty for things that are clearly hardware-related even if the bootloader is unlocked.

Honestly, I'm more than halfway through the one-year warranty at this point (I got mine on the first day) and I haven't had any problems (knock on wood). I'd think that any physical defect would have made itself known by now.
[Nexus One Android Development] mlevin:
So basically, redoing steps 16-24 from the first post again, right?

So, on FRF85B, do the steps from this tutorial, then flash the re-packaged FRF91, the root package, optionally the "extras" package, then once on FRF91, go into the terminal, su, and re-install the recovery partition just in case the FRF91 updater killed it. Sounds right?
[Nexus One Android Development] alexh3791:
I agree. I got mine on March 28, and the only weird thing that I have noticed is the power button being unresponsive sometimes, but I have heard several reports that the FRF85B update resolves this. (I'm sitting in a coffee-shop right now about to load up FRF85B from EPE54B)

Just unlocking the bootloader and going the easy route to root is extremely tempting, but I'm still nervous about the warranty thing. I don't want to have to shell out tons of money if something goes wonky...
[Nexus One Android Development] Rusty!:
Pretty much yeah, that's what I was getting at, I believe the repacked FRF91 should leave the custom recovery alone, but as long as it's pre-rooted, it doesn't matter if it replaces it.
[Nexus One Android Development] alexh3791:
So, has anyone tried this method to get to FRF91 with success? (If yes, can you go into detail from start to finish on the instructions to do it so that everyone can follow your method?)
[Nexus One Android Development] Vlad83:
It appears the "security update" was to remove this loophole...

Has anyone flashed any FRF91 updates successfully without losing root?

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

or

http://xdaforums.com/showthread.php?t=715799
[Nexus One Android Development] cmstlist:
This one worked just fine from rec-rooted FRF85B:

http://htcpedia.com/forum/showthread.php?t=3033

I flashed the FRF91 file and then the root update.zip both from RA recovery. Skipped the addons. Root continued to work, and after several reboots the recovery has not been replaced. Go wild.
[Nexus One Android Development] apogee82:
I was able to gain root back after the FRF91 OTA by doing the following:

Boot into bootloader with PASSIMG.zip on my SDCARD

Let the PASSIMG.zip install and boot into ERD79

Reboot into Recovery and apply FRF85B via update.zip

Remove SIM card to prevent OTA FRF91 and boot into FRF85B

Follow instructions per post one of this thread

Reboot into custom recovery and Nand backup

Reboot into FRF85B and decline OTA FRF91

Tedious but I have root and custom recovery back.
[Nexus One Android Development] gom4381:
How did you get past step two?
[Nexus One Android Development] :
so passimg does in fact work right? thats what i thought.

@Rusty!

even though the PASSIMG.zip is older than the current build, as its an HTC repair recovery, it can be forced to flash
[Nexus One Android Development] J.L.C.:
Can PASSIMG.zip (ERD79) be used with an ATT phone?
[Nexus One Android Development] Marine6680:
So where can I find this PASSIMG? the one I have will not flash.

EDIT: the 79 build I have worked. Had to have it on a clean SD card.

Edit 2: failed after loading..."main is older"
[Nexus One Android Development] unchainedrssr:
Worked fine. IDK what happened to yours. I just used stock (non rooted) FRF91 and adb found my device w/o a problem.

I didn't flash anything but the recovery. (Amon RA's)
[Nexus One Android Development] unchainedrssr:
This version worked when I tried it. Make sure you have set up adb correctly and that you update to the latest SDK.

Good luck.
[Nexus One Android Development] Marine6680:
I can not get adb to see the device in recovery, it can see it any other time as it should though.
[Nexus One Android Development] gom4381:
I think with unchainedrssr you have the superuser permissions still valid from the first time you rooted the phone. I released all the superuser permissions after I didn't have root. The last guy I think is new to this and updated before reading this thread. If you guys release your permissions I would assume you would be in the same place as me. I know what I am doing now. I have done it before. It is not working. I still have superuser icon but I cannot get the phone to show up in adb while in recovery mode. I AM SURE OF THIS! And please don't post if you are not sure.
[Nexus One Android Development] unchainedrssr:
I completely lost root. I was 100% back on stock aside from the unlocked bootloader.

You could be right though. If there is some way to have superuser permissions without nothing requiring su permissions working. (Clockwork, Shoot me, Set CPU, Nexus One Torch, Quick Boot, etc.)

I haven't heard of su remnants before, but okay. I AM a n00b. :p

I guess I should DM some devs to see if I was way out of line on this. (being that you asked me not to post if there is a possibility that I could be wrong)

I am standing behind the OP on this, though. With the testing that I have done, and with the steps that I have followed, everything works as it should. :)

I'll post any input that I get. Until then, keep testing and posting your results. It can only help move forward.

We all learn from each other's mistakes, misinformation, and results. ;)
[Nexus One Android Development] J.L.C.:
The methods in this thread are for gaining root without unlocking the bootloader.
[Nexus One Android Development] gom4381:
I was not trying to be rude. I apologize for that. I was frustrated with the amount of time(5 hours) I have put into this and not have it to work. I understand the remnants part-It strikes me as weird also. The superuser icon does not disappear no matter how many wipes you do. My bootloader is locked and yours isn't. That is why you are able to do what you want because your bootloader is unlocked which voids the warranty and allows you to install different mods. I have tested for hours trying to get this to work-I might unlock the bootloader. I am a noob also but I have some hacking experience if having a N900 counts-before the pr1.2 update ;) So to make it clear or get more help:

(P.S.) PASSIMG.zip does not work. Updating the regular way will void this way of rooting-it killed my root

1. Someone try this method with locked bootloader from the frf91 update that was released and post results.

2. If the OP could comment, I'm pretty sure he would know in 5 minutes.

3. Someone create a new way of doing this

4. Someone finds out how to downgrade.
[Nexus One Android Development] nomadism:
This method also worked with me. Got stuck in the middle, but not because the method was wrong, but because I made stupid mistakes (typos, forgetting to insert the SD card etc...)

PS. Anyway that we can update to FRF91 without losing the root access?
[Nexus One Android Development] mlevin:
I am still on 85 and had planed on rooting today. I got OTA 91 last night but did not apply it. Am I gonna have problems when I boot into recovery now that 91 is already downloaded and ready to be applied?
[Nexus One Android Development] gom4381:
You might. If you can don't install. You will lose your recovery and root. Look for another rooted frf91 and then install. Otherwise you will be like me. No root and contemplating unlocking bootloader.
[Nexus One Android Development] gom4381:
Use a rooted version of frf91.
[Nexus One Android Development] mlevin:
I didn't apply 91 but I keep getting prompted that it is ready to install (I keep saying "install later"). But I'm afraid that because it is already hanging out in the cache partition, the next time I boot into recovery it is just gonna apply itself before I get a chance to root under 85.
[Nexus One Android Development] Rusty!:
Custom recoveries wont install an OTA update.
[Nexus One Android Development] unchainedrssr:
:eek: No way!

lol

Yeah, I know. :rolleyes: But the method of gaining root this way from stock still applies.:)

Yes, I know I have other options with an unlocked bootloader, but it really doesn't matter.

This method has nothing to do with the bootloader other than avoiding the need to unlock it.

I sincerely hope that everyone is able to get their devices rooted and working properly. I look forward to having more and more people testing and contributing to the Android community. Don't give up, and share your experiences and thoughts. Right or wrong, it all helps others following this thread.
[Nexus One Android Development] dasbooter:
Well I think I have read almost all 31 pages or so of this thread. I am a n00b for sure, in fact my first cell phone ever :eek: and I am pretty old but I am not new to modding (jtagged xbox, hacked psp, linux based sat tuner, running linux distro as main OS etc etc). I really like to have some at least basic understanding of what i am doing so I have been lurking around here. This exploit seems to have been patched pretty fast which is a little unnerving.

Can somebody confirm I am generally following along here.

Steps 1-5 are getting your N1 seen by your computer with the SD card out while it is recovery mode. The loop script does while the value returned is 1 keep doing adb devices(look for devices till you find? or maybe this is a busy work script which is part of the exploit?)

Steps 6-8 getting the sd card mounted

Steps 7-15 The real meat of the exploit. Get the files onto the system and run them.On the next boot you will have root permissions. I am not sure about the "limited capabilites" thing though. In linux if you are root you can do anything. If you sudo su or similiiar then you get to root but this condition is only valid until you reboot. So maybe it is you have to move on to the next steps in order to keep permanent root?

Steps 16-24 With your new found root capabilities you can install a custom recovery.I dont know what this is for sure but a lot of OS's have some way to restore back to original in case you fubar your system.The system recovery sits on the rom waiting to restore a backup of the original on the sdcard.I dont know why you need a "custom recovery" though unless it is the only way to install a complete custom rom. I am really confused at this point as in the thread some say you can stop here if you want to run stock.

Can you clarify:

1)you have flashed your custom recovery and you now have the option to do stuff but you really cant do much anyway after you reboot.You will keep this option as long as you dont overwrite the system recovery with a stock update/rom.

or 2)you can move on and flash a custom rom that somebody made that will give you full lasting root permissions and therefor do lots of stuff...get access to parts of n1 you didnt have b4 and run programs that you couldnt b4.You will keep all of this as long as you dont overwrite with stock.

or 3)you can install the latest cyanogenMod a custom rom with all the bells and whistles that tried to improve/correct issues with froyo 2.1.You will keep this...dont overwrite with stock.

Lastly there is the radio. From what I have read this is device bricking territory so what are you supposed to do if you want to go the cyanogenMod method. I am on FRF85B with baseband version 32.36.00.28u_4.06.00.12_7. Do I have to flash the radio I saw in the wiki directions at the Cyanogenmod site.

I think I will stop now sorry for the length of the post:o
[Nexus One Android Development] Sold4JC:
I have a stock Nexus One with locked bootloader that I updated to FRF91 from FRF85B before I saw this thread. I tried to run the passimg.zip that I downloaded from androidtechnical without any luck. I renamed the file I downloaded passimg.zip and put it on the root of the SD card, then booted into bootloader and the file was not flashed successfully. I'm still on FRF91 and it appears I lost my opportunity to gain root access without unlocking the bootloader. I hope this is informative and if I did anything wrong please let me know and I will try again.

Thanks
[Nexus One Android Development] apogee82:
Try this one shipped-roms.com/shipped/Passion%20(Nexus%20One)/PASSIMG_Passion_.zip

It worked for me.
[Nexus One Android Development] vsc:
It would seem I can confirm this file works....

For clarity I have a locked bootloader and (had) FRF91. Renamed the file to PASSIMG.zip, dropped it into the root of the SD card and ran a recovery. Note that I did not clean off the SD card.

Update: And just used "universal update to FRF85B.zip" to get back to FRF85B

Update2: Followed the process on the first page of this thread... Rooted.
[Nexus One Android Development] jnwhiteh:
Where did you get the 'universal update' to 85B? Any chance you can point me in the right direction?
[Nexus One Android Development] jnwhiteh:
I've just tried to downgrade to ERD79 using the linked file above (MD5: bef86698cafc88ca03fff5758571d9d6) but during the 'Checking' step, it gives me:

Main version is older!

Update Fail!

Do you want to reboot device?

My bootloader version is:

NEXUSONE PVT SHIP S-ON

HBOOT-0.33.0012

MICROP-0B15

TOUCH PANEL-SYNT0103

RADIO-4.06.00.12_7

Dec 17 2009, 13:05:23

Are you on a different bootloader for some bizarre reasons?
[Nexus One Android Development] cmcm:
I am on a non-rooted but unlocked bootloader FRF91 and this file does not work for me. It gives me the error "Main Version is older! Update Fail!"
[Nexus One Android Development] jnwhiteh:
Why are you doing any of this if you have an unlocked bootloader? Just flash a custom recovery image and you can install whatever you want, or am I missing something?
[Nexus One Android Development] vsc:
Here,

h**p://www.megaupload.com/?d=WMCZIIIB
[Nexus One Android Development] :
If you have any other questions, post here or pm me
[Nexus One Android Development] jnwhiteh:
Thanks, I'm downloading it now.. but it seems I'm unable to downgrade my device (or I'm doing something wrong). Any chance you can check your bootloader versions for me?
[Nexus One Android Development] Sold4JC:
Thanks a ton. This did work for me and I was able to downgrade to Firmware 2.1 Build# ERD79 from 2.2 FRF91 with locked bootloader.

Thanks