yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] cj chitwood:
First off, it's DREAIMG.nbh, is it not? If you misspell it here (you typed "dreaming.nbh" ), we can assume you misspell it in telnet too.

Second, do the instructions say to use DREAIMG.nbh and rename it, or to use something else? Been a while since I've done this and I'm on my phone, not a PC, so I can't easily go look for myself.

Third, you unwittingly answered your own question. In telnet, you're basically using the phone's underlying Linux command shell. So, if you mistype something, you might get a one-line response telling you how to use the command. Hence, as you typed, "usage: flash_image partition filename" (going from memory, I think I mistyped something) is telling you that you got something wrong on your command line.notice the command, "flash_image", followed by a space, then the name of the partition (I don't remember the valid names, but "boot" and "recovery" come to mind), followed by another space and the path to and name of the image file you're trying to flash.

For example, "flash_image boot /mnt/sdcard/boot.img" (this of course would have to be altered to suit what you're doing).

If you're flashing amon ra, it should be as the other respondent said (sorry, forgot your name).

flash_image recovery /mnt/sdcard/recovery.img

Of course, the filename has to match exactly what's on your sd card. It does NOT have to be "recovery.img" or "amonra.img". You just have to make sure it's an img format (as opposed to an update.zip or an nbh) and you have to make sure you get the exact name. By the way, cApitALiZAtIon matters.

Hope this helps.

--
[G1 Android Development] xanda143:
thiss needs a option to remove sig verification
[G1 Android Development] demkantor:
+1

I contacted amonra a few months back to see if he was interested in doing a final update along with some other stuff

He respectfully declined at the moment as he had other things going on, but hopefully someday he will consider it
[G1 Android Development] AndDiSa:
-1

I think AmonRa is right in not providing this feature. Why you need the possibility to flash unsigned zip files? What's the problem in providing a signed update file? The only advantage I see in that: It will be much more easy for people to brick their phones.
[G1 Android Development] demkantor:
I agree mostly, the only thing is I've been trying to build, when I test these I don't always sign, so for that it would be nice. but being the real only reason I guess it does make more sense not to as others may cause damage. but then again wouldn't it only creat a soft brick at the worst? I mean isn't it very hard to truley brick flashing a rom even if its curropt in some way?
[G1 Android Development] AndDiSa:
As log as you flash only boot / system and/or data images you are right, but if you flash recovery/radio/spl within the update zip, flashing will take place while rebooting the phone and after that it will automatically reboot into recovery. If something goes wrong or if the image doesn't work it will be a hard brick ...

... use a script which automatically packs and signs your update.zip or use adb to push your modified files.
[G1 Android Development] cj chitwood:
And if you truly, truly neeeeeeed to disable sig verification, didn't Kushik Doutta offer up a version of ClockworkMod Recovery for the G1 that included this option?
[G1 Android Development] xanda143:
This is the reason I need it of course I have apps ect that can sigjn them for me but it would be nice to just jave that fwature as I test and some of the zips I test aren't sighned as the devs dont bother to and I really just want amon ra with that feature
[G1 Android Development] AndDiSa:
Blame the devs or use adb to install them on your phone. There is no need for flashing unsigned zips by recovery.
[G1 Android Development] xanda143:
Its no vig deal but it was given in cwn the safest of recoverhies not saying your wring but the feature couldn't hurt
[G1 Android Development] demkantor:
not saying anyone is wrong as (like is said previously) for me it is a nice feature but after thinking about it more probably not a feture that should be there as for many others it could just prove to be harmfull

I can't agree that clockwork recovery is the safest, it actually has turned out to be the buggest and least "safe" for any phone/tablet I have used. as I appreciate koush's hard work I dislike his recoveries and more or less do my best not to use them. having said this I did purchase rom manager a long ways back to support him, but I have only used maybe once or twice just to test and I feel it was too expensive (should have just donated to his paypal)

rambling done...
[G1 Android Development] xanda143:
Poimt taken well what can I say except what the hec I would luke an amon ra with this feature buts maybe a moded one not the standerd as this is thanks for the input
[G1 Android Development] peschka:
Someone still keep a copy of latest recovery-RA-dream-v1.7.0.img ? I want to revive this legendary device.
[G1 Android Development] AndDiSa:
[MENTION=440464]peschka[/MENTION] I've just uploded the recovery-RA-dream-v1.7.0.img

If you need other files please let me know. I suppose I still have most of the G1 related files available
[G1 Android Development] peschka:
Thanks dude !

Everything is working like a charm now ! I found the rest of the files needed on alternative hosts around the web.
[G1 Android Development] zerolimit1:
works perfect!!! this rocks!!!
[G1 Android Development] drewdown227:
Yeah i just triead again like 6 more times and i cannot get it to flash. Im in terminal emulator and everytime i type this:

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

it just says flash_image: not found

I checked my sdcard like 5 times and the file is on the root so i cant figure out why i cannot flash it. Its probably something real simple that im missing. I am using The TMO OTA DRC83 US (Donut Inside) - NEW! 1.9.1 and have the expansion installed i dont know if this has something to do with the problem?

I also tried:

mount -a

mount sdcard

mount system

that someone posted a while back and that didnt fix the problem.

Any help with this would be greatly appreciated. Thanks.
[G1 Android Development] JROC27:
what i did was unroot then root putting RA-dream-v1.2.2

i am still new at this rooting stuff so not if u want to do all that

i use the one click root so didn't take long. :o
[G1 Android Development] |Logic|:
awesome recovery man! nice work! :)
[G1 Android Development] bkmo:
Looks like flash_image is not in the search path of the rom you are on. You will have to find it and use the full path as in /sbin/flash_image flash recovery etc., or use fastboot to flash it.
[G1 Android Development] Amon_RA:
No, this recovery has nothing to do with the rom you are currently running. It will work on for all roms. So a reflash of you rom is for sure not needed.
[G1 Android Development] jda1977:
for those on mytouch. Rename recovery img without the .v1.2.2.img portion and it works in terminal emulator for me. Since I could type everything with the keyboard but the numbers.
[G1 Android Development] skrki:
Amon_RA,

Awesome work once again, thanks a lot :cool: I have got to buy you, and other significant ones, some redbull, or beer or something..

I particularly like the fact that you can mount/umount SD card in recovery :D

Guys&Gals,

I see lots of people getting "errors" using mount -a. This command tried to mount ALL the file systems in file system table, so it may fail on some (for various reasons, not important here), hence you see some errors.

The fact is (besides the fact that you haven't searched ENOUGH ;)) all you need to mount here is your /sdcard and /system (which should be mounted automatically anyways). If you get errors "Can't find RA_recovery.img", that means probably your SD card is not mounted. So, before using files on your SD card, type mount in the shell, and check which file systems are mounted. If you don't see your SD card (/dev/block/mmcblk0p* on /sdcard), then you're gonna have to mount it. (asterisk represents a number, could be 1, could be 2, depends on the number of partitions on your card.)

Type this in the shell:

mount /sdcard
[I]Abbreviated form[/I]

To see what mount can do, check it's help:

mount --help

Second thing:

Why not try out/flash this recovery image in bootloader? Once in fastboot, open Windows command prompt and type:

[B]fastboot devices[/B]
[I]Makes sure your device is in fastboot mode, you should see it in the output[/I]

[B]fastboot boot RA_recovery.img [/B]
[I]Only BOOT the recovery, this does not make a premanent change[/I]

When you're sure you want to flash it, while still in boot loader, type:

[B]fastboot erase recovery[/B]
then,
[B]fastboot flash recovery RA_recovery.img[/B]

There you go, good luck!

P.S. Solutions like "I renamed this file to blah.img and it worked" or "Tried this a couple of times and it worked", are not solutions :P

P.S.S. My apologies to experienced users, with hope that this little guide will finally stop the clogging of this thread with questions that do not belong here in the first place... And clear things up for the new users, just cos I know how hard it is in the beginning.
[G1 Android Development] uansari1:
Any chance the next version of this could also include MikeTaylor's script to fix the auto rotate function? It would be nice if it was an item in the upcoming Recovery in a submenu somewhere. His script and other info is at the link below:

http://xdaforums.com/showpost.php?p=4424396&postcount=1481
[G1 Android Development] makethetick:
Great improvement over cm's recovery, only one thing that stands out so far though, when flashing it asks to confirm with the 'GREEN' key, not sure about anyone else but my G1 has all black and white keys on the front so that may confuse people. Most other phones have the green call answer key but ours don't! IMO it would be best leaving it how it was before by comfirming with the HOME key.

Apart from that, well done :cool:
[G1 Android Development] bkmo:
This is one I modded with a second menu option run from terminal. Type u at console prompt and you will get a menu with other options including the rotate fix.

http://www.4shared.com/file/137752446/7d5c3290/recovery-RA-dream-v122_BKMOd_2.html
[G1 Android Development] clevetbs:
this is nice.... i installed it and it works great... i have one question can there be a menu be added for view existing partitions as well.... but to top it off awesome!!!!
[G1 Android Development] bhilgeman:
Sick Sick Sick!!

Great Work!
[G1 Android Development] uansari1:
Outstanding!!! Thanks bro!
[G1 Android Development] here.david:
Easy as eating pie...:)

download - copy to SD (root directory)

(connect to PC)

adb remount

adb shell

flash_image recovery /sdcard/recovery-RA-dream-v1.2.2_BKMOd_2.img
[G1 Android Development] :
This had been working great for me, then, strangely enough, my track ball stopped working in recovery mode (though keyboard shortcuts continue to work). I reflashed but the track ball still doesn't work in recovery. It works fine one the system is loaded. Unless I'm imagining that the track ball was working in recovery mode?
[G1 Android Development] temporizer:
suggestion...

I love what you have done! Great work!

One suggestion: it bothered me when cyan first incorporated nandroid backup/restore into his recovery, when you go to do a nandroid backup, it doesn't ask you to confirm, it just performs a backup. when doing a nandroid restore, it does ask you to confirm.

it sucks because the trackball is so sensitive, if you go to do a restore you might accidently scroll and hit backup (it's happened to me twice).

Just a thought to make something great even better. IMO
[G1 Android Development] innerspace:
Very nice!

I'm digging this a lot, thanks for putting all these tools together in one spot!
[G1 Android Development] 305android:
pure genius.
[G1 Android Development] youngstacks74:
switchrom not working for me.... it says cant find swithrom.sh
[G1 Android Development] apurvis18:
flashing failure

I tried to follow directions on flashing the RA-1.2.2 recovery image but i keep getting the error message

mtd: erase failure at 0x003c0000 (I/0 error)

mtd: erase failure at 0x003c0000 (I/0 error)

mtd: skipping write block at 0x003c0000

I have root on my phone now and if i rename it, it does the same thing. The only time it will bring up the # afterward is if i do .img.img when i rename it. Sadly it will not boot into recovery mood this way. is there a problem that anyone may know how to fix? thanks for all your help ahead of time.
[G1 Android Development] ipalaus:
I tried to flashboot the 1.2.2 recovery but I'm getting:

C:\androidsdk\tools>fastboot flash recovery recovery-RA-dream-v1.2.2.img
sending 'recovery' (3978 KB)... OKAY
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)

C:\androidsdk\tools>

The problem is that I've done a fastboot erase recovery... What to do now? :S

Please help me.

Thank you in advance!

Isern Palaus
[G1 Android Development] bkmo:
Download it again and/or check the MD5sum to see if it matches.
[G1 Android Development] ipalaus:
I've downloaded twice times from different sites. If I ereased the recovery... will be possible to install another one? I booted the phone and now I'm on th OS.

Thank you.
[G1 Android Development] bkmo:
You have to erase recovery to install a new recovery image. Try and download something like cyanogens's 1.4 and see if it will flash.
[G1 Android Development] DAKIDD236:
when i try to start gparted from the command line (parted /dev/block/mmcblk0) it says there is no such file or directory.. any reasons why this happens?
[G1 Android Development] tazz9690:
this is such an improvement over the 1.2.1G Recovery Image that's over in the sapphire forums. It's great that we now have the option to wipe our ext. Just makes it easier for us lazy people :) It works flawlessly on the MyTouch 3G. Great work Amon_Ra!
[G1 Android Development] tazz9690:
you don't have to erase it. I just flashed it directly with fastboot and didn't erase my old recovery image. worked fine for me.
[G1 Android Development] griemar:
Hmm, I seem to have a issue. I have a fresh 8Gb SD card in and running cyanogen's 4.1.11.1. When I try to run the back up, i get the following error:

Error occurred during storing of app data...

tar operation failed.

Do you have enough space on the /sdcard?

As far as i know, I should have enough space. Only have 3 apps installed.
[G1 Android Development] Six6Sicks:
Anyway to edit this recovery image and the format part?

I don't like the values for Fat32, ext2, or Linux-Swap I'd like to enter my own.
[G1 Android Development] bkmo:
You can run it manually from the terminal. Just enter sdparted at the terminal prompt to get the usage of the script.
[G1 Android Development] beautifulscars:
Problem With Flash NOOBEE sorry

I go to terminal emulator in my G1 and type in the required string and I get this message

usage: flash_image [-d] partition file.img

options:

-d delete the image file after a successful flash

$

When i go into recovery mode there are only the options for cynogen and no added extras what am I doing wrong?
[G1 Android Development] lt1pnyklr:
Im trying to flash this from the terminal emulator but it wont allow me to key in numbers, only letters.
[G1 Android Development] mathewss:
unable to install new recovery image.

Only been playing with this phone a few days and this is my first attempt at fastboot so any help is welcome.

./adb shell

# reboot bootloader

# ./fastboot flash recovery recovery-RA-dream-v1.2.2.img

sending 'recovery' (3978 KB)... FAILED (remote: not allow)
[G1 Android Development] lt1pnyklr:
FINALLY!!! I got it to work after numerous attempts thanks to this.
[G1 Android Development] My_Name_Is_Neo:
Recovery Partition is independent of which version of main Android OS you are running. Think of it like self contained operating system running on a separate partition with ability to overwrite/access/modify any other partition on your phone.

When you press Home+Power it tells the phone to boot into this independent OS partition instead of main OS. like when you have multi OS computer. with Linux & WinXP running on it and you tell the boot loader which OS to boot to.

Hope this explained it.
[G1 Android Development] akycia:
A-MA-ZING!!!!!!!!!! Great job on this one, bro!
[G1 Android Development] JAWheat411:
Nice..I do like all the features. Please keep us updated on any changes.
[G1 Android Development] pathia:
I get this, if I follow your instructions when I run the flash_image command

At boot, the SPL shows instead. I can flash testkeys this way, with no issue and HOME+PWR works again.

DREA100 PV 32B

HSPL10.95.3000

CPLD-4

Radio-2.22.19.26I

Oct 20 2008

Serial 0
[G1 Android Development] k00lguy105:
mass storage mode

what exactly does this mode do? does it mount your sd to your computer in the recovery mode? so you can add files without having a card reader if your phone wont boot?
[G1 Android Development] here.david:
Do not understand what you are saying/asking....send me a private e-mail with "ALL" the facts and I will try to help you....
[G1 Android Development] mexedi:
Help - trackball fail

Help - trackball it doesnt work

[Alt+A] -->Select ROMs

trackball it doesnt work (t doesnt function)
[G1 Android Development] :
I posted that the same thing happened to me. It worked for a while, then didn't. I rebooted, and it still didn't work. Then a day later it started working again. (Of course, the trackball continued to work in the system, just not in recovery mode.) Not a super big problem, because you can always use keyboard shortcuts.
[G1 Android Development] mrnv45:
i cant install it!!

im running 4.1.999

wit the rav v1.2.1

i tried running thru terminal and it wont find it on my sdcard for some reasin..and its in the root folder!..

also if i update it wont mess up my cyan 4.1.999 right>
[G1 Android Development] staticshadow:
awesome recovery image man. thank you for this
[G1 Android Development] weezkelas:
Wow looks great im going to install now. Thank you very much sir.
[G1 Android Development] .PaNiNi.:
this is my new best friend seeing as my stupid pc wont mount my sdcard
[G1 Android Development] :
Nice work dude, installing it right now...sent to all of my buddies.

:eek:
[G1 Android Development] aaronkt:
Any chance i can get someone to email the file to me? I am at work and am unable to get to the share sites. Also the link in the one guys blog doesnt work. I would be grateful if someone would help me out here.

Thanks!

aaronkt@gmail.com

PS This should be uploaded to www.androidspin.com

someone one sent it. Thanks!
[G1 Android Development] djkrisg:
how can i erase and reflash the recovery .img?????

hey guys i am stuck on JF1.42 recovery. everytime i try and flash a new one in terminal (w/ SU), I get the response: flash_image: not found

the file is in the root of my sdcard.

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

response:

flash_image: not found

i have also tried flashing cm's recovery .img, from the terminal in the recovery console and the terminal in android.

i am at a loss. i need to flash a recovery console that is capable of formatting my sdcard w/ the proper partitions that all the current roms require. im thinking either i have to erase the jf 1.42 recovery.img first, and/or maybe it was stored somewhere different. (by a previous update.zip)

i have tried to get adb going on my pc but i get a daemon error every time. my current rom is the htc 1.6 ADB

thanks for any and all help.
[G1 Android Development] bkmo:
Maybe the JF recovery does not have flash_image available? You may have to flash using fastboot from your pc.
[G1 Android Development] rondey-:
The flash_image command uses a parameter (what to flash) after it and the path to the file you are flashing

Ie flash_image recovery /sdcard/ra1.2.2.img

From what you posted you need to add a space between recovery and the path to the recovery.img file
[G1 Android Development] djkrisg:
i had the space between recovery & /sdcard.

how do i flash the recovery using fast boot? every time i try to connect with adb on my pc i get a daemon failure, error 2 i believe.
[G1 Android Development] pathia:
mtd: write error at 0x00200000 (I/O error)

mtd: re-read error at 0x00200000 (I/O error)

mtd: write error at 0x00200000 (I/O error)

mtd: re-read error at 0x00200000 (I/O error)

mtd: skipping write block at 0x00200000

Got a little farther, I think, but still stuck at this error.

I get this when I try to flash any recovery image other than recovery_testkeys.img. Any idea what's up?
[G1 Android Development] sovereignty68:
Is RA-dream-v1.2.2 only available for Dream only? I flashed it on MyTouch 32b and it worked flawlessly.
[G1 Android Development] problem1:
this is the ****
[G1 Android Development] Hexxer:
is there a max size for swap? Today i tested around with the recover menu 1.2 and get massive problems with a automated swap size of 96mb.

I do the partitioning from within the menu and with an 4gig sdcard i get a partitioning like this.

Model: SD 00000 (sd/mmc)
Disk /dev/block/mmcblk0: 4003MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos

Number Start End Size Type File system Flags
1 512B 3407MB 3407MB primary fat32 lba
2 3407MB 3907MB 500MB primary ext2
3 3907MB 4003MB 96.5MB primary linux-swap(v1)

After this my phone wannt boot or boot only with problems (cyanogen 4.1.999), I need 5 hours to check that it could be a problem with swap. After this i do the prtitioning by hand with an swap of 32mb - after this my phone run asap stable and free of problems. Just for testing i kicked ext3/swap install swap with 96mb 8obnly for testing again)....phone make one problem after the other. Go back to 32mb Swap - perfect.

Can anyone confirm this or is there a llimit for swap? If yes the auto-partition isnt working.
[G1 Android Development] prettyboy85712:
I noticed this bug also. Is this an easy fix?
[G1 Android Development] Amon_RA:
Ok, some people told me that 96mb is what most people are using, if this is causing issues I'll change it back to 32mb (or any other value you want).

Let me know what the best swap value is.
[G1 Android Development] brownbomba:
I just had to come back and give you props for this......!!! NICE!!
[G1 Android Development] livecoslove:
Nothing

I typed those command on the terminal but nothing. my phone is my touch 3g.:(
[G1 Android Development] cingall:
just flashed straight from terminal emulator with no problems :)

RA you are the man, this is one sick recovery image.
[G1 Android Development] EWitsJan:
This recovery is fckken beast!
[G1 Android Development] kingskidd268:
Oh Snap.....

Great Job My friend...
[G1 Android Development] problem1:
you sir r the greatest
[G1 Android Development] problem1:
ust one request can you make the swap 32 mb 96 is alil too high
[G1 Android Development] Hexxer:
Ok, i tested i litle bit with my second sd card. 96mb Swap is within Cyanogen (can only say for this and only for the Dream) crap. Phone go crazy with this. Will be great if somebody is crazy enough to make his own test?

As an ide for this Recover image ? The point "reboot recovery" will be great, if you have no adb connection it helps and you dont have to do this by console.
[G1 Android Development] Burag:
Same here, I've got this bug too.

You could make 2 options - one creating 32 mb swap and one creating 96mb.

Also, some of my proposals:

Clean dalvik-cache option

Convert ext3 to ext4

Reboot back to recovery option :D
[G1 Android Development] deafptl4ever:
YES

Thank You. No one said to type su until I saw yours. Every time I tried to follow the exact instructions it would say access denied. Then after going through all the pages here I come upon your can viola it workes. I been wanting to try the other roms but not able too because of not having this recovery. ;)
[G1 Android Development] clone132:
Thank you for this great recovery. :)
[G1 Android Development] Zappza:
Why 96 MB? The optimal swapsize for BFS enabled ROMs is 64MB according to miketaylor00's benchmarks.
[G1 Android Development] raven1019:
got mirror to other website like zshare.net