Related
Hello everyone and sorry for my bad english.
I come here for help with my problem. I bought a Moto G2 TV (XT1069) who was stuck in fastboot mode.
But after more than 40 different procedures in 2 days, nothing worked.
Each command was returned with a failure in the cmd screen.
In fastboot mode no option works except the Barcode option.
My question is: is there a possibility that the main memory has been damaged and fastboot have been saved by being in another memory separately?
I tried everything I found here on XDA and Google and nothing work.
What disturbs me is also the fact of not knowing what version of Android it was, if the bootloader was unlocked or not and if it was with root or not.
CMD Log:
Code:
D:\Downloads\Moto\Android 6>mfastboot flash partition gpt.bin
< waiting for device >
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 5.008s]
writing 'partition'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 10.019s
D:\Downloads\Moto\Android 6>mfastboot flash motoboot motoboot.img
target reported max download size of 536870912 bytes
sending 'motoboot' (2184 KB)...
OKAY [ 5.083s]
writing 'motoboot'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 10.100s
D:\Downloads\Moto\Android 6>mfastboot flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (697 KB)...
OKAY [ 5.054s]
writing 'logo'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 10.081s
D:\Downloads\Moto\Android 6>mfastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (10200 KB)...
OKAY [ 5.357s]
writing 'boot'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 10.392s
D:\Downloads\Moto\Android 6>mfastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (10280 KB)...
OKAY [ 5.375s]
writing 'recovery'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 10.425s
D:\Downloads\Moto\Android 6>mfastboot flash system system.img_sparsechunk.0
target reported max download size of 536870912 bytes
sending 'system' (257435 KB)...
OKAY [ 13.094s]
writing 'system'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 18.134s
D:\Downloads\Moto\Android 6>mfastboot flash system system.img_sparsechunk.1
target reported max download size of 536870912 bytes
sending 'system' (255486 KB)...
OKAY [ 13.022s]
writing 'system'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 18.066s
D:\Downloads\Moto\Android 6>mfastboot flash system system.img_sparsechunk.2
target reported max download size of 536870912 bytes
sending 'system' (256778 KB)...
OKAY [ 13.080s]
writing 'system'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 18.124s
D:\Downloads\Moto\Android 6>mfastboot flash system system.img_sparsechunk.3
target reported max download size of 536870912 bytes
sending 'system' (254001 KB)...
OKAY [ 12.991s]
writing 'system'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 18.035s
D:\Downloads\Moto\Android 6>mfastboot flash modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem' (50136 KB)...
OKAY [ 6.594s]
writing 'modem'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 11.635s
D:\Downloads\Moto\Android 6>mfastboot erase modemst1
erasing 'modemst1'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 10.046s
D:\Downloads\Moto\Android 6>mfastboot erase modemst2
erasing 'modemst2'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 10.047s
D:\Downloads\Moto\Android 6>mfastboot flash fsg fsg.mbn
target reported max download size of 536870912 bytes
sending 'fsg' (1012 KB)...
OKAY [ 5.100s]
writing 'fsg'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 10.144s
D:\Downloads\Moto\Android 6>mfastboot erase cache
erasing 'cache'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 10.046s
I accept other suggestions, although I have tried everything I found.
Have you tried flashing official Marshmallow 6.0 or 6.0.1 for your device?
I have xt1068. A month ago I was almost in a same situation. Only barcode command was working and nothing else from fastboot screen.
I have no experience in this flashing thing so I went to retailers store to fix this software issue but they failed.
Later I found official Android 6.0 thread on xda forum and just followed every step of installation Android 6.0. And Boom!! Phone is now working flawlessly on latest Android OS.
ps. While installing Android 6.0, my phone was not rooted, no custom ROM was Installed before and USB debugging was turned OFF.
I don't know if this is a proper solution or not; as I said I have no experience in flashing.
Hope this help. Ty
Hey, can you provide the link to the official android 6.0 thread?
pkirtan84 said:
Have you tried flashing official Marshmallow 6.0 or 6.0.1 for your device?
I have xt1068. A month ago I was almost in a same situation. Only barcode command was working and nothing else from fastboot screen.
I have no experience in this flashing thing so I went to retailers store to fix this software issue but they failed.
Later I found official Android 6.0 thread on xda forum and just followed every step of installation Android 6.0. And Boom!! Phone is now working flawlessly on latest Android OS.
ps. While installing Android 6.0, my phone was not rooted, no custom ROM was Installed before and USB debugging was turned OFF.
I don't know if this is a proper solution or not; as I said I have no experience in flashing.
Hope this help. Ty
Click to expand...
Click to collapse
pkirtan84 said:
Have you tried flashing official Marshmallow 6.0 or 6.0.1 for your device?
I have xt1068. A month ago I was almost in a same situation. Only barcode command was working and nothing else from fastboot screen.
I have no experience in this flashing thing so I went to retailers store to fix this software issue but they failed.
Later I found official Android 6.0 thread on xda forum and just followed every step of installation Android 6.0. And Boom!! Phone is now working flawlessly on latest Android OS.
ps. While installing Android 6.0, my phone was not rooted, no custom ROM was Installed before and USB debugging was turned OFF.
I don't know if this is a proper solution or not; as I said I have no experience in flashing.
Hope this help. Ty
Click to expand...
Click to collapse
Hello, pkirtan84.
I have experience in roms samsung and LG, but on a Motorola is my first attempt, so I figured he was doing something wrong.
Anyway, although I have already tested one rom with Android 6, could send the rom link you used? Perhaps I would not have been the wrong rom I used, not hurt to try!
Thank you
ederstk said:
Hello, pkirtan84.
I have experience in roms samsung and LG, but on a Motorola is my first attempt, so I figured he was doing something wrong.
Anyway, although I have already tested one rom with Android 6, could send the rom link you used? Perhaps I would not have been the wrong rom I used, not hurt to try!
Thank you
Click to expand...
Click to collapse
sure ederstk, here is it
http://forum.xda-developers.com/moto-g-2014/general/official-stock-firmware-t3018682
pkirtan84 said:
sure ederstk, here is it
http://forum.xda-developers.com/moto-g-2014/general/official-stock-firmware-t3018682
Click to expand...
Click to collapse
Thank you, pkirtan84! I'll check when I get home and post results!
All the best!
Hello, pkirtan84. Still not working, with same messages.
I believe that the low battery warning is now in the way. I will try to recharge it and continue my tests.
Still, thank you!
ederstk said:
Hello, pkirtan84. Still not working, with same messages.
I believe that the low battery warning is now in the way. I will try to recharge it and continue my tests.
Still, thank you!
Click to expand...
Click to collapse
um.. what's not working?
download link of Android 6.0 or the process of flashing 6.0?
the flashing process. still stuck in same screen. I try searching more solutions in the web
I'm trying to flash it using TWRP, but when it asks which partition to flash it to, my only options are Boot and Recovery. Vendor is not there (it is mounted, though).
when I try flashing it using fastboot, I get this:
Code:
target reported max download size of 471859200 bytes
Invalid sparse file format at header magi
sending sparse 'vendor' (311613 KB)...
OKAY [ 7.933s]
writing 'vendor'...
FAILED (remote: Command not allowed)
finished. total time: 7.940s
Exact same problem
D:\phone extracts>fastboot flash vendor VENDOR.img
target reported max download size of 471859200 bytes
sending sparse 'vendor' 1/2 (457331 KB)...
OKAY [ 10.760s]
writing 'vendor' 1/2...
FAILED (remote: Command not allowed)
finished. total time: 10.768s
any help on this?
Same problem here on ANE-lx1
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash vendor vendor.img
target reported max download size of 471859200 bytes
sending sparse 'vendor' 1/2 (435194 KB)...
OKAY [ 16.808s]
writing 'vendor' 1/2...
FAILED (remote: Command not allowed)
finished. total time: 16.808s
Sounds like your bootloader has been locked. Try unlocking before re-flashing
Hey guys, recently I hard bricked my sanders 1802 in way that everything I tried does not work.
After I flashed lineage 16.0, the fingerprint sensor and some other things were not working, then I tried downgrading it back to stock via fastboot, Sanders retail 8.1.
After that everthing went to hell. It got into bootloop. So i tried to restore it via Leonovo Moto Smart Assistant. Went back to bootloop and started showing some cache mount issues.
I tried over 10 different ROMs and every time it showed cache mout problems or ERROR 6, 7 and 1 in TWRP and sometimes kernel issues.
I've already tried flashing new kernels, tried every ERROR 6 and 7 solutions that are available online and nothing happens.
Right now I have it at the best shape possible, it has the latest TWRP installed (3.2.1 sanders r20), it does not show any cache nor kernel errors when I try to install a ROM, but it keeps giving me the ERROR 7 even when I delete the assert line on the updater-script file.
Searching the XDA foruns I found someone talking about getting a fresh start for the phone by flash the sdcard with mmcbk0.img. I'm not even sure if that's the right path to solve my problem, but I thought I give it a try since I have no idea what else to do.
I'm pretty noob on everything regarding android, just followed everything easily when it comes to tutorials.
Can someone please help me? Is the new mmcbk0.img file the right path or should I try somthing else? I talked to a "expert" guy here in my city and he said that the phone is gone and there's nothing I can do. Is it possible?
Have you tried TWRP 3.3
pradeeppk said:
Have you tried TWRP 3.3
Click to expand...
Click to collapse
It does not even install, it gives me this:
cmd: getvar: partition-type: recovery
cmd: getvar: max-download-size
cmd: download: 00471000
cmd: flash: recovery
Error: failed to load kernel!
Boot up failed
voliveira92 said:
It does not even install, it gives me this:
cmd: getvar: partition-type: recovery
cmd: getvar: max-download-size
cmd: download: 00471000
cmd: flash: recovery
Error: failed to load kernel!
Boot up failed
Click to expand...
Click to collapse
Are you using fastboot command to flash recovery, Try to boot from twrp3.3 without installing, "fastboot boot recovery <your twrp3.3 Name>.img and flash a custom rom from there. Have you any backup of your stock image?
pradeeppk said:
Are you using fastboot command to flash recovery, Try to boot from twrp3.3 without installing, "fastboot boot recovery <your twrp3.3 Name>.img and flash a custom rom from there. Have you any backup of your stock image?
Click to expand...
Click to collapse
Yes, I'm using fastboot to flash it.
I tried booting directly from twrp.3.3.1 but it gives me this error message:
cannot load 'recovery': No such file or directory
Searched for a solution and tried to rename the file to one single name (twrp.img), tried renaming the adb/fastboot folder to one single name as well and it didn't work.
And unfortunately I don't have a backup of my stock
voliveira92 said:
Yes, I'm using fastboot to flash it.
I tried booting directly from twrp.3.3.1 but it gives me this error message:
cannot load 'recovery': No such file or directory
Searched for a solution and tried to rename the file to one single name (twrp.img), tried renaming the adb/fastboot folder to one single name as well and it didn't work.
And unfortunately I don't have a backup of my stock
Click to expand...
Click to collapse
Have you missing something? i mean .img, Code is fastboot boot recovery twrp.img.
HTML:
pradeeppk said:
Have you missing something? i mean .img, Code is fastboot boot recovery twrp.img.
Click to expand...
Click to collapse
I'm pretty sure that I'm not missing anything.
I was able to flash Twrp 3.3.0 from this thread (https://forum.xda-developers.com/moto-g5s-plus/development/recovery-twrp-3-3-0-t3940378), but now it keeps giving me Error 7 and 'unable to mount system'.
Tried lineage and Havocs ROM. Tried altering the assert line again and no changes.
pradeeppk said:
Try to boot from twrp3.3 without installing, "fastboot boot recovery <your twrp3.3 Name>.img and flash a custom rom from there.
Click to expand...
Click to collapse
Wrong command format
voliveira92 said:
it gives me this error message:
cannot load 'recovery': No such file or directory
Click to expand...
Click to collapse
Try the command:
Code:
fastboot boot <your_twrp_filename.img>
Run
Code:
fastboot --help
for the help on how to use fastboot.
D302Thakur said:
Wrong command format
Try the command:
Code:
fastboot boot <your_twrp_filename.img>
Run
Code:
fastboot --help
for the help on how to use fastboot.
Click to expand...
Click to collapse
I'm not having troubles with flashing or booting Twrp via fastboot, I'm having issues with Twrp or something else that is interfering and not allowing me to flash any ROM.
I've tried every TWRP I've found, 3.2.1, 3.3.0, 3.3.1, all of them gives me the ERROR 7 when I try to flash a ROM.
Looked online for the ERROR 7 solution, tried erasing the assert line from updater-script file and still no help.
The times that I flashed the ROMs via fastboot or adb the phone stays in bootloop or just freezes at the boot screen.
I don't have a backup stock file.
voliveira92 said:
I'm not having troubles with flashing or booting Twrp via fastboot, I'm having issues with Twrp or something else that is interfering and not allowing me to flash any ROM.
I've tried every TWRP I've found, 3.2.1, 3.3.0, 3.3.1, all of them gives me the ERROR 7 when I try to flash a ROM.
Looked online for the ERROR 7 solution, tried erasing the assert line from updater-script file and still no help.
The times that I flashed the ROMs via fastboot or adb the phone stays in bootloop or just freezes at the boot screen.
I don't have a backup stock file.
Click to expand...
Click to collapse
It may be a hardware issue or currupted partition, Flash stock firmware using fastboot, erase data and cache using these fastboot commands "fastboot erase userdata and fastboot erase cache"
pradeeppk said:
It may be a hardware issue or currupted partition, Flash stock firmware using fastboot, erase data and cache using these fastboot commands "fastboot erase userdata and fastboot erase cache"
Click to expand...
Click to collapse
Don't think its hardware because the only thing I did was flash lineage 16.0 (worked) and then try to go back to stock ROM. Do you have the link for stock firmware, please? I tried one but didn't work as well (SANDERS_NPSS26.116-64-2).
voliveira92 said:
Don't think its hardware because the only thing I did was flash lineage 16.0 (worked) and then try to go back to stock ROM. Do you have the link for stock firmware, please? I tried one but didn't work as well (SANDERS_NPSS26.116-64-2).
Click to expand...
Click to collapse
Those are the lines that came with error. The phone went on a bootloop after clearing the cache and userdata.
platform-tools>fastboot flash system system.img_sparsechunk.0
target reported max download size of 536870912 bytes
sending 'system' (504333 KB)...
OKAY [ 11.743s]
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 11.804s
platform-tools>fastboot flash system system.img_sparsechunk.5
target reported max download size of 536870912 bytes
sending 'system' (495479 KB)...
OKAY [ 11.539s]
writing 'system'...
(bootloader) Invalid sparse image data
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 15.942s
platform-tools>fastboot flash system system.img_sparsechunk.6
target reported max download size of 536870912 bytes
sending 'system' (65436 KB)...
OKAY [ 1.528s]
writing 'system'...
(bootloader) Invalid sparse image data
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 1.552s
platform-tools>fastboot flash oem oem.img
target reported max download size of 536870912 bytes
sending 'oem' (335882 KB)...
OKAY [ 7.802s]
writing 'oem'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 7.841s
Try to fix file system using "repair or change file system" menu in twrp and set them all default. Then format data, cache and system and flash a new rom.
Here is the link to g5splus firmwares https://firmware.center/firmware/
pradeeppk said:
Try to fix file system using "repair or change file system" menu in twrp and set them all default. Then format data, cache and system and flash a new rom.
Here is the link to g5splus firmwares https://firmware.center/firmware/
Click to expand...
Click to collapse
Ok, so I repaired system file, formated data, cache and system and tried to flash from TWRP and fastboot.
On TWRP I got the same ERROR 7 as always (tried Pixel Experience and Havoc OS, as well stock firmware Sanders_NPS26.1):
E1001: Failed to update system image.
Updater process ended with ERROR: 7
Tried again editing the assert line and the same ERROR 7 anyway.
And via fastboot (stock firmware) I got this and the phone went on bootloop after rebooting:
fastboot oem fb_mode_set
...
OKAY [ 0.004s]
finished. total time: 0.004s
fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (45 KB)...
OKAY [ 0.005s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.073s
fastboot flash bootloader bootloader.img
target reported max download size of 536870912 bytes
sending 'bootloader' (5115 KB)...
OKAY [ 0.124s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'emmc_appsboot.mbn' to 'aboot'
(bootloader) - flashing 'rpm.mbn' to 'rpm'
(bootloader) - flashing 'tz.mbn' to 'tz'
(bootloader) - flashing 'devcfg.mbn' to 'devcfg'
(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'
(bootloader) - flashing 'cmnlib64.mbn' to 'cmnlib64'
(bootloader) - flashing 'keymaster.mbn' to 'keymaster'
(bootloader) - flashing 'prov.mbn' to 'prov'
(bootloader) - flashing 'sbl1.mbn' to 'sbl1'
OKAY [ 0.704s]
finished. total time: 0.828s
fastboot flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (2192 KB)...
OKAY [ 0.054s]
writing 'logo'...
OKAY [ 0.109s]
finished. total time: 0.163s
fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.397s]
writing 'boot'...
(bootloader) Image signed with key bad key
OKAY [ 0.419s]
finished. total time: 0.816s
fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (20580 KB)...
OKAY [ 0.496s]
writing 'recovery'...
(bootloader) Image signed with key bad key
OKAY [ 0.511s]
finished. total time: 1.007s
fastboot flash dsp adspso.bin
target reported max download size of 536870912 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.385s]
writing 'dsp'...
OKAY [ 0.286s]
finished. total time: 0.670s
fastboot flash oem oem.img
target reported max download size of 536870912 bytes
sending 'oem' (327830 KB)...
OKAY [ 7.627s]
writing 'oem'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 7.669s
fastboot flash system system.img_sparsechunk.0
target reported max download size of 536870912 bytes
sending 'system' (524260 KB)...
OKAY [ 12.189s]
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 12.260s
fastboot flash system system.img_sparsechunk.1
target reported max download size of 536870912 bytes
sending 'system' (522314 KB)...
OKAY [ 12.161s]
writing 'system'...
OKAY [ 6.230s]
finished. total time: 18.391s
fastboot flash system system.img_sparsechunk.2
target reported max download size of 536870912 bytes
sending 'system' (522269 KB)...
OKAY [ 12.161s]
writing 'system'...
OKAY [ 7.196s]
finished. total time: 19.356s
fastboot flash system system.img_sparsechunk.3
target reported max download size of 536870912 bytes
sending 'system' (524204 KB)...
OKAY [ 12.207s]
writing 'system'...
OKAY [ 6.143s]
finished. total time: 18.349s
fastboot flash system system.img_sparsechunk.4
target reported max download size of 536870912 bytes
sending 'system' (524139 KB)...
OKAY [ 12.211s]
writing 'system'...
OKAY [ 6.929s]
finished. total time: 19.141s
fastboot flash system system.img_sparsechunk.5
target reported max download size of 536870912 bytes
sending 'system' (435100 KB)...
OKAY [ 10.111s]
writing 'system'...
(bootloader) Invalid sparse image data
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 12.502s
fastboot flash modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem' (75360 KB)...
OKAY [ 1.758s]
writing 'modem'...
OKAY [ 1.088s]
finished. total time: 2.846s
fastboot flash fsg fsg.mbn
target reported max download size of 536870912 bytes
sending 'fsg' (2452 KB)...
OKAY [ 0.059s]
writing 'fsg'...
OKAY [ 0.118s]
finished. total time: 0.178s
fastboot erase cache
erasing 'cache'...
OKAY [ 0.018s]
finished. total time: 0.018s
fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.334s]
finished. total time: 0.334s
fastboot erase customize
erasing 'customize'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.003s
fastboot erase clogo
erasing 'clogo'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.003s
fastboot oem fb_mode_clear
...
OKAY [ 0.118s]
finished. total time: 0.118s
fastboot flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (2192 KB)...
OKAY [ 0.054s]
writing 'logo'...
OKAY [ 0.131s]
finished. total time: 0.185s
I have the option of switching the system file to another format on TWRP (EXT2, EXT3, EXT4, FAT, exFAT, F2Fs), could any of those help?
voliveira92 said:
fastboot erase customize
fastboot erase clogo
Click to expand...
Click to collapse
Where did you get this firmware from ?
From what I used to flash, the was nothing like customise or clogo.
Try this stock : https://rsdsecure-cloud.motorola.co...900158&Signature=8E+n+/9YjxFXHGokrKaycy1StXI=
And this script :
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
D302Thakur said:
Where did you get this firmware from ?
From what I used to flash, the was nothing like customise or clogo.
Try this stock : https://rsdsecure-cloud.motorola.co...900158&Signature=8E+n+/9YjxFXHGokrKaycy1StXI=
And this script :
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
Click to expand...
Click to collapse
Ok, so I tried the stock you recomended and used the codes you provided.
Here's what I got. Frozen at boot screen. Tried from -fastboot- and -minimal adb and fastboot-.
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot getvar max-sparse-size
max-sparse-size: 268435456
finished. total time: 0.000s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot oem fb_mode_set
...
OKAY [ 0.002s]
finished. total time: 0.002s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash partition gpt.bin
target reported max download size of 534773760 bytes
sending 'partition' (45 KB)...
OKAY [ 0.002s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.057s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash bootloader bootloader.img
target reported max download size of 534773760 bytes
sending 'bootloader' (5115 KB)...
OKAY [ 0.122s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'emmc_appsboot.mbn' to 'aboot'
(bootloader) - flashing 'rpm.mbn' to 'rpm'
(bootloader) - flashing 'tz.mbn' to 'tz'
(bootloader) - flashing 'devcfg.mbn' to 'devcfg'
(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'
(bootloader) - flashing 'cmnlib64.mbn' to 'cmnlib64'
(bootloader) - flashing 'keymaster.mbn' to 'keymaster'
(bootloader) - flashing 'prov.mbn' to 'prov'
(bootloader) - flashing 'sbl1.mbn' to 'sbl1'
OKAY [ 0.519s]
finished. total time: 0.641s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash modem NON-HLOS.bin
target reported max download size of 534773760 bytes
sending 'modem' (71941 KB)...
OKAY [ 1.678s]
writing 'modem'...
OKAY [ 0.980s]
finished. total time: 2.658s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash fsg fsg.mbn
target reported max download size of 534773760 bytes
sending 'fsg' (3024 KB)...
OKAY [ 0.071s]
writing 'fsg'...
OKAY [ 0.120s]
finished. total time: 0.191s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.035s]
finished. total time: 0.035s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.035s]
finished. total time: 0.035s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash dsp adspso.bin
target reported max download size of 534773760 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.382s]
writing 'dsp'...
OKAY [ 0.254s]
finished. total time: 0.637s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash logo logo.bin
target reported max download size of 534773760 bytes
sending 'logo' (2192 KB)...
OKAY [ 0.051s]
writing 'logo'...
OKAY [ 0.097s]
finished. total time: 0.150s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash boot boot.img
target reported max download size of 534773760 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.396s]
writing 'boot'...
(bootloader) Image signed with key bad key
OKAY [ 0.357s]
finished. total time: 0.754s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash recovery recovery.img
target reported max download size of 534773760 bytes
sending 'recovery' (20580 KB)...
OKAY [ 0.490s]
writing 'recovery'...
(bootloader) Image signed with key bad key
OKAY [ 0.452s]
finished. total time: 0.942s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.0
target reported max download size of 534773760 bytes
sending 'system' (262140 KB)...
OKAY [ 6.097s]
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 6.099s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.1
target reported max download size of 534773760 bytes
sending 'system' (249863 KB)...
OKAY [ 5.809s]
writing 'system'...
OKAY [ 2.935s]
finished. total time: 8.744s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.2
target reported max download size of 534773760 bytes
sending 'system' (260323 KB)...
OKAY [ 6.091s]
writing 'system'...
OKAY [ 3.729s]
finished. total time: 9.820s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.3
target reported max download size of 534773760 bytes
sending 'system' (262140 KB)...
OKAY [ 6.105s]
writing 'system'...
OKAY [ 3.309s]
finished. total time: 9.414s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.4
target reported max download size of 534773760 bytes
sending 'system' (262142 KB)...
OKAY [ 6.098s]
writing 'system'...
OKAY [ 3.106s]
finished. total time: 9.203s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.5
target reported max download size of 534773760 bytes
sending 'system' (262141 KB)...
OKAY [ 6.097s]
writing 'system'...
OKAY [ 2.928s]
finished. total time: 9.025s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.6
target reported max download size of 534773760 bytes
sending 'system' (262141 KB)...
OKAY [ 6.104s]
writing 'system'...
OKAY [ 2.986s]
finished. total time: 9.090s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.7
target reported max download size of 534773760 bytes
sending 'system' (255675 KB)...
OKAY [ 5.971s]
writing 'system'...
OKAY [ 3.487s]
finished. total time: 9.459s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.8
target reported max download size of 534773760 bytes
sending 'system' (242629 KB)...
OKAY [ 5.647s]
writing 'system'...
OKAY [ 2.830s]
finished. total time: 8.478s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.9
target reported max download size of 534773760 bytes
sending 'system' (239745 KB)...
OKAY [ 5.575s]
writing 'system'...
(bootloader) Invalid sparse image data
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 6.124s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.10
target reported max download size of 534773760 bytes
sending 'system' (65436 KB)...
OKAY [ 1.518s]
writing 'system'...
(bootloader) Invalid sparse image data
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 1.520s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash oem oem.img
target reported max download size of 534773760 bytes
sending 'oem' (135426 KB)...
OKAY [ 3.150s]
writing 'oem'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 3.153s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot erase cache
erasing 'cache'...
OKAY [ 0.009s]
finished. total time: 0.009s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.124s]
finished. total time: 0.124s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot erase DDR
erasing 'DDR'...
OKAY [ 0.001s]
finished. total time: 0.001s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot oem fb_mode_clear
...
OKAY [ 0.002s]
finished. total time: 0.002s
SANDERS_RETAIL_8.1.0_OPS28.65-36-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot reboot
rebooting...
finished. total time: 0.001s
voliveira92 said:
fastboot flash system system.img_sparsechunk.0
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
fastboot flash system system.img_sparsechunk.9
writing 'system'...
(bootloader) Invalid sparse image data
(bootloader) Failed to flash sparse image
FAILED (remote failure)
fastboot flash system system.img_sparsechunk.10
writing 'system'...
(bootloader) Invalid sparse image data
(bootloader) Failed to flash sparse image
FAILED (remote failure)
fastboot flash oem oem.img
writing 'oem'...
(bootloader) Preflash validation failed
FAILED (remote failure)
Click to expand...
Click to collapse
I guess, there's some problem with your system partition.
Like you said, even in TWRP system was failing to flash and here also.
Further, oem also failed here.
Rest of the output is fine and expected.
To conclude anything further, may I know your region ? Like India, Brazil,...
Or better if you know the device model, like xt1804, xt1802, etc...
D302Thakur said:
I guess, there's some problem with your system partition.
Like you said, even in TWRP system was failing to flash and here also.
Further, oem also failed here.
Rest of the output is fine and expected.
To conclude anything further, may I know your region ? Like India, Brazil,...
Or better if you know the device model, like xt1804, xt1802, etc...
Click to expand...
Click to collapse
Brazil, model XT1802
voliveira92 said:
Brazil, model XT1802
Click to expand...
Click to collapse
Can anyone please help me with this? I'm almost giving up on this device but I can't accept that there's nothing else I can try.
hello iam just newer on xda , & i have probleme with my honor 9 lite is bricked whene iam downgrade my device used hisuite , the device fixed on fastboot mode and black screen , frp locked , bootloader locked
can anyone helpe me please
model : lld-l21
lilolahcen said:
hello iam just newer on xda , & i have probleme with my honor 9 lite is bricked whene iam downgrade my device used hisuite , the device fixed on fastboot mode and black screen , frp locked , bootloader locked
can anyone helpe me please
Click to expand...
Click to collapse
help meeeeeeee please
lilolahcen said:
help meeeeeeee please
Click to expand...
Click to collapse
Can you get into recovery?
Have you held power button for 10 seconds to reboot from fastboot if you can't use terminal
villapark75 said:
Can you get into recovery?
Have you held power button for 10 seconds to reboot from fastboot if you can't use terminal
Click to expand...
Click to collapse
no, i can't get into recovery because the device does'nt boot
i can use a terminal but , when i write fastboot reboot , the device reboots and returns to fastboot
What happens when you issue 'fastboot reboot' hit enter and immediately unplug USB from PC ?
Sparkrite said:
What happens when you issue 'fastboot reboot' hit enter and immediately unplug USB from PC ?
Click to expand...
Click to collapse
i didn' try it , But i flashed the device via adb fastboot
However, the flash does not pass , Just get me this error
failed (remote command not allowed )
lilolahcen said:
i didn' try it , But i flashed the device via adb fastboot
However, the flash does not pass , Just get me this error
failed (remote command not allowed )
Click to expand...
Click to collapse
that my adb show when i am use it
C:\adb>fastboot devices
MKJNW18531002486 fastboot
C:\adb>
C:\adb>fastboot flash recovery_ramdisk recovery_ramdis.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (32768 KB)...
OKAY [ 1.152s]
writing 'recovery_ramdisk'...
FAILED (remote: Command not allowed)
finished. total time: 1.170s
C:\adb>fastboot flash recovery_vbmeta recovery_vbmeta.img
target reported max download size of 471859200 bytes
sending 'recovery_vbmeta' (6 KB)...
OKAY [ 0.004s]
writing 'recovery_vbmeta'...
FAILED (remote: Command not allowed)
finished. total time: 0.018s
C:\adb>fastboot flash recovery_vendor recovery_vendor.img
target reported max download size of 471859200 bytes
sending 'recovery_vendor' (16384 KB)...
OKAY [ 0.580s]
writing 'recovery_vendor'...
FAILED (remote: Command not allowed)
finished. total time: 0.597s
C:\adb>fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' (460796 KB)...
OKAY [ 28.857s]
writing 'system'...
FAILED (remote: Command not allowed)
finished. total time: 28.889s
C:\adb>fastboot flash vbmeta vbmeta.img
target reported max download size of 471859200 bytes
sending 'vbmeta' (16 KB)...
OKAY [ 0.005s]
writing 'vbmeta'...
FAILED (remote: Command not allowed)
finished. total time: 0.017s
please can you help me :crying::crying::crying:
lilolahcen said:
that my adb show when i am use it
C:\adb>fastboot devices
MKJNW18531002486 fastboot
C:\adb>
C:\adb>fastboot flash recovery_ramdisk recovery_ramdis.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (32768 KB)...
OKAY [ 1.152s]
writing 'recovery_ramdisk'...
FAILED (remote: Command not allowed)
finished. total time: 1.170s
C:\adb>fastboot flash recovery_vbmeta recovery_vbmeta.img
target reported max download size of 471859200 bytes
sending 'recovery_vbmeta' (6 KB)...
OKAY [ 0.004s]
writing 'recovery_vbmeta'...
FAILED (remote: Command not allowed)
finished. total time: 0.018s
C:\adb>fastboot flash recovery_vendor recovery_vendor.img
target reported max download size of 471859200 bytes
sending 'recovery_vendor' (16384 KB)...
OKAY [ 0.580s]
writing 'recovery_vendor'...
FAILED (remote: Command not allowed)
finished. total time: 0.597s
C:\adb>fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' (460796 KB)...
OKAY [ 28.857s]
writing 'system'...
FAILED (remote: Command not allowed)
finished. total time: 28.889s
C:\adb>fastboot flash vbmeta vbmeta.img
target reported max download size of 471859200 bytes
sending 'vbmeta' (16 KB)...
OKAY [ 0.005s]
writing 'vbmeta'...
FAILED (remote: Command not allowed)
finished. total time: 0.017s
please can you help me :crying::crying::crying:
Click to expand...
Click to collapse
Hello. Hope you have enough data on your plan. First download the firmware from this link https: // androidhost . ru / 9X9 (remove the spaces while pasting). Once downloaded extract the contents from the zip file to your pc. Before proceeding make sure your smartphone is charged. In the extracted contents you will have a folder named 'Software'. Inside that folder you will have a folder named 'dload'. Copy the 'dload' folder to the root directory of a formatted sd card. Once it is copied insert the sd card inside your honor 9 lite and press the power, volume up and down buttons simultaneously until your phone enters recovery mode. From there it will take a few minutes for the software installation to be completed. Once the installation is finished your phone will be rebooted and you will have to finish the initial setting up process. If you follow these steps you can recover your phone but you will loose all the data previously present in the phone. Hope this works for you. Please reply if this is successful.
Leeban Joseph said:
Hello. Hope you have enough data on your plan. First download the firmware from this link https: // androidhost . ru / 9X9 (remove the spaces while pasting). Once downloaded extract the contents from the zip file to your pc. Before proceeding make sure your smartphone is charged. In the extracted contents you will have a folder named 'Software'. Inside that folder you will have a folder named 'dload'. Copy the 'dload' folder to the root directory of a formatted sd card. Once it is copied insert the sd card inside your honor 9 lite and press the power, volume up and down buttons simultaneously until your phone enters recovery mode. From there it will take a few minutes for the software installation to be completed. Once the installation is finished your phone will be rebooted and you will have to finish the initial setting up process. If you follow these steps you can recover your phone but you will loose all the data previously present in the phone. Hope this works for you. Please reply if this is successful.
Click to expand...
Click to collapse
Very late to the party, but wanted to thank you for a comprehensive, helpful answer.
The fact lilolahcen didn't respond is hopefully because his phone is working once again.
Good post ?
Thanks. I myself have gone through many guides available here at xda. So I hope I can be of some use for someone who is facing the same problems I have faced.
So... I tried to unlock/root my Redmi Note 11 (SPES), and something went wrong. So now I am trying to fix it, restore to the stock ROM to try again.
How I broke it:
1. Unlocked the bootloader.
2. Installed probably the wrong TWRP (I installed twrp-3.6.2-12.1-21.06.22.img from https://razaoinfo.dl.sourceforge.ne...ld/Recovery-Spes/twrp-3.6.2-12.1-21.06.22.img )
3. I tried flashing said img using fastboot (fastboot flash recovery_a <img>, followed by fastboot flash recovery_b <img>, then fastboot boot <img>
4. Got into TWRP, flashed Magisk.
5. Got into ROM. Everything seems to work, I have root. Next day, I realize my bluetooth is not working.
Next day, I tried flashing another TWRP that I found linked in this forum (twrp-3.6.2_12-0-spes-Jabiyeff.img, downloaded from https://forum.xda-developers.com/t/...-redmi-note-11-and-how-do-i-flash-it.4466177/ post #4).
6. After flashing, ROM no longer boots, and just sends me to fastboot.
7. I checked again with fastboot, and.. it seems the recovery partition isn't there?
Code:
C:\adb2>fastboot.exe devices
ff23ad4 fastboot
C:\adb2>fastboot.exe flash recovery twrp-3.6.2_12-0-spes-Jabiyeff.img
target reported max download size of 796917760 bytes
sending 'recovery' (131072 KB)...
OKAY [ 2.902s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 2.909s
C:\adb2>fastboot.exe flash recovery_a twrp-3.6.2_12-0-spes-Jabiyeff.img
target reported max download size of 796917760 bytes
sending 'recovery_a' (131072 KB)...
OKAY [ 2.828s]
writing 'recovery_a'...
FAILED (remote: (recovery_a_b) No such partition)
finished. total time: 2.835s
C:\adb2>fastboot.exe flash recovery_b twrp-3.6.2_12-0-spes-Jabiyeff.img
target reported max download size of 796917760 bytes
sending 'recovery_b' (131072 KB)...
OKAY [ 2.805s]
writing 'recovery_b'...
FAILED (remote: (recovery_b_b) No such partition)
finished. total time: 2.812s
C:\adb2>fastboot.exe flash recovery twrp-3.6.2_12-0-spes-Jabiyeff.img
target reported max download size of 796917760 bytes
sending 'recovery' (131072 KB)...
OKAY [ 2.849s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 2.857s
C:\adb2>fastboot.exe boot twrp-3.6.2_12-0-spes-Jabiyeff.img #NOTE: Here I changed the active partition in this TWRP from B to A.
downloading 'boot.img'...
OKAY [ 2.790s]
booting...
OKAY [ 0.367s]
finished. total time: 3.159s
C:\adb2>fastboot.exe devices
ff23ad4 fastboot
C:\adb2>fastboot.exe flash recovery twrp-3.6.2_12-0-spes-Jabiyeff.img
target reported max download size of 268435456 bytes
sending 'recovery' (131072 KB)...
OKAY [ 2.933s]
writing 'recovery'...
FAILED (remote: No such file or directory)
finished. total time: 2.946s
C:\adb2>fastboot.exe flash recovery_a twrp-3.6.2_12-0-spes-Jabiyeff.img
target reported max download size of 268435456 bytes
sending 'recovery_a' (131072 KB)...
OKAY [ 2.899s]
writing 'recovery_a'...
FAILED (remote: No such file or directory)
finished. total time: 2.918s
C:\adb2>fastboot.exe flash recovery_b twrp-3.6.2_12-0-spes-Jabiyeff.img
target reported max download size of 268435456 bytes
sending 'recovery_b' (131072 KB)...
OKAY [ 2.931s]
writing 'recovery_b'...
FAILED (remote: No such file or directory)
finished. total time: 2.943s
C:\adb2>fastboot.exe flash recovery twrp-3.6.2_12-0-spes-Jabiyeff.img
target reported max download size of 268435456 bytes
sending 'recovery' (131072 KB)...
OKAY [ 2.874s]
writing 'recovery'...
FAILED (remote: No such file or directory)
finished. total time: 2.887s
So, I wonder if I should be concerned about not finding a recovery/recovery_a/recovery_b partition (I am pretty sure recovery_a/b where there when I flashed TWRP the first time).
So, I am following now this guide to install the stock ROM: https://xiaomistockrom.com/xiaomi-redmi-note-11
Am I on the right path? I want to check before proceeding, because... right now I have fast boot and can boot into TWRP using it, but if I do things incorrectly from now on, I could brick the device. So I wanted to ask for advice on what I am doing first here.
TIA.
It's fairly difficult to hard brick a device. Most of the time you'll just end up soft bricking your device which is easy to fix as long as you can access bootloader mode. If you want to fully restore your device to default, you can download your stock rom (fastboot version) and flash using miflash.
Also yes, the guide you linked is correct.
Thanks, I managed to solve it.
The fastboot issue went away some time afterwards, and I could boot normally into the ROM, but... my bluetooth stopped working (which is really strange considering I only flashed the recovery partition). I tried flashing the bluetooth partition from the stock ROM's, but that didn't fix it.
So I tried flashing the stock ROM, following the previously linked guide (and that guide, not the guides that came bundled in the downloaded ROM, that one was for a different device, not a Xiaomi phone at all, weird!).
And now, I have bluetooth again. Thanks goodness for Migrate, I should be able to restore the rest of the device swiftly now.