Hi,
So I wanted to upgrade my CM6.1.1 to the stable CM7.
I went to CyanogenMod's wiki for Nexus one as I always did and it says to install the latest radio 5.08.00.04, However I already updated my ClockworkMod to 3.0.0.5 and when trying to flash the radio zip I get this error:
Amend scripting (update-script) is no longer supported.
Amend scripting was deprecated by Google in Android 1.5.
It was necessary to remove it when upgrading to the ClockworkMod 3.0 Gingerbread based recovery.
Please switch to Edify scripting (updater-script and update-binary) to create working update zip packages.
After googling a bit I saw understood that my only solution is to downgrade CWM or to flash Amon_RA instead.
Now here's the real problem:
I can't flash to Amon_RA because I won't be able to boot into it. My power button is not functional.
I'm scared to try and downgrade CWM. After some more googling I saw people that claimed downgrading through rom manager did nothing and they still booted to 3.0.0.5, one guy said he got bricked though I don't see how since it's not a radio flash.
Bottom line, the page http://wiki.cyanogenmod.com/index.php?title=Latest_Version#Nexus_One says the latest radio (without saying which one it is) is required for CM7.
Is this true?
Any ideas, thoughts, help, cookies, would be welcome.
p.s.
My Nexus One is originally an AT&T/Rogers nexus if it makes any difference
p.p.s
How come Cyanogen posts instructions to flash a radio that doesn't work on the most recent CWM, is there another version of this radio update.zip that's using Edify?
Try post in the Q&A section
update:
Got over my fears and tried downgrading CWM.
Now trying to flash the radio... Couple of consecutive reboots, my heart skipping a couple of beats...
ok... looks ok... CM (still on 6) is loading...
Takes a long time...
Got the new radio!
Flashing back to CWM 3.0.0.5.
Everything seems to work fine...
will update after upgrading to CM7
Sorry for not posting in the Q&A section.
CM7 loaded fine, everything seems to be in order...
Damn it:
1. For some unexplained reason, Google talk authentication fails, even though contacts and calendar synced fine (so it's not a wrong password or something)
2. The Market is acting funny:
2.1 It won't download anything (same old "failed downloading..)
2.2 Search auto complete shows a list of java.lang.NullPointerException
update:
Had to download Titanium backup .apk manually from the web, push it to the device with adb, only to wipe the data of the market app.
That seemed to fix the market.
For some reason it looks like Google talk authentication is also fixed.. after the market wipe...
weird.
I've never updated my radio, and I've never had a problem with any custom ROMs. I've been running CM7 for a while now with no issues.
Related
I've been reading these forums for quite some time folowing H's and JF's builds and just seeing what the devolping community has been up to.
I've been wanting to root my g1 for some time but didnt ever make the jump till now. I read through the Helpful Thread / Build Round up started with in the beginning there was root as well as the How-to- Root, Hack, and Flashing your G1/Dream and decided i could do it. i followed all of hte steps with ease. had my phone rooted within 20 minutes the first thing i wanted to do was to get a new rom with cupcake but i also wanted to be sure not to mess it up so i read through nandroid and was a bit confused as to what all was needed so i figured the recovery img that the tutorial gave was fine since everything i had done was no problem. i then went to H's ion thread and saw that i needed a differen spl so i went and read about those and decided with hardspl got that applied no problem. i downloaded the ion rom renamed it to update.zip put it on my card and loaded up recovery mode pressed alt+s to apply it and everything went fine till it hung at the 2nd boot screen. a little disheartened i went into the spl using camera+power and flashed the recovery img. i read around the forums seeing if i did anything wrong and couldnt figure it out so i tried a different rom this time one of Jf's early roms i think it was rc33 i tried to apply that but i got a no signature verication failed at the recovery screen so i tried some others. JF's 1.51 and same problem. i read around some more and thought maybe it was because i didnt do alt+W so i tried that with JF's roms and both of the leaked hero roms (i know hero is extremely unstable but i just wanted to see if something entirely differnt would work.) by this time i go into the spl again and saw that the hard spl wasnt loaded any more (i guess the recovery img changes that) i reloaded the recovery img once more and tried to install a the 2nd Ion rom with H's root apps and still the same problem.
i really try to read and search before posting but after 4 hours of nothing i really just want some help. if someone could help me get a working rom on my phone preferably H's new Ion rom and tell me what im doing wrong i'd be endlessly great full.
Im guessing what happend was you did the switch of releasekeys to testkeys and then later redid the DREAIMG.nbh. If so you need to redo the steps involving testkeys. This is why it gives the no signature verification error.
In fact id suggest redoing the whole root process again. starting with the DREAIMG.nbh.
I'm trying to upgrade my brother's MT3G from a 1.5 build of cyanogen to a 1.6 build. the latest one, which is I believe is 4.2.5.
When I upgraded my G1 ages ago, I downloaded this file
"signed-dream_devphone_userdebug-ota-14721.zip"
ran it from the from power + home then upgraded cyanogen rom without a problem.
The sapphire equivalent is this:
signed-google_ion-ota-14721.zip
I just finally got around to my brother's MT3G, and when I try to install it I get this error:
assert failed getprop == "sapphire" (status 7)
some tutorials I read listed this one instead, so I tried it...
HTC_ADP_1.6_DRC83_rooted_base.zip
it installed, then I upgraded to 4.2.5 and it booted no problem. But, I can't get Market or Gmail to open now. I thought the last file I listed was supposed to fix that, but apparently not. I'm at a brickwall, I have zero clue what to do to solve this problem.
just did a wipe and reinstalled both zips.
it works now.
HAHA good job buddy
you did the right process the onlything you might have not done right is a full coplete wipe that is the only thing that could've caused you to not get those things to work properly... try again from recovery wipe evrything do it twice to make sure there arent any "crumbs" left behind and then flash the drc83 image tehn the cyanogen....
P.S. there is cyan 4.2.6 out now just a heads up not much differant but appearently bug fixes even though I never had any bugs with cyan 4.2.5
Hello,
I have a problem with my G1.
I got my G1 maybe a month ago. It had firmware 1.1 and radio module 1.22.12.29. Back then I did not realize it was a radio image compatible with firmware 1.0 as far as I gather from the HTC website.
At first, I did not intend to root it at all, a decision later I would regret. Well, it worked OK, only it was not updated. I was told I would receive the update over-the-air in 4 days. At first they said it would be to 1.5, but it turned out my operator started to upgrade straight to 1.6.
And so I did receive it in 4 days and the problems began.
Basically, the voice quality is so bad that half of what I say is ununderstandable. My voice sounds metalic and I cannot have a coherent conversation over the phone. It is a business phone, so you can imagine it is rather annoying when I have to struggle to be understood by clients.
Ok, so I checked the bootloader for the radio image version and I found out it was still version 1.22.12.29. As per the HTC website I should have 2.22.19.26I. So, obviously the radio firmware was not updated as it should be as per the HTC website. Thus, it seems the reason voice quality is so poor is the outdated radio firmware.
Since I did not plan to return my new phone to my operator (I had no time for it), I decided to root the phone and update the radio firmware myself. It seemed simple enough and I use Unix and Linux since 15 years, so it seemed it would pose no problem.
Quickly I learned that rooting 1.6 is not so simple. One-click method fails. Only goldcard worked and after a few days of struggle I finally got back to firmware RC7 and rooted the device.
Right after I updated the recovery image to CM 1.4, but before I flashed the CM ROM I attempted to update the radio firmware as was suggested by one tutorial I followed as well as the CM website.
Well, it all went smooth. After the update I pressed Home and Back, it rebooted, back to recovery CM1.4, one more time Home and Back and I was back to the working phone. I checked the radio firmware and lo and behold, it was still version 1.22.12.29. No errors, nothing, smooth update process and no result. I repeated it at least 5 times to no avail.
I decided to install CM 4.2.7.1 ROM and try to update the radio then. Before the CM ROM I updated the SPL to HardSPL with success to have fastboot and went to install CM. It went smooth and I booted into this new rooted G1 ROM with ease.
Again, I attempted to update the radio firmware from recovery CM1.4 and again no results.
So, I am back to square one. I have again firmware 1.6 only from CM instead of stock HTC, and I cannot use this phone for calling.
So, summarizing, I got the phone with firmware 1.1, but radio firmware from 1.0. Why it was not updated together with the system I do not know. Then I got an update to 1.6 and the radio firmware also did not upgrade. Then I went back to RC7 (firmware 1.0), rooted the phone, attempted the radio firmware update before installing CM ROM and failed. And finally, I installed HardSPL + HTC 1.6 recovery (as suggested on the CM website) + CM ROM and again failed to update the radio firmware to 2.22.19.26I. The update process is going without any errors. Verification, extracting, installation of radio image all go OK, the phone reboots but no radio updated.
Anybody any idea why it is like this? Why this phone refuses to update the radio from HTC website.
Any suggestions?
Oliwer
PS. One more thing, I was contemplating updating the radio via fastboot, but it seems after reading HTC website that fastboot is only for system and recovery image flashing. The radio has to go first adn from recovery console. Am I right on this?
I too have a problem updating to the 26i version. however i rooted at 1.5 using the one click root method and ive since switched from cyan 1.4 recovery and cyan roms to amon recovery and dwang roms. No matter which recovery i use, the 26 update flashes without an error but shows up as the same radio ive had all along (1.22.14.11) i made a thread about it but noone seems to have an answer. Sorry I couldnt help, but at least bumped up your thread and maybe someone can help us.
speedysilwady said:
I too have a problem updating to the 26i version. however i rooted at 1.5 using the one click root method and ive since switched from cyan 1.4 recovery and cyan roms to amon recovery and dwang roms. No matter which recovery i use, the 26 update flashes without an error but shows up as the same radio ive had all along (1.22.14.11) i made a thread about it but noone seems to have an answer. Sorry I couldnt help, but at least bumped up your thread and maybe someone can help us.
Click to expand...
Click to collapse
Thanks for sharing!
At least I know I am not alone here with this problem.
Since it's Christmas and I have some more time, I decided to do a Nandroid backup and wipe my phone back to the original rom with 1.0 firmware (RC7).
I used my goldcard and I flashed it in a few minutes. I logged back into 1.0 firmware with the original bootloader and recovery console.
Next I put everything on my goldcard, flashed the recovery CM1.4 from the terminal, went to the bootloader, flashed update.zip with the newest radio 2.x from HTC, everything went smooth. Reboot and again NO change of the firmware. Tried a few more times flash the radio and HardSPL together to no avail. I restored my backup and found myself back to square one.
One think I noticed, and I wonder if you get the same, is that when I flash the radio, the phone reboots back to the recovery console and shows "Formating Cache..." message. It does not tell me anything like Please reboot, just this message. Meanwhile I can move the cursor up and down the recovery menu, so the phone has not hang up. It just sits at the recovery until I reboot it. Once I waited 30 minutes to see if it reboots itself and it does not. So, I press Home+Back and then it reboots fully and after loging in I check the radio and NO change.
So, I wonder if your phone does the same?
Oliwer
PS.
T-Mobile G1 - w/ ROOT
DREA110 PVT 32B
HardSPL 10.95.3000
Recovery image: HTC Android 1.6 (from HTC website)
Class IV 8GB SD Card w/ Ext 4 Partition and Swap partition
That's a huge wall of text, and it's Christmas so I'm a little merry
When flashing the radio image w/ Cy's recovery you must flash as an update.zip using alt-s, press whatever key you need to press to confirm and reboot using home+back. If you use flash any zip or use the trackball to reboot the radio image (or SPL) will not reboot in the required way to complete installation.
AdrianK said:
When flashing the radio image w/ Cy's recovery you must flash as an update.zip using alt-s, press whatever key you need to press to confirm and reboot using home+back. If you use flash any zip or use the trackball to reboot the radio image (or SPL) will not reboot in the required way to complete installation.
Click to expand...
Click to collapse
I tried all possible ways. Just a few minutes ago I went to CM1.4 recovery, used the update from update.zip, pressed Home+Back, rebooted back to recovery console, pressed Home+Back again, booted to CM4.2.10, punched the PIN code, checked the About Phone section and I am still with 1.22.x radio firmware.
This phone simply refuses to update the firmware in any known way.
So, my plan now is to un-root it back to the state I got it 2 months ago and return it to the operator and request upgrade of radio, since Donut with an old radio is basically useless. People simply do not understand half of what I say even if I speak slowly and quietly.
Cheers,
Oliwer
You have to press
Cam+power and it will show radio
....
In settings that radio has nothing to do with one installed...Do you know that the radio does?
It allows custom roms like cyan to be installed while keeping root access. The rom allows some tmo apps like account to still be used here in the states.
yes oliwer i get the same formatting cache message but nothing else happens. i tried in cyans recovery and amons recovery using only button shortcuts and not the trackball. i always named the radio update.zip, but still no luck. Im not sure if the 26i radio requires a certain version before it can upgrade, like maybe i have to upgrade to another radio before i can get to 26i? im not quite sure...ive run out of ideas on what to do. I dont have a warranty or anything on my g1. does the fact im using a donut rom on a cupcake radio have anything to do with it? if i had a cupcake rom and upgraded the radio to 26i from there would it work? i know these might sound like dumb ideas but im still relatively new to the scene and im running out of ideas as to why this is happening or why i cant solve it..
bump? anyone have a solution for us? or advice?
i just realized that i had android 1.1 with the 1.22.14.11 radio when i first got my phone, when t-mobile gave me the 1.5 update, i was still stuck on the same radio for some reason. After that I used the one click method to root and ive been on dwang donut rom ever since with the same dated radio...Ive tried using cyans recovery to flash and still no luck, no error, it says its updated but when i check the baseband or stock spl its still the same radio. I never went for a danger spl when i rooted because i was afraid to brick so i cant fastboot a radio update. I asked in another topic if it was possible to use the "flash_image" command in terminal to flash the radio but i dnt think itll work and i dont wanna risk it. If anyone has any advice or a possible solution please keep us updated.
Thank you!
Turn your phone off, hold the camera button down, and power on your phone.
What do you see?
each time before and after the flashing of the radio using cyans or amons recovery image id get the same rainbow screen saying
DREA100 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-1.22.14.11
Serial0
so im still stuck on the Android 1.1 radio.
speedysilwady said:
yes oliwer i get the same formatting cache message but nothing else happens. i tried in cyans recovery and amons recovery using only button shortcuts and not the trackball. i always named the radio update.zip, but still no luck. Im not sure if the 26i radio requires a certain version before it can upgrade, like maybe i have to upgrade to another radio before i can get to 26i? im not quite sure...ive run out of ideas on what to do. I dont have a warranty or anything on my g1. does the fact im using a donut rom on a cupcake radio have anything to do with it? if i had a cupcake rom and upgraded the radio to 26i from there would it work? i know these might sound like dumb ideas but im still relatively new to the scene and im running out of ideas as to why this is happening or why i cant solve it..
Click to expand...
Click to collapse
I do not know, really, why the radio refuses to upgrade. Since my last message I have read tons of posts on this issue and nearly ALL people can upgrade the radio firmware easily, just like the SPL. Somehow, I can upgrade the SPL to whatever I want, but not the radio. Very strange indeed and no luck so far.
Oliwer
speedysilwady said:
bump? anyone have a solution for us? or advice?
i just realized that i had android 1.1 with the 1.22.14.11 radio when i first got my phone, when t-mobile gave me the 1.5 update, i was still stuck on the same radio for some reason.
Click to expand...
Click to collapse
Exactly the same in my case. Except they upgraded straight to 1.6. Before the upgrade I have 1.1 firmaware and quality of voice was perfect. After the upgrade things went south.
speedysilwady said:
After that I used the one click method to root and ive been on dwang donut rom ever since with the same dated radio...Ive tried using cyans recovery to flash and still no luck, no error, it says its updated but when i check the baseband or stock spl its still the same radio.
Click to expand...
Click to collapse
Same thing with me.
speedysilwady said:
I never went for a danger spl when i rooted because i was afraid to brick so i cant fastboot a radio update.
Click to expand...
Click to collapse
Well, I installed HardSPL and it worked despite the old radio. HardSPL offers FASTBOOT and I use it at times. This is safe, at least for me.
speedysilwady said:
I asked in another topic if it was possible to use the "flash_image" command in terminal to flash the radio but i dnt think itll work and i dont wanna risk it.
Click to expand...
Click to collapse
Well, I did, but it does not work since flash_image updates partitions and G1 does not have radio partition. So, when you try to update the radio.img it tells you no radio partition. It is only possible for Roger G1 since it has radio partition unlike all other G1s and there you could upgrade the radio with flash_image.
speedysilwady said:
If anyone has any advice or a possible solution please keep us updated.
Thank you!
Click to expand...
Click to collapse
Yeap! I just practised how to un-root the phone straight to 1.6 with the original SPL and recovery and I was able to restore my phone to the state before rooting and I plan to give it back to my operator under warranty and ask to get this radio fixed. I will do it next week. I will report if the authorized service will be able to upgrade the radio.
Oliwer
Hi, I have a MT3G and a G1 before that. I have experience flashing roms and other stuff. I have had the MT3G for sometime and noticed that I can't flash roms anymore since I get FC errors after the boot up. Even the latest CM mods don't let me sign in, and I have to skip the initial sign in to find the market FCing every time I open it. This is getting really annoying, and some roms won't even get past the boot screen without a fix uid mismatches which allows me to boot up, but still gives me some errors, like no android keyboard to sign in or FC on settings or other important things. Any help would be appreciated!
are you wiping the phone completely... list things in your signature like what recovery image what rom you are using at the time are you using a different SPL the community needs to know these kind of things to help you out...
I had this same problem when trying to flash Cyanogens latest.
Go ahead and find version 4.2.1.8 or 4.2.1.9
Wipe everything, then flash one of those.
Everything should work, I would advise not to upgrade to 4.2.12.2 or whatever because I experience home not responding upon reboot. Have to wait a couple times, then it's ok.
Well, I would put it in my sig, but for some reason, I can't edit it. Here's what I've got.
I had the SPL 1.33.2005 then recently 1.33.2009.
I've had problems like this on my G1 as well and never really understood the problem. I have the latest RA v1.5.2 recovery.
I do perform a full wipe and have tried to follow what someone else posted about installing a fresh rom and to fix the apk uid mismatches and a command in terminal, although neither seem to last long. Sometimes I can wipe and do an install of any rom 10 times and still get FC on startup. I fix the apk uid mismatches in recovery to be able to get further, but will usually start to have problems in other settings and apps.
I have a general idea on what to do, and usually wipe the data and everything else about 2 times. I just don't know if it's something I'm doing that's causing this.
I just searched around for the differences of SPL's and read from Amon_RA that they aren't really different besides being able to allow certain roms to run. I'm wondering if the reason I can't run certain roms is because I don't have Haykuro's Death SPL? Is the Death SPL only .2005?
Hi, I've recently bought a HTC Magic and since then I've been reading into how to root my phone. Before I start I would like to know if it's possible on my phone.
Details:
HTC Magic Vodafone Uk (32B)
Hboot: 1.33.0007
Firmware version: 1.5
Build: CRC24
I've read from a thread in another section of this forum
that it would be impossible because of 1.33.0007 being a perfect spl BUT my phone is running the firmware version 1.5, with a CRC24 build. Would this mean I will be able to root my phone or not?
Also I've been reading up on how you either have cupcake or donut. My version is 1.5 so would that mean I have cupcake?
I'm worried that I might brick my phone so would prefer to use the one click tutorial at theunlockr (would add link but I can't) which is for htc magic running on cupcake.
Would it work?
Sorry for all my questions and I probably will end up asking more
Thanks if anyone can answer these for me!
You should be able to root using the relentless rooter or by following the guide on the unlockr. You are lucky you are running cupcake and don't need to downgrade
I think you are only really at risk when you flash radio and spl. Using the unlockr's stuff shouldn't be too bad. But read eveerything a bajillion times incase
same boat
Hey bunnybag
Was in the same boat as you until yesterday.
Also had a perfect SPL (0010) on a 32A.
I was also reading up a lot wrt getting a new ROM on my phone, and was also afraid of bricking it...
The gold-card method seemed quite involved, and that QMAT application doesn't exist anymore, and the newer version of it, does not run in XP or Vista...
Yesterday, I used the one click method from theunlockr, and after a few mistakes, it worked! Now I have a shiny CyanogenMod running with a 1.6 donut
It seems with the one click method -that you do not need to change the radio or SPL (which I guess are the most dangerous flashes to attempt)
Quicky summary of what I did, and where I deviated:
1) Read the one click method from theunlocker, and some of the comments at the bottom. Also - very importantly - watch the YouTube video at the top of the one click method page a few times!!
2) Downloaded the FlashRec apk (follow link on the one click method's page)
3) Installed FlashRec (the latest version of FlashRec looks slightly different to the one in the YouTube video but functions the same)
4) Did a backup of the existing recovery image via FlashRec. After the backup, you can copy the backed up .img to your PC...
5) Copied the latest Amon RA recovery image (v1.5.2) onto the SD card. Make sure you get the right one... there is a different one for 32A/32B... [Deviation from the one click method- which uses an older version of the RA recovery image]
6) Attempted to flash the new RA recovery via FlashRec. Here is where I struck a problem - the thing just stalled - for a good 10mins - and said 'do not interrupt' :|
I hooked up the USB cable, and from the command prompt ran: adb catlog
From here, scrolling up, I could see that FlashRec gave some message of invalid recovery image... Bit of a bummer - I checked the CRCs of the recovery image after copying it to the SD, and also tripple-checked the filename I typed into FlashRec! In the one click method page, they also warn about inadvertently adding spaces to the end of the filename when you type it in. I also checked for that.
I attempted it once more as follows:
-Rebooted phone
-Deleted the RA recovery .img from the SD
-Re-copied it onto the SD, and this time renamed it to something easy: ra.img
-Checked the CRC
-Ran FlashRec, and specified the path as: sdcard/ra.img
-Flash succeeded! maybe FlashRec can't handle very long file names?
7) After the recovery was flashed, I booted into recovery mode (HOME & POWER). Seems like the Amon RA recovery image takes slightly longer to boot that the stock recovery... so - don't crap yourself if it takes a few seconds. This is also a good point to stop, and watch the second video from theunclockr on how to load a new ROM...
8) After verifying that the new recovery image was working I booted back into Android, and I copied my ROM's files onto the SD. I used the Cyanogen Mod. The Cyanogen wiki has a page on how to load it for a 32A and also 32B.
Basically, you need the latest stable cyanogen mod, an Android 1.6 "defanged" ROM (link available on the Cyanogen wiki), and a new kernel. The kernel is 32A/32B specific, so get the right one.
9) With the 3 files on the SD, I booted back into the new RA recovery I just flashed.
10) Did a Nandroid backup
11) Did a wipe/factory reset [Deviation from theunlockr method: I did not format my SD card, or partition it into Ext & Swap. I prefer not to have a Swap partition on the SD, nor do I think I'll need to swap any apps out to the SD card... I think the 32A has enough space... you can read further about it in the xda-developers wiki, under page: HTC_Sapphire_Hacking_2]
12) Still in RA recovery, I applied (in order) a) the defanged 1.6 ROM, b) the Cyanogen mod, c) the new 32A kernel
13) Flashing it takes a while - there is a progress bar...
14) Reboot after all 3 were flashed. The first reboot takes a looong time... couple of minutes... don't worry, or try to reboot again... just give it time.
15) Once inside - tested everything: GPS, Wifi, Phone, Market, G-sensor, Gtalk, Gmail.
16) It might be worth while to note that once the phone is booted, and you've entered your SIM PIN, and the Android desktop is displayed, it can still take a few seconds - 4 or 5 I guess, before you are able to interact (swipe desktop left/right). Give it time to settle down, and all is well
//TODO: still need to flash a new splash-image...
Good luck - post back here with your results!
How to root Magic (32A) with Europe ROM ROM Version:3.05.401.3 with Sense?
Have somebody any idea, how to root Magic (32A) with Europe ROM Version:3.05.401.3 with Sense? Thanks!
bogo_mips said:
Hey bunnybag
-Re-copied it onto the SD, and this time renamed it to something easy: ra.img
-Checked the CRC
-Ran FlashRec, and specified the path as: sdcard/ra.img
Good luck - post back here with your results!
Click to expand...
Click to collapse
Ah, I tried using the unlockr's method and failed at flashrec. The unlockr kept saying that the reason was because I was already on Donuts but that is not true. I ended up using the relentless rooter software (looking back, his method is basically an automation of the original method).
Maybe you should post this also in the unlockr so that people who have "backup failed" messages know what to do?
Thanks for the info. It will be very helpful for other members trying to use the unlockr method.
Thanks for the post guys.
@bogo_mips: Great advice and I'll more than likely use this along with the unlockr one click tutorial.
Oh and there's one thing I'm worried about. My phone has somehow automatically downloaded the 1.6 upgrade and it keeps asking me to install it. Anyone know of a way to delete it so that it won't upgrade?
I'm worried that it might install if I turn my phone off.
@bunnybag: that 1.6 download sounds like a problem... if it takes, you'll no longer be able to do to the one-click method...
Check around the forum for advice. I'd guess - since the download would have had to happen in user-space, that the downloaded file might be sitting on the SD card or possibly the phone's flash. Get that Linda Filemanager app from the market and poke around... I guess if you could find the file, and delete / rename it - you could avert an install?
Alternativley, I'm guessing that if you can attempt the one-click method, that you'll have a new recovery image before you power down your phone, so - I think that will keep you safe...
@visitador02: according to the FlashRec page, there are 1.5 cupcakes out there which have been patched, so - FlashRec can't work on them... maybe that is what happened to you...