Saridnours’ AKU 3.5+ Rom. Current 3/19 v3.5pr5 w/SP1

[gof]

Microsoft Reader is flat file. Everything is in \Program Files\Microsoft Reader. The only exception is I believe that during install a couple font files are installed into the \Windows folder (these can be moved manually and had to be if installed onto the Storage Card if I recall correctly). The reason I'd love it in ROM is it takes 2.3MB

[Raging Idiot]

cebain, cebain, cebain... WTF are you doing?

Really, what's going on, what's different on your setup?

Did you first install the latest ROM provided by your carrier before installing this ROM?
It was recommended a while back, not sure if it still applies, but I've heard no reason as of right now to believe it doesn't. <EDIT - found it no longer applies>

Also, just as a last resort troubleshooting process, try removing everything out of your startup. And don't use XCPUscalar...at least while troubleshooting...don't do anything different. That means, no setting up outlook, hotmail, and ACTIVESYNC...

FOR THE LOVE OF GOD - figure this out!

[saridnour]

cebain: what files are you loading from the extended rom (you said you didn't load anying in the extended ROM, then later say let the extended load so I am guessing you are loading from it and not copying anything back to it for storage)???
Be very careful of what is loaded from the extended ROM as many files contain bits that are older than the rom and will overwrite things. Have you tried to run VC without loading the extended at all?
If you want to PM me your VC cab or setup file, I can do a compare to what I have and see if this is another version. If it is and it is a valid copy of vc 1.6 retail (thats my leagle disclaimer) I could send you the exe I use and you could try that. I know it is working for others so I am really at a loss for what is happening on your unless its something from your extended or your VC build. Have you tired this on another build with a full install with same software config?

schwos: what is the phone ROM version? Are you placing calls in low coverage areas or are you seeing this everywhere. I know I have seen this in a lab at work or in the store sometimes but not out in public. When are you seeing screen lockups? What events preceed the lockup? What resolves the lockup? PR6 will be out about the same time as sp1 so it should be out within the week. Most of the changes are not around the radio, but wisbar update could help some locking issues possibly.

gof: Do you have a link for the latest rev? That or PM me the build you are using. Also if you have a dump of yout reg entres for it send it along as well. Since I will not be able to test too much so the more data I have upfrot the easier I could get it in (won't fit in my registered release so I can only get it in the PR release).

-saridnour

[xmind2006]

Hey Saridnour,

In regards to your bluetooth service pack, unless has had any negative affects, I really believe that the Priority 256 registry entry should be in the ROM. Reference:
http://www.ppcgeeks.com/a2dp-working-t2560.html

I really couldn't get my bluetooth to work until after I had that setting in place. (using MSI FS300)

If not no big deal to me, but others may need it also.

[jendand]

Originally Posted by cebain

After the update is complete, I disconnect the phone from the usb and perform a hard reset by pressing both soft keys and the reset key. Select "Y" and the phone resets.

Everything sounds right to me. Just to make absolutely certain there is no misunderstanding: the two soft keys are the ones on the front at the bottom with the minus signs (-) (I got this wrong at first!) and soft reset with the stylus. Then you're asked to select Y or N. You select Y and then the space bar. Right?

[cebain]

Ragin Idiot: I have no friggin clue what I'm doing here. But I was just coming to the thought that I may have skipped ROM versions. So now I've got to figure out how to fix that.

Currently running PR5 with SP1. NO EXT ROM (stopped from loading after hard reset).

ROM Version 2.11.20 WWE
ROM Date 4/4/06
Radio Version 1.10.00
Protocol Version SNAZ-40306
Ext Rom [BLANK]
Hardware 0041
blah blah blah

OS 5.1.195 (Build 15698SAR.3.5.pr5)

Is this an skipped ROM version issue? If so, how do I fix it?

Thanks Raging Idiot for your help.

[cebain]

saridnour,
Sorry I confused you. I've run the phone both with and without the EXT ROM (hard reset in between, of course). I've downloaded the file twice from Handango and also tried another from a guy at work. No go. For now, I'm pursuing the skipped ROM version possiblilty discussed in my previous post.

All in all, I've got a couple of people at work who want me to update their phone to work like mine (minus the MSVC issues). You're ROM has gotten their attention...GOOD WORK!

[cya]

cebain,

I'm on Verizon as well and running pr5 and beta 3 .... getting the same info on startup and had similar issues after my initial install. I did three hard resets in a row, put the phone into bootloader, and installed the latest Verizon rom, extended_rom, and phone. Three more hard resets and installed pr5, vzw extended_rom followed by beta3.cab and the phone has been flawless. I love this setup ... great work saridnour.

cya
ps still getting the same info at startup:
ROM Version 2.11.20 WWE
ROM Date 4/4/06
Radio Version 1.10.00
Protocol Version SNAZ-40306

[cya]

cebain,

I should add that on top of pr5, beta3, and complete vzw ext_rom I've also loaded MS DST patch, Wisbar Advance 2, Wisbar Advance Themes, Wisbar Desktop, psShutXP, WMA Profiles, MagiCall, Flash Player ACX7, Autostep (set to 520) .... currently running iphone_theme_ozankilic theme with operational slide lock and MSVC 1.6.

One thing I noted after the first attempted install was multiple copies of a couple of programs ... Total Commander for example. That's what prompted the multiple hard resets ... hope it works for you.

cya

[nuguy]

Cebain: are you sure you have VC 1.6 and not 1.5 as well the full version, not the upgrade, or tial version?

Also, I know you just said so, but just to cover all bases... when you are done w/ the upgrade, and do the hard reset (it appears you are doing that right), are you SURE you are soft resetting BEFORE the 'customization' (Extended rom) even BEGINS?

As soon as I see the countdown I get 'er done. I once did my soft reset about 2 seconds into the customizations and my phone ran like... well it didn't run well and I had to hard reset before I could really get going.


Sardinour: are you familiar with sk tools? The trial (same as retail file) has the limitation of only 6 entries in any of there lists are shown (really works enough for those of us that keep a tight machine). Anyway my point is particularly in the 'invalid registry enties/values'. It seems that there are some things in there that may run better if they were complete, or removed.

One of the first things I do w/ I load a rom (after a couple boots and real basic settings) is to run SKTools. I know it won't find things like the extra space in sp2, but it does show entries that seem to be referencing invalid objects. Specifically 'COM object registration info' and 'System drivers (built in and PCMCIA' as well as there seem to be some 'Empty keys'.

While I have already done some slight pruning, I would guess you may be able to do a little more, and that may add to stability, these are probably leftover from previous build revisions at MS or the original carriers tweaks.

You can find the latest at www.s-k-tools.com .