Phone will only boot to recovery after flashing TWRP? - Google Pixel XL Questions & Answers

Hey all, so this is a strange issue. I've tried this 3 times, on 8.0, 8.1 Jan security patch, and 8.1 March security patch. Booting to TWRP via fastboot works just fine, but after flashing it via ZIP within TWRP and rebooting, the phone will only boot to TWRP. Even flashing a stock boot.img and/or dirty flashing the stock image did not fix the issue and every time I had to do a clean install of the stock image. Any ideas why this is going on?

Have you tried installing Magisk after it boots back into TWRP?

sliding_billy said:
Have you tried installing Magisk after it boots back into TWRP?
Click to expand...
Click to collapse
Absolutely. It will patch the Boot Img.

Mikkey81 said:
Absolutely. It will patch the Boot Img.
Click to expand...
Click to collapse
hooligan33_3 said:
Hey all, so this is a strange issue. I've tried this 3 times, on 8.0, 8.1 Jan security patch, and 8.1 March security patch. Booting to TWRP via fastboot works just fine, but after flashing it via ZIP within TWRP and rebooting, the phone will only boot to TWRP. Even flashing a stock boot.img and/or dirty flashing the stock image did not fix the issue and every time I had to do a clean install of the stock image. Any ideas why this is going on?
Click to expand...
Click to collapse
Sorry, I meant to quote you when I suggested installing Magisk since it will patch boot.img.

Hello, this happened to me too after I uninstalled Magisk. I just reinstalled it and wiped the phone (just to be sure) and it works now.

stepedes said:
Hello, this happened to me too after I uninstalled Magisk. I just reinstalled it and wiped the phone (just to be sure) and it works now.
Click to expand...
Click to collapse
Are you trying to flash Magisk in fastboot or through TWRP?

In TWRP.
I'm a noob in all this, glad I didn't brick it. ?

it just happened to me now, I read one of the posts saying flash Magisk again and it worked.
aside: can someone tell me briefly who phones now having slot A and B? everytime i reboot twrp, i see option to decide which slot. I did choose slot B once and the phone never booted up. i'm little bit confused. and everytime twrp boots in, it asks me to draw my security pattern for decryption, is that OK? thx

mohawahba said:
it just happened to me now, I read one of the posts saying flash Magisk again and it worked.
aside: can someone tell me briefly who phones now having slot A and B? everytime i reboot twrp, i see option to decide which slot. I did choose slot B once and the phone never booted up. i'm little bit confused. and everytime twrp boots in, it asks me to draw my security pattern for decryption, is that OK? thx
Click to expand...
Click to collapse
Are you using twrp-pixel-installer-marlin-3.2.3-1.zip and twrp-3.2.3-1-marlin.img on your Pixel XL?
twrp should not be giving you an option to choose
a slot nor draw a security pattern for decryption.
look at this guide: [Guide] Pixel XL Android 9.0 (Pie) Unlock/Root/Install Images/Kernels/Recovery + by Homeboy76

Homeboy76 said:
Are you using twrp-pixel-installer-marlin-3.2.3-1.zip and twrp-3.2.3-1-marlin.img on your Pixel XL?
twrp should not be giving you an option to choose
a slot nor draw a security pattern for decryption.
look at this guide: [Guide] Pixel XL Android 9.0 (Pie) Unlock/Root/Install Images/Kernels/Recovery + by Homeboy76
Click to expand...
Click to collapse
I am actually sailfish .. will look into the link. Thanks

mohawahba said:
I am actually sailfish .. will look into the link. Thanks
Click to expand...
Click to collapse
Try the Pixel forum
TWRP for sailfish
- twrp-pixel-installer-sailfish-3.2.3-1.zip
- twrp-3.2.3-1-sailfish.img

Related

How to Root Using SuperSU and TWRP on Oreo OPR6 Official Release

After a bit of trial and error, I managed to find a combination of files and actions that allowed me to successfully root my 64GB Pixel C on 8.0.0 by installing SuperSU via TWRP.
Steps:
Perform a clean installation of the official release, found here
Use the unofficial 3.0.0 TWRP release found in this thread (direct download link here) and boot to recovery ("fastboot boot [TWRP filename].img") - the latest official 3.1.1 TWRP did not work, either via flashing or booting
ADB sideload SuperSU 2.82SR3 found in this thread (direct download link here)
Hope this helps!
Stuck at TWRP after
Flashed the TWRP from the link and side loaded the SuperSU, now my Pixel C is stuck at TWRP on reboot, any idea ?
Jeff Z. said:
Flashed the TWRP from the link and side loaded the SuperSU, now my Pixel C is stuck at TWRP on reboot, any idea ?
Click to expand...
Click to collapse
The only thing I can think of is to reflash the stock recovery using the downloaded factory image. Seems like it was flashed, not simply booted into TWRP.
Sent from my Pixel XL using Tapatalk
MadManMoon said:
The only thing I can think of is to reflash the stock recovery using the downloaded factory image. Seems like it was flashed, not simply booted into TWRP.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Thanks. My problem was my pixel kept booting to TWRP even selecting to boot the system, kind of strange. I think I missed your first step, the pad was OTA updated to 8.0 from 8.0 Beta release. I will try again with flash the factory image of 8.0 first.
Anyone else able to root their pixel c tablet on Oreo with success? I'm thinking about trying it with the original posters guide. Just thought I'd see who else has been able to make this work.
NitroSS said:
Anyone else able to root their pixel c tablet on Oreo with success? I'm thinking about trying it with the original posters guide. Just thought I'd see who else has been able to make this work.
Click to expand...
Click to collapse
Still works for me as of the September 2017 update. About to try it again with the October update.
It's driving me absolutely mad. I just got a brand new Pixel C today. It's updated to the latest Oreo but nothing else has been installed yet. I unlocked the bootloader and copied the SuperSU zip file onto the device via USB file transfer from my PC, then I set up a password. I'm booting (not flashing) TWRP because all I want is root.
When I'm prompted for a password in TWRP I'm told it's invalid. I also tried "default_password" and that's invalid, too. I looked all over for a solution and found a modified TWRP that doesn't prompt for a password but it won't decrypt the internal storage.
I'm really pulling my hair out here. I can't figure out why it's working for some people and not others.
CatThief said:
It's driving me absolutely mad. I just got a brand new Pixel C today. It's updated to the latest Oreo but nothing else has been installed yet. I unlocked the bootloader and copied the SuperSU zip file onto the device via USB file transfer from my PC, then I set up a password. I'm booting (not flashing) TWRP because all I want is root.
When I'm prompted for a password in TWRP I'm told it's invalid. I also tried "default_password" and that's invalid, too. I looked all over for a solution and found a modified TWRP that doesn't prompt for a password but it won't decrypt the internal storage.
I'm really pulling my hair out here. I can't figure out why it's working for some people and not others.
Click to expand...
Click to collapse
Try format userdata, then boot straight into twrp
Command is "fastboot format userdata"
You also have to flash SuperSU while in twrp to stop the tablet from encrypting again.
Huffy1 said:
Try format userdata, then boot straight into twrp
Command is "fastboot format userdata"
You also have to flash SuperSU while in twrp to stop the tablet from encrypting again.
Click to expand...
Click to collapse
I'm confused about "stop the tablet from encrypting again". I know TWRP needs to decrypt the data partition to access it, but are you saying encryption won't be re-enabled when I reboot the system? I had to ask because it sounds strange that installing the SuperSU zip would mess with encryption.
CatThief said:
I'm confused about "stop the tablet from encrypting again". I know TWRP needs to decrypt the data partition to access it, but are you saying encryption won't be re-enabled when I reboot the system? I had to ask because it sounds strange that installing the SuperSU zip would mess with encryption.
Click to expand...
Click to collapse
If everything goes to plan yes.
You can encrypt again if you wish through settings once the tablet is booted up
Huffy1 said:
If everything goes to plan yes.
You can encrypt again if you wish through settings once the tablet is booted up
Click to expand...
Click to collapse
Does this mean when I flash the factory images for the monthly updates and need to root the device again that I'll be wiping all userdata each time?
CatThief said:
Does this mean when I flash the factory images for the monthly updates and need to root the device again that I'll be wiping all userdata each time?
Click to expand...
Click to collapse
No just use flashfire to update and keep root, it won't encrypt the tablet. You can still boot official twrp as well after using flashfire to update as your tablet shouldn't encrypt.
Huffy1 said:
No just use flashfire to update and keep root, it won't encrypt the tablet. You can still boot official twrp as well after using flashfire to update as your tablet shouldn't encrypt.
Click to expand...
Click to collapse
Is removing encryption something everyone is doing, or is it just a workaround for the people who can't get TWRP to work? I never ran into anything like this before.
CatThief said:
Is removing encryption something everyone is doing, or is it just a workaround for the people who can't get TWRP to work? I never ran into anything like this before.
Click to expand...
Click to collapse
Use FDE then and it reportedly works.
Huffy1 said:
Use FDE then and it reportedly works.
Click to expand...
Click to collapse
Just curious though, is this a standard prerequisite for using TWRP and rooting *all* Pixel C devices?
CatThief said:
Just curious though, is this a standard prerequisite for using TWRP and rooting *all* Pixel C devices?
Click to expand...
Click to collapse
Don't know, only telling you what I did cause I had the same problem as you
Well I'm finally rooted. I didn't change the encryption, just tried a different method and after several tries it finally worked. I used adb sideload inside TWRP after canceling the password screen. Odd that it took several tries, though, to get through it without generating errors. We'll see how it goes next month.
I have had a lot of trouble with rooting Oreo...
I started out trying to use Magisk but gave up after many attempts. Every version, and every kernel I tried resulted in booting to recovery and not system. I could have tried the ADB method but I actually want to have TWRP so I didn't try that.
By the time I tried SuperSU my factory image had had an OTA and many apps & files installed so I can't say my system is "clean" but I have Fastboot flashed the stock boot image many (many) times to recover from whatever Magisk does to the kernel. I never looked all that hard for this unofficial TWRP people talk about so I used 3.1.1-1. At some point I converted to File Based Encryption because it is so much nicer to use, and so TWRP cannot decrypt my internal storage, but the workaround is to put zips and images on a USB drive. It also does not ask for a password. So far so good, I have my workarounds. I do also have this weird error where TWRP cannot unmount the system but I can flash kernels without problems. I have chosen to keep system read-only for superstitious reasons. I think it will fail if I look at it funny sometimes lol.
From this state I flashed the latest SuperSU and it booted! So I do have root. I still would like to try Magisk for the modules but it seems this isn't ready. However, my trusty old terminal app hangs at the su command... and several kernels will crash my tablet... so it's "working" but there is more to do. And literally just now I see I have an OTA. lol.
I followed the original instructions and got rooted with the latest version of Oreo. But, TWRP still wouldn't flash correctly without causing boot loops.
I finally got it resolved by using the original instructions, then loading the Official TWRP app from Google Play. I used the app to flash twrp-3.1.1-1-dragon.img.
Everything is working properly now. I have 8.0.0 (OPR1.170623.032, Nov 2017) loaded and rooted, and the Pixel C will boot into TWRP and see the encrypted data.
Is it posible to flash latest Oreo stock factory image https://developers.google.com/android/images ryu-opr1.170623.032-factory-020f1cf9.zip using stock TWRP or do I have to side load it ?
I'm getting a Invalid zip file format error in TWRP when I try and flash it

magisk for Pixel xl dp3

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.

Boot hang, TWRP Recovery unresponsive

Coming to you all with hat in hand.
Not sure what steps to take next.
Unlocked bootloader and all the rest of the steps here:
https://www.xda-developers.com/google-pixel-3-unlock-bootloader-root-magisk/
Symptom is a never ending booting "G".
I reboot and can choose recovery but the twrp screen in unresponsive. As in, I get the slider but cannot slide it.
I'm not sure what that means.
I do see the device and its listed as 'recovery' in adb.
I did see the issue of using old platform tools too late. :crying:
How bleak is my outlook?
Thank you for any help.
When you booted the twrp.img did you have the newest one and then install the newest twrp installer.zip?
Short version... Extract the boot.img from the system image file and install that to both partitions through fastboot (going to have to do some reading on how to do that, and you might learn a bit in the process). System should boot normally then with stock recovery. Now, you can use the current version of the twrp.img to root without even needing to permanently install it. Before you even do that though, spend some time getting to know your device and the current versions and options that are out there. That web page you pointed to was just a primer and was published when the device first came out. Their have been some small changes.
@edmodumb - What billy said^^. From your adb folder you can fastboot flash boot.img, then fastboot boot twrp.img right afterwards to get TWRP back (and the phone will boot System as well).
pixel 3xl unlocked bootloader - installed twrp.img via fastboot- installed twrp.zip in recovery-installed magisk 17.3 via
recovery
phone booted up , no problem then i went to magisk app and installed magisk installed by direct patch and rebooted,
now struck in booloop.
if i boot into recovery twrp is unresponsive even if i reinstall with fastboot.
i tried to install factory image but still stuck in bootloop????
i tried to flash boot.img to the a and b partions with fastboot but no sure if i'm doing it right?
motrac said:
pixel 3xl unlocked bootloader - installed twrp.img via fastboot- installed twrp.zip in recovery-installed magisk 17.3 via
recovery
phone booted up , no problem then i went to magisk app and installed magisk installed by direct patch and rebooted,
now struck in booloop.
if i boot into recovery twrp is unresponsive even if i reinstall with fastboot.
i tried to install factory image but still stuck in bootloop????
i tried to flash boot.img to the a and b partions with fastboot but no sure if i'm doing it right?
Click to expand...
Click to collapse
Flash the boot image to both slots #6 in the guide or flash the factory image #4 in the guide to return to stock. then do #7 in the guide to root. Done! Do not flash the patched_boot.img.
[Guide] Pixel 3 XL Android 9.0 (Pie) Unlock/Root/Install Images/Kernels/Recovery + November 2018 Security Patch
Homeboy76 said:
Flash the boot image to both slots #6 in the guide or flash the factory image #4 in the guide to return to stock. then do #7 in the guide to root. Done! Do not flash the patched_boot.img.
[Guide] Pixel 3 XL Android 9.0 (Pie) Unlock/Root/Install Images/Kernels/Recovery + November 2018 Security Patch
Click to expand...
Click to collapse
i flashed factory and it installs but at the end i get this:
"Erase successful, but not automatically formatting. File system type raw not supported."
is that ok or is it an error?
phone still doesn't boot.
when i flash boot file i get:
"FAILED (remote: Failed to write to partition Not Found)"
motrac said:
i flashed factory and it installs but at the end i get this:
"Erase successful, but not automatically formatting. File system type raw not supported."
is that ok or is it an error?
phone still doesn't boot.
when i flash boot file i get:
"FAILED (remote: Failed to write to partition Not Found)"
Click to expand...
Click to collapse
reflashed factory after updating fastboot and it boots now, good learning lesson for me. thanks for the help
Yikes ! I am not the expert, but . . . . it really sounds like 'rma' time to me...
.
If you do things on a low battery, it'll corrupt stuff. Is this thing fully charged up ?
.
motrac said:
reflashed factory after updating fastboot and it boots now, good learning lesson for me. thanks for the help
Click to expand...
Click to collapse
Homeboy76 said:
Click to expand...
Click to collapse
@motrac @Homeboy76
Woah sounds like my problem is similar --- I can't boot into anything but a dark screen except for bootloader.
I saw the "updated fastboot"
I tried flashing the boot.img and then the factory image
but no luck --- just blackscreen when I try to do anything other than bootloader
I had some errors when flashing factory image -- see screeen shot
jcrompton said:
@[email protected]
Woah sounds like my problem is similar --- I can't boot into anything but a dark screen except for bootloader.
I saw the "updated fastboot"
I tried flashing the boot.img and then the factory image
but no luck --- just blackscreen when I try to do anything other than bootloader
I had some errors when flashing factory image -- see screeen shot
Click to expand...
Click to collapse
Is "updated fastboot" r28.0.1?
Homeboy76 said:
Is "updated fastboot" r28.0.1?
Click to expand...
Click to collapse
Yes.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
Yes.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Still can't boot my device -- just no luck after updating fastboot
PLEASE .. any help would be appreciated!!
This is another place where I was trying to solve the issue - sorry for doubling up
https://forum.xda-developers.com/showpost.php?p=78276952&postcount=258
Resurrecting. Had to set aside for a while, sorry.
@sliding_billy & @v12xke , thank you for the responses. Out of around six phones, this is the first time I've had issues rooting/flashing images. That's thanks to XDA.
After your responses and some more learning (this time paying more attention to post dates), I have the phone back up on its feet.
Off to re-root, wish me luck.
Thank you very much!
I did a backup on twrp and then it wouldn't boot ugh off to try it all again LOL
edmodumb said:
Resurrecting. Had to set aside for a while, sorry.
@sliding_billy & @v12xke , thank you for the responses. Out of around six phones, this is the first time I've had issues rooting/flashing images. That's thanks to XDA.
After your responses and some more learning (this time paying more attention to post dates), I have the phone back up on its feet.
Off to re-root, wish me luck.
Thank you very much!
Click to expand...
Click to collapse
Best of luck!

December update breaks magisk?

Hi all,
I've updated my 3xl to the december update like usual, flash-all.bat without -w. Afterwards, it boots fine, and in settings it clearly states that I'm running the December security patch.
However, when I boot into twrp (not installed) and flash magisk, android boots to just before asking my SIM PIN, says "Shutting Down", then reboots and gives me the message "Can't load Android System. Your data may be corrupt." etc. inside stock recovery.
Did the December update somehow break magisk? Anyone gotten it to work? I'd rather not do a factory reset if it's not needed.
Works fine for me.
Try re-flashing the December update with the - w deleted see if it boots up. Then try flashing magdisk manually on bkth a and b partitions
Working fine for me as well.
I would try flashing the stock boot and system images to both slots. It probably won't work but worth a try before doing a factory reset.
Sent from my [device_name] using XDA-Developers Legacy app
You have a corrupt backup copy of boot.img, Magisk grabbed that and used it for root.
Flash the stock boot.img to both slots and reroot.
mikepopo99 said:
Try re-flashing the December update with the - w deleted see if it boots up. Then try flashing magdisk manually on bkth a and b partitions
Click to expand...
Click to collapse
jd1639 said:
I would try flashing the stock boot and system images to both slots. It probably won't work but worth a try before doing a factory reset.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
TonikJDK said:
You have a corrupt backup copy of boot.img, Magisk grabbed that and used it for root.
Flash the stock boot.img to both slots and reroot.
Click to expand...
Click to collapse
First off, thanks for trying to help!
Flashing the stock boot.img "solves" the problem, I can boot and use the phone like normal, but without root obviously. Using the stock boot.img inside magisk manager to patch it with 17.3 and flashing that boot image to both partitions gives me this error again. I've also tried re-applying the December update at least 3 more times, with the same result. Any other ideas?
RogerXIII said:
First off, thanks for trying to help!
Flashing the stock boot.img "solves" the problem, I can boot and use the phone like normal, but without root obviously. Using the stock boot.img inside magisk manager to patch it with 17.3 and flashing that boot image to both partitions gives me this error again. I've also tried re-applying the December update at least 3 more times, with the same result. Any other ideas?
Click to expand...
Click to collapse
Flash the stock boot.img to both slots.
Reboot and check it.
Copy the Magisk zip to your phone.
Fastboot boot the TWRP img file, don't install it.
Use TWRP to install the Magisk zip, and you are done.
RogerXIII said:
First off, thanks for trying to help!
Flashing the stock boot.img "solves" the problem, I can boot and use the phone like normal, but without root obviously. Using the stock boot.img inside magisk manager to patch it with 17.3 and flashing that boot image to both partitions gives me this error again. I've also tried re-applying the December update at least 3 more times, with the same result. Any other ideas?
Click to expand...
Click to collapse
Do you have the previous version of Edge Sense Plus module installed? That sounds exactly like what happens if you install Magisk with that module still there. He put out a new one today.
sliding_billy said:
Do you have the previous version of Edge Sense Plus module installed? That sounds exactly like what happens if you install Magisk with that module still there. He put out a new one today.
Click to expand...
Click to collapse
Thank you so much, this worked!
Instead of going back an Android version, I used this script, uninstalled all modules and re-flashed Magisk. It works perfectly now. Thanks again!
RogerXIII said:
Thank you so much, this worked!
Instead of going back an Android version, I used this script, uninstalled all modules and re-flashed Magisk. It works perfectly now. Thanks again!
Click to expand...
Click to collapse
Good deal. That is why I always keep a copy of the Magisk uninstaller on the phone itself. As long as I can get to BL/temp TWRP .img, the worst I am out is the time it takes me to reconfigure Magisk.
RogerXIII said:
However, when I boot into twrp (not installed)
Click to expand...
Click to collapse
What do you use to get TWRP going when it's not permenantly installed? Just curious?
Fire Hound 8.1
Shaftamle said:
What do you use to get TWRP going when it's not permenantly installed? Just curious?
Fire Hound 8.1
Click to expand...
Click to collapse
The TWRP image from the official website, and then simply fastboot boot twrp.img
RogerXIII said:
The TWRP image from the official website, and then simply fastboot boot twrp.img
Click to expand...
Click to collapse
Ok cool. Wasn't sure if there was an app like fashify or something.
Fire Hound 8.1
sliding_billy said:
Do you have the previous version of Edge Sense Plus module installed? That sounds exactly like what happens if you install Magisk with that module still there. He put out a new one today.
Click to expand...
Click to collapse
you are godsend my friend.
Touz604 said:
you are godsend my friend.
Click to expand...
Click to collapse
Glad you got it figured out.
RogerXIII said:
The TWRP image from the official website, and then simply fastboot boot twrp.img
Click to expand...
Click to collapse
How can we boot the twrp from fastboot?
The one from official website doesn't support Android 10 I believe and I failed with the info says "too many links".
bbs3223474 said:
How can we boot the twrp from fastboot?
The one from official website doesn't support Android 10 I believe and I failed with the info says "too many links".
Click to expand...
Click to collapse
You ca't yet.
bbs3223474 said:
How can we boot the twrp from fastboot?
The one from official website doesn't support Android 10 I believe and I failed with the info says "too many links".
Click to expand...
Click to collapse
Thread is from 2018
I am gonna check the official TWRP website for the workable TWRP for my Pixel 3 till I see your post
wangdaning said:
Thread is from 2018
Click to expand...
Click to collapse

Issues Rooting Pixel XL with TWRP/Magisk

I'm following some guides to root my pixel xl but am running to some issues.
I tried using twrp-3.3.1-0-marlin.img to load Magisk-v19.3.zip but it gives me errors mounting system and vendor.
I then tried using twrp-3.3.0-0-marlin.img to load Magisk-v19.3.zip and it appears to succeed. I reboot, but Magisk Manager never appears. When I load it manually, it tells me that Magisk 19.3 isn't installed.
I'm not sure what I'm doing wrong. Is there some hidden step?
Thank you.
ookami007 said:
I'm following some guides to root my pixel xl but am running to some issues.
I tried using twrp-3.3.1-0-marlin.img to load Magisk-v19.3.zip but it gives me errors mounting system and vendor.
I then tried using twrp-3.3.0-0-marlin.img to load Magisk-v19.3.zip and it appears to succeed. I reboot, but Magisk Manager never appears. When I load it manually, it tells me that Magisk 19.3 isn't installed.
I'm not sure what I'm doing wrong. Is there some hidden step?
Thank you.
Click to expand...
Click to collapse
Mounting errors are normal. Use 3.3.1-0
Boot TWRP image
Flash TWRP zip
Flash magisk (latest canary channel)
Reboot
Install magisk manager if necessary (latest canary)
Open magisk manager and follow any instructions.
Tulsadiver said:
Mounting errors are normal. Use 3.3.1-0
Boot TWRP image
Flash TWRP zip
Flash magisk (latest canary channel)
Reboot
Install magisk manager if necessary (latest canary)
Open magisk manager and follow any instructions.
Click to expand...
Click to collapse
Need to try this soon, glad to see it's working ?
Sent from my Pixel XL using XDA Labs
Tulsadiver said:
Mounting errors are normal. Use 3.3.1-0
Boot TWRP image
Flash TWRP zip
Flash magisk (latest canary channel)
Reboot
Install magisk manager if necessary (latest canary)
Open magisk manager and follow any instructions.
Click to expand...
Click to collapse
I've followed this along with every other guide I could find at least 10x each or more, and still haven't achieved root. Everything seems to install fine, but everytime I open Magisk Manager, it shows "Magisk is not installed". And that seems to be the only thing keeping me from getting root. There has to be a missing step or something... It's been about 5 years since I've rooted a device(HTC M8), but I don't remember ever having so much difficulty. I've wiped the phone more times than I can count, uninstalled/reinstalled Magisk(regular and Canary), tried to do this on both Android 8 and 9, tried to complete this process on both LinuxMint and Windows, etc. I'm completely out of ideas at this point.
tyler.durden said:
I've followed this along with every other guide I could find at least 10x each or more, and still haven't achieved root. Everything seems to install fine, but everytime I open Magisk Manager, it shows "Magisk is not installed". And that seems to be the only thing keeping me from getting root. There has to be a missing step or something... It's been about 5 years since I've rooted a device(HTC M8), but I don't remember ever having so much difficulty. I've wiped the phone more times than I can count, uninstalled/reinstalled Magisk(regular and Canary), tried to do this on both Android 8 and 9, tried to complete this process on both LinuxMint and Windows, etc. I'm completely out of ideas at this point.
Click to expand...
Click to collapse
Have you tried fastboot flash boot magisk_patched.img after making one in magisk manager? Are you on Android 10?
This was made from a pixel XL boot.img, Android 10
https://mega.nz/#!lQg0RaiJ!_YRjiL3nHysUeLavKt0umJjrHbSPzJsqkPVi2qIQfZE
Make sure your ADB/fastboot platform tools are up to date.
Tulsadiver said:
Have you tried fastboot flash boot magisk_patched.img after making one in magisk manager? Are you on Android 10?
This was made from a pixel XL boot.img, Android 10
https://mega.nz/#!lQg0RaiJ!_YRjiL3nHysUeLavKt0umJjrHbSPzJsqkPVi2qIQfZE
Make sure your ADB/fastboot platform tools are up to date.
Click to expand...
Click to collapse
That's definitely one that I haven't tried yet. I'm still on Android 9 for now. I downloaded the latest Platform tools just a few days ago, so that part should be up to date. It doesn't seem like there's much for Android 10 yet, so I'm waiting a bit before I switch.
tyler.durden said:
That's definitely one that I haven't tried yet. I'm still on Android 9 for now. I downloaded the latest Platform tools just a few days ago, so that part should be up to date. It doesn't seem like there's much for Android 10 yet, so I'm waiting a bit before I switch.
Click to expand...
Click to collapse
Here is the boot and patched boot from 9 August update. I typically have firmware for recent Pixel phones.
https://mega.nz/#!gRBGhYAZ!Z7mEBEHVT9V4ut0p__g5BVboS8RjLSSPWXgjurSQxbU
Tulsadiver said:
Here is the boot and patched boot from 9 August update. I typically have firmware for recent Pixel phones.
https://mega.nz/#!gRBGhYAZ!Z7mEBEHVT9V4ut0p__g5BVboS8RjLSSPWXgjurSQxbU
Click to expand...
Click to collapse
Thank you! Magisk finally installed using the boot.img patching method, and now I have root access.
Tulsadiver said:
Have you tried fastboot flash boot magisk_patched.img after making one in magisk manager? Are you on Android 10?
This was made from a pixel XL boot.img, Android 10
https://mega.nz/#!lQg0RaiJ!_YRjiL3nHysUeLavKt0umJjrHbSPzJsqkPVi2qIQfZE
Make sure your ADB/fastboot platform tools are up to date.
Click to expand...
Click to collapse
I am having the same issue, but with the Oct patch. How do I make one of these with Magisk Manager? I tried making it with the bootloader img from the stock factory image, but it fails at repackaging step. Anyone else having issue with Oct patch?
smithilberry said:
I am having the same issue, but with the Oct patch. How do I make one of these with Magisk Manager? I tried making it with the bootloader img from the stock factory image, but it fails at repackaging step. Anyone else having issue with Oct patch?
Click to expand...
Click to collapse
You meant boot.img, right?
Edit. You need to unzip the image zip in order to get the boot.img.
Tulsadiver said:
You meant boot.img, right?
Edit. You need to unzip the image zip in order to get the boot.img.
Click to expand...
Click to collapse
Yes, that's what I meant. I also got it working. I used TWRP 3.3.0 and it worked. Not sure what the reason would be.
Tulsadiver said:
Mounting errors are normal. Use 3.3.1-0
Boot TWRP image
Flash TWRP zip
Flash magisk (latest canary channel)
Reboot
Install magisk manager if necessary (latest canary)
Open magisk manager and follow any instructions.
Click to expand...
Click to collapse
Sent from my marlin using XDA Labs
---------- Post added at 10:51 AM ---------- Previous post was at 10:45 AM ----------
Tulsadiver said:
Have you tried fastboot flash boot magisk_patched.img after making one in magisk manager? Are you on Android 10?
This was made from a pixel XL boot.img, Android 10
https://mega.nz/#!lQg0RaiJ!_YRjiL3nHysUeLavKt0umJjrHbSPzJsqkPVi2qIQfZE
Make sure your ADB/fastboot platform tools are up to date.
Click to expand...
Click to collapse
This was my dilemma. I have no PC so I am using Osmosis's static fastboot magisk mod and it works excellent but because the sdk must be an updated version it does not know the command when you flash the patched boot.img the " --slots all " it says unrecognizabled command in termux and terminal emulator but everything else will flash it's just that new --slots all that gets it. Is there any way for me to get the boot.img on both slots without using that command? Can I just fastboot the boot then reboot bootloader and repeat? Would that get it on both slots?
Is it possible to install the boot.img in one slot or will that mess things up? Guide has patched boot on both...Or just boot twrp 3300 and flash a rom? I'm weary about getting too brave because I bricked a device recently that was A/B. I been around for many years and never bricked anything till recently. ?
Sent from my marlin using XDA Labs
flash713 said:
Sent from my marlin using XDA Labs
---------- Post added at 10:51 AM ---------- Previous post was at 10:45 AM ----------
This was my dilemma. I have no PC so I am using Osmosis's static fastboot magisk mod and it works excellent but because the sdk must be an updated version it does not know the command when you flash the patched boot.img the " --slots all " it says unrecognizabled command in termux and terminal emulator but everything else will flash it's just that new --slots all that gets it. Is there any way for me to get the boot.img on both slots without using that command? Can I just fastboot the boot then reboot bootloader and repeat? Would that get it on both slots?
Is it possible to install the boot.img in one slot or will that mess things up? Guide has patched boot on both...Or just boot twrp 3300 and flash a rom? I'm weary about getting too brave because I bricked a device recently that was A/B. I been around for many years and never bricked anything till recently.
Sent from my marlin using XDA Labs
Click to expand...
Click to collapse
I personally have never flashed it to both slots. Just the current slot
fastboot flash boot magisk_patched.img
Tulsadiver said:
I personally have never flashed it to both slots. Just the current slot
fastboot flash boot magisk_patched.img
Click to expand...
Click to collapse
You rock! Appreciate you telling me this! I believe I understand more now that I've read about the A/B partition for a few weeks.. Pixel XL forums actually has the most detailed information of A/B that I've seen yet. Cheers.
Sent from my marlin using XDA Labs
Tulsadiver said:
I personally have never flashed it to both slots. Just the current slot
fastboot flash boot magisk_patched.img
Click to expand...
Click to collapse
Can I fastboot vendor and bootloader, or anything instead of the entire factory image if I want to roll back to August Pie from October 10? I'm going after DU and it's an August pie build.. Thanks for the info on slots! Somehow it helped me better understand the entire partition deal... I remember you from many years ago on some Nexus device that you made various mods for.. Anyway thanks! Alot!
Sent from my marlin using XDA Labs
flash713 said:
Can I fastboot vendor and bootloader, or anything instead of the entire factory image if I want to roll back to August Pie from October 10? I'm going after DU and it's an August pie build.. Thanks for the info on slots! Somehow it helped me better understand the entire partition deal... I remember you from many years ago on some Nexus device that you made various mods for.. Anyway thanks! Alot!
Sent from my marlin using XDA Labs
Click to expand...
Click to collapse
To roll back you not only have to flash the entire image but you'll have to wipe your phone.
TWRP boot looping?
I'm trying to root a Pixel XL Android 10, purchased form Google. I'm stuck at the point of trying to boot the phone to the temporary TWRP. Using command "fastboot boot twrp.img" .
I get the "Sending, Booting, Finished OKAY" messages, but the phone then shows a never ending flash of the TWRP logo every few seconds, with no functionality.
The twrp.img I'm using is twrp-3.0.2-0-RC1-fastboot-marlin.img
Any suggestions?
SeekMocha said:
I'm trying to root a Pixel XL Android 10, purchased form Google. I'm stuck at the point of trying to boot the phone to the temporary TWRP. Using command "fastboot boot twrp.img" .
I get the "Sending, Booting, Finished OKAY" messages, but the phone then shows a never ending flash of the TWRP logo every few seconds, with no functionality.
The twrp.img I'm using is twrp-3.0.2-0-RC1-fastboot-marlin.img
Any suggestions?
Click to expand...
Click to collapse
NEVER MIND: I was using wrong version of TWRP.
SeekMocha said:
NEVER MIND: I was using wrong version of TWRP.
Click to expand...
Click to collapse
What TWRP version did you use?

Categories

Resources