Related
So I'm trying the Magisk root mode instead of SuperSU. This is my first time messing with Magisk.
I flashed the lastest OOS version and flashed the Magisk zip.
I went to the dowload modules section and installed a bunch of modules without rebooting immediatly. After all installed I rebooted and to my surprise, the phone didn't boot. It stays in the 1+ logo forever.
What have I done wrong? Installed wrong modules? Should I reboot after each module installed?
I flashed the ROM back, wiped cache and dalvik and flashed Magisk again and still the phone isn't booting..
EDIT: Flashed the ROM again without Magisk or SuperSU and it booted, but somehow I lost the TWRP recovery!
Great now it will wipe my phone to install the TWRP recovery again..
These are my favorites so far, I am so happy with them
gonsa said:
So I'm trying the Magisk root mode instead of SuperSU. This is my first time messing with Magisk.
I flashed the lastest OOS version and flashed the Magisk zip.
I went to the dowload modules section and installed a bunch of modules without rebooting immediatly. After all installed I rebooted and to my surprise, the phone didn't boot. It stays in the 1+ logo forever.
What have I done wrong? Installed wrong modules? Should I reboot after each module installed?
I flashed the ROM back, wiped cache and dalvik and flashed Magisk again and still the phone isn't booting..
EDIT: Flashed the ROM again without Magisk or SuperSU and it booted, but somehow I lost the TWRP recovery!
Great now it will wipe my phone to install the TWRP recovery again..
Click to expand...
Click to collapse
It won't wipe your phone if you simply run it in fastboot and flash the TWRP recovery. The only reason it wipes the first time is because you had to do an oem unlock, which is already done now. The only time you will have to wipe your whole phone from now on is if you decrypt, and with ROMs starting to work with encryption, that shouldn't need to be done.
For the boot loop, my guess is a bad module.
To get the phone working again, you did the correct thing in flashing the stock zip without Magisk. The only thing you needed to do right after that was flash TWRP recovery image again through TWRP to overwrite the stock recovery. Then you would boot up, uninstall the modules, and reflash Magisk.
The only Magisk module I use is the stock Google Dialer/Contacts mod.
chazarss said:
These are my favorites so far, I am so happy with them
Click to expand...
Click to collapse
Wow. Didn't knew there are so many modules just for OP5. Guess it's time to root.
Does using doze for Google play services causes any notification issues? Delay etc.
naturist said:
Wow. Didn't knew there are so many modules just for OP5. Guess it's time to root.
Does using doze for Google play services causes any notification issues? Delay etc.
Click to expand...
Click to collapse
None any issue, just flash and relax
ArkAngel06 said:
It won't wipe your phone if you simply run it in fastboot and flash the TWRP recovery. The only reason it wipes the first time is because you had to do an oem unlock, which is already done now. The only time you will have to wipe your whole phone from now on is if you decrypt, and with ROMs starting to work with encryption, that shouldn't need to be done.
For the boot loop, my guess is a bad module.
To get the phone working again, you did the correct thing in flashing the stock zip without Magisk. The only thing you needed to do right after that was flash TWRP recovery image again through TWRP to overwrite the stock recovery. Then you would boot up, uninstall the modules, and reflash Magisk.
The only Magisk module I use is the stock Google Dialer/Contacts mod.
Click to expand...
Click to collapse
thank you for your explanation. I managed to install the TWRP recovery again. what's happening now is I flash the ROM and it boots. I flash Magisk and it doesn't boot. I flash the ROM again and then SuperSU and it works. What I think is happening now is when I flash Magisk it might load the modules that don't work and it won't boot. Is there a way to know if the modules are installed in the background?
What I did now was flash the Magisk uninstaller and flashed the SuperSU and it's working.
Check out this guide I wrote!
https://forum.xda-developers.com/oneplus-5/how-to/guide-fix-twrp-recovery-script-loop-t3649727
Im_Mattgame said:
Check out this guide I wrote!
https://forum.xda-developers.com/oneplus-5/how-to/guide-fix-twrp-recovery-script-loop-t3649727
Click to expand...
Click to collapse
I llaughed out loud when I read the "Flash Stock Recovery - Step 7/ Ponder for a minute at how useless it is"
You guide is good but not for my situation. I can boot, just not with Magisk. The thing was, I installed a lot of Magisk modules all at once, like Viper4Android, Emoji one module, and a bunch of more. Then rebooted and it bootlooped.
Would like to get center clock on the status bar. Is there a module that does this?
the_rooter said:
Would like to get center clock on the status bar. Is there a module that does this?
Click to expand...
Click to collapse
Substratum is your answer to that question. I haven't tried any full themes since our recovery is still a working mess it seems, so I'm worried about backups. But the Ozone Substratum module works well. I just made my clock centered with small date and am/pm. Persists through dirty flashes too.
the_rooter said:
Would like to get center clock on the status bar. Is there a module that does this?
Click to expand...
Click to collapse
This will do it
https://forum.xda-developers.com/oneplus-5/themes/v3-1-ozone-substratum-module-oos-t3627336
gonsa said:
thank you for your explanation. I managed to install the TWRP recovery again. what's happening now is I flash the ROM and it boots. I flash Magisk and it doesn't boot. I flash the ROM again and then SuperSU and it works. What I think is happening now is when I flash Magisk it might load the modules that don't work and it won't boot. Is there a way to know if the modules are installed in the background?
What I did now was flash the Magisk uninstaller and flashed the SuperSU and it's working.
Click to expand...
Click to collapse
I haven't had to mess around with uninstalling Magisk modules, but I assume the method to uninstall a module would be to
Flash system zip
Flash TWRP recovery
Boot into phone
Run the Magisk manager app without actually having Magisk installed
Uninstall or disable the modules
Then install Magisk
gonsa said:
I llaughed out loud when I read the "Flash Stock Recovery - Step 7/ Ponder for a minute at how useless it is"
You guide is good but not for my situation. I can boot, just not with Magisk. The thing was, I installed a lot of Magisk modules all at once, like Viper4Android, Emoji one module, and a bunch of more. Then rebooted and it bootlooped.
Click to expand...
Click to collapse
Ah okay I see, then yeah it is maybe an incompatibility issue with one of the modules, mind listing all of them, I'll try and figure out which one is causing the Bootloop ?
chazarss said:
These are my favorites so far, I am so happy with them
Click to expand...
Click to collapse
Where I can find those zips?
FloyderE said:
Where I can find those zips?
Click to expand...
Click to collapse
just google it man
gonsa said:
So I'm trying the Magisk root mode instead of SuperSU. This is my first time messing with Magisk.
I flashed the lastest OOS version and flashed the Magisk zip.
I went to the dowload modules section and installed a bunch of modules without rebooting immediatly. After all installed I rebooted and to my surprise, the phone didn't boot. It stays in the 1+ logo forever.
What have I done wrong? Installed wrong modules? Should I reboot after each module installed?
I flashed the ROM back, wiped cache and dalvik and flashed Magisk again and still the phone isn't booting..
EDIT: Flashed the ROM again without Magisk or SuperSU and it booted, but somehow I lost the TWRP recovery!
Great now it will wipe my phone to install the TWRP recovery again..
Click to expand...
Click to collapse
Keep in mind that everytime you update your phone it will also install stock recovery. So you'll need to re-install twrp after every oos update.
I have no module installed but I use other apps that needs root.
Btw can anyone comment on atmos or viper4android, does your phone/headphone sound any better?
chazarss said:
None any issue, just flash and relax
Click to expand...
Click to collapse
How big of a difference on battery have you noticed using this doze Google play services module?
sl___ said:
How big of a difference on battery have you noticed using this doze Google play services module?
Click to expand...
Click to collapse
Not realy I can't say that really can fell
chazarss said:
These are my favorites so far, I am so happy with them
Click to expand...
Click to collapse
So for the YouTube no ads, which one did you use, generic or Vance or black Vance?
Aldo for the arise module, do you have a link? I can't find it searching. Thanks.
i am using black version, so far soo good
Arise comes with magisk module in latest version from here https://www.androidfilehost.com/?w=files&flid=176171 but it is little complicated to install. but you can follow here for instuctions http://www.droidviews.com/install-arise-magnum-opus-sound-mod-android/
Hi to all.
I have a rooted A1 with secure start up (have to enter pin before boot starts).
Sometimes when rebooting, device never reaches the point where I'm supposed to enter pin and I have to force a reboot (press & hold power button).
Does anyone else have this problem?
I think it might be an issue with magisk, but not sure.
Thanks in advance!
same happens to me, i have to reboot 2 or 3 times to finally boot
Yeah I had this problem years ago on a Nexus 6
Secure boot isn't really great with magisk or anything that need to do some stuff on boot at it "probably" mess init script I guess
Maybe it could be fixed but as you're rooted safety is below you now.
Be like me and deactivate secure boot !?
Dead-neM said:
Yeah I had this problem years ago on a Nexus 6
Secure boot isn't really great with magisk or anything that need to do some stuff on boot at it "probably" mess init script I guess
Maybe it could be fixed but as you're rooted safety is below you now.
Be like me and deactivate secure boot !?
Click to expand...
Click to collapse
Thanks for your reply.
Yes, I could disable Secure Boot, but without it and by having bootloader unlocked anyone booting TWRP can access my files.
Maybe there are a lot of ways to access files that I'm not aware about too!
Hope the dev could fix this!
deewfrank said:
same happens to me, i have to reboot 2 or 3 times to finally boot
Click to expand...
Click to collapse
Thanks for your reply!
I had this periodically with stable Magisk 16.0. After updating to the latest beta, I'm not experiencing it anymore, phone always boots on the first try.
_mysiak_ said:
I had this periodically with stable Magisk 16.0. After updating to the latest beta, I'm not experiencing it anymore, phone always boots on the first try.
Click to expand...
Click to collapse
Do you think Beta Magisk v16.7 ?
And the right procedure would be : - in fastboot mode booting to twrp.img
- flash uninstaller Magisk, reboot
- and then again booting to twrp.img and install beta Magisk ?
Modules ( Xposed,..) stay untouched during this procedure or I'll have to install them again in beta magisk ?
maputi said:
Do you think Beta Magisk v16.7 ?
And the right procedure would be : - in fastboot mode booting to twrp.img
- flash uninstaller Magisk, reboot
- and then again booting to twrp.img and install beta Magisk ?
Modules ( Xposed,..) stay untouched during this procedure or I'll have to install them again in beta magisk ?
Click to expand...
Click to collapse
It stopped freezing since beta 16.4 as far as I remember, 16.7 is still fine. To update to the latest beta just change from stable to beta channel in Magisk manager and update Magisk as usual. There is no reason to uninstall Magisk.
_mysiak_ said:
It stopped freezing since beta 16.4 as far as I remember, 16.7 is still fine. To update to the latest beta just change from stable to beta channel in Magisk manager and update Magisk as usual. There is no reason to uninstall Magisk.
Click to expand...
Click to collapse
Thanks!
I have updated to 16.7 beta and did 3 or 4 reboots.
So far, so good.
I'm having this problem , I'm using magisk 16.0 and installing magisk 16.7 beta did solve this problem but it made YouTube app crashes and giving me YouTube has stopped error so i returned to magisk 16.0 with booting problem
Anyone have a solution for YouTube app ?
Ashalby said:
I'm having this problem , I'm using magisk 16.0 and installing magisk 16.7 beta did solve this problem but it made YouTube app crashes and giving me YouTube has stopped error so i returned to magisk 16.0 with booting problem
Anyone have a solution for YouTube app ?
Click to expand...
Click to collapse
Have you tried turning on Youtube in MagiskHide while using Magisk 16.7?
whrynox said:
Have you tried turning on Youtube in MagiskHide while using Magisk 16.7?
Click to expand...
Click to collapse
Thanks bro ? i turned on YouTube in magisk hide on 16.7 beta version and restarted my phone and it worked well
Thanks ?
I did a clean reset and installed a fresh android 9. So no root, nothing.
Anyways I install magisk 5.8.3 and then tried to patch the boot.img from the android 9 factory image.
But every time I select the boot.img and try to patch it, it says "Failed! ! Installion failed!".
How has everyone else tried to install magisk on android 9?
xringo said:
I did a clean reset and installed a fresh android 9. So no root, nothing.
Anyways I install magisk 5.8.3 and then tried to patch the boot.img from the android 9 factory image.
But every time I select the boot.img and try to patch it, it says "Failed! ! Installion failed!".
How has everyone else tried to install magisk on android 9?
Click to expand...
Click to collapse
Not the way you are doing it. I boot to TWRP, without installing it and have TWRP install the full zip.
Hm I'll try this. Used to the boot patching.
xringo said:
Hm I'll try this. Used to the boot patching.
Click to expand...
Click to collapse
Just dirty flashed 9 over dp5, booted to twrp and flashed magisk. Rooted, and all appears well.
lorax70 said:
Just dirty flashed 9 over dp5, booted to twrp and flashed magisk. Rooted, and all appears well.
Click to expand...
Click to collapse
You can give link file magisk for use on android 9.
newyesor said:
You can give link file magisk for use on android 9.
Click to expand...
Click to collapse
Fwiw. I've been using this magisk version for dp3-5, but there are newer versions, but 16.4 works for me...
https://thedroidarena.com/download-magisk-16-4-beta/
I may try a newer version at some point, but I'm in no rush.
newyesor said:
You can give link file magisk for use on android 9.
Click to expand...
Click to collapse
Got this from the Flash kernel thread. It works fine on Pie :good:
https://drive.google.com/file/d/106ZiqeQxNYtCHkOEc6niuHRcWiCzG_eA/view?usp=drivesdk
xringo said:
I did a clean reset and installed a fresh android 9. So no root, nothing.
Anyways I install magisk 5.8.3 and then tried to patch the boot.img from the android 9 factory image.
But every time I select the boot.img and try to patch it, it says "Failed! ! Installion failed!".
How has everyone else tried to install magisk on android 9?
Click to expand...
Click to collapse
Make sure your using 16.7 you have to change in setting to beta. Same thing happened to me trying to use 16.0
I get updater error :2 failed to install every freaking time. No matter what zip i use. 1600 1671 1674
After dirty flash (remove -w) Android 9 PPR1 then install Magisk 16.7, it seems I am not able to set PIN or any security... Anyone has the same issue?
I have the same issue TWRP also can't decript the phone. I am going to wipe everything, and fastboot erase userdata.
lssong99 said:
After dirty flash (remove -w) Android 9 PPR1 then install Magisk 16.7, it seems I am not able to set PIN or any security... Anyone has the same issue?
Click to expand...
Click to collapse
Sent from my Pixel 2 XL using Tapatalk
Airpil said:
I have the same issue TWRP also can't decript the phone. I am going to wipe everything, and fastboot erase userdata.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Don't wipe your phone! Just flash the new boot.img from the image file (not OTA file) and you will be able to go back to your Android system and disable the pin. After disable the pin, boot into TWRP and flash the Magisk from here https://forum.xda-developers.com/showpost.php?p=77240449&postcount=2832
Hope this helps!
madmuthertrucker said:
I get updater error :2 failed to install every freaking time. No matter what zip i use. 1600 1671 1674
Click to expand...
Click to collapse
Use magisk uninstall first and this should solve the issue.
lssong99 said:
After dirty flash (remove -w) Android 9 PPR1 then install Magisk 16.7, it seems I am not able to set PIN or any security... Anyone has the same issue?
Click to expand...
Click to collapse
I have flashed ota from dp5 and fresh install of 9 and I cannot use security with 3.2.1_2 or 3.2.2 TWRP
Brakiss said:
I have flashed ota from dp5 and fresh install of 9 and I cannot use security with 3.2.1_2 or 3.2.2 TWRP
Click to expand...
Click to collapse
There's a 3.2.3-0 out as well. It's reportedly able to decrypt using alphanumeric codes. However a straight 4 number pin still isn't working for me.
Badger50 said:
There's a 3.2.3-0 out as well. It's reportedly able to decrypt using alphanumeric codes. However a straight 4 number pin still isn't working for me.
Click to expand...
Click to collapse
Where did you see this? I have pattern and would like to keep it.
Brakiss said:
Where did you see this? I have pattern and would like to keep it.
Click to expand...
Click to collapse
One of the other threads. Here's the twrp version though. https://dl.twrp.me/taimen/
Been having issues myself since updating to Pie yesterday. TWRP installed working fine. Installed magisk manager, set to beta channel. Rebooted into TWRP and flashed magisk 16.7, phone hanging at the lovely google logo page. I then have to run the uninstaller back in TWRP or i cant get the phone to boot. Anyone had this?
pr1vate piles said:
Been having issues myself since updating to Pie yesterday. TWRP installed working fine. Installed magisk manager, set to beta channel. Rebooted into TWRP and flashed magisk 16.7, phone hanging at the lovely google logo page. I then have to run the uninstaller back in TWRP or i cant get the phone to boot. Anyone had this?
Click to expand...
Click to collapse
Yeah, rooting on P is a little tricky it seems. You'll likely have to run the uninstaller, then boot up. Then go back to twrp and flash this version of magisk. It's the 16.7(4) version found in the Flash kernel thread :good:
https://drive.google.com/file/d/106ZiqeQxNYtCHkOEc6niuHRcWiCzG_eA/view?usp=drivesdk
Badger50 said:
Yeah, rooting on P is a little tricky it seems. You'll likely have to run the uninstaller, then boot up. Then go back to twrp and flash this version of magisk. It's the 16.7(4) version found in the Flash kernel thread :good:
https://drive.google.com/file/d/106ZiqeQxNYtCHkOEc6niuHRcWiCzG_eA/view?usp=drivesdk
Click to expand...
Click to collapse
Your not wrong there. Tried it as you suggested, same thing, hanging at the G logo page with the bar animation under it. Had to run the uninstaller to get back into my phone. Very odd
What is the best way to update Magisk on OP6T. Currently running v17.1 and if I would like to update to latest v18, what is the way to do it and not to brick the phone?
Thank for info
maraschino said:
What is the best way to update Magisk on OP6T. Currently running v17.1 and if I would like to update to latest v18, what is the way to do it and not to brick the phone?
Thank for info
Click to expand...
Click to collapse
You can either update via the Magisk Manager app,or,if you have TWRP,use it to update to the latest Magisk.
FWIW,I have TWRP installed,but,updated using the Magisk Manager app,using the recommended install suggestion given.
Just updated mine via app , after reboot there was no signal , no simcard ,no imei dont panic reboot one more time ,and everything is working as usual.
KOLIOSIS said:
You can either update via the Magisk Manager app,or,if you have TWRP,use it to update to the latest Magisk.
FWIW,I have TWRP installed,but,updated using the Magisk Manager app,using the recommended install suggestion given.
Click to expand...
Click to collapse
I have no TWRP, so I can just install through app and there will be no problem. It will install in the right slot automatically and I will keep root?
maraschino said:
I have no TWRP, so I can just install through app and there will be no problem. It will install in the right slot automatically and I will keep root?
Click to expand...
Click to collapse
Yes, I used the direct install via the Magisk Manager app & immediately rebooted,no problems at all.
KOLIOSIS said:
Yes, I used the direct install via the Magisk Manager app & immediately rebooted,no problems at all.
Click to expand...
Click to collapse
Thx for info
I always update through TWRP. Just updated. Since I always choose the hide magisk option replacing it with a random name I uninstall the app real quick before I reboot to recovery. Used to be if you didn't you would end up with two apps installed. Don't know if this is still an issue or not. Either way all your settings will still be there. I uninstall the app, reboot to recovery, flash Magisk. Boot back into the OS, all my settings are already there, so the only thing I have to do is rehide Magisk.
Do this update fix the charge problem when the device is off?
ELGeKo24 said:
Do this update fix the charge problem when the device is off?
Click to expand...
Click to collapse
Didn't fix it for me.
OS 9.0.7.
TWRP 3.2.3-9
Magisk v18
I'm having issues acquiring superuser rights with the new update (stock rom/kernel). On some apps it works on others it doesn't pop up with a notification, Titanium Backup being a notable one.
Any ideas?
edit: got it working by increasing the length of time before timeouts from 10sec to 60sec.
I usually start over.
I flash a virgin boot age to both slots.
Reboot with TWRP
Install TWRP zip
Install ElementalX and Magisk zips.
Change slots and reboot recovery
Install ElementalX and Magisk in this slot.
I have the same OS version and kernels etc flashed in both slots.
lostunsunghero said:
I'm having issues acquiring superuser rights with the new update (stock rom/kernel). On some apps it works on others it doesn't pop up with a notification, Titanium Backup being a notable one.
Any ideas?
edit: got it working by increasing the length of time before timeouts from 10sec to 60sec.
Click to expand...
Click to collapse
Or you can also disable the Battery Optimisation for Magisk
Hey guys, sorry for my stupid asking. I have following case:
I had installed an old version of magisk. Today I got the update offered in magisk manager app. I updated the manager first, now I have 2 magsik manager apps in my device. I opened the new one and it says that I haven't installed the latest version. So far so good.
I downloaded the latest V18.1 from GitHub and installed the zip via twrp.
It installed normally and booted as always.
But I still have 2 versions of the manager apps in my device. Old one says I have V18.1 installed, root access is there. Checked it with root checker.
The new manager app says that I haven't installed the latest version and I have an update available.
Does anyone have an idea how I can get to a normal state with 1 manager app ?
KOLIOSIS said:
You can either update via the Magisk Manager app,or,if you have TWRP,use it to update to the latest Magisk.
FWIW,I have TWRP installed,but,updated using the Magisk Manager app,using the recommended install suggestion given.
Click to expand...
Click to collapse
What is the recommended install suggestion? Only Zip or with Boot image patch?
Calvin1997 said:
Hey guys, sorry for my stupid asking. I have following case:
I had installed an old version of magisk. Today I got the update offered in magisk manager app. I updated the manager first, now I have 2 magsik manager apps in my device. I opened the new one and it says that I haven't installed the latest version. So far so good.
I downloaded the latest V18.1 from GitHub and installed the zip via twrp.
It installed normally and booted as always.
But I still have 2 versions of the manager apps in my device. Old one says I have V18.1 installed, root access is there. Checked it with root checker.
The new manager app says that I haven't installed the latest version and I have an update available.
Does anyone have an idea how I can get to a normal state with 1 manager app ?
Click to expand...
Click to collapse
Same thing with me. I tried it twice to set of something weird happened with the same result. And if you do a safetynet check on the old app it deletes the new one for me for some reason.
bladestonez said:
Same thing with me. I tried it twice to set of something weird happened with the same result. And if you do a safetynet check on the old app it deletes the new one for me for some reason.
Click to expand...
Click to collapse
You're right. If tried the safetynet check on the new one, and after that the new one was removed. Completely strange. I hope someone here knows what to do
No problem here just selected install then used recommended.
spjetrovic said:
No problem here just selected install then used recommended.
Click to expand...
Click to collapse
What's the recommended option? I have the options flash zip and patch Boot image but there isn't any "recommended" mark
spjetrovic said:
No problem here just selected install then used recommended.
Click to expand...
Click to collapse
So you just did the direct install option? Also are you running magisk with or without TWRP?
Calvin1997 said:
What's the recommended option? I have the options flash zip and patch Boot image but there isn't any "recommended" mark
Click to expand...
Click to collapse
This is what I get when I install from magiek manager.
Yes with TWRP
So my phone was working fine with magisk installed and for a couple weeks then I tried to install Viper and Busybox modules but when I did the phone got stuck in a recovery bootloop. Now every time I try and flash magisk I get a recovery bootloop. I've uninstalled all the modules uninstalled magisk everything but I can't figure it out. for some reason every time I install magisk I can no longer boot the phone. Can anyone help me out with this?
Thanks
GbizzleMcGrizzle said:
So my phone was working fine with magisk installed and for a couple weeks then I tried to install Viper and Busybox modules but when I did the phone got stuck in a recovery bootloop. Now every time I try and flash magisk I get a recovery bootloop. I've uninstalled all the modules uninstalled magisk everything but I can't figure it out. for some reason every time I install magisk I can no longer boot the phone. Can anyone help me out with this?
Thanks
Click to expand...
Click to collapse
Only thing I can think of is try dirty flashing your current rom and try again.
bladestonez said:
Only thing I can think of is try dirty flashing your current rom and try again.
Click to expand...
Click to collapse
Thanks I finally got the msmtool to work after 15 straight hours. Wow what a finicky program apparently if you don't enter EDL after the online had been off for at least 30 seconds it just doesn't work.
Still I don't understand what happened. Obviously a magisk module broke it in a truly fantastic way