Related
My setup
Pixel XL from Verizon
Bootloader unlocked
Bootloader Version 8996-0121001-1611091517
Baseband 8996-012511-1611190200
Android 7.1.1 NOF26V
Kernal 3.18.31-g367e645 Dec 7, 23, 2016
Twrp Version 3.0.2.0 RC1
I have tried following this guide to get root access https://www.xda-developers.com/root-is-now-available-for-the-google-pixel-and-pixel-xl/
My steps are
1. boot phone into fastboot
2. from pc run fastboot boot boot-to-root.img
3. the phone reboots
4. Phone is stuck with the 4 colored dots jumping over each other
5. i've given this screen up to 30 minutes with no results.
6. Forcing a reboot causes the same issue
7. Flash stock android via the official google factory image method
I have attempted this other method as well http://www.theandroidsoul.com/root-pixel-xl-magisk/
But after TWRP says it's successful, i boot into my OS and there is no supersu and if i manually install supersu, it says no root access.
You are doing it the old way that was for 7.1.
You want SU 2.79 SR3
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
And you want TWRP RC1.
https://forum.xda-developers.com/pixel-xl/development/twrp-alpha1-pixel-devices-t3500312
I would not install TWRP at this point. So copy SU to your phone. Then boot to TWRP.
Fastboot BOOT twrp.img
With twrp.img being the correct name of the file. Then in TWRP install the SU you copied.
The old way... Sheesh, there's only so much space up here. But thank you. You've saved be a big headache when my XL finally arrives.
Edit: you boot TWRP, not flash through fastboot?
Larzzzz82 said:
The old way... Sheesh, there's only so much space up here. But thank you. You've saved be a big headache when my XL finally arrives.
Edit: you boot TWRP, not flash through fastboot?
Click to expand...
Click to collapse
You boot it, always.
If you want to install it you copy the twrp ZIP to the phone. Boot it with the TWRP image file then install the twrp zip from within twrp.
Gotta be done that way. Partition layout has changes, they are a bit intertwined now.
I dont install TWRP anymore.
That was half the fun not needing a PC to flash a ROM.
I see I'll be reading. A LOT before it gets here.
Larzzzz82 said:
That was half the fun not needing a PC to flash a ROM.
I see I'll be reading. A LOT before it gets here.
Click to expand...
Click to collapse
That might be doable, I am not a ROM guy. Root and kernel only....and I always got a PC.
so I would just want to pull down the twrp RC1 image file, boot from fastboot without flashing it, and use it to flash the SU SR3? All i want is root access at the moment on the pixel XL.
if i understand this right, this will just give me SU with root, and not install any form of TWRP.
steber04 said:
so I would just want to pull down the twrp RC1 image file, boot from fastboot without flashing it, and use it to flash the SU SR3? All i want is root access at the moment on the pixel XL.
if i understand this right, this will just give me SU with root, and not install any form of TWRP.
Click to expand...
Click to collapse
Exactly.
Larzzzz82 said:
That was half the fun not needing a PC to flash a ROM.
I see I'll be reading. A LOT before it gets here.
Click to expand...
Click to collapse
You don't need a PC if you just install TWRP.
TonikJDK said:
Exactly.
Click to expand...
Click to collapse
will i need anything more than ADB? I used depixle8 via ADB to unlock my bootloader.. i assume its just the same to push the files through or am i missing something?
steber04 said:
will i need anything more than ADB? I used depixle8 via ADB to unlock my bootloader.. i assume its just the same to push the files through or am i missing something?
Click to expand...
Click to collapse
What files are you pushing that you cannot just load directly with the device powered up?
steber04 said:
will i need anything more than ADB? I used depixle8 via ADB to unlock my bootloader.. i assume its just the same to push the files through or am i missing something?
Click to expand...
Click to collapse
You will need fastboot, so you can fastboot boot twrp. I don't push the SU zip with adb, I just copy/download it to the phone before I reboot into Fastboot. Make sure you get Fastboot from Google, not the Minimal one.
https://developer.android.com/studio/releases/platform-tools.html
I'm running the stock rom on the November patch. I have TWRP installed with Magisk and the Kirisakura kernel. I've read and Googled for a solution and still can't get it to work. I have the latest ADB told installed but I am unable to push the update through. Can someone tell me what I'm missing? This used to be so much simpler lol. Thanks in advance.
DarkPhoenix said:
I'm running the stock rom on the November patch. I have TWRP installed with Magisk and the Kirisakura kernel. I've read and Googled for a solution and still can't get it to work. I have the latest ADB told installed but I am unable to push the update through. Can someone tell me what I'm missing? This used to be so much simpler lol. Thanks in advance.
Click to expand...
Click to collapse
From what I understand you can not do ADB in TWRP to install an update. What I did was download the factory images, remove -w from the flash all.bat. flashed the images and let the phone boot normally. Once I knew it was running I went to the bootloader and booted TWRP temporarily. Once that was up I flashed Magisk and then my kernel
I don't install TWRP anymore.
DarkPhoenix said:
I'm running the stock rom on the November patch. I have TWRP installed with Magisk and the Kirisakura kernel. I've read and Googled for a solution and still can't get it to work. I have the latest ADB told installed but I am unable to push the update through. Can someone tell me what I'm missing? This used to be so much simpler lol. Thanks in advance.
Click to expand...
Click to collapse
Adding to what hatdrc said, you want the full image, not OTA, and install from your PC in fastboot mode. If you are concerned about saving your data, remove the -w switch from flash-all.bat first using a file editor like notepad. Have the twrp.zip, kernel.zip and magisk.zip files already staged. I personally don't boot to system first (but you can), I "catch" the reboot after flashing completes with the volume down button to reboot to fastboot mode. Then fastboot boot twrp.img, and then install twrp, kernel and magisk zips all in one go using the "add more zips" button in twrp. Every month when you update, you'll lose twrp, kernel and magisk, so those have to be reflashed each time. You'll soon get used to it and can do the whole thing in about 5 minutes consistently. Just make sure to pre-stage the 3 zip files on the phone before you start. Best of luck.
I tried that but couldn't get it to work. I downloaded the ADB tools again just in case there was an issue with that. I'm going to run the flash-all script again to see if I can get it to work.
DarkPhoenix said:
I tried that but couldn't get it to work. I downloaded the ADB tools again just in case there was an issue with that. I'm going to run the flash-all script again to see if I can get it to work.
Click to expand...
Click to collapse
if whats suggested above doesnt work, you can make the OTA work....download the ota to your PC, boot to Android Recovery (not TWRP), apply the ota via ADB from the menu. Whenever I have "odd" issues applying the Full image, this always works for me. Obviously you need to re-root after.
GL!
cmh714 said:
if whats suggested above doesnt work, you can make the OTA work....download the ota to your PC, boot to Android Recovery (not TWRP), apply the ota via ADB from the menu. Whenever I have "odd" issues applying the Full image, this always works for me. Obviously you need to re-root after.
GL!
Click to expand...
Click to collapse
Doesn't installing TWRP remove Android Recovery?
DarkPhoenix said:
Doesn't installing TWRP remove Android Recovery?
Click to expand...
Click to collapse
hmm, since I dont install TWRP anymore, you may be correct....still cant hurt to try
DarkPhoenix said:
Doesn't installing TWRP remove Android Recovery?
Click to expand...
Click to collapse
Yes it does. TWRP replaces the stock recovery.
Sent from my [device_name] using XDA-Developers Legacy app
v12xke said:
Adding to what hatdrc said, you want the full image, not OTA, and install from your PC in fastboot mode. If you are concerned about saving your data, remove the -w switch from flash-all.bat first using a file editor like notepad. Have the twrp.zip, kernel.zip and magisk.zip files already staged. I personally don't boot to system first (but you can), I "catch" the reboot after flashing completes with the volume down button to reboot to fastboot mode. Then fastboot boot twrp.img, and then install twrp, kernel and magisk zips all in one go using the "add more zips" button in twrp. Every month when you update, you'll lose twrp, kernel and magisk, so those have to be reflashed each time. You'll soon get used to it and can do the whole thing in about 5 minutes consistently. Just make sure to pre-stage the 3 zip files on the phone before you start. Best of luck.
Click to expand...
Click to collapse
Ok, I got the flash-all script to run. My brain shut down and I was running the wrong command.
DarkPhoenix said:
Ok, I got the flash-all script to run. My brain shut down and I was running the wrong command.
Click to expand...
Click to collapse
Well done. Now you can do it all over again in a week on Monday the 7th when the January build comes out.
v12xke said:
Well done. Now you can do it all over again in a week on Monday the 7th when the January build comes out.
Click to expand...
Click to collapse
I was updating so I could install Bootleggers rom so updating should be a lot easier lol.
Hi all, I have TWRP + Magisk on my device and I am attempting to update from PQ1A.181205.006 to PQ2A.190205.001.
Steps taken
1. Downloaded the OTA from here: https://developers.google.com/android/ota#crosshatch
2. Moved the OTA to phone storage.
3. Checked SHA256 checksum matches.
4.
Code:
adb reboot recovery
5.
Code:
fastboot boot twrp-3.2.3-3-crosshatch.img
6. From TWRP > Install > OTA zip file
Fails with the attached error. I have also tried sideloading through TWRP with the same result. Has anyone hit this error or successfully flashed the OTA update through TWRP?
I have not heard of anyone successfully loading an OTA through TWRP. Either restore stock recovery (install boot.img to both slots) and sideload with the Google instructions or run the flash-all (remove the -w) to use the factory image. Either way, you ere going to be reverting to stock recovery.
P.S. Your message doesn't make sense since you say you have TWRP on your device but then are showing that you used fastboot boot to run the TWRP .img file. If TWRP was on your device, you wouldn't have to use that command. You would just have entered TWRP with the adb reboot recovery command. I am guessing you are rebooting into the bootloader screen where either you run the TWRP .img or run the flash-all.
I also thought I saw a previous post somewhere that said you cannot skip an update, so going from December to February may not work.....not sure...
But definitely you need to load the OTA via regular Recovery using adb not TWRP....
Can you install a OTA?
I thought you had to perform an ADB sideload of an OTA.
Even then I am not aware that ADB sideload works for Pixel 3xl yet.
I have been flashing the factory image with -w removed.
parakleet said:
Can you install a OTA?
I thought you had to perform an ADB sideload of an OTA.
Even then I am not aware that ADB sideload works for Pixel 3xl yet.
I have been flashing the factory image with -w removed.
Click to expand...
Click to collapse
ADB sideload works fine for the OTAs in stock recovery. That's how I've been doing mine.
On a side note, the Essential phone is the only phone I've come across so far that TWRP will flash the factory OTAs.
spotmark said:
ADB sideload works fine for the OTAs in stock recovery. That's how I've been doing mine.
On a side note, the Essential phone is the only phone I've come across so far that TWRP will flash the factory OTAs.
Click to expand...
Click to collapse
The P2XL and Nexis 6p can flash OTA's via twrp as well. Hopefully Team Win will get it sorted out for you guys as well :good:
Badger50 said:
The P2XL and Nexis 6p can flash OTA's via twrp as well. Hopefully Team Win will get it sorted out for you guys as well :good:
Click to expand...
Click to collapse
Flash them or sideload them? I never had a P2XL, but I had a Nexus 6p and I don't remember being able to flash that with the factory zips. That doesn't mean my memory isn't shot either.
spotmark said:
Flash them or sideload them? I never had a P2XL, but I had a Nexus 6p and I don't remember being able to flash that with the Factory zips. That doesn't mean my memory isn't shot either.
Click to expand...
Click to collapse
Yeah, it was possible, just not many people knew about it, but it definitely works :good:
Flashing them that is.
I went from dec to feb update no problem
hilla_killa said:
I went from dec to feb update no problem
Click to expand...
Click to collapse
Sideloading or factory image method?
I am trying to do an OTA update on my Pixel 3xl. I have TWRP installed and need to get back to stock recovery. I have the stock boot.img file and have attempted to flash with adb fastboot but I keep getting this error
writing 'recovery'...
FAILED (remote: Not allowed to flash (recovery))
Bootloader is unlocked
USB debugging is on
Any help would be appreciated.
Badbrad17 said:
I am trying to do an OTA update on my Pixel 3xl. I have TWRP installed and need to get back to stock recovery. I have the stock boot.img file and have attempted to flash with adb fastboot but I keep getting this error
writing 'recovery'...
FAILED (remote: Not allowed to flash (recovery))
Bootloader is unlocked
USB debugging is on
Any help would be appreciated.
Click to expand...
Click to collapse
Did you first extract the secondary zip file inside the factory image, and then placed the boot.img in your platform-tools folder, and the used the command..fastboot flash boot boot.img....??
Badger50 said:
Did you first extract the secondary zip file inside the factory image, and then placed the boot.img in your platform-tools folder, and the used the command..fastboot flash boot boot.img....??
Click to expand...
Click to collapse
Yes that is what I did.
Badbrad17 said:
Yes that is what I did.
Click to expand...
Click to collapse
Okay, and you are in fastboot mode and not adb from the OS as well I take it? Have you tried a different USB cable and port? If all else fails, you can flash the boot.img in twrp as well.
Badger50 said:
Okay, and you are in fastboot mode and not adb from the OS as well I take it? Have you tried a different USB cable and port? If all else fails, you can flash the boot.img in twrp as well.
Click to expand...
Click to collapse
OH I di not know I could do it in TWRP. Will try that first. thanks
Badbrad17 said:
OH I di not know I could do it in TWRP. Will try that first. thanks
Click to expand...
Click to collapse
Just make sure you flash it to the boot partition :good:
raphytaffy said:
Hi all, I have TWRP + Magisk on my device and I am attempting to update from PQ1A.181205.006 to PQ2A.190205.001.
Steps taken
1. Downloaded the OTA from here: https://developers.google.com/android/ota#crosshatch
2. Moved the OTA to phone storage.
3. Checked SHA256 checksum matches.
4.
Code:
adb reboot recovery
5.
Code:
fastboot boot twrp-3.2.3-3-crosshatch.img
6. From TWRP > Install > OTA zip file
Fails with the attached error. I have also tried sideloading through TWRP with the same result. Has anyone hit this error or successfully flashed the OTA update through TWRP?
Click to expand...
Click to collapse
I've installed 3 latest updates from twrp ...
Download the latest OTA, you have to be in stock Rom and Kernel stock ... and have last twrp on your phone... Flash OTA and twrp installer to keep twrp ... restart in twrp for magisk or restart system ... benefits
sorry for my bad english.
Badger50 said:
Just make sure you flash it to the boot partition :good:
Click to expand...
Click to collapse
How do I make sure of this? Sorry I'm a bit of a noob.
Badbrad17 said:
How do I make sure of this? Sorry I'm a bit of a noob.
Click to expand...
Click to collapse
Tap install on the twrp home screen. Then go to where you have the boot.img on your internal storage and tap image on the bottom right. Then select the "boot" partition, and swipe to install. This will return you back to stock recovery and kernel :good:
Badger50 said:
Tap install on the twrp home screen. Then go to where you have the boot.img on your internal storage and tap image on the bottom right. Then select the "boot" partition, and swipe to install. This will return you back to stock recovery and kernel :good:
Click to expand...
Click to collapse
Well I managed to do that, but now when my phone rebooted the touch screen no longer responds. Very strange. It all loads fine and I can see my screen but nothing works. I tried to go back into recovery and I get the little dead Android guy laying on his back with a red exclamation point and "No Command" below it.
Any ideas?
I really don't have a clue how to get auto updates via System Updates on my rooted Pixel 2 XL (Pie, Magisk 18.1).
If I check updates it replies that I already have the latest version (still from February 2019).
Is it possible to get updates via system menu on a rooted phone?
P. S. Sorry if I've missed a right thread for this topic)
b3rsus said:
I really don't have a clue how to get auto updates via System Updates on my rooted Pixel 2 XL (Pie, Magisk 18.1).
If I check updates it replies that I already have the latest version (still from February 2019).
Is it possible to get updates via system menu on a rooted phone?
P. S. Sorry if I've missed a right thread for this topic)
Click to expand...
Click to collapse
No, you will have to manually update on a rooted phone. It requires a computer but only takes a couple minutes.
murphyjasonc said:
No, you will have to manually update on a rooted phone. It requires a computer but only takes a couple minutes.
Click to expand...
Click to collapse
Is it possible to update the system without full wiping? As I remember I should put -w in the flash script, but will it update correctly and should I reinstall TWRP or Magisk in this case?
b3rsus said:
Is it possible to update the system without full wiping? As I remember I should put -w in the flash script, but will it update correctly and should I reinstall TWRP or Magisk in this case?
Click to expand...
Click to collapse
It will not wipe your phone as long as you remove the -w. Magisk and Twrp will have to be reinstalled but that's an easy process. Fastboot boot the twrp.img file. That will get you back in to twrp temporary so you can flash the twrp and magisk zip files.
murphyjasonc said:
It will not wipe your phone as long as you remove the -w. Magisk and Twrp will have to be reinstalled but that's an easy process. Fastboot boot the twrp.img file. That will get you back in to twrp temporary so you can flash the twrp and magisk zip files.
Click to expand...
Click to collapse
Is it any difference with the sideload method?
b3rsus said:
Is it any difference with the sideload method?
Click to expand...
Click to collapse
Mostly personal preference.. if you use the side load method you need to download the ota file instead of the full image. I personally prefer flashing the whole image in fastboot. In my experience there is less room for user error but that's my opinion.
murphyjasonc said:
Mostly personal preference.. if you use the side load method you need to download the ota file instead of the full image. I personally prefer flashing the whole image in fastboot. In my experience there is less room for user error but that's my opinion.
Click to expand...
Click to collapse
Thank you very much!)
Probably will be useful for somebody.
How to update system on a rooted Pixel 2 XL with TWRP.
Code:
[LIST=1]
[*]Download OTA file, TWRP.zip and Magisk.zip to the phone
[*]Reboot to TWRP, install OTA archive
[*]Reboot to Bootloader
[*]fastboot boot twrp.img
[*]Install TWRP.zip and Magisk.zip
[*]Power off system from TWRP
[*]Run!
[/LIST]
b3rsus said:
Is it possible to update the system without full wiping? As I remember I should put -w in the flash script, but will it update correctly and should I reinstall TWRP or Magisk in this case?
Click to expand...
Click to collapse
remove the -w from the bat file
wrecklesswun said:
remove the -w from the bat file
Click to expand...
Click to collapse
This!!
This method will not flash any custom recovery or any custom boots.
Caution: I don't take any responsibility. Proceed with your own risk and resilience in mind
Prerequisites: Oxygen OS 11 (tested with 11, issues reported with 10) and a PC with working adb and fastboot commands.
Method:
Download lineage-18.1-20210606-recovery-instantnoodlep.img or never version to your pc
Download Magisk-v23.0.apk or newer and rename it as Magisk-v23.0.zip
Enable OEM unlock in the Developer options under device Settings, if present.
Boot in to bootloader
adb reboot bootloader
Or press "Volume Up + Volume Down + Power" when the device boots
Unlock the bootloader (Caution: this will factory reset your phone)
fastboot oem unlock
Boot in to bootloader again
Boot in to lineage recovery temporarily (not flashing)
fastboot boot lineage-18.1-20210606-recovery-instantnoodlep.img
You will be booted in to lineage recovery, install Magisk-v23.0.zip now
Enable ADB
Apply update
Apply from ADB
in your pc: adb sideload Magisk-v23.0.zip
Reboot and voilà.. you are done.
Cheers!!
Worked like a charm, except for some confusion in the recovery menu choices. After enabling ADB in recovery, I had to choose "Apply update." I was then given a choice to "Apply from ADB." After enabling that option, "adb sideload Magisk-v23.0.zip" gave me an error message about some kind of mismatch and asking me if I wanted to install anyway. I took a deep breath, clicked "Yes," and all went well. Needless to say, all others proceed at their own risks, but my IN2025 running OS 11.0.7.7.IN11AA is now happily rooted with Magisk V23.0.
Wow! This is just awesome!! What will be the downside of a rooted device though? Will I still get OTA update?
melmarPH said:
Wow! This is just awesome!! What will be the downside of a rooted device though? Will I still get OTA update?
Click to expand...
Click to collapse
Yes, you will get OTA updates. If you want to accept them and still retain root, you'll need to uninstall Magisk and "Restore the boot images" so the phone will accept the OTA update. You then install the update from System Update in Settings, BUT DO NOT REBOOT!!!! Navigate back to the Magisk Manager app and click on "Install" for Magisk. You'll want the option that says, "Install to Inactive Slot (After OTA.)" After that installation finishes, you can safely reboot the OS update installed and rooted.
Abort Retry Fail? said:
Yes, you will get OTA updates. If you want to accept them and still retain root, you'll need to uninstall Magisk and "Restore the boot images" so the phone will accept the OTA update. You then install the update from System Update in Settings, BUT DO NOT REBOOT!!!! Navigate back to the Magisk Manager app and click on "Install" for Magisk. You'll want the option that says, "Install to Inactive Slot (After OTA.)" After that installation finishes, you can safely reboot the OS update installed and rooted.
Click to expand...
Click to collapse
Sweet. Thanks a lot for the guide mate.
mahendral said:
This method will not flash any custom recovery or any custom boots.
Caution: I don't take any responsibility. Proceed with your own risk and resilience in mind
Download lineage-18.1-20210606-recovery-instantnoodlep.img or never version to your pc
Download Magisk-v23.0.apk or newer and rename it as Magisk-v23.0.zip
Enable OEM unlock in the Developer options under device Settings, if present.
Boot in to bootloader
adb reboot bootloader
Or press "Volume Up + Volume Down + Power" when the device boots
Unlock the bootloader (Caution: this will factory reset your phone)
fastboot oem unlock
Boot in to bootloader again
Boot in to lineage recovery temporarily (not flashing)
fastboot boot lineage-18.1-20210606-recovery-instantnoodlep.img
You will be booted in to lineage recovery, install Magisk-v23.0.zip now
Enable ADB
Select ADB sideload
in your pc: adb sideload Magisk-v23.0.zip
Reboot and voilà.. you are done.
Cheers!!
Click to expand...
Click to collapse
On step 5 I dont see the option for fastboot oem unlock anywhere. Can a nob get a noob friendlier guide? As im lost thanks!
thanks guys worked on my 11.0.7.7.IN11AA
Thanks for the guide. It was very easy and fast to do it.
n08 said:
On step 5 I dont see the option for fastboot oem unlock anywhere. Can a nob get a noob friendlier guide? As im lost thanks!
Click to expand...
Click to collapse
Here I have assumed that the adb and the fastboot are available in your PC before begin. Step 5 should be executed from your PC (Linux or Windows) with the phone is connected through USB.
@mahendral
Super guide!
Got my OP8 Pro yesterday, less than one hour after unboxing, it was rooted
Why so long?
Because i had to update to OOS 11 (OOS 10 out of the box).
If you try your method with OOS 10, you get stuck at this step:
Boot in to lineage recovery temporarily
==> Stuck at Fastboot logo
Hence i updated to OOS 11 OB and it worked like a charm!
Thanks a lot
bc1977 said:
@mahendral
Super guide!
Got my OP8 Pro yesterday, less than one hour after unboxing, it was rooted
Why so long?
Because i had to update to OOS 11 (OOS 10 out of the box).
If you try your method with OOS 10, you get stuck at this step:
Boot in to lineage recovery temporarily
==> Stuck at Fastboot logo
Hence i updated to OOS 11 OB and it worked like a charm!
Thanks a lot
Click to expand...
Click to collapse
Thanks for the info bc1977, I'll add that as a prerequisite
Abort Retry Fail? said:
Worked like a charm, except for some confusion in the recovery menu choices. After enabling ADB in recovery, I had to choose "Apply update." I was then given a choice to "Apply from ADB." After enabling that option, "adb sideload Magisk-v23.0.zip" gave me an error message about some kind of mismatch and asking me if I wanted to install anyway. I took a deep breath, clicked "Yes," and all went well. Needless to say, all others proceed at their own risks, but my IN2025 running OS 11.0.7.7.IN11AA is now happily rooted with Magisk V23.0.
Click to expand...
Click to collapse
Amended the steps to sideload with exact steps as you pointed out. Thanks
Mahendral,
Many many thanks!!!!!
The title says it all. This is the easiest way.
I'm on 11.0.7.7.IN11AA.
Worked perfectly.
And yes, it is the easiest!
Hi, will this work on normal OP8 version IN2015? thanks.
EDIT: so this guide is for both unlocking bootloader and having root?
The lineage-18.1-20210606-recovery-instantnoodlep.img is no longer available though. Help
Wow! This was so easy and so quick. Thank you SOO MUCH!
arfhel09 said:
The lineage-18.1-20210606-recovery-instantnoodlep.img is no longer available though. Help
Click to expand...
Click to collapse
I just googled the file name and found a mirror with new images. Google is your friend, as they say.
LineageOS Downloads
download.lineageos.org
How can I root latest version (11.0.8.8) with magisk?
Sneakdovi said:
How can I root latest version (11.0.8.8) with magisk?
Click to expand...
Click to collapse
same thing, since there is nothing specified for the OS version ONLY OOS 11.
im going to flash this to 11.0.8.8, if u want to wait or u can try it and report back before I do ^^
Edit-------------
I successfully rooted my phone ver 11.0.8.8 using this method with latest lineage recovery
STALKER18 said:
same thing, since there is nothing specified for the OS version ONLY OOS 11.
im going to flash this to 11.0.8.8, if u want to wait or u can try it and report back before I do ^^
Edit-------------
I successfully rooted my phone ver 11.0.8.8 using this method with latest lineage recovery
Click to expand...
Click to collapse
Same