yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] mwade12001:
I'm still on the old recovery but on CM 5.07 so looking to flash the new recovery. I have a UK Voda magic 32b so should I use the dream/g1 image or the magic/mytouch image? I know how stupid that seems, but it's the dream/g1 roms which work on a uk Voda magic as it has a 32b board.
[G1 Android Development] sturmeh:
Just a note guys, do not flash from terminal using su, the flashing will fail and your recovery will no longer start.

You should follow the fastboot instructions.

EDIT: This is concerning CM 5.0.7 users with Danger SPL.
[G1 Android Development] boldfilter:
New recovery ahhh
[G1 Android Development] Amon_RA:
Just wait until I update the Magic recovery.
[G1 Android Development] mwade12001:
OK thanks for the clarification. Looking forward to the updated version for the Magic.
[G1 Android Development] bosna110:
hey ppl, just needing some help putting this new recovery image on my g1, i know there are instructions on the main page, but i am so bad at understanding the steps that i should slap my self silly. if someone can help me out id appreciate it. Send me a personal message if you can help. Thanks
[G1 Android Development] Ace42:
What part do you need help with?
[G1 Android Development] bosna110:
ive got the 1.6.2 as most people have for the recovery image. i need help downloading and installing/flashing (whatever you wanna call it) on my g1. so i kind of need click by click instructions.
[G1 Android Development] fox12345:
any update for mt3g .lol
[G1 Android Development] borwin:
I've got out of memory error too, but RA1.7 is there. No bear but is there:p
[G1 Android Development] Ace42:
All you need to do is

1)DL from computer(dont DL from phone, high chance of corruption)

2)connect usb, but first put phone into recovery mode

3)now enable usb

4)copy over the new image

5)disconnect usb

6)goto console:type

mount -a

flash_image recovery /sdcard/nameofrecovery.img

reboot(type it)

then hold the house & power buttons
[G1 Android Development] bosna110:
okay but which one do i download tho because there are like 4 of them to choose from.
[G1 Android Development] Ace42:
1)Which phone do you have?

2) second set if just a cyan colored ver and first set is green ver
[G1 Android Development] bosna110:
how do i find out? if you mean 32a or 32b i have 32b. is that what you mean?
[G1 Android Development] Ace42:
Then you can pick

recovery-RA-dream-v1.7.0.img

Or

recovery-RA-dream-v1.7.0-cyan.img
[G1 Android Development] bosna110:
okay. check back in like 3 minutes. ill let you know when i have finished downloading for further instructions
[G1 Android Development] bosna110:
okay ive picked the recovery-RA-dream-v1.7.0.img and its done downloading

now what? mount phone and turn it off and put it in recov mode?
[G1 Android Development] Ace42:
Mount while in recovery then copy the file
[G1 Android Development] bosna110:
wtf? so i get it in recovery mode and toggle usb connect?
[G1 Android Development] bosna110:
okay i first rebooted my phone in recovery mode, and then i hit the usb-ms toggle and then i went back to my laptop and i put the new recovery img to root of the phone and then now what
[G1 Android Development] Ace42:
safely eject the usb from your laptop, then press home btton on phone

then goto console
[G1 Android Development] bosna110:
okay give me a hot sec ill repost when thats completed
[G1 Android Development] bosna110:
alrighty, sorry for the delay ace, im writing down some notes to help me remember in the near future when new recovery is released so i wouldnt pester alot about it unless something will change. so yeh now im console now what are the steps for me now
[G1 Android Development] Ace42:
Press[Enter]

mount -a

flash_image recovery /sdcard/recovery-RA-dream-v1.7.0.img

reboot

once it reboots hold the Home & Power button so it will go back to recovery(hold once you see the G1" screen )
[G1 Android Development] MotoMudder77:
MD5sum is good, this error still mean bad d/l?

mtd: not writing bad block at 0x001e0000
[G1 Android Development] bosna110:
errors are occuring. i went into console, and i hit enter as you said and i did the mount -a and then pressed enter and its saying something like

mount -a ( what i typed in )

mount: mounting /dev/block/mcblk0p2 on /system/sd failed: no such file or directory

????? what am i doing wrong? am i suppost to have kept the usb plugged in?
[G1 Android Development] Ace42:
Did you remove the usb from the computer,with the USB icon to safely remove(on comp)?

Then you can press the home bttn on the phone.But since it says that type reboot recovery[press enter]
[G1 Android Development] Blueoval24:
I thought the first post was pretty good at explaining what to do? There are like 4 different methods for installing. Choose what SOUNDS easiest to you...:confused:
[G1 Android Development] bosna110:
yeh i felt pretty dumb of doing that so yeh i have removed it thinking i wouldnt need it anymoe. so i have connected my usb again and typed in reboot recovery and now i am going back into console
[G1 Android Development] xjjjay:
Not quite... I'm getting read/write errors left and right. Never used fastboot before, guess I'll give it a go when I've got time.
[G1 Android Development] bosna110:
for some reason im still getting the same error msg... ive got the cord in the phone and other end in the laptop and i even rebooted in recovery.. this is getting a lil agrivatting
[G1 Android Development] Ace42:
Take the sd out and then reinsert it.
[G1 Android Development] bosna110:
kk check back in 1 min
[G1 Android Development] bosna110:
same error with sd removed and removed and reboot recovery and then console with enter first then i type in mount -a then it gives me the msg... im startin to think the file never made it in the sd lemme check.
[G1 Android Development] xjjjay:
Look more closely at the first post. You need to use fastboot.
[G1 Android Development] bosna110:
yepp the file is still on the phone and now i dont know what the hell could be going on?
[G1 Android Development] bosna110:
well im tryen to follow ace's instructions... whatever he tells me to do i do because i think he has enough experience
[G1 Android Development] Ace42:
I used console & adb and both are fine, flashed cyan's newest test rom and used bart.
[G1 Android Development] xjjjay:
mmm I got out of memory errors left and right in both console and adb. Wonder what the difference can be...
[G1 Android Development] Ace42:
Well This is my setup:

New radio

Danger SPL

4GB SD:EXT3-256MB / 160swap

Tmo G1

I always use console though, only use fastboot to change splash screen
[G1 Android Development] rynosaur:
great!

Thank you very much Amon!! Your work is the one piece of code I rely on *every* day regardless of theme, ROM, mods, etc. You are integral to the Android development community! :D
[G1 Android Development] TeeJay3800:
I've always updated my recovery from either the console in my current recovery or via Terminal Emulator...
[G1 Android Development] rynosaur:
Apparently, someone has forgotten how they rooted their phone to begin with ;)
[G1 Android Development] TeeJay3800:
I'm not following you. I've never used ADB/fastboot. In fact, I still have the original SPL so it's not even an option.
[G1 Android Development] lowlife546:
someone else had mentioned this too but using terminal, got the memory error msg. tried a few more times and about the 5th time it worked
[G1 Android Development] Reyland:
just wondering if is going to be a version of this for m3g users??
[G1 Android Development] roccoadam32:
copy to sdcard rename to RA-dream-v1.7.0

go into console type su then enter

then type $su

flash image recovery /sdcard/RA-dream-v1.7.0.img

then your done reboot phone and hold home new recovery

32b g1 with danger spl no issues flashing!
[G1 Android Development] Rrod15:
Help i have a real big problem i tried flashing through terminal and got the no space error and now i cant even get into the recovery menu!!!
[G1 Android Development] Rrod15:
Is there any way i can wipe the recovery and flash the new one without having to do the whole re-rooting process over again???
[G1 Android Development] b0ricuaguerrero:
Please use the "via fastboot" method if you have "out of memory" issues.

via a simple reboot -> Requires Cyanogen's ROM (other ROMs will probably work too, check init.rc where to put the recovery.img)

Rename recovery-RA-dream-v1.7.0.img to recovery.img
Copy recovery.img to /data
Reboot fully (the recovery will be flashed automatically)
Reboot to recovery
[G1 Android Development] Rrod15:
what would i use to copy it to that folder?
[G1 Android Development] b0ricuaguerrero:
i used root explorer. make sure you remount as r/w
[G1 Android Development] Rrod15:
Thank u i will try it right now
[G1 Android Development] Rrod15:
do i mount system or mount data i am using the SUFBS file system
[G1 Android Development] b0ricuaguerrero:
paste it to the root of the data folder.
[G1 Android Development] Rrod15:
Alright i pasted ot to the root of the data folder rebooted and then tried to reboot to recovery after and it still just hangs at the g1 screen
[G1 Android Development] xjjjay:
Same, fastboot is the only way to do it. Can somebody walk me through this? I've never had to use fastboot before. G1 Danger latest radio CM5
[G1 Android Development] TeeJay3800:
No it's not. You can easily upgrade your recovery using the other methods. I've always upgraded mine through Terminal. So have others...
[G1 Android Development] smithfb3:
Deleting Old Bart And Nand backups

Is there a way to delete the old Bart and Nand backups. When I seem to have a dozen back-ups that I no longer need.

I tried searching through the SD drive but I was unable to figure out where they were hiding. The only file in the Bart folder was my last back-up.

Sorry for the Noob question. I tried doing a search through the forum but it gave me pages of post that don't help.
[G1 Android Development] lowlife546:
i think he meant most reliable way for this particular update since so many are having problems going through terminal. but yes not the only way since me and others were able to. it took me about 5 times though until i finally got no errors and it flashed and i know reading back a few pages other ppl experienced the same.
[G1 Android Development] cidica:
Just did mine in term. got the out of memory part at first rebooted the g1 and did it again rebooted to recovery and it was fine. All Systems Go.
[G1 Android Development] lowlife546:
i know nandroids are stored in the nandroid folder on the root of ur sd. the bdes or bds folders are ur backups you can either delete or move to ur computer for possible future use. not sure about bart,
[G1 Android Development] tissimo:
Flashed via terminal in CM5.0.7 Test 5, no issues.
[G1 Android Development] smithfb3:
Thank you, now I feel so stupid. I looked for days and never considered nanoid.

Thanks again
[G1 Android Development] Jdom58:
This worked like a charm for me, no issues at all:

copy to sdcard rename to RA-dream-v1.7.0

go into terminal

$ su

# flash_image recovery /sdcard/RA-dream-v1.7.0.img (enter)

# reboot (enter) and press home to get to the new recovery

32b g1 with danger spl no issues flashing!
[G1 Android Development] Firerat:
since the out of memory issue is due to a bug in CM5's kernel, that will likely fail and kill the current recovery, then you will only be able to flash via fastboot

for the best chance flash in recovery

boot to recovery

go to console

mount /sdcard
flash_image recovery /sdcard/recovery-RA-dream-v1.7.0.img

save yourself a little typing

mount /sdc<tab>
fla<tab> recovery /sdc<tab>rec<tab>

where <tab> is <alt> then q

do <tab><tab> if nothing 'expanded', a double tab will show you options ;)

edit: ahh, the kernel bug is only when memory is low, the recovery flash in the init.rc happens before Android eats up memory, so that will be fine

still, the above is probably the easiest if you haven't got fastboot

Also any reason why an update.zip package would not work?
[G1 Android Development] timeline62x:
HELP

can someone plz tell me how to use fastboot am i missing something or wat? ive googled everything this is so frustrating
[G1 Android Development] Blackman778g:
Ummmmmmm... ok. I am confused. Old App2Sd method?. What does that mean?

"out of memory"? Im on superbad 1.2.4 and how do I know that if I flash this I will have out of space issues?

Sorry, but I kind of lost my experience from flashing recoveries.. 1.5.2 and 1.6.2 were so easy but these have a few questionable remarks..

edit: what does the download link with cyan in it do?
[G1 Android Development] Firerat:
http://www.google.com/cse?cx=partner-pub-2900107662879704:fs7umqefhnf&ie=ISO-8859-1&q=fastboot

once you have fastboot for your OS installed

fastboot flash recovery <full path and file name of recovery.img>
[G1 Android Development] philosophics:
While your device is off, hold the camera+power button.

You'll a white screen with a couple android dudes on skateboards.

Let it do its thing on checking for a dreimg.nbh (don't have it on your card) then push back.

You'll be in fastboot mode.

Open a command prompt and type

Hope this helps...

-------------------------------------

Sent via the XDA Tapatalk App
[G1 Android Development] Jdom58:
Firerat, what do you think could be causing the problems for some folks here?

I can confirm this method worked like a charm for me and it seems simple enough;

copy to sdcard rename to RA-dream-v1.7.0

go into terminal

$ su

# flash_image recovery /sdcard/RA-dream-v1.7.0.img (enter)

# reboot (enter) and press home to get to the new recovery

so why wouldn't it be working for others? just picking your brain :D
[G1 Android Development] Firerat:
the only real difference as far as recovery cares is the mount point

cm5 it got moved to /sd-ext instead of /system/sd

( but it was very simple to fix on cm5, just make /system/sd folder !! )

the new recovery now has /sd-ext, its compatible with both old and new roms

the problems people are having flashing this is due to a bug in cm5's current kernel

flashing via recovery console will have no such issue

if your not using cachehack, or cm5 then you don't *really* need it

but, you should be able to flash it with no problems anyway ( since your not using the kernel with the low memory bug )

Oh, hold on, superbad 1.2.4 is just a themed cm5

see my above posts ref flashing via recovery console
[G1 Android Development] overground:
I've uploaded a copy to my 4shared. You can get it HERE. XDA seems to be having file upload problems atm.
[G1 Android Development] beatle7777777:
Thanks alot the original link wasn't working
[G1 Android Development] steven178s:
All i can say is BEAUTIFUL its perfect
[G1 Android Development] rubbachicken:
awesome

this was awesome loved cyanogens till i tried this same but twice the options partition auto etc it was great; anyone having trouble installing all i did was copy it to the sd card; reboot into cyano recovery 1.4 and go to it's console type in mount -a recieved 2 errors about no such file or directory and flash_image recovery /sdcard/whatevertehfilenamewas (case sensative); rebooted and it was done....
[G1 Android Development] fairymaru:
nice job done!
[G1 Android Development] andjohn:
Works Great

Thanks a lot. Saves me a couple seconds each time I do something in recovery :)

No more ums_enable...
[G1 Android Development] TheUriel:
Is any 1 having the same problem as me ? Im trying to do this with Terminal on MyTouch and i cant type numbers.

Forget it , i did it.
[G1 Android Development] ccriffman:
RA- You are THE MAN! Just flashed your recovery img from terminal and re-booted into recovery, and OMG- Awesome- Chris
[G1 Android Development] kyleds:
Is there a way to run apps from sd? I tried doing the martinfink sdplit but would get an error when I try to do the last part. The one that has the 14500M -nc @ the end. Got a 16gb card. When I look at settings it says I have a secondary partition of 500m, but it keeps downloading to phone and not 2nd partition... my computer mb fried... so don't have one to download any partition program. The apps to sd doesn't do anything for me
[G1 Android Development] bkmo:
I took a look at the script and it moves the apps and dalvik from /data to /system/sd. This is all well and good, but without symlinks and/or bind mounts the system will still look to /data for apps and dalvik. Seems useless to me unless the rom supports it. Cyanogen already supports it and the apps and dalvik get moved automatically if the ext partition exists.
[G1 Android Development] dta1974:
Woww...this is an awesome updrade,thank you so much.Easy to use and multitask.

Thanks again.
[G1 Android Development] g1junky:
go to the option in this recovery that says part sd ext2+lswap+fat32
[G1 Android Development] sagementor:
I just typed "switchrom" without the "sh", it works.
[G1 Android Development] sagementor:
I think the recovery img works in any versions of Dream and Magic. However you have to be careful if you are going to flash the SPL. It may brick your phone if you do it wrongly. Some ROMs required Haykuro's SPL.
[G1 Android Development] sagementor:
No need to remove the old recovery img. The new image automatically replaces the old one.
[G1 Android Development] jerzy448:
after i type su then flash_image recovery /sdcard/recovery-RA-dream-v1.2.2.img

i get usage: flash_image [-d] partition file.img

options:

-d deletethe image after sucessful flash

what do i do from here
[G1 Android Development] dbarrett480:
I keep getting "flash_image: not found" in terminal. Does anyone know what would be causing that. I would just do it through adb but I have followed every tutorial out there and have never been able to get adb to work. so my only choice is terminal.

Nevermind, just kept trying and eventually it flashed
[G1 Android Development] barracudax:
ah so if i just flash the recovery img only just for get rooted

then

change to the rom that suite 32A it will be ok .

i just want to change the language 1st

coz all of this stuff in chineses

btw is this last update 1.2.2 are for both 32A n 32B ?

so we can use this without any wory bout wrong type of recovery img ?

tq b4 n after
[G1 Android Development] ahijada:
I don't know if its just me experiencing this, but I cannot seem to load MEGAUPLOAD or RAPIDSHARE when I click on the links posted in the 1st page and 2nd page.

If it does load, it takes forever, (45mins) to load and then won't download the file.

I've tried this with my home internet (wifi) and work.. still no go.

Has anyone had this problem? Are there other links of the recovery image someone can give me?
[G1 Android Development] the_faith01:
i can't access rapidshare at university

could someone email it to: darren.emedo@gmail.com?
[G1 Android Development] Firerat:
you happen to have enough memory

which is why it appears to be random

do you use swap?

do you use a memory manager?

are you using a none standard kernel?

many factors , but it may have been pure luck
[G1 Android Development] saprano614:
what is the difference between the cyan one and the regular one

sorry i found the answer.
[G1 Android Development] Jdom58:
Maybe so look at my sig, it's exactly what I'm running. With CM5 and your patch131 I'm showing 73.27MB available internal memory and I have 55 apps installed (to sd of course). Just curious why others would be running low on memory since I would guess most of them would have installed your patch also. Also I don't use swap or compcache
[G1 Android Development] lowlife546:
look at the 2 screen shots in the op. the left is regular and the right is the cyanogen
[G1 Android Development] timeline62x:
hey firerat

i did all that stuff u said but its says cannot load the img like is it C:/Users/MyName/ etc?
[G1 Android Development] Firerat:
I have no idea where you put it

find it and move it somewhere easy

like

C:/recovery.img
[G1 Android Development] Firerat:
in that case I think you were just lucky

some are lucky the fist time, others 4th or 5th time

do it in recovery console, ( after mount -a ) and it should work first time
[G1 Android Development] TeeJay3800:
So that method avoids any errors caused by a lack of available memory, correct? I ask because I do not use apps2sd and only have ~12MB of internal memory free.
[G1 Android Development] Firerat:
yes

but the problem is free RAM, not internal memory

its an issue with the kernel in CM5, the kernel in recovery is fine

use fastboot or recovery console as described above
[G1 Android Development] Jdom58:
He he that was the ironic thing, I tried via recovery comsonle first and I couldn't get mount -a to take
[G1 Android Development] Firerat:
could have been a /system/sd not existing, but it should have still mounted /sdcard/
[G1 Android Development] TheDeadWalk:
ive tried using Console. Terminal Emulator. and fastbood and ADB and i cannot get 1.7.0 running. just hangs on G1 screen.

doing everything to a T.

any ideas?

dream. haykuro spl. cyan test 5.

EDIT:

FOR THOSE HAVING PROBLEMS INSTALLING, INSTALL DROID EXPLORER AND USE THE RECOVERY FLASHER FUNCTION.

AFTER HOURS OF FRUSTRATION, IT GOT THE JOB DONE IN SECONDS!
[G1 Android Development] TeeJay3800:
I ended up upgrading through Terminal, and it worked fine.

Interesting thing though. In both recovery and Terminal, I got the same error when typing 'mount -a' : "mounting /dev/block/mmcblk0p1 on /sdcard failed: No such file or directory". I then flashed the recovery despite the error and it went fine.
[G1 Android Development] Firerat:
:eek:

how can you flash from the sdcard if it failed to mount /sdcard :confused:
[G1 Android Development] TeeJay3800:
I have no idea, but the exact same thing happened when upgrading to RA 1.6.2 as well. I type mount -a, get the error, then proceed to enter flash_image... and it flashes the recovery successfully. :confused:
[G1 Android Development] Lieu10ant:
same with me.... i didn't type the whole "mount /dev/block/mmcblk0p1" thingy... but i typed the other thing that makes you mount it. but it failed and i continued on typing the rest of the commands and i didn't get any errors. and then when i restarted my phone, to my surprise i had updated it.
[G1 Android Development] TeeJay3800:
Good to know I'm not the only one! :eek:
[G1 Android Development] oreoOozZz:
x2. worked like a charm for me.
[G1 Android Development] jkoenig00:
same here got memory error then rebooted phone into fastboot and couldn't figure out what to do from there so gave up then re tried it in terminal and it worked
[G1 Android Development] rgawenda:
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).
[G1 Android Development] Firerat:
maybe, but last time I looked the rootfs was ro
[G1 Android Development] Amon_RA:
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?
[G1 Android Development] Amon_RA:
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.
[G1 Android Development] jkoenig00:
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.