I am currently running one of the latest DCD releases with radio 3.42.50 and am very happy with it, but I cannot seem to find a 6.5 release that is compatible with Telus.
Does anyone have 6.5 running on their P4000? What build is it?
Cheers,
You can easily build your own in PPCkitchen. Then just add the telus carrier file.
Excellent - Never done this before so I am following walk-throughs on ppckitchen.org. What are the risks of bricking your phone while using this?
You can just install this rom, http://forum.xda-developers.com/showthread.php?t=512718 Its the newest 6.5 Rom that I know of. Then delete the VZ data settings, install the Good ole DCD Telus cab and Bang! If your not wanting to delete the VZ settings then thats fine. Still works.
This is a very good rom, I have not had to do a reset since I installed it.
Chris
Sirhcchris said:
You can just install this rom, http://forum.xda-developers.com/showthread.php?t=512718 Its the newest 6.5 Rom that I know of. Then delete the VZ data settings, install the Good ole DCD Telus cab and Bang! If your not wanting to delete the VZ settings then thats fine. Still works.
This is a very good rom, I have not had to do a reset since I installed it.
Chris
Click to expand...
Click to collapse
Umm noob here.
1. How would I delete the VZ settings?
2. Where can I get the DCD Telus cab?
Thanks
To delete the network settings:
Settings>connections>connections> Advance (tab at the bottom)>select Networks>edit. Hold your stylus on the #777 area until the pop up menu appears and select delete.
Then install the DCD Telus cab. It will reset all the nessary settings to work with telus.
Your good to go!
If your really new to this racket then let me warn you its like using crack! Try it just to see what its like then it will take over your life!
Kidding its not that bad, but be sure to read the wiki and have your boot loader and radio updated after you have recorded your vital serial information like it says to do there. I've never needed to re-enter that info but some ppl here have had to.
EDIT: All Cabs Here: http://dcd1182.n715dp.com/titan/carriers/
Chris
Related
I am having problem with the internet after flashing the new rom. I've tried resetting the profile, client IOTA (No response), hard reset, soft reset, reflashed and to no avail. Please advise.
did u let sprint install all the customized software after 1st flash?
Problem solved. I installed IOTA.cab separately so that it can run. Thanks.
can you link us to iota.cab? thanks
fusQer said:
can you link us to iota.cab? thanks
Click to expand...
Click to collapse
the iota cab is in your extended rom folder...if you have your er unlocked just select it from there...
i'm sorry i dont understand. where is the extended rom folder? i have dcd 3.0.0 and internet doesnt work so i want to run iota.cab.
Someone mind rapidsharing this? I dont have the tools to get to my extended ROM, I made my own IOTA cab from bits I copied back out of the Sprint ROM after it was flashed.
fusQer said:
i'm sorry i dont understand. where is the extended rom folder? i have dcd 3.0.0 and internet doesnt work so i want to run iota.cab.
Click to expand...
Click to collapse
yeah i just ran into that problem when flashing to dcd 3.0.0
Yay 4 Juggs said:
yeah i just ran into that problem when flashing to dcd 3.0.0
Click to expand...
Click to collapse
you said to check in the extended rom if its unlocked. how do i unlock it?
http://forum.ppcgeeks.com/attachment.php?attachmentid=5022&d=1202108628
from the 3.0.0 ROM Thread...
I also have extremely slow data transfers and high latency after installing DCD's kitchen 3.0. I'll give IOTA a try and hopefully it will fix it.
Edit: IOTA errors out for me, guess its back to the stock rom for me.
ilogik said:
I also have extremely slow data transfers and high latency after installing DCD's kitchen 3.0. I'll give IOTA a try and hopefully it will fix it.
Edit: IOTA errors out for me, guess its back to the stock rom for me.
Click to expand...
Click to collapse
I flashed the new Sprint ROM. I then did the ##728# stuff and changed to Rev. A. I let the Sprint Customizations Run as it booted the first time. I I took a drive and tested the GPS. It worked great. I also tried the Rev. A. I could see no difference in performance. Latency seemed down.
Then I used the "Clear Storage" program under Settings/System. While it was rebooting, I soft reset as soon as the Sprint Customizations began loading. I didn't want the bloatware installed.
Evidently I cleared the IOTA. It would be great if someone could post that cab here so we could try. The device did seem to work without the Sprint stuff loaded. Latency was poor.
I have alltel ppc 6800. I wanted to updated to newest dcd's build but cant find the download links for the files. I have windows vistsa. I have downloaded the kitched and its ready to build my os like i have in the past. But i dont have the spl 2.4 or radio 3.35. Can someone post links for those files with instructinos to install. I see the link to the spl doesnt work to download. The radio says use sprint updater to download but i dont understand that part.
Thanks
I have Alltel and was able to upgrade successfully but to my knowledge, MMS (picture mail) is still broken.
If you want to upgrade anyway:
1) Install Olipro 2.4 http://forum.ppcgeeks.com/showthread.php?t=9093
2) Install the Sprint radio but do not let the customizations run. I did this by installing the radio and going into boot loader at reset.
3) Install DCD ROM
My mms works fine on my 6800 here. I have dcd rom installed also.
can u link me the downloads for the sprint thing with directions. i dunno what that is.
It looks as though the official Alltel update (ROM version 3.35.671.9) is in the process of going up on HTC's website. The text is there but when you click to download the update, it doesn't do anything. Should be soon though.
EDIT: Well, I just went back to the page and it's now the previous update to WM 6. I guess someone was overzealous in putting up the new page.
You can search google for the sprint 3.35 rom.... what version of dcd rom are you going to flash?
When I flashed to dcd 3.0.1 rom and 3.0.4 rom my mms would not work. I had to install lennys alltel cab and it would work again. If you use 3.0.4 kitchen dont select the new arsoft and just install the lenny cab for picture messaging. At least this is how I got mine to work. I have included a link to cab.
http://www.lennysh.com/forums/showthread.php?t=2
well i have dcd 2.3.2 with radio 3.27 opl 1.24 so if i upgrade them should it work and run smoother?
tobylaek said:
It looks as though the official Alltel update (ROM version 3.35.671.9) is in the process of going up on HTC's website. The text is there but when you click to download the update, it doesn't do anything. Should be soon though.
EDIT: Well, I just went back to the page and it's now the previous update to WM 6. I guess someone was overzealous in putting up the new page.
Click to expand...
Click to collapse
The text is up again. And the link doesn't work as you said... but interestingly there is no mention of GPS, only RevA and Bluetooth fixes.
I'll keep an eye on it and see if anything changes.
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
Hello all!
I'm running dcd 3.2.6 with 3.42.40 radio and a Titan on Verizon. The GPS was working with Google Maps with the Verizon 6.1 update, but the phone was so slow to use (and no BT ICS), so I went to dcd. Since then, I get BT ICS, and the phone is much faster, but the GPS cannot lock on any sats. Any ideas?
I'd check to make sure all your aGPS settings are correct using QPST.
Already did that, but I checked them again to confirm.
What next? Is there a CAB I need to install? Should it just work out of the box?
it should work fine. Makesure it's set for com4 in google.
Actually I got my gf a touch and it was working fine til earlier this week now its back to the slow non aGPS where we have to wait 15 mins to get a lock. and i just got a new titan and cannot get gps working on the nuerompre3 rom. Maybe they blocked it?
did you make sure the location setting was set to on and not to 911 only?
It is on COM4, and it is set for Location Only. It was working with the Verizon MR1 release...
Did you reflash back to a pre 6.1 Verizon rom first? You have to do that or MR1 breaks the GPS. Once you flash back to an older rom, then the normal update flashes for custom roms works fine.
BTC
BillThyCat said:
Did you reflash back to a pre 6.1 Verizon rom first? You have to do that or MR1 breaks the GPS. Once you flash back to an older rom, then the normal update flashes for custom roms works fine.
BTC
Click to expand...
Click to collapse
That was it! I re-locked and flashed with a stock Verizon rom, and then installed SPL 2.47, dcd 3.2.6, and radio 3.42.40 and everything works perfectly! GPS, BT tethering / internet sharing, and it's quite responsive. Thanks for the tip!
No verizon ROM, but still the same problem
Well, I've never used a Verizon ROM (I'm in Mexico city, my carrier's IUSACELL), but I have the same problem. I got GPS working with DCD 3.2.5 and after upgrading to Radio 3.42.30 and DCD 3.2.6 (same day, one after the other), I've been unable to lock onto a satellite in spite of leaving the unit in the open for over half an hour and prepping the unit with toggleGPS.
I've tried flashing back the radio and ROM to the working versions and even cooked several ROMS using PPCKitchen, to no avail. The system can open the port, does read up to 7 satellites, but cannot lock onto them.
I tried setting the GPS up with the QPST tool and Verizon settings, and got nowhere.
I'll try and relock and unlock tip that eclipse used, but maybe I'm missing something here...
any help will be mucho appreciated.
Thanks
Hey there. I found the aGPS settings for IUSACELL here (site is in spanish and the info is on post 27 of this thread). I'll reproduce them here for quick reference:
PDE IP: 207.83.200.238
PDE Port: 8888
PDE Transport: IP
Position Calculation: PDE
I've tested them using dcd radio 3.42.50 and they work like a charm
Anyone know if/how we can get them listed in the tutorial and/or included in the Iusacell carrier cab?
I know I'm a senior member..and as a senior member I should know better than to ask something nooby like this: so please excuse my noobness and help me out!
I'm considering on flashing to dcd's 3.2.6 ROM but I had a couple of questions in mind first:
1) I'm on Sprint running on Evdo Rev. A speeds, I was wondering if I'd still have these speeds after flashing to dcd
2) I read about several GPS problems after flashing to dcd..but most of them came from Verizon devices..will this happen to me if I did the same?
3) Does it have MS Office Mobile in it as well?
Thanks a lot to whoever answers me! I really appreciate it!!
Answers for you:
a) yes, EVDO-A is supported
b) The problem stems from the official Verizon update. There is now an entire section in the Titan wiki related to fixing those problems.
c) Yes, it does have Office 6.1 in it.
Hope that helps.
drnoir said:
Answers for you:
a) yes, EVDO-A is supported
b) The problem stems from the official Verizon update. There is now an entire section in the Titan wiki related to fixing those problems.
c) Yes, it does have Office 6.1 in it.
Hope that helps.
Click to expand...
Click to collapse
Helps a lot drnoir! Appreciate it, will flash to dcd tonight
I was trying to get flash a new rom and found out thta I needed to upgrade my radio.
I'm with bell so I upgraded to the 3.42.50 radio and I flashed with dcd's newest rom.
Now when I try to send text msgs or call it doesn't work. it goesd "beep beep beep" as if all the calls are always busy.
is it a bug? did I get the wrong radio?
what version of bootloader did you use? what method did you use to flash?
I unlocked the bootloader SPL 2.47 (2.47No2Chem Titan SPL EVT) (Recommended)
and to flash the rom, I used the usb method. I doubleclicked on dcd3.3.4.exe and let the rest go. However I don't plan on using dcd, but rather a ppckitchen rom.
the phone boots up fine, I just cant use the phone though.
Did you install the carrier cab (although non-data calls should still work fine without it I think)? Perhaps you need to call the automated programming line?
By non data calls, do you mean text messages? I cannot make any calls or send texts...
I did not install/download anything carrier cab related. I'm assuming this may be the missing link. How does this carrier cab fit in with all of this? I did not see anything relate to carrier cabs in the Titan WIKI
I followed the steps:
-updater my SPL
-then the radio
-then I used DCD3.3.4
DCD ROMs do not include carrier information, hence the carrier cabs:
http://dcd1182.n715dp.com/index.php?dir=carriers
great! I found the bell carrier cab... now how do I install it? just put it in my device and install?
can I ask another question? where can this information be found?
this information can be found all over this forum. especially in the wikis. just do a little searching and you'll find most of your answers. sometimes searching wont find you your answer, but make sure youve done your fair share of searching before you create a thread. installing the carrier cab is about as basic as you can get with flashing, so you definitely need to do some reading to get a better understanding of how it all works. its alot to read, but it's totally worth it (and pretty much necessary)
i assume to install a cab, I just have to drag it to my PPC, then start file explorer and click on it.
it installs, then I reset... and still not working
bump ------ still not working need help
like stated before did you do the initial programming. for example verizon is either *22899 send or *228 option 2. you have to do the programming everytime you flash a rom or hard reset. you will see the triangle roaming icon until you program it.
oops, forgot to say it was resolved.
The issue was that the radio I used, even stated made for bell CDMA was most like meant for another carrier. ANyway, the MSID was changed in the EPST so I had to get the password using getSPC and change my MSID back to my 10 digit phone number. reset and voila.
thanks!