yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] vegetaleb:
Ok weird thing it says:

FAT32: 6.46gb

EXT2: 488MB Used: 50MB Free: 0

Other: 488MB Used 488MB Free: 0

While I ma pretty sure I upgraded to Ext3, could the original Ext 2 splited to Ext2 and Ext3?
[Nexus One Android Development] tufeijoe:
Where to download your latest source code?

This recovery is great but not work for all mobile, i want to build one for my phone.

Can you share or tell me your email?
[Nexus One Android Development] Robdyx:
I've heard 2.3 is finally out, is there a stable version or still in beta 3? Where can I get it?
[Nexus One Android Development] roxtedy:
Hello, I have problem, when I format SD card in recovery 2.2.1 I can not use SD card in Windows 7. I have SD card reader but I cant format, delete SD card, is it some solutions?
[Nexus One Android Development] jayjay1234:
Restore on another Device

Hello XDA,

I have a question that I don't know if anyone can answer. I was wondering if it's possible to made a backup on a my N1 and restore it on another N1. When I tried to do it I keep on getting an error:

Oops... something went wrong!

Please check the recovery log!

"I:Set boot command"

I checked the log and it said the same thing.

If I can't do it that's fine, just need to know to clear my mind.

Thanks,

Jay
[Nexus One Android Development] temasek:
The nandroid backup folder name is your device name. So its basically device specific.

Workaround

1. New n1 create a nandroid backup. Then delete its contents, leaving the folder intact.

2. Old n1 copy the contents of the nandroid backup to new n1 nandroid backup folder

3. Restore nandroid from new n1

Done!

Have fun. :)
[Nexus One Android Development] jayjay1234:
WOW what a quick reply. Thanks, will give this a try and report back.

Update

OK it worked so now I don't need to start all over on my other N1.

Thanks temasek
[Nexus One Android Development] techmagyor:
Is there a chance to get a format system section (like /system and all other internal memory directory) in the recovery?
[Nexus One Android Development] ZeroXtreme:
i'm not sure if beta versions are posted here, but here is the listing of androidspin.com's Amon_RA recoveries:

http://files.androidspin.com/downloads.php?dir=amon_ra/RECOVERY/

I only see version 2.3 for the HTC supersonic at this point.

NOTE: Try clicking on the "Modified" column header to sort the releases by date, you will see the latest releases easier this way.
[Nexus One Android Development] uoY_redruM:
I haven't updated since 1.7.0.1 LOL (I was using PSFreedom for my PS3 but just recently decided to stop hacking).

My question is, how do you theme the recovery? I'd love to create my own backsplash for my own personal use.

Anyone have any information on how to do it?
[Nexus One Android Development] uoY_redruM:
Anyone have any information on this?
[Nexus One Android Development] bahathir:
Feature request or suggestion:

It will very convenient if this recovery image has the 'REroot' feature. This feature will come handy, if you already 'rooted' the Android OS, but when we update with official OTA update, the suid permission of /system/bin/su will be removed by the installation scripts. So, to REroot is when we want to change the /system/bin/su file permission to 4755, after the /system is mounted.

Refer to my post in this thread.

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

I think it can be implemented easily into RA recovery image.

Thank you.
[Nexus One Android Development] daveid:
My trackball does not scroll downwards, using CW recovery I can fully navigate with the volume keys the menus. I wanted to try RA recovery for a little while (to test Nandroid backup/restore feature differences) but it is very hard to navigate only being able to move up. Is there any way you could make the navigation similar to CW? Whereas the volume keys as well as the trackball scroll up/down, the power button is used to return to a previous menu - instead of volume down... Or am I asking too much?
[Nexus One Android Development] sputnik99:
I am looking desperately for a stock recovery for nexus one SLCD. I want to revert before sending it back to HTC for repair.

I know there will be the non-stock and unlocked bootloader but that can't be helped. I want to have as much "stock" experience as possible (just had to part from my beloved custom rom).

Thanx
[Nexus One Android Development] efrant:
Just pull the recovery.img file out of the FRG33 shipped ROM here: http://www.shipped-roms.com/index.php?category=android&model=Passion (Nexus One) and flash it using fastboot.
[Nexus One Android Development] dryphi:
Let me start by saying I love Amon_Ra. So easy to use and so functional.

But can we

please

get a "permanent", meaning auto signature verification disabled, option?

It would be awesome so we could get OTA updates. I've always been a rom guy, but lately I've been on an official 2.3.3 (with superuser access and amon_ra recovery of couse) kick.

Thats all. Thanks.
[Nexus One Android Development] efrant:
Just use v1.9, it has signature verification off.

Sent from my Nexus One
[Nexus One Android Development] Amon_RA:
Signature verification = off doesn't mean you can flash official OTA updates.

An OTA update will patch a previous stock version, so if you changed something to the stock image (rooted boot, custom recovery, etc...) the patch will fail and you'll corrupt your rom. Always return to 100% (recovery included) stock to apply an ota update.
[Nexus One Android Development] DaveKid:
I keep getting an error whenever I attempt a backup. Something along the lines of "oops, something went wrong". I've checked the recovery log but don't really know what I should be looking for.

I'm on CM7 RC1

thanks in advance for any help someone can provide
[Nexus One Android Development] temasek:
Reboot and back to recovery again. It should work now.
[Nexus One Android Development] DaveKid:
Tried that already. Unfortunately didn't have any effect.
[Nexus One Android Development] temasek:
I had that once during backup and I just reboot to ROM and back to recovery. It worked for me.
[Nexus One Android Development] mtw4991:
Make sure you are either plugged in or have battery greater than 30-35%, I think.
[Nexus One Android Development] uoY_redruM:
^please, information anyone?
[Nexus One Android Development] Foxwolfe:
I would also be interested in how to do that, missed out on the old carebear recovery :P
[Nexus One Android Development] dryphi:
Yeah I know, thanks though. I flashed a stock 2.2.2 and the new hboot. Then my phone notified me about an OTA update, which I elected to download. The installer rebooted my phone into the recovery to complete the install process, at which point it was halted because the update (from Google) wasn't signed.

I ended up having to download a stock 2.3.3 and flash. It wasn't a big deal, but providing the option to set a default setting for the signature option in Amon_Ra would be useful and an easy change.
[Nexus One Android Development] Amon_RA:
Google updates are always signed...

Please see my previous post, if you want to flash updates you should return to full stock including stock recovery before you update! You didn't return to stock recovery...
[Nexus One Android Development] temasek:
Amon_Ra

I really love your recovery. Its been my only recovery. May I ask if you will update your recovery for n1 to enable formatting system partition? Its the only option missing and much needed by many.

Thank you very much. :)
[Nexus One Android Development] Amon_RA:
Yes, I'll bring it to the same version as the supersonic recovery when I find some time.
[Nexus One Android Development] temasek:
Great news for all n1 users of your recovery!

Thanks! :)
[Nexus One Android Development] dryphi:
You're right. I didn't want a stock recovery. And it's working fine.

Anyway I was trying to follow this post:

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

So I flashed a stock 2.2.2, HBOOT, and the latest Amon_Ra because I read elsewhere that Amon_Ra now has the ability to turn signature verification off.

Then when the phone downloaded the OTA and rebooted, it got to the recovery and Amon_Ra gave me an error, something along the lines of "cannot flash due to signature verification" (don't remember exactly what it said).
[Nexus One Android Development] efrant:
I don't think you are understanding. A custom recovery like the latest Amon_RA can only flash stock Google OTA updates IF and only IF you go into the menus manually switch off signature verification. It is not off by default. If you do not do this, it will not work.

P.S. If you want a custom recovery with signature verification off by default, flash Amon_RA version 1.8 or 1.9...
[Nexus One Android Development] dryphi:
I do understand that. My whole point here is requesting the option to turn signature verification off by default. If the recovery had that option, it could flash OTA updates.

You're right, I should have flashed 1.8 or 1.9 at the get-go but I didn't realize this was an issue. I figured the latest Amon_Ra would have the same functionality as an old one.
[Nexus One Android Development] efrant:
Again, I don't think you understood. The latest Amon_RA does have the same functionality as the older version, and it does allow signature verification to be turned off. It is just set to ON by default. You can easily turn it OFF.
[Nexus One Android Development] dryphi:
Right. But what I'm saying is, if you had the option to turn verification off by default, it could flash OTA updates in a totally automated manner, which would be slick.

Edit: I didn't know where the OTA downloads to, so I couldn't go and find it to flash after turning signature off. I had to instead download and flash manually.
[Nexus One Android Development] temasek:
Still u don't seems to understand.

To flash OTA updates, u need a stock everything including stock recovery. U cannot flash OTA updates using custom recovery.

Edit: my bad....ignore this post. :p
[Nexus One Android Development] efrant:
No, it is you who doesn't understand.

NO, you do not. You can flash OTA updates on stock ROM with a CUSTOM recovery if you turn the signature verification off. I have flashed every OTA update with a custom recovery...
[Nexus One Android Development] dryphi:
Thank you, efrant. You can, and I have as well.
[Nexus One Android Development] GldRush98:
lol wrong. That is the point of turning off sig verification, so you can flash OTA's with non-stock recovery. Tons of us did it with the GB OTA.
[Nexus One Android Development] temasek:
My bad. :)

Been sometime since I flashed back stock and try stuffs. Lol......
[Nexus One Android Development] Amon_RA:
If the OTA update patches the recovery you better have the stock recovery or else it will fail... not all OTA updates patch recovery. To be safe it's better to flash everything back to stock (including recovery), do the update in stock recovery and flash a custom back after the update.

I always make a nandroid recovery of everything with a custom recovery booted (not flashed), that way I have a backup of everything stock (stock recovery included). When I want to flash an OTA update I restore everything back to stock (except for data.. depending on the update) and apply the update from stock recovery. Right after the update I boot (not flash) a custom recovery and make a new nandroid (for when i want to flash the next ota update). You can use boot.img from this nandroid to disable secure and flash superuser with a custom recovery.
[Nexus One Android Development] dryphi:
How do you boot a recovery without flashing it?
[Nexus One Android Development] temasek:
Fastboot boot recovery.img

Assuming your recovery is renamed as recovery.img
[Nexus One Android Development] efrant:
Obviously you are much more knowledgeable than I, but from my experience, an OTA update does not patch the recovery. That is why OTA updates don't fail if you have a custom recovery, as the package does not verify the recovery partition before proceeding. The OTA does, however, verify the system partition (as well as sometimes the boot partition) before preceeding, so if you have files missing, the OTA update will fail.

Moreover, what the OTA update does, is write two files onto the system partition: /system/recovery-from-boot.p and /system/etc/install-recovery.sh. These two files are responsible for re-flashing the stock recovery upon every boot (which is why the OTA update does not patch the recovery per se - it adds the two files which will insure the stock recovery will be reflash as soon as you boot into the ROM).

As I have said previously, since FRF91, I have received every OTA update and installed them via your awesome recoveries (either v1.8 or v1.9). I just make sure I flash ChainsDD's Superuser package before I reboot, and I keep root access. Then as soon as I boot into the ROM, the stock recovery is flashed. So I just delete the two files mentioned above, and reflash you recovery.
[Nexus One Android Development] Tdj.fr:
restore in progress since 5 hours

Hello,

I use RA Recovery v2.2.1 on my N1. I make a backup and now wnat to restore it : the restore is in progress since 5 hours, is it normal ? Can I stop it ?

Thanks in advance,

David.
[Nexus One Android Development] baseballfanz:
Shouldn't take more than a few minutes. You can reboot into recovery and try again
[Nexus One Android Development] dryphi:
I just flashed a stock 2.3.3 image and my recovery is still Amon_Ra after multiple reboots. I did not delete those two files mentioned.

I did, however, flash su.zip immediately after flashing the rom. Maybe su.zip deletes these files for you while granting superuser access?
[Nexus One Android Development] efrant:
Could very well be. I've never used that file. I've only used chainsdd's superuser zip

Sent from my Nexus One
[Nexus One Android Development] dryphi:
Well here it is if you're interested:

http://xdaforums.com/showthread.php?t=968396
[Nexus One Android Development] Tdj.fr:
I reboot and start the restore again, and take only few minutes (and phone starts).

Thanks,

David.
[Nexus One Android Development] Amon_RA:
Ok, true, in that case flashing from a custom recovery should work fine.
[Nexus One Android Development] ZeroXtreme:
Still accustomed to AR Recovery...

At this point, until Amon_RA releases the new version for GB, I use a very crude method for flashing various types of files such as ROMs, Themes, customized apps, etc. As I noticed some .zip files require certain scripting that ClockWork's recovery supports, so I switch recoveries as required. An easy method is to use ROM Manger where you can easily switch between CW and AR recoveries, but I am more accustomed to the fastboot method.

Basically I use AR's recovery for everything unless it fails to do something right, which is usually flashing certain .zip files. But for everything else like backup, recovery, partitioning, etc. AR's recovery still does the job solid.

Just sharing my thoughts...
[Nexus One Android Development] serg2k9:
Hello, i had a rooted N1 before, but over a week ago i sent my n1 for a hardware repair and i needed to reinstall root and recovery.

I already have root, but when i try to install recovery from fast boot i get this message

C:\SDK\tools>fastboot devices
HT9CWP813218 fastboot

C:\SDK\tools>fastboot flash recovery recovery-RA-passion-v2.2.1.img
sending 'recovery' (3380 KB)... OKAY [ 0.470s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.913s
[Nexus One Android Development] Amon_RA:
Did you fastboot oem unlock already?
[Nexus One Android Development] serg2k9:
DOH! Forgot that part, thanks.

Edit: just tried to oem unlock

C:\SDK\tools>fastboot devices
HT9CWP813218 fastboot

C:\SDK\tools>fastboot oem unlock
... INFOErasing userdata...
FAILED (status read failed (Too many links))
finished. total time: 14.033s
[Nexus One Android Development] fcisco13:
The probably put a spell on it!

N1
[Nexus One Android Development] serg2k9:
I know there is that way but i would like to install it this way.
[Nexus One Android Development] efrant:
Since you already have root, just download flash_image to your device, place the recovery image in the same directory, and open a root shell (either via adb on your computer, or on the phone) in the directory that you placed both the files. Then just type flash_image recovery name-of-your-recovery.img
[Nexus One Android Development] serg2k9:
I was gonna do that until i rebooted after it failed, the boot-loader said

Unlocked

i found that to be weird, but nonetheless i got it.
[Nexus One Android Development] Amon_RA:
Kill adb or any other process trying to communicate with your phone.

Reboot your phone into hboot again and try again.
[Nexus One Android Development] gregferns:
Hi all,

Ok. I have the same thing happening to me also.

I was on STOCK 2.3.3, no root. Hence downgraded to Froyo, rooted and then flashed Nocturnal mike's rom. My bootloader is locked and i prefer keeping it that way ( my reasons ). I did the flashing via clockworkmod recovery. When i tried to flash Amon's recovery via adb it gave me above error. I tried it through the terminal and it gave me a mount error.

When i flash Amon's recovery from CWM it flashes successfully but after that if i try booting into recovery it gets stuck at the X.

Don't know whats happening.. Am very used to Amon's recovery so want to flash that,,, and especially since CWM above 3 is giving problems....

Any help ?? And pls guide me on how to give logcats etc.... i can try ( if the logs are there :) )
[Nexus One Android Development] efrant:
How are you flashing via ADB? If your bootloader is locked, you cannot use fastboot commands... You need to download flash_image, push it to your device/sdcard, put the recovery in the same directory and then, in an ADB sell (or terminal on your device) type:

su

cd the-directory-where-you-placed-the-files

flash_image recovery name-of-your-recovery.img
[Nexus One Android Development] gregferns:
Thanks efrant. Will try this, but does the file have to be pushed? Will it be ok if I just copy paste it to sd card?
[Nexus One Android Development] efrant:
That'll work fine.
[Nexus One Android Development] gregferns:
Hi efrant,

It gives me an error when i try from the terminal app on the phone

" mount: Device or resource busy

mount: Device or resource busy "

Can you tell me what's to be done ?

thanks

greg
[Nexus One Android Development] efrant:
Take me through the steps of what you are typing in a terminal, and what the response is on each line.
[Nexus One Android Development] gregferns:
Start terminal, it shows

sh-3.2$

Then i type

su {enter }

it displays

sh-3.2#

Then i typed

cd /mnt

cd sdcard

ls -l ( it showed me all the files on the card including flash_image and the recovery file )

Then i typed

flash_image recovery recovery-passion-RA-v2.2.1.img

it replied -

mount: Device or resource busy

mount: Device or resource busy

I think i have to do some mount RW commands for it to be

successful as maybe the device is in RO mode while being used.

Would be helpful if you or anyone else can help.

thanks

greg
[Nexus One Android Development] efrant:
I'm not sure what the problem is. The only thing different I do than what you did is cd /sdcard, not cd /mnt/sdcard, but I doubt that's the problem. You don't have to mount anything as r/w when using flash_image.
[Nexus One Android Development] gregferns:
I did that also and tried.. It is showing me the same thing.
[Nexus One Android Development] temasek:
Read this under section for locked bootloader

http://xdaforums.com/wiki/index.php?title=Nexus_One/Recovery_Images
[Nexus One Android Development] efrant:
temasek is correct. Forgot about that. You need to put flash_image into /system/bin and change the permissions on it, so just follow the directions in his link to the wiki.
[Nexus One Android Development] gregferns:
Thanks to both you guys temasek and efrant

Finally managed to get it done, although struggled a bit

in following the commands.

In the wiki it mentions unmount sdcard before typing in

the commands. But when you do that it gives errors.

Mounted it again, typed the commands and that did it.

thanks

greg
[Nexus One Android Development] temasek:
Great job! Welcome onboard! Next thing for u is to decide what rom to use. Lol. :D

I'm using Cyanogenmod Rom - best of all roms available!
[Nexus One Android Development] gregferns:
Thanks, but i am on board from a long time now.

I had a N1 where i had unlocked the bootloader, sold it

and got a new N1 with LOCKED BL. The unlocked had CM, MODACO

MIUI etc etc..

Now from the time i rooted with CWM i use nocturnalmike's rom. It's

quite good and fast. had also flashed the HC port onto this one. Its good but will wait for that also to be done nicely. Waiting for the gr8 cyanogen to finish the wonk issue, then will shift to CM7 nightlies.

But all said and done,, thanks once again,,, nothing like being part

of a community where nobody is made to feel dumb... :-)

Edit : Forgot to supplement the fact that CM is the best rom ever :-)

regards

greg
[Nexus One Android Development] temasek:
Ah ic.

Anyway welcome back to rooted community. N1 STILL ROCKS! ..... at least till end of this year. Lol :)
[Nexus One Android Development] gregferns:
Thanks. Y till the end of the year? I still find it the best after the slew of phones and tablets coming up. But there will always b something better. Ciao
[Nexus One Android Development] Lazat:
My trackball decided to stop working yesterday, so now i cannot use amon-ra ;( is there anyone that can help me how to use it from the adb connected to the compi??

commands to; wipe data, dalvic-cache, cache, nandroid backup, nandroid restore. and also functions like format sdcard and partition and upgrade to ext3 and ext4?
[Nexus One Android Development] SiNJiN76:
Wondering what to do if a restore doesn't restore all apps on sd card (froyo style). Is there a way to fix that? I tried fix permissions hoping...but no luck...Maybe it's because I used Rom Manager's gui to do it? (I use 2.2.1 Ra, but use Rom Manager to auto start a flash). Or was it just a bad backup/restore?
[Nexus One Android Development] :
You must restore with the same recovery you back up with.
[Nexus One Android Development] SiNJiN76:
Yeah...I did. Oops, I just meant that I ran fix permissions using Rom Manager.
[Nexus One Android Development] clozecall:
My bootloader is also locked and using this link I tried the "For locked bootloader - flash_image using ADB only" method but encountered an error.

As soon as I type the first command "adb shell" I saw deamon tools do something then it says "device not found"

-I have android sdk installed in my documents, oddly though my adb was not in the tools folder, but rather in the "platform-tools" folder

-I have nexus one drivers installed via this method.

-Once I do step 7, my phone restarts with my screen displaying /

!

\ and an Android guy next to it, not sure if thats even supposed to happen.

Anyone know what I'm doing wrong? The instructions on both locked bootloader steps are a little vague, such as when exactly do I plug in the phone into the computer.
[Nexus One Android Development] daveid:
Really, the easiest thing to do is to use Clockwork, as it allows navigation with the volume keys. That is assuming that you can still press the trackball in to simulate a "click". My trackball does not roll downwards (or it does, but it doesn't actually register any movement downwards), so I am stuck using Clockwork as a recovery.
[Nexus One Android Development] Hollow.Droid:
Try this, download a terminal application such as terminal emulator from the market. Place the recovery image on your phone and rename to recovery.img (Making sure not to name recovery.img.img if known file extensions are hidden). Start TE and allow it root permissions. Then type the following:

- su (Just to confirm root permission)

- mount -o remount,exec /dev/block//vold/179:1 /sdcard

- cd /sdcard

- ./flash_image recovery /sdcard/recovery.img

- reboot recovery

I found that an easy way to enter these commands was through using chrometophone and simply pasting them into the terminal. Good luck :)