yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] denimjunkie82:
Hi all,

I am having the exclamation mark error as well. I can only enter NA Recovery using fastboot boot.

However, when coming off a stand-alone reboot into the bootloader > recovery > i get the exclamation mark.

I am not rooted yet. I have 2.1 update-1

I've tried shiver's method above within RA Recovery, and it says "flashing recovery from blahblah...img". Then after a fresh reboot, I am still getting exclamation point.

I've also tried codington's method above. After flashboot booting RA recovery, and then re-flashing RA recovery, then re-booting within flashboot and then going back directly to bootloader > recovery, I can access RA. However, upon a fresh reboot from ROM to bootloader > recovery, I am again getting the exclamation point.

Anyone have any ideas? I the image is there and I've already created a nand backup, it just doesn't default to it...

p.s. I notice that while HBOOT is loading...it suddenly flashes with "loading PASSING .nhh...no image or wrong image!" but I can't catch what it says exactly because it disappears right away. I'm not sure what it's supposed to say here or if it's related.

p.p.s. I also noticed that as long as I successfully boot NA and then stay within fastboot/bootloader/recovery partitions, I can also boot back into NA. However, once I go into the rom and do a soft reboot there (or ADB reboot recovery), I get the exclamation point again and have to start over.

FIXED - Apparently, I found out that the RA recovery can only be flashed successfully AFTER rooting. I was trying to make RA work before I root...which was the wrong order. So RA can be booted manually, but it can only be defaulted after root.
[Nexus One Android Development] david1171:
denimjunkie82, did you fastboot flash or fastboot boot the file?
[Nexus One Android Development] denimjunkie82:
i used fastboot flash...many times!
[Nexus One Android Development] codington:
You can rename the backup folders, just make sure you have one continuous naming convention (no spaces). Even renaming with spaces will not corrupt the backup images; just that the nandroid shell script will not be able to read the folder names.
[Nexus One Android Development] mrandroid:
For those having trouble:

Boot into Fastboot

make sure it says fastboot-usb

install the recovery "fastboot flash recovery <filename>"

WAIT about 1 min... After 1 min THEN reboot and try your recovery
[Nexus One Android Development] jlevy73:
This is a beauty. Should come preinstalled on all Android devices.
[Nexus One Android Development] lothos88:
I agree, has saved me from many a brick on my G1 and kept me from soiling myself after a pooched experiment today on my N1 :)

Thanks for all the hard work you do Amon_RA!
[Nexus One Android Development] rb_darryl:
recovery-ra-nexus-v.1.5.3.img WONT FLASH ON DEVICE?!?!

I dont post much and read alot. After careful consiteration i finally decided to "Unlock" my Nexus One. Now 1st this is not my 1st go round with rooted devices. So with that on to the problem..

Everytime I try to flash the Amon RA recovery 'command prompt' tells me that the image cannot be flashed????

I have the .img in the adb file folder I can assess everythign else even tried re doing the bootloader and system told me the phone was unlocked... so if there is something I am missing please fill me in! Thanks.

I can be reached on Twitter as well

dkemp4prez
[Nexus One Android Development] jerrycycle:
unlockr has a tutorial video on this. This might help you.
[Nexus One Android Development] btmec:
Take a look at this and see if it will help

http://theunlockr.com/2009/10/15/how-to-flash-a-new-recovery-image-if-you-are-already-rooted/
[Nexus One Android Development] bofslime:
re-download your bootloader image and verify the md5 is correct. I had an issue with a corrupt image when I did mine.
[Nexus One Android Development] Common Sense:
confused

It seems I cannot make it work despite a lot of effort, I hope you guys can help me.

First I have put the recovery file recovery-RA-nexus-v1.5.3.img on the root of the sd card in the phone.

I then reboot following these instructions:

1) copy recovery-RA-nexus-v1.5.3.img to root of your sdcard.

2) boot into fastboot mode (trackball + power)

3) 'Fastboot boot recovery_RA_nexus_v1.5.3.img' (this will boot with Amon-Ra's recovery, but it's not flashed yet.)

3) While in Amon-ra's recovery, do what shivers316 says,

1 and 2 is no problem, I successfully enter the fastboot mode. I also got "FASBOOT USB" written there and usb cable connected. So far so good.

But step 3 I cannot understand, Should I somehow type the command 'Fastboot boot recovery_RA_nexus_v1.5.3.img' using the soft keyboard when I am in this menu? Or should this complete sentence be in the menu?:confused: that is one of the options should read like that whole string and I just press it?

I have 4 options in the "FASTBOOT USB" menu:

BOOTLOADER - brings HBOOT menu

REBOOT - reboots the phone :)

REBOOT BOOTLOADER - restarts bootloader :)

POWER DOWN - turns off the phone :)

If I press BOOTLOADER and then arrive at the menu HBOOT:

FASTBOOT - Search sd card for a zip file and says fail, quickly returns to menu, no chance to see what it writes, too fast. I can see it writes fail something.

RECOVERY - Gives me the droid with the ! warning triangle next to it.

CLEAR STORAGE - never tried, don't think it can help.

SIMLOCK - probably not.

Conclusion:

It seems I follow all the steps exactly as I should, and all is fine until I reach 3, please help, what does it mean? :) How am I suppose to do this step? :)

Any help greatly appreciated.

CS
[Nexus One Android Development] landstander:
The fastboot command is entered at your computer while the phone shows FASTBOOT USB. You need to have a copy of recovery_RA_nexus_v1.5.3.img there as well... it will be uploaded to the phone as a temporary (unflashed) boot image.

The copy on your sdcard is needed so that you can flash it via adb, once the temporary image is booted.
[Nexus One Android Development] rb_darryl:
what did you fo when you had a corrupt image? i downloaded them from both links Amon supplies
[Nexus One Android Development] liam.lah:
I have gotten to the point where i wrote ‘fastboot flash recovery recovery-RA-nexus-v1.5.3.img. It said it worked in the command prompt. i then try to boot into the recovery and i get the little android !

What's more is that the computer no longer seems to see the device when i fastboot devices, even though it sees the USB, and it even says it is in debugging mode on the phone, so i cant try and install it again. Even though it does not show up in the command prompt, typing "adb reboot recovery" still makes the phone reboot back to the !android.
[Nexus One Android Development] Common Sense:
Thanks a lot, I am now much more clear on what to do.

I install the sdk on 2 macs and one pc running windows 7 (with usb drivers installed and working) and none of them can find my phone when I type adb devices :(

I am in fastboot usb mode.

do I need to have a sim card installed for it to work?
[Nexus One Android Development] landstander:
You should be using "fastboot devices" at that point... the adb commands wont work until you're past the fastboot stage (booted into either normal or recovery mode).

I did my flashing, however, from a Linux environment... the basic process is the same (once communication is working), but I can't really speak to any Windows or Mac requirements. I wouldn't expect a sim card to be needed for any of this, but have never tried without it.
[Nexus One Android Development] rb_darryl:
odd... when i try to use terminal emulator typing in "su" to access the superuser it tells me 'permission denied'
[Nexus One Android Development] rb_darryl:
i reverified the MD5 is correct... still wont let me flash the recovery onto the phone... not sure what options I have at this point. phone boots up shows that it is unlocked, wont flash recovery from bootloader and denies me access to su through terminal emulator... is there a way to start over and root the phone again..?
[Nexus One Android Development] jerrycycle:
This is the nexus one tutorial from the unlockr site. This is a very good tutorial. Please try it.

http://theunlockr.com/2010/01/02/how-to-root-the-nexus-one/
[Nexus One Android Development] liam.lah:
Scrap that, i was putting th commands in at the wrong place. But now i have tried the recovery from both mirrors, in both instances the command prompt says sending OKAY and Writing OKAY, but still comes up with the little android with the !.

EDIT: some more info so someone can help me

I have unlocked the bootloader

i am using windows

i have put a copy of the boot recovery in my sdk/tools directory, same as where fastboot is

i have put a copy of the boot recovery on the root folder of my sd card.
[Nexus One Android Development] 51dusty:
ditto

i'm having the "! android" issue...tried flashing several times, tried waiting after flash...no luck. hope we figure out what the prob is.

edit: got it...i also did not realize i needed superboot...*dumdumdum*
[Nexus One Android Development] liam.lah:
I managed to fix it, i didnt realise i needed superboot. Superboot fixed it

Follow what is said here
[Nexus One Android Development] r8zer:
i can not believe so many people have said the same things, i mean, even to touch the bootloader u have to be unlocked, and rooted to gain user permissions, even states this when u are following the guides, sorry to be a bit of a downer but, it is all there in writting, people need to slow down take time, to read, and re-read the documents, and get it in their head and absorb the info, other wise peeps are gonna do some real damage to their beloved phones, once again sorry for being a bit of a tard on this!!
[Nexus One Android Development] liam.lah:
I read the guide at the front of this thread, and a video and text walkthrough on androidandme, neither went through superboot, it was only a third tutorial from godknowswhere that it mentioned superboot. In each of the documents i have read, there is a lot of assumed knowledge so big pieces are missed out.

I might give a shot at writing out a walkthrough :eek:, i had problems to overcome at every single stage, i shouldn't need to use three tutorials to root one phone, having to do that is where you are likely to do some real damage to the phone.
[Nexus One Android Development] Mikey:
Hey,

Amon, are you gonna update your recovery image to include your backup/restore feature to include apps2sd????

I tried to restore mine and i boot-looped :(

Can you please look into updating it.....PLEASE :D
[Nexus One Android Development] Amon_RA:
I intentionally left the apps2sd features out of the recovery and I don't plan to include them tbh...
[Nexus One Android Development] daveid:
Do you know there is an issue with Nandroid restores that causes the permissions of /system/xbin/su to get borked? Makes it look like root has been lost, and some people actually panic about it (starting threads and stuff). Is this something you can look into?
[Nexus One Android Development] Brajin:
Please help!

Ok I have unlocked the boot loader on my nexus. Next I downloaded the the recovery image and placed in the tools folder of my sdk. My issue is that when I open command prompt and type the command to flash the image it replies "can not load recovery. I type "Fastboot flash recovery recovery-RA-nexus-v1.5.3.img. I also tried the other method to try and boot in to the recovery and flash via adb. bit the image does not load that way. Trying to instal on Windows 7. I am assuming the sdk is properly installed since I was able to root. Thanks to anyone who could help me.
[Nexus One Android Development] packetlss:
Is this reproduceable?

Also, a 'ls -al /system/xbin/su' on an affected system would help.

In fact, include a 'ls -al /system/bin/su' aswell.

The problem seems to be that either mkyaffs2image or the unpacking, cause it to lose the attributes.
[Nexus One Android Development] rb_darryl:
I have followed the unlockr tutorial verbatim, still having a issue flashing the img
[Nexus One Android Development] manup456:
Now that roms are coming out using apps2sd will we see a new recovery soon I really hope so your work is great bro.
[Nexus One Android Development] landstander:
Seriously, you couldn't see just 4 posts back? :confused:
[Nexus One Android Development] Mikey:
May we know the reason??? Please

Limiting the Android Community to be forced to leave apps on phone, instead of giving us the option to apps2sd should be the real Android way.

You have great Recoveries dont let this recovery be any different from your others.

;)
[Nexus One Android Development] packetlss:
(I'll answer this, since I got quite alot to do with the recovery development.)

Have a look at the other recovery threads. Almost every single issue is related to ext-based filesystems w/ regards to backup and restore.

There is just too much **** that can go wrong with it as it is implemented at the moment.

Nothing really prohibits you from using apps2sd with it now though. It's just the troublesome bits that are gone. Fix UIDs are still there, partition SD card is there. Only thing missing from the menu is ext filesystems upgrade and the apps2sd specific move options (which should be implemented by the rom anyway).

If you REALLY want to backup w/ ext, upgrade your ext filesystem or move files around, it's still doable from adb.

Also what enomther has done w/ including lucid in his rom to support apps2sd functions is good.

After all the recovery is there to support the most basic stuff that needs to be done, not a skeleton key to everything android related. Otherwise it will be bloated beyond repair very quickly.

As for apps2sd in general. I think the community needs to agree on a new way of doing it, possibly with a set of generic scripts and checks that can be easily adjusted to specific needs. As it is now it's burdened by decisions taken way back in the beginning of android hacking.
[Nexus One Android Development] Brajin:
Please help!

My Nexus one is recognized in fast boot, but when i follow the intalation instructions I get the following..........................................................

When flashing the 'fastboot flash recovery-RA-nexus-v1.5.3.img' I get an error

"unknown partition 'recovery-RA-nexus-v1.5.3.img' error:can not determine image filename for recovery-RA-nexus-v1.5.3.img'

....Can anyone please help, I've been at this all day and just can not seem to figure it out. I am running the sdk on Windows 7.
[Nexus One Android Development] SiNJiN76:
Cool! Thanks. It'll be less confusing. I'm probably just going to add a little note to the end of the original file name.
[Nexus One Android Development] manup456:
Bro I am not going to sit and read this whole thread and who are you? lol.....oh your amon because I was not talking landstander thought he was talking junk to me lol...

@packetlss

I think wiping the ext is more needed than the upgrade part.
[Nexus One Android Development] kingklick:
to be 100% honest

I agree with manup on this one

not saying we need ALL ext options ma man, but at least WIPE ext would be good.......

I am guessing all it is is a simple mke2fs............................:(
[Nexus One Android Development] dantheman_:
it should be fastboot flash recovery recovery-RA-nexus-v1.5.3.img you're getting an error because your telling it to flash the recovery-RA-nexus-v.1.5.3.img partition (which you dont have :p)
[Nexus One Android Development] packetlss:
True. I'll look into it.

Until it happens, use adb.
[Nexus One Android Development] Brajin:
Thanks for the help, When I type "fastboot flash recovery recovery-ra-nexus-v1.5.3.img....I get error: cannot load 'recovery-RA-nexus-v1.5.3.im
[Nexus One Android Development] landstander:
Heaven forbid that anyone else might ever reply on an open internet forum... :rolleyes:
[Nexus One Android Development] hks18psigst:
no automatic upgrade_fs?... for ext3... hmm... adb shell wont let me upgrade either..
[Nexus One Android Development] Brajin:
Cant flash the dam image

Ok so I have tried over and over again to flash the recovery. But FAstboot cant seem to flash the image. I have followed all the tips on this thread....but no dam luck at all. Can anyone offer any tips please. All my adb and fastboot commands work fine. And I placed the recovery image in the tools folder of the sdk. I am running windows 7
[Nexus One Android Development] Worsty:
Hi all, just wondering if anyone experienced losing their root after restoring with Nandroid.

Didn't used to have this issue but happened only after i changed the radio img (ERE36B) and flashing to cyanogen 5.0.3.1 coming from ERE27 and 5.0.2.

I'm only able to regain root by wiping and flashing 5.0.3.1 again.

Same issue happening to me after flashing the MoDaCo Desire ROM Alpha 7 and restoring with Nandroid to 5.0.3.1

I guess it's not that bad an issue since i can restore my apps and system from titanium backup but doing a full restore from Nandroid saves me some time so was wondering if there is a solution to my problem.
[Nexus One Android Development] Worsty:
If all your commands are fine and you have placed it correctly, i can only think of the Recovery img file that you have downloaded is corrupted.

But just to confirm,

1)When you "fastboot-windows devices", can you see your serial number?

2)When you "fastboot-windows flash recovery recovery-RA-nexus-v1.5.3.img" , what message comes up?
[Nexus One Android Development] ggrant3876:
A noob question, with no terminal in the recovery console how do you run fix_permissions?
[Nexus One Android Development] Amon_RA:
Yes I'm aware of this problem, it's probably mkyaffs2image which is confused by the su symlink in xbin and restores the wrong permissions as a result...

in the mean time fix it with :
[Nexus One Android Development] landstander:
You don't actually need a terminal for this with the Amon_RA recovery. It's called "Fix apc uid mismatches", and can be found under "Other" in the menu.
[Nexus One Android Development] Mikey:
Use the lucid script
[Nexus One Android Development] simms22:
you can run fix_permissions in the regular terminal emulator.
[Nexus One Android Development] Worsty:
Thanks Amon_RA!

If it happens again, that'll come handy.
[Nexus One Android Development] Amon_RA:
Updated to v1.6.0

Change-log :

v1.6.0

Fixed mkyaffs2image-arm-uclibc which will hopefully fix the "loosing root" issues after a nandroid restore (a big thanks to packetlss for the help on this one)

Updated busybox to v1.5.3

Recompiled kernel to fully support ext3 and ext4

Added lots of ext-features + scripts to stop the a2sd nagging

Created a carebear version after the idea of packetlss. Be aware that this version contains some "ultra-secret" features! ;)
[Nexus One Android Development] kylez64:
this is gonna be fun!:D
[Nexus One Android Development] Gimpeh:
Can anyone put up another mirror that aint 4shared or rapidshare?
[Nexus One Android Development] Amon_RA:
Please READ before you post. Thanks.
[Nexus One Android Development] wicked_beav:
My bad................
[Nexus One Android Development] graphreak:
The (Mirror) link has another site.

Worked perfectly fine for me.

Thanks for the awesome work Amon_RA.
[Nexus One Android Development] Amon_RA:
Did you read the post? Did you try the mirror link? :(
[Nexus One Android Development] Brajin:
New Recovery

I personally agree with amon, I care for using applications to sd on the nexus, only used it on my G1 out of necessity. But it is nice having the applications back up option to sd. If anything happens its nice to be able to copy them back onto the phone.
[Nexus One Android Development] Beast84:
Seeing as how I really don't want a carebear on my phone lol anyone wanna share what these "ultra-secret" features are?
[Nexus One Android Development] gtrplr71:
I salute you sir this is awesome!!!:D
[Nexus One Android Development] mgorman:
will this overwrite my OC'd kernel? will I need to reflash it after I flash this?
[Nexus One Android Development] irokes:
big thanx :)
[Nexus One Android Development] geovass:
flashing the new image now!

many thanks!
[Nexus One Android Development] geedave:
OP Links

Please don't yell at us when ALL THREE links in the OP point to RapidShare!
[Nexus One Android Development] david1171:
No, it will not.

Not entirely sure what you mean? That is his primary file sharing service. You could use what is labeled mirror right beside it and download it from androidspin.
[Nexus One Android Development] Mikey:
they are uploaded to rapidshare and androidspin.

So your missing the point that (mirror) are actually different links???
[Nexus One Android Development] Gilg@mesh:
Cant' flash the carebear

Hi

I'm trying to flash the carebear version but with no luck, what is it I'm doing wrong?? please help, the fastboot "sees" my phone.. and the img image is on the SD card...

here is a picture...

thanks
[Nexus One Android Development] Spinstorm:
The carebear is cute!

Anyway its not exactly hard to reflash the recovery if you want it back to your "X" but honestly who is going to see the recovery screen except you when you hack and flash the phone?! It makes more sense to go for the features over the looks for recovery!

Thanks Amon_RA!
[Nexus One Android Development] david1171:
Is the file in your working directory?
[Nexus One Android Development] m00moo:
you have not specified the location of the recovery image.

eg

C:/recovery....img

that will mean the image is located on the root of c: drive. Also you need to fastboot flash so the image will need to be on your computer not SD card
[Nexus One Android Development] Gilg@mesh:
aha ok, now I understand..
[Nexus One Android Development] Amon_RA:
Incorrect, there are 6 links, 3 to rapidshare and 3 to android spin...

The following is even mentioned in RED in the OP :

Click on the Mirror-link if you don't like rapidshare

I think it's very clear...
[Nexus One Android Development] Gilg@mesh:
thanks I will try it :)
[Nexus One Android Development] youneek:
I'm disappointed. I flashed 1.6 and I don't see carebears anywhere? Do I need to reflash?

EDIT: nevermind, it was the link right below the one I flashed... duh...
[Nexus One Android Development] gIMpSTa:
did you download the carebear version or just the regular version? 2 different versions 1 is yellow text with nexus x in recovery mode and other is pink text with carebear pic in recovery mode.
[Nexus One Android Development] gtrplr71:
that looks right did you type a wrong digit or letter and then backspace and correct sometimes it wont flash if you do. just do it again I have flashed both with success
[Nexus One Android Development] kingskidd268:
Rapidshare is acting up is their another link.
[Nexus One Android Development] daveid:
Jesus, learn to read. Did you not see the word MIRROR next to the link? MIRROR!!!!!!!!!!!!!!!!!
[Nexus One Android Development] kingskidd268:
Yo why are you so nasty. I think you need a hug..
[Nexus One Android Development] RonnieFoxxx:
ok i HAD to flash the CareBear one for the laughs and the kitch of it. But now im hearing about "ultra secret features"? i ran the plain jane 1.6.0 and i see no difference... anyone want to give me a hint? I GOTTA KNOW!!1! lol :D
[Nexus One Android Development] geedave:
OK, fair enough... But it was NOT clear that (Mirror) referred to a separate link from the main link beside it.
[Nexus One Android Development] bobtentpeg:
Really, because its rather clear. Given that theres not linking of the parenthesis and if you took 1 second to mouse over the word you'd notice it was different. Just because you were lazy doesn't mean it wasn't clear
[Nexus One Android Development] Thats BS:
Awesome work as always. Thank you.
[Nexus One Android Development] Four Fourty Four:
Is there a way to flash this via terminal emulator? I don't my use cable with me.
[Nexus One Android Development] daveid:
Seriously, let's count the number of times the exact same thing has been asked and answered in this thread...

I think my response was quite normal considering the circumstances. This question has been beaten into the ground, yet is fully answered in the first post.
[Nexus One Android Development] daveid:
yes, download to your sdcard and do this:

su
cd /sdcard
flash_image recovery recovery-RA-nexus-V1.6.0.img