yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] Joe333x:
Some one posted a mirror back a couple pages
[G1 Android Development] bruce_wayne:
Thanks will have a look now. Any update on the wipe issue yet? Are people still not able to perform this?
[G1 Android Development] hjlow:
also posted a mirror at my blog :)
[G1 Android Development] uansari1:
Don't be such a drama queen... that's no reason not to flash the latest recovery!

Wipe Data is the same as the old system wipe (alt w).
[G1 Android Development] bruce_wayne:
I take back the thank you for 'helpfull' message you posted in response to my question. As I have just checked my email and have seen what the message said before you edited it.

Hope you feel stupid after pointing out what I supposedly didn't read before you had to edit your own post because you realised it was infact you who overlooked what I had posted and that I myself can read.
[G1 Android Development] bruce_wayne:
Thank you for pointing this out. Obviously it is very handy to know that wipe is the same as it always was and that it still works.
[G1 Android Development] ettr11:
my G1 just show me this when i start it and keep it nd give me error when i chose one of the options from the list...

what can i do to solve it i did format for my sdcard by the way and i try having update.zip from sdcard but :( give me error:

E:can't mount /dev/block/mmcb1k0

p1 (or/dev/block/mmcb1k0)

(Invalid argument)

Can't mount sdcard
[G1 Android Development] rbrahmson:
I got the same problem.

Running enomther TMO-OTA-US-DRC83 and TMO_1.6_ExpPack_v2.2.1 and DRC83-TMO-US_Theme_template_v2.2.1 and recovery-RA-dream-v1.3.2
[G1 Android Development] PsychoPomp:
None of the options work? Or is it just one in particular?
[G1 Android Development] michaelkecia:
Users Guide

Was wondering if there is a complete users guide for

each option and how to use it...???

Thanks,

Mike
[G1 Android Development] PsychoPomp:
@michaelkecia

Your best bet is to start reading the links in the change-log.
[G1 Android Development] JAWheat411:
Looks to me like you keep mounting SD to your pc before trying to run an update. Don't do that. That is just for copying files back and forth. Just install the update without mounting. The error states it can't read the SD because it isn't there.
[G1 Android Development] rbrahmson:
Almost exactly as bert269 wrote:

"When I try to run Bart from your new menus with 1.3.0, I get a message after a while:

Error: Run bart via console!"

In my case I get the message as soon as I select the Bart option on the new menus.
[G1 Android Development] captinamerica:
Mike,

Did you ever find a user guide? Thanks
[G1 Android Development] Fr0sTy333:
very nice. i like the new updates a lot :-)
[G1 Android Development] buzzdroidx:
Thanx!

Although the version 1.2.3 ran flawlessly for me, I am sure this one is somehow better. Thanks for your work on this and obviously the dedication to make something even better. Oh and for sharing it with us all.
[G1 Android Development] SolemnWishing:
Alright, I have a very strange question to ask. I was wondering, when making a BART backup and I hit Alt 2 to make it, will I need to press Home to confirm? At the moment my LCD screen is fried so I cant see anything and I need to back everything up by keystroke.
[G1 Android Development] droiddv:
I tried the new recovery, I do not like it!!! Just my opinion, but why on earth do you want to take 2 steps to do the same thing you can do in one step with v1.2.3. No offense but v1.2.3 kicks ass, v1.3.2 not liking it. :confused:
[G1 Android Development] rondey-:
press alt + b to get into the backup/restore submenu. then press alt + 2 for the bart backup. then home to confirm.

to be honest i would just hit alt +x, then wait a second and hit enter. from there you can use adb for bart or switchrom and get visual assurance everything is ok.
[G1 Android Development] Amon_RA:
I guess you mean the home confirmation as extra step? It's added on request, lots of people select something by accident so I added a confirmation for everything.

Maybe you should try to "run bart from the console....".

Something is going wrong and the best way to find out what is to run the script manually (you'll get more detailed error feedback that way).
[G1 Android Development] unchainedrssr:
I just wanted to correct myself on an earlier post. I just used switchrom after wiping everything and after restoring I now have everything back the it was when I saved it. I reaaly love this recovery!

Amon_RA,

Check your inbox:D
[G1 Android Development] javacody:
something strange

Please excuse me if this has been posted already.

I have the latest recovery image and when I select reboot, the phone reboots (I see the G1 screen), but it won't actually boot up. I have to give it the three finger salute to get it to reboot properly.

Any one else having this issue?
[G1 Android Development] Lou2serious:
I wanted thank AR for his work, also I love the recovery but I had no problems with 1.2.2. Since you released to new versions I had to try 1.3.2 but I don't like it. I just wanted to repair my ext since my facebook app disappeared from my app drawer but I don't know how to open the submenu for it and there isn't any instructions on the first page.
[G1 Android Development] Tempestrs4:
after i type su then flash_image recovery /sdcard/recovery-RA-dream-v1.3.2.img

i get usage: flash_image [-d] partition file.img

options:

-d deletethe image after sucessful flash

Would someone please answer what this means and why it isn't working?

I've searched the entire thread and other people are getting this message.
[G1 Android Development] jndd333:
@Tempestrs4: Are you running it through console? Terminal? ADB? please define, or try a different method of flashing image.
[G1 Android Development] Amon_RA:
- Use the trackball to scroll down to "Partition".

- Press the trackball to open the Partition submenu.

- Use the trackball to scroll down to "Repair SD:ext"

- Press the trackball

- Press HOME to confirm

(You can also use the volume keys to navigate up and down in the menu and use HOME to select something)
[G1 Android Development] webmastertroi:
I successfully flashed the RA-dream-v1.3.2. But how do I know if my apps are going to my SD Card?

When I go into Home > Settings > SD Card, I can see the partitions.

I just want to know if these settings are right:

Total Space: 6.73 GB

Avail Space: 6.00 GB

SD Card secondary-

Total Space: 572 MB

Avail Space 488 MB

Internal Phone storage-

Avail Space 64.50 MB

So what now?

Thanks! :)
[G1 Android Development] Amon_RA:
Check with your ROM dev if your ROM is supporting apps2SD or not...
[G1 Android Development] su27:
http://forums.t-mobile.com/t5/Opera...if-your-app2sd-is-working-properly/m-p/196515
[G1 Android Development] droiddv:
No I like the idea of having the home confirmation, I just didn't like the idea if I wanted to wipe, I had to open a wipe menu, then go to a sub wipe menu, then do the home confirmation. To me it was just so much easier seeing all the process's on one page, without all the sub-menu's, so to clear up what I said, I really do like the home conformation, I just didn't like to have to go to sub-menu's. Just my opinion of course. You have done extremely good work. And I am not in any way trying to offend your attempt's to improve the recovery consule. Put some cool ass graphics in the background, and leave it like v1.2.3. Then it would be perfect. IN MY OPINION.

NOTE: It is impossible to make everyone happy. You have made life for everyone a lot easier with your recovery console's!!!!
[G1 Android Development] j.books:
can't mount sd card

this is my 1st post. I usually figure stuff out on my own but I am prety much a noob and I don't know what's going on here... probably something dumb on my part.

this has never happened before, but in terminal when I enter: mount -a, it returns 3 'no such file or directory' lines. it's not recognizing my sd card. yet otherwise my sd card functions as normal.

btw, I have no partitions. any help appreciated

EDIT - ok, managed to flash the image without mounting -a. I just CDed to sdcard and flashed. I really don't know what I'm doing but somehow I always manage to make it work :D
[G1 Android Development] j.books:
I don't know why, but somehow the .img file changed its name when it got onto my sdcard. instead of recovery-RA-dream-v1.3.2.img, it ended up as recovery-RA-dream-v1-1.3.2.img. it took me a couple tries to realize that was why I wasn't able to flash it at first.
[G1 Android Development] Joe333x:
I only made a 500mb ext because it was the option that this recovery gave at the time for a one click partition. I know i will not use it all but it makes sense to keep it larger than you need to because its better to have more space than not enough. You never know what apps you might want down the road.

I like the home confirmation but I think that its over kill to have home confirmation on the usb toggle option.
[G1 Android Development] bruce_wayne:
Did you use the android spin mirror? When I tried to download that (not that it would download for me) it was named recovery-RA-dream-v1-1.3.2.img

Also thank you to CQMS13 for emailing this file to me.
[G1 Android Development] reg442:
no #'s

im new to using the terminal app, but every thing goes fine until it is time to type in the 1.3.2. it wont let me type any numbers.. am i that dumb that im missing something?? currently running cy's4.2.5 with the black bar notifacation rom and recovery 1.2.3. any help would be great...
[G1 Android Development] Joe333x:
No idea why you wouldnt be able to type numbers in terminal but you have a couple of options. Simply change the name of the recovery image file to something without numbers or boot into recovery mode and go to console to flash it.
[G1 Android Development] reg442:
i tried the console and all it does is reads (press enter) then about 15 or so white lines slowly go do the screen... i never used the console but i will rename and see whats happens.. thanks
[G1 Android Development] bruce_wayne:
Agreed. Great recovery image! But 1 page of options instead of sub-menu's would be better. Of course this JUST OPINION and at the end of the day with or without sub-menu's this is the best recovery image by far. However personally 1 big list of options is something I would prefer.
[G1 Android Development] reg442:
renamed and worked like a charm thanks... joe333x:)
[G1 Android Development] ccriffman:
Amon- your genius keeps yielding better and best stuff. This recovery is absolutely incredible. - chris aka riffman
[G1 Android Development] Joe333x:
I dont think every option would fit on one page. Which I would assume is the reason for sub menus
[G1 Android Development] bruce_wayne:
Fair point. Would it be possible to make a recovery image with two pages? That would eliminate the need for sub-menu's.
[G1 Android Development] uansari1:
Why would you want to have two pages instead of submenus? The new layout is more efficient than having multiple pages.
[G1 Android Development] bruce_wayne:
Its only a matter of opinion. Personally I would prefer to see all the options in a list than have to hunt through sub-menu's.

Like I said before great recovery image either way. So thanks amon ra for developing this.
[G1 Android Development] Lou2serious:
Ok I get it, this is brillant!! Thank you AR this helps to clean up the recovery but still have all the wonderful option available!!
[G1 Android Development] romanr:
mtd: erase failure at 0x00260000 (Input/output error)

Hey, guys, look at this:

# ./flash_image recovery /sdcard/bak/recovery-RA-dream-v1.3.2.img

flashing recovery from /sdcard/bak/recovery-RA-dream-v1.3.2.img

mtd: erase failure at 0x00260000 (Input/output error)

mtd: erase failure at 0x00260000 (Input/output error)

mtd: skipping write block at 0x00260000

# dmesg

...

<4>[ 329.885467] deinit sharp panel

<4>[ 330.528656] save exit: isCheckpointed 1

<3>[ 5670.720397] msm_nand_erase: erase failed, 0x2920000

<3>[ 5670.724304] msm_nand_erase: erase failed, 0x2920000

<3>[ 5670.728942] msm_nand_erase: erase failed, 0x2920000

# cat /dev/zero > /dev/mtd/mtd1

write: No space left on device

# ./flash_image recovery /sdcard/bak/recovery.img

flashing recovery from /sdcard/bak/recovery.img

mtd: erase failure at 0x00260000 (Input/output error)

mtd: erase failure at 0x00260000 (Input/output error)

mtd: skipping write block at 0x00260000

error writing recovery: No space left on device

# cat /dev/zero > /dev/mtd/mtd1

write: No space left on device

# ./flash_image recovery /sdcard/bak/recovery-RA-dream-v1.3.2.img

flashing recovery from /sdcard/bak/recovery-RA-dream-v1.3.2.img

mtd: erase failure at 0x00260000 (Input/output error)

mtd: erase failure at 0x00260000 (Input/output error)

mtd: skipping write block at 0x00260000

AFAIK recovery & boot don't use OOB nand data, so this should work too, doesn't it?

# cat /sdcard/bak/recovery-RA-dream-v1.3.2.img >/dev/mtd/mtd1

# cat /dev/zero > /dev/mtd/mtd1

write: No space left on device

# cat /sdcard/bak/recovery-RA-dream-v1.3.2.img >/dev/mtd/mtd1

#

I counted that block at 0x00260000 is a part of ramdisk, the one is a cpio-gz archive, so if there would be an error, ramdisk didn't unpack then.

Bit it boots and works fine!

strange... but OK :)
[G1 Android Development] jubeh:
great job on this amon-ra. I have a suggestion/request. Is there a way you could make a second fastboot backup option that prompts the user for the folder name to use? I sometimes can have around 10-15 nandroid folders backed up, and usually restoring involved moving the folder from /sdcard root to the nandroid folder (before 1.3.2) through the console. As you might imagine, managing that large amount of folders is a pain if the name is not descriptive enough (date/time stamps aren't descriptive enough), so i usually rename the folders right after creation.

I'm also suggesting it as a second option rather than replace the default because maybe other people like the way it already works.
[G1 Android Development] iskateremz:
So Awesome.
[G1 Android Development] d_bot:
just flashed on mt3g, using terminal, and the steps provided, it works great! like the instructions said. "Ignore the mount -a error you get", type the flash command exactly, hit enter, it will think for a sec then drop down a line and you are done, reboot into recovery and good to go. I love the features, especially being able to part my sd, i used to boot a VM of Ubuntu to part out my sd. GREAT work!
[G1 Android Development] BookCase:
[Recovery] [15-Nov-2009] RA-dream-v1.3.2

Very Nice, Thanx!!

:killer:
[G1 Android Development] GTIChris04:
Very nice! I like this recovery image. Perfect for when you are away from the computer. Two Thumbs Up!!!
[G1 Android Development] wettems35:
quick question...with this new recovery and the options to wipe data from ext partitions, does this mean we never have to wipe again when going to a new rom? because i have trouble deleting partitions,backing them up, etc. and its a drag to have to delete all apps and re installing them.
[G1 Android Development] cdw9800:
help

ignore figured out how to do it..
[G1 Android Development] bug666:
Ignore this post
[G1 Android Development] Amon_RA:
Updated to RAv1.4.0 :

Change-log :

v1.4.0

- Changed the item select key to CALL ANSWER-key instead of HOME-key. The HOME-key was conflicting other operations.
- Added a "Nandroid restore no recovery" option which allows you to restore a nandroid-backup without recovery (handy when you don't want to overwrite your current recovery with an old nandroid backup recovery)
- Added "Other" sub-menu :
- Moved "fix apk uid mismatches"-item from main menu to "Other" sub-menu.
- Added "Move apps+dalv to SD"-item.
- Added "Move recovery.log to SD"-item (Check this log if you want to see what is going wrong).
- Fixed the Nandroid restore menu; an error message is now displayed when no nandroid backup or device-id was found (instead of showing an empty menu).
- Removed flash submenu and "Apply sdcard:update.zip" item, because we already have "Apply sdcard:choose zip".
- Removed "Wipe cache partition" item, wipe cache is already included in the "Wipe data/factory reset" item.
- Changed UMS-toggle enable behaviour; you can not access the menu while UMS is enabled (avoid mount issues).
- Changed some menu-item labels to make the options more clear.
- Fixed UMS-toggle disable behaviour; files are now refreshed in the menu (sdcard is unmounted).
- Updated the busybox binary to 1.15.2 which has fixes for ash and hush (`trap` handling), dd (fixed handling of I/O errors), find (fix for -follow and symlinks), pidof (corrected recognition of kernel thread names), sed (SEGV), uniq (memory leak), line editing (Ctrl-D works again), build system.
- The busybox binary was :
- statically linked against uclibc (0.9.30)
- configured to preferentially execute busybox applets
- busybox --install -s installs links into /data/local/bin (JF patch)
- mount looks for loop devices at /dev/block/loop (JF patch)
- modprobe and family look for modules in /system/modules (JF patch)
- fixed an issue with vi where it would save a file as just a blank file (JF patch)
- Compiled new kernel : RA-recovery-v1.0:
- increased CONFIG_MSM_CPU_FREQ_ONDEMAND_MIN to 384000
- enabled "Support for large block devices and files" to fix ext4 issues
- removed Multimedia device drivers as they are not needed in recovery mode
- removed Network File Systems as I don't see the real need for that in recovery mode
- applied mtd6 kernel patch from Cyanogen so splash1 and splash2 screens can be backed-up with nandroid.
- added all modules to /lib/modules in ramdisk
- Updated sdparted script to v0.6
[G1 Android Development] Ace42:
O.o look at this Taylor isn't the only one upgrading to 1.4 :p
[G1 Android Development] mrnv45:
rav 1.4 + cyan 2.4.5 = 100%

always been a fan of your recoverys so simple and officialy made my phone portable! thanks man!
[G1 Android Development] sturmeh:
Amazing work!
[G1 Android Development] tehseano:
I love your work Amon, your recovery image makes things so simple, and quick, I just love it.

My only suggestion is, is it possible to remove the "sdcard:" from the flash any zip menu? Many ROM and Theme makers use long file names, and often they are too long, so when multiple versions of a zip are on the sd card, the version numbers may be off the screen, so theres no way of knowing which update you are flashing until you actually select it. Any chance of removing that "sdcard:", so free up space for file names? Every character counts :) Not to mention, where else are we installing them from if not the SD card?

Whether you use this suggestion or not, keep up the great work. I always get a little jitter of joy every time I see an update to your recovery image via my subscriptions.
[G1 Android Development] evilkorn:
Can anyone verify if BART is working...

I am trying to backup but so far the screen has filled with .... I know it can take a while based on the amount of applications etc.

Problem sorted via twitter.
[G1 Android Development] Amon_RA:
Check the recovery log and see what is going wrong...
[G1 Android Development] grandomegabosses:
Just want to say that the new update is GREAT! My only complaint though is that the home button can't be used to make selections. It made it easier to choose things cause sometimes i would scroll a wee bit with the trackball and accidentally click something i didn't want. granted, i had to press home to go further; it just cuts time, you know? :P
[G1 Android Development] DashKiller:
You can use "CALL-ANSWER key to select items" ;)
[G1 Android Development] grandomegabosses:
oops! my bad... teehee... then just ignore my previous post! great job! :D
[G1 Android Development] cityeyes:
I'm getting the same thing as you, but with nandroid. I literally backed up twenty minutes before and it completed successfully with only three lines of dots. Now I'm filling complete screens.

What was your solution? Maybe it'll help me out.

Edit: Whoops, I'm an idiot. I was still connected to computer via USB. Worked perfectly after a disconnect and reboot.
[G1 Android Development] AustinKnight45:
Thx for the update good work with all the perks in your recovery.
[G1 Android Development] aodpoe:
no recovery

I updated to RA1.4 today, was able to enter the recovery and recover to my previous bart restore(cy4.2.5) after playing around with sensehero1.4, now im trying to update to new cy4.2.6 but i'm not able to boot into recovery anymore, im stuck on g1 screen while holding home and power. i now have have to pull out the battery in order to boot to cy4.2.5 any ideas how to fix this?

Edit: fixed, had to re-install 1.4 again for some reason.
[G1 Android Development] jchico1021:
so i updated to ra 1.4 and i keep getting this error when trying to flash a new rom.

E:syntax error in update script

did i do something wrong??

EDIT: hmm...i formatted the sdcard, and also wiped battery stats and rotate settings this time, and for somereason it worked.
[G1 Android Development] JLine05:
Thank you, its working great.
[G1 Android Development] BrooklynAvi:
Thanks for the thanks but...

@Amon_RA While I was active while bart.sh was being developed as far as some testing and ideas were concerned (going back to when it was switchrom.sh), I did not, however, write any of the actual code. I noticed you had my name listed as one of the creators of bart.sh. While I'm indeed a developer, I cannot take credit for something I did not create.

While I'm sure I contributed in some small way (I can claim the reboot idea, LOL) to its development and advancement, I do not want to detract from the fine folks (devsk, dumfuq, overground, et al) who truly developed one of the greatest scripts written for Android.

BTW, thanks for the great recovery.
[G1 Android Development] Alucardis666:
This just keeps getting better ^^
[G1 Android Development] Amon_RA:
That depends on the rom you are switching too.

Som rom's require a wipe, some don't...

I can not change the way the rom devs cook their roms ;)

Why do you delete your partitions when you change rom?

You don't need to re install your apps, just backup the apps folder and restore it... or use BART (it will backup your nand + ext partition)

Credits are updated ;)
[G1 Android Development] Binary100100:
nandroid backup

I've had a couple of instances where the nandroid backup fills up with "..." and still doesn't seem to complete. I allowed the screen to fill up more than halfway be I had to do the three finger solute to reboot my phone. Usually successful with the second attempt but it's just a strange problem that I didn't ever have with the previous versions. Possible bug?
[G1 Android Development] Amon_RA:
Yes, it could be a bug.

The nandroid script sometimes fails to unmount/mount the sdcard due to a previous process still "using" the sdcard.

Do you remember which other actions you took before the "..." ? Was your usb cable still plugged in? Which pc OS do you use?
[G1 Android Development] Binary100100:
The problem occured while it was connected to the computer after installing the 1.4.0.

I read a previous post that another user had it connected to the computer. He disconnected it, rebooted and tried again which seemed to work. So I tried it and it did work.

I ported a theme for 4.2.6 and after a successful boot used adb to reboot into recovery. "adb shell reboot recovery"

I went to backup and selected to perform a nandroid backup.

My phone wasn't connected to the computer (it was on my hip)

About 5 minutes went by and I looked at it and half the screen was filled up with "........." and it still didn't complete. I rebooted it and it worked on the second attempt. I then did "switchrom -s Themed426" and that seemed to work without any problems. I haven't tried bart yet.
[G1 Android Development] anthonws:
Thank you so much for your hard work :)

Best regards,

Anthon.
[G1 Android Development] DJ Marvin:
i do not know why that when i flash rom RA-1.4 tell Me "abort" but RA-1.22 OK!!!

can you Help me???
[G1 Android Development] Binary100100:
what are you asking?
[G1 Android Development] DJ Marvin:
i use "Flash a zip update file from your sdcard" but it is not working well it show me "abort" i don`t know why?
[G1 Android Development] ThrashWolf:
Fantastic recovery image, thanks!