yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] Amon_RA:
You can't update a recovery via "flash a zip update"...

Please follow the installation instruction in the first post of this thread.
[G1 Android Development] Amon_RA:
Thanks, I'll try to reproduce the issue.

Could it be that your sdcard was mounted when you used the adb shell reboot recovery command?

When did you unplug your usb cable? When it was booted into recovery or right after you entered the adb shell reboot recovery command?
[G1 Android Development] ERamseth:
Wipe Battery Stats

Exactly what stats are wiped by wipe battery stats? Is it the status of what is using the battery? Does this undo or re-do "battery conditioning" (full drain, then full recharge as is often suggested by various people/sources)?

(searched the forum and this thread and didn't find any real answers)
[G1 Android Development] billquinn1:
It removes /data/system/batterystats.bin After that you should leave it charging until it reaches 100%.
[G1 Android Development] ERamseth:
If I get a new battery, then, I should probably wipe battery stats then charge the battery until full?
[G1 Android Development] lt1pnyklr:
No release for MT3G?
[G1 Android Development] AustinKnight45:
I think what he's talking about is that when he try's to "Flash a zip from sdcard" like CM v4.2.6 or anyone that he is going to flash, when you select the rom you want it goes like this.

Install : SDCARD:update-cm4.2.6

-signed.zip?

Press HOME to confirm,

any other key to abort.

Installation aborted.

Without you pressing home to start the update it just goes to abort real fast, but if you go back to "Flash zip from sdcard" it will flash the rom, this only really happens the first try this has also happened to me on CM's recovery.
[G1 Android Development] uansari1:
Amon_RA... thanks for the new Recovery! I'm a fan of your work. :)

I have a quick question... BKMO modified your v1.3.2 release so that running BART from the Utility menu in console would skip restoring the Recovery partition of an existing backup. Have you incorporated that change into v1.40?

Thanks!
[G1 Android Development] down8:
Thanks for the update, RA.

I like the sub-menus. Seriously, if you're actually "searching" through submenus, maybe you shouldn't be playing with this stuff. Everything is very well labeled.

My ¥1.7,

-bZj
[G1 Android Development] cephaus:
best recovery image ever. i wish that you could put names on BART back ups :( maybe we can put a bunch of names into a .txt file and choose one for each back up? i hope that makes sense.
[G1 Android Development] uansari1:
Start using BART from console by typing in "utility" and picking option 7. It will ask you to name the backup. Not as simplified as using the main menu, but there's MUCH more control. That's the tradeoff between the main menu and doing it "manually" through console.
[G1 Android Development] bkmo:
I just downloaded the 1.4 recovery and took a look at the nandroid-mobile script for you. It is configured to backup/restore the recovery image. I am going to change it again, and also add an option to use sdparted in interactive mode from the utility script. I'll upload it and change my signature when it is done.
[G1 Android Development] uansari1:
You, my friend, are really an asset to our community. :)

Thanks!
[G1 Android Development] Joe333x:
just updated and want to say geat job! I like the new usb mass storage toggle much better than the previous version, and now you can never forget to turn usb mass stoge off. Keep up the great work
[G1 Android Development] Amon_RA:
See changelog and features in my first post...

I implemented a new option in the backup and restore submenu called "restore no recovery"...

Just use the norecovery parameter for restoring. Changing the nandroid script will break my no recovery restore option in the menu.
[G1 Android Development] enomther:
def great job man

@Amon_RA

I just gotta say man excellent work. I absolutely love 1.4 :D

I'm struggling to find anything to suggest to improve it now! Keep it up man.

~enom~
[G1 Android Development] tiggerbcn:
Thank you very much for this grear program, but I have a problem and it's with the option Wipe Dalvik cache, there me does not work, goes out for me a message that he says:

Error: Run 'wipe dalvik' via console!

How is it done by console?

Thanks

PD: It was happening also with the previous version of the Recovery
[G1 Android Development] bruce_wayne:
Not knowing where to find something (as it is in a submenu)

And not knowing what something does are two different things.

And as for 'playing with this stuff' well that's yet another different matter that is frankly laughable.

Not knowing where to find something is not an issue anymore thanks to the lists of submenu's on post 1. So thanks Amon for this and yet another great recovery image. Keep up the good work.
[G1 Android Development] bkmo:
I didn't see that. I will restore nandroid-mobile to default, and then add norecovery to the bart restore command in my script. Thanks.
[G1 Android Development] michel-xda:
Just installed but still have BusyBox v1.15.1 instead of v.1.15.2...
[G1 Android Development] Crios:
[Alt+0] Nandroid backup :: Make a Nand backup (including Splash) *UPDATE

it is possible include into next recovery release a SPL partition?

Tks...

:-)
[G1 Android Development] uansari1:
Thanks for the response. I prefer the verbose and more manual method of using BART through BKMO's utility menu. It allows me to see what stage the backup or restore is on, and allows me to name the backup, which is key for me as I try out a lot of ROMs and customizations.

I'll try your "mod 2" version. I currently have your "mod 1" version and while running Amon_RA's backup from main menu worked fine, BART would hang where it was dumping system.img when run through the Utility menu...

Hopefully that is the cause?

Edit: Just tried your newest version, but BART still hangs at system.img. It was working fine in your v1.3.2 modded version.
[G1 Android Development] devitocoke:
Amon, I love your work, especially the MS USB toggle. Thanks, you are awesome.
[G1 Android Development] karthikjr:
Fantastic!

The new "Flash zip file" option from root is awesome.

In 1.3.1, this option was buried under sub menus.

And I kept wondering who had any use for the

"Flash update.zip" option. Thanks for perfecting

an already amazing recovery.

And yes, the USB toggle. Mad props! :)
[G1 Android Development] Amon_RA:
I'm currently working on v1.4.1 which hopefully will fix the nandroid issues some are experiencing.
[G1 Android Development] ID#:
Wipe hangs, bug

The USB-Toggle is awesome!

The recovery hangs, every time i want to wipe dalvik-cache or the ext-filesystem.

It wipes, everything seems to work fine, but after wiping it hangs.

Factory-reset works fine!

It's only with dalvik and ext.

I'm on G1.
[G1 Android Development] Charrion:
Compatible with EBI1?

I've searched through this thread and can't find any reference so here goes, does anyone happen to know if this recovery will work with the Rogers Dream using the EBI1 radio? So far, the only recovery image I've found that will work is the 32a version of CM 1.4 that is available on zenthought.org. I'd like to try RA since it has some very nice features but I haven't had a lot of luck getting any other recovery to work.
[G1 Android Development] jrm1508:
dont know if this was discussed before but when i updated from your last version and next time i went to it, it changed back to the last.
[G1 Android Development] DJ Marvin:
i follow the installation instruction but it can't flash <AOSP_ADP_1.6_r1.4_DRD20_rooted_base_v2.zip>,Now i have to use RA-1.2.2 to update !:(
[G1 Android Development] tq745:
hey amon will you be updating the recovery image for the mt3g also? or can we use this on it too?
[G1 Android Development] enomther:
Yup ... gonna have to agree man ... very nice brother!

~enom~
[G1 Android Development] IConrad01:
Mount -a not necessary.

Booted quick as could be.

Awesome stuff. :)
[G1 Android Development] Thats BS:
No, but you can flash it through the terminal emulator after you put it on your sd.

su

flash_image recovery /sdcard/recovery-RA-dream-v1.2.2.img

Very nice job sir! Thank you.
[G1 Android Development] jabbawalkee:
This wont work on mytouch huh??
[G1 Android Development] big nu:
Exactly where do you type "bart" i did it in recovery img. console

and got not found.. do i flash this whole file like the original? via terminal?

:confused:
[G1 Android Development] kingskidd268:
Oh snap i just crapped in my pants.... This is the Dream come true. get it Dream... I can die a happy man....
[G1 Android Development] brownbomba:
I flashed it in the recovery console.

Thanks.........
[G1 Android Development] bkmo:
You have to re-flash the image I uploaded to get bart functionality.
[G1 Android Development] kirkcody:
Where is adb in recovery ? What letter or number is it on the menu
[G1 Android Development] Apaca1ypse:
now with BART!!!

RA, you are a GENIUS my friend! Thank you for this! Thank you to bkmo for the bart (and all the previous devs who made this possible). :D:D:D
[G1 Android Development] Dror520:
so do I need to type mount -a or just the flash_image line? thanks!
[G1 Android Development] Reignzone:
There isn't any reason that this will not work on the MyTouch 3G.

Essentially, it would be no different than all those of you who had Cyanogen's v1.4 recovery image that had the optional console access.

I'm going to flash it regardless and see how this looks.
[G1 Android Development] skaterA223:
questions

NOOB question do i flash this like any other recovery.img (in terminal)

and if i have all three partitions do i have to delete all of them like haveing a frash sd?
[G1 Android Development] tq745:
ima try it too...let you know how it goes...
[G1 Android Development] :
Thanks for the instruction!
[G1 Android Development] ransome:
This is a awesome recovery but I noticed one problem. The BART UTILITY does not work with this recovery but on my other G1 that still has CM Recover 1.4 the BART UTILITY does work.

I just tried to use BART with each recovery.img and it only will work with the CM recovery.img

Is there something that you can do to add bart to this recovery because it has so many options compared to switchrom.

Bart Util

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

Otherwise this recovery image ROCKS!

Edit- Oh I just noticed some uploaded a version with bart, I will try it and report back

Originally Posted by bkmo

Here is Amon_RA's super awesome recovery image with the BART backup script added to it. Jyst type bart at the recovery console.

http://bit.ly/Nhfl4 MD5SUM e5af7ade77116af16d0a578e547187e7
[G1 Android Development] bkmo:
Just for you I have re-upped a new version with a deldalvik command added. This is a quickie until Amon_RA can possibly get it added to his recovery image.

http://xdaforums.com/showpost.php?p=4648192&postcount=62
[G1 Android Development] bkmo:
I have already added it for you. Use this until Amon_RA can get it "officially" added.

http://xdaforums.com/showpost.php?p=4648192&postcount=62
[G1 Android Development] tq745:
okay, flashed it on mt3g with no problems...everything seems to be working fine. obviously we can't go into terminal though...but that's why we got adb. anyway nice, keep up the good work amon. love that you included switchrom too. no more nandroid for me.
[G1 Android Development] adacali:
exactly the same...
[G1 Android Development] FiFTYSiX:
so proper!

thank you for the wipe's and formats saves SOOOO much time!
[G1 Android Development] pcigre:
Is there Magic 32A port?
[G1 Android Development] Amon_RA:
Can you try to boot the Magic 32A version (recovery-RA-magic-v1.3.2H.img) of this recovery : http://xdaforums.com/showthread.php?t=530492
[G1 Android Development] Amon_RA:
A recovery will not change back by itself, it's probably your current rom that is flashing a recovery at boot (check /system and /data for recovery images), or maybe you restored an old nandroid that containted the old recovery...
[G1 Android Development] AbsoluteDesignz:
real issues starting now...I can't use switchrom (built in version, haven't tried the script itself) to backup and maybe even restore anymore (afraid to try and restore)

it gets stuck on storing nandroid backup forever...im going to try reflashing the recovery then I'll report back, but damn :-\
[G1 Android Development] Amon_RA:
See post #783 , I'll update the recovery soon with a fix.

Try to make sure nothing is mounted when you make a backup (so boot clean without cable attached to pc and run backup).
[G1 Android Development] AbsoluteDesignz:
WOW @ the super quick reply...came back to reply saying that I fixed the issue by reflashing the image...but yea...nice work.
[G1 Android Development] Charrion:
Just tried both the H and G versions, neither would boot.
[G1 Android Development] Swervo:
I hadn't seen this specifically mentioned as something that happens with the "backup never finishes" bug, so I thought I'd post it.

I've been running the bart backups from the console via 'utility'. I boot into recovery, run the backup, and it always ends up hanging while backing up either system.img or data.img. If I reboot from there via call + menu + power and boot back into recovery again, then the backup works perfectly, it just always fails the first time through. It's a perfectly usable workaround for now, but hopefully that'll help narrow down what the issue is.

Fantastic recovery image btw!
[G1 Android Development] uansari1:
I mentioned the same issue a couple pages back. I also use BART from the Utility menu so that I can name each backup so that I can flash back and forth from various ROMs when I'm playing around. On my phone, it hangs at the system.img step. Hopefully this will be fixed by Amon_RA soon.

I also think that BKMO's modification to the script to exclude the recovery partition from BART is a good idea. Otherwise it will keep reverting to whatever the backup contains.
[G1 Android Development] embracelb:
nandroid back up question.

running Nandroid Backup takes forever now, i get a full screen of ...... everywhere & it still hasn't finished. I'm assuming it's taking longer cause it's including splash? Is the time it takes to finish normal? Cause it's taking a really really long time. Just curious? Cause I'm just running a Nandroid Backup cause I'm about to flash CM Rom 4.2.7 & I usually run a Nandroid Backup but it's never ever taken this long. It's now been running a nandroid backup for 15+ minutes & still hasn't finished. The dot's are continuing to move along the screen.

ps. i've gone back &edited this post 3 times to change the time duration. it went from 5+ minutes to 10+ to 15+ in which now, im going to just pull the battery out &say forget a nandroid back up & just flash CM Rom 4.2.7
[G1 Android Development] el-zilcho:
I had the same problem . When I deleted all the old nandroid backups except the most recent , it fixed the problem .
[G1 Android Development] uansari1:
Why not just go back to the v1.3.2 recovery until Amon_RA fixes this one?
[G1 Android Development] Amon_RA:
This issue has been reported by a few other people already (see previous post) and I'm trying to fix it.

Just do a clean boot into recovery and try again.

Someone also deleted all previous nandroid backups and that worked for him.

Others reformatted their sd and that also solved the problem...

Unfortunately only a handful of people reported this issue, all the others don't seem to have a problem...

I'm trying to figure out why some have the issue and others don't (I can not reproduce the issue myself).

It would be very handy if people who have this problem gave a bit more information :

- Do you have enough space on your sdcard?

- Did you do a clean boot into recovery and immediately ran nandroid backup or did you do some other actions before?

- Is your sdcard mounted?

- Is your phone connected via a usb cable to your pc?

- Which rom are you using at the moment?

- How is your sdcard partitioned?

- Are you using ext4?

- What is the class of your sdcard?

- How many nandroid backups are already stored on your sdcard?

- What does the recovery.log file indicate?

- Do you have the same problem when you run nandroid manually?

- Do you have an engineerings SPL?
[G1 Android Development] prettyboy85712:
This actually just happened to me right now.

- Do you have enough space on your sdcard?Yes

- Did you do a clean boot into recovery and immediately ran nandroid backup?Yes

- Is your phone connected via a usb cable to your pc?Yes and used Dual Mount SD prior to booting into recovery.

- Which rom are you using at the moment?CM 4.2.7.1

- Are you using ext4?No, ext3

- How is your sdcard partitioned?w/out swap

- What is the class of your sdcard?6

- How many nandroid backups are already stored on your sdcard?Delete all prior to start.

- Do you have an engineerings SPL?No, Hard SPL

Resolved problem by rebooting, deleting Nandroid backup folder and starting over again.
[G1 Android Development] lotherius:
Wow, just updated from several versions old of RA Recovery, and I must say, this is much cleaner and more professional. Also, I didn't have any problems performing Nandroid backup.
[G1 Android Development] Swervo:
- Do you have enough space on your sdcard? I believe so. I've got 3.5 gigs free of an 8 gig card.

- Did you do a clean boot into recovery and immediately ran nandroid backup or did you do some other actions before? Clean boot and immediately hit alt-X to go to console, ran utility, and ran a bart backup. (which appears to do nandroid, and it looks like it's during the nandroid that it locks up)

- Is your sdcard mounted? I can't speak for the other times, but I just repeated my normal process and no, it's not mounted at the time I start the backup.

- Is your phone connected via a usb cable to your pc? It was the first time I did this a week or two ago, it hasn't been since then.

- Which rom are you using at the moment? A few of them, namely cyanogen's 4.2.6, AOSP eclair 1.9, SenseHero and KingClick's Hero (mostly focused on cyanogen's and the aosp, the others were just quick looks)

- How is your sdcard partitioned? FAT32/ext3/swap

- Are you using ext4? Nope, ext3.

- What is the class of your sdcard? Class 6

- How many nandroid backups are already stored on your sdcard? I have 5 bart backups and 12 nandroid backups. I had no bart backups when this first started happening, however.

- What does the recovery.log file indicate? Right now, just some information about moving the recovery.log to the SD card. I'll try to get ahold of it when it's actually got pertinent information...where is it normally stored when it's not moved to the SD?

- Do you have the same problem when you run nandroid manually? Haven't tried to run it manually outside of the 'utility' app from the console. I can try manually, but I don't know that I have any documentation on how to run it.

- Do you have an engineerings SPL? I have the Danger/Death/1.33.2005 SPL (or whatever it's being called this week).

Hopefully some of that helps, thanks!

Edit: Just as an experiment, I went into recovery, went to the console, and immediately did the call + menu + power reboot into recovery again, then ran the backup. Worked fine the first time, so maybe there's something special about the call + menu + power reboot vs. powering up from off?

Edit Again: No idea if this is related, but I just had another lockup on system.img and then got a kernel message saying: [ 134.028259] Disabling IRQ #26.
[G1 Android Development] embracelb:
I might try running it again, after I maybe delete all nandroid backups. Not really into wiping & doing the whole reflashing just cause I have no problem with my flashed CM Rom, I suppose I can live w/o a nandroid backup until it's fixed.
[G1 Android Development] bert269:
Nandroid backup loops here too

This actually just happened to me right now.

- Do you have enough space on your sdcard? Yes more than 1.9GB

- Did you do a clean boot into recovery and immediately ran nandroid backup? Yes

- Is your phone connected via a usb cable to your pc? No - not connected at all

- Which rom are you using at the moment? CM 4.2.7.1

- Are you using ext4? Yes.

- How is your sdcard partitioned? Fat32/Ext4/Swap

- What is the class of your sdcard?6

- How many nandroid backups are already stored on your sdcard? One - which I do not want to loose - I will rename the directory for testing.

- Do you have an engineerings SPL? No, Hard SPL
[G1 Android Development] bkmo:
I cannot reproduce the bart/nandroid issues no matter how hard I try. I have many backups, ext4, class6, and the cable connected to the computer but not mounted or adb connected. Works perfect every time from a phone reboot from the cyanogen rom reboot phone. Works perfectly from the main menu,or the utility menu for me. This only happens to some, and it only started with the new kernel.
[G1 Android Development] BigJPR:
Hiya guys... quick question.

I tried coming off cm 4.2.7.1 to try one of the hero roms. I did the fools mistake of partitioning the sdcard before flashing (I know...I know) and ofcourse now I can't get into my phone because I did a wipe and the an ext wipe.

I tried to use the "mount usb storage" from this recovery and nothing happens. I also tried restoring the nandroid backup and ofcourse... I guess I deleted it when partitioning...but on previous times it would tell me to run a command from console because of an error and it would run it and it will give me another error.

Back to topic. I don't have a card reader, but I do have my wifes g1 (mines a g1 too). I tried to do it thru adb (which I'm not experienced in) by pluggin the phone in recovery, cmd on winxpsp3-adb shell and another long command that starts with "echo" and its supposed to get me the usb mass storage drive on xp, but nothing happens eventhou I am on the # and in adb devices I show my g1.

Now that the details are on the table, am I doing anything wrong on amons recovery in order to enable the usb mass storage? Is there anything I could do or try?

Thanks guys. And when I fix it... would using that other backup utility be my only other backup option to nandroid at this moment?
[G1 Android Development] BigJPR:
Sorry for double post... I'm on the phone and can't find a delete button.
[G1 Android Development] xallyx:
question?

ive just got the new rec to the root of my sd...

ive been having horrible issues with my sd and need to reformat and whatever but my phone keeps saying cant read sd... which is why im not sure if i need to reformat/repart, it says healthy on my pc lol and im able to see all my files and folders.

so to go in the terminal and do that flash, it needs to read from my sd? im so confused, and ive done all this rec/flashing/root/partition sd, like a year ago with the exception of getting on xrom and now cyan ive never had an sd problem...

and if it doesnt take in the terminal it wont mess my phone up?

omg i feel so stupid, just want to do it right the first time =/
[G1 Android Development] xallyx:
ahhh i get this....

$ su

# mount -a

mount: mounting /system/modules/modules.sqf on /system/modules failed: No such file or directory

mount: mounting /system/xbin/xbin.sqf on /system/xbin failed: No such file or directory

# flash_image recovery /sdcard/recovery-RA-dream-v1.4.0.img

error opening /sdcard/recovery-RA-dream-v1.4.0.img: No such file or directory

#
[G1 Android Development] Amon_RA:
First 2 "warnings" after mount are normal (those depend if sqf is implemented in your rom or not).

The error after flash_image means that it can't find "recovery-RA-dream-v1.4.0.img" on the root of your sdcard. Are you sure that you copied it correctly?
[G1 Android Development] xallyx:
I Just got it on there =) after a i took the sd out and put it back in, kinda had to do a blow in the sd slot like old nintendo, maybe that helped idk... Im sooo excited lol I did it all on my own!! haha... im just trying to figure out the parting im already parted like this i have a 8g but the person who help me...

fat32 0 7377

ext2 7377 7889

linux-swap 7889 8014

it was something like -512 -128 +518 and i see this 32 in place of 128 everywhere so im not sure of this... if u can help me ill buy u a 12 pack lol
[G1 Android Development] aiiao:
simply amazing!