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.
Related
Guys,
I just tried to upgrade to a new ROM on my Cingular 8125. I have upgraded from the original rom to a Mr. Clean AKU 2.3 Rom a while back. This time I tried to load Ell's AKU 3.2 Rom.
Anyway, my computer locked and restarted during the flashing process (99%)
My phone turns on and shows the colored bar screen (is this called the bootloader?). This is all it does. I'm not sure how to try and fix this. I'd like to try and reflash a rom; however, if I try to do that I get Error 260. This error says it can't find the phone which is easy to understand since Activesync can't connect since the phone won't boot.
HELP!
SuperDodge said:
Guys,
I just tried to upgrade to a new ROM on my Cingular 8125. I have upgraded from the original rom to a Mr. Clean AKU 2.3 Rom a while back. This time I tried to load Ell's AKU 3.2 Rom.
Anyway, my computer locked and restarted during the flashing process (99%)
My phone turns on and shows the colored bar screen (is this called the bootloader?). This is all it does. I'm not sure how to try and fix this. I'd like to try and reflash a rom; however, if I try to do that I get Error 260. This error says it can't find the phone which is easy to understand since Activesync can't connect since the phone won't boot.
HELP!
Click to expand...
Click to collapse
i had this very proglem... TURN OFF THE PHONE ASAP.. as the bootloader screen will drain your battery very quickly.... reset computer and phone... plus in the USB cord.. and in the booth loader screen in the lower left corner.. you should see USB!!! just flash workin room.. and you should be set to go.. i believe>.
When I plug the phone in it does show USB in the lower left corner; however, The rom update utility can't see the phone.
Am I doing something wrong or should I be trying to install the rom in another manner?
SuperDodge said:
When I plug the phone in it does show USB in the lower left corner; however, The rom update utility can't see the phone.
Am I doing something wrong or should I be trying to install the rom in another manner?
Click to expand...
Click to collapse
hmmm i dont know... try restarting both devices.. other then that i cant hlep ya.. im still new to this...
USB means it is connected.
Again, keep the battery out when you aren't doing the flash. Reboot the PC in case the link is down.
Try flashing a stable ROM, like the Mr. Clean one you used before. Activesync doesn't need to operate, the ROM will see the wizard if the wizard says USB.
Zonealarm actually interferes with my ROM flashes, although it prompts me to see if it is ok; you might turn off your firewall prior to doing the ROM flash. If you do so, disconnect from the web.
I have also the same problem with my XDA 2 mini or the other called this the HTC Magician. I try to UPgrade my Radio 1.03 to 1.12. and when im applying the upgrade procedure the Upgrading stops and error. What happen now is my XDA 2 mini or HTC magician doesnt open now. only the word "SERIAL" and when i plug the USB, the word "USB" show on the screen................... Is there some one can help me pleasssse with my problem....
There is a problem with my MDA: It continually flashes the volume/ringer control on the screen with the circle with the loudspeaker and mic turned off. This flashes every second or two and when it flashes, prevents pretty much anything else from working or command from executing.
I had a very old TMobile software version on it. I down loaded a much newer version from TMobile in an attempt to get rid of this problem before upgrading to XDA firmware: (The whole thing is very out of warranty)
The upgrade went successfully but the flashing volume / ringer control still flashes.
Does anyone know what this means or if upgrading to XDA will get rid of this problem (or exacerbate it!)
Has anyone noticed IF there is a problem with Puttenham's "Step 17"?
I got around my nerves about upgrading this G3 with a hardware problem in place and appear to be encountering a severe problem with Step 17 which is that it says it is "Your Choice" to go to a 3.08 SPL/IPL. Nowhere however does it say which later ROMs you can apply if you DO choose to go with the 3.08. I applied this to correct what I thought was the hardware issue (reinstalling the T-Mobile ROM at SPL 2.26 didn’t seem to cure it) and the 3.08 did install properly and cured the hardware problem.
I tried different ROMs because I cant seem to understand how to use VoIP or which ROM will let me use this 'feature' or which ROM has this feature built it as some say they have deliberately taken it out.
Suddenly I am getting error messages telling me that the unit needs a later ROM revision to install perfectly.
(WizardLove was the first to do this: It executes in Italian and as I mentioned, just tells me that it needs a later version to work)
So I reflashed with the Molski ROM which is the only one which seems to be around and the flash worked up until 94%. At that stage the progress bar turned to red and there was an error message telling me that I can recover and try again. I did this a few times and SEEM to have bricked my Wizard (When the Molski upgrade failed, attempts to chkdsk, reboot, delete all temp files etc failed). The unit will now only boot to the three-colour screen? Further attempts to flash seem to see and read the device and tell me either that there is no ROM on it and would I like to upgrade? Followed by this unexplained 'USE LATER ROM'. (There may be a problem with installing the T-Mobile ROM on an unlocked Wizard with a 3.08 IPL/SPL However it has to be said that Molski is, still, the only ROM which runs and it inevitably stops at the same position, the 94% mark when the MDA progress bar goes red, the unit shuts down, the upgrade process thinks about it for a while and ultimately reports ERROR [302] UPDATE ERROR)
Alternatively they (for example ROM Update Utility 2.00.1) tell me that there is no communication between the PC and the Wizard. Actually ActiveSync 4.5 does show no connection between the device and the PC, which I suppose I would expect if the Molski ROM failed to complete? Device Manager seems OK with the unit being in place though? And I cant believe this is important as there obviously IS connection between the computer and the PDA
Easymob said he would let users have a path to a ROM they could use but no where is it set out which ROMs you can use of the ones you actually CAN find?
I have also tried the Xelencin ROM which initially tells me that it cant see the PDA. Then it admits that it can and tries to unlock the CID (which surely must be already unlocked by now if I have upgraded to the later SPL??)
I am not sure I have a totally bricked unit, - The Xelencin T-Mobile ROM MUST be doing something because it does successfully run the RAPI unlock and after a few error messages telling me it can't access the MDA, reports DONE! But then it tries to run Machinagod's HTC Wizard Unlocker and gets stuck. It shouldnt get stuck at this step as I must already BE unlocked! It should pass this step.
I can hear hdd movement (not churning) but the program doesn’t progress past this step. Ultimately this carries on for hours and the Wizard shuts down I presume when the battery fails as the charge function doesn’t seem to work in ROM upgrade three colour screen mode. Plugging the charger in now doesnt seem to do anything
Again as the program was built for the 2.26 SPL, I still cant figure out whether these available ROMs should run on the 3.08 which I followed in the STEP 17.
MEANWHILE BACK AT THE RANCH: Is there a more obvious answer to why Molski always fails at precisely the same 94% position?
I was upgrading my t-mobile 8150(?) the k-jam with the new windows mobile 6 and in the middle of it my comp crashed!! now i am stuck at the bootloader mode (3 colored screen) and when i try to redo it i get to 99% and get a 302 error message. i follow the instructions given but keeps going in circles. its a G3 so is my phone bricked or is there a way to save it? i've been looking at this site all day but am now just more confused. lol thanks for your help!
No your phone isn't bricked. As long as you can get into the bootloader screen you should be ok. What you need to do is flash an official carrier rom either tmobile 2.26 or wizard love rom after you that than you can reflash to wm6. look at the stickies in the wizard forums that is where you can find these roms.
Thanks for the info but seems my techno curse continues. I tried the wizard love rom but it was in a different language and whem i tried the tmobile 2.26 i got "error 274 connection." Any more suggestions? Again thanks soo much for an issue I'm sure has been posted here a thouand times.
This happens to me all the time. I always use the Cingular 2.25 rom, it works perfectly and I have an I-mate K-JAM. Then, do the WM6 upgrade, but ensure all of your Norton and Antivirus and background running apps are shut down. Good luck.
yes also take out your mini sd card if you have one. even though its in another language it will work. "AVANTI means next. so just keep hitting that and you will be fine.
hmm been trying to d/l the Cingular 2.25 rom but the link seems to have stoped working...
It;s aaaaaaaaaaaaaaalllllllllliiiiiiiiiiivvvvvvvvvvvvvvvvveeeeeeeeeeeeeeeee!!! for now lol Lets see what happens after i install wm6 I couldn't get the cingular rom but i had already dowbloaded the button rom i found here earlier and it worked like a dream!! quick and easy!! thank you all soooooo much!
hi all. one more little thing. after adding the new rom to get it back to life, now the numbers don't match so i can't upgrade to wm6. i have ipl 1.01 spl 2.26. advice?
flash to the tmo 2.26 or cingular 2.25...that will give you an IPL/SPL of 2.xx
then, you can flash to WM6
i want to delete this message. can't find a way to do it.
there's any other way to flash without usb cable?? sorry to bug in this thread but i lost my usb connection somehow and did a hard reset and still doesn't work. my phone charges. and no is not my computer cuz my wifes phone same as mine does sync i have a tmobile mda also known as the cingular 8125.
fallon75 said:
hi all. one more little thing. after adding the new rom to get it back to life, now the numbers don't match so i can't upgrade to wm6. i have ipl 1.01 spl 2.26. advice?
Click to expand...
Click to collapse
keep reflashing buttons rom until both ipl/spl are the same number. if they are different, then the flash didn't complete correctly. (it happens often, so it's kinda normal). just keep reflashing. after both ipl/spl are the same, then CID unlock and then update to an official carrier...then flash a wm6.
can anyone help me??
Check if "USB" displayed when in bootloader mode (Camera+reset) with Wizard connected to PC.
If so, you may try to flash another ROM through bootloader.
starkwong said:
Check if "USB" displayed when in bootloader mode (Camera+reset) with Wizard connected to PC.
If so, you may try to flash another ROM through bootloader.
Click to expand...
Click to collapse
it does shows but how can i flash?? it still won't connect o my pc. my pc doesn't recognize it. but it does recognize my wifes phone.
Try to run RUU straight with Wizard connected and running in bootloader mode
First off, anyone on this forum who has contributed anything, I am have the deepest respect for, and my favorites will get donations as soon as I have money. Ok enough a$$ kissing.
So here is my problem:
I flashed it's right's TNT 6.1 19919 after hardspling. After many problems, like pseudo-hard resetting (turning off, losing all but 6% battery, and changing the date back to what it was originally i.e. 1/27/06) while in a phone call and doing the same while using the wifi, i hard reset and still the same problems occurred. so I undid the hardspl, so now i am back to 2.25.001 in the bootloader but when i connect it to the computer (winxp) to flash the original rom (cingular 2.25) it freezes at 91%. If anyone has had this problem occur or knows the solution as to get ANY rom back on it, IT would be greatly appreciated.
Also after doing some reading I tried to flash wizard love 2.26 to it and that freezes at about 50-60%. so I am stuck and it is really annoying.
Full 8 hour charge, restart computer, different usb port. Same happens: Error 302 Update Error
Hum... maybe when you reCID locked it, you put a CID that's not for that official ROM you're trying to flash. The misbehavior of the phone is due to the ROM you had, not the CID Unlock. If I'm not mistaken, you can hardSPL it again, from bootloader. Then you can try and flash any other ROM you wish. Give my ROM (WM5SE rev5 - if your phone can handle 240MHz - or rev4) a go, after you have CID Unlocked your phone.
My phone can take up to 273 but, all the roms i flashed were g4 safe.... because the ipl spl never changed and i checked them in shell tool . it gives me a update error 302 which wizard love documentation says that the "phone needs a new rom code" which implies that it needs to be taken to cingular, and i dont think i can lie that well. how would one "accidentally" put their phone into bootloader?
theblackhandx said:
First off, anyone on this forum who has contributed anything, I am have the deepest respect for, and my favorites will get donations as soon as I have money. Ok enough a$$ kissing.
So here is my problem:
I flashed it's right's TNT 6.1 19919 after hardspling. After many problems, like pseudo-hard resetting (turning off, losing all but 6% battery, and changing the date back to what it was originally i.e. 1/27/06) while in a phone call and doing the same while using the wifi, i hard reset and still the same problems occurred. so I undid the hardspl, so now i am back to 2.25.001 in the bootloader but when i connect it to the computer (winxp) to flash the original rom (cingular 2.25) it freezes at 91%. If anyone has had this problem occur or knows the solution as to get ANY rom back on it, IT would be greatly appreciated.
Also after doing some reading I tried to flash wizard love 2.26 to it and that freezes at about 50-60%. so I am stuck and it is really annoying.
Full 8 hour charge, restart computer, different usb port. Same happens: Error 302 Update Error
Click to expand...
Click to collapse
You have posted present IPL/SPL 2.25.001,is it 2.25.001 or .0001 ?
As you removed 'HardSPL',did you reflash the appropriate IPL/SPL regarding your phones official bootloader IPL/SPL...?
You shud do the 'HardSPL' again and either do the removal of HardSPL again correctly as instructed in the sticky ' How to remove HardSPL' or Flash any other Rom to recover.
Cheers!
no it was 2.25.001 just a typo. i think i will try these suggestions when i get home and i will post my findings.
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