Related
Hello all
i need some help. just finished upgrading my mogul and it keeps on rebooting after a few seconds after it reaches the today screen. i have tried dcd 2.2.4 and 2.2.6 with same results.
i believe if i keep it plugged into the computer it will stay on. any help please!??!
thanks
I just had the exact same problem. Did you load any other software after flashing the radio and rom?
Unfortunately i couldnt find a solution that involved DCD's roms. I flashed to 2.4 2.6, 1.6 new radios but nothing worked. I had to use no2chems nuerom 2.0 buld 5044 which works great, but doesnt have the verizon specifics. GPS is good and its fast. If anyone else comes up with something please let us know as i would like to have some of that software back.
this has been posted many times.
most likely you do not have the new bootloader installed.
http://forum.ppcgeeks.com/showthread.php?t=9093
go here get the 2.40 bootloader and start over
thanks for the quick responses!!
first time doing all this, but nothing to hard i think in my opinion. you just have to get over the learning curve.
i used this guide: http://forum.ppcgeeks.com/showthread.php?t=17667
which bootloader should i use if that guide led me to the wrong one?
also where can i find the other rom?
thanks for the bootloader. i will give it a shot now
2. If you are using 3.16+ code then you need either:
>>>a. The reLocker if upgrading to the unofficial carrier released rom
>>>b. the unLocker (new) 2.40 if running custom built roms
you'll learn the terms eventually....
just an FYI
do a search on here and on google FIRST if you run into problems because most likely you'll not be the first to have the issue.
but if you can't find any answers most people here will be willing to help
just verified, i am already using 2.40
also im not new to forums... i am well aware of google and search tools. these forum websites are getting annoying with spam protection that half the time when i tried doing a search, it would not complete it.
i knew i was running a stock 3.16
did you have an old custom bootloader? you need to relock it if so then run the 2.40
if its like mine then when you relock it you will lock up on the bootloader and have to do exit bootloader to get back to the splash screen where it will lock again. I even flashed back to the stock rom and it relaoded. I think it may be an glitch in the s.27 radio personally.
i went from the latest stock to custom using the guide above. is there a need to relock it or do you leave it unlocked?
if you go from stock to custom bootloader and upgrading the radio 3.27 and a DCD rom you don't need to relock it.
you only need to relock for the leaked sprint rom
did you upgrade the radio too?
yes i used titan_radio_3.27.00
when i go into boot mood i get this:
TITA100
SPL-1.20.0lipra
Click to expand...
Click to collapse
is this how it should be?
please and thank you everyone for your help!!!
that should say olipro 2.40
who is your carrier? sprint, verizon.......
my carrier is sprint
http://forum.ppcgeeks.com/showthread.php?t=9093
run the 2.40 spl and start over
okay so you want me to run the hard spl again and then dcd??? or should i do the titan radio 3.27.00 before dcd
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 installed the wrong rom on the wrong hard spl. i had the hard spl a 1.30 installed and dcd 3.2.0. now the screen is stuck at the loading screen that says htc smart mobility. and no radio at the bottom. please help and the phone wont sync.
Good luck on that.. You installed a bootloader for a different model -- likely the TyTn or Trinity. What phone do you have? What instructions did you follow?
If you do have a Titan, then possibly via the SD Card you can change the bootloader to the new 2.47 (I haven't played with it yet but another may provide a solution). You are likely out of luck in flashing to any of the other Titan bootloaders as you must be able to boot into the OS, but with you error of installing an inappropriate bootloader you are out of luck there.
no it was a bootloader 1.30 for the titan
Your information is incoherent.
What rom/bootloader did you have prior to updating?
What rom/bootloader did you try to upgrade to?
You need a minimum SPL of 2.40 to install DCD 3.2.0
I use 2.47 from no2chem and it works great. http://forum.ppcgeeks.com/showthread.php?t=30561
Are you able to boot up the device? If so copy the SPL 2.47 to the card then to the PDA and run it from there.
If not, put the PDA into Bootloader mode and try to install Olipro 2.40
http://www.lifesnotsogood.com/dcd1182/titan/spl/titan_SPL_2.40-olipro.exe
Failing that you can try to flash back to an official ROM if you have one.
You need to soft reset your phone while holding the Camera and power buttons. This will force your phone in to the bootloader. You should then be able to reflash to lower ROM. Then you need to search for Olipro or whatever the 2.40 bootloader is. Your best bet after that is to flash the official Sprint 3.35 Radio and Rom then flash to DCD's.
**Edited**
Sorry Hamilton didn't realize you gave a link to the 2.40 bootloader.
If he is sure that it is "bootloader 1.30 for the titan" then I know of NO such bootloader. He has likely installed the wrong bootloader (for another device) and therefore no amount of flashing to an OS ROM will help him boot into the OS. Unless via an SD card for 2.47, beastmode216 is stuck with a borked device.
So, beastmode216, I'll ask again, where did you get such instructions and where did you source your bootloader 1.30?
What is one of the earlier bootloaders? I was thinking my Mogul orginally had something like 1.30 or 1.40.
thanks guys but the problem is solved. just make the phone go in to the bootloader
Verizon stock bootloader is 1.30 if I remember correctly. It has been several months since I have seen a stock bootloader
calash said:
Verizon stock bootloader is 1.30 if I remember correctly. It has been several months since I have seen a stock bootloader
Click to expand...
Click to collapse
My mistake, as pointed out by gc14 the stock bootloader is 1.04.
Ahh, ok, my fault as I thought that he had also installed a bootloader under the name of 1.30.. That could've been an unlocker for a TyTn or another device.
Correct, OEM bootloader should be 1.30.60.
Click to expand...
Click to collapse
This is incorrect. The stock bootloader is 1.04. The stock radio is 1.30.60.
SPL 1.30 does NOT exist for the Titan.
Stickies exist for a reason...to read them as they contain valid, useful information. http://forum.xda-developers.com/showthread.php?t=392133
Hi I'm looking for some help. I tried upgrading my XV6800 to the windows 6.5 rom but I think I might of messed up. I tried to update my radio first but ran in to issues.
I used Oilpro 1.20 to try and tried to update the radio but along the way messed up while trying an older rom and I'm currently at a Verizon screen with the message "NO RADIO" at the bottom. I'm assuming the radio rom was erased. I might have gotten confused with the roms and used a rom without the appopriate Radio. When I try to flash that rom back to a stock Verizon upgrade it just ends 11% in to the flashing process and the rom update utility returns a Error 290 screen.
Currently I can get the oilpro 1.20 bootloader to still load up but I'm not sure what to do at this point. I tried updating the ROM to DCD's older 3.20 roms, which did complete but I still have that screen coming up. Can anyone give me some suggestions on what I should do next? Any help would be greatly appreciated.
Try using NueSPL 2.47 it's more current
Doesn't have have to be run on the phone itself once inside Windows? The only screen I can get up is the Verizon (splash) screen where it normally lists the rom and radio, or the oilpro boot loader screen. I actually can't get back in to windows to run the nueSPL 2.40.exe file.
Is there a way for me to flash the radio back from a bootloader screen and USB or SD card? The thing is I actually tried to take the 3.42.40 radio and use the Flash Rom Utility to see if it would flash the radio rom back on but even though the process completes successfully, I still get the no radio error so I guess it doesn't work. Thanks for the help, I think I may have been a few of the idiots out there who screwed things up and didn't make sure the radio was up before attempting any rom upgrade.
You should've changed the bootloader first. Your radios that you are trying are not compatible with your bootloader.
Flash an old stock rom via SD, then update your bootloader to 2.47 once you can get back into windows, then update your radio, and then your rom.
Yeah that was one of the first things I've tried a USB update back to the stock Verizon 6.1 ROM, but for some reason it prematurely ends at 11% with the PDA Phone Update Utility throwing a ERROR 290 message. This is the first time this has happened as I've flashed with this same rom tons of times. I've been looking online for the past hour on how to flash the ROM from a SD card if I can't get in to Windows. But all I could find was the USB update utility and it ends at 11% Am I doing it wrong? any ideas would be greatly appreciated.
If you can still get in the bootloader then you should be fine....I would put it manually in bootloader holding power and camera simultaneously and poke the hole to get it into bootloader.
Once you do that plug in the data cable and run Olipro 2.40 or Nue 2.47. It should be able to take after that.
Basics steps to flashing a phone:
correct unlocker-->stock ROM-->custom ROM
Most custom ROMs will not include Radios that why you would run the stock ROM first to install the radio and then run the custom ROM. Alot simpler then trying to update the Radio by itself.
AWESOME! I got it back up, thanks guys. For reference purposes I'm going to restate the problem and solution incase other noobs run in to the same issue.
PROBLEM:
I installed oilpro 1.2 during the process of installing a new radio then a rom. Along the way the rom install failed. I tried to reinstall a stock Verizon rom RUU 3.57 & 3.37 radio but it failed at 11%. I was then stuck at the splash screen with a message that said NO RADIO. I could still get in to the boot loader with the power and camera button. But the stock Verizon rom did not install anymore.
SOLUTION:
I used titan_exitbl.exe to exit the bootloader and I went back to an earlier rom found here, rom 2.09 & radio 1.30. That one actually installed. It seems to have worked. I'm back in windows now but I need to uninstall oil pro 1.2 and get nuSPL 2.47 on there before I move further (it looks like while it's still on the stock RUU won't work for me).
Do you guys know how I would go about uninstalling Oilpro 1.2? Will Titan_relocker do it for me? I'm not sure if installing nueSPL over oilpro will do it.
Use this ROm from Verizon to get the Stock 6.1 back up and running. It's the MR2 rom
http://www.pcdphones.com/phone_downloads.aspx?bid=89&cid=1&mid=287&carrier=Verizon Wireless
Beyond888 said:
AWESOME! I got it back up, thanks guys. For reference purposes I'm going to restate the problem and solution incase other noobs run in to the same issue.
PROBLEM:
I installed oilpro 1.2 during the process of installing a new radio then a rom. Along the way the rom install failed. I tried to reinstall a stock Verizon rom RUU 3.57 & 3.37 radio but it failed at 11%. I was then stuck at the splash screen with a message that said NO RADIO. I could still get in to the boot loader with the power and camera button. But the stock Verizon rom did not install anymore.
SOLUTION:
I used titan_exitbl.exe to exit the bootloader and I went back to an earlier rom found here, rom 2.09 & radio 1.30. That one actually installed. It seems to have worked. I'm back in windows now but I need to uninstall oil pro 1.2 and get nuSPL 2.47 on there before I move further (it looks like while it's still on the stock RUU won't work for me).
Do you guys know how I would go about uninstalling Oilpro 1.2? Will Titan_relocker do it for me? I'm not sure if installing nueSPL over oilpro will do it.
Use this ROm from Verizon to get the Stock 6.1 back up and running. It's the MR2 rom
http://www.pcdphones.com/phone_downloads.aspx?bid=89&cid=1&mid=287&carrier=Verizon Wireless
Click to expand...
Click to collapse
Glad to hear you got your phone back up
As far as I know you should be able to just install 2.47 and it will overwrite your old bootloader without problems. I could be mistaken but there isn't really a way to "uninstall" a bootloader, just overwrite it with a different one.
unL33T is correct...just run Nue 2.47 and let it overwrite the old one. 8p
Yeah that's what I thought too, but when I tried to over right it with 2.47 the 1.20 showed up again so I used the titan_relocker tool. Maybe I did something wrong. I'll go recheck, thanks for the replies guys.
Hey so here's my situation:
Installed the CM Nightly on my AT&T One M9, didn't like it, so I tried to revert to stock. I didn't want to pay $25 to S-OFF so I just tried installing various RUUs, but none would work. I read somewhere that I needed to relock my bootloader in order for the RUUs to work, so I did that, and now my phone just boots to Recovery Mode. I've tried installing AT&T RUU 2.6.502.16 (which didn't work because my phone is on a more recent firmware) and reinstalling 2.11.502.18/flashing its 0PJAIMG.zip (which didn't work because it's apparently broken). I've even tried installing T-Mobile's 2.11.531.19 RUU, which of course didn't work because my CID doesn't match and I can't change it because I'm S-ON.
I realize I went about this very badly almost from the start--no stock backup in TWRP, etc. This is my first Android phone so I've been learning this as I go and I was a bit sloppy.
I'm pretty sure I'm screwed, at least until a new update comes out or the current AT&T RUU is fixed, but I'm wondering if there's something else I can try. Any ideas? Thanks.
StageProps said:
Hey so here's my situation:
Installed the CM Nightly on my AT&T One M9, didn't like it, so I tried to revert to stock. I didn't want to pay $25 to S-OFF so I just tried installing various RUUs, but none would work. I read somewhere that I needed to relock my bootloader in order for the RUUs to work, so I did that, and now my phone just boots to Recovery Mode. I've tried installing AT&T RUU 2.6.502.16 (which didn't work because my phone is on a more recent firmware) and reinstalling 2.11.502.18/flashing its 0PJAIMG.zip (which didn't work because it's apparently broken). I've even tried installing T-Mobile's 2.11.531.19 RUU, which of course didn't work because my CID doesn't match and I can't change it because I'm S-ON.
I realize I went about this very badly almost from the start--no stock backup in TWRP, etc. This is my first Android phone so I've been learning this as I go and I was a bit sloppy.
I'm pretty sure I'm screwed, at least until a new update comes out or the current AT&T RUU is fixed, but I'm wondering if there's something else I can try. Any ideas? Thanks.
Click to expand...
Click to collapse
I do not have this phone... but...
I would go thru the bootloader unlock process again... reflash twrp...
And then probably flash the viper ROM... since it's modified stock