Develop Bugs

Fastboot Failed (remote: Permission denied)

So, my phone is stuck in a bootloop. I'm not 100% sure how this happened, but I also can't access recovery. Every time I try, it goes to the ASUS screen, then boots back into bootloader. (this happened before I got soft bricked.) In other words, I can't use adb shell. So my only chance of unbricking is using fastboot, but it says permission is denied. Why would it tell me that?
EDIT: I got recovery working. I formatted my SD card, then injected CWM so I could reflash SuperSU.zip. Now I can get to recovery, but still not use adb shell. Storage doesn't show up on my PC via USB. When I try adb sideload, it says "error: device not found."

Water_Soup said:
So, my phone is stuck in a bootloop. I'm not 100% sure how this happened, but I also can't access recovery. Every time I try, it goes to the ASUS screen, then boots back into bootloader. (this happened before I got soft bricked.) In other words, I can't use adb shell. So my only chance of unbricking is using fastboot, but it says permission is denied. Why would it tell me that?
EDIT: I got recovery working. I formatted my SD card, then injected CWM so I could reflash SuperSU.zip. Now I can get to recovery, but still not use adb shell. Storage doesn't show up on my PC via USB. When I try adb sideload, it says "error: device not found."
Click to expand...
Click to collapse
Make sure you have the LATEST ADB drivers. Older drivers just don't seem to work...
What commands are you using in fastboot and from what firmware are you trying to flash from?
If you have the latest firmware it seems you need to flash ALL partitions to go back.
Just make sure your downloads are good and don't flash the wrong image on the wrong partition. Copy and paste can be your enemy here if you aren't careful...

ultramag69 said:
Make sure you have the LATEST ADB drivers. Older drivers just don't seem to work...
What commands are you using in fastboot and from what firmware are you trying to flash from?
If you have the latest firmware it seems you need to flash ALL partitions to go back.
Just make sure your downloads are good and don't flash the wrong image on the wrong partition. Copy and paste can be your enemy here if you aren't careful...
Click to expand...
Click to collapse
I figured it out. I flashed stock FW from a .zip. That got me out of the bootloop. As for commands not working, I found an alternate method to unlock the bootloader, and that seemed to be my problem.

Water_Soup said:
I figured it out. I flashed stock FW from a .zip. That got me out of the bootloop. As for commands not working, I found an alternate method to unlock the bootloader, and that seemed to be my problem.
Click to expand...
Click to collapse
Cool, as long as you got to your destination, the journey doesn't matter...
(and yes, I found that in a fortune cookie...)

Having the same problem, i have the
C:\adb>fastboot flash fastboot droidboot.img
target reported max download size of 536870912 bytes
sending 'fastboot' (14826 KB)...
How is that alternative method to unlock the bootloader?
Every time i try to go into recovery mode it doesnt open :/
OKAY [ 0.661s]
writing 'fastboot'...
FAILED (remote: Permission denied
)
finished. total time: 0.817s

Disable your lockscreen password first in setting, set to NONE
Sent from M919V Galaxy S4 via XDA Premium HD app.

Thanks!
madman604 said:
Disable your lockscreen password first in setting, set to NONE
Sent from M919V Galaxy S4 via XDA Premium HD app.
Click to expand...
Click to collapse
THAAAANKS! it works !! :laugh::fingers-crossed:

EchoeSD said:
THAAAANKS! it works !! :laugh::fingers-crossed:
Click to expand...
Click to collapse
you're welcome.
i found the solution in another obscure forum after a few days of Google-Fu.
on a sadder note. my screen gave up to the vertical line problem and Asus denied my warranty claim for being "Rooted". i unrooted, but they still know lol.
whatever tho. this phone has been nothing but problems in the 6 months i've owned it. back to Samsung whenever they ship that piece of junk back to me.

I get same message...Failed (remote: Permission denied) but the phone has bricked and I cannot get into the phone to disable the lockscreen.
Any ideas for a work around?
Also, I can access fastboot commands but not adb
and the phone will not enter into recovery on it's own.

Same issue
bricklayer67 said:
I get same message...Failed (remote: Permission denied) but the phone has bricked and I cannot get into the phone to disable the lockscreen.
Any ideas for a work around?
Also, I can access fastboot commands but not adb
and the phone will not enter into recovery on it's own.
Click to expand...
Click to collapse
Yeah, I have the same problem, so it's not just you!

who ever getting issue with remote permission denied or unable to flash via adb side load. down load raw firmware. extract it. place files in adb fastboot folder. open command windows here. and run mannual commands to install firmware

How do I get past this "permission denied" issue of fastboot ? Disabling the lockscreen surely was not the key to my problem.
I have also always allowed USB connections from the machine I am using for this fastbooting thing. Thank you!
LE: it was a matter of linux permissions . Just added +x and worked. Now I have advanced to the <Waiting for any device> error

kelogs said:
How do I get past this "permission denied" issue of fastboot ? Disabling the lockscreen surely was not the key to my problem.
I have also always allowed USB connections from the machine I am using for this fastbooting thing. Thank you!
Click to expand...
Click to collapse
multiple things you can try... unlocking bootloader if locked. flash dnx, ifwi , splash screen, boot , droidboot images. then go to recovery and factory data reset. then clear cache partition. and sideload firmware via adb

Water_Soup said:
So, my phone is stuck in a bootloop. I'm not 100% sure how this happened, but I also can't access recovery. Every time I try, it goes to the ASUS screen, then boots back into bootloader. (this happened before I got soft bricked.) In other words, I can't use adb shell. So my only chance of unbricking is using fastboot, but it says permission is denied. Why would it tell me that?
EDIT: I got recovery working. I formatted my SD card, then injected CWM so I could reflash SuperSU.zip. Now I can get to recovery, but still not use adb shell. Storage doesn't show up on my PC via USB. When I try adb sideload, it says "error: device not found."
Click to expand...
Click to collapse
Otra forma para solucionarlo en caso de que alguien mas tenga el mismo problema, es consiguiendo la imagen del TWRP, luego de esto entran en modo fastboot y escriben "fastboot boot TWRP.img", esto les servira para entrar al recovery, despues de ahi pasan la imagen del twrp a el celular, flashean la imagen en la particion de recovery y listo, no tendran problema con eso ya.

[Flashing] OTA / Fastboot ROM .tgz Xiaomi Redmi Note 8 Pro

Need flash or unbricking your Xiaomi redmi note 8 pro? Maybe this your first solution
We all know that currently the best phone in the family NOTE on Xiaomi is the Note 8 series, and this phone has been launched almost to all countries with MIUI 10 Android 9.0 Pie, and will soon be updated to a higher version of MIUI 11 Android 10 Q. For this reason this thread might be very useful for anyone who wants to solve various problems after making modifications, such as failed on Root rooting, Flashing TWRP recovery or new ROM and others.
Attention! Before you download the firmware that is right for you, please get to know your phone via fastboot mode, because the type of firmware is distinguished through the codename or region. Xiaomi Redmi note 8 Standart edition or Pro? From china, india or Global?
Steps:
- Download adb driver and instal to your computer
- Download Adb Fastboot tools and unpack on windows OS computer
- Open Adb Fastboot tools folder
- Search cmd.exe on your computer and copy to Adb fastboot tools folder
- Double click to run cmd.exe
- Now, Turn off your phone
- Press "Volume down + Power button" simultaneously into Fastboot mode
- Connect the USB cable
- Now, Back to Adb fastboot folder
- Run cmd.exe
- Type command "fastboot devices" press enter
- Type command " fastboot getvar product" press enter. here you will see the version of your device.
codename:
begonia_ru = Russia
begonia _id = Indonesia
begonia_in = India
begonia_cn = China
begonia_eea = European
begonia = China / Global
Download all official firmware OTA updates or Fastboot rom from https://boycracked.com/2019/10/25/official-xiaomi-redmi-note-8-pro-begonia-ota-fastboot-stock-rom/
How to flash Xiaomi Redmi Note 8 pro by problems.
- Can'boot to home screen but you can still enter recovery mode. Then download the firmware update.zip to install it via recovery mode.
- Lost recovery, bootloop or stuck on logo. Download .tgz fastboot rom and than flash via adb or miFlash. Read tutorial from https://boycracked.com/2017/08/16/3-safe-way-to-fix-bootloop-xiaomi-mobile-devices-with-safe/
- Softbrick, bootloop hang logo, lost recovery, blink red light, Test point, flash via miflash https://boycracked.com/2017/08/14/installing-xiaomi-firmware-using-miflash-tool/ , Spflashtool https://boycracked.com/2015/06/07/how-to-flashing-mediatek-rom-firmware-using-sp-flashtool/ or Mediatekdownloadertools https://boycracked.com/2019/03/28/m...rade-procedure-using-multiport-download-tool/
That's all from me, and thanks
Sent from my Redmi Note 8 Pro using Tapatalk

kujangsbj said:
Need flash or unbricking your Xiaomi redmi note 8 pro? Maybe this your first solution
...
- Softbrick, bootloop hang logo, lost recovery, blink red light, Test point, flash via miflash https://boycracked.com/2017/08/14/installing-xiaomi-firmware-using-miflash-tool/ , Spflashtool https://boycracked.com/2015/06/07/how-to-flashing-mediatek-rom-firmware-using-sp-flashtool/ or Mediatekdownloadertools https://boycracked.com/2019/03/28/m...rade-procedure-using-multiport-download-tool/
That's all from me, and thanks
Click to expand...
Click to collapse
Hey.
Have you tried what you suggest on Redmi Note 8 pro?
You talk about testpoint flash via miflash. How to get to testpoint mode on RN8p?
Doesn't SP flash tool give an error while trying to flash?

if you want to make that make a tutorial with proof and screenshots...

Unfortunately it doesn't work to hard bricked devices! Only if there is a solution with patched rom that can bypass authorization.
The only solution till now is to find an authorized account and to flash it.

Hello guys,.
I have redmi note 8 pro global version with: miui 10.4.5
PGGEUXM.
My question is, can i flash indonesia version V10.4.2.0.PGGIDXM fastboot flash on locked bootloader,without unlock him, or must unlock install twrp recovery and then??
I want to change my global rom, if it is possible with this one, because the stupid Google dialer make me crazy

galev_90 said:
Hello guys,.
I have redmi note 8 pro global version with: miui 10.4.5
PGGEUXM.
My question is, can i flash indonesia version V10.4.2.0.PGGIDXM fastboot flash on locked bootloader,without unlock him, or must unlock install twrp recovery and then??
I want to change my global rom, if it is possible with this one, because the stupid Google dialer make me crazy
Click to expand...
Click to collapse
did you success installing Indonesia version ?? I wanna do the same as you . please help me too.

kujangsbj said:
...
Download all official firmware OTA updates or Fastboot rom from https://boycracked.com/2019/10/25/official-xiaomi-redmi-note-8-pro-begonia-ota-fastboot-stock-rom/
That's all from me, and thanks ...
Click to expand...
Click to collapse
Why would I download "all official firmware" from a website called "Boycracked.com" when real official fastboot roms are openly available on the manufacturers website and has no download caps nor is it full of advertising. FYI I'm sure you know that your site blocks people who have ad blocking on.
This whole post smells fishy like it's just for site promotion and revenue generation.

I read in some forum that mi flash tool supports only devices with Snapdragon chipset, however I was able to successfully downgrade(11.0.4 to 11.0.3) my rn8pro using the same tool... Please clarify

For Official Rom : https://xiaomifirmware.com/roms/miui-roms-redmi-note-8-pro-begonia/

V12.0.2.0.QGGINXM where can i found fastboot img for this version the website doesn't have this one

bonsoir, j'ai eu un problème de bootloop après la récupération flash sur rn8pro. Comme je ne peux pas réinstaller miui 12, j'ai téléchargé une rom pour rn8pro, décompressé, extrait la récupération d'origine et je la flash avec l'outil de plate-forme adb en mode fastboot "fastboot flash recovery.img" puis "fastboot reboot" et le redémarrage a eu lieu instantanément . Ici, je suis très content.

my adb-fastboot doesn't recognize my smartphone

Hey guys, I was trying to root my smartphone using magisk, so I downloaded the stock rom and got the boot.img file for magisk to modify, passed the modified file to the computer and put my device in fastboot mode, but adb-fastboot didn't recognize my device even though I installed the google drivers, so I decided to install the manufacturer's own drivers, but it didn't work, I went to several forums and nothing, so please help!

Filkiro said:
Hey guys, I was trying to root my smartphone using magisk, so I downloaded the stock rom and got the boot.img file for magisk to modify, passed the modified file to the computer and put my device in fastboot mode, but adb-fastboot didn't recognize my device even though I installed the google drivers, so I decided to install the manufacturer's own drivers, but it didn't work, I went to several forums and nothing, so please help!
Click to expand...
Click to collapse
Does it show in Device Manager?
Install Moto USB Drivers

sd_shadow said:
Does it show in Device Manager?
Click to expand...
Click to collapse
Yes, when i go into fastboot mode, it pops up "Android adb interface"

Filkiro said:
Yes, when i go into fastboot mode, it pops up "Android adb interface"
Click to expand...
Click to collapse
seems to be a reoccuring problem to us. steps as show:​​1. press the windows key + r at the same time to open the "run" window.​
2. type "devmgmt.msc" and press enter. it should give a device management window in a few seconds.​
3. if the phone is in mtp mode, it will appear under portable devices/mobile devices. right click that and select "update drivers." click on "search drivers in my computer" and then select "allow me to choose from a available drivers list from my computer." scroll down until you see "mtp device" and double click on it. just click on "proceed". if it fails, try it again but with different drivers.​
make sure to have usb depuration on and reboot to fastboot yadda yada badlaldaaa
then update fastboot drivers "device may be on android phone "'''make sure to install motorola drivers or built in fastboot drivers''''' and then proceed

no matter how much you manage to install drivers you will not be able to root your moto e6 play, (BOOTLOADER IMPOSSIBLE TO UNLOCK UNTIL THE MOMENT)
and do not come to say that it is due to drivers or because we are using an incorrect method, etc.
fastboot oem get_unlock_data not working
fastboot oem unlock does not work
fatboot flashing unlock and unlock_critical either
and it does not appear as waiting for device
appears as remote: unknown command
so it is a problem of the bootloader and not the user

G.Kart said:
não importa o quanto você consiga instalar os drivers, você não conseguirá fazer o root no seu moto e6 play, (BOOTLOADER IMPOSSÍVEL DE DESBLOQUEAR ATÉ O MOMENTO)
e não quero dizer que é devido aos drivers ou porque estamos usando um método incorreto, etc.
fastboot oem get_unlock_data não funciona
fastboot oem unlock não funciona
fatboot piscando desbloqueio e desbloqueio_crítico também
e não aparece como aguardando dispositivo
aparece como remoto: comando desconhecido
então é um problema do bootloader e não do usuário
Click to expand...
Click to collapse
Yes, I searched many forums and it really is practically impossible to unlock the bootloader, but I have a question, is it possible to root using the sp flash tool?

Filkiro said:
Yes, I searched many forums and it really is practically impossible to unlock the bootloader, but I have a question, is it possible to root using the sp flash tool?
Click to expand...
Click to collapse
no, AVB2.0 doesn't allow it, unless I manage to get motorola's private key (.pem) to be able to sign a patched boot.img and even GSIs

Question Bricked device?

I tried to flash Evolution X 5.9. I came from the latest Xiaomi.eu stable (12.5.4). Followed the installing instructions (flash via twrp/ format data), but after reboot, i got a "no command" error message. I then tried to flash the original F3 EEA Fastboot Rom downloaded here: https://c.mi.com/oc/miuidownload/detail?guide=2 , unzipped it twice, but when i tried to flash the rom, i got the error message "can not find file flash_all.bat. I can only enter fastboot now. I have no idea what i did wrong. I would be grateful for any help!
Edit: I'm getting another error now: "error:Writing 'crclist'"

sycomantis said:
I tried to flash Evolution X 5.9. I came from the latest Xiaomi.eu stable (12.5.4). Followed the installing instructions (flash via twrp/ format data), but after reboot, i got a "no command" error message. I then tried to flash the original F3 EEA Fastboot Rom downloaded here: https://c.mi.com/oc/miuidownload/detail?guide=2 , unzipped it twice, but when i tried to flash the rom, i got the error message "can not find file flash_all.bat. I can only enter fastboot now. I have no idea what i did wrong. I would be grateful for any help!
Edit: I'm getting another error now: "error:Writing 'crclist'"
Click to expand...
Click to collapse
Don't go any further, it's really easy to fix, I had the same issue yesterday.
Just try this:
- Download the latest TWRP image
- Launch it from RAM: fastboot boot twrp.img
- Now, try to flash whatever you need to!
- Reboot, and the motherboard will be put out of fastboot.
Good luck!

facuarmo said:
Don't go any further, it's really simple to fix, I had the same issue yesterday.
Just try this:
- Download the latest TWRP image
- Launch it from RAM: fastboot boot twrp.img
- Now, try to flash whatever you need to!
- Reboot, and the motherboard will be put out of fastboot.
Good luck!
Click to expand...
Click to collapse
what do you mean by "Launch it from RAM" ? and which TWRP version should I downlaod? I have the "RUN_TWRP Toolkit" which lets me enter TWRP via fastboot and windows10, is that sufficient? Thx!
The thing is, that I cant copy files to the internal storage, thats why i cannot flash a rom via that RUN TWRP Toolkit.

I downloaded the latest [unofficial] TWRP Version 3.5.2_11-0, entered TWRP via cmd, but i do not know how to flash a ROW now, since i can not copy a rom.zip to the internal storage.

I'm in a similar situation. Tried out a few roms and wanted flash back to stock. Something went wrong and now TWRP is gone and I can only boot into fastboot and stock recovery. I can fastboot TWRP, but don't know how to get a rom accessible. I tried MiFlash but that just tells me "flash done" after 5 seconds without actually doing anything. Tried just executing flash_all.bat, but it comes down to this error message:
$fastboot -s devicename getvar product 2>&1 | findstr /r /c:"^product: *alioth" || echo Missmatching image and device
Click to expand...
Click to collapse
I'm trying to flash MiUI 12.5.1 on a POCO F3, so I don't really understand. Any help would be appreciated.

I was in similar situation. Twice.
Solution: fastboot rom.
I successed with Syberia.
FASTBOOT Roms of Syberia are here:
SyberiaOS - Browse /alioth/fastboot at SourceForge.net
SyberiaOS - Browse /alioth/fastboot at SourceForge.net
Syberia Project (aka Syberia OS) is a custom ROM for many devices that implements various features. This project was designed by our "Syberia Team"…
sourceforge.net
Unpack it.
Enter fastboot mode on phone.
Run install.bat. Wait. Device reboots to system.

That worked, thank you very much! The only other option I found was to remove part of the flash_all.bat, but I didn't really feel comfortable removing something I don't quite unterstand.

ptr21 said:
I was in similar situation. Twice.
Solution: fastboot rom.
I successed with Syberia.
FASTBOOT Roms of Syberia are here:
SyberiaOS - Browse /alioth/fastboot at SourceForge.net
SyberiaOS - Browse /alioth/fastboot at SourceForge.net
Syberia Project (aka Syberia OS) is a custom ROM for many devices that implements various features. This project was designed by our "Syberia Team"…
sourceforge.net
Unpack it.
Enter fastboot mode on phone.
Run install.bat. Wait. Device reboots to system.
Click to expand...
Click to collapse
Thank you so much!! It worked

ptr21 said:
I was in similar situation. Twice.
Solution: fastboot rom.
I successed with Syberia.
FASTBOOT Roms of Syberia are here:
SyberiaOS - Browse /alioth/fastboot at SourceForge.net
SyberiaOS - Browse /alioth/fastboot at SourceForge.net
Syberia Project (aka Syberia OS) is a custom ROM for many devices that implements various features. This project was designed by our "Syberia Team"…
sourceforge.net
Unpack it.
Enter fastboot mode on phone.
Run install.bat. Wait. Device reboots to system.
Click to expand...
Click to collapse
Hi,
excuse me but I don't know English.
My Poco F3 crashes on MIUI, can I get into Fastboot or start TWRP from Windows powershell.
I downloaded the syberia_alioth-v4.7-20210715-1557-OFFICIAL-fastboot but I didn't understand how to proceed.
Could you please explain me step by step what to do?
Thank you.

pegasoc said:
Hi,
excuse me but I don't know English.
My Poco F3 crashes on MIUI, can I get into Fastboot or start TWRP from Windows powershell.
I downloaded the syberia_alioth-v4.7-20210715-1557-OFFICIAL-fastboot but I didn't understand how to proceed.
Could you please explain me step by step what to do?
Thank you.
Click to expand...
Click to collapse
Unzip syberia fastboot rom to your computer.
Enter fastboot mode on your phone (power+ volume down buttons)
Connect your phone to computer via USB
In unzipped folder of Syberia fastboot rom you find windows command : install ...... .bat
Run it. It will install Syberia rom.
Dont worry if the errors are shown, iust wait, it will reboot to Syberia rom.

ptr21 said:
Decomprimi la rom di syberia fastboot sul tuo computer.
Accedi alla modalità di avvio rapido sul telefono (pulsanti di accensione e riduzione del volume)
Collega il telefono al computer tramite USB
Nella cartella decompressa della rom Syberia fastboot trovi il comando di Windows: install ...... .bat
Eseguirlo. Installerà la rom Syberia.
Non preoccuparti se vengono mostrati gli errori, aspetta, si riavvierà su Syberia rom.
Click to expand...
Click to collapse
WOW WOW WOW WOW!!! Sei un salvavita. Grazie molte!!!
Ciò che è ancora meglio è che dopo aver bloccato POCO F3 stavo solo cercando di installare syberia_alioth-v4.7-20210723-1108-OFFICIAL.
Presumo che Syberia fastboot non sia aggiornato come syberia_alioth-v4.7-20210723-1108-OFFICIAL, per aggiornare devo installare TWRP e poi
Riavvia in TWRP
Vai su "Installa" -> scegli ROM.zipper (assicurati di aver selezionato "Inietta TWRP dopo l'installazione")
Riavvia -> ripristino
Vai su "Installa" -> scegli Gapps.zipper (Magisk, Gapps-Addons opzionali ecc.) (assicurati che NON SELEZIONATO "Inietta TWRP dopo l'installazione")
Riavvia -> Sistema
Destra?

General Nokia G21 development

Hi all!
DEVELOPMENT IN PROGRESS​
This thread is not to talk about HMD/Nokia and its policies.
The goal is to extract vendor files to build an AOSP ROM. Also, to unlock bootloader and root the device for developing purposes.
At the moment we know that:
-Nokia doesn't includes commands like "fastboot oem unlock" or "fastboot flashing unlock" in their bootloader (but includes oem unlock in developer settings).
-Without unlocked Bootloader we cannot flash custom recovery or root our device.
-adb shell cannot elevate privileges without root. Then, we cannot extract vendor files (completely).
-Android 11 patch is in february. March patch not released.
-Device codename is SCP_sprout, model TA-1418.
-We must be cautious with the information we publish.
Testings:
-Extracted vendor partially as img.
-Still searching for vulnerabilities to gain temporary root access.
That's all, for the moment.
I have no much time to spend in it. Please, be patient.

I've created 3 new repositories in github for new data when available
device_nokia_SCP_sprout (to upload device tree)
rom_dump_nokiaG21_SCP_sprout (to upload whole stock rom img)
vendor_files_nokiaG21 (to upload vendor files (blobs)). This repo is temporary. The final repo would be proprietary_vendor_nokia_SCP_sprout

I think I've found your repos on github, but they're empty.. I'm trying to figure out of how re-enable the standard FM app (It's probably disabled because I'm in Italy where's there's a silly law prohibiting FM devices without DAB support)

Hi. Can anyone help me updating to A12 using adb sideload?
The problem is whenever I type adb reboot recovery nothing happens
If i try adb reboot fastboot i get into fastboot mode and then type fastboot reboot recovery
I get into recovery but it does not have any option to apply update from adb . The only 3 option i get is 1. Reboot bootloader 2. Reboot to fastboot mode and 3. Power off

arpankgec said:
Hi. Can anyone help me updating to A12 using adb sideload?
The problem is whenever I type adb reboot recovery nothing happens
If i try adb reboot fastboot i get into fastboot mode and then type fastboot reboot recovery
I get into recovery but it does not have any option to apply update from adb . The only 3 option i get is 1. Reboot bootloader 2. Reboot to fastboot mode and 3. Power off
Click to expand...
Click to collapse
From what I know, then maybe I'm wrong, Nokia from a security patch of 2018 made it ALMOST impossible to unlock the bootloader and enter recovery

In Italy with the Android 12 update now exist a recovery and a fastbootd (not fastboot) for Nokia G21

VinaceAle2807 said:
In Italy with the Android 12 update now exist a recovery and a fastbootd (not fastboot) for Nokia G21
Click to expand...
Click to collapse
Fastbootd is useless if the bootloader is locked. How about the recovery mode? Do you have useful options inside of recovery?

singhnsk said:
Fastbootd è inutile se il bootloader è bloccato. Che ne dici della modalità di recupero? Hai opzioni utili all'interno del recupero?
Click to expand...
Click to collapse
If you want to go to recovery you have to enter FastbootD with this command: "fastboot reboot fastboot".
In FastbootD, enter recovery.
The recovery is empty, there is only rebooting the system, enter fastboot and shut down.
(Sorry for the bad English)

singhnsk said:
Fastbootd è inutile se il bootloader è bloccato. Che ne dici della modalità di recupero? Hai opzioni utili all'interno del recupero?
Click to expand...
Click to collapse
But I think that with the Android 13 update (I don't know when it is) there will be more things in recovery and more commands for the classic fastboot mode.

arpankgec said:
Hi. Can anyone help me updating to A12 using adb sideload?
The problem is whenever I type adb reboot recovery nothing happens
If i try adb reboot fastboot i get into fastboot mode and then type fastboot reboot recovery
I get into recovery but it does not have any option to apply update from adb . The only 3 option i get is 1. Reboot bootloader 2. Reboot to fastboot mode and 3. Power off
Click to expand...
Click to collapse
Sorry but I can' t help you, try in other forum

arpankgec said:
Hi. Can anyone help me updating to A12 using adb sideload?
The problem is whenever I type adb reboot recovery nothing happens
If i try adb reboot fastboot i get into fastboot mode and then type fastboot reboot recovery
I get into recovery but it does not have any option to apply update from adb . The only 3 option i get is 1. Reboot bootloader 2. Reboot to fastboot mode and 3. Power off
Click to expand...
Click to collapse
Not Possible with this update.
Use MTK Client to unlock bootloader.

VinaceAle2807 said:
But I think that with the Android 13 update (I don't know when it is) there will be more things in recovery and more commands for the classic fastboot mode.
Click to expand...
Click to collapse
They have removed the recovery options on purpose. Hence, they will not add them back again