Hello all,
I have a Mate 10 Pro that I was having trouble updating, I assumed due to having TWRP installed. So, I tried to restore the stock recovery via fastboot flash.
However, the flash would always fail with "remote: Command Not Allowed" error. Googling showed this to be result of locked bootloader, but my phone was indeed unlocked. Indicated on the screen when in Download mode.
Some threads suggested relocking and then unlocking the bootloader again. So I ran fastboot oem relock, which restarted and factory reset the phone. Then I ran fastboot oem unlock and I am now getting the "remote: Command Not Allowed" error, and my phone remains locked and now it will not boot at all but only to the eRecovery screen which wants to connect to wifi and download a package but getting package info always fails. Oh, and since I didn't think to remove my account, the phone is also FRP locked.
I had found a thread before this incident saying to change the DNS in order to get the eRecovery download to work, and at the time it did. Now the only thread I find with that suggestion (81.177.139.39, not sure it's the same one) it still fails to get package info.
So as it stands I have a FRP locked, bootloader locked Mate 10 Pro that will only boot to eRecovery.
Anyone have any suggestions?
This guide is to help you recover from “The system has destroyed screen” on Redmi Note 7 Pro
I presume the bootloader is unlocked on your device.
The things you need are (Links are provided below):
1: VB meta and Peter’s TWRP (zip)
https://drive.google.com/open?id=1kd9H2cBsjkN-9oa2_6Sj8OlXLTfpRjNN
2: Platform tools (latest)
https://developer.android.com/studio/releases/platform-tools
Install Platform Tools to windows
First turn off the phone, and put it to fastboot mode by pressing the “Power button" and holding the "Volume down button" and release them when the fastboot mode screen appears.
Connect the phone to PC by USB cable, Place the “vbmeta.img” in a folder, hold shift and right click the blank space in the folder and select “Open powershell window here” (command prompt for windows 7)
Type fastboot devices and enter , you will see your device in the list.
Enter the command “fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img” and press enter.
After flashing vb meta, Its time to flash TWRP to retain the ability to flash rom again. To do that, place the “recovery.img” file in the same folder as “vbmeta.img”. open the powershell again by the method above, enter the command “fastboot devices” to ensure the device is connected. After that, enter the command “fastboot flash recovery recovery.img”, you will get success message below.
Now hold the “Power button” and “Volume up Button” and release the “Power button” as soon as the redmi logo appears while still holding the “Volume up button” till the twrp logo appears.
Flash Rom and you are set.
If you are trying to flash MIUI,
Download latest MIflash tool here and install it on windows.
https://androidfilehost.com/?fid=889764386195900328
Download latest fastboot rom for Note 7 Pro from below link and place the folder on desktop
http://en.miui.com/a-234.html
Open MIflash tool and put device to fastboot (steps to boot to fastboot are above), connect to pc via USB, click the refresh button on the flash tool and start.
The tool takes approx 400-500 seconds to complete , once its finished it will show in a green coloured text that its successfully completed.
Enjoy
DISCLAIMER
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here before flashing it!
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
This Video can also help how to flash Note 7 Pro Using MI flash tool..
https://youtu.be/t8zqIMw-Zsc
i tried but after this step
Enter the command “fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img” and press enter.
it gives error disable verity unknown command. if i use fastboot flash vbmeta vbmeta.img it flashes sucessfully, i then install custom recovery and that flashess correctly too but when booting to recovery it still says system destoyed.
I recovered from the same issue with a newer fastboot version and LOS Twrp
ustaadg said:
i tried but after this step
Enter the command “fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img” and press enter.
it gives error disable verity unknown command. if i use fastboot flash vbmeta vbmeta.img it flashes sucessfully, i then install custom recovery and that flashess correctly too but when booting to recovery it still says system destoyed.
Click to expand...
Click to collapse
I got this same issue and then I downloaded the newer fastboot from a third party site. I assume you would had installed ADB and Fastboot systemwide(The one that requires Y as an answer and runs in blue command prompt) That one is like 1.3. You need to install a newer fastboot for this command to work.
I am not sure which one was it that I had but I am adding the link to the same. Newer Fastboot and added vbmeta
Also, I didn't install the Peter's Recovery because I was installing Lineage OS and used the recover_twistloop with wrappedkey for the same
Original Thread Here: LinegaOS16_RN7Pro
One more important thing: I didn't use "fasboot boot <recovery>" for it. I turned off the device and then used "Power Key + Volume Up". At first it didn't work but after one reboot it worked, and this is the only method I am using to go into recovery NOT VIA FASTBOOT or from inside the system. You can try it but it didn't work.
“fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img”
P.S: I thought it was verify the first time I saw it.
Also, I really hope you are not going to install MIUI either via Fastboot or Recovery. If you are going to do check roll-back protection. First check your current roll back index and check the rollback in fastboot folder of the Fasboot ROM that you are going to install. More details here. WARNING. MUST READ THIS ARTICLE IF YOU ARE THINKING OF RE-FLASHING MIUI/EUMIUI AT ANY POINT OF TIME.
You will be doomed if you didn't read this. And not in a usual way like a bricked phone. You will need to visit the service center and maybe a month wait for the device to get fixed
Thanks for replying. I downloaded fastboot rom and flashed that with clear all and lock option.
Unlocked again, installed evolution rom and even tried aosipderpfest but whenever I tried installing magisk or after reboot phone stuck on phone is starting and it won't start, I can access settings but nothing else.
Finally wooed everything, installed EU rom then evolution rom. Then magisk now everything is smooth.
I installed the latest IN Global firmware
Now I have the message
"This MIUI version can't be installed on this device" and the unlock is gone
Now when I try with XiaoMiFlash I have error: "Flash xbl error"
And miunlock says 99% This device is not bound to this account
I don't know what to do now
Spleeny97 said:
I installed the latest IN Global firmware
Now I have the message
"This MIUI version can't be installed on this device" and the unlock is gone
Now when I try with XiaoMiFlash I have error: "Flash xbl error"
And miunlock says 99% This device is not bound to this account
I don't know what to do now
Click to expand...
Click to collapse
Xbk eror is related to baseband lock. I saw one video where following was mentioned
Put phone in fastboot mode
In adb use command fastboot oemlock
After that reboot and follow the miflash method with bottom option erase and lock selected. You need to download fastboot rom.
After you set up the device again. Go to developer settings and enable oem unlock and bind the account from there
(bootloader) Device is already locked!
"Flash xbl error"
I tried
violet_images_V10.3.10.0.PFHCNXM_20190725.0000.00_9.0_cn
violet_images_V10.2.5.0.PFHCNXM_20190316.0000.00_9.0_cn
osm bro you just save me thnx alot bruh
I tried to go back to miui11 from pixel experience(10) by flashing a fastboot rom using mi flashtool (clean and lock). the result of flashing is shown as successful but the device is not booting, instead it is showing 'the system has been destroyed'. i tried unlock the device using mi unlock and it unlocked succesfully and booted succesfully . then i locked the device using the command 'fastboot oem lock' and rebooted. but the eroor 'the system has been destroyed is coming'. after several attempts i found that locking bootloader is causing the error. can anybody tell why is this happening and way to succesfully lock my bootloader.
dineshp953 said:
I tried to go back to miui11 from pixel experience(10) by flashing a fastboot rom using mi flashtool (clean and lock). the result of flashing is shown as successful but the device is not booting, instead it is showing 'the system has been destroyed'. i tried unlock the device using mi unlock and it unlocked succesfully and booted succesfully . then i locked the device using the command 'fastboot oem lock' and rebooted. but the eroor 'the system has been destroyed is coming'. after several attempts i found that locking bootloader is causing the error. can anybody tell why is this happening and way to succesfully lock my bootloader.
Click to expand...
Click to collapse
did you found the solution??
i am getting the same error
I have two Redmi Note 7 Pro devices. (Global Devices - A.K.A Indian Variant)
first device is unlocked but no custom rom installed like ever
second device is unlocked with lots of custom rom history
While trying to relock my bootloader with MIFLASH (clean all and lock) and Global firmware 11.0.8
First device firmware flash worked perfectly and bootloader is set to lock state - (Widevine status is L1 )
Second device as stated in OP . Flashing success but device showing "SYSTEM HAS BEEN DESTROYED". If i unlock the bootloader of the device then it boots normally but device is in unlock state (widevine status L3)
I think some modifications might have happened to some system partitions which causes the VBMETA - SRCLIST check failure.
ANY DEVS PLEASE LOOKS INTO THIS ISSUE ...
Yeah someone out there I"m trying to relock bootloader bcoz to get access to my corporate mails , netflix HD content and GPAY
(On other hand magisk is having CTS profile check failure as google changed the approach to check the unmodified system)
hi..
Greetings to every Android Magicians out there...!
Device:- MiA1 (Never rooted)
1.USB debugging was enabled and OEM is not enabled.
2.Hence Boot loader is Locked.
3. Adb drivers installed in my laptop.
4.Windows driver signature are disabled.
5. Xaiomi flash tool and drivers installed.
6. Qualcom HS-USB Diagnostics 900E installed.
7. Can be enter in fastboot mode and edl mode as well.
The problem:- My MiA1 was never rooted (USB debugging was enabled and OEM is not enabled.).
All apps are force stopped suddenly while using the phone so tried to reboot my devices,
and there it begins.. it stuck at boot logo.
Things i have tried:
1. Fastboot Mode:
Since the boot loader is locked i cant flash Any ROM through fastboot so i tried to enter in EDL mode through CMD.,But failed.
so i just open the back panel & however entered in EDL mode by Testpoint.
(and i've tried in fastboot through cmd { fastbooot oem unlock } it says successful but when i check the status through
{fastboot oem devices-info} but the bootloader is still locked).
2. Test Point Method:
I tried to flash MiA1 official global version ROM's (7,8,9 as well) through Xaiomi Flash tool(2015,2016,2017 versions) by test point Methods.
i have encountered the problems like AKC don't match and Cant receive Hello packets.
However i have got solved this Prolems by using Beta version of Xaiomi Flash tool.
3. When i flash (tissot_images_7.8.23_20170823.0000.00_7.1_61cf97d794) flashing was successful but devices still stuck at
Androidone logo.
Tried to flash other versions of ROM (tissot_images_V10.0.4.0.PDHMIXM_9.0) flashing was successful but devices still stuck at
Androidone logo.
By the way i have tried it using different type C cables and different ports (COM5, COM20,COM40 etc) and and different laptop as well but No luck.
i hope you guys do some Magic and help me out.
Thank you so Much for reading this thread.
Hi,
I tried to install twrp on my device and must have done something wrong. I then tried to use one of the fastboot roms to go back to stock. However, this didnt work and i was unable to boot past the fastboot bootloader. For some reason i then decided to run 'fastboot oem lock' and have locked the bootloader. I understand that was stupid and now i'm stuck at a screen that says 'Your device is corrupt. It can't be trusted and will not boot'. Is it possible to fix this or have i permanently bricked this. Thanks for any answers and i'll happily get any other information you need.
Also i have seen the thread that says to use the msm tool to reflash the stock firmware/unbrick but i can't get the device to go into EDL mode. Every time i hold the volume + and - buttons while booting the device shows up on my pc for about 5 seconds before disconnecting. Sorry if i've misunderstood these instructions but i've tried it so many times and it just doesn't seem to go to EDL mode.
Keep trying with MSM tool. It can be very finicky from what I've heard.
Try different usb ports, maybe different cable or computer.
Since you can start your device it's not really hard bricked and you should be able to restore it completely.
Sent from my OnePlus7TPro using XDA Labs
No need to worry.
Flashing the stock rom with fastboot did not work because you have relocked the bootloader. Unlock the bootloader again with fastboot oem unlock and then flash the fastboot stock rom. It would work just fine and you would be able to boot into stock rom.
Is it possible to install twrp recovery and root using magisk in this phone or not possible because of mediatek processor?
Bhai have patience , this is Mediatek we all know but another thing to notice is This is MT- g95 SoC ?
Orange state in realme 7 when bootloader unlocked but unable to use fastboot.
I have unlocked my realme 7 bootloader with in-depth test built for realme 6 pro. It is working. But now after unlocking the phone factory resets itself and when trying to go into fastboot mode with ADB command ADB reboot bootloader the fastboot verify check fails all the time. So how to go into fastboot mode after bootloader unlock. This issue never happened when I start in-depth test after permissions. It's very strange that even after unlocking the phone is not booting into fastboot mode while giving error in verification. Guys can anyone knows how to solve this. Please reply asap.
Realme 7 After unlocking the bootloader is not going into fastboot mode again.
Can anyone tell when twrp for realme 7 wipp be available
I think i made a mistake by choosing mtk soc because it's hard chance to get twrp for mtk soc
Simple solution realme 7
Senxco said:
I have unlocked my realme 7 bootloader with in-depth test built for realme 6 pro. It is working. But now after unlocking the phone factory resets itself and when trying to go into fastboot mode with ADB command ADB reboot bootloader the fastboot verify check fails all the time. So how to go into fastboot mode after bootloader unlock. This issue never happened when I start in-depth test after permissions. It's very strange that even after unlocking the phone is not booting into fastboot mode while giving error in verification. Guys can anyone knows how to solve this. Please reply asap.
Click to expand...
Click to collapse
I think your adb driver not working please install adb driver reinstall and verfiy fails problem solve, thanks
No no adb driver is working and tested on other devices. I think the problem is with smartphone serial key ( It shows serial key mismatch and therefore fastboot unlock verify fail in fastboot mode).
To Root you phone:-
Download your device boot image > download magisk manager > patch your device boot image > go to fastboot mode > type in command >fastboot --disable-verity--disable-verification > flash vbmeta (fastboot flash vbmeta (put your vbmeta path here) > flash magisk patched image (fastboot flash boot (put your patched file path here) now reboot your phone it will be rooted if on First boot it didn't then reboot your device