Database Develop

"Mr. Clean" AKU 2.3 ROM - G4 Version (2.24.0001)

Please note, this is a TEST ROM and may not work.
I do not have a G4 version Wizard to test on, so some brave soul with the hardware in question is going to have to give it a try. Be aware, while I have double checked everything and this should work, FLASHING THIS ROM MAY BRICK YOUR DEVICE.
Once this is confirmed working on a G4 version Wizard, I'll update this post.
The contents of this ROM are functionally the same as the standard Mr. Clean ROM. For more information on Mr. Clean please read the original Mr. Clean thread:
http://forum.xda-developers.com/viewtopic.php?t=52775
Download:
ftp://xda:[email protected]/MrClean_RUU_WIZARD_2240001a_AKU23_WWE.zip
Readme:
-------------------------------------------------------------
Mr. Clean AKU 2.3 ROM v2.24.0001a for HTC Wizard (G4 version)
-------------------------------------------------------------
The ROM of choice for tinkerers and hobbyists is back, and this time the big baldy is ready to take on the G4 variant of the HTC Wizard. Because this ROM is designed specifically for Wizard units with the G4 flash chip it WILL NOT WORK on the original Wizard. If you have an original Wizard, you must use the 2.24a version of Mr. Clean.
---------------
WHAT DO I NEED?
---------------
-A CID Unlocked HTC Wizard with a G4 Flash Chip
-Windows PC with a USB port
-ActiveSync 4.0 or higher installed
-MrClean_RUU_WIZARD_2240001a_AKU23_WWE.zip
-------------------------------------------------------
HOW CAN I TELL IF I HAVE A G3 or G4 VERSION FLASH CHIP?
-------------------------------------------------------
There is an easy way to tell which version flash chip you have in your Wizard.
Simply look at your boot screen and check the IPL/SPL version.
2.xx = G3 Flash Chip
2.xx.0001 = G4 Flash Chip
-----------------------------
WHAT DOES CID UNLOCKING MEAN?
-----------------------------
A CID lock normally prevents you from using any ROM aside from an official ROM provided by your carrier/OEM. Trying to upgrade a CID locked device with an unofficial ROM can damage your Wizard. DO NOT try to upgrade your Wizard if you have not CID unlocked it.
If you wish to search for a free solution, please check the forums on http://xda-developers.com. Be aware however, that free solutions are only available for certain ROM versions. As of this writing there are no known free solutions for the G4 series Wizard, but this may change in the future.
A viable alternative to waiting for a free solution is to visit http://imei-check.co.uk. This company charges 20 British Pounds (approx 40 US Dollars) to perform a SIM and CID unlock on your Wizard. It claims to handle all versions of the Wizard hardware, so if you have a G4 version, this may be your only option. It is generally accepted as the place to go for SIM and CID unlocks.
*Note - I have NO affiliation with IMEI-Check. I am simply including the information as a service to the reader.
---------------------------------
HOW DO I FLASH THE Mr. Clean ROM?
---------------------------------
1) Unzip MrClean_RUU_WIZARD_2240001a_AKU23_WWE.zip to a folder on your hard drive.
2) Make sure your Wizard has at least a 50 percent charge on the battery.
3) Connect your Wizard to the PC via the USB cable.
4) Run the program ROMUpdateUtility_Wizard_NoID.exe in the ROM folder.
5) Follow the prompts to update your Wizard.
6) When you get to the UPDATE screen the version listed should be 2.24.0001a_MRC. If not STOP NOW. You have the wrong ROM.
7) Once you start the upgrade, your Wizard will reset to a rainbow colored screen. This is normal.
8) The Wizard then switches to a blank screen with a progress bar. It may pause for a few minutes at 98%. This is normal.
9) Once the update has completed, the Wizard will reset and present you with the initial configuration.
10) Calibrate the touch screen and let the customization option complete.
11) After the customization completes, the Wizard will reboot a final time and the upgrade is finished.
-------------------------------------------------------------------
WHAT IF I HAVE A WIZARD (G3 VERSION) AND WANT TO INSTALL MR. CLEAN?
-------------------------------------------------------------------
If you have a G3 version Wizard, then you need the file MrClean_RUU_WIZARD_224a_AKU23_WWE.zip.

When i reached step 6 of "How to Flash" i get this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
i should not continue right?

Tried to proceed, everything went ok till the "progress bar" part.. Phone turned to rainbow color, and this is what i got:

About to give this ago.. stay tuned!

no joy! I got Error 300 like the poster above me.
Maybe there's something incompatible with the noid version of the uploader that is refusing to let us upgrade?

allo gamescan;
correct if im wrong:
but if u try to install this rom into a g3 wizard a dont see how it could brick it.
because the rom checks the machine chip before flashing as the official roms that include the 2 versions.
so if u flash this rom into a g3 the only thing that not gets updated its the bootloader.....as it would not be compatible.
are you using the g3 update utilitys in the g4 roms?
because it coud be potencialy fatal.
as the haked update utilitys that we can find were made from roms prior to g4.
for the testers;
unless this rom has a 2.5 or above haked update utility u need to have the device cid unlocked because it will be no way u will be able to install it.
regads
faria

faria: my device is fully CID unlocked with the imei-check solution, as I can flash the 2.x versions of the imate and tmobile USA roms on my tmobile UK device.

sporkguy said:
faria: my device is fully CID unlocked with the imei-check solution, as I can flash the 2.x versions of the imate and tmobile USA roms on my tmobile UK device.
Click to expand...
Click to collapse
i wrote above;
unless this rom has a 2.5 or above haked update utility u need to have the device cid unlocked because it will be no way u will be able to install it.
im quite aware that if you have cid unlocked you will be able to install any rom,from any provider. i have flashed my with every possible rom plus my own.

sporkguy said:
no joy! I got Error 300 like the poster above me.
Maybe there's something incompatible with the noid version of the uploader that is refusing to let us upgrade?
Click to expand...
Click to collapse
Do you still have the T-Mobile 2.24 BETA ROM that I had you download the other day? If so, I'd love for you to try a few things.
First, upzip the T-Mobile ROM and the Mr. Clean ROM to two separate folders.
Now, make a new folder and *copy* the Mr. Clean ROM installer files to the new folder.
After than, copy the RUUGetInfo.exe from the T-Mobile folder and overwrite the one in the new folder. Click on the RUU Wizard (NoID) and try to run the upgrade.
If that fails, I want you to copy the RUUGetInfo.exe from the Mr. Clean folder and overwrite the one in the new folder. Now, copy the RUU Wizard from the T-Mobile folder into the new folder. Click on the RUU Wizard (DO NOT click on the NoID version) and try to run the upgrade.
If that fails, I want you to once again copy the RUUGetInfo.exe from the T-Mobile folder into the new folder. Click on the RUU Wizard (DO NOT click on the NoID version) and try to run the upgrade.
What were're trying to do here is track down where the version info is getting conflicted. I suspect it is because the hacked RUUGetInfo.exe is setup to always report a low version of the ROM so that the upgrade utility will allow downgrading. However, if the upgrade utility sees a G3 ROM on the device (which it always will with the hacked RUUGetInfo) it'll freak when you try to flash a G4 ROM to the Wizard. At least, that's what I'm going with right now. By swapping out a "normal" RUUGetInfo, I'm hoping that the upgrade utility will be happy because it will see a G4 ROM on the device and know that it is flashing a G4 ROM. The only "catch" that I foresee with this is that because it will be able to read the true value of the ROM, downgrading to earlier IPL/SPL versions will not be possible.
faria said:
allo gamescan;
correct if im wrong:
but if u try to install this rom into a g3 wizard a dont see how it could brick it.
because the rom checks the machine chip before flashing as the official roms that include the 2 versions.
so if u flash this rom into a g3 the only thing that not gets updated its the bootloader.....as it would not be compatible.
Click to expand...
Click to collapse
Yes. If someone manages to flash this to a G3 based device IT WILL BRICK. The software should prevent the flashing, but if you manage to override the safety check and force the flash, IT WILL BRICK.
It is foolish to the extreme for someone to try to flash this file to a G3 version Wizard.
As I mentioned earlier, I don't believe the flashing utility is the issue, I believe it is in what the RUUGetInfo utility is reporting to the flashing utility since the hacked version of the RUUGetInfo utility reports a fixed version number all the time.
Hopefully with Sporkguy's testing, we'll be able to successfully package a ROM that can be used by owners of CID unlocked G4 version Wizards. Of course, once the specifics are known, then that will also make it easier for others to package up custom ROMs for the G4 version Wizards as well.

thanks for the reply gamescan.
lets crack this....
it is my belive that there is an eazyest way ....
as far as i know the only diference betwin the g3 and g4 devices is the bootloader ipl/spl ,so we can take any rom and remove the ipl/spl ,therefore the rom would be OS+EXTENDED-ROM+RADIO+SPLASH AND HTC LOGO, and so we would be able to install this rom in any chipset version because we would not touch the bootloader and then we would have 1 rom for all ,and avoid confusion ,specialy to newbies.
the proof of this[as you know] is in the newest official roms ,after we take it apart it contains 2 ipl and 2 spls ,so that tells us that apart from the ipl/spl there is nothing diferent about the roms,since the official rom install in in the g3 and g4 chipsets.
forgive me if im wrong.

If you check the prior thread, you will see that did not work. A flash of GSM + Splash + Ext ROM failed with the same error 300.
The only way anything is going to get solved is with testing and careful deduction. Random guessing or untested assumptions will only confuse things.

gamescan said:
If you check the prior thread, you will see that did not work. A flash of GSM + Splash + Ext ROM failed with the same error 300.
The only way anything is going to get solved is with testing and careful deduction. Random guessing or untested assumptions will only confuse things.
Click to expand...
Click to collapse
a just flashed the latest 2.24 rom taken from an official rom that contains the 2 ipl/spls into a g3 wizard without probems[without the ipl/spl].so its not an random guess or untested assumptions. he got the error 300 because the wizard its locked.
i will be posting the rom soon ,i just nedd to finish integrating NETCFv2 into it .this should also work with cid unlocked g4,
godbye.

I'll try the above shortly - i'm just waiting on getting a copy of Sprite backup so I can come back again. (I'm getting tired of reloading all my stuff back onto the device every other day!)
Will let u know how it goes!

gamescan said:
After than, copy the RUUGetInfo.exe from the T-Mobile folder and overwrite the one in the new folder. Click on the RUU Wizard (NoID) and try to run the upgrade.
Click to expand...
Click to collapse
Error 300
If that fails, I want you to copy the RUUGetInfo.exe from the Mr. Clean folder and overwrite the one in the new folder. Now, copy the RUU Wizard from the T-Mobile folder into the new folder. Click on the RUU Wizard (DO NOT click on the NoID version) and try to run the upgrade.
Click to expand...
Click to collapse
Error 238 - File Read
(The UU Cannot open the requested file)
If that fails, I want you to once again copy the RUUGetInfo.exe from the T-Mobile folder into the new folder. Click on the RUU Wizard (DO NOT click on the NoID version) and try to run the upgrade.
Click to expand...
Click to collapse
Error 238 again

Ok, so i've never flashed my device bofore, and i'm dumb and i overlooked the first step of checking to see if i had a 3g or 4g.
I downloaded the program, and updated the rom. It installed, and it loaded up, i saw the pretty MR clean bootscreen (at which point i realized how dumb i was but i looked at the version in the loading screen, and i did say it was 4g, but this was AFTER the flashing of the rom, so i donno if that was just changed cause of hte flashing), and then it started installing the customizations. Then, my mind rests and i chat away for a bit with my friend on aim, and i glance over my phone. Its off, hmm i guess it had to restart, ok lets turn the baby on! umm why aren't you turning on? Huh? No? NOOOOOOOOOOOOOOOOOOOOOOOO!!! MOTHERFU$()*#&(CKER PIECE OF SHS$(T*( AHHHHHHHHHHHHHHHHHHHHHH
Its deAD! It won't turn on! Oh god what have i DONE!!!!!
HELPPPPPPPPPPPPPP
PS i have a tmobile USA version of the MDA vario

f18viper said:
Ok, so i've never flashed my device bofore, and i'm dumb and i overlooked the first step of checking to see if i had a 3g or 4g.
I downloaded the program, and updated the rom. It installed, and it loaded up, i saw the pretty MR clean bootscreen (at which point i realized how dumb i was but i looked at the version in the loading screen, and i did say it was 4g, but this was AFTER the flashing of the rom, so i donno if that was just changed cause of hte flashing), and then it started installing the customizations. Then, my mind rests and i chat away for a bit with my friend on aim, and i glance over my phone. Its off, hmm i guess it had to restart, ok lets turn the baby on! umm why aren't you turning on? Huh? No? NOOOOOOOOOOOOOOOOOOOOOOOO!!! MOTHERFU$()*#&(CKER PIECE OF SHS$(T*( AHHHHHHHHHHHHHHHHHHHHHH
Its deAD! It won't turn on! Oh god what have i DONE!!!!!
HELPPPPPPPPPPPPPP
PS i have a tmobile USA version of the MDA vario
Click to expand...
Click to collapse
Before looking into it being a more serious problem, do you by chance know what your battery charge was before starting this escapade?
The phone won't charge via USB when it's in bootloader or flash mode, and flashing has a decent current draw, so...could it have hit empty?

heh, it does say several times, in this very thread, that this rom is experimental and intended for G4 chips ONLY.
Hell, we've even been discussing why it doesnt work on my G4 device yet, and you still tried it? Brave, man, brave
I'd Probably try flashing it again by putting it into bootloader mode (take out battery, put back in again and press and hold the camera button whilst plugging in USB) - and sticking an older official rom on there.
Best of luck lol

Yeah i don't think brave is the word, dumb and impatient sounds better i think.
Well i don't think its the battery cause it did load, and I calibrated the screen and everything, and then it started installed the customizations, and then it went blank, so it did have a chance to start charging again.
I did only have a 60% charge though, i'm gonna try to sawp a battery a guy at work who's got a similar phone (its not the same, i hope htc uses the same batteries for its models)
At this point, NOTHING WORKS!!!!!!!!!!!!!!!!!!!! No buttons, not plugging in pressing the reset buttons, nada, nothing , zip just a blank dead piece of plastic. I took ou tthe battery countless times, ahh i'm lost
I broke my pretty thing

f18viper said:
Yeah i don't think brave is the word, dumb and impatient sounds better i think.
Well i don't think its the battery cause it did load, and I calibrated the screen and everything, and then it started installed the customizations, and then it went blank, so it did have a chance to start charging again.
I did only have a 60% charge though, i'm gonna try to sawp a battery a guy at work who's got a similar phone (its not the same, i hope htc uses the same batteries for its models)
At this point, NOTHING WORKS!!!!!!!!!!!!!!!!!!!! No buttons, not plugging in pressing the reset buttons, nada, nothing , zip just a blank dead piece of plastic. I took ou tthe battery countless times, ahh i'm lost
I broke my pretty thing
Click to expand...
Click to collapse
Exactly the same thing happened to mine at exactly the same stage (customizations), my battery was at 100% before flashing and have tried another battery too. It was totally dead, no flashing LED's even when left on charge, couldnt get into the bootloader by holding the camera button and plugging in the USB cable either. Luckily it was swapped over for a new one within a few days....
Oh mine was on the other rom the ""Mr. Clean" AKU 2.3 ROM" but the same result.... so put very bluntly, you are buggered

Exactly the same thing happened to mine at exactly the same stage (customizations), my battery was at 100% before flashing and have tried another battery too. It was totally dead, no flashing LED's even when left on charge, couldnt get into the bootloader by holding the camera button and plugging in the USB cable either. Luckily it was swapped over for a new one within a few days....
Oh mine was on the other rom the ""Mr. Clean" AKU 2.3 ROM" but the same result.... so put very bluntly, you are buggered
Click to expand...
Click to collapse
Ughh i don't think i'm going to be able to swap it. This sucks severly. Is there any possible way to access the bootloader? Possible breathe life into this thing?

Cingular 2.26 Aku2.3 w/a2dp FULLY LOADED *BETA* SCREWED ME

I have enclosed my link to the problems I have with this ROM upgrade. I am looking for suggestions other than bitting the bullet to purchase a new phone, or God help me, taking it down to Cingular to do a complete reflash if possible.
Any assistance is highly appreciated.
http://forum.xda-developers.com/showthread.php?t=276651&page=72
Regards,
jlsenter

jlsenter said:
I have enclosed my link to the problems I have with this ROM upgrade. I am looking for suggestions other than bitting the bullet to purchase a new phone, or God help me, taking it down to Cingular to do a complete reflash if possible.
Any assistance is highly appreciated.
http://forum.xda-developers.com/showthread.php?t=276651&page=72
Regards,
jlsenter
Click to expand...
Click to collapse
if you bother to read the posts u would know that the rom contain no boot loader.thats why you ipl i showing 1xxx
put the device into bootloader mode and reflash aofficial rom.
next time before posting post like this do some reading.
did anyone force you to flash this rom or any other?

faria said:
if you bother to read the posts u would know that the rom contain no boot loader.thats why you ipl i showing 1xxx
put the device into bootloader mode and reflash aofficial rom.
next time before posting post like this do some reading.
did anyone force you to flash this rom or any other?
Click to expand...
Click to collapse
Sorry faria, your wrong.....that is not what happened as you have blasted me; for as my ipl was not 1xx as you stated. I was able to go back into the boot and flash back to 2.17. ABTY, I do read and have been doing flashes of all sorts of electronics for more years that I hate to admit to. Don't be so presumptuous. Not every one can be righteous

if the rom read as 1.2 then its not the right rom

Have you tried
flashing an official rom that includes the bootloaders?
If you do this and then reflash with the rom you say screwed you your IPL should update.
This rom does not contain the bootloaders.
You may have to go buy a new battery (or borrow one that is charged at least 50% from a friend)
Start the device in bootloader mode while connected by USB by holding down voice tag and camera buttons while powering on. You should get the RGB boot loader screen with USB in the lower corner.
Flash a FULL 2.xx rom (preferably an official one from your provider), this should upgrade your IPL and SPL correctly. Then you can go back and re-flash this rom and all should be well.
From what you describe it looks pretty much exactly the same as happened to me earlier in the thread you linked. I had to go buy a new battery to get mine reflashed because I played with it so much with conflicting bootloader/OS/Radio versions that it went dead and would not re-charge in this state.
EDIT: Also if you IPL and SPL are different numbers this may indicate that you are not correctly CID unlocked (not 100% sure on this as it hasn't happened to me, but from what I read on these boards this is the impression that I get) If I were in your situation this is what I would do:
Downgrade to Button's 1.05 rom
run Lokiwiz02b and perform a CID unlock
Upgrade to a 2.xx carrier rom (pretty much everyone agrees to go with a carrier rom first)
Then upgrade to a 2.xx rom of your choice.

Zzan is putting you on the right path, yo do need to get your battery charged before you can flash though.
Also, just so you know when flashing cooked roms most of them use a hacked RUU that will always show the currently installed phone rom to be 1.2. This is so that you can freely flash between roms as the RUU will not normally let you flash to a lower rom version.
Regarding your comments to Faria, clam down. Your orignal post in the other thread is a bit jumbled and I can see where it is easy to think you might have been referring to IPL/SPL being 1.2 as you were not very specific.
When posting you will get a lot better help if you give as much info as possible and organize it clearly. For example say that the RUU showed you currently had version 1.2 Rom installed on your device then nobody thinks you are talking about IPL/SPL.
Finally, When you say things like "x's Rom screwed me" you're going to rub a lot of people the wrong way here (especially when the Rom is clearly marked as BETA). Remember that nobody forced you to flash the Rom and if you are as experienced at flashing as you say then you should have understood the risk you are taking every time you flash your device. Now you should to expect that risk to triple when you use anything marked as BETA. Maybe saying "Help, I'm having problems after flashing xxx Rom" would get you more assistance.
Take my advice with a grain of salt and realize that it is worth exactly what you paid for it so I'm not upset if you disregard everything I said.

jlsenter said:
Sorry faria, your wrong.....that is not what happened as you have blasted me; for as my ipl was not 1xx as you stated. I was able to go back into the boot and flash back to 2.17. ABTY, I do read and have been doing flashes of all sorts of electronics for more years that I hate to admit to. Don't be so presumptuous. Not every one can be righteous
Click to expand...
Click to collapse
this is what you posted;
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Cingular 2.26 Aku 2.3 Update - SCREWED ME
I guess I needed a reason to upgrade to the HP6925 as this update screwed me up big time. Everything appeared to be find during the update....just a very long time to reboot and setup. After setup and reboot again, very slow. The telephone function is completely gone. Icon is there, just nothing happens. Additionally appears to be processing allot of STUFF? as the processor seems to be being tasked as the screen taps are very inconsistent. I tried to restore to my 2.17 AKU2 ROM without success. The USB is no longer operative at all. I have tried to use the IR port, but it is too flaky, and bluetooth is bluetooth....no consistency; can't active sink here either. It no longer tells me about the battery, just empty information. No lights to even tell if it is charging in the cradle, or even just a power supply.
What is really bizarre, is when I tried to restore 2.17 for IR, it read the ROM as 1.2.....someone switch the LINKS load???? IR just bombs after it starts to initiate the load. Then have to go through recovery by removing battery.
Like pissing in a can with a 40mph wind :-(
HELP I HAVE TRIED ALL RESOURCES........lucky I backed up all my data, as I would have been SCREWED even more.
jlsenter
sorry. missread ,and i was not blasting you away.
but still u did not read the posts ,otherwize you would know how to restore your device.it was stated several times .
and since u stated that u been flashing all sorts ,im suprised u did not know how to restore you device. or was it the first time in this device?

Thanks Kyphur, Zzan, & Faria
Thanks for the suggestions; as it now make sense to some of anomalies that I saw. I did go back into the boot and re-flash back to 2.17 with success. The whole reason I started on this path to begin with was because 2.17 was not seeing my 2G memory card.....or should I say "not installed" to be more precise. Then after the ill-fated 2.26 install and re-flashing back to 2.17, the 8125 now recognizes the 2G memory. The 2.17 release has been very stable for me and will stay that way......., besides, my pre-ordered 8525 arrives this Friday.
Kind regards,
and personal apology to Faria if I was too FIERY

jlsenter said:
Thanks for the suggestions; as it now make sense to some of anomalies that I saw. I did go back into the boot and re-flash back to 2.17 with success. The whole reason I started on this path to begin with was because 2.17 was not seeing my 2G memory card.....or should I say "not installed" to be more precise. Then after the ill-fated 2.26 install and re-flashing back to 2.17, the 8125 now recognizes the 2G memory. The 2.17 release has been very stable for me and will stay that way......., besides, my pre-ordered 8525 arrives this Friday.
Kind regards,
and personal apology to Faria if I was too FIERY
Click to expand...
Click to collapse
all happy.....

faria said:
all happy.....
Click to expand...
Click to collapse
Group hug?

dcdivenut said:
Group hug?
Click to expand...
Click to collapse
tellytubbys...... lala...poo... ho **** cant remember the others.

What are the basics of installing a custom ROM?

I'm new to this whole custom ROM scene and am dying to put one on my AT&T HTC Tilt. I really want the new features of Windows Mobile 6.1 plus all the tweeks that come with these ROM's.
The problem however is the basics. I've searched around and see people talk about HardSPL, SSPL, JumpSPL, Unlocking SIM, Selecting Correct Radio, and so forth.
Needless to say I need to ask a newb question and that is for a basic explanation of what I need to do to install a custom ROM. From what I understand so far I need one of those SPL programs ... specifically for the ROMeOS v4.1 I need HardSPL. I need to find the correct radio and I may or may not need to unlock my SIM.
Any help is greatly appreciated,
Thanks!

omg are you serious? Everything has already been explained in the wiki so what more do you want? I guess the noobs need it pasted in their personal thread.
There is a reason it says READ BEFORE POSTING.. the ****s already written and waiting for all the noob lazieness in the world.

http://forum.xda-developers.com/showthread.php?t=369282
http://wiki.xda-developers.com/index.php?pagename=HTC_Kaiser#ROMx20.Upgrading
The wiki's are your friends

I am in the same boat dude. Although it is outlined in the wiki (in numerous places), there are way too many updates, and dont use this spl, use this one. This hard spl requires this, pick this radio not that one. And one thing is explained this way, and one is explained that way. I have yet to find one single tutorial that outlines everything in one place. From soft/Spl all the way until you turn the thing on with the new ROM.

Well look at it from this point of view.
Different names and possible builds.
HTC P4550 / HTC TyTN II / Orange & HTC TyTN II / Vodafone VPA Compact V / Vodafone v1615 / SFR v1615 / Swisscom XPA v1615 / T-Mobile MDA Vario III / AT&T Tilt / O2 Xda Stellar / EMobile Emonster S11HT
Some of the carriers
att, rogers, tmobile, orange, ?fido? etc etc (all using somewhat different signals)
OS
6.0, 6.1,
ROMS
hybrids, htc releases, att releases, cooked, hybrids, diamonds, dutty, leo, garmin, alex, etc etc etc
So you have to have a tutorial that encompasses all the variables above and more. Not all Kasiers are the same and not all carriers communicate the exact same.
Personaly I think the info in the wiki/stickys is great and totally useful. Sure you might need to read it 3 or 4 times to piece it all together, but thats because there is so much to know and so many variables.
I live in the middle of Texas and use a tilt (7200 not 7201) I use a specific radio that works for my area. Since I use att and a 6.1 rom I use a specific spl and radio (these are just for 6.1) and I also chose to flash via usb and not SD. So I guess I could write a tutorial on how I hooked my particular phone up but it would only outline for my phone, where it is, with what I have on it.
That is all.

ChumleyEX said:
omg are you serious? Everything has already been explained in the wiki so what more do you want? I guess the noobs need it pasted in their personal thread.
There is a reason it says READ BEFORE POSTING.. the ****s already written and waiting for all the noob lazieness in the world.
Click to expand...
Click to collapse
I am amazed by the tone of some people here. Yes there are Wikis for that, very good ones in fact. But hell, can't you simply provide the link and say it politely? Would it burn your mooth?
Damn, this is community, not a "who knows better and who has more experienced can flagellate a "noob""...
Stop posting if you can't stand it anymore.

In turn,
Why can't you just read the sticky that says, read before you post.
You want to be spoon fed, why should ANYONE link something to you that is out in plain site.
These articles don't write themselves and should be treated with respect.

ChumleyEX said:
In turn,
Why can't you just read the sticky that says, read before you post.
You want to be spoon fed, why should ANYONE link something to you that is out in plain site.
These articles don't write themselves and should be treated with respect.
Click to expand...
Click to collapse
You talk about respect, that's funny . I won't go on polluting the post, I stop this off-topic, it won't lead anywhere.

Respect given where earned.
On post number 1 you're asking a simple question without reading, expecting to not work for what you want.
0 respect.
Write several articles, work for your knowledge, contribute =
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Well, the instructions for flashing your first ROM are pretty straightforward:
1. Flash HardSPL
a. The first thing to do is to pick a ROM you want to flash,
and plug in your device to your computer.
b. The chef (person who makes the ROM) will usually say
which SPL he/she recommends. If he doesn't, you can just PM him.
c. Go to this page and pick the HardSPL that the chef recommends.
A HardSPL Security unlocks your phone, meaning that you can
flash different ROMs than the default shipped ROMs that come pre-installed on your phone.
d. Download the Kaiser-HardSPL-3.xx.zip from the above page and
extract them to a folder on your computer, for example: HardSPL.
e. Now download the attached file in this post (JumpSPLv1) and
extract it to a folder on your computer, for example: JumpSPL.
f. Once you have extracted the three files to a folder, open the folder,
and copy "kaiser_JumpSPL_pof_v1.nb" and "JumpSPL.exe" (no quotes) to
your device.
g. Power down your device, take out your SIM and SD card (if one),
then power back on the device. If it opens an emergency call screen
once restarting, just click the red End key button on your device to
exit and go to the today screen.
h. Open File Explorer, then open JumpSPL.exe on your device, select
the kaiser_JumpSPL_pof_v1.nb, then enter in: "0x00000000" no quotes.
i. Now, if done correctly, you should be at a Tri-color screen and
it should say "USB".
j. Now disable USB connections in Activesync/Windows Mobile Device
Center. To do this, click on settings under Activesync or Windows
Mobile Device Center (depending on if you're running Vista or XP) and
UNcheck "Allow USB connections"
k. Unplug your device, wait 5-20 seconds, then plug your device back in.
l. Remember that folder that you extracted the SPL to? Well, on your
computer, open that folder, then run KaiserCustomRUU.exe.
m. Click Next, Next, then Update. Wait for it to finish, then click Finish.
n. Congratulations! If done correctly, you should have HardSPL flashed
on your device. To confirm this, press and hold the camera button on your
device all the way while pushing the stylus into the reset hole. You should
be at a tri-clor screen (called the bootloader). The second line down should
say "SPL-versionhere.Hard" (no quotes). If it does, you're ready to flash!
If it doesn't, please re-read all instructions.
o. NOTE: You only need to flash HardSPL once unless you revert back to the original AT&T or HTC ROM!​2. Flash the ROM
a. Flashing the ROM is very easy. First, pick the ROM you like, and
download it. Usually ROMs are in a .zip or .exe file.
b. Once the download is finished, extract the .zip to a folder on your
computer. If it is an .exe, just run it.
c. If it was a .zip, just run KaiserCustomRUU.exe from the folder you
extracted the files to, click Next, Next, then Update, then Finish. It it
was an .exe that you downloaded, it should do this automatically. However,
if it doesn't, it should just extract the files for you into a folder. Just follow
the same procedure for a .zip file if it does do this.
d. NOTE: After you flash the ROM, when you get to the whole "Please tap the
screen to begin setting up your Windows-Mobile based device", hard reset by
holding down the two soft keys while pushing the stylus into the reset hole.
You should get to a white-colored screen. Just follow the directions on that
screen and then reboot. This fixes many issues, and is also known to make your
ROM perform at 100%.
e. Congratulations, you should have just flashed the ROM! If not, please
re-read the instructions above.​3. Flash the Radio
a. This is where newcomers tend to become confused. Basically, you just need
a radio that matches the ROM you have. One reason to tell if you do not have
a correct radio is if you have camera issues, and sound issues while talking on
the phone. Just remember: only flash Kaiser radios! If you try flashing a Polaris
radio on your device, chances are you'll brick it.
b. You can flash the radio before or after you flash the ROM. Basically, the ROM
and the Radio just need to match. Chefs sometimes include Radios in their ROM,
in which case you would not need to flash a new one. Just look in the thread of
the ROM you want to flash to see if the chef included it. If there is an included
radio, you can skip the rest of the steps. If the chef does not include a radio,
he/she will usually recommend one.
c. You can download kaiser radios from here. Just download the
one your chef recommends. If your chef does NOT recommend a radio,
just PM him/her and ask which radio he/she recommends. Many
people prefer 1.58.25.17 for its awesome battery life. 1.58.25.17 also
works on many newer ROMs.
d. So, just for the sake of the rest of these steps, we are going to assume
that you have flashed a newer ROM and are now going to flash Radio 1.58.25.17.
e. Now, just download 1.58.25.17 from the link I posted above (should be a .zip),
extract the files to a folder on your computer, run KaiserCustomRUU.exe, click
Next, Next, Update, then Finish.
f. Congratulations, you have flashed your radio and you are completely done.
If, for example, you are experiencing issues with the camera and phone, just flash a
different radio using the same method as posted above.​
That's it.
And remember, please read the Wiki, Stickies, and G.W.E.N.I. for the answers to most of your questions. Or, you could use the wonderful Search functions of this forum.
Hope this helps and good luck

A surely as you wrote that, there will be a thread started in a week asking the same thing. Have copy and paste ready..
That was nice of you though.

ChumleyEX said:
Have copy and paste ready..
Click to expand...
Click to collapse
haha I was thinking of the exact same thing, except I have this page bookmarked instead of copy/paste ready

I appreciate the detailed steps, I look forward to getting rid of the default AT&T crap and installing WM6.1.
I apologize for asking the obvious questions of the most basic nature. Everything I read on these forums tells me to do one thing one way or another, and if I do it a certain way I'll brick my phone. All pieced together information seems to be contradicting each other. A simple link to the wiki, or a known to be good already written guide is all I was really asking for. I don't know what SPL's are or if I have to have an unlocked phone before I install this stuff.
Also, half the time "Read Before Posting" topics say the same thing, which is to search the forums for your answer before asking, which I did and found a bunch of confusion.
P.S. Ali G spells it "Respec"
Thanks,
Patrick

basic elements to the phone
cid unlock the phone, now able to use any carrier (att t-mobile)
spl: newer rom (os or build number) newer version of spl needed. this gets flashed and only need to do it once unless you want a newer version, or are going to turn the phone in for service
rom: flashed all the time, can do it 4-5 times a day or or once a month or never. Like windows xp, upgraded or tweaked to ones liking. try them all see whet you like. there is no best, just the best for you.
radio: flashed, mostly comes with a rom, find the one that you like for your area and phone. save it. if a new one comes out try it, then flash back if you don't. I have had some issues with that and will hard reset, and start over.
The phone is quad band, (am fm vhf uhf, Just an example,) will work anywhere, some radios will work better in different markets.
Back all your stuff up, keep a copy of your cabs (programs) on you sd card.
pm me if you think you need more, or don't want to get flamed.
I don't like reading super long post of great job or will flash later.
but searching or posting in the relevant rom thread is always better
Ok some times I do like to read the flames

The link to the wiki was in the thread that says read first..
And please provide some of the contradicting information you came across, we need to get rid of it or correct it.

mbarvarian,
That was the most useful post I have seen. Rather than get rude like your typical "know it all's", and waste responses rather than help someone gets kudos from me. Thanks for taking the time to outline the steps, it was very useful for newbie like myself.

ebayork said:
mbarvarian,
That was the most useful post I have seen. Rather than get rude like your typical "know it all's", and waste responses rather than help someone gets kudos from me. Thanks for taking the time to outline the steps, it was very useful for newbie like myself.
Click to expand...
Click to collapse
Funny. Typically the ones who defend in these circumstances are prior offenders themselves. After reviewing all of your prior posts, they almost perfectly match this OPS questions. THIS IS THE REASON WE GET IRRITATED! We answered your posts, we answered the 400 other posts behind you...... should we REALLY be expected to answer all the posts forever? Its not difficult. Go to the first page for our device..... the Kaiser WIKI.
Here you will learn:
What is a ROM?
A Rom is an OS ( like XP , or VISTA , or MACOSX )
What s a radio?
A radio is the firmware that controls the base operation of the cellular phone. I.E. the camera/phone/sound
What is SPL?
SPL is your bootloader.... kind of like a BIOS. You MUST change this to a HARD-SPL in order to install a NON OEM BRANDED ROM. If you READ, Jump-SPL allows you to install HARDSPL. Once you have HARD-SPL installed, then you can continue to load custom OS/Radio without worry of bricking your phone.
If you READ ALL THE COOKED ROMS..... and by ALL i DO mean ALL...... the ROM COOKER TELLS YOU WHAT RADIO/SPL to use with HIS Cooked ROM. READ THE FIRST PAGE OF HIS ROM'S WIKI!!!!!!
All of this is on the VERY VERY VERY VERY FIRST PAGE
http://wiki.xda-developers.com/index.php?pagename=HTC_Kaiser
ITS NOT THAT WE HATE NOOBS, we HATE helping people who refuse to even look for basic terms before jumping to the " Start new thread " and dont use the "Search forum" buttons.
As stated before, this is covered about 100 times already........
Chumly and Jimmy, you guys have a lot more patience with these people than I do LOL.
**EDIT**
P.S.
If there IS contradicting information PLEASE tell us so we can have mods fix it.

ebayork said:
mbarvarian,
That was the most useful post I have seen. Rather than get rude like your typical "know it all's", and waste responses rather than help someone gets kudos from me. Thanks for taking the time to outline the steps, it was very useful for newbie like myself.
Click to expand...
Click to collapse
thanks man, glad it helped. i also find it annoying when someone posts a post only to read the wiki, or read this or that and is completely unhelpful. althoug the wiki does have some great information

mbarvian said:
thanks man, glad it helped. i also find it annoying when someone posts a post only to read the wiki, or read this or that and is completely unhelpful. althoug the wiki does have some great information
Click to expand...
Click to collapse
I assure you....... ALL of your answers are in the WIKI.

Touch pro2 stuck at tricolor bootloader screen

OK i tried getting help at the hardspl thread but just getting a generic answer.
I was wondering if there is anyone who can point me in the right direction or hold my hand so to say with step by step instruction on possibly fixing the problem i currently have.
here is what i had performed to get to where i am at right now.
I had my phone hardspl. been flashing different roms then stayed with one. then today my phone wasnt able to activesync and the usb wasnt being recognized so i wasnt able to activesync, or use phone as a disk drive or internet sharing but the phone would still charge through usb. i called tmobile they are sending me a phone ill get it in about a week in the meantime i need to make this one back to stock.
So i downloaded and flashed the tmobile stock rom which i found here....http://forum.xda-developers.com/showthread.php?t=550975 after that was installed.
I then downloaded the tmobile splash screen which was provided in a link found here... http://forum.xda-developers.com/showpost.php?p=4592520&postcount=163
i then downgraded the radio.
after doing all that all what was left was to change the hardspl to relock to spl. well being that my usbport was not being detected by computer to use activesync being that your phone needs to be synced in order to use the rhodiumsplrelocker.exe program. so i ran the program and when the files showed up from the program i took the RUU_signed.nbh file and moved it into another folder and renamed it to rhodimg.nbh and placed on my memory card thinking this would relock the phone using the sd card loader method..
I ran it and then the phone frooze. it rebooted and when it did this is what shows up
When i try to put the stock rom image file back on my memory card as i was told to do... after the first screen with the tricolor it then goes into a second screen with the words loading and thats it...i let it run like this for 20minutes and there was no change. heres what that screen looks like
is there anyone who may help me i would appreciate it greatly. ill be willing to make a donation to you for a solution that really works.

Connect to your device via MTTY (delete the NBH on your SD for good measure), and in the MTTY terminal, simply type this command:
Code:
[FONT=Courier New][B]set 16 0[/B][/FONT]
After that, it should boot back to Windows Mobile just fine. Good luck

DaveTheTytnIIGuy said:
Connect to your device via MTTY (delete the NBH on your SD for good measure), and in the MTTY terminal, simply type this command:
Code:
[FONT=Courier New][B]set 16 0[/B][/FONT]
After that, it should boot back to Windows Mobile just fine. Good luck
Click to expand...
Click to collapse
can you send me the mtty program or send me a link or direct me to where i can get this mtty program much appreciated
edit: i tried mtty program and its not working. the program needs to access the usb port on phone. the first problem i was having was that the computer was no longer to read the usb port on phone due to a problem with the usb hardware. so any fix that may require a usb to computer connection may not work...if theres a way to put a file on the memory card that would work to fix or to have it boot to windows without going into the loader all the time that would help.

I just looked at the pictures in the first post, and that SPL is the shipping SPL, and not HardSPL. Therefore, it doesn't matter if the phone boots or not, since you've made everything stock, and they have nothing on you. You can just say that your phone started doing this and you don't know why, and if you play dumb, they'll have no reason to suspect otherwise.

you need to find a computer with a working usb port. Mtty is your best way out of this. It's a pretty simple problem that you have actually. mtty can be quirky so don't give up!

Sleuth255 said:
you need to find a computer with a working usb port. Mtty is your best way out of this. It's a pretty simple problem that you have actually. mtty can be quirky so don't give up!
Click to expand...
Click to collapse
I have the same problem and the issue isn't our computer is the actual MINI USB port on the phone that no longer works

Um, i hate to tell you, but that same thing happened to me. I got it all back to stock, called HTC , sent it in for repair, they kept it for 45 freeking days. I just got it back. Cost $20.
Good luck. I tried everything before sending it in. Nothing worked.

Im just wondering if sending it to T-mobile that way would cause a charge to me

usb not working
ok this is for everyone who has tried to help and i really do appreciate it. but one thing people seem to keep forgetting about is you have to remember the USB PORT on the phone has MALFUNCTIONED meaning it doesnt work anymore. So for those of you who have come up with try using MTTY program...well the thing is you need to have a working USB in order for that to even work. so as i have mentioned before is there any program out there that would help by trying some rebooting program you can install on the memory card or what would really help is if the people who made the hardspl and the splrelocker would make a splrelocker program that can all be run off of the memory card with no need for the USB port because if and when that usb port is no longer working and you need to return for warranty reasons then it would be a great help being you can still relock the spl even with a non working usb port.

ok, so everybody started out not being able to activesync due to a malfunctioning mini-USB port.
If this was the case, how was anyone able to downgrade the spl in preparation for a return.... which normally requires a working MiniUSB connection?
Are you absolutely sure this isn't the (more common) PnP-doesn't-recognize-the-port issue?

usb problem
Sleuth255 said:
ok, so everybody started out not being able to activesync due to a malfunctioning mini-USB port.
If this was the case, how was anyone able to downgrade the spl in preparation for a return.... which normally requires a working MiniUSB connection?
Click to expand...
Click to collapse
when i first received the phone ... yes the usb port was functioning well and i was able to hardspl my phone... and everytime i would flash a rom i would put the rhodimg.nbh file on the root of my memory card and do the hold volume button down and hit the reset button allowing me to boot to the tricolor screen without the need for activesync or usb to flash a rom. during the use and life of my phone the usb port malfunctioned maybe from wear and tear who knows...so even with the usb dying im still able to flash roms to my phone through the memory card which i could use a memory card reader to put the rhodimg.nbh file onto and then put memory card into phone and reboot the phone while holding down the voldown button still letting me access the bootloader screen without the need for usb. so my thing is if a problem develops during this process how do you fix it when the usb no longer works.

So your SPL isn't downgraded then? That would make sense given the problem you cite. I'm hoping you say that it is because that means there's still hope b/c I don't know of a way to do the downgrade from SD. The only way you can communicate with the BL is through the USB port afaik.

Sleuth255 said:
So your SPL isn't downgraded then? That would make sense given the problem you cite. I'm hoping you say that it is because that means there's still hope b/c I don't know of a way to do the downgrade from SD. The only way you can communicate with the BL is through the USB port afaik.
Click to expand...
Click to collapse
Correct me if im wrong, the screen where he is stuck (See screenshot post #1), looks like original SPL? If so, how can T-Mobile even notice it has been reflashed? What im trying to say is, if he just play dumb, he should get warrantee just fine, since it looks all original to me.

good point... looks like yours is one option. Still perplexing how the downgrade could have occurred with a bad miniUSB port... There are some real quirks getting mtty to connect. Some of them had to do with getting USB active on the BL screen... I haven't used the utility since I had my TyTN in the days before soft/hardSPL however.

not sure where you ended up with this, but I ran across the following thread and thought about your problem:
http://forum.xda-developers.com/showthread.php?t=540290
It shows the many things that are needed for successful USB tri-color connect with mtty.

Sleuth255 said:
not sure where you ended up with this, but I ran across the following thread and thought about your problem:
http://forum.xda-developers.com/showthread.php?t=540290
It shows the many things that are needed for successful USB tri-color connect with mtty.
Click to expand...
Click to collapse
i have same problem
my touch pro 2 stuck at tricolor bootloader screen
and i have mtty1.42 soft
what i do or how i can slove my problem
plz help
B.R.

mobitec said:
i have same problem
my touch pro 2 stuck at tricolor bootloader screen
and i have mtty1.42 soft
what i do or how i can slove my problem
plz help
B.R.
Click to expand...
Click to collapse
what is the SPL version?

cmonex said:
what is the SPL version?
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
check plz
thx

plz any help
????

mobitec said:
plz any help
????
Click to expand...
Click to collapse
wow that was a big photo...
ok, well, do you have a GSM tp2? or a CDMA/GSM one? because it says RHOD500 modelid on the screen but I'm not convinced that you actually have a CDMA worldphone...
if you are not sure, then tell me what carrier the device is from, that'll give me a hint if it's GSM or CDMA/GSM.

[SOLVED] Extraction Problem for NoDo Radio (have screenshot)

After I downloaded the NoDo radio for my phone from here http://forum.xda-developers.com/wiki/HTC_HD7/Radios I go to extract the files and got a WinRAR Diagnostics window showing 'Error- Operation failed'. Is this a big deal? I've attached a screenshot. Thx

Momomuffins said:
After I downloaded the NoDo radio for my phone from here http://forum.xda-developers.com/wiki/HTC_HD7/Radios I go to extract the files and got a WinRAR Diagnostics window showing 'Error- Operation failed'. Is this a big deal? I've attached a screenshot. Thx
Click to expand...
Click to collapse
make sure you have the latest version of WinRAR.
i used a new(er), better compression type with all of the Radios.
if that doesn't work, i suggest 7-zip or ExtractNow.

sh4d0w86 said:
make sure you have the latest version of WinRAR.
i used a new(er), better compression type with all of the Radios.
if that doesn't work, i suggest 7-zip or ExtractNow.
Click to expand...
Click to collapse
Genius that was is....thaaaank you! Onward I go!

Momomuffins said:
Genius that was is....thaaaank you! Onward I go!
Click to expand...
Click to collapse
welcome, glad to hear that worked.

New Roadblock..."Rapitool has stopped working"
I was following Step #13 here http://forum.xda-developers.com/showthread.php?t=1295068.
Repro Steps:
- In the stock folder of the radio file I double clicked on the file and chose to open with HD7_RUUWrapper00 like the instructions say.
- Went thru the couple screens of the tool and launched the action then received the error that Rapitool has stopped working....what now?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Momomuffins said:
I was following Step #13 here http://forum.xda-developers.com/showthread.php?t=1295068.
Repro Steps:
- In the stock folder of the radio file I double clicked on the file and chose to open with HD7_RUUWrapper00 like the instructions say.
- Went thru the couple screens of the tool and launched the action then received the error that Rapitool has stopped working....what now?
Click to expand...
Click to collapse
instead of opening with...
move SPL_Signed.nbh into the task00 folder then run ROMUpdateUtility.exe.

sh4d0w86 said:
instead of opening with...
move SPL_Signed.nbh into the task00 folder then run ROMUpdateUtility.exe.
Click to expand...
Click to collapse
Still get the 'rapitool as stopped working error' but now with a different error screen in the actual program. I tried doing Run as Admin since this is pc is running crap Vista but that didn't make a difference (Run as admin sometimes fixed crashing issues with Blackberry's desktop software on Vista...was worth a shot =/...I hate Vista but this isn't my PC, thankfully LOL)

Momomuffins said:
Still get the 'rapitool as stopped working error' but now with a different error screen in the actual program. I tried doing Run as Admin since this is pc is running crap Vista but that didn't make a difference (Run as admin sometimes fixed crashing issues with Blackberry's desktop software on Vista...was worth a shot =/...I hate Vista but this isn't my PC, thankfully LOL)
Click to expand...
Click to collapse
do you have the device in the Bootloader?
if that is so...
try re-downloading both the Radio and task00.

sh4d0w86 said:
do you have the device in the Bootloader?
if that is so...
try re-downloading both the Radio and task00.
Click to expand...
Click to collapse
Yep, the rainbow looking screen is up and USB is displaying in the white section. I'm plugged straight into the PC but I'm going to try another USB port. I'm running off the front since the cord is kinda short. I know it's usually better to run off the back. I'll keep you posted of course

Momomuffins said:
Yep, the rainbow looking screen is up and USB is displaying in the white section. I'm plugged straight into the PC but I'm going to try another USB port. I'm running off the front since the cord is kinda short. I know it's usually better to run off the back. I'll keep you posted of course
Click to expand...
Click to collapse
No dice on the port change, checked to make sure Power Mgmt to all root hubs was off too....re-downloading I guess D: Gahhh what an A**pain LOL Anti-virus is ESET NOD32...it usually doesn't give any issues but I'll disable it before downloading just to eliminate that variable. Be back in a bit....
**EDIT** Just a thought...the fact that I upgraded my phone out of the box to Mango manually couldn't possibly be causing this???

Momomuffins said:
No dice on the port change, checked to make sure Power Mgmt to all root hubs was off too....re-downloading I guess D: Gahhh what an A**pain LOL Anti-virus is ESET NOD32...it usually doesn't give any issues but I'll disable it before downloading just to eliminate that variable. Be back in a bit....
**EDIT** Just a thought...the fact that I upgraded my phone out of the box to Mango manually couldn't possibly be causing this???
Click to expand...
Click to collapse
nope, Mango update won't be a cause of issue.
also, you needn't keep posting screenshots, just need to know Error numbers.
also, is WMDC/Activesync installed?
if not, this could be the reason for the Rapitool error.

It's still crashing after re-downloading...and about to get on my last nerve...

sh4d0w86 said:
nope, Mango update won't be a cause of issue.
also, you needn't keep posting screenshots, just need to know Error numbers.
also, is WMDC/Activesync installed?
if not, this could be the reason for the Rapitool error.
Click to expand...
Click to collapse
Sorry saw your post as my went up...
I haven't seen anything referencing the WMDC/Activesync. Where do I look for that (i'll be looking in the forums while waiting for your reply) ? 10-4 on the screenshots...just figured it'd help to see exactly what I'm seeing.
**EDIT** Duh I know what Activesync is...just took minute to register. Don't see it installed on here so I'll get that. Pretty sure it was uninstalled when we were messing with Blackberry's in the past bcs Active Sync was something else that interfered with Blackberry desktop at one point in time. I used to work for RIM tier 3 support so we (We=my friend that still works there and I) have probably gotten rid of a few things needed for WP7 stuff that wasn't necessary for Blackberry...but anyway...it's downloading...

Momomuffins said:
Sorry saw your post as my went up...
I haven't seen anything referencing the WMDC/Activesync. Where do I look for that (i'll be looking in the forums while waiting for your reply) ? 10-4 on the screenshots...just figured it'd help to see exactly what I'm seeing.
**EDIT** Duh I know what Activesync is...just took minute to register. Don't see it installed on here so I'll get that.
Click to expand...
Click to collapse
I had the same problem. I didn't have WMDC installed. When you install it the issue should be resolved. sh4d0w86 made a great guide, he just forgot a tiny detail

KayxGee1 said:
I had the same problem. I didn't have WMDC installed. When you install it the issue should be resolved. sh4d0w86 made a great guide, he just forgot a tiny detail
Click to expand...
Click to collapse
hadn't forgot about that 'tiny' detail. just placed it in the wrong step. going to change it right now.
edit.
changed from Step 19 to Step 05.
Momomuffins said:
Sorry saw your post as my went up...
I haven't seen anything referencing the WMDC/Activesync. Where do I look for that (i'll be looking in the forums while waiting for your reply) ? 10-4 on the screenshots...just figured it'd help to see exactly what I'm seeing.
**EDIT** Duh I know what Activesync is...just took minute to register. Don't see it installed on here so I'll get that.
Click to expand...
Click to collapse
WMDC is Windows Mobile Device Center. WMDC is the successor to Activesync.

sh4d0w86 said:
hadn't forgot about that 'tiny' detail. just placed it in the wrong step. going to change it right now.
edit.
changed from Step 19 to Step 05.
WMDC is Windows Mobile Device Center. WMDC is the successor to Activesync.
Click to expand...
Click to collapse
Ahhh and I was about come back here to post that I just read there's no Active Sync for Vista but there's WMDC LOL What a way to spend my entire Saturday...wheee! Off to download that now...

Success...wewt! Step 14 is complete and the phone is back up...moving on...question though..."Repeat step 1, 2 and 5"? Do this all over again? Sorry brain is frying...I guess that's if I want another radio? Figured HSPL was next...I'll shut up now
(**Ya know...had I read Step 2 on the 2nd screen (I think) of the update tool I would've known about the Active Sync thing...it says makes sure you have a connection with it Patience...must get some LOL)