Database Develop

Magic v11 installation question

Hi, do i need install systemless SuperSU always in twrp before install magisk v11 if I want use new MagiskSU instead??
If I try install Magisk v11 with superSU uninstalled and phone unrooted TWRP give me error and installation fails and if I install superSU and after Magisk v11, Magisk manager say system is using SuperSU instead MagiskSU. How do I install Magisk with MagiskSU??
I have Samsung Galaxy S4 with optimized LineageOS 14.1

Read the pinned Magisk thread...
Unroot again using unSu by osm0sis (Google) before flashing magisk

Installation Instructions
If you're already rooted with MagiskSU, Magisk phh's superuser (not original), or Official Systemless SuperSU
Install/upgrade Magisk Manager from Play Store
Install/upgrade Magisk as prompted in the application
Reboot and you're done!!
If you're not rooted, or something went wrong and you need a clean start
(Recommended) Restore your boot image back to stock
Download the latest Magisk zip file
If you choose to use SuperSU (only support Android 6.0+), first flash SuperSU in systemless mode
Flash Magisk zip
Reboot, and update the stub Magisk Manager to the latest from Play Store
Click to expand...
Click to collapse
I read 200 times but when I install Magisk without SuperSU (because I want MagiskSU) TWRP give me an error and install fail... read my initial post first please....
Error:
Code:
! SU image mount failed...
! Please immediately flash SuperSU now
! Installation will complete after flashing SuperSU
[B]Updater process ended with ERROR: 1
Error installing zip file 'sdcard/Download/Magisk v11.1/Magisk-v11.1.zip[/B]

dhaern said:
I read 200 times but when I install Magisk without SuperSU (because I want MagiskSU) TWRP give me an error and install fail... read my initial post first please....
Error:
Click to expand...
Click to collapse
You need to FULLY unflash superSU using the zip that the other person told you to google.

PartyPlease said:
You need to FULLY unflash superSU using the zip that the other person told you to google.
Click to expand...
Click to collapse
Ok I will try unflash with the zip, I was using unroot inside superSU menu but installation instructions dont say nothing about the unflash with an extrenal script

dhaern said:
Ok I will try unflash with the zip, I was using unroot inside superSU menu.
Click to expand...
Click to collapse
Yeah that button doesn't work for systemless superSU. It doesn't roll back your boot.IMG like it should.
Worst case scenario, flash the stock boot.img and then flash magisk.

Thanks guys, I installed Magisk v11.1 with MagiskSU working, Magisk Hide enabled but I have CTS mismatch error now in Safetynet test. I guess I cant do nothing about this error. Optimized LineageOS 14.1 and Samsung Galaxy S4
EDIT: Finally I passed the Safetynet test (no CTS mismatch error) disabling ADB interface in developer options. Thanks for Magisk, amazing.

PartyPlease said:
Yeah that button doesn't work for systemless superSU. It doesn't roll back your boot.IMG like it should.
Worst case scenario, flash the stock boot.img and then flash magisk.
Click to expand...
Click to collapse
ahh, this would explain why my boot.img was not the same after "unrooting"! thanks for clearing this up for me...

dhaern said:
Thanks guys, I installed Magisk v11.1 with MagiskSU working, Magisk Hide enabled but I have CTS mismatch error now in Safetynet test. I guess I cant do nothing about this error. Optimized LineageOS 14.1 and Samsung Galaxy S4
EDIT: Finally I passed the Safetynet test (no CTS mismatch error) disabling ADB interface in developer options. Thanks for Magisk, amazing.
Click to expand...
Click to collapse
By disabling ADB interface, do you mean the USB debugging part? for some reason I am still getting Safetynet error.

vicky_ag said:
By disabling ADB interface, do you mean the USB debugging part? for some reason I am still getting Safetynet error.
Click to expand...
Click to collapse
Yeah I said USB debugging option, when I disabled this I passed Safetynet test.

dhaern said:
Yeah I said USB debugging option, when I disabled this I passed Safetynet test.
Click to expand...
Click to collapse
Thanks but doesn't seem to work for me.

dhaern said:
Yeah I said USB debugging option, when I disabled this I passed Safetynet test.
Click to expand...
Click to collapse
Thanks for this hint; got my build "passed" now appreciate it

What settings are you guys using in Magisk? I have disabled BusyBox, enabled Magisk Hide and systemless hosts. Superuser options are Access to "Apps and ADB" and Automatic Response set to prompt

I'm still having an issue installing Magisk on my phone with RAMROM V10. It gives me an ERROR 1.
It has been suggested that I should re-flash my boot.img with TWRP following the instruction:
Place your BOOT.img on your sdcard
Reboot into TWRP recovery
Tap "Install"
In the bottom right corner tap "Install Image"
Select your BOOT.img
Select the Boot Partition, then swipe to confirm Flash
However, when I follow the step, my TWRP cannot seem to find BOOT.IMG in my SD Card (I know it is there). What did I do wrong? Can anyone help?

i think the .img thingy is only for twrp.img files. You have to use another method to place your boot image like. -> make a backup of only your boot image via twrp backup function. Then duplicate that backup folder of twrp containing only the newly just regernated files, in the twrp folder. Then replace the su-modified boot file there with your original boot file, you obviously have to rename your boot image to fit the right name. (eg. with the logo image -> logo.bin changes to logo.emmc.win -> etc;.) Then use the twrp restore function to restore your "original" boot logo.
Hierarchy folder view would be like:
TWRP->folder 1 (original folder, in case something goes wrong)-> boot file and others
->folder 2 (our modified folder)-> files

sm00th4f3 said:
i think the .img thingy is only for twrp.img files. You have to use another method to place your boot image like. -> make a backup of only your boot image via twrp backup function. Then duplicate that backup folder of twrp containing only the newly just regernated files, in the twrp folder. Then replace the su-modified boot file there with your original boot file, you obviously have to rename your boot image to fit the right name. (eg. with the logo image -> logo.bin changes to logo.emmc.win -> etc;.) Then use the twrp restore function to restore your "original" boot logo.
Hierarchy folder view would be like:
TWRP->folder 1 (original folder, in case something goes wrong)-> boot file and others
->folder 2 (our modified folder)-> files
Click to expand...
Click to collapse
FIY: Flashing regular boot.img files works just fine with "Install Image" in TWRP (of course, YMMV, depending on your device).

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!!

Fix adblock on rooted 9.1

Found a way to get adblocking back on rooted emui 9.1.
in magisk settings enable systemless hosts
then in downloads, search for "busybox for android NDK" install that, then search for "energized protection" and install that too, then reboot
in a terminal emulator type "su" and allow the terminal emulator to run as root.
Then to configure the adblock just type "energized"
let it do it's check and then you have several options, first you have to choose the pack
i usually go with basic (4)
after applying, exit with q and type reboot in the console.
after reboot check some website with known ads and enjoy
for more information check out Github: https://github.com/Magisk-Modules-Repo/energizedprotection#usage
Or Energized website: https://energized.pro/

Thanks, works great.

Daniehabazin said:
Found a way to get adblocking back on rooted emui 9.1.
in magisk settings enable systemless hosts
then in downloads, search for "busybox for android NDK" install that, then search for "energized protection" and install that too, then reboot
in a terminal emulator type "su" and allow the terminal emulator to run as root.
Then to configure the adblock just type "energized"
let it do it's check and then you have several options, first you have to choose the pack
i usually go with basic (4)
after applying, exit with q and type reboot in the console.
after reboot check some website with known ads and enjoy
for more information check out Github: https://github.com/Magisk-Modules-Repo/energizedprotection#usage
Or Energized website: https://energized.pro/
Click to expand...
Click to collapse
Can you provide download links and instructions on how you have rooted EMUI 9.1 mate 20 pro.
I tried to root, but unable to mount few partitions. I have formatted "/data" using TWRP but still unable to flash magisk. After mutiple retries able to flash magisk with some errors mentioning about error in mount. Then my mobile keeps on rebooting and going to erecovery. Am on EMUI 9.1.0.300

adaway is working fine for me.

side_flip15 said:
adaway is working fine for me.
Click to expand...
Click to collapse
on 9.1?
with 9.1 huawei intruduced a new file system that is read only.

sharath91221 said:
Can you provide download links and instructions on how you have rooted EMUI 9.1 mate 20 pro.
I tried to root, but unable to mount few partitions. I have formatted "/data" using TWRP but still unable to flash magisk. After mutiple retries able to flash magisk with some errors mentioning about error in mount. Then my mobile keeps on rebooting and going to erecovery. Am on EMUI 9.1.0.300
Click to expand...
Click to collapse
there is no difference rooting 9.0 or 9.1, you do it the same way.
well, with the exeption that directly after factory reset you have to flash the recovery_ramdisk, if you let the phone boot up without the modified recovery then android messeges stops working.
so the step is simple, install 9.1, if your phone is messed up use the hstool or erecovery, hstool was faster for me.
get yourself a patched recovery_ramdisk from 9.1 (i did this myself by extracting the ramdisk and patching in magisk on my phone when i was still on 9.0)
before first boot, enter fastboot and flash the recovery_ramdisk.
boot with volume up, and then profit.
for more information check: https://forum.xda-developers.com/mate-20-pro/how-to/guide-manual-updating-firmware-t3893171

Daniehabazin said:
there is no difference rooting 9.0 or 9.1, you do it the same way.
well, with the exeption that directly after factory reset you have to flash the recovery_ramdisk, if you let the phone boot up without the modified recovery then android messeges stops working.
so the step is simple, install 9.1, if your phone is messed up use the hstool or erecovery, hstool was faster for me.
get yourself a patched recovery_ramdisk from 9.1 (i did this myself by extracting the ramdisk and patching in magisk on my phone when i was still on 9.0)
before first boot, enter fastboot and flash the recovery_ramdisk.
boot with volume up, and then profit.
for more information check: https://forum.xda-developers.com/mate-20-pro/how-to/guide-manual-updating-firmware-t3893171
Click to expand...
Click to collapse
You used patched_recovery_ramdisk.img from 9.0 on 9.1 or you have extracted recovery_ramdisk from 9.1 and then patched it using magisk?
If you have extracted recovery_ramdisk.img from 9.1, can you provide me the link?

sharath91221 said:
You used patched_recovery_ramdisk.img from 9.0 on 9.1 or you have extracted recovery_ramdisk from 9.1 and then patched it using magisk?
If you have extracted recovery_ramdisk.img from 9.1, can you provide me the link?
Click to expand...
Click to collapse
i extracted the ramdisk from 9.1.0.310 and patched it in magisk on my phone. i'm unable to share the file right now because i'm on a trip right now but i'll be back on monday. but it's easy to patch it yourself, just extract it with huaweiupdateextractor and transfer it to your phone.

Daniehabazin said:
i extracted the ramdisk from 9.1.0.310 and patched it in magisk on my phone. i'm unable to share the file right now because i'm on a trip right now but i'll be back on monday. but it's easy to patch it yourself, just extract it with huaweiupdateextractor and transfer it to your phone.
Click to expand...
Click to collapse
Great. Thank you Daniehabazin :good:. I will download 9.1.0.310 using firmware finder app and extract UPDATE.APP using hauweiupdatextractor and use magisk to patch ramdisk.

sharath91221 said:
Great. Thank you Daniehabazin :good:. I will download 9.1.0.310 using firmware finder app and extract UPDATE.APP using hauweiupdatextractor and use magisk to patch ramdisk.
Click to expand...
Click to collapse
sounds good, hit me up for the patched ramdisk if you can't get it to work and i'll upload it on monday.
have a lya-l29c432 but the firmware i downloaded was for lya-lgrp-ovs, i guess it covers several hardware versions

Daniehabazin said:
sounds good, hit me up for the patched ramdisk if you can't get it to work and i'll upload it on monday.
have a lya-l29c432 but the firmware i downloaded was for lya-lgrp-ovs, i guess it covers several hardware versions
Click to expand...
Click to collapse
After factory reset, I have flashed patched ramdisk.img from 9.1.0.310 and while rebooting press and hold vol+ button, it is going to "press power key to continue, press volume up key..." thing. If i reboot and press vol- key again it was going to "press power key to continue...."thing. Magisk app still shows it was not installed.

Off topic for rooting... There is already a thread for that with patched recovery img 9.1 and procedure for rooting. 9.1...(search my posts) To return to subject of this topic, what is missing and why I don't use energized it's because it don't have blocklist GoodbyeAds (Google ads)
Also you can use private dns in network setting and put dns.adguard.com in it, but in my case that break mms so...
---------- Post added at 10:58 PM ---------- Previous post was at 10:56 PM ----------
Daniehabazin said:
on 9.1?
with 9.1 huawei intruduced a new file system that is read only.
Click to expand...
Click to collapse
Wrong, it's only "/system" and "/" r/o. Subfolders are r/w (ie /etc /cache...)

Daniehabazin said:
on 9.1?
with 9.1 huawei intruduced a new file system that is read only.
Click to expand...
Click to collapse
Take a look at my screenshots. I got something like storage error at first. Adaway worked after I debloat and systemize app using magisk module. Not sure if it's related but works for me three times already. Those two modules actually alters files on /system without any issue. Worth trying...

sharath91221 said:
After factory reset, I have flashed patched ramdisk.img from 9.1.0.310 and while rebooting press and hold vol+ button, it is going to "press power key to continue, press volume up key..." thing. If i reboot and press vol- key again it was going to "press power key to continue...."thing. Magisk app still shows it was not installed.
Click to expand...
Click to collapse
Trick is not to send command on fastboot to reboot. After flashing recovery_ramdisk successfully remove the usb cable then press and hold power + volume up buttons. Release them when you see the yellow text warning saying "your device is booting now..."

side_flip15 said:
Trick is not to send command on fastboot to reboot. After flashing recovery_ramdisk successfully remove the usb cable then press and hold power + volume up buttons. Release them when you see the yellow text warning saying "your device is booting now..."
Click to expand...
Click to collapse
I found an another way. After flashing patched ramdisk and after reboot if it shows "press power key to continue.." thing. Go to erecovery and then go to factory wipe. It does not actually wipe the phone, it simply reboots and turn on with magisk installed.
Now am unable to install exposed or core. If i install them, mobile is stuck at boot

side_flip15 said:
Take a look at my screenshots. I got something like storage error at first. Adaway worked after I debloat and systemize app using magisk module. Not sure if it's related but works for me three times already. Those two modules actually alters files on /system without any issue. Worth trying...
Click to expand...
Click to collapse
oh, ok.
because i also got the storage error and on the thread for p30 pro rooting i saw that adaway doesn't work, checked the p30 forum because they got their phone with 9.1.
i'll try adaway again, but i also kinda like the feeling of running a terminal on my mate 20 pro

Adaway is working just fine here in LYA 9.1.
But Energizer should be also fine.

oslo83 said:
Adaway is working just fine here in LYA 9.1.
But Energizer should be also fine.
Click to expand...
Click to collapse
Yes if systemless host is enabled. This is the trick. You can use all ad blocker apps.

Daniehabazin said:
Found a way to get adblocking back on rooted emui 9.1.
in magisk settings enable systemless hosts
then in downloads, search for "busybox for android NDK" install that, then search for "energized protection" and install that too, then reboot
in a terminal emulator type "su" and allow the terminal emulator to run as root.
Then to configure the adblock just type "energized"
let it do it's check and then you have several options, first you have to choose the pack
i usually go with basic (4)
after applying, exit with q and type reboot in the console.
after reboot check some website with known ads and enjoy
for more information check out Github: https://github.com/Magisk-Modules-Repo/energizedprotection#usage
Or Energized website: https://energized.pro/
Click to expand...
Click to collapse
Great work, just did it and it works. Have been busting my head for a week now without Adaway. Thanks man!

adaway just works fine on 9.1

[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.

How To Guide [Android13] Custom GSI ROM Installation - Full Process

I'm going to explain the complete process for getting up and running on a custom GSI ROM as the guides so far seem to either have only parts of information or incorrect information.
Following this process will wipe your data and alter your phone. I am not responsible for any bricked or damaged devices.
For the purpose of this thread I'm going to assume the installation of an Android 13 GSI image which you can get from the GSI images site. I like to use crDroid.
Make sure you read and understand all instructions before beginning!
1 - Unlock the bootloader
Important things to note:
One Xiaomi account can unlock one device per month. If you need to unlock multiple devices create an account for each one.
Unlocking the bootloader requires a wait time of 1 week after adding your Xiaomi account to the device before it can be unlocked
Create a Xiaomi account to use during this process here: https://account.xiaomi.com
Download the MI Unlock tool from here: https://en.miui.com/unlock/download_en.html
Procedure:
Ensure a SIM card is in with mobile data working and disable Wifi (required when associating your device with your Xiaomi account)
Enable developer mode by going into "About Phone" and tapping on the MIUI Version until it unlocks the setting
In Settings go to Additional Settings > Developer Options
Enable "OEM Unlocking" option
Select the "Add Account" option and enter your Xiaomi account details to link your device to your account
Open the Mi Unlock tool on your PC and log in with your Xiaomi account
If you get asked for a phone number when you log in the tool may get stuck as it doesn't allow you to click on the country code drop down correctly.
To avoid this, use the QR code icon on the first sign in page and from your phone go into the Xiaomi Account settings and click the scan icon on the top right
Log your account in with your phone to set the phone number there and you should be able to log in through the Mi Unlock tool next time without a problem.
Boot your phone into fastboot mode by holding Volume Down & Power buttons
Connect your phone to your PC with a USB cable
Click Unlock on the Mi Unlock tool and it should check your device and then give you a wait timer (generally 168 hours)
After that time is up (you can use your phone normally while waiting but don't mess with the Xiaomi Account settings) connect your phone in fastboot mode again and click Unlock in the Mi Unlock tool to unlock the bootloader.
2 - Install TWRP Recovery (or alternative)
Important things to note:
This phone does not have a dedicated recovery partition, the recovery is a ramdisk that resides within the boot partition
You cannot flash a recovery partition directly to the boot partition as it will then fail to boot
Make sure you use a current version of fastboot: https://provider.xiaomi.eu/tools/fastboot.zip
All commands written below are to be used without the apostrophes within a command prompt (powershell will require .\ placed in front of the command)
Download a TWRP image from here: https://sourceforge.net/projects/recovery-for-xiaomi-devices/files/vili/ Use the A13 image for Android 13 ROMs.
Procedure:
Boot your phone into fastboot mode by holding Volume Down & Power buttons
Connect your phone to your PC with a USB cable
Run command "fastboot boot twrp.img" to reboot phone into TWRP recovery
If this is the first time using TWRP it will likely be in Chinese language. Click the 2nd to last button on the right side of the menu, then the globe icon on the top right to change language.
Go to Advanced and choose Flash Current TWRP to install TWRP into the boot image
Choose Reboot to Recovery to test the image is installed
3 - Install Latest Xiaomi.eu ROM (optional)
Important things to note:
I like to use the xiaomi.eu ROM as a base before installing a GSI image as it seems to be more stable and functional afterwards
This step is optional as you can continue with the global ROM base instead
Additionally, you can stop after this step if you would prefer to use a MIUI based ROM instead of a custom GSI image
The Xiaomi.eu ROM can be downloaded from here: https://xiaomi.eu/community/threads/miui-14-stable-release.67685/
The bootloader must be unlocked and TWRP recovery installed
Procedure:
Boot your phone into TWRP recovery by holding Volume Up & Power buttons
Click the Wipe button and then Format Data. Enter yes to wipe the data partition. (This will erase all data as well as the internal storage)
Connect your phone to PC and copy the xiaomi.eu ROM onto the phone
Click the Install button on the main menu in TWRP and select the ROM zip file to install
Go to Advanced and choose Flash Current TWRP to install TWRP back into the boot image
4 - Install Custom GSI Image
Important things to note:
This phone has a Super partition which dynamically contains system, system_ext and vendor partitions
This means that you cannot flash a GSI image directly to the system partition from TWRP so it must be installed via fastbootd
fastbootd is an enhanced version of fastboot that works with the dynamic Super partition
fastbootd mode looks like TWRP but it will say "Entered fastboot mode..." on the screen
Make sure you use a current version of fastboot: https://provider.xiaomi.eu/tools/fastboot.zip
All commands written below are to be used without the apostrophes within a command prompt (powershell will require .\ placed in front of the command)
Extract vbmeta.img file from the Xiaomi.eu ROM (or global ROM if using that) and place it in same folder as fastboot
Download your custom GSI image of choice from here or other source: https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
Extract the GSI image, rename it system.img and place it in the same folder as fastboot
Procedure:
Enter fastbootd mode on your phone using one of the following methods:
boot phone into fastboot mode and from your PC run command "fastboot reboot fastboot"
boot phone into TWRP and choose Reboot and then Fastboot
From your PC run the command "fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img" to disable the boot image hash checks to avoid boot loops
Run the command "fastboot erase system" to wipe the existing system image
Run the command "fastboot flash system system.img" to install your custom GSI image
NOTE: If you get an error saying "Not enough space to resize partition" run the command "fastboot delete-logical-partition product_a" and repeat the install again
5 - Install Magisk and Root
Important things to note:
Using the TWRP installation method by renaming the magisk apk to zip is not very reliable and the lastest versions require installation to be performed from within the OS
Download the lastest magisk from here: https://github.com/topjohnwu/Magisk/releases
We use a backup of the installed boot image rather than one from the xiaomi ROM as it has TWRP recovery installed in the ramdisk
Procedure:
Boot your phone into TWRP recovery
Enter the Backup menu, select the boot partition and run the backup
Copy the boot.emmc.win file out of the TWRP backup folder into the Download folder on your phone and rename it boot.img
Reboot your phone into System
Install the magisk apk file
Open magisk and click Install on the top right (in the Magisk section, not the App section)
For the Method choose Select and Patch a File then click Lets Go
Find the boot.img backup file copied to the Download folder and select it (after patching it will tell you the filename of the patched image)
Reboot your phone into TWRP recovery
Choose Install, then Install Image, select the file Magisk created above, select the Boot partition and then swipe to flash
Reboot to system and check in Magisk that it shows as installed (you may also want to reboot to recovery to ensure TWRP is still installed)
6 - Fixing Safetynet
Important things to Note:
The Shamiko magisk module is used to hide root status from apps that detect root/magisk. This can be used to make any app work that fails due to root status.
Shamiko uses the Denylist in Magisk settings to block root settings for those apps enabled but you should NOT have the denylist enforced in Magisk settings
You can find the Shamiko module here: https://github.com/LSPosed/LSPosed.github.io/releases
The default Universal Safetynet Fix can be found here however due to problems in a previous phone, I used the modded version from here (I'm not sure if that's still required for A13)
Procedure:
In Magisk settings choose to hide the magisk app to reinstall it with a different name and app id
In Magisk settings enable Zygisk and reboot phone
In Magisk settings choose Configure Denylist, show system apps from the top menu and enable Google Play Services, Google Play Store & Google Service Framework
In Magisk install the following modules: Shamiko, Universal Safetynet Fix
Install a Safetynet Checker from Google Play (SafetyNet Device Check) and verify safetynet tests pass successfully
7 - Post installation Fixes
Below are some fixes to common problems after installing a custom ROM.
Phh Settings Tweaks:
Qualcomm features - Use alternate audio policy -> fix audio in whatsapp
Qualcomm features - Disable soundvolume -> fix broken audio
Xiaomi features - Enable DT2W -> to enable double tap to wake
Misc features - Force alternative backlight scale -> fix auto brightness
IMS Features - Install IMS APK for Qualcomm -> allows SMS to work