Related
This message contains all postings in this thread
dated before January 19th 2003
Subject: New ROM & radio also here ...
From: Muellmaen
Date: 18 Dec, 2002 10:12:09
At http://www.myxda.com there is
now the Asian ROM 3.14 and radio 4.16 available. But you need an
Asian IMEI Can somebody help out ?
<span class="sm" style="color:#999999">modified: 18 Dec 2002
15:29</span>
Subject: new rom
From: MiNG
Date: 18 Dec, 2002 17:42:24
download at my tempoary ftp server
202.166.108.116
userid: xda
password : xda123
Subject: new rom
From: Muellmaen
Date: 19 Dec, 2002 10:32:31
Hi Ming,
seems that you are also at every corner 8)
Subject: My XDA is fried
From: Confused
Date: 20 Dec, 2002 17:59:00
My XDA stopped flashing in the middle of upgrading the Radio
version 4.16. Now my unit is senseless. I tried to reflash but
it didn't work out.
anybody here knows how to solve this problem? Is it possible to
backup the GSM ROM using the Wallaby bootloader? Any idea if
this can be solved with hyperterminal (parrot) method?
Subject: Fried XDA too...
From: :-(
Date: 20 Dec, 2002 21:07:37
The same happened with my XDA... The Radio Stack Upgrade version
4.16 stopped flashing at 10% and afterwards the GSM part of the
XDA didn't work anymore and the XDA itself started to behave
weird (long boot up time, no ActiveSync connection etc.)
OK, maybe I shouldn't have flashed the Asian RSU version over my
German XDA but it did work with the Irish RSU version.
Now, I will need to buy an MMC/SD card reader and try to restore
the Flash ROM with the ROM image tool from this site...
At least I have some free time around Christmas...
Subject: Hate to say this, but ...
From: XDA developers
Date: 20 Dec, 2002 22:13:02
We've never claimed anything about the phone updates yet.
The XDA-developers ROM Image Tool using SD cards, as published
on this site, will only help you flash the Bootloader and the
Windows CE image, both located in the 32 MB of flash attached to
the main (Strong ARM) processor.
The phone image is uploaded through the PDA to another 4MB of
flash attached to the "digital baseband chip", which is a
completely different (ARM7) processor and DSP combination.
We're working on the GSM ROM, but no guarantees as to when work
is done. If you send us mail at [email protected],
we'll try to see if we can help you, and we'll post the outcome
here.
Subject: Fried XDA
From: Festan
Date: 20 Dec, 2002 23:10:57
(I'm the guy who flased the Asian RSU over his German XDA)
Thank you for the clarification about the separate flash memory
areas.
I'm actually suspecting that the failed Radio Stack Upgrade did
some harm to the regular flash memory that stores the OS.
Here is what happened so far in more detail:
- RSU stopped flashing at 10% as described previously
- Soft reset (the big hole)
- XDA needs quiet long to come up because it unsuccessfully
tries to start up GSM but it does come up with the Today screen
at last (and GSM turned off)
- XDA behaves weird (no ActiveSync connection, RSU upgrade
cannot be removed) but is still operable, i.e. reacts to user
input
- Hard reset (the small hole) with 60 secs wait time between
punching into the small hole
- Now the XDA behaves even weirder: Long boot up time, white
screen with a blue border at the top, hardly any reaction to
user input, after pressing the volume button a couple of times
the Today screen appears but somewhat mutilated
So my conclusion is that there must be something wrong with the
flash ROM holding the OS because after the hard reset which
erases all RAM the XDA still doesn't work right. I'm guessing
that if the GSM part cannot correctly be turned on (because of
an incomplete radio stack), it should not severeley impact the
rest of the OS.
Just to inform you: I'm also a developer (telecommunication and
networking) with electrical engineering and computer
architecture background so I don't mind reading all the
technical terms
Subject: Fried XDA
From: Confused
Date: 21 Dec, 2002 08:38:46
Well, I flashed my 3.12 & 4.06 Asian ROM with the Irish 3.14
plus the Radio version 4.14 without any problems. They are
working perfectly until I got an itch to flash the Radio version
4.16. It stopped exactly at 10% and afterwards it behaves as
described above. What happened is that the Top Bar is
completely unusable. I tried a hard reset and the screen is
completely blank. To get to the Today menu, I need to press the
volume buttons. Then by pressing the Action & Calendar keys I
did the screen alignment stuff. I used the same buttons
pressing combination to activate the StartMenu (it's a pain to
get it though). Once I access the StartMenu, I mapped the file
explorer shortcut to the StartUp so it will be activated
everytime I soft resetted my XDA. Then I copied the CAB files
of both 4.14 & 4.16 version and tried to reflash my XDA. But
none of them worked out
I would be pleased to try any suggestions to bring my XDA back
from the dead :wink:
Subject: Fried XDA
From: Confused
Date: 21 Dec, 2002 08:41:34
Well, I flashed my 3.12 & 4.06 Asian ROM with the Irish 3.14
plus the Radio version 4.14 without any problems. They are
working perfectly until I got an itch to flash the Radio version
4.16. It stopped exactly at 10% and afterwards it behaves as
described above. What happened is that the Top Bar is
completely unusable. I tried a hard reset and the screen is
completely blank. To get to the Today menu, I need to press the
volume buttons. Then by pressing the Action & Calendar keys I
did the screen alignment stuff. I used the same buttons
pressing combination to activate the StartMenu (it's a pain to
get it though). Once I access the StartMenu, I mapped the file
explorer shortcut to the StartUp so it will be activated
everytime I soft resetted my XDA. Then I copied the CAB files
of both 4.14 & 4.16 version and tried to reflash my XDA. But
none of them worked out
I would be pleased to try any suggestions to bring my XDA back
from the dead :wink:
Subject: flash crash
From: Muellmaen
Date: 21 Dec, 2002 11:31:41
sounds not to god at all ....
What to the experts think about it ? For me it seems, that the
top bar does not show up, because the XDA does not a status from
the phone. What happens if you try to deactivate the phone by
pressing the off hook button (red phone) for several seconds? I
had a similar problem after (trying) to flash the 4.06, but
after a hard reset and switching off the phone I was able to
flash the phone directly from the device. But, as it is unclear
at which point your flash crashed, it might not help. If nothing
helps, just go to a o2 shop and look as innocent as you can
:wink: :wink:
Subject: Flash process not fail safe
From: Idefix
Date: 21 Dec, 2002 16:53:02
As many of you already found there are strong indications that
the flash process is not fail safe. There is very likely *no*
fixed ROM in the whole XDA. This means when the flash process
goes wrong you're stuck cause the CPU can't boot anymore and the
flash process can not be restarted.
FYI this is different from for example a Nokia phone where it
allways first boots from ROM that is not reflashed. This way it
can almost always be repaired with normal flash equipment even
if the flash ROM is completely ****ed.
One thing on the RSU update: it seems that this always is a
partial flash. For example GSM calibration data is always
retained, but also some of the code is not reflashed. This means
that it most likely is an incremental flash and that could mean
it is not useable over just any other existing flash version.
I suspect that the only way to repair a broken flash on an XDA
is to reflash through JTAG or other means of 'in circuit'
flashing.
Idefix
Subject: Top Bar is OK now
From: Confused
Date: 21 Dec, 2002 18:00:11
I managed to get the top bar to work. What I did was I deleted
all shortcuts associated to the phone like SMSReceiver,
Handsfree, poutlook etc. Now after resetting, the top bar is
working. At least now my XDA is usable as a PDA :wink:
Subject: Fried XDA and XDArit attempts
From: Festan
Date: 21 Dec, 2002 18:39:59
Hi,
I played around with XDArit in order to try to repair my XDA. It
took a while and a few flashing attempts until I found out that
the binary file in the official O2 update distribution does
contain the bootloader. It also contains a kind of a header
(ASCII characters) that indicate the version and language.
XDArit does not strip off the header but takes the file as it is
to generate the SD card data. So at first I ended up flashing
something totally wrong into my XDA and it made it even worse
(only Wallaby came up, nothing else).
After stripping off the header and the bootloader data (256K)
and using this altered file for XDArit, I was able to get back
to the point where I was before (white screen, no top bar).
I will try Confused's tips now and hope that I can somehow get
the correct Radio Stack into the device.
Subject: XDA ROM Image Tool
From: XDA developers
Date: 22 Dec, 2002 15:56:27
The text on the XDA ROM Image Tool page has been rewritten, and
is now much easier to understand.
http://xda-developers.com/
XDArit
On the same page, there is now also a diagnostics card image
that allows patching 5.17 bootloaders to be able to dump and
flash from SD.
Festan: XDArit reads the upgrade .nbf files directly, so you did
not need to go through so much trouble. Just select .nbf as the
input file type.
Subject: Rescue XDA RSUpgrade
From: PL
Date: 23 Dec, 2002 10:40:29
I have tried a few times on upgrade and face the same problem as
all of your faced.
You have to take out the SIM and try again. There will be a
message "Take out AC before start" and later it will pass 10%
and it run OK.
Subject: XDA ROM Image Tool
From: Festan
Date: 23 Dec, 2002 21:30:47
XDA Developers:
Yes, I didn't realize that the type of input file for the flash
can be chosen.
However, my XDA still doesn't work properly. The PDA part does
work (after applying Confused's tips) although the response time
to user input is sometimes quite high. The GSM part is still
broken. Maybe the OS tries to access some GSM functionality but
cannot and thus causes the pauses.
Subject: Fried XDA
From: SuperKT
Date: 25 Dec, 2002 04:58:10
Please help to confirm how to solve this problem that I also
faced it.
Subject: Need Bootloader and WinCE ROM
From: SuperKT
Date: 25 Dec, 2002 08:36:13
I tried to solve by the flash ROM but I cannot find the
Bootloader and WinCE ROM Image. Please help to ask me for
downloading. Thanks.
Subject: Images
From: XDA developers
Date: 26 Dec, 2002 12:30:18
You'll all notice we become very quiet when it comes to firmware
images. XDA-developers does not, and will not, distribute
software that carries someone else's copyright. Besides: there's
a number of legal sources for these images on the net: O2
Ireland being the prime source for European O2 users at the
moment.
http://www1.o2.ie/master?content=http://www1.o2.ie/xda_upgra
de
SuperKT: if you really need to flash both bootloader and WinCE,
do as follows:
- Get NT, Win2000 or XP
- Get a PC-card or USB to SD-card adapter
- Get the Irish update and let it install without putting XDA in
cradle.
- Start XDArit (
http://xda-developers.com/
XDArit )
- Write to SD from file, check bootloader and WinCE, and use the
.nbf file from the "English" directory of the upgrade package.
- Insert card in XDA and put in bootloader mode
- Flash from SD
Procedure changes somewhat if you have a 5.17 bootloader. See
the XDArit page mentioned above.
Subject: It doesn't work
From: SuperKT
Date: 27 Dec, 2002 09:47:10
XDA Developers,
I tried to do as suggested but it has an error after ROM Flashed
to XDA "Check sum is not correct". I rebooted my XDA but it's
not been work.
I did :-
- Get Win2000
- Get USB to MMC-Card
- Get NK.nbf in the "English" directory of the Asian upgrade
package
- Write Wallet Patch to MMC-Card because my loader version is
5.17
- Boot from MMC-Card with patch
- Take out MMC-Card
- Write NK.nbf to MMC-Card
- Put MMC-Card into XDA
- Select Restore from SD
- It was flashing until finished at 200000 and have the error
"Check Sum is not correct" , Cold boot, Reset
- I dis rest but it's still the same problem
- If boot by loader it has still been "GSM Error".
Subject: Flash problems
From: XDA developers
Date: 29 Dec, 2002 14:33:24
We're aware of multiple people having problems wrecking their
phones during upgrades, usually using the normal RSU upgrade
packs meant for their phone. There's currently not much we can
do, but we are peeking more and more into what is happening
during the phone upgrade process. More info will certainly
follow in the next few weeks.
As for the WinCE part not flashing correctly: flashing through
the bootloader has been very reliable for us, and we're not
aware of others having similar problems. SuperKT: please send us
an even more detailed description of what you did exactly via
e-mail to [email protected].
Subject: XDA Update Problem
From: onkeldietmar
Date: 30 Dec, 2002 09:05:30
Hello,
Festan please contact me. i have the same problem as you.
i' ll hope you can help me, because i don't want to sent my XDA
to the service center.
Thanks
[email protected]
Subject: ROM Upgrade
From: FintonK
Date: 06 Jan, 2003 12:57:53
Hi,
is there any chance someone could send me a link to download the
new Asian ROM 4.16, i tried MiNGS but the ftp server is no
longer active. I dont have an Asian IMEI to get it from
www.myxda.com
Subject: Or Please mail it to me!
From: FintonK
Date: 06 Jan, 2003 12:58:38
[email protected]
THANKS!
Subject: ASIA rom removed
From: westa
Date: 08 Jan, 2003 08:53:35
Not long after the ASIA rom update was published it was removed
from the myxda website. It looks like there are some ... need to
be fixed issues with that rom ... flash it at your own risk me
thinks.
Westa
Subject: GSM ROM
From: eladsalad
Date: 08 Jan, 2003 18:43:40
i have managed to resurrect my PDA from the dead using the tips
on this post (thanks guys) and have been fiddling to see if i
can get the GSM part working again.
dropping the (rsu_eng.exe) GSM ROM CAB file onto a SD card and
then into my XDA and 'tapping'it starts the Flash Update 1.08
program, tho it doesn't complete (or really start the flash
actually). I have tried a few different things (like SIM/no SIM
and AC Power/no AC) but to no avail.
anyone have any ideas what may be stopping the rsu program from
working?
thanks to xda-dev for they're excellent work and the guys in
this post for thier advice.
Subject: cannot enter patched BL
From: Bong99
Date: 09 Jan, 2003 04:21:03
My BootLoader is 5.17 and I follow the
http://xda-developers.com
/XDArit/
I copy the file "wallaby-patch-tool.nb2" into my 64 MB SD card
to the root directory. Then enter the bootloader mode with
inserted the SD card.
But it cannot enter the Patched BL mode.....
Am I doing something wrong?
Thanks
(mods i would appreciate if you could make this a sticky for people... ive worked long and hard trying to get this thing working again)
Ok so heres what happened to my XDA which proberly happened to yours.
I went onto the 02 site and got the latest radio stack upgrade for my xda, but i didnt have the sim in my device so once it finshed and restarted the xda it crashed because there was no sim in it. So i hard reset it.
Causing it to hang on the boot screen showing the G & U letters on the side for about 4 minutes before booting to a blank screen with the keyboard icon in the corner.
*** Please remember at the moment my status LED isnt working showing there is no battery (but still booting etc - P.S i have installed a new battery - no diffrence) ***
Heres how to get it working...... remember that everything takes longer because the XDA lags like mad.
Ive created this guide myself ive took nothing from anyone else info ive done this from scratch, it will need to be done everytime the machine runs out of power (hard resets).
---------------------------------------------------------------------------------
* when i put " + " it means AT THE SAME TIME e.g button1 + button2 = keep pressing them at the same time.
** I refer to the directional keypad centre button as the "OK" button.
Make sure you have the correct RSU Version from here :>
http://wiki.xda-developers.com/index.php?pagename=Wallaby_HT_GSMError
Download it and put the files onto an SD card.
1. Boot up the device
2. keep pressing the OK button + volume button until it shows the today screen, please note there will be no titles on the screens, HENCE NO START BUTTON.
3. Then press the contacts button + THEN OK a few times, then press the OK button this should bring up the start menu
4. CLICK programs, file explorer, select the SD Card. Then Copy RSUPGRAD.exe to : my device > windows>start up.
5. Copy the remaining 3 files to the : my device > windows
6. Soft Reset Device
7. Click on start (on the upgrade util) it will then restart the device because theres no LED for the battery (hence the 1% then fail).
8. Once started it should then start up as it did when it came out the box giving you the windows setup screen.
9. Go into file explorer and delete tha flas util file from the startup.
Thats it!
- Remember if you hard re-set the device again it will need to be re-done, i dont know how to solve this problem LONG TERM, im giving my XDA to 02 to fix it...... been as its there screw up.
----------------------------------------------------------------------
Thanks Everyone
James
Does this actually flash the gsm radio? If it does then why does it need reflashing following a hard reset?
No it doesnt re-flash it.............
All i know is that it fixes it and many people have had the same problem but had no replys so id thought id help them out :roll:
Where are he diffreneces to the instrucions on wiki????
Stefan
huh? so your saying someone has already written the instructions?
Do you have a link? it will be intresting to find out how i can get my LED working again so the system will be able to work once more.
EDIT: IF THE BATTERY LED/STATUS IS UNKOWN (as in my case)
"Maybe the upgrade will stop again at 1%, this may occur when you have an empty battery. "
Does not apply to you............... hence why my guide overcomes the one on wiki.
If you have had the situation happen to you, then you would undertsand.
would it be possible to use the xda developers 1.2 special edition ROM instead of the 1.1 version for this procedure?thats the only rom i seem to have found.
Boogie, I think you need only the radio stack not the rom if I read the post correctly. The special edition rom contains NO RADIO STACK.
That´s not 100% correct. I´ve noticed, that some ROMs wouldn´t boot up so that you can follow the procedure.....
Stefan
hey guys this is my 1st post to this forum, but for the last year or so I've found it very helpful.
I was experiencing this same issue it would just boot up and hang on the welcome screen for what seemed like an eternity. I gave up and just left it booting up and finally the today screen came up. This is what I tried and it worked. All of this was after a hard reset when I tried to upgrade the radio stack and it fell into this infinite loop of 1% and fail and reboot. I had read a couple of the procedures for doing a radio stack upgrade but here is some of what I did.
In one of the procedures it says to copy the files to ur ppc windows directory and to copy the exe file to ur windows startup directory. I figured I would bypass that in some way. After I finally got to the today screen and used my pc to copy the files to the sd card, I copied all the files to the windows directory on the device and ran the exe file from the windows directory. It worked like a charm and my ppc was back to life. It no longer took for ever to get passed the welcome screen. I hope this helps some of you that have this issue
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.
Hi all,
First post and all that, so hi! I've been lurking for a few days, but thought i'd post this as a) I might be doing something wrong, and b) if i'm not, it might help someone..
Basically, I installed ozVGA last night, and it turned my exec into a nice-looking, albeit ineffective doorstop.
I may have done this completely wrong, let me know if i did, as i really would like a 640x480 res
This is what i did:
1. I had upgraded my exec to the latest ROM released by o2.
2. I downloaded ozVGA from http://oz.sciox.org/
3. I followed the instructions on the above URL.
a) "unzip this file VgaRes.zip and put its contents to the \windows directory"
b) After that you will need to unzip this file OzVGA053.zip and place OzVGA.exe file wherever you want on your PDA
4. I launched ozVGA
5. I pressed the ozVGA button, it rebooted, the o2 bubbles screen with the red writing stating the ROM versions etc. appeared, and the SELECT and EXIT buttons were visible at the bottom. These were in the 640x480 resolution! Yey!
6. But...it stayed on that screen for a long, long time. It would not progress from that screen no matter what I tried, or how long i waited.
7. in the end, i had to do a factory reset, then install the new o2 rom again.
So... did i do something wrong :S I hope i did - as i would really like to have my exec in 640x480!
Cheers for any help
You need the VGA res files that are on the xda-developers ftp. The ones on the OzVGA site don't work IIRC.
You didn't need to install the ROM again. A normal hard-reset would have been fine.
Thanks for replying rilot.
Are the files you mention at the start of this thread?:
http://forum.xda-developers.com/viewtopic.php?t=32217
If so, they dont actually seem to be on the FTP site.
Also, in this thread:
http://forum.xda-developers.com/viewtopic.php?t=37448
"Soft resets result in it powering backon, but stopping at the boot screen, after displaying the ROM versions in red text. "
The poster also says: "I had just installed OzVGA, and was testing it when this occurred, but that is probably just a coincidence"
Do you think this could be related? Just wondering
Grab them here: http://forum.xda-developers.com/download.php?id=7513
I've never had any problem with running my Exec in VGA mode. I don't actually use OzVGA though. I hack the registry manually.
Those files bricked my m5000
I just downloaded the zip archive from your link, unzipped, copied the windows file folder contents to the windows folder on the spv m5000(orange switzerland), and the ozVGA.exe to the programs folder, then started the .exe.
Result: the well known imitation of a brick. The thing booted to the orange screen with the red version info, then stayed there with two buttons showing at the bottom of the screen. These buttons did show the small VGA font, but none of them caused anything to happen. Soft resets didn't help either.
A hard reset worked (without re-installing the ROM) and I'm now back to where I was before.
Has anyone with an orange device had any other(better) experiences with ozVGA?
Re: Those files bricked my m5000
Rapax said:
Result: the well known imitation of a brick. The thing booted to the orange screen with the red version info, then stayed there with two buttons showing at the bottom of the screen. These buttons did show the small VGA font, but none of them caused anything to happen. Soft resets didn't help either.
Click to expand...
Click to collapse
Right, that's 2 deaths from ozvga... if this can be confirmed, is it worth adding a sticky on this forum or something?
Did you run the signing app (sdkcerts.cab) after coying the files?
If not, that's your problem.
rilot said:
Did you run the signing app (sdkcerts.cab) after coying the files?
If not, that's your problem.
Click to expand...
Click to collapse
ahh
it's not mentioned until the 3rd page http://forum.xda-developers.com/vie...der=asc&highlight=sdkcerts+cab+ozvga&start=50
which is why i didnt see it :roll:
Right then - before i try it again, is there a way to back up *everything* on my universal? So i dont have to go through the misery of setting everything up again if it goes wrong?
yezzer said:
rilot said:
Right then - before i try it again, is there a way to back up *everything* on my universal? So i dont have to go through the misery of setting everything up again if it goes wrong?
Click to expand...
Click to collapse
Sunnysoft's Backup Manager works well for me. But don't rely on restore from a backup after a ROM upgrade, since you will be overwriting those newly upgraded files with possibly older versions. Another useful trick for those difficult to configure apps, is a registry export.
As for the OzVGA glitch. Yep, the culprit is not running the signing app (sdkcerts.cab) after coying the files. Forgot to do this once myself, just at the end of re-installing everything after a ROM upgrade , so had to start again. :evil:
Click to expand...
Click to collapse
Re: Those files bricked my m5000
yezzer said:
Rapax said:
Result: the well known imitation of a brick. The thing booted to the orange screen with the red version info, then stayed there with two buttons showing at the bottom of the screen. These buttons did show the small VGA font, but none of them caused anything to happen. Soft resets didn't help either.
Click to expand...
Click to collapse
Right, that's 2 deaths from ozvga... if this can be confirmed, is it worth adding a sticky on this forum or something?
Click to expand...
Click to collapse
Weird enough, but after the hard reset, I tried again last night, and this time it worked. Beautiful VGA bliss on my m5000. A million thanks to the authors.
Now I can hardly wait for the international (german) version of vj555's BigPhone.
So just to check (before I end up hard resetting from not following instructions!) In the VGA files I downloaded from this thread, it contains ozVGA.exe, some files that need copying to my windows directory and sdkcerts.cab.
What order do I do things? I would first copy the windows files and the ozVGA.exe, then run the sdkcers.cab I take it i then need to soft reset. Where do I put ozVGA.exe? Does it just perform a registry hack or does it need to be placed in the Startup folder so it runs every time I soft reset?
Any help would be great!
Cheers
Fin
1. Copy files
2. Run SDKCerts.cab
3. Run OzVGA
4. Soft reset
OzVGA performs registry hacks so doesn't need to be placed in start-up.
Thanks for your help. Will try it tonight!
Unable to copy files in Windows directory
rilot said:
1. Copy files
2. Run SDKCerts.cab
3. Run OzVGA
4. Soft reset
OzVGA performs registry hacks so doesn't need to be placed in start-up.
Click to expand...
Click to collapse
Stuck at Step1. None of .dlls or gifs that already exist can be overwritten!
2. I am able to copy SDKCerts.cab in the WIndows folder and run it.
Tried a soft reset as well. But still can not do the step 1.
Please advise.
to all,
look at new Helmi3.5 rom
ozvga is integratted
very easy to use and if necessary to revert back to qvga
Those who stuck at the boot screen, suspect that it is not properly install.
Only way out is hard reset, you will lose everything if you do not have the habit of backup.
You need to copy the *.96.* files into Windows directory. Think Windows hang when seaching for this files.
yezzer said:
Hi all,
First post and all that, so hi! I've been lurking for a few days, but thought i'd post this as a) I might be doing something wrong, and b) if i'm not, it might help someone..
Basically, I installed ozVGA last night, and it turned my exec into a nice-looking, albeit ineffective doorstop.
I may have done this completely wrong, let me know if i did, as i really would like a 640x480 res
This is what i did:
1. I had upgraded my exec to the latest ROM released by o2.
2. I downloaded ozVGA from http://oz.sciox.org/
3. I followed the instructions on the above URL.
a) "unzip this file VgaRes.zip and put its contents to the \windows directory"
b) After that you will need to unzip this file OzVGA053.zip and place OzVGA.exe file wherever you want on your PDA
4. I launched ozVGA
5. I pressed the ozVGA button, it rebooted, the o2 bubbles screen with the red writing stating the ROM versions etc. appeared, and the SELECT and EXIT buttons were visible at the bottom. These were in the 640x480 resolution! Yey!
6. But...it stayed on that screen for a long, long time. It would not progress from that screen no matter what I tried, or how long i waited.
7. in the end, i had to do a factory reset, then install the new o2 rom again.
So... did i do something wrong :S I hope i did - as i would really like to have my exec in 640x480!
Cheers for any help
Click to expand...
Click to collapse
I see your post is sent WELL after I've published the tutorial on all these questions (see http://www.pocketpcmag.com/blogs/index.php?blog=3&p=1197&more=1&c=1&tb=1&pb=1 ). Please make sure you follow my latest articles; they are all cross-posted to the General forum here at XDA-Dev.
Menneisyys said:
I see your post is sent WELL after I've published the tutorial on all these questions (see http://www.pocketpcmag.com/blogs/index.php?blog=3&p=1197&more=1&c=1&tb=1&pb=1 ). Please make sure you follow my latest articles; they are all cross-posted to the General forum here at XDA-Dev.
Click to expand...
Click to collapse
Is he supposed to apologize for not following your articles and having the nerve to ask questions? Get off your high horse, seriously.
OzVGA v0.53
Noting the cumbersome method of installing/uninstalling OzVGA - I just decided to make a CAB Installer from the resources listed in this thread.
Also, given the fact that http://oz.sciox.org seems to be offline or maybe defaced, the attached archive might become even more relevant.
The attachment, OzVGA v0.53.zip, contains 2 CAB files:
1. OzVGA + DLLs
2. SdkCerts for DLLs
It's advisable to run the CABs in the order above.
Hi there,
after flashing my Universal with the latest i-mate ROM (thanks to the forum for all the information that I found here) my beloved Opera browser is unusable since it seems to have replaced the default font with Windows Dingbats
Pretty hard to read
Does anyone know where the relevant entries regarding the used font are hidden?
Thanks for all input,
Manuel
u can read up my post on how to solve this problem
Thanks for the quick help, but it doesnt work for me... I copied a Arial.ttf to windows folder (tried both on Storage card a root)...still the ugly symbols...
For future desperados, here the link to vapors thread: http://forum.xda-developers.com/viewtopic.php?t=46825&highlight=opera
Edit: Funny, for me it works, when I copy arial.ttf to the fonts folder
hmmm i guess it depends on ur device then though it didnt work for me when i tranfered to fonts folder. well glad it helped u one way or the other
vapor said:
u can read up my post on how to solve this problem
Click to expand...
Click to collapse
Where is that?
Here
http://forum.xda-developers.com/viewtopic.php?t=46825&highlight=
Your fix resolved my problem with the font. I copied the Ariel font to the \windows folder; I launched Opera and saw no change. I reset my device and re-launched Opera and it worked. Thanks!
My Opera install says it will expire on May 1st. Do you have a fix for that to extend the time period? I really don't like uninstalling/reinstalling apps on my Pocket PC.
vezer said:
Your fix resolved my problem with the font. I copied the Ariel font to the \windows folder; I launched Opera and saw no change. I reset my device and re-launched Opera and it worked. Thanks!
My Opera install says it will expire on May 1st. Do you have a fix for that to extend the time period? I really don't like uninstalling/reinstalling apps on my Pocket PC.
Click to expand...
Click to collapse
It's June 1st.
Check here.
Cheers
hrb
http://www.opera.com/products/mobile/products/winmobileppc/
My bad, you are right it is June 1st. Is there any way I can extend that time without having to install a new version?
vezer said:
My bad, you are right it is June 1st. Is there any way I can extend that time without having to install a new version?
Click to expand...
Click to collapse
apparently, there is no new version available .... possibly on June 1st Opera is either to launch new beta or fully-fledged and commercial product