Ok. I'm updated to DCD 3.0.1, with radio version 3.35.04. Everything appeared to be just fine up till I tried to install programs. It will NOT install anything from memory card anymore, and multiple programs I've tried to install from the main memory give me the Installation of "whatever program" was unsuccessful. The last one that I tried to install was Geoscout. I talked to the people that created the program, and there should be no problems installing it on this version of windows Mobile.
Any ideas why I can't install anything?
Please let me know before I dump this project.
I guess I'm out 3 for 3 on here. Suppose this is an uncommon problem considering no one's talking about it. Back to factory stuff I go. Thanks for all the responses.
Chem
How did you upgrade?
I'm not sure what your asking. I used Olipro 1.20, flashed the new Radio rom, flashed DCD 3.0.1, then flashed back to olipro 2.40. I used the instructions that DCD posted. This isn't the first rom I have used from DCD. I have been following the Custom roms for about 2 months or so now, and have kept up with them. I have never had memory card or installation issues. I talked to the manufacturer of Geoscout, and they said it is compatable with 6.1. I also need Compact .net framework 2.0 on here which I have. So I'm lost.
You just confirmed to me that you did not flash "correctly." When I say correctly, I mean how others are doing it problem free. These are dcd's instructions:
1. If you have not already done so, run the 2.40-olipro unlocker. Your device will again be left in tri-color screen.
2. Flash the official sprint 3.35 update.
3. When the device boots for the first time, do not pass screen calibration. Flash a 3.x.x ROM.
Now, I'm not saying the problems you are having are caused by how you flashed, but I do know that most everyone that flashed the way you did are having major issues.
Let me know what happens.
Last month I posted about a problem I was having after updating from DCD 3.1.1 to 3.1.2.....I couldn't get Active sync to work no matter what I tried. At that time I was still on the new Alltel radio and I was considering trying the newer 3.39 radio. Well, a day or so after posting I upgraded to the new radio and stayed with DCD 3.1.1. Today, I tried updating to DCD 3.1.2 again (carrier cab installed BTW) but still no activesync. I'd really like to figure this out since I noticed DCD had rolled back the OEMXIPKernel and I'm assuming his future builds will be based on that....so, does anybody have any ideas on why activesync would work on 3.1.1 and not on 3.1.2....both roms cooked in DCD kitchen using identical selections. Thanks
blueglide said:
Last month I posted about a problem I was having after updating from DCD 3.1.1 to 3.1.2.....I couldn't get Active sync to work no matter what I tried. At that time I was still on the new Alltel radio and I was considering trying the newer 3.39 radio. Well, a day or so after posting I upgraded to the new radio and stayed with DCD 3.1.1. Today, I tried updating to DCD 3.1.2 again (carrier cab installed BTW) but still no activesync. I'd really like to figure this out since I noticed DCD had rolled back the OEMXIPKernel and I'm assuming his future builds will be based on that....so, does anybody have any ideas on why activesync would work on 3.1.1 and not on 3.1.2....both roms cooked in DCD kitchen using identical selections. Thanks
Click to expand...
Click to collapse
well if you mean that activesync wont connect in bootloader, then yes. i had this happen to me during reflashing. just run the RUU while the device is connected to your computer. should work fine. also, if you hard reset, make sure you let it boot before entering bootloader.
Problem solved...but i have no idea why!! I downloaded and installed the 3.1.2 ROM already cooked in the original post and flashed that. Hooked up my PPC6800 via USB and instantly Activesync saw my device and synced. Everything is working fine. Still have no idea what could be the difference as I used DCD's 3.1.2 kitchen for my cooked ROM. I did not add anything other than what was in his kitchen but at least it upgraded this time.
I realized that I forgot to upgrade the radio shortly after upgrading to the dcd 3.1.2 rom. Now my phone can't send/receive calls (it either restarts when I make a call, or it makes/receives the call with no sound).
How do I upgrade to the Alltel 3.37 rom (the one I need for my verizon phone, right?) without using an micro SD card.
Thank you!!
I dont think it is possible. You are going to want to go the route of the SD card. I am fairly certain you will need to flash to Stock(see the Wiki). Then start over with the Radio 3.35 or 3.39 then DCD 3.1.2. 3.39 is better on the 6800 in my eyes. It cleared up dropped calls and signal issues.
Dont forget to run the Verizon Cab and not to allow Sprint to customize.
Thanks for the reponse but I fixed it; I installed the Alltel radio rom (3.37.20) which also downgraded the O.S to the previous (but not stock) windows 6.0. Now that the radio had been upgraded, I then reinstalled the DCD 3.1.2 windows mobile 6.1 rom. Internal GPS and REV A work like a charm!
edit
PS I hate using the SD cards. I like updating through USB from my pc, because if I run into any problems I can just push another rom through the bootloader and it's all back to normal. It's safer IMHO, and saved my phone countless times where the SD never could have.
After accidentally running the sprint PRI update on my xv6800, I was stuck with the phone thinking it belonged on Sprint and was roaming. I'm not completely foolish and I did not purposely disregard the instructions; I downloaded it elsewhere and it was labeled as "GPS fix" or some such. Anyway, I relocked, flashed to stock Verizon, called 611 and had them do a DMU reset. No problems, everything worked fine after calling 611. Reflashed to olipro 2.40, radio 3.42.30, and dcd 3.2.0. After flashing everything was fine, I ran the carrier cab, did *228,1 and everything seemed to work correctly. I then ran Sashimi to reinstall my software, rebooted. Well, the roaming indicator was back after reboot. I thought that perhaps the Sprint PRI update cab had made its way into my autoinstall folder, but that was not so. Do you guys have any ideas that might explain how this happened? I am flashing back to 3.2.0 and don't want to repeat this experience
playoff beard said:
After accidentally running the sprint PRI update on my xv6800, I was stuck with the phone thinking it belonged on Sprint and was roaming. I'm not completely foolish and I did not purposely disregard the instructions; I downloaded it elsewhere and it was labeled as "GPS fix" or some such. Anyway, I relocked, flashed to stock Verizon, called 611 and had do a DMU reset. No problems, everything worked fine after calling 611. Reflashed to olipro 2.40, radio 3.42.30, and dcd 3.2.0. After flashing everything was fine, I ran the carrier cab, did *228,1 and everything seemed to work fine. I then ran Sashimi to reinstall my software, rebooted. Well, the roaming indicator was back after reboot. I thought that perhaps the Sprint PRI update cab had made its way into my autoinstall folder, but that was not so. Do you guys have any ideas that might explain how this happened? I am flashing back to 3.2.0 and don't want to repeat this experience
Click to expand...
Click to collapse
When you update the PRI, it does not install into your ROM, it actually updates something inside the phone (similar to flashing your radio/etc). You need to find a verizon PRI ripped from the verizon stock rom (if it is even there) and install and run PPST.exe again. My original post he reposted had said not to install on another carrier in big red letters
Read this here, should do the trick.
After doing yet another relock, stock rom, and *228, I installed the latest PPC Kitchen 5060 rom (set to Verizon) and new radio (3.42.30). As soon as the phone boots, it thinks it is roaming and *228,1,2 does not help at all. I've done all the steps on the thread that serfboreds recommended. It still thinks it is roaming. Any advice?
I just don't understand this. The phone is fine until I install DCD 3.2.0 or nue 5060, after which it thinks it is roaming again. Getting desperate here...
playoff beard said:
I just don't understand this. The phone is fine until I install DCD 3.2.0 or nue 5060, after which it thinks it is roaming again. Getting desperate here...
Click to expand...
Click to collapse
Reload stock and take to store. This is a common outcome after letting Sprint customizations run. It really hoses your phone and can cause irreparable damage.
Any other suggestions?
serfboreds said:
Reload stock and take to store. This is a common outcome after letting Sprint customizations run. It really hoses your phone and can cause irreparable damage.
Any other suggestions?
Click to expand...
Click to collapse
The only problem is that the phone seems to look and work fine when the stock rom is loaded, as long as the DMU reset is done for data. Problems don't appear until I load a custom rom. I can't figure out why the phone shows verizon network (1.35_002 PRI) when the stock rom is installed, but then shows sprint (2.03_003) when I load a non-carrier specific DCD roms and even carrier specific roms (i.e. ppckitchen 5060 for vzw).
I don't know how I can convince a verizon tech to swap when the phone appears normal with the stock rom.
playoff beard said:
I just don't understand this. The phone is fine until I install DCD 3.2.0 or nue 5060, after which it thinks it is roaming again. Getting desperate here...
Click to expand...
Click to collapse
When you do update to DCD 3.2.0, Are you installing the Verizon Carrier Cab?? Also, How are you getting the radio onto the device??
Hmm, works normal with stock rom and radio but funky when you upgrade?
Sounds like you are not loading the radio or verizon carrier as azclown suggests. after going back to vanilla rom, upgrade using gc's newest radio via sd, then load dcd 3.2.0, let his customizations run, then load verizon carrier and you should be fine. Dont load the newest sprint rom/radio.
serfboreds said:
Hmm, works normal with stock rom and radio but funky when you upgrade?
Sounds like you are not loading the radio or verizon carrier as azclown suggests. after going back to vanilla rom, upgrade using gc's newest radio via sd, then load dcd 3.2.0, let his customizations run, then load verizon carrier and you should be fine. Dont load the newest sprint rom/radio.
Click to expand...
Click to collapse
I've been unlocking with olipro 2.40, flashing the new 3.42.30 radio from a microSD card, and then installing the custom rom while still in the bootloader. After installing DCD 3.2.0, I ran the carrier cab and then used *228. Plus, I wouldn't think the carrier cab would be the issue, because I had the same problem when installing PPCkitchens 5060 verizon rom.
-Update: I've tried using radiorefurbish.exe /refurbish to reset my phone to Verizon, but when I run the radiorefurbish.exe using resco explorer, nothing seems to happen. Any more suggestions?
Problem Solved:
I finally resolved this by installing and running this version of radiorefurbish. I ran it using resco explorer with the argument '/refurbish'.
Thanks to you guys and drellisdee at PPCGeeks. You guys rock. I was horrified that I was going to be stuck with the tock VZW rom.
Take the following screenshots (making sure to block out any personal information) and post them:
Device Information
EPST->Security
EPST->M.IP Default Profile
Then, flash back to stock, re-take the screenshots, and post them.
Finally, flash back to 3.42.30 and 3.2.0, install nothing except the carrier cab, re-take the screenshots one last time, and post them.
playoff beard said:
Problem Solved:
I finally resolved this by installing and running this version of radiorefurbish. I ran it using resco explorer with the argument '/refurbish'.
Click to expand...
Click to collapse
I've got the same problem and I reflashed to stock Rom and reflashed to custom. Still stuck in roaming. Could you give details on exactly how you ran resco with an argument?
Thanks
I wonder how he got that working. i've used that file and still have the issue. Yes... I used resco explorer and tried the argument... but got nowhere
nitro66215 said:
I wonder how he got that working. i've used that file and still have the issue. Yes... I used resco explorer and tried the argument... but got nowhere
Click to expand...
Click to collapse
i distinctly remember that one of the customizations after flashing back to stock was radiorefurbish. youve gone back to stock right and loaded the vz PRL?
aguas said:
i distinctly remember that one of the customizations after flashing back to stock was radiorefurbish. youve gone back to stock right and loaded the vz PRL?
Click to expand...
Click to collapse
Yup. and yes... it did run when the Verizon stock ran it's customizations. The PRI stays as sprints PRI 2.00_003. This is the main issue. Also, the ERI is 0. I've tried updating the ERI via ##eri... to the correct 4.eri... but it just gives me a write error. Under ##PROGRAM... the ERI fails to read. Hence my dilemna with the stupid Roaming indicator. I've been back and forth flashing different roms, and am pretty fed up with it actually. This is a Sprint Mogal "Cloaned" as my original VZW XV6800. I left the 6800 in the box.
check this
this wont help for the cloned moguls. But it will help the xv6800 users if they install sprint customizations.
http://forum.ppcgeeks.com/showthread.php?p=401137#post401137
believe it or not, a few months ago i let the sprint customizations run and used it like that just for the better signal...only downfall was no data services....i just switched back to verizon radio stuff yesterday and got my data reactivated
ever since I installed the rom, my wifi stopped catching signals completely. now I just added the data plan on my phone, and the data isnt working either. Any idea what the problem could be?
EDIT: ALSO I have a verizon phone, yet when I soft reset, Alltell shows up instead of the Verizon Logo. Maybe this has something to do with it
fix
What radio are you using?
Have you tried hard resetting and skipping the customizations? I don't see why Alltel would be displayed if you did a fresh ROM flash, as there is nothing associated with AllTel unless you installed the wrong CAB.
Best bet would be: Go to the Radio 3.40.30 thread, download the Unlocker for Olipro 1.2 and most recent Radio...flash the Unlocker, let it get into Boot Loader mode, then flash the Radio. Then it will boot up again, and flash your phone with Olipro 2.4, then flash the 3.2.3 DCD rom. Install carrier cab, and the Arcsoft one if you need it....then you're done.
The data connection may be another story...but I'd first get the ROM up and going, with the ability to make phone calls / send texts.
scotcha12345 said:
What radio are you using?
Have you tried hard resetting and skipping the customizations? I don't see why Alltel would be displayed if you did a fresh ROM flash, as there is nothing associated with AllTel unless you installed the wrong CAB.
Best bet would be: Go to the Radio 3.40.30 thread, download the Unlocker for Olipro 1.2 and most recent Radio...flash the Unlocker, let it get into Boot Loader mode, then flash the Radio. Then it will boot up again, and flash your phone with Olipro 2.4, then flash the 3.2.3 DCD rom. Install carrier cab, and the Arcsoft one if you need it....then you're done.
The data connection may be another story...but I'd first get the ROM up and going, with the ability to make phone calls / send texts.
Click to expand...
Click to collapse
Actually that's the funny part, I CAN make calls and texts. I didn't brick my phone or anything, GPS works fine too. The only problem is the WIFI and data connection - should I still go ahead and try that new rom?
problem
I would definitely suggest the whole procedure, from Radio flash and then further to the ROM reflash.
If after you've done all those things, and your WiFi is jacked, at least in my mind, the things probably broken.
Data connection could just be a matter of password being incorrect, or needing a DMU reset. See if you can do the flash to get the WiFI working first.
scotcha12345 said:
I would definitely suggest the whole procedure, from Radio flash and then further to the ROM reflash.
If after you've done all those things, and your WiFi is jacked, at least in my mind, the things probably broken.
Data connection could just be a matter of password being incorrect, or needing a DMU reset. See if you can do the flash to get the WiFI working first.
Click to expand...
Click to collapse
Do you have aim/msn or something? I updated to DCD 3.2.3 and the wifi works great now. But the data network keeps saying I have the wrong username and password. I even called up verizon for that and they dont know what the problem is. I bet it's incredible simple :/ What is a DMU reset????
Thanks a bunch in advance
EDIT: Also my phone is RIDDLED with alltel settings when it should be verizon, even AFTER all these updates!! I went into the EPST and a bunch of things had alltel. need help fast :/
inbox
check your private messages
Ok pm'ed you back! let me know if you get my email, if not i'll just post it here
I've upgraded and changed to:
NueRom v2.2
Chose Verizon, checked the EPST. Everything looked fine, but the m.IP Default Profile is still [email protected].
I was able to get an A-Key (and a password???) from the rep. The A-Key is pretty long.. does that sound about right? Anyway DATA still doesn't work. Any help is greatly appreciated, I'm trying to get this up and running as soon as possible