FORUMS

Kyocera Zio M6000 - boot.img has 4K header... odd?

249 posts
Thanks Meter: 41
 
By phazei, Senior Member on 25th October 2010, 08:00 PM
Post Reply Email Thread
I dumped the boot.img using:
Code:
cat /dev/mtd/mtd1 > /sdcard/cat-boot.img
and
Code:
dump_image boot /sdcard/dump-boot.img
Using dump_image it says:
Code:
mtd: read all-zero block at 0x00240000; skipping
mtd: read all-zero block at 0x002a0000; skipping
mtd: read all-zero block at 0x002c0000; skipping
And the sizes differ:
cat-boot.img: 4096K
dump-boot.img: 3712K

Then I ran unpackbootimg to unpack them. Neither worked, invalid gz files. So I took a look at the image files and instead of 2K header, it had a 4K header that had an extra 2K of 0's. Any idea why that might be?

I deleted the extra 2K of 0's and ran unpackbootimg again, both boot images provided identical gz's that worked.


I am able to test the gz's and extract the cpio, but how can I check if the kernel is good?
Since it seems to be malformed, it might have different spacing or something?
If I try to boot off of it using fastboot it just gives an error:
Code:
C:\android-sdk\tools>fastboot boot pulled\extracted\dump-boot.img-zImage

creating boot image...
creating boot image - 2263040 bytes
        downloading 'boot.img'... OKAY [  2.687s]
                       booting... FAILED (remote: invalid boot image)
finished. total time: 2.687s

Could someone with some experience take a look and help? I'm doing my best

The attached file has the extra 2K of 0's in the header I mentioned already removed.


Edit: I did the dump while the phone was booted up normally. It doesn't have any recovery mode where I could otherwise do it. If I use "adb reboot recovery" it just formats the phone and reboots.

Edit 2:
After doing a bunch of searching I tried this:

Code:
fastboot -b 400000 -n 4096 boot pulled\extracted\dump-boot.img-zImage pulled\extracted\dump-b
oot.img-ramdisk.gz
And it worked!!
Now I can try to port Clockwork Recovery

Edit 3: removed attachment, extracted version is attached to next post.
27th October 2010, 06:01 PM |#2  
OP Senior Member
Flag Las Vegas
Thanks Meter: 41
 
More
I attached the extracted kernel and ram disk here so anyone can use them without having to bother taking them apart themselves.

To fix a broken boot image, get the Andriod SDK installed, plug in the phone, reboot holding both green and red buttons to get to fastboot screen. Then use fastboot.exe to load image. Try to boot off it before flashing it. In order to flash it the "flash:raw boot" fastboot option will need to be used. I haven't tried this, but I've booted off of my extracted version and that worked.

The base address is "400000" and the page size is "4096" those need to be specified in the fastboot options.

Also just for reference, the extracted file "boot.img-cmdline" had this in it:
Quote:

mem=215M console=ttyMSM2,115200n8 androidboot.hardware=qcom

Not sure where or when that's needed yet, not for flashing, but maybe for compiling.
Attached Files
File Type: zip boot.img-zImage.zip - [Click for QR Code] (1.93 MB, 279 views)
File Type: zip boot.img-ramdisk.gz.zip - [Click for QR Code] (219.5 KB, 173 views)
File Type: zip recovery.img-ramdisk.gz.zip - [Click for QR Code] (568.9 KB, 202 views)
13th February 2011, 03:41 AM |#3  
Junior Member
Thanks Meter: 0
 
More
Sanyo zio m6000
I have locked myself out of my phone. I was wondering if you could upload/send me the boot image you used. I have tried all the ones you have for download, but none work.
18th March 2011, 05:32 AM |#4  
Spz0's Avatar
Inactive Recognized Developer
Thanks Meter: 674
 
Donate to Me
More
Any updates on this? I think this is suspect as to why nandroid restore borks the kyocera boot splash screen.

Sent from my Zio using XDA App
18th March 2011, 06:25 AM |#5  
Member
Flag Tulsa,Oklahoma
Thanks Meter: 76
 
More
I know this is off topic so excuse me but myprepaiddroid.com has some rom's that have been converted to the zio on cricket but they have not been tested yet.
23rd March 2011, 02:35 AM |#6  
Mattix724's Avatar
Senior Member
Flag Phoenix, Arizona
Thanks Meter: 2,539
 
More
So is the kernel in the boot image?

http://db.tt/zisPRYH boot.img after 2.2.1 update.

Sent from my Zio using XDA Premium App
25th March 2011, 02:40 PM |#7  
Spz0's Avatar
Inactive Recognized Developer
Thanks Meter: 674
 
Donate to Me
More
That extra 2k of 0s in the header is the kyocera logo (or the instruction that points to the actual image).

Would you mind unpacking the 2.2 boot.img zImage and Ramdisk and posting them phazei?
26th March 2011, 12:29 AM |#8  
Mattix724's Avatar
Senior Member
Flag Phoenix, Arizona
Thanks Meter: 2,539
 
More
Is phazei around anymore?

Sent from my Zio using XDA Premium App
3rd April 2011, 02:48 AM |#9  
OP Senior Member
Flag Las Vegas
Thanks Meter: 41
 
More
Quote:
Originally Posted by Mattix724

Is phazei around anymore?

Haha, yeah, I'm here. Just been busy, life's been getting me down. Foreclosure, and other misc stuff.

I browse the forum a couple times a week or so.
3rd April 2011, 06:30 PM |#10  
Mattix724's Avatar
Senior Member
Flag Phoenix, Arizona
Thanks Meter: 2,539
 
More
Sweet. Do you know if there was any change to the boot.img after 2.2?

Sent from my Zio using XDA Premium App
Post Reply Subscribe to Thread

Tags
android, boot, header, image

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes