yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] stellarman:
Hang in there...

Looks like some nice work.

If you haven't already done so, PM Cyanogen and let him know what you are working on. He would probably be glad for the help.
[G1 Android Development] drebel1:
i have been reading and reading i cant seem to find how to reformat my ext3 useing this i thought i seen it once before but i cant seem to find it again can someone please send me to the correct page thank you
[G1 Android Development] cyanogen:
Yeah definitely, the code for the recovery UI is on Github if you want to hack on that as well.
[G1 Android Development] digital006:
Thanks, I'm at work now so will try it out when I get home in about 10 hour
[G1 Android Development] D-e-v-i-l:
is there a way to change the keyboard layout vom qwerty to qwertz?
[G1 Android Development] pensive:
UI massaging

I am not averse to playing with the UI, but testing it might be an issue. Testing the script was easy, pushed it with the adb, with g1 in the recovery mode, changed permissions. I am not sure, however, what kind of build environment is requisite for the recovery UI and how to hook the modified code in. Is there is a set of instructions? Better yet is there a download that

is already all set up to build recovery.img?

My initial thought was that the UI code could use FILE *fp = popen ("android-mobile-{restore,backup}.sh", "r+") to open a bidirectional pipe to the script's stdin/stdout. Then the UI could take the input and pass it on.
[G1 Android Development] temporizer:
what script?

if you used the one on the recovery, you have an old recovery, 1.3.1 does not have that option anymore.

try to remove the shortcuts on your home screen and recreate them.
[G1 Android Development] markimar:
Quick question is there a way to get from terminal in recovery mode back to main recover menu?
[G1 Android Development] spinjason:
When you are done inputting your code type recovery at the # sign and press enter.
[G1 Android Development] spinjason:
Your talking about the console not the terminal emulator right. .
[G1 Android Development] temporizer:
this is correct.
[G1 Android Development] markimar:
Thanks so much I always removed the battery covet. LOL I knew there had to be s proper way
[G1 Android Development] temporizer:
I have heard you can only do that once then you have to reboot it by typing

reboot recovery

Or if you want to just reboot you can type

reboot

You can also power down the phone by typing

reboot -p

You should rarely have to take the cover off your g1.

If it freezes and cant get to the powerdown/reboot screen press

phone+menu+end

Take the cover off as a last resort.

:D
[G1 Android Development] DMaverick50:
i flashed the latest recovery image. how can i check to make sure it worked?

i put the update in my sd and flashed and it appeared to load, no errors or anything but in recovery it still says cyanogen v1.0....thanks
[G1 Android Development] hiroots:
r u serious? home power
[G1 Android Development] schwiz:
yeah it will be noticeably different than what you originally used to flash you update. I just gotta say this image is amazing the nandroid is so frakkin useful!
[G1 Android Development] DMaverick50:
i know how to power into recovery but it looks the same as before i flashed 1.3.1, i tried flashing it twice but i still have cyanogen v1.0 at the bottom of the recovery screen...
[G1 Android Development] schwiz:
then you did it wrong, it should be a differnt color, and have options for nandroid backup and restore, you should also be able to select options with the trackball instead of using the keypad
[G1 Android Development] VGPOP:
It would've been helpful if you wrote here how you fixed it.

Because I am having a similar problem.

I just got this new recovery image, and it won't even wipe or installed new ROM (Hero r2.5_slowSD). It says "Data Wipe Aborted" (as soon as I click ALT+W)

If you could please write what do you did to fix, I'd greatly appreciate it.

Or anyone here that have had similar problem and know how to fix this.

Thanks in advanced!
[G1 Android Development] DMaverick50:
i see.

i have the trackball navigation and nandroid backup options but no restore options so im guessing i have 1.2 even though it says v1.0 at bottom of screen. if i had 1.3 it would say cyanogen v1.3 at the bottom no? it says v1.0 currently but i remember flashing two recovery images total, i have the blue web background right now... sorry im making this difficult
[G1 Android Development] temporizer:
launch a command prompt like you are going to use adb.

Reboot your phone into bootloader. (Camera+power)

Press BACK until you see fastboot on your g1 screen.

Wait until your g1 connects to the computer.

In your command prompt type:

fastboot erase recovery
fastboot flash recovery cm-recovery-1.3.1.img

If you do not see any errors, it has flashed correctly

Press call+menu+end* to reboot your g1.

Let your phone boot up completely then reboot into recovery(home+power)

This information is on the first post for different circumstances.

*also known as "three finger salute"
[G1 Android Development] nicholasbithell:
Odd Request...

Cyanogen... I was wondering if you could create a special Recovery image. I am looking for a recovery image that has the "Update" and "Wipe" options removed from the image. I hope you can help! let me know! Donation headed your way soon!;)
[G1 Android Development] nicholasbithell:
I started a thread awhile back about password protecting the image so not just anyone could wipe or update the phone and I was told it was not possible. So now im looking into other methods, like just removing the features all together and when I need to update I will just use terminal to install different image. I know it seems like alot of work but I am trying to get every bit of security possible! so apps cannot be removed from my phone with out specific know-how of the System and its work-arounds.
[G1 Android Development] lolo2007:
I have the android system recovery utility build JFv1.42 and when I install the update zip it doesn t change anything can anyone help me please ?
[G1 Android Development] question.com:
if i dont have ADB how will I be able to use fast boot and fix the no space available issue? the phone reboots on its own every few min. also reboots as soon as i mount the sd card. sucks im not at home and dont have my pc. my laptop is 64 bit and is a pain to set up ADB. if anyone has any suggestions, please help out
[G1 Android Development] TheRealAru:
Just finished adding this onto my phone, this definitely is an incredible release and im glad to FINALLY have added it to my baby. lmao
[G1 Android Development] Superken7:
I have an ADP1, I have the latest official HTC update applied (radio 2_22_19_26, recovery signed-dream_devphone_userdebug-ota-148830 from HTC)

I am trying to get this cyanogen recovery so i can nandroid backup ( with no luck )

First i tried downloading in update.zip format, I copied it to the sdcard, rebooted into recovery, applied the update.zip successfully, but I don't see any changes in my system or in the recovery menu.

Then I tried downloading the cm-recovery-1.3.1.img, I opened a shell via adb -d shell, got root, then did a

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

No errors, it just silently completed.

However, when I reboot, everything is still unchanged. I dont see any changes in the recovery menu, I can't get into a shell from recovery, no alt+x, no alt+b, no busybox when fully booted, nothing.

I am obviously doing something wrong, might have missed a step.

Anyone knows why? =D

thank you!
[G1 Android Development] temporizer:
go back a page and look at my post.
[G1 Android Development] Superken7:
Thank you, that worked!

I would be very interested to know why the usual approach did not work for me.

thanks again!
[G1 Android Development] temporizer:
who knows.

i'm glad it worked for you.

that being said.

I wish people would read the WHOLE thread.
[G1 Android Development] Superken7:
Well, you are right.

I wish i had, too. I read like the first 30+ pages, used search in this forum and googled around, but could not find the answer (technically, still haven't. The "official instructions" didn't work). Unfortunately, my answer was on the 72th post...

I'm sorry you had to repeat yourself.

Although IMHO you should not expect everyone to read through 70+ pages, just like people should not have to read through 70+ pages in order to find the answer. What I mean is that a forum is not the best way to store and index information, so things like this happen from time to time.

(another thing is people not reading or not doing any search/research at all before asking, I think thats wrong)

Maybe cyanogen can update the first post to include this "anomaly" ?

So if anyone else encounters this strange behaviour, they will be able to figure out before asking, or reading through 72 pages =D . (Or maybe it's a bug in the recovery?)
[G1 Android Development] temporizer:
Cyanogen, is there a way you can add this to your FAQ?

There have been quite a few people having this issue.
[G1 Android Development] Elloco305:
Bypassing Setup

Is it possible to Bypass the Gmail Account Setup, ike in JF 1.50? Thank you.
[G1 Android Development] temporizer:
yes, just hit cancel.
[G1 Android Development] Elloco305:
Wow Bro, Thanks. I was expecting a reply tommorow. I guess i'm off to flashing.. I hope all goes smooth, Been reading alot of of posts of people not able to get it working right.
[G1 Android Development] temporizer:
use my method on page 71 and you can't go wrong.
[G1 Android Development] DMaverick50:
i ran a search in this thread but couldnt find the answer to this.

From what i understand i can create a 3rd partition with 1.3.1

I currently have fat32/ext3 and id like to know how to get to fat32/ext3/linux-swap. can anyone help? thank you
[G1 Android Development] temporizer:
Here you go
[G1 Android Development] DMaverick50:
many thanks
[G1 Android Development] pensive:
A further tweaked version of nandroid-mobile.sh

Cleaned up output not to use /dev/console to display available backups (now it goes to stdout), it runs the same way now on G1 console and via the adb shell. In addition, since some people had problems overwriting their latest recovery images with the earlier ones I added the ability to exclude any image from the restore operation.

for example

nandroid-mobile.sh restore 200907 -o norecovery nodata

will restore only boot and system partitions for the latest backup in July if the user does not choose a different backup in the process.

I currently keep the script on my sdcard since the recovery image /sbin gets trashed every time the recovery is invoked. The script needs to run in the recovery shell, since when it is invoked by the UI, via execv, stdin/stdout are closed and the default behavior results.

Hopefully it would be useful to some folk and there will be less of "I just trashed my G1, why is God punishing me like that?"
[G1 Android Development] pensive:
Umm, search for "parted"

There is a message titled My experience with CMrecovery parted
[G1 Android Development] jawash22:
I flashed this, but it says v 1.2 + JF at the bottom.....I have the new options using trackball and blue screen. :confused:
[G1 Android Development] pensive:
A few more thoughts given your specific situation.

You have two choices (assuming that your entire card is now occupied by fat32 and ext3 partitions) either shrink fat32 or shrink ext3. In the former case your linux-swap would end up residing between the fat32 and ext3 partitions. Since you already have your ext3 partition it is certain that it is partition number 2 (I suspect that apps2sd will work fine in either circumstance). I assume that you do not want to either lose your data or take your data off the card (especially gigabytes of it). It is also assumed

that you have not filled your partitions to the brim.

So, unless there is some reason why you do not want to shrink your ext3 that would be my choice, then the partitions will be numbered 1)fat, 2)ext3, 3)swap and physically would be in the same order.

Actually, since swapping on the card causes hell of a lot wear and tear on the card I would consider allocating space for 3 swap partitions at the end of the card. But setting only one up as linux-swap. When that partition stars wearing out, you delete it, and set up another segment as the swap.

Lets assume you have an 8096MB card, give or take. And lets assume you have the second partition starting at 7000mb and ending 8096mb

then after umount /sdcard

resize 2 7000mb 8000mb

mkpartfs primary linux-swap 8000mb 8032mb

giving you a 32mb partition for swapping and leaving 64mb free to move the swap later on as your card wears out and starts causing errors. I think it should prolong useful sdcard life.
[G1 Android Development] Elloco305:
You mean 'the three finger salute'? If so, How can that help?

Thanks in advance..
[G1 Android Development] Strapt:
ok so when I do the update.zip one .. it doesnt work ... I reboot and hold the home+power key and it still comes up as JF 1.42 and I tried that twice in a row .. then I thought . hell why not wipe and update ... tried that and the phone started to loop at the HTC screen ... not real sure how to get this on my phone .. the other method .. well.. I know NOTHING about adp and apparently couldnt get it setup right on my comp. Is there something wrong with the update.zip??

so anyhow I used to have the JF version but am now running the JacHero ROM the 2.63 one at the moment .. any help on how to get this on here would be great thanks!
[G1 Android Development] mcp2009:
i tried flashing the upgrade twice and it says i still have 1.2
[G1 Android Development] pensive:
Did you remove recovery.img from /system?

If you were running JF rom and installed JF1.4* recovery.img into /system

then it is going to be flashed every time the phone is booted overwriting any

changes.

Either delete (or move it) that file, or upgrade both the system and recovery

at the same time, etc...
[G1 Android Development] stevemartin1991:
where is the jf1.42 recovery.img in the phone system? im hoping just 2 delete it then reflash the new 1.3.1 thanks in advance....steve
[G1 Android Development] temporizer:
Go here and follow these instructions.
[G1 Android Development] stevemartin1991:
and if you dont have adb?
[G1 Android Development] johnnylicious:
can't wait for whats new for the next recovery image update :)

great job once again.
[G1 Android Development] stevemartin1991:
where is recovery.img saved on the phone/sd card that is all i want 2 know? surely some1 knows????????????? steve
[G1 Android Development] pensive:
Ok, here is a very simple way to check if....

you have an old image that is being flashed. You can do it either in normal

mode or in recovery.

1) Terminal emulator

2) su

3) cd /

4) find / | grep recovery.img

Mine is sitting in /data/recovery.img

5) If the file is THERE, you can check init.rc file if has a line flashing that recovery.img image

grep recovery.img /init.rc

6) You can actually simply overwrite that recovery.img with the new image

like (check the permissions first and set the same permissions after the cp)

cp $YOURDIRECTORY/cm-recovery-1.3.1.img /data/recovery.img

7)The new recovery should be flashed upon a boot

Simply erasing the recovery partition ain't going do it if the old image is being

flashed all the time.

My recovery.img is living in /data but I think under JF it was in /system.
[G1 Android Development] AndroidFiend:
ok i am a complete noob with this recovery thing.

can someone help out on flashing this whole thing without adb

do we have to flash the image and the update.zip?
[G1 Android Development] johnnylicious:
directions are on the FIRST POST of this thread,

please READ and follow directions its not that hard.

Cyanogen basically holds your hands thru this entire process...:p
[G1 Android Development] AndroidFiend:
yes i read everything i updated the .zip through recovery have that down and now with image do we have to install that too

also i see no difference in the recovery
[G1 Android Development] johnnylicious:
umm your "flashing" the recovery.1.3.1.img

you dont need anything with the update.zip

download Recovery 1.3.1.img from the first post

put into the root of your sdcard

and open terminal and type this in

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

simple as that.

it explains what i said in the first post... i don't think you understand what your doing...:confused:
[G1 Android Development] AndroidFiend:
wow i am really slow :P

i got it up and running

its my first putting a recovery thing on my g1 so i didnt know what i was doing but thanx alot :)
[G1 Android Development] ei8htohms:
we really need a guide to this recovery image and options

There is a lot of stuff CM Rec 1.3.1 can do that is not in the UI and is not obvious, but it takes a lot of digging in this thread and others to really know what the options are and how to use them. Any chance of getting someone to put everything together in one place? I'll gladly volunteer to help out, but I would definitely need to send a LOT of emails to an expert or two to make sure I didn't sound like an idiot or give bad advice.

Anyone wanna volunteer to play expert if I play secretary/scribe?
[G1 Android Development] pensive:
Shifting sands or recovery.

I am modifying the nandroid script now (for my own amusement and public use) to add a bunch of options and at the same time expanding the --help section for it. It might be added to the recovery, after someone else, in addition to me, kicks its tires.

Features being added.

1) Much better handling/error handling of command line options via getopt

2) Compression of backups (saves about 40meg out of 90+), 20 backups would take up only 1gig for those who do not have thick wallets for 16gig cards.

3) Removal of stale backups

4) Looking for *update*.zip in /sdcard/download, where your browser puts it

and copying or moving the chosen one into /sdcard/update.zip for flashing

5) Not working on at the moment but it would be good to be able to push out a compressed, archived backup to some web-based storage server, just

in case the SDCARD itself gets trashed.
[G1 Android Development] ComplexMinded:
sounds like a nice plan...
[G1 Android Development] alritewhadeva:
Hope you can get this to work :)
[G1 Android Development] curlz187:
how do i run a fastboot bcuz my phone is saying no space on device
[G1 Android Development] cyanogen:
Let me know when it's ready and I'll make a new recovery image with it, if you want.
[G1 Android Development] temporizer:
Sweet!!!!!!
[G1 Android Development] parrothd:
Does nandroid backup the ext3 partition?
[G1 Android Development] temporizer:
No, it does not, you will have to do that yourself.
[G1 Android Development] parrothd:
bummer... Just tar it or is there something else available?
[G1 Android Development] drewno1:
getting an error message when trying to do a nandroid restore via recovery

does anyone know the commands for the console to do it that way ?

Thanks In Advance
[G1 Android Development] ei8htohms:
this would be great

And if it's alright with you guys I'll put together a draft of a general user guide for installing and using CM Recovery and the various options for the (general - NOT development) Dream forum and bounce it off of whoever is willing to take a look (Cyanogen? pensive?). PM me or post a follow-up if you're willing to help out with some tech brain power (don't worry, I'll do the writing/formatting/grunt-work).
[G1 Android Development] temporizer:
if you have access to adb you can back up by

adb remount
adb pull /system/sd/* path/to/back/up/dir

then once you are done, you can restore by

adb remount
adb push path/to/back/up/dir/* /system/sd/
[G1 Android Development] Freddyrico14:
"To install update.zip format: copy to your sdcard as "update.zip" and flash it as normal and reboot"

Sorry guys but im trying to do this correctly what does "flash" mean? sorry for the stupid q?:confused:
[G1 Android Development] Shatterz:
I was doing the same thing as AndroidFiend, trying to install cm-recovery-1.3.1.zip (which is also avalaible in the author's original post) using the current recovery, which [for me] was JF's 1.42. This doesn't work. It installs normally with no errors, but nothing is actually done; the recovery stays the same

*Installing cm-recovery-1.3.1.zip does NOT WORK*

I had to use the .img and install it with the terminal (which ment reinstalling my old ROM). Is this how it should work (cannot install a recovery from recovery mode) or is this a bug?
[G1 Android Development] pensive:
Apparently I need to repeat this many times.

You need to get rid of the old recovery.img which is sitting in your file system

and is being flashed by init.rc every time you reboot, therefore nullifying your

previous actions. You flash did work but init.rc overwrote it.

This has nothing to do with cm-recovery, it has to do with the way JF had

set up the init.rc. (or whoever it is, whose rom you are using)
[G1 Android Development] KaL-EL3038:
alright i am a noob at this ....

Well I just happen to have got recovery like two days ago but I wanted to try a new room so itired doing th end and home button method to do the nandroid back up but every time I do it it says error couldn't do back up...so what am I doing wrong...I only have a 1gig memory card so I think it won't do it cause I have no memory but it doeesnt say anything about that so if anybody can help me that would be cool....and I already did the search this forum but no help..
[G1 Android Development] ei8htohms:
in my experience yes. that's the problem

Free up some space on your card and try again.
[G1 Android Development] Scholesville:
Do i need to flash Cyanogen v1.3.1 recovery image in order to install his Cyanogen ROMS or can i just stick to my JF v1.43 recovery image?
[G1 Android Development] pensive:
Nope, you do not need the CM recovery to use the ROMS

You can use one or the other or both.
[G1 Android Development] kicker1:
Thanks Max!! you saved me a wipe :)
[G1 Android Development] Drizzy Drake Rogers:
This would be even nicer if it woulp prompt me the home key for the nandroid backup and the terminal entrys because I intent to hit those accedentally lol!
[G1 Android Development] cyanogen:
Yeah the trackball is so sensitive on these things. I might add this.
[G1 Android Development] LvDisturbed1:
I'm having issues trying to install this. Where is this old recovery.img so I can get rid of it? Hell, does anyone know if I can use a linux-swap2 partition? It would be easier for me to do that.
[G1 Android Development] gwydionwaters:
this is gonna drive me crazy lol, i tried update method but have a rogers rom - rooted. so it overwrites, so i then changed out the existing recovery in data to the new 1.3.1 and it still is 1.2 when i boot :(
[G1 Android Development] pensive:
The process to recover from recovery issues

Tools required (at least):

Terminal emulator

root priviledges

1) Drop to shell using terminal emulator

2) su

to get root access

3) df

just to make sure /system /data are mounted

4) find / | grep recovery.img

to see where, if anywhere, your old recovery.img might be residing

5) pwd

to make sure you are in /

6) grep recovery.img init.rc

hopefully you will see a line like this one:

service flash_recovery /system/bin/flash_image -d recovery /data/recovery.img

NOTE1: the "-d" flag which tells the flash_image to delete a successfully flashed recovery.img so that it does not do it every time at boot time.

If you are missing this flag "-d" your phone will continue flashing that image, if it exists.

NOTE2:Your recovery.img may NOT be in /data, it may be elsewhere, 4) will tell you where.

7) either "rm recovery.img" or if you have space "mv recovery.img JF1.42-recovery.img" in case you want to move back.

8) At this point you can also flash a different recovery:

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

NOTE: no -d flag is used since you may NOT want to delete the image from

your sdcard, right?

reboot recovery (to see if it took hold)

If you either rm'ed or mv'ed that old recovery.img, it should work.
[G1 Android Development] masarliev:
I am noob and i want to install this recovery image. is there any way to brick my phony while updating