Has anyone who installed both noticed any differences? I've run into 1 for sure difference, and 1 that I'm not so sure about. I installed a program called SmartphoneNotes, worked fine but wouldn't sync. While trying to get it to work, I uninstalled and was going to reinstall after a reboot. The reboot went into an endless loop of reaching the T-Mobile splash screen, and then it would power off and reboot again. No choice but to start over, so I flashed with the official ROM instead of the 'leaked one'.
The 1 for sure difference I noticed was how Activesync (Windows Mobile Device Center) named my device. With the leaked ROM, my device was named 'TMobile0', with the official ROM, it was named 'chaznet's Dash', the same as when I had WM5. A minor difference, but something did change with the initial partnership setup.
The difference I'm not so sure about is the Settings icon in the Start Menu, I could swear it looks different in the official ROM, but don't really know.
You may be right but according to the HoFo post below, the two builds are exactly the same...
http://www.howardforums.com/showthread.php?t=1156233&highlight=RUU_signed.nbh
WM6 Leaked vs Official
The two builds are identical. There was some speculation in one thread as to whether or not T-Mobile hosted on Infospace (the leaked version was hosted there) but it turned out that the official release was hosted there as well.
Official jogbar problems, leaked no jogbar problems?
Using the leaked RUU file my jogbar worked for in call volume control, using the DashUpgrade file the jogbar would not work for in volume control; went back to leaked RUU file and now it works fine. Tried the jogbar in both versions with no additional software installed, so it wasn't a software conflict. Would like someone to confirm cause the registry settings appear to be the same on both versions.
Mine works fine with the official release, the same as it did with the leaked one.
mar11974 said:
Using the leaked RUU file my jogbar worked for in call volume control, using the DashUpgrade file the jogbar would not work for in volume control; went back to leaked RUU file and now it works fine. Tried the jogbar in both versions with no additional software installed, so it wasn't a software conflict. Would like someone to confirm cause the registry settings appear to be the same on both versions.
Click to expand...
Click to collapse
The morning of the official release, there was a Infospace link posted prior to the file being available via http://www.t-mobile.com/wmupgrade/. But in the days prior to release, the links that were going around were hosted on RapidShare.
curtislanham said:
The two builds are identical. There was some speculation in one thread as to whether or not T-Mobile hosted on Infospace (the leaked version was hosted there) but it turned out that the official release was hosted there as well.
Click to expand...
Click to collapse
chaznet said:
Mine works fine with the official release, the same as it did with the leaked one.
Click to expand...
Click to collapse
Re-downloaded T-Mobile Upgrade file and re-installed, now they work!
Related
Hello All,
I have been upgrading mine and a few friend's dash's to the Kavana 6.1. My Dash however has a hardware issue (the ear piece speaker is distorted) and is being replaced through warranty service. My new dash arrived today, and I know I need how to re flash my software back before I send it to T mobile. I downloaded TMO_1.22.531.6 from the official rom sticky. However when I open the zip file it is a RUU_signed.nbh file contained inside.
I am not sure how to flash with this file. I assume it requires some other software in order to flash it. I have tried numerous searches and can't really seem to find what I am looking for. I really got spoiled by the simple EXE launchers included with Kavana rom's.
Any help would be VERY appreciated.
Thanks!
You need to go to this thread .
On the bottom of that thread download the files needed zip file, add (copy or move) the .nbh file in that folder after you unzip it of course.
Run the romutilityupgrade.exe file and follow the directions as you did before.
Why not go to Tmobile support site and download the official Rom and install that ?
Thank you for your help -- I actually tried it both ways.
First I tried to use the t-mobile website and when I attempted to run the exe it always failed out on error 202 which of course is usb (even though it was connected). So then I tried it the way by grabbing the software recommended. When I ran the AUTO batch script (similar to the way I installed Kavana), it installed just fine. So that being said, I got it downgraded. If you can't tell I don't have a real great understanding of the actual upgrade/downgrade process.
Issue is tho, when I first got the phone, the initial splash screen was t mobile if I remember correct, but when I upgraded to Kavana it changed it to the HTC logo. Well after the downgrade, it still boots with the HTC logo instead of Tmobile. Will that be a dead give away that I flashed the phone when warranty center receives it? If so how could i change it?
That's definitely gonna raise some eyebrows.. but I kinda doubt they'll notice it. Just look at the idiot phone techs you get when you call their tech support line... I don't know how you would change that...
chris300zx said:
Thank you for your help -- I actually tried it both ways.
First I tried to use the t-mobile website and when I attempted to run the exe it always failed out on error 202 which of course is usb (even though it was connected). So then I tried it the way by grabbing the software recommended. When I ran the AUTO batch script (similar to the way I installed Kavana), it installed just fine. So that being said, I got it downgraded. If you can't tell I don't have a real great understanding of the actual upgrade/downgrade process.
Issue is tho, when I first got the phone, the initial splash screen was t mobile if I remember correct, but when I upgraded to Kavana it changed it to the HTC logo. Well after the downgrade, it still boots with the HTC logo instead of Tmobile. Will that be a dead give away that I flashed the phone when warranty center receives it? If so how could i change it?
Click to expand...
Click to collapse
you can go here--> http://forum.xda-developers.com/showthread.php?t=341753 and follow instructions on post #1 to reflash the tmobile boot spash screen. i've tried it and i have the t-mo splash screen now.
Thanks for the help! I actually was able to get it to successfully go away by stepping back another version to .4 from .6 -- this replaced the screen and returned it back to the way it came. Coincidentally, after looking at the replacement units software version and confirming it was .4 I feel fairly confident everything will be fine, oh and now everyone doesn't sound like a robot!
Thanks again,
Chris
After updating the phone, the update utility on desktop said "congratulations. Your phone has been successfully updated." The phone restarted then. But it can't boot into the main menu. After the Sprint logo, it dies there.
Help!!!
have you tried performing the update again?
Yes. I have updated the phone several times.
I couldn't update the ROM directly. There is not USB connection. I had to press camera + power + reset to initiate the connection and then start the flashing. But still there is no luck.
I called the HTC support just now. A guy told me that the update isn't official and asked me to contact Sprint for the original ROM to flash it back.
To be honest, I don't quite believe him. I think he just gave me the run around.
Draiko said:
have you tried performing the update again?
Click to expand...
Click to collapse
dongdongdog said:
Yes. I have updated the phone several times.
I couldn't update the ROM directly. There is not USB connection. I had to press camera + power + reset to initiate the connection and then start the flashing. But still there is no luck.
I called the HTC support just now. A guy told me that the update isn't official and asked me to contact Sprint for the original ROM to flash it back.
To be honest, I don't quite believe him. I think he just gave me the run around.
Click to expand...
Click to collapse
its because its not "official" until the 21st... didnt you see they took the download page for the mogul and touch down? that was just testing and preparing and someone caught it and posted it.. thats a lot of theories anyways..
That's correct, the ROM updater won't work until 7/21. But you can start to run it at 12:01am on 7/21, if you're up that late on Sunday night... Make sure you keep the file in a cool, dry place until you use it...
(just kidding... the ROM updater works perfectly fine. However there are reports that it works best with XP... problems with both Vista and Win2K (not a joke))...
Can you extract the contents and then run the nbh off a memory card?
I am running Rick and Stylez Rose ROM v1.6 !
Yesterday I needed to revert back to the HTC WM6.0 version to make sure a problem existed in that ROM prior to calling Tech Support.
When I tried to run the original ROM update, it kept failing with a COMMUNICATIONS [202] error.
I am sure there is some multi-finger startup method that can get the phone into a state where this will not happen - but a quick search did not find one. So, I took a look at the AUTO.BAT file that installs the latest Rose ROMs.
Turns out that Rick's previous insertion of "Pause"s in that batch file has made it really easy to load the Original ROM.
Simply run the AUTO.BAT as normal to load the latest ROM, and when you get to the point where your S620 screen is all white, and the PC screen displays the message
"Now use RUU to flash ROM(Don't touch the usb link line)"
Press and key to contiue ...
Press Ctrl-C to terminate the batch file (and the installation of the new ROM). Instead go and run the installer for the Original ROM.
It will install without any COMMUNICATIONS errors.
Hope this helps others who run into this issue.
LiverpoolFCfan said:
I am running Rick and Stylez Rose ROM v1.6 !
Yesterday I needed to revert back to the HTC WM6.0 version to make sure a problem existed in that ROM prior to calling Tech Support.
When I tried to run the original ROM update, it kept failing with a COMMUNICATIONS [202] error.
I am sure there is some multi-finger startup method that can get the phone into a state where this will not happen - but a quick search did not find one. So, I took a look at the AUTO.BAT file that installs the latest Rose ROMs.
Turns out that Rick's previous insertion of "Pause"s in that batch file has made it really easy to load the Original ROM.
Simply run the AUTO.BAT as normal to load the latest ROM, and when you get to the point where your S620 screen is all white, and the PC screen displays the message
"Now use RUU to flash ROM(Don't touch the usb link line)"
Press and key to contiue ...
Press Ctrl-C to terminate the batch file (and the installation of the new ROM). Instead go and run the installer for the Original ROM.
It will install without any COMMUNICATIONS errors.
Hope this helps others who run into this issue.
Click to expand...
Click to collapse
Or you can turn off the phone, then hold the camera button down for like 5 seconds, plug the usb while still holding it down. This should bring you to a tri-colored screen and now you can flash with the original (official) rom without any errors...
jdoggraz said:
Or you can turn off the phone, then hold the camera button down for like 5 seconds, plug the usb while still holding it down. This should bring you to a tri-colored screen and now you can flash with the original (official) rom without any errors...
Click to expand...
Click to collapse
And that's definitely the best way to do it! I outlined it in detail in my Rose ROM thread. Or better yet, load the modified SPL made by jockey(also found in my thread) and never worry about whether the ROM matches the phone again. You can load ANY ROM anytime!
NRGZ28 said:
And that's definitely the best way to do it! I outlined it in detail in my Rose ROM thread. Or better yet, load the modified SPL made by jockey(also found in my thread) and never worry about whether the ROM matches the phone again. You can load ANY ROM anytime!
Click to expand...
Click to collapse
Oh sweet haha thanks for letting me know about that...
I have had my s620 for a while now and everything has been fine, flashed it with a rickys rom then changed my mind and went with kavanas (sp?) then something happened....
i broke the darn screen!, not a problem i replaced it. simple but... i lost all my settings, smart toolkit and the t9 programs were no longer installed?
i've been trying to flash back to kavanas or the new rose rom with no luck, whatever i do it wont run the SPL part of the auto.bat ???
i've unlocked it again, played with the usb connection settings, everything i can think of! someone please help!
i've attached a screen shot of where it hangs for you...
***EDIT*** and i have tried all the obvious things, and some of the less obvious (running the SPL file myself from the device, restarting the device, hard reset, etc)
Maybe try flashing with your official ROM first. I don't know that much but what ever is screwed up from having a broken screen might get fixed doing that. I know, annoying extra step but worth a shot...
i wish it was so simple lol!
I cant find my official rom anywhere, its a UK BT Broadband Rom ???
I've tried 3 different Roms, even tried to bypass the Auto.bat files for the roms and do the flashing manually with no luck!
Edited: (Link removed, was software update. Not the Full ROM)
There's the link to download the official BT Broadband ROM Update
The BT ROM is here http://www.mediafire.com/?mgldgtxc3gq
So did it end up working when flashing with your official rom?
well first try nope, no luck
It went through the install process and not all of the cabs installed (it copies everything to the phone and then runs individual packages) so i stopped the process in fear of bricking my phone.
Im stumped on this one, what could i of done when i replaced the screen that would stop the flashing process from working???
southect said:
well first try nope, no luck
It went through the install process and not all of the cabs installed (it copies everything to the phone and then runs individual packages) so i stopped the process in fear of bricking my phone.
Im stumped on this one, what could i of done when i replaced the screen that would stop the flashing process from working???
Click to expand...
Click to collapse
What cabs? The ROM is a .exe the first link placed on this thread is not the ROM it's the BT software update, run the BT ROM i placed link to and see if works?
Actually the first link is the newest ROM for his Phone from the BT Broadband website. I searched it quite extensively to find it. Newer then the one you posted.
Edit: http://bt.custhelp.com/cgi-bin/bt.c...at_lvl3=1978&p_cv=3.1978&p_cats=760,1851,1978
drkfngthdragnlrd said:
Actually the first link is the newest ROM for his Phone from the BT Broadband website. I searched it quite extensively to find it. Newer then the one you posted.
Edit: http://bt.custhelp.com/cgi-bin/bt.c...at_lvl3=1978&p_cv=3.1978&p_cats=760,1851,1978
Click to expand...
Click to collapse
Actually it's not it is an .msi install for the bt software update it's about 5mb in size and there is not a new bt ROM please use the link i provided....
I'm an ex BT user and i just knowz.... BT do not distribute the ROM....
Nevermind he's right, didn't read that page thoroughly...
ok thanks people, especially the person that 'searched extensively'!
I will try the link provided now and report back
Worked Perfectly
Thanks you guys, worked perfectly after i re-flashed to the original rom.
Will backup the Bt Rom for later use, just in case.
Thanks again
southect said:
Thanks you guys, worked perfectly after i re-flashed to the original rom.
Will backup the Bt Rom for later use, just in case.
Thanks again
Click to expand...
Click to collapse
Thats cool happy to help Always good to keep a copy back.
Glad to hear it, sorry for the wrong link...
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?