Database Develop

Forcing Bootloader Mode

Maybe some of you are already aware of this procedure, maybe not.
Anyway, it worked for me and I decided to share how to do it. Simple.
This procedure should only be used in case you really need enter into a bootloader mode and all other ways to do it has failed! Hold Camera button is one of these I am mentioning.
My Wizard was almost bricked at that time and after I speak with an I-mate technical guy, I got the following:
1. Make sure your i-mate™ K-JAM is not Connected to the PC and remove the dummy card or SD/MMC card
2. On your Desktop PC, open Microsoft ActiveSync, then go to File >Connection Settings >Remove the Selection from “Allow USB Connection with this desktop computer”
3. Reconnect your i-mate K-JAM to the Desktop PC using the USB Cradle and the Charger MUST be Connected to the Cradle (Don’t use the IrDA or Bluetooth for the Upgrade)
4. Run the Upgrade again and it will work fine without any problems.
While upgrading, the ActiveSync program will not go on, however the upgrade is running.
Hope it helps!

this realy worked for my (ex)bricked dutch tmobile mda vario !!!!
tip: REALY make shure that there is no wcescomm.exe running all the time and realy remove the sd card else is nogo
btw: my wizard is CID locked! and works like a charm

Thanks buddy!
I'm happy that worked for ya!
Take care!

I'm having a problem
The power went out as I was upgrading my Wizard (Cingular) so now it just turns on at the boatloader screen. I've tried running updates while it was in this screen (it did show the "USB" in the white bar) but most of the time it tells me there is a connection error. Even if I kill Activesync, I notice that when I run the update utility it still runs Activesync. I've tried disabling the USB connection but still get the connection error.
The only time I haven't gotten the connection error was twice it asked me to update but then told me I had the wrong file. This only happened when I tried "upgrading" to 1.05 as I was trying to start again. After it tells me that if I try running it again it gives me the connection error.
Any ideas?

Hi!
Have you already flashed your device once?
Which ipl/spl do you have?
I had problems over 1.05 ROM in the beggining.
If you stuck on bootloader mode, that's a good signal your device is not bricked.
I'd recommend you to disable activesync as you did and reflash it again! Check also if your device is CID unlocked! Search for a thread in the xda developers root.
Try to upgrade to ipl/spl 2.26 first and later to others you want.
Regarding the old file error...can be related to a missing file called enterbootloader.exe.
Hope it works for ya!
Take care
Ironman273 said:
I'm having a problem
The power went out as I was upgrading my Wizard (Cingular) so now it just turns on at the boatloader screen. I've tried running updates while it was in this screen (it did show the "USB" in the white bar) but most of the time it tells me there is a connection error. Even if I kill Activesync, I notice that when I run the update utility it still runs Activesync. I've tried disabling the USB connection but still get the connection error.
The only time I haven't gotten the connection error was twice it asked me to update but then told me I had the wrong file. This only happened when I tried "upgrading" to 1.05 as I was trying to start again. After it tells me that if I try running it again it gives me the connection error.
Any ideas?
Click to expand...
Click to collapse

My device is unlocked as I've been trying different ROMs as of late. I had gone back to the Cingular 2.25 ROM for a couple days to sort some things out and was going to flash Farias AKu 3.3 when my power problems happened. My Current IPL/SPL is 2.25
I've tried flashing the TMobile 2.26 but keep getting connection errors. In fact, I've tried flashing with every ROM I have pdviet 3 and 4, CIngular 2.25, TMobile 2.26 and Custom 1.05. Everything (except twice in the custom) gives me connection errors.
Any other trick I can try?
BTW, I used to live in Sao Paulo years ago...
Edit: OK, so I tried the 2.26 TMobile ROM after I typed this and it worked!! I'm back up but I was having trouble with that ROM beause of some incompatibilities with Cingular. I'll go back to Cingular's ROM and play it safe for now.
I believe part of my problem was I kept trying different updates one after the other. Now that I think back, the 2 times I got the update to almost work was after I turned off the device and turned it on again, which is what I did this time around also.

I had the same problems as mentioned by Ironman before. I followed the steps and with a few slight changes, I managed as well to "unbrick" my wiz. THANKS A LOT for the great step by step manual!!!
Still I wanted to know WHY i bricked my device:
I was trying to upgrade to the underground WM6 ROM. I got the same situation as ironman:
Quote:
The power went out as I was upgrading my Wizard (Cingular) so now it just turns on at the boatloader screen. I've tried running updates while it was in this screen (it did show the "USB" in the white bar) but most of the time it tells me there is a connection error. Even if I kill Activesync, I notice that when I run the update utility it still runs Activesync. I've tried disabling the USB connection but still get the connection error.
The only time I haven't gotten the connection error was twice it asked me to update but then told me I had the wrong file. This only happened when I tried "upgrading" to 1.05 as I was trying to start again. After it tells me that if I try running it again it gives me the connection error.
Unquote
I then followed the instructions by epimazzo as written above. I also tried the T-Mobile ROM 2.26 which was not working for me. PANIC!!!! Error messag was that I had the wrong Vendor ID. THerefore no upgrade to TMob 2.26 was possible. I tried it then my original qtek ROM in my language and see it worked!!! This IMHO means that I did not put the device in a proper IPL1.xx and SPL 1.xx status which is required for a clean system in irder to unlock it! So if it is bricked, try your native AKU2 ROM and make sure you unlocked it properly. Maybe you have to run the 1.05 ROM for a second time after the unlocking.
I hope this helps you guys.

Sounds great to hear that!
I had play around with pdaviet3, underground and another ROM just today without any problems at all. I don't think that this is the case. Now you get your device back to normal, try to reflash it again. Hope it works this time!
BTW,...São Paulo is a nice city. Thanks! Let me know if you decide to come here!
Take care
Ironman273 said:
My device is unlocked as I've been trying different ROMs as of late. I had gone back to the Cingular 2.25 ROM for a couple days to sort some things out and was going to flash Farias AKu 3.3 when my power problems happened. My Current IPL/SPL is 2.25
I've tried flashing the TMobile 2.26 but keep getting connection errors. In fact, I've tried flashing with every ROM I have pdviet 3 and 4, CIngular 2.25, TMobile 2.26 and Custom 1.05. Everything (except twice in the custom) gives me connection errors.
Any other trick I can try?
BTW, I used to live in Sao Paulo years ago...
Edit: OK, so I tried the 2.26 TMobile ROM after I typed this and it worked!! I'm back up but I was having trouble with that ROM beause of some incompatibilities with Cingular. I'll go back to Cingular's ROM and play it safe for now.
I believe part of my problem was I kept trying different updates one after the other. Now that I think back, the 2 times I got the update to almost work was after I turned off the device and turned it on again, which is what I did this time around also.
Click to expand...
Click to collapse

It seems you got the idea!
You did the right thing! Sometimes, use the official ROM can solve many issues out there!
Keep walking!
enlite_de said:
I had the same problems as mentioned by Ironman before. I followed the steps and with a few slight changes, I managed as well to "unbrick" my wiz. THANKS A LOT for the great step by step manual!!!
Still I wanted to know WHY i bricked my device:
I was trying to upgrade to the underground WM6 ROM. I got the same situation as ironman:
Quote:
The power went out as I was upgrading my Wizard (Cingular) so now it just turns on at the boatloader screen. I've tried running updates while it was in this screen (it did show the "USB" in the white bar) but most of the time it tells me there is a connection error. Even if I kill Activesync, I notice that when I run the update utility it still runs Activesync. I've tried disabling the USB connection but still get the connection error.
The only time I haven't gotten the connection error was twice it asked me to update but then told me I had the wrong file. This only happened when I tried "upgrading" to 1.05 as I was trying to start again. After it tells me that if I try running it again it gives me the connection error.
Unquote
I then followed the instructions by epimazzo as written above. I also tried the T-Mobile ROM 2.26 which was not working for me. PANIC!!!! Error messag was that I had the wrong Vendor ID. THerefore no upgrade to TMob 2.26 was possible. I tried it then my original qtek ROM in my language and see it worked!!! This IMHO means that I did not put the device in a proper IPL1.xx and SPL 1.xx status which is required for a clean system in irder to unlock it! So if it is bricked, try your native AKU2 ROM and make sure you unlocked it properly. Maybe you have to run the 1.05 ROM for a second time after the unlocking.
I hope this helps you guys.
Click to expand...
Click to collapse

Excellent post. I messed up with my own cooked ROM and could only get the bootloader screen. Tried the tips here - didn't work first time but I pulled the battery from the KJAM to reset it rather than using the reset button and it worked fine.

In my opinion this thread is so helpful to people who brick their device, it should go "sticky". Mods anything you can do about it?

Thanks buddy! I really appreciate!
We survive here over tips like that!
jt_armstrong said:
Excellent post. I messed up with my own cooked ROM and could only get the bootloader screen. Tried the tips here - didn't work first time but I pulled the battery from the KJAM to reset it rather than using the reset button and it worked fine.
Click to expand...
Click to collapse

Help me similar problem
I upgraded Super Rom, then my Wizard run very slow and no signal (no call out and in- no network at all). And Terible thing is PC could not dectect PPC thought Active Sync. I've soft and hard reset but no use.
So I donot know where to start to re install Rom again.
Please help me....

Hi there!
It seems that you just need to enter into the bootloader mode and reflash it again!
I had similar problems and more during my brick "false" stage!
So, just try to follow my steps here and you should be fine! Once you get into bootloader mode, just use any ROM out there to reflash.
Good [email protected]
thaiphong said:
I upgraded Super Rom, then my Wizard run very slow and no signal (no call out and in- no network at all). And Terible thing is PC could not dectect PPC thought Active Sync. I've soft and hard reset but no use.
So I donot know where to start to re install Rom again.
Please help me....
Click to expand...
Click to collapse

I was about to start a EMERGENCY HELP thread, but I *think* this is the right place instead.
The "touch" of my screen went dead today. It got progressively worse over a few hours, starting with difficulty in using the phone dialer, then random incorrect stuff getting triggered by screen taps.
So I hard reset, and got no response on the fifth alignment cross, meaning 1) "Tap on the screen...; 2) center; 3) top left; 4) bottom left; 5) bottom right. In that I could not proceed with alignment, I hard reset again, and now, at the first alignment screen, i.e. "Tap on the screen...", I have no screen response at all.
I called T-mo, and they are being great about sending a replacement ASAP (and getting me a loaner in the meantime).
BUT, I am running Faria+ AKU3.3 V2... so I clearly have to flash back to T-mo 2.26. I can;t figure out how to do it though, as no matter what I do I am stuck at the first alignment screen!!
HELP!! EMERGENCY!!!
(I have three or four days to get this done, so it's not THAT urgent)

Do a search for Broken Screen. Someone (either in Wizard Upgrading or in the Wizard forum) just had a similar issue with a cracked screen. They downloaded something that allowed them to get around the welcome page.

Actually, if you are just trying to flash a new ROM, don't even mess with it. Go straight to the Boot Loader screen (see the first post of this thread). No tapping necessary until the new rom is on (and that will be the Tmobile then so you would be good.

Thanks for the quick reply. Charging up to green now, and then will try to enter bootloader and flash T-mo 2.26. Will report back.

Worked great. Back to T-mo she goes!!!

BootLoader Mode
Excellent thread but you left out one thing.....exactly how to place your device in bootloader mode.
To clear up any misunderstanding because this is very important....this is how you do it:
Perform a soft reset, when the screen goes blank hold the camera button until a multi colored screen comes up .... That's it !!!!!!
When the unit is connected, USB is displayed at the bottom left.

Bootloader question/trouble

Hey there everyone, I am pretty new to this forum so I must apologize for throwing you all into the deep end. I recently purchased an o2 XDA mini S second hand from a guy on boards.ie here in Ireland. I got the phone and really liked it because it allowed me to get rid of my Dell Axim X3i and mp3 player and keep it all in one device.
After a little bit of more research I discovered that I could remove some of the bloatware from the o2 xda mini S by just hard resetting and choosing the basic option which I than did. Still not satisfied with the overall performance of the XDA I decided to try a rom upgrade. Not wanting to do a totall overhaul I decided to just do a radio upgrade first.
My device is sim unlocked, it was like that when I bought it. I used the latest wizard service tool to CID unlock the device before I even flashed the phone. I also used the wizard service tool to change the nk.nbf file within the o2 mini S radio update into 96000000-GSM.nb. I then used this file to write to the GSM radio code (Bdk 1) according to the wizard service tool in the hopes that it would upgrade my radio version.
Well when I restarted, nothing of the sort happened, on the boot screen I noticed I was now missing my GSM version and when the phone finally got into windows mobile, it did not pick up any signal even though beforehand it could. The phone also became super slow to the point where it was unusable.
I have gone into bootloader mode subsequently after reading on this forum and tried to reflash with a number of updates with active sync disabled and nothing else running with the phone connected via usb to the pc. None of the updates would even pick up the phone or allow me to flash it.
My phone is pretty much screwed, I have a spare so it is not that big of an issue but I would like to make this usable again if at all possible. So my question is how do I flash a rom while the phone is in bootloader mode?
P.S I forgot to include the Current boot screen details:
IPL - 1.05
SPL - 1.05
OS - 1.5.4.2

Hi,
You can use the Wizard Love Rom from here http://rapidshare.com/files/17792050/Wizard_Love_2.26.10.2_WWE_Novii_CF2.rar

Hey there, thanks for the advice, I did download that ROM but like I said before, none of the roms manage to flash my XDA because they all cannot seem to connect to it. Activesync does not even pick it up in windows mode, and even when I have it connected in bootloader mode via usb and I double click on the love rom, it goes through the motions but never managed to "verify the information with the pda"

Try a stock Tmobile ROM but not from bootloader. Also, I would check the activesync app on the device. Make sure it's set to use USB as the default connection method.
A few other steps to try...
Uninstall ActiveSync and install an older version. If still no go, try a newer version.
Try a different USB cable and/or USB port.
Try a different computer with XP, not Vista.
Try flashing it without the SIM card or any memory cards.
If all else fails, you can try the SD card flashing method. There are instructions in the Wiki on how to do it, but always a stock ROM.
Try this one... http://forum.xda-developers.com/showthread.php?t=311027
Updated IPL/SPL and radio 2.69

Hey Devis, I think I have come one step closer, I tried all the suggestions that you made. Except well now my phone will not even go into the operating system when I switch it on. It will boot and the version numbers show but then it just resets itself.
I tried a different usb cable and I am not using vista, tried a different pc and the same result. The one place I did have some marginal success was the sd card method.
Basically what happened is that It backed up the OS from my phone and then reloaded it, not exactly what I wanted since the OS and rom are both screwed on the phone so my question at this point is, is there anyway using the SD card method to load one of the stock roms onto my phone?
I searched around the net and found the opposite to the "r2sd all" function, would be the "s2d" function, would that allow me to flash the phone with a stock rom?
Thanks for your time, I am going to call it a night here in ireland and head to bed.

Ok, if the phone resets then you probbably have a dead/dying battery. Charge it for about an hour or so using the wall charger, not the USB cable. Try to restart it and see if you can get in the OS. I was looking in the SD card method thread and some guy was successful at restoring the image from the SD even though his OS had died. He then had a fully functional phone.
The other thing to do would be to get the image file from someone that has a living and breathing wizard, preferably one with a stock ROM. Since this method is the equivalent of making an image of a PC using Ghost, the restoration of such an image to your Wizard should work just fine.
Just make sure that the other Wizard is SIM and CID unlocked. Or just go buy a Wizard from the store, unlock SIM and CID, copy the image on the SD and flash your device. Or... since u've got a new Wizard in your hands, just take the freaking thing appart and swap the guts return the store bought wizard to the store saying that the thing just doesnt freaking work!
As for the AT commands... it is possible that s2d would workfor you, it doesn't work in my wizard. from what i have been reading it appears that the bootloader is password protected and that password is randomly generated. I haven't played long enough with it to figure out how to get the password.
It looks like you've got some "trial and error" processes ahead of you. There is a wealth of info on bootloader AT commands on Wiki, nothing for the Wizard though. But something may work... not sure.
I could try to get you a ROM dump from my Wizard but I already am on SPL/IPL 3.08 and running WM6. the SPL/IPL version alone wouldn't allow you to restore from my backup.

Hey Devis, thanks for your time, just woke up here, will work some more on the phone today and let you know what is going on

Hey Devis, I did not even get a chance to fiddle around with the phone today, from being able to switch on less than 24 hours ago, it does not even want to switch on now so I am going to officially declared it a brick and move on. Will see if anyone can fix it for me, spent way too much time already when I should be working on my dissertation, thanks alot anyway

Sorry to hear that...
I have bricked one phone myself in the past... my old Pana GD87 and I absolutely loved that phone. I know how you feel.
Good luck with your dissertation.

260 Error when flashing

I have just bought a P3600 and trying to upgrade to WM6. Been following the various instructions all evening but cant get any further than the same point regardless of which rom I try.
My phone connects up via USB and is detected etc, I click through the screens on the RUU, and then run it. Prompt appears on the phone to run enterbotloader.exe, click yes, and then it goes to bootloader screen, where it doesnt do anything after that. I try rerunning the RUU whilst its still attached at bootloader, and makes no difference. It just sits there on bootloader screen and program on windows comes up with a 260 error.
Any suggestions please as to how to get it to go further?1 Windows XP 64 by the way.

Just update your HTC driver in device manager, that's all.

russthewomble said:
I have just bought a P3600 and trying to upgrade to WM6. Been following the various instructions all evening but cant get any further than the same point regardless of which rom I try.
My phone connects up via USB and is detected etc, I click through the screens on the RUU, and then run it. Prompt appears on the phone to run enterbotloader.exe, click yes, and then it goes to bootloader screen, where it doesnt do anything after that. I try rerunning the RUU whilst its still attached at bootloader, and makes no difference. It just sits there on bootloader screen and program on windows comes up with a 260 error.
Any suggestions please as to how to get it to go further?1 Windows XP 64 by the way.
Click to expand...
Click to collapse
You musst unlock your device CID/SIM unlocker here in the forum

Make My Day! said:
You musst unlock your device CID/SIM unlocker here in the forum
Click to expand...
Click to collapse
I try to do this but I get to exactly the same stage ie it goes to the tri color screen and then the RUU does not seem to be able to detect the phone.

russthewomble said:
I try to do this but I get to exactly the same stage ie it goes to the tri color screen and then the RUU does not seem to be able to detect the phone.
Click to expand...
Click to collapse
Hmm than is the Problem your Window XP 64 Bit system!
Do the upgrade at windows XP 32 Bit version.

I think I'll try and do it via SD card, probably easiest way! Just have to wait for SD card to be delivered :S

I agree. I found the SD card is the easiest way but could not get it to work without using the SSDL posted here on the forum.
This the info is taken form this forum and can not remember who posted it "Thanks any way"
The only thing did not work in my case was the rebooting using the reset button "Ihad HSPL installed". The only way to get it working was by running the SSPL application after setting the SD card as below.
Good luck
Extract the .NBH file from your preferred ROM upgrade: In windows use winrar (right click) to extract
the contents of the exe file. In Linux / MacOS use cabextract
(http://www.cabextract.org.uk/) .
Rename the .NBH file to TRINIMG.nbh and copy it to the root folder of your miniSD card.
With miniSD card inserted on the phone, start the bootloader (hold Power button on right side
and Camera button at same time and stick with stylus in RESET on bottom).
You should see the screen pictured on the left, confirm flashing on screen by pressing the power
button.
Flashing might hang after some time but this is normal. Just wait. Complete flash takes about
30 minutes, so check your battery or connect to charger before the flashing process starts.
When flashing completes soft-reset your device.
Make sure your SD has FAT32 and has no label. There have been reports that if SD has a label the
bootloader can not access the TRINIMG.nbh

Well, i couldn't extract the nbh file from the roms I had, but evenutally found one which extracted to an nbh file. Put it on the SD card, and it worked! Also updated radio using same method so got GPS working as well
If anyone knows of a more up-to-date ROM which an nbh file can be extracted from (or any NBH files available for download!) I would greatly appreciate it as this current rom seems slightly unstable (has frozen a couple of times already).
Rom Version 2.0.1.1
ROM Date: 03/07/07
Radio Version: 1.56.70.11
Protocol version 32.89.7020.20H

can not flash button rom

HI.. Im a newbie here, just got my g3 wizard ipl2.25 / spl2.25 couple weeks ago and seen what you can do with them. phone is sim and cid unlocked. i would like to flash to wm6 eventually all thought im running into problems. i followed all the guides to upgrade. tried on my vista 32 bit and win xp sp2. every time i run the button rom to downgrade, i get "romupdateutility mfc application not responding" on vista and "error 260 or 274" with the xp. ive tried it in bootloader mode, restarting pc and wizard, tried different driver for vista, and shut down AS and WMCD before attempting to flash. ive been at this thing for weeks. firewall and antivirus turned off on both pcs, phone is at 100% charge. once in bootloader i get usb at bottom of screen. so i know i have connectivity. run rom not in bootloader, identifies version, then goes to bootloader, then i get error. run again and it dont even identify wizard. happens with both pcs. any ideas please help. i have already read, read, read and still cant figure this out. any ideas are greatly appreciated.

First of all,as you say its SIM/CID unlocked already then why are you trying to downgrade with Button's Rom,its only needed to downgrade if its required to CID unlock.If you are sure its already CID unlocked than simply download any wm6 rom and flash to upgrade,but if you are not sure if its CID unlocked,download WST_4.2.2 tool and run it to verify the CID lock/unlock status.

sorry i made a typo. it is Locked both sim and cid. typed last night at 3:30 in the morning. i ran the wizard service tool and thats what it told me. sorry again

check firewall (even XP one) / anti-virus settings, avoid using front panel USB, avoid usb cables with electric components, try different RUUs, avoid Vista, try another XP computer

Take all the precautions mestrini has posted above and always try on a winXP machine,don't use vista for flashing.May be the Button's rom you downloaded is not a correct package,try to download it again or from a different download link,you can even downgrade with official AKU 1.xx rom if you can find and download.

thanks for all the idea. definately stop trying with vista. i already have tried downloading button rom from a different link, no electronics in usb cable, and firewall and anit-virus have been disabled. i just found a aku 1.xx rom last night so im going to try that tonight. thanks again

well i tried all that and still nothing always get a error 274 connection code. my xp is ran through virtualbox on a ubuntu machine. could that have anything to do with it? i can run WST that works fine. one thing i have noticed though is when my wizard goes into bootloader my connection gets lost and usb connection icon comes up with unknown device and a different pid # then if phone is just turned on, and no check next to it. i tried activating it while ruu is searching and that immediately gives me a 274 error. is it normal for product id to change when in bootloader? by the way i was using the cingular 1.08 ship rom this time, tried it about 15 5itmes with same result everythime. never touched the phone and never took out of bootloader.

litlldevill666 said:
... my xp is ran through virtualbox on a ubuntu machine. could that have anything to do with it? i can run WST that works fine. one thing i have noticed though is when my wizard goes into bootloader my connection gets lost and usb connection icon comes up with unknown device and a different pid # then if phone is just turned on, and no check next to it. i
Click to expand...
Click to collapse
I think you touched the wound!!
I guess RUU can't communicate properly through virtual box. Please try another XP machine before anything else (i think you can manage a friend with one since M$ is so spread - unfortunantely )
cheers

well thats what it was, i did a dual boot on my linux laptop with xp sp2. ran button rom and flashed first time. thank you both very much.

litlldevill666 said:
well that's what it was, i did a dual boot on my linux laptop with xp sp2. ran button rom and flashed first time. thank you both very much.
Click to expand...
Click to collapse
Thanx ! it was pleasure to help you,hope you upgrade it successfully,do let us know if there's any problem,we are always here to help,Thats what this excellent forum is all about !!!

Stuck on Splash, can't flash another ROM

A while ago I tried to Flash a version of WM6 from mfrazzz on my wizard. The installation seemed to go ok, but when I boot it up i coudn't get past the second splash screen. I thought the phone was a gonner until last night, when I gave it another shot putting on Button ROM. I followed these instructions and it worked. The instructions also had me unlock the phone, and that worked fine too. after that I tried updating my IPL and SPL, Right now my IPL is 1.05 and SPL is 3.08
After this I tried unsuccessfully to get WM6, I think I started off trying Faria.
(So here is the actual problem)
After I tried installing Faria unsuccessfully, I couldn't get Button ROM back up. I'm stuck on the second splash screen (picture of a mug of beer in front of the Colosseum). I've tried flashing my phone w/ everything i've got, including button ROM and Love, and nothing works. most of the WM6 Update Utilities won't even connect. Button Rom connects, stalls at 98%, finished and says it was a success, but I'm still hung up on the Splash.
(I'm running WinXP w/ SP2)
I really just want something running on this phone, don't care what it is.
Thank you for your time

Download official stock rom to recover back and download WST_4.2.2 to verify the CID lock/unlock status,most probably its still CID locked.or you can even reflash 'Button's Rom' again.

No, I've tried to reflash button rom many times. It says it works but it gets hung up on the splash. Since I can't get anything to run on it WST won't work (I think)

Yes! WST only works on a working OS,have you tried to flash the official stock rom ?
Don't activesync or establish partnership,better if you altogether disable & close activesync and end process 'WCESCOMM.EXE' in the Task Manager and try to end as many applications running at the background.Don't surf the net,disable all anti virus and firewall.
Simply get the phone into Bootloaders mode,hook up with pc via usb cable,watch small usb appear at the bottom of Bootloader screen and run the Rom,hope it'll work.

hEY ZABARDAST
zabardast_1 said:
Yes! WST only works on a working OS,have you tried to flash the official stock rom ?
Don't activesync or establish partnership,better if you altogether disable & close activesync and end process 'WCESCOMM.EXE' in the Task Manager and try to end as many applications running at the background.Don't surf the net,disable all anti virus and firewall.
Simply get the phone into Bootloaders mode,hook up with pc via usb cable,watch small usb appear at the bottom of Bootloader screen and run the Rom,hope it'll work.
Click to expand...
Click to collapse
I did this when my Wizard stucks on the splash...
Get mtty 1.04 i thin i dont remember exactly but the higher i ever saw.
kill process wcesscom in PC
conect the ppc on Bootloader
click on conection it shows USB if not... start up again the process
then a white screen appears
I type: task 28
then it works a little on some memory directions
I type: task 28 55aa [or something] (its better get the info on wiki cause it works on chip directly)
without unplug the PDA starts the RUU again...
It works for me...
This is a process for HTC Universal but it works on Blue angel and Wizard for sure!
wait a little i will confirm the steps and the exactly words to type in.

you might need clean the ROM or your flash ROM is overcooked.
I can repair your phone !

+ Que PPC said:
I did this when my Wizard stucks on the splash...
...
wait a little i will confirm the steps and the exactly words to type in.
Click to expand...
Click to collapse
Hey + Que PPC!
Have you confiirmed those values? And is your Wizard CID unlocked?
This would be great to confirm working so that all those with CID locked devices could get their phones back - without paying IMEI-check.co.suckourmoney.uk
@ twig2256
If your phone is CID unlocked try Drugstore's method of recovering Splash Screen frozen phones
cheers

YES
The values are the same for every DOC CHIP
When the MTTY conects to USB type exactly this...
task 28
(then it will work formating and cleaning the DOC
then it says succesfully clean
and now type...
task 28 55aa
it again works on the same process you can close the mtty without unplug your device... update your device with a Stock rom.
Actualy I have issues with mtty i dont know why i can acces to USB it say CMD GOD Damn can anybody helps...
This is the link that mestrini said for drug gsm store metod to unfreeze
http://forum.xda-developers.com/showthread.php?t=276963
Hey mestrini see this...
http://wiki.xda-developers.com/index.php?pagename=Uni_Stuck_Bootloader
even if it is universal it work for Wizard i did it once it works for me. but now it wont why????

zabardast_1 said:
Yes! WST only works on a working OS,have you tried to flash the official stock rom ?
Don't activesync or establish partnership,better if you altogether disable & close activesync and end process 'WCESCOMM.EXE' in the Task Manager and try to end as many applications running at the background.Don't surf the net,disable all anti virus and firewall.
Simply get the phone into Bootloaders mode,hook up with pc via usb cable,watch small usb appear at the bottom of Bootloader screen and run the Rom,hope it'll work.
Click to expand...
Click to collapse
can't solve my t-mobile mda