yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] Midget010:
Thanks a lot! I tried the black status bar, but it didn't work :S But the stock one worked great.

Thanks for your help.
[Nexus One Android Development] mlevin:
Portable Hotspot no longer working

Now that I've upgraded to a rooted FRF91, my portable wifi hotspot no longer works.

Anyone seen this problem?

Any ideas how to fix?

It was working when I was unrooted and on FRF85B.

What could have messed it up?

I rebooted the phone multiple times.

Also, I thought the WiFi symbol showed up on the status bar when tethered. It doesn't seem to do that now.

I can sometimes get it to connect to my XP machine with an "open" network but never WPA2-PSK :(
[Nexus One Android Development] kos888:
No problems here. I just checked and the hotspot works fine with wpa2 authentication
[Nexus One Android Development] Constrabus:
Updated to include information and links on rooting FRF91, T-Mo and AT&T!
[Nexus One Android Development] mlevin:
Hmm. My phone has become quite unhappy. In the last hour or so it has been completely freezing up such that I have to take the battery out. Grr.

Does your regular wifi icon show in the status bar when you have the hotspot on?
[Nexus One Android Development] kos888:
No, I get a blue wifi icon instead.
[Nexus One Android Development] alexh3791:
Success!

I followed the main root instructions in this thread with only a bit of difficulty (caused by my own stupidity / I deleted a file from the SD card before it was appropriate to do so), and I used the FRF91 build above to update and root to FRF91 from FRF85B.

Thanks to everyone who made this and helped me find an appropriate FRF91 build! I can't say it enough; you guys rock! :cool:
[Nexus One Android Development] mlevin:
Yeah, I started getting crazy stuff in the logcat and then it would freeze -- threads hanging, a message about the CPU being pegged, etc.

I nandroided back to a snapshot of about 24h ago and everything seems OK so far. I must have done something wacky today...
[Nexus One Android Development] cchhk:
Anyone Stuck in Step 13/14 like me?

When I try to apply sdcard:update.zip,

it keep saying "E:signature verification failed"

Does anyone know how to fix it?

P.S. its not saying there is no such file tho.

Thank you!
[Nexus One Android Development] cmstlist:
There are three stages that have to be each done correctly in terms of update.zip.

1) The first time you try to apply update.zip there must be NO update.zip on the card.

2) The second time, after you've pushed ota.zip to /sdcard/update.zip, this has to be the file your phone sees when you *first* apply sdcard:update.zip... *but*

3) You have to replace it with the second update.zip *after* the yellow bar appears and *before* it actually starts following the instructions in the first file. Bait and switch!

And if this sequence fails, then you have to remove update.zip from the SD card again, and go back.
[Nexus One Android Development] lukbeat:
EPE76 to frf85B

Hi,

I am back from frf91 ota to EPE76 by applaing passimg.zip. My question is how can I move to frf85B ? I've tried to download universal frf85B, change name to update.zip and go to recovery, but I only see exclemation mark. Please advise. Thank you.
[Nexus One Android Development] hmanxx:
Sorry I am very confused even after reading all the pages..

Question for FRF91 OTA-non rooted users

1) Downgrade to OEM first ship rom.

2) Upgrade up to FRF85B and perform the rooting procedures are listed on 1st post.

Question 1: Isnt this rooting up to FRF85B ? and not possible to apply further update to RFR91 and maintain FRF91 FW.

I find FRF91 is better than RFR85B..there are more than just security patch.

Q2: If no custom recovery ROM is applied..just root, what benefit can we have?

Q3:After applying custom Recovery ROM. Can it still be fully recovered to stock non rooted ROM..including restoring stock recovery ROM.
[Nexus One Android Development] lukbeat:
I've found answer:

This guide will help you manually flash an update image to your Google Nexus One.

1. First thing you have to do is rename your update file to update.zip.

2. Copy the update.zip file onto your microSD card.

3. With your Nexus One powered off, hold down the trackball and press the power button.

4. You’ll be booted into a white screen with three Android robots on skateboards. Select “Bootloader“

5. On the next screen, select “Recovery“

6. Your phone will reboot, giving you a picture of the Android robot and an exclamation point inside a triangle.

7. Now press the power button and volume up button at the same time. It could take a couple of tries.

8. Now (using the trackball this time) choose “Apply sdcard:update.zip” and let things run their course.
[Nexus One Android Development] mlevin:
Once rooted at FRF85B, you can certainly upgrade to FRF91 (I did). You just can't install the OTA version. Install a re-packed version and you'll be just fine. After rooting on FRF85B according to the instructions in the first post, follow the steps here:

http://xdaforums.com/showpost.php?p=7075094&postcount=379
[Nexus One Android Development] Jizzle74:
im having a big problem. Someone please help. When i get to the loop step, no matter what i do i get this message (adb is not recognized as a internal or external command) i never got this message before and i have no idea what to do next. Help??
[Nexus One Android Development] Constrabus:
Make sure that you place the loop.bat in the same directory that adb is in. It should be in the tools folder inside the android-sdk folder,
[Nexus One Android Development] goldfingerfif:
I'm on a rooted 2.2 fr87, I think the OTA update it keeps bothering me to update is for FR91. It is pissing me off that it won't stop asking for me to update, will I lose my root if I update? I only got my android phone a few days ago already rooted so I did not read anything much about android.
[Nexus One Android Development] schahr01:
Worked great! Thanks.

PS - Step 15 (reboot into system) can be skipped. Go into 'adb shell' right after the unrEVOked update.zip is installed. Once in the shell, after 'su' just issue "PATH=/system/bin" to set the shell's binary search path and carry on with the flash_image steps. Saves time and there's no superuser popup :D
[Nexus One Android Development] Constrabus:
Why not just flash an FRF91 rooted rom from the development section? Or any other rooted rom for that matter.
[Nexus One Android Development] danger-rat:
Trying now...
[Nexus One Android Development] dihy:
Am I able to run stock FRF91 using this method? If so, what happens if I receive another OTA update?
[Nexus One Android Development] 3RR0R404:
Really sorry for my poor english, i'm not able to read and understand all 400 replies here =/

Is this trick working on EPF21B ? Cause I'm on EPF21B and don't want to remove warranty but need root :p

Thanks !
[Nexus One Android Development] shenlei089:
should i wipe？
[Nexus One Android Development] Michigan Jason:
UGH

I feel stupid as I have done this before, but....

I can get ADB working in android and my pc sees the htc device connected, HOWEVER, in recovery, all I get While running loop, is "daemon not running, starting it now..." and it stops there and still doesnt see my device.

Thanks alot op.

EDIT: While running loop, I get ADB while the phone is booting, so I know the driver is installed correctly. But when I reboot with SD card out, and run loop, while booting into recovery, it says, *daemon still not running, cannot connect to daemon*

Why am I not getting ADB while in recovery, but I do while in android? If I can figure this out, I think im good to go.

EDIT #2 Ok, thanks to an earlier post on page 2 I believe, I was able to get adb working by not running loop until the last minute. It seems that running loop too early will error out before it gets the change to see the attached devices. So for those who are trying this, do not run loop until your phone is booted into the bootloader and you have recovery option highlighted, but not selected, now run loop and select recovery and the adb will connect.
[Nexus One Android Development] goldfingerfif:
I don’t get much free time to research these things and this 2.2 notification is pissing me off, if you have a link to a guide to do this I would appreciate it but my short question is if I tell it to install will I lose root access as I need it for setCPU.

I am still new to all of this android stuff, I switched from a crappy crappy iPhone 3g which I hated (it would drop about 1 in 5 calls sometimes more, the screen would go all white and I needed to “spank” the phone to get the screen back, random reboots, and it would at least once a day tell me “No SIM Card” and I would have to take the sim out and put it back in sometimes more than 5x before it would recognize it again)

Before my iPhone I had a N900 which I absolutely LOVED but it wouldn’t work with ATT 3g only Tmobiles and I spun a crank bearing in my car (2004 SRT-4) back in Feb ’10 so I had to sell the phone to pay for a motor rebuild,

before that was an HTC Fuze which I honestly liked but it was terribly slow,

before that I had a Nokia N95 which I also LOVED TO DEATH but the backlight went out forcing me to get the Fuze since I was resisting the iPhone at the time. I eventually got the iPhone to check out the hype but everything about it was lame except it was overly simple but for a power user like me it didn’t suit.
[Nexus One Android Development] cursordroid:
Curious if this 'bait and switch' method would work to flash the 0.33.2012 Engineering SPL?

If it works for the update.zip mentioned here, why not replace the contents with the hboot flash commands and the 1.33.2010 SPL?

Then we'd be able to flash pretty much anything to the phone...

thoughts?
[Nexus One Android Development] sp83142:
SD Card Removal

I've remove the entire tab on the battery but the sd card still will not slide out. I have no clue what it's causing it to not come out. I even tried putting little pressure on the battery to get the card out. Can anyone help pls?
[Nexus One Android Development] :
lol thats VERY risky. besides the sizing of the SPL's are different. dont know if they will fit exactly even if the difference in size is small

your not supposed to take it out.....your supposed to put it in..
[Nexus One Android Development] danger-rat:
Great write up!

...but can someone offer a bit more guidance?

I did the roll-back from FRF91, and then re-updated to the universal FRF85B.

I then rooted, following instructions 1 through 15, and everything worked great!

I then tried the custom RA recovery steps 16 through 24...

Everything seemed OK, but how do I know if I actually achieved the flash of the the custom recovery? Everything looks/acts the same...

My ultimate goal is to get back to FRF91, but without losing my root.

Thanks!
[Nexus One Android Development] cmstlist:
Boot into recovery again... do you get the stock Android recovery, or do you get a screen that says Amon-RA on it?

Now boot into the OS, shut it down, boot into recovery a second time. If you still see Amon-RA then the flash was successful and is not reverting to stock.

Now you can apply one of the pre-rooted stock FRF91 update.zip files found on this forum, or alternately the two-parter which 1) flashes stock FRF91 minus stock recovery, 2) reapplies root and insecure boot.img.
[Nexus One Android Development] danger-rat:
The root definitely worked, so I've just tried running through steps 16 to 24 again.

Getting the new recovery screen this time (says RA-nexus, etc).

Thanks for your help...

Now I just need to work out how to do the Nandroid backup before I load a new FRF91. I've seen some good posts, but they still miss a few details for someone as green as myself...

I presume that I "run nandroid.sh" from within adb?

Do the nandroid files need to be in the same folder as the sdk tools?

UPDATE:

Scratch that, I figured I'd likely do more damage with Nandroid than with flashing FRF91, so I just went ahead and did it...

Now have FRF91, rooted, without unlocking my bootloader.

Thanks again!
[Nexus One Android Development] itsjaylou:
Downgraded

If I downgraded from FRF91 to EPE76

Do I need to upgrade to ERD79?

Because in order to upgrade to ERE27 I need to be on ERD79, correct?

If so, where can I find a signed update?

Or am I just going about this the wrong way?

Are we not supposed to be using bootloader/recovery?
[Nexus One Android Development] Constrabus:
Thank you so much danger-rat. I really appreciate it.

If your still interested inn doing a nandroid backup, all you need to do is boot into your new recovery, choose the backup option, then choose the nandroid backup. It's that easy. and it will back up to your sd card in a folder called nandroid. You can even restore a backup from this menu in your recovery.
[Nexus One Android Development] Constrabus:
Use this.

http://www.megaupload.com/?d=WMCZIIIB

It will update you to FRF85b. You can then finish the tutorial as normal.
[Nexus One Android Development] Rusty!:
Ah but what about a SHIP SPL with S-OFF?
[Nexus One Android Development] :
well first we need to dump it :P

ask @haykuro if he knows how
[Nexus One Android Development] vr2004:
hi guys.. i'm new here. may i know if this method can be used on unlocked nexus one directly from google?
[Nexus One Android Development] Michigan Jason:
Yes, I just got my 2nd N1 in the mail yesterday and followed this guide. Tweaked a few steps to make it easier and all worked 100% If you are new, you will most likely need help, so just ask. Please read and educate yourself as much as possible though before attempting it.

Jason
[Nexus One Android Development] vr2004:
yes infact i do need help.

i manage to downgrade my n1 from frf91 to epe76 and upgrading it back to frf85b.

followed step 1 to 15 without any problems.

the problem occured when i tried flashing the recovery-RA-nexus-v1.7.0.1.img

when in step 20, i kept getting the error message that there is no such file or directory. i continued all the way to step 24 but when i rebooted my phone, the recovery was still stock.

the sdcard was unmounted when i did step 16 to 24

i used my desktop cmd command promt for all the steps. also i noted that when carrying out this hack, the root file used was frf83 but the firmware that i used was frf85b. after gaining SU. my fone was still in frf85 which i'm not sure if its correct or shoud it show frf83?

thanks in advance.
[Nexus One Android Development] Constrabus:
Do step 19, then 22 to 24 again, then reboot.

That should flash your recovery.

The root file is called FRF83, but it works on all builds. No need to worry about that.

Remember, if your phone has the open padlock icon when you boot your phone, this will root your phone, but won't re lock it.
[Nexus One Android Development] itsjaylou:
Broken Links?

Is my computer messing up or are a bunch of the links broken?
[Nexus One Android Development] scalp42:
Most of the links from Google servers are gone unfortunately!

Would be great if the first post was updated with people links to different OTA/full updates (megaupload or wherever people found those).

Along with MD5 hash and it would be awesome!
[Nexus One Android Development] fearedbliss:
When I try to download (T-Mobile pre-requisite) FRF83 or FRF72 it says "404 Not Found".
[Nexus One Android Development] vr2004:
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

May i know... when the instruction says in your terminal, what terminal does it mean? windows cmd ??
[Nexus One Android Development] Constrabus:
Yes, the terminal in Windows is called CMD.
[Nexus One Android Development] Constrabus:
I didn't even realize the links were broken.

Thanks guys.

Fixed!
[Nexus One Android Development] vr2004:
op, sad to say that i can only achieve SU but can't flash custom recovery.

i followed exactely the steps and at step 20 i had a readout that the file was not found. step 23 n 24 also gave me the same error but i'm sure they are removed from my system. i did a reboot but the stock android system recovery <3e> keeps poping back!!!:o
[Nexus One Android Development] Constrabus:
If you run "ls /system/"

can you see install-recovery.sh listed as a file?

and/or

If you run "ls /system/etc/"

can you see install-recovery.sh listed as a file?

If you do see them, you need to make sure that you don't before you reboot after flashing the new recovery image.

If you don't see them, then the recovery image isn't being flashed properly for some other reason.
[Nexus One Android Development] Constrabus:
As an additional note, if you are having trouble running those commands through the Windows CMD, you can also type them within a Terminal App in android.
[Nexus One Android Development] vr2004:
Microsoft Windows [Version 6.0.6002]

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

C:\Users\Viknesh>adb shell

'adb' is not recognized as an internal or external command,

operable program or batch file.

C:\Users\Viknesh>cd C:\Users\viknesh\Desktop\android-sdk-windows\tools

C:\Users\Viknesh\Desktop\android-sdk-windows\tools>adb shell

$ su

su

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

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

# cat /sdcard/flash_image > /system/bin/flash_image

cat /sdcard/flash_image > /system/bin/flash_image

/sdcard/flash_image: No such file or directory

# chmod 775 /system/bin/flash_image

chmod 775 /system/bin/flash_image

# flash_image recovery /sdcard/recovery-RA-nexus-v1.7.0.1.img

flash_image recovery /sdcard/recovery-RA-nexus-v1.7.0.1.img

# rm /system/etc/install-recovery.sh

rm /system/etc/install-recovery.sh

rm failed for /system/etc/install-recovery.sh, No such file or directory

# rm /system/recovery-from-boot.p

rm /system/recovery-from-boot.p

rm failed for /system/recovery-from-boot.p, No such file or directory

# ls /system/

ls /system/

framework

build.prop

media

bin

tts

fonts

lib

usr

app

etc

lost+found

# ls /system/etc/

ls /system/etc/

permissions

media_profiles.xml

init.goldfish.sh

hosts

gps.conf

firmware

event-log-tags

ecclist_for_mcc.conf

dhcpcd

dbus.conf

contributors.css

bluetooth

apns-conf.xml

NOTICE.html.gz

AudioBTID.csv

AdieHWCodecSetting.csv

01_qcomm_omx.cfg

wifi

vpimg

vold.fstab

updatecmds

security

pvplayer.cfg

ppp

#

sorry i pasted a long file here... This is the current situation i'm facing. am a completely nood to this command stuffs but am willing to learn
[Nexus One Android Development] vr2004:
in terminal i can't type adb shell

only can start with su.

the rest are the same respond as the cmd command promt.
[Nexus One Android Development] salimmk:
Thank you so much. Worked perfect on my stock t-mo N1. I did not wake up this morning thinking I was going to be shaving a plasic tab off my N1 battery but oh well, it worked!

You could have been more clear on how to proceed after downgrading from FRF91 to EPE76.
[Nexus One Android Development] Cjizzy:
Excuse my noob-ness if thats a word

I cant seem to get past step 20 to save my life, i keep getting the error /sdcard/flash_image : no such file found when i do step 19 nothing seems to happen is there something im missing here
[Nexus One Android Development] unleashed12:
Just wondering about one thing and would like it cleared up before I try this..

Can I flash any rom after this? Ie. 2.1 desire rom???? Just wondering because it says cm and stuff..
[Nexus One Android Development] Constrabus:
Read the notes section of the first post.
[Nexus One Android Development] Boswell20:
Thank you!

I attempted this two days ago and it was my first time doing anything like this. After a bit of struggling to begin with, I am glad to say that I was successfull!!!! Thanks a lot! This guide was great
[Nexus One Android Development] vr2004:
ok.... i finally manage to flash a custom recovery!! i was searching through the market n came across rom manager by clockworkmod. install it n the program can do rom n recovery flashes.. i flash the amon RA recovery n woot... it worked!! time to try out some custom roms :D
[Nexus One Android Development] uoY_redruM:
Once downgrading to EPE76 I CANNOT update to ANY other versions. I've tried from the bottom up. They all fail to update...

What the hell do I do? I've never had a problem updating before...now I'm stuck on EPE76.

EDIT:

Got that fixed....but now I can't figure out how to work sdk. How the heck do I open a command prompt?

EDIT EDIT:

Got that finally. Now, I'm stuck. On the adb push, each time I do it, is it suppose to open a bunch of text again or is it suppose to do something else? I've done it over and over and over again and nothing has seemed to work..
[Nexus One Android Development] uoY_redruM:
I'm beyond frustrated now.

The adb push doesn't seem to be doing anything at all. Every time I type it in, it just recycles the menu again as if nothing is happening. I went through it several times (I'm on FRF85B, just an FYI) and over and over it just recycles the menu when doing adb. I figured maybe that's normal but when I get to the final step (adb push then click and hit enter fast) I see nothing about unlocking...
[Nexus One Android Development] rmagruder:
Suggestion: Can you add to your sticky a complete guide to getting back to Stock if it has to go back to HTC?

A Nandroid restore (assuming they follow your steps to install will get you to Rooted FRF85B with Amon-Ra recovery. But that's 90% of the way. How would you then get back to stock recovery and 100% stock rom?

Thanks,

Randy
[Nexus One Android Development] IllegalOpcode:
Works like a charm. Thanks for your hard work.:D
[Nexus One Android Development] vorach:
can somebody say if this rom can be rooted or downgraded with this methode??

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

i am a french user with EPF21B and i have made the update to this one without unlock the bootloader. and wit success
[Nexus One Android Development] uoY_redruM:
Can anybody help me? Thread says just ask but I've PMed the author and like two other people while they were online with no response and nobody has anything to say on the forum...
[Nexus One Android Development] Flippy125:
To simplify the recovery flashing process just download "ROM Manager" from the market and flash that recovery.
[Nexus One Android Development] Flippy125:
Make sure you set up ADB properly. Check the OP for info. Make sure it is ON not in recovery when you do it. You can also test the functionality of ADB from there by just typing in "ADB devices"
[Nexus One Android Development] uoY_redruM:
I haven't tried the "adb devices" command yet, but I'm sure I'm in the right location.

I'm in recovery, I stop the loop, I slide my card in, I do the volume+/power, click update.zip, then do all the adb push commands. Each time I do teh adb push commands though, it filters all the adb command lines as if it did not do anything at all. Should it be giving me, for example, "adb push flash_image successful" after I type it in? Or any kind of message?

I'm not thinking I'm achieving adb or something...
[Nexus One Android Development] ellesshoo:
I got stuck on step 20: " In your terminal, type "cat /sdcard/flash_image > /system/bin/flash_image" and hit Enter"

Returns: No such file or directory.

I ended up installing ROM Manager and flashing the recovery that way.

HOWEVER, I noticed that after I flashed the recovery rom and rebooted to check it, it worked. If I rebooted a second time I'd get the stock recovery ROM (e3) again.

Anyone know what I'm doing wrong?