I don't know why it was so damn hard to find this information for the myTouch4G here on XDA, but here:
For mkbootimg, add:
--base 0x04000000 --pagesize 4096 --cmdline 'no_console_suspend=1'
Well, I haven't needed this but if I ever do, thank you. No one else has replied, but you went to a lot of trouble. I figure a thanks is in order, at least.
Related
Hi all,
Since it took me some time to figure out the correct values I guess this info can be useful to someone out there
1) the boot partition is mmcblk0p20 but it is signed. To get something meaningful out of it you need to drop the head of it
Code:
dd if=/dev/block/mmcblk0p20 of=boot.img bs=256 skip=1
2) to repack you need to pass the options
Code:
--pagesize 2048 --base 40400000
to mkbootimg
Hi,
Does someone knows which codename for the board the SGS+ use?
I know its for SGS2 in the kernel source: arch/arm/s5pv310.
What is it for SGS+?
It is for OC´ing
Netchip
stock kernel
Hi Netchip,
I don't know the codename.
Can somebody confirm following about the stock kernel:
-kernel base address 0x00400000
-pagesize 4096
As soon as I unpack and repack the boot.img (without modifications), the device doesn't boot anymore. Binary comparison between the repacked and original boot.img shows, that the last 30% of the file has changed.
I use the command
> mkbootimg --kernel zImage --ramdisk ramdisk --base 0x00400000 --pagesize 4096 -o repackedBoot.img
The same way workes on HTC and SE devices. Could it be somehow different for S+?
Any idea?
Thanks,
Adrian
I want to mod my stock boot.img for init.d support, but I'm not sure what "base" and "pagesize" parameters to use with mkbootimg. Can anyone help me out?
See here lines 37 and 38
imnuts said:
See here lines 37 and 38
Click to expand...
Click to collapse
Thanks! So, these settings are specific to the kernel. I see that for CM kernel, I would use:
BOARD_KERNEL_PAGESIZE := 4096
BOARD_KERNEL_BASE := 0x40000000
I was also trying to modify the stock boot.img for my device (p3110) and I came across a tool called "unmkbootimg" found here:
http://forum.xda-developers.com/showthread.php?t=1877807
When I use this new tool to extract the stock boot.img, I get this:
mkbootimg --kernel kernel.gz --ramdisk initramfs.cpio.gz --base 0x80000000 --cmdline 'console=ttyO2,115200n8 mem=1024M androidboot.console=ttyO2 vram=20M omapfb.vram=0:16M androidboot.carrier=wifi' -o new_boot.img
When I use the tool to extract the CM10 boot.img, I get this:
mkbootimg --kernel kernel.gz --ramdisk initramfs.cpio.gz --base 0x40000000 --pagesize 4096 -o new_boot.img
cool.
please help...
I tried not go... the system does not boot
need link, HOWTO make boot.img for nexus 5 (zImage+initrd.gz)
./mkbootimg --kernel zImage --ramdisk ramdisk.gz bla-bla-bla.....
tnx
I build the kernel from the source,and packed the zImage into boot.img.
But it did not work, after a burn the boot.img into the phone nx403a.
I will descript the build process and packet proccess ,later.
I build the source ,get the zImage,
and I use "mkbootimg --kernel zImage --ramdisk initramfs.cpio.gz --base 0x80200000 --cmdline 'console=null androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x3F ehci-hcd.park=3 maxcpus=4' -o new_boot.img"
to get the new_boot.img .
But it also doesn't work after I burn it use "dd if=new_boot.img of=\\?\Device\Harddisk2\Partition7".
Hi,
Sir please understand that this forum is not a "helpdesk" providing technical assistance but more to point you in the correct direction with your problem. Perhaps you can't find posts on how to root your phone, install custom recovery or maybe you have questions about how to navigate and use features on the site.
I suggest reading a couple of the relevant kernel tutorials found here....
xda-developers Chef Central Android
Good luck