Database Develop

Help! My Motorola RAZR I XT890 cannot be "unbricked" and I tried several methods...

Help! My Motorola RAZR I XT890 cannot be "unbricked" and I tried several methods...
Hello!
I unlocked the bootloader successfully, then I tried to root my phone using The Razr guy method and I used the "RAZRi_Root_Windows" file, while rooting my phone went to the "warning bootloader unlocked" screen and it just loops forever from that screen, the bat file, showed that it successfully rooted my phone. I tried to fix it using rsd lite, but it never detects my phone, so I searched for a way to make my pc able to detect it, so I found I could use Intel xFSTK, installed it but still nothing it doesn't appear as shown in the tutorial, I even downloaded the dll file that it needed to run, but after running the xFSTK DLDR or something like that, the application is completely empty, and I saw it should show some tools to download something. Also tried using Linux Zorin, but it only says that my XT890 cannot be accessed and shows an usb error code.
I am able to enter the fastboot screen, the one you get by pressing POWER and VOLUME DOWN, also it charges my batter completely normal. Also my pc is able to show that the XT890 is connected, but only before installing the drivers and it shows the CD installer for the Motorola Device Manager and some other files (all this while looping), and if I enter the fastboot flash mode, it appears as "fastboot smi S", with a yellow triangle and an exclamation sign while in Windows device manager. It has Jelly Bean update from telcel (mexico), and I already have the xml.zip file to reinstall it.
I use windows 8.1 , and as mentioned Linux Zorin on my PC.
Could some help me with it...if you now how to fix it please list every single step on how to do it T_T, THANKS IN ADVANCE!!!!

It looks like the root method changed something bad in your system partition and that's why it won't boot up. First thing to do is installing the correct Motorola drivers. When in fastboot the device should be normally listed and could be acceded by fastboot. If fastboot is working well, use rsd lite to recover it or flash the system partition manually.
If everything is working well, consider installing a custom recovery and flashing a SuperSU zip for root access.

Hazou said:
It looks like the root method changed something bad in your system partition and that's why it won't boot up. First thing to do is installing the correct Motorola drivers. When in fastboot the device should be normally listed and could be acceded by fastboot. If fastboot is working well, use rsd lite to recover it or flash the system partition manually.
If everything is working well, consider installing a custom recovery and flashing a SuperSU zip for root access.
Click to expand...
Click to collapse
Thanks for answering!!
I've checked on some websites that if the phone is not detected by RSD Lite it maybe due to a bug in the phone's driver that happens only on windows 8/8.1, so I will try to do the same thing on windows 7 and see what happens...
Hope it works...T_T

weird_user said:
Thanks for answering!!
I've checked on some websites that if the phone is not detected by RSD Lite it maybe due to a bug in the phone's driver that happens only on windows 8/8.1, so I will try to do the same thing on windows 7 and see what happens...
Hope it works...T_T
Click to expand...
Click to collapse
That could be it.
I just noticed u have unlocked your bootloader. That means u have used fastboot earlier to get the unlock code into the device. So the drivers should work perfectly if u are in the good device modes. Try to flash the system_signed image manually though fastboot and see what happens ("fastboot flash system <path-to-system_signed-image>", u may need mFastboot for that(is inside the rsd-lite package))
Just for the record if u didn't know:
Adb: works only in selected recovery's and normal boot(sometimes in charging mode as well)
Fastboot: works only in AP fastboot mode (power+vol-down, black screen with white/blue text (rsd-lite needs this mode))
XFSTK: works only in medfield flash modues, something u don't need to be with that kind of error

Thanks again!!!
Hazou said:
That could be it.
I just noticed u have unlocked your bootloader. That means u have used fastboot earlier to get the unlock code into the device. So the drivers should work perfectly if u are in the good device modes. Try to flash the system_signed image manually though fastboot and see what happens ("fastboot flash system <path-to-system_signed-image>", u may need mFastboot for that(is inside the rsd-lite package))
Just for the record if u didn't know:
Adb: works only in selected recovery's and normal boot(sometimes in charging mode as well)
Fastboot: works only in AP fastboot mode (power+vol-down, black screen with white/blue text (rsd-lite needs this mode))
XFSTK: works only in medfield flash modues, something u don't need to be with that kind of error
Click to expand...
Click to collapse
Hazou said:
That could be it.
I just noticed u have unlocked your bootloader. That means u have used fastboot earlier to get the unlock code into the device. So the drivers should work perfectly if u are in the good device modes. Try to flash the system_signed image manually though fastboot and see what happens ("fastboot flash system <path-to-system_signed-image>", u may need mFastboot for that(is inside the rsd-lite package))
Just for the record if u didn't know:
Adb: works only in selected recovery's and normal boot(sometimes in charging mode as well)
Fastboot: works only in AP fastboot mode (power+vol-down, black screen with white/blue text (rsd-lite needs this mode))
XFSTK: works only in medfield flash modues, something u don't need to be with that kind of error
Click to expand...
Click to collapse
I am able to enter RECOVERY MODE NOW (I installed CWM, before this I was only able to see the android lying on the floor ans saty dead right there, I was supposed to press Volume + and - and the camera button at the same time, but nothing happened), it seems to be easier to unbrick it this way, but now the problem is that after I follow the steps to reinstall the original ROM, it aborts installation. I read this may be caused due to a file on the zip file, I looked for it, but nor the Folder META-INF, whic is supposed to contain a "update-script" file, nor that file is anywhere in the ROM folder...
I've even tried cyanogenmod (after first trying Telcel original ROM and then the retail GB ROM) cuz it actually contains the folder previously mentioned and the file is in a different path, but it is there, I modified it, but got a "Can't open tmd/update.zip (bad) Installation aborted" error...I don't know what else to do T_T...
Note: I also used sideload and CWM to install it, but the same thing happens. Also checked some other post about this issue, but none has helped me...

What zip file are u installing?
If u want to go back to stock, just use a RSD lite package for 4.1.2 or install TWRP and restore a TWRP backup to go to 4.4.2. There is no official RSD lite package for 4.4.2 and the update.zip doesn't work if your system doesn't boot already.

Hazou said:
What zip file are u installing?
If u want to go back to stock, just use a RSD lite package for 4.1.2 or install TWRP and restore a TWRP backup to go to 4.4.2. There is no official RSD lite package for 4.4.2 and the update.zip doesn't work if your system doesn't boot already.
Click to expand...
Click to collapse
It's done! Thanks!
I actually used another computer with windows 10, also I used RSD Lite and it worked just fine, now I have the stock ROM from Telcel and it it is working almost normal. The only abnormality I've seen is that my phone turns itself off when battery is at 20%, I searched info about that problem and it says I may re calibrate the battery, so it may work fine again, but now I need to root again to be able to do that T_T, hope it works this time...
THANKS! again!

SOFT BRICK using tool Xiaomi Mi A2

Hi guys, i need some help pleeease!
I was with the November security patch on my cell phone, I unlock the bootloader and went to use the friend tool (https://forum.xda-developers.com/mi-a2/how-to/mi-a2-toolkit-unlock-bootloader-root-t3834585) to activate the camera2api.
But it gave problem and the cell phone did not turn on, it was locked in the screen of android one.
So I downloaded the patched_boot.img from the version I was in and put it via fastboot. did not work.
Now, my phone is in this situation: I tried to use MiFlash (three versison: 2018528, 2017720 and 20151028) and they fail in the middle of the process, accusing "FAILED (command write failed (Unknown error))".
And: when I try to connect the cell phone normally, it shows the unlocked bootloader warning and goes straight to the fastboot, even without my request. This is strange. Perhaps because the system is damaged by the miflash unfinished
Obs: bootloader are unlocked and i can access twrp
If anyone can help me I will be very grateful and happy

What exactly did the "tool" do? I mean if you don't know that, pretty difficult to diagnose what's wrong...

AsItLies said:
What exactly did the "tool" do? I mean if you don't know that, pretty difficult to diagnose what's wrong...
Click to expand...
Click to collapse
Hi.
The tool (her topic link is up there) promised to activate camera2api without root my device (allowing OTAs in the future).
I believe she did a "temporary root" with a "temporary" boot.img just to activate the camera2api, and when it rebooted, it would return to normal boot.img without root. I do not know if I could explain it well.
The current issue is that it seems that the system is currently "destroyed or corrupted". Can not I reinstall the entire system through TWRP? Or something like this

Like I said, you don't know what it actually did. What it promised is one thing, what it did... another
That's the problem with 'tools'.
Have you tried doing a factory reset? Hold Vol up and power until it gets to Recovery (hopefully), if you do a quick press of vol up, that gets past the 'no command'. Then use vol up and down for selection and press power when on 'factory reset'.
It might work

AsItLies said:
Like I said, you don't know what it actually did. What it promised is one thing, what it did... another
That's the problem with 'tools'.
Have you tried doing a factory reset? Hold Vol up and power until it gets to Recovery (hopefully), if you do a quick press of vol up, that gets past the 'no command'. Then use vol up and down for selection and press power when on 'factory reset'.
It might work
Click to expand...
Click to collapse
You are right, friend.. this is the problems with tools! I never use tools with my A1 and past phones.. just this time :crying:
I tried the factory reset now. And it did not work, unfortunately. On the first attempt (I was in fastboot mode) he showed a white circle with the writing "ERASING" and then went back to the screen of Android One, and then I tried again Vol Up + Power and he appeared "No command" , and after I rebooted and tried again, nothing appears, it just restarts to the static screen of "Android One"
Another ideas?

erickxd said:
You are right, friend.. this is the problems with tools! I never use tools with my A1 and past phones.. just this time :crying:
I tried the factory reset now. And it did not work, unfortunately. On the first attempt (I was in fastboot mode) he showed a white circle with the writing "ERASING" and then went back to the screen of Android One, and then I tried again Vol Up + Power and he appeared "No command" , and after I rebooted and tried again, nothing appears, it just restarts to the static screen of "Android One"
Another ideas?
Click to expand...
Click to collapse
The only other thing I can think of would be to change the current slot. If that works you would be booted into the prior version of the OS vs the latest update you did.
In fastboot, do fastboot getvar current-slot
Depending on what that slot is, change it to the other one (can only be a or b)
thus fastboot set_active a (or b, whichever is not the current one)
then fastboot reboot - and hope it boots.

AsItLies said:
The only other thing I can think of would be to change the current slot. If that works you would be booted into the prior version of the OS vs the latest update you did.
In fastboot, do fastboot getvar current-slot
Depending on what that slot is, change it to the other one (can only be a or b)
thus fastboot set_active a (or b, whichever is not the current one)
then fastboot reboot - and hope it boots.
Click to expand...
Click to collapse
Well... fastboot don't recognize this command, he show the list of avaible commands
And i don't know why, but for now i can't boot in twrp.img
i'm going crazy :crying::crying::crying:

erickxd said:
Well... fastboot don't recognize this command, he show the list of avaible commands
And i don't know why, but for now i can't boot in twrp.img
i'm going crazy :crying::crying::crying:
Click to expand...
Click to collapse
That's probably because you have an old version of fastboot installed. Upgrade to the newest version, which should recognize dual slots.
dual slots are quite new.

AsItLies said:
That's probably because you have an old version of fastboot installed. Upgrade to the newest version, which should recognize dual slots.
dual slots are quite new.
Click to expand...
Click to collapse
Fastboot updated now! I changed the slot from B to A.
But doesn't work, unfortunately. After reboot, the phone can't boot and appears the screen asking between Try Boot Again or Factory Reset. I tried Factory Reset, but don't work =( return to the same screen.
What seems very strange to me, is the Miflash doesn't work. With my Mi A1 miflash ever save me

erickxd said:
Fastboot updated now! I changed the slot from B to A.
But doesn't work, unfortunately. After reboot, the phone can't boot and appears the screen asking between Try Boot Again or Factory Reset. I tried Factory Reset, but don't work =( return to the same screen.
What seems very strange to me, is the Miflash doesn't work. With my Mi A1 miflash ever save me
Click to expand...
Click to collapse
I've never used miflash, so no help there.
I'd try flashing the correct boot.img (for your software version). You can find the various boot images in the following link (don't forget to thank user ckpv5 for uploading these).
https://sourceforge.net/projects/others/files/Xiaomi_MiA2/
you would do fastboot flash boot_b boot.img
I'd suggest using b slot, as that was originally active. After flashing, set it back to active, try to reboot... then cross your fingers

AsItLies said:
I've never used miflash, so no help there.
I'd try flashing the correct boot.img (for your software version). You can find the various boot images in the following link (don't forget to thank user ckpv5 for uploading these).
https://sourceforge.net/projects/others/files/Xiaomi_MiA2/
you would do fastboot flash boot_b boot.img
I'd suggest using b slot, as that was originally active. After flashing, set it back to active, try to reboot... then cross your fingers
Click to expand...
Click to collapse
Doesn't work man.. I went to twrp and checking there in the "WIPES session", I saw that the SYSTEM partition is 0kb used and 0kb free. Appears to be entirely empty
Do not have a way to install the whole system via twrp?

erickxd said:
Doesn't work man.. I went to twrp and checking there in the "WIPES session", I saw that the SYSTEM partition is 0kb used and 0kb free. Appears to be entirely empty
Do not have a way to install the whole system via twrp?
Click to expand...
Click to collapse
No, I don't. But I can tell you, twrp is a recovery app. It shouldn't be in the boot slot. And, with dual slot configurations, there is no recovery partition. The other slot is now used to do a recovery.
In other words, the way we *used* to use twrp doesn't work on dual slot phones. I think that's a big part of the confusion people are having. While the boot images do have a small recovery part to them, it's not a separate partition.
If you're flashing boot.img, and setting that slot active, I've no idea how you're getting into twrp.

Since now your fastboot is working why don't you use miflash to flash official stock ROM
1. You need unlocked bootloader which you already have.
2. Run these command to unlock critical partition
fastboot flashing unlock_critical
3 . Download the official fastboot V9.6.14.0 ROM from
https://forum.xda-developers.com/mi-a2/how-to/ota-v9-6-5-0-odimife-t3823445
Or here
http://en.miui.com/getrom.php?r=353&m=yes&app=false
4. Install with miflash (you already know the how-to)
5. Once up & running, do OTA to latest
Later .. redo what you want to do like enable camera api2 with proper guide.
E.g: https://forum.xda-developers.com/mi-a2/how-to/how-to-enable-cam2api-simply-ota-t3858861

ckpv5 said:
Since now your fastboot is working why don't you use miflash to flash official stock ROM
1. You need unlocked bootloader which you already have.
2. Run these command to unlock critical partition
fastboot flashing unlock_critical
3 . Download the official fastboot V9.6.14.0 ROM from
https://forum.xda-developers.com/mi-a2/how-to/ota-v9-6-5-0-odimife-t3823445
Or here
http://en.miui.com/getrom.php?r=353&m=yes&app=false
4. Install with miflash (you already know the how-to)
5. Once up & running, do OTA to latest
Later .. redo what you want to do like enable camera api2 with proper guide.
E.g: https://forum.xda-developers.com/mi-a2/how-to/how-to-enable-cam2api-simply-ota-t3858861
Click to expand...
Click to collapse
Hello.
I've tried using Miflash several times (3 different versions), but it never ends, it end up with an error every time that he will copy the file system.img to the mobile phone (I analyzed the log).
The miflash divides the file system.img into 5 or 6 smaller parts to be able to transfer to the mobile phone, and in some of these parts gives error, everytime :crying:

AsItLies said:
No, I don't. But I can tell you, twrp is a recovery app. It shouldn't be in the boot slot. And, with dual slot configurations, there is no recovery partition. The other slot is now used to do a recovery.
In other words, the way we *used* to use twrp doesn't work on dual slot phones. I think that's a big part of the confusion people are having. While the boot images do have a small recovery part to them, it's not a separate partition.
If you're flashing boot.img, and setting that slot active, I've no idea how you're getting into twrp.
Click to expand...
Click to collapse
I can access twrp when I flash ''fastboot boot twrp.img" in powershell, so until the next reboot I have access to twrp

erickxd said:
Hello.
I've tried using Miflash several times (3 different versions), but it never ends, it end up with an error every time that he will copy the file system.img to the mobile phone (I analyzed the log).
The miflash divides the file system.img into 5 or 6 smaller parts to be able to transfer to the mobile phone, and in some of these parts gives error, everytime :crying:
Click to expand...
Click to collapse
When I read your post here - https://forum.xda-developers.com/showpost.php?p=78085858&postcount=188
"flashing is not allowed for critical partitions" usually due to critical partitions not unlocked. So .. if you already run "fastboot flashing unlock_critical" and you still have error using miflash .. nothing much I can offer to help. Hopefully you'll be able to fix it.

ckpv5 said:
When I read your post here - https://forum.xda-developers.com/showpost.php?p=78085858&postcount=188
"flashing is not allowed for critical partitions" usually due to critical partitions not unlocked. So .. if you already run "fastboot flashing unlock_critical" and you still have error using miflash .. nothing much I can offer to help. Hopefully you'll be able to fix it.
Click to expand...
Click to collapse
Hmm thanks for the answer!
Even when the operation fails after transfer a couple of archives before the system.img??? (on the Miflash)
If my phone was locked, Miflash could transfer these couple of archives before the operation fails?? Or if bootloader is locked, zero files can be passed by Miflash, and the error is apresented at the beginning of the operation?

Have you successfully unlocked critical partitions?
If yes, try to run flash_all.bat from the official stock image you downloaded. No need to use MiFlash.

prokaryotic cell said:
Have you successfully unlocked critical partitions?
If yes, try to run flash_all.bat from the official stock image you downloaded. No need to use MiFlash.
Click to expand...
Click to collapse
well... When I just run flash_all.bat from the stock image folder, the .bat file will recognize that I am running it for the connected mobile?
how exactly should I run flash_all.bat? just double clicking it in stock image folder? or should I copy the .bat to /adb folder and open power shell prompt in adb folder and execute the .bat from there? sorry for my ignorance
Can you show me, please?

erickxd said:
well... When I just run flash_all.bat from the stock image folder, the .bat file will recognize that I am running it for the connected mobile?
how exactly should I run flash_all.bat? just double clicking it in stock image folder? or should I copy the .bat to /adb folder and open power shell prompt in adb folder and execute the .bat from there? sorry for my ignorance
Can you show me, please?
Click to expand...
Click to collapse
Before someone can explain that, why don't you answer the question asked .. in fact at least 3 people was asking/telling ...
"Have you successfully unlocked critical partitions?"
Without the proper answer from you, not easy to help.

PLEASE HELP - Device Bricked - edl waiting for device

Hello I have a Mi A2 with ONE.
I tried to install Mi6X following this guide:
Guide
I got to step 9:
9- Click Refresh on Mi Flash Then choose Clean all and click flash
Then I got this error:
Error oem edl miflash tool, ACK count don't match
Then I tryed instead to install Jasmine again, and I started getting this error:
Cannot receive hello packet,MiFlash is trying to reset status
And then I was stupid enough to unplug my phone
THE ACTUAL PROBLEM (rigth now)
1. My phone will start, then stay at Mi(mi.com) logo indefinitely.
2. I can't enter download mode, Vol + and power will bring me the Mi logo again and again.
3. Can enter Fastboot mode... BUT...
-Mi flash don't detect it
-miflash_unlock don't detect it
-edl.cmd, unlock auto, and unlock critical say "< waiting for device >"
Edit: I solved the problem using test point to enter EDL mode, then It connected and I could flash it.

our phones (mia2) are weird devices to be honest, mine was recently bricked after choosing the "reboot to bootloader" option in twrp. id recommend you to go to mi service center if your phone is still in warranty

Stoopid Dickhead said:
our phones (mia2) are weird devices to be honest, mine was recently bricked after choosing the "reboot to bootloader" option in twrp. id recommend you to go to mi service center if your phone is still in warranty
Click to expand...
Click to collapse
Thanks for the reply. But unfortunately I can't
That would be my first solution, but my Mi A2 is not in warranty anymore...

have you tried to install stock rom with fastboot?

Maharram said:
have you tried to install stock rom with fastboot?
Click to expand...
Click to collapse
Miflash won't detect the phone, it's like is not connected at all...

puerco-potter said:
Miflash won't detect the phone, it's like is not connected at all...
Click to expand...
Click to collapse
No im not talking about miflash im saying fastboot u can install stock rom with fastboot too you need payload bin dumper and ota flasher for that

Maharram said:
No im not talking about miflash im saying fastboot u can install stock rom with fastboot too you need payload bin dumper and ota flasher for that
Click to expand...
Click to collapse
Sorry, can you help me unsderstand a little.
I found this guide:
Guide
But none of my Roms (Jasmine or Wayne) have a file that's named payload.bin
I feel like I am missing something
Edit:
I found that ota updates are the ones with the payload.bin file followed the guide and everything, but fastboot bring almost the same error that EDL brings:
< Waiting for any device >
Can it be that my cable somehow magically from one conection to another stoped working or something? I asked a friend for his cable... Cs are not as common in this country yet.

puerco-potter said:
Sorry, can you help me unsderstand a little.
I found this guide:
Guide
But none of my Roms (Jasmine or Wayne) have a file that's named payload.bin
I feel like I am missing something
Edit:
I found that ota updates are the ones with the payload.bin file followed the guide and everything, but fastboot bring almost the same error that EDL brings:
< Waiting for any device >
Can it be that my cable somehow magically from one conection to another stoped working or something? I asked a friend for his cable... Cs are not as common in this country yet.
Click to expand...
Click to collapse
Have you enabled oem unlock ?

puerco-potter said:
Hello I have a Mi A2 with ONE.
I tried to install Mi6X following this guide:
Guide
I got to step 9:
9- Click Refresh on Mi Flash Then choose Clean all and click flash
Then I got this error:
Error oem edl miflash tool, ACK count don't match
Then I tryed instead to install Jasmine again, and I started getting this error:
Cannot receive hello packet,MiFlash is trying to reset status
And then I was stupid enough to unplug my phone
THE ACTUAL PROBLEM (rigth now)
1. My phone will start, then stay at Mi(mi.com) logo indefinitely.
2. I can't enter download mode, Vol + and power will bring me the Mi logo again and again.
3. Can enter Fastboot mode... BUT...
-Mi flash don't detect it
-miflash_unlock don't detect it
-edl.cmd, unlock auto, and unlock critical say "< waiting for device >"
Please help, I am really afraid my phone will die permanetly as I can't turn it off and I don't know if it will charge in it's current state.
Click to expand...
Click to collapse
Did you flash hex kernel? You know that phone on 6x miui rom will not boot if you havent flash custom kernel after miui?

Mi flash tool won't work with locked bootloader
Install adb drivers and write command
' abd oem edl '
If ur phones connects
Than u can use mi flash tool

Maharram said:
Have you enabled oem unlock ?
Click to expand...
Click to collapse
I followed this guide to unlock bootloader previous to the guide on flashing of the first post:
GUIDE
The .bat that you run there actually executes "fastboot oem unlock". I did that part without any problem, the phone screen asked for confirmation and everything fine. After succefully unlocking bootloader I followed the guide on flashing Miui 10.
Now even that "fastboot oem unlock" will show this message:
< waiting for any device >

Amnvlad said:
Mi flash tool won't work with locked bootloader
Install adb drivers and write command
' abd oem edl '
If ur phones connects
Than u can use mi flash tool
Click to expand...
Click to collapse
"adb oem edl" brings this error:
adb.exe: unknown command oem
"fastboot oem edl" brings this error:
< waiting for any device >
and
"adb reboot bootloader" brings this error:
error: no devices/emulators found
(tested everything with the phone in fastboot or the Mi logo)

mariosenta said:
Did you flash hex kernel? You know that phone on 6x miui rom will not boot if you havent flash custom kernel after miui?
Click to expand...
Click to collapse
I didn't, because I got an error when flashing Miui, never got to follow the rest of the guide because my phone won't be recognised by any program it seems...
Thanks you all for the help, I will try with another cable, and if that don't work I will test point this little one. I really don't want to open it... but It seems like fastboot won't connect no matter what...

puerco-potter said:
I followed this guide to unlock bootloader previous to the guide on flashing of the first post:
GUIDE
The .bat that you run there actually executes "fastboot oem unlock". I did that part without any problem, the phone screen asked for confirmation and everything fine. After succefully unlocking bootloader I followed the guide on flashing Miui 10.
Now even that "fastboot oem unlock" will show this message:
< waiting for any device >
Click to expand...
Click to collapse
Did you execute this line "fastboot flashing unlock_critical" after fastboot oem unlock?

mariosenta said:
Did you execute this line "fastboot flashing unlock_critical" after fastboot oem unlock?
Click to expand...
Click to collapse
Originally yes, after oem unlock, I ran flashing unlock_critical

puerco-potter said:
I followed this guide to unlock bootloader previous to the guide on flashing of the first post:
GUIDE
The .bat that you run there actually executes "fastboot oem unlock". I did that part without any problem, the phone screen asked for confirmation and everything fine. After succefully unlocking bootloader I followed the guide on flashing Miui 10.
Now even that "fastboot oem unlock" will show this message:
< waiting for any device >
Click to expand...
Click to collapse
You installed oreo on pie? Because Mi A2 has antiroll back projection if you downgrade your Android version then you lost your imei code

Maharram said:
You installed oreo on pie? Because Mi A2 has antiroll back projection if you downgrade your Android version then you lost your imei code
Click to expand...
Click to collapse
6x has antiroll back, a2 does not.
---------- Post added at 11:13 AM ---------- Previous post was at 11:12 AM ----------
[/COLOR]
puerco-potter said:
I didn't, because I got an error when flashing Miui, never got to follow the rest of the guide because my phone won't be recognised by any program it seems...
Thanks you all for the help, I will try with another cable, and if that don't work I will test point this little one. I really don't want to open it... but It seems like fastboot won't connect no matter what...
Click to expand...
Click to collapse
Please, keep us updated.

I had the same issues like you months ago. The only solution you buy a pentalobe 0.8mm for iphone, a small philips screw driver, and a tweezer. Flash your phone in EDL mode. You need to contact 2 pins. You can search the location of the pins, how to disassemble the phone by googling it. then just flash Mi A2 stock ROM first, then convert it to Mi 6X again. I

hasel17 said:
I had the same issues like you months ago. The only solution you buy a pentalobe 0.8mm for iphone, a small philips screw driver, and a tweezer. Flash your phone in EDL mode. You need to contact 2 pins. You can search the location of the pins, how to disassemble the phone by googling it. then just flash Mi A2 stock ROM first, then convert it to Mi 6X again. I
Click to expand...
Click to collapse
No need to convert, now we have miui for a2.

mariosenta said:
No need to convert, now we have miui for a2.
Click to expand...
Click to collapse
Where can I take a look at this? I am really interested.
The cable wasn't the issue, I am getting the tools to open it tonight.

Totaly bricked phone

Hello all, I have a big problem - I tried to use last TWRP from L00 Kostyan LOS13 version. I bricked my phone :-(. I had Kostyan last LOS13. by mistake I installed recovery.img to oem info partition. When I start the mobile LEDs first blink is red then green. There is no logo. I can only go to FASTBOOT&RESCUE MODE. It say phone locked. I can connect to phone via fastboot, adb says there is no device. I found out via fastboot that bootloader is locked. I am not able to load anything - its say command not allowed probably due to locked bootloader. Coudl you help me please? I also tried to save an official Huawei ROM to SD card to dload folder, but nothing happens during starting phone (I tried all combinations - power button + only vol-, only vol+, both volume). I can go only to FASTBOOT&RESCUE MODE :-(

You may have messed up your oem partition, which is very important in order to boot your device properly.
Although your bootloader is locked, I think you should be able to flash EMUI properly.
Extract your update.app using the Huawei Update Extractor Tool (google it, you will be able to find it in a xda forum, in the first results).
Try to flash that oem partition, it should be inside your update.app.
If it doesn't work, you may be able to unlock your P7 without any code.
Try typing fastboot oem unlock .
If it doesn't work, then try booting that TWRP image
fastboot boot <nameofyourtwrp>.img
There you will be able to reflash your OEM partition properly.
Obviously, for all the previous steps, you need ADB & Fastboot drivers:
MEGA
MEGA provides free cloud storage with convenient and powerful always-on privacy. Claim your free 20GB now
mega.nz

masemoel said:
You may have messed up your oem partition, which is very important in order to boot your device properly.
Although your bootloader is locked, I think you should be able to flash EMUI properly.
Extract your update.app using the Huawei Update Extractor Tool (google it, you will be able to find it in a xda forum, in the first results).
Try to flash that oem partition, it should be inside your update.app.
If it doesn't work, you may be able to unlock your P7 without any code.
Try typing fastboot oem unlock .
If it doesn't work, then try booting that TWRP image
fastboot boot <nameofyourtwrp>.img
There you will be able to reflash your OEM partition properly.
Obviously, for all the previous steps, you need ADB & Fastboot drivers:
MEGA
MEGA provides free cloud storage with convenient and powerful always-on privacy. Claim your free 20GB now
mega.nz
Click to expand...
Click to collapse
Thank you very much for you quick response. I extracted the official P7-L10V100R001C00B609Esp ROM (I can try another but I do not think it matters). I do not see there anything similar to oem partition. I tried to flash recovery and boot section. But I always got "FAILED (remote: Command not allowed)". I tried also the TWRP with the same result.
I tried fastboot oem unlock but I got "FAILED (remote: data parse fail)" it probably requires a code.
I think I have to unlock bootloader but how to do it if my phone does not work?

How To Guide Master Guide to Unlock Bootloader/Flash TWRP/Root Device/Flash EU ROM/Pass SafetyNet

Hi All, as this device is fairly new and there is not much clarity on things so, I decided to create a master guide as you see below. I am also attaching a PDF version of this guide as I have not formatted this XDA post to what I feel it should be like. You may download and follow that, I will keep updating things as I find.
Lets start​
1. Unlock Bootloader​1.1 Apply for Bootloader Unlock​
Enable developer settings
Go to Settings>About phone/My device> All specs> Hit MIUI Version 8 times
Access Developer Settings from Settings>Additional Settings
Enable OEM Unlocking option
Now login to your desired Mi Account that you wish it to be associated with your device (Mi account should have a mobile number registered for OTP and verification sometime asked by MI flash unlock tool)
Your unlock bootloader wait time starts now. Wait for 7 days (168 hours from the time you added MI account) to unlock bootloader
1.2 Unlocking Bootloader​So you have crossed the wait period…. Now follow below to unlock assuming you have all the USB drivers for Mi devices (usually auto installed when you connect mobile)
Warning: All your userdata (including pictures and files) will be wiped out
Download official Mi flash unlock tool from this link: https://miuirom.xiaomi.com/rom/u1106245679/5.5.224.24/miflash_unlock-en-5.5.224.24.zip
Boot into Booloader: Power off your mobile then hold Volume Down + Power Button till fastboot bunny pops up
Open Mi Flash unlock tool downloaded in step 1
Sign in with same account that you used to sign in in Developer Settings in step 1.1.d. It may ask to verify your account with OTP. do it.
Click Unlock on the tool.
Your device will be unlocked and rebooted. Wait till reboot.
Congrats… you have an unlocked mobile device now
Now let’s go to Rooting your device for which we will have to flash TWRP to Mobile
2 TWRP Flash and Rooting​2.1 TWRP Flash​
Download and Install Minimal ADB and Fastboot for windows for this link: https://androiddatahost.com/wp-content/uploads/Minimal_ADB_Fastboot_v1.4.3.zip
Download unofficial TWRP (only one available as of writing this guide) from here: https://sourceforge.net/projects/xi....6.0_11-0_LOCAL-20220203-01-vili.img/download and rename it to twrp.img
Also download Magisk from below link: https://github.com/topjohnwu/Magisk/releases/download/v24.0/Magisk-v24.0.apk we will use it next section for rooting.
Rename the downloaded magisk file from magisk.apk to magisk.zip and copy it to your device’s storage
Copy the above twrp.img file to Minimal ADB and Fastboot folder (not necessary if you know some directory navigation using command prompt)
Boot mobile into bootloader (follow 1.2.b)
From your Minimal ADB and Fastboot folder open Cmd here.exe file to access the ADB tool
Connect your device to PC
Verify if device has connected successfully using the command below
Fastboot devices
This should return your device id
Now boot into TWRP using below commands
Fastboot boot “twrp.img” if you pasted twrp.img in minimal adb and fastboot folder
Fastboot boot “path to twrp.img” if you did not move it to the minimal adb and fastboot folder
Let the device boot to TWRP
In above step we just booted by TWRP which is temporary. Now let’s flash it to make it permanent:
Go to Advanced settings in TWRP and click Flash Current TWRP
Reboot to TWRP
2.2 TWRP Backup of Current Rom​
You should have a working TWRP
Boot to TWRP and navigate to Backup section
Select all partitions and swipe to confirm
If you see error in backing up, uncheck Data and EFS partition backup
The backup should complete successfully
Have this backup copied to a PC for emergency wipout of your mobile
2.3 Rooting/Flashing Magisk​
Go to Install in TWRP and select magisk.zip you copied in step 2.1.d
This will flash magisk and root your device. Now reboot to system from recovery
Once you have the device booted, rename the magisk.zip to magisk.apk again and install the magisk app on device
You may update if you see any updates to magisk or app
2.4 Passing Safetynet​
Download this magisk module zip from here: https://drive.google.com/file/d/1QJHPpL4R8fcxjB35XbcpaCOipKzpvL2I/view?usp=sharing
Go to magisk app settings and enable Zygisk (beta) also enable Enforce Deny List
Select Hide the Magisk app and give any desired name for Magisk to hide its identity
Now go to modules page in Magisk app.
Select Install from source/storage option and chose the downloaded safteynet zip
Reboot
This will pass safetynet but still Indian bank apps won’t work. Keep following below for clear
Go to magisk settings and enter Configure DenyList
Add all the apps you want to hide magisk and root from (such as phonepe, Gpay)
Don’t leave any service from the selected apps unchecked
3. Flash EU Rom​Warning: All your userdata (including pictures and files) will be wiped out
A TWRP backup of current rom is recommended before following the next steps
You can see section 2.2 for the instruction on backup
Download Fastboot EU rom from here: https://androidfilehost.com/?fid=17825722713688263895
Extract all the contents in zip file to any normal folder
We will be using Bootloader/Fastboot mode. Boot into Bootloader: Power off your mobile then hold Volume Down + Power Button till Fastboot bunny pops up
Connect your device to PC
From the extracted folder Open windows_fastboot_first_install_with_data_format.bat(for windows).
You may execute appropriate similar named file if you are running Linux or MacOS
The EU rom flashing process will start. Hit “Y” on keyboard to accept Formatting
Wait patiently while the PC does its Job.
You may see a long pause post “writing Cust” command depending on PC configuration. You should wait for 5 minutes at least, then try hitting any letter key on your keyboard, the process continues this way.
You may hit letter key whenever you see unusual pauses during pushing of super partition file sparse sending 1 of 9 to 9 of 9
Wait till process finishes and reboots
For TWRP and Rooting you can follow the same guide in section 2.
Updating to Miui13/Android 12 EU Rom​
Check out this guide to Update to Android 12
Happy Rooting… Njoy your device.
Lastly.. All the credit goes to respective owners, I have just compiled everything together and in an easy manner. PM me for credits.
Do let me know if you have any suggestions and corrections.
Thanks & Regards,
Abdus Saboor Asad

Reserved

Reserved

Much appreciated, good overview.
Will try when I get my bootloader unlocked.

Rammetje.b said:
Much appreciated, good overview.
Will try when I get my bootloader unlocked.
Click to expand...
Click to collapse
You are welcome.

sasaboor64 said:
You are welcome.
Click to expand...
Click to collapse
Quick question if you allow me.
The unlock boot loader timer starts ticking even without hooking the phone up to the mi unlock tool? Just the dev options, OEM unlock and login to mi account is sufficient?
I remember I messed around with this when I tried to unlock my Poco F1 at the time.
Thanks
Bram

Rammetje.b said:
Quick question if you allow me.
The unlock boot loader timer starts ticking even without hooking the phone up to the mi unlock tool? Just the dev options, OEM unlock and login to mi account is sufficient?
I remember I messed around with this when I tried to unlock my Poco F1 at the time.
Thanks
Bram
Click to expand...
Click to collapse
Good question... I think we should hook once, that's how I unlocked. But I feel it should work without hooking as well.
Anyone should test it and update for us the other way.

When i download the TWRP and boot into TWRP (through fastboot boot "twrp.img"), my touch screen will not work anymore. How could i fix this?

working on miui 13 android 12?

paulboqs said:
working on miui 13 android 12?
Click to expand...
Click to collapse
you may go through the last thread in my post for miui 13 related rooting. this guide is for miui12 rooting and there is no TWRP yet for miui13 for our device

at what point exactly will all my data be wiped?

yuukiw said:
at what point exactly will all my data be wiped?
Click to expand...
Click to collapse
the moment u hit unlock after your waiting period...

sasaboor64 said:
the moment u hit unlock after your waiting period...
Click to expand...
Click to collapse
is there a way to back upp all apps + data?

MIUI13 Android12 How to enter bootloader?
I'm try but FASTBOOT "orange" Showing?
how to enter bootloader? any driver or any solution?

m38d1 said:
MIUI13 Android12 How to enter bootloader?
I'm try but FASTBOOT "orange" Showing?
how to enter bootloader? any driver or any solution?
Click to expand...
Click to collapse
Please make sure you are having latest ADB installed on your machine. The best option is to install Android Studio . Secondly make sure to enable USB debugging .
You can reboot to fastboot through adb commands.
Once you are connected to ADB enter the command below.
ADB reboot Bootloader.
This will reboot to fastboot mode.
Fastboot devices
The above command shows whether you are on fastboot or not.
Now open the unlock tool and unlock your bootloader. Else if you are confident in recovering your device. use the command below
Fastboot flashing unlock
Hope the above helps.

AwkwarddWhale said:
When i download the TWRP and boot into TWRP (through fastboot boot "twrp.img"), my touch screen will not work anymore. How could i fix this?
Click to expand...
Click to collapse
did you found a solution?
this is the first time this happen to me since mi3, RHnote5,7, pocox3nfc, mi11tpro.
tactil isn't working as soon i ented the twrp.. and theres no orange fox for this devices.. shame.

Jctatis said:
did you found a solution?
this is the first time this happen to me since mi3, RHnote5,7, pocox3nfc, mi11tpro.
tactil isn't working as soon i ented the twrp.. and theres no orange fox for this devices.. shame.
Click to expand...
Click to collapse
There is no solution, there is no twrp for Android 12 / MIUI13 yet.

Well I did manage to make it work using a mouse otg. But it useless since theres no storage to flash

mm_rajesh said:
Please make sure you are having latest ADB installed on your machine. The best option is to install Android Studio . Secondly make sure to enable USB debugging .
You can reboot to fastboot through adb commands.
Once you are connected to ADB enter the command below.
ADB reboot Bootloader.
This will reboot to fastboot mode.
Fastboot devices
The above command shows whether you are on fastboot or not.
Now open the unlock tool and unlock your bootloader. Else if you are confident in recovering your device. use the command below
Fastboot flashing unlock
Hope the above helps.
Click to expand...
Click to collapse
thanks
The problem was the phone cable

This TWRP from the first post is Android 12 too?