Database Develop

MDA III ROM

I have tried to warn people out there that you cannot just buy an MDA III for USA use, unless fluent in the German Language.
You have to either wait for the i-Mate PDA2K or make certain that the MDA III is flashed by the supplier prior to forwarding the unit from overseas.
Also be aware that when flashing the MDA III with an English ROM, this is in essence a hack, and most likely will void the T-Mobile Germany device warranty.
How do I know all this, because I own an MDA II, and I went through all of this one year ago.
I'm now waiting for my i-Mate PDA2K.

indeed..
Also bought one from T-Mob Germany and was unsuccessfull trying to run the english rom on my device.
I got this message from a source I don't know up to which level I can trust, supposedly coming from an HTC engineer. If that's only half true then is anyone interested by buying a brand new german MDAIII :? ?
The HTC BlueAngel device was specifically added some customization upon operators requests to prevent unlocking and Rom change out of their control. Without entering into too much details, the memory mapping of each device is adapted to the operator by an hardcoded memory address translater. This translater uses a private key generated by operators and embedded into a component (a single-die chip KFG1216Q2M that can be flashed only once). Result is that attempting to flash an incorrect ROM or attempting bootloader insertion of a different language ROM result in no operation being accepted by the BlueAngel bootloader.
Click to expand...
Click to collapse

i spotted an xda3 in liverpool uk on saturday it was in english

Will a QTek do ???
I don't know if it interests you but in Portugal you can buy them branded Qtek9090 and they come in English.
...or i'm i just misreading this post ?!?

This all came before we figured out how to update the Tmo German to imate english. The threads were lost in an Oct disk crash.

lol
my mistake then.....sorry.....

A problem gruuuuu. I can't fix with all tools

hi, everybody
I have a Wizard. But yesterday, when I turn on it, i see :" Data Crashes. Plese contact your service Center" with this title: "SIM LOCK" in the screen.
I used awizard, Lokiwiz to unlock it. But nothing at all
please help me

No body help me???? or not have solution to fix this prolem?

try to start it over without a sim-card....what happens...!?

it's oke and I can use it same a pocket.

I am experiencing the same issue. Did anyone find a solution to this? No matter what I use Lockwiz etc... It still wont work. Pls Help
Thx

Beside you is possible violated area CID.In the field of CID is found SIM and CID lock.The Area CID -unique for each device .Lokiwiz -does not calculate new this area -he only modernizes given in this area.
This inscription appeared After what action?
p.s.
There is command In bootloader which destroys the area CID and others.
Check Your IMEI.If IMEI does not coincide -possible you have started this command.

how can solve it?

wlinsong said:
how can solve it?
Click to expand...
Click to collapse
I unsure that you this will help - but when I on C500 has deleted the area CID and got such message - I have restored only with the help of unlock http://www.imei-check.co.uk/ imei-check -anew calculates the area CID - unlock works through bootloader and so he does not modernize but anew calculates this area.
Try to talk with itsme in this forum -he has said that possible to calculate the new area CID -but has not described as.
p.s In Typhoon C500 and Wizard is used alike method SIM and CID blocking.
But aside from this unlock changes bootloader
For you http://www.imei-check.co.uk/m3000unlock.php

arc said:
wlinsong said:
how can solve it?
Click to expand...
Click to collapse
I unsure that you this will help - but when I on C500 has deleted the area CID and got such message - I have restored only with the help of unlock http://www.imei-check.co.uk/ imei-check -anew calculates the area CID - unlock works through bootloader and so he does not modernize but anew calculates this area.
Try to talk with itsme in this forum -he has said that possible to calculate the new area CID -but has not described as.
p.s In Typhoon C500 and Wizard is used alike method SIM and CID blocking.
But aside from this unlock changes bootloader
For you http://www.imei-check.co.uk/m3000unlock.php
Click to expand...
Click to collapse
WOW worked like a charm! Thanks I thought I had a brick!

I hope that this will help you.
I met several times like you situation on Wizard -but nobody did not describe after what action this has occurred.
It is Enough that 1 byte changed in the field of CID and she will be bad.
Possible during unlock or as a result other action (for instance action what other program ) has occurred the malfunction and something have changed this area.
Given area is not changed during flash ROM.

arc said:
I hope that this will help you.
I met several times like you situation on Wizard -but nobody did not describe after what action this has occurred.
It is Enough that 1 byte changed in the field of CID and she will be bad.
Possible during unlock or as a result other action (for instance action what other program ) has occurred the malfunction and something have changed this area.
Given area is not changed during flash ROM.
Click to expand...
Click to collapse
thanks very much

not solution to fix this problem!!!!!!!!!!!!!!!

Okay, I can report that paying for this software and running it on my MDA fixed the data crashes problem. I tried everything I could find on the web from using the lokiwiz02b and going back to the original rom... everything in every order I could think of. I flashed back to the original ROM which I downloaded from HTC America's site w/o the SIM in the phone, ran this software after shelling out 40 bucks, once it came back up I shut down, put my SIM in, booted and sure enough it worked.
Here is how I got in this position. I had a warranty replacement phone from a bad screen that kept getting out of calibration. I put my SIM and MINISD in and powered it on. I flashed to the 2.17 custom rom. It rebooted and I got the data crashes error.
Of course this is no guarantee. I see above where someone posted that it didnt fix their problem.
I just flashed up to the 2.21 custom rom and everything works fine.
I noticed after I started all this BS that there are two bad pixels on the replacement phone! SOB!

it worked for me too. but why does this happen in the first place? I only got this error from one of the two MDA's that I have flashed, the other one worked just fine.....

My screen died as well, got a replacement in. Blam drashed as well.
Ran all the loki stuff, and it IS the IMEI that causes it. Used this unlocker program, and it does work. I am on 2.17 now and about to load 2.21.

This is my last resort...
I tried every possible solution to solve this same issue and I am going to shell out the cash, but my problem is that I can't get my IMEI from my phone (#06#) like the imei-check website said to without my SIM in there. But with the SIM in there I can't type #06#. So how did everyone get their IMEI? Should I just use the number on the box, and just pray that it is the same as my phone?
Thanks

earljg said:
This is my last resort...
I tried every possible solution to solve this same issue and I am going to shell out the cash, but my problem is that I can't get my IMEI from my phone (#06#) like the imei-check website said to without my SIM in there. But with the SIM in there I can't type #06#. So how did everyone get their IMEI? Should I just use the number on the box, and just pray that it is the same as my phone?
Thanks
Click to expand...
Click to collapse
your imei is also in the back of the pda under the batery.

Cool, thanks!! Website didn't mention that

earljg said:
Cool, thanks!! Website didn't mention that
Click to expand...
Click to collapse
u can also get your imei by going to start/settings/system/device information and tap the indetity tab

Had a pain with this myself....had to cough up the money and unlock my phone that way but everything works fine now.

Operator Code Problem

Hey guys, when I use GetDeviceData, the DeviceData.txt file I get contains the following where my operator code should be:
AT%CID?
(OK, it's not coming out right as text, so I posted up an image)
This is not a HUGE issue, as I can still upgrade my phone just fine, but it is worrying me.
Any ideas, comments, answers?

Ignore device data now, it's useless. You could however check this invaluable list of Model ID so you can get your operator code

@TheLastOne
Been a long time.
I have seen a few posts about trashed OPID codes and have not been able to work out were they come from or why they come about.
With the MA_noid...exe the Country code problem sort of went and I have yet to find a reason why we need a OPID in the first place (bar to stop us loading roms from other carriers).
As A German MDAIII user I have been flashing my GER device with WWE roms too many times to count and they all have worked on my swiss carrier.

Operator commands

When "calling" special numbers such as *444*# or #121# (to get a message with my remaining credit) or similar codes for operator commands, I do not get the expected message back but luckily the call does get processed (by the operator).
All I see is a balloon saying "Waiting..." with an OK button, but the answer from the operator never shows (unless it is an unknown code/command!).
I tried with the following ROMs (some WM6, some WM5) but only the HTC ROM (from europe.hct.com) works OK with these operator commands:
- AX3L_OS_v2.0.8.1 (WM6)
- LVSW_Trinity_WM6_v2.0.1.1 (WM6)
- LVSW_Trinity_WM6_v2.0.0.1 (WM6)
- mUn_2.01.TE_WWE_GPS (WM6)
- LVSW_WWE_1.25.0.8_GPS_AKU3.5.2 (WM5)
- RUU_Trinity_HTC_NLD_1.23.404.2_103_6275_1.38.00.11_108.exe (WM5)
Does anyone have a clue?

Probaby these cooked roms disabled or deleted the USSD service.
http://en.wikipedia.org/wiki/USSD

Unstructured Supplementary Service Data
ww2250 said:
Probaby these cooked roms disabled or deleted the USSD service.
http://en.wikipedia.org/wiki/USSD
Click to expand...
Click to collapse
Thank you, now at least I have a name for it

It seems to be an issue of the RADIO ROM, for instance 1.38.00.11 works OK with Simyo and Proximus whereas 1.46.00.11 works OK with Simyo but not with Proximus?!

[Q] Network messages coming through in Chinese and invid MMI codes

I've recently left my i9100 for an i9305 and decided to start by flashing the equivalent to my favourite ROM from my S2, namely SlimSaber (SlimKat unoffical build with Saber Mod) from here (build 8.0).
Anyway, regrettably i never tested out the phone much with the stock software because i wanted to go strait back to the KitKat experience I'm used to. I did however unlock the phone using USSD code *#19732864# as outlined in method 3 here. I believe I followed it exactly and it worked without a hitch
With it unlocked i put in my GiffGaff SIM and the first thing I noticed was that after every text, instead of getting the regular message saying "woohoo that text was free" or relevant credit update, i just get a similar box with a load of Chinese text.
Then I realised that the proximity sensor doesn't work. I don't mean to go specifically into that problem in this thread but while researching a fix I came across some USSD codes that might help. Now I can get a few to work: *#06# to show my IMEI , *#31# (Checks outgoing caller ID settings) and *#*#4636#*#* (User statistics and Phone Info), but all others I've tried just give me "Running USSD Code" and then "Connection problem or invalid MMI Code". This includes the one I unlocked my phone with in the first place and all the ones that are supposed to help my problem. A couple of the codes (*#526# and *#528#, both for WLAN Engineering Mode) yielding more Chinese text in place of the second message. I've tried putting a coma or semi-colon after the codes to no avail.
I presume that the network messages run on the same system as USSD/MMI and that the problems are connected. Not sure if the proximity sensor issue is connected.
The fact that a code worked before, but then stopped working seems to imply that it was something to do with flashing the ROM. Can anyone confirm that custom ROMs can mess with your USSD codes? Or could the unlock process have changed something? I've tried different kernels but the problem persists. Does anyone know at what firmware level native USSD codes are defined?
Many thanks for any input.

Chinese Gibberish
In case anyone's interested i took a screen shot of the Chinese text and put it through an optical character recognition web site. This is what came out after "Processing USSD code" for *#528# :
口秀一鼬一儡公囿一 找偎偎鬟醋蝌找阡醋份一
Which Google takes as:
Mouth of a puppet show, a male ferret caught a cuddle cuddle find DW vinegar vinegar a tadpole to find a footpath
Not very meaningful but at least quite amusing.
Then where I'd normally get "woohoo that text was free", instead it reads:
囿架架栀架蘖 王含栀揪王含 王含攀砀王含 目月T秋窃沙 昀
煸攀攀 嚣架甄蹴 想锹重毛锹瀵振攀 惋渺 彗沙王含惋蔓毛翼毛
Or:
Caught rack rack rack tiller Wang Zhi Zhi pulling containing containing Wang Wang Wang Dang containing climb mesh containing sand Yun month T autumn burglary
Well despite the problems with online translation it seems like this really is pure nonsense, which at least suggests to me that this is probably some kind of data that was never meant to be interpreted as Chinese text rather than the product of an incorrect language setting somewhere. Might be wrong.
Cheers

Wrong forum, ask a moderator to move it to i9305 q&a.

Chinese sorted
Right, Chinese gibberish was sorted by flashing updated modem from here as detailed here. However I am still suffering from invalid MMIs.
I should point out that I've tried all the methods outlined here. For anyone wondering how to get a comma or semi-colon on the dialer, add two-sec pause or wait respectively from options in the bottom right corner.