Can anybody compile mkbootimg for linux x86 or have a up to date compiled mkbootimg? Since the one's I found in other threads dosen't have --base parameter support.
Thx in advance!
Related
Searching mkbootimg binary with "--base" parameter ... for MacOS X ... or Linux.
Thanks a lot
Hello,
I tried to compile aapt for amd64 but can't obtain a 64bits binary file.
I've just typed "make -j2 aapt". Is there somthing to add to this command line to tell to compile in 64 bits ?
Thanks for your help.
Jerome
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 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
Hi,
After researching why one binary is working in both systems (5.0 and 2.3.5) ive found that (is logic i know) static compiled binaries will be work in both versions.
The problem is that the binary will be increased in size a lot, but you don´t need to touch your application and just compile your c code and put in assets folder.
So all the static compiled binaries still will be working in both versions of Android
With the "file" command you can see if is statically compiled:
ELF 32-bit LSB executable, ARM, version 1 (SYSV), statically linked, not stripped
This binary will work in any version of android and you have to compile with the static flag:
arm-linux-androideabi-gcc -static yourcode.c -o youbinary
I said the binary increase the size dramatically but for small binaries maybe its ok.
Regards,
Sylkat