Jump to content

Why cant I boot from other boot image than the original?


Guest oernii
 Share

Recommended Posts

Hi, i have flashed 3 images on my rooted desire:

- the original backed up image

- splitted & recreated boot image with the same kernel and initrd as the original boot img

- boot image extracted from update-cm-6.0.0-N1-RC3-signed

Only the first image boots up, the other 2 do not even start on adb logcat. I have to reflash the original to boot up. This is what I do in recovery:

# ./split_bootimg.pl boot.img

# mkbootimg --kernel boot.img-kernel --ramdisk boot.img-ramdisk.gz --cmdline 'no_console_suspend=1' -o newboot.img

# adb push newboot.img /sdcard

# cat /dev/zero > /dev/mtd/mtd2

# flash_image boot /sdcard/newboot.img

this does not boot up. If I flash the original boot.img however, it goes up.

Link to comment
Share on other sites

One other thing: there are some notices when flashing, but as the original boot.img shows these also and it boots up, I presume they are not that important.

mtd: read all-zero block at 0x00000000; skipping

mtd: read all-zero block at 0x00020000; skipping

mtd: read all-zero block at 0x00040000; skipping

mtd: read all-zero block at 0x00060000; skipping

mtd: read all-zero block at 0x00080000; skipping

mtd: read all-zero block at 0x000a0000; skipping

mtd: read all-zero block at 0x000c0000; skipping

mtd: read all-zero block at 0x000e0000; skipping

mtd: read all-zero block at 0x00100000; skipping

mtd: read all-zero block at 0x00120000; skipping

mtd: read all-zero block at 0x00140000; skipping

mtd: read all-zero block at 0x00160000; skipping

mtd: read all-zero block at 0x00180000; skipping

mtd: read all-zero block at 0x001a0000; skipping

mtd: read all-zero block at 0x001c0000; skipping

mtd: read all-zero block at 0x001e0000; skipping

mtd: read all-zero block at 0x00200000; skipping

mtd: read all-zero block at 0x00220000; skipping

mtd: read all-zero block at 0x00240000; skipping

mtd: read all-zero block at 0x00260000; skipping

mtd: read all-zero block at 0x00280000; skipping

mtd: read all-zero block at 0x002a0000; skipping

mtd: read all-zero block at 0x002c0000; skipping

mtd: read all-zero block at 0x002e0000; skipping

Link to comment
Share on other sites

  • 11 months later...

Got similar issue when doing the same on Huawei U8230

~ # cat /proc/mtd

cat /proc/mtd

dev:	size   erasesize  name

mtd0: 00280000 00020000 "boot"

mtd1: 05500000 00020000 "system"

mtd2: 06940000 00020000 "userdata"

mtd3: 01400000 00020000 "cache"

mtd4: 00500000 00020000 "recovery"

mtd5: 00040000 00020000 "misc"

~ # cat /dev/zero > /dev/mtd/mtd0

cat /dev/zero > /dev/mtd/mtd0

cat: write error: No space left on device  (see URL below)

~ # flash_image boot /sdcard/boot.img

flash_image boot /sdcard/boot.img

mtd: read all-zero block at 0x00000000; skipping

mtd: read all-zero block at 0x00020000; skipping

mtd: read all-zero block at 0x00040000; skipping

mtd: read all-zero block at 0x00060000; skipping

mtd: read all-zero block at 0x00080000; skipping

mtd: read all-zero block at 0x000a0000; skipping

mtd: read all-zero block at 0x000c0000; skipping

mtd: read all-zero block at 0x000e0000; skipping

mtd: read all-zero block at 0x00100000; skipping

mtd: read all-zero block at 0x00120000; skipping

mtd: read all-zero block at 0x00140000; skipping

mtd: read all-zero block at 0x00160000; skipping

mtd: read all-zero block at 0x00180000; skipping

mtd: read all-zero block at 0x001a0000; skipping

mtd: read all-zero block at 0x001c0000; skipping

mtd: read all-zero block at 0x001e0000; skipping

mtd: read all-zero block at 0x00200000; skipping

mtd: read all-zero block at 0x00220000; skipping

mtd: read all-zero block at 0x00240000; skipping

mtd: read all-zero block at 0x00260000; skipping

~ # ls -al /dev/mtd/mtd0

ls -al /dev/mtd/mtd0

crwxrwxrwx	1 root 	root   	90,   0 May 17 03:25 /dev/mtd/mtd0

crwxrwxrwx	1 root 	root   	90,   0 May 17 03:25 /dev/mtd/mtd0

~ # ls -al /sdcard

ls -al /sdcard

drwxrwxrwx	7 root 	root      	4096 Jan  1  1970 .

drwxr-xr-x   15 root 	root 			0 May 17 03:25 ..

-rwxrwxrwx	1 root 	root   	1918976 Feb  2  2010 boot.img

-rwxrwxrwx	1 root 	root   	2621440 May 17 03:02 mtd0.img

-rwxrwxrwx	1 root 	root   	5242880 May 17 03:01 mtd4.img

This is reported as not an issue here URL.

I also have tried to chmod to 777 the mtd0.

but when I reboot, the Fastboot version has not changed and the boot image is still the same !!!!

I'll keep doing some investigation but any advice is welcomed

Edited by U_Droid
Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
 Share

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.