First off, I've been flashing my phone for almost a year now. So I don't consider myself too big of a noob. I loaded scrosler's round 4 rom. Worked great! Until I did a soft reset. It put the phone in bootloader mode and I can't boot up at all.
Here's what I have:
Olipro SPL 2.40
Radio 3.42.50
Here's what I've tried to get it out of bootloader:
mtty1.42.exe
titan_exitbl.exe
No success. I'm able to install a ROM, but as soon as it reboots after 100%, it goes right back into bootloader.
Someone please tell me it's not bricked
Try reflashing your radio.
BTC
kill the active sync processes via the task manager, then put the phone back into the usb cradle, run the titan exit bootloader and it should work.
josh77b said:
First off, I've been flashing my phone for almost a year now. So I don't consider myself too big of a noob. I loaded scrosler's round 4 rom. Worked great! Until I did a soft reset. It put the phone in bootloader mode and I can't boot up at all.
Here's what I have:
Olipro SPL 2.40
Radio 3.42.50
Here's what I've tried to get it out of bootloader:
mtty1.42.exe
titan_exitbl.exe
No success. I'm able to install a ROM, but as soon as it reboots after 100%, it goes right back into bootloader.
Someone please tell me it's not bricked
Click to expand...
Click to collapse
If no other suggestion works this will... But it sucks.... Flash a stock rom. I garuntee that will fix the problem. then just flash back. You don't have to flash a VZW ROM and I recommend against it. My new recommended ROM for unlocking and flashing is the Alltel ROM. Its got the latest radio in it (which you already have). Good luck and let us know how it turns out.
thanks for all the suggestions. i'm not sure what exactly went wrong, but i spent about a day and a half just to get it working again. it's somewhat stable now.
after flashing an older dcd rom, i was somehow able to get the OS to boot up, even after the auto soft reset. immediately i wanted to upgrade the bootloader to 2.47 since i've only found it in an exe(only can run from windows mobile) version. I then was able to flash the OEM MR1. Which automatically downgraded my radio. it was definitely the most stable thing i've flashed since the phone got all screwed up. i could soft reset as much as i wanted and didn't get the blue screen of death aka bootloader.
but of course, i couldn't be satisfied with no gps and no internet sharing. i use internet sharing more since i use it when i commute to work on BART (bay area's version of the subway) 50 min each way.
so now i'm on DCD's 3.2.6 ROM with 3.42.50 radio. so far it's somewhat stable. if i soft reset, i get the bootloader sometimes. but a couple solutions to the get the OS to boot back up is
1.) take the battery out for 20-30 seconds and power up
or
2.) take the battery out, plug in the computer usb or power usb with the battery still out. somehow resets the phone? i have no idea.
but i read somewhere that ROM's were causing people to have to take their battery out for 30 seconds to boot up. I doubt it was DCD's ROM's. But who knows, maybe i ran a bad radio file, ROM, or bootloader upgrade, that really caused the initial issues.
My only issue now other than getting the bootloader once in a while is that GPS isn't working. Not that big of a deal for now since I have the Pioneer AVIC F90BT in my car now. but would be nice to have it on my phone (tomtom & google maps) for that one time that might come up when i really need it and i'm not in my car.
again thanks for your help in trying to help a brotha out.
Verizon xv6800 bootloader and startup issues
My issues are, I cant get into the bootloader screen no matter what I try(power, camera and reset). Most times my phone will only go to the verizon screen and then just go white, other times, it may show the WM 6.5 startup screen and the freeze there. This all came from me trying to install WM 6,5 Beta 5 21159 rom from WM 6.1. On another not, my pc will not see my phone. So am I completely screwed? Is there any hope? Thanks in advance for any help.
So, overall, am I screwed?
Anybody have any suggestions?
Thanks
Can anyone help? my phone will not let me into bootloader mode or even startup past the verizon splash screen. I am desperately hoping that its not bricked. Also, the pc to phone usb connection will not see eachother.
My phone will charge via the usb cable to pc. When the wifi switch is turned on, the led on opposite side of the power led will do it green blinking.
Is there anyone that has time and is willing to work with me?
Thanks in advanced.
I have taken the phone apart so that I could push the internal buttons (power, camera and reset) to see if the outer shell buttons were the problem. They werent. I also still can't get past the verizon splash screen. Anyone have any ideas?
Thanks
I you cant get into bootloader you dont have any options.
Related
Hey, I just tried to install DCD's newest ROM and it looks as if i may of bricked my phone. When i connect it to my PC, Active Sync will not even pick it up. this happened right after i ran Hard-SPL-MFG to unlock the phone... I did try and run the titan_exitbl but no luck. I also attempted to run the relocker but i would not even run.. any ideas?
thanks!
recover from flash
Are you at the 3 color screen? If so you need to unplug the USB and replug it again as per the instructions. You MUST follow the instructions EXACTLY or your flashing will be very scary experience.
If you are not at the 3 color screen, you need to get back to the bootloader by pressing power+camera and soft reset. This will get you to the 3 color screen. Then have a look at the version of bootloader you have. If it doesnt say Olipro 1.20 or 2.40 you still have the locked bootloader and you can flash a stock carrier rom. If you have 2.40 you can flash to the 3.16+ rom and then flash the new radio this way or via sd card install which will be more painless and less scary.
If you dont know what an sd card flash is, I would search the forums here. Over at ppcgeeks you can look up imcokeman's posts and see instructions how to do a sd flash.
If you are are real noob, I would suggest staying with non gps roms at this stage because the change of radio rom needed to enable you to flash a gps rom will almost certainly lead to sleepless nights wondering if you have bricked your machine.
Most important thing to realise is that the machine is almost certainly not bricked. But you might have a few more scary moments before you get your machine back working again. You might also need to call your carriers service desk a number of times to get your provisioning data back working.
Check all the way through these two posts and dont sweat too much. With effort you will get your machine back. The answer to your problems is listed in one of these threads, but you need to dig a fair bit to find it. The posts contain lots of problems that people had flashing this rom, and I am sure your exact problem was there and solved. Its I believe somewhere in the second link I have listed here.
Good luck. i feel for you.
http://forum.xda-developers.com/showthread.php?t=371314
http://forum.xda-developers.com/showthread.php?t=362566 particularly this bit http://forum.xda-developers.com/showpost.php?p=1856032&postcount=216
thanks ill take a look, as a side note i am currently at the verizon logo, i can boot to the bootloader screen (red,green,blue) and when i connect the USB cord it does switch from Serial to USB on the screen... but gets stuck there. Active Sync shows no device connected.... I am running 2.40.Olipro
Thanks again
optyhtp said:
thanks ill take a look, as a side note i am currently at the verizon logo, i can boot to the bootloader screen (red,green,blue) and when i connect the USB cord it does switch from Serial to USB on the screen... but gets stuck there. Active Sync shows no device connected.... I am running 2.40.Olipro
Thanks again
Click to expand...
Click to collapse
It doesn't need to active sync. Once it switches to USB you are ready to flash.
Stuck at Verizon Screen/HTC Mobilty Screen
If you are stuck at the VZW screen then you have only flashed one of the two essential parts. You need both (ROM and RADIO) to make it work. 3.16+ ROM will not work with the old radio. You need 3.27 radio.
Use the camera+power+soft reset and you can flash the one (new radio or new ROM) that you are missing.
See dcd's thread about the 2.3.2 rom. He has added a HUGE new disclaimer.
http://forum.xda-developers.com/showpost.php?p=1952956&postcount=1
Well nothing really worked so i used a sd card to flash back to the stock verizon ROM, i then attempted it again and got it all working!!!
The Problem Is...
Every time i restart my phone via any type of reset....
(soft reset, hard reset, battery out of the phone, powerbutton turn off, a programs phone restart)
... the phone turns straight to the bootloader screen. It does not do the normal viberate and restart.
To get the phone to restart I have to go through a long process of removing the battery, plugging it into the charger, pressing all the buttons with a million resets.
Then eventually it will start up like normal.
Titan_exitbl.exe does not do anything... It sends the code and goes straight back to bootloader screen with any of the bootloaders stock or olipro customs
What I Have Tried:
installing and reinstalling the 3.39, 3.35, 1.30 stock radio
installing and reinstalling correct combinations of roms for the above radios. (including stock)
installing all bootloaders (including relocking)
each with their corresponding roms and radios
What I Think
Because of not being able to hard reset something is wrong there.
i'm open to suggestions
Where exactly are you right now?
What bootloader, ROM, and radio do you have installed? Are you able to boot into Windows Mobile?
right now completely stock i'm in windows mobile
i have now done a hard reset via settings->system-> clear storage
EDIT more exactly
verizon rom 2.09
radio 1.30.60
bootloader 1.06
Ok...do you have a microsd card to flash with?
not right now however,
let me know what you're thinking i might go grab one.!
I've got the same thing happening to me... I was running the test "sprint" radio on my alltel 6800 along with no2chem's latest rom... it started happening, so I decided to install the newest stock alltel rom... didn't fix it at all. What sucks now is I can't even get activesync working witht eh alltel rom now...
Also, I can get it to boot if I do one thing. If I connect up a usb cord (to a computer, or my usb headphone adapter) and hit soft reset, it'll boot fine.
However, soon as I hit that soft reset button on the bottom again, back to bootloader it goes.
This happened to me once before a long time ago, I fixed it by relocking the device and installing a stock Alltel rom... however I've read that's a bad idea with the newer GPS enabled roms and can kill the phone.
any ideas?
Just a quick update... after messing around I had an idea... I connected the USB headphones so I could actually do a soft reset that works... But this time, instead I held down the power/cam when I did it so it would load the boot loader... my thinking was that it might trick it into not loading it. Sure enough, it worked. Now when I hit soft reset, it does just that. No more boot loader unless I hold down those buttons.
Very strange... like the phone got tricked into thinking the buttons were always pressed down on restart.
Anyways, hopefully this will help others that might come across this issue.
spoke too soon... now its is doing it again after flashing the sprint rom back on and then no2chem's latest.
argh...
My phone was working fine for sometime with DCD 3.1.2, SPL 2.40 and radio 3.39.10. Last week it starting randomly resetting when I would slide open the keyboard. Not always, but quite annoying. The past few days it started getting stuck in the bootloader on initial start. I would reset it, remove the battery, etc. Still it would go to the bootloader. I even tried the exitbl utility and although it sends the data and executes the reset, it still goes back to the bootloader. Screen says:
TITA100 MFG
SPL-2.40.Olipro
CPLD-9
I figured it was a bug with the rom or whatnot, so I (microsd) reflashed it with the latest official Sprint rom. It still goes into the bootloader. If I hit the reset button enough times, it will occasionally boot up. No idea what's goin on here. Don't understand how it could be random either.
Any ideas?
do you have the wire that you plug in for headphones?
it's the headphone/ USB plug?
if so plug it in and just push the soft reset button
it should work
Ok, that worked like a charm, thanks!
Question is it still enters the bootloader when I reset or turn off/on the phone without the adapter. Should I reflash the bootloader?
i have found no info pointing towards what is doing it. i've re-flashed with no luck
Is there a way to flash the bootloader off just the memory card? Can I copy the Hard_MFG_SPL_2.40_RUU_signed.nbh file to a card and rename it?
Figure it's worth a try.
I've got the exact same situation as you guys... Just wanted to chime in on it.
cpujunky said:
Is there a way to flash the bootloader off just the memory card? Can I copy the Hard_MFG_SPL_2.40_RUU_signed.nbh file to a card and rename it?
Figure it's worth a try.
Click to expand...
Click to collapse
i think i read on another forum that you can not flash off the memory card for a bootloader.. but i do not know
Try a hard-reset and then flash to another pre-built or Kitchen built ROM that uses the 2.40 bootloader.
You must boot into the WinMo OS and get connected with Activesynch to program a bootloader. At least none of us have yet managed to figure another way to do it.
Is there a way to flash the bootloader off just the memory card? Can I copy the Hard_MFG_SPL_2.40_RUU_signed.nbh file to a card and rename it?
Figure it's worth a try.
Click to expand...
Click to collapse
Do NOT, I repeat do NOT attempt to update the SPL with the memory card. The unlockers are developed to first load a temporary bootloader, then flash with an RUU once using the temporary. You will mess up your phone.
Thanks... I was having the same problem that the OP was having until I found this thread. It seems like headphone adapters other than the Sprint one works. Also, if you're stuck in the bootloader, there is no reason to flash any roms because it will have no effect at all.
Also, as an alternative, you can take out the battery for a couple hours.
By the way, I'm running dcd 3.1.2 and radio 3.37
So we know that flashing a new ROM doesn't work, and flashing different radios doesn't work. We also know the headphone adapter will get you to boot up normally, so no stuck buttons or anything. This has to be a bootloader bug or phone defect or bent usb pins or something. Has anyone tried relocking the phone? I can't express how annoying it is to carry around a headphone adapter in case you need to reboot.
Thinking,,,,,
I stopped where you see in my signature as everything works for me, but I wonder if maybe you flash back to stock, relock, put it back exactly as you started if that would straighten it out. If it still fails stock then some nice new defect has been found. If it works then go forward but only as far as I did ans see if it is stable as with mine,,,,,maybe somthing in the new ROMs???????
cpujunky said:
So we know that flashing a new ROM doesn't work, and flashing different radios doesn't work. We also know the headphone adapter will get you to boot up normally, so no stuck buttons or anything. This has to be a bootloader bug or phone defect or bent usb pins or something. Has anyone tried relocking the phone? I can't express how annoying it is to carry around a headphone adapter in case you need to reboot.
Click to expand...
Click to collapse
i have relocked also. i've think i've done everything except rip the phone apart and look at the usb pins
This is not a rom issue, it's a bootloader issue. I've flashed, tested, and used all released roms and non-released (internally tested) roms numerous times on several different titans and have never seen this issue. I'm not doubting the existence of the issue, but the rom will have nothing to do with the device being stuck in the bootloader.
My guess is that something went wrong while unlocking or it's a hardware defect on a certain batch of these phones.
there was some talk over at ppcgeeks about there being something about relocking and flashing and something... however. my phone worked great and then one day it just started and nothing changed on the phone for like 3-4 weeks and then it started going to bootloader
This weekend I replaced the stock bootloader on my VZW XV6800 with SPL-2.40.Olipro; upgraded radio to 3.39.10; installed dcd's Titan 3.1.2. All went well, phone was doing fine for a couple days.
Today the battery died, nothing unusual. I plugged in AC power and turned on the phone and the bootloader displayed. Did a soft reset 2 or 3 times, no change. Disconnected AC, popped out the battery, let it sit while I search and found this thread.
I used a can o' air to blast out the USB/power port on the phone. Put in the battery, powered the phone, and the OS loaded just fine. Soft reset the phone and again could only get to the bootloader. Poppped out the battery again, found my USB/headphone adapter, connected it, returned the battery and powered the phone, and the OS loaded just fine.
This is a long way of saying I'm experiencing the same that's been reported in this thread. Is there a fix for this issue? It seems like an issue with the device to me. Was there any confirmation that there was a "bad batch" of phones and is a hardware issue with the XV6800?
I am also experiencing this same problem.
I flashed to 3.1.2, then to 3.2.0 today...nothing changed. It still loads the bootloader when i do any kind of a reset without the usb or the headphones plugged in.
The only odd thing that i can comment on during my experience is that my USB cable failed on me and I had to replace it. Seems odd, but perhaps that can shed some light on the problem.
Did anyone find a solution to this problem? Is it a hardware issue?
So after having my Mogul for quite sometime, I figured it was time to upgrade the ROM which includes the GPS, etc etc. I followed all the instructions to the "t" and when I go to update it, the phone goes to the tri-color and says "USB" at the bottom...but on my computer, it stays stuck at 0%.
I've left it go for almost 30 minutes. I end up having to shut down the update and reboot my phone. Luckily my phone wasn't affected at all. (whew!) I've tried this three times and all end up being stuck.
I'm new to all this, so ANY help would be greatly appreciated. I've searched for this same occurrence but have not read about any resolutions to the problem.
Thanks for any help!
Anyone have any suggestions?
Right now I have ROM version: 2.09651.3
I have downloaded a ROM for the Quest 'version' of the Mogul which is 3.35.656.2....will this work?
I dont get why it wont update and install the ROM.
Any help is greatly appreciated!
what version of bootloader are you using?
if its not giving you an error try letting it go overnight. Maybe its just going REAL slow.
Other than that, try one of the intermediate ROMs first, or try re-downloading the ROM and going from that.
The process is pretty simple, sync, backup anything important, establish activesync/MWDC connection, run the RUU, press yes several times, restore backup/resync.
Did you ever unlock the phone? The sprint ROMs wont load with an unlocked phone, AFAIK.
not sure what you mean by version of bootloader....
As far as running reall slow, not sure, I might try that if nothing else works.
I'm going to try the 3.35 ROM and see if that works. So stupid that it is such an easy task, yet it doesnt work....and I never "unlocked" the phone...its basically factory straight from Sprint. Again, it was bought back in December 2007 so the ROM on it is pretty 'dated'
I'll let ya know what happens...
2.09... lol.
that rom was slooow. screen flickered.
lockups.
your problem is that you cannot use a rom from a different carrier unless you unlock first. Just get the latest sprint rom and flash it.
edit: perhaps i read your post wrong. do you have the sprint or qwest rom? the qwest rom will not work. the sprint rom should work fine providing the phone has not been unlocked with olipro 1.2. Check the bootloader version when in the tri color screen. if it says olipro 1.2 then you need to update to 2.4.
If it's stock then you should be good. you could try putting the phone into bootloader before running the ruu. sometimes this helps the connection since it doesn't mess with activsync. to get to bootloader hold power + camera and hit the reset button.
Hi guys,
I successfully flashed Android to my HD2 a few months back. I used what I believe is Cotulla's rom(?). However the other day my phone sorta died and whenever I plugged it into the charger it would vibrate go through the boot screen and reset at the "1234 go go go" stage. I read some reading on the forum and flashed it back to "RUU_Leo_S_HTC_WWE_3.14.405.2_Radio_15.42.50.11U_2.15.50.14_LEO_S_Ship" from the HTC website, using the SD card. Windows mobile restored the phone and I started using it again.
I tried to put android back on it and I think I unsuccessfully tried to update the radio after which the phone sorta died again. So I thought ok, no problem, lets get back to windows again. So I installed the HTC rom again through the SD card, which the screen told me was successful. But now I can't get the phone to boot or go into bootloader or anything. When I plug the charger in, I get a vibrate and HTC bootscreen, with the red writing at the bottom left and then dead to only do this again and again. If i pull out the charger, the phone just dies. Battery charge was about 50% when it died.
Any ideas or help on how to resurrect my beloved HD2 would be greatly appreciated!
*quick update*
I stuck the phone in the fridge for a while and managed to get it into the bootloader just once and flashed the official winmo rom again, which was successful but still dead phone!
What made you decide to stick the phone in the fridge??
What is your SPL version??
mentalityx said:
What made you decide to stick the phone in the fridge??
Click to expand...
Click to collapse
Probably the dozens of threads that talk about successfully flashing only when the phone has been cooled.
@op it doesn't look good. Usually the fridge trick working implies hardware overheating issues.
Just confirm please, its not a tmous right?
Samsamuel is right, i just read about it and thought hey, why not! plus it got a priceless look from the mrs! lol
It's definitely not TMOUS, its UK Virgin and the SPL was 3.03.0000 if I recall correctly.
When I cool it, I can get it into bootloader, but only once.
well, i still suspect its hardware and unfixable, but there have been cases where for whatever reason a rom suddenly seems to fix it. Try all the versions of the correct stock Rom.
Try the 1.43 the 1,66 and again the 3.14, wwe ones, chilling the phone well before each flash, a good 20 mins.