0

Had trouble with it for a long time because manufacturer disabled the button to unlock the rooting functionality.

Improve this question
8
  • Bootloaders binaries are signed with OEM's private key. You can't sign them. And they are closed-source and highly vendor-specific. There is no general way to patch them.
    – Irfan Latif
    Feb 25 '20 at 8:04
  • I managed to find an answer to the continuation of my question. Which technically removes any reason for this question. Should I answer this question by it or create a new one?
    – TheK0tYaRa
    Feb 26 '20 at 16:47
  • It'd be better if you post the answer for other's benefit.
    – Irfan Latif
    Feb 26 '20 at 20:09
  • @IrfanLatif Is it really practical to repost info from xda-developers ? It's the post about suboot.sh which works with mtk-su and magiskinit on mtk devices
    – TheK0tYaRa
    Feb 27 '20 at 0:37
  • You can provide a brief description with link so that answer is not useless if link is dead.
    – Irfan Latif
    Feb 27 '20 at 7:16
0

I live in the U.S. and what was once the land of the free is now the land of the locked bootloader. Good luck

https://www.geektrouble.info/explore/android/view/218873

"OEMs/SoC vendors implement a Chain of Trust which must have a hardware-backed root of trust - a cryptographic key. On boot every software component verifies the integrity of the next component before loading it in memory. This chain of trust starts with BootROM (the very first executable code which runs on Power ON) and ends at /system and /vendor partitions. Everything in between - bootloaders, Device Tree, Linux kernel and Android OS code - is verified to be unaltered."

Improve this answer
1

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.