Hi Guys,
I have an I-Mate PDA2K with problems.
I'm new on this site and I'm in a bit of a pickle with the 2005 upgrade ROM...
The upgrade went fine and it was interesting to see what can be expected from the new OS but it still isn't user friendly enough for me just yet.
My problem is that I can't downgrade back to the original ROM, I have a copy of it which I have used several times but now when I try to reflash it it comes up with an error saying...
"ERROR 120: COUNTRY ID ERROR"
"The ROM image that you are trying to use is not designed to work with your device. Please check the vendor website and download the correct ROM update"
Then it lets me choose "Exit"
This as you can imagine is quite worrying as I have now lost most of the original functionality of the device.
If anyone knows how to remove it so that I can replace with the original OS I would be very grateful.
Thanks
Terry
PS - Please send any ideas to [email protected]
Thanks
You need to go into bootloader mode first. Check the Wiki.
Thanks Mastiff, you're a Star
No problem. But you can't lock/hide your extended ROM again, which I suppose you've already found out.
I'm a bit confused- it says on the wiki that if you downgrade to 2k3se from 2k5 after repartitioning DOC, then the ext rom will forever be visible. Why isn't this the case with mine? I followed all the instructions, copied my ext rom over after repartitioning a new ext rom and hard reset and it has disappeared again. Not complaining, just thought the doc repartioning tool reset the rom password.
Anyone else had this?
Im using XDA IIs, i've just rolled back to WM2K3SE and i couldnt see my O2 Connect applications and auto configurations tools ? where does it's go?
Hello
I have an XDAII1 PH10C
Ive had a few issues with TomTom etc and have downloaded an update or two - including the official O2 update.
Unfortunately me XDA keeps freezing and Im getting pretty upset with having paid £400 for nothing.
When I did the O2 upgrage I got the following :-
The file "rofs_target.zip" was not copied sucesfully. To re-install, you will need to get the source .cab file again. Continue with Setup?
Ive even let both batteries run down completely in the hope of restoring original O2 set-up - but I get a Country Error code when I re-install the upgrade.
My hardware settings are :
ROM 1.11.00 WWE
Date 01/27/05
Radio 1.04.00
Protocol 1337.42
ExtROM [this is blank]
Ive got the chance of returning to O2 support to try and sort problem, but I need original O2 set-up or they will charge me £96+vat for re-setting XDA.
PLEASE - does anyone have solution for solving [blank] ExtROM issue or the original O2 settings to solve the repair bill problem.
Thanks
Paul
what types of sd card are you using
sometimes i get that error as well but all i have to do is re run the no id app and it works 2nd time
I have a PQ1 1GB card, but dont have that inserted when I download updates or reset PDA.
Paul
re-run the O2 update if it errors with country ID error then just start it back up again it should then work.
It looks from the specs you posted your using the latest 1.04 radio. i assume you installed PUGs new update version ?
Hi
Yes I tried Pugs version, and the ExtROM was still blank.
So, Ive gone back to an O2 version - and the ExtROM is still blank.
I need to reassure myself that I have ONLY O2 software on the XDA before I send it in for repair as it will be free - if they find any other stuff on there they will charge me c£100.
Paul
PS Im still having major TT5 issues. Today it froze and I had to hard reset and then tried to re-install TT5. Only to be told it was already there and did I wish to overite. When I said yes, the today screen came up and theres no sign of TT5 anywhere.
Bloody XDAIIi is doing my head in.
Have you downloaded the latest O2 ROM from the XDA2i mini site?
When you are installing it have you got your anti-virus software turned off?
Yep - O2 download.
Yep - AntiVirus, Internet Security & Anti-Spam all Off.
Ive just done the download again and still got the rofs_target.zip message.
Paul
Hi there, have you tried unlocking the extended rom by any chance? This will cause the storage to be locked and cause the extended rom to stop installing past a certain point (Happened to me). There are instructions on this site on how to unlock it, do a search for unlock and my screen name (pug).
Hope this works.
Pug
I found the link you refer to and downloaded the exttools.200.exe and ran it on XDA.
I then tried the official O2 update again and the XDA has FROZEN !!!!
It is now stuck on Serial v1.01 and WILL NOT alter no matter what I do.
Ive soft-reset, hard-reset and done the soft-off-action button thing - and nothing.
When I place in cradle, the PC plays a tune as if to say it knows the XDA has been connected, but I cannot get activesync to recognise the XDA.
Now what can I do please ?
Im particularly worried that I now cant remove the exttools.200.exe from the XDA and will have to return it for repair with that dodgy software on there - they will definately be charging me for a repair now.
What can anyone suggest please ?????
Paul
There is a problem with my MDA: It continually flashes the volume/ringer control on the screen with the circle with the loudspeaker and mic turned off. This flashes every second or two and when it flashes, prevents pretty much anything else from working or command from executing.
I had a very old TMobile software version on it. I down loaded a much newer version from TMobile in an attempt to get rid of this problem before upgrading to XDA firmware: (The whole thing is very out of warranty)
The upgrade went successfully but the flashing volume / ringer control still flashes.
Does anyone know what this means or if upgrading to XDA will get rid of this problem (or exacerbate it!)
Has anyone noticed IF there is a problem with Puttenham's "Step 17"?
I got around my nerves about upgrading this G3 with a hardware problem in place and appear to be encountering a severe problem with Step 17 which is that it says it is "Your Choice" to go to a 3.08 SPL/IPL. Nowhere however does it say which later ROMs you can apply if you DO choose to go with the 3.08. I applied this to correct what I thought was the hardware issue (reinstalling the T-Mobile ROM at SPL 2.26 didn’t seem to cure it) and the 3.08 did install properly and cured the hardware problem.
I tried different ROMs because I cant seem to understand how to use VoIP or which ROM will let me use this 'feature' or which ROM has this feature built it as some say they have deliberately taken it out.
Suddenly I am getting error messages telling me that the unit needs a later ROM revision to install perfectly.
(WizardLove was the first to do this: It executes in Italian and as I mentioned, just tells me that it needs a later version to work)
So I reflashed with the Molski ROM which is the only one which seems to be around and the flash worked up until 94%. At that stage the progress bar turned to red and there was an error message telling me that I can recover and try again. I did this a few times and SEEM to have bricked my Wizard (When the Molski upgrade failed, attempts to chkdsk, reboot, delete all temp files etc failed). The unit will now only boot to the three-colour screen? Further attempts to flash seem to see and read the device and tell me either that there is no ROM on it and would I like to upgrade? Followed by this unexplained 'USE LATER ROM'. (There may be a problem with installing the T-Mobile ROM on an unlocked Wizard with a 3.08 IPL/SPL However it has to be said that Molski is, still, the only ROM which runs and it inevitably stops at the same position, the 94% mark when the MDA progress bar goes red, the unit shuts down, the upgrade process thinks about it for a while and ultimately reports ERROR [302] UPDATE ERROR)
Alternatively they (for example ROM Update Utility 2.00.1) tell me that there is no communication between the PC and the Wizard. Actually ActiveSync 4.5 does show no connection between the device and the PC, which I suppose I would expect if the Molski ROM failed to complete? Device Manager seems OK with the unit being in place though? And I cant believe this is important as there obviously IS connection between the computer and the PDA
Easymob said he would let users have a path to a ROM they could use but no where is it set out which ROMs you can use of the ones you actually CAN find?
I have also tried the Xelencin ROM which initially tells me that it cant see the PDA. Then it admits that it can and tries to unlock the CID (which surely must be already unlocked by now if I have upgraded to the later SPL??)
I am not sure I have a totally bricked unit, - The Xelencin T-Mobile ROM MUST be doing something because it does successfully run the RAPI unlock and after a few error messages telling me it can't access the MDA, reports DONE! But then it tries to run Machinagod's HTC Wizard Unlocker and gets stuck. It shouldnt get stuck at this step as I must already BE unlocked! It should pass this step.
I can hear hdd movement (not churning) but the program doesn’t progress past this step. Ultimately this carries on for hours and the Wizard shuts down I presume when the battery fails as the charge function doesn’t seem to work in ROM upgrade three colour screen mode. Plugging the charger in now doesnt seem to do anything
Again as the program was built for the 2.26 SPL, I still cant figure out whether these available ROMs should run on the 3.08 which I followed in the STEP 17.
MEANWHILE BACK AT THE RANCH: Is there a more obvious answer to why Molski always fails at precisely the same 94% position?
Hey everyone. I'm tearing my hair out trying to get this sorted but I just don't know what to do!
So, when I got my X1 as everyone on here should do, was flash my X1 with the HardSPL and some custom roms, this was a few months back. Then, shock! Horror! My case went and broke, (cracked near the volume button build W44) so I sent it back to SE for repair. I sent it back reset back to defaults but left the hardspl on there.
SE sent me a brand new phone (I think... This one says under the battery build w50, but the battery says w32..) I received it today. I thought it would be my old one repaired but SE had other ideas. Booted up and have Image Version: 1.03.931.10 and HardSPL 72.000 I think I said that correctly...
Now since sending it for repair and receiving it back, their seems to be quite a few wm6.5 roms floating about, and obviously I can't use the stock software as that wouldn't be right!
Now I have tried flashing the hardspl to the phone through my Vista PC and all it keeps giving me is connection errors. I thought maybe it was already flashed so I tried flashing just a rom, and that just made the phone get stuck on loading (flash by memory card). I thought it might be Vista, so I tried doing it on my other PC (XP) and I get the same issue. This bloody thing won't flash!
I have had "Connection Problems" - "Update Errors" with different numbers. The current one being Error [260] CONNECTION.
Now I have been searching around through the hardspl thread and other places trying to find out what I need to do or how I can fix it, but everything I try doesn't make a difference. I did read some other people with recently repaired phones having the same problem and perhaps SE have put a new spl thingy-ma-jiggy on there. (Please forgive the technical jargon, I have no idea what im on about.) I have also tried the ticking/unticking advanced network functionality, but that hasn't made a difference either.
So by the end of typing this, I have little hair left. Let's hope you can all help, before I have none left!
I would appreciate ANY help! Really.
Just wanted to add, I was at first getting the phone to a loading bar when flashing, but it would stay at 0% then flag up an error on the PC. Now after the tri-colour bars, the phone just sticks on Loading...
Well just to update. I have been trying to sort this since posting. I flashed the rom to an old UK generic one, as I read in another topic people had to do that before HardSPL. Done that, and tried flashing the hardspl. Same thing, just getting connection errors.
I tried going into bootloader and running the hardspl from there. It works and the phone gets to 10% and then gives an UPDATE ERROR. The phone is now bricked, and I have to reflash the original wm rom to get it back.
Though the Tricolour screen now shows 0.52.Olinex
Any ideas?
Shameless bump for help.
very stupid situation.
i have the same situation in puncto of flashing.
i get my phone three month ago.
after hardspl i .... sorry, no hardspl ... the phone says at 0% bla bla bla
i solve the problem by consulting one night absolutly stressing again and again and again .... google ... xda ... google
than 3 thinks at one time was the solution:
0. need activesync - connect !!!!
1. SDA_ApplicationUnlock.exe for desktop pc
2. enterbootloader.exe for pocketpc (please, the right version, it exist for eten too, but we need the xpediaversion ..)
3. changing registry-entries
how to:
activesync-connect, than copy "enterbootloader.exe" to pocketpc. it must be root, not sd-card. use a pocketpc-registry-program to change these values :
HKEY_LOCAL_MACHINE\Security\Policies\Policies\00001001 = 1
HKEY_LOCAL_MACHINE\Security\Policies\Policies\00001005 = 40
HKEY_LOCAL_MACHINE\Security\Policies\Policies\00001017 = 144
HKEY_LOCAL_MACHINE \Security\Policies\Policies\0000101b = 1
if not exist than add the key.
now, start desktop-program, follow instruction EXCEPT reboot.
start "enterbootloader.exe" on pocketpc. now, you can install hardspl and the device is flashable for ever.
thats works on me, hope it could help you too.
Thanks for the reply. Not had time to try it till this morning. Ok so, after spending about an hour trying to find the correct enterbootloader.exe I finally realized, that the hardspl package includes it. *Duh!* So that was time wasted.
I changes the registry values as you said with Resco registry editor, and follower the unlock then enterbootloader.exe Start HardSPL package. Starts to install. Gets to 10% then I get
ERROR [262] : UPDATE ERROR
The rom update utility has encountered communication errors during the update process.
So im open to suggestions if anyone has any. I just can't understand why it's not working. It's not a problem with my computer or cables. I flashed the phone before I sent it for repair and I have tried doing it on two computers one with XP 32bit and one with Vista 64bit.
hmm. would u like to install a custom rom, or a stock rom?
msg me, and i hope, i can halp u.
I want to have the hardspl on there so I can flash custom roms.
If it's a case of the software/firmware/hardspl whatever you call it, has been updated by SE. How would one go about getting it flashed? Would we have to wait for an update HardSPL to be released?
U read this thread?
My first hardspl was from this thread. New X1 will come tomorrow back from SE (vibration was defect +++ some more problems with case), and i will try it again with this thread.
hope, this will help u mate.
Yeah, I have been through that thread with a fine toothcombe trying everything suggested to see if I can make it work.
When you get yours back, if you have to do anything out of the ordinary to get it to flash or can't do it. Please come and let me know in this thread. If they have updated yours like mine, and yours won't flash, at least I won't be the only one!
k, i will msg u tomorrow around 2pm.
Cheers.
In the meantime. Does anyone have any other suggestions I could try?
Bump, for some help.
now i know, what is exatcly your problem.... <--- SAME Problem
i hope, i will find a solution and msg u then. if u´ll got a solution for this prob, msg me too plz.
Solution found in this Thread!
Download this and unzip it to your device. ++ run it. It will start your X1 in Bootloader menu and say "0.52.OliNex".
Then start hardspl while X1 is in Bootloadermenu....
FINISH =)
Thanks for the reply matey. Glad you got yours sorted. Just tried what you said and I get 0% then it switches to ERROR [262] : UPDATE ERROR.
vwrmic said:
Thanks for the reply matey. Glad you got yours sorted. Just tried what you said and I get 0% then it switches to ERROR [262] : UPDATE ERROR.
Click to expand...
Click to collapse
hmmm... it works fine on my new x1. are u sure, that u start the ssplmanual on your x1 and not on your computer?
Yea, im not sure what the problem was with it. Thankfully I have it done and dusted today! Because I flashed it earlier to an older official version, and you said you got it working. I presumed you had - had yours flashed to the newest version due to it being off for repair. So I reflashed the official update and fully updated it. Then tried hardspl which didn't work. Tried with the advanced USB thing off, tried again with how you said you did it above, and Viola!
Hip hip hoorah! Thanks for the help. Can finally use me bleedin phone now!
no problem mate hf with your x1
hello,
i see smilies and yea's ...
for me to understanding (for next time or other users):
1. complete official update (if exists)
2. flashing (hardspl) without "advanced usb"
thats all?
cool.
Hi to everyone.
I've just bought a HTC Diamond on the vodafone network, but need to unlock it as I'm on O2's network.
I've been able to install SPL 1.4 and this shows on the boot loader page.
The problem seems to come when I try and install the 'new' rom. It goes through the whole stage up to 100%. Then on the device it says error code please try again. On my Pc it says error code 226. I've tried it on a windows vista pc, and again on XP. I've also tried it by installing it direct onto the internal storage. This again goes through the installation up to and including 1005, but then come sup with a new screen on the device saying that the update and the radio have both failed to install.
I'd really like to unlock my device and to have a new rom so that I dont have all the vodafone branding.
Like many others, I'm willing to contribute so that research and new software is developed, and I have also read the forums for many hours trying to find a solution to my problem before posting.
Hopefully I can be directed to some help.
Kind regards.
Just to update and incase anyones interested.
I ended up downloading the latest version of the official rom that I could find, then extracted the nbh file using winrar, and installed that from the internal storage which has successfully worked.
Not sure why the other rom image I had wouldn't work, just glad I've got rid of the vodafone bits really.
Regards.