I recently followed the instructions in this video to root my Pixel 1 (non-XL, Verizon version unlocked bootloader, updated to final version of Pie). I'm not exactly sure what I did wrong, but my phone went into a bootloop and I couldn't get any adb command to work (it said phone not authorized even though it clearly was before the bootloop), so I went ahead and did a factory reset using the Recovery mode.
Now, after the factory reset, I have Magisk Manager appear in my list of apps. When I open it it asks if I want to upgrade to the full Magisk Manager, and if I go ahead with that it finally says "App not installed". I've tried uninstalling the app but it reappears after every reboot.
I'm trying to start afresh with the root now, but I'm not sure if I need to uninstall Magisk first, or just go ahead with following #7 in this XDA guide? Any advice would be helpful.
Thanks!
Run the Magisk uninstaller and reboot, then reinstall Magisk.
post-mortem said:
Run the Magisk uninstaller and reboot, then reinstall Magisk.
Click to expand...
Click to collapse
Hi, thanks for posting. I'm kinda new to this so I'm not sure how to do that. Can you give me a little more help as to how I should go about uninstalling it? I have downloaded Magisk-uninstaller-20180719.zip. Thanks a lot!
hassanrashid3 said:
Hi, thanks for posting. I'm kinda new to this so I'm not sure how to do that. Can you give me a little more help as to how I should go about uninstalling it? I have downloaded Magisk-uninstaller-20180719.zip. Thanks a lot!
Click to expand...
Click to collapse
Transfer that Fe to your phone. Boot to recovery (TWRP), a d install the Magisk uninstaller zip file. That will remove all files related to Magisk. Reboot,* then reboot to TWRP and you can try to install Magisk again.
*If your device doesn't boot, use fastboot to install the boot.img. If it seems a bit daunting, you can sideload the most recent OTA. You won't lose data.
post-mortem said:
Transfer that Fe to your phone. Boot to recovery (TWRP), a d install the Magisk uninstaller zip file. That will remove all files related to Magisk. Reboot,* then reboot to TWRP and you can try to install Magisk again.
*If your device doesn't boot, use fastboot to install the boot.img. If it seems a bit daunting, you can sideload the most recent OTA. You won't lose data.
Click to expand...
Click to collapse
I actually did these steps just a few hours ago and rooted my device successfully. After uninstalling Magisk my device wouldn't boot, so had to use ./flash-all.sh (I'm on a Mac) after removing -w from the file, then installed Magisk.
Anyway, thanks for the reply! I'm sure someone will find it useful.
hassanrashid3 said:
I actually did these steps just a few hours ago and rooted my device successfully. After uninstalling Magisk my device wouldn't boot, so had to use ./flash-all.sh (I'm on a Mac) after removing -w from the file, then installed Magisk.
Anyway, thanks for the reply! I'm sure someone will find it useful.
Click to expand...
Click to collapse
I've been trying to get rooted all day. It took forever to get TWRP flashed, but when I finally did, I installed Magisk, in accordance with that same video you watched. Installed the Magisk app and it was totally worthless. Nothing but ads. Still not rooted. I'd love to know what you did to finally get root if you have a second.
Hmm, I'm not sure what version of Magisk you installed but mine didn't have ads. I'd recommend uninstalling Magisk (there's an uninstaller that you can install to your phone just as you installed Magisk) and then again using TWRP to install the correct version. Look at the instructions here. You'll need to download the Magisk uninstaller, the latest version of Magisk, and the latest version of platform-tools.
hassanrashid3 said:
Hmm, I'm not sure what version of Magisk you installed but mine didn't have ads. I'd recommend uninstalling Magisk (there's an uninstaller that you can install to your phone just as you installed Magisk) and then again using TWRP to install the correct version. Look at the instructions here. You'll need to download the Magisk uninstaller, the latest version of Magisk, and the latest version of platform-tools.
Click to expand...
Click to collapse
Yeah, it was a big ol' mess. The Magisk I had installed was from the app store. That was the worthless one. Apparently the real Magisk hadn't been flashed correctly. When I ditched the store app and then re-flashed Magisk, suddenly I was rooted and everything went smoothly. Worst rooting experience ever, but man does it feel good to have control over my phone again. Been kicking bloatware extra hard just because can.
---------- Post added at 12:30 AM ---------- Previous post was at 12:27 AM ----------
By the way, hassanrashid, thanks for the reply and for posting this in the first place. I'm not so sure that I would have gotten rooted at all if I hadn't stumbled upon this thread.
Related
Hi, I rooted my a9 back in May right around when 6.0.1 came out. Long story short, my device just gave up the ghost after a nasty interaction between the screen and concrete, so now I have a new device being shipped tomorrow. I figured the first thing I'll do is let it run any updates / OTAs it might have to get it up to date then attempt to root again.
I've been looking around for the past several hours trying to determine what the correct rooting method might be now given Nougat's rollout, but I haven't come across anything truly definitive yet. If anyone could enlighten me on what I'll need to do now to root this new version I'd be very appreciative.
Thanks in advance guys!
Just got the phone today and updated to 7.0 (software version 2.18.651.2) Still searching around and not seeing a definitive answer on whether or not the old method for rooting works for this or not. I'm hesitant to attempt it without knowing, so any advice would be greatly appreciated.
Last time I rooted, I used Windroid toolkid to unlock the bootloader, flash TWRP and apply SU. I'm wondering, would the same program work if I replaced the recovery.img file in the Data folder with the TWRP 3.0.3 unofficial recovery I saw floating around in here for nougat?
txag2011 said:
Just got the phone today and updated to 7.0 (software version 2.18.651.2) Still searching around and not seeing a definitive answer on whether or not the old method for rooting works for this or not. I'm hesitant to attempt it without knowing, so any advice would be greatly appreciated.
Last time I rooted, I used Windroid toolkid to unlock the bootloader, flash TWRP and apply SU. I'm wondering, would the same program work if I replaced the recovery.img file in the Data folder with the TWRP 3.0.3 unofficial recovery I saw floating around in here for nougat?
Click to expand...
Click to collapse
You can unlock it on the HTCDEV website, although if you've already got it unlocked I doubt you need to do it again. To root I just ADB fastboot flashed TWRP 3.0.3-4, then used that to flash Magisk, mounting system read only. I'm fairly sure some people are using Su on Nougat, so it'll probably work.
Never used the Windroid toolkit so I can't comment on that, but I've also never minded typing commands to the prompt. I'd imagine if you gave it the right TWRP it'd flash it OK..
JohnRogers23 said:
You can unlock it on the HTCDEV website, although if you've already got it unlocked I doubt you need to do it again. To root I just ADB fastboot flashed TWRP 3.0.3-4, then used that to flash Magisk, mounting system read only. I'm fairly sure some people are using Su on Nougat, so it'll probably work.
Never used the Windroid toolkit so I can't comment on that, but I've also never minded typing commands to the prompt. I'd imagine if you gave it the right TWRP it'd flash it OK..
Click to expand...
Click to collapse
That actually doesn't sound too bad; From that it seems like the process is still more or less the same. Why is the system mounted as read only though? After looking through most of the older step by step guides it doesn't mention anything about doing that. From what I see, after i run the command "fastboot flash recovery recovery.img" i boot into TWRP and then proceed to do a factory reset and wipe the cache, presumably to remove the encryption iirc, then install the supersu.zip is that still the correct procedure, or does this require mounting the system as read only now?
If you don't mind me asking, what steps exactly did you take to root yours? from what I've found all I need to do is get the bootloader unlocked with the steps from HTCDev, drop into download more, fastboot flash recovery recovery.img to get TWRP, boot into TWRP, run a format to get rid of the encryption, then install supersu.zip and that should be it. IS this correct or am I missing something?
I'm about to start the process trying to root using the above methods.. I'll post again when I have results.
txag2011 said:
That actually doesn't sound too bad; From that it seems like the process is still more or less the same. Why is the system mounted as read only though? After looking through most of the older step by step guides it doesn't mention anything about doing that. From what I see, after i run the command "fastboot flash recovery recovery.img" i boot into TWRP and then proceed to do a factory reset and wipe the cache, presumably to remove the encryption iirc, then install the supersu.zip is that still the correct procedure, or does this require mounting the system as read only now?
If you don't mind me asking, what steps exactly did you take to root yours? from what I've found all I need to do is get the bootloader unlocked with the steps from HTCDev, drop into download more, fastboot flash recovery recovery.img to get TWRP, boot into TWRP, run a format to get rid of the encryption, then install supersu.zip and that should be it. IS this correct or am I missing something?
Click to expand...
Click to collapse
It wasn't bad at all. The reason I mounted R/O is because I'm using Magisk and not disabling dm-verity. I'm not sure if it works the same on 7, but SuperSu should disable dm-verity, so if you're using it you might not need to mount R/O, I haven't been keeping up on that at all. Benefits of Magisk include Android Pay and being able to take an OTA.
That all sounds like exactly what you need to do, except I believe it's fastboot mode (the one with the black screen?) to flash TWRP. I also didn't have to format anything, but I believe you do if you're using Su and disabling forced encryption. You may want to take a system image backup before you change anything, so you can go back to stock and get an OTA, or in case something goes wrong, but other than that it sounds correct to me.
JohnRogers23 said:
It wasn't bad at all. The reason I mounted R/O is because I'm using Magisk and not disabling dm-verity. I'm not sure if it works the same on 7, but SuperSu should disable dm-verity, so if you're using it you might not need to mount R/O, I haven't been keeping up on that at all. Benefits of Magisk include Android Pay and being able to take an OTA.
That all sounds like exactly what you need to do, except I believe it's fastboot mode (the one with the black screen?) to flash TWRP. I also didn't have to format anything, but I believe you do if you're using Su and disabling forced encryption. You may want to take a system image backup before you change anything, so you can go back to stock and get an OTA, or in case something goes wrong, but other than that it sounds correct to me.
Click to expand...
Click to collapse
huh... Magisk can utilize android pay and OTA's? I'm a little bit intrigued.. I just might have to give that a quick look now. Was it difficult to get up and running, and is there a fairly decent guide for doing it?
txag2011 said:
huh... Magisk can utilize android pay and OTA's? I'm a little bit intrigued.. I just might have to give that a quick look now. Was it difficult to get up and running, and is there a fairly decent guide for doing it?
Click to expand...
Click to collapse
Magisk is a framework for systemlessly modifying /system, so safety net works and you can take an OTA (with stock recovery), and also includes root. It's brilliant, but not quite as powerful as Xposed. Not difficult at all to get running, all it needs is to flash the magisk installer zip in TWRP (system mounted R/O of course) and then install the Magisk Manager app from the play store.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
JohnRogers23 said:
Magisk is a framework for systemlessly modifying /system, so safety net works and you can take an OTA (with stock recovery), and also includes root. It's brilliant, but not quite as powerful as Xposed. Not difficult at all to get running, all it needs is to flash the magisk installer zip in TWRP (system mounted R/O of course) and then install the Magisk Manager app from the play store.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Click to expand...
Click to collapse
I might give this a shot then, thank you for that. I'm about to try flashing TWRP 3.0.3-0. From the looks of it this is the most current one available. I'll update when it's done
txag2011 said:
I might give this a shot then, thank you for that. I'm about to try flashing TWRP 3.0.3-0. From the looks of it this is the most current one available. I'll update when it's done
Click to expand...
Click to collapse
Go to the TWRP thread, hit the download tab, pick one of the newer ones there. I went with 3.0.3.-4.
JohnRogers23 said:
Go to the TWRP thread, hit the download tab, pick one of the newer ones there. I went with 3.0.3.-4.
Click to expand...
Click to collapse
Did just that. Got TWRP installed successfully. I PM'ed you a second ago but I might as well ask this here for everyone else to see in case someone else is wondering this too.... So if I'm understanding Magisk correctly, all I do now is hit install and choose Magisk v11.1?
Edit: I did just that, but it doesnt seem to have done anything.. I dont see and magisk apps, and root checker says i'm not rooted.. Did I miss something?
edit 2: scratch that... I just installed the magisk manager app from the playstore.. according to it, the latest version of magisk is in fact, installed, and it's rooted with magisksu (despite not showing so in rootchecker).. Little confused now. Is that everything that needs to be done?
edit 3: I went back in after seeing something mentioning installing phh's superuser via TWRP and installing the app after installing magisk. Did both, but noticed safety net wasn't passing. found an option in settings to hide magisk, which seems to fix that. I also ran root checker again and it shows I have root.
unless I missed anything you can think of I think that about finishes things. If thats it thank you for all the help @JohnRogers23
txag2011 said:
Did just that. Got TWRP installed successfully. I PM'ed you a second ago but I might as well ask this here for everyone else to see in case someone else is wondering this too.... So if I'm understanding Magisk correctly, all I do now is hit install and choose Magisk v11.1?
Edit: I did just that, but it doesnt seem to have done anything.. I dont see and magisk apps, and root checker says i'm not rooted.. Did I miss something?
edit 2: scratch that... I just installed the magisk manager app from the playstore.. according to it, the latest version of magisk is in fact, installed, and it's rooted with magisksu (despite not showing so in rootchecker).. Little confused now. Is that everything that needs to be done?
edit 3: I went back in after seeing something mentioning installing phh's superuser via TWRP and installing the app after installing magisk. Did both, but noticed safety net wasn't passing. found an option in settings to hide magisk, which seems to fix that. I also ran root checker again and it shows I have root.
unless I missed anything you can think of I think that about finishes things. If thats it thank you for all the help @JohnRogers23
Click to expand...
Click to collapse
I'm glad you got it working. Strange you had to flash phh's Su separately though. Anyway, glad I could help.
Well Working !
1.Backup your all imp data from internal memory
2.Flash TWRP 3.0.3-4.. Do not reboot into system and enter into Recovery TWRP..
3.Do a factory Reset via TWRP.. Do not reboot into system
4.Now flash SuperSU 2.79 SR3 via TWRP.. Finally Reboot into system..
*2 bootloops are common, do not give up for at least 3 bootloops..
*It will take a long time to boot as you have done a factory reset.. So be patient and wait for at least half hour..
Dr.Anshuman said:
1.Backup your all imp data from internal memory
2.Flash TWRP 3.0.3-4.. Do not reboot into system and enter into Recovery TWRP..
3.Do a factory Reset via TWRP.. Do not reboot into system
4.Now flash SuperSU 2.79 SR3 via TWRP.. Finally Reboot into system..
*2 bootloops are common, do not give up for at least 3 bootloops..
*It will take a long time to boot as you have done a factory reset.. So be patient and wait for at least half hour..
Click to expand...
Click to collapse
Thanks! I got it more or less and went with magisk. Couldn't pass up a chance to have root and still get OTAs and use android pay. I'm still monkeying around trying to figure out how to use it to get liveboot back up and running.
Sorry, its been quite a while since ive rooted and im new to Magisk. Im currently on November .a1 update. I followed the below tutorial
If starting fresh from November (.A1.) Update
Install November update
Download latest Magisk Beta (17.3) and move it to the internal storage of the device
Reboot to bootloader
Download the .img version of TWRP for "crosshatch"
In the location of downloaded TWRP .img, open cmd and enter
Code:
fastboot boot twrp-3.2.3-1-crosshatch.img
Allow twrp to boot (this will take a minute or two)
Then go to install and install the Magisk zip
Reboot and find magisk manager and make sure it says you're rooted
Until there is an update to the patched_boot.imgs, dont follow the how to beyond this point. In fact I am hiding it for the time being.
https://forum.xda-developers.com/pixel-3-xl/how-to/how-to-root-pixel-3-xl-magisk-t3856712#login
Click to expand...
Click to collapse
But I do not see the "MAGISKSU (topjohnwu)" at all. I feel like there's more to root than just installing Magisk from TWRP. I see an "Install" but am hesistant as I bricked my phone last time I tried this.
What am I missing?
JJT211 said:
Sorry, its been quite a while since ive rooted and im new to Magisk. Im currently on November .a1 update. I followed the below tutorial
But I do not see the "MAGISKSU (topjohnwu)" at all. I feel like there's more to root than just installing Magisk from TWRP. I see an "Install" but am hesistant as I bricked my phone last time I tried this.
What am I missing?
Click to expand...
Click to collapse
It is just flash the zip from TWRP. And based on that screenshot it looks like you are done. What happens when you try and do something that requires root?
TonikJDK said:
It is just flash the zip from TWRP. And based on that screenshot it looks like you are done. What happens when you try and do something that requires root?
Click to expand...
Click to collapse
I usually verify root by downloading root checker app. App says that I'm not rooted.
EDIT: Nevermind, I tried it again and now it says I'm rooted. Thanks!
Someone help me shed some light. I'm not sure what I did wrong while updating using magisk.
So this is the steps I did.
1. Installed the OTA update
2. In magisk went to install to inactive slot (after OTA)
3. Then it went through the motions and restarted.
At the screen where you put the password in it shut down and then went to the stock recovery. Tried again, same thing. So after some panicking I did this.
Reflashed twrp via computer
Flashed the uninstall of magisk
Flashed twrp zip
Restarted it and everything is fine now. I just had to re-flash the modules which was quite annoying.
So what did I do wrong? Have I buggered up anything to do with the inactive slots or partitions?
Did you uninstall Magisk modules First?
null0seven said:
Did you uninstall Magisk modules First?
Click to expand...
Click to collapse
I didn't. The whole point of doing it the way I did was to eliminate the need to uninstall the modules.
Could that be what went wrong?
YES.
null0seven said:
YES.
Click to expand...
Click to collapse
So that's what I should have done. Although it is working now could I have caused any problems with the partitions/slots? And what about future updates, could there be any problems using this method (the correct one).
To clarify is this the steps:
Install OTA update (no reboot)
Go to magisk delete the mods
Then install to inactive slot
Flash twrp?
Reboot
Would that be correct?
JohnsNotHome said:
So that's what I should have done. Although it is working now could I have caused any problems with the partitions/slots? And what about future updates, could there be any problems using this method (the correct one).
To clarify is this the steps:
Install OTA update (no reboot)
Go to magisk delete the mods
Then install to inactive slot
Flash twrp?
Reboot
Would that be correct?
Click to expand...
Click to collapse
Go to magisk and delete mods,
Reboot,
Install OTA,
TWRP A/B retention script,
Install magisk to inactive,
Reboot
Arden144 said:
Go to magisk and delete mods,
Reboot,
Install OTA,
TWRP A/B retention script,
Install magisk to inactive,
Reboot
Click to expand...
Click to collapse
Sorry to ask but what is "twrp a/b retention script"? Everything else is all clear. Thank you so much.
JohnsNotHome said:
Sorry to ask but what is "twrp a/b retention script"? Everything else is all clear. Thank you so much.
Click to expand...
Click to collapse
It's available in Magisk under downloads, and basically backs up your old TWRP install and installs it on the newly updated slot. I have an update guide if you'd like to read it
https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-bootloader-unlock-twrp-install-t3940368
The exact same thing happened to me! The thread I followed said to 'remove' all Magisk modules which is what caused the problem. You have to delete all Magisk modules, then re-install them when your up & running again
mike710_0 said:
The exact same thing happened to me! The thread I followed said to 'remove' all Magisk modules which is what caused the problem. You have to delete all Magisk modules, then re-install them when your up & running again
Click to expand...
Click to collapse
Interesting.. I think I'll just follow this method. This was all in the name of saving time.
mike710_0 said:
The exact same thing happened to me! The thread I followed said to 'remove' all Magisk modules which is what caused the problem. You have to delete all Magisk modules, then re-install them when your up & running again
Click to expand...
Click to collapse
Arden144 said:
It's available in Magisk under downloads, and basically backs up your old TWRP install and installs it on the newly updated slot. I have an update guide if you'd like to read it
https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-bootloader-unlock-twrp-install-t3940368
Click to expand...
Click to collapse
Thank you so much for this. I think I understand now.
I hope I haven't caused any problems to the slots thing on magisk with the mistake I made.
1. Uninstal Magisk mods.
2. Flash Oos in System > Update > Local Update. DON'T reboot.
3. Open Magisk > Downloads > TWRP A/B Retention script. Instal it.
4. From Magisk reboot to twrp. Flash Magisk 19.3 stable.
Reboot to system. You should be updated and rooted.
I upgraded to Android 10 using a guide from someone who successfully kept root when upgrading from Android Pie to 10. I followed the steps exactly, but I still lost root. I'm using the latest version of TWRP Guacamole for the OnePlus 7 Pro. I fully understand that it's not fully compatible with my phone so I'm wanting to roll back to Pie. My phone currently does not have an OS on it because another guide I followed said to flash TWRP as the boot in the bootloader in order to reboot into TWRP to then reflash the OTA and then TWRP. I did this because TWRP would not mount my storage and therefore could not install or flash anything because it couldn't access storage. That didn't work. So now when I boot normally or into TWRP, it only boots into the bootloader. I need help fixing this because now I'm out of a very nice phone.
https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691
unrated87 said:
https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691
Click to expand...
Click to collapse
That did not work. Everytime I hit the hyperlink for the tool, it redirected me to an ad for a network monitoring software called solarwinds.
BUZzZERBeater00 said:
That did not work. Everytime I hit the hyperlink for the tool, it redirected me to an ad for a network monitoring software called solarwinds.
Click to expand...
Click to collapse
Just a few things before you flash. Don't worry about losing root, it's better to uninstall Magisk before upgrading, updates you can flash without uninstalling Magisk, although I wouldn't recommend it. I'm coming from the 5T, and it's basically the same process. The only difference is that I have a device with A/B partitions now
https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-mega-unbrick-guide-hard-bricked-t3934659
blas4me said:
Just a few things before you flash. Don't worry about losing root, it's better to uninstall Magisk before upgrading, updates you can flash without uninstalling Magisk, although I wouldn't recommend it. I'm coming from the 5T, and it's basically the same process. The only difference is that I have a device with A/B partitions now
https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-mega-unbrick-guide-hard-bricked-t3934659
Click to expand...
Click to collapse
Thank you. I'm going to try it when I have time. I had to go through a few links that your initial link let me to. I found this thread. I'm hoping this will work. Sounds a lot like my problem.
https://forum.xda-developers.com/oneplus-3t/how-to/op3t-collection-unbrick-tools-t3896765/page2
blas4me said:
Just a few things before you flash. Don't worry about losing root, it's better to uninstall Magisk before upgrading, updates you can flash without uninstalling Magisk, although I wouldn't recommend it. I'm coming from the 5T, and it's basically the same process. The only difference is that I have a device with A/B partitions now
https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-mega-unbrick-guide-hard-bricked-t3934659
Click to expand...
Click to collapse
I tried using the MSMDownloadTool, but the Qualcomm HS-USB QDLoader 9008 (COM3) driver was grayed out in the device manager. When I would open the MSMDownloadTool, it would not recognize my device, and would not download anything. Any suggestions?
BUZzZERBeater00 said:
Thank you. I'm going to try it when I have time. I had to go through a few links that your initial link let me to. I found this thread. I'm hoping this will work. Sounds a lot like my problem.
https://forum.xda-developers.com/oneplus-3t/how-to/op3t-collection-unbrick-tools-t3896765/page2
Click to expand...
Click to collapse
I fixed it. These links helped me along the way. Thanks again for the initial suggestion!
https://forum.xda-developers.com/one...t3896765/page2
https://piunikaweb.com/2019/05/29/how-to-unbrick-oneplus-7-pro-using-msm-download-tool/
BUZzZERBeater00 said:
I fixed it. These links helped me along the way. Thanks again for the initial suggestion!
https://forum.xda-developers.com/one...t3896765/page2
https://piunikaweb.com/2019/05/29/how-to-unbrick-oneplus-7-pro-using-msm-download-tool/
Click to expand...
Click to collapse
Suggestion, when you get to stock, stay there. If it's taking you this long to figure things out, this is not your thing.
blas4me said:
Suggestion, when you get to stock, stay there. If it's taking you this long to figure things out, this is not your thing.
Click to expand...
Click to collapse
Sorry. It's too late. I already have Magisk installed and Edxposed.
I just installed Edxposed
blas4me said:
I just installed Edxposed
Click to expand...
Click to collapse
Ya. It worked perfectly as long as I flashed Riru - Core, rebooted, then flashed Riru - Edxposed, rebooted. Then installed the Edxposed apk. Flashing both Riru -Core and Riru - Edxposed back-to-back before rebooting put my OnePlus 7 Pro into a bootloop. I had to boot into TWRP and flash a "Magisk in TWRP" module and then in the terminal type "mm for first time" hit enter, and type "c" which put takingmy phone in Core Only Mode. This disabled the modules it out of the bootloop. But then after it reboots, attempt to uninstall the modules, which won't fully work. So basically you'd just have to flash the magisk uninstaller and flash the magisk installer to get rid of the bad modules. Moral of the story is don't flash both Riru - Core and Riru -Edxposed without rebooting between each install. Also, don't just flash the magisk uninstaller and flash the magisk installer to get rid of the bad modules and then not later flash the "Magisk in TWRP" module and disable Core Only Mode. Or just turn it off in Magisk Manager. Modules will install, but they won't work. And they won't uninstall either.
I installed magisk manager. When I tried to install magisk using the boot image, it does not work. It says that it installs, but then it still shows that it is not installed. I tried using TWRP, but my phone would get stuck in a bootloader loop, so I stopped doing that. Any ideas?
bmp
https://forum.xda-developers.com/pixel-2/how-to/guide-unlock-flash-root-pixel-2-walleye-t3702417
twrp does not work on our phones anymore. therefore you can't flash it in the magisk manager. use the methode in the 1st post in the thread above. It works just fine.
Snow_ball said:
https://forum.xda-developers.com/pixel-2/how-to/guide-unlock-flash-root-pixel-2-walleye-t3702417
twrp does not work on our phones anymore. therefore you can't flash it in the magisk manager. use the methode in the 1st post in the thread above. It works just fine.
Click to expand...
Click to collapse
Sorry, what post? The only thing I see in there about Magisk is, "Rooting with Magisk". I'm already rooted though, I just need to install magisk to my phone. I already have Magisk manager on my phone.
upperbladez said:
Sorry, what post? The only thing I see in there about Magisk is, "Rooting with Magisk". I'm already rooted though, I just need to install magisk to my phone. I already have Magisk manager on my phone.
Click to expand...
Click to collapse
I've been using the method described in the following thread for over a year and a half, and it still works with Q.
https://forum.xda-developers.com/pixel-2/how-to/guide-how-to-install-google-software-t3760033
Exactly how are you rooted if Magisk is not installed?
upperbladez said:
Sorry, what post? The only thing I see in there about Magisk is, "Rooting with Magisk". I'm already rooted though, I just need to install magisk to my phone. I already have Magisk manager on my phone.
Click to expand...
Click to collapse
having Magisk Manager installed doesn't root your phone. It interacts with the bits that need to be flashed to the kernel. This can be done inside Magisk Manager if TWRP works. Since it doesn't, you will need to either boot twrp via fastboot, push magisk.zip to your phone and flash it through twrp or you need to flash the file modified by Magisk Manager via the bootloader.
AS DESCRIBED IN THE REFERENCED THREAD
please just follow the instructions to the letter and you will be rooted.