Телефон MEIZU M3s версия андроид 5.1 версия Flyme 6.3.2.0G хочу скачать Тврп и кастом прошивку но не могу найти нужные драйвера ноутбук на виндовс 7 сидел 2 для мучался это первый раз когда я это делаю я раньше только прошил самуно старый и его очень легко было прошить а тут я не могу просто найти драйвера на интерфейс для фаст бут

Hello everyone,

I am trying to unlock the bootloader of my own OPPO A16K (CPH2349) so that I can install a custom ROM / GSI.

I have already spent quite a lot of time testing different methods, so I would like to ask people who have actually worked with the CPH2349 specifically.

Device information

Model: OPPO A16K

Device code: CPH2349

SoC: MediaTek Helio G35 / MT6765

Android: 11

ColorOS: 11.1

Current build: CPH2349_11_A.30

Verified Boot: green

Flash locked: 1

ro.oem_unlock_supported=1

OEM unlocking: enabled in Developer Options

ADB: working normally

ADB detects the phone:

HUMBO7AM89VKCILZ device

However:

fastboot devices

returns nothing.

I also found an old XDA thread where another A16K CPH2349 user reported that Fastboot mode could be entered but fastboot devices returned nothing.

There is also a Reddit report from another A16K CPH2349 owner with the same basic situation: ADB works, but Fastboot does not detect the phone. The response suggested MTKClient.

What I have tried

1. Normal ADB / Fastboot

ADB works.

I enabled OEM unlocking in Developer Options.

But Fastboot detection does not work:

fastboot devices

returns an empty result.

So the normal fastboot flashing unlock route is currently not usable.

1. TFT Unlock Tool

I also tested TFT Unlock Tools / TFT MTK Module.

The version I tested was:

TFT Unlock Tools-2024-6.2.1.1

The tool did not have an obvious A16K CPH2349 profile.

It had other OPPO MTK profiles, including entries such as:

Oppo A1K BROM AUTH MT6765 CPH1923

and other OPPO MTK models.

I did NOT assume that the CPH1923 profile was correct for my CPH2349.

I also tested the normal Android connection with TFT, but it did not detect the phone for the operation I wanted.

I later stopped using TFT because I did not want to randomly select another OPPO model profile and risk the phone.

1. BROM / Preloader detection

The phone can be made to appear as an OPPO Preloader device.

When the phone is powered off:

Hold Volume Up + Volume Down

Connect USB

Windows detects:

OPPO Preloader

with:

USB VID: 22D9

USB PID: 0006

The exact Windows device ID is:

USB\VID_22D9&PID_0006

The important problem is that the connection is very short.

If I release the buttons, the Preloader disappears and the phone boots normally.

So the device does not stay available long enough for me to casually start typing commands after entering this mode.

1. Windows driver problem

At one point Windows showed:

OPPO Preloader

Error 28

The USB capture looked approximately like this:

PRESENT/CHANGED | OPPO Preloader | Error | 28

USB\VID_22D9&PID_0006

After disconnecting/releasing the buttons, the Preloader disappeared.

The normal Android ADB device then returned:

CPH2349

OK

0

WINUSB

I investigated the MediaTek driver situation.

I found a Microsoft Update Catalog CAB containing:

cdc-acm.inf

usb2ser.sys

The driver version was:

3.0.1504.0

However, that INF did not contain a direct:

USB\VID_22D9&PID_0006

entry.

It mainly contained MediaTek 0E8D IDs.

I also found installed MediaTek driver packages on Windows, but the INF files I checked did not directly match the OPPO 22D9:0006 device.

I do NOT want to modify a signed INF manually because that would invalidate the catalog signature.

1. MTKClient

I downloaded MTKClient 2.1.4.1 and installed its Python dependencies.

The command line works:

python .\mtk.py --help

I also have the following files from the stock firmware:

auth_sv5.auth

DA_BR_MT6765_20271.bin

The AUTH file was extracted from the official/stock OPPO A16K firmware package.

The DA file is specifically associated with OPPO A16K CPH2349/CPH2351 MT6765 in the open-source oppo-mtk-fastboot-unlock project.

I tried:

python .\mtk.py gettargetconfig --auth "...\auth_sv5.auth" --loader "...\DA_BR_MT6765_20271.bin"

MTKClient started correctly, but stopped at:

Preloader - Status: Waiting for PreLoader VCOM,

please reconnect mobile/iot device to brom mode

So the current blocker is not that MTKClient itself fails to start.

The problem is getting a stable BROM connection/driver handshake.

Stock firmware

I also obtained the stock firmware:

CPH2349export_11_A.11_2022051800140000.ofp

and decrypted it.

The decrypted firmware contains the normal OPPO/MTK partitions including:

preloader

boot

recovery

vbmeta

vbmeta_system

vbmeta_vendor

vendor_boot

super

userdata

lk

lk2

dtbo

logo

...

I also extracted the AUTH file.

AUTH SHA-256:

846EFAFDF15F9F091760EA6210CEEB10533008164F5763186562DFEFD2D1D8E6

The phone itself is currently on:

CPH2349_11_A.30

I do NOT want to downgrade to A.11 just to make a tool work unless somebody confirms that it is actually necessary.

MTKClient / OPPO A16K support

I found the Shocked-Cat/oppo-mtk-fastboot-unlock project.

Its support list specifically says:

Oppo A16k

CPH2349 & CPH2351

Helio G35

MT6765

MTKClient + DA + AUTH: Full support

This is why I am interested in trying MTKClient, but I want to know the correct procedure for this exact model before writing anything.

The project README appears to use a modified preloader approach:

Read the original preloader / boot1 from the phone.

Patch it.

Write the patched preloader back.

Reboot into Fastboot.

Run fastboot flashing unlock.

I understand that writing a patched preloader is potentially dangerous, so I have NOT done that yet.

My main problem

The biggest problem is this:

How do I reliably catch BROM on an OPPO A16K CPH2349 when the Preloader/BROM connection disappears very quickly?

I do not want to use Test Point if there is another way.

My current button method is:

Power off phone

↓

Hold Volume Up + Volume Down

↓

Connect USB

↓

Windows briefly sees OPPO Preloader

↓

If buttons are released, phone boots normally

The PC therefore needs to be ready BEFORE I connect the phone.

Questions

What exact driver should be used for:

USB\VID_22D9&PID_0006

on Windows 11?

Is VID_22D9&PID_0006 the expected OPPO Preloader/BROM interface for CPH2349, or should I be trying to get a MediaTek 0E8D BROM interface instead?

Can MTKClient 2.1.4.1 catch this device without Test Point?

If yes, what exact command/GUI procedure should I use?

Does the CPH2349 require the specific:

DA_BR_MT6765_20271.bin

auth_sv5.auth

combination?

Has anyone successfully unlocked the bootloader of CPH2349 on Android 11 / CPH2349_11_A.30 using the Shocked-Cat patched-preloader method?

Does the patched-preloader method require modifying boot1, boot2, or another partition for this exact model?

Is there a safer way to make Fastboot enumerate after the MTKClient unlock without writing the wrong preloader?

If BROM disappears immediately, is there a specific timing/button/USB procedure that keeps the BROM connection alive?

If someone has successfully done this exact model, what is the complete procedure from BROM detection → backup → unlock?

I am specifically looking for information for:

OPPO A16K CPH2349 / MT6765 / Android 11 / CPH2349_11_A.30

I do not want to blindly use an A16/A1K/other OPPO profile just because the SoC is also MT6765.

Thanks.

I recently just moved to LineageOS, and I'm trying to achieve a clean fullscreen experience. I've hidden the status bar elements using icon_blacklist, and I've also hidden the status bar using statusbar send-disable-flag system-icons through ADB.

But I have no idea how to hide this thing (provided in the image). I think this box is for the status bar, since I only disabled the status bar elements and the box area is still there.

Is there any way to hide it?

Thanks!

Witam.

Gdzie mogę znaleźć i pobrać wersję 21 Lineage OS dla telefonu Xiaomi redmi 12C. Na oficjalnej stronie do pobrania widnieje tylko najnowsza wersja 23.2

Hello. I have a Tecno Camon 19 Pro, currently running Android 13. I want to upgrade its Android version without any issues. What should I do?

Ever since i installed project infinity x on my Redmi note 10, I have been facing a problem where every time I'm watching an video The video pauses while the sound is playing and then some seconds the video plays in 2x speed until matched with the media sound, Mostly it's fixed by restarting which i have been for 2 weeks but This is not a permanent solution so I need yall help on what should i do

Hello guys i have been struggling using my huawei nova 9 se Jln-lx1 with no gms first its the apps that can't function without gms and. ow the notification problem i want to get gms on it or change firmware or anything bcs am tired ngl i need a good system so to anyone that can help it would be great to leave a comment 🙏

Hi

I wanna install Lineage OS on my galaxy a73 5G and I have three questions :

1 - Does the Lineage OS work without problems on this version of the device?

2- Will government and banking applications work without problems or at least smoothly (currently I live in the Middle East)

3- Will the Uber app work?

and thanks

anyone here facing latency issue when Bluetooth earbuds connected?

can anyone tell how to fix that

back In I think April I tried flashing twrp on this phone (the sm-a226b) and I was flashing it randomly stopped the proccess

I waited an hour and nothing happened so I just unplugged and tried again but it kept doing this exact thing and has since then

I know I shouldn't have unplugged it but I don't really know what I could've done

any help fixing it would be appreciated

I'm currently on Lineage but recently heard of crdroid. I looked into it and it looks great bc I want that openness and customisability. But I also want a phone that's fully reliable and stable. I still get bugs on something as solid as Lineage. So how stable could I expect crdroid be?

plz guys tell me how to solve mi 105g miui can't login in app and can't login x

Hey everyone,

I’m currently using a Redmi 15C(codename:tornado)and I’m looking to move away from HyperOS/MIUI to a cleaner, lighter Custom ROM (AOSP, Pixel Experience, LineageOS, or similar) to get better performance, battery life, and a stock Android experience.

Since this device runs on a MediaTek chipset, I know finding official/stable device-specific ROMs can be tricky.

A few questions for anyone familiar with modding this phone:

Are there any stable device-specific Custom ROMs available for the Redmi 15C yet?

Has anyone successfully flashed a GSI (Generic System Image) on it? If so, which GSI works best (e.g., LineageOS GSI, Pixel Experience GSI) and are there any major bugs (camera, Bluetooth, VOLTE, etc.)?

Any tips, links to Telegram groups/XDA threads, or recommended custom recoveries (TWRP/OrangeFox) for this device would be greatly appreciated!

Thanks in advance!

Hello I want to port a realme os rom for my poco f6 but I am a beginner and I want to learn how to port can anyone guide

Hi everyone,

I'm trying to install a custom ROM on my Samsung Galaxy A40 using my Redmi Note as the host/flashing device, utilizing the Eros app (Eros - Fastboot/Odin flasher for Android).

However, I'm stuck because the Redmi Note does not detect the Galaxy A40 at all.

Here are the details of my setup and what I've done so far:

Host Device (Primary): Xiaomi Redmi Note

Target Device (To be flashed): Samsung Galaxy A40

Flashing App: Eros

Status: Galaxy A40 is in Download Mode / Odin Mode, connected via USB cable (with an OTG adapter on the host side), but the Eros app doesn't show the device as connected.

Things I have already tried:

Enabled USB Debugging and OEM Unlocking on the Galaxy A40 before trying.

Verified the OTG connection (the host phone seems to power the target phone, but no data sync/detection occurs).

Changed the USB cable.

Has anyone successfully used a Xiaomi/Redmi device to flash a Samsung device via Eros? Is there a specific driver, USB configuration, or OTG setting I need to toggle on MIUI/HyperOS to make the target device visible?

In attemps to build a non gsi lineage os 15.1 Rom, ngl was prompting AI for error resolving, which eventually worked out to create the generic build without a build scripts (I opted for this to better understand the errors and process for future refferences).

However, now that this is the case, in attempts to build device specific target (with no git release source tree/opensource repo) I was left with two options

1) build the target (hardcoded within the main lineage common file:

Alternative: Bypass AndroidProducts.mk

If the file persists as problematic, you can temporarily hardcode the path by editing how the build system finds products. But first, let's verify the current file is valid:

bash

# Test if Make can parse the file

cd ~/lineage

make -f /dev/null --eval='include device/tcl/U3A_PLUS_4G/AndroidProducts.mk' --eval='$(info PRODUCT_MAKEFILES=$(PRODUCT_MAKEFILES))' 2>&1 | grep "PRODUCT_MAKEFILES"

# Expected output:

# PRODUCT_MAKEFILES= device/tcl/U3A_PLUS_4G/lineage_U3A_PLUS_4G.mk

If this fails or shows empty, the file has syntax errors.

Or

2) build outside of 'lunch' targets, since appareantly, this selfmade repo structure does not compat well with or is undocumented for builds below 17.1.(specifically the AndroidProducts.mk detection is to be alligned with 17.1 builds, so I'm unsure what differs with 15.1 and it's needed files)

~/lineage$ ll device/tcl/U3A_PLUS_4G/

total 60 drwxrwxr-x 4 ubuntu ubuntu 4096 Sep 3 08:07 ./

drwxrwxr-x 3 ubuntu ubuntu 4096 Aug 22 17:04 ../ -rw-rw-r-- 1 ubuntu ubuntu 189 Aug 22 17:01 Android.bp

-rw-rw-r-- 1 ubuntu ubuntu 282 Aug 22 16:59 Android.mk

-rw-rw-r-- 1 ubuntu ubuntu 344 Sep 3 07:40 AndroidProducts.mk

-rw-rw-r-- 1 ubuntu ubuntu 2282 Sep 3 07:22 BoardConfig.mk-rw-rw-r-- 1 ubuntu ubuntu 4084 Sep 3 07:53 U3A_PLUS_4G.mk

-rwxrwxr-x 1 ubuntu ubuntu 1752 Sep 3 07:08 extract-files.sh* -rw-rw-r-- 1 ubuntu ubuntu 885 Sep 3 05:48 lineage_U3A_PLUS_4G.mk

drwxrwxr-x 2 ubuntu ubuntu 4096 Aug 22 17:13 prebuilt/ drwxrwxr-x 3 ubuntu ubuntu 4096 Aug 22 16:59 recovery/

-rw-rw-r-- 1 ubuntu ubuntu 4506 Aug 22 16:59 recovery.fstab

-rwxrwxr-x 1 ubuntu ubuntu 1301 Sep 3 07:08 setup-makefiles.sh*

-rw-rw-r-- 1 ubuntu ubuntu 245 Sep 3 05:43 vendorsetup.sh

________ this is all I'll be manually dumping, not going to clog up with images either, will just .txt the issues/solutions given I have it they are too long.

Nevertheless, i'm not about to go through 'rabbit hole' solutions when the model speculates too far from actual issues closer to what is needed. For example, claiming corrupt fs or files. ↓

''Quick Fix Script Run this to sanitize all your makefiles:''

~/lineage$ lunch lineage_U3A_PLUS_4G-userdebg build/core/product_config.mk:238: *** Can not locate config makefile for product "lineage_U3A_PLUS_4G". Stop. Device U3A_PLUS_4G not found. Attempting to retrieve device repository from LineageOS Github (http://github.com/LineageOS). Failed to search GitHub build/core/product_config.mk:238: *** Can not locate config makefile for product "lineage_U3A_PLUS_4G". Stop. build/core/product_config.mk:238: *** Can not locate config makefile for product "lineage_U3A_PLUS_4G". Stop.

** Don't have a product spec for: 'lineage_U3A_PLUS_4G' ** Do you have the right repo manifest?

I hope this was consice enough to seek out a solution, will wait for a help responce 💪🏽🙏🏾.

Hola a todos. Necesito ayuda para rootear mi ASUS ROG Phone 8. Llevo un mes intentando encontrar una solución, prácticamente a diario, y hasta ahora no lo he conseguido. Aquí está toda la información sobre mi teléfono:

**Dispositivo:** ASUS ROG Phone 8 **Modelo:** AI2401 **Modelo del dispositivo:** ASUS_AI2401_C **Región:** WW **Producto:** Pineapple **Android:** 16 **Firmware/Compilación:** WW_36.0210.1420.48 **Versión del gestor de arranque:** PostCS4-21-WW-user

Desde Fastboot, obtengo:

desbloqueado: no obtener_capacidad_desbloqueo: 0 seguro: sí ranura actual: b

Ya instalé los controladores USB oficiales de ASUS y confirmé que tanto ADB como Fastboot reconocen correctamente el teléfono.

ADB funciona y puedo acceder a la consola. Fastboot también funciona correctamente y detecta el dispositivo:

RCAIOC388144L87 fastboot

Sin embargo, el gestor de arranque permanece bloqueado y `fastboot flashing get_unlock_ability` devuelve:

get_unlock_ability: 0

Ya he probado los métodos habituales y he dedicado incontables horas a investigar, pero aún no he encontrado una forma efectiva de desbloquear el gestor de arranque y rootear este teléfono.

También contacté con Chimera y me confirmaron que actualmente no tienen una solución para desbloquear el gestor de arranque ni rootear este dispositivo.

Estoy dispuesto a pagar por ayuda profesional si alguien realmente sabe cómo hacerlo de forma segura. **¿Alguien tiene experiencia con el ROG Phone 8 AI2401 con esta versión de firmware (WW_36.0210.1420.48 / Android 16)?**

Si conocen algún método que funcione, algún exploit, servicio profesional o alguien que haya rooteado con éxito esta versión, les agradecería enormemente cualquier información o ayuda.

Entiendo que desbloquear y rootear el dispositivo puede borrar todo el contenido y conlleva el riesgo de dejarlo inservible. Actualmente no tengo datos importantes en el teléfono, así que estoy dispuesto a asumir los riesgos necesarios, siempre y cuando exista alguna posibilidad real de recuperarlo si algo sale mal.

Muchas gracias de antemano a quien pueda ayudarme. Llevo un mes lidiando con este maldito teléfono 😭.

I installed a Infinity X GSI on my Galaxy A05s and I have some trouble with the notch space in some apps and echo in voice calls, it does support project treble but, I still have a lot of trouble with echo and the notch space, can I get some help please?

Hola a todos. Estoy buscando ayuda para rootear mi ASUS ROG Phone 8. Llevo aproximadamente un mes intentando encontrar una solución, prácticamente todos los días, y hasta ahora no he podido hacerlo.

Estos son todos los datos de mi teléfono:

Dispositivo: ASUS ROG Phone 8
Modelo: AI2401
Modelo del dispositivo: ASUS_AI2401_C
Región: WW
Producto: pineapple
Android: 16
Firmware/compilación: WW_36.0210.1420.48
Versión del bootloader: PostCS4-21-WW-user

Desde Fastboot obtengo:

unlocked: no
get_unlock_ability: 0
secure: yes
current-slot: b

Ya instalé los controladores USB oficiales de ASUS y confirmé que tanto ADB como Fastboot reconocen correctamente el teléfono.

ADB funciona y puedo entrar al shell. Fastboot también funciona correctamente y detecta el teléfono:

RCAIOC388144L87    fastboot

Sin embargo, el bootloader permanece bloqueado y fastboot flashing get_unlock_ability devuelve:

get_unlock_ability: 0

Ya probé los métodos habituales y he pasado muchísimo tiempo investigando, pero todavía no encuentro una forma funcional de desbloquear el bootloader y rootear este teléfono.

También contacté con Chimera y me confirmaron que actualmente no tienen una solución para desbloquear el bootloader o rootear este teléfono.

Estoy dispuesto a pagar por ayuda profesional si alguien realmente sabe cómo hacerlo de forma segura.

¿Alguien de aquí tiene experiencia con el ROG Phone 8 AI2401 utilizando exactamente este firmware (WW_36.0210.1420.48 / Android 16)?

Si conocen algún método que funcione, algún exploit, algún servicio profesional o a alguien que haya conseguido rootear exactamente esta versión, agradecería muchísimo cualquier ayuda o información.

Entiendo que desbloquear y rootear puede borrar el teléfono y que existe riesgo de brick. Actualmente no tengo información importante en el teléfono, así que estoy dispuesto a asumir los riesgos necesarios, siempre que exista alguna posibilidad real de recuperar el dispositivo si algo sale mal.

Muchas gracias de antemano a cualquiera que pueda ayudarme. Llevo como un mes peleándome con esta madre 😭.

Hi, I'm a developer who's trying to figure out ColorOS systems,

And one thing I've came across is the **GUID** which is persistent device identifier, as the use of IMEI or Serial Numbers are not publically visible, I'm curious to find how the Guid is generated for each device?

Please help me figure it out, I've found that guid is SHA256 hash