Bootloader re-locked and now "System Destroyed" with no solutions - Xiaomi Redmi Note 7 Questions & Answers

Hi all, I had official MIUI Global 11 on Android 10 on a phone with unlocked bootloader and a recovery. I wanted to re-lock the bootloader, so I went to fastboot and I gave the command to lock it.
Obviously (but I didn't even imagine it) the devide DID lock, but now it doesn't start any longer. ""System destroyed" is the message.
What I want to get is one of these two results: having a working phone OR having everything erased.
What I have already tried is:
- installing a firmware via fastboot: failed because the bootloader is locked
- flashing single .img via fastboot: failed because the bootloader is locked
- erase partitions: failed because the bootloader is locked
- unlock again the phone via fastboot: failed
- unlock again the phone via Mi Unlock: failed because missing authorization in developer options
Let's add the fact that I don't have windows, but Mac, that reduces the available options.
ANY SUGGESTIONS?

You can use Platform tools in windows.As far as i know platform tools can be used both locked and unlocked bootloader.You can search on YouTube how to flash mi phones through platform tools.

francanna said:
Hi all, I had official MIUI Global 11 on Android 10 on a phone with unlocked bootloader and a recovery. I wanted to re-lock the bootloader, so I went to fastboot and I gave the command to lock it.
Obviously (but I didn't even imagine it) the devide DID lock, but now it doesn't start any longer. ""System destroyed" is the message.
What I want to get is one of these two results: having a working phone OR having everything erased.
What I have already tried is:
- installing a firmware via fastboot: failed because the bootloader is locked
- flashing single .img via fastboot: failed because the bootloader is locked
- erase partitions: failed because the bootloader is locked
- unlock again the phone via fastboot: failed
- unlock again the phone via Mi Unlock: failed because missing authorization in developer options
Let's add the fact that I don't have windows, but Mac, that reduces the available options.
ANY SUGGESTIONS?
Click to expand...
Click to collapse
I think that the only way to flash it successfully again is to use QPST ,but you need to open the phone remove battery and get 9008 port , check in YouTube.

Related

Problems with unlock/relock bootloader and TWRP flashing

Hi, I have Asia-Pacific version of the Huawei Mediapad M3 (BTV-W09C209B005). I'm trying to flash TWRP to gain root access, but I'm encountering problems in the preliminary stage. I've searched for similar problems in the forum, but couldn't find a solution that works for me.
So here are the steps I've done:
1. I received the official bootloader code from Huawei.
2. I used ADB and Fastboot to unlock the bootloader, but I noticed something peculiar: the screen says
Phone UNLOCKED
FRP UNLOCKED
I am the first owner of the tablet, so I was surprised to see that it was already unlocked. In any case, I tried the fastboot oem unlock command, and it returned this error:
FAILED (remote: password wrong)
3. I tried to proceed to TWRP flash on the assumption that the phone was already unlocked. But I get this error:
sending 'recovery' (23794 KB)....
OKAY [ 0.740s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished, total time: 0.740s
4. I tried relocking the bootloader, as per several XDA threads, before unlocking again. But I once again encounter an error:
FAILED (remote: stat not match)
I already contacted Huawei to make sure that the unlock code they sent me was correct, but I doubt that it'd be wrong because they probably just paste it after generating it in the system.
Any ideas how to proceed?
Interesting, first off if you want to check and see if you phone is BL is unlocked go to Settings, Developer Options and see if your OEM unlocking is grayed or doesn't move..if it doesn't move or grayed out then it's unlocked.. if it moves the it not unlocked.. check that your fastboot /adb are set up correctly. Though the easiest way to this ( unlocking the BL and flashng TWRP) would be to get Huawei Multi-Tool v8 by Team MT and use it,, ( grab the one in the Honor 8, as I know it does work) and make sure you ave the correct TWRP for your tablet..
lilbrat said:
Interesting, first off if you want to check and see if you phone is BL is unlocked go to Settings, Developer Options and see if your OEM unlocking is grayed or doesn't move..if it doesn't move or grayed out then it's unlocked.. if it moves the it not unlocked.. check that your fastboot /adb are set up correctly. Though the easiest way to this ( unlocking the BL and flashng TWRP) would be to get Huawei Multi-Tool v8 by Team MT and use it,, ( grab the one in the Honor 8, as I know it does work) and make sure you ave the correct TWRP for your tablet..
Click to expand...
Click to collapse
Thanks for pointing me the Huawei multi-tool. So I tried that, and as suspected, the device is still locked. I am able to toggle the OEM unlocking and the tool says so through the lock status (oem lock-state info LOCKED). I proceeded unlocking with the tool, but I received the same error: FAILED (remote: password wrong)
The unlock code doesn't seem to be the problem because the tool displayed the corresponding serial number and it was a match. So there's something preventing me from unlocking the bootloader--it's probably the same reason why the fastboot says "PHONE Unlocked" even though it actually isn't. Again, I can't do the relock trick because the device wouldn't accept the Huwei unlock code.
Thoughts?
Hmm, why do some of these seem to be so picky when it comes to unlocking.. The multi too will copy what ever code you but in, sorry for the questions just trying to help narrow it down.. in the developer section there are 3 things that need to be ticked,, OEM unlocking, USB debugging and and allow ADB debugging in charge only mode.. Maybe you software got out of wack.. read here ( https://forum.xda-developers.com/mediapad-m3/help/bricked-mediapad-m3-t3746893) as it may help.. Not sure if HiSuite can restore it.
OEM unlocking and USB debugging are "working" in the sense that I can send commands from the PC via USB. It's just that I can't properly unlock the phone. I updated the drivers to see if that's the problem, but I still encounter the same error. I basically couldn't move forward with the link you sent because the first step was to unlock the device and I couldn't get past that. When I try to unlock the error is still 'FAILED (remote: password wrong)'.
I've seen some threads from other Huawei devices that suggest rolling back the firmware, but this is the first time I'm trying to root this device. And it's still on Marshmallow, which is the version that came with the first release of the Mediapad M3, so basically there's nothing to roll back to.
Why not upgrade to 7 as that is where most of the newer threads are written for plus it will redo your boot loader... giving you a clean slate to work with..and that might be your issue..
I can't update to 7 because Huawei stopped providing updates for my region. I failed to mention that the reason why I'm trying to unlock the device is to change the region and upgrade to 7.
May I ask where you are?
From Southeast Asia, but the tablet was imported from China. I planned to convert it to the European version so I can at least upgrade to Nougat. I'm still stuck though.
So Huawei sent me a new unlock key and it works! Problem solved!
cescpistol said:
From Southeast Asia, but the tablet was imported from China. I planned to convert it to the European version so I can at least upgrade to Nougat. I'm still stuck though.
Click to expand...
Click to collapse
Imy model also seas... Has updated to nougat without changging to us.

Flashing Help - Mismatching image and device

Hi All,
Trying to flash an A1 with the following rom images and both give the error of Mismatching image and device.
tissot_images_V9.5.9.0.ODHMIFA_20180316.0000.00_8.0_f8cd1b4e8e
tissot_images_V9.5.11.0.ODHMIFA_20180504.0000.00_8.0_1a04581058
The phone is currently a brick belonging to a friend of mine, and I would like to try and get it back up and running. Fastboot can see the device, as can MiFlash, but when running the command
Code:
Fastboot oem device-info
it throws an error stating
Code:
FAILED (Command write failed (Unknown Error))
Any ideas? The device will boot into fastboot but no further, and gives a warning about being unlocked when you try to boot. I'm not sure how to check if it is a re-branded Mi5x or not, as the box is a Global version A1 box with corresponding IMEI cods to a model MDG2. The phone does have the Android One laser etch on the back however.
By bricked I mean the phone will turn on, load the warning about an unlocked bootloader and then go to the Android One "bars" screen you see before the pretty android one loading screen. Here it just stops.
The drivers i'm using come from the MiFlash install, and I've tried doing a TWRP install with fastboot but still no joy. Fastboot can see the device, and talk with it, but nothing I seem to do has got the kit back working.
Anyone able to give some help or advice?
Further info on what ive tried here
http://en.miui.com/thread-3158263-1-1.html

Huawei P10 Plus back to Stock Firmeware / Recovery

Hello everyone,
I have a Vky-l09c432 Huawei P10 Plus with an working System. So I would like to Update the System from Nougat to Oreo, and there is a small problem, which I cannot deal with. So maybe here is someone who has a good tipp for me. The Phone is not rooted, but has the bootloader unlocked.
The Thing is, that I have broken any Recovery installed (There no stock recovery or no TWRP).
So I tried to flash a recovery / System / Boot or whatever via. Fastboot Mode. If I try to do this the command prompt shows up with the fallowing error: failed (remote command not allowed).
All Drivers are installed correctly and in HiSuite the phone shows up too.
So the Debugging Mode is activated, but I cannot active OEM in developer Tools, because its grayed out. And I cannot also relock the bootloader again to use OEM in Developer Option. I don't have the Bootloader Code anymore.
Is it Right, that I cannot flash (failed (remote command not allowed). ) because of the OEM Setting ? (Fastboot devices shows up correctly)
With the Dload Methode, I also have a Problem, because the Files are to great for my SD Card (4GB+).
Is there any Option to install a Recovery (custom or Stock...) on my phone again ?
Kind Regards & Thank you a lot
Chip

Bootloader Unlock

Hello all! I have been trying to unlock my bootloader on my SGP311. I have searched the threads, followed the instructions, and still have problems. i initially looked at my service menu to determine if it is unlockable and it said yes. I then went through the steps to unlock it and it kept saying failed. Then, it finally worked, and my tablet rebooted. i got dual recovery loaded and then proceeded to wipe and install lineageOS from recovery. recovery kept failing to install the new rom. i then had to reflash a stock rom because the tablet wouldnt even boot into recovery again. now my service menu simply says rooting status: unknown and says nothing about the bootloader. What the heck happened?
Gilly86 said:
Hello all! I have been trying to unlock my bootloader on my SGP311. I have searched the threads, followed the instructions, and still have problems. i initially looked at my service menu to determine if it is unlockable and it said yes. I then went through the steps to unlock it and it kept saying failed. Then, it finally worked, and my tablet rebooted. i got dual recovery loaded and then proceeded to wipe and install lineageOS from recovery. recovery kept failing to install the new rom. i then had to reflash a stock rom because the tablet wouldnt even boot into recovery again. now my service menu simply says rooting status: unknown and says nothing about the bootloader. What the heck happened?
Click to expand...
Click to collapse
You can't install LOS Rom from the dual recovery (XZDR). By flashing stock ROM, you bootloader may be locked again.
Check this guide to unlock it, and install LOS.
It simply will not let me unlock the bootloader anymore. And I can't seem to find a firmware that I can flash to get me to the appropriate version
so far, part of the problem is flashtool in androxyde still using the command fastboot -i 0x0fce oem unlock 0xkey. windows 10 denies this command every time and should be fastboot oem unlock 0xkey. But even doing so manually through the cmd prompt, it still will not let me unlock the bootloader. does anyone have a ftf file that has an unlockable bootloader? seems mine locked up completely when i reflashed the rom
Gilly86 said:
so far, part of the problem is flashtool in androxyde still using the command fastboot -i 0x0fce oem unlock 0xkey. windows 10 denies this command every time and should be fastboot oem unlock 0xkey. But even doing so manually through the cmd prompt, it still will not let me unlock the bootloader. does anyone have a ftf file that has an unlockable bootloader? seems mine locked up completely when i reflashed the rom
Click to expand...
Click to collapse
bootloader is in device, not in firmware, so no such firmware exist you ask for.

How to recover my data??! - terrible scenario

Hello to all gurus here
my Redmi Note 7 had a screen broken...I can only hardy recognize when it's in fastboot or recovery.... Touch not working.
The bootloader is locked, I am not sure if USB Debugging was enabled, but I suppose it was not because I get the following:
C:\MyDocs\TEMP\Varie\platform-tools>fastboot oem unlock
FAILED (remote: 'Token Verify Failed, Reboot the device
')
fastboot: error: Command failed
In this terrific scenario, is there any way on earth to recover my data?
I can only see my device in fastboot mode for what I can say...
On the other hand I could probably install a TWRP (which should already have debugging enabled) using fastboot but it seems to me it should clear all my user data.
Any way out?
Thanks in advance
unlocking bootloader requires bonded mi account in developer options and can only unlocked from miunlock tool. btw that will erase userdata during unlock for security reasons

Categories

Resources