I used 25206 before , no luck. Gonna try the Delta 25210, but using the p7p boot. img right ?
I used 25206 before , no luck. Gonna try the Delta 25210, but using the p7p boot. img right ?
Yes, I patched the P7P boot image with Magisk Delta 25210 and retain root without issue, also all of my installed modules are all working properly.I used 25206 before , no luck. Gonna try the Delta 25210, but using the p7p boot. img right ?
The weird thing is the first time after I used delta to fastboot , then it's rooted but it said something happened that magisk has to reinstall. Then after that I tried many times with p7p's boot.img, but after I opened the magisk app to direct install, magisk will close and delete itself. But if I used p6p's img then it's not rooted but the app won't delete itself.
You might have the Canary and Delta mixed with each other! Uninstall Magisk whether it is Canary or the Delta, reboot and clean install the Delta again, then flash the P7P patched boot image (If I were you, I would patch a new P7P boot image with the new install Magisk Delta 25210 to be sure I am flashing the correct one).The weird thing is the first time after I used delta to fastboot , then it's rooted but it said something happened that magisk has to reinstall. Then after that I tried many times with p7p's boot.img, but after I opened the magisk app to direct install, magisk will close and delete itself. But if I used p6p's img then it's not rooted but the app won't delete itself.
Thanks , I gonna try it laterYou might have the Canary and Delta mixed with each other! Uninstall Magisk whether it is Canary or the Delta, reboot and clean install the Delta again, then flash the P7P patched boot image (If I were you, I would patch a new P7P boot image with the new install Magisk Delta 25210 to be sure I am flashing the correct one).
After I direct install magisk , restarted my phone and it's still said N/A. Should I still use direct install or install to inactive slot?You might have the Canary and Delta mixed with each other! Uninstall Magisk whether it is Canary or the Delta, reboot and clean install the Delta again, then flash the P7P patched boot image (If I were you, I would patch a new P7P boot image with the new install Magisk Delta 25210 to be sure I am flashing the correct one).
I am not sure I get your question. Install HuskyDG's latest Magisk Delta 25210 dated March 16 should be pretty straightforward. Are you getting the correct one? Why are you talking different slots? You flash the QPR3 Beta 2 to whatever slot which is active in your system with bootloader unlocked, boot without root to make sure everything is ok, then install the Magisk Delta 25210 to patch the P7P boot image, flash it (don't change slot), reboot, you phone should be rooted now.After I direct install magisk , restarted my phone and it's still said N/A. Should I still use direct install or install to inactive slot?
Sorry I'm new to this, because I saw there is another option beside direct install, that's why I wanna know if there is another way.I am not sure I get your question. Install HuskyDG's latest Magisk Delta 25210 dated March 16 should be pretty straightforward. Are you getting the correct one? Why are you talking different slots? You flash the QPR3 Beta 2 to whatever slot which is active in your system with bootloader unlocked, boot without root to make sure everything is ok, then install the Magisk Delta 25210 to patch the P7P boot image, flash it (don't change slot), reboot, you phone should be rooted now.
Is it the first time you root your phone? No, direct install and install in inactive slot are both not correct, you should choose to patch a file. Then choose the P7P boot image file which you exact from the P7P factory image, patched it. Now you got a new patched P7P boot image in your download folder. Renamed it to a easier name such as magisk_patched.img then move it to your PC, boot your phone into fastboot mode and flash this magisk_patched.img, reboot and your phone should be rooted now.Sorry I'm new to this, because I saw there is another option beside direct install, that's why I wanna know if there is another way.
I installed the official debug one before but I already tried the HuskyDG one and still, after I fastboot it and after reboot and it's still no root..
Android 14 will make it easier to hide your phone’s PIN from shoulder surfers
BYMISHAAL RAHMAN
Android is adding a new "enhanced PIN privacy" setting that will make it safer for you to enter your phone's PIN in public.
Readers like you help support XDA Developers. When you make a purchase using links on our site, we may earn an affiliate commission. Read More.
Google just released the second beta for the upcoming Android 13 QPR3 release this June, but the new release doesn’t offer a whole lot in terms of new features and improvements. Since QPR3 will be Android 13’s final maintenance release, it mainly focuses on stability and bug fixing changes. However, some minor quality-of-life improvements do make their way into QPRs, and Android 13 QPR3 is no different. Given that few OEMs outside of Pixel ever merge QPRs, these quality-of-life improvements will become available on devices from other brands in the next major Android release, ie. Android 14. And in Android 13 QPR3 Beta 2, we spotted a new feature that’ll make its way to other devices on Android 14: Enhanced PIN privacy.
After booting up Android 13 QPR3 Beta 2 on a Pixel 6, we spotted a new “enhanced PIN privacy” toggle under Settings > Security & privacy > Device lock. The description for this toggle reads “disable animations while entering the PIN”, meaning that the animation that normally plays when you tap any number on the keyguard won’t be shown. This will make it harder for shoulder surfers to watch you enter your PIN, because the Android lock screen won’t show an obvious visual cue for each number you tap.
Here’s a video demonstrating this new enhanced PIN privacy feature. This video was recorded from another device because Android applies FLAG_SECURE to the keyguard window, preventing screenshots and screen recordings from being taken. Special thanks to Nail Sadykov for sharing this video with us!
Shoulder surfing is a common social engineering attack used to obtain access to users’ devices, as many people enter their PIN while in public places. A recent report from The Wall Street Journal showed how shoulder surfers could gain nearly full access to a user’s Apple or Google Account simply by observing their phone’s unlock code and then swiping their device. Making it harder for shoulder surfers to observe PIN entry will make it harder for them to subsequently access a user’s Apple or Google Account, hopefully.
Enhanced PIN privacy isn’t the only new lock screen-related improvement coming in Android 14. We previously spotted a new feature called “auto-confirm correct PIN” that allows you to bypass tapping Enter in order to unlock your phone. That feature is not available to users yet, unlike the new enhanced PIN privacy toggle we spotted in Android 13 QPR3 Beta 2. Speaking of which, it’s likely that this new enhanced PIN privacy toggle will appear in the next Android 14 preview release, which is expected to be Android 14 Beta 1. Android 14 Beta 1 will likely land in early April, and when it does, we’ll be covering the new features and changes extensively.
I know this way , I do this many times but usually with the stable build.Is it the first time you root your phone? No, direct install and install in inactive slot are both not correct, you should choose to patch a file. Then choose the P7P boot image file which you exact from the P7P factory image, patched it. Now you got a new patched P7P boot image in your download folder. Renamed it to a easier name such as magisk_patched.img then move it to your PC, boot your phone into fastboot mode and flash this magisk_patched.img, reboot and your phone should be rooted now.
Search in the forum a thread which guide how to update monthly without wipe and follow details there if you still got problem.
I have P6P and my wife has the P6, we both update to the QPR3 Beta 2 and use the Magisk Delta 25210 to retain our root status without any issue. I really couldn't understand why it is not working for you, suggest you to read the documentation and FAQ to see if you have missed something. Also you may post your question there atI know this way , I do this many times but usually with the stable build.
And yes , it's ok after I flash the patched p7p. Img but after I follow the app and it reboot my phone then the root is gone
Thank you for your reply, that is the screenshot after I fastboot the image , and the root is temporary and after I restart my phone and the root will be gone.I have P6P and my wife has the P6, we both update to the QPR3 Beta 2 and use the Magisk Delta 25210 to retain our root status without any issue. I really couldn't understand why it is not working for you, suggest you to read the documentation and FAQ to see if you have missed something. Also you may post your question there at
you have better chance to get help there.![]()
[Discussion] Magisk Delta - Another unofficial third-party Magisk fork
This is not an officially supported topjohnwu project. If you are looking for official Magisk source, please go to this page Introduction Custom Magisk fork by HuskyDG. Sync with official Magisk adding back MagiskHide...forum.xda-developers.com
And based on your screen shot, it seems OK, Magisk Delta didn't ask you to install anything, what are you try to install to casue the reboot to loose you root?
Your first screenshot showing you have Magisk Delta and Magisk Manager installed properly. If you press install again and choose direct install (which is your second screnshot and I don't know what makes you to think that you need to do this procedure!!!), the Magisk Manager would install again and revert back to your original boot.img (in this case which is the P6P boot.img), so after reboot, your on P6P original boot.img without patching and this is why you lost your root.Thank you for your reply, that is the screenshot after I fastboot the image , and the root is temporary and after I restart my phone and the root will be gone.
I used to follow this, and the last step is to direct install because the root is temporary?Your first screenshot showing you have Magisk Delta and Magisk Manager installed properly. If you press install again and choose direct install (which is your second screnshot and I don't know what makes you to think that you need to do this procedure!!!), the Magisk Manager would install again and revert back to your original boot.img (in this case which is the P6P boot.img), so after reboot, your on P6P original boot.img without patching and this is why you lost your root.
Bottom line is that you flash the the P7P patched boot.img and reboot, if you see everything exactly as your first screenshot, then you phone is rooted, don't (no need) to install Magisk Manager again.
Hope this make sense to you.
I never use OTA update and always use factory image update as I personally believe it is most simple and straight forward method, see my other above message for further comments.I used to follow this, and the last step is to direct install because the root is temporary?
And right now after I flashed the p7p img and it starts ok but I can't restart because it will lose the root , is that normal here ?
After I installed the Delta magisk and there's no direct install in my phone ? There's only patch there. I'm checking more comments up there to see if I'm doing anything wrongI don't have the patience to watch that video plus it is talking OTA update, we are talking factory image update! Anyway, you have to understand the Magisk install procedure, you install the Magisk Delta 25210 and after reboot, the Magisk Home would showing that App is installed and Magisk is N/A, then you choose direct install to install the Magisk manager, then reboot again, the installation is completed now. Now with this new installed Magisk, you patch the P7P boot image and flash it, reboot and your phone gained root. No need to install the Magisk manager again (like I said, it would revert your phone's boot image and it would loose root).
If you keep on direct install Magisk manager again after you flash the patched boot.img, you are just cycling it again and again.
I believe you should read these 2 threads to make sure you are doing correctly:After I installed the Delta magisk and there's no direct install in my phone ? There's only patch there. I'm checking more comments up there to see if I'm doing anything wrong
I'm posting OTA video because I just follow his video to update my p6p from stable to T3B2,
And I'm wondering if I have to root it again like fastboot flash -disable-verity -disable-verification vbmeta vbmeta.img then boot the patched img or just fastboot boot patched.img.
Sorry I just came from iOS and I don't have many experience rooting my phone
fastboot flash boot Magik'dPixel7ProBoot.img
I'm only being allowed to Opt into the Android 14 beta program. I want to enroll in the Android 13 QPR Beta program instead. Any idea how?
I don't know for sure, but I suspect that no one can opt into the QPR3 Beta program any longer.
Even Google's QPR3 Beta release page:
which has a link:
and leads to:
the Enroll in Android 13 Beta for Pixel button there still leads to:Get Android 13 | Android Developers
Get an Android 13 on your eligible device.developer.android.com
which only mentions Android 14 Beta.
So I think your only choice if you want to try QPR3 Beta is to have an unlocked bootloader and flash the factory image, or I think it's possible to sideload the OTA without unlocking the bootloader - but it's highly discouraged to try a Beta with a locked bootloader, as you'll be locked into the Beta program (via manual OTA sideloads) until it goes final, and you'll have no choice but to deal with the issues.
Pixel 6 Pro raven-tpb3.220617.002-factory-1acb43a3.zip 1acb43a3d082b8d2cd16cba834c1b1de25042c5d5122483bbf54ff4a16682186
Android 13 Beta 3.3 (June 2022)
Release date: June 27, 2022
Build: TPB3.220617.002
Emulator support: x86 (64-bit), ARM (v8-A)
Security patch level: June 2022
Google Play services: 22.21.16
API diff:
If you’re already running a Developer Preview or Beta build, you will automatically receive an over-the-air (OTA) update to Beta 3.3.
This minor update to Android 13 Beta 3 includes stability and performance improvements as well as the following fixes:
- Fixed an issue with the Pixel launcher where if the Always show keyboard option was enabled for the app drawer, then when the user closed the app drawer and opened an app folder on the Home screen, the keyboard was erroneously shown as well. (Issue #236584457)
- Fixed an issue where in some cases, such as gesturing to go back, the system UI crashed. (Issue #236558007)
- Fixed an issue where devices couldn't connect to a WiFi network in some cases even when the network was available and the signal strength was good. (Issue #236617510)
- Fixed an issue where the BluetoothManagerService continued to try and bind to the TbsService even when bluetooth.profile.ccp.server.enabled was false, leading to slow performance and cold starts for apps.
- Fixed an issue where in some cases after a device was plugged in to charge (for example, overnight), the device would become unresponsive until it was rebooted.
- Fixed a kernel issue with lib/list_debug.c that caused a kernel panic in certain cases on some devices.
- Fixed an issue with the Connectivity Thermal Power Manager that caused slow UI rendering, unresponsiveness in apps, and poor battery performance in some cases.
June 27, 2022 2:30pm Comment Skanda Hazarika
Google rolls out Android 13 Beta 3.3 with a bunch of bug fixes
The beta branch of Android 13 just picked up a new bug-squashing update. Following in the footsteps of Android 13 Beta 3’s earlier incremental updates, this new release fixes a whole bunch of issues, including slow UI rendering, inability to connect to a Wi-Fi network, system UI crashes, and a few other problems.
The build number of Android 13 Beta 3.3 is TPB3.220617.002. There is no change in the security patch level, though, hence it’s still June 2022 on this release. You can find the full list of published fixes in this update below:
Apart from the aforementioned bug fixes, the update also bumps the Google Play services version from 22.18.19 to 22.21.16.
- Fixed an issue with the Pixel launcher where if the Always show keyboard option was enabled for the app drawer, then when the user closed the app drawer and opened an app folder on the Home screen, the keyboard was erroneously shown as well. (Issue #236584457)
- Fixed an issue where in some cases, such as gesturing to go back, the system UI crashed. (Issue #236558007)
- Fixed an issue where devices couldn’t connect to a WiFi network in some cases even when the network was available and the signal strength was good. (Issue #236617510)
- Fixed an issue where the BluetoothManagerService continued to try and bind to the TbsService even when bluetooth.profile.ccp.server.enabled was false, leading to slow performance and cold starts for apps.
- Fixed an issue where in some cases after a device was plugged in to charge (for example, overnight), the device would become unresponsive until it was rebooted.
- Fixed a kernel issue with lib/list_debug.c that caused a kernel panic in certain cases on some devices.
- Fixed an issue with the Connectivity Thermal Power Manager that caused slow UI rendering, unresponsiveness in apps, and poor battery performance in some cases.
In case your Google Pixel device is already enrolled in the Android 13 beta program, you will automatically receive an over-the-air update to Beta 3.3. You can also download the full OTA or the factory image from the link below if you want to manually upgrade to the latest beta release.
Download Android 13 Beta 3.3
Source: Android Beta Program on Reddit
Good spot. Seeing as how that's now intended behaviour, I guess wiping and disabling verification is all our best moves from here.I think Magisk removed the need to pass the vbmeta disable verity/verification flag with Canary 24303. Here's a quote related to a kernel issue from yujincheng08 (LoveSy):
"Let me clarify the things.
Magisk was used to modify the fstab to inject Magisk components, and in the meantime, Magisk stipped avb_key and avb flags for all partitions. So, that 24300 works is just a side effect and has no insurance.
Now Magisk changed its way of injecting Magisk components, and it will no longer modify the fstab, and the side effect was thus gone together with the refactorization. Some configurations that rely on the fact that Magisk will strip those verification flags will no longer work, and that's expected. Users should disable the verification themselves since they are expected to have unlocked bootloaders."
This all relates to problems with custom kernels and Magisk, but may have further implications for us. Check out more in the issue here..
Some customized kernels are incompatible with Magisk 24303+ that no longer strips verification flags of early mount partitions · Issue #5777 · topjohnwu/Magisk
Device: Pixel 6 Pro Android version: 12.1...github.com