Related
I just bricked my phone :crying: :crying:
I wanna get back to the official rom, after trying android P (without make it work).
(the rom is from http://en.miui.com/download-354.html)
But I run the wrong script and take the flash_all_lock.img
And my device is stuck on android 8.1 bootloop (It boot, but i get an animated line loop ...)
Any ideas or tricks before i get it back to warranty ?
Thanks
Unlock bootloader and flash again. You can find a guide to unlock bootloader at the beginning of this guide.
BubuXP said:
Unlock bootloader and flash again. You can find a guide to unlock bootloader at the beginning of this guide.
Click to expand...
Click to collapse
But since I flashed the official rom with data whipe, I'm unable to go to dev option and enter OEM Unlocking .... And Fastboot respond me that my device is locked
Seems like my only option left is to boot into EDL mode ...
But seems fastboot oem edl does not work I don't lnow how to handle the problem
droopeur said:
Seems like my only option left is to boot into EDL mode ...
But seems fastboot oem edl does not work I don't lnow how to handle the problem
Click to expand...
Click to collapse
Have you tried to switch the active slot?
Try if it boots using
fastboot set_active a
or
fastboot set_active b
If not working, can you enter recovery (power on with Volume up button pressed)?
If you can enter recovery, hold down the power button for 3-5 seconds and then press and release the Volume up button, to make commands appear. Then your only hope is to install the OTA update zip from there (copy the OTA in a microSD card, there is a thread where you can find the link to the OTA zip).
In my opinion, "OEM unlocking" in developer options MUST be always keep active, because incidents like this could happen, and because even without modding, an OTA could go wrong resulting in your same situation.
I was in your same situation (OEM unlocking disabled and then I locked bootloader with a custom ROM installed) with a Nexus 5X.
I don't remember well how I fixed it, but I remember entering in Qualcomm download mode (should be the same EDL mode) and loading a file found after many hours of research in strange forums and sites.
BubuXP said:
Have you tried to switch the active slot?
Try if it boots using
fastboot set_active a
or
fastboot set_active b
Click to expand...
Click to collapse
In fact, both work, but my phone still stucked at the bootloader (infinite line animation in both cases).
BubuXP said:
If not working, can you enter recovery (power on with Volume up button pressed)?
If you can enter recovery, hold down the power button for 3-5 seconds and then press and release the Volume up button, to make commands appear. Then your only hope is to install the OTA update zip from there (copy the OTA in a microSD card, there is a thread where you can find the link to the OTA zip).
Click to expand...
Click to collapse
Yes I can enter recovery and I have already tried this, but I always end up with the error:
Code:
E: Unknow volume for path [/sideload/package.zip]
Verifying update package...
Update package verification took 17.3 s (result 0)
Installing update...
E:Error il /sideload/package.zip (Status 1)
Installation aborted
BubuXP said:
In my opinion, "OEM unlocking" in developer options MUST be always keep active, because incidents like this could happen, and because even without modding, an OTA could go wrong resulting in your same situation.
I was in your same situation (OEM unlocking disabled and then I locked bootloader with a custom ROM installed) with a Nexus 5X.
I don't remember well how I fixed it, but I remember entering in Qualcomm download mode (should be the same EDL mode) and loading a file found after many hours of research in strange forums and sites.
Click to expand...
Click to collapse
Yes of course !
But I revert to stock rom with Mi Flash and I click on Flash all and lock, since the telephone should have been "brand new" it should not have any problems but ...
I have to enter EDL mode, but don't know how to do it since modified fastboot executables does not activate it it just reboot the phone...
Deep flash cable may help but not shure if it works, or I may have to disassemble the device to find EDL pins...
after unlock bootloader type fastboot flashing unlock_critical and flash with miflash tool
LUNARIO said:
after unlock bootloader type fastboot flashing unlock_critical and flash with miflash tool
Click to expand...
Click to collapse
But since I can't activate OEM I can't unlock bootloader....
try this http://www.xiaomitool.com/ not sure if it works on our phone but maybe can unlock the bootloader so you can use miflash
Have you sideloaded the zip? I think it's better to copy the OTA zip to microSD than ADB sideload.
droopeur said:
I have to enter EDL mode, but don't know how to do it since modified fastboot executables does not activate it it just reboot the phone...
Deep flash cable may help but not shure if it works, or I may have to disassemble the device to find EDL pins...
Click to expand...
Click to collapse
There should be only two methods for entering EDL:
1- request authorization in en.miui.com forum. Sometimes the admins accept requests to give an account one EDL flash permission (but I don't know if it works with AndroidOne devices).
2- finding the test point in the phone's motherboard.
Hi guys,
i tried to install this twrp but it doesnt work...
so i searched on internet and i found another article, i tried to check the current partition and install in another way
for first:
fastboot getvar current-slot
after i do this
fastboot boot_b recovery.img
and then
fastboot set_active b
so nothing to do....but right now my MI A2 lite not boot.
i try again to check my partition but this time i have no replay.
i have unlocked bootloader but i cant go to recovery and i cant boot!!
someone can help me please?
I HAVE THE SAME PROBLEM
everything you said is completely simillar to mine. Can someone help us? Or did you already fix it? Please help me i need my phone working.
I have same problem fastboot flash but after that, it started to reboot automatically. The phone was automatically turning off and on. I again did a "clean all and lock" via miflash tool but still now, no result!
I can boot into recovery without having any problem. But when I boo to setup country date....etc, it starts its auto rebooting process,
Any help ?
droopeur said:
But since I can't activate OEM I can't unlock bootloader....
Click to expand...
Click to collapse
Same situation here. I am desperate!! Did you solve it?
Isso resolve
steledama said:
Same situation here. I am desperate!! Did you solve it?
Click to expand...
Click to collapse
gadgetsfarm.com/download-mi-a2-lite-fastboot-rom-v9-6-4-download/[/url]
How to unbrick?
Hey guys. I bricked my Mi2 Lite as well. Is there any step by step way to unbrick?
had the same problem, was stuck in the bootloop even after I flashed img with MiFlash! NOTE: MY BOOTLOADER WAS UNLOCKED!!! (LUCKLY I DID NOT TRIED FLASH ALL AND UNLOCK!)
headed to this thread
Code:
fastboot flashing unlock
fastboot flashing unlock_critical
did not work, I get error saying FAILED
but after i used
Code:
fastboot oem edl
I went to MiFlash and used "Clean all" option (again note DON'T use "Clean all and lock"!!!). It took around 5 minutes to flash and my notif. light blinked whole the time. After it say "Success" I was able to normaly boot the phone again
Find "Mi A2 Lite toolkit V 1.0.4.2" and use it to flash stock 8.1, it will do all the magic with a few clicks, just don't interrupt it until your phone restarts and you get the "Welcome" screen. After you can do the upgrade to Pie via OTA.
Hi, where i can find MI A2 Lite Tool Kit? i open my device and i can put in EDL mode., my computer detect my pone in EDL mode, but i can not know do.
I like bypass FRP, can anybody help me
Thanks.
mr_techno said:
Find "Mi A2 Lite toolkit V 1.0.4.2" and use it to flash stock 8.1, it will do all the magic with a few clicks, just don't interrupt it until your phone restarts and you get the "Welcome" screen. After you can do the upgrade to Pie via OTA.
Click to expand...
Click to collapse
Hi all,
I also had same problem and I just resolve it.
My phone was in bootloop mode after stock rom flashing...
You don't need apply "fastboot oem edl" !
Just be sure your device is unlocked.
Download first stock rom (V9.6.4.0.ODLMIFF Firmware for Mi A2 Lite). If you flash last ROM, it don't work.
Flash it with XiaoMiFlash tool (don't forget to enable "Clean All") in bottom of the tool.
After reboot, you can apply OTA updates.
Enjoy !
Hi,
After several ROM flashings, my A2 Lite is in bootloop mode.
To try to recover my phone, I did followings.
Installed adb, fastboot, miflash.
Executed 'fastboot oem edl' - successful
Miflash of 'daisy_global_images_V9.6.10.0.ODLMIFF_8.1' gives 'SUCCESS' message, however still in bootloop mode.
I opened the back cover and successfully put the phone in edl mode.
Miflash again with the same ROM folder with 'SUCCESS' message , however still in bootloop mode
When I tried 'fastboot flashing unlock' or 'fastboot flashing unlock_critical' command, it produced - 'Failed, remote unknown command' message.
When I try ' fastboot boot twrp_for_daisy.img' , successfully executed . however the phone can not boot in recovery mode.
I would appreciate very much if somebody provides me any help.
Best regards,
Moricelo said:
Hi,
After several ROM flashings, my A2 Lite is in bootloop mode.
To try to recover my phone, I did followings.
Installed adb, fastboot, miflash.
Executed 'fastboot oem edl' - successful
Miflash of 'daisy_global_images_V9.6.10.0.ODLMIFF_8.1' gives 'SUCCESS' message, however still in bootloop mode.
I opened the back cover and successfully put the phone in edl mode.
Miflash again with the same ROM folder with 'SUCCESS' message , however still in bootloop mode
When I tried 'fastboot flashing unlock' or 'fastboot flashing unlock_critical' command, it produced - 'Failed, remote unknown command' message.
When I try ' fastboot boot twrp_for_daisy.img' , successfully executed . however the phone can not boot in recovery mode.
I would appreciate very much if somebody provides me any help.
Best regards,
Click to expand...
Click to collapse
Try changing boot slots via fastboot command
So, a few months ago I rooted my device with twrp and then installed magisk manager... A few days later the manager stopped working and I got tired of not being able do do nothing so I tried to unroot. I used mi flash to flash the daisy rom and it didn't work so I tried to load to the twrp app and flash through there. Didn't work either. From then on every time I boot the device it shows the message "the system has been destroyed" and Bc of that I searched for solutions. I kinda found one. I boot to fastboot mode and with the platform tools I write on the command line ". /fastboot devices" and then it shows my device. After I write ". /fastboot boot continue" and it starts booting the device and it has worked for like 2 months but 2 days ago I had to reboot my device Bc it started to freeze but when I load to fastboot mode and plug it to the pc it show a prompt saying "the device is not recognized" and the device reboots to the message "system has been destroyed". Pls help, I've searched everywhere and didn't find any solution
Are you have your bootloader unlocked? I guess no, the most "easy" solution for your problem is test point , never fail, you need to download Qualcomm drivers (search in Google) open your device connect your device, your phone need to be recognized like 9008 in manager drivers of your PC then flash stock room in mi flash (flash all option) my recommendation is flash 10.0.13.0 or 10.0.18 version of stock rom, good luck.
Os_Herdz said:
Are you have your bootloader unlocked? I guess no, the most "easy" solution for your problem is test point , never fail, you need to download Qualcomm drivers (search in Google) open your device connect your device, your phone need to be recognized like 9008 in manager drivers of your PC then flash stock room in mi flash (flash all option) my recommendation is flash 10.0.13.0 or 10.0.18 version of stock rom, good luck.
Click to expand...
Click to collapse
Yes, my bootloader is unlocked, and is not recognized on the miflash tool.
I cant't even boot the phone to edl mode
0flip3 said:
Yes, my bootloader is unlocked, and is not recognized on the miflash tool.
I cant't even boot the phone to edl mode
Click to expand...
Click to collapse
you are trying to get to edl mode by typing command "fastboot oem edl" when phone is in fastboot?
So basically, I've tried to flash a custom ROM on my Mi A2 Lite. After flashing the TWRP recovery on fastboot, it shows the message "Device unable to boot
Error - mdtp image is corrupted."
I need help. Please. If I can't fix this, I'm just going to give up. I've also flashed the stock ROM images, but it still doesn't boot into the system (It doesn't even work, actually). :crying: :crying: :crying:
I've also Googled a lot for a fix, but can't seem to find one that works. I did everything I could do on fastboot (fastboot tool was showing my phone was on fastboot in the cmd) but none worked. It showed this error: fastboot write command failed (no error). If there is a fix, please reply. I would be crying if it works.
Did you flash both _a and _b partitions?
Pixeloyco said:
So basically, I've tried to flash a custom ROM on my Mi A2 Lite. After flashing the TWRP recovery on fastboot, it shows the message "Device unable to boot
Error - mdtp image is corrupted."
I need help. Please. If I can't fix this, I'm just going to give up. I've also flashed the stock ROM images, but it still doesn't boot into the system (It doesn't even work, actually). :crying: :crying: :crying:
I've also Googled a lot for a fix, but can't seem to find one that works. I did everything I could do on fastboot (fastboot tool was showing my phone was on fastboot in the cmd) but none worked. It showed this error: fastboot write command failed (no error). If there is a fix, please reply. I would be crying if it works.
Click to expand...
Click to collapse
Just flash stock back via fastboot and MiFlash and flash custom ROM again with their instructions followed.
And BTW, use offain's TWRP for flashing custom ROMs (most).
Majaque said:
Did you flash both _a and _b partitions?
Click to expand...
Click to collapse
Yes I did, but it always shows the error "write command failed(no error)" during the flashing process.
RFD80M-75679 said:
Just flash stock back via fastboot and MiFlash and flash custom ROM again with their instructions followed.
And BTW, use offain's TWRP for flashing custom ROMs (most).
Click to expand...
Click to collapse
Ok, so I did that. But I accidentally selected flash_all_lock.bat instead of flash_all.bat.... Now it's stuck in a bootloop.
Pixeloyco said:
Ok, so I did that. But I accidentally selected flash_all_lock.bat instead of flash_all.bat.... Now it's stuck in a bootloop.
Click to expand...
Click to collapse
Try wipe data/cache from stock recovery. If no luck, then try the EDL short circuit test point method and reflash stock ROM again with MiFlash. If all fails, go to service center.
Test point EDL needs very short wire (or tweezers), your regular USB cable and Qualcomm Drivers. Disconnect battery before short circuit the test points.
Test Point video tutorial: https://www.youtube.com/watch?v=BrEyAEXid_o
Test Point Location Diagram: https://gsm5g917658702.files.wordpress.com/2019/02/edl-testpoint-xiaomi-mi-a2lite.png
Good night.
I have been using for a few days the YAAP custom rom for android 11 on my 7T, and it's been great. But I wanted to root it for some customizations and tried to flash magisk through mauronofrio's unnoficial TWRP. After trying to flash through it, my phone bricked. I can't get into fastbootd mode and the
HTML:
fastboot getvar is-userspace
command outputs "no", so I couldn't re-flash YAAP normally. I tried using the MSM tool for the 7T but I was also not able to boot into EDL mode. When I try to boot into it through the vol up/down mode, it reboots into bootloader again, and the
HTML:
fastboot oem edl
command returns FAILED (remote: unknown command).
I can flash twrp, but when I try to flash the YAAP zip, it shows me an error.
It shows signs of life, as it gets caught into the OOS boot animation loop, so I know there is a way around it, but I am having trouble figuring out how.
Would anyone here know how to circulate this issue? Or has been through something like this?
Shiro744760 said:
Good night.
I have been using for a few days the YAAP custom rom for android 11 on my 7T, and it's been great. But I wanted to root it for some customizations and tried to flash magisk through mauronofrio's unnoficial TWRP. After trying to flash through it, my phone bricked. I can't get into fastbootd mode and the
HTML:
fastboot getvar is-userspace
command outputs "no", so I couldn't re-flash YAAP normally. I tried using the MSM tool for the 7T but I was also not able to boot into EDL mode. When I try to boot into it through the vol up/down mode, it reboots into bootloader again, and the
HTML:
fastboot oem edl
command returns FAILED (remote: unknown command).
I can flash twrp, but when I try to flash the YAAP zip, it shows me an error.
It shows signs of life, as it gets caught into the OOS boot animation loop, so I know there is a way around it, but I am having trouble figuring out how.
Would anyone here know how to circulate this issue? Or has been through something like this?
Click to expand...
Click to collapse
If you are getting as far as the boot logo then you might be able to format data and try it
can't you reboot to EDL from fastboot?
fastboot reboot EDL ?
You said you can't use the MSM tool. Have you tried the regular all-in-one tool here on the forum?
Try fastboot boot twrp.img, format data and reflash the custom rom?
I'm just throwing ideas out here they may not be the best lol
redemptionx11 said:
If you are getting as far as the boot logo then you might be able to format data and try it
can't you reboot to EDL from fastboot?
fastboot reboot EDL ?
Click to expand...
Click to collapse
Can't. I have tried it before. fastboot reboot edl says the command is unknown, and the existing command (fastboot reboot emergency) throws me back to the bootloader.
The logo got weird. It shows up for a second after turning on and then the bootloader shows up.
redemptionx11 said:
You said you can't use the MSM tool. Have you tried the regular all-in-one tool here on the forum?
Try fastboot boot twrp.img, format data and reflash the custom rom?
I'm just throwing ideas out here they may not be the best lol
Click to expand...
Click to collapse
I haven't tried the all-in-one tool yet, but I don't know which one is it yet lol.
As for twrp this is the log I get:
HTML:
PS D:\Documentos\ADB> fastboot boot .\recovery-oneplus7t-3.4.2-10.0-b26.img
downloading 'boot.img'...
OKAY [ 2.318s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 2.337s
I'm going to assume you did fastboot reboot fastboot before you tried yes?
I'd go try the all in one. There's a thread for it named "all in one" or something.
The tool might have an option to reboot to EDL I can't remember but I've fixed several soft bricks using it.
redemptionx11 said:
I'm going to assume you did fastboot reboot fastboot before you tried yes?
Click to expand...
Click to collapse
Yes I did. Powershell says it does not exist and list all other commands
redemptionx11 said:
I'd go try the all in one. There's a thread for it named "all in one" or something.
The tool might have an option to reboot to EDL I can't remember but I've fixed several soft bricks using it.
Click to expand...
Click to collapse
I will look into it
The all in one worked for getting into the EDL mode. And for the rest of the process, @SkippRunning really helped a lot. Kudos for him for helping out lost souls and bricked devices!
Shiro744760 said:
The all in one worked for getting into the EDL mode. And for the rest of the process, @SkippRunning really helped a lot. Kudos for him for helping out lost souls and bricked devices!
Click to expand...
Click to collapse
ayyy well done man. Good to see you got it going
maybe you can try changing the slot from a to b or opposite