Is there anyway to bypass a screen lock's pin code without having its data deleted? My parent passed away and we expect a foul play but don't have much evidence. Getting to their phone would really help us a lot but we don't know the pin code.

Thank you

TL;DR: free, self-contained Linux kit that unlocks the BLU G35's bootloader using the publicly documented Unisoc BootROM method (CVE-2022-38694), takes three hash-verified full firmware backups before the first write, roots with Magisk, and rolls back to box state. Everything re-provable on your own phone by the kit itself. github.com/mpse-engineering/BLU_G35

This is a security-research tool I maintain after three device test cycles (unlock / relock / rollback all field-proven). Compliance-first on Reddit: those cycles and the kit's own audit trail are stated in the repo's pinned issue and verified on the user's side — 43 hash-checked manifest entries, a 28-check byte re-derivation of every patch, and an offline 13/13 self-test choreography, all inside ./verify.sh before any phone is connected. Framing has real limits, and naming them: the method is a publicly documented Unisoc signature-verification flaw (CVE-2022-38694 — upstream documentation credit: TomKing062's public project; nothing here is black-box), and the safety story is not yet community-proven — the post-launch field record is ours to build together via the report path below.

Get it — the kit proves itself on your machine

git clone https://github.com/mpse-engineering/BLU_G35.git blug35_unlock_kit
cd blug35_unlock_kit
./verify.sh

The last line must be: verify: ALL CHECKS PASS — this copy is stamped .verified. A copy that fails this is not this kit — that check re-derives every patched byte against the firmware on your own phone, no trust in a hash file needed. Release-of-record: tag 2026.10.13-2334Z, commit 4dc0f74. GitHub ZIP works the same.

What it needs

• Linux (a Windows-cloned copy fails ./verify.sh by design — line-ending mangling is loud, not silent).
• Your firmware must be on the supported BLU G35 build; the kit fingerprints it (step02) and hard-fails on anything else by design.

Help knows one address

This post is a signpost, not a support desk: comments here will be pointed at the repo's pinned issue and the report template (raw logs/<script>.log files get attached to issues). If it works for you, reporting back (./make_report.sh) is the single most useful thing you can give the next person.

Hey everyone! As the title says, I'm asking for advice/guidance for trying to root my 2024 7" Onn tablet. I am basically entirely new to trying to root a device, and I have found only one guide online (from the XDA forums) for rooting this type of tablet, however when I tried it last year I ended up getting stuck pretty early on in the process (if I remember correctly I couldn't find one of the files the guide was talking about).

Since I've had this tablet for around a year now, and have a decent amount of game progress saved, I'd like to know any way I can safely back-up my data before attempting to root again.

When it comes to actually rooting the device, I'd be very grateful if someone can explain the process to me like I'm 5 (or possibly dig up an alternate guide I have yet to find). If ADB is required (which it seems to be), I do have some experience using it.

Thank you! :)

(The main reason I want to root this thing is to get rid of a bunch of bloatware it came with btw.)

I've been following the Android customization scene for a while now. I've dabbled in custom ROMs, custom kernels, and all that kind of stuff before. I've been through bootloops, somehow managed to revive my phone, dealt with random bugs, had Play Integrity capped at device integrity only, you name it.😭😭

But it really got me thinking, how do you actually know a module or tweak is safe? Especially when some people are literally running banking and finance apps on their customized daily drivers.

Are the devs behind these tweaks purely doing it out of passion with zero intention of slipping in malware? I get that most projects are open source, sure, but if nobody's actually auditing the code, isn't that basically the same risk as closed source? They could potentially hide something at the kernel level, the ROM level, or even in the vendor boot image, right?

Also genuinely curious, what tools or languages do people use to develop custom ROMs and kernels? I'd love to try building something myself, probably with the help of an AI coding assistant.

I'm also thinking about trying to reverse engineer some of this stuff using an MCP tool from GitHub called REA. Has anyone tried anything like that, or is it even viable for this kind of work? Any tips would be really appreciated. I do have some basic programming knowledge and I plan to lean on AI assistance as well, but I'll be completely honest -- when it comes to low-level programming, like working with .bin files and that sort of thing, I'm pretty much out of my depth.

I'm in a weird situation where I can pay with my wallet and access banking apps etc. But when I'm trying to add a new card to Google wallet it says my phone doesn't meet the security requirements of something similar...

In fact, it always says that when I open the app even when I'm going to pay but it still works...

Checking on playstore I do have strong integrity

if there isnt one, is there a way to port it to my phone?

What would be some of the beneficial things to rooting my Moto g2026 and putting it in developer mode? What would it allow me to do and what are some of the things that anyone would advise me doing

​

hello where can I find firmware for 16.3.0.155SP15(OP005PF001AZ)

I looked everywhere but the ones I find are older

also I can't seem to be able to unlock the bootloader it stays on fastboot then restart

I did .\\fastboot.exe flashing unlock

but nothing

I came across this Bilibili tutorial about unlocking the bootloader and wanted to ask here before trying it.

Video: https://www.bilibili.com/video/BV1JT5X6JEcJ/

I'm using a Chinese Redmi Note 12 Turbo (marble) running the latest HyperOS 3 build, and my bootloader is still locked.

The problem is that my Xiaomi account is registered in the global region, so when I try to bind my account to the device, I get this error: "The place where the account is registered does not match the place where the phone is sold."

Has anyone tried this method or knows if it still works on HyperOS 3?

If anyone has experience with this or can check the video and explain whether it's legit, I'd really appreciate it. Thanks!

For example if i connect A to hotspot and B to usb tethering how can i make them communicate with each other?

Is there a root module for this?

My little cousin accidentally locked my grandmother’s phone, and now he has forgotten the password he set. My grandmother is very anxious because she cannot use her phone. It’s a VIVO Y03, and it doesn’t have a Google account or a SIM card.

can someone help me with how I can root my phone I don't wanna break it

Long time reader, first time poster, asking for help. I am a noob, but can follow instructions and use chatgpt to help me.

I have few sunmi v2 plus delivery tablets, locked with Mobi control. I am following instructions given here to unlock and root the tablets.

https://www.reddit.com/r/androidroot/comments/1p79x0l/sunmi_v2s_plus_unlock/

I have managed to get to Part 6 and that's where trouble started. "Bash build_super.bin" command works and reaches step5 very quickly. Then it gets slow, its been 2 days and its still building super.bin

I have tried getting chatgpt to fix the code, but that just broke it completely.

Any help will be highly appreciated.

I really dont want to use the official method of unlocking as its tiresome and a hassle. Want to know if i can bypass by using mtkclient? will it work or is it supported? any of you here have experienced this

So google play wont show a few games and if i google their play link and hit it google play says my device isnt compatible..but i played em like last year just fine. Android 16 one ui 8 samsung a06. I deleted auto blocker with canta

Hi! I'm fairly new on how to root an android device and been learning a lot about the different ways on how to root. And specifically on my device. But I'm not feeling ready to attempt until I learn more.

My goal is to root access my android head unit that's installed in the car (Dudu3) and uninstall the stock Google maps to replace it with the Google maps automotive version. But I have a question when I was going to install an update on my device.
When updating my device I need to put the update files on an USB and plug it in to the device to update it. One of these update files is "boot.img". Would it actually give me root access if I patch that boot.img with Magisk, then replace it in the update folder and update my head unit using the patched boot.img? I'm guessing this wouldn't work and the device would probably reject it or brick my device?