I know my phone isn't bricked...but I'm stuck.
I wanted to restore the Verizon stock ROM (for reasons I'll post in a different thread).
I was originally at DCD 2.1.0 with the Radio 3.17.
I got the Verizon Stock Rom from ftp://up.ppcgeeks.com/Titan/Users/vboyz
I ran the Titan unlocker, and changed the nbh to the verizon one and flashed it.
Now I'm stuck on the white Verizon screen.
I know I did it wrong, but I couldn't find a consistent post with all the links and instructions how to do it.
HELP!
For starters you might want to use an actual Verizon Stock ROM:
http://forum.xda-developers.com/showpost.php?p=1845171&postcount=13
THANK YOU! I am downloading those now.
What steps do I need to follow
I have the relocker, and the verizon files. All I can get to is the SPL2.4 Olipro screen and the white verizon screen...help!
I just reloaded the dcd rom, ran the unlocker, loaded the verizon rom, and it all works now
Please give exact steps used
dkreifus said:
THANK YOU! I am downloading those now.
What steps do I need to follow
I have the relocker, and the verizon files. All I can get to is the SPL2.4 Olipro screen and the white verizon screen...help!
I just reloaded the dcd rom, ran the unlocker, loaded the verizon rom, and it all works now
Click to expand...
Click to collapse
Please post the exact steps you used as these 'stock' verizon ROMs do not as yet exist. I will explain: The ROM you used is an image taken of a phone, a full image of someone's phone, and not really the factory 'out of box' software that is available for the Sprint unit. The reason that this is important is that it could lead possibly to a problem, or at least I would like to see if it does, before I mess with it. The phone comes stock with the 1.6 bootloader and is keyed to look for valid signed by the vendor software, and if it is not signed by the vendor it will not get past 0% and if it is signed by Sprint and you try to load it on a verizon unit it goes 1 % and gets a 'invalid vendor id' error and stops. On a Sprint unit if you mess up and get the wrong radio/ROM combo and maybe get the 1.6 bootloader back on by mistake then you can fix it with the stock 2.09 Sprint RUU because it exists and is signed. If you do this on a Verizon unit at the moment you might have trouble with the 1.6 bootloader as it is looking for signed software and I wonder if that image file satisfies this ?????? So I guess the long and the short of it is to know if you re-locked the phone (bootloader shows 1.6) BEFORE you ran back in the stock Verizon image ??? Did you have the unlocked (OliPro 2.4 bootloader) on the phone when you restored that stock image ???? Thanks.
madman34 said:
Please post the exact steps you used as these 'stock' verizon ROMs do not as yet exist. I will explain: The ROM you used is an image taken of a phone, a full image of someone's phone, and not really the factory 'out of box' software that is available for the Sprint unit. The reason that this is important is that it could lead possibly to a problem, or at least I would like to see if it does, before I mess with it. The phone comes stock with the 1.6 bootloader and is keyed to look for valid signed by the vendor software, and if it is not signed by the vendor it will not get past 0% and if it is signed by Sprint and you try to load it on a verizon unit it goes 1 % and gets a 'invalid vendor id' error and stops. On a Sprint unit if you mess up and get the wrong radio/ROM combo and maybe get the 1.6 bootloader back on by mistake then you can fix it with the stock 2.09 Sprint RUU because it exists and is signed. If you do this on a Verizon unit at the moment you might have trouble with the 1.6 bootloader as it is looking for signed software and I wonder if that image file satisfies this ?????? So I guess the long and the short of it is to know if you re-locked the phone (bootloader shows 1.6) BEFORE you ran back in the stock Verizon image ??? Did you have the unlocked (OliPro 2.4 bootloader) on the phone when you restored that stock image ???? Thanks.
Click to expand...
Click to collapse
I was stuck at the OliPro 2.4 bootloader. It would freeze at the white screen, or I could get to the bootloader. So I reloaded the DCD 2.x image.
Once it was up and running, I used the relocker, and downgrader the bootloader.
From there, I loaded the 'stock' verizon image, and presto, it all took like magic.
I was fortunate enough to not panic, and realize that its not bricked. Just a matter of trial/error and patience.
Coolness
dkreifus said:
I was stuck at the OliPro 2.4 bootloader. It would freeze at the white screen, or I could get to the bootloader. So I reloaded the DCD 2.x image.
Once it was up and running, I used the relocker, and downgrader the bootloader.
From there, I loaded the 'stock' verizon image, and presto, it all took like magic.
I was fortunate enough to not panic, and realize that its not bricked. Just a matter of trial/error and patience.
Click to expand...
Click to collapse
Ok so it is nice to know that this image will store back,,,,thanks.
You totally wrote complete misinformation. The ROM I linked is not a dump of a running ROM. It's a complete Ship ROM from VZW. The link I provided is from a complete thread where this was discussed. You might want to actually look at the files before posting about them. If you would have extracted the NBH you would have noticed that it was a complete ROM not just the OS.nb.
Just what blazingwolf said,,,,,,,
jrebeiro said:
You totally wrote complete misinformation. The ROM I linked is not a dump of a running ROM. It's a complete Ship ROM from VZW. The link I provided is from a complete thread where this was discussed. You might want to actually look at the files before posting about them. If you would have extracted the NBH you would have noticed that it was a complete ROM not just the OS.nb.
Click to expand...
Click to collapse
Anyway, it is acknowledged as a ship ROM, but Blazingwolf said that that since there has been no release from HTC for the Verizon as there was for the Sprint that these ROMs were actually extracted from a unit out-of-box and compiled correctly, and do contain all data that they are supposed to contain. If you look at the utstar.com downloads section you will see that there is no RUU for the VZW unit but there is for the Sprint unit, this being because Sprint released 2.17 and had broken some stuff and had to release 2.09 which you do find there. So I did not mean that I was worried about completeness, as I did de-compile and look, but just was curious to see someone get it done with these because they were obtained in a different way than usual. I think it is a cool way to do it and would like to have the tool used to pull a ROM from a unit so that I could do the same with mine configured as it is and return to it anytime I wanted to.
dude... the ROM I linked to is digitally signed by Verizon.
If you are suggesting that someone was capable of fully ripping the IPL/SPL/Radio/Splash/ExtROM/OS from a running Titan AND getting VZW's digital certificate to sign the NBH then I want to meet the person who did it so we won't need to Hard SPL our devices anymore!
Related
Greetings all. I made an error during the upgrade to the new 3.16 ROM and accidently booted back to the stock bootloader before flashing the radio. Now I freeze on the splash screen because my ROM is the 3.16 and my radio is the old stock, so I need the VX 6800 verizon stock image to go back and then forward, or a way to get the 2.4 bootloader back on so I can flash the radio forward. utstar.com does not have it and the sprint one gives a vendor ID error, so I need the VZW image, anyone got ??????Thanks
Put your phone in bootloader mode (hold power and camera while soft reseting). Now flash the radio ROM. It should work fine.
Failed, because ...
Because the bootloader got back to stock and it will not let me upgrade it again, guess it is stuck til i get stock ROM
Then flash the new bootloader. You shouldn't need to go back to the stock ROM to accomplish this. However, the stock ROM is on the PPCGeeks FTP. In vboyz files.
How do I get there ????
I am a member there as well but how do I get to the FTP server you speak of ??
You don't need the stock rom.
Connect your phone to the computer via USB.
Hold the power button, camera button, and use the stylus to soft reset all at the same time, this will put you into the bootloader.
Your PC should detect the phone and it should say USB at the bottom of your phone.
Run the 2.4 bootloader self extracting executable and use the RUU to flash the bootloader...if the self extracting executable doesn't work, you can just extract the files and run the .bat file.
Once the new bootloader is on there, you'll have to get into the bootloader using the power button, camera button, and soft reset again due to the fact that you have the ROM on there without the new radio. (your phone will freeze at the verizon splash screen).
Once back into your freshly flashed bootloader, follow the same instructions above and flash the radio.
Done.
If you do decide to go back to stock, remember that Verizon's latest version is 2.09 (Sprint is at 2.17 or something).
I need it too.
Just in case I have to send the phone in for repair.
been trying all that for hours
I have been trying all the ways you have mentioned for hours and with the 3.16 ROM and the old radio and bootloader it will not let me do the new bootloader,,,,,,,just have to find the 2.09 stock ROM, my only way out at this point. My login at geeks will not let my to the ftp server.
I know this has been posted in the forum here a couple of time but here it is again (though specific to the Verizon ROM folder). ftp://up.ppcgeeks.com/Titan/Users/vboyz
Username: ppcgeeks
Password: ezupload
Something must be up....
There's no reason why you would need the stock rom to flash your bootloader....
Guess you can try it though.
I seem to have done the same thing, however when I go to reload the newer bootloader it freezes at 0% and I get the ERROR [262]: UPDATE ERROR each time, even when going through the "recovery" process it guides through.
Any ideas?
Heres where we are now, conclusion
Well to update everyone on whats happening: The unit was less than a month old so the VZ store swapped it out for me, although I wish I could have kept it to putter with because I think I know what went wrong and how to fix it. First of all, I too had the bootloader fall back to the stock one and I got the error mentioned above saying that it could not copy the files for the 2.04 bootloader, so it was stuck with the 3.16 ROM, the old radio, and the old bootloader which causes the thing to freeze at the splash screen, and because of the stated incompatability between the old bootloader and the new ROM is causing the error at 0% when copying files. The reason I wanted to fall back to the stock 2.09 ROM was because I know it would load and allow me to go forward again. The reason I know is that I got the Sprint 2.09 from the utstar.com page and it went to 2% on the ROM before giving the 'VENDOR ID' error and stopping, so this means that it would take the VZ load if I could get it, but it is not on the utstar page. I did get the file from VZBOYZ ftp but I am pretty sure that it is not totally stock as it goes to 0% and fails, not even as far as the sprint ROM did so I think that it fails the needed checksum validation in the stock bootloader. If I had suspected that the stock image was not available in the first place, I never would have gone forward with it in the first place and would avise all others (Verizon units that is) NOT to do it either until a true stock ROM and radio load exist to put it back. VZBOYZ does not have the radio load so even if it passed the validation and put the ROM back you would have a brick because the radio load needs reverting also. Sprint users are lucky because you have this, and I will try again once I know I have the stuff to go back. Thanks for all the help and someone please let me know if the real stock loads do appear somewhere, probably will happen when Verizon releases the 2.17 update then the 2.09 for them will appear on the utstar page i bet. Thanks all.
madman34 said:
Greetings all. I made an error during the upgrade to the new 3.16 ROM and accidently booted back to the stock bootloader before flashing the radio. Now I freeze on the splash screen because my ROM is the 3.16 and my radio is the old stock, so I need the VX 6800 verizon stock image to go back and then forward, or a way to get the 2.4 bootloader back on so I can flash the radio forward. utstar.com does not have it and the sprint one gives a vendor ID error, so I need the VZW image, anyone got ??????Thanks
Click to expand...
Click to collapse
this little bit of info helped me with the same issue. and my phone after 228 was able to make and get calls and also use the internet.
i now have the new radio and the new dcd 2.20 rom
I have since learned (After reading through hundreds of posts on this thread), that is WRONG for the VX6800. After installing the bootloader Hard_MFG_SPL_2.40_RUU_signed, I should have installed the Radio 3.27 Rom FIRST, and THEN the Titan 2.0 Rom.
Just to let you know in more detailed terms what I did to get out of stuck nightmare that is the Verizon white screen with the red letters and big graphic check mark on top:
(1) Got the Tricolor Bootloader Screen to come up. You must simultaneously: (a) hold down the power button; (b) hold down the camera button; and (c) use your stylus to press the little reset button in the hole at the bottom of your VX6800. This should pop up the Tricolor Bootloader screen if you'd installed this first, as instructed.
(2) Then plugged the VX6800 into the computer's USB port. As the bootloader earlier instructed, I made sure that USB was NOT enabled in "Windows Mobile Device Center" (should be in your start->programs menu). Click on connection settings and turn off the checkbox for USB connection.
(3) Then ran the RADIO 3.17 Rom loader (not the Titan 2.0). It loaded in Radio 3.27 without a hitch. The VX6800 then rebooted. It was not stuck on the white Verizon screen with the red lettering.
(4) Then ran the Titan 2.09 Rom loader. It loaded without a hitch. It then rebooted, and I was done with this portion.
this is from: http://forum.xda-developers.com/showthread.php?p=1870224
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.
hi, i just got the XV6800 from verizon today because my Moto Q9m died after only 7 months. so they gave me this for it. now after reading the forum and many other sites and tutorials. i am ready to flash my phone. is this the easiest "[Tutorial] Verizon xv6800 Custom ROM Flashing" to follow? i read it and it didn't seem that bad. just wanted to know and make sure if the names of the files he speaks of are the most recent one's. and i take it i should back up my factory setting file off the phone before i attempt to do this. a few of my friends at work has this phone and i liked the fact they have it doing somethings the iphone does. like you can scroll through contacts by just sliding your finger and all. i would like to do this stuff as well. is that all then included in the flash or must i install other apps.
Phone has
Software Version: 2.09.605.8 (ROM version)
Firmware Version: 1.30.60 (radio version)
please help, really appreciate it
thanks
His guide is pretty good. Everything is up to date except for the SPL. I would recommend using the latest bootloader put out by No2Chem - version 2.47, but that's my only change from his guide. It installs via an SD card only, whereas his guide uses the computer to get Olipro's 2.4. You should be able to find a guide to using SD cards to flash as well as links to 2.47 throughout this forum and ppcgeeks.
Or you can certainly follow his guide as written and you'll be just fine.
Ivan
Keep in mind that using No2chems SPL you cannot go back to stock Verizon radio and ROM..... So if your phone breaks, you have to bring it in as is and chance they don't notice the difference.....
ok on the fact that once you go new flash you can't go back to factory. so before i do this i should back up my contacts. since the phone is new i don't have anything else on it. is there anything else i should back up either? so after its flashed then how do i get the programs on to scroll by just sliding? is that stuff that can be put on with out flashing this. but from what i read on here flash makes the phone run much better anyway
azclown said:
Keep in mind that using No2chems SPL you cannot go back to stock Verizon radio and ROM..... So if your phone breaks, you have to bring it in as is and chance they don't notice the difference.....
Click to expand...
Click to collapse
You can flash the old bootloader back on the phone after upgrading to 2.47 though then go back to the original ROM and radio, you just cant flash provider ROM from 2.47 just like you cannot from 2.40.
Am I missing something about what you are saying?
so i can flash to newer rom and be able to go back.. now i'm confused
if you i install themes must it be a new roM
serfboreds said:
You can flash the old bootloader back on the phone after upgrading to 2.47 though then go back to the original ROM and radio, you just cant flash provider ROM from 2.47 just like you cannot from 2.40.
Am I missing something about what you are saying?
Click to expand...
Click to collapse
I'm pretty sure he's simply saying: if you use No2Chem's 2.47, you can't directly flash back to Verizon's stock firmware, but if you flash back to the old bootloader (factory bootloader), you can.
and LilSnoop40, as far as I know, all of those files are the most up-to-date that I could find. I may update the guide because I am noticing (from other people's experience) that after the 3.42.02 firmware (which I flashed to, not 3.42.30), that you need to use a Low-density MicroSD (not MicroSDHC) card to flash on the new radios.
If you need help with any of this in more detail, feel free to contact me.
serfboreds said:
You can flash the old bootloader back on the phone after upgrading to 2.47 though then go back to the original ROM and radio, you just cant flash provider ROM from 2.47 just like you cannot from 2.40.
Am I missing something about what you are saying?
Click to expand...
Click to collapse
serfs - As I understand it, once you flash to No2chems SPL, you cannot go back to a non GPS rom. I asked this in his thread and it was confirmed. Now, they didn't say whether you could flash Olli Pro and then use his re-locker and then flash the stock ROM.... Look at this post....
http://forum.ppcgeeks.com/showthread.php?t=30561&page=4
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....
Check your current bootloader
1. Hard reset your phone by holding down both softkeys, hitting reset, and pressing R (just for good measure)
2.
Hit POWER-CAMERA-RESET to check what version of bootloader you have installed.
* At the tri-colour bootscreen you will see the version number installed.
* if it is 1.04 or 1.06 then your Titan is locked and has the correct bootloader to flash to the stock ROM of your choice --> skip to step III
* if it is 1.20, 2.40, or 2.47 then your phone is unlocked with a third party bootloader and must relock your phone.
---------------------------------------------------------------------------
I have a Sprint HTC Mogul and have been shuffling through all the threads and still confused, sort of...
I am at the Tri-color screen and none of those version number matches mine.
on my tri-color screen it displays:
Tita100
SPL-2.06.0000
CPLD-9
i searched the board and found but it didnt give me a clear answer.
http://forum.xda-developers.com/showthread.php?t=284404
So far i have downloaded
Sprint Cab
dcd_titan_3.2.5.exe
Titan_Radio_ROM_3.42.40.exe
[OliPro MFG 2.40] (Hard SPL)
I'm hoping someone can help me figure this out, whether or not i need to downgrade/upgrade.
And Also was wondering what type of neat things i can do with the roms/kitchen im a total noob at this but trying to make sense of all of this.
Other Phone info:
rom Version 3.35.651.2
radio ver. 3.35.04
I'm *PRETTY SURE* that's just an updated version of the relocker SPL.
You should be able to flash back to a stock (non-GPS if I remember right) ROM from there.
I think what *MAY* have happened was the process got interrupted when you were unlocking?
so I *BELIEVE* your best bet is to return to stock, and unlock using SPL 2.40, then flashing on the new ROM/Radio
If I'm wrong, I'm sorry; It's early in the morning and I'm not quite awake enough to comprehend everything yet.
scrawnyb said:
flash back to a stock (non-GPS if I remember right) ROM from there.
so I *BELIEVE* your best bet is to return to stock, and unlock using SPL 2.40, then flashing on the new ROM/Radio
If I'm wrong, I'm sorry; It's early in the morning and I'm not quite awake enough to comprehend everything yet.
Click to expand...
Click to collapse
You are right on the money.......
that should be the stock bootloader for a stock gps rom.
if you want a custom rom you will need to unlock using 2.40 or 2.47.
kitchens just allow you to cook in apps that you want instead of installing them later. the problem is the install is permanent and they cannot be removed.
i prefer to flash a clean rom and install my apps later.
im pretty sure 2.06 is the temporary bootloader used by no2chem's nueSPL to ram with 2.47. if your bootloader shows 2.06 you will need to flash nueSPL again as it did not flash correctly. 2.07 is nueSPL Relocker.
i had not heard of anyone getting "stuck" in 2.06 and the op didn't mention he had tried flashing 2.47 or relocking.
i think you are correct though as i just checked and i am @ 2.07 (relocked).
lafester said:
i had not heard of anyone getting "stuck" in 2.06 and the op didn't mention he had tried flashing 2.47 or relocking.
i think you are correct though as i just checked and i am @ 2.07 (relocked).
Click to expand...
Click to collapse
it happened to me, although i didnt get stuck. it was flashed on a card that isnt flashing compatible (telus). i only noticed because it didnt reset itself like it said it should have. returned the card, got a San Disk, and reflashed nueSPL. this time it soft reset itself, and displayed the correct bootloader, 2.47.
I got stuck in 2.06 last night... earlier in the day I dropped my mogul in water and somehow cracked the screen at the same time. After drying everything out for 12 hours the phone came on with barely anything on the screen, I got the phone into bootloader (it was at 2.47) flashed a stock sprint rom, I immediately ran the nueSPL relocker (had to use my mobler to see the screen), after the relocker ran I was stuck in a 2.06 bootloader for some time, eventually I got out of the bootloader (not quite sure how... I flashed the stock sprint rom a few more times and mash some buttons) eventually I was able to run the relocker again and get my phone back to 2.07... a little bit of trouble but it was worth it now that I know I should have absolutely no problems getting a new (probably refurb) phone through TEP
scrawnyb said:
I'm *PRETTY SURE* that's just an updated version of the relocker SPL.
You should be able to flash back to a stock (non-GPS if I remember right) ROM from there.
I think what *MAY* have happened was the process got interrupted when you were unlocking?
so I *BELIEVE* your best bet is to return to stock, and unlock using SPL 2.40, then flashing on the new ROM/Radio
If I'm wrong, I'm sorry; It's early in the morning and I'm not quite awake enough to comprehend everything yet.
Click to expand...
Click to collapse
My phone is stock, i hadnt done anything to it yet. Im just unsure what to do because 2.06 was not shown at the step-by-step instructions.
so let me see if i understand what i need what to do....
flash the current rom, stock 2.06, with [OliPro MFG 2.40] (Hard SPL)
then run dcd_titan_3.2.5.exe and Titan_Radio_ROM_3.42.40.exe
then Sprint Cab??
Thanks for the replys