yashsingh1/xdaforums huggingface dataset:
[Touch CDMA Windows Mobile ROM Development] knarly327:
In step 2 unlocking the device I missed #5. When I go to bootloader I do see 2.31 CoKe MFG. I can flash the ROMs OK but when it reboots it just come up with a blue screen that says bell on it. Is there hope?
[Touch CDMA Windows Mobile ROM Development] egzthunder1:
You said that you were in Verizon, so here you go

http://rapidshare.com/files/107459295/xv6900_RUU_signed.rar

Simply unpack it and run it.
[Touch CDMA Windows Mobile ROM Development] egzthunder1:
Flash back to stock and re-run the unlocker... Same happened to me at the beginning...
[Touch CDMA Windows Mobile ROM Development] knarly327:
Thanks

I flashed back to OEM and the did a reinstall. It's up and running, but when I scroll on the main screen or in the start menu I get ghosting.
[Touch CDMA Windows Mobile ROM Development] dwigginstm:
ok so ive so i flashed back to stock rom and but now when it tells me to run exitbl and disconnect connection through usb i do then it promps me saying to do disconnect again and then the entire program closes? is it unlocked
[Touch CDMA Windows Mobile ROM Development] knarly327:
I reloaded the new OS one more time and it fixed it!
[Touch CDMA Windows Mobile ROM Development] egzthunder1:
When you say "disconnect connection through USB", you mean going through Active Sync >File>Connection Settings> uncheck "Allow USB Connections", right?

I believe that the only way you can find out if it did unlock the device is by trying to flash something other than stock and see if it worked.

If I were you, I would run the unlocker one more time just to be on the safe side. Remember, before continuing with exitbl, you have to disable the usb in active sync as I described above, and then continue with exitbl.

Good luck... you are getting close :D
[Touch CDMA Windows Mobile ROM Development] skijosh:
GPS Help

I feel like I am way close on this, and it could just be a setting that I have wrong. I am hoping someone has an easy answer for me. My ultimate goal is to run Android from the SD and to have GPS working without a data plan.

I was running Windows 6.5 Hack originally,

I installed the Stock Verizion 6.1 Rom.

I installed cokeman's unlocker, hardSPL 2.31

Flash/Unlock with 0.40.coke

Flash RUU_Vogue_SPRINT_WWE_1.12.651.1_2.12.00_WPC_NV133_Ship.exe

Flash/Unlock with 2.31.coke

*Load Unlocker & Flash Verizon Stock Rom

Then I tried to install the 3.42.50 radio which is a .nbh file. This is where I ran into some difficulty. This thread, however said that I could use the normal Verizon stock ROM without any difficulty using the GPS, so I decided to give up on the 3.24.50 radio.

When I tried to install that radio though my phone and computer would get 8% through the RUU and then tell me that I could not use that RUU on my device and then it would reset my phone. The method by which I tried to install that radio was by downloading the NFSFAN's 6.5 Rom and by replacing the RUU_signed.nbh file in his ROM with the 3.42.50 .nbh file (obviously changing the name of the 3.24.50 radio file to RUU_signed.nbh).

Since I could not get the 3.24.50 radio to install and since I saw a post in this thread that says the stock Verizon radio should work fine, I decided to proceed to the next step.

I flashed NFSFAN's Rom 6.5 Rom.

I activated my phone by dialing *228. Verizon said my phone was already activated. I called my voicemail to verify that my phone was active.

I installed the Verizon provisioning cab

I imported the provisioning XML

set the mxipupdate_oemoperators_102.provxml

did Soft Reset

I then changed my GPS registry to these settings:

[HKLM\Software\HTC\SUPL GPS]

\EnableAGPS = 1

\EnableSmartMode = 1

\GPSMode = 4 (should also work as 2)

\NumberFixes = 999999999

\QoSAccuracy = 50

\QoSPerformance = 89

\ServerIP = 195.207.101.126

\ServerPort = 7788

\timeBetweenFixes = 1

Now when I go to GPS viewer I change the COM port: to 4 and I keep the baudrate at 4800. I press Open GPS and hit Cold Start. I then go to the GPS status tab and wait. I can wait 10 minutes and it never finds any satellites at all.

I want to proceed to install Android but I really want my GPS to be up and running. Does anyone have any ideas as to what the problem might be. Am I just not using GPS viewer correctly or do I actually need the 3.24.50 radio? If so, how can I install it without the error I was getting?

Thanks for everyones help so far and for the useful guides. I feel like I am very close on this!

Thanks,

josh
[Touch CDMA Windows Mobile ROM Development] skijosh:
^got it. I didn't have GPS location turned on in settings. I can now see satellites, lets see if I can get a lock.
[Touch CDMA Windows Mobile ROM Development] Driodl:
Egz, you da man :D

So I can get the device back into the bootloader, but whatever I try to flash it just gets to about 31%, throws a connection error and that's it.

I even tried the stock flash from the HTC website: same thing...

Rob.
[Touch CDMA Windows Mobile ROM Development] egzthunder1:
Try to get a new battery as I have a feeling that you may be trying to flash on a dying battery.

I still think that Win7 may be causing you more headaches than not...

Try to see if you can charge the battery fully.

Another idea. Flash to Android NAND. If it is a battery problem, you should be able to get away with this since the flash to Android only takes a couple of minutes (a little less than what it takes to flash 31%)
[Touch CDMA Windows Mobile ROM Development] Driodl:
I was finally able to get it to a somewhat workable state by flashing a Telus stock rom. (Not even the one from the HTC website worked).

I then tried to run Android via Haret.exe off the SD card, figuring that if I can run it from there I could flash it later. But I keep on getting a kernel panic. Tried various android versions: no dice.... so I'm gonna leave it for now, might try again later...
[Touch CDMA Windows Mobile ROM Development] egzthunder1:
I meant flash Android to NAND, but if you got it working... See how much your battery lasts. I have a feeling that your battery must be dying...
[Touch CDMA Windows Mobile ROM Development] necafe:
Hi~ I followed again through your method. but when i execute mtty.exe, there are no USB menu in drop down box. there are just com1~com9 and baud so i cannot into the command prompt. I thnk because my os is windows7, this is the reason. How can I solve this?
[Touch CDMA Windows Mobile ROM Development] Driodl:
You need to install a different driver first. See post #2 in this thread:

xdaforums.com/showthread.php?t=540290
[Touch CDMA Windows Mobile ROM Development] necafe:
Thanks a lot, Can I ask something?

Thanks a lot, I can entered mtty.exe with usb mode thanks to u.

My error is because of the windows7 driver. when i changed my driver with "x86 active sync driver-wceusbsh.inf", everything can be okay. thanks.

and I passed step4. but I don't know what radio rom I can choose. My phone is htc p3050 vogue(telus) and when i execute "RUU_Vogue_4350_TELUS_WWE_3.07.661.1_Radio_4350H_3.41.00_Ship_withPPSTPatch1.20.exe" or use "vogue_CDMA_3.42.30.nbh" file, there are error message 328 such as writer.

I also dont know why flashing radio rom. maybe i think it is necessary to use gps, but in my case, if i don't install radio rom, what is next step? is it reflashing previous rom such as "NFSFAN's WM6.5 1.00 FINAL ROM"?

sorry to ask ugly question.
[Touch CDMA Windows Mobile ROM Development] egzthunder1:
You don't really need to flash a radio, but the radios 3.4x.xxx seem to have better reception and some people even report improvements of the GPS signal. Remember that to flash an nbh file you need to rename the file to VOGUIMG.nbh, place it in the folder where you have the RUU, and then flash. If you were able to successfully unlock the Vogue with CokeMan's unlocker, you should be able to flash anything.
[Touch CDMA Windows Mobile ROM Development] Romparoo:
I am using this phone temporarily while I wait 3 days for my replacement Eris. Thought I would unlock this one as well.

Problems:

1. I have followed the first step several times and flashed the 2.31 coke, however I get 2.00 on the bootscreen. Not sure why. The only thing I notice is when I follow the steps from the additional screen, it says to make sure your device is connected to activsync, however it will not connect when in bootscreen mode. So I obviously can not do this.

2. How do I get to the bootscreen? Only way I know is to run the file. On my Eris is is power+volume up.

Thanks.
[Touch CDMA Windows Mobile ROM Development] Romparoo:
I downloaded your link and a custom ROM, they are sitting in my downloads folder. I do step 4 and it wants to run the 2.31 coke file. What do I need to do? Seems to me a step is missing.

What do I do VogueRUU zip? What do I do with the ROM file I downloaded?

Thanks.
[Touch CDMA Windows Mobile ROM Development] egzthunder1:
To get the device into bootloader you have to press Power+Camera and while holding them, you need to stick the Stylus in the Reset hole. If the device is still in 2.00, this means that you did not flash it (or at least that the process didn't run). The guide is complete as it is, I would suggest you to read it over a few times before attempting this again. Also, if you have a computer running XP (32 bit), try to do it with that as Windows 7/Vista act "funny". Good luck.
[Touch CDMA Windows Mobile ROM Development] Romparoo:
Thanks for the help.

Can you please help me with my second post about how to flash the ROM?

Thanks again.
[Touch CDMA Windows Mobile ROM Development] egzthunder1:
It wasn't clear in your post whether you were successful in running CoKeMaN.
[Touch CDMA Windows Mobile ROM Development] Romparoo:
Yep, got that working.
[Touch CDMA Windows Mobile ROM Development] egzthunder1:
Good. Okay since you already downloaded a rom (which is a compressed file), just go to any folder and uncompress it there. This should be the whole package for flashing (RUU and nbh). The reason why it is trying to run 2.31 again is because you are running the unlocker RUU again.

Again, just decompress the custom rom that you downloaded and run the RUU that comes out of that one. Then, simply follow the on screen instructions.

Good luck and let me know if anything.
[Touch CDMA Windows Mobile ROM Development] Lmiller1708:
Does anyone have .40 locker? The link to it is dead... Someone over at ppcgeeks is in need of it.. http://forum.ppcgeeks.com/showthread.php?p=1917168#post1917168

@egzthunder1,

Update your Post #7 with this link... The other site has been taken down or something...

https://sites.google.com/site/vogueroms/vogue-files

Edit:

Found the links at Mobile Underground. From Codybear.

I also added them to the above site. :)
[Touch CDMA Windows Mobile ROM Development] egzthunder1:
It should be uploaded in a few threads over at PPCG. I thought MU went under :confused:

I updated the link... thanks much :)
[Touch CDMA Windows Mobile ROM Development] jawhite:
Step 3?

I only got to step 3...I downloaded both NFSfan's ROM and the RUU package from the post, but both are RAR files. Nowhere can I find "Romupdateutility.exe"

Am I supposed to run it from the phone?

If someone can give me a solution, it would be much appreciated.

Thanks!
[Touch CDMA Windows Mobile ROM Development] jawhite:
Nevermind^ :]

Looked through the threads again and saw that I have to use winRAR
[Touch CDMA Windows Mobile ROM Development] egzthunder1:
Uhmm... RUU stands for RomUpdateUtility. You have to decompress the rar files.
[Touch CDMA Windows Mobile ROM Development] egzthunder1:
Question from caquito07

First and foremost, what was the status of the device before this happens? (connected and synced to the PC or in bootloader)? Also, did you make sure that you have a full charge in your battery?

In many occasions, the USB port is the culprit, so before anything else... try to change ports and see if that solves anything.

When you say "same result", do you mean to say that the unlocker does the same after flashing stock? Or are you saying that it gives you 262 while flashing stock?

@Nu,

Told you :D
[Touch CDMA Windows Mobile ROM Development] caquito07:
I tried the unlock with and without first putting the phone in bootloader. When I say same results, is that I am always getting the 262 error.

Thx
[Touch CDMA Windows Mobile ROM Development] egzthunder1:
So you cannot flash anything at all? Not even stock?
[Touch CDMA Windows Mobile ROM Development] leebobmonkey:
Alright, I have no idea where I went wrong. I was unlocking my Vogue. Everything was going smooth until the reboot. When it turned back on it was locked asking me to PM a guy named to0 with my "code" and he would pass me a serial to unlock the ROM. I did PM him and am waiting a response, meanwhile I can't use my phone. I thought I was just unlocking it, not flashing a ROM. Has this happened to anyone else? Where did I go wrong? Thanks for your replies. :)
[Touch CDMA Windows Mobile ROM Development] leebobmonkey:
Alright! I guess I freaked out a little bit. Even though it flashed one of to0's ROMs I just followed the rest of the guide as if it hadn't, and it worked fine. Now im running WM 6.5 Thanks to you egzthunder1 and NFSFAN! It is truly beautiful!
[Touch CDMA Windows Mobile ROM Development] caquito07:
This worked for me. Thanks Nu
[Touch CDMA Windows Mobile ROM Development] egzthunder1:
Glad you got it working :)
[Touch CDMA Windows Mobile ROM Development] NuAngel:
BTW, egzthunder1, I wasn't trying to be a jerk about "they always lock threads like these" or anything like that, in caquito07's original post... I just know I hate it when people tell me "go look somewhere else." I get easily confused. lol ;)

Glad we all got the problem solved, though. Enjoy flashing, caquito07!

Nu
[Touch CDMA Windows Mobile ROM Development] egzthunder1:
Hey Nu,

Don't worry about it... I was half joking about it myself :D
[Touch CDMA Windows Mobile ROM Development] alltimeqb:
going crazy?!

Not sure what I am doing wrong.

I have a win7 64 bit machine. Downloaded WMDC and reinstalled. Get activesync going and start the vogueunlocker batch file as administrator. (using coke 2.31)

Everything goes as planned (plug-unplug; RUU to coke 2.00) then something goes wrong. Exitbl is ran and it gives me an error, no usb connection. In the mean time the phone has rebooted and is going into windows 6.1 and customizes itself. I don't think its flashed to 2.31 because I press camera, power and d pad and it says it is shutting down (no bootscreen).

Another thing I notice is the status bar for the RUU update goes from 0 to 100 really quickly. Does that mean anything? I have a feeling I'm either missing something or using win 7 64 bit is problematic.

Oh and as soon as the program tells me to disable usb connection I do it in WDMC. but titan_exitbl gives me a usb error, while device is rebooting and going back into win 6.1

any help, please!! :confused:
[Touch CDMA Windows Mobile ROM Development] egzthunder1:
Actually bootloader is not Power+Camera+D-Pad, but rather Power+Camera+Reset. Also, the unlocker is fast, so seeing it jump from 0 to 100 is normal behavior. Check the version in bootloader and if it is ok, you can flash to any other rom. If it failed, the rom will flash but it will not boot. If this happens to be the case, simply flash back to stock and start the unlocker process again.

One last thing, try to get a WXP machine or if you must use 7, try to use a 32 bit version.

Good luck.
[Touch CDMA Windows Mobile ROM Development] pigeonguy:
messed up this time

I toasted my orig Vogue by winding up in Lake Winnebago with the Touch in my pocket.

Luckily, my brother got a new phone and gave me his Vogue to mess with.

Started the unlock process and thought I got 2.31 on as it shows up in bl but as in the message above I get stuck in the htc smart mobility screen when I reset or hard reset.

I forgot to undue the USB in AS during the disconnect/reconnect part of installing the unlocker.

So I flashed NFS final but it won't boot.

My question is how do I flash back to stock if the unlocker isn't instalaled correctly?

thanks,

pigeonguy
[Touch CDMA Windows Mobile ROM Development] Lmiller1708:
You should be able to just flash back to stock. Then restart the process over again.

Just don't forget to unplug! ;)

Happy flashing!
[Touch CDMA Windows Mobile ROM Development] pigeonguy:
Thanks for the quick response.

That's my problem. How do I flash back to stock if I can't hook up to AS?

pg
[Touch CDMA Windows Mobile ROM Development] egzthunder1:
You don't need to be synced. Put your device in bootloader mode. The RUU will recognize it that way.
[Touch CDMA Windows Mobile ROM Development] pigeonguy:
Okay. Didn't know if that would work as I have the stock ROM (nbh) on the mem card and it won't load from there.

Will try the RUU process while I have it in bootloader.

That will work even if the bootloader isn't installed correctly?

thanks again,

pg
[Touch CDMA Windows Mobile ROM Development] egzthunder1:
If you are talking about CokeMan's unlocker, then yes... don't worry :)
[Touch CDMA Windows Mobile ROM Development] pigeonguy:
FM just happened!! :)

I had taken the card out and xferred what I thought was the stock ROM to the card and renamed NFS' ROM and the orig to VOGUEIMG.nbh.

I did a hard reset again thinking it would go into bootloader and it did a update again and then I did another hard reset and it fired up a version of 6.5!

Not even sure whose it is.

In the device info the ROM version is 1.00.6_5 ROM WWE with Radio version 3.42.50 and 30 was on it before with orig.

Hot damn, back in business. <g>

Thanks for the help,

pigeonguy
[Touch CDMA Windows Mobile ROM Development] egzthunder1:
I think it is NFS's based on the build number, but I could be wrong... In either case, glad you got it working.
[Touch CDMA Windows Mobile ROM Development] reckoner13:
After the RUU is done and do you push ok? The phone automatically reboots. Then I unchecked Activesync allow USB and I get the error that tells me to uncheck allow USB (even though I already did it). Is the phone supposed to reboot and do you let it boot up and install everything before running the last part?
[Touch CDMA Windows Mobile ROM Development] necafe:
I flashed radio rom but it is window mobile 6.1

As you show, I unlocked correctly and I flashed my rom with NFSFAN's WM6.5 1.00 FINAL ROM. And I skipped step4 and stated step5 to change radio rom. At that time, I could know that radio rom is window mobile 6.1.

Of course, in that 6.1 rom, I can use gps signal and I could use navigation program, garmin. But I want to use NFSFAN's WM6.5 1.00 FINAL ROM and garmin program together.

And then, must I flash NFSFAN's WM6.5 1.00 FINAL ROM again?
[Touch CDMA Windows Mobile ROM Development] egzthunder1:
The radio and the rom are two separate things. Unlocking and flashing a rom to a device will not change your radio. You must flash the radio separately (or with a stock rom that includes whatever radio you are willing to flash).
[Touch CDMA Windows Mobile ROM Development] necafe:
okay, I got it

Thanks so much. You mean radio rom uses different area. I know, but the method change rom is same. That's why I confused, but anyway, I flashed that rom with 6.5 rom after changing radio rom. And when I checked gps, it worked correctly. In fact, when I checked before, my phone could not find satelite signal.

However, now I can use gps.. Thanks a lot.

I think the reason is not install radio rom correctly, because now I can see the telus name in my phone exactly.

Nawadays, I am interested in Android freyo. Also I flashed my vogue phone with Android. Ah, do you know how to install dual booting of that?

Last time, I remembered I watched similiar article...^^
[Touch CDMA Windows Mobile ROM Development] egzthunder1:
Simple, just download the rom that you are going to be using and run it from SD (NoRootFS). If you flash to NAND, you will lose WM altogether.
[Touch CDMA Windows Mobile ROM Development] johnnyboy_CM@msn.com:
egzthunder1 Thanks for posting this thread. It was exactly what I've been looking for. I've had the HTC Touch(US cellular) for quite awhile and wanted to change the OS. I'm on the second step of Unlocking the CID.

-fyi, I'm using a Mac, but running Windows 7 x64.via VMware fusion. (and I read that you said to use a 32 bit, is there a way to do that with out purchasing new software?

My main problem: I run the vogue unlocker_2.31.exe in Windows. It extracts some items and then opens up the command prompt.

1) My phone is connected via WMDC(not in bootloader) the first step i press any key to start.

2) Then like you said there are those errors that just run through(sleep.somethin).

3) Next it says"The next step will load temp SPL to ram with JumpSPL... "so I press enter.

4) Now it says "my device should be in a three color screen, showing the softbootloader."....however, Its not :/ So Idk whats wrong.

5) Right after that is when Im supposed to disconnect and reconnect but obviously I can't.

Any help would be appreciated. I've tried alot of things in the past few days.
[Touch CDMA Windows Mobile ROM Development] johnnyboy_CM@msn.com:
New problem:

However, now I'm having the problem that others have had too. After doing the RUU, I disconnect the phone via WMDC. I then press 'enter' to start the next page of instructions on the command prompt. It tells me "your device should now be in bootloader 2.31 coke"..."next step is titan_exitbl.exe"...."manually disconnect"....

So what I did was turn off connections via usb from wmdc right after it closed itself automatically. So it didn't even have time to connect. Yet I know it is stillconnected to the computer. Because my computer asked me to connect to either Mac or Windows.

Finally I pressed enter, and a dialog box says you must manually disconnect form autosync but make sure your usb is plugged in...I think this question got posted around the #3 page of this thread but I didnt understand how to fix it. Thanks again guys!
[Touch CDMA Windows Mobile ROM Development] egzthunder1:
Try to get an image of XP 32 bit. I have not seen too many success stories with 7, let alone with an emulated 64 bit version on a Mac. I know that the unlocker had quite a few issues with 64 bit systems, and as far as changing that, the only way is to get a different version of the OS (you cannot change the architecture of an OS... it isn't an option).

I hope this can help you a bit.
[Touch CDMA Windows Mobile ROM Development] johnnyboy_CM@msn.com:
I'm glad this thread isn't Dead :)

Well I went out and bought Vista 32-bit system. I tried for XP but, im buying from university bookstore with a discount so I didn't think I could go wrong....However....:/ still doesn't work. It wont run the .exit and whenever my phone goes into standby mode it still won't turn back on without resetting. I even tried flashing back to what I thought was stock Rom. (Which I got from htc's site.) Nothing works. When I try to flash anything other than the unlocker I get the 260 Error. I've even tried extracting files from unlocker and the official .exe from htc to grab the .nbh files and putting them on my SD to boot them up from the bootloader. I am just about ready to give up and go buy a new phone :( Please help egzthunder! ps. I would sooo pay you to just do it for me at this point. I've been without my phone for almost 24 hours now.
[Touch CDMA Windows Mobile ROM Development] egzthunder1:
Believe me that if I had your phone with me, it would be my pleasure to do it for you. Do you have any friend who has a Win XP PC? You will only need to install ActiveSync due to the drivers rndis.dll... but the computer must have said drivers. Now, if you can get your hands on one, follow the guide again, but first flash to the correct stock (nothing else will flash properly on your phone until you unlock it completely). I have a link in one of my posts to all the stock roms from most carriers...