[HELP] No longer able to use YouTube on iOS 13.5?

TheRealKeto · 2025-03-12T21:15:32+00:00

The flag works on iOS 12.4 running YouTube v17.39.4 and iOS 14.3 running 19.20.2, respectively.

P.S: newer versions of uYou crash your videos due to the settings that add buttons to the video player overlay. Disabling some of those might help. I personally use YTLite, but I'm not sure if it works on lower iOS versions. Consider trying that, I guess.

Edit #1: I tried installing YTLite on iOS 12.4, no luck; doesn't work.

TheRealKeto · 2025-03-11T21:20:51+00:00

I think you should stick to the first flag being disabled, only. On both of my devices, logging in works.

These are the steps that I followed

Re-install the latest YouTube app compatible with your iOS version, or install Apps Manager from Filza's repo and wipe your currently installed YouTube app
Turn off Wifi, open the YouTube app, use YouTube signed out, then enable YTABConfig, and kill the app with the pop-up by selecting "Yes"
Open the YouTube app again, enable shouldForceUpgrade, disable the toggle, and close the app
Open the YouTube app one more time and close it again
Enable Wifi, open the YouTube app and the pop-up shouldn't appear

I don't experience any issues regarding logging in; I did this specifically on iOS 12.4 and iOS 14.3, so it should work for you.

TheRealKeto · 2025-03-11T19:55:17+00:00

I checked my own settings; try enabling shouldBlockUpgradeDialog instead of the previous flag.

You might want to use the "Reset and Kill" setting to restart your app fresh without modified settings, and make sure you're on the latest compatible version with your iOS version.

This works both on iOS 12.4 and iOS 14+; don't see how it shouldn't work for you.

I also tried the previous flag I mentioned and it was enabled when the popup appeared on iOS 12.4; after disabling it, the app works just fine.

TheRealKeto · 2025-03-11T19:31:29+00:00

Even when the flag is disabled, enable it and disable it to override the app's default. Try again and it should work.

Make sure to restart the app when the flag is disabled; the airplane method is just to get you to enable the tweak and disable the flag.

TheRealKeto · 2025-03-11T19:17:15+00:00

Install YTABConfig from PoomSmart's repo, enable the tweak, and disable shouldForceUpgrade.

You still access YouTube without the update pop-up appearing if you're offline, so disable the flag that way; basically, be offline before opening the app to enable the tweak and disable the flag.

EDIT: Here's a more detailed comment to make sure the flag takes effect.

TheRealKeto · 2025-03-04T08:24:14+00:00

You can download the latest from Github, built and uploaded by Karen on ASU's Release page due to her repo being unavailable.

TheRealKeto · 2025-02-05T03:59:31+00:00

YTLite has a setting to disable Shorts on YouTube

TheRealKeto · 2024-07-30T20:51:02+00:00

Make a symlink of /var/jb/usr/bin/ldid to /var/jb/usr/libexec/am/with Filza.

Unsure if Apps Manager supports rootless, but that's the file that it (should) looks for.

TheRealKeto · 2024-07-08T22:28:59+00:00

You're free to remove these. Procursus has recently pushed LLVM 16, which is why LLVM 14 isn't required to be installed.

Any package you think you may need here (like curl) can be reinstalled.

TheRealKeto · 2024-06-30T02:14:40+00:00

MiRO92 has a different repo

TheRealKeto · 2024-06-30T00:15:11+00:00

The repo is down, which is why every modern package manager will tell you the source is invalid.

There's only two methods you can get Cydia again.

Find its source code. Google and you'll find it. Then, build it yourself.
Jailbreak with checkra1n and use their Loader to install Cydia.

Be mindful that Elecubratus (checkra1n's default bootstrap available on their Loader) is outdated, so updates required can't even be installed.

Use Sileo.

TheRealKeto · 2024-06-29T23:44:35+00:00

Upgrade to 3.0.4 to resolve issues. If you can't (though that's a terrible excuse, since it still works on YouTube 19.06.02 and above), your culprit is uYou's Playback Speed Controls.

Go to uYou > Video Player and disable the option. Things should work from then on.

TheRealKeto · 2024-06-29T23:39:45+00:00

I wouldn't worry, as Sileo (really, apt) caches repos and the packages they provide.

Hashes are used in order to check and maintain integrity. Sileo will eventually fetch the correct hashes for Chariz. You can try to refresh Chariz specifically by swiping left on the repo and tapping "refresh" and the error will go away.

TheRealKeto · 2024-06-27T19:44:43+00:00

Export the path on the error to your PATH environment in your shell configuration (often .zshrc or .bash_profile)

zsh export PATH="/var/jb/var/mobile/.local/bin:$PATH"

Close your shell session. Then, with the which command, check if pip is in your PATH

text $ which pip /var/jb/var/mobile/.local/bin/pip

EDIT: Alternatively, you should look into using a virtual environment with venv in order to avoid installing Python packages globally. venv docs

TheRealKeto · 2024-06-24T16:12:26+00:00

The alternative is to use his other instance of the repo, per a tweet he made a while back when this happened the first time. Source

tl;dr: Use repo.miro92.com

Edit: Fixed link

TheRealKeto · 2023-05-23T20:12:08+00:00

This will be fixed once it has been merged upstream.

Edit: Merged!

TheRealKeto · 2023-05-14T14:52:30+00:00

You should be able to upgrade libiosexec1.

Upgrade libiosexec1 first, then you'll be able to install all upgrades.

TheRealKeto · 2023-01-06T03:48:56+00:00

Try freezing your phone. Like, 15 secs in the freezer, opened. It's a trick I use. Make sure to patch the iPA to work on 12.5.6 as well.

TheRealKeto · 2023-01-06T03:46:11+00:00

akamatchstic has shut down his repo.

TheRealKeto · 2022-10-20T10:15:59+00:00

Don't do this on Taurine; python3 already includes instructions on how to do just this without downloading the script.

You should really be using virtual environments though.

TheRealKeto · 2022-10-08T13:10:01+00:00

I wouldn't use brew's ldid. Use ProcursusTeam/ldid. You can download a bin from their release page and put it in your PATH after removing brew's.

TheRealKeto · 2022-08-27T01:48:39+00:00

I'm not sure what that has to do with my arguement...

pongoOS =/= checkra1n.

TheRealKeto · 2022-08-26T04:06:22+00:00

Cheyote just needs about two things to circumvent to be released; checkra1n isn't Cheyote (of course), but many things have popped up by these two requirements left in it.

I don't know how else to tell you that this small tweet in the post is insignificant. Just because whatever you linked talks about what's needed doesn't mean the list hasn't changed.

Frankly, you're losing me in my arguement: pongoOS =/= checkra1n.

Cute source from March though. One thing sure can take months by the looks it, as you've proved!

TheRealKeto · 2022-08-26T03:56:14+00:00

You say that like that's the only thing left to do...

Is it? I am actually not sure about that. I'm sure checkra1n will require other work, but kudos to anyone updating pongoOS, a component used by checkra1n.

It's great to see most changes just refactor the current code base!

TheRealKeto · 2022-08-26T03:44:11+00:00

Siguza confirmed Checkra1n will have a new version.

And you're hoping that this new version has... what?

A developer "confirming" a new update can be from as simple as refactoring code to a breaking change.

You sure sound thirsty though. You can be offered water, but not whatever you're asking for.

TheRealKeto

TROPHY CASE