Related
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?
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
Will upgrading or downgrading my radio cause me lose everything? I want to update to a new radio but dont wanna lose the way my phone is setup (ie: installed software, reg hacks, ect......) ?????
If so, if I use Spb Backup first then update the radio, will Spb put everything else back and keep the radio new
highflyin128 said:
Will upgrading or downgrading my radio cause me lose everything? I want to update to a new radio but dont wanna lose the way my phone is setup (ie: installed software, reg hacks, ect......) ?????
If so, if I use Spb Backup first then update the radio, will Spb put everything else back and keep the radio new
Click to expand...
Click to collapse
I've upgraded and downgraded my radio without losing anything. I went from 3.39 to 3.42.02 to 3.42.30 and back to 3.42.02 and then back to 3.42.30 again.
But if you go from like a GPS radio to a non-GPS radio, you will be forced to upgrade your ROM as well, and then you will lose your data. You must make sure that your radio(s) are compatible with the ROM you have.
As another newbie, I had written myself a chart, is this the right thinking?
Update SPL : FINE
Update Radio : FINE
Update ROM : loose everything and if using a DCD rom, make sure to run the verizon cab.
Obviously one must look at the compatibility chart for SPL/Radio/ROMs that work together.
Also, doing the ROM is the only time you have to call to get a new A-Key and resetup the phone? (my thought, not totally sure, I am a newbie). I did my phone for the first time 3 days ago and did all 3. I used Oilpro 2.4 and am thinking up updating to nueSPL. I don't think that will cause any issues.
tschwenke said:
As another newbie, I had written myself a chart, is this the right thinking?
Update SPL : FINE
Update Radio : FINE
Update ROM : loose everything and if using a DCD rom, make sure to run the verizon cab.
Obviously one must look at the compatibility chart for SPL/Radio/ROMs that work together.
Also, doing the ROM is the only time you have to call to get a new A-Key and resetup the phone? (my thought, not totally sure, I am a newbie). I did my phone for the first time 3 days ago and did all 3. I used Oilpro 2.4 and am thinking up updating to nueSPL. I don't think that will cause any issues.
Click to expand...
Click to collapse
If you upgrade the Radio via RUU, it will perform a hard reset. The only way to upgrade the radio without losing anything is to flash via SD card method.
miguelfp1 said:
If you upgrade the Radio via RUU, it will perform a hard reset. The only way to upgrade the radio without losing anything is to flash via SD card method.
Click to expand...
Click to collapse
Thanks alot for this information
Thanks also. I did my first update via USB, now I will learn the increasingly popular (and seems easier) SD card method, just as soon as UPS shows up with my big card so I can take the stuff off my small card and transfer I will make sure to keep that in my notes!