Database Develop

After upgrade WIZA200 SPV M3000 stuck in Startup screen

Hi friends,
I am very new to upgrading\downgrading pc phones. I was trying to upgrade my wizard to upload diffirent language ROM, using this method :-
http://forum.xda-developers.com/viewtopic.php?t=56088
After some tries, I succeeded to upgrade rom, but after this power on the wizard and it stuck into startup screen.
If I press Camera + Power swich it shows three colour screen and some text :
IPL 2.16. 0001
SPL 2.16 0001
I think my device was CID locked and G4, and that is why I have a dead wizard.
I have backed up the phone before upgrading with wizBackup.exe and I have back files on my hard disk. I dont know how to restore rom from these backup files. :?: :?: :?:
Please help me to revive my PC.
Thanks in advance

Singh06 said:
Hi friends,
I am very new to upgrading\downgrading pc phones. I was trying to upgrade my wizard to upload diffirent language ROM, using this method :-
http://forum.xda-developers.com/viewtopic.php?t=56088
After some tries, I succeeded to upgrade rom, but after this power on the wizard and it stuck into startup screen.
If I press Camera + Power swich it shows three colour screen and some text :
IPL 2.16. 0001
SPL 2.16 0001
I think my device was CID locked and G4, and that is why I have a dead wizard.
I have backed up the phone before upgrading with wizBackup.exe and I have back files on my hard disk. I dont know how to restore rom from these backup files. :?: :?: :?:
Please help me to revive my PC.
Thanks in advance
Click to expand...
Click to collapse
Your phone is not dead!!!
If you can get to the three color sceen then your botloader is intact (and preserving the bootloader was the point with the tutorial that you followed).
Your phone is CID locked and is G4, that's right, but this is NOT the reason for the problem. The tutorial you followed, which incidentally I wrote, deals with CID locked G4 phone like yours.
The problem you had is probably due to a not correctly cooked rom.
Anyway, don't worry. You got the three colors screen so you can connect your phone to USB (even if activesync won't recognise it) and flash your factory rom (the one you were trying to replace). Don't need to use your backup: simply download the original rom from the manufacturer/operator site.
bye

After many tries now my phone is working again,
I downloaded RUU_Prodigy_2170702_21707102_20710_QTEK_WWE_Ship from internet then cooked its nk.nbf file.
then uploaded the rom and phone is working again. Thanks for your help

Singh06 said:
After many tries now my phone is working again,
I downloaded RUU_Prodigy_2170702_21707102_20710_QTEK_WWE_Ship from internet then cooked its nk.nbf file.
then uploaded the rom and phone is working again. Thanks for your help
Click to expand...
Click to collapse
I glad you worked it out!
Bye

hello. I have similar problem. I upgraded my wizard to AKU2.3 and now phone doesn't start. It start showing splash screen with the information:
IPL:2.24
SPL:2.24
GSM:02.25.11
OS:2.24.10.1
HOW to fix this problem ?

hi guys
i have qtek wiza200 today i'm use MrClean_RUU_WIZARD_224a_AKU23_WWE.zip after flashing my phone turn on and installing all soft and restart and dead my phone. i'm push camera+power+reset i can't enter to boot mode. help me to repair my cellphone and how resolve my problem. my phone forever dead????
thanks a lot

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.

My MDA won't boot correctly anymore.

I was upgrading my MDA using the official mda update 2.26 and then the phone completely froze. When I soft-resetted the phone, it wont get off the T-Mobile load screen. I tried to hard-reset it using the voice+commanager to reset, but then it just goes back to the T-Mobile load screen. Can anyone help me? I also tried to flash the Wizard_Love on the 3 color screen but it keeps giving me error 200. Please I need your help.

wow no response to such a serous problem. I'm having the same issue I down loading and install to my storage card some files gps navi apps from the ppc freeware site. while trying the apps my device froze. I held down the power button and it didn't respond so I removed battery.but device won't lad pass the second start up screen. what do I do

collwatt said:
wow no response to such a serous problem. I'm having the same issue I down loading and install to my storage card some files gps navi apps from the ppc freeware site. while trying the apps my device froze. I held down the power button and it didn't respond so I removed battery.but device won't lad pass the second start up screen. what do I do
Click to expand...
Click to collapse
Remove the sdcard/minisd and do a hard reset.

Bricked?
Hi all,
i have similar problem like Lo0o0nG.
Tried to flash wm6 on my g3 wizard following the wiki:
Flashed the Button ROM "CUSTOM__RUU_Wizard_1050412_WWE_101_11210_WWE ROM" but after rebooting the wizard stucks in the first screen with the beer glass on it - showing IPL 1.01, SPL 2.21, GSM 01.12.10 and OS 1.5.4.2.
Then nothing else happens...
Did this 6 or 7 times before with g3 and g4 phones - worked perfectly till now..
Are there any suggestions / any possibility to get my phone working again?
thx,
derHarry

If the phone is CID unlocked use the SD/mtty method to restore the full ROM image.
If it's not CID unlocked then try to unlock it with WST and reflash the ROM(s)

Thank you for your fast reply!
It's not CID unlocked, but WST can't connect to the device...
any other suggestions?

I'm sorry but WST can't connect unless the OS has booted already. I didn't realize it when answering.
I guess the only solution now is to use the commercial unlocking solution by IMEIcheck.co.uk

Thank you for your suggestions,
i think i'll replace the touchscreen from this bricked device with the broken one from my other device... so it's not that tragical
btw: how could this happen? did i something wrong while flashing?

derHarry said:
Thank you for your suggestions,
i think i'll replace the touchscreen from this bricked device with the broken one from my other device... so it's not that tragical
btw: how could this happen? did i something wrong while flashing?
Click to expand...
Click to collapse
Yes. I believe you flashed a ROM without permission (CID unlocking) or an upgrade went wrong (stopped before finishinfg) and now the bootloader 1.xx can't load the OS because the 2.xx address is different and can't be found.
cheers

MDA Problems

Hi. I am trying to unlock and flash my T-Mobile MDA, but as soon as I open and hit update on the wizard button rom the phone shuts down and then doesnt start back up to show me the beer screen. It is a G3 device and it is CID locked. SIM is also locked. Any suggestions?

i have
the same problems.
It´s a MDA from german t-mobile with G3 - so a wizard.
But i searched about 2 days but it´s not possible to get into bootloader mode. The original firmware update also is NOT working because restart in bootloader not works.
But there IS a solution that i´m trying just at this time - try ShellTool (search in Forum) and you will get lucky. The first Software update from t-mobile just worked now i´m flashing version 3.x to try.
But don´t forget to first enable RAPI on it - the easiest solution is with "Wizard Service Tool", because else you won´t have luck in updating.
And be sure to ONLY prepare a G3 phone in that way (when rebooting you can see it in the versions of IPL and SPL - if they are something like 1.06 or 2.21 or so you have luck - but 2.xx.xxxx is a G4 phone there you have to pay attention (look into forum for more infos).
After that i want to get wm6.1 on it.
If there is somebody who has an idea getting into or updating the bootloader then he is greatly welcome
And yes i tried camera button, power button, soft reset and so on - also (some people wrote down) i tried to put in USB Cable - every time i press camera and want to restart there is NO reaction of the phone until i make a new soft reset!

Thanks man. i will definitely try the shell tool out. If any one else has more suggestions that would be great!

Update: WM 6.1 is now working on it - but still with the old bootloader. I don´t now, why there is no possibility to get into it but now it´s not my problem any more
Best regards!
Stefan
Lustikus said:
the same problems.
It´s a MDA from german t-mobile with G3 - so a wizard.
But i searched about 2 days but it´s not possible to get into bootloader mode. The original firmware update also is NOT working because restart in bootloader not works.
But there IS a solution that i´m trying just at this time - try ShellTool (search in Forum) and you will get lucky. The first Software update from t-mobile just worked now i´m flashing version 3.x to try.
But don´t forget to first enable RAPI on it - the easiest solution is with "Wizard Service Tool", because else you won´t have luck in updating.
And be sure to ONLY prepare a G3 phone in that way (when rebooting you can see it in the versions of IPL and SPL - if they are something like 1.06 or 2.21 or so you have luck - but 2.xx.xxxx is a G4 phone there you have to pay attention (look into forum for more infos).
After that i want to get wm6.1 on it.
If there is somebody who has an idea getting into or updating the bootloader then he is greatly welcome
And yes i tried camera button, power button, soft reset and so on - also (some people wrote down) i tried to put in USB Cable - every time i press camera and want to restart there is NO reaction of the phone until i make a new soft reset!
Click to expand...
Click to collapse

Kaiser bricked nothing worked yet.

Hi.
today i bricked my kaiser when i tried to install a dutty's rom
been trying to get this fixxed for over 5 hours. nothing worked out.
used kaisdiag.nbh from h ttp://forum.xda-developers.com/showthread.php?t=420683
in both suggested solutions my kaiser wont go further then the Loading page. ( waited atleast 10 mins twice without any success)
used some other RUU installs while in the tricolour screen:
ahmedfikry wm6.5 23549 Tilt UC light rom
KAISER_WM65_OS23547_PP12MB_Sonblack05
RUU_Kaiser_HTC_WWE_1.56.405.5_radio_sign_22.45.88.07_1.27.12.11_Ship
RUU_Kaiser_HTC_WWE_3.02.405.0_radio_sign_25.70.30.05_1.58.26.20
Ruu_Signed_Duttys_WM6.1_5.2.19700_Hybrid_V2_1_64.08.21_CubeV2_ <== the one wich bricked my phone
Ruu_Signed_Duttys_WM6.1_5.2.19700_Hybrid_V2_1_65.14.06_No_CubeV2_
RUU_Kaiser_TMO_UK_3.31.110.3_radio_sign_25.83.40.02_1.70.18.02_Ship
some other topic sugested to use MTTY.
but that probram says: usb port cannot open.
long story short: im desperate.
can any of u please help me fix my phone ?
its an MDA vario II. model Kais130 P/N 99hcy063-00
thanks in advance.

i'm no expert at recovering bricked phones...
but what i understand is that IF you have a hard SPL (which hard SPL do you have?), then you should be able to recover your device from nearly any situation.
try this...if RUU is not working well, try to flash using the SD card method.
also, try to flash a stock ROM (using RUU as well as using the SD card method). let us know what happens.

Try putting your phone into bootloader, ( press and hold power and camera buttons while doing a soft reset ) once it is in the " tri-color " screen, let us know what it says on the screen.

thanks for your time and the fast response, to both of you.
@#1
i used Pofs hard spl.
and as mentioned above i tried both the RUU way and with my micro SD card.
the SD way only shows me the 'Loading' screen. over and over.
and with the RUU i get several errors. connection errors at 0% and connection errors some later.
some roms just say they wont work on my phone.
and others just reboot my phone.
@#2
i think my phone gets to the bootloader all the time. cause i c no difference when resetting with camera and power button on.
its the tri color screen with the folowing information that shows up:
RUUNBH
Kais130
SPL-1.56.0000
CPLD-8
serial/USB
______________________
the serial shows up when the phone is not connected.. and the USB shows up when its attached to my pc with usb.
Any other suggestions ?
Thanks in advance .

You don't have hard-spl you still have a stock, flash the stock ROM of your carrier from bootloader.
Then follow the noobs guide to flashing.

Thx guys my phone is working like it used to be.
downoaded the original rom from t-mobile again. and again.
now got one wich is working.
thanks for your help.
i was about to throw the brick trough the window.