Related
hi,
i've searched, and am stuck. i tried to flash a new ROM today, but it stopped at 76% and said no connection!?? i've flashed before with no problems many ROMs. I have HardSPL 1.15 mfg installed and everything always worked. Now i'm stuck at 4 color boot screen screen. HardSPL is still there, there is a message at top right saying 'RUUNBH'. I plug USB in and it says 'USB'. I run mtty but can't seem to get any CMD, or even type 'boot' in, no response on app, running on XP?
i'm reeally stuck, and had to come to work, so am worried. can anyone help??
sorry, i am still searching for solution, but please any help appreciated!!
thank you
i will try to check back often, but stuck at work might be problem ..
i got stuck at that boot screen too, but it happened during a boot image change operation. All I had to do was install a new rom.
Hope it helps...
how did you install a new rom? cos i cant activesync, and running CustomRUU.exe says it cant find pda device
am i bricked? really stuck here :'(
badaas said:
how did you install a new rom? cos i cant activesync, and running CustomRUU.exe says it cant find pda device
am i bricked? really stuck here :'(
Click to expand...
Click to collapse
Don't worry, you just need to get to the bootloader screen and flash again, you may have a corrupted update that may hault everytime. If it doen't work try another ROM.
Hold down power and the camera button while pressing and holding the reset button.
When you see the Boot Loader screen you can release all three.
Plug in your cable if it is not already, wait to make sure the computer installs the device and then run the ROM Update executable you want or ROMUpdateUtility.exe if everything is placed in a folder.
Note: Activesync and Mobile Device Center will not launch in this mode, and if the utility tells you to connect through activesync or Mobile Device Center ignore and continue.
OK thank you my friends, i will try when i get home from work. fingers crossed!!
cheers
thx guys, all sorted
hi guys, I have a mogul for sprint but it is stuck at the bootloader. The message I see is: TITA100,SPL-2.07.0000,CPLD-9 and it says serial at the bottom. I have updated the rom via sd card and it completed succesfully but when I reboot I am back at the same screen. When I plug it into a computer it says the usb device as malfunctioned. I have tried the exitloader but with no usb connectivity its not working. So I have no connectivity that way. Can anyone help?? Thanks
by the way
By the way I should tell you It started after I was in windows and it froze up. I soft reset the device and have been in this screen ever since.
you did not update your bootloader correctly, as your are still in 2.07. that is the temporary BL in which no2chem's program uses to flash the 2.47 bootloader. if youre stuck, use exit bootloader, and run the thing again. make sure you go through the whole process.
Confused
I don't understand how I can do this. I cant access the device with usb so I cannot run exit bootloader on the computer and I cannot install nuespl update because I cant usb connect to the device and cannot get into the windows os on the device.
I don't understand how I can do this. I cant access the device with usb so I cannot run exit bootloader on the computer and I cannot install nuespl update because I cant usb connect to the device and cannot get into the windows os on the device.
Click to expand...
Click to collapse
You didn't update your bootloader before you flashed, that's what's causing your problems.
While in the bootloader, if you plug it in via USB, it should change to USB at the bottom. Flash the Official 3.56 Sprint Rom to be able to boot into Windows Mobile again. Then connect to Activesync and update your bootloader first BEFORE you flash any custom roms/radios.
hmm
ok i tried that but the ruu program gives me error 260 cannot connect to usb. Which doesn't surprise me becuase the second I plug the usb cable it windows says the device is not recognized. What am i missing?
Into windows
Ok I got into windows mobile by plugging the phone into the power outlet and soft reseting the phone. Then I can unplug it and Its fine and in windows but if i reset it without it being plugged into the wall its stuck at the boot loader again. Any ideas whats going on with this thing
missinglink2 said:
Ok I got into windows mobile by plugging the phone into the power outlet and soft reseting the phone. Then I can unplug it and Its fine and in windows but if i reset it without it being plugged into the wall its stuck at the boot loader again. Any ideas whats going on with this thing
Click to expand...
Click to collapse
I would start from scratch again like GC said. Get into Activesync... and do the Bootloader flash... then reflash the Radio/Rom.
advise
missinglink2 said:
hi guys, I have a mogul for sprint but it is stuck at the bootloader. The message I see is: TITA100,SPL-2.07.0000,CPLD-9 and it says serial at the bottom. I have updated the rom via sd card and it completed succesfully but when I reboot I am back at the same screen. When I plug it into a computer it says the usb device as malfunctioned. I have tried the exitloader but with no usb connectivity its not working. So I have no connectivity that way. Can anyone help?? Thanks
Click to expand...
Click to collapse
hit the 2 buttons with the dot on them,at the same time press the rest button at the bottom were the usb plugs in.make sure you have the right activesync for your OS.xp uses 4.5 and vista uses mobile center.also make sure when your flashing your ppc that you disable the stand by power mode,uncheck all option that would put your ppc in standby will your flashing it.
Stuck in tri-colour screen
I GOT MI HTC TITAN STUCK IN BOOTLOADER MODE FOR BOUT A MONTH NOW AND NOTING SEEM TO BE WORKIN
ON THE SCREEN I SEE A MESSAGE DAT SAY
TITA100
SPL-1.07.0000
CPLD-9
NEED U HELP PLZ AND THANKS IN ADVANCE
buzzinstudios said:
I GOT MI HTC TITAN STUCK IN BOOTLOADER MODE FOR BOUT A MONTH NOW AND NOTING SEEM TO BE WORKIN
ON THE SCREEN I SEE A MESSAGE DAT SAY
TITA100
SPL-1.07.0000
CPLD-9
NEED U HELP PLZ AND THANKS IN ADVANCE
Click to expand...
Click to collapse
Please stop typing in all caps.
Then describe what you did that resulted in this. Did you try to flash a custom ROM? If so, it probably failed because you didn't update your bootloader.
i'm having the same problem... tri-color bars:
TITA100
SPL-2.07.0000
CPLD-9
Serial (USB when i plug in the usb cable)
PC would not recognize the device so i can not run the exit boot loader that seems to solve the problem for a lot of ppl here.
The scenario with my device: i was not trying to update anything. the phone dropped onto the floor and the battery came loose. when i put the battery back in, it was stuck in the bootloader.
any help would be greatly appreciated.
eskargo said:
i'm having the same problem... tri-color bars:
TITA100
SPL-2.07.0000
CPLD-9
Serial (USB when i plug in the usb cable)
PC would not recognize the device so i can not run the exit boot loader that seems to solve the problem for a lot of ppl here.
The scenario with my device: i was not trying to update anything. the phone dropped onto the floor and the battery came loose. when i put the battery back in, it was stuck in the bootloader.
any help would be greatly appreciated.
Click to expand...
Click to collapse
I just had a similar problem though my phone didn't even drop, it went into bootloader while I was listening to a podcast via bluetooth. You could try to re flash via sd card(see the wiki), but if you're unable to connect with the pc, your phone is likely bricked. I tried the sd route and though I was able to get the update to complete, it always went back to the bootloader. The phone was swapped out (my 4th!) yesterday, unfortunately they had Moguls so no TP for me! Good luck!
i did get the mogul to reflash via the sd card but it would return to the bootload screen. so i left the battery out. i tried the next morning and the phone proceeded to boot up. it recognized that there is a new image and started to run thru the setup and installed all the files. when the setup completed, guess what, it required a reset. and back came the bootload screen. seems that, 99.9% of the time, after a reset (soft or hard), my phone would return to the bootload screen.
after countless tries, i finally managed to boot up my phone with my personal info restored. but if i need to reset or battery drains and a restart is needed, the bootload screen would return. and the only course of action is to remove the battery and keeping trying until the phone boots up properly.
obviously, i can not live with a phone this way... so i will be sending the brick back to UT starcom for a replacement.
in the mean time, i guess i will get one of those pay as you go sim card for a spare nokia i have laying around the house.
thank you for all the info and tips here... i think i know more about the mogul than some of the sprint employees at my local sprint store.
If your PC is not recognizing the phone when its in bootloader is probably because you don't have the correct drivers installed for your phone. Might wanna google the drivers and install it and then try going through the advice from the other members.
Meaning put into bootloader manually then install correct unlocker (Olipro 2.40 or Nue 2.47)-->run stock ROM (to install radio)-->install custom ROM
I'm not sure if this helps but I just ran in to a similar issue of getting stuck in the boot loader. What I did was use to flash back to the earliest stock from Verizon (for me it was 2.09 and radio 1.30) but I was still stuck in the bootloader screen. I then used titan_exitbl.exe (found here at XDA) and exit the boatloader. Afterwards I did the rom flash one more time and it worked. I was back in to a stock rom. The issue I'm having now is that if I try to upgrade to the next stock rom the process fails at 11% again, and since I never had this issue before with this rom (3.57) prior to oilpro 1.20, I suspect that is the problem. I have to uninstall oilpro 1.20, then try the 3.57 stock rom again or install nuespl 2.47 or something. You guys have any clue how to uninstall oilpro 1.2? Will titan_relocker do it for me?
Here is my thread, and thanks for all the guys who helped me on this one.
http://forum.xda-developers.com/showthread.php?p=3402819#post3402819
UPDATE:
Use this link if you are on Verizon to get the MR2 rom update back up and running on your phone.
http://www.pcdphones.com/phone_downloads.aspx?bid=89&cid=1&mid=287&carrier=Verizon Wireless
The whole
TITA100
SPL-2.07.0000
CPLD-9
keeps happening w/ my Sprint HTC Mogul a little more often now (it's about 1.5 years old). But it just goes away after a while, I really don't do anything.
On Monday I was shutting my Mogul down after fully charging the battery by holding the power button until the reboot prompt came up on the screen, I pressed yes and it shut down like it always has. I removed the battery and swapped to my other battery to charge it and when I tried to boot it up by pressing the power button again I just got the bootloader screen. I tried everything, with power plugged in an not, tried either battery, nothing, just stuck on the bootloader, I even tried the factory reset as a last resort thinking I wouldn't lose much, I sync pretty frequently. Even the factory reset holding the 2 soft keys while pressing the reset button it went blank then back to bootloader again. I am running everything stock from Sprint, no modifications or other software (WM 6.1 from HTC). I scoured the web and found on a ppcgeeks thread that someone had tried plugging the Y-adapter cable with the 2.5mm headset and mini-usb connectors on it and I happened to have it sitting around and plugged it in and pressed the reset button with the stylus again and it booted right up just fine. It also seems to boot fine with any of the other adapters I have (nothing needs to be connected to the adapters, just the adapter needs to be inserted into the phone in order for it to boot properly). I took it to Sprint and they had the techs look at it and had never heard of it before. They offered to reflash the rom but said that there is an equal chance that it could either fix it or brick it and they wanted me to sign a waiver that would release them of any liability if it bricked. I told them I can flash the rom myself with activesync at home, if they're not going to take any liability I'd be just as well off doing it myself.
I also found that sometimes when placing a call I can't hear anything, and when I have my Seidio 3.5mm audio adapter plugged in the audio will not pass through the adapter unless the phone is rebooted with the adapter plugged in all the time, as soon as I unplug the adapter it goes to the phone speaker for audio (music from windows media player) and it will not return the sound to the adapter when it is plugged back in until it's rebooted again.
Any ideas?
buzzinstudios said:
I GOT MI HTC TITAN STUCK IN BOOTLOADER MODE FOR BOUT A MONTH NOW AND NOTING SEEM TO BE WORKIN
ON THE SCREEN I SEE A MESSAGE DAT SAY
TITA100
SPL-1.07.0000
CPLD-9
NEED U HELP PLZ AND THANKS IN ADVANCE
Click to expand...
Click to collapse
same thing happened to me sept it says
TITA100
SPL-1.06.0000
CPLD-9
cant fix it
wmobilefrik said:
same thing happened to me sept it says
TITA100
SPL-1.06.0000
CPLD-9
cant fix it
Click to expand...
Click to collapse
There are some solutions 1 page behind http://forum.xda-developers.com/showpost.php?p=2516968&postcount=5.
Hi,
This is my first rom flashing, and when it came to 96% it stopped, and I got communication error.
After trying several times more the same.
When I start the phone now I only gets to the tricolor picture where it says "upgrade ROM code error please try again"
When I run the Custom RUU again I get the the following error
ERROR (240): FILE OPEN
The upgrade utility can not open the requested file, please check your update utility.
Any good suggesions how to proceede?
btw my phone is an O2 XDA Guide.
try to use bootloader -
1. turn it off. (disconnect from pc, remove battery)
2. insert battery
3. hold volume down and press power
4. you will see tricolor screen
upload new ROM.
As serfer222 suggested, go to bootloader or in other words do a hard reset.
Try this link as FYI.
http://wiki.xda-developers.com/index.php?pagename=IoliteHardReset
bootloader is not a hard reset.
hard reset returns your last flashed ROM to default state, just if you just flashed your device.
bootloader doesn't change anything but allow you to load new ROM even if your previous ROM flashing failed
that's why I suggest to use bootloader.
Hi all,
I have searched all over and can't figure out what is my problem. Any help would be greatly appreciated. I have TMO US H2. I've been trying to flash my phone for a few hours to no avail. I have tried to flash a few different ROMs via ActiveSync and I get an error saying it lost connection after it tries to access the bootloader. I then tried to flash it via the SD card, but can't get past the tri color screen, even with a signed ROM.
The tri-color screen shows the following:
PB81120 HX-B3
SPL-2.00.HSPL 8G XE
0x05
Cotulla aHSPL 0x50
Can anyone tell me why I can't seem to get past this screen when trying to flash a ROM?
Sounds like a task for task29. Search for it in this forum, and after you perform it - load a proper rom to your device.
I tried task29 but when it gets to the bootloader it gets stuck on the tricolor screen and says USB at the bottom, just like all the other times I tried to flash it. I get the following error message:
Error [302] - Update Error
The ROM update utility has encountered communication errors during the update process. The program will guide you step-by-step to recover from the errors so you can continue with the update.
What am I doing wrong? I keep seeing this error message every time.
so you can't even load a ROM from the sd card? that eliminates a bad usb.
You put a Rom image on the root of your sd card (usually needs to be 8gb or smaller). You make sure it is named LEOIMG.nbh. While pressing in the reset button (by the battery), you hold down the volume down button. Your phone should go into bootloader (tricolored) momentarily, then switch to a grey screen that asks if you want to update. press power for yes or vol up? for no. You press the red (phone call end button) and it errors? Is this what happens?
many people report the supplied 16gb card doesn't work for flashing.
for usb flashing, enter bootloader manually. wait for serial to become usb, and then run the flash.
im having the same problem. i have hardspl, i falshed a radio 2.07.50 just fine, then i tried flashing the rom via computer, the bootloader screen would not display the grey coloured screen where you 'update image' and it said lost connection on my computer. I then tried the sd card way, LEOIMG.nbh, same result - no grey screen to 'update image'
I was trying to rootkit it, but on the last step I got locked in to a fastboot-loop, I eventually got out of it and was able to "install through ADB" through the OTA Oriole software.
Trying to rootkit it again, I messed up and got stuck on the same loop, but when I try to "install through ADB" the OTA file loads up 50% and I get the error "Current SPL 2021-11-05 Target SPL: 2021-10-05 this is considered a downgrade.
Denying SPL because it's SPL downgrade" and it aborts the installation.
Now whenever I try to boot, I get a "your phone is corrupted" message, I press power to continue, I get a message "your phone security is compromised" in orange, than I press power and it hangs on the Google logo on a white screen.
I can still get in to fastboot and all the options.
No idea what to try next.
If I took it to where I bought it, would they send it off to Google and they can fix it? Or do I have a brand new $1150 paperweight?
hiksemebs said:
I can still get in to fastboot and all the options.
No idea what to try next.
Click to expand...
Click to collapse
When you're in "fastboot" mode, can you still see your device name when you type in fastboot devices?
If so, then you still should be able to fastboot the latest factory image by following one of the outstanding guides by:
@Homeboy76 here.
Or
@V0latyle here.
Best of luck to you.
hiksemebs said:
I was trying to rootkit it, but on the last step I got locked in to a fastboot-loop, I eventually got out of it and was able to "install through ADB" through the OTA Oriole software.
Trying to rootkit it again, I messed up and got stuck on the same loop, but when I try to "install through ADB" the OTA file loads up 50% and I get the error "Current SPL 2021-11-05 Target SPL: 2021-10-05 this is considered a downgrade.
Denying SPL because it's SPL downgrade" and it aborts the installation.
...
Now whenever I try to boot, I get a "your phone is corrupted" message, I press power to continue, I get a message "your phone security is compromised" in orange, than I press power and it hangs on the Google logo on a white screen.
I can still get in to fastboot and all the options.
No idea what to try next.
If I took it to where I bought it, would they send it off to Google and they can fix it? Or do I have a brand new $1150 paperweight?
Click to expand...
Click to collapse
Your phone isn't bricked until you're completely unable to do anything.
Is your bootloader unlocked?
You should be able to sideload the OTA, as long as you aren't already on the newest firmware. Make sure you use the latest one.
Sideloading the OTA is the only way I know of to fix the corrupted screen; if that doesn't work, you're going to have to perform a whole flash of the factory image, and likely have to wipe. You can do this using the Android Flash Tool, but this requires an unlocked bootloader.
Since you essentially caused this problem yourself, it is likely you would have to pay for repair or RMA. So, let's see if we can help you fix it yourself first.
hiksemebs said:
I was trying to rootkit it, but on the last step I got locked in to a fastboot-loop, I eventually got out of it and was able to "install through ADB" through the OTA Oriole software.
Trying to rootkit it again, I messed up and got stuck on the same loop, but when I try to "install through ADB" the OTA file loads up 50% and I get the error "Current SPL 2021-11-05 Target SPL: 2021-10-05 this is considered a downgrade.
Denying SPL because it's SPL downgrade" and it aborts the installation.
...
Now whenever I try to boot, I get a "your phone is corrupted" message, I press power to continue, I get a message "your phone security is compromised" in orange, than I press power and it hangs on the Google logo on a white screen.
I can still get in to fastboot and all the options.
No idea what to try next.
If I took it to where I bought it, would they send it off to Google and they can fix it? Or do I have a brand new $1150 paperweight?
Click to expand...
Click to collapse
When you say you were trying to "rootkit it", do you mean you were trying to root it with Magisk? Or some other method? You should only use Magisk if you were trying some other method. I'm assuming you weren't trying to give yourself a virus
In addition to what the others have said, if you go the Android Flash Tool method you have to have OEM unlocking enabled it Developer Options. If you do, the flash tool will unlock your bootloader during the process so you don't have to unlock it manually beforehand. If it is grayed out in the disabled mode, you'll have to sideload the OTA, as stated earlier, or try factory resetting if you can.
Good luck...
I did something to mine where it would be stuck in a loop, wouldnt boot, I was able to get it into download mode, and then I flashed it back to stock from the google factory images website, then rerooted it. Been fine since.
Mine fast softbricked as well like 2 weeks ago.
I used the android flash tool to get back to stock rom again and after that I rooted it again. But you need an unlocked bootloader for that method.
Edit: Link to the flash tool