WM 6.5 Kitchen QVGA and VGA Developer Edition

[inertiax3]

OK, here we go... the Samsung i780 is a QVGA device, 320 x 320 screen resolution with 128MB RAM and no officialy planned WM65 upgrade

I have a BIG problem cooking a WORKING W65 on this device (WM61 NO PROBLEM, all work 100%!!!). Can some GURU take a look at the following steps and tell me what I am doing wrong please? (already talked to Anryl and StevenH who pointed out a few things), this is a revised version.

Here's what I do:

1. I take an original ROM for the Samsung i780, dump it, get a directory called DUMP (.ROM,.VM and many modules and files).

2. Using PKGTOOL I create the corresponding OEM and SYS directories (PKGTool version 1.01 by bepe) and one more file that is not in the OEM or SYS dir (a427cbd...dsm) - I put it in the OEM directory under OEM_Other

3. Then I prepare the OEM dir with these directories:

OEM_DPI_128
OEMApps
OEMDrivers
OEMMisc
OEM.cer (this is a file)

--> !!IMPORTANT!! PKGTool doesent create the OEM_Lang_0409 directory with some original ROMs, if this directory is not present then PkgToolsBuildOS 5.3 throws up an error (somethinig with paramater s..).
--> Can I use this directory from other WM61 releases? It contains, amongst other, initflashfiles.dat and as such copies quite a lot of files, including welcome.lnk..
--> The OEM.cer file (certificate?) - is it important? It contains the word Samsung, I guess it must not be replaced by any other OEM.cer, right?

4. Now onto the SYS - I delete all directories from the ORIGINAL dump except .VM and metadata, these two will be used from the original dump

5. Then I copy the new SYS folders, either WM65 21176 or 21189, rename directories containing resh/resv to 320 (i780 is a 320x320 device). Nothing else is removed and .VM and metadata is kept from original ROM.

6. Now the XIP - port it, old XIP from my original dumped ROM (HL2 in my case, not sure about the build), the donor will be a 21176 or 21189 XIP, I use either XIP Kitchen beta 2 from LennySh or XIPPorterEx (build 32/35) - whichever produces a working XIP without any overlaps in map.txt.

--> !!IMPORTANT!! WinCE.nls is kept within the XIP - I've heard it's possible to integrate into the IMGFS but I think that the Samsung i780 doesen't like this.
--> !!IMPORTANT2!! WinCE.nls can ONLY be present in the XIP, not XIP and SYS at the same time, true?
--> !!IMPORTANT3!! Can WWE WinCE.nls be used on Chinese builds? (0804)

7. A working and ported XIP is the dumped via XIPPort, "write maps" just to make sure (again) there are no overlaps

8. The files obtained in step 7 are copied to ROM\XIP
(so I have all dll directories [eg.busenum.dll,cachefilt.dll...] and files [a few dsm, boot.hv, boot.rgu, wince.nls, mxip_lang.vol...]

--> !!IMPORANT!! - Which files should REALLY be in ROM\XIP? Is BOOT.RGU enough? I've seen some kitchens with BOOT.RGU and NK.EXE ?! What does this mean?

9. OK, so I have nice OEM, SYS and ROM directories, I run PkgToolsBuildOS5.3, press LOAD ROM, run COMPILE, the tool reads everything, RGUComp runs OK and a temp\dump directory is created - nice.. it's around 125 MB

10. Next I run WMReloc, version 1.04 for WM6.5, all files are relocated (no errors in log). Is this it for the relocation process? The tool only changes the imageinfo.txt in each dir, is this enough? G'reloc throws up errors with
some WM65, but WMReloc runs OK all the time. Should I use WMReloc or G'Reloc? Is WMReloc reliable?

11. Next some i780-specific stuff:

move temp\DUMP to the root, run RecreateBin.bat which contains:

imgfsfromdump imgfs_raw_data.bin new_imgfs.bin
del imgfs_raw_data.bin
ren new_imgfs.bin imgfs_raw_data.bin
make_imgfs i780.nb0.payload.body -nosplit
merge i780.nb0.payload.header i780.nb0.payload.body i780.nb0.payload
nbmerge -data 2048 -extra 8 i780.nb0 -conservative

12. I get i780.nb0 file

13. Export the XIP from i780.nb0

osnbtool -sp i780.nb0
osnbtool -d i780.Nb0.os.nb 1 xip.bin

14. Import the ported XIP (21176 or 21189, based on which SYS I use) into i780.Nb0 (also I change the PP or leave original, tried both)

osnbtool -ap xip.bin 16
osnbtool -c i780.Nb0.os.nb 1 xip.bin
osnbtool -extra i780.Nb0.os.nb.NEW
copy /b /y i780.Nb0.pre + i780.Nb0.os.new.EXA i780.Nb0.new
del i780.Nb0
ren i780.Nb0.pre i780.Nb0

15. And finally I convert the i780.Nb0 into a BIN:

conv3 input.txt > conv3_output.txt
ren i780.nb0.b000ff !!i780_flashable_bin.bin

16. And flash the whole thing.....

ET VOILAAAAAAA

First I see the Samsung logo, then Samsung animation but then either a black screen with a white pointer which I can't move (the i780 has a optical mouse) (which later goes dim and the the backlight turns off), or the Green WinMo 6.5 background (which later goes dim and the the backlight turns off) or Green Logo and DING sound (but no welcome center)... the keypad doesent react, neither does the power button, however the touchscreen does (tapping it brings up higher backlight).

Once the PDA screen turns off I can only power it up (resume from StandBy) by connecting a data cable, the PDA then wakes up (to the same black or green screen). Pressing the power button while the device is in StandBy sometime brings up the blue LED.. what a mess!!!

I've tried maybe 70-80 different variations, no luck .. I HATE flashing ! And because there is no easy kitchen for the i780 one ROM cooking+flashing takes ~25mins.. OMG

So please, can someone tell what am I doing wrong?!

Regards to every and THANX!!!

[alex2]

actually somewhere i read a little about the same problem with samsung
but i really cannot remember where
try googling, maybe you will find that forum...
but if you can see wm 6.5 green screen that means that your xip is made ok otherwise your device won't boot to this step and the problem is in your imgfs and probably with your oem drivers
if you succeed building wm6.1, try to replace just sys folder in your kitchen to sys from wm6.5 and leave oem as is, probably oem is always the same for wm6.1 and wm6.5. and try to use g'reloc, because at least for me wmreloc never made something usable.

also you device is 320x320, but existing wm6.5 are prepared for 640x480 or 320x240, just renaming the folders won't help, you have to find or made proper resolution resources.

[inertiax3]

Originally Posted by alex2

also you device is 320x320, but existing wm6.5 are prepared for 640x480 or 320x240, just renaming the folders won't help, you have to find or made proper resolution resources.

Yep, but those are just some pictures and stuff (i.e wmplayer skins..), I would at least hope to have reached the Welcome center before even considering touching these "extras"

[Tplane37]

I had a similar issues on my Titan the first dozen or so attempt at 21176 and 21189. (Except obviously no mouse curser). My screen went to black. I had actually thought the device turned off completely and was unresponsive until I could see the off haze around the edges if the lights were off (talk about freaking me out!). Also, the only thing I was able to do was return to bootloader or soft reset. And I could only go to bootloader if I caught it on either subslash 1 or subsplash two.

I was using Mr. FREE's kitchen. I would like to use PPCKitchen's build OS, but I am having major difficulties figuring out all the files that need editit and what to add to the individual archives, txt file, and option.xml's. Can someone post a link or instructions on how to get a 6_5 Build into the PPCKitchen's Build OS??? There are networking programs and other items I want to use in that kitchen, and I am really not in the mood to try to dig for each individual itme if I can just place a check by the stuff I want.

Again, if you know how to add the WM6_5 Builds into PPCKitchen's BuildOS, please post instructions or a link to the instructions. I could even go for a PM if need be! Thanks in advance!

[Getitnowmarketing]

Anryl or anyone else working on qvga can you share 21189 qvga 0409 working resources. Ive got a booting 21189 on apache however the titanium freezes and the lock will not unlock device. I used da_g's 21189 0409 files with the 21169 96dpi as I couldn't figure out how to use res hacker for translation. Havent been able to test further.

[anryl]

Originally Posted by drellisdee

Anryl or anyone else working on qvga can you share 21189 qvga 0409 working resources. Ive got a booting 21189 on apache however the titanium freezes and the lock will not unlock device. I used da_g's 21189 0409 files with the 21169 96dpi as I couldn't figure out how to use res hacker for translation. Havent been able to test further.

will do but the office still no GO cant figure this one out

WORKING QVGA SYS

http://www.linksafe.info/show.php?show=45535

[Getitnowmarketing]

Originally Posted by anryl

will do but the office still no GO cant figure this one out

WORKING QVGA SYS

http://www.linksafe.info/show.php?show=45535

Thanks I was dsm reassembling a kasier and BA 21189 dump to try to get the QVGA I haven't updated the office I'm still using wm6.1 office which works for me on 21189.

[anryl]

i included CRCinAU device update in rom and his office and icontacts are fine

[Getitnowmarketing]

Originally Posted by anryl

i included CRCinAU device update in rom and his office and icontacts are fine

Strange using the 21189 from da_g with 96 dpi from 21169 office worked (but not titanium) and using your qvga which is A+++ btw the exact same office didn't work. Beyond compare found no diff in reg or anything else that would seem to cause it.

[m_reyna_16]

so then which system will be the final release? i read a cpl of posts back that a certain sys was the last build but cant remember which one it was.