|
|
Post by dipcore on Oct 12, 2016 1:30:29 GMT
I looked at update.zip and it seems like boot and recovery images are encrypted.
Will you have it plain img, so we can play with it? Or provide some tools to encrypt/decrypt them ?
|
|
|
|
Post by Admin on Oct 13, 2016 6:50:32 GMT
Hi,
The initial images are indeed signed and encrypted, as this is the way the default bootloader and boot process for the MStar SoC works.
We will be providing an update image with a public/private key pair, so users can change the Android distro, install their own system apps, etc.
Hope this helps.
|
|
|
|
Post by dipcore on Oct 13, 2016 16:13:30 GMT
I'm not asking about OTA keys.
Right now it's not a big problem to assemble MstarUpdate.bin file which contains system.img only (and userdata.img, if we need some pre-installed stuff in user area) and flash it without any keys. system.img and userdata.img are plain ext4 images.
But boot.img and recovery.img are encrypted, so there is no way to have custom kernel builds, no way to have custom recovery, no way to at least change ro.security=0 in default build.prop
I know it's possible to build MBOOT with that security option disabled. In that case we can run un-encrypted boot.img and recovery.img
Or as I said we need a tool to encrypt/decrypt them.
|
|
|
|
Post by Admin on Oct 26, 2016 8:01:32 GMT
I was thinking of the bootloader keys, not OTA keys.
We're still working with MStar to see what we are allowed to release.
|
|
|
|
Post by kajkajkaj on Dec 2, 2016 14:26:20 GMT
Where can I read about the recovery procedure? It would be nice to have a fallback if you get the unit completely mangled up.
|
|
|
|
Post by gothicawakening on Dec 31, 2016 14:16:17 GMT
Hi, The initial images are indeed signed and encrypted, as this is the way the default bootloader and boot process for the MStar SoC works. We will be providing an update image with a public/private key pair, so users can change the Android distro, install their own system apps, etc. Hope this helps. Any update on this? I would like to change some values in build.prop, sepcifically ro.sf.lcd_density |
|
|
|
Post by dipcore on Jan 5, 2017 19:26:22 GMT
any update?
|
|
|
|
Post by Admin on Jan 6, 2017 9:08:14 GMT
We're working on a solution that fulfills the technical requirements, business agreements and software licenses. It is a tricky task and decisions are not entirely in our hands.
|
|
|
|
Post by dipcore on Feb 16, 2017 3:18:17 GMT
We're working on a solution that fulfills the technical requirements, business agreements and software licenses. It is a tricky task and decisions are not entirely in our hands. It seems like after some research and reverse engineering I was able to decrypt boot.img and recovery.img and launch it without encryption. I believe my solution does not affect any licensing, only open source tools are used. If you need more info pls contact me. |
|
