Related
As a regular contributor to various motor car forums I am always amazed at how idiots destroy perfectly serviceable cars in an attempt to 'improve' them. Anyway - today, I am one of those idiots.
I recently purchased a QTEK 2020 which I got a bit cheap on account of it not having 'iMate' written on it. Before I get really into it and put software and stuff on it, I'd like to upgrade my ROM from 1.66 to 1.72, which I have found on this site. Do I have to go through all of the xda2nbftool stuff (which I more or less understand)? Presumably yes, to change the Operator (only?). I'm quite happy for the machine to think that it is an iMate, but presumably this does not work!
I am happy with my machine. It hasn't crashed yet. But it annoys me that it might not be quite as good as yours...
(I so feel like one of those people who wants to remove his cylinder head and replace it with pineapple's to make the engine run sweeter)
i dont really understand what you are asking
are you asking
1 about changing operator and so sim locking ?
2 are you asking if you need the pretty manual xda2nbftool way to upgrade xda2's ?
3 are you asking if it will work upgrading to 1.72 ?
1 you can sim unlock your device without changing rom
a rom never require you to use a special operator but the preset settings will be the operators who put out the rom
2 yes currently it's the only way with time people are likely to make it a bit more gui like the xdatools for xda1
3 it should work but some people are reporting issues with it or maybe that was the beta of 1.72
read about the exp of others in the posts about 1.72
Sorry - it's a simple question.
If I had an iMate I could just use the RUXXX upgrade without any fuss to upgrade to 1.72
However, I have a QTEK 2020. I guess therefore I have to use xda2nbftool to modify the operator name to QTEK - otherwise it will not work (despite the 2 devices being identical). I do not want to unlock a SIM or anything else (it is unlocked by default).
Just looking for confirmation of the above paragraph!
I read about the experience of others using the 'official' 1.72 and it seems okay (better battery life etc.)
Cheers
there are 2 errors i think which stop people from just flashing their xda2 flavor with any rom update in the form of an exe file
1 is country code error if the rom is released in one country it often have a block which will stop people from upgrading their another country xda2 with it, not sure why they do that
2 maybe a form of device block so you dont upgrade your qtek with the imate
i'm sure if you had an imate and the country code dident differ you would be able to upgrade without using xda2nbftool
with time a GUI tool like xdatools for xda1 will come and you'll be able to get around all these blocks without having to type
and such
If you want to upgrade your Qtek to Imate's 1.72 ROM, yes, you need to do all that stuff.
It's actually quite simple, the description on http://wiki.xda-developers.com/wiki/HimalayaRomFlashing is full, accurate, and is actually suited to Qtek owners without changing a single instruction.
I flashed my device (though on the first go it ended up in a dead-ish screen and I had to re-flash) and it works swimmingly.
However, you might get somewhat nervous encountering such dead-ish screens; and for good reason, flashing is dangerous after all.
Perhaps it's best to wait for a Qtek upgrade, they seem to be holding back a bit, so perhaps they're waiting to integrate WM2003 Second Edition, which should be a much larger upgrade. Also, you'll still be covered by warrantee.
If you're having specific problems with your 1.6x ROM, it could conceivably be a good idea to upgrade to the iMate ROM (using the instructions on the wiki), but if you're not having any problems, or problems that also occur in 1.72, or which are a result of 3rd party software you're using; don't bother.
You are right that QTEK seem to be a little slow in releasing anything. In fact I can't find any detailed 'official' support on QTEK outside the pages of this forum. Their website appears to be in swedish and is of very little use!
The QTEKCorporation website doesn't even list the 2020! Strange, as I understand that HTC own QTEK.
Most vendors (Expansys for example) list the 2020 as 'discontinued' (which is how I managed to negotiate a big discount!)
I tried to gatecrash club-iMate but they didn't like my IMEI number, and when I asked why not they said that they don't support my device.
I don't really care (assuming that my machine never has a problem...) and is it seems to do everything I want it to, I'll wait before updating the ROM. Maybe something will come from QTEK eventually - although I am not sure from where!!
Cheers
well qtek were the first ones out with 1.66 it came on my device before most people had gotten 1.60
beljames said:
As a regular contributor to various motor car forums I am always amazed at how idiots destroy perfectly serviceable cars in an attempt to 'improve' them. Anyway - today, I am one of those idiots.
Click to expand...
Click to collapse
Who am I to contradict you? ;-)
Seriously: don't do the upgrade yet. Why?
- 1.72 has well-known problems. First, ClearType has become much worse - text just doesn't look as good as with older versions. Second, quite a few people report hangs that needed a hard reset (and cause a loss of all data). See, for example, the pages 45 - 50 of the PocketZenPhone thread in this forum. With my ROM version (1.60) I never had to hard-reset a single time. And I tried quite a few programs, some less buggy, some more buggy.
- also, although there are detailed instructions, things can always go wrong. And if that happens, you may need a bit of experience to sort them out. So wait a few more week, enjoy your device, read forums, and gain experience.
Cheers
Daniel
I have 1.72 for some time now and:
- it *never* crashed (I have to do soft reset from time to time like in any other release though, but no hang or anything)
- clear type is fixed. There's a post about a .cab to install which fixes the problem. ClearType is now great on 1.72
- my battery life improved over previous versions and I have a unit that can stand up to three days connected to my BT headset (a bluetrek G2) with me talking 2 to 3 hours a day and doing PDA stuff
so I would recommend you move on
Hi beljames, really I can understand you! I've almost destroyed a lot of good working car engines trying to "improve" them... :lol:
So: if you want to do this with your brand new QTEK 2020 go there
http://forum.xda-developers.com/viewtopic.php?t=9060
and read carefully.
All worked fine for me. I upgraded from 1.66 ITA to 1.70 EN and my QTEK works perfectly!
About the cleartype problem you can find a fix in this forum: it works too.
I've also added a N2Ox system and a small turbocharger... it's a little bit heavier, yes, but it runs like a rocket! :lol: :lol: :lol:
Good balanced opinions!!
I think I'll wait a while to see if it annoys me. One single hang and I'll upgrade. Screw it up in Ghana and you don't get a lot of 1 to 1 technical support!!
By the way - I find it far easier to read the screen with Cleartype switched off (and mine is 1.66). Cleartype makes me squint!
An Loxodont - assuming that you are Italian, you will be amused to hear that the one car I used to lunch very frequently was an Alfa 33. Used to blow the inlet manifold clean off almost weekly.
- 1.72 has well-known problems. First, ClearType has become much worse - text just doesn't look as good as with older versions. Second, quite a few people report hangs that needed a hard reset (and cause a loss of all data).
Click to expand...
Click to collapse
in defence of 1.72 then i have had both these issues with 1.66
Go for it....
Hi all,
just to let you know I also upgraded my Qtek 2020 from 1.66 to i-mate 1.72 following the "manual steps" to overryde the country code error and it works fine. The steps are simplier than it seems and i did it in 5 minutes. The upgrade itself is quite boring....it took almost one hour to complete the upgrade on all stacks.
One thing i can tell you: after the upgrade the device gets faster and it seems it has a "new" battery.
The cleartype prob is solved and forgotten with the right patch.
The only problem i still get is the stupid i-mate logo at startup and i can't seem to get rid of it. I want my old qtek logo back....
If i can give advise on this: Just go for it.....
Portuguese do it better....and we will win Euro2004 !
The only problem i still get is the stupid i-mate logo at startup and i can't seem to get rid of it. I want my old qtek logo back....
Click to expand...
Click to collapse
maybe this guide can help you get your old pic or a new and more fancy one as bootImage
http://forum.xda-developers.com/viewtopic.php?t=3759
I was very very happy when I saw 2003SE last week and I tried every version of it, incl. chinese one, but now I give up becouse it's not stable "NOT STABLE AT ALL" right now my PPC is so death as a peace of rock and when it starts after 100 times of softreset then it's freezes after 10 seconds...
So I'm going to flash it with off. v1.7 + ROM 1.18 and I'll wait one more month and see whats happening then....
Thanks you guys for your hard work
There seems to be alot of different experiences depending on the version of bootloader you have. I have version 1.06 and SE works like a charm, except for ONE anoying bug.
It simply wont ring when someone calls me.
Other than that, im very satisfied.
Skenliv_offline said:
There seems to be alot of different experiences depending on the version of bootloader you have. I have version 1.06 and SE works like a charm, except for ONE anoying bug.
It simply wont ring when someone calls me.
Other than that, im very satisfied.
Click to expand...
Click to collapse
anoying bug,It simply wont ring when someone calls me
It happent to me also, because I edit the register
so no sound, Think I take out the default ring tone
uninstall wisbar or pocketplus, soft-reset and check it out.
uninstall wisbar or pocketplus, soft-reset and check it out.
shaytaan said:
I was very very happy when I saw 2003SE last week and I tried every version of it, incl. chinese one, but now I give up becouse it's not stable "NOT STABLE AT ALL" right now my PPC is so death as a peace of rock and when it starts after 100 times of softreset then it's freezes after 10 seconds...
Click to expand...
Click to collapse
Well my fren, that's called life. We should be able to feel the joy and accept the sad part when something turns hairwire. No high and low will definitely make you an extremely dull person.
Cheer up! Specify your problems clearly and i think all the SE supporters will definitely help you in anyway they possibly could.
Look at the bright side, a not stable PPC makes me occupied and keep on thinking to overcome the challenges ahead. Opps...sorry guys i think i'm abit overly here like doing a motivation course.....
Nevertheless, i just wanted to save a lost soul of SE to revive back his excitement before an official launch of WM2003SE.....
eman said:
uninstall wisbar or pocketplus, soft-reset and check it out.
Click to expand...
Click to collapse
Ah!! now i see, its because i chosed to start wisbar advance automaticly.
When i removed that option, it WORKED!! THANX!!!!
Wisbar advance freezes the phone application on 2k3SE shame because it is a good program.
My extended ROM consists of GSFinder (freeware), MIDI561.sa, todayweather (freeware old version), Extended ROM unlocker by xda-developers, Cproghook, BT executable upgrade and CameraB10_Hima25_WWE.
Oh yeah and a licensed verion of TomTom3.
I threw everything else out as I dont use it.
My XDA2 now benchmarks at 1452 according sbp benchmark which according to their comparisons on the website is 2nd or 3rd fastest. 1 full charge see's 24-30 hrs use without a recharge on standby including the folowing settings: bluetooth of, average of 4-5 hrs spend email, telephone, sat nav and games with back light to minimum and switch of backlight after 2 min and unit of after 3 min .
My conclucion is that 2k3SE is stable however a lot of the software used by us is not wholely compatible yet as it is a new platform and until the vendors realise their software bugs it will make 2k3SE appear to be unstable!
just my £0.02
I can assure you that the 2.20.07.CHS, aka the chinese version i s stable just like 1.72 was in its time
yes maybe there are some problem relating to the software (wisbar, I had the same problem as you guys), but it is not the wm2003se fault, but the fault of the software houses realesing apps with no SE support.
So try to look at the good times we are having doing all that upgrade, downgrade stuff....
The T9 Intellipad, does NOT save words if you chose another language.
This is seriously not good on my device, since im from sweden.
Has anyone got any sollution to this problem?!...
you will need to get the latest new version for WIn2003 SE
cause most of the software/program design for win2003 only not SE yet
wait for new version for SE
then you dun have the problems
I m running my A.K.A chinese SE no error/problems with all my software/program
Now I figured out how to get rid of the wisbar adv problem.
I found it on the lakeridge soft forum.
There is a guy that uninstalled the caller_id app, and it solves the problem.
I personaly don't use the caller_id thing (picture of the caller) and I don't have any problems in removing it.
Maybe it helped
HERMIMG_O2_1.25.207.1_SHIP.nbh
http://www.o2online.de/o2/kunden/technikundeinst/exclusive/xda/xdatrion/index.html?nidx=1
did not test it yet - will do when i´m back home and have a few mins spare time
finally! thanks for the headsdup!
@dutty
give it a try please and let me (us) know if you notice any fixes or improvements
Wiki updated, and ROM moved to safe heaven in FTP:
http://wiki.xda-developers.com/index.php?pagename=Hermes_Upgrades
ftp://xda:[email protected]/Hermes/Shipped_Complete_Updates/O2_1.25.207.1_GER.exe
Thanks guys
okay. it's flashed, i havent noticed anything different tho!
screenalignment issues are still present and there is only one new cab : suspend_resume_null.cab not sure what it does as i really see no difference.
i wonder why they never release any changelogs..
dutty said:
okay. it's flashed, i havent noticed anything different tho!
screenalignment issues are still present and there is only one new cab : suspend_resume_null.cab not sure what it does as i really see no difference.
i wonder why they never release any changelogs..
Click to expand...
Click to collapse
The screen alignment issue is a hardware fault, about this problem this is the email that I have received by htc europe:
Good Afternoon,
There are now procedures in place for fixing the Screen alignment issue with the TyTN devices. This is a hardware issue that we have identified and we are offering a replacement to owners of affected devices with two conditions.
1: The device must be returned with all accompanying accessories.
Everything that was in the box when you bought the device must be in the box when you return it.
2: The device must be a Genuine HTC Badged device. This means that the device cannot be a Vodafone v1605, an O2 XDA Trion, a T-Mobile Vario II or any other device based on the TyTN, but that is not actually a TyTN. For these devices, you must contact the Network/Reseller for further advice on this issue.
If you meet these two provisions, you may contact your nearest repair centre to arrange the swap. Please place everything back into the original box and arrange to have the device picked up. It will then be tested to confirm that it has the problem, and then it will be swapped for a replacement unit.
If you are unable to return everything, you will be eligible for a repair under the warranty. For this also, you can contact your nearest repair centre to arrange this.
I must note that this email is a standard answer. Other people have received the same email.
Hi,
does it exist O2 English ROM yet ?
Hello,
can anyone tell me the version and date from the file SAPSettings.exe in the windows-directory from the new O2-Update?
Thanks
Mad_M said:
Hi,
does it exist O2 English ROM yet ?
Click to expand...
Click to collapse
No at moment o2 uk doesnt sell the trion.
You can find it only in o2 german
It is possible create a MUI for this Rom?
OK i am again disappointed from this O2 sh*t realease.
The GPRS/UMTS Radio disconnects itself and i have to hard resed my device again. Now i know why i moved away from the O2 ROM. I flashed my device back to the updated O2 ROM in hope the issue was only a temporary problem and will be fixed in the new update but its not.
I am considering to replace my device. With this problem i cant live for much longer time.
Overall i am a lot more unsatisfied with the TRION. The Wizard from Cingular didnt had those major issues and performed very well. It doesnt matter if the TRION has a 400 Mhz CPU inside compared to the Wizard it works more worse and I am going back to use my Wizard until O2 has a stable release of the TRION ROM. :evil:
EXT_ROM keypad .cab
Hey,
does anybody knows which .cab from O2 Ext_ROM is for keypad (phone dialer) layout and colors ?
Tnx
http://rapidshare.com/files/43432242/RUU_Hermes_O2_DE_3.54.207.2_6275_1.47.00.00_108_Ship.rar
here is officail wm 6 o2 germany
The story:
I just got a HD2 today, and to be honest I'm pissed.. I've been ripped off big time, the phone has a cracked screen(it said the description, but I expected something smaller), it has been taken apart and put back poorly(windows key isn't backlit anymore). Also, the LCD has 3 big white circles and the touchscreen sometimes doesn't work. Not to mention that the USB connection doesn't work(USB device not recognized), No usb modes work. Sorry about that but I had to write it, I have to let the angryness come out some way.. I demanded a refund, and he better give it to me.
OK, now about my question:
The phone has a french rom(original, not updated) and it's AZERTY keyboard. Since USB doesn't work and I can't flash updated rom without HSPL, I'm stuck with this ROM and without Android(2.04 radio (( ).
How do I change the keyboard to qwerty, in keyboard settings, there's no option to change the layout, just auto-correct and other things, but no layout option.
And I can transfer files to it, I have an X1 and I can use that to transfer files to the SD card...
Since the phone is knackered and you're demanding a refund anyway (and quite right too!!), why does it matter?
Pay a bit more and get a good condition one. If you have issues with a working phone then we can help you.
johncmolyneux said:
Since the phone is knackered and you're demanding a refund anyway (and quite right too!!), why does it matter?
Pay a bit more and get a good condition one. If you have issues with a working phone then we can help you.
Click to expand...
Click to collapse
I don't think it matters if it's good or not, that's more of a software thing. Is there any cab or something to change the keyboard?
But you're returning it as damaged, so what do you care?
Seriously, from your description I wouldn't even bother turning that thing on!
A quick search (using the search) found this...
http://forum.xda-developers.com/archive/index.php/t-268225.html
It's the opposite to what you're asking for, but it should point you in the right direction.
Hi, I have a couple of HD2's ready for use within the business I work for.
These HD2's were purchased as replacements for older HD2's that had been used and were getting tempramental and old.
I have recieved the new HD2's and heres my problem:
The touch screen seems to decide when, and IF it works. The first time I EVER got it out of the box, unwrapped it etc the touch didn't work.
After a couple of restarts the touch works, then after a bit it will then decide not to work.
This happens constantly, it will work, then wont work, then work, then wont work.
When it works it is fine, just like the HD2 should be, it just seems to be like a moody teenager who decides when and if it want's to work.
Any one know what could cause this? Why it is happening and why it works and then doesn't?
Thanks !
the touch has always been a weak point of this phone, and your issue doesn't sound all that uncommon.
if they still have older version, rom then you should certainly update that.
if there's any warranty you should definitely go that route immediately,, because you almost certainly aren't gonna fix it.
Hi mate
Yes I have updated the ROM's which went from 1.4 (ish) to the current ROM listed on the HTC website. That seemed to fix it, but then I realised the phone was in a good mood, and 10 minutes later it started its hissy fit again.
And about warranty I don't know as I didn't buy them, we may have to attempt to send them back but thats gonna take weeks, as it took weeks for them to arrive. And we need them out and about tbh.
Do you have any idea what the cause is?
Hardware/Software?
Thanks !
sorry no clue why, and I'd say it's most likely hardware,,, a failing digitizer by the sound.
Sounds like the common digitizer issue, just had same with my personal TMOUS HD2.
Our local supplier said he had units 100% new but old that had failed in the box, reckons digi ribbon bonding to digi is bad on both solder & socket types.
From 20+ HD2 handsets we have running in our company I would conclude similar myself.
My personal handset has had extremely light & sympathetic use & hardly minimal use of end key but it still failed.
Hardware durability of digi/micro USB port & mainboard thermal control/BGA solder quality is very poor to be polite ...