[WM 6.5 v16] ROM Update Question(s) - Touch CDMA Windows Mobile ROM Development

All,
I'm upgrading what I believe to be a pre-release verizon Vogue. When I boot the device a series of numbers pop up
M 03
B 01
P ACAAAAM-4070
R 1.60.30
D 1.15
When I hold the power+camera+reset, I get the following at the top:
VOGU100
SPL-0.36.0000
CPLD-3
Can anyone tell me what these mean, and if that confirms the device is already unlocked? These same numbers showed up when i unlocked a phone years ago (the last time I tried to do this).
Now, when I run RUU (MFG 2.31 unlocker), I the 'verifying information' part does not seem to be gathering much info. The Image Version has NOTHING listed (see screenshot). If I try to begin the update, it shows the update version as 'Unlocker 2.31' (see screenshot).
Is this expected?
When I start the update process, it kicks off and suddenly errors with a "ERROR [262]: UPDATE ERROR" Message reads: "The ROM Update Utility has encountered communications errors during the update process." Screenshot provided of the Vista mobility center.
Update: I've also experienced an application failure "Windows Mobile-2003-based device connectivity has stopped working" in Vista. See latest attachment.
Any insight would be greatly appreciated.
-zarfu
Update: MicroSD card was in the phone at the time
Update2: Added Vista application failure screenshot
Update3: I should also disclose, i'm running Windows Vista SP1 64-bit

zarfu said:
All,
I'm upgrading what I believe to be a pre-release verizon Vogue. When I boot the device a series of numbers pop up
M 03
B 01
P ACAAAAM-4070
R 1.60.30
D 1.15
When I hold the power+camera+reset, I get the following at the top:
VOGU100
SPL-0.36.0000
CPLD-3
Can anyone tell me what these mean, and if that confirms the device is already unlocked? These same numbers showed up when i unlocked a phone years ago (the last time I tried to do this).
Now, when I run RUU (MFG 2.31 unlocker), I the 'verifying information' part does not seem to be gathering much info. The Image Version has NOTHING listed (see screenshot). If I try to begin the update, it shows the update version as 'Unlocker 2.31' (see screenshot).
Is this expected?
When I start the update process, it kicks off and suddenly errors with a "ERROR [262]: UPDATE ERROR" Message reads: "The ROM Update Utility has encountered communications errors during the update process." Screenshot provided of the Vista mobility center.
Update: I've also experienced an application failure "Windows Mobile-2003-based device connectivity has stopped working" in Vista. See latest attachment.
Any insight would be greatly appreciated.
-zarfu
Update: MicroSD card was in the phone at the time
Update2: Added Vista application failure screenshot
Update3: I should also disclose, i'm running Windows Vista SP1 64-bit
Click to expand...
Click to collapse
OK
1.make sure the Phone is connected through Activesync
2.it is supposed to show unlocker_2.3.1 when trying to update YOU MUST UPDATE IN ORDER TO PUT CUSTOM ROM AND CAREFULLY DO WHAT THE COMPUTER TELLS YOU

Thanks - can you clarify 'make sure the phone is connected through activesync'
Vista SP1 has the Mobile Device Center which manages the connection. That connection is failing due to the application failure I sent in the udpated thread. it may be easier for me to walk through the steps and you identify any changes that are necessary:
1. Boot the phone, establishing and verifying the connect between the phone and Mobile Device Center
2. Unplug USB cable
3. Power+Camera+Reset to Rainbow/'Serial'
4. Plug USB cable in
(At this point, Mobile Device Manager does not show a connection of course, but the device is recognized through in device manager as 'microsoft usb sync')
5. Run RUU (2.31 unlocker)
---> At the point where RUU says 'verifying information', the Microsoft crash agent kicks in with the failure shown in Capture4.jpg
The docs and readme's do not have troubleshooting steps for this fault.
Again, any help would be greatly appreciated.
-zarfu
Update: I have tried all these sets on a Vista 32-bit home edition laptop, and the same failures occur. This biggest missing piece I see is the references to 'ActiveSync.' There is no build of ActiveSync for Vista or beyond - that product was sunset for Mobile Device Center i suspect. As anyone successful run this on Vista and beyond, or do i need to roll-back to XP to use ActiveSync?

Not sure if you have tried this or not as it's unclear in your first post, have tried simply establishing a connection and running the unlocker skipping going into bootloader entirely? it should automatically put you into bootloader if my memory serves me.

Worked. Thank you!
3.9 ROM is up and running. What's with the crappy old digital keyboard. I thought Microsoft had changed the keyboard to be finger friendly...

zarfu said:
Worked. Thank you!
3.9 ROM is up and running. What's with the crappy old digital keyboard. I thought Microsoft had changed the keyboard to be finger friendly...
Click to expand...
Click to collapse
Great stuff!! What's the 3.9 ROM?, thought you were installing NFSFAN's rom as you said 6.5 v16.

Yes, ignore that comment. I was trying out two different builds, and confused the two. Thanks again for the help.

Related

Serious Problem here guys...

So i downloaded WM6 Black 2.0, and its constantly crashing, so i wanted to re-install it and see if that helped.
now whenever i try to launch the file, i get an error message that states
"custom RUU has encountered a problem and needs to close. we are sorry for the inconvenience."
So im wondering what changed that wont allow me to run the ruu file? Im kinda freaking out here because i need to get my phone working! its constantly crashing on me!
i hope someone knows a fix for this, i tried to search but came up with nothing
newnoise1024 said:
So i downloaded WM6 Black 2.0, and its constantly crashing, so i wanted to re-install it and see if that helped.
now whenever i try to launch the file, i get an error message that states
"custom RUU has encountered a problem and needs to close. we are sorry for the inconvenience."
So im wondering what changed that wont allow me to run the ruu file? Im kinda freaking out here because i need to get my phone working! its constantly crashing on me!
i hope someone knows a fix for this, i tried to search but came up with nothing
Click to expand...
Click to collapse
Looks like a problem on your PC... (I mena for the Customruu crashing)
newnoise1024 said:
So i downloaded WM6 Black 2.0, and its constantly crashing, so i wanted to re-install it and see if that helped.
now whenever i try to launch the file, i get an error message that states
"custom RUU has encountered a problem and needs to close. we are sorry for the inconvenience."
So im wondering what changed that wont allow me to run the ruu file? Im kinda freaking out here because i need to get my phone working! its constantly crashing on me!
i hope someone knows a fix for this, i tried to search but came up with nothing
Click to expand...
Click to collapse
Had this happen to me. I downloaded .net framework 3.0 from the M$ site and then it worked fine.
Maybe that will help you.
Jim
Need more info?
newnoise1024 said:
So i downloaded WM6 Black 2.0, and its constantly crashing, so i wanted to re-install it and see if that helped.
now whenever i try to launch the file, i get an error message that states
"custom RUU has encountered a problem and needs to close. we are sorry for the inconvenience."
So im wondering what changed that wont allow me to run the ruu file? Im kinda freaking out here because i need to get my phone working! its constantly crashing on me!
i hope someone knows a fix for this, i tried to search but came up with nothing
Click to expand...
Click to collapse
Ok, first off, this is not a flame. It's an education, ok?
When posting a problem, it's best practice to let us know your:
Model of phone
Radio version
Boot Loader version
OS on your PC
ActiveSync version (s/b 4.5 by now)
Then, and only then, will you be able to get some intelligent answers. You also need to follow the link in my signature and there you will find answers.
If you're still stuck, usually re-downloading the RUU will result in a working ROM patch, unless you have other PC issues. You really need to fix that first, and the guides posted here are FULL of the diagnostic and troubleshooting steps that will propel you to a successful resolution.
Please read those posts, add your info, and you may be extremely pleased with the results.
Good reading!
newnoise1024 said:
So i downloaded WM6 Black 2.0, and its constantly crashing, so i wanted to re-install it and see if that helped.
now whenever i try to launch the file, i get an error message that states
"custom RUU has encountered a problem and needs to close. we are sorry for the inconvenience."
So im wondering what changed that wont allow me to run the ruu file? Im kinda freaking out here because i need to get my phone working! its constantly crashing on me!
i hope someone knows a fix for this, i tried to search but came up with nothing
Click to expand...
Click to collapse
First off; relax. At least the problem isn't with your phone. It's a heck of a lot easier to fix a PC.
I assume you've already tried to re-download the file?
Did you completely reboot your PC? Shut it down to power down, then restart. Make sure you don't have any extra USB stuff plugged in (like cameras, etc). If you have a PS/2 mouse and KB, use those, and not USB versions. One trick is to have the USB bus on your computer completely empty except for your phone.
Head over to Microsoft's site and download a fresh version of Compact Framework .NET (3.0 is the current version). Reboot after installing it -- even though it doesn't tell you to.
Run Windows Update. Make sure you're OK on those.
If that doesn't work, try downloading another ROM (OS only) -- like the Cingular Black 2.02 or the LVSM ROM, and see if that works.
You can also strip it apart -- use WinRAR to open the EXE file that you've been executing and extract the .nbh file from the EXE. Then go and download this guy: http://wiki.xda-developers.com/index.php?pagename=Hermes_CustomRUU and extract it into its own folder. Copy that .nbh file into that directory, and execute the executable -- it will flash your phone with a known good flasher.
But.... stepping all of the way back ... if the ROM doesn't work on your phone, it's very likely reflashing it won't help a single bit. Those ROM's are checksummed when they go on the phone -- if they're corrupted, they won't load right in the first place (and you'd end up with a boot-loader only phone). Soo... uh.. first, reboot/clean USB, then try a different ROM.
Last resort will be completely reinstalling Windows XP. I've had to do this several times because Windows will get in some weird state and it refuses to flash my phone. I finally gave up and started flashing on my Mac using a Windows virtual machine -- it's a lot easier to restore my Windows system to a working point when I do that.
Thanks to everyone who gave a response!
Here's all the information i was asked to post ( i will remember this for next time)
Cingular 8525 HERM100
Radio version: 1.40.30.00
Boot Loader version: (Not quite sure what this is?)
OS on your PC: Pro Black 2.0
ActiveSync version 4.5
I have redownloaded the ruu about 3 times and it has failed everytime.
Restarted the PC, disconnected everything from my laptop, realized that i havent installed Framework .NET 3.0, ( although i have it on my phone as i needed it to run hitchhiker)
So i'm going to download framework .NEt 3.0 and run it.
As for my phone, i uninstalled all the apps, hard resetted and everything is working fine right now, hasn't froze at all since yesteray, so im going to wait it out and see if something happens again.
Thanks again to everyone!! This forum is really really helpful.
-Matthew
How to determine the bootloader version
newnoise1024 said:
Boot Loader version: (Not quite sure what this is?)
-Matthew
Click to expand...
Click to collapse
You need to have a look at your user guide, as it states how to enter bootloader and check the version. Otherwise press and hold the left OK button and the power button at the same time, then hit the reset button with your stylus. You will enter a tri-color screen. This is bootloader mode. Jot down the numbers and compare against the below link.
Exiting is simple, press the reset button with your stylus.
Here's a valuable link for updating your bootloader.
Bootloader Version: SPL-1.40.01pro
IPL-1.01
i just tried to install Framework .NET 3.0 and got this error message
[04/20/07,08:50:20] Windows Communication Foundation: [2] Error: Installation failed for component Windows Communication Foundation. MSI returned error code 1603
[04/20/07,08:57:35] Windows Communication Foundation: [2] Error: Installation failed for component Windows Communication Foundation. MSI returned error code 1603
[04/20/07,08:57:54] WapUI: [2] DepCheck indicates Windows Communication Foundation is not installed.
[04/20/07,08:57:54] WapUI: [2] DepCheck indicates Microsoft .NET Framework 3.0 was not attempted to be installed.
i uninstalled any previous version, is there something i'm missing?
.Net Framework co-existence
newnoise1024 said:
Bootloader Version: SPL-1.40.01pro
IPL-1.01
i just tried to install Framework .NET 3.0 and got this error message
[04/20/07,08:50:20] Windows Communication Foundation: [2] Error: Installation failed for component Windows Communication Foundation. MSI returned error code 1603
[04/20/07,08:57:35] Windows Communication Foundation: [2] Error: Installation failed for component Windows Communication Foundation. MSI returned error code 1603
[04/20/07,08:57:54] WapUI: [2] DepCheck indicates Windows Communication Foundation is not installed.
[04/20/07,08:57:54] WapUI: [2] DepCheck indicates Microsoft .NET Framework 3.0 was not attempted to be installed.
i uninstalled any previous version, is there something i'm missing?
Click to expand...
Click to collapse
You're probably missing version 2.0 of the .NET framework. .NET Framework is to be left in place once installed. You should have left V 2.0 installed and added .NET 3.0. Go to www.microsoft.com/net and get version 2.0 redistributable re-installed on your machine. (If you can). If you cannot, search the KB and you may get by without rebuilding your OS.
"Head over to Microsoft's site and download a fresh version of Compact Framework .NET (3.0 is the current version). To be extra safe, go into Add/Remove Programs and uninstall any existing versions -- reboot -- then install the new CF Framework. Reboot after installing it -- even though it doesn't tell you to."
this is the advice i was given in this thread, so i uninstalled version 2.0 before installing version 3.0.
So am i screwed now? lol
Well, version 3.0 just installed successfully... does that mean i still need to install 2.0? or am i fine just running 3.0?
Sorry for all the questions, i just want this fixed :/
You should be good. Give it a go.
If not, just dl .Net CF2 and install that. I think you are fine now though.
Edit: never mind
version 2.0 installed fine
Thanks everyone

Update just radio in Vista

I have a TyTN with official Russian WM6 onto it, which includes 1.16 radio version. I want a newer one, because this seems unstable, so i decided to update just radio (i don't want any cooked ROM or whatever for now).
Each new version of radio I found here failed earlier or later on a Vista x64 computer with error 260. What I have tried is 1.54.07.00 and 1.54.00.10 and 1.50.
To my surprise, packaging is different, but the effect is the same: after "Verifying the image on your device" (i can hear USB disconnecting and connecting back as the device enters bootloader) they time out with 260.
Right now I'm trying to revert what have I done to Vista as it won't allow me to turn off driver signing, as advised.
Ah, this doesn't work either (same error 260).
What am I doing wrong? My bootloader is, as said on that screen:
Code:
HERM200
IPL-1.01
HERM200
SPL-1.40.Olipro
Yes, I have installed some...er...thing before, maybe it was called "HardSPL", but it didn't come handy and wasn't any use to me as I decided against cooking a ROM.
Update: What I like the most is, despite all my attempts the device still works! Other than the radio troubles, that is.
I've updated from an SD card.
Try this my friend... http://www.mrvanx.org
Thank you, I did.
Please note the x64 drivers are unsigned so to use them successfully you must disable driver signing.
Click to expand...
Click to collapse
This is what I'm unable to do, but I suppose is beyond this forum.
Hi
I have had the same problem with my x64 vista pc and the 260 error msg. It took me hours but what seemed to finally fix it for me was to:
1. completely remove WMDC from the pc, reboot the pc,
2. reinstall WMDC plus upgrade,
3. uncheck the allow USB connections option on your 8525, exit out of the window, then do a soft reset
4. now make a USB connection w the PC
Let us know how it works
Sorry, you'll have to wait till my next upgrade Everything is working so far - so until I need something that can't be achieved using SD flashing I'll stick to this technique. Thanks for the advice anyway.

[Question] 260 error when updating ROM

Okay, I've searched alot to get this thing solved. When I try to update my rom, the update starts normally, but then my telephone screen turns black, my gets disconnected, windows tells me it has found new hardware. The update failes and returns error 260 (connection lost). When I soft-reset the telephone afterwards, it returns to it's old shape.
Info about my telephone.
Rom: 1.93.404.1 NLD
Radio: 1.0025.05
PC: Windows XP SP 3, Active Sync 4.5
I tried to update with this rom: RUU_Diamond_HTC_NLD_2.03.404.3_Radio_Signed_Diamond_52.51.25.26_1.09.25.23_Ship.exe
I also tried to update to Hard-SPL but that gave me the same error.
PLease guys does anyone of you know how to fix this? (personally I think it's windows xp which is screwing up).
Thanks in advance, I appreciate all help.
Yours, Martijn.
Even the tiniest tip may help (A)
I had the same trouble with that rom, I tried from internal memory and it worked. Search the wiki I am sure the info is there.
"ERROR [260] : UPDATE ERROR
This error occurs when there is an "open port error" before upgrading the CE ROM image. Solution: You can reset the device and run RUU again. If you still encounter an "OPEN PORT ERROR" again, reset your computer and try again."
This is what the WIKI tells me. But I have tried that. How did you manage to perform the update on the internal storage? Because I tried that with hard-spl but it wouldn't work.
Besides I only have .exe files for the Hard-Spl and the official rom from HTC.
Thanks for your reply though.
EDIT PART, just read this on another thread in the wiki:
ERROR 260 (Update Error):
"Your phone is not connected to ActiveSync. Check your connection or restart the phone. Also make sure in ActiveSync that "Allow USB connections" is checked (under File->Connection Settings). If this still doesn't help, then remove the memory card and SIM card before flashing."
I'm going to try this now, if it worked, I'll let you know
Just found out I have a CDMA version or something, I'll try google for the problem now.
Get the rom image from your temp directory and look here, found in the wiki
http://wiki.xda-developers.com/index.php?pagename=Diamond_FlashfIS
Does the hardware install incorrectly? My laptop did this on XP.
XP would find the new hardware, my bootloader would say USB. Then it'd tell me new hardware could not be installed properly and from there my phone suffered those symptoms - Back to where I was. Funnily enough it eventually fixed itself.
dickenz said:
Does the hardware install incorrectly? My laptop did this on XP.
XP would find the new hardware, my bootloader would say USB. Then it'd tell me new hardware could not be installed properly and from there my phone suffered those symptoms - Back to where I was. Funnily enough it eventually fixed itself.
Click to expand...
Click to collapse
It looks alot like your problem yes. But last time the hardware installed correctly, then the patch I found for CDMA models on ppcgeeks failed, and my telephone got bricked. So I'll need to get that fixed first. After that I'll sure think twice before I try another rom update :/
Thanks for all the help though, and I have to advice everyone to not use the hard-spl for cmda users from ppcgeeks unless you're 100% sure it fits your model!

Cant upgrade to hard spl

Hi all, i just bought my HTC diamond today and it came with the spl 1.93.00.. I tried upgrading to the signed and unsigned versions of Olinex 1.93 hard spl..... But the process starts but the progress bar is stuck at 0% and is not moving.... Can someone please help me out.
Hi 1onew0lf,
I have very similar problem, spent the whole day trying to update to Hard-SPL
I have a MDA Compact IV - T-Mobile (German) version of Diamond.
The original SPL, if I go to a boot loader mode, shows:
DIAM200 64M
SPL-1.93.0000
MicroP-Diam (LED) v11
PSOC-Vict STAGE_PVT v0x20
Click to expand...
Click to collapse
Original ROM Versions are:
ROM-Version: 1.93.111.2 GER
ROM-Date: 09/24/08
Radio-Version: 1.00.25.16
Protocol-Version: 52.29a.25.13U
Click to expand...
Click to collapse
When I try to run ROMUpdateUtility.exe after answering "Yes" (Ja) on the screen of Diamond on the request to place the enterbootloader.exe into \Windows directory the device goes black screen and never comes back.
After 1-2 min. the ROMUpdateUtility.exe utility gives an Error 260: CONNECTION and informs that USB is disconnected, the Active Sync is already long time grayed out.
I tried a trick described in the pinned forum to run SSPL manually: I copied SSPL-Manual.exe into a Temp folder on the device and launched it from Diamond with the same effect: black screen till I do a soft reset of device. I have found somewhere a tip to update the .NET CF to the latest version, and I did so have now .NET CF 3.5 on the device, it didn't solve the problem.
So I may assume that device somehow is not able to switch to SSPL mode, but nobody speaks of such problems!
Looking for anyone who may help us to solve this problem!
Thanks in advance!
yepiee! I actually did it! I managed to update to Hard-SPL
So, first of all the black screen IS actually the SSPL mode of device. My only problem was that USB drivers were not automatically configured. I'm not sure is it a problem with Windows XP SP3, or I messed up some settings for USB devices long time ago.
So what I did is before starting ROMUpdateUtility.exe I opened the Windows Device Manager and placed at the background. Then started the regular procedure of updating to Hard-SPL.
At the moment the screen of the device turned to black a new USB device appeared in the Device Manager, but with exclamation sing giving me a hint that no proper driver found/configured automatically.
Right click -> Update driver... -> Search for suitable driver - did a trick for me. I picked up a second driver from the list of choices with number 32 instead of 16. After the driver was successfully installed the update continued and eventually ended with congratulation message about successful update!
I hope my experience may help someone as well.
endlessspace said:
yepiee! I actually did it! I managed to update to Hard-SPL
So, first of all the black screen IS actually the SSPL mode of device. My only problem was that USB drivers were not automatically configured. I'm not sure is it a problem with Windows XP SP3, or I messed up some settings for USB devices long time ago.
So what I did is before starting ROMUpdateUtility.exe I opened the Windows Device Manager and placed at the background. Then started the regular procedure of updating to Hard-SPL.
At the moment the screen of the device turned to black a new USB device appeared in the Device Manager, but with exclamation sing giving me a hint that no proper driver found/configured automatically.
Right click -> Update driver... -> Search for suitable driver - did a trick for me. I picked up a second driver from the list of choices with number 32 instead of 16. After the driver was successfully installed the update continued and eventually ended with congratulation message about successful update!
I hope my experience may help someone as well.
Click to expand...
Click to collapse
Thx, your hint was very helpful!

i780 WM upgrade query

Hey guys, really been enjoying the forum. Spent all of time reading so far. Now it's time to act.
Going to upgrade my Samsung i780 with this rom SGH-i780 WM 6.5.3 WWE PRE-RELEASE from heineken78.
Hit the first possible snag which I am sure someone here can help me with.
Trying to upgrade first to PDXIB1, but the installer says I have the incorrect software version.
PDA : i780JCHC2
Phone : i780JCHC2
How would I get my version to a version that can be updated. had a seach in the forums for my version number, came up empty. Mustn't be too many people South Africa on here then
{EDIT}
Well got I sorted, I bypassed the step to update to PDXIB1 and just flashed it with WM6.5 works perfectly.
Thanks in advance.
Be interested to know exactly how you did that. I have been trying (unsuccessfully) to upgrade to PDXIB1 as well.
Now tried going straight to this pre-release but keep getting "Emergency Mode - You must push detect button...before you connect the USB port". I have hit detect but as soon as the phone switches on Mirage simply says "PDA device not found".
I haven't got an XP machine and cannot download XP mode. I can run Vista or Win 7. I haven't found usb drivers for Win 7. I assume this is the problem.
I really want to get rid of the Orange branding (as the phone is now out of contract) so any help would be greatly appreciated. TVM.
Have now tried Win7 in XP compatability mode and Mirage starts but then hangs on reading the bin file. I don't know what to do next.
I've now considered Virtual PC running XP and activesync, but I believe this does not support USB. Anyone any ideas please?

Categories

Resources