Hello,
i have successfully unlocked bootloader with the official way. I can flash everything twrp, cm rom, supersu...no problems.. but as i saw in 2 apps of playstore for device's info. These two said that bootloader is unknown... So i tried via cmd in order to see whats really happening and i took these results with this command "fastboot oem device-info" :
C:\adb>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.007s]
finished. total time: 0.007s
Anyone knows why this confusion happends?
UPDATE: By pressing volume up + power button i can't boot on bootloader anymore, either from advanced reboot of cm. It's a think that does not matter to me, but i would like to know the reason.
Hi
Im trying to unlock the bootloader but I get error mesasge
C:\Users\z400>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_enabled: 0
(bootloader) exec_console_unconsole: 0
OKAY [ 0.019s]
finished. total time: 0.020s
C:\Users\z400>fastboot oem unlock
...
FAILED (remote: oem unlock is disabled)
finished. total time: 0.010s
In dev option I dont see the option to enable OEM unlock
android version 5.1.1
oxygen 2.1.4
build ONE E1005_14_160119
thanks in advance
Try updating the device first. I unlocked mine while it was on 2.2.2 and the Unlock bootloader option was there in the Developer settings.
thanks I updated to 3.x.x and the option was there
Hello guys can you help me, i cant unlock the bootloader of HTC Desire 10 PRO cos the command "fastboot flash unlocktoken Unlock_code.bin" is not working getting this message below again n again. i have checked usb debugging & OEM Unlock options too in Developer options too. i really don't understand why is this happening. Also there is not much help from this device available here on XDA or other sites too.
M:\HTCRoot>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.042s]
writing 'unlocktoken'...
(bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/platform/mtk-msdc.0/11230000.msdc
(bootloader) [KillSwitch] Last Byte is 0X01, enable unlock
FAILED (remote: UnlockToken Verify Fail!!)
finished. total time: 0.132s
need help guys..
here is more info if required.... guys plz help
C:\Users\Desktop\platform-tools>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_a56dj_pro_dtwl
(bootloader) version: 1.0
(bootloader) max-download-size: 1596000000
(bootloader) serialno: LC73XZ9*****
(bootloader) current-slot:
(bootloader) imei: 35**520********
(bootloader) version-main: 1.18.400.22
(bootloader) boot-mode: download
(bootloader) version-baseband: READ version-baseband ERROR
(bootloader) version-bootloader: 1.01.0000(8804eff8)
(bootloader) mid: 2PYA10000
(bootloader) cid: HTC__060
all:
finished. total time: 0.037s
Same error here. Tried Desire* and other supported devices from the HTCdev site.
Kindly help which device to choose from dev site.
D:\HTC Desire 10 PRO\ADB-Windows> fastboot flash unlocktoken Unlock_code.bin
target reported max download size of 1602400000 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 1.009s]
writing 'unlocktoken'...
(bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/platform/mtk-msdc.0/11230000.msdc
(bootloader) [KillSwitch] Last Byte is 0X01, enable unlock
FAILED (remote: UnlockToken Verify Fail!!)
finished. total time: 1.033s
princepavs said:
Hello guys can you help me, i cant unlock the bootloader of HTC Desire 10 PRO cos the command "fastboot flash unlocktoken Unlock_code.bin" is not working getting this message below again n again. i have checked usb debugging & OEM Unlock options too in Developer options too. i really don't understand why is this happening. Also there is not much help from this device available here on XDA or other sites too.
M:\HTCRoot>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.042s]
writing 'unlocktoken'...
(bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/platform/mtk-msdc.0/11230000.msdc
(bootloader) [KillSwitch] Last Byte is 0X01, enable unlock
FAILED (remote: UnlockToken Verify Fail!!)
finished. total time: 0.132s
need help guys..
Click to expand...
Click to collapse
Are you still able to unlock? I have the same issue too. Stuck here
I don't know if this one helps you too but I was unable to unlock bootloader from bootloader mode and I tried it from download mode. It was successfully done with fastboot.... command. Root? I used Magisk. only problem is it takes 5 minutes to start up every time I reboot.
carlochiefsg said:
Are you still able to unlock? I have the same issue too. Stuck here
Click to expand...
Click to collapse
naaa never worked.. so gave this phone to my dad as he's a normal android user... must say MTK processors r the worst
princepavs said:
naaa never worked.. so gave this phone to my dad as he's a normal android user... must say MTK processors r the worst
Click to expand...
Click to collapse
to be exact HTC MTK processor is the worst, HTC lied about all HTC phones boot loader is unlockable.... BS!
My One Plus X is stuck in Oneplus logo I haven't rooted my phone, now i can only enter in fastboot mode. unable to enter in recovery mode and system.
when i try to fastboot oem unlock failed it says unable to unlock, device is locked.
how to unlock oem device through fastboot mode. or any way to solve this issue ?
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_enabled: 0
(bootloader) exec_console_unconsole: 0
OKAY [ 0.008s]
finished. total time: 0.009s
Edit : Sorry, I forgot to answer the question : No...
**********************
Was TWRP installed before ?
Explain what you did just before that !
But seeing what you have, I bet flashing the official recovery won't work.
Flashing stock recovery
1) Download stock Recovery OnePlus (there are one for MM version and one for previous version. Depends on question one I asked !)
2) Copy the recovery in the adb folder
3) Start a new prompt command from the folder adb
4) Put the smartphone in fastboot mode (power off the smartphone , and click volume up + power)
5) Put the command "fastboot device" for be sure computer can see the smartphone
6) Put the command fastboot "flash recovery name-recovery.img"
But you bet shot will be to run the Mega unbrick guide I guess...
aiwin007 said:
My One Plus X is stuck in Oneplus logo I haven't rooted my phone, now i can only enter in fastboot mode. unable to enter in recovery mode and system.
when i try to fastboot oem unlock failed it says unable to unlock, device is locked.
how to unlock oem device through fastboot mode. or any way to solve this issue ?
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_enabled: 0
(bootloader) exec_console_unconsole: 0
OKAY [ 0.008s]
finished. total time: 0.009s
Click to expand...
Click to collapse
It's softbricked. Happened to me awhile ago, i've resolved it with the unbrick tools.
*Your bootloader is locked and can't do oem unlock, can't boot to twrp/system→ So there's no way to flash anything.
You need to run the unbrick tools. Head to the mega unbrick guide for more details.
Mega Unbrick's Thread
Notes:
Link for the recovery tool in OP is dead, so use this one instead
Recovery Tool
And download "Qualcomm driver" from OP.
I'm attempting to downgrade from Android 11 to Android 10 for a plethora of reasons. These are the instructions I am following:
Gordstor instructions
I have done the following:
I enabled "OEM Unlocking"
I unlocked the bootloader.
I enabled "USB debugging".
I found my Software Channel and I believe it is "RetUS".
I determined that my phone does not use fastbootd.
I installed LMSA on my Windows 10 PC.
I downloaded what I believe is the correct Android 10 firmware, "XT2041-4_SOFIA_RETUS_10_QPMS30.80-109-5_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml"
I renamed it "SOFIA_RETAIL_RPMS31.Q1_54_13_7_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml"
I moved it to "C:\ProgramData\RSA\Download\RomFiles\"
I then set my Moto G Power (2020) in fastboot mode and plugged it into my PC via USB C cable.
From within LMSA, I rescued my moto, which I was hoping would be my last step.
LMSA attempts to push image to phone, but only gets to 32%. at that point,, I get the error message: "FASTBOOT FLASH SINGLE PARTITION. Flash failed. Please tray again."
Below is output from fastboot getvar all and fastboot getvar is-userspace.
Any help greatly appreciated.
fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-sofia_retail-2c4117ea2d6-211002
(bootloader) product: sofia
(bootloader) board: sofia
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: NA
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB MICRON S0J9K8 RV=08 PV=10 FV=0000000000000004
(bootloader) ufs: N/A
(bootloader) ram: 4GB MICRON LP4 DIE=16Gb M5-M8=FF 04 10 10
(bootloader) cpu: SM_NICOBAR 1.0
(bootloader) serialno: ZY227QFDWG
(bootloader) cid: 0x0032
(bootloader) channelid: 0x8d
(bootloader) uid: 1C00A4C4
(bootloader) securestate: oem_locked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 805263360
(bootloader) reason: Volume down key pressed
(bootloader) imei: 357244102645879
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 08-26-2020
(bootloader) sku: XT2041-4
(bootloader) carrier_sku: XT2041-4
(bootloader) battid: SB18C57585
(bootloader) battery-voltage: 3972
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) poweroffalarm: 0
(bootloader) ro.carrier: retus
(bootloader) ro.build.fingerprint[0]: motorola/sofia_retail/sofia:11/RPM
(bootloader) ro.build.fingerprint[1]: S31.Q1-54-13-7/57bd6:user/release-
(bootloader) ro.build.fingerprint[2]: keys
(bootloader) ro.build.version.qcom: LA.UM.9.11.r1-02100-NICOBAR.0
(bootloader) version-baseband: M6125_43.45.03.49R SOFIA_NA_CUST
(bootloader) kernel.version[0]: Linux version 4.14.180-perf+ ([email protected]
(bootloader) kernel.version[1]: roid-build) (clang version 10.0.7 for An
(bootloader) kernel.version[2]: droid NDK, GNU ld (binutils-2.27-bd24d23
(bootloader) kernel.version[3]: f) 2.27.0.20170315) #1 SMP PREEMPT Sat O
(bootloader) kernel.version[4]: ct 2 10:30:41 CDT 2021
(bootloader) git:xbl: MBM-3.0-sofia_retail-1186df2c3-211002
(bootloader) git:xbl_config: MBM-3.0-sofia_retail-1186df2c3-211002
(bootloader) git:rpm: MBM-3.0-sofia_retail-2579863-211002
(bootloader) git:tz: MBM-3.0-sofia_retail-da525ab0-211002
(bootloader) git:hyp: MBM-3.0-sofia_retail-da525ab0-211002
(bootloader) git:devcfg: MBM-3.0-sofia_retail-da525ab0-211002
(bootloader) git:cmnlib: MBM-3.0-sofia_retail-da525ab0-211002
(bootloader) git:cmnlib64: MBM-3.0-sofia_retail-da525ab0-211002
(bootloader) git:keymaster: MBM-3.0-sofia_retail-cf01af6-211002
(bootloader) gitrov: MBM-3.0-sofia_retail-da525ab0-211002
(bootloader) git:abl: MBM-3.0-sofia_retail-2c4117ea2d6-211002
(bootloader) git:qupfw: MBM-3.0-sofia_retail-319dab9-211002
(bootloader) git:uefisecapp: MBM-3.0-sofia_retail-da525ab0-211002
(bootloader) frp-state: protected (77)
(bootloader) current-slot: b
(bootloader) running-bl-slot: _b/_b
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: yes
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 6
(bootloader) logical-block-size: 0x200
(bootloader) erase-block-size: 0x200
(bootloader) is-userspace: no
(bootloader) pcb-part-no: SB28C55260
(bootloader) primary-display: tm_ft8756_fhd_vid
(bootloader) secondary-display:
fastboot getvar is-userspace
is-userspace: no
Finished. Total time: 0.000s
Click to expand...
Click to collapse
Note that if I download the latest stock firmware via LMSA, I am able to push it to the phone via the rescue operation. This is good news, but does not help me resolve my issue.
Maybe the A10 firmware I'm attempting to push to it is not the correct one?
I also tried switching to fastbootd via these commands,
fastboot reboot fastbood AND adb reboot fastbootd.
Neither worked.
I'm at a stand still at the moment. Anybody have any suggestions?
The saga continues...
I finally decided to do the downgrade using the commands in the flashfile.xml file.
Everything appeared to go well. However, once the phone rebooted, it entered an infinite reboot cycle.
I did manage to stop it from rebooting and using Rescue and Smart Assistant I was able to push A11 stock firmware. So at least it's not bricked, but I'm back to square one.
ezjamm
What I discovered after upgrading to XT2041-4_SOFIA_RETUS_11_RPMS31.Q1-54-13-7_subsidy-DEFAULT_regulatory-DEFAULT_CFC with fastboot flash commands pasted into a terminal:
The bootloader can't be downgraded. Bootlooping ensues when mixing old and new among some of these: partition bootloader radio bluetooth dsp logo. I flashed 11 firmware of all of those, then successfully installed LineageOS with image flashing in fastbootd (boot system vbmeta product).
Don't flash TWRP, because that overwrites fastbootd. Instead, fastboot boot twrp.img from the bootloader if you need it.
Hi danrex,
Thanx for the suggestions. It's going to take me a while to decipher what you wrote though.
Can you expand on what you wrote above? I honestly only understood about 30%. I'm only 3 weeks old when it comes to xda and hacking an android phone.
Thanx,
ezjamm
fastboot getvar is-userspace
Click to expand...
Click to collapse
fastbootd is Motorola's userspace fastboot invoked from the bootloader unless fastbootd has been replaced by TWRP:
# fastboot reboot fastboot
# fastboot getvar is-userspace
is-userspace no: bootloader
is-userspace yes: fastbootd (or TWRP in fastboot mode if I recall correctly)
fastbootd mode is needed for fastboot flashing some parts like a custom vbmeta (verified boot meta) for a non-stock ROM.
What I discovered after upgrading to XT2041-4_SOFIA_RETUS_11_RPMS31.Q1-54-13-7_subsidy-DEFAULT_regulatory-DEFAULT_CFC
Click to expand...
Click to collapse
That's Android 11 stock firmware.
fastboot flash commands pasted into a terminal
Click to expand...
Click to collapse
After upgrading to the bootloader from the Android 11 firmware above:
With the phone in the bootloader, connected to a PC, I ran "fastboot flash bootloader bootloader.img" for the older Android 10 bootloader.img. The Android 11 bootloader refused to allow the downgrade, producing a flashing error. This may explain why you saw the error about failing to flash a single partition when attempting rollback to Android 10 firmware after installing Android 11 firmware.
Bootlooping ensues when mixing old and new among some of these: partition bootloader radio bluetooth dsp logo.
Click to expand...
Click to collapse
Bootlooping is endless rebooting like you described. It happened on a family member's Moto G Power when I tried to mix the Android 11 bootloader with parts of Android 10 firmware.
Don't flash TWRP, because that overwrites fastbootd. Instead, fastboot boot twrp.img from the bootloader if you need it.
Click to expand...
Click to collapse
TWRP takes the place of fastbootd with its own userspace fastboot mode. It might not work 100% as a replacement. As a recovery it's finicky with the A/B slots and installing to the inactive slot with a zipped ROM.
my heart is RACING! after 1.5 full days of many attempts to downgrade from A11 to A10 FASTBOOTD IS THE ANSWER omg. so, I used Motorola-XML-To-Batch-Script-master with stock firmware XT2041-4_SOFIA_RETUS_10_QPMS30.80-109-5_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml many times from bootloader with nothing but boot loops. went into fastbootd just for the hell of it and ran the bat. BOOM! back to stock 10! will update if flashing roms works soon. Woo!!! I am in tears x'D
EXCELLENT news. I will try your steps above. However, if I recall correctly from my previous attempts, I was unable to get into fastbootd. I'll try again.
danrex said:
What I discovered after upgrading to XT2041-4_SOFIA_RETUS_11_RPMS31.Q1-54-13-7_subsidy-DEFAULT_regulatory-DEFAULT_CFC with fastboot flash commands pasted into a terminal:
The bootloader can't be downgraded. Bootlooping ensues when mixing old and new among some of these: partition bootloader radio bluetooth dsp logo. I flashed 11 firmware of all of those, then successfully installed LineageOS with image flashing in fastbootd (boot system vbmeta product).
Don't flash TWRP, because that overwrites fastbootd. Instead, fastboot boot twrp.img from the bootloader if you need it.
Click to expand...
Click to collapse
Hi danrex,
How did you boot into fastbood?
What does this mean, "(boot system vbmeta product)"?
I finally downgraded back to A10. Like auhsoj200 above, I'm excited.
What prevented me from success for two months was getting into fastbootd. No matter what I tried I could not get into it. Turns out, in order to execute the command "adb reboot fastboot" the phone cannot be in recovery mode. It has to be on, in normal operational mode. Who knew? Most of you I'm sure. I did not.
At any rate, I may write a detail HOWTO as I have to repeat the steps for my wife's Moto G Power 2020.
Wonderful news!
I'm thinking about doing this as well because I didn't even know about the whole 10 being needed to be able to flash any of the non stock roms (or any rom really). I of course thinking everything was like a normal phone, just let it run all of the dozen or so OTA updates it had available before I unlocked the BL and rooted. Bad move now I'm on the 11 firmware above and I can't flash any rom. I don't mind all that terrible much as this is my 2nd phone who's purpose serves just as a navigation device and a Viper4Android enhanced music and podcast player. My problem though is it can be quite laggy at times not really the software's fault too much it's not the world's most powerful processor and I'm running Maps doing turn by turn + Viper4Android audio processing with several of it's plugins enabled in a hot car. BUT I know from past experience with other phones the Pixel Experience rom tends to make lesser hardware devices a little more fluid in day to day use so I wanted to try it.
Anyway.... Do you guys think that's worth rolling back for? I've never done it and my fastboot knowledge is somewhat limited but I have it installed already obviously as I recently unlocked the BL and rooted via the Magisk patched boot.img method which worked and that's how I'm running mine right now.
Danng, I'm having no luck either.... I've enabled USB Debugging and OEM bootloader unlock, but when running the script I get a whole bunch of errors saying Downloads and Erase in not allowed on locked device. Tried a whole bunch of other methods with no luck either.
I'm super bummed... bought this phone specifically to root and install custom rom and turns out it came with Android 11 already on it.
Tested the auhsoj200 approach on my Moto G8 (Rav-XT2045-1), worked well so far, no bootloping error. In my case, the state of my moto is like this:
Unlocked bootloader
USB Debugging activated
I followed the steps in this tutorial (using method 1) and successfully reached the fastbootD. Then with this other tutorial I managed to get my flashfile.bat
Once your smartphone is in fastbootD, run the bat file in your computer, It doesn't take that long and within a few minutes you will have your motorola in Android 10 again
Dohva said:
Tested the auhsoj200 approach on my Moto G8 (Rav-XT2045-1), worked well so far, no bootloping error. In my case, the state of my moto is like this:
Unlocked bootloader
USB Debugging activated
I followed the steps in this tutorial (using method 1) and successfully reached the fastbootD. Then with this other tutorial I managed to get my flashfile.bat
Once your smartphone is in fastbootD, run the bat file in your computer, It doesn't take that long and within a few minutes you will have your motorola in Android 10 again
Click to expand...
Click to collapse
this fixed my bootloop, sofia
had to flash 11 first, then boot system and adb reboot fastboot to get to fastbootd and flash 10 and booted no problem
funny thing is when I was bootlooped I could get fastbootd manually through bootloader>recovery, but downgrade from there kept bootlooping.
Having some degree of success... But eventually, my device is bootlooping, and after timing out, i see:
Boot Failed
No bootable A/B Slot
So I'm assuming the partitions were done incorrectly.
It was a bit of a journey to get to this point, I'll outline my steps in greater detail for others who wish to follow. I ran into a few issues that haven't been documented yet.
I followed the two tutorials suggested by Dohva. Here are a couple extra things I had to do:
Must install Motorola USB Drivers to enable your PC to see the android device with Fastboot. (Initially, when I ran the .bat file, the terminal would perpetually say <waiting for any device>. The motorola drivers fix this)
Must unlock the motorola device, otherwise the device won't accept the flash.
Set the android USB config to picture transfer protocol (PTP) (I'm not sure if this actually helped... I tried it at some point along the way before the previous two steps. Not sure if it made a difference)
Dohva said:
I followed the steps in this tutorial (using method 1) and successfully reached the fastbootD. Then with this other tutorial I managed to get my flashfile.bat
Click to expand...
Click to collapse
I obtained the firmware from lolinet.com. I'm not sure if it's where everyone else got their firmware, but it's what I tried first. But this is the firmware that resulted in the bootlooping and Boot Failed error after the flash.
I also tried firmware from firmwaresupport.com, but I had the same outcome.
At this point I'm out of luck, and would appreciate any recommendations!
Here is the output of the flash operation.
As you can see, when it gets to "Writing partition" the bootloader responds with "No suitable package". So I imagine this is a problem...
Code:
max-sparse-size: 268435456
Finished. Total time: 0.001s
OKAY [ 0.002s]
Finished. Total time: 0.003s
Sending 'partition' (37 KB) OKAY [ 0.002s]
Writing 'partition' (bootloader) no suitable package!
FAILED (remote: '')
fastboot: error: Command failed
Sending 'bootloader' (14204 KB) OKAY [ 0.372s]
Writing 'bootloader' (bootloader) no suitable package!
FAILED (remote: '')
fastboot: error: Command failed
fastboot: error: Failed to identify current slot
Sending 'radio' (199577 KB) OKAY [ 4.803s]
Writing 'radio' (bootloader) no suitable package!
FAILED (remote: '')
fastboot: error: Command failed
fastboot: error: Failed to identify current slot
fastboot: error: Failed to identify current slot
fastboot: error: Failed to identify current slot
fastboot: error: Failed to identify current slot
fastboot: error: Failed to identify current slot
fastboot: error: Failed to identify current slot
Sending 'super' (232496 KB) OKAY [ 5.575s]
Writing 'super' OKAY [ 0.056s]
Finished. Total time: 5.640s
Sending 'super' (262140 KB) OKAY [ 6.369s]
Writing 'super' OKAY [ 0.001s]
Finished. Total time: 8.602s
Sending 'super' (262140 KB) OKAY [ 6.313s]
Writing 'super' OKAY [ 0.001s]
Finished. Total time: 10.216s
Sending 'super' (236804 KB) OKAY [ 5.690s]
Writing 'super' OKAY [ 0.001s]
Finished. Total time: 7.258s
Sending 'super' (262140 KB) OKAY [ 6.324s]
Writing 'super' OKAY [ 0.001s]
Finished. Total time: 6.337s
Sending 'super' (260592 KB) OKAY [ 6.269s]
Writing 'super' OKAY [ 0.001s]
Finished. Total time: 7.549s
Sending 'super' (262140 KB) OKAY [ 6.312s]
Writing 'super' OKAY [ 0.001s]
Finished. Total time: 8.200s
Sending 'super' (262140 KB) OKAY [ 6.325s]
Writing 'super' OKAY [ 0.001s]
Finished. Total time: 6.377s
Sending 'super' (257980 KB) OKAY [ 6.203s]
Writing 'super' OKAY [ 0.001s]
Finished. Total time: 8.881s
Sending 'super' (262140 KB) OKAY [ 6.321s]
Writing 'super' OKAY [ 0.001s]
Finished. Total time: 6.355s
Sending 'super' (262140 KB) OKAY [ 6.304s]
Writing 'super' OKAY [ 0.001s]
Finished. Total time: 7.508s
Sending 'super' (262140 KB) OKAY [ 6.290s]
Writing 'super' OKAY [ 0.001s]
Finished. Total time: 7.486s
Sending 'super' (262140 KB) OKAY [ 6.271s]
Writing 'super' OKAY [ 0.001s]
Finished. Total time: 7.472s
Sending 'super' (262140 KB) OKAY [ 6.325s]
Writing 'super' OKAY [ 0.001s]
Finished. Total time: 6.346s
Sending 'super' (259316 KB) OKAY [ 6.223s]
Writing 'super' OKAY [ 0.001s]
Finished. Total time: 7.437s
Sending 'super' (33112 KB) OKAY [ 0.799s]
Writing 'super' OKAY [ 0.000s]
Finished. Total time: 0.976s
Erasing 'carrier' OKAY [ 0.008s]
Finished. Total time: 0.010s
Erasing 'userdata' OKAY [ 0.180s]
Finished. Total time: 0.181s
Erasing 'metadata' OKAY [ 0.006s]
Finished. Total time: 0.007s
Erasing 'ddr' OKAY [ 0.003s]
Finished. Total time: 0.005s
fastboot: error: Failed to identify current slot
OKAY [ 0.002s]
Finished. Total time: 0.002s
-------------------------------------------------------------------------
please scroll up and check your flash for any errors
-------------------------------------------------------------------------
Press any key to continue . . .
Is there any way to get back to android 10? I have tried all the methods mentioned above but still not working.