Round 2 Unofficial PPCK Build Updates 21027, 21028, 21040

[brol1k]

Originally Posted by Xanius

It's saying it's not a sanctioned rom because it's not released by the guys that make the kitchen. It was ported by someone else and they want to make sure you know that it's not their work so people don't ask them for help.

Yes I am aware of this, the fact that i click ok and let it continue, the phone flashes but it wont boot, it stays stuck in the splash and keeps soft resetting

[Getitnowmarketing]

Originally Posted by brol1k

Yes I am aware of this, the fact that i click ok and let it continue, the phone flashes but it wont boot, it stays stuck in the splash and keeps soft resetting

You either are selecting a bad oem(s) or have your device base pointing to the wrong core as it should point to vogue_core_drellisdee not to vogue_core for what ever device it is. You did create a new project selecting the vogue_6.1_drellisdee correct? If its not pointing to the right core its not getting the correct xip. The bt oems may be causing you trouble if its a herman/victor device. As I don't have a cdma diamond and IF & ONLY IF you have tried all the above steps replace the nk.fat and victor_21028.bin in the victor_core_drellisdee with the ones in the attachment and re-rar and rebuild 21028. Its possible I had a bad payload/xip on victor as I had no way to test it.

[ali3nfr3ak]

21040 sys and xip available here

http://forum.xda-developers.com/showthread.php?t=495871

[Getitnowmarketing]

Originally Posted by ali3nfr3ak

21040 sys and xip available here

http://forum.xda-developers.com/showthread.php?t=495871

Thanks am downloading now if all goes well look for 21040 soon.

[mr4r4n]

are the timebombs removed from all of the previously released builds? and even if they dont have them, when are most of the timebombs set to go off? on the experimental builds

[Getitnowmarketing]

Originally Posted by mr4r4n

are the timebombs removed from all of the previously released builds? and even if they dont have them, when are most of the timebombs set to go off? on the experimental builds

yes most were removed before I got them. 21032 Had july bomb

[brol1k]

Originally Posted by drellisdee

You either are selecting a bad oem(s) or have your device base pointing to the wrong core as it should point to vogue_core_drellisdee not to vogue_core for what ever device it is. You did create a new project selecting the vogue_6.1_drellisdee correct? If its not pointing to the right core its not getting the correct xip. The bt oems may be causing you trouble if its a herman/victor device. As I don't have a cdma diamond and IF & ONLY IF you have tried all the above steps replace the nk.fat and victor_21028.bin in the victor_core_drellisdee with the ones in the attachment and re-rar and rebuild 21028. Its possible I had a bad payload/xip on victor as I had no way to test it.

hmm I guess I forgot to mention im using a Herman, not a victor. Can I just rename the Victor_21028.bin to Herman_21028.bin?

[Getitnowmarketing]

Originally Posted by brol1k

hmm I guess I forgot to mention im using a Herman, not a victor. Can I just rename the Victor_21028.bin to Herman_21028.bin?

no xip and nk.fat/os.nb.payload are device specific. You must have a bad oem or missed something. Herman 100% works as its my main device. The ppck RDM and the older Bluetooth oems can cause no boot and data errors on herman and victor. Most likely your error is not generating the correct project and are using the stock ppck herman core and getting a flash with no xip inserted and thus no boot into windows

[brol1k]

Originally Posted by drellisdee

no xip and nk.fat/os.nb.payload are device specific. You must have a bad oem or missed something. Herman 100% works as its my main device. The ppck RDM and the older Bluetooth oems can cause no boot and data errors on herman and victor. Most likely your error is not generating the correct project and are using the stock ppck herman core and getting a flash with no xip inserted and thus no boot into windows

O I see now...Yes you were right I was not using the core u had put up.So i downloaded the one u put up and used that and still got the not a sanctioned rom warning and thought that couldve been why it was stuck on boot screen and soft resetting all the time so I didnt bother flashing my touch pro again untill the warning was gone....So I should be good if I use your core and still get the warning correct?

[Getitnowmarketing]

Originally Posted by brol1k

O I see now...Yes you were right I was not using the core u had put up.So i downloaded the one u put up and used that and still got the not a sanctioned rom warning and thought that couldve been why it was stuck on boot screen and soft resetting all the time so I didnt bother flashing my touch pro again untill the warning was gone....So I should be good if I use your core and still get the warning correct?

Yes the ppck team edits the shellresdll.mui to say the created by Drellisdee (your name here)& a product of ppckitchen.org on the settings about screen. Its throwing the not a sanctioned rom error because this text is not there. I could put it in but prefer not to as it's my base kit and not an official release by the ppck team. It in no way affects the rom other than the settings/about tab.