Titan Kitchen CE OS 5.2.19209 (Build 19209.1.0.2) aka 5060

[ComputerGeek]

Ok. I had to reflash my phone back to Verizon for a day. When I was trying to Flash the phone back to the Kitchen, I downloaded the newest Sprint's rom from your website. This file is a lot smaller than usually. Approximately 4.12 megs. Why is the file smaller now? I downloaed it three times.

So, after flashing it with Sprint's rom (radio) that you have on your website, I cannot get the phone to boot. It just displays the Verizon logo and does not go past that screen. It does show in red letters that the radio rom has been updaed to 3.35.04 and that the firmware is Verizon's. I really need to use my phone. Now I cannot flash it with BuildOS because I need to fully boot the phone so that it can active sync and BuildOS can recognize it. PLEASE HELP.

[clockcycle]

Originally Posted by ComputerGeek

Ok. I had to reflash my phone back to Verizon for a day. When I was trying to Flash the phone back to the Kitchen, I downloaded the newest Sprint's rom from your website. This file is a lot smaller than usually. Approximately 4.12 megs. Why is the file smaller now? I downloaed it three times.

So, after flashing it with Sprint's rom (radio) that you have on your website, I cannot get the phone to boot. It just displays the Verizon logo and does not go past that screen. It does show in red letters that the radio rom has been updaed to 3.35.04 and that the firmware is Verizon's. I really need to use my phone. Now I cannot flash it with BuildOS because I need to fully boot the phone so that it can active sync and BuildOS can recognize it. PLEASE HELP.

Have you tried to put your phone into Bootloader mode (camera+ power+reset) and reflash back to the official Verizon rom/radio?

My suggestion would be that you read up on the threads pertaining to getting the GPS Sprint Radio/Rom working on Verizon before jumping into it like that, you may ruin/brick your phone..

Seems like you downloaded and burned in the Sprint Radio only, and not the ROM, I don't think your Verizon Rom is compatible with that radio/bootloader.

-CC

[puff]

Originally Posted by ComputerGeek

Ok. I had to reflash my phone back to Verizon for a day. When I was trying to Flash the phone back to the Kitchen, I downloaded the newest Sprint's rom from your website. This file is a lot smaller than usually. Approximately 4.12 megs. Why is the file smaller now? I downloaed it three times.

So, after flashing it with Sprint's rom (radio) that you have on your website, I cannot get the phone to boot. It just displays the Verizon logo and does not go past that screen. It does show in red letters that the radio rom has been updaed to 3.35.04 and that the firmware is Verizon's. I really need to use my phone. Now I cannot flash it with BuildOS because I need to fully boot the phone so that it can active sync and BuildOS can recognize it. PLEASE HELP.

i see you cross-posted this. at least this is a kitchen thread
looks like someone already mentioned bootloader...

*edit* activesync wont recognize your device in bootloader, but just continue anyway. it sounds like you need to double check and make sure you have 2.40 olipro bootloader, 3.35 radio, then install a 3.35 compatible rom

[ComputerGeek]

Bootloader will not recognize the device. I always used the full rom from Sprint, but I did not see it on the PPCKitchens website this time. Why is only the radio posted on the website? The full version was always posted before? I think that a warning for Verizon users is well deserved. Can anyone help me resolve this? When I start bootloader, it indicates that I must have my device synced and it will not recongize the device. Am I doing something wrong?

[gguruusa]

Originally Posted by ComputerGeek

Bootloader will not recognize the device. I always used the full rom from Sprint, but I did not see it on the PPCKitchens website this time. Why is only the radio posted on the website? The full version was always posted before? I think that a warning for Verizon users is well deserved. Can anyone help me resolve this? When I start bootloader, it indicates that I must have my device synced and it will not recongize the device. Am I doing something wrong?

You're not making any sense. You mean ActiveSync/Mobile Device Center won't recognize your device? Are you on Vista or XP? Bootloader indicates you must have your device synced? huh? You don't need to be synced for any of this.

Only the radio is posted because the full upgrade kit causes problems for many, and the rest of the upgrade isn't needed if you're going to make your own rom.

[ComputerGeek]

I understand what you are saying. But when you are upgrading from Verizon's firmware and are only using the Sprint's radio, it causes problems. The two do not work together, causing the device to no longer be recognized by the computer and for the phone to be stuck on Verizon's splash screen, when it is booted. I learned this lesson the hard way. I am just recommending that Verizon users know to only flash their Verizon's firmware with full version of Sprint's firmware and not just the radio.

I don't think that there is anyway that I can recover the device now, since the computer is not recognizing it and bootloader is not working. Ofcourse, any suggestions would be most appreciated. This is in no way a complaint, I am just trying to fix my phone and make sure that this will not happen to anyone else.

[crwinger]

Originally Posted by ComputerGeek

I understand what you are saying. But when you are upgrading from Verizon's firmware and are only using the Sprint's radio, it causes problems. The two do not work together, causing the device to no longer be recognized by the computer and for the phone to be stuck on Verizon's splash screen, when it is booted. I learned this lesson the hard way. I am just recommending that Verizon users know to only flash their Verizon's firmware with full version of Sprint's firmware and not just the radio.

I don't think that there is anyway that I can recover the device now, since the computer is not recognizing it and bootloader is not working. Ofcourse, any suggestions would be most appreciated. This is in no way a complaint, I am just trying to fix my phone and make sure that this will not happen to anyone else.

if this was rlly happening to ppl, id think there would have been a warning.........O about 1,2,3,4,5,6,7 months ago???

[tiermann]

Originally Posted by crwinger

if this was rlly happening to ppl, id think there would have been a warning.........O about 1,2,3,4,5,6,7 months ago???

It's the same process for everyone. New roms use the new radio, old roms use the old radio.

If you're using a kitchen ROM you need 3.35.04 + or it won't boot.
In the same way, Stock Verizon will not boot with the new radio. You will just sit at the splash screen.

If you're going from an old ROM to a new ROM versions, you will need to pop the battery out once to boot.

If you're still stuck on the splash screen (you're not in bootloader and you're not in windows so activesync will not recognize your device) you can always go back to bootloader mode (multi-color screen) and reflash the proper ROM.

It has nothing to do with using full sprint 3.35 or using just the radio to upgrade.

The reason only the radio is available now is that too many non-sprint users were flashing the entire sprint ROM and letting customizations run which were then setting all of their EPST settings to sprint. No fun having to reset all of those, especially if you don't know what the originals were for your carrier.

Originally Posted by ComputerGeek

I understand what you are saying. But when you are upgrading from Verizon's firmware and are only using the Sprint's radio, it causes problems. The two do not work together, causing the device to no longer be recognized by the computer and for the phone to be stuck on Verizon's splash screen, when it is booted. I learned this lesson the hard way. I am just recommending that Verizon users know to only flash their Verizon's firmware with full version of Sprint's firmware and not just the radio.

I don't think that there is anyway that I can recover the device now, since the computer is not recognizing it and bootloader is not working. Ofcourse, any suggestions would be most appreciated. This is in no way a complaint, I am just trying to fix my phone and make sure that this will not happen to anyone else.

If you have a verizon splash screen, there's no reason you can't get back to bootloader (multi-color screen) mode. Press power+camera and hold them while you soft-reset. You can then flash your custom ROM. If it doesn't bring you to bootloader mode the first time, keep trying until you get it. If it doesn't vibrate, then you've got it.

[gguruusa]

Originally Posted by ComputerGeek

I understand what you are saying. But when you are upgrading from Verizon's firmware and are only using the Sprint's radio, it causes problems. The two do not work together, causing the device to no longer be recognized by the computer and for the phone to be stuck on Verizon's splash screen, when it is booted. I learned this lesson the hard way. I am just recommending that Verizon users know to only flash their Verizon's firmware with full version of Sprint's firmware and not just the radio.

I don't think that there is anyway that I can recover the device now, since the computer is not recognizing it and bootloader is not working. Ofcourse, any suggestions would be most appreciated. This is in no way a complaint, I am just trying to fix my phone and make sure that this will not happen to anyone else.

As Tiermann stated, you do NOT want to use the full sprint release on your non-Sprint phone. Your phone is OK, just put it in bootloader mode and flash a 3.35 compatible ROM. If you truly can't get it into bootloader mode (power+camera+reset = tri-color screen = bootloader), you did something other than you are telling us. Of course, that you can even get the first splash to show indicates your phone isn't bricked and your bootloader is OK.

[shaggylive]

Originally Posted by shaggylive

any chance we could have the cLaunch oem updated?

12.04
Fixed : There is an undocumented issue with today screen plugins that causes startup display error

thought I'd report back, I installed the cab of cLaunch 12.0.4 over the top of version 11.0.0.1 in the kitchen with great success! works perfect now. (so far)
here's the link for those interested..
http://downloads.sourceforge.net/cla...4&big_mirror=0

btw, i'm no programmer, but it seams like all apps seemed to have this issue going from wm5 to 6, just some were more ahead of the curve than others...

also as a kitchen junky, I think this oem was from the apache kitchen which at the time was wm5.