WM 6.5 Kitchen QVGA and VGA Developer Edition

[xda2_haseeb]

Originally Posted by pyrorob

could you post where a diffrent 21812 qvga sys is other then xda2_haseeb's? i cant get that one to boot on my kaiser.

Tell me the kind of problem ur having the not booting problem could be the XIP not SYS ... on my device where the IPL/SPL and GSM version are shown, if tht screen dims out after some seconds means XIP is f9 problem might be in the OEM/SYS, if its bright all the time and device isnt booting it means problems in the XIP so u can see maybe the sames with your device

[pyrorob]

well it sticks at the initial splash screen (where the radio, protocol and rom version is shown) and doesnt dim. ive tried 2 diffrent xip's the one from the one you posted and the other from jojo, i guess i shouldve tried the 21806 xip first to rule it out. i assume its the sys only cause the last time it wouldnt startup at the same place it was because of it.

[gtrab]

Originally Posted by pyrorob

well it sticks at the initial splash screen (where the radio, protocol and rom version is shown) and doesnt dim. ive tried 2 diffrent xip's the one from the one you posted and the other from jojo, i guess i shouldve tried the 21806 xip first to rule it out. i assume its the sys only cause the last time it wouldnt startup at the same place it was because of it.

if it stops at first splash screen, it may be due to:

1- corrupted MSXIPkernel / or not properly inserted (ported)
2- wrong decompressor DLL (LZX or XPR)

I wouldn't blame SYS in the first instance (unless it's got wrong DPI or LANG folders)

BTW: SYS and XIP can belong to different builds ("hybrid" build)
Test your new SYS with a previously working XIP
That will help to streamline the possibilities

[pyrorob]

well, i tested using my previous working xip and no go.. i just found a diffrent sys and am about to try that

[Da_G]

I know you guys like 96 dpi / 240x320 over here, so i'm uploading the 21812 dump for that res/dpi now it will be on my thread @ xda.

also i've uploaded smartphone 131 dpi / 320x240 @ the xda smartphone general forum

[pyrorob]

Originally Posted by Da_G

I know you guys like 96 dpi / 240x320 over here, so i'm uploading the 21812 dump for that res/dpi now it will be on my thread @ xda.

also i've uploaded smartphone 131 dpi / 320x240 @ the xda smartphone general forum

da_g as always you da man!

[xda2_haseeb]

Originally Posted by pyrorob

well it sticks at the initial splash screen (where the radio, protocol and rom version is shown) and doesnt dim. ive tried 2 diffrent xip's the one from the one you posted and the other from jojo, i guess i shouldve tried the 21806 xip first to rule it out. i assume its the sys only cause the last time it wouldnt startup at the same place it was because of it.

well this is usually because of XIP, but as u say it doesnt work with you old XIP too, so it might be the SYS

[pyrorob]

Originally Posted by xda2_haseeb

well this is usually because of XIP, but as u say it doesnt work with you old XIP too, so it might be the SYS

yeah sorry man, your last couple ones have been gems, but the last one i tried to insert the missing dpi folder's and i think that broke it, but i grabbed a new sys from a trinity kitchen and it booted right up.

[pyrorob]

i have a question for everyone.. i had read that converting files to modules would allow those files to be accessd quicker (correct?), and i also heard that certain files in the sys shouldnt be converted or itll break the rom. is there any rule/guide as to what files can/cant be converted?

also im working with twopumpchump on figuring out and making a guide on which files for the kaiser can/cant be spinlock patched. any input?
Thanks!

[xda2_haseeb]

Originally Posted by pyrorob

yeah sorry man, your last couple ones have been gems, but the last one i tried to insert the missing dpi folder's and i think that broke it, but i grabbed a new sys from a trinity kitchen and it booted right up.

No Problem man!! dont be sorry!! and thx for calling my work GEM have fun