To: flibblesan and BigBearMDC, why Repacked boot.img can't boot?

[Guest Tom G]

The base address is always 0 (so using mkbootimg you don't need to specify a base).

Sorry, that is incorrect. The base is 0x10000000 (which is the default for mkbootimg).

I should check things like this before posting.

[Guest twrock]

Sorry, that is incorrect. The base is 0x10000000 (which is the default for mkbootimg).

I should check things like this before posting.

How sure are you of that? :huh:

But seriously, if that really is it, thanks much. Hopefully I'll be able to get something to work now.

I think what has some of us stumped is that in the Darktremor thread it looks like there are a lot of possibilities:

0x19200000 - HTC Hero CDMA. HTC Hero GSM, HTC Magic (myTouch 3G)

0x11200000 - HTC Droid Eris

0x20000000 - HTC Evo, Nexus One, HTC Desire, HTC Incredible

0x2e000000 - HTC Tattoo

0x12c00000 - HTC Legend, HTC myTouch 3G Slide, HTC Aria

0x10000000 - HTC G1, Motorola Droid

So without someone "in the know" to tell us, I don't know how to find it.

[Guest Tom G]

How sure are you of that? :huh:

It is definitely correct. As a test unpack an image and repack it with mkbootimg --base 0x10000000. Normally you don't need to specify a base, but if you look at the source for mkbootimg its defaults assume the base is 0x10000000.

[Guest mryongzhang]

楼主啊 你在不在啊

你的mkbootimg能用了吗

能不能给一个给我啊

我想把Recovery中文了

可以加你QQ吗 有很多菜鸟问题想请教你

谢谢

呵呵，mkbootimg本身应该没问题，但是做出来的boot.img就是不能

[Guest mryongzhang]

How sure are you of that? :huh:

But seriously, if that really is it, thanks much. Hopefully I'll be able to get something to work now.

I think what has some of us stumped is that in the Darktremor thread it looks like there are a lot of possibilities:

0x19200000 - HTC Hero CDMA. HTC Hero GSM, HTC Magic (myTouch 3G)

0x11200000 - HTC Droid Eris

0x20000000 - HTC Evo, Nexus One, HTC Desire, HTC Incredible

0x2e000000 - HTC Tattoo

0x12c00000 - HTC Legend, HTC myTouch 3G Slide, HTC Aria

0x10000000 - HTC G1, Motorola Droid

So without someone "in the know" to tell us, I don't know how to find it.

I'm just stumped by Darktremor thread. And I want to know how to find Pulse's base address.

[Guest Chinese farmers]

5555

你把你的mkbootimg发一个给我 [email protected]

能中文哦

我在其他论坛已经看到了

应该是mkbootimg的问题

你不信 你可以这样试一下

找个能用的boot.img 解开 什么都不动 在合成 很有可能 都不能启动

[Guest twrock]

I'm just stumped by Darktremor thread. And I want to know how to find Pulse's base address.

So have you tried 0x10000000 as Tom G suggested? Did it not work?

[Guest mryongzhang]

So have you tried 0x10000000 as Tom G suggested? Did it not work?

いいえ、まだです。週末に試して見ます。

[Guest mryongzhang]

いいえ、まだです。週末に試して見ます。

haha, replied by japanese.

I havn't tried 0x10000000, I will try it this weekend. And I will post the result.

[Guest mryongzhang]

5555

你把你的mkbootimg发一个给我 [email protected]

能中文哦

我在其他论坛已经看到了

应该是mkbootimg的问题

你不信 你可以这样试一下

找个能用的boot.img 解开 什么都不动 在合成 很有可能 都不能启动

这周末就给你发，别着急，呵呵。

[Guest twrock]

haha, replied by japanese.

I havn't tried 0x10000000, I will try it this weekend. And I will post the result.

沒有關係 :huh:

Yes, please let us know.

Edited September 2, 2010 by twrock

[Guest Chinese farmers]

你平时没搞啊 编译得怎么样了嘛

这周休息了 555 发到邮箱哦 谢了

[Guest mryongzhang]

thanks BigBear for your paient reply, I will try FLB MOD.

Hi，BigBear and everyone.

Today I have tried FLB MOD, and that works fine. So there's something wrong in my init.rc.

[Guest mryongzhang]

Today I Unpack the root.img, Extract the ramdisk, nothing to change. And then re-create the ramdisk, Repack the boot.img by mkbootimg.

The new boot.img works fine, so there's something wrong in my init.rc.

[Guest Chinese farmers]

你是不是说成功了哦

rc有点不正常

你用的哪种方法解压和打包的 我用的这种 不过不行

解压

# ./split_bootimg.pl boot.img

# mkdir ramdisk

# cd ramdisk

# gzip -dc ../boot.img-ramdisk.gz | cpio -i

还原

#cd ramdisk#find . | cpio -o -H newc | gzip > ../ramdisk-repack.cpio.gz

#mkbootimg --cmdline 'no_console_suspend=1 console=null' --kernel boot.img-kernel --ramdisk ramdisk-repack.cpio.gz -o 999.img

mkbootimg是你传给我的哪个

我就把里面的图片换了 图片觉对没问题（来自其他台湾版的开机第二屏）

刷到手机后 刚刚把第二屏显示出来 就自动重起了 进入re哪个模式了

麻烦你把你用的方法写出来一下 谢谢

你用不用及时的通信工具啊 有问题想请教你

我马上去 把自己改的解开看看是不是一样的

5555555555

[Guest Chinese farmers]

我对比了一下

能用的 和我自己改的 差别是对的 但是不能启动是方法不对还是

我看看能不能上传图

[Guest mryongzhang]

你是不是说成功了哦

rc有点不正常

你用的哪种方法解压和打包的 我用的这种 不过不行

解压

# ./split_bootimg.pl boot.img

# mkdir ramdisk

# cd ramdisk

# gzip -dc ../boot.img-ramdisk.gz | cpio -i

还原

#cd ramdisk#find . | cpio -o -H newc | gzip > ../ramdisk-repack.cpio.gz

#mkbootimg --cmdline 'no_console_suspend=1 console=null' --kernel boot.img-kernel --ramdisk ramdisk-repack.cpio.gz -o 999.img

mkbootimg是你传给我的哪个

我就把里面的图片换了 图片觉对没问题（来自其他台湾版的开机第二屏）

刷到手机后 刚刚把第二屏显示出来 就自动重起了 进入re哪个模式了

麻烦你把你用的方法写出来一下 谢谢

你用不用及时的通信工具啊 有问题想请教你

我马上去 把自己改的解开看看是不是一样的

5555555555

你的mkbootimg使用有问题：

#mkbootimg --cmdline 'no_console_suspend=1 console=null' --kernel boot.img-kernel --ramdisk ramdisk-repack.cpio.gz -o 999.img

应该用：

#mkbootimg --cmdline ’mem=128M console=ttyMSM2,115200n8 androidboot.hardware=qcom console=ttyUSBCONSOLE0 androidboot.console=ttyUSBCONSOLE0’ --kernel boot.img-kernel --ramdisk ramdisk-repack.cpio.gz -o 999.img

[Guest Chinese farmers]

你的mkbootimg使用有问题：

#mkbootimg --cmdline 'no_console_suspend=1 console=null' --kernel boot.img-kernel --ramdisk ramdisk-repack.cpio.gz -o 999.img

应该用：

#mkbootimg --cmdline ’mem=128M console=ttyMSM2,115200n8 androidboot.hardware=qcom console=ttyUSBCONSOLE0 androidboot.console=ttyUSBCONSOLE0’ --kernel boot.img-kernel --ramdisk ramdisk-repack.cpio.gz -o 999.img

谢谢 马上测试

[Guest Chinese farmers]

怎么不行

root@ylmfos:/media/54E8B25EE8B23DD4/111/工具/要的/ramdisk# mkbootimg --cmdline 'mem=128M console=ttyMSM2,115200n8 androidboot.hardware=qcom console=ttyUSBCONSOLE0 androidboot.console=ttyUSBCONSOLE0' --kernel boot.img-kernel --ramdisk ramdisk-repack.cpio.gz -o 999.img

error: could not load kernel 'boot.img-kernel'

root@ylmfos:/media/54E8B25EE8B23DD4/111/工具/要的/ramdisk#

[Guest Chinese farmers]

不好意思 是我sb了 目录都进错了 马上刷机

[Guest Chinese farmers]

还是不行 这次只是多了点点东西 第二屏完后在重启之前 能看到没改之前的开机画面 就是and哪几个字母 一闪就重启了 是不是还要在init里面加什么

麻烦你

[Guest mryongzhang]

怎么不行

root@ylmfos:/media/54E8B25EE8B23DD4/111/工具/要的/ramdisk# mkbootimg --cmdline 'mem=128M console=ttyMSM2,115200n8 androidboot.hardware=qcom console=ttyUSBCONSOLE0 androidboot.console=ttyUSBCONSOLE0' --kernel boot.img-kernel --ramdisk ramdisk-repack.cpio.gz -o 999.img

error: could not load kernel 'boot.img-kernel'

root@ylmfos:/media/54E8B25EE8B23DD4/111/工具/要的/ramdisk#

error: could not load kernel 'boot.img-kernel'

这句是说你指定的kernel文件不存在，你看一下你解出来的kerne

文件名是不是'boot.img-kernel'，如果不是的话，指定成正确的文件名。

另外，貌似你是在/ramdisk/目录下执行的mkbootimg，你的boot.img-kernel和ramdisk-repack.cpio.gz可能都在上一层目录里边，如果是的话，先回到上

[Guest mryongzhang]

还是不行 这次只是多了点点东西 第二屏完后在重启之前 能看到没改之前的开机画面 就是and哪几个字母 一闪就重启了 是不是还要在init里面加什么

麻烦你

我还没研究过怎么改开机画面，所以我也不知道，另外自己

[Guest Chinese farmers]

开机第二屏太难看了 唉

悲剧啊

fastboot flash splash1 123.rgb565 改开机第一屏也不行 提示分区有问题 华为的说是加了什么保护机制

你现在有没有试着编译rom呢

[Guest tknv]

How sure are you of that? ;)

But seriously, if that really is it, thanks much. Hopefully I'll be able to get something to work now.

I think what has some of us stumped is that in the Darktremor thread it looks like there are a lot of possibilities:

0x19200000 - HTC Hero CDMA. HTC Hero GSM, HTC Magic (myTouch 3G)

0x11200000 - HTC Droid Eris

0x20000000 - HTC Evo, Nexus One, HTC Desire, HTC Incredible

0x2e000000 - HTC Tattoo

0x12c00000 - HTC Legend, HTC myTouch 3G Slide, HTC Aria

0x10000000 - HTC G1, Motorola Droid

So without someone "in the know" to tell us, I don't know how to find it.

hexdump boot.img | head -n1

0000000 4e41 5244 494f 2144 a13c 0027 8000 0020

means 0x00200000 - Huawei ideos U8150

but use split_bootmig.pl more info,that show command line too

split_bootimg.pl boot.img

Page size:	  4096 (0x00001000)

Kernel addr:	2129920 (0x00208000)

Kernel size:	2738400 (0x0029c8e0)

Ramdisk addr:   18874368 (0x01200000)

Ramdisk size:   174024 (0x0002a7c8)

Board name:	 

Command line: mem=211M console=ttyMSM2,115200n8 androidboot.hardware=ideos

Writing orig.boot.img-kernel ... complete.

Writing orig.boot.img-ramdisk.cpio ... complete.

example command line for mkbooimg --cmdline 'mem=211M console=ttyMSM2,115200n8 androidboot.hardware=ideos' and boot.img from device or update.zip

cat /dev/mtd/mtd0 > boot.img

and mkdX is depend on device,so

cat /proc/mtd

dev:	size   erasesize  name

mtd0: 00500000 00020000 "boot"

mtd1: 00500000 00020000 "recovery"

mtd2: 00140000 00020000 "misc"

mtd3: 00060000 00020000 "splash"

mtd4: 0aa00000 00020000 "system"

mtd5: 05d00000 00020000 "cache"

mtd6: 0a6a0000 00020000 "userdata"

mtd7: 01400000 00020000 "cust"

you can know where is boot.img

hope it help