Related
Hi,
For warranty issues i have to send the pocket pc phone in for a replacement, but i have upgraded to T-Mobile 4.01 with the new radio Stack.
I can downgrade the OS to original 3.18 but the radio is not downgrading - can anyone please help and post instructions on downgrading to the original Radio...would greatly appreciate.
thanx
As far as i have read (and I've read several posts) there is no way to go back to a previous RS version.
If it is a hardware fault on the phone and is under warranty and not due to misuse like dropping it or breaking screen etc, I cant see that they would bother checking the radio version, probably just chuck in a box with a bunch of others.
Yeah... I've had to return a couple of them. I've always flashed them back to the old rom, but not the radio stack. I've never had any comments on it from TMObile.
I may have been wrong, I have heard that its possible to downgrade the same way you upgrade. Copy the original RUU files into the windows dir and run them. I hear that this might bring it back to it's original radio.
If you try and it works let us know, this is something that is discussed often but never really answered.
I returned a phone cause i dropped it and cracked the screen. I put the original rom back, but left the radio stack. they never mentioned anything.
But, my current problem could be due to the radio stack, cause the new phone i got often times turns off (soft reset). I don't want to call in a warranty issue until i can either put back the old RS or until t-mo officially releases the new one. So... if you find a way to do it, please, please let us know.
I tried the method ntwebguy mentioned, but with no luck, but i don't remember exactly how it failed... I think it just said a newer version already existed on the phone.
I assume there must be a way to do it for the sake of testing if nothing else, but I have not seen anyone that was able to.
John
john - it's most likely hardware, i've had 4 different XDA's from Tmobile and they all did the same thing. i'm in the same boat as you with 4.01 and 6.24 installed waiting for the official release to send this one back in.
that being said, i have an idea - too risky for me though
what if you "upgraded" to ATT or O2's radio stack and then "upgraded" back to Tmobile 6.18?
OK so I need some input and I did a ton of searching/asking around about this issue.
Firstly I was running Black IV and the camera application worked for a week or so and then it stopped and started the "camera will not initial, unable to open" and ultimately ended up that the camera app would not start or load at all.
Secondly I flashed back to the At&t Rom and WM5, I thought maybe the ROMS were bad etc. Now I don’t have the Camera Icon/Program in the Programs folder and it will not run when I find the file in the Windows folder??
Does anyone know what is going on with my phone or is this definitely a Warranty Replacement??
Here are my current specs
Windows Mobile 5.0 with Messaging & Security Feature Pack
OS 5.1.478 (Build 15706.3.5.2)
ROM version 2.15.502.3
Rom Date 04/09/07
Radio 1.40.30.00
Protocol Version 32.73.7020.16h
Thank you in advance for all of your suggestions and please let me know if more information is needed.
D
Anyone have any suggestions??
thanks.. D
Do a hard reset with the stock WM5 rom in there.
Also, if you do opt for warranty return, be sure you have the right IPL and SPL in there.
Thanks, I actually did the mrvanex downgrade guide for the ROM and Olipro.and then did the ROM update from HTC, I think that is factory specks..
and I did the whole hard start and battery out procedure.. it is just not there anymore..
Seems you can’t find a resolution with this problem, except warranty refurb
Hi guys...I know there have been numerous reports of this kind, but I can't seem to find the answer.
I don't have this problem myself, but another person does and I thought I'd ask Olipro and the rest of the community for some help and clarification. Also hoping this answer can help anyone else who has this issue.
OK, Someone tried to flash WM6 before using the Unlocker. I know...don't say it. Anyway they now have the black screen of death and the tri-coloured bootloader screen, but are still unable to flash WM6 and obviously cannot use the unlocker until they have an O/S to sync with.
Has anybody encountered this and received incorrect vendor ID and found a way out of this scenario? They have an Austrian T-Mobile Ameo UK, so they can't even use the T-Mob 005 ROM for the UK Ameo (which doesn't require the unlocking of ones device).
Any clues peeps? It would really help a fellow owner out. Cheers for any input. Remember even if you said it before and don't want to repeat yourself again, please just cpoy & paste the answer here so it can act as part of the wiki for future incidents of this nature.
Thanks friends.
I got part of the experience. So I will tell what happen to mine AMEO.
due to some software conflict, my WM6 OS got kill. I was stuck in the tri-colour screen as well.
Since my unit was unlocked before, so refreshing (any) ROM solved my problem. (refreshing the ROM doesn't required activesyn running on yr PPC.)
If can't reflash yr ROM due to vendor_id error, I think the best way is to get the origin WM5 ROM (read it out from another same model) and flash it back.
after getting yr origin OS, then u can proceed unlocker and WM6 upgrade.
Hope this can help.
royalmail said:
I got part of the experience. So I will tell what happen to mine AMEO.
due to some software conflict, my WM6 OS got kill. I was stuck in the tri-colour screen as well.
Since my unit was unlocked before, so refreshing (any) ROM solved my problem. (refreshing the ROM doesn't required activesyn running on yr PPC.)
If can't reflash yr ROM due to vendor_id error, I think the best way is to get the origin WM5 ROM (read it out from another same model) and flash it back.
after getting yr origin OS, then u can proceed unlocker and WM6 upgrade.
Hope this can help.
Click to expand...
Click to collapse
Thanks Royalmail. I'll pass it on.
Is the original WM 6.0 ROM for the vzw xv6800 up on the vzw or htc site?
(I'm paranoid so I really would like to download it from one of those two sites.)
Or are there tools that will allow me to copy the ROM out to later restore?
I ask because I'm about to upgrade to WM 6.1 and I want a rollback option before I take the plunge. Basically, I would hate to find out that after the upgrade one or more apps I have working on 6.0, stop working on 6.1. I would, specifically, hate to loose ability to make free international calls with Skype. (Has anybody got Skype working on 6.1?)
I don't think there is an easy way back as the 6.1 ROM also has a new Radio ROM and PRI version. You would have to contact VZW to get the 6.0 ROM but there is an unofficial one in the Wiki for the Titan. You would need to follow the process for taking your phone back to stock or 6.0 and see if it works or not. I would call VZW and see how they would advise on how to do this as well. Using both 6.0 and 6.1 I personally have not found any issues with any of my apps but there were a few that others did. You might check the build version in DCD's custom ROMs and see when his went to 6.1 and if people had any issues with any third party apps.
I'm going to give this a try anyway. After upgradeing to 6.1 from verizons link the bluetooth in my xv6800 wouldn't sync my contact listing with my 2007 mercedes e350 anylonger (it worked great when I was running the orig ROM with 6.0). And verizon support says I'm stuck at 6.1 whether I like it or not. UTC said the same.
So, my options are to either
A) upgrade my Benz to an 09 model that can handle this new bluetooth obx profile stuff so I can resync my contact list to my car. lol
B) pay for a new phone for $400 (yes, i'm so lazy I'd pay $400 just to get my contact list in my car back)
C) attempt to revert back to windows mobile 6.0
if I brick it or can't make any progress I go back to Verizon and show them I bricked my phone trying to upgrade and see what they say.
So, with that said, here is my plan. Someone correct me if I'm way off here or saying something you know or suspect will not work
http://wiki.xda-developers.com/index.php?pagename=TitanStockHome
WILL THOSE INSTRUCTIONS NOT WORK? It says in section II, step 7...
"Press the CAMERA-POWER-RESET buttons at the same time in order to enter the bootloader. You should see a screen that says SPL-2.07.0000. If you see this text, your SPL has been sucessfully updated. If you do not, power of your phone and start over from step 1. To return back to your phone, press the RESET button. "
well, I'm at 2.07.0000 right now so I should be good to proceed with the remaining instructions, correct?
OR... do I need to go thru the hassle of first moving up to 2.40 bootloader... then back down to SPL 2.07.0000 and THEN I proceed after section II step 7?
wish me luck.
Thanks,
Ben
Yep! It worked. I'm back at 6.0 now.
Just booted for the first time and it self installed all those first time CABs.
Now I'm restoring from an spb backup that I had made just prior to my upgrade to 6.1 and I should be back in business.
Ben
*edit: and my bluetooth in my phone is fully integrated and working my my mercedes once again... yay! 6.1 was pretty cool other than that one issue I was having. I wouldve left it at 6.1 otherwise. But its good to know you can go back if you really wanted too.
Thanks for blazing the trail, Ben. Skype stopped working for me (both the beta and the latest version). Looks like I'll be heading back to 6.0.
send me a message if you have any questions during your rollback. It is very simple to rollback to 6.0 from the verizon 6.1 ROM update.
Here is what I did:
I bought a 1 gig micro card and card reader and formated it to FAT32 from my laptop... format ?: /FS:FAT32 /A:1024
*where ? was the drive letter of my card
Then I downloaded the verizon stock ROM ruu_signed.nbh file and copied it to the root directory of the card... renamed it TITAIMG.nbh.
*edit: i used the stock verizon ROM from the wiki Titan Stock link... Verizon themselves do not have a 6.0 ROM, hard to imagine but thats what their support people said. Or maybe they think we, their customers, are too dimwitted to do anything with it.
plugged the card into the phone and then I pressed the POWER + CAMERA + SOFTRESET buttons (to enter into bootloader) and watched it do its stuff.
Then I had to call verizon support (from a different phone of course) after getting back into Windows 6.0 and they had me reprogram my phone by calling *228 and select option #1... then the support person gave me a new authentication number and they had to re-setup my ip address settings from their end.
WHen that was done and I confirmed I could make and receive calls and had data connection, I then restored my applications and contact info etc from a backup I took prior to upgrading to 6.1.
Then I was back to exactly how I was prior to upgrading to 6.1
The verizon guy was impressed. They hadn't heard of anyone being able to go back after upgrading to 6.1. Without the wiki links from this forum I wouldn't have been able to do it.
Thanks,
Ben
It really sux that vzw doesn't have a rollback for this. Not only does skype not work on this phone but I can't get my bluetooth GPS to work either. (yeah, I upgraded to 6.1 so I could use the built in aGPS but it does not look like aGPS works with mgmaps.) I'll be buying a 1GB microSD come Monday.
Thanks again, Ben.
well, I get to do this again. Yay!
I dropped my phone onto the cement sidewalk while I taking out the trash and damaged it pretty good.
Asurion (the insurance company I have my plan with) just shipped me overnight a new (refurbashed?) phone with the 6.1 already loaded. And yep, the OBEX bluetooth handsfree profile won't work with my car. The phonebook doesn't synch with my car. So I'm rolling back this one to 6.0 too.
Too bad really. I like 6.1. Anyone know if 6.1 is available on a cooked ROM but with the original vzw 6.0 bluetooth obex profiles?
Anyway, here I go again at least I know I can do it and I'm not stuck with 6.1
Ben
When you did the rollback to version 6.0, did it update your PRI back to the 1.35 version as well?
blancmik said:
When you did the rollback to version 6.0, did it update your PRI back to the 1.35 version as well?
Click to expand...
Click to collapse
I don't know what PRI is or to see what version it is. If you tell me where to view that I'll post what I find.
here are some of the #s I do know...
SPL 1.04
R 1.30.60
D 2.09
By the way, the rollback worked on this refurbashed phone that came pree loaded with 6.1... the rollback worked the same as when I rolled back my original phone with the VZW mr1 download. Except this latest time I didn't have to reauthenticate the number. They did have to reset my ip info though but that took only a few minutes.
I don't know why but I find this thread amusing. The 2007 benz os works fine with whatever radio and rom combination I have ever used. Did you try and and do a stock verizon 6.1 update? Let me share something and its not just because I am a tech junkie. I can obviously see that there is fear in updating outside of stock vzn rom, but let me paint a picture for you; DCD'S ROMS ARE FAR MORE STABLE AND PRODUCTIVE THAN ANY CARRIER ROMS. They have less junk that you don't need crash much less and sync with everything seemlesly. A bluetooth receiver for a titan? Come on. Do you know that you have a built in gps one receiver in your titan that with verizon you can have locking in 30 seconds or less every time? It is not hard to update to one of these roms, especially if you have everything backed up. If you pm me I will glide you through the process. It may take you 1-2 hours of your time but you will be so much more satisfied with your titan.
PM sent!
which 6.1 ROM do you recommend?
Thanks,
Ben
Something interesting for those of you who are downgrading...
If you follow the instructions on the Wiki, not only will it revert the phone to true stock condition (rom version, prl, pri, etc) but it will also restore your gpsOne settings.
I had a phone that has the bad pickles on the screen... I was bringing it into the store for a replacement and upgraded to MR1. They were of course out of replacements and shipped a dummy phone and I was in need of GPS (I had issues with the adapter program and iGuidance and MR1) so I reverted back to stock (following the WIKI instructions) and then DCD 3.34. I was having issues with GPS after reverting back and when I checked the gpsOne setting that I had made with the QPST program, my prior changes had been overwritten.
Just an FYI...
yeah, I rolled back from the mr1 using the wiki instructions and it is a pieace of cake.
actually my phone is doing all I need it to do at the moment and I've been exceedingly pleased with it.
guess i'm somewhere between intermediate and advanced. ha.
I may get bored ovr the holidays tho and try out the DCD 3.34 rom.
Sweeny, I sent you a PM... can you confirm the DCD3.34 works with your mercedes 2007 and can synch the contacts? would be good to have confirmation before I spend a few hours only to have to rollback again
thanks
Ben
blancmik said:
...so I reverted back to stock (following the WIKI instructions) and then DCD 3.34. I was having issues with GPS after reverting back and when I checked the gpsOne setting that I had made with the QPST program, my prior changes had been overwritten.
Just an FYI...
Click to expand...
Click to collapse
just to clarify, are you recommending against upgrade to 3.34 then because the gpsone setting gets overwritten?
thanks and I apologize for my newbish questions.
ben
well, I am an "intermediate" afterall. ha. I just read 30+ pages of the 3.3.4 rom and it looks great! but at the same time there are quite a few reports of people having some issues (keyboard, capslock, start menu dissapearing, etc.. that may all be install/user errors or related to version of the taskmanager they have).
But I've decided that since I'm intermediate level and admittidly a little "scared", I'm going to stick with my boring ole stock ROM at least for now.
Thanks for the info though guys.
*EDIT: well, I'm feeling adventurous. ha. I'm going to give the DCD 3.2.6 a shot tomorrow... and considering using radio 3.42.40 (or any reason not to try the 3.42.50?)... and the Nue SPL 2.47. Shoot, if it don't work all I've got to do is downgrade back to the stock vzw 6.0 right? I'm assuming I can still go back to that factory vzw 6.0 rom using the unlocked bootloader or at least using the lock 2.07 bootloader (the stock verizon bootloader is actually 1.04 and their isn't a way to get back to it after upgrading)
Oh, and blancmik... I did finally see where the pri # is in my EPST settings... yes, the rollback did set it back to 1.35_002
Also, thanks to Russ for the PM. appreciate the info.
This thread has shifted slightly off topic and I apologize for that... hopefully though it will give insight to the newbs who didn't like the factory MR1 6.1 UPDATE for whatever reason.
Thanks,
Ben
I've gotten really good at flashing ROMs, SPLs and Radios lately. lol. I've tried the VZW MR1 6.1 ROM... the DCD 3.3.4 and 3.2.6 both using the 3.37.20 radio and nue2.47 SPL. none of these 6.1 ROMs work with mercedes <=2008 model year bluetooth
Mercedes 2007 COMMAND system does not work with the obex bluetooth handsfree profiles in that the contact list from my phone does not synch with the mercedes. Incomming and outgoing calls work fine if I don't mind typeing them uing the dashboards keypad... but that defeats the purpose of the "hands free" profile.
With the good ole 6.0 factory rom and radio I'm able to use my steering wheel control buttons to scroll thru my address book, place/receive calls, adjust volume, speak thru the built in mic on the rearview mirror, and listen using the stereo system. Its one of my favorite features on the car and sucks that MERCEDES has not updated their firmware to handle 6.1 bluetooth profiles.
So I've once again, for the 3rd time, rolled back to vzw's original 6.0 ROM, RADIO and SPL (and pri too). I think I'll try some custom windows 6.0 ROMs sometime later but what I've got now works good for me (no GPS but I don't need it I guess)
THanks,
Ben
I am new in this type of phone and I bricked it. how I flash a rom with out HSPL and the phone dont do nothing only one thing when I connect to the computer it reconize it like Qualcomm CDMA Technologies MSM but now I dont know what to do to fix it. I think the phone is not damage because the pc reconize it. please help me fix it if there is away to . thankyou
sounds like you have flashed an incorrect radio. Did you by any chance try and flash a non tmous stock rom? Cos thats what happens if you flash an incorrect (non tmous) stock rom because they all include a radio that WILL NEVER work on the tmous.
The phone is dead. Sorry.
the rom I flash it work with my phone because I flash it before. The problem was that I flash my phone to stock and I forgot to HSPL to flash the same rom I had. I think there is a solucion for thins because the phone is like he does't have rom install.
I'm not too knowledgeable on this, but I think you flashed a wrong SPL base or something for the ROM you used to use. Having said that, making multiple threads does not accelerate the rate at which people respond to your problem, so please stop it.
what rom did you flash?
this the rom I flash NorgzRom.2.13.1.N0R.6Z tmous. I have it install on my other HD2 right now and it work perfectly. I brick it because I flash it without HSPL. I what to know if someone know's how to fix it. thanks
Let's see if I can sort the problem out, as your grammar leaves much to be desired.
You took a phone with a custom ROM already on it, and flashed it back to the stock ROM. Which stock ROM? The thing is, depending on how/which ROM you flashed, your unlocked version of SPL 2.08 could have been replaced with the updated and locked down SPL 2.10. Attempting to flash a custom ROM would then result in what you're seeing now.
You then decided to flash NorgzRom 2.13.
The phone now does not boot or do anything except for show up on your computer when connected via USB.
Does this cover what happened?
My suggestion is to attempt a Task 29; although I highly doubt it will work.
The symptoms you are having are the same ones that manifest when a bad radio is flashed. At this point if T29 fails call T-mobile, play dumb, and get the phone taken in under warranty. Currently there is no other solution.
Best of luck
kelkey said:
I am new in this type of phone and I bricked it. how I flash a rom with out HSPL and the phone dont do nothing only one thing when I connect to the computer it reconize it like Qualcomm CDMA Technologies MSM but now I dont know what to do to fix it. I think the phone is not damage because the pc reconize it. please help me fix it if there is away to . thankyou
Click to expand...
Click to collapse
Regarding your connection to the PC:
Don't worry about the "Qualcomm CDMA Technologies MSM" message -- many phones (including the HD2) when connected to the PC identify themselves in such a way as to match this driver. So the fact that Windows is seeing the phone and trying to install this driver is a good thing. Once Windows searches Windows Update it will identify the *correct* driver (something like "HTC USB Sync" if I remember correctly) and install it.
I believe you can also install this Windows Mobile Device Center update that will allow you to skip the step of searching for drivers on Windows Update.
tai4de2 said:
Regarding your connection to the PC:
Don't worry about the "Qualcomm CDMA Technologies MSM" message -- many phones (including the HD2) when connected to the PC identify themselves in such a way as to match this driver. So the fact that Windows is seeing the phone and trying to install this driver is a good thing. Once Windows searches Windows Update it will identify the *correct* driver (something like "HTC USB Sync" if I remember correctly) and install it.
I believe you can also install this Windows Mobile Device Center update that will allow you to skip the step of searching for drivers on Windows Update.
Click to expand...
Click to collapse
Ummm...what does that have to do with the fact that his phone will not boot?
I tried with windows mobile device center and active sync. but nothing happens.It keeps saing to install the drivers for this devices (Qualcomm CDMA Technologies MSM) .I hope some one get a anwser for this problem.I all ready got a new one because of the injurent but I wish to fix this one. here is the link for my video, so you can see the problem.Sorry for my bad ingles because I speak spanish,hope you understand http://www.youtube.com/watch?v=NZE70gwHmSc. please live comments. Thankyou!
Hi, I know you assured us the same rom was loadeed onto your other phone, but having just watched yor video, that is exactly what happens when you flash the wrong radio to a tmous. The phone wont turn on, nothing on screen, and when you connect to PC it shows up as qualcomm.
There are a fair number of posts with exactly this behavour, and all of them are down to the wrong radio.
It may be that it is just a coincidence and that the phone has died for some other reason, but I would guess the result is still the same - unrecoverable.
Still under warranty?
I have one question can I clone my new HD2 the one I have from the warranty with the one is damage. Our if there is a program that do this. I mean like transfer all the progaraming from the Hd2 (working) to the damage one. please if someone know's let me know. Thankyou very much!
There is nothing you can do. I know you wish there was because it is a lousy circumstance but you can't do anything once it's bricked. Get a new one if you haven't already and move on. I hate having to be so repetitive but you don't seem to understand. Plenty of people have bricked...just talk to T-mobile, act like you don't know what happened, get a new one under warranty, and move on.
~Jasecloud4
Help for bricked phone
samsamuel said:
sounds like you have flashed an incorrect radio. Did you by any chance try and flash a non tmous stock rom? Cos thats what happens if you flash an incorrect (non tmous) stock rom because they all include a radio that WILL NEVER work on the tmous.
The phone is dead. Sorry.
Click to expand...
Click to collapse
I think this what happened also to my unlocked Tmobile HTC HD2. I now have a bricked phone too...
With all our experts here, is there really no way that we can fix a bricked HTC HD2 besides sending it back to T-mobile?
allanbsutarez said:
I think this what happened also to my unlocked Tmobile HTC HD2. I now have a bricked phone too...
With all our experts here, is there really no way that we can fix a bricked HTC HD2 besides sending it back to T-mobile?
Click to expand...
Click to collapse
There is no way to undo the damage. You have to make sure you know exactly what you're doing when flashing a rom to your phone. All the experts in the world can't help you if you don't do your research first. It is your responsibility to make sure you are flashing a compatible rom or radio. I don't intend to sound harsh but you need to read, read, read then read again for good measure. Good luck and just play dumb when you contact T-Mobile.
Bricked hd2
I am kinda new to this forum. I just purchased my HD2 on June 30th and prior to that I was a Blackberry power user.
I have bricked my Blackberry devices MANY times and each time I was able to recover it so I had no fear of installing a new OS. It got so bad that every time a leaked or official OS was released for my Bold 9700 I would install it and Blackberry OS updates are released several times in a month sometimes.
But in the last couple of weeks of HD2 ownership I have "thought" about installing a cooked ROM but there is no room for error. I would hate to brick this HD2 and I just got it.
Hell.......I work in the IT field on workstations, servers......ect and I have no fear of working on those systems because I know I can recover the data and the system if need be. Since a bricked HD2 is basically a pretty paperweight I will wait until I am seriously comfortable with the process.
Until that time I'll just continue to pick up tips and tricks for this great device!
squire366 said:
I am kinda new to this forum. I just purchased my HD2 on June 30th and prior to that I was a Blackberry power user.
I have bricked my Blackberry devices MANY times and each time I was able to recover it so I had no fear of installing a new OS. It got so bad that every time a leaked or official OS was released for my Bold 9700 I would install it and Blackberry OS updates are released several times in a month sometimes.
But in the last couple of weeks of HD2 ownership I have "thought" about installing a cooked ROM but there is no room for error. I would hate to brick this HD2 and I just got it.
Hell.......I work in the IT field on workstations, servers......ect and I have no fear of working on those systems because I know I can recover the data and the system if need be. Since a bricked HD2 is basically a pretty paperweight I will wait until I am seriously comfortable with the process.
Until that time I'll just continue to pick up tips and tricks for this great device!
Click to expand...
Click to collapse
There is plenty of room for error , but the ONE thing you cannot do is flash an incompatible Radio, out of all the things you can do that is only one, the MAIN one ...
If it is a TMOUS HD2, which I assume it is you cannot flash any radio to be safe, prior to 2.08 or any radio that has x.xx.51.x in it ... Pretty much anything else you do short of a hardware failure there is a recovery option ...
so TMOUS HD2 Nothing but Official TMO ROMs or TMOUS compatible custom ROMs and TMO Compatible Radios ...
EU ROMs , may brick your device if they have a radio ..
HTC ROMs , may brick your device if they have a radio
Hey all! I'm kinda new to this windows mobile stuff also...I used to be a blackberry man, but couldn't resist the hype on the htc hd2 so i jumped on the wagon and got one. I'm paying full price ($400.00) so I am definitly afraid of doing a rom flash. After reading all the horror stories on here and seeing all the different roms out there...it's just to risky for me. The last thing I need in this economy is a $400.00 paper wieght. There has to be an easier way to do this rom stuff. Does anyone know of a rom that works for sure...or are they all problematic?
kelkey said:
I tried with windows mobile device center and active sync. but nothing happens.It keeps saing to install the drivers for this devices (Qualcomm CDMA Technologies MSM) .I hope some one get a anwser for this problem.I all ready got a new one because of the injurent but I wish to fix this one. here is the link for my video, so you can see the problem.Sorry for my bad ingles because I speak spanish,hope you understand http://www.youtube.com/watch?v=NZE70gwHmSc. please live comments. Thankyou!
Click to expand...
Click to collapse
did you try the wmdc update in the prev. post that has the drivers?
nrfitchett4 said:
did you try the wmdc update in the prev. post that has the drivers?
Click to expand...
Click to collapse
This threads from May. His phones probably been replaced...