Apache WM6 CE OS 5.2.1620 (Build 18125.0.4.2)

[pdx77]

As this thread is going to grow large, and to help keep things a little organized
Let's post all bugs in this thread:
http://forum.ppcgeeks.com/showthread.php?t=7780

But I want to say that this is great! I've been running it since last night, and 0 lock ups so far =0) Great job helmi on another great release.

[cheeb]

i would just like to say i've been using this since about 12:30 MIDNIGHT...and this thing is rediculous....i can't believe we're using Win Mobile 6 on Apache...awesome job Helmi...

BTW....those having issues...i'm kinda confused....he packaged the rom in one executable...now...you can go ahead and do bootloader if you like...but that wasn't necessary...just plug your ppc 6700 into the computer and run setup....(I have vista btw)...your phone will automatically go into botloader mode....and after about 3-5 min. your phone will be considered gold...

I have a question...

With Internet Sharing, is Phone as Modem option and Sprint PCS connection option any different? I usually use internet sharing without issue...but i noticed this option on the mogul..and i know that the mogul wasn't "fixed" to have sprint not recognize...

will that "change" with this rom or not...thanks

[taiwo989]

Thanks Helmi,

This is indeed a great job. Theres a bug i noticed on the sprint version. When a text message comes in, you cant see the name or number of the person that sent the text message to you. so when you tab "reply" on the return address it has the first couple of lines of the text message received as the contact name. This means you have to always guess who sent you the message and then compose a new message to them. .

[track2]

I'm trying to follow the instructions that Hemli laid out at the start of the thread. He mentions to put the device in bootloader mode, then run the updater app. I'm running Windows Vista on my PC. If I put the device in bootloader mode then connect I get a 101 NOT CONNECTED error. If I just have the 6700 running normally, plug it in, then run the updater, it detects my phone just fine and is ready to upgrade.

Am I creating a problem by NOT having the phone in bootloader mode? Just want to verify before I pull the trigger.

[on-line]

Originally Posted by track2

I'm trying to follow the instructions that Hemli laid out at the start of the thread. He mentions to put the device in bootloader mode, then run the updater app. I'm running Windows Vista on my PC. If I put the device in bootloader mode then connect I get a 101 NOT CONNECTED error. If I just have the 6700 running normally, plug it in, then run the updater, it detects my phone just fine and is ready to upgrade.

Am I creating a problem by NOT having the phone in bootloader mode? Just want to verify before I pull the trigger.

I am still having the same issue, I see that everyone else seem to be working so I wonder why a select few of us are having issues. Maybe there is a common theme. My boot loader is version 2.04. The last successful upgrade was using the Bell Mobility direct from the UTstarcom site. I can alway reinstall the Bell one just nothing else. I tried using kirvin rom just as a test and it also fails. Could there be something wrong with our bootloaders? Is it possible to install a newer, better bootloader?

Thanks

[naigaboy]

Originally Posted by on-line

I am still having the same issue, I see that everyone else seem to be working so I wonder why a select few of us are having issues. Maybe there is a common theme. My boot loader is version 2.04. The last successful upgrade was using the Bell Mobility direct from the UTstarcom site. I can alway reinstall the Bell one just nothing else. I tried using kirvin rom just as a test and it also fails. Could there be something wrong with our bootloaders? Is it possible to install a newer, better bootloader?

Thanks

Hmmm your bootloader might be the problem. But try this, extract the bell ROM u used and extract the wm6 ROM you just downloaded. Replace all the RUU files in the WM6 folder with the files from the bell folder, then flash wm6. Come to chat room, so we can help easier.

[erock123]

Originally Posted by naigaboy

Hmmm your bootloader might be the problem. But try this, extract the bell ROM u used and extract the wm6 ROM you just downloaded. Replace all the RUU files in the WM6 folder with the files from the bell folder, then flash wm6. Come to chat room, so we can help easier.

Flash "bricked" my phone? Don't know if it's relevant WinXP via VMWare Fusion. Successfully upgraded my phone in past on this OS. This Sprint WM6 "Helmi" ROM flash seemed to result in a 101 error after confirmation dialogue (you're going from this version to this version). Now it's not detectable via USB (ActiveSync), etc. It seems to be stuck in "bootloader" mode (Gray screen that states Serial/USB and Ver 2.02 at the bottom). I tried to run uni_exitbootloader.exe as it was recommended by helmi (diff. post) to bring a device out of bootloader mode - no success - error msg about "cannot open USB port..." even though I killed the activesync process. As ActiveSync doesn't seem to be detecting the device (when restarted) it's not possible to reflash or return to OEM ROM. I'm a n00b admittedly but none of the wiki pages or other forums seemed to address a scenario like this. Help, please?

Thanks,

-E

[gguruusa]

Originally Posted by erock123

Flash "bricked" my phone? Don't know if it's relevant WinXP via VMWare Fusion. Successfully upgraded my phone in past on this OS. This Sprint WM6 "Helmi" ROM flash seemed to result in a 101 error after confirmation dialogue (you're going from this version to this version). Now it's not detectable via USB (ActiveSync), etc. It seems to be stuck in "bootloader" mode (Gray screen that states Serial/USB and Ver 2.02 at the bottom). I tried to run uni_exitbootloader.exe as it was recommended by helmi (diff. post) to bring a device out of bootloader mode - no success - error msg about "cannot open USB port..." even though I killed the activesync process. As ActiveSync doesn't seem to be detecting the device (when restarted) it's not possible to reflash or return to OEM ROM. I'm a n00b admittedly but none of the wiki pages or other forums seemed to address a scenario like this. Help, please?

Thanks,

-E

Once you are in bootloader, activesync won't see it. This is normal. Something is already using your USB port - did you disable ActiveSync USB, or kill it? Killing might leave the port reserved. Try restarting your VM session and/or rebooting. Then try uni_exitbootloader again. Or reflash.

[aelb771]

Originally Posted by erock123

Flash "bricked" my phone? Don't know if it's relevant WinXP via VMWare Fusion. Successfully upgraded my phone in past on this OS. This Sprint WM6 "Helmi" ROM flash seemed to result in a 101 error after confirmation dialogue (you're going from this version to this version). Now it's not detectable via USB (ActiveSync), etc. It seems to be stuck in "bootloader" mode (Gray screen that states Serial/USB and Ver 2.02 at the bottom). I tried to run uni_exitbootloader.exe as it was recommended by helmi (diff. post) to bring a device out of bootloader mode - no success - error msg about "cannot open USB port..." even though I killed the activesync process. As ActiveSync doesn't seem to be detecting the device (when restarted) it's not possible to reflash or return to OEM ROM. I'm a n00b admittedly but none of the wiki pages or other forums seemed to address a scenario like this. Help, please?

Thanks,

-E

The exact same thing happened to me. Unplug your phone, and plug it into a DIFFERENT usb port. It'll ask you to install a driver, and click on "continue anyway". After this is installed, then run the uni_exitbootloader.exe, and it will work.

Hope this helps, and thanks for the great software!

[DiamynzNPearlz]

Originally Posted by erock123

Flash "bricked" my phone? Don't know if it's relevant WinXP via VMWare Fusion. Successfully upgraded my phone in past on this OS. This Sprint WM6 "Helmi" ROM flash seemed to result in a 101 error after confirmation dialogue (you're going from this version to this version). Now it's not detectable via USB (ActiveSync), etc. It seems to be stuck in "bootloader" mode (Gray screen that states Serial/USB and Ver 2.02 at the bottom). I tried to run uni_exitbootloader.exe as it was recommended by helmi (diff. post) to bring a device out of bootloader mode - no success - error msg about "cannot open USB port..." even though I killed the activesync process. As ActiveSync doesn't seem to be detecting the device (when restarted) it's not possible to reflash or return to OEM ROM. I'm a n00b admittedly but none of the wiki pages or other forums seemed to address a scenario like this. Help, please?

Thanks,

-E

I had this EXACT same problem and thought I had effed something up. I tried everything including uni_exitbootloader.exe with no help. Follow helmi_c's instructions to DL wtty1.42.exe below and you will be fine!

http://forum.xda-developers.com/showthread.php?t=304408