yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] briangnyc:
Hi All:

Ever since flashing recovery 1.6.0 - 1.6.2 I notice that when powering on to recovery, the HBOOT check is taking a really long time as opossed to before. It used to be about 2 seconds when doing the HBOOT check, now its a matter of minutes. The info I get is this...

SD Checking.....

Loading (passdiag.zip)

No Image!

Loading (passdiag.ndh)

No Image or wrong image!

Loading (passimg.nbh)

No Image!

Loading (passimg.nbh)

No image or wrong image!

After that I get back to the main menu and I am able to use Fastboot, Recovery or whatever. It does not seem to be a problem, only I was wondering why this is happening and if I did something to cause this. Or perhaps it is a problem and I need to correct whatever it is that I did, LOL :-)

I have been switching back and fourth with Cyan and MoDaco roms. Apps2SD and not, etc.

Any help is most appreciated.
[Nexus One Android Development] craigacgomez:
This is the phone default image flash functionality. The phone scans the SD card for factory ROMs with those names to flash. If you put the entire ERD79 or ERE36 ROM zip and rename it to PASSIMG.zip, the phone will pick up that zip as ask you if you want to flash it. Just ignore these.
[Nexus One Android Development] evidenc3:
His point was it's taking minutes instead of seconds to get past these warnings and allow him to use fastboot. It's a valid concern.. it never takes more than 3s for me.
[Nexus One Android Development] craigacgomez:
Well, I think I kinda overlooked that... but yeah, I did have this problem once...

had a lot of junk on my SD card and this took forever... almost 2-3 minutes... reformatted my SD and things working fine again... guess it just took time to scan the SD card...
[Nexus One Android Development] claritoz:
awesome work! works great, no longer losing root! :D
[Nexus One Android Development] lolittle:
Great work... but when making a nandroid backup now it does not finsh :/

i shall reflash it and try again :confused:

EDIT:

Only happens on NexDesire ROM when performing Nand + ext backup :/
[Nexus One Android Development] pearce616:
tried this ^

got this > unable to chmod/system/bin/flash_image: no such file or directory
[Nexus One Android Development] myn1:
I seems have lost "root" after upgrading to RA-nexus-v1.6.0.

In terminal emulator, the command "su" will hang at SU REQUEST screen" and after a few minutes, it comes up with the following pop-up message:

----------

Sorry!

Activity SU Request (in application Superuser Permissions) is not responding.

[Force Close] [Wait]

----------

Then I upgraded to v1.6.2, but it's still the same.

N.B. I'm not sure if it's really related to recovery upgrade though.. as I also changed my ROM from CM5 to DESIRE around similar time. But in DESIRE thread, they said the problem is specific to me only.

Question: How do I get back the root?

Thanks!
[Nexus One Android Development] pearce616:
you need to turn on usb debugging.

Goto Settings > Applications > Development and turn on USB Debugging and then Reboot the phone.
[Nexus One Android Development] myn1:
HEY It works!!! I could never correlate this problem with USB Debugging!. Is this a FAQ or what? I see nobody's complaining about this problem..

A BIG Thank You!!
[Nexus One Android Development] pearce616:
im not sure where i saw it. but it worked for me too. just saw it reading on the boards.
[Nexus One Android Development] confirm045:
This method worked for me heheh thanks y'all
[Nexus One Android Development] awdlexusis:
blue care-bear

how about getting a blue care-bear version with nexus sign? that would be real real nice lol...;)
[Nexus One Android Development] AbsoluteDesignz:
having issues with switchrom and bart via ADB with 1.6.2...trying 1.6 right now seeing if that works, will let u know.
[Nexus One Android Development] AbsoluteDesignz:
annnnnd nevermind...going to try reflashing 1.6.2 since the download links for the previous versions don't exist...
[Nexus One Android Development] AbsoluteDesignz:
repartitioning SD card using your recovery...hopefully that does the trick
[Nexus One Android Development] SANTilt:
You ROCK!

I'm lovin' the carebear/X, hilarious!

Thank you! :cool:
[Nexus One Android Development] AbsoluteDesignz:
and it did not...switchrom and bart just do not work for me...luckily nandroid does...so I can use that for now.

gonna try actually flashing one of the carebear recoveries...not my cup of tea but yea.
[Nexus One Android Development] Amon_RA:
Did you read the 2 RED lines in the first post?

Always check recovery.log before posting your issues!

Please make sure that your ROM supports apps2sd if you plan to use the ext-features! (/system/sd MUST be available in the ROM)

- Please post the recovery log (use the move recovery to sd option)

- My best guess is that the rom you are trying to backup doesn't use apps2sd
[Nexus One Android Development] SPAS79:
I'm flashing 1.6.2 but it is taking forever... seems to be stuck on

sending 'recovery' <3954 KB>...

I just don't want to interrupt the process but it seems to be stuck there...
[Nexus One Android Development] SPAS79:
Ok that was just me... i didn't go into fastboot... maybe it's too early in the morning...
[Nexus One Android Development] rockingfire:
thanks, i need it
[Nexus One Android Development] AbsoluteDesignz:
EL OH EL...man...

this is a mirror image of the same "issue/solution" we had when I used ur G1 recovery image. lol. My bad.
[Nexus One Android Development] detritu5:
hy. Anyones help me? I make a nand recovery and now wifi don´t work. Can I fix this problem. Ithink i made the backup when i had 1.6.0 and now I make a restore with 1.6.2

I solve the root access problem with adb commands, but wifi don´t work.

I make a radio flah again and the problem is the same.
[Nexus One Android Development] ggrant3876:
Wifi has nothing to do with the recovery. Reflash whatever rom you are using.
[Nexus One Android Development] visitam:
Delete post please
[Nexus One Android Development] manup456:
I need this one.

http://th08.deviantart.net/fs48/300W/i/2009/203/e/0/Care_Bears_Got_High_by_stephfaith.png
[Nexus One Android Development] awdlexusis:
Lmao..I second that!!!
[Nexus One Android Development] simms22:
changed my mind on my post :p
[Nexus One Android Development] GodDriven:
Your Right.. On Your Way...

Manup your a trip.. I guess people love you all the way around.. Your Roms, Themes and then Humor.. So, how's the next drop looking... Can we have that as a boot screen, and smoke as the progress/wait bar.. LOl..

Now Thats Thinking Ahead.. :eek:
[Nexus One Android Development] manup456:
I really want the old sense boot with the droid. =)
[Nexus One Android Development] kaotikking:
+1 on that, but it should be 2 droids coming from behind the HTC logo this time, one green on one side and a cyan one on the other side. Got to step it up :D
[Nexus One Android Development] lars1110:
download links

any other links to download i hate rapidcrap i keep getting the to many people downloading error
[Nexus One Android Development] jlevy73:
Thanks for the update and including a non care bear version :)
[Nexus One Android Development] ggrant3876:
Download from one of the mirrors then.
[Nexus One Android Development] irishrally:
I also have the same questions.
[Nexus One Android Development] noodles12:
I can't find out how to do a backup with the new 1.6.2 recover.

It says do nandroid-mobile.sh in adb. But where? I do it in regular adb from my mac and it says command not found.

There is no adb in the new recovery and I tried it in the mobile terminal app and there's nothing there.

How come it's so different than the old one where just click on nandroid backup worked?
[Nexus One Android Development] irishrally:
I'm not sure I understand your issue, but when I am in recovery, I can nandroid backup like before.

Still wondering what BART is and the other questions above.
[Nexus One Android Development] noodles12:
when I do the nandroid-backup like before, it says " Error: Run 'nandroid-mobile.sh' via adb!"

And it won't backup for me. I don't know what's wrong.

Edit: I found out what was wrong. For some reason going into my sd card and deleting the old backups from the old recover (1.5.3) and then doing the backup worked. Maybe there was an incompatibility between the two.
[Nexus One Android Development] irishrally:
reflash recovery and then whatever ROM you are using. If that doesn't work then wipe first and flash everything again.

Note: I only kind of know what I'm talking about.
[Nexus One Android Development] PISSANDVINEGAR:
I try and flash anything to my recovery and get the error

C:\Users\Matt\Desktop\superboot>fastboot-windows flash recovery recovery-RA-nexus-v1.6.2-pink.img
sending 'recovery' (4030 KB)... FAILED (status read failed (Too many links))

C:\Users\Matt\Desktop\superboot>
[Nexus One Android Development] shmigao:
while you do this, is the file (recovery-RA-nexus.....img) in the same folder?
[Nexus One Android Development] PISSANDVINEGAR:
Yes. 10char
[Nexus One Android Development] shmigao:
trying to help... not sure if i am getting somewhere near

are you actually in bootloader fastboot?

i mean, i recall you have to boot into bootloader first, then select fastboot... done that?
[Nexus One Android Development] PISSANDVINEGAR:
I succesfully flashed it via my terminal, just then. Yes I was in fastboot when I tried. I get errors when trying to backup/restore via my device also, the error is "run nandroid-mobile.sh via adb!" or "run bart via adb!" which both work, I can backup using the nandroid-mobile.sh command, that works. Just nothing through amon-ra.
[Nexus One Android Development] PISSANDVINEGAR:
Just flashed 1.5.3 via terminal on my device, rebooted into recovery, after trying a nandroid backup ( 1 of 2 options, the other being restore) and it worked. ...
[Nexus One Android Development] Stea1thmode:
completely off topic again,

I heard pissandvinegar is quite a good cure for a hangover:D :D :D

Please MOD don't bar me, Its Monday morning, am at work and trying to rid myself from the Monday blues.:D:):D:)

@pissand water pls. dont take offence.
[Nexus One Android Development] PISSANDVINEGAR:
Turns out the too many links error was due to one of my usb ports being a piece of ****.

So basically 1.5.3 lets me backup OK, but 1.6.2 tells me to run nandroid-mobile.sh, i dont know why i should run that command, i did, its like a dead end.
[Nexus One Android Development] hypersonicx:
I get the same error when I try to backup on 1.6.2 also. any idea? Worked fine on 1.5.3 though.
[Nexus One Android Development] irishrally:
Is there anyway you can add more detail to the nandroid backups? Maybe the date to each file name? It seems the most recent backup is not always at the end of the list.
[Nexus One Android Development] jerhoyet:
I second that request.

Btw, does BART have to be run via adb? I've always just used Nandroid, but when I tried using BART today on 1.6.2 it wouldn't work.
[Nexus One Android Development] jda1977:
I also got this error but I believe it was because I was using nandroid/bart backup +ext but I have no ext as Im on cyanogen which does not have apps2sd, and my card is not even formatted with a ext. It works when I do just a regular backup and not one that does ext backup.. No facts, just guesses so may or may not be the answer to your problems. Just happens to be for me.
[Nexus One Android Development] packetlss:
From the top post:

Always check recovery.log before posting your issues!

Please make sure that your ROM supports apps2sd if you plan to use the ext-features! (/system/sd MUST be available in the ROM)
[Nexus One Android Development] Cuda1337:
When I try to flash the 1.6.2 recovery via cmd prompt all I get is waiting for device. It never actually does anything. I have checked to make sure the phone is connected to the cpu using the fastboot-windows devices. The serial shows up just fine, but when trying to flash the image it just hangs on waiting for devices.

The weird thing is I show a recovery option on the phone, but when I select it I get the !symbol with the android guy and it just sits there. Hrmm, any ideas?
[Nexus One Android Development] dremox:
Apply Update.zip from sdcard

Hey guys,

i'm trying to apply a self cooked rom via Amon_RA's recovery 1.6.2.

But when i try to apply it, i get this error:

Any ideas?

I have packed the rom with the kitchen from the kitchen manual in the hero forum, which is also linked here.

I know it's a how-to for the hero, but i think it's also possible to let it working for n1 right?

Please don't hit me, if i asked for a stupid question ;)

Regards

//dremox
[Nexus One Android Development] codington:
Have you tried:

Fastboot boot recovery recovery-RA-nexus-v1.6.2-green.img

Need to ensure your recovery img is good. The HBOOT recovery option is showing you the default - not the custom you are trying to flash.
[Nexus One Android Development] juju125:
Hi there,

whenever i create a backup and restart my Nexus One. the time changes and i have to connect to the internet (i do not know why) to get the correct time. this really annoys me. is this issue well known or it is just happening to me.

Thanks ...
[Nexus One Android Development] Mighty07:
Hi,

When using the included the Nandroid backup I found something that can be a bit bad.But again it more related to Nandroid than to the recovery image itself.

So I noticed that if I make a backup and the SD becomes full the backup still proceeds and states it was correctly performed.

In my case the userspace image wasn't totally completed and when I restored i got a totally unusable system.

Does anyone have seen this problem before?

Thanks.
[Nexus One Android Development] xavier7:
hi there, i might or might not have a previous version of amon ra image (v1.5.3) on my nexus one.

previously i tried to go in to recovery, instead i saw the exclamation mark in a triangle with bugdroid. i boot into boot loader (hold the trackball and Power).

and i did the following

fastboot boot recovery-RA-nexus-v1.5.3.img

does this mean that i have amon ra img in my phone?

============================

also, can i use the terminal on my phone to straightaway install latest amonra img now? (even if i dont have a previous image, or i have one)
[Nexus One Android Development] Amon_RA:
Upgrade to 1.6.2 please!!

fastboot boot recovery-RA-nexus-v1.5.3.img WILL just boot the recovery, it will not flash the recovery to your phone!

You can install from the terminal if you have root and the flash_image binary present on your phone.
[Nexus One Android Development] xavier7:
thank you very much for replying, Amon_RA!

i did it :)

tho my terminal cant input numbers, i renamed the file to recovery.img

and manage to flash it.

i'm performing a nandroid backup as i type this :D
[Nexus One Android Development] Amon_RA:
Indeed this is a known issue, I guess it would be possible to calculate the required amount of space before making the backup... I'll see what I make for a future version.

I think it's kind of normal... you restore a backup made in the past.

Why do you have a N1 which isn't connected to the internet anyway?

That's like driving a Porsche without an engine... :confused:
[Nexus One Android Development] xavier7:
backup complete :D

no more exclamation mark bugdroid when i boot recovery! yay!

thanks again Amon_RA! :D
[Nexus One Android Development] Prod1702:
Hey Amon i have a question for you. I have been getting a boot.img failed to write error since 1.6.0 when i am trying to flash a rom on your recovery. It also will not flash with fastboot as well, but what i don't get is it will flash in the ROM its self. we are talking about it over on Cyan's forums can you take at a look at this and tell me if you think it might be a bug on your recovery or if it is a problem with the rom.

http://forum.cyanogenmod.com/index.php?/topic/181-cant-flash-504/

Maybe this will help as well. it is the recovery.log file from the last time i tried to flash a rom.

http://pastebin.com/faba6PHG
[Nexus One Android Development] retaliator:
Does this recovery support the ROM CyanogenMod-5 for Nexus One 5.0.4.1?

I have flashed my Nexus One with CyanogenMod 5.0.4.1 and I have the recovery 1.5.3

But I can't see, with Linda, there is a system/sd on my ROM.

Or do I miss something else?

TIA
[Nexus One Android Development] Swervo:
/system/sd is part of using an Apps2SD mod. Cyanogen's mod doesn't support Apps2SD, at least not out of the box, you'll have to manually tweak it or use modaco's kitchen if you want that. So if you just flashed CyanogenMod and don't see /system/sd, all is working as advertised.
[Nexus One Android Development] packetlss:
(I answered it over at CM forum but I post a similar one here, good for people to know).

You got 2 bad eraseblocks on your boot partition.

Normal boot partition size 2560 kb

Each bad eraseblock deducts 128 kb useable space.

So in your case you can't flash a boot.img larger than 2304 kb.

5.0.3 used such a large boot.img that it could only be flashed on devices with 0 bad blocks, meaning quite alot people couldn't flash it.

5.0.3.1 is using a smaller boot.img that only fails if you got 2 or more bad blocks.

Both fastboot and the flash_image in recovery check for ECC errors during write to avoid using bad blocks. The one in cyanogen rom seems not to, this is not good and could explain the strange ADB issue you have (messed up ramdisk or something from flashing to bad blocks).

The solution is basically for Steve to at least keep his boot.imgs under 2304 kb. That way people with 2 bad blocks (which is fairly common) can at least flash it.
[Nexus One Android Development] bherren:
Flashed recovery image doesn't boot

Hi folks !

So I got this shiny new Nexus 1. I've tried to flash Amon's new recovery image (1.6.2) using fastboot, but hit the problem described below.

Note that the same image boots fine if I use fastboot boot <filename.img>

So I unlocked the bootloader, and then did:

benh@xxx:$ sudo ./fastboot flash recovery recovery-RA-nexus-v1.6.2.img

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

writing 'recovery'... OKAY

From there, I reboot with volume down, get the bootloader menu, press volume down again to get to "RECOVERY" and power to boot. I get the boot screen (the X and the unlocked icon) for a few seconds, then a little droid holding a "!" sign, and that's about it.

Any idea what's going on ? Are there maybe different versions of fastboot ? Any way to get some kind of log off that failed boot process ?

The phone still boots fine to it's normal android image (2.1update1) and I can reliably boot the recovery image using "fastboot boot ..." but just not boot it from flash.

Cheers,

Ben.
[Nexus One Android Development] Z51:
is there anyway we can get a custom recovery with the pedobear on it?
[Nexus One Android Development] proengin:
Hi Amon,

Is there any plan to support backup and restore of sd-ext partitions for people using ctso's snappacks?

Thanks

Patrick
[Nexus One Android Development] phonepersonality:
Nice Recovery Images Sir.

Still...If you're gonna do one with Care Bears, then you really gotta do the next one with Thunder Cats or Masters of The Universe.

Those are the rules :)
[Nexus One Android Development] rossy_k:
Nandroid restore?

Hi all,

I have Amon's RA 1.6.2. installed on my N1. I do a Nandroid backup from the handset's recovery menu and all goes fine... Now, if I attempt to do a Nandroid restore (I select the correct backup, hit the trackball to confirm) I get the message:

Restoring: .

Error: run 'nandroid-mobile-sh restore' via adb

Any idea on why the restore wont work from the handset itself? To compound matters, when I attempt to do a adb nandroid-restore to restore the backup, I get windows popping up with a "Select program to open this file" dialogue box.... (The same one you get when you try to open a file with an unknown file extension). Any idea why this is?

Thanks in advance.

Ross
[Nexus One Android Development] Amon_RA:
From the top post:

Always check recovery.log before posting your issues!

Please make sure that your ROM supports apps2sd if you plan to use the ext-features! (/system/sd MUST be available in the ROM)
[Nexus One Android Development] retaliator:
Thank you, in that case the initial posting of Cyanogen in his Nexus One Rom forumthread is not good because his advice is to install this recovery image wich not work, isn't it?
[Nexus One Android Development] Amon_RA:
The recovery image will work perfectly with the CM rom.

CM doesn't use Apps2SD, so you why would you want to use the apps2sd features of the recovery with that rom?
[Nexus One Android Development] Sim-1:
Hello there! I have version 1.5.3 of your great recovery, and I'm pretty happy with it: why should I upgrade to the newer version? Any reason I should (e.g. next ROMS cannot be installed using 1.5.3?).

Thank you! ;)
[Nexus One Android Development] rossy_k:
recovery.log

Hi Amon,

Sorry about not posting the recovery.log! Here it is...

http://pastebin.com/A96MNhSu

Just for some reference here... in my nandroid folder that the backup has been created in, there are 3 files only:

1) boot.img

2) data.img

3) system.img

Thanks a lot!

Ross.

***EDIT: OK... slight odd behavior here... I just did ANOTHER nandroid backup and the .md5 file is there now.... My only question is should there be only those three files backed up as I mentioned above?
[Nexus One Android Development] juju125:
Thanks for your reply. Most of the time i have the N1 connected but sometime i disable it to save power.

thanks again
[Nexus One Android Development] retaliator:
My apologize, I did a misinterpretation. You did a good job for the community.

Thanks!

Now I have the new recovery on my N1.
[Nexus One Android Development] Finn04:
I have the same problem (
[Nexus One Android Development] packetlss:
Try and use the latest fastboot from the SDK.
[Nexus One Android Development] Part Four:
I'm having trouble here. Can't do a BART or Nandroid backup from the recovery menu on the device. It stops part of the way through and gives an error message, basically telling me to run the commands from my PC instead. Any help would be appreciated. Thanks.
[Nexus One Android Development] JUSMEJOSE:
when input the code it give gives me a error "flash_image not found"?? what did i do?....

via terminal app -> Requires root

Copy recovery-RA-nexus-v1.6.2.img to the root of your sdcard
start the terminal app
su(press enter)
flash_image recovery /sdcard/recovery-RA-nexus-v1.6.2.img(press enter)
reboot recovery(press enter)
[Nexus One Android Development] PISSANDVINEGAR:
Same here/ Exactly the same.
[Nexus One Android Development] PISSANDVINEGAR:
http://pastebin.com/4ErFW7eP
[Nexus One Android Development] Amon_RA:
Again from the top post:

Always check recovery.log before posting your issues!

Please make sure that your ROM supports apps2sd if you plan to use the ext-features! (/system/sd MUST be available in the ROM)

It's very clear (see log) that you don't have an ext partitition, so why are you using BART?

I have the impression that you don't have a clue what you are doing, and that you just post whatever goes wrong without trying to understand or at least read things (not even your own log).
[Nexus One Android Development] landstander:
Just out of curiosity, why did you add BART to RA-nexus in the first place? I recall you mentioning at one point (in either the RA-dream or RA-sapphire thread, IIRC) that it was superseded by NAND+ext, and now included only for backward compatibility. Since the N1 is such a new device, it doesn't seem like the compatibility issue would apply in this case.

Again, I'm just curious... I'm not using apps2sd at present, and still seem to have quite a bit of space available after installing 40+ items. So it really doesn't affect me either way. :)