yashsingh1/xdaforums huggingface dataset:
[Touch CDMA Windows Mobile ROM Development] dwigginstm:
You never put the phone in bootloader mode tho, just turn the phone on and connect it to activesync like normal. Then when you run the unlocker it will atomatically go into bootloader. You will be about to run the RUU just dont forget once the upgrade is complete you still have to REopen activesync and uncheck "allow usb connections" then finish the instructions on the command prompt. Due pay attention to what it says because it will change the instructions. I hope this helps
[Touch CDMA Windows Mobile ROM Development] egzthunder1:
So, did you get it? Are you finally running custom roms? I have not heard from you in a couple of days so either you gave up or you got it done...
[Touch CDMA Windows Mobile ROM Development] mrstak:
Damn. Okay so I followed your instructions but when its running the RUU, I'll hear the usb and activesync disconnect then it'll close out of activesync and I get an Error 262. I see the progress bar on both the computer and the phone but it stays at 0%.

Edit: Basically, I never get to the command prompt portion of the unlocking.
[Touch CDMA Windows Mobile ROM Development] mrstak:
I'm gonna flash back to the stock ROM and try the unlocker again. I'll post back tonight when I get it done.
[Touch CDMA Windows Mobile ROM Development] dwigginstm:
ive got a question on step six can i just install the carrier cab that i need and then use my phone with that carrier? In short what are the carrier cabs for?
[Touch CDMA Windows Mobile ROM Development] egzthunder1:
I believe they are presets for things like web, mms, sms. That saves you from having to manually configure everything... I think.

You are in #6, which can only mean that you finally unlocked it, right?
[Touch CDMA Windows Mobile ROM Development] dwigginstm:
lol no i dont think i ever will i actually went to metro today to see if they could flash it the lady explained that all they do is unlock it usually with a program called hudini?
[Touch CDMA Windows Mobile ROM Development] egzthunder1:
Yes. What houdini does is simply what cdma workshop does, with the only difference that houdini is the only official (and legal) way of adding the esn of your phone to their database, so that you can use it. They also configure all your nam settings as well, but you can do that yourself if you know your MIN...

They do not unlock phones...
[Touch CDMA Windows Mobile ROM Development] AFace:
Won't sync when in bootloader mode.

screen does change from serial to USB. When I attempt to run unlocker screen says connect device and press any key to continue. I have tried several times, changed USB ports with no resolve. Any other ideas... I'll try anything.

Device does sync when in normal mode.. no problem.

Thanks,

Alan
[Touch CDMA Windows Mobile ROM Development] egzthunder1:
Don't start up in bootloader. I will fix my tutorial since that seems to have caused more harm than good. Just start up the unlocker with the device being in normal mode.
[Touch CDMA Windows Mobile ROM Development] AFace:
New Problem after SPL-2.31.CoKe loaded

After reading the threads for 2+ hours I now realize I need to start over again. I downloded XV6900_RUU_signed.rar, now need instructions on how to run it as it's not a exe file. I know I missed something and feel very stupid now. But... need help.

Thanks again,

Alan

I will be donating when this is all over believe me!
[Touch CDMA Windows Mobile ROM Development] egzthunder1:
Use WinRaR to decompress it.
[Touch CDMA Windows Mobile ROM Development] AFace:
Extracted file now I have .nbh file.

From what I read I have to put the.nbh file on the SD card and boot up the phone forcing it to read the file and revert to the original ROM? I that correct? Or is there something else I can use to extract from the .nbh file?

If I have to put in on the SD card what buttons do I push to force reading from the card?

thanks,

Alan
[Touch CDMA Windows Mobile ROM Development] egzthunder1:
Read this thread from the start, especially post 3. If you get an nbh file only, you have to put it in the RUU folder that you need to obtain as well (in that post too). Please read the whole guide again as I have a feeling that it is not clear to you what you need to do).
[Touch CDMA Windows Mobile ROM Development] AFace:
Yes, I missed the real meaning of step #3. Now I have completed the process (3 times) went through the complete process including updating the Rom. Now the phone sits at the Verison screen. (that's why I tried 3 times.)

The reason for this whole thing is to get back to stock and start over as the small file on the original unlocker did not complete. I never got that option the process just ended before I got that option (as it in the video). what now???
[Touch CDMA Windows Mobile ROM Development] egzthunder1:
That is where the problem lies. Unless you are certain that everything went correct, you should not flash a custom rom. Going back to stock is not such a big deal. In fact, here is the link

Verizon Stock Rom

Simply connect your device in bootloader to the computer and run the exe. Once you are back in stock, you can try to reflash the unlocker. Which, by the way, which radio version do you have? If you can see the version number, you should be able to see the R (which is the radio)

Here is another guide http://john-time.com/?p=296 if you want to see it. It is in essence the same as mine.
[Touch CDMA Windows Mobile ROM Development] AFace:
I don't know the Radio version number is and I can't see the version number now. Is it ok to ahead with this without knowing the Radio version?
[Touch CDMA Windows Mobile ROM Development] AFace:
I ran the stock rom... the radio version I have is 3.37.78. I can't seem to get it back in bootloader mode to if the rom took. I did have 2.31 CoKe before running this latest.

I am not stuck at Verizon screen any more. Do I go ahead and try again to update to ROM with 2.31 unlocker again to see if I can get the exitbl to run this time?
[Touch CDMA Windows Mobile ROM Development] AFace:
got it into bootloader mode.. still have SPL-2.31 CoKe running. Should I try to reinstall it again over what's there?
[Touch CDMA Windows Mobile ROM Development] egzthunder1:
If you completed exitbl successfully, then go for it.
[Touch CDMA Windows Mobile ROM Development] oralite:
Need help unable to unlock...

When i run the unlocker, the ROM flahsing finished quickly (even though it says takes 10 minutes)? and then the phone immeidately reboots and goes back to normal mode. I do not get the chance to run the titan_exitbl program.

Am I missing something?
[Touch CDMA Windows Mobile ROM Development] AFace:
exitbl never ran. What's interesting is that the phone displays 2.31 Coke. But when I run the wwe_3.14.605 over again the program displays 3.14.605 as the existing. Which one do you think I have?

I did try everything over again but with no success. Should I go ahead a try to upgrade the WM6.5 anyway? I'm really lost now.
[Touch CDMA Windows Mobile ROM Development] egzthunder1:
You are doing it right but you have to make sure that ActiveSync USB connections are disabled after the phone is done flashing the unlocker. The flashing is a lot shorter because you are only flashing a SPL and not a rom (major size difference).
[Touch CDMA Windows Mobile ROM Development] egzthunder1:
Try to flash a custom rom (NFSFan). If it worked, all the better. If it did not, simply flash back to stock and try again.
[Touch CDMA Windows Mobile ROM Development] AFace:
Flashed NFSAN's WM65.1.00 final

It took on the first try. Is that the version I should have? Do I need to add any thing else to it, like cab's? From what I see I think I'm likin it. Please advise what I should do now. I will need to call VZ and reactivate it when I'm ready. I had to transfer over to my old XV6800 w/6.1 while this one was not working, so there is no rush to reactivate the 6900.

thanks for all your help, and you understanding.

Alan
[Touch CDMA Windows Mobile ROM Development] egzthunder1:
Glad it worked out! You can install anything you see fit to make your device yours :)
[Touch CDMA Windows Mobile ROM Development] AFace:
Verizon couldn't activate

I tried several times to activate the phone with no success. I finally went to the local Verizon (company) store. Their first reaction was excitement that I was successful in flashing to 6.5. They then tried several times to activate it and finally called tech support and they tried to go through even the manual process but the instructions they had were different than the phone was. They (of course) didn't tell the tech support what had been done. Anyway they felt that what I had was the wrong Radio?? installed. So I left and have now flashed it back to 6.1 but the Radio still has the same version. What do you think we can do now.
[Touch CDMA Windows Mobile ROM Development] egzthunder1:
As far as I understand, CDMA phones work with companies in the following manner: The customer purchases a phone (which has an ESN number, which is a number of each device). When the customer (you) has a phone ready for activation, they create an account which also has a series of numbers that belong to you (your phone number and another number call MIN). For a phone to work on that particular network for that particular account, all of the numbers that I have mentioned must match when the tower queries your device. Else, you will have no service in the device.

My guess is that the ding-dongs at Verizon have no clue on what they are doing (which does not surprise me). Moreover, there is nothing to activate, they simply need to match all of these numbers in your account in their system and you should be up and running. The device can be running on WM2003SE and it still wouldn't matter as it has nothing to do with WM in the first place. It is the programming of the phone itself that has to be done. The radio has nothing to do with it either. I tell you because I reprogrammed my Sprint Vogue myself to go into MetroPCS and it works without a problem.

I would go to another store and see if you can get someone a bit more knowledgeable on the subject...
[Touch CDMA Windows Mobile ROM Development] dash88:
vogue unlocker 2.31

its not compadible with 64 bit windows7 or vista? that was the error message i was geting. Any sugestions, arrrgghh:mad:
[Touch CDMA Windows Mobile ROM Development] mikurej95:
same with me, the 64 bit problem
[Touch CDMA Windows Mobile ROM Development] AFace:
Do you think I need to lock it again

I flashed it back to stock OS (6.1). Do you think I should lock it again and try to activate it? My thought of that is because when I activated the 6800 the first thing that happens in the automated process is "SPL unlocked" pops up on the phone screen. After that it shows the process. When I attempt to activate the 6900 that doesn't happen. Just about the time it would pop up a message comes up that it unable to process, call 800..........

If so what do I se to lock it again, of does flashing it back to stock lock it also?

Regards,

Alan
[Touch CDMA Windows Mobile ROM Development] egzthunder1:
I don't think it will help. Read my last post regarding how this works and you'll see that it is the people at Verizon that have no idea.
[Touch CDMA Windows Mobile ROM Development] egzthunder1:
@dash88 and mikurej95,

Try a 32 bit XP machine. I have not seen many workarounds for this...
[Touch CDMA Windows Mobile ROM Development] AFace:
I agree with what your say however, being there and watching them go through the same process as I go through myself at home to activate a phone and when it didn't work they called tech support and then started a manual process of activating it, following the instructions from tech support, didn't get far because as they were told to 'now go to...' , which was about the third step, that option wasn't there on my phone so they couldn't go any farther. I did have MW6.5 installed, not flashed back to stock, just so you know the whole story.
[Touch CDMA Windows Mobile ROM Development] egzthunder1:
If you know the settings for your account and you know that Verizon has the ESN registered under your account, you can get a program like CDMA Workshop and program it yourself. Alternatively, you can try (if you are using NFSFan's rom) to use the tools in the folder labeled (Phone Codes), particularly one called PST. In there, you can change all the parameters of the connection and it should allow you to connect. Remember that you will need your MSL code to change the options in the PST menu. BAFMSL is a simple to use program that will yield the MSL code quick.

Ask the people from Verizon (over the phone) to give you the MIN and any other important information that is needed to configure your phone (settings for NAM1 and NAM2, etc). I can almost guarantee you that they tried to input the phone code to get to the EPST menu and because the rom that you have has a skinned dialer, they could not get to the menus. Long story short, if you can get the necessary numbers, you can get that phone activated. I can help you if needed be. Let me know.
[Touch CDMA Windows Mobile ROM Development] AFace:
Your help is appreciated. I am new at this, I did upgrade my XV6800 to 6.1, which I am using now, some time ago. I will give your suggestions a shot and be in touch if I run up against a stone wall. Again, thanks much!
[Touch CDMA Windows Mobile ROM Development] novafreak69:
GPS

OK I cannot remember... Do I need to load the sprint ROM fist on the Verizon phone to unlock the GPS chip? or can I go straight from st6ock to NFSFAN's 6.1 and have the GPS unlocked?
[Touch CDMA Windows Mobile ROM Development] egzthunder1:
Is your device unlocked? If it isn't, you will end up bricking it. You don't need to go to Sprint to unlock the GPS.
[Touch CDMA Windows Mobile ROM Development] novafreak69:
NO... I unlocked it and then did The NFSFAN 6.1 Verizon rom v1.15 Not sure what the radio is or if the GPS is working...
[Touch CDMA Windows Mobile ROM Development] egzthunder1:
Go to settings>System>Device Information. The radio version will be displayed there.
[Touch CDMA Windows Mobile ROM Development] novafreak69:
3.37.78

I mean does that mean it is Unlocked??? cause I know in the beginning that Verizon was locking thir GPS chips so Peeps would Purchase VZNavigator. Then I heard their last revision of the Stock ROM had the GPS unlocked...

I have had poor Luck with the GPS in this particular device...
[Touch CDMA Windows Mobile ROM Development] novafreak69:
I have not acivated this phone yet either... and will need to return my current phone back to stock Status...
[Touch CDMA Windows Mobile ROM Development] egzthunder1:
That radio version means that your Vogue is GPS capable. If you were successful in unlocking the device simply flash any custom rom and you will have a working GPS in no time. It just takes a while to get a lock-on. 3.42.50 has a bit of a faster lock-on than 3.37.78, so you may want to give it a shot.
[Touch CDMA Windows Mobile ROM Development] stiltzkin:
Thanks so much, egzthunder1! An excellent guide, and a rare one considering how little material is aimed at (relative) n00bs such as myself.

Just thought I should mention, I had to do a little digging to find the Bell ROM you referred to (3.09.666.1) - it has moved and your link is now a 404.

It can now be found here.

Thanks again! Still tinkering with this; I may be back with questions...
[Touch CDMA Windows Mobile ROM Development] egzthunder1:
Thanks for pointing it out! I will update the first posts.
[Touch CDMA Windows Mobile ROM Development] stiltzkin:
Alright, I'm a little confused now.

I successfully unlocked my phone with CoKe 2.31, and SuperCIDed it (because I planned on updating the radio). I also flashed the NFSFAN rom you mentioned, for the sake of completeness.

Here's what I'm trying to do: I'd like to flash Android (a la this post) to NAND and not use WinMo at all. AND also I'd like to have the latest radio for the device with the best working GPS signal.

With that said, I have a couple of questions:

1. What's the latest/best radio for the Vogue (just the radio so I can flash via sdcard, not a ROM + radio), and most importantly where can I download it?

2. What exactly controls whether or not the phone can be reprogrammed after upgrading a radio (dialing *228)? Is it just the fact that the radio has changed, or if I flash back to my stock ROM will I be able to make calls again? At the moment my phone is not authenticated and can't make any calls. *228 fails. So...do I need to call customer service if I want a new radio to work?

Sorry for all the questions, but I spent a good 4 or 5 hours working on this last night and ended up with a disconnected phone. Any help is appreciated...
[Touch CDMA Windows Mobile ROM Development] egzthunder1:
Here are your answers:

1. I am using 3.42.50, which is the latest official found in the Bell rom. I personally had a bunch of issues trying to flash the radio by itself (not that I don't know how to flash a radio, but for some reason it simply wasn't doing it). So, I flashed it with that rom (the same one you pointed out). There is a thread in this sub-forum called "3.42.40" which has a zip file with all the latest three radios (.30, .40, and .50). These are only the nbh files, so they are good for what you want to do.

2. Programming of the phone and radio upgrade are two separate things that have nothing to do with each other. If you are taking your device to a carrier that is not the one who sold it in the first place, you need to make sure that they have your ESN in their database, and most importantly... linked to your service account. You will need to call up your provider and explain to them that you are trying to activate your phone on their network. At that point, they will ask you for the phone's ESN and they will walk you through the process of programming it so that it can work with your account. Word of the wise, most carrier tech reps have no clue that the Vogue can go past WM6.1, which was their last official update, so if you tell them that you are in 6.5.x, you will get a few "huh?!?"

I hope this helps. I spent nearly a week learning about CDMA phone technology, how to program my Vogue, and how to change the E$N since I did not want to pay MetroPCS $50 for doing what I can do myself.

Good luck!
[Touch CDMA Windows Mobile ROM Development] stiltzkin:
Thanks for your reply.

I have to stay with Verizon on this (my contract isn't up until 2011), so getting it re-authenticated with them is a must.

So, what's the best way to go about this? I would think:

1. Flash 3.42.50 radio either from sdcard or flash the Bell ROM (3.09.666.1)

2. Flash Android

3. Try *228 to authenticate phone.

The problem with this, though, is that if *228 doesn't work (and it probably won't), then I'd have to flash a WinMo ROM anyway and call Verizon (Android doesn't let you edit radio parameters and all that advanced stuff). Plus I'm not about to call them while my device is running something other than Windows.

So, should I flash the Bell ROM and then call Big Red, or go to Android? And just to be clear - I can get my phone working if I do this right, yes?
[Touch CDMA Windows Mobile ROM Development] egzthunder1:
You should be able to get it working. I wouldn't go to Android until you get your device working first. CDMA programming is relatively simple if you are on WinMo, but I have very little experience with Android (and I am sure that Verizon techs do too). I can almost picture them scratching their heads if you tell them that you have a Vogue running Android... that picture would be priceless :D
[Touch CDMA Windows Mobile ROM Development] stiltzkin:
Alright, so I think what I'll do is flash the Bell ROM with the new radio and then give Verizon a call. Hopefully they'll be able to reauth my phone.

Then I should be able to flash Android (having at this point a GPS-enabled radio and authenticated network).

Thanks for your help so far - let me know if there are any holes in this plan...
[Touch CDMA Windows Mobile ROM Development] stiltzkin:
Well, I figured it out - flashed back to stock (with radio 3.37.78) and then called Verizon through #8899. The reauth process took about a half hour and involved lots of screwing around in EPST with NAM settings. Even when we were done (and I received the mountain of texts I missed while my service was out), *228 programming didn't work. But I'm back in action, so I digress.

Thanks for all the clarifications and help, egzthunder1! I think I'll be sticking to Android via SoftSPL (Haret) until I really know what the deuce I'm doing with ROMs and radios.

My only remaining question is - can I get GPS to work without changing my ROM now? As I said, my radio is 3.37.78 on Verizon's stock ROM (WM 6.1) and my phone is still fully unlocked.

Thanks again!
[Touch CDMA Windows Mobile ROM Development] novafreak69:
How do I get my hands on a downgrade version of the radio?
[Touch CDMA Windows Mobile ROM Development] novafreak69:
Activation

I am guessing that I should have Activated my new phone before I hacked it... cause they are having a hell of a time getting it activated...
[Touch CDMA Windows Mobile ROM Development] egzthunder1:
Verizon, I'm assuming? Flash back to stock and get them to program it. They have no clue of what to do without the EPST via dialpad :)
[Touch CDMA Windows Mobile ROM Development] egzthunder1:
You can get GPS to work. I believe it is only a registry modification, but you should be fine. In fact, I believe that Verizon "freed" the GPS in their last update for their version of the Vogue.
[Touch CDMA Windows Mobile ROM Development] egzthunder1:
You can find a zip with all the radios in the following thread

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

Good luck.
[Touch CDMA Windows Mobile ROM Development] stiltzkin:
Okay, great. First though, should I try to update my radio to 3.42.50 with Verizon stock? I'd like to get the best signal and lock time, obviously.

But will upgrading the radio deactivate my phone again? If at all possible I'd like to avoid having to call them and go through the whole charade again.
[Touch CDMA Windows Mobile ROM Development] egzthunder1:
If I am not mistaken the latest Verizon rom has 3.42.30 and not .50. The only stock rom that I am aware of that has 3.42.50 was the Bell rom. Flashing a new radio has no effect in the EPST settings at all, nor will it modify anything in your current rom. Good luck!
[Touch CDMA Windows Mobile ROM Development] dannonc:
Verizon htc xv6900

I have the Verizon version of the Vouge? And I've got the WM 6.5 programed on my phone however it's unable to program and register as an activated phone. (I can play with the new software but can't dial out, text, use Internet-No Service!) Called Verizon twice & they had me dial *228 & *22890-unable to reprogram at this time. Should I just reinstall the original program (is there an easier way?!) or is there a fix without getting rid of the new wm 6.5? Thank you for your time & any help!
[Touch CDMA Windows Mobile ROM Development] jimt007:
Your link, Sprint rom with radio 3.42.30, posted on page 6 no longer works.

What happens if you follow your steps and don't have that rom?

Phone won't work right?

Sprint HTC Touch - Winmo 6.1 (now)
[Touch CDMA Windows Mobile ROM Development] egzthunder1:
I think that the phone is not able to use the config tools with the rom that you are using. You can always flash to a different rom and try that. If you need to program your device, simply use the stock rom and use the *228. After you are done programming, simply flash back to whatever rom you want. Changing the rom usually does not change your EPST settings. Good luck!
[Touch CDMA Windows Mobile ROM Development] egzthunder1:
Thanks for pointing it out. I will look for a new link. That rom is only if you need to go back to stock for warranty purposes. It does not affect anything else.
[Touch CDMA Windows Mobile ROM Development] novafreak69:
NO MMS after Flash

I recently recieved a replacement for my XV6900 which I Imediately flashed NFSFANS Verizon rom 1.15. Since then I am unable to send or recieve MMS... any push in the right direction would be greatly appreciated.
[Touch CDMA Windows Mobile ROM Development] egzthunder1:
Did you install the carrier cab for Verizon?