Related
https://drive.google.com/open?id=1QkXY-SdEbkRRj8DXJL2btxLKXkN7fH6g
File is currently uploading (I made this thread in case someone is digging around.
I couldn't install it from TWRP for some reason, kept getting error 1. I went to the stock updater, picked "local install" with this zip file on the root of my storage, then it updated.
Right after updating, but prior to rebooting, I flashed the TWRP Installer as a Magisk Module, rebooted into recovery, and flashed Magisk in there.
I know you can flash Magisk right after an OTA then flash TWRP after it reboots, but if you called my luck bad, you'd be giving me too much credit.
Regardless, file is on it's way to the drive and I hope it was worth the time!
ready for download!
Thanks, I was testing.
---------- Post added at 03:53 AM ---------- Previous post was at 03:16 AM ----------
สุรินทร์ พลโธา said:
Thanks, I was testing.
Click to expand...
Click to collapse
From testing hours than typical usage, better 0.2 overview and notifications improved. The battery cannot be dictated at this time.
I can't install from twrp, too. Same error.
=。= said:
I can't install from twrp, too. Same error.
Click to expand...
Click to collapse
True... It's not possible to install it via TWRP. Maybe it has something to do with Android sec. patch 2019.11.
rage302 said:
True... It's not possible to install it via TWRP. Maybe it has something to do with Android sec. patch 2019.11.
Click to expand...
Click to collapse
I installed through an app system. I tested it now, it's better to use a stable battery enough to say it's saving
aNGERY said:
https://drive.google.com/open?id=1QkXY-SdEbkRRj8DXJL2btxLKXkN7fH6g
File is currently uploading (I made this thread in case someone is digging around.
I couldn't install it from TWRP for some reason, kept getting error 1. I went to the stock updater, picked "local install" with this zip file on the root of my storage, then it updated.
Right after updating, but prior to rebooting, I flashed the TWRP Installer as a Magisk Module, rebooted into recovery, and flashed Magisk in there.
I know you can flash Magisk right after an OTA then flash TWRP after it reboots, but if you called my luck bad, you'd be giving me too much credit.
Regardless, file is on it's way to the drive and I hope it was worth the time!
ready for download!
Click to expand...
Click to collapse
After activating magisk modules my device is not booting. continuously booting to twrp and showing Rescueparty. i had tried magisk untinstaller but nothing happen.
rage302 said:
True... It's not possible to install it via TWRP. Maybe it has something to do with Android sec. patch 2019.11.
Click to expand...
Click to collapse
The only ones that can be installed from TWRP are the ones from Oneplusfirmware webpage. The downloaded ones from Updater app are marked as OTA , thus can only be installed with official updater app due to verification keys and all the stuff.
I'm wondering if there is any advantage to installing the update twice, so that it's on both slots?
This Walkthrough works with me perfectly
Updating from open beta 5 to open Beta 6 successfully
Rooted 20.1 & Twrp 72 no issues
Thanks a lot
1- uninstall Magisk modules.
2- install Oos stable/open beta with Settings > Local upgrade . DON'T reboot! (Must be newer than actual Oos you have installed allready on the phone)
3- open Magisk > downloads. Install TWRP A/B Retention Script. DON'T reboot.
4- go back in Magisk. Touch install. Choose (Install to inactive slot after' OTA)
5- reboot to system.
I was on 10.0.2 stable with Magisk Canary, twrp 3.3.1-72
null0seven said:
1- uninstall Magisk modules.
2- install Oos stable/open beta with Settings > Local upgrade . DON'T reboot! (Must be newer than actual Oos you have installed allready on the phone)
3- open Magisk > downloads. Install TWRP A/B Retention Script. DON'T reboot.
4- go back in Magisk. Touch install. Choose (Install to inactive slot after' OTA)
5- reboot to system.
I was on 10.0.2 stable with Magisk Canary, twrp 3.3.1-72
Click to expand...
Click to collapse
This works like a charm. Just did it to install it to the other slot being slot a. I'm ocd so I like both slots flashed. Easy solution to not being able to flash it in twrp. I'm kind of curious why it won't flash in twrp though. Maybe something to do with the security patch
I'm getting OnePlus cloud storage and OnePlus account login in my settings now. Never had that before. Anyone have this with beta 6?
Account login in settings:
I was able to flash in TWRP using version -74, downloading OB6 using oxygen updater
Gordietm said:
I'm getting OnePlus cloud storage and OnePlus account login in my settings now. Never had that before. Anyone have this with beta 6?
Click to expand...
Click to collapse
Not up at the top but yes can add in through settings.View attachment 4883201
Aporzio said:
Not up at the top but yes can add in through settings.
Click to expand...
Click to collapse
So why do I have in the main settings and others don't?
Gordietm said:
So why do I have in the main settings and others don't?
Click to expand...
Click to collapse
Not really sure
If anybody wants official download link for OB6 Global:
https://otafsg1.h2os.com/patch/amaz...13.W.17_OTA_017_all_1911152150_5b8908ba7b.zip
ZoiraP said:
The only ones that can be installed from TWRP are the ones from Oneplusfirmware webpage. The downloaded ones from Updater app are marked as OTA , thus can only be installed with official updater app due to verification keys and all the stuff.
Click to expand...
Click to collapse
this is the first one i couldn't flash in TWRP
Gordietm said:
So why do I have in the main settings and others don't?
Click to expand...
Click to collapse
I updated from twrp and got the same popup in my settings. Also, xXx has been affected, the debloat doesn't work properly on ob6. Hopefully things will get figured out soon.
OxygenOS 11 OP7TPro_ O2_BETA_02
Magisk v21.4 Manager 8.0.7 Patched Root Boot Image
https://www.androidfilehost.com/?fid=17248734326145729690
Stock Boot Image
https://www.androidfilehost.com/?fid=17248734326145729691
ADB Enabled Recovery Image
https://www.androidfilehost.com/?fid=17248734326145729692
Stock Recovery Image
https://www.androidfilehost.com/?fid=17248734326145729693
Combined Folder
https://www.androidfilehost.com/?w=files&flid=322771
OxygenOS 11 OP7TPro_ O2_BETA_01
Magisk v21.4 Manager 8.0.7 Patched Root Boot Image
https://www.androidfilehost.com/?fid=17248734326145719958
Stock Boot Image
https://www.androidfilehost.com/?fid=17248734326145719959
ADB Enabled Recovery Image
https://www.androidfilehost.com/?fid=17248734326145719960
Stock Recovery Image
https://www.androidfilehost.com/?fid=17248734326145719961
Full ZIP OxygenOS HD01BA 11 Open Beta
https://androidfilehost.com/?fid=17248734326145719998
Combined Folder
https://www.androidfilehost.com/?w=files&flid=322187
May need to install Magisk Manager manually
OxygenOS 10.0.4 EU was kindly picked up by @t-ryder Linked Below
https://forum.xda-developers.com/t/...-rom-oxygen-os-10-0-14.4236633/#post-84539771
OxygenOS 10.0.13 HD01BA Magisk/Stock Boot Images, ADB/Stock Recovery
Magisk v21.1 Manager 8.0.3 Patched Root Boot Image
https://www.androidfilehost.com/?fid=10763459528675591459
May need to install Magisk Manager manually
Full ZIP OxygenOS HD01BA 10.0.13
https://www.androidfilehost.com/?fid=10763459528675591484
Stock Boot Image
https://www.androidfilehost.com/?fid=10763459528675591455
ADB Enabled Recovery Image
https://www.androidfilehost.com/?fid=10763459528675591468
Stock Recovery Image
https://www.androidfilehost.com/?fid=10763459528675591462
Combined Folders
https://www.androidfilehost.com/?w=files&flid=320311
Usage (Unlocked Bootloader)
adb devices (give permission on device)
adb reboot fastboot
fastboot devices (to confirm that device is being detected)
fastboot flash boot path/to/patched_boot.img or fastboot flash recovery path/to/patched_recovery.img
fastboot reboothttps://www.androidfilehost.com/?fid=17248734326145729693
Thanks for posting these very useful resources... much appreciated...
How's the full zip upload coming along?
I thought I was clever and used the patched magisk image for 10.0.13 HD01BA on my firmware (updated OTA) version 10.0.13 HD01AA... all seems to be working fine barring one crucial function, that being wifi which is greyed out...
I'm assuming the broken wifi radio is symptomatic of the differing firmware versions?
sand_man said:
How's the full zip upload coming along?
I thought I was clever and used the patched magisk image for 10.0.13 HD01BA on my firmware (updated OTA) version 10.0.13 HD01AA... all seems to be working fine barring one crucial function, that being wifi which is greyed out...
I'm assuming the broken wifi radio is symptomatic of the differing firmware versions?
Click to expand...
Click to collapse
I'm grabbing what I think is the HD01AA Full ZIP from Oxygen Updater, I'll grab the stock boot and try making a magisk patched img for you as well, If they work I might add HD01AA to my supported devices manifest.
digidude512 said:
I'm grabbing what I think is the HD01AA Full ZIP from Oxygen Updater, I'll grab the stock boot and try making a magisk patched img for you as well, If they work I might add HD01AA to my supported devices manifest.
Click to expand...
Click to collapse
That's very kind of you sir! I've flashed BA and WiFi is working now. I think my device, as are many others, are impartial to firmware version. BA/AA/global/European, seems to all be the same barring 1 or 2 minor differences. Using the right patched magisk boot image is critical though.
Having said that I'm yet to flash boot the patched image so let's see what effect it has on WiFi (it any)...
Once again thank you for providing these resources. [emoji1303]
sand_man said:
That's very kind of you sir! I've flashed BA and WiFi is working now. I think my device, as are many others, are impartial to firmware version. BA/AA/global/European, seems to all be the same barring 1 or 2 minor differences. Using the right patched magisk boot image is critical though.
Having said that I'm yet to flash boot the patched image so let's see what effect it has on WiFi (it any)...
Once again thank you for providing these resources. [emoji1303]
Click to expand...
Click to collapse
Hope this helps
https://forum.xda-developers.com/7t-pro/how-to/oos-10-0-13-hd01aa-t4195159
@digidude512 Every Update needs a new Thread... interesting.
Stop this sh!t.
K3V1991 said:
@digidude512 Every Update needs a new Thread... interesting.
Stop this sh!t.
Click to expand...
Click to collapse
Your feedback has been taken.
Original Post has been updated for OxygenOS 11 Open Beta.
OOS 10.0.13 is still in original post but moved to spoiler.
Thanks for the update. Will probably stay on 10.0.13 for now though, as it is super stable and practically bug free.
Hello,
I just want to confirm is it really that simple to get Magisk & Root Access just by flashing patched boot image? Won't I need to full system & data wipe? I have stock OOS 10.0.13.
Athum said:
Hello,
I just want to confirm is it really that simple to get Magisk & Root Access just by flashing patched boot image? Won't I need to full system & data wipe? I have stock OOS 10.0.13.
Click to expand...
Click to collapse
yes
Thread updated with Open Beta 2
In the beta 2 A11 i have problem with magisk. Update and bootloop. All steps install correct and finnaly bootloop.
Any steps to fix it?
Magisk 21.4
chudy34 said:
In the beta 2 A11 i have problem with magisk. Update and bootloop. All steps install correct and finnaly bootloop.
Any steps to fix it?
Magisk 21.4
Click to expand...
Click to collapse
Just to confirm are you using a OnePlus 7T Pro EU Model.
HD01BA is for EU, I will be updating my second thread for 7T Global (HD01AA) and India models later.
digidude512 said:
Just to confirm are you using a OnePlus 7T Pro EU Model.
HD01BA is for EU, I will be updating my second thread for 7T Global (HD01AA) and India models later.
Click to expand...
Click to collapse
yes my model is EU.
I updated ota and install magisk unactive slot and the same boot to recovery and bootloop. Maybe problem is in magisk?
Flashing via OTA full ROM works great. After installation was completed I installed magisk to inactive slot and rebooted my device after this and my device is still rooted! Automatic brightness works much better with Beta 2
kaplatz said:
Flashing via OTA full ROM works great. After installation was completed I installed magisk to inactive slot and rebooted my device after this and my device is still rooted! Automatic brightness works much better with Beta 2
Click to expand...
Click to collapse
I get an error. And what version of magisk do you use? I used the latest 21407 and unfortunately bootloop after uploading.
I use 21.4 (21400) and it works like a charm.
Do we get patched boot image or diy instructions for Beta 3?
I see the release candidate for Android 11 has dropped! Anyone have access to the full download file? All I can find is the open_beta 4 which isn't going to work patched and flashed running the RC...
Have anyone can upload the last oos A11 adb recovery please
Phone Model no : Samsung Galaxy S6 / SM-G920F
Security patch date: 01.10.2017
Android version: 7.0
Root status: Yes
Hey guys,
I rooted my phone several weeks ago for the first time via odin and everything went fine. I installed TWRP and Magisk and everything worked out.
Today I was trying to update Magisk from v20.x to v21.x with the inapp option, but now im stuck in a bootloop to download mode, screen says "Downloading... do not turn off target".
Even if I turn the phone off with Power + Home + Vol Down its just restarting right away and getting stuck in the same screen again.
Im still able to enter TWRP Recovery, but I dont know what to do to end the download mode problem when trying to start the phone.
I actually dont know/understand much about that stuff, so I dont know which other info I need to provide.
Is there something I could do without going through the whole flash/root process again?
should i try to delete magisk and install it again? if yes, how do i do it?
Help would be appreciated.
n00btuber said:
Phone Model no : Samsung Galaxy S6 / SM-G920F
Security patch date: 01.10.2017
Android version: 7.0
Root status: Yes
Hey guys,
I rooted my phone several weeks ago for the first time via odin and everything went fine. I installed TWRP and Magisk and everything worked out.
Today I was trying to update Magisk from v20.x to v21.x with the inapp option, but now im stuck in a bootloop to download mode, screen says "Downloading... do not turn off target".
Even if I turn the phone off with Power + Home + Vol Down its just resarting right away and getting stuck in the same screen again.
Im still able to enter TWRP Recovery, but I dont know what to do to end the downloading problem when trying to start the phone.
I actually dont know/understand much about that stuff, so I dont know which other info I need to provide.
Is there something I could do without going through the whole flash/root process again?
should i try to delete magisk and install it again? if yes, how do i do it?
Help would be appreciated.
Click to expand...
Click to collapse
I don't know much about your device but if you can enter TWRP, it's not that bad. First what you can try is to download Magisk uninstaller and flash it in TWRP from USB. However, I don't know what can you do to update Magisk safely. Would be best if you can check your device forum or ask the question there
Lord Sithek said:
I don't know much about your device but if you can enter TWRP, it's not that bad. First what you can try is to download Magisk uninstaller and flash it in TWRP from USB. However, I don't know what can you do to update Magisk safely. Would be best if you can check your device forum or ask the question there
Click to expand...
Click to collapse
Looked like my device forum is pretty dead, which is why I asked the question here again. Thanks for the fast respone
Its probably not possible to just install a Magisk version again and overwrite the current one, probably need to uninstall first and then install it again?
There is a Magisk Module Uninstaller and a Magisk Uninstaller. Are those different things or just the same?
How to Uninstall Magisk Module Using TWRP Recovery | MagiskRoot
Uninstall Magisk Module using TWRP Recovery or Offline whenever you stuck into bootloop. Magisk Module Uninstaller and Magisk Manager for Recovery methods.
magiskroot.net
How to Uninstall Magisk From Android [2 Easiest Method]
Are you facing issues with Magisk? You can uninstall magisk from your phone with these simple and easy steps.
magiskmanager.com
Because the 2nd guide says in the end
Keep in Mind – Whenever you use TWRP as a method to uninstall Magisk, it is imperative to flash the Magisk Module Uninstaller Zip onto your device.
Does this mean I need to do the magisk module one first?
@n00btuber Do not trust those websites. They're in no way official and are just trying to get adc revenue from Magisk's popularity. If you're really unlucky they'll also provide you with malicious zips...
Only download stuff from John's GitHub:
https://github.com/topjohnwu/Magisk
If you need to uninstall Magisk use the uninstall zips from the above linked Github repo, and if you need to uninstall modules (but those will also be removed by the Magisk uninstaller) you can do that directly from TWRP:
https://www.didgeridoohan.com/magisk/Magisk#hn_Uninstalldeletedisable_modules_from_recovery
A lot of times you can just flash another Magisk version over your installed one, but there are times where you do need to uninstall first. Since you have TWRP it can't really hurt to just try flashing whatever Magisk zip you want and it it doesn't work you can just use the uninstaller first.
One other thing to try would be the Canary release, mainly to see if you're affected by any bugs that is present in the current stable release but has been fixed upstream. You'll find the Canary app in the same Github link above.
Didgeridoohan said:
@n00btuber Do not trust those websites. They're in no way official and are just trying to get adc revenue from Magisk's popularity. If you're really unlucky they'll also provide you with malicious zips...
Only download stuff from John's GitHub:
https://github.com/topjohnwu/Magisk
Click to expand...
Click to collapse
Ok.
Was trying to use the uninstaller from his GitHub.
Trying to flash it leads to
"Updater process ended with ERROR:1
Error installing Zip file .....
Updating partition details"
So what to do now?
Trying to just flash any Magisk version to overwrite the current one leads to the same result.
I think it says Unsupported/Unknown image format
Your TWRP might be bugged/incompatible. I'd reflash your stock boot image and then patch the file manually (you'll find the instructions for that on GitHub as well).
Didgeridoohan said:
Your TWRP might be bugged/incompatible.
Click to expand...
Click to collapse
But TWRP worked fine when installing magisk the first time, I even tried the same zip folder I used to install it back then, but it wont work anymore.
Didgeridoohan said:
I'd reflash your stock boot image and then patch the file manually (you'll find the instructions for that on GitHub as well).
Click to expand...
Click to collapse
However, whats my stock boot image and how to reflash it? Cant find a guide for that on GitHub.
Would a Factory Reset wipe all Magisk stuff and my TWRP Partition as well?
Does anyone know what is going on between Magisk and Google? It seems Google has removed Magisk Manager from the Play Store AGAIN! What's more, I downloaded and installed the apk but when I try to use it to install the latest Magisk the install fails. Tried installing the Magisk zip via TWRP, and while it doesn't show any errors, I still don't have root.
Ok I really need some more help @Didgeridoohan
Meanwhile I tried to reinstall TWRP from within TWRP. There was no error so I think it should have worked, but didnt solve the problem.
As soon as I try to boot the system it directly boots download mode and gets stuck in it. The volume buttons wont work or do anything as they are supposed in download mode.
Im still able to get into TWRP, but I still dont know what to do to stop this crashed download mode that starts over and over again.
When trying to flash the magisk uninstall it states "cannot access /data", when trying to flash a magisk installer it states "unsupported/unknown image format"
I dont care about Magisk right now though, I can root and install magisk again as soon as im able to clear the download mode problem. I was just trying this because trying to update magisk from within magisk manager has caused this download mode problem to appear.
Just tell me please how to fix that or how to factory reset my phone so it is able to boot regular again.
Thank you
n00btuber said:
Ok I really need some more help @Didgeridoohan
Meanwhile I tried to reinstall TWRP from within TWRP. There was no error so I think it should have worked, but didnt solve the problem.
As soon as I try to boot the system it directly boots download mode and gets stuck in it. The volume buttons wont work or do anything as they are supposed in download mode.
Im still able to get into TWRP, but I still dont know what to do to stop this crashed download mode that starts over and over again.
When trying to flash the magisk uninstall it states "cannot access /data", when trying to flash a magisk installer it states "unsupported/unknown image format"
I dont care about Magisk right now though, I can root and install magisk again as soon as im able to clear the download mode problem. I was just trying this because trying to update magisk from within magisk manager has caused this download mode problem to appear.
Just tell me please how to fix that or how to factory reset my phone so it is able to boot regular again.
Thank you
Click to expand...
Click to collapse
Sounds to me like you need to reflash your ROM, not TWRP. According to your OP, you're running Android 7, but it doesn't say if it is stock or a custom ROM.. If it is stock, then use Frija.exe to download the ROM and then flash th AP, BL and HOME_CSC md5 files with Odin. If it is a custom ROM, use TWRP to flash the ROM and gapps. DO NOT try to flash Magisk. Right now there seems to be a problem with Google disabling Magisk. Wait till it is resolved before attempting to get root.
@n00btuber Dirty flashing your ROM is most likely the way to go, just like described above.
But @lewmur, what do you mean by "Google disabling Magisk"? If you're talking about SafetyNet there are ways around that (and it doesn't affect root)...
Didgeridoohan said:
@n00btuber Dirty flashing your ROM is most likely the way to go, just like described above.
But @lewmur, what do you mean by "Google disabling Magisk"? If you're talking about SafetyNet there are ways around that (and it doesn't affect root)...
Click to expand...
Click to collapse
I not talking about safety net. Look in Play Store for Magisk Manager. It is no longer there. And even if you download and install the apk, it won't install Magisk. Flashing Magisk from TWRP doesn't give root privileges. This just happened yesterday.
lewmur said:
I not talking about safety net. Look in Play Store for Magisk Manager. It is no longer there. And even if you download and install the apk, it won't install Magisk. Flashing Magisk from TWRP doesn't give root privileges. This just happened yesterday.
Click to expand...
Click to collapse
The Magisk Manager hasn't been on the Play Store for years... Edit: reference - https://forum.xda-developers.com/t/magisk-the-magic-mask-for-android.3473445/post-72508849
Nothing of what you describe has anything to do with Google "disabling Magisk".
Didgeridoohan said:
The Magisk Manager hasn't been on the Play Store for years... Edit: reference - https://forum.xda-developers.com/t/magisk-the-magic-mask-for-android.3473445/post-72508849
Nothing of what you describe has anything to do with Google "disabling Magisk".
Click to expand...
Click to collapse
That 's my mistake. Play Store would put up a lot of "Magisk Manager" stuff, but I never really tried any of it because flashing Magisk would give me the Manager. But even that "stuff" no longer shows up.
Butt Magisk Manager still won't install Magisk. It will download the zip file, but when it attemps to install it, it get an error saying Unsupported/Unknown image format. If I flash it from TWRP, and then open Magisk Manager, it still says N/A under Installed for Magisk.
lewmur said:
Then why won't Magisk Manager install Magisk. It will download the zip file, but when it attemps to install it, it get an error saying Unsupported/Unknown image format. If I flash it from TWRP, and then open Magisk Manager, it still says N/A under Installed for Magisk.
Click to expand...
Click to collapse
That will be an incompatibility between Magisk and your device and has nothing to do with Google (blame your OEM for doing weird stuff instead).
Thanks for the help guys, had to flash the ROM, now its working again.
So i was minding my own business then i notice "Magisk Manager" have red dot notification on it's icon upon opening there's update for "Magisk Manager" app and "Magisk" itself... so i decided to first Install the "Magisk Manager" update and it went real smooth
but when i try to update Magisk itsaid "Magisk Manager is Dead. Love live the Magisk app" then it ask me for Method
"Select and Patch file" or "Direct Install" now at this point idk what to do. I have at least done 3x Magisk update installation already it never ask me this option also when i try download root checker on playstore itsaid im rooted i just want to update Magisk should i patch my stock boot.img again or what??
For me this has been the case all this time for Magisk updates - I get that choice, and I choose 'direct install'. This time also I chose the same - 'direct install'. It got installed and prompted me to reboot.
scarmage said:
For me this has been the case all this time for Magisk updates - I get that choice, and I choose 'direct install'. This time also I chose the same - 'direct install'. It got installed and prompted me to reboot.
Click to expand...
Click to collapse
clicking Direct Install doesn't do anything
This is what my Magisk Manager look like before i update it to v22.0
https://ibb.co/gvPzDs7
Now after i update it to Magisk Manager V22.0 i can't update Magisk
https://ibb.co/HXLCvLS
You can try going to the Magisk GitHub and download the app and install it through file manager and try updating again. I did that accidentally and had no issues installing.
dl200010 said:
You can try going to the Magisk GitHub and download the app and install it through file manager and try updating again. I did that accidentally and had no issues installing.
Click to expand...
Click to collapse
I have the app already but after they decided to merge Magisk Manager and Magisk in just one apps i can't update Magisk anymore also i have stock boot.img of my device that i have previously patched via Magisk so it's just unusual for Magisk Manager to ask me again ...
ineedroot69 said:
I have the app already but after they decided to merge Magisk Manager and Magisk in just one apps i can't update Magisk anymore also i have stock boot.img of my device that i have previously patched via Magisk so it's just unusual for Magisk Manager to ask me again ...
Click to expand...
Click to collapse
I downloaded the apk from GitHub and installed it over the updated one. I was able to do a direct update. I was just suggesting it. Couldn't hurt to try it.
dl200010 said:
I downloaded the apk from GitHub and installed it over the updated one. I was able to do a direct update. I was just suggesting it. Couldn't hurt to try it.
Click to expand...
Click to collapse
Same here. Worked on Xiaomi Note 10 Pro (Tucana) with Android 10.
Did not work on Xiaomi Mi 10 Lite 5G (Monet) with Android 11. (The phone booted into fastboot-mode, so I had to extract the original boot.img from an original ROM and flashed it via fastboot-command to get the phone back booting to system).
PrussianWolf said:
Same here. Worked on Xiaomi Note 10 Pro (Tucana) with Android 10.
Did not work on Xiaomi Mi 10 Lite 5G (Monet) with Android 11. (The phone booted into fastboot-mode, so I had to extract the original boot.img from an original ROM and flashed it via fastboot-command to get the phone back booting to system).
Click to expand...
Click to collapse
Can you tell more? How did you extract the boot.img? Did you get it from the newest Android full OTA? DId it just straight up work after flashing the new boot.img? I'm asumming it was an unpatched one, right?
PrussianWolf said:
Same here. Worked on Xiaomi Note 10 Pro (Tucana) with Android 10.
Did not work on Xiaomi Mi 10 Lite 5G (Monet) with Android 11. (The phone booted into fastboot-mode, so I had to extract the original boot.img from an original ROM and flashed it via fastboot-command to get the phone back booting to system).
Click to expand...
Click to collapse
How do I flash a ROM from bootloader? I am on Xiaomi Redmi Note 4 (mido) and have the same issue. Device won't boot into anything except fastboot. I tried flashing recovery using fastboot flash recovery <reccovery>.img but it got stuck in bootloop again.
ineedroot69 said:
This is what my Magisk Manager look like before i update it to v22.0
https://ibb.co/gvPzDs7
Now after i update it to Magisk Manager V22.0 i can't update Magisk
https://ibb.co/HXLCvLS
Click to expand...
Click to collapse
Exactly the same experience as OP here.
I am at exactly this stage as well..oneplus 6T; rooted; stock image.
Not sure what to do next?
Thanks in anticipation.
~S.O
where is the "Download zip only" option ?
VangelisGi said:
where is the "Download zip only" option ?
Click to expand...
Click to collapse
There isn't one, because there is no separate zip anymore:
https://topjohnwu.github.io/Magisk/releases/22000.html
Why?
I'm so confused.
I'm on Lineageos 17 on Oneplus 6
I used to install magisk with the zip and it went smoothly now I don't have the option anymore..
How can you do when you use OTA update?
Cygnust said:
Why?
I'm so confused.
I'm on Lineageos 17 on Oneplus 6
I used to install magisk with the zip and it went smoothly now I don't have the option anymore..
How can you do when you use OTA update?
Click to expand...
Click to collapse
It's all explained in the link posted right above your post...
Spoiler: rename the .apk to .zip.
Didgeridoohan said:
It's all explained in the link posted right above your post...
Spoiler: rename the .apk to .zip.
Click to expand...
Click to collapse
Sorry, I skipped that part and when directly to the one saying you had to patch BOOT.IMG..
Many thanks
Didgeridoohan;
I understand that the 'Manager' now has become the 'App'. I also understand to just rename the '.apk' file to '.zip' to flash from an OTA update event. I also understand that the '.apk' now with this latest release has everything you need to install Magisk.
I have had Magisk already installed like this: https://ibb.co/gvPzDs7
So, after I updated, can I ask what do I do about the problem of 'update' indicating via the Magisk Home page on the App?
I mean now I have this: https://ibb.co/HXLCvLS
Just don't worry about it?
Thank-you for your help.
sprocketoctopus said:
Didgeridoohan;
I understand that the 'Manager' now has become the 'App'. I also understand to just rename the '.apk' file to '.zip' to flash from an OTA update event. I also understand that the '.apk' now with this latest release has everything you need to install Magisk.
I have had Magisk already installed like this: https://ibb.co/gvPzDs7
So, after I updated, can I ask what do I do about the problem of 'update' indicating via the Magisk Home page on the App?
I mean now I have this: https://ibb.co/HXLCvLS
Just don't worry about it?
Thank-you for your help.
Click to expand...
Click to collapse
Magisk still consists of two parts, Magisk app and Magisk internals, they're now just distributed together.
What your screenshot shows is that you've now updated the app, but not yet the internals...
Do not update simply as the update is Device bricking.
Magisk 22.0 update killed phone will only boot into fastboot
Have never had an issue went to update to latest Magisk app, followed directions and restored it first, everything seemed fine, then went to flash Magisk itself from the app (Direct install) like always, didn't seem to do anything, checked the...
forum.xda-developers.com
I updated my magisk to version 22, and it looks ok, except for the bottom menu that disappeared, does anyone know where it went or is it a bug?
Prerequisites:
Bootloader unlocked
TWRP
Bootloader unlock guide : https://forum.xda-developers.com/t/guide-bootloader-unlock-on-rui-2-0-based-on-android-11-r.4286451/
TWRP : https://forum.xda-developers.com/t/twrp-recovery-unofficial-for-realme-x7-max-rmx3031.4336503/
Download this version of Magisk Manager "Magisk Alpha (706a4922-alpha)" from file attached below because stable version is causing bootloop, for now
Steps :
To Root Your Phone Install above mentioned version of magisk manager
Pull your boot.img from recovery
adb pull /dev/block/by-name/boot boot.img
check boot image in directory you extracted your adb zip
Patch your pulled boot.img from apk given below
Flash it via Twrp in Boot Partition
Now u successfully rooted your device
Troubleshooting:
One issue I personally faced was driver problem (Fastboot Device Not detecting) which I was easily able to fix with the help of this video : https://cutt.ly/wEEit33
use this only if you are also facing this issue
Sources : here
Sir can i flash the magisk alpha from twrp by converting the apk into .zip then flash it directly from twrp.??
Aditya8520 said:
Sir can i flash the magisk alpha from twrp by converting the apk into .zip then flash it directly from twrp.??
Click to expand...
Click to collapse
NO, that's not how it works
Always getting bootloop. Tried multiple magisk versions, multiple ways to extract boot.img, but always getting only to white "realme" logo. Im on A18 btw
borkakoz said:
Always getting bootloop. Tried multiple magisk versions, multiple ways to extract boot.img, but always getting only to white "realme" logo. Im on A18 btw
Click to expand...
Click to collapse
Read carefully, I have metioned in post "Download this version of Magisk Manager "Magisk Alpha (706a4922-alpha)" from file attached below because stable version is causing bootloop, for now"
Harsh raj sah said:
Read carefully, I have metioned in post "Download this version of Magisk Manager "Magisk Alpha (706a4922-alpha)" from file attached below because stable version is causing bootloop, for now"
Click to expand...
Click to collapse
As I mentioned in my reply, I tried multiple versions of Magisk, and version from post too. Is there any other way to get that patched boot img?
I also noticed that flashing process is almost instant. It takes only like a split second. Can it be the issue?
it's not stable at all
are there any other options?
i had arranged all the things fix all the issue and make an article of root realme x7 max. all the command is provided here even downloads file