PPCGeeks - Apache WM6 Kitchen CE OS 5.2.1908 (Build 18508.0.7.0)

PPCGeeks (http://forum.ppcgeeks.com/index.php)

- HTC Apache Development (http://forum.ppcgeeks.com/forumdisplay.php?f=53)

- - Apache WM6 Kitchen CE OS 5.2.1908 (Build 18508.0.7.0) - UPDATED 20071217 (http://forum.ppcgeeks.com/showthread.php?t=11074)

Quote:

Originally Posted by BelligerentOC (Post 117531)

This is from way back on Page 9. I cant figure out for the life of me how to do this. I found the 3 types of RUU in the upgrade folder. When I click on the folders, I can only get ROMupgradeut.exe to load. It gives me the first screen, welcoming me to the software update utility. I hit next, and it then checks the info on the 6700. Then it crashes. This exact thing happens with both newbootloader and the plain RUU. When I try to NoID RUU, the only thing I can get to run is APACUpgradeUt_noID.exe....

You should not even be in the upgrade folders. If you notice at the top of BuildOS, you'll see the option to change the RUU. By default, it should be on Standard. This BuildOS is designed to be used by anybody, and everybody. The only reason you would even need to actually go into the folders is if you wanted to add an OEM or something. Everything else can be done from within the program itself.

Quote:

Originally Posted by BelligerentOC (Post 117531)

This will go until the screen where it is supposed to say what version everything is on my phone and what it will be upgraded to. However, there are just blanks where this data should be...

If you run the RUU correctly from the BuildOS, you may notice blanks sometimes. This is normal. If you are flashing with this kitchen, it should say WM6_AKU0.7.0 or something similar. That may be all you see, as long as you see something like that, it's ok to proceed.

Are you trying to do this on a Vista box? I had the same problem. In fact, I couldn't get my phone out of bootloader mode.

I then installed all the kitchen stuff to my XP laptop, moved the phone over to it, and everything went fine. Actually, it's gone fine 4 or 5 times now.

Quote:

Originally Posted by BelligerentOC (Post 117610)

I know how to put it into bootloader, I just cant get anything to go once I am in it...

Revert back from Bootloader 2.5 ?

Quote:

Originally Posted by gguruusa (Post 116713)

Yes, but you probably hosed yourself with the 3.3 update. Check your bootloader version. If it's 2.04/2.05, you did yourself a little harm. You can still use the kitchen, you just can't burn as much stuff into your ROM. There's a thread somewhere here about reverting your bootloader to 2.02 - if you like the kitchen, I suggest you give it a try.

Firstly, thanks to all that have contributed here. The comprehensive nature of everything I've seen/read is amazing.

I think I've read through all the theads here and can't find the info I think I need. Can some one point me to the posts dicussing how to revert back to bootloader 2.02.

A few days ago I "updated" to AKU 3.3
Bootloader currently registers 2.5

Looking for tips on how to get my 6700 in the best state to begin PPC-BuildOS. Any direction/help would be greatly appreciated.

thanks,

Found my answer at http://forum.ppcgeeks.com/showthread.php?t=7820

Just downloading the 11/08 edition, hope that has corrected the issue that cant invoke the htc camera from the mms applet, or that to revert to full working 3.0.6.24
Another hope that fix that shorcuts are erraticaly keep on windows folder, so that cant view in programs group, just happened to flash lite and added oems
adding mms 3.0.6.24 generate a duplicate file error, but this oem doesnt carry this file! (player_middlelayer.dll already exists)
A Error generating ROM as final message (whats annoying!!)

MMS 3.0.6.24 does indeed include player_middlelayer.dll. It's a hidden file so make sure you have file explorer set to see hidden files in windows.

Simply move the file from MMS 3.0.6.24 OEM to your Patches directory.

Quote:

Originally Posted by schettj (Post 117436)

Yep, but, since all the wallpaper files have to get copied into their final location anyway (\Windows\gfx) you can just copy your files into that location after you flash your rom... or just name the files the same as the ones in the s2ul OEM, and drop them in Patches before you build your rom, and yours will overwrite the rom-versions and get copied into the right place on the hard reset.

Make sense?

Edit: Don't change the registry, that points to where a bunch of images used by S2UL are kept. Including the wallpaper.

Makes perfect sense. I didn't realize that there were also things in \Windows\gfx.

Quote:

Originally Posted by Snager (Post 117449)

I think you should just install S2U2 instead of adding it as OEM ....all the images for S2U2 take up twice the space ...one in \windows and other one in \Windows\gfx ... with the extra space you save, you can add other OEM packages

what i do is i keep all the files that are custom to me....like images and links in my storage card and after a flash or hard reset i just copy/paste them over to My Device path example for S2U2 i would keep my custom wallpaper.jpg in a folder

\Storage Card\BackUp\Program Files\S2U2\gfx\wallpaper.jpg so when it comes time to copy everything all i do is highlight everything in BackUp then copy then paste to My Device ...and your somewhat back to what you had before the Hard reset or flash

After further consideration, I think I'm going to do just this. Of course, this means that I need to make a new ROM without S2U2. Well, I haven't flashed my ROM in over 16 hours, so I guess its about time...

Thanks for all the help, both of you.

Quote:

Originally Posted by cjbreisch (Post 117709)

Well, I haven't flashed my ROM in over 16 hours, so I guess its about time...

LOL - that's how I feel. Constant reflashing and re-customizing.
Ahhh, the downside of wanting every little update and tweak to be perfect.

Quote:

Originally Posted by Gervy (Post 117719)

LOL - that's how I feel. Constant reflashing and re-customizing.
Ahhh, the downside of wanting every little update and tweak to be perfect.

Me too. Going on the same ROM since tuesday and a lot has changed since then!

Quote:

Originally Posted by cjbreisch (Post 117709)

Better than an SD card, is to use your ExtROM for S2U2's graphics files. If you put them on the ExtROM, and make an OEM to redirect S2U2s gfx location registry value to there, you'll be all set to go without wasted space or a copy. (you can't do the same thing with your SD card because SD cards aren't always mounted when the system exits standby mode - ExtROM is).

Quote:

Originally Posted by gguruusa (Post 117763)

Pardon my confusion. Are you saying that I can put S2U2 in my ROM, but redirect where it looks for the jpegs to a folder in my Ext Rom?