yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] Mi|enko:
Worked a treat, no issues here. :-)
[G1 Android Development] hamshu:
Ah thanks a ton.

How would I run Fix_Permissions.sh. Open up Console(ALT+X) then SU, then SH Fix_Permissions.sh?

Sending a beer your way soon.
[G1 Android Development] Binary100100:
Out of memory?

# su

su

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

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

mtd: write error at 0x00240000 (Out of memory)

mtd: verification error at 0x00240000 (Out of memory)

mtd: wrote block after 1 retries

mtd: write error at 0x00340000 (Out of memory)

mtd: verification error at 0x00340000 (Out of memory)

mtd: wrote block after 1 retries

#

that's the error I got when I tried 1.1.

edit... but it seemed to work anyway. Interesting...
[G1 Android Development] JAWheat411:
Awesome great work. Seems more useful now.
[G1 Android Development] chief2842:
Can I use this is I have the hero rom?
[G1 Android Development] xidominicanoix:
i shouldnt see why it wouldnt work .. but you should let cyan answer that for sure
[G1 Android Development] calypso78:
yes u can. i installed it on mine and works like a charm. :)
[G1 Android Development] jroid:
of course, worked great for me.
[G1 Android Development] ckessler235:
i really dont know what to say about this dude... worked like i knew it would !!

CYAN, YOU ROCK !
[G1 Android Development] spikus:
i am using hero also and it seems to work well for me also. great job cyanogen, between this and 3.4 jf modded rom...you got some good stuff going on.

hell, not having to open the keyboard and being able to use the trackball might be the best option, i think.
[G1 Android Development] jrnnoruka:
how do you restore the nanodroid .img file

i have already back it up but i want to know how to restore it
[G1 Android Development] mianosm:
http://code.google.com/p/android-roms/wiki/NANDROID_Fastboot
[G1 Android Development] Ryanmo5:
Running like a champ, much thanks donation heading your way.
[G1 Android Development] DreamcastDC:
Great recovery image, hope that Nandroid works for me this time, with JF 1.42 it never worked for me.
[G1 Android Development] nolageek:
BE CAREFUL!

The thing about enabling the trackball is that ALT-B and ALT-W are right next to each other. I just went to backup before upgrading to CM 3.4 and the ball rolled as I pushed it and I wiped my phone by accident. Totally user error, but Cyan.. can we get a prompt before it wipes?

:/

EDIT: OMG. I just did it again. Is my trackball just hyper-sensitive or am I just that stupid? (Don't answer that!)
[G1 Android Development] cl2eep:
Love it! With adb it is easy as pie. I renamed the file "recovery.img" to reduce the chance of a typo, and put it in the root of the sdcard.

Voila!
[G1 Android Development] SimonNWalker:
How to handle recovery images!

I want to try and handle recovery images in the JAB database.

Anyone got any ideas of the best way to handle this?

I could just add this as another build, but it's not really a build.

or I could add recovery images as a field within each build.

Give me some feedback guys. What would you like to see!!

PM me or email at simonnwalker@gmail.com

Thanks

Simon
[G1 Android Development] xidominicanoix:
A separate database would make sense, since they don't fall into the category of 'build' and they don't necessarily belong to any specific build.
[G1 Android Development] Neromyr:
I tried that and it still didn't work. it still freezes at the G1 screen when i try and enter recovery mode. any other ideas or solutions that might work?
[G1 Android Development] pensive:
Stop dribbling out bits of info and post in detail

what you did (exactly) and what you saw (exactly). How many times do you intend to write "it does not work?" You are not even providing enough information to analyze the problem.

What ROM are you running?

Just exactly what have you tried? Does someone need to get info out of you

with pliers or a rubber hose?

Have you installed fastboot? Have you tried using that? What were the

results?
[G1 Android Development] Neromyr:
First of all please calm down. I'll admit i'm not the best when it comes to working with this but i do try. so there is no need to get upset with me simply because i'm not as skilled with this as you are. Second Yes i tried typing it exactly as you showed. and it went through at least i'm assuming it was successful since i got the pound sign after a few moments. I am running Cyanogens 3.3.8 Rom with the 2.22.19.261 radio. I can't remember which SPL i have though it was one you had to install the radio update for before you could use it or it would brick your phone. as far as fastboot goes. i think when i installed the SPL it said it was a fastboot enabled SPL so i didn't know if that meant it installed fastboot on my phone or not. what i have tried so far. I've tried the installation method that was posted with the revovery-1.4.img i have tried renaming it simply recovery.img and installing it the way that it shows in the tutorial when you first root your phone. I tried the method that RikuPW posted and i also tried the method you suggested where i enter "cp /sdcard/cm-recovery-1.4.img /data/recovery.img

reboot" i tried it with recovery.img at the end and i've tried it with cm-recovery-1.2.img at the end (since that was how i got version 1.2 to install). each time being sure to type EXACTLY what was posted. with the exception of RikuPW's method where i ended up getting the "write: No space left on device" message and the other methods seemed to have worked since i got the # sign on the next line. None of them have let me access recovery after following the directions.
[G1 Android Development] pensive:
Before you can do anything else

First you have to understand that "fastboot" is not and never has been an Android program, it is a PC program, and the previous post explicitly said so. The link below will help you to install the SDK on your PC (not your phone). After you install the fastboot on your PC you can start dealing with your problem.

http://androidforums.com/android-tips-tricks/6905-windows-driver-install-using-adb-fastboot.html
[G1 Android Development] Charrion:
I'm assuming you meant to say you can't get it working. If you you download the 3.0b version from the google code page here and set it to emulate a german carrier instead of T-Mobile it should work fine.
[G1 Android Development] shaff:
hi

thanks, it worked.
[G1 Android Development] xplosiv757:
Did anyone else lose their Default G1 ringtones and notification tones when updating to this build?
[G1 Android Development] miketaylor00:
This isn't a build. It will only affect your recovery partition. It shouldn't touch anything on your system or data partitions.
[G1 Android Development] xplosiv757:
Apologies, I have more than one XDA thread open, I replied in the wrong one ; /
[G1 Android Development] TheWishy:
Hi,

I'm sorry for the n00b questions. I've had a good look through. I might have the same problem as XL3N7, but he didn't come back with any response.

I have a newly rooted G1, based on the rooting instructions here - http://xdaforums.com/showthread.php?t=442480

I've then moved onto flashing this. I start up telnetd, telnet in and run the above standard commands.

First reboot is great, I get the full recovery screen, can use the scroll wheel, etc. Generally, looks to me like the flash has been sucessful.

I go with home and back, and boot back to UK Spec RC7. If i then reboot again, i get the standard flash screen again (Triangle !) and get the below error

e: can't open /cache/recovery/command

As i said, i had a dig through, but wouldn't find anything that matched. Any thoughts? Think its wise to get this working correctly before i try to update baseband and Cyan v4
[G1 Android Development] pensive:
You need to overwrite the old recovery.img

Find where your old recovery.img is, and overwrite it with the new image.

In the terminal emulator

1)su

2)cd /

3)find / | grep recovery.img

Once you find the folder where the recovery.img is, copy the new recovery.img over it.
[G1 Android Development] TheWishy:
Thanks

I can't find recovery.img, but I can find /cache/recovery and /sbin/recovery - any thoughts? (This is from the Alt-X terminal - can't SU but i've got a # prompt so assume i'm root already)

Did try cp /system/recovery.img as suggested here - http://xdaforums.com/showthread.php?t=443041 - but same problem
[G1 Android Development] pensive:
You are in the wrong place.

You should be in the terminal emulator, not in recovery console.

You can do this in the recovery console, BUT first you have mount some file systems

mount /sdcard

mount /data

mount /system

mount -o rw,remount /system

Then look for recovery.img
[G1 Android Development] TheWishy:
I couldn't find anything but /system/recovery.img (Which i'd put there), but copying again from the recovery console seems to have worked!

Thanks for your help
[G1 Android Development] pensive:
It is good that it worked, however,

The first time around you copied it into the wrong place. You copied it into

the RAM mount point /system NOT into the actual file system.

After the /system was mounted read/write and you copied it the second

time it went into the right place. The file you found after /system was mounted,

in fact, was your old recovery.img

The RAM copy is gone now any way, so there is nothing more you

have to do.
[G1 Android Development] zDisturbed1:
Im having trouble when I type flash_image recovery /sdcard/cm-recovery-1.4.img into the recovery console or better terminal it gives me the same error amounting to that its the wrong command and that it should be flash_image recovery /sdcard/ cm-recovery-1.4.img a space between partition and the .img but when I try that I get an error saying /sdcard/ is an unknown partition can anyone help me?
[G1 Android Development] giovannirm:
Hi everyone!!!:)

is it possibile with the recovery console (ALT+X) change the bootloader image?

if yes, how??? thanks
[G1 Android Development] :
Wow!

Well, I've been working to get this recovery for about three hours:

My problems:

When I was able to get to the recovery console (HOME+POWER) and typed everything in like the instructions on page one I got: flash_image: not found

So I started reading through the threads and tried flashing through the terminal emulator, got a similar error.

Upon reboot to recovery console I now get a white screen with three androids skating on a skateboard with Serial0 highlighted in yellow, white background, and in the top right it reads:

DEA100 PVT 32V

HSPL10.95.3000

CPLD-4

RADIO-2.22.19.261

Oct 20 2008

Any ideas?

Before I was running Cyan's 1.31 recovery along with Cyan's 3.8 ROM and it worked PERFECT! I just want to upgrade!

Any help would be appreciated thanks!

-joseph

EDIT: If I pull the battery out and reboot, the phone reboots normally, not bricked....yet
[G1 Android Development] mikedmeyer:
That's the fastboot screen (camera+power). Make sure your camera button isn't stuck.
[G1 Android Development] :
Hmmm...for a second I thought that was the problem, its not stuck, and I just tried camera+power (fastboot) and it gets me the same screen, odd.

-joseph
[G1 Android Development] mikedmeyer:
Well, you can do anything from the fastboot screen, from flashing the recovery image to restoring a nandroid backup. Start there.
[G1 Android Development] :
Thanks Mike!

FIXED IT!

FROM ADB I followed these instructions:

-joseph
[G1 Android Development] rberger13:
Question

I installed the utility and it works great. My issue is somehow my recovery image reverts back to the crappy base one, not the 1.4. Any thoughts? Am I doing something wrong?
[G1 Android Development] xidominicanoix:
if you're restoring a backup that contained the old recovery this should happen
[G1 Android Development] maxisma:
Or if you stay on the stock ROM with cyans recovery.
[G1 Android Development] pensive:
Yes, you failed to read page 140 in this thread.

Your problem has been brought up, explained, and fixed by several people.
[G1 Android Development] :
Hi, i like the recovery image, but i need still some questions answered:

1.

If i do something with Alt-x, how can i return from console to the green setup screen?

exit or quit doesn't work.

2.

I often use

parted /dev/block/mmcblk0

print

Will this be possible to add to a setting shortcut like ALT+S

e.g. ALT+P for parted and print info.

So we know with one click if the SD-Card is formated right.

3.

I often try different ROMs with different swap-sizes, so i often wipe, but i alays have to manually delete and recreate the ext3 and swap-file on sd card.

Is there a quicker way to erase all data on ext3 and swap and recreate when doing a wipe with ALT+W?

It always takes a long time to delete and repartition the sd-card.:(
[G1 Android Development] the_fish:
1. use reboot recovery

2. create a file "print.sh" for example, with the content you want it to run, so in this case:

parted /dev/block/mmcblk0

print ( you might have to type this in manually though )

push it to /

and run sh print.sh

3. why don't you use a swapFILE until you switch to a rom?
[G1 Android Development] :
Thanks for quick reply!

I did this like described here in forum:

print
Model: Unknown (unknown)
Disk /dev/block/mmcblk0: 7969MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos

Number Start End Size Type File system Flags
1 512B 7437MB 7437MB primary fat32 lba
2 7437MB 7937MB 500MB primary ext3
3 7937MB 7969MB 32.2MB primary linux-swap(v1)

So i have got a 32MB swap partition and 500MB ext3 partition.

If i wipe all old data from old ROM stays in ext3 and swap and e.g. the new JACxHero build shows 64 MB swap in swapper app.

With parted still 32 MB swap. I'm confused now! :confused:

Then i always "rm 2" and "rm 3" the ext3 and swap-partitions and recreate them to avoid hanging in bootscreen or have other issues, but isn't there a quick solution to delete all data of ext3 and swap with the wipe?

Seen the recovery image on mytouch-device and i'm missing the option "format ext+swap"
[G1 Android Development] pensive:
Use the newer version of nandroid-mobile.sh

/sdcard/nandroid-mobile.sh --save YourOwnROMName

will save the entire environment

/sdcard/nandroid-mobile.sh --switchto YourOwnROMName

will restore the entire environment

ext2,3,4 also get cleaned in the process
[G1 Android Development] :
I'll look into this!

btw i found this advice:
[G1 Android Development] Orange Crush:
Does nandroid back up installed apps when using apps2sd or does it skip those?

I want to reformat my SD card and set up a swap partition, and don't want to lose what I have in the Ext2 partition.
[G1 Android Development] vshzR:
help installing the recovery images with the proper HOME + POWER screen

I have been trying to get this backup to work and I keep running into problems where either in Terminal Emulator I am getting "Permission denied", both when I type in "flash_image recovery /sdcard/cm-recovery-1.4.img" or "su flash_image recovery /sdcard/cm-recovery-1.4.img". Also if I reboot into recovery mode, I am not getting the awesome one, but still the bog standard one that is there when you first get the phone. Have I missed something? I am currently running CM v 4.0.4 so I have the phone rooted, but I just cant get this to work and it makes me want to put my head through the desk...can someone save my head please?

OK, I have gotten the command to work, however now I have an issue with the next line where it does not know what the command "fastboot" is

fastboot erase recovery

fastboot: not found
[G1 Android Development] pensive:
"--save NAME" option

Will preserve the entire ext2 partition along with the rest of the backup.

Search this thread for the latest nandroid-mobile.zip, unzip it to your sdcard

and run it from there until the new options get added to the recovery image.

It is assumed the script is run within the recovery console.
[G1 Android Development] ei8htohms:
standard Nandroid does not back up Ext partitions

Use SwitchRom or the latest Nandroid-Mobile instead.
[G1 Android Development] pensive:
P.S. There is no need to take drastic measures.

If your goal is to set up swap only, there no need to reformat your card.

Simply resize your ext2 partition leaving a little space for the swap.

parted /dev/mmcblk0

resize 2 oldbeg newend

partfs primary linux-swap newend endofsdcard
[G1 Android Development] Jacob_K:
Will resizing not touch the data? As I want to make my swap bigger but i will have to resize fat and ext3. Will it delete any data on my fat32 partition?
[G1 Android Development] pensive:
parted will shuffle(move) your data, as long as

Ext2 has enough free space to chop off for the swap. If not it will fail and tell you so.

Still do the backup first to be on the safe side.

The case with enlarging the swap is only slightly different. The ext partition still needs to be

reduced in size, but the swap partition is best deleted and recreated.

rm 3

will remove the swap partition. Then recreate it using the new end of the ext partition as the

new beginning of the swap partition.
[G1 Android Development] rikupw:
a 4th partition for custom script utilities

Hey Cyanogen! Idea for you, not sure if you'll like the idea or not (since it could be slightly negative for newer users)

I know for a fact that your latest builds boot with an SD with more than 3 partitions, since I do it myself, what about allowing the users that have a 4th parttion, (add it to fstab of course) it somewhere in the rootfs in recovery? allowing the user to ALT+X mount /sd (or whatever) and cd into that folder, use a script (like switchrom, or a custom after-update script, etc). instead of having to type

#mkdir /sd
#mount /dev/block/mmcblk0p4 /sd
#cd /sd
#sh 'etc etc etc etc etc'

its kind of annoying, though when i'm using recovery menu for extended times i just echo the fstab info on to /etc/fstab anyway, but its still a pain in the butt for those who are not by a computer all day :(

I love this recovery image, and I'd compile my own, (or unpack/repack my own) if I could just get rid of the bleeping A N D R O I D _ and make command work properly >.> *le sigh*

KEEP IT UP STEVE!
[G1 Android Development] Orange Crush:
What am I screwing up here?

Alright, I'm pulling my hair out here . . . maybe there's something obvious I'm doing wrong that I'm missing. I test drove the Jac Hero build, which required changing the SPL. That all ran fine, but I didn't like it, so I want to put it back the way I had it w/ Cyanogen.

I didn't want to risk bricking it, so I went back to stock, followed LucidREMs rooting instructions:

http://files.lucidrem.us/jf/ROOT/g1_root.txt

If I flash recovery with the recovery_test_keys, it works fine. But as soon as I flash Cyanogen's version, it never gets to recovery, always kicks me into the SPL screen (Hard SPL--Androids on skateboards).

I've tried flashing from the phone w/ the CMrecovery on the SDcard, I've tried using the fastboot method . . . both appear to successfully flash the recovery partition . . . but I can't get it to go into recovery mode.
[G1 Android Development] miketaylor00:
What does your SPL have to do eith you recovery image? I don't understand why you chose to downgrade you SPL. You can use the 2 together without a problem.

It sounds like you didn't get recovery reloaded. Go into fastboot, erase the recovery partition and then reload the cm recovery. You should be golden after that.

What exactly do you mean when you say you can't boot into recovery?
[G1 Android Development] Orange Crush:
Power down, power up holding home and back. It just goes directly to the SPL as if I powered up holding home+camera.
[G1 Android Development] pensive:
you corrupted your recovery partition

That is why it kicks into the boot-loader. It was not wise to downgrade

the spl.
[G1 Android Development] Orange Crush:
Still, I can't see why the spl would even touch the recovery partition, nor does it explain why the smaller recovery-test-keys image works just fine . . . even more telling was when I restored my Nandroid backup via fastboot--erased each partition before I flashed--everything restored perfectly . . . except recovery.

Might this be a problem with the internal memory itself?

Any way to check?
[G1 Android Development] miketaylor00:
Pensive, do you think dropping in dreaming.nbh will help?
[G1 Android Development] miketaylor00:
The SPL touches more than you think. If the smaller recovery works, then something is wrong or corrupted with your recovery partition as Pensive said. Have you tried reinstalling the radio and the upgrading the SPL back to Hayakuro? If you don't want to do that, I would suggest loading the dreaming.nbh and see if you can reinstall CM recovery from there. Wait for Pensive to check in on my idea before you do it. He might have a better one.
[G1 Android Development] androidmonkey:
I am trying to flash the recovery image. When I do ALT-X in the existing JF recovery, it goes to the Console. I cd sdcard the ls, nothing shows up on the sdcard.

Any ideas?
[G1 Android Development] miketaylor00:
mount /sdcard
[G1 Android Development] pensive:
It is no longer relevant why and how.

What is relevant is what still works? Can you normally boot into your ROM and

which version is it?
[G1 Android Development] Orange Crush:
^I already did, I'm afraid. Here's the order of operations for what I did (this has happened before, btw, but the last time using fastboot to erase and reflash recovery fixed it):

-Ensured I had the up to date radio

-Flashed the SPL from here:

http://xdaforums.com/showthread.php?t=534461 (for whatever reason, this SPL will cause the G1 to hang at the G1 logo screen until the Hero ROM is installed

-Entered cm-recovery 1.4 to flash the Jac hero Rom from here:

http://xdaforums.com/showthread.php?t=534479

-Booted fine into Hero, albeit sluggish, decided I wanted to go back to Cyanogen

-For fear of picking the wrong SPL and bricking the thing, I just restored DREAMIMG.nbh and re-rooted.

-No dice on geting cm-recovery to come back up. Tried going to HardSPL, no dice, updated radio, no dice, restored Nandroid via fastboot, no dice.
[G1 Android Development] Orange Crush:
Everything works except cm-recovery. recovery-testkeys works fine if I flash that. Main OS works fine, I'm using Cyanogen's latest stable 4.04, i believe.
[G1 Android Development] androidmonkey:
Thanks.

I am following the instructions in the first post, it didnt mention that :)

I am having issues now flashing.

I get sh:flash_image: not found

I used this command

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

Any ideas?
[G1 Android Development] pensive:
Hm, I am in danger of repeating myself.

Get into the terminal emulator

1)su

become root

2)cp /sdcard/cm-recovery-1.4.img /data/recovery.img

assuming the image is at the root of your card

3) reboot

4) stop randomly flashing stuff.
[G1 Android Development] pensive:
Because you are in the wrong place.

Get out of recovery and do it in the terminal emulator.
[G1 Android Development] androidmonkey:
Yep, I tried that after reading someone who did it in the thread. Someone should update the first post.

Thank :)
[G1 Android Development] pensive:
It is possible to do from the older cm recovery but

more steps are required and flash_image has a different name without any

aliases defined. 1.4 image has flash_image link defined in the recovery.
[G1 Android Development] Orange Crush:
I followed your instructions and copied cm-recovery-1.4.img to the /data/recovery.img via terminal and rebooted. Upon rebooting, recovery.img was no longer present in /data, but attempting to reboot in to recovery still kicks it to the SPL.
[G1 Android Development] pensive:
It is a little worse than I thought.

See, if you have the following device

/dev/mtd/mtd1

It is number 1 not l at the end.

cat /dev/zero > /dev/mtd/mtd1

After that attempt to flash it again, or copy into /data again.

Actually before you do anything else you need to verify that the image

you have on your sdcard is not itself corrupted. Run md5sum on that

image and compare it to what's on the web page.
[G1 Android Development] Orange Crush:
Md5sum matches. /dev/mtd/mtd1 is present, but catting zeroes to mtd1 gives a "write: i/o" error.