Hello,
USB Debugging is on
Bootloader is unlocked
HiSuite is up to date
Correct ADB Drivers are installed
and my device is recognized in both "adb devices" and "fastboot devices"
The problem: I'm trying to flash a TWRP recovery, but I keep getting the error "Failed (remote: Command not allowed)".
I don't know what's wrong, and I don't see any other way how I'd be able to flash a custom recovery. I'm trying to get my phone rooted ASAP.
I also get the same error when I type "fastboot oem device-info" for example, it's so weird I get so frustrated by phones sometimes :silly:
Hope anyone can help me out
Oh and I own a Huawei Honor 7 (PLK-L01 aka plank)
*BUMP*
Anyone who can help me out, please?
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,
this is my first post of any kind in this sort of forum, so I apologize in case of any mistakes. I am currently trying to root my Doogee Y7 with the help of the adb tool and am running into different issues.
Phone details:
Model: Doogee Y7
OS: 8.1.0 (Kernel 4.4.83+)
Board: sp9863a_1h10
CPU: ARM Cortex-A55
According to my developer options the bootloader is unlocked, however in CPU-Z the loader is marked as unknown. Fastboot cannot be accessed via button combinations, but only through the command 'adb reboot bootloader'. Currently, when my phone is in fastboot, there is a small info note in the top left saying 'lock flag is: unlock' which - while restarting - gets the addition 'skip verify!!!'.
Any commands that interact with the bootloader (e.g.: fastboot flashing unlock) come back with the following error: FAILED (remote: Not implemet.). 'fastboot oem unlock' returns 'FAILURE (remote: unknown cmd.)'. When trying to flash a boot image via 'fastboot flash boot boot.img' the file transfers to the phone without issue. It then gets stuck in the writing process. The phone and PC can then not interact with each-other anymore. Unplugging and re-plugging the phone end with fastboot not being authorized anymore. I can still reboot my phone by pressing 'Vol UP + Power'.
Other than that, I have tried many different one-click rooting apps of which none had any real effect.
I really hope someone can help me. Thank your for your time, have a wonderful day.
Regards,
After doing a flash for new pixel experience PixelExperience_Plus_beryllium-11.0-20210823-0645-OFFICIAL, phone restarted and then no other option for access. Boots into twrp logo and stuck.
adb devices in command prompt show device and recovery.
When I do bootloader into fast boot,
fastboot devices shows
??????? fast boot
then disconnects. (after this it doesnt progress any further and disconnects from pc).
cant fastboot any files as it has error, my boot loader is unlocked and was on pixel experience 10 prior.
what are my next steps?
the teamwin recovery is 3.2.3-0
kmkzboi said:
After doing a flash for new pixel experience PixelExperience_Plus_beryllium-11.0-20210823-0645-OFFICIAL, phone restarted and then no other option for access. Boots into twrp logo and stuck.
adb devices in command prompt show device and recovery.
When I do bootloader into fast boot,
fastboot devices shows
??????? fast boot
then disconnects. (after this it doesnt progress any further and disconnects from pc).
cant fastboot any files as it has error, my boot loader is unlocked and was on pixel experience 10 prior.
what are my next steps?
the teamwin recovery is 3.2.3-0
Click to expand...
Click to collapse
Use the latest Official TWRP since the one you have now is outdated and do clean install according the guide at POCO F1 Ultimate Collection & Guides. (You need to format data not just wipe) You can find everything you need there.
first time i turned on phone today, i was able to to do command fastboot devices and it actually showed the device id, then when i tried to flash it stopped and then everytime i connect it wont even show fastboot devices without showing ???????? and shutting down again.
ive tried installing uninstalling the drivers and boot loader drivers, i believe its something to do with that, otherwise it has unlock symbol when it gets stuck on twrp logo, then when i put into fastboot it doesnt have unlock symbol before fastboot splash, what could it be? (im unable to flash anything without getting
1. running fastboot flash/boot/ any command really
Sending 'recovery' (1551913 KB) FAILED (Write to device failed (Unknown error))
fastboot: error: Command failed
2. running command then connecting phone already in fastboot
< waiting for any device >
FAILED (Write to device failed (Unknown error))
fastboot: error: Command failed
kmkzboi said:
first time i turned on phone today, i was able to to do command fastboot devices and it actually showed the device id, then when i tried to flash it stopped and then everytime i connect it wont even show fastboot devices without showing ???????? and shutting down again.
ive tried installing uninstalling the drivers and boot loader drivers, i believe its something to do with that, otherwise it has unlock symbol when it gets stuck on twrp logo, then when i put into fastboot it doesnt have unlock symbol before fastboot splash, what could it be? (im unable to flash anything without getting
1. running fastboot flash/boot/ any command really
Sending 'recovery' (1551913 KB) FAILED (Write to device failed (Unknown error))
fastboot: error: Command failed
2. running command then connecting phone already in fastboot
< waiting for any device >
FAILED (Write to device failed (Unknown error))
fastboot: error: Command failed
Click to expand...
Click to collapse
Check AMD Ryzen Fastboot Fix at the thread I posted above. If you have Intel system just install the Fastboot Drivers which is there (at the thread) and check.
Hello,
I have a p20 lite stuck in a boot loop. I tried installing an A13 gsi, stopped booting to the system. Tried reinstalling EMUI from erecovery and doing a factory reset, still stuck in a boot loop. I can reboot to TWRP, fastboot and erecovery, but booting to system gets to the huawei logo with a jingle (past the this phone cannot be trusted screen), then reboots.
Command info from fastboot:
fastboot oem get-build number:
ANE-LX1 8.0.0.180(C432)
fastboot oem get-product-model:
ANE-LX1
fastboot getvar vendorcountry:
vendorcountry: hw/eu
fastboot oem oeminforead-CUSTOM_VERSION:
FAILED (remote: 'Read oeminfo failed!')
fastboot: error: Command failed
fastboot oem oeminforead-SYSTEM_VERSION:
ANE-LX1 8.0.0.180(C432)
The device shows up in device manager as "Android Sooner Single ADB Interface", fastboot recognizes it, I can transfer files via MTP, it just doesnt boot to the system.
I do have the bootloader code saved, so it does not matter if it relocks.