Database Develop

Someone help me please

I tried to update my rom and it was working, until my laptop turned off. (I forgot to plug in the power cord). So I tried it again, and it was stuck in bootloader and so I tried to update it using a Official Cingular Rom. But it gives me an error 260 saying cannot connect. I then tried to use mtty (one of the guides on here) but there's no USB option. I tried this on 3 different computers. Any suggestions please?!

To access mtty with USB option, you need to kill the wcescomm process (or disable USB connection in ActiveSync).

Thanks for the reply but I did kill it and disable usb connections. Stll no USB shows up. Im using a pretty new laptop with XP

Are you sure your Wizard is in bootloader mode when you start mtty?

It's always in bootloader mode when it's on since the Rom Update Failed ( computer turned off).
I really don't know why I have this problem. It was working before, but then it failed, and now it wont connect

Try to flash it on another computer.
I suspect there are problems on the USB ports (And/Or software issues) of your computer...

In my first post I said I tried to flash it on 3 different computers ( I meant laptops.) I dont know why it wont work now though. It worked yesterday

If it helps before it gives me the 260 error it says my USB device is not recognizable.
Please, does anyone have anything?
Im getting realy worried and my warrantys expired

help me stuck on bootloader
what do i do when i downloaded mtty? im am stuck on the bootloader screen due to a 98percent error but right now i cant do anything but stay on the bootloader.
I downgraded so im back to
IPL 1.01
and SPL 2.25.
HELP me get out this screen please? I've tried almost everything i could search on this forum. thanks in advance. and thanks for the hard work on the great roms you guys have!

Is there any other way to revive my device? I've been trying for the past 2 days and it's still not working
TheTop- Flash a official rom to it

I have tried official Roms like the one from the htc website, should I just keep trying even if I get error 260?

dunno if it helps, but make sure that you're battery is charged at least 50%. It seems to be one of the requirements that are needed when you normally flash with the RUU after activesync hookup. I know that when I tried flashing below 50%, the program wouldn't work for me and boot out.
if it's below 50%, look for a friend to charge it and try again.

Stuck in BOOTLOADER ! I tried everything

i just spend 2 days searching for a solution, i use the search option but without results..
I got a mda g3 device ipl spl both 3.08
i flashed it with a wcrx2 rom wm6 based, but during the flash it stucked somewhere and then it went to bootloader.
If i turn it on u get the bootloader screen..
I tried several roms even the original ones, but NO CONNECTION with USB !
i get the Connection error !
is there someone who know how to solve this?
id rather paypal u 25 euros for solving my problem then send it to customer service t-mobile !

come on guys
i really need some help here !

you can still flash from bootloader mode
you can't connect via activesync but you should be able to connect still
make sure you don't have any virus protection firewall preventing the connection
then try flashing the button rom or something

ewatylerdurden said:
come on guys
i really need some help here !
Click to expand...
Click to collapse
First verify if your phone is establishing connectivity with pc through usb cable.Get into bootloaders and connect your phone with the pc via usb cable,verify if small usb appears at the bottom of the bootloader screen,if it appears then run the Ruu,if doesn't appear,then you have a either usb cable fault or mini usb port of the phone is damaged,it maybe that usb slot of the pc is not working,try with other usb input of the pc .
Cheers !

first i thank u for the time u took to help me out..
i tried several times to flash my rom and yeah i see the USB text in the corner of the screen, so im 100% sure the USB is working..
but im gonna try to flash it with the BUTTON ROM
are there other roms wich i can use for flashing my mda?
i mean wich roms are good for flashing my mda that stucked in bootloader..
cause the other ROMS didnt want to connect with my mda !
i was halfbaked when i typed this text..so sorry for my grammar et..

HELP!! I think my Wizard is a Paper weight! Bricked!

HELP PLEASE!!
Ok so i think i bricked my wizard!
I have the t-mobile MDA wm5 unlocked g3.
I've flashed it to the WM6 Rom and everything had been working well, except there was no MMS feature on the phone at all which sucked! . My girlfriend thought it would be better if she did the "windows mobile update" icon feature that was on the phone to speed up the phone....She downloaded the updates & my phone shut off!! When it rebooted everything seemed normal...
1st.
T-mobile screen
IPL 2.26
SPL 2.26
GSM 02.25.11
OS 10.1.0.811
-Then i get the green windows mobile splash screen, but after i get an error message!!
*Device Authentication*
“Device authentication failure. Please contact the product manufacturer. For reference, please provide your device ID.
3563820017905901 38000050bf3f5173”
Ive tried to boot in safe mode to try & flash my phone again but for sum reason my computer wont recognize my phone is plugged in! What do i need to do?!? Please help, any help is thankful!

is not a bricked wizard men
easy men easy... but please tell to your girl dont push everything that she dont nderstands... Everybody knows that upgrade official is only for original OS like windows XP or VISTA..
Firs of all
Put your Wizard on bootloaders mode... plug in via usb the PC Active sync wont recognize your phone.. then run the original shipped Stock ROM and then your Coocked rom...
But if the PC at the same time you place your Device on Bootloaders and plug it via USB... shows a pop up message that said Windows cant recognize your device or unknown device or something... Restart your Pc... Hard reset your PDA... and replug your Device as I said it before... if not check your USB cable maybe a broken cable failure...
IF NOT?????!!!!!!!! then Use another PC with XP!!!!!
If it still on his not reconized message you are in serious problem but your girfriend Too...
Good luck

Easy..."Device Authentication failure" is caused by your ROM. Just flashing another custom ROM and the message should go away.

I'm surprised that the chef that made your WM6 rom left the Windows Update feature in there, it was bound to crash a cooked rom, since the update service never worked properly anyway.
I'm sure flashing another rom will resolve this.

yeah, flash the rom (you might want to try WizFlo 20273 v6.1.1.3 - i'm on it, and loving it). heck, you can even do a hard reset and that would probably resolve it.

What on earth am I doing wrong when flashing?? *SOLVED!*

Hi, first of all let me begin by saying that I have spent a long time reading around through the guides and forums about flashing rom/radio to my Rohdium but still face problems. I have successfully flash my old TyTN II and Orange E650 but am at a loss as to why Im struggling this time round!
I flashed the Hard SPL which went 'fairly' smoothly, got there in the end after having problems on WIndows 7 64bit and then succeeded using Xp 32. However when trying to flash a new rom and/or radio I am greeted with an error, that being Error 284. I have tried like I say on Win7 64, Xp32 and when the error pops up my phone gets stuck on the process bar and forced to pull battery out. I then put it back in and it freezes on bootloader. The RUU software trys to recover but it is a loop of the same thing happening (attempts and then crashes). The only way to get out of this mess was strangely reflashing HardSPL which recovers it and allows me to boot to Windows. I have tried flashing a radio and/or rom whilst in sync within windows, I have tried flashing when manually forcing the phone to enter bootloader, I even paid the £10 to get the unlocker which would patch the special radio but that even returns the same error. I have the sim card out and storage card, battery charged over 50%. I even tried the Mtty program (sorry if mispelled, at work now and can't fully remember name!) when it was stuck at bootloader and using the "boot" command it boots as far as Touch Pro 2 logo but then doesn't progress, then i resorted to reflashing HardSPL which allowed me to boot properly. I just don't know what else to try!
Like I said Im sorry if this is obvious to someone but I have tried alot!
Many thanks in advance if someone could help!
* Update: Just tried flashing a radio on my works computer (XP 32) and it flashed no problem!? Wonder why my operating systems had an issue?
** SOLVED! ** - got home and randomly tried again on Win7 64 without using my USB extension cable and plugged into a different USB port directly and it worked! Faulty cable maybe, bad luck, who knows, it works!
Thanks.

Sound like maybe your RUU/update utility may have gotten corrupted. I would try to re-download the rom you want to flash over to your home pc again and try to re-flash.
If that doesn't work, you can always flash your rom through the storage card.

hmmm yea thats possible, will try when I get back in couple of hours thanks! Just seemed weird how nothing was working, different roms (cooked roms or shipped roms) and even the security/sim unlocker that I purchased......mystery!

USB cable tends to go bad easily! That might be the reasion why!

X1 huge problem: starts with bootloader, not recognized by pc via usb

Hi guys, for several days i've been trying to come up with a solution regarding my X1.
I have read many similar posts implying different solutions with this problem, tried tons of methods to make it work, but unsuccesfull.
Anyway...a few days ago I recieved an X1 from my cousin. No hardware problem, scratched or dropped device.
The main problem is (i've met this problem on different posts, but no one could find an answer): the X1, when booted, it starts on bootloader/ flashscreen (the 4 colour screen) everytime showing info :
KOVS110
SPL-0.78.0000
MicroP1-787
MicroP2-707
If I connect the X1 to the PC via USB, or if I plug the charger in, it boots normally, and the phone works just fine. ANOTHER PROBLEM is that the PC does not recognize the X1, so I cannot HardSPL it using OliNex....!!!!?!
I know the current SPL version is a SSPL, so I can't flash custom ROM's. It's frustrating because I've spent days trying to get a solution, I'm not a newbie on this one, I've done it many times before.
I used up all the methods I could think of, including flashing an official ROM, radio, and returning to SSPL (I recogn it wasn't the case...but still). In this moment, I flashed it to Official Vodafone UK bla-bla-R3 doesn't matter, because it is not branded.
I really could use your help, guys, because I can't take my charger or usb with me everywhere I go just to start my phone, in case I need to turn it off or something.
I'm stuck, and don't know what else to do, I know the procedure to HardSPL and flashing a custom/ official ROM, but I can't go on because of the fact that by any ways, I can't get the X1 to be recognized by ANY PC. Tried ActiveSync on XP, WMDC on Vista and Win 7...the Mitty procedure is buggy, couldn't get pass the recognizing of the USB (lol !!!!)....also tried using SE Update Utility Service, no result since the X1 is not recognized... It already has SPL 0.78.0000, so I guess SEUS fails from the point of idea.
I've also tried using X1-Manual-SSPL.exe....no chance..!
Tried also to flash from MicroSD a custom ROM (knowing and assuming through the absurd that it will work inspite having SPL 0.78.0000), but it always get's stuck at the grey "Loading..." screen
I would really apreciate some proffesional help, because I'm starting to think I'm not skilled enogh for an X1 ))) I don't have the necessary resources at this point to bring the phone to a GSM Service
So...kindly...PLEASE HELP !!!

How about usb cable? is it still good? have you try to connect the usb with other devices?

the usb works fine, I've tried different usb cables and on different PC's with the X1. As I said, I used up all the ways possible to make it work...

some guys on other thread have the exact same problem: http://forum.xda-developers.com/showthread.php?t=1611223
That's mysterious...