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
Related
So last night I installed the November 5, 2017 security patch on my Pixel XL running Google's 8.0.0 ROM. I did have Magisk installed at the time and this is what I did:
Uninstall Magisk from Magisk Manager
Start update and wait for step 2
Go back to Magisk Manager and install in the OTA slot with force encrypt disabled
Reboot
This caused a boot loop, figuring that the Magisk flash was just bad I downloaded "marlin-opr3.170623.013" from Google and flashed the boot image in there. This fixed the bootloop but prevented my phone from passing SafteyNet, and I found that there was an update notification saying that the update failed. I attempted it again and it would not install at all.
So I downloaded the OTA package from Google and flashed as there instructions say.
Still not passing.
I then removed the -w flag from flash-all.bat to keep my data and ran that to flash my device with the factory image.
Still not passing.
What should I do about this? I can not manage to get my phone to pass SaftetyNet and I want to keep all of my data. When I had my Nexus 6p I would just reflash the system stuff with TWRP, but since TWRP does not work that is not an option here. (I also used to use a custom ROM, but don't now because TWRP is broken)
gudenau said:
So last night I installed the November 5, 2017 security patch on my Pixel XL running Google's 8.0.0 ROM. I did have Magisk installed at the time and this is what I did:
Uninstall Magisk from Magisk Manager
Start update and wait for step 2
Go back to Magisk Manager and install in the OTA slot with force encrypt disabled
Reboot
This caused a boot loop, figuring that the Magisk flash was just bad I downloaded "marlin-opr3.170623.013" from Google and flashed the boot image in there. This fixed the bootloop but prevented my phone from passing SafteyNet, and I found that there was an update notification saying that the update failed. I attempted it again and it would not install at all.
So I downloaded the OTA package from Google and flashed as there instructions say.
Still not passing.
I then removed the -w flag from flash-all.bat to keep my data and ran that to flash my device with the factory image.
Still not passing.
What should I do about this? I can not manage to get my phone to pass SaftetyNet and I want to keep all of my data. When I had my Nexus 6p I would just reflash the system stuff with TWRP, but since TWRP does not work that is not an option here. (I also used to use a custom ROM, but don't now because TWRP is broken)
Click to expand...
Click to collapse
It sounds like it's not passing after you flashed the image because you are unlocked. If you want to pass safetynet with an unlocked bootloader, you need to modify the kernel (or use one that is already modified).
Like this one: https://forum.xda-developers.com/pi...rnel-stock-kernel-safetynet-patch-dm-t3684405
mwalt2 said:
It sounds like it's not passing after you flashed the image because you are unlocked. If you want to pass safetynet with an unlocked bootloader, you need to modify the kernel (or use one that is already modified).
Like this one: https://forum.xda-developers.com/pi...rnel-stock-kernel-safetynet-patch-dm-t3684405
Click to expand...
Click to collapse
Strange, I didn't have to use a custom kernel before this patch. I guess Google did something.
gudenau said:
Strange, I didn't have to use a custom kernel before this patch. I guess Google did something.
Click to expand...
Click to collapse
I believe Magisk was hiding it for you. If I understand where you are at now Magisk is gone right?
TonikJDK said:
I believe Magisk was hiding it for you. If I understand where you are at now Magisk is gone right?
Click to expand...
Click to collapse
It passed before without Magisk. The latest update did something.
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 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
Can someone help me with directions on how to install Magisk on a Pixel XL running dp3
Just fastboot boot TWRP image and install latest Magisk v16.4 through TWRP.
That's all.
Sent from my Google Pixel XL using XDA Labs
mr-tical said:
Just fastboot boot TWRP image and install latest Magisk v16.4 through TWRP.
That's all.
Click to expand...
Click to collapse
Thanks for the information, that about what I usually do. Although I would usually use Magisk uninstall first. I'll give it a go tomorrow.
Thanks
There is a thread for this with really good instructions in the News,Guides,etc,etc.. section called "How to root Android P". And honestly from what I've seen and experienced, it can take several times of trying before it actually sticks. Make sure you make a backup in TWRP first cuz it can bootloop on you or stick on the boot animation screen. Some have only had luck doing a complete reinstall of Android P dp3 using the "Flash-all" from dp3. Im on the OTA and tried several times during dp1 and dp2 with no luck. But for the hell of it I tried flashing Magisk 16.3 zip in TWRP yesterday on the OTA of dp3 and it went through. It's even surviving reboots. So who knows the proper way. I think it's hit or miss sometimes. Lmao. Good luck.
MAKE A BACKUP
fiverings said:
Can someone help me with directions on how to install Magisk on a Pixel XL running dp3
Click to expand...
Click to collapse
I installed dp3 using flash-all.bat
Then booted it. Didn't set any security Once at the home screen I rebooted to the bootloader. Then @ a command prompt on the PC:
flashboot boot twrp 3.2.1.img - https://dl.twrp.me/marlin/
Then installed twrpv3.2.1.ziphttps://dl.twrp.me/marlin/
Then rebooted to recovery
then installed Magisk v16.4- https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589/page349
reboot to system
rooted. Passing safetynet.
What the title says but here's the backstory for me...
Back in January, I upgraded my OP6 to OxygenOS 10/Android 10... And had flash a patched boot img with Magisk and maybe sideload boot into TWRP to install it. Ended up soft-bricking my phone :crying: but managed to reflash OOS 9 via native/bios bootloader? Lost all data though.... And probably spent a whole day trying to fix it and hoping I didn't have to buy a new phone...
Also TWRP did say back on January it's hard for them to support Android 10 because of some boot order change? (Maybe I did end up flashing it but when I tried to boot into recovery, it didn't load... Loaded the default OP recovery instead.)
But I basically want to make sure I can avoid all this again or at least have all steps when I flash LOS 17.1 instead of trial and error... And probably screwing up again...
allanx2000 said:
What the title says but here's the backstory for me...
Back in January, I upgraded my OP6 to OxygenOS 10/Android 10... And had flash a patched boot img with Magisk and maybe sideload boot into TWRP to install it. Ended up soft-bricking my phone :crying: but managed to reflash OOS 9 via native/bios bootloader? Lost all data though.... And probably spent a whole day trying to fix it and hoping I didn't have to buy a new phone...
Also TWRP did say back on January it's hard for them to support Android 10 because of some boot order change? (Maybe I did end up flashing it but when I tried to boot into recovery, it didn't load... Loaded the default OP recovery instead.)
But I basically want to make sure I can avoid all this again or at least have all steps when I flash LOS 17.1 instead of trial and error... And probably screwing up again...
Click to expand...
Click to collapse
Follow your guide
https://wiki.lineageos.org/devices/enchilada/
And ask in irc/discord #lineageos if something fails
Thanks but the guide doesn't mention installing TWRP, Magisk, or OpenGApps. The last 2 always need to be flash from Recovery or can you do that with Lineage Recovery now?
Was thinking asking here would be better as others will/have wondered the same thing. (Can't add the TWRP blog link)
But thanks for the Discord, guess will try there and just post a guide when I do do it... which won't be until all this Covid gets fixed and I can go back to my apt...
allanx2000 said:
Thanks but the guide doesn't mention installing TWRP, Magisk, or OpenGApps. The last 2 always need to be flash from Recovery or can you do that with Lineage Recovery now?
Was thinking asking here would be better as others will/have wondered the same thing. (Can't add the TWRP blog link)
But thanks for the Discord, guess will try there and just post a guide when I do do it... which won't be until all this Covid gets fixed and I can go back to my apt...
Click to expand...
Click to collapse
Read you guide:
Optionally): If you want to install any additional add-ons, click Advanced, then Reboot to Recovery, then when your device reboots, click Apply Update, then Apply from ADB, then adb sideload filename.zip those packages in sequence.
info_outline
Note: If you want Google Apps on your device, you must follow this step before booting into LineageOS for the first time!
/end quote
Magisk can be flashed in a later session
In discord the first thing they will ask is: "did you follow the guide?"