Database Info

Manual OTA installation: seamless?

One of the great new features of Nougat on new devices like the Pixel is the seamless installation. Because there are two partitions, OTA updates can install and optimize in the background; then reboot straight into the updated version. I had read a while back that installing an OTA manually might not allow the same seamless update path. Does anyone know? Has anyone tried it?
I want to keep pure stock, non-rooted, etc. I just want my OTA now rather than potentially waiting weeks for it. Seems like installing the OTA manually via ADB could install it to the second partition and preserve all apps and user data...but I'm not about to find out the hard way.

Side loading the OTA won't wipe your user data or anything. The "seamless" update system simply allows Android to update itself while still letting you use the phone, needing only a reboot to switch once that's done. The only difference between that and sideloading is that it takes a while and you can't use your phone during the process.
Just took the update myself through sideloading on stock, so feel free to go ahead with it!

zphantom55 said:
Side loading the OTA won't wipe your user data or anything. The "seamless" update system simply allows Android to update itself while still letting you use the phone, needing only a reboot to switch once that's done. The only difference between that and sideloading is that it takes a while and you can't use your phone during the process.
Just took the update myself through sideloading on stock, so feel free to go ahead with it!
Click to expand...
Click to collapse
Thanks, appreciate that! Giving it a try now.

Super easy process. If this helps anyone else, here are the basics.
On Windows computer:
1. Download the appropriate OTA image from Google: https://developers.google.com/android/ota
2. Install the latest version of Minimal ADB and Fastboot: https://androidmtk.com/download-minimal-adb-and-fastboot-tool
On Pixel
3. Enable USB debugging from Settings > Developer Menu
4. Plug Pixel into USB port in your computer using the USB-C to USB-A cable that came with the phone. Windows 10 (and probably earlier versions) will install drivers if you haven't plugged it in before.
On Computer
5. In command prompt in Minimal ADB directory, type "adb devices". Make sure a device shows up with the word "device" after it. If it says "unauthorized", you need to accept the dialog box on the phone, then try again.
6. After OTA file is downloaded, check the checksum again the SHA-256 hash listed on the Google OTA page, if you want. Not really needed since the phone will check this later before it installs.
7. Move the OTA file into the Minimal ADB directory.
8. In the command prompt, type "adb reboot recovery"
On Pixel
9. You should now see Android logo with red exclamation mark on the screen. Hold the Power button and press Volume Up once, and a menu will appear. Select the option Apply update from ADB.
On Computer
10. In command prompt type "adb sideload [filename of OTA file].zip"
On Pixel
11. Once the update finishes, reboot the phone by choosing Reboot the system now.
12. After Android loads, you should disable USB debugging for security.
There is no need to unlock bootloader for sideloading an OTA. (Don't do it--it will factory reset your phone.)

9. You should now see Android logo with red exclamation mark on the screen. Hold the Power button and press Volume Up once, and a menu will appear. Select the option Apply update from ADB.
....question ? doing same thing on my pixel...went ok, also got nexus 6p ...dont know how to enter to recovery mode on 6p

[MAGISK][MOD][13/01][v4] Stereo Speaker & Headphone Volume Boost Mod

Pre-requisites :
Rooted with Magisk
Disclaimer : I am not responsible for any damage to your device.
Click to expand...
Click to collapse
Download : AFH
Included Versions :
Volume Boost : Speaker & Headphone Boost
Volume Boost_Call : Speaker, Headphone & InCall Boost
Credits :
gururoop (Stock OOS)
Regards,
acervenky

If the speaker starts crackling at high volume, immediately lower the volume and report on the thread.
I've increased the gain by 4+2dB on all the versions which should be within safe threshold.
Regards,
acervenky

reserved 2

Gonna try today when my new phone arrives
#oneplus7pro
Thanx bud!

acervenky said:
Pre-requisites :
Rooted with Magisk
Download : Github
Included Versions :
Speaker Volume Boost
Headphone Volume Boost
Speaker & Headphone Volume Boost
Credits :
gururoop (Stock OOS)
Regards,
acervenky
Click to expand...
Click to collapse
so just copy paste into a directory and overwrite all?
(haven't got 7pro yet, waiting 21st to order).
thanks

entwicklun said:
so just copy paste into a directory and overwrite all?
(haven't got 7pro yet, waiting 21st to order).
thanks
Click to expand...
Click to collapse
You can do it manually, or just flash the zip via magisk.
Regards,
acervenky

acervenky said:
You can do it manually, or just flash the zip via magisk.
Regards,
acervenky
Click to expand...
Click to collapse
thank you, and I need a custom recovery for magisk?
https://www.xda-developers.com/how-to-install-magisk/

entwicklun said:
thank you, and I need a custom recovery for magisk?
https://www.xda-developers.com/how-to-install-magisk/
Click to expand...
Click to collapse
Follow this thread to install magisk : Patched Boot Image
And then install this as a module using magisk manager.
Regards,
acervenky

acervenky said:
Follow this thread to install magisk : Patched Boot Image
And then install this as a module using magisk manager.
Regards,
acervenky
Click to expand...
Click to collapse
oh man I've never command prompt stuff on a phone. I once flashed a wrong zip on my note 3 (2012 I think?) and hard bricked it lol, I'm so scared now haha!!

entwicklun said:
oh man I've never command prompt stuff on a phone. I once flashed a wrong zip on my note 3 (2012 I think?) and hard bricked it lol, I'm so scared now haha!!
Click to expand...
Click to collapse
It's not very difficult at all and is nothing to be fearful of. The beauty of OnePlus and this community is that it's difficult to royally screw up to a point of no return. If your device can get into fastboot, you're always fine. If you can get into EDL mode, you're fine. Here's a small guide of what you have to do, in order: I'm writing it out as if you are completely new in case you are or if anyone reading it is, I'm not assuming you are and don't mean to disrespect you if you aren't.
1) Download and install "Minimal ADB and Fastboot" on your computer from here: https://forum.xda-developers.com/showthread.php?t=2317790
2) Go to your phone's settings -> about phone -> then tap the build number until you've unlocked developer options.
3) Go to developer options under settings -> system -> developer options. Enable OEM unlocking, then scroll down and enable USB debugging. Connect your phone to your computer and authorise access on your phone when it prompts for it.
4) On your computer, go to the folder where you installed Minimal ADB and Fastboot. Hold your shift key and right click anywhere where there's open space (without a selected file in the window), and hit "Open Powershell Window Here"
5) Confirm your device is indeed connected by typing "adb devices". On my computer, I'm forced to type "./adb devices" with the period and forward flash for whatever reason, but the command prompt should show your device as connected. Might be a Windows 10 thing, I haven't researched it.
6) In the command prompt you've just opened, type "adb reboot-bootloader". You're now in fastboot mode.
7) Once you are in fastboot, type "fastboot oem unlock". Follow the prompts on your phone to unlock the bootloader with the volume keys. This will erase all your data on your phone. Your phone will now reboot after you've confirmed that you're okay with data being wiped.
8) Set up your phone again and unlock developer options/USB debugging again.
9) On your computer, download the correct patched version of your boot.img here: https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-root-oneplus-7-pro-patched-boot-t3931205 - please remember to download the correct version, downloading the wrong one and flashing it will cause your WiFi not to work. You can check which version you need by going into settings -> about phone -> build number. I'm on Oxygen OS 9.5.3. If you've accidentally installed the wrong one, no worries - download the correct one and follow the steps again.
10) Drag the file you've just downloaded (filename should be: boot_patched.img) into your Minimal ADB and Fastboot folder.
11) Hold your shift key + right click anywhere in the window and open Powershell again.
12) Reboot into bootloader again by typing "adb reboot-bootloader". Again, if you're on Windows 10 or if you get some long message, you may have to type "./adb reboot-bootloader". This applies to all commands input into the command prompt, including the next steps'.
13) Once your phone has reboot into fastboot, in the command prompt, type "fastboot flash boot boot_patched.img".
14) After that's completed, type "fastboot reboot". Your phone will now reboot normally.
15) On your phone, download Magisk Manager from here: https://www.xda-developers.com/how-to-install-magisk/ - it's a 1.85 mb file that's actually just an apk file. Allow Google Chrome access to your storage, and allow Chrome to install apps from an unknown source - then continue to install Magisk Manager.
16) Once installed, you'll be prompted to finish installing Magisk, tap continue and let it do its thing. Then hit reboot.
17) Once rebooted, locate Magisk Manager and open the app. You should see the fact that it successfully installed. From there, swipe in from the left and select downloads to start looking for mods! You can download them on Chrome and find them under the modules, just gotta click the plus sign and locate it.
Cheers.

I tried the speaker mod, but I had problems with most of my applications. The mod pairs nicely with Poweramp music player, but everything else lacks that pop. I could say I tried and thanks. Here is list of the apps that had bad output
(1)OG YouTube
(2) YouTube Vanced
(3) FL Mobile
(4) Audio Evolution Mobile
(5)Ntrack DAW
(6) Audiolab
(7) Meditation Drums
(8) Bebot
(9) Deflemask
(10) Videoder
*Maybe I did something wrong or it's conflicting with other apps
Sent from my GM1917 using Tapatalk

Thanks
AhsanU said:
It's not very difficult at all and is nothing to be fearful of. The beauty of OnePlus and this community is that it's difficult to royally screw up to a point of no return. If your device can get into fastboot, you're always fine. If you can get into EDL mode, you're fine. Here's a small guide of what you have to do, in order: I'm writing it out as if you are completely new in case you are or if anyone reading it is, I'm not assuming you are and don't mean to disrespect you if you aren't.
1) Download and install "Minimal ADB and Fastboot" on your computer from here: https://forum.xda-developers.com/showthread.php?t=2317790
2) Go to your phone's settings -> about phone -> then tap the build number until you've unlocked developer options.
3) Go to developer options under settings -> system -> developer options. Enable OEM unlocking, then scroll down and enable USB debugging. Connect your phone to your computer and authorise access on your phone when it prompts for it.
4) On your computer, go to the folder where you installed Minimal ADB and Fastboot. Hold your shift key and right click anywhere where there's open space (without a selected file in the window), and hit "Open Powershell Window Here"
5) Confirm your device is indeed connected by typing "adb devices". On my computer, I'm forced to type "./adb devices" with the period and forward flash for whatever reason, but the command prompt should show your device as connected. Might be a Windows 10 thing, I haven't researched it.
6) In the command prompt you've just opened, type "adb reboot-bootloader". You're now in fastboot mode.
7) Once you are in fastboot, type "fastboot oem unlock". Follow the prompts on your phone to unlock the bootloader with the volume keys. This will erase all your data on your phone. Your phone will now reboot after you've confirmed that you're okay with data being wiped.
8) Set up your phone again and unlock developer options/USB debugging again.
9) On your computer, download the correct patched version of your boot.img here: https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-root-oneplus-7-pro-patched-boot-t3931205 - please remember to download the correct version, downloading the wrong one and flashing it will cause your WiFi not to work. You can check which version you need by going into settings -> about phone -> build number. I'm on Oxygen OS 9.5.3. If you've accidentally installed the wrong one, no worries - download the correct one and follow the steps again.
10) Drag the file you've just downloaded (filename should be: boot_patched.img) into your Minimal ADB and Fastboot folder.
11) Hold your shift key + right click anywhere in the window and open Powershell again.
12) Reboot into bootloader again by typing "adb reboot-bootloader". Again, if you're on Windows 10 or if you get some long message, you may have to type "./adb reboot-bootloader". This applies to all commands input into the command prompt, including the next steps'.
13) Once your phone has reboot into fastboot, in the command prompt, type "fastboot flash boot boot_patched.img".
14) After that's completed, type "fastboot reboot". Your phone will now reboot normally.
15) On your phone, download Magisk Manager from here: https://www.xda-developers.com/how-to-install-magisk/ - it's a 1.85 mb file that's actually just an apk file. Allow Google Chrome access to your storage, and allow Chrome to install apps from an unknown source - then continue to install Magisk Manager.
16) Once installed, you'll be prompted to finish installing Magisk, tap continue and let it do its thing. Then hit reboot.
17) Once rebooted, locate Magisk Manager and open the app. You should see the fact that it successfully installed. From there, swipe in from the left and select downloads to start looking for mods! You can download them on Chrome and find them under the modules, just gotta click the plus sign and locate it.
Cheers.
Click to expand...
Click to collapse
I just wanted to say a big THANKS for that awesome explanation!

Hentai_expert said:
I tried the speaker mod, but I had problems with most of my applications. The mod pairs nicely with Poweramp music player, but everything else lacks that pop. I could say I tried and thanks. Here is list of the apps that had bad output
(1)OG YouTube
(2) YouTube Vanced
(3) FL Mobile
(4) Audio Evolution Mobile
(5)Ntrack DAW
(6) Audiolab
(7) Meditation Drums
(8) Bebot
(9) Deflemask
(10) Videoder
*Maybe I did something wrong or it's conflicting with other apps
Sent from my GM1917 using Tapatalk
Click to expand...
Click to collapse
Interesting, only with third party apps... No Google apps or sth like that

I flashed the headphone boost through Magisk and feel like it didn't do anything.

Any updates for a better mod or any way to increase the volume?

Just get Viper for volume boost.

FaflaMcDafla said:
Just get Viper for volume boost.
Click to expand...
Click to collapse
Or a custom kernel like EX so increase max volume

Eric214 said:
Or a custom kernel like EX so increase max volume
Click to expand...
Click to collapse
Or just use both

FaflaMcDafla said:
Just get Viper for volume boost.
Click to expand...
Click to collapse
Unfortunately the gain control doesn't do anything in viper on the op7 pro. and the audio is natively very low, especially on Bluetooth earphones or headphones.This mod pairs very nicely with viper. Now my op7 pro sounds nice and punchy just like my op6 does.
This mod is legit. Very happy with it.

Burt Squirtz said:
Unfortunately the gain control doesn't do anything in viper on the op7 pro. and the audio is natively very low, especially on Bluetooth earphones or headphones.This mod pairs very nicely with viper. Now my op7 pro sounds nice and punchy just like my op6 does.
This mod is legit. Very happy with it.
Click to expand...
Click to collapse
Does it boost Bluetooth? Was looking for a bit more oomph

Bricked full stock

I never modified my phone whatsoever, I apply the OTA updates
Last day it bricked between my hands while I texted someone
I can boot it in "CSC FastBoot Mode" and here I can select what I want to do
Is there a way to reflash it without loosing data? Or anything, but retreiving my data

Please, someone can reply if it's possible?

Does it offer the option to access/start recovery? If yes once in recovery mode you should be able to choose apply update from adb or maybe even apply update from sd card.
Depending on the firmware you were on (Android 11 or Android 10) download the appropriate firmware version from https://www.asus.com/Mobile/Phones/All-series/ZenFone-6/HelpDesk_BIOS?model2Name=ZenFone-6 and rename it to update.zip and put in on your sd card if you have one and if that options is available. If that option is available choose that option and navigate to the appropriate folder and choose the update.zip.
If you only have the apply update from adb option or the other one doesn't work download the platform tools https://developer.android.com/studio/releases/platform-tools first, extract them, connect your phone to your pc, then in the extracted folder hold shift key while right clicking an empty space in the extracted windows explorer folder and choose the option "open command prompt here" or similar. On your phone choose the update from adb option, in the command prompt on pc put in adb devices first. If it hasn't already windows should install drivers now and the command prompt should say a long sequence of numbers and "sideload" besides it. If windows doesn't recognise the device or it doesn't show any device in the command prompt line go to windows updates, "show optional windows updates", open driver updates and it should offer an ASUS android bootloader or ASUS adb driver or something similar.
Once that works simply input the command shown on the phone adb sideload update.zip or similar into the command prompt and it should reinstall the full OTA again without wiping anything.

*double post*

regenwurm16 said:
Does it offer the option to access/start recovery? If yes once in recovery mode you should be able to choose apply update from adb or maybe even apply update from sd card.
Depending on the firmware you were on (Android 11 or Android 10) download the appropriate firmware version from https://www.asus.com/Mobile/Phones/All-series/ZenFone-6/HelpDesk_BIOS?model2Name=ZenFone-6 and rename it to update.zip and put in on your sd card if you have one and if that options is available. If that option is available choose that option and navigate to the appropriate folder and choose the update.zip.
If you only have the apply update from adb option or the other one doesn't work download the platform tools https://developer.android.com/studio/releases/platform-tools first, extract them, connect your phone to your pc, then in the extracted folder hold shift key while right clicking an empty space in the extracted windows explorer folder and choose the option "open command prompt here" or similar. On your phone choose the update from adb option, in the command prompt on pc put in adb devices first. If it hasn't already windows should install drivers now and the command prompt should say a long sequence of numbers and "sideload" besides it. If windows doesn't recognise the device or it doesn't show any device in the command prompt line go to windows updates, "show optional windows updates", open driver updates and it should offer an ASUS android bootloader or ASUS adb driver or something similar.
Once that works simply input the command shown on the phone adb sideload update.zip or similar into the command prompt and it should reinstall the full OTA again without wiping anything.
Click to expand...
Click to collapse
How can I know if I need WW version or another one?
I don't remember if I was on 10 or 11 but I applied all OTA until december 2020, something like that
And how can I know if I can take the last firmware version or not?
Booting into recovery mode gives a black screen for 10 seconds then a reboot
Even the charging mode display bolt before charging animation then black screen then reboot itself after a time
Only CSC mode works normally, displaying something and not rebooting

In general ASUS does only offer one firmware package for all regions as far as I know and the statement on the firmware page generally only means which regions it has been certified for. Further information can be found at https://zentalk.asus.com/en/categories/zenfone-6-(zs630kl)
It depends on where you bought the device.
If recovery mode isn't accessible you will most likely have to use on of the unbrick threads under https://forum.xda-developers.com/f/asus-zenfone-6-2019-guides-news-discussion.8906/ most probably https://forum.xda-developers.com/t/...k-your-zenfone-6-android-p-q-zs630kl.4189715/ will help you here.

[GUIDE] UNLOCKING, DOWNGRADING TO A10, TWRP, ROOT

Hello,
I'm posting this guide for those (like me) who can't do without TWRP on their device.
I'm providing only a step-by-step explanation. Credits to @nikamura for his kernel and TWRP: https://forum.xda-developers.com/t/twrp-3-4-0-0-for-sunfish-testing.4179101/
Credits to @Zackptg5 for his guide, from which I've started: https://forum.xda-developers.com/t/guide-unlock-root-safetynet-for-pixel-4a.4153773/
Credits to @topjohnwu for Magisk: https://github.com/topjohnwu/Magisk
DISCLAIMER: I don't take any responsibility if your phone explodes or anything... The guide is provided as is.
FIRST STEP: UNLOCKING THE BOOTLOADER
Download USB drivers for your phone here: https://androidfilehost.com/?fid=8889791610682922010
Download SDK Platform-Tools for Windows here: https://developer.android.com/studio/releases/platform-tools
Extract the SDK Platform-Tools to a directory of your choice.
Open your command prompt, change directory to where you extracted the Platform-Tools and type "fastboot". Depending on your Windows setup (I'm a linux guy, so I've used an ancient win8.1 installation in a VM...) you might receive a message of a missing dll (api-ms-win-crt-convert-l1-1-0.dll): if so, download and install the Universal C Runtime from https://support.microsoft.com/en-us...-windows-c0514201-7fe6-95a3-b0a5-287930f3560c
If you try the "fastboot" command once more, it should now work.
On your phone go to system settings -> About phone -> tap on 'Build number' several times until Developer Options is enabled.
Back out into settings and go to System -> Advanced -> Developer Options -> Enable 'OEM Unlocking'.
Switch off the phone.
Boot into fastboot by holding Vol Down + Power.
Plug the phone into a usb port of your pc.
In your command prompt type "fastboot devices". If there is no output, it means you have to install the USB driver. So, open "Device Manager" on your pc, right click on your Pixel 4A (should be on top of the list with a yellow exlamation mark) and update the driver choosing the USB drivers you previously downloaded. In Device Manger you should now read "Android Bootloader Interface", with no exlamation mark.
Now back to the command prompt, "fastboot devices" should now output a string with "fastboot" written next to it.
Now type 'fastboot flashing unlock' -> Follow prompt on the device to unlock the bootloader (note that this will FACTORY RESET the device).
The bootloader is now unlocked! You can now safely reboot (or it reboots on its own, I don't actually remember).
Note that after you unlock the bootloader you will see a reminder for a few seconds every time you reboot, reminding you that the phone is unlocked. That's normal and we have to live with that, as far as I know.
SECOND STEP: USING THE FACTORY IMAGE TO DOWNGRADE TO ANDROID 10
At present, TWRP is not available for Android 11. So we have to downgrade.
Download A10 factory image (version qd4a.200805.003) here: https://dl.google.com/dl/android/aosp/sunfish-qd4a.200805.003-factory-fac7c08d.zip
If you are paranoid like me, check the SHA-256 checksum of the download with some freeware hashing tool. The SHA-256 checksum should be: fac7c08d3d4cb92078fbcdbcc7e80fc4c438612a1a004d3d12814f51928458f3
Extract the files contained in the downloaded archive into the folder where your fastboot.exe is. To be clear, flash-all.bat should be in the same folder as fastboot.exe.
Place your phone in fastboot mode (Vol Down + Power).
Connect your phone to your PC.
In your command prompt type "fastboot devices" to make sure there is proper connection.
Double click "flash-all.bat".
The phone is going to reboot a few times. Just wait patiently until you read "Press any key to exit..." in the command prompt.
You've now downgraded to Android 10!
THIRD STEP: FLASHING A CUSTOM KERNEL AND TWRP
A custom kernel is needed for TWRP to work, because the stock kernel comes with no LZMA support. Just download the kernel provided by the same developer of TWRP (@nikamura): https://drive.google.com/file/d/1nuXc88t0Iokc0ha-AicOtZEUeGCGwQ-R/view?usp=sharing
And download TWRP, obviously: https://drive.google.com/file/d/1PZaU9PpYmdcAHlyi0zhNwEGnBsAHDW_E/view?usp=sharing
Place both the kernel and TWRP where your fastboot.exe is.
Note that since you just used the factory image you have to boot Android 10 at least once and run the first boot wizard, before you can flash the kernel and TWRP. Also, turn on "USB debug" in Developer Options (see "FIRST STEP" for how to reach Developer Options).
Now, connect your phone to your PC.
In your command prompt type "adb devices". Follow prompt on your phone to permanently allow the adb connection to your pc.
Type the following commands (without quotes):
"adb reboot bootloader"
"fastboot flash boot TKernel-sunfish_V0.1.img"
"fastboot reboot bootloader"
"fastboot boot sunfish_twrp201017-test5.img"
The phone should now boot into TWRP on-the-fly, but it's not been flashed yet.
Place TWRP file on your phone with the following command:
"adb push sunfish_twrp201017-test5.img /sdcard/"
Now in TWRP go to "Install" > "Install Image" > "sunfish_twrp201017-test5.img" > "Install recovery ramdisk" > Swipe.
Now back to the home of TWRP > "Reboot" > "Recovery".
The phone should now boot into TWRP! And this time it's properly installed (not just sideloaded).
You can now reboot into Android 10.
FOURTH STEP: ROOTING WITH MAGISK
Now, you need to grab your current boot image. To do this, boot into TWRP (Vol UP + Power) > "Backup" > flag only "Boot (64MB)" > "Options" tab > unflag "Enable compression" > "Backup" tab > Swipe.
Reboot to Android 10.
Disable "Automatic System Updates" in Developer Options.
Connect phone to PC.
If you browse your phone, in /sdcard/TWRP/BACKUPS/xxxxxxxx/xxxxxxx/ there will be a file named "boot.emmc.win". That's your boot image and you can rename it "boot.img". It should weigh exactly 64MB.
Download Magisk Manager apk (credits @topjohnwu): https://github.com/topjohnwu/Magisk/releases/download/manager-v8.0.7/MagiskManager-v8.0.7.apk
Copy Magisk Manager apk to your device.
Install Magisk Manager apk.
Open Magisk Manager. My locale is not English, so the following commands might slightly differ from what you will see, but still they should be easy to understand. Select 'Install' (Magisk) -> 'Select and Patch File' -> select your boot.img file -> 'Go!' -> it'll output the patched boot image to your Download folder.
Copy the magisk_patched_xxxxxx.img from Download folder to your pc, where your fastboot.exe is.
In your command prompt type:
"adb reboot bootloader"
"fastboot flash boot magisk_patched_xxxxxx.img"
"fastboot reboot bootloader"
You're now rooted!
Enter recovery to make sure TWRP is still working.
Reboot system.
Check in Magisk Manager the resulting installed version of Magisk is 21.4 (=rooted).

This worked great for me - thank you for the post!

Why would you patch the boot.img via Magisk Manager when you can just flash the Magisk v21.4 zip in TWRP?

I;m still confused AF why you would Patch the Boot.img with a working TWRP.img?
BTW: Are you passing safety net, not that it matters, but i figured i'd would on stock Android 10 at least....

Moto_Fan said:
Why would you patch the boot.img via Magisk Manager when you can just flash the Magisk v21.4 zip in TWRP?
Click to expand...
Click to collapse
Yes, that should supposedly work the same, although not personally tested.
Moto_Fan said:
I;m still confused AF why you would Patch the Boot.img with a working TWRP.img?
BTW: Are you passing safety net, not that it matters, but i figured i'd would on stock Android 10 at least....
Click to expand...
Click to collapse
Before flashing TWRP you need custom kernel.
Safetynet is ok, at the moment. Just need to flash this Magisk module: https://github.com/kdrag0n/safetynet-fix/

nor-ric said:
Yes, that should supposedly work the same, although not personally tested.
TESTED AND WORKED PERFECTLY!!!
Before flashing TWRP you need custom kernel.
Safetynet is ok, at the moment. Just need to flash this Magisk module: https://github.com/kdrag0n/safetynet-fix/
Click to expand...
Click to collapse
Yea, I already found out about the module, and it did indeed work and passed safety net after cts profile failed.
Now on too Pixel 4a #2 ON android 12 PDP1, too ROOT or NOT to ROOT??? We'll find out soon enough i guess???

nor-ric said:
Hello,
I'm posting this guide for those (like me) who can't do without TWRP on their device.
I'm providing only a step-by-step explanation. Credits to @nikamura for his kernel and TWRP: https://forum.xda-developers.com/t/twrp-3-4-0-0-for-sunfish-testing.4179101/
Credits to @Zackptg5 for his guide, from which I've started: https://forum.xda-developers.com/t/guide-unlock-root-safetynet-for-pixel-4a.4153773/
Credits to @topjohnwu for Magisk: https://github.com/topjohnwu/Magisk
DISCLAIMER: I don't take any responsibility if your phone explodes or anything... The guide is provided as is.
FIRST STEP: UNLOCKING THE BOOTLOADER
Download USB drivers for your phone here: https://androidfilehost.com/?fid=8889791610682922010
Download SDK Platform-Tools for Windows here: https://developer.android.com/studio/releases/platform-tools
Extract the SDK Platform-Tools to a directory of your choice.
Open your command prompt, change directory to where you extracted the Platform-Tools and type "fastboot". Depending on your Windows setup (I'm a linux guy, so I've used an ancient win8.1 installation in a VM...) you might receive a message of a missing dll (api-ms-win-crt-convert-l1-1-0.dll): if so, download and install the Universal C Runtime from https://support.microsoft.com/en-us...-windows-c0514201-7fe6-95a3-b0a5-287930f3560c
If you try the "fastboot" command once more, it should now work.
On your phone go to system settings -> About phone -> tap on 'Build number' several times until Developer Options is enabled.
Back out into settings and go to System -> Advanced -> Developer Options -> Enable 'OEM Unlocking'.
Switch off the phone.
Boot into fastboot by holding Vol Down + Power.
Plug the phone into a usb port of your pc.
In your command prompt type "fastboot devices". If there is no output, it means you have to install the USB driver. So, open "Device Manager" on your pc, right click on your Pixel 4A (should be on top of the list with a yellow exlamation mark) and update the driver choosing the USB drivers you previously downloaded. In Device Manger you should now read "Android Bootloader Interface", with no exlamation mark.
Now back to the command prompt, "fastboot devices" should now output a string with "fastboot" written next to it.
Now type 'fastboot flashing unlock' -> Follow prompt on the device to unlock the bootloader (note that this will FACTORY RESET the device).
The bootloader is now unlocked! You can now safely reboot (or it reboots on its own, I don't actually remember).
Note that after you unlock the bootloader you will see a reminder for a few seconds every time you reboot, reminding you that the phone is unlocked. That's normal and we have to live with that, as far as I know.
SECOND STEP: USING THE FACTORY IMAGE TO DOWNGRADE TO ANDROID 10
At present, TWRP is not available for Android 11. So we have to downgrade.
Download A10 factory image (version qd4a.200805.003) here: https://dl.google.com/dl/android/aosp/sunfish-qd4a.200805.003-factory-fac7c08d.zip
If you are paranoid like me, check the SHA-256 checksum of the download with some freeware hashing tool. The SHA-256 checksum should be: fac7c08d3d4cb92078fbcdbcc7e80fc4c438612a1a004d3d12814f51928458f3
Extract the files contained in the downloaded archive into the folder where your fastboot.exe is. To be clear, flash-all.bat should be in the same folder as fastboot.exe.
Place your phone in fastboot mode (Vol Down + Power).
Connect your phone to your PC.
In your command prompt type "fastboot devices" to make sure there is proper connection.
Double click "flash-all.bat".
The phone is going to reboot a few times. Just wait patiently until you read "Press any key to exit..." in the command prompt.
You've now downgraded to Android 10!
THIRD STEP: FLASHING A CUSTOM KERNEL AND TWRP
A custom kernel is needed for TWRP to work, because the stock kernel comes with no LZMA support. Just download the kernel provided by the same developer of TWRP (@nikamura): https://drive.google.com/file/d/1nuXc88t0Iokc0ha-AicOtZEUeGCGwQ-R/view?usp=sharing
And download TWRP, obviously: https://drive.google.com/file/d/1PZaU9PpYmdcAHlyi0zhNwEGnBsAHDW_E/view?usp=sharing
Place both the kernel and TWRP where your fastboot.exe is.
Note that since you just used the factory image you have to boot Android 10 at least once and run the first boot wizard, before you can flash the kernel and TWRP. Also, turn on "USB debug" in Developer Options (see "FIRST STEP" for how to reach Developer Options).
Now, connect your phone to your PC.
In your command prompt type "adb devices". Follow prompt on your phone to permanently allow the adb connection to your pc.
Type the following commands (without quotes):
"adb reboot bootloader"
"fastboot flash boot TKernel-sunfish_V0.1.img"
"fastboot reboot bootloader"
"fastboot boot sunfish_twrp201017-test5.img"
The phone should now boot into TWRP on-the-fly, but it's not been flashed yet.
Place TWRP file on your phone with the following command:
"adb push sunfish_twrp201017-test5.img /sdcard/"
Now in TWRP go to "Install" > "Install Image" > "sunfish_twrp201017-test5.img" > "Install recovery ramdisk" > Swipe.
Now back to the home of TWRP > "Reboot" > "Recovery".
The phone should now boot into TWRP! And this time it's properly installed (not just sideloaded).
You can now reboot into Android 10.
FOURTH STEP: ROOTING WITH MAGISK
Now, you need to grab your current boot image. To do this, boot into TWRP (Vol UP + Power) > "Backup" > flag only "Boot (64MB)" > "Options" tab > unflag "Enable compression" > "Backup" tab > Swipe.
Reboot to Android 10.
Disable "Automatic System Updates" in Developer Options.
Connect phone to PC.
If you browse your phone, in /sdcard/TWRP/BACKUPS/xxxxxxxx/xxxxxxx/ there will be a file named "boot.emmc.win". That's your boot image and you can rename it "boot.img". It should weigh exactly 64MB.
Download Magisk Manager apk (credits @topjohnwu): https://github.com/topjohnwu/Magisk/releases/download/manager-v8.0.7/MagiskManager-v8.0.7.apk
Copy Magisk Manager apk to your device.
Install Magisk Manager apk.
Open Magisk Manager. My locale is not English, so the following commands might slightly differ from what you will see, but still they should be easy to understand. Select 'Install' (Magisk) -> 'Select and Patch File' -> select your boot.img file -> 'Go!' -> it'll output the patched boot image to your Download folder.
Copy the magisk_patched_xxxxxx.img from Download folder to your pc, where your fastboot.exe is.
In your command prompt type:
"adb reboot bootloader"
"fastboot flash boot magisk_patched_xxxxxx.img"
"fastboot reboot bootloader"
You're now rooted!
Enter recovery to make sure TWRP is still working.
Reboot system.
Check in Magisk Manager the resulting installed version of Magisk is 21.4 (=rooted).
Click to expand...
Click to collapse
Would like to go this route for reasons you have stated above. Have a few questions:
1: If you use normally use Linux why did you use a Windows VM rather than simply do all operations in a Linux terminal?
2: After the above transition will SU required programs such as Titanium Backup and Adaway install and function as they have in the past? I had previously rooted current P4a and neither of the above programs would install?????
3: Will SuperSuperuser be installed under this environment?
I have rooted several devices in the past using varied methods and things seem to have changed drastically since my previous Nexus 6p
Thanks

CarlInMO said:
2: After the above transition will SU required programs such as Titanium Backup and Adaway install and function as they have in the past? I had previously rooted current P4a and neither of the above programs would install?????
Click to expand...
Click to collapse
I did the above steps and titanium backup, root explorer and other root apps work great.
CarlInMO said:
3: Will SuperSuperuser be installed under this environment?
Click to expand...
Click to collapse
You will NOT use a separate SU app - Magisk has a built-in SU interface that will pop-up and grant SU permission when an app asks for it - just like the old SU app used to do.

JohnC said:
I did the above steps and titanium backup, root explorer and other root apps work great.
You will NOT use a separate SU app - Magisk has a built-in SU interface that will pop-up and grant SU permission when an app asks for it - just like the old SU app used to do.
Click to expand...
Click to collapse
Thanks for the quick response, again!!! I like this phone but it looks at this point as if it has a rather small following here. Are you using the stock build or have you moved on to a custom ROM?

CarlInMO said:
Thanks for the quick response, again!!! I like this phone but it looks at this point as if it has a rather small following here. Are you using the stock build or have you moved on to a custom ROM?
Click to expand...
Click to collapse
Using stock android 10 image from google because TWRP and Edxposed are stable with android 10, not 11.

And what happens to root & TWRP after upgrade back to Android 11. I assume installed apps continue to operate OK

TWRP has now been modded and is working with A11! Details in the TWRP thread!

How To Guide A13 detailed guide to Root & OTA's & pass SafetyNet / Play Integrity

My Phone already came with A13 and OEM unlocking became available straight after connecting to wifi.
If it stays grayed out for you or you need to update to A13 / July A12 patch first please refer to other guides such as this one.
Disclaimer:
I don't take responsibility for whatever happens to your device. Expect your device to get wiped.
While everything went without a hitch for me, there is no guarantee it will for you as well.
sources:
Pixel 6 root guide
Pixel 6a root guide
Magisk root guide
Magisk OTA guide
As a sidenote, if you are already rooted and want Magisk to have a backup of the stock boot image, just flash stock boot.img (this will remove root), then boot the Magisk patched boot image and do "direct install" through Magisk. Thats essentially just unrooting and re-rooting.
Prerequisites:​Update ur phone to the newest available version if possible. At least you probably should be on June 2022 patch, though this Guide is meant for A13.
Get the original Factory Image (not OTA) from google, the version that matches the currently installed one (aka probably the newest if you're fully up to date).
Get the Magisk app apk from the official Github.
Get the adb & fastboot tools as well as necessary google USB drivers (15s installer seems to be outdated yet again).
Get the safetynet-fix-MOD Module from it's Github. (official safetynet-fix got updated and works as well not anymore as of February update.)
Preparing files and device:​Open the downloaded firmware archive. Inside there will be another zip archive (image-bluejay-[...].zip). Open this and get the boot image (boot.img) from it.
Connect your phone to your pc over USB, and copy both the Magisk apk file and the boot.img file to your phone.
On your phone, open Settings -> About phone, then tap on "Build number" until it says "deveoper options unlocked".
In Settings -> System -> Developer options turn on "OEM unlocking" as well as "USB debugging" and then check the "allow" and "remember" option when it asks you if it should remember your computer.
Now install the Magisk app with the apk, then open it, select "install" and then "select and patch a file" and select the boot.img you moved to your phone earlier.
Magisk saves the patched boot.img in your Downloads folder, move it to your computer.
Now you should have a modified boot.img on your computer, OEM unlocking and adb debugging enabled, as well as your computer authorised for adb on your phone.
You should also not have any outstanding OTA's or reboots after OTA installation.
Unlocking and Rooting:​Note that unlocking your bootloader will wipe your phone!
Just rooting it won't wipe it if you already have an unlocked bootloader.
Open a terminal on your pc and type adb devices. It should show some number if your adb is working correctly.
Type adb reboot bootloader and wait for it to reboot to bootloader.
Then type fastboot flashing unlock and confirm on your phone that you want to unlock your bootloader.
After you unlocked your bootloader check your phone's screen, specifically where it lists the Bootloader version (second line).
Compare the version number with the one of the bootloader image inside your downloaded firmware zip file. (bootloader-bluejay-bluejay-[...].img)
Also compare the Baseband version with the one of the radio image. (radio-bluejay-[...].img)
If either of those has a newer version in the downloaded factory image, unpack it and flash the new version by executing either command respectively.
Code:
fastboot flash bootloader <drag the new bootloader.img here>
fastboot flash radio <drag new radio.img here>
Now do
Code:
fastboot boot <drag magisk patched boot image here>
and your phone should boot and you should see the first setup screen again.
After going through that, repeat the above steps to enable USB debugging as well as to authorise and remember your computer.
At this point it's also important to turn off "Automatic system updates" in Settings -> Developer options as well. (so that future OTA's don't mess up your phone)
Since your phone got wiped you need to copy the Magisk app apk and install it again.
Now also copy the safetynet-fix-Mod.zip module to your phone.
When you open Magisk and it asks you to complete additional steps after opening it select "cancel" and instead tap on "install" and then -> "direct install".
When Magisk is done tap on "reboot".
After rebooting enable "Zygist" in Magisk's settings and then tap on "Configure DenyList".
Tap the three dot menu and check "Show system apps", then search for "Google Play services" and "Google Play Store", expand them and tap the checkmark, this should select all subcomponents at once for. Do this for both, Play Services and Play Store.
Exit Magisk Settings and tap on the "Modules" tab in Magisk.
Select "Install from storage" and find and select the "safetynet-fix-Mod.zip".
Let it flash and reboot and that's it, you should now pass SafetyNet and Play Integrity.
Play Integrity was a bit iffy for me, after immediately checking it failed but after turning Play Protect in Play Store app settings off and on again and rebooting it worked and never failed again.
OTAs​
Spoiler: OTA sideload with Pixel Flasher (recommended)
Download the newest OTA and Pixel Flasher.
In Magisk app, disable all modules.
Enable adb debugging if you don't have it enabled.
Connect your phone to your computer and start Pixel Flasher.
Enter the path to your platform tools at the top, below select your phone from the list.
For "Pixel Phone Factory Image" click "browse" and select your downloaded OTA, then select the one boot image that should appear in the list below.
For "Flash Mode" select "Full OTA" and don't check any of the "Flash Options" below.
Click "Flash Pixel Phone" and confirm.
Wait for the OTA to complete and your phone to reboot and then unlock it.
Check your android version f.e. under the quick tiles, it should match the update version you installed just now.
Also confirm that adb debugging is still active.
If you see an "update completed" or "finishing update" sort of notification, wait for it to complete.
If you don't see one, just wait a few minutes.
In Pixel Flasher, select your device again from the adb list at the top, also select the one boot image again that should be in the list, then click the "Patch" button on the right.
When that completed you should see a new entry in the boot.img list with a "patch" symbol next to it.
Select that and click the "Live Boot" button on the right.
After your phone reboots, go into Magisk app, click "Install" -> "direct install", then don't reboot yet, now enable all your modules again and then reboot.
Optionally you can do the same thing again to update the other slot as well, resulting in both of your slots being on the newest update.​If you want to do that you might wanna skip the entire re-rooting process on your first update pass, so your "backup slot" will be unrooted stock.​Essentially you'd do Steps [1] - [6], then jump back to [3] and follow all the way to the end [9].​​(example: you are on Slot_A pre-update, update will apply to Slot_B and reboot you in Slot_B, you update again and it'll apply to Slot_A and reboot you in Slot_A, you re-root Slot_A and continue to use it as normal while having an unrooted fully updated Slot_B as backup)​​
Spoiler: OTA sideload manually
Download the newest OTA as well as the factory image with the matching version.
Extract the boot.img from the downloaded factory image, move it to your phone, open Magisk app, click "Install" -> "select and patch a file", then let it patch the boot.img and move the new patched image back to your computer.
In Magisk app, disable all modules.
Enable adb debugging if you don't have it enabled, then from your computer's terminal, do adb devices to check your device connection, after that do adb reboot sideload
Your phone will reboot to download mode. It should be prompting you to apply the update now.
Do adb sideload <drag_your_downloaded_OTA.zip_here>
Choose "Reboot system now" on the menu that appears after the update completes.
Wait for your phone to reboot and unlock it.
Check your android version f.e. under the quick tiles, it should match the update version you installed just now.
Also confirm that adb debugging is still active.
If you see an "update completed" or "finishing update" sort of notification, wait for it to complete.
If you don't see one, just wait a few minutes.
Do adb reboot bootloader and after your phone boots into bootloader you can do fastboot boot <drag_the_patched_boot_image_here> and wait for it to boot.
Go into Magisk app, click "Install" -> "direct install", then don't reboot yet, now enable all your modules again and then reboot.
Spoiler: Update with factory image with Pixel Flasher
Download the newest factory image and Pixel Flasher.
Open your Magisk app and disable all modules.
Connect your phone to your computer and start Pixel Flasher.
Enter the path to your platform tools at the top, below select your phone from the list.
For "Pixel Phone Factory Image" select your downloaded firmware, then select the one boot image that should appear in the list below.
For "Flash Mode" choose "Keep Data", then click the big "Flash Pixel Phone" button.
When it completes click the "Reboot to Bootloader" button near the top.
Additionally select the boot image from the list and click "Patch".
Select the new patched boot image that will appear below.
When your phone rebooted to bootloader click "Live Boot" and it will boot system with root.
Open Magisk app, click "Install" -> "direct install", then don't reboot yet, re-enable all your modules and reboot your phone.
Spoiler: Magisk OTA method
I don't recommend using the Magisk OTA method as it seems there is a bug that might lead to corrupt and bootloop your device.
I list it regardless if you want to try, but I'd recommend to update by sideloading the OTA instead.
check the official Magisk OTA guide for reference.
tldr:
don't modify or even rw remount read only partitions such as /system or /vendor
disable automaric otas in dev menu
when otas are available, open Magisk app, tap on "Uninstall Magisk" -> "restore images", and do NOT reboot.
Also disable all modules just in case.
then open Settings app -> System -> System update
wait for the installation to be fully done, both steps 1 and 2, then do NOT press restart now or reboot button
go back to Magisk, tap on "install" -> "install to inactive slot
after Magisk installed you can press the "reboot" button in Magisk

If you want to remove some preinstalled apps you dont need first check your user id with
Code:
adb shell cmd package list users
Usually it's 0, if not then replace it with your user id, then you can simply use
Code:
adb shell cmd package uninstall --user 0 <package_name>
adb shell cmd package disable-user --user 0 <package_name>
to uninstall / disable the app over adb.
Attached is a powershell script that removes / disables all apps you put in $removeApps or $disableApps respectively.
The current selection is by no means recommended, it is just a collection that won't result in a bootloop, but thats about it. (yes the commented ones included, they are just commented from the last time I used it)
(change file extension to .ps1 if you want to use it, modify it to fit your needs)
You can always reinstall / enable apps by using
Code:
adb shell cmd package install-existing --user 0 <package_name>
adb shell cmd package enable --user 0 <package_name>

Hi,
Thank you for your thorough guide.
I'm stuck after this command:
"fastboot flashing unlock"
I get error "waiting for device"
I have installed the USB drivers as per the link you provided, I think, not sure what's happening.
Any suggestion?
Many thanks.
UPDATE: I used a different USB cable and it worked!!

juv3nal said:
Hi,
Thank you for your thorough guide.
I'm stuck after this command:
"fastboot flashing unlock"
I get error "waiting for device"
I have installed the USB drivers as per the link you provided, I think, not sure what's happening.
Any suggestion?
Many thanks.
Click to expand...
Click to collapse
Make sure you have enabled OEM unlocking and USB debugging in Developer Options
Also, you can try the command "fastboot devices" to make sure your device is visible to your PC/Laptop.

^this
if "fastboot devices" doesnt show the id for your phone then the drivers arent working properly.
iirc there might be an issue with the drivers being properly detected sometimes, only had this once on an older computer.
The original now outdated 15s installer has instructions in the"Note" section on how to fix device detection.
if "fastboot devices" returns the device id then I can only think of OEM unlocking being disabled.
if it still doesnt work, consider switching to the full sdk platform tools, idk if it includes the usb drivers.

G5-User7080 said:
^this
if "fastboot devices" doesnt show the id for your phone then the drivers arent working properly.
iirc there might be an issue with the drivers being properly detected sometimes, only had this once on an older computer.
The original now outdated 15s installer has instructions in the"Note" section on how to fix device detection.
if "fastboot devices" returns the device id then I can only think of OEM unlocking being disabled.
if it still doesnt work, consider switching to the full sdk platform tools, idk if it includes the usb drivers.
Click to expand...
Click to collapse
Aswell as using a USB A connected to a USB 2.0 port

This guide worked very well for unlocking my Pixel 6a.
Sadly I cannot root my device, probably because the newest factory image is from February 2023. Does anyone know where to get the newest factory image from?

Okay, I managed to bootloop my device lol
How I fixed it + root:
I used the PixelFlasher to downgrade to the newest factory image (from February) + Data Wipe (sadly).
Then I went through your guide again and it successfully got rooted.

d_TraXer said:
Sadly I cannot root my device, probably because the newest factory image is from February 2023. Does anyone know where to get the newest factory image from?
Click to expand...
Click to collapse
Newest Factory Image is from April though.
I linked it under "Prerequisites".
You can use Pixelflasher just fine for rooting as well, check the OTA with Pixelflasher section, it's essentially just applying OTA and "re-rooting".
If you already figured out how to use Pixelflasher you might as well use that to flash factory
You can also check the Pixel 6 Guide that's linked in "sources", that one is very comprehensive and includes multiple methods, just be aware that versions and downloads are different for the Pixel 6a, the general process is the same though.

G5-User7080 said:
Newest Factory Image is from April though.
I linked it under "Prerequisites".
Click to expand...
Click to collapse
Okay that's weird, I checked the link multiple times but everytime I looked the newest factory image was from February. Just now I noticed a banner on top of the page. It says that the website got automatically translated to german. So I switched back to English and now the newest factory image is from April.
Anyways thank you for your response. Now I can update to the newest version.

Thanks for the pointer to the MOD version, Integrity Check was only passing Basic with the original safetynet, the MOD version also passes Device now.