Database Develop

Help Please ! Won't go past the Splash Screen?

I've been trying to get my old extended rom and new Qtek OS on my Wizard (Vario).
But now it gets stuck in the spash screen (ie the one giving the ROM numbers).
I've tried putting the wizard into bootloader mode and I can flash RUU's but when it resets it still gets stuck on the spash screen and won't go any further !!!????
What can I do ??
Please Help
Cheers
John

I should say that I had flashed using button's ROM RUU_Wizard_1050412_WWE_101_11210_WWE.exe.html
and this worked fine!
I then copied across my T-mobile Extended ROM and again everything seemed OK.
BUT then I tried to restore my new saved OS ROM using aWizard and this caused a freeze on my Wizard. It was after a hard reset that the wizard stopped at the splash screen.
Now of course I'm limited in my options because Activesync won't work until the Wizard has fully booted up.
I have tried setting the Wizard into bootloader mode and tried several ROM's (RUU Installer ones) but every time the correct splash screen comes up with the new ROM numbers but that is as far as it gets.
I also noticed on hard reset that you get the following message
Format FAT partition
Format failed
it then goes to the splash screen as before.
Are there any other things I can try Or will I have to send it back to T-mobile for a replacement??
(It's only 2 months old and I have re-flashed it with the orginal T-mobile ROM - but still won't go past the splash screen!!)
I live in hope
John

I have this EXACT same problem!
I can reflash any ROM but it will not go past the splash screen. Only difference was I wasn't playing with my extended ROM. I flashed the AKU2 QTEK ROM yesterday and have been fine through several soft resets, etc. This last time I was uninstalling phonealarm and after a soft reset I got a "could not find smswakeup.exe" (or something similar) and it's been stuck ever since! I also get the "Format Failed" message. Can anyone help!?

I think I'm going to have to send it back to T-mobile and hope they give me a replacement. Something is wrong, it doesn't seem to make any difference what ROM I used.
I think I'll reload the T-mobile shipped ROM grom the FTP site and send it back - and claim ignorance that it it suddenlt freezed and now won't boot up! - Bummer!!!

Right I've logged a fault and it will be sent back - let's hope T-mobile can't detect it's been unlocked and had several ROM updates - I suspect they will try a ROM update themselves then give up ???
The worrying thing though is that it IS possible to kill your phone with updates - maybe it was when I used aWizard to try and restore a ROM that did it??? I'll be more carefull next time!!

this has just happened to one of the devices im flashing at the moment.... absolulty f**king raging :evil: :evil:
i wish teher was a solution!!? anyone got any ideas?
activesync wont find it, so aWizard wont work.
i can flash between 3 roms without any problems (1.5.x 1.6.x 2.x) but always hangs on the splash screen. i have flashed back to the default rom that it came installed with it so i could just send it back to o2 (only 2 days old!)
i would rather just get it sorted by myself thoough so if anyone has ANY ideas then please let me know.
thank you!

Good luck! after about 3 days of trying different types of firmware, I gave up and sent it to expansys, for repair. And it looks like they've lost the bloody thing now. :evil:

tonym001 said:
Good luck! after about 3 days of trying different types of firmware, I gave up and sent it to expansys, for repair. And it looks like they've lost the bloody thing now. :evil:
Click to expand...
Click to collapse
yup looks like i might have to give up... ohwell, no worries i will just return it back to O2...
looks like one of our sales guys wont be getting a new phone on tuesday :lol:

same problem here.
tryed to write os with awizzard after changing extended_rom.
kills phone.
format failed..
Tryed different os's from win util - failed
upgraded with sd card methode worked.
in short :
you need a working wizzard to make a os dump on sd card.
Connect to wizzard with usbterm or romupdate.exe or simular.
do a rs2all command to dump os to sd card.
stick this card in broken phone.
hold voice comm button while resetting.
On ask press voice comm button again.
it bow restores the sd backup to phone.
saved mine.....
btw sd card backup can be read ad write by pc with util ntrw.exe .
so if you don't have a working dump i can upload one.
just mail me.
grtx , arnold

hard reset your device and hold your Camera Button prior to starting the wizard back on.
when the device turns back on, you will get the boot screen. Plug in your USB cable and load one of the known ROMS like the second to last iMate ROM.
This will allow you to get past the splash screen.

FarSeide said:
hard reset your device and hold your Camera Button prior to starting the wizard back on.
when the device turns back on, you will get the boot screen. Plug in your USB cable and load one of the known ROMS like the second to last iMate ROM.
This will allow you to get past the splash screen.
Click to expand...
Click to collapse
this didn't work for me.
couls flash rom. even splash screen changed to new roms one.
but still stuck at splash...
tried it with about 4 different orgigenal roms
grtx arnold

arnoldl said:
FarSeide said:
hard reset your device and hold your Camera Button prior to starting the wizard back on.
when the device turns back on, you will get the boot screen. Plug in your USB cable and load one of the known ROMS like the second to last iMate ROM.
This will allow you to get past the splash screen.
Click to expand...
Click to collapse
this didn't work for me.
couls flash rom. even splash screen changed to new roms one.
but still stuck at splash...
tried it with about 4 different orgigenal roms
grtx arnold
Click to expand...
Click to collapse
Don't worry, I met the same problem as you before, almost lost my hope, but finally I managed to fix it.
The solution is simple, that is to find an original SD card backup image from your wizard or others, then try to restore it in the bootloader mode. In my case, it said checksum error or sth else after begin restoring, and it gave up. Then I put my wizard into bootloader mode, picked one offical released RUU package, start reflash again. Finnally, I found the wirzrd works again for me after reboot.
I guess the principle is that the SD restore will destroy some import flash data structure before it said wrong, then the RUU package will rebuilt it wholely in the next reflash.
Hope this helpful, and sorry for my bad english.

There is hope
Last week after trying to downgrade to the original Cingular ROM on my 8125 using aWizard I ended up with a device that was close to being a paperweight. At least I thought so until I read and read and finally was able to get it to the bootloader and then plugged in the USB cable and ran the RUU for the new Qtek ROM (2.17). Guess what happened, yeah it worked. To my surprise I had a perfect device after 15 minutes.
For about 3 hours I thought I was a toast. Never will I do that again.

THIS is truly heaven for me !!
I have my O2 XDA MINI S locked on the splash screen .. and i updated some ROMS to it ....BUT IT DOESNT GET THROUGH IT .... please tell me what to do in a little detailed manner .. please so that i can get my phone to work.. there is no warranty on the phone and i stay IN INDIA . SO YOU'LL ARE MY ONLY HOPE .
my email id is - [email protected]
If you have a dump of the O2 XDA MINI S ..please mail it to me
Plese tell me what to do next ? WILL TRULY APPRECIATE HELP

PLEASE SOME ONE ATLEAST MAIL ME the dump of the os SO THAT I CAN TRY THE SD CARD UPGRADING ,.,,, O2 XDA MINI S

Re: There is hope
Dear Friend
I have problem that my xda mini s stuck on O2 screen, could you help me step by step.
Thank you so much
my mail : [email protected]
Thanks friend
hellomoto_25 said:
Last week after trying to downgrade to the original Cingular ROM on my 8125 using aWizard I ended up with a device that was close to being a paperweight. At least I thought so until I read and read and finally was able to get it to the bootloader and then plugged in the USB cable and ran the RUU for the new Qtek ROM (2.17). Guess what happened, yeah it worked. To my surprise I had a perfect device after 15 minutes.
For about 3 hours I thought I was a toast. Never will I do that again.
Click to expand...
Click to collapse

Dear Friend
I have problem that my xda mini s stuck on O2 screen, could you help me step by step.
Thank you so much
my mail : [email protected]
Thanks friend
odyseus said:
I've been trying to get my old extended rom and new Qtek OS on my Wizard (Vario).
But now it gets stuck in the spash screen (ie the one giving the ROM numbers).
I've tried putting the wizard into bootloader mode and I can flash RUU's but when it resets it still gets stuck on the spash screen and won't go any further !!!????
What can I do ??
Please Help
Cheers
John
Click to expand...
Click to collapse

stuck on o2 screen helppp
Dear Friend
I have problem that my xda mini s stuck on O2 screen, could you help me step by step.I see alot of post, so complicated
Thank you so much
my mail : [email protected]
Thanks friend
flexchen said:
arnoldl said:
FarSeide said:
hard reset your device and hold your Camera Button prior to starting the wizard back on.
when the device turns back on, you will get the boot screen. Plug in your USB cable and load one of the known ROMS like the second to last iMate ROM.
This will allow you to get past the splash screen.
Click to expand...
Click to collapse
this didn't work for me.
couls flash rom. even splash screen changed to new roms one.
but still stuck at splash...
tried it with about 4 different orgigenal roms
grtx arnold
Click to expand...
Click to collapse
Don't worry, I met the same problem as you before, almost lost my hope, but finally I managed to fix it.
The solution is simple, that is to find an original SD card backup image from your wizard or others, then try to restore it in the bootloader mode. In my case, it said checksum error or sth else after begin restoring, and it gave up. Then I put my wizard into bootloader mode, picked one offical released RUU package, start reflash again. Finnally, I found the wirzrd works again for me after reboot.
I guess the principle is that the SD restore will destroy some import flash data structure before it said wrong, then the RUU package will rebuilt it wholely in the next reflash.
Hope this helpful, and sorry for my bad english.
Click to expand...
Click to collapse

how to use bootloader
could you tell me how to use mentioned bootloader for restoring the images? where can I get the software?
Please help
Hendrick
flexchen said:
arnoldl said:
FarSeide said:
hard reset your device and hold your Camera Button prior to starting the wizard back on.
when the device turns back on, you will get the boot screen. Plug in your USB cable and load one of the known ROMS like the second to last iMate ROM.
This will allow you to get past the splash screen.
Click to expand...
Click to collapse
this didn't work for me.
couls flash rom. even splash screen changed to new roms one.
but still stuck at splash...
tried it with about 4 different orgigenal roms
grtx arnold
Click to expand...
Click to collapse
Don't worry, I met the same problem as you before, almost lost my hope, but finally I managed to fix it.
The solution is simple, that is to find an original SD card backup image from your wizard or others, then try to restore it in the bootloader mode. In my case, it said checksum error or sth else after begin restoring, and it gave up. Then I put my wizard into bootloader mode, picked one offical released RUU package, start reflash again. Finnally, I found the wirzrd works again for me after reboot.
I guess the principle is that the SD restore will destroy some import flash data structure before it said wrong, then the RUU package will rebuilt it wholely in the next reflash.
Hope this helpful, and sorry for my bad english.
Click to expand...
Click to collapse

Hi Arnold
My O2 cda mini s get stuck at splash scree, I read your post, still not so understand how to solve it, could you be so kind to write me step by step, and send me some software to solve it. Your help will be so much appreciated.
Hendrick
Email: [email protected]
arnoldl said:
same problem here.
tryed to write os with awizzard after changing extended_rom.
kills phone.
format failed..
Tryed different os's from win util - failed
upgraded with sd card methode worked.
in short :
you need a working wizzard to make a os dump on sd card.
Connect to wizzard with usbterm or romupdate.exe or simular.
do a rs2all command to dump os to sd card.
stick this card in broken phone.
hold voice comm button while resetting.
On ask press voice comm button again.
it bow restores the sd backup to phone.
saved mine.....
btw sd card backup can be read ad write by pc with util ntrw.exe .
so if you don't have a working dump i can upload one.
just mail me.
grtx , arnold
Click to expand...
Click to collapse

Revive this bricked (?) Wizard!

I'm trying to fix my friend's MDA right now. The problem is, it's stuck on T-Mo splash screen. It can however go to tri-color screen. Can I save this MDA or should I bury it?
Any help would be appreciated

Hi!
At the tri-color screen you should be able to flash it with a new ROM. Just try it, that worked for me after a failed flash.
Cheers
djvw

rockmanneo said:
I'm trying to fix my friend's MDA right now. The problem is, it's stuck on T-Mo splash screen. It can however go to tri-color screen. Can I save this MDA or should I bury it?
Any help would be appreciated
Click to expand...
Click to collapse
I just had the same problem myself, talk about ****ting my pants.
I have a Dutch rom in my Vario and I cid unlocked it and tried installing
a US rom but the phone was dead after it.
In the tri-color screen I tried to load the new 2.26 US rom and then the latest UK rom but both failed with invalid Vendor id or something like that.
So I downloaded the NL rom from here and thnk god it loaded without a problem and the Vario is working again.
Sadly in Dutch but at least it works again, can anyone from Holland help me upgrade to the latest US rom ?.
Dave...
Dave...

Encountered some problem..
It would not connect to ActiveSync from tri-color screen. There is a 'USB' at the bottom screen when I plug in the USB cable, but I don't think the PC recognizes the device.
And the thing is my friend has never CID unlock the thing
He said he just took it overseas and never turned it off, when he got back here the phone went like this.
More help please

rockmanneo said:
Encountered some problem..
It would not connect to ActiveSync from tri-color screen. There is a 'USB' at the bottom screen when I plug in the USB cable, but I don't think the PC recognizes the device.
And the thing is my friend has never CID unlock the thing
He said he just took it overseas and never turned it off, when he got back here the phone went like this.
More help please
Click to expand...
Click to collapse
PC doesn't need to recgonize the device via activesync to flash the Rom.

Try and find your original rom.
Put the phone in the bootloader (canaryscreen aka tri-colored screen).
plug-in your usb plug.
And start the rom update utility.
Regardless of your activesync status it should start updating your mda.
This takes about 10 minutes, and will pause at some stage, don't be alarmed and don't pull the plug !!!
Good luck

the-equinoxe said:
Try and find your original rom.
Put the phone in the bootloader (canaryscreen aka tri-colored screen).
plug-in your usb plug.
And start the rom update utility.
Click to expand...
Click to collapse
Can I update using the latest ROM (2.26)? Why does it have to be original rom?
Regardless of your activesync status it should start updating your mda.
Click to expand...
Click to collapse
Even tho PC cannot detect the phone at all, rom update util still can go thru?
I will try again tonight, last night I tried, 2.26 rom update utility cannot detect the mda
Good luck
Click to expand...
Click to collapse
Thanks :wink:

rockmanneo said:
Can I update using the latest ROM (2.26)? Why does it have to be original rom?
Click to expand...
Click to collapse
It's recomended to go back to the original rom, so you can go back to the point before the problems began..
Even tho PC cannot detect the phone at all, rom update util still can go thru?
I will try again tonight, last night I tried, 2.26 rom update utility cannot detect the mda
Click to expand...
Click to collapse
In canary-screen mode the phone will have an active usb connection, ActiveSync won't detect it however, because the ActiveSync software on the phone is only started when windows-mobile is running (which doesn't occur in boot-loader).
The Rom Upgrade Utility, should be able to detect the phone.
But always make shure the battery has been charged (at least half-charged).
Several people on this forum have revived their semi-bricked phone this way.
Thanks :wink:
Click to expand...
Click to collapse
You're welcome

Phone not responding.

I was going to CID unlock my phone. I ran the .cab file on the phone and I soft-reset my phone. Now my phone reboots and when it shows my Today screen, it does not respond to anything (soft-keys or hard-keys) . I tried several times to reboot it, the phone responds for like 5 seconds then nothing on the touch screen or the hardkeys work.
I have t-mob MDA with the latest T-mob rom.
Thanks for your help..

seskyrabart said:
I was going to CID unlock my phone. I ran the .cab file on the phone and I soft-reset my phone. Now my phone reboots and when it shows my Today screen, it does not respond to anything (soft-keys or hard-keys) . I tried several times to reboot it, the phone responds for like 5 seconds then nothing on the touch screen or the hardkeys work.
I have t-mob MDA with the latest T-mob rom.
Thanks for your help..
Click to expand...
Click to collapse
Which "the .cab file"? what version phone? G3? G4?
--M

seskyrabart said:
I was going to CID unlock my phone. I ran the .cab file on the phone and I soft-reset my phone. Now my phone reboots and when it shows my Today screen, it does not respond to anything (soft-keys or hard-keys) . I tried several times to reboot it, the phone responds for like 5 seconds then nothing on the touch screen or the hardkeys work.
I have t-mob MDA with the latest T-mob rom.
Thanks for your help..
Click to expand...
Click to collapse
Is your device a G3 or G4? Hopefully it was a G3 before you did this.
The CID unlocking procedure only works on G3 phones and will brick G4's.
Best thing to try now is to re-flash your carrier's latest rom. If the phone starts working again maybe you just had bad luck with the CID unlock procedure.
If your IPL/SPL were x.xx.0001 before you started you are most likely out of luck.

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

Qtek 9100 Boot help

Hi Guys
I could do with some help on this one.
Ive just gone to update the qtec, ive installed SPL-3.08 to update all worked fine. The device went back into wm5 ready to update to wm6.1, clicked on the rom update it reset the device to go into bootloader and never came back on.
The New rom update wizzard came up with the recovery option but i didnt read it like a fool and now the device wont turn on.
Can anyone help with this?
Thanks Kev

sutt359 said:
Hi Guys
I could do with some help on this one.
Ive just gone to update the qtec, ive installed SPL-3.08 to update all worked fine. The device went back into wm5 ready to update to wm6.1, clicked on the rom update it reset the device to go into bootloader and never came back on.
The New rom update wizzard came up with the recovery option but i didnt read it like a fool and now the device wont turn on.
Can anyone help with this?
Thanks Kev
Click to expand...
Click to collapse
Which is your phone G3 or G4,if its a G3,did you CID unlock it before upgrading to IPL/SPL 3.08.Did you have a fully charged battery before flashing ? this cud be sign of a dead battery also.

zabardast_1 said:
Which is your phone G3 or G4,if its a G3,did you CID unlock it before upgrading to IPL/SPL 3.08.Did you have a fully charged battery before flashing ? this cud be sign of a dead battery also.
Click to expand...
Click to collapse
Thanks for getting back to me. Its a G4 I didnt bother doing the CID unlock, just went for the upgrade of the SPL. After the SPL update it went back into WM5. I left the phone over the weekend on charge but the charge light never came on.
Thanks Kev

sutt359 said:
Thanks for getting back to me. Its a G4 I didnt bother doing the CID unlock, just went for the upgrade of the SPL. After the SPL update it went back into WM5. I left the phone over the weekend on charge but the charge light never came on.
Thanks Kev
Click to expand...
Click to collapse
I believe you've bricked your phone by flashing unappropriated bootloader to it.
Attach here the IPL/SPL you flashed to see if they are indeed G3 files

mestrini said:
I believe you've bricked your phone by flashing unappropriated bootloader to it.
Attach here the IPL/SPL you flashed to see if they are indeed G3 files
Click to expand...
Click to collapse
I Used the
Mobile 6.1 ROM_Wizard_OCTAIVOI_Core_19716_v6.3_PP6MB
Build from the wizard mobile 6 part of the forum.
And the SPL is
http://rapidshare.com/files/107435245/IPL_SPL_3.08.rar.html
It worked fine on the last one i done.
Is there anyway to recover from a brick?

I asked to upload the file here because i can't access rapidshare from work...