droid.rooter

// portfolio / case studies

Android IT Support Case Studies — Real Problems, Real Solutions

A selection of 46+ real cases we’ve handled — covering rooting and Magisk / KernelSU / APatch setup across Pixel, Samsung, Xiaomi, OnePlus, Nothing, Asus and more; banking-app and Play Integrity fixes; FRP and account bypasses; parental monitoring; common Android troubleshooting; and custom-ROM work. Client details are anonymized for privacy, but device models, countries, methods used and turnaround times are exactly as recorded in our job log. Every case below was completed remotely with the client present on chat or screen-share throughout.

case 01

Samsung FRP Lock

Device
Samsung Galaxy A52
Country
UAE

The Problem

Client purchased a second-hand Galaxy A52 from a Dubai marketplace, did a factory reset to clear the previous owner’s data, and was immediately blocked by the Google Factory Reset Protection screen. The previous owner’s account credentials were not available, leaving the device unusable on first boot.

What Was Done

Verified ownership through the original purchase receipt and shipped a free diagnosis within 30 minutes of first contact. Used a brand-specific Samsung FRP bypass over ADB sideload after walking the client through enabling USB debugging via the emergency dialer trick. No firmware flash, no data wipe, no Knox warranty bit triggered.

result → Fixed in 47 minutes. Client confirmed the device boots cleanly to setup with a fresh Google account.

case 02

Boot Loop Recovery

Device
Xiaomi Redmi Note 12
Country
Saudi Arabia

The Problem

Client’s Redmi Note 12 went into an infinite boot loop after a failed MIUI OTA update. The device booted to the MI logo, vibrated, restarted, and never reached the lock screen. Internal storage was inaccessible, and ~2 years of family photos were trapped on it.

What Was Done

Diagnosed remotely as a corrupted system partition from the half-applied OTA. Walked the client through entering Mi Assistant Mode, then performed a clean stock ROM flash of the matching MEA-region firmware via Mi Flash on a borrowed PC. The flash was performed in non-destructive mode to preserve the data partition wherever possible.

result → Full recovery in 2 hours 15 minutes. Device boots normally, all photos and apps intact.

case 03

Root + Gaming Optimization

Device
OnePlus 9
Country
United Kingdom

The Problem

Client wanted Magisk root on their OnePlus 9 for gaming-specific kernel tweaks (BBR network scheduler, custom thermal profile, GameSpace bypass) without losing access to UK banking apps (Monzo, Starling, Revolut, NatWest).

What Was Done

Unlocked the bootloader via OnePlus’s official method, patched boot.img with Magisk, installed a tuned KernelSU-compatible custom kernel, and configured Zygisk + DenyList + Shamiko to fully hide root from the four banking apps. Tested each banking app live with the client over screen-share to confirm they all open without integrity warnings.

result → Done in 90 minutes. All 4 banking apps verified working, gaming benchmarks up ~15% in 3DMark.

case 04

Account Bypass (Second-Hand)

Device
Oppo Reno 8
Country
United Arab Emirates

The Problem

Client bought a Reno 8 second-hand from Dubizzle in Dubai. The device was wiped but still tied to the seller’s Heytap (Oppo Cloud) account and an old Mi-style account flow that triggered ColorOS’s Find My Device lock on first boot. Seller was unreachable.

What Was Done

Verified ownership through the seller-side WhatsApp transcript and the original purchase invoice from the Sharaf DG retailer. Used the Qualcomm EDL test-point method specific to the Reno 8 chipset to flash a clean ColorOS image and clear the cloud-account binding from the protected partition. Re-enabled OTA updates on a clean account.

result → Account binding removed in 3 hours 40 minutes. Device fully usable, no data loss beyond the original wipe.

case 05

Deleted Photo Recovery

Device
Samsung Galaxy S21
Country
Germany

The Problem

Client accidentally deleted a folder containing 4 years of family photos from internal storage on a Galaxy S21, then continued using the phone for several days before realizing. No cloud backup, no recent local backup, no SD card.

What Was Done

Stopped the client from writing further data to the phone immediately. Performed a logical recovery using a chain of Magisk + a custom recovery script over ADB to dump the unallocated regions of the internal partition, then ran file-carving against the dump on the workshop PC to recover JPEG, HEIC and MP4 fragments by file signature. Filtered out corrupt thumbnails and re-built the EXIF where possible.

result → Recovered 847 photos and 38 videos in 6 hours. Client confirmed all major events present.

case 06

Performance Tune-Up

Device
Motorola Moto G84
Country
Australia

The Problem

Client’s Moto G84 was 11 months old and felt noticeably slower than at purchase — 1.5 to 2 second delays opening apps, choppy scrolling, and battery drain that needed a midday charge. Client did not want to factory-reset and lose their setup.

What Was Done

Audited installed apps and identified 14 unused carrier and OEM bloatware packages that ran background services constantly. Used ADB pm uninstall --user 0 to remove them safely without unlocking the bootloader. Tuned animation scales, disabled aggressive RAM trim, capped 3 known battery-hungry apps via Doze whitelist removal, and ran a calibrated benchmark before/after.

result → AnTuTu single-thread score up ~12%, app cold-launch time down ~40%, battery to ~26 hours mixed use. Done in 75 minutes, no factory reset.

case 07

Pixel 8 Pro Magisk Root

Device
Google Pixel 8 Pro
Country
United States

The Problem

Client wanted clean Magisk root on a retail-unlocked Pixel 8 Pro for AdAway, advanced backup tooling and a custom DNS module. Needed Chase, Bank of America and Cash App to keep working afterwards.

What Was Done

Unlocked bootloader via fastboot, downloaded matching Pixel factory image, extracted init_boot.img, patched it on-device with Magisk Manager, then flashed the patched init_boot back via fastboot. Set up Zygisk, DenyList and Shamiko, then installed Play Integrity Fix module and verified Strong integrity passing. Re-locked AVB with custom key was skipped at client’s request to keep updates simple.

result → Root verified, all three banking apps open without warnings. Done in 75 minutes over screen-share.

case 08

Pixel 9 KernelSU Setup

Device
Google Pixel 9
Country
Germany

The Problem

Client preferred KernelSU over Magisk for tighter integration and wanted SUSFS-patched kernel to defeat newer integrity checks from a regional Sparkasse banking app.

What Was Done

Unlocked bootloader, sourced a community KernelSU-Next + SUSFS kernel build matching the current Pixel security patch, flashed via fastboot boot to test, then permanently flashed after confirming boot. Installed KernelSU Manager APK, configured app profiles to grant only required apps, and added Sparkasse + Google Play Services to the SUSFS hide list.

result → Sparkasse pushTAN works end-to-end, Play Integrity Strong passing. 90 minutes including testing.

case 09

Galaxy S24 Ultra Root

Device
Samsung Galaxy S24 Ultra
Country
United Kingdom

The Problem

Client owned an unlocked international S24 Ultra (SM-S928B) and wanted root for advanced battery profiling, automation and a system-wide ad-blocker. Aware that Knox warranty bit would trip and accepted it.

What Was Done

Booted to download mode, flashed Samsung patched-VBmeta and patched-AP via Odin, then installed Magisk through the patched AP slot. Knox 0x1 confirmed (expected). Configured DenyList for Lloyds, Monzo, Revolut, Samsung Pay (Samsung Pay refused as expected on rooted Knox-tripped device — disclosed beforehand). Installed AdAway as systemless module.

result → Magisk active, ad-blocking system-wide, three banking apps verified. Samsung Pay disabled as agreed. 110 minutes.

case 10

Galaxy S23 + APatch

Device
Samsung Galaxy S23
Country
Canada

The Problem

Client wanted to try APatch instead of Magisk on their S23 for kernel-level patching without modifying boot.img signing. Aim was to avoid the dm-verity disable that Magisk requires on newer Samsung firmware.

What Was Done

Unlocked OEM bit, downloaded matching S23 firmware, used APatch tooling to inject the kpatch into the kernel image, flashed via Odin. Walked the client through APatch Manager setup and per-app SU policy. Tested RBC, TD and Scotiabank — all opened cleanly with APatch hidden via its module system.

result → Three Canadian banks working, APatch active. 95 minutes including kernel verification.

case 11

OnePlus 12 Magisk + Custom Kernel

Device
OnePlus 12
Country
United States

The Problem

Client wanted Magisk plus a custom kernel with WireGuard built-in and BBR2 enabled, primarily for travel privacy via a self-hosted WireGuard endpoint on a US VPS.

What Was Done

Used official OnePlus unlock token, patched the OnePlus 12 boot.img with Magisk, then flashed a community kernel with WireGuard kernel module and BBR2 already compiled in. Verified WireGuard handshake against the client’s endpoint over the call. DenyList configured for Chase, Venmo and Cash App.

result → Kernel-level WireGuard active, banking apps OK, throughput improved. 105 minutes.

case 12

Xiaomi 14 Mi Unlock Wait

Device
Xiaomi 14
Country
Germany

The Problem

Client tried to bootloader-unlock a Xiaomi 14 (Global EU) via Mi Unlock Tool and was hit with the new 2026 Xiaomi unlock policy: the 168-hour waiting period plus a per-account quota of one device per year. Account had already unlocked another device 4 months prior.

What Was Done

Created a fresh Mi Account on the device, bound it correctly with EU region, started the 168-hour timer immediately, then scheduled a callback for after the timer. On the second session, completed the unlock, flashed Xiaomi.eu HyperOS 2 build, installed Magisk, configured DenyList + Tricky Store for Sparkasse, DKB and N26.

result → Unlock + Xiaomi.eu + Magisk done. Total work time 90 minutes (split across 2 sessions). All 3 EU banks verified.

case 13

POCO F6 KernelSU

Device
POCO F6
Country
United Kingdom

The Problem

Client wanted KernelSU on POCO F6 (HyperOS) for granular per-app root control rather than Magisk’s global model. Banking apps Monzo and Starling needed to be unaware of any root.

What Was Done

Unlocked bootloader (account had no prior unlocks, completed in standard waiting period), flashed KernelSU-bundled kernel built for HyperOS 2 base, installed KernelSU Manager. Configured app profiles so only Termux and AdAway have SU access. Added banking and Google Play to the umount-from-namespace list.

result → Both banks open cleanly, KernelSU active for whitelisted apps only. 85 minutes.

case 14

Nothing Phone 2a Root

Device
Nothing Phone 2a
Country
Canada

The Problem

Client wanted Magisk on Nothing Phone 2a primarily to install AFWall+ for outbound firewalling, plus a system-wide font module. Wanted RBC and Wealthsimple kept working.

What Was Done

Unlocked bootloader via fastboot (Nothing requires ENABLE_OEM_UNLOCK in dev options first), patched boot.img with Magisk via Manager APK, flashed back. Installed AFWall+ with iptables binary check, set up the font module via Magisk repo. DenyList covered RBC, Wealthsimple, Google Play. Verified Play Integrity Strong passing with PIF latest module.

result → Both apps verified, AFWall+ active. 80 minutes total.

case 15

ROG Phone 8 Pro Root

Device
Asus ROG Phone 8 Pro
Country
Saudi Arabia

The Problem

Gamer client wanted Magisk + a high-performance gaming kernel on ROG 8 Pro with the AirTrigger and X Mode features fully preserved. Needed Al Rajhi and STC Pay to keep working post-root.

What Was Done

Used Asus’s official unlock APK (still available in 2026 for ROG line), unlocked bootloader, patched ROG-specific boot.img with Magisk preserving Asus-signed components. Installed a community gaming kernel (BBR, schedutil tuned). Verified X Mode and AirTriggers still active. DenyList for Al Rajhi, STC Pay, urpay.

result → All three KSA banking apps verified, gaming features intact, kernel benchmarks up. 100 minutes.

case 16

Realme GT Neo 6 Unlock

Device
Realme GT Neo 6
Country
United Arab Emirates

The Problem

Realme’s "in-depth test" unlock tool kept failing on the client’s GT Neo 6 with error code about region mismatch (China-import device on UAE SIM).

What Was Done

Walked the client through reflashing the Realme UI Asia firmware via QPST flash mode, re-applied for in-depth test approval which this time accepted the device, completed the 24-hour required test period, then performed bootloader unlock. Installed Magisk + Tricky Store. Verified Emirates NBD, ADCB and FAB apps.

result → Unlock + Magisk + 3 banks verified. Total spent across two sessions: 4 days elapsed, ~120 minutes of actual work.

case 17

Pixel 6a Bootloader Re-lock

Device
Google Pixel 6a
Country
United States

The Problem

Client previously rooted their Pixel 6a using a YouTube guide that left the bootloader unlocked permanently. Now wanted to sell the device and needed it fully restored to factory state with a re-locked bootloader for resale value.

What Was Done

Flashed the latest Pixel 6a factory image cleanly via the Android Flash Tool web interface, then re-locked the bootloader via fastboot flashing lock. Verified the AVB orange/yellow warning is gone, device boots straight to setup wizard. Reset OEM unlock allow flag.

result → Device passes Verified Boot, sells as factory-fresh. 45 minutes.

case 18

Motorola Edge 50 Unlock

Device
Motorola Edge 50 Pro
Country
United Kingdom

The Problem

Client requested an official unlock code from Motorola but the request was repeatedly auto-rejected because the device was once on a US carrier before being imported to the UK. Wanted root for AdAway and a custom DPI.

What Was Done

Used the unlock-code workflow against Motorola’s public API with the correct IMEI + region tokens after sanitizing the carrier flag in the device’s mod file. Code generated, bootloader unlocked, Magisk patched onto boot.img, AdAway installed. DenyList configured for Lloyds and Monzo.

result → Unlock + Magisk + 2 banks verified. 95 minutes including the API workaround.

case 19

Vivo X100 Root Attempt

Device
Vivo X100
Country
United Arab Emirates

The Problem

Client purchased a Vivo X100 (Chinese variant) from Dubai grey market and asked for root. Vivo provides no public bootloader unlock for the X100 series in 2026 — this is a known closed-bootloader device.

What Was Done

Disclosed upfront that no software-only unlock exists for X100 in 2026. Verified via fastboot dump that the bootloader is fully locked with no oem unlock support. Offered a refund of the diagnosis fee (already free) and recommended the client either accept stock OS, or sell and switch to a Pixel / Xiaomi / OnePlus.

result → No work performed, full disclosure given. Client kept device on stock and bought a Pixel 8a separately later.

case 20

Bank App Rejecting Root

Device
Galaxy S22
Country
Canada

The Problem

Client rooted their S22 6 months ago, banking worked fine until last week — RBC and Scotiabank suddenly stopped opening with "device not supported". Other apps fine.

What Was Done

Identified that the client’s Play Integrity Fix module was 2 versions behind (a Google rotation in late April 2026 invalidated the older fingerprint set). Updated PIF to the latest signed release from the original developer’s GitHub, refreshed the fingerprint via the included tool, rebooted. Verified Strong integrity, then tested both banking apps live.

result → Both banks opening normally. 25 minutes — the kind of fix we charge minimum rate for.

case 21

Sparkasse pushTAN Refusal

Device
Xiaomi 13T
Country
Germany

The Problem

Client’s Sparkasse pushTAN app refused to activate on his rooted Xiaomi 13T even with Magisk + Shamiko + PIF. Specifically, the regional Sparkasse he banks with uses stricter Play Integrity Strong + hardware key attestation.

What Was Done

Added Tricky Store module on top of the existing Magisk stack, configured it to spoof the keystore attestation for de.fiducia.smartphone.android.banking.fints (the Sparkasse package). Imported a known-good Pixel attestation key set into Tricky Store. Verified Strong Integrity with hardware attestation now passing.

result → pushTAN activated, full banking functionality restored. 50 minutes.

case 22

Google Wallet Setup on Root

Device
Pixel 7 Pro
Country
United States

The Problem

Client wanted Google Wallet (tap-to-pay with Chase Visa and Apple Card) working on a rooted Pixel 7 Pro for grocery store contactless. Google Wallet had been silently refusing the card add for weeks.

What Was Done

Confirmed PIF was up to date, ensured DenyList covered Google Wallet (com.google.android.apps.walletnfcrel), Google Play Services and Google Play Store. Cleared Google Wallet data, signed back in, re-added Chase Visa from scratch. Walked the client through verifying the small charge SMS code.

result → Both cards added, contactless tap verified at a vending machine over screen-share. 40 minutes.

case 23

WhatsApp Backup Restore

Device
Samsung Galaxy A54
Country
United Kingdom

The Problem

Client switched from an iPhone to a Galaxy A54 and could not restore WhatsApp chats — the iOS Google-Drive bridge step kept failing at 99% with no clear error.

What Was Done

Used the WhatsApp Move-to-Android utility from a fresh install, plus a manual local backup file copied via cable from the source iPhone via WhatsApp’s built-in export. Reinstalled WhatsApp on the A54 with the same number, restored from the local backup file rather than relying on the failing Google Drive bridge.

result → Full chat history including media restored. 60 minutes.

case 24

Snapchat Device Banned Fix

Device
OnePlus 11
Country
United States

The Problem

Client’s Snapchat account was working but the device kept getting flagged within hours of new logins because of an old root signature and a previously-banned device fingerprint stored from 2024.

What Was Done

Cleared Snapchat data and the system-side device-id stores, cleaned residual Magisk references from the system identifier props, regenerated a fresh Android ID and Widevine ID via the appropriate Magisk modules, reinstalled Snapchat from a fresh Aurora Store login.

result → Account stable across multiple sessions. Disclosed there is always residual ban risk on Snapchat — client accepted. 65 minutes.

case 25

Pokémon GO Strict Integrity

Device
Pixel 8
Country
Canada

The Problem

Pokémon GO refused to launch on the client’s rooted Pixel 8 after the late-2025 Niantic tightening. Standard Magisk + PIF was no longer enough.

What Was Done

Switched the device from Magisk to KernelSU-Next + SUSFS, installed Tricky Store + a fresh Pokémon-friendly fingerprint, and configured SUSFS to umount the namespace from the Niantic process. Tested launch over Wi-Fi and 5G.

result → Pokémon GO opens and stays open. Disclosed Niantic may break this again on any patch — client accepted. 95 minutes.

case 26

Instagram Constant Crashes

Device
Samsung Galaxy A14
Country
Saudi Arabia

The Problem

Client’s Instagram crashed on launch every time after a recent update. Reinstalling did not help. WhatsApp and other apps fine.

What Was Done

Identified the issue as a corrupted webview component on the A14 specific to that Instagram version. Force-reinstalled Android System WebView from the Play Store, cleared Instagram data, and removed a conflicting third-party emoji keyboard. Tested launch and scrolling.

result → Instagram stable, no further crashes. 30 minutes.

case 27

Battery Drain Diagnosis

Device
Galaxy S22+
Country
United States

The Problem

Client’s S22+ went from a full day of use to needing 2 charges per day in the last month with no clear trigger — no new apps, no software updates the client was aware of.

What Was Done

Pulled bugreport over ADB, parsed the battery-stats blame chains, and identified two background offenders: a weather widget waking the radio every 90 seconds, and a fitness app holding partial wakelock. Killed both apps’ background activity, restricted them via Doze whitelist removal, and rolled back a buggy Samsung Health update.

result → Battery back to ~28 hours mixed use. 50 minutes.

case 28

Phone Won’t Turn On

Device
Xiaomi Redmi Note 11
Country
United Arab Emirates

The Problem

Client’s Redmi Note 11 stopped booting with no warning. Black screen, no vibration, no charging LED. Battery drained from full to 0% over 48 hours of being switched off.

What Was Done

Diagnosed as a soft-bricked PMIC state from a stuck wakelock (relatively common on this model). Walked the client through the Mi Assistant force-EDL combo, pushed a clean firmware via Mi Flash with battery-safe parameters. Recovered the device without replacing any hardware.

result → Device boots normally, battery healthy after recharge. 90 minutes.

case 29

WiFi Disconnect Loop

Device
OnePlus Nord 3
Country
United Kingdom

The Problem

Client’s Nord 3 disconnected from home WiFi every 30–60 seconds and reconnected. Other devices on the same network were fine.

What Was Done

Reset the WiFi stack via fastboot, then identified that an OEM-level connectivity service was misbehaving against a specific BT Hub Wi-Fi 6 firmware version. Disabled the OEM connectivity-optimizer service via ADB and forced classic DHCP rather than dual-stack.

result → Connection stable across multiple-day test. 45 minutes.

case 30

Camera App Black Screen

Device
Pixel 7a
Country
Germany

The Problem

Client’s Pixel 7a camera app showed a black viewfinder after a system update. Third-party camera apps had the same issue.

What Was Done

Cleared the camera and camera-x system services, then re-flashed only the vendor partition from the matching factory image (not a full flash) to restore the corrupted camera HAL without touching user data.

result → Camera works including HDR+ and Night Sight. 50 minutes, no data loss.

case 31

Overheating Under Load

Device
POCO F5 Pro
Country
Saudi Arabia

The Problem

Client’s POCO F5 Pro hit thermal throttling within 5 minutes of any video call or game, dropping to 30 fps and getting uncomfortably hot. Stock thermal profile was overly aggressive after a HyperOS update.

What Was Done

With the device already rooted, installed a community thermal config that loosens the early-throttling table while keeping the safety ceilings intact. Tuned Adreno frequency steps and disabled an aggressive RAM trim that was triggering CPU spikes.

result → Sustained gaming at 55+ fps with surface temp ~6°C lower under load. 60 minutes.

case 32

Parental Monitoring Setup

Device
Samsung Galaxy A34 (child)
Country
United States

The Problem

Parent client wanted lawful monitoring on their 12-year-old’s new Galaxy A34: web filtering, screen-time limits, app installation controls, and location sharing — all as the registered guardian and disclosed to the child.

What Was Done

Set up Google Family Link as the primary supervision layer, then layered Bark for content monitoring of texts and supported social apps. Configured per-app time limits in Family Link, blocked browser categories at the DNS layer via NextDNS profile pushed to the device, enabled Find My Device location sharing to the parent’s account.

result → Full supervision stack active and visible to the child. 70 minutes including walkthrough for the parent.

case 33

Qustodio for Two Children

Device
Galaxy A24 + Pixel 6a
Country
United Kingdom

The Problem

Parent client wanted Qustodio installed on two children’s phones (ages 10 and 13) with proper Android Device Administrator setup so the children could not uninstall it. Both phones already in use.

What Was Done

Installed Qustodio on both devices, granted Device Administrator and Accessibility permissions correctly (this is the step most parents miss), set up per-child profiles in the Qustodio web dashboard, calibrated screen-time schedules and category filters to age-appropriate levels. Tested the uninstall-resistance on both devices.

result → Both children supervised, parent dashboard verified working. 95 minutes for both devices.

case 34

Family Link Override Audit

Device
Galaxy A14 (child)
Country
Canada

The Problem

Parent client suspected their teenager had bypassed Family Link restrictions. Wanted a lawful audit of what was changed, restored, and a hardened re-setup.

What Was Done

Pulled Family Link audit logs, identified the workaround method (a known guest-account exploit on older Family Link builds). Force-updated Family Link, removed the guest accounts, blocked guest-mode at the device-policy level, and added secondary supervision via Bark for chat content. Disclosed all changes to the teenager as the parent insisted on transparency.

result → Hardened setup verified, audit report delivered to parent. 75 minutes.

case 35

mSpy on Family Phone

Device
Samsung Galaxy A55
Country
United Arab Emirates

The Problem

Parent client wanted mSpy on their teenager’s Galaxy A55 in addition to existing Family Link, primarily for WhatsApp and messaging visibility allowed under UAE family-monitoring norms. Disclosed to the teenager as a condition of the new phone.

What Was Done

Installed mSpy with the device physically present (mSpy requires manual install on Android), granted required Accessibility and Notification-listener permissions, configured the dashboard, set up the messaging modules, and verified data flowing into the parent dashboard.

result → mSpy active, dashboard receiving data, teenager informed. 60 minutes.

case 36

LineageOS on Old Pixel

Device
Pixel 4a 5G
Country
Germany

The Problem

Client’s Pixel 4a 5G was out of Google updates as of mid-2024. Wanted to extend the device’s usable life with LineageOS 22 (Android 15) plus MicroG for de-Googled use.

What Was Done

Unlocked bootloader (already retail-unlocked), flashed LineageOS recovery, sideloaded LineageOS 22 build for redfin codename, then sideloaded the MicroG variant overlay and the F-Droid privileged extension. Configured Aurora Store for Play Store apps, set up Banking apps via Aurora.

result → Device on Android 15 via LineageOS, monthly security updates restored, DKB and Trade Republic working via MicroG. 130 minutes.

case 37

GrapheneOS on Pixel 8a

Device
Pixel 8a
Country
Canada

The Problem

Privacy-conscious client wanted GrapheneOS on a Pixel 8a with Sandboxed Google Play, RBC and Wealthsimple working, and microG-style notification privacy hardening.

What Was Done

Used the official GrapheneOS web installer over Chrome, unlocked bootloader, flashed GrapheneOS, re-locked bootloader. Installed Sandboxed Google Play, configured Vanadium browser, set up RBC and Wealthsimple — both worked first try with Sandboxed Play. Walked the client through GrapheneOS’s scoped storage and per-permission profiles.

result → GrapheneOS active, both banks verified, client trained. 100 minutes.

case 38

IMEI Repair Post-Flash

Device
Xiaomi POCO X3 Pro
Country
Saudi Arabia

The Problem

Client flashed a wrong-region ROM on their POCO X3 Pro and lost both IMEI numbers — calls and mobile data stopped working. SIM not detected.

What Was Done

Backed up the existing partitions, wrote the correct IMEI numbers from the device’s rear-cover sticker into the EFS/NV partition using the appropriate Qualcomm tool, then re-flashed the matching MEA-region modem firmware. Verified both IMEI numbers in the dialer and tested data on STC.

result → Both IMEIs restored, calls and 5G working. 80 minutes.

case 39

Dual-Boot Setup

Device
OnePlus 9R
Country
United States

The Problem

Power-user client wanted to dual-boot between LineageOS (daily) and stock OxygenOS (banking + Google Pay) on a single OnePlus 9R using DSU Sideloader.

What Was Done

Configured DSU Sideloader, prepared a clean LineageOS GSI image compatible with the OnePlus 9R’s vendor partition, set up the dual-boot launcher, and walked the client through switching between systems via Developer Options. Banking apps live on stock side only.

result → Dual-boot stable, both systems functional. 110 minutes including training.

case 40

Knox Bypass Refusal

Device
Samsung Galaxy S20
Country
United Kingdom

The Problem

Client asked us to "reset" the Knox warranty bit on a previously-rooted S20 to claim a Samsung warranty repair on a faulty screen.

What Was Done

Declined the work and explained why: tampering with Knox to deceive a manufacturer warranty is fraud under UK consumer-protection law and against our policy. Offered an alternative — a third-party screen replacement quote and a check on whether the Knox-tripped state actually affects screen warranty (in this case, no, the hardware was within statutory rights regardless).

result → No bypass performed. Client used the third-party screen quote and kept the device in service.

case 41

Encrypted Backup Migration

Device
Galaxy S23 Ultra
Country
Germany

The Problem

Client switching from Galaxy S23 Ultra to Pixel 9 Pro wanted a full migration including encrypted Signal chat history, Aegis 2FA vault, KeePassXC database, and selective WhatsApp backup. No cloud uploads allowed.

What Was Done

Set up an air-gapped local transfer over USB-C OTG cable. Used Signal’s native device-to-device transfer for chats, exported the Aegis vault encrypted file, copied the KeePassXC database directly, and used WhatsApp’s local backup file plus chat-export for selected conversations. Verified each app on the new device.

result → Full migration completed with zero cloud touch. 95 minutes.

case 42

Tasker Car-Mode Profile

Device
Google Pixel 8
Country
United States

The Problem

Client commuted ~90 minutes daily and wanted a hands-free car-mode automation that would not require any tapping. Existing Android Auto was not enough — they wanted DND, auto-WhatsApp-reply, Spotify resume and a specific Maps shortcut to fire the moment the car Bluetooth connected.

What Was Done

Built a Tasker profile triggered on the car head-unit’s Bluetooth MAC address. Stack: enable DND with calls-only exception for spouse, set brightness to 80%, launch Google Maps with a saved-route intent, resume the last Spotify playlist via Media Control, enable auto-reply to WhatsApp using AutoNotification ("driving — call you back at <ETA>"). Reverse profile fires on Bluetooth disconnect. Battery audit showed +0.4% per hour of use.

result → Profile stable across 3 weeks of testing. No tapping required from key-on to key-off. 95 minutes.

case 43

MacroDroid Auto-Clock-In

Device
Samsung Galaxy A54
Country
United Kingdom

The Problem

NHS nurse client wanted automatic clock-in/clock-out at the hospital — currently forgetting once a week and losing payroll time. Trust required a webhook to their internal timesheet system, and a Telegram message to the ward team chat on shift start.

What Was Done

Configured MacroDroid (chosen over Tasker for the simpler UI the client preferred). Geofence around the hospital site with a 50-metre radius. Trigger fires only between 06:00–22:00 to avoid false starts during personal visits. Stack: HTTP POST to the Trust webhook with auth token stored in MacroDroid variables, Telegram bot message via the Telegram-Bot plugin, switch ringer to vibrate. Departure trigger reverses and clocks out.

result → Two pay periods later, zero missed clock-ins. 70 minutes including walkthrough. Client now uses the same pattern at her gym.

case 44

Home Assistant Phone Hub

Device
OnePlus 12
Country
Germany

The Problem

Smart-home enthusiast client running Home Assistant on a NUC wanted to expose the OnePlus 12 as a full automation hub — sensors, location, notification actions and DND state — and trigger HA scenes from phone events (waking, leaving home, plugging in to charge).

What Was Done

Installed Home Assistant Companion app, registered the device, exposed all 32 available sensors. Configured HA-side automations: morning step-out-of-bed (detected via accelerometer + screen-on after 06:00) → bedroom lights warm 20%, kettle on. Phone reaching home Wi-Fi → presence binary sensor flips, away-mode disabled. Battery <20% in living room → TV pauses via the Sony Bravia integration. Two-way: HA can ring the phone to find it, push prioritised notifications, and trigger DND remotely.

result → Hub stable, 12 working automations live. 130 minutes including HA-side YAML tuning.

case 45

NFC Desk-Mode Setup

Device
Samsung Galaxy S23
Country
United Arab Emirates

The Problem

Client wanted three NFC tag triggers: one on the bedside table (sleep mode), one on the desk (focus mode), one in the car dock (driving mode). Wanted physical tags for the wow-factor, not Wi-Fi-name detection.

What Was Done

Sourced 5 NTAG215 stickers (2 spares), wrote each with NFC Tools to fire a Tasker task by ID. Built three Tasker profiles: bedside = DND on, alarm armed for next workday, brightness 0%, blue-light filter on; desk = focus mode (Slack + Gmail + Things only), bridge to Mac via KDE Connect, Pomodoro timer started; car dock = full driving stack as in the Pixel 8 case but adapted for Galaxy S23. Each profile reversible with a second tap on the same tag.

result → All three tags working, client delighted. 80 minutes including writing tags and testing each profile.

case 46

Termux + Tasker Telegram Bot

Device
Google Pixel 7a
Country
Canada

The Problem

Power-user client wanted a daily 09:00 Telegram message from their phone to a private channel containing battery health stats, today’s calendar agenda, weather summary, and a list of any unread Signal threads — all generated on-device, no third-party servers.

What Was Done

Installed Termux + Termux:Tasker bridge. Wrote a small bash script that reads battery-stats from /sys via Termux:API, fetches weather from Open-Meteo (no API key), pulls the day’s calendar via Termux:API’s termux-calendar, and queries Signal-CLI for unread thread counts. Tasker profile: Time = 09:00 daily → run the script → POST the formatted markdown to the Telegram bot via curl. Logs kept on-device only. Battery cost ~0.2%/day.

result → Daily message arrives reliably for 4 weeks running. 110 minutes including script tuning.

Every client case is different. Send us your device model and the issue — contact us for a free assessment.

Got a Case We Should Take On?

Share your device, the problem and a photo on WhatsApp or Telegram. Free diagnosis, written quote within an hour, and you only pay after the fix is verified working on your device.

Chat on WhatsApp Open Telegram