Hello,
I try to port Cyanogenmod to my tablet (codename: hwt1a21l/chipset: MSM8916). I build a recovery image according to the CM-Wiki. Target was CM11 because the tablet is based on Android 4.4.4 and huawei have specific downloads for 4.4.4 (kernel source). If this would work, I go further with current CM releases.
After boot into fastboot/rescue and flash the CM-recovery, the tablet restarts repeatly in rescue/fastboot (every time I press the key combination for recovery). If I flash the stock recovery, the stock recovery displays (if I press the combination for recovery).
If I execute a "fastboot boot"-command with my custom image, the output says "signature checking failed". (with "fastboot boot" on an official image, there is no problem, of course)
Bootloader is unlocked. Root access is denied (su command not found and I cannot search through the bin-directories - permission denied). I tried SuperSU, Fararoot, Kingroot, Kingo-Root. If I upload a busybox executable to the device, the shell command of 'busybox su' prints out an error about 'setuid'. A 'chmod s' doesnt work (permission denied).
I have two logs. One log for a working recovery with very detailed information and one with the pre-boot process.
Which steps can be performed to go further? Any hints are welcome :)
I thought about a custom aboot, sbl-hacking, etc but I didnt find any useful information for this case. (ok, I can buy IDA, which is a little bit expansive :))
I read documentation about boot-image signing, but it looks like, that CM do this stuff for me? (keys-file in res is updated)
I try to port Cyanogenmod to my tablet (codename: hwt1a21l/chipset: MSM8916). I build a recovery image according to the CM-Wiki. Target was CM11 because the tablet is based on Android 4.4.4 and huawei have specific downloads for 4.4.4 (kernel source). If this would work, I go further with current CM releases.
After boot into fastboot/rescue and flash the CM-recovery, the tablet restarts repeatly in rescue/fastboot (every time I press the key combination for recovery). If I flash the stock recovery, the stock recovery displays (if I press the combination for recovery).
If I execute a "fastboot boot"-command with my custom image, the output says "signature checking failed". (with "fastboot boot" on an official image, there is no problem, of course)
Bootloader is unlocked. Root access is denied (su command not found and I cannot search through the bin-directories - permission denied). I tried SuperSU, Fararoot, Kingroot, Kingo-Root. If I upload a busybox executable to the device, the shell command of 'busybox su' prints out an error about 'setuid'. A 'chmod s' doesnt work (permission denied).
I have two logs. One log for a working recovery with very detailed information and one with the pre-boot process.
Which steps can be performed to go further? Any hints are welcome :)
I thought about a custom aboot, sbl-hacking, etc but I didnt find any useful information for this case. (ok, I can buy IDA, which is a little bit expansive :))
I read documentation about boot-image signing, but it looks like, that CM do this stuff for me? (keys-file in res is updated)
No comments:
Post a Comment