Database Develop

Downgrade to Nougat from Pie?

Hello
Can I downgrade my P10 VTR-L09 from 9.1.0.262
to EMUI 5, via firmware finder?
Is it safe?

kenzyyy said:
Hello
Can I downgrade my P10 VTR-L09 from 9.1.0.262
to EMUI 5, via firmware finder?
Is it safe?
Click to expand...
Click to collapse
No, you cannot
Bootloader has changed since EMUI 8, Security Patch 06/2018, trying to roll-back to the old Bootloader from a firmware with the new Bootloader causes a serious brick
(although, dload will probably just fail with no result and no harm - depending on which package you take, you need a stronger/root method to enforce 'rollback' and therfore to brick)
Anyway, do not even try - there were numerous people who tried with various Huawei phones and ended up with fully bricked devices (they could be repaired only by Testpoints methods, and only by Testpoints method you can rollback over the Bootloader change divide)

zgfg said:
No, you cannot
Bootloader has changed since EMUI 8, Security Patch 06/2018, trying to roll-back to the old Bootloader from a firmware with the new Bootloader causes a serious brick
(although, dload will probably just fail with no result and no harm - depending on which package you take, you need a stronger/root method to enforce 'rollback' and therfore to brick)
Anyway, do not even try - there were numerous people who tried with various Huawei phones and ended up with fully bricked devices (they could be repaired only by Testpoints methods, and only by Testpoints method you can rollback over the Bootloader change divide)
Click to expand...
Click to collapse
Thanks buddy for that information!
Sine I can't go back to Nougat is it possible to roll back to EMUI 8.0? Via firmware flasher or something?
I tried with hisuite but it says I have the latest OS and there is no roll back option.

kenzyyy said:
Thanks buddy for that information!
Sine I can't go back to Nougat is it possible to roll back to EMUI 8.0? Via firmware flasher or something?
I tried with hisuite but it says I have the latest OS and there is no roll back option.
Click to expand...
Click to collapse
In HiSuite, there must be option for Other firmware or so, to go backwards.
Maybe it depends on info from oeminfo and shown only for users who regularly updated byOTA.
Just tried my HiSuite, to roll-back:
click to Update,
switch to Other version / Earlier versions,
and accept Restore
Beware:
>> Bootloader has changed since EMUI 8, Security Patch 06/2018, trying to roll-back to the old Bootloader from a firmware with the new Bootloader causes a serious brick
Which means, you cannot rollback to the old Bootloader (even with Oreo), to be able to seek for BL code the old and cheap way through DC Unlocker (if that was your agenda for rolling back)

zgfg said:
In HiSuite, there must be option for Other firmware or so, to go backwards.
Maybe it depends on info from oeminfo and shown only for users who regularly updated byOTA
Beware:
>> Bootloader has changed since EMUI 8, Security Patch 06/2018, trying to roll-back to the old Bootloader from a firmware with the new Bootloader causes a serious brick
Which means, you cannot rollback to the old Bootloader (even with Oreo), to be able to seek for BL code the old and cheap way through DC Unlocker (if that was your agenda for rolling back)
Click to expand...
Click to collapse
On latest version I don't have rollback option, but I used to have it on previous builds.. I will try to download previous build and try to rollback.
So it's safe to downgrade from 9.1 to 9.0 and to latest 8.0? EMUI ofc

Bricked it.. Black screen no signs of life I can only hear windows connection sounds USB
Please help. Was trying to downgrade from 9.0 to 8.0

kenzyyy said:
On latest version I don't have rollback option, but I used to have it on previous builds.. I will try to download previous build and try to rollback.
So it's safe to downgrade from 9.1 to 9.0 and to latest 8.0? EMUI ofc
Click to expand...
Click to collapse
Again, make sure you don't go back to Sec Patch Jun 2018 or earlier.
Install Firmware Finder on the phone or PC (or go by browser to pro-teammt.ru) find the given version (model, cust and version must match), open ChangeLog and read which Sec Patch it includes (you must double-check yourself, it depends on your model/cust and which build number will HiSuite offer to you for going back)
And before you go, make sure you have stock Recovery (not eg TWRP), also unroot if it was rooted. No hack modifications that included flashing

zgfg said:
Again, make sure you don't go back to Sec Patch Jun 2018 or earlier.
Install Firmware Finder on the phone or PC (or go by browser to pro-teammt.ru) find the given version (model, cust and version must match), open ChangeLog and read which Sec Patch it includes (you must double-check yourself, it depends on your model/cust and which build number will HiSuite offer to you for going back)
And before you go, make sure you have stock Recovery (not eg TWRP), also unroot if it was rooted. No hack modifications that included flashing
Click to expand...
Click to collapse
Its bricked now. I tried to downgrade from 9.0.1.190 to EMUI 8 latest version. Now phone has black screen, I cant seem to turn it on I tried all key combinations still no luck. But my PC recognizes my phone as HI386 something. In Multi-Tool says phone is still on 9.0.1.190 and it hasnt reverted back to EMUI 8. So I think there is a chance probably, I dont have unlocked bootloader nor enabled OEM unlock.
Please I need help getting it back to life. fastboot commands work fine eg. reboot etc..

kenzyyy said:
Its bricked now. I tried to downgrade from 9.0.1.190 to EMUI 8 latest version. Now phone has black screen, I cant seem to turn it on I tried all key combinations still no luck. But my PC recognizes my phone as HI386 something. In Multi-Tool says phone is still on 9.0.1.190 and it hasnt reverted back to EMUI 8. So I think there is a chance probably, I dont have unlocked bootloader nor enabled OEM unlock.
Please I need help getting it back to life. fastboot commands work fine eg. reboot etc..
Click to expand...
Click to collapse
You don't have BL code - or just Bootloader and OEM/FRP were not unlocked?
Have you tried to boot to eRecovery (switch off, connect to charger, press and keep pressing Vol+, boot),
does it offer to (re)install latest firmware and recovery
With the locked BL and/or FRP, you could only try to fix with DLOAD and a proper firmware for your phone and DLOAD,
try the following queries from Fastboot (switch off, connect to PC, press and keep pressing Vol-, boot):
Code:
fastboot devices
PAUSE
fastboot oem get-bootinfo
PAUSE
fastboot oem get-product-model
PAUSE
fastboot oem get-build-number
PAUSE
fastboot oem oeminforead-SYSTEM_VERSION
PAUSE
fastboot getvar vendorcountry
Edit: You can check the following post and ask the poster who also had a brick with P10 and EMUI 9, and how he repaired: https://forum.xda-developers.com/p1...enkirin-aosp-collection-t3828797/post80996581

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
zgfg said:
You don't have BL code - or just Bootloader and OEM/FRP were not unlocked?
Have you tried to boot to eRecovery (switch off, connect to charger, press and keep pressing Vol+, boot),
does it offer to (re)install latest firmware and recovery
With the locked BL and/or FRP, you could only try to fix with DLOAD and a proper firmware for your phone and DLOAD,
try the following queries from Fastboot (switch off, connect to PC, press and keep pressing Vol-, boot):
Code:
fastboot devices
PAUSE
fastboot oem get-bootinfo
PAUSE
fastboot oem get-product-model
PAUSE
fastboot oem get-build-number
PAUSE
fastboot oem oeminforead-SYSTEM_VERSION
PAUSE
fastboot getvar vendorcountry
Edit: You can check the following post and ask the poster who also had a brick with P10 and EMUI 9, and how he repaired: https://forum.xda-developers.com/p1...enkirin-aosp-collection-t3828797/post80996581
Click to expand...
Click to collapse
Thanks for the reply!
So I have to get exact same build number and system version? In Multi Tool it says its on EMUI 9.0.1, phones is recognized in fastboot. But my phone wont go to eRecovery none of the key combinations work its a hard brick

https://prnt.sc/q2r3cn
kenzyyy said:
Thanks for the reply!
So I have to get exact same build number and system version? In Multi Tool it says its on EMUI 9.0.1, phones is recognized in fastboot. But my phone wont go to eRecovery none of the key combinations work its a hard brick
Here is the screenshot of powershell via fastboot https://prnt.sc/q2r3cn
Click to expand...
Click to collapse

kenzyyy said:
https://prnt.sc/q2r3cn
Click to expand...
Click to collapse
Per Fastboot, Bootloader is locked - I guess, you never had BL unlocked?
It shows two versions for VTR-L09 C432, first 9.0.1.190, then 9.0.1.185 - do you remember, did you have 9.0.1.190 and were you downgrading by HiSuite to 9.0.1.185?
Or, were you downgrading by HiSuite from 9.1.0.262 to 9.0.1.190
Try from androidhost.ru, they don't have 190 for c432, but they have 185:
https://androidhost.ru/2AQn
As for their other firmwares (other Huawei phones) that should be the official Huawei Service Repair package
You need to download, unzip, unarj or whatever compression/archiving you find - until you find two folders:
Docs
Software
In Docs folder there must be an installation guide in English, describing (standard, forced) DLOAD procedure
In Software folder, there must be one or more update*.zip files.
You must not unzip those files.
If some of them have c636 or L29 or so in the name, not matching your L09 c432, then exclude such file(s)
Copy these update*.zip files (zipped, with original names) to /DLOAD folder on SD card (not Internal memory) - pull the SD card out, use another phone or card reader to connect to PC and for copying
Read the Installation guide from Software folder to double-check about DLOAD details!
Switch the phone off, put SD card, have it charged at least 50%, press and keep pressing Vol+ and Vol- simultaneously, then boot by Pow
It should start DLOAD installation for 9.0.1.185
If it asks you at the end for Factory Reset (from Recovery), better take it (or take it later)

zgfg said:
Per Fastboot, Bootloader is locked - I guess, you never had BL unlocked?
It shows two versions for VTR-L09 C432, first 9.0.1.190, then 9.0.1.185 - do you remember, did you have 9.0.1.190 and were you downgrading by HiSuite to 9.0.1.185?
Or, were you downgrading by HiSuite from 9.1.0.262 to 9.0.1.190
Try from androidhost.ru, they don't have 190 for c432, but they have 185:
https://androidhost.ru/2AQn
As for their other firmwares (other Huawei phones) that should be the official Huawei Service Repair package
You need to download, unzip, unarj or whatever compression/archiving you find - until you find two folders:
Docs
Software
In Docs folder there must be an installation guide in English, describing (standard, forced) DLOAD procedure
In Software folder, there must be one or more update*.zip files.
You must not unzip those files.
If some of them have c636 or L29 or so in the name, not matching your L09 c432, then exclude such file(s)
Copy these update*.zip files (zipped, with original names) to /DLOAD folder on SD card (not Internal memory) - pull the SD card out, use another phone or card reader to connect to PC and for copying
Read the Installation guide from Software folder to double-check about DLOAD details!
Switch the phone off, put SD card, have it charged at least 50%, press and keep pressing Vol+ and Vol- simultaneously, then boot by Pow
It should start DLOAD installation for 9.0.1.185
If it asks you at the end for Factory Reset (from Recovery), better take it (or take it later)
Click to expand...
Click to collapse
Thanks again for replying.
I downgraded from 9.1.0.262 to 9.0.1.180. it booted fine i used the phone normally. Then I decided to downgrade it to EMUI 8 latest version via firmware finder, since it was complete phone wont boot, respond, nothing. When charging the phone gets pretty warm. So to conclude it its bricked on 9.0.1.190..

Still no luck..

I cannot downgrade from 9 to 8 anymore. This opion is not displayed in HiSuite, did they kill this option? Can someone confirm?
Is there any other option to downgrade from 9.0.1.185 to 8?
Thanks
---------- Post added at 07:25 PM ---------- Previous post was at 07:22 PM ----------
tangmubuddy said:
I cannot downgrade from 9 to 8 anymore. This opion is not displayed in HiSuite, did they kill this option? Can someone confirm?
Is there any other option to downgrade from 9.0.1.185 to 8?
Thanks
Click to expand...
Click to collapse
Update:
Works again after restarting HiSuite, strange

First of, sorry for i don't mean to hijack this thread.
Now here is my question, if for example I was able to unlock my P10 (android ver.7.0) bootloader using DC-unlocker then relock it will I be able to use the unlock code again if my P10 is already in android 9 Pie version?
Thanks!

eyeyousee said:
First of, sorry for i don't mean to hijack this thread.
Now here is my question, if for example I was able to unlock my P10 (android ver.7.0) bootloader using DC-unlocker then relock it will I be able to use the unlock code again if my P10 is already in android 9 Pie version?
Thanks!
Click to expand...
Click to collapse
Bootloader code is bound to the Serial Number of your device, you can reuse it for unlocking/relocking as many times you want, no matter did you upgrade/downgrade, etc

zgfg said:
Bootloader code is bound to the Serial Number of your device, you can reuse it for unlocking/relocking as many times you want, no matter did you upgrade/downgrade, etc
Click to expand...
Click to collapse
Ok thank you for clearing that up.

[QUOTE = "zgfg, publicación: 81031851, miembro: 7786725"]
Por Fastboot, Bootloader está bloqueado, supongo, ¿nunca desbloqueaste BL?
Muestra dos versiones para VTR-L09 C432, primero 9.0.1.190, luego 9.0.1.185 - ¿recuerdas, tenías 9.0.1.190 y estabas bajando por HiSuite a 9.0.1.185?
O, ¿estaba cambiando HiSuite de 9.1.0.262 a 9.0.1.190?
Pruebe desde androidhost.ru, no tienen 190 para c432, pero tienen 185:
https://androidhost.ru/2AQn
En cuanto a sus otros firmwares (otros teléfonos Huawei), ese debería ser el paquete oficial de reparación de servicios de Huawei.
Necesita descargar, descomprimir, unarj o cualquier compresión / archivo que encuentre, hasta que encuentre dos carpetas:
Docs
Software
En la carpeta Docs debe haber una guía de instalación en inglés, que describa el procedimiento de DESCARGA (estándar, forzado)
En la carpeta Software, debe haber uno o más archivos * .zip de actualización.
No debe descomprimir esos archivos.
Si algunos de ellos tienen c636 o L29 más o menos en el nombre, y no coinciden con su L09 c432, excluya dichos archivos.
Copie estos archivos * .zip de actualización (comprimidos, con los nombres originales) a la carpeta / DLOAD en la tarjeta SD (no en la memoria interna); extraiga la tarjeta SD, use otro teléfono o lector de tarjetas para conectarse a la PC y para copiar
¡Lea la guía de instalación de la carpeta Software para verificar los detalles de DESCARGA!
Apague el teléfono, coloque la tarjeta SD, cargue al menos al 50%, presione y mantenga presionado Vol + y Vol- simultáneamente, luego arranque con Pow
Debería iniciar la instalación DLOAD para 9.0.1.185
Si al final te pide el restablecimiento de fábrica (desde la recuperación), mejor tómalo (o tómalo más tarde)
[/CITAR]
I have a similar case, I tried to go down from 9 to 8 but I got an absolute black screen (It does not load, it does not turn on, not erecovery, not fastboot), only when connecting it to the PC, fastboot mode comes out due to the sound of the pc and in fastboot devices it appears but nothing more than there.
I have tried the method you mentioned but without any success, the phone is still dead. My last option is to unlock the bootloader but I don't know if it will be a good idea. I would appreciate your help.

LGE Crash Handler help?

I got a sprint v40, modded it to work with all carriers
I got TWRP installed, got Lineage OS working but I decided that I also wanted to try to get my other slot all modded up so I could also try out DotOS side by side.
After that stuff wasn't working correctly, and now I can't boot into Lineage OS or download mode. (If I let it try to boot normally it says "LGE Crash Handler : FIQ: NOC Error! on a black screen| and at the end says "Enter Sahara Mode")
I've tried stock pie and v35 boot loaders. TWRP is weird on pie boot loader, seems to work fine on v35(bootloader is still unlocked)
If I try to flash either OS it doesn't work and doesn't get installed to phone
I'm lost, and very confused. Does anyone have any tips? I'll take anything.
(I do have LGUP, but can't get it to work. I do have QFIL and adb+fastboot)
(I did nuke LAF's but did restore them thanks to something I found by a fellow user here trying to help someone else and posting LAF's to google drive)

Update, I'm still getting an LGE Crash Handler Error, but I have been able to get it to say "LGE Crash Handler : Kernel Crash!"
I'm hoping that is a step in the right direction
I don't want to see my stupidity dump nearly $200 down the drain.

If someone is in a similar position, get it into download mode. Turn the device off, hold volume up and plug it into your computer. It got my phone to actually go into download mode and save it from death. Finally. Only took two days of messing with to do.

Nice save. That's why keeping download mode is so important. As long as we have download mode, the phone can be brought back to life.
Beware nuking laf. Just don't, unless you really know what you are doing.
[NG]Owner

I nuked it but saw that you uploaded your LAF files, I think I saved mine before hand but didn't label them.So thank you for saving me on that one

I can't get into download mode though, any tips?
Still on 9.0 and the stock img

NGOwner said:
Nice save. That's why keeping download mode is so important. As long as we have download mode, the phone can be brought back to life.
Beware nuking laf. Just don't, unless you really know what you are doing.
[NG]Owner
Click to expand...
Click to collapse
Aún tienes esos archivos tengo el mismo problema pero no puedo entrar ni a modo descarga
Mod translation via GT: You still have those files I have the same problem but I can't even enter download mode

[Bootloop Fix ] Asus zenfone max M2 [X01AD]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
How to Fix BOOTLOOP | Asus Zenfone Max M2
Requirements:
Unlocked Bootloader
Twrp installed
Download Stock ROM android 10
Download Vbmeta.img
Download Tool Kit
Download red warning fix.zip
Using toolkit you can fix
Red warning
Fastboot stuck (continuously reboot into fastboot)
Flash twrp 3.4
Lock Bootloader
Unlock Bootloader
If you facing fastboot stuck or continuously rebooting to fastboot mode
so download toolkit and extract it then connect phone to pc in fastboot mode (press volume + and power)
then run (double click) on Click me to fix stuck fastboot problem.cmd [file]
Or flash file manually
Code:
fastboot flash vbmeta vbmeta.img
Fastboot reboot
{ Now your fastboot stuck problem is fix but still phone not booting so follow below steps also you facing bootloop problem follow below steps }
------------------------------------------------------------------------------------------------------------------------
Fix BOOTLOOP using Recovery
Download any custom ROM
Download firmware
Wipe dalvik cache data, system, vendor
Flash Firmware.zip
Flash ROM.zip
Format data
Reboot system
------------------------------------------------------------------------------------------------------------------------
Fix BOOTLOOP using Stock ROM
Download stock ROM
Download magisk
Download dm-verity
Reboot recovery
Wipe dalvik,data,cache, system,vendor
Flash stock rom.zip
Format data (type yes)
Flash magisk
Flash Dm-Verity
Reboot system
Wait 5-10 minutes until phone Boot up :good:
------------------------------------------------------------------------------------------------------------------------
Fix RED WARNING using phone
Method 1
First Download RED warning fix.zip
- Reboot recovery
- Flash red warning-fix.zip
Your phone automatically boots to system
This fix only works when your system are bootable
if you facing bootloop + red warning so you need to fix bootloop then reboot system
----- Then reboot recovery then flash red warning fix.zip
------------------------------------------------------------------------------------------------------------------------
Method 2. using /ROOT
Install any terminal emulator app
Type su and hit enter
Grant root permission
Copy pest below command
reboot "dm-verity enforcing"
Now hit enter
Your device well be automatically reboot wait until it's Boot
-----------------------------------------------------------------------
Method 3
Fix using PC
Install ADB drivers on pc
Enable developers option from settings
enable USB debugging plug the cell phone into the PC,
type in cmd if not works then download minimal adb.exe
Open it
Type adb devices
(if devices have been detected, proceed to the next command just copy pest)
adb reboot "dm-verity enforcing"
The phone will automatically reboot and the red warning disappears
--------------------------------------------------------
Fix Stuck AT ASUS LOGO
Download Fix-Stuck-at-ASUS-LOGO.zip
IF you flash ROM.zip
but phone stuck at Asus logo so just flash fix stuck-at-Asus.zip
using recovery after flashing ROM.zip
OR......
Reboot recovery
Flash Fix_stuck-at-ASUS-logo.zip
Reboot system
If your Problem are solved then Enjoy
IF not then try again once (read thread carefully)

Agar phone lock ho and eio state se OS pe boot na ho raha ho to kya karoge bhai ?

Techgaming432 said:
Agar phone lock ho and eio state se OS pe boot na ho raha ho to kya karoge bhai ?
Click to expand...
Click to collapse
Go fastboot unlock Bootloader
Then follow steps buddy [Bhai]

Thank you my friend! God bless you!

Noesao said:
Thank you my friend! God bless you!
Click to expand...
Click to collapse
Thank you:angel:

Surendra R sonawane said:
Thank you:angel:
Click to expand...
Click to collapse

Can anyone help with red warning "g.co/ABHg.co/ABH"?
I already googling about it but there are only exist solution to red warning "g.co/ABH".
I've tried the solution but no succeed.
BTW I cannot enter the recovery mode.
Every time I've tried to enter recovery mode, it just restarted.
And I have no idea if the phone has unlocked bootloader nor TWRP installed.
Does anyone has the same trouble?

ipta said:
Can anyone help with red warning "g.co/ABHg.co/ABH"?
I already googling about it but there are only exist solution to red warning "g.co/ABH".
I've tried the solution but no succeed.
BTW I cannot enter the recovery mode.
Every time I've tried to enter recovery mode, it just restarted.
And I have no idea if the phone has unlocked bootloader nor TWRP installed.
Does anyone has the same trouble?
Click to expand...
Click to collapse
hello, mine was having the same problem. to solve it I downloaded a rom on this site https://firmwarex.net/asus-zenfone-max-m2-zb633kl-zb632kl-official-firmware/ then when I finished flashing the rom he gave the same error but this time with the system installed , so I went to fastboot and unblocked it. so the device was working again, but I still haven't found a solution to keep it blocked without the error. if i find i will come back here. sorry if there are mistakes in writing, i don't speak english and use a translator to write

Paulo Ricardo zenfone said:
hello, mine was having the same problem. to solve it I downloaded a rom on this site https://firmwarex.net/asus-zenfone-max-m2-zb633kl-zb632kl-official-firmware/ then when I finished flashing the rom he gave the same error but this time with the system installed , so I went to fastboot and unblocked it. so the device was working again, but I still haven't found a solution to keep it blocked without the error. if i find i will come back here. sorry if there are mistakes in writing, i don't speak english and use a translator to write
Click to expand...
Click to collapse
And how did you unblocked it?
I've already tried using those ROM (FirmwareX.Net_WW_ZB633KL_16.2018.1905.44_20190522_Phone-user.raw) but still gave the same error and when i tried to enter to the recovery, it just restart.

ipta said:
Can anyone help with red warning "g.co/ABHg.co/ABH"?
I already googling about it but there are only exist solution to red warning "g.co/ABH".
I've tried the solution but no succeed.
BTW I cannot enter the recovery mode.
Every time I've tried to enter recovery mode, it just restarted.
And I have no idea if the phone has unlocked bootloader nor TWRP installed.
Does anyone has the same trouble?
Click to expand...
Click to collapse
I think you using official twrp they have some problems try unofficial 3.4
[RECOVERY][3.4.0][X01AD]Unofficial TWRP for Asus Zenfone Max M2
Features: - Decryption works So I'm always confused about this encryption/decryption. Decryption works means: in TWRP i can decrypt my phone data if I have enabled encryption? this decryption option only affects me if I want to make backups of...
forum.xda-developers.com

Paulo Ricardo zenfone said:
hola, el mío estaba teniendo el mismo problema. para resolverlo descargué una rom en este sitio https://firmwarex.net/asus-zenfone-max-m2-zb633kl-zb632kl-official-firmware/ luego, cuando terminé de flashear la rom, dio el mismo error pero esta vez con el sistema instalado, así que fui a fastboot y lo desbloqueé. por lo que el dispositivo estaba funcionando de nuevo, pero todavía no he encontrado una solución para mantenerlo bloqueado sin el error. si lo encuentro volveré aquí. perdón si hay errores al escribir, no hablo inglés y uso un traductor para escribir
Click to expand...
Click to collapse
amigo, ¿podría ayudarme sobre cómo poner el firmware original? Es que no puedo encontrar con qué programa actualizar el firmware

help me i'm stuck.
my phone asus zenfone max m2 got restarted by itself and then stuck on bootloop(showing logo then switch off) . i tried something to solve it and things got even worse.
now no asus logo showing red warning ,can't flash any version of twrp(tried many)
sometimes showing this sometimes some error.
C:\adb>fastboot flash recovery twrp.img
Sending 'recovery' (38936 KB) OKAY [ 1.172s]
Writing 'recovery' OKAY [ 0.500s]
Finished. Total time: 1.726s
tried diretly booting in to recovery after flashing twrp but
fastboot boot twrp.img is not temporarily booting twrp on phone.
I don't know what to do now. help me out please.

Saurabh.010101 said:
help me i'm stuck.
my phone asus zenfone max m2 got restarted by itself and then stuck on bootloop(showing logo then switch off) . i tried something to solve it and things got even worse.
now no asus logo showing red warning ,can't flash any version of twrp(tried many)
sometimes showing this sometimes some error.
C:\adb>fastboot flash recovery twrp.img
Sending 'recovery' (38936 KB) OKAY [ 1.172s]
Writing 'recovery' OKAY [ 0.500s]
Finished. Total time: 1.726s
tried diretly booting in to recovery after flashing twrp but
fastboot boot twrp.img is not temporarily booting twrp on phone.
I don't know what to do now. help me out please.
View attachment 5368365
View attachment 5368367
View attachment 5368365View attachment 5368367
Click to expand...
Click to collapse
try this method
#Fix RED WARNING using phone
maybe you can try method 3

Surendra R sonawane said:
How to Fix BOOTLOOP | Asus Zenfone Max M2
View attachment 5308849
Requirements:
Unlocked Bootloader
Twrp installed
Download Stock ROM android 10
Download Vbmeta.img
Download Tool Kit
Download red warning fix.zip
Using toolkit you can fix
Red warning
Fastboot stuck (continuously reboot into fastboot)
Flash twrp 3.4
Lock Bootloader
Unlock Bootloader
If you facing fastboot stuck or continuously rebooting to fastboot mode
so download toolkit and extract it then connect phone to pc in fastboot mode (press volume + and power)
then run (double click) on Click me to fix stuck fastboot problem.cmd [file]
Or flash file manually
Code:
fastboot flash vbmeta vbmeta.img
Fastboot reboot
{ Now your fastboot stuck problem is fix but still phone not booting so follow below steps also you facing bootloop problem follow below steps }
------------------------------------------------------------------------------------------------------------------------
Fix BOOTLOOP using Recovery
Download any custom ROM
Download firmware
Wipe dalvik cache data, system, vendor
Flash Firmware.zip
Flash ROM.zip
Format data
Reboot system
------------------------------------------------------------------------------------------------------------------------
Fix BOOTLOOP using Stock ROM
Download stock ROM
Download magisk
Download dm-verity
Reboot recovery
Wipe dalvik,data,cache, system,vendor
Flash stock rom.zip
Format data (type yes)
Flash magisk
Flash Dm-Verity
Reboot system
Wait 5-10 minutes until phone Boot up :good:
------------------------------------------------------------------------------------------------------------------------
Fix RED WARNING using phone
Method 1
First Download RED warning fix.zip
- Reboot recovery
- Flash red warning-fix.zip
Your phone automatically boots to system
This fix only works when your system are bootable
if you facing bootloop + red warning so you need to fix bootloop then reboot system
----- Then reboot recovery then flash red warning fix.zip
------------------------------------------------------------------------------------------------------------------------
Method 2. using /ROOT
Install any terminal emulator app
Type su and hit enter
Grant root permission
Copy pest below command
reboot "dm-verity enforcing"
Now hit enter
Your device well be automatically reboot wait until it's Boot
-----------------------------------------------------------------------
Method 3
Fix using PC
Install ADB drivers on pc
Enable developers option from settings
enable USB debugging plug the cell phone into the PC,
type in cmd if not works then download minimal adb.exe
Open it
Type adb devices
(if devices have been detected, proceed to the next command just copy pest)
adb reboot "dm-verity enforcing"
The phone will automatically reboot and the red warning disappears
--------------------------------------------------------
Fix Stuck AT ASUS LOGO
Download Fix-Stuck-at-ASUS-LOGO.zip
IF you flash ROM.zip
but phone stuck at Asus logo so just flash fix stuck-at-Asus.zip
using recovery after flashing ROM.zip
OR......
Reboot recovery
Flash Fix_stuck-at-ASUS-logo.zip
Reboot system
If your Problem are solved then Enjoy
IF not then try again once (read thread carefully)
Click to expand...
Click to collapse
please update link of stuck at asus logo

Saurabh.010101 said:
please update link of stuck at asus logo
Click to expand...
Click to collapse
Link updated

zeo270183 said:
try this method
#Fix RED WARNING using phone
maybe you can try method 3
Click to expand...
Click to collapse
i was missing one step while in red warning. just pressing power button at red warning took me to recovery. this was my first time dealing with red warning.

Saurabh.010101 said:
i was missing one step while in red warning. just pressing power button at red warning took me to recovery. this was my first time dealing with red warning.
Click to expand...
Click to collapse
I haven't had a red warning problem yet, but I've had fastboot stuck and tried the tricks in this post and I succeeded and I hope you too

Bootloop Redmi 9 (lancelot)

Hello i have flash TWRP on my Redmi 9
and on my computer i have typed this command
"fastboot reboot fastboot"
for acces to the fastbootd mode
and now i have
REDMI
Powered By Android
black screen
and
Redmi
Powered By Android
and this loop
my english is very bad
bye

I have this problem too!!! could you fix it? it happened to me when I did this too

try to hard reset

I had the same problem after trying to flash the TWRP custom recovery on my Redmi 9 (lancelot).
In case that someone still needs to know, following was my solution:
I needed to flash back the stock firmware on my device with SP Flashtool. For that you of course need to download the firmware and take the scatter file of it. Then grab a custom Download Agent File and an authentication file from the web.
Also you need the MTK_bypass utility with the right payloads from the github website (Redmi 9 is MT6768, just take the master collection payload, it worked for me). You need that tool to disable the DAA und SLA protection on your Redmi 9. (Except you have access to an authorized Mi account of course, then you can just flash it with Mi Flash tool, but usually, one doesn't have that.) Follow the instruction on the web, there are detailed ways how to install the right drivers and run the bypass utility correctly.
In my case I had to format my device with the automatic flashing in SP Flashtool before the flashing worked, but that was it - my Redmi 9 is working fine again.

thank you for the input as it really cleared my head after i took a break at trying to get this thing out of a bootloop.
this does work, using sp flash tool but the device will auto detect through usb and you've gotta have the scatter file and firmware for the device. after using the brom utility don't restart the phone, you will reverse the process.

iReebu said:
I had the same problem after trying to flash the TWRP custom recovery on my Redmi 9 (lancelot).
In case that someone still needs to know, following was my solution:
I needed to flash back the stock firmware on my device with SP Flashtool. For that you of course need to download the firmware and take the scatter file of it. Then grab a custom Download Agent File and an authentication file from the web.
Also you need the MTK_bypass utility with the right payloads from the github website (Redmi 9 is MT6768, just take the master collection payload, it worked for me). You need that tool to disable the DAA und SLA protection on your Redmi 9. (Except you have access to an authorized Mi account of course, then you can just flash it with Mi Flash tool, but usually, one doesn't have that.) Follow the instruction on the web, there are detailed ways how to install the right drivers and run the bypass utility correctly.
In my case I had to format my device with the automatic flashing in SP Flashtool before the flashing worked, but that was it - my Redmi 9 is working fine again.
Click to expand...
Click to collapse
if my phone is bootloop and can't go into recovery mode either fastboot mode, can it be done ?
my phone bootloop after installing twrp and there you go bootloop until the end. can't go any mode also can't turn off the phone. any suggestion ?

daniel04222 said:
if my phone is bootloop and can't go into recovery mode either fastboot mode, can it be done ?
my phone bootloop after installing twrp and there you go bootloop until the end. can't go any mode also can't turn off the phone. any suggestion ?
Click to expand...
Click to collapse
I had the same issue, I was not able to enter neither recovery mode nor fastboot mode. But you are able to enter EDL mode, the Emergency Download Mode - in my case at least. From there I was able to unbrick the phone. I was able to enter EDL mode without opening the phone and using test points. Turning the phone on and connecting it to the computer in the same second as the screen goes on let me enter for some seconds, it was enough to let me run the tool to bypass the DAA and SLA protection of the device. Then I was able to flash back the stock firmware with SP-Flashtool. In my case I needed to format the device before the flashing worked, but then it booted back up alive.
Just be aware you probably need to install the proper drivers first to bypass DAA and SLA protection with LibUSB.

I have the same problem, help
I already tried all the methods in this post, my phone cannot access fastboot or recovery mode, and when I connect it via usb it starts immediately

iReebu said:
I had the same issue, I was not able to enter neither recovery mode nor fastboot mode. But you are able to enter EDL mode, the Emergency Download Mode - in my case at least. From there I was able to unbrick the phone. I was able to enter EDL mode without opening the phone and using test points. Turning the phone on and connecting it to the computer in the same second as the screen goes on let me enter for some seconds, it was enough to let me run the tool to bypass the DAA and SLA protection of the device. Then I was able to flash back the stock firmware with SP-Flashtool. In my case I needed to format the device before the flashing worked, but then it booted back up alive.
Just be aware you probably need to install the proper drivers first to bypass DAA and SLA protection with LibUSB.
Click to expand...
Click to collapse
Can you tell us how did you unbricked your device step - by - step? Sorry I am a newbie and do not know how to do it.

Alfredo_One said:
Tengo el mismo problema, ayuda
Ya probé todos los métodos en esta publicación, mi teléfono no puede acceder al modo de arranque rápido o de recuperación, y cuando lo conecto a través de USB, se inicia de inmediato.
Click to expand...
Click to collapse
Si hablas español podría ayudarte, te dejo mi FB
Log into Facebook
Log into Facebook to start sharing and connecting with your friends, family, and people you know.
www.facebook.com
Cualquiera que tenga ese problema en cualquiera de los dispositivos Xiaomi que hable español puede comunicarse conmigo y con gusto los ayudaré

How To Guide [GUIDE] UNBRICK YOUR HARD-BRICKED MTK

MIFLASHPRO PROCEDURE​
The MiFlashPro procedure is easier (and the easiest to recover your hard-bricked device), as you do not require the installation of any other external program (like python used in MTK Client for example (expect, of course, the drivers)
MTK Client is a more complicated installation as it requires the installation of Python and Git, which can be harder to use commands for people that don't or never used Python and Git, but gives you access to lock and unlock your bootloader with no 168 HOURS wait
In general, newer MTK chips are really easy to unbrick, even from a hard-brick, as it does not requires to open your phone and test-point it (especially this forum MTK 6833), compared to Snapdragon chips, which is the opposite and even costs 25€ to have a "Authorized Mi EDL Account". Keeping that out of the way, lets get to it
FIRST OF ALL​Install the MTK Preload/BROM VCOM drivers for your computer to recognise your phone in BROM state and follow the instructions given in the installation. Attached at the end of the thread
And download any MIUI ROM version from any trusted website (my favorite is mifirm.net, it downloads faster)
INSTALL MIFLASHPRO Attached at the end of the thread​There's two different Mi Flash(es). Mi Flash and Mi Flash Pro.
Mi Flash is only used to flash MIUI in your device, nothing special, probably everyone knows about it.
Then theres Mi Flash Pro (MFP for short). It's an All-In-One (AIO) tool, as shown below.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
We got the some tabs, but let's focus on the "Recovery" and "SP Flash" tabs, as we do not need the other ones.
Recovery - Recovery flashing. If your device is only booting to Recovery (which can be possible, since someone here has got a case that couldn't boot to fastboot neither system, only to recovery), by writing both your device IMEI's on the spaces, then clicking "Refurbish" leads to a more advanced factory reset than just wiping your data normally. This can get you out of recovery and go back to MIUI however. If it's not your problem, then follow on.
SP Flash - The famous SP Tool. SP Tool is a easy tool to use, may be confusing at first, but then first time a charm and you can get used to it, easily, or after some times. SP Tool is famous for recovering many MTK devices from hard bricks, and thats what we will use to recover your device.
OPEN SP FLASH UP​
Here you are, greeted by a nice interface. There's nothing, but I will explain you to it.
There's 3 blank spaces, called Download-agent (DA for short), Scatter-loading file & Authentication file.
DA is to have access to the devices internal storage to be able to do the flashing;
Scatter-loading shows you the mapping of the partitions it will flash on the MTK;
Authentication is just the MTK protection for newer mtk devices that you need to be able to flash (*its also used to successfully flash, but you still need to bypass it somehow, as you require a Mi Account able to do BROM flashing, see below as you follow the thread)
Now, fill the blanks up:
To find the DA, it is always in the MiFlashPro installation location, so ...\MiFlashPro\. Access that folder, open up "\SP_Flash_Tool_V5" folder, and you will find a file named "MTK_AllInOne_DA.bin", use it as the DA.
To find the authentication file, its located in the same path of the DA, so ...\MiFlashPro\SP_Flash_Tool_V5\, and you will find a file named "auth_sv5.auth", use it as the authentication file.
Finally, to find the scatter-loading file, it is in the ROM folder you extracted, so ...\camellian_xx_xxxx_images_VXX.X.X.X.xxxxx_XXXXXXXX.XXXX.XX_XX.X_xxxxxl\ (the X's represent your MIUI version you downloaded). The scatter-loading file is always located in the folder "images", so \camellian...\images\, and you will find a text file named "MT6833_Android_scatter.txt", use it as the scatter-loading file.
Done?
Don't flash it yet, as we need to fix a issue with "combo_partisize_check".
Open up the scatter-loading file with Notepad or any text editor, so the text file named "MT6833_Android_scatter.txt".
Now, use the locate function to locate the following:
combo_partsize_check: true
After finding the first one, replace the "true" to "false", and the following one, and so on, till every line of them is set to "false" and isn't able to locate any set as "true".
We are done and finished setting up SP Tool!​*Now, we need to bypass the Authentication of our device. Why? Just as the Snapdragon chips, Xiaomi has also implemented a security layer where you need to log in with a "Authorized Mi Flashing Account", which costs money (generally only on Snapdragon devices, I am not sure if we can find any paying service for it), which is really easy to bypass due to BROM.
Download the file "mtkauthbypass.zip" attached in the thread below.
Extract it, open it up, and it looks like this:
Now, press the "Disable Auth" button, you will have 60 seconds to get ready, get your hands on the phone and press at the same time the VOL+, VOL- & POWER button, till you see prompt appearing in the blank space. Should be similiar as this:
(thanks to chopwell20 for image)
After that, immediately open up SP Tool, and press "Download" as fast as possible.
Let it flash, from 5 to 15 minutes.
After it finishes, a blue window with a checkmark appears, disconnect your phone, and just press down the POWER button to boot it up.
And thats it! You have recovered your phone!​If you have any issues or it didn't work out, please reply so someone can help you out
(Simplified image to understand better without explanation)
ISSUES​CONNECTIONS ISSUE is completely normal!
It is when you try to connect your phone in BROM mode to your computer, but it always shows the error symbol over it.
From what it seems, this should be a issue from the phone and not your computer or the drivers itself
It doesn't mean that it makes you unable to unbrick it, but a lot of patience, as with this issue you will require to keep trying over and over again to bypass it.
So, if you can't bypass the Auth, this is probably it. Just keep trying and trying over again till you get it. There's (probably) no workaround rather than having patience to do it
(This also happens to me every time, so I consider it normal, and with some users such as bg0169 having this same issue, I just considered this was important to address it out, but if you think its not this issue, then reply, better safe than sorry)
I made this thread due to some users bricking their devices, and for every new user that hard-bricks their device to hopefully make this to help them

Amazing guide.
Thanks. and missing screenshot where Authbypass gives you prompt.

SP Flash Tool gives error on "gz.img, rescue.img and cust.img" because verified boot is enabled.
Is it possible to bypass it? or how do i disable verified boot without fastboot access? is my device completely dead?

Reelin said:
SP Flash Tool gives error on "gz.img, rescue.img and cust.img" because verified boot is enabled.
Is it possible to bypass it? or how do i disable verified boot without fastboot access? is my device completely dead?
Click to expand...
Click to collapse
yes, it is bypassable.
you just go to the mapping, and disable the checks on those partitions. it will still boot normally, afterwards, if you want (which is not necessary), you can reflash your phone via fastboot and miflash for those partitions to be flashed correctly

1lopes said:
yes, it is bypassable.
you just go to the mapping, and disable the checks on those partitions. it will still boot normally, afterwards, if you want (which is not necessary), you can reflash your phone via fastboot and miflash for those partitions to be flashed correctly
View attachment 5895435
Click to expand...
Click to collapse
Thanks for your reply.
Unfortunately, my phone won't boot when i exclude those images. No vibration, no black screen and no fastboot/recovery.
The another bypass method which requires using readback also doesn't work. I think it's probably because mt6833 is a newer chipset compared to the ones used in tutorials.
Any other advices please? I really don't want to pay money just to use MIUI again.

Reelin said:
Thanks for your reply.
Unfortunately, my phone won't boot when i exclude those images. No vibration, no black screen and no fastboot/recovery.
The another bypass method which requires using readback also doesn't work. I think it's probably because mt6833 is a newer chipset compared to the ones used in tutorials.
Any other advices please? I really don't want to pay money just to use MIUI again.
Click to expand...
Click to collapse
Could you give me more details about the another bypass? I dont understand what do you mean.
If that did not work, then I suppose your bootloader is locked
Please download the engineering ROM > https://mifirm.net/model/camellian.ttt#files;
and flash it via SP Tool like you did to MIUI, then boot to fastboot and flash an EEA image > https://mifirm.net/model/camellian.ttt#eea (if i am correct, EEA images are allowed to be flashed even with locked bootloader.)
If you do get the same verified boot error, disable those partitions to flash once again
If these methods didnt work, you need to install MTK Client to unlock your bootloader and try to reflash via fastboot or SP Tool

1lopes said:
Could you give me more details about the another bypass? I dont understand what do you mean.
If that did not work, then I suppose your bootloader is locked
Please download the engineering ROM > https://mifirm.net/model/camellian.ttt#files;
and flash it via SP Tool like you did to MIUI, then boot to fastboot and flash an EEA image > https://mifirm.net/model/camellian.ttt#eea (if i am correct, EEA images are allowed to be flashed even with locked bootloader.)
If you do get the same verified boot error, disable those partitions to flash once again
If these methods didnt work, you need to install MTK Client to unlock your bootloader and try to reflash via fastboot or SP Tool
Click to expand...
Click to collapse
My father took my phone and paid to repair it. Well, i guess thats a way to fix things...
Anyway, the other method i was talking about was the one using PGPT image and using Hex editor blah blah blah.
By the way, now my phone works but it seems NVRAM was deleted. My IMEI doesn't show up. Can i recover it without using temporary methods?

Reelin said:
My father took my phone and paid to repair it. Well, i guess thats a way to fix things...
Anyway, the other method i was talking about was the one using PGPT image and using Hex editor blah blah blah.
By the way, now my phone works but it seems NVRAM was deleted. My IMEI doesn't show up. Can i recover it without using temporary methods?
Click to expand...
Click to collapse
I dont know how to recover IMEIs since I always back my NVRAM and write it via MTK Client.
You can try this guide:
Thread '[QUICK GUIDE][HOW TO] Unbrick Camellia/Camellian and restore IMEI' https://forum.xda-developers.com/t/quick-guide-how-to-unbrick-camellia-camellian-and-restore-imei.4502077/
Alternatively, which I am not sure, try looking up a IMEI writer program somewhere in the web for MTK

---------- full quote removed ----------
Bro i need help
I followed the process as is, everything went well, I marked the blue box with the checkmark, when I turned on my device it was still the same, what do you recommend I do?
sorry for my bad english, i am using a translator because i am spanish speaking

TheZian said:
Bro i need help
I followed the process as is, everything went well, I marked the blue box with the checkmark, when I turned on my device it was still the same, what do you recommend I do?
sorry for my bad english, i am using a translator because i am spanish speaking
Click to expand...
Click to collapse
That is weird, are you able to boot into recovery or fastboot?
Did you get any verified boot error?
Did you use the right firmware? If so, what version (MIUI version (Indonesia/EEA/MI, etc.), Android version and Codename)? If you used the latest one (MIUI 14 Android 13) please try MIUI 13 Android 12 or lower
Try this:
Post in thread '[SOLVED] RN10 5G Hard-bricked after installing GSI' https://forum.xda-developers.com/t/solved-rn10-5g-hard-bricked-after-installing-gsi.4563191/post-88302451
Esto no debería pasar.
¿Eres capaz de reiniciar en fastboot o recovery?
¿Obtuviste algún error de arranque verificado (verified boot)?
usaste el firmware correcto? si si, cual version (version de la MIUI (Indonesia/EEA/MI...) version de la Android y codename)?

1lopes said:
That is weird, are you able to boot into recovery or fastboot?
Did you get any verified boot error?
Did you use the right firmware? If so, what version (MIUI version (Indonesia/EEA/MI, etc.), Android version and Codename)? If you used the latest one (MIUI 14 Android 13) please try MIUI 13 Android 12 or lower
Try this:
Post in thread '[SOLVED] RN10 5G Hard-bricked after installing GSI' https://forum.xda-developers.com/t/solved-rn10-5g-hard-bricked-after-installing-gsi.4563191/post-88302451
Esto no debería pasar.
¿Eres capaz de reiniciar en fastboot o recovery?
¿Obtuviste algún error de arranque verificado (verified boot)?
usaste el firmware correcto? si si, cual version (version de la MIUI (Indonesia/EEA/MI...) version de la Android y codename)?
Click to expand...
Click to collapse
I use MIUI 12 global version, and can't access fastboot or recovery mode, it didn't give me any error either, and I think I use the correct firmware version.

TheZian said:
I use MIUI 12 global version, and can't access fastboot or recovery mode, it didn't give me any error either, and I think I use the correct firmware version.
Click to expand...
Click to collapse
Try this:
Post in thread '[SOLVED] RN10 5G Hard-bricked after installing GSI' https://forum.xda-developers.com/t/solved-rn10-5g-hard-bricked-after-installing-gsi.4563191/post-88302451

I am unable to use MTK Auth Bypass Tool on my device. It shows an error message 'MTK Auth Disable (SLA/DAA) error!' Can you please help me?

Addendum_expired said:
I am unable to use MTK Auth Bypass Tool on my device. It shows an error message 'MTK Auth Disable (SLA/DAA) error!' Can you please help me?
Click to expand...
Click to collapse
I get the same error, anybody know how to fix?

And there is a "MediaTek Preloader USB VCOM" displayed in the Windows Device Manager.

Reelin said:
SP Flash Tool gives error on "gz.img, rescue.img and cust.img" because verified boot is enabled.
Is it possible to bypass it? or how do i disable verified boot without fastboot access? is my device completely dead?
Click to expand...
Click to collapse
I did have an issue but did not really go through all these stress...I also unbricked it using Brom and my original stock ROM files

Addendum_expired said:
I am unable to use MTK Auth Bypass Tool on my device. It shows an error message 'MTK Auth Disable (SLA/DAA) error!' Can you please help me?
Click to expand...
Click to collapse
Shilze said:
I get the same error, anybody know how to fix?
Click to expand...
Click to collapse
Please try this:
Post in thread '[SOLVED] RN10 5G Hard-bricked after installing GSI' https://forum.xda-developers.com/t/solved-rn10-5g-hard-bricked-after-installing-gsi.4563191/post-88302451

1lopes said:
Please try this:
Post in thread '[SOLVED] RN10 5G Hard-bricked after installing GSI' https://forum.xda-developers.com/t/solved-rn10-5g-hard-bricked-after-installing-gsi.4563191/post-88302451
Click to expand...
Click to collapse
It doesn't work, I think the problem is that the boot mode is bootloader instead of bootrom.

Shilze said:
It doesn't work, I think the problem is that the boot mode is bootloader instead of bootrom.
Click to expand...
Click to collapse
if your phone is displaying the 3 boot modes in the edge, then yes you are in bootloader*
you should restart to any mode, then right as it reboots you shall boot into BROM immediately and redo the same process

I think that when I press the volume up (+), volume down (-), and power buttons on my phone simultaneously, it doesn't seem to recognize any device. However, when I only press the volume up (+) and volume down (-) buttons, it recognizes a MTK Preloader USB VCOM port, and during the process, it seems to attempt to connect twice when "Disable Auth" is enabled. In addition, the BootMode displays as BootLoader