Went through all of the GPS settings in Bing and none worked. Google maps worked off the bat. Com0 4800 baud. I used Sprite Backup to merge @ level 1 and everything seems be working fine. My main memory is still low, I may hard reset and try installing things from fresh to see if that helps at all.
I know the FAQs for the official ROM state that it does not support 64bit. However, both my laptop and desktop are Vista 64bit. Does anyone know of a way to install the ROM on Vista 64bit? Some special setting in Vista, or some free virtualization software, or something?
I know the FAQs for the official ROM state that it does not support 64bit. However, both my laptop and desktop are Vista 64bit. Does anyone know of a way to install the ROM on Vista 64bit? Some special setting in Vista, or some free virtualization software, or something?
Thanks
The funny thing is that I upgraded to Adrynalyne's v1.7 ROM (at least) using Windows 7 RC 64-bit on my new Dell XPS 1340 AFTER my 32-bit HP-Laptop died. So the UMDL Loader with the LEAKED ROM works with 64-bit but the OFFICIAL ROM loader does not?!?! What ingenious programming!
So, Archi, shall we flip a coin and see who gets to try 64-bit first? (I'd like to go for one of Adrynalyne's cooked ROM's on top of CF03.
Like many others, I gave up on downloading new ROM from official site and went to Megasomethingorother and downloaded it in 10 minutes. The new flash went as advertised. My only problem was that once complete I could only get ActiveSync to connect as Guest. Spent a couple of hours hard resetting and removing/reloading AS until I googled a solution by connecting the device, changing the registry setting for ActiveSync for Guest Mode from 1 to 0 (how that changed is anyone's bet), the disconnecting and reconnecting. Everything works. Got the GPS working today in GglMap like the others by changing the phone setting for GPS location and resetting the GglMap option for GPS to COM8. Found 5 satellites in about 3 minutes (suggest you set the phone down so it doesn't move during the sat acquire.) I guess it was all worth the inconvenience.
I know the FAQs for the official ROM state that it does not support 64bit. However, both my laptop and desktop are Vista 64bit. Does anyone know of a way to install the ROM on Vista 64bit? Some special setting in Vista, or some free virtualization software, or something?
Thanks
I attempted to flash in xp and vista 32 using vmware and virtualbox (which is free and rocks) but the virtualized usb port could not be recognized by the installer, even though it was recognized by activesync and wmdc
So, Archi, shall we flip a coin and see who gets to try 64-bit first? (I'd like to go for one of Adrynalyne's cooked ROM's on top of CF03.
I am willing to give it a try but I am travelling today and won't have access to my computers for a while.
I am one of the holdouts who has not flashed any ROMs yet. Now that the official one has been released, I think I am going to flash one of the cooked ROMs based off the new one. Any recommendations on which are good?
I am willing to give it a try but I am travelling today and won't have access to my computers for a while.
I am one of the holdouts who has not flashed any ROMs yet. Now that the official one has been released, I think I am going to flash one of the cooked ROMs based off the new one. Any recommendations on which are good?
Hi, Archi
EDIT: This post claims "There are memory blocks that are not updated unless you flash verizons CF03 Image by using there (means: "their") tool."
It shouldn't be too hard to try the lot and see which one you like best - the hard thing is reinstalling apps if you can't restore from a backup - going from his v1.6 to v1.7 based on the leaked CC20, things were a bit messed up when I restored system settings from a backup. It would help if the ROM chefs gave a bit more advice on restoring vs clean installs.
Guess they get flashed over the base CF03 install and from Adrynalyne's advice, doesn't seem like it's a good idea to try to flash CF03 directly on a 64-bit system but rather use a work around.
__________________
-Jim-
Use every part of the buffalo - Brad Bird
Last edited by Jim Lewis : 07-17-2009 at 09:53 PM.
Reason: Retract 64-bit install suggestion for CF03
Guess they get flashed over the base CF03 install and from Adrynalyne's advice, doesn't seem like it's a good idea to try to flash CF03 directly on a 64-bit system but rather use a work around.
Actually, this download link, which I accessed from My Verizon account, doesn't saying ANYTHING about NOT using a 64-bit system. It just says use the right download for the right OS, Vista and XP versions. So I will follow it along and see what happens. Toodle-loo for now. CF03 or bricked?
I'm downloading it now. It says it'll delete all information off the phone, anyone know if this includes SD cards and/or the 8GB onboard or just the system storage?
Upgraded. It doesn't appear to have deleted anything off the memory card or the 8 GB onboard. I'm not having luck getting Garmin XT or Bing to find the GPS though. Is there a certain port I need to point Bing towards?
Tried com 8 on Bing, no luck. How do you change the phone setting from 911 only?
Quote:
Originally Posted by gangolfus
Anyone have an answer?
I think Dan12R answered his own question - the danger is that if you somehow brick your phone, you'll probably lose My Storage, too. So backup any important data whether in Main Memory or in My Storage, just in case....
Took me only about 8 minutes to download 120 Mb of the Vista Update tool at around 200 KB/sec. So the initial download frenzy must be cooling off a bit.
I think Dan12R answered his own question - the danger is that if you somehow brick your phone, you'll probably lose My Storage, too. So backup any important data whether in Main Memory or in My Storage, just in case....
Whoops, missed that.
Download was plenty fast for me.... ~500k/s took a couple of minutes to download.
Results of trying to run Vista Tool in 64-bit Win7 RC
Not playing by the book but just launching the supposed Vista Update Tool in 64-bit Win7 RC without my Omnia attached via USB to see what happens, I get a message that Active Sync v4.5 is not installed, please install it - whereas the TOOL instructions are all about WMDC v6.1 required? So maybe my "funny" OS has the tool looking for Activesync in XP? Next abortive attempt is to try to use 32-bit virtual XP VMware machine to see if that replicates smithsquared experience: http://pdaphonehome.com/forums/samsu...tml#post793418
(he had no luck with virtual machines)
__________________
-Jim-
Use every part of the buffalo - Brad Bird
Last edited by Jim Lewis : 07-17-2009 at 11:13 PM.
Not playing by the book but just launching the supposed Vista Update Tool in 64-bit Win7 RC without my Omnia attached via USB to see what happens, I get a message that Active Sync v4.5 is not installed, please install it - whereas the TOOL instructions are all about WMDC v6.1 required? So maybe my "funny" OS has the tool looking for Activesync in XP? Next abortive attempt is to try to use 32-bit virtual XP VMware machine to see if that replicates smithsquared experience: http://pdaphonehome.com/forums/samsu...tml#post793418
(he had no luck with virtual machines)
The problem with a VMware virtual XP machine, trying to use it as a 32-bit system running under a real 64-bit OS to install CF03, is that during the restart of the Omnia, the USB connection is lost back to the host (64-bit system) until the Omnia restarts and by the time the USB connection to the 32-bit virtual machine is re-established, the Omnia is already rebooting its old WM. If the USB connection were "permanently" attached to the VM, I think it would work.
I went to an old slow XP desktop machine since all other home machines are 64-bit. On my slow desktop, the Upgrade Tool had trouble finding the Omnia before the Omnia rebooted (I think I decided to cancel out the Upgrade Tool just as Tool finally started the download) so I entered the "Emergency Upgrade Mode" (pull cable, pull battery, reinstall battery, connect cable, click NEXT on Emergency Screen, turn Omnia on). The upgrade then appeared to successfully download but the update progress meter never moved beyond about 10% and I went about 25 minutes with the Omnia screen totally blank, almost 20 minutes beyond the expected time required for the upgrade. The phone back was hot from Processor activity. But since no progress on the meter, etc., I pulled the plug. Don't know if having a cooked ROM on the Omnia had anything to do with failure to progress thru the Update after the initial download. Be interested to hear how other people with cooked ROMs fare on the upgrade.
I went to an old slow XP desktop machine since all other home machines are 64-bit. On my slow desktop, the Upgrade Tool had trouble finding the Omnia before the Omnia rebooted (I think I decided to cancel out the Upgrade Tool just as Tool finally started the download) so I entered the "Emergency Upgrade Mode" (pull cable, pull battery, reinstall battery, connect cable, click NEXT on Emergency Screen, turn Omnia on). The upgrade then appeared to successfully download but the update progress meter never moved beyond about 10% and I went about 25 minutes with the Omnia screen totally blank, almost 20 minutes beyond the expected time required for the upgrade. The phone back was hot from processor activity. But since no progress on the meter, etc., I pulled the plug. Don't know if having a cooked ROM on the Omnia had anything to do with failure to progress thru the Update after the initial download. Be interested to hear how other people with cooked ROMs fare on the upgrade.
To answer your query about other's experience upgrading, I can report a successful upgrade while using a 64-bit Vista notebook. I was at Adryn's 6.5 4.0.1. I did download the CF03.img file as Adryn mentioned. I used the Unified Image button in UDML for CF03. Then I flashed Adryn's 6.5 1.0 ROM on top of CF03.
I used Sashimi for the first time to help re-install all my cabs. I still have some work to do in Sashimi to handle all the various settings, registrations, and such that are the real pain in reinstallation.
To answer your query about other's experience upgrading, I can report a successful upgrade while using a 64-bit Vista notebook. I was at Adryn's 6.5 4.0.1. I did download the CF03.img file as Adryn mentioned. I used the Unified Image button in UDML for CF03. Then I flashed Adryn's 6.5 1.0 ROM on top of CF03.
I used Sashimi for the first time to help re-install all my cabs. I still have some work to do in Sashimi to handle all the various settings, registrations, and such that are the real pain in reinstallation.
Thanks, Jon. The thing most important to know is if you have a cooked ROM, is it safe to use the Verizon tool on your device and would there be any possible difference in updating from different cooked ROMs? This point of discussion came up with the CC20 LEAKED ROM, whether it might interfere with the official update, and it was said then that, although the updater might check the installed ROM, it virtually always just successfully overwrote what was already on the phone. Just wondering what the experience is of people using the official Verizon tool to update on a 32-bit system if they have a cooked ROM. Adrynalyne's advice seemed to be "here's what to do if you have a 64-bit system," not, "here's what you have to do with a cooked ROM...."
__________________
-Jim-
Use every part of the buffalo - Brad Bird
Last edited by Jim Lewis : 07-18-2009 at 11:44 AM.
Login
Panel
