MobileRead Forums - View Single Post

Renate · 03-05-2022, 06:58 PM

Yeah, I can guess that they are using some sort of compression on the ramdisk that I haven't implemented in imgutil. That's a different problem. Sigh. But it still identified it as an Android image.

I still don't know why edl with the automatic sizing (without the 8000) didn't work.

Do you have a hex dumper? Could you show me 0x00 to 0x40 (the first 64 bytes) of one of those 32 Meg files?

Here's a typical example, a 16 Meg image in a 64 Meg partition:

Code:

imgutil /v part09
Header:         596 (00000254)
Kernel:  12,516,122 (00BEFB1A) @ 00008000
Payload: 12,215,482 (00BA64BA)
DTB:        300,640 (00049660)
Ramdisk:  6,280,716 (005FD60C) @ 01000000
Second:           0 (00000000) @ 00F00000
Padding: 48,304,128 (02E11000)

You can also simply hand a file to Magisk for modification and it will tell you if everything is ok.

If you really want the full 100 Megs just change 8000 to 24576.

I'm beginning to think that those images are not the "old" standard ANDROID! images. That would explain everything. imgutil must have thought they were gzip standalone ramdisks when they were gzip standalone kernels.

If you have 7zip or other utility, try ungzipping one of the images.

03-05-2022, 06:58 PM	#97
Renate Onyx-maniac Posts: 4,002 Karma: 18026955 Join Date: Feb 2012 Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5, Go6	Yeah, I can guess that they are using some sort of compression on the ramdisk that I haven't implemented in imgutil. That's a different problem. Sigh. But it still identified it as an Android image. I still don't know why edl with the automatic sizing (without the 8000) didn't work. Do you have a hex dumper? Could you show me 0x00 to 0x40 (the first 64 bytes) of one of those 32 Meg files? Here's a typical example, a 16 Meg image in a 64 Meg partition: Code: imgutil /v part09 Header: 596 (00000254) Kernel: 12,516,122 (00BEFB1A) @ 00008000 Payload: 12,215,482 (00BA64BA) DTB: 300,640 (00049660) Ramdisk: 6,280,716 (005FD60C) @ 01000000 Second: 0 (00000000) @ 00F00000 Padding: 48,304,128 (02E11000) You can also simply hand a file to Magisk for modification and it will tell you if everything is ok. If you really want the full 100 Megs just change 8000 to 24576. I'm beginning to think that those images are not the "old" standard ANDROID! images. That would explain everything. imgutil must have thought they were gzip standalone ramdisks when they were gzip standalone kernels. If you have 7zip or other utility, try ungzipping one of the images. Last edited by Renate; 03-05-2022 at 07:20 PM.