How To Guide Delete magisk module from bootlooping phone

How To Guide Delete magisk module from bootlooping phone - POCO M3 Pro / Redmi Note 10 5G

This guide will be about deleting a magisk module that caused your phone to bootloop. Definetly works with Xiaomi Redmi Note 10 5G, let me know if it works on Poco M3 Pro as well.
Prerequisites:
- rooted phone with magisk installed
- usb data cable
First you have to boot into safe mode which will disable the loading of all magisk modules:
- Turn off the smartphone completely.
- Turn it on normally and when the MIUI logo appears, press and hold the volume down button until the system boots completely, and you see the lock screen, it should also display "safe mode" in the bottom left corner.
Next enable USB debugging on your phone and connect it to a pc, then run
adb devices
If your devices is recognized and authenticated it will output:
List of devices attached
**************** device
where ************* is your device ID. If it writes 'unauthorized' then accept the prompt for authorization on your phone.
Now open an ADB shell from your pc:
adb shell
su
cd /data/adb/modules
ls
This will list all your installed magisk modules. Remove the problematic one with:
rm -r problematic_module
Done, reboot normally!
------------------------- If su command freezes the command line------------------------------
If somehow this does not work, for example you have not granted shell superuser rights before, then you have the following backup options:
run:
adb wait-for-device shell magisk --remove-modules
This should remove all installed modules, and reboot the phone. If it does not work from safe mode, you can try it during the boot animation. (After MIUI logo comes up adb gets enabled (check with 'adb devices' command, if adb is running))
If so far nothing worked you still have a third option to recover you phone/data:
--------------------- Nothing working ---------------------------
You can flash the stock boot.img from your currently installed stock ROM and it should boot your phone without magisk (but also no root). This will enable you to back up your phone/data, but if you want magisk again, you probably have reflash your ROM from fastboot again. This is because with no root access, and magisk not present in your boot image there is no way to remove the module that is causing the bootloop.
Feel free to comment, share your suggestions, and correct me on anything if I am wrong.

Gorg2331 said:
This guide will be about deleting a magisk module that caused your phone to bootloop. Definetly works with Xiaomi Redmi Note 10 5G, let me know if it works on Poco M3 Pro as well.
Prerequisites:
- usb debugging already enabled and authenticated (preferrably)
- rooted phone with magisk installed
- usb data cable
all you have to do is connect your phone to your PC and when it shows the MIUI logo during normal boot run
adb devices
If your devices is recognized and authenticated it will output:
List of devices attached
**************** device
where ************* is your device ID. If it writes unauthorized then skip to the "Other Method" section below. If you get back nothing try to run it a couple times during boot. I am not sure when adb gets enabled during the boot but should be around the MIUI logo appearing.
next write:
adb wait-for-device shell magisk --remove-modules
This will delete all magisk modules from your phone, and it reboot it automatically. It should boot up just fine, and all your magisk modules will be deleted.
---------------- Other method --------------------------
If you really need access to the phone, but do not have adb enabled:
You can flash the stock boot.img from your currently installed stock ROM and it should boot your phone without magisk (but also no root). This will enable you to back up your phone/data, but if you want magisk again, you probably have reflash your ROM from fastboot again. This is because with no root access, and magisk not present in your boot image there is no way to remove the module that is causing the bootloop.
Feel free to comment, share your suggestions, and correct me on anything if I am wrong.
Click to expand...
Click to collapse
just a thought on the above;
i haven't followed this topic anymore since the built-in functionality where modules are disabled if phone is in safe mode so i just thought to post it as a way to remind people that ( i think) most phones have a safe mode and with that , it might get you out of the bootloop.
I guess the above option is a great way too, but i think the use of safe mode makes it a lot easier.

pjottrr said:
just a thought on the above;
i haven't followed this topic anymore since the built-in functionality where modules are disabled if phone is in safe mode so i just thought to post it as a way to remind people that ( i think) most phones have a safe mode and with that , it might get you out of the bootloop.
I guess the above option is a great way too, but i think the use of safe mode makes it a lot easier.
Click to expand...
Click to collapse
That is a great suggestion, tho you cannot use any root applications since they will not be loaded. (Even if you install them during safe mode) But it should help sidestep the adb not authorized issue possibly! I incorporated safe mode in the post.

I used safemode purely to get rid of the troublesome modules( since you still have root access) . Then reboot the phone normal, and all should be fine/ you should be out of the bootloop
And i know the safemode is a bit off topic compared to what you are writing about, but it might help getting back into the phone

pjottrr said:
I used safemode purely to get rid of the troublesome modules( since you still have root access) . Then reboot the phone normal, and all should be fine/ you should be out of the bootloop
And i know the safemode is a bit off topic compared to what you are writing about, but it might help getting back into the phone
Click to expand...
Click to collapse
Oh you are totally right! You can use safe mode to remove the problematic modules with rm -r. But I think this only works if you have previously granted shell superuser rights. (Since in safe mode you will not get prompts to give SU rights)

I confirm, your guide Is correct. Now i have installed a modules called magisk bootloop saver. Works fine. Do the same thing without digit the adb command.

i'd also suggest in case of BOOTLOOP (cause of bad magisk module)
you can still fastboot
Code:
fastboot flash boot boot.img
the ORIGINAL boot.img of your actual ROM ( so everytime you root keep a copy of the original BOOT.IMG)
in that case you'll be able to reboot your phone ( without root ) and without losing any data !

yes, all these suggestions are good and 100% work! great thread

Booting into Safemode, adb shell and deleting the bad module worked great, thank you!

Related

[Solved] X8 unable to enter xRecovery / Flashmode

Hello,
I've had my phone rooted for a long time and things were working out quite fine (yes, I have a recent xRecovery backup ) but a couple of days ago I wanted to try out something new, and wanted to prepare my system for the installation of a custom kernel.
Long story short: I used the busybox installer from the market, but it couldn't verify the installation process because of some previously installed busybox version (guess it came with my ROM...) So I used the uninstall option within the app and this is were things started to go down the drain:
Now when I reboot the phone, it's no longer possible to enter xRecovery as it was possible before (pressing back button repeatedly, during SonyEricson Logo) instead the it just reboots straight into Android. And in Android all that works is the log screen - all other applications / services crash. (I really can't do anything, as soon as I try to unlock the screen I'm bombarded with Error Messages, and sometimes the phone reboots because so many services fail)
I still can get into the reboot options menu when I press the power button > 1sec, but selecting "reboot into xRecovery" or "reboot into CWM" doesn't work -> it will just reboot normally again.
It also seems impossible to get the phone into flash mode. (Turn Phone off, Unplug USB, hold Back Button, Turn Phone on, Connect USB - and every possible variation I could find just leads to the phone booting into Android)
What I tried to do:
I still have root access when I connect to the phone with adb, so I reinstalled the busybox binary from the "SuperOneClick" package into the /system/xbin/ folder manually -> no change
I checked the debug log (from adb logcat) for errors indicate a problem, but there's no obvious message
I checked the dmesg output for errors / problems, but here everything seems to be fine
I reinstalled xRecovery manually (files from SuperOneClick) via adb by putting the files (xrecovery.tar+chargemon), into /system/bin -> no change
I tried to get into recovery / bootloader mode by using "adb reboot bootloader" and "adb reboot recovery" -> normal reboot
I checked the permissions of the binary files (su, busybox, chargemon) and they're all set to 06755
I checked if all symlinks of system programs that require busybox / su are pointing to existing binaries, and they all seem to be correct
Before I proceed and start trying some things that are not so easily reversible I've got a couple of questions:
What happens if I delete all files in the "/system/" folder? (the xRecovery files are in that folder and I guess xRecovery itself needs a couple of files to work properly)
Do you have any tips / ideas what I could try? I really don't mind resetting the phone as I have backups, it's just that I can't get into the mode where I can reset the phone
Thank you very much!

In your case, i suggest you never ever, ever fiddle up with busybox again... leave that up to chefs.
Also, i think you should try removing the battery for a couple minutes, then put it back and press back, then (while holding it) insert usb cable. That's a surefire way to get into flash mode (At least for me, sometimes it happens to boot normally even if i press back if i don't remove the battery). Also, just to be sure, before connecting your phone in flash mode, press Windows + R [In your keyboard, obviously] and type "devmgmt.msc" [Without the quotes] and see if you get a new device under USB devices. If it has a yellow triangle, right click it and choose update drivers, then point it to the flashtool folder for drivers, it should be able to find them. Good luck.

Use PCC
PCC Brought my phone to its original state when I had soft bricked my phone. It worked as a charm , and it was back to the state like nothing ever happened. Also my phone got unrooted. Everything stock like I had bought it from the store.
Use PCC , thereafter get your phone rooted again , as you had initially done.

Dude are you kidding me???You are doing it wrong man...
to get into flashmood
1. turn your phone off
2.press and hold the back button
3.without leaving the back button insert ur phones cable ..
you don't. need to turn on your phone after doing this....
use pcc or seus to repair it it's a soft brick......

@all that replied: Thank you for your help, I managed to fix the problem, will explain it in next post in case somebody runs into a similar problem
@Drknzz
about the fiddeling: that's how you learn stuff - in the last 36 hours I was forced to dig deep into android, and it was fun - and now I've got a pretty good picture of the system
Your your tip about removing the battery for a cpl of minutes didn't work for me.
I also tried XperiaRebootOptions, but this app also fails putting the phone into FASTBOOT mode - so I'll have to keep searching for an explanation
@Mayank77
I can't use PCC, because I'm running Linux as my O/S of choice and try to keep my VirtualBox locked (when I was very desperate this morning I tried it in a VirtualMachine, but PCC wouldn't connect properly to my phone)
@noobismyname
thanks, but doesn't work in my case

a little description of how you can solve problems (using Linux) with incompatible versions of su and busybox that can occur when Market Apps like BusyBoxInstaller are used in combination with ROMs that require specific Versions of the above tools.
In special cases this might lead to the problem, that you can no longer enter xRecovery or put your phone into fastboot mode (depending on your ROM) but you still have debug access to your phone.
Requirements
Nandroid / xRecovery Backup on your local machine
Android SDK -> adb
Image extraction tool unyaffs
root access to phone
Steps
Extract the backup image
The backup files created by xRecovery use an uncommon format because of the filesystem used in android. Use the tool unyaffs (code dot google dot com/p/unyaffs) to extract the image to a directory of your choice.
log into you phone with adb
open up a terminal, and use $adb shell to connect to your phone. Change to root user $su root
If required: make the partition writeable
$mount -o remount,rw -t yaffs2 /dev/block/mtdblock0 /system
compare files
open a second terminal window and navigate to the folder where you extracted the backup image. Start comparing the content of the directories with each other. Important files are: /system/build.prop, /system/bin/su ->symlink to system/xbin/su, /system/xbin/busybox, ...... (depending on what you messed up)
the command $busybox ls -l /system/targetdir | grep sought_file [/] comes in handy, because it will output the files alphabetically sorted and not in arbitrary order like the default adb ls proproamm
[*]use adb to push files to your device
if you find a missing / missmatching file use $adb push /file/on/your/pc /data/local/tmp to copy the backup file to your mobile
[*]copy files to target directory
use (as root) $ cp /data/local/tmp/file /system/..... to copy your backup into the correct place
[*]check permissions
check the permission of every file you copied and in case you're unsure: they should belong to root, group root, access permission 755 (or 06755 in case of busybox and su)
$ls -l /target/dir | grep filename to check
$chown root /target/file
$chgrp root /target/file
$chmod 755 /target/file
[*]make sure changes are written to disk
flush all pending filesystem changes $sync
[*]reboot
exit the adb session with ctrl+c
and use adb reboot to restart & enjoy your phone

Rooted with kingroot and replaced with SuperSu, TWRP and Xposed

Hi everyone. My aim here is to present a more clear Tutorial... not sure if i'll succeed, but i want to try. :good: Good Luck. Your results may be different.
A word of Caution: These steps will soft brick the phone and erase all data from your phone. Proceed with caution.
A huge thanks to:
emowing
quyvinh
jemmini
John Hale
kingroot
I refered to these posts when I was rooting:
http://forum.xda-developers.com/vivo-xl/how-to/root-tutorial-t3313120
http://forum.xda-developers.com/vivo-xl/development/recovery-t3311601
https://drive.google.com/folderview?id=0B0g-ojj_rL70czVOZERhY3AxeHc#
http://forum.xda-developers.com/vivo-xl/development/root-confirmed-blu-vivo-xl-unlock-t3314010
Download the BLU Vivo XL Backup from https://www.dropbox.com/s/x4lgfv27jtgirkh/Blu_VivoXL_backup-2016-03-05.zip . This is required to unbrick the phone.
WARNING: THE METHOD I FOLLOWED WILL ERASE ALL DATA ON THE PHONE. I really didn't care for the data on the phone so I didn't create a backup. You could google for steps to make a backup before continuing.
I did these on a Windows 7 machine. I didn't take any screenshots. This was totally random effort.
1. Ensure ADB Universal Drivers, adb.exe and fastboot.exe are installed. Use google search. I used this one http://rootjunkysdl.com/?device=Amazon Fire 5th gen. Even though it is for Amazon 5th gen Fire tablet, it worked for BLU Vivo XL
2. Enable 'Developer Options'
3. Enable 'USB Debugging'
4. Connect the phone to the computer.
If you are doing this for the first time then...
The phone will show up as a new 'cd' drive
Open that and you should see the software to install official drivers for the phone
Install the drivers using that software.
If you have previously connected the phone then it will show up like a 'USB flash storage' device with 2 partitions - Phone and SD Card5. Run 'adb.exe' in command prompt ( i assume you know how to do this)
6. Run adb devices and make sure that adb is able to communicate with the phone.
At some point, there will be a pop up on the phone with a key to enable the computer to securely connect to the phone. I don't know what this is called , but it is needed. Make sure you choose to remember this key permanently on the phone.
7. Root the phone with 'Kingroot' (Yes, this is odd, but this is required to get the TWRP recovery to load)
The reason i say this is needed is because without the root when I tried to install the TWRP recovery i got the error saying that there is no root access and therefore TWRP recovery file cannot be copied to the phone
[a] go to kingroot (dot) net and get the latest kingroot apk
try to root with kingroot. the first time i did this it didn't work. kingroot app said there is 'root' method available but it couldn't root.
[c] i uninstalled kingroot
[d] then i installed purify from play store
[e] rebooted the phone
[f] installed kingroot again and tried root again and this time it worked. (go figure...)
[g] so YMMV.
if you rooted successfully with Kingroot, then you can continue, otherwise.... try again till you can root with kingroot

8. reboot the phone
9. Go to developer options and enable the option - 'Enable OEM Unlock'
CAUTION: The next steps will soft brick your phone.
10. Run adb.exe. check connectivity using command 'adb devices'
11. Run command 'adb reboot bootloader' (this will put the phone in fastboot mode)
12. Make sure the TWRP recovery is in the same folder as the adb.exe file. (get the twrp recovery from here http://forum.xda-developers.com/vivo-xl/development/recovery-t3311601)
13. Run command 'fastboot oem unlock'. At this point, there will be a prompt on the phone to confirm the action. Read it carefully, it clearly says that this process will wipe all data.
14. Press 'volume up' on the phone to confirm. It should take a few seconds. Then the phone will become unresponsive. Pressing volume up/down buttons or power button doesn't do anything.
15. Run command 'fastboot reboot-bootloader'
16. Run command 'fastboot flash recovery recovery.img'
17. Run command 'fastboot reboot'. When the phone is rebooting press volume up. If everything went well, This will put the phone in TWRP recovery mode.
18. When the phone enters TWRP recovery mode, it'll ask for 'write permissions'. I swiped to enable the write permissions.
19. At this point, the phone has no OS.
20. On the PC, extract the files downloaded from https://www.dropbox.com/s/x4lgfv27jtgirkh/Blu_VivoXL_backup-2016-03-05.zip
21. With the phone connect to the PC and adb running. Run command adb devices. The phone must be listed as 'xxxxxxxxxxxxxxxxx recovery'
22. You will have to push the back up files to twrp backup using adb
23. The general command is 'adb push <local> <remote>'. This is what i did for each of the files. Be patient, this will take time.
adb push "C:\boot.emmc.win" /data/media/TWRP/BACKUPS/BLU_VIVO_XL/2016-03-05/boot.emmc.win
adb push "C:\logo.emmc.win" /data/media/TWRP/BACKUPS/BLU_VIVO_XL/2016-03-05/logo.emmc.win
adb push "C:\logo.emmc.win.md5" /data/media/TWRP/BACKUPS/BLU_VIVO_XL/2016-03-05/logo.emmc.win.md5
adb push "C:\nvram.emmc.win" /data/media/TWRP/BACKUPS/BLU_VIVO_XL/2016-03-05/nvram.emmc.win
adb push "C:\nvram.emmc.win.md5" /data/media/TWRP/BACKUPS/BLU_VIVO_XL/2016-03-05/nvram.emmc.win.md5
adb push "C:\secro.emmc.win" /data/media/TWRP/BACKUPS/BLU_VIVO_XL/2016-03-05/secro.emmc.win
adb push "C:\secro.emmc.win.md5" /data/media/TWRP/BACKUPS/BLU_VIVO_XL/2016-03-05/secro.emmc.win.md5
adb push "C:\system.ext4.win000" /data/media/TWRP/BACKUPS/BLU_VIVO_XL/2016-03-05/system.ext4.win000
adb push "C:\system.ext4.win000.md5" /data/media/TWRP/BACKUPS/BLU_VIVO_XL/2016-03-05/system.ext4.win000.md5
adb push "C:\system.ext4.win001" /data/media/TWRP/BACKUPS/BLU_VIVO_XL/2016-03-05/system.ext4.win001
24. Once all the files are copied to the phone. Go to TWRP Restore option and then do a restore from the backup you just uploaded 2016-03-05.
25. After the restore is successfull and complete, TWRP will automatically ask to install 'SuperSu'.
26. Choose 'yes' and install SuperSu
27. TWRP will recover the phone and root the phone with SuperSu
If all of the above worked then install Xposed as per instructions in http://forum.xda-developers.com/vivo-xl/development/root-confirmed-blu-vivo-xl-unlock-t3314010
GOOD LUCK !!! :good::good::good:

Please help me on rooting my Blu vivo XL I upgraded it to Android 6.0 and now it does not root. Please help.

hamilLewiston said:
Hi everyone. My aim here is to present a more clear Tutorial... not sure if i'll succeed, but i want to try. :good: Good Luck. Your results may be different.
A word of Caution: These steps will soft brick the phone and erase all data from your phone. Proceed with caution.
A huge thanks to:
emowing
quyvinh
jemmini
John Hale
kingroot
I refered to these posts when I was rooting:
http://forum.xda-developers.com/vivo-xl/how-to/root-tutorial-t3313120
http://forum.xda-developers.com/vivo-xl/development/recovery-t3311601
https://drive.google.com/folderview?id=0B0g-ojj_rL70czVOZERhY3AxeHc#
http://forum.xda-developers.com/vivo-xl/development/root-confirmed-blu-vivo-xl-unlock-t3314010
Download the BLU Vivo XL Backup from https://www.dropbox.com/s/x4lgfv27jtgirkh/Blu_VivoXL_backup-2016-03-05.zip . This is required to unbrick the phone.
WARNING: THE METHOD I FOLLOWED WILL ERASE ALL DATA ON THE PHONE. I really didn't care for the data on the phone so I didn't create a backup. You could google for steps to make a backup before continuing.
I did these on a Windows 7 machine. I didn't take any screenshots. This was totally random effort.
1. Ensure ADB Universal Drivers, adb.exe and fastboot.exe are installed. Use google search. I used this one http://rootjunkysdl.com/?device=Amazon Fire 5th gen. Even though it is for Amazon 5th gen Fire tablet, it worked for BLU Vivo XL
2. Enable 'Developer Options'
3. Enable 'USB Debugging'
4. Connect the phone to the computer.
If you are doing this for the first time then...
The phone will show up as a new 'cd' drive
Open that and you should see the software to install official drivers for the phone
Install the drivers using that software.
If you have previously connected the phone then it will show up like a 'USB flash storage' device with 2 partitions - Phone and SD Card5. Run 'adb.exe' in command prompt ( i assume you know how to do this)
6. Run adb devices and make sure that adb is able to communicate with the phone.
At some point, there will be a pop up on the phone with a key to enable the computer to securely connect to the phone. I don't know what this is called , but it is needed. Make sure you choose to remember this key permanently on the phone.
7. Root the phone with 'Kingroot' (Yes, this is odd, but this is required to get the TWRP recovery to load)
The reason i say this is needed is because without the root when I tried to install the TWRP recovery i got the error saying that there is no root access and therefore TWRP recovery file cannot be copied to the phone
[a] go to kingroot (dot) net and get the latest kingroot apk
try to root with kingroot. the first time i did this it didn't work. kingroot app said there is 'root' method available but it couldn't root.
[c] i uninstalled kingroot
[d] then i installed purify from play store
[e] rebooted the phone
[f] installed kingroot again and tried root again and this time it worked. (go figure...)
[g] so YMMV.
if you rooted successfully with Kingroot, then you can continue, otherwise.... try again till you can root with kingroot

Yes
Sent from my chronos_ace using XDA Free mobile app

Yes, is it for marshmallow? Or yes, is it for lollipop? Or does it work for both? Please clarify.

Please help ME my phone vivo v 5 plus root How To

Gungho-sd said:
Yes, is it for marshmallow? Or yes, is it for lollipop? Or does it work for both? Please clarify.
Click to expand...
Click to collapse
From what I've read this would only work for Lollipop, as apparently kingroot no longer works on Marshmallow.

Changing /system folder permissions causes bootloop

Alright, maybe I did something stupid, but I don't think so...
I unlocked the bootloader, used the R2 version to remotely launch TWRP (can't get the phone to do it) and then rooted with Magisk. All as recommended.
Ad Away wouldn't work because the permissions weren't set right for system/etc/host directory. So, I used Solid Explorer to change the system directory permissions (rwxrwxrwx -R). Probably overkill, but just wanted to eliminate the issue of permissions.
Shortly after executing the command, I got an error "couldn't remount" and the phone rebooted into a bootloop, which leads to a recovery that won't launch (TWRP won't launch from the phone).
I can stop the bootloop and get into the bootloader, but can't "see" the phone in PC ADB.
Anyone have advice on how to proceed?

In bootloader or recovery it wont be ADB but Fastboot. Try "fastboot devices" and see if the pc sees it.
Also Magisk is a systemless root and they have in option in their main app to allow host file to be written to system/ect/host/.

Will installing TWRP allow adb root?

I just want to run a couple of 'setprop' commands to enable cam2api and eis.
To install twrp, we need oem unlock, of course. Once installed, would I be able to connect via usb and run 'adb root', to then do the setprop commands?
I'm just trying to keep it simple, enable cam2api and eis, and go back to stock, if possible.
Sound do able?

Actually, now that I think about it, maybe twrp isn't needed at all for 'adb root'? Maybe just unlock bootloader, device resets, enable dev and adb, connect usb and then 'adb root'?
without oem unlock (iow, as it is now); 'adb root' returns 'adbd cannot run as root in production builds'. But with oem unlock then it may work?

AsItLies said:
I just want to run a couple of 'setprop' commands to enable cam2api and eis.
To install twrp, we need oem unlock, of course. Once installed, would I be able to connect via usb and run 'adb root', to then do the setprop commands?
I'm just trying to keep it simple, enable cam2api and eis, and go back to stock, if possible.
Sound do able?
Click to expand...
Click to collapse
You do not need twrp. You need root access. Even then you cannot just run "adb root" because debugging and secure flags in the default.prop (which is compiled into vendor and boot images) disable that exact command. I was able to find a workaround though. You still need root (systemless should allow ota updates so don't worry about that) but in place of "adb root" run the following.
adb shell
su
mount -o rw,remount -t ext4 /system
exit
This will do the same thing, just through adb shell instead of straight adb.
If you really want to go stock, (no root) you can root the device and download a build prop editor (tons of them on the play store) edit the values you want, then unroot by flashing the stock boot.img. Just keep your bootloader unlocked. You're welcome!

For those following along on this adventure
One thing you can do now, if you haven't already, is be sure you have the (one of the) recent versions of fastboot installed. Older versions don't recognize multiple 'slots' (The A & B slots on the MiA2). The following link has the packages for Linux, Windoh's, and Mac.
To test your fastboot just use 'fastboot -h' and you'll want to see options like '--slot' and '--set-active[=SLOT]. If you have that already, at least this part is accomplished, if not, need to update your fastboot.
https://developer.android.com/studio/releases/platform-tools
Great info @Daha3ker - looking for a simple systemless root now. Trying to keep it all as simple as possible

AsItLies said:
For those following along on this adventure
One thing you can do now, if you haven't already, is be sure you have the (one of the) recent versions of fastboot installed. Older versions don't recognize multiple 'slots' (The A & B slots on the MiA2). The following link has the packages for Linux, Windoh's, and Mac.
To test your fastboot just use 'fastboot -h' and you'll want to see options like '--slot' and '--set-active[=SLOT]. If you have that already, at least this part is accomplished, if not, need to update your fastboot.
https://developer.android.com/studio/releases/platform-tools
Great info @Daha3ker - looking for a simple systemless root now. Trying to keep it all as simple as possible
Click to expand...
Click to collapse
My tool installs systemless and removes it. If you choose root, do what you need to do, then unroot you should be good. The toolkit is about as simple as it gets right now when it comes to rooting.
https://forum.xda-developers.com/mi-a2/how-to/mi-a2-toolkit-unlock-bootloader-root-t3834585
Otherwise you can use https://forum.xda-developers.com/mi-a2/how-to/guide-how-to-root-xiaomi-mi-a2-magisk-t3831586
root your phone, do what you like then follow the same steps to flash the stock boot.img instead of the rooted version.
P.S. All root options available right now are systemless unless you install a custom rom.
P.P.S. Setprop commands are used systemlessly (Applied at boot using magisk). so if you unroot, your custom values will not stay. You must edit the actual build.prop
A set of steps to try:
1. Root the device. Toolkit or Manually
2. Install https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor&hl=en_US or similar on your phone.
3. Add the following to the end of the build.prop
persist.camera.HAL3.enabled=1
4. reboot phone and verify it is enabled using https://play.google.com/store/apps/details?id=com.airbeat.device.inspector or similar. If level 3 is green then you are good, if not then I may be missing another value that needs changing.
5. unroot the device using the same method you used earlier to root the device. Toolkit or Manually
6. reboot and see if the settings stuck. I am curious to see if it works..

[Guide] How to Unlock and Magisk Root on Stock OOS 9.0.7 (For Beginners)

NOTE: Since I am a semi-amateur at unlocking/rooting, this is not independent development. Instead, I noticed these forums don't seem to have a single one-stop guide that lays out the process for safely rooting the latest (9.0.7) Oxygen OS 9.0.7. This process may seem obvious to experts, but for people who are rusty or new to this, I wanted a process that didn't require lots of extra cross-referencing and research. I hope this is ok.
Big thanks to Dameon87 who supplied the patched boot rom, and deserves all the credit for the actual hard work with the patched boot image.
STEP 1: PREPARATION
Check that your phone is on 9.0.7.
On PC: Download patched_boot-9.0.7.img and MagiskManager-v6.0.1.apk from Dameon87's thread ( https://forum.xda-developers.com/oneplus-6t/how-to/9-0-7-patched-magisk-boot-img-t3875498 ) . Download ADB Tools if you don't have them ( https://developer.android.com/studio/releases/platform-tools#download ) and extract to a folder. Copy patched_boot-9.0.7.img to your PC’s ADB root directory (the directory with fastboot.exe and adb.exe).
On phone: Boot into OOS. Navigate to Setup->About Phone. Tap Build Number until you turn on Developer Options.
On phone: Navigate to System->Developer Options. Enable OEM Unlocking and USB Debugging.
STEP 2: UNLOCKING
Connect your phone to your PC. Click ok on the OEM Debugging prompt on your phone.
On PC: Open a command prompt [Windows: Start->type "cmd.exe"], and navigate to the ADB tools directory. Run this command in the command prompt:
Code:
adb reboot bootloader
The phone should reboot to the bootloader.
On PC: When phone finishes rebooting to the bootloader, run this command in the command prompt:
Code:
fastboot oem unlock
IMPORTANT: ALL DATA WILL BE ERASED WHEN YOU DO THIS, INCLUDING ANY PERSONAL DATA, TEXTS, PHOTOS, MUSIC, ETC. If the phone has been used, please move your files off your device first! The phone will take some time to factory reset.
On Phone: Repeat Preparation Steps 3-4 to turn back on OEM Debugging in OOS.
STEP 3: INSTALLING MAGISK
On PC: Copy MagiskManager-v6.0.1.apk to the phone.
On PC: In the command prompt window, run this command (note this .img file should be in the adb.exe and fastboot.exe directory):
Code:
fastboot boot patched_boot-9.0.7.img
Phone will reboot.
On Phone: Use a file manager app to install MagiskManager-v6.0.1.apk (I use Astro or ES, but admittedly there are probably better ones out there).
On Phone: Open the Magisk Manager App, agree to the setup popup, and click install. When prompted, choose Direct Install.
On Phone: Reboot.
On Phone: In the OS, open Magisk Manager again and add MagiskHide exceptions.
This enabled all apps that I typically need SafetyNet for, including Pokemon Go, Netflix and Google Pay, as well as of course all root apps like TItanium Backup.
Again, apologies if this seems basic, but I hope this is useful for some who don't know all of the inner workings of android unlocking and rooting by heart. If you have any improvements, feel free to suggest them.

You need to change adb oem unlock to fastboot oem unlock. Otherwise good job!

Dameon87 said:
You need to change adb oem unlock to fastboot oem unlock. Otherwise good job!
Click to expand...
Click to collapse
Ah, thanks! Fixed.

Does OTA update lock bootloader?

BesoC said:
Does OTA update lock bootloader?
Click to expand...
Click to collapse
No it doesn't, the root will be lost though.

geminium said:
No it doesn't, the root will be lost though.
Click to expand...
Click to collapse
I'm also a semi amateur at unlocking/rooting so I'm the target audience of the OP.
Ready to get my hands dirty and try it out. Last time I rooted it was on my old phone before Magisk was a thing.
I ended up not updating out of laziness.
Does magisk make OTA updates / keeping the phone up to date easier?
What's the best method for doing so if you want to keep your phone rooted?

spudsrus said:
I'm also a semi amateur at unlocking/rooting so I'm the target audience of the OP.
Ready to get my hands dirty and try it out. Last time I rooted it was on my old phone before Magisk was a thing.
I ended up not updating out of laziness.
Does magisk make OTA updates / keeping the phone up to date easier?
What's the best method for doing so if you want to keep your phone rooted?
Click to expand...
Click to collapse
Well there's quite detailed procedure explained on the forum. You'll find easily...
In general, you have to restore images in magisk, then install OOS OTA update, then install magisk to inactive slot... It's one of the easiest steps for keeping root and be up to date .

I've been rooting for almost a decade and I am grateful for this. I don't know why some of these devs always assume you know when their talking about using a PC or running shell commands. Lol. Everyone started as a noob.
Sent from my OnePlus6TSingle using XDA Labs

ScaryBugThing said:
NOTE: Since I am a semi-amateur at unlocking/rooting, this is not independent development. Instead, I noticed these forums don't seem to have a single one-stop guide that lays out the process for safely rooting the latest (9.0.7) Oxygen OS 9.0.7. This process may seem obvious to experts, but for people who are rusty or new to this, I wanted a process that didn't require lots of extra cross-referencing and research. I hope this is ok.
Big thanks to Dameon87 who supplied the patched boot rom, and deserves all the credit for the actual hard work with the patched boot image.
STEP 1: PREPARATION
Check that your phone is on 9.0.7.
On PC: Download patched_boot-9.0.7.img and MagiskManager-v6.0.1.apk from Dameon87's thread ( https://forum.xda-developers.com/oneplus-6t/how-to/9-0-7-patched-magisk-boot-img-t3875498 ) . Download ADB Tools if you don't have them ( https://developer.android.com/studio/releases/platform-tools#download ) and extract to a folder. Copy patched_boot-9.0.7.img to your PC’s ADB root directory (the directory with fastboot.exe and adb.exe).
On phone: Boot into OOS. Navigate to Setup->About Phone. Tap Build Number until you turn on Developer Options.
On phone: Navigate to System->Developer Options. Enable OEM Unlocking and USB Debugging.
STEP 2: UNLOCKING
Connect your phone to your PC. Click ok on the OEM Debugging prompt on your phone.
On PC: Open a command prompt [Windows: Start->type "cmd.exe"], and navigate to the ADB tools directory. Run this command in the command prompt:
Code:
adb reboot bootloader
The phone should reboot to the bootloader.
On PC: When phone finishes rebooting to the bootloader, run this command in the command prompt:
Code:
fastboot oem unlock
IMPORTANT: ALL DATA WILL BE ERASED WHEN YOU DO THIS, INCLUDING ANY PERSONAL DATA, TEXTS, PHOTOS, MUSIC, ETC. If the phone has been used, please move your files off your device first! The phone will take some time to factory reset.
On Phone: Repeat Preparation Steps 3-4 to turn back on OEM Debugging in OOS.
STEP 3: INSTALLING MAGISK
On PC: Copy MagiskManager-v6.0.1.apk to the phone.
On PC: In the command prompt window, run this command (note this .img file should be in the adb.exe and fastboot.exe directory):
Code:
fastboot boot patched_boot-9.0.7.img
Phone will reboot.
On Phone: Use a file manager app to install MagiskManager-v6.0.1.apk (I use Astro or ES, but admittedly there are probably better ones out there).
On Phone: Open the Magisk Manager App, agree to the setup popup, and click install. When prompted, choose Direct Install.
On Phone: Reboot.
On Phone: In the OS, open Magisk Manager again and add MagiskHide exceptions.
This enabled all apps that I typically need SafetyNet for, including Pokemon Go, Netflix and Google Pay, as well as of course all root apps like TItanium Backup.
Again, apologies if this seems basic, but I hope this is useful for some who don't know all of the inner workings of android unlocking and rooting by heart. If you have any improvements, feel free to suggest them.
Click to expand...
Click to collapse
Can you elaborate a bit more on how you got Pokemon Go working.
OS. 9.0.2 Magisk v18. Successfully rooted.
I'm selecting Pokemon Go under Magisk hide. But it still detects it. PoKe will sometimes run for about 30 secs then it gives me the error incompatible os.
Sent from my [device_name] using XDA-Developers Legacy app

Ok I'm new to this as well..I'm trying to understand the patched boot img part...so do u need the patched boot img for whichever oos ur currently running so to install magisk cleanly is that it...also I can't find the tutorial on how to install the ota's after ur rooted to where everything doesn't get erased etc..I need sumone to point me in the right area to look..I found a lil bit on it once but now I can't seem to find it..thx to everyone in this great community for all the time and effort all put into this. It's so easy to overlook all the hard work that gets done behind the scenes..so I just thank u personally for what u do for us...

Database Develop

welcome