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.

/Vendor won't unmount in recovery

Hi guys,
Just looking for some information, or maybe we could get a successful discussion on this matter to help others who might come across this issue.
I was getting a bootloop after flashing the latest Dolby Atmos build via Magisk Manager. I'm on Magisk 17.1
I could successfully reach recovery and I could successfully restore /system, /data and /boot from an earlier back up. But I couldn't restore /vendor, because TWRP could not unmount it.
I know that this is fixable via RUU (which is what I did in the end), though i'd like to understand what is happening and how to fix it without RUU (if it is even possible at all).
As mentioned in other posts, uninstalling Magisk is impossible without /Vendor being unmounted.
Any help and information is appreciated. I'll continue investigating to see if there's any further info for me to find.

Kyuubi10 said:
As mentioned in other posts, uninstalling Magisk is impossible without /Vendor being unmounted.
Click to expand...
Click to collapse
That's simply wrong. You should have installed Magisk using the Magisk Manager and a stock boot image in your internal SD card, by using the patch boot image method in Magisk Manager and flash it afterwards. Thus uninstalling Magisk would simply be to flash an unpatched stock boot image.
Sent from my HTC U12+ using XDA Labs

5m4r7ph0n36uru said:
That's simply wrong. You should have installed Magisk using the Magisk Manager and a stock boot image in your internal SD card, by using the patch boot image method in Magisk Manager and flash it afterwards. Thus uninstalling Magisk would simply be to flash an unpatched stock boot image.
Click to expand...
Click to collapse
No, that isn't an "uninstall"... What you described is an overwrite.
Flashing RUU does the exact same thing.
I'm talking about flashing the magisk uninstaller zip. - that is a true uninstall.
Maybe were getting semantics wrong, should we start defining the meaning of "uninstall" from now on?

Kyuubi10 said:
No, that isn't an "uninstall"... What you described is an overwrite.
Flashing RUU does the exact same thing.
I'm talking about flashing the magisk uninstaller zip. - that is a true uninstall.
Maybe were getting semantics wrong, should we start defining the meaning of "uninstall" from now on?
Click to expand...
Click to collapse
Man I'm not stupid and know exactly that it's "just" an overwrite.
But if you used the patch boot image method in Magisk Manager, and flashed the patched boot to "install" Magisk, you could uninstall all modules in Magisk Mananger and afterwards flash the stock boot and you'll be done uninstalling Magisk anyway. In this very case the uninstaller isn't needed at all.
Learn about the different ways on how to install and uninstall Magisk and you'll see that I'm right, as I clearly defined the installation method as well. Maybe you still didn't understand the different ways of how to install and uninstall Magisk.
If you flashed Magisk through TWRP yeah you're done and may have to flash a RUU. But anyone who read up on
this very topic and knew all basics of how Magisk and rooting on Treble A/B devices currently works would have known that one prior to rooting as well. It's stated in a lot of threads and happens on other devices as well, that Magisk isn't allowed to mount and alter vendor.
Sent from my HTC U12+ using XDA Labs

5m4r7ph0n36uru said:
Man I'm not stupid and know exactly that it's "just" an overwrite.
But if you used the patch boot image method in Magisk Manager, and flashed the patched boot to "install" Magisk, you could uninstall all modules in Magisk Mananger and afterwards flash the stock boot and you'll be done uninstalling Magisk anyway. In this very case the uninstaller isn't needed at all.
Learn about the different ways on how to install and uninstall Magisk and you'll see that I'm right, as I clearly defined the installation method as well. Maybe you still didn't understand the different ways of how to install and uninstall Magisk.
If you flashed Magisk through TWRP yeah you're done and may have to flash a RUU. But anyone who read up on
this very topic and knew all basics of how Magisk and rooting on Treble A/B devices currently works would have known that one prior to rooting as well. It's stated in a lot of threads and happens on other devices as well, that Magisk isn't allowed to mount and alter vendor.
Click to expand...
Click to collapse
Brilliant! You should have started with this.
I'm looking for knowledge and information.
To be given a solution which I'm already aware of is useless to me. This thread was my way of asking for information... And telling me "i'm simply wrong" and then using wrong semantics for your explanation is a sure fire way of getting someone to call you stupid (though I never said it, and you simply implied it. Very good victim complex there).
In my daily job semantics are VERY important... So I absolutely WILL point out words used in the wrong context when I come across them.
It's just what I'm used to.
So next time choose your words very carefully not to confuse myself or others who come across this post.
Uninstall is a script designed to "uninstall" something... If I overwrite the entire partition manually, then it's not an uninstall.
Now that we have that out of the way, lets move on to building information that the community can make use of.
1. Magisk no longer can mess with a vendor partition. (Is this truly across the board? On all A/B devices? Can you post threads with more information please?)
2. You advise that the best way to install Magisk on A/B devices is via flashing patched boot... This is very interesting.
3. From your signature I noticed you've got different set ups in your A/B partitions.
I like that, do you have a guide where I can learn more?

5m4r7ph0n36uru said:
Man I'm not stupid and know exactly that it's "just" an overwrite.
But if you used the patch boot image method in Magisk Manager, and flashed the patched boot to "install" Magisk, you could uninstall all modules in Magisk Mananger and afterwards flash the stock boot and you'll be done uninstalling Magisk anyway. In this very case the uninstaller isn't needed at all.
Learn about the different ways on how to install and uninstall Magisk and you'll see that I'm right, as I clearly defined the installation method as well. Maybe you still didn't understand the different ways of how to install and uninstall Magisk.
If you flashed Magisk through TWRP yeah you're done and may have to flash a RUU. But anyone who read up on
this very topic and knew all basics of how Magisk and rooting on Treble A/B devices currently works would have known that one prior to rooting as well. It's stated in a lot of threads and happens on other devices as well, that Magisk isn't allowed to mount and alter vendor.
Sent from my HTC U12+ using XDA Labs
Click to expand...
Click to collapse
Also additionally, why can't TWRP mount/unmount Vendor?
Is that something that's already been discussed prior as well?
because that's the bigger problem I had.

Hi,
It would be nice to find how to format the partition 'vendor' and reinstall via TWRP? it's a problem for a complete custom rom that includes the 'vendor' part!
PS: With Super-R kitchen 'vendor' does not flash !!

Alan-B said:
Hi,
It would be nice to find how to format the partition 'vendor' and reinstall via TWRP? it's a problem for a complete custom rom that includes the 'vendor' part!
PS: With Super-R kitchen 'vendor' does not flash !!
Click to expand...
Click to collapse
As far as I've experienced after a fresh RUU i can flash vendor.
But not after the first boot.

SOLVED: Flashed Magisk zip from TWRP but no root

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!

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.

Rooted Redmagic 3S with Magisk, xposed (edexposed) created bootloop

Folks,
I had rooted my RM 3S with Magisk which worked fine for couple of days until I installed Edxposed zip via Magisk. Device is in boot loop.
Can access recovery..
Any suggestions or help greatly appreciated. Please help.
Device from India running on 1.16 (I guess)
Aru

B01070 said:
Folks,
I had rooted my RM 3S with Magisk which worked fine for couple of days until I installed Edxposed zip via Magisk. Device is in boot loop.
Can access recovery..
Any suggestions or help greatly appreciated. Please help.
Device from India running on 1.16 (I guess)
Aru
Click to expand...
Click to collapse
Can you access internal memory from recovery on comp? If so, load the latest update.zip from rm on root of memory, then in recovery, hit install update

suzook said:
Can you access internal memory from recovery on comp? If so, load the latest update.zip from rm on root of memory, then in recovery, hit install update
Click to expand...
Click to collapse
Thanks suzook for your quick response. I don't have access to comp, but I doubt I will have access to internal storage. However, can I connect an otg with the zip and install via Recovery Vol up + power, I see that there is an option tk do it?
Any advise?
Aru

Also I only have an option to install from. Otg and not from internal storage..

B01070 said:
Thanks suzook for your quick response. I don't have access to comp, but I doubt I will have access to internal storage. However, can I connect an otg with the zip and install via Recovery Vol up + power, I see that there is an option tk do it?
Any advise?
Aru
Click to expand...
Click to collapse
That will work
Do yourself a favor, and install twrp, so you can restore a backup incase of a bootloop

suzook said:
That will work
Do yourself a favor, and install twrp, so you can restore a backup incase of a bootloop
Click to expand...
Click to collapse
It's mid night in here.. Will try morning and will keep you informed. Thanks.
I have not seen twrp for 3s and was skeptical.. But looks like I need it...
Aru

B01070 said:
It's mid night in here.. Will try morning and will keep you informed. Thanks.
I have not seen twrp for 3s and was skeptical.. But looks like I need it...
Aru
Click to expand...
Click to collapse
The twrp for the rm3 here, works fine. Been using it for 3 days.

suzook said:
The twrp for the rm3 here, works fine. Been using it for 3 days.
Click to expand...
Click to collapse
Can you please help me with the twrp link? It is missing in your reply.
Aru

B01070 said:
Can you please help me with the twrp link? It is missing in your reply.
Aru
Click to expand...
Click to collapse
Link....LOL, its right here, in the rm3 dev thread
https://forum.xda-developers.com/red-magic-3/development/recovery-unofficial-twrp-nubia-red-t3962482

suzook said:
Link....LOL, its right here, in the rm3 dev thread
https://forum.xda-developers.com/red-magic-3/development/recovery-unofficial-twrp-nubia-red-t3962482
Click to expand...
Click to collapse
Thanks suzook... I now got back access to my phone.. Obviously, lost root access... Will install the patched boot img... Post that will install twrp..
Finally, still curious why Edxposed caused bootloop..
Aru

B01070 said:
Thanks suzook... I now got back access to my phone.. Obviously, lost root access... Will install the patched boot img... Post that will install twrp..
Finally, still curious why Edxposed caused bootloop..
Aru
Click to expand...
Click to collapse
suzook said:
Link....LOL, its right here, in the rm3 dev thread
https://forum.xda-developers.com/red-magic-3/development/recovery-unofficial-twrp-nubia-red-t3962482
Click to expand...
Click to collapse
Though I got access to my phone, I am not able to obtain root... I install the patched img through fastboot, but end up in bootloop..
I believe the EdExposed module that I installed in Magisk is the culprit.. I tried uninstalling and reinstalling Magisk Manager.. Same bootloop issue..
Any idea on how to resolve this issue.. Cheers!
Aru

B01070 said:
Though I got access to my phone, I am not able to obtain root... I install the patched img through fastboot, but end up in bootloop..
I believe the EdExposed module that I installed in Magisk is the culprit.. I tried uninstalling and reinstalling Magisk Manager.. Same bootloop issue..
Any idea on how to resolve this issue.. Cheers!
Aru
Click to expand...
Click to collapse
Module installed in Magisk was the reason for bootloop.. Once after acquiring root, when the phone is in bootloop, entering the below command from computer will remove all modules in Magisk...
adb wait-for-device shell magisk --remove-modules
Hope this helps someone in need..
Aru

suzook said:
Link....LOL, its right here, in the rm3 dev thread
https://forum.xda-developers.com/red-magic-3/development/recovery-unofficial-twrp-nubia-red-t3962482
Click to expand...
Click to collapse
suzook, how did you install twrp? I tried to install with the below commands, commands executed successfully, not no TWRP recovery.. Any thing did I miss?
adb devices
adb reboot bootloader
fastboot flash recovery twrp.img
fastboot reboot
Aru

B01070 said:
suzook, how did you install twrp? I tried to install with the below commands, commands executed successfully, not no TWRP recovery.. Any thing did I miss?
adb devices
adb reboot bootloader
fastboot flash recovery twrp.img
fastboot reboot
Aru
Click to expand...
Click to collapse
I have major issues....reboot to twrp, as soon as you flash it...then flash magisk to keep it flashed......MY Rm3s is F'd.

suzook said:
I have major issues....reboot to twrp, as soon as you flash it...then flash magisk to keep it flashed......MY Rm3s is F'd.
Click to expand...
Click to collapse
I can't reboot to twrp.. I go only into stock recovery.. Don't know if it good or bad.. For now, everything is in order.. Hopefully nothing would go wrong.. I restarted atleast dozen times...
Aru

some magisk modules gave me bootloop many times, i used twrp file manager to remove xxxx
location is data/adb/modules/xxxx

Is anyone running xposed modules? I see this "Xposed modules with Taichi" and edxposed which caused you to bootloop. I guess i can just backup with TWRP and try it...
I mainly want to remove all ads for now.
Any recommendations for magisk/xposed modules?

crusnikmachine said:
Is anyone running xposed modules? I see this "Xposed modules with Taichi" and edxposed which caused you to bootloop. I guess i can just backup with TWRP and try it...
I mainly want to remove all ads for now.
Any recommendations for magisk/xposed modules?
Click to expand...
Click to collapse
I don't have an answer to your question but I wanted to ask you about your rooting process. When I flashed either twrp or installed magisk I lost wifi connectivity. Logcat confirms something's going on. Have you run into this by any chance?

I was worried about installing edxposed after reading this thread and a few others, but I went ahead and went on with the install and it works for what wanted. Granted I don't install many modules I only use xinsta...
I installed the riru core and riru edxposed in magisk. At first restart the edxposed manager said it was installed but not activated. I went ahead and installed a edXposed module, ignoring the notification that edXposed framework was not active but installed(also in settings check the setting for "Skip status check"), activated my module and restarted. Later the edxposed manager would say edxposed framework is active and my module works.
As for wifi not working, I had ran into that problem as well, only because I skipped the part in the root/twrp guide for the rm3 about downloading the firmware, extracting the boot.img, having magisk patch it, then reflashing the patched boot image with adb. I did just that and wifi works. I have yet to have a bootloop problem or a need for the rm3s "unbrick tool." ?
Only issue im having is cellular connection, but that is probably due to this phone lacking band 13 on Verizon.

B01070 said:
Folks,
I had rooted my RM 3S with Magisk which worked fine for couple of days until I installed Edxposed zip via Magisk. Device is in boot loop.
Can access recovery..
Any suggestions or help greatly appreciated. Please help.
Device from India running on 1.16 (I guess)
Aru
Click to expand...
Click to collapse
The same thing happened to me, I had to do the following:
1-download official filmware (NX629J-update)
2-once loaded unzip using winrar or 7 zip
3-search through the folders and take out the recovery.img file and flash it through adb
3-copy filmware at the root of a USB and look for a USB OTG
4-go to recovery and install the filmware the first time it will not boot
Restart recovery again and perform wipe data and cache. I hope it serves you greetings.