Re: Round 2 Unofficial PPCK Build Updates 21027, 21028, 21032
 

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

Re: Round 2 Unofficial PPCK Build Updates 21027, 21028, 21032
 

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.

Re: Round 2 Unofficial PPCK Build Updates 21027, 21028, 21032
 

21040 sys and xip available here

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

Re: Round 2 Unofficial PPCK Build Updates 21027, 21028, 21032
 

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

Re: Round 2 Unofficial PPCK Build Updates 21027, 21028, 21032
 

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

Re: Round 2 Unofficial PPCK Build Updates 21027, 21028, 21032
 

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

Re: Round 2 Unofficial PPCK Build Updates 21027, 21028, 21032
 

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?

Re: Round 2 Unofficial PPCK Build Updates 21027, 21028, 21032
 

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

Re: Round 2 Unofficial PPCK Build Updates 21027, 21028, 21032
 

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?

Re: Round 2 Unofficial PPCK Build Updates 21027, 21028, 21032
 

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.

Re: Round 2 Unofficial PPCK Build Updates 21027, 21028, 21032
 

ok gotcha on that..ill re cook and come back with any known problems, and thank u very much for the help

Re: Round 2 Unofficial PPCK Build Updates 21027, 21028, 21032
 

Thank you for keeping this whole website up to date!
Like it or not,but soon as I open paypal accnt.,I will definetly donate :headbang:

Re: Round 2 Unofficial PPCK Build Updates 21027, 21028, 21032
 

21040 is up!!!

http://pic90.picturetrail.com/VOL225.../359489674.jpg

Re: Round 2 Unofficial PPCK Build Updates 21027, 21028, 21040
 

thanks for the updates...Now here is my feedback for 21028 sys...I cannot for the life get HTC volume or the rhodium volume app to work with the volume keys, instead the volume keys are used for scroll up/down like on a Dpad. And the other problem is the battery indicator is showing the wrong battery info on the taskbar unless I use a custom taskbar that tsowen did, and the last problem is the G sensor isnt working on tf3d2...any help on this maybe guys?

Re: Round 2 Unofficial PPCK Build Updates 21027, 21028, 21040
 

Post your selections.txt as an attachment and I'll look at it I'm using the old nov oem's still with no problems. Its not in any way sys related its the oems.

Re: Round 2 Unofficial PPCK Build Updates 21027, 21028, 21040
 

OK here it is,and most of the oems I use are my own that I put in User_OEM folder

Re: Round 2 Unofficial PPCK Build Updates 21027, 21028, 21040
 

Try leaving out the HTC_Rhodium_Menu_Enhancement, TF3D TP2, & TouchResponse_v0_3_2.

I've enclosed working htc vol and gsen calibrator for regular manila. They may not be compatible as is with TP2 manila. Also are some untested TP2 apps that may be compatible if you choose to use the newer manila. Let me know as it seems most of the problems may be due to the Tp2 manila.

Re: Round 2 Unofficial PPCK Build Updates 21027, 21028, 21040
 

time bomb removed from the new sys? one question i had, i downgraded to BL 2.02 from 2.05 and it gives me more room for customizing the rom, however i noticed i get more glitches now, and when i had 2.05 i installed all the apps instead of including it in the rom, the most noticeable problems being 10 second gap from ringtone on SD card and no working activesync and generally overall more prone to crashes, could the 2.02 be the culprit if so is there any version that you would recommend? Edit: also constant beeps and i mean like the phone will be in standby and beep like something happened but no messages, i am going to try the newest build

Re: Round 2 Unofficial PPCK Build Updates 21027, 21028, 21040
 

Yes the S000 in shell32.exe is patched to remove timebomb. As far as bootloaders i've only had 1.00 1.02 and 2.02 bootloaders and never downgraded one. I currently have a 1.00 & 2.02 devices now and dont seem to have those issues but then again I haven't recived a call on apache in over 1.5 years.

Re: Round 2 Unofficial PPCK Build Updates 21027, 21028, 21040
 

lol lucky you, i love my apache dont get me wrong i would love to get an upgrade though dunno if verizon will have anything new by the time my contract is up, cuz imm dyin for an upgrade, just a few more months to go](*,)

Re: Round 2 Unofficial PPCK Build Updates 21027, 21028, 21040
 

just flashed 21040 going to install and test it out, has the rev A icon again but lol its cool to see even if it dont have it, going to install my usual apps and report back

Re: Round 2 Unofficial PPCK Build Updates 21027, 21028, 21040
 

OK now the tp rom is in effect, everything is working as it should, I thank u very much.Now im building for the victor using 21040...well appears that it is getting stuck in boot screen again, I tried building with tf2d2 and all its stuff, and w/o them and still...I used the updated core for the new sys and it hangs on boot screen?

Re: Round 2 Unofficial PPCK Build Updates 21027, 21028, 21040
 

Brol, take the nk.fat and the victor_21028.bin from a page or 2 back from the attach I posted and overwrite the ones in victor core. After that inside the core where you have the xip, rom, and sys folder ctrl a select all and re-rar it. Try the 21028 build and tell me if it works. The victor is the only device I dont have so its not tested. If it works I'll update the victor core tonight. Btw were you able to get the TF2 apps working with vol and gsensor?

Re: Round 2 Unofficial PPCK Build Updates 21027, 21028, 21040
 

I tested 21040 with pagepool set to 12 .Works very good for me.(ROM packed with 75 applications+M2d).Everything stable and fast.Battery life is good too.

Re: Round 2 Unofficial PPCK Build Updates 21027, 21028, 21040
 

The vogue page pool on 21040 I set to 24mb in the xip. Did you change it after the fact to 12 with the standalone changer on the nbf? Thanks for the report.

Re: Round 2 Unofficial PPCK Build Updates 21027, 21028, 21040
 

ok I downloaded 21028 and the core and it works fine w/o the attached nk.fat and bin. And on the Touch pro, I did get the volume to work with the one u supplied, as far as the Gsensor on tf3d2, no it doesnt work still, but it does work on any other app, I hear its an issue with the beta even with ppl who dont have it cooked in. and also I oemd the battery app u supplied and it did fix it, but for some reason if i put in autorun/sd autorun it messes it up after it does its soft reset...maybe the oems supplies in ppck is just messed up?

Re: Round 2 Unofficial PPCK Build Updates 21027, 21028, 21040
 

You cant have both 1% battery on title bar and fastcharge as fastcharge doesnt support 1% on title. Did you use the old victor core and try to build 21040 or was it the new one i updated yesterday?

Re: Round 2 Unofficial PPCK Build Updates 21027, 21028, 21040
 

ok for the battery issue, I dont use 1% battery increments, but I can take out fast charge as I dont care much for it. And as for the victor, I used the updated core u posted for 21040, but once i go back to 21028 sys it works perfect w/o putting in the new files u gave me to add.

Re: Round 2 Unofficial PPCK Build Updates 21027, 21028, 21040
 

Yes.In the kitchen I selected "default pagepool"
Before flashing opened standalone changer and changed ruu_signed.nbh pagepool to 12

Re: Round 2 Unofficial PPCK Build Updates 21027, 21028, 21040
 

I just flashed with os 21040 and under memory it shows 93.40 mb, whereas under 20931 I have 115.43 mb - with the same stuff loaded in both runs. I have pagepool set at 28 with os 20931. Any ideas?

Re: Round 2 Unofficial PPCK Build Updates 21027, 21028, 21040
 

flashed 21040 and all the previously posted problems have so far disapered you are the man :headbang:drellisdee !!:headbang:

Re: Round 2 Unofficial PPCK Build Updates 21027, 21028, 21040
 

That "28" is actually a 2mb pp. Stock a vogue has 12mb with 105mb in mem under settings about. The stock kitchen changer doesnt function properly on vogue. Test for yourself on 20931 and build a rom and try to change the pp on the .nbh and it will show you. The vogue core i put out has a 24 mb pp set in all xips which should read 93.4 on settings about 28 would be 89.4. Use default pp and change the ruu_signed.nbh pagepool with standalone pp changer

Re: Round 2 Unofficial PPCK Build Updates 21027, 21028, 21040
 

Found little bug in 210240.Battery % not working properly.My CDMA_RSSI_PPC.dll with blue antenna and signal bars is white for some reason..
Timezone not changing automaticly
I think it has something to do with GSM-CDMA difference
The worst part I dont remember of having this issue in the morning..and I didnt saved that ROM to make sure...this one is totally different.May be there is nothing wrong with 210240,,

Re: Round 2 Unofficial PPCK Build Updates 21027, 21028, 21040
 

so are you saying that the 115.42 is really 89.4 that shows up on the 20931?

Re: Round 2 Unofficial PPCK Build Updates 21027, 21028, 21040
 

I downloaded the 21040 link but in that folder I don't see a SYS_21040_96DPI_0409

However, there is a 21032 one...did you maybe accidentally put in the 21032 instead of a 21040?

File Contents:

Re: Round 2 Unofficial PPCK Build Updates 21027, 21028, 21040
 

No the 115.42 means you have a 2mb pp on vogue.

Use the 21032 resources. I didnt update as almost nothing changed

Re: Round 2 Unofficial PPCK Build Updates 21027, 21028, 21040
 

This is an interesting project. I have a Sprint Touch Diamond.

I was able to download and build with 21028 and all works fine.

I downloaded 21040 and I get stuck at the screen with the protocol, radio and rom version in red ... any thoughts on resolving the issue.

A suggestion or request - can you update the version of nk.exe in your xip so that the rom version goes from 1.0x to 2.00 ?

Best regards,
-boggsie

Re: Round 2 Unofficial PPCK Build Updates 21027, 21028, 21040
 

Fixed victor core for 21040 please redownload. Boggsie do you have a newer stock shipped.exe other than sprint test which gave me xip problems with the old 21040? If so PM me and I'll instruct from there and can build a new victor core with a 2.0x. This is a test boot.rgu for boggsie and is pass protected(pass sent in PM). Enclosed and also pass protected is a new test core built from the new sprint test payload. Let me know if this works.

Re: Round 2 Unofficial PPCK Build Updates 21027, 21028, 21040
 

Thanks so much for the quick reply!

ygpm

Re: Round 2 Unofficial PPCK Build Updates 21027, 21028, 21040
 

Thanks for the quick reply and for the custom service !

There is a new core in the first post.
There is an updated core (2.00 nk.exe) in the reply to me in the thread. - password protected
There is an updated boot.rgu in the reply to me in the thread. - password protected

1st try ... the new core in the first post. - no boot
2nd try ... the new core in the first post w/ new boot.rgu. - no boot
3rd try ... the custom core (2.00 nk.exe). - no boot
4th try ... the custom core (2.00 nk.exe) w/ new boot.rgu. - no boot

ygpm

Best regards,
-boggsie