yashsingh1/xdaforums huggingface dataset:
[Touch CDMA Windows Mobile ROM Development] egzthunder1:
You are correct. SuperCID is not needed if you are upgrading the radio via a stock rom update. If you flash a radio only, no hard reset is required. The radio is independent of the rom.
[Touch CDMA Windows Mobile ROM Development] scotttr:
I'm trying out 3.42.50 now.

I downloaded it from the file found here

It contains 3.42.30, 3.42.40 and 3.42.50

I flashed it via the memory card through the procedure here
[Touch CDMA Windows Mobile ROM Development] egzthunder1:
How is .50 working out for you? See any improvements (faster GPS lockon)?
[Touch CDMA Windows Mobile ROM Development] scotttr:
I just did it. I don't know if it is better or worse yet, I was only trying them to see if they improve reception over the stock Verizon 3.37.78 radio. My wifes phone is still on the stock rom so I'm checking mine vs hers.

I still have no GPS, so I don't know about lock speed. We are going to send my wifes phone in for one last warranty replacement for the housing cracking, so I am going to try a few more things on it before sending it back for the replacement to see if I can get the GPS working.
[Touch CDMA Windows Mobile ROM Development] rowehc:
How do you put your phone in bootloader?
[Touch CDMA Windows Mobile ROM Development] scotttr:
press and hold power and camera, then insert the stylus in reset hole for about a second
[Touch CDMA Windows Mobile ROM Development] blindfold king:
Trouble flashing NFSFan 6.5 1.00

Okay, so I got to the point where you open romupdateutility.exe in the NFSFan folder and followed the instructions and the load bar filled up and all that but when I disconnect (manually, pulled the chord) and do a hard reset, I get stuck at the VerizonWireless screen.

I'm using a Windows Vista 32-bit comp, and my phone is a Verizon XV6900

I tried running romupdateutility.exe multiple times with the same outcome. If it doesn't work do I need to do something before re-trying? I'm a super noob, and have no idea what I'm doing wrong, so any help is appreciated. Speak to me like I'm stupid, haha
[Touch CDMA Windows Mobile ROM Development] egzthunder1:
Did you follow the whole guide? If you are stuck at bootscreen (and you followed the unlocking procedure), it could mean that you did not let extbl run at the end of the unlock. If you did not unlock the device, the reason why you are stuck is because you flashed without unlocking.
[Touch CDMA Windows Mobile ROM Development] blindfold king:
hmmm, I did the unlocking part the way it said in the quote box in step 2 for windows vista users. followed the instructions, disconnected and reconnected when it said to, let it flash, disconnected and closed prompt. i don't think an exitbl showed up... what would it look like?
[Touch CDMA Windows Mobile ROM Development] egzthunder1:
It simply tells you in the command prompt that it is going to run it.
[Touch CDMA Windows Mobile ROM Development] blindfold king:
oh yeah, it told me that. said i could continue flashing with ctrl+c or i could shut down the prompt thing. i pressed ctrl+c and i don't remember what happened then, but the command window wasn't open long after that.

also, when i was flashing nfsfan, it only took like 3-4 minutes.
[Touch CDMA Windows Mobile ROM Development] devildog0729:
Default Fingerboard Keyboard and Soft Button Rotate Screen

Thunder and Esteemed Colleagues:

Is there anyway to set Finger keyboard as default input? Tried to use advance config...no luck, and is there a file to set rotate screen as a soft button? Thanks in advance for your help.
[Touch CDMA Windows Mobile ROM Development] egzthunder1:
Did you get it to work?
[Touch CDMA Windows Mobile ROM Development] egzthunder1:
Once you select it, it should remain as the default keyboard. I don't believe that it should be jumping back to the stock keyboard...

As far as the soft button, there is an app (which I believe I normally set in my roms (for which I cannot remember its name) that is used to remap the soft buttons. I will try to find out and let you know.
[Touch CDMA Windows Mobile ROM Development] blindfold king:
nah, i flashed a verizon wm6.1 os on it and at first it wouldn't let me make calls or send my texts, but a day later it decided to let me do that. but all my calls are roaming... and i think i might be getting data charges or some such **** for texts. i'm going to call to find out if i'm getting extraneous charges or anything.

one other thing. when i did the unlock process and it ran exitbl i kept it connected and went through the set-up process (for my original os, wm6) on the phone before running bootloader and trying to flash anything. should i have

not

set it up? i'm not sure where things went wrong but i guess there's a few places since i don't exactly know what i'm doing, haha

i also think i may have gotten confused at step 3 parts 1 and 2. what exactly was i supposed to do with VogueRUU.zip if I already had the NFSFan folder? I'm pretty sure I still ran the RUU you attached to the step 3 post, as well as NFSFan after that.
[Touch CDMA Windows Mobile ROM Development] blindfold king:
Upon doing some reading, I hear that "letting customizations run" is something I SHOULDN'T do on Verizon. When my phone re-set after the unlocking process, I went through set-up and at the end it did customization. Should I do the entire process again without doing anything after it re-sets? Just go straight to bootloader?

And I'm still curious about VogueRUU.zip and the RUU in the NFSFan folder (last 'paragraph' in my previous post).
[Touch CDMA Windows Mobile ROM Development] egzthunder1:
If you read my post with the RUU, you will see that I wrote that I posted it just in casce it was needed. Many chefs upload the rom only (nbh file) as opposed to a full upgrade package (with the RUU).

You should try again from scratch and, don't let customizations run.
[Touch CDMA Windows Mobile ROM Development] blindfold king:
Ah, okay. Yeah sorry, I didn't know what nbh files were so I ran that anyways thinking maybe it was necessary for me, haha. I'm really not familiar with much of the terminology so I was pretty confused the whole time but I think I'm getting a better understanding now. I got my phone fully operational again on wm6.1 but I think I'm going to try to put NFSFan's wm6.5 on again. If I do try again, I'll let you know how it goes. Thanks :)
[Touch CDMA Windows Mobile ROM Development] blindfold king:
All right, sorry for all the questions, but I've been going through the directions and taking notes so I know what I'm doing when I try it again, and while reading this and several other threads I got a better understanding, but still need to clear a few basic things up:

How can I tell if my phone is CDMA and not GSM? I have a Verizon XV6900. Pretty sure it's CDMA but just wanna confirm, as I'm not 100%.

Before re-trying the unlock process do I need to "re-lock" my phone with the 0.40 Unlocker and a stock Verizon ROM?

My Radio is 3.37.78 ... Is that a GPS Radio? (Asking because in NFSFan's thread about his ROM it says you need a GPS Radio to use it).

Again, sorry for all my noob questions, but I really appreciate any help I can get in knowing what I'm doing.
[Touch CDMA Windows Mobile ROM Development] egzthunder1:
Your phone is CDMA as long as it doesn't have a SIM card on it. Verizon and Sprint are CDMA networks, so don't worry...

It isn't really necessary to re-lock prior to retrying to unlock. You can simply run the unlocking tool again. My recommendation (to avoid any possible issues)... use an XP (32 bit) machine.

Any radio above 3.xx.xxx is GPS enabled, so you are ok with 3.37

I hope this helps.
[Touch CDMA Windows Mobile ROM Development] scotttr:
I screwed it up my first try too. First try *228 option 1, for me that was unsuccessful. To get rid of the roaming I had to change my Home SID to the right one. All that extra flashing must have changed mine.

dial ##778 Send from the default keypad(##778# from NFSFan's ROM)

choose edit:

type 000000(6 zeros)(for verizon, other carriers may be different)

OK

View Info

Home SID/Home NID

Home SID/NID #1

Menu

Edit

enter the right SID number in the first box(The Denver area is 58)

verify the NID number

OK

then reset the phone
[Touch CDMA Windows Mobile ROM Development] egzthunder1:
Thanks for that scotttr. You actually gave me a pretty good idea, which you will see shortly (hopefully as a sticky :))
[Touch CDMA Windows Mobile ROM Development] novafreak69:
Still No GPS....

I have a fresh install of NFSFAN's WM6.1 V1.15 Verizon rom radio-3.42.40 And I still cannot get any GPS locks... can some one give me a shove in the right direction to either troubleshoot this or fix it?
[Touch CDMA Windows Mobile ROM Development] egzthunder1:
Try this and see if it works...
[Touch CDMA Windows Mobile ROM Development] blindfold king:
Okay, I've got my phone working with nfsfan's wm6.5 1.00 but I had a friend (who knows what he's doing) do it via memory card, so I didn't get to test it out myself and find out what problems I may have had when I failed. One thing is, I couldn't get the MMS fix to work (verizon problem). I really want to try to work on this... Getting the hang of customizing with .cab files. I wanna find some more stuff to get on there. It's pretty cool. I really like 6.5 :)

Any verizon people who put this rom on their phones have any advice about fixing MMS? My friend tried two different ways that are listed on threads on this site. Didn't get anywhere.
[Touch CDMA Windows Mobile ROM Development] scotttr:
This is how I got my GPS working on Verizon.thread here.

I had trouble with the downloads on that page so I put them all here.

This was the third Vogue I tried for GPS on.

On the first phone I followed all the steps in the tutorial, 2.31, vogueruu, nfsfan rom, alltel rom, superCID, bell rom for the radio, nfsfan rom etc... That phone lost most of it's settings on the ##778 menu and will not hold the settings through a hard reset. *228 is always unsuccesful, I had to call Verizon tech support to get it working again.

For phone number two all I did was unlock it with the 2.31 unlocker and load NFSFan's rom, then flashed the radio via the sd card. It will program on on *228 but GPS does not work.

On the third phone I followed the procedure I linked to above. *228 works and both GPS and aGPS work.:D I upgraded the radio with the sd card again, it took a couple of tries I had to reformat the card again to get it to work. Too bad I get to relock it and put the stock verizon rom back on when it's replacement gets here next week.

I'm going to try this on phone #2 at some point, I don't know if the wife wants it on #3s replacement.
[Touch CDMA Windows Mobile ROM Development] scotttr:
Follow the steps in NFSFANs thread.

I did this without deleting the connections and it has worked, repeatedly.

does your internet work? no internet = no mms
[Touch CDMA Windows Mobile ROM Development] blindfold king:
My internet does not work (I'm pretty sure it doesn't... How can I confirm this?). Any idea what I need to do to get my internet working?
[Touch CDMA Windows Mobile ROM Development] scotttr:
open ie or opera and go to a web page to see if it works.
[Touch CDMA Windows Mobile ROM Development] blindfold king:
Okay, yeah. I tried using IE and when it tried to go to a page it gave me an error message like this:

Cannot Connect.

Dialed: #777.

Your username or password is wrong. To check your connection settings and change them if needed, tap Settings. If the problems continues, turn the device off and try again.
[Touch CDMA Windows Mobile ROM Development] scotttr:
did your friend just flash it or did he go through ALL of the steps in the ROM thread?(dialer, mms cab(and it's procedure I quoted earlier), provisioning, etc...)

I would try to reinstall the cabs, make sure you follow the instructions on what to do after installing the mms cab, maybe he missed the import and soft reset steps.

check your connections(start,settings,connections, manage existing connections, edit) make sure you have your user name and password set. Maybe security and m.ip default profile in the epst menu.

Or, call your provider, tell them you did a hard reset and they can walk you through it.
[Touch CDMA Windows Mobile ROM Development] blindfold king:
i put a dialer on, and we tried mms but couldn't get it to work (and ended up having to re-flash, and fix things agaaaain with customer service and ##778# [i seriously need to write down the correct info from that so i don't have to keep calling]), and we skipped a provisioning .cab because he said we wouldn't need it.

i tried setting my username/password in connection settings but it still tells me it's wrong when i try to connect to the data network, so i'm gonna see if verizon can help me with that and when data's working i'll try the mms .cab again.

should i put a provisioning .cab on anyways even though i'm already on the verizon network?

ps. i'm so lost on all of this, so thanks for all the advise! once i get mms working again, i'll be extremely happy with this new os (i'm already pretty excited about it. it's my first time using a custom rom).
[Touch CDMA Windows Mobile ROM Development] scotttr:
install the provisioning cab.

retry the mms one. it has to work. did you import the file and reset?
[Touch CDMA Windows Mobile ROM Development] bill2u:
vogue sd flash

Hy I have Vin23506 v4 in my vogue nice room I been looking in a step by step to flash a room from sd card can you help me any information will be appreciated I am trying to flash Vin28014 thanks in advance :confused:
[Touch CDMA Windows Mobile ROM Development] vaporize88:
HELP

Help, I just went through step by step, step 1, step2, and step3

After it flashes the ROM 100% and reboots itself. I disconnect it and hard reset the device as instructions.

It shows the first HTC screen and then it keeps on stuck at the blue Bell Screen.

I have tried to hard reset it a few times and it does not do anything?

Any hints on what to do? I flashed it with the NSFFAN WM6.5 1.0 ROm
[Touch CDMA Windows Mobile ROM Development] egzthunder1:
grab a rom (nbh file) and rename it to voguimg.nbh and dump it in the root of the card (the card can't be larger than 2 GB and must be formatted to fat32). Go into bootloader and the upgrade process should start by itself. Good luck!
[Touch CDMA Windows Mobile ROM Development] egzthunder1:
That points to a faulty unlock. Repeat the unlock process again and this time make sure that titan_exitbl runs.
[Touch CDMA Windows Mobile ROM Development] CanadianTSi:
I'm having the Exact same problem, I know the Unlock worked because I see Coke MFG on the boot loader screen.
[Touch CDMA Windows Mobile ROM Development] egzthunder1:
If you don't let exitbl run, you will still see Coke under bootloader, but your rom will not start. Repeat the process one more time and make sure that you let exitbl run.
[Touch CDMA Windows Mobile ROM Development] CanadianTSi:
The Unlocker does not detect the phone anymore so it won't run.
[Touch CDMA Windows Mobile ROM Development] egzthunder1:
Sorry to be so blunt, but that doesn't make any sense. What do you mean that "the unlocker doesn't detect the phone"? Put the device in bootloader and run the app.
[Touch CDMA Windows Mobile ROM Development] jbenge308:
NFSFAN 6.5.1 Internet issues

So my friend unlocked and flashed my Touch with NFSFAN 6.5

Its awesome, but the internet will not connect, and thus... none of my programs will connect. weather, email, news, facebook... etc. etc.

what do i need to do to get my internet to connect?
[Touch CDMA Windows Mobile ROM Development] egzthunder1:
You have to install the carrier's provisioning cab for your carrier.
[Touch CDMA Windows Mobile ROM Development] codybear:
Hey, thanks for keeping up on a new FAQ.

I just didn't have time to redo it and keep it updated.

There's also tons of links to good threads in the other links section of my faq.

I recommend linking to it or maybe reposting them or something.

But nonetheless, great job bro.
[Touch CDMA Windows Mobile ROM Development] egzthunder1:
Honestly, if it wasn't for your guide, I would have not been able to even unlock my Vogue (well, probably I would have, but still I am being grateful, so take it as it is :D)

I usually update the first posts as I see fit, but I will certainly look for more interesting stuff in the other links in your thread. Thanks for all your hard work as well and good to have you back!
[Touch CDMA Windows Mobile ROM Development] billyh:
Locking

Hey egzthunder1,

My friend's Vogue started freezing all of the time, so I followed the directions in here and flashed it to Nfsfan's rom. It worked fine for a while but started freezing again. I just found out that she actually had a three year warranty on it, so I'd like to flash it to stock and see if they can fix it, or replace it.

I see on the first page you say to use the unlocked to flash the stock rom.

So, if I just flash the "Bell rom with radio 3.42.50" back onto the phone, they won't know it was tampered with?

Someone mentioned somewhere in here that the phone was still unlocked when they flashed to stock. Is this the case?

If they can't fix it, then I will come back and flash again!!

I'll send a few coffee's your way for sure if I can get this back to normal... actually I'll send em anyways for this awesome guide!

Thanks for the help.
[Touch CDMA Windows Mobile ROM Development] scotttr:
Run the .40 locker/unlocker then reflash with your carriers rom. The phone will be locked again.
[Touch CDMA Windows Mobile ROM Development] egzthunder1:
I will be looking forward to the coffee :D. As far as the re-locking procedure, scotttr is absolutely right. You will need to flash the .4 locker/unlocker since that one gets overwritten by stock once it is flashed. They normally should not be able to tell if the device was unlocked or not.
[Touch CDMA Windows Mobile ROM Development] jamsandwich:
I've had no luck doing this and I really don't know what the problem is.

Followed the instructions to a T, but the problem happens right after the unlocker appears to be flashing the ROM. After the RUU is done, the phone resets and I get the message (in the unlocking program) that I should be stuck on bootloader.

This has never worked. What happens, in fact, is the phone resets, I see Bell and HTC splash screens and it loads Windows Mobile.

I'm running Windows through my MacBook, so I thought maybe it was some sort of weird problem with the hardware. So I hauled out my old XP machine and tried it there, with the same results.

I was certain I saw the 2.31 bootloader screen at one point (perhaps when re-flashing to the Bell ROM?), but never have I gotten to the point where I've been able to/had to disable USB connections in ActiveSync. I mean, I can do it, but the phone isn't where it's supposed to be at that point.

Not really sure where this is going wrong.

About the only plus of this so far is that in the hours I've wasted on it, I've at least eradicated all traces of ZoneAlarm from my old PC, so it can now reliably get online. Downside is I was so determined to get the phone flashed that I forgot to record my contacts. My phone's not packed with them, but I'm going to have to call around for a couple of the numbers. Grr.

EDIT: Speaking of my certainty about seeing the bootloader screen, that would indicate the phone was unlocked, no? If so, surely I'd be able to test that theory somehow, right? (Without any considerable risk of bricking). I'd love to get running WM 6.5, but I'm just not convinced the unlock is going to work for me.

EDIT AGAIN: I guess my bigger concern is that I just want to be sure, as well, that if this isn't working for me, there's no trace of the unlock/unlock attempt, should something happen with the phone.
[Touch CDMA Windows Mobile ROM Development] egzthunder1:
The moment is done with the flashing, simply do not touch your phone, go to ActiveSync and disable USB connection. This is all without exiting the cmd prompt in your screen, which after flashing should read something like "disble USB and press any key run titan_exitbl"

Let me know if this works...
[Touch CDMA Windows Mobile ROM Development] jamsandwich:
Unless that's a time-sensitive step, I have done that.

Althought the unlocker says more than that, it says something along the lines of "Your phone should now be stuck on bootloader", and if it's not, to close the window or press Ctrl-C.

It also offers a prompt to disconnect ActiveSync.

I've tried both, with nothing working. Of course that doesn't really surprise me, as the phone never appears to be in the state the unlocker wants at that stage.
[Touch CDMA Windows Mobile ROM Development] egzthunder1:
Have you tried flashing a rom yet?It could be that you are already unlocked... the worst that can happen is that it gets stuck in the first bootscreen in which case you can simply put it in bootloader and flash a stock rom and start again.

The other thing would be to get the device in bootloader manually right after the unlocker is done flashing.
[Touch CDMA Windows Mobile ROM Development] jamsandwich:
I should know better... just concerned about the risk of bricking (as much as I want a new phone, I've still got a fair bit of contract left), but of course just trying is always a worthwhile solution. Have the new ROM on my phone now.
[Touch CDMA Windows Mobile ROM Development] egzthunder1:
Working, I presume?
[Touch CDMA Windows Mobile ROM Development] jamsandwich:
Yeah, it is.

As soon as I put it into bootloader mode, I wondered why I hadn't tried earlier. I spent a lot of time trying to will it to work precisely as stated in the guide (and the unlocker itself), to no avail.

Don't know where it went "wrong," but at least I got to where I wanted to be.
[Touch CDMA Windows Mobile ROM Development] egzthunder1:
Well, I am glad everything worked out... welcome to Vogue flashing 101!

Happy Flashing :)
[Touch CDMA Windows Mobile ROM Development] murkywaters:
So...I flashed NFSFAN's 6.5 rom and everything is kosher except that my internet stopped working. It did for a moment after the Sprint provision thing installed but now i get nothin'. sprint vogue on windows xp. data connection toggle switch is on and it's counting several minutes of connection time on the fone but IE won't search and google maps won't lock my GPS anymore. both things worked and then stopped. This is the only speedbump in what was an otherwise awesome unlocking/flashing experience.
[Touch CDMA Windows Mobile ROM Development] egzthunder1:
make sure that your username and password are still there. Check the EPST settings for this.
[Touch CDMA Windows Mobile ROM Development] murkywaters:
Oy I fear I'll get some crap for this but...yes,my username and pass are gone. And even worse, i'm assuming that EPST settings are something that i should have written down before i unlocked my fone eh? where can i get that username and pass from again?
[Touch CDMA Windows Mobile ROM Development] egzthunder1:
Call your carrier and tell them that you cannot access the internet. One more thing, do not tell them that you are in WM6.5 since they have no clue how to deal with it. Simply ask them for username and password for internet access.

Just out of curiosity, you can still make/receive calls, right?