Database Users

SuperSU added support for Pixel C -> BETA-SuperSU-v2.72-20160510112018.zip

http://forum.xda-developers.com/showpost.php?p=64916199&postcount=3
Changelogs
10.05.2016 - v2.72 - BETA - RELEASE NOTES
- Add support for ChromeOS boot images (Pixel C)
- supolicy: Fix logging to logcat for some processes on some firmwares
- supolicy: Fix fsck of /data/su.img being denied on some firmwares
- ZIP: Add LESSLOGGING flag
- ZIP: Add KEEPVERITY flag
- ZIP: Add KEEPFORCEENCRYPT flag
- ZIP: Also read flags from /cache/.supersu (aside from /data/.supersu and /system/.supersu)
Yes, baby !

wow! That's a surprise!

BaristaBot said:
wow! That's a surprise!
Click to expand...
Click to collapse
Indeed .. but now we have support.
Just tested 2.72 .. works perfectly.
Installed stock boot.img via TWRP and Supersu.zip directly afterwards ..
Supersu.zip is perfectly modifying the ramdisk and re-signing the kernel to chromeos.
Tested xceed kernel and my pre-rooted kernel too.
Supersu will not modify the ramdisk at all.
"Can't find stock Image, already modified .." and will stop the ramdisk installer.
The system will start anyway, but with "old" ramdisk modifications.
So a fresh clean stock boot.img is recommended.
Install it via TWRP, just before the supersu.zip installation.
No reboot required, nothing.
Download from here ..
http://forum.xda-developers.com/pixel-c/development/twrp-flashable-monthly-update-zip-pixel-t3375591
Running on 2.72 now ... we don't need to build any stock rooted kernels anymore.
Don't be surprised .. after Supersu.zip installation the first boot will look like bootloop, but only once. Same like on other devices as well.
Cheers

After flashing a stock android N preview 2, I installed TWRP and flashed the superSU ZIP (2.72). I can confirm this works perfectly, and i have root on android N preview 2

@NYCHitman1 @cheep5k8 Did you see this? Great news eh?

Samt434 said:
After flashing a stock android N preview 2, I installed TWRP and flashed the superSU ZIP (2.72). I can confirm this works perfectly, and i have root on android N preview 2
Click to expand...
Click to collapse
Great! I'd like to give the N preview a try now, too. Could you please elaborate on how you achieved root with the new SuperSU? Did you have to reflash a custom recovery after flashing Android N?

Which version of TWRP should be used as there are alot of other versions around thats not clear which one is working?

scoobydu said:
Which version of TWRP should be used as there are alot of other versions around thats not clear which one is working?
Click to expand...
Click to collapse
This one
TWRP_dragon_3.0.2-0_v2.img
- Added vendor.img flashing via TWRP. (thx to NYCHitman1 )
Download: https://onedrive.live.com/?authkey=!ABLdSOKIeXgg_XU&id=479EB75F5DD9DA59!117&cid=479EB75F5DD9DA59
Cheers

followmsi said:
This one
TWRP_dragon_3.0.2-0_v2.img
- Added vendor.img flashing via TWRP. (thx to NYCHitman1 )
Download: https://onedrive.live.com/?authkey=!ABLdSOKIeXgg_XU&id=479EB75F5DD9DA59!117&cid=479EB75F5DD9DA59
Cheers
Click to expand...
Click to collapse
Using this version, TWRP loads but it cannot see my files on the internal sdcard, so I cannot install supersu, or anything else for that matter.
Not sure what I am missing.
Edit: Ok, didn't do the format data piece doing that now
Edit2: I managed to boot with boot-ryu-MXC89F-su-nocrypt-r205 and then copy the latest supersu to my sdcard. I rebooted into TWRP and installed Supersu successfully. Rebooted to system resulted in a boot loop to recovery?
Going into security to check encryption status causes setting to fc.
Edit 3 [Resolved] Copied the only kernel that would boot, as well as the clean boot.img from the latest factory images. Booted into TWRP and first flashed the clean boot.image from the factory images and then installed supersu successfully this time. I tried before with the boot.img from here -> http://superuser.phh.me/nexus/ryu/MXC89F/ but couldn't get supersu to install.
@Chainfire Thanks!! for supersu and flashfire support.

Great news! Any idea if supersu works with complete stock and encryption enabled?
And TWRP_dragon_3.0.2-0_v2.img doesn't solve the encryption problem yet, right?

doumer said:
Great news! Any idea if supersu works with complete stock and encryption enabled?
And TWRP_dragon_3.0.2-0_v2.img doesn't solve the encryption problem yet, right?
Click to expand...
Click to collapse
For me on a previously unrooted encrypted device I couldn't get it to work by just installing it and supersu, no.
But that may have been user error on my part, but my guess is that encryption was causing an issue with just the v2 TWRP installed as it could not see my data partition, even after a format.

scoobydu said:
Using this version, TWRP loads but it cannot see my files on the internal sdcard, so I cannot install supersu, or anything else for that matter.
Not sure what I am missing.
Edit: Ok, didn't do the format data piece doing that now
Edit2: I managed to boot with boot-ryu-MXC89F-su-nocrypt-r205 and then copy the latest supersu to my sdcard. I rebooted into TWRP and installed Supersu successfully. Rebooted to system resulted in a boot loop to recovery?
Going into security to check encryption status causes setting to fc.
Edit 3 [Resolved] Copied the only kernel that would boot, as well as the clean boot.img from the latest factory images. Booted into TWRP and first flashed the clean boot.image from the factory images and then installed supersu successfully this time. I tried before with the boot.img from here -> http://superuser.phh.me/nexus/ryu/MXC89F/ but couldn't get supersu to install.
@Chainfire Thanks!! for supersu and flashfire support.
Click to expand...
Click to collapse
Three lines above your thread ..
Tested xceed kernel and my pre-rooted kernel too.
Supersu will not modify the ramdisk at all.
"Can't find stock Image, already modified .." and will stop the ramdisk installer.
The system will start anyway, but with "old" ramdisk modifications.
So a fresh clean stock boot.img is recommended.
As well the Phhuson kernel is not pre-rooted for SuperSU.
( boot-ryu-MXC89F-su-nocrypt-r205 )
NEW Root access:
For root access: Pls install latest "stock" kernel and install SuperSU.zip version 2.72 directly afterwards - no reboot in between.
Hope this help all people in the same situation ..
Cheers

doumer said:
Great news! Any idea if supersu works with complete stock and encryption enabled?
And TWRP_dragon_3.0.2-0_v2.img doesn't solve the encryption problem yet, right?
Click to expand...
Click to collapse
Yes, it doesn´t solve the problem ..
There were no encryption related changes in this TWRP release.
But .... we have a new SuperSU now ..
Look here .. should be tested from the encryption fans .. Maybe this works on Pixel C too.
http://forum.xda-developers.com/htc...bootloader-t3365986/post66837323#post66837323
EDIT 2: Figured I might as well detail my complete procedure here, so others can confirm whether it works for them (or not):
Unlocked bootloader via HTC Dev
Flash TWRP
Boot into TWRP (Cancel decryption prompt & leave system read-only on boot)
Backup "Boot" and ""System Image" in TWRP to External SD
Wipe - Format Data (or Wipe Encryption) in TWRP
Boot device and let it re-encrypt
Reboot back into TWRP (Cancel decryption prompt & leave system read-only on boot)
In adb shell or TWRP Terminal, echo KEEPFORCEENCRYPT=true>>/cache/.supersu
Flash BETA-SuperSU 2.72 from external SD card
Reboot back to system, and the device will reboot itself once as SuperSU installs
Do the SunShine
Boot into TWRP, restore stock boot and system image backup & Wipe - Format Data (or Wipe Encryption) again
Reboot device and let it encrypt again
Reboot back into TWRP (Cancel decryption prompt & leave system read-only on boot)
In adb shell or TWRP Terminal, echo KEEPVERITY=true>>/cache/.supersu (the file should still be there, so both commands will now be present)
Flash BETA-SuperSU 2.72 (again) from external SD card
Reboot back to system, and the device will reboot itself once as SuperSU installs (again)
Now you're rooted, with pristine stock system image and with forced encryption and dm-verity still enabled. In this state, you should be able to Download OTAs, use Android Pay, etc.
Inside the SuperSU.zip are more informations ...
Overridable variables (shell, /system/.supersu, /cache/.supersu,
# /data/.supersu):
# SYSTEMLESS - Do a system-less install? (true/false, 6.0+ only)
# PATCHBOOTIMAGE - Automatically patch boot image? (true/false,
# SYSTEMLESS only)
# BOOTIMAGE - Boot image location (PATCHBOOTIMAGE only)
# STOCKBOOTIMAGE - Stock boot image location (PATCHBOOTIMAGE only)
# BINDSYSTEMXBIN - Poor man's overlay on /system/xbin (true/false,
# SYSTEMLESS only)
# PERMISSIVE - Set sepolicy to fake-permissive (true/false, PATCHBOOTIMAGE
# only)
# KEEPVERITY - Do not remove dm-verity (true/false, PATCHBOOTIMAGE only)
# KEEPFORCEENCRYPT - Do not replace forceencrypt with encryptable (true/
# false, PATCHBOOTIMAGE only)
# Shell overrides all, /data/.supersu overrides /cache/.supersu overrides
# /system/.supersu
Hope this helps .. but the external sd card could be tricky.
Cheers

followmsi said:
Three lines above your thread ..
Tested xceed kernel and my pre-rooted kernel too.
Supersu will not modify the ramdisk at all.
"Can't find stock Image, already modified .." and will stop the ramdisk installer.
The system will start anyway, but with "old" ramdisk modifications.
So a fresh clean stock boot.img is recommended.
As well the Phhuson kernel is not pre-rooted for SuperSU.
( boot-ryu-MXC89F-su-nocrypt-r205 )
NEW Root access:
For root access: Pls install latest "stock" kernel and install SuperSU.zip version 2.72 directly afterwards - no reboot in between.
Hope this help all people in the same situation ..
Cheers
Click to expand...
Click to collapse
Is this the case if you are already stock, unrooted and encrypted? as I had copied Supersu to my sdcard but TWRP could not see it.
boot-ryu-MXC89F-su-nocrypt-r205 was used only to boot the device after twrp was installed, as the stock boot.img would not boot and caused a recovery boot loop.
boot-ryu-MXC89F-su-nocrypt-r205 got me out of the bootloop and allowed me to recopy supersu to the sdcard, but I could not see if encrypttion was now disabled, as settings/security caused a force close of settings.
I had assumed that boot-ryu-MXC89F-su-nocrypt-r205 allowed me to disable encryption and copy supersu to sdcard, which twrp could then find and supersu worked successfully.

scoobydu said:
Is this the case if you are already stock, unrooted and encrypted? as I had copied Supersu to my sdcard but TWRP could not see it.
Click to expand...
Click to collapse
If you are on stock and unrooted it works the way above.
Sorry, I am not sure on encryption now.
Removed it on the first day.
Before copying SuperSu to data .. just followed the guide.
Needs to be verified if 3.0.0.0 version from xceed is able to access encrypted data ..
Sorry, can't help you better here ...

scoobydu said:
Is this the case if you are already stock, unrooted and encrypted? as I had copied Supersu to my sdcard but TWRP could not see it.
boot-ryu-MXC89F-su-nocrypt-r205 was used only to boot the device after twrp was installed, as the stock boot.img would not boot and caused a recovery boot loop.
boot-ryu-MXC89F-su-nocrypt-r205 got me out of the bootloop and allowed me to recopy supersu to the sdcard, but I could not see if encrypttion was now disabled, as settings/security caused a force close of settings.
I had assumed that boot-ryu-MXC89F-su-nocrypt-r205 allowed me to disable encryption and copy supersu to sdcard, which twrp could then find and supersu worked successfully.
Click to expand...
Click to collapse
I saw only the first part of your answer ...
You got recovery boot-loop after installing TWRP ?
Never had any reboot issues, but I had always unencrypted data partition and could access my SuperSu.zip - all the time.
Never had to reboot without unchanged fstab nor stock kernel, as was able to flash SuperSu all the time.
As said before, I did remove encryption directly.
I did use xceed kernel for this .. some time ago.
Needs to be checked if xceed 3.0.0.0 TWRP has also problems to boot into system with stock kernel, was always used with xceed kernel together.
Version 3.0.2.0.img is using xceed only settings.
Version 3.0.2-0_v2.img has some parts from NYCHitman1 included.
Needs to be verified...
But we may need to adapt the instructions .. and may still need a stock rooted kernel for initial SuperSU installation.

Uploaded new TWRP version .. as TWRP flashable zip !
Just install this version with your current TWRP version and reboot to recovery again.
Have a look .. OTG is working now.
Update.ZIP_TWRP_dragon_3.0.2-0_v4.zip
Just made a fresh backup to my usb-stick via USB-OTG ..
Cheers

Samt434 said:
After flashing a stock android N preview 2, I installed TWRP and flashed the superSU ZIP (2.72). I can confirm this works perfectly, and i have root on android N preview 2
Click to expand...
Click to collapse
Is your device still encrypted ?
Did you format the /data partiton inside TWRP ?
How did you access the SuperSu.zip file inside TWRP ?
Did you install other kernel for intermediate reboot into system to decrypt data ?
A lot of questions .. but it helps to understand problems better
Thanks

I just successfully rooted the Android N beta with this!
I upgraded from Preview 2 via flash-all without wiping data.

[Mini Guide] How to root 8.1

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?

How to flash TWRP in Android 10 Open Beta 1?

I have installed this today and now those fastboot commands don't work. Fastboot boot fails with the error (unknown command). Any idea about how to install TWRP in this scenario?

Bhargav97 said:
I have installed this today and now those fastboot commands don't work. Fastboot boot fails with the error (unknown command). Any idea about how to install TWRP in this scenario?
Click to expand...
Click to collapse
Where did you get the zip?

Play store has to be authorized and added, Google Pay that is, play services for the device/region. That way it will pass safetynet. If it doesn't include the safetynet info, when you try to use it, and verify, it fails. It takes awhile often for them to get it working.

Bhargav97 said:
I have installed this today and now those fastboot commands don't work. Fastboot boot fails with the error (unknown command). Any idea about how to install TWRP in this scenario?
Click to expand...
Click to collapse
You can't. Currently there's no working twrp for Android 10 open beta.

Yes, officially, no TWRP, firmware is updated/changed, plus fastboot boot is often disabled on these builds. Also, it will fail Safety Net, so no root, no twrp and no GPay....Android Q is a bust so far. There are TWRP for Guacamole, I tried those on the Chinese version, ended up hosing my phone..finally got it back working and back on stable 9.0.17 and rooted/twrp. I'm guessing we will need another month at least to get a stable/working Q for 6T, and TWRP/root.

In h2os 10...twrp 3.3.1-8 works
Personally used

sanjeev7 said:
In h2os 10...twrp 3.3.1-8 works
Personally used
Click to expand...
Click to collapse
As long as you don't update twrp in in twrp and flash it is magisk after local upgrade before reboot

techlogik said:
Yes, officially, no TWRP, firmware is updated/changed, plus fastboot boot is often disabled on these builds. Also, it will fail Safety Net, so no root, no twrp and no GPay....Android Q is a bust so far. There are TWRP for Guacamole, I tried those on the Chinese version, ended up hosing my phone..finally got it back working and back on stable 9.0.17 and rooted/twrp. I'm guessing we will need another month at least to get a stable/working Q for 6T, and TWRP/root.
Click to expand...
Click to collapse
Magisk working fine and safety net passes.

Noob_Master said:
Magisk working fine and safety net passes.
Click to expand...
Click to collapse
how did you manage that? did you manage to flash twrp? or did you manage to root the phone without it?

i havent been able to get a working TWRP on it yet however i have managed to get working root with magisk, see my post about it here https://forum.xda-developers.com/on...agisk-pre-rooted-boot-img-oneplus-6t-t3986585

stardustsouls said:
how did you manage that? did you manage to flash twrp? or did you manage to root the phone without it?
Click to expand...
Click to collapse
1. Extract boot.img from OnePlus 6T Android 10 Open beta
2. Download magisk manager apk on OP6T
3. Place boot.img file on OP6T storage, and click "install" in the magisk manager app. There are two options, direct and one that will let you choose your boot.img file.
4. Place new modified file from downloads folder on OP6T back onto computer
5. Boot OP6T into fastboot mode (must already have unlocked bootloader, or this next one will not work!)
6. run "fastboot flash boot /location/of/file"
7. Profit

dtronics said:
i havent been able to get a working TWRP on it yet however i have managed to get working root with magisk, see my post about it here https://forum.xda-developers.com/on...agisk-pre-rooted-boot-img-oneplus-6t-t3986585
Click to expand...
Click to collapse
youre the bomb dude
---------- Post added at 08:54 PM ---------- Previous post was at 08:51 PM ----------
Odder1 said:
1. Extract boot.img from OnePlus 6T Android 10 Open beta
2. Download magisk manager apk on OP6T
3. Place boot.img file on OP6T storage, and click "install" in the magisk manager app. There are two options, direct and one that will let you choose your boot.img file.
4. Place new modified file from downloads folder on OP6T back onto computer
5. Boot OP6T into fastboot mode (must already have unlocked bootloader, or this next one will not work!)
6. run "fastboot flash boot /location/of/file"
7. Profit
Click to expand...
Click to collapse
you too lmao
now i can use viper4android again frick yeah

Noob_Master said:
Magisk working fine and safety net passes.
Click to expand...
Click to collapse
I tried the A/B Magisk TWRP retention script...and that didn't go well when I tried it.
Tried the fastboot method per your thread, that didn't work. Then tried the Magisk method and install, then select patched file, reboot, Magisk says it isn't installed and ctsProfile fails Safetynet.
Thanks

techlogik said:
I tried the A/B Magisk TWRP retention script...and that didn't go well when I tried it.
Tried the fastboot method per your thread, that didn't work. Then tried the Magisk method and install, then select patched file, reboot, Magisk says it isn't installed and ctsProfile fails Safetynet.
Thanks
Click to expand...
Click to collapse
Same, tried both methods and also got stuck on boot loop.

Tested the thread HERE and it worked for me I have the phone rooted without TWRP.
I already had the Magisk apk installed on the phone and flashed the img as mentioned in the thread and it worked.

To whom it may concern. I followed this method and it works flawlessly.
1. Magisk Manager > Tap "Uninstall" > Tap "Restore Images" (DO NOT REBOOT)
2. Now Run the System update to download and install the full OTA zip (DO NOT REBOOT)
3. Close all background apps
4. Open Magisk > Tap "Install" > Tap "install" again > Tap "Install to Inactive/Second Slot (After OTA)"
5. Finally tap Reboot after Magisk installation is complete.

Finally just gave up on TWRP and did the normal OTA procedure above, then patched inactive in Magisk. Now rooted, just no TWRP.
So the above works, just make sure you have the right full Android Q from the official thread and follow the above.

Odder1 said:
1. Extract boot.img from OnePlus 6T Android 10 Open beta
2. Download magisk manager apk on OP6T
3. Place boot.img file on OP6T storage, and click "install" in the magisk manager app. There are two options, direct and one that will let you choose your boot.img file.
4. Place new modified file from downloads folder on OP6T back onto computer
5. Boot OP6T into fastboot mode (must already have unlocked bootloader, or this next one will not work!)
6. run "fastboot flash boot /location/of/file"
7. Profit
Click to expand...
Click to collapse
Thanks man. Worked flawlessly. :good:

alp47470 said:
Thanks man. Worked flawlessly. :good:
Click to expand...
Click to collapse
Could you please explain after the 2nd step? Im already unlocked bootloader on android 10.
What modified boot image and how install?
please explain

suhas2k said:
Could you please explain after the 2nd step? Im already unlocked bootloader on android 10.
What modified boot image and how install?
please explain
Click to expand...
Click to collapse
Sure,
1. Unlock Bootloader
2. Install Magisk Manager - Magisk - Install - Select the boot.img When finished.
3. Reboot to Bootloader and flash the same boot.img file.
4. Boot OOSQ with Root.
https://t.me/aadarsh47
DM me if you couldn't get boot img file.
I'm getting some error uploading here.

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.

Root disappears after a while

Hi!
I'm on OnePlus 8 Pro IN2023 (OOS 11.0.1.1.IN11BA).
I can't hold my root after a while.
I did the whole rooting procedure (get the boot.img from the update zip, install magisk manager on phone (try different versions), patch the boot.img, boot into magisk_patched.img, install/update magisk, then reboot) and it succeed. But a couple of hours some apps crashed (fb, messenger, insta, etc.). Then reboot the phone, but stuck in bootloop... the only thing i can do is reset to factory settings (the root gone, the phone profile gone, the apps gone)
In magisk manager I tried the canary channel (does not work), I tried beta and stable channel, it work fine, but after reboot the bootloop is comming.
I have no idea what did I do wrong

aktap said:
Hi!
I'm on OnePlus 8 Pro IN2023 (OOS 11.0.1.1.IN11BA).
I can't hold my root after a while.
I did the whole rooting procedure (get the boot.img from the update zip, install magisk manager on phone (try different versions), patch the boot.img, boot into magisk_patched.img, install/update magisk, then reboot) and it succeed. But a couple of hours some apps crashed (fb, messenger, insta, etc.). Then reboot the phone, but stuck in bootloop... the only thing i can do is reset to factory settings (the root gone, the phone profile gone, the apps gone)
In magisk manager I tried the canary channel (does not work), I tried beta and stable channel, it work fine, but after reboot the bootloop is comming.
I have no idea what did I do wrong
Click to expand...
Click to collapse
You said boot the magisk patched. Do you flash it?
You boot magiskpatched to make sure it works
Then once confirmed you flash magiskpatched
You make no mention that you flash the magiskpatched (unless I'm blind)?

c_86 said:
You said boot the magisk patched. Do you flash it?
You boot magiskpatched to make sure it works
Then once confirmed you flash magiskpatched
You make no mention that you flash the magiskpatched (unless I'm blind)?
Click to expand...
Click to collapse
I use this method:
"Rooting using fastboot commands
Method 1
Booting the patched image first
1. Obtain a patched boot img for your device variant preferably using payload dumper or download one of mine from the foot of this guide or if you've just performed the above guide you should already have a functional one, copy this file to your fastboot folder on your computer
**NOTE - Again the above suggested downloads are for the EU/ UK variant- if you have another model / firmware please use that instead, If you did not obtain the boot.img from a firmware and patch it yourself, you will need to patch it again in magisk manager, to avoid a bootloop
2. Reboot your phone to fastboot and connect to your computer.
3. Boot the magisk patched img
fastboot boot magisk_patched (or name of your patched boot img
4. Reboot your phone, your phone should now boot and you should now be rooted but we need to make this permanent.
5. Open magisk manager and click install/update, if you are missing the install/ update buttons, change magisk version to beta in magisk settings.
6. Select Direct install (recommended)
7. Allow magisk to permanently root your device then click reboot.
You should now remain rooted."
So I probably didn't flash ...

aktap said:
I use this method:
"Rooting using fastboot commands
Method 1
Booting the patched image first
1. Obtain a patched boot img for your device variant preferably using payload dumper or download one of mine from the foot of this guide or if you've just performed the above guide you should already have a functional one, copy this file to your fastboot folder on your computer
**NOTE - Again the above suggested downloads are for the EU/ UK variant- if you have another model / firmware please use that instead, If you did not obtain the boot.img from a firmware and patch it yourself, you will need to patch it again in magisk manager, to avoid a bootloop
2. Reboot your phone to fastboot and connect to your computer.
3. Boot the magisk patched img
fastboot boot magisk_patched (or name of your patched boot img
4. Reboot your phone, your phone should now boot and you should now be rooted but we need to make this permanent.
5. Open magisk manager and click install/update, if you are missing the install/ update buttons, change magisk version to beta in magisk settings.
6. Select Direct install (recommended)
7. Allow magisk to permanently root your device then click reboot.
You should now remain rooted."
So I probably didn't flash ...
Click to expand...
Click to collapse
After which point should i do it?

I wouldn't do it that way...
When you boot magisk patched image. And get to system to confirm you boot fine
Reboot back into bootloader and
Fastboot flash boot_a magisk_patched.img
Fastboot flash boot_b magisk_patched.img
Fastboot reboot
That will permanently install the boot image.
Don't bother with the direct install on magisk app

c_86 said:
I wouldn't do it that way...
When you boot magisk patched image. And get to system to confirm you boot fine
Reboot back into bootloader and
Fastboot flash boot_a magisk_patched.img
Fastboot flash boot_b magisk_patched.img
Fastboot reboot
That will permanently install the boot image.
Don't bother with the direct install on magisk app
Click to expand...
Click to collapse
Okay i'll try
Thank you for your help

aktap said:
Hi!
I'm on OnePlus 8 Pro IN2023 (OOS 11.0.1.1.IN11BA).
I can't hold my root after a while.
I did the whole rooting procedure (get the boot.img from the update zip, install magisk manager on phone (try different versions), patch the boot.img, boot into magisk_patched.img, install/update magisk, then reboot) and it succeed. But a couple of hours some apps crashed (fb, messenger, insta, etc.). Then reboot the phone, but stuck in bootloop... the only thing i can do is reset to factory settings (the root gone, the phone profile gone, the apps gone)
In magisk manager I tried the canary channel (does not work), I tried beta and stable channel, it work fine, but after reboot the bootloop is comming.
I have no idea what did I do wrong
Click to expand...
Click to collapse
If you are using lucky patcher, this is the cause. The symptoms you describe are the same. This app became harmful for 8 pro in a11. Causing apps to crash, detachment from gms services, and eventually bootloop. You lose root because of the factory reset. That is expected. Please confirm if this is the cause. I experienced this myself in a test environment.

elmarian756 said:
If you are using lucky patcher, this is the cause. The symptoms you describe are the same. This app became harmful for 8 pro in a11. Causing apps to crash, detachment from gms services, and eventually bootloop. You lose root because of the factory reset. That is expected. Please confirm if this is the cause. I experienced this myself in a test environment.
Click to expand...
Click to collapse
Yes, I use Lucky Patcher. So you're saying that if I don't install the LP, the problem won't occur? And some app that replaces LP?

aktap said:
Yes, I use Lucky Patcher. So you're saying that if I don't install the LP, the problem won't occur? And some app that replaces LP?
Click to expand...
Click to collapse
A fix can't be discussed for that application.
Yes it is the reason you have a fault.. Get rid of it

dladz said:
A fix can't be discussed for that application.
Yes it is the reason you have a fault.. Get rid of it
Click to expand...
Click to collapse
I rooted my phone again, without LP the system is stable. Thank You for Your help!

Good good.
Tbh there is no reason to use that app. And now it causes a lot of crap anyway, best to avoid it