I searched around to see if an issue I'm having is common, with no success. To keep it short I am running:
Hard-SPL unlocker on an AT&T touch pro 2
DeepShining X10.21680 Rom
Rhodium Radio 4.49.25.88 Radio
My issue is that the phone freezes up and after reset goes into the tri-color screen. Once in tri-color it will remain there until it "feels happy", remain operational until it decides to freeze again. There is nothing that I am doing before that seems to be a trend. I have tried a hard reset, a different ROM, and a different radio but it still has not improved.
Is there any ideas that can be suggested to help me with this problem.
Thank you
It's a pain reverting back to the stock bootloader, I had to for a warranty exchange.
Click to expand...
Click to collapse
Going back to stock spl is really easy.
1. Boot into bootloader
2. Plugin usb
3. flash the stock spl
Related
Hello everyone.
Apologies if this has been addressed somewhere already, but if this is the case, I was unable to find it.
I have a French Orange Diamond, which I was able to flash w/o problems with Hrad-SPL 1.30 by Olinext, and then with the RUU_Diamond_HTC_Europe_1.37.401.3_Radio_Signed_Dia mond_52.26a.25.09_1.00.25.03_Ship Rom. This worked flawlessly, and I have been a very happy camper since!
Tonight, I tried to upgrade the radio ROM to 1.00.25.05. To do so, I first installed the developer version of Hard-SPL 1.40 by Olinext, which went very well. Then, I tried flashing the radio, and instead of getting the bootloader, I got the colorwheel, and almost immediately afterwards the phone screen faded to complete black. After a little while, the ActiveSync (4.5) window disappeared from my XP SP3 PC screen, and the phone waited there until the flash process timeed out and it entered recovery mode. This happens every time now, and I am always able to recover perfectly.
Thinking it might be related to the Hard-SPL, I flashed back to version 1.30 by Olinext, and then even reverted back to the stock 1.37. Whenever flashing an SPL, the screen still fades to black, but the process completes ok, whereas whenever I try to flash the radio, it will always time out with an Error 262, apparently comms-related.
Has anyone encountered this in the past? Anyone know what/how to fix?
Thanks!
P.S. I forgot to mention that if I copy the EnterBootloader.exe onto the phone and run it from there, the screen will also fade to black in exactly the same way.
I have a major issue here. Please bear with me.
I flash my phone to the official 6.1 rom a few months back. Now I recently decided to try a custom rom by NFSFAN. So first thing was to flash the bootloader by IMCokeMan version 0.41. After doing that I flashed the custom rom. Once it booted up my phone kept reboot itself every few seconds or so. It turns out now that it was a battery issue, but I was sure the battery was fine and thought it was simply an incompatibility issue with the rom.
So I then tried to flash the official 6.1 rom back on, but it froze at 44% and then threw a 262 error after a minute or so. I then learned that I needed to flash the IMCokeMan 0.40 unlocker/relocker to get the official rom back on. So I did. Then tried the official rom again, and lone behold, froze at 44% and then gives the 262 error.
Then I thought I'd try the NFSFAN's rom again. So I flashed that. Once it successfully finished and started to load it freezes at the Telus splash screen and "No Radio" appears in red on the screen.
So this is where I'm at. I've tried to flash nearly every bootloader I could find and no matter what I do the bootloader always shows "SPL-0.41.coke". I can't flash any official rom including Telus, Bell or Sprint as they each freeze at different spots but consistently at the same spot individually (Telus at 44%, Bell at 30-some%, Sprint at 29%). I can flash custom roms as well as the beta wm6.5 rom but those don't fully load and give the "No Radio" error.
The ONLY rom I can successfully flash is an old 6.0 rom that someone dumped from a telus vogue. But in this rom under "Device Information" the rom is 1.11.661.1 and the radio version field is blank! And I cannot make data connections, as in I cannot connect to the internet, etc.
So my question to anyone that may know is: why am I having these issues with the radio version? How can I get rid of the SPL-0.41.coke bootloader?
And what can I do at this point? Any help from anyone is a thousand times over appreciated!
There's another copy of this thread at PPCGeeks.com:
http://forum.ppcgeeks.com/showthread.php?p=792095#post792095
-Chris
*********** bump-a-doo? *************
eeps! similar issue! did I brick it???
My symptoms are different, but the way I got there is pretty much the same:
I wanted to try NFSFAN's 1.28 Bell rom, so I unlocked with IMCokeMan's 2.31 unlocker (2.31 instead of 0.41 because I had previously upgraded to UTStarcom's Bell WM6.1 rom with the 3.42.50 radio when it came out). The unlock process went smoothly, and I had no problem flashing NFSFAN's 1.28 rom after that either.
NSFAN's RUU said I was successful, and my Vogue automatically restarted but got hung up on the "Bell" splash screen, I tried to let it work itself out for over 15 minutes before I tried a reset, but it still had the same problem. Tried a hard reset: same problem. I let it sit connected to the charger for a half week now and it still is hung at the "Bell" splash screen.
I'd try to flash the stock rom again, but I can't get the RUU to work without an activesync connection (right?).
Did I brick it? Any advice would be appreciated.
Here's everything my version-screen says if it helps at all:
M 03
B 01
P DCAAXOM-4350H
R 3.42.50
D 3NFS (is that NFSFAN's rom or an error?)
cbstryker said:
I then learned that I needed to flash the IMCokeMan 0.40 unlocker/relocker to get the official rom back on. So I did. Then tried the official rom again, and lone behold, froze at 44% and then gives the 262 error.
Click to expand...
Click to collapse
I've been reading through the ImCoKeMaN's unlocker sticky (http://forum.ppcgeeks.com/showthread.php?t=20370), and I noticed there is a "VERY IMPORTANT / Warning" referring to the 0.40 rom you used. Here's what it says:
If your carrier did not release a rom and you flash an exe of another carrier with the 0.40 unlocker you won't be able to flash ANY rom until unlocking again (this requires booting into WM)
Click to expand...
Click to collapse
then it points to this: ftp://up.ppcgeeks.com/Vogue/Users/ImCoKeMaN/Vogue_unlocker.exe
Hopefully that helps you out.
esskay said:
My symptoms are different, but the way I got there is pretty much the same:
I wanted to try NFSFAN's 1.28 Bell rom, so I unlocked with IMCokeMan's 2.31 unlocker (2.31 instead of 0.41 because I had previously upgraded to UTStarcom's Bell WM6.1 rom with the 3.42.50 radio when it came out). The unlock process went smoothly, and I had no problem flashing NFSFAN's 1.28 rom after that either.
NSFAN's RUU said I was successful, and my Vogue automatically restarted but got hung up on the "Bell" splash screen, I tried to let it work itself out for over 15 minutes before I tried a reset, but it still had the same problem. Tried a hard reset: same problem. I let it sit connected to the charger for a half week now and it still is hung at the "Bell" splash screen.
I'd try to flash the stock rom again, but I can't get the RUU to work without an activesync connection (right?).
Did I brick it? Any advice would be appreciated.
Here's everything my version-screen says if it helps at all:
M 03
B 01
P DCAAXOM-4350H
R 3.42.50
D 3NFS (is that NFSFAN's rom or an error?)
Click to expand...
Click to collapse
hey, I answered this question of yours already over here http://forum.xda-developers.com/showthread.php?p=3526872#post3526872
Detroit Doug
Thats the problem im having theres no way I know to get passed that screen that says no radio. So you can't even get into WM. So since it cant load into WM you can't run the unlocker. Most custom roms flash fine but its the radio thats missing it wont go past that.
Viper Matrix Wireless said:
Thats the problem im having theres no way I know to get passed that screen that says no radio. So you can't even get into WM. So since it cant load into WM you can't run the unlocker. Most custom roms flash fine but its the radio thats missing it wont go past that.
Click to expand...
Click to collapse
You do NOT need to be in WM to unlock, WM has nothing to do with it
Start phone in bootloader mode (power+camera+stylus in reset hole and hold this until the 3 color screen comes up) it will say serial at the bottom
Plug in the USB cable to your PC and it will change to say USB
Start the 2.31 Unlocker RUU.EXE (RomUpdateUtility.exe) file, follow the steps
then run your custom ROM when after it restarts do does it thing and reboots again by going back into bootloader mode and doubleclicking the RUU.exe file in the custom ROM folder you want to use
Once it runs through the setup after flashing and then the autorun and restarts - hard reset the phone (red+green+stylus in hole) until a gray screen comes up
Follow directions and then setup and autorun and reboot
Make sure you have a carrier cab and/or mms fix either on your PC to copy over to your phone or on your SD Card ahead of time and you should be set to go
Detroit Doug
Detroit_Doug said:
You do NOT need to be in WM to unlock, WM has nothing to do with it
Start phone in bootloader mode (power+camera+stylus in reset hole and hold this until the 3 color screen comes up) it will say serial at the bottom
Plug in the USB cable to your PC and it will change to say USB
Start the 2.31 Unlocker RUU.EXE (RomUpdateUtility.exe) file, follow the steps
then run your custom ROM when after it restarts do does it thing and reboots again by going back into bootloader mode and doubleclicking the RUU.exe file in the custom ROM folder you want to use
Once it runs through the setup after flashing and then the autorun and restarts - hard reset the phone (red+green+stylus in hole) until a gray screen comes up
Follow directions and then setup and autorun and reboot
Make sure you have a carrier cab and/or mms fix either on your PC to copy over to your phone or on your SD Card ahead of time and you should be set to go
Detroit Doug
Click to expand...
Click to collapse
I answered his question on his thread. You forgot one thing though Doug. He doesn't have a radio. He'll need to flash back to stock before he flashes a custom. Doesn't this get frustrating???
Hi everyone,
my Vogue has 3.37.15 radio and is unlocked with 2.31 running NSFFAN 6.5 rom. My phone randomly restarts every 5 seconds to 20 minutes, makes no difference whether it is connected to power or not. Any ideas or experience with this? Wondering if its software or and internal problem.
have you tried a hard reset yet?
im in the same situation. i had nsfan v8 on and working for a few weeks, and just upgraded to v10. and it is restarting and now it won't come up. and yes i did the hard reset. any suggestions should i re flash it?
infinateLoopMan said:
im in the same situation. i had nsfan v8 on and working for a few weeks, and just upgraded to v10. and it is restarting and now it won't come up. and yes i did the hard reset. any suggestions should i re flash it?
Click to expand...
Click to collapse
Hard Reset = Re-Flashing of phone
Soft Reset = rebooting or using the reset button with stylus on bottom of phone
Yes, hard reset the phone
Detroit Doug
If re-flashing doesn't work, then flash back to the Verizon 6.1 ROM, don't let customizations run, then flash whatever ROM you want the radio to be (Bell 3.42.50 for instance) or if you're keeping the Verizon 3.37.78 or whatever it is, then flash the v11 ROM that was just released and soft reset after customizations then re-flash it once more for good measure. Hopefully after all that it will be more stable.
I was attempting to change to ookba's 3VO ROM but the operation failed and the ROM did not install. I did get the recovery instructions screen and followed them but the phone did not reset to the previous ROM (NRGZ28's EnergyROM 52409). The phone hangs on the Windows Mobile screen. I have done the following -
1) Followed ookba's recovery instructions and gotten the tri-band screen. However whenever I try to flash back to the T-Mobile ROM (any version) I get Error 260.
2) Followed stylez hard reset instructions and gotten the reset screen but the phone hangs on the Windows Mobile boot screen. A hard reset does not occur.
3) Followed NRGZ28's "In Case Things Go Wrong" instructions and gotten the tri-band screen, however when I try to flash the EnergyROM (or any other non T-Mobile ROM) I get corrupted image errors.
4) I have used jockeyw2001's bootloader but get Error 260
Also, the power button does not turn the phone off. I have to remove the battery to get it to shut down. I think I have tried all the recovery steps I know if. If anyone has a suggestion or solution I would be most appreciative. Thanks.
The Rotagilla said:
I was attempting to change to ookba's 3VO ROM but the operation failed and the ROM did not install. I did get the recovery instructions screen and followed them but the phone did not reset to the previous ROM (NRGZ28's EnergyROM 52409). The phone hangs on the Windows Mobile screen. I have done the following -
1) Followed ookba's recovery instructions and gotten the tri-band screen. However whenever I try to flash back to the T-Mobile ROM (any version) I get Error 260.
2) Followed stylez hard reset instructions and gotten the reset screen but the phone hangs on the Windows Mobile boot screen. A hard reset does not occur.
3) Followed NRGZ28's "In Case Things Go Wrong" instructions and gotten the tri-band screen, however when I try to flash the EnergyROM (or any other non T-Mobile ROM) I get corrupted image errors.
4) I have used jockeyw2001's bootloader but get Error 260
Also, the power button does not turn the phone off. I have to remove the battery to get it to shut down. I think I have tried all the recovery steps I know if. If anyone has a suggestion or solution I would be most appreciative. Thanks.
Click to expand...
Click to collapse
Maybe its safe to assume you have a hardware issue? Since the initial flash and following consecutive flashes failed, maybe its a bad USB cable? I would try reflashing the shipped T-Mobile ROM from a different PC altogether using a different USB cable. Since your phone gets to the Bootloader (multicolor) screen means it's not bricked. Try different PC and cable hardware...
Will do. I did try another hard reset and the boot screen has sat for over 20 minutes without getting past it.
Or try flashin stock ROM via SD
you must flash to official rom to make any progress at this point. at least thats what i had to do when my computer auto-restarted in the middle of one of my flashes.
Fixed, thanks for the help.
bricked excalibur
how did you fix it cause i'm having the very same problem
Switched from a PC running Windows 7 to one running XP.
muga said:
how did you fix it cause i'm having the very same problem
Click to expand...
Click to collapse
Welcome to the forum
Also reading here would help http://forum.xda-developers.com/showthread.php?t=415225
Well that didn't work for me its stuck it the multi colour screen and pc not flashing it. When it does recognise and start to flash i see a count down screen like the one on pc but only stops at 3percent
muga said:
Well that didn't work for me its stuck it the multi colour screen and pc not flashing it. When it does recognise and start to flash i see a count down screen like the one on pc but only stops at 3percent
Click to expand...
Click to collapse
Muga, It's also happening to me. I had previous flashes with different roms Kavana's, rose, energy (6.1 release) and everything went well with no problems at all. But a few days ago, I tried to flash my excalibur with the latest release by NRGZ28 (energy rom 6.5) and what I think what happened was that I didn't run the unlock file aplications (since I didn't have to do it in the other flashes, because I already had unlock the phone with the first upgrade) that's the only explanation I can get. At the end, I came up with the frozen screen and I've tried the bootloader steps, original rom installation, hard reset with no succes at all. What I get is the same error you have.
Ok so i just recently got a Verizon XV6900 (Vogue), i tried flashing the NFSFANS wm6.1 and wm6.5 roms but both of these would constantly cause my device to reboot if it wasn't plugged via USB. So i tried reflashing it back to the original 6.1 pro that came on the phone by using the one from the HTC Website, that failed after 31% and i had to recover it. Now the device is just stuck at the screen with the 3 colors with the message
Vogu100
SPL - 2.01.0000
CPLD-3
i have no idea what to do to get out of this, sorry I'm a complete noob and I tried searching but I couldn't find what i was looking for
Any help is appreciated
Your Vogue is not unlocked. Try running the unlocker (.40) again. Once that is done, unlock using the 2.31 unlocker. You should then be ready to flash a custom ROM.
EnZandOutZ said:
Ok so i just recently got a Verizon XV6900 (Vogue), i tried flashing the NFSFANS wm6.1 and wm6.5 roms but both of these would constantly cause my device to reboot if it wasn't plugged via USB. So i tried reflashing it back to the original 6.1 pro that came on the phone by using the one from the HTC Website, that failed after 31% and i had to recover it. Now the device is just stuck at the screen with the 3 colors with the message
Vogu100
SPL - 2.01.0000
CPLD-3
i have no idea what to do to get out of this, sorry I'm a complete noob and I tried searching but I couldn't find what i was looking for
Any help is appreciated
Click to expand...
Click to collapse
just plug it back in and try to reflash the stock ROM. don't open any programs on your computer while you are flashing. i tried to open a media player to listen to music and it froze the RUU. just flash it again it worked for me.