Just ran through the following steps:
Uninstalled Vanced+Manager, module, reverted youtube back to stock, removed all Vanced files from data/adb and service.d, reboot → Can't find anymore youtube folder in data/app.
Installed Manager, installed Vanced → Youtube now shows in data/app as:
● com.google.android.youtube-ulPeSkEtPG8zP2SVhqee2w==
This contains split_config.en.apk (screenshot). Vanced can be opened.
Installed module and reboot → Folder in data/app still the same, Vanced no longer starts and shows weird name in Android App settings (screenshot):
● com.google.android.apps.youtube.app.YouTubeApplication
Checked adb/service.d and there is no vanced.sh script. Reinstalled Vanced from Manager + Disable/Enable app from app settings. Now vanced.sh script appears, it shows normal YouTube name in Settings and Vanced can be opened.
Reboot again to see what happens → exactly same as previous, Vanced can only be opened after I Reinstall from Manager + Disable/Enable app from Settings (must do both or else nothing changes).
I hope that's comprehensive enough for someone to figure out what is wrong.
Sent from my OnePlus6T using XDA Labs
Your screen-shots did not upload. (Temporary xda issue due to back-end switch.)
What ROM are you running?
What happens if you clear everything and start clean?
Then install Vanced (root) from Vanced Manager and reboot.
Are all the file in/data/app/com.google.android.youtube-StringShit/ or just base.apk ?
Check for a vanced.sh file in /data/adb/service.d and /data/ad/post-fs/data.d and /data/adb/vanced/base.apk file.
If the Vanced version is not active, and all the files in /data/app/com.google.android.youtube-StringShit and /data/adb/vanced/base.apk exists.
What happens if you run the mount command manually, root command line (adb shell or terminal app)?
[ Replace com.google.android.youtube-StringShit with your path to YouTube. ]
Code:
su -c mount -o bind /data/adb/vanced/base.apk /data/app/com.google.android.youtube-StringShit/base.apk
[ You may have to force stop and/or clear cache (maybe data) for YouTube after mounting Vanced over the regular version. ]
--
I have a 6T T-Mobile convert.
Been on LineageOS 17.1 for a little while testing custom rom crap.
Reverted back to OOS (Global) stock tonight to check.
[ OnePlus6TOxygen_34.J.48_OTA_048_all_2010042240_dbd576b615 ]
The current Vanced root worked for me on LineageOS 17.1 and OOS 10.3.6
No need to adjust or replace the mount script. ¯\_(ツ)_/¯
Is it possible you have something installed/running that may affect the mount scripts?
Cheers.
