Related
I have always been afraid to flash my 6800 Verizon phone because I need it for work & I can't afford to brick it.
I recently realized my sms/mms program would not send images & Verizon was clueless as to what was wrong (after connecting me to 2 different tech #'s & two hours wasted time). They decided to send me a new phone & it will be here today.
After researching, I realized it was HTC Audio manager causing the conflict & I tried to uninstall it. I could not uninstall it however (it refused to uninstall) & since I had no "safe mode" to use I was screwed until I found the newer version of Arcsoft mms/sms. Installing that cured the problem & the original phone now works perfectly.
Now, I think I will try modding the new phone & see if I can get the GPS working before de-activating (or keeping) the original.
Could someone please link me to a page with the necessary files & instructions on how to do this?? (I am at work & can't spend 1/2 the day searching the site).
Thankyou very much for any/all advice etc anyone can give me.....
~John
There is a Titan ROM upgrade forum right here at this site. You just need to scroll down a little to find it.
Anyway, dcd is the biggest ROM creator for the Titan on this site. Here is his latest ROM: http://forum.xda-developers.com/showthread.php?t=413039
You can also check over at PPCGeeks.com in the Titan upgrade forum for a bunch of them.
I read that the xv6800 agps fix would also work for the xv6900, but after I install the modem drivers and plug in my phone and then put it in dmr mode, it shows up on my computer as "HTC Vogue Diagnostics" not "HTC USB Modem" and it cannot find the drivers. anyone else have this problem?
im experimenting the same thing but what rom are you using? im using NFSFAN sprint rom and I saids vogue diagnostics I dont know what I did wrong.
yep...i'm using the same rom. I wish there was a way to solve this without flashing to a diff rom. i really like this rom and have a lot of stuff that would take quite a bit to backup/restore if i flashed to another rom
Follow these links and you'll find your fix! I had the same problem as you guys. NFSFAN at ppchaven.com posted the driver you need. (or you can use a vista computer) Vista works with a weird quirk.
Feel free to join and list me as a referral... thanks are welcome too!
I'm sambonedd there.
http://www.ppchaven.com/viewtopic.php?f=19&t=492
http://www.ppchaven.com/viewtopic.php?f=43&t=140&st=0&sk=t&sd=a&start=1375
thanks a lot sambino! you saved my life cuz im not running vista and i didn't wanna reflash. Merry Christmas!
Remember, you have to make 5 good posts on ppchaven to download files. Just register, use me as a referral if you will, post five times, and enjoy your file. Thanks at the haven are welcome too! Merry Christmas!!!
Here is how I got the drivers installed and working perfectly.
For some reason the model numbers don't match up in the inf file provided by the WModem installer. I changed the following line in qcusbmdm.inf
from:
; For WinXP
[Models.NT.5.1]
%OEM00% = ModemXP, USB\VID_0BB4&PID_0B03&MI_00
to:
; For WinXP
[Models.NT.5.1]
%OEM00% = ModemXP, USB\VID_0BB4&PID_00CF
Then just went to device manager and updated the driver using the updated qcusbmdm.inf
bigjr99 said:
Here is how I got the drivers installed and working perfectly.
For some reason the model numbers don't match up in the inf file provided by the WModem installer. I changed the following line in qcusbmdm.inf
from:
; For WinXP
[Models.NT.5.1]
%OEM00% = ModemXP, USB\VID_0BB4&PID_0B03&MI_00
to:
; For WinXP
[Models.NT.5.1]
%OEM00% = ModemXP, USB\VID_0BB4&PID_00CF
Then just went to device manager and updated the driver using the updated qcusbmdm.inf
Click to expand...
Click to collapse
Sweet! That worked beautifully. Thanks.
I was having the same problem, I flashed to an older radio, not the 450. And then my phone was recognized. I then applied that agps fix and upgraded the radio and agps has been working flawlessly. As for ROMs, I have been running NFSFAN's and have been very happy with them. Im running 1.09 right now because I upped to 1.10 (verizon) and had a problem with Touchpal and autocomplete SMS, so i went back to 1.09.
bigjr99 said:
Here is how I got the drivers installed and working perfectly.
For some reason the model numbers don't match up in the inf file provided by the WModem installer. I changed the following line in qcusbmdm.inf
from:
; For WinXP
[Models.NT.5.1]
%OEM00% = ModemXP, USB\VID_0BB4&PID_0B03&MI_00
to:
; For WinXP
[Models.NT.5.1]
%OEM00% = ModemXP, USB\VID_0BB4&PID_00CF
Then just went to device manager and updated the driver using the updated qcusbmdm.inf
Click to expand...
Click to collapse
Don't know what this means? nor how to do this. I've done this fix on a titan (numerous time) but can't get the computer to recognize the phone in DRM?
Sambino, one of those links is broken. can't find the driver, any chance of posting?
Thanks
Kmanuel, download the usual wmodem drivers, which you probably already have. Once they are installed, navigate to \C:\Windows\system32\drivers and locate the driver installed, qcusbmdm.inf. You could also just do a search on C: for that file. Once you find it, right click and open with notepad. Locate the lines that bigjr99 gives, beginning with "For WinXP":
; For WinXP
[Models.NT.5.1]
%OEM00% = ModemXP, USB\VID_0BB4&PID_0B03&MI_00
and simply change the data to:
; For WinXP
[Models.NT.5.1]
%OEM00% = ModemXP, USB\VID_0BB4&PID_00CF
Then save that file and put your phoen in DIAG and plug it in. If it asks what driver just locate the system32\drivers\ folder and it will find it!
Thanks, that works pisser. Did not know where to start to look for those drivers. Thank you.
Thanks so much guys - I've been looking for a solution for this for hours. Only interesting thing was that the files were actually located in a different folder (not the drivers folder) - they were in a folder called 'DRVSTORE'. So I copied the inf. file into the driver folder. It worked until it asked for a system file (qcmdmxp.sys) which was also in the DRVSTORE folder. Copied that in, and poof - I'm good to go! Thanks!
Ok I am confused and cant seem to get the GPS to work. This is what i have done.
The phone is a verizon xv6900 (a week old).
1) when I first recieved it the customizations ran
2) I upgraded to the official VZW WM6.1 (3.14.605.1) from the verizon site and again let the customizations run
3) Now I started researching the gps features - reflashed WM6.1 (3.14.605.1) but didnt let the customizations run.
4) Installed the Vahalla cab - http://wiki.xda-developers.com/index.php?pagename=VerizonAGPSFix
no luck with 3rd party gps (a standard one like a garmin).
5) Installed NSFAN's verizon GPS cab and GPS Viewer.
GPS viewer looks like it is doing something (scrolling through stuff in the setup screen) but never gets a satellite (about 5 - 10 min waiting time).
What am I doing wrong. I would like to keep the verizon rom if possible.
jbsmith said:
Ok I am confused and cant seem to get the GPS to work. This is what i have done.
The phone is a verizon xv6900 (a week old).
1) when I first recieved it the customizations ran
2) I upgraded to the official VZW WM6.1 (3.14.605.1) from the verizon site and again let the customizations run
3) Now I started researching the gps features - reflashed WM6.1 (3.14.605.1) but didnt let the customizations run.
4) Installed the Vahalla cab - http://wiki.xda-developers.com/index.php?pagename=VerizonAGPSFix
no luck with 3rd party gps (a standard one like a garmin).
5) Installed NSFAN's verizon GPS cab and GPS Viewer.
GPS viewer looks like it is doing something (scrolling through stuff in the setup screen) but never gets a satellite (about 5 - 10 min waiting time).
What am I doing wrong. I would like to keep the verizon rom if possible.
Click to expand...
Click to collapse
You would probably get a quicker answer from this thread:
http://forum.xda-developers.com/showthread.php?t=424387&page=81
Well I followed those instructions, but it doesn't work for me. I think because my rom version is not the same that is listed in those instructions. Evidently vzw has created a new WM6.1 rom since the orginal in 2008.
What I mean is post the questions there. That is the thread to discuss GPS issues with the stock MR1 or MR2 roms.
"Serfboreds" has come up with a really easy GPS Fix if your running Valhalla with the latest Verizon rom. Simple and easy as pie. Dowload and install the Serf Telus aGPS for Valhalla Cab and dial *22899 to reprogram the phone. Damn thing is working again!!!!!!!!
Fix to the Verizon's BS move to shut down the GPS!
http://forum.xda-developers.com/showpost.php?p=3555579&postcount=703
This WORKS AS OF 5-31-09
http://forum.ppcgeeks.com/newreply.php?do=newreply&noquote=1&p=939180
KCDale99 Posted this, couple weeks ago, it still works people.!!!!!!!!........
I justreceived a new XV6900 in the mail today when mine suffered a hardwarefailure of some sort. The new phone came with the newest ROM whichincludes the 3.37.78 radio. Of course I turn on the phone, and updatesrun. This disabled the GPS even after loading a custom ROM. the aGPSfix would not work, and gps Viewer couldn't even find one satellite.
Ifigured this was just like an old, 'let the customizations run'problem. So I followed the steps found here with one exception:
<!-- m -->http://wiki.ppchaven.com/index.php?titl ... ERIZON_GPS<!-- m -->
Onstep 4, I ran the RUU_Vogue_VZW_WWE_3.14.605.1_Radio_3.37.78_ShipOfficial ROM from Verizon. I did NOT let customizations run. I thenloaded my custom ROM. This puts me on the official Verizon radio.
After that, the aGPS fix worked like a charm and GPS is working.
Iknow this is a rehash of other issuew, but I wanted to let everyoneknow that the newest phones shipping are disabling GPS all together.
THIS STILL WORKS PEOPLE!!!!!!! been at this for a week now with absolutely no luck until now this guy has it.................. 5-31-09
I used NFSFAN's custom ROM WM6.5v8 for my custom rom.
the only other thing i had to do is when i was done installing ROM's my phone would not authenticate on Verizon network, so instead of calling them i use the online MY Verison to activate my phone to a old Verizon i760 then re-activated my xv6900 online ordered (verizon) a week ago !!! I have tried every fix, etc... until this combo... except i never went to the leaked verizon radio been to the bell, us cellular, alltel, verzon, etc... and back again..... now it works...... with the fix this guy posted......QPST ip info fom the fix page, links all seem to work!
Again********THIS STILL WORKS PEOPLE
XV6900 CAME STOCK ABOUT A WEEK AGO!!!
No GPS in Google maps
I have done the aGPS mod on my XV6900.... I did it on my previous 6900 without a problem at all...
I am running WM6.1 from NSFAN v1.15 and I get locks on Sats with GPS viewer but nothing with google...
anyone have any ideas on troubleshooting or tips?
Hey guys I know this is not the unlocking thread but I tried posting on the thread made by "coke" with no response. So I thought I'd do it here. So here's the story
I have a Sprint Vogue and I was really getting tired of the slow HTC WM 6.1 and all the buttons that I could not modify on the cube (which is useless cuz I dont use any of the them). So I decided to try out a new rom with 6.1 and touchflo 2D.
I went to the ppcgeeks forum to unlock the phone, followed the instructions, read and reread the posts. Finally decided to give it a go. Everything went smoothly until the last step (exitbl) of coke 2.31. It kept telling me to disable USB on activesync and then the program would just shut down! ?? And yes I did disable the USB option for the activesync before that step. I looked under the device information and realized that nothing has changed interms of the ROM. So I tried it again and again (4 times). Then I just reinstalled the HTC 6.1 rom with the 3.42.30 radio... So any ideas on why this may be happening? I promise I followed all the steps
My second question is, in your opinions, what is the most reliable, stable and fast Touch 6.1 rom? Let me know if you have an opinion.
Thanks so much in advance, any help would be appreciated.
I had what sound like the same problem yesterday.
my post is over at ppcgeeks.
"I disconnected but I did not see the phone exit bootloader mode and reset itself.
....
What should I do from here?
Reboot phone, soft reset, hard reset? - go have fun?
....
I did a couple soft resets and have been playing around with it,
I guess I upgraded right... but it was weird there at the end, instructions not the clearest to me, i guess."
mine seems to be working fine, except the weather thing.
shows
in the About section my phone reads
WM 6.1 Pro
CE OS 5.2.21041
Device Information reads
ROM version 1.05.Alltel
Radio version 3.42.30
PRL Version 30008
PRI version 2.02_011
I was kinda scared to do another hard reset b/c I had already changed a bunch of settings.
Sorry if this doesn't help you too much,
but it is nice to know I'm not the only one with this issue
.
Hmm sounds like a similar problem. But I thought it wasn't unlocked unless we saw 2.31.coke somewhere in the device information.
As far as I know, hard reset did not hurt the phone. I tried installing that unlocker 4 times then went with the original HTC rom and it still turned out just like before. It installed the rom fine
Yeah I am still concerned about how it wont go through the exitbl step...
moonwoo said:
Hey guys I know this is not the unlocking thread but I tried posting on the thread made by "coke" with no response. So I thought I'd do it here. So here's the story
I have a Sprint Vogue and I was really getting tired of the slow HTC WM 6.1 and all the buttons that I could not modify on the cube (which is useless cuz I dont use any of the them). So I decided to try out a new rom with 6.1 and touchflo 2D.
I went to the ppcgeeks forum to unlock the phone, followed the instructions, read and reread the posts. Finally decided to give it a go. Everything went smoothly until the last step (exitbl) of coke 2.31. It kept telling me to disable USB on activesync and then the program would just shut down! ?? And yes I did disable the USB option for the activesync before that step. I looked under the device information and realized that nothing has changed interms of the ROM. So I tried it again and again (4 times). Then I just reinstalled the HTC 6.1 rom with the 3.42.30 radio... So any ideas on why this may be happening? I promise I followed all the steps
My second question is, in your opinions, what is the most reliable, stable and fast Touch 6.1 rom? Let me know if you have an opinion.
Thanks so much in advance, any help would be appreciated.
Click to expand...
Click to collapse
Yeah, the directions can be a bit confusing over there on that thread
Basically here are the steps
Download the 2.31 unlocker
Download the ROM you want to use (my personal preference is this one for a TF2D style or this one for a WinMO 6.5 style interface that has TF2D included to switch back and for - both very stable, fast and clean and the thread is very active for help (especially if your on Verizon or Bell which can have issues)
from there, use WinRAR to extract each file into separate folders
then Put your phone in bootloader mode (press and hold power+camera+stylus in reset until 3-color screen comes up)
At this point at the bottom of the screen it will say Serial, plug it into the USB cable or cradle and it should change to USB
Start the exe in the 2.31 and follow the directions (you may get some errors about sleep4.exe just click on OK as it keeps occuring its a XP/Windows7 64 bit issue if that is what your using)
At the point where it tell you to disconect, unplug the phone from the USB cable and wait (count to 10 or something) then plug it back in, it should have went from USB to SERIAL and now back to USB at that point go ahead and hit any key on your PC and it should continue along
once complete, reboot, allow it to do its thing then reboot and go back into bootloader again during reboot you should see coke 2.31 in the upper left if so your ready to go
plug it into your USB/Cradle again and then go into the ROM folder you extracted the ROM into
Once the screen on your phone says USB again go to the folder and double click on the RomUpdateUtility.exe file and follow the directions again, it may take some time so be paitent
once the phone flashes and reboots, let it run and do its thing to the and reboot itself then (and here is an important step for stability) once it starts up do a hard reset (red+green+stylus in reset hole) hit the enter button (center of D-Pad) it will reflash the phone and then red key (send) when prompted
then go thought the setup again, this time you can actually set things up as your keeping them this time and once things are done and your at the start screen on your phone power off (not reset) the phone and then start it up again - seems doing it this way takes care of alot of little issues that will come up before they can happen
Depending on your carrier be sure to have one of the DCD Carrier Cabs as well especially for the 6.5 ROM as it is a generic ROM and some have reported needing to run the DCD Carrier Cab for the service they use to get on the internet and use GPS and the like
Hope that clears up things a bit LOL
Detroit Doug
Doug, when I go into the bootloader it DOES say SPL-2.31.Coke. Does that mean that it is all set? Also this time, it still asked me to disable active sync at this time (at the exitbl step) do you have to run that step to complete the unlock?
This is what my bootloader image says
VOGU100 NFG
SPL-2.31.CoKe
CPLD-3
Let me know if I need to run the exitbl or if I am set to load the rom. Thanks so much for your help!
moonwoo said:
Doug, when I go into the bootloader it DOES say SPL-2.31.Coke. Does that mean that it is all set? Also this time, it still asked me to disable active sync at this time (at the exitbl step) do you have to run that step to complete the unlock?
This is what my bootloader image says
VOGU100 NFG
SPL-2.31.CoKe
CPLD-3
Let me know if I need to run the exitbl or if I am set to load the rom. Thanks so much for your help!
Click to expand...
Click to collapse
Your all set to flash if in bootloader it says as your phone does SPL-2.31.CoKe
you all unlocked and ready to go ... just put your phone in bootloader mode then connect the phone to your PC "serial" will change to "USB" and then run the RomUpdateUtility.exe file and follow along with the bouncing ball, do the watusi, wipe hands on pants - whatever helps you pass the time
but follow the steps as outlined above with the hard-resets and power-offs and the like, believe me its better to solve the issues before they occur than wait and have to start over
Detroit Doug
Doug, it worked like a charm. I did not know that the last step of the unlocker was not required. I installed 6.1 with Touchflo 2D. Looks and feels .. wow. it's the coolest thing I've seen. I've followed all your step including a hard reset before I started using it. So far the speed is impressive.
Couple more questions for you since you are an expert at this.
1. If I reload the factory default ROM, will it reset everything back to normal and can I keep reverting back and forth between different ROMs without any consequences?
2. It (the NFSFAN's 6.1 rom) seems to use less Storage memory (137 free vs HTC's ~100 free) but much more Program memory (59 free vs. ~80 in HTC's) than the HTC default. Any ideas or concerns about this?
All in all thanks so much! Hopefully as I learn more and more I will be able to contribute things too. You are right. This is so cool and highly addictive!!
Take care~ BTW I am in Lansing Go State!
moonwoo said:
Doug, it worked like a charm. I did not know that the last step of the unlocker was not required. I installed 6.1 with Touchflo 2D. Looks and feels .. wow. it's the coolest thing I've seen. I've followed all your step including a hard reset before I started using it. So far the speed is impressive.
Couple more questions for you since you are an expert at this.
1. If I reload the factory default ROM, will it reset everything back to normal and can I keep reverting back and forth between different ROMs without any consequences?
2. It (the NFSFAN's 6.1 rom) seems to use less Storage memory (137 free vs HTC's ~100 free) but much more Program memory (59 free vs. ~80 in HTC's) than the HTC default. Any ideas or concerns about this?
All in all thanks so much! Hopefully as I learn more and more I will be able to contribute things too. You are right. This is so cool and highly addictive!!
Take care~ BTW I am in Lansing Go State!
Click to expand...
Click to collapse
Glad it worked, and Ill try to answer you concerns
1 -Now that it is unlocked go ahead and swap ROMs all you want to, the tricky part is the stock ROM, flashing back to stock can and will revert your radio (if youve upgraded it) and ca cause issues with the unlocker, but a simple run of the unlocker 2.31 again can correct it
2 - NFSFAN like other Chefs have ways of moving data/programs around when they cook up these ROMs utilizing whatever kitchen program they personally prefer that being the case how they data/programs get pushed about can create the speediness you now see in your phone by freeing up the RAM for apps and the like and pushing programs off to the side optimizing how the device should have been setup from the start
As for that, Ive been using his ROMs as well as some others for quite some time and have had little to no issues with how he places the progs and data so I wouldnt worry about it
Yeah, Live in Las Vegas now - but Michigan will ALWAYS be home Go Red Wings !!!!
Detroit Doug
Thanks Doug, for all your information. Your answers were great! Hopefully I wont need too much more help in the future. i'm learning~
Don't mean to go off on a little tangent, but I find this post really helpful and was wondering if you, Doug, or someone else could provide a link to this 2.31 unlocker or whatever it is. Thanks in advance.
hibbiejibbie3 said:
Don't mean to go off on a little tangent, but I find this post really helpful and was wondering if you, Doug, or someone else could provide a link to this 2.31 unlocker or whatever it is. Thanks in advance.
Click to expand...
Click to collapse
http://forum.ppcgeeks.com/showthread.php?t=20370
Detroit Doug
Having trouble unlocking my xv6900. I'm using 2.31 unlocker. I have the phone in bootloader mode and when I connect the usb it goes from serial to usb. I run the RUU from the unlockers self extracted folder but it get an error message. I'm pretty positive its just something im not doing correctly. Any help appreciated.
Another thing I noticed the RUU will not detect my current version if I am in bootloder mode. If I run the RUU with active sync on it will detect my current version but when it puts my phone into bootloader mode to update it, it disconnects my active sync connection.
Reddog80p said:
Having trouble unlocking my xv6900. I'm using 2.31 unlocker. I have the phone in bootloader mode and when I connect the usb it goes from serial to usb. I run the RUU from the unlockers self extracted folder but it get an error message. I'm pretty positive its just something im not doing correctly. Any help appreciated.
Another thing I noticed the RUU will not detect my current version if I am in bootloder mode. If I run the RUU with active sync on it will detect my current version but when it puts my phone into bootloader mode to update it, it disconnects my active sync connection.
Click to expand...
Click to collapse
Check your PM over at PPCGeeks
Detroit Doug
Reddog80p said:
Having trouble unlocking my xv6900. I'm using 2.31 unlocker. I have the phone in bootloader mode and when I connect the usb it goes from serial to usb. I run the RUU from the unlockers self extracted folder but it get an error message. I'm pretty positive its just something im not doing correctly. Any help appreciated.
Another thing I noticed the RUU will not detect my current version if I am in bootloder mode. If I run the RUU with active sync on it will detect my current version but when it puts my phone into bootloader mode to update it, it disconnects my active sync connection.
Click to expand...
Click to collapse
From Detroit_Doug
At the point where it tell you to disconnect, unplug the phone from the USB cable and wait (count to 10 or something) then plug it back in, it should have went from USB to SERIAL and now back to USB at that point go ahead and hit any key on your PC and it should continue along
Maybe wait longer if you can,
I reckon some pc take longer to fully recognize[process] the disconnect and reconnect procedure.
example: disconnect > wait 20-30 seconds > reconnect > wait 20-30 seconds > then continue
I had that same issue and waiting longer during this process helped
.
I can't even get to that point. With active sync on as soon as I start the unlocker RUU it gets the info from my phone and shows the current rom 3.14.605.1 ....I click update and it shows 2.31 unlocker I hit next and then the install status bar comes up on my desktop and my phone goes into bootloader mode and the active sync connection drops and I get the 262 connection error. If I start the RUU with my phone in bootloader usb mode already it does not detect my current rom and I click next. click next to 2.31 unlocker, and it goes through the same steps and I get the same error. Is there anything I have to do to my phone prior to running the RUU. My phone is a verizon xv6900 running wm 6.1 rom 3.14.605.1 with radio 3.37.78
I have the same problem with my new sprint touch. I get error 262 at 0%, did they change something in these new phone that won't allow us to unlock?
Rom is 3.03.651.4
radio 3.42.30
I think I got it, what I did was not to extract the vogue_unlocker_MFG_2.31.exe file but to run it. I had activesync set up and connected, then just ran the unlocker, don't extract it. It will shut off activesnyc and put my phone in to the 3 color screen, form there, just follow the directions. Also I didn't have to run the exitbl step as my phone auttomatically exit and restarted.
I ended up having to re-run the .041 unlocker and then the 2.31 unlocker and it ended up working for me. I'm not sure why I had to because I Had the same bootloader info prior to running the 2.31 unlocker in the first place. The 6.5 rom and gps rom has been working flawlessly for a week now, the only thing I had to do was call up VZW (*8889) the guy answered "account investigations" LOL I told him I had to hard reset and my phone wouldn't authenticate and he asked me to call back from another line. I told him that I had no landline and he said thats fine I can override it just call back right away whenever you get to another phone. That was on friday and I have not called back but I've been able to text, make and receive calls so I don't think I will unless I have to.
gooney said:
I think I got it, what I did was not to extract the vogue_unlocker_MFG_2.31.exe file but to run it. I had activesync set up and connected, then just ran the unlocker, don't extract it. It will shut off activesnyc and put my phone in to the 3 color screen, form there, just follow the directions. Also I didn't have to run the exitbl step as my phone auttomatically exit and restarted.
Click to expand...
Click to collapse
thank you! i did that and it worked for me.
yeah, it says right in the directions over there to just run the exe it will create a temp folder and run the RUU itself from there
Extracting it and running it will always cause issues
also - Ignore the sleep4.exe or whatever if you encounter it - it is a legacy exe that is called that isnt used anymore, wont affect the unlocking just hit OK through it
Detroit Doug
I used all of the step by steps on your site (xda) unlocked the phone, unplugged the cable when it told me to. I even ran the rom 3 times like someone suggested. Did the hard reset, and loaded the sprint cab file.
I get internet when plugged into my computer via usb cable. I love 6.5 but if I cant use the internet while away from a pc I cant use it. A have already gone back to 6.1 where everything is working. Please help me...
smsmustsng said:
I used all of the step by steps on your site (xda) unlocked the phone, unplugged the cable when it told me to. I even ran the rom 3 times like someone suggested. Did the hard reset, and loaded the sprint cab file.
I get internet when plugged into my computer via usb cable. I love 6.5 but if I cant use the internet while away from a pc I cant use it. A have already gone back to 6.1 where everything is working. Please help me...
Click to expand...
Click to collapse
Which 6.5 rom are you using? If it's NFSFAN's, did you try his spring internet&gps posted in his thread? What sprint cab did you use? DCD's?
smsmustsng said:
I used all of the step by steps on your site (xda) unlocked the phone, unplugged the cable when it told me to. I even ran the rom 3 times like someone suggested. Did the hard reset, and loaded the sprint cab file.
I get internet when plugged into my computer via usb cable. I love 6.5 but if I cant use the internet while away from a pc I cant use it. A have already gone back to 6.1 where everything is working. Please help me...
Click to expand...
Click to collapse
I had the same thing happen to me when I upgraded to 6.5 on my Sprint Touch (I also flashed the ROM 3 times). I ended up going back to 6.1 (everything works), re-upgrading to 6.5 (internet still didn't work), back to 6.1 and finally upgraded to 6.5 (everything works). Regarding the internet, make sure that your "Current username" in Device Information is [your sprint.com username]@sprintpcs.com. I think that was my problem... I only casually checked the GPS, so I am not sure when it worked and when it didn't, but it's working now. Good luck
cdude said:
Regarding the internet, make sure that your "Current username" in Device Information is [your sprint.com username]@sprintpcs.com. I think that was my problem...
Click to expand...
Click to collapse
seems to be my issue as well, but i must be stupid. how do you change that. i have went through every setting that i can think of
jmleedy said:
seems to be my issue as well, but i must be stupid. how do you change that. i have went through every setting that i can think of
Click to expand...
Click to collapse
I think mine was configured automatically by Sprint when I was using the stock 6.1 ROM. If I am wrong about that (I tried so many different things), I must have edited "User Name" in the DATA [3282] phone code.
ok i am still dead in the water on this. i checked with sprint and they told me to go to start-settings-personal-phone and then under settings should be an internet or network option to which i should be able to hit the "get settings" button and it should be ok, however internet isn't even there and nothing ele seems to fix it? anyone?
Yeah, those options aren't in 6.5. Have you tried going back to 6.1 and checking the internet? HTC has the ROMs posted on their support pages (e.g. this is the Sprint one)
I had the same issue. Flashed what seems to be a billion times.
Now I'm just running a bare 6.1 stock rom and running android on it for a much, much better OS. 6.5 is amazing and all, but it still can't hold a candle to android. Next I need to try Hero, as I'm running cupcake.
When you flash back to 6.1 run the IOTA (provisions) under the settings to make your internet works. then when you flash to 6.5 you shouldn't need to run the provision or gps cabs. this has worked for me every time. so just make sure your internet works on whatever rom you are using before 6.5...
cdude said:
I think mine was configured automatically by Sprint when I was using the stock 6.1 ROM. If I am wrong about that (I tried so many different things), I must have edited "User Name" in the DATA [3282] phone code.
Click to expand...
Click to collapse
The data [3282] keeps asking me for a password, ? Just need to change the user name so sprint tv will work.
I haven't been able to unlock my touch. I am using 2.31 unlocker, I run the RUU.exe and get up to the point where the phone shows the gray screen with the %bar. But it stays at 0% and after a few minutes a get Error 262.
I have already re-flashed to my stock ROM, but same results.
Touch (Sprint)
ROM: 3.03.651.4
Radio: 3.42.30
WinMo 6.1
Update:
I have tried on Windows 7 Pro 32-bit, and on Windows XP Pro 32-bit. Same results....
Try this...
I'm sure the thread will be locked and you'll be told to ask in the FAQ's thread or something, but I hate when that's the only thing you get... not helpful enough! So maybe I can sneak in before the lock.
I had this problem a week ago, and for whatever reason, the only thing that worked for me was: 1st, flashing to the latest stock ROM (which you already have), then turning on the phone and letting it connect to Windows Mobile Device Center (Win7) or ActiveSync (WinXP) (do the whole 'connect without configuring device thing) then run the actual unlocker BAT file (Vogue_unlocker.bat) in the 2.31 unlocker.
Trying to manually run the EXE didn't want to work - letting the BAT file do it's thing through activesync actually worked for me.
Maybe it'll help... I hope so! Good luck!
NuAngel
NuAngel said:
I'm sure the thread will be locked and you'll be told to ask in the FAQ's thread or something, but I hate when that's the only thing you get... not helpful enough! So maybe I can sneak in before the lock.
I had this problem a week ago, and for whatever reason, the only thing that worked for me was: 1st, flashing to the latest stock ROM (which you already have), then turning on the phone and letting it connect to Windows Mobile Device Center (Win7) or ActiveSync (WinXP) (do the whole 'connect without configuring device thing) then run the actual unlocker BAT file (Vogue_unlocker.bat) in the 2.31 unlocker.
Trying to manually run the EXE didn't want to work - letting the BAT file do it's thing through activesync actually worked for me.
Maybe it'll help... I hope so! Good luck!
NuAngel
Click to expand...
Click to collapse
Oh come on Nu!
Unlike most other mods, I don't simply lock the thread. I lock it and/or transfer it to the Q&A thread where I answer the question myself. Please don't say these things. I try to keep the Vogue apart from the usual MO in several other fora.
I do it for 2 reasons:
a. To keep clutter to a minimum
b. To have a nice db with solutions to many issues that people may have with their Vogues. Trust me that the Search Engine of this site works much better when you look through a single thread than when you look for threads.
@caquito07,
I am transferring your question over to the Flashing Guide Sticky thread. Please follow up over there.
@Nu,
One last thing... thanks for stepping in
Thread closed.