yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] Neo-K:
I can't seem to navigate through your Recovery menu with my trackball.

I had the New Froyo Rom installed and wanted to and install the new Cyanogenmod rom.

I have the RA-Nexus-v1.7.0 Cyanogem version installed. (according to the MD5sum check it was okay)

What can be the problem?

Update:

Also tried the other 1.7.0 , doesn't work and tried the older version, which also doesn't work for me.

Update2:

I found out that my trackball is responding really bad! So i pressed harder and now it works (barely)
[Nexus One Android Development] Amon_RA:
Trackball works just fine in recovery, I think you have a hardware problem...
[Nexus One Android Development] GrandMstrBud:
When I reboot the phone that way I get the stock nexus recovery screen. Yes I do have superboot also because I am able to install apps that require root access.

C:\Nexus\android-sdk_r06-windows\android-sdk-windows\tools>fastboot flash recove

ry recovery-RA-nexus-v1.7.0.img

sending 'recovery' (3948 KB)... OKAY [ 0.594s]

writing 'recovery'... OKAY [ 1.312s]

finished. total time: 1.906s

Is there a command after the fastboot flash recovery? As you can see it copies the image and I reboot and I still don't have the custom recovery.

EDIT:

Okay I finally got the recovery image going. After the image copied over I believe I rebooted the bootloader and now I can get into the custom recovery menu. Finally, I didn't see that in any of the instructions I found anywhere but oh well I got it now.
[Nexus One Android Development] GrandMstrBud:
For some reason I keep lossing the recovery image and have to reflash it. I installed ROM manager and flashed to the ClockworkMod 1.8.1.4 and it still randomly looses the recovery image and I have to go in and reflash the image. And of course the same thing happens with the RA-nexus-v1.7.0.
[Nexus One Android Development] Amon_RA:
Updated to v1.7.0.1

Change-log :

v1.7.0.1

Fixed fix_permissions script to use use /sd-ext instead of /system/sd as mountpoint

Fixed unmount script to also unmount /sd-ext

Nandroid menu option now backups/restores /cache again by default

Fixed wipe script, dalvik-cache is wiped in /cache /data and /sd-ext if present

Changed selected menu-text color to black for the cyan version
[Nexus One Android Development] lpasq:
thank you :cool::):D
[Nexus One Android Development] Wysie:
The black text is much easier to see in cyan version :). Thanks Amon_RA!
[Nexus One Android Development] crimsondr:
Re: [Recovery] [30-May-2010] RA-nexus-v1.7.0.1

Instructions might want to mention you need su before flashing in terminal.

I tried to flash in terminal and our seemed to work. But I can't get into recovery anymore. It freezes at the google x now.
[Nexus One Android Development] gtrplr71:
fastboot is a safer way. Thanks for this recovery worked great:D
[Nexus One Android Development] cmarti:
Worked beautifully!

Thanks
[Nexus One Android Development] BogiYear:
Ditto. Works a treat. Many thanks for the update.
[Nexus One Android Development] 13bjunkie:
i came by the same problem. i got it to work after renaming

the file shorter to just recovery.img. it worked perfectly

afterward.
[Nexus One Android Development] crimsondr:
Re: [Recovery] [30-May-2010] RA-nexus-v1.7.0.1

I tried this previously but it didn't work. I will try fastboot later when I am near a computer.
[Nexus One Android Development] Driskol:
Same prob here,

No booting into recovery renaming to reco.img and flashing i i dont have any adb here...
[Nexus One Android Development] kelddaug:
fastboot flash recovery recovery-RA-nexus-v1.7.0.1.img works fine.

Remember to copy the recovery-RA-nexus-v1.7.0.1.img file in to your SDK Dir or where fastboot and Adb is.

Mine is in C:\SDK

Tnx Amon_Ra
[Nexus One Android Development] crimsondr:
Finally tried installing via fastboot. Worked fine this time.

Thanks.
[Nexus One Android Development] superg81:
anyone have any ideas why this isnt working via terminal?terminal is how i prefer to flash
[Nexus One Android Development] knightnz:
Thanks very much AmonRa!

(Seriously, how hard is it to use FastBoot people!?)
[Nexus One Android Development] big nu:
No go term!!

It sucks, I always flash amon's recoveries via terminal app and never had a problem and with this one its just not cooperating,, BOOOOO!!

All I get is stuck at the nexus X I see other are having the same issue..:(

Hopefully this problem gets work out cause I lost my USB so i cant do it via fastboot.
[Nexus One Android Development] Drakon911:
I was unable to flash via terminal either. I'm running the latest CM5.0.7.1.

I even went back and tried to flash a previous version of the recovery and it wouldn't work either. Makes me wonder if it's not a problem with CM or perhaps the basic terminal?

I was able to get it installed by using Clockworkmod ROM manager.
[Nexus One Android Development] big nu:
Damn near impossible when you dont have a usb cable handy atm..:rolleyes:
[Nexus One Android Development] Amon_RA:
The problem seems to be CM related, koush and cyanogen are looking into it.

Which terminal app are you guys using?

Did you try to use bash as shell yet?
[Nexus One Android Development] Jack_R1:
Sorry to interrupt, but - 1) thanks, flashed via fastboot and works, 2) a request lost between those pages, wasn't heard since March - maybe we could see an option to flash from any folder?
[Nexus One Android Development] superg81:
im using better terminal from market.flashed last version with this and went without a hitch.i dont know how to use bash as shell so i cant comment there.thanks to the ones looking into this
[Nexus One Android Development] Amon_RA:
so it works if you flash via better terminal??
[Nexus One Android Development] crimsondr:
I tried and received out of memory errors.
[Nexus One Android Development] oneadvent:
I can confirm the issue here, via terminal app Terminal Emulator with root privileges provided by Superuser, it did not work, but when i used fastboot, it was no problem and good to go.

I am running the latest CM, 5.0.7.1-N1. Let me know if I can provide anything of assistance.

I was scared there fore a minute, but good now.
[Nexus One Android Development] superg81:
sorry,i have not tried. after rreading through the threads,i assume most terminal apps are the same.i didnt want to get stuck and be without a phone.
[Nexus One Android Development] dnsmo:
having the same problem too here, i have to flash with fastboot, cm 5.0.7.1-n1
[Nexus One Android Development] theloginwithnoname:
Completely cosmetic and relatively-trivial, but I'm loving the new colour for the standard version!
[Nexus One Android Development] lwclam:
after I shorten the name to "recovery.img", it works
[Nexus One Android Development] ibegary:
I can confirm that doing the flash by terminal resulted in a hang at boot for me (When trying to boot in recovery). Had to flash by fastboot.

Cyan v5.0.7N1 with intersectRaven Kernel.

Thanks
[Nexus One Android Development] PhantomRampage:
Just wanted to say thanks for the update Amon_RA! :D
[Nexus One Android Development] RiNo808:
HELP, i first tried to install via terminal, it hanged...so i followed the link to install superboot and installed it and now my phone is hanging in booting up...it hangs i just the the blue cyan's...the phone wont boot up...pulled the bat and tried to reboot and still hangs on cyans image...

Okay guys i solved my problem...i had to install RA's 1.0.7.1 via fastboot, it installed the new RA's 1.0.7.1 but it still hung in booting up...so i did a nandroid recovery and it worked...wheww i thought i bricked my phone...talk about a puckering effect...lol
[Nexus One Android Development] mdubs:
Ok, I have the same issue trying to flash via terminal.

Tried both of the terminal apps that I have. Tried shortening the name to "recovery.img"... No luck.

Can't use fastboot on work pc so I'll report back after I'm home and have a few minutes to run it that way.
[Nexus One Android Development] ilmusso:
i've an time/date issue everytime i enter in recovery... :(

set back to 1980...

my system setting are set to 24h european time

anyone can confirm this?

Thanks in advance!
[Nexus One Android Development] smarti13:
changing boot.img

do you think I can change a boot.img from one to another ?

thanks
[Nexus One Android Development] enriqueluis:
cant update phone to froyo..help

/Volumes/NO NAME/DCIM/101MSDCF/DSC01811.JPG
[Nexus One Android Development] DreamScar:
Sorry if this has been asked/addressed already, but I'm having an "issue" with wiping while in recovery, in that the phone is never fully wiped. After wiping and reinstalling Cyanogen's ROM for a fresh install, when the phone boots up, the wallpaper I was using is still loaded and my wifi network is still saved. There may be other things that have remained after a wipe as well, but these two are the only I have come across. This has occurred in 1.7.0 and 1.7.0.1.

Is there any reason why these things are being saved?
[Nexus One Android Development] smarti13:
so which RECOVERY should I use for DESIRE ?

thanks
[Nexus One Android Development] RogerPodacter:
i believe these 2 things are backed up via google's standard backup if you have that option checked in your main settings. at least i'm pretty srue about that. so you probably ARE doing a full wipe, but the data is just being replaced as soon as you log back in with your gmail account into the phone.
[Nexus One Android Development] RogerPodacter:
i have a question. when i create a nand backup, the time of my created file/folder is way off. i think its off by a couple hours, but i'm not sure exactly. is this normal? perhaps its just using some standard time zone, but shouldnt it match my current phone timezone? used the standard recovery, and also now using cyanogen recovery.
[Nexus One Android Development] DreamScar:
Ah, thanks.

BTW, I've also noticed that my nandroid timestamps are way off.
[Nexus One Android Development] RogerPodacter:
can i use the cyanogen recovery as my main recovery, for switching to froyo? or should i use the regular recovery? can the cyan one just replace and be my main recovery?
[Nexus One Android Development] codington:
Nandroid backups use GMT for timestamps
[Nexus One Android Development] alodar1:
after several errors...this is what worked for me...just shortening the name...
[Nexus One Android Development] superg81:
has anything been discovered or fixed regarding flashing via terminal?
[Nexus One Android Development] kwrose14:
Error in CACHE: recovery/log

when I flash an item getting Error in CACHE: recovery/log (no space left on device) message.

- recently wiped and partitioned SD card

- 1.5 ext 4 with 5 gb fat 32 96mg swap

- running cyan 5.0.8 image

also unable to download applications from market, not sure if related.

Would appreciate any help possible with these issues.

Thanks in advance.
[Nexus One Android Development] Daneshm90:
Ur cache seems to be full. Do "cat proc/mtd" in terminal and check the free space. Neway just fastboot erase cache for now and see if that helps
[Nexus One Android Development] enriqueluis:
su request blank screen

please i tried flashing this recovery image via terminal app but after typing su i am now stuck with blank dark screen and nothing happens until it says su permission is not respondong force to quit???? help?????
[Nexus One Android Development] Daneshm90:
Im not too sure but hasnt there been issues with the flash_image binary on the recent cyanogen mod ? Anyway, just go into fastboot and type

fastboot erase recovery

fastboot flash recovery <drag recovery.img here>
[Nexus One Android Development] Bigworm37:
I just installed 1.7.0.1 and everything went smooth (i had to use fastboot because the terminal made the phone freeze up when i tried going into recovery) I have a problem with the "wipe SD:ext partion" command when i try to wipe it gives me this message " Error : Run 'wipe ext' via adb" is this problem something im having or is this something new with the recovery. When i had 1.7.0 i didnt have this problem... i am running Froyo FRF50

Any help on this would be greatly appreciated...
[Nexus One Android Development] Daneshm90:
Just to be safe u shud wipe ur recovery partition after u tried flash_image recovery and it failed. Do that and see if it resolves ur issue.

fastboot erase recovery
fastboot flash recovery <drag recovery.img here>
[Nexus One Android Development] Amon_RA:
Please check first post :

Always check recovery.log before posting your issues!

You can do this by doing :

"cat /tmp/recovery.log" OR "cat /cache/recovery/log" right after you had the issue.

Use the "move log to sd" option in the "others" menu right after you had the issue. This will move the log to /sdcard/recovery.log so you can easily open it with a text editor.
[Nexus One Android Development] Bigworm37:
I tried the fastboot erase recovery command and it told me it diddnt recognize fastboot..then i tried fastboot-windows erase recovery and it said " erasing 'recovery'.....FAILED < remote: not allowed>"

Is this some kind of SU permision thing...because i have titanium backup installed and maybe it doesn't allow the recovery to wipe the SD data.

I might revert back to the 1.7.0 if i cant solve this thing

Anyways thanks for the advice..
[Nexus One Android Development] Amon_RA:
You can't fastboot erase with the n1 spl...

Anyway, why are you trying to erase the recovery when you have wipe ext issues? See my post above, check the log.
[Nexus One Android Development] Bigworm37:
Amon, i was trying to erase the recovery because i thought maybe i didnt install it properly. I have read the Log file and cant really see what the problem is.. i have attached it if you like to look at it.

Thank You

BGW
[Nexus One Android Development] codington:
FRF50 does not use the ext partition - the ext partition was only used for loading apps if you selected that option in recent ROMs. If you enable apps to SD under FRF50, they (supposedly) will load straight to your SD card partition. I don't use that option and have never tried.

If you really want to know why the wipe SD:ext is failing, send your recovery log (from Amon) to the SD card, you can see exactly what is erroring when trying to wipe SD:ext.
[Nexus One Android Development] Bigworm37:
Codin... i think you answered my problem... I flashed back the original 1.7.0 recovery and i got the same error. So definately the recovery img was installed correctly.

BTW...were do you see the app2sd option on FRF50? i cant find that anywere

I used to see it with previous roms....

Thanks

BGW
[Nexus One Android Development] prettyboy85712:
It's under applications settings and must be enabled by the app developer to work.
[Nexus One Android Development] joel.bourquard:
The application has to support it, and for now, very few do.

With some command-line trickery or Titanium Backup, you can move any app to the SD card. But be aware that the Froyo App2sd implementation is not perfectly stable yet. Every time you move an app, there's a small chance that the App2sd engine will hang, leaving you without the apps that you had on the SD card. So backup often, and don't forget to backup the /sdcard/.android_secure directory too !
[Nexus One Android Development] Bigworm37:
I see...so if the app developer has that option it will appear (when i download from market) and then i can install it on SD card.. nice

Thanks guys for your help

BGW

PS: I do use Titanium Backup...great tool...i have never used the app2sd even with my previous roms....
[Nexus One Android Development] cdw9800:
im on 1.7.0.1 and im trying to wipe my battery stats but it starts and stop i dont know why anyone can help me on this? is there a manual way i can wipe the stats?
[Nexus One Android Development] smarti13:
HTC Desire

can I use this recovery for a HTC Desire ?

thanks
[Nexus One Android Development] SANTilt:
I tried flashing the latest version via terminal, but it just hangs at the X on reboot.

I tried via fastboot, and it gives me this error every time: FAILED (remote: signature verify fail)

I've tried both files, and I've tried renaming them. I've also tried the old 1.7.0 file, and it gives the same error. I'm running CM 5.0.7.1 any ideas? :confused:
[Nexus One Android Development] SANTilt:
nevermind, figured it out.
[Nexus One Android Development] bhake:
Too many errors happening lately

I've been using Amon RA recovery for several months (along with Cyanogen roms) with my Nexus One and everything was working fine. Lately, backups started failing. Giving me that Error: run nandroid in adb line. Sometimes it worked, mostly not though as of late. I've been trying out different ROMs and radios the last few weeks, does that effect how nandroid works?

So, I flashed the latest 1.7.0.1 via fastboot, hoping known issues may have been fixed. First backup I did with this version said it was successful... but after restoring, all my data was missing and it only restored the stripped ROM. That was a bummer (note to self, invest in SMS backup app)! (FYI, I do not use apps2sd or have a partitioned SD, so I do not use backup+ext.) So had to use an older backup to restore from that was good. Tried to backup again, and started getting same errors (run nandroid in adb).

I am not sure how to use adb, so is there another way to troubleshoot this? via terminal? If anyone can point me in the right direction to get nandroid backups working again, let me know.

Thanks!
[Nexus One Android Development] brandnewsimmy:
Whenever I install the recovery images the work the first time immediately after, but then resort back to the stock recovery screen. I thought I read something about that but no cannot find the info. Any idea what is going on?

I have followed the pre-requirements as well. Thanks for any help.
[Nexus One Android Development] asero:
It's in the first page.

which means delete or rename that file if you have it. Then flash recovery again.
[Nexus One Android Development] Amon_RA:
Copy paste from first post (please read) :

Important notes

Always check recovery.log before posting your issues!

You can do this by doing :

"cat /tmp/recovery.log" OR "cat /cache/recovery/log" right after you had the issue.

OR

Use the "move log to sd" option in the "others" menu right after you had the issue. This will move the log to /sdcard/recovery.log so you can easily open it with a text editor.

You don't need adb to do this... just move the log to sd and check what's going wrong.
[Nexus One Android Development] brandnewsimmy:
Oh, you mean the line directly under the steps I mentioned I used? :(

I will try that and thank you so much for your help!
[Nexus One Android Development] ToneSoFly:
Recovery-Image

Is there by any chance can someone post the version of ra recovery image 1.7.0.img i had it but lost the file when i had to format my computer.:eek:
[Nexus One Android Development] raspdeep:
Hi Amon_RA, I am sure you have been asked this questions many times before with all the recovery threads, i dont know where to begin searching so I am using going to ask it here. Is there a recovery for HTC Desire or do you plan to make one?
[Nexus One Android Development] Abe546:
Amon Ra Recovery Won't work.

Hey man I sent you a message but I dont know if you received it.Amon Ra wont load on my Nexus I did all the requirements bit It doesnt work through the terminal emulator and when I try to use super boot it says it sent and flashed it but when I go on my phone and go into recovery an exclamation point pops up and nothing happens.Please anyone help me send me a message or something Im a super noob to XDA.Also,if you dont know what to do could you suggest ways I could flash Amon Ra or something else.P,S I tried 1.6.2img,1.7.0.1.img,and 1.5.3img and thay dont work either.
[Nexus One Android Development] JWhipple:
I am somewhat of a n00b, so please excuse the ignorance of this question.

Can this be flashed without currently having root but currently having an unlocked bootloader? I was on Paul's Froyo, went back to 100% bone stock, and now realizing the error of my ways. Unless I have to, I don't want to have to root again - would rather just install the recovery and then use it to reinstall Paul's Froyo.

Thanks in advance!
[Nexus One Android Development] codington:
You must be rooted in order to load this recovery. You know that Paul's FroYo is rooted - I think what you are asking is do have to root the stock ROM before you can run this custom recovery, right? The recovery won't stick without root. I supposed you could probably just

boot

the recovery and not flash it - that should allow you to enter recovery and restore a previous backup. However, once your phone reboots, you will be left with stock recovery. With the phone plugged in to USB, try these fastboot commands:

fastboot devices
fastboot boot recovery recovery-RA-nexus-v1.7.0.1.img

Good luck
[Nexus One Android Development] yumeul:
hey i tried flashing by terminal app on cm5.0.7.1 when i try to boot in to recovery mode its stuck on the screen with the unlocked sign but im still able to boot into normal operating mode
[Nexus One Android Development] prettyboy85712:
Maybe you should read a little before posting. It's a known issue. :rolleyes:
[Nexus One Android Development] plinton876:
problem

Everytime I try to download onto my Mac it says mounting failed. What is going on here? idk i cant update it unless its downloaded.
[Nexus One Android Development] douglasjboehme:
Signature Verify Fail issue

When I try to flash the recovery using your steps in the first post (I powered on using the trackball and see the fastboot menu), I get the following:

c:\sync\apps\Android\android-sdk-windows\tools>fastboot devices

HT9CSP801581 fastboot

c:\sync\apps\Android\android-sdk-windows\tools>fastboot flash recovery recovery-RA-nexus-v1.5.3.img

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

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

FAILED (remote: signature verify fail)

Is that because my bootloader is locked? This is a Nexus One ordered directly from Google, not through T-Mobile. I verified the MD5 sum just in case.
[Nexus One Android Development] deprecate:
fastboot oem unlock my friend :) My n1 is also a carrier independent phone but I still had to unlock my bootloader.
[Nexus One Android Development] douglasjboehme:
I *just* found that over at http://www.nexusoneforum.net and came back to your great response! Thank you! Success! :)

This is what I get for doing the all-in-one-magical-noob-unlock for my MT3G prior to getting this.
[Nexus One Android Development] deprecate:
I take it you never had a g1 :) The n1 is an 'all in one magical noob unlock' compared to the g1.

Now that you no longer have a warranty, go crazy! The tethering is quite nice. Dropbear is too. Once things really start moving along (full rom releases), ownership will become rather interesting!
[Nexus One Android Development] douglasjboehme:
Sadly I never had a G1. I jumped into the Android fray with a MT3G coming from Palm devices starting with the Handera stuff.

It's funny, I remember thinking when I first got my MT3G "pffft, what do I need root for" and the following week I had CyanogenMod's ROM on there. Bought him a beer on my 3rd week of ownership, the rest is history.

I'm still embarrassed that I couldn't find the OEM unlock stuff but am glad you posted it.
[Nexus One Android Development] deprecate:
The G1 was quite a lot of fun. I'd be lying if I said you had not missed much :)

Cya got a TON of people involved with their phones more than he will ever know. I hope more people bought him a pint.

No reason to be embarrassed. When a flood of information hits for something new, the n1 for example, digestible information can be very hard to come across in a sane manner. I assume that once things standardize, proper how-to threads will pop-up and be stuck. Until then? The fray will continue to be an amusing show to pop some popcorn, sit back and observe :)
[Nexus One Android Development] BrooklynAvi:
Yes, I had that set. I'm curious to learn more about that new setting. I'm going to look into it some more. If this is the case then doing a factory reset doesn't truly reset the device to factory state. I wonder if there is a way for the recovery wipe to unset the setting to prevent Google from restoring settings, thus making it a true factory reset.