Database Info

【HOW TOs】How to root UK v2.51 ROM.[Updated 12-27-20:50]

Hi Friends.
Please redownload defy_recovery.zip.sorry for my mistake.
please downloade attachment 474211
Here is the tut of how to root the defy uk 2.51 rom.
It's simple and easy way.
this will be a step by step tut.because of my poor english.i will try to explain more detial.
1、download attatch files.
defy_2.21_boot_only.sbf
View attachment 2.21boot.zip
defy_2.51_boot_only.sbf
View attachment 2.51boot.zip
defy_recovery.exe
View attachment 474211
2、flash the defy_2.21_boot_only.sbf via rsd then reboot in to system.
3、open you phone's usb debug mode(settings-application-development-usb debug mode),then double click the defy_recovery.exe you just downloaded ,it will process the root method.when it finished you phone is rooted with superuser and my clockworkmod recovery for defy.
4、the last step is flash the defy_2.51_boot_only.sbf via rsd lite.
5、and now your phone is rooted and customized recovery installed.
This method original comes from adlx @ modmymobile.com
if your like this tut.. please buy me or adlx a beer or I can buy another phone eg. Nexus S ...Thanks.

well done！

SteveChou said:
well done！
Click to expand...
Click to collapse
No way here... It doesn't fuction... There is a problem in the batch file:
Code:
@echo off
echo µÈ´ýÉ豸
adb wait-for-device
echo »ñµÃrootȨÏÞ
adb push rageagainstthecage-arm5.bin /data/local/tmp/rageagainstthecage-arm5.bin
adb shell "chmod 0755 /data/local/tmp/rageagainstthecage-arm5.bin"
adb shell "./data/local/tmp/rageagainstthecage-arm5.bin & sleep 300;kill $!"
echo ÖØÐÂÁ¬½ÓÉ豸£¬¿ÉÄÜÐèÒªÒ»¶Îʱ¼ä
adb kill-server
call :sleep 10
adb start-server
call :sleep 30
echo È¡ÏûsystemÖ»¶ÁÊôÐÔ
adb shell "mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system"
echo °²×°Superuser.apk
adb push Superuser.apk /system/app/Superuser.apk
echo °²×°GoAPK MOD Recovery
adb push recovery.apk /system/app/recovery.apk
echo °²×°su
[B]adb push su /system/app/su[/B]
adb shell "chmod 4755 /system/bin/su"
echo °²×°busybox
adb push busybox /system/bin/busybox
adb shell "chmod 4755 /system/bin/busybox"
echo ÖØÉèsystemÖ»¶ÁÊôÐÔ
adb shell "mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system"
echo Íê³Éroot£¬ÇëÖØÆôÊÖ»ú
:sleep
(ping 127.0.0.1 -n 2 -w 1000 > NUL)> sleep.txt
(ping 127.0.0.1 -n %1 -w 1000 > NUL)> sleep.txt
del sleep.txt
You have to push su in bin directory non in app directory...
Code:
[B]adb push su /system/app/su[/B]
Please correct this bug.
I've also tried to upload any file thought adb (after r/w mount), but the phone doesn't recognize the apk's (Superuser and Recovery), they still invisible...
Any solution?

Well done, i did it this:
- Downloaded your 2.21boot.zip;
- Flashed thought RSD;
- Downloaded Android SDK with ADB;
- Download this Rootpack http://www.mediafire.com/?kjee8aj22j9m5zj;
- Extract this files in you /sdk/tools directory;
- Open cmd and point it in the directory with ADB;
- Run this commands:
Code:
adb devices
adb shell mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
adb push Superuser.apk /system/app/Superuser.apk
adb push su /system/bin/su
adb shell chmod 4755 /system/bin/su
adb push busybox /system/bin/busybox
adb shell chmod 4755 /system/bin/busybox
adb shell mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
adb reboot
- Flash back to 2.51boot.zip
That's all!
Thank you sir!

sorry for my mistake...
bugfixed
View attachment defy_recovery.zip

its not working , root exe not found

socket84 said:
Well done, i did it this:
- Downloaded your 2.21boot.zip;
- Flashed thought RSD;
- Downloaded Android SDK with ADB;
- Download this Rootpack http://www.mediafire.com/?kjee8aj22j9m5zj;
- Extract this files in you /sdk/tools directory;
- Open cmd and point it in the directory with ADB;
- Run this commands:
Code:
adb devices
adb shell mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
adb push Superuser.apk /system/app/Superuser.apk
adb push su /system/bin/su
adb shell chmod 4755 /system/bin/su
adb push busybox /system/bin/busybox
adb shell chmod 4755 /system/bin/busybox
adb shell mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
adb reboot
- Flash back to 2.51boot.zip
That's all!
Thank you sir!
Click to expand...
Click to collapse
Thank you for Your Bug Report.

Is there any way now to flash back to an older SBF?

fixed recovery.exe = its not working , root exe not found windows warning

batch reply "root.exe not found" after double click the defy_recovery.exe
also, from above reply:
"mount: Operation not permitted"
---------------------------------------------------------------------------------------------------
Hello,
I found out the way to get this rooting working.
everything stays the same until running the recovery.exe part
then please refer to the old rooting method
BUT using the rooting pack mentioned above link
then flash back to 2.51
it should work!
cheers!

cometcao said:
batch reply "root.exe not found" after double click the defy_recovery.exe
also, from above reply:
"mount: Operation not permitted"
Click to expand...
Click to collapse
Try This One
View attachment defy_recovery.zip

sorry sir,
About the root process, Why different with "http://bbs.goapk.com/forum.php?mod=viewthread&tid=48445&extra=%26page%3D1&page=1" ??
In goapk forum, the process2-> flash the original SBF? process3->Wipe data?
no need ?
Can this solution fit for Taiwan version 2.51.0?

Dear Sir:
Taiwan version could rooting by your solution!!
Thanks a lot~
you so great!!!

yeah~ it works for my Taiwanese version.
great job!
thanks~

Thank you very much for the HOW TOs.
Has anyone tried this on 2.51 HK rom?

hkipaqer said:
Thank you very much for the HOW TOs.
Has anyone tried this on 2.51 HK rom?
Click to expand...
Click to collapse
this will work on HK TW SG version 2.51

can we have any details about the rooting process ?
i want to get the Taiwan version of the Defy (Blurless)
1) is there any way to get root access, but still use the firmware that came with the phone ? (TW SG HK 2.51) i wouldn't mind doing some stuff manually...
2) As far as i know the original ROM of the Taiwan SG HK defy isn't available for download right ?
thanks for your hard work.

tenfar, thank you very much for your great work, I just rooted my HK DEFY.
Here are few steps added for those like me very new to Android and Root.
1. If you RSD Lite did not recognize your DEFY, download the USB driver here:
http://developer.motorola.com/docstools/USB_Drivers/
2. Power off DEFY. Then press 'Volume Up' and 'Power' together to boot to loader before you flash the SBF to your DEFY.
Happy rooting.

Thanks
Now I finished my HK defy rooted.
Very thanks for tenfar.

rooting wit Uk 2.51 possible..not other ROM flashable
hi Guys.....i have installed the UK JRDNEM_U3_2.51....and the root method desribed here worked too...
My question is: What happens after
- rooting the Uk U3_25.1 with our method (Sytem.boot.only 2.1 2.5 etc.)
- Restore system with SystemRecovery-App "Recovery Boot"
- i restored with a backup of t-mobile U3_2.21 (from my friend)
-worked
??
Build Number ist U3_2.21.0 now
Did I downgraded my system now?
If yes,
the Problem is then:
I cannot flash any ROM (RSD 4.9) from here http://and-developers.com/sbf:defy
except the JRDNEM_U3_2.51.1_BLUR_P3_SIGN_SIGNED_USAJRDNEMARAB1B8RTGB02C.0R_USAJORDANRTGB_P035_A011_HWp3_Service1FF.sbf
Therefore I dont believe i downgraded anything :-mad:
The flash-procedure with all other ROMs is the same:
RSD : finished --> Defy is not booting is hanging in the bootLoader-mode
Any Help?
Or anyone with a Vodafone 360 Original Backup that would be great
Thanks

[MISC] 1click tools (Windows only)

S-Off + Perm root is required to use this tools!
there are 3 batch files inside:
_Radio.bat
_Recovery.bat
_EngBootloader.bat
how to use:
_EngBootloader - run and follow instructions
_Radio.bat - download radio image, rename it to radio.img and put it into the directory, run _Radio.bat
_Recovery.bat - download recovery image, rename it to recovery.img and put it into directory, run _Recovery.bat
don't know if all of you think that those tools are useful, but for some people it may be useful cause they aren't familar with cmd & adb
code for the batch files are included in the 2nd post, executables (no drivers) for adb and fastboot are included in the attachment

_EngBootloader.bat
Code:
@echo off
cls
adb devices
echo If your device is not listed exit this program now, enable usb debugging and try again.
pause
cls
adb push hboot.img /data/local/tmp
adb shell chmod 777 /data/local/tmp/hboot.img
echo Please accept superuser request on your phone
adb shell su
pause
adb shell dd if=/dev/block/mmcblk0p18 of=/sdcard/backup.img
adb shell dd if=/data/local/tmp/hboot.img of=/dev/block/mmcblk0p18
echo Bootloader should be flashed to your device now, backup from old bootloader is saved at /sdcard/backup.img
pause
adb reboot bootloader
_Radio.bat
Code:
@echo off
cls
adb devices
echo If your device is not listed exit this program now, enable usb debugging and try again.
pause
cls
echo Please accept superuser request on your phone
adb shell su
pause
echo Phone should reboot now to bootloader, please wait for it to boot
adb reboot bootloader
pause
echo Wait for flash to finish
fastboot flash radio radio.img
pause
fastboot reboot
_Recovery.bat
Code:
@echo off
cls
adb devices
echo If your device is not listed exit this program now, enable usb debugging and try again.
pause
cls
echo Please accept superuser request on your phone
adb shell su
pause
echo Phone should reboot now to bootloader, please wait for it to boot
adb reboot bootloader
pause
echo Wait for flash to finish
fastboot flash recovery recovery.img
pause
fastboot reboot

is this method for s off DS without xtc clip?

jalal.arkat said:
is this method for s off DS without xtc clip?
Click to expand...
Click to collapse
No, unfortunately these are a group off tools that can only be used once you are S-OFF.
So S-ON need not apply
@Blezz : thanks these will be useful

i don't know if they will be useful, they are still simply work.. it's more for... lazy people

Stuck on LG Logo

I flash KDZ,TOT but it not work
When finish flashing, LG Logo and reset and LG Logo(reboot) and reset.
TOT - FBoot check failed
KDZ - WParam error

SerenityS said:
I flash KDZ,TOT but it not work
When finish flashing, LG Logo and reset and LG Logo(reboot) and reset.
TOT - FBoot check failed
KDZ - WParam error
Click to expand...
Click to collapse
try this, Chapter 3 Using ADB as solution. Sorry , my English too bad, so it's all i can find for you.Hope you can countinue with CM rom.
Source: http://forum.xda-developers.com/showthread.php?t=1660596
ADB can be used to access the phone while booting, be aware that some bootloops make it unable to use ADB since they do not go further then the samsung logo.
The only tricky part about using ADB with bootloops is that you have to do it on the right time, this is just after the Galaxy S Plus logo, so just when the bootanimation starts. The easiest way to enter your phone in this part is using a batch script that monitors the state of your device and connects directly when possible.
I use this script for example (requires adb.exe and the 2 dlls)
Code:
@echo off
cd /d %~dp0
echo.
echo Waiting for device...
adb wait-for-device
echo.
adb -d shell stop
adb push mycwmfix.zip /sdcard/mycwmfix.zip
adb reboot recovery
This script will wait for the device to become ready, when it's ready it freeze the device, so the script has more time to push the file (instead of keep rebooting). Then it will push the specified cwmfix zip to your sdcard, and after that it will reboot in recovery so you can install the cwm fix you made.
You can also make an batch script that pushes the files automatically to your phone, here is an example:
Code:
@echo off
cd /d %~dp0
echo.
echo Waiting for device...
adb wait-for-device
echo.
adb -d shell stop
adb -d shell su -c "mount -o remount rw /system"
adb push framework-res.apk /system/framework/framework-res.apk
adb -d shell chmod 644 /system/framework/framework-res.apk
adb push SystemUI.apk /system/app/SystemUI.apk
adb -d shell chmod 644 /system/app/SystemUI.apk
adb reboot
This script will wait for the device to become ready, when it's ready it freeze the device, so the script has more time to push the file (instead of keep rebooting). Then it will push framework-res.apk and SystemUI.apk to the directory it belongs to, after that it changes the permissions of the files to RW-R-R (644) and then it will reboot.

odatoshiie said:
try this, Chapter 3 Using ADB as solution. Sorry , my English too bad, so it's all i can find for you.Hope you can countinue with CM rom.
Source: http://forum.xda-developers.com/showthread.php?t=1660596
ADB can be used to access the phone while booting, be aware that some bootloops make it unable to use ADB since they do not go further then the samsung logo.
The only tricky part about using ADB with bootloops is that you have to do it on the right time, this is just after the Galaxy S Plus logo, so just when the bootanimation starts. The easiest way to enter your phone in this part is using a batch script that monitors the state of your device and connects directly when possible.
I use this script for example (requires adb.exe and the 2 dlls)
Code:
@echo off
cd /d %~dp0
echo.
echo Waiting for device...
adb wait-for-device
echo.
adb -d shell stop
adb push mycwmfix.zip /sdcard/mycwmfix.zip
adb reboot recovery
This script will wait for the device to become ready, when it's ready it freeze the device, so the script has more time to push the file (instead of keep rebooting). Then it will push the specified cwmfix zip to your sdcard, and after that it will reboot in recovery so you can install the cwm fix you made.
You can also make an batch script that pushes the files automatically to your phone, here is an example:
Code:
@echo off
cd /d %~dp0
echo.
echo Waiting for device...
adb wait-for-device
echo.
adb -d shell stop
adb -d shell su -c "mount -o remount rw /system"
adb push framework-res.apk /system/framework/framework-res.apk
adb -d shell chmod 644 /system/framework/framework-res.apk
adb push SystemUI.apk /system/app/SystemUI.apk
adb -d shell chmod 644 /system/app/SystemUI.apk
adb reboot
This script will wait for the device to become ready, when it's ready it freeze the device, so the script has more time to push the file (instead of keep rebooting). Then it will push framework-res.apk and SystemUI.apk to the directory it belongs to, after that it changes the permissions of the files to RW-R-R (644) and then it will reboot.
Click to expand...
Click to collapse
I try to anything for recovery my phone, but everything not work.
I think Some partition(Cant recover with TOT and KDZ) were broken.

SerenityS said:
I try to anything for recovery my phone, but everything not work.
I think Some partition(Cant recover with TOT and KDZ) were broken.
Click to expand...
Click to collapse
i think MR. Le Thanh Tung can help you. ask him about this problem
facebook.com/Tungkick777?fref=ts

SerenityS said:
I flash KDZ,TOT but it not work
When finish flashing, LG Logo and reset and LG Logo(reboot) and reset.
TOT - FBoot check failed
KDZ - WParam error
Click to expand...
Click to collapse
This is a Super Brick,i have the same Problem 2 Months ago,tungkick help me,but no change to repair this error.
I send my GP2 to Repair Station and he tell me,the Board is death.I have brought a new GP2.
R.I.P.

I think so too.
R.I.P.

Teclast Tbook 16 Power (M5F8) root

I want to get root.
Does not work.
Turn on USB debugging
Bootloader unlock:
Code:
adb reboot bootloader
fastboot flashing unlock
Erase and flash recovery:
Code:
fastboot erase recovery
fastboot flash recovery TWRP_2_8_7.img
Reboot recovery.
TWRP - Install zip - SuperSU.zip
E:Unable to mount 'factory'
Rebood system.
SuperSU - not installed
Root - not installed
Go to fastboot:
Code:
adb reboot fastboot
Erase and flash recovery:
Code:
fastboot erase recovery
fastboot flash recovery TWRP_3_0_2.img
Reboot recovery.
TWRP - Install zip - SuperSU.zip
Is installed without errors.
Rebood system.
SuperSU - not installed
Root - not installed
---
ADB install:
Code:
adb root
adb remount
adb shell mkdir /system/bin/.ext
adb shell chmod 777 /system/bin/.ext
adb push su /system/bin/.ext/.su
adb shell chmod 6755 /system/bin/.ext/.su
adb push su /system/xbin/su
adb shell chmod 6755 /system/xbin/su
adb push busybox /system/bin/busybox
adb shell chmod 6755 /system/bin/busybox
adb shell mkdir /system/app/SuperSU
adb shell chmod 755 /system/app/SuperSU
adb push SuperSU.apk /system/app/SuperSU/SuperSU.apk
adb shell chmod 644 /system/app/SuperSU/SuperSU.apk
adb reboot
SuperSU - installed, but error on run: "SU Binary occupied"
Root - not installed
Help me please!

Root teclast tbook 16 power (m5f8)
First off, I take no responsibility for bricked devices!
Things you need before you start: charged tbook 16 power (M5F8)
!! usb mouse or keyboard dock, since touch in twrp is NOT working!!
usb-c cable
minimal adb and fastboot https://forum.xda-developers.com/showthread.php?t=2317790
usb drivers https://software.intel.com/en-us/android/articles/intel-usb-driver-for-android-devices
isoc drivers https://androiddatahost.com/te67m
1. Start your tablet and navigate to developer settings. Check usb debugging, oem unlock and uncheck analyse apps through usb
2. download latest magisk.zip to your tablet and put it in the root of the sd card
3. download attached twrp img(https://www.dropbox.com/s/rrngzwq2uvaq05l/TWRP-2.8.7.0_teclast_Tbook16Power-beta03.img?dl=0) and put it in the same folder where adb and fastboot is located
4. Connect the tablet with pc through usb-c cable
5. install minimal adb and fastboot
6. Sart a command prompt in the folder where adb is located (shift + right click)
7. type -adb reboot fastboot- and click enter (tablet enters fastboot mode)
8. type -fastboot flashing unlock- (!!! caution !!! USERDATA of android will be ERASED, like factory reset) and click enter
9. type -fastboot boot TWRP-2.8.7.0_teclast_Tbook16Power-beta03.img- and click enter
10. on twrp swipe right(mouse or keyboard dock needed!) to allow modifications, if it aksks you to root your device click no
11. click install and navigate to the magisk.zip file located on the tablet. click install, magisk will be installed and your device will be rooted
12. click reboot, first reboot takes about 5 minutes. Voilà!

It works!
Very good!
Thank you!

Thank you very much!!!

easy way, thank you.

Hi, I tried this guide just a teclast tbook 16 power, but it doesn't work for me, I don't install Magisk-v18.1.zip, from compatibility errors.
Why?

LineageOS 19.1 + Magisk. Script to help automate rooting after LOS OTA.

After setting up Magisk root and MagiskHide Props, I was a bit disappointed to learn that you loose root after a LOS OTA update (which comes out every week). So, I decided to make a bash script to help me automate restoring root. This script still needs to run on your computer rather than on the phone, but it is still a major improvement to the manual process. I am sure smart people can adapt this script to be a BAT script that will work on Windows.
Prerequisites
USB Debugging enabled on your OnePlus 6.
ADB/Fastboot installed on your computer.
It is assumed that you already have root, you just temporarily lost it after an OTA update.
You will need python 3. You will also need to install at least re and requests packages using pip.
Python script for extracting boot.img from the payload.bin provided here https://wiki.lineageos.org/extracti...ing-proprietary-blobs-from-payload-based-otas
It is expected that you put it into `scripts` folder within your current working directory (from where you run the script).
Python script to download the latest LOS zip from the website created by me. Here are the contents of that downloadLOS.py script which is expected to be in your working directory.
Python:
import re
import requests
# Get HTML text of the downloads webpage
webpage = requests.get("https://download.lineageos.org/enchilada").text
# Get the firmware urls
pattern = r"(https:.*nightly.*signed\.zip)\""
matches = re.findall(pattern, webpage, flags=0)
matches.sort(reverse=True)
# Get the latest firmware URL
latestOSURL = matches[0]
# Extract firmware name
name = latestOSURL.split('/')[-1]
print("Latest firmware: " + name)
print("Download link: " + latestOSURL)
# Download the latest firmware
print("Downloading...")
with open(name, "wb") as f:
f.write(requests.get(latestOSURL).content)
print("Done!")
Magisk Root Automation Script
Before running the script, install the latest OTA update through the updater app and reboot once that is done.
The script is quite self explanatory. The steps are:
Download the latest LOS zip using downloadLOS.py script.
Extract boot.img and vbmeta.img from the zip using unzip and update-payload-extractor. These are needed for rooting.
Copy boot.img to phone's Download folder.
Here the script pauses, waiting for you to go into Magisk app to patch the boot.img that was just copied. Hit any key once you are done.
The patched boot image is copied to your computer and both boot images are removed from the phone.
The phone now reboots into bootloader. The script pauses. Hit any key once your phone is in bootloader.
Both boot_a and boot_b are flashed with patched boot image. vbmeta partition is also flashed.
The phone reboots.
Firmware files are cleaned from your folder.
flash.sh
Bash:
#!/bin/bash
echo "Launching python script to download latest firmware ..."
python3 ./downloadLOS.py
echo ""
echo "Extracting boot.img ..."
echo "----"
unzip lineage*.zip 'payload.bin'
python3 ./scripts/update-payload-extractor/extract.py payload.bin --output_dir ./ --partitions boot vbmeta
echo "----"
echo ""
echo "Copying boot.img to phone... "
echo "----"
adb push ./boot.img /storage/emulated/0/Download
echo "----"
echo ""
read -t 1 -n 1
echo "Press any key after done patching boot... "
while [ true ] ; do
read -t 3 -n 1
if [ $? = 0 ] ; then
break ;
else
continue ;
fi
done
echo "Copying patched boot.img to PC... "
echo "----"
adb shell mv /storage/emulated/0/Download/magisk_patched* /storage/emulated/0/Download/magisk_patched.img
adb pull /storage/emulated/0/Download/magisk_patched.img magisk_patched.img
echo "----"
echo ""
echo "Removing boot images from phone... "
echo "----"
adb shell rm /storage/emulated/0/Download/boot.img
adb shell rm /storage/emulated/0/Download/magisk_patched.img
echo ""
echo "Rebooting to bootloader... "
echo "----"
adb reboot bootloader
read -t 1 -n 1
echo "Press any key when in bootloader... "
while [ true ] ; do
read -t 3 -n 1
if [ $? = 0 ] ; then
break ;
else
continue ;
fi
done
echo "----"
echo "Flashing both boots... "
echo "----"
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
echo "----"
echo ""
echo "Flashing vbmeta... "
echo "----"
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
echo "----"
echo ""
fastboot reboot
echo ""
echo "Done rooting!"
echo "Cleaning up local files ..."
rm *.img
rm *.bin
rm *.zip
echo "Complete!"
Notes
If you have slow internet and do not want to download the update twice. You could remove the whole downloadLOS.py section and use a separate script pullLOS.sh to pull the LOS update from your phone BEFORE YOU REBOOT after installing the update. After you reboot you loose root and cannot access it. For this you will need to enable rooted debugging in developer options.
Bash:
#!/bin/bash
adb root
echo "Copying update zip from the phone ..."
adb shell mv /data/lineageos_updates/lineage* /data/lineageos_updates/lineage.zip
adb pull /data/lineageos_updates/lineage.zip lineage.zip
adb shell rm /data/lineageos_updates/lineage.zip
echo "----"
echo ""
Attachment
Attachments contains:
scripts folder for your convenience containing LOS extractor scripts. Feel free to remove and re-download from source.
downloadLOS.py python script to download the latest LOS zip from the website.
flash.sh the main script
pullLOS.sh optional script for those who want to avoid re-downloading OTA update.
I hope you guys find it helpful! Let me know if you encounter any problems.

Doesn’t your device factory reset afterwards?

Will it copy your data over to your device again?

I think you are misunderstanding something. This is only if you already have LineageOS 19.1 and Magisk root.
LineageOS has over the air (OTA) updates. They release them every week. They do not touch your data. You just install through Settings -> System -> Updater, reboot and you are good to go. The same way OTAs work in OOS.
The problem is that you loose your Magisk root. In order to bring it back you need to patch and flash a boot partition again (and also vbmeta). Flashing boot partition does not do anything to your data. The script just automates what you would have to do by hand.

Isn't it the same outcome as with Magisk "Install on inactive partition after OTA" option?
I always install OTAs and select that option on Magisk and reboot.

jfromeo said:
Isn't it the same outcome as with Magisk "Install on inactive partition after OTA" option?
I always install OTAs and select that option on Magisk and reboot.
Click to expand...
Click to collapse
You could be right, but I have never seen / not been able to find this option. Maybe it is only available right after an OTA, don't know.