|
||||
I got it from the stock rom, but edited it with the HT64 encoder program to try to bypass a country code error that was occurring for another user with the stock rom. This is a similar method to one i used to successfully get the contents of the telus extended rom for Colonel
|
|
||||
OK here is exactly what happen. The phone has colonel latest nbf installed. I wanted to see why my phone signal was so low sometime. So I decided to flash back to the Colonel3.3beta2VerizonExtRom.zip but I added the radio_.nbf found in imcokeman dir the flashed actually completed OK but after it reboot it display none under the radio version. Now the boot screen display
h/w=2 m=12 u=4 r: none d 2.11.20 wwe The phone still boot up with rom and ext rom just no radio stack. and when I try to flash back using the stock Verizon rom I get error at the first part of the flash which is the radio portion, it just stayed at 0% for about 4-5 min. and error out. On the phone it display "upgrade radio stack please wait" and just freeze there. I still have PDA function but the phone part is not on because of no radio stack. I can still flash to different colonel version. I just need to flash the radio version back, my phone has no radio stack. I just need the Verizon radio flash back to the phone. I tried extracting the radio_.nbf from the stock rom but that file won't flash using the MaUpgradeUTnoID.exe, but if I use the radio file found in the imcokeman it will attemp to flash but freeze at 0% and error out some country code error. kdoweb |
|
||||
Yikes. Yeah, ok that makes more sense then as to why that guy's phone is borked. I was thinking that shouldn't happen with just a normal radio ROM file.
You may want to just delete it from the FTP site altogether (if you haven't already) or edit the file name to say "Do not use" or something in case people don't see this thread. |
|
||||
Quote:
you rename the file to test now is this still the same file? so you use HT64 to decrypt the files? my problem is after successfully flashing this file the phone boot up with no radio stack. is there a way to force the stack to install? kdoweb |
|
||||
kdoweb - man it is possible that you won't be able to get another radio ROM on your device. I didn't know that the file ImCoKeMaN posted had been modified. This is sort of uncharted territory... so it may not be fixable. You might be able to get Verizon to give you a new one if you go in and tell them it just started doing that. It's not the most honest thing to do, but maybe UTStarcom can refurbish it with their equipment. Or if you have insurance, use that.
If any good can come from this I think we now know not to mess around with radio ROMs. |
|
||||
Quote:
__________________
Kitchen updates at www.ppckitchen.org and you can get BuildOS help Here
If you have been helped by me or would like to support developers like Olipro, helmi_c, and others please feel free to Donate ALWAYS FLASH BACK TO YOUR CARRIER'S OFFICIAL ROM BEFORE TAKING YOUR PHONE IN FOR SERVICE OF ANY KIND ![]() |
|
||||
Quote:
kdoweb |
|
||||
Exactly the same process as kdoweb got me in the same spot, stuck at 0% on stage 1 of MaUpgradeNOID when using a radio rom.
In the RUU.log file, the errors are "Device CID Error" and "RWipe Data Error." Thanks. |
![]() |
|
|
|