|
|
Posted at 6/2/2015 18:43:05
1#
Last edited by achary In 6/2/2015 18:44 Editor
Hi,
I had identical problem, 100% reproducible.
It turned that the reason for it was a recovery.img produced by mkimage.sh script after kernel and Android build.
When I used recovery.img that is included in stock firmware - then things went fine and I was able to boot the device from my custom Android kernel.
The official wiki on hereclearly suggests using recovery.img and for some reason the recovery.img seems not to run out of the box after I got it built on my Ubuntu machine.
Hope that helps a bit
Regards,
|
|
