Question Help restoring Stock ROM [SOLVED] - Redmi Note 11 (spes/spesn)

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.

Related

Soft bricked OP3T

Hello my hope :3
actually i cannot access my recovery or the os, if i start the device, its just a bootloop.
Fastboot is possible, but bootloader is locked and im not able to tick something in the develeloper settings because there is no os anymore.
C:\adb>fastboot flash recovery recovery_OBT7.img
target reported max download size of 442499072 bytes
sending 'recovery' (22237 KB)...
OKAY [ 0.500s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.529s
Click to expand...
Click to collapse
i tried the Snapdragon tool(MsmDownloadTool) also but only get this error: FirehoseWriteData Failed, do you have any suggestions? :c

Can't flash vendor.img

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

How to revert back to Stock Rom for Asus Max Pro M1 (and relocking the bootloader)

I owned an European version of Max Pro M1 (WW_X00TD) and I played with it with custom ROMs by unlocking the bootloader and install TWRP for flashing custom ROM.
When the trials done, I tried to flash back to the original international ROM (recovering the phone to original status including relocking the bootloader and re-installation of the stock recovery, etc.)
I searched the forum and also other web resources and I have tried an easier and more direct way to do this. Basically I used the Asus Fastboot flashing technique to directly overwrite the phone’s internal memory with stock data. So I guess this method can also be applied to a bricked phone
I think I should document the steps here so that in case other owners of this phone have the need to go back to stock, you can try the similar steps.
*Waning: I have only tried these steps on my own phone with the files suggested below. Proceed at your own risk.
1. Backup the important data in your phone
2. Get a Windows machine (7 or 8 or 10)
Install the Asus phone drivers for Windows
Visit this thread for downloading the rar file. One of the extracted files contains the drivers
This thread also contains the instruction to unlock your phone’s bootloader and install the TWRP
Download and install the adb setup files here in this thread
I used the one for Version 1.3 there
3. Connect your phone via usb cable to see if it can be properly connected to your Windows machine to make sure your drivers work.
4. Download the file [TuserHp.com]_WW_ZB601KL(ZB602KL)_14.2016.1802.247_20180419_AFT.zip in this thread
5. Extracted the zip file
6. Copy all the contents of the zip file to a folder under C: drive (in my case c:\asus )
7. Now reboot your phone into fastboot mode by pressing volume up + power on at the same time (make sure your phone has more than 80% power for the battery)
8. Connect your phone via usb connection to your Windows computer
9. Open the command Windows in your computer and navigate to the directory where you have extracted those files
10. At your command prompt, type flashall_AFT.bat to execute this batch file
11. Wait and watch the outputs while this batch file overwrites your phone internal storage with stock data
Here is the sample output:
c:\asus>flashall_AFT.bat
------------------------
Begin fastboot flashall
------------------------
Earse Data: Yes
Support All device
current-slot is current-slot
buildtype is user
target reported max download size of 536870912 bytes
…………………………..<< truncated the outputs>>>>>
...
FAILED (remote: unknown command !)
finished. total time: 0.000s
...
FAILED (remote: unknown command !)
finished. total time: 0.033s
--------------------------------
begin to flash partition xbl
target reported max download size of 536870912 bytes
sending 'xbl' (2802 KB)...
OKAY [ 0.233s]
writing 'xbl'...
OKAY [ 0.021s]
finished. total time: 0.254s
done
--------------------------------
--------------------------------
begin to flash partition xblbak
target reported max download size of 536870912 bytes
sending 'xblbak' (2802 KB)...
OKAY [ 0.134s]
writing 'xblbak'...
OKAY [ 0.027s]
finished. total time: 0.161s
done
--------------------------------
--------------------------------
begin to flash partition tz
target reported max download size of 536870912 bytes
sending 'tz' (1916 KB)...
OKAY [ 0.165s]
writing 'tz'...
OKAY [ -0.000s]
finished. total time: 0.191s
done
--------------------------------
--------------------------------
begin to flash partition tzbak
target reported max download size of 536870912 bytes
sending 'tzbak' (1916 KB)...
OKAY [ 0.088s]
writing 'tzbak'...
OKAY [ 0.000s]
finished. total time: 0.111s
done
--------------------------------
--------------------------------
begin to flash partition rpm
target reported max download size of 536870912 bytes
sending 'rpm' (219 KB)...
OKAY [ 0.059s]
writing 'rpm'...
OKAY [ -0.000s]
finished. total time: 0.086s
done
--------------------------------
--------------------------------
begin to flash partition rpmbak
target reported max download size of 536870912 bytes
sending 'rpmbak' (219 KB)...
OKAY [ 0.023s]
writing 'rpmbak'...
OKAY [ 0.000s]
finished. total time: 0.073s
done
--------------------------------
--------------------------------
begin to flash partition hyp
target reported max download size of 536870912 bytes
sending 'hyp' (272 KB)...
OKAY [ 0.060s]
writing 'hyp'...
OKAY [ 0.028s]
finished. total time: 0.087s
done
--------------------------------
--------------------------------
begin to flash partition hypbak
target reported max download size of 536870912 bytes
sending 'hypbak' (272 KB)...
OKAY [ 0.027s]
writing 'hypbak'...
OKAY [ 0.000s]
finished. total time: 0.054s
…………………………..<< truncated the outputs>>>>>…………………………
done
--------------------------------
...
OKAY [ 0.081s]
finished. total time: 0.081s
...
OKAY [ 0.079s]
finished. total time: 0.079s
...
OKAY [ -0.000s]
finished. total time: 0.039s
All is download​
12. When everything done, the phone should reboot and you should have your phone restored to original stock Rom.
13. For my case, I can still normally get the OTAs so my phone can be updated to the latest updated Rom available from Asus
There is already a post with a very similar procedure, but already tested and approved by several people...
https://forum.xda-developers.com/as...ow-to/guide-revert-to-stock-rom-lock-t3798420
Is there any difference or advantage in your procedure?
When i do this it show 1 was not expected at this time

please help me

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.

Question Redmi Note 10 5G bricked

I've got to unbrick my phone, I think.
I can't boot into system or recovery cause my phone is bricked.
What should I do?
When I start fastboot and try to flash twrp, ther comes this message:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery 4_twrp.img
target reported max download size of 134217728 bytes
sending 'recovery' (65536 KB)...
OKAY [ 1.532s]
writing 'recovery'...
FAILED (remote: This partition doesn't exist)
finished. total time: 1.563s
This is an a/b device , use fastboot flash boot instead of fastboot flash recovery

Categories

Resources