Apache WM6.1 Kitchen CE OS 5.2.19716 (Build 19716.1.0.0) - UPDATED 20080308

[thenig]

yo man could someone point me in the direction of a tutorial because a. I have searched; b. build os has a mind of its own and, c. rom building is new to me.....help ya boy out.

[dvrman123]

Originally Posted by thenig

yo man could someone point me in the direction of a tutorial because a. I have searched; b. build os has a mind of its own and, c. rom building is new to me.....help ya boy out.

Yes that would be awsome i need a tutorial as well i dont want to do it in the wrong order or maybe a step by step instructions which ever would be great

[gguruusa]

Originally Posted by thenig

yo man could someone point me in the direction of a tutorial because a. I have searched; b. build os has a mind of its own and, c. rom building is new to me.....help ya boy out.

It's really very easy:

1) Determine your bootloader version (power+notes+reset, hold for 2 secs, screen will be dark, read version # off of screen using a bright light)
2) If you're using Vista and have v1.00 phone, you will need to update to 1.02.
3) Download the kitchen installer
4) Install the kitchen. It will add a new PPCkitchen group to your start menu.
5) Run updater (you only need to download Apache kitchen, you will probably want to download ppcgeeks_oem.rar)
6) Run buildos
7) select an Apache selections.txt file in the file picker
select your bootloader version in the REV dropdown
9) select your carrier in the carrier dropdown
10) select any additional oems (start very light - these phones don't hold much
11) push play button
12) If you get "Error building file system", you need to go back to step 10) and uncheck some stuff
13) Put your phone in bootloader mode (power+notes+reset) and plug in USB cable
14) When RUU starts, ignore it's directions...just keep pressing next until it starts flashing.
15) If you have a 1.00/1.02/2.02 bootloader, and get and Error during flash, select NoID in the RUU dropdown and go back to step 11)
16) after the flash completes, Hard reset your device (two sofkeys + reset, screen will go white with "Clear memory?" question. Use slide out keyboard to respond)
17) your phone should boot. If it will not leave bootloader, download and run UNI_exitbootloader.exe
1 donate your savings/kids/time to those who have helped you.

[puff]

Originally Posted by guitardoc64

Yeah I checked it out with a search. It seems cool but winrar works well enough for me. Thanks for the info, and BTW I got the G'Reloc issue solved! Thanks GGuruUSA!!!

resolved g'reloc error? was it something simple? just curious... never seen a fix posted for it

Originally Posted by gguruusa

donate your savings/kids/time to those who have helped you.

how many kids can we donate?

[wezx]

Hi, I am running a 6.1 ROM I created with the kitchen...runs great. Do I need to run the Helmi6.1 Patch on the first page of this post? I can't find any answer to this??

[guitardoc64]

Originally Posted by wezx

Hi, I am running a 6.1 ROM I created with the kitchen...runs great. Do I need to run the Helmi6.1 Patch on the first page of this post? I can't find any answer to this??

From the first post:

Fix #1: Kitchen has been updated, you should not need this cab if you have updated the kitchen core.

[guitardoc64]

Originally Posted by PPC_N00B

resolved g'reloc error? was it something simple? just curious... never seen a fix posted for it

Mine was solved by unpacking the .rars and editing the selections.txt by removing the .rar references.

[mastersm]

Originally Posted by gguruusa

It's really very easy:

1) Determine your bootloader version (power+notes+reset, hold for 2 secs, screen will be dark, read version # off of screen using a bright light)
2) If you're using Vista and have v1.00 phone, you will need to update to 1.02.
3) Download the kitchen installer
4) Install the kitchen. It will add a new PPCkitchen group to your start menu.
5) Run updater (you only need to download Apache kitchen, you will probably want to download ppcgeeks_oem.rar)
6) Run buildos
7) select an Apache selections.txt file in the file picker
select your bootloader version in the REV dropdown
9) select your carrier in the carrier dropdown
10) select any additional oems (start very light - these phones don't hold much
11) push play button
12) If you get "Error building file system", you need to go back to step 10) and uncheck some stuff
13) Put your phone in bootloader mode (power+notes+reset) and plug in USB cable
14) When RUU starts, ignore it's directions...just keep pressing next until it starts flashing.
15) If you have a 1.00/1.02/2.02 bootloader, and get and Error during flash, select NoID in the RUU dropdown and go back to step 11)
16) after the flash completes, Hard reset your device (two sofkeys + reset, screen will go white with "Clear memory?" question. Use slide out keyboard to respond)
17) your phone should boot. If it will not leave bootloader, download and run UNI_exitbootloader.exe
1 donate your savings/kids/time to those who have helped you.

I'm running Vista and Bootloader 1.00 and all seems to be working. What problems are normally associated? Also how do I update to 1.02, or is there a better bootloader?

[Trident]

I've started seeing the dreaded 'You have to resync everything after a change in the server' error again. It appears that very few others are seeing it.
Does anyone ever see anything like this with the newer/older 19213 kitchen?
I like my config, but I hate that I keep having to resynch for half an hour and then reset all my custom ringtones.

[guitardoc64]

Originally Posted by Trident

I've started seeing the dreaded 'You have to resync everything after a change in the server' error again. It appears that very few others are seeing it.
Does anyone ever see anything like this with the newer/older 19213 kitchen?
I like my config, but I hate that I keep having to resynch for half an hour and then reset all my custom ringtones.

I had it with the older kitchen builds. Most recently when I got my Touch and synced it, it happened to my Apache. I personally think it's an activesync issue, not a ROM issue.