[Mini Guide] How to root 8.1 - Google Pixel XL Guides, News, & Discussion

The current version of TWRP will not accept your pin/password on 8.1. Until we get an update to TWRP there are a couple of work arounds.
One option is totally wipe your phone and root it before you set up a pin/password/fingerprint.
The other option is to get a thumb drive and a USB to C adapter from Best Buy or elsewhere. Put SU on the thumb drive, boot to TWRP img with fastboot as you normally do and then plug in the thumb drive to the phone. In twrp you will see an option to select storage, select the OTG USB Drive and you can install SU from there.
Edit. As of Jan 1 it looks like SU is no longer working. I have switched to Magisk without issue.

Good to know! Kudos

Which version of TWRP and SU did you use? Is it possible to install custom kernel on 8.1.?Thank you ?

veskostoev said:
Which version of TWRP and SU did you use? Is it possible to install custom kernel on 8.1.?Thank you ?
Click to expand...
Click to collapse
3.1.1.1 TWRP and 2.82 SR5 SU. The latest of both. So far I have not gotten EX to work, it boot loops. Going to try a couple of things after dinner but I expect it will fail.

Actually, you could use the old fastboot boot boot-to-root method used on 8.0 dev. It also works on 8.1 dev. Then you could use Flashfire to flash the latest SuperSU SR5 as the boot-to-root SuperSU version is an old one (SR1). Remember to choose Auto Mount option. Works for me, hope it helps you guys.

I tried flash fire but couldn't seem to get it to work. I just get a black screen. I know it says this is normal and it should come up after half a minute. I gave it a few minutes and never got anything other than the black screen. Did you get this screen? How long did it last?
EDIT- nevermind just did it with TWRP

TonikJDK said:
One option is totally wipe your phone and root it before you set up a pin/password/fingerprint.
Click to expand...
Click to collapse
I'm assuming after it is rooted, you can enable PIN/fingerprint? If so, what happens when the next dev build comes out, you will have to wipe again and setup without a pin/fingerprint and then add again, or hope TWRP is updated by then?

Here is what I did to get root on 8.1:
1: Flash factory image of 8.1 WITH the "-w" (wipe) command
2: Boot up and set up the system (and updated apps while I was there)
3: Reboot into bootloader
4: fastboot BOOT TWRP 3.1.1-1
5: Flash TWRP 3.1.1-1
6: Reboot to recovery
7: Flash Magisk v14.3
8: Reboot to Android
I'm now running 8.1 with Magisk v14.3, and root it working as it should. I also have TWRP 3.1.1-1 installed, functional, and accessible via reboot without the need for a computer.

I just adb sideloaded the latest Magisk beta after the data decryption failed and I have root.

cleeezzz said:
I just adb sideloaded the latest Magisk beta after the data decryption failed and I have root.
Click to expand...
Click to collapse
How? It fails signature verification when I try

Rooted with SU and usb stick works perfectly. Thank you very much.

chevycam94 said:
Here is what I did to get root on 8.1:
1: Flash factory image of 8.1 WITH the "-w" (wipe) command
2: Boot up and set up the system (and updated apps while I was there)
3: Reboot into bootloader
4: fastboot BOOT TWRP 3.1.1-1
5: Flash TWRP 3.1.1-1
6: Reboot to recovery
7: Flash Magisk v14.3
8: Reboot to Android
I'm now running 8.1 with Magisk v14.3, and root it working as it should. I also have TWRP 3.1.1-1 installed, functional, and accessible via reboot without the need for a computer.
Click to expand...
Click to collapse
where to find 14.3 zip? i found only version 14..or you mean to flash 14 and to update the app to v. 14.3?

chevycam94 said:
Here is what I did to get root on 8.1:
1: Flash factory image of 8.1 WITH the "-w" (wipe) command
2: Boot up and set up the system (and updated apps while I was there)
3: Reboot into bootloader
4: fastboot BOOT TWRP 3.1.1-1
5: Flash TWRP 3.1.1-1
6: Reboot to recovery
7: Flash Magisk v14.3
8: Reboot to Android
I'm now running 8.1 with Magisk v14.3, and root it working as it should. I also have TWRP 3.1.1-1 installed, functional, and accessible via reboot without the need for a computer.
Click to expand...
Click to collapse
it works! thanks! :good:

galza said:
where to find 14.3 zip? i found only version 14..or you mean to flash 14 and to update the app to v. 14.3?
Click to expand...
Click to collapse
No, just flash Magisk the first time. No need to do any updates.
https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589

chevycam94 said:
Here is what I did to get root on 8.1:
1: Flash factory image of 8.1 WITH the "-w" (wipe) command
2: Boot up and set up the system (and updated apps while I was there)
3: Reboot into bootloader
4: fastboot BOOT TWRP 3.1.1-1
5: Flash TWRP 3.1.1-1
6: Reboot to recovery
7: Flash Magisk v14.3
8: Reboot to Android
I'm now running 8.1 with Magisk v14.3, and root it working as it should. I also have TWRP 3.1.1-1 installed, functional, and accessible via reboot without the need for a computer.
Click to expand...
Click to collapse
Great method just did that and working flawless thanks mate

chevycam94 said:
Here is what I did to get root on 8.1:
1: Flash factory image of 8.1 WITH the "-w" (wipe) command
2: Boot up and set up the system (and updated apps while I was there)
3: Reboot into bootloader
4: fastboot BOOT TWRP 3.1.1-1
5: Flash TWRP 3.1.1-1
6: Reboot to recovery
7: Flash Magisk v14.3
8: Reboot to Android
I'm now running 8.1 with Magisk v14.3, and root it working as it should. I also have TWRP 3.1.1-1 installed, functional, and accessible via reboot without the need for a computer.
Click to expand...
Click to collapse
I know this may sound stupid, but is there a more complete guide to this? I was able to root on 8.0, but I'm not sure I understand your method. Do I just type these commands into adb?

Juzman said:
I'm assuming after it is rooted, you can enable PIN/fingerprint? If so, what happens when the next dev build comes out, you will have to wipe again and setup without a pin/fingerprint and then add again, or hope TWRP is updated by then?
Click to expand...
Click to collapse
That would interest me also whether it is then possible to use fingerprint without the Twrp no longer goes.

DarthScabrous said:
I know this may sound stupid, but is there a more complete guide to this? I was able to root on 8.0, but I'm not sure I understand your method. Do I just type these commands into adb?
Click to expand...
Click to collapse
I might make a quick guide this afternoon. Got a few things I need to get done first. But I'll make another guide.

chevycam94 said:
Here is what I did to get root on 8.1:
1: Flash factory image of 8.1 WITH the "-w" (wipe) command
2: Boot up and set up the system (and updated apps while I was there)
3: Reboot into bootloader
4: fastboot BOOT TWRP 3.1.1-1
5: Flash TWRP 3.1.1-1
6: Reboot to recovery
7: Flash Magisk v14.3
8: Reboot to Android
I'm now running 8.1 with Magisk v14.3, and root it working as it should. I also have TWRP 3.1.1-1 installed, functional, and accessible via reboot without the need for a computer.
Click to expand...
Click to collapse
Worked perfect for me. Since I setup phone, fingerprint and pin before I installed TWRP and magisk, it bootlooped.
So, I re-flashed the 8.1, and then followed steps 3-8.
Thanks!

bradhoschar said:
Worked perfect for me. Since I setup phone, fingerprint and pin before I installed TWRP and magisk, it bootlooped.
So, I re-flashed the 8.1, and then followed steps 3-8.
Thanks!
Click to expand...
Click to collapse
Would deleting fingerprint / security, etc before rebooting resolve the TWRP lock issue?

Related

Oneplus 5 TWRP and Root Issues

Oneplus 5, Official ROM, H2OS, Android 7.1
1. First time, I followed https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-unlock-bootloader-flash-twrp-t3624877 and successfully install TWRP and root using Supersu. I can goes into TWRP recovery without any problem. I notice that the supersu I installed in a systemless one, some apps can't get root access, like AD Away, Titanium Backup. But most apps can work with it. I used the one of the two root method in that tutorial as follows:
For Users who want to remain Encrypted:
1. Boot into TWRP Recovery and allow system modifications.
2. Swipe right and enable modifications.
3. Select your preferred Language, Tap “Never show this screen on boot again,” and Swipe allow modification.
4. Navigate to Install and select Magisk Or SuperSU to root OnePlus 5.
5. Swipe to confirm the flash
6. Reboot System
Click to expand...
Click to collapse
2. After several months I want to upgrade the original H2OS to new version, so I unroot in Supersu first, when it ask me if I want to recover Boot Image, I say "Yes", and say "NO" when ask me if I want to recover Recovery Image. Then I upgrade to the new H2OS v13 (Android 7.1) using the Full package through TWRP, after that I reinstall TWRP 3.2.1, it was successful. But it doesn't ask me to allow it to make modification. I tried to install Supersu 2.82 and 2.82 SR5 using the same method as in tutorial, at the end of "Booting Image patcher" it shows
.........
-Calling user ramdisk patch script
---Failure, aborting
-Unmounting /system and /vender
-Done
Click to expand...
Click to collapse
Then I reboot to recovery, it return to official REC, not TWRP, and system says there is no root.
netsonic said:
Oneplus 5, Official ROM, H2OS, Android 7.1
1. First time, I followed https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-unlock-bootloader-flash-twrp-t3624877 and successfully install TWRP and root using Supersu. I can goes into TWRP recovery without any problem. I notice that the supersu I installed in a systemless one, some apps can't get root access, like AD Away, Titanium Backup. But most apps can work with it. I used the one of the two root method in that tutorial as follows:
2. After several months I want to upgrade the original H2OS to new version, so I unroot in Supersu first, when it ask me if I want to recover Boot Image, I say "Yes", and say "NO" when ask me if I want to recover Recovery Image. Then I upgrade to the new H2OS v13 (Android 7.1) using the Full package through TWRP, after that I reinstall TWRP 3.2.1, it was successful. But it doesn't ask me to allow it to make modification. I tried to install Supersu 2.82 and 2.82 SR5 using the same method as in tutorial, at the end of "Booting Image patcher" it shows
Then I reboot to recovery, it return to official REC, not TWRP, and system says there is no root.
Click to expand...
Click to collapse
Just use the latest universal codeworks recovery and flash it via fastboot.
For root i suggest use of Magisk over Su, the latest 15.3 works fine for me.
What is the codeworks recovery? Is it "twrp-3.2.1-0-cheeseburger.img" on https://twrp.me/oneplus/oneplus5.html?
netsonic said:
What is the codeworks recovery? Is it "twrp-3.2.1-0-cheeseburger.img" on https://twrp.me/oneplus/oneplus5.html?
Click to expand...
Click to collapse
No, it's the -universal- one from here https://forum.xda-developers.com/on...overy-twrp-3-2-1-0-oreo-oxygenos-5-0-t3725723
I can flash universal TWRP and Magisk 15.3. But Magisk show "SafetyNet API Error"? How to fix it?

Android 10, root working

Pretty straight forward for those of us who like a nice clean flash. Not you dirty dogs.
1 clean flash lastest Android 10 factory image and install
2 setup the device don't set a password or pin
Install latest canary Magisk manager
3 pull the boot.img out of the Factory image zip.
4 move the boot image to phone internal storage
Patch boot.img with Magisk.
5 download latest twrp.img and fastboot boot it
Install the patches boot.img to your boot
Mount opposite partition if A then mount b, if b mount a
Ignore the error.
And repeat flashing patched boot.img like you did the first time
Mount original partition reboot. And boom
So installing the magisk canary build via zip in TWRP does not work?
---------- Post added at 04:07 PM ---------- Previous post was at 04:05 PM ----------
Also, did you use .019 or .020 build from the factory image website?
ne0ns4l4m4nder said:
Pretty straight forward for those of us who like a nice clean flash. Not you dirty dogs.
1 clean flash lastest Android 10 factory image and install
2 setup the device don't set a password or pin
Install latest canary Magisk manager
3 pull the boot.img out of the Factory image zip.
4 move the boot image to phone internal storage
Patch boot.img with Magisk.
5 download latest twrp.img and fastboot boot it
Install the patches boot.img to your boot
Mount opposite partition if A then mount b, if b mount a
Ignore the error.
And repeat flashing patched boot.img like you did the first time
Mount original partition reboot. And boom
Click to expand...
Click to collapse
Is patching the boot.img in magisk mentioned in step 4 an option in magisk? How do I "patch" the boot image?
How do I do this portion of step 5?:
Install the patches boot.img to your boot
Mount opposite partition if A then mount b, if b mount a
Does magisk store the patched boot image somewhere (and it tells you where) that is accessible in TWRP? then we need only go to that file path in TWRP under the "install" tab?
What does this mean?:
And repeat flashing patched boot.img like you did the first time
Do you mean on the partition you were originally on?
So if we're on A, mount B, install the patched boot image on A, remount A, install the patched boot image on B, and then reboot?
How do we "install to th boot?"
I used the .20 from the factory. And Magisk saves the patches boot.img for me in downloads, which I can access in twro
Good instructions but you don't even need TWRP if you want to save time. I just patched the boot.img with the Canary. 20 Magisk build and moved it over to my pc so that I could just flash it using the fastboot flash boot boot.img command. Worked like a champ and did not have to disable my security pin and jack with mounting A or B with TWRP.
I just flashed .20
Booted it once.
Then using fastboot I booted twrp, installed magisk 19.3
and Im rooted.
?* lol w.e works ?
Which magisk modules are workings?
tweaked said:
I just flashed .20
Booted it once.
Then using fastboot I booted twrp, installed magisk 19.3
and Im rooted.
Click to expand...
Click to collapse
Clean or dirty flash of A10?
I just flashed the canary magisk zip (from a booted/not installed TWRP) and it was fine... I didn't go through any extra steps.
hmm so now i have root following these instructions, but i cant seem to do much with it.. i cant seem to make system rw. cant edit build.prop to enable tether, cant edit host files for adaway. those are the two reasons i root, and neither seem to work.
edit: got adaway to work, needed to enable systemless hosts in magisk settings, reboot, then adaway works.
phyl0x said:
hmm so now i have root following these instructions, but i cant seem to do much with it.. i cant seem to make system rw. cant edit build.prop to enable tether, cant edit host files for adaway. those are the two reasons i root, and neither seem to work.
edit: got adaway to work, needed to enable systemless hosts in magisk settings, reboot, then adaway works.
Click to expand...
Click to collapse
I just flashed the factory image without the -W let it boot. Rebooted back to fastboot, booted Twrp, Flashed Twrp, Flashed magisk 19.3. All modules are working including Adaway except for the active edge mod.
dmarden said:
I just flashed the canary magisk zip (from a booted/not installed TWRP) and it was fine... I didn't go through any extra steps.
Click to expand...
Click to collapse
Which Canary please?
humdrum2009 said:
Which Canary please?
Click to expand...
Click to collapse
https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337
tweaked said:
I just flashed .20
Booted it once.
Then using fastboot I booted twrp, installed magisk 19.3
and Im rooted.
Click to expand...
Click to collapse
Did the same coming from 9.
What was new for me was the android 'no command' screen; power+volume-up -> menu .
Also had to reinstall Magisk in the manager (19.3), even as it was already installed, to get AdAway (systemless) to be able to alter the hosts.
Adb recognizes my phone and I manage to restart bootloader, but when I try to boot TWRP img it says "waiting for a device.."
What is wrong?
phyl0x said:
hmm so now i have root following these instructions, but i cant seem to do much with it.. i cant seem to make system rw. cant edit build.prop to enable tether, cant edit host files for adaway. those are the two reasons i root, and neither seem to work.
edit: got adaway to work, needed to enable systemless hosts in magisk settings, reboot, then adaway works.
Click to expand...
Click to collapse
I got tethering working (Verizon grandfathered unlimited plan)
1. Magisk -> Downloads -> MagiskHide Props Config
2. Magisk -> Downloads -> BusyBox
3. Reboot
4. Adb shell -> type ‘props'
5. Select ‘5’ -> ’net.tethering.noprovisioning’ -> y -> y
6. Wait for reboot
7. Adb shell -> settings put global tether_dun_required 0
8. Reboot
Adaway and tethering are my only reasons to be rooted as well. Glad both are working now on 10.
barski said:
I got tethering working (Verizon grandfathered unlimited plan)
1. Magisk -> Downloads -> MagiskHide Props Config
2. Magisk -> Downloads -> BusyBox
3. Reboot
4. Adb shell -> type ‘props'
5. Select ‘5’ -> ’net.tethering.noprovisioning’ -> y -> y
6. Wait for reboot
7. Adb shell -> settings put global tether_dun_required 0
8. Reboot
Adaway and tethering are my only reasons to be rooted as well. Glad both are working now on 10.
Click to expand...
Click to collapse
Awesome, yeah I am in the exact same boat as you, thanks for sharing that I will probably take the plunge and root as well. Which magisk version and twrp versions you use?
What kernel if any?
I'm running 10 now with root, I just flashed the latest canary build in twrp, didn't need to modify anything else. I do have a question though, has anybody been able to load up Titanium Backup? It just keeps crashing for me.
murphyjasonc said:
I just flashed the factory image without the -W let it boot. Rebooted back to fastboot, booted Twrp, Flashed Twrp, Flashed magisk 19.3. All modules are working including Adaway except for the active edge mod.
Click to expand...
Click to collapse
This is the way i usually root my device as well.
Flash a fresh rom
fastboot boot twrp.img
flash twrp.zip in twrp, reboot recovery
flash magisk.zip in twrp
reboot.
However after i flashed twrp then rebooted into it, the touch screen wouldn't work. I had to hold power + vol down to reboot into fastboot then i did the boot into twrp.img again and then i flashed magisk from there.
I have no idea why the flashed twrp is not working with the touchscreen. The twrp img and the twrp zip that i used were version 3.3.0-0 and magisk was 19.3.
In Magisk manager it says it is installed properly and that safety net check passes.

October Security Patch has been posted

October Security Patch has been posted.
What is the size of this update? I received only 7.1mb update ?
astaineakash said:
What is the size of this update? I received only 7.1mb update
Click to expand...
Click to collapse
I don't know. Flashed the full image from Google.
in Germany, the update is also so big
astaineakash said:
What is the size of this update? I received only 7.1mb update
Click to expand...
Click to collapse
Yes, it is 7.1 MB. Strange.
Wow huge update! My WiFi couldn't cope up with 7.1mb update. Awesome Google ?
Nothing here yet, T-Mobile, Houston.
Edit: received OTA last evening 10/08. I believe the size was 7.4mb.
Sent from my [device_name] using XDA-Developers Legacy app
yes the ota is 7.1mb, i have root so i tired to uninstall magisk (restoring images) then applying the ota then reinstalling magisk then reboot but didnt work as system update error couldnt install, also tried to boot to twrp then sideload the ota zip but caused problems and was about to lose my data (storage didnt show up in twrp) but i played around and changed boot slot and storage showed up again so i flashed factory image without -w and reflashed magisk and kernel
Nightf0x_007 said:
yes the ota is 7.1mb, i have root so i tired to uninstall magisk (restoring images) then applying the ota then reinstalling magisk then reboot but didnt work as system update error couldnt install, also tried to boot to twrp then sideload the ota zip but caused problems and was about to lose my data (storage didnt show up in twrp) but i played around and changed boot slot and storage showed up again so i flashed factory image without -w and reflashed magisk and kernel
Click to expand...
Click to collapse
Dude sometimes this phone just needs a little extra... Lol glad you kept your cool and hung in there.
Sent from my Pixel 2 XL using XDA Labs
Nightf0x_007 said:
yes the ota is 7.1mb, i have root so i tired to uninstall magisk (restoring images) then applying the ota then reinstalling magisk then reboot but didnt work as system update error couldnt install, also tried to boot to twrp then sideload the ota zip but caused problems and was about to lose my data (storage didnt show up in twrp) but i played around and changed boot slot and storage showed up again so i flashed factory image without -w and reflashed magisk and kernel
Click to expand...
Click to collapse
How did you "reflash magisk and kernel?" Did you boot to system first?
astaineakash said:
What is the size of this update? I received only 7.1mb update ?
Click to expand...
Click to collapse
Me too
jlokos said:
How did you "reflash magisk and kernel?" Did you boot to system first?
Click to expand...
Click to collapse
Yes after flashing factory image without wiping, i booted up to system then checked magisk wasnt installed (only manager app), then i fastbooted to twrp recovery flashed custom kernel then flashed magisk and reboot, thats it, and all my magisk settings returned back to what it was like before all this
Can anyone please post the fingerprint for the October build from build.prop?
Much thanks!!
Any easy way to install this on a rooted phone without wiping data?
Dylan.4 said:
Any easy way to install this on a rooted phone without wiping data?
Click to expand...
Click to collapse
First, YMMV! Make backups, always.
Here's my process. It's worked for me for a good while now. My main goal was to do this all on-device, without using a computer or other ADB source. It assumes you keep TWRP installed.
1. Download the full OTA from Google. This is the one in a recovery flashable package, not the fastboot script one.
2. Download the TWRP installer.
3. Download the latest Magisk installer.
4. Turn off the screen lock. TWRP doesn't like it, and won't see the internal storage elsewise.
5. Boot to TWRP recovery.
6. Install the OTA zip via TWRP. DO NOT REBOOT NOW!
7. Install the TWRP recovery zip.
8. Reboot. I like to let Android boot all the way before I install Magisk. It may not be completely necessary, but I believe you have to switch the A/B slot in TWRP if you don't, before installing.
9. Boot to TWRP recovery again.
10. Install the Magisk zip.
11. Re-enable your security, including re-adding your fingerprints if you use them.
If you want to use an additional computer, just fastboot the full images after removing the "-w" from the bat file, fastboot boot to TWRP, then re-install TWRP (if desired) and Magisk.
Since October patch (rooted) I have massive problems my pc/my phone detecting my phone/my pc. I dont know why, its just charging, one time it worked (I need USB-Tethering) I was just restarting and restarting the phone, turning debugging on/off...
Any idea how to fix this?
edit: It just says unknown usb-device, I manually uninstalled and installed the latest android usb drivers. If I try to use an adb command it just says "error: no devices/emulators found"
Probably the worst security patch. My sensors aren't working properly, phone doesn't go off while i talk. It hangs at odd occasions. Battery is weak. Auto brightness isn't working either
hawkjm73 said:
First, YMMV! Make backups, always.
Here's my process. It's worked for me for a good while now. My main goal was to do this all on-device, without using a computer or other ADB source. It assumes you keep TWRP installed.
1. Download the full OTA from Google. This is the one in a recovery flashable package, not the fastboot script one.
2. Download the TWRP installer.
3. Download the latest Magisk installer.
4. Turn off the screen lock. TWRP doesn't like it, and won't see the internal storage elsewise.
5. Boot to TWRP recovery.
6. Install the OTA zip via TWRP. DO NOT REBOOT NOW!
7. Install the TWRP recovery zip.
8. Reboot. I like to let Android boot all the way before I install Magisk. It may not be completely necessary, but I believe you have to switch the A/B slot in TWRP if you don't, before installing.
9. Boot to TWRP recovery again.
10. Install the Magisk zip.
11. Re-enable your security, including re-adding your fingerprints if you use them.
If you want to use an additional computer, just fastboot the full images after removing the "-w" from the bat file, fastboot boot to TWRP, then re-install TWRP (if desired) and Magisk.
Click to expand...
Click to collapse
Perfect, it worked. Thank you!

So how to root Android 10?

If we don't have TWRP,
How do we root the device?
Magisk has the option to patch a boot.img file. Technically, you could:
1. pull the boot.img file from the A10 OB1 zip
2. copy it to the phone's internal storage
3. install latest magisk manager, click on install - patch boot.img - choose the boot.img
4. copy the patched boot.img to a pc with ADB and USB drivers
5. put the phone in fastboot mode, sideload the boot.img
I have no idea if this would work, but you could give it a go. I believe that someone else already made a guide for exactly this here in the OP6T forum.
Refer to the twrp thread for OB 10.
https://forum.xda-developers.com/oneplus-6t/help/how-to-flash-twrp-android-10-beta-1-t3986345
Either do the OTA local upgrade and magisk uninstall then install to inactive slot method, or use the boot patch which there is another thread on that on the ROM Dev section.
I used the first, worked fine. But there is no supported twrp yet. Only magisk root is officially supported on Q.
Hello, After Root, it's impossible for me to boot on recovery mode
Always i'll want to do or, thé phone reboot on fastmode.
g4seb said:
Hello, After Root, it's impossible for me to boot on recovery mode
Always i'll want to do or, thé phone reboot on fastmode.
Click to expand...
Click to collapse
Yes, likely because the update flashed to the inactive, and there is no recovery now. So...if you want recovery, only way is to full wipe and do a MSM or flash all and wipe with older stable.
OP support/forums made announcements on their thread on what will happen with upgrading, or rolling back.
They have a rollback file you can download if you want it all working again including recovery. But you will get wiped as mentioned, and be back on the last stable and firmware. Then you can twrp and root all over again.
That is Beta testing for you!!

Android 11 is live.

Today just received update notification as below image. Downloading now, let see what are changes and improvements.
I'm enrolled in beta for Android 11 and got the September Security patch today. Will I get the stable release soon or should I opt out from beta and go for a fresh instal?
TenTuTego said:
I'm enrolled in beta for Android 11 and got the September Security patch today. Will I get the stable release soon or should I opt out from beta and go for a fresh instal?
Click to expand...
Click to collapse
You are automatically switched to the stable release. Check in your "About" settings.
tkachenko.ic said:
You are automatically switched to the stable release. Check in your "About" settings.
Click to expand...
Click to collapse
I have readed yesterday that, when Android 11 Stable is released, u can stay on beta program for beta features and experimental updates, also you can receive updates earlier than others.
Has anyone been able to successfully root using Magisk? I tried and bootlooped.
Edit: Magisk Canary works, but you CANNOT install TWRP as it hasn't been developed to work with A11 yet.
socal87 said:
Has anyone been able to successfully root using Magisk? I tried and bootlooped.
Click to expand...
Click to collapse
Use magisk canary
Anyone have the screen record enabled in power menu and how ?
khanhcc said:
Use magisk canary
Click to expand...
Click to collapse
not working for pixel2, same bootloop
monikmax said:
not working for pixel2, same bootloop
Click to expand...
Click to collapse
Are you using a custom recovery? TWRP does not work with A11 yet.
Extract the boot image from a factory ZIP and flash it in bootloader:
Code:
fastboot flash boot "boot.img"
Then, boot TWRP:
Code:
fastboot boot "twrp.img"
And install Magisk using the canary zip. Please note that you do not use the quotation marks.
Alternatively, you can boot to TWRP and sideload the OTA, then reboot to bootloader, boot TWRP again, and install Magisk.
V0latyle said:
Are you using a custom recovery? TWRP does not work with A11 yet.
Extract the boot image from a factory ZIP and flash it in bootloader:
Code:
fastboot flash boot "boot.img"
Then, boot TWRP:
Code:
fastboot boot "twrp.img"
And install Magisk using the canary zip. Please note that you do not use the quotation marks.
Alternatively, you can boot to TWRP and sideload the OTA, then reboot to bootloader, boot TWRP again, and install Magisk.
Click to expand...
Click to collapse
Magisk is installed, but after patched boot applied phone is bootlooping.
any ideas?
monikmax said:
Magisk is installed, but after patched boot applied phone is bootlooping.
any ideas?
Click to expand...
Click to collapse
You must use the Magisk Canary zip on the stock boot image. Regular Magisk will not work.
V0latyle said:
You must use the Magisk Canary zip on the stock boot image. Regular Magisk will not work.
Click to expand...
Click to collapse
Could you describe the procedure or write out the steps for rooting our device running on Android 11?
SoloMid Hazard said:
Could you describe the procedure or write out the steps for rooting our device running on Android 11?
Click to expand...
Click to collapse
Your bootloader must be unlocked to use this method.
Start fresh, use the OTA or the factory image. I did this coming from Android 10 without wiping.
Download the Magisk Manager Canary APK and installer ZIP here
Download the latest TWRP image here, put it in your platform tools folder and rename to twrp.img
Using platform tools, reboot your phone into bootloader:
Code:
adb reboot bootloader
Then, boot (DO NOT INSTALL) TWRP:
Code:
fastboot boot twrp.img
Install the Magisk Canary ZIP, reboot to system.
Yes I am using canary latest, and did everything as you explaining, still getting bootloop. But I will get done sooner or later )
hemal_4404 said:
Today just received update notification as below image. Downloading now, let see what are changes and improvements.
Click to expand...
Click to collapse
I am trying to screen record by the official android screen recorder app my phone doesn't records the video afte the recording is done and played laters only one thing pops in the video "gboard encountered a problem" and the same thing comes up whenever I try to record. Is someone facing the same issue?
V0latyle said:
Your bootloader must be unlocked to use this method.
Start fresh, use the OTA or the factory image. I did this coming from Android 10 without wiping.
Download the Magisk Manager Canary APK and installer ZIP here
Download the latest TWRP image here, put it in your platform tools folder and rename to twrp.img
Using platform tools, reboot your phone into bootloader:
Code:
adb reboot bootloader
Then, boot (DO NOT INSTALL) TWRP:
Code:
fastboot boot twrp.img
Install the Magisk Canary ZIP, reboot to system.
Click to expand...
Click to collapse
+1 on this method, worked for me, thank you for the instructions
I'm also bootlooping. Did you solve your problem?
I installed through the OTA button. Of course, I lost root, so I followed the above instructions, but am stuck at the G loading.
The canary zip is magisk-debug.zip, correct?
EDIT: I overlooked that I had EdXposed installed with active modules and I don't think it works with Android 11 yet, at least not the modules I use (Gravity box). I'll try rooting again tonight with EdXposed modules disabled.
Chilipepprflea said:
I'm also bootlooping. Did you solve your problem?
I installed through the OTA button. Of course, I lost root, so I followed the above instructions, but am stuck at the G loading.
The canary zip is magisk-debug.zip, correct?
EDIT: I overlooked that I had EdXposed installed with active modules and I don't think it works with Android 11 yet, at least not the modules I use (Gravity box). I'll try rooting again tonight with EdXposed modules disabled.
Click to expand...
Click to collapse
Yes, both the apk and the zip are named "magisk_debug".
I am not sure why you are bootlooping. If you installed the OTA, it should have overwritten /boot with the stock image, and flashing Magisk Canary should work. It is possible that if you had modules enabled before and didn't disable them, you could have issues.
V0latyle said:
Yes, both the apk and the zip are named "magisk_debug".
I am not sure why you are bootlooping. If you installed the OTA, it should have overwritten /boot with the stock image, and flashing Magisk Canary should work. It is possible that if you had modules enabled before and didn't disable them, you could have issues.
Click to expand...
Click to collapse
I disabled the edxposed modules and still got stuck at the G logo. I'm not sure what else I could be doing wrong, but it's obviously me or my setup. I'm going to downgrade to Android 10 because the modifications I rely on from GravityBox are more important to me than the new features of Android 11.
Thanks for the help.
Chilipepprflea said:
I disabled the edxposed modules and still got stuck at the G logo. I'm not sure what else I could be doing wrong, but it's obviously me or my setup. I'm going to downgrade to Android 10 because the modifications I rely on from GravityBox are more important to me than the new features of Android 11.
Thanks for the help.
Click to expand...
Click to collapse
Anyone have luck downgrading from 11 to 10? I've tried several different 10 builds and I get "Error: Slot Unbootable: Load Error" in bootloader.
I used the same commands I always use to upgrade builds:
fastboot flash radio radio-walleye-...img
fastboot reboot bootloader
fastboot update image-walleye-...zip
I can flash 11 again and all is fine, but I haven't been able to go back to 10.

Categories

Resources