Related
Hey guys,
I need your advice/help.
I have googled and searched XDA for 5 hours total now and I couldn't find a solution, so please be lenient if someone has already answered this question.
So I was browing along with my D855 32gb with CM13 on it. Then it crashed, which it did sometimes, so I pulled the battery and restarted. But instead of working flawlessly again like it did so many times it kept on crashing after my restarts (5 at least).
So I went to the twrp recovery, erased cache and dalvik cache and restarted.
It went into a bootloop (stuck at CM logo for hours)
Tried to get to the recovery again, doesn't work, stuck at LG logo. DAMN!
So I tried with download mode, but it starts fastboot mode instead.
So I tried booting twrp in tethered mode with
fastboot boot recovery.img
Stuck at TWRP logo...
I decided to go back to stock completely and try to unbrick it this way, but I need download-mode to flash the tot/kdz.
So I tried the following:
Tried flashing matching laf.img this way:
fastboot flash laf laf.img
Error: [1185970] Error: command never completed
[1185970] Error: Auto CMD12 error
[1185970] Error: command completed with errors
[1185970] Error: command never completed
[1185970] Error: command timeout error
[....]
[1191000] Failed Writing block @1
Tried BOOTING laf.img like suggested elsewhere with
fastboot boot laf.img
Error: (like above) then
"Continuous splash enabled, keeping panel alive."
and stuck there forever
So I tried erasign the laf partition before flashing it..
ends with
"MMC erase failed" error.
A "fastboot oem check_mmc" yields it being stuck there until I unplug it then it says "never completed: too many links"
So my guess is that the MMC broke (since it bricked after erasing cache.. which is very strange in my eyes) and therefore the phone is trash..
Do you guys agree? Can I try something else?
Thank you very much for all the suggestions!
i have a very simillar problem
just fully reinstall your phone if that doesnt work ist broken that simple
And how would you do that with just fastboot, no download mode, no recovery, and flashing/booting laf/recovery not working?
try charging itif it charges (gets to the battery charging screen) you still have a partially working bootloader if not it is a paperweight, try the qcom unbrick tool but with mmc not working it will be impossible
Me to, I have the same problem. Me phone freezed a couple of times, then I tried to reinstall CM and it failed and from then I can't even got to Recovery or Download mode. Only LG logo.
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 !
Hello friends
a friend brought me a Moto G7 Play (XT1952-2), and said he had forgotten the password, the email and all, to try to recover, he tried to flash, but did not unlock the bootloader, did not enable USB debugging and did not enable OEM unlock and yet downgraded on mobile.
The result is that the phone no longer leaves the Start Up Failed screen, it shows the following messages:
Fastboot AP Flash Mode (Secure)
SSM: Android checking failed.
No bootable A / B slot
Failed to boot Linux, failing back to fastboot
Fastboot Reason: Falling Through Normal Boot Mode
I already tried to unlock the bootloader, but as the OEM unlock option is not enabled, I could not. I tried to flash with the same rom as before or with a more current one and it didn't change anything either. I've tried basically everything I found in the forums. Can someone give me an idea of what to do?
Tks!
riickseven said:
Hello friends
a friend brought me a Moto G7 Play (XT1952-2), and said he had forgotten the password, the email and all, to try to recover, he tried to flash, but did not unlock the bootloader, did not enable USB debugging and did not enable OEM unlock and yet downgraded on mobile.
The result is that the phone no longer leaves the Start Up Failed screen, it shows the following messages:
Fastboot AP Flash Mode (Secure)
SSM: Android checking failed.
No bootable A / B slot
Failed to boot Linux, failing back to fastboot
Fastboot Reason: Falling Through Normal Boot Mode
I already tried to unlock the bootloader, but as the OEM unlock option is not enabled, I could not. I tried to flash with the same rom as before or with a more current one and it didn't change anything either. I've tried basically everything I found in the forums. Can someone give me an idea of what to do?
Tks!
Click to expand...
Click to collapse
Download Your Latest ota zip from
https://mirrors.lolinet.com/firmware/moto/channel/official/
then flash via rsd lite that will fix your phone and reset it
Help download
motorola/aljeter/aljeter:9/PPPS29.55-35-12-3/a0b9b:user/release-keys
I've been trying to unlock a Blu G5 - I've gotten as far as patching the disk image and all that is left to do is just flash the image onto the phone.
The issue is whenever I try to flash something onto the phone I get the following error :
Code:
FAILED (remote: Flashing Lock Flag is locked. Please unlock it first!)
.
When I go to unlock through Flashing unlock I get the error in the title - OEM unlock gives me cmd not found.
I have USB debugging and OEM unlocking both enabled inside the app settings. I'm not sure if its pertinent but on Magisk I see "Ramdisk : No". I've also been unable to get into recovery mode despite trying every combination possible except for once on accident (which I haven't been able to replicate).
Any help would be appreciated, Thanks!
yodamaul said:
I've been trying to unlock a Blu G5 - I've gotten as far as patching the disk image and all that is left to do is just flash the image onto the phone.
The issue is whenever I try to flash something onto the phone I get the following error :
Code:
FAILED (remote: Flashing Lock Flag is locked. Please unlock it first!)
.
When I go to unlock through Flashing unlock I get the error in the title - OEM unlock gives me cmd not found.
I have USB debugging and OEM unlocking both enabled inside the app settings. I'm not sure if its pertinent but on Magisk I see "Ramdisk : No". I've also been unable to get into recovery mode despite trying every combination possible except for once on accident (which I haven't been able to replicate).
Any help would be appreciated, Thanks!
Click to expand...
Click to collapse
having the same problem right now. did you get a fix?
Hello everybody, I have a problems with unbricking Note 8 Pro - begonia - M1906G7G.
It stuck in boot loop. Bootloader is locked.
I have tried that python bypass and flashing firmware using SP Flash Tool. I get success / done message after a while, but when I power the phone, there are no changes. Phone is sitll in boot loop.
Is there anything, what can I do?
Thank you in advance!
EDIT:
Have just tried to flash TWRP, now I'm getting "system has been destroyed" error. So flashing probably works. Problem must be somewhere else.
If you dont care about data (I think you dont because you flashed by Sp flash tool), just unlock bootloader and flash by Sp Flash Tool again. Maybe you flash fastboot rom not same region with stock phone with locked bootloader. This is the way to unlock bootloader unofficial way you can try.
Kirasu2080 said:
If you dont care about data (I think you dont because you flashed by Sp flash tool), just unlock bootloader and flash by Sp Flash Tool again. Maybe you flash fastboot rom not same region with stock phone with locked bootloader. This is the way to unlock bootloader unofficial way you can try.
Click to expand...
Click to collapse
At first, I could not use that tool. Everytime I tried, I get this error: "mtk: error: argument cmd: invalid choice: 'xflash'".
I had to edit the mtkclient-gui.py with this two commands (from github)
subprocess.call(f"{runtime} mtkclient/mtk e metadata,userdata,md_udc")
subprocess.call(f"{runtime} mtkclient/mtk da seccfg unlock")
Now after running the commands I get this in log: "Failed to format all partitions." and after that: "
100.0% Write (Sector 0x1 of 0x1, ) 0.05 MB/s
xflashext - Successfully wrote seccfg."
After this process, when I turn on the phone I get errors:
"dm-verify error
Android system on your device is corrupted."
When I check with fastboot mode, phone have bootloader unlocked now.
So I have tried to flash firmware using SP Flash Tool, got 100% done success message, but on phone I still can see only:
"dm-verify error
Android system on your device is corrupted."
I have also tried fastboot rom and flashing using fastboot "flash_all.bat". Result was "OKAY" for every single file. Phone rebooted and again this error:
"dm-verify error
Android system on your device is corrupted.".
UPDATE:
Finally found firmware, which does not give me "dm-verify error. Android system on your device is corrupted.". But phone is still in a bootloop.
Growicek said:
At first, I could not use that tool. Everytime I tried, I get this error: "mtk: error: argument cmd: invalid choice: 'xflash'".
I had to edit the mtkclient-gui.py with this two commands (from github)
subprocess.call(f"{runtime} mtkclient/mtk e metadata,userdata,md_udc")
subprocess.call(f"{runtime} mtkclient/mtk da seccfg unlock")
Now after running the commands I get this in log: "Failed to format all partitions." and after that: "
100.0% Write (Sector 0x1 of 0x1, ) 0.05 MB/s
xflashext - Successfully wrote seccfg."
After this process, when I turn on the phone I get errors:
"dm-verify error
Android system on your device is corrupted."
When I check with fastboot mode, phone have bootloader unlocked now.
So I have tried to flash firmware using SP Flash Tool, got 100% done success message, but on phone I still can see only:
"dm-verify error
Android system on your device is corrupted."
I have also tried fastboot rom and flashing using fastboot "flash_all.bat". Result was "OKAY" for every single file. Phone rebooted and again this error:
"dm-verify error
Android system on your device is corrupted.".
UPDATE:
Finally found firmware, which does not give me "dm-verify error. Android system on your device is corrupted.". But phone is still in a bootloop.
Click to expand...
Click to collapse
Flash this TWRP if you using Miui 12.5.x: MOD EDIT: Link Removed
Try
- Advanced > Patch vbmeta
- Reboot > System and check
If you dont have twrp:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
And vbmeta.img take from fastboot or recovery rom you flashed
If not work, try flash custom rom same as Miui Firmware based to check if phone still can work or not.
And if Custom roms work, just throw Miui away.
Kirasu2080 said:
Flash this TWRP if you using Miui 12.5.x: MOD EDIT: Link Removed
Try
- Advanced > Patch vbmeta
- Reboot > System and check
If you dont have twrp:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
And vbmeta.img take from fastboot or recovery rom you flashed
If not work, try flash custom rom same as Miui Firmware based to check if phone still can work or not.
And if Custom roms work, just throw Miui away.
Click to expand...
Click to collapse
Have tried flashing that TWRP. After doing it, I have tried: fastboot reboot recovery. Recovery never loaded. Just pure bootloop. Have also tried flashing vbmeta.img from firmware I have flashed. Then I powered on the phone. Again bootloop. When I tried to flashing few others TWRP. Same result - bootloop. Recovery never boot.
Could not find any custom rom, which is flashable through SP Flash Tool (With working scatter etc..), so I have tried to flash img files from custom rom one by one using fastboot (probably did something wrong or maybe not, idk), phone still in bootloop.
Growicek said:
At first, I could not use that tool. Everytime I tried, I get this error: "mtk: error: argument cmd: invalid choice: 'xflash'".
I had to edit the mtkclient-gui.py with this two commands (from github)
subprocess.call(f"{runtime} mtkclient/mtk e metadata,userdata,md_udc")
subprocess.call(f"{runtime} mtkclient/mtk da seccfg unlock")
Now after running the commands I get this in log: "Failed to format all partitions." and after that: "
100.0% Write (Sector 0x1 of 0x1, ) 0.05 MB/s
xflashext - Successfully wrote seccfg."
After this process, when I turn on the phone I get errors:
"dm-verify error
Android system on your device is corrupted."
When I check with fastboot mode, phone have bootloader unlocked now.
So I have tried to flash firmware using SP Flash Tool, got 100% done success message, but on phone I still can see only:
"dm-verify error
Android system on your device is corrupted."
I have also tried fastboot rom and flashing using fastboot "flash_all.bat". Result was "OKAY" for every single file. Phone rebooted and again this error:
"dm-verify error
Android system on your device is corrupted.".
UPDATE:
Finally found firmware, which does not give me "dm-verify error. Android system on your device is corrupted.". But phone is still in a bootloop.
Click to expand...
Click to collapse
That dm-verity error is normal if you use mtkclient. You need to lock the phone in mtkclient and reunlock the phone in the normal way to get rid of that error
Also the link seems to got removed but i use Salih-Sonar's TWRP for MIUI 12.5 (search begonia-oss and download the MIUI 12.5 one)
You can just flash the full fastboot rom and it should work unless you corrupted properitary partitions (nvdata,persist,nvcfg etc)
Canny1913 said:
That dm-verity error is normal if you use mtkclient. You need to lock the phone in mtkclient and reunlock the phone in the normal way to get rid of that error
Also the link seems to got removed but i use Salih-Sonar's TWRP for MIUI 12.5 (search begonia-oss and download the MIUI 12.5 one)
You can just flash the full fastboot rom and it should work unless you corrupted properitary partitions (nvdata,persist,nvcfg etc)
Click to expand...
Click to collapse
I have finally after hours and hours of trying flashed firmware, which is not stuck in bootloop. Now the phone reboots after few seconds of running. I found out, that CPU is overheating, so probably hardware issue. Will try reball of the CPU chip and we will see, if it helps.
Growicek said:
I have finally after hours and hours of trying flashed firmware, which is not stuck in bootloop. Now the phone reboots after few seconds of running. I found out, that CPU is overheating, so probably hardware issue. Will try reball of the CPU chip and we will see, if it helps.
Click to expand...
Click to collapse
Well good luck then.
There is a super small chance that the overheat is be related to the firmware though. But the odds of that are really low if the phone is running normal.
Canny1913 said:
Well good luck then.
There is a super small chance that the overheat is be related to the firmware though. But the odds of that are really low if the phone is running normal.
Click to expand...
Click to collapse
Phone was in a bootloop, so I have unlocked bootloader, flashed latest firmware, phone was still in bootloop. So I have flashed very very old firmware and then phone booted successfuly. I was able to set language, region, connect to wifi and then freeze. After few seconds it rebooted. I have checked the temperature of CPU (with my finger) and it was quite hot.
Let's hope that reballing will help.