Database Users

How to flash TWRP in Android 10 Open Beta 1?

I have installed this today and now those fastboot commands don't work. Fastboot boot fails with the error (unknown command). Any idea about how to install TWRP in this scenario?

Bhargav97 said:
I have installed this today and now those fastboot commands don't work. Fastboot boot fails with the error (unknown command). Any idea about how to install TWRP in this scenario?
Click to expand...
Click to collapse
Where did you get the zip?

Play store has to be authorized and added, Google Pay that is, play services for the device/region. That way it will pass safetynet. If it doesn't include the safetynet info, when you try to use it, and verify, it fails. It takes awhile often for them to get it working.

Bhargav97 said:
I have installed this today and now those fastboot commands don't work. Fastboot boot fails with the error (unknown command). Any idea about how to install TWRP in this scenario?
Click to expand...
Click to collapse
You can't. Currently there's no working twrp for Android 10 open beta.

Yes, officially, no TWRP, firmware is updated/changed, plus fastboot boot is often disabled on these builds. Also, it will fail Safety Net, so no root, no twrp and no GPay....Android Q is a bust so far. There are TWRP for Guacamole, I tried those on the Chinese version, ended up hosing my phone..finally got it back working and back on stable 9.0.17 and rooted/twrp. I'm guessing we will need another month at least to get a stable/working Q for 6T, and TWRP/root.

In h2os 10...twrp 3.3.1-8 works
Personally used

sanjeev7 said:
In h2os 10...twrp 3.3.1-8 works
Personally used
Click to expand...
Click to collapse
As long as you don't update twrp in in twrp and flash it is magisk after local upgrade before reboot

techlogik said:
Yes, officially, no TWRP, firmware is updated/changed, plus fastboot boot is often disabled on these builds. Also, it will fail Safety Net, so no root, no twrp and no GPay....Android Q is a bust so far. There are TWRP for Guacamole, I tried those on the Chinese version, ended up hosing my phone..finally got it back working and back on stable 9.0.17 and rooted/twrp. I'm guessing we will need another month at least to get a stable/working Q for 6T, and TWRP/root.
Click to expand...
Click to collapse
Magisk working fine and safety net passes.

Noob_Master said:
Magisk working fine and safety net passes.
Click to expand...
Click to collapse
how did you manage that? did you manage to flash twrp? or did you manage to root the phone without it?

i havent been able to get a working TWRP on it yet however i have managed to get working root with magisk, see my post about it here https://forum.xda-developers.com/on...agisk-pre-rooted-boot-img-oneplus-6t-t3986585

stardustsouls said:
how did you manage that? did you manage to flash twrp? or did you manage to root the phone without it?
Click to expand...
Click to collapse
1. Extract boot.img from OnePlus 6T Android 10 Open beta
2. Download magisk manager apk on OP6T
3. Place boot.img file on OP6T storage, and click "install" in the magisk manager app. There are two options, direct and one that will let you choose your boot.img file.
4. Place new modified file from downloads folder on OP6T back onto computer
5. Boot OP6T into fastboot mode (must already have unlocked bootloader, or this next one will not work!)
6. run "fastboot flash boot /location/of/file"
7. Profit

dtronics said:
i havent been able to get a working TWRP on it yet however i have managed to get working root with magisk, see my post about it here https://forum.xda-developers.com/on...agisk-pre-rooted-boot-img-oneplus-6t-t3986585
Click to expand...
Click to collapse
youre the bomb dude
---------- Post added at 08:54 PM ---------- Previous post was at 08:51 PM ----------
Odder1 said:
1. Extract boot.img from OnePlus 6T Android 10 Open beta
2. Download magisk manager apk on OP6T
3. Place boot.img file on OP6T storage, and click "install" in the magisk manager app. There are two options, direct and one that will let you choose your boot.img file.
4. Place new modified file from downloads folder on OP6T back onto computer
5. Boot OP6T into fastboot mode (must already have unlocked bootloader, or this next one will not work!)
6. run "fastboot flash boot /location/of/file"
7. Profit
Click to expand...
Click to collapse
you too lmao
now i can use viper4android again frick yeah

Noob_Master said:
Magisk working fine and safety net passes.
Click to expand...
Click to collapse
I tried the A/B Magisk TWRP retention script...and that didn't go well when I tried it.
Tried the fastboot method per your thread, that didn't work. Then tried the Magisk method and install, then select patched file, reboot, Magisk says it isn't installed and ctsProfile fails Safetynet.
Thanks

techlogik said:
I tried the A/B Magisk TWRP retention script...and that didn't go well when I tried it.
Tried the fastboot method per your thread, that didn't work. Then tried the Magisk method and install, then select patched file, reboot, Magisk says it isn't installed and ctsProfile fails Safetynet.
Thanks
Click to expand...
Click to collapse
Same, tried both methods and also got stuck on boot loop.

Tested the thread HERE and it worked for me I have the phone rooted without TWRP.
I already had the Magisk apk installed on the phone and flashed the img as mentioned in the thread and it worked.

To whom it may concern. I followed this method and it works flawlessly.
1. Magisk Manager > Tap "Uninstall" > Tap "Restore Images" (DO NOT REBOOT)
2. Now Run the System update to download and install the full OTA zip (DO NOT REBOOT)
3. Close all background apps
4. Open Magisk > Tap "Install" > Tap "install" again > Tap "Install to Inactive/Second Slot (After OTA)"
5. Finally tap Reboot after Magisk installation is complete.

Finally just gave up on TWRP and did the normal OTA procedure above, then patched inactive in Magisk. Now rooted, just no TWRP.
So the above works, just make sure you have the right full Android Q from the official thread and follow the above.

Odder1 said:
1. Extract boot.img from OnePlus 6T Android 10 Open beta
2. Download magisk manager apk on OP6T
3. Place boot.img file on OP6T storage, and click "install" in the magisk manager app. There are two options, direct and one that will let you choose your boot.img file.
4. Place new modified file from downloads folder on OP6T back onto computer
5. Boot OP6T into fastboot mode (must already have unlocked bootloader, or this next one will not work!)
6. run "fastboot flash boot /location/of/file"
7. Profit
Click to expand...
Click to collapse
Thanks man. Worked flawlessly. :good:

alp47470 said:
Thanks man. Worked flawlessly. :good:
Click to expand...
Click to collapse
Could you please explain after the 2nd step? Im already unlocked bootloader on android 10.
What modified boot image and how install?
please explain

suhas2k said:
Could you please explain after the 2nd step? Im already unlocked bootloader on android 10.
What modified boot image and how install?
please explain
Click to expand...
Click to collapse
Sure,
1. Unlock Bootloader
2. Install Magisk Manager - Magisk - Install - Select the boot.img When finished.
3. Reboot to Bootloader and flash the same boot.img file.
4. Boot OOSQ with Root.
https://t.me/aadarsh47
DM me if you couldn't get boot img file.
I'm getting some error uploading here.

Failed Update/Root Android 11

So I followed the steps to update to Android 11 while keeping Magisk. During this process, you uninstall magisk, you update, then you install magisk again before you reboot...more to it than that but you get the picture.
I got temporarily stuck in a boot loop, and when the phone did successfully reboot, it didn't update to Android 11 and Magisk isn't installed anymore. The system update page basically says 'restart now.'
I don't really want to lose root, I don't want to update and lose root and somehow lose my data trying to figure this out.
Any thoughts?

If you aren't using Magisk Canary, it won't work.

coachmarino said:
So I followed the steps to update to Android 11 while keeping Magisk. During this process, you uninstall magisk, you update, then you install magisk again before you reboot...more to it than that but you get the picture.
I got temporarily stuck in a boot loop, and when the phone did successfully reboot, it didn't update to Android 11 and Magisk isn't installed anymore. The system update page basically says 'restart now.'
I don't really want to lose root, I don't want to update and lose root and somehow lose my data trying to figure this out.
Any thoughts?
Click to expand...
Click to collapse
just back up your data first and then play around with it. just fresh install a11 then root

Losing root is only temporary and won't cause any trouble.
You just have to update to android 11, reboot, then once it boots with a clean boot img you can patch the boot img file with the latest magisk manager canary, then go in fastboot and flash the patched img.

TENN3R said:
Losing root is only temporary and won't cause any trouble.
You just have to update to android 11, reboot, then once it boots with a clean boot img you can patch the boot img file with the latest magisk manager canary, then go in fastboot and flash the patched img.
Click to expand...
Click to collapse
I don't tinker with my phone as much anymore...what's the process here?

coachmarino said:
I don't tinker with my phone as much anymore...what's the process here?
Click to expand...
Click to collapse
I usually do like this:
- Download full factory image, extract it from the zip and edit the "flash-all.bat" removing the "-w" from the last line, so it won't wipe the data while updating
- Inside the folder you extracted there is another zip, extract the boot.img from it
- Copy the boot image to the phone, and using the latest magisk canary select to install magisk updating a file, and select the image you just copied
- In generates a magisk_patched img, copy that on your adb folder on your pc
- Put phone in fastboot, start the edited flash all bat, once it ends the phone will reboot with your data but no root
- Go again in fastboot and run "fastboot flash boot magisk_patched.img --slot=all"
- Reboot, you should have root now

TENN3R said:
I usually do like this:
- Download full factory image, extract it from the zip and edit the "flash-all.bat" removing the "-w" from the last line, so it won't wipe the data while updating
- Inside the folder you extracted there is another zip, extract the boot.img from it
- Copy the boot image to the phone, and using the latest magisk canary select to install magisk updating a file, and select the image you just copied
- In generates a magisk_patched img, copy that on your adb folder on your pc
- Put phone in fastboot, start the edited flash all bat, once it ends the phone will reboot with your data but no root
- Go again in fastboot and run "fastboot flash boot magisk_patched.img --slot=all"
- Reboot, you should have root now
Click to expand...
Click to collapse
Perfect thank you

Android 11 is live.

Today just received update notification as below image. Downloading now, let see what are changes and improvements.

I'm enrolled in beta for Android 11 and got the September Security patch today. Will I get the stable release soon or should I opt out from beta and go for a fresh instal?

TenTuTego said:
I'm enrolled in beta for Android 11 and got the September Security patch today. Will I get the stable release soon or should I opt out from beta and go for a fresh instal?
Click to expand...
Click to collapse
You are automatically switched to the stable release. Check in your "About" settings.

tkachenko.ic said:
You are automatically switched to the stable release. Check in your "About" settings.
Click to expand...
Click to collapse
I have readed yesterday that, when Android 11 Stable is released, u can stay on beta program for beta features and experimental updates, also you can receive updates earlier than others.

Has anyone been able to successfully root using Magisk? I tried and bootlooped.
Edit: Magisk Canary works, but you CANNOT install TWRP as it hasn't been developed to work with A11 yet.

socal87 said:
Has anyone been able to successfully root using Magisk? I tried and bootlooped.
Click to expand...
Click to collapse
Use magisk canary

Anyone have the screen record enabled in power menu and how ?

khanhcc said:
Use magisk canary
Click to expand...
Click to collapse
not working for pixel2, same bootloop

monikmax said:
not working for pixel2, same bootloop
Click to expand...
Click to collapse
Are you using a custom recovery? TWRP does not work with A11 yet.
Extract the boot image from a factory ZIP and flash it in bootloader:
Code:
fastboot flash boot "boot.img"
Then, boot TWRP:
Code:
fastboot boot "twrp.img"
And install Magisk using the canary zip. Please note that you do not use the quotation marks.
Alternatively, you can boot to TWRP and sideload the OTA, then reboot to bootloader, boot TWRP again, and install Magisk.

V0latyle said:
Are you using a custom recovery? TWRP does not work with A11 yet.
Extract the boot image from a factory ZIP and flash it in bootloader:
Code:
fastboot flash boot "boot.img"
Then, boot TWRP:
Code:
fastboot boot "twrp.img"
And install Magisk using the canary zip. Please note that you do not use the quotation marks.
Alternatively, you can boot to TWRP and sideload the OTA, then reboot to bootloader, boot TWRP again, and install Magisk.
Click to expand...
Click to collapse
Magisk is installed, but after patched boot applied phone is bootlooping.
any ideas?

monikmax said:
Magisk is installed, but after patched boot applied phone is bootlooping.
any ideas?
Click to expand...
Click to collapse
You must use the Magisk Canary zip on the stock boot image. Regular Magisk will not work.

V0latyle said:
You must use the Magisk Canary zip on the stock boot image. Regular Magisk will not work.
Click to expand...
Click to collapse
Could you describe the procedure or write out the steps for rooting our device running on Android 11?

SoloMid Hazard said:
Could you describe the procedure or write out the steps for rooting our device running on Android 11?
Click to expand...
Click to collapse
Your bootloader must be unlocked to use this method.
Start fresh, use the OTA or the factory image. I did this coming from Android 10 without wiping.
Download the Magisk Manager Canary APK and installer ZIP here
Download the latest TWRP image here, put it in your platform tools folder and rename to twrp.img
Using platform tools, reboot your phone into bootloader:
Code:
adb reboot bootloader
Then, boot (DO NOT INSTALL) TWRP:
Code:
fastboot boot twrp.img
Install the Magisk Canary ZIP, reboot to system.

Yes I am using canary latest, and did everything as you explaining, still getting bootloop. But I will get done sooner or later )

hemal_4404 said:
Today just received update notification as below image. Downloading now, let see what are changes and improvements.
Click to expand...
Click to collapse
I am trying to screen record by the official android screen recorder app my phone doesn't records the video afte the recording is done and played laters only one thing pops in the video "gboard encountered a problem" and the same thing comes up whenever I try to record. Is someone facing the same issue?

V0latyle said:
Your bootloader must be unlocked to use this method.
Start fresh, use the OTA or the factory image. I did this coming from Android 10 without wiping.
Download the Magisk Manager Canary APK and installer ZIP here
Download the latest TWRP image here, put it in your platform tools folder and rename to twrp.img
Using platform tools, reboot your phone into bootloader:
Code:
adb reboot bootloader
Then, boot (DO NOT INSTALL) TWRP:
Code:
fastboot boot twrp.img
Install the Magisk Canary ZIP, reboot to system.
Click to expand...
Click to collapse
+1 on this method, worked for me, thank you for the instructions

I'm also bootlooping. Did you solve your problem?
I installed through the OTA button. Of course, I lost root, so I followed the above instructions, but am stuck at the G loading.
The canary zip is magisk-debug.zip, correct?
EDIT: I overlooked that I had EdXposed installed with active modules and I don't think it works with Android 11 yet, at least not the modules I use (Gravity box). I'll try rooting again tonight with EdXposed modules disabled.

Chilipepprflea said:
I'm also bootlooping. Did you solve your problem?
I installed through the OTA button. Of course, I lost root, so I followed the above instructions, but am stuck at the G loading.
The canary zip is magisk-debug.zip, correct?
EDIT: I overlooked that I had EdXposed installed with active modules and I don't think it works with Android 11 yet, at least not the modules I use (Gravity box). I'll try rooting again tonight with EdXposed modules disabled.
Click to expand...
Click to collapse
Yes, both the apk and the zip are named "magisk_debug".
I am not sure why you are bootlooping. If you installed the OTA, it should have overwritten /boot with the stock image, and flashing Magisk Canary should work. It is possible that if you had modules enabled before and didn't disable them, you could have issues.

V0latyle said:
Yes, both the apk and the zip are named "magisk_debug".
I am not sure why you are bootlooping. If you installed the OTA, it should have overwritten /boot with the stock image, and flashing Magisk Canary should work. It is possible that if you had modules enabled before and didn't disable them, you could have issues.
Click to expand...
Click to collapse
I disabled the edxposed modules and still got stuck at the G logo. I'm not sure what else I could be doing wrong, but it's obviously me or my setup. I'm going to downgrade to Android 10 because the modifications I rely on from GravityBox are more important to me than the new features of Android 11.
Thanks for the help.

Chilipepprflea said:
I disabled the edxposed modules and still got stuck at the G logo. I'm not sure what else I could be doing wrong, but it's obviously me or my setup. I'm going to downgrade to Android 10 because the modifications I rely on from GravityBox are more important to me than the new features of Android 11.
Thanks for the help.
Click to expand...
Click to collapse
Anyone have luck downgrading from 11 to 10? I've tried several different 10 builds and I get "Error: Slot Unbootable: Load Error" in bootloader.
I used the same commands I always use to upgrade builds:
fastboot flash radio radio-walleye-...img
fastboot reboot bootloader
fastboot update image-walleye-...zip
I can flash 11 again and all is fine, but I haven't been able to go back to 10.

Rooting Help

I've been running custom roms since before android was a thing so I'm usually pretty good at this stuff.
I'm running 11.0.9.9 IN11AA
It refuses to root. I'm not sure if there is some step I'm missing that's so obvious nobody mentions it?
I was rooted, but when the new Magisk 23 came out without Magisk hide.. it was a big problem for me. I have corporate apps that will refuse to work on a rooted device. I restored the stock images (just like I do to get my OTA).. but then I uninstalled Magisk 23 and Installed 22.1. I then patched the bootloader (Dire3ct Install) and all was good, until I rebooted and had no root.
My bootloader is unlocked.
So I downloaded the full stock rom v11.0.9.9 IN11AA directly from Oneplus.
Extracted payload.bin
Used Payload dumper to get the proper boot.img.
Copied boot.img to my device and used magisk 22.1 to patch the file.
Downloaded the patched boot.img to my desktop.
Used ADB to flash it
adb reboot bootloader
fastboot flash boot patched_boot.img
fastboot flash boot_a patched_boot.img
fastboot flash boot_b patched_boot.img
fastboot reboot
Nothing. No Root.
I tried this over and over with different versions of magisk.
I tried downloading pre-patched version, and using fastboot boot patched_boot.img.
The device just hangs, and then boots using the stock image. No root.
I have no idea what could be wrong.
Ideas?

I just updated from v11.0.8.8 to v11.0.9.9 today on the EU variant.
Downloaded the update via Oxygen Updater, then used the built in updater with the local file downloaded.
Before restarting the device, opened up Magisk, then clicked "Install to inactive slot" since the new update gets put on the inactive slot. After it installed, rebooted the phone, and done. Updated to latest, and kept root. Didn't even turn off the modules, although I only have 1 installed.
This is my usual method to keep root while updating.
I'm not sure where you got your Magisk from, but i'm using v23.0 from the official github page (HERE), and it still has MagiskHide built-in, and currently using it for all of my banking apps, and it works.
Most likely the issue is that you have used the old Magisk version to patch the file.
Download the app from the link above, and use that to patch your boot.img file.
While the extracted file should work as flashed, I like to just boot from it rather than flash it and make it "permanent".
Use fastboot boot patched_boot.img to boot using the file once only.
After starting up, you should have Magisk installed in a couple of seconds. It might prompt you to restart the phone when opening it first time, but just ignore that and do not restart as you'll lose the root. Alternatively, you can install the app when you're not rooted yet, and when you boot using the patched boot.img, you won't need to restart.
When done, Magisk should tell that you have 23.0(23000) installed.
Then just use the built-in Install > Direct Install (Recommended) option within Magisk to install it to the current slot.
Do NOT install it to inactive slot. This option only to be used when updating via OTA.
Other option:
Download the Magisk app from the link above, and rename it to magisk.zip then copy it to your phone.
Download TWRP from HERE to your PC and use fastboot flash recovery twrp.img to flash this recovery.
Reboot to recovery. (Might take 2-3 mins to boot first time)
Flash the magisk.zip using recovery.
That's all you should need to be able to root.

I appreciate the help.
I was so hopeful you gave me what I needed, but it didn't work.
So, It wasn't an update issue... it was more of an attempt to downgrade Magisk.
I always OTA the same way as you and it always works.
I also always get Magisk from the official Github page.
What I got excited about was that I wasnt aware there was a working TWRP! So I thought.. THAT will fix it.
I didnt flash it, I just booted from it. I flashed Magisk that way, BUT... still not rooted.
Here is the interesting bit.. when flashing Magisk via TWRP, it detected that my boot.img was already Magisk patched and not stock (Which is right). It's like the boot.img is correctly patched, Magisk just isn't seeing it.
I'd be ok with a full wipe and factory reset at this point, but I'm not even sure that will fix it.
** Edit - I tried manually flashing the latest full OOS downloaded from Oneplus. It didnt help. I finally factory reset and it's working now.

This is my fav. root method.
[GUIDE] Easiest way to root/magisk Oneplus 8 Pro
This method will not flash any custom recovery or any custom boots. Caution: I don't take any responsibility. Proceed with your own risk and resilience in mind Prerequisites: Oxygen OS 11 (tested with 11, issues reported with 10) and a PC with...
forum.xda-developers.com

ps000000 said:
This is my fav. root method.
[GUIDE] Easiest way to root/magisk Oneplus 8 Pro
This method will not flash any custom recovery or any custom boots. Caution: I don't take any responsibility. Proceed with your own risk and resilience in mind Prerequisites: Oxygen OS 11 (tested with 11, issues reported with 10) and a PC with...
forum.xda-developers.com
Click to expand...
Click to collapse
Agreed, this is a great method. I tried that too before I ended up doing a reset... no good. I somehow broke something with the rom outside of Magisk so that Magisk wouldnt work. Whatever it was, A full wipe fixed it..

Install TWRP via official app after you have root with magisk?

Hello there, back in the day (2019 in March or April the phone shipped with Android 9) I rooted my galaxy S10+ Exynos with Magisk and stock recovery (because TWRP method did not exist yet or did but non twrp method looked safer, I forgot the reason)
Then I forgot about TWRP and even upgraded to Android 10 like this:
(standard procedure, download android with Friya, then patch ap file with magisk, then flash it with odin)
Well I used my phone as always, forgot about twrp, but always had a little voice in my head telling me, that twrp is good idea, what if something happens, I would at least be able to copy my data)
So I decided to flash twrp, to ease my mind a bit, and also be able to copy apps to /system/priv-app
So I am using Android 10 (see no reason to upgrade, what I need is there I prefer OneUI 2.0 over later versions and I dont want to make my device slower or loose some obscure api function that I dont even know exists until I need it)
Now, can I just use official twrp app and let it do its thing (I have root), or do I need to download twrp with the app, but prepatch it with magisk before I install it? (I read conflicting info, on xda they say you need to prepatch it, while on twrp guide: https://twrp.me/samsung/samsunggalaxys10plus.html
They say to just use the app if you already have root, so I am confused now
It seams using the app is the easiest and most safe method
Thanks for Anwsering and Best Regards

only in case recovery and boot share the same partition, you will lose magisk after flashing TWRP (does not apply)

alecxs said:
only in case recovery and boot share the same partition, you will lose magisk after flashing TWRP (does not apply)
Click to expand...
Click to collapse
well, I gues this did apply to me, because I tried to flash TWRP with the app (latest version: twrp-3.7.0_9-2 that the app offered, it offered 2 files .img or .img.tar, and I chose to flash .img), and now my phone cannot boot, its stuck in download mode it says with red letters
kernel: Could not do normal boot, (DT LOAD failed)
I don't know know what happened, I only flashed recovery, and bootloader is unlocked
adb doesn't work
I cannot even get to recovery
So what now? Can at least flash TWRP somehow back so I can get ot my files (I have most of my videos on an SD card, but 2 or 3 are on internal storage )
I would reflash Android 10 anyway if it wasn't for the files

you can flash recovery.img as tar file but that is useless for backup stock ROM userdata. if you still have the magisk_patched.tar you can flash it to get your data back. don't flash unpatched stock boot.img this will most likely result in data loss.
I would first try older TWRP as DT LOAD failed (device tree) looks like TWRP problem to me.

alecxs said:
you can flash recovery.img as tar file but that is useless for backup stock ROM userdata. if you still have the magisk_patched.tar you can flash it to get your data back. don't flash unpatched stock boot.img this will most likely result in data loss.
Click to expand...
Click to collapse
OK
after installing TWRMP
3.4.0 I got into recovery​
I guess the latest version twrp-3.7.0_9-2 is broken (because I tried flashing from Odin and I got the same error
but 3.4.0 works now
Well then I got into a non rooted android state (I couldnt boot into the rooted one because if I held volume up I just got into TWRMP)
I do have my magisk patched AP file (I did keep that), so I tried flashing it by odin to get into rooted state again, but then got scared because I was aftaid it would delete my data, so pulled the plug out, immediately after I discovered its flashing system.img (it just started)
thats where I interupted it
<ID:0/035> SingleDownload.
<ID:0/035> dt.img
<ID:0/035> dtbo.img
<ID:0/035> system.img
<ID:0/035> __XmitData_Write
<ID:0/035> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
So then phone would not boot, not in TWRMP not in android anymore, so I flashed TWRMP again and now at least
I am in TWRMP (I can see my files, but they are encrypted (they have wierd names but size does seam to match my files)
So how do I reflash android now, without messing with /data partition?
or can I somehow backup just data partition, reflash android and flash /data back?

let the magisk_patched.tar flash, just make sure you don't flash CSC (HOME_CSC is fine it won't erase userdata)

alecxs said:
let the magisk_patched.tar flash, just make sure you don't flash CSC (HOME_CSC is fine it won't erase userdata)
Click to expand...
Click to collapse
Yey, that did it (that was scarry), now root works, as well as android 10 (for some reason Magisk Manager does not open (but all the magisk modules work)
Now, I did patch this ap file back in the day I updated android to 10 so
I used Magisk Manager 7.4.1.291c718b
and if I remember corecly (thanks got I recorded everything) I patched the AP file for Magisk 20.2-11b7076a)
Now I have Magisk Manager 8.0.7 installed
So after I downgraded my Magisk manager to 7.5.0 it opened
Now I just have to figure out how to install Magisk v21.4 which is the version that belongs to my Magisk Manager 8.0.7, because Magisk Manager won't let me install a custom magisk, it only wants to download the latest version

you can install latest Magisk apk and patch stock boot.img again. Anyway I would do a backup with Migrate and adb pull -a /sdcard first.
or you can paste this url as custom channel and install older magisk if you want to.
https://raw.githubusercontent.com/topjohnwu/magisk_files/b0694fad86/stable.json

alecxs said:
you can install latest Magisk apk and patch stock boot.img again. Anyway I would do a backup with Migrate and adb pull -a /sdcard first.
Click to expand...
Click to collapse
aha, I see
is there any other way besides patching my AP file again? (I mean Magisk can clearly update itself somehow)
I mean, Magisk Manager does open (but only version 7.5.0, not version 8.0.7), and I have root its just that I don't have Magisk Manager 8.0.7
So how do I install a specific Magisk version from Manager? (I did try to install like a Magisk module, but now I am stuck in download mode again, so lets install Android 10 again )

look in the json for download link
https://github.com/topjohnwu/Magisk/releases/download/manager-v8.0.7/MagiskManager-v8.0.7.apk
https://github.com/topjohnwu/magisk_files/commits/master/stable.json
https://github.com/topjohnwu/magisk-files/commits/master/stable.json

alecxs said:
look in the json for download link
https://github.com/topjohnwu/Magisk/releases/download/manager-v8.0.7/MagiskManager-v8.0.7.apk
https://github.com/topjohnwu/magisk_files/commits/master/stable.json
https://github.com/topjohnwu/magisk-files/commits/master/stable.json
Click to expand...
Click to collapse
OK, after I installed Android again (with my older prepatched magisk)
Not sure what happened but now Magisk Manager 8.0.7 opens and says I have 20.2-11b7076a installed
of course as this combo should not exist, magisk Manager cannot see any modules (modules are there in /data/adb/modules and they do work, its just that Magisk Manager cannot see them installed, which means you can not easly delete them and you could install them over and over again, since Manager would not know that they are there)
So now I need to find a way to update to Magisk 21.4
So how would I do that (I tried the module install method before (I downloaded 21.4 from official github release pages) , but that just got me stuck into download mode again, so any other way, is there a patcher for computer maybe?
I mean I can only install the latest version, even if I disable internet, I cannot select a specific version

refer to post #8

Thanks, after spending 3hours to get into magisk I decided to share my procedure (because I forget it a lot)
FIrst: make sure your phones last state was power off (you can eather power off from red button or from recovery)
Then turn phone on and start holding power button + bixby + volume up, and count to 10 then release (not 11, 10, if you count to 11 you will get to recovery)
To try out if you are in magisk mode (without ruining your saved wifi passwords), you can plug the phone into the charger, if it turn on normaly, you are in magisk, if it shows battery charging, then you are not in magisk mode)
OK, I tried updating Magisk with https://raw.githubusercontent.com/topjohnwu/magisk_files/b0694fad86/stable.json
but for some wierd reason, it doesn't want to update, its stuck on 20.2-1
OK,. I tried installing Magisk Manager v7.4.1 and when launching it, it said that it patched dtbo.img and it needs reboot, so after I reboot, I am stuck on download mode again
It sayd: DT table header check fail
well, lets install Android 10 a third time

wait, you're booting into recovery to get into Magisk? you can use Nemesis kernel to skip this.
https://forum.xda-developers.com/posts/81316371

alecxs said:
wait, you're booting into recovery to get into Magisk? you can use Nemesis kernel to skip this.
https://forum.xda-developers.com/posts/81316371
Click to expand...
Click to collapse
Yes I am, but its allright, I am used to this
one day I will have to compile my own kernel anyway (to add some drivers to the phone)
Now I have to figure out why Magisk 21.4 won't install
I tried patching my AP file with it, but no matter what I do, I cannot get into it for some reason? (even my trust and tried method does not get me into it, while it got me into 20 all the time)
Is this version broken?
Whats the latest magisk version that still supports Magisk Hide (usefull thing that always worked for me)

With Nemesis kernel no need for button dance, it boots straight into Magisk. Magisk Hide exist up to v23 but there is also unofficial Magisk v25
[Discussion] Magisk Delta - Another unofficial third-party Magisk fork
This is not an officially supported topjohnwu project. If you are looking for official Magisk source, please go to this page Introduction Custom Magisk fork by HuskyDG. Sync with official Magisk adding back MagiskHide...
forum.xda-developers.com

alecxs said:
only in case recovery and boot share the same partition, you will lose magisk after flashing TWRP (does not apply)
Click to expand...
Click to collapse
Magisk needs the ramdisk of the recovery/TWRP to patch it. If flashing a non-prepatched image you will lose root.

WoKoschekk said:
Magisk needs the ramdisk of the recovery/TWRP to patch it. If flashing a non-prepatched image you will lose root.
Click to expand...
Click to collapse
Yea, I discovered that already
Now I am trying to get it back and failing
UPDATE: after installing Magisk 23 (last version that has Magisk Hide), prepatching AP file, and flashing it like 10th time, I finaly have root
Do I dare to try TWRP again? (I guess I need to prepatch it with Magisk before I install it with odin? (but which file do I install there are 2 files provided (twrp-3.4.0-2-beyond2lte.img.tar or twrp-3.4.0-2-beyond2lte.img)?

patch the tar file