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

[ImCoKeMaN]

Thanks schettj, I updated the first post with the link to the wiki.

I uploaded the broken nk.nbf to the ftp at:
ftp://up.ppcgeeks.com/Apache/ImCoKeMaN/broken3.5nk.zip
[The only difference really is the reg entry for ms2_usbfn.dll]

I'm currently building a rom using the kitchen with the 2 patched dll's provided by helmi. It looks like it's fixed the bluetooth issues (including VC?). It hasn't fixed the USB, but it might be nice to have a common ground so i've uploaded them as packages for the kitchen. The packages to add are in my subdirectory on the FTP:
wavedev.dll_helmi.zip (for the OEM folder replace wavedev.dll)
e658c544-26bf-45ac-a458-2044a5d1e698.zip (for the OS folder)

I tried a different RNDIS/USB serial switcher before without success and unfortunately this one still isn't USB syncing for me.

I still don't think i get the RAM address checking that Helmi does and i sure don't know how to patch the dll, but i'm very confident that if helmi can find the time to patch the ms2_usbfn.dll that this USB issues would be resolved. In the meantime i'm gonna continue trying whatever I can find though.

[finster869]

Originally Posted by ImCoKeMaN

I'm currently building a rom using the kitchen with the 2 patched dll's provided by helmi. It looks like it's fixed the bluetooth issues (including VC?).

So far, it looks like it did fix the VC/blue tooth issue!

[helmi_c]

guys... I forgot to ask/mention AKU3.5 hv problem with smartdialing function, does u guys hv problem with smartdialing/phonecanvas?

[HKEY_LOCAL_MACHINE\Security\Phone\Skin]
"Ext"="PhoneCanvas.dll"
[HKEY_LOCAL_MACHINE\Software\Microsoft\DialParser]
"DLL-OEM"="PhoneCanvas.dll"

In any of AKU3.5, smartdialing is causing problem... what about apache device?

[ImCoKeMaN]

Yes the smartdialing is broken for the apache as well. I haven't looked too deeply into it though, because i had read it wasn't working for any aku 3.5. Unfortunately our apache doesn't fix the problem.

[eyeballz]

I think you will have more people running this rom now that the BT works with the patch. I for one am looking forward to 3.5+


thanks again, let me know if you need anything as I am running this rom for the time being as primary rom.

[ImCoKeMaN]

I feel like we're so close to getting this, but i just can't quite get there. I tried looking over all the memory addresses and i can't find the conflicts. I know that ms2_usbfn.dll can exist in the rom without it causing issues and the associated usbfn registry entry is fine except for the MemBase 40600000. Once that line is put in the phone becomes completely unstable. However this entry has made it start to be recognized by activesync for me. It never get it synced though cuz it always locks up.
This makes me think that the membase address is causing the conflict.

Also as i think i mentioned earlier i tried replacing the ms2_usbfn.dll driver and reg entries with one for usbfndrv.dll from another rom package also without success. The main difference there being the IOBase was AE60000. I also tried AE600000 for the membase with ms2_usbfn, and it didn't lock up, but it still did not work.

The only other entry i see with a IO/membase near these is AE60000 is the QCT1.DLL driver which i tried before(edited it to point to the QCT.DLL). the USB is detected when that driver is used, but that is for diagnostic mode. Then i tried taking out that package completely incase that was the conflict, but that didn't have any effect either.


For me the usbswitch mode hasn't worked either. I guess some of this info might have been said before, but hopefully this will consolidate the info and what has been tried a little. If anyone else has suggestions or tried other ideas i'm interested to know what the results were. I guess one option is to hope helmi can find time to patch the ms2_usbfn.dll, but it would be great if we can figure this out so we can give back to him as well

[sfaure03]

Im? You just need a copy of ms2_usbfn.dll ? Right?

If so lemme know, though I tried it, and it did not stabilize the app.

I will fetch one anyway and upload it.

[sfaure03]

actually, likely you can use this trick to get it yourself. Use the Wide's original "extract a rom" program. that will make a dump of you're rom.

if you read carefully the imgfs/viewfs programs automagically also extract and BUILD the dll's for you.

cd dump
cd ms2_usbfn.dll
dir ms2_usbfn.dll

There she blows. use it just like the other "conflicting dll's from helmi.

good luck. Like I said i tried this but to no avail. Of course there may be other things you did to the kitchen trying to track this down that I have no idear how to "undo"

[ImCoKeMaN]

Yes i've already tried copying just the dll over as well, but thanks for another idea which i hadn't mentioned. I think those other conflicting DLLs of helmi's were actually patched not just extracted, but i could be wrong. I've also used those imgfs tools to get the dump_MemoryMap.txt to try to look for conflicts.

The kitchen that i posted to the FTP has actually only had a few minor changes to get 3.5 to work with the apache at this point. This was in hopes that it wouldn't have caused more problems than it was fixing.


Update: Didn't get too much time with USB tonight, but i did fix the timesync issue and posted an nk.nbf of a test version using sprint customizations. (if anyone is daring please try this as i'm having PCS vision issues, but i'm unsure if they are related at this point) For these updates please check the first post.

[vboyz103]

I just grabbed the R2 from FTP server yesterday and seems very stable and ActiveSync through bluetooth works like a charm. The USB is not yet working as usual but I'll settle for Bluetooth.

Put my OEMs on there and now it is my main ROM.

Thanks.