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
Related
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!
Got the radio upgrade 3.3x and all works well with 2.x dcd rom, but upgrading to 3.0.1 has problems with phone calls. Both receiving or outgoing, the device resets 10 sec into the call. Also Voice Command 1.6 not working. sucks.
verizon xv6800
I'd be willing to bet millions you didn't follow directions when flashing.
Nope. Cooked a kitchen, tried the Verizon Rom....neither work with 3.0.1. works great with 2.x though.
Voice Command 1.6 now working OK as well under 2.3.2. I is happy. Still looking for good GPS software. I really liked Earthcomber, but doesn't work with this rom.
If you tried to flash the radio standalone, then the verizon cooked rom...you didn't follow directions.
The ONLY way to successfully upgrade to 3.0.x is by flashing the sprint update to upgrade the radio.
OK so I cry for help. Why the heck would I apply a Sprint update to a Verizon handset, granted both CDMA. I upgraded the radio at the same time as 2.2. The 2.2 DCD rom I'm using that WORKS WELL should be no different than the upgrade to 3.0.1. Unless I'm forgetting to stop customization with a soft reset.
You're not getting the point!!!
The only reason to flash sprint's official rom is so you can update the radio to its latest version. After this is done, it DOESN'T MATTER whatever rom you flash next, such as a Verizon rom. Use DCD's 3.0.1 rom it should be working. You would have known this if you read instructions. If you flashed the radio alone first, then your settings (ESN, MSID, etc) will be wiped. You will have to re-enter these either manually or call up Verizon to do it for you. This is probably why you can't make calls.
Exactly my point. I flashed the radio with the Oli 2.4 and updated the radio from stock verizon. Then flashed 2.3.2 and all is good with the new radio. So why doesn't it work with 3.0.1? I just found my way to the In and Out Burger via Odyssey Mobile locator.
Everyone keeps telling me that i didn't follow the destructions but they don't point to where they are.
Maybe wrong radio ver?
Crap. Mine says 3.24.00. I guess that's my problem. I'm an idiot.
Please point me to the proper radio D/L.
Thanks,
Sorry for asking what is probably a simple question, but I am having the same problems. I have SPL-2.40.Olipro atm, installed the verizon ROM upgrading to 3.0.1 from NexVision's Hybrid rom. My radio is upgraded to 3.25 or whatever it was supposed to do fine. On vibrate mode, when a phone call is incoming, I get stuck in an ever ending vibrating. I can text, and attempt to cal lsomeone but nothing can be heard and no one can hear me. I know i screwed up somehow- but what exact steps do I do to remedy this?
Thank you in advance
We have to do the Sprint radio update to 3.35 first, which is an upgrade from 3.27. Then go to ROM 3.0.1.
It's always interesting to me how people jump up to say "you're doing it wrong" but don't tell you how to do it right.
Here's how to do it right.
http://forum.ppcgeeks.com/showthread.php?t=17667
Gecko122, There is more to the Sprint file than just the radio... It includes the ROM as well.... My understanding is this:
1st - Run Olipro unlocker 2.4
2nd - Run Sprint Official upgrade , NO CUSTOMIZATIONS.
3rd - Load Custom ROM.....
That has worked for me.....
PS - the DCD 2.x.x series do NOT play well with the new radio, hence the 3.0.1 kitchen.... Driver differences....
do i have to flash back to a former version of dcd or anything? or can i start from a messed up 3.0.1?
hi Penn,
Well, exactly what have you done to your phone?
Bootloader version?
ROM version?
Radio Ver?
Then we can start from there and develope a plan to help ya.
Ignore that above - I re-read you original post....
Here's what you can do and correct me if I'm wrong Penn...
You have Oli-pro 2.4 bootloader loaded
You have DCD 3.0.1 ROM loaded
You have the 3.27 Radio loaded?
If the above is true, then we have options..... Let me know
gcincotta said:
If you tried to flash the radio standalone, then the verizon cooked rom...you didn't follow directions.
The ONLY way to successfully upgrade to 3.0.x is by flashing the sprint update to upgrade the radio.
Click to expand...
Click to collapse
No, I flashed new radio stand alone package by dcd first day from an olipro 1.20 then 3.0.0 rom then 2.40 bootloader, and then one day later 3.0.1 rom... I never use sprint upgrade at all, and I have no problem about my phone at all. There is not just one way
No, I flashed new radio stand alone package by dcd first day from an olipro 1.20 then 3.0.0 rom then 2.40 bootloader, and then one day later 3.0.1 rom... I never use sprint upgrade at all, and I have no problem about my phone at all. There is not just one way
Click to expand...
Click to collapse
Correct me if I'm wrong, but weren't you the one with the extremely long, complicated post about how you were able to get everything working that way?
http://forum.xda-developers.com/showpost.php?p=2014972&postcount=326
Secondly, you may have been able to get everything working, but you're lucky. The chance of problems occurring by flashing this way is way too high in my opinion to even bother, not to mention others have had problems that absolutely cannot be fixed without reflashing back to stock and updating with the sprint update. That is why dcd removed the standalone radio from the Radio Rom thread.
Gecko, the reason why I did not "tell" you how to do it the right way is because dcd's thread has 94 pages of information on how to do it the right way. I've even posted several times on different pages in that thread with explicit instructions on how to. While I am always very eager to welcome newcomers to this community, I also strongly encourage them to read, research and educate themselves before touching their device. It doesn't mean I'm not a nice guy and don't like to help, because if you search my posts you will see that I help a lot around here. If you had simply taken 20 minutes and even skimmed dcd's thread, you would have found the answer yourself in no time.
gcincotta said:
Correct me if I'm wrong, but weren't you the one with the extremely long, complicated post about how you were able to get everything working that way?
http://forum.xda-developers.com/showpost.php?p=2014972&postcount=326
Secondly, you may have been able to get everything working, but you're lucky. The chance of problems occurring by flashing this way is way too high in my opinion to even bother, not to mention others have had problems that absolutely cannot be fixed without reflashing back to stock and updating with the sprint update. That is why dcd removed the standalone radio from the Radio Rom thread.
Click to expand...
Click to collapse
Wow... I'm sorry, I had not been keeping up with the issues of others, so until you said that just now, I had no idea. You are right, I am really lucky, so thanks for bringing it to my attention.
No problem
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.
I'm just curious, but after flashing the newest sprint rom and radio, I noticed that everytime I do a soft reset, I automatically get the roam triangle. This stays on for about 10 minutes till it goes to EVDO, or 10X. I am currently using the newest DCD 3.2.0 Rom, for Sprint, and there is no difference. Does anyone know how to prevent this from going into Roam mode when you do a soft reset?
Hopefully this hasn't been answered, and I missed it. If it has, I appologize. Thanks in advance.
Chem
Chemdawg said:
I'm just curious, but after flashing the newest sprint rom and radio, I noticed that everytime I do a soft reset, I automatically get the roam triangle. This stays on for about 10 minutes till it goes to EVDO, or 10X. I am currently using the newest DCD 3.2.0 Rom, for Sprint, and there is no difference. Does anyone know how to prevent this from going into Roam mode when you do a soft reset?
Hopefully this hasn't been answered, and I missed it. If it has, I appologize. Thanks in advance.
Chem
Click to expand...
Click to collapse
Do you know what version of the PRL you're using? It shows up as "PRL version" under Start->Settings->System->Device Information. Someone along the line you might have ended up with an outdated one. 60613 is the latest for Sprint EVDO-capable phones.
Chemdawg said:
Does anyone know how to prevent this from going into Roam mode when you do a soft reset?
Click to expand...
Click to collapse
I can confirm that with 3.2.0 (yes...I've finally moved on from my own kitchen based from Sprint's 3.35.xxx.... ) a soft-reset consistently reverts back to Standard for the Phonerefered Serving System. Over a soft-reset it should retain the choice of Home Only.
In the registry under HKLM\Software\OEM\InitProv\PhoneSetting what can I set to retain Home Only but retain the option to switch back to Standard when travelling?
This is an issue for me since I live by the water and the US is just across a straight leaving my phone often switching between my local and a US carrier.
Keystone said:
I can confirm that with 3.2.0 (yes...I've finally moved on from my own kitchen based from Sprint's 3.35.xxx.... ) a soft-reset consistently reverts back to Standard for the Phonerefered Serving System. Over a soft-reset it should retain the choice of Home Only.
In the registry under HKLM\Software\OEM\InitProv\PhoneSetting what can I set to retain Home Only but retain the option to switch back to Standard when travelling?
This is an issue for me since I live by the water and the US is just across a straight leaving my phone often switching between my local and a US carrier.
Click to expand...
Click to collapse
we probably need the previous version initprov.dll. i will look tonight. thanks for finding this
You're welcome, DCD.. Thank you!
This afternoon I may also have a chance to build a new ROM with a familiar initprov.dll and see if that resolves it.
With 3.2.0 on my Titan I just replaced the initprov.dll (v1.25.0.0) with the v1.21.0.0 (from the March Sprint release and what I was first using in my kitchen), rebooted, but still faced the problem of the phone defaulting back to Standard rather than retain Home Only.
That was without rebuilding a ROM with the older initprov version in.
...to note, the April Alltel ROM was also using this latest v1.25.0.0.
With 3.2.0 on my Titan I just replaced the initprov.dll (v1.25.0.0) with the v1.21.0.0 (from the March Sprint release), rebooted, but still faced the problem of the phone defaulting back to Standard rather than retain Home Only.
Click to expand...
Click to collapse
Certain dll's are self registering and some aren't. It's probably going to take a little more than just a copy/paste.
gc14 said:
Certain dll's are self registering and some aren't. It's probably going to take a little more than just a copy/paste.
Click to expand...
Click to collapse
Worth a shot.. Can't rebuild until I get home......
I realize now that it is related to the radio rom. Originally I installed the NEW factory firmware/rom upgrade. Well that was when it started. So thinking it was a factory rom issue, I installed DCD 3.2.0. Still doing it. So I decided to downgrade back to 3.1.6 which was what I WAS using before the upgrade.. Still doing it. So.. .It has to be the newest radio rom. I am going to downgrade the radio back to what I had and see if that fixes it.
I realize now that it is related to the radio rom. Originally I installed the NEW factory firmware/rom upgrade. Well that was when it started. So thinking it was a factory rom issue, I installed DCD 3.2.0. Still doing it. So I decided to downgrade back to 3.1.6 which was what I WAS using before the upgrade.. Still doing it. So.. .It has to be the newest radio rom. I am going to downgrade the radio back to what I had and see if that fixes it.
Click to expand...
Click to collapse
That's not necessarily true. It could have been something that was installed during the 3.56 factory customizations. Try flashing Sprint 3.35 stock rom/radio, let the customizations run. Then flash 3.2.0 and 3.42.02 or 3.42.30. If you're going to use the 3.56 stock rom/radio to flash 3.42.02, that's ok, just DON'T let the customizations run this time.
that was the issue with mine I ran the sighned sprint cab from the extended rom from the 3.56 "official" rom that was part of no2chems pre 2.2 after i did that my phone was stuck in roaming... Thinking it was the radio i downgraded 1 step @ a time from the 3.42.03 back to 3.39 still roaming went back to the stock radio that came with the 3.35 release still roaming when phone was booted. Figured it might be rom related @ that point so i reflashed to good ole 5069k left battery out after flash for 2 min... first boot it was roaming and would not lock onto a tower in sprint only mode... my muerom boot agent always runs the sprint carrier settings 4 me and on my second boot still no sprint signal only digital roam.. In a last ditch effort I reflashed via activesync the whole 3.35 stock rom/radio ... and wala all was fixed booted right up and even b4 the sprint custimization was started i had the evdo icon and no roaming triangle. Leaving the 3.35 stock rom on there i went forward 1 step @ a time radio wise and even with 3.39 and 3.42.02 i still got sprint coverage and evdo icon and connection. so i re-flashed to the nue 2.2 preview let it do tis sprint thing on first boot. then i did not go in and eun anything from the extended rom. No more roaming triangle. Something in the 3.56 exended rom i ran (sprint sighned whatever) Changed something in epst that dod not get reset even with flashes and hard resets till i relfashed back to stock 3.35 relaease full with radio from activesync.
So my suggestion would be that u can run the newer radio and roms just be sure to let your carrier settings run but don't touch files in the extended rom esp the file mentioned bc it stuck me in roaming and it would not get a sprint signal (home) for anything even after just letting it sit. and when setting roaming option to sprint only I would not get any bars @ all just the animated dots nest to the signal icon.
So it can't be anything in the new rom or settings in the new rom that is doing it nor the radio bc when downgrading back to stock radio from march update it did the same thing.
To fix your going to need to do a fill rom/radio flash then just pick your fav flavors after its flashed and has booted up the second time.
Boy, am I glad y'all started a thread on this. I've been trying to figure out what was wrong since this came out. My first flash of the new rom caused mine to be stuck in roaming, and sometimes it won't even come out.
I'll try what you guys suggested.
Customizations = Extended Rom
That's exactly what I said.
Ok, things a little different now. I reflashed back to the stock 3.35 Rom and let customizations run.
Then flashed just the new radio 3.42.30 from SD card
Last I flashed just the dcd 3.2.0 ROM and the carrier cab, and now no more roaming after the soft reset.
So, maybe the problem is in that radio included with the new 3.56 ROM
As long as I got it working, I'm happy
Ok, things a little different now. I reflashed back to the stock 3.35 Rom and let customizations run.
Then flashed just the new radio 3.42.30 from SD card
Last I flashed just the dcd 3.2.0 ROM and the carrier cab, and now no more roaming after the soft reset.
So, maybe the problem is in that radio included with the new 3.56 ROM
As long as I got it working, I'm happy
Click to expand...
Click to collapse
Again, it's not the radio. It's in the customizations from 3.56.
gc14 said:
Again, it's not the radio. It's in the customizations from 3.56.
Click to expand...
Click to collapse
If all we had to do was not let the customizations run, why didn't someone just say that? I've been asking about this for like 3 days now.
When I tried flashing the 3.56 rom without the Customizations it still would roam, so go figure
If all we had to do was not let the customizations run, why didn't someone just say that? I've been asking about this for like 3 days now.
When I tried flashing the 3.56 rom without the Customizations it still would roam, so go figure
Click to expand...
Click to collapse
That's because you've already let them run. They don't go away after a reflash, the same way Verizon users who let them run can't just reflash their rom to make it go away. You need to flash sprint 3.35, let THOSE customizations run. Then reflash 3.2.0.
Before you do anything though, you DO have Sprint right?
I upgraded for the 2nd time to a non-official rom recently. The first time through I had no problems. This time, I lost my internet connection and ##778# does nothing.
I have the Sprint Mogul with radio 3.35.04 and DCD 3.2.0. I'm at a total loss for solutions outside of trying to upgrade again, but would prefer to avoid that.
launch EPST from \Windows\EPST.exe
can you be more specific about the no internet issue? are you receiving any errors? have you considered upgrading your radio?
kflip makes a good point, I'm pretty sure you need Radio 3.39 or above to run DCD 3.2.0 (I vaguely recall people having issues with versions below 3.39)
At worst case, why not do the official Sprint upgrade to get to 3.42.02 then flash to DCD 3.2.0 or 3.2.2 even
3.35.04 is compatible, but when it comes to radios you really cant go wrong by upgrading.
For the billionth time....
Did you install the carrier cab?
gc14 said:
For the billionth time....
Did you install the carrier cab?
Click to expand...
Click to collapse
That's embarassing... Fixed both problems obviously.
gc14 said:
For the billionth time....
Did you install the carrier cab?
Click to expand...
Click to collapse
you should put that in your signature and just put in your post "read below"
actually i'm going to quote you and put it in mine
perfect!!!!
Haha that's awesome.
To the OP: If you have a microsd card and you're able to flash with it, you should upgrade your radio. As long as you do it using the card, you won't lose anything or be forced to reinstall anything.
gc14 said:
Haha that's awesome.
To the OP: If you have a microsd card and you're able to flash with it, you should upgrade your radio. As long as you do it using the card, you won't lose anything or be forced to reinstall anything.
Click to expand...
Click to collapse
/update to 3.2.2, as 3.2.0 had several problems with it that are fixed now.