Related
Hi there
I had 2,17 and upgraded to the leak rom 3.16. I did not use any locker or unlocker when upgrading. I am having issues with mail2web that it sends the same sent email several times. I think there is an active sync bug with the leaked rom. Anyways, I am trying to downgrade back to the official 2.17 and I when try to flash after the intial reboot it tell me error 328 invaild command
can anyone please help??
I had that same problem on one of the other roms. My email issue was fixed by hard resetting and reflashing the same rom. AS far as getting back to a different rom, not sure. You might need to find the older unlocker program from oilpro and cokeman.
Good Luck
As a matter of fact I plan on doing this within the hour. I'm ging to use the Re-locker tool and ill back report back with progress.
*Update*: Re-locker tool worked perfect Find it here
http://forum.xda-developers.com/showthread.php?t=363556http://forum.xda-developers.com/showthread.php?t=363556
Anytime you want to flash an "Official" Sprint ROM, you will need to relock the device.
Also, to make sure the reflash completely overwrites everything, I usually flash a ROM multiple times...
trying to downgrade bricked my mogul
I was having issues with the leaked rom, and wanted to downgrad back to the sprint 2.17, I was also geting error 328. and here is the part that bricked my phone, since i couldn't get teh official 2.17 to load i tried to load a custom 2.17 rom which said it installed 100%. However when i reboot i am now stuck in the preboot screen that says for testing only.
I had pretty much the same issue - upgraded to a 3.16 custom to try it out. Didn't care for the flakiness of it.
To downgrade, you will need to use the relocker to go back. After that I flashed a stock Sprint 2.17. Then unlocked again to get a 2.17 custome ROM.
FIXED! Read below for details.
So i've been messing with my mogul for nearly 4 hours now trying to convert it to dcd's rom..and i've flashed it twice now and after it reboots from being 100% loaded it just sticks on the HTC black screen..I've read and read and searched and searched and cannot find a definite answer. Can anyone help?!
basics?
did you load the radio rom?
did you load the unlocker?
you may need to restart the phone to the boot loader and resend the rom
(press and hold camera and power and push reset button)
I did TRY and reload the radio and unlocker..now im stuck at the black htc screen where it says no radio though. bleh. i can't even get it back up and running. what do i do?
edit:
I'm at the multi color screen..ive tried running the unlocker RUU and then running dcd's ruu and it doesn't work..and the radio RUU does not run at this screen...I can't get the phone back to a working status! Argghhhh. It wont let me run the relocker unless im in activesync...but i can't be recognized in activesync unless the phone is up and functional..so..? how do i relock it to put hte stock rom on to try and unlock again?
I am kinda stuck in the same spot, but mine is is the verizon logo screen, i tryed doing the power,camera and hte reset button but its till stuck, i tryed the relocker but i need to be in active sync
any help?
what i dont get is..i flashed it with the unlocker, then the rom then the radio...isn't RUU just overwriting each one or something? it doesn't make sense to me. and all i can do is run RUU..i did the rom, then the radio and it was stuck in the bootloader so i used the exitbl and got out of it but then it just went back to going to the HTC black screen saying no radio. ..i'm gonna try and flash the rom from a sd card next..we'll see what happens..
jkrolcz said:
I am kinda stuck in the same spot, but mine is is the verizon logo screen, i tryed doing the power,camera and hte reset button but its till stuck, i tryed the relocker but i need to be in active sync
any help?
Click to expand...
Click to collapse
This just happened to me after flashing the ROM but not the RADIO yet. Flashing the Radio fixed the problem.
I've flashed the radio..then its stuck in the BL and i use the program to get me outta it then it just keeps saying i have no radio! what the hell..this sucks. i'm in the worst possible situation to have to buy a new phone
There are three parts to the "operating system" of your phone.
1. Bootloader (also called locker, unlocker, re-locker, SPL)
2. Radio
3. ROM
The three components are saved in discrete portions of the device's memory. Flashing one does not overwrite the others. All three must be compatible for the phone to operate properly. If you stop the upgrade process recommended by the ROM compiler prior to completion, your phone may not operate properly. If you flash the "leaked" 3.16 ROM package, it contains all three components.
To use the 3.16 stock OEM ROM, or a custom ROM based on the stock OEM 3.16 ROM, you must have a level 3.xx radio and a level 2.xx bootloader. The current implementations of those are the 3.27 radio and either the stock bootloader distributed with the "leaked" 3.16 ROM package, or the Olipro 2.40 unlocker.
If you are running a level 2.xx stock OEM ROM, or a custom ROM based on a stock 2.xx OEM ROM, you must have a level 1.xx bootloader and a level 1.xx radio.
Custom ROMs are not always named using the OEM convention, so you must research the custom ROM to determine whether it is based on a level 2.xx or 3.xx stock OEM ROM.
I hope this helps all of you get your phones back up and running.
FIXXXED!
So heres the best description I can give of what was going wrong for me..Its my first time trying flash to a different rom..and well it didn't go so well. First, I used the titan unlocker, then installed the radio (not sure which one) and then some form of the newer dcd rom and i was getting stuck on the black HTC smart mobility splash screen where it said "no radio". I had to have messed around for over 5 hours today at college trying to figure it out by doing different arrangements what order i installed the radio and unlocker and rom in. I couldn't get it to connect with activesync so i couldn't use the titanunlocker.exe..all i was going off of was RUU's. Im not sure whether or not what OS I was using effected it..I was playing in Vista earlier today but had done the correct steps to install the drivers, and now this last time i did it on XP. This last time I ran the 3.27 radio RUU as found.. here ( http://forum.xda-developers.com/showthread.php?t=362563 )...Theeen I ran this form of the newer sprint ROM. (I'm pretty sure they say it comes with a included in this RUU, but i'm just stating exactly what I did) the .651 rom can be found.. HERE ( http://forum.ppcgeeks.com/showthread.php?t=16806 ) He had a error when packing or something so you have to manually rename it to .exe because it was missing a e..I did this within winrar before extracting..ran that and about 10 minutes later it booted up and i've got service. I'm not going to promise that this is 100% functional all i'm saying is im out of that horrid black HTC screen where I can now go on to try and get the correct rom i wanted. Hope this helps..may be a bit confusing and probably did things wrong but this was my first time doing it all.
I saw something here about this from azclown and really want to know if it is true.
After flashing nueSPL is it possible to downgrade to other bootloaders?
I tried to run unlocker (Olipro 1.20) and it wouldn't connect right. Do I need to use relocker then load 1.20 then load stock rom. I am testing this out for another phone right now and am a little curious why this would be created so that no other bootloaders could be reloaded.
What I am realizing is that this bootloader is not such a good idea for Verizon users, being that they will not be able to revert to the stock rom (as Verizon has not released a GPS Rom yet).
Am I right here?
serfboreds said:
I saw something here about this from azclown and really want to know if it is true.
After flashing nueSPL is it possible to downgrade to other bootloaders?
I tried to run unlocker (Olipro 1.20) and it wouldn't connect right. Do I need to use relocker then load 1.20 then load stock rom. I am testing this out for another phone right now and am a little curious why this would be created so that no other bootloaders could be reloaded.
What I am realizing is that this bootloader is not such a good idea for Verizon users, being that they will not be able to revert to the stock rom (as Verizon has not released a GPS Rom yet).
Am I right here?
Click to expand...
Click to collapse
um, DO NOT attempt to DOWNGRADE your SPL unless you want a permanent brick.
reasoning:
ALL ATTEMPTS whatsoever to downgrade the radio to a pre-GPS radio have F-A-I-L-E-D. They have all resulted in BROKEN BRICKED IRREPARABLE devices.
1.xx SPLS are not (at least that i'm aware of, compatible with GPS radios)
therefore, you cannot downgrade your radio to 1.xx.
You can downgrade to olipro-2.40, but thats pretty much it. Unless your device is SuperCID, i would NOT ADVISE locking your device, because you will only be able to download updates signed by VZW, and as we all know - there are none.
If warranty is a concern,... it would be better to turn in a complete brick than a partial brick. flash a modified VZW OS Only with proper OEMDRIVERS, then run my relocker and lock the SPL down, then warranty it. /... I wouldn't suggest this for anything else, because in case of a bad OS flash, you'd be pretty screwed...
Thanks for chiming in on this no2chem, there's a lot of good information in that post!
no2chem said:
um, DO NOT attempt to DOWNGRADE your SPL unless you want a permanent brick.
reasoning:
ALL ATTEMPTS whatsoever to downgrade the radio to a pre-GPS radio have F-A-I-L-E-D. They have all resulted in BROKEN BRICKED IRREPARABLE devices.
1.xx SPLS are not (at least that i'm aware of, compatible with GPS radios)
therefore, you cannot downgrade your radio to 1.xx.
You can downgrade to olipro-2.40, but thats pretty much it. Unless your device is SuperCID, i would NOT ADVISE locking your device, because you will only be able to download updates signed by VZW, and as we all know - there are none.
If warranty is a concern,... it would be better to turn in a complete brick than a partial brick. flash a modified VZW OS Only with proper OEMDRIVERS, then run my relocker and lock the SPL down, then warranty it. /... I wouldn't suggest this for anything else, because in case of a bad OS flash, you'd be pretty screwed...
Click to expand...
Click to collapse
True, I see your point about returning a complete brick. The rest is fine I guess.
Thanks!
no2chem said:
:
ALL ATTEMPTS whatsoever to downgrade the radio to a pre-GPS radio have F-A-I-L-E-D. They have all resulted in BROKEN BRICKED IRREPARABLE devices.
Click to expand...
Click to collapse
now, by that do you mean they werere were bricked by downgrading the radio with nueSPL previously (or currently) loaded on the device, or downgrading the radio on a device that never had nueSPL loaded on it?
the only reason i ask this is because ive done several radio downgrades from olipro 2.4 to 1.2 to the stock radio/ROMs for refurbishment and ive never had a problem. i dont use the stock SPL because theres no tech around here smart enough to check it.
no2chem said:
um, DO NOT attempt to DOWNGRADE your SPL unless you want a permanent brick.
reasoning:
ALL ATTEMPTS whatsoever to downgrade the radio to a pre-GPS radio have F-A-I-L-E-D. They have all resulted in BROKEN BRICKED IRREPARABLE devices.
1.xx SPLS are not (at least that i'm aware of, compatible with GPS radios)
therefore, you cannot downgrade your radio to 1.xx.
You can downgrade to olipro-2.40, but thats pretty much it. Unless your device is SuperCID, i would NOT ADVISE locking your device, because you will only be able to download updates signed by VZW, and as we all know - there are none.
If warranty is a concern,... it would be better to turn in a complete brick than a partial brick. flash a modified VZW OS Only with proper OEMDRIVERS, then run my relocker and lock the SPL down, then warranty it. /... I wouldn't suggest this for anything else, because in case of a bad OS flash, you'd be pretty screwed...
Click to expand...
Click to collapse
No2chem.. I think I am an exception or my XV6800 must be special because I actually messed up my phone because i wanted the new Radio 3.42.02 but couldn't get my Phone to Flash From SD.. So I had to flash a sprint 3.56 ROM to get the Radio and then flashed Verizon kitchen before Sprint customization started.. but for some weird reason.. Sprint customization still ran after i flash the Verizon ROM.. My EPST Settings were all Sprint.. lols..
These are the steps I took to bring it back..
1. Ran Titan_Relocker to relock SPL from version 2.40 Olipro
2. Flashed Stock Verizon ROM and let Verizon Customization run
3. Unlock using NueSPL2.47 letting it format my SD card to enable Flashing from SD [Thank GOD you added this feature]
4. Placed the new Radio 3.42.30 onto my SD card and enter Bootloader and Flashed it [Thanks to You]
5. then flashed my Verizon kitchen.. All with no problem..
I've discussed this method with some of the guys over at PPCKitchen.org and they were concerned about me bricking my phone.. but I said oh what the heck.. my phone is already messed up..
every one was supprised that it worked.. lol.. I must be one of the lucky few..
b16daddy said:
No2chem.. I think I am an exception or my XV6800 must be special because I actually messed up my phone because i wanted the new Radio 3.42.02 but couldn't get my Phone to Flash From SD.. So I had to flash a sprint 3.56 ROM to get the Radio and then flashed Verizon kitchen before Sprint customization started.. but for some weird reason.. Sprint customization still ran after i flash the Verizon ROM.. My EPST Settings were all Sprint.. lols..
These are the steps I took to bring it back..
1. Ran Titan_Relocker to relock SPL from version 2.40 Olipro
2. Flashed Stock Verizon ROM and let Verizon Customization run
3. Unlock using NueSPL2.47 letting it format my SD card to enable Flashing from SD [Thank GOD you added this feature]
4. Placed the new Radio 3.42.30 onto my SD card and enter Bootloader and Flashed it [Thanks to You]
5. then flashed my Verizon kitchen.. All with no problem..
I've discussed this method with some of the guys over at PPCKitchen.org and they were concerned about me bricking my phone.. but I said oh what the heck.. my phone is already messed up..
every one was supprised that it worked.. lol.. I must be one of the lucky few..
Click to expand...
Click to collapse
weird. what were you running before step 1?
the problem seems to manifest itself when you take a GPS radio, and flash a 2.xx RADIO onto it. When you flashed the verizon stock rom, are you sure you had the 2.xx radio on it?
the reason everyone was concerned about your phone though, was because there were several bricks produced by downgrading radios - ask ImCokeMan, he'll tell you..
no2chem said:
weird. what were you running before step 1?
the problem seems to manifest itself when you take a GPS radio, and flash a 2.xx RADIO onto it. When you flashed the verizon stock rom, are you sure you had the 2.xx radio on it?
the reason everyone was concerned about your phone though, was because there were several bricks produced by downgrading radios - ask ImCokeMan, he'll tell you..
Click to expand...
Click to collapse
I didn't quite understand your question..
"When you flashed the verizon stock rom, are you sure you had the 2.xx radio on it?"
When I ran Titan_Relocker.. it installed version 1.06..
Before the Sprint radio upgrade I had...
Hard SPL2.40 Olipro
Radio 3.39.10
No2chem wm6.1 5067 Kitchen
I have also went from a GPS radio to the stock verizon radio/rom a few times because of accidentally letting sprint customizations run.
i am not 100% sure if i had the stock radio on my phone. however it worked with stock verizon rom and phone/ data/ text all worked in stock verizon rom/radio.... so i assume it was the correct radio since it worked with the stock rom...?
EDIT: i do believe i had verizon 1.3 radio on my phone after flashing back from a GPS radio
also i remember reading somewhere that if you do flash back to a stock radio/ rom that it might say stock radio but it will still have components of the gps radio's... i think i read it at ppcgeeks
aguas said:
ive done several radio downgrades from olipro 2.4 to 1.2 to the stock radio/ROMs for refurbishment and ive never had a problem. i dont use the stock SPL because theres no tech around here smart enough to check it.
Click to expand...
Click to collapse
i also have downgraded radio from 3.xx to 1.xx without any problems.
I flashed back to non gps as well. I was having bad experiences with dcd's 2.x so I went to his 1.7. No issues flashing at all.
I have also downgraded to 2 different phones from GPS radios to NON-GPS radios.... Verizons stock radio is 1.30, not a 2.x radio, so that may be the issue for some other folks on different carriers.... It may be an incompatibility with 2.x radios and GPS radios.... I have a folder on my desktop that has all the files necessary AND the instructions clearly written out on how to downgrade..... It has saved my butt 2 times now....
azclown said:
I have also downgraded to 2 different phones from GPS radios to NON-GPS radios.... Verizons stock radio is 1.30, not a 2.x radio, so that may be the issue for some other folks on different carriers.... It may be an incompatibility with 2.x radios and GPS radios.... I have a folder on my desktop that has all the files necessary AND the instructions clearly written out on how to downgrade..... It has saved my butt 2 times now....
Click to expand...
Click to collapse
hmm, it might actually be an issue with 2.X radios. I'll do a little bit of research on this one.
no2chem said:
hmm, it might actually be an issue with 2.X radios. I'll do a little bit of research on this one.
Click to expand...
Click to collapse
the radio i downgraded to was 1.59
no2chem said:
um, DO NOT attempt to DOWNGRADE your SPL unless you want a permanent brick.
Click to expand...
Click to collapse
Ya I used to switch from gps to nongps all the time back when the original leaked radio was the only one out... I also converted my last phone (sent in for broken button) back to complete stock vzw (locked and all) as well....
I haven't tried doing any downgrading after installing nueSPL though... are you indicating this is a probelm after flashing nueSPL? Your post has me a 'lil scared now but I'll wait for followups before I attempt anything.. no plans to go back to nongps anyways, though... the new radios seem to have the bugs worked out.
Zenoran said:
Ya I used to switch from gps to nongps all the time back when the original leaked radio was the only one out... I also converted my last phone (sent in for broken button) back to complete stock vzw (locked and all) as well....
I haven't tried doing any downgrading after installing nueSPL though... are you indicating this is a probelm after flashing nueSPL? Your post has me a 'lil scared now but I'll wait for followups before I attempt anything.. no plans to go back to nongps anyways, though... the new radios seem to have the bugs worked out.
Click to expand...
Click to collapse
Only No2chem knows for sure, but after reading his post again I think he's saying you can downgrade to Ollipro 2.4, if thats the case then one should be able to downgrade back to stock as well....
I think no2 is onto something here. I am on VZW also and have gone back to stock from a 3.xx gps radio --> stock 1.30 radio.
I have a feeling that for once we may be glad that verizon never does any updates - they still use 1.30 radio - and that may be the common thread in all our (vzw) success at going back to non gps.
I'd say that I was onto this before him.... He just knows how to verify it...
azclown said:
I'd say that I was onto this before him.... He just knows how to verify it...
Click to expand...
Click to collapse
and i would agree with you!
Speaking of the man himself ^^^^ .. I would note that you had all the data, I just thought it was odd that anyone who tried to go back to a 2.X radio would brick it, while us verizon folks would go back to 1.X and have no issues....
Okay, I've looked around the forums and tried a number of things. I started out wondering if I should install the new update. Got to looking around and decided to just install a custom rom. Was a little weary because of my experience with the xv6700. Anyway. Ran SPL Unlocker to install 2.40 Oilpro. Installed the Radio 3.27.00 and dcd 2.1.0....did a *228 and then my phone would not pick up service. Tried a few things but since I was in a hurry just ran the vzw update and it fixed it. Later I come back and decided to try an do this right. So I run the RadioRefurbish. It worked and rolled me back to 1.35_002. Still no GPS. I've tried everything including this:
http://wiki.xda-developers.com/index.php?pagename=VerizonAGPSFix
Still no change. I do not get a fix. I mean GPS Viewer can see the GPS but I never get anything from it. I have a bluetooth GPS and can get a fix inside on a cold start in 5 min max. I left this thing for hours. Indoor, in the car, etc... nothing. I'm at a loss. I am currently running SPL 2.40 Oilpro. Radio 3.42.02 and dcd 3.2.3. With PRI 1.35_002. I had read of success with the new vzw PRI and NueSpl 2.47. Tried to install 2.47. Gives me checks on all of the prequisites and then when I continue it goes into the bootloader and displays spl 2.07 I have to then soft reset and if I go back to the bootloader it's still 2.40. I am at a loss and would really like to get this working. Any suggestion from any of you oober smart people out there would be great or just someone that might know what else to try.
P.S. Thought about trying to flash back to the original rom but had read where that can easily brick my phone. So that's about the only thing I haven't tried.
oober? lol...
First, what guide were you using that had you using such an outdated bootloader, radio, and rom?!
Secondly, am I to understand that you ran the new MR1, WinMo 6.1 from Verizon, with the new PRI? If so, I would try GC14's fix, he has a thread on it, to roll you back to the old PRI.
Thirdly, definetly use NueSPL 2.47 for flashing. Grab the newest radio, 3.42.50. Flash that. Grab the newest dcd, 3.2.6, flash that. Then install the Verizon Carrier Cab. Then do a *228 option 1. Call verizon *611 if need be, to re authenticate the phone if you can't make calls or use data.
Fourthly, go into the Phone control panel, and Get Settings on the Location option. Make sure location is enabled.
Fifth, do the new aGPS fix that was posted by gc14.
Lastly, get a program like Google Maps that is known to be highly compatible with GPS. Set it's GPS options to COM4, 4800 baud. And enable Use GPS. After initializing GPS for about 15 seconds, you should see a very fast lock of about 5-20 seconds or so with the new aGPS fix.
jjsparks3589 said:
...Installed the Radio 3.27.00 and dcd 2.1.0.......
Click to expand...
Click to collapse
Is that even a GPS enabled rom?
Why are you using such an old rom?
PRI rollback really required?
Is the PRI roll back really required? I went from the MR1 update to DCD 3.2.6 and radio 3.42.40 and got GPS working without rolling back the PRI. My process was;
1. Titan GPS Fix (almost the same as AGPS fix wiki)
2. PRI from hell (only did first step, flashing back to stock)
3. Fix from PPCGeeks (My GPS did not work at all till I did this)
4. Verizon xv6800 aGPS Fix
As far as the PPCGeeks fix goes, I'm now using the PDE IP & port# in the SUPL_AGPS keys in the registry, long with GPSMODE=4. Everything seems to be working great. Maybe I'm just a fluke.
The stock rom I flashed back to when I started the PRI from hell fix was VzW_titan_20273_a2.rar (I think this is the right one, only one I found on my laptop that seems big enough). Now that I think about it I did do the second step on the PRI from hell, I changed my bootloader to 2.40, and reloaded DCD 3.2.6.
i believe that guide would be from PhoneNews as its still one of the top results for "GPS on HTC Titan." Of course no one reads that there is an updated guide, but even that isn't that recent (around release time of 3.35). plus, they give ZERO credit to DCD or anyone on any forums, and took if upon themselves to host all the downloads, and not link to the forums where these originated.
3.42.50 has issues with gps on some phone for some reason. flash with the sprint radio and it will work with out issue.
aguas said:
i believe that guide would be from PhoneNews as its still one of the top results for "GPS on HTC Titan." Of course no one reads that there is an updated guide, but even that isn't that recent (around release time of 3.35). plus, they give ZERO credit to DCD or anyone on any forums, and took if upon themselves to host all the downloads, and not link to the forums where these originated.
Click to expand...
Click to collapse
Well, not saying it's a better fix, just the one that got mine working. But thanks to the xda-dev forums it went from a searchlight to a laser beam.
I've got a solution for GPS on the MR1 release for the xv6800. I should hopefully have a full release soon, but there is hope if you're stuck and unable to get anything except (possibly) VZ Navigator working due to the firmware being placed into locked down GPS mode.
Protonus said:
oober? lol...
First, what guide were you using that had you using such an outdated bootloader, radio, and rom?!
Secondly, am I to understand that you ran the new MR1, WinMo 6.1 from Verizon, with the new PRI? If so, I would try GC14's fix, he has a thread on it, to roll you back to the old PRI.
Thirdly, definetly use NueSPL 2.47 for flashing. Grab the newest radio, 3.42.50. Flash that. Grab the newest dcd, 3.2.6, flash that. Then install the Verizon Carrier Cab. Then do a *228 option 1. Call verizon *611 if need be, to re authenticate the phone if you can't make calls or use data.
Fourthly, go into the Phone control panel, and Get Settings on the Location option. Make sure location is enabled.
Fifth, do the new aGPS fix that was posted by gc14.
Lastly, get a program like Google Maps that is known to be highly compatible with GPS. Set it's GPS options to COM4, 4800 baud. And enable Use GPS. After initializing GPS for about 15 seconds, you should see a very fast lock of about 5-20 seconds or so with the new aGPS fix.
Click to expand...
Click to collapse
I was able to roll back to PRI 1.35_002 using Radiorefurbish. I would love to install nuespl 2.47, but how. I downloaded it, ran it. It formated my card and ran. Reboots into the bootloader with a spl of 2.07 and just stays there. When I soft reset, reboots as normal. If I enter the Bootloader after that it's still 2.40. I've tried it from a few different Roms thinking that maybe there was an issue. BTW, How bad (dangerous) is it to flash back to original stock. It's about the only thing I haven't tried. I had read that going back to a non GPS rom is a bad idea.
jjsparks3589 said:
I was able to roll back to PRI 1.35_002 using Radiorefurbish. I would love to install nuespl 2.47, but how. I downloaded it, ran it. It formated my card and ran. Reboots into the bootloader with a spl of 2.07 and just stays there. When I soft reset, reboots as normal. If I enter the Bootloader after that it's still 2.40. I've tried it from a few different Roms thinking that maybe there was an issue. BTW, How bad (dangerous) is it to flash back to original stock. It's about the only thing I haven't tried. I had read that going back to a non GPS rom is a bad idea.
Click to expand...
Click to collapse
The reason you are stuck in 2.07 could be because of your sd card. try a different card. SanDisk works really well with them.
jjsparks3589 said:
I was able to roll back to PRI 1.35_002 using Radiorefurbish. I would love to install nuespl 2.47, but how. I downloaded it, ran it. It formated my card and ran. Reboots into the bootloader with a spl of 2.07 and just stays there. When I soft reset, reboots as normal. If I enter the Bootloader after that it's still 2.40. I've tried it from a few different Roms thinking that maybe there was an issue. BTW, How bad (dangerous) is it to flash back to original stock. It's about the only thing I haven't tried. I had read that going back to a non GPS rom is a bad idea.
Click to expand...
Click to collapse
I had the same problem trying to use nuespl 2.47. I just kept getting stuck at that screen. soft resetting and trying again. I gave up for a few hours... and came back to it and with absolutely no rhyme or reason, it just decided to work one time... I was also using the SD card method with a 2gig micro. I hope it just decides to work for you.
animez said:
Is the PRI roll back really required? I went from the MR1 update to DCD 3.2.6 and radio 3.42.40 and got GPS working without rolling back the PRI. My process was;
1. Titan GPS Fix (almost the same as AGPS fix wiki)
2. PRI from hell (only did first step, flashing back to stock)
3. Fix from PPCGeeks (My GPS did not work at all till I did this)
4. Verizon xv6800 aGPS Fix
As far as the PPCGeeks fix goes, I'm now using the PDE IP & port# in the SUPL_AGPS keys in the registry, long with GPSMODE=4. Everything seems to be working great. Maybe I'm just a fluke.
The stock rom I flashed back to when I started the PRI from hell fix was VzW_titan_20273_a2.rar (I think this is the right one, only one I found on my laptop that seems big enough). Now that I think about it I did do the second step on the PRI from hell, I changed my bootloader to 2.40, and reloaded DCD 3.2.6.
Click to expand...
Click to collapse
Do you need to use a relocker before flashing the stock rom? Edit: NVM this
Also, can you share VzW_titan_20273_a2.rar somehow? Any search for it only brings me back to this thread :\... Thanks
Just use the gc14 guide to roll back to the old PRI as stated and be done with it...
3.42.50 radio works fine with GPS, doubly fine with the aGPS hack.
deboy_001 said:
Do you need to use a relocker before flashing the stock rom? Edit: NVM this
Also, can you share VzW_titan_20273_a2.rar somehow? Any search for it only brings me back to this thread :\... Thanks
Click to expand...
Click to collapse
I should have room to upload it on my comcast account. I'll PM you a link when it's done. Standard warning that flashing back to stock has bricked phones (from what I've read). Didn't happen to me, just saying.
Flashing back to MR1 should work. From what I have been told, the problem occurs if you flash to a pre-GPS version after having upgraded to a GPS-enabled version.
Skywing said:
Flashing back to MR1 should work. From what I have been told, the problem occurs if you flash to a pre-GPS version after having upgraded to a GPS-enabled version.
Click to expand...
Click to collapse
ah yes... MR1 would be no problem, but I believe pri from hell fix first step is referring to the pre-MR1 stock (if I'm not mistaken). so I see where animez is coming with the warning. At that step, all you can do is hope for the best I suppose...
Ive flashed back to the ut of the box" stock rom form the SD card several times with no issues at all.
now as far the radio i don go below 3.xx
I still cant get my GPS to work after i updated my PRI, even before i updated it was very hit or miss, I would get 10 sec locks or none at all for days
**Posted at PPCG also.....
Hey guys just wanted to see if you can shed some light on my situation. I have flashed other TItan's before with no issues and then came this little butterfly.
I flashed it to Metropcs from stock Sprint ROM. Then I unlocked it using 2.47 SPL. This is where its a bit different for me. I have always used 2.4 to unlock, not sure if that made a difference this time.
Then I tried running the RELOADED ROM with no luck. Then I tried Ryans Cricket ROM with no luck. It starts with HTC and then when it goes to the next splash screen it gets stuck there for hours.
I even tried to put a basic kitchen together from PPCKitchen, but that didn't even work either...
I am all out of ideas.
I would give you specs, but I cant get into phone. I can at least get it into bootloader mode to load different ROMS.
Here is what I see when I soft reset:
Home splash screen
D 3.2.6
R 1.32.00
2.4 SPL????? **Tried this already and that didn't do anything. In bootloader stills hows 2.47...
Did you update your radio to 3.42...the ROMS you are trying to use need to have a radio of 3.35+
To get the radio....easiest way to do that, instead of messing with it alone...do the following
unlocker 2.40olipro/nuesp2.47--->stock ROM--> then custom ROM
you need to upgrade radio
You rom and spl are fine. Just upgrade your radio to something like 3.42.40 or 3.42.50