Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 01/29/2023 in Posts

  1. There is no need to root stock, just to install LineageOS. For that it would have been enough to just unlock the bootloader, no need for Magisk and boot.img patching ... On the other hand, if having root during use of the phone was your goal, you will find that in your newly flashed LineageOS, Magisk and su are now gone. You'll then have to re-install Magisk and re-do the boot.img-patching procedure (this time using the boot.img from payload.bin, contained in the lineage*.zip you used for sideloading).
    2 points
  2. Also, if all you want is root (SU) and you don't care about magisk modules, you can simply use the depreciated method of renaming the magisk file changing the .apk extension to .zip and then using adb sideload to flash it in recovery the same way you do MindTheGapps. I'm not sure you can't also still use Magisk modules that way, but since I don't use them, I can't say. I never even open the Magisk app, but it gives root to any app that asks permission and I say ok.
    1 point
  3. Ahh, that's it, thank you! I ran fastboot right on the "START" screen and it worked. Even worked on my X270 without needing to boot up the Raspberry Pi.
    1 point
  4. I agree with @Hook. That screen in the first screenshot should be shown while you use fastboot to flash the boot.img. adb, on the other hand, does its job only from recovery, not from that bootloader screen. That said, just flashing the Magisk-patched boot.img (which I understand is what you are trying to achieve) does not require any action to be performed from recovery. You should not go there at all for this. The no-command-screen usually indicates that the recovery image fails to boot. It normally should not be shown at any step of a reflashing procedure, and probably indicates t
    1 point
  5. While all our work is public, we don't necessarily post a neon sign saying, "Break ur phone here!" 😉 The Pro1-X work is moderately stable now and has been moved to the official LineageOS org on GitHub: https://github.com/LineageOS/android_device_fxtec_pro1x https://github.com/LineageOS/android_kernel_fxtec_sm6115 You are welcome to use these for your own builds, but please be prepared debug any problems yourself. There are a few outstanding fixes on our gerrit, esp. this topic: https://review.lineageos.org/q/topic:pro1x-old_kbd_driver Also, please remember that although we work
    1 point
×
×
  • Create New...

Important Information

Terms