yashsingh1/xdaforums huggingface dataset:
[Touch CDMA Windows Mobile ROM Development] tempests:
If you have not done so already, search for and download your carrier's stock ROM.

Re-flash the phone back that stock ROM. I suggest flashing 2 or 3 times, to make sure you have cleaned out any random code.

Then flash your phone to the latest ROM.

It would also be nice if you could tell us your carrier and all the procedures you have done so far.

The following statement is directed to all that are having problems flashing their phones and it is not meant to humiliate or belittle anyone:

Flashing your Vogue is really a very simple procedure. If the directions are followed, you will be successful. If you take shortcuts, because you are lazy, or don't believe you should have to do something multiple times, or the last time you flashed you didn't have to do all that stupid stuff so why do it now, YOU WILL INCREASE YOUR CHANCES OF HAVING A BAD FLASH.

So my suggestion is simple:

Follow the proven method and Do Not take any shortcuts and you have a 99% chance of success. Be stubborn and you will have a 50% chance of success.
[Touch CDMA Windows Mobile ROM Development] wud_e:
Hey Guys thanks for the Responses. I am on Sprint and Flashed to WinMo 6.5 V16. If I take the card out before the soft rest or pulling the battery out then the card is safe. If I leave it in then not only does the device get rest but the card as well.

I have flashed to the stock Sprint ROM 6.1 ROM form the HTC website a few times and then loaded the new NFSFAN 6.5 ROM. Just when I think I am passed the hump it surprises me and the phone resets again. I've tried this about 10 times already. I also do a Hard Reset after and let the Provision run before I start normal use. Sounds like it could just be my device. I've flashed Plenty of ROMs to my phone with no problems though.
[Touch CDMA Windows Mobile ROM Development] revcp:
Beautiful! Thanks so much. Before I got your post I muddled through to get the rom on by doubleclicking on the vogue unlocker exe. That did the trick. My phone went very smoothly. My wife's, however, has been a challenge. I got data connection right away on mine, but I'm trying your fix on hers and crossing my fingers!
[Touch CDMA Windows Mobile ROM Development] revcp:
Worked! Kudos!
[Touch CDMA Windows Mobile ROM Development] tempests:
After you flash successfully and for a while have no problem, are you then installing any 3rd party software?
[Touch CDMA Windows Mobile ROM Development] wud_e:
Sometimes I did and sometimes I didn't.
[Touch CDMA Windows Mobile ROM Development] brett_bates:
I've had a similar problem in that when I use the Windows Default lock, every few days I get the unlock screen, but none of my button presses register. It then does a hard reset and my card is wiped (unless I remove it before the reset occurs). I seem to recall the unlock screen being partially hidden as well.

I have to have a lock because it is required by my work's Exchange service for me to sync. Switching the lock to use Windows Classic lock resolved it. I even tested by going back to Windows Default lock and my phone reset the same day. Set the lock back to Classic and haven't had issues since.

Not sure if it is the same issue as yours, but it sounds similar...Exchange sync with special security update and Windows Default lock are what cause it for me, but at least I have a workaround.
[Touch CDMA Windows Mobile ROM Development] proelin:
Mine just did it again as well. I'll try the classic lock and see if that helps. (if I can find it.)
[Touch CDMA Windows Mobile ROM Development] tempests:
look under start / settings / lock / display you have 2 choices windows default and classic
[Touch CDMA Windows Mobile ROM Development] NFSFAN:
*Fixed ClearStorage not opening

*Fixed Manila2D theme layout

*Removed Operator & MyFaves option from Manila2D Customizer

*Cleaned up registry

*Removed Location AGPS Tab (not compatible with Vogue driver)

*Updated Display Driver, BT HeadSet Driver, Keyboard Driver

*Updated Manila2D Customizer

*Updated SYS lang files (20765 build clean, should fix a few issues)

*Patched AudioManager to show in TaskManager (Added option in Advanced Config to Hide as well)
[Touch CDMA Windows Mobile ROM Development] NFSFAN:
What format is this file in?
[Touch CDMA Windows Mobile ROM Development] derekwilkinson:
Does it open on your computer?
[Touch CDMA Windows Mobile ROM Development] derekwilkinson:
Sounds nice, especially the patched AudioManager. And about the AGPS tab, I kind of thought it didn't work right, it didn't seem to be speeding up GPS at all.

Is this going to be public testing or private?
[Touch CDMA Windows Mobile ROM Development] NFSFAN:
You have to PM me if you want to test. The AGPS tab wasn't meant to speed up GPS at all. All it did was check if it was connected to a server. I removed it because it didn't work, since our drivers don't support a server url.
[Touch CDMA Windows Mobile ROM Development] xxmillertimexx:
I was just wondering...what program is it that makes the screen vibrate with taps? Is it a program?
[Touch CDMA Windows Mobile ROM Development] c_swin:
start>settings>system tab>touch response settings.

when y'all get these new roms do you not look around and check out whats new????
[Touch CDMA Windows Mobile ROM Development] 4thought:
Problems flashing 1.27

I hope its ok to post this here. After flashing a Bell Touch, I can't get past the Bell blue screen. Here's what I did:

1. Followed the imCoke unlock procedure. Confirm ok since I can see SPL-2.31 CoKe on my tri-colour bootloader screen

2. Eventually booted back to the standard Bell ROM

3. Ran NFSFAN's ROM update. Here's where I screwed up. I didn't load a new radio. Instructions are all over the place on the web and I missed this part.

So now I've tried loading the Tital radio 3.42.50 .nbh from the SD card using the power/camera/reset procedure. I get a "loading" white screen so something is happening. Still boot to the blue Bell screen and no more.

I tried also re-loading NFSFAN's ROM .nbh from the Sd card, Bell's standard ROM, no luck.

So since I can get to bootloader and see CoKe 2.31, can anyone give me steps to either get back to Bell's ROM or over te NFSFAN's? Hopefully I haven't totally screwed this up. Thanks ... Pete
[Touch CDMA Windows Mobile ROM Development] gt!:
While connected to your computer (via the usb cable) you should be able to flash the latest Bell rom while at the bootloader screen.

-GT
[Touch CDMA Windows Mobile ROM Development] NFSFAN:
Why would you load a titan radio on the vogue?
[Touch CDMA Windows Mobile ROM Development] 4thought:
Probably because I don't know what I'm doing!
[Touch CDMA Windows Mobile ROM Development] derekwilkinson:
Oh sorry, I misunderstood what it was I suppose. :o
[Touch CDMA Windows Mobile ROM Development] jaytavarez91:
Do you think you can add the new Firefox browser to the final build? Would be pretty cool.
[Touch CDMA Windows Mobile ROM Development] NFSFAN:
I prefer to leave that up to the user to install.
[Touch CDMA Windows Mobile ROM Development] SL:
the file is in xls format.

It opens fine on the desktop.

mobile office just wont recognise it in recent build. It previous build the same file would open when clicked.
[Touch CDMA Windows Mobile ROM Development] NFSFAN:
Previous build being?
[Touch CDMA Windows Mobile ROM Development] MXQBLGH:
NFSFAN or anyone,

Hi, I'm sorry if this is considered off topic but since you've done a lot of customizing with your ROM I was wondering if you could help me with something.

Do you know of there being any limit to the 'maximum' number of SMS you can have in a threaded conversation? Reason being, I text with my gf a lot since last October and since last week, all the old messages are gone, and only the messages starting last week appear. My other friends whom I don't text as much have all msgs since the beginning.

I know the messages are in there, because if I turn off threaded SMS from the manila2d customizer, I can see ALL the messages since oct. It's just the threading for my gf's convo seems to ''reset" starting last week....did I hit a limit or something? Also...it seems that PIM Backup restored all convos fine (in threaded view), but my gf's texts from last week onwards don't appear in the threading, only my own. But all NEW texts from her appear in there and are threaded properly....

thought you might know since you've put in the 'sms settings' under settings etc.

thanks!
[Touch CDMA Windows Mobile ROM Development] MXQBLGH:
Also, is there a trick to setting Opera as the default browser? It's worked before magically by itself when I installed it, but now with the latest build that I installed, PIE is now the default browser.

thanks
[Touch CDMA Windows Mobile ROM Development] Detroit_Doug:
Got to the M2D Customizer within the settings area and browse to opera as default browser (its under the internet tab in M2d)

Detroit Doug
[Touch CDMA Windows Mobile ROM Development] ludester:
use m2d customizer and set the default browser.
[Touch CDMA Windows Mobile ROM Development] gjbnh:
Could I make a request? Are you using the SAME card, or have you tried different cards? And have you run a "chkdsk" on the card from your computer or laptop? I had a problem running Android UNTIL I checked the card; it had file structure errors I was not aware of. Just asking for the information. Your the first person I've heard of with this prolem. (the make and size of the card too please if it is just the one card) Thanks
[Touch CDMA Windows Mobile ROM Development] Evan.Anderson:
Another way to lock, no app needed

I've remembered an app that i used to use on my wizard called Long Press End Key. I've found something similar, if not the same app, under Start>Settings>Personal>Buttons, Select the End Key Tab, Under Automatically Execute the selected action: Select Lock Device. With this you can press and hold the end key(2 seconds) while at the today screen and wammo locked, then just press power...

Extra settings that I use:

Start>Settings>Lock: Uncheck, prompt if phone unused, so no pin is required.

Start>Settings>System>Key Lock: Select, Lock all buttons except Power button, so you can hit power after locking with long press end key.
[Touch CDMA Windows Mobile ROM Development] caquito07:
Hi everyone,

I'm a noobie on upgrading WM Phones, so I have a few questions.

First of all, I have a Sprint Touch that was flashed (configured) for MetroPCS, it's working fine. Questions:

1- How can I know if my phone is already unlocked? Will the phone get re-locked after a Hard reset?

2- What are the steps to upgrading the phone to wm6.5 NFSFAN V16?

3- Will MetroPCS internet work?

4- Will the GPS work?

5- Can I roll back to WM6.1 Original Sprint ROM?

Thanks,

Phone info:

ROM version: 3.03.651.4

Radio version: 3.42.30

PRI version: 2.04_003
[Touch CDMA Windows Mobile ROM Development] tempests:
Go here:

http://xdaforums.com/showthread.php?t=508544

It should answer most of your questions.
[Touch CDMA Windows Mobile ROM Development] caquito07:
Thanks.... going to
[Touch CDMA Windows Mobile ROM Development] caquito07:
Hey, I succesfully upgrade my phone to WM6.5, just one problem, I'm on MetroPCS and I have no Internet. I ran the MetroPCS carrier cab, but it's not connecting.

I remember something about Simple IP, but the config is change going in ##778# menu and the phone is not accepting that menu.

Help please!
[Touch CDMA Windows Mobile ROM Development] eruisi:
Reminder can not pop up

I can see it in notification list but the message can not pop up (either automatically or tap it in notification list).

I am using NFSFAN's WM6.5 ROM with Windows Mobile Shell 3.01

Please help me out!
[Touch CDMA Windows Mobile ROM Development] tempests:
Uninstall Windows Mobile Shell 3.01 and see if the problem is still there.

Also, since this forum is for NFSFAN's ROM support, check for a support forum for Windows Mobile Shell.
[Touch CDMA Windows Mobile ROM Development] caquito07:
I fixed it!!!! Install the NFSFAN Vogue CDMA Dialer and it will accept the ##codes#, after that dial ##778#, edit and enter your SPC, then is just going to Mobile IP Settings and changing from Mobile IP only yo Simple IP only.
[Touch CDMA Windows Mobile ROM Development] caquito07:
Running WM6.5 after the upgrade when I dial ##diag# (##3424#), the phone is now installed as a Palm, and I can't configure the phone settings on QPST. Any idea on how to do it now???
[Touch CDMA Windows Mobile ROM Development] kuluminati:
tempests you are quick on the draw with the responses. Nice work!
[Touch CDMA Windows Mobile ROM Development] bobzero:
Not ROM related, but still awesome, google street view and traffic layer are finally working as of today in Toronto! woohoo!

Any the traffic layer seems to have more coverage than Bing.
[Touch CDMA Windows Mobile ROM Development] proelin:
Found it. So far so good. But sometimes it would last up to 5 days. Thanks for the info!
[Touch CDMA Windows Mobile ROM Development] austinite007:
I had a similar experience a month ago. I got mine to work but not my mother's data connection on her new Vogue. I finally discovered that "IOTA" (also known as a process for provisioning data power vision services on Sprint) was not running on NFSFAN's ROM Installs. It was a brand new phone and it did not have all of the data connection settings that are defined during this process. After careful troubleshooting, I discovered that if you wait a few minutes after the WM6.1 Stock ROM install is complete, the IOTA process runs and captures all of the necessary data connection configuration settings without having to know the dial codes and how to edit multiple fields to do this process manually. After the IOTA icon (at the very top of the screen) disappeared, I opened Internet Explorer Mobile while still in the Stock ROM to confirm that the data connection was good, I got a few pop up messages that stated something like "Provisioning Data/Vision Services" for about 10-20 seconds, after that the data connection was working. I then followed the recommended procedures of flashing NFSFAN's ROM 3 times and it worked fine after that. This website explains some detail as to what IOTA stands for and does if you are curious: http://pdaphonehome.com/forums/ppc-6700-xv6700/76392-iota-what-about.html
[Touch CDMA Windows Mobile ROM Development] Nick N:
Does anyone else check the Vogue upgrading forum multiple times per day looking for *Updated: October XXth* NFSFAN's Custom WM6.1 & WM6.5 (pg.10XX) ROMs ??? :D
[Touch CDMA Windows Mobile ROM Development] mike21pr:
every chance i get...lol

its not healthy, i hope its released soon so i can get on with my life hahaha
[Touch CDMA Windows Mobile ROM Development] amad99:
LOL....this is soo true... NFSFAN needs twitter so he tweet us everytime there is an update...jokes!
[Touch CDMA Windows Mobile ROM Development] acdc_rulz:
ICS not working in NFSFan WM6.5 V13-->V16

Hello,

I recently upgraded my HTC XV6900 to NFSFan's v16 ROM(was running v8 before). Everything went smoothly with the upgrade until I noticed that my ICS(Internet Connection Sharing) stopped working - (the Connect button would be greyed out) when I attempted to establish a USB ICS connection. I searched this thread for similar posts and found several messages from users complaining of the same issue. The common thread between all of these and my issue is that we installed either the MMS ArcSoft from here or the Verizon Carrier cab here - both of which are referenced in this ROM's FAQ.

I have tested this scenario repeatedly (fresh install of the ROM, testing ICS (works), then installing the carrier cab or Arcsoft MMS software package and after installing these cabs and soft resetting the phone, I am no longer able to click on the Connect button in the ICS menu. MMS works following the FAQ steps to install/configure it but ICS is more important... Also, uninstalling either cab still does not bring back my ICS Connect!

I searched as well for any registry tweaks to try and fix this problem but could not find any posts on this or the PPCGeeks forums. For now, I will leave V16 on my phone until a fix is found or I hear back from you all.

Here are some specs. on my XV6900:

Phone: HTC XV6900

Radio version: 3.37.78 (upgraded using the MR1 Verizon stock ROM)

Carrier: Verizon

Thanks...and has been said many times before - great ROM NFSFan!
[Touch CDMA Windows Mobile ROM Development] acdc_rulz:
I think I found a fix to the ICS problem!

Well, I couldn't leave this issue well enough alone and I went back to PPCgeeks - see the post here. In the post, Hucklepig suggested deleting the following entries in order to enable the Connect button in the ICS application. I tested making this change BEFORE installing the Arcsoft MMS cab and it did not have any effect - I was still able to connect w/out issue using ICS.

I then deleted these 2 entries AFTER installing the Arcsoft MMS cab and soft reset my phone. When my phone came back up, I connected the USB cable and started a Internet Sharing connection tapping on the Connect button! However, in the ICS window, I now have 2 dropdowns - PC Connection and Network Connection. If I don't edit the Connections-->Data Connection entry, I only get 1 drop down option under Network Connection - Data Connection. If I follow the FAQ and add my xxxxx@vzw3g.com for the connections username/password then this creates another option - Phone As Modem.

If your Connect button under ICS is greyed out and you have already installed the Arcsoft MMS or the MMS cab from the FAQ, delete the following entries using PHM RegEdit (under Start-->System Tools):

[HKEY_CURRENT_USER\Software\Microsoft\InternetSharing]

Delete The Following Key: "LastCellConnection"

[HKEY_LOCAL_MACHINE\Comm\InternetSharing\Settings]

Delete The Following Key: "ForceCellConnection"

Soft-reset your phone and check ICS again after reboot - you will now be able to click on Connect button in ICS (you should also see a Network Connection dropdown in the ICS window). I checked my registry and the above entries reappeared after I tapped Connect and their REG KEY Value was populated with "Data Connection" (the option I selected in the Network Connection dropdown in ICS).

Codybear - I found this post from you awhile back asking about what registry values to change...here. Is this the same issue that was raised then and if so, maybe this can be added to the FAQ?

Hope this helps anyone upgrading to the current revs. of NFSFan's WM6.5 ROM!
[Touch CDMA Windows Mobile ROM Development] Jacklad:
ICS still not working -

Did you follow the NFSFAN instructions regarding using Advanced Config. to import the indicated provisioning file after installing the MMS cab? I've found that if you skip this step, ICS will not work - try that before making any possibly unecessary registry changes -
[Touch CDMA Windows Mobile ROM Development] alogreco:
From Backlight settings uncheck the "On external power - Turn off device if not used for:"
[Touch CDMA Windows Mobile ROM Development] bobzero:
has anyone tried out this new version of windows live?

Windows Live Mobile v10.7.0057.0801

http://forum.ppcwarez.org/viewtopic.php?f=41&t=82627

if it's working well, NFSFAN might update it in v17
[Touch CDMA Windows Mobile ROM Development] acdc_rulz:
Hey Jacklad - thank you for that suggestion! I went back and re-installed the V16 ROM fresh and followed the MMS HOTFIX instructions on NFSFan's ROM page. In short that worked and I am able to use ICS again after installing the MMS cab. The hotfix steps are completely different from the FAQ steps here. Following the FAQ's steps for MMS on Verizon, I completely hosed my ICS app. I posted a message on the FAQ for Codybear or someone else to fix this(hopefully save some grief for others). Thanks!
[Touch CDMA Windows Mobile ROM Development] amad99:
Yeah...it's alright. MyPhone and Marketplace need to be updated also for the next release.
[Touch CDMA Windows Mobile ROM Development] slow88lx:
Why can't we get the new keyboard in addition to the only ones in v17?
[Touch CDMA Windows Mobile ROM Development] Jacklad:
Cool -glad it helped - I figured that out after doing multiple re-installs and forgetting that final step -
[Touch CDMA Windows Mobile ROM Development] slow88lx:
Good job guys. I had been using those other instructions and it was pissing me off that I couldn't use ICS. Thanks!
[Touch CDMA Windows Mobile ROM Development] NFSFAN:
V17 changelog (work in progress):

*Kitchen changed to platformrebuilder with my .bat scripts

*Updated to final WM6.5 21864 build (builds after will be designed on 6.5.1 branch and will be betas)

*Fixed headphone issue (this time it works properly no joke)

*Fixed blurry camera

*Fixed video recording issues (removed CIF & L modes)

*Optimized boot

*Optimized memory allocation

*Fixed date and time picker position in landscape + ported new version

*Added aGPS Confirmation -- 1.0.1918.3131

*Added HTC Geo Service -- 1.0.1919.1120

*Added Microsoft Facebook -- 1.0.0.7

*Added Manila2D Weather Cities Editor -- 2.1

*Added Marketplace

*Updated Google Maps -- 3.2.1.17

*Updated Adobe PDF -- 2.5.1.0.395886.05H

*Updated Boot Launcher -- 1.0.1918.1525

*Updated HTC Framework -- 1.1.1919.2728

*Updated Shared Resource -- 1.0.1919.2728

*Updated Manila 2D -- 2.0.1919.1432

*Updated AudioManager -- 2.2.1918.2329

*Updated Media Tool Kit -- 1.0.1918.2223

*Updated Random Access -- 4.1.1917.3928

*Updated RSS Hub -- 2.1.1.1101

*Updated Settings Improvement -- 1.0.1918.4129

*Updated Streaming Media -- 3.1.1918.3421

*Updated Task Manager -- 2.1.1918.3027

*Updated USB to PC Popup -- 2.3.1918.3029

*Updated Voice Recorder -- 1.10.1918.1619

*Updated Menu Enhancement -- 1.1.1919.1133

*Updated Email Setup Wizard -- 2.1.1919.1730

*Updated HTC Power -- 3.3.0.0

*Updated Windows Live

*Updated MyPhone

With V17, it will be a major release. I've done an entire kitchen overhaul, and switched to platform rebuilder, with my own scripts so I can still use the old kitchen layout. The advantages are better module relocation, and less stability issues. Below is a screen cap of the memory layout :)
[Touch CDMA Windows Mobile ROM Development] cbaty08:
AH! CAN't WAIT!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[Touch CDMA Windows Mobile ROM Development] :
So when can we expect this mighty mighty release
[Touch CDMA Windows Mobile ROM Development] 2002wrex:
can we get a teaser date or something?!?!?!?
[Touch CDMA Windows Mobile ROM Development] ludester:
holy **** batman, MASSIVE RELEASE!
[Touch CDMA Windows Mobile ROM Development] Nick N:
!!!

:eek::eek::eek:

Can't wait!

Noticed you just uploaded a new ROM for the CDMA Touch Pro... hope my wife likes 6.5 on hers...
[Touch CDMA Windows Mobile ROM Development] apurvjawle:
prob my 100th refresh to see if it changed from sept to oct :D cant wait!!
[Touch CDMA Windows Mobile ROM Development] mike21pr:
nice!!! cant wait. one question, why arent you using the mega's sip keyboard and sticking to the diamond one? the new one is much nicer and it also has a compact qwerty
[Touch CDMA Windows Mobile ROM Development] 2Sancho:
V17

Wasnt Manilla 2d Better when it was Black & White? I was able to easy read the little numbers even under sunlight. Now it almost gives me pink eye trying to read it.

Has any body found a fix for the QPST not connecting?
[Touch CDMA Windows Mobile ROM Development] acdc_rulz:
2Sancho,

I am having similar issues and I am running v16 of NFSFan's ROM! Whenever I connect my phone, ActiveSync kicks on even though I put the phone in DIAG mode with code 3724 using the built-in Phone Codes shortcut(under System Tools). I then launch QPST on my PC but my phone is not seen as an available port. Fortunately, I flashed and programmed the AGPS settings long before this current ROM so I don't need to get into QPST right now. Also, there is a 778 shortcut in the Phone Codes folder that if you launch that you can see many of the settings that can be modified in QPST though not the AGPS settings.
[Touch CDMA Windows Mobile ROM Development] NFSFAN:
No landscape support.
[Touch CDMA Windows Mobile ROM Development] NFSFAN:
QPST will be fixed in v17. I know its broken in v16.