yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] notxel21:
@ Cyan, was the move AppsToSd option removed? Thanks!! Keep up the GREAT work! :)
[G1 Android Development] kizer:
Thats the idea. ;)

Nothing like having a do-over button in your hands.
[G1 Android Development] prettyboy85712:
Yes

(10 characters)
[G1 Android Development] cronin4392:
Hey Cyan, i was wondering if you could change the color of the text. Not much contrast between it and the background and it can get hard to read.
[G1 Android Development] samethsom:
Can somebody upload, dont have access to computer...im on my phone
[G1 Android Development] nxt:
Yes.

1346654
[G1 Android Development] nxt:
It's on the revision log on the first post.
[G1 Android Development] EpedemicOptikz:
for us stupid people, what's the script for apps-to-sd since it isn't in the menu anymore?
[G1 Android Development] here.david:
WOW...=<5 sec to install - had me worried

Here is what I did...USB connected the G1 copied cm-recovery-1.3.img to the (FAT) SDCARD, unUSB-ed the G1, still pluged in...

# cd (path)/android-sdk/tools

(path)/android-sdk/tools# ./adb remount

* daemon not running. starting it now *

* daemon started successfully *

remount succeeded

(path)/android-sdk/tools# ./adb shell

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

# (path)/android-sdk/tools#

=< 5sec

WOW! WOW! WOW!:D
[G1 Android Development] sw20matt:
are you still working on puting in a ext wipe also?

thanks for this awesome recovery!
[G1 Android Development] cyanogen:
Its "apps2sd" from console. You don't really need to use this after you have set your phone up for it, or you are running a ROM that does it automatically. Once you are setup for it, your apps should be already going to SD.
[G1 Android Development] EpedemicOptikz:
Thanks for quick response, also, one last question, for "nandroid restore", do I just type nandroid restore in console or would I type what I usually type in DOS, in the console e.g. "fastboot flash system system.img" etc.
[G1 Android Development] Drizzy Drake Rogers:
well done cyno you are the man! flashed with hero perfect!
[G1 Android Development] cyanogen:
The menu has an option to restore your latest backup. If you want one thats not the most recent, you have to use the console, check a couple pages back for instructions.
[G1 Android Development] temporizer:
I am so lost with this parted thing. can someone please help me. I have a fresh 4 gb sdcard that i want to have a 24mb swap, 1gb ext3 and the rest fat32.

please help?
[G1 Android Development] EpedemicOptikz:
Thanks, can't wait for the "super-wipe" now.
[G1 Android Development] samethsom:
nevermind........
[G1 Android Development] Paging Dr B:
great work Cyanogen! the restore option in the main menu is the ultimate undo button. That'll seriously come in handy with those hero roms coming out everytime i blink.
[G1 Android Development] SyXbiT:
i really like the battery at the unlock screen. great feature.

problem is, it's not accurate. i'll be charging my phone for 2 hours and I know it's fully charged, but it shows 70%. A restart, and it'll show 100%.

anyone else notice this?
[G1 Android Development] kicker1:
Nandriod restore!!! yeah baby yeah!! Well done Cyno :)
[G1 Android Development] BSDADON:
Just did a backup and flashed another theme, did a restore and my old theme is back! This is amazing how much simpler it got. Now I can test more on the road and not have to worry about being near a computer :D
[G1 Android Development] borodin1:
Wow Cyanogen.. you've outdone yourself this time. 2 rom updates and new recovery....

Flashed without any problems, love the new "nand restore" feature, we needed that

Hopefully work picks up a little so I can provide some beer for you.....
[G1 Android Development] kkll70:
Been using your recovery images and I just thought you deserved my thank you... so...

Thank you :).
[G1 Android Development] cidica:
ok just did a nandroid restore and went to terminal did su and got permission denied? not sure if this an issue or just a part of namdroid? Anyone have an idea by chance? Oh and this is with the 1.3 recovery img
[G1 Android Development] ei8htohms:
minor issue

After restoring from the Recovery utility, it seems to do something weird to SU permissions. I tried it a couple times to confirm, and after the restore I get "Permission denied" both in Terminal and when using GScript trying to reboot, use PowerTop, etc. Hopefully an easy/quick fix?(<- fixed, why doesn't XDA allow strikethrough tags?)

Thanks again for everything!

1.3.1 works great. Excited that this seems like a quick and easy step away from allowing us to basically dual-boot ROMs. :)
[G1 Android Development] Diceman4:
cyanogen, I think that I am in love with you. Seriously. you are by far the most active dev for android and I love waiting for your next mod/rom/hack
[G1 Android Development] Binary100100:
Permission denied

I am not sure if it was from the new 3.6.1 or the new recovery 1.3 update but when I type "su" in terminal I get "permission denied".

This has never happened before.

Anyone else experience this?
[G1 Android Development] cidica:
read above 2 of us have the issue. so far atleast.
[G1 Android Development] temporizer:
does this mean i have a swap partition?

c:\android\tools>adb shell free
total used free shared buffers
Mem: 97908 96088 1820 0 376
Swap: 32120 1384 30736
Total: 130028 97472 32556

c:\android\tools>
[G1 Android Development] maxisma:
To fix su-issue:

cat /system/bin/sh > /system/bin/su

chmod 04755 /system/bin/su
[G1 Android Development] Binary100100:
Yeah I noticed. I was composing the e-mail when I was distracted for about a half hour (work related) before i hit the "Submit Reply" button. But I swear I did search first. :p
[G1 Android Development] Lou2serious:
Didnt work for me, It says "cannot create /system/bin/su: read-only file system.

I also did a nandroid backup and restore before this and all of my fonts are missing.
[G1 Android Development] nxt:
Didn't work for me.

I did a nandroid backup, (only backup on my sd card).

then i put on the spl for hero, then flashed jachero's rom, then i didn't like it, flashed back the hard spl, then went to restore nandroid and it gave me an error telling me to go to console and run nandroid-restore.sh or something like that.

i did it, and in the middle gave all kinds of errors. So I did adb restore and it's fine.

Will try again and get the exact error messages
[G1 Android Development] maxisma:
do

mount -o rw,remount /dev/block/mtdblock3 /system
[G1 Android Development] Binary100100:
Thanks... but doesn't work.

"cannot create /system/bin/su: read-only file system"
[G1 Android Development] Binary100100:
mount: permission denied. (are you root?)
[G1 Android Development] maxisma:
Boot up to recovery mode, press alt-x

and then enter

cat /system/bin/sh > /system/bin/su

chmod 04755 /system/bin/su
[G1 Android Development] Binary100100:
sh: can't create /system/bin/su: nonexistent directory
[G1 Android Development] maxisma:
AHH! Please forgive me! This should work:

mount system

cat /system/bin/sh > /system/bin/su

chmod 04755 /system/bin/su

if that doesn't fix the issue, try the same , but replace last line with chmod 4755 /system/bin/su
[G1 Android Development] Binary100100:
That did it!

Danke!
[G1 Android Development] Ummuish:
the image did not work for me at all, I cannot boot into recovery. logcat says nothing.
[G1 Android Development] Moriah:
Try this....

wasn't working for me either so i tried this:

In Terminal;

SU

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

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

worked like a charm, rebooted to recovery and basked in the beauty :cool:
[G1 Android Development] garsim:
cyanogen, thank you very much :D

i love your work :)
[G1 Android Development] bjehsus:
After flashing this, home+power just takes me to SPL
[G1 Android Development] geekoo:
My G1 just got screwed. I installed this recovery image. Then I wanted to flash the HardSPL bootloader. I took a NAND backup from the recovery and then I flashed HARDSPL. Flash was successful.

Then I rebooted through the recovery and the phone is just stuck on the G1 screen. I don't have bootloader screen, I don't have recovery screen. I don't have my 3 day old G1. I'm devastated. :((((

Any pointers please?
[G1 Android Development] tulamidan:
Afer flashing this home+power doesn't take me to the bootloader any more... just stays at the G1 screen. OS boots up normally though.
[G1 Android Development] cyanogen:
Ahhhh it looks like my hacked up unyaffs isn't restoring setuid perms, easy to fix. I'll take care of it.

You probably got a corrupted download. Always verify the md5sum ON THE DEVICE before flashing it. If it still fails, use the fastboot instructions in the first post.
[G1 Android Development] Amdathlonuk:
Is this safe to use now?
[G1 Android Development] borodin1:
Quick question for Cyan... how does this recovery image knows which nand was the most recent for restoring it from the device? Does it know by name (xxxxxx-yyyymmdd) or does it know by properties? I always rename my backups to "buildX-themeY-dateZ" so I don't get lost in countless folders :), that's why I would like to know.

Thanks!
[G1 Android Development] overground:
yes...you do...is that 10 chars?
[G1 Android Development] ei8htohms:
definitely not having these problems

Home + Power boots me into Recovery as expected. When you say "SPL", I'm guessing you mean Fastboot/Bootloader? It might help Cyan if you post the relevant info about your phone (carrier - UK T-Mo?), prior Recovery image, SPL, ROM, etc. as well as detailed steps about how you flashed and arrived at your current state.

Haven't heard of this happening outside of the many occurrences related to the "Danger" SPL. If you can't get to Recovery or Fastboot, sorry to say, but I think you have a brick. To my knowledge there is still no fix for this, but hope springs eternal around a JTAG solution, but how practical that will be for your average user would be optimistic speculation this side of "not very".

I'm guessing that you mean that Home + Power doesn't take you to Recovery? Fastboot/Bootloader is accessed with Camera + Power. If the OS boots up, obviously that's a good sign, but I'd proceed with extreme caution when trying to resolve this as Recovery is, well, how you recover from a lot of things. As mentioned above, it also might help Cyan if you post the relevant info about your phone (carrier and location), prior Recovery image, SPL, ROM, etc. as well as detailed steps about how you flashed and arrived at your current state.
[G1 Android Development] Ohsaka:
For folks having problems, did you verify the md5 hash on your download before installing it?

You can go here, http://md5.my-addr.com/md5sum_for_file-md5_file_checksum/online_md5_file_hash_generator_tool.php ,and and get the md5 hash of any file you have downloaded.

Last night it seemed like the server was overloaded (could have been my spotty connection since I'm out in the woods too) and my first download attempt was corrupted. Cyan posts the md5 hash to verify against in the first post of this thread. Protect yourself and your phone!
[G1 Android Development] cyanogen:
It looks at the timestamp on the directory. "ls -tr | tail -1"

It's even better if you verify the md5sum from terminal ON THE DEVICE before flashing it (just do an "md5sum /path/to/file" from terminal), that way you know if you had a bad transfer.
[G1 Android Development] bjehsus:
Right, just tried to flash again;

I'm on T-Mobile G1, UK. CM 3.6.1, with CM recovery 1.2, HardSPL.

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

Tried remounting /system, and verified md5sum, flash seemed successful in terminal.

Rebooted, and home+power brings up fastboot, with the skating androids.

Tried this about 4 times, now.
[G1 Android Development] Moriah:
What Does Camera + Power do?
[G1 Android Development] bjehsus:
Fastboot, again
[G1 Android Development] Ohsaka:
Good call. I always do things from my laptop over the USB cable... I forget about doing things with just the phone.
[G1 Android Development] Ohsaka:
Have you tried going into terminal or starting an adb shell and typing 'reboot recovery'?
[G1 Android Development] mianosm:
Worked perfect (aside from having to get su back).

Thanks for the work cyanogen. = )
[G1 Android Development] Amdathlonuk:
I have exactly the same build as you. However I would have NO CLUE on what to do if this went wrong, so think I'll leave well alone for a while.......
[G1 Android Development] mimic1011:
no recovery!

I did this and now its stuck at the black and white G1 scrren when I try 2 go recovery mode, don't have a comp right now so I can't do the fast boot, is their anything I can do from the terminal? Please pm me
[G1 Android Development] BSDADON:
In the first post are directions for doing it through terminal, but you say you are stuck at the G1 screen so I don't know how you would access terminal:confused:
[G1 Android Development] mimic1011:
I had cyan mod 3.6

New hardslp

Cyan Recovery mode 1.2

Downloaded 1.3 and entered terminal commands

Phone won't go past boot screen when I hit home+power

I have no computer right now

Please pm me.
[G1 Android Development] mimic1011:
thanks

I thought that was for fastboot, thanks
[G1 Android Development] kevo:
I'm on same build, and T-mob uk and all works fine here, home+power takes me the the new recovery.
[G1 Android Development] bjehsus:
Fastboot.. :/

It boots fine, I just seem to have lost access to the recovery console..

I used CM recovery since the first version, and haven't had any problems before. I'll try flashing it with fastboot.
[G1 Android Development] sim64one:
nandroid restore

My DREAM (not mean the phone :)) it is now reality.

Thank you a lot Cyanogen:cool:
[G1 Android Development] cyanogen:
Sorry about the setuid (su) bug. I just uploaded a 1.3.1 that fixes this issue.
[G1 Android Development] cidica:
woot 1.3.1. will give this a shot after my phone gets a full charge. Thanks for the update cyan :)
[G1 Android Development] bjehsus:
Flashed with fastboot, and still home+power starts fastboot.

Going to try flashing a different recovery.img
[G1 Android Development] JAWheat411:
Man this is freaking awesome. You can back up your phone and restore it without even using a computer.

This has been needed for some time. Thanks cyanogen
[G1 Android Development] alapapa:
thx...1.3.1 works as advertised
[G1 Android Development] bjehsus:
Successfully flashed back to cm1.2 without issue.. :/

Any ideas?
[G1 Android Development] cjkholt:
Same thing happened to me, I am going to try again
[G1 Android Development] abteer:
Thanks for the fix cyanogen. You are too good.
[G1 Android Development] cyanogen:
Redownload and check the md5sum before you flash the thing.
[G1 Android Development] bjehsus:
I did, three times..

CM1.3.1 seems to have fixed whatever was happening, flashed successfully. =]

Cheers, man.
[G1 Android Development] cjkholt:
tried 3 times, no go, I will try flashing back to 1.3
[G1 Android Development] notxel21:
Here is an easy way to flash this from Terminal:

Install from terminal

Open terminal, and type:

su

cd sdcard

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

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

reboot recovery
[G1 Android Development] tulamidan:
I had the problem that it didn't want to reboot into recovery mode after the 1.3. After flashing to 1.3.1 the problem was solved. Good job. I like the easy nandroid recovery. No more hassle after playing with a new rom that requires going back to the good old one.
[G1 Android Development] Mr. Moe:
Cyan...Just want to say awesome recovery. Like others have said. Now an easy way to nandroid backup, test drive other ROMS and restore backup all while driving..Friggen awesome work. Just what we needed.

NOW I hope SOON we can get the MyTouch Rooted, bcuz I am really looking into getting on the early release list next week.
[G1 Android Development] hiroots:
stoked, i like the usb toggle. its gonna be really useful when flashing roms, and finally a easy nand restore. could of used it last week.
[G1 Android Development] cyanogen:
I posted an update.zip format of this so you don't have to mess around with terminal. See the first post for info.
[G1 Android Development] sim64one:
a little problem

after installing recovery 1.3.

Try to install 1.3.3 give this on terminal:

root@sim-top:~/Dream/ROM#fastboot devices
[COLOR="Blue"]????????????[/COLOR] fastboot

Then remove battery and restart again in fastboot mode:

root@sim-top:~/Dream/ROM# fastboot devices
[COLOR="Blue"]HT935NG05828[/COLOR] fastboot
root@sim-top:~/Dream/ROM# fastboot erase recovery
erasing 'recovery'... OKAY
root@sim-top:~/Dream/ROM# fastboot flash recovery cm-recovery-1.3.1.img
sending 'recovery' (4024 KB)... OKAY
writing 'recovery'... OKAY
root@sim-top:~/Dream/ROM# fastboot reboot
rebooting...
root@sim-top:~/Dream/ROM#

:)
[G1 Android Development] uberingram:
I just did a test drive of the built in nandroid restore and it performed flawlessly. You are the man, cyanogen. THE man. :D
[G1 Android Development] lstevens86:
nandroid with restore feature nice job. keep it coming. happy 4th of july:):):)
[G1 Android Development] KyleK29:
Some feature suggestions for future, if possible:

- Ability to "wipe" (or reformat with same filesystem) EXT drive. This is great for when changing roms.

- Ability to take an .img (or .zip it) of EXT drive.

Excellent work otherwise.
[G1 Android Development] hiroots:
ay man where u gettin 1.3.3 at? were all still on 1.3.1.
[G1 Android Development] Binary100100:
Yeah dude... your a week early! :p
[G1 Android Development] marshallladd:
Just did my first nandroid restore from recovery mode. Awesome and flawless. I tried installing stericsons HTC Music port on cyan3.6.2 without reading the HTC Music player thread, which says the two are incompatible. Non-stop home screen force closes and reboots. Not fun, but nandroid restore from recovery and presto, all while doing my grocery shopping.

This is the best.
[G1 Android Development] Denkai:
what do you use to make a screen shot?
[G1 Android Development] alritewhadeva:
dude its so blueeee :eek:
[G1 Android Development] Chedderknight:
awesome!! thought I did it wrong but tried it for kicks, legend status indeed.
[G1 Android Development] indiekid97:
Great Work, I felt outdated whenever I saw "JF1.43" in my recovery console

:p

Love the move AppsToSD option, now I have one less step to do after a wipe
[G1 Android Development] sw20matt:
I love it, THANK YOU!
[G1 Android Development] joe v:
loving it!!! life just got easier ;)
[G1 Android Development] malaeus:
are there any issues with nandroid from JF1.43 recovery or is this the same one?

the "repair ext file systems" is that just the upgrade to ext3? or will it actually attempt to fix any issues.

where is the fix_permissions.sh option in this ?

and the apps2sd from this menu, is there any real difference between this and marcus's apps2sd application?

im using JF.143 recovery right now with your 3.3.8 and hero v1.2 theme.

i guess what im really asking, is simply, should i flash this recovery or stay with JF for the time being?

thanks

--peace
[G1 Android Development] joe v:
is there options in the "repair ext filesystems"? or does it just wipe anything on the ext?
[G1 Android Development] bkmo:
Looks to me that it does an fsck of the filesystem. Shouldn't need any options, and it is a repair not a re-format. Nothing should be lost.
[G1 Android Development] DVS_Sokar:
Is there a in phone option for formating your Ext2 parition without firing up your favorite partitioning software?

I want to wipe my EXT2 and start from scratch..

----

Feature Request on this utility.

Cyanogen - Nandroid Restore from your utility =) Please
[G1 Android Development] Rickster08:
I am also wondering does the alt F...automatically create a ext 3?
[G1 Android Development] cyanogen:
It just runs e2fsck on your filesystem. If you want to convert to ext3 you have to do it from console (which I seem to have broken, wait for 1.1).
[G1 Android Development] joe v:
su

#rm -r /system/sd/*

#reboot
[G1 Android Development] malaeus:
are there any other issues with console? for instance the fix_permissions.sh

should we continue using that script inside terminal emulator once booted as your other post shows? or can it be used inside 1.0 at this time.

and on that subject of the fix_permissions.sh file. should that be done after EVERY update.zip? including themes?

thanks

--peace
[G1 Android Development] G'uno:
I Swear to BOB!

It never ends...

Cool Stuff, I Thank you for the constant hard work (all of you)

:cool:
[G1 Android Development] prash:
Cyanogen is quickly becoming my favorite ROM cook, this loaded perfectly without any issues, and the blue looks way better on screen than screenshots. Great job on trackball support too! Way to think ahead.

Keep up the great work, with this and a new stable CM rom, I'll be sure to donate some beer towards you.
[G1 Android Development] DVS_Sokar:
Thanks Joe .. That was what I was thinking.. I was just being stupid about the asterisk.
[G1 Android Development] Rickster08:
Great job !!! LOving the blue and no need to open the keyboard.....:)
[G1 Android Development] Rickster08:
is alt-x not working as It wont open to type commands...
[G1 Android Development] bryon13:
No console. ):

nm... I couldn't see the last few posts when I posted about the broken console, now I see it's a known issue. My appologies.
[G1 Android Development] overground:
This may be a stupid question, but all my questions are. If 1.3 seems to have taken fine for me, is it recommended I still put 1.375 over it? Just kidding, I mean 1.31.
[G1 Android Development] sim64one:
ops!

OK guys :D

I'm come back to 1.3.1 - lol
[G1 Android Development] temporizer:
Its not a stupid question actually.

What exactly does that mean and the benefits of it?
[G1 Android Development] Pinesal:
The Hero theme comes with the HTC music app and it works with Cyanogen's.
[G1 Android Development] marshallladd:
If I am not mistaking, people were doing nandroid restores from recovery in 1.3 and they were no longer able to use "su" in the terminal, which pretty much is like loosing root. setuid permissions fix puts "su" commands back in for 1.3.1.

Someone correct me if I'm wrong.
[G1 Android Development] marshallladd:
It works up to 3.6.1. according to stericson then its not compatible with 3.6.2(verified by my compete crash of the home screen). He is releasing an update for 3.6.2 he has said.
[G1 Android Development] overground:
Is it only supposed to happen after a nandroid is restored? SU is working fine for me, but I haven't restored any nandroids. I'll just flash it anyways.
[G1 Android Development] marshallladd:
yes, just after a restore.
[G1 Android Development] huh28:
lost SU = loosing root?

So in excitement from 1.3 being released, i quickly did a nandroid backup then restored it. Worked like a charm!!!

Today, I tried root booter to reboot my phone, but i found out that I've lost root :(

Now I don't know what to do, I've flashed 1.3.1, but when i go into the terminal and type su, still get "Permission denied". Any suggestions?
[G1 Android Development] widto08:
Does 1.31 work with the newer hero roms since this uses a newer kernel than the ones found in the hero roms or does this not matter?
[G1 Android Development] cyanogen:
It was a bug with the 1.3 recovery. The fix is easy, boot into recovery, go to console and type this:

mount /system
chmod 4755 /system/bin/su

Doesn't matter.
[G1 Android Development] ryce124:
cant backup anymore :/
[G1 Android Development] ei8htohms:
alternate root fix

The other way to get root back (if you don't wanna type in Console) is to just reflash a rooted ROM.
[G1 Android Development] cyanogen:
You need to provide more information, posts like this are useless.
[G1 Android Development] ryce124:
What do you need to know?

I was able to back up on your recovery 1.2

was using your ROM 3.6.2 and your recovery image last time I backed up.

Flashed to 1.3.1 recovery image and it tells me i have an error in backing up
[G1 Android Development] cyanogen:
Go to console and type this"

nandroid-mobile.sh backup

It will tell you the errors. Most likely your SD card is full or your battery is low.