yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] ryce124:
thanks!

Yea it said my sdcard was too full.

Thanks Cyanogen, for your help and for all the work you've been doing.

Much appreciated.
[G1 Android Development] huh28:
Thanks so much for the quick response....

but too late! I was tooo impatient and just started waaaay over and started from step one of this post: http://xdaforums.com/showthread.php?t=442480

so sad.......i need more patience!
[G1 Android Development] _Kyros_:
What's the difference between flashing the update.zip and flashing the raw .img?
[G1 Android Development] prash:
Nothing at all, some people just prefer update.zip files.
[G1 Android Development] _Kyros_:
Oh ok so it's just for convenience purposes, thanks for the quick reply. By the way can't wait for your System Force to be ported on Cyanogen's ROM.
[G1 Android Development] _Kyros_:
How do you browse SD card files in the Console of Recovery? I tried mount sdcard but that didn't work.
[G1 Android Development] mianosm:
Be sure to do:

mount /sdcard
[G1 Android Development] _Kyros_:
I did both mount sdcard and mount /sdcard and neither one worked.
[G1 Android Development] NeoBlade:
Tried the mount /sdcard and then "ls"?

My linux knowledge isn't that great ^_^;;
[G1 Android Development] marshallladd:
drop into a terminal

#su

#mount /sdcard

#cd sdcard

#ls

{a list of files and folders will come up here}

"CD" to the next folder and "CD .." to get back a folder. And then your basic "CP {original file location} {new file location}" to move things around. Linux is case-sensitive to type carefully.
[G1 Android Development] imnothimm:
Hmm SU problems

Having SU problems after Restoring a Nandroid Backup

(Superuser Whitelist just not working)....

All works fine after running enabler from my pc.... Just wondering if there was a way to do it from your phone?

Any help would be appreciated.
[G1 Android Development] NeoBlade:
Usually when it comes to Super User issues, most recommend clearing out the Super User list and then start afresh with the applications that call it. Did the job for me before.
[G1 Android Development] imnothimm:
Hmm Tried that.... Still nothing..

Oh well at least I have a way to enable it from the pc at least
[G1 Android Development] cyanogen:
Make sure you install 1.3.1 because it fixes the su problem after a restore.
[G1 Android Development] draco007:
i'm new at this, but i think i am doing something wrong. i just flash the new 1.3.1 with the update method. now when i go into the recovery mode by home+power i still get the same old screen with the three options nothing with alt+b or alt+x

any help please cause i really want to try this out and back up my stuff just in case i brick my phone
[G1 Android Development] NeoBlade:
Sounds like it didn't flash properly. Which method did you use? The update.zip? If so then just boot into the recovery mode and flash it like any other ROM.

If you downloaded the .img file then just open the command prompt and follow the instructions as shown on the very first post of this thread. Should work like a charm. Then boot into the recovery mode to see if it worked.
[G1 Android Development] draco007:
thank

i did the update thing twice, i guess i'll try the img thing
[G1 Android Development] nasell:
Same thing here...Flashed several times, but still same basic recovery screen. Trying the img flash also...
[G1 Android Development] NeoBlade:
I personally flashed it using the .img instead of the update.zip. See how it goes for you guys though!
[G1 Android Development] draco007:
just flashed it with the img way through the terminal and now i am good to go

thanks for the help
[G1 Android Development] NeoBlade:
No worries, good to hear it worked out fine ^_^
[G1 Android Development] cyanogen:
The update.zip method probably doesn't work on all ROMs. My builds and anything remotely JF based should work though.
[G1 Android Development] cjkholt:
used update method, this worked perfectly, i dont know why i couldnt get the .img to work, thanks Cy
[G1 Android Development] BSDADON:
Crap! Just did this in recovery console rebooted and went into terminal and typed su and got this:

[1] Segmentation fault su

Should I clear out all my su permissions or am I boned?:confused:

EDIT: clearing the permissions didn't work

EDIT EDIT: Ignore me, I'm an idiot who doesn't read, post below the one I quoted or above (can't remember too much 4th of July) said flash a rooted rom and that worked.
[G1 Android Development] mrgzg1:
I flashed thru .img method and now all I get is a tmobile g1 screen when ever I try to go into recovery console ........ any help... I downloaded on g1 and it was downloaded as .txt whch I renamed to .img.... is that the my fault by renaming it. Or dwnloading it as .txt.... it wasn't downloadin as .img..... HELP
[G1 Android Development] temporizer:
nevermind...
[G1 Android Development] Glen L:
would the update.zip work on JF 1.51?

I read that it doesnt work on all roms
[G1 Android Development] NeoBlade:
I wouldn't use my mobile personally to download files that I would flash to my phone... Use a computer, download the .img file and copy it to your SDcard. Then flash it again.

@providence

I believe Cyanogen said it would work on JF based builds so try it out. If it doesn't work, grab the .img file and flash via the terminal emulator.
[G1 Android Development] _Kyros_:
Tried that and still no luck...

I actually wanted to do this via Recovery. I asked a while back on a few pages before this one if there was a way to browse files on your SD card like ASTRO but from Recovery for people that don't have card readers or another phone that uses Micro SD (Like me) and run into boot loops and what not. Being able to move or rename files in your SD when having these problems via Recovery would be very convenient.
[G1 Android Development] NeoBlade:
Don't think there is a way to run an application in recovery mode so the things that you want to do could only be done via the command line.

You could probably use the File Explorer program developed with ADB and use that, but then you'd require a laptop, USB mini cable and a working ADB.

I can't remember if you can run .sh files as well in the Recovery mode, if so then you could easily create an .sh file to basically pull files from your SD card into the root dir to re-flash if things go wrong.

For example I use gscript scripts when I flash as on my SD card I have a folder called "os" and inside I have various builds for testing (Dude, Cyanogen etc). I then use the script to copy the update.zip from the build I want into the root of the SD card and then flash.

In theory you could create another .sh file to pull a known working build then back into the root of the SD card to re-flash.

Or use Cyanogen's new recovery image which supports Nandroid restores all from your mobile :P
[G1 Android Development] Glen L:
@NeoBlade

I have flashed it through Terminal Emulator.

When I first ran it , it was a black screen and it says Build: CyanogenMod 1.3.1 + JF

then I took out the battery and plugged it back it, went back to recovery mode

now it works..

I can now see the options :)
[G1 Android Development] osho741:
Ok this is probably a dumb question but I didn't see the answer in this thread. With the new nandroid backup and restore option in recovery terminal, in order to recover using just the phone does the .img file nandroid creates need to be moved out of the folder on the sd card and placed directly on the sd card by itself in the root directory of sd card or does the recovery tool take care of everything now?
[G1 Android Development] cyanogen:
Nandroid stores backups with a path like /sdcard/nandroid/DEVICE_ID/TIMESTAMP. The restore menu option just picks the most recent backup and restores it. If you want to pick a specific one, you can do it from console- "nandroid-mobile.sh restore /path/to/your/backup/images". Hoping to add menu support for this in the future.
[G1 Android Development] NeoBlade:
Having a menu to pick what backup you want to use would be pretty sweet and pretty much the last of the major features that I can think of when using the recovery console. Other than maybe specifying which update.zip file you'd like to use (good for flashing certain ROMs, Themes etc for testing).

I use GScript atm for such a feature, slapped all ROMs in a folder called "os" and then various themes in "themes". Then just pick the script to flash which file I want without the need to move the update.zip file to the root of the dir manually.
[G1 Android Development] temporizer:
I am able to drop into console and rename any file i want.

mount sdcard works

mount system works

i'm not sure why it doesn't work for you.
[G1 Android Development] osho741:
I understand what your saying about being in bootloops and needing access to saved files but I think the updated recovery tool fixes this scenario nicely. You no longer need adb to flash a backup, just created a nandroid before you flash a new or updated rom and if it loops go back to the recovery menu and select restore and it will put your last nandroid.img back on your phone. This feature helps people without access to adb tremendously
[G1 Android Development] NeoBlade:
Certainly the new recovery image makes life that much easier really when things go wrong. ADB though is still a useful and powerful tool when required upon.
[G1 Android Development] _Kyros_:
Oh ok so there's no need to use a card reader or what not when getting a boot loop, I never used nandroid so now I know thanks for the info and thanks to everyone else for their help and suggestions.
[G1 Android Development] matt_stang:
I have a question. How does nandroid backup work when you have apps to sd? I'm on cyanogen 3.6.1 with apps to sd. Say I format my ext3 partition and flash a different rom. If I do a nandroid restore will that restore all my apps on my ext3 also? Or do I need to keep the apps on the partition?
[G1 Android Development] ei8htohms:
you know what's funny?

I just realized that when you restore using the Recovery 1.3.1 tool that it also restores the Recovery itself. So if you restore to an earlier Nandroid from before you had the 1.3.1 image, you won't be able to restore again until you reflash the Recovery partition. Maybe it's just me, but I find that a little funny.

Any way it could be set up to only restore /system, /data and /boot instead? Wouldn't that make more sense? I mean, if Recovery 1.3.1 is working well enough to restore a Nandroid, you don't really need to reflash the Recovery image, right?
[G1 Android Development] osho741:
I believe the nandroid backup is stored on the fat32 partition, so flashing the nandroid image will just reinstall your previous rom and your apps will remain on the other partition, of course if you reformat the partition you will erase all the data on it so id only reformat if your ext3 partition is really messed up somehow.
[G1 Android Development] alapapa:
I concur, this would be preferable for me.
[G1 Android Development] DOHCtor:
I smell a 1.3.2 coming out soon :)
[G1 Android Development] temporizer:
you have to keep all your data on the ext3 partition. Nandroid doesn't back that up.
[G1 Android Development] pensive:
My experience using CMrecovery parted

Pitfalls

1) parted apparently has a bug in mkfs and does not like partition numbers

2) make ext2 partition number 2, I made a mistake of making linux-swap the

second partition and ext2 the third partition and apps2sd went nuts trying to

move the apps to the card.

The card I was experimenting with was only 1gig, I was not about to break my 16g card for the sake of experiments.

Procedure at the console

1) parted /dev/block/mmcblk0

2) print (to see what you have)

since you have a fat32 formatted card it will tell you you have a fat32

partition from 0.0mb to 4096mb (or so)

3) You have to shrink this fat partition with resize

resize 1 0mb 3000mb (you have shrunk your fat by 1096mb)

5) mkpartfs primary ext2 3000mb 4000mb (1gig ext2)

6) mkpartfs primary linux-swap 4000mb 40096mb

7) print (check your handy work)

Note parted will reserve a little space upfront on the card so your FAT32

will no longer start at 0MB, parted should move the data there without ill

effects. Adjust sizes to your liking.
[G1 Android Development] temporizer:
Thank you so much, this helps heaps
[G1 Android Development] My_Name_Is_Neo:
Well what you can do to achieve this is - remove all the other img files from nandroid folder in /sdcard/nandroid/[phone's serial]/[date], except system, data & boot and try restore. If Cyan has not done a lot of error handling in his code it will work. But If he is checking the md5 file against all the IMG files before flashing it would fail. you can try it though.
[G1 Android Development] mrgzg1:
Anybody HELP me i am unable to flash this image...

I tried fashing thru terminal method and now when i try to go to recovery console it shows tmobile G1 screen.... or can any one post old recovery image??????

my id: mrgzg1@gmail.com
[G1 Android Development] Smokuevo:
how do we convert ext3 to ext4?
[G1 Android Development] Gorguts:
HELP!!!

Going Fking crazy. Who can figure this out.

Copying files...

E: can't chown/mod /system/xbin

(No such file or directory)

E: Failure at line 71:

set_perm_recursive 0 2000 0755 0

6755 SYSTEM:xbin

Installation aborted.

This happens only when trying to update to a hero rom. I actually installed hero with the old JF1.42 spl and it worked. I read on xda that the new spl was tits so I flashed it. Now I have the above issue unless I install an older rom. I even went all the way back to RC29 and re-rooted the device; still the same issue. HELP!!!! Radio is correct as well.
[G1 Android Development] Mysticales:
Im no expert.. but my initial guesses are that things are linked, installed, whatever, What recovery console did you install? I know the one in this thread added a good deal, Also is your Sd card already partitioned? Like I said, just tossing out random thoughts in my head about this. Finally.. you could also mkdir them and make the dir yourself. Then again.. why do I have this thought that maybe its a mounting issue too.. I dont know. =/

And ah, I knew I read about that issue before. http://xdaforums.com/showthread.php?t=530900
[G1 Android Development] lilm:
Quick question

I flashed this a couple of days ago and today I went to but in one of jacs 9 million updates....well now that i did that i cant seem to get anything to work. every time i hit a option and hit home to confirm it says installation aborted. Any hints to what i'm doing wrong?
[G1 Android Development] Mysticales:
Wiped your phone too?
[G1 Android Development] lilm:
It wont let me wipe either....pretty much the only thing i can do is go to the console and reboot =/
[G1 Android Development] temporizer:
I hope this helped.
[G1 Android Development] temporizer:
question

answer
[G1 Android Development] tr.slate:
I need some help. It seems after I installed 1.3, I restored to a nandroid backup which overwrote the 1.3 back into 1.2.

Now in terminal, I get this error trying to su:

permission denied

help1help2help3help4help5$

I have tried installing the 1.3.1 recovery again, through the update.zip format, but that isnt working for me either.

Can someone please give me the code to put into the console in the recovery utility? I tried using the one on the first page, but it doesnt work for me in console.
[G1 Android Development] sxfx:
UHM dude look at the post above yours LOL....
[G1 Android Development] temporizer:
if you have the image on your sd card type this in recovery console:

mount sdcard
flash_image recovery /sdcard/cm-recovery-1.3.1.img

if you get no errors, it worked.

if this doesn't work, let me know.

do you have ADB working on your computer?
[G1 Android Development] cal3thousand:
Feature Request

Hi Cy,

LOVE the ROMs and recovery!

i have a suggestion that would make our lives slightly easier (except yours:p):

Is there a way to set the name of the folder that is created during a NANDROID backup? It would help quickly tag and identify backups.
[G1 Android Development] jklong03:
Forgive me, but isn't it possible to still adb from your PC just in the recovery screen? Seems like I remember having to do something of this sort a month or so ago when I was getting stuck in a boot loop. Was able to adb push the correct update.zip that way I think. Not exactly what you asked for, but maybe a thought of how to proceed if stuck in the future?
[G1 Android Development] temporizer:
you are able to go into adb in the recovery screen.

you would have to do

mount sdcard

to be able to push items to the sdcard via adb
[G1 Android Development] free-sidux:
The update.zip did not work for me, it flashed but I keept recovery-rebooting into JFs recovery.

Using fastboot did it.

Thanks, cool menu :)
[G1 Android Development] eros78:
Update from JF1.42 not working

I have JacHero a fat32 and a ext2 partition. I am tried the update and it still pops up JFv1.42 utility. Should I start off with a clean unpartitioned SD card or is there something else going wrong here.
[G1 Android Development] spinjason:
This is great, just flashed. Was very smooth, I am not partitioned yet. Going to do that soon. Thanks for the great work. Love the nandroid restore...:)
[G1 Android Development] eros78:
Ok. I didn't see the previous post by the time I posted. Fastboot did the trick to update the recovery image.
[G1 Android Development] schwiz:
what is nandroid and how do you use the gparted stuff?
[G1 Android Development] 71CH:
Hi. I just used the nandroid restore and now I don't have root lol. How can I remedy this? Thanks.
[G1 Android Development] timal:
If you lost su give this a try in adb:

adb shell

and then:

mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system

cd system

cd bin

cat sh > su

chmod 4755 su

sync

reboot
[G1 Android Development] Mysticales:
Did you lose the terminal app or did you still have the terminal and get permission errors which then implies you lost root? Which if it is the permission thing, only way is downgrading and doing step 1 over again.

If its that you lost terminal and still have root access like in the recovery console. What I did was just apply the update.zip to redo.
[G1 Android Development] 71CH:
Crap. It sounds like I'll have to downgrade and start over again. Does anybody know why this might be happening? I don't want to continue using the nandroid option if this is gonna happen every time.
[G1 Android Development] temporizer:
It's because the rom you are using replaces the recovery.img upon every boot.

actually, if you did a nandroid backup in 1.3 and restored that backup after flashing 1.3.1 you lose root permissions, yes.

BUT, if you READ on page 1, i posted a remedy for this. it came directly from the creator's, cyanogen, mouth.

try it.

edit: please read before you post.
[G1 Android Development] pensive:
let me chime in, I hope I understand what the problem is.

Do you have an engineering/development loader? Is your fastboot enabled?

1) fastboot boot cm-recovery-1.3.1.img (or whatever it is)

2) go to shell

3) cp (or cat if you have no cp) sh su

4) chmod 4755 su
[G1 Android Development] pensive:
There are detailed instructions on GNU parted in an earlier post.

Look at the earlier posts for parted stuff.
[G1 Android Development] Falling Awake:
Help!

I have done everything and used acronis software to partition then applied th update. My phone loops an won't stop! help me plz
[G1 Android Development] 71CH:
umm you dont have a single post on page 1. thanks for the help anyway.
[G1 Android Development] shorteh:
Ok so I installed this successfully using the IMG.

When I try and enter recovery mode, it hangs at the first splash screen (Rogers Logo)

What gives?
[G1 Android Development] LPChris:
Has anyone run the repair ext filesystems and had their phone not boot up afterwards? Something happened and it said that it errored when it ran and to go to the console and type in e2fsck, did that and saw all the options and said screw it and rebooted the phone. Now the phone won't get passed the first splash screen (I don't think its getting out of the SPL).

I've gone into the recovery console now and I don't see any data in the /data folder. Should that folder be empty in the recovery console? Or did I just lose everything again?
[G1 Android Development] tinyaznboi:
its possible that ur sd is corrupted (no longer works properly) and that now you need to reformat it (using your computer and an sd reader) and then repartition it
[G1 Android Development] aceo07:
I'm not sure if it's been mentioned before, but I think it's a typo.

If you try to restore and are low on battery, it will tell you there was a problem and to go to the console and type 'nandroid-mobile.sh backup'. Shouldn't it be 'nandroid-mobile.sh restore'?
[G1 Android Development] LPChris:
I don't think that's the problem considering I didn't have anything on the ext portion of my SD card and everything was running off of the phone's internal memory. Its the phones internal memory that seems to be cleared.
[G1 Android Development] temporizer:
my bad. Page 66.

Even so, have you tried it?
[G1 Android Development] Ohsaka:
Yes, I did do a google search and didn't find an answer...

When I run repair ext, i get an error "run e2fsck manually"...

Whats up with that?
[G1 Android Development] lilm:
Well i flashed back to 1.3.1 and im still having the same exact problem....im not sure what to do. In essence if there is anything i have to confirm it will say aborted......
[G1 Android Development] pensive:
I am about done with the tweaks to nandroid-mobile.sh

To add prefixes like CMv3.6.4.1- to backups and the scanning ability to restore particular backups. It is useless though unless the script is added to the recovery.img by the author.
[G1 Android Development] pensive:
Tweaked nandroid-mobile.sh

If run from UI it has the default, old behavior. When run from the console you can do the following.

nandroid-mobile.sh backup WierdBuildCMv3.99.1

backup directory will be named WierdBuildCMv3.99.1-20090709-2045

nandroid-mobile.sh backup

will prompt you to enter a prefix or let the default stand.

nandroid-mobile.sh restore CMv3.99

Will look for all the backups with this substring, it will match WierdBuildCMv3.99.{1,2,3,4}{whatever dates)

and will give you a choice to choose more precisely, if your input is still NOT

unique, it will choose the latest of the SUBSET.

nandroid-mobile.sh restore

Will prompt you for the substring to look for and then again to narrow it down.

If you fail to make a unique choice, it will take the latest of the SUBSET to which you narrowed this down.

Being lazy myself, I would prefer if it were hooked into the UI.
[G1 Android Development] digital006:
I'm having real issues with 1.3.1

My main install Cyanogen Mod crapped out on me and started reboot looping, so I tried to do a nandroid restore.

Booted into the recovery image and I get E: can't open CACHE: etc etc.

I can't boot into the os to run any terminal commands but I can use adb while in the recovery console. Alt + L is the only command that will respond. I read a thread about using the following command "mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /cache" I did this through adb while in the recovery console and it just hung.

Is my phone well and truly bricked?
[G1 Android Development] IRIE4IPIER:
when i try to flash a rom i get this error,

E:Cant mount /dev/block/mmcblk

p1 (or /dev/block/mmblk)

(I/O error)

E:Cant mount SDCARD:update.zip

installation aborted

so what is wrong with this, uugghgh why did i flash this stupid image i didnt need it. please someone help

EDIT: nevermind i figured it out
[G1 Android Development] temporizer:
Try rebooting into bootloader by either camera+power or typing

adb shell reboot bootloader

Hit the back button, you'l see "fastboot" on the screen.

From command prompt (have 1.3.1 recovery .img in tools folder) type

Fastboot erase recovery
fastboot flash recovery cm-recovery-1.3.1.img
[G1 Android Development] lyric911:
Edit: Nm, found it.

Ok, ran the apps2sd script. Booted into my phone, and all my app shortcuts on my home screen are broken. Do I have to reinstall everything?
[G1 Android Development] prettyboy85712:
Just recreate them.