yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] garlonnl:
Error writing rocovery on CM6RC2

I tried to flash amon ra recovery 1.7.0 while on cyanogenmod CM6 RC2 but when i tried to flash iall i got where a lot of errors and after a reboot i couldn't get into my recovery nor cyanogenmod. I do have fastboot but no ADB yet so i hope anyone can help, and tell me what to do next. Thanks in advance

edit: Installing android sdk at the moment for ADB, my Windows 7 recognises my fastboot i believe) it installed some drivers and bootloader says FASTBOOT USB. I have no idea this is helping but i thought maybe i could try to fastboot flash a new recovery image but i don't know how that works exactly. so any help is appreciated. I'm going to sleep now but i hope i get my phone fixed for tommorow i can't afford a new one :P
[G1 Android Development] Firerat:
connect phone via usb, on press 'back', that should get you into fastboot mode

then on your pc, go to command prompt and cd into your sdk tools folder

fastboot flash recovery c:\recovery.img

where c:\recovery.img is the full path and filename of your recovery.img

alternatively try this

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

Its a script I made for people who couldn't use fastboot for whatever reason
[G1 Android Development] garlonnl:
Thank you very much you just saved my G1 :)

your method worked just perfect and i'm running RA-dream-1.7.0 now.

i'll try to read better the next time i want to flash a recovery image.
[G1 Android Development] Manny-:
Thanks for this! :D
[G1 Android Development] cameron.t90:
thank you ssoooo much, fixed my recovery with this method first try!

:)
[G1 Android Development] robuser007:
any updates in the future?
[G1 Android Development] raven_raven:
It would be sweet if there will be file explorer like in clockwordmod and an option to wipe system.
[G1 Android Development] IanVaughan:
Is this method ok now with CM5.0.8-DS?

As I cannot get to Amon Ra recovery! Holding down Home just hangs, but I can boot normally!

So its either this method, or fastboot via adb, and Im not very comfortable with adb/fastboot.

Firmware:2.1-update1

Baseband:62.50S.20.17H_2.22.19.16I

Kernel: 2.6.34-cyanogenmod shade@toxygene #1

Cheers
[G1 Android Development] Firerat:
http://forum.cyanogenmod.com/topic/961-recoveryfixed-unable-to-reboot-to-recovery/

your best bet is to scroll right down and do

*NEW* Another script by Firerat

tbh it should be the first option as the others are just 'voodoo'

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

yeah, nice little hacky crap which may or may not work

direct link to something that works , and works first time

http://forum.cyanogenmod.com/topic/...to-recovery/page__st__40__p__21996#entry21996

it is the easiest why to fix it
[G1 Android Development] turb0chrg:
Menu script location?

Hey there. Where do I find the code for the menu script in the file system? Specifically I'm interested in looking at what exactly is executed in the "Wipe cache" and "Wipe Dalvik-cache" items.

Thanks, Joel.
[G1 Android Development] Firerat:
the link is in the OP for everyone to see
[G1 Android Development] phucnguyen:
Struggling on ADP1, using fastboot

Hi,

This is like the first time I do anything like this

I followed the instruction on this thread, using the fastboot method. Fastboot saw my device and eventually outputed:

sending 'recovery' (4594 KB)... OKAY
writing 'recovery'... OKAY

Then I tried rebooting into recovery mode again using Home+End, but found the same old screen. Not with menus with a lot of options like in the screenshot. What have I done wrong? And ultimately, am I going on the right track of trying to install CyanogenMod-6 on my ADP1?

Many thanks :)
[G1 Android Development] jj972:
ok heres my problem. about a week ago i wet my phone and since then the home button doesnt work. when i press it nothing happens. when i reboot my phone it boots into recovery everytime (i have to go into console and type reboot android)....so the cyan rc3 came out and im getting ready to flash but cant wipe, flash, etc because it says press home to confirm and of course my button doesnt work. i press home and it doesnt do anything....i remapped my home button to my camera button and it works in the os but still does the same when booting and in recovery. ive tried searching on how to flash roms through adb but cant find anything.....so is there anything i can do in console, adb, etc? any ideas? any advice would help :confused:
[G1 Android Development] Firerat:
learn fastboot, and flash the ROMs boot image to the recovery partition.

downside is you will only be able to boot recovery via fastboot

use the search feature and read about fastboot
[G1 Android Development] wrsg:
is the dream also getting the update to allow unsigned flash?
[G1 Android Development] BookCase:
Mirrors are down.

:(
[G1 Android Development] Duke3d:
What am I doing wrong?

OK so looking to upgrade from CM 4.2.0.15 to the newest and greatest (6.x) and I apparently need Danger SPL, which needs Amon Ra's recovery.

The problem I'm having with running the recovery .img is it just sits in the console and doesn't do squat. I tried changing the file name to a non-existent one and it gives me a file not found error, so the file is indeed there but it's just not flashing.

I have tried the recovery screen, as well as the terminal app. I type su - and hit allow/remember when asked for the permissions prompt screen (I'm assuming this is "rooting").

When I type the flash_recovery recovery /sdcard/recovery-RA-dream-v1.7.0.img and hit enter, nothing happens. Tried a different console app, same thing.

Please advise.

Or can I just go ahead and install Danger SPL with the stock CM4.2.0.15 recovery?

Thanks!
[G1 Android Development] Firerat:
try doing

su
erase_image recovery

first

but, tbh it probably worked the first time, its just a little shy and keeps quiet
[G1 Android Development] warriorvibhu:
My friend i Had PMed you Amon_RA... How about one for Htc Buzz/Wildfire.
[G1 Android Development] bluedragon1982:
That would be great, and it should have an additional menu for PSFreedom too ;p
[G1 Android Development] NeTRaW:
It would be great a port for HTC Fuze (HTC Touch PRO) :D

Regards,
[G1 Android Development] zgjbeta:
Ok so i have a MT3g running Cyans 5.0.7 this is obviously a 32b. Unfortunatley i made the most retarded mistake of trying to flash a new recovery rom 1.7.0 from 1.2.6 and instead of booting in recovery i did it directly from adb shell on my pc while phone was booted on rom. It oddly didnt give me any error messages but when i tried booting in recovery i get the mytouch green logo screen and wont boot. There are no recovery logs tried both commands and i cant update my rom nor can i push the engineering spl because i was told u need to be in recovery for that? Is that it? Is this phones recovery done? What are my options? Thank You in advance!

Btw looked at other posts i promise this is not related.

Phone however does boot to my rom just not in recovery?

Also i cant do it from fastboot cus it wont allow me!
[G1 Android Development] Amon_RA:
Boot your current rom.

Download rom mananger and flash cwm recovery, once it's flashed return to rom manager and flash alternative recovery (alternative recovery is greyed out if you didn't flash cwm yet).
[G1 Android Development] Firerat:
do as RA says above, and if that fails then

http://forum.cyanogenmod.com/topic/...to-recovery/page__st__40__p__21996#entry21996

its a script I made to get round the low memory bug

use the FR-flashRec-v04.txt ( it will find the .img rom manager downloaded auto magically )
[G1 Android Development] damien8:
Can someone please help me, I have no idea how to install the Amon_RA Flash.

I have a HTC Dream on Rogers (Canada).

What is the easiest way for me to install this? I have the file on my sd card, and the first method of installation says I need Engineering SPL???

Please help!!!
[G1 Android Development] TeeJay3800:
Check out this guide here: http://wiki.cyanogenmod.com/index.php?title=Full_Update_Guide_-_Rogers_Dream_EBI1#Installing_a_Custom_Recovery_Image
[G1 Android Development] damien8:
How do I launch Flashrec? I installed it, but then I get an option for "download recovery image" or "backup recovery image".

On the guide you linked me, it shows a command prompt???

HELP PLEASE!
[G1 Android Development] trapdogg:
Which recovery do I use for a mytouch 3g 1.2? H or g
[G1 Android Development] beckytijerina1:
im trying this to download all the files i need to root my G1 but some of the files like recovery and signed-kila is a zip file....should they be zips files ???? help.Thanks
[G1 Android Development] Jakg:
Got a wierd problem with 1.7 Cyan - when I boot into recovery it just freezes.

I also get the error "E:Can't open CACHE:recovery/log"

I can reboot with the three finger saloon, and everything works in CM just fine... but it means I can't update :(
[G1 Android Development] Amon_RA:
fastboot erase cache
[G1 Android Development] Firerat:
or

adb shell rm -r /cache/*

or in cm do above in terminal , but leave off adb shell
[G1 Android Development] Jakg:
"No such file or directory" in the terminal.

I used TA Utility to move my cache to the SD card - could this be the problem?
[G1 Android Development] Firerat:
no

cache comes from the French cacher 'to hide'

the /cache partition , and "cache" are two different things that happen to have the same name
[G1 Android Development] ralphclark:
Titanium Backup needs recovery image to flash unsigned zips

Titanium Backup has two features that need a compliant recovery image

1. Ability to flash titanium backup software from recovery right after flashing a new rom or nandroid backup

2. "Chuck Norris" mode - uninstall applications from /system by passing a removal script on to recovery and rebooting.

Unfortunately the app saves the software in each case as an unsigned zipfile so RA-dream-v1.7.0 won't play along. Amon-Ra has released updated recovery images supporting unsigned zips but only for other phones, not for the Dream.

I know it's possible to remove bloatware from /system manually via adb but given the ever expanding list of things to do when you flash a modern ROM (2708 radio, custom MTD, sd2ext scripts etc etc) it would be darn nice to have just one or two things made a bit easier.

I've PM'ed Amon Ra to ask him if he plans to release updated versions of the Dream recovery image. Surely I can't be the only Dream tinker affected by this...?
[G1 Android Development] Ohsaka:
In the meantime, couldn't you just sign the zips yourself and run them?
[G1 Android Development] houn2000:
Can't get into amon-ra recovery....

I've tried all the methods out there to get into RA-recovery, but after every flash, when I boot into recovery mode, it still gives me the default recovery screen, with no option to update from .zip.

the flash_image command reports no errors, so I can only assume that it successfully flashed the recovery.img, but still no luck booting into it.

This is on a Rogers Dream, hboot 1.33.0010. Is there still no way around this "perfect" rom?

Please help, before this phone goes in the blender!
[G1 Android Development] Firerat:
post to

I will blend it for you...

or, read stuff
[G1 Android Development] Ohsaka:
On twitter I saw some posts about v2.0 of this recovery for Nexus phones... I wonder if it will be backported to the G1...
[G1 Android Development] ralphclark:
Obviously that's what we're all currently doing. I'm just saying it would be nice if this wasn't necessary as it's already been fixed for other HTC android phones. I did try to make my choice of words clear enough to convey my intentions.

In any case the "chuck norris" function doesn't allow this; it creates an unsigned zip and a boot script on the sdcard, reboots via recovery into the script, and then fails because the unsigned zip won't install. At that point the script is terminated so you have no opportunity to sign the zip and continue.

Remember, the entire point of this function is to avoid having to do it manually, so don't ask me if I can't jump into console and do it manually. That's not the point.
[G1 Android Development] Amon_RA:
Just because one software package is not working like it should (it should sign zips, period) doesn't mean that I need to update my recovery for it...

If tomorrow someone makes a software package that requires a recovery to beeps every few seconds you would assume that every custom recovery is updated specially for this, for one software package?!

Anyway, I added a toggle signature verification in v2.0.0 which will be released when it's finished.
[G1 Android Development] Vlad83:
With all due respect, unless I am mistaken, you make your recoveries as a contribution to the community. If that's the case why not let the user decide whether he wants signature verification enabled? Clearly, there is enough demand. This is evident in every forum, not just because of titanium. Also, your comparison of signature verification to software that makes the recovery beep every few seconds is silly, this has been a desired feature for a long time, hence why clockwork recovery disables it by default.

There is a very popular company that is very closed minded and arrogant. It is run by a dictator that believes he is always right and never admits his mistakes. He is feuding with another company that makes software which is on over 90% of worlds computers, yet he refuses to allow it to run on the company's devices. All while his loyal customers are complaining that this software is essential and the devices are incapable of doing many things that they desire...

Please don't act towards this feature as Steve Jobs does towards flash...
[G1 Android Development] Amon_RA:
I do give the user to option to decide what they want, the source is available on github, everyone is free to compile their own version with signature verification switched off by default.

There will be a toggle option in the next version, so there's no need to compare me with idiots.

I just don't like to switch it off by default because of the many winzip "devs" that want to push their awesome l337 roms to the public. If a "dev" can't even sign a rom something must be wrong with the quality of his/her work. You can't imagine how many many users PM me claiming my recovery "broke" their phone after they flashed a ****ty rom.
[G1 Android Development] ralphclark:
Amon RA thanks for responding, it's appreciated.

I completely understand your point about amending the recovery rather than the app being kind of like the tail wagging the dog. I don't disagree, and I've also lodged a query with the Titanium Backup developers.

I only sought remedy from you because it seems you already fixed it in the recovery images for other HTC Android ROMs. I just wanted to know if your recovery image for the relatively ancient G1 was still actually being maintained or not.

This is only speculation, but the TB devs might be reluctant to add zip signing because there's little info out there on how it's done apart from the physical example of Stericsson's testsign tool - and incorporating that into their non-free app might have difficult licencing ramifications.

Please don't add a beeping feature though as it would wake up my wife when I'm flashing nightly ROMs in bed under the duvet... :D
[G1 Android Development] bemymonkey:
Sorry i this has been asked before, but is it normal for this recovery to have problems making a NAND+EXT backup if there are two EXT partitions (SWAP+EXT)?

I keep getting an error (run nandroid-mobile.sh or something) when I run the NAND+EXT backup, but NAND backup without EXT works fine. The SD card was partitioned within Amon-RA recovery, with 64MB SWAP and 512MB for A2SD. Should I reformat with just the one EXT partition (I don't need the SWAP partition any more)?
[G1 Android Development] billquinn1:
Could you include "beeping" in v2.0.1(whenever it comes out)? I like to flash roms with my eyes closed in case the phone explodes. Sometimes I have waited for hours not knowing if the flash had finished or not. It can be really difficult to keep your eyes closed that long when you are awake. Maybe I could start the flash and just go to bed or I guess I could purchase some sort of face shield but I just thought it would be so easy for you to make it beep...
[G1 Android Development] AndDiSa:
Why not using bart (which pincipally isn't anything else)? I am using it always without any problems and my sdcard has also EXT and SWAP.
[G1 Android Development] Ohsaka:
I agree. Just use BART. It was save the backup in /sdcard/bart/defaultrom folder. I usually rename the folder to something else to indicate which ROM version it is and then copy it to my computer for safekeeping. I have over 50 BART images now. When you need to restore one, copy it back to the phone and rename the folder back to defaultrom.
[G1 Android Development] AndDiSa:
I agree fully! Have a look at the G1-General or Q&A-section. Almost every day the same questions like: 'I used AndROOT to root my phone now it sticks on the G1 logo' Or in the other threads here around. You can tell them tree times they should read the OP, but they are still asking the same questions. If people can get a tool, they will use it, even if they do not now how to ... :(
[G1 Android Development] bemymonkey:
Thanks for the tip - to be honest, coming from my Desire, I don't have any idea what BART is - AmonRA and Clockwork both only have NANDroid on the Desire :p

I'll give it a try though. Don't know why I didn't think of it earlier :D

BTW: I swapped out my SD card for one with only one ext3 partition, and I'm still getting the error. Maybe it's ext3 that's the problem? Should I have used ext2?
[G1 Android Development] raven_raven:
If we think that way, we never should have rooted G1, because that itselfed caused problems for noobs. Don't go crazy, please. What a strange kind of thinking it is. If there is a nice feature and it will be useful for many users, why resist do implement it? Because some morons will break their phones with it? OK, but in the same time more users will have benefits from this.
[G1 Android Development] AndDiSa:
I think it's a matter of responsibility. Technically it's no problem to build a car which goes up to 300 mph, but is it responsible to sell it to everybody? I have no problem with providing tools which help people to root / mod / ... their phones, but I would prefer to make people think about what they are doing and that it might be dangerous to do so and this before they brick their phones. Only my 2 cents.
[G1 Android Development] Vlad83:
Actually your analogy is wrong. It is the technological limitations of power, weight, wind resistance, etc. that prevent a company to build a 300mph car, not their morals. If Lamborghini or any other company had the capability to produce it, they would. Which would only be 30mph faster then the current fastest car by the way. By that reasoning knives, scissors, nails, etc (won't even mention guns) shouldn't be produced because some idiot may hurt him self.

If they root their phone it is their responsibility to educate them selves as to what to do and what not to do. Raven is right, should those of that are informed have to suffer because some idiot may brick their phone? Developers are here for those of us that know what we are doing and the risks involved. It is not their responsibility to hold anybody's hand.

I agree that signature verification should be on by default but we shouldn't be deprived of the option to turn it off because of idiots.
[G1 Android Development] Firerat:
@thewhiningmuppets

do it yourself or stfu
[G1 Android Development] Vlad83:
@thecommunist

We are discussing a feature that many in the community would appreciate.

Your opinion is noted. Ty
[G1 Android Development] Firerat:
stop whining, code it yourself and stop making petty demands

The only person stopping you from being the community hero is yourself
[G1 Android Development] sparksco:
^^ they think it's easy, until they try it themselves. I've never had any serious issues with this recovery, so I don't know what all the griping is about.
[G1 Android Development] Vlad83:
This is the last post from me on this topic, sorry for thread jack.

1)No one is demanding and it's not petty. Amon_RA was simply asked to make this available for the G1. This is a long wanted feature that was implemented in the other recovery a while ago and in RA recoveries on other phones already. As a matter of fact before 2.0 he had a custom 1.8.0.1 recovery for the N1 that had no verification check, not even a toggle.

2)Kudos to you for writing a couple of scripts but don't get all high and mighty. Most features in the custom apps (browser, dialer, phone, even ROMs) are requested and tested by the users in this community. Are you saying we should refrain from suggesting adding new functionality or how to improve a piece of software? That sounds pretty silly... Look guy, you can be the community hero, I am not trying to, but if it doesn't pertain to you... as you so eloquently said a few comments back; stfu.

@sparksco

You must have missed the point while looking up at Firerat. No one said coding was easy. Amon_RA is just trying to protect the idiots from bricking their phones while some of us feel that it should be up to the user to be properly informed. So your 2cents is really off base.

I am out. Flame on.
[G1 Android Development] jamal717:
wowwwwwwwwwwwww thats crazy
[G1 Android Development] Sergio54:
Hello,

I am also interested in this feature
[G1 Android Development] Firerat:
if you want to flash unsigned zips, use clockwork

I realise that it has no console, but lets face it, if you can't sign a zip, what are you going to do in console?

http://lmgtfy.com/?q=sign+update+zip

flashable recoveries ( sighed )

http://www.mediafire.com/?eufe1p61c8pny

I have RA 1.7 on my sdcard, just in case I need to get to a recovery console and I don't have adb shell

You ( the community ) have asked, request was declined with explanation

move on
[G1 Android Development] MentalDeath:
You can call me whatever you want but this damn thing won't work for me.... I tried the fastboot and the adb methods but it just won't work.... I can do this on my Hero but and for some reason this will not work on my G1 (I only got it yesterday my friend gave it to me he didn't want it so I rooted it and all that jazz, it is a Rogers Dream and it is running 1.33.2005 spl and if it matters which I doubt I am using BiffMod2.1).
[G1 Android Development] Firerat:
Flash the Rogers version (R)

Or type less and read more
[G1 Android Development] MentalDeath:
I already tried the Rogers version I tried the 1.7.0 and the 1.6.2. Neither boot into recovery just hang on splash screen.
[G1 Android Development] Firerat:
maybe your mate gave you a phone with screwed mtd

or you did something wrong, like flash a 2.x radio and not use a standard 32b recovery
[G1 Android Development] sparksco:
Your asking if it matters what rom your using, yes it does. The rom only has the kernel, and everything else to make your phone run or not run, so why wouldn't it matter?
[G1 Android Development] MentalDeath:
I flashed a 2.x radio since the BiffMod thread said it was necessary and I did that using this thread. And I tried to do 2708+ kernel prior to the BiffMod to get different kernels, but I always ended up with no recovery but then I got a recovery with it (1.4.2 from Haykuro's root thread but no ROM would boot up so I got rid of the 2708+ stuff I install by "fastboot flash nbh orange-1.58.73.2.nbh" found in the 2708+ thread. Then I flashed BiffModv2.1 and I am stuck with the 1.4.2 recovery so I assume I screwed something up.

I know what a ROM pertains but I was stating what ROM I was using in case it made a difference for some reason to why I couldn't flash the newest RA recovery. I thought it might matter because I find flashing ROMs on the Dream quite weird since it seems that certain ROMs need the DeathSPL with this radio or that radio. Since I am used to the HTC Hero all I know about radios is that they change how well your reception is and GPS and what not.