Related
Any of you 8125 owners who installed the imate 2.16.9.101 release have any new feedback on how it's going? Are there still issues with the connection icons or wifi connectivity?
I'm eager to get push mail working and have not been able to get a straight answer from a dozen different folks at Cingular on when their release will come out...so I might give the imate release a shot.
What about going back to the shipping Cingular version after installing the imate update - is it easy/possible? Any problems with extended ROM?
thx
I never even used the phone with the original cingular firmware, I went directly to the Q-tek Test rom. From that rom to this rom, the radios seem a little better (getting better signal, edge seems slightly faster, wifi picks up network much faster) and for some reason the whole feel is "snappier" seems like the menus and such load faster. I haven't had any stability issues, and push is working perfect.
I dont' know about the much faster part, but mine is very stable since i removed battery pack pro. I have SPB's power plus as well as their weather software.
if there are any software you want tested just let me know. Well if I can atleast run it without having to buy it, (i.e. Demos, etc.)
Bluetooth, Wifi, Edge, and signal are all real good. (signal on par with 1.12 radio as well as faster to get a signal than it was)
Battery icon is NOT on the bottom and does NOT show more than 2 bars ( so you have full, somewhere in between, and low).
Battery life seems pretty good, but I can't compare it to any other version as I had the phone 36 hours before I upgraded it to this version.
Great thanks for the feedback yall. So once I do the upgrade, how hard will it be to go back to the shipped version if I ever need to? I have everything backed up using awizard, but I understand there could be problems trying to go to a previous version. I think downgrading via the bootloader mode requires executable rom images, but there isn't one available for the shipping version.
You can still downgrade to an old imate ROM and then use aWizard to restore your cingular ROM.
I have installed it on my Qtek 9100.
I hanged 5 times in 2 days.
What is more annoying is when it hangs and
someone tries to call me at the same time, the
other party hears my phone ringing, but my
Qtek is dead silent.
ethorn said:
I dont' know about the much faster part, but mine is very stable since i removed battery pack pro. I have SPB's power plus as well as their weather software.
if there are any software you want tested just let me know. Well if I can atleast run it without having to buy it, (i.e. Demos, etc.)
Bluetooth, Wifi, Edge, and signal are all real good. (signal on par with 1.12 radio as well as faster to get a signal than it was)
Battery icon is NOT on the bottom and does NOT show more than 2 bars ( so you have full, somewhere in between, and low).
Battery life seems pretty good, but I can't compare it to any other version as I had the phone 36 hours before I upgraded it to this version.
Click to expand...
Click to collapse
Is your wifi working OK? If so, did you install any of the cingular exrom customizations?
Just curious, because I installed the released imate rom and everything is working like a champ except wifi. I installed some of the original customizations from the cingular exrom and I wonder if one of those cabs did something to the wifi config...
What kind of porblems are you having with the wifi?
nickcerda said:
What kind of porblems are you having with the wifi?
Click to expand...
Click to collapse
It won't turn on.. =)
I thought perhaps it was one of the cingular customization cabs I installed from the original exrom, but now I'm not so sure. I looked at all the cabs and the only one that relates to wifi is the cab that sets the key to enable talking to 802.11g APs.
In comm manager, if I click the wifi icon, it appears to attempt to start wifi, but then goes back to an "x" over the wifi button. The wifi radio doesn't start and the left LED that blinks when wifi is on does not come on.
I wish there were some logs to look at on this thing to see why it's failing to start wifi..
Solved the wifi problem. It appears to be related to something in one of the original 8125 exrom cabs. I reinstalled the new imate rom, skipped the imate exrom install, and only installed a couple cabs from the 8125 exrom. The cabs I installed that did not affect wifi were the mms config, the gprs account config, and the edge icon.
All is now well. If I had the time and patience I'd tear apart the original 8125 cabs to see which one might cause wifi probs, but at this point it's not necessary.
I'll stick with it as-is now until cingular releases their own update...assuming that happens before the hermes is out.. =)
I have a Dopod 838 (identical to 8125, I suppose). The new ROM has worked awesome for me. Better in every way. Even the infamous Activesyn problem went away
I am getting ready to take the plunge...just in case...
does anyone have the original 8125 ROM?
I use SPB backup can restore a backup after I upgrade?
I installed this rom on my 9100, and it is much better than it was with any of the other roms including the original shipped rom!
The radio is much clearer and the wifi hooks up faster and runs better, and I have had absolutely NO lock ups at all.
Later
I am thinking of installing it on an 8125...
Without a backup 'known good' ROM to revert back to I am cautious
summiter said:
Solved the wifi problem. It appears to be related to something in one of the original 8125 exrom cabs. I reinstalled the new imate rom, skipped the imate exrom install, and only installed a couple cabs from the 8125 exrom. The cabs I installed that did not affect wifi were the mms config, the gprs account config, and the edge icon.
All is now well. If I had the time and patience I'd tear apart the original 8125 cabs to see which one might cause wifi probs, but at this point it's not necessary.
I'll stick with it as-is now until cingular releases their own update...assuming that happens before the hermes is out.. =)
Click to expand...
Click to collapse
I added the extROM files one by one to see which one caused the wifi issue and it was Signed-gprsstall_128.sa.cab...so far. It was only the third one in a series of 17. I'll see what happens when I add the rest. This cab file moves a radio.dll file around.
I've installed this ROM on 2 8125's. Much better and faster than Cingular's ROM. The only thing I did was to install the Cingulcustomize_No_Emails.cab, Microsoft Voice and TRE Pocket PC registry editor and remove all traces of the Voice Command. WiFi connects to my secured access point flawlessly (though I never use WiFi) and the AKU2 push email typically has my emails coming in in about 8-10 seconds from my Exchange 2003 server. Very infrequent lockups, much less than any other ROM I've installed.
Just my two cents worth ...
Steven
ROM version: 2.16.9.1 WWE
ROM date: 2/6/06
Radio version: 02.07.10
Protocol version: 413.1.03
ExtROM version: 2.16.9.101
Cingulcustomize_No_Emails.cab
What does that cab do?
nickcerda said:
Cingulcustomize_No_Emails.cab
What does that cab do?
Click to expand...
Click to collapse
the one thing I see is it sets up the GPRS settings for data connection ... you do not need it to make phone calls or use Wifi
Step by step to 2.16
I have a cingular 8125. I'm no stranger to flashing roms, I had a SX66 that was running WM5 and I reloladed it all the time. I'd like to see a step by step guide for unlocking the ext rom, flashing the radio and system roms for the 8125. Anyone know a post with that info in it?
Thanks!
Re: Step by step to 2.16
dmelton75 said:
I have a cingular 8125. I'm no stranger to flashing roms, I had a SX66 that was running WM5 and I reloladed it all the time. I'd like to see a step by step guide for unlocking the ext rom, flashing the radio and system roms for the 8125. Anyone know a post with that info in it?
Thanks!
Click to expand...
Click to collapse
Interesting you say you're no stranger to flashing ROMs but then ask for a step by step.
It's laid out quite well in several topics, but basically:
-Use awizard and enable rapi
-Use awizard and CID unlock
-Use awizard to back up Extrom, radio, splash, os
-Run the executable RUU installer for the imate
-On first boot, as soon as you get prompted to choose a carrier, do a soft reset to prevent the imate ext rom stuff from loading
-Install desired customization items from your backed up cingular ext rom. Any of them can be installed EXCPET the gprsstall cab - it will kill your wifi.
There is currently no way to unlock the ext rom in the lates imate upgrade, so you're stuck with what's in there, but you don't have to let it install.
Hey All-
Rather then adding to the large Helmi thread, I figured it would be best to start my own...
In short today I upgraded from TuMa v1.3 to Helmi's new ROM: Helmi_BA_WM2k5_AKU_2.3_32mb_v1.rar
Everything went fine during the upgrade, I set the Operator Code to T%CID? which was retrieved by using GetDeviceData.exe and the upgrade went smoothly... but now the phone functionality doesn't work at all. I've tried with two different SIM's, one being a T-Mobile and the other a Cingular. Both just show no service when inserted, although if I place those SIM's into other phones everything works properly without issue and I get 'full bars' (I have another Cingular 8125 and a T-Mobile SDA).
Here is what I have done so far:
- Reupgraded the Radio to the latest rev 1.15
- Recreated the nk.nbf again with retyping the operator code
- Reupgraded to the ROM to Helmi's
- Reunlocked SIM with xdadev_all_unlock-v1.5.exe
... and still no phone service.
Any suggestions on how to get the phone functionality to work properly? Its pretty much useless right now...
Thanks!
tempie23
I'm not sure that T%CID is right for an operator code... I know for O2 UK it's O2___001 and I'm sure a T-Mobile code isT-MOB101, both of these are 8 digits... check you're devicedata output again and use the setoperator.bat to set it properly, then try again
It's all good clean fun
spkr4thdd
I have the same operator code T%CID? but only on WM5. When i use 2003SE it is DANGA001.
tempie23
I had such error on TuMa 1.4 but reinstalling the ROM helped for a while. Then I tried helmi's ROM and the problem gone. But a couple of days ago it appeared once and reflashing did not help. What I done is downgraded to 2003SE, did a hardreset and reinserted SIM. The phone came back to work. Then installed helmi's ROM again. Now it is working for a day without any trouble, HOPE it's gone forever.
Tried a few things...
I tried downgrading and then reupgrading, but it still is stuck. No phone service. Interestingly enough the LED for the phone doesn't even come on anymore.
Interestingly enough when I select the phone settings from the upper menu I'm getting a Popup message stating "The phone is not ready. Wait 15 Seconds and try again." Obviously waiting 15 seconds does nothing...
Any other ideas?
Thanks!
tempie23
sometimes (happened to me) the operator info corrupts when upgrading to WM5
copy the files attached to the update directory and run 'MaUpgradeUt_noID.exe'
spkr4thdd said:
I'm not sure that T%CID is right for an operator code... I know for O2 UK it's O2___001 and I'm sure a T-Mobile code isT-MOB101, both of these are 8 digits... check you're devicedata output again and use the setoperator.bat to set it properly, then try again
It's all good clean fun
Click to expand...
Click to collapse
No it is not, it sounds like he has the same SX 66 that I have.
The ID is = AT%CID?
I posted this in this thead Here
read my above post, it can happen to anyone when upgrading to any wm5, mine happened the very first time i upgraded (TuMa 1.3), i dont know how it happens, but it seems to be permanent even with further reflashes (haven't tried 2k3)
NO Service
Midget_1990 said:
read my above post, it can happen to anyone when upgrading to any wm5, mine happened the very first time i upgraded (TuMa 1.3), i dont know how it happens, but it seems to be permanent even with further reflashes (haven't tried 2k3)
Click to expand...
Click to collapse
HI.
Sorry for my post, but I did not "get" how to fix the "NO Service" error:
This is what I've done today with Helmi_BA_WM2k5_AKU3.5_v1.4.CF2 by baniaczek:
Hi all.
Today finally spent some time, trying to upgrade my Qtek 9090.
Everything went fine:
1st) Did a SD backup of my current settings;
2nd) Updated ROM with SetOperator to my Operator (got from getdevice.txt);
2nd) Updated without problems;
Then used the Qtek by 5 minutes (inclusively i did a phone call), after that could no longer get the "phone" working - exactly when I received a call, the phone "gone out" and never more. After several soft resets and hard resets the phone was always with "no service" message (but strangely, I could go to settings phone, and look for "the broadcasting" networks).
I swaped the SIM to another phone and it was working, never the less I got another working sim, but the problem continues (btw, I always have the PinCode disabled, and I remember now that I forgot to test enabling PinCode request!!!).
Then, just in case I downgraded the phone to W2003SE, again, and everything was working fine.
My radio was 1.12. So upgraded radio to 1.15, and started over again but with no sucess.
When I downgraded once again, the Qtek works fine with either RADIO versions or sims.
Has anyone got this "nice feature"?????
Is there any overcame solution? (My only missing test is to enable Pincode, and test if it works?)
tks for any help
I'm having the same issue here as well, tried the comm manger on and off and disable and enable it. Still makes no difference, someone please help me out, I can't get anyone to help me
Ok, I posted a thread on the main wizard forum and I'm trying again here since this is a little more on topic in this forum.
Here goes with all the technical specifics I can add in.
I recently got an HTC 8125 (I've had one before and never had this problem)
I immediately CID and SIM unlocked the phone using lokiwiz's unlocking program.
I inserted my tmobile sim into the cingular 8125 and all was great.
I upgraded the ROM to the TNT 19199 batch of WM6.1 Everything is still great.
The phone worked awesome, the next day I downloaded the T-Mobile UK radio version 2.19.11.
I flashed it to the phone and everything seemed fine, the program finished and the phone restarted.
Upon restart I was greeted with a no service message and the phone behaves as though it is shutoff. No big deal, right? WRONG...
I went to the tmobile and cingular site and got the default roms from each just in case.
I then connected the phone to the usb and activesync would not recognize the phone, or do anything for that matter.
I used an external USB bluetooth dongle to try and connect the phone to the PC to flash the default rom and fix the radio problem, this wouldn't work either.
I then put the phone into bootloader mode, this works ok, I see the USB in the corner and figure I'm saved. Nope.
I ALWAYS get an Error Connecting from the rom software. Even though my PC recognizes the phone, active sync does not. I re-installed Activesync and rebooted my computer numerous times. To no avail.
The ONLY rom software I which has worked is the TNT 19199 but it doesn't fix the lack of radio.
Here are some other points of interest. On phone bootup I get this:
IPL 1.08
SPL 1.08
<----Notice, NOTHING in the GSM spot.
OS 1.11.1.0.1 (or whatever the numbers are for that particular rom)
The USB will recognize the phone ONLY in bootloader mode, otherwise when the phone is on the Today screen I get no recognition.
The TNT rom has worked twice when I tried it, (by worked I mean it allowed me to re-flash the same rom) Of course the TNT rom doesn't work all the time, it has given me several connection errors.
No other rom has worked as of yet, all others give me a connection error.
The battery meter will not display, nor will it tell me what type of battery or how much charge is left.
The phone will sometimes go to amber light when plugged into the wall charger but NEVER with the usb to PC cable.
I can still navigate around the windows mobile 6.1 interface though it moves incredibly SLOW. i.e. I pushed the comm manager button to make sure the phone didn't simply get shutoff and I waited about a minute and a half or longer for it to bring up the comm manager.
I need some severely good advice and some new tricks to try, I'm running out of ideas, I saw several threads under the HTC TyTn threads about similar problems and something about the IPL/SPL being important but I'm not sure what they're talking about. I have searched this forum and I have found people talking about similar problems, all the responses point to, "If you can get to the bootloader you're fine." This is incorrect.
So seriously, help me out here.
HOW DO I FIX MY STINKIN' PHONE.
I would suggest rolling back to your working configuraton by reflashing using a memory card instead of the USB.
fixed.
Actually I finally figured it out.
It seemed the reason that those roms worked sometimes but not others was this: To get the phone to recognize you had to do things in a VERY specific sequence.
You had to let the phone boot all the way into WM6 and then plug in the usb cable. Then put it into bootloader with the camera / soft reset button method. Then you waited for the nice USB connect sound, and began the ROM flash RUU program. (In this case it was the T-Mobile default rom).
Once that was done the phone acts as normal and everything is good.
Doing anything out of order or putting the phone into bootloader without it having first booted all the way to the OS would give you the connect error.
Please clarify if you're running WM6 with IPL/SPL 1.xx? I believe that's not possible to get good results that way.
IPL 1.08
SPL 1.08
<----Notice, NOTHING in the GSM spot.
OS 1.11.1.0.1 (or whatever the numbers are for that particular rom)
TNT 19199 batch of WM6.1
Wm6.1 on ipl/spl 1.xx,strange ,how do you explain this,how did you manage to get wm6 installed with ipl/spl 1.xx,cuz it only works on ipl/spl 2.xx and higher. Are you sure its TNT 19199 series wm6.1 Rom ?
Not sure how this has come about but I used to be able to connect to internet really easily through my work laptop when the TyTn II was connected by either Bluetooth or USB. Now I don't seem to be able to connect to either????
When connecting through USB I seem to be able to connect to the PC via 'Internet Sharing' which also lights up the 'Data Connection' icon but when I try to use IE it just says 'Cannot connect using current settings'. Thing is, I haven't changed anything and it used to work fine. Getting a bit fed up with the whole TyTn II at moment as I seem to spend more time fathoming why it's not doing what I want than doing it. Beginning to think a seperate phone/PDA may be best way ahead.
Unsure of whether the problem is related to the official 6.1 upgrade or the install of NoData (as I got fed up with accidentally hitting the weather and Quick GPS refresh and having the phone eat money).
Regardless of what I try I can't seem to get it to connect to internet albeit phone shows as connected via both Bluetooth or USB.
Short of solving this (and I'm not sure where to start) I'm temted to do a reflash and leave out things like No Data etc etc and just see if it works again. Bit of a nuisance really.
Tried searching all manner of related topics but no joy so far
It is a problem with the WM 6.1 official HTC update
I had exactly the same problem in reverse with my TyTN II when it was running the WM 6.1 (the same official HTC ROM that you have). By 'in reverse' I mean I couldn't initially do internet related things on the TyTN II using my home internet (either via USB or Bluetooth connection). It was fine before but after the upgrade thats when the problem occurred. I didn't have any additional software installed apart from Tomtom Navigator 6.032 (HTC Version) so I don't think your NoData install will be to blame (at least not solely). I did manage to get pocket IE working under these circumstances though after I had a fiddle around in the connections tab under settings - or was it Activesyncs settings.... I could never get the automatic Quick GPS updates to occur though, even under those settings and I still had to manually update (although it did use the home internet connection when I did this).
I remember that I changed a drop down selection from something along the lines of this device is connected to 'Auto' to make it 'The Internet'. Sorry for being so vague but I've now reverted to the original WM 6.0 ROM (more precisely I had HTC do it for free under the warranty) and none of the options I'm looking at now ring any bells. Perhaps someone else recalls more clearly what settings change is required.
I think the most important part of your post is:
Empgamer said:
Getting a bit fed up with the whole TyTn II at moment as I seem to spend more time fathoming why it's not doing what I want than doing it.
Click to expand...
Click to collapse
Thats how I felt about the HTC upgrade that wasn't. I was quick to go down the upgrade path but since it's been back with WM 6.0 other than a few uncommanded resets in the first day or two which haven't since reoccured, the device is now rock solid again. Of course it'd be nice to think the latest HTC upgrade didn't introduce more problems than were already present but in my experience their current update is more trouble than it's worth (and you haven't even mentioned GPS). If you decide you want it reverted under warranty, I found the HTC Repair Centre (at least here in the UK) to do a fine job of it. I dropped off my phone in the morning, after booking it in over ther phone the day before and it was ready at the end of the same day.
Flying Kiwi said:
If you decide you want it reverted under warranty, I found the HTC Repair Centre (at least here in the UK) to do a fine job of it. I dropped off my phone in the morning, after booking it in over ther phone the day before and it was ready at the end of the same day.
Click to expand...
Click to collapse
Or you can always download the original shipped roms here off the wiki and flash it yourself. It only takes about 10 minutes. You dont have to download a special SPL for an OEM rom
http://wiki.xda-developers.com/index.php?pagename=Kaiser_ROMs
The spl is an issue - reverting it
pyraxiate said:
Or you can always download the original shipped roms here off the wiki and flash it yourself.
Click to expand...
Click to collapse
I was tempted to do that myself (and even asked HTC for the downgrade file to do so) but there are a couple of issues for those of us that like to keep things 'HTC Official'. A big one for me is that since HTC was responsible for creating the buggy WM 6.1 ROM, they should also accept responsibility for fixing it (fat chance of that, I agree with what -888- wrote in the WM 6.0 vs. WM 6.1 thread here http://forum.xda-developers.com/showthread.php?t=432482&page=4 along the lines of the best developers being assigned to the latest and greatest products). If they're not going to fix it, then they should at least revert the device to a reliable state. I was in a fortunate position to be in the area of the HTC Repair Centre but if it means sending the phone away, I understand why some might prefer the DIY option.
It only takes about 10 minutes. You dont have to download a special SPL for an OEM rom
Click to expand...
Click to collapse
There's alot to digest about ROM (and Radio and spl) flashing in the wiki and that takes much more than 10 mins. Although a special spl such as hardSPL isn't used with the HTC official setups, the spl does need to be reverted from the 3.28 version with the official WM 6.1 WWE, back to a 1.xx version with WM 6.0 for proper functioning. That isn't just a simple case of running the RUU program like the upgrade to WM 6.1 was - it has to be manually reverted (presumably using something like jumpSPL and the procedure in the wiki for restoring a device for warranty purposes) so it gets more complicated. I was expecting spl version something along the lines of 1.56 on my WM 6.0 setup (to match the ROM numbers) but they installed 1.93, presumably because it was more reliable or offered other performance benifits. Perhaps the ideal spl is in the package already but again this cant just be run like the WM 6.1 upgrade was so there's some jiggery pokery involved
I tend to agree. Not sure why I really bothered with 6.1. One of the first things I did was use Kaiser Tweaks to turn threaded SMS off.
I didn't realise that reverting to WM 6.0 would require more than reflashing so that makes it a little more problematic. I'm not near a HTC Centre. The whole device certainly seems more buggy under 6.1 than it did before and this internet through laptop problem is a nuisance. Being fairly unimpressed with Co-Pilot I don't use GPS that much and, withe the aside that i think I've used the keyboard twice since I had it (another 'essential' I'd put on my list for phone/PDA attributes), I'm beginning to wonder if return to factor state and sell it might not be the better option, reverting to a Nokia E51 and Ipaq 214 Enterprise combination
Post is an option.
Empgamer said:
I'm beginning to wonder if return to factor state and sell it might not be the better option, reverting to a Nokia E51 and Ipaq 214 Enterprise combination
Click to expand...
Click to collapse
Of course it's up to you but don't forget that even though you may not be near a HTC Repair Centre, you could still call them up on the phone to make the booking and post the device to them once you've arranged to have it reverted. They should do it for free but confirm this so you don't get any unpleasant surprises.
I have had a Treo 750 on AT&T for the last year and a half or so, and have never gone "outside the box" for upgrades til recently.
Device started as WM5.1 and I used the AT&T upgrade to get to 6.0
About a month or so ago, work ported my number from AT&T to T-Mobile and gave me a BB Curve 8320 as a new phone. While I used to use BB's, after getting into the WM side, I quickly realized I couldnt go back, and decided to unlock my Treo, and use the T-Mobile sim in it.
Everything has been working, but other projects have kept me from being able to look into why I wasnt getting 3G on the Treo. I would consistently have a G indicator, and dslreports never would report higher than 180K on a 100K d/l test.
I started to try to fix it by upgrading to the WM6.1 generic img that is here - since I already was set up for SD card upgrading, this was pretty easy, tho it didnt fix the speed issue.
I next looked at the radio - firmware was reported as 1.16, so I bumped it to 1.50.00.0, as this was the highest on the wiki that reported success with T-Mo. By doing this, I was able to get the G to change to an E, but I think this was largely just a lateral move, as the speeds havent changed at all.
I have tried numerous times to re-flash the radio, but the firmware never changes - always say 1.50.00.00
The weird thing to me is that i even fell back to WM6.0 by getting the nbh file out of the 2.27 ROW Palm updater, but even though it did fall back to that OS, the software version still reported TREO750-2.25-ATT and firmware was still 1.50.00.00
I reapplied the generic 6.1, still shows the same software and firmware.
Even though everything "works" - I'd still like to get 3G if at all possible, and would love any suggestions of other things to try, if anyone has any...
Thanks!