CheatDroid 4.2 is out
4.1 came out of writing the game guides. 4.2 is about getting CheatDroid onto the phone in the first place, and about the no-root path saying what it can and can’t do before you lean on it. 4.2.1 and 4.2.2 came out on 31 October, from another round of game guides: the hex editor got rebuilt, capture started working on Unity games, and this page has all of it.
Temporary root
CheatDroid changes another app’s files, and that has always meant your phone was already rooted. 4.2 adds a way in for a phone that isn’t. A banner on the home screen walks you through a temporary root that lasts until the next restart: it installs KernelSU and DFRoot, then opens DFRoot to switch the access on.
The honest part first, because this one has sharp edges. It only works on some phones and some Android versions, and I can’t promise yours is one of them. If it doesn’t take, the phone may freeze and reboot on its own, and a deliberate restart is also how you turn it back off. Do it on a phone you own. CheatDroid doesn’t carry the exploit itself; it downloads those two apps from their own pages on GitHub and hands off to them.
Shizuku says what it can reach
Without root, Shizuku still opens the data of your own debuggable builds, and 4.2 stops overselling it. Before you grant it, the app tells you plainly what Shizuku can and can’t get at. The apps it can actually open are tagged in the list, so you’re not guessing. And while the connection is still coming up, or it failed, or you denied it, the app says which of those happened instead of showing a flat “ready”.
Back goes back one step
Back used to leave the screen even with an open drawer, a search box or a memory selection sitting in front of it. Now it closes those first, one at a time, and only then leaves. Small thing. It annoyed me for months.
New icon
An adaptive launcher icon, so it takes whatever shape your launcher gives every other icon, and a monochrome version for the themed-icon setting.
Hex editor (4.2.1)
- Search. A number finds it as 32-bit little and big endian, 64-bit, float and double. Text matches in UTF-8 and UTF-16, ignoring case, and
3f 42 0ffinds those bytes. - Set a value. A strip shows what the bytes at the cursor read as. Tap a number there and type the new one, without working out the hex or the byte order.
- Binary saves as fields. .NET BinaryFormatter and BSON files open like JSON does: 14,256 fields on a 214 KB Cell to Singularity save. Change a string in a BSON file and the lengths around it get corrected.
- Bigger files, no freezing. On a 100 KB file every tap froze the screen for about 7 seconds. It only draws the rows on screen now, and the limit went from 256 KB to 1 MB. A file too large for the text editor offers the hex editor instead of a dead end.
Search in databases (4.2.1)
Someone asked for this one. Search from the table list and it narrows to the tables holding your text, with a count like “3 of 120 rows match”. Inside a table it filters the rows across all columns, highlights the match and scrolls it into view. Numbers match as text, and % and _ are just characters.
Save files (4.2.1)
Field view now follows a checksum of the whole document. If a string field is the MD5, SHA-1 or SHA-256 of the file with that field emptied, it gets rewritten when you save, which is what Vampire Survivors wants. The filter also puts matching fields first in their group, because in a flat file of 60 settings it narrowed nothing and the hit sat somewhere below the fold.
Network capture (4.2.1 and 4.2.2)
- TLS 1.2 apps work. The worst bug in this round. Capture refused every client on TLS 1.2 while TLS 1.3 was fine, so browsers looked good and nobody saw it. Unity’s own networking only speaks 1.2, so a Unity game’s API calls failed with PIN in the row, and QuizzLand sat on its loading screen. If capture told you a Unity game pins, try it again.
- A refusal doesn’t break the app. The client that refused CheatDroid’s certificate gets tunnelled unread from then on, so it stops retrying forever. In 4.2.2 that means that one TLS stack, not the whole host: NYT Games’ WebView refuses while its native code on the same host doesn’t, and those rows stay readable.
- Big responses (4.2.2). Opening a 452.7 KB response got CheatDroid killed at about 2.5 GB. Bodies are drawn as you scroll now, and the same response takes 164 MB. If you capture anything at all, this is the reason to update.
- Bodies. Gzip unpacks, binary shows a hex dump of the first 8 KB instead of a byte count, and Find in body jumps to the match with a button for the next one.
- Replay sends the real bytes. It used to send the text on screen, so a binary request went out as the words “106 bytes”. Untouched, it’s exactly what the app sent. Editing a binary body still means editing a hex dump as text, which is no real binary editor.
Still open: an endless stream like a radio station doesn’t reach the app during a capture, and a killed CheatDroid leaves its redirect rules behind until the target app’s next capture. Two guides show what capture is good for: the Wordle answer and a radio station’s stream URL.
Updating
4.x shows the update in its menu within a day, or download 4.2.2 and install it over the old one. Pro and your settings stay.