Database Info

HELP! MDA wont boot!

Ok, I know that I probably messed something up...
I have a T-Mobile MDA and was trying to unlock it.
When it turns on it just stays on the boot splash screen and wont progress.
I cannot use the T-Mobile tool (or any other that I can find) to reload the original OS because they require that the ActiveSync make a connection which it cannot do until it gets past this point (unless I am not using the right tools).
All I see on my screen is:
IPL 2.26
SPL 2.26
GSM 02.25.11
OS 2.18.0.0
T-Mobile
Can someone please help me to resurrect my device?!

are you able to get to the bootloader mode? if you can get there you should be able to use the RUU tool anyway to get it installed.
had that happen to me once. so relieved when i found out that worked.

how
How do you get to that mode?

Got it!
Never mind... it is the camera button + reset, thanks... it is loading the original OS now.

Have I bricked my 8125?

I flashed my g4, using shell tool, to core 2.0n. After the hard reset it just sits at the boot screen listing ipl 2.25, spl 2.25, gsm 02.25.11, os 10.2.0.8.
When booting it to the boot loader I try to flash with the htc 8125 rom, but this fails with error 274 or 260.
Any help would be appreciated.

Splooshie said:
I flashed my g4, using shell tool, to core 2.0n. After the hard reset it just sits at the boot screen listing ipl 2.25, spl 2.25, gsm 02.25.11, os 10.2.0.8.
When booting it to the boot loader I try to flash with the htc 8125 rom, but this fails with error 274 or 260.
Any help would be appreciated.
Click to expand...
Click to collapse
Some G4's can't be flashed with the ROM on the HTC site, but can be flashed with the Wizard Love ROM. I'd try that. It's saved me several times.

Or try a hard reset before flashing another rom. See if it fixes the problem

If your phone makes it to the boot screen it isn't bricked.

It isn't bricked. It shouldn't be. If he flashed the Core 2.0n it's impossible that a OS only ROM would brick it because it doesn't touch the bootloader or the extended rom. Plus, from what i understand the ShellTool flashes OS only and that means even if the ROM he was trying to flash contained an IPL/SPL , then only OS would be flashed.

The fact that it even gets to the bootloader screen is proof enough it isnt bricked.... reinstall the carrier update and try something else.

Oh Sorry, he tried to reinstall the carrier ROM .. disregard.

I tried the love rom, but it errors out with error 300, invalid argument ( I think it looks like italian) =/
I've rebooted my pc, did a couple hard resets on the phone and verified the phone is being detected. The USB sync driver is loading. Seems every flash utility cant see the phone even when in the boot loader.
BTW it fails at the point where it tries to verifiy the information on my phone. if that helps.

Is your PC XP or Vista? If its Vista, it can't talk to a phone in bootloader mode. If you are XP then you should be fine but then I'm not sure why you can't flash the Wizard Love rom...

I'm using xp.

When you put it into boot loader mode, is USB in the lower left corner?

Splooshie said:
I'm using xp.
Click to expand...
Click to collapse
Have you tryed a hard reset ?

yes twice the second time when it rebooted I forced it to boot the boot loader before it tried to boot the OS.

And you have tryed taking out your SD card, and flashing the Wizard Love rom directly from the RUU (not with ShellTool) ?
You have enough battery ?

I have been using the flash utility, I don't know how to use shell tool without the scripts, and I can't install any of the cabs since it wont boot into the OS. I just tried on another xp machine and both the cingular rom utility and the love rom failed to communicate with the phone.
any other ideas?
edit: oh and I should have near if not 100% battery ( been plugged into a pc since the problem started and it was 100% when I started this mess. =) SD card has always been removed.

FYI, even though it has been plugged into the computer, it may not have enough battery. From my experiences, it drains the battery even if it is plugged in. Luckily, I have a second wizard so when my first battery drained (and wouldnt recharge even when plugged into the wall) I just popped the second battery in and i could flash it again. See if you can find a charger or something for the battery, and then once it is charged, let me know and I will give you a ROM i have that saved my other wizard (which is a G4 and no it isnt wizard love)
-Nstefanelli-

it seems to be charging, the orange light is on and the phone is off.

ok in a few i'll PM u a link to the ROM.. i havent used it in a while so i might have to gather it up..
-Nstefanelli-

well I tried the rom and it said error 300 this version cannot be used with your phone try a newer version (best I can figure from the italian?)

Splooshie said:
well I tried the rom and it said error 300 this version cannot be used with your phone try a newer version (best I can figure from the italian?)
Click to expand...
Click to collapse
Are you sure you don't have a G3 ? Hmm, I think you have a G3 and that's why it doesn't work. Try and flash the Tmobile 2.26
If your ipl 2.25, spl 2.25, then you defenively have a G3 CID UNLOCKED
Go back to Button's 1.05 ROM, CID UNLOCK it and then flash the Tmobile 2.26 and then flash Core 2.0n
Don't use ShellTool !

Error 260 Update Error

Hi
I get this problem too often and I dont know why and what I did do when I dont get it. This is the case.
Now I have flashed the g3 wizard with one of the wm6-manilla roms. I have succeded with this once so I have followed the guides with the unlocking and downgrading etc. Now I have downloaded a new cook and try to install it by starting the rom update utility wizard.
Problem is that the installation ALWAYS fails now. It starts, the device disconnects from activesynk, waits another 30 seconds then fails to restart the device so I get the dreadful Error 260 update error and the phone is dead. I remove the battery, restart the device and try again and my hair turns grey.
I figure I need to downgrade first so I try all the differens RUU's that are pointed out in the guides (CUSTOM__RUU_Wizard_1050412_WWE_101_11210_WWE.exe, ruu_prodigy_226102_22610105_022511_tmous_wwe_ship.exe, Xda_MiniS_LaunchROM_v154102.exe) but always the same problem.
What am I missing?
WinXP
AS4.5
IPL 2.26
SPL 2.26

Once downgraded and CID unlocked,a G3 device will remain CID unlocked forever,there's no need to downgrade everytime you flash a new rom.Just simply flash a new rom whenever you desire.So don't reflash Button's Rom 1.05 before every flash,its just required to flash once to get IPL/SPL 1.xx for CID unlocking,after which there's no need to reflash it again.
Error 260 is due to open port,so reboot your pc and Soft Reset the phone,hope it'll work fine.If you have reflashed Button's Rom 1.05 and downgraded,it wud be better if you perform the CID unlocking procedure again through lokiwiz02b or WST_4.2.2,after that upgrade to IPL/SPL 2.xx by either flashing T_mobile 2.26 or any official aku 2 rom,then upgrade to any wm6.1 rom.
You can even take out the battery and leave it for 30 minutes,after that put it back and try to flash.

Hmm.. now I have rebooted the pc and disconnected the battery for 30 mins. No luck. Still the same error.
There must be something I have missed. I have flashed with several roms before w/o any trouble.
I am connected to activesync as a guest on usb-cable.
Oh i didnt downgrade because it failed that too. So right now im on a wm6 manilla pretty good rom but the wifi's gone

Try flashing from bootloader:
* Hold down the camera button and then softrest without letting go of the camera button.
You should se a pretty tri color screen with IPL/SPL Information.
* Connect Wizard to PC using usb and wait for windows to detect the drivers if they are not already installed.
* Start your RUU and follow the steps.
Normally this error occurs when trying to flash under vista, if this is the case visit a friend who has XP and take some coffee

It gets worse im afraid.. and I am under XP.
Now the phone wont pass the t-mobile bootscreen. It gets stuck when showing the IPL/SPL information.
I fail to enter the bootloader. Hopefully im doing something wrong.
I have tried this:
1) Holding down cam-button and pressing soft-reset. The phone boots as normal but stucks at same place.
2) soft-reset and when sceen goes black, hold cambutton. Doing this makes the boot halt totaly and the screen remains black. Looks like it turns off cause the softreset wont work and I have to press the powerbutton to get life signs again.
How (exactly) do I get it into bootloader?

Evolution... i managed to do a hard-reset and got the phone to boot up again. So back to square one with not being able to use the ubs+ruu
hmm very strange.. in a desperate attemt to get into bootmode i held down the voice-button instead of the cam-button and then power-on. Not it worked! Mystic....
***
update! problem solved
In case anyone else reads this. I rebooted the pc for the 10th time, rebooted the phone at the same time and (a dramatic paus here) i pulled the usb-cable and placed it in another slot in the pc. And there it goes...
I dont work with computers... i work against them!

Htc TOuch Pro Stucked on Startup

i've already did a research.
Manage to Go bootloader.
But i cant seem to reflash my rom.
Stuck at 0% and theres an eror that came out.
It's strange.
For the first attempt it was a sucess and i managed to stock the Original SPL
So after doing that i tried the Hard-SPL.
Stuck at 0% eversince.

What phone do you have?
GSM or CDMA?
For almost if not all ROMs here you MUST HAVE hardSPL!!!

Oh i did have rom previously.
And i wanted to try lunacieROM
so i did flash it.
and it's stuck on the Black Screen after sucessfully reflashing.
So i went to the bootloader.
Reflash the Stock SPL
and wanted to reflash the Hard SPL
but it failed.
Its GSM.

Don't know why you flashed back to a stock SPL but I assume after flashing to a stock SPL you should FIRST flash your (or a) stock ROM and start from scratch (stockSPL --> hardSPL --> new ROM).

the problem is
after goin back to stock spl.
i dont think i can flash other roms.
including hard spl
or any other roms.
any idea?

And it get stuck at 0%
everytime i try to hard spl.
thats the thing thats been bothering me.

rullly said:
And it get stuck at 0%
everytime i try to hard spl.
thats the thing thats been bothering me.
Click to expand...
Click to collapse
What PC do you have (OS)?
You get a reliable active sync connection?
Did you try to put the phone into bootloader mode (tri-color screen) while DISCONNECTED from USB - will read "serial" at the bottom of the screen- and connect USB while in tri-color screen - should change to USB?
That are some basics to check and to test.
You COULD try to connect the phone in storage mode that it forces your PC to install Qualcom USB/NDIS drivers.

[Q] Can't flash? Stuck at bootloader

Hey guys'n'gals!
I got a QTEK 9100 and I'm stuck at the bootloader screen, it feels like i've tried everything but I can't start the phone.
So I read this tutorial:
forum.xda-developers.com/showthread.php?t=298613
And when I run the Wizard Love Rom exe it tries to verify my phone, but since it's at bootloader screen, ActiveSync won't connect, which results in error from RUU.
Am I doing something wrong or can someone please give me detailed instructions on how to fix this, since I really need my phone!
At bootloader screen it says:
RUU
IPL 2.17
SPL 2.17
USB
Click to expand...
Click to collapse
All help is appreciated!
Cheers / DiNozzo

Can I please get some help?

I am not sure what you are describing.
It seems like maybe you are trying to install the ROM but RUU won't connect because you are in the bootloader?
Does your phone boot into a ROM, or is is stuck in the bootloader?
If so, do not despair, as long as you see the bootloader your phone can be revived.
I will try to help but need a more thorough description of what you have done and what state your phone is in.

Yes my phone is stuck in bootloader, and every time I boot the phone, I get stuck in the bootloader. This happend after I got stuck in a ROM installation on 99%.
And ActiveSync won't connect since I can't get out of bootloader.
And I don't think that the phone is CID Unlocked.

DiNozzo5512 said:
Yes my phone is stuck in bootloader, and every time I boot the phone, I get stuck in the bootloader. This happend after I got stuck in a ROM installation on 99%.
And ActiveSync won't connect since I can't get out of bootloader.
And I don't think that the phone is CID Unlocked.
Click to expand...
Click to collapse
Some versions of RUU require ActiveSync, others don't. I found an RUU that works from just the bootloader, but I don't remember where. Perhaps it was RoryB's kitchen, I know he included an RUU, and I think maybe it works from just the bootloader.