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
The problem appeared today morning, while listening music using tcmp. the sound stopped suddenly, and standard animated cursor appeared over tcmp screen. i closed tcmp, and the rest of the system seemed fine, i was able to mute the phone and entered my work place. After a while i noticed the screen is off and i can not turn it on using pwr button, although green led kept blinking so the phone was operating. after a soft reset it would not go over splash screen showing IPL, SPL (which are: IPL: 1.06, SPL 1.06, GSM: 01.12.10, OS 1.6.2.4).
I've tried multiple times and still the same, only difference is that sometimes I can see the cursor and sometimes not. I can get to rgb screen and "press send to restore" as well, but that's it. I can't remember whether previously pressing a key illuminated a screen and keys, but now it doesn't. I used to have problems with screen not going black on idle since few days, but that's it. What could have happened? And if the only solution is hard reset, please tell me, could I somehow backup my contacts now? I don't have activesync here so I have to wait till I finish my work to find out..
please help anyone...
rom version : 1.6.2.4 WWE,
date : 11/15/05
radio : 01.12.10
protocol : 4.0.13.23
extrom : 1.6.2.105
That's spooky. My MDA has the same versions of IPL, SPL, GSM and OS, and this morning started misbehaving.
What's this rgb screen you can get to with the "press send to restore" option?
How do I do a hard reset (I have a backup on SD) without being able to get to the Start>Settings>System>Clear storage control panel option?
Rgb screen is a bootloader which i enter by holding cam+voicedial+commmanager butons while softreseting wizard. the other screen i mentioned i enter holding cam and voice buttons, and then pres reset. that screen says 'pres send to restore factory defaults any other key to quit' and it does hard reset if you press green button here...
my problem seems to be over for now, i managed to turn the phone on while i plugged it into a wall charger (believe me, the battery was not a problem - i don't know for how long it's ok now, but at least i made contacts backup now so that i'm ok with a hard reste if i have to...
You both have old roms and could do with upgrading them to aku2 roms. (your device will be more stable) i.e. the first number of the rom will be 2. Please dont ask me to go through how to flash a rom because there are hundreds of posts on the same topic and read the wiki - shortcut top left of the screen. You need to identify whether your device is g3 or g4 but i suspect you both have g3 chips.
Now read & read esp the wizard upgrading forum and wiki and then when you feel confident - flash your device.
mu chipset is g3 based on my ipl/spl info... i wouldn't dare to ask anyone to explain the process of flashing, i'm not that crazy. only thing i'd dare, would be to advice me what rom should i use... or a way to determine this, since i know it can't be just any rom...
banannq said:
mu chipset is g3 based on my ipl/spl info... i wouldn't dare to ask anyone to explain the process of flashing, i'm not that crazy. only thing i'd dare, would be to advice me what rom should i use... or a way to determine this, since i know it can't be just any rom...
Click to expand...
Click to collapse
Looking at your rom numbers i gather you have a t-mobile vario - is it uk or usa rom or polish - i see you live in poland.
there latest uk rom is here ftp://[email protected]/Wi...Prodigy_2210206_109_21911_TMO_UK_WWE_Ship.exe
us rom ftp://[email protected]/Wizard/Roms/Tmobile/RUU_Prodigy_2170702_217_20710_TMO_US.exe
user name xda password xda
Its prob best you sim unlock and cid unlock before you flash in case you change to a non-tmobile rom inc one of the cooked roms.
see here http://forum.xda-developers.com/showthread.php?t=249474
and read dr puttingham's tutorial http://forum.xda-developers.com/showthread.php?t=285435
and now i have given you more than enough hints
p.s. by the way remember to write down your gprs settings and mms settings to use with your new rom.
thats right, its tmobile vario, uk one. it is sim unlocked, i'm not sure about cid but it should not be a problem. thanks for the hints, it really seems more then enough;] i'll probably have to use theese, as soon i have a spare evening...
you don't have to explain me the importance of gprs settings - forcing my wiz to work in uk's o2, then in polish plusgsm, then loosing settings and doing it again finally got me into a habbit of backing every settings up ;]
and last but not least, guys, yesterday i did my first HR ;] ...
i posted this in another thread but no one replied so thought this one mite be more busy.
i am new to all this and i stupidly went running into things and tryed to ROM upgrade my t-mobile MDA Vario II (HERM300), not knowing i had to CID unlock first, it has broke! when i boot it up i can not get passed the t-mobile splash screen and it also flashes "no-gsm". i have read many suggestions on fixing this but i have had no luck. i can get into the boot screen however and get the red green and blue stripes.
i have IPL 1.01 and SPL 1.04.
it will allow me to connect to my PC with USB but active-sync does not recognize i have connected the phone.
please help someone. i just need a way i can get this thing working again. if i could just get the phone into a state of use again that would be good.
please help, at least let me know if Ive got a chance of repairing it
i believe if you can get it in to bootloader mode you can flash back to original rom and start over
i thought that to but when i tryed the t-mobile rom it said "connection error" and also said it should be connected through active sync. but then agen it mite of been the wrong t-mobile rom but im sure it was for the vario ii. do you have a link to the one i should try please?
i downloaded the official UK shiping rom from t-mobile site and upgrading now through bootloader. will report on what happens.....
nope, keep getting "device not responding" or "connection error". any other sugestions?
i looked on here http://wiki.xda-developers.com/index.php?pagename=Hermes_Unbrick and it says that i have to "Flash any type2 radio in NBF format. If that doesn’t work, flash the radio using HERMflasher" please could someone tell me how to do this, if this is the solution to my problem or if there is another way around this. thanks.
please help someone i realy need to fix my phone
Cool down....
what's ur radio version?
Also have u read this? http://wiki.xda-developers.com/index.php?pagename=Hermes_SimUnlock - TRY THIS FIRST, before attempting anything else...
ok, i have tryed that "sim and cid unlocker" and i beleve that you have to connect with active-sync because when i tryed it when i was in boot loader it said that it was not connected but it was. i will get my radio version now.
EDIT: my radio version is: 0107
EDIT2: also, here are some other numbers (which i dont know what they mean but mite be needed) which apear on boot-up t-mobile splash screen, in red letters/numers, just before "no-gsm" flashes on:
M 05
S 04
B 06
D 1.21
If you can get into the Bootloader (Rainbow Screen) you should be okay (Not a Brick)
Go download a Radio Rom from the wiki.
Enter Bootloader first, then connect to PC. Then flash the Radio Rom.
Edit, Also Read: http://forum.xda -developers.com /showthread.php?t=296722
berdinkerdickle said:
If you can get into the Bootloader (Rainbow Screen) you should be okay (Not a Brick)
Go download a Radio Rom from the wiki.
Enter Bootloader first, then connect to PC. Then flash the Radio Rom.
Edit, Also Read: http://forum.xda -developers.com /showthread.php?t=296722
Click to expand...
Click to collapse
ok, ill try that, does it need to be a perticular radio because im not super CID? for some reason the link will not work.
oooooo, it seems to be workin!!!!!!!!! im at...16%. ill report what happens after update finished
yes!!! it worked!! thank you very very much for your help!!!
Nice thing happened to my hermes200: before christmas I upgraded it to the shap's rom, following the instructions... Everything was great until 2 weeks ago: without doing anything special the phone was not working anymore and the rest of the device was working very slowly. I tried several times a hard-reset but nothing changed. After this I tried to flash the rom with the original htc wm6 but it's impossible: at 12% everything freezes and the wizard says that there's a connection error ..From that moment I tried other several rom from different sites, some are faster and some slower, but every single one has the same problem: the phone doesen't work (It also shows "no GSM" every boot). Other interesting thing is that if it goes in standby, it's impossible to turn it on again and I have to soft-reset it.
But the best and amazing thing I found yesterday is this: if I go on the "device Information" of my device, with ANY rom there's NO RADIO VERSION, NO PROTOCOL VERSION and NO IMEI!!...
I tried to look on the net if someone had the same problem but, up to now, i didn't find any.
Thanks for everything, mediomat.
I too have the same problem with the device information settings. The version tab is displays no version, the Call Duration tab displays incoming and outgoing as unknown, the Identity tab only displays the proper Platform while Model No and IMEI are blank, and Hardware tab displays garbled text. Though, on the Hardware tab, it shows the RAM and Flash size as xxxxxxx MB.
I haven't had any luck either finding a solution to this.
Solution:
1. Check your SPL and flash HardSPL if you don't have it
2. Flash your shipped ROM
3. Repeat step #1
4. Flash back some Hermes cooked ROM
5. Done. Check Device info, if you don't believe me
Best regards,
aDEO
If the radio rom has been corrupted this STILL may not work... Its a brick... Sorry...
Still, no harm in trying....
Hi everybody,
I recently bought a serial-to-miniusb cable on ebay and am expecting it to arrive in a couple of days. My intention is to reset the life timer/call duration on my polaris by using the xda manipulator. I would like to hear your opinion on this. Can I try it riskfree? Will it work?
Thanks!
buekly said:
Hi everybody,
I recently bought a serial-to-miniusb cable on ebay and am expecting it to arrive in a couple of days. My intention is to reset the life timer/call duration on my polaris by using the xda manipulator. I would like to hear your opinion on this. Can I try it riskfree? Will it work?
Thanks!
Click to expand...
Click to collapse
Use Mitty.exe instead to RESET CALL TIMERS.
Read the guide and software are on the forum here: http://forum.xda-developers.com/showthread.php?p=2027058#post2027058
XDA Manipulator is very unlikely to be able to reset the counters on a Polaris and trying it would be very risky.
Thank you carryo,
So it seems I will have to install olipro 1.10 . Could you please guide me through this step? I know how to turn the phone into bootloader mode. What next? Should I connect it to the PC via USB ?
Thanks again
and wouldn't it be dangerous to install this SPL olipro 1.10 on me device? I mean I am not a specialist and don't know, what's the difference between older and newer spl?
Hi buekly,
Careful that hardspl for htc hermes, tq
Well then, can anybody suggest another way to reset call timers? I have done a big search and found nothing useful...
just download that mtty.exe, flash HardSPL for Polaris and that's it
the rest is on the help page
Download ATcommander for your phone and try [email protected]=270F,270F should reset call timers to 0
buekly said:
and wouldn't it be dangerous to install this SPL olipro 1.10 on me device? I mean I am not a specialist and don't know, what's the difference between older and newer spl?
Click to expand...
Click to collapse
You should use the HardSPL for Polaris which instead of olipro 1.10 which was a version or an older phone. You can find the file and instructions on the Sticky thread in the Polaris Upgrading etc. section. HardSPL won't damage your phone and will make sure that you can easily recover from anything else you change.
Then use Mitty.exe to reset the counters.
OK, now this is getting more and more interesting. Let me tell you about my progress. I made a Hard SPL for my Polaris. Then, I ran Atcommand. I insterted the following:
ate1----> 0
ate0----> OK
[email protected]=270f,270f ---> Error
When I saw that error, I remained quite disappointed. However when I checked the call duration in settings/device information I saw it was 00:00:00. But also, I saw in Identity that the phone doesn't have an IMEI number. So, I inserted a SIM card, made a call and, when I checke again, I saw that all the information was back, i.e. call duration back to 40 hours, IMEI reappeared. Why is that happening? These commands seem to oinly apparently remove the call duration, but when you insert a sim card, everything is back.
I tried another option, through MTTY. I disabled USB connection in Sync, turned the phone into bootloader mode, connected, ran MTTY, selected USB. But when I enter rtask b, see what I get below in the image. And that's it! After this text appears, I can't type anything else. I have to restart the MTTY.
So please help with any suggestions, cause I'm already run out of them. Thanks
which spl are you using does your spl say security unlocked at the top? If not try this one http://forum.xda-developers.com/showthread.php?t=351964 .I just use ATcomander to reset my timers When you use rtask b it just puts the phone in diagnostic mode you can proberly connect via a com port (after installing drivers) but i dont think we can use many AT commands with the polaris spl.
meknb said:
which spl are you using does your spl say security unlocked at the top? If not try this one http://forum.xda-developers.com/showthread.php?t=351964 .I just use ATcomander to reset my timers When you use rtask b it just puts the phone in diagnostic mode you can proberly connect via a com port (after installing drivers) but i dont think we can use many AT commands with the polaris spl.
Click to expand...
Click to collapse
yes, I used namely this spl and this I told you what happened. Do you also have a polaris and it worked reseting timers on yours?
Yes i have a polaris and have just reset the timers with ATcommander using [email protected]=270f,270f,ATcommander should return with a 0,now all timers a 00:00:00.
The only thing i can think of is i dont think hard spl fully security unlocks under mtty try "rtask a" then "setinfo" and see if your SECU_FLAG=0.
Also what radio are you using?
no really, it isn't working:
1) when i type ate1, it gives 0, then atv1, it gives OK, then [email protected]=270f,270f it gives ERROR. I'm run out of options. I mean there's something wrong with the last command. Maybe I should change it or what? Maybe I should enter another value? I tried [email protected]=9999,9999 it also shows ERROR.
2) I tried "rtask a" in mtty, but it shows the same text as in "rtask b" (see previous attatchment).
My radio version is 1.59.42.15
OK, I tried checking secu flag
I typed "[email protected]?AA" it showed "@secu_flag 1 0" What does it mean?
@secu_flag 1 0 means your phone is not fully security unlocked i can't remember how i got mine to secu_flag 0 it was using [email protected]=2,0 or something like that.I'll have a look how, you dont need the ate or atv commands there just for displaying results.
@secu_flag 1 0 means your phone is not fully security unlocked i can't remember how i got mine to secu_flag 0 it was using [email protected]=2,0 or something like that.I'll have a look how,
Click to expand...
Click to collapse
Thanks, I'm waiting for your assistance!
you dont need the ate or atv commands there just for displaying results.
Click to expand...
Click to collapse
OK then, why are the timers then resetting temporary after I introduce these commands? By temporary I mean they are back again when I insert a sim card. And also, after I introduce these commands IMEI disappears in system/device information/identity. It says "IMEI not support", and when I dial *#06# I get "Failed". When sim card inserted or phone restarted - everything reappears.
Right i found [email protected]=7,1 relocks security setting,and [email protected]=7,0 unlocks them,if [email protected]=7,0 doesn't work with your radio use the polaris unlocker and flash OliNex patched radio go through the all three steps then try [email protected]=7,0 and then [email protected]=270f,270f,I tried reseting the timers when locked and got a error,so with some hopes that will work for you ,Then flash your radio back when finished.
meknb said:
Right i found [email protected]=7,1 relocks security setting,and [email protected]=7,0 unlocks them,if [email protected]=7,0 doesn't work with your radio use the polaris unlocker and flash OliNex patched radio go through the all three steps then try [email protected]=7,0 and then [email protected]=270f,270f,I tried reseting the timers when locked and got a error,so with some hopes that will work for you ,Then flash your radio back when finished.
Click to expand...
Click to collapse
do you mean I should use this one http://forum.xda-developers.com/showthread.php?t=375338 ?
I downloaded it, however by the end of the thread I can see a lot of complaints from users, claiming that the signal either disappeared or reduced by 80% after using it. Have you tried it?
Yer thats the one i used,as i said flash your original radio back after you have finished to 1.59.42.15 or whatever you where using because i think olinex radio is just patching the simlock i think ? but is not very good for everyday use.