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

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.

oh my...did i brick my phone?

I cant believe this....I had no issues all day upgrading the ROM...until my PC overheated and shut off at 57%...
now when my phone starts up I see the 3 bars and it sais USB in the bottom left...but active sync is not connecting!
help!

what 3 bars?
a Red Blue Green Bars color?..
If that so.. you are too lucky..

I read a little more on the wiki:
Type 2a: When the phone boots, it goes directly to bootloader mode (tri-color screen)
This is what I have right now...I can't seem to get active sync to connect...although at the bottom of the screen it has "USB"
I have tried using mtty and dont think its diong anything...

Just stay in the bootloader (tri-color screen) and make sure the "USB" is shown in your device screen..
The reflash.. even if its not sync/connected.. just reflash the ROM..
Everything will be fine..

wow....i think it may actually work....that was SCARY.
nice to know the good ole button flash works when all others fail

I just want to make a clarification..
You are just flashing your device and when the upgrade process is on 57% your computer suddenly shutoff? and the upgrade was cut..
What happened next? did you reset the device then went to tri-color screen? or you just force bootloader mode it?

Yeah pretty much exactly what you said. I literally got up for a second to get some water, came back and saw the telltale sign that my pc had just shut itself off (the screen was black except for the standard boot junk that shows up).
So I look at my device (8125) and it was locked at 57% and was not responsive. I figured that the flash util probably wouldn't continue after the computer started back up (and besides, the device wasn't alive anymore) so I rolled the dice and unplugged the USB and took out the battery. When I put the battery back in and hit the power button, it went straight to the bootloader (the tri color screen).
- By the way - ive got the button image on here now - workin like a champ...

tnx for the explanation..
have fun!!..

thanks for the quick reply - i thought i was completely stuck but the button flash seemed to take care of everything. Makes me almost think that bricking this thing is near impossible... >

Yup!.. that also my conclusion.. its impossible to brick.. thats why i ask for your clarification..

What is this "button flash"? I am stuck in RGB boot mode with no activesync connection. I have read til my eyes crossed, but can not fix my 8125 (G3)!
Please advise.

How about more information? On your bootloader (Rainbow screen) what does it show the IPL / SPL to be? What were you trying to do when you got into this situation? What happened when you were flashing? Is your device a G3 or G4?
Safest thing for you to do right now is to flash your carrier's rom onto the phone (an official shipped ROM). With your phone in the bootload, just run the ROM and it will install (DO NOT RUN A CUSTOM ROM AT THIS POINT SINCE YOU HAVEN"T TOLD US ANY OTHER INFORMATION).

G3 8125
ipl/spl 2.25
Was trying to use faria's latest rom...got stuck at 99% for almost one hour, so I rebooted computer and discon'd the wizard. Now it will boot to rainbow screen and will not connect via activesync (so I can't utilize any other roms to get back to square one).

ActiveSync will NOT connect when you are at the boot loader. As long as you see USB in the bottom left of your phone (above the left soft key) then you can flash your original Cingular ROM and be good to go again.

brick, brick, brick
It happend to me too with faria´s new crossbow rom:
the device freezed at 99% and I reseted it then....nothing happend- bootloader mode: red green blue + usb... but no chance to flash ANYTHING... always the same message:ERROR (260) update error, no connection to the device...???
I tried the O2-mini s update, and the faria rom, no chance just a brick
I need help....

Hunter6 said:
It happend to me too with faria´s new crossbow rom:
the device freezed at 99% and I reseted it then....nothing happend- bootloader mode: red green blue + usb... but no chance to flash ANYTHING... always the same message:ERROR (260) update error, no connection to the device...???
I tried the O2-mini s update, and the faria rom, no chance just a brick
Click to expand...
Click to collapse
Why did you reset it??? All roms freeze. The screen that is flashing the ROM even says it can take up to 10 mins. If you don't get an error onthe PC then DON'T stop the flashing process.
Go get a copy of your carrier's official ROM (not a custom one, but an official one from your carrier.). Then with the phone at the boot loader (Rainbow screen) and the USB cord plugged, in, run the official ROM. If that doesn't work, then get a copy of the Wizard Love rom and flash it (You'll need to find links around here for it, or pull it via PirateBay). You may also want to reboot the PC you are running on and remove your SD card (if you have one) just to remove variables that can play in to all of this.
Good luck

mfrazzz said:
Why did you reset it??? All roms freeze. The screen that is flashing the ROM even says it can take up to 10 mins. If you don't get an error onthe PC then DON'T stop the flashing process.
Click to expand...
Click to collapse
Ten minutes is understandable, but mine stalled for about an hour at the 99% mark. Even my PC would not respond. Is that normal for a rom upgrade?
-----
I was finally able to reset my 8125 to the Cingular ROM. Not sure why I couldn't do it on my PC, but after moving over to my wife's PC I did not have any problems.
Thanks!

brick, brick, brick
o.k. boys, now it is a nice little crossbow brick from faria.....and I can make telefon-calls with my brick.
thanks a lot for your help

entdiablo said:
Ten minutes is understandable, but mine stalled for about an hour at the 99% mark. Even my PC would not respond. Is that normal for a rom upgrade?
Click to expand...
Click to collapse
No, that sounds like your pc locked up or something (I'd blame windows on that one )
I was finally able to reset my 8125 to the Cingular ROM. Not sure why I couldn't do it on my PC, but after moving over to my wife's PC I did not have any problems.
Click to expand...
Click to collapse
Glad to hear you got it going. Good luck and be careful out there!

Hunter6 said:
o.k. boys, now it is a nice little crossbow brick from faria.....and I can make telefon-calls with my brick.
thanks a lot for your help
Click to expand...
Click to collapse
Sorry, I may be missing your humor or sarcasm... Are you saying its dead (if so, give more details about what it does or doesn't do, IPL/SPL it shows (if it turns on), etc... If its now working, then congrats!

upgrade fails

Hello,
I`m trying to get latest lvsw wm6 to the device.
I own the phone since today.
I made the following steps:
Execute ROMUpdateUltility (Hard-SPL)
->Next->Next->Update
From: Image Version 1.16.407.2
to: Image Version 1.20
->Next -> Next
On the phone:
Enterbotloader.exe
"blabla"
YES
On the computer:
ERROR[246]: Device not responding
On the phone:
IPL-SSPL by Des
SPL-1.07.ds
ok,
trying to run ROMUPdateUltility again...
next next next... he shows me the progress bar --> finished! YES!
Rebooting the phone --> same software version as before the update?
trying to update for 2 hours... just to use gps as advertised

please help, i tried the official Update from HTC -> successfull but effects! programs, contacts etc still there, same version number!

messiah said:
please help, i tried the official Update from HTC -> successfull but effects! programs, contacts etc still there, same version number!
Click to expand...
Click to collapse
I've the same problem [246] upgrading unofficial roms like
GSM_1.41.00.11
and
ROM_ING_WM6_2.27
The only upgrade I make successfully is original
htcp3600-RUU_Trinity_HTC_ITA_1-23-408-2_103_6275_1-38-00-11_108
what's wrong ?
P.S.
I test it using activeSync 4.2 & 4.5

Messiah..... Have you read the very first post in the LVSW ROM thread?
I am NOT having ago, just checking, seems you may have miss-understood.
Grab ALL 3 downloads listed there.
Apply first one, and yes there IS NO real visible change to the phone apart from it has been hard SPL'd
Now apply Second one, will go through the same process BUT the Radio ROM is changed and updated
Now Apply the Third and WM6 is installed
The failure you describe is the computer dropping Activ Sync and then "seeing" the phone in Bootloader mode, which is why it take 2 bites of the first cherry, after that all "should " be ok.
I managed to get mine on the first attempt so it is "Me Proof"[TM] and "Just Works" (c)..... however report back if this hasnt helped

yeah, the process you described tells me that you've loaded hard-spl on your phone.. that's all. No WM6 yet...

I have the same problem.
I have Hard-SPL'ed my Orange M700
Then reboot and reestablish Active Sync
Then I have updated the Radio Rom
Then reboot and reestablish Active Sync
and now it's 1.41.00.11 in settings/system/device information
but when i apply
20070527_Trinity_WM6_v2.0.1.1 it uploads then i power on my device and it's still WM5 ?
What am I doing wrong??
Any help appreciated.

This may be a stupid question but have you SuperCID your device before running the updates?
If you go:
Start -> Settings
System
Device Information
What does it say under Radio version? (Just checks the second step has been completed successfully).
Also when you enter the bootloader what does it say on the screen?

akirainblack said:
This may be a stupid question but have you SuperCID your device before running the updates?
If you go:
Start -> Settings
System
Device Information
What does it say under Radio version? (Just checks the second step has been completed successfully).
Also when you enter the bootloader what does it say on the screen?
Click to expand...
Click to collapse
I thought you didn't need to SuperCID the device (http://forum.xda-developers.com/showpost.php?p=1245390&postcount=70)
My radio Rom shows 1.41.00.11

TBH I don't know. But it can't hurt to try it, I SuperCID mine and it flashes perfectly each and every time.
I'm merely trying to make suggestions that may get a result.
Oh, you didn't tell me what the bootscreen said and what version of Activesync do you have on your PC?

While doing the SuperCID upgrade i was wondering: After flashing any of the ROMs do I reboot or power On manually or wait for the device to reboot itself as the message in the SupoerCID tool suggests:
If radio upgrade went fine, wait until your phone reboots and make sure
ActiveSync is enabled again (you should see green icon in system tray)
Click to expand...
Click to collapse

Stupid Q: How can i make the boot screen stay long enough so i can write it down?
My ActiveSync is 4.5 on WinXP

Rummage around in Start--> Setting --> device ID, and version and stuff...... they are there and you get the same info as on the boot screen... and it stay on longer ;-)
Sorry if a little vague but away from phone at the moment......... erkkkkkkkk
/me runs off to find it so this may get edited

akirainblack said:
TBH I don't know. But it can't hurt to try it, I SuperCID mine and it flashes perfectly each and every time.
I'm merely trying to make suggestions that may get a result.
Oh, you didn't tell me what the bootscreen said and what version of Activesync do you have on your PC?
Click to expand...
Click to collapse
I didnt Super CID just followed the instructions in LVSW 's first thread, applied each DL in order and "it just works" (c)

Thanks. That's where i got the infroramtion from b4. I just thought it might be different in the boot screen.
I now did the SuperCID unlocking and did the 3 upgrades again. after the 3rd upgrade i still have:
- WM5.1.342 Build 15096.3.0.0
- ROM 1.23.61.5
- Radio 1.41.00.11
Q again: Do I need to wait after the flashing or do i immidiately press power
(that's what i do when it says finish) or do i soft reset? Or what else?
Thanks for your help.

Hmmmmm just got me phone....... dont ask
Right CE OS 5.2.1413 build 17745.0.2.3
ROM 2.0.1.1
Radio 1.41.00.11
Sooooo.......
a) are you using LVSW (just to be sure)
b) have you grabbed the latest version posted on page 1 of the upgrading thread?
c) I let it restart it self after it finished flashing, it then reclibrates the screen etc etc
Also looks like you havent upgraded anything just yet ... follow the instructions to the letter and it "should" be fine

a) yes
b) yes
c) there might be the problem i waited 2 mins ans as it wasn't rebooting i just used the power button. How long should i wait aftr the WM6 install?

I soft reset mine directly after the screen goes black. So that should be fine.

Maybe it has to do with my boot loader:
When i go to bootloader i see:
IPL-0.50
SPL-1.07.0000
then it starts fading quickly. is this normal? I have the same fading effect when i install ste 2 the radio ROM. but i still have the new radio rom on as it displays as 1.41.00.11
I again tried to use the 2.0.1.1 it uploads very quickly (maybe 2min) and then it's still the "orange" screen and WM5 on reboot and i still have all my data.
What a I doing wrong?

No. Mine stays there right up until the upload to the phone starts.
Then I get a grey background with a blue progress bar.
What happens if you run Enterbootloader on the phone. Then connect it to the PC.
Then run the install program on the PC.
The first process didn't work.
You should have:
TRIN100
IPL-SSPL by Des
TRIN100
SPL-1.07.ds

Hmmmmm if all else fails try a hard reset on your phone and see what versions of what you have after that.
Did you use ANY form of unlocking prior to using LVSW rom?
/me suspects this might be casuing issues
The radio rom zoooooomed up to my phone and likewise the WM6
I cannt remember reseting the phone after flashing.... IIRC it just worked as in it finished then re-started and way hey off it went.
Also FWIW I just used the DL's in the thread without bothering with anyother boot loaders etc... ie extract flies in first DL into 1 folders, run them, ditto DL's 2 and 3.

New Tilt 2 ST-7377 Won't Flash.

I have tried flashing this new Tilt 2 several times. It, the PC software and the progress graph on the Tilt 2, always stay stuck at 0% progress, the PC app times out after about 5 min's. Then I reboot the Tilt2 and it comes back to its usual annoying self (with AT&Ts irritating splash screen) and works fine.
I have tried:
Rhodium-HardSPL_V2_00R3_185HSPL
Energy.RHODIUM.23569.Sense2.5.MaxSense.Jul.10.7z
and others with the same result.
I have even tried a hardware reboot (Power + Vol-) with a ROM image on the Micro SD card and all I get is the tri-colour screen with the word SERIAL near the bottom.
I have owned and flashed HTC Hermes, Ty-TNII and an I-Mate Ultimate 8205 with out any problems.
There must be a reason for this odd behavior and hopefully a solution.

Sparticus Palace said:
I have tried flashing this new Tilt 2 several times. It, the PC software and the progress graph on the Tilt 2, always stay stuck at 0% progress, the PC app times out after about 5 min's. Then I reboot the Tilt2 and it comes back to its usual annoying self (with AT&Ts irritating splash screen) and works fine.
I have tried:
Rhodium-HardSPL_V2_00R3_185HSPL
Energy.RHODIUM.23569.Sense2.5.MaxSense.Jul.10.7z
and others with the same result.
I have even tried a hardware reboot (Power + Vol-) with a ROM image on the Micro SD card and all I get is the tri-colour screen with the word SERIAL near the bottom.
I have owned and flashed HTC Hermes, Ty-TNII and an I-Mate Ultimate 8205 with out any problems.
There must be a reason for this odd behavior and hopefully a solution.
Click to expand...
Click to collapse
First off have you installed hardspl ? If not then you will not be able to install any custom ROM till you do. I suggest that you go to the hardspl thread and read on how to flash it, once you do then you can flash any GSM ROM you like..

You may need to install the enablerapinew.cab before the Hardspl will run. Just do a search on site and you'll find it.

read first ask questions later!!
yeah read, read, then read some more and then if you have question ask lol. it is very easy and i came on and asked a lot of questions that i ended up answering for myself when i read through the posts. [email protected] i can be reached any time and answer any question

Sparticus Palace said:
I have tried flashing this new Tilt 2 several times. It, the PC software and the progress graph on the Tilt 2, always stay stuck at 0% progress, the PC app times out after about 5 min's.
Click to expand...
Click to collapse
Did you ead the stickie?

try this. install it first and then try to hardspl.

I have this same phone, and everytime I try to flas it, it says the servers are down? Hmmmm.

Have you tried turning it off & on again?

Joshwah said:
I have this same phone, and everytime I try to flas it, it says the servers are down? Hmmmm.
Click to expand...
Click to collapse
same here servers down. the internet check is annoying.