I'm having problems running the ROM upgrade by iMate. I keep getting Error 101 connection error, and I had grown to assume this was a problem relating to running from Virtual PC on a Mac rather than a real PC.
Today I at last managed to get access to a PC running Windows XP, activesync 3.7.1, and got exactly the same problem. I tried it several times.
I'm beginning to wonder if any of my past failed attempts on my mac have done something to the phone that is preventing it from being controlled properly by the ROM upgrade software?
Is there anything more than a hard reset to take the device back to factory settings?
Please - if anyone can help me get this sorted I'd be really grateful. The device is just too unreliable in it's current state, and I just cannot manage to get the ROM upgrade working. It's just unbelievably frustrating!
A hard reset will take the device to the last rom upgrade.
Now in your case this could be the failed rom upgrade which you did over the mac. You would have to look at the device info to check that.
If I was you I would do a rom upgrade of a PC and not off a mac, not that I have anything agaist macs (apart from ...) Its just that I know it works of a pc.
I tried a ROM upgrade from a PC this morning and it didn't work. It kept reseting the device, then said Error 101 connection error (even though it was connnecting fine to Activesync 3.7.1).
I've made a little progress since then. I've pressed power-reset-record to put it into the 'bootloader'? and this allows the installer to go one step further and says installing the radio rom (but never gets beyond 0%). I now get the error 114.
Now that I've got this far, I will have another go with a PC on Monday and see if that makes any difference.
I've just bought the SE K700i which I hope will be a little more reliable. I really just want to get the PDA2K upgraded so it's in a fit state to sell, and perhaps I might even consider keeping it if the ROM makes a radical difference to reliability. It's so nice to go back to just using iSync with the K700i without go-between software and Virtual PC and all that hassle. My plan is to use the K700i until something comes along that catches my attention (I'm still not convinced by the Treo 650 or P910, and I wont forget my experience of Pocket PC for a while!).
If I may add my experience on similar situation, I got a device which was upgraded using a wrong ROM file, and now it ended up with no radio and no operator ID :shock: ... and can't accept "standard" ROM upgrade ... I managed to be able to upgrade the ROM or Ext ROM individually by using null operator ID ... but when it comes to Radio upgrade it doesn't start at all giving failure.
Biso007
So what is the story if you let the device drain down and then take out the battery. Would a Normal offical update not work then.
I have yet to read anything about were on the device the Opid is coded in the hardware. What I know is that the ndf have the opcode in the header and this is checked against the getdevicedata.
I have had check for the opcode in regedit with no luck. (this I some what expected as I did not feel that it is part of the OS).
anybody have a better understanding on that issue?
when I run getdevicedata.exe I get nothing except "PH20B" ... so I used NULL opid to upgrade ROM and Ext ROM ... but this trick didn't work with the Radio part ... more over, I tried the trick of draining the battery down ... it worked only once and the radio is back (I don't know how!!) however, with the last reset after the upgrade the Radio is gone again!!
My suggestion so far is that the Radio part is there but it's inactive due to a problem with the charging circute ... and since the Radio is the 1st stage of the upgrade, it holds the whole process failed.
maybe someone with solid experience with the device design itself can shed more light on this issue.
Hum!
Well what I know about the radio is that it is Lang independent, which means what ever check is run on the upgrade it does not look for the lan code.
Further it must check against the radio type as this is part of the config file that is in the upgrade.
I know that a hardreset will load what ever file is around (so it must be stored in the orignal format on the device, then loaded on hardreset). This seems not to be true for the EXTrom as this seems to be extracted as files on the device (thus you can flush it).
So we have a hardcored opid somewere on the device that now shows zero for you. What was the shipped version of it. Have you tried a ship.exe from your original device without using the xda-tools.
Can you tried a radio only upgrade and used your shipped opid in the fix.bat (maybe after a battery drain again)
Seems a shame to have a paper wheight and not a phone.
Crossing my fingers, but now it worked!! :lol:
The only additional action I took this time is to take the battery out and close the bottome notch which I believe has something to do with the backup battery.
When the device restarted, the Radio part is back with the original version, IMEI and call durations which confirms my idea that the Radio part was always there but blocked by a power charging issue.
Update [27/2/2005 6:40 pm GMT +2]:
I checked the devicedata.txt file and it has nothing except "PH20B" ... this means for me that this device will never accept any official ROM upgrade in the future ... and doing a hard reset is a potential risk to loose the Radio again :?
Related
I've stuggled on with the unreliable ROM that my PDA2K came with because I have been unsuccessful at upgrading using my Mac and Virtual PC 7 (Windows XP).
I don't have access to a PC, and wondered whether anyone could give me any guidance.
Is it possible to upgrade the rom directly from the device itself, or are there ROM installers for other Blue Angel phones that would work via Virtual PC?
Any help very welcome - but please give as much detail as possible if telling me to install or change things manually. I've read posts about 'extended roms' and taking bits from here and there and I've no idea what this is about.
hello fellow mac user
What exactly is the problem?
ANy error messages? are you trying via BT or USB ?
HI,
When I tried to upgrade previously the PDA2K's screen showed USB but I got an error (sorry I cant remember the number code; radio upgrade error or something).
Recently, and I don't know what's changed, I just get Error 101: Connection Failure. When I try to run the upgrade the device does a soft reset at the beginning, then there is a long pause then I get the error. It seemed to manage more previously (may be that was an earlier from upgrade, but it never worked anyway!).
Have you been successful from your Mac?
Just looked back at my old posts on the howard forums, and discovered it was Error 114 I was getting previously (with the first ROM upgrade). I presume I'm getting the 101 connection error now that I'm trying to use the latest ROM upgrade.
One thing I'm about to try myself is to switch off both the windows and Mac OS X firewalls just in case they are interfering with the process.
Just to be more specific:
It comes up with the info from the phone and the upgrade, then I click next to start the upgrade; the device does a soft reset then repeatedly the device says it's connecting to host, the PC says reading info from device; then after a while I get error 101. As soon as the ROM upgrade installer quits, then Activesync reconnects the device (as guest).
Are the ERK files supposed to be run from the device? Will this help me? I've just downloaded one, and downloaded a thing called WinRAR but the resulting files say they aren't Win32 applications; and most of the contents of the folder are .rar files even after I extracted it. Wierd. Please can someone help!
Oh well, it's getting late here in the UK, I will just have to try again another time. Going to have to reinstall everything again now (as I have after every failed attempted at a ROM upgrade over the past few months). This is the last time I buy anything with a Microsoft operating system!!!!
Can anyone help?
Anyone?
Hi
Sorry but I don't think I am going to be much help.
I too am a Mac user with VPC and happily ActiveSync every day using VPC 7.01.
HOWEVER I would never try and use VPC to do something as basic as a ROM upgrade.
I managed to borrow a PC from someone at work and used that for the upgrade. I went on the basis that a ROM upgrade is so basic to the device and would likely need real PC hardware that I would not risk it.
Is there no colleagure, friend or workmate that can help you out?
Regards.
Robin
Hi,
Thanks for replying. I had bought Virtual PC because I just couldn't find any other way of getting a lot of the software onto the iMate. Having made this investment I hoped it would work with the ROM upgrade too.
I did manage to get use of a PC yesterday, but unfortunately it didn't work either. The PDA2K reset itself at the start, then after a delay the updater gave error 101 connection error, exactly the same as with Virtual PC.
Later, I managed to get someone really helpful at i-mate on the live support (and for once it didn't time out) and I went through a few things, including pressing power-reset-record (so that USB is displpayed) and trying from there. It still didn't work, I got Error 114 after the updater sat at 0% for several minutes.
This leads me to the exact reason I didn't want to have to rely on someone elses PC: having access to it for a limited time I tried repeatedly the ROM upgrade yesterday with no success. Later, at home, I got help from iMate and some ideas that will be trying again with a PC, but now I've got to wait for another opportunity to use a PC. What concerns me, is if I ever get a major problem the phone may be unusable until I next get access to a PC. Worse still - if the phone locks up when I'm using the PC and I don't have the time/knowledge to resolve it, I could end up with a non-functioning phone. It's much easier to tinker with these things in the comfort of my own home when time is less of an issue.
I just received my K700i yesterday. I decided enough was enough. I'm going to sell the PDA2K as soon as I've got the ROM sorted out. I really did try to get on with this device but it's caused me more grief than I have ever had with an electronic device before. I learned a lot, setting up GPRS, wifi, bluetooth, found all sorts of useful software, used VNC to control my Mac remotely etc etc, but at the end of the day I just couldn't rely on it. Some days I could get email, some days I couldn't. Some days people would receive the SMS I sent, some days they didn't. Sometimes the people I was calling could hear me, sometimes they couldn't. Sometimes the phone would stay switched off, sometimes it turned itself on and drained the battery. The list of problems I had with this phone were endless. Hence why I was trying to get the ROM upgraded.
I understand your concenr and problem.
I actually have the latest ROM installed on mine and I STILL get someof the problems you describe.
Only Microsoft could get away with writing such a crap operating system to run a phone.
And i-mates issues just compund the Windows issues.
Good luck.
Robin
ive never bothered even trying to run activesync thru vpc. It was a bit hit and miss on my XDA1 so as soon as my xda2i arrived i just bought missing sync from mark space. Hassle free syncing and installing, plus the ppc gets mounted like a mass storage device too.
Trouble is I use Outlook at work and need to sync it to my PDA.
I cannot even use Entourage as we are a) running to old a version of Outlook server and b) Missing Sync will not sync with Entourage.
I am stuffed both ways.
Robin
Me again!
Just thought I'd let everyone know that I did indeed succeed first time on a PC today (having pressed power-reset-record to go into bootloader mode first).
So, as everyone told me, it was necessary to use a PC, and Virtual PC on a Mac just wont work.
I'm getting on ok with my K700i, although the email seems a bit limiting (doesn't seem to have message titles displayed, and a short limit to the length of the email).
My plan: use the K700i for a few weeks and see how I get on, then perhaps I might try the newly upgraded PDA2K for a few weeks, and see which I prefer.
The other complicating factor is that the SIM free Treo 650 has just become available, but I'm going to hold fire on that for now. Perhaps if I'm not happy with either the K700i or the upgraded PDA2K then I might consider it...
So, I've unlocked my T-Mobile MDA G3 phone both CID and otherwise using loki. I've tried the T-Mobile update off their own site, and here is what happens. I suspect I need a different data cable, but I might be wrong there, so I figured I'd bring the issue to you all because you are the gurus of all gurus...type peoples.
So, here's what goes on. I download the software. I sync my MDA and my notebook. I ensure both machines are on and set to stay on. I check the connection and all is good. Heck, I've even backed up my MDA system using one of those backup utilities for Smartphones available online for trial download(which worked great, btw). So I run the software and click next and check everything it says the check and then it begins. This is where my problem begins and the goodness ends...
The MDA shuts off and just sits there. I don't touch it for fear of what might happen by being impatient, but every time, no matter which ROM I've tried to use for update purposes, the notebook pops up saying that it encountered a "communications error". It doesn't brick the phone, thank God. It simply just requires removal of the battery for 5-10 seconds after disconnecting the USB, then turning it on. It boots fine and all is good, except, no new ROM, same old 1.0.8.something version and bah!
I want to update my ROM and am stuck. I've tried at least 5 DIFFERENT ROMs and loaders and still the same thing.
I'm running the original T-Mobile ROM 1.0.8.something, IPL 1.X, and SPL 1.X. The phone says it's unlocked using the CheckLock program you can download from the forums, or elsewhere, I forget which. I've run the cidunlock with the loki tool multiple times and it finishes no issues.
If anyone has ANY ideas or thoughts, or even if they've run into this I'd like to know.
I'm pretty sure my phone right now won't do the whole A2DP via bluetooth bit, and that's what I'm REALLY wanting. I just got those Motorola HT820's and am anxious to play around with them more.
Anywho. You all rock and I've only been here like a day, but your information, walkthroughs, and just general geekiness(oh yeah, I work for the Geek Squad and we ALL use either the Verizon or Sprint version of the MDA, heh heh) have been most appreciated!
-----------
Originally posted under xda-developers > Wizard (Oops? )
You all probably have heard the things that have happened to others, this might be different.
I got my Audiovox XV6600 (verizon) from a friend. His father used it extensively so there were some blemishs and such on it, and the battery life is horrible.
That was about 4 months ago and a week after I got it, I flashed it to the lates firmware.
Before I continue, I would like to state that I am computer lieterate, so through anything at me. I have owned a few regular cell phones that I have modded with firmware and such (not personally modded but flashed). Same goes for regular PDAs. (But I will warn you that I am a horrible speller )
Yesterday, I went to use my phone, and a common error happened that requires a soft reset. When I hit talk on w/e number I am calling, it just says "Dialing" for like 3 minutes, even if I turn off the phone, it will complete the call later if it has too, no way of cancelling in unless I reset or wait.
So I reset it.
That is when wierd **** happened.
Normally, the screen will blank, Windows Mobile will pop up and about 10 seconds later the back light will pop on. Well it the light took about 1 minute to start and I noticed at lower right hand part of the screen it says
"p DM FAIL"
"r DM FAIL"
"2.07.00 WWE"
After it FINALLY boot, I noticed I that it said the phone was off and there was NO WAY of turning it back on.
My hunch is that somehow the radio ROM got corrupted or this phone finally bit the dust. Probably both. BUT I WILL NOT ACCEPT DEFEAT UNTILL ALL OF MY OPTIONS HAVE BEEN EXSAULSTED!
I have searched google, searched this forum, searched the wiki and nothing fixes this thing.
The first option = Reflash
Answer= I have tryed that multiple ways and I am typing this right now since I think I have tried everything.
Option A,
I got the latest ROMS from verisons site. When I flash I get the country ID error, so I tried it with the _noid updater. First time, got the id error again, second time, continued with the update BUT, NO PROGRESS happens on the radio update and that is the first update!
Option b =?
option f = THROUG THE F***ing THING AT THE GROUND! (but this is my ONLY phone and it will be months before i even get a **** phone!)
Here is what is listed in my Device information of the phone. Remember I can use the PDA side of this phone, but that is all. NO phone, NO inet, and it makes sense too, it is like I don't have the drivers for the radio.
ROM version:2.07.00 WWE
ROM Date: 02/07/06
Radio version: DM FAIL
Protocol version: DM FAIL
PRL version: N/A
ExtROM version: 2.07.00 WWE
Hardware Version: 0041
ESN: N/A
Browser Version: MSIE 6.0
(Info from GetDeviceData.exe)
PH20A2 ( and yes that is all that is in the txt file)
HELP!
EDIT: Wow, UTStarcom can suck my *....*
Meexplains what happend)
Tech: Your phone is "pooched"(wtf is that) Let me transfer you to *click* HELL no I am NOT going to send my freaking phone some where so you can restore my perment save and sell my contacts for money!
Starhero said:
You all probably have heard the things that have happened to others, this might be different.
Click to expand...
Click to collapse
I'm afraid it's not.
Starhero said:
I got my Audiovox XV6600 (verizon)
Click to expand...
Click to collapse
Starhero said:
error, so I tried it with the _noid updater. First time, got the id error again, second time, continued with the update BUT, NO PROGRESS happens on the radio update and that is the first update!
Click to expand...
Click to collapse
Starhero said:
Here is what is listed in my Device information of the phone. Remember I can use the PDA side of this phone, but that is all. NO phone, NO inet, and it makes sense too, it is like I don't have the drivers for the radio.
Click to expand...
Click to collapse
That is expected.
If you tried to flash your phone with a ROM image you pulled from here, it will not work. The wiki states that your phone is a CDMA phone, not a GSM phone. WM5 and 6 ROMs will not work with that phone.
The only thing you can try is to flash it with the official ROM from VZ and talk to them if it won't take.
I used the ROM from my service provider, but since the phone has screwed up, for some reason it won't flash it.
Also, I am currently at my friends house who has Windows XP, I leave tommorow for home. At home I have Windows Vista Ultimate, I am well aware that is it either impossible or very hard to flash on Vista. Is there a way around it with out installing XP?
Keep replieing please, I will be checking, just a busy 20 year old (almost 20).
Starhero said:
I used the ROM from my service provider, but since the phone has screwed up, for some reason it won't flash it.
Click to expand...
Click to collapse
Ah, I read your original post as the last ROM you tried was a WM5/6 ROM you found here.
Starhero said:
Also, I am currently at my friends house who has Windows XP, I leave tommorow for home. At home I have Windows Vista Ultimate, I am well aware that is it either impossible or very hard to flash on Vista. Is there a way around it with out installing XP?
Click to expand...
Click to collapse
Yes. It involves installing some USB drivers, older ones I think. You will have to search the forums for that, as I don't know what is involved as I know better than to run Vista.
Knowing which ROM you tried and rereading your original post, with the very limited experience I have with the Harrier, I would think that yes, the CDMA radio is 'pooched'.
You /might/ have some luck with a hard reset. It's worth a shot, but with those errors at the boot screen, I'm going to have to side with the person you talked with on the phone.
Beyond that, I'd search the forum for harrier and radio rom and see if you can find anything.
Serial v1.02 screen
I, too, lost the radio ROM recently. I got with same p DM FAIL" and "r DM FAIL" errors display on boot. Verizon replaced the pda with one of rom date 02/07/06 ver 2.07.00.
I tried to do the manditory update on the new XV6600 from the Verizon download website using my Vista workstation and ActiveSync (HA_VZW_207_117_01167_A12.exe).
The update failed and now the pda screen reads "Serial v1.02". In no longer connects to ActiveSync via the cradle, and it is totally unresponsive to the keyboard, buttons, hard reset, etc. What do I have, and what can I do with it?
Also, is it Vista that is blew up the upgrade? I had done this same upgrade on my original unit via XP.
Still haven't fixed it
and I haven't gotten another phone yet cuz I am a cheap a$$
As a despreate atempt can someone send me an ORINGINAL radio rom( the latest or maybe a step before)?
Idk exactly how to do such a thing but i figure my email is good
[email protected]
If someone has another idea PLEASE tell 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.