Hello, I am currently on US998. I followed a rooting guide here couple months ago, and my phone is on US99820h software version with Android 8.0.0. I keep getting notifications about updating and upgrading Magisk through the Magisk Manager. I come here asking if it is safe to do so since I recall dealing with bootloop issues when I updated Magisk (though not through the manager). Should I just ignore these update notifications?
Magisk Manager: 7.3.2 -> 7.3.5
Magisk: 19.3 -> 20.0
techsam2k8 said:
Hello, I am currently on US998. I followed a rooting guide here couple months ago, and my phone is on US99820h software version with Android 8.0.0. I keep getting notifications about updating and upgrading Magisk through the Magisk Manager. I come here asking if it is safe to do so since I recall dealing with bootloop issues when I updated Magisk (though not through the manager). Should I just ignore these update notifications?
Magisk Manager: 7.3.2 -> 7.3.5
Magisk: 19.3 -> 20.0
Click to expand...
Click to collapse
Yes, since you have flashed to most recent USS98 Oreo 20h, you can now update Magisk.
Safest way is to go into TWRP and run the Magisk uninstaller, then flash latest version in TWRP.
Then boot into Oreo and update Manager.
However if you ever have to reflash Oreo TWRP-flashable zip, you'll need to revert to Magisk 18.x temporarily to do that.
ChazzMatt said:
Yes, since you have flashed to most recent USS98 Oreo 20h, you can now update Magisk.
Safest way is to go into TWRP and run the Magisk uninstaller, then flash latest version in TWRP.
Then boot into Oreo and update Manager.
Click to expand...
Click to collapse
Just curious, why is it safer to install Magisk from TWRP instead of from the manager? Also, does it matter if I update Manager first then update Magisk since the update notification for the manager was there for much longer?
techsam2k8 said:
Just curious, why is it safer to install Magisk from TWRP instead of from the manager? Also, does it matter if I update Manager first then update Magisk since the update notification for the manager was there for much longer?
Click to expand...
Click to collapse
Maybe it's fixed now, but going from 18.x to 19.x some people had problems. What worked was using the official Magisk uninstaller zip, then install the new version.
Just to stick in my 2 cents, I always update magisk through twrp too. But I don't uninstall the old version first. I just flash the new version wipe caches and reboot. I've never run into problems.
Sent from my LG-US998 using Tapatalk
ChazzMatt said:
Maybe it's fixed now, but going from 18.x to 19.x some people had problems. What worked was using the official Magisk uninstaller zip, then install the new version.
Click to expand...
Click to collapse
That's been fixed.
Sent from my LG-H932 using XDA Labs
Related
It seems it is impossible to get root with magisk on latest Oreo stock. Maybe someone found solution?
I asked and I answer =)
To get the root it is required to
- install latest TWRP (current version twrp-3.2.1-0)
- reboot to TWRP
- install 16.2 or higher magisk, link for 16.2
- install f2fs bug workaround
- reboot system
- install magisk Manager
- enjoy your root =)
dolar4ik said:
I asked and I answer =)
To get the root it is required to
- install latest TWRP (current version twrp-3.2.1-0)
- reboot to TWRP
- install 16.2 or higher magisk, link for 16.2
- install f2fs bug workaround
- reboot system
- install magisk Manager
- enjoy your root =)
Click to expand...
Click to collapse
its not work for me:crying:
Try to follow this guide then: https://forum.xda-developers.com/moto-z-play/how-to/guide-how-to-magisk-root-xposed-oreo-8-t3743273
But use latest magisk beta instead of suggested 15.3.
And keep in mind that it is possible to easily restore working state with magisk uninstaller.
Do you have any errors during magisk or workaround installation in twrp console?
dolar4ik said:
Try to follow this guide then: https://forum.xda-developers.com/moto-z-play/how-to/guide-how-to-magisk-root-xposed-oreo-8-t3743273
But use latest magisk beta instead of suggested 15.3.
And keep in mind that it is possible to easily restore working state with magisk uninstaller.
Do you have any errors during magisk or workaround installation in twrp console?
Click to expand...
Click to collapse
now its working for me.:highfive::highfive:
dolar4ik said:
I asked and I answer =)
To get the root it is required to
- install latest TWRP (current version twrp-3.2.1-0)
- reboot to TWRP
- install 16.2 or higher magisk, link for 16.2
- install f2fs bug workaround
- reboot system
- install magisk Manager
- enjoy your root =)
Click to expand...
Click to collapse
Hi, does not work for me, stuck at bootloader logo, tried Magisk, followed the steps many times but nothing, can you help please ?
evnimaster said:
Hi, does not work for me, stuck at bootloader logo, tried Magisk, followed the steps many times but nothing, can you help please ?
Click to expand...
Click to collapse
follow this: https://forum.xda-developers.com/mot...reo-8-t3743273
Code:
echo keepverity=true>>/data/.magisk
echo keepforceencrypt=true>>/data/.magisk
Is there a way to remove encryption already?
Remove root?
Is it possible to remove root and the TWRP without hard reset? Does anyone already have the original recovery of Oreo?
DavidKalil10 said:
Is it possible to remove root and the TWRP without hard reset? Does anyone already have the original recovery of Oreo?
Click to expand...
Click to collapse
There is magisk uninstaller provided in official thread.
To remove twrp you just need to flush original recovery via fastboot
Hello guys, can I have some advice on whether I should install this latest Oreo update on my moto z, how is the battery doing on this update? And overall experience?
@dolar4ik
i reflash the stock oreo ROM,then flash TWRP,flash magisk,flash f2fs bug workaround, stuck at bootloader logo,how can i do it??
Flash the Magisk uninstaller, reboot to recovery (you have this option in TWRP) and flash again only the Magisk 16.3 (without the f2fs bug workaround). This worked for me two days ago.
Today I updated to the latest Magisk 16.4 without any problems.
lesbianu said:
Flash the Magisk uninstaller, reboot to recovery (you have this option in TWRP) and flash again only the Magisk 16.3 (without the f2fs bug workaround). This worked for me two days ago.
Today I updated to the latest Magisk 16.4 without any problems.
Click to expand...
Click to collapse
still not work for me.:crying::crying:
---------- Post added at 03:12 AM ---------- Previous post was at 02:58 AM ----------
This is strange. It works on Oreo OTA but it does not work in full flash Oreo ROM.
have anyone help me??
rakee said:
It works on Oreo OTA but it does not work in full flash Oreo ROM.
Click to expand...
Click to collapse
This is right.
I re-flashed my phone using the OPL27.76-51 firmware. Now, no way to install Magisk (old, new, any version).
The solution, I restored a TWRP backup made at the first bootloader unlock (when the ROM was updated only using OTAs, not flashed). Immediately I was able to install Magisk 16.4 - without any F2FS workaround.
HERE is my TWRP backup containing the partitions: Boot, Data & System. Hope it helps!
rakee said:
@dolar4ik
i reflash the stock oreo ROM,then flash TWRP,flash magisk,flash f2fs bug workaround, stuck at bootloader logo,how can i do it??
Click to expand...
Click to collapse
Uninstall magisk with it's own uninstaller.
I installed Magisk on the full Oreo release and everything is working.
I did make a "less bloat, less bs" zip version but I doubt it would make a change.
If you guys want, I can upload it when I get home.
The Marionette said:
I installed Magisk on the full Oreo release and everything is working.
I did make a "less bloat, less bs" zip version but I doubt it would make a change.
If you guys want, I can upload it when I get home.
Click to expand...
Click to collapse
Could you provide your twrp ZIP Version? That would be great.
lesbianu said:
This is right.
I re-flashed my phone using the OPL27.76-51 firmware. Now, no way to install Magisk (old, new, any version).
The solution, I restored a TWRP backup made at the first bootloader unlock (when the ROM was updated only using OTAs, not flashed). Immediately I was able to install Magisk 16.4 - without any F2FS workaround.
HERE is my TWRP backup containing the partitions: Boot, Data & System. Hope it helps!
Click to expand...
Click to collapse
Just got myself a hand me down Moto z.
My friend who gave it to me hasn't touch the phone for a year.
So i started with 6.0 and after multiple updates, now i am on Oreo.
Since i have done ota from Marshmallow, would this method work?
Bootloader was never unlocked.
thanks for any input
Hi guys,
Just got notified that new magisk is available for install. Is it stable and working with the v30 (running Oreo v21a)?
I had a magisk update soft brick some phones before that's why I'm asking...
Cheers
clouds5 said:
Hi guys,
Just got notified that new magisk is available for install. Is it stable and working with the v30 (running Oreo v21a)?
I had a magisk update soft brick some phones before that's why I'm asking...
Cheers
Click to expand...
Click to collapse
See the last few pages of WTF thread. 17.0 boot loops. 17.1 fixes boot loops, but best to uninstall 16 Magisk in TWRP before installing 17.1. Run the uninstaller.
However, there's problems with Magisk Hide on 17.x right now. It crashes for a lot of people.
Thx, I'll stick with 16.0 for the moment. No issues with it and I'm not missing anything so...
17.0 made my stock rom bootloop.
17.1 works fine for me.
It probably makes no difference how you install it, but I used the patch boot image option then flashed the patched boot.img using fastboot.
use dd to get an image of your currently working boot partition
patch that boot.img with magisk manager to 17.1 and copy to PC
use fastboot to flash that patched_boot.img and then reboot (or fastboot boot TWRP.img then reboot from there to be extra safe)
I'm on 21B and that works for me. I have not tried a different way so I can't confirm/deny any other method yet
Sent from my LGE V30 using XDA Labs
21a here i just clean flashed with 17.1 ._.
I'm getting issues with 17.1 and magisk hide.. Is there any fixes? Thanks in advance
So just want to make sure.. can I run the magisk Uninstaller by flashing the zip in TWRP and the flashing 17.1 in TWRP to reinstall magisk?
Hi All,
Just to let people know. I believe the issue is with the Magisk Manager App. I'm currently still using Magisk 17.1. However, I've uninstalled the Magisk Manager and re-installed Magisk Manager 5.8.3 instead. I can now use Magisk Hide without crashing. Maybe others can give this a try as well.
silver311 said:
Hi All,
Just to let people know. I believe the issue is with the Magisk Manager App. I'm currently still using Magisk 17.1. However, I've uninstalled the Magisk Manager and re-installed Magisk Manager 5.8.3 instead. I can now use Magisk Hide without crashing. Maybe others can give this a try as well.
Click to expand...
Click to collapse
This worked for me as well.
1. Uninstall Magisk 16 in TWRP using the latest MagiskUninstaller.
2. Flash Magisk 17.1
3. Boot up and un-install MagiskManager 5.9.1
4. Install MagiskManager 5.8.3.
As expected, the SafetyNet check doesn't work but some of the modules I use are being updated to the new template which prevents them from running on Magisk 16.0.
Anyone know how to get rid of the pop-up to update MagiskManager every time the app is opened?
The lastest pop-up on MagiskManager shows the 6.0 version and the changelog shows that it is designed for Magisk 17.2
Anyone has tried with these new modules?
trekminal said:
The lastest pop-up on MagiskManager shows the 6.0 version and the changelog shows that it is designed for Magisk 17.2
Anyone has tried with these new modules?
Click to expand...
Click to collapse
Yes, discussed over in WTF thread.
https://forum.xda-developers.com/showpost.php?p=77687418&postcount=1798
Thanks.
I updated to MagiskManager 6.0 but it shows me the option to update to Magisk 17.1, not the 17.2
I will wait some days until 17.2 will be available through the main app.
Any else have magisk manager crashing when using selecting #magisk hide from the magisk manager menu?
running 20d us998
with magisk 17.1
magisk manager 6 (although 5.9.1 did the same thing)
and root checker remover
someone on the magisk support thread recommended deleting the hidelist file which didn't really do anything. Problem is still occuring even with the new hidelist.
So the October patch just came out, but my phone's rooted (magisk, no twrp), so I can't install the update. If anyone could provide a guide on how to update and re-root the phone again, that would be very much appreciated. Thank you.
bibekmufc said:
So the October patch just came out, but my phone's rooted (magisk, no twrp), so I can't install the update. If anyone could provide a guide on how to update and re-root the phone again, that would be very much appreciated. Thank you.
Click to expand...
Click to collapse
No need to unroot. If u can get the boot.img u can use magisk to root it and instal.
i use magisk tutorial for updating. and there is a magisk modul for reinstalling twrp. you have to use it before installing magisk on inactive slot.
i suggest you to wait a few days before updating. i update to October and install magisk and twrp but wifi and hotspot are broken. and twrp won't work correctly. not shore if it's because twrp or October ota
It was my fault that break wifi and hotspot. magisk tutorial should do the work. just backup before doing anything
ghasemi.hussein said:
It was my fault that break wifi and hotspot. magisk tutorial should do the work. just backup before doing anything
Click to expand...
Click to collapse
I decided to completely reset my phone and it's now better than ever
From twrp thread
If you want you can also update a stock rom from phone settings with local upgrade:
- Update the Rom WITHOUT REBOOT;
- Open Magisk Manager;
- Menu/modules/+ button/select the twrp installer.zip and flash it;
- Always in Magisk Manager, click on Install/Install/Direct Install;
- Again in Magisk Manager, click on Install/Install/Inactive Slot;
- Reboot.
kimikim0 said:
From twrp thread
If you want you can also update a stock rom from phone settings with local upgrade:
- Update the Rom WITHOUT REBOOT;
- Open Magisk Manager;
- Menu/modules/+ button/select the twrp installer.zip and flash it;
- Always in Magisk Manager, click on Install/Install/Direct Install;
- Again in Magisk Manager, click on Install/Install/Inactive Slot;
- Reboot.
Click to expand...
Click to collapse
This steps work for update rom with magisk and root installed? Need help for install october update (no twrp, just magisk and root)
Enviado desde mi Mi A3 mediante Tapatalk
I wanted to update my one plus 7t pro but I don't know why even if I used the incremental update I don't have anymore the root. Now I have the following build: Oxygen OS 10.0.8.HD01BA (Europe).
The problem is that I didn't find any patched bootable .img for the version 10.0.8HD01BA.
Is it possible to root my phone with version 10.0.8 or I need to go back to version 10.0.7, root it and then again made the incremental update?.
Thank you in advance.
DiOriginal said:
I wanted to update my one plus 7t pro but I don't know why even if I used the incremental update I don't have anymore the root. Now I have the following build: Oxygen OS 10.0.8.HD01BA (Europe).
The problem is that I didn't find any patched bootable .img for the version 10.0.8HD01BA.
Is it possible to root my phone with version 10.0.8 or I need to go back to version 10.0.7, root it and then again made the incremental update?.
Thank you in advance.
Click to expand...
Click to collapse
You don't need to revert 10.0.7 to root, you can use this guide to root 10.0.8 -> https://forum.xda-developers.com/7t-pro/how-to/10-0-3-patched-boot-image-oneplus-7t-pro-t3986351
DiOriginal said:
I wanted to update my one plus 7t pro but I don't know why even if I used the incremental update I don't have anymore the root. Now I have the following build: Oxygen OS 10.0.8.HD01BA (Europe).
The problem is that I didn't find any patched bootable .img for the version 10.0.8HD01BA.
Is it possible to root my phone with version 10.0.8 or I need to go back to version 10.0.7, root it and then again made the incremental update?.
Thank you in advance.
Click to expand...
Click to collapse
Also, after downloading the update, don't press reboot.
Go to magisk manager and select install and pick install to inactive slot wait till it's done then reboot.
Always remember to disable modules that could make your device boot loop and restart your device before doing the update process
If you do it this way you don't have to keep making or asking others for patched images and have to use your computer
DiOriginal said:
I wanted to update my one plus 7t pro but I don't know why even if I used the incremental update I don't have anymore the root. Now I have the following build: Oxygen OS 10.0.8.HD01BA (Europe).
The problem is that I didn't find any patched bootable .img for the version 10.0.8HD01BA.
Is it possible to root my phone with version 10.0.8 or I need to go back to version 10.0.7, root it and then again made the incremental update?.
Thank you in advance.
Click to expand...
Click to collapse
Hi I have version 10.0.8 EU and used this one https://forum.xda-developers.com/7t-pro/how-to/magisk-auto-install-tool-magisk-t4001471
worked for me
man i swear i tried somthing and it worked and i pass SafetyNet right now. i'am not a professional and i dont know what exactly i did that fixed the problem. but i will tell you what i did.
- i had some problems with my phone so i did MSM-flashtool it to get it back to clean
- then i installed latest magisk application 7.5.1 from github.
-patched my boot image and flashed it
-i got safetynet check failed.
-i then removed magisk by installing the stock boot image again.
-then i downloaded an older version of magisk which is 7.4.0.
-flashed the same patched boot image again.
WALLAH! i passed safteynet and magisk hide works with bank and google pay apps agian ! <3
-then i updated magisk from the app both manager and magisk zip
-rebooted
-still my safetynet passes! try it and tell me guys!
Hi there,
i'm rooted and i installed the latest OTA (oxygen os 10.3.7.hd01AA - india rom maybe because i used a patched boot.img in the first time months ago) right now and just like all the times before i made the usual steps:
1) Restored Original Image via Magisk Manager
2) Downloaded and installed OTA
3) Didn't reboot and tried to Install Magisk to inactive slot
Unfortunately 3 didn't work. More than that - Magisk Manager doesn't even recognized Magisk was uninstalled. So there is no Installation option.
Tried to Uninstall it again (Restore Original Image) but that didn't change anything.
a) Was the 2nd "Restore Original Image" after installing the OTA a bad idea?
b) How can i install Magisk now?
I don't reboot the phone as i think it could be bricked after that.
Dacoco said:
Hi there,
i'm rooted and i installed the latest OTA (oxygen os 10.3.7.hd01AA - india rom maybe because i used a patched boot.img in the first time months ago) right now and just like all the times before i made the usual steps:
1) Restored Original Image via Magisk Manager
2) Downloaded and installed OTA
3) Didn't reboot and tried to Install Magisk to inactive slot
Unfortunately 3 didn't work. More than that - Magisk Manager doesn't even recognized Magisk was uninstalled. So there is no Installation option.
Tried to Uninstall it again (Restore Original Image) but that didn't change anything.
a) Was the 2nd "Restore Original Image" after installing the OTA a bad idea?
b) How can i install Magisk now?
I don't reboot the phone as i think it could be bricked after that.
Click to expand...
Click to collapse
Well the procedure is disable all magisk modules. Reboot. Take the update don't reboot when the updater says to. Go to magisk select patch to inactive slot let it do it's thing then reboot
for now make a new patched one based on your current is to obtain root like you did initially
Ex pull your current non root boot img patch it in magisk then flash in fastboot
If you need I can grab the India ROM from Updater and make you a patched boot image?
I've already done it for HD01AA EU and HD01BA
Hey, i could manage to install Magisk into inactive slot after updating Magisk manager to the latest version. I would try to reboot now?
If I would like to patch my current boot.img - how can I do so?
digidude512 said:
If you need I can grab the India ROM from Updater and make you a patched boot image?
I've already done it for HD01AA EU and HD01BA
Click to expand...
Click to collapse
Thanks. I think I'll try to reboot and then - if it doesn't Boot - I will come back to you.
Dacoco said:
Thanks. I think I'll try to reboot and then - if it doesn't Boot - I will come back to you.
Click to expand...
Click to collapse
Any luck?
digidude512 said:
Any luck?
Click to expand...
Click to collapse
Booted up and root is working! Thanks a ton!
Dacoco said:
Booted up and root is working! Thanks a ton!
Click to expand...
Click to collapse
Well the ROM is already downloading, Might as well do the boot and recovery images anyway lol
When I'm done I'll update this thread to include HD01AA India
https://forum.xda-developers.com/7t-pro/how-to/oos-10-0-13-hd01aa-t4195159