Database Users

Flashing ROMs is dangerous !!!

There's two type of ROM upgrades: Operating System ROM upgrades and Radio Stack Upgrades.
Radio Stack Upgrades:
Radio Stack upgrades are distributed by the devices resellers. They come in packages with names that may or may not include "Programme B" or "RSU", and they are usually about 2 MB in size. Version numbers are a mess, and lower version numbers do not mean earlier versions. There's at least three different paths of version numbering out there, and the version number on the file doesn't always match the version number displayed at boot and by 'Device Information'.
The official Radio Stack Upgrade process is a mess. We've seen way too many people wreck their devices doing nothing weird or strange. Our advice regarding Radio Stack upgrades is to get them from your own device provider (so you know it's for you type of device: 900/1800 or 900/1900 MHz), and to only upgrade if you know the upgrade will fix known issues that are bothering you.
Operating System Upgrades:
Operating System upgrades are distributed by the resellers in packages whose names may contain "Programme A" or "RUU" (to confuse things, RUU stands for "Radio Unit Upgrade", even though they do not upgrade the Radio part but the PDA part). Operating System upgrades are usually 15 MB in size, and unless you use our utility 'adaptROM', they will only install on phones sold by specific resellers in specific markets.
In this community, the OS is sometimes also distributed as .nb1 file, for use with our XDArit tool. These files are often zipped to about 15 MB, uncompressed they are 32MB (well: 32 MB minus 256 kB actually).
We've seen a number of people doing terrible things to their devices by upgrading their OS ROMs. Here's what we've seen:
- It appears someone is distributing an EXE file for the PPC2003 ROM that contains a part of the OS in the spot where the bootloader needs to be. People that use this EXE to upgrade to 2003 may experience problems immediately or later on, possible making their device unusable.
- We've observed our XDArit tool in the hands of people that should not be using it. If you don't know what a DOS box is, or think you can rename .nb1 files to .nb0, or if you generally do not feel technically proficient, do not use XDArit. It's as simple as that.
(We also blame ourselves for this: XDArit is very counter-intuitive in some parts, and is long-due for an overhaul....)
- Apart from the above, there seem to be problems for people getting back from PPC2003 to earlier versions of the OS. We've been busy doing other things, and we haven't really researched this yet.
- It seems the exe files Jeff makes are OK, and if they aren't, people would know pretty quickly. We advise against running exe-files from others until we've found what causes this 'bootloader mangling' we've observed.

Thanks for your warnings. I just checked my device information. It reads rom version 3;14.06 ENG, Rom date 10/01/02, Radio Version T313. Being not technical at all. Your advice is not to upgrade the Rom or de radio version.
But that leaves me with some problems. F.i. when I try to synchronize with Outlook on my pc. I keep losing mails. The only mails being synchronized at all are those from my inbox. A series of attachments cannot be converted and there is no way to know which mails they are in. I was also hoping that a rom-update would solve my constant memory-lack.
Are there any other solutions?

Upgrade Fails
We have been upgrading some ATEK's with success, but we have two that don't want to upgrade. The message is:
"Can not open COM/USB port...." \\Can someine help...

Re: Upgrade Fails
scalci said:
We have been upgrading some ATEK's with success, but we have two that don't want to upgrade. The message is:
"Can not open COM/USB port...." \\Can someine help...
Click to expand...
Click to collapse
:wink: it's same problem that i have but the slution is download the XDA-dev's XDAtools.exe and cook your ROM then save it on your SD-card
for me it's work 100% my Qtek provieder in Saudi Arbia said that you can't downgread ROM after you do upgread but what ?? it's work
:lol:
[email protected]

Upgrade radio fail
Thanks for the advice. Unfortunately I read it a bit too late.
I download ROM from O2 site, program A (3.20.06ENG) and program B(4.21). Upgarded my xda with program A, after reset it works. When upgrade the radio program B it hang for half hour. After reset the xda does not boot!
Is there a way i can flash back the ROM so that i can use back my xda?
Original version ROM 3.17.03ENG and radio 3.14.
Thanks in advance.

After upgrad radio from 4.16 to 4.21, My O2 does not reset or hardreset normally. After a long process, I get a blank screen with only input icon on the lowwer right corner. How to fix it now?

problem solved.

inaccess said:
problem solved.
Click to expand...
Click to collapse
How have you done it ?

Re: Upgrade radio fail
pcloo said:
Thanks for the advice. Unfortunately I read it a bit too late.
I download ROM from O2 site, program A (3.20.06ENG) and program B(4.21). Upgarded my xda with program A, after reset it works. When upgrade the radio program B it hang for half hour. After reset the xda does not boot!
Is there a way i can flash back the ROM so that i can use back my xda?
Original version ROM 3.17.03ENG and radio 3.14.
Thanks in advance.
Click to expand...
Click to collapse
I did the exact same thing and had the same problem. anything I could do to had my xda up and running again?
thanx in advance

Re: Upgrade radio fail
darkdragoon said:
pcloo said:
Thanks for the advice. Unfortunately I read it a bit too late.
I download ROM from O2 site, program A (3.20.06ENG) and program B(4.21). Upgarded my xda with program A, after reset it works. When upgrade the radio program B it hang for half hour. After reset the xda does not boot!
Is there a way i can flash back the ROM so that i can use back my xda?
Original version ROM 3.17.03ENG and radio 3.14.
Thanks in advance.
Click to expand...
Click to collapse
I did the exact same thing and had the same problem. anything I could do to had my xda up and running again?
thanx in advance
Click to expand...
Click to collapse
If you push the power buttom and than do a hard/cold reset do you get a bootloader ???
If so you need a storage card and put a good rom on it.
Read more on this forum

Re: Upgrade radio fail
I got a problem yesterday night, while trying to updgrade the ROM with the XDA developers Special Edition ROM v1.2, I got the message from the tool saying it will take up to 5 min and a scroll bar appeared on the XDA and not removing it from its base.
But I accidently removed it (in fact, I caught my foot on the damn wire and everything went to the floor).
Now nothing works, except the diagnostic bootloader when I reset and press on button. Hard reset changes noting.
The screen when I hard-reset it shows the scrollbar that was displayed when I tried to upgrade it.
ActiveSync does not recognize it anymore (PC beeps when the XDA is put in craddle, but it does go further).
Any idea how to put back original ROM content ? I have backup of the content made with Active Sync.
I own a SX-56 and subscribe to Rogers AT&T; I guess my config is identical to a AT&T phone, as it's written on top
Any suggestion will be welcomed
Bernard

Re: Upgrade radio fail
droletbe said:
I got a problem yesterday night, while trying to updgrade the ROM with the XDA developers Special Edition ROM v1.2, I got the message from the tool saying it will take up to 5 min and a scroll bar appeared on the XDA and not removing it from its base.
But I accidently removed it (in fact, I caught my foot on the damn wire and everything went to the floor).
Now nothing works, except the diagnostic bootloader when I reset and press on button. Hard reset changes noting.
The screen when I hard-reset it shows the scrollbar that was displayed when I tried to upgrade it.
ActiveSync does not recognize it anymore (PC beeps when the XDA is put in craddle, but it does go further).
Any idea how to put back original ROM content ? I have backup of the content made with Active Sync.
I own a SX-56 and subscribe to Rogers AT&T; I guess my config is identical to a AT&T phone, as it's written on top
Any suggestion will be welcomed
Bernard
Click to expand...
Click to collapse
You need a storage card (32 MB or more SD or MMC will do) and a reader/writer for it,
than write a rom on the card, put it in your devices an start the boot loader, than if everthing went good it will ask you if you wanted to update the rom.

Re: Upgrade radio fail
Weezer-DC said:
darkdragoon said:
pcloo said:
Thanks for the advice. Unfortunately I read it a bit too late.
I download ROM from O2 site, program A (3.20.06ENG) and program B(4.21). Upgarded my xda with program A, after reset it works. When upgrade the radio program B it hang for half hour. After reset the xda does not boot!
Is there a way i can flash back the ROM so that i can use back my xda?
Original version ROM 3.17.03ENG and radio 3.14.
Thanks in advance.
Click to expand...
Click to collapse
I did the exact same thing and had the same problem. anything I could do to had my xda up and running again?
thanx in advance
Click to expand...
Click to collapse
If you push the power buttom and than do a hard/cold reset do you get a bootloader ???
If so you need a storage card and put a good rom on it.
Read more on this forum
Click to expand...
Click to collapse
Yes, I got the Wallaby bootloader and it said GSM failed.
Pls show me where about I could get more info on the forum.
ThanX in advance.

Re: Upgrade radio fail
Weezer-DC said:
droletbe said:
...
Now nothing works, except the diagnostic bootloader when I reset and press on button. Hard reset changes noting.
...
Any idea how to put back original ROM content ? I have backup of the content made with Active Sync.
...
Any suggestion will be welcomed
Click to expand...
Click to collapse
You need a storage card (32 MB or more SD or MMC will do) and a reader/writer for it,
than write a rom on the card, put it in your devices an start the boot loader, than if everthing went good it will ask you if you wanted to update the rom.
Click to expand...
Click to collapse
Any place/URL to look for such thing as the ROM and the writer ? How much should I expect ?
Thanks for your help

Re: Upgrade radio fail
droletbe said:
Weezer-DC said:
droletbe said:
...
Now nothing works, except the diagnostic bootloader when I reset and press on button. Hard reset changes noting.
...
Any idea how to put back original ROM content ? I have backup of the content made with Active Sync.
...
Any suggestion will be welcomed
Click to expand...
Click to collapse
You need a storage card (32 MB or more SD or MMC will do) and a reader/writer for it,
than write a rom on the card, put it in your devices an start the boot loader, than if everthing went good it will ask you if you wanted to update the rom.
Click to expand...
Click to collapse
Any place/URL to look for such thing as the ROM and the writer ? How much should I expect ?
Thanks for your help
Click to expand...
Click to collapse
Now everything works ! And this accident "forced" me to buy an SD, so I will not be so limited by the 32Mb limit
Thank you very much

help needed....
i hard reseted my qtek 1010 .... its like 30mins ....and am still gettin 4 bands white red greem blue... is that normal ...that hard reset take this much time... if this si not normal ... what should i do next

Bootloader not recognising sd card image
I am having the same problem. When pressing power and reset, bootloader shows v 5.17 GSM fail.
I have an sd card which has a new bootloader and nb1 file on it. I do a reset with the card in the slot and i get the same screen v517 GSM fail. From what i have read i should be getting an option to upload the new rom.
Can some one help me out please?
If I currently turn the device on normally activesync does not recognise the device.....
The sd card I have was configured using the xdirt programme and it appears to have worked as the sd card is shows not formatted now...

Thanks for all the info and warnings, just got my XDA II today and Im not too hot with it yet so I guess I will be leaving the ROM's alone for the time being

Peter Poelman said:
Radio Stack Upgrades:
Click to expand...
Click to collapse
We have several system where the GSM rom is toast. Is there a way to get a GSM Rom to SD w/o using the PC Monitor program?
The systems will successfully bootup and we have tried loading the GSM rom using RSUpgrade, but it fails after 1%.
Is there any other way to recover the GSM Rom?

You may try speaking to Cgigate on this forum, he has hardware methods of programming the chips directly, whether it works for the radio stack as well as the bootloader and rom you will need to ask him.

error getting device data after T-Mobile (4.00.10) update

Hi developers,
first of all I'd like thank you for your excellent work. I used a couple of roms and really appreciate your efforts.
This time I updated my device from WM 2003 (4.00.01 ENG, Radio 4.21.00) to the T-Mobile release whitout radio update, posted in this forum by Aurora13. After a backup of my data and removement of the T-Mob. stuff like suggested by Aurora13, I noticed that my backlight was turned of and I couldn't turn it on again either.
So I tried to downgrade again, because working without backlight really is a pain, by I'm unable to.
Not depending on which ROM I use, I get the message: "error getting device data" (CMD.exe) & "execute remote communication program error" (prog. a 1.09).
My active sync (WinXP) seems to work.
The device & telefone seems to work either.
How can I fix this?? Any suggestions?? I'd really like to go back to 4.00.01!!!!
Thanks in advance!!!

If you restored your applications from a former version of WME 2003 you will see this happen. I don't know what registry setting or file is getting changed but after a restore from say 4.00.01 or 4.00.05 backups (I use SPrite Backup) you will see this phenomenum occur after a soft reboot no backlight. Do a hard reset and resinstall your applications and all will work fine.

error in CMD.exe window after T-Mob 4.00.10 update
Hi developers,
I have similar problem, I’d like to go back to 4.00.005 too.
Using the ROMkitchen_4.00.05.exe, in the CMD.exe window I got an error message:
“error: GetConnectionType – An existing connection was forcibly closed by the remote host.
error getting connection”
My activesync seems to be working properly.
What has gone wrong? How do I fix it?
Thanks in advance

Experienced the same with the backlight.
So NEVER do a restore from a different ROM!!! Alway do a clean install.

error in CMD.exe window after T-Mob 4.00.10 update
Do a hard reset and resinstall your applications and all will work fine.
Click to expand...
Click to collapse
Always do a clean install.
Click to expand...
Click to collapse
So in plain words: how do I do that when this occurs during the flashing-procedure :
“error: GetConnectionType – An existing connection was forcibly closed by the remote host.
error getting connection”
Click to expand...
Click to collapse
It's not only the backlight, the problem is the "execute remote communication program error" which makes flashing the ROM impossible .
I used do update with *.exe-files which won't work out anymore :evil: . Can anybody post a step by step guide how to fix it and go back to the ROM before :? (Which would obviously be the best)?
Or does anybody know which registry key has to be changed to fix the backlight :idea: ?
Thanx!!!

Does it work OK after a hard reset?
Because you shouldn't have to go back, do a hard reset and do a clean install of your apps and 4.00.10 should work ok.

Thanx Aurora13,
it now seems to work !
I'm on 4.00.10 again with all the T-Mob. stuff and backlight working.
In my case, going back to 4.00.01 and restoring my backup seems to be less time consuming than doing a clean install (would loose adress book & calendar).
I actually can't spot a lot of differences besides the version numbers in the OS anyway :? .
:evil: But trying to do that, I still have the same problem with the cmd.exe:
“error: GetConnectionType – An existing connection was forcibly closed by the remote host.
error getting devicedata (cmd.exe)”
Click to expand...
Click to collapse
and
"execute remote communication program error" (prog. a 1.09).
Click to expand...
Click to collapse
:evil:
Seems to me like a serious bug that I can't flash my ROM with the USB-cradle anymore :x .
Anybody any suggestions how to get rid of this OS-version without SD-card-writer?? I'd really like to have evrything working again like it was before!
Thanks a lot in advance!!!

Most importantly: do not upgrade to a T-Mobile ROM 900/1900 MHz (American) ROM on anything but a 900/1900 MHz phone. The T-Mobile ROMS contain the RSU phone upgrade, which will run as soon as WinCE boots. You will ruin your 900/1800 (European/Asian) phone if you do.
Click to expand...
Click to collapse
Could that be the problem that I'm unable to fllash my ROM again?
You will ruin your 900/1800 (European/Asian) phone if you do.
Click to expand...
Click to collapse
What does that mean?

"What does that mean?"
i suspect it means that your xda will only work in US
untill you find some way to flash it back to the 900/1800 gsm mode
which is used in EU and much of the rest of the world [/quote]

untill you find some way to flash it back to the 900/1800 gsm mode which is used in EU and much of the rest of the world
Click to expand...
Click to collapse
Anybody know how to do that when unable to flash ROM due to
Quote:
“error: GetConnectionType – An existing connection was forcibly closed by the remote host.
error getting devicedata (cmd.exe)”
and
Quote:
"execute remote communication program error" (prog. a 1.09).
Click to expand...
Click to collapse
Only via XDArit?????????

if it can be flashed using the sd flash card and you have an sd flash card reader / writer for the pc it would be possible

Similar discussion going on here:
http://www.xda-developers.com/forum/viewtopic.php?t=2134
T-Mobile update 4.00.10 sucks!!!

@reiggue
4.00.10 does not suck.
The problems you are experiencing are not real problems but a lack of knowledge on your side.
If you asked how to solve them I can help you to solve EACH one. But you are not asking, but only being negative.
As with all ROMs if you don't know what you are doing, then don't do it.
If you read this forum more securely, you already got answers of a few of your problems:
- How to go back to an old ROM
- Removing the TMobile stuff
- Backup of previous version does not work
All the answers of the above and how to solve them you can find in this forum.
So use the knowledge of the people of this forum and don't be so negative.

I want to second Aurrora13's statement. Over and over in this forum it is stated that you should not attempt these ROM updates if you don't have an SD reader. Sometimes it is the only way to save your bacon (XDA)! If a user insists on ignoring sound advice, then he shouldn't complain about suffering the consequences.
In general, the more experienced users on this forum provide good advise and are more than willing to ehlp others. Personally, I think this forum is awsome!
We all know we are taking risks but being techno-junkies we jump in there trying to improve our XDA's and learn more about its capabilities and ways to improve it. I hope when the next majore WME phone becomes available (I'm hoping for the TI WANDA, though XDA II will probably be first) that we are able to do the same with it.

4.00.10 user wanted to revert back to old rom
You need to use SD card reader to revert back to older rom, Activesync doesn't work properly in windows, even you had sync with your windows.
I had the same problem before, but I found out this 4.00.10rom is more stable then others WM2003roms.
Please follow Aurora13 instruction,removing a few item under program/AIM -/Tmobile and if you have radio signal problem You might want to try to bootloader setting 900/1800 or 900/1900, it works for me.
This is my second time flashing v4.00.10 and I'm using XDA asian unit.
Good Luck.
:lol:

@Aurora13
You might be right in me being negative.
As I read through the forum, there are other people experiencing the same problems.
I think that people should be warned to use the 4.00.10 version instead of hyping it, because, you might agree on that, you loose the ability to go back to an old ROM via activesync, which is the most convenient procedure so far.
I didn't know that I lose this ability, especiallly after performing 4 successfull ROM-updates so far with ROM from this site. That in fact frustrated me.
I agree that the information provided in this forum should help restoring the old ROM.
To close this message, I'd like to thank everybody in this forum who contributes to help fools like me, obviously not knowing what they're doing! This forum is great and I don't want anybody to get the impression I'm blaming anybody else for my faults.
Thanx!

imho then buying a SD reader is a pretty good idea no matter what
they come in versions which read 6 or 7 different flash types so one can also read ones digi cams card if it's a different type
and they are only about 50$ or EUro or something like that
i'm sure getting 2->3 flash readers one of these days

@reiggue
Yep this forum rules big time.
If you check the Sticky thread:
http://xda-developers.com/forum/viewtopic.php?t=1624
There is already enough warnings for the 'beginner', that's why I didn't warn it can be dangerous.
But enough said, good luck with your downgrade and/or if you will stay with the 4.00.10 ROM I'll be glad to help solving some problems you may experience or talk you through the downgrade.

I appreciate your assistance, Aurora13!
Thanx! :lol:

For those of you in the UK - I bought an SD card reader (only reads SD and MMC cards) from PC World for only £6.99 - I've used it to change ROMS back and fourth several times on four XDA's without incident so far - I bought it after an activesync update (genuine O2 upgrade) went horribly wrong and trashed my XDA. I think that everyone "playing" with these ROMs should get one.

Any other way to flash radio than SD card method?

Hi everyone,
Thanks for all of the good work happening her in these forums. It’s really amazing how much information is here. I have the following situation and wonder if anyone can help me sort it out.
I have a running qtek with an un-working radio. I have the developers SE ROM 1.2 installed and it’s running but very slow. The system can’t detect the battery and its charge. The radio is off and will not turn on. I tried to install the O2 4.21 radio update using the SD card using the repair file downloaded from your site but no luck. It stops after it reboots and start the upgrade process with the dreadful 1% can’t flash error. From what I read so far the problem hover around the radio not being able to detect the battery power so it stops the flashing process. I tried changing the upgrade file and to do it many times but still always stops at 1%.
One way I didn’t try is copying the upgrade file to the windows root directory and tries to upgrade from there instead from the card. I don’t know where to find the 2 monitors files needed to be installed there before the upgrade. Anyone knows where to get them from?
Is there any other way to flash the radio using the SD card method (I am traveling and don’t have the cradle with me.)
Thanks again.

Have you tried fixing it with the following?
http://xda-developers.com/repair.zip
Hope it helps.

I have exactly the same problem as ahmedateeq. Runnung the repair.zip files as suggested by beeheij just results in Radio Stack Upgrade failure at 1% every time the XDA soft resets (the only way to break this loop is a hard reset). I have tried two different RSU upgrade versions, but to no avail.
What else can be done?
Geoff :?

gwhitea said:
I have exactly the same problem as ahmedateeq. Runnung the repair.zip files as suggested by beeheij just results in Radio Stack Upgrade failure at 1% every time the XDA soft resets (the only way to break this loop is a hard reset). I have tried two different RSU upgrade versions, but to no avail.
What else can be done?
Geoff :?
Click to expand...
Click to collapse
Did you try to turn on your GSM using the bootloader, by Holding power button then Soft reset the unit, then if you see the logo "Bootloader 5.15" press the calendar button, then you will see the GSM menu, try to select GSM ON then press the action button( the middle of navigation key), when it go back to the menu then soft reset again, then check if it is working or not..Please telme the version of your unit RSU and RUU... thank i hope this will help you.
:?

Did what you said - I was able to turn on GSM in Bootloader (though there was no message to confirm) - but this hasn't improved the situation. I still get the upgrade failure at 1%.
My RUU is SER1.2 (based on O2 3.17.03. RSU is (WAS!) O2 4.21
Any more ideas? Is it worth trying to copy the upgrade files to the Windows folder on teh XDA and running it from there?
Thanks for your help.
Geoff

I tried switching the radio on as suggested, but it failes.
Can we try the windows root directory install method. I need to know where to get the 2 monitors files to be installed with the rsupgrade file. Any one know where to get them.
Any other suggestions (Gurus help needed here)
RUU is SER1.2, O2 3.17.03, RSU O2 4.21

ahmedateeq said:
I tried switching the radio on as suggested, but it failes.
Can we try the windows root directory install method. I need to know where to get the 2 monitors files to be installed with the rsupgrade file. Any one know where to get them.
Click to expand...
Click to collapse
Ok here you go!
http://www.o2.co.uk/personal/xda/docs/Radio_Stack_Upgrade_v421.zip

Thanks Qman,
I have this file already and its installed, but I dont see the 2 monitor files in the programme b directory. Are they included in the rsupgrade cap file and if yes which one is which?
Thanks again and still waiting for some creative thinking how to solve this delmma that hit so many members.

ahmedateeq said:
Thanks Qman,
I have this file already and its installed, but I dont see the 2 monitor files in the programme b directory. Are they included in the rsupgrade cap file and if yes which one is which?
Thanks again and still waiting for some creative thinking how to solve this delmma that hit so many members.
Click to expand...
Click to collapse
Yeap they're included in the RSUpgrade.sa.CAB!
What I would do is copy the RSUpgrade.sa.CAB to my device and run it from there and if the upgrade fails do a search for the needed files and relocate them manually.
HTH

Magician and Blue Angel GPRS “Cannot Connect” Fix

After watching for months the issues that many have suffered over this problem, I finally found a solution that will fix all the woes.
A few months ago I was one of the many here that upgraded to 1.11 ROM, had the problem. It drove me crazy to the point that I went back to the 1.06 ROM that was rock solid. Well the other day I did a hard reset to have a clean slate. While looking at the Extended ROM I saw the file DefaultV_1.12 in the EXT Rom (Compared 1.11 ROM on FTP to my device). This was the same file that a XDA developer member had modified to somewhat solve the GPRS problem a few months ago.
At this point I had a hypothesis, so I pulled the same file from the older 1.06 ROM which was rock solid and did not have the “Cannot Connect” problem. In this EXT ROM it is named Default_Version_WWE_106150.sa.CAB.
Installed it first on my Blue Angel as a guinea pig, then for the next three hours I would sit there and disconnect and reconnect. I did it manually by holding the red button to disconnect, then I would reconnect to another webpage, then would have a call come in while in the middle of the GPRS session which would suspend it. After done with the phone call I would reconnect manually by clicking connect as well as by just hitting a link on the webpage.
The Results: No “Cannot Connect” problem.
So off I went to my Magician:
Upgraded to 1.11(I have 850 JAM)
Installed Default_Version_WWE_106150.sa.CAB
Put the phone through its paces, I have been disconnecting and reconnecting without a single problem. I receive phone calls that suspend the GPRS session and I am able to reconnect without a problem. Activesync is able to make OTA connections without a hitch.
During my trials I used the same programs:
Which included:
Photo Contacts(newest version)
Activesync
WEBIS Mail 2
xVbar
PocketZenPhone
Regking 2003
As the only variable throughout the trials was Default_Version_WWE_106150.sa.CAB
This is the solution folks.
At least until someone says it does not work.
Installation Steps:
1. Download CAB that I have attached.
2. Copy over to device
3. Install
4. Soft Reset.

1st of all let me say this is a great site for the HTC devices, I found it years ago when i had the first XDA (Wallaby i think) and now i own a O2 Mini.
I have just installed your patch and i'll let you know how it goes.

I wonder if this patch does the same as the "downgrading" of the caller id as detailed in this thread: http://forum.xda-developers.com/viewtopic.php?t=20428
The downgrade has been succesful for blue angel users too.

randomshots said:
Installation Steps:
1. Download CAB that I have attached.
2. Copy over to device
3. Install
4. Soft Reset.
Click to expand...
Click to collapse
Many thanks for posting this information.
For a relative newbie like me who has never manually fiddled with ROM files, can you please explain what I actually have to do to "install" the CAB file, i.e. in which directory on the device do I put it, and how do I run it?
- Peter

Once copied over to the device just place it where you can find it using the file explorer. Once located using the file explore simply click on it and it will install on its own. Do a soft reset and enjoy.
Crisscross: The Photo Contact solution that people have found only alleviates the problem a little, not entirely.
In my trials it has solved my problems completly. I wish for other members who try it out to report back as well to see whether all my trials were just a fluke, or our solution.

don't work for me
don't work for me. same problem as before, can't connect due unknown reason.
thanks anyway.

Orcas what is your ROM?

randomshots said:
Crisscross: The Photo Contact solution that people have found only alleviates the problem a little, not entirely.
In my trials it has solved my problems completly. I wish for other members who try it out to report back as well to see whether all my trials were just a fluke, or our solution.
Click to expand...
Click to collapse
The downgrade of caller-id to an earlier version has also solved the problem totally for me and several other people, both blue-angel and magician users. Thats why I was curious just what your patch did. Seems that it is something similar, you are maybe downgrading more of the rom?
Did you try downgrading of the caller-id first? Not just photo contacts but downgrade to the specified earlier build of caller-id?

randomshots said:
Once copied over to the device just place it where you can find it using the file explorer. Once located using the file explore simply click on it and it will install on its own. Do a soft reset and enjoy.
Click to expand...
Click to collapse
Hi there,
Just thought I'd report that I've just installed it. My ExtROM now reports as 1.06.150 WWE.
And... so far, so good!!! I've connected/disconnected to GPRS multiple times, interrupted GPRS with a phone call and then reconnected, have sent files to my device via BT while GPRS is on, and still no problem. It's looking very good!!!
And I'd swear it connects faster than it did previously.
Anyway, I'll keep hammering at it over the weekend and report back on Monday.
Thanks again randomshots!

Well, I'm back already, because I still have the problem. DARN IT!!!!!! :x
The thing that made it happen was that I made a phone call while GPRS was on. When I ended the call and tried to reconnect to GPRS, I got the blasted error. So it seems that receiving a phone call does not cause the error to happen, but making a call does. At least for me.
Oh well, it was worth a try. Back to the drawing board.

Same problem in Hong Kong
I upgraded to ROM v1.11 a few days ago and since then I have the GPRS connection error after 1 or 2 connections. Soft reset will solve the problem. This problem was not encountered at all before the ROM upgrade. It must be the new ROM that mess things up!

As this "default cab" from an old rom seems to solve the problem and also an older version of caller-id solves it there is probably something wrong in the communication between caller-id and some of the customisations from this cab on newer roms. Btw the problem is also in 1.12 roms.
Nice too see that we have two possible solutions here, I will stick to the downgrade of caller-id as it has solved the problem totally for me but it would be interesting to know what the real cause is...

Hi again. Just to answer the previous question to my post: my rom version is 1.12.00 WWE, radio 1.12.00, extrom now says 1.06.150. i think the only thing this cab changes is this rom number, nothing else
orcas

orcas,
I believe you are absolutely right. When the extended rom has finished installing the programs, it runs this .cab file to 'brand' the Magician with the build number. Nothing more or nothing less. But faith can move mountains, as we all know...

I guess some of you know that there is another (older) thread about GPRS problems. If you do not, there is a link below.
Anyway, I finally tried the most recent suggested fix in that thread (downgrading the device's CallerID program to an earlier version) and like a number of others I can happily report that so far, it has fixed my GPRS cannot connect problem. Looking good.
Here is the thread:
http://forum.xda-developers.com/viewtopic.php?t=20428
- Peter

Just thought I'd share that the second fix I tried (downgrading CallerID) has continued to work for me. I have no more problems with GPRS. All is well with my Magician. At last.

P800 rom flashing problem

I have an unbranded Chinese P800 from eBay and would like to upgrade it to WM 6.0. What I have onboard :
1. WM 5.0 OS 5.1.525 (Build 15364.3.4.4)
2. Processor ARM926T OMAP730
However, one perculiar thing is that I can't find any Device Info on IPL, SPL, Radio ROM etc. I've tried using WST 4.2.2 but to no avail. I'm using my Lenovo S10 Netbook running XP and ASync 4.5. What I've managed to do are :
1. Run USPL, it goes from 0.. to 60.. and hangs, I reset my P800, USPL resumes to 70..100 and the RUU program starts,
2. the screen on my P800 turns dark with the Linux Penguin and some message of mapping, preloader etc comes on temporarily before Windows comes on again,
3. RUU runs, upgrading to image 9.99 (original image is blank-no info), when UPDATE ROM IMAGE ON YOUR PDA PHONE comes on it never gets to more than 0% (no blue progress bar), my P800 screen goes dark, loses connection and I get ERROR(260).
I have done this several times and there is no way I can verify if the CID is unlocked as I can't get the SPL info anywhere. So I will appreciate any help I can get. Thanks in advance.

Hi Salimbs,
Have a look at these two posts:
* Regarding the CID unlock for Artemis
http://forum.xda-developers.com/showthread.php?t=334667
* Regarding the error 260
http://forum.xda-developers.com/showthread.php?t=293085&highlight=error+260
Hope this will solve your problem

mouse.co.nr said:
Hi Salimbs,
Have a look at these two posts:
* Regarding the CID unlock for Artemis
http://forum.xda-developers.com/showthread.php?t=334667
* Regarding the error 260
http://forum.xda-developers.com/showthread.php?t=293085&highlight=error+260
Hope this will solve your problem
Click to expand...
Click to collapse
Hi mouse.co.nr,
Many thanks for your reply and pointing to the right direction. I'll get to it asap and post the outcome (success I hope!)

Hi Salimbs,
just another note,
in the past I found myself in big trouble (not with Himalaya as it was SD flashed) but with Charmer and Magician ROM updates, also with ROMs that I have already used in the past and classified as stable,
Roms used to get blocked during upgrade leaving me in Boot mode if I don't remember bad..
I have noticed that this error was common when Ms. Office applications like for sxample Word or Excel was turned on!
it makes like a kind of disturb to the rom!
once closed (all office and not necessary applications) roms updates smooth and bug free!
Don't remember if it was an Err 260 or not, I just remember that update blocked at a certain point...
try to do your upgrades with office turned off!
wish it will help to solve your problem
X-Mouse

mouse.co.nr said:
Hi Salimbs,
just another note,
in the past I found myself in big trouble (not with Himalaya as it was SD flashed) but with Charmer and Magician ROM updates, also with ROMs that I have already used in the past and classified as stable,
Roms used to get blocked during upgrade leaving me in Boot mode if I don't remember bad..
I have noticed that this error was common when Ms. Office applications like for sxample Word or Excel was turned on!
it makes like a kind of disturb to the rom!
once closed (all office and not necessary applications) roms updates smooth and bug free!
Don't remember if it was an Err 260 or not, I just remember that update blocked at a certain point...
try to do your upgrades with office turned off!
wish it will help to solve your problem
X-Mouse
Click to expand...
Click to collapse
Hi mouse.co.nr,
Well noted and I'll keep this in mind. From your experience have you ever tried the SDHC.cab so that your phone can read the micro SDHC? I ran it in my phone and now my STORAGE CARD is gone! Anyway, thanks again. Cheers!

Not SDHC my friend but Artemis SDHC,
I don't know what is exactly the difference, maybe one is for big SD and the other is for MicroSD, anyway I've tried the one for artemis and now I'm working with a 8 GB micro sd, and it can go till 16 GB.
I've tried that with other artemis ROM versions and works very good...
For your problem have a look at this post:
http://forum.xda-developers.com/showthread.php?t=345038;
and download the programs indicated below...
What I advice you to do is the following:
1) remove your SDHC card (it have a sort of bad luck with any upgrade that needs a reboot)
2) copy SDHC_Artemis_back2original.cab to your documents folder (PPC documents obviously) then run it, soft reset.
3) then copy the correct SD HC for artemis "SDHC-Artemis.cab ", in the same way of the above and run it.
this shuld work "I wish for you"
let me know..
how about the ROM update? did you succeed at the end?
have you also updated also GSM radio ROM? generally original roms come with a 2.11.... version, old and not always good in reception!
I advice to change it in 03.18.90 shall work well also with your provider, for GSM signal WIFI, GPRS and GPS..
have a look at this post for more details: http://forum.xda-developers.com/showthread.php?t=397939
X-Mouse

mouse.co.nr said:
Not SDHC my friend but Artemis SDHC,
I don't know what is exactly the difference, maybe one is for big SD and the other is for MicroSD, anyway I've tried the one for artemis and now I'm working with a 8 GB micro sd, and it can go till 16 GB.
I've tried that with other artemis ROM versions and works very good...
For your problem have a look at this post:
http://forum.xda-developers.com/showthread.php?t=345038;
and download the programs indicated below...
What I advice you to do is the following:
1) remove your SDHC card (it have a sort of bad luck with any upgrade that needs a reboot)
2) copy SDHC_Artemis_back2original.cab to your documents folder (PPC documents obviously) then run it, soft reset.
3) then copy the correct SD HC for artemis "SDHC-Artemis.cab ", in the same way of the above and run it.
this shuld work "I wish for you"
let me know..
how about the ROM update? did you succeed at the end?
have you also updated also GSM radio ROM? generally original roms come with a 2.11.... version, old and not always good in reception!
I advice to change it in 03.18.90 shall work well also with your provider, for GSM signal WIFI, GPRS and GPS..
have a look at this post for more details: http://forum.xda-developers.com/showthread.php?t=397939
X-Mouse
Click to expand...
Click to collapse
Hi Mouse,
Thanks to you my STORAGE CARD problem is solved! However with regards to my ROM update I'm still a little confused.I've managed to patch the artemis_jumpSPL_pof_v1.nb using Kermit the Frog(jumpSPL.exe). After that I run the RUU again but I still get the same result-0%Can you tell me how or show me the relevant threads?

Hello Salimbs,
Kermit sounds funny but it's the first time I don't know how does it work!!
try the ufficial SPL unlocker for artemis, nothing more,
download from here:
http://forum.xda-developers.com/showthread.php?t=311403
* Connect your PPC through Active Sync (connection shall be established),
* Run start_uspl.exe from the Artemis_USPL package in the link above,
* Run till it reachs 100% and Dos Window turns off alone, and launches RUU upgrade interface..yes, yes, continue, continue.... 100%
* After device shall have SPL 1.11 and so you can load new ROMs
let me know if it will solve the problem..
X-Mouse

mouse.co.nr said:
Hello Salimbs,
Kermit sounds funny but it's the first time I don't know how does it work!!
try the ufficial SPL unlocker for artemis, nothing more,
download from here:
http://forum.xda-developers.com/showthread.php?t=311403
* Connect your PPC through Active Sync (connection shall be established),
* Run start_uspl.exe from the Artemis_USPL package in the link above,
* Run till it reachs 100% and Dos Window turns off alone, and launches RUU upgrade interface..yes, yes, continue, continue.... 100%
* After device shall have SPL 1.11 and so you can load new ROMs
let me know if it will solve the problem..
X-Mouse
Click to expand...
Click to collapse
Hi mouse,
Actually "Kermit the Frog" is the icon for JumpSPL.exe. Anyway, like I've mentioned in my first post everything seems OK except that I can't check for the SPL and when the RUU runs it never gets to more than 0% and then I lose connection and get ERROR 260. I'll be trying again and let you know of the outcome. Once again, thank you, I really appreciate your help!
salimbs.

Hi Salimbs,
sorry for hearing that...
try to enable RAPI before USPL!
http://forum.xda-developers.com/showthread.php?t=320155
Remove SDHC card (and uninstall SDHC software from ppc)
Then USPL
Then Rom Update Utility

mouse.co.nr said:
Hi Salimbs,
sorry for hearing that...
try to enable RAPI before USPL!
http://forum.xda-developers.com/showthread.php?t=320155
Remove SDHC card (and uninstall SDHC software from ppc)
Then USPL
Then Rom Update Utility
Click to expand...
Click to collapse
Hi Mouse,
I'm open to all suggestion. I'll try it again and we'll see. Thanks.

I'm afraid that I've not met with any success after trying all the combination and tricks mentioned in this thread. Every time at the part of the RUU flashing it never goes beyond 0% then I lose connection and get ERROR 260. I would appreciate any help I can get, and thank you in advance.

Hallo,
i have got a p800 from china and have the same problems. I tried all things but the update doesnt work. The connection always interupts with err260.
regards