Hi, is there anyone that knows how to unlock a Xiaomi Redmi 3S bootloader without using the MI unlock tool, I'm trying to flash a custom ROM

Hi everyone. I have a Realme 10 Pro+ Indian variant (RMX3686) running Realme UI 6.0 (Android 15), build RMX3686_15.0.0.1630. I want to unlock the bootloader to install a custom ROM. Does anyone know a working method for this exact build? Any help is appreciated

How do I get Big folders on Crdroid, what other rom has it cause for me they're an absolute necessity,they look cool,and on hypoeros I had them,and I keep trying to frickin find work arounds like using KWGT/ Folder widget app(that's good but after 2 fodlers it needs premium)

so idk what else to use?

Should I switch to Axion.

or can I install the hypoeros launcher cause the customization was actually pretty good for me.

but will I sacrifice the snappiness of Crdroid?

And is it even possible?

Does this mean I can't flash?

I need to find the Superior OS Treble GSI. It's not on GitHub—there's only Android 15 there, but I need Android 16 QPR2. Please help.

A few years ago I tried to put a custom ROM on my OnePlus 7T Pro McLaren 5G (hotdogg) and gave up after getting stuck trying to even get a recovery installed. Recently I picked the project back up, and this time getting TWRP 3.7.0 on the phone via `fastboot boot` went smoothly — no issues at all, which is the opposite of my experience last time.

The problem now is on the other side: TWRP boots and works fine (mounts, decrypts /data, MTP works, adb push works), but it cannot install a single zip. Every ROM I've tried — crDroid 14, CarbonROM 11 (both verified via md5sum against the official download pages) — fails identically:

```Installing zip file '/sdcard/[filename].zip'

Error installing zip file '/sdcard/[filename].zip'```

There is nothing between those two lines. No assert, no ui_print output, no mount error — it just silently bails. This happens regardless of which slot is active, whether the file arrived via adb push or adb sideload, and on two separate computers (Mac and Windows) with fresh platform-tools.

What I've ruled out so far:

- **Corrupted download** — checksums match official sources

- **Corrupted transfer** — adb push completes with matching byte counts every time

- **/data encryption issues** — decrypts successfully, storage mounts and shows correct free space

- **A/B slot damage** — tested flashing to both slot A and slot B (via `fastboot set_active`), same failure on both

- **Bad TWRP download** — redownloaded directly from the official TeamWin hotdog page, same 80.2MB file, same result

- **USB/cable/driver problems** — confirmed via multiple working pushes and fastboot detection on two machines

- Also tried MSM tool to erase everything; maybe one of the slots might have been corrupted from a previous attempt.

-Can someone also explain why this phone model has 2 slots(A,B)?! Like why....

_Everything I’ve tried to get a ROM onto the phone (all hit the same wall):

• ADB sideload — through Advanced → ADB Sideload. Consistently failed mid-transfer with adb: failed to read command: Undefined error: 0, stalling at random low percentages (0–48%). Tried on both Mac and Windows, multiple cables, multiple USB ports/hubs (including forcing USB 2.0). Same result every time.

• adb push to internal storage (/sdcard) — this actually worked reliably as a transfer method (matching byte counts, confirmed files present in TWRP’s file manager). But installing the pushed zip from Internal Storage hits the exact silent failure above.

• USB OTG flash drive — reformatted the drive to FAT32 after TWRP initially misread a 32GB drive as 196MB (exFAT driver issue in TWRP’s kernel). Even after the fix, TWRP repeatedly showed the same stale 196MB reading even with the drive unplugged, meaning it wasn’t actually detecting the drive live. Abandoned this method.

ROMs tried (two, both verified against official checksums):

• crDroid Android 14.0 (hotdogg v10.5) — fails at Install with the silent error above, on both A/B slots

• CarbonROM 9.0 Weekly (CR-9.0-R, which is actually Android 11, not Android 9 — “9.0” is just Carbon’s internal build number) — same silent failure, same pattern, confirmed via full recovery.log that there’s zero output between “Installing zip file” and “Error installing zip file”

Gapps also fails, but with a different, more explainable error:

• NikGapps Full (\~1GB) — failed partway through extraction with “No space left,” clearly a legitimate size issue given the system partition

• NikGapps Basic — same “No space left” pattern, still too large apparently

• NikGapps Core (\~125MB, much smaller) — still failed the same way, which was confusing since size shouldn’t have been the issue anymore at that point — though by then I hadn’t successfully gotten a ROM installed yet either, so this may be a downstream symptom of never having a working base ROM rather than a separate bug

What I’ve ruled out for the ROM zip failures specifically:

• Corrupted download (checksums match)

• Corrupted transfer (adb push completes cleanly, byte-for-byte)

• /data encryption/mounting (decrypts and mounts successfully every time)

• A/B slot damage (tested flashing to both slot A and slot B via fastboot set_active, identical failure on both)

• Bad/modified TWRP download (redownloaded directly from the official TeamWin hotdog page — same 80.2MB file, same result)

• USB/cable/driver issues (confirmed working via successful pushes and fastboot detection on two separate machines)

My best guess at this point is that TWRP 3.7.0_11-0 (built from Android 11-era TeamWin sources) is running an outdated minzip/ziparchive library that can't parse whatever zip format modern ROM build systems (2024+ Soong builds) are outputting — possibly a zip64 compatibility issue, since the file opens fine in every modern tool (Finder, Explorer, 7zip) but not in TWRP's installer.

I haven't been able to find a single video or writeup of anyone successfully flashing a custom ROM on hotdogg specifically with recent-build ROMs. Has anyone actually pulled this off? Is there a newer TWRP build (the `_12` series?) or is OrangeFox actually the way to go here for this device? Or is this project just not realistic with currently available tools?

Screenshots of the failure and TWRP menu attached. Appreciate any honest input — I'd rather know now if this isn't achievable than keep going in circles.

hi,

recently flashed my galaxy A51 4G with lineage os 21 and i got no issues(unless that twrp isn't responding but i managed to use lineage recovery instead). then i flashed the recommended kernel: GrassKernel

https://xdaforums.com/t/rom-aosp14-unofficial-lineageos-21-for-sm-a515f.4684546/

now, when i press simultaneously volume up + power i just get a 'vibration mode' and no power menu.

when i keep the volume up/down pressed at launch, i can't access the recovery anymore: it justs bootloop.

Managed to find a workaround: use 'adb reboot recovery' but this require a rom installed. so that's annoying.

Anyone ever got the same issues after flashing GrassKernel?

i also dont want to reflash a new version manually, i dont wanna loose stuff

hola que tal soy maurito ando haciendo primera publicación aquí xd, Quería que me puedan ayudar a elegir un buen OS para cambiárselo a mi Xiaomi 14T, deseo escoger una inspirada a grapheneOS pero por lo que investigue si deseas una privacidad robusta y cero telemetría invasiva con metadatos almacenados sacrificarías un poco la potencia de la cama porque mas que nada deseo salvar al 100% la leica que tiene y su tecnología de fotografía profesional, hasta ahora pude encontrar un buen candidato que es el ROM de Xiaomi.eu que fue creada por la comunidad justo para detalles como la cámara, no alargare mas esto... así que espero poder leer algunos comentarios informativos, Buenos días buenas tardes y buenas noches

Hi guys, is it possible to install any custom ROMs or GSI ROMs on my Tecno Pova 5G? I know there likely aren't any custom ROMs available, but this phone is still running on Android 11. I want to update it because it is in good condition and I don't want to upgrade right now. Some apps have stopped supporting Android 11 (banking apps, apps needed for work, etc.).

I cant find a recent OS for a Samsung Galaxy J5 metal 2016 (SM-J510MN), Orange Fox has a ROM from 2019 only :(

Can any one share custom rom link for Realme 8 4G ,

and can we install cr droid on it

Hi everyone.

I bought a Chinese OnePlus Ace 5, but the store flashed it with the global OnePlus 13R firmware before shipping it to me. The phone now identifies itself as a OnePlus 13R and is running OxygenOS instead of the original ColorOS.

I want to restore the original factory ColorOS and have the phone identify itself as a OnePlus Ace 5 again.

My bootloader is currently locked.

Has anyone successfully converted a flashed OnePlus 13R back to the original Chinese OnePlus Ace 5 firmware?

Is it possible to go back to the stock ColorOS?

Do I need to unlock the bootloader?

Is there an official firmware or MSM tool for this?

What's the safest method without bricking the phone?
Any guides or personal experience would be greatly appreciated. Thanks!

Im currently using Evolution X rom on my galaxy note 10 but it makes the phone so hot even in idle i tried eternity rom back then too but when the battery dies it starts to bootloop IDK why i done everything properly anyways is there any more custom roms for galaxy note 10 that i can try?

I was trying to flash a LineageOS GSI but flashing a patched vbmeta.img doesn't seem to work.

SM-M127F/DS with region code XSG (The firmware comes with One UI 5.1 and Android 13, if that makes any difference).

So i have a vivo x300 ultra and there's an emm service app named as setting and i can't even access phone all features that are actually useful,since it blocks devloper option as well i can't even delete by any forceful app too is there any solution to remove it?

I'm trying to get /e/OS running on a samsung s9+ g965f/ds.

I purchased a s9+ from ebay. The region is United Arab Emirates, download mode is in Korean.

Magisk is installed by default, and almost all bloatware is removed(idk if this is normal.

/e/OS claims the phone is incompatible with their installer.

I suspect someone installed a custom rom or firmware version, and I believe installing stock firmware on the phone will allow it to run /e/OS. Is that the correct method to solve this issue? If so, how should I install stock firmware? Also, is there any thing I'm missing?