Hi,
I downloaded the SM-N910F kernel from samsung compiled and burned it with Heimdall. It works fine.
The problem I am facing is when I add some code into the kernel. It won't boot (returns do DOWNLOAD mode screen), error message "could not do normal boot".
Note: I have tried burning my boot.img both with Heimdall (linux) and Odin (windows), and get the same results, i.e. unmodfied kernel works fine, modified -- fails.
It seems to be a zImage size issue.
I tested this by only adding lots of seq_print(m ,"something somthing ....") in print_binder_transaction() (drivers/stagin/android/binder.c). just to make the zImage bigger (unmodified zImage size: 9792000 bytes, bloated zImage 9799072 bytes, only ~7Kb more).
I checked the with busybox fdisk the BOOT partition size, its 17MB.
I pulled the boot.img with dd from the device and used "abootimg -u boot.img -k ../arch/arm/boot/zImage" to update it with my compiled zImage.
any ideas?
missing info?
Thanks,
Daniel.
I downloaded the SM-N910F kernel from samsung compiled and burned it with Heimdall. It works fine.
The problem I am facing is when I add some code into the kernel. It won't boot (returns do DOWNLOAD mode screen), error message "could not do normal boot".
Note: I have tried burning my boot.img both with Heimdall (linux) and Odin (windows), and get the same results, i.e. unmodfied kernel works fine, modified -- fails.
It seems to be a zImage size issue.
I tested this by only adding lots of seq_print(m ,"something somthing ....") in print_binder_transaction() (drivers/stagin/android/binder.c). just to make the zImage bigger (unmodified zImage size: 9792000 bytes, bloated zImage 9799072 bytes, only ~7Kb more).
I checked the with busybox fdisk the BOOT partition size, its 17MB.
I pulled the boot.img with dd from the device and used "abootimg -u boot.img -k ../arch/arm/boot/zImage" to update it with my compiled zImage.
any ideas?
missing info?
Thanks,
Daniel.
No comments:
Post a Comment