I have Magisk installed and decided to try out some of the modules for it but could never get them to update it said on all that they would update on next reboot, well after several reboots nothing. I clicked on the little garbage can to delete and they wouldn't delete?? I ended up having to uninstall magisk to get rid of them and had to reinstall magisk to get root back.. Any one else have any problems with the modules??
blake .l said:
I have Magisk installed and decided to try out some of the modules for it but could never get them to update it said on all that they would update on next reboot, well after several reboots nothing. I clicked on the little garbage can to delete and they wouldn't delete?? I ended up having to uninstall magisk to get rid of them and had to reinstall magisk to get root back.. Any one else have any problems with the modules??
Click to expand...
Click to collapse
I had a similar problem. It took multiple reinstalls of magisk to get it working, hang in there you'll get it working. That's just one of the issues with how this phone handles many different things. T-Mobile has had to issue updates to fix updates and that has potential to turn people away from an otherwise great piece of hardware. Hang in there you'll figure this phone out.
Sent from my Moto Z (2) using XDA Labs
blake .l said:
I have Magisk installed and decided to try out some of the modules for it but could never get them to update it said on all that they would update on next reboot, well after several reboots nothing. I clicked on the little garbage can to delete and they wouldn't delete?? I ended up having to uninstall magisk to get rid of them and had to reinstall magisk to get root back.. Any one else have any problems with the modules??
Click to expand...
Click to collapse
Out of curiosity, did you go through the full TWRP installation, or just use it to boot and install Magisk?
dismembered3po said:
Out of curiosity, did you go through the full TWRP installation, or just use it to boot and install Magisk?
Click to expand...
Click to collapse
Did the full TWRP install them installed Magisk
Related
My original Pixel XL died completely with a hard brick, no power, no lights, nothing. The refurbished replacement arrived yesterday. It booted up in 7.1.2 and had an update notice to Oreo 8. I did that and was on OPR6 with another update notice to the September security patch. Even with my T-Mobile SIM installed, it installed OPR1 for Project Fi and Canada instead of OPR3. Is that normal?
None of my Play Store apps downloaded and installed. Is that normal or is it because I couldn't sync with my dead phone? Unfortunately all of my recent backups had been to the local SD card, so that is a lesson learned for next time.
I unlocked the bootloader and fastboot flashed OPR3 with no problems, but now my Play Store says it's uncertified. I tried clearing the Play Store data and rebooting, plus several other tips I found online, but nothing fixed it. Is that because of the unlocked bootloader and not being rooted? Rather than doing a factory reset and starting over, if I root with SuperSU and run suhide, will the Play Store be certified again?
Anyone?
It changed back to certified for me. I'm rooted with SuperSU and suhide. I cleared Playstore data, I blocked Playstore, Pay, etc. app's in suhide, then I hid SuperSU and suhide icons, Safetynet passed, and rebooted.
galaxys said:
It changed back to certified for me. I'm rooted with SuperSU and suhide. I cleared Playstore data, I blocked Playstore, Pay, etc. app's in suhide, then I hid SuperSU and suhide icons, Safetynet passed, and rebooted.
Click to expand...
Click to collapse
Thanks! I rooted with SuperSU, installed suhide, blocked Play Store, cleared Play Store data and then rebooting fixed it. I have seen that others have had to hide the SuperSU and suhide icons but I didn't have to on either my old phone or this replacement.
JimSmith94 said:
Thanks! I rooted with SuperSU, installed suhide, blocked Play Store, cleared Play Store data and then rebooting fixed it. I have seen that others have had to hide the SuperSU and suhide icons but I didn't have to on either my old phone or this replacement.
Click to expand...
Click to collapse
Did you require TWRP to root or is there a way to directly flash SuperSU and suhide from fastboot?
Zwitterion said:
Did you require TWRP to root or is there a way to directly flash SuperSU and suhide from fastboot?
Click to expand...
Click to collapse
I don't know if there's a way to root without TWRP. I used the bootable one for Oreo with:
fastboot boot twrp-3-1-pixel-bootable-mod.img
JimSmith94 said:
I don't know if there's a way to root without TWRP. I used the bootable one for Oreo with:
fastboot boot twrp-3-1-pixel-bootable-mod.img
Click to expand...
Click to collapse
Could you kindly provide a link to the Oreo compatible TWRP? Also what SuperSu zip did you use?
Thanks so much!!
Zwitterion said:
Could you kindly provide a link to the Oreo compatible TWRP? Also what SuperSu zip did you use?
Thanks so much!!
Click to expand...
Click to collapse
You really should be searching and reading for yourself before you try any of this, but here is the TWRP thread with download link: https://forum.xda-developers.com/pixel/development/mod-twrp-recovery-pixel-android-o-dp4-t3651896
I always use the newest SuperSU and suhide, which at the moment are SR4-SuperSU-v2.82-SR4-20170918204844.zip and UPDATE-suhide-v1.08-20170815171034.zip. I'll let you Google those yourself.
JimSmith94 said:
You really should be searching and reading for yourself before you try any of this, but here is the TWRP thread with download link: https://forum.xda-developers.com/pixel/development/mod-twrp-recovery-pixel-android-o-dp4-t3651896
I always use the newest SuperSU and suhide, which at the moment are SR4-SuperSU-v2.82-SR4-20170918204844.zip and UPDATE-suhide-v1.08-20170815171034.zip. I'll let you Google those yourself.
Click to expand...
Click to collapse
Thanks!
JimSmith94 said:
You really should be searching and reading for yourself before you try any of this, but here is the TWRP thread with download link: https://forum.xda-developers.com/pixel/development/mod-twrp-recovery-pixel-android-o-dp4-t3651896
I always use the newest SuperSU and suhide, which at the moment are SR4-SuperSU-v2.82-SR4-20170918204844.zip and UPDATE-suhide-v1.08-20170815171034.zip. I'll let you Google those yourself.
Click to expand...
Click to collapse
Did you let the phone boot once between application of SuperSu and Suhide?
Zwitterion said:
Did you let the phone boot once between application of SuperSu and Suhide?
Click to expand...
Click to collapse
Haven't you read the threads about all of this? The instructions say to boot in between so that's what I did.
JimSmith94 said:
Haven't you read the threads about all of this? The instructions say to boot in between so that's what I did.
Click to expand...
Click to collapse
I have, including the line where Chainfire notes that it may be beneficial to not boot between flashing of these packages depending on how TWRP behaves, which is why I asked you.
Hi all,
Good news is I get the "how to root" stuff. But one aspect remains a bit unclear.
I did search but I didn't find a clear answer. If I would clean flash a full update (signed flashable zip), do you loose TWRP and root?
If yes, is the only option to reinstall TWRP-recovery and reroot?
kr,
Jeroen
You wouldn't lose TWRP, but root might give you problems depending on what method you used to root.
Best to do a full unroot, flash update, then re-root.
xocomaox said:
You wouldn't lose TWRP, but root might give you problems depending on what method you used to root.
Best to do a full unroot, flash update, then re-root.
Click to expand...
Click to collapse
Method would be just flashing Su or Magisk from TWRP. A full unroot is the same as a clean flash I suppose?
Both SuperSU and Magisk have uninstall methods. I think Magisk has an uninstall zip you can flash.
xocomaox said:
Both SuperSU and Magisk have uninstall methods. I think Magisk has an uninstall zip you can flash.
Click to expand...
Click to collapse
Thanks for the clarification. Now the long wait for the parcel too arrive::fingers-crossed:
Jeroen1000 said:
Thanks for the clarification. Now the long wait for the parcel too arrive::fingers-crossed:
Click to expand...
Click to collapse
I just got mine. Already unlocked bootloader.. Flashing TWRP now.. Then I will flash the latest update to see how it goes.
Jeroen1000 said:
Thanks for the clarification. Now the long wait for the parcel too arrive::fingers-crossed:
Click to expand...
Click to collapse
Okay, so I had TWRP installed and no Magisk. I took the OTA through System Update screen...
I lost TWRP and gained stock recovery back. Everything else went fine. So I guess system update wipes TWRP! Oh, well. Easy fix.
Wait for OTA updates this is normal. You need full ROM flashable zips. For the 5 there was a topic in which they got posted. Don't know yet for the 5T. But as you say rerooting is hardly a chore
xocomaox said:
Both SuperSU and Magisk have uninstall methods. I think Magisk has an uninstall zip you can flash.
Click to expand...
Click to collapse
From the heck of it today I tried uninstalling magisk by flashing the uninstaller in twrp and through magisk manager in system. After both methods my phone wouldn't get past the OnePlus splash screen.
How can you get phone to boot after unrooting and restoring the stock boot image through Magisk?
Dazed No More said:
From the heck of it today I tried uninstalling magisk by flashing the uninstaller in twrp and through magisk manager in system. After both methods my phone wouldn't get past the OnePlus splash screen.
How can you get phone to boot after unrooting and restoring the stock boot image through Magisk?
Click to expand...
Click to collapse
Hmm, that is interesting. Try taking the OTA zip using the official method (but use TWRP file manager to move it in place).
Or just flash official system image. You can get it from this forum.
Losing TWRP
Help! Trying to install twrp. Able to flash, but after reboot, phone reverts back to original recovery. Also, while in twrp- was not able to do anything... Figure something to do with encryption? In twrp formatted data, then was able to back up... Thought it fixed the problem, but still reverting back to original.
Thanks.
I was using magisk so before update i uninstalled the magisk and checked for update it started immediately since then its stuck on downloading i did force stop for play services and google framework and checked again but nothing worked. However i did factory reset and then checked again this time also it stuck on downloading update. Does anyone know what is the issue ?
goti(0) said:
I was using magisk so before update i uninstalled the magisk and checked for update it started immediately since then its stuck on downloading i did force stop for play services and google framework and checked again but nothing worked. However i did factory reset and then checked again this time also it stuck on downloading update. Does anyone know what is the issue ?
Click to expand...
Click to collapse
There's really no reason to uninstall magisk before an update. Just let it update itself through the app. You should be able to just flash the magisk 16.0 zip in twrp to get things back to normal.
When you say update, you mean OTA or fastbooting the factory image?
Badger50 said:
There's really no reason to uninstall magisk before an update. Just let it update itself through the app. You should be able to just flash the magisk 16.0 zip in twrp to get things back to normal.
When you say update, you mean OTA or fastbooting the factory image?
Click to expand...
Click to collapse
OTA only
goti(0) said:
OTA only
Click to expand...
Click to collapse
Ah..gotchya. Yep, those can cause problems for sure with magisk. Did you try side loading the OTA zip, or consider learning fastboot?
goti(0) said:
OTA only
Click to expand...
Click to collapse
You probably got my issue lol did you flash a custom rom before flashing back stock or any mod that would give you the internal provider error pop up after every boot?
goti(0) said:
I was using magisk so before update i uninstalled the magisk and checked for update it started immediately since then its stuck on downloading i did force stop for play services and google framework and checked again but nothing worked. However i did factory reset and then checked again this time also it stuck on downloading update. Does anyone know what is the issue ?
Click to expand...
Click to collapse
No magisk installed here. Had the same issue of getting stuck at downloading. Factory reset and it worked. Need enough battery charge for it to work. Download was slow on a fast internet btw.
Hope it works fine for you soon
Sent from my Pixel 2 XL using Tapatalk
Badger50 said:
Ah..gotchya. Yep, those can cause problems for sure with magisk. Did you try side loading the OTA zip, or consider learning fastboot?
Click to expand...
Click to collapse
finally i did flash latest image using deuces script as factory reset did not solve the problem but i was wondering what may be the reason as i have never heard of this kind of issue so i posted if anyone else has the same problem.
Jiggs82 said:
You probably got my issue lol did you flash a custom rom before flashing back stock or any mod that would give you the internal provider error pop up after every boot?
Click to expand...
Click to collapse
no i am on stock+magisk since day 1 no rom at all.
X-jo said:
No magisk installed here. Had the same issue of getting stuck at downloading. Factory reset and it worked. Need enough battery charge for it to work. Download was slow on a fast internet btw.
Hope it works fine for you soon
ya i did that but i used deuces script so i can not tell that it will check the update correctly for next month security bulletin.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Everytime i try to install magisk I get a bootloop. Bootloop goes away again as soon as I use magisk uninstaller so it's definetly magisk.
Any idea how I can get round this, it's kinda annoying.
yusuo said:
Everytime i try to install magisk I get a bootloop. Bootloop goes away again as soon as I use magisk uninstaller so it's definetly magisk.
Any idea how I can get round this, it's kinda annoying.
Click to expand...
Click to collapse
I get this too and have not been able to figure it out. What year and month was your Pixel XL manufactured in? Are you using the March update?
Homeboy76 has been helping me troubleshoot my problem so maybe one of these set of steps could help you flash yours. I'm still trying to get mine to root.
https://forum.xda-developers.com/pixel-xl/how-to/guide-pixel-xl-android-9-0-pie-unlock-t3825866/post79177838#post79177838
i had the same problem as u. the fix for me was to update to the march pixel xl factory image and flash it with no wipe. delete -w so i keep all my existing data/apps etc and flash latest twrp and latest magisk v18.1 and no twrp bootloop. hope this helps
Hi, I was wondering if I could update magisk directly from the app ? my phone is obviously rooted but with stock recovery.
Or do I have to just ADB it ?
Also, is it better to just flash TWRP permanetly ?
Thanks
youssefkr said:
Hi, I was wondering if I could update magisk directly from the app ? my phone is obviously rooted but with stock recovery.
Or do I have to just ADB it ?
Also, is it better to just flash TWRP permanetly ?
Thanks
Click to expand...
Click to collapse
Interesting question, with an interesting answer. Maybe yes and maybe no! The P2XL is one of the most interesting devices in recent memory. Personally, I have updated magisk several times through magisk manager. Until the May update that is, at least for me. Magisk versions 19+ has bootlooped me every time, yet 18.1 works fine. Yet, there are several other users that have had zero problems with the latest twrp and magisk versions as well. So, who knows what your device will do. You don't need to necessarily install twrp, since you can temporarily fastboot into twrp, and then flash magisk, or you can adb it, it's your call. Just be prepared for a bootloop, or, it may work fine. Best of luck to you, and sorry for my ambiguous answer, but then again, that's how the P2XL is
Badger50 said:
Interesting question, with an interesting answer. Maybe yes and maybe no! The P2XL is one of the most interesting devices in recent memory. Personally, I have updated magisk several times through magisk manager. Until the May update that is, at least for me. Magisk versions 19+ has bootlooped me every time, yet 18.1 works fine. Yet, there are several other users that have had zero problems with the latest twrp and magisk versions as well. So, who knows what your device will do. You don't need to necessarily install twrp, since you can temporarily fastboot into twrp, and then flash magisk, or you can adb it, it's your call. Just be prepared for a bootloop, or, it may work fine. Best of luck to you, and sorry for my ambiguous answer, but then again, that's how the P2XL is
Click to expand...
Click to collapse
Now I'm more confused lol
Thanks for the answer though
youssefkr said:
Now I'm more confused lol
Thanks for the answer though
Click to expand...
Click to collapse
Makes 2 of us. Heck, if I were you, I'd just let magisk manager update itself to the latest versions and see what happens. At worst, you'd, have to fastboot into twrp, flash the magisk uninstaller, then flash 18.1 again to acquire root again. Only bad thing is that you'd have to instal your modules again.
Badger50 said:
Makes 2 of us. Heck, if I were you, I'd just let magisk manager update itself to the latest versions and see what happens. At worst, you'd, have to fastboot into twrp, flash the magisk uninstaller, then flash 18.1 again to acquire root again. Only bad thing is that you'd have to instal your modules again.
Click to expand...
Click to collapse
So I just updated via the app (19.2) and it went well, not bootloops or whatsoever
youssefkr said:
So I just updated via the app (19.2) and it went well, not bootloops or whatsoever
Click to expand...
Click to collapse
Congrats! Lucky duck. This issue is still perplexing me. The P2XL is just like a box of chocolates..."Ya never know what your gonna get" :laugh:
I'm having the same issue in beta Q 3.. everything I try to update it through magisk, it will not install at all.
Just get a error that reads, " app did not install".
Just updated yesterday to 19.2 through the manager yesterday. Running Q Beta 3. No problems.