Problems/Bugs/Issues with AKU 3.3 Helmi_c ROM - Page 38

**schettj** · #**371** (**permalink**) 01-31-2007, 07:03 PM

Right - radio firmware rev #s are all over the map, and I don't think mixing and matching those is a good plan.

So, your best bet in general with the AKU3.3 stuff is
(1) really good backups before you go...
(2) make sure you are running the latest and greatest offical version
(3) if possible, when flashing, don't allow the carrier extended_rom stuff run when you hard-reset after install
(4) check it out, see if it seems to behave correctly - you *may* need to install some of the extded rom cabs just to get it to connect to evdo, it really depends on the carrier. If so, avoid "PP_" or "PT" ones at first, and see if you can get it up and running with EVDO access to test with the minimum (probably need to install Cert_ ones, Customize, IOTA, PP_IOTA, and RTPlugin_CDMA - but your files may be named differently!)

If it does work, you can try installing the ones you didn't until it fails, so we can find the bad one(s). If it does not work even with the minimum carrier stuff, then we're kinda SOL.

technole · #**372** (**permalink**) 01-31-2007, 11:00 PM

Quote:

Originally Posted by schettj

Right - radio firmware rev #s are all over the map, and I don't think mixing and matching those is a good plan.

So, your best bet in general with the AKU3.3 stuff is
(1) really good backups before you go...
(2) make sure you are running the latest and greatest offical version
(3) if possible, when flashing, don't allow the carrier extended_rom stuff run when you hard-reset after install
(4) check it out, see if it seems to behave correctly - you *may* need to install some of the extded rom cabs just to get it to connect to evdo, it really depends on the carrier. If so, avoid "PP_" or "PT" ones at first, and see if you can get it up and running with EVDO access to test with the minimum (probably need to install Cert_ ones, Customize, IOTA, PP_IOTA, and RTPlugin_CDMA - but your files may be named differently!)

If it does work, you can try installing the ones you didn't until it fails, so we can find the bad one(s). If it does not work even with the minimum carrier stuff, then we're kinda SOL.

Looks like its something in the VZW extended rom. Went back to 2.2, worked perfect. Went back to AKU 3.3 did not let external roms install. Still good.

Then installed only the following extrom cabs:

CAB: \Extended_ROM\VZWProvision_Signed.sa.CAB
CAB: \Extended_ROM\Apache_VZW_MMS3.0.6.24_20060124.CAB
CAB: \Extended_ROM\Customize_105201.sa.CAB
CAB: \Extended_ROM\VZWProvision.PPC400_2577MTM.CAB

The customize is the one that sets up the EV-DO. Phone averages 80mA while idle on EV-DO. Much better.

Still wish we had the idle arrows on the EV-DO connection like in the old AKU. But oh well, it working great now.

technole · #**373** (**permalink**) 01-31-2007, 11:44 PM

Also here is an explanation for these cabs:

CAB: \Extended_ROM\VZWProvision_Signed.sa.CAB <-- Sets up some signed certificate
CAB: \Extended_ROM\Apache_VZW_MMS3.0.6.24_20060124.CAB <-- MMS
CAB: \Extended_ROM\Customize_105201.sa.CAB <--Sets up phone settings/EV-DO/VZW Logo for IE/Handago Link...etc

CAB: \Extended_ROM\VZWProvision.PPC400_2577MTM.CAB <--Did not need this, Verizon Wireless Sync App

flash13 · #**374** (**permalink**) 02-01-2007, 08:56 AM

The cabs that are installed from the Alltel extended rom are:
CAB: \Extended_ROM\DisableDataCode.sa.CAB
CAB: \Extended_ROM\Link.sa.CAB
CAB: \Extended_ROM\PP_Rilphone_Apac_211707.sa.CAB
CAB: \Extended_ROM\Default_DPST.sa.CAB
CAB: \Extended_ROM\Default_Generic.sa.CAB
CAB: \Extended_ROM\PP_ImportReg_Apac_211711.sa.CAB
CAB: \Extended_ROM\Default_Settings.sa.CAB
CAB: \Extended_ROM\PT_BT_Apache_205200.sa.CAB
CAB: \Extended_ROM\PP_DataRetry_Apache_205200.sa.CAB
CAB: \Extended_ROM\axcess_shop.cab
CAB: \Extended_ROM\PP_Version_Apac_211711.sa.CAB

I might give AKU 3.3 another shot today with a hard reset once the custom install starts to see if that makes a difference.

**schettj** · #**375** (**permalink**) 02-01-2007, 09:11 AM

Quote:

Originally Posted by flash13

The cabs that are installed from the Alltel extended rom are:
CAB: \Extended_ROM\DisableDataCode.sa.CAB
CAB: \Extended_ROM\Link.sa.CAB
CAB: \Extended_ROM\PP_Rilphone_Apac_211707.sa.CAB
CAB: \Extended_ROM\Default_DPST.sa.CAB
CAB: \Extended_ROM\Default_Generic.sa.CAB
CAB: \Extended_ROM\PP_ImportReg_Apac_211711.sa.CAB
CAB: \Extended_ROM\Default_Settings.sa.CAB
CAB: \Extended_ROM\PT_BT_Apache_205200.sa.CAB
CAB: \Extended_ROM\PP_DataRetry_Apache_205200.sa.CAB
CAB: \Extended_ROM\axcess_shop.cab
CAB: \Extended_ROM\PP_Version_Apac_211711.sa.CAB

I might give AKU 3.3 another shot today with a hard reset once the custom install starts to see if that makes a difference.

It's a soft-reset you want to stop the custom installs, but basically sounds good.
The ones you probably want to avoid above are
PP_DataRetry_Apache_205200.sa.CAB
PP_Rilphone_Apac_211707.sa.CAB
DisableDataCode.sa.CAB
PT_BT_Apache_205200.sa.CAB
PP_Version_Apac_211711.sa.CAB

But like the verizon guy, you want to do as little as possible to get your EVDO working, then test it for the "no idle" issue, and if its OK you're good to go.

Good luck, it sounds hopeful!

**schettj** · #**376** (**permalink**) 02-01-2007, 09:15 AM

Quote:

Originally Posted by technole

Looks like its something in the VZW extended rom. Went back to 2.2, worked perfect. Went back to AKU 3.3 did not let external roms install. Still good.

Then installed only the following extrom cabs:

CAB: \Extended_ROM\VZWProvision_Signed.sa.CAB
CAB: \Extended_ROM\Apache_VZW_MMS3.0.6.24_20060124.CAB
CAB: \Extended_ROM\Customize_105201.sa.CAB
CAB: \Extended_ROM\VZWProvision.PPC400_2577MTM.CAB

The customize is the one that sets up the EV-DO. Phone averages 80mA while idle on EV-DO. Much better.

Still wish we had the idle arrows on the EV-DO connection like in the old AKU. But oh well, it working great now.

Woohoo!
Good work technote!

Wideawake, any chance we can update the main AKU3.3 rom thread with some heads up warnings about the Extended_ROMs from the carriers potentially causing issues (Sprint - "missing card" - Verizon, "never ending EVDO") and which CABS to avoid (or minimum to install)?

flash13 · #**377** (**permalink**) 02-01-2007, 11:10 AM

Quote:

Originally Posted by schettj

Quote:

Originally Posted by technole

Looks like its something in the VZW extended rom. Went back to 2.2, worked perfect. Went back to AKU 3.3 did not let external roms install. Still good.

Then installed only the following extrom cabs:

CAB: \Extended_ROM\VZWProvision_Signed.sa.CAB
CAB: \Extended_ROM\Apache_VZW_MMS3.0.6.24_20060124.CAB
CAB: \Extended_ROM\Customize_105201.sa.CAB
CAB: \Extended_ROM\VZWProvision.PPC400_2577MTM.CAB

The customize is the one that sets up the EV-DO. Phone averages 80mA while idle on EV-DO. Much better.

Still wish we had the idle arrows on the EV-DO connection like in the old AKU. But oh well, it working great now.

Woohoo!
Good work technote!

Wideawake, any chance we can update the main AKU3.3 rom thread with some heads up warnings about the Extended_ROMs from the carriers potentially causing issues (Sprint - "missing card" - Verizon, "never ending EVDO") and which CABS to avoid (or minimum to install)?

I'll second that - I'm trying to figure out what I should install from the Alltel Extended ROM (EVDO worked without doing anything).

I would like to find a way to have the connectivity arrows for the data connection go grey when they're dormant too, I would have a more "warm and fuzzy feeling" if there's a way to make that happen.

Nothing like updating the phone, reverting and updating again - especially when I've only had it for seven days now.

technole · #**378** (**permalink**) 02-01-2007, 11:57 AM

Quote:

Originally Posted by flash13

The cabs that are installed from the Alltel extended rom are:
CAB: \Extended_ROM\DisableDataCode.sa.CAB
CAB: \Extended_ROM\Link.sa.CAB
CAB: \Extended_ROM\PP_Rilphone_Apac_211707.sa.CAB
CAB: \Extended_ROM\Default_DPST.sa.CAB
CAB: \Extended_ROM\Default_Generic.sa.CAB
CAB: \Extended_ROM\PP_ImportReg_Apac_211711.sa.CAB
CAB: \Extended_ROM\Default_Settings.sa.CAB
CAB: \Extended_ROM\PT_BT_Apache_205200.sa.CAB
CAB: \Extended_ROM\PP_DataRetry_Apache_205200.sa.CAB
CAB: \Extended_ROM\axcess_shop.cab
CAB: \Extended_ROM\PP_Version_Apac_211711.sa.CAB

I might give AKU 3.3 another shot today with a hard reset once the custom install starts to see if that makes a difference.

I would avoid the PP/PTs to start. I have a feeling that DataRetry one might be the culprit, as i was looking at the xmls in the cabs to see what registry changes/programs that might cause the connection idle problem. Still looking further.

But yeah, everything is good so far. Nice to hold the 6700 again without it being warm every time.

TheRocoLoco · #**379** (**permalink**) 02-02-2007, 12:28 AM

I've been having a wierd problem with my calendar reminders only poping up for about 0.5 seconds an then disapearing.

supadoggie · #**380** (**permalink**) 02-02-2007, 07:26 AM

Quote:

Originally Posted by NitroSS

I found a problem today after I installed the AKU3.3

I subscribe to XM radio and I can listen online. But when I goto the page to login and start the stream it doesn?t bring up WMP and nothing happens. It wasn?t like this b4 I updated.

I was having this problem too with AKU3.3 and with Colonel's 3.3

The musicdock.com page uses asp so something is not able to translate it correctly....

good thing I have my Inno and only use my phone as a backup (when the Inno battery dies..) but it would be nice to get it working..

EDIT: after looking at the source page i see that this is the actual stream.. so it's an .asx stream..

Code:

GetStream_XM.asx?c=202&Key=XZDTOIQIXY407935955TYKYOHGXIK

i tried with both WMP and TCPMP and neither one is working..