Related
I installed the dcd 2.1.0 verizon rom with the v3.27.0 radio (following these instructions:
http://www.phonenews.com/how-to-add-gps-to-htc-mogul-xv6800-p4000-titan-2663/)
and everything went fine but now my device is freezing up and generally not acting healthy. Can anyone vouch for this set up and/or recommend the best current rom for verizon? Im not too concerned with having GPS available (but would be nice), I would really like to have a nice no junk rom above all else. Thanks for any advice.
I haven't had good luck with any of the gps/reva roms on verizon... Seems every rom combination has it's share of quirks/bugs it's just a matter of finding the one that has some u can live with
I'm yet to find one that is FLAWLESS... if you find one let me know!
I have flashed several VZW xv6800s. If you have the 3.35 radio just flash DCDs latest (3.0.4). It runs very smooth. I have no issues except sometimes the GPS fix takes longer. It does everything else. Make sure you Hard reset after flashing.
Edit: sorry guys, was not thinking as i typed. I meant 3.35 radio (the one from the sprint update). Flash the 3.35 or 3.37 radio!
I would suggest using the latest ROM as well. Seems to have made a difference with battery life to me.
mdjkim said:
I would suggest using the latest ROM as well. Seems to have made a difference with battery life to me.
Click to expand...
Click to collapse
interesting how u guys on vzq have no problems with the reva radios... I was running 3.0.4 for quite a while until I finally canned it because I couldn't deal with apps crashing when switch to other procs... I went back to 1.7 to see if there was a problem there too but everything runs good it seems... am having bluetooth problems locking up device sometimes though so now I'm back to vzw stock radio to see if that fixes things? Actually I have no idea if bluetooth would be affected by radio or not but I'm desperately trying to find a stable setup.
I have flashed several VZW xv6800s. If you have the 3.27 radio just flash DCDs latest (3.0.4). It runs very smooth. I have no issues except sometimes the GPS fix takes longer. It does everything else. Make sure you Hard reset after flashing.
Click to expand...
Click to collapse
This is VERY bad advice and will only screw your phone up even more. It says in numerous places on these boards that 3.27 radio is NOT compatible with 3.x.x roms. The only roms that will work with the 3.27 radio are the 2.x.x roms.
My question to you though is why on god's green earth are you still wanting to run a 2.x.x rom with the old crappy buggy beta radio 3.27? Just update with the alltel updater to get radio 3.37.20, don't let customizations run, then flash dcd 3.0.4...much much better and will probably fix your gps problems.
corey113888 said:
I have flashed several VZW xv6800s. If you have the 3.27 radio just flash DCDs latest (3.0.4). It runs very smooth. I have no issues except sometimes the GPS fix takes longer. It does everything else. Make sure you Hard reset after flashing.
Click to expand...
Click to collapse
Danger!
radio 3.27 is NOT compatible with dcd 3.0.4 rom!!!
1) radio 1.30 or radio 1.40 = use dcd 1.7 (non gps rom)
2) radio 3.27 radio = use ONLY dcd 2.x.x series roms (with gps , revA - experimental)
3) radio 3.37 radio = use dcd 3.0.1 or 3.0.4. (gps and revA official)
my recommendation would be option 1 or 3. Depending on whether you want gps or not.
Zenoran said:
interesting how u guys on vzq have no problems with the reva radios... I was running 3.0.4 for quite a while until I finally canned it because I couldn't deal with apps crashing when switch to other procs... I went back to 1.7 to see if there was a problem there too but everything runs good it seems... am having bluetooth problems locking up device sometimes though so now I'm back to vzw stock radio to see if that fixes things? Actually I have no idea if bluetooth would be affected by radio or not but I'm desperately trying to find a stable setup.
Click to expand...
Click to collapse
Zen,
I think you might be the victim of a dodgy titan. I was, like you, using 1.7 for the longest time because I couldnt put up with the buggy 3.27 radio. So i just stayed non gps until the new radion 3.35 came out and dcd released 3.x.x series of roms. Since then I bit the bullet and went back to gps rom. I didn't look back. So far dcd rom 3.0.4 + radio 3.37 (alltel) has been the best (i.e reliable) rom setup I have experienced since I was on dcd 1.7.0. I think they are both equal now, except that I have gps enabled now and I dont need to carry my gps with me all the time.
The internal gps does SUCK the battery down kinda fast, but it is reliable. No bluetooth issues that I can see except that call quality is still sub-par but at least it connects without any trouble. If I am using the gps function in the car i use my BT gps because the BT radio uses a lot less juice than the internal gps receiver.
I have VZW just like you and gc, az clown etc and we all have similar good experience with the new setup. So the only other thing I could say about your titan problems is that it must be hardware. Try stock again and see if it clears up the problems then I would say that my reading of your situation is wrong. But from what you have said it seems right.
maccaberry said:
Zen,
I think you might be the victim of a dodgy titan. I was, like you, using 1.7 for the longest time because I couldnt put up with the buggy 3.27 radio. So i just stayed non gps until the new radion 3.35 came out and dcd released 3.x.x series of roms. Since then I bit the bullet and went back to gps rom. I didn't look back. So far dcd rom 3.0.4 + radio 3.37 (alltel) has been the best (i.e reliable) rom setup I have experienced since I was on dcd 1.7.0. I think they are both equal now, except that I have gps enabled now and I dont need to carry my gps with me all the time.
The internal gps does SUCK the battery down kinda fast, but it is reliable. No bluetooth issues that I can see except that call quality is still sub-par but at least it connects without any trouble. If I am using the gps function in the car i use my BT gps because the BT radio uses a lot less juice than the internal gps receiver.
I have VZW just like you and gc, az clown etc and we all have similar good experience with the new setup. So the only other thing I could say about your titan problems is that it must be hardware. Try stock again and see if it clears up the problems then I would say that my reading of your situation is wrong. But from what you have said it seems right.
Click to expand...
Click to collapse
Well, that's the thing.. when I go to stock everything I have no problems but am stuck with crappy wm6.0... I don't mind not having the gps so much but it def would be nice... However, I do hate having to run an older rom that isn't community-supported any longer due to newer releases...
I think my problem with 3.0.4 might have been the way I flashed the radio.. I was one of the original ones to actually get the dcd released radio installation to work and hadn't really looked back.... im wondering if maybe that was the problem... I might consider trying the sprint rom method to get the radio and then trying 3.0.4 again...
Other than that, I don't see any way to get a warranty replacement on the device if all the stock vzw stuff works without a problem.. only support I ever have logged with vzw for this device is the many many many times I've had hung data connections from switching back and forth to reva/non reva radios so much.... I long for a stable setup so I don't have to deal with this anymore
Other than that, I don't see any way to get a warranty replacement on the device if all the stock vzw stuff works without a problem.. only support I ever have logged with vzw for this device is the many many many times I've had hung data connections from switching back and forth to reva/non reva radios so much.... I long for a stable setup so I don't have to deal with this anymore
Click to expand...
Click to collapse
Now I'm not saying I condone this, but man...there are definitely ways to get warranty replacements even if everything works fine...
Just need to "screw things up" on your own Make it so your phone won't boot, bring it to a vzw tech center...cuz they won't know what the hell is wrong with it trust me...and bam they'll swap it out.
Edited my original post...
Also, i have had 2 replacement xv6800s. One was for white spot in the bottom left part of the screen. I had to call VZW and tell them they were out of replacements at the store. The other was replaced a week later for data not working.
Zenoran said:
Well, that's the thing.. when I go to stock everything I have no problems but am stuck with crappy wm6.0... I don't mind not having the gps so much but it def would be nice... However, I do hate having to run an older rom that isn't community-supported any longer due to newer releases...
I think my problem with 3.0.4 might have been the way I flashed the radio.. I was one of the original ones to actually get the dcd released radio installation to work and hadn't really looked back.... im wondering if maybe that was the problem... I might consider trying the sprint rom method to get the radio and then trying 3.0.4 again...
Other than that, I don't see any way to get a warranty replacement on the device if all the stock vzw stuff works without a problem.. only support I ever have logged with vzw for this device is the many many many times I've had hung data connections from switching back and forth to reva/non reva radios so much.... I long for a stable setup so I don't have to deal with this anymore
Click to expand...
Click to collapse
Zen,
go the 'official' route from stock. olipro 2.40. sprint 3.35 official (without allowing customizations) then flash dcd 3.0.4. If you still then have problems then we can isolate your flash before as a potential problem.
if you still have all the same issues then i really think its time for a new titan. If all is well then you can finally relax and enjoy the device.
Good luck
maccaberry said:
Zen,
go the 'official' route from stock. olipro 2.40. sprint 3.35 official (without allowing customizations) then flash dcd 3.0.4. If you still then have problems then we can isolate your flash before as a potential problem.
if you still have all the same issues then i really think its time for a new titan. If all is well then you can finally relax and enjoy the device.
Click to expand...
Click to collapse
Ya, I actually did the Sprint Flash this time around and things seem to be working better, to my surprise... Things seem to be running a lot better now compared to the radio hack I was using before... I imagine that's the reason dcd killed that link off the forums... although it didn't brick my phone, it obviously was crippling my device quite a bit.
Only thing that worries me (somewhat) about the sprint rom was that it changed the bootup screen (pre os load).. it's now black screen with red lettering showing versions... I have NO idea how that can be reverted back if I ever need to have this thing serviced. That sprint rom appears to totally changed the device.
Zenoran said:
Ya, I actually did the Sprint Flash this time around and things seem to be working better, to my surprise... Things seem to be running a lot better now compared to the radio hack I was using before... I imagine that's the reason dcd killed that link off the forums... although it didn't brick my phone, it obviously was crippling my device quite a bit.
Only thing that worries me (somewhat) about the sprint rom was that it changed the bootup screen (pre os load).. it's now black screen with red lettering showing versions... I have NO idea how that can be reverted back if I ever need to have this thing serviced. That sprint rom appears to totally changed the device.
Click to expand...
Click to collapse
Flashing of the pre-windows boot screens (i.e. the ones that show up around the time that the red lettered rom versions appear) are not part of the rom. You can't modify them with dcd's kitchen.
There are three options that you have.
1. You can create a mini rom with the splash screens in it that you can flash to the device. I dont know how to do it and dont really care to find out, but gcincotta knows how to do it and posted instructions a few days ago in another post. He can tell you how to do it.
2. You can use the ppcgeeks kitchen to create boot screens and then flash your dcd rom over the top.
3. Flashing a stock verizon, sprint, alltel etc rom will contain the splash screens and put them back on along with the correct (stock) radio and roms. Then you can take your very clean 'stock' titan back to the store for repairs or replacement without fear.
maccaberry said:
Flashing of the pre-windows boot screens (i.e. the ones that show up around the time that the red lettered rom versions appear) are not part of the rom. You can't modify them with dcd's kitchen.
There are three options that you have.
1. You can create a mini rom with the splash screens in it that you can flash to the device. I dont know how to do it and dont really care to find out, but gcincotta knows how to do it and posted instructions a few days ago in another post. He can tell you how to do it.
2. You can use the ppcgeeks kitchen to create boot screens and then flash your dcd rom over the top.
3. Flashing a stock verizon, sprint, alltel etc rom will contain the splash screens and put them back on along with the correct (stock) radio and roms. Then you can take your very clean 'stock' titan back to the store for repairs or replacement without fear.
Click to expand...
Click to collapse
Interesting.. I've never seen that changed other than this sprint rom... the stock VZW rom images I have just do the OS and Radio separately... I guess when/if I run into a situation where I need to revert back I'll worry about it then.. Until then, the newer boot screen is def cooler
gcincotta said:
Now I'm not saying I condone this, but man...there are definitely ways to get warranty replacements even if everything works fine...
Just need to "screw things up" on your own Make it so your phone won't boot, bring it to a vzw tech center...cuz they won't know what the hell is wrong with it trust me...and bam they'll swap it out.
Click to expand...
Click to collapse
gc, this is so true. The 'techs' at the verizon stores (bless their hearts) know nothing at all about the titan. you could go in there with a fully "sprintized' titan and seriously they wouldn't notice.
I found this out the first time I tried to flash. I thought I had bricked the device and took it to the "service center" verizon store near my location to get the data back working (yeah that's all the problem was, but I was a noob and didnt know better). They didnt have the slightest idea what to do to solve the problem. They screwed around with it for a while and gave it back, basically the same. they offered to switch it out for me, but I said i will try just a bit longer (and it had a customized 'colonel - ppcgeeks' rom on it - if you have ever seen one it is completely unmistakable - looks nothing like a verizon rom).
I went outside, called *8899 and got a service support tech to fix the phone over the air. The problem had just been the data account needed to be reset at their end. Not only did the guys in the store have no idea how to fix it, they didnt even notice that my device was clearly not stock.
Zenoran said:
Interesting.. I've never seen that changed other than this sprint rom... the stock VZW rom images I have just do the OS and Radio separately... I guess when/if I run into a situation where I need to revert back I'll worry about it then.. Until then, the newer boot screen is def cooler
Click to expand...
Click to collapse
Yeah, if you do the flashes separately the boot screen never change. I still had the original verizon boot screens until just recently when I did the upgrade to dcd 3.0.4. Its the running of the sprint installer that overwrites your verizon splash, not the rom or the radio themselves.
Anyway, i used the dcd kitchen to create my 3.0.4 rom and selected HTC animation. That creates a HTC splash to overwrite the sprint stuff, and then I did this and this and my machine looks sweet when it boots.
The instructions of how to load them is explained in the thread http://forum.xda-developers.com/showthread.php?t=379822
Enjoy. (I cant post pics of the screens because the xda database is busted at the moment)
Hi
whenever i open google maps and enable GPS
it'll stay as "seeking GPS satellites (0)" for like 5 minutes.
After..it'll say "GPS Active (0)"
well how can it be active if it's 0?
2 seconds later it goes back to the seeking message.
The weird thing is...when it says "GPS Active (0)" it brings me to random places in my city. Meaning it DID detect something, but then lost it immediately again.
i read the GPS guide and did whatever it said already. I had the GPS working a few weeks ago...now it's not working...even after reflashing with different ROMs.
Any help?
I am also unable to get a lock. I have Alltel and today I have tried going all the way back to stock and tried everything from 3.35, 3.39 and now I am back at 3.37 trying out ppcgeeks Titan_3.49. Everything is working great except no GPS. Using the GPS Viewer if I do a scan it does find the GPS radio on com4 but when I start it I never get a lock. I have also tried using BAF's and QuickGPS. Anyone have any idea how to get this working. At one time a while back I did have GPS working on this device.
Thanks,
mr.ellsworth
edit: I forgot to mention I also have tried out several of the differnt kitchens today in my quest to get the GPS working again including dcd 3.1.2
mr.ellsworth said:
I am also unable to get a lock. I have Alltel and today I have tried going all the way back to stock and tried everything from 3.35, 3.39 and now I am back at 3.37 trying out ppcgeeks Titan_3.49. Everything is working great except no GPS. Using the GPS Viewer if I do a scan it does find the GPS radio on com4 but when I start it I never get a lock. I have also tried using BAF's and QuickGPS. Anyone have any idea how to get this working. At one time a while back I did have GPS working on this device.
Thanks,
mr.ellsworth
edit: I forgot to mention I also have tried out several of the differnt kitchens today in my quest to get the GPS working again including dcd 3.1.2
Click to expand...
Click to collapse
I'm not sure if this will help - but I recently discovered that if ActiveSync is running while you are trying to get a lock - it will not lock. Stop ActiveSync with task manager and try again. I've been doing this for the last three days and get a lock every time now.
Try a free diagnostic's app such as VisualGPSce that will display the satellite status. Goggle Maps leaves you rather blind as to what is going on.
Sadly, we have discovered that not all Titans are equal and some have a hardware discrepency that greatly hinders the ability to clearly receive and lock onto the satellites. I've played with a few and my personal device consistently locks to 5 or more within seconds while another with identical software settings rarely if ever locks onto 3. Others have realised the same. Try waiting up to 30 minutes to see if any locks can be achieved -- if not then there's likely no software solution.
My kids are using the Moguls in our family. I removed a bunch of junk from the Sprint ROM but it is mainly as shipped. I cannot believe how fast the Moguls on Sprint acquire the satellites. It usually takes less than a minute and is often just a few seconds.
I use the Kaiser. It takes about 3 to 5 minutes sometimes to find the satellites. Sometimes I have to use the QuickGPS program to nudge it along.
With the Mogul, the fix is extremely quick. I wish my Kaiser was as quick.
I'm running a Mogul on Sprint w/ DCD 3.04. Locks take 10+ minutes, GPSViewer shows satellites immediately, but the lock just takes a while. I verified that ActiveSync is not running.
The Mogul was purchased in Nov/Dec last year.
wizzy99 said:
I'm running a Mogul on Sprint w/ DCD 3.04. Locks take 10+ minutes, GPSViewer shows satellites immediately, but the lock just takes a while. I verified that ActiveSync is not running.
The Mogul was purchased in Nov/Dec last year.
Click to expand...
Click to collapse
radio 3.35.04 took me 10+ minutes at times, 3.39.10 takes me 10 seconds.
It still takes me 10 mins to get a lock with 3.39.10, i use the GPS viewer to check for the lock.. Even with QuickGPS it takes about 10 mins.. Once it only took 6 seconds after that everything went to hell haha..
dcd1182 said:
radio 3.35.04 took me 10+ minutes at times, 3.39.10 takes me 10 seconds.
Click to expand...
Click to collapse
I just upgraded to 3.1.2/3.39.10 and google maps locks very quickly. GPSViewer still isn't very fast.
I upgrade to 3.1.2 and 3.39.10 and now my GPS is out by nearly 5 miles
Guys, 3.1.2 / 3.39.10 is not your issue if gps isn't working as good as you'd like it to. If anything, 3.39.10 is MUCH better in acquiring a fix. It's pretty much an unspoken fact that the gpsone chips inside these titans are spotty and some just work better than others. Sometimes mine gets a fix within seconds, sometimes it's 2 minutes. It's a combination of weather conditions, location of the satellites, and the gps hardware. These phones do not have SIRF chips in them...let's get over it.
It's np, I reinstall 3.35 radio and now gps work fine
Something about 3.39.10 and my gps chip doesn't like each other...
My inability to get over something not working correctly has led to getting things working correctly at least for now. Since I had had GPS working quite well under the 3.35 radio and knowing that I had been jumping all over the place with flashing different radios and kitchens in my never ending quest to try things out it occurred to me that I don't know all that much about what actually goes on during a reflash of a kitchen or radio etc... I thought it could be possible that during all the reflashes that not everything is cleanly removed and reflashed. Being an Alltel user I took my phone all the way back to stock which for me was the Alltel ROM “RUU_TITAN_ALLTEL_WWE_2.14.671.3_1.40.00_Altel_0816_NV132_Ship”. I got everything back up and running on this ROM. I ended up having to enter the MSID and MDN etc... I then unlocked the phone using "titan_SPL_2.40-olipro" next having had success using Sprints 3.35 radio I flashed “RUU_TITAN_SPRINT_WWE_3.35.651.2_RS_TITAN_3.35.04_4350H_SPCS_AM_Ship” that radio back onto my phone and then flashed dcd's 3.01 kitchen. I then tried out the GPS and everything was working great. Having finally received my 2 gig micro sd card I reformatted it to fat32 with 1024 clusters and proceeded to flash the 3.39 radio using this method instead of using the test sprint ROM as I did before. I decided to try out a different kitchen this time and I put on ppcgeeks "Titan_3.49_WM6" then installed “dcd QuickGPS.cab” and "dcd VisualGPSce.cab" and my GPS is working better than ever. For all of you out there that still are having GPS problems I would recommend doing something similar to what I did here. I would be interested to hear if this helps.
mr.ellsworth
mr.ellsworth said:
My inability to get over something not working correctly has led to getting things working correctly at least for now. Since I had had GPS working quite well under the 3.35 radio and knowing that I had been jumping all over the place with flashing different radios and kitchens in my never ending quest to try things out it occurred to me that I don't know all that much about what actually goes on during a reflash of a kitchen or radio etc... I thought it could be possible that during all the reflashes that not everything is cleanly removed and reflashed. Being an Alltel user I took my phone all the way back to stock which for me was the Alltel ROM “RUU_TITAN_ALLTEL_WWE_2.14.671.3_1.40.00_Altel_0816_NV132_Ship”. I got everything back up and running on this ROM. I ended up having to enter the MSID and MDN etc... I then unlocked the phone using "titan_SPL_2.40-olipro" next having had success using Sprints 3.35 radio I flashed “RUU_TITAN_SPRINT_WWE_3.35.651.2_RS_TITAN_3.35.04_4350H_SPCS_AM_Ship” that radio back onto my phone and then flashed dcd's 3.01 kitchen. I then tried out the GPS and everything was working great. Having finally received my 2 gig micro sd card I reformatted it to fat32 with 1024 clusters and proceeded to flash the 3.39 radio using this method instead of using the test sprint ROM as I did before. I decided to try out a different kitchen this time and I put on ppcgeeks "Titan_3.49_WM6" then installed “dcd QuickGPS.cab” and "dcd VisualGPSce.cab" and my GPS is working better than ever. For all of you out there that still are having GPS problems I would recommend doing something similar to what I did here. I would be interested to hear if this helps.
mr.ellsworth
Click to expand...
Click to collapse
I've tried your recommendation...however it did not make a difference
I don't know exact how you look at VisualGPSce.
On my "sig/nav" tab, there are a few vertical bars...all says 0...except two, which says 20 and 15.
Satellites in use: 0 (rarely 1)
Satellites in view: 0
Try resetting, or pull battery
After some experimentation, I now think that I can get out of the loop of not locking onto satalights buy resetting. Sometimes just turning off, other times a soft reset, and if that does not work, a shutdown plus remove battery seems to do the trick.
So, I downloaded the visual gps and I have good news and bad news. The good news is it is finding satellites so we know the GPS in my phone is working, the bad news is is isn't USING any of the damn satellites. When i'm inside my house it is only finding 1 but, when I go outside it is normally finding 3 with very strong signals and then picks up a few other ones that arn't very strong signals.
What do I do from here? We know the GPS is working, but it isn't locking. Maybe if I get it to lock somewhere other then my house and then come back it might work? I'm still under my 30 day free trial with Alltel and if I can't get this fixed I might return the phone. It is one of the main reasons I bought it and it's really pissing me off that it's not working right!!!
leepoffaith said:
What do I do from here? We know the GPS is working, but it isn't locking. Maybe if I get it to lock somewhere other then my house and then come back it might work? I'm still under my 30 day free trial with Alltel and if I can't get this fixed I might return the phone. It is one of the main reasons I bought it and it's really pissing me off that it's not working right!!!
Click to expand...
Click to collapse
Sounds like you've got a bad GPS chip. If the phone is otherwise working out for you, you should bring it back to Alltel for a swap-out due to defective hardware. Do it while you are in your 30 day period to minimize any hassles with them.
-Doc
The USB port on my 6800 broke so insurance replaced it. I'm running DCD's 3.44 and 50 radio on Verizon. I have flashed and flashed over and over checked QPST and reg settings.
Can it be just be the GPS never worked in this phone? Could this have come with the MR1 update on it? Is there a way to check? I have dloaded every kind of primer app as well and they do see the GPS port. GPS gate seems to work but reports no data.
I'm out of ideas.
nylaw said:
The USB port on my 6800 broke so insurance replaced it. I'm running DCD's 3.44 and 50 radio on Verizon. I have flashed and flashed over and over checked QPST and reg settings.
Can it be just be the GPS never worked in this phone? Could this have come with the MR1 update on it? Is there a way to check? I have dloaded every kind of primer app as well and they do see the GPS port. GPS gate seems to work but reports no data.
I'm out of ideas.
Click to expand...
Click to collapse
My first guess, assuming you turned the GPS on, is that you did have the MR 1 update.
You may as well try reverting back to stock winMo6.0 then back up to 6.1 via the standard method.
Secondly you could flash stock MR1 update then install valhalla GPS server cab.
What PRI do you have. If its 2.xx then you prolly did have MR1.
How did you unlock and what ROM/radio etc did you use?
The PRI is 2.xx but I thought that was from DCD's Verizon cab? I believe I unlocked with 2.40 than 2.47 at least that is my current BL. The radio is 3.42.50 and the rom is DCD 3.3.4 I am just about ready to pull the trigger on reverting back to stock and starting over. I just wanted to make sure I hadn't missed something.
One odd thing. I still get the white Verizon splash screen.Whenever I loaded a new romDCD's always had an HTC splash screen so that also leads me to believe it may have the MR1 update on it but not sure. Does that mean anything to you?
nylaw said:
The PRI is 2.xx but I thought that was from DCD's Verizon cab? I believe I unlocked with 2.40 than 2.47 at least that is my current BL. The radio is 3.42.50 and the rom is DCD 3.3.4 I am just about ready to pull the trigger on reverting back to stock and starting over. I just wanted to make sure I hadn't missed something.
One odd thing. I still get the white Verizon splash screen.Whenever I loaded a new romDCD's always had an HTC splash screen so that also leads me to believe it may have the MR1 update on it but not sure. Does that mean anything to you?
Click to expand...
Click to collapse
Thanks for the info on the splash screen. Did not think of asking that. If you have the standard VZW splash screens then you didint update correctly wiht the sprint ROM and not knowing where the ROM was before you started I would hazzard a guess and say you were on MR1. If you were not on MR1 then you hosed something during the sequence of flashing but that usually leads to a phone that sticks booting... I would try this before I revert back.....
Keep phone unlocked, flash sprint firmware and be careful not to let the customizations run, apply aGPS fix for VZW, test. If it fails then I can certainly say you were on MR1 and must revert back to stock. There may be another way of doing it but I honestly think starting fresh is always best.
Good news to report. I couldn't sleep last night as this was really bothering me. I went back to the stock radio and rom then flashed the radio and rom back to 3.42.50 and DCD's 3.4.4. All is working now but I still have the Verizon splash screen. I would have to say this must have shipped with the MR1 update. There was one value in the regisrty that I missed with the agps settings but that shouldn't have had any effect on the GPS from just the sats.
My PRI is also at 2.xx. This must be in DCD's Verizon cab. I did check when I flashed back to stock and it was at 1.xx
Seems a lot of people have broken USB ports. That was the reason for this replacement. On my last one the voice record button broke. So this is my third 6800.
nylaw said:
My PRI is also at 2.xx. This must be in DCD's Verizon cab. I did check when I flashed back to stock and it was at 1.xx
Seems a lot of people have broken USB ports. That was the reason for this replacement. On my last one the voice record button broke. So this is my third 6800.
Click to expand...
Click to collapse
That PRI is a bastard to get of. I found the best way to get rid of it is to kitchen a ROM, and then add in the Extended ROM from the stock VZW rom (non-GPS) and it was able to finally get rid of the PRI.
If you are still having issues with that PRI, let me know, I might be able to supply my PRI killer ROM if I still have it around.
Thanks but I am all set. Everything is working fine. I believe the guru's feel the 2.xx PRI is the one to have, just not the rest of the update.
My HD2 is about a year old. Decided to try android on the sd.
Device: HTC HD2 TMOUSA
Radio: 2.10.50.26 (Original) NOW flashed to 2.15.50.14
SPL: 2.10.xxxx (Original) NOW HSLP 2.08.0000
Android Rom: SD AmeriCanAndroid AOSP HD2 GB234 CM71
WM Rom: 2.13.531.1 (Original)
ACA seemed ok but would freeze randomly. So I flashed the radio to the 50.14. Seemed a little better but still a few freezes in android. Thought I would try the partition to improve the sd card performance. can't tell if it helped or not to many freeze ups to use android during the day. Had to go back to winmo.
NOW my winmo side it giving me random reboots. It gets hot--reboots, especially bad if using gps. I know overheating is part of the issue because during the middle of the day in my car without A/C it is terrible.
I also have an OTTERBOX Defender which has kept the phone looking great but is a really pain with on all the battery removal with the freeze ups.
I have read that this can be a mainboard issue, but how can I tell if it is or not?
Could the radio and winmo rom be incompatible?
Should I flash the winmo rom to a more compatible android rom?
Should I send it in since I have TMO insurance? (Anyone know if there is a deductible if you didn't lose the phone?)
I have also noticed the on the winmo side it reboots less if I turn htc sense off.
Not sure if I should go back to a different radio or send it in?
Are the insurance replacements refurbished or new? do they have the same issue?
Thanks for any expertise you care to share.
Could be indeed some incompatibility issue.
You write HSPL 2.08.0000, but that doesn´t exist. It should be SPL 2.08.HSPL.
Together with your original WinMo ROM, that indeed might generate some issues.
Still, just a guess.
Ok sorry for the miss understanding on my part SPL 2.08.HSPL is what I did. I guess I will try a custom winmo rom. Thanks for the response.
Hi,
I have been having a having an issue with my Evo3D since I got this replacement phone and I am trying to figure out if it is the phone or the software/firmware.
Simply put,
when the phone's screen is off (asleep and locked), sometimes when I press the power key to wake it up and then swipe to unlock, about a second later, the screen goes black, then I get the HTC splash screen, ie it does a full reboot;
at other times, the phone will be in my hip case or in my pocket, I won't touch it or do anything to it and the thing will reset itself, I am fairly sure this occurs when it is scanning for a tower or when it is changing to/from roaming as this occurred mainly while I was in the middle of nowhere this past weekend; and
this can happen immediately after a phone call, or right after I turn off/on one of the wireless subsystems, but this is less common.
I am unlocked, I downgraded using the bricking method, I have used both Freeza's and TreVe's firmware packages, I have used the 2.17 stock RUU twice.
I have run Mik's 3.6 rom, D3rp's 3.6 rom, dropzeroc's ROM, MeanRom's ICS and gingerbread ROMs, and some others and I still get this problem. I have also tried multiple different batteries. I always superwipe between ROMs.
Because I have used so many different ROM's, I am fairly sure the issue is either firmware or hardware.
Anyone have any thoughts before I send this back to Sprint for 2nd replacement because I REALLY don't want to have to brickroot ANOTHER phone. Took me 8 f***ing hours to get this one done.
Thanks,
Osiris
My first suggestion would be flash a new radio.
If the radio and firmware doesn't get along that well, it can cause problems like the ones you're having.
Moonbloom said:
My first suggestion would be flash a new radio.
If the radio and firmware doesn't get along that well, it can cause problems like the ones you're having.
Click to expand...
Click to collapse
Which radio would you use if you want to run ICS Sense 3.6? I guess I am confused though, wouldn't the 2.17 radio jive with the 2.17 firmware (radio 1.06 should be fine with 2.17 firmware right?)
I had the same issue. My phone would randomly reboot on screen on or sometimes i would check it and would see it restarting.
I went back to full stock and still had the same issue.
Took it to sprint and they get me another replacement.
I suggest you take it back.
I am trying the radio suggestion but thank you for the suggestion and I will probably take that advice if it continues having issues.
Well, I am not sure what to say.
Like any BAD troubleshooter, I changed two factors at once.
I switched to PKMN and downgraded the radio to .97
Well, it hasn't reset itself since.
Who the hell knows why either thing would fix my issue.
Downgrading the radio to .97 (from the 2.08 ruu) when everything else is 2.17 ruu makes no sense.
Going to Sense 4.0 ROM makes even less sense as a fix.
Anyone have a clue?