Related
First of all, I have very limited android experience but I need too root my phone for the functionality of an app that's critical to my business. Anyways, I'm running a Moto x4 with Pie. I already installed magisk 17.3 and magisk manager 6.0.1 using twrp recovery following a tutorial on youtube. When opening the magisk manager, it asked me to update to 7.1.1, which I did. Then it told me that I needed at least v18.0 magisk to be able to run the new magisk manager. Am I able to update magisk by flashing the new zip version in twrp, or is another method required since a prior version is already installed? Is this how I would install all future versions of magisk that comes out? Is there anything that I should know before flashing? I really don't want to get stuck in a boot loop or brick the phone.... Any guidance will be greatly appreciated.
organicloot said:
First of all, I have very limited android experience but I need too root my phone for the functionality of an app that's critical to my business. Anyways, I'm running a Moto x4 with Pie. I already installed magisk 17.3 and magisk manager 6.0.1 using twrp recovery following a tutorial on youtube. When opening the magisk manager, it asked me to update to 7.1.1, which I did. Then it told me that I needed at least v18.0 magisk to be able to run the new magisk manager. Am I able to update magisk by flashing the new zip version in twrp, or is another method required since a prior version is already installed? Is this how I would install all future versions of magisk that comes out? Is there anything that I should know before flashing? I really don't want to get stuck in a boot loop or brick the phone.... Any guidance will be greatly appreciated.
Click to expand...
Click to collapse
You can update it from Magisk and as well as from TWRP...
organicloot said:
First of all, I have very limited android experience but I need too root my phone for the functionality of an app that's critical to my business. Anyways, I'm running a Moto x4 with Pie. I already installed magisk 17.3 and magisk manager 6.0.1 using twrp recovery following a tutorial on youtube. When opening the magisk manager, it asked me to update to 7.1.1, which I did. Then it told me that I needed at least v18.0 magisk to be able to run the new magisk manager. Am I able to update magisk by flashing the new zip version in twrp, or is another method required since a prior version is already installed? Is this how I would install all future versions of magisk that comes out? Is there anything that I should know before flashing? I really don't want to get stuck in a boot loop or brick the phone.... Any guidance will be greatly appreciated.
Click to expand...
Click to collapse
First of all: backup! Then you can bootloop, brick (or not!) with no worries. Do it with twrp.
Download latest (beta) Magisk 19.0, flash it under twrp and be happy.
Just to add to the above....
Since you're already rooted you don't have to flash the zip in TWRP. Just go to the Magisk Manager Modules section, click the "+"-button and select the Magisk zip. When it's done, reboot and you're updated.
Shubham259 said:
You can update it from Magisk and as well as from TWRP...
Click to expand...
Click to collapse
I'm not able to open manager because it says I need at least v18.0. The app wont open.
Didgeridoohan said:
Just to add to the above....
Since you're already rooted you don't have to flash the zip in TWRP. Just go to the Magisk Manager Modules section, click the "+"-button and select the Magisk zip. When it's done, reboot and you're updated.
Click to expand...
Click to collapse
If it's in the manager app, I'm not sure how to do it because it says that I can't open it with anything <v18.0.
wilsonhlacerda said:
First of all: backup! Then you can bootloop, brick (or not!) with no worries. Do it with twrp.
Download latest (beta) Magisk 19.0, flash it under twrp and be happy.
Click to expand...
Click to collapse
Good news! The flash has been successful. And I learned about NANDroid backups. Super helpful! Thanks for the help!!
organicloot said:
If it's in the manager app, I'm not sure how to do it because it says that I can't open it with anything <v18.0.
Click to expand...
Click to collapse
You could of course uninstall the incompatible Manager and reinstall the one that works with your Magisk version.
But, that's now besides the point.
A day when you learn something new is a good day. :good:
If you want to learn more, here's a trivia [emoji14]
Also install "Magisk Manager for Recovery Mode (mm)" module. Not promoting it, but I myself feel it's a good module that you need to have before playing with Magisk Modules
It allows you to manage Magisk Modules from TWRP itself. So next time you run into a bootloop, you know what to do
Sent from my #FlagshipKiller3T using Tapatalk
Here you can find latest boot image for OnePlus7 Pro rooted with Magisk.
ROM:
OnePlus7ProOxygen_21.E.13_OTA_013_all_1907050211_b8852b6
https://1drv.ms/u/s!AvJju0GuwXqysxoo9LNYN3wla8KX
Why do need the boot.img for root ?
I never used it for root my device.
khalisz said:
Why do need the boot.img for root ?
I never used it for root my device.
Click to expand...
Click to collapse
How old is the last phone you had?
Since Jul 9, 2019.
Cozzeck said:
How old is the last phone you had?
Click to expand...
Click to collapse
Since Jul 9, 2019.
As of OOS 9.5.10 you can boot twrp by fastboot, then sideload twrp into both slots and finally flash magisk which patches the boot.img itself. Thus no need for patched boot.img anymore.
Does this work for the global version??
Patched boot.img is a silly way of rooting... If someone uses the wrong boot.img for their version it will fail to boot. Plus, booting TWRP and flashing the magisk zip is faster and more reliable
alexander1297 said:
Does this work for the global version??
Click to expand...
Click to collapse
The only difference between the global and the EU versions are supposed to be the LTE bands.
lichtblitz said:
As of OOS 9.5.10 you can boot twrp by fastboot, then sideload twrp into both slots and finally flash magisk which patches the boot.img itself. Thus no need for patched boot.img anymore.
Click to expand...
Click to collapse
Sorry for asking but I wanna root mine as soon as it comes. So if you install TWRP and flash with magisk the OTAs won't be broken?
Kengat said:
Sorry for asking but I wanna root mine as soon as it comes. So if you install TWRP and flash with magisk the OTAs won't be broken?
Click to expand...
Click to collapse
I get still offered OTAs by the system. However I prefer to use Oxygen Updater app from Play Store to download it and flash directly in TWRP.
lichtblitz said:
I get still offered OTAs by the system. However I prefer to use Oxygen Updater app from Play Store to download it and flash directly in TWRP.
Click to expand...
Click to collapse
Oh cool. So like "dirty flashing". Will magisk also get killed in the proccess? I'm not sure how A/B partitions work. Do you just install magisk from twrp or do you have to somehow install it on both partitions?
GM all
I seem to have lost my root after I did the update for 9.5.11 this morning
Here is what I did
I did as stated
Download update, Install, DO NOT REBOOT
Went to Magisk, unistalled all modules, then did OTA Install
Rebooted
Went to Magisk installed TWRP, but my phone froze at that point and the screen turned all white and just sat there
So I clicked on the power button and rebooted
Got back into my phone and checked to see if I was still rooted via root checker app and now it says I AM NOT ROOTED
What can I do to fix this I can launch Magisk, but now it says its is not installed on the screen, so I click install, download the ZIP option
It says Select Method, Download ZIP ONLY which I did or Select and Patch a File which I am not sure what file I need to use?
How can I get my root back on the phones
I am on NOW on 9.5.11 GM 1917
Thanks all
Thanks all
dallasnights said:
GM all
I seem to have lost my root after I did the update for 9.5.11 this morning
Here is what I did
I did as stated
Download update, Install, DO NOT REBOOT
Went to Magisk, unistalled all modules, then did OTA Install
Rebooted
Went to Magisk installed TWRP, but my phone froze at that point and the screen turned all white and just sat there
So I clicked on the power button and rebooted
Got back into my phone and checked to see if I was still rooted via root checker app and now it says I AM NOT ROOTED
What can I do to fix this I can launch Magisk, but now it says its is not installed on the screen, so I click install, download the ZIP option
It says Select Method, Download ZIP ONLY which I did or Select and Patch a File which I am not sure what file I need to use?
How can I get my root back on the phones
I am on NOW on 9.5.11 GM 1917
Thanks all
Thanks all
Click to expand...
Click to collapse
Follow the steps on TWRP and rooting on my guide. Look in the Guides & Discussion section of XDA
Flashing this on International breaks the WiFi. Does anyone have the international version?
Hideaki02 said:
Flashing this on International breaks the WiFi. Does anyone have the international version?
Click to expand...
Click to collapse
just flash boot twrp and flash magisk there..
Arden144 said:
Patched boot.img is a silly way of rooting... If someone uses the wrong boot.img for their version it will fail to boot. Plus, booting TWRP and flashing the magisk zip is faster and more reliable
Click to expand...
Click to collapse
If you don't need TWRP, first booting it and flashing the zip takes way longer than "fastboot flash boot boot.img".
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.
6- https://otafsg1.h2os.com/patch/amaz...22_OTA_061_all_1911200429_a3efe64891d2c42.zip
6T- https://otafsg1.h2os.com/patch/amaz..._41_OTA_061_all_1911200419_f2e12518eef8ae.zip
Found this today. File has a date of 11/20/19. I put in root and do manual update thru settings/update.
Magisk patched boot.img for the above 6T ROM.
https://drive.google.com/open?id=1DIoNvGG81IC6FdWiOgSRawG0-eAKUqBF
I had a boatload of bugs with the OB1. I have a 6T converted. Couldnt answer or make calls, reboots, freezes, crashes, WIFI didnt work, no pic messages, etc. I just tested for a second and I could make calls and wifi works. Do not try to install the Magisk patched boot.img. It will give the problems I had with OB1. I tried.
Def works a lot better. No freezes or reboots. My phone was useless on OB1 and I didn't want to flash back to 9 and lose my data. I had to forward my calls to another phone and wait for an updated ROM. But this def fixed a lot of the problems I encountered.
Edit: Still cant flashboot boot twrp.img.(3.3.1-1) Same error as before (failed remote unknown command)
Here's a bonus: Magisk patched boot.img for this OB2. Tested and verified root and no problems. Patched myself. For 6T. Extracted the boot.img from the payload.bin and patched.
https://drive.google.com/open?id=1DIoNvGG81IC6FdWiOgSRawG0-eAKUqBF
shatty said:
Here's a bonus: Magisk patched boot.img for this OB2. Tested and verified root and no problems. Patched myself. For 6T. Extracted the boot.img from the payload.bin and patched.
https://drive.google.com/open?id=1DIoNvGG81IC6FdWiOgSRawG0-eAKUqBF
Click to expand...
Click to collapse
@shatty, thanks.
What did you do to upgrade ? Actually i'm in OB1 Android 10 and Root with patched boot. So you upgrade with OTA or local upgrade ? You loose Root, and you put the new patched in adb? IS it ok?
Thanks
g4seb said:
@shatty, thanks.
What did you do to upgrade ? Actually i'm in OB1 Android 10 and Root with patched boot. So you upgrade with OTA or local upgrade ? You loose Root, and you put the new patched in adb? IS it ok?
Thanks
Click to expand...
Click to collapse
If you're rooted use the same method as always, use local update ( you don't have access to incremental update anyway as you are rooted) and BEFORE rebooting go in Magisk manager and install Magisk again but on other slot. You don't need to play with adb or fastboot.
@Striatum_bdr :
Thanks, so download the update, do local update and after juste install magisk on the other slot.
shatty said:
Here's a bonus: Magisk patched boot.img for this OB2. Tested and verified root and no problems. Patched myself. For 6T. Extracted the boot.img from the payload.bin and patched.
https://drive.google.com/open?id=1DIoNvGG81IC6FdWiOgSRawG0-eAKUqBF
Click to expand...
Click to collapse
wiped my device and flashed A10 beta 2, but every time flash this patched img file from fastboot my not booting. is there any other way to flash this patched img ?
ariyan rana said:
wiped my device and flashed A10 beta 2, but every time flash this patched img file from fastboot my not booting. is there any other way to flash this patched img ?
Click to expand...
Click to collapse
It worked on my 6t converted from tmo. Anyone else try this patched boot.img? Why wipe? Upgrade works fine.
So after hours of using the ob2 I didn't have any freezes or reboots. 1000000x better than my experience on ob1
shatty said:
So after hours of using the ob2 I didn't have any freezes or reboots. 1000000x better than my experience on ob1
Click to expand...
Click to collapse
Same here bud. Thanks.
shatty said:
Def works a lot better. No freezes or reboots. My phone was useless on OB1 and I didn't want to flash back to 9 and lose my data. I had to forward my calls to another phone and wait for an updated ROM. But this def fixed a lot of the problems I encountered.
Edit: Still cant flashboot boot twrp.img.(3.3.1-1) Same error as before (failed remote unknown command)
Click to expand...
Click to collapse
For now the right command is fastboot flash boot twrp mauronofrio.img version and then flash the installer zip through recovery.
It's a Oneplus's problem.
[EDIT 1]
After a few tries it worked! Now I try to install twrp (mauronofio version) and root the phone.
P.s. I'm trying to update (come form OB-1) I removed all magisk's modules, flashed magiks unistaller but the update with update manager keep failing...any idea?
[EDIT2]
ok, now I'm rooted and I've twrp but wifi doesn't work it's turn off automatically!
[EDIT3]
I've fix it! I've talked with mauronofrio and he said that it's due to flashing the twrp in the boot partition, so he suggested me two ways:
1. Root your device and flash the twrp installer using magisk manager
2. After the command fastboot flash boot twrp.img reboot in recovery, flash the stock boot.img flash twrp installer.zip and finally flash magisk.
I choosen the second way and it worked! Now I've OB_2, twrp, magisk and wifi connection.
Thx a lot for the links and Infos.
I have flashed it and it feels definitely smoother and I hope the random reboots are fixed.
From the changelog they should be.
Here is a small how to, how the upgrade from 10 to 10 ob2 went smooth. Also using this on every update.
1. Just use normal systen ota & let it install or Flash full OOS 10 zip via local update . (DO NOT REBOOT)
2a. Flash newest TWRP: fajita twrp 3.3.1-28.zip (or newer) by @mauronofrio via Magisk Manager (DO NOT REBOOT)
or 2b. go into magisk manager, search for a module called "twrp a/b retention script" Install it (DO NOT REBOOT)
3. Flash magisk to 2nd slot via MAgisk Manager (Magisk Manager → Tap on Install → Then select Install to Inactive Slot)
4. Reboot, wait and enjoy
pOpY
Gesendet von meinem ONEPLUS A6013 mit Tapatalk
Be very careful with the patched boot image. It hard-bricked my OP6T! Full details here:
https://forum.xda-developers.com/oneplus-6t/help/spent-6-hours-trying-to-rooted-android-t4012909
It looks like they took FactoryMode away using *#808# when using the dialer... anyone noticed?
Did they fix the extra blank space under navigation keyboard when type? Thanks
nicche said:
For now the right command is fastboot flash boot twrp mauronofrio.img version and then flash the installer zip through recovery.
It's a Oneplus's problem.
[EDIT 1]
After a few tries it worked! Now I try to install twrp (mauronofio version) and root the phone.
P.s. I'm trying to update (come form OB-1) I removed all magisk's modules, flashed magiks unistaller but the update with update manager keep failing...any idea?
[EDIT2]
ok, now I'm rooted and I've twrp but wifi doesn't work it's turn off automatically!
Click to expand...
Click to collapse
same thing happened to me. Have you found the fix sir?
OK just reflash the rom and dont forget to flash twrp and magisk again
anddd boom i got wifi working again
Anyone else having issues like the systems is getting slower animation is choppy and it just lag. I noticed it as well when playing games when that happens and it feels like i dont get as much framerates but a reboot of system fixed it for me. I thought by updating to ob2 it would fix this choppy feeling but its still there
I upgraded from OOS 10 Stable to OOS Beta 2 and all went on okay. No data lost.
Rickydwi said:
Anyone else having issues like the systems is getting slower animation is choppy and it just lag. I noticed it as well when playing games when that happens and it feels like i dont get as much framerates but a reboot of system fixed it for me. I thought by updating to ob2 it would fix this choppy feeling but its still there
Click to expand...
Click to collapse
I don't have this issue, but I do have the Bluetooth not working bug
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?