I got Helmi's AKU 3.5 Rom Kitchen to work(NO USB)

[hdiffly]

Hoping to get some advice here as to how to get my radio working again.

Have had so much fun playing with this stuff, though I may be in too deep.

I decided to give "helmi_Apache_kitchen_3.5_ImCoKeMaN_R2" a shot, and I loved ImCoKeMan's 3.3 helmi work. Just incredible.

Unfortunately, i'm getting the "A wireless radio must be attached to use the phone" message and my Radio Rom is listed as NONE. I've tried everything I know. I was able to go back to the 3.3, but still the radio is out. I tried to run the official Verizon OEM that has always taken me back to safe ground, but it now tells me that I have a Country Code error. I then tried to run those files using MAUpradeNoID, but this time the program just comes to the finish screen in like 10 seconds and says congrats!

Looking at RUU.log, there are radio errors:
When using MaUpgradeNoID tool I get an "Image Radio Checksum Error"
When I run ROMUpgradeUt.exe (from Verizon package) I get "Device CID Error."

Did that make any sense?

Thanks for anyone's input.

[ImCoKeMaN]

Are you using using the convert amd flash directory in the kitchen i posted? It sounds like you have a radio rom somewhere in the same directory as the flash utility which isn't working properly. Do you have a sprint phone? If so here is the correct radio rom:
EDIT: File removed as VZW rom was requested and I don't want to cause any added radio rom confusion

To include this just place it with the others in the flash subdirectory. Another option is to run the sprint rom first to flash the ROM then try a kitchen rom WITHOUT the radio_.nbf in the same directory.

Good luck, hope this works!

[hdiffly]

I did try and put the verizon radio from the Verizon XV6700 APAC_VZW_20720_200_11000_Ship.exe downloaded from UTStarcom in the flash utils subfolder of the convert and flash directory of the Kitchen. When the radio rom is in that directory, then the Device Software Upgrade Utility just speeds through to finish screen without ever running the rom installs (neither the radio nor the nk.) As soon as I remove that radio rom, then the MaUpgradeUt_noID.exe file runs as expected by installing the nk rom.

When I try to run the Verizon XV6700 full APAC_VZW_20720_200_11000_Ship.exe downloaded from UTStarcom, which I just now actually did to make sure I wasn't maybe working from a corrupt copy, I get the "Country ID Code Error 120" message window in the Device Software Upgrade Utility, which then exits. When I look in the RUU.log file created in my c:\ directory, there is a "Device CID Error" listed. However, if I use the MaUpgradeUt_noID.exe Uitlity instead of the one from UTStarcom, the error in the RUU.log file is "UpdateRadio Check Error Fail." And also, if I take the three ROM files (nk, ms_ and radio) and move them into the the flash utils subfolder of the convert and flash directory of the Kitchen the error in the RUU.log file is "Image Radio Checksum Error."

Probably just gave you too much info there, but thought it all may be useful.

Nice to know I have insurance on this phone, other wise I'd be a bit worried. Makes playing in the Kitchen much less stressful, though the loss of wireless access is not good. (I must confess though, not being directly accessible via mobile over the weekend is gives this IT tech a chance to breath).

[ImCoKeMaN]

here give this one a try:
[radio link removed]

I tweaked it's language settings so the country code should work, but i didn't test it since i'm sprint.


If you weren't having trouble with the stock rom i'd think that it was an issue with removing some OEMs (since i've done similar things lately )

[hdiffly]

Don't think that file uploaded correctly. Its file size is 209bytes.

[ImCoKeMaN]

This time i think it worked, try again.

[eyeballz]

imcokeman,


anyway to change the splach from the ugly telecom one without usb. WIll it work via BT activesync or did you break that too

j/k

[ImCoKeMaN]

My suggestion is to use the tools from widawakes rom builing toolkit and follow these steps of his procedure before converting to .nbf:

Changing bootscreen.

1. copy your nk.nba file into the directory 5. BootScreen, then rename to nk.fat.

2. Run patchlogo.exe, select nk.fat in the first dialog and your preferred .nb file in the second. Note: If you have a 320X240 image you would like to use, you can use the nb_image_converter_859_418.exe to create a custom .nb file

3. Rename the nk.fat back to nk.nba and convert into a nk.nbf.



As for the bluetooth, i don't have that on my PC, but i've heard bluetooth activesync works. I don't know that it will work for the bootscreen changes, but you are welcome to try

[mcevoke]

I can confirm that bluetooth active sync works, flawlessly, It allows you browse the device, move files and yes even chamge the bootscreen, I also installed software via bluetooth activesync.

kinda silly to be charging via a usb cable and syncing bluetooth...

but bluetooth is faster than usb2... aside from the fact I need usb to do the first sync via the missing sync on my mac I would ditch the usb.

[hdiffly]

ImCoKeMaN,

I apologize for the delay in my response.

I thought it had worked, the VZW radio you sent, as it ran as it was supposed to, with the color bar moving along, taking about 5 or 10 mins. But alas, when I hard reset and got back to the desktop, still no radio!

I tried to run it again via bootloader as I did the last time, but now it gets stuck at 0% and then gives me an Error 114, Radio Rom Update Error.

The RUU.log still gives me that "Device CID Error." Which doesn't stop it from moving forward though. "RWipe Data Error" is the line that seems to stop it this time.

Again, thanks for your help here.