Apache WM6 Kitchen CE OS 5.2.1908 (Build 18508.0.7.0) - UPDATED 20071217

[luv2chill]

Originally Posted by daveedem

tried that.. they are prompting me for a password to unrar it.

You opened the wrong rar file. PPCGeeks_OEM.rar is what you're looking for. The skins are in folders beginning with "Skin-Phone-"

[Schwartz]

How Would I Go About Deleting the windows default theme so its not it a ROM or cant I do this?

[lightbiter]

o.k. this maybe a dumb question but i noticed that there is an option at the top to choose wm5 so just for kicks i tried it nothing happened it just installed wm6 so how do you implement this option i'm sure it's something simple that i'm not getting or it's spelled out somewhere but i'm not finding it any help would be very appreciated
thanks

[jrs]

Originally Posted by luv2chill

Fact is, your bootloader protects you from yourself--and the bootloader does not get touched during any of these procedures. If you screw something up all you need to do is reflash your original carrier ROM (or whatever known working ROM you might have saved to your hard drive).

You may have answered my question.

Does this mean that the bootloader won't change?

I am in bootloader 1.0 now, ready to cook and flash but the only thing stopping me is the fear of not being able to go back to WM5 the way it is now, if I have to.

[elmillero]

Y'all are the BOMB!!!

[daveedem]

Originally Posted by luv2chill

You opened the wrong rar file. PPCGeeks_OEM.rar is what you're looking for. The skins are in folders beginning with "Skin-Phone-"

you are right... thanks. trying that now. but damn thing with vista and RUU... it's really pissing me off as I'm not around my XP machine.

Any ideas on that one?

[luv2chill]

Originally Posted by jrs

You may have answered my question.

Does this mean that the bootloader won't change?

I am in bootloader 1.0 now, ready to cook and flash but the only thing stopping me is the fear of not being able to go back to WM5 the way it is now, if I have to.

Correct--if you're using this kitchen environment along with the flashing tools built into it then there is no chance that your bootloader version will change. The only people who got an unwanted bootloader update are people who flashed the latest official (AKU 3.3) ROMs from Verizon and Bell Mobility. If you stay away from those then your bootloader will not be touched.

[luv2chill]

Originally Posted by daveedem

you are right... thanks. trying that now. but damn thing with vista and RUU... it's really pissing me off as I'm not around my XP machine.

Any ideas on that one?

Vista is still somewhat mysterious... but I think these are the key things:

1. WMDC 6.1 (maybe reinstall it if already installed)
2. Make sure sync drivers have a 2007 date (look in device manager)
3. Turn UAC off... also make sure your user account has administrator-level access.
4. Either put Apache in bootloader mode before flashing, or go to Start->Settings->Connections tab->USB to PC->uncheck "Enable Advanced Networking"
5. Use the appropriate RUU to flash based on your bootloader--Standard for bootloaders 1.00, 1.02, and 2.02 and x.04+ for 1.04, 2.04, and 2.05.

If it still doesn't work then you may need to double-check things like USB ports, cables, hubs, and other "hardware" type stuff.

[jrs]

Originally Posted by luv2chill

Correct--if you're using this kitchen environment along with the flashing tools built into it then there is no chance that your bootloader version will change. The only people who got an unwanted bootloader update are people who flashed the latest official (AKU 3.3) ROMs from Verizon and Bell Mobility. If you stay away from those then your bootloader will not be touched.

Thanks, man. And thanks for the quick response.

You guys are something else.

I know how I'm spending my Sunday...

[daveedem]

UGH...

turned off UAC again.
have 6.1
did NOT use Modaco's RUU fix.

swapped my USB connection with an alternative.

It started flashing

. I swear I've been f'ing with this for 1 hour.

I wish I knew what the ulimate answer is besides reboot, reboot, reboot.

back to customizing...