yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] gravufo:
Or a better solution would be to have some kind of constant configuration file which would save the last "signature check" state, meaning that if I turn it off, it will stay off, even after a reboot, until I turn it back on! Dunno if it's possible
[Nexus One Android Development] lxe524:
try this new version!!!
[Nexus One Android Development] mgorman:
Any news on when next update will be released?
[Nexus One Android Development] HereAsWell:
I fear that the author is busy with his Nexus S. The Nexus One is used by his GF from now on... That what I have read at twitter... I guess we'll have to live with the fact that the Nexus S will receive a lot of the attention that our N1 once had...
[Nexus One Android Development] Amon_RA:
Updated to v2.1.0

Changlog v2.1.0 :

Reduced recovery size by 800kb so it fits any hboot version to date :

Set Kernel compression mode to LZMA (33% smaller kernel)

Switched kernel debugging off

Removed : Networking support - Bluetooth subsystem support

Removed : Device Drivers - Misc device - AKM8973 Compass Driver

Removed : Device Drivers - Misc device - A1026 Voice Processor Driver

Removed : Device Drivers - Multimedia support

Removed : Device Drivers - MSM 3D Graphics driver for Adreno class GPU's

Nandroid now backups the entire content of /sd-ext , not just the apps. This fixes bootloops of certain restored roms.

Moved the "Toggle signature verification"-option from the Other- to the main flash-submenu.

Re-ordered the wipe menu.
[Nexus One Android Development] RinTinTigger:
Great work so far!!

Tested Backup

Tested restore

Tested Wipe

Working!
[Nexus One Android Development] Autinhyeu:
Thx so much :-)
[Nexus One Android Development] Know-Fear:
Top notch. Flashed new version and tested. All is good thus far. Thank you Amon-RA.
[Nexus One Android Development] Bakano:
awesome work as usual =D
[Nexus One Android Development] simms22:
thank you!

no problems flashing 2.1 :)
[Nexus One Android Development] cmarti:
Update is much appreciated. :)
[Nexus One Android Development] superg81:
flashed and working well :D
[Nexus One Android Development] fabioccoelho:
Works fine for me too :D

Thanks @Amon_RA ;)
[Nexus One Android Development] Docmjldds:
Nexus One HD ROM Error EXT wipe

MicroMod and I both have identical issues. Choosing wipe the ext only we get the following. This is using his SuperHybrid V1.6 HD-Desire Sense ROM as noted in my sig too. I am using a 1GB EXT3 Partition. Your 2.0 didn't have this issue, BTW.

Formatting SDEXT:...

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

(No such device)

Error mounting /sd-ext/!

Skipping format...

/sd-ext wipe complete!
[Nexus One Android Development] Docmjldds:
Did you test a wipe ext only with MicroMods HD-Desire Sense ROM? Doesn't work :(

Formatting SDEXT:...

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

(No such device)

Error mounting /sd-ext/!

Skipping format...

/sd-ext wipe complete![/code][/QUOTE]
[Nexus One Android Development] prettyboy85712:
Thank you for your hard work!!!
[Nexus One Android Development] Amon_RA:
Thanks for reporting this.

I'm looking into this...

Do you have just FAT and EXT3 on your sdcard, or do you have a swap or anything else too?

Did you have the same issue with the previous recovery version?
[Nexus One Android Development] wsrider:
Donated for your work. thank you :D a few packs of red bull there
[Nexus One Android Development] thejron:
NEED power select option! My trackball is toast. :(
[Nexus One Android Development] Amon_RA:
updated to v2.1.1

Changelog : v2.1.1

Fixed ext4 support in kernel! Update from v2.x if you are using sd-ext!
[Nexus One Android Development] simms22:
thanks again, flashed perfectly :)
[Nexus One Android Development] Royan:
v2.1.1 flashed perfectly via terminal

brgds

Royan
[Nexus One Android Development] 1xguns:
Excellent. Thanks for your work. I use your Recoverys from Magic to N1.
[Nexus One Android Development] Docmjldds:
Just fat and EXT3. No swap. Nothing else. Never had issues before and last version 2.0 worked fine, as does clockwork 2.5.1.1 (I don't use Clockwork 2.5.1.4 as it has issues with MM's HD ROM)

Thanks for the quick reply. Much appreciated.
[Nexus One Android Development] Docmjldds:
I'll try this even though it says fixes EXT4 and my issue is EXT3, but you do state to update with ext-sd :D

EDIT: Hooray...it works. Thanks a bunch. Will report results back on MicroMods Thread too. Merry XMAS, Happy Holidays, and a Happy New Year to you and yours.
[Nexus One Android Development] lcksh0t:
This is a noob question, am I able to flash using fastboot or the terminal app without unlocking my bootloader? I also am rooted using CM6.1.

Thanks.
[Nexus One Android Development] philanini:
a ,man!This is a goodthing, I love u ,RA.
[Nexus One Android Development] SubyWill:
this is great! thanks!
[Nexus One Android Development] LFact:
If you already rooted, you can use terminal to flash recovery(read first post). Also, you can use adb to flash it:

adb push (your recovery image file name) /sdcard/ (<- you don't need to do this if you already copied recovery image into your SD card)
adb shell
#flash_image recovery /sdcard/(recovery image file name)
[Nexus One Android Development] zekers:
Thank you soo much Amon! We appreciate the update. :D
[Nexus One Android Development] TonDwg:
I tried to update from 2.0.0 to 2.1.1 via terminal app, but it doesn't work. there are read, re-read and write errors, and after each error "Out of memory". In the last line there stands "error writing recovery: No space left on device" . Can someone help me please?
[Nexus One Android Development] iniro:
For me it works on second try.
[Nexus One Android Development] shahmi86:
Yeah.it happen to me also for my 1st try. Then i tried to flash back and the terminal told me " same header"

Then i boot to recovery , there 2.1.1 . Voila~

Maybe you can check 1st at ur recovery whether already flash to the new one or not
[Nexus One Android Development] musashiken:
+1.

I also had out of memory errors on the first try. It worked on the 2nd try and the recovery was fine.

As my bootloader is still locked, I used the Terminal method (from the xda wiki) to flash it.
[Nexus One Android Development] TonDwg:
hmm, it seems that my recovery was completely deleted. I tried rebooting into recovery, but it takes me to bootloader. And if I trie to go to recovery through the bootloader, it throws me back to the bootloader :confused:
[Nexus One Android Development] RinTinTigger:
2.1.1 working real slick...only thing i miss is the carebear ^^
[Nexus One Android Development] chris4chelsea:
Same. I just reboot an.d flash again then fine.
[Nexus One Android Development] TonDwg:
ok, tried again, this time via fastboot, and it finally worked :)
[Nexus One Android Development] lcksh0t:
Thanks!
[Nexus One Android Development] mori220:
i can not download link is dead
[Nexus One Android Development] thanant:
Thank fine working
[Nexus One Android Development] :
Thanks Amon,

Flashed 2.1.1 thru terminal, all good.

Back up did seem faster than before

Ken
[Nexus One Android Development] Jesse6749:
I noticed the restore of Micro's HD rom was a lot quicker than clockwork recovery too, and I love the fact that it now it backs up everything :D :D :D.
[Nexus One Android Development] warpaper:
error:

In my CM6.1.1, flash from terminal but got the following error:

Please help. Thanks alot.
[Nexus One Android Development] Amon_RA:
flash via fastboot or boot into your current recovery and use adb and flash_image to flash the recovery.

You can also try to boot your phone and immediately run flash_image.
[Nexus One Android Development] armyengineer51:
I am assuming my problem is related to the above, but I'm not sure how to fix it. Everything seemed to go fine flashing the recovery, and I can boot into it while connected to my computer. If I am not connected to the computer however, I get the above result (stock recovery). I'm used to Clockwork which I had on my Aria and could boot into recovery disconnected, is this just the way Amon_Ra's works? If not, how do I make sure that init.rc isn't calling install-recovery.sh?

I'm on the AT&T version of the Nexus One and rooted with my bootloader unlocked, if it matters.

EDIT: It appears that the only time I can get into Amon_Ra's recovery is immediately after I flash it, and I have to go directly from fastboot to recovery. Other than that, I get stock recovery, it seems like the flash isn't sticking.
[Nexus One Android Development] clustered:
thanks very much Amon_RA.... ;)
[Nexus One Android Development] efrant:
You need to delete the install-recovery.sh file before you reboot. This has been covered many times.
[Nexus One Android Development] gravufo:
It really isn't clear for the people I guess =\ Maybe amon_ra should add the two "rm" commands in his instructions, it would probably help
[Nexus One Android Development] armyengineer51:
Well thanks for not hammering me too badly, or giving me the lmgtfy answer. I did search but came up empty.

That probably would have helped a little. Anyway, I've got it now. After flashing CM 6.1.1 that pesky file is gone and I can boot into recovery without issue.

Thanks all!
[Nexus One Android Development] efrant:
That file only exists on stock ROMs. Every time you flash a stock ROM, you need to delete it and re-flash your custom recovery.
[Nexus One Android Development] meechto:
Thanks, Amon_RA :) 2.1.1 flashed fine ;) Works great :D
[Nexus One Android Development] armyengineer51:
Thanks, I appreciate that info! Can't really see myself going back to stock for any reason tho...
[Nexus One Android Development] mgorman:
Never mind. I figured it out.
[Nexus One Android Development] overground:
2.1.1+BART

For those who know what it is and miss it. Credits to dumfuq for BART and packaging this for me. Unzip first, then flash through fastboot or terminal.
[Nexus One Android Development] capncark:
Sorry for the newb question but what does this mean. I flashed recovery image in fastboot and all appeared ok but I am still getting stock recovery mode.

Thanks
[Nexus One Android Development] efrant:
Have you done any reading in this thread? This has been covered numerous times, even just a few posts back - look at post 1556...
[Nexus One Android Development] ellesshoo:
Not sure if this has been mentioned but if you replace the amon ra 1.7 "alternate" recovery file in the clockworkmod folder with this recovery and rename the file to the same as the 1.7 filename you can simply use the flash alternate recovery option in ROM Manager to flash 2.1.1. RM will still display 1.7 as your recovery but if you boot into recovery it will indeed be 2.1.1
[Nexus One Android Development] mijaskydive:
YES!

PLEASE ADD A CAREBEAR THEMED VERSION!!!

Please. The bear is so awesome^^
[Nexus One Android Development] :
Love the Bear, but 2.1.1 is rocking!
[Nexus One Android Development] arminsoyka:
I have a question:

I have a SLCD Nexus One so ClockworkMod Recovery doesnt work for me. The old Amon_Ra Version 1.7 which comes as an alternative Recovery Mode System with the Rom Manager didn't either. So I downloaded 1.7, then downloaded 1.8 - which is SLDC compatible - manually and switched and renamed the directories on the SD-Card. That way I could have a working Recovery Mode System, but still use the Rom Managers features. What happens if I now flash new Amon_RA? It will overwrite whatever other Recovery Mode System is running at the moment write? And then I wont able to use Rom Manager anymore as long as I wont overwrite Amon_Ra with ClockworkMod right? Is there a way to upgrade within Rom Manager?
[Nexus One Android Development] Kiserai:
I'm also loving the 2.1.1 update, but I do find myself missing the bear. It was weird and quirky and unique, and it made me smile whenever I rebooted into recovery.

It would be great to bring it back as an option.

Thanks for the great work, Amon Ra.
[Nexus One Android Development] edansbro:
I run the fastboot install of the amon recovery, yet when I reboot into fastboot and choose recovery, I'm still going to stock recovery. What did I mess up?
[Nexus One Android Development] davados:
Is there anyway of getting rid of bad memory blocks through recovery?
[Nexus One Android Development] samo_nz:
Password support

nice recovery guys..

But, can we please get some sort of security on our phones with a password prompt before getting access to recovery/adb?

I was thinking the first screen could be a menu of 0 to 9 selecting the first digit of the pin and so forth.. thoughts?

it has always scared me how someone could just restart in recovery and reflash with no lock code.. $1000 fone for free
[Nexus One Android Development] Amon_RA:
What's the purpose of a password in recovery mode when you can just use fastboot or even flash_image to boot/overwrite a custom recovery?

It doesn't make sense at all...
[Nexus One Android Development] Franc38:
You can use rom manager with any recovery you want... And there's only one on your phone at any given moment.

So if you flash RA 2.1.1 it won't show in Rom Manager (in mine it says that the current recovery is ClockworkMod... when I'm using RA 2.1.1) but that's not a problem....

And it seems to me that the latest ROM Manager version proposes to flash RA 2.1.1 in options (at the bottom, in "flash other recovery"... ) I haven't tried, since I don't really use ROM manager (just for some downloads... ) and prefer do things manually.
[Nexus One Android Development] :
When you use Rom Manager and select to flash alternate recovery, it is going to flash the recovery on Rom Manager's server which is 1.7.0 or .1, don't remember exact version.

So, you either use RM/CW or flash amon thru fastboot or Terminal. It will be there until you flash CW thru RM.

I only use amon 2.1.1 now even though RM is still on phone. If I wanted to use CW and restore a bu I have made with CW, I will use Quick Boot to get to recovery after flashing CW. I use Quick Boot to get to recovery for amon also. Don't like using RM UI anymore. Had some issues with bu's and restores with it.

This is the way I understand it.

Ken
[Nexus One Android Development] makelegs:
Fwiw .... I just opened RM (recently updated version) and it lists Ra 2.1.1 as the available alternate recovery (even though that's what I'm already using). So....if some of you still need to update, it would appear that RM can now flash it for you, without your needing to use terminal.

# WIN

Sent from my Nexus One
[Nexus One Android Development] paura01:
is just me or it is impossible to load the MIUI rom after flashing with this new release?
[Nexus One Android Development] shuka325:
Amon.. Is there ANY chance of you creating this recovery for the G2? I am so used to using and loving this recovery on the Nexus a. Having to use CW recovery with the G2 seems like such a downgrade in my view. Thanks for all your work, only problem is trying to go to something else after all the convenience of this recovery...
[Nexus One Android Development] :
I have no problem-running it now
[Nexus One Android Development] yeahyeah123:
Can you post an ls of the directory you are in?

(Sorry got banned, had to make a new account, I'll probably have to come back with a proxy soon, but I'll try to help you)
[Nexus One Android Development] gtxhckr818:
the recovery and the fastboot are under the tools section of the SDK on the desktop.

Sotry i do not know what ls means.
[Nexus One Android Development] yeahyeah123:
Well that's correct, they are in the right directory.

I don't think I can help you because it seems it's a mac thing, and I don't use macs. Try pming serpah1024 he's on a mac. Sorry.
[Nexus One Android Development] Swervo:
It's definitely a case of running the app in one directory while your recovery-RA-nexus-v1.5.3.img file is in another one. You have to figure out what directory/folder you downloaded the file to, change to that directory, and then run the same command. I've never really used a mac, but it's close enough to linux, you could try this command in the terminal:

That will search your whole system looking for that file and print out where it is when it finds it. You can then just copy and paste that whole path, say it's /home/anthony/Desktop/recovery-RA-nexus-v1.5.3.img, and run

Then spend some time reading about how to navigate your way around the terminal, you're *really* going to want to know more about that before going much further.
[Nexus One Android Development] fosormic:
Hey there. From what you post then I assume that it would be technically possible to repurpose this area to implement things such a "slider" or add more "soft buttons" (altough they would be hard to find)... am I correct?
[Nexus One Android Development] dnanj:
- adb reboot recovery(fr windows command prompt)

- sdparted -ufs ext3(upgrades ext partition to <TYPE>)
[Nexus One Android Development] cupOjo:
Is there no way to do it through like terminal emulator? I remember being able to flash the recovery like that with the G1, correct me if I'm worng. I have a mac and am having a hard time flashing this IMG.
[Nexus One Android Development] cupOjo:
Ok I'm really confused. Would somebody with a MAC be kind enough to walk me through the process?

Edit: Finally figured it out! Thank god.
[Nexus One Android Development] sputnik99:
maybe a silly question but as i don't have my nexus yet:

how do you enter text in recovery mode? Is there a virtual keyboard? On my G1 there was only the phisical keyboard for terminal emulator and recovery etc.

Thanks

Hoping to switch soon from g1 community to nexus 1. Ordered yesterday but my nexus is brought from a friend from usa to europe. Have to wait for this.
[Nexus One Android Development] L10nH34Rt:
You can't. Same was for Magic :) You'll love the Nexus btw...
[Nexus One Android Development] Swervo:
You can also use adb to open a shell on it while it's in recovery mode.
[Nexus One Android Development] march7th:
sorry if a dumb question, but is it supposed to show as H after installing recovery or should it still display 3G?
[Nexus One Android Development] Swervo:
The recovery won't change that, did you also install cyanogen's beta rom? That will change that (and don't worry, just a different designation, you're still moving at at least 3G speeds).
[Nexus One Android Development] RonnieFoxxx:
so i feel really stupid now... i have searched and searched and came up with nothing.... i have managed to root my nexus but im clueless on how to flash amon ra's recovery image on mac osx. im not great in the terminal and i have no idea what it means in the op by "...where fastboot can see it". somebody help a n00b out? please?

:(
[Nexus One Android Development] RonnieFoxxx:
wow.... opened up a book and figured it out... sorry for the waste of space guys :D
[Nexus One Android Development] Amon_RA:
would you mind sharing the steps you took so i can add them to the first post for mac users. ;)
[Nexus One Android Development] SiNJiN76:
Does partitioning the SD card allow me to save apps to the SD card? If it does...how do I set it to do so? I'm already rooted...got the backup...and beta 2 of cyanogen's rom. I'm also a first timer (Android, Rooting, Touch Phone, etc.). =)
[Nexus One Android Development] irishrally:
Deleted ...
[Nexus One Android Development] anthro:
Whenever I run the recovery, I just get the Android with the exclamation point.

I thought, I installed it properly, but I'm not getting the right recovery screen.

Where should I put the RA recovery? I just put it on my SD card's root.
[Nexus One Android Development] amirnew:
hi can you please add the option of wiping the ext partition to the recovery?

thank you

amir
[Nexus One Android Development] :
Thanks for that info--never worked that way before

Maybe Koush heard our cries

What version of RM are you running and all you did was flash 2.1.1 thru TE and now it shows available?

Ken
[Nexus One Android Development] :
Well I'll be a -----

2.1.1 is now there

I have paid version and that's the way it should have been working

Need to test now, since I have an old CM rom backed up under CW and would like to flash it and save under Amon

Thanks to Koush and Amon_Ra for getting this done

Ken
[Nexus One Android Development] makelegs:
I have RM 3.0.0.2. It just updated yesterday, after I finally got the GB build to work. I really haven't "used" RM in a looong time. I just looked b/c you folks were discussing it. Yes, I flashed 2.1.1 thru TE when Ra released it. TE is so easy that I didn't even think to check RM. I have no idea if flashing thru TE impacts what shows in RM. Don't see how it could, but WTH do I know? ;)

hope that's helpful!

Sent from my Nexus One
[Nexus One Android Development] :
I had amon 2.1.1 on phone, flashed CW thru RM to restore an older CM6.1 bu made with RM/CW. I reset up screens and stuff then wanted to back it up with amon 2.1.1. Doing this to get all roms under amon_ra.

Tried to reflash amon thru TE as I have done many times and it won't flash. Says "header the same, not flashing recovery". Not sure what that means.

Under Preferences: Command line says--/system/bin/sh -

Under Initial Command: export PATH=/data/local/bin:$PATH

Not sure if that is correct, I never changed them. The export line is at top of screen when I open TE.

Wanted to get it set back up to use amon all the time.

Any help?

Ken
[Nexus One Android Development] :
OK,

I rebooted anyway and booted into recovery with Quick Boot and Amon 2.1.1 is there.

Why did it do that and am I safe to proceed as all is 100%, or do I have an issue.

Have not had good luck the last month with CM or RM.

Ken
[Nexus One Android Development] makelegs:
I'm no expert, by any measure, but I'm pretty sure I saw folks having similar issues where they thought something was wrong with the recovery flash, but when they booted recovery everything seemed fine. Ur probably ok. Maybe see if u can complete a nandroid backup just to make sure it seems to work. Either that, or perhaps flash an older Ra, and then reflash 2.1.1, again.

That's all I can think of for now. :-/

Sent from my Nexus One
[Nexus One Android Development] :
Thanks for the reply makelegs,

I read similar posts when researching this. All seems ok. I bu'd the old CM6.1RC2 that was originally done with CW. It backed up fine into 2.1.1. Also, restored Micro's HD Desire rom from my amon 2.1.1 backup. When I checked alternate recoveries with RM, Amon 2.1.1 showed available like before. It did not show available with the old CM6 flashed. Haven't flashing between the two from RM just for the heck of it, to see if it sticks.

Even CM6 did not show my sd ext info correctly, not even close. That shows ok now. It may have something to do with having a 512mb when I first saved CM6 and flashing onto my current 1gb sdext. It shouldn't matter, but maybe my phone is not handling it. These phones seem to behave differently for different people. Also, couldn't even run DT commands with TE while running the CM6 rom.

I am working on trying to use amon exclusively. I don't have anymore old bu's of interest from CW. Will wait for CM7 and flash from scratch using amon. Although, like I mentioned, nothing seems to work right for me with CM anymore. Not sure which gapps to flash with these final CM roms before 7. He only lists 20101014, I believe, as latest gapps.

Anyway, all ok for now.

Thanks,

Ken
[Nexus One Android Development] prettyboy85712:
20101114 is the latest I believe.
[Nexus One Android Development] :
No, 2010 12/12 is the latest with new Market. And I guess it is 20101114 not 1014, sorry.

Flashing that with CM may have been some of my previous problems. Not sure why.

I can see where running the older CM6 with the old Market could have messed with my app links that were bu'd with the new Market thru TB and were restored to the old CM6.

I am done with old CM roms and will, like mentioned, flash CM7 when and if it has New Market. Sure it will.

Either way 2.1.1 is fantastic and flows well when moving between screens and toggling sigs

Thanks Amon, again

I know I donated quite awhile back. But, will need to do it again after Christmas is paid for. :)

Ken