Round 2 Unofficial PPCK Build Updates 21027, 21028, 21040

[Xanius]

I couldn't get any of these to boot on my vogue. Followed directions exactly and it was a no go, always got stuck on second splash screen.

However, doign the same thing with 21018 worked just fine, so I'm happy.

[Whosdaman]

Originally Posted by Whosdaman

Dre...I'm trying to help you dude, the 21032 is screwed up for some reason...

Everyone is having the same problem, 028 and 027 work perfect, but 032 is getting stuck

I love your work dude, and I'm trying to help ya out here

Just incase you miss it ^^^

[Getitnowmarketing]

Originally Posted by Whosdaman

Dre...I'm trying to help you dude, the 21032 is screwed up for some reason...

Everyone is having the same problem, 028 and 027 work perfect, but 032 is getting stuck

I love your work dude, and I'm trying to help ya out here

Thanks 21032 removed.

Originally Posted by Xanius

I couldn't get any of these to boot on my vogue. Followed directions exactly and it was a no go, always got stuck on second splash screen.

However, doign the same thing with 21018 worked just fine, so I'm happy.

Did you use the new vogue core from the 1st post? Sorry if you have done this already. Place the NEW vogue_core_drellisdee in /kitchens and the new vogue_wm6.1_drellisdee into projects/groups/devicebases overwriting the old ones? Known bad oems are anything flash related or user added .net 2.0 or 3.5 as its included in the sys. Also the ppck oem of remote desktop (cab is fine) has been known to cause no data issues. Also on herman/victor (possibily vogue) the BT oems have been known to cause a hang at splash. Possibily other oems could cause a hang on boot also as there is no guarantee that one that used to work on an older sys will work with newer ones.

If that fails check your selections.txt (the name of your project you saved in the /projects folder) the top lines should read:
SelectionsVersion=.90.04
[BaseGroup]=GroupFile=Groups\BuildBases\WM6.1_96DPI_QVGA_Drel lisdee_21028_0409.txt
[DeviceGroup]=GroupFile=Groups\DeviceBases\Vogue_WM6.1_Drellisd ee.txt
GroupFile=[UserSetup]
ROMDeviceType=Vogue
ROMRevType=GPS
ROMOSType=WM6.1
DeviceRUUType=Standard
DeviceCarrierType=Verizon
PagePoolSize=4
PagePoolType=<Default>

Then try to extract the vogue_core_drellisdee (not in kitchen directory) to see if its corrupted and make sure vogue_21027.bin & vogue_21028.bin are inside it.

[Whosdaman]

Alright dude....your welcome

NFSFAN look at it as well and said the XIP is causing the problems, or it could be the dsm's
He has a working SYS from the official shipped rom, but won't realease it :'(

[deegimus]

Adding my two cents...

First, thanks for your hard work.

I cook a fairly clean ROM.

21018 works great and is mostly without any noticeable hiccups.
21028 appeared to work, but then wouldn't display any M2D page but the home page. Weird.
21032 hung on 2nd boot screen.

Had to get into the bootloader manually and then go back to 21018.

I'd like to try and get 21028 working.
What, specifically, is the difference between 21028 and 21018?

Thanks,
dj

[Xanius]

Originally Posted by drellisdee

Thanks 21032 removed.



Did you use the new vogue core from the 1st post? Sorry if you have done this already. Place the NEW vogue_core_drellisdee in /kitchens and the new vogue_wm6.1_drellisdee into projects/groups/devicebases overwriting the old ones? Known bad oems are anything flash related or user added .net 2.0 or 3.5 as its included in the sys. Also the ppck oem of remote desktop (cab is fine) has been known to cause no data issues. Also on herman/victor (possibily vogue) the BT oems have been known to cause a hang at splash. Possibily other oems could cause a hang on boot also as there is no guarantee that one that used to work on an older sys will work with newer ones.

If that fails check your selections.txt (the name of your project you saved in the /projects folder) the top lines should read:
SelectionsVersion=.90.04
[BaseGroup]=GroupFile=Groups\BuildBases\WM6.1_96DPI_QVGA_Drel lisdee_21028_0409.txt
[DeviceGroup]=GroupFile=Groups\DeviceBases\Vogue_WM6.1_Drellisd ee.txt
GroupFile=[UserSetup]
ROMDeviceType=Vogue
ROMRevType=GPS
ROMOSType=WM6.1
DeviceRUUType=Standard
DeviceCarrierType=Verizon
PagePoolSize=4
PagePoolType=<Default>

Then try to extract the vogue_core_drellisdee (not in kitchen directory) to see if its corrupted and make sure vogue_21027.bin & vogue_21028.bin are inside it.

Yeah I had tried with the stuff from this thread before I tried the older sys files.
If the .net stuff being added is causing problems and BT might, then it was one of those. Didn't know it was included in the file so I tried adding it on separately.
I may try again with 21028 but unless there's a huge difference between it and 21018 then I don't see a reason.

[CRACING]

Originally Posted by deegimus

What, specifically, is the difference between 21028 and 21018?
dj

Hello,

Normally I will be using blackstone official 20764 build inwhich it given faster performance for my htc wizard. Few days back I ported 21018 build xip/sys build but I feat slower. Day before yesterday I ported 21028 build xip/sys and its unbelievable fast so 21028 is not the 21018.

21018 is also not a fake build....................

Thanks and regards

[1loudsvt]

using these with no selections made so a perfectly clean rom on my vogue...

21032 would freeze...known issue

21028 booted fine, could not install cabs, could not make or receive calls but text messages worked fine???? links to dialer and com manager would not work

21027 com manger does not work, may be a tad slower than 21018 but kinda hard to tell at this point.

[darkomega69]

Quick question guys, 21028 has IE6 in it correct? I've noticed that even on mobile view, browsing wap sites, the text are no longer wrapped like the older IE. I believe the old IE had even choices, page width, one column, desktop. Is there a way to fix this?

[dishe]

Originally Posted by darkomega69

Quick question guys, 21028 has IE6 in it correct? I've noticed that even on mobile view, browsing wap sites, the text are no longer wrapped like the older IE. I believe the old IE had even choices, page width, one column, desktop. Is there a way to fix this?

remove the entire browsingie folder in the kitchen base you are using, and it will automatically revert to the old IE. I do this for compatibility with LogMeIn.