Hi, all.
I've been reading a lot through these forums and I've learned a lot, but I don't seem to be able to fix this by myself. I have a Dutch T-mobile MDA Vario (WM5) that's over 3 years old so I'm not worried about voiding warranties.
A few weeks ago, my phone didn't want to boot anymore. I don't know if it's related, but around a week before the crash it had problems with finding the SIM card.
When I boot, it quickly gets stuck at the white background with gray/pink squares and the T-mobile logo. This is the data that's given (after a few factory resets):
IPL 2.21
SPL 2.21
GSM 02.19.11
OS 2.21.2.5
After that, it... just... hangs..., no matter how long I wait.
I tried to reset it to factory defaults (holding the three buttons + power button). The resetting seems to work, but then it gets stuck at the same screen again.
I came along forum.xda-developers.com/showthread.php?t=298613 <-- this thread, and I figured that I might as well try to flash it. I mean, if it doesn't work, well then at least I've tried. As you notice I'm new at this. I'm not afraid of electronics but flashing phone roms is new to me.
I can startup to the bootloader menu (photobutton + power) which tells me:
IPL 2.21
SPL 2.21
So, I've got a G3 device.
When I connect the USB cable to my pc (Win XP SP3), my PC gives the normal sound when a USB device is connected. the MDA nicely adds the text USB to the lower left of the screen. Nice. ActiveSync doesn't recognize it, but that seems to be normal, or so I read.
Following the thread's advice, I've downloaded the needed files and want to install them as ordered. First in the list is the Wizard_Love rom, so I go ahead and try to install it (from c:\XDA\final\). The first download link is broken, but at the end of the tread there is another link( to Wizard_Love_2.26.10.2_WWE_Novii_CF2.rar). The installer is in Spanish(?) but if it can give me back my phone, I'm fine with it. Besides, the readme is in English...
Then, after a short while, it gives me the following error:
ERRORE [300]: STRUMENTO DI AGGIORNAMENTO NON VALIDO
and some more text. I don't speak Spanish, but strumento will translate as instrument and non valido will undoubtedly be 'non-valid'.
It seems somehow that the communication still has some issues. I have just charged the battery, so that's not a problem here.
Do I have a wrong wizard_love rom? If yes, where can I get a proper one?
If not.. What else can I do?
Thanks in advance. You'll be my hero
You could always try to flash the original ROM and see if that gets you past the boot screens.
The installer language translates to Italian, ERROR [300]: INVALID UPDATE TOOL.
Try a different No ID Installer package, not the whole ROM just the No ID Installer.
Thanks! You have no idea how happy you made me..
Your comment on installing the original ROM sent me in the right direction. I went to t-mobile.nl and looked for updates (I shoud've done this much earlier). Where the hard reset failed, the official update worked flawless. I have yet to do the radio update, but I have my phone back! phew, 3 weeks with my old (by now- fossil) Samsung X100 made me realize how much I love this phone.. The QWERTY keyboard to begin with, my agenda, programs...
Related
I've had my Qtek 9000 for a week. I've spent most of that week installing software, and getting it setup (using a lot of useful info from this site).
This afternoon it locked up, and wouldn't respond to any button presses (including the on/off button)
Soft resets result in it powering backon, but stopping at the boot screen, after displaying the ROM versions in red text.
Eventually, I tried a hard-reset. Same thing happens - process goes ok until it displays the ROM version, when it just sits there. I've tried removing the SD card and SIM card and hard-resetting. No Joy.
I had just installed OzVGA, and was testing it when this occurred, but that is probably just a coincidence (surely a hardreset should fix anything bad that happened there?)
I hadn't at any point played with the ROM.
What should I try next?
And, does anyone know if I'm going to be able to get support for this in the US from Qtek? (I bought it in the UK), new
Thanks in advance.
-Steve
RE
Have you try taking out the battery, leave it for a while, put back the battery and do a hard reset?
It may work
Re: RE
FOSA said:
Have you try taking out the battery, leave it for a while, put back the battery and do a hard reset?
It may work
Click to expand...
Click to collapse
Unfortunately, no such luck
I'd tried that before, but the battery was only out for a short time. This time it was been out for at least 15 minutes.
Does anyone know if there's any kind of hardware or diagnostic test mode it can be booted into?
-Steve
How about updating/upgrading thr ROM?
This might work. you'll have to reinstall everything again, though
Jorgee said:
How about updating/upgrading thr ROM?
This might work. you'll have to reinstall everything again, though
Click to expand...
Click to collapse
Thanks - I may try that tomorrow. However, I'm a little concerned that updating it with a new ROM might invalidate the warranty (especially if it's not a QTEK ROM)
I was hoping that there was some kind of hidden 'diagnostic mode' I could try first, before taking that step. I've also been looking everywhere on the web, and I can't find anyone else that this has happened to. This makes me think it may be a hardware problem, though the way it just 'happened' seems more like s/ware.
Anyway, I'm out today so this will have to wait until tomorrow. My biggest concern at the moment is how I'm going to get any warranty support in the US. All I have at the moment is a very expensive brick!
-Steve
Have you tried entering bootloader mode?
BACKLIGHT BUTTON + POWER BUTTON + RESET HOLE
Then the screen will go blank then show the words SERIAL but you have to look real good because the backlight will be off when the serial is displayed. If it does go there, try hard resetting from there:
__ + __ + RESET HOLE
Hope this helps. WHat's your ROM verison/language anyway?
Jorgee said:
Have you tried entering bootloader mode?
BACKLIGHT BUTTON + POWER BUTTON + RESET HOLE
Then the screen will go blank then show the words SERIAL but you have to look real good because the backlight will be off when the serial is displayed. If it does go there, try hard resetting from there:
__ + __ + RESET HOLE
Hope this helps. WHat's your ROM verison/language anyway?
Click to expand...
Click to collapse
Thanks - but no improvement. I do get the 'serial' screen (with v1.00 displayed at the bottom), but when I do _+_+reset from there, it just goes back to the 'normal' Qtek boot screen and sits there.
Unfortunately, not having access to the OS, I don't know exactly the ROM versions etc. However, the info displayed in red text on the Qtek boot screen (where it hangs) is as follows. How do you interpret this?
R 1.03.00
G 42.36.P8
D 1.13.64 WWE
Thanks for your help - I'm hoping I can get this resolved without having to find out how to get support from Qtek!
-Steve
thefixer said:
Jorgee said:
Have you tried entering bootloader mode?
BACKLIGHT BUTTON + POWER BUTTON + RESET HOLE
Then the screen will go blank then show the words SERIAL but you have to look real good because the backlight will be off when the serial is displayed. If it does go there, try hard resetting from there:
__ + __ + RESET HOLE
Hope this helps. WHat's your ROM verison/language anyway?
Click to expand...
Click to collapse
Thanks - but no improvement. I do get the 'serial' screen (with v1.00 displayed at the bottom), but when I do _+_+reset from there, it just goes back to the 'normal' Qtek boot screen and sits there.
Unfortunately, not having access to the OS, I don't know exactly the ROM versions etc. However, the info displayed in red text on the Qtek boot screen (where it hangs) is as follows. How do you interpret this?
R 1.03.00
G 42.36.P8
D 1.13.64 WWE
Thanks for your help - I'm hoping I can get this resolved without having to find out how to get support from Qtek!
-Steve
Click to expand...
Click to collapse
You have a WWE (English QTEK ROM) but since you cannot enter bootloader mode, I don't think you will be able to update. You might have to return your device to where you bought it
Jorgee said:
You have a WWE (English QTEK ROM) but since you cannot enter bootloader mode, I don't think you will be able to update. You might have to return your device to where you bought it
Click to expand...
Click to collapse
Jorgee,
I notice (in the HTC 'confidential' manual I just downloaded) that there is a diagnostic program. Apparently, I put it on an SD card, and do Power+Backlight+reset to invoke it.
Do you know if that diagnostic tool is available anywhere on here, or elsewhere on the web?
Also - I wqas trying to find exactly how to enter 'bootloader' mode (after I have the 'serial' screen). Should it boot differently from here when doing a hware reset (_+_+reset)?
Regards
Steve
Actually, when you see SERIAL, that means you are already in bootloader mode. One question, what ROM do you wanna update to? QTEK, IMATE, MDA, O2?
Do the following once you get the SERIAL ON THE SCREEN:
1. Open active SYNC, then choose FILE>CONNECTION SETTINGS, then remove the check on the USB option.
2. Connect the phone to the computer with the sync cable. This should change the SERIAL on the device to say USB.
3. Run the ROM Upgrade (whichever it is you chose).
This shoulod update your device. If you are able to enter bootloader mode (SERIAL) this means that probably your ROM (OS) is damaged. Just update it even to the same verison then it should work.
If you get Country ID error while trying to update or any other error, just inform me, i'll walk you through the process.
Jorgee said:
Actually, when you see SERIAL, that means you are already in bootloader mode. One question, what ROM do you wanna update to? QTEK, IMATE, MDA, O2?
Do the following once you get the SERIAL ON THE SCREEN:
1. Open active SYNC, then choose FILE>CONNECTION SETTINGS, then remove the check on the USB option.
2. Connect the phone to the computer with the sync cable. This should change the SERIAL on the device to say USB.
3. Run the ROM Upgrade (whichever it is you chose).
This shoulod update your device. If you are able to enter bootloader mode (SERIAL) this means that probably your ROM (OS) is damaged. Just update it even to the same verison then it should work.
If you get Country ID error while trying to update or any other error, just inform me, i'll walk you through the process.
Click to expand...
Click to collapse
Hi Jorgee,
I'd prefer to go for the QTEK Rom (I'm assuming, from the info I posted above that I currently have 1.13.64 WWE). I'd like to go for the same or later version of this, but looking on the ftp site here I can't see ay QTEK ROM upgraders.
I have checked that when I plug in the USB I get 'USB' appearing on the screen, so I'm hoping that a ROM upgrade will at least work, even if it doesn't fix my problem.
One other thing that concerns me. When I plug into USB (with either a PC or the AC charger) the LEDs aren't lighting to indicate it's charging. Obviously, when during the flash upgrade I should make sure I have a reasonably charged battery. However, I don't know if I do (or even if it's currently charging).
-Steve
I guess leave it charged using the AC adapter for an hours, then here's the QTEK ROM.
ftp://xdaupload:[email protected]/Universal
Under Shipped ROM's you should see the QTEK.
If you cannot find it, tell me, ill send it to you. Trying to avoid this because it is almost 60MB in size
Jorgee said:
I guess leave it charged using the AC adapter for an hours, then here's the QTEK ROM.
ftp://xdaupload:[email protected]/Universal
Under Shipped ROM's you should see the QTEK.
If you cannot find it, tell me, ill send it to you. Trying to avoid this because it is almost 60MB in size
Click to expand...
Click to collapse
Thanks - I'd already found it on the devbuzz site, and am currently giving the unit an hour or two's charge before trying this. Wish me luck!!
-Steve
OK, here's what happened when I tried to update with the same Qtek firmware:
Initial dialog (that shows old and new (to be installed) firmware versions had blanks for all three firmware versions currently installed.
Started the upgrade, and left it running (couldn't bear the tension of watching!). Came back, and found the following error message displayed:
"Error 113: Extended ROM Update Error"
The update tool indicated that I should 'try again'. I'm currently re-charging the unit, and hoping (against hope) that this error was caused by insufficent battery charge.
-Steve
Okay, but maybe it just didn't update the extended ROM but the OS rom has been updated properly. After this error, try the __ + __ + reset button and see if it does boot fine.
Jorgee said:
Okay, but maybe it just didn't update the extended ROM but the OS rom has been updated properly. After this error, try the __ + __ + reset button and see if it does boot fine.
Click to expand...
Click to collapse
No luck.
I've also tried re-flashing a second time, but this time I watched it to see what happens
As the radio firmware is flashing, a message to that effect is shown on the Qtek screen. Once that is finished, the upgrade tool starts the extended ROM flash. At that time the Qtek's screen goes completely blank. The, after a minute or two, the upgrade tool reports that the extended ROM failed to upgrade.
I am assuming that normally, while flashing the extended ROM, there's a message on the phone's screen to say what's going on?
I'm also wondering whether to have a go at flashing the ROM in one of the other ways?
-Steve
I heard sometimes just flashing the Radio only might work.... Then after that you can flash the rest. Just extract the contents of the ROM to a directory. Take note of the ff:
Radio : radio_.nbf
OS : nk_.nbf
Ext : ms_.nbf
I just rename/move/delete the MS and NK files then run the update
Jorgee said:
I heard sometimes just flashing the Radio only might work.... Then after that you can flash the rest. Just extract the contents of the ROM to a directory. Take note of the ff:
Radio : radio_.nbf
OS : nk_.nbf
Ext : ms_.nbf
I just rename/move/delete the MS and NK files then run the update
Click to expand...
Click to collapse
Thanks Jorgee. Still no real success, but I think I might be getting closer.
I've tried the above (using both the original romupdate_ut.exe and MaUpgradeUt_noID.exe - same results with both).
I've tried each of the three files individually (using the ones from the shipped ROM, as downloaded above)
radio_.nbf always seems to flash ok
ms_.nbf always fails right at the start, and nothing appears on the phone's screen
nk.nbf almost worked. It started, and got up to 87% (tried this 3 times), with the update showing on both the phone screen and PC. Then it failed with error 112, leaving the '87% complete' message on the phone's screen.
Soft or hard reboots still result in us just ending up 'hung' at the boot screen.
Once again, thanks for your help so far. However, I am beginning to give up hope!
-Steve
I have the same problem with my Dopod 900 at post http://forum.xda-developers.com/viewtopic.php?p=207524#207524
But mine is no problem with EXTRom Upgrade
Waiting for your advise!
Thanks
truongia said:
I have the same problem with my Dopod 900 at post http://forum.xda-developers.com/viewtopic.php?p=207524#207524
But mine is no problem with EXTRom Upgrade
Waiting for your advise!
Thanks
Click to expand...
Click to collapse
I wish I had a solution!!! I've spent about 20 hours trying to get this thing to boot!
One question though - how did you get the 'boot option' menu up (allowing you to clear the registry etc). I might try that on mine (I had assumed that a hard reset ALWAYS cleared the registry.
Given that I was playing around with ozvga before this happened, there's a small chance that might help (though I think not; as I can't see how that would also stop the flash update working)
-Steve
Hi all,
Since last friday I'm the happy owner of an S200, until sunday atleast. After a soft-reset, initiated from windows, my device won't boot anymore. It hangs in the red-green-blue bootloader screen (says: IPL 2.09, SPL 2.09). I've tried soft-resets and hard-resets, but the device would consequently keep hanging in the bootloader.
So for the past few days I've been searching the web and just managed to update the ROM. I was expecting that updating the ROM succesfully would mean my device would boot again, but it still keeps hanging in the bootloader (saying IPL 2.09 SPL 2.15 now, so the update did take place).
Does anyone has any idea whats wrong with my phone? Or how to fix this? Please help.
* bump *
I've been searching further and tried to do a SD dump, but I'm getting the message I don't got enough rights to perform a SD dump. This meens my S200 isn't CID unlocked. Is there any way to CID unlock the device without the need of booting into WM?
The solution to your problem
Hello, if you are having bootloader screen right after starting your mobile (prophet) check if your camera button is depressed since i had the similar problem. In my case i had to disassembly the phone in order to fix it. Right after fixing the button it worked fine
hi syzzer,
i really feel with you - why? - i have the exactly same problem. after i tried to upgrade my rom from o2-germany to another one the device isn't starting anymore and hangs in the beautiful-colored bootloader. and now, if i just even want to re-install the same or another rom, doesnt matter which one, the s200 wont start again. i think this is a really unlucky situation for us to stand alone with our weak pda =) hoping for more help, otherwise we have to take up our warranty and try to get it fixed by the store we did buy it (if a rom-update damage is still in warranty )
good luck
budy!
awechris said:
Hello, if you are having bootloader screen right after starting your mobile (prophet) check if your camera button is depressed since i had the similar problem. In my case i had to disassembly the phone in order to fix it. Right after fixing the button it worked fine
Click to expand...
Click to collapse
in my case, the camera button is not pressed in... i truly don't know what to do hopeless? mhm?
greets!
budy!
hello Syzzer
I have the same problem, but i make a soft reset and it works.
Camera but + Com Button + Power
Wait until message appear.
You Get the message : For Hard reset press send
If you choose other key the system boots normaly.
I had already tried all your suggestions, but nothing seemed to work.
About a month ago I bought a Trinity. In the mean while, I forgot I had put my S200 in my bag and carried it around for a month. When I found it a week ago and started pressing random buttons, it suddenly booted and has been working ever since! The problem has gone as mysterious as it came. I can only imagine there was some hardware failure / dirt in my device that caused the trouble and is now gone / moved to some place it does not do harm. Because I already bought a Trinity, I gave the S200 to my brother. He's been using it ever since and did not have any problems. So keep your head up, there's hope!
I m also having the same problem
Now I am having the same problem, no button is pressed, and I can not install the NVID ROM
Actually I can install only a few ROMs, the NVID ROM was working before on my Neo perfectly but, I think it can be because I have changed many ROMs, from a month, actually I have tried different WM6 ROMs and I used NVID ROMs mostly for Step 1.
Now when I install any ROM, it shows a msg some nbf one after 80% or 95%
It can install the pdaviet first step ROM, but now the problem is that it hangs very much and it can not start Wifi, it has stopped working, a few more ROMs i have tried, but the WIFI is completely stopped.
When I press it in communication manager, it will show busy icon for a few seconds and will not start it in end.(I tried it in both WM5 and WM6, same problem, I also tried after soft reset and hard reset, the problem is still there)
Please someone help me out.
please help! I have made a wrong ROM Update for my Artemis. The result is that it doeasn`t starts anymore. I see only the start screen no more. If i make a SW or HW reset tahn i see a 3 colored screen and USB. But i don`t get a connection via usb to my compute`! How can i wake up my Artemis ???
tell use more what did you do and how did you do it?
what artemis is it?
what rom was it
Flash went sour..
You need the original ROM which was on your device when you bought it. What version (HTC, MDA, etc..) and what language was the original ROM?
please i need help too
I guess I made the same or a similar mistake that dr.moppi did. My machine is a Dopod P800 from mainland china with the chinese operating system. I flahsed it with PDAMobiz_Dopod_P800W_AKU301_v1.1.2_PowerMap. Don't really remember what the original ROM was but now when i turn it on it freezes when it lights up. On the screen, it says
IPL 1.27.0001
SPL 1.27.0000
GSM 02.67.90
OS 1.28.0.0
DOPOD
I don't get a connection through usb to the computer either. I am not sure if I did the hard reset correctly. Didn't understand the instruction on that "press the soft key left and right and soft reset at the same time." Anyway, you guys are all experts, can you help me please?
it should be the same as my problem
if i remeber than i used the same ROM Update :-(
I hope anyone could give us a solution, please.
@dr. moppi we can only help you if we know what version you had before.
@empathyvirus you have to look for the original ROM which, in your case, should be the Chinese Dopod ROM. Install that one and your good to go.
Without the original ROM the only thing left to do is: sending your device to your provider or contact and sent it to the guys of imei-check. Either way, you'll probably have to pay to get it fixed.
how to install original rom
Thanks for your quick reply Pyth. In the case I get the original ROM from somewhere, how do I install it if I can't get a connection between the phone and my computer? Can you advice?
Put your device in bootloader by pressing the record button and reset at the same time. If you have your USB-cable connected between your PC and your phone it will indicate a connection by 'USB' in the left corner of your device. Now you should be able to run the ROM executable and update your device.
thanks anyway
i tried but it didn't seem to work. anyway, i have troubled you enough and maybe it's best i just go to the repair centre of dopod and pay for a fix. i really appreciate your help though Pyth.
Where can i find the t-mobile rom its the MDA Compact III that wont start for me
hi all,
my jasjar had an error while upgrading to ranju 7.7,
i tried to reset, didn't came back,
hard reset neither,
i went to bootloader mode, i could,
i connected it again to the pc, it showed usb,
i tried to flash to Rom that was working previously it arrives to 7% than stops,
what should i do ...
i tried to flash with official rom, it says that the rom wasn't designed for this model, it has worked before...
please help...
Hi,
if you search in the ranju's thread there's the solution.
You could have the doc corrupted. Simply read the wiki,
you must use mtty to format your device and then reflash the rom you want (with radio rom also).
Had similar problem
upgrading Imate JasJar to Ranju 7.7, only at first it showed as success, then it started behaving funny during customization, then failed to customize, then got stuck on Windows 6.1 green flash screen and eventually refused to budge beyond blue Imate screen with versions info. I tried everything, a few dozens of hard resets returned me to the same problem, removing the battery didn't do much and mtty didn't show USB as available option, so couldn't even use that. I was pretty much stuck solidly and for a while. At my wits end I read that problems like mine are associated with DOC corruption and my JasJar is as good as dead, quite a few people suggested to those who are in the same position to throw their bricked babies away, as there is no economic solution apart from sending it for service where the corrupted chip may be replaced. What do you know, I followed wiki recommendation and entered a boot screen by pressing light power reset, then just flashed back to Ranju 7.6 and my JasJar was brought back to life!!! The update went without a glitch and everything is working fine. I guess I will keep the 7.7 on my O2 and 7.6 on my Imate for now, won't be risking an update anymore on the JasJar, don't think I have much hair left after all the pulling I did trying to bring it back to life. Hope this helps someone in the same predicament
jokove said:
hi all,
my jasjar had an error while upgrading to ranju 7.7,
i tried to reset, didn't came back,
hard reset neither,
i went to bootloader mode, i could,
i connected it again to the pc, it showed usb,
i tried to flash to Rom that was working previously it arrives to 7% than stops,
what should i do ...
i tried to flash with official rom, it says that the rom wasn't designed for this model, it has worked before...
please help...
Click to expand...
Click to collapse
does it turn on at all?
Does the device turn on at all after a hard reset?
Dude, I had a same problem it rectified though, check following of my blog...
http://jay-joshi.spaces.live.com/blog/cns!851D717EDFF14CEC!3258.entry
or
http://buzzdev.net/read.php?40,13307,page=1
Rarest_Kind said:
Dude, I had a same problem it rectified though, check following of my blog...
http://jay-joshi.spaces.live.com/blog/cns!851D717EDFF14CEC!3258.entry
or
http://buzzdev.net/read.php?40,13307,page=1
Click to expand...
Click to collapse
Problem resolved?
I have read and read and read. I have "bricked" my phone in the past and fixed it. I have used, tested, and flashed many roms from this site (Thanks to all cooks for their work!) but I still consider myself somewhat 'new' to troubleshooting.
I woke up this morning to make some important phone calls today and as luck would have it, my phone was stalled again. It's been doing that for a few weeks now. My last flash was Open Touch 5.0 UL I believe (either that or 5.2 biggy) and it has been working great except for the occasional freeze.
EDIT: Forgot to add, the actual problem is now it won't boot up after it froze this morning. Just sits at the boot screen
So I've tried my other methods of fixing it... /edit
Except this morning nothing is working. I have tried flashing with Orig. T-mobile ruu, tried SD flashing with the RUU_signed.nbh, tried restarting the computer, phone, removing battery and sim... NOTHING! When trying the sd flash (which I've never done before today, it reads and tells me to push the down button but then goes to bootloader screen and just sits there. With the RUU I'm getting err 300 but I'm using the SAME RUU (4.10...) that I've used in the past to reflash my phone AND tried the new one (4.26...)
Possible problem: Does it matter what kind of usb cable you use? I don't have the normal one I use as I am not home but I figured usb is usb...
I've read about it being a motherboard issue, how common is this?
I've read somethings about MTTY, would this apply to me??
Please help, anyone who has any suggestion, I'll try it!!
Stats:
IPL 4.10.0002
SPL 4.10.0000
NOT hard-spl'd
Wing w/ Open Touch Project 5.0 or 5.2
actualy the sd method needs hard spl thats all i can really provide
I appretiate it, that I did not know... I could barely find anything on how to do it even.
im having the same problem bt instead of freezing da screen jus goes different colors or jus goes gray and stays der
Thats basically what mine did. The colors would get messed up and no matter what button i pressed it would not do anything. My advice to you edrift, is BACK UP YOUR STUFF NOW and reflash it asap if you can still reboot. I can get into my phone at all now.
yea i tink i might jus throw my phone away.dis is jus gettin rediculous