2015-03-23, 04:16
After further investigations now I can say that the device has a secure boot... and its stock "recovery.img" is signed, as matter of fact its original name is "recovery-sign.img".
Furtermore the boot magic (ANDROID!) is finding at offset 0x4040... I'm not an expert, but I guess that the values at the beginning was a kind of signature and I do not know how to sign an edited recovery.img or an existing one (created by MTKDT, as an example)...
So definively it is not a CTRv2.4 issue.
Please note that a custom CWM recovery for Y330-U01 is out there (and working flawlessly) and I wonder how its creator did in order to sign the recovery.img...
If compared running an HEX editor the stock recovery.img and the custom CWM recovery.img have the boot magic at the same offset (0x4040) although the values are slightly different...
So many thanks the same!
Greetings
Furtermore the boot magic (ANDROID!) is finding at offset 0x4040... I'm not an expert, but I guess that the values at the beginning was a kind of signature and I do not know how to sign an edited recovery.img or an existing one (created by MTKDT, as an example)...
So definively it is not a CTRv2.4 issue.
Please note that a custom CWM recovery for Y330-U01 is out there (and working flawlessly) and I wonder how its creator did in order to sign the recovery.img...
If compared running an HEX editor the stock recovery.img and the custom CWM recovery.img have the boot magic at the same offset (0x4040) although the values are slightly different...
So many thanks the same!
Greetings