Round 2 Unofficial PPCK Build Updates 21027, 21028, 21040 - Page 12

mr4r4n · #**111** (**permalink**) 03-27-2009, 07:31 PM

flashed 21040 and all the previously posted problems have so far disapered you are the man

drellisdee !!

**Getitnowmarketing** · #**112** (**permalink**) 03-27-2009, 07:49 PM

Quote:

Originally Posted by fredcatsmommy

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?

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

**vin255764** · #**113** (**permalink**) 03-27-2009, 08:07 PM

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,,

fredcatsmommy · #**114** (**permalink**) 03-27-2009, 10:53 PM

Quote:

Originally Posted by drellisdee

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

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

computerjunkie · #**115** (**permalink**) 03-28-2009, 12:40 AM

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:

Code:

Readme.txt
SYS_21032_96DPI_0409.rar
SYS_21040_192DPI_0409.rar
SYS_21040_Common.rar
WM6.1_96DPI_QVGA_Drellisdee_21040_0409.txt
WM6.1_192DPI_VGA_Drellisdee_21040_0409.txt

**Getitnowmarketing** · #**116** (**permalink**) 03-28-2009, 07:25 AM

Quote:

Originally Posted by fredcatsmommy

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

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

Quote:

Originally Posted by computerjunkie

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:

Code:

Readme.txt
SYS_21032_96DPI_0409.rar
SYS_21040_192DPI_0409.rar
SYS_21040_Common.rar
WM6.1_96DPI_QVGA_Drellisdee_21040_0409.txt
WM6.1_192DPI_VGA_Drellisdee_21040_0409.txt

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

**boggsie** · #**117** (**permalink**) 03-28-2009, 08:23 AM

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

**Getitnowmarketing** · #**118** (**permalink**) 03-28-2009, 12:16 PM

Quote:

Originally Posted by boggsie

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

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.

**boggsie** · #**119** (**permalink**) 03-28-2009, 02:53 PM

Thanks so much for the quick reply!

ygpm

**boggsie** · #**120** (**permalink**) 03-28-2009, 03:16 PM

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