Database Users

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.

HTC Alpine radio 1.04!!!

Here is rom with new Radio ROM 1.04
http://extendedsystems.dk/download/qtek/2020i/WWE_Sonofon_11100_165_10400_Ship.exe
Enjoy

Thank for the new radio, but some how I got country erro on the processing upgrade.
Please Help.

is this for the xda 2i please ..only asking as i'm not sure
thanks

This rom is only for Alpine phones, thats the 2i, 2020i etc.
As soon as my broadband is working again (tomorrow hopefully) I'll post the O2 162 rom with the radio 1.04 update for the UK users and anyone else who wants it.
If you want to try this update on the 2i you will need to extract the files from the installer and locate a copy of maupgradeut_noid.exe and use that instead of the included installer. There are better instructions elsewhere on this site, just do a search for my name, I'll be in amongst it all somewhere.

cheers i'll give it a go but if you are doing it maybe i'll wait ,i've only just gone back to your old 1 tonight as i don't use blackberry & it seemed better than o2 update

I have just posted the ROM upgrade on the ftp site, the only change is the radio from 1.03 to 1.04. It seems to give a better signal strength than version 1.03 on my phone anyway.
Here's the link to download the O2 version I just combined
(Edited to working link
ftp://xda:[email protected] XDA_IIi_Upgrade_v1.11.162_Radio_1.04.rar
1: Backup your contacts/device to Storage, Storage Card or PC. If you are using Ext Rom 1.11.162 now you can use full device backup to restore at the end to save you re-installing all your programs later.
2: Extract the ROM using Winrar to a folder of your choice.
3: Run MaUpgradeUT_Noid.exe. The install will fail, don't worry, just run it again without touching the phone.
4: When the upgrade has finished, do a hard reset by pressing the power button and reset button at the same time.
5: Install any programs and any data you backed up during step 1.
Good luck.

Excellent stuff
Upgraded and now running 1.04 radio and i can also say it has improved my signal strength too
Big thanks Pug for your work on the ROM image too, very much appreciated.

Hear, Hear. Many thanks to Pug, great work!

many thanks to Pug,
its work perfectly.....no more lag of ringtones or lag after green button pushed!! thanks Pug.....
i want to know about backup, after upgrade ROM, i cant restore back by backup. When using Backup Sprite, i will go back to old ROM after restore complete. any ideas????

@ Clustered
When you say it goes back to the old rom do you mean that the Radio rom is regerted back to 1.03 or that your extended rom goes back to 192 or whichever you are using?
Sprite backup should not revert the radio rom back to 1.03 as it should only do the file system of your device.
As far as the extended ROM version, all it is there for is to indicate the "update" status of the extended ROM and what software is installed in it. An asian rom may have a higher rom version but may be no newer or better than the european 162 rom. You're talking about comparing hedgehogs to wibbles, completely arbitary. As soon as you cook the extended ROM like I have it is completely meaningless anyway as the version number is no longer valid.
If you wish to change the version number yourself, use a registry editor and go to:
HKEY_LOCAL_MACHINE\SOFTWARE\OEM\3RDVERSION and change the MSYSTEM value to whatever you like.
If I have the wrong end of the stick, I apologise otherwise I hope this helps.

huh!? are u mad at me ??? anyway, i just wanna tell that you're the great! thanks very much....

I'm not mad at you, just woke up from a night shift....bloody binmen.
Was just trying to figure out which rom was reverting and so on. Hope it was of use to you anyway.
Once again, sorry.

HELP!
I Can't Upgrade the ROM.
step 1 is OK (radio)
Step 2 is OK (EXT):
Step 3 to 8 % PC show : Error 112: CE ROM UPDATE ERROR
WHY???
i run the MaUpgradeUt_noID.exe second Time , but frist Run MaUpgradeUt_noID.exe Need to STOP(use TASK Manager)??
PLEASE HELP ME

thanks for the update ..it's upgrading at the moment

thanks for the update, the only problem i'm having is that even though i've got the in call volume as low as it will go it is still too loud to be comfortable which is a big change from the previous rom. Also when using in the car on handsfree the other person can hear his voice echoing as they speak. Any ideas????

Successfully upgraded my XDAIIi.....
I'm now with the latest ROM from O2 UK (1.11.169 WWE) and the Radio version 1.04.00

Hi, I'm from Malaysia and will this rom be able to use on my device?
I'm using XDA IIi and device id is PH10C.
I'm affraid there will be a problem for my local operator "Maxis".

@ ramnkc
To be honest I can't see a problem with this ROM working with your current operator. I'm pretty sure that others from your neck of the woods are using the ROM with no problems. The biggest problem you would have is that it wouldn't load all your GPRS, WAP, MMS, etc settings as it is a UK rom.
Make sure you can get hold of these settings off your current provider before you perform the upgrade. Or as an alternative, extract your current ROM and reload it back onto your phone using SD card.

thanks for the reply !
Well i guess i gonna wait for the official release coz so far i'm happy with it. Apart of the constant SD Card data missing after playback mid, mp3 or what ever music files from SD Card.
And i finally found out that it cause by SBP pocketplus which had an option to close all application once you tab on X. Once i turn that option off in pocket plus so far problem free.
Guys/gals out there have this problem ?

ykyloveu - Does this mean you have BB Connect as well? The only modified rom from here I can download is based on cer .112 The new rom for o2 with BBConnect is ver .169

WM2003, No Camera

Hello,
I flashed back to Windows Mobile 2003 SE after having windows mobile 6 installed.
The only problem is the camera does not work, There is no camera option in the menu, and when I press the camera button nothing happens.
The OS I flashed with is WM2003SE 2.06.00WWE XDA2 from the buzzdev website.
Any help?
Thanks.

sounds like you dident put in a new extended rom where the cam software autoinstall from

I searched on the forums for extended rom and found this :
http://forum.xda-developers.com/showthread.php?t=221732
So I put contents in my STORAGE, as per instructions, and now I am flashing, is this the correct way?
One Question, is there any newer WM2003 SE ROM avaliable for himalaya than WM2003SE 2.06.00WWE?
Edit : Nothing happened I still do not have camera, and I also notice My XDA II splashscreen is not showing up, instead it is a blank screen, probably some firmwares I flashed with earlier messed everything up on my himalaya.
Edit 2 : I manually looked through the extended rom contents and found the camera and installed it and a few other programs, but I get error "the program you have installed may not display properly because it was designed for a previous version of Windows Mobile software" nonetheless it works

extended rom is a nbf file like a real rom it include a list of cab files and a text file which list the cabs
after a hardreset it auto install all the cabs
you dont need to flash a nbf file (it's don the same way as a normal rom buzzdev prob got some)
about 2003SE then it's a bit of a bastard rom
it was never released (as far as i know) as WWE (world wide english)
but only as chineese and was manualy translated to english by fans (heard that there are still chineese bits around in the rom which display as garbage chars)
about a later 2003SE then there was another chineese rom 2.11 or something like that
but it was pretty unstable so never translated to english
personaly i were to drop wm6 wm6.1 or wm5 and go back i would go to wm2003 not se
version 1.77 as it's more stable so unless one need the rotate without a softreset (which is pretty much the only thing i recall SE offering )

About the EXTrom, i was never able to get it to install after Hard Reset, I have to manually install the cabs myself, ussually I remember my pocket PC would say "Please wait until your device is configuired" , then it would install a few things. But since I have began flashing with all sorts of firmwares I cant get the extrom contents to auto-install after hard reset, so i have to manually install them myself. And you are right, I am seeing weird garbage characters already after instaling the MMS programs from the extended rom contents.
But I do remember the first time i went to WM 2003 SE, which was a few years ago, I got the ROM from the offical o2 xda website, and it was perfect. But thats not longer available.
As for WM2003SE, I always thought it was an upgrade to 2003, I thought that SE (Second Edition) should be more stable.
I might just flash to WM2003, not second edition, do you know where I could find the ROM + Extended Rom contents for it ?

yeah it's 2th eddition
but wm is not more stable then the drivers and 3th party stuff
the rom have in them
also heard about a wwe 2003SE but never confirmed that it was around
maybe if you google deep and long enough you can find it
about official 2003 roms for himalaya then first place i would look would be
the ftp of this site they may still be there
2th would be around at buzzdev
3th would be on the sites or ftp's of o2 / tmobile/ imate and the likes
4th would be googling around

Ah the problem is the XDA Developers ftp site is not working. I looked over at buzzdev and they have no WM2003 Roms for the Himalaya, only WM2003 SE

Ok from XDA Developers ftp I find the following :
1.60.36 T-Mobile_NL_Shipped
Himalaya_T-Mobile_NL_1.72.903_eDsuBsofT
Himalaya_T-Mobile_NL_1.72.90_Shipped
Himalaya_T-Mobile_NL_1.75.903_eDsuBsofT
Qtekk_1.75_Converted
I believe they are all WM2003 (not se)
Which one to use?

V1605 / WM6 / TomTom Nav 6 - possible?

Hi all,
Have searched the wiki and threads but can't get a definitive answer?
So my question is this....
I have a Vodafone V1605 that is running with its original ROM (which is generally cack but I do use TomTom 5.21 with a Holox receiver which actually works pretty well.
Now, I've just bought TomTom Navigator 6 (latest version and so latest build - can't be precise, but will d/load latest update when s/w arrives).
However, I'm also considering flashing my ROM for a WM6 build (or later WM5 build if that's a no-go).
There's nothing like making a challenge for yourself is there
So basically, is there anyone out there who's managed to:
a) Flash a v1605 successfully with a stable WM6 ROM (and if so, which ROM)
b) Then managed to get TomTom Navigator 6 running on it?
Thanks all - what a hugely useful forum this is!

Mate, as long as your phone is a Hermes, every wm 6 rom works brilliantly but wm6.1 is SPEEDY and some of the newer releases seem stable (its been getting better as the chefs get newer builds). You need to do some research to find the right rom for you as its a personal choice on what you like... DON'T make the mistake of asking what is best as you'll be inundated with answers why people think the rom they are using is best but it may not be the best solution for you...
As for Tomtom, It works brilliantly. Just upgraded to Tomtom 7. If you looked here 1st you would have found it on the site for download. It is offered on the Diamond and has been ripped and modified to work on the Hermes. You still need to purchase maps but it is a hell of a lot better than Tomtom 6.
My suggestion, look here first before spending cash, sometimes you find apps that are as good as or better than their commercial counterparts... There is a hell of a lot of apps out there that aren't available commercially too. Most apps seem to feature here first and then go commercial (a good example is touchflo). Thats not to say that the commercial programs aren't brilliant too and I believe the pittance we pay for them REALLy does help to make some awesome apps..
Cheers...
If you do upgrade your os, make sure you read and do this - http://forum.xda-developers.com/showthread.php?t=296722
Hard SPL is a MUST for anyone flashing roms... It won't guarantee a perfect flash but makes it SOOOO much easier if(and when) something goes wrong...
Also give this a read as you can unlock your phone to allow ANY sim card to be inserted and used - http://forum.xda-developers.com/showthread.php?t=293665
Welcome, and happy flashing....

Thanks mate - all sound advice
First thing I did was to install Hard SPL (2.10 Olipro) - better safe than sorry - but that's as far as I got.
I did try to install the latest (final) official Vodafone RUU 2.07.161.1, but it crapped out with Error 260. I decided to cut and run at that point as I was worried I'd bricked the device - but it's all ok now after a hard reset (yes, I'd backed up my data
I'd be using an err... eval version of TT5.21 and it's been great - so much so I decided to cough for a full legit copy (UK and W.Europe) of TT 6 Navigator.
I'll try it on the standard ROM (WM5) but well, you know how it is, I like to have stuff up to date, so it would be good to flash a WM6 ROM. Oh, this and the fact that Vodafone won't give me a phone upgrade until next October!
So I just wanted to hear from someone who'd done it successfully with a full-fat version of TT6 Navigator running on WM6. If it was running with a Holox BT receiver then even better!
S/ware (and 2Gb Micro SD card) here in a day or two - so will sit tight and see....
Thanks!

tt running
i have latest radio 1.54.30.10 Schaps_WM6Pro_Hermes_4.31_WWE_Lite on my v1650 supercided
tt7 (orig.)) fine runing all m8

tomtom works perfectly on the hermes, v5/6 or even the tt7 version. I have it working on pdacorner pro wm6.1 v15 at the moment and it works fine.
So chill out on the worries and flash a wm6.1 rom if you get a 260 connection error try entering the bootloader manually yourself and try flashing it then, just tick the boxes saying you agree and you have an active sync connection(even though you dont). Also if you download one of the latest wm6.1 packages then the ruuwrapper file is an updated version which solves most of the silly errors that pop up when trying to flash e.g. error 260/300 etc

anryl said:
i have latest radio 1.54.30.10 Schaps_WM6Pro_Hermes_4.31_WWE_Lite on my v1650 supercided
tt7 (orig.)) fine runing all m8
Click to expand...
Click to collapse
That's what I wanted to hear - thx mate

If connection issues are a worry however, now you have Hard SPL you can use the SD Card method. I personally haven't EVER had problems with this and I believe its safer as there are no concerns about usb cables being unplugged, reset button being pressed or powwer fluctuations/outages.
To do this,
1).first format an sd card fat32.
2).Copy the .nbh file in your upgrade directory to it and rename to Hermimg.nbh. 3).Put into hermes and go to bootloader screen ( hold powerbutton, OK button above flywheel and rset with stylus. Hold in until tricolour screen appears - This is called bootloader screen) It should automatically recognise the os flash information.
4). Follow prompts..
Easy as 1,2,3,4.
Cheers...

[Q] How to backup original ROM of my I-mate Jas jar

Hello,
how can I backup the original Rom of my I-mate jas jar ?
I am fairly new to this and I want to upgrade from WM 5 to WM 6.5.
Thanks
Regards,
Some one

Welcome to forums
Applications can be stored on your SD card with no problem, and as for your SMS and log calls search for PIM Backup.
WM6.5 is 100% working on Universal but its heavy to run unless you have a modified 128Mb RAM, if not I would recommend WM6.1 (Tomal 8.2, 8.5 and 8.9 ROM´s) as they will be fast and stable.
Instructions to upgrade on my signature link.
Good luck,

Thanks orb,
But I was asking if there was a way to backup my original Wm5 from my phone , I have already backed up the apps and contacts.Now (if there is such a way) I want to backup the actual WM which came with it.
Regards,
some one

If you mean to the ROM this will be wiped out but you can check on my signature link for WM5 ROM to have it.
Believe me once you test WM6 or above you won´t want to go back, unless video call is a must for you
Good luck,

Yes I saw the wm5 in the signature on your link but isn't there a way for me to backup wm5 from my own PPC??
Oh and from where can I get the java midlet manager for wm5 (till I have not flashed my phone ) , I want the cab file of the same one which comes pre-installed?

Backing up and reconstructing the ROM is hard work. There's usually no reason to do so unless you want to cook your own rom. If you can find the version of your rom (probably somewhere in start-settings-system, can't recall exactly where off-hand), you can download the same or a newer version if you want to return to it later. As orb3000 says though, you won't want to unless you really have to make video calls.