Database Info

Rooting the Pixel after a failed attempt

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.

【HELP!】Installed a module in Magisk Download manager and now i'm f*****

Sup guys, i had this problem with the SafetyNet Check that always kept failing, done some tutorials here at the forum but none of them worked, so i gave up... yesterday i was searching for some modules at the download page in the Magisk Manager app and found a module that was supposed to correct SafatyNet problema, after that installation my Magisk don't want to open anymore, all my modules still installed but i can't open the app anymore, i rooted my cellphone without TWRP so i can't use it to manage the dependencies of the app... any suggestion?
obs.: I'm not using TWRP cuz i just keep having a problem at the installation, i'm runnig the last version of the Android Pie OS (Beta 3)

You could temporarily boot into TWRP via ADB and a PC and flash the uninstaller.

DiGtal said:
You could temporarily boot into TWRP via ADB and a PC and flash the uninstaller.
Click to expand...
Click to collapse
He can boot it through fastboot, adb push the uninstaller and flash it.*
But isn't the safetynet fix just a build.prop tweak?
He can technically adb pull the build.prop, fix it and put it back in. Or just take a working build.prop from a fellow OB3 user ( me included ) and push it into the system through adb.

The Marionette said:
He can boot it through fastboot, adb push the uninstaller and flash it.*
But isn't the safetynet fix just a build.prop tweak?
He can technically adb pull the build.prop, fix it and put it back in. Or just take a working build.prop from a fellow OB3 user ( me included ) and push it into the system through adb.
Click to expand...
Click to collapse
I think the OP mentioned the problem they are having is from a Magisk module that is incompatible with the OP6. My recommendation, without TWRP on the phone, might be a Fastboot Rom to get your phone functional again.

tabletalker7 said:
I think the OP mentioned the problem they are having is from a Magisk module that is incompatible with the OP6. My recommendation, without TWRP on the phone, might be a Fastboot Rom to get your phone functional again.
Click to expand...
Click to collapse
I know that and the OP probably does too, but I guess they don't want to lose their current data?

The Marionette said:
I know that and the OP probably does too, but I guess they don't want to lose their current data?
Click to expand...
Click to collapse
I don't know if that can be helped at this point. That bad Magisk module may have made that decision for him

The Marionette said:
I know that and the OP probably does too, but I guess they don't want to lose their current data?
Click to expand...
Click to collapse
That's right, i know that i can fix this issue just installing the ROM again but i don't want to lose my data, i just want to delete a specific module from Magisk

s3nn4 said:
That's right, i know that i can fix this issue just installing the ROM again but i don't want to lose my data, i just want to delete a specific module from Magisk
Click to expand...
Click to collapse
restore stock boot.img. no root, no mods to load. fix it then reroot.

You don't need to restore. Follow this guide: https://forum.xda-developers.com/apps/magisk/module-core-mode-bootloop-solver-modules-t3817366
It's called CoreOnlyMode4Magisk and it's flashed through TWRP. Magisk modules are systemless and this module will fix your problem.

mdl054 said:
You don't need to restore. Follow this guide: https://forum.xda-developers.com/apps/magisk/module-core-mode-bootloop-solver-modules-t3817366
It's called CoreOnlyMode4Magisk and it's flashed through TWRP. Magisk modules are systemless and this module will fix your problem.
Click to expand...
Click to collapse
he does not have twrp installed, but your way would work as well. the choice is up to op then to make.
http://www.mediafire.com/file/5h1hzimcj1irbn5/stockboot.img stock boot.img for OB3

MrSteelX said:
he does not have twrp installed, but your way would work as well. the choice is up to op then to make.
http://www.mediafire.com/file/5h1hzimcj1irbn5/stockboot.img stock boot.img for OB3
Click to expand...
Click to collapse
Oh sorry I missed that part

You can use the modified boot.img with TWRP preinstalled from the OB3 thread:
https://forum.xda-developers.com/showpost.php?p=77390204&postcount=2

Just reflash OB3 from system updater and that will get rid of root and also keep your data. Then start over.
Sent from my OnePlus6 using XDA Labs

The Marionette said:
I know that and the OP probably does too, but I guess they don't want to lose their current data?
Click to expand...
Click to collapse
MrSteelX said:
he does not have twrp installed, but your way would work as well. the choice is up to op then to make.
http://www.mediafire.com/file/5h1hzimcj1irbn5/stockboot.img stock boot.img for OB3
Click to expand...
Click to collapse
Already fixed it, installed the last version of blu spark TWRP along with the Magisk 17.2, all perfect, had a problem with my OS at the beginning but just flashed again and did all the process to root, thanks for your help!

Next time don't be a twrp and use twrp

dgunn said:
Next time don't be a twrp and use twrp
Click to expand...
Click to collapse
The last update wouldn't let me install it, the Blu stuff made my day when I saw the compatible update

Bootloop on newest X.x.10 Update? No TWRP only Magisk

I installed the update like i normally did. Went into magisk and installed Magisk on the "After OTA" setting. Now it's boot looping. I'm NOT using TWRP. This is the first time this has happened. Normally I update the OTA, DONT RESET, install Magisk on OTA setting and reboot and it works fine. Anyway to fix this? It boots 90%, but once it gets to main screen RIGHT before it asks for my PIN, it goes to 'rebooting'. Do I need to wipe my phone and start over?

I'm not rooted but From my experience you have to delete modules folder in twrp

RISHI RAJ said:
I'm not rooted but From my experience you have to delete modules folder in twrp
Click to expand...
Click to collapse
I just wiped my phone and I'm going to start fresh. I should have done some reading before installing the new OTA. I just figured it was like the old ones. I was bootlooping so I was unable to disabled those AFTER the fact.
My fault at this point. I'll just start fresh and reinstall Magisk when I have time.

whitak3r said:
I just wiped my phone and I'm going to start fresh. I should have done some reading before installing the new OTA. I just figured it was like the old ones. I was bootlooping so I was unable to disabled those AFTER the fact.
My fault at this point. I'll just start fresh and reinstall Magisk when I have time.
Click to expand...
Click to collapse
Only disabling modules won't help,You have to delete the folder,Next time when you update

RISHI RAJ said:
Only disabling modules won't help,You have to delete the folder,Next time when you update
Click to expand...
Click to collapse
Thank you. I'll do that next time, would of saved me a bunch headache if I would of just read a little bit lol
I ended up cleaning my system and everything went back to stock root. So I updated magsik and magisk man. And it fixed everything. I'm in the processes of reinstalling all my stuff now though

For me, there is only one module causing problems - the OOS call recorder enabler.
I simply remove that module and reboot before starting the OTA and all was fine.

I have same problem here (bootloop). Removing the los call recorder module folder from TWRP file explorer (/data/adb/modules/folder_to_remove) worked!

Is this a bug of Magisk?

sulliwane said:
I have same problem here (bootloop). Removing the los call recorder module folder from TWRP file explorer (/data/adb/modules/folder_to_remove) worked!
Click to expand...
Click to collapse
Hi, can you use this command on adb shell? OnePlus 7T Pro doesn't have TWRP yet. Thanks.

sulliwane said:
I have same problem here (bootloop). Removing the los call recorder module folder from TWRP file explorer (/data/adb/modules/folder_to_remove) worked!
Click to expand...
Click to collapse
This. But the module clearly says REMOVE before attempting upgrade!
And like I suppose most people here - I also did not follow that instruction and ended up with a bootloop. lmao. :good:

If you have TWRP you can remove modules if you have a bootloop.

What did I do wrong during the update?

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.

No SIM detection after last update (June 2020). Anyone?

I'm facing no SIM card detection after last system update. Does it happened to any of you?
Oxygen OS 10.0.6.GM57BA
GM1900 (red Chinese version)
Magisk and Xposed

Me. Same model and system version here.

After trying some things today I find that uninstalling magisk solved the problem. Installing it back doesn't brick it again. I can remember that before upgrading it says that there will be a partition optimization so I can asume magisk interfere on it. Hope it helps someone.

carmeloamg said:
After trying some things today I find that uninstalling magisk solved the problem. Installing it back doesn't brick it again. I can remember that before upgrading it says that there will be a partition optimization so I can asume magisk interfere on it. Hope it helps someone.
Click to expand...
Click to collapse
Sorry, could you elaborate a bit on how you uninstalled Magisk and installed it back again? Does it require wiping my data? I'm kind of a noob.

For me it seems to be caused by a Magisk module called OxyMod. After uninstallation everything is back to normal.

For me it was a magisk call recording module that solved this issue.

staenk said:
Sorry, could you elaborate a bit on how you uninstalled Magisk and installed it back again? Does it require wiping my data? I'm kind of a noob.
Click to expand...
Click to collapse
Hi! I've just seen your reply and that you solved it. If you already have magisk installed, unistalling it won't make you loose data I'll explain the process at the end of the post.
tpunkttpunkt said:
For me it was a magisk call recording module that solved this issue.
Click to expand...
Click to collapse
I also had a call recording module for magisk so maybe this was causing the issue and uninstalling magisk solved it but was not necessary. Now the Magisk and that module are installed again causing no problem.
EDIT: I research about oxymod xposed module and find that it has also a call recording patch... everything suggests that enabled call recording was causing the after-update issue.
Now the notes about installing/unistalling magisk for @staenk (hidden to avoid huge post):
In case you have Magisk already installed, you just need to:
Already have adb/fastboot installed in your computer
Download the official Magisk uninstaller .zip from the original developer post.
Save it in your phone memory.
Then find a .img of TWRP that works for our device on android 10 (there's one developed by @mauronofrio )
Power off your phone and boot it into fastboot (volume down + power)
Plug your phone to your computer
Boot twrp using the following terminal command where twrp is the path to the twrp image you downloaded in your computer:
Code:
fastboot boot twrp.img
Click on keep read only when asked.
Use install zip to browse the Magisk uninstall .zip and install it.
You have uninstalled magisk, reboot to system normally.
To install magisk again, just download the latest magisk .zip and repeat the process.
If it is the first time you are installing Magisk the process require to first unlock bootloader, and this process will erase your data. Once unlocked it will remain until you lock it back again. You can relock bootloader after installing Magisk (not recommended from my point of view) and your phone will keep rooted but you won't be able to boot twrp again if something goes wrong, what could lead into you unlocking bootloader again and loosing your data in the process.
If you are too noob to understand the instructions means you should not mess with Magisk or whatever yet and need to read more about.

I also experienced the same issue which I fixed by uninstalling the Magisk Call Recording module.