▶️ReVanced & ReVanced Extended - Guides & Useful Links📚

[R0298]

@R0298 Seems it's related with this. But as you said if u don't have ReVanced Manager or any YT ReVanced app installed, then idk.

until a few days I had revanced manager, but without ever using it. Can this be it?

 

[ipdev]

<SNIP>
I read somewhere in Reddit that inotia00 is also a contributor to the Official ReVanced team, so he can help make it better (I can't confirm tho, if anyone knows more please enlighten us).
<SNIP>

ReVanced GitHub Contributors.
author=inotia00

Commits · revanced/revanced-integrations

🔩 Integrations containing compileable classes referenced by ReVanced Patches - originally maintained by Vanced - Commits · revanced/revanced-integrations

github.com

Commits · revanced/revanced-patches

🧩 Patches for ReVanced. Contribute to revanced/revanced-patches development by creating an account on GitHub.

github.com

Cheers.

 

[Retrial]

I am a little confused.
Are you just installing the modified apk?

Yes what else should I do? I just wanted to check if the installation process working because R0298 said it gives him conflict.

[[email protected] Root]$ adb install youtube-revanced_extended_root_v17.49.37.apk
Performing Streamed Install
adb: failed to install youtube-revanced_extended_root_v17.49.37.apk: Failure [INSTALL_FAILED_UPDATE_INCOMPATIBLE: Package com.google.android.youtube signatures do not match previously installed version; ignoring!]

So I disabled the system version of YouTube..
mModule_rsyt - [GitHub] - Link
Rebooted and tried again.

[[email protected] Root]$ adb install youtube-revanced_extended_root_v17.49.37.apk
Performing Streamed Install
Success

I asked if he has any YouTube app installed even official and he told me not. If there is no YouTube app there why the root version find "an update" and gives him error?

until a few days I had revanced manager, but without ever using it. Can this be it?

I don't think so, If you uninstalled it.

 

[Retrial]

ReVanced GitHub Contributors.
author=inotia00

Commits · revanced/revanced-integrations

🔩 Integrations containing compileable classes referenced by ReVanced Patches - originally maintained by Vanced - Commits · revanced/revanced-integrations

github.com

Commits · revanced/revanced-patches

🧩 Patches for ReVanced. Contribute to revanced/revanced-patches development by creating an account on GitHub.

github.com

Cheers.

Thx for the confirm Now that we are sure, I will edit the OP tomorrow

 

[Retrial]

I'm trying to install but I can't. Here is the error message

Translate: App not installed because the package conflicts with an existing package.

I am a little confused.
Are you just installing the modified apk?

[[email protected] Root]$ adb install youtube-revanced_extended_root_v17.49.37.apk
Performing Streamed Install
adb: failed to install youtube-revanced_extended_root_v17.49.37.apk: Failure [INSTALL_FAILED_UPDATE_INCOMPATIBLE: Package com.google.android.youtube signatures do not match previously installed version; ignoring!]

So I disabled the system version of YouTube..
mModule_rsyt - [GitHub] - Link
Rebooted and tried again.

[[email protected] Root]$ adb install youtube-revanced_extended_root_v17.49.37.apk
Performing Streamed Install
Success

ReVanced just keeps closing.
It will open, see a glimpse of the home screen and then close.
Not fully close, only go into background apps.

Cleared YouTube cache and data.
Rebooted (bit surprised it passed verification on boot) still the same story.

Not sure if it helps.

Cheers.

Note:
Pixel 5a, Stock Android 12 Dec.2021
Apparently I have not used/updated this one in a while.
Magisk Debug (personal build), updated just before I tried the ReVanced Extended apk.

Ok guys,
So I figured out what's going on, on my rooted device.

1. @R0298 The error you get with conflict package name is because I am sure you have youtube official app installed. Check your apps and you will find it. It detects the same package name with the an app you have already installed so I am sure you have the youtube app installed.
2. So even if you could install it as I did in all of my devices (root and non root), you couldn't open it since it needs to be installed "as Root" via ReVanced Manager which you would already gave root permissions.
3. So I've deleted completely the Root folder with .apk(s) from my .zips and now my zips contain only non root apk(s) since it's not possible to install like that for root.
4. I've slightly updated the Root guides.
5. I've updated my Download post.
6. To sum up, if you want to use ReVanced or ReVanced Extended via Root without microG, you either build yourself with my Root guides at OP and press "Install as Root" option in Manager or use the j-hc/ ReVanced Magisk Module by scrubjay55.

Cheers.

 

[zgfg]

• Remove all YouTube related modules, if you have any.
• Remove directories: /data/adb/service.d, /data/adb/post-fs-data.d, /data/adb/revanced.

This better needs to be corrected pls (post #1, Installation guide for root users, spoiler)

One should never blindly delete the whole post-fs-data.d and service.d folders (regular Magisk folders!), but to open them and to delete only those files whose names resemble Vanced, ReVanced, YouTube, YT or similar

Actually, the sh files (those folders contain) are scripts, they can be opened as text files and then found from their content (like fron the comments in the scripts) if they really correspond to the (Re)Vanced, and only then to be deleted

For example - see my screenshot, my service.d folder contains the scripts aml.sh and jdsp.sh that have nothing with (Re)Vanced but that are essential scripts for the AML and JamesDSP audio mods

By deleting the whole service.d folder with those two scripts, AML and JamesDSP will appear as still 'installed' but they will no more work (fully and correctly)

 

[Retrial]

This better needs to be corrected pls (post #1, Installation guide for root users, spoiler)

One should never blindly delete the whole post-fs-data.d and service.d folders (regular Magisk folders!), but to open them and to delete only those files whose names resemble Vanced, ReVanced, YouTube, YT or similar

Actually, the sh files (those folders contain) are scripts, they can be opened as text files and then found from their content (like fron the comments in the scripts) if they really correspond to the (Re)Vanced, and only then to be deleted

For example - see my screenshot, my service.d folder contains the scripts aml.sh and jdsp.sh that have nothing with (Re)Vanced but that are essential scripts for the AML and JamesDSP audio mods

By deleting the whole service.d folder with those two scripts, AML and JamesDSP will appear as still 'installed' but they will no more work (fully and correctly)

I don't even know if this step is necessary. I had the same though but I saw this at the documentation of extended.
I will edit it tommorow.

 

[ipdev]

I am a little confused.
Are you just installing the modified apk?

Yes what else should I do? I just wanted to check if the installation process working because R0298 said it gives him conflict.

Ok guys,
So I figured out what's going on, on my rooted device.

1. @R0298 The error you get with conflict package name is because I am sure you have youtube official app installed. Check your apps and you will find it. It detects the same package name with the an app you have already installed so I am sure you have the youtube app installed.
2. So even if you could install it as I did in all of my devices (root and non root), you couldn't open it since it needs to be installed "as Root" via ReVanced Manager which you would already gave root permissions.
3. So I've deleted completely the Root folder with .apk(s) from my .zips and now my zips contain only non root apk(s) since it's not possible to install like that for root.
4. I've slightly updated the Root guides.
5. I've updated my Download post.
6. To sum up, if you want to use ReVanced or ReVanced Extended via Root without microG, you either build yourself with my Root guides at OP and press "Install as Root" option in Manager or use the j-hc/ ReVanced Magisk Module by scrubjay55.

Cheers.

That is why I was surprised it worked by just installing the modified apk like normal.

A few years ago, it started becoming an issue to the Vanced version.
If it passed boot verification, it might work and it might not.

That was why Team Vanced ended up adapting the mount overlay idea to use as their root inastall method.

When You use the ReVanced Manager app to patch and install as root..
It will copy the modified version to /data/local/tmp/"AppPackageName".
Then a boot script(s) is created into post-fs-data/d and service.d to run the mount on boot.
The overlay is run so you can use the modified version right away, the boot scripts will take care of mounting on boot.

Cheers.

 

[ipdev]

This better needs to be corrected pls (post #1, Installation guide for root users, spoiler)

One should never blindly delete the whole post-fs-data.d and service.d folders (regular Magisk folders!), but to open them and to delete only those files whose names resemble Vanced, ReVanced, YouTube, YT or similar

Actually, the sh files (those folders contain) are scripts, they can be opened as text files and then found from their content (like fron the comments in the scripts) if they really correspond to the (Re)Vanced, and only then to be deleted

For example - see my screenshot, my service.d folder contains the scripts aml.sh and jdsp.sh that have nothing with (Re)Vanced but that are essential scripts for the AML and JamesDSP audio mods

By deleting the whole service.d folder with those two scripts, AML and JamesDSP will appear as still 'installed' but they will no more work (fully and correctly)

I don't even know if this step is necessary. I had the same though but I saw this at the documentation of extended.
I will edit it tommorow.

Long story short..
I use a post-fs script to remove competing script(s) and file(s) in my module.
YouTube - iYT - [ GitHub ] - Post-fs-data
YouTube Music - iYTm - [ GitHub ] - Post-fs-data
Those are the scripts and files (directories) you want to remove to stop competing installs from running along with your own.

I suppose to make you list more complete, add my current modules also.

iYT Module (YouTube)

[[ -d $MMDIR/iyt ]] && rm -rf $MMDIR/iyt;
[[ -d $ADB/iyt ]] && rm -rf $ADB/iyt;

iYTM Module (YouTube Music)

[[ -d $MMDIR/iytm ]] && rm -rf $MMDIR/iytm;
[[ -d $ADB/iytm ]] && rm -rf $ADB/iytm;

$MDIR = Current module directory (The module directory the script is called from).
$MMDIR = /data/adb/modules/
$ADB = /data/adb/

Cheers.

 

[zgfg]

Long story short..
I use a post-fs script to remove competing script(s) and file(s) in my module.
YouTube - iYT - [ GitHub ] - Post-fs-data
YouTube Music - iYTm - [ GitHub ] - Post-fs-data
Those are the scripts and files (directories) you want to remove to stop competing installs from running along with your own.

I suppose to make you list more complete, add my current modules also.

iYT Module (YouTube)

[[ -d $MMDIR/iyt ]] && rm -rf $MMDIR/iyt;
[[ -d $ADB/iyt ]] && rm -rf $ADB/iyt;

iYTM Module (YouTube Music)

[[ -d $MMDIR/iytm ]] && rm -rf $MMDIR/iytm;
[[ -d $ADB/iytm ]] && rm -rf $ADB/iytm;

$MDIR = Current module directory (The module directory the script is called from).
$MMDIR = /data/adb/modules/
$ADB = /data/adb/

Cheers.

It was also Vanced Manager that left it scripts, I'm not sure but I think they were called vanced.sh or similar in /adb/data in post-fs-data.d and service.d (and unfortunately Vanced Manager did not care to remove them when you clicked on to uninstall the root Vanced YT)

I'm not using ReVanced Manager, hence I don't know how its scripts are called (and does it remove them properly when you click on Uninstall the ReVanced YT, but scripts will be left if user does not click but only uninstalls the manager app)

Also, j-hc/Re-Vanced.io module's folder is /data/adb/modules/ytrv-magisk

I don't even know if this step is necessary. I had the same though but I saw this at the documentation of extended.
I will edit it tommorow.

Long story short

Yes it is better to search for those scripts and to (manually) remove them if they were left there when switching from one root 'solution' (like from Vanced to ReVanced, from manager to module, etc) to another

They either try to mount to the 'hard-coded' paths in /data/app/<YT app folder> thus preventing you to properly remove the folder with your previous old YT installation or (if smarter) they search for
/data/app/<YT app folder> and in that case they may try to even mount their old patched app to your new version of YT app, thus messing up with your new 'solution'

PS: That's why I'm always in favor of the modules implementation like j-hc/ReVanced (or there were also module versions for the root Vanced YT) instead of the Managers. Modules can be easily removed with all their leftovers by clicking to Uninstall that module in Magisk app, module tab

On the other side, when you eg just uninstall the (Re)Vanced Manager app, nothing would clean its leftovers from its root installation in /data/adb post-fs-data.d and/or service.d folders - and if not familiar with the scripts given to Magisk for the mounting, user will never know where are those leftover scripts (that prevent him to properly install/use new 'solution')

Btw, 'suggested' ways for such mods are to use Magisk modules mechanism, not to install your scripts directly to the Magisk post-fs-data.d or service.d folders (like managers do) - and exactly for thar hygienics reasons

 

[ipdev]

It was also Vanced Manager that left it scripts, I'm not sure but I think they were called vanced.sh or similar in /adb/data in post-fs-data.d and service.d (and unfortunately Vanced Manager did not care to remove them when you clicked on to uninstall the root Vanced YT)

I'm not using ReVanced Manager, hence I don't know how its scripts are called (and does it remove them properly when you click on Uninstall the ReVanced YT, but scripts will be left if user does not click but only uninstalls the manager app)
<SNIP>

Vanced used /data/adb.
Vanced was YouTube.
Music was YouTube Music.

post-fs-data.d/vanced.sh
service.d/vanced.sh
data/adb/Vanced

post-fs-data.d/music.sh
service.d/music.sh
data/adb//Music​

ReVanced uses /data/adb and /data/local/tmp.

post-fs-data.d/com.google.android.youtube.sh
service.d/com.google.android.youtube.sh
/data/local/tmp/revanced-manager/com.google.android.youtube

post-fs-data.d/com.google.android.apps.youtube.music.sh
service.d/com.google.android.apps.youtube.music.sh
/data/local/tmp/revanced-manager/com.google.android.apps.youtube.music​

<SNIP>
Also, j-hc/Re-Vanced.io module's folder is /data/adb/modules/ytrv-magisk
<SNIP>

Thank you for confirming.
Hence why I added it to my removal script.

# Check and remove ReVanced YouTube module.
[[ -f $ADB/com.google.android.youtube_rv.apk ]] && rm $ADB/com.google.android.youtube_rv.apk;
[[ -d $MMDIR/ytrv-magisk ]] && rm -rf $MMDIR/ytrv-magisk;

Cheers.

 

[Retrial]

It was also Vanced Manager that left it scripts, I'm not sure but I think they were called vanced.sh or similar in /adb/data in post-fs-data.d and service.d (and unfortunately Vanced Manager did not care to remove them when you clicked on to uninstall the root Vanced YT)

I'm not using ReVanced Manager, hence I don't know how its scripts are called (and does it remove them properly when you click on Uninstall the ReVanced YT, but scripts will be left if user does not click but only uninstalls the manager app)

Also, j-hc/Re-Vanced.io module's folder is /data/adb/modules/ytrv-magisk


Long story short

Yes it is better to search for those scripts and to (manually) remove them if they were left there when switching from one root 'solution' (like from Vanced to ReVanced, from manager to module, etc) to another

They either try to mount to the 'hard-coded' paths in /data/app/<YT app folder> thus preventing you to properly remove the folder with your previous old YT installation or (if smarter) they search for
/data/app/<YT app folder> and in that case they may try to even mount their old patched app to your new version of YT app, thus messing up with your new 'solution'

PS: That's why I'm always in favor of the modules implementation like j-hc/ReVanced (or there were also module versions for the root Vanced YT) instead of the Managers. Modules can be easily removed with all their leftovers by clicking to Uninstall that module in Magisk app, module tab

On the other side, when you eg just uninstall the (Re)Vanced Manager app, nothing would clean its leftovers from its root installation in /data/adb post-fs-data.d and/or service.d folders - and if not familiar with the scripts given to Magisk for the mounting, user will never know where are those leftover scripts (that prevent him to properly install/use new 'solution')

Btw, 'suggested' ways for such mods are to use Magisk modules mechanism, not to install your scripts directly to the Magisk post-fs-data.d or service.d folders (like managers do) - and exactly for thar hygienics reasons

Vanced used /data/adb.
Vanced was YouTube.
Music was YouTube Music.

post-fs-data.d/vanced.sh​

service.d/vanced.sh​

data/adb/Vanced​

​

post-fs-data.d/music.sh​

service.d/music.sh​

data/adb//Music​

ReVanced uses /data/adb and /data/local/tmp.

post-fs-data.d/com.google.android.youtube.sh​

service.d/com.google.android.youtube.sh​

/data/local/tmp/revanced-manager/com.google.android.youtube​

​

post-fs-data.d/com.google.android.apps.youtube.music.sh​

service.d/com.google.android.apps.youtube.music.sh​

/data/local/tmp/revanced-manager/com.google.android.apps.youtube.music​

Thank you for confirming.
Hence why I added it to my removal script.

# Check and remove ReVanced YouTube module.
[[ -f $ADB/com.google.android.youtube_rv.apk ]] && rm $ADB/com.google.android.youtube_rv.apk;
[[ -d $MMDIR/ytrv-magisk ]] && rm -rf $MMDIR/ytrv-magisk;

Cheers.

I've made some edits in OP at Root guide. Let me know if it's better.

 

[zgfg]

I've made some edits in OP at Root guide. Let me know if it's better.

Ok, super. You refer to the above post(s), hence one could hopefully understand

It's all pretty much complicated, hopefully not many would have real problems with all that (the guy in the other thread has some issues with Android emulator and the system installed YT app - that's not this thing)

 

[Retrial]

It's all pretty much complicated, hopefully not many would have real problems with all that

I tried to make the building guides with steps as simple as I can but with the details and informations so each user to understand what he is doing.

The sections I've made along with the proper links redirections, I believe they can be prevent the overwhelming feeling so each user to search specifically what he wants.

ReVanced it's still something new for a lot of people, need some time to understand and adapt, like I did. I learned a lot since the time I've made the thread and tried to include these informations.

There are couple ways each user prefers to follow to install ReVanced, I tried to cover everything. If they follow the steps I don't think they will have a problem but If they do, they can post here to help them.

 

[xdauser003]

Nice finally got it working with the magisk module, couldnt get it working the other ways

missed this since they killed vanced

 

[Retrial]

Nice finally got it working with the magisk module, couldnt get it working the other ways

missed this since they killed vanced

I could help you build yourself if you tell me what steps u did and didn't worked. (Non root or root - in what step you had problem)
But if you are rooted -anyway- (and didn't rooted just for ReVanced) then the magisk module u flashed it's the easiest and convenient method.

 

[@KraxZher]

thanks i install the already built version of revanced seems to work pretty well on android 13

 

[Retrial]

New Update: 05/01/2023
Changelog:

• Updated slightly the Root Guides.
• Updated the guides, links and compatibility of YouTube version 18.01.32 for ReVanced Extended.
• Added ReVanced Extended based on YT 18.01.32.
• Updated my "ready" .apks in Download post.
• Updated Vanced MicroG to v0.2.26.224915.
• Added Vanced MicroG Release Date and Changelog in Download post.
• Updated the root installation and few other things in Download post.
• Removed from my "ready" .apks the "Root" folder. Read here why.
• Added Revanced Extended Telegram Group link for chat.
• Added Crowdin link for the ReVanced Extended Music.
• Added two new sections for "Desktop" and "Spotify" recommendations to achieve similar result as you do with ReVanced.
• Added at Notes my other useful threads.

 

[Anndra]

Download Official ReVanced & ReVanced Extended
I've created these .apk(s) using the guides at OP, for Non Root users or for Root users who still want to use it along with microG, which you can find attached below, so I can help you can get them ready out-of-the-box, without the need to build it.
[Read this]​

Patches used

Spoiler: 🩹Patches used for Official ReVanced

• All Recommended, except Custom Branding (because it has ugly icon), Premium Heading, Debugging.

Spoiler: 🩹Patches used for ReVanced Extended

• All Recommended, except Translation (since some languages may not be 100% completed and it will show half English half native language and that seems ugly. I will include that patch when most languages will be translated).

Build Date (DD-MM-YYY)

Date Format: DD-MM-YYYY

• Official Revanced: 05/01/2023 - YouTube version 17.49.37 - Changelog
• ReVanced Extended: 05/01/2023 - YoutTube version 18.01.32 - Changelog
• Vanced MicroG: 05/01/2023 - v0.2.26.224915 - Changelog

Installation

Spoiler: Non Root

• Install microG and then the Official ReVanced or ReVanced Extended.
• While you installing the app and when you first open the app, you will get a warn from play store. Press ignore and then press -do not send-. It's safe don't worry about what play store says.
• To set the app as default: Go to App info > Set as default > Open supported links, "On" > Supported web addresses > Turn them all "On"
• Enjoy!

Spoiler: Root

• To Install via Root without microG, you need to manually build according my Root guides at OP. (You can still install my .apks here as Root user but along with the microG) [Read here]
• Or you can simply install the j-hc/ ReVanced Magisk Module.

Notes

• Each .zip contains the ReVanced or ReVanced Extended.apk along with the latest Vanced MicroG.apk.
• I've linked this post at OP.

please use the original theme!

 

[Retrial]

please use the original theme!

Explain what you mean and in which one? Official ReVanced or Extended?