Database Develop

[ROOT][6.0][XT1097] Systemless root for Moto X 2014

Hello, everyone!
TL;DR: You're about to perform a systemless root installation on your phone so make sure you have uninstalled Xposed Framework, uninstalled root, the device's bootloader is unlocked and your phone's boot image is in its untouched stock state. Then boot into TWRP and install SuperSU-v.279-SR3 or newer.
UPDATE 2017-01-19:
- Provided missing bootloader information regarding root. Thanks, @Charlita for the heads-up!
- Moved TL;DR section to the top.
UPDATE 2017-01-15:
- SuperSU-v.279-SR3 learned how to use systemless mode as default flashing method for Motos. This is great news as the installation process now is just a matter of flashing the SuperSU installer. The segmentation fault had been fixed on SR2 and this version also includes that fix.
- Included a TL;DR section.
UPDATE 2016-12-25:
- SuperSU-v.279-SR1 contains a regression bug regarding the "segmentation fault". Skip this version for now. I've already contacted Chainfire.
- suhide: as the Chainfire himself stated, the tool is a losing game so I'm not putting any further effort here.
UPDATE 2016-11-03:
- As of SuperSU-v2.78-SR3 boot image patching works out-of-the-box. Just install it and you're done!
- TWRP version 3.x works as expected.
- Unfortunately, SafetyNet checking fails as Google constantly updates the server-side code.
- WIP: Check if Chainfire's suhide are able to help here.
UPDATE 2016-08-08:
- Added a backup reminder.
- Added flashable zip systemless_root_enabler_by_glauberlima.zip.
After a few days playing with it, I finally managed to perform a systemless root install for our beloved Moto X 2014
Benefits:
- Install OTA updates when they arrive;
- SafetyNet checking will pass so Android Pay can be used (not available in Brazil yet).
Requirements (links below) :
- Android 6 Marshmallow
- Bootloader must be unlocked otherwise you won't be able to root your phone;
- Boot partition must be in its original untouched stock state otherwise, SuperSU installer won't be able to patch it;
- System partition must be untouched as well but a simple uninstall of applications that have changed it should be enough. This step is not mandatory but if your system partition remains changed SafetyNet checking will fail;
- Your device must be unrooted. SuperSU has the option "Completly remove root". Use it;
- If you have Xposed Framework installed, uninstall it;
- You'll need ADB and Fastboot in order to flash stock boot.img if applicable;
- TWRP. Version 3.0.2-2 works just fine. If you prefer 2x series, I highly recommend version 2.8.7.1;
- SuperSU-v2.79-SR3 zip installer (or a newer version). DO NOT TRY AN OLDER VERSION. WILL NOT WORK;
Install guide:
- Make a Nandroid backup first using TWRP;
- Uninstall Xposed Framework if applicable;
- Uninstall SuperSU;
- Connect your device to your computer via USB;
- Reboot into bootloader:
Code:
adb reboot-bootloader
- Restore stock boot partition (you can skip this step if you already been on stock boot):
Code:
fastboot flash boot xt1097_boot_stock_with_may_2016_update.img
VERY IMPORTANT: The binary file boot xt1097_boot_stock_with_may_2016_update.img is device dependent. I have extracted stock boot.img from victara May 2016 update full ROM package and put it here. If you are trying on the other variants, make sure you will use the right image.
- Reboot into Recovery (TWRP);
- Flash the attached zip file systemless_root_enabler_by_glauberlima.zip. This will set both variables SYSTEMLESS=true and BINDSYSTEMXBIN=false. Without these variables set, SuperSU will fail to systemless root the device. Feel free if you want to manually enter the commands in the Command Prompt:
Code:
adb shell "echo SYSTEMLESS=true>/data/.supersu"
adb shell "echo BINDSYSTEMXBIN=false>>/data/.supersu"
- Install SuperSU and reboot system. If the first boot fails, just wait - the second will work I promise you!
- As soon as Android UI shows up you should be systemless rooted;
- Confirm SuperSU is installed by recognizing the green icon on your app drawer;
- Open up any root app you have. The world-famous Superuser permission request dialog should pop-up;
- Install SafetyNet Helper, in order to attest your Android, is passing Google's SafetyNet checking: https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample
Now you should be good. Congrats!
Go ahead and get some systemless apps:
- Systemless Xposed Framework
- Systemless Adaway
This procedure should work for the other variants too - all you need is the original boot.img
If you need any help feel free to ask.
Attached you can find the screenshots taken from my XT1097 after the procedure
Related links:
SuperSU-v2.79-SR3:
https://download.chainfire.eu/1021/SuperSU/SR3-SuperSU-v2.79-SR3-20170114223742.zip
Latest stable SuperSU:
http://download.chainfire.eu/supersu-stable
Systemless Xposed Framework:
http://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268
Systemless AdAway:
http://forum.xda-developers.com/showthread.php?t=2190753
Material Design Xposed Installer:
http://forum.xda-developers.com/xposed/material-design-xposed-installer-t3137758
Minimal ADB and Fastboot:
http://forum.xda-developers.com/showthread.php?t=2317790
TWRP for Moto X 2014:
http://forum.xda-developers.com/mot...recovery-twrp-2-8-0-0-touch-recovery-t2911523
Thanks:
@Chainfire

Even if I am on stock I have to flash boot*.img?
Sent from my XT1097 using Tapatalk

rtrotsky said:
Even if I am on stock I have to flash boot*.img?
Sent from my XT1097 using Tapatalk
Click to expand...
Click to collapse
Since your device already has the untouched stock boot you don't need to flash anything.

I seem to be having trouble installing the "Systemless Xposed". It errors out with - ! Failed: Unable to extract zip file!
I have verified "systemless root - ver 2.76" and tried re-downloading the zip. Any thoughts?

jbaumert said:
I seem to be having trouble installing the "Systemless Xposed". It errors out with - ! Failed: Unable to extract zip file!
I have verified "systemless root - ver 2.76" and tried re-downloading the zip. Any thoughts?
Click to expand...
Click to collapse
Could you provide your recovery.log from TWRP so we can see the detailed logging information?
You can pull it from your device by running the following command in command prompt:
Code:
adb shell cat /tmp/recovery.log | clip
This will copy recovery.log contents to the clipboard. Paste it into notepad then save and attach here.

glauberlima said:
Could you provide your recovery.log from TWRP?
You can pull it from your device by running the following command in command prompt:
Code:
adb shell cat /tmp/recovery.log | clip[code]
This will copy contents to the clipboard. Paste it in notepad then save and attach here.[/QUOTE]
This is pretty neat. Given what I read as the requirements am I correct this only works with stock ROM? (and test will only pass on stock).
Click to expand...
Click to collapse

vpxf said:
This is pretty neat. Given what I read as the requirements am I correct this only works with stock ROM? (and test will only pass on stock).
Click to expand...
Click to collapse
Hi @vpxf
The unmodified boot.img is a requirement for SuperSU as it tries to patch the boot image on-the-fly during the install process (by the time you flash it using TWRP). If the image is not in its original state, SuperSU will fail to install in systemless mode.
Regarding your question about custom ROMs compatibility I don't know if the SafetyNet checking will pass/fail. That's a good test to perform.

glauberlima said:
Could you provide your recovery.log from TWRP so we can see the detailed logging information?
You can pull it from your device by running the following command in command prompt:
Code:
adb shell cat /tmp/recovery.log | clip
This will copy recovery.log contents to the clipboard. Paste it into notepad then save and attach here.
Click to expand...
Click to collapse
I've attached the log. I did notice "unzip: zip flags 1 and 8 are not supported".
NOTE: I was able to flash the 85.7 version found in the second post of the "Systemless Xposed" thread. The newest 86.2 is the one giving me troubles.

As glauberlima found out in the other thread, you need to re-zip the xposed installer with 7-zip (that's what i used at least) and the install will work.

bertolehm said:
As glauberlima found out in the other thread, you need to re-zip the xposed installer with 7-zip (that's what i used at least) and the install will work.
Click to expand...
Click to collapse
jbaumert said:
I've attached the log. I did notice "unzip: zip flags 1 and 8 are not supported".
NOTE: I was able to flash the 85.7 version found in the second post of the "Systemless Xposed" thread. The newest 86.2 is the one giving me troubles.
Click to expand...
Click to collapse
As stated by @bertolehm I've discussed in the other posts the exactly same issue with the zip installer you have reported @jbaumert. Take a look at them:
http://forum.xda-developers.com/showpost.php?p=67792193&postcount=1193
http://forum.xda-developers.com/showpost.php?p=67805517&postcount=1233
Regarding your device being systemless rooted check with SafetyNet Helper Sample app. If everything turns green you are good

** Duplicated **

Thanks for the tutorial.
The first boot fails, ok ; but how long is the second boot ?
I wait a long time (around 15 minutes) blocked at the first screent (static moto logo) and I stop it, reboot and reinstall my backup. I panic a little

oyoyl said:
Thanks for the tutorial.
The first boot fails, ok ; but how long is the second boot ?
I wait a long time (around 15 minutes) blocked at the first screent (static moto logo) and I stop it, reboot and reinstall my backup. I panic a little
Click to expand...
Click to collapse
Which variant is your X?

glauberlima said:
Which variant is your X?
Click to expand...
Click to collapse
XT1092

oyoyl said:
XT1092
Click to expand...
Click to collapse
15 minutes... That's definitely too much.
I'm about to update this guide with my new findings so If you don't mind I'd like to suggest you this:
Repeat the steps but this time skip the update to latest version. After the reboot access SuperSU. It should display a message regarding your su needs update. Accept it.
Make sure your nandroid backup is up to date.

Same thing, but it's possible that my boot image is not up to date and I have no other boot backup to test.
I have only a complete backup (boot + system without root), perahps I'll try later with complete restore ...
Thanks

Something went wrong, the root works fine, but when I run the SafetyNet test, I got "CTS profile match: false", I just want to keep the OTA upgrades working, if I did something wrong, is there any way to unroot and do the systemless root again?? Thankss

Hi! Hey, I followed the steps and my MotoX got stuck when rebooting after flashing. I'm trying to enter fastboot with power+Volume down but no luck so far, any idea? I hope you can help me!

oyoyl said:
Same thing, but it's possible that my boot image is not up to date and I have no other boot backup to test.
I have only a complete backup (boot + system without root), perahps I'll try later with complete restore ...
Thanks
Click to expand...
Click to collapse
OK. Just leave a reply by the time you have the result of your test.

guilhermoaraujo said:
Something went wrong, the root works fine, but when I run the SafetyNet test, I got "CTS profile match: false", I just want to keep the OTA upgrades working, if I did something wrong, is there any way to unroot and do the systemless root again?? Thankss
Click to expand...
Click to collapse
One of your installed apps modified system partition. Did you test on a completly stock image?

Xperia X Performance root 7.1.1 + PS4 remote play/android pay OK+ Safetynet OK +DRM

I have done the update to 7.1.1 with Magisk v13beta https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589 . The steps below still more or less works on Android 7.1.1
--------------
After playing with the Xperia XP for 2 days over weekend, I finally managed to root it with PS4 remote play and Safetynet working. (If Safetynet is working, games like Pokemon and app like Android pay should work with rooted phone as well)
Before you do anything, backup the TA partition first. You have to downgrade back to version 6.0.1 to backup the TA partition. Flash your phone back to 6.0.1 first. (If you don't know how to flash a firmware, https://forum.xda-developers.com/xperia-xz/how-to/how-to-flash-firmware-using-flashtool-t3523946)
Download 6.0.1 firmware here. By backing up the TA partition, in case if you want to roll back to stock rom with valid DRM key , you can install the original DRM key back into your phone. You need this if you want your warranty in case you need to fix your phone.
Download and install backupTA_v2
https://forum.xda-developers.com/crossdevice-dev/sony/universal-dirtycow-based-ta-backup-t3514236
Backup TA partition
1) Ensure you have adb access (e.g. drivers installed, install flashtool)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you encounter issue on installing drivers, follow this to disable driver signature first.
https://www.howtogeek.com/167723/how-to-disable-driver-signature-verification-on-64-bit-windows-8.1-so-that-you-can-install-unsigned-drivers/
2) Run backupTA.sh (linux) or backupTA.cmd (windows) in the root directory.
3) TA will be saved as TA-ModelNumber-Serial-Timestamp.img in
the backupTA.sh directory.
4. Send this image file to your gmail or something so that your email will permanently keep a copy of this backup TA partition image.
DO NOT GO BEYOND THE LINE BELOW IF YOU CAN'T BACKUP YOUR TA PARTITION.
-----------------
Now, you have done all pre-requisite. We can now start the rooting.
1. unlock phone https://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/
Get into fastboot mode first by holding down volume up button and plug in USB cable to computer, click BLU
You should type in unlock code which you got it from the above Sony link.
2. flash/upgrade to stock firmware 7.0 if phone is not having stock rom, check all erase on flash. Flash it so that it will have both stock firmware and stock boot image. (don't restart phone after flash).
3. flash the TWRP. fastboot flash recovery f:\path_to_downlaod\TWRP-3.0.2-4-dora.img (Download TWRP here)
Also download XP_AndroPlusKernel_v22.zip . Get the newest version for both app if available.
4. go into twrp install UPDATE-SuperSU-v2.79-20161211114519.zip, reboot (Download https://download.chainfire.eu/696/supersu/ or see attachment)
5. start the phone the first time and get into phone, should find out the phone still not rooted. Check Setting > Display , the Bravia engine should have no effect on your display.
7. go into twrp install Magisk-v12.0.zip, reboot (download https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 or see attachment)
8. start magisk, it will open google play to update magisk. reboot
9. go into twrp , install phh’s SuperUser superuser-r310-beta.zip, reboot (download https://superuser.phh.me/ or see attachment)
10. go into phone, open google play, search and install phh’s SuperUser app
11. run SuperUser app, upper right choose setting, choose Superuser access and then choose Apps and ADB
12. run magisk, 2nd checkbox should be check by now. Should show Properly rooted)
13. run magisk, 1st checkbox click and install Magisk v12 , reboot
14. run magisk, upper left menu click, then choose Downloads,install Sony Framework v1, reboot
15. On reboot, the phone should hang during boot up, on boot loop, hold the volume up button , plug the usb cable to computer, until you see the blue light turn on on the top of the phone, and screen stays black
16. flash the XP_AndroPlusKernel_v22.zip boot image. fastboot.exe flash boot f:\path_to_downlaod\boot.img
17. go back into phone once again, run magisk, choose menu upper left, choose modules, find the file Magisk_RemotePlayEnabler_v1.zip, press and hold on that file to select, and install, reboot (download https://forum.xda-developers.com/apps/magisk/module-ps-remote-play-enabler-t3575876 or see attachment)
18. Enable Magisk Hide in Setting of Magisk...can put the remote play in Magisk hide if remote play doesn't work.
18. go back to phone again, run magisk, all 3 checkbox should be all checked and OK. PS4 remote play should work fine as well with root running on phone.
In case if you need to roll back to stock rom with original TA partition, here is the instruction.
1. Backup all the data as your device will reset and formatted after this process.
2. Rename your backed up TA partition and rename it TAbackup.img
3. Boot into TWRP.
4. Plug your device in your pc via USB and check the connection by the command adb devices in command prompt in your fastboot directory.
5. Now run the command adb push TAbackup.img /data/local/tmp/TAbackup.img
6. Then run adb shell dd if=/data/local/tmp/TAbackup.img of=/dev/block/bootdevice/by-name/TA
7. Now flash Stock ROM via FlashTool and your device will have original DRM and stock ROM and Ta partition.

great work! followed your instructions, worked almost perfectly for me (but I am using marshmallow and didn't need to do the remote play or anything but I'm rooted for now)
for those that might do what I did, if you do appear to be unrooted after flashing the kernel, you'll need to flash MagiskSU back again.
Also you'll need to flash a compatible kernel version for your build.
I wasn't able to get remote play working and didn't need it but I guess if I'd like to use Android pay I'll spend more time figuring that one out. But for most I think this guide is a dummy's guide ( I did it ) and it covers everything clearly

Thank you for the guide, sdugoten! I followed your process to a t and indeed, it helped me achieve the intended result. I appreciate the time you spent writing up this guide.
However, I did have to find a lot of extra information by searching XDA to achieve each step. For example, I found that after step 2 (flashing the new firmware), all that really needs to be done is to flash both the AndroPlus Kernel (by downloading the flashable zip, unzipping it, and flashing the boot.img via "fastboot flash boot boot.img) and TWRP via fastboot. I found that by NOT doing this, my phone would not boot (due to the stock ROM not accepting a custom recovery w/o a custom kernel). From there, reboot into recovery to flash Magisk v12, reboot the device, go through first-time setup, update Magisk Manager, and enable Magisk Hide. At this point, all three checkmarks in Magisk Manager should show up as green, indicating a successful install. This eliminates flashing both SU beta zips. Installing the Sony Framework and RemotePlayEnabler should be OK in the same step as well. I hope this helps! If anyone wants me to write out a detailed guide as to how I went about this, just let me know!

I have done similar steps and able to get XP Performance running on Android v7.1.1 with Magisk v13 beta and Safetynet working

@sdugoten Your DRM fix isn't complete. It's missing the Device Key (DK). Here are instructions how to make one. Important: Once you have created your DK.ftf, you need to use Flashtool 0.9.22.3. Other Flashtool versions don't install it.

Hi, i'm trying to do this tutorial... Everytime i flash something, a write a "diary" of what i'm doing, just in case of problems. and this is that case.....
i have unlocked bootloader, and done root many months ago, never backup TA partition, so i know what it mean, and so, i've skip step 1 and start from 2.
installed flashtool 0.9.23.1
installed adb and fastboot drivers
enabled in developer debug usb and unknow sources and when connected phone to pc, allowed debug to pc, and allowed supersu to adb.
start flashtool
volume up and plug cable, blu led appear, flashtool says me to install driver from driver folder, installed only fastboot and flashtool drivers (i disabled verify of firma driver)
flashtool says device connected in fastboot. i think is not right, then unplug, volume down and plug, flashtool ays device connected in flash mode
click on flash, selected flashmode, selected right folder of .tft, and selected all the checkboes in wipe tab, and then click in flash.
02/009/2017 22:09:11 - INFO - Device connected in flash mode
02/009/2017 22:09:28 - INFO - Selected Bundle for Sony Xperia X Performance(F8131). FW release : 41.2.A.2.199_R2D. Customization : Switzerland Generic_1302-9924
02/009/2017 22:09:28 - INFO - Preparing files for flashing
02/009/2017 22:09:54 - INFO - Please connect your device into flashmode.
02/009/2017 22:09:54 - INFO - Opening device for R/W
02/009/2017 22:09:54 - INFO - Reading device information
02/009/2017 22:09:54 - INFO - Phone ready for flashmode operations.
02/009/2017 22:09:54 - INFO - Opening TA partition 2
02/009/2017 22:09:54 - INFO - Current device : F8131 - CB512AJSMZ - 1302-9940_R3C - 1300-5321_39.2.A.0.417 - GENERIC_39.2.A.0.417
02/009/2017 22:09:54 - INFO - Closing TA partition
02/009/2017 22:09:54 - INFO - Start Flashing
02/009/2017 22:09:54 - INFO - No loader in the bundle. Searching for one
02/009/2017 22:09:55 - INFO - No matching loader found
02/009/2017 22:09:55 - WARN - No loader found or set manually. Skipping loader
02/009/2017 22:09:55 - INFO - Loader : S1_Root_de8d - Version : 1299-4832_S1_Boot_MSM8996_LA2.0_N_110 / Boot version : 1299-4832_S1_Boot_MSM8996_LA2.0_N_110 / Bootloader status : ROOTED
02/009/2017 22:09:55 - INFO - Max packet size set to 4M
02/009/2017 22:09:55 - INFO - USB buffer size set to 512K
02/009/2017 22:09:58 - INFO - Parsing boot delivery
02/009/2017 22:09:58 - INFO - No flash script found.
02/009/2017 22:09:58 - INFO - Flash script is mandatory. Closing session
02/009/2017 22:09:58 - INFO - Ending flash session
02/009/2017 22:09:58 - INFO - Flashing finished.
02/009/2017 22:09:58 - INFO - Please unplug and start your phone
02/009/2017 22:09:58 - INFO - For flashtool, Unknown Sources and Debugging must be checked in phone settings
02/009/2017 22:09:58 - INFO - Device connected in flash mode.
Tried this 3 times and still not working, So, i've downloaded the stock firmware directly from flashtool, took me 14mins, then retry to flash... i can't flash because the file downloaded is not a tft, and flashtool has extract it in a lot of files..... how can i flash stock rom?!?! i'm wrong?

25agosto said:
installed flashtool 0.9.23.1
Click to expand...
Click to collapse
As I posted one post above you, you need to use Flashtool version 0.9.22.3. Other versions such as 0.9.23.1 won't work.

Hi
8. start magisk, it will open google play to update magisk. reboot
Doesnt work. Google play says App Not Found. Cant update then.
How to proceed ?!
I downloaded the newest magisk manager apk and installed it manually.
Also i try to use magisk v13.3 but Im stuck again here
12. run magisk, 2nd checkbox should be check by now. Should show Properly rooted) -> doesnt show root / how should it be shown? safety net test passed?
13. run magisk, 1st checkbox click and install Magisk v12 , reboot -> wants to install v13.3 when i click checkbock
14. run magisk, upper left menu click, then choose Downloads,install Sony Framework v1, reboot -> framework install keeps crashing magisk manager app. sometimes immediately / sometimes flashes and says magisk not installed + crash
--------------------
Update
I deinstalled SU and magisk app and run magiskuninstaller.
started to do every step again. this time i stay on v12.0 and when install SU app and give permission ADB/APP Magisk Manager first time crashes.
Then i run magisk manager, grant SU rights. Nothing is rooted. Screen looks totally different then your picture....
When i try to install magisk v13.3 via manager following error occurs: boot image patched by other programms / please restore stock boot image
framework install keeps crashing magisk manager app. probably cuz of missing root
now i when i try to run magsikuninstaller.zip via twrp it drops me
!Boot image patched with other programms
cannot uninstall with this uninstaller
----------------------
SEE LATEST POST for updates!
----------------------
please help!
Thank so much !

sdugoten said:
I have done similar steps and able to get XP Performance running on Android v7.1.1 with Magisk v13 beta and Safetynet working
Click to expand...
Click to collapse
see next post

i just found out why all this is happening
i was on newest FW which was wrong
i followed every step an took correct firmware for v22 kernel
magisk manager is no longer on google
then you go install newest version viia APK download but after 5.0 its not more compatible with v12.
so i installed old version of magisk manager 4.3.3 manually
then i get the root thing done BUT NOW im stuck on step 13. cuz when you click install. it wants to download v13.3. and you cant force to install from sd card.
v13.3 wont work with 4.3.3 manager
-------------
update
you can probably mark this thread as outdated cuz the instructions leading nowhere.
i flashed 7.0 clean install. did twrp. did the su flash from step 4
then on step 7 ( i saw you forgot step 6, lol)
i want to install v13.3 instead of v12
to proceed with latest magisk manager.
but its unable to repack boot.img on flashing Error1
also happens with v13.2 and v13.1
so only v12 is working correctly on flashing in twrp - (even I thought the newer v13.3 should be downwards compatible?).
but then you get stuck as described in my very first post with missing manager in play store
how to fix it see following update post
----
update
so when doing the flash from v13.3 with the newest manager installed BEFORE (right after v12 twrp flash step)
THEN it succeed. MEANS
install v12 via twrp. install latest manager. install v13.3 via TWRP (now works)
then i flash the superuser. download phh app via playstore. grant SU access. reboot. like in OP described.
now i got both first field green. so ready to install framework
BUT when installing it. magisk manager (latest version) crashes and installing fails......
it says _> magisk not activated in flashing process
also no success with the zip in twrp
tried to proceed with kernel fastboot flash after this framework v1 fail.
but NOW it says magisk is not installed
then i twrp flashed v13.3 again. reboot. okay both checkboxes green again!
then you need to flash remoteplayenabler v1 via twrp.
then you have all 3 things green.
SUCCESS. :fingers-crossed::victory:
---------------------
UPDATE:
After all 3 field green i needed to install the latest Superuser form chainfire v82 R3.
Now Magisk wants me to install 13.3 again when i start the device. Also the Safety Check both fails and is red.
Installation fails via APP and TWRP! How can i try to fix it?
Do I need to start from Step 4 again?
How to keep everything Up 2 Date : Like FirmWare and SuperUser?
Thanks for your help!

guys i need help i tried twice and keep ending up with ERROR - Processing of system.sin finished with errors.
yes develop and usb debug is on, what am i doing wrong i want to dowgrade from 7.1.1 to 6.0.1 and root after backed up that key

guys i need help i tried twice and keep ending up with ERROR - Processing of system.sin finished with errors.
yes develop and usb debug is on, what am i doing wrong i want to dowgrade from 7.1.1 to 6.0.1 and root after backed up that key

Mate 10 Pro lost root

Hi guys
I have rooted my mate 10 pro using the guides from this forum and everything worked like a charm.
Now I wanted to check on my adaway to install the latest block lists and it said that the phone has to be rooted. So I opened my SU and it said root undetected.
I haven't done any updates or what else could have caused the loss of root.
Any ideas on how that could have happened?

Aval0n1979 said:
Hi guys
I have rooted my mate 10 pro using the guides from this forum and everything worked like a charm.
Now I wanted to check on my adaway to install the latest block lists and it said that the phone has to be rooted. So I opened my SU and it said root undetected.
I haven't done any updates or what else could have caused the loss of root.
Any ideas on how that could have happened?
Click to expand...
Click to collapse
Which SU were you using? SuperSU, PHH Superuser or Magisk?
I do know that SuperSU sometimes loses root, a reboot usually fixes it. Or flash it again.
If SuperSU or PHH I recommend switching to Magisk. It has modules that you can install and uninstall easily and ad-blocking is one of them (Unified hosts block).
You would need Twrp to install it the easiest way, you can get that here: https://forum.xda-developers.com/mate-10/development/huawei-mate-10-pro-twrp-3-2-1-0-t3769904
And Magisk from here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Flash TWRP if you don't have it already, and if your current doesn't have decrypt support:
Then simply reboot to fastboot mode (Vol down + USB + power).
Then use the command
fastboot flash recovery_ramdisk twrp.img
After you have flashed TWRP, type 'fastboot reboot', and hold Vol up + Vol down (while USB is still plugged in).
When in TWRP, enter pin/password to enable decryption.
Transfer Magisk to sdcard and flash using Install button.
If it says ramdisk is already patched you will have to restore stock image. You can do this by downloading your current firmware update.zip from http://pro-teammt.ru/firmware-database/
When you have update.zip, extract update.app from it and download Huawei Update Extractor.
Extract and open Huawei Update extractor, then go to settings and disable Header check (else it will give you an error when you open update.app).
Open update.app in the program and rightclick on Ramdisk and Extract Selected. Now go to fastboot mode and flash 'fastboot flash ramdisk ramdisk.img'.
After this go back to TWRP and flash Magisk again.
After it is flashed open Magisk Manager, tap the hamburger menu and then on Downloads. Here you can download modules. Unified Hosts block is the one you'd want for ad-block. When it is flashed, reboot and open a terminal app. Use the command 'hosts' to enter the Unified hosts block interface. I only use 'm' for ad blocking.
You could set up Adaway systemless blocking with Magisk too if you prefer Adaway.

Thank you for your help! I have Super SU and the reboot fixed the problem.
I will go through your post and use the tips you gave!
Thank you again!!

[GUIDE] OTA updates with Magisk

If you have managed to root your phone with Magisk, getting updates after that for the stock ROM isn't always a smooth thing. Here are some steps to be successful with updates.
1. Open Magisk Manager and disable all installed modules by unchecking the circle for each.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Please note that steps 2-4 can be done with the stock 1+ updater so long as it senses that you are rooted and offers to download a full rom. So a note about magisk hide which is used to hide root. Make sure you haven't managed to hide root for any process related to the 1+updater or it won't know you are rooted and will offer incremental updates.
2. Install Oxygen Updater (This app may become abandoned in 2019 requiring the use of the stock updater which is slower or manually downloading roms.) https://play.google.com/store/apps/details?id=com.arjanvlek.oxygenupdater
3. Open the app, verify that your device is identified correctly. Open it's settings and set Update Method to "Full Update"
4. Check for an update and download it. Make sure you end up with a full 2GB ROM image not an incremental small one. It will be in the root of internal storage.
DO NOT use Oxygen Updater to update the phone (unless you have TWRP and that is for a different GUIDE)
5. Open the built in OnePlus updater: Settings - System - System Updates - Gear - Local Upgrade and select the newly downloaded update. TAKE NOTE while it is installing which slot it is installing too. It will say something like "inactive slot a". Remember this as it is the "new" slot.
6. After it has installed DO NOT reboot the phone or you will lose root. Open Magisk Manager and install Magisk, even though it says "installed". Select the option when it prompts for "after OTA". This will install magisk in the boot partition of the new slot.
7. Reboot and If all went well you shouldn't boot loop and you'll be running the new slot. If you want TWRP (optional), install the zip now from Magisk->Modules->+ (sign) then select the TWRP zip file and install it. Do NOT reboot. Then do a "Direct Install" of Magisk again, then reboot.
8. Open Magisk Manager and go to the downloads section and reinstall the modules you want to use. Do this from the Downloads screen or using the + button on the Modules screen. This will install them in the current slot.
DO NOT simply reenable the modules with the check mark or you will boot loop. Some modules aren't listed in Magisk and can't be automatically moved from slot to slot. If you installed one of those previously, you must reinstall it with the plus button manually from the modules tab.
You should be done now.
Oh no I'm boot looping: Don't panic.
1. Make sure you have adb/fastboot 1.4.3 or newer on a PC https://forum.xda-developers.com/showthread.php?t=2317790
2. Boot the phone into Bootloader/fastboot either through the recovery menu or VolDn + Pwr
3. If in step 5 above the inactive slot was "a", issue the command from a PC command prompt:
fastboot --set_active=b
or vice versa
fastboot --set_active=a
If you are not sure which to use try one or fastboot getvar current-slot
4. Then: fastboot reboot
This will allow the phone to boot into the last good ROM version. Now you figure out what went wrong.
Another option If your phone didn't retain root, you can stay in the unrooted slot. download a rooted boot image of your firmware version, place it in the your fastboot pc directory, reboot the phone to fastboot and issue the command: fastboot boot boot.img (or whatever the downloaded image is called.) this is a temporary root that is non destructive. Then do a direct install from Magisk manager even though it already says installed. That will permanently root your boot copy. Then install your modules.
Here is the 9.5.11 1917AA rooted boot image https://www.dropbox.com/s/6csxd9zaa4mihwk/boot_a_backup_2019-08-04_19-05-29.img?dl=0
If your phone looped right after flashing, you may not have disabled Magisk modules properly. You can still disable them from the good slot, swap active slots again using fastboot and see if it boots into the new ROM. If not, swap back to the good old slot again and start over flashing again from the beginning.
If you looped after reenabling your modules, it is possible you only enabled one but didn't install it into the new slot. Again swap back to the good slot and disable the modules. Swap back to the new slot and install the modules again even if Magisk thinks they are there.
If all else fails, you can stay in the good old slot until you sort things. If you are looping in both slots then something really went bad and you have to flash back a full ROM from fastboot. See this thread
https://buzzfire.de/xda/t3931424
Then root again using the rooted boot image above.
You may be able to boot into the old rooted slot and root the new slot with the ota option also.
If you have issues where stuff like Wifi doesn't work, then somewhere along the line or previously you flashed a (boot) image that didn't match the /system image in the slot you were working on. This error will persist in that slot every time you use that slot until it gets a fixed set of images.
Hope this helps!

I updated to 9.5.7 yesterday with following process, which was very simple (also used the same exact process to update to 9.5.6 last week):
Note: This assumes your device is already bootloader unlocked and has developer options enabled.
Download latest twrp.zip to your phone
Download latest magisk.zip to your phone
Download latest twrp.img to your pc
Allow oxygen updater to download/install OTA. It will say 'your device is rooted, a full image will be downloaded'. (If you're not already rooted, this process will still work)
After it completes the installation, do not select reboot. Instead, hold power button and press reboot to bootloader (make sure you enabled Advanced reboot in settings to see that option)
In fastboot and connected to pc, run from pc: fastboot flash boot twrp-3.3.1-3-guacamole.img (or whatever latest version is - you need to do this step because the OTA wipes out twrp if you already had it installed)
Reboot phone to twrp recovery
Flash install the twrp.zip you downloaded above
Flash install the magisk.zip you downloaded above
Reboot System
Done
Using this method, I haven't needed to change the slots at all, as the OOS updater takes care of that and the twrp/magisk flash installs each to both slots. This method preserves all data/settings/root (but I still do a twrp backup just prior to doing the update). I had tried the magisk install OTA to inactive slot option a few times but it never worked for me. This method also eliminates the need to download any patched boot images.

If you are on bootloop, just simply flash magisk_uninstaller.zip on twrp
boot into system > then flash magisk on twrp again.

Perfect manual and working great

gtelnet said:
I updated to 9.5.7 yesterday with following process, which was very simple (also used the same exact process to update to 9.5.6 last week):
Note: This assumes your device is already bootloader unlocked and has developer options enabled.
Download latest twrp.zip to your phone
Download latest magisk.zip to your phone
Download latest twrp.img to your pc
Allow oxygen updater to download/install OTA. It will say 'your device is rooted, a full image will be downloaded'. (If you're not already rooted, this process will still work)
After it completes the installation, do not select reboot. Instead, hold power button and press reboot to bootloader (make sure you enabled Advanced reboot in settings to see that option)
In fastboot and connected to pc, run from pc: fastboot flash boot twrp-3.3.1-3-guacamole.img (or whatever latest version is - you need to do this step because the OTA wipes out twrp if you already had it installed)
Reboot phone to twrp recovery
Flash install the twrp.zip you downloaded above
Flash install the magisk.zip you downloaded above
Reboot System
Done
Using this method, I haven't needed to change the slots at all, as the OOS updater takes care of that and the twrp/magisk flash installs each to both slots. This method preserves all data/settings/root (but I still do a twrp backup just prior to doing the update). I had tried the magisk install OTA to inactive slot option a few times but it never worked for me. This method also eliminates the need to download any patched boot images.
Click to expand...
Click to collapse
You Sir are the good damn man i have spent 3hrs trying to update to 9.5.9 cheers boss!!

Will this method work if I was a TMobile OnePlus 7pro which converted to international running 9.5.8 currently?

Yes if you are offered the aa rom in the updater

@larsdennert I guess you may well know about this:
https://forum.xda-developers.com/oneplus-7-pro/help/oxygen-updater-shutting-november-t3948339

I just start the update under settings, system, syst update
It found new update and tell me he need to download full ROM (I have rmagisk installed).
While it was downloading full ROM I uninstall magisk from magisk app.
After update finish before restart I installed magisk again (option after ota update) and restart.
Now I'm updated and with magisk installed
Inviato dal mio GM1913 utilizzando Tapatalk

SlyUK said:
@larsdennert I guess you may well know about this:
https://forum.xda-developers.com/oneplus-7-pro/help/oxygen-updater-shutting-november-t3948339
Click to expand...
Click to collapse
Yes I'm thinking, In the worst case it may be possible to use the stock updater as it senses root and downloads the full update now. Simply substitute the step where oxygen updater is used to download with the stock updater.
There may be a slightly longer delay before the stock updater offers an update as 1+ does it in waves. I have to hand it to 1+for even offering updates as most phones won't.

hi experts,
what and where to set or unset to make sure there is NO auto OTA update?
How do I control the update time on my op7p?
I'd like to avoid surprise of getting update in background that would / can remove root, magisk and etc that were manually added?
as example I use xXx over magisk and I's like to be prepared ahead of time to apply the OTA update
thanks for the education.

The 1+ updater has a setting to auto download updates or not. You can change it.

If we have TWRP installed could we get a guide for using the updater app?

kirschdog1 said:
If we have TWRP installed could we get a guide for using the updater app?
Click to expand...
Click to collapse
This is the method i use. Screenshot it from a thread here on XDA and unfortunately cannot remember the posters name to give credit. But it is the job!

kirschdog1 said:
If we have TWRP installed could we get a guide for using the updater app?
Click to expand...
Click to collapse
I used a method that didn't require uninstalling Magisk modules or even booting into recovery (unless you have issues):
1.) Download FULL OTA from 1+ updater (should be approximately 2gb)
2.) Disable all Magisk modules and substratum themes
3.) Install OTA manually via the system updater in Settings > System > System Updates > Gear in upper right > Local Upgrade **DON'T REBOOT!!!**
4.) Search for TWRP Retention Script in Magisk, install **DON'T REBOOT!!!**
5.) Re-install Magisk from the main page in Magisk Manager App (OTA Option) **REBOOT**
6.) Re-enable Magisk modules and any substratum themes **REBOOT**
If you get stuck in a bootloop due to a Magisk module causing issues (EdXposed did this to me) you can:
Boot Into Recovery (Volume Down + Power Button) > Advanced > File Manager > Navigate to data/adb/modules > Click module you want to disable / delete > Hit bottom right checkmark > Delete > Hit Home > Reboot System
Magisk modules I'm currently running in 9.5.10 with no issues:
- Google Dialer Framework
- Google Product Sans
- liboemcrypto disabler
- OnePlus Google Launcher
- Renovate Ice
- Substratum
- ViperFX
- xxxNoLimitsxxx

i.Design said:
I used a method that didn't require uninstalling Magisk modules or even booting into recovery (unless you have issues):
1.) Download FULL OTA from 1+ updater (should be approximately 2gb)
2.) Install OTA manually via the system updater in Settings > System > System Updates > Gear in upper right > Local Upgrade **DON'T REBOOT!!!**
3.) Disable all Magisk modules and substratum themes
4.) Search for TWRP Retention Script in Magisk, install **DON'T REBOOT!!!**
5.) Re-install Magisk from the main page in Magisk Manager App **REBOOT**
6.) Re-enable Magisk modules and any substratum themes **REBOOT**
If you get stuck in a bootloop due to a Magisk module causing issues (EdXposed did this to me) you can:
Boot Into Recovery (Volume Down + Power Button) > Advanced > File Manager > Navigate to data/adb/modules > Click module you want to disable / delete > Hit bottom right checkmark > Delete > Hit Home > Reboot System
Magisk modules I'm currently running in 9.5.10 with no issues:
- Google Dialer Framework
- Google Product Sans
- liboemcrypto disabler
- OnePlus Google Launcher
- Renovate Ice
- Substratum
- ViperFX
- xxxNoLimitsxxx
Click to expand...
Click to collapse
Question. How do you know it was edxposed module? I'm currently trying to track down. Why I'm still getting SOD after updating from 9.5.9 to 9.5.10

Pvt WhoOkid said:
Question. How do you know it was edxposed module? I'm currently trying to track down. Why I'm still getting SOD after updating from 9.5.9 to 9.5.10
Click to expand...
Click to collapse
I assumed it was and disabled it first, did a reboot and booted up fine. It was a good guess
Best bet would be to delete all modules and start from scratch if you're not sure. It depends what kinds of modules you run.
I had issues of bootloop where I would get past the unlocked message and boot up animation but then would freeze with my background showing only (no launcher, no status bar, etc).

i.Design said:
I assumed it was and disabled it first, did a reboot and booted up fine. It was a good guess
Best bet would be to delete all modules and start from scratch if you're not sure. It depends what kinds of modules you run.
Click to expand...
Click to collapse
Yeah back to the drawing broad for me. Luckily I don't run many modules. Just edXposed , xXx and Riru Core.

Pvt WhoOkid said:
Yeah back to the drawing broad for me. Luckily I don't run many modules. Just edXposed , xXx and Riru Core.
Click to expand...
Click to collapse
I was running Riru Core, edXposed and ended up dropping both, it wasn't worth the hassle for me since I run Renovate Ice and it does most of the tweaks I want from GravityBox (reason I was running Xposed).

Pvt WhoOkid said:
Yeah back to the drawing broad for me. Luckily I don't run many modules. Just edXposed , xXx and Riru Core.
Click to expand...
Click to collapse
Try disabling all the modules and see if you can boot into 9.5.10 slot. If it does, reinstall them (then reenable them)

[RECOVERY][TB-X505F][UNOFFICIAL] TWRP 3.6.x for Lenovo Tab M10 HD

This version of TWRP works on the Lenovo TB-X505F (wifi).
For the TB-X505X, see this thread. For the TB-X605F/L, see this thread.
For the TB-X606F/L, see this thread. The X606F/L is the second gen M10 and it uses a Mediatek SOC.
Code:
#include <std_disclaimer.h>
/*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*/
Working:
AFAIK, everything is working including:
data decryption
MTP
Known issues:
time not adjusting for Daylight Saving
OTA (for a workaround see this post)
Before installing TWRP
Before you install TWRP, upgrade your tablet to the Android 9 (Pie) or Android 10 (Q) stock ROM.
This tablet shipped with Android 8 (Oreo), in which the bootloader did not allow unlocking. When you tried to unlock the bootloader, it gave this error message:
Code:
fastboot oem unlock-go
FAILED (remote: 'unknown command')
fastboot: error: Command failed
Installation
It is recommended that you also install Magisk. This will ensure TWRP remains your default recovery.
Step-by-step guide
download TWRP to your PC (see the Download section below)
download magisk.apk to your MicroSD or OTG device. Get the latest Magisk apk file here. Rename the filetype from apk to zip (for example Magisk-v22.0.zip)
if your bootloader is already unlocked, go to step 4. To unlock bootloader:
on tablet: go to Settings->System->About and press "Build number" 7 times to enable Developer Options.
on tablet: go to Settings->System->DeveloperOptions. Turn on: "OEM unlocking" and "USB debugging".
connect tablet to your computer. Tablet will ask for permission to "Allow USB debugging". Tick "always allow" and select "OK".
backup any files you want to keep to an external device (MicroSD/OTG/computer), because the next step will wipe all your photos, files, google account etc on the tablet.
Now unlock the bootloader:
Code:
adb reboot bootloader
fastboot oem unlock-go
fastboot reboot
flash the twrp image:
Code:
adb reboot bootloader
fastboot flash recovery twrp.img
if you haven't loaded Magisk yet, go to step 6. If you have already loaded Magisk, you can just reboot and you're finished:
Code:
fastboot reboot
adb reboot recovery
load Magisk (step one): reboot to recovery. Do not reboot into the system, because it will over-write TWRP with stock recovery. If that happens, go back to step 4 and start again. When you issue the reboot command (below), you have to immediately press the button combination to reboot to recovery (TWRP). Here are the steps:
issue the reboot command:
Code:
fastboot reboot
immediately press and hold all three buttons (Pwr+VolUp+VolDown). The tablet might reboot twice. Release all the buttons when you see the TWRP screen, or hear your PC acknowledge that ADB is connected.
load Magisk (step two): flash Magisk. In TWRP:
select "Install"
use "select storage" to locate device you stored magisk.zip on.
press the OK button
select the Magisk zip file
swipe to confirm Flash
when Magisk is finished, hit the "Reboot System" button
finished!
If you prefer to use button combos, rather than fastboot/ADB commands:
Vol Down + Power = fastboot mode
Vol Up + Vol Down + Power = recovery mode
Changelog
Code:
01/03/2023 - bug fix: data partition again backs up and restores correctly
20/01/2023 - add TW_EXTRA_LANGUAGES and TB_X505F_S001149_221115_ROW kernel (credit to @Tonyha7 )
30/12/2022 - add system partition to AdvancedWipe (TB_X505F_S001147_220830_ROW firmware only)
15/11/2022 - TWRP 3.7.0-0 update
- support for TB_X505F_S001147_220830_ROW
18/12/2021 - TWRP 3.6.0-0 update
- support for A12 decryption (keymaster)
27/03/2021 - TWRP 3.5.1-0 update
- change to landscape mode for tablets
01/01/2021 - TWRP 3.5.0-0: initial release
Downloads
TWRP 3.7.0-0 for X505F: twrp-X505F_11.img (for TB_X505F_S001147_220830_ROW and above)
TWRP 3.6.0-0 for X505F: twrp-X505F_11_2021.img (for earlier stock ROMs)
Source code
https://github.com/minimal-manifest-twrp/platform_manifest_twrp_aosp/tree/twrp-11
https://github.com/Yahoo-Mike/recovery_device_lenovo_X505F/tree/android-11.0
Credits
The guys at TeamWin Recovery Project.
Everyone whose device trees I plagiarised from GitHub.
Contributors
Yahoo Mike
Tonyha7
Last Updated 2023-03-01 (fix /data backup/restore)
Created 2021-01-01

reserved

Thanks for useful post,
Possible to reboot into recovery from fastboot?

zubair1836 said:
Thanks for useful post,
Possible to reboot into recovery from fastboot?
Click to expand...
Click to collapse
Not that I know of. The bootloader accepts the command fastboot reboot recovery, but boots to system anyway.

Hello there, I've been looking how to install this on my slow tablet for almost like an hour. Could there be some tutorial or extended explanation to the process and installation, I'm such a noob, sorry.

This worked for me. Thank you for your effort and the TWRP!

Worked for me too - many thanks!
Can't wait for a custom ROM!
TWRP Recovery Installation Steps
1. Download android platform tools
2. Unlock developer mode on the M10
3. Enable USB debugging on the M10
3. OEM unlock enable on the M10
4. XDA download TWRP copy to sd
5. Download Magisk app (from Github!!! johnwu), change extension to .zip
6. Adb to fastboot
7. fastboot flash recovery [filename.img]
8. Turn off device
9. Turn on device holding all 3 buttons, release when see Lenovo splash screen
10. In TWRP find Magisk zip
11. Install Magisk
Stock ROM Recovery
1. Download qualcomm drivers 64 bit install
2. Download Lenovo recovery and image tool windows app from Lenovo support website
3. Fastboot oem edl
4. Turn off M10
5. Start recovery windows app, wait till instructions
6. Hold volume up (up is the side of the button closest to the front camera) and insert cable
7. Release button after windows app detects device
8. Troubleshoot by checking windows device manager for the M10 appears as a Qualcomm device

I'm thinking about getting one of these tablets, but before I do so I'd like to know that the screen lock still works after installing TWRP.
This might sound like a crazy question, but my Samsung Tab A won't set a screen lock - pattern, PIN or password - once TWRP has been installed, and I'd rather not run into the same issue again.

Heeni said:
I'm thinking about getting one of these tablets, but before I do so I'd like to know that the screen lock still works after installing TWRP.
This might sound like a crazy question, but my Samsung Tab A won't set a screen lock - pattern, PIN or password - once TWRP has been installed, and I'd rather not run into the same issue again.
Click to expand...
Click to collapse
Confirmed working normally.

zubair1836 said:
Confirmed working normally.
Click to expand...
Click to collapse
Many thanks.

Thank you! TWRP is working fine!
Stupid me flashed before I installed the Android 10 OTA, so I had to temporarily go back to stock recovery. Unfortunately beamingbadger's method didn't work for me.
This is how it worked for me:
Download the OTA via Lenovo's "Rescue And Smart Assistant"
The stock recovery image will be in the Download folder (default path: C:\ProgramData\LMSA\Download\RomFiles) called "recovery.img"
Flash the recovery.img the same way as you would with the twrp img (adb reboot bootloader -> fastboot flash recovery recovery.img)
fastboot reboot
Install OTA
Flash TWRP recovery + Magisk again (follow the steps from the first post, skip bootloader unlock)

The method I use to install OTAs is:
open Magisk App
select "Uninstall Magisk", then the "Restore Images" option
reboot to Android (you will have no root access and stock recovery is restored)
apply OTA
re-flash twrp and install Magisk
NOTE 1: if you've unencrypted your data partition, it will be re-encrypted by this process.
NOTE 2: the new Magisk App (v22) can be installed in TWRP by renaming the *.apk to *.zip. See the new install instructions.

What's involved with running gsi ROMs on this device? It's got the same SoC as my Samsung Tab, which runs them well, so I'm assuming that this tab will also, but I'd like to know if there are any traps that I need to be aware of.

I can partly answer my own question. It all went more smoothly than I expected: installing TWRP, Magisk and then LineageOS R Mod //LiR, followed by Disable_Dm-Verity_enfec.zip.
If I want to try other GSI ROMs, do I need to flash stock before trying another one? I've had some trouble doing that (won't boot) and it's possibly to do with encryption.

Heeni said:
I can partly answer my own question. It all went more smoothly than I expected: installing TWRP, Magisk and then LineageOS R Mod //LiR, followed by Disable_Dm-Verity_enfec.zip.
Click to expand...
Click to collapse
That's great news. Well done.
Heeni said:
If I want to try other GSI ROMs, do I need to flash stock before trying another one? I've had some trouble doing that (won't boot) and it's possibly to do with encryption.
Click to expand...
Click to collapse
On my X605F I do this in twrp for a new GSI install:
format (not wipe) data partition. This is the option where you have to confirm by swiping.
factory reset. This clears the caches.
restore the stock boot and vendor partitions (from a backup I made). This is because Magisk can touch these partitions.
install the GSI system image
install anything else I need like disable_Dm-Verity, Magisk, gapps etc
I don't know what LOS R Mod //LiR does to your system. If it touches any other partitions, you should restore those to stock too.

Thanks for that. It gives me something to go on with. I've downloaded the stock ROM from lolinet, so I can grab the boot and vendor images from that.

I was able to try a couple of other GSI ROMs and I've settled on AndyYan's LineageOS 17.1 for now. The only serious installation issue I had - which I can laugh about in hindsight - was thinking I'd got myself into a very bad bootloop, when all I needed to do was let go of the power button after the Lenovo logo appeared.
On this tablet, there is no navigation capability at all (no navbar, no gestures, no setting to configure them) on installation, and I have to set it using adb. I suspect it goes back to PHH basic ROMs, but I don't feel like doing yet another install and testing right at this moment. Is this happening on the other tablets that you're testing, or is it unique to this one?

I just posted the v3.5.1 update to twrp.
It's also changed to landscape mode, as many of you requested.

Quick question, how do i apply new system updates with twrp installed? Should i not bother? Also, i forgot how to block check for updates!

will this allow flashing of stock roms download from lenovo recovery? ive been stuck on an ancient android 9 version because the ota updater fails.