Verizonguy's 3.5 Beta 2.1 (fixed usb, smartdialer, ##)

[mcq3000]

i dont understand the situation verizon guy. You obviously have a kitchen version of your version of the 3.5 rom as you are updating the rom with new betas and you can only do this with kitchen files as you are compiling new versions of the rom. If you cannot remember the exact changes you made to get smardialing working please can you just post the kitchen version of the rom. You can use the ppcgeeks ftp and upload it there, colonel and others have posted 3.5 kitchen versions of their roms, colonel did this just for me when I asked last week for a kitchen of 3.3 rom (thanks for that Colonel)

verizonguy, help us out please, the beta 2.1 you have, please let us get the kitchen version of the rom instead of the compiled one. PLEASE.

[technole]

Originally Posted by nobrakes

I think he used the custom mms in the kitchen oem folder. I've used that in my rom, it will send but i couldn't recieved. I just use the regular verizon mms cab and it worked fine on a clean rom. But I am having problem with vzwguy's rom because i can't remove the custom mms

Yep, MMS is hosed in this newer 2.1 rom even if i install the VZW one from extrom. Also looks like whatever vzwguy did, he definitely backed out the crossbow dialer skin and reverted to smartdialer 2.2 from 2.5.

[Sogarth]

Originally Posted by mcq3000

i dont understand the situation verizon guy. You obviously have a kitchen version of your version of the 3.5 rom as you are updating the rom with new betas and you can only do this with kitchen files as you are compiling new versions of the rom.

Uh... from everything I've read, that was true at one point, but is no longer. This is my read of the situation:

1. Had a kitchen. Made changes.
2. Used the kitchen. Made a ROM. Uploaded it to FTP.
3. Deleted the kitchen. Oops.
4. Downloaded the ROM from FTP.
5. Made further changes as per the earlier way of changing ROMs

So I'm pretty sure he's (I'm guessing he, based on "verizonguy") being honest, much to everybody's dismay (at not being able to look at the changes).

[ImCoKeMaN]

As far as i can tell here are the different files:
contactsdmenu.dll
ContactsPicker.dll
default.hv
DPadMenu.dll
phcanhtc.dll
phcanrc.dll
smartdialing.dll
user.hv

The default hive appears to have minor differences mostly the key# entries that have to do with the ## EPST features. The user.hv seems to have the no changes once converted to txt. I'm more interested in getting the smartdialer working at this point though so if anyone else can get those files from this rom to fix smartdialing with a kitchen OEM let us know. I've tried copying them to my device manually, but this did not work so far.

Just thought i'd give it a shot at getting the reconstruction started

[technole]

Tried fiddling with the MMS registry entries and re-installing MMS. No dice.

Somehow I noticed an MMS1 folder in the Inbox for some reason, and I can't get the SMS inbox to come back. ahh, not good. I'll keep looking.

[mcq3000]

Made further changes as per the earlier way of changing ROMs

Segarth, cooking your own rom always requires kitchen files. Hell the link to that tutorial you posted requires a 3.3 Kitchen rom. There is no way else currently to cook your own rom and make mods on the rom level without kitchen files. Hence if he is making rom mods he definately has kitchen files. I mean beta 2.1 is an updated rom file not some cab or regedit to apply to the old rom file he had earlier. If verizonguy is making new roms he definately has the kitchen files.

I can understand completely not remembering what patches or files you edited, hell I fell victim to this last week cooking my own 3.5 rom. But he can at least post the kitchen version of the rom

[Sogarth]

Originally Posted by mcq3000

Segarth, cooking your own rom always requires kitchen files. Hell the link to that tutorial you posted requires a 3.3 Kitchen rom. There is no way else currently to cook your own rom and make mods on the rom level without kitchen files.

Wow. I'm a total idiot - I posted the wrong link. You're right - the link I posted was, in fact, to a kitchen thread.

Okay. The proper link to Wideawake's method for modifying ROMs (which was used for the custom AKU 2.x ROMs) is this. That thread provides a set of tools to take apart an existing .nbf and put it back together with your own changes. If you read back to what verizonguy said, it required re-downloading a previously uploaded ROM. In addition, some of the really painful things that he (assumption again) did in the other thread where he first mentioned having fixed some of the issues refers to needing to use rgucomp to rebuild the registry hives, something that isn't necessary in the kitchen method.

I apologize for having misled you, but I do take verizonguy at face value, and believe that he genuinely doesn't have the kitchen he used to build his original AKU 3.5 ROM any longer.

[mcq3000]

well well, i was wrong on that then. My apologies. That way of deconstructing the nbf, I dont suppose there is any way to take verizonguys nbf, deconstruct it and throw in the kitchen oem files I want that I downloaded of the ppcgeeks ftp site as readint the instructions you posted it shows nothing concerning adding kitchen oem files

[Sogarth]

Originally Posted by mcq3000

That way of deconstructing the nbf, I dont suppose there is any way to take verizonguys nbf, deconstruct it and throw in the kitchen oem files I want that I downloaded of the ppcgeeks ftp site as readint the instructions you posted it shows nothing concerning adding kitchen oem files

Actually, I think that ImCoKeMaN over there might have already started on that with the list of files that changed.

But, unfortunately, they're completely different ways of working, so it's pretty painful trying to move from the hand-crafted ROM way to the ROM kitchen... The registry entries are probably going to be the most painful to figure out, since it would be matter of diffing large text files.

[technole]

Originally Posted by nobrakes

I think he used the custom mms in the kitchen oem folder. I've used that in my rom, it will send but i couldn't recieved. I just use the regular verizon mms cab and it worked fine on a clean rom. But I am having problem with vzwguy's rom because i can't remove the custom mms

I think I figured it out how to get the VZW MMS installer to work on top of that custom mms *ahem* crap that you can't uninstall automatically.

I deleted the MMS1 key from HKLM\Software\Microsoft\Svc\Inbox

then installed the VZW MMS, soft reboot. You'll notice the MMS inbox disappears. Go back in that key and change the new key that was created from MMS to MMS1 and everything works again. I was able to get MMS instantly from a Sprint user.

Although I would like it if someone can tell me how do you edit that menu when you hit send in p&v. the 'old' MMS still shows, but its really FLIX now, and the new MMS (pix) shows which is the right one.