[Recovery] [15-May-2010] RA-dream-v1.7.0 (also for the Rogers Dream)

Firerat · May 16, 2010

rgawenda said:
I've had a very similar situation before, and not only in android, but other *IX systems. /sdcard *IS* a not a mount point only, it is a directory. If a mount there fails, you still can copy files to it. Thery'll be stored in the root partition (or whatever FS it belongs to).

maybe, but last time I looked the rootfs was ro

Amon_RA · May 16, 2010

Out of memory problems

Are you guys with "out of memory" issues using the terminal application when your phone is normally booted, or are you using the console (or adb) in the recovery mode?

Amon_RA · May 16, 2010

Some feedback :

To everyone complaining about "mount -a" :
- You don't have to enter "mount -a" if you are using the terminal apk when your phone is normally booted, you do have to use it when you are using adb or console in recovery mode.

- "mount -a" can give back an error if you don't have an ext partition, nothing to worry about.

You don't have to type "su" if you are root already...

I removed the not compatible with older apps2sd warning, it should all work as indicated by Firerat in this thread.

jkoenig00 · May 16, 2010

i used terminal w CM5t4. no errors with mount -a just memory error after flash recovery command. then rebooted into fastboot and plugged the phone into the comp, didnt do anything, then rebooted, retried, and it worked with the terminal app. i didnt have my setcpu or swapper running maybe that has something to do with it.

themapleboy · May 16, 2010

yes!! adb via recovery was a beautifull addition as is the new cyan themed recovery loving both of them

thanks alot

btw couldn't flash via console mount -a would come back with a could not be found (not exact wording you alrede know what it is) but it flashed w/o any issues via terminal and yes i have a ext 3 partition :S

qwerty3656 · May 16, 2010

Amon_RA said:
To everyone complaining about "mount -a" :
I removed the not compatible with older apps2sd warning, it should all work as indicated by Firerat in this thread.

Sorry - I read the previous Firerat posts, but I guess I missed something. Are you saying that even if we are running one of the old ROM's (e.g. a donut ROM), that the apps2sd of this recovery will support it?

Firerat · May 16, 2010

qwerty3656 said:
Sorry - I read the previous Firerat posts, but I guess I missed something. Are you saying that even if we are running one of the old ROM's (e.g. a donut ROM), that the apps2sd of this recovery will support it?

before your extension partition was mount /system/sd/ and backed up
when you came to restore they were put back in /system/sd/

now your extension partition is mounted /sd-ext/ and backed up
when you restore they go to /sd-ext/

when you restore a donut and reboot, the rom will mount the ext partition /system/sd
so it will be fine

hope that makes sense

999phonebug · May 16, 2010

OOOOOOH... I read that Amon wasn't going to update his Recovery and 1.6.2 wasn't compatible with sd-ext, so I went to Clockwork... Now Amon is back... Should I switch back..............................?

Firerat · May 16, 2010

999phonebug said:
OOOOOOH... I read that Amon wasn't going to update his Recovery and 1.6.2 wasn't compatible with sd-ext, so I went to Clockwork... Now Amon is back... Should I switch back..............................?

cm5 wasn't compatible with ra_1.6.2
easy to make cm5 compatible, create /system/sd

does clockwork do what you need it to do?

rgawenda · May 16, 2010

Firerat said:
maybe, but last time I looked the rootfs was ro

Last time I did, it was not. Do check in recovery:

Code:

ais@dvn3 ~ $ adb devices
List of devices attached
HT93VKF10368    recovery

ais@dvn3 ~ $ adb shell
/ # touch /a
/ # ls -l /a
-rw-rw-rw-    1 0        0               0 May 16 16:29 /a
/ # rm /a
/ # reboot
ais@dvn3 ~ $

Firerat · May 16, 2010

rgawenda said:
Last time I did, it was not. Do check in recovery:

Code:

ais@dvn3 ~ $ adb devices List of devices attached HT93VKF10368 recovery ais@dvn3 ~ $ adb shell / # touch /a / # ls -l /a -rw-rw-rw- 1 0 0 0 May 16 16:29 /a / # rm /a / # reboot ais@dvn3 ~ $

oh yeah, so it is

Code:

android@Firerat:~$ adb shell mount
[B]rootfs on / type rootfs (rw)[/B]
tmpfs on /dev type tmpfs (rw,mode=755)
devpts on /dev/pts type devpts (rw,mode=600)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
/dev/block/mtdblock4 on /cache type yaffs2 (rw,nodev,noatime,nodiratime)

rgawenda · May 16, 2010

Firerat said:
oh yeah, so it is

I do check on my servers' mount points once in a while, just in case.

zimphishmonger · May 16, 2010

Anyone else notice it doesnt say the name before you flash the .zip anymore. It just say "Are you sure you want to flash .zip, press home to continue" where it said the actual file name before.

lleong1 · May 16, 2010

Nuked Recovery....

So while I was trying to update the recovery from 1.6.2, I did something wrong after I got the low memory error and nuked my recovery. I can still boot into CM5.0.7 but I have lost my recovery.

I have been trying to figure out how to install it via fastboot but apparently I need the engineer's SPL but I am on the DangerSPL because CM5 needs that. Now I can't even get into recovery to install the Engineer's SPL.

Can anyone help me get my recovery back?

EDIT: I am on a Mac as well.

Firerat · May 16, 2010

lleong1 said:
So while I was trying to update the recovery from 1.6.2, I did something wrong after I got the low memory error and nuked my recovery. I can still boot into CM5.0.7 but I have lost my recovery.

I have been trying to figure out how to install it via fastboot but apparently I need the engineer's SPL but I am on the DangerSPL because CM5 needs that. Now I can't even get into recovery to install the Engineer's SPL.

Can anyone help me get my recovery back?

DangerSPL should have the fastboot mode you need

follow the instructions for fastboot

if you still have no luck,

read this entire thread

http://forum.cyanogenmod.com/index.php?/topic/3440-recovery-is-toasted-not-bricked-phone-thread/

philosophics · May 16, 2010

1. rename your recovery image to recovery.img (just easier to type later) and place it on the root of your sd

2. while device is off, hold camera button + power and wait till you see some android dudes on skakeboards.

3. Let it run it's check and then push the back button.

You are now in fastboot mode.

OR
2. bootup device till you get to homescreen
3. open terminal emulator
4. type

flash_image recovery recovery.img

Either way will work. But because I know nothing about mac's, I wouldn't know what command you would enter on a mac or what you would use in place of a command prompt...

rgawenda · May 16, 2010

lleong1 said:
Can anyone help me get my recovery back?
EDIT: I am on a Mac as well.

Just put it as /data/recovery.img using whatever method (adb/usb+term). You're running CM, and will flash it automagically as stated in the OP.

Firerat · May 16, 2010

philosophics said:
1. rename your recovery image to recovery.img (just easier to type later) and place it on the root of your sd

2. while device is off, hold camera button + power and wait till you see some android dudes on skakeboards.

3. Let it run it's check and then push the back button.

You are now in fastboot mode.

can't wait for the end......

Firerat · May 16, 2010

########################
edit:

http://forum.cyanogenmod.com/topic/...ot-to-recovery/page__view__findpost__p__21996

^^^^

the above link is what I now recommend

######################################
This is not the recommended way to flash 1.7.0
Personally I recommend via recovery console or fastboot
######################################
this is only needed if you can't get into recovery
or use fastboot
######################################

ok

little bit of a twist on the flash on boot method

its actually commented out in cm5's init.rc

Code:

# Never flash the recovery!
#service flash_recovery /system/etc/install-recovery.sh
#    oneshot

so, we use the 'firstboot' script

attached is
firstboot.txt

did it work?
please link in your sig
http://goo.gl/n8GE

this needs to be put on your sdcard and

Code:

cp /sdcard/firstboot.txt /data/firstboot.sh

you also need to copy the recovery image to /data/recovery.img

this is what is in the firstboot.sh file

Code:

flash_image recovery /data/recovery.img
if [ "$?" = "0" ];
[COLOR="Blue"]$? is the exit code, its 1 if it failed, 0 if it flashed ok[/COLOR]
then
[COLOR="blue"]so, if it flashed ok we delete the recovery image[/COLOR]
	rm /data/recovery.img
	echo "recovery flashed"
else
[COLOR="blue"]if it failed to flash we don't delete it[/COLOR]
	echo "recovery flash failed..."
fi

it will flash the recovery image before android starts, thus limiting the chance of hitting the low memory bug

the /system/etc/init.d/03firstboot
script is

Code:

#!/system/bin/sh
# execute any postinstall script then kill it
if [ -e /data/firstboot.sh ];
then
   log -p i -t boot "Executing firstboot.sh..";
   logwrapper /system/bin/sh /data/firstboot.sh;
   rm -f /data/firstboot.sh;
fi;

that will delete the firstboot.sh script

once you have booted, check data
ls /data/
if the flash worked then you should not see recovery.img

did it work?
please link in your sig
http://goo.gl/n8GE

Firerat · May 16, 2010

rgawenda said:
Just put it as /data/recovery.img using whatever method (adb/usb+term). You're running CM, and will flash it automagically as stated in the OP.

check the init.rc, it wont

[Recovery] [15-May-2010] RA-dream-v1.7.0 (also for the Rogers Dream)

Senior Member

Retired Senior Recognized Developer

Retired Senior Recognized Developer

Senior Member

Senior Member

Senior Member

Senior Member

999phonebug

Guest

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Attachments

Senior Member

Similar threads

Top Liked Posts