Essentially, how I bypassed was check first 7-8 bytes for ANDROID! - in
java: byte androidMagic[] = {0x41, 0x4E, 0x44, 0x52, 0x4F, 0x49, 0x44,
0x21}; //ANDROID!
If that isn't found, skip 256 bytes and check again. With the signed
boot.img files, boot_signed.img, HTC has been using on newer devices
Do you have a specification of this signed format ?
I'm not sure to understand how this works. If the first 256 bytes are
expected to contains a signature key for the boot image, I suppose you
would need an additionnal tool to update this signature ?
--
You received this bug notification because
** Summary changed:
- Not able to process Android "signed" boot.img
+ Not able to process "signed" Android boot.img
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/881977
Title:
Not able to process "
