Fully working Helmi AKU 3.5 kitchen PPCGeeks revision

[oturn]

Looking good so far on my VZW XV6700. However, dialing ##778 no longer brings up the phone provisioning menu. I just get a Verizon "call could not be completed" message. Any idea why this isn't working?

[verizonguy]

Originally Posted by oturn

Looking good so far on my VZW XV6700. However, dialing ##778 no longer brings up the phone provisioning menu. I just get a Verizon "call could not be completed" message. Any idea why this isn't working?

Ditto. I just noticed that myself today. I flashed back to the stock utstar rom, then reflashed the 3.5 build just to make sure it wasn't something custom of mine, but it wasn't. All the ## stuff no longer works, ie: ##778, ##33284, ##3328873, etc.

I had heard that custom dialpad skins can caus that too. Any ideas?

[willysp]

Originally Posted by bzo

thanks for the info. What util do we use to apply a different splash to nk.nba?

From one of Mike's first custom ROM posts:

http://www.ppcgeeks.com/how-to-build...rom-t2124.html

Mike says:

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 back into a nk.nbf.

[ashen]

Does anyone know if this new Rom fixes the issue of iGuidance crashing when switching back from Full screen mode?

Thanks for the great release and keep up the good work.

Ashen

[Wideawake]

Originally Posted by oturn

Looking good so far on my VZW XV6700. However, dialing ##778 no longer brings up the phone provisioning menu. I just get a Verizon "call could not be completed" message. Any idea why this isn't working?

All # codes stopped working with aku3.3 if I'm not mistaken...

[avaya]

Originally Posted by ashen

Does anyone know if this new Rom fixes the issue of iGuidance crashing when switching back from Full screen mode?

Thanks for the great release and keep up the good work.

Ashen

Strange that I don't have any problem running iguidance on any of the ROM. I have iGuidance installed on the mini-SD too. I am not using the theme.ini file and my map size is relatively small (oregon, washington). I am using 3.01 version of iGuidance so not sure about 3.0.

[willysp]

In Device Information (start-settings-system-dev info), my ExtROM version field is blank. I had manually deleted my few remaining Sprint files from it before loading my 3.5 ROM (with the SprintExtendedOEM_199).

I have the Ext Rom unhidden and unlocked, and can copy files in and out, and can install to it.

I doesn't look like a big issue, but I wonder if something is wrong.

Thoughts and advice, please?? TIA!

[vboyz103]

to get the ## numbers working, you need to install the APAC_Customize.sa.cab in the VZW extended rom.

[kinglou0]

Originally Posted by vboyz103

to get the ## numbers working, you need to install the APAC_Customize.sa.cab in the VZW extended rom.

Will this work for Sprint phones???

[verizonguy]

Originally Posted by vboyz103

to get the ## numbers working, you need to install the APAC_Customize.sa.cab in the VZW extended rom.

Do you mean Customize_105201.sa.CAB ?