LZX Compression woes

[toadlife]

I've compiled my current ROM build with both XPR and LZX compression. It works fine with XPR, but with LZX compression the phone freezes after playing the start up animation.

I've verified that I have the correct cecompr.dll module in my XIP.

My kitchen based on ivan's "justme" kitchen.

Anyone here have any idea?

[ivanmmj]

Strange. If it can pla the startup animation, then it is reading the cecompr.dll just fine. Are you using the cecompr.dll I posted in the XIP porting thread in the main development forums? And you're not changing anything else? Also, you're hex editing the image, just like I mentioned in that same thread?

[toadlife]

I'm not changing anything in the SYS/OEM when building.

I'm not doing any hex editing though. I thought the kitchen handled that. I did place pauses in the LZX build script and checked out the imgfs.bin file with a hex editor. THe letters "LZX" appeared near the front of the file so I assumed everything was okay on that front.

I'm sure I'm using the correct cecompr.dll. I inserted a couple of different cecompr.dll files just to be sure. One was the file from your easylzx thingy and the other was the module posted in a thread that you started.

[toadlife]

To try and narrow down the problem, I am going to insert my OEM into your justme kitchen and use the old sys/XIP that comes with the kitchen. If that boots, then it's my SYS/XIP (which will be disappointing since it works so damn well on my phone otherwise).

I'm using 21051 for both SYS and XIP and I ported it in myself. I would hate to have to do the porting all over again.

[ivanmmj]

The SYS and XIP won't have anything to do with it, except for the cecompr.dll.
My old kitchen doesn't automatically set it. You HAVE to follow the walkthrough I made. You HAVE to hex edit the first XPR to LZX. The LZX you might see there right now might just be one of the LZX's from the cecompr.dll file after it's been inserted into the image before the rest of the ROM is inserted. But even if you didn't edit it, it should build a XPR ROM and boot just fine. Tell me, does the build process take a LOOOOOT longer when you're using the "LZX" process? If it doesn't, then it's not making a LZX compressed ROM.

[toadlife]

The build process takes a long time and 2 gigs of memory and the resulting ROM is much smaller, so I know it's LZX compressed.

The kitchen I am using asked if you want LXZ or XPR compression when it starts and says nothing of hex editing so I was under the impression that no hex editing was required.

Just to be sure, I tried hex editing the imgfs.bin and replaced the first XPR string I found with LZX, but the resulting ROM did the same thing on boot.

I wasnt able to test out using your sys because I've never been able to get flashing from an SD card to work and I can find my sd adapter at the moment.

Oh well.

[ivanmmj]

Hmm... That sounds like my old 1st gen LZX kitchen... it was very broken... lol
Don't use it.
I could always release my old 2nd gen LZX kitchen while I'm still working on my current kitchen. It's the kitchen that I made JustStableV1 and the early versions of JustStableV2 and JustHome.
*The later versions of JustStableV2 and JustHome were created on my 1st Gen Visual Kitchen. I'm currently working on my 2nd Gen Visual Kitchen. Just2Clean was created on my 1st gen non-LZX kitchen. I've made a lot of kitchens, I just never release them. :p

Anyhoo... if you're using the JustMe kitchen's built-in LZX system, that's probably where your problem lies, unfortunately...
I'll try to remember to upload the 2nd gen LZX kitchen later on today.

EDIT: Also, the 2nd gen kitchen doesn't take that extra RAM to make the ROM.

The build process takes a long time and 2 gigs of memory and the resulting ROM is much smaller, so I know it's LZX compressed.

The kitchen I am using asked if you want LXZ or XPR compression when it starts and says nothing of hex editing so I was under the impression that no hex editing was required.

Just to be sure, I tried hex editing the imgfs.bin and replaced the first XPR string I found with LZX, but the resulting ROM did the same thing on boot.

I wasnt able to test out using your sys because I've never been able to get flashing from an SD card to work and I can find my sd adapter at the moment.

Oh well.

[toadlife]

That would be great if you could upload a working lzx kitchen. The xpr part from the kitchen I'm using works fine. Maybe I can modify the XPR script with a pause, replace the appropriate DLLS and do the hex editing method to get it to work for now.

Thanks for all your help.

[ivanmmj]

That would be great if you could upload a working lzx kitchen. The xpr part from the kitchen I'm using works fine. Maybe I can modify the XPR script with a pause, replace the appropriate DLLS and do the hex editing method to get it to work for now.

Thanks for all your help.

You need a module version of the LZX file you have currently, that's the biggest difference (actually, the 2nd gen kitchen also auto hex edits the parts, instead of keeping a copy of the LZX and XPR cores.)

[toadlife]

You need a module version of the LZX file you have currently, that's the biggest difference (actually, the 2nd gen kitchen also auto hex edits the parts, instead of keeping a copy of the LZX and XPR cores.)

WOOHOO!!


I already had the module version of cecompr.dll. I modified the XPR version of your kitchen and the resulting ROM booted right up!!


YAY!

:D

[ivanmmj]

WOOHOO!!


I already had the module version of cecompr.dll. I modified the XPR version of your kitchen and the resulting ROM booted right up!!


YAY!

:D
lol
Glad I could help. :p