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???
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.
This is the first time I've messed with this phone I've flashed many different models in the passed but this is the only one that is giving me issues and the worst part is that its not mine so any hell i will greatly appreciate it.
Here is what i did read what ever i can to get more accustomed to this phone. and searched everywhere to help me figure out what i can do.
So i flashed the unlocker. Coke 2.31
after i did that i flashed nfsfan's 1.5 rom using usb cable.
no i cant get into the operating system at all it hangs at the vzw splash screen.
Is there a way to get this phone back to normal? i cannot connect thru activesync and when i tried to reflash using sd card it shows the loading screen for a split secon then goes back to the bootloader.
Please help its my bros phone i need it up and running asap.
Thank you
This post helped quite a bit
ArcaneMagus said:
Just thought that I would post what happened to my phone and the steps that eventually recovered it in case it helps somebody else:
My phone was stuck with "No Radio" on the boot loader screen and the SPL as "SPL-2.31.CoKe", but none of the 3.x ROMs would flash properly that I tried. So here are the steps that eventually recovered it (mostly...):
1.) I installed the ROM above from the tri-color screen (power+camera+reset). I still had no radio, but it was letting me past this and booting up to WM. http://forum.xda-developers.com/showthread.php?t=357762
2.) I then re-flashed the 2.31.CoKe boot loader (not sure if this step is necessary but listing what worked...)
3.) I tried to install RUU_Vogue_VZW_WWE_3.14.605.1_Radio_3.37.78_Ship.exe but it failed at 10% restarting to RUUNBH screen and the installer gave me Error [290]: Invalid Command
4.) I then tried to install the latest sprint ROM straight from the HTC site:_Touch by HTC (Sprint)_RUU_PPST_Vogue_SPRINT_WWE_3.03.651.4_2_Radio_3.42.30_AM_NV_2.04_Ship this looked like it was going to fail at the same part the Verizon rom did as it rebooted at 10% to RUUNBH screen, but the Sprint installer did something (I heard the computer lose and gain connection multiple times) and eventually it went right back and continued on from 11% and finished successfully.
5.) Rebooted and I had a radio now! Rather then risking trying to install the Verizon ROM again I went straight to the custom ROM I had originally started out with: NFSFAN 6.5 V6 which is working fine for me, except the GPS which is what started out my adventure of the last 3 days...
Just a note: for all flashes except the final one I simply waited till it was at the "Tap the screen..." stage till flashing. I never let any ROM but the final one run it's customization.
Click to expand...
Click to collapse
The above method works on a Vogue that is stuck on the bootloader screen with no radio.
Or if you get a rom to install and it stops at a windows screen that says no radio.
the only difference i tried was i didn't use the HTC Official Sprint rom, as i could not find it.
I used this rom.
RUU_Vogue_4350_ALLTEL_WWE_3.10.671.1_RS3.42.30_NV2.02_PRL30031_SHIP.exe
I let all customizations run on the last rom update.
Ok, I'm with Bell mobility, had nsf's 6.5 rom installed. I had t osend my phone in for repair, so I needed to downgrade.
I read the instructions and put the coke 0.41 unlocker on, Now I try putting on the original bell rom and it stops at 31% and says theres a error.
What I've tried
-Restarting the rom, keeps erroring at 31%
-Tried the unlocker again, says no device connected
-Tried the 2.31 unlocker still says nothing connected
Somebody please help
Why do people keep using the .41 unlocker? That is for non-gps devices.
You need to flash the .40 unlocker, then the stock ROM.
Flash from bootloader (Power+ Camera button, and stylus reset)
Thanks for your quick response, I got it back up by putting the custom rom back on, but as you just said the wrong unlocked
where would i get .40
I found 0.40
Now do I just downgrade the unlocker, let it restart the device and everything it does and then install the stock rom?
Yep.
10chars
ok so I installed 0.40, and then the stock rom
It stopped at 31% again, I followed the recovery, removed the battery and it went back to stock!!!
Thanks
ok have a new problem, Now it turns on, Gets to the today screen and I get the error "\windows\ppst.exe does not exist" And it won't let me do anything, have to take the battery out
You're going to want to flash it again. It should have gone all the way through. ppst.exe is loaded during customizations.
Ok, so now activesync won't connect, so it won't let me flash the rom again
my internet won't work on it, I'm guessing it has to do with ppst.exe not installing.
What should I do now
Put the phone into bootloader, then flash. Don't worry about activesync right now.
Ok so heres an update. I finally got the .40 unlocker working and reinstalled the original rom, but it said PPST.exe was missing. I tried a hard reset and it still said PPST.exe was missing from \Windows
I tried again to reflash the original rom that I downloaded from the htc website for bell and still got PPST.exe is missing.
I installed 2.31 unlocker and put nsf's wm 6.5 on and everything works fine
But I need to know why PPST isn't working so I can replace the original
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.
Hi
I had my S620 aside, haven't used for 3 years.
Now I'm trying to give it to a friend and i need to put a Portuguese rom on it.
I know I've change the stock rom to the 3VO.2.80.092509 and now I want to flash the official portuguese rom.
I've downloaded it (RUU_Excalibur_BRIGHTSTAR_PTB_1.30.514.2_4.1.13.47_02.98.90_Ship Extract) from official rom's page but when I try to flash it, it gives me the Error [244]: Invalid model ID, at 3%.
Well, the rom is for Excalibur, i flashed a rom before long time ago, do i need to update the HSPL ?
What am i doing wrong?
Thks for your help.
Regards
My Excalibur especifications:
On Bootloader
Excalibur
ONBL 1.30.0000
SPL 1.30.0000
Windows Mobile 6.5
OS: CE OS 5.2.23004 (build 23005.5.3.0)
ROM: 3VO.2.80.092509
Radio version: 4.1.13.47_02.98.90
read carefully
i overclock mine and i solve it. go to windows mobile center and disable usb connection. press and hold sym while pluging in usb( this will take you to bootloader mode) and run uspl from the cid bypass after that run the original rom. if it does work go back to stock rom and run cid bypass and ru the rom you metion.
http://forum.xda-developers.com/showthread.php?t=329605
http://forum.xda-developers.com/showthread.php?t=328690&highlight=cid
XicoBombas said:
Hi
I had my S620 aside, haven't used for 3 years.
Now I'm trying to give it to a friend and i need to put a Portuguese rom on it.
I know I've change the stock rom to the 3VO.2.80.092509 and now I want to flash the official portuguese rom.
I've downloaded it (RUU_Excalibur_BRIGHTSTAR_PTB_1.30.514.2_4.1.13.47_02.98.90_Ship Extract) from official rom's page but when I try to flash it, it gives me the Error [244]: Invalid model ID, at 3%.
Well, the rom is for Excalibur, i flashed a rom before long time ago, do i need to update the HSPL ?
What am i doing wrong?
Thks for your help.
Regards
My Excalibur especifications:
On Bootloader
Excalibur
ONBL 1.30.0000
SPL 1.30.0000
Windows Mobile 6.5
OS: CE OS 5.2.23004 (build 23005.5.3.0)
ROM: 3VO.2.80.092509
Radio version: 4.1.13.47_02.98.90
Click to expand...
Click to collapse
so weird
Ratchewer said:
i overclock mine and i solve it. go to windows mobile center and disable usb connection. press and hold sym while pluging in usb( this will take you to bootloader mode) and run uspl from the cid bypass after that run the original rom. if it does work go back to stock rom and run cid bypass and ru the rom you metion.
http://forum.xda-developers.com/showthread.php?t=329605
http://forum.xda-developers.com/showthread.php?t=328690&highlight=cid
Click to expand...
Click to collapse
Hi
I did what you've told, ran uspl from cid paypass, all good till the screen stayed almost white.
When i tried to install PTB stock rom the flasing frooze at 0%.
Had to unplug the usb cable, and now each time i turn on the pda it goes to bootloader mode everytime.
Tried to flash through sd card all the stock roms i found without success. All the attempts through usb cable didnt passed 0%.
It starts to check the sd contents but then goes straight away to 3 colour bootloader mode without doing anything.
Then i remembered i had to install the original stock rom, which was the BT brand, that i found yesterday.
Now comes the weird part.
First time i try to flash the BT brand rom, it installed the rom (i didnt quite saw the whole process), and when it restarted it self, went again to bootloader mode.
Tried hardreset, tried to flash again, it goes straight to bootloader.
What the hell is going on???????
In my whole flashing history, i had 100% success over 50 flashes, and now its freaking weird.
Can you lead me again?
Thanks for everything.
Greetings
Try this here
ok go back to the original phone stock rom from the service provider and start over. use the usb bootloader mode after run the xda applicationunlocker file and do the cid bypas. then run the utilityupdate from the other rom ( not the one in the cid bypas file in the link) meaning do not click yes to the windows security prompt skip and run the romm u want to use
XicoBombas said:
Hi
I did what you've told, ran uspl from cid paypass, all good till the screen stayed almost white.
When i tried to install PTB stock rom the flasing frooze at 0%.
Had to unplug the usb cable, and now each time i turn on the pda it goes to bootloader mode everytime.
Tried to flash through sd card all the stock roms i found without success. All the attempts through usb cable didnt passed 0%.
It starts to check the sd contents but then goes straight away to 3 colour bootloader mode without doing anything.
Then i remembered i had to install the original stock rom, which was the BT brand, that i found yesterday.
Now comes the weird part.
First time i try to flash the BT brand rom, it installed the rom (i didnt quite saw the whole process), and when it restarted it self, went again to bootloader mode.
Tried hardreset, tried to flash again, it goes straight to bootloader.
What the hell is going on???????
In my whole flashing history, i had 100% success over 50 flashes, and now its freaking weird.
Can you lead me again?
Thanks for everything.
Greetings
Click to expand...
Click to collapse