Database Develop

fastboot error "FAILED (remote: Command not allowed)"

hello i get this error every time when i try to use fastboot, can some one help me?
c:\sdk\platform-tools>fastboot erase cache
erasing 'cache'...
FAILED (remote: Command not allowed)
finished. total time: 0.004s
i tried many diffrent commands, each time i get this error
have install google usb driver, device manager calls all fine.
have also tried the flashtool driver, device manager calls all fine but cmd.exe (admin) and fastboot same error.
only working command is to unlock the bootloader .
so my bootloader is unlocked and fastboot driver senn to be right.
can you please help me
windows 8.1 64 bit
xperia z c6603
bootloader open

no idea?
Sent from my C6603 using XDA-Developers mobile app

bump
If no one replies, in my experience, just inbox one of the old devs from our phone. Sometimes, if their not too busy they'll give you some time. They're just dudes trying to help people have cooler phones, anyway.

In my case, I get those errors because my bootloader was locked. I've unlocked a lot of times but not with the right code. I suggest you to try unlocking the bootloader with the right IMEI (not the one on the box nor the one in Flashtool) and enabling USB debugging.

i have order the unlock code 3 times from sony, also look on the rooting status:
Bootloader unlocked: Yes
i´m using the sony emma flashtool, and this works only with unlocked bootloader, but on fastboot i cant execute comands
dont know what is wrong

steve233 said:
i have order the unlock code 3 times from sony, also look on the rooting status:
Bootloader unlocked: Yes
i´m using the sony emma flashtool, and this works only with unlocked bootloader, but on fastboot i cant execute comands
dont know what is wrong
Click to expand...
Click to collapse
In case you use linux, try this setting permissions first:
http://forum.xda-developers.com/xperia-z/help/flashing-rom-twrp-bootloader-boot-img-t3241148
Edit:
You mentioned cmd.exe, so I guess you use windows and this is not the case,
however it may be similar issue for windows, since you run cmd from admin.
In my case, on linux, without permissions, my computer could only recognize the device from superuser/admin. With permissions like in the thread above, any user could run commands to device, and finally I did the trick without superuser/admin.

so you think it is an administrator premission problem?
i have format my windows pc today and reinstall all, but same problem, fastboot and device driver is without issue in device manager.
also create new administrator account, didn´t help.
edit:
i tried some more commands and some of them worked
HTML:
> fastboot erase boot works
> fastboot erase system works
> fastboot erase userdata works
> fastboot erase cache faild
> fastboot erase recovery faild
> fastboot oem lock faild just show 3 dots and nothing happening i wait 1 hour for sure

I can see you are using Windows 10. There are problems with driver verification. Have a look in device manager and check if your device is recognized properly in fastboot mode. If drivers cannot be installed you have to boot windows with signed driver verification turned off. For this press and hold shift and klick on reboot. Then choose troubleshooting and then something like restart options. At the next boot you have to press 7 - I think. Now fastboot drivers should install correctly.
Sent from my E6653 using XDA-Developers mobile app

its windows 8.1 x64 and driver are already installed no problems on device manager, i also have open bootloader.

I am having the same problem with windows 10 64 bit.
I give up.
pls help

try to run fastboot.exe under administrator's permission (either by setting properties on fastboot.exe or by running administrative cmd).
I'm using android sdk on ubuntu, I have to add "sudo" (run as root) before fastboot command but there's no need for "adb".

I think the device (xperia z c6603) isn't supporting some commands, but (boot system userdata) erase works.
maybe some experts can give a final answear

Try enabling OEM unlocking in the developer settings on the phone first.

This!
jackflap said:
Try enabling OEM unlocking in the developer settings on the phone first.
Click to expand...
Click to collapse
Thanks, been trying to unlock the BL of my Z5. I didn't know that this has the option. Previously on my Z1C and Z3 Dual there was no such option or lock

jackflap said:
Try enabling OEM unlocking in the developer settings on the phone first.
Click to expand...
Click to collapse
Awesome, thanks for that needle in a haystack!
Worked on Xperia X F5121 US version with the UK firmware to enable fingerprint scanner.

remote: command not allowed
Honor 6X BLN-L24
I had the same issue for the longest and tried everything possible under XDA's advice. its for the first time that I was not able to find the soloution to my isuues with the phone. Desperation led me to keep on trying until I accidently found how to do a "Hard Reset" which eventually solved this issue
1) Power your phone off.
2) Press Vol Up (+) Button and while keeping it pressed push the power Button (keeping both pressed).
3) As soon as you see the honor logo (blueish color), move from Vol up (+) to Vol down (-) While Still Pressing On The Power Button.
4) Keep Pressing Vol (-) and Power Button, --> will go through "turning your device on" --> Blank Screen --> Hard Reset Menu.
5) Well everyone knows from this point onwards --> Wipe It Clean, Reboot, Just like New.
Hope this helps.

I have bricked my phone (sony logo and nothing else) and can only connect in fastboot (not even flashmode). I try to flash a kernel but shows the same error. What should i do now? (Im on wind10 64bit)

Totesz00 said:
I have bricked my phone (sony logo and nothing else) and can only connect in fastboot (not even flashmode). I try to flash a kernel but shows the same error. What should i do now? (Im on wind10 64bit)
Click to expand...
Click to collapse
same problem.....

gungsye said:
same problem.....
Click to expand...
Click to collapse
Lograste solucionar el problema, a mi me pasa lo mismo...solo reconoce mi móvil en modo Fastboot y me muestra el mismo mensaje de error. Habrá alguna forma de instalar todo por fasstboot y recuperar mi Xperia Z (c6603)?
De antemano garcías.

PLEASE HELP - Device Bricked - edl waiting for device

Hello I have a Mi A2 with ONE.
I tried to install Mi6X following this guide:
Guide
I got to step 9:
9- Click Refresh on Mi Flash Then choose Clean all and click flash
Then I got this error:
Error oem edl miflash tool, ACK count don't match
Then I tryed instead to install Jasmine again, and I started getting this error:
Cannot receive hello packet,MiFlash is trying to reset status
And then I was stupid enough to unplug my phone
THE ACTUAL PROBLEM (rigth now)
1. My phone will start, then stay at Mi(mi.com) logo indefinitely.
2. I can't enter download mode, Vol + and power will bring me the Mi logo again and again.
3. Can enter Fastboot mode... BUT...
-Mi flash don't detect it
-miflash_unlock don't detect it
-edl.cmd, unlock auto, and unlock critical say "< waiting for device >"
Edit: I solved the problem using test point to enter EDL mode, then It connected and I could flash it.

our phones (mia2) are weird devices to be honest, mine was recently bricked after choosing the "reboot to bootloader" option in twrp. id recommend you to go to mi service center if your phone is still in warranty

Stoopid Dickhead said:
our phones (mia2) are weird devices to be honest, mine was recently bricked after choosing the "reboot to bootloader" option in twrp. id recommend you to go to mi service center if your phone is still in warranty
Click to expand...
Click to collapse
Thanks for the reply. But unfortunately I can't
That would be my first solution, but my Mi A2 is not in warranty anymore...

have you tried to install stock rom with fastboot?

Maharram said:
have you tried to install stock rom with fastboot?
Click to expand...
Click to collapse
Miflash won't detect the phone, it's like is not connected at all...

puerco-potter said:
Miflash won't detect the phone, it's like is not connected at all...
Click to expand...
Click to collapse
No im not talking about miflash im saying fastboot u can install stock rom with fastboot too you need payload bin dumper and ota flasher for that

Maharram said:
No im not talking about miflash im saying fastboot u can install stock rom with fastboot too you need payload bin dumper and ota flasher for that
Click to expand...
Click to collapse
Sorry, can you help me unsderstand a little.
I found this guide:
Guide
But none of my Roms (Jasmine or Wayne) have a file that's named payload.bin
I feel like I am missing something
Edit:
I found that ota updates are the ones with the payload.bin file followed the guide and everything, but fastboot bring almost the same error that EDL brings:
< Waiting for any device >
Can it be that my cable somehow magically from one conection to another stoped working or something? I asked a friend for his cable... Cs are not as common in this country yet.

puerco-potter said:
Sorry, can you help me unsderstand a little.
I found this guide:
Guide
But none of my Roms (Jasmine or Wayne) have a file that's named payload.bin
I feel like I am missing something
Edit:
I found that ota updates are the ones with the payload.bin file followed the guide and everything, but fastboot bring almost the same error that EDL brings:
< Waiting for any device >
Can it be that my cable somehow magically from one conection to another stoped working or something? I asked a friend for his cable... Cs are not as common in this country yet.
Click to expand...
Click to collapse
Have you enabled oem unlock ?

puerco-potter said:
Hello I have a Mi A2 with ONE.
I tried to install Mi6X following this guide:
Guide
I got to step 9:
9- Click Refresh on Mi Flash Then choose Clean all and click flash
Then I got this error:
Error oem edl miflash tool, ACK count don't match
Then I tryed instead to install Jasmine again, and I started getting this error:
Cannot receive hello packet,MiFlash is trying to reset status
And then I was stupid enough to unplug my phone
THE ACTUAL PROBLEM (rigth now)
1. My phone will start, then stay at Mi(mi.com) logo indefinitely.
2. I can't enter download mode, Vol + and power will bring me the Mi logo again and again.
3. Can enter Fastboot mode... BUT...
-Mi flash don't detect it
-miflash_unlock don't detect it
-edl.cmd, unlock auto, and unlock critical say "< waiting for device >"
Please help, I am really afraid my phone will die permanetly as I can't turn it off and I don't know if it will charge in it's current state.
Click to expand...
Click to collapse
Did you flash hex kernel? You know that phone on 6x miui rom will not boot if you havent flash custom kernel after miui?

Mi flash tool won't work with locked bootloader
Install adb drivers and write command
' abd oem edl '
If ur phones connects
Than u can use mi flash tool

Maharram said:
Have you enabled oem unlock ?
Click to expand...
Click to collapse
I followed this guide to unlock bootloader previous to the guide on flashing of the first post:
GUIDE
The .bat that you run there actually executes "fastboot oem unlock". I did that part without any problem, the phone screen asked for confirmation and everything fine. After succefully unlocking bootloader I followed the guide on flashing Miui 10.
Now even that "fastboot oem unlock" will show this message:
< waiting for any device >

Amnvlad said:
Mi flash tool won't work with locked bootloader
Install adb drivers and write command
' abd oem edl '
If ur phones connects
Than u can use mi flash tool
Click to expand...
Click to collapse
"adb oem edl" brings this error:
adb.exe: unknown command oem
"fastboot oem edl" brings this error:
< waiting for any device >
and
"adb reboot bootloader" brings this error:
error: no devices/emulators found
(tested everything with the phone in fastboot or the Mi logo)

mariosenta said:
Did you flash hex kernel? You know that phone on 6x miui rom will not boot if you havent flash custom kernel after miui?
Click to expand...
Click to collapse
I didn't, because I got an error when flashing Miui, never got to follow the rest of the guide because my phone won't be recognised by any program it seems...
Thanks you all for the help, I will try with another cable, and if that don't work I will test point this little one. I really don't want to open it... but It seems like fastboot won't connect no matter what...

puerco-potter said:
I followed this guide to unlock bootloader previous to the guide on flashing of the first post:
GUIDE
The .bat that you run there actually executes "fastboot oem unlock". I did that part without any problem, the phone screen asked for confirmation and everything fine. After succefully unlocking bootloader I followed the guide on flashing Miui 10.
Now even that "fastboot oem unlock" will show this message:
< waiting for any device >
Click to expand...
Click to collapse
Did you execute this line "fastboot flashing unlock_critical" after fastboot oem unlock?

mariosenta said:
Did you execute this line "fastboot flashing unlock_critical" after fastboot oem unlock?
Click to expand...
Click to collapse
Originally yes, after oem unlock, I ran flashing unlock_critical

puerco-potter said:
I followed this guide to unlock bootloader previous to the guide on flashing of the first post:
GUIDE
The .bat that you run there actually executes "fastboot oem unlock". I did that part without any problem, the phone screen asked for confirmation and everything fine. After succefully unlocking bootloader I followed the guide on flashing Miui 10.
Now even that "fastboot oem unlock" will show this message:
< waiting for any device >
Click to expand...
Click to collapse
You installed oreo on pie? Because Mi A2 has antiroll back projection if you downgrade your Android version then you lost your imei code

Maharram said:
You installed oreo on pie? Because Mi A2 has antiroll back projection if you downgrade your Android version then you lost your imei code
Click to expand...
Click to collapse
6x has antiroll back, a2 does not.
---------- Post added at 11:13 AM ---------- Previous post was at 11:12 AM ----------
[/COLOR]
puerco-potter said:
I didn't, because I got an error when flashing Miui, never got to follow the rest of the guide because my phone won't be recognised by any program it seems...
Thanks you all for the help, I will try with another cable, and if that don't work I will test point this little one. I really don't want to open it... but It seems like fastboot won't connect no matter what...
Click to expand...
Click to collapse
Please, keep us updated.

I had the same issues like you months ago. The only solution you buy a pentalobe 0.8mm for iphone, a small philips screw driver, and a tweezer. Flash your phone in EDL mode. You need to contact 2 pins. You can search the location of the pins, how to disassemble the phone by googling it. then just flash Mi A2 stock ROM first, then convert it to Mi 6X again. I

hasel17 said:
I had the same issues like you months ago. The only solution you buy a pentalobe 0.8mm for iphone, a small philips screw driver, and a tweezer. Flash your phone in EDL mode. You need to contact 2 pins. You can search the location of the pins, how to disassemble the phone by googling it. then just flash Mi A2 stock ROM first, then convert it to Mi 6X again. I
Click to expand...
Click to collapse
No need to convert, now we have miui for a2.

mariosenta said:
No need to convert, now we have miui for a2.
Click to expand...
Click to collapse
Where can I take a look at this? I am really interested.
The cable wasn't the issue, I am getting the tools to open it tonight.

[bricked] Slot _b is unbootable

So I ended up in the brick wagon, basically doing this:
- Tencent CN version converted to WW by vendor.
- Rooted / uptaded from root folder
- Changed fingerprint to WW
- Decided things got buggy here and there, did a factory reset
-> Slot _b is unbootable / Bricked
I tried flashall_AFT.cmd from both WW and CN raw firmware, both by clicking and command prompt, nothing happens (windows either disappear or stay still).
Phone does still answer to .\fastboot devices with powershell cmd.
Could somebody put me out of my misery ?

duck from space said:
So I ended up in the brick wagon, basically doing this:
- Tencent CN version converted to WW by vendor.
- Rooted / uptaded from root folder
- Changed fingerprint to WW
- Decided things got buggy here and there, did a factory reset
-> Slot _b is unbootable / Bricked
I tried flashall_AFT.cmd from both WW and CN raw firmware, both by clicking and command prompt, nothing happens (windows either disappear or stay still).
Phone does still answer to .\fastboot devices with powershell cmd.
Could somebody put me out of my misery ?
Click to expand...
Click to collapse
This happens when we root the phone.. so basically when you factory reset, phone tries to boot to recovery and doesn't work.. this is a known issue.. just get stock boot image for your versionand flash it using fastboot...

Thanks a lot !

duck from space said:
Thanks a lot !
Click to expand...
Click to collapse
Did it work OK flashing boot stock?

Yes thank you, phone is alive again.
Wish I could use the raw firmware flash method though, ADB works but flashall_AFT.cmd does nothing (not seemingly frozen while doing its job, just nothing).

duck from space said:
Yes thank you, phone is alive again.
Wish I could use the raw firmware flash method though, ADB works but flashall_AFT.cmd does nothing (not seemingly frozen while doing its job, just nothing).
Click to expand...
Click to collapse
Does the cmd window pop up briefly and go again? If so, try removing or deleting the original zip from that folder, the one with the same name as the raw. Cmd gets confused /conflicts and crashes out...

Thanks for your help dude, yes that's what it does. I already done most known tricks to solve that issue to no avail. Might try on another PC now.

duck from space said:
Yes thank you, phone is alive again.
Wish I could use the raw firmware flash method though, ADB works but flashall_AFT.cmd does nothing (not seemingly frozen while doing its job, just nothing).
Click to expand...
Click to collapse
i have same problem too.

Experienced that as well at first, flashall_aft.cmd not doing at all. But I got it work by putting the extracted raw folder to the root of my C: in my pc.

ram4ufriends said:
This happens when we root the phone.. so basically when you factory reset, phone tries to boot to recovery and doesn't work.. this is a known issue.. just get stock boot image for your versionand flash it using fastboot...
Click to expand...
Click to collapse
if we flash stock boot image, are the phone still rooted..?

ghayathok said:
if we flash stock boot image, are the phone still rooted..?
Click to expand...
Click to collapse
No, you need to update Magisk after ota or flash root boot

I can't flash the stock boot image. It says my phone is locked. I tried relocking the bootloader and it gave me the Slot_b is unbootable message as well. Any advice?
---------- Post added at 09:12 PM ---------- Previous post was at 08:36 PM ----------
Schramx4 said:
I can't flash the stock boot image. It says my phone is locked. I tried relocking the bootloader and it gave me the Slot_b is unbootable message as well. Any advice?
Click to expand...
Click to collapse
Nevermind, I figured out I could switch the boot image over to Slot_a and that worked for me.

Just flash the raw full rom with bootloader by pc

How to do

Ajmi24 said:
How to do
Click to expand...
Click to collapse
Download the RAW firmware version you want, then;
'Extract the file on your PC. Boot the phone into fastboot mode (hold volume up then press and hold power button, Fastboot mode is the 1st screen you come across, the one with the options to Start, boot to recovery, etc...) connect to the side port and run "flashall_AFT.cmd" wait for it to finish and the phone will restart itself (it will take a number of minutes to complete, with the cmd window open all the time. If the cmd window only flashes up and closes down, then check the rest of the notes with this step).
NOTE: you need to remove or delete the original zip from the raw folder once extracted as it confuses the Flashall_AFT.cmd with the raw rom and zip having the same name. Also, it can help to extract to the root of C drive.'
Taken from my guide;
https://forum.xda-developers.com/rog-phone-2/how-to/guide-to-check-change-fingerprint-cn-to-t4002279

duck from space said:
Yes thank you, phone is alive again.
Wish I could use the raw firmware flash method though, ADB works but flashall_AFT.cmd does nothing (not seemingly frozen while doing its job, just nothing).
Click to expand...
Click to collapse

BOA TARDE AMIGOS
ESTOU TENDO O MESMO PROBLEMA APÓS INSTALAR O TWRP
APAGO O TECIDO ROM WW ANDROID 10
REINICIALIZE O SISTEMA E APENAS LIGA E DIZ ESTAS INFORMAÇÕES (Slot _b não pode ser inicializado) VOCÊ PODE ME AJUDAR ONDE EU ENCONTRAR A IMAGEM DE BOOT, POSSO ENTRAR EM FASTBOOTON SMATPHONE MAS NO PC DE DISPOSITIVO DESCONHECIDO

[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

Question FIX BOOT LOOP (HEEEELP)

It all started when I decided to unroot my phone. First I backed up my data. Second, I formatted the cell phone directly through its settings. So root was removed. So far, everything was fine. The cell phone turned on normally and I did the initial settings. After that I decided to lock the bootloader again. I put the phone in bootloader mode and gave the command to block (Fasboot flashing lock). A confirmation message appeared on my cell phone and I accepted it. After that the phone was like this... Blinking at boot. I can't enter fasboot or bootloader through the buttons.
Heelp please!!
See the problem (video link)

Diguinho76 said:
It all started when I decided to unroot my phone. First I backed up my data. Second, I formatted the cell phone directly through its settings. So root was removed. So far, everything was fine. The cell phone turned on normally and I did the initial settings. After that I decided to lock the bootloader again. I put the phone in bootloader mode and gave the command to block (Fasboot flashing lock). A confirmation message appeared on my cell phone and I accepted it. After that the phone was like this... Blinking at boot. I can't enter fasboot or bootloader through the buttons.
Heelp please!!
See the problem (video link)
Click to expand...
Click to collapse
Pretty sure factory resetting the phone from the settings doesn't remove root. You root by flashing a patched boot.img but the factory reset doesn't touch the boot partition at all. So you locked the bootloader and now the phone won't boot because the boot partition is not signed by the OEM. If you can't enter bootloader mode you only have two solution.
- Flashing in EDL mode through MSM tool. However, since this phone OnePlus requires an authorized account to flash through MSM tool. You can try requesting a remote session through the official support (probably they won't do it) or find someone on telegram or somewhere else who sells tokens for MSM tool.
- Shipping the phone to OnePlus for repair or going to a local repair center of your choice.

Did you complete unninstalled magisk or just have formatted?

TheNewHEROBRINE said:
Pretty sure factory resetting the phone from the settings doesn't remove root. You root by flashing a patched boot.img but the factory reset doesn't touch the boot partition at all. So you locked the bootloader and now the phone won't boot because the boot partition is not signed by the OEM. If you can't enter bootloader mode you only have two solution.
- Flashing in EDL mode through MSM tool. However, since this phone OnePlus requires an authorized account to flash through MSM tool. You can try requesting a remote session through the official support (probably they won't do it) or find someone on telegram or somewhere else who sells tokens for MSM tool.
- Shipping the phone to OnePlus for repair or going to a local repair center of your choice.
Click to expand...
Click to collapse
I can't believe I did this... All I wanted was to remove root and I forgot to do it through magisk. I just ****ed myself

Diguinho76 said:
I can't believe I did this... All I wanted was to remove root and I forgot to do it through magisk. I just ****ed myself
Click to expand...
Click to collapse
Just to confirm, holding vol + and vol - together at boot doesn't do anything?

Machad3x said:
Did you complete unninstalled magisk or just have formatted?
Click to expand...
Click to collapse
No.... just formatted
TheNewHEROBRINE said:
Just to confirm, holding vol + and vol - together at boot doesn't do anything?
Click to expand...
Click to collapse
Nop. nothing

Diguinho76 said:
Nop. nothing
Click to expand...
Click to collapse
I just remembered that with this phone you can't boot into EDL mode by holding the volume buttons like in the old days. To get into EDL mode you would need to disassemble the phone and short two pins and I immagine you don't want to do that at all. There are some special cables that can boot Qualcomm phones into EDL, although I don't know if they work with the OP10 Pro specifically.
I think your best option at the moment is to send it for repair to OnePlus or to whichever repair center you prefer.

Diguinho76 said:
No.... just formatted
Nop. nothing
Click to expand...
Click to collapse
When you can not boot to booloader (fastboot) or fastbootd you need a Services Center (for flash over edl with msm tool )

I got it. Payed 15$ and a guy from vietnam solved the problem for me.
FIXED!!! Flashed over edl.

Diguinho76 said:
I got it. Payed 15$ and a guy from vietnam solved the problem for me.
FIXED!!! Flashed over edl.
Click to expand...
Click to collapse
How did you put the phone into EDL?

TheNewHEROBRINE said:
How did you put the phone into EDL?
Click to expand...
Click to collapse
Vol+ Vol- Power Button ( All of them at the same time) plugged on the pc

Diguinho76 said:
Vol+ Vol- Power Button ( All of them at the same time) plugged on the pc
Click to expand...
Click to collapse
ah so it still works! I thought it wouldn't.

TheNewHEROBRINE said:
ah so it still works! I thought it wouldn't.
Click to expand...
Click to collapse
But now im trying to go to 2213... I flashed a 2213 payload.bin from fastboot enhance and its not booting the system. I can acess bootloader. Do you have any suggestion to change the region from bootloader now ?

Diguinho76 said:
But now im trying to go to 2213... I flashed a 2213 payload.bin from fastboot enhance and its not booting the system. I can acess bootloader. Do you have any suggestion to change the region from bootloader now ?
Click to expand...
Click to collapse
I would have installed the update through the settings. I don't think switching slot can help this time. The only thing I think you can do is extract the payload.bin with payload-dumper-go and flash the partitions manually through fastboot but this procedure doesn't have a 100% success rate. If you write me the partitions you extracted from the payload.bin I can write you the commands to do as I'm not used to the partition layout of the 10 Pro specifically.

TheNewHEROBRINE said:
Eu teria instalado a atualização através das configurações. Eu não acho que mudar de slot pode ajudar desta vez. A única coisa que acho que você pode fazer é extrair o payload.bin com payload-dumper-go e atualizar as partições manualmente por meio do fastboot, mas esse procedimento não tem uma taxa de sucesso de 100%. Se você me escrever as partições extraídas do payload.bin, posso escrever os comandos a serem feitos, pois não estou acostumado com o layout da partição do 10 Pro especificamente.
Click to expand...
Click to collapse
Ok. Ill try. But do you know any way to do this using fastboot enhance ?

Diguinho76 said:
Ok. Ill try. But do you know any way to do this using fastboot enhance ?
Click to expand...
Click to collapse
When you flashed the payload.bin in fastboot enhance were you in fastbootd or bootloader mode?

TheNewHEROBRINE said:
When you flashed the payload.bin in fastboot enhance were you in fastbootd or bootloader mode?
Click to expand...
Click to collapse
fastbootd

Diguinho76 said:
fastbootd
Click to expand...
Click to collapse
I don't know why it has failed then. Can you still boot to fastbootd? Or does it say something like userspace not bootable?

TheNewHEROBRINE said:
I don't know why it has failed then. Can you still boot to fastbootd? Or does it say something like userspace not bootable?
Click to expand...
Click to collapse
Yes, i can. I tried to flash the payload again but havent success

Diguinho76 said:
Yes, i can. I tried to flash the payload again but havent success
Click to expand...
Click to collapse
In the fastboot mode the touch is not working. so i cant format data etc. Only buttons working