Database Info

Can you root the Pixel 3a?

The price is amazing but I need root first.

i made these but havent tested them yet. they were made using the newest canary magisk. i would boot and not flash first just to make sure they work. ill know tomorrow if they work as that is when i will have my phone i made one for each update that was out on googles site. so make sure you use the proper one.
https://cdn.discordapp.com/attachme...981002485770/patched-pd2a.190115.032-boot.img
https://cdn.discordapp.com/attachme...981908586506/patched-pd2a.190115.029-boot.img
they do indeed work

I am thinking,,,,but have no idea, the Pixel 3a is basically the same as the Plixel 3 correct? So wouldnt the current magisk and TWRP work for it? TWRP might not if Google did anything different but Magisk in general should work should it not?

Archangel said:
I am thinking,,,,but have no idea, the Pixel 3a is basically the same as the Plixel 3 correct? So wouldnt the current magisk and TWRP work for it? TWRP might not if Google did anything different but Magisk in general should work should it not?
Click to expand...
Click to collapse
the soc is different so twrp wont work. magisk is fine as it patches the boot.img of the device

Awesome, thanks for letting us know. TWRP should hopefully be an easy fix.
pbanj said:
the soc is different so twrp wont work. magisk is fine as it patches the boot.img of the device
Click to expand...
Click to collapse

Archangel said:
Awesome, thanks for letting us know. TWRP should hopefully be an easy fix.
Click to expand...
Click to collapse
kernel source is out so it shouldnt be long

TWRP is what is messing up the pixel 3 and 3 XL. if rotting do it topjohnwu's way. Patch your boot image. Download your factory image and extract the boot image. TWRP has been conflicting with magisk and especially 19.1. Many issues that do not get reported on XDA in fear of TWRP team. But it doesn't work right on the pixel 3 line. Not like it use to.

pbanj said:
i made these but havent tested them yet. they were made using the newest canary magisk. i would boot and not flash first just to make sure they work. ill know tomorrow if they work as that is when i will have my phone i made one for each update that was out on googles site. so make sure you use the proper one.
https://cdn.discordapp.com/attachme...981002485770/patched-pd2a.190115.032-boot.img
https://cdn.discordapp.com/attachme...981908586506/patched-pd2a.190115.029-boot.img
Click to expand...
Click to collapse
these work
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
also safetynet passes
https://forum.xda-developers.com/showpost.php?p=79497002&postcount=13 pay should be working. ill try to test it in store tomorrow.

In case anyone wants to put the old style nav bar on thier new phone this still works
How to disable Android Pie gestures on the Google Pixel 3
1. Install any 3rd-party launcher of your choice. This is a must because otherwise, you won’t have a launcher app left once we’re done with this tutorial!
2. Set up ADB on your PC. Here’s a tutorial we previously wrote that you should you through the process.
3. Connect your Pixel 3 to your PC and open up a command prompt/terminal in the directory where you downloaded the ADB binary. Enter the following command depending on your OS:
Windows Command Prompt
adb shell
Windows Power Shell
.\adb shell
macOS/Linux Terminal
./adb shell
4. Now, enter the following command to uninstall the Pixel Launcher from the current user.
pm uninstall -k --user 0 com.google.android.apps.nexuslauncher
5. Now, enter this command to re-enable the stock navigation bar after reboot. This is the setting you’ll be changing by issuing the below command.
settings put secure system_navigation_keys_enabled 1
6. Reboot your Pixel 3.
7. Once you’re booted back up, you should see the original 3 button navigation bar layout and the original vertical stacked card recent apps overview.

Can't unlock Pixel 3a
I have been jailbreaking/rooting since the first iPhone, and every device I have owned since.
So I was fully expecting to do it again, and easily, with the Pixel 3a (my first direct-from-Google device).
I enabled Developer options.
I checked the 'Allow unlocking' switch
I enabled USB debugging
I ran the CMD window from the proper path
ADB recognized the device
Reboot fastboot worked
However, it will not recognize 'fastboot flashing unlock', returning the list of acceptable commands,
and flashing is not on the list.
What am I missing?

ggibby said:
I have been jailbreaking/rooting since the first iPhone, and every device I have owned since.
So I was fully expecting to do it again, and easily, with the Pixel 3a (my first direct-from-Google device).
I enabled Developer options.
I checked the 'Allow unlocking' switch
I enabled USB debugging
I ran the CMD window from the proper path
ADB recognized the device
Reboot fastboot worked
However, it will not recognize 'fastboot flashing unlock', returning the list of acceptable commands,
and flashing is not on the list.
What am I missing?
Click to expand...
Click to collapse
update your adb and fastboot https://developer.android.com/studio/releases/platform-tools.html

pbanj said:
update your adb and fastboot https://developer.android.com/studio/releases/platform-tools.html
Click to expand...
Click to collapse
YOU. ROCK.
Thanks much!

pbanj said:
i made these but havent tested them yet. they were made using the newest canary magisk. i would boot and not flash first just to make sure they work. ill know tomorrow if they work as that is when i will have my phone i made one for each update that was out on googles site. so make sure you use the proper one.
https://cdn.discordapp.com/attachme...981002485770/patched-pd2a.190115.032-boot.img
https://cdn.discordapp.com/attachme...981908586506/patched-pd2a.190115.029-boot.img
they do indeed work
Click to expand...
Click to collapse
Boot image working great! Got magisk, adaway and swift installer working perfectly! Thanks a million!
Sent from my Pixel 3a using Tapatalk

I'm waiting for TWRP to drop before I swap my boot image out, but was able to flashboot with the modded boot image to block ads and set up unlocked tethering without replacing the stock image. Thanks for the work on the boot images!

Edit: Nvm. Guess I probably have to wait til I get my cord so I can hook it up to the PC.

EnragedPopsicle said:
I'm waiting for TWRP to drop before I swap my boot image out, but was able to flashboot with the modded boot image to block ads and set up unlocked tethering without replacing the stock image. Thanks for the work on the boot images!
Click to expand...
Click to collapse
How do you setup unlocked tethering?

EnragedPopsicle said:
I'm waiting for TWRP to drop before I swap my boot image out, but was able to flashboot with the modded boot image to block ads and set up unlocked tethering without replacing the stock image. Thanks for the work on the boot images!
Click to expand...
Click to collapse
Are you saying that unlocked phone does not support tethering out of the box?

It does, but only if you have a tethering plan on your cell plan, at least in the US. I made the build.prop provisioning edit to unlock mine.

EnragedPopsicle said:
It does, but only if you have a tethering plan on your cell plan, at least in the US. I made the build.prop provisioning edit to unlock mine.
Click to expand...
Click to collapse
Can you elaborate how you edited the build.prop?

Fi, it's your data, you paid for it, do whatever you want. It should be the law.

is it possible to install magisk on huawei emui 9 or 8?

i have the firmware for emui 8, but i am not sure if my phone can be rooted with emui 9
i already extracted update.app but i dont know what to flash, how and where? can someone help?

First of all, before you read my guide below, how much knowledge do you have so far? Is your bootloader unlocked? That is the hardest part. If it's still locked, you have to either buy a code somewhere or use quite some effort, opening up your phone and do some tinkering. I will not go into details because I hope it's not necessary and you are already there .
I successfully rooted my honor 9 (STF-L09) with magisk using the official guide and also a guide on the OpenKirin homepage that uses appropriate terminology and commands for Kirin devices. However, I had to do some things differently, because Magisk > v20.4 fails to install somehow.
I would love to know why the installation of higher versions fails and install Magisk v23.0, but I can only tell you how I installed v20.4. Hope you have ramdisk because it's a much better experience with Magisk. I had to do it on EMUI 9 before I downgraded, so do not upgrade to EMUI 9, you may lose ramdisk! I will try to explain the install from recovery with EMUI as good as I remember, but first the ramdisk way. As always, follow at your own risk! Can just confirm it worked on my phone!
Follow the official Magisk guide, but just until before you reach "Patching Images".
If you have ramdisk, got to the next step. Otherwise, read the guide about magisk from recovery and follow my explanation at the bottom afterwards.
Now that we have the necessary info, we need an older version of Magisk Manager to get v20.4 running. 7.5.1 is the latest Manager compatible with Magisk v20.4, but you are welcome to DYOR. Get Matrix Manager from the official Github releases.
Install Magisk Manager 7.5.1. Connect your phone and run adb install PATH_TO_MM_APK
To actually root the device with Magisk v20.4, we need to tell Magisk Manager to stfu about the outdated version and available updates. We can achieve this by modyfying the update channel in the settings to a custom channel. You can get the appropriate URL for the setting in this github repository. This is the appropriate commit. The link to the raw file is the following: https://raw.githubusercontent.com/t...5ffa9b079f3a411dd2c00a80a3d985ccc/stable.json. Copy the link to the raw stable.json and paste it in the settings of Magisk Manager as the custom channel URL. Restart Magisk Manager and verify it does not complain about the old version anymore.
Now Magisk Manager allows to actually patch the image. You should continue with the OpenKirin guide now. The official guide uses "boot" instead of "ramdisk", which is probably not appropriate for your device. But again, DYOR to make sure.
That should be it if you've got a ramdisk. If not, first read "Magisk in Recovery" in the official guide. Then continue with "Patching Images" and be careful to use "recovery" when both "recovery" and "boot" are mentioned. The OpenKirin guide does not include patching recovery.
AFAIK with EMUI 8 you should have a ramdisk. Had to use Magisk from recovery when I was on EMUI 9, which is why I'm glad I downgraded.
If anyone thinks I'm talking BS, I would love to know how to install higher versions of Magisk myself, or what could be the issue!

witty_bricker said:
First of all, before you read my guide below, how much knowledge do you have so far? Is your bootloader unlocked? That is the hardest part. If it's still locked, you have to either buy a code somewhere or use quite some effort, opening up your phone and do some tinkering. I will not go into details because I hope it's not necessary and you are already there .
I successfully rooted my honor 9 (STF-L09) with magisk using the official guide and also a guide on the OpenKirin homepage that uses appropriate terminology and commands for Kirin devices. However, I had to do some things differently, because Magisk > v20.4 fails to install somehow.
I would love to know why the installation of higher versions fails and install Magisk v23.0, but I can only tell you how I installed v20.4. Hope you have ramdisk because it's a much better experience with Magisk. I had to do it on EMUI 9 before I downgraded, so do not upgrade to EMUI 9, you may lose ramdisk! I will try to explain the install from recovery with EMUI as good as I remember, but first the ramdisk way. As always, follow at your own risk! Can just confirm it worked on my phone!
Follow the official Magisk guide, but just until before you reach "Patching Images".
If you have ramdisk, got to the next step. Otherwise, read the guide about magisk from recovery and follow my explanation at the bottom afterwards.
Now that we have the necessary info, we need an older version of Magisk Manager to get v20.4 running. 7.5.1 is the latest Manager compatible with Magisk v20.4, but you are welcome to DYOR. Get Matrix Manager from the official Github releases.
Install Magisk Manager 7.5.1. Connect your phone and run adb install PATH_TO_MM_APK
To actually root the device with Magisk v20.4, we need to tell Magisk Manager to stfu about the outdated version and available updates. We can achieve this by modyfying the update channel in the settings to a custom channel. You can get the appropriate URL for the setting in this github repository. This is the appropriate commit. The link to the raw file is the following: https://raw.githubusercontent.com/t...5ffa9b079f3a411dd2c00a80a3d985ccc/stable.json. Copy the link to the raw stable.json and paste it in the settings of Magisk Manager as the custom channel URL. Restart Magisk Manager and verify it does not complain about the old version anymore.
Now Magisk Manager allows to actually patch the image. You should continue with the OpenKirin guide now. The official guide uses "boot" instead of "ramdisk", which is probably not appropriate for your device. But again, DYOR to make sure.
That should be it if you've got a ramdisk. If not, first read "Magisk in Recovery" in the official guide. Then continue with "Patching Images" and be careful to use "recovery" when both "recovery" and "boot" are mentioned. The OpenKirin guide does not include patching recovery.
AFAIK with EMUI 8 you should have a ramdisk. Had to use Magisk from recovery when I was on EMUI 9, which is why I'm glad I downgraded.
If anyone thinks I'm talking BS, I would love to know how to install higher versions of Magisk myself, or what could be the issue!
Click to expand...
Click to collapse
thanks for your reply, I have the bootloader unlocked already, but I don't know what to flash and what is boot.img and recovery.img
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Relected said:
thanks for your reply, I have the bootloader unlocked already, but I don't know what to flash and what is boot.img and recovery.img
Click to expand...
Click to collapse
Well, that is why I linked you the guide from the OpenKirin page, because they tell you to use ramdisk.img (in your case all caps RAMDISK.img). On some devices, the boot partition is split into ramdisk.img and kernel.img. On others you have boot.img. I know it's kind of confusing, but if you are SURE that you have the right firmware for your phone, then it's ramdisk.img for you.
The fact that they use ramdisk.img in the OpenKirin guide indicates that Kirin devices usually have a ramdisk.img. If you want to be 100% sure, go to adb shell and check the block devices. For me it's
Code:
ls -l /dev/block/platform/hi_mci.0/by-name
. If you can't find the by-name directory, type
Code:
ls -lR /dev/block
.
If you have a partition named "ramdisk_a" or "ramdisk", then everything is fine and you can flash the ramdisk as per the OpenKirin guide. If you have no "ramdisk" partition but a "boot" partition instead, then you have the wrong firmware. And should not proceed.
Other than that, you should be all set. Use Magisk v20.4 to patch the image as described above and follow the OpenKirin guide. Cannot guarantee that it works though, I can only speak for my STF-L09.

General [UNOFFICIAL] Recovery for Veux/Peux

Edit:
I am not the Developer.
It seems like it will still take quite a while for well known custom recoveries to be available as the device has a/b partions
Till then we can use an unofficial Lineage recovery
It is not the best but it has basic stuff like adb sideload mode (to flash stuff) and format data
I'll attach the file below but this is how you apply/install it
fastboot flash vendor_boot vendor_boot.img
^^^ here add the file path or just drag n drop it
This was only possible because of
Mod Edit: Link Removed
go check them out they have some unofficial roms for the device too!
Disclaimer: I am not responsible for any issues this causes to your device, please uss this at your own risk
also attaching a link just in case you're unable to download
vendor_boot
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
edit: since a lot of people were confused gonna add this
you do not directly go in and flash the recovery
First you need to flash a boot.img file then only can you flash the recovery
I'll attach boot.img file
Here is how to flash correctly
fastboot flash boot boot.img
fastboot flash vendor_boot vendor_boot.img

BR4UTAL said:
Are there any custom recoveries for The Poco X4 Pro? (Veux)
Click to expand...
Click to collapse
Not yet, Stay tuned...

coolpixs4 said:
Not yet
coolpixs4 said:
Not yet
Click to expand...
Click to collapse
Oh I see, thanks
Click to expand...
Click to collapse

Lineage recovery Mod Edit: Link Removed

yannickoczkowski said:
Lineage recovery Mod Edit: Link Removed
Click to expand...
Click to collapse
The file extension is gone

Rip ig that's that

not any news of custom recovery ?

sami8r8 said:
not any news of custom recovery ?
Click to expand...
Click to collapse
Only an unofficial Lineage recovery as of yet...

still no any poco X4 Pro 5G twrp news

p2pteam said:
still no any poco X4 Pro 5G twrp news
Click to expand...
Click to collapse
sadly every dev seems to be saying "security this, security that" i personally don't think it's that big of a issue since other devices with AB partitioning and same sort of encryptions have had TWRP made for them
Prime example would be the Poco F4 which released like a week ago, it got twrp made for it just after 2 days of release (unofficial but yeah)
also what are the chances of someone being a security freak and still modding the hell out of their device?
Dunno but from what i understand not a very high chance so yeah

This recovery is with fastbootd and this fastbootd dont work
correctly. (fastboot stay original, but fastbootd is from lineage after flash this file)
i try it yesterday and i have problems with "flash" command for
some partitions
adb sideload work like charm

sami8r8 said:
not any news of custom recovery ?
Click to expand...
Click to collapse
Work is underway, but so far it is not possible to make the recovery decrypt the date.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You can of course disable it (encryption), but it's not very convenient

Hey I tried flashing the vendor_boot.img via the stated method but it didn't work. Can anyone help me how to use it? I don't want to download the entire rom just to root it.

Soma Das said:
Hey I tried flashing the vendor_boot.img via the stated method but it didn't work. Can anyone help me how to use it? I don't want to download the entire rom just to root it.
Click to expand...
Click to collapse
I didn't understand what it was about.

arraki said:
I didn't understand what it was about.
Click to expand...
Click to collapse
I mean I want a recovery that is compatible with miui and can be used to flash magisk.
The conventional method of rooting is by patching the stock boot.img and flashing it but getting the stock boot.img requires downloading the rom (4GB<) and I don't have WiFi or unlimited data. So I wanted to just simply flash magisk.zip and root my phone.
As for what I said in previous comment, I flashed the given vendor_boot.img but couldn't get a custom recovery, just the plane MIUI Recovery. That's why I wanted to ask what should I do now.

Soma Das said:
I mean I want a recovery that is compatible with miui and can be used to flash magisk.
The conventional method of rooting is by patching the stock boot.img and flashing it but getting the stock boot.img requires downloading the rom (4GB<) and I don't have WiFi or unlimited data. So I wanted to just simply flash magisk.zip and root my phone.
As for what I said in previous comment, I flashed the given vendor_boot.img but couldn't get a custom recovery, just the plane MIUI Recovery. That's why I wanted to ask what should I do now.
Click to expand...
Click to collapse
You need to know what is your current slot A/B and flash it to current slot
fastboot getvar all
and find current slot (mostly it's down on list)
then write:
fastboot flash vendor_boot_a vendor_boot.img
or
fastboot flash vendor_boot_b vendor_boot.img
or
you can flash it to both slots =)
i recommended: you need to be in fastbootd for full priv...
tip: if you are in fastboot and write "fastboot reboot fastboot", then you are in fastbootd with full priv.
tip2: use this file and flash it. worked for me
vendor_boot
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
if you need boot.img wih magisk patch, tell me your version (phone and miui version) and i can give you link .)

Fedon said:
You need to know what is your current slot A/B and flash it to current slot
fastboot getvar all
and find current slot (mostly it's down on list)
then write:
fastboot flash vendor_boot_a vendor_boot.img
or
fastboot flash vendor_boot_b vendor_boot.img
or
you can flash it to both slots =)
i recommended: you need to be in fastbootd for full priv...
tip: if you are in fastboot and write "fastboot reboot fastboot", then you are in fastbootd with full priv.
tip2: use this file and flash it. worked for me
vendor_boot
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
if you need boot.img wih magisk patch, tell me your version (phone and miui version) and i can give you link .)
Click to expand...
Click to collapse
I bought this device yesterday "Redmi Note 11 pro+ 5g and miui version is 13.0.6 Global" Please give magisk patched boot.img

shrialex said:
I bought this device yesterday "Redmi Note 11 pro+ 5g and miui version is 13.0.6 Global" Please give magisk patched boot.img
Click to expand...
Click to collapse
Ok, no problem.
Can you upload your "about phone" ?
I want to be sure what to send you.
This screen:

Fedon said:
You need to know what is your current slot A/B and flash it to current slot
fastboot getvar all
and find current slot (mostly it's down on list)
then write:
fastboot flash vendor_boot_a vendor_boot.img
or
fastboot flash vendor_boot_b vendor_boot.img
or
you can flash it to both slots =)
i recommended: you need to be in fastbootd for full priv...
tip: if you are in fastboot and write "fastboot reboot fastboot", then you are in fastbootd with full priv.
tip2: use this file and flash it. worked for me
vendor_boot
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
if you need boot.img wih magisk patch, tell me your version (phone and miui version) and i can give you link .)
Click to expand...
Click to collapse
Thanks.
For boot.img I am using MIUI 13.0.6 Indian rom (stock)

Fedon said:
Ok, no problem.
Can you upload your "about phone" ?
I want to be sure what to send you.
This screen:
View attachment 5677359
Click to expand...
Click to collapse
Sure, here I'm

Question Pixel 6a on Official 13 - is Root possible

Phone arrived today, got on the website, downloaded the latest August build. I did not notice it was 13. Unlocked the bootloader, flashed the image and the phone booted right up. I was about to root when I realized I was on 13 and then came here and saw the PSA about the phone can't be downgraded from 13 to a previous build.
My question (I've searched and found nothing), can I root the Pixel 6a on the official August 13 build with Magisc? Will I need to do anything differently like disable verifications and stuff? Usually I install the latest Magisk (v25.2), patch the boot.img, flash the patchedboot.img and profit.
Thanks in advance.

Bad Bimr said:
My question (I've searched and found nothing) can I root the Pixel 6a on the official August 13 build with Magisc?
Click to expand...
Click to collapse
Yes
Bad Bimr said:
Will I need to do anything differently like disable verifications and stuff?
Click to expand...
Click to collapse
No. Disabling verity and verification is optional.
Bad Bimr said:
Usually I install the latest Magisk (v25.2), patch the boot.img, flash the patchedboot.img and profit.
Thanks in advance.
Click to expand...
Click to collapse
Yep

Rooting Android 13 works exactly the same way as Android 12. The only thing that would prevent rooting is a locked bootloader. Google hasn't done anything to prevent root (yet).

Lughnasadh said:
Yes
Click to expand...
Click to collapse
It worked like a charm. Only thing is I cannot get YoutubeVanced to work on 13. I assume the Youtube Version in 13 is a higher build number and it will not work.
Thanks.

V0latyle said:
Google hasn't done anything to prevent root (yet).
Click to expand...
Click to collapse
I wish that, in addition to the "allow bootloader unlock" switch, there was a "don't be a nanny" switch.

Bad Bimr said:
It worked like a charm. Only thing is I cannot get YoutubeVanced to work on 13. I assume the Youtube Version in 13 is a higher build number and it will not work.
Thanks.
Click to expand...
Click to collapse
Glad it all worked out! Yeah, the version of YouTube that comes with A13 is higher than the Vanced YouTube version.

Just use the new revanced builder. It's on Reddit. There's even APKs there. You can scan for viruses if you want.
r/revancedapks
r/revancedapks: Share your revanced apks.
www.reddit.com

i wish i could unlock my bootloader, mine is still greyed out

beanaman said:
Just use the new revanced builder. It's on Reddit. There's even APKs there. You can scan for viruses if you want.
r/revancedapks
r/revancedapks: Share your revanced apks.
www.reddit.com
Click to expand...
Click to collapse
Are there any rooted versions that work with A13? Is building it simple? I didnt see anything there just doing a quick search.

Yes very simple to build. Just use the builder and follow instructions to patch current YouTube APK.
Here is link to GitHub w instructions.
How to use revanced builder on Android
A NodeJS ReVanced builder. Contribute to reisxd/revanced-builder development by creating an account on GitHub.
github.com

beanaman said:
Yes very simple to build. Just use the builder and follow instructions to patch current YouTube APK.
Here is link to GitHub w instructions.
How to use revanced builder on Android
A NodeJS ReVanced builder. Contribute to reisxd/revanced-builder development by creating an account on GitHub.
github.com
Click to expand...
Click to collapse
Ok, that was stupid simple. Thanks

"Disabling verity and verification is optional"
What are the advantages or disadvantages of doing that?

beanaman said:
Just use the new revanced builder. It's on Reddit. There's even APKs there. You can scan for viruses if you want.
r/revancedapks
r/revancedapks: Share your revanced apks.
www.reddit.com
Click to expand...
Click to collapse
Thank you for this!

Bad Bimr said:
It worked like a charm. Only thing is I cannot get YoutubeVanced to work on 13. I assume the Youtube Version in 13 is a higher build number and it will not work.
Thanks.
Click to expand...
Click to collapse
Just got a pixel 6a, updated to 13, pulled Vanced Manager off my old phone, and installed it. It's working fine for me
¯⁠\⁠_⁠(⁠ツ⁠)⁠_⁠/⁠¯

Hi, how to fix this issue?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

7kAi said:
Hi, how to fix this issue?
View attachment 5804131
Click to expand...
Click to collapse
Try using the latest Platform Tools and also try using command prompt instead of PowerShell. Put the patched image in the Platform Tools folder, open up command prompt from that folder and flash.
fastboot flash boot <nameofpatchedimage>

Lughnasadh said:
Try using the latest Platform Tools and also try using command prompt instead of PowerShell. Put the patched image in the Platform Tools folder, open up command prompt from that folder and flash.
fastboot flash boot <nameofpatchedimage>
Click to expand...
Click to collapse
worked using
fastboot.exe flash boot <nameofpatchedimage>
Thanks!

people were reporting that the OTA Beta QPR2 (it was qp something) was having issues with root, but as far as I can tell, its cleared up.
Or just use AICP for the 6a. no issues. Had issues with crdroid

TechX1991 said:
people were reporting that the OTA Beta QPR2 (it was qp something) was having issues with root, but as far as I can tell, its cleared up.
Click to expand...
Click to collapse
It was QPR2 Beta 1 where root could not be obtained by flashing a patched Pixel 6 boot image, so people had to patch a Pixel 7 boot image to obtain root.
We don't know if this is "cleared up" since QPR2 Beta 2 has not been released yet.

Lughnasadh said:
It was QPR2 Beta 1 where root could not be obtained by flashing a patched Pixel 6 boot image, so people had to patch a Pixel 7 boot image to obtain root.
We don't know if this is "cleared up" since QPR2 Beta 2 has not been released yet.
Click to expand...
Click to collapse
Got it, thanks for clearing it up. I wonder if that's similar to the issues with crdroid rom. Root can't be done via recovery at all, it just errors out. When you patch the boot.img from crdroid's rom, at least for me, I had random crashes and bluetooth flat out didn't work. It would say the app for controlling bluetooth was crashing.

Development [RECOVERY][UNOFFICIAL] TWRP 3.7.0_12-0 for OnePlus Nord 2T [karen]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
What's not working?
See https://github.com/oneplus-karen-ro...s_karen-twrp/issues/1#issuecomment-1272629658
- Using fastboot boot <image> doesn't work, due to a very common MediaTek bootloader bug.
- Backing up Data partition may fail due to possible FBE issue.
- Installing OxygenOS stock OTA zip probably fails, because OnePlus didn't add version numbers to their partititons.
Flash guide:
1. Make sure you have the stock boot.img ready that matches your current OxygenOS version.
There's a list of them on this great guide: How to Root Nord 2T with Magisk without TWRP
Add both boot.img and twrp-3.7.0_12-0-UNOFFICIAL-karen.img to your phone storage, using MTP or adb push for example.
2. Flash the TWRP release to the boot partition.
Code:
fastboot flash boot twrp-3.7.0_12-0-UNOFFICIAL-karen.img
fastboot reboot
3. Once you've rebooted to TWRP, install the stock boot.img
- [Install]
- Toggle [Install Image]
- Choose boot.img in the file browser
- Select partition: Boot
- Swipe, DO NOT REBOOT
4. Next we install the ramdisk.
- Press back
- Choose twrp-3.7.0_12-0-UNOFFICIAL-karen.img in the file browser.
- Select partition: Install Recovery Ramdisk
- Swipe (optional, if you want to root the phone, DO NOT REBOOT).
- If you don't want to root, you can reboot now.
Optional, rooting:
5. Save the repackaged boot for Magisk.
Code:
adb shell dd if=/dev/block/by-name/boot of=/sdcard/boot-with-twrp.img
6. Patching the image to root.
- Reboot the device, to normal OS.
- In the Magisk app, choose install and patch our boot-with-twrp.img image.
- Note the ..../Download/magisk_patched-XXXXXXX.img filename in the logs.
7. Install the rooted boot image.
- First switch to TWRP
Code:
adb reboot recovery
- In TWRP, [Install]
- Toggle [Install Image]
- Choose Download/magisk_patched-XXXXXXX.img in the file browser
- Select partition: Boot
- Swipe
- Reboot! You're (finally) done.
Download:
twrp-3.7.0_12-1-UNOFFICIAL-karen.img
twrp-3.7.0_12-0-UNOFFICIAL-karen.img
Source code:
GitHub - oneplus-karen-roms/android_device_oneplus_karen-twrp
Contribute to oneplus-karen-roms/android_device_oneplus_karen-twrp development by creating an account on GitHub.
github.com
Credits:
@SakilMondal for the TWRP denniz (Nord 2) tree this is largely based on.
@PattasuBalu for testing out alpha builds and troubleshooting.
Information:
TWRP version: 3.7.0_12-1-UNOFFICIAL
Created: 2022-10-09
Last Update: 2022-10-15

Reserved :]
Q&A:
Do you need to repeat the install steps after an OTA update?
Short answer: yes you do.
Longer answer
Can't we install Magisk as a zip from TWRP?
Maybe you can? I just don't recommend it.
And neither does Magisk.

Fantastic work. Congrats and a huge thank you

Thanks for the TWRP, now the question is, what happen when we receive OTA updates?
Why seems not possible to directly flash magisk zip (apk renamed) to patch boot img?
I think is better to add this first Q&A in a FAQ list.

cioce said:
Thanks for the TWRP, now the question is, what happen when we receive OTA updates?
Why seems not possible to directly flash magisk zip (apk renamed) to patch boot img?
I think is better to add this first Q&A in a FAQ list.
Click to expand...
Click to collapse
When you recieve an OTA update you have do the entire process again.

garylawwd said:
Fantastic work. Congrats and a huge thank you
Click to expand...
Click to collapse
Thanks for the kind words. :] Was a fair bit of a learning curve but nothing quite as troublesome as now trying to build a full ROM. No luck on that yet.

cioce said:
Thanks for the TWRP, now the question is, what happen when we receive OTA updates?
Why seems not possible to directly flash magisk zip (apk renamed) to patch boot img?
I think is better to add this first Q&A in a FAQ list.
Click to expand...
Click to collapse
(Added the TL;DRs to the second post)
Do you need to repeat the install after an OTA?
Indeed you will need to repeat the process after an OTA.
With an asterisk. Because in theory you could speed this up if you have root access.
The Magisk app has a feature to "Install to Inactive Slot". And the TWRP app could be doing something similar, but I find it needs some work to be more reliable in doing that :]
So if 1. this becomes an OFFICIAL build, and 2. the TWRP app gets some love. It could be done.
Why can you not install Magisk as an APK?
Maybe you can though? I just don't recommend it.
I'm not a Magisk dev so I might miss the finer details why, but they state this method is no longer recommended and deprecated. So it wasn't on my checklist to try or support it.
I suspect though that the patching script will need to make a load of assumptions about how that recovery environment is set up, while the app would be more reliable.

Small update, https://github.com/oneplus-karen-ro...karen-twrp/releases/tag/3.7.0_12-1-UNOFFICIAL
Update the kernel and dtbo.img to use A.15 version.
Rebuild with upstream patch, that should fix the lpdump utility.
Note: you only really need to update if you're interested in using lpdump in TWRP.

Thanks for the update, what about SafetyNet test after TWRP + Root?
Is there any Magisk module that working 100%?

cioce said:
Thanks for the update, what about SafetyNet test after TWRP + Root?
Is there any Magisk module that working 100%?
Click to expand...
Click to collapse
SafteyNet is working fine. Using Universal SafteyNetFix by kdrag0n and added play services to blocklist on Zygisk.

Will the OnePlus Nord 2T be getting any Custom ROM's being built for it in the future?

ArmashOnXDA said:
Will the OnePlus Nord 2T be getting any Custom ROM's being built for it in the future?
Click to expand...
Click to collapse
I hope that yes It's simillar to previous model, we have the kernel etc. Beanow is doing well job with preparing recovery, so it should works We need to find only someone with skills and free time to prepare e.g. LineageOs for us

Beanow Could you tell me if you will continue working on the reocvery?​

hi,
can I use this twrp to install full ROM zip file?
what is the right order to install:
1. full zip ROM
2. twrp.img
3. magisk patched boot.img
is it ok?

nutfile said:
hi,
can I use this twrp to install full ROM zip file?
what is the right order to install:
1. full zip ROM
2. twrp.img
3. magisk patched boot.img
is it ok?
Click to expand...
Click to collapse
It depends if the rom has ramdisk or not but I've seen techkaran's video and he had ramdisk the rom had ramdisk

Did anybody install a ROM in this device yet? Is is possible to install a ROM from the regular Nord 2?

simongaiteiro said:
Did anybody install a ROM in this device yet? Is is possible to install a ROM from the regular Nord 2?
Click to expand...
Click to collapse
There is not yet a rom but u could flash gsi with dsu sideloader

Stephanizgo said:
There is not yet a rom but u could flash gsi with dsu sideloader
Click to expand...
Click to collapse
Never tried to install a GSI before. Did you already tried it on this phone?

simongaiteiro said:
Never tried to install a GSI before. Did you already tried it on this phone?
Click to expand...
Click to collapse
I tried dsu loader on a different phone and it partialy worked but it's ment for the devs
But it's easy u just unlock the bootloader and download dsu sideloader. Then connect to pc and type some command and dsu will sideload sideload your preferred GSI

Now using DSU side loader with magisk patched boot.img working fine