Hello all,
I'm having problems upgrading my HTC Touch Pro2 to Energy ROM (Standard). It's probably a problem with the connection rather than the upgrade.
I downloaded the Standard Energy ROM for Touch Pro2 from EnergyRoms.com, and did everything as specified in the instructions: made sure the battery is charged, and established an ActiveSync connection.
However, when I proceed with the upgrade, the following happens:
1) ActiveSync disconnects
2) HTC USB Upgrade software gets auto-installed (if it's the first time run on that PC)
3) The ROM upgrade starts, and progress bars appear both on the phone screen and on the PC utility
4) .... nothing happens. The progress bars stay at 0% for a few minutes.
5) The upgrade utility reports there is a communication error [262: Update Error].
No harm done: after removing and replacing the battery, the phone works as previously. Something just doesn't let the ROM upgrade through. I've tried this on two WinXP PCs and one Win7 PC already.
Note: Currently there is no SIM card in the phone. But I suppose this is not relevant? (haven't tried it with the SIM card present yet)
Anyone else run into this problem? Any insights appreciated.
Maybe a dumb observation... but you don't specifically mention if you've done the hard-spl step?
Thank you for your reply. Not a dumb observation at all, the joke is on me. I haven't done that step. I didn't know. n44b.
I'm located in Finland and ordered my phone from the UK so it's a GSM phone. After posting this question I did some Googling around but only found links to old threads which I wasn't sure if they were still valid.
I presume there's a recent, up to date thread on the subject somewhere here?
Ah, found it, via the Wiki:
http://forum.xda-developers.com/showthread.php?t=550131
All right, then! I'll attempt update again later this week.
All done. And all this went easier than I thought (the only obstacle I ran into was that I had to disable my anti-virus while hard-SPLing).
Yes, it's very stable and fast. I can't believe my phone is still operational after being left alone overnight. Before this, my TP2 (with official HTC ROM updates) froze 3-5 times a day and had to be reset by removing the battery.
Welcome to the world of custom ROMs. Good luck with your new addiciton.
Related
Having done dozens of updates over the past couple of years I've finally had my first problem occur. I've searched the other postings and been unable to find anything which is similar to the effects that I'm getting.
For some reason I'm unable to upgrade the radio rom - just the radio rom, the other roms updates go in perfectly OK.
The universal displays the screen that it's "started upgrading.... Please wait" but then nothing happens. Eventually the the upgrade tool times out. I've tried about 10 different radio roms (ones that I know I've loaded before) but no luck.
All firewalls are turned off, I'm not using vista, direct USB connection, and other roms update OK so I'm really not sure what's happened. It's now left me with a universal with no radio rom at all!
Has anyone any ideas or is it perhaps that this rom has broke in the device?
Try removing the sim card and the SD-card.
Ok, PC is fine, close any running programs. Hermes has stock WM5 with some programs added. Only reg tweaks are PTT and removed 3G animation at start.
Device syncs normally every day and both Work and Home.
When I follow all the directions, run the Updater - The PPC gets the Color Bars as the Updater is trying to read it....then AS (V4.5) disconnects and closes. (gone from taskbar) I can soft reset the device, reopen AS, they sync just fine. At this point I have the updater do the next, it pulls up the Current ROM info and says it will upgrade to the new one. I select next, and it starts.....and AS closes again. After a minute the upgrade app says it lost connection. (duh!)
Any ideas why?
I'm not a stranger to upgrading roms on PPC's, have several that have both been updated a number of times. No issues, though that several AS versions earlier.
I've given thought to Hard Reseting the device, but I'm wondering if its more AS's fault.
Any and all input much appreciated!
Thank You!
JETninja said:
Ok, PC is fine, close any running programs. Hermes has stock WM5 with some programs added. Only reg tweaks are PTT and removed 3G animation at start.
Device syncs normally every day and both Work and Home.
When I follow all the directions, run the Updater - The PPC gets the Color Bars as the Updater is trying to read it....then AS (V4.5) disconnects and closes. (gone from taskbar) I can soft reset the device, reopen AS, they sync just fine. At this point I have the updater do the next, it pulls up the Current ROM info and says it will upgrade to the new one. I select next, and it starts.....and AS closes again. After a minute the upgrade app says it lost connection. (duh!)
Any ideas why?
I'm not a stranger to upgrading roms on PPC's, have several that have both been updated a number of times. No issues, though that several AS versions earlier.
I've given thought to Hard Reseting the device, but I'm wondering if its more AS's fault.
Any and all input much appreciated!
Thank You!
Click to expand...
Click to collapse
Are you following the directions at THIS GUIDE . What ROM are you trying to put on there? Did you CID unlock the device? Are you running Vista? Do you have .NET 2.0 or 3.0 version?
That should be enough questions to get us started.
Did you read my title? This is the stock ATT WM6 that came out yesterday. No need to unlock the phone, it is a 1 week old ATT 8525 with the stock ATT WM5 Rom on it.....
Windows XP SP2+ PC.
If it's the rom RUU_Hermes_CINGULAR_WWE_3.62.502.3_6275_1.54.07.00_108_UOOS_SVN05_Ship maybe it had some problems because if you go to the official release site http://www.htcamerica.net/support/8525/software-downloads.html they are still showing the WM5 rom for download.
There may have been a problem with the release and they pulled it back for some reason. Just a thought and not much help I'm afraid.
Yes thats it. When it ID's my current Rom and what it will upgrade to, it is correct. (it shows it's 3.62 vs my current 2.xx) Many peeps have had no problem upgrading to it. (most find it a very good Rom from the varios sites I read)
And this page at HTC still has it up:
http://www.america.htc.com/support/8525/software-downloads.html
JETninja said:
Ok, PC is fine, close any running programs. Hermes has stock WM5 with some programs added. Only reg tweaks are PTT and removed 3G animation at start.
Device syncs normally every day and both Work and Home.
When I follow all the directions, run the Updater - The PPC gets the Color Bars as the Updater is trying to read it....then AS (V4.5) disconnects and closes. (gone from taskbar) I can soft reset the device, reopen AS, they sync just fine. At this point I have the updater do the next, it pulls up the Current ROM info and says it will upgrade to the new one. I select next, and it starts.....and AS closes again. After a minute the upgrade app says it lost connection. (duh!)
Any ideas why?
I'm not a stranger to upgrading roms on PPC's, have several that have both been updated a number of times. No issues, though that several AS versions earlier.
I've given thought to Hard Reseting the device, but I'm wondering if its more AS's fault.
Any and all input much appreciated!
Thank You!
Click to expand...
Click to collapse
You just need to wait for a while AS shuts down that is normal be patient and it will start updating you will see a progress bar will take approx 10 min after that
@brorex he can wait till christmas next year, if the updater cant communicate with the device , because it has closed AS then it will never update.
@JETninja
try doing what i said to this guy here,
http://forum.xda-developers.com/showthread.php?t=341282
yesterday he upgraded with the same rom and device and it worked
brorex said:
You just need to wait for a while AS shuts down that is normal be patient and it will start updating you will see a progress bar will take approx 10 min after that
Click to expand...
Click to collapse
I thought that too, but after the color bar test when it want to set you up to actually install the ROM, the Upgrader whats you to make sure there is an active connection with AS. Well, there isn't. It shut down and the PPC is still showing the color bars. I can reset it, then re-sync to AS. (after having to re-launch AS from the Program Files - it no longer resides in the Tray when it shuts down during the process) I then get it going again, it attempts to start the ROM upgrade, AS quits again.....about a min later I get the Communication Error message....
I'm downloading a 2nd copy right now, will try it as soon as it completes...
*Edit...think I have an idea what I'm doing wrong, I have it connected and synced too early, the first part of the ROM updater is just a PC test, I'm thinking the PPC should not have been connected at that time. Re-trying it now.....
Try putting it in boot loader and upload...thats what i did when i updated my 8525...Very much like the new ROM...
Going to give it a shot here at work on this PC. If no go still, will try the above mentioned methods. PC at home kept getting communication errors...
i had the same problem
make the connection at AS then start the update process.... the 8525 will go into 3 bar mode and when the update gets to the upgrading rom screen... the installed rom wont show up.... hit upgrade... and then continue and it will work.... i was stuck there for a while too because if i waited for the istallation to load then made the as connection the right image would show up in the installer but then it would stop working after that.....
I just put this rom on my 8525 and it worked well for me. My 8525 is unlocked with supercid so I had to extract the OS and update using the methods described for working with SPL-140 Olipro with IPL-1.01 or the "How not to Brick thread".
That won't help you much as you don't want to do that mod to your New 8525 and void the warranty, but thought you might like to know the stock OS seems pretty stable at this point and I have had no problems yet.
Thanks everyone! It finally worked here on my Work PC. At home I could get to the Bootloader, but it would lose connection for some reason. Here I lost it the first time, but tried it again and it managed to stay connected and apply the update. Got it up and running, applied owner info, just now re-doing the AS relationship. (a good 500+ contacts! LOL! It'll take a little while as usual!)
Then it's back to all the tweaks I like so far...and some new ones I've held up on since I've been waiting for WM6.
Out of my 3 PDA's (2 ipaqs and this puppy) this one has certainly been the trickiest ROM update, but it seems to be more my device since most don't have this much trouble.
Thanks again!
So far- So good, but just one problem- BATTERY!!!
After I installed upgrade, my battery drains in few hours... I reset phone, I reloded upgrade- nothing helps! Warranty still in affect, but phone worked well and I'm positive- hardware is OK. What else can i do to fix this problem?
I have the same problem
ai6908 said:
Try putting it in boot loader and upload...thats what i did when i updated my 8525...Very much like the new ROM...
Click to expand...
Click to collapse
I have the same problem exactly. As soon as I start the upgrade the device immediately sleeps and the connection is lost. 1 minute later I get a Connection error message.
I am new to all this. How do i put the machine in 'boot loader' mode?
Thanks
Just did this rom update again on a 8525 the installation went extracting files active sync shut down wait a few minutes nothing happens the the upgrade screen no ACTIVESYNC connection while update is happening as soon as device is in bootloader mode activesync closes out
I have a imported DIA100 phone, and trying it on the T-mobile network here in the states. everything was fine up until today when i upgraded my phone to the 1.93 series, now it randomly shuts off, and it cannot connect to the T-mobile network, keeps saying (searching). I don't know what's going on, I reflashed the device and it still does the same thing, infact it might even be worse now. Restarting the phone doesn't work, as it keeps restarting from the boot. Anyone have any idea what to do? I'm going back to 1.35.
Intradvocate said:
I have a imported DIA100 phone, and trying it on the T-mobile network here in the states. everything was fine up until today when i upgraded my phone to the 1.93 series, now it randomly shuts off, and it cannot connect to the T-mobile network, keeps saying (searching). I don't know what's going on, I reflashed the device and it still does the same thing, infact it might even be worse now. Restarting the phone doesn't work, as it keeps restarting from the boot. Anyone have any idea what to do? I'm going back to 1.35.
Click to expand...
Click to collapse
i too have many problems with 1.93.456.2 WWE baserom. somehow, it just doesn't seem so stable ... not sure if many others are feeling the same for 1.93 roms. i guess 1.37.456.2 ME WWE is still the most stable at the moment...
if only we can have a review on all official rom consolidated in one thread.
Sprite?
Did you use Sprite to backup your previous rom and store it in 1.93xxx?
This could be the cause.
ruffruff said:
i too have many problems with 1.93.456.2 WWE baserom. somehow, it just doesn't seem so stable ... not sure if many others are feeling the same for 1.93 roms. i guess 1.37.456.2 ME WWE is still the most stable at the moment...
if only we can have a review on all official rom consolidated in one thread.
Click to expand...
Click to collapse
Yes i had same problems. imo the 1.93 isnt a stable rom(yet) so im back with 1.37.456.2 this one is just perfect,very stable,less memory leakage.
Well, the problem is still on going. I can't flash my phone anymore for some reason, even though I've tried both, unsigned and signed Hard-SPL, which both of them flash fine. However, the phone gives me error [276] update error. So not sure what exactly is going on here.
Also, no, didn't sprite backup, phone's just being retarded, mobilecityonline will repair it, but it will take almost 4-6weeks, I cannot wait that long. What else should i try?
Okay, nope not fixed... Flashed it with 1.37, connected to the network for a few seconds, dialed somebody and no ring or anything, but when i called my phone i could hear my own voice. So I guess i have to send it in for repair. Damn.
berlinberlin said:
Did you use Sprite to backup your previous rom and store it in 1.93xxx?
This could be the cause.
Click to expand...
Click to collapse
Could you please detail? I've flashed 1.93.xxx just in the day it appeared on the site and after flashing, I've restored the backup made with Sprite Backup to preserve the settings and so on. I wasn't worried about the contacts/calendar since I have them in Outlook, but I didn't want to start all over with settings, install programs and so. I've made the restore in "upgrade mode", restoring also the databases. The result was that I got a verry strange TF3D, displaying "Home" between the operator name and date, and strange behaviour. I've seen also that the animations were taken out so I've flashed back 1.37.xxx.3. Could be any problems generated by the restore operation? Should I use a different restore type (eventually not selecting "restore databases")?
I have had no problem with the new 1.93xx rom.
Touch FLO 3d is quicker (probably because the animation is disabled)..
and the battery life is about 20% better
Radio ROM Anyone
Sounds like the Radio...
What version is everyone on? The 1.93 ROM updates the Radio, have you tried downgrading to 03?
mhbr12742 said:
Sounds like the Radio...
What version is everyone on? The 1.93 ROM updates the Radio, have you tried downgrading to 03?
Click to expand...
Click to collapse
I am on 05 and has no problem ( have been using it for a day now)
I don't know, but If i plug the diamond into my adapter, the network suddenly works and I can actually make calls and everything's fine and dandy, but just on the battery, I can't call anyone, and if I pull out the adapter when the phone gets a signal, the signal stays but again, can't call anyone because i can't hear anything.
It's an awkward problem. I'm not sure if it's my battery or something. So I'm getting another battery off ebay since they don't sell HTC Touch Diamonds in the U.S. yet.
I've been having random freezes with the 1.93.xxx
Anybody else experienced that?
A.
adwinp said:
I've been having random freezes with the 1.93.xxx
Anybody else experienced that?
A.
Click to expand...
Click to collapse
Yes, me I had same problem twice - freezes on PIN input screen, second problem with this release is that sometimes PIN screen doesn't appear. Now I'm back on 1.37 and everything seems to be ok
Intradvocate said:
I have a imported DIA100 phone, and trying it on the T-mobile network here in the states. everything was fine up until today when i upgraded my phone to the 1.93 series, now it randomly shuts off, and it cannot connect to the T-mobile network, keeps saying (searching). I don't know what's going on, I reflashed the device and it still does the same thing, infact it might even be worse now. Restarting the phone doesn't work, as it keeps restarting from the boot. Anyone have any idea what to do? I'm going back to 1.35.
Click to expand...
Click to collapse
THe Problem you've encountered:
1. Random auto reboot
2. Random freeze
3. etc.
It's sounds familiar to me. Well it's maybe have to do with SPL just like the Kaisers do.Well, I said maybe... So, what we did to our Kaiser before is flashing the HardSPL which has the same version number as the ROM flashed. So, if you're using ROM 1.93 then the HardSPL should be flashed is Olinex HardSPL 1.93 or you can try one by one of the developed HardSPL existed in this forum. My saying is, go with HardSPL 1.93 and see what happen. If it's still no go then it must have to do with the ROM itself.
Just my 2cents.
Hi all,
My Diamond is acting weird lately; sometimes (so far it seems at random) when I turn on the device (from standby), the display is grey'ish / scrambled, and nothing works. I have to removed the battery to get it working again.
This happens with all ROMS found here (haven't tried stock rom yet).
Anyone know what this might cause?
I'm running dev. edition SPL from olinex...
Any tips would be greatly appreciated!
/edit; Could this be SPL related?
Maybe perform the hardSPL again?
Reform the battery for a minute. After this hard reset your device a few times.
If this doens't fix the problem use your original ROM and send the device back for repair.
Would be my solution
I have the same problem. Diamond swiches to standby mode and does not resume or just the light switches on and the screen is blank. Sometimes, it even switches off while booting. All the time, I have to remove the battery. And after some "battery remove resets", the error seems to occur more and more often. It also suddenly looses the phone signal but immediately finds a new one ofter 1-2 seconds.
I think it is somehow related to the phone chip-whatever. Because when I turn the phone of it seems to run more stable. Errors are not gone but at least I can use it as a mp3 player then.
I tried lots of roms but none of them worked fine. I even restored the original spl to make sure it is not the spl. But error is still there... stronger than ever
I will send it back to htc. This thing is obviously broken. Its one of the typical qualcomm errors. These chips are... what do you say in english... moody? My old polaris had a similar error. the 3g part of the phone went away.
TerianSilva said:
I have the same problem. Diamond swiches to standby mode and does not resume or just the light switches on and the screen is blank. Sometimes, it even switches off while booting. All the time, I have to remove the battery. And after some "battery remove resets", the error seems to occur more and more often. It also suddenly looses the phone signal but immediately finds a new one ofter 1-2 seconds.
I think it is somehow related to the phone chip-whatever. Because when I turn the phone of it seems to run more stable. Errors are not gone but at least I can use it as a mp3 player then.
I tried lots of roms but none of them worked fine. I even restored the original spl to make sure it is not the spl. But error is still there... stronger than ever
I will send it back to htc. This thing is obviously broken. Its one of the typical qualcomm errors. These chips are... what do you say in english... moody? My old polaris had a similar error. the 3g part of the phone went away.
Click to expand...
Click to collapse
Sounds bad
I'm trying an updated radio rom at the moment, we'll see if it hangs today...
mikkelnl said:
Hi all,
My Diamond is acting weird lately; sometimes (so far it seems at random) when I turn on the device (from standby), the display is grey'ish / scrambled, and nothing works. I have to removed the battery to get it working again.
This happens with all ROMS found here (haven't tried stock rom yet).
Anyone know what this might cause?
I'm running dev. edition SPL from olinex...
Any tips would be greatly appreciated!
/edit; Could this be SPL related?
Click to expand...
Click to collapse
Hi mikkelnl... from what you described, it seems to be a typical problems with the SPL you are using. Depending on which SPL that the original ROM that came with your device, you can resolve by installing the respective 1.37 OliNex HardSPL Unsigned or the 1.93 OliNex HardSPL Unsigned by cmonex.
Try to get it from the same thread that you got the 1.40 OliNex HardSPL-Developers Edition. There is also some explanation on the problems that you are experiencing.
One more thing, Radio 1.00.25.08 also appears to have some detrimental effects on some devices after some usage. And it has a lingering effects too. Try use Radio 07 if you are in Europe or Radio 05 if you ar in Asia...
Having said all these, I must state that these are purely my observations and you really need to try it out for yourselves to know whether it works for you. I have given the same advice to about 5 users experiencing these problems and it had worked for them so far.
Swiftblade said:
Hi mikkelnl... from what you described, it seems to be a typical problems with the SPL you are using. Depending on which SPL that the original ROM that came with your device, you can resolve by installing the respective 1.37 OliNex HardSPL Unsigned or the 1.93 OliNex HardSPL Unsigned by cmonex.
Try to get it from the same thread that you got the 1.40 OliNex HardSPL-Developers Edition. There is also some explanation on the problems that you are experiencing.
One more thing, Radio 1.00.25.08 also appears to have some detrimental effects on some devices after some usage. And it has a lingering effects too. Try use Radio 07 if you are in Europe or Radio 05 if you ar in Asia...
Having said all these, I must state that these are purely my observations and you really need to try it out for yourselves to know whether it works for you. I have given the same advice to about 5 users experiencing these problems and it had worked for them so far.
Click to expand...
Click to collapse
Hi Swiftblade!
Thanks for the reply. I've read about those newer SPL versions, but I didn't think it was the reason for my problems, since I have one of the first Diamonds (can't remember the spl version ). And; the thread mentions "fuzziness issues on some newer diamonds", my screen is not 'fuzzy', it simply is scrambled and the device completely hangs. So I didn't figure that would be the problem
Anyways; I am a bit reluctant to install a new SPL, never did that before...
mikkelnl said:
Hi Swiftblade!
Thanks for the reply. I've read about those newer SPL versions, but I didn't think it was the reason for my problems, since I have one of the first Diamonds (can't remember the spl version ). And; the thread mentions "fuzziness issues on some newer diamonds", my screen is not 'fuzzy', it simply is scrambled and the device completely hangs. So I didn't figure that would be the problem
Anyways; I am a bit reluctant to install a new SPL, never did that before...
Click to expand...
Click to collapse
Hi mikkelnl.. It's really worth a try. the description on the thread is of course vague. It is actually to deal with some discrepancy issues between SPL and the device's specification.
Doing a HardSPL will not affect your rom but it will hard reset it so you get a fresh clean rom. Do perform a backup before you do a HardSPL though. My best bet is 1.37 OliNex HardSPL Unsigned.. Cheerz
Edited: If this HardSPLs can't solve your problems then it might be a hardware issue that you are facing...
Well, I just installed 1.37 olinex, let's see if this helps
Thanks for the input Swiftblade! Now I'll just have to re-setup your 7.0 rom
mikkelnl said:
Well, I just installed 1.37 olinex, let's see if this helps
Thanks for the input Swiftblade! Now I'll just have to re-setup your 7.0 rom
Click to expand...
Click to collapse
Hope it works out for you bro... Good Luck!
Did the 2.29.405.2 update OTA initially and noticed problems. So reinstalled it from SD card but no help.
Bought sim free, unbranded/locked and never rooted:
Cannot dial out from phone lists or contacts. Going to phone and clicking on an entry in the call list does not launch phone call any more. Going to contacts, opening one and clicking on an available phone number does not launch phone any more.
The only way I can make a call is to punch it in on the keypad! Grrr.
Wifi connects to my home base after a reboot but, after an undetermined amount of time it drops the connection and cannot get it again. Going to Wifi settings shows it scans, connects and tries to obtain IP address. After a short time it gives up, turns wifi off and starts over. Again & again.
Cannot get it to connect again without another reboot.
This is a crippling loss of functionality for me. Can anyone suggest a way to roll back this update so my phone works as id did?
Many thanks all,
M1
First try a hard rest(you will lose all personal data on the phone,pictures and other stuff on the SD will be fine). If that does not work try either the 2.29.405.2 or 2.10.405.2 RUU.
More info - to my horror, around 15 minutes after I had tried and failed to make calls from contacts the phone started making them one after the other as if they were stuck in a spool or something! Ouch - any thoughts?
Backup everything you can and flash the same ruu from shipped roms.
Sent from my HTC Desire using XDA App
> flash the same ruu from shipped roms
where do I find this? - android noob!
http://shipped-roms.com/download.ph...9.00.32U_5.11.05.27_release_151783_signed.exe
And if it works, keep it safe!
Sent from my HTC Desire using XDA App
Thanks to all for help on this. Decided worth a trouble shoot before a hard reset and culprit seems to have been an app - extended controls widget. Removed this and all seems well again.
Try this one. This definately works! i have used it.
http://forum.xda-developers.com/showthread.php?t=768256
I was stuck at 2.29 update.
Then i used this guide and windows tool.
So i did this process and it rolled my phone back to stock android 2.1 rom 1.X
The first version that the phone was bought with.
This tool will boot the phone into bootloader and load a stock 1.x rom ota off the sd card as the tool will extract it to sd card and then load it.
This will wipe all your data not sure about the sd card as i dont remember any of that because i formatted my sd card after i had used the tool.
Thats because i had rooted my phone and tried custom sense hd rom.
The only reason i had was of the battery usage as the consumption was very badly increased and that the 2.29 rom was unstable.
PS: I did first try the htc service in Denmark. They couldn't help me and said i was stuck with the 2.29 rom update. :/
After my phone got rolled/flashed back to stock android 2.1.
The next day in the morning i could upgrade again to android 2.2 rom ver. 2.10 OTA from htc servers.
Maybe this works for you as i did for me and others.
Turns out it wasn't the app.
After a couple of days playing ok my sim free stock htc desire is unstable again.
Cut me off mid call - went to phone and clicked on last call entry - absolutely nothing happened, repeated with same problem. Exited phone to home screen then opened contacts and tried to make call from there - same behavior, a complete hang.
No web access either so opened wifi manager to find it hanging on "obtaining IP address" from my home network and continually shutting down and restarting wifi automatically at this stage.
Noticed general UI lag and several apps failing to open too.
Left phone alone and again, around 10 minutes later all of the actions - including trying to make the phone calls started running one after the other. Like everything had been caught in a spool or something. After this all seemed OK until it happened all over again later.
Although the UI seemed OK and some apps worked as expected, the only way to get phone and wifi working whilst it was hung was a warm boot.
Dreading a hard reset as it's going to waste another day or two getting everything reconfigured just so (can't find a back up solution that does everything - multiple mail account settings etc) but looks like only option.
Will try going back to mikep99's suggested rom as soon as I have time and will not be responding to an HTC OTA auto update offer again.
Grrr.
I still suspect an app conflict.
Can anyone recommend a util that might give me a clue which app / sys process could be hogging system / radio resources?
just got another OTA update pushed to me. installed (nothing to loose) and Congratulations my phone has been updated to 2.29.405.5.
Not sure whats going on here as that was the update I got 2 days ago. This time round it was only 4.8mb download so I'm assuming it's an update update. Hope it fixes things .....