View Single Post
  #134 (permalink)  
Old 05-11-2008, 09:18 PM
gguruusa's Avatar
gguruusa
Deep Thinker
Offline
Location: Mountain top
 
Join Date: Jan 2007
Posts: 3,252
Reputation: 4726
gguruusa should be added to the payroll for their contributionsgguruusa should be added to the payroll for their contributionsgguruusa should be added to the payroll for their contributionsgguruusa should be added to the payroll for their contributionsgguruusa should be added to the payroll for their contributionsgguruusa should be added to the payroll for their contributionsgguruusa should be added to the payroll for their contributionsgguruusa should be added to the payroll for their contributionsgguruusa should be added to the payroll for their contributionsgguruusa should be added to the payroll for their contributionsgguruusa should be added to the payroll for their contributions
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Re: Cook your own Custom Touch ROM

Quote:
Originally Posted by rstoyguy View Post
As a guess, I'm thinking that it has something to do with the bootup images and where the entry point is. The rom(s) are made from the ppckitchen. I'm thinking that your kitchen does a little more with the boot up images, as the command line kitchen won't flash properly. I have been searching for some enlightenment on why this happens.
Once we flashed the alltel rom, our methods quit working. Today I built a rom with the ppckitchen. This one I selected the same boot splash, and limited the stuff I added. Then I could flash a command line kitchen to my phone. Before it would hang at the bootsplash screen and never got to display the radio/rom info.
The methods are taking omj's rom, prepit, buildos, buildit. even with no editing it wouldn't work before.
Now I'm really confused...are you saything that flashing the stock alltel rom starts the problem, then flashing something (any rom?) from ppckitchen's kitchen cures it?
__________________
Grammar: The difference between knowing your shit and knowing you're shit.