Problem unlocking my k-jam (HTC wizard) - 8125, K-JAM, P4300, MDA Vario Software Upgrading

hi there,
on running k-jam_Lokiwiz02b ... i did all the instructions , after unlocking (step 1) , & rebooting
a message appeared : SIM Lock
"Data crashes..contact your service center"
i tried to install the old ROM ,, nothing happened & the same error
tried to unlock my device several times as mentioned ,, also the same error reappears every time ????
when i remove the SIM card , the ppc works normally (but not the phone of course) , tried another SIM & also no use
plz HELP

Do you have a G4 or G3 device? What ROM version do you have? We'll take it from there.

i've a G3 device 3.
installed this ROM lastly :
KJAM_ROM_1010903_103_10110_cdl_me_ship
on boating the following appears :
IPL 1.01
SPL 1.01
GSM 1.1.10.0
OS 1.1.9.3

up.....................

While your KJAM rom is 1.01, why don't you try using the Button ROM just to see if it makes a difference.
No clue about the SIM Lock error though. You can use lockiwiz .3 to do the SIM Unlock to see if that fixes that issue, then go back to trying the CID Unlock with .2b.

thnx for concern mfrazzz .. u mean i should try the oldest ROM available ? i tried so & no use ,,,,
i'll try .3 Lockiwz version & c ....?

i tried .3 Lockiwz version .... problem still exists

dr.moh said:
i tried .3 Lockiwz version .... problem still exists
Click to expand...
Click to collapse
Bummer... Ok, I just did a google search on your message and found this form Howard Forums:
The data crash message means that the encryption block controlling the simlock is damaged.
That should not be possible, but it apparently IS possible, because you're not the first person who's had it happen.
What I would attempt to do to recover is:
1. Take OUT the SIM card.
2. Bring up the phone in boot loader mode.
3. Reflash an official RUU that matches the phone (T-Mobile US) OR restore an SD image that matches the phone (T-Mobile US)
See if that works. If it DOES, then use the Lokiwiz again BEFORE you go screwing around with anything new. If it does NOT, then attempt the RUU to the Qtek or Imate ROM, again, with card out, and see if THAT one can be booted.
Click to expand...
Click to collapse
There was no indication in the thread if this worked or not, but its something else to try.
Hope that works for you (or lets you make progress).
FYI: Here's a link to the thread Google put me in where I found this. Just do a search on "data crash" in your browser on this thread and you can read from there down (for aways). I didn't dig real far though.
http://www.howardforums.com/archive/topic/872974-1.html

A similar problem with solution !
i searched the forum & found that post
earljg said:
Just in case everyone is wondering what I did before I decided to pay for the IMEI and wanted to try before buying a program...
Having the 2.17 ROM installed when I started to have this problem, I first decided to try the method suggested here:
http://forum.xda-developers.com/viewtopic.php?t=50768
That still came up with the "Data crashes..." error with both T-Mo and Cingular SIM cards inserted. The same as the method in the above link (Lokiwiz3a, etc...).
So then I decided to try an alternative method followed by in this thread:
http://forum.xda-developers.com/viewtopic.php?t=47848
Which involves downgrading, then unlocking, then upgrading. Also with no luck on removing the "Data crashes..." error. I tried inserting my SIM after the downgrade and running Lokiwiz02b and still same error message.
Then I finally broke down and paid for the IMEI unlock program as posted in this thread (suggested by meschle, and in many other threads):
http://forum.xda-developers.com/viewtopic.php?t=43319
If the two previous methods mentioned before the pay method do not work and you decide to pay for the IMEI unlock mentioned: PLEASE follow jt_armstrong's advice (mentioned in above post) for obtaining your phones IMEI # when ordering the program!!
Since I did it as a last resort, it was already too late for me to obtain the IMEI from my phone as the pay website suggests (dial *#06# on your phone). This is due to when I insert my SIM the "Data crashes..." message comes up and there is no way I could obtain my IMEI without looking at the label behind my battery.
All is well now after running the $38 program. I finally realized (with the help of the previous posters, and other threads in this great forum!!) I have exhausted all other options.
Unless you can wait for someone to come up with a definitive solution to this rare (from what I have read) problem, I highly recommend using IMEI unlocking program. I have been trying to find a solution for about 5 days in the forums and this was my last resort...
Click to expand...
Click to collapse
will the IMEI unlock program work with my Imate kjam ?

up......00

Related

Error 114, help me please,I'm helpless.

Hi All
I have a SPV M2000.One day the phone stopped working. Everything was all right, it did ask for pin but then didn't even looked for network,was immediately saying NO SERVICE. I tried few sim cards - the same.
So then I wanted to reinstall the ROM, I downloaded the official from Orange UK , tried to install it,and it shows ERROR 114, Radio Rom Upgrade Error.
And the phone now is in bootloader mode and I can't do anything!
I downloaded different ROM from xda-developers ,at the beggining with a country error, but i managed to fix it and now with this ROM it's the same thing. ERROR 114. I tried everything, hard,soft reset, Pc reset etc. Nothing works!PPC still in bootloader mode!
Please tell me if you know what else can I try!
Guys,come on,really noone knows???
Have you read WIKI? Follow the first method to flash your ROM. Have you remembered to plug in your power supply to your cradle when you flash your device?
Heres another thread on NO SERVICE Plz help... No Service after radio upgrade. Happened to me. Read it and see the advise by MDAIIIUser and TheLastOne. If all else fails, bring it to the shop.
I had a very similar problem....
First I tried to update a whole package that means rom, extended rom and radio
The radio update is always the first one and there always upgrade error 114 occured.
So I updated every part seperately and it works except the radio. So I tried alot but it just didn't work..even downgrading was impossible. MDAIIIuser and happy goat tried to help me as well as they could but nothing had an effect.
So I read in another forum that asus mainboards have some problemes with these radio updates....I thought they were joking...but I tried the radio pdate at another pc and it worked!
I know it sounds a bit stupid but I was desperate and at last it worked!
You can read it here :
http://forum.xda-developers.com/viewtopic.php?p=89657#89657
TRied that method.Doesn't work
Any other ideas?
One more thing.Is it normal that in bootloader mode when I plug the power cable in the charging LED is not working?it was working before.
The battery is charged ,but shouldn't it show that the power is connected anyway?
EDIT: this is a reply to the first answer.
So you think I should try on another PC?I will today!Hopefully it will work.
So I managed to install new rom on a different computer! I think that there was a problem with active sync.I used the one that was installed from my old XDAII.Could that be the reason?Now i installed the one provided with a M2000.
But it doesn't work anyway
Still NO SERVICE message.
ANy other ideas different than taking it to Orange?
Hi rottie,
No Service could mean anything. Could your SIM card be faulty? Device SIM locked? Or hardware faulty? You cannot just use any ROMs you find at ftp. Try to flash your device with full shipped rom at http://wiki.xda-developers.com/index.php?pagename=BA_1.40.00_Upgrade. Use the first method and upgrade using MaUpgradeUt_noID.exe to bypass the Country code error. Remember that you'd need to run MaUpgradeUt_noID.exe twice.
Read wiki carefully, it has alot of precious information. Cheers ^^
Before you update any version you should be sure that your radio is
compatible with your device. Usually all radio upgrades should be
independent off the language of the device but as I understood (could be
wrong) there are differences because of the servicenetwork frequency.
So you must be sure that the chosen radio is compatible and that your
device is not simlocked.
So perhabs you should chose an upgrade of your provider.
But perhabs itis better not to risk your guarantee of your provider by
using updates or components of other providers! Because there could be
the possibility that your device is damaged and you should bring it back!
Good luck!
Guys, you get me wrong.I'm not trying anything what I'll find.
1)One of the ROMs that I tried and the one that I left now is a ROM downloaded from orange.co.uk for SPV M2000. So there can't be any incompatibility, don't you think?
2)I have 2 sim cards,both from Orange,I was using both of them before in my M2000 which is sold only through Orange so there can't be any simlock problem,don't you think?
3)I used only that orange ROM, original and the I-Mate one.None of them were working good,always NO SERVICE.
I bought the phone second hand,with box,all accessories etc. But I don't have a receipt :? And of course have lost the guy's number.That's why I want to try everything before going to the service.
I think this phone is network blocked, probably been reported damaged or stolen, once the insurance or replacement is issued a block is put on the imei of the phone that was subject to claim.

T-mobile MDA says "Data crashes" with SIM card ins

First I would like to thank everyone for posting their wealth of knowledge on these forums, I have learned a lot.
My problem is just as posted in the subject. I upgraded my phone to the 2.17 T-Mo custom ROM just as the instructions said. Ran cidunlock and everything before flashing. My phone works great as a PDA, but as soon as I put in a SIM card I get the "Data Crashes" error. I even tried several SIM cards from varying providers (T-Mobile, Cingular... etc).
I downloaded the 2.17 ROM from a link on these forums. Now Ihave downloaded the T-Mo original ship OS (from same link as the custom ROM), but it is not an exe and I have no idea how to use the files downloaded. I am not even sure that restoring the original OS will fix this problem. I was going to pay for the program from that imei-check.co.uk site, but unfortunately I can't get my imei (#06#) without a SIM in my phone.
I only found one post about this problem. One soultion offered was to copy thecidunlocked.bin to the phone, but the poster didn't say where to copy the file to on the phone.
I noticed a new program on the hompage here that will unlock any Universal. Will this work to fix my T-Mo MDA?
Will performing a SIM unlock solve this issue?
I did't want to try to SIM unlock or do anything else to my phone without further guidance from some helpful person. Trying not to screw my phone anymore than it is.
I am desperate for suggestions/solutions from anyone that has solved this issue.
Also, with so many different names for the Wizard, what name is the T-Mobile MDA commonly refered to? Is it the MDA Vario? This just makes me more confused about which programs apply to my phone.
Use lockiwiz 0.3a worked with my device after upgrading to qtek aku2.
Follow instructions here http://forum.xda-developers.com/viewtopic.php?t=50768
Re: T-mobile MDA says "Data crashes" with SIM card
earljg said:
First I would like to thank everyone for posting their wealth of knowledge on these forums, I have learned a lot.
My problem is just as posted in the subject. I upgraded my phone to the 2.17 T-Mo custom ROM just as the instructions said. Ran cidunlock and everything before flashing. My phone works great as a PDA, but as soon as I put in a SIM card I get the "Data Crashes" error. I even tried several SIM cards from varying providers (T-Mobile, Cingular... etc).
I downloaded the 2.17 ROM from a link on these forums. Now Ihave downloaded the T-Mo original ship OS (from same link as the custom ROM), but it is not an exe and I have no idea how to use the files downloaded. I am not even sure that restoring the original OS will fix this problem. I was going to pay for the program from that imei-check.co.uk site, but unfortunately I can't get my imei (#06#) without a SIM in my phone.
I only found one post about this problem. One soultion offered was to copy thecidunlocked.bin to the phone, but the poster didn't say where to copy the file to on the phone.
I noticed a new program on the hompage here that will unlock any Universal. Will this work to fix my T-Mo MDA?
Will performing a SIM unlock solve this issue?
I did't want to try to SIM unlock or do anything else to my phone without further guidance from some helpful person. Trying not to screw my phone anymore than it is.
I am desperate for suggestions/solutions from anyone that has solved this issue.
Also, with so many different names for the Wizard, what name is the T-Mobile MDA commonly refered to? Is it the MDA Vario? This just makes me more confused about which programs apply to my phone.
Click to expand...
Click to collapse
i have the same problem, i still could not get an answer from here. I have followed numerous tutorials done by others who have had a similar crash. restoring to original tmo rom did not help me. ran unlokwix03a, which gave me the unlock code.
So I did manage to get a unlock code but when I put in a diff sim from another carrier am not even getting the prompt to enter it. so anyone with a solution we realy could use your help.
kizo
I used Lokiwiz3a to unlock my custom T-Mo 2.17 ROM MDA phone. I am still getting the "Data Crashes..." error even when I insert a cingular SIM into my T-Mo device. I can't seem to get the input screen to enter the SIM code that I got from Lokiwiz. I even ran Lokiwiz twice, with my T-Mo SIM card inserted ("Data crashes" screen was on) and without it inserted. Then tried again with a cingular SIM and the same error message appears.
Can someone advise me in this issue again?
Thanks
I had the same issue and spent countless hours trying to correct the problem. I tried every Rom and unlocking software I could find. Nothing worked. I'm no expert but from what I have learned there seems to be an issue with the IMEI in the US T-Mobile MDA. A few weeks ago I started having problems with the phone so I went to HTC's US website and downloaded the original shipping ROM, flashed it to my phone, not a single problem. In fact the phone actually worked better. Since it worked so well I figured I'd try one of the cooked Roms. I could always go back to the original right? WRONG. I got the data cash screen and an expensive paper weight no matter what I Tried. I called T-mobile and Htc every day for a week. They were no help. Big surprise. The only solution offered by the two was to send the phone to HTC for repair. They said it would cost $38 US just to look at the phone plus any additional fees for repair. 7 to 10 days to figure out the problem and 7 to 10 days for repair. A few days ago I read that some people were using imei-check.co.uk to solve the problem. I decided to go for it. $38 and 5 minutes later, I know have a working phone. Screw T-mobile and HTC.To get the IMEI you need to take your sim card out, go to the COM manager and turn the phone off. Place the Sim card back in and and the data crash screen wont show up unless you turn the phone back on through the COM manager. Hope this helps.
It looks like occassionally it is fixed by going back to the original rom, but not always - then unlocking and reflashing.
Most success with this http://www.imei-check.co.uk/ cost 30-40 bucks but most cases seems to work.
Read this thread http://forum.xda-developers.com/viewtopic.php?t=43319
IMEI-Check.co.uk definitely works. I got the same data crash message after I upgraded to 2.17 and their solution worked immediately. BTW the IMEI is printed on the phone right underneath the battery. Whatever you do don't assume the IMEI printed on the box is the one on your phone.
Thanks for everyone's help!! I finally broke down and went to the IMEI site and paid for the program to fix it. My phone is working beautifully now!
Just in case everyone is wondering what I did before I decided to pay for the IMEI and wanted to try before buying a program...
Having the 2.17 ROM installed when I started to have this problem, I first decided to try the method suggested here:
http://forum.xda-developers.com/viewtopic.php?t=50768
That still came up with the "Data crashes..." error with both T-Mo and Cingular SIM cards inserted. The same as the method in the above link (Lokiwiz3a, etc...).
So then I decided to try an alternative method followed by in this thread:
http://forum.xda-developers.com/viewtopic.php?t=47848
Which involves downgrading, then unlocking, then upgrading. Also with no luck on removing the "Data crashes..." error. I tried inserting my SIM after the downgrade and running Lokiwiz02b and still same error message.
Then I finally broke down and paid for the IMEI unlock program as posted in this thread (suggested by meschle, and in many other threads):
http://forum.xda-developers.com/viewtopic.php?t=43319
If the two previous methods mentioned before the pay method do not work and you decide to pay for the IMEI unlock mentioned: PLEASE follow jt_armstrong's advice (mentioned in above post) for obtaining your phones IMEI # when ordering the program!!
Since I did it as a last resort, it was already too late for me to obtain the IMEI from my phone as the pay website suggests (dial *#06# on your phone). This is due to when I insert my SIM the "Data crashes..." message comes up and there is no way I could obtain my IMEI without looking at the label behind my battery.
All is well now after running the $38 program. I finally realized (with the help of the previous posters, and other threads in this great forum!!) I have exhausted all other options.
Unless you can wait for someone to come up with a definitive solution to this rare (from what I have read) problem, I highly recommend using IMEI unlocking program. I have been trying to find a solution for about 5 days in the forums and this was my last resort...
i got the same problem and fixed it with the paysites....BUT i know i could have fixed it without them...had i saved the locked_bkp.bin file that unlock software generated the first time...
If any of you has the file, they can figure out how to write it to the phone by reading out the .bat file that came with the lokiwiz...
If you tried to unlock it twice....forget about that because the second time the software actually overwrites the backed up file with the crashed one it reads from the phone...
Not to sound to dumb or nieve, i ran lokiwiz, it gave me my unlock code, but when I put a cingular sim in my tmobile device it never asked me for the code. The phone works with both my T-Mobile sim and a Cingular sim. Can I assume than that my Wizard is sim unlocked even though I never had to put in a code?
Not to sound to dumb or nieve, i ran lokiwiz, it gave me my unlock code, but when I put a cingular sim in my tmobile device it never asked me for the code. The phone works with both my T-Mobile sim and a Cingular sim. Can I assume than that my Wizard is sim unlocked even though I never had to put in a code?
Papa_I said:
Not to sound to dumb or nieve, i ran lokiwiz, it gave me my unlock code, but when I put a cingular sim in my tmobile device it never asked me for the code. The phone works with both my T-Mobile sim and a Cingular sim. Can I assume than that my Wizard is sim unlocked even though I never had to put in a code?
Click to expand...
Click to collapse
Sounds like it is unlocked to me, but I am no expert. Just figuring if you can use two different SIM cards (not form the same company) in a phone, then it is unlocked. That seems logical, but who knows, maybe T-Mobile isn't being logical and Cingular SIMs normally work with T-Mobile phones. I never actually tested that idea...
To those that find themselves in this situation i just want to tell you that i didn't have to pay to fix my phone. I simply used itsme's tools to flash a new CID block back to the phone (lucky for me that i had a backup of it before facing this problem)
The reason for this is checksum errors in CID block (last 8 bytes of the 64k section) which may occur from bad flashing process or, as in my case, for messing with SPL messages with mtty program.
So all you have to do (if you have a G3 DOC model) is make a backup of CID block before upgrading rom (machinagod's programs create that file automatically when CID unlocking - even if it generates write errors). If the accident happens then downgrade SPL/OS to version 1.06 or bellow and flash the backup CID
cheers
i have a t-mobile dash with the same problem, what can i do if i dont have the cid backup??
tramuyo said:
i have a t-mobile dash with the same problem, what can i do if i dont have the cid backup??
Click to expand...
Click to collapse
Get this application http://forum.xda-developers.com/showthread.php?t=295038 (version 0.3), read the CID block and check if the CID IMEI is same as the label one
downgrade SPL/OS to version 1.06 or bellow and flash the backup CID
Click to expand...
Click to collapse
how can i flash the backup cid ? is there any program because i only got 3 .bin-files and dont know what to do with them.
I have another question. What is the difference between the normal IMEI number and the CID-IMEI cause my device has 2 different ones.
peran281 said:
how can i flash the backup cid ? is there any program because i only got 3 .bin-files and dont know what to do with them.
I have another question. What is the difference between the normal IMEI number and the CID-IMEI cause my device has 2 different ones.
Click to expand...
Click to collapse
Where did you get those 3 bin files?
The IMEI is stored at two locations:
the gsm_data block and that's where the device reads it from when you browse the "Device Information" ("Identity" tab)
and the CID block as well where i believe that cprog.exe (the GSM app) reads it from
Now the "Data crashes" error might come from bad CID block checksum or from the existence of two different IMEI numbers of these two locations (i tested it )
Use my program again to read the gsm_data IMEI (use the "Read IMEI" button) and see what IMEI you get
Where did you get those 3 bin files?
Click to expand...
Click to collapse
i got these files from the lokiwiz tool cause i cid unlocked my device with it.
but since this step i can only flash t-mobile roms on my device but i have an o2 branded one. why?
i have in both locations the same imei i think.
What is the difference between the normal IMEI number and the CID-IMEI cause my device has 2 different ones.
Click to expand...
Click to collapse
did u mean this ?
but how can i get a imei which works ?

T-mobile NL: problems with dialing after unlocking & upg

Hello everybody
Yesterday I tried to use "lokiwiz - HTC Wizard Unlocker v0.2b" for my new T-mobile MDA Vario because otherwise I was not able to upgrade the ROM from 1.6.2.2 to the latest one. But.. in the end I got a problem. To be honest this problem was appearing periodically before unlocking/upgrading but now it presents permanently. I simply can not dial any phone number. The systems responds as: "SIM card is not installed or invalid" (something like that from translation from Dutch into English, originally: "SIM-kaart ontbreekt of ongeldig").
I already tried to use this SIM in my previous phone (SE T630) and it still works perfectly. I can dial numbers, I can SMS, whatever. But in my new T-mobile MDA Vario this SIM card just does not admit dialing the phone numbers.
Does anybody have any thoughts, what it might be?
Thank you very much in advance!!!
P.S. Honestly, in case of warranty during unlocking process I kept my SIM card out off the MDA.
Just for info...
When I bought MDA the version of ROM was 1.6.2.2 NLD
After upgrading I got ROM 2.21.2.5 NLD and ExtROM 2.21.2.108
As I see now it connected to T-mobile network but still can't dial any number, reporting of the possible problems with SIM card. In the same time this SIM card is working with no any problems in my T630.
This is a very strange problem indeed. When you turn your device on or soft reset, does the device ask for a PIN code for the phone? If it asks for a PIN code and it accepts that code and starts searching for a signal, that means that the device can read the SIM card. It is very strange that when you have a signal, the device cannot make call. Either it should not be able to compare your PIN code to the one on your SIM and give an error message, or if it accepts your PIN code, you should be able to make calls. Perhaps there is a hardware problem with your SIM slot that makes the device unable to read the info on your card? Since it works in your other phone, the SIM does not seem to be the problem. You can try flashing another ROM on it to test if the device works with that ROM. If that does not work as well, flash back to an original T-Mobile NL ROM and call T-Mobile for your warranty.
When it is loaded it shows up the Telefoon screen with the following message: "Ongeldige of ontbrekende SIM-kaart. U kunt nog wel alarmnummers bellen, als uw seviceprovider dit ondersteunt." If I type numbers it show stars, like I would enter the password. Why stars? I already tried to input my unlocking code but it didn't help, as looks like it expects something else that this. I may just press Annuleren and continue working with other available functions of MDA but still may not use the phone.
Could you please share the info how to downgrade back to 1.6 ROM?
Thank you very much for your response!
Ok, this indicates that your device cannot read your SIM card. The screen you get on start-up is the screen where you normally enter your PIN code, if the device can read your SIM Card. That is why you see only stars when you enter a number there. Seems to me that your device cannot read your SIM Card and therefore cannot compare the PIN you enter to the one on your SIM card. You should not be able to get a signal from T-Mobile, since your phone cannot read the SIM and cannot register with the network. This can be caused by three problems: either your SIM card slot is broken, or your ROM is faulty (try flashing it to another ROm first, for instance a Qtek ROM from the ftp server, there are many ROMs available there) or the SIM card is defective ( seems not to be the case here, since it still works in your other phone).
I recommend that you first try another ROM on your phone, e.g. a Qtek ROM. If the problem goes away then, just keep the Qtek ROM or try flashing the T-Mobile ROM again. If that does not help, flash the latest T-Mobile ROM (from their website) to your device and claim your warranty for a broken sim slot.
As far as I know it is not possible to downgrade to the 1.6 ROM, it is a non-AKU ROM and cannot override an AKU ROM. Perhaps someone can correct me, since I am not a 100% sure of this. You do not need the 1.6 ROM at all, if the Qtek ROM does not work, just flash the latest T-Mobile ROM to your device and claim warranty. Since you then have an official T-Mobile ROM on your device, warranty should not be a problem.
Would be that a problem to flash latest T-mobile upgrade back from Qtek? I need to know it just in case I would not be able to do that. Cause otherwise, sorry, but im ****ed up in front of warranty office..
It should not be a problem to flash the T-Mobile ROM over a Qtek ROM. You can first try a hard-reset to see if that solves your problem. You can also call T-Mobile Klantenservice and tell them your problem. Tell them you want to use a Qtek ROm to figure out the problem and ask them permission to do so. They are known to give permission for such actions if that can save them from repairing your device. Be sure they make a note in your file stating that they give you permission, that makes your case stronger if there is a problem with your warranty later on. Good luck!
Do you think it's illegal installing even T-mobile NL ROM updates by myself, i.e. not asking T-mobile to do so?
Like I said the previous version of my ROM was 1.6.2.2. Then I actually tried to flash the latest UK version (2.21.2.5). The network signal was actually appearing from time-to-time but then it just died. Then I tried to install the latest NL version (2.21.2.5NLD) to check whether the signal would appear. But it didn't help.
Installing official T-Mobile updates is not illegal. T-Mobile NL made the upgrade available on their site. These updates are meant to be carried out by the users themselves, therefore the file and instructions are placed on their site. For other brands ( Nokia, SE) these updates cannot be done by the users themselves, but Windows Mobile updates are meant to be done by you, thereby saving T-Mobile the costs of performing the upgrades for you. So if an official T-Mobile ROM is on your device, they can never deny you your warranty. You can try to replace the radio Rom only (there is a thread on this) to see if that helps, but I recommend flashing an official T-Mobile NL ROM on your device and claim your warranty. Since you have tried different ROMs, the problem obviously resides in the hardware. If a hard-reset does not help, use the lokiwiz application to sim and cid lock your device again and T-Mobile will not be able to see that you had unlocked it. Just mention that you tried a hard reset and that you tried upgrading to the latest official T-Mobile ROM and they will have to honour your warranty.
Re: T-mobile NL: problems with dialing after unlocking &
First of all to my knowledge T-Mobile MDA Vario in NL is SIMlocked and CID locked . If you want to know the difference I advise you to search in the xda-forum or google it.
Here are a few comments from my experience of upgrading and unlocking my MDA Vario.
( BTW I have T-Mobile MDA Vario initially with 1.6 ROM and SIM& CID lock -first upgraded to 2.21.2.5 then unlocked with lokiwizard3a !! )
cagliostro said:
Hello everybody
Yesterday I tried to use "lokiwiz - HTC Wizard Unlocker v0.2b" for my new T-mobile MDA Vario because otherwise I was not able to upgrade the ROM from 1.6.2.2 to the latest one. .
Click to expand...
Click to collapse
I disagree with this, upgrading should not require you to unlock your device unless you upgrade to a None-T-Mobile ROM. If this was your main target ( only the Tmobile upgrade ) you shoudn;t have messed with the unlock stuff
cagliostro said:
But.. in the end I got a problem. To be honest this problem was appearing periodically before unlocking/upgrading but now it presents permanently. I simply can not dial any phone number. The systems responds as: "SIM card is not installed or invalid" (something like that from translation from Dutch into English, originally: "SIM-kaart ontbreekt of ongeldig").
Click to expand...
Click to collapse
I am a bit puzzled you state that the device was not behaving well before you started tweaking. Why did you not go to the Tmobile shop? OK you like the challenge ? Anyway it does look like a Hardware issue to start with.
cagliostro said:
I already tried to use this SIM in my previous phone (SE T630) and it still works perfectly. I can dial numbers, I can SMS, whatever. But in my new T-mobile MDA Vario this SIM card just does not admit dialing the phone numbers.
Does anybody have any thoughts, what it might be?
Thank you very much in advance!!!
P.S. Honestly, in case of warranty during unlocking process I kept my SIM card out off the MDA.
Click to expand...
Click to collapse
OK what have you tried else?
The suggestion of trying a QTEK ROM shold be blocked by your CID lock. I you remove the CID lock ( which is possible but not legal ) your warranty is at risk. Tmobile may claim you messed up your device ...
Therefor What I did is only take the SIM lock out. Lokiwizard 2(a/b) did not work for my upgraded MDA so I looked around a bit and found that there is a newer version 3a. That one worked for me on the Tmobile 2.21.2.5 ROM. I did not use or try the QTEK rom since the Tmobile rom allows my warranty to be safe and is newer ( and stable afaik) then the QTEK rom .
I also have found there are updater that do not check your version number of NBF file because you officially can not downgrade the 2.21.2.5 so there is a way back should you need to. Though I personally did not verify this . I mailed with a person here at XDA forum who did it with success.
I would propose to play dummy when approaching Tmobile and not ask to go to QTEK rom and tryin to be the smartass.
Try to downgrade and go for warranty - thats what I would do..

8125 ROM Upgrade Problems

I recently attempted to update the ROM in my Cingular 8125. The process stopped at 95% and I received an "Internal Error". Now, when I turn on the phone, it gets as far as the color RUU screen, and nothing else.
How can I find out if I can repair this situation myself or if I need to take it back to Cingular.
Hopefully you'll give Cingular a little more info regarding this than you gave us.
My psychic advisor is STILL on vacation so I can be of very little help to you, sorry!
What ROM were you running before and what ROM were you trying to flash it with? Did you CID unlock before you flashed?
Sorry - When I posted the 1st message, I was in a hurry...
I am not sure what ROM version was on the device before I attempted to update (I know, I should have paid attention, but I was not). The phone was new from Cingular and I had not done anything else to it besides load a couple of apps (Skype & Agile).
I attempted to run the file RUU_Wizard_225111_22511102_022511_CWS_WWE_Ship.exe that I downloaded from the HTC site. The update go to 95% and I received the error "ERROR [326]: INVALID COMMAND" - This NBF file cannot be used for your PDA Phone. Please check your NBF file." (I have attached a screenshot of the error to this post).
I am not sure what to do at this point.
Thanks,
Chris
Some folks at the Cingular forum are having the same issue with no solution offered.
I'd suggest putting the device into bootloader mode (Holding Record and Camera buttons while soft reseting) and then reflashing. Make sure not to launch any programs while flashing. I also don't touch the device at all as I've noticed the USB connection might slightly disconnect.
Good luck and let us know what happens.
I just tried reloading from the bootloader screen - no luck. Exact same error at 95%. Would it work to try to reload an original earlier ROM? If so, how would I go about trying that?
Chris
I had this same problem.....I went to the cingular site after having the problem. Before installing I stopped all applications then soft reset.
THen after it boots up install the file from cingular. It worked from their site. Not sure what changed but I am not having any problems now with the new ROM.
I had this same problem.....I went to the cingular site after having the problem. Before installing I stopped all applications then soft reset.
THen after it boots up install the file from cingular. It worked from their site. Not sure what changed but I am not having any problems now with the new ROM.
I have re-downloaded the ROM file from the Cingular site (actually it just redirects to the HTC site). Same problem. I cannot get to the point to even shut down any programs because the phone OS does not even load at this point. When I do a soft reset, I get the following (sorry for the blurry image - as you can see my good phone with the good camera is dead...)
I had a similar problem. I posted the fix on another thread and ppl said i was wrong, this wasnt it...but heres what worked for me.
Are you using a usb port on the front of the computer? if so, try pluggin into the ports on the back of your computer. I tried flashing the official rom from cingular a few times using front port and it stopped at the exact same % each time. got the same thing as you, colored bars.
Someone had mentioned to me that front usb ports don't work as well as back ones. give it a try. good luck
from the picture, it looks you have the G4 chip(u can see 2.25 0001)
Thanks to everyone for their input. From the suggestions above, I have tried various USB ports on my laptop and I always get to the same point. I have also called HTC tech support and they are pretty sure I have bricked my phone. I talked to Cingular and they have agreed to replace it. I have also researched the G4 chip issues (looked at the post: http://forum.xda-developers.com/viewtopic.php?t=56408).
Now I have the following question - When I get my new phone (which I will assume will have the G4 chip as well), the Cingular rep told me that it will already have the latest 2.25.0001 ROM on it. What are my options at that point to SIM unlock my phone. Will I be able to? From the post I referenced above, it sounds like I may not be able to with the G4 chip.
Chris
xtreme23 said:
from the picture, it looks you have the G4 chip(u can see 2.25 0001)
Click to expand...
Click to collapse
I second this observation! :shock:
This makes a major difference on wether or not you can even upgrade.
Search for G4 issues.
The .0001 in the IPS/SPL number will tell you which one you have.
The way I understand it is:
2.25 - G3
2.25.0001 - G4
I think this is the proper way to identify it.
slapper said:
Now I have the following question - When I get my new phone (which I will assume will have the G4 chip as well), the Cingular rep told me that it will already have the latest 2.25.0001 ROM on it. What are my options at that point to SIM unlock my phone. Will I be able to? From the post I referenced above, it sounds like I may not be able to with the G4 chip.
Chris
Click to expand...
Click to collapse
Chris, LokiwizMSL ( http://forum.xda-developers.com/viewtopic.php?t=50768 ) can SIM Unlock your device. Be sure to read the instructions.
Well - Now I have a new problem. So far, Cingular is refusing to replace my phone - saying that the ROM upgrade voided the warantee. I am still fighting that, but just in case I loose, is there any way to get my phone fixed once it has been "bricked"?
slapper said:
Well - Now I have a new problem. So far, Cingular is refusing to replace my phone - saying that the ROM upgrade voided the warantee. I am still fighting that, but just in case I loose, is there any way to get my phone fixed once it has been "bricked"?
Click to expand...
Click to collapse
If you installed an unofficial ROM then they are correct. You should never admit that you used a ROM that was not provided by HTC.
There are warnings all over this site about VOIDing your warranty.
Since you used the Official Update they are wrong.
Same problem with official Cingular 8125 ROM
I tried to flash the official Cingular ROM from the HTC site here:
http://www.htcamerica.net/docs/RUU_Wizard_225111_22511102_022511_CWS_WWE_Ship.exe
I got the same error at 95%:
"Error [326]: INVALID COMMAND This NBF file cannot be used for your PDA Phone. Please check your NBF file."
When I reset the phone I get the RGB bootloader screen and nothing else.
My phone is a G4 and was running ROM version 2.25.11.1 WWE before. The reason I tried to apply this ROM is because there was apparently no Extended ROM. None of the customization cabs executed on a hard reset. Also, in Device Information, there was no "ExtROM" listed.
This is the second phone that this has happened on. I thought the first time was just a fluke thing and I had a bad phone. But now I think there is an issue with this ROM.
Anyone have any idea what is going on here with this ROM? Does the fact that there was no Extended ROM have anything to do with this ROM not flashing properly?
Is there anything else to try or do I need to try to return the phone (AGAIN)?
how to fix the problem
read this thread carefully. The upgrade problem seems to be occuring on G4 chipped Wizards with the most current IPL/SPL.
http://forum.xda-developers.com/viewtopic.php?t=56088
take the official update. run it, when it finishes extracting look for the extracted NBF file in your
C:\Documents and Settings\yourusernamehere\Local Settings\Temp\the newest directory just made
find the NK.NBF file
extract it using the tutorial in the post above you will be flashing with the official cingular components sans IPL/SPL.
flash it and your are back up and running
I would have posted this earlier but i had to make sure it worked and was repeatable.
I think the problem with the new update is the new IPL/SPL version checking. It seems that if the patcher sees the same version already running it will give you that error at 95%. I've seen it on 3 phones already and I have been able to fix them by doing what i've told you above. You are already in bootloader mode and your phone is ready to accept a new rom anyways. My solution may not be the best for your phone and take no responsibilites but you are already desperate and need a fix. Good Luck!
Thanks for the reply, evilito. Since I hadn't gotten any replies for a few days, I decided to go ahead and try to exchange the phone at the Cingular store. They were baffled that this was the second phone I had returned for the exact same problem, but gave me a new phone anyway. I wish now that I had waited so that I could try evilito's solution to see if it works. As it is now, I am too scared to try any flashing on this new phone after my results with the first two. I would really hate to have to try to return a third phone
Can anyone else verify that there is a problem with the latest Cingular ROM when flashing a G4? Or did I really have two bad phones?
slapper said:
Now I have the following question - When I get my new phone (which I will assume will have the G4 chip as well), the Cingular rep told me that it will already have the latest 2.25.0001 ROM on it. What are my options at that point to SIM unlock my phone. Will I be able to? From the post I referenced above, it sounds like I may not be able to with the G4 chip.
Chris
Click to expand...
Click to collapse
Thats good to know, I thought that when we unlocked it and updated the ROM we lost Warentee Support. Where can you get the official Cingular 2.25 ROM. I am still on 2.17.

blocked on the boot screen

Hello,
I've tried to update my phone using the shelltool method and my phone crashed during the update.
Now it can't boot. it's freezed on the splash screen.
I've tried to put the CUSTOM__RUU_Wizard_1050412_WWE_101_11210_WWE rom and it does nothing.
I have a G3 device, the IPL/SPL is now 1.01
Thanks in advance for your help
Flash back to official carrier ROM.
I have already tried using the bootloader method. it tells me that the device is not compatible
Try it doing the storage card method.
I also tried and it tells me I don't have the right
Before the first update, I have made a backup of the OS ROM but the file format is NBA. Is there a solution to reuse my original ROM?
In Addition to the SD method, the bootloader is password protected
Try reflashing the ROM you were flashing in the first post using the RUU in bootloader mode. You shouldn't need to use the shelltool to flash that one. Then when you get that flashed on there do your CID unlock. After that you should be able to flash any ROM you want.
I've tried tu put Button's ROM using the RUU in bootloader mode and its still blocked
Try flashing the wizard love rom then. I'm not sure where it is at the moment, but you can find it on here somewhere.
I also tried this ROM
I have made some research.
At the beginning (when my first upgrade crashed) someone on a chat told me to do a doctest.
No the problem is that the memory is damaged.
When I try a hard reset, I have the message "format is failed"
Any idea?
You've got me on this one, I don't think I've run across anyone else ever having this problem. By the way, did you remove any miniSD card that you had in the phone before flashing? Having one in there while flashing tends to cause people problems.
Also, I just realized that you said that you used sheeltool to flash the first time when you flashed the button rom and that it changed your IPL/SPL to 1.01. Flashing using shelltool won't change your IPL/SPL, it skips those files if they are added to a rom since they are the files that will destroy a G4 device. So, if it did change them then that's where you did something wrong. Why don't you start over and explain exactly what you did on the first flash with the button rom and see if we can't figure it out from there.
OK I'll explain from the beginning
Before beginning the flash, I have made a backup of the ROMs (OS, Radio and Ext) with aWizard.
I wanted to put a french WM6 ROM. In the the tuto, it was told to use shelltool to do this. For an unknown reason, the phone crashed. So I had to reboot the phone because it was freezed and after this point it did'nt boot.
I went on a chat to get help and someone told me to start the bootloader and with mtty enter the command doctest (I think he's a joker becose today I saw this command is very dangerous).
When I saw this command doesn't work I discovered this forum and tried 2 of the 3 methods to unbrick a phone in the wiki.
I can't use the SD one because the boot loader is password protected.
I also discovered today that the IMEI number doesn't correspond to the label on the phone.
Here is my story .
http://forum.xda-developers.com/showthread.php?t=276963&page=7&highlight=wizard+bootloader+password
This post seems to have helped many. Read from beginning to end, then try to follow it. Good Luck.
raskell said:
http://forum.xda-developers.com/showthread.php?t=276963&page=7&highlight=wizard+bootloader+password
This post seems to have helped many. Read from beginning to end, then try to follow it. Good Luck.
Click to expand...
Click to collapse
I'can't use imei check because my imei is invalid
Why do you think your IMEI is invalid? If the only reason is that it shows a different one on the box than it shows in aWizard or whatever program you're using, don't worry about it because that seems to happen quite a bit. Usually it's because it got put in the wrong box. Anyway, you're in luck, I have a program that I believe I downloaded off of XDA which is a version of the IMEI-checks unlocker with the master unlocker code for all wizards.
Well, I was going to upload that tool for you but after trying 6 times to upload it and it failing each time I figured that maybe I should wait a little bit and try again later.
I think the IMEI is different because the one given from imei-checks is different from the one on the label back the battery.
Also, when I tried to order an UNL file with the IMEI given by the unlocker, they told me its a wrong number
Lets try this again.
Still failing to upload. I'm not sure why, but I'll try yet again later.
I sent you in PM the address of my ftp server

Categories

Resources