Related
I've had a Cingular 8525 since Jan. of last year, and it worked flawlessly. I was interested in updating it to Windows Mobile 6, and posted a few questions on the forum under the Windows Mobile 6 forum for my device. However, as of recently the phone started to just go totally white when I would try to use the phone after pulling it out of my pocket, etc. I knew this was a common issue with the 8525, and a hard reset usually solved the problem with no issue. However, it kept happening more often. Sometimes even a hard reset wouldn't help. So, I called up the warranty division at AT&T and they agreed to send me a new AT&T 8525. I got it in the mail today. Great. New phone. I'm happy about that for sure, because the white screen issues won't happen anymore.
Here comes the problem. I'm sure most people (if not everyone) know that if you don't have any data plan on your account with Cingular/AT&T, the original Cingular 8525 would allow you data access if you set it up correctly. My old 8525 connects to the Internet, and I don't have a data package, and never have. I never get billed for it, and I've been doing it forever. My replacement 8525 when setup with these settings that I've been using fails to work. PIE will connect to the network, but it locks up at "Locating..." and then eventually spits and error that the remote computer disconnected.
As much as I hate to do it, I want to downgrade the AT&T firmware on the replacement phone they sent me back down to the Cingular firmware. Currently, the firmware I have on the old 8525 is ROM version 1.34.502.1, Radio version: 1.16.00.00. Is there any way to do it to my replacement 8525 with ease? I searched around and didn't find much step-by-step information, so if someone could kindly post exact instructions for me, I would greatly appreciate. I would be more than willing to search around some more and learn as much as possible about the process, but I really want to get this completely working with no errors before the weekend is over. Thanks.
Check THIS GUIDE.
Thanks for that info. Sure enough, after following the instructions you provided, I'm successfully down to my firmware version I had on my old 8525, and my data settings work perfectly. However, I have a different radio version, which is now 1.40.30.00. On the old 8525 I had the 1.16.00.00. Is this an issue?
I wonder if you were just encountering the bjilt in proxy in the newer roms? In the newer roms, to connect via isp.cingular, you need to disable the proxy. programs/proxy manager/disable proxy.
How are you getting free data?
How did you get att to warranty a ten month old device?
mthomas said:
I wonder if you were just encountering the bjilt in proxy in the newer roms? In the newer roms, to connect via isp.cingular, you need to disable the proxy. programs/proxy manager/disable proxy.
How are you getting free data?
How did you get att to warranty a ten month old device?
Click to expand...
Click to collapse
I'm getting the free data in conjunction with a feature I have on my account that is a legacy feature. So, even if I told you, you most likely wouldn't be able to get it added to your account, to my knowledge.
Thanks for the information, but I did try all variations of the different proxies and the APN names, but nothing worked. A friend of mine that works for AT&T just said to flash down, so that's what I did. All working now
Well, according to AT&T, my device was under warranty for 1 year, so they shipped me a replacement unit. I'm sending the old one back just as soon as I restore my stuff from my old device onto the new one.
Does anyone know the current bell mobility PRL? My phone seems to be stuck forever in roaming mode. I flashed DCD's bell ROM and my phone is constantly stuck in roaming mode and it shows the carrier as Sprint. Any ideas or do i need to re-program my phone?
origins81 said:
Does anyone know the current bell mobility PRL? My phone seems to be stuck forever in roaming mode. I flashed DCD's bell ROM and my phone is constantly stuck in roaming mode and it shows the carrier as Sprint. Any ideas or do i need to re-program my phone?
Click to expand...
Click to collapse
Check this site:
http://www.corolada.com/prl/
Bell PRL?
quantumforce1 said:
Check this site:
http://www.corolada.com/prl/
Click to expand...
Click to collapse
Yeah i took a look at it earlier, it's only american carriers
origins81 said:
Yeah i took a look at it earlier, it's only american carriers
Click to expand...
Click to collapse
Ahh -- sorry dude. Wish I could have helped.
If a Bell user with a working device has QPST installed on their PC, we could extract their PRL to share with everyone. (and i'd like a copy for my kitchen)
How do I extract the PRL? I haven't flashed the new rom yet and I'm a Bell Mobility user.
Cheers,
Tom
SUCCESS!!
So after hours of searching, it hit me like a ton of bricks....The PRL file has to within the stock rom
After that it was a case of looking up the current PRL
so here you go Bell users.... FLASH AWAY!!!
PS: Remember to delete the .txt extension before upgrading
I am a Bell user, and I flashed yesterday, but I don't think I had any issues with roaming. How can you tell if it's roaming?
The EV icon is replaced by the roaming triangle, normally the phone will warn you that you are in roaming mode if you get an incoming call or if your data connection is about to commence provided you have the roam guard settings set to ON
origins81 said:
Usually the EV icon is replaced by a dark triangle, pretty much after that the phone will constantly warn you that you are in roaming mode if you get an incoming call or if your data connection is about to commence provided you have the roam guard settings set to ON
Click to expand...
Click to collapse
Thank you, I don't think mine is roaming then. The phone will tell you with a verbal message (similiar to "The number is long distance. You will now....") prior to you answering it then?
Bell Mobility Users
Bell mobility users who flash the new sprint rom will need to update their radio with the above prl otherwise your phone will constantly roam
How can I help? I heard dcd is looking for a PRL to add to his 3.0 kitchen for Bell Canada. But you will have to guide me cuz I don't know how to extract the PRL. I tried ##228# but it just asks me for an unlock code...
dcd1182 said:
If a Bell user with a working device has QPST installed on their PC, we could extract their PRL to share with everyone. (and i'd like a copy for my kitchen)
Click to expand...
Click to collapse
How do you do that? you what to share how2 please! i have the program i only missing how2 extract the PRL. Cheers
I'm with telus and I just do the old *22803 thing and it updates my PRL for me...
The latest version of the PRL is already posted on the first page and i'm sure DCD already has it by now
I have a Bell Mobillity PPC6800 as well. I had updated it with the latest official ROM from UTStarcom's website. Am i at a certain risk because of this if i try to use this latest Sprint radio on it ? (and the DCD 3.01 as well ?)
Any Bell user that took the plunge yet ?
Adi
adisor19 said:
I have a Bell Mobillity PPC6800 as well. I had updated it with the latest official ROM from UTStarcom's website. Am i at a certain risk because of this if i try to use this latest Sprint radio on it ? (and the DCD 3.01 as well ?)
Any Bell user that took the plunge yet ?
Adi
Click to expand...
Click to collapse
Already flashed the new radio and built my own rom using DCD's 3.0.0 kitchen. Got a crapload of ram to boot, GPS picks up really quick, and haven't had any lock ups, still testing bluetooth but has been all positives. Granted you flash correctly, there is no risk involved and this place is littered with tutorials
Good luck...
http://rapidshare.com/files/99219142/DCD_3.0.1_Bell.exe
It seems there is a lot of work going on for the 6800. I'm unfortunate enough to own a 5050 and I'm having a hard time getting information. I know that it wasn't offered with bell for very long.
My main objective is to unlock the GPS receiver (why does bell disable this stuff!?) Can someone point me in the right direction?
Kessler said:
It seems there is a lot of work going on for the 6800. I'm unfortunate enough to own a 5050 and I'm having a hard time getting information. I know that it wasn't offered with bell for very long.
My main objective is to unlock the GPS receiver (why does bell disable this stuff!?) Can someone point me in the right direction?
Click to expand...
Click to collapse
HTC 5050 A.K.A. Falcon A.K.A. Wallaby, try here
http://forum.xda-developers.com/forumdisplay.php?f=268
origins81 said:
Already flashed the new radio and built my own rom using DCD's 3.0.0 kitchen. Got a crapload of ram to boot, GPS picks up really quick, and haven't had any lock ups, still testing bluetooth but has been all positives. Granted you flash correctly, there is no risk involved and this place is littered with tutorials
Good luck...
http://rapidshare.com/files/99219142/DCD_3.0.1_Bell.exe
Click to expand...
Click to collapse
Everywhere I look I see people talking about problems with different radio versions...copying certain IDS...and it's got me a bit concerned, I'd rather not brick anything.
Would you mind, in step form, telling us how you flashed yours with your custom dcd there?
I'd really appreciate it.
I would prefer this thread not become a "I am getting XYZ HELP!" thread, because it would be off topic. But I know it runs the risk of that because I would like to talk about the choice of Roms that XV6800 owners have used and the pros and cons of them.
I'm pretty sure I've seen the following GPS enabled ROMS on the verizon phones: (in order of complexity)
1. Original leaked ROM
2. No2Chem's nueROM http://forum.ppcgeeks.com/showthread.php?t=17219
3. DCD's 2.3.2 http://forum.xda-developers.com/showthread.php?t=371314
4. nexvisions's http://forum.xda-developers.com/showthread.php?t=364043
This section is now expanded to include a longer list of relative information needed to prepair for this process:
I've seen the Easy update thread: (This thread flashes the unlocker and radio in a single step using a ROM installation designed ONLY for a Sprint phone. Some believe this is why ppl have the 15 minute delay before aquiring a signal.)
http://forum.ppcgeeks.com/showthread.phpHere ?t=17667
You can see documentation for DCD's update from a Verizon Customer here:
http://forum.xda-developers.com/showpost.php?p=1973238&postcount=536
Here are the stock roms for recovery purposes (Signed and sealed by Verizon -not rips)
http://forum.xda-developers.com/showpost.php?p=1845171&postcount=13
Here is an unlocker: (also includes exit bl; read the .bat file to learn a lot and get some useful CLI commands)
http://forum.ppcgeeks.com/showthread.php?t=9093
Here is the Titan relocker:
http://forum.ppcgeeks.com/showthread.php?p=125160
Radio ROM 3.27.00
http://forum.xda-developers.com/showthread.php?t=362563
"general flashing rule is to start device in bootloader mode first and then flash. Do NOT flash it while it is running WindowsMobile OS."
Here are the generic steps to peform a standard burn from stock (works for some but all numbers should be written down in preparation)
0. WRITE DOWN ALL INFO UNDER ##778
0.1 REMOVE YOUR MicroSD CARD NOW!!!
1. Flash 2.40 unlocker using the Titanunlocker.bat inside the rar file (all files should be extracted to a new directory)
2. Flash DCD 2.3.2 (or preferred rom) different roms will
3. Flash radio 3.27
4. after booting dial a *228 to get the latest programing
That's it. It should be that simple.
If you are stuck, you might just be in the boot loader, use this tool for Verizon phones only to exit the boot loader:
http://forum.ppcgeeks.com/showthread.php?t=9229
Here's how to recover when it is not:
1. Using a PC, format a microSD card to FAT32.
2. Using winrar or an unzipper, extract the *.nbh file from the ROM upgrade .exe.
3. Copy the *.nbh file to the formatted microSD card
4. Rename the file on the microSD card TITAIMG.nbh.
5. Insert the microSD card into the phone and reset into bootloader.
6. The phone will tell you to press the power button to flash the ROM; do so.
Going into bootloader mode: power, camera, reset all at once.
Hard reset: Press the two dot (bottom menu) keys and hit the reset button, release all after two seconds. (RUMOR: Leaving the SD card in the phone may result in the SD card content being wiped. I don't care to test the rumor.)
I've read loads of threads tonight. My problem is that most of this stuff is slanted to Sprint stuff. I'm creating this as a central place for Verizon update facts. I'd love to hear if things work or if things don't work.
I'm considering flashing my phone tomorrow, (didn't happen yet by choice) but will also be travelling starting that night. Obviously the smart thing to do would be do go without GPS on my adventures, but it would be soo cool to have it working for SxSW just for the geek factor. And that calls to me.
So, here are some of my myths and mythunderstandings:
1. Every Verizon customer who updates their radio has to call into verizon to re-authenticate their phone. But Verizon is pretty cool about that even if you say you were flashing your phone.
2. This is true even if you follow the steps in the easy guide and write everything down it tells you to write down because Verizon uses a GUID generated by the radio rom when it is used for the first time on your phone. Not all areas as of today not every area does this but most and soon all will. It depends upon where you are in their upgrade chains.
3. If you install Radio 3.27, you're a screwed verizon customer because resets (hard and soft) and power ons (?????) will no longer aquire a signal right away. You will be waiting for 15 minutes or longer before you can use your phone again and no one has a working solution to this for Verizon customers. This happens to EVERY verizon customer.
4. People have upgraded to the original leaked rom without a problem (and without that delay) and that allowed them to have working phones possibly because of one or all of the following:
a. It is signed by Verizon and you don't have to unlock your phone?
b. MAYBE it doesn't require the radio upgrade???? (FIRST REPLY STATES THE RADIO IS REQUIRED FOR ALL GPS ROMS)
c. Because it was built using only Verizon stuff it is missing whatever incompatible tool the other kitchens have in them????
d. Because it has WM 6.0 and 6.1 hasn't been tested with Verizon????
5. DCD's rom has all of the MS Office software as an installable option whereas No2Chem's excludes it. Don't know if this includes outlook or not.
6. Both of the Kitchens mentioned above will work with Verizon and they have options that allow you to choose Verizon as an install option branding your phone correctly.
So that is upgrading your verizon phone as I understand it. Am I off too far on anything? I've not seen reports of any bricks yet but I know that is always possible.
So who has tried what ROM and to what degree of success?
BrianLayman said:
I would prefer this thread not become a "I am getting XYZ HELP!" thread, because it would be off topic. But I know it runs the risk of that because I would like to talk about the choice of Roms that XV6800 owners have used and the pros and cons of them.
I'm pretty sure I've seen the following GPS enabled ROMS on the verizon phones:
1. Original leaked ROM
2. DCD 2.3.2 with 3.27 Radio upgrade
3. No2Chem
I've also seen the Easy update thread:
http://forum.ppcgeeks.com/showthread.php?t=17667
You can see documentation for DCD's update from a Verizon Customer here:
http://forum.xda-developers.com/showpost.php?p=1973238&postcount=536
I've read loads of threads tonight and my problem is that most of this stuff is slanted to Sprint stuff. I'm creating this as a central place for Verizon update facts. I'd love to hear if things work or if things don't work. I'm considering flashing my phone tomorrow, but will also be travelling starting that night. Obviously the smart thing to do would be do go without GPS on my adventures, but it would be soo cool to have it working for SxSW just for the geek factor and that calls to me.
So, here are some of my myths and mythunderstandings:
1. Everyone Verizon customer has to call into verizon to re-authenticate their phone. But Verizon is pretty cool about that even if you say you were flashing your phone.
2. This is true even if you follow the steps in the easy guide and write everything down it tells you to write down because Verizon uses a GUID generated by the radio rom when it is used for the first time on your phone. Not all areas as of today not every area does this but most and soon all will. It depends upon where you are in their upgrade chains.
3. If you install Radio 3.27, you're a screwed verizon customer because resets (hard and soft) and power ons (?????) will no longer aquire a signal right away. You will be waiting for 15 minutes or longer before you can use your phone again and no one has a working solution to this for Verizon customers. This happens to EVERY verizon customer.
4. People have upgraded to the original leaked rom without a problem (and without that delay) and that allowed them to have working phones possibly because of one or all of the following:
a. It is signed by Verizon and you don't have to unlock your phone?
b. MAYBE it doesn't require the radio upgrade????
c. Because it was built using only Verizon stuff it is missing whatever incompatible tool the other kitchens have in them????
d. Because it has WM 6.0 and 6.1 hasn't been tested with Verizon????
5. DCD's rom has all of the MS Office software as an installable option whereas No2Chem's excludes it. Don't know if this includes outlook or not.
6. Both of the Kitchens mentioned above will work with Verizon and they have options that allow you to choose Verizon as an install option branding your phone correctly.
So that is upgrading your verizon phone as I understand it. Am I off too far on anything? I've not seen reports of any bricks yet but I know that is always possible.
So who has tried what ROM and to what degree of success?
Click to expand...
Click to collapse
1. There are people who say they did not need to call verizon, but i did.
2. this is mostly true, some areas still use an akey but verizon will gladly give that to you, just tell them you did a hard reset.
3. the roms that work with GPS require the 3.27 radio... I had no delay with using the phone after any flash (i've done several) there is a delay for GPS to work the first time
4.a. original leaked rom was from sprint
4.b. the radio upgrade to 3.27 is required or GPS will not work and neither will any rom that is based on this radio
4.c. again original leaked rom is from sprint and contains no verizon stuff, dcd broke down the leaked rom and made available to everyone else
4.d. the titan or xv6800 shipped with 6.0 (6.1 to release soon for verizon, although i have it now)
5. the outlook portion of office is standard on all pocket pc phone
6. True...you must choose your carrier or you won't be able to connect to your towers properly
that being said, I use a rom built with dcd's kitchen and am very pleased, if you want one with lots of stuff you may want to try nexvisions rom
Hope this helps
rmancl said:
that being said, I use a rom built with dcd's kitchen and am very pleased, if you want one with lots of stuff you may want to try nexvisions rom
Hope this helps
Click to expand...
Click to collapse
Thanks rmacl! That helps a lot. Reading through a few hundred pages of facts for different versions mixed in with cries for help and resolved issues can make the process, for someone who thought a kitchen was a room till a very short time ago, pretty daunting no matter how tech savy they are they are.
I appreciate your help in solidifying the details.
I will then be upgrading my phone tomorrow. I plan on following the easy update post listed above exactly as it is written.
I saw one post of a person who had done the same thing EXCEPT that they took a break and installed SPL 2.40-olipro. They had the 15 minute pause in aquiring the signal. So, I am wondering if that is a contributing factor. I'm thinking that the "Sprint unofficial 3.16 Release" includes an upgraded boot the spl/bootloader.
If this is a bad plan, or if it is not how you did it successfully and you are willing to share the steps you followed, please let me know.
Thanks again for your help.
EDIT: nexvisions rom pretty closely matches my current config. And what I don't have from that rom I like. The rest of the stuff I have installed should be enabled when I run a sprite backup restore. Thanks for the suggestion
Just did this today-
I'm using NexVision's Hybrid ROM(version based on dcd's latest 2.3.1).
I did the following:
1. Update SPL app
2. Loaded above ROM
3. Loaded latest radio
4. *228 'ed to get programming
5. did IOTA for some reason
6. No outgoing calls. Could not authenticate. Had to call VZW and they got me going in a few minutes. (the MSL for my phone i got from GetSPC.exe didn't work)
So, bottom line- My 6800 is working just fine with NexVisions Hybrid right now.
Anything else you'd like to know?
I was up and running on a DCD 2.3.2 cooked ROM and 3.27 radio with issues acquiring signal. Some have implied that running the "Easy Guide" instructions on PPCGeeks would resolve the delay in acquiring signal issues.
I couldn't get the leaked 3.16 ROM loaded using the 1.06 Bootloader, so I loaded the 2.40 Bootloader and then successfully loaded the leaked 3.16.
This put my phone on Sprint. According to the guide, running DCDs ROM that I cooked using the kitchen would reset the phone to Verizon (by selecting Verizon as my carrier.) This didn't work. Right now my phone is running the DCD ROM, 3.27 radio, and I can't get into the PST to edit the MSID and MDN.
Guess I'm going stock and upgrading again.
Am I the only one or is the fact that this phone is carried by at least 2.5(sorry alltell) major carriers a problem. We get people, admittedly I almost was one, that flash their phones with roms for the wrong carrier and then wonder what's going on. One would hope that you could pick up a cdma phone and use it on a CDMA network but that's just not true. There are tons of documented and undocumented crap holes that deviate from the spec because of the ad-hoc hobbled together system that is the United States cellular system. I would suggest splitting sprint and verizon but that would further fragment an already super fragmented market.
I am not sure the state of your phone or how to go about fixing it but the easy guide does seem to be for sprint users and not for Verizon. There is yet to be an uprgrade sanctioned for us - I hear it's coming, but I heard that with the Samsung i730 - and it took 9 months to get from 'soon' to released.
VX6800 DCD2.3.1 Working great
Ok I am an engineer on the network and perhaps Murphy got me to be over prepared and so I had the least problems. Started stock, flashed 2.40 unlocker, flashed DCD 2.3.1, flashed radio 3.27, booted back up and worked perfectly. I did write down everything, and I do mean everything that could be gotten in the PST ( by the way, the MSL on Verizon units is 000000 and no GetMSL is required) so I did not need that. I called VZW data support and told them that I was about to do a hard reset and had heard that sometimes the A key got messed up, so he gave it to me up front just in case, and because I had it ready is why I suppose I did not need it either. My signal came up perfectly, my PRL and provisioning data did need a *228 option 1 to get it back in, my GPS came right up fast and accurate, could make and receive calls right away, MMS worked perfectly right away. The only problem that I have with the new ROM is that the 'box type' mini-usb to 3.5 mm adapter with the mini-usb pass thru does not work properly anymore, but my stock one and my pigtail adapters do work, so it is somthing in the adapter design. Also SelectRadio 4.02 drops out as if the data connection goes down and back up, but it does not. I look at the PPP data and it is perfect, and when I just put my channels in Resco Pocket Radio all is well.
Well, I'm a long experienced IT guy with a background of working in cellular....so I'm not exactly ignorant on the subject.
madman, I did the exact steps you did, with the exception of writing down every setting in the PST (just the MSID and MDN). Yet my phone takes 15-20 minutes to acquire signal. Was there anything you had to adjust besides the MSID and the MDN?
To complete my story from my last post, I was able to recover back to a VZW stock ROM and try again. Second time around I didn't let the Sprint cutomizations run. That fixed the problem of my phone being "Sprintized". However, it didn't help with my issues acquiring signal (which was the entire reason I went through this exercise.) BLAH.
Having 1 set of instruction for Sprint and Verizon is fine, but what we need is are people from each side working together on the documentation. Right now everything seems to be completed by Sprint users.
Geckotek said:
...
To complete my story from my last post, I was able to recover back to a VZW stock ROM and try again. Second time around I didn't let the Sprint cutomizations run. That fixed the problem of my phone being "Sprintized". However, it didn't help with my issues acquiring signal (which was the entire reason I went through this exercise.) BLAH.
Having 1 set of instruction for Sprint and Verizon is fine, but what we need is are people from each side working together on the documentation. Right now everything seems to be completed by Sprint users.
Click to expand...
Click to collapse
I'm willing to bet it's the fact that you used a sprint rom. Even though it said you weren't sprintized I bet there are still sprint ghosts in your phone. These things aren't well documented nor are they straight forward. I am sure that there is something in the sprint rom that is causing your problem (it's the only thing that is different from stories of people who have been successful)
ICLKennyG said:
I'm willing to bet it's the fact that you used a sprint rom. Even though it said you weren't sprintized I bet there are still sprint ghosts in your phone. These things aren't well documented nor are they straight forward. I am sure that there is something in the sprint rom that is causing your problem (it's the only thing that is different from stories of people who have been successful)
Click to expand...
Click to collapse
Well, what you are saying is basically what I've suspected all along. I think the 3.27 radio is basically a rip from a Sprint ROM...right?
This is why I am trying to get a VZW tech to review ALL of the PST settings with me. She was gonna call back, but stupid me, I think I reset my phone and missed her call. Grrrrrr
Geckotek said:
Well, what you are saying is basically what I've suspected all along. I think the 3.27 radio is basically a rip from a Sprint ROM...right?
This is why I am trying to get a VZW tech to review ALL of the PST settings with me. She was gonna call back, but stupid me, I think I reset my phone and missed her call. Grrrrrr
Click to expand...
Click to collapse
What I am saying is the Sprint Rom is for Sprint. The radio is a radio from what I can tell. It doesn't seem to be setup to be one company or another with the correct rom. However what you are doing is taking a rom that is built by another carrier for their network and trying to use it on your network. Use a verizon intended rom (Hint: not sprint) and the 3.27 radio and you should be fine.
One would hope that you could just strip the sprint part out of their roms and run it on the VZW network but we all know these devices are more hodgepodge then strict implementation of standards.
ICLKennyG said:
What I am saying is the Sprint Rom is for Sprint. The radio is a radio from what I can tell. It doesn't seem to be setup to be one company or another with the correct rom. However what you are doing is taking a rom that is built by another carrier for their network and trying to use it on your network. Use a verizon intended rom (Hint: not sprint) and the 3.27 radio and you should be fine.
One would hope that you could just strip the sprint part out of their roms and run it on the VZW network but we all know these devices are more hodgepodge then strict implementation of standards.
Click to expand...
Click to collapse
There is no Verizon intended ROM that I'm aware of that supports the 3.27 radio.
spreeway said:
J
6. No outgoing calls. Could not authenticate. Had to call VZW and they got me going in a few minutes. (the MSL for my phone i got from GetSPC.exe didn't work)
Click to expand...
Click to collapse
getspc.exe is for sprint only
the msl code for verizon is "000000" minus the "'s
I've added a bunch of info to the first post. I haven't had time to do the flash till now. After I pack tomorrow, I should be able to do it. Plus I wanted to have all my ducks in a row for this process. I'm now fairly confident I know most of the failure points in the process and how to recover from them... we'll see.
Geckotek said:
There is no Verizon intended ROM that I'm aware of that supports the 3.27 radio.
Click to expand...
Click to collapse
Ummmmm NexVision IS a verizon user and his ROM is most certainly built for verizon above others, sprint and alltel second. DCD also has an option in his kitchen for verizon. as for No2Chem... I havnt used his rom so I couldnt tell you for sure. But I assure you as I am alive and breathing, there are ROMs intended for the Big Red V, I know I use one and Love it. I messed up when I first flashed, but never had to call VZW about it, just reflashed to stock then tried again.
As stated, I used both DCD and NexVision and both activated, called and surfed on the network. If you have any specific questions, I will gladly field them, Specialy since I have insurance on the phone... If it hoses, i will break and replace it.
Launching my first rom flashing...
blksprk said:
Ummmmm NexVision IS a verizon user and his ROM is most certainly built for verizon above others, sprint and alltel second. DCD also has an option in his kitchen for verizon. as for No2Chem... I havnt used his rom so I couldnt tell you for sure. But I assure you as I am alive and breathing, there are ROMs intended for the Big Red V, I know I use one and Love it. I messed up when I first flashed, but never had to call VZW about it, just reflashed to stock then tried again.
As stated, I used both DCD and NexVision and both activated, called and surfed on the network. If you have any specific questions, I will gladly field them, Specialy since I have insurance on the phone... If it hoses, i will break and replace it.
Click to expand...
Click to collapse
Ummmmmm, you completely missed the point.
So is there any word when Verizon will release an update similar to what we are able to do with the new ROMs and Radio?
I mean if it's going to be a month away, I may just, if it's going to be 3 months or forever then I guess I'll have to try it.
It seems either it works perfect, or it doesn't, and some people don't need to enter in an akey? Interesting...
I went from a stock XV6800 (Verizon) to the 2.40 unlocker, the 3.27 radio and a ROM built off of DCD's 2.3.2 kitchen. I did not need to record *any* of the phone's programming info. After flashing, *228 successfully set up the phone and I was able to start making/receiving calls.
"3. If you install Radio 3.27, you're a screwed verizon customer because resets (hard and soft) and power ons (?????) will no longer aquire a signal right away. You will be waiting for 15 minutes or longer before you can use your phone again and no one has a working solution to this for Verizon customers. This happens to EVERY verizon customer."
This seems not to be true, because I'm a Verizon customer and it didn't happen for me. I get both a cell and data signal right away on either reset (soft, anyway; haven't had to try hard yet) or power-on.
I'm a happy camper so far, with the only glitch being one unexplained soft reset one morning while the phone was waking up to execute an alarm. The phone reset instead and the alarm sounded when it came back up. Hasn't happened again since.
rmancl said:
getspc.exe is for sprint only...
Click to expand...
Click to collapse
No, I can verify that it works for Telus as well.
Okay
I bought the htc touch pro sprint version off a good deal. I used the elite team unlocker and I tossed the vzw leaked rom on the touch pro. Installation of the leaked rom went fairly well, and I thought I was ready to get this device connected via vzw network. I called vzw 3 times, went to 3 different stores, all have the same answer.
They cannot add the esn to their database. So my question is - what's the workaround regarding that policy? Do I have a very expensive alarm on my hands or is there something that can be done?
btw I haven't unlocked the msl code and I put the sprint rom (stock rom) back on the device to start fresh. Bear in mind I tried Getspc and I found that didn't work too well. I also tried QPST on vista and windows xp and the same popup on both machines came up (installing new drivers, please select driver location) to try and change the msl.
Any other thoughts or a good direction of where to go? I tried going to mobile files and I got an okay understanding of it, but an issue is well...I'm not sure of what to do.
I know there was a thread in the diamond forum to change the esn and I think that would be a good idea, what are your thoughts on it? Is it a good idea? Did I just open up pandora's box?
Try this
Go to forum.ppcgeeks.com
I believe I read something similar to this on that site. Don't know about the solution, but they are more advanced in dealing with the CDMA Pro, as they appear to have had it longer.
Sorry I couldnt help more. So Much for the Open Network Verizon promised.
Carriers sometimes are just a BIG Joke.
yeah I was reading two topics started by one guy...seems he went through the same drama that i went through
so I'm thinking from the discussion the only way would be to send the phone to verizon and I don't want to do that honestly
Dont
Don't Do it, and Verizon would rather you bu their own touch Pro when it gets released
Unless you can edit/spoof a Verizon ESN I don't think it's possible currently. If you do manage to find a way to do that, you need to be careful as it's probably illegal (as the ESN could belong to someone else -- and I'm sure there's laws in place to "protect you") -- Guessing at least, IANAL
Yes, technically it is illegal to change the ESN of a phone, however, I know that there was a way to change it (at least for the Mogul).
its been done
http://forum.ppcgeeks.com/showthread.php?t=44663
trying it now and so far my results are exactly as advertised huzzah!
So what's the verdict? Success or Fail?
m4f1050 said:
So what's the verdict? Success or Fail?
Click to expand...
Click to collapse
its my understanding that at this time vzn has suspended adding ESN's to there DMD. check the PPCgeeks post above your post and check to make sure though.
Yeah, I see they have some Sprint Touch Pro's on e-bay and I was thinking about getting one for my verizon account because they are cheaper and also I heard they have more processor memory or something. So does that no longer work, or can someone point me to a thread on this?
if you go to PPC geeks you can fint the post in the TP section.
I have a sprint touch pro on vzw network working perfectly using the above method a wile back, however 2 days ago i lost internet, and decided to activate an old phone and reactivate the touch pro to reset the internet settings on verizons network, when reactivating the sprint touch pro i was told the esn was invalad du to the fact that it was not 911 compadable,.. wich we allknow it is, but i believe verizon has just set their network to generate that error when a sprint esn is trying to be added, as of right now there is a truble ticken in with verizons it department but, im not very hopefull, i think my next step would be to clone an esn of a verizon phone i am not using, can anyone help me with that?
if it was anything close to what I had to do to get it on alltel, if you can get them to add the esn you may have to manually program it then add a prl then try *228 it....you do best to call vzw CS and tell them its theirs if they ask...
I have a T-mobile HTC pouch pro 2, and I've been testing NAND ROMS, which I LOVE, but I don't get any signal at all. My bars show an X. even after I put in the SIM. Is there any way to fix this? My WIFI and everything else works, but I just don't get any mobile network.
Any ideas? Thanks in advance.
Guefaunteno said:
I have a T-mobile HTC pouch pro 2, and I've been testing NAND ROMS, which I LOVE, but I don't get any signal at all. My bars show an X. even after I put in the SIM. Is there any way to fix this? My WIFI and everything else works, but I just don't get any mobile network.
Any ideas? Thanks in advance.
Click to expand...
Click to collapse
Does it work in WM? Does it work with SD based roms? What Android roms have you tried? Are you using a T-mobile device on the T-mobile network with a T-mobile sim card?
Please give us as much specific info as possible.
wizardknight said:
Does it work in WM? Does it work with SD based roms? What Android roms have you tried? Are you using a T-mobile device on the T-mobile network with a T-mobile sim card?
Please give us as much specific info as possible.
Click to expand...
Click to collapse
It does not work on WM or SD android ROMs. I am using a T-MOBILE device with Solavei (Which uses T-MOBILE towers) And a solavei SIM. But it SHOULD have bars even without a SIM. It doesn't recognize ANY network, no matter which SIM I put in it. I've tried AT&T and Solavei and T-MOBILE. I have flashed many different ROMs, HSPL and everything. I've tried reverting it back to WM and it still won't connect. I've tried every RADIO that was available for me to flash. It's like the signal in turned off in my phone.
Would it be a problem with the RADIO software? Or the Antenna?
If WM is not working right then Android will most definatly not work right. You would probably be better off posting in the WM forums for support as that is what the device shipped with. Even that is a long shot. These sub forums are mostly for Android dev and related issues. If the phone is not working with WM on it, then you need to take the phone to a repair shop. Odds are something is very broken, and they will have a better chance of sorting it out with the phone physical present. Other than suggesting that you reload the rom with the stock software, there is not much else I can suggest here.
Indeed. Get the phone working in WinMo first, then try Android. Thanks!