yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] here.david:
Same with me...Now I fastboot the previously installed CM, flash again with the new CM and then flash with Hero theme...mins vs. the hours I use to re-installing all the apps and settings...plus two G1's...:eek:
[G1 Android Development] bkmo:
Yup that was the exact error. And yup without the typo life is good. Thanks for the help.
[G1 Android Development] abteer:
Wow man great work once again. Thank you very much for all your hard work. Works great.
[G1 Android Development] Drizzy Drake Rogers:
wow I thank you!

wow is there anything that the android OS cant do!!

apps to sd couldnt be easier awesome job!
[G1 Android Development] bhang:
native browser d/l issues

My browser, even with download crutch and astro the browser is viewing your recovery.img

Anybody else having an issue, maybe I should linda file manager?

Maybe somebody could u/l it with a .txt extension, I'm not gonna be back at a pc for hours and this is just what I've been waiting for

Bhang
[G1 Android Development] kingskidd268:
Sweet now I have A Nadd back up Thanks...
[G1 Android Development] Denkai:
try long pressing the download link and click "save as"
[G1 Android Development] Thats BS:
Typo sorry. Lmao. Was reading the update info on 1.2 and was'nt thinking.:o
[G1 Android Development] andonnguyen:
Looking good cyanogen =]

Here's a screenshot if anyone is curious:
[G1 Android Development] mikedmeyer:
I didn't know it had been named "DangerSPL." I like it.
[G1 Android Development] kristoff123:
When I try to download the .img file from my g1, it just loads a huge page of garbage code. Any clue as to how I download just the file instead?
[G1 Android Development] temporizer:
What's the dangerSPL? 1.33.2005?
[G1 Android Development] temporizer:
On mine I longpressed and saved as. It downloads as a .txt and I just went and changed the name in terminal, moved it to my sdcard and flashed. No problems.
[G1 Android Development] cyanogen:
Yeah. Thats an appropriate name I think :eek:
[G1 Android Development] Denkai:
well I feel like an idiot now..
[G1 Android Development] temporizer:
I flashed dangerSPL with your recovery a while ago. no problems.

*two thumbs up*
[G1 Android Development] ScottGood:
I flashed that SPL last night and all is good, I've been running this recovery image for a good while.
[G1 Android Development] heldc:
Can't write recovery.img "no space left on device"! wtf?

When I try to flash cyanogen's recovery image, I get

~/Desktop/g1/android-sdk-linux_x86-1.5_r2/tools$ ./adb shell flash_image recovery /sdcard/recovery.img
error writing recovery: No space left on device

I don't seem to have any recovery image at this point (when I boot while pressing home, I end up at the bootloader, not the recovery screen), although the system is functional otherwise, running cyanogen's 3.4.6 ROM. I can't wipe, since I can't get to the recovery screen. I did an in system factory reset, and still get the same error. I get the error regardless of whether or not I adb remount first. This has me completely perplexed and is making life quite difficult!

Edit-This happens even tho the phone reports 40+MB of free internal space.

I DID search, but this doesn't seem to be an error message ever before seen on this forum! http://www.google.com/search?q=site%3Axdaforums.com+"error+writing+recovery"+"No+space+left+on+device"
[G1 Android Development] Mikey:
why cant you just transfer the file to your card, using a usb cord and just:

flash_image recovery /sdcard/cm-recovery-1.2.img
[G1 Android Development] cyanogen:
Try using fastboot from the SPL and erasing first..

fastboot erase recovery

fastboot flash recovery cm-recovery-1.2.img
[G1 Android Development] heldc:
Will try that when my fiance gets home from work (the problem is his phone, not mine) and report how it went, thanks!

I get the same error, regardless of whether I run the command via ADB or in terminal on the phone.
[G1 Android Development] bboy_201:
i was looking for the jf version and look at this even better thank you!!!!!!!!
[G1 Android Development] jaron7_11:
I tired to install and nothing happen. I put the file on the sd and typed in the comand and nothing happen was I suppose to do something else after that
[G1 Android Development] heldc:
Tried it, no luck. :(

:~/Desktop/g1/android-sdk-linux_x86-1.5_r2/tools$ ./fastboot erase recovery
erasing 'recovery'... OKAY
:~/Desktop/g1/android-sdk-linux_x86-1.5_r2/tools$ ./fastboot flash recovery cm-recovery-1.2.img
error: cannot load 'cm-recovery-1.2.img'

Ok, just for the heck of it, I tried a normal adb recovery image flash after the fastboot flash didn't work, and it worked! So I guess the magic trick here was to delete recovery via fastboot, then do the normal recovery image flash.
[G1 Android Development] Abolfazl:
It is a problem of where the recovery img is. Try putting it in the same directory as fastboot
[G1 Android Development] heldc:
It worked out, thanks!
[G1 Android Development] WhAtSROoT?:
it doesnt give you a confirmation.as long as it didnt tell you it failed it should have worked. just reboot to recovery (home + power) and see if it gives you the new screen. i was thining the same until i checked
[G1 Android Development] icegad:
need help asap

How do I perform a super wipe I'm running 3.5.3 with cyanogen recovery image I jus upgraded from ext2 to ext3 and the #rm -r/system/sd/* not working like when I jus had the ext2 well actually its giving me all kinda options I jus want to wipe the ext3 and/or ext2 and start fresh

Plz no adb commands. I need to do it from terminal or console. Thx
[G1 Android Development] cyanogen:
"mount /system/sd" then "rm -rf /system/sd/*" will delete everything, but do this from recovery.

If you want to really nuke the filesystem and start fresh, you need to use ADB for two reasons- 1. you need to stop the Android runtime and unmount the filesystem to do it (which will stop Terminal), and 2. because I'm an idiot and didn't include mke2fs in the recovery image (next version though).

If you want to use adb, run "adb shell", and do this (this won't work in terminal):

stop
umount /system/sd
mke2fs -j /dev/block/mmcblk0p2
reboot
[G1 Android Development] icegad:
Thx for the help really appreciate it

But it said device busy. I did try it from the recovery...

Can't use adb cuz my laptop is on her period.....

One other stupid question is it possible to downgrade. Back to ext2 where I kno the rm sytem/sd* will work and then upgrade again back to ext3
[G1 Android Development] Mikey:
Define the word, nuke?

Will i have to repartition the card again after this command??

mke2fs does what exactly?
[G1 Android Development] jjjackson56:
Sd card gone!

ok not sure if anyone has had this happen to them but in recovery i did a alt+w to wipe my data before flashing to a new rom, well not only did it erase my user data but it also wiped my fat32 (sdcard) partition now all my data is gone. Anyone have any ideas.
[G1 Android Development] My_Name_Is_Neo:
nuke means reformat the partition to to ext3 journal. so difference is

Delete All vs reformat(nuke).
[G1 Android Development] startekee:
The link to the recovery img is broken
[G1 Android Development] _Kyros_:
Is there a way to browse files on the SD card like ASTRO through Recovery? If not that would be a great addition to make it even more convenient.
[G1 Android Development] stogchris81:
so, i have done upgrade_fs 2 times, everything seemed to work ok. the first time it had to fix a few things. however, when i mount the card in ubuntu, partition editor says it is still ext2. am i doing something wrong?
[G1 Android Development] temporizer:
yes, drop to console and type

mount sdcard

should work just fine
[G1 Android Development] temporizer:
you did this from recovery right?
[G1 Android Development] _Kyros_:
I did this and it said "mount: mounting /dev/block/mmcblk0p1 on /sdcard failed: No such file or directory"
[G1 Android Development] temporizer:
when i got this error i had to repartition my sd card

try popping it out of your phone and putting it in a reader. if nothing happens or windows says it's corrupt, it needs to be repartitioned.
[G1 Android Development] stogchris81:
yes. i did it from this pimped recovery.
[G1 Android Development] _Kyros_:
Ok I'll try removing the SD card and putting it back. By the way my SD card isn't partitioned and Windows doesn't say that it's corrupted.
[G1 Android Development] Mikey:
I tried this ^ and i got this:

C:\tools>adb shell
# stop
stop
# umount /system/sd
umount /system/sd
# mke2fs -j /dev/block/mmcblk0p2
mke2fs -j /dev/block/mmcblk0p2
mke2fs 1.41.6 (30-May-2009)
/dev/block/mmcblk0p2 is mounted; will not make a filesystem here!
# reboot
reboot
reboot returned
#
[G1 Android Development] _Kyros_:
Nope didn't work it still said the same thing.
[G1 Android Development] pensive:
Ran into quite a few problems with the stable image.

So, I tried out this build. Wifi could no longer find networks, nor could I save any network I entered. If the blue tooth was on, phone calls had no sound

anywhere, either on car radio or on the phone, I was forced to turn the blue tooth option off. When I ran fix_permissions instead of fixing things, it caused complete bedlam and none of the applications which used to run fine could run any longer. I had to revert back to JF1.51. Camera and camcorder only could see in black and white also. I played with it for only a day or so. I was able to boot debian from a partition but an attempt to connect to vnc server immediately booted the phone.

I have no idea if I am doing something different from others but that is what

I saw.
[G1 Android Development] cyanogen:
Do a "mount" and make sure /system/sd actually is unmounted. If you were connected to wifi you also need to do a "stop dhcpcd" to get it to unmount.
[G1 Android Development] warburto:
I'm attempting to flash the recovery image and am getting the following error while using fastboot.

c:\android>fastboot flash boot cm-recovery-1.2.img

sending 'boot' (3832 KB)... OKAY

writing 'boot'... FAILED (remote:image update error)

Any thoughts?
[G1 Android Development] stellarman:
Exactly the same message I got when trying to flash boot from a Nandroid backup. Cyanogen suggested I try next time:

fastboot erase boot

and then try again to flash the boot image.

BUT, I HAVE NOT TRIED THIS MYSELF. If you want to experiment, you can try it. But, you are on your own... :) Personally, I am a little nervous about erasing my boot image without knowing why the new image won't flash.
[G1 Android Development] warburto:
Actually already typed

fastboot erase boot

Still got the error when attempting to flash the backup. Then attempted to flash my nandroid backup, which flashed successfully but when I attempt to boot the phone as normal it hangs at the G1 screen. So I'm stuck right now
[G1 Android Development] stellarman:
If you flash your ROM again (whatever you have been using) it should rewrite the boot image as part of the install. That's how I got past being stuck at the G1 screen.

But, we really need to find out why people are having trouble flashing boot, from Nandroid or otherwise.

What ROM are you on?
[G1 Android Development] warburto:
Cyanogen's 3.4.6

Hard SPL /2.22.19.26I Radio
[G1 Android Development] antt b:
download link wont work
[G1 Android Development] warburto:
Ok, I was able to flash the recovery image after formatting the SD card. I formatted both partitions, just to be sure. Using fastboot, I successfully flashed the recovery image.
[G1 Android Development] pensive:
v3.4.6 - old stable version, updated 6/24

Sorry, I should've been more specific. I left the JF1.43 recovery in but I did try the CM recovery by booting it with "fastboot boot cm-recovery.img" and made a nandroid backup with it, worked fine.

Previously I failed to mention the whole procedure.

1) First I loaded CM v3.4.6

2) I had my apps and data backed by backup for root users, I did a restore

of apps and app data. It seemed to work fine, except for a couple of protected apps, initially it seemed like none of the apps could be run but after

a reboot most of them appeared. The protected Apps I had to reload from the market.

(as an aside improvement, since the CM setup has 5 screens it would have been nice if I could reorganize the apps moving them to new screens without having first to dump them. Dragging icons from one screens to another would be useful)

3) I did not check WiFi or Bluetooth before I reloaded the apps

4) After everything was reloaded, things appeared more or less stable and I was able to run various apps.

5) I ran fix_permissions mostly to be on the safe side (I thought it would first do no harm), it ran without reporting any errors. However, afterward I could not launch ANY application.

6) Bluetooth was usable with the Meridian music player or StreamFurious internet radio setup, BUT did not work with the phone (hmm, I should look at the profiles if I make another attempt)

7) Since there is yet another version out, I will probably make an attempt with that one.
[G1 Android Development] Breakthecycle2:
OK, I just got this installed and I ran the alt F. I got an error message, saying "error checking filesystem. Run e2fsck manually from console". Whats the code for this?
[G1 Android Development] SyXbiT:
so, is CM recovery 1.2 something that replaces the regular recovery we did to get root?

p.s. i flashed this by loading up connectbot. typing 'su' and then the listed command. i assume that's right.
[G1 Android Development] stellarman:
From the recovery screen where you tried to run Alt-F, instead press Alt-x. This gets you to the console and a # (root) prompt. That is where you type in e2fsck manually to try again to check your ext2/3 file system for errors.
[G1 Android Development] stellarman:
From my experience in a similar situation, I suspect you will need to wipe and reflash the ROM. Don't know why running fix_permissions would mess things up like that (maybe someone who knows can chime in).

I have found this series of CM roms to be pretty stable and dependable, once you get them installed and everything working. And getting to that point is usually pretty simple.
[G1 Android Development] vinhnguyenho:
After i flash new recovery by command in Terminal.

#su

#flash_image recovery /sdcard/cm-recovery-1.2.img

do not find error when i type command, everything done. After then i can not boot to recovery (Home+Power). It stays on G1 logo.
[G1 Android Development] crebaindamme:
Bug on this recovery

First of all, I want to say thank you for all your work, I know it's hard and I want to help a little bit with this post.

I found a bug on this when I wanted to flash the new SPL of Haykuro, after 5 or 6 attemps (doing the tutorial step by step, wipping, formating the two partitions of the SD, etc), I wasn't able to flash the SPL. My HardSPL sticks like a tick in my device. I knew that this happened to other people... Then I realize that all the guys that installed it successfully made it before installing this recovery. Then I install JF recovery and all was good, I was able to make it.

I hope this can help other people.
[G1 Android Development] Lemonade727:
I had a similar issue, but I was able to install the new SPL by hitting the actual home+back buttons on the phone instead of using the trackball to hit the command on the new recovery page.
[G1 Android Development] temporizer:
Cyanogen, do you have a possible ETA for your new image?
[G1 Android Development] cyanogen:
Not much longer, just tidying up the restore function. It's nothing fancy, it just restores your most recent backup. If you want to restore a different one, do it from the command line.
[G1 Android Development] alritewhadeva:
Thanks cyanogen! Breaking my F5 button
[G1 Android Development] temporizer:
YAY!!!!!!!!!!!!!!!
[G1 Android Development] cyanogen:
Recovery version 1.3 is posted. We now have restore capability from the menu! This restores your most recent backup. If you want a different one, you'll have to drop to console and do it manually. Lots of other little goodies included, see the first post for details!
[G1 Android Development] t1h5ta3:
awesome man! now take a break and enjoy the weekend!
[G1 Android Development] Lemonade727:
Great release as usual man, much appreciated.
[G1 Android Development] revwillie:
aw crap. looks like I'll have to update my sig again.
[G1 Android Development] Geniusdog254:
Any chance of letting us choose which backup we want to flash, kinda like glob update support, just show a list of folder names and let us choose which one.
[G1 Android Development] cyanogen:
You can do it from the console with "nandroid-mobile.sh restore /path/to/your/backup". I plan on adding some globbing for this as well as update.zip files with trackball selection in the future but I wanted to get this version out.
[G1 Android Development] Binary100100:
Tried, tested and working beautifully! But I have a request:

Instead of:

How about being able to select it from the menu like the other options?

That would be VERY helpful.

ps. YOU'RE THE MAN!
[G1 Android Development] temporizer:
You rock Cyan! Thanks a bunch.
[G1 Android Development] temporizer:
is there a list of commands/tutorial on the gparted portion of your recovery?
[G1 Android Development] Geniusdog254:
Very very cool. Thanks a bunch cyanogen. You rock!

BTW- to the poster who requested ums_enable & ums_disable from the list as well +1
[G1 Android Development] sir*mez:
dude i love you!!! your making android so much easier!!
[G1 Android Development] revwillie:
CM 3.6 and now recovery 1.3! we should declare tomorrow a national holiday or somesuch. Crack open a cold one.
[G1 Android Development] KPeriod:
*jaw drops* O_O

Stop being so awesome and making me hug my phone so much.
[G1 Android Development] cyanogen:
Yeah, I am lazy with the UI part. I'm going to work on some stuff like this for the next version.

It's all command line.

http://www.gnu.org/software/parted/manual/html_node/index.html

If you do something like "parted /dev/block/mmcblk0" you can type "help" to get a list of commands. Make sure you unmount those partitions first!
[G1 Android Development] manup456:
Ah great work bro sounds good tossing this in a.s.a.p :)
[G1 Android Development] MontAlbert:
thanks- installed nicely. Will try it out soon i am sure.

I also would love the option of a menu where you can choose which nandroid backup to restore... but until then old skool terminal it is... :D
[G1 Android Development] TheGreenJester:
Thanks again Cyanogen!

When I went to flash this I discovered flash_image was no where to be found. I just did a mount -a and then pushed it into sbin and all is well. Why would it disappear like that? I certainly didn't delete it, but something did.
[G1 Android Development] ei8htohms:
devs like you rock!

The work you guys do continues to make Android the best smart phone OS ever. Thanks for everything!
[G1 Android Development] Gimpeh:
Now this just needs to be ported so us Magic/Ion users can utilize this gift.
[G1 Android Development] cyanogen:
Oh, I also included mke2fs with this one, so if you need to nuke your ext partition for some reason, you can with a "mke2fs /dev/block/mmcblk0p2". Add a "-j" if you want ext3.
[G1 Android Development] tr.slate:
Having some sort of problem flashing 1.3.

I get this error: sh: flash_image: not found

I have tried 2 different sd cards, and reformatted. Running Virtudude Rogers V3. Anyone have an idea?
[G1 Android Development] nxt:
delete my post.
[G1 Android Development] markgoho:
I hate to ask such a naive question, but I must:

What was the reasoning behind removing the Move Apps to SD option in the recovery image? I know you're all about making things more efficient and easier so I have to assume there's actually a good reason for it. Will all future apps I install automatically be put on my ext3 partition when I reboot the phone?

Thanks for all of your tremendous work, Cyanogen. I'd like to buy you that beer :)
[G1 Android Development] johnnylicious:
1.3 works perfect thanks again =D
[G1 Android Development] I am M3:
Just tested the nandroid recovery portion of this image, and I'm pleased to say it works great! All hail Cyanogen! :D
[G1 Android Development] cyanogen:
Because most recent builds (including mine and JACHero) do it automatically for you as long as you have a second partition created. The option seemed like it caused problems for a lot of people as well. I left the apps2sd script there so you can run it from the command line if you want, though.
[G1 Android Development] ScottGood:
If i have:

Nand image 1 jf

Nand image 2 cm

Nand image 3 hero

If jf was my last backup how would I restore hero for example?
[G1 Android Development] cyanogen:
Drop to console, and run:

nandroid-mobile.sh restore /path/to/your/images

Normally, backups are stored as /sdcard/nandroid/DEVICE_ID/TIMESTAMP. Running it from the menu or without an image path will pick the most recent image and restore it.
[G1 Android Development] grokdesigns:
Shouldn't

be:

:confused::confused::confused:

That's what worked for me anyway...
[G1 Android Development] stellarman:
Nice work! Especially the Nandroid restore. Thank you very much.
[G1 Android Development] cyanogen:
oops, fixed!
[G1 Android Development] davil124:
so quick question, if i convert from ext3 and ext4 is that going to give me any props ?! or is it gonna be almost the same thing ?!
[G1 Android Development] samethsom:
Can i run the commands in terminal?
[G1 Android Development] soba5150:
Help my sd card was corrupt from the swapper i reformatted then did the flash_image commands from terminal and when i tried to reboot into recovery i have no recovery at all.... can i fix this. Without ADB??
[G1 Android Development] Paul22000:
Silly question:

What *IS* a recovery image? ;D
[G1 Android Development] beagz:
cyanogen. You Rock!
[G1 Android Development] Ryanmo5:
Is anyone else having problems with the link? Won't download for me.
[G1 Android Development] Booker-T:
Run the script in terminal?
[G1 Android Development] countkakula:
easiest way ive been able to do is by going back to an old rom like JF 1.41
[G1 Android Development] samethsom:
Um....download link seems to be down, can somebody upload please?
[G1 Android Development] cyanogen:
It's the part of your system that comes up when you turn the phone on while holding the home key. It lets you do things like flash new ROMs, make backups, and perform general maintenance. It has a minimal Linux console environment as well.

Try right-click, save as.
[G1 Android Development] samethsom:
I'm downloading from my phone.....
[G1 Android Development] Lou2serious:
Do I have to remove 1.2 before o flash 1.3. And if so how do I do that??
[G1 Android Development] TheGreenJester:
flash_image

It seems I'm not the only one who's flash_image has disappeared. I have attached a zip containing flash_image. Extract and then do an adb push to the system/bin directory.
[G1 Android Development] cyanogen:
Nope.

What ROM are you guys running that doesn't have flash_image? Someone screwed up I think :eek:
[G1 Android Development] Paul22000:
Ohhhhhh, ok. Got it.

Now that I understand what it does, I installed it and took a few pics. Any chance you might want to put them in your OP?

Hope this helps someone out there! :)
[G1 Android Development] TheGreenJester:
I'm running your ROM lol! I haven't used anything but your ROMs and recovery images in ages. I don't know what happened to the file, but it flat out disappeared on my phone at some point since the 1.2 recovery was flashed. I'm not using any themes, never have. :confused:
[G1 Android Development] Ryanmo5:
Duh lol, thanks man!
[G1 Android Development] prettyboy85712:
Damn Cyanogen, you are on fire baby!!!! Simply brill once again! :D
[G1 Android Development] cyanogen:
Hrm.. I have no idea. flash_image is in /system/bin and I can't think of any reason why it would be deleted. A theme wouldn't affect it.
[G1 Android Development] fleshdeep:
My flash_image is intact with the newest cyanogen 3.6. even have the ophone theme with no problems. This new update is great!
[G1 Android Development] 71CH:
Sorry for the dumb question but if I do alt+b and then flash some other rom, and then restore the nandroid file, I'll go back to the rom I had before the flash?