yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] themapleboy:
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
[G1 Android Development] qwerty3656:
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?
[G1 Android Development] Firerat:
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
[G1 Android Development] :
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..............................?
[G1 Android Development] Firerat:
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?
[G1 Android Development] rgawenda:
Last time I did, it was not. Do check in recovery:

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 ~ $
[G1 Android Development] Firerat:
oh yeah, so it is

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)
[G1 Android Development] rgawenda:
I do check on my servers' mount points once in a while, just in case.
[G1 Android Development] zimphishmonger:
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.
[G1 Android Development] lleong1:
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.
[G1 Android Development] Firerat:
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/
[G1 Android Development] philosophics:
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

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...
[G1 Android Development] rgawenda:
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.
[G1 Android Development] Firerat:
can't wait for the end......
[G1 Android Development] Firerat:
########################

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

# 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

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

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

#!/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
[G1 Android Development] Firerat:
check the init.rc, it wont
[G1 Android Development] lleong1:
Followed @firerat's instructions and it worked! Thanks firerat!
[G1 Android Development] BigWorldJust:
Aight which one of these do I download, lol? I am running Cyanogen Test 5 and I have G1..
[G1 Android Development] jjq13:
Hey guys I flash the recovery and I too got the error memory. What I did was run the script of [PATCH] Firerat 'all in one' patch file. I run the "swap" script, reboot and then flash the RA-dream-v1.7.0.img. This was the only way I got it to work.
[G1 Android Development] Firerat:
I doubt swap was the fix, plenty use swap and have the problem

*don't* use flash_image in cm5

do it in recovery

If you are reading this after messing things up

check 5 posts back, or use fastboot
[G1 Android Development] obiwanbartek:
I have a question. Is the old backup method (with /system/sd) completely deleted, or the new (/sd-ext) is just added (without deleting the old one)? Other worlds can I use 1.7.0 backup option in CM 4.2.15.1?
[G1 Android Development] Firerat:
yes

and /system/sd isn't deleted ( its on the /system fs )

instead it is mounted /sd-ext

everything will be fine
[G1 Android Development] obiwanbartek:
Hmm... So if it is just a matter of mounting point in actually booted system, why 1.6.2 isn't compatible with new Apps2SD? (it should be, as ext partition used by new A2SD is the same as used in old A2SD, just mounted in different place in CM5, and 1.6.2 still has access to this partition)? I don't get it :/
[G1 Android Development] Firerat:
it is compatible, but cm5 doesn't have /system/sd mount point

I have made many posts in plenty of places on the subject
[G1 Android Development] dumfuq:
because if a script mounts /system in 1.6.2, then the placeholder/system/sd is no longer there to mount your ext partition. This can cause mounting the ext to fail whenever system is mounted.
[G1 Android Development] jjq13:
Ok I understand but this is how I got it to work. I am also running Cyan5 test5. Well this is how I got it to work.
[G1 Android Development] Firerat:
if you want/need to flash ra1.7.0 then you should do it via the recovery console

or fastboot

if you have already tried with the terminal method in CM5 and can't get to recovery, then use the firstboot script I made a few posts back, or use fastboot

anyway, this killing recovery via cm5 thing does seem to be common, so

I would welcome feedback on the script above working

you can link to it ( in sig so it is seen ;) )

with

http://goo.gl/n8GE

I will add to that page to detail that it is only needed if already in the broken recovery loop
[G1 Android Development] Ace42:
Surprised people are losing access to recovery, I upgraded when I tried T5...But I'm no longer using T5(Testing purposes only), I only like sense roms daily or SuperD.
[G1 Android Development] Firerat:
have to admit I have missed sense

( use to hate it as it was sooooo slow, cachehack made it useable for me )

I finally got round to sorting out my 32bit thing

( for swype )

I can't make any sense of it :( ( smali that is, I've apktooled some stuff including swype and some framework.jars )

I'm hoping it will 'click' and I can have a stab at fixing the slide

but very early days on that.. java is alien to me, smali well more so..

but at least I can now make a 3D app get 3D perms if it doesn't have it already ;)
[G1 Android Development] AnGeL_WiT_SiNs:
i tried flashing this and it game me the out of memory..now i cant boot into recovery..im trying to flash 1.6.2 but its still saying low memory now i cant access recovery at all...can some one help me
[G1 Android Development] Firerat:
Join Date: Aug 2009

Posts: 117

^^^^

not learnt to read a few pages back yet?

I hope it helps, please let us know if it does
[G1 Android Development] Firerat:
and your sig is blue but no links?
[G1 Android Development] s15274n:
firerat, once I realize I was supposed to do this in terminal, it worked great.

I will update my sig soon with your link. THanks for helping the community so much.
[G1 Android Development] AnGeL_WiT_SiNs:
my appologies....well i got it to work..and yes my bad in not reading a couple of pages back..just got cought in the moment on flashing with out reading a couple of posts then when i flashed it and it didnt work...again didnt think on reading a couple of posts..

well the way i got it to work was all i did was typed the commands in terminal like 4 times till it finally flashed..i read it on a post 5 pages back..lol KEY WORD ANGEL....READDDD!!!! and will change my color in my sig...THANKs...by the way..does the recovery come in blue?

EDIT.. Nevermind..found the link in the first post for the cyan recovery
[G1 Android Development] master.peterm:
it took me a while to get it to work without all the memory errors, (didn't work with copying to /data on CM 5.07 Test 5 or through terminal). But when i moved it to /data then rebooted then went to the terminal and wrote everything except for #mount -a it worked like a charm ;)
[G1 Android Development] Amon_RA:
Updated the Install guide in the first post :

removed the via a simple reboot method, it's not implemented anymore in CM roms.

removed the use of "su".

removed "mount -a" where it's not needed.

added a warning for users trying to use the terminal app in CM5.0.7 (will remove it as soon as it's fixed in CM5.0.x).
[G1 Android Development] OFinch:
I had the same problem as the guy a couple post above. error saying no memory.. reboot to no recovery, thought I was gonna have to go recovery'less lol. But kept trying in terminal and it works perfect. Thanx man, keep up the great work.. The cyan version looks very nice with the colors. again thank you for your hard work
[G1 Android Development] fakecaker:
google branded, but H

Hi,

i have a 32b magic, wich is google branded.

i thought i should flash the G version (like i did before i sent it for repair), but when i did, it wouldn't start up (teh recovery):confused:

later i decided to flash the H version. in some way: It worked :eek:

The recovery screen now sais: Build : RA-sapphire-v1.7.0H !!!

What's going on ? :P
[G1 Android Development] Firerat:
no idea

perhaps you should post in the sapphire thread and not the dream thread
[G1 Android Development] timeline62x:
flashed it

ok so i flashed it thru fastboot and it said okay twice like it should then when ill try to get to recovery on my fone it will just stay on the first splash screen
[G1 Android Development] TCDroid:
New recovery images won't flash

I've had 1.5.2 for awhile and i'm just now getting around to flash v1.6.2. the problem is that I put it on my sdcard and tried to flash via console Entered everything correctly. It says flash was successful but after a reboot my recovery image is still v1.5.2. i tried doing this via console and the terminal any ideas? because at this point i haven't a clue. BTW i did have this same issue when coming from v1.3 to 1.5.2 i ended up unrooting and rerooting to get it on there. I just don't want to have to go through that whole process every time there's an image update. Thanks for any advice you have. OH i forgot i'm running HTC clays superbad J5 basically cm-5.0.7 test5 , latest radio, 4gb cl6 ext3/swap on G1

This is about the 2 or 3rd time i asked this last time was back on page 148 or 147. So some type of help would be greatly appreciated. A new bit of info is that i downloaded Rom manager and was able to flash the clockwork recovery via the app but when i tried to use it to flash 1.6.2 after a reboot i was still on clockwork. and yes i have downloaded another 1.6.2 recovery image just to make sure i'll try 1.7.0 as well and see what happens..
[G1 Android Development] Erikbronx:
Boot holding the camer button and power, when u see the androids on skate board press send to reset. Let me know if that helped... off the top of my head.
[G1 Android Development] darksideofdamoon:
Amon-Ra, whaddup! XDA, whaddup! 1st and foremost, Amon-Ra, thank you for the cool ass image recovery you've given us. It is a life saver for those who are on the go and don't always have access to a pc, and for those, who like me, can't seem to figure adb out... We appreciate your time and effort :.)

Here's my issue... Since v1.6.2, I've had a hard time flashing the image recoveries, via the console and the terminal. I would get a msg stating that the directory could not be found. I never got to try the Care Bears version :.( I successfully flashed v.1.7.0 via the terminal but then I noticed the Cyan themed version... Flashing that via console or the terminal was unsuccessful... So I downgraded to v1.6.2 and tried to get v.1.7.0 back. Utter fail! When i view the files (v1.6.2, v1.7.0) on my pc, I see sheets of paper with symbols on them. When I view the files on my sdcard (via Astro) I see blank sheets of paper with no symbols on them... Any ideas? Anybody...
[G1 Android Development] nocute8072:
Thanks for your work.
[G1 Android Development] DesselNailo:
What is the difference between the one with O and the one with OR?

(Sorry I'm a dumb ass lol, I skipped over that part.)
[G1 Android Development] fleity:
this "R" ?
[G1 Android Development] pelo88:
g1 stuck at g1 screen

I flashed in recovery from 1.6.2 to 1.7.0 rebooted fine. Then went to recovery to see 1.7.0 which was there. Chose reboot on the screen and bang. No more phone. Thanks a lot.

I tried reflashing CM 5.0.7t5 to no avail. How is it that I can overwrite the boot.img that way and still not get in?! How the fuq did flashing recovery fuqup the boot that badly?

I used adb to reflash 1.7.0 to recovery to no avail and I reflashed 1.6.2 successfully but the damage has been done. No more phone for me at all. Can't get past the G1 screen but fastboot and recovery (now 1.6.2) still works.

What the hell am I to do now?

UPDATE: had to wipe (wiped ext as well since it was only a couple apps, lovin th new apps2sd). fixed now, but why did this take down my rom? I've no clue.
[G1 Android Development] LordPhoenixSalvation:
flashing now thanks Amon_RA
[G1 Android Development] LordPhoenixSalvation:
can anyone please explain fastboot to me please for my second g1 which is on cm 5.0.7 t5

i use android commaner for adb do i have to learn how to use the adb console?
[G1 Android Development] cdw9800:
im trying to falsh my recovery via fastboot and it keeps telling me cant locate the file where do i need to put it im confused.
[G1 Android Development] TeeJay3800:
The root of your SD.
[G1 Android Development] cdw9800:
thanks for the quick reply i have done that and still get the error tried flashing via console adb and no luck first time i ran into this issues trying to upgrade from 1.6.2
[G1 Android Development] Amon_RA:
When you use fastboot the recovery image needs to be in the same directory on your pc as where you launch the fastboot command. It doesn't need to be on the sdcard...

The issues you have are not related to upgrading from 1.6.2 , they are related to the fact that you are using a CM test build , right?
[G1 Android Development] themapleboy:
soo i just came hee to download a updated backup of the recovery img (i forgot to keep it after i flashed it) and i saw you added a waring to the terminal method.

i have cyanogen 5.0.7 i flashed it via terminal w/o an issue should i be worried?
[G1 Android Development] Amon_RA:
No, you shouldn't :-)
[G1 Android Development] psjames:
Can't restore older BART Backups

I am using CM5.0.7 T5 and have installed RA-dream-v1.7.0. I am trying to go back to the back up CM4.2.15.1 and get the following:

Checking for cache partition backup.....

cache-backup not fount for ROM cm4.2.15.1.

press any key to continue . . .

then just goes back to Utilities.

Is there a way to go back to cm4.2.15.1 using BART 1.3.1 Restore in the utility?
[G1 Android Development] Firerat:
http://xdaforums.com/showthread.php?t=562292
[G1 Android Development] cdw9800:
yes i am and i have it there also should i flash to a different rom than flash back?
[G1 Android Development] Amon_RA:
No, you can use fastboot or you can try this method :

From terminal :

This will likely be unsuccessful, now trackball up to repeat the last line and hit enter, after several attempts it worked for two separate people.
[G1 Android Development] cdw9800:
ok ill give it a try once i get the phone back im doing it for a friend
[G1 Android Development] cihan978:
Video

someone made a vid about this

check youtube and search it
[G1 Android Development] cdw9800:
wow it worked on the first attempt thanks
[G1 Android Development] Mardenator:
one question: what's the difference between

recovery-RA-dream-v1.7.0.img and

recovery-RA-dream-v1.7.0R.img ??

what's the difference between the "O" and "OR"?
[G1 Android Development] :
1.7.0 is the version.

the 1.7.0R is for rogers dream.
[G1 Android Development] Mardenator:
wow.. i am such an idiot.. it even explains it right above the download links.. thanks!
[G1 Android Development] :
You're welcome. =]
[G1 Android Development] jakijal:
alright, i have a quick question...

i did notice a while back that the new version, 1.7.0 was meant for cyan's cm5 roms, and that it really wouldnt work for the donut roms.

its not on the first post anymore so wondering if this new 1.7 version will now work correctly with the donut roms also.
[G1 Android Development] xaueious:
Think I noticed a bug on my Amon_RA 1.7R Recovery

I select Go to console, and back using 'u', followed by 'r' to return to the menu, and then Go to console again, it does not reset the terminal and presents me with console that forces me to either pull my battery, 3 finger salute or adb shell reboot recovery.
[G1 Android Development] onire:
And what's the difference between

recovery-RA-dream-v1.7.0.img and

recovery-RA-dream-v1.7.0-cyan.img ??
[G1 Android Development] michel-xda:
Obviously the color. What else? :D
[G1 Android Development] Firerat:
It should be fine

All that is happening is anythingin /sd-ext is getting backed up

The backup 'script' is correctly striping the leading path ( and has been for some time )

So, as long as your ext partition can mount then it will be backed up and restored correctly

From what I have read there _might_ be a problem with restore not working if no cache.img exists, but I havn't looked into it

Would be quite easy to 'patch' (just yaffs up a fake img and inject its md5sum, or mod the code to test for cache existing )
[G1 Android Development] dcowboys2184:
wont boot into recovery .. i know i didnt do anything wrong !! but phone boots right up
[G1 Android Development] hollywoodxxx:
I do not understand the instructions firerat, someone could explain simply please?

sorry but i'm a noob
[G1 Android Development] djm25:
three finger salut i like that one ...... i usualy just in put this code when im done with the console reboot recovery it takes like 4-5 seconds longer but its worth it just to be on the safe side
[G1 Android Development] xiaotao1015:
i can't enter in the recovery after flash image, but i can enter in the andriod system, i don't know how to solve it.

my system is cm 5.0.7 stable.
[G1 Android Development] Firerat:
I'm guessing you have tried to flash ra_1.7.0 from CM5

read the thread, there are a number of options
[G1 Android Development] fermunky:
OK, needing some help.

I went to CM5.0.7. I then tried screwing with ClockworkMod Recovery. Installed his app from market, then told it to install his recovery. While trying to boot to recovery, I got the G1 screen, then nothing. Yanked battery then rebooted back normally.

Removed Clockworkmod app, downloaded RA 1.7.0, and of course didn't notice the warning, but I didn't try the terminal method yet. I first used Droid Explorer to flash the recovery image. Tried rebooting to recovery, and now it hangs at the G1 screen. yanked battery, rebooted...

Tried the terminal method of flashing, same as Droid Explorer.

Then I followed Firerat's method: I put firstboot.sh and recovery.img into the /data/ folder, rebooted, checked /data/ and both files were gone. Tried rebooting into recovery, and hanging at the G1 screen. Yanked battery, rebooted back into the phone normally.

This is where I currently sit. I do not know how to do fastboot, but will it even be worth the try?
[G1 Android Development] hollywoodxxx:
i'm in the same situation... need help
[G1 Android Development] fermunky:
UPDATE: Fixed mine

I think I was having issues with my work PC working with fastboot specifically. I got home, removed all USB drivers, removed Droid Explorer, and my old folder for the Android SDK.

Downloaded new SDK, had it install the latest USB driver. Confirmed ADB worked, booted my phone into fastboot mode, and then flashed it via fast boot, and I now have RA 1.7.0 recovery :)

For those having USB issues, it's gonna be tricky. With the phone plugged in, you have to find the either old working driver in device manager and remove it, or remove the failed one (with the yellow "!" on it). I probably didn't need to do all that, but not having fastboot detecting my phone on my work PC drove me bonkers. Worked fine from another PC though.

C:\>fastboot erase recovery
erasing 'recovery'... OKAY [ 0.057s]
finished. total time: 0.058s

C:\>fastboot flash recovery c:\recovery.img
sending 'recovery' (4602 KB)... OKAY [ 2.421s]
writing 'recovery'... OKAY [ 2.373s]
finished. total time: 4.796s
[G1 Android Development] mark manning:
So i have a stock spl and cant seem to flash this recovery, how to I get an engineering spl so i can fastboot flash this.

Or better yet flash this with the stock spl
[G1 Android Development] LucidREM:
Recovery

have you tried first copying to /data/recovery.img? i have always updated my recovery via my script file which downloads to the sdcard, copies to /data/recovery.img and then flashes with this line:

# flash_image recovery /data/recovery.img

i had experienced strange errors trying to flash directly from the sdcard .. the script is being modified to accommodate cyan's work:

# lucid -rc -ra

this should always download the latest recovery .. again .. it is a work in progress but will be released soon
[G1 Android Development] ZilverZurfarn:
From the changelog (first post):
[G1 Android Development] crxforya:
Mine says fail remote not allow. How do i get it to allow remote comand?