Database Info

I Bricked my Huawei Mate 9 MHA-L29 (C567) USA Model

-SOLVED-Hi everyone, I bricked my phone trying to downgrade from Oreo to Nougat.
I extracted the img. files from UPDATE app with Huawei extractor. and flashed via fastboot
But the same error still there.
fastboot flash kernel
fastboot flash ramdisk
fastboot flash recovery_ramdisk
The same ERROR MODE still there. plus I bought some credits on DC Phoenix and did not help at all
I download all the files but I got this error:: -FAIL Command not allowed-
I attached some pictures of the errors.
My phone is totally dead, I will really appreciate your help guys
thanks

osk4rin said:
Hi everyone, I bricked my phone trying to downgrade from Oreo to Nougat.
I extracted the img. files from UPDATE app with Huawei extractor. and flashed via fastboot
But the same error still there.
fastboot flash kernel
fastboot flash ramdisk
fastboot flash recovery_ramdisk
The same ERROR MODE still there. plus I bought some credits on DC Phoenix and did not help at all
I download all the files but I got this error:: -FAIL Command not allowed-
I attached some pictures of the errors.
My phone is totally dead, I will really appreciate your help guys
thanks
Click to expand...
Click to collapse
Fastboot flash the files from the system that you were on before you bricked it or flash twrp then use hwota8 or hurupdater to flash back to stock 8.0.

ajsmsg78 said:
Fastboot flash the files from the system that you were on before you bricked it or flash twrp then use hwota8 or hurupdater to flash back to stock 8.0.
Click to expand...
Click to collapse
I tried all the files that I mentioned and nothing happened, the error still there, TWRP is flashable but won't boot in recovery.

ajsmsg78 said:
Fastboot flash the files from the system that you were on before you bricked it or flash twrp then use hwota8 or hurupdater to flash back to stock 8.0.
Click to expand...
Click to collapse
I flashed the stock recovery_ ramdisk ramdis img. From the stock system 8.0 Oreo where the phone was.
And is stuck on - Your device is booting-
And I see no progress. After that the same Upgrade your system ERROR is back again.

osk4rin said:
I flashed the stock recovery_ ramdisk ramdis img. From the stock system 8.0 Oreo where the phone was.
And is stuck on - Your device is booting-
And I see no progress. After that the same Upgrade your system ERROR is back again.
Click to expand...
Click to collapse
Did you try the recovery from Nougat since that's what you were trying to downgrade to before you bricked it?

ajsmsg78 said:
Did you try the recovery from Nougat since that's what you were trying to downgrade to before you bricked it?
Click to expand...
Click to collapse
I did too, but won't let me flash the Recovery img. from Nougat, just the Oreo recovery
look:

osk4rin said:
Hi everyone, I bricked my phone trying to downgrade from Oreo to Nougat.
I extracted the img. files from UPDATE app with Huawei extractor. and flashed via fastboot
But the same error still there.
fastboot flash kernel
fastboot flash ramdisk
fastboot flash recovery_ramdisk
The same ERROR MODE still there. plus I bought some credits on DC Phoenix and did not help at all
I download all the files but I got this error:: -FAIL Command not allowed-
I attached some pictures of the errors.
My phone is totally dead, I will really appreciate your help guys
thanks
Click to expand...
Click to collapse
Te recomiendo que mejor flashear un rom de Openkirin para que puedas recuperar el celular, y si vas bajar a 7. 0 tendrías que haber bajada las 3 cremalleras que utiliza para hacerlo por medio de hwt8 para que lo flashes por bat. Espero te funcione

franciscojavi31 said:
Te recomiendo que mejor flashear un rom de Openkirin para que puedas recuperar el celular, y si vas bajar a 7. 0 tendrías que haber bajada las 3 cremalleras que utiliza para hacerlo por medio de hwt8 para que lo flashes por bat. Espero te funcione
Click to expand...
Click to collapse
Hola ,gracias por tu respuesta.
Que ROM the Open Kirin?Treble Project?de Oreo?
Gracias!
edited:Ya trate y no ahi algun Progreso.

use erecovery back to that firmware
---------- Post added at 09:42 AM ---------- Previous post was at 09:37 AM ----------
Vol up plus power.approve firmware for imei but using dns as suggested hicloud.doing from another phone or pc. older version firmware before pie supported.

luck2ang said:
use erecovery back to that firmware
---------- Post added at 09:42 AM ---------- Previous post was at 09:37 AM ----------
Vol up plus power.approve firmware for imei but using dns as suggested hicloud.doing from another phone or pc. older version firmware before pie supported.
Click to expand...
Click to collapse
I tried to flashed the recovery from that firmware, but.. Won't flash any Nougat img. Just Oreo
fastboot flash recovery_ramdisk recovery ramdis img.
Won't flash - fastboot flash recovery img.
By the time whe recovery_ramdisk is flashed I did power & volume up to boot into recovery, and it just goes to the message - Your device is booting -
It stays on a bootloop.

osk4rin said:
I tried to flashed the recovery from that firmware, but.. Won't flash any Nougat img. Just Oreo
fastboot flash recovery_ramdisk recovery ramdis img.
Won't flash - fastboot flash recovery img.
By the time whe recovery_ramdisk is flashed I did power & volume up to boot into recovery, and it just goes to the message - Your device is booting -
It stays on a bootloop.
Click to expand...
Click to collapse
Try doing it in command prompt instead of PowerShell.

ajsmsg78 said:
Try doing it in command prompt instead of PowerShell.
Click to expand...
Click to collapse
I tried but can't flash the Nougat recovery img.

osk4rin said:
I tried but can't flash the Nougat recovery img.
Click to expand...
Click to collapse
You have an Oreo partition table at the moment.
You aren't going to be able to flash the Nougat recovery - the N recovery image is a traditional Android boot image (kernel + ramdisk), the O recovery image is just the ramdisk; the O recovery_ramdisk partition is half the size of the N recovery partition.

irony_delerium said:
You have an Oreo partition table at the moment.
You aren't going to be able to flash the Nougat recovery - the N recovery image is a traditional Android boot image (kernel + ramdisk), the O recovery image is just the ramdisk; the O recovery_ramdisk partition is half the size of the N recovery partition.
Click to expand...
Click to collapse
I know, Oreo partition is on it.but the Build system is MHA-L29C432B126 that is why I could not flash any Recovery img from Nougat. and my Original Model is MHA-L29C567 (Oreo)
That means that my phone is dead.

osk4rin said:
I know, Oreo partition is on it.but the Build system is MHA-L29C432B126 that is why I could not flash any Recovery img from Nougat. and my Original Model is MHA-L29C567 (Oreo)
That means that my phone is dead.
Click to expand...
Click to collapse
I haven't yet gone looking too closely into this, but check the P10 guides board - there's a set of instructions there along with some scripts which you can probably use or tweak to revive your device back with Oreo at least. If you were on a recent O security patch you won't be able to roll back to Nougat anyway. (Xloader & fastboot updates in newer security patches cause downgrades to brick.)
Also, the underlying tools (hikey_idt) does work provided you've got suitable sec_usb_xoader/lpm3/fastboot images, which look to be included there.

irony_delerium said:
I haven't yet gone looking too closely into this, but check the P10 guides board - there's a set of instructions there along with some scripts which you can probably use or tweak to revive your device back with Oreo at least. If you were on a recent O security patch you won't be able to roll back to Nougat anyway. (Xloader & fastboot updates in newer security patches cause downgrades to brick.)
Also, the underlying tools (hikey_idt) does work provided you've got suitable sec_usb_xoader/lpm3/fastboot images, which look to be included there.
Click to expand...
Click to collapse
The bootloader is Unlocked as you see on the pic, but Well, I'll keep searching for a solution or just give up with this.
Thanks.

osk4rin said:
The bootloader is Unlocked as you see on the pic, but Well, I'll keep searching for a solution or just give up with this.
Thanks.
Click to expand...
Click to collapse
Bootloader unlock is different than full fastboot unlock. A full fastboot unlock allows for the flashing of any partition (including the partition table itself) via fastboot, a normal bootloader unlock only allows you to flash a selected handful of partitions.
Unfortunately, I only know of 3 ways to get that unlock:
* The backdoor used by DC Unlocker and the like
* NVME patching
* USB xloader from a board firmware package, loaded via testpoints.
If you were ever on a newer security patch, the backdoor doesn't work any longer as the key used for generating the backdoor token was changed; and since you don't have a working system or recovery, you can't do the NVME patch.

irony_delerium said:
Bootloader unlock is different than full fastboot unlock. A full fastboot unlock allows for the flashing of any partition (including the partition table itself) via fastboot, a normal bootloader unlock only allows you to flash a selected handful of partitions.
Unfortunately, I only know of 3 ways to get that unlock:
* The backdoor used by DC Unlocker and the like
* NVME patching
* USB xloader from a board firmware package, loaded via testpoints.
If you were ever on a newer security patch, the backdoor doesn't work any longer as the key used for generating the backdoor token was changed; and since you don't have a working system or recovery, you can't do the NVME patch.
Click to expand...
Click to collapse
Yes, I cant able to flash the recovery from the Nougat system. Just Oreo.
Pretty much can't do anything.

osk4rin said:
Yes, I cant able to flash the recovery from the Nougat system. Just Oreo.
Pretty much can't do anything.
Click to expand...
Click to collapse
No, you can't flash a Nougat recovery on an Oreo partition table. Absolutely won't work.
You HAVE to flash an Oreo recovery, and you probably need to make sure you've got a suitable kernel image as well in the 'kernel' partition. (As has been said before - recent security patch CANNOT roll back to Nougat. You will brick. There is no workaround, it will fail, as you have discovered. Usually the brick is worse - you don't even get fastboot. You just get the serial port in download mode waiting for a sec signed xloader & such to come down.)
This was coming to mind when you posted that:
From an Oreo package, you might try flashing the following:
kernel
recovery_ramdisk
recovery_vendor
recovery_vbmeta
Then try booting recovery. I don't remember whether fastboot will allow you to flash the other two, but at the very least I know you need a working kernel and recovery image - if flashing those will get you booting to recovery, you can probably load up an Oreo TWRP from there and possibly use hurupdater or hwota8 to flash the full system back.

irony_delerium said:
No, you can't flash a Nougat recovery on an Oreo partition table. Absolutely won't work.
You HAVE to flash an Oreo recovery, and you probably need to make sure you've got a suitable kernel image as well in the 'kernel' partition. (As has been said before - recent security patch CANNOT roll back to Nougat. You will brick. There is no workaround, it will fail, as you have discovered. Usually the brick is worse - you don't even get fastboot. You just get the serial port in download mode waiting for a sec signed xloader & such to come down.)
This was coming to mind when you posted that:
From an Oreo package, you might try flashing the following:
kernel
recovery_ramdisk
recovery_vendor
recovery_vbmeta
Then try booting recovery. I don't remember whether fastboot will allow you to flash the other two, but at the very least I know you need a working kernel and recovery image - if flashing those will get you booting to recovery, you can probably load up an Oreo TWRP from there and possibly use hurupdater or hwota8 to flash the full system back.
Click to expand...
Click to collapse
I flashed those commands and nothing happened.
Power +Volume Up trying to boot into Recovery.
My device is Just:
Your Device is booting now....
-Bootloop-
Also Same error, Please update your system
Error!
Func NO: 11 (recovery image)
Func NO: 2 (load failed!)

Bootloop, only fastboot and EDL mode no system boot please help Axon 10 Pro

hi Guys
I'm in the forum for a very long time as an assistant helper now it has got me hard I have an Axon 10 Pro with curly boot loader and trying to flash a TWRP I have somehow the device or SotA and SlotB have shrunk. The Axon Bootet permanently in 0.5 second cycle and also a FULL Restot or FULL Flash with EDL Tool has not changed anything. Likewise, a new flash about fastboot with the command (fastboot flash boot_a boot.img) the same for boot_b then try with fastboot command (fastboot boot twrp.img) Recovery to start without success fastboot erase boot_a and boot_b has also flashing new but it does not start. Always bootloop:crying::crying::crying::crying:

the Axon 10 pro is back because he had no backup of all we had from my Axon 10 pro made a backup with the edl tool (Backup all) and have then copied his efs backup purely and then this with then on the Axon 10 flashed the Axon 10 pro is now back

Where did you get the twrp from?

From udev
On his donload page
https://forum.xda-developers.com/showpost.php?p=80156866&postcount=3

I had a bootloop issue as well and even though I reflashed using the EDL tool, it doesn't erase and the errors remained, but when I entered EDL mode and reflashed using the Xiaomi Flash Tool, storage was completely erased and the device was flashed cleanly and booted correctly.

I've encountered a similar issue with my Axon (2020U version). I can boot into EDL but nothing else (no fastboot, recovery, etc.). I previously had TWRP up and running successfully, not sure what happened.
Is there a full EDL zip or similar that I can flash to return everything to stock? I tried restoring with the EDL tool but with no success

jbeaulieu said:
I've encountered a similar issue with my Axon (2020U version). I can boot into EDL but nothing else (no fastboot, recovery, etc.). I previously had TWRP up and running successfully, not sure what happened.
Is there a full EDL zip or similar that I can flash to return everything to stock? I tried restoring with the EDL tool but with no success
Click to expand...
Click to collapse
The reason the EDL tool may not work is that is doesn't have the capability to erase. The boot loop that occurs is usually due a corrupt bootfile. Use the MiFlash fastboot recovery tool. Make sure to select the clean all button at the bottom. Place your phone in EDL mode. Hit refresh to make sure your phone is detected. Select the EDL file and then hit flash.

jim262 said:
The reason the EDL tool may not work is that is doesn't have the capability to erase. The boot loop that occurs is usually due a corrupt bootfile. Use the MiFlash fastboot recovery tool. Make sure to select the clean all button at the bottom. Place your phone in EDL mode. Hit refresh to make sure your phone is detected. Select the EDL file and then hit flash.
Click to expand...
Click to collapse
Apologies for my ignorance - what exactly am I flashing? I see the "clean all" radio button, but I'm not sure what EDL package to flash after selecting that option - is there a 2020U package floating around that I'm not seeing?

jbeaulieu said:
Apologies for my ignorance - what exactly am I flashing? I see the "clean all" radio button, but I'm not sure what EDL package to flash after selecting that option - is there a 2020U package floating around that I'm not seeing?
Click to expand...
Click to collapse
The EDL package, use the same EDL package that you used with the EDL tool. Just select the "clean all" radio button. Select the path to the EDL , hit refresh once phone, in EDL mode, is detected, hit flash.

jim262 said:
The EDL package, use the same EDL package that you used with the EDL tool. Just select the "clean all" radio button. Select the path to the EDL , hit refresh once phone, in EDL mode, is detected, hit flash.
Click to expand...
Click to collapse
Okay, I'm trying to use MiFlash to restore the backup I took through the original EDL tool. The MiFLash tool is only timing out with a "cannot receive hello packet" - was this something you encountered as well?

jbeaulieu said:
Okay, I'm trying to use MiFlash to restore the backup I took through the original EDL tool. The MiFLash tool is only timing out with a "cannot receive hello packet" - was this something you encountered as well?
Click to expand...
Click to collapse
I did attempt to flash the wrong EDL file (They are region and device specific) and received that error. I have the Chinese version and once I downloaded the correct EDL file, I had no issues I have even maintained an unlocked boot loader, flashed Magisk and taken OTAs.

jim262 said:
I did attempt to flash the wrong EDL file (They are region and device specific) and received that error. I have the Chinese version and once I downloaded the correct EDL file, I had no issues I have even maintained an unlocked boot loader, flashed Magisk and taken OTAs.
Click to expand...
Click to collapse
Ah, okay. I have the US version - A2020U. Unless I'm mistaken, it looks like there isn't a full EDL zip file available for my version yet, so I might be stuck

There were EDL files up, but apparently they were taken down for some reason.

in the russians there are the 1.6 of the g model as edl (which one can use in a brick) but I do not know if this is synonymous with the u model as you would have to ask @Unjustified Dev or something
@MOD
I hope that the links are allowed here else delete please
1.6 g model edl
http://4pda.ru/forum/index.php?showtopic=965431&st=0#entry88768840
And the lonk too the forum
http://4pda.ru/forum/index.php?showtopic=965431

Chris axon 7 said:
in the russians there are the 1.6 of the g model as edl (which one can use in a brick) but I do not know if this is synonymous with the u model as you would have to ask @Unjustified Dev or something
@MOD
I hope that the links are allowed here else delete please
1.6 g model edl
http://4pda.ru/forum/index.php?showtopic=965431&st=0#entry88768840
And the lonk too the forum
http://4pda.ru/forum/index.php?showtopic=965431
Click to expand...
Click to collapse
Thanks for sharing these. @Unjustified Dev do you happen to know if the 1.6 2020G EDL would be able to be flashed to a 2020U model to recover from a brick? Or if not, is there a place to obtain the proper files, either here on the forums or via PM?

jim262 said:
I did attempt to flash the wrong EDL file (They are region and device specific) and received that error. I have the Chinese version and once I downloaded the correct EDL file, I had no issues I have even maintained an unlocked boot loader, flashed Magisk and taken OTAs.
Click to expand...
Click to collapse
Please share us the EDL file for the Chinese version.

has anyone found the US EDL file yet?

Futility's Forgotten Soldier said:
has anyone found the US EDL file yet?
Click to expand...
Click to collapse
Still waiting. I'm stuck on the EU version.

Redmi 9A Bootloop Bootloader and Recovery mode inaccessible

Hi All,
I had my Redmi 9A flashed and was using the original stock rom unlocked and rooted. Since I ran into some issue with applications failing to start I decided to reflash with the OTA update zip. Now that I did that the phone keeps rebooting anc connecting it to a PC with all the drivers available including MTK, QUALCOM the system won't detect the phone and the phone will never boot into bootloader, or recovery or EDL mode.
I have tried various ADB and Fastboot commands but they would work only when the system detects thd phone and the phone does not reboot.
Has anyone come across such issues ?
MiUnlock tool failed
MiFlash tool failed
Sp flash tool failed
All other flash tools failed too

hola ya encontraste alguna solución estoy en el mismo caso

have you tried holding power button + vol down button till fastboot shows up?
Answer to the first post
when you have rooted your phone, it modifies the boot.img file, and the original MIUi ROM detects that, and bootloops
The fix its to flash vbmeta.img via fastboot, using the keys (power + vol down )

yes and neither fastboot with volume down nor recovery with volume up appears ... please have any suggestions or it will be that this device has no remedy

Hi,
I think I have the same issue: I tried to root and corrupted/incompatible vbmeta security, and device will continuously self-reset, will not enter fastboot, and no recovery.
I must remove battery to stop it from draining due to bootloop.
From what I searched, my guess, there is only one hope: to use the hardware test-pins to force EDL mode.
I found some info on EDL pins for many other devices (9c 9T... ) but not for 9A.
So please, if anyone knows, has the PCB layout, please post a picture and explain how to force enter EDL mode.
After that, I guess SP flasher can be used.

kukudro said:
Hi,
I think I have the same issue: I tried to root and corrupted/incompatible vbmeta security, and device will continuously self-reset, will not enter fastboot, and no recovery.
I must remove battery to stop it from draining due to bootloop.
From what I searched, my guess, there is only one hope: to use the hardware test-pins to force EDL mode.
I found some info on EDL pins for many other devices (9c 9T... ) but not for 9A.
So please, if anyone knows, has the PCB layout, please post a picture and explain how to force enter EDL mode.
After that, I guess SP flasher can be used.
Click to expand...
Click to collapse
I was able to revive it by downloading the correct image with sp flash tools, it turns out that my device after investigating a little was from a Russian region, and with that image it was like new, what a scare

MaykoDiaz7 said:
I was able to revive it by downloading the correct image with sp flash tools, it turns out that my device after investigating a little was from a Russian region, and with that image it was like new, what a scare
Click to expand...
Click to collapse
and you used EDL test-pins to force EDL mode? or you entered from fastboot reboot EDL ?
for me is auto resetting continuu, so can't enter fastboot..

Boot stuck at U+5G (vendor logo). (Fastboot o, EDL o, ADB x, Unlocked)

Hi guys,
I recently got a v50 and tried to flash custom ROM.
I followed this guide to unlock.
It worked well, I could unlock the device successfully. But when I flashed the custom ROM/Magisk thorugh TWRP, I flashed into a wrong slot, which led it to boot into only bootloader.
Since I could not get into the download mode, I tried to extract img files from kdz (V500N21a_00_LGU_KR_OP_0903) and flash them through QFIL. I followed this guide (v50backup files from this post did not work for me, so I decided to extract img files from kdz and use them).
This worked well, it gave me download mode back.
With that download mode, I tried to flash it with LGUP. And I could flash it successfully. But when the device boots, it does not boot completely. It stuck at the U+5G logo.
I have tried to use two versions of LGUP (1.16 from here and 1.17 cmd tool from this korean dude). And these tools allow me to flash kdz (V500N21a_00_LGU_KR_OP_0903) successfully but I could not make phone to boot with any of them...
I have checked
Code:
fastboot getvar all
and it shows that slot is not bootable... (fastboot getall var result)
What can I do now? I can not find what is the problem to fix... Any suggestions please? Thank you very much in advance!

Question [SOLVED] Soft Bricked device stuck in boot loop, only fastboot working. No TWRP. MiFlash does not work. How can I fix this mess?

Solution: I hardbricked my device because of my dumbness. This device is not veux... It s viva. Be cautious my friends...
I unlocked my bootloader and wanted to install TWRP to flash a custom ROM to the device. Unfortunately, right after I tried, device got stuck in a bootloop (Mi logo showing, then closing.)
I tried flashing multiple TWRP files after that. Since there is no official file for this device, I tried the ones given in the forum and a youtube video.
Holding power+up does not open anything. Holding power+down I can go to fastboot. ADB does not see the device (adb devices does not show anything). But fastboot devices does show. (MiFlash tool also sees the device but can't flash the ROM.)
MiFlash first gives the classic crc error, I delete the lines, it passes this error and finally gives another error ("Command failed"). I tried flashing 2 versions (my local version and eu version) of the stock rom in both windows and ubuntu based linux. What am I doing wrong?
Am I doomed? What can be done? Why isn't ADB working? Thank you for replies

turbotales said:
I unlocked my bootloader and wanted to install TWRP to flash a custom ROM to the device. Unfortunately, right after I tried, device got stuck in a bootloop (Mi logo showing, then closing.)
I tried flashing multiple TWRP files after that. Since there is no official file for this device, I tried the ones given in the forum and a youtube video.
Holding power+up does not open anything. Holding power+down I can go to fastboot. ADB does not see the device (adb devices does not show anything). But fastboot devices does show. (MiFlash tool also sees the device but can't flash the ROM.)
MiFlash first gives the classic crc error, I delete the lines, it passes this error and finally gives another error ("Command failed"). I tried flashing 2 versions (my local version and eu version) of the stock rom in both windows and ubuntu based linux. What am I doing wrong?
Am I doomed? What can be done? Why isn't ADB working? Thank you for replies
Click to expand...
Click to collapse
ABD works only if you have enabled USB debugging.
Eventually check here that everything is correct:
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
Or try to install a Xiaomi Eu rom (Fastboot).
Extract the zip then run the scrip in the corresponding extracted folder to your O.S.
Fastboot_first install.
xiaomi.eu_multi_VEUX_V13.0.3.0.SKCCNXM_v13-12-fastboot.zip
https://sourceforge.net/projects/xi...files/xiaomi.eu/MIUI-STABLE-RELEASES/MIUIv13/

NOSS8 said:
ABD works only if you have enabled USB debugging.
Eventually check here that everything is correct:
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
Or try to install a Xiaomi Eu rom (Fastboot).
Extract the zip then run the scrip in the corresponding extracted folder to your O.S.
Fastboot_first install.
xiaomi.eu_multi_VEUX_V13.0.3.0.SKCCNXM_v13-12-fastboot.zip
https://sourceforge.net/projects/xi...files/xiaomi.eu/MIUI-STABLE-RELEASES/MIUIv13/
Click to expand...
Click to collapse
Hello, I do have my bootloader unlocked and USB debugger is also on.
I tried flashing twrp again, says it worked but does not boot into it. Goes back to boot loop
Then I tried flashing with MiFlash again. Same error
fastboot error remote: command failed
When I google it everyone says my bootloader should be locked. But it is not.
Can I use the hard brick solution with bypass for this problem?

turbotales said:
Hello, I do have my bootloader unlocked and USB debugger is also on.
I tried flashing twrp again, says it worked but does not boot into it. Goes back to boot loop
Then I tried flashing with MiFlash again. Same error
fastboot error remote: command failed
When I google it everyone says my bootloader should be locked. But it is not.
Can I use the hard brick solution with bypass for this problem?
Click to expand...
Click to collapse
All these procedures, Miflash, Twrp, Xiaomi Eu rom are done in Fastboot mode not ADB and obviously the bootloader must be unlocked.
Try the Xiaomi Eu rom.(TWRP included).

NOSS8 said:
All these procedures, Miflash, Twrp, Xiaomi Eu rom are done in Fastboot mode not ADB and obviously the bootloader must be unlocked.
Try the Xiaomi Eu rom.(TWRP included).
Click to expand...
Click to collapse
Tried doing this.. now it s hard bricked.

turbotales said:
Tried doing this.. now it s hard bricked.
Click to expand...
Click to collapse
You have flashed a Xiaomi Eu rom and it does not work?
And with Miflash?

NOSS8 said:
You have flashed a Xiaomi Eu rom and it does not work?
And with Miflash?
Click to expand...
Click to collapse
I tried flashing with Miflash didnt work,
Tried flashing with linux and said it is done, but now device does not open in any way. What should I do?

These are the screenshots of the Xiaomi Eu rom?
What is the version of your phone? (11 pro/Poco).
What rom were you on?
post the Miflash log.

NOSS8 said:
These are the screenshots of the Xiaomi Eu rom?
What is the version of your phone? (11 pro/Poco).
What rom were you on?
post the Miflash log.
Click to expand...
Click to collapse
Downloaded the rom from the link you sent me earlier. My device is veux and had MIUI13 before getting bricked.
Again the device got bricked from the last think i did. Do you know what wen wrong?

turbotales said:
Downloaded the rom from the link you sent me earlier. My device is veux and had MIUI13 before getting bricked.
Again the device got bricked from the last think i did. Do you know what wen wrong?
Click to expand...
Click to collapse
If you tried with Miflash post the log otherwise try and post the log.

Solved, I'm dumber than I thought. This phone is not veux. It's viva. If I were to re-check it I d not be in this position... Let this be a lesson to me. Going to have to take it to the service now.