Related
Hi Guys,
Glad to see WM6 on the Tornado...
Pulled my Cingular 2125 out of the bin and trying to get it upto WM6.
The problem I'm having is that I need to SuperCID it but SPVServices isn't working.
I get the "ALL OK" RAPI init was Successful when I run SPVServices.
Then I click the "CID Tool (Alpha) Link" but it only displays a blank screen.
I have successfully App-Unlocked and installed the Certs.cab
Any help would be appreciated.
What OS no ur PC are you using? FYI, it must be done on XP
OS & IE Versions...
Sorry, forgot to mention...
Windows XP, IE 7. Thought there might be an issue with IE7 so I uninstalled it and tried again with IE 6. Same results.
Try it on other computer ?
Gonna try on my work PC tomorrow (or actually later today).
Just wondered if others had experienced this..
Odd, never heard of a blank screen issue, most errors are saying that it can't write the to the correct memory area or it just wont run at all under vista..
Phil
[EDIT: Good to see you about again kyphur ]
try to supercid with lokiwiz (wizard sim unlock and supercid tool). it works on tornados too
before this make sure that the phone is fully app-unlocked.
ps: skip the enablerapi.cab step
Ah yes, LokWiz my old friend... Wizard was my second HTC Device (Blue Angel being my first).
I used SDA_ApplicationUnlock.exe, is there a sure-fire way to confirm that my Tornado is App-Unlocked?
Success!!
Go figure, worked right off the bat on my work PC, that's just not fair!
Well, thanks you guys have really got your stuff together here.
We'll see how my 12 year old daughter likes WM6 SmartPhone Edition.
I want to flash my current radio rom (1.27.12.11) to 1.27.12.17. but if i open the EXE of the file i get the flash window. and if i click update. it shows me that my current image is version 1.56.404.6 and if i want to update it to 1.00.000.0 ... so whats up? is that normal?
and is this safe to do?
i have an unbranded HTC TyTN 2
Hi
That's normal. The version number relates to the whole ROM, but as you are only flashing the radio that question and version comparison is meaningless.
Just flash and you will see the radio rom version change to the new one and everything else remains the same.
Regards
Phil
its stuck at 0%... my AS connection dissapeared.. what now?
i managed to reboot it correctly, but my AS disconnects at the colour screen... why is that?
On this topic, I want to flash this new radio also, but I don't trust Vista, my Sync connection is always doing crazy things, its my vista that toast.
So can I Flash a Radio just using the SDcard method?
And how?
Thanks
Oh, btw, HI all, my First post, and 1 month with my Kaiser!
And a noob question, whats the difference from a TouchFlo rom to a non-Touchflo?...
Hi
i managed to reboot it correctly, but my AS disconnects at the colour screen... why is that
Click to expand...
Click to collapse
ActiveSync will disconnect at the coloured screen as it isn't ActiveSync in use at that point.
You also likely need HardSPL installed, if you haven't already please see the top threads in this forum for info as to how it all works.
Regards
Phil
Well im trying to install HardSPL. but when it comes to the tricoulour screen i have to unplug and plugin back my USB. AS disconnects as it should. and RUU starts. now it says make connection trough AS.... how? i cant get it to connect anymore and i need to reset my device in order to be connected again..
*edit* nevermind it worked. just ignore and go to update and click update
I had the exact same problem with Windows Vista. Tri-colour screen and Hardspl wouldn't continue.
Everything worked until the Unplug-replug part, and thats where is all stopped.
Had to soft reset device to get it back.
Still haven't figured it out.
Question to Seniors, if my Kaiser is "Free" or "Open", do I need hardSPL?
Or is HardSPL for getting around unsigned roms?
EDIT:
Ok did some reading, and understand HardSPL a bit better now...
One problem was the USB with thought a HUB, and not directly connected. Second problem was Vista not finding some driver, needed a reboot, Strang, ... anyway.
ITs on!!!
I think I got it Flashed on my Kaiser, but how do I KNOW, is there a way to check?
Edit: Figured this out too, My TriColour is now different, the USB was up top, its not lower and it says something about SPL by pof..
Hope you have more luck Imperium, I now have Radio .17 on my Kaiser.
Hi everyone,
I think I may have bricked my Kaiser. I've been following some similar threads but nothing seems to be working to fix the problem.
I was going through the process to flash a new Rom, starting with installing HardSPL following this thread I was. I was having problems, I think because I have the 1.82 ROM version.
Finally, I thought I had HardSPL installed, so I continued to run KaiserCustomRUU.exe. This completed (jumped from 0% to 100%) very quickly. However, I reset my phone and it is now stuck in the tri-color bootloader screen
The screen has the says:
KAIS130
SPL-1.82.0000
CPLD-8
and has the letters RUUNBH in the top right corner.
I've tried removing the battery and resetting, but the phone always goes back to this screen. I've also tried running mtty, but without success. The command 'readconfig' returned a result 'Command error !!!'.
does anyone know of anything else I can try?
Small bit of good news: if I issue the command 'boot' using mtty, my phone boots into my original ROM successfully, with the mtty output:
InitDisplay: Display_Chip=1
No card inserted
OSSIReadBack ++
Read SI data from flash success
tail signature match
Checksum match
UserStorageSIPreload ++
It takes a long time to boot (like a couple of minutes), but it does eventually boots up fine. When I reset, I'm back at the tri-color screen though
If your at the tri-color screen, just reflash a new rom
Im not an expert but when its at the tri colour screen, try to flash Hard SPL again, it should pick it up and flash i believe.
If that goes through ok, then do the same to flash another ROM.
Again no expert at unbricking but its definately worth a try
japher said:
Small bit of good news: if I issue the command 'boot' using mtty, my phone boots into my original ROM successfully, with the mtty output:
InitDisplay: Display_Chip=1
No card inserted
OSSIReadBack ++
Read SI data from flash success
tail signature match
Checksum match
UserStorageSIPreload ++
It takes a long time to boot (like a couple of minutes), but it does eventually boots up fine. When I reset, I'm back at the tri-color screen though
Click to expand...
Click to collapse
Try this.
1.) Open ActiveSync and navigate to File > Connection Settings - Uncheck Allow USB connections.
2.) Download this ROM http://rapidshare.com/files/5781641...dio_sign_22.45.88.07_1.27.12.11_Ship.rar.html and flash it to your device.
That should work for you.
hi alltheway. thanks for the advice!
I don't want to sound ungrateful, but are you sure the above is safe? I just don't want to make a wrong step now and totally screw up the device (now that I can successfully do a manual boot using mtty).
I know you can't guarantee it but is this what others who are stuck in the bootloader have done?
japher said:
hi alltheway. thanks for the advice!
I don't want to sound ungrateful, but are you sure the above is safe? I just don't want to make a wrong step now and totally screw up the device (now that I can successfully do a manual boot using mtty).
I know you can't guarantee it but is this what others who are stuck in the bootloader have done?
Click to expand...
Click to collapse
I had this problem about 2 weeks ago.
I was flashing one of Dutty's Great ROMs and I lost power at the house and shut down my computer when I was 46% done.
I had the same RUUNBH in the top right hand corner. All I did to fix this was flash a factory shipped ROM like the one I provided to you and it worked great. No issue thus far.
Honestly I can't gurantee 100% if this will totally fix your problem but I am 95% sure.
Unless some other users have an answer for you I think this will be your best solution. Regardless of what you do you will have to flash to a new ROM anyways.
Also, I'm a bit dubious on whether i will be able to flash to that ROM. I don't think I have the right HardSPL installed to flash roms (see what my boot-loader screen says in the first post).
I'm no expert though.... obviously
Thanks for all the info alltheway. I'm too tired now (will probably f*ck the thing up even further! ), so I'll try flashing this tomorrow.
Here's some more info I've collected using mtty (my phone is an O2 XDA Stellar):
Code:
Cmd>info 2
HTCSO2___001¯JG±HTCE
Cmd>getdevinfo
GetDevInfo: Get CID OK
HTCSKAIS1300O__0HTCE
New Thread
Read this:
http://forum.xda-developers.com/showthread.php?t=355910
Hi tqm. I've been following that post but as far as I can tell there is no solution there yet.
From what I can tell from that thread (and others), the only way stop the phone booting to the tri-color screen (in RUUNBH mode) is to flash with a ROM that matches the vendor. I think because I haven't been able to install HardSPL properly, my phone's version of SSPL will only load O2 ROMs (could be wrong here, but that's the picture I'm building ). Unfortunately no-one seems to have extracted the ROM from an XDA Stellar :\
I believe alltheway's solution above worked for him because he had HardSPL installed properly. He could load the stock ROM to fix the phone, because his SSPL version allowed different ROMs to be loaded. I'm not certain of this, and I'll probably try his suggested solution when I get home today... but I'm not too confident.
If only there was an mtty command to just get the phone out of 'RUUNBH' mode. I've seen the command 'task 8' mentioned on here, but it doesn't work when I try it. Does anyone know of a list of mtty commands for the Kaiser anywhere?
Definitely flash the original ROM, it will get your device to the default HTC shipped state.
Then sync phone with ActiveSync, install HardSPL again and then flash custom ROM.
I remember i had the same issue but the original rom is a lifesaver
You mean the original HTC ROM? or the original O2 ROM? (what my phone originally came with)
If I don't have one of the HardSPL versions posted on the forums (I believe they never installed properly, which is what caused all my problems I think), will I still be able to flash the stock HTC ROM:
RUU_Kaiser_HTC_WWE_1.56.405.5_radio_sign_22.45.88.07_1.27.12.11_Ship.exe
Basically my questions is: is this stock HTC ROM flash-able to ALL kaisers? (even without downloading/installing HardSPL from the forums)
If not (i.e. I can't flash even the stock HTC ROM), is it expected that if I can't successfully install HardSPL, my Kaiser will only accept O2 ROMS?
japher said:
You mean the original HTC ROM? or the original O2 ROM? (what my phone originally came with)
If I don't have one of the HardSPL versions posted on the forums (I believe they never installed properly, which is what caused all my problems I think), will I still be able to flash the stock HTC ROM:
RUU_Kaiser_HTC_WWE_1.56.405.5_radio_sign_22.45.88.07_1.27.12.11_Ship.exe
Basically my questions is: is this stock HTC ROM flash-able to ALL kaisers? (even without downloading/installing HardSPL from the forums)
If not (i.e. I can't flash even the stock HTC ROM), is it expected that if I can't successfully install HardSPL, my Kaiser will only accept O2 ROMS?
Click to expand...
Click to collapse
IMHO the HTC stock ROM should work even without HardSPL, at least for me it worked fine... but just for sure have your O2 stock ROM by hand.
jaso2005 said:
Im not an expert but when its at the tri colour screen, try to flash Hard SPL again, it should pick it up and flash i believe.
Click to expand...
Click to collapse
I don't thinks there's a way to flash HardSPL on tri-color scrren so far, coz activesync cannot connected to computer
the best way is trying to find the phone's offcial ship rom to flash
No luck trying to flash with the stock HTC ROM:
RUU_Kaiser_HTC_WWE_1.56.405.5_radio_sign_22.45.88.07_1.27.12.11_Ship.exe
After getting to 1%, it reports an error:
Error [294] : Invalid Vender Id
As suspected, looks like this will only accept an O2 ROM Will have to wait until one is available.
Did you try installing HardSPL and then reflashing?
the stock HTC rom will not load onto your kaiser simply because it is still CID locked to O2's CID code. You HAVE to find the O2 rom that your device came with or any O2 ROM and reflash that and you will be good to go. You may also try and flash HardSPL but I dont think its going to work. But remember have a friend or someone on the forum dump and rebuild the O2 rom for you and just reflash the OS.nb or ROM only no radio!
It is very simple to dump and rebuild a rom so if you have a friend that has a kaiser have him over for an hour and dump his
thats your only shot at this point.
URPREY said:
Did you try installing HardSPL and then reflashing?
Click to expand...
Click to collapse
My current ROM version is 1.82. I don't think installing HardSPL has been solved for this ROM version, which I think is where all my problems started. I have tried, but no version of HardSPL (that I've found) will install correctly.
austinsnyc said:
You HAVE to find the O2 rom that your device came with or any O2 ROM... just reflash the OS.nb or ROM only no radio!
Click to expand...
Click to collapse
Thanks for the reply austinsnyc, this is what I'm hoping to do now, I'm watching this thread 'Has anyone dumped the o2 Stellar rom yet ?' closely Maybe I should reconstruct the ROM myself, I'm just a bit worried about arsing that up as well I'd rather someone experienced reconstructed and verified the ROM (on a phone that isn't already messed up).
Out of interest, would you be able to give me a succinct explanation of what is actually wrong with my phone at present? As far as I can tell, the only problem is that the boot-loader is stuck in RUUNBH mode. Has part of the ROM on the phone actually been destroyed?
I'm assuming right now that the point of flashing the O2 ROM is just to make the phone 'finish' a flash and get out of RUUNBH mode. Or is it actually to re-instate something that has been lost?
If it is to reinstate something that's at present lost, is this data definitely part of the os.nb?
If it's just to get the boot-loader out of RUUNBH mode, I'm REALLY gutted that there isn't just a mtty command to do this
Oh yeah, and perceptivepixel.com Ace!
Attached you find all you need to flash cooked ROMs on your HTC Snap 511 (Willow).
The sspl/hardspl are confirmed to work fine on the HTC Willow platform (HTC Snap 511).
It will not work on the HTC Maple platform (Dash3G). Running this sspl on a Dash3G will definitely brick it. Also the HTC CEDAR platform (Ozone) is not supported. For the Dash3G and Ozone I have already developed a sspl/hardspl.
The packages contains a SSPL, HardSPL, patched ROM updater and the original Snap S511 SPL. The package is based on SPL v0.34
Instructions:
1. remove SD and SIM cards (don't forget otherwise the sspl is likely not to work!!)
2. connect your device to your pc with a USB cable and wait until it is synced
3. extract the file "Snap S511 HardSPL by JockyW.zip" and execute "auto.bat"
4. follow all instructions given on screen: first the sspl is copied to the device and executed. You must confirm running JumpSPL on the device: first time you must click Yes to allow it to run, you also must click the trackball to continue execution of JumpSPL. The device display will turn dark and after that the romupdate tool will install the hardspl on your device. (the identification string in the tri-color bootloader screen is "0.34.Hard")
5. to test the sspl and the hardspl you can flash a splash screen
Once the HardSPL is installed on your device you can flash any cooked or original ROM.
A donation for my work would be highly appreciated
Have fun,
JockyW
PS: Moderators please make this a sticky. Thanks.
Donation
Donation has been sent. Thank you for this.
Good work!!!!
Thanks Jocky, sending you good vibes and tips!
Once we install the hardSLP on the sprint snap, which cooked roms can we use? Are we going to need one specially cooked for the snap 511?
dougmwpsu said:
Thanks Jocky, sending you good vibes and tips!
Once we install the hardSLP on the sprint snap, which cooked roms can we use? Are we going to need one specially cooked for the snap 511?
Click to expand...
Click to collapse
Yes, ookba is waiting to get his own phone to get a ROM working... Donations really speed up that process
Should this be stickied like the last few? Maybe consolidate all into one?
Black_V!per said:
Yes, ookba is waiting to get his own phone to get a ROM working... Donations really speed up that process
Should this be stickied like the last few? Maybe consolidate all into one?
Click to expand...
Click to collapse
Anyone care to donate their S511 to me for a week or so?
ookba said:
Anyone care to donate their S511 to me for a week or so?
Click to expand...
Click to collapse
Maybe the next week I'm on vacation... can the phone be service deactivated while you have it?
dougmwpsu said:
Maybe the next week I'm on vacation... can the phone be service deactivated while you have it?
Click to expand...
Click to collapse
Sure it can. Where are you though?
ookba said:
Sure it can. Where are you though?
Click to expand...
Click to collapse
Raleigh, NC. My next vacation isn't till the week of Christmas though, so maybe someone else can step up in the meantime. I'll also be out of the office again for a week in the spring.
first off, thanks so much to Jocky and Ookba for all the work you guys do! but i'm having some issues. i've dont a lot of searching on here and i can't find a solution hopefully someone can help me. i can't get the hardspl to run successfully.
my bootloader screen shows this:
CEDA200
SPL-0.34.0000
MicroP-Willow#C (LED) v58B
i'm using windows 7 (through VMWare on my iMac), everything seems fine until the pop up on the phone, i click the button (the not really a trackball button) and the screen goes black, i lose all connectivity through WMDC and the Rom Utility gets error 266.
If i don't click when the pop up shows on the phone, the Rom Utility will show and then the phone will go into the bootloader with USB written in the white area then i get the error 266 again.
of course there's no sim because it's a Sprint s511, and the sd card is always removed.
what can i do? i'd really love to get 6.5 on there, but i'm at a loss.
The fact that your running on a MAC with VMWare makes me think the issue could be in the connection...
Im not even sure if Win7 works, i could be wrong however. You wouldnt happen to know of anyone that has a WinXP machine would you?
I did try in vmware with XP and Activesync, but it did the same things. I have a Dell that I was gonna make a hackintosh, but I'm gonna throw xp on it and try using that machine. I was thinking it was the vmware too, i guess i just wanted one of you guys (you know, the one's with a clue! LOL) to confirm.
I applied the HardSPL to my snap using Windows 7 and everything went well
robconway said:
I did try in vmware with XP and Activesync, but it did the same things. I have a Dell that I was gonna make a hackintosh, but I'm gonna throw xp on it and try using that machine. I was thinking it was the vmware too, i guess i just wanted one of you guys (you know, the one's with a clue! LOL) to confirm.
Click to expand...
Click to collapse
Thats what it sounds like... Good to know it works on Win7 though SPIK3.
Thanks Black_V!per for responding and all. I did finally get it going! I set up the dell with XP and it actually didn't work at first. I had originally unRARed the package on the iMac and just copied the unarchived folder over to the XP machine, thinking it would save me a download, but it didn't work. So i just dl'd an RAR utility for windows and unpacked the RAR on the xp machine and it worked perfect. originally the Rom Updater said it couldn't find the nbh file. all's well! And i'm loving 6.5!!
Thanks again Jocky and Ookba!!!
robconway said:
Thanks Black_V!per for responding and all. I did finally get it going! I set up the dell with XP and it actually didn't work at first. I had originally unRARed the package on the iMac and just copied the unarchived folder over to the XP machine, thinking it would save me a download, but it didn't work. So i just dl'd an RAR utility for windows and unpacked the RAR on the xp machine and it worked perfect. originally the Rom Updater said it couldn't find the nbh file. all's well! And i'm loving 6.5!!
Thanks again Jocky and Ookba!!!
Click to expand...
Click to collapse
Must have corrupted during the download... Havent seen that since my 56k-days.
Glad to hear that!
First off, I appreciate everyone's hard work throughout this whole process.
Unfortunately I am running into a problem. The auto.bat is able to copy the JumpSPL file and the .nb file to my phone just fine. However once the Rom Update Utility starts the flashing process, the phone shuts off.
I did a hard reset to my phone, and went through the process again. The JumpSPL notice popped up on the screen, but then crashed when I hit OK. I know it crashed because the Windows Error Reporting popped up (which apparently I had disabled before I did the hard reset, so I never was able to tell if it was still running).
So then I manually ran the JumpSPL file. This time the memory box popped up, so I hit OK with the Jump Address at the default 0x00000000. It then asked which SPL file I wanted to use. I chose the .nb that was copied over. Then the Windows Error Reporting screen showed up again.
I'm not sure what is going on, but hopefully the details I just provided will allow someone to figure something out. Thanks.
BTW: My phone is a Sprint HTC Snap S511, and my splash screen is the same as the one posted before:
CEDA200
SPL-0.34.0000
MicroP-Willow#C (LED) v58B
Jaymoon said:
First off, I appreciate everyone's hard work throughout this whole process.
Unfortunately I am running into a problem. The auto.bat is able to copy the JumpSPL file and the .nb file to my phone just fine. However once the Rom Update Utility starts the flashing process, the phone shuts off.
I did a hard reset to my phone, and went through the process again. The JumpSPL notice popped up on the screen, but then crashed when I hit OK. I know it crashed because the Windows Error Reporting popped up (which apparently I had disabled before I did the hard reset, so I never was able to tell if it was still running).
So then I manually ran the JumpSPL file. This time the memory box popped up, so I hit OK with the Jump Address at the default 0x00000000. It then asked which SPL file I wanted to use. I chose the .nb that was copied over. Then the Windows Error Reporting screen showed up again.
I'm not sure what is going on, but hopefully the details I just provided will allow someone to figure something out. Thanks.
BTW: My phone is a Sprint HTC Snap S511, and my splash screen is the same as the one posted before:
CEDA200
SPL-0.34.0000
MicroP-Willow#C (LED) v58B
Click to expand...
Click to collapse
Is your phone applications unlocked? When I did mine it gave me a bunch of errors because it wasn't applications unlocked. Also make sure you remove your memory stick.
SPIK3 said:
Is your phone applications unlocked? When I did mine it gave me a bunch of errors because it wasn't applications unlocked. Also make sure you remove your memory stick.
Click to expand...
Click to collapse
How would I go about checking this?
I remember on my Samsung Ace, before the 6.1 update, I had to install an "application unlocker" that allowed unsigned programs to install. Is this the same thing with the Snap? Also this is the Sprint version, so I don't have a Sim card, or anyway to typically "unlock" this phone.
EDIT: Ah, now I know what you mean. I found the SDA Application Unlock here: http://forum.xda-developers.com/showthread.php?t=563761
The Rom Update Utility finished successfully! Now to move on to the next step... Thank you SPIK3
No problem, glad I can help.
Hi to all. Is there anyone who can help me with HardSPL my snap which shows SPL 1.24. I would like to use some of the cooked roms. Cheers.
rocksford77 said:
Hi to all. Is there anyone who can help me with HardSPL my snap which shows SPL 1.24. I would like to use some of the cooked roms. Cheers.
Click to expand...
Click to collapse
Try ookba's roms, use Auto_1.19 worked for me... If it all goes wrong as we now have a shipped rom you can fall back to SD flash as in this post:
http://forum.xda-developers.com/showpost.php?p=4872255&postcount=78
ibanyard said:
Try ookba's roms, use Auto_1.19 worked for me... If it all goes wrong as we now have a shipped rom you can fall back to SD flash as in this post:
http://forum.xda-developers.com/showpost.php?p=4872255&postcount=78
Click to expand...
Click to collapse
No, it didn't work for me. I thought by now there will be a solid solution to this. Now we are stuck with stock roms as we cannot HardSPL our devices.
SPL 1.24 is hard to hack. Anyone got any solutions??????
rocksford77 said:
No, it didn't work for me. I thought by now there will be a solid solution to this. Now we are stuck with stock roms as we cannot HardSPL our devices.
SPL 1.24 is hard to hack. Anyone got any solutions??????
Click to expand...
Click to collapse
What didnt work?
I ran the Auto_1.19, (it prompted that device wasnt connected a couple of times, then got the prompt on the device to ask if an application should be run, selected yes (using left softkey), then had to use the trackball to select yes (the screen obscures some of the prompt), then screen went black and RUU began upgrade proces..
ibanyard said:
What didnt work?
I ran the Auto_1.19, (it prompted that device wasnt connected a couple of times, then got the prompt on the device to ask if an application should be run, selected yes (using left softkey), then had to use the trackball to select yes (the screen obscures some of the prompt), then screen went black and RUU began upgrade proces..
Click to expand...
Click to collapse
When I use Auto_1.19, i press the track ball on my device, I get an Error message and asks me to send the error to microsoft.
rocksford77 said:
When I use Auto_1.19, i press the track ball on my device, I get an Error message and asks me to send the error to microsoft.
Click to expand...
Click to collapse
Try with the older version if still fails might be worth a hard reset....
Anyone knows if HardSPL for SPL 1.24 is developed yet?
HArder SPL 1.24
Yeah anyone? I have a SNAP with SPL 1.24 running WINDOWS Mobile 6.5 but I cannot for the life of me get any of the JockyW SPL's to work 1.17 or 1.19. I hate these Bloody Telstra / HTC phones, there locking them down so tightly nowdays. Not even the SDA unlocker works.. it tells me the phone is unlockable
SNAP with 1.22 Telefonica
Hi ther,
I´m running with a SNAP from Telefonica with SPL 1.22 and WM6.1 which doesn´t let me install any of the ROMS here. Not even upgrade to 6.5 of original ROM from HTC. It says 294 invalid vender ID.
I have also tried aplication unlocker.. and nothing seems to work.
A few questions... has HardSPL 1.24 been released?
Any ideas to be able to flash a new rom onto this baby...
Thanks
OkiOKi.
I have MAPL110 with SPL-1.24.0000. Successfully flashed by hspl 1.17 and
this ROM - 3VOLUTION SERIES *][WM6.5 STD 21854][Build 3VO.2.50.112509.
succesfully flashed spl 1.25. used hard spl 1.19 through activesync. stuck on tmo load up page then used bootloader then flashed 11.25.09 rom from there.
all went well and my wife has a newish dash for $100