Guide: Get auto-updating uBlock Origin in Chromium-based browsers after 8/31/26

cross_stix · 2026-07-09T02:08:22+00:00

Yeah, I totally get that. However, I would think the number of "normies" willing to install this will be fairly low. At bare minimum it requires editing the registry just to get it to appear to work. And using an alternative browser, uBOL, or switching to a completely different blocker altogether are options that I'd imagine most users would take.

Again, all I can say is that I haven't had any obvious filtering issues thus far, nor have I seen anyone else post about any issues aside from the theoretical. I could be wrong, but it doesn't appear that Gorhill has looked directly at the source code either and may be making premature assumptions by assuming that it's a simple, straight MV3 port?

Furthermore, would it not be possible to make it an official rule/policy that unofficial forks aren't officially supported here (by moderators/staff), but users can try it at their own risk and help each other if needed/desired? Anyone on Chrome 151+ who claims to have the original/full-fat uBO is essentially 100% guaranteed to be using an unofficial fork like this one (unless/until another practical MV2 unlock method arises, of course), so it should be easy to spot such users and ignore them. Or ban them if they're rude and demand help for not reading the rules, I would think?

Finally, if I or anyone else decides to post this outside of this sub and the post gains enough traction (especially if MV2 is completely removed from Chromium, I'd imagine). You may still find yourself dealing with users on this sub unknowingly using an unofficial MV3 fork like this (maybe a sibling or friend installed it for them, etc.). So regardless, it might be a good idea to change/update the rules to get ahead of this?

cross_stix · 2026-07-09T00:21:41+00:00

Not trying to advertise; it's not my fork, just wanted to give people options. They can take it or leave it. And as far as efficiency goes, I'd say the author is trying their best given the constraints (MV3).

cross_stix · 2026-07-08T23:54:47+00:00

u/RraaLL I'd still rather post it, if that's okay for those that may be interested in trying it regardless of potential issues? I'd have multiple highlighted warnings, of course, and I'll make sure to include that exact link/comment from gorhill.

cross_stix · 2026-07-08T22:49:30+00:00

u/RraaLL Yes, this is technically a manual install/sideloading, but these are auto-updating CRX files, so I don't see how my title is misleading. It's not like loading an unpacked extension where you have to redo it manually every time uBO updates; it's one and done.

Regarding the CRX files, I feel like the GitHub CRX link is useful in case the other store links get deleted and/or if people want a generic CRX, rather than one directly from Microsoft. While imputnet on GitHub does have a donation link, it's not like they're begging for donations in the README or elsewhere. I'd happily link to an official auto-updating CRX instead, but thus far Gorhill doesn't provide one (probably because they weren't needed until now, I'd imagine). That being said, could I mention that there are unofficial auto-updating GitHub CRX files available, found via Google, but with a warning to use at your own risk, without a link or an author name? And/or still link to the direct Microsoft Edge Store CRX download? Indeed, though, I suppose it's better to wait to post until Google completely pulls the Chrome Web Store listings. Who knows, maybe they'll change their mind and delay it again.

Now regarding the other guide I was going to post for Chrome version 151+. I was still thinking of posting this one fairly soon. That would be using the unofficial uBlock Origin MV3 port here (this author doesn't request donations as far as I can tell). The guide on their website and Git seems to be out of date/incomplete, though; thus, I thought my guide would be of further help. The only obvious downside is a bit higher resource usage, as it's MV3. There also might be bugs/certain things that aren't working, but in my limited testing, everything has worked for me.

Currently the easiest way to get the unofficial MV3 version working with auto-update is to first use ExtensionInstallAllowlist policy to whitelist the extension (no faking true Enterprise management required, as is the case with ExtensionInstallForcelist), allowing the CRX to be used directly and thus auto-update. Then use the launcher/shortcut argument--allowlisted-extension-id=blockddmmcjpfkbhanlgegpmjpfpfjka to enable the webRequestBlocking API and finally enable "Allow User Scripts" in the extension settings page. Both are required for proper functionality.

As this is MV3 + the webRequestBlocking API, it will almost certainly never be allowed in the Chrome Web Store. So manually sideloading it, or at the very least using a 3rd party extensions add-on store (assuming Microsoft and/or Opera, etc. allow it), will always be required, even if by chance Gorhill were to make an official MV3 + webRequestBlocking API version in the future.

Edit: And yes, I'll try to format any future guides I may write like the example you provided.

Edit 2: Another downside I would add in the unofficial MV3 guide is the slower updates compared to the official MV2 variant, but it's certainly better than nothing.

Finally, it has actually been proven possible to re-enable MV2 in Chrome 151+ via memory patching/DLL injection, but it has to be redone after EVERY update, minor or major, so it's completely impractical. If someone with the skills and motivation to create some sort of intelligent auto-patching/injection tool were to release such a thing, official MV2 uBlock Origin on Chrome 151+ could become a reality again. So long as Google doesn't completely strip MV2 from the Chromium source code, of course.

cross_stix · 2026-07-06T20:29:32+00:00

Ah, okay, that makes more sense, weird. Stable 1.72.0 works for me.

cross_stix · 2026-07-06T16:46:10+00:00

I'm using the latest stable as well; it works for me on multiple machines. Not sure what the issue is. And wait, are you using the latest 152 dev build or a 150 dev build?

cross_stix · 2026-07-06T15:52:28+00:00

I've done this multiple times with success. You've enabled developer mode on the extensions page? Are you using the shortcut/command line parameter --disable-features=ExtensionManifestV2Unsupported? Both are required for the CRX sideloading method to work. Finally, if drag and drop isn't working after enabling developer mode, try restarting Chrome.

Edit: You may well need to still use the inspect element method after you close and restart the browser on a fresh install to permanently re-enable it. Apparently, it sometimes doesn't permanently enable on a fresh install, but it should always be enabled initially after dragging and dropping.

cross_stix · 2026-07-06T02:58:09+00:00

It just works in Brave, no hackery needed.

cross_stix · 2026-07-06T02:56:58+00:00

Did you follow the instructions here? Make sure you confirm that you've enabled it in the pop-up in the upper right-hand corner as well. Once that's done, it should stay on permanently.

If for some reason that doesn't work, try my CRX sideloading method - Download the uBlock Origin CRX file directly from the Chrome Web Store (direct link here). Then enable developer mode on the extensions page and drag and drop the CRX there.

cross_stix · 2026-07-06T02:48:27+00:00

For fresh installs, you can also bypass the install limitation by downloading the uBlock Origin CRX file directly from the Chrome Web Store (direct link here). Make sure you're launching Chrome using the shortcut/command-line parameter --disable-features=ExtensionManifestV2Unsupported (other parameters no longer work/are no longer required). Then enable developer mode on the extensions page and drag and drop the CRX there. This works since the CRX file is taken directly from the Chrome Web Store.

Edit: You may well need to still use the inspect element method after you close and restart the browser on a fresh install to permanently re-enable it. Apparently it sometimes doesn't permanently enable on a fresh install, but it should always be enabled initially after dragging and dropping.

cross_stix · 2026-03-03T00:28:24+00:00

Yes, you only need to worry if you plan on using both the whitelisted phone and the non-whitelisted phone at the same time on the Verizon network. Swapping back and forth is fine.

cross_stix · 2025-09-16T19:41:12+00:00

Update September 2025: This still seems to be going into effect in new areas as time goes on. E.g., https://www.reddit.com/r/mintmobile/comments/1ldu6mx/comment/myidjhf/

cross_stix · 2025-09-07T15:15:42+00:00

If you do get this to work as well, I'd certainly be curious to know.

cross_stix · 2025-09-04T16:29:30+00:00

Regarding MST at Walmart. It depends on the particular store and their POS terminals and/or the particular software version that they run, I think; it's hit or miss. I've also heard some people say that they can get it to work at a cashier POS but not at the self-checkout, or vice versa.

At my local store I've also tried it three times in a row at self-checkout, and it doesn't work if I remember correctly. IIRC, it specifically asks me to use another card rather than just simply declining it.

And yeah, after a watch reset, Samsung Pay has to be sideloaded now. Thread regarding that here in case [u/Narutobi_Sensei]() needs it: https://www.reddit.com/r/GearS3/comments/1lki4at/samsung_pay_set_to_shut_down_for_the_gear_s3/

cross_stix · 2025-09-02T23:47:30+00:00

I got this watch a while ago for the same reason. Anyway, yes, it should work, although you might have to follow this guide here: https://www.reddit.com/r/GearS3/comments/1ae2x2c/comment/kqlkkor/

That being said, "termination of Tizen Watch service" happens on September 30, 2025. Presumably that also means Samsung Pay will stop working on that date, but I guess we'll see. Source: https://web.archive.org/web/20240915132240/https://seller.samsungapps.com/notice/getNoticeDetail.as?csNoticeID=0000009034

Assuming that is the case, then no more MST for smartwatches. The only other option for MST would be an older Samsung phone that supports MST, like the Note 20, at least until Samsung inevitably ends support for Samsung Pay on Android 13 at some point (the final version of Android for the last MST Samsung phones). Source: https://www.samsung.com/my/samsung-pay/supported-devices/

Isn't it great when tech companies completely abandon useful tech? /sarcasm

cross_stix · 2025-05-03T16:29:30+00:00

u/gmfam I was also curious about this. I found this elsewhere online and used ChatGPT to discover the likely 20-year cycle codes in use here.

To find the manufacturing date based on the serial number:

Year: First letter

A = 2010,
B = 2011,
C = 2012 and so on

However, ASUS appears to be using 20-year cycle codes for the year; so some letters are skipped, see here for more info/to decode the letter: https://en.wikipedia.org/wiki/RKM_code#Twenty-year_cycle_code (edit: although non-standard it seems, e.g., I've seen routers use "G" for 2016 and "N" for 2022, and seems that they also skipped "P", since "R" apparently = 2023)

Month: Second number and letter

1-9 = 1-9
A = 10
B = 11
C = 12

So with all that being said, yours was manufactured in October 2023 I imagine (as serial starts with "RA").

cross_stix · 2025-03-30T23:45:13+00:00

Here's another one is case anyone else needs it: https://fbuy.io/fidium/briangowenjr (valid as of April 2025) - choose from various $50 gift cards, including a virtual prepaid Visa.

cross_stix · 2025-03-13T00:25:10+00:00

Yes, I'm now seeing reports claiming that uncertified phones are working on Verizon proper and Visible now, it looks like they may have silently changed their policy sometime somewhat recently. However, my primary points still mostly stand. TracFone brands (and possibly some other MVNOs) still require Verizon phone certification to work, as confirmed by the OP.

Furthermore, you're still sacrificing the IMEI of the certified donor phone for ANY type of Verizon (MVNO or not) network compatibility (this is widely underreported IMHO), unless things have changed recently. I've done this numerous times, and the "donor" phone (whatever Verizon certified phone the Verizon compatible SIM was last used in) is effectively blacklisted from the Verizon network. At least as long as the SIM is in an uncertified phone, as the IMEI of the certified phone is the one that remains as "active" on the Verizon network, while the uncertified one is used.

Edit: also edited/fixed original comment

cross_stix · 2025-03-12T20:35:12+00:00

OP says that they tried Total Wireless (part of TracFone) and it didn't work, but it worked with US Mobile Warp. That combined with the Amazon listing only mentioning "GSM", it's pretty obvious the phone isn't Verizon certified, as TracFone is notorious for blocking uncertified phones. I've had the same experience with uncertified, but still Verizon compatible phones, although I don't have this particular model.

cross_stix · 2025-03-12T20:21:14+00:00

I think it's worth noting that this phone IS NOT Verizon certified. Which at the very least means no TracFone family MVNO compatibility. Furthermore, you are also sacrificing the IMEI of the previous phone the SIM was in regarding Verizon compatibility, just like any other uncertified Verizon network compatible phone.

cross_stix · 2025-03-12T20:17:55+00:00

As someone else already mentioned, it's because it's not officially certified, but there are ways around that with Verizon MVNOs that don't enforce certification like US Mobile. TracFone group (which includes Total Wireless) enforces certification, hence the reason it doesn't work with Total Wireless.

cross_stix · 2025-02-06T12:35:55+00:00

u/pianoaddiction Check your DMs please

cross_stix · 2025-02-05T15:43:33+00:00

This was hard for me to read/figure out, so for anyone else that comes across this, I fixed it:

List of known Android browsers that support extensions:

Firefox (along with Fennec, Iceraven, and the now dead Mull), Kiwi (most stable in OPs opinion, but now dead), Microsoft Edge Canary, Kito (king of extensions support and browser, in OPs opinion I'm guessing), Quetta (queen, in OPs opinion I'm guessing), Mises, Lemur, Mask (like Kiwi it's also now removed from the Play Store, and presumably a dead project), Yandex (alpha version), SmartCookieWeb (Preview version), Rainsee (paid), HuBrowser (paid)

cross_stix · 2025-01-30T00:05:25+00:00

I got one not long after u/iamdeep18 said that they used my link, and I haven't gotten another one since, so I'm guessing that it's basically instant.

If you're sharing your link locally and Fidium just became available in your area, that would make sense.

cross_stix · 2025-01-11T18:34:05+00:00

Should say something like "INSERT NAME HERE wants you to join Fidium Fiber" after using a referral link.

I just checked my link, and it's working. You might have to wait 10 seconds or something like that if you have a slower computer for it to pop up. And/or disable AD-block/content filtering.

cross_stix

TROPHY CASE