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

[Guest mryongzhang]

Hi, flibblesan and BigBearMDC and this forum's everybody.

Thank you for your excellent work and MoDaCo forum, I'm a new pulse's user from China.

I've been using the T-mobile official 2.1 update for one week, and I like it.

Now I want to install A2SD by myself. Firstly in recovery mode I flash the A2SD's install ZIP,

then I want to edit boot.img to mount ext2 partition.

I successfully unpack boot.img, Extract the ramdisk, and edit default.prop to following:

ro.secure=0

ro.allow.mock.location=0

ro.debuggable=1

persist.service.adb.enable=1

and I edit init.rc to following:

export TERMINFO /system/etc/terminfo

   ...

start sysinit

on property:cm.filesystem.ready=1

   ...

# Execute files in /etc/init.d before booting

service sysinit /system/bin/logwrapper /system/xbin/busybox run-parts /system/etc/init.d

disabled

oneshot

then I use the mkbootfs binary to recreate the ramdisk(new-ramdisk), and run the following command to repack the boot.img.

$ mkbootimg --cmdline 'mem=128M console=ttyMSM2,115200n8 androidboot.hardware=qcom console=ttyUSBCONSOLE0 androidboot.console=ttyUSBCONSOLE0' --kernel ./boot.img-kernel --ramdisk ./new-ramdisk -o /new-boot.img

Every step's result seems success, and the new boot.img's size is same as the FLB's custom ROM.

But when I flash the new boot.img to my pulse, the pulse can't boot.

Then I flash the boot.img from FLB1.4's custom rom, the pulse can't boot too.

Is there any wrong in my unpack and repack steps? Or code edit?

Thanks , sorry for my poor english.

[Guest BigBearMDC]

Hi, flibblesan and BigBearMDC and this forum's everybody.

Thank you for your excellent work and MoDaCo forum, I'm a new pulse's user from China.

I've been using the T-mobile official 2.1 update for one week, and I like it.

Now I want to install A2SD by myself. Firstly in recovery mode I flash the A2SD's install ZIP,

then I want to edit boot.img to mount ext2 partition.

I successfully unpack boot.img, Extract the ramdisk, and edit default.prop to following:

ro.secure=0

ro.allow.mock.location=0

ro.debuggable=1

persist.service.adb.enable=1[/code]




and I edit init.rc to following:

  
[code]export TERMINFO /system/etc/terminfo

   ...

start sysinit

on property:cm.filesystem.ready=1

   ...

# Execute files in /etc/init.d before booting

service sysinit /system/bin/logwrapper /system/xbin/busybox run-parts /system/etc/init.d

disabled

oneshot

then I use the mkbootfs binary to recreate the ramdisk(new-ramdisk), and run the following command to repack the boot.img.

$ mkbootimg --cmdline 'mem=128M console=ttyMSM2,115200n8 androidboot.hardware=qcom console=ttyUSBCONSOLE0 androidboot.console=ttyUSBCONSOLE0' --kernel ./boot.img-kernel --ramdisk ./new-ramdisk -o /new-boot.img

Every step's result seems success, and the new boot.img's size is same as the FLB's custom ROM.

But when I flash the new boot.img to my pulse, the pulse can't boot.

Then I flash the boot.img from FLB1.4's custom rom, the pulse can't boot too.

Is there any wrong in my unpack and repack steps? Or code edit?

Thanks , sorry for my poor english.

Use gzip to create the ramdisk, that works fine for me.

I don't know the exact command right now, but I'll post it in anfewnhours if that's ok. You can also have a look at the official Android side from google, just google 'unpack and repack boot.img', the gzip command to repack the ramdisk is there :huh:

Best regards,

BB

[Guest mryongzhang]

thank you very much.

I just unpack and repack boot.img according to the following link's method.

http://android-dls.com/wiki/index.php?titl...ack_Boot_Images

and now I will try to use gzip to create the ramdisk.like this:

find . | cpio -o -H newc | gzip > ../new-ramdisk.cpio.gz

hope to success. :huh:

Edited August 26, 2010 by mryongzhang

[Guest BigBearMDC]

thank you very much.

I just unpack and repack boot.img according to the following link's method.

http://android-dls.com/wiki/index.php?titl...ack_Boot_Images

and now I will try to use gzip to create the ramdisk.like this:

find . | cpio -o -H newc | gzip > ../new-ramdisk.cpio.gz

hope to success. :huh:

Exactly thatls the right command ;)

If it still refuses to boot (maybe because you tried to mount the wrong partition) you can run 'adb shell' and have a look at the output from logcat, bugreport, dmesg and kmsg (kmesg is in /proc, run cat /proc/kmsg).

Best regards,

BB

[Guest Chinese farmers]

搞鸡巴 我也是中国人 你在中国哪个论坛混啊 交流交流啊

用google翻译看了一下 听别人说 好像是mkbootimg这个工具的原因 这个工具一定要是8220的

我去你妈的鸟文

[Guest BigBearMDC]

搞鸡巴 我也是中国人 你在中国哪个论坛混啊 交流交流啊

用google翻译看了一下 听别人说 好像是mkbootimg这个工具的原因 这个工具一定要是8220的

我去你妈的鸟文

I think I need an interpreter here.

Google translater fails epic while translating this, sorry :huh:

Best regards,

BB

[Guest Chinese farmers]

Master, your flb1.5 and http://u.115.com/file/f17b40cc30

Not compatible, what the solution you

高手,你的flb1.5与 http://u.115.com/file/f17b40cc30

不兼容 ，有什么办法解决吗

[Guest mryongzhang]

搞鸡巴 我也是中国人 你在中国哪个论坛混啊 交流交流啊

用google翻译看了一下 听别人说 好像是mkbootimg这个工具的原因 这个工具一定要是8220的

我去你妈的鸟文

哥们儿，虽然你是在英文论坛用汉语打字，但是你也最好不

[Guest mryongzhang]

I think I need an interpreter here.

Google translater fails epic while translating this, sorry :huh:

Best regards,

BB

haha，Chinese farmers said: Maybe there's some wrong with mkbooting, the mkbooting muse be pulse's mkbooting.

Is that right?

so, where can I download a pulse's mkbooting tool?

BigBearMDC, can you send me one?

thanks.

Edited August 26, 2010 by mryongzhang

[Guest irvine]

Master, your flb1.5 and http://u.115.com/file/f17b40cc30

Not compatible, what the solution you

高手,你的flb1.5与 http://u.115.com/file/f17b40cc30

不兼容 ，有什么办法解决吗

你好 中国农民先生

Have you tried the FLB1.4 ROM from "this thread?

[Guest rjm2k]

http://android.modaco.com/content/t-mobile...g-a-custom-rom/

see post 11, much easier way of adding a2sd

[Guest Chinese farmers]

哥们儿，虽然你是在英文论坛用汉语打字，但是你也最好不

[Guest mryongzhang]

外国人要是能把我说的 看懂了 哪我在也不来这论坛了 哈哈

支持你啊 我好像学啊 就是看不懂 鸟文 烦啊

太烦了

你在bbs.hiapk.com叫什么

在安卓网的ID跟这个是一样的，也叫mryongzhang

[Guest mryongzhang]

http://android.modaco.com/content/t-mobile...g-a-custom-rom/

see post 11, much easier way of adding a2sd

thanks for your reply.

I just want to use Darktremor Apps2SD 2.7.5 RC3C , but the rom must could mount the ext partition.

so I edit the offical boot.img to mount ext partition.

[Guest mryongzhang]

thank you very much.

I just unpack and repack boot.img according to the following link's method.

http://android-dls.com/wiki/index.php?titl...ack_Boot_Images

and now I will try to use gzip to create the ramdisk.like this:

find . | cpio -o -H newc | gzip > ../new-ramdisk.cpio.gz

hope to success. :huh:

I have tried gzip，but I still fail too..........

[Guest Chinese farmers]

楼猪

他们怎么给你说的哦 你解决了没有 我也想知道

http://bbs.hiapk.com/thread-449943-1-1.html

[Guest mryongzhang]

According to Darktremor Apps2SD's install guide, to add Apps2SD support to custom Rom， we will need to know phone's kernel base address.

Does anybody know Pulse's base address?

Edited August 27, 2010 by mryongzhang

[Guest mryongzhang]

Today I download Phoenix-Kernel, and found mkbootimg in package.

But I use that mkbootimg to Repack the boot.img, it's still fail to boot.

Now I have to give up.

[Guest BigBearMDC]

Today I download Phoenix-Kernel, and found mkbootimg in package.

But I use that mkbootimg to Repack the boot.img, it's still fail to boot.

Now I have to give up.

Okay, try repacking the FLB MOD kernel image. If that works you just made an error in your init.rc. I should have plenty of time to help you the following week (maybe even tomorrow afternoon UTC+2).

Best regards,

BB

[Guest Tom G]

Today I download Phoenix-Kernel, and found mkbootimg in package.

But I use that mkbootimg to Repack the boot.img, it's still fail to boot.

Now I have to give up.

If you upload the failing image we might be able to identify the problem.

[Guest mryongzhang]

If you upload the failing image we might be able to identify the problem.

I just upload the boot.img made by myself, could you make a look?

thank you very much.

boot_new.img

[Guest mryongzhang]

Okay, try repacking the FLB MOD kernel image. If that works you just made an error in your init.rc. I should have plenty of time to help you the following week (maybe even tomorrow afternoon UTC+2).

Best regards,

BB

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

[Guest twrock]

According to Darktremor Apps2SD's install guide, to add Apps2SD support to custom Rom， we will need to know phone's kernel base address.

Does anybody know Pulse's base address?

I have the same question. I assume it is different for 1.5 and 2.1, and maybe even different for different updates of those two rom versions.

Does anyone know how to find that information off of a particular phone?

[Guest Chinese farmers]

楼主啊 你在不在啊

你的mkbootimg能用了吗

能不能给一个给我啊

我想把Recovery中文了

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

谢谢

[Guest Tom G]

I have the same question. I assume it is different for 1.5 and 2.1, and maybe even different for different updates of those two rom versions.

Does anyone know how to find that information off of a particular phone?

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