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

[Retrial]

extended. 17.45.36. Root way.

ReVanced Manager 0.42 or 0.43?

 

[rullydotcom]

Succeeded. I don't know whats wrong. I did try to delete folder for prerequisite of root enbironment, I did use revanced manager 42, extended, excluded what should be excluded with root environment and some other exclusion.

Maybe those other exclusion made the difference.

 

[Neo3D]

Amazing guide! Thank you to everyone contributing to keep the Vanced legacy alive!

 

[Retrial]

Old YouTube versions no longer supported.
Info: -> GitHub <-
Recommended version: 17.45.36 (nodpi)

Your old revanced YouTube will continue to work. It's just you can't patch old versions of YouTube.

 

[matadorprobr]

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).

yes, he contributed on the official ReVanced patches repo with 3 commits and you can see on his github commit history: https://github.com/revanced/revanced-patches/commits?author=inotia00

 

[otonieru]

0 problem. Both on rooted phone (Pixel 7 Pro) and non rooted one (Aquos R6)

simply flash magisk module on rooted phone

and simply use the manager on non rooted one,

i think it can't be any more simple than this. You just need to know what to use for your condition

 

[Arealhooman]

Is root or non-root version better/more stable?

 

[Retrial]

Is root or non-root version better/more stable?

The app functions are the same.
Non-root it's less complicated and so I guess more "stable".
If you know what you are doing you won't have a problem with root as well.

 

[Abish4i]

@Retrial can you tell what is the issue here is it device specific or due to patches. Building latest recommend version but results in error. (BTW using it on A7 LITE Samsung Tab)

 

[Retrial]

@Retrial can you tell what is the issue here is it device specific or due to patches. Building latest recommend version but results in error. (BTW using it on A7 LITE Samsung Tab)View attachment 5778017

ReVanced Official or ReVanced Extended?
Which method? Root or non-root?
Which YouTube version you trying to patch? 17.45.36?
Which ReVanced Manager you using? Version 0.42?

 

[Abish4i]

Checked from different version 0.41 and 0.43 still same
Currently trying extended library for save playback functionality
Non-root for 17.45.36 yes
Using nodpi orginal file to patch.

 

[Retrial]

Checked from different version 0.41 and 0.43 still same
Currently trying extended library for save playback functionality
Non-root for 17.45.36 yes
Using nodpi orginal file to patch.

Use ReVanced Manager 0.42.
Make sure you changed these:

• Go to Settings > Sources > and Change both names (patches organization & integration organization) from revanced to inotia00.

I don't know why you can't patch it if you followed the correct steps.

 

[Abish4i]

Yes, I'm using inotia00 patches.

I think either patch has issues or the version is probably corrupt. Haven't found on github with similar issue.

 

[Retrial]

Yes, I'm using inotia00 patches.

I think either patch has issues or the version is probably corrupt. Haven't found on github with similar issue.

I just patched it again perfectly fine.
I don't know why you have that issue. 🫤

 

[wreaver]

I'm getting aborting errors as well. Here's the log in case it helps.

 

[Abish4i]

@Retrial
I'll just stick to revacned patches rather than inotia00 and wait till patches library updates and becomes stable.

 

[Retrial]

I'm getting aborting errors as well. Here's the log in case it helps.

@Retrial
I'll just stick to revacned patches rather than inotia00 and wait till patches library updates and becomes stable.

Sorry guys, I don't know why you have this issue, I can't help you further since I am not the developer. If anyone else is knowledgeable please enlighten us.

Me and many others patched both Official & Extended fine. As I said I tried to patch with Extended again yesterday with the same steps and worked perfectly fine.

I would suggest you to try these steps:

• Download and Install latest Vanced microG.
• Redownload Official YouTube 17.45.36 (nodpi)
• Download and Install ReVanced Manager version 0.42
• Make sure you did the correct changes to manager to fetch from inotia00.
• Make sure Manager have the necessary permissions.
• If still doesn't work: Instead of using the .apk of Official YouTube directly to manager try to install first the official YouTube app and then patch it. But if you already have official YouTube installed to your device that may cause a conflict.

I can share you my already extended builded .apk if you want.

 

[Abish4i]

Sorry ...

Ok, add attachments to your main thread for your build.
I used different device to compile apk it worked but on my device still showing errors.
[I guess it has some sort of arc issue]

YT Extended
Micro-G

 

[asripath]

Ok, add attachments to your main thread for your build.
I used different device to compile apk it worked but on my device still showing errors.
[I guess it has some sort of arc issue]

YT Extended
Micro-G

Uninstall revanced manager and
patched YouTube.

Use revanced manager 0.42 for extended.

Install microg (for non-root)
https://github.com/inotia00/VancedMicroG/releases

Follow below instructions

Home

🗄 Documentation and guides for ReVanced Extended. Contribute to inotia00/revanced-documentation development by creating an account on GitHub.

github.com

Upload logs and patchlist on error

Edit
Don't think OP can add patched YT apk as it
Might conflict with XDA policies

 

[Retrial]

Uninstall revanced manager and
patched YouTube.

Use revanced manager 0.42 for extended.

Install microg (for non-root)
https://github.com/inotia00/VancedMicroG/releases

Follow below instructions

Home

🗄 Documentation and guides for ReVanced Extended. Contribute to inotia00/revanced-documentation development by creating an account on GitHub.

github.com

Upload logs and patchlist on error

Edit
Don't think OP can add patched YT apk as it
Might conflict with XDA policies

These are pretty much the same steps. These are the errors he has.

I may could add my own builds to OP, since Vanced has it's own thread and also has an article for it. But If I am gonna do it, I will talk with Mod just to be sure. Tbh, I don't know if it's needed since everyone can patch and make their own build but if there is a demand for "ready" .apk then I may consider it.