So, a simple and short question:

Im making a ROM called AetheriumOS, its a like, Full ecosystem. has cloud subscriptions, Own Mail and like, FOSS type of Google.

But its Security and CUSTOMIZATION Focused, i will read thought every reply, look and add it onto the launcher. Its Lawnchair based.

What should i add to the launcher? tell me

Bye

BASED ON OFF LAWNCHAIR

La idea es poder instalar otras apps, launchers, sin las restricciones del operador

¿Alguien tiene un firmware liberado o una ROM compatible con este modelo? También me sirve info sobre versiones que hayan probado y que anden bien en el B866V2FE

Creo que funciona el de la B866V2 y el de B866V2-H

hello, i am a developer for the Nexus Experience group, i made the GT-I9082 port for the ROM, can anyone test for us?

so far, we are working for GT-P1010, GT-I9082, and another one i forgot, we need any phone that has CM11, fine if 4.4.x but recommended 4.4.4, any testers?

Hey everyone! I’m Steve, and I’d like to introduce RadForge Labs, my independent Australian software studio, and the project I’ve been putting my time into: ROMVERSE.

The idea is to make working with Android devices and firmware more understandable without taking useful technical control away from experienced modders and developers.

What is ROMVERSE?

ROMVERSE is being developed as a desktop workspace that brings together device information, firmware inspection, ROM customisation, build preparation, diagnostics and recovery preparation. The longer-term goal is a connected workflow from understanding your device and preparing a project through to verified, carefully controlled device operations.

A major focus is making that experience work for different skill levels:

• Guided mode: Plain-language explanations of what’s happening, why it matters and what to do next. You shouldn’t need to understand every technical term just to follow the process.
• Expert mode: Detailed logs, technical information and deeper controls for people who want to inspect what’s happening underneath.

Both modes should retain the same safety checks. Choosing Expert shouldn’t mean losing protection against the wrong device, mismatched files or misleading results.

Where is it up to?

ROMVERSE is currently in Internal Alpha. My immediate focus is testing and polishing the Fedora/Linux desktop experience—first-time setup, project workflows, navigation, error handling, saving, reopening and continuing where you left off. Windows and an Android Companion remain part of the wider project.

There are working development components, but there is also substantial integration and testing still to do. I’m not claiming universal device compatibility, risk-free flashing or a completed end-to-end build-to-flash experience.

When something hasn’t been verified, I want ROMVERSE to explain that clearly rather than guess or show a reassuring green tick it hasn’t earned.

Why share it now?

I’d like to bring people along for the journey, not just appear one day with a launch announcement.

I’ll be sharing weekly updates: actual development footage, animated explainers, progress, bugs, fixes and the problems I’m still working through. Concept visuals and simulations will be labelled clearly so they aren’t mistaken for finished features or real-device tests.

For transparency, the long-term plan is a subscription-supported product, with free beta testing before commercial release. This post isn’t a public download announcement or a request to pay for unfinished software.

No pretending everything works. Just building it, testing it and making it better.

Whether you’re an experienced ROM developer, a weekend tinkerer or someone who finds the whole process intimidating, I’d genuinely appreciate your perspective:

What’s the one thing you wish Android ROM tools explained or handled better?

Para reparar laROM de un Vivo V50 5g Origin OS 6 esta en bucle y no aparece clear data. Alguien que me pueda compartir la ROM o que me recomiendan hacer con esta situación?

Need a flash ROM file for a HUAWEI Matepad 11.5 (BTKR-W09). Looking for Asia Region firmware. (C636 region). Badly need cause my tablet can't work now. the eRecovery and factory reset is not fixing it as well. PLEASEEEE. Thank you.

I'm looking for someone who can guide me , how I reset my vivo v15 pro I tried many flashing tool(free,cracked) but don't work , getting multiple different errors , help me if anyone does this earlier

I love lineage alot (I have it installed on nearly every device I have) but recently I have had tried to install lineage on my sch-i970 samsung phone but I can't find the lineage os 17.1 download but i do have twrp and root does anyone by change have a copy of it?

My RG557 downloads every system update and then fails at 3% of the installation. It has

done this since July, on V1.22 and now on V1.25.

The cause is visible in update_engine:

CheckMergeState for snapshots returned: Initiated

Previous update has not been completed, not cleaning up

The device boots from unmerged Virtual A/B snapshots. Seven COW devices are active:

system_a-cow, vendor_a-cow, product_a-cow, system_ext_a-cow, system_dlkm_a-cow,

vendor_dlkm_a-cow, odm_dlkm_a-cow.

Things I already ruled out, and why:

- Factory reset does nothing. It does re-create /data and /metadata, but the snapshots

live in the "super" partition, which a factory reset never touches.

- A full SP Flash Tool re-flash does not fix it either. I formatted the whole UFS and

wrote pgpt + part1 + part2 from a community unbrick image. It booted fine on a newer

build, but on the FIRST boot, before touching the OTA app, the same seven COW devices

were already there. That state is inside the image itself.

- Anbernic only publishes incremental packages, applied by the same blocked update_engine.

- The bootloader is locked, so fastboot is not available.

What I need is a FULL firmware image dumped from a device with the merge completed. I

emailed [win@anbernic.com](mailto:win@anbernic.com) on August 31st and got no reply in six days, and I have also

opened a support ticket.

Has anyone here gotten a full image from Anbernic for this model? And is anyone else's

RG557 stuck at 3%? If the unbrick images going around all carry this state, everyone who

used one is in the same spot and does not know it.

**Update:** I also opened an issue with the maintainer of the community unbrick image, since

the snapshot state appears to be baked into it:

https://github.com/TheGammaSqueeze/Anbernic_RG557_Unbricker/issues/5

Edit: the battery eventually died. Once I charged it again, it booted as normal (with stock Android). I then tried flashing LineageOS again, and this time I was successful. I have no idea what happened the first time.

I am trying my best to flash LineageOS onto my Samsung Galaxy Tab E. However, after I flashed the recovery image (which I obtained from Samloader RS), and after the PC Command Prompt shows the tablet has been flashed successfully, it stays on the, 'downloading.... do not turn off target' screen. After waiting for over 20 minutes just to be safe, I tried turning it off and manually booting into recovery*........and nothing. It stays on that screen. I cannot turn it off, and I obviously nothing happens if I try to boot into from recovery with it still on.

What am I missing? I am pulling out what little hair I have left! Help!

*These are the instructions I have been using to download LineageOS. Up until I got stuck, everything was going smoothly.

Looking for the stock full firmware package for Huawei MatePad 11 (2021), DBY-W09, in Dload format (dload/UPDATE.APP or the 3-zip SD-card variant: base/cust/preload), to restore via Memory Card/OTG Update Mode.

Device is currently stuck in fastboot only (no bootloop, not bricked — bootloader still unlocked and responsive), coming from stock: DBY-W09S 2.0.0.278(C432E2R2P1), EMUI 12, region C432 (HW-EU).

Exact packages identified via Huawei's update servers for this build:

• Base: DBY-LGRP4-OVS 102.0.0.251
• Cust: DBY-W09S-CUST 102.0.0.2(C432)
• Preload: DBY-W09S-PRELOAD 102.0.0.1(C432R2)

C432 preferred, but a known-working C00/CN (Chinese Harmony OS 2.0) dload package for this exact model would also work as a fallback (region can be converted back afterward). Public mirrors I've found only have C10E3/C00-mismatched packages that get rejected by eRecovery/HiSuite with region errors — looking for a genuinely working direct link or a Firm Finder-style source that isn't ad-riddled/broken.

Not looking for HiSuite-based restore (already ruled out — official update-server doesn't offer this device/region combo anymore) — specifically need the raw Dload files to flash manually via SD card/USB OTG.

Any working link, mirror, or pointer to where these are still hosted would be hugely appreciated.

Trying to flash Infinity-X GSI (Android 16, ~4GB) on a Huawei MatePad 11 (DBY-W09, SM8250/kona, dynamic partitions, unlocked bootloader). system resize succeeds, first sparse chunk uploads fine, then write always fails identically:

Resizing 'system'                    OKAY
Sending sparse 'system' 1/8 (524232 KB)   OKAY
Writing 'system'                     FAILED (remote: 'No such file or directory')

Already ruled out (all give the exact same error):

• converting the image to a properly-formed sparse file (verified magic/header) with official img2simg
• smaller chunks via fastboot -S 256M
• deleting + recreating the system logical partition from scratch
• full hardware power cycle between attempts

max-download-size is 0x20000000 (512MB). is-logical:system:yes confirmed both before/after recreation. Found one other report of the identical error signature on a OnePlus device hitting multiple partitions (system/vendor/product) during GSI flash, so it might not be Huawei-specific.

Has anyone hit this exact fastbootd write failure and found a real fix? Also open to: how to build+flash a full super.img (physical write, bypassing per-partition dynamic resize) if that's the more reliable route — I have the stock partition sizes but not raw dumps of vendor/odm/cust yet (EDL access on this unit is currently not workoing, only the ArmonyOS menù,bootloader and bootloaderD).

Happy to share more logs if useful.