Unlocking Box Box’s Pro widgets by changing one value on the phone
Box Box is a Formula 1 companion app with a set of home-screen widgets, some of which need a Pro subscription. It is closed source, so to see how the Pro check works I pulled the APK off my phone and decompiled it. The whole gate turned out to be a single value stored on the device. Change it and every Pro widget unlocks.
Start from what the app does
The app was built with R8, so almost every class and method is renamed to short, meaningless names like ec0 and mr1. JADX listed more than 17,000 classes. Searching for words like premium or subscription mostly fails, because those names were renamed away during the build.
So I started from something the app visibly does: tap a Pro widget and, instead of adding it, it opens the subscribe screen. That behaviour is triggered by code, and finding that code puts you right next to the decision. Working back from what an app clearly does beats guessing what a variable might be called.
Finding the decision
Every Android app ships a manifest listing its screens and background receivers. It gave me two threads to pull: the widget receiver, and ProPlanActivity, which is the subscription screen.
My first guess was wrong. I followed the widget receiver, expecting the check to live near the widget code. It did not. That path just loaded race data and drew the widget. The useful part of the failure: the permission decision happens when you add a widget, not while it runs.
So I traced both ends at once. From the widget side, one small function handles all thirteen widgets and asks Android to pin them, with no subscription check in it. From the other side, I followed who opens the subscription screen. Both trails met at the same click handler, the code that runs when you tap a widget. It compares two values, your plan and the plan the widget requires:
- If you are already Pro, the widget gets added.
- If you are Free and the widget is Free, it gets added.
- If you are Free and the widget is Pro, you get the subscription screen instead.

Where the value comes from
I could have forced that one comparison to always say yes, but I wanted the source of your plan, not a single screen. The readable strings usually survive renaming, because the app still needs its real string keys at runtime. So I chased strings instead of names, and they led to a small storage class holding these:
"plans_data_store" a small database on the phone
"plan_type" the key that holds your plan, as a number
"revenuecat_synced_v1" a hint that the billing service writes here
So the app keeps your plan in a tiny local store, as a single number. Nearby was the enum it maps to: Free is 0, Pro is 1, and nothing saved defaults to Free. Everything upstream decides which of the two you are, and everything downstream reacts to it. The reader does something this simple:
int saved = plansDataStore["plan_type"]; // 0 or 1
Plan plan = Plan.values().get(saved); // 0 -> Free, 1 -> Pro
emit(plan); // hand it to the rest of the app
That last line matters. It does not just return your plan, it pushes it into a stream the rest of the app listens to. Change what it hands out and the whole app changes its mind about who you are.
One loose end: revenuecat_synced_v1 implies the billing service (RevenueCat) is what normally writes that number after checking your real subscription. I did not fully trace that writer, so I know how the app reads your plan and only have hints about how it gets written.
The one change
I changed the reader, not the saved number and not the paywall comparison. The saved number can be overwritten the moment the billing service syncs, and the paywall comparison is only one of many places that trust your plan. The reader is the one spot everything listens to. It normally does this:
Plan.values().get(saved) // saved is the stored number, 0 or 1I made it always read the Pro slot:
Plan.values().get(1) // always ProIn the app's low-level instructions this was a single added instruction, const/4 v4, 0x1, dropped in before the lookup so it ignores the saved number and returns Pro every time. I did not touch the paywall check, the stored value, or RevenueCat. Then the usual rebuild, sign, install, and test while logged out so nothing could sync a real plan over the top.
What happened
I opened the widget picker, went for a widget I knew was Pro-only, and got the normal Add widget dialog instead of the subscription screen. Every other Pro widget I tried worked too, and since the app is essentially all widgets, that covered everything paid.

The real app: this widget wants a subscription

The patched build: the Pro widget just gets added
The only things that broke were login, sign-up, and updating the app. That is expected. Rebuilding means re-signing with my own key, and those flows check the app's signature and reject a build that is not the official one. The widgets, which are the whole point, all worked.
What I'd change if it were mine
The renaming slowed me down but never stopped me, because it hides where a decision is, not the fact that the decision is made on a device I control. The real issue is what the app trusts. If it were mine:
- Do not decide “are you Pro?” from a number saved on the phone. That number is only a copy of what the billing service last reported, and anyone can edit what is on their own phone. When someone uses a Pro feature, ask the real source right then, the billing service or your own server, instead of trusting the copy.
- Make the server check entitlement for anything it sends back. Several widgets pull live data from Box Box's servers. If the server checks the subscription before handing that data over, a patched app that only thinks it is Pro still gets nothing. That is what Google's Play Billing guidance recommends: keep the lock somewhere the user cannot reach.
- You already check the signature somewhere, which is why login broke on my rebuilt app. Extending that check to the add-widget path would reject a re-signed build there too. It raises the bar, though a determined person can strip client-side checks, which is why the server check above is the real fix.
I did not look at Box Box's servers, so these are suggestions about design, not claims about how their backend works today. I have sent the full reproduction steps and this fix to the Box Box team.