A friend of mine recently took her T-mobile MDA Compact to a High St vendor to have it unlocked. Whatever they have done to it, they appear to have buggered it up properly.
She gave it to me to try and fix it.
When I got it, it would only turn on to the splash screen with the ROM versions displayed, and wouldn't load any further than that. It also wasn't detectable by Active Sync, so I had no choice but to put it into bootloader mode, and try to restore the ROM on the device in this way, as there was obviously something wrong with what was on it.
The upgrade started fine, using the ROM off the T-mobile web page, completing the Radio Rom upgrade fine. However, when it got to 10% of the Extended ROM, an error occured, and shut the program down:
ROMUpgradeUt.ex.exe has generated errors and will be closed by Windows.
You will need to restart the program.
An error log is being created
I tried this a couple of times with the T-mobile Rom, and got the same result, at exactly the same point.
I thought that perhaps there may have been a problem with the T-mobile UK version of ROM, so I thought as it was pretty messed up anyways, I would try loading another T-mobile ROM on to it. I trie both teh German, and the Dutch registered T-mobile ROM's, getting the exact same error during the upgrade, at exactly the same point.
I then changed computers to try and rule out any possible problem there, and the same result again.
I then proceded to try using the iMate ROM, changing the MaUpgradeUt file to the no ID one, as suggested earlier in this thread, and again got exactly the same result, with the second ROM upgrade stage stalling, and cancelling at exactly 10 again.
Can anybody offer me any assistance with this, or any ideas, or id it possible that the High St vendor has buggered it totally??????
And to boot, the store charged my friend £50 for buggering up her phone, when it is a pretty simple, 5 minute process to unlock one at home!!!!!
I'm no expert but just a thought, it is definately an mda compact and not an mda compact II isn't it? They look the same but are not.
pjam said:
I'm no expert but just a thought, it is definately an mda compact and not an mda compact II isn't it? They look the same but are not.
Click to expand...
Click to collapse
No, I am very sure that it is the original T-mobile UK MDA Compact. I actually have one of each of the Compact and Compact II myself.
Related
Hi,
I am using the 1.11 Rom. Unfortunately, my mdac's audio quality suffers from a kind of distortion. You almost cannot hear it, when somebody speaks soft, but as soon as it gets a little louder it is not very pleasing to the ears.
I tried to have it repaired, but they could not find anything.
So, I had the lady at the T-Mobile shop in my town make a test call.
She immediately noticed the distorted sound. We also changed the SIM to a new one, but it did not help.
So, finally, they would swap the thing toworrow.
But, as I stated....
So, is it possible at the moment to downgrade to a German ROM (T-Mob Germany or even better T-Mob Austria?)
I also want to add that my brother owns the same device, but he still has the German Rom, only the radio update to 1.05 was made...
Thanks for your answers and help, Günter
well, sure you can downgrade... no problem in doing that!
it's the same steps when upgrading but instead of upgrading the new rom use the old one.....!
the only problem is that it seems almost impossible to get an original T-Mobile ROM. But if you have a brother...
@pietrucci:
You mean, I can make an image of my brother's mdac's rom?
And then put it back on my mdac?
Is that possible?
Guenne said:
@pietrucci:
You mean, I can make an image of my brother's mdac's rom?
And then put it back on my mdac?
Is that possible?
Click to expand...
Click to collapse
Yes it is! You need ntrw.exe (v 2.0) and a sd-card. With the ntrw tool you can write your brothers ROM onto your computer (if you have a sister with a MDA, you can use that one too! I mean her MDA, not your sister herself ofcourse). And with the same ntrw tool you can make a bootable sd-card with this ROM. And then put it on the other machine. Look in this forum, there are several threads. For example, look at today's thread: http://forum.xda-developers.com/viewtopic.php?t=19500
@pietrucci:
Thank you (concerning my sister, unfortunately I don't have one).
I decided to go with my mda til the T-Mob Update which hopefully should be out in April (they didn't say 2005.)
It got a little better with my new SIM, and the guy in the shop allowed me to use his device, same ****ty audio quality (of course, he had no Radio Update :wink: )
So again, thank you very much
First, my palm 750 was having the problem that it got stuck like always, and when it finally started working, i had no signal at all, radio on, turned off and back on, hard reset, soft reset, nothing. So then I saw that there was WM6 and upgrading sounded like a good idea. Started looking for the rom and i found the voda WM6 rom, followed the instructions and when it was upgrading the battery felt cuz I didn't put back the cover (my bad). After that, I tried to turn on the fone and all I got is the Bootloader screen, have read a lot and all the answers are to format the card to fat32, or to switch computers, I've used like 3 different cards, checked on 3 pc's, used another card reader and all I got is the boot screen, if I put the card in it says loading, press the end call botton, start updating and then got stuck after splash1 and bootloader says ok. What I'm wondering is if the it is a hardware problem was before the update I had no signal, and now it got stuck on the gsm part of the update. Any Ideas?? this is a really expensive paperweight!!!!!
A couple thoughts...first, when it gets to the GSM portion of the flash it takes significantly longer than the others, so you might just need to be a bit more patient. Run it again and leave it alone for 10 minutes.
If you can get to the bootloader screen, your device is not bricked. You didn't mention what carrier your device is from..is it a Vodafone device? If so, you might be able to just connect the device to your PC while it's in bootloader mode and run the full Vodafone updater on your PC. There's a chance that this method might not work if a partial flash has left your device in a state that the PC based updater can't identify.
pirulino23 said:
First, my palm 750 was having the problem that it got stuck like always, and when it finally started working, i had no signal at all, radio on, turned off and back on, hard reset, soft reset, nothing. So then I saw that there was WM6 and upgrading sounded like a good idea. Started looking for the rom and i found the voda WM6 rom, followed the instructions and when it was upgrading the battery felt cuz I didn't put back the cover (my bad). After that, I tried to turn on the fone and all I got is the Bootloader screen, have read a lot and all the answers are to format the card to fat32, or to switch computers, I've used like 3 different cards, checked on 3 pc's, used another card reader and all I got is the boot screen, if I put the card in it says loading, press the end call botton, start updating and then got stuck after splash1 and bootloader says ok. What I'm wondering is if the it is a hardware problem was before the update I had no signal, and now it got stuck on the gsm part of the update. Any Ideas?? this is a really expensive paperweight!!!!!
Click to expand...
Click to collapse
Thanks, and well it is a Cingular Treo, and I left the updater running several times for more than 3, 4 hours until the battery run out, and well, keep being stuck at gsm part, tried the tool that is on the update but after some % it got disconnected, any ideas???
im no expert. but if your using it with cingular (att) and you used a voda rom, i dont know how it would work in the first place without some sort of cid unlock? correct me if im wrong.
anyway. I would try that leaked att rom it it were me.
kapster said:
im no expert. but if your using it with cingular (att) and you used a voda rom, i dont know how it would work in the first place without some sort of cid unlock? correct me if im wrong.
anyway. I would try that leaked att rom it it were me.
Click to expand...
Click to collapse
Well First never do a rom update off the battery second I have a att/Cingular 750 had leaked att on it ran fine then moved to the voda rom still fine
If the ATT rom doesnt work search for a WM5 Rom I think someone said it was posted in here. If that doesnt work, the first rom update I screwed up killed my device I called ATT said I tried to install the audio update and it killed my device they sent a new one and then i up'ed the ATT rom GL.
mtty perhaps?
I got my Kaiser last week, well actually it's a T-Mobile MDA Vario II (what a terrible name!), and quickly found this site which seems very interesting. Being perhaps a little too impulsive I attempted the ROM installation sticky at the top of the page. First step: HardSPL, I got a white screen. Tried the fixed Jumpspl in the sticky but again, white screen. Fortunately after a soft reset the phone was back to normal but all of a sudden I'm not so confident about ROM flashing. So I'm wondering, before I try to sort out the white screen problem, has anyone actually bricked their Kaiser whilst attempting a ROM flash? The FAQ says:
Q: Can I brick my phone by flashing a ROM?
A: To be true… YES. But if you follow all instructions, it is quite implausible that your device bricks.
But what are people's real life experiences?
.
If you don't mess with the boot loader, it's unlikely you will brick your device.
It possibly won't work because the T-Mobile MDA Vario II isnt a Kaiser it's a Hermes aka TyTn.
The T-Mobile MDA Vario III is the Kaiser aka TyTn II. Might want to check your model number again.
Crobe
V1615 aka Kaiser
Rom : Alex's
Radio: 1.27.12.17
Sorry, my mistake. I definitely have a MDA Vario III aka Kaiser, I just missed off an I from the original post.
if you wanna flash, flash now, coz if it really goes wrong, just phone t-mobile and tell them you got the fauty phone and get the new one, I think there is a 14 days worrenty for faulty phone.
I mess up my o2 stella 2 months ago when I made mistake due in flash progress, but it was my faut anyway coz mI didnt do it correctly. and I playing dumb and complain to o2 say "you'v send me a bad phone", then I got new one within 3 days. and this time I fellow the rule and flash my phone step by step, now I have my kasia with dutty's rom, it's way better then o2's orignal rom.
Good luck
I have flashed my 8525 (previous device) and the Tilt multiple times, and I have never bricked them.
The only reason I can say be careful is... IT'S ADDICTING!!!!
I've flashed almost every variant of ROM out there.
Gone through all of Dutty's, 3 of schaps, q-mobiles, etc...
These guys are always working for a better ROM, and it makes for a very exciting week running a new ROM every day
That's all... Enjoy!
Never bricked one, Ive always found the answer to fix my phones
Guys,
I had a screen fault and sent my Kaiser away and the repair centre have flashed it with what appears to be an official T-Mobile UK 6.1 ROM (it's showing as CE OS 5.2.19212 Build 19212.1.0.3).
Is this any use to anyone before I put something else on the phone?
As an aside, I made a hash of restoring the phone back to factory for the repair and sent it with a custom splash screen and HardSPL installed and they still repaired it.
Mindful of the custom splash I did make a point of fully charging the battery and sending it switched on, so I dunno if they noticed or not but either way it seems to be working now
are you able to export it ?
what hardware are you using ?
As it happens the fault has reoccurred.
I'm absolutely raging with them so it's going back to the store again tomorrow.
When I get it back (again) then yes, i'll gladly export it if someone can provide some hints or a link to a decent guide.
Never mind a custom splash screen - from my experience of T-Mobile, they probably wouldn't have noticed if you'd sent them a cucumber in the Vario box. They would probably have tried to re-flash the ROM onto that...
There are threads on ROM dumping, although I don't know anything about it myself.
I would be very grateful for a copy of this ROM.
Good luck
Thats a shame I have been hoping to get the 6.1 update!
Just received a replacement Vario 3 and it has Windows 6.1 !! and radio 1.70.18.02 but unit keeps rebooting when putting the pin in.
just removed pin and now working!
Anychance of a ROM Dump? Software version?
SPL details?
Cheers
If anyone's still interested in this, I also received a replacement with this on, and have attempted a reconstruction:
http://www.megaupload.com/?d=99MBNM1T
Not sure if it'll work, as had some issues when reconstructing, but I don't want to try it as I can't get the rom again anywhere else currently.
Let me know if anyone has any luck. There's no radio cooked in - it came with 1.70.18.02.
Monkey0 has successfully reconstructed this rom over in this thread:
http://forum.xda-developers.com/showthread.php?t=421896
So if you want the official T-mobile WM 6.1rom for Kaiser, you can have it!
Hello,
I recently got a O2 XDA diamond pro with original (sucking) O2 ROM/Firmware. I also tried to unlock the phone to be able to Flash the Original HTC-Firmware, because I experienced the O2-Firmware very unstable!
While my first try to use Olinex-Unlock and other tools (of course use with my phone!), I once bricked the phone. Even Hardreset-Tricks didn't work anymore, after the Screen disapeared with strange stripes. It was fully dead (not even power-on gives any signs of life). Before that the phone worked fine (except the O2-Firmware bugs).
I was able to get a new phone through warrenty by O2 (which wasn't that easy because I didn't buy the phone myself!!!). After sending in the phone, they told me that my original phone has been damaged (main-circuit) for any reason. I can't believe it was my fault / because of any software trying to unlock it, that could have also damaged hardware that way?!
Now I'm not satisfied with the O2 ROM (strange errors, bugs, hangs too often even when opening a menu). Are there any other O2 / German users had problems unlocking their "O2 diamond pro"? Maybe it was just bad luck that my phone bricked trying unlocking the first time?
What would you (other "diamond pro" users / xda-experts) advise me? Is the original HTC Firmware worth doing it?
Best regards
Gabriel
I have a UK o2 Touch pro, i flashed mine to the latest HTC firmware.
All the errors with the o2 rom annoyed me too much. I would get an error everytime i slid open the hadware keyboard. I also found it very slow.
No problems since upgrading with mine.
I 1st flashed mine with hard-spl then with the HTC firmware, didnt have any problems.
I did the same like bod001 with my german XDA Diamond Pro. Worked really good and the HTC firmware is a lot better than the one from o2.
Also no big deal to convert back to o2 firmware and apply the orignial spl back. I had to do this because I send mine in for repair (because of this: http://forum.xda-developers.com/showthread.php?t=447891 ).
I think it's worth doing it. As said I had absolutely no problem to flash.