Database Develop

Issue installing spl and latest radio

Hi Everyone,
I am been visiting xda since I got my g1/adp1 over a year ago. I have been using it and it has been doing very well for me. Back in January I had flashed a rom and I had ended up with the hardspl. Since then for some odd reason, I was never able to flash the dangerspl or engineering spl. So from what I looked over on the forum, I used the dream.nbh file and went back to the original release and then flashed the cupcake update as advised in one of the posts here. After doing that, I was able to log in and install FlashRec and install the Amon Ra 1.6.2 recovery.
However, after doing that, I tried to flash the updated Radio and the hard spl, and I have been unsuccessful. Prior to installing the radio, I do the wipe/factory reset and then flash the ota-radio-2_22_19_26I.zip. After it complete it and pressing back + home, it even says writing radio image. However, when I boot into android or fastboot, it still shows that radio is 1.22.12.29. And the spl is the original 0.95.0000. I have also followed the procedure in the above link to install the radio then hard spl and then the cyanogen Cyanogen4.2.12.2 installation. I was able to boot into the rom; however the radio is still 1.22.12.29 and the spl is 0.95.0000.
With regards to info on the phone, it is DREA100 PVT 32B. So I would really appreciate anyone’s advice on how I can restore it to the engineering SPL or install the hard spl and then switch to the danger spl; and also update the radio. Thank you

zer003 said:
Hi Everyone,
I am been visiting xda since I got my g1/adp1 over a year ago. I have been using it and it has been doing very well for me. Back in January I had flashed a rom and I had ended up with the hardspl. Since then for some odd reason, I was never able to flash the dangerspl or engineering spl. So from what I looked over on the forum, I used the dream.nbh file and went back to the original release and then flashed the cupcake update as advised in one of the posts here. After doing that, I was able to log in and install FlashRec and install the Amon Ra 1.6.2 recovery.
However, after doing that, I tried to flash the updated Radio and the hard spl, and I have been unsuccessful. Prior to installing the radio, I do the wipe/factory reset and then flash the ota-radio-2_22_19_26I.zip. After it complete it and pressing back + home, it even says writing radio image. However, when I boot into android or fastboot, it still shows that radio is 1.22.12.29. And the spl is the original 0.95.0000. I have also followed the procedure in the above link to install the radio then hard spl and then the cyanogen Cyanogen4.2.12.2 installation. I was able to boot into the rom; however the radio is still 1.22.12.29 and the spl is 0.95.0000.
With regards to info on the phone, it is DREA100 PVT 32B. So I would really appreciate anyone’s advice on how I can restore it to the engineering SPL or install the hard spl and then switch to the danger spl; and also update the radio. Thank you
Click to expand...
Click to collapse
When installing a radio or SPL, you need to follow its instructions.
That means that when you start in recovery mode and flash the "update.zip" matching your radio, its first step is to write it (to the cache partition), then reboot into update-radio mode, then write it AGAIN (to the radio partition), then reboot into recovery and format the cache partition.
You need to follow it the WHOLE WAY THROUGH -- not stop at the first stage and call it good.

Hi,
As mentioned before, I did follow the guide to the T on re-rooting and reflashing. I followed both ttp://forum.xda-developers.com/showthread.php?t=606147 and also ttp://theunlockr.com/2010/04/26/how-to-root-the-htc-g1dream/ + ttp://theunlockr.com/2010/04/26/how-to-load-a-custom-rom-on-the-htc-g1-dream/ . However, neither of these procedures resulted in the installation of the hard spl or the updated radio ota-radio-2_22_19_26I. The adp1 continues to be to have the Original G1 Spl 0.95.0000 and radio 1.22.12.29 from the flashing of the Dream nbh file.
So could anyone please advise on what else I can do to flash and update the spl and the radio. Thank you ^^.

you can try to flash the radio through adb/fastboot its better and safer to do..

oh? can you please tell me the adb commands to use to flash the new radio? I have look at the ADB guide for dummies and ttp://forum.xda-developers.com/showthread.php?t=532719 & ttp://forum.xda-developers.com/showthread.php?t=517874 . I can't seem to figure out how to install radio via adb. When I had the hardspl, I could install radio, system, boot, etc via fastboot. But adb is unfamiliar to me as I have never been successful with it. So can you please guide me with the commands to follow ^^. Thank you in advance.

Thats what i meant was fastboot that was my noobieness to say adb.. flash radio thru fastboot...

Yes, fastboot is where I am trying to get too. However, the original G1 spl is not letting me access fastboot. If have files on the sdcard, in fastboot it shows serial0. But when I wipe it, it shows nothing under the original g1 fastboot mode.
So can someone advice me on what I can do to install hardspl or engineering spl to get fastboot working again T.T.

same problem
hi! am having exactly the same problem. stuck on stock SPL (hboot 0.95.0000) and radio (1.22.12.29). flashing radio via recovery (RA-dream-1.7.0) yields same results (formatting cache...). tried rebooting after reboot by radio but i still end up with old radio.
any thoughts?
i want to update radio so i can flash dangerSPL and be able to flash CM6.
TIA!

Yep, that's exactly how it works. First off, are you using T-Mobile USA?
Remember to NEVER flash DangerSPL on a 1.x, 4.x, or 6.x radio!!
The following are compatible radios that you can safely flash before you flash DangerSPL:
2.22.23.02 (T-Mobile USA)
3.22.26.17 (Rogers CA)
3.22.20.17 (Orange UK)
2.22.19.26I (Non-US)
Sent from my HTC Dream using XDA App
CyanogenMod V6.0.0 Stable / HBOOT-1.33.2005 / Radio 2.22.23.02 T-Mobile USA

using a T-Mobile G1 outside the U.S.
ok, since i can't update radio as it stands, here's my plan.
1. reboot to recovery mode
2. flash HardSPL
3. flash radio
(... if radio update successful)
4. flash DangerSPL
5. flash CyanogenMod6
6. do the funky chicken!
sounds good?

Yes, but I don't think that will make a difference. You should be able to flash the radio successfully on a stock HBOOT. I've never had problems flashing the radio before, so I don't know. But sure, you can update the HBOOT to HardSPL, but I don't think it'll make any difference.
Sent from my HTC Dream using XDA App
CyanogenMod V6.0.0 Stable / HBOOT-1.33.2005 / Radio 2.22.23.02 T-Mobile USA

exact same problem
Having the exact same problem. I have literally spent 2 days trying to do this.
Trying to do the whole CMwiki procedure, unlockr procedure, and various others.
Luckily I didn't brick it.
But I am in the same boat, now matter what I try, after flashing the radio via
recovery amon-ra 1.7 I check on fastbook and it is still 1.22 version of radio.
I have the stock Hboot, etc....
Has anyone had luck with fastboot / adb flashing the radio??
Thanks for any help.

machine*head* said:
Having the exact same problem. I have literally spent 2 days trying to do this.
Trying to do the whole CMwiki procedure, unlockr procedure, and various others.
Luckily I didn't brick it.
But I am in the same boat, now matter what I try, after flashing the radio via
recovery amon-ra 1.7 I check on fastbook and it is still 1.22 version of radio.
I have the stock Hboot, etc....
Has anyone had luck with fastboot / adb flashing the radio??
Thanks for any help.
Click to expand...
Click to collapse
Flash HBOOT 1.33.2003:
http://forum.xda-developers.com/showpost.php?p=6510019&postcount=76
Once 1.33.2003 is installed you can install 1.33.2005 via fastboot as on the post I linked to .. or skip directly to the newer 2708+ radios/SPLs with extra ram:
http://forum.xda-developers.com/showthread.php?t=831139

ok guys hopefully i can solve this problem.. i never had this issue but have had slight problems almost like so here was my solution....
Stage 1 un-rooting (very simple)
1. download update.zip and DREAIMG.nbh files here...
DREAIMG.nbh http://www.4shared.com/file/9izdCbvo/DREAIMG.html
update.zip http://www.4shared.com/file/ePnmmoxA/update.html
2. boot into recovery mode and do complete wipe of everything, also repartition your sd card set 0mb swap and 0mb ext..
3. then either use usb mounting through recovery or power off and place sd card in comp to copy files over.. than put back in phone and boot in recovery.
4. flash update.zip
5. power on in boot loader and flash DREAIMG.nbh
6. reboot and do normal setup just to make sure you are 1.0 firmware
Stage 2 Re-Root device..
1. download update.zip, flashrec, recovery.img, radio and spl files here...
1.5 update http://www.4shared.com/file/EyiKXmTd/update.html
flashrec http://www.4shared.com/file/ABXfQQ1H/flashrec-113-20091107-2.html
radio 2.22.23.02 http://www.4shared.com/file/jGTeRvfs/G1-radio-2_22_23_02.html
SPL http://www.4shared.com/file/nJkB58Qf/Latest_G1_SPL.html
recovery http://www.4shared.com/file/zCVPjMUz/recovery-RA-dream-v170-cyan.html
2. place files on your sd card than boot into recovery
3. flash update.zip (gets you to firmware 1.5)
4. now boot up normal and go to settings, check in applications and check unknown sources and usb debugging.
5. go to market and download "oi file manager" open app and select the flashrec file
6. when finished select open, then press backup recovery, then type in the box sdcard/recovery-RA-dream-v1.0.7-cyan.img then select flash recovery image.
7. when finished power off phone then boot into recovery.. wipe data factory reset, then flash the radio.zip press home+back to complete installation
8. wipe data again, now flash spl.zip, press home+back to complete..
9. now partition sd card.. i use 128mb swap and 1024mb ext4...
Stage 3 advanced rooting
1. download danger spl, fr boot, super wipe, radio and hboot files here...
fr boot http://www.4shared.com/file/gjRmpuh7/FR-boot-v157-CustomMTD_S.html
hboot (0.33.0013d) http://www.4shared.com/file/tfbsSTys/hboot0013d-signed.html
superwipe http://www.4shared.com/file/qm3gl7fQ/Ohsaka-SuperWipe_v2.html
radio (2.22.28.25) http://www.4shared.com/file/tMqoIX3p/update_2222825_S.html
2. place files on root of sd card
3. boot into revovery wipe data cache all that good stuff than flash the spl.zip let finish...
4. flash superwipe, power off than rebbot to recovery then do manual wipe of everything data, cache, battery, sd partition.. then repair sd..
5. flash the fr boot file, then go to console and type reboot recovery
6. flash radio file, let it finish then flash the hboot file.. power off than power on in fastboot mode (camera+power) and check phone stats.. should be on latest radio and hboot and s-on than you are free to flash roms from here...

[Q] CM5 install prob- not booting into custom recovery?!

Hi,
I've owned and ROM'd two Android phones, but not a G1 and wanted to help out a friend to get her stock 1.6 G1 to CM5. We ran into problems which led me to not want to continue before they are sorted out. I looked for answers to this but couldn't find any, so please don't flame me if I overlooked any. I tried to go by the instructions in the CM wiki.
This is what we did:
- We installed ClockWorkMod Recovery through the ROM Manager app
- We rebooted into that recovery and via adb flashed AmonRA recovery
- we rebooted into the AmonRA recovery which worked (I *think* just regularly holding Home while powering on)
- we flashed the appropriate radio update for her US TMo G1
- the documentation said "phone will reboot during update". I think it did, but it seemed stuck on "formatting cache" in recovery.
- when holding Home on reboot after that, it did from there on NOT reboot into the custom recovery
- instead, it rebooted into what looks like "bootloader" mode on my Moto Milestone, a screen with a phone and an exclamation point. We could get into stock recovery with Alt-L, but I don't think that is what we wanted.
At this point, it seemed to not reliably boot into custom recovery, so I didn't want to continue the process. I assume I could have gone down the same of flashing a custom recovery, but I wasn't sure what would happen with/after installation of the DangerSPL if booting into recovery wouldn't work.
So - is the "booting into bootloader instead of recovery" a known issue? Am I too much of a noob on the G1 and did totally miss something? Could or should we proceed to the DangerSPL / CM5 installation with this going on?
Any help would be much appreciated!
W0nk0

Flashing a new recovery from CM5 or CM6 is not working well. Try flashing the recovery image / radio image / ... from fastboot and you should be fine.
Edit: I did not read well the first time. Now I notice, that you are still on stock SPL, sorry. But re-reading well I've got a question: Are you sure you flashed already successfully a new recovery? For me it seems you are still on a plain stock G1.
Sent from my Htcclay's Superfly G1 using XDA App

Thanks a lot for your help!
We _were_ on a custom recovery twice, after flashing it from ROM manager (Clockworkmod then) and on the AmonRA recovery after that. As the recoveries clearly had non-stock things like nandroid I'm quite positive.
The problem seems to be that they didn't "stick" - we flashed the radio ROM upgrade from Amonra recovery, but after a reboot with Home pressed landed in the exclamation point screen again (which seems to indicate stock recovery as you can get to that with Alt-L from there).
If fastboot is indeed the way to go, where do I get the drivers for the windows/pc side of it? The noob guide I found had no help there :/.
Thanks again,
W0nk0
Sent from my Dell Streak using Tapatalk

Few things;
1) if you have the OEM system image, then, indeed, the recovery will be overwritten by the OEM recovery image upon reboot into the system.
2) You say that you've written a RADIO image.... ***WHAT*** radio image did you write? You should have written a radio with a version number that starts with a "2".
3) Have you written a new SPL? The SPL you should write is 1.33.2003. DO NOT install deathSPL, no matter how many RETARDS suggest it. There is ABSOLUTELY NO USE in it. 1.33.2003 is SAFE to install (unlike 1.33.2005), and the ONLY benefit of 1.33.2005 has been GREATLY EXCEEDED, making that "benefit" entirely pointless.
Note that with the stock SPL (0.95.0000), there IS NO FASTBOOT. 1.33.2003 has a very strong fastboot capable of writing ALL partitions, including the radio image. Fastboot is the safest way to write the radio and SPL, but prior to installing an SPL with a strong fastboot mode, obviously you can't use this feature.
Steps:
1) Reinstall custom recovery,
2) reboot into recovery and write 1.33.2003 SPL.
3) DO NOT let it boot into regular system prior to installing 1.33.2003 SPL, or it will overwrite that custom recovery.
4) After installing the good SPL, it would still overwrite the custom recovery by booting into the regular system, but by this time, you will have FASTBOOT, so it doesn't matter.
5) Now do what you want... but once you have a 2.x radio and 1.33.2003, do NOT write any other radio or SPL, and for F SAKES DO NOT RUN ANY NBH FILES EVER NO MATTER WHAT!!!

[Q] Nexus One dead, no screen Response

Hi everybody, I unlocked a N1 using fastboot and clockwork recovery. At the time to install the CM6 I encountered and error related to the version of de HBOOT.
I found a guide by Amritttt for reverting HBOOT to 0.33.0012, when I flashed PASSIMG following reboot the screen has become dead.
I tried to re-flash the phone with Amon_Ra recovery (1.8.1 and 2.0) but I can't enter in any mode. The only way I found is entering in the Bootloader and pushing files using fastboot... so I tried to restore the original system using the following:
PASSIMG_Passion_Google_WWE_1.01.1700.1_ERD79_release_signed
Passion-VF-FRF91
with this method: uncompress, flash userdata, system and recovery.
But it did't work, in the last flash the phone hasn't the SIM inside and I realized that the trackball blincked in red two or three minutes after rebooting. So I am wondering if I have a SLCD N1 what can I do to solve this disaster??
thanks!

Look at my signature, go there, see "Unroot/restore your Nexus", reflash EVERYTHING - either with fastboot (and you need to reflash HBOOT too), or do the PASSIMG method - with FRG33, and then upgrade to FRG83.

actually ignore me, that wont work for s-on, yeah, u gunna have to go through the pass-img method, completely reverting back to stock and start from scratch

Thanks, I'll try. I can't use PASSIMG method because my screen ism't working, or there's other way to do?
When you say all, you refer to use "fastboot flash all FRG33" Doing that I reflash alse the HBOOT or I need to do something more?
Thanks

ptrigomou said:
Thanks, I'll try. I can't use PASSIMG method because my screen ism't working, or there's other way to do?
When you say all, you refer to use "fastboot flash all FRG33" Doing that I reflash alse the HBOOT or I need to do something more?
Thanks
Click to expand...
Click to collapse
Can you not get your working hboot.img
boot to fastboot by Powering off
Power on by holding power & Trackball (will take you directly to fastboot)
then do "fastboot flash hboot hboot.img"

bagofcrap24 said:
Can you not get your working hboot.img
boot to fastboot by Powering off
Power on by holding power & Trackball (will take you directly to fastboot)
then do "fastboot flash hboot hboot.img"
Click to expand...
Click to collapse
The hboot files i have are hbootxxxxxxxxx.nb0, it's ok?

bagofcrap24 said:
actually ignore me, that wont work for s-on, yeah, u gunna have to go through the pass-img method, completely reverting back to stock and start from scratch
Click to expand...
Click to collapse
Yeah, but my screen is not working, and ADB is not reconizing the phone. I only can send files using fastboot and the screen is not working
There is a method for doing the pass-img method using fastboot?
or maybe the only problem is the HBOOT?

OK, here we go
Download Latest Amon-Ra
http://forum.xda-developers.com/showthread.php?t=611829
copy it to your android-sdk/tools/ folder and rename recovery.img
boot to fastboot, (Power & Trackball)
open up a shell (cmd prompt) and
cd (path to sdk/tools)
fastboot devices (make sure your device is there)
fastboot boot recovery.img
your phone should boot into recovery image
use your method for flashing through adb now if you can
if you can't then try flashing the korean wwe update
hit enable usb-ms
download this, its a korean FRF91 build. it is known to have the updated 0.35.0017 Hoot in it which i believe has support for slcd displays, http://forum.xda-developers.com/showthread.php?t=722281
copy to your SD
hit trackball to disable usb-ms, go to wipe, wipe all data
then goto flash image from zip,
choose the korean frf91 that you just downloaded hopefully when you reboot you will have updated your hboot again

i tried the baove method but i cannot get the recovery .......i have the same problem my display is dead !! i have gone into recovery but i cant see it and hence cant do a wipe and flash the zip can nyone please help me!!!!

Jack gave you the response you need.
Follow the unroot/restore guide from the wiki, using the PASSIMG method:
http://forum.xda-developers.com/wik...des_&_Tutorials#Unroot_.2F_Restore_your_Nexus
The long to the files is on the word "here" on step 2. Use FRG33.
This is done from the bootloader - you don't need to use recovery...
Sent from my Nexus One using XDA App

actualy i cant see anything cant see fastboot menu nor the bootloader! so i will not be able to do from step 2...please can nyone tell me wad to do?? is my fone bricked?? do i have to giv it to htc??

Its HBOOT, not recovery.

Rusty! said:
Its HBOOT, not recovery.
Click to expand...
Click to collapse
What's HBOOT, not recovery?
Sent from my Nexus One using XDA App

[Q] Amon RA (1.7.0-Cyan ->> 1.7.0) - Rooted G1

OK! It's been a while since I started a topic.
I might already know the answer to this, but just to check and see.
I am currently using Amon RA recovery 1.7.0 Cyan, and now I want to change it to the Amon RA recovery 1.7.0.
I downloaded the Recovery Flasher to see if I can flash it that way, it fail to do the backup.
Can I use terminal emulator or boot into console and flash it using the command line from the phone?
Or, do I have to use ADB to flash it?

be careful flashing recovery with Recovery Flasher and adb, especially when you have a different partition layout, i.e. using custom mtd.
The most secure (and for sure working) way: use fastboot, but having the 0013d SPL this means you need to get an engineering SPL first ...

Thanks for the fast response.
AndDiSa said:
be careful flashing recovery with Recovery Flasher and adb, especially when you have a different partition layout, i.e. using custom mtd.
Click to expand...
Click to collapse
I do not have a custom mtd (not to my knowledge). Flash Recovery does not work (get errors), and I am far off at using ADB. Since I no longer have the computer I originally setup ADB with. So these options will be out for me.
AndDiSa said:
The most secure (and for sure working) way: use fastboot, but having the 0013d SPL this means you need to get an engineering SPL first ...
Click to expand...
Click to collapse
Don't know if I want to go through that trouble again just to change from one to the other.
How easy is it anyway to revert back to engineering SPL from 0013d?

It's easy, everything is described in Terry's thread. Read especially the parttitled with "== Important Information about 1.33.0013d =="

Thanks again, that is fairly easy. Before I really jump in (if I do, since this is the only phone I got for now), should I also revert back to radio 2.22.27.08 before I flash the Eng SPL? Sicne ezTerry indicated radio 2.22.27.08, not radio 2.22.28.25.
Sorry for a lot of question, I didn't want to end up bricking my G1.
ezterry said:
If you just temporarily need an engineering SPL (and recovery is working):
(and have SPL 1.33.0013 + radio 2.22.27.08):
1) Nanroid backup
2) Flash (via recovery) ENG SPL 1.33.2005 **
3) do what you need to in the engineering SPL
4) reflash 1.33.0013d as above (install, reboot bootloader, fastboot erase)
5) restore nandroid
** Please remember if you have CustomMTD to remove it before flashing a SPL of Radio from recovery
Click to expand...
Click to collapse

Flashing the orange nbh will erase also your radio, so you will need to flash a new one. Whether you choose 2.22.27.08 or 2.22.28.25 is not important. Both of them will work.
Btw. as long as you use fastboot for flashing radio / spl chances are quite good that you will not brick your phone.
Sent from my Gingerbread on Dream using XDA App

Just changing the background
OK! I come to the conclusion that it not worth the trouble to go through all the steps to change from 1.7.0-cyan to 1.7.0. I can live with the font color.
Is there anyway to just replace the Cyan Android background instead?
Sorry for the trouble.

[Q] [Help] Incompatible Bootloader

Good morning,
I've 'inherited' an Incredible S where an attempt to try a custom ROM has gone wrong. The handset has ARHD 6 ROM installed in it which never gets past the white HTC bootscreen, probably because it hasn't had the BlackRose bootloader installed. Obviously there is no Nandroid to make life easy.
It's on HBoot 2.02, S-on, and the bootloader is unlocked with 4Ext installed.
Quick question: is there a ROM I can install on bootloader 2.2 via 4Ext that will enable the phone to be used, e.g. Virtuous Quattro?
Longer question: Can anybody point me in the direction of a good method to downgrade the bootloader, bearing in mind I can't boot to the ROM. I do seem to have fastboot access and don't mind command line work, I just can't see the best combination of bootloader/ROM that isn't on a dead link.
Alternatively an RUU suitable for the bootloader would be good, but for some reason the list on HTCDev.com doesn't seem to be filtering properly for me on Opera or Iron.
Thanks in advance,
RH

Bossk128 said:
Good morning,
I've 'inherited' an Incredible S where an attempt to try a custom ROM has gone wrong. The handset has ARHD 6 ROM installed in it which never gets past the white HTC bootscreen, probably because it hasn't had the BlackRose bootloader installed. Obviously there is no Nandroid to make life easy.
It's on HBoot 2.02, S-on, and the bootloader is unlocked with 4Ext installed.
Quick question: is there a ROM I can install on bootloader 2.2 via 4Ext that will enable the phone to be used, e.g. Virtuous Quattro?
Longer question: Can anybody point me in the direction of a good method to downgrade the bootloader, bearing in mind I can't boot to the ROM. I do seem to have fastboot access and don't mind command line work, I just can't see the best combination of bootloader/ROM that isn't on a dead link.
Alternatively an RUU suitable for the bootloader would be good, but for some reason the list on HTCDev.com doesn't seem to be filtering properly for me on Opera or Iron.
Thanks in advance,
RH
Click to expand...
Click to collapse
Download CM7.2
Go back to bootloader.
Go to Recovery.
Mount USB storage and transfer CM7.2 to SD card
Now Flash CM7.2
Flash boot.img of CM7.2
Enable USB Debugging after you've booted up (no need for GApps atm)
Continue with downgrade guide (Everything is in sticky roll up thread)

072665995 said:
Download CM7.2
Go back to bootloader.
Go to Recovery.
Mount USB storage and transfer CM7.2 to SD card
Now Flash CM7.2
Flash boot.img of CM7.2
Enable USB Debugging after you've booted up (no need for GApps atm)
Continue with downgrade guide (Everything is in sticky roll up thread)
Click to expand...
Click to collapse
Nice one, thanks. I've downloaded the ROM from http://get.cm/get/2KU and will flash from 4Ext recovery.
The bootloader in in that same zip file, I'll flash as follows:
At ADB prompt:
fastboot flash boot boot.img
Reboot, ROM should load up fine. I spotted the downgrade guide yeterday and it looks very good. I'll give it a shot if CM isn't suitable.
Again, thanks very much.
Time for 2 small questions? How long does it take to flash the boot.img, 10 seconds? 5 minutes? Why does the boot image have to be flashed manually?
Cheers!

Bossk128 said:
Nice one, thanks. I've downloaded the ROM from http://get.cm/get/2KU and will flash from 4Ext recovery.
The bootloader in in that same zip file, I'll flash as follows:
At ADB prompt:
fastboot flash boot boot.img
Reboot, ROM should load up fine. I spotted the downgrade guide yeterday and it looks very good. I'll give it a shot if CM isn't suitable.
Again, thanks very much.
Time for 2 small questions? How long does it take to flash the boot.img, 10 seconds? 5 minutes? Why does the boot image have to be flashed manually?
Cheers!
Click to expand...
Click to collapse
boot.img flashing should take >1s or around that at least...
And the boot.img has to be flashed manually only if you are S-ON. S-ON doesn't give you full clearance to some particular partition that I forget. S-OFF will so when you achieve S-OFF, you will no longer need to flash the boot.img manually

072665995 said:
boot.img flashing should take >1s or around that at least...
And the boot.img has to be flashed manually only if you are S-ON. S-ON doesn't give you full clearance to some particular partition that I forget. S-OFF will so when you achieve S-OFF, you will no longer need to flash the boot.img manually
Click to expand...
Click to collapse
OK, same as my HOX then. Anyway, I've followed your instructions.
Hm, ROM installed and now trying to flash boot.img (from the rom zip).
Fastboot devices shows one device.
Command line states "sending boot (2182 kb)..." but hasn't changed for over 3 minutes. Handset says Fastboot USB and is unresponsive (as expected) at this moment.
I'll leave it until it errors.
RH
Edit: 30minutes later i pulled the usb cable.
"FAILED (status read failed (Too many links))"
Handset is in the same state, i.e.fastboot/hboot and recovery are fine, but ROM doesn't boot and handset stalls at white screen with green HTC letters.
Any ideas why I can't flash the boot.img?

Success! After reinstalling the the drivers and moving the USB cable to another port, the boot.img was successfully pushed, and booted into CM.
I'll now go for downgrading!
thanks for the help.
RH