Related
I'd like to know who all here have flashed the 2.06 rom and reflashed to another or downgraded back to the original because of rom instability.
If you have please post the instability issues you had and which rom you flashed to and why.
I have some instability issues but I'm trying to decide if I should try another rom and then I have to determine which rom.
X
Mods if this should be put somewhere else lock it and I'll repost in the thread you suggest.
I really liked that ROM, and I hate carrier customizations. But then XDA Live 0.1 came out and changed everything.
I had cingy rom installed but installed "Special K's" XDA-LIVE.
Still running 2.06 - waiting for a few WM6 issues to be sorted before I flash it - Slingplayer for one
URPREY said:
Still running 2.06 - waiting for a few WM6 issues to be sorted before I flash it - Slingplayer for one
Click to expand...
Click to collapse
Slingplayer and FizzTraveller are a deal breaker for me. I cannot go to any rom where those 2 items won't work.
Are you having lockups with 2.06?
I have the new Cingular ROM on my 8525 and have been running it a few weeks. I like it (and find it stable) ... check out this thread I started and am trying to maintain dealing with known issues on the new ROM and some solutions (definitely check out the registry hacks on the wiki for this).
Personally, these issues are minor annoyances to me, and I have no thoughts of downgrading to the older ROM.
weinson said:
I have no thoughts of downgrading to the older ROM.
Click to expand...
Click to collapse
second that
URPREY said:
Still running 2.06 - waiting for a few WM6 issues to be sorted before I flash it - Slingplayer for one
Click to expand...
Click to collapse
second that, also realplayer integration was nice on the Cingy 2.06
xultar said:
Slingplayer and FizzTraveller are a deal breaker for me.
Click to expand...
Click to collapse
Is that because you watch entirely too much television, or because you paid entirely too much for mobile TV?!?
Just kidding, but not really.
bricked.
I flashed my JASJAM to the latest Cingular ROM, and noticed the bizarre SD card going missing problem. I tried to flash it back to the HTC ROM from November, and the stupid phone reset itself in mid-flash. Bricked.
No matter what I did, I couldn't get it back. The phone worked fine, except for the "NO GSM" error... which means no phone functions. I even put the 1.01 bootloader on there (but then it wouldn't let me upgrade it to 1.04). It refused to write to the radio portion of the ROM. I followed every instruction on here multiple times, with no luck, tried every ROM out there, tried every command (the erase... commands, etc). MTTY just showed it hanging every time on "Entering Radio Loader".
It's in California now, hopefully they'll be able to fix it. I'm sure they're going to charge me a small fortune since it's obvious I was screwing with it (it boots up with a 1.01 bootloader, and has an HTC logo on the splash, when it should be JASJAM).
In the meantime, I'm back on my Motorola L6. Oh god. I forgot how painful GPRS is. I'm lucky to get 23kbps.
I upgraded to the 2.06 rom and had all the decribed problems identified on this forum. I kept 'losing' all the contents of my sd card (a real problem with all the tomtom maps loaded plus music and photos)...couldn't get smartdial back to full function even with some updates...and i did face 3 or 4 freezes a day with the rom. I also couldn't get xm radio to stream properly (wouldn't load windows media player to stream music). I finally reflashed back to the original Cingy rom and have everything working good again. I hope when Cingular officially releases this rom update they will have these problem addressed and fixed.
xultar said:
Slingplayer and FizzTraveller are a deal breaker for me. I cannot go to any rom where those 2 items won't work.
Are you having lockups with 2.06?
Click to expand...
Click to collapse
@xultar
FizzTraveller doesn't work on the Cing ROM? Yikes, I didn't see that mentioned anywhere. Where did you see that?
Wow. I saw none of this. I actually really liked the "AT&T" 2.06 ROM on my TyTN - even better than the 2.05 ROM which was supposed to be "vanilla". It sucks that you guys had problems...
dwcliff703 said:
I upgraded to the 2.06 rom and had all the decribed problems identified on this forum. I kept 'losing' all the contents of my sd card (a real problem with all the tomtom maps loaded plus music and photos)...couldn't get smartdial back to full function even with some updates...and i did face 3 or 4 freezes a day with the rom. I also couldn't get xm radio to stream properly (wouldn't load windows media player to stream music). I finally reflashed back to the original Cingy rom and have everything working good again. I hope when Cingular officially releases this rom update they will have these problem addressed and fixed.
Click to expand...
Click to collapse
@dwcliff: No problems flashing back to the original ROM, then? I am not SuperCID. If I give the 2.06 and want to go back, that shouldn't matter, right?
xultar said:
I'd like to know who all here have flashed the 2.06 rom and reflashed to another or downgraded back to the original because of rom instability.
Click to expand...
Click to collapse
I tried it (as well as the WWE Test ROM) and quickly reverted back to 1.35 afterwards. I could not successfully sync with two 'puters with either AKU3 version. I could sync OK with the first 'puter, then sync OK with the second 'puter, but as soon as I went to sync again with the first, ActiveSync would delete my existing partnership and ask me to create a new one, then the process would be repeated when I tried to sync with the second, ad infinitum...
John
BigBen said:
@dwcliff: No problems flashing back to the original ROM, then? I am not SuperCID. If I give the 2.06 and want to go back, that shouldn't matter, right?
Click to expand...
Click to collapse
No problems...just be sure and download the correct rom (dated 9/21/06) from the Hermes Wiki.
dwcliff703 said:
No problems...just be sure and download the correct rom (dated 9/21/06) from the Hermes Wiki.
Click to expand...
Click to collapse
Thanks for the response!
Ben
dwcliff703 said:
No problems...just be sure and download the correct rom (dated 9/21/06) from the Hermes Wiki.
Click to expand...
Click to collapse
Ummm, is that ROM date right???
Ben
richy240 said:
Is that because you watch entirely too much television, or because you paid entirely too much for mobile TV?!?
Just kidding, but not really.
Click to expand...
Click to collapse
I travel weekly. LEave Mon return on Thurs nite. I think I deserve to watch what I want instead of Faux news in airport bars. So. Sling it is. Plus I can only keep so many Star Trek TOS on my 2gb card. I can't wait till the 4 gb.
BigBen said:
@xultar
FizzTraveller doesn't work on the Cing ROM? Yikes, I didn't see that mentioned anywhere. Where did you see that?
Click to expand...
Click to collapse
It doesn't work on the WM6 rom yet. I should have been more clear. Sorry for the confusion.
xultar said:
It doesn't work on the WM6 rom yet. I should have been more clear. Sorry for the confusion.
Click to expand...
Click to collapse
OK, gotcha. I like Fizz too. Surprised that I hadn't seen anyone mention it in the WM6 Issues thread.
Thanks
Ben
Anyone having issues with the GPS working? I'm unable to get any GPS Sats locked at all. I can do everything else just fine.
Just verifying, did you check the steps in the GPS thread?
I'm installing 3.0 for the first time right now. Will test GPS soon.
Yeah
I've been using GPS for a bit now with the older ROMs. I just want to confirm other VZW have it working.
Works great here. Be sure you have Be sure your Location Setting is set to Location On.
If you are using Google Maps, be sure to turn on the GPS in the GMM menu.
Also, be sure you are outside, not in a building.
etexter said:
Anyone having issues with the GPS working? I'm unable to get any GPS Sats locked at all. I can do everything else just fine.
Click to expand...
Click to collapse
DCD 3.0.0 works Excellent on my XV6800
GPS improved. I get way more satellites.
I modified the ROM a little bit and on a Bare ROM flash I get 28MB and with some major apps i get down to 25MB to 26MB
etexter said:
I've been using GPS for a bit now with the older ROMs. I just want to confirm other VZW have it working.
Click to expand...
Click to collapse
Yes, it works. I have been using Google maps. One thing, I noticed this morning is starting it up after an hour being off and in a building is "Google Maps" would get hung at "Initializing GPS" when I selected "Use GPS". The only why I have gotting it to work again was a soft reset. Not sure what is going on, yet.
Everything works fine on my xv6800 with dcd 3.0.0 including GPS.
No more issue where it takes 5 seconds to connect to a call when answering...among many other fixes from the leaked rom.
Interesting
Seems to be related to building the Kitchen on Vista for me. I can reproduce the problem if I build the kitchen on Vista. If I use all the same options on XP, it works fine. Strange. I guess something it messing with the build process on Vista. Solved for me at least.
Stupid question... assume you need the latest radio for this (3.35 or whatever, I have 3.27)? I'm a little leery on upgrading again considering I had to call VZW and apparently they're hip to people flashing these roms.
J Shed said:
Stupid question... assume you need the latest radio for this (3.35 or whatever, I have 3.27)? I'm a little leery on upgrading again considering I had to call VZW and apparently they're hip to people flashing these roms.
Click to expand...
Click to collapse
Yes, you need 3.35 to work with DCD's 3.0.0. I did not have to call VZW this time going from 2.3.2 to 3.0.0, I can't confirm if it will retain the A-key authenication from previous versions, haven't been back there for a couple of weeks.
rschell said:
Yes, you need 3.35 to work with DCD's 3.0.0. I did not have to call VZW this time going from 2.3.2 to 3.0.0, I can't confirm if it will retain the A-key authenication from previous versions, haven't been back there for a couple of weeks.
Click to expand...
Click to collapse
hmm... I don't have an A key on mine, but when I re-entered all the info it wouldn't let me place a call.
I'll give this a wack maybe tonight or tomorrow. I JUST upgraded to 2.3.2 and this comes out... figures.
I have only ever had to enter the A-key once, the very first time I flashed a ROM to the phone. Every upgrade since has just worked.
The latest is working great for me under VZW today. I was running 2.3.2 before that. I flashed the sprint ROM to get the new radio, then immediately flashed the ROM I built for verizon from the 3.0.0 kitchen. Did a *228 1 just in case, and verified that the PRL after that was identical to the one it had before I did the upgrade (##775 SEND, 000000).
EVDO, wifi, GPS all working. I like the new wireless today plugin.
I'd still love to see an up to date step by step on how to get VOIP working, I've never managed to get anything VOIP related on this phone.
GREAT WORK AS ALWAYS DCD! Thank you! Remember to show dcd the monetary appreciation guys.
rschell said:
Yes, you need 3.35 to work with DCD's 3.0.0. I did not have to call VZW this time going from 2.3.2 to 3.0.0, I can't confirm if it will retain the A-key authenication from previous versions, haven't been back there for a couple of weeks.
Click to expand...
Click to collapse
rschell, i'm very curious to hear the exact steps you took to upgrade, so that you did not have to call verizon.
some specific questions i also have:
1) did you do the entire sprint upgrade to get the radio, or did you just install dcd's standalone 3.35 radio?
2) if the entire sprint upgrade was used: did you let the customizations run, or did you reboot into bootloader before that point, and if so, where exactly?
3) did you have to re-enter any settings in ##778 ?
thanks for any help you can offer!
a_lazy_dude said:
rschell, i'm very curious to hear the exact steps you took to upgrade, so that you did not have to call verizon.
some specific questions i also have:
1) did you do the entire sprint upgrade to get the radio, or did you just install dcd's standalone 3.35 radio?
2) if the entire sprint upgrade was used: did you let the customizations run, or did you reboot into bootloader before that point, and if so, where exactly?
3) did you have to re-enter any settings in ##778 ?
thanks for any help you can offer!
Click to expand...
Click to collapse
Do not let the customizations run, just soft reset before they do. Now run the new kitchen creating your ROM. Should be nothing else to do.
I've never had to call Verizon through any flashes including when 3.16 first came out.
J Shed said:
hmm... I don't have an A key on mine, but when I re-entered all the info it wouldn't let me place a call.
Click to expand...
Click to collapse
At least to Verizon customers, the EPST A-key will always be blank. It is a 26 digit number generated by Verizon that is different each time you authenticate. Once you enter it, and the device reboots the A-key disappears. I have had to call and get a new A-key every time I have made the switch from non-Rev A to Rev-A. Not sure this new radio is any different. I have had excellent support from Verizon, every time I have called, you just have to let them walk through their diagnostic tests.
The authentication issues appear to be Network Switch dependent. I just happen to be in one of those areas.
blazingwolf said:
Do not let the customizations run, just soft reset before they do.
Click to expand...
Click to collapse
So if I just go ahead and reboot while, say, I'm in the screen calibration after my initial boot, I should be in the clear?
I was thinking of yanking the battery at this point, putting it back in, rebooting into bootloader, then flashing either by the RUU or SD (can't recall if the RUU works while in bootloader mode or not, so i've got the SD option to fall back on). Or should i just do as you say: soft reset, let the device come all the way back up, let activesync connect the phone as a guest, then run the RUU w/ DCD 3.0.0?
you don't even have to soft reset, or manually enter the bootloader. once you finish flashing the sprint update the phone will boot and will stop at the tap screen to set up device screen...at this screen activesync WILL connect. just run the kitchen and the phone will AUTOMATICALLY put itself into the bootloader and flash the new rom without running sprint customizations. the sprint customizations only run after you set the device up, not before.
gcincotta said:
at this screen activesync WILL connect.
Click to expand...
Click to collapse
bam! thanks man, it's details like these that always get glazed over in the flurry of "i installed the new rom no problem!!!!111one" posts that i'm seeing all over the place around here.
a_lazy_dude said:
rschell, i'm very curious to hear the exact steps you took to upgrade, so that you did not have to call verizon.
some specific questions i also have:
1) did you do the entire sprint upgrade to get the radio, or did you just install dcd's standalone 3.35 radio?
2) if the entire sprint upgrade was used: did you let the customizations run, or did you reboot into bootloader before that point, and if so, where exactly?
3) did you have to re-enter any settings in ##778 ?
thanks for any help you can offer!
Click to expand...
Click to collapse
Starting from 2.3.2 (if you start from the pre-GPS ROM, you may need a different SPL).
I did both the radio and ROM in one upgrade, I just did not let the customizations run, actually I forced it to the boot loader just after the HTC Mobile splash screen came up. Then I installed DCD's 3.0.0 ROM from the boot loader (2.40!). See http://forum.xda-developers.com/showpost.php?p=2011926&postcount=3
Success!
Data connection confirmed working
Incoming/Outgoing calls confirmed working
Incoming/Outgoing texts confirmed working.
GPS confirmed working.
no calls to VZW customer support whatsoever.
so far, no *228 updates at all (prl seems to be current, 50989; confirmed within ##778)
Here's a quick rundown of my starting conditions, and what I did (basically, just followed gcincotta's instructions exactly)
Starting conditions:
-NexVision's no2chem 5051 - based ROM w/ 3.27 radio
-2.40 SPL
Upgrade procedure:
1) Connected phone via activesync
2) ran the official Sprint/HTC 3.35 upgrade utility, which ran successfully.
3) On the initial boot, I let activesync connect while the phone was still holding on the "tap screen here to begin" screen
4) I then ran the RUU using a DCD 3.0.0-based rom (NexVision's VZW 3.0.0), which was successful.
5) After initial boot on NexVision's rom, I let the customizer run (i think it's just an SD power management program). It soft reset, and I was good to go.
That's it! Once it booted up after the second install, everything that I confirmed above was working perfectly.
Thanks again guys!
Had dcd 3.1.1 installed running fine. This morning decided to upgrade to 3.1.2. Another post advised it was easy to upgrade using sprite backup (new version allows restores across dif device platforms and OS) so I wouldn't spend several hours...again...tweaking my device. Made a backup and flashed dcd 3.1.2. Installed fine and then I used Sprite to reinstall my software. Device appeared to be restored back to dcd 3.1.1 and Activesync would not connect. Sooo I figured I would start from scratch again and did hard reset. Rom is dcd3.1.2...phone works...boots....everything appears normal but still no activesync. Tried disabling 'advanced network funtionality' on device...several reboots...uninstall activesync...reinstall...etc etc...still no connection. I've searched and tried the suggestions mentioned but I'm at a loss. Does anyone have any ideas how to get activesysnc to connect. BTW...when I connect via USB I hear 'chime' and the activesync icon spins but then times out with no connection. Sorry for lengthy popst but I wanted to try and provide all info....help please!?!?
I'm having this same exact problem. On top of that since I can't get activesync to work, I can't copy the verizon carrier cab to the device and run it. I can't even run it from an SD card so I've got a brick of a phone.
I'm trying to reflash to dcd 3.0.4 verizon-specific to see if I can get a working phone. Yesterday when I tried it, I was able to go back to stock by running the relocker and all that but I can't anymore for some reason. The relocker won't work.
Well..I fixed it...sorta....reflashed 3.1.1 with SD card and all is well again...I think I borked up something when I used Sprite....not gonna do that again. Will try 3.1.2 again and tweak for a few hours.
edsai said:
I'm having this same exact problem. On top of that since I can't get activesync to work, I can't copy the verizon carrier cab to the device and run it. I can't even run it from an SD card so I've got a brick of a phone.
I'm trying to reflash to dcd 3.0.4 verizon-specific to see if I can get a working phone. Yesterday when I tried it, I was able to go back to stock by running the relocker and all that but I can't anymore for some reason. The relocker won't work.
Click to expand...
Click to collapse
if you have data you can always download it from the thread but I suppose that wouldn't work without verizon customization...hm...I was going to flash to this (sorry nochem dcd comes out with a really stable and fast rom, now about that kitchen...)
at any rate...I hope the problem gets settled
Well 3.1.1 works great...flashed 3.1.2 via SD card and back to same problem...no activesync and no data. Strange...I have the updated Alltel radio on my device. Anyone else experiencing this. I'm on Alltel
Are you installing the alltel carrier cab everytime you flash? It is REQUIRED with these roms.
gcincotta said:
Are you installing the alltel carrier cab everytime you flash? It is REQUIRED with these roms.
Click to expand...
Click to collapse
Yes...installed the proper alltel carrier cab...still didn't work. Am considering downloading 3.39 radio and see if dcd 3.1.2 will work with that radio...currently I have the new alltel radio.
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
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