|
||||
Re: WinMo 6.5 Pro stock ROM
Quote:
http://forum.ppcgeeks.com/showthread.php?t=91940 |
This post has been thanked 1 times. |
|
||||
Re: WinMo 6.5 Pro stock ROM
Ether of these 2 should be fine to send back
RUU_Rhodium_W_VERIZON_WWE_1.18.605.12_RS_1.88.07WV _NV_VZW_1.65_0811_PRL58002_Ship.exe RUU_Rhodium_W_WM65_VERIZON_WWE_3.04.605.3_RS_2.23. 00WV_NV_VZW_1.94_1111_PRL58005_Ship.exe |
This post has been thanked 1 times. |
|
||||
Re: WinMo 6.5 Pro stock ROM
Some Verizon TP2's come with 6.1 and some newer ones shipped with 6.5. I've had 2 replacements with 6.1, but the latest one I got was 6.5. Doesn't really matter
__________________
|
This post has been thanked 1 times. |
|
||||
Re: WinMo 6.5 Pro stock ROM
I'm tryin'! Lots to learn still.
I appreciate your help, especially you and Wesley762. You guys always answer my questions promptly! ...and on that note! I asked these question on the Energy thread, but that thread is huge and most likely got lost. I just flashed the Energy Cookie rom (can't remember the build, but it was the bigger of the numbers). If I tap 'Notifications' it says "Sprint - Connected". I'm on Verizon. I didn't run any sort of "Provisioning" but everything seems to run fine, including MMS. Also, for the life of me, I can't find the settings for the keyboard backlight. Could you guys point me towards this? Thanks again guys! Aaron |
|
||||
Re: WinMo 6.5 Pro stock ROM
When you go into messaging, try to type all you "function" buttons. I believe the keys for parenthesis are switched. If all fn keys work fine, then it should be provisioned correctly.
For the keyboard backlight, slide to settings tab>menu>all settings>personal>buttons>backlight (should be third from left) This will give you a box to check if you want auto sensor on keyboard backlight or no. Hope that is what you were looking for |
This post has been thanked 1 times. |
|
||||
Re: WinMo 6.5 Pro stock ROM
Quote:
|
This post has been thanked 1 times. |
|
||||
Re: WinMo 6.5 Pro stock ROM
Quote:
I had to run a .cab to fix the keyboard mapping, which worked. I did get a message this morning when trying to use the phone that "the system was unable to detect my phone" or something along that line. I did a *228 and that fixed it. I'll have to see if that happens again. Thanks again! Aaron |
|
|
|