yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] ESKIMOn00b:
You can proceed any valid URL with the wget command and it will try to download the file to your PWD (present working directory)
[G1 Android Development] Rmag37:
I can't get your little tip working I reverted to rc29 and downloaded telnet what I'm getting is:

#wget: not found

# # wget http://n0rp.chemlab.org/android/cm-recovery-1.4.img

Btw I searched for busybox on market but I found nothing. I can't download steel either.

new problem, i cant open the terminal now i try to connect to the default localhost 23 but it keeps getting refused

so right now i have three choices

1. i can save the link of the recovery image and rename it from .asc to .img

2. i can figure out how to work the tether app and download the recovery img on my laptop

3. i can forget the recovery img and do without.

i would prefer option 1 but if someone can explain the tether app ill gladly take option 2.
[G1 Android Development] anon1ski:
im kinda stuck here, i've pushed a couple recioverys so far and now im stuck conmpletely. im trying to push it in console and it keeps saying error opening /sdcard/cm-recovery-1.4.img:no such file or directory found....

i know its there. im looking at it as i type this....
[G1 Android Development] xidominicanoix:
could it be that you have the sdcard mounted?
[G1 Android Development] killerspaz:
First off, many thanks cyanogen...

Only bug I've been able to find is that if you go into console, then run the "recovery" script to restart the menu system, then hitting console again causes a lock..

Now for a few minor requests :D

Haptic/Audible feedback on ready/action complete(when done flashing, etc). I often do an action and forget about it for 10-20 minutes do to side tracking, and I remember when I need to make a call.. Which obviously requires a flash and then initial boot time...

Have the update.zip flasher also search /sdcard/download for when using the browser to download... Actually, could this be converted to a "find" for all zip files? I couldn't imagine there being that many on one's sdcard to clutter the display.

Maybe load an image placed in the correct place on the sdcard for the bg?

I know these requests aren't entirely trivial, and probably low on the priority list for taking on new requests... but you'd have one happy camper here!
[G1 Android Development] anon1ski:
i've tried it under ALL circumstances lol.

on another note, my superuser doesnt work and ive been told its a problem with cyan's 1.3(wich im currently running) and when i try to push the image through the terminal emulater it says bla bla permissions bla bla bla. so i try to SU it and hence my su doesnt work, on ANYTHING requiring SU acces.
[G1 Android Development] newtothegame:
I seem to be having the same issue but am sure I am missing something obvious. When I go into recovery and then into console, type SU enter and then type in the flash_image command I get the "not found" message. Since I can use a file manager on the phone when booted up and see it under /sdcard i know it is there. Back in recovery-->console I can ls right after SU and see the directory, if I do ls /cache I see a directory listing but if I try ls /sdcard it just comes back /# which I'm guessing means it doesn't see any files.

So sorry for the noob question but do I have to mount the /sdcard in console to run this command? Or am I really having a problem?

*******************************

EDIT: never mind. I assumed that I could not do this from terminal but I did and it worked fine.
[G1 Android Development] skilo0918:
problems flash recovery img

I been following the threads but i still get the fill not found error, I cant use the downloading method neither is there something that is wrong with recovery image 1.2 or do you have to type more then flash_image..... because I been tryin everything and I cant even get it to work if I use terminal emulator I get usage info and then it says options [-d] delete image after successfull flash but i keep checking and nothing, can someone explain the process for me because I had this same problem with image 1.3. thanks
[G1 Android Development] anon1ski:
any one have any ideas on my SU problem? if i can fix that ill probably be able to do the rest thru trial and error
[G1 Android Development] dilfatx:
Just did a backup with the new version.. it backed up fine..(or so i thought)

Went to do a restore and got error each time.. told me to do it through command line (terminal)
[G1 Android Development] gmon187:
man awesome recovery
[G1 Android Development] AngryCookieMonster:
Re Pimped Out Recovery Image.

Great Work on the new recovery image. now its not so boring anymore:).

took a minute sec to understand how to flash it, but i kinda like the way this one is applied dont have to rename to update and reboot phone.

worked flawlessly in terminal. now to go and play chicken with cyanogens 3.9 rom.:eek:
[G1 Android Development] xidominicanoix:
what was the exact error?
[G1 Android Development] pensive:
When I saw this post, I decided to test it out.

1) I flashed the 1.4, no problems

2) I made a backup through the UI, no problems

3) I restored the backup I just made, no problems

4) I rebooted, still no problems.

Hm. I at least cannot recreate the problem you describe.
[G1 Android Development] question.com:
i have the exact issue. now im running 3.9.1 and cant restore to a stable build.
[G1 Android Development] beedroid:
wonder when the dev will set a feature to allow which backup image to restore..?? i've tried Cyanogen and Amon_RA but they just restore the latest image. Is there a way around this to choose which backup to restore ??

e.g I have backupB installed on phone and want to install backupA

When in recovery utility, the backup restore, restores most recent backup. When I move backupB out of the sdcard and leave backupA, backupA won't restore.

help please thanks!
[G1 Android Development] skilo0918:
can you help me

I been having the same problem and I just keep gettin the same error image file not found, so when i do it with terminal emulator it gives me the usage info and then options [-d] delete afther flash but I dont know if i have to do anything else or is there something else i have to do before I put the flash_image recovery/sdcard/cm-recovery-1.4.img command because the first post says just to put that but I really dont know how to do it and im stuck at 1.2 because I couldnt even get it to work with 1.3 is there a thread or something that explains how to do from beginning to end. I would really be greatful if you help me out because no one seems to be helping me with this and I can't find instructions exept for flash it just like jf image.
[G1 Android Development] pensive:
Use the console

Assuming you are running recovery 1.4

nandroid-mobile.sh -r --subname backupA

You may have a problem with the backup itself though.
[G1 Android Development] beedroid:
would you know how this is done on the magic?
[G1 Android Development] pensive:
Magic?

I thought this was about a problem with the new cm-recovery-1.4.img.

Again if you are running the 1.4 version cm-recovery on your magic you can

do that. If not, I have no idea what you have there.
[G1 Android Development] Lou2serious:
I cant download the recovery through firefox says something like "page load encoding error unsupported compression type"

Don't know what that is but is there an alternate link????

Thanks
[G1 Android Development] sha.goyjo:
For those of you that can't seem to flash it, the only time I've ever gotten such errors is when I'm typing incorrectly. Make sure you are copying the code from the first page of this thread VERBATIM.
[G1 Android Development] beedroid:
what im trying to say is how you do it on the magic, because you can't run commands when in system recovery mode...we don't have a keyboard to enter the command you gave me.
[G1 Android Development] pensive:
Same recovery but no keyboard?

The only other thing you can do is to connect using "adb shell" from your PC, while phone is in recovery 1.4. And then run the same commands.

That means you need to have the USB drivers installed, adb installed.
[G1 Android Development] Rmag37:
I think i only need one more answer.

how do i get the wget command to work?

i enter in:

wget http://n0rp.chemlab.org/android/cm-recovery-1.4.img

what i get back is:

wget: not found

i dont understand lol. Please explain why this is happening instead of downloading the img like its supposed too. I'd be even more grateful if you could tell me how to fix it.
[G1 Android Development] beedroid:
what terminal are you using? im using google terminal emulator you download from the market and wget works fine :) try the terminal im using.
[G1 Android Development] Rmag37:
When i run it through the "Terminal Emulator" it tells me access denied. same with some of the other terminals.

Disregard my previous questions I got everything figured out.Huzzuh!
[G1 Android Development] offcina:
please explain!

in the first post its written:

To install image: copy it to your sdcard and run:

Code:

flash_image recovery /sdcard/cm-recovery-1.4.img

i tried it lots of times and didn't work, then i find out that if i copy the image to the root of the SD and then

"fastboot flash recovery cm-recovery-1.4.img"

it works first time.....anyone with problems with flashing the recovery, try this!

can anyone please explain me why is this? where did i go wrong? is it ok to do it this way?

another thing: it would be nice to put this thread in the magic forum too, or at least mention that it works great in the 32B Magic too!!!
[G1 Android Development] pensive:
A lot of people seem thoroughly confused.

flash_image is a command available on the Android OS itself (on the phone)

fastboot is a command that is available on a PC (if you installed the SDK, and that is a task in its own right, have to install the USB drivers)

and it would work if and only if you have fastboot mode available on the phone, i.e. the appropriate bootloader is already installed and put into the fastboot mode.

In the former case you need to copy *.img file onto your phone first before

you can flash it.

In the latter case fastboot copies the *.img into the phone and flashes it.

Apples and Oranges.
[G1 Android Development] elgortiz:
is there anyway to get a recovery image that has the option to MOunt via USB from the recovery itself? just so that u dont have to go back to ur rom just to mount and then put on whatever new rom you want?
[G1 Android Development] goldenarmZ:
Drop into the recovery console and type this:

echo /dev/block/mmcblk0 > /sys/devices/platform/usb_mass_storage/lun0/file

when you've copied your stuff over, just type:

reboot recovery
[G1 Android Development] anon1ski:
ughh. this is killing me now. even if i wipe,re-flash or try a new rom my SU is completely smashed.
[G1 Android Development] ajthornton52:
cyanogen - you are the man. This recovery image is fire. No more need to rename to update.zip. Thanks for the contributions.
[G1 Android Development] clefster:
I know with previous recovery images it was recommended you copy it to /system as well, so that when it automatically reflashes the recovery image it will use the new one.. is this necessary still?
[G1 Android Development] SexualChocolate:
Im having an issue as well.

I also first attempted to type the image_flash command from the recovery console and as the others stated this did not work. I saw mention of using the terminal to do it and I received a permission denied message as well. The card is not mounted, so I'm not sure what the issue is.
[G1 Android Development] Proxin:
The image_flash command didn't work for me either, I flashed using fastboot and it worked, no worries.

If you want to check it to make sure it worked, reboot your phone while holding the Home button. If you see a new Recovery layout and more options, then you flashed it correctly.
[G1 Android Development] Pfeffernuss:
The ability to flash ANY zip is... A W E S O M E ! :eek:

No more renaming, no more keeping up which update.zip on the SD-card is which Rom... This ROCKS!

For peops who update their Roms "regularly" (:cool:) this is SO handy. Thank you very VERY much!!!
[G1 Android Development] media_:
worked for me in terminal emulator no problem!
[G1 Android Development] glock30:
I don't know if it was already suggested, but maybe a way to choose which nandroid backup to restore would be cool. Just an Idea.
[G1 Android Development] jamizzal:
wait so with alt+a we will be able to choose any .zip file on the phone thats a rom to flash ??? :D
[G1 Android Development] kockroach:
If you would have looked at everything in the first post....you would have found at the end, cyanogen's todo list.
[G1 Android Development] xidominicanoix:
Yes.......
[G1 Android Development] glock30:
I read the first page when I first flashed it... guess I just forgot... my apologies... :rolleyes:
[G1 Android Development] skaterA223:
still new to rooting and every thing but do i just flash like normal alt. s or wipe first then alt s pleas help and can it be done on any rom
[G1 Android Development] temporizer:
I don't know why you guys are making it harder for yourself. just do what cyanogen said in the FIRST POST!!

so, reboot into recovery, drop to console (alt-x) and type

ums_enable

to mount the fat32 partition on your pc

and

ums_disable

to unmount.

way easier than the above option, don't ya think?
[G1 Android Development] perdid0:
Nandroid backup error?

anybody having a problem with nandroid backup. i flashed the new recovery image and it was great but now when i try and backup it starts then it says

error running nandroid backup, backup not performed.

i thought maybe it was an issue with the recovery image so i flashed back to 1.3 ......same problem......the weird thing is it is happening to my brothers g1 as well.

EDIT: This always happens to me. i look all day for the answer then i decide to make a post. then i figure it out. dooh! (in case anyone was interested my sd card was full from all my backups!)
[G1 Android Development] pensive:
That is why there are new options now

nandroid-mobile.sh --delete --subname 200905

will offer to you backups to delete from May.
[G1 Android Development] anglisano:
installing recovery image

I went to terminal emulator and typed in "flash_image recovery /sdcard/cm-recovery-1.4.img" but what do I type on the next line?

Im a little new here. thanks for your help

NEVERMIND. THX
[G1 Android Development] thebowers131:
i did this and now i cant get to recovery screen. what do i do?
[G1 Android Development] pensive:
It has been suggested only a zillion times. That is why I tweaked the nadroid script.

If you feel comfortable enough dealing with command line you can ALREADY

do it by using the nandroid-mobile.sh script, which the UI calls with default

options now. You can label backups with --subname option like so

nandroid-mobile.sh -b --subname MYFUNKYLABEL

and restore like this

nandroid-mobile.sh -r --subname FUNKY
[G1 Android Development] pensive:
Is it a state secret what you specifically did?

If you want, need help, you at least must share with the folk here what it is you allegedly did.
[G1 Android Development] xidominicanoix:
Please read the OP next time.

You copy the file to the root of your sdcard

Open up terminal

Type "flash_image recovery /sdcard/cm-recovery-1.4.img"

Done
[G1 Android Development] downloadsking:
i must say im impressed with this recovery image no more renaming thanks
[G1 Android Development] mrmonto:
This new recovery image doesn't have an option to partition your sd does it? I've had a hell of a time trying to re-partition with paragon.
[G1 Android Development] devsk:
nandroid-mobile.sh --help still shows 2.1. You can't tell if you are dealing with newer version (supposedly 2.2) or older, which is 2.1....:(
[G1 Android Development] DMaverick50:
yes you can partition your card with this recovery image. if the commands arent in the op then you can find them in the first post of the "jachero 2.7.4..." thread
[G1 Android Development] RTX:
i cant flash 1.4

error openning /sdcard/.... no such file or directory
[G1 Android Development] pensive:
Umm, true. The version change was not anticipated.

That said, however, 2.1 did not have a --help option, so you know you are

dealing with 2.2.

I've attached the up to date version with the version change, also since the current recovery kernel does not populate splash1, splash2 images, adjusted backup legend marking to reflect that.

Until the next recovery release, however, it is kind of painful to use this fresher version just for the correct revision number. You would have to keep it on the sdcard and then do this in recovery

cp /sdcard/yourdirectory/nandroid-mobile.sh /sbin

chmod 755 /sbin/nandroid-mobile.sh

before you run it.

So, I would just wait for the 1.4.1.
[G1 Android Development] DOHCtor:
Hey Pensive, are we still able to do the old fashion nandroid-mobile.sh restore /to/my/saved/directory ?
[G1 Android Development] pensive:
Yes, but slightly differently.

You can override the default backup/restore path with --path

Specifically,

nandroid-mobile.sh -b [--subname YOURLABEL ] --path YOURPATH [-c|--compress|--bzip2 -LEVEL]

if restoring

nandroid-mobile.sh -r|--restore [--subname YOURLABEL] --path YOURPATH

use -b for now, --backup is not being processed correctly, -b means the

same thing, do a backup.

--help helps.
[G1 Android Development] DOHCtor:
OMG so confusing. I tried using the old fashion nandroid-mobile.sh restore /to/my/paht (nandroid-mobile.sh restore /sdcard/nandroid/tmobile/<where the .img files are located along with .md5>) But with this new nandroid-mobile.sh it keeps returning jibber jabbish.

What do I have to type exactly? I'm thinking about going back to the old Cyan recovery image.
[G1 Android Development] alapapa:
love the new options!

is there any way to turn on the keyboard backlight from the recovery console?

I do most of my hacking at night
[G1 Android Development] pensive:
Confusing? I thought clear as day.

nandroid-mobile.sh -r --path /sdcard/nandroid/tmobile
[G1 Android Development] DOHCtor:
ummm... help...

/ # nandroid-mobile.sh -r --path /sdcard/nandroid/tmobile
nandroid-mobile.sh -r --path /sdcard/nandroid/tmobile

nandroid-mobile v2.1

/sdcard/nandroid/tmobile
Using G1 keyboard, enter a directory name substring and then <CR>
to find matches or just <CR> to accept default:

Using string to search for matching backup directories

Looking for the latest backup, will display other choices!

Default backup is the latest: /sdcard/nandroid/tmobile/nandroid.md5

Other available backups are:

/sdcard/nandroid/tmobile/boot.img
/sdcard/nandroid/tmobile/recovery.img
/sdcard/nandroid/tmobile/misc.img
/sdcard/nandroid/tmobile/system.img
/sdcard/nandroid/tmobile/data.img
/sdcard/nandroid/tmobile/cache.img

Using G1 keyboard, enter a unique name substring to change it and <CR>
or just <CR> to accept:

Restore path: /sdcard/nandroid/tmobile/nandroid.md5

/sbin/nandroid-mobile.sh: cd: line 780: can't cd to /sdcard/nandroid/tmobile/nan
droid.md5
error: /sdcard/nandroid/tmobile/nandroid.md5/nandroid.md5 not found, cannot veri
fy backup data
/ #
[G1 Android Development] DOHCtor:
Well, I downgraded back to 1.3.1 so I could utilize the fail-proof way of restoring images in different directories. Too bad it flashed the backed up recovery image, now I'm back to 1.4 :(

/# nandroid-mobile.sh restore /sdcard/nandroid/tmobile
nandroid-mobile.sh restore /sdcard/nandroid/tmobile
nandroid-mobile v2.1
Restore path: /sdcard/nandroid/tmobile
Verifying backup images...
boot.img: OK
cache.img: OK
data.img: OK
misc.img: OK
recovery.img: OK
system.img: OK
Flashing boot...
flashing boot from boot.img
Flashing recovery...
flashing recovery from recovery.img
Erasing /data...
Unpacking data image...
end of image
Erasing /system...
Unpacking system image...
end of image
Restore done
/#
[G1 Android Development] pensive:
Ok, you were not clear what path you use.

nandroid-mobile.sh -r --path /sdcard/nandroid

Apparently you named the directory tmobile.

Yep, life is complicated when one applies options randomly.

nandroid-mobile.sh --help

actually has useful info if one is willing to read it.

By the way, --norecovery

would have suppressed the flashing of the recovery partition.
[G1 Android Development] DOHCtor:
Yea, I move the backups into directories according to the rom i use. I have another directory named cyan (/sdcard/nandroid/cyan/<backup images>).

As you can see in the other post, the 1.4 recovery, even though it found the images, couldn't verify the .md5 file. Wassup with that?
[G1 Android Development] DOHCtor:
I spent almost an hour reading the information in --help and utlizing the proper commands and still no give.
[G1 Android Development] pensive:
The path was wrong.

--path specifies the path upto the actual backup directory.

So, it is --path /sdcard/nandroid

not --path /sdcard/nandroid/tmobile

It could not find the *.md5 file because the wrong path was given.

It will then present choices of

/sdcard/nandroid/cyan

/sdcard/nandroid/tmobile

and whatever else you have there.

And when the question is asked you enter:

cyan -- if you want that or

tmobile -- if you want tmobile

dude -- if you had it

jfreke -- if you have that one.

As an alternative you could do this instead if you know already which one you want.

nandroid-mobile.sh -r --path /sdcard/nandroid --subname tmobile

it would restore then the tmobile backup.

Clearer?
[G1 Android Development] devsk:
Hey Pensive, are you willing to subsume the script I have at http://xdaforums.com/showpost.php?p=4209412 ?

What it does is that it backs up app* dalv* folders from ext partition, creates a tagged folder of this backup and the corresponding nandroid backup.

Moreover, it hides the nandroid options (I noticed --backup is broken at this time) behind a simpler interface where you just tag the backup with a name.

Have a look!
[G1 Android Development] pensive:
Have a question first.

The reason I did not add the ext2 backup is because it did not seem to make sense to me to backup one partition to another partition on the same sdcard. If the sdcard gets trashed, both get trashed.

I have backed up my ext2 in its entirety, tar -cvzf somefile.tgz /system/sd and then pulled off the archive from the sdcard onto my PC.

My thinking was that backing up the ext2 would make sense when and if

ftp is available so that one can push out the backups to distant ftp servers.

Tell me what the rationale is to backup ext2? It is already on the sdcard, right? Is it because the apps you have for the different ROMs are different?

--backup is broken, need to use -b.

p.s. Although I do not have very many apps, the ext2, even compressed takes up 35meg.
[G1 Android Development] devsk:
The reason for writing that script was not to backup the system against a failing card. The reason was to get an ability where I could test out as many ROMs I wanted but still could bookmark the ones which I liked on the way. And I could switch to the stable most liked ROM at any time. That's why its called switchrom....:D

I now archive my switchROM folder to PC once in a while.

The strength of the script lies in simplicity (just switchrom -s <rom_name> to store and switchrom -r <rom_name> to restore) and exhaustive error checking. For example, I discovered while testing that nandroid script did not like the fact that /sdcard was already mounted, it fails.

One more thing I noticed is that cyanogen has removed the executable gzip from 1.3.1 and provided the busybox wrapper. This kills the compression completely because busybox gzip does not understand '-1' as option to change the compression level to 1 (which is way faster than 17minutes for the default compression level of 6 used by busybox exe). The gzip version in 1.3.1 allowed -1 and I tested it to be much much faster.
[G1 Android Development] pensive:
I certainly have no problem adding an option to exec

Your script, the user can make a choice if he wants to backup the ext2 or

not. Currently I provide options to suppress operations on different partitions but the default is to backup everything.

I'll make sure /sdcard/ is unmounted everywhere first. Thanks for the

testing.

p.s. bzip2 still understood levels as of 1.3.1, maybe I should check it on the 1.4.