Related
I was trying to get hands on RR (second version) , I went to developer setting enabled USB Debugging Booted into Fastboot mode and while i was flashing system.img. I noticed it shows Bootloader Unlocked Red and FRP locked Green I happened to disable developer option in process of usb debuging which might have unchecked OEM Unlocking
Now while flashing i get this
sending sparse 'system' 1/4 (460796 KB)...
OKAY [ 23.100s]
writing 'system' 1/4...
FAILED (remote: Command not allowed)
finished. total time: 23.131s
I can neither flash RR or Stock system.img but i can access my TWRP recovery ( Oreo)
Any way to fix it? Can i flash RR or Stock system.img in TWRP?
TIA
Username.php said:
I was trying to get hands on RR (second version) , I went to developer setting enabled USB Debugging Booted into Fastboot mode and while i was flashing system.img. I noticed it shows Bootloader Unlocked Red and FRP locked Green I happened to disable developer option in process of usb debuging which might have unchecked OEM Unlocking
Now while flashing i get this
sending sparse 'system' 1/4 (460796 KB)...
OKAY [ 23.100s]
writing 'system' 1/4...
FAILED (remote: Command not allowed)
finished. total time: 23.131s
I can neither flash RR or Stock system.img but i can access my TWRP recovery ( Oreo)
Any way to fix it? Can i flash RR or Stock system.img in TWRP?
TIA
Click to expand...
Click to collapse
Speculation. Bit as long as twrp is working and bootloader open. Best thing is to go with stock . That way hopefully can access Dev options to allow frp unlock.
As long as frp is in locked DO NOT try flash stock recovery till last resort. Because twrp will give more options than stock. And will not be able to return to twrp with frp in locked state.
Of course it seems might be best option to flash a full ota(specific for your device). And that will need no-check recovery, so is tough choice
mrmazak said:
Speculation. Bit as long as twrp is working and bootloader open. Best thing is to go with stock . That way hopefully can access Dev options to allow frp unlock.
As long as frp is in locked DO NOT try flash stock recovery till last resort. Because twrp will give more options than stock. And will not be able to return to twrp with frp in locked state.
Of course it seems might be best option to flash a full ota(specific for your device). And that will need no-check recovery, so is tough choice
Click to expand...
Click to collapse
Fixed it!! Formatted data and booted into EMUI and Flash RR again
Thanks
Honor 7x boot loop, Twrp 3.1.1.0 and Frp lock
mrmazak said:
Speculation. Bit as long as twrp is working and bootloader open. Best thing is to go with stock . That way hopefully can access Dev options to allow frp unlock.
As long as frp is in locked DO NOT try flash stock recovery till last resort. Because twrp will give more options than stock. And will not be able to return to twrp with frp in locked state.
Of course it seems might be best option to flash a full ota(specific for your device). And that will need no-check recovery, so is tough choice
Click to expand...
Click to collapse
Status of phone Honor 7x BND-L24 usa variant
1.Boot loop
2. frp lock,bootloader unlocked
3.It can boot into twrp 3.1.1-0
4.It can boot into eRecovery
5.When i try to wipe data/factory reset from eRecovery it boots and restarts into twrp
6.When i try to download latest version it says "Getting package info failed"
7.I believe it locked when i was trying to install gpu turbo update ..i started by clearing dalvik and cache.I have also wiped data currently.
Putnam123 said:
Status of phone Honor 7x BND-L24 usa variant
1.Boot loop
2. frp lock,bootloader unlocked
3.It can boot into twrp 3.1.1-0
4.It can boot into eRecovery
5.When i try to wipe data/factory reset from eRecovery it boots and restarts into twrp
6.When i try to download latest version it says "Getting package info failed"
7.I believe it locked when i was trying to install gpu turbo update ..i started by clearing dalvik and cache.I have also wiped data currently.
Click to expand...
Click to collapse
Oh, there is an frp-unlock.zip file that can be installed with TWRP. That should fix the lock.
As for the boot looping, I suppose something you flashed caused it.
After flashing the frp-unlock use hwota and go to next stock ota
mrmazak said:
Oh, there is an frp-unlock.zip file that can be installed with TWRP. That should fix the lock.
As for the boot looping, I suppose something you flashed caused it.
After flashing the frp-unlock use hwota and go to next stock ota
Click to expand...
Click to collapse
https://forum.xda-developers.com/honor-7x/how-to/tested-unbrick-bnd-l24-t3811645
I Used this guide at it helped me been stuck on that locked state for almost 2 days now , thanks for the reply.
can anyone help or point me in the right direction.
i have the us variant 7x and today there was oct update. after updating the phone rebooted and was stuck on honor logo.
i was able to get fastboot but not recovery. i tried adb to reboot recovery and it did not work, as if the recovery was not there.
so i then decided i wold try to reflash stock firmware. obviously i neede to unlock boot loader to do this so i unlocked it.
now the phone boots to the unlocked boot screen and sits on "your device is booting now..."
the real problem now is i cannot access bootloader any longer.
to recap...i cannot enter bootloader or recovery and the device is unlocked.
please help
joenun said:
can anyone help or point me in the right direction.
i have the us variant 7x and today there was oct update. after updating the phone rebooted and was stuck on honor logo.
i was able to get fastboot but not recovery. i tried adb to reboot recovery and it did not work, as if the recovery was not there.
so i then decided i wold try to reflash stock firmware. obviously i neede to unlock boot loader to do this so i unlocked it.
now the phone boots to the unlocked boot screen and sits on "your device is booting now..."
the real problem now is i cannot access bootloader any longer.
to recap...i cannot enter bootloader or recovery and the device is unlocked.
please help
Click to expand...
Click to collapse
Unlocking needs recovery. So when you unlocked when ypi couldn't enter recovery that caused this problem.
Have seen this stuck at booting before..it is a little bit of a pain to get through. You need to have the battery totally dead, and on the first boot with USB cable plugged on you should be able to get onto fastboot. (Disconnecting battery will do it too)
mrmazak said:
Unlocking needs recovery. So when you unlocked when ypi couldn't enter recovery that caused this problem.
Have seen this stuck at booting before..it is a little bit of a pain to get through. You need to have the battery totally dead, and on the first boot with USB cable plugged on you should be able to get onto fastboot. (Disconnecting battery will do it too)
Click to expand...
Click to collapse
thank you very much i will wait for it to die then try rebooting into fastboot.
i went ahead and had honor send me a label to return for repair just in case.
Today morning, I started facing bootloops on my whyred (running Pixel Experience pie latest).I clean flashed PE but couldn't boot into it. Phone would be stuck in bootloops. I changed roms to Potato OS,AICP,Descandent,Syberia,RR etc. but none could boot. All of them would get stuck in boot loop. ( I clean flashed all of them, wiping even my internal storage each time) Then I tried clean flashing Global MIUI latest stable, it boots but my sim cards are not detected and wifi doesnt turn on.Therefore, I was unable to log in to my mi account to verify the device.I tthen downloaded the latest stable MIUI (global) fastboot rom,using the mi flash tool i tried flashing, mi flash tool gave an error:
Code:
Flash antirbpass error
I checked the logs and it said:
Code:
echo current device antirollback version is greater than this package.
I am on anti 4, the rom is anti 4 compliant...why this error. Please help!
Also why was every other rom bootlooping?
Edit1: I still have access to fastboot and TWRP.
Edit2: On the latest Indian beta, It says my IMEI and mac address is not available ( possible curroption) that explains the sim card and wifi not working. Any fix for this?
Edit3: I am now able to boot properly into MIUI (latest Indian developer build) I just need to repair my IMEI and Mac now...has any1 got any idea on how I am supposed to fix it?
rtm2000 said:
Today morning, I started facing bootloops on my whyred (running Pixel Experience pie latest).I clean flashed PE but couldn't boot into it. Phone would be stuck in bootloops. I changed roms to Potato OS,AICP,Descandent,Syberia,RR etc. but none could boot. All of them would get stuck in boot loop. ( I clean flashed all of them, wiping even my internal storage each time) Then I tried clean flashing Global MIUI latest stable, it boots but my sim cards are not detected and wifi doesnt turn on.Therefore, I was unable to log in to my mi account to verify the device.I tthen downloaded the latest stable MIUI (global) fastboot rom,using the mi flash tool i tried flashing, mi flash tool gave an error:
Code:
Flash antirbpass error
I checked the logs and it said:
Code:
echo current device antirollback version is greater than this package.
I am on anti 4, the rom is anti 4 compliant...why this error. Please help!
Also why was every other rom bootlooping?
Edit1: I still have access to fastboot and TWRP.
Edit2: On the latest Indian beta, It says my IMEI and mac address is not available ( possible curroption) that explains the sim card and wifi not working. Any fix for this?
Edit3: I am now able to boot properly into MIUI (latest Indian developer build) I just need to repair my IMEI and Mac now...has any1 got any idea on how I am supposed to fix it?
Click to expand...
Click to collapse
No participations yet...hmm...guys??
rtm2000 said:
No participations yet...hmm...guys??
Click to expand...
Click to collapse
Just be patient. This isn't a regular bug/error that can be easily solved.
You we're running PE ROM without problems, what did you do in your device that started to bootloop?
Letrix said:
Just be patient. This isn't a regular bug/error that can be easily solved.
You we're running PE ROM without problems, what did you do in your device that started to bootloop?
Click to expand...
Click to collapse
Thanks for replying...
I did nothing, literally nothing...I just kept my phone for overnight charging and found it bootlooping in the morning. (It may have been running the whole night..)
ON another note, flashing the latest miui global stable via mi flash tool gives the error : Flash antirbpass error
I am on anti 4 , the rom I am trying to flash is anti 4 too...then why doesn't it let me flash?
...........?
rtm2000 said:
Thanks for replying...
I did nothing, literally nothing...I just kept my phone for overnight charging and found it bootlooping in the morning. (It may have been running the whole night..)
ON another note, flashing the latest miui global stable via mi flash tool gives the error : Flash antirbpass error
I am on anti 4 , the rom I am trying to flash is anti 4 too...then why doesn't it let me flash?
Click to expand...
Click to collapse
If you have adb and fastboot installed system wide, uninstall it . Reinstall drivers from xiaomi miflash and try again. It looks like your efs partition has been corrupted. If you have twrp backup of stock rom, use it.
arunmohan16 said:
If you have adb and fastboot installed system wide, uninstall it . Reinstall drivers from xiaomi miflash and try again. It looks like your efs partition has been corrupted. If you have twrp backup of stock rom, use it.
Click to expand...
Click to collapse
Thanks for your reply.
Actually, I don;t have the backup of my EFS partition with me. Is there any other way?
___________________________?
Hello everyone,
My Mi A2 Lite just died today. I was on stock 8.1 rooted and suddenly it freezes so I rebooted it and I got stuck on Android One logo WITHOUT ANY animation.
I tried to boot into recovery via adb but I get stuck on TWRP logo. I tried to flash fastboot image but nothing changes....
I really need help because I'm out of options
pocchio said:
Hello everyone,
My Mi A2 Lite just died today. I was on stock 8.1 rooted and suddenly it freezes so I rebooted it and I got stuck on Android One logo WITHOUT ANY animation.
I tried to boot into recovery via adb but I get stuck on TWRP logo. I tried to flash fastboot image but nothing changes....
I really need help because I'm out of options
Click to expand...
Click to collapse
Two quick questions:
1.The phone died on its self without your intervention or...?
2.Have you tried to flash the stock firmware via MiFlash , while the phone is in edl mode(the command is: fastboot oem edl)?
1) yes, it got stuck so I rebooted it
2) I tried flashing with MiFlash tool in fastboot mode. When I connect it in fastboot edl the mi flash tool sees it as COM and therefore I’m not able to flash it.
I’m I doing something wrong?
pocchio said:
Hello everyone,
My Mi A2 Lite just died today. I was on stock 8.1 rooted and suddenly it freezes so I rebooted it and I got stuck on Android One logo WITHOUT ANY animation.
I tried to boot into recovery via adb but I get stuck on TWRP logo. I tried to flash fastboot image but nothing changes....
I really need help because I'm out of options
Click to expand...
Click to collapse
pocchio said:
1) yes, it got stuck so I rebooted it
2) I tried flashing with MiFlash tool in fastboot mode. When I connect it in fastboot edl the mi flash tool sees it as COM and therefore I’m not able to flash it.
I’m I doing something wrong?
Click to expand...
Click to collapse
I think you are confusing some things here; adb is not an option now so you can´t boot device normally and also you said "fastboot edl" but they are different modes.
While in fastboot how did you try booting to TWRP image? (you said through adb but this is not right)
Can you get to fastboot? (hold vol down while booting, should see a rabbit on the screen)
pocchio said:
1) yes, it got stuck so I rebooted it
2) I tried flashing with MiFlash tool in fastboot mode. When I connect it in fastboot edl the mi flash tool sees it as COM and therefore I’m not able to flash it.
I’m I doing something wrong?
Click to expand...
Click to collapse
When your phone is in EDL mode(you won't be seeing any logo on your phone ,only black screen) it's absolutely normal to see the device as COM port , because the device is in another factory mode. And there is no problem flashing stock ,when your phone is seen as COM port. So if you can't flash the stock firmware in fastboot mode or EDL mode , maybe you have a hardware issue. To be sure -take a screenshot of the error in MiFalsh when the phone is in edl Mode (seen as a COM port) and you try to flash the stock firmware.
Ok, I understand the difference between EDL (black screen) and Fastboot mode. I can get in both mode. I tried to flash fastboot stock rom (taken from the thread in xda) and everything goes smoothly, but it stays in fastboot mode at the end and when I send the command fastboot reboot it gets stuck again on the Android One logo (no animation).
When I tried the EDL mode, mi flash returns something missing (I will post the screenshot asap) and it seems like is not the right thing I'm trying to flash or something similar (I will post more information as soon as I can). (I'm trying to flash the same fastboot roms found in xda)
So, just to make sure I'm doing the right thing, where I can find the stock firmware to flash?
Thanks again for your help!
pocchio said:
Ok, I understand the difference between EDL (black screen) and Fastboot mode. I can get in both mode. I tried to flash fastboot stock rom (taken from the thread in xda) and everything goes smoothly, but it stays in fastboot mode at the end and when I send the command fastboot reboot it gets stuck again on the Android One logo (no animation).
When I tried the EDL mode, mi flash returns something missing (I will post the screenshot asap) and it seems like is not the right thing I'm trying to flash or something similar (I will post more information as soon as I can). (I'm trying to flash the same fastboot roms found in xda)
So, just to make sure I'm doing the right thing, where I can find the stock firmware to flash?
Thanks again for your help!
Click to expand...
Click to collapse
Here is the stock firmware from Xiaomi site:
https://en.miui.com/getrom-354.html?m=yes&mobile=2
Don't worry that it says MIUI , the firmware is Android One , they just forgot to change the name from MIUI to Android One , I have already tried it ,and I can confirm that it's 100% stock Android One firmware , good luck!
Ok I performed the flash but the error i get is new.
I get the error ACK count don't match!
I tried the version
daisy_global_images_V10.0.9.0.PDLMIXM_20190514.0000.00_9.0_f9d0c739e0.tgz
pocchio said:
Ok I performed the flash but the error i get is new.
I get the error ACK count don't match!
I tried the version
daisy_global_images_V10.0.9.0.PDLMIXM_20190514.0000.00_9.0_f9d0c739e0.tgz
Click to expand...
Click to collapse
I will give a solution in a minute
EDIT: Are you sure your bootloader is unlocked? (fastboot oem unlock)
You have two choices , you need to find an older version of MiFlash beta , i'll give you a video :
https://m.youtube.com/watch?v=-7O1Svib14g
In the video description you can find a link for the MiFlash beta ,I hope it helps.
If not , you'll have to consider the Testpoint unbrick method , there are several guides.
OK, thanks to the use of the BETA version I was able to flash the rom but unfortunately I still get the same AndroidOne logo without any animation....
I really don't know what to do now...
Yes the bootloader is unlocked and I checked with fastboot getvar
pocchio said:
OK, thanks to the use of the BETA version I was able to flash the rom but unfortunately I still get the same AndroidOne logo without any animation....
I really don't know what to do now...
Yes the bootloader is unlocked and I checked with fastboot getvar
Click to expand...
Click to collapse
Ok , it totally sound like some kind of hardware issue with the storage . Is there any way to boot in TWRP ?
Download the TWRP version 3.3.3-1 offain and try to boot with it (fastboot boot recovery(the name of the recovery).IMG) and wait until the TWRP logo disappear. Wait at least 1 minute if the logo doesn't disappear , then in my opinion , you have a hardware problem , if you succeed to booting in TWRP download the GM 1.1 version from this thread :
https://forum.xda-developers.com/mi-a2-lite/development/9-miui-rom-t3960704
and flash it via TWRP. Then reboot and leave the phone without touching at least 10 minutes (until you see some movement like on the bottom of the screen , there will be a MI logo , right above the logo if you see 3 dots moving , then you're saved . From there we can proceed , but if you can't flash even this rom , if nothing helps. I hope you have a warranty , reflash the stock rom with the option flash_all_lock and go to your warranty service center.
EDIT: I googled and found another issue, that might be causing this strange situation: You may got scammed , and the device might not be a Mi A2 Lite , but rebranded Redmi 6X. See this thread:
http://en.miui.com/thread-5984082-1-1.html
If your phone is displayed "Wayne" ,not "Daisy" ,then you'll have to flash a Redmi 6X firmware to get rid of the bootloop
nikoman1987 said:
Ok , it totally sound like some kind of hardware issue with the storage . Is there any way to boot in TWRP ?
Download the TWRP version 3.3.3-1 offain and try to boot with it (fastboot boot recovery(the name of the recovery).IMG) and wait until the TWRP logo disappear. Wait at least 1 minute if the logo doesn't disappear , then in my opinion , you have a hardware problem , if you succeed to booting in TWRP download the GM 1.1 version from this thread :
https://forum.xda-developers.com/mi-a2-lite/development/9-miui-rom-t3960704
and flash it via TWRP. Then reboot and leave the phone without touching at least 10 minutes (until you see some movement like on the bottom of the screen , there will be a MI logo , right above the logo if you see 3 dots moving , then you're saved . From there we can proceed , but if you can't flash even this rom , if nothing helps. I hope you have a warranty , reflash the stock rom with the option flash_all_lock and go to your warranty service center.
EDIT: I googled and found another issue, that might be causing this strange situation: You may got scammed , and the device might not be a Mi A2 Lite , but rebranded Redmi 6X. See this thread:
http://en.miui.com/thread-5984082-1-1.html
If your phone is displayed "Wayne" ,not "Daisy" ,then you'll have to flash a Redmi 6X firmware to get rid of the bootloop
Click to expand...
Click to collapse
I will now try your solution, I just tried the testpoint unbrick method but still same problem.
The output from fastboot getvar all shows a DAISY bootloader. Where I can see the real name of the device to see if it is a Mi 6X?
pocchio said:
I will now try your solution, I just tried the testpoint unbrick method but still same problem.
The output from fastboot getvar all shows a DAISY bootloader. Where I can see the real name of the device to see if it is a Mi 6X?
Click to expand...
Click to collapse
the command is: fastboot oem get-product-model
nikoman1987 said:
the command is: fastboot oem get-product-model
Click to expand...
Click to collapse
Unfortunately I get unknown command.
Additionally when I try to boot the TWRP I get stuck at logo forever....
pocchio said:
Unfortunately I get unknown command.
Additionally when I try to boot the TWRP I get stuck at logo forever....
Click to expand...
Click to collapse
tried the command too, it doesn't work.
So test point doesn't work too.. That's bad news
EDIT: fastboot getvar product command works , you can try it
And another question , have you tried to boot with patched boot.IMG ?
It seems indeed some hardware problem... Is there any way I can try to boot something from the SD card? (In order to rule out the storage problem....
pocchio said:
It seems indeed some hardware problem... Is there any way I can try to boot something from the SD card? (In order to rule out the storage problem....
Click to expand...
Click to collapse
You need a recovery to flash , which has a specific partition in the phone storage. You can flash only via fastboot . You need to boot into recovery , so try with a patched boot image for your version of the rom
---------- Post added at 02:47 PM ---------- Previous post was at 02:38 PM ----------
pocchio said:
It seems indeed some hardware problem... Is there any way I can try to boot something from the SD card? (In order to rule out the storage problem....
Click to expand...
Click to collapse
So the last resort , we'll try to flash the ROM that I have mentioned before via fastboot. Place the zip file GM 1.1 in your PC (it has to be in the same directory as your adb and fastboot tools)
then open cmd and run the command
fastboot flash (the full name of the zip).zip
and hit enter
maybe that will solve it
And if this doesn't help again... type these fastboot commands :
fastboot format userdata
fastboot format system
fastboot format cache
fastboot format vendor
fastboot format recovery
fastboot format boot
then try again to reflash the stock rom (first try in edl mode ,if this doesn't do anything ,you'll have to format everything via fastboot commands again ,and try to flash the ROM in fastboot mode)
And if this doesn't help too... Then you're free to hit that ? in the ground hahahah (just kidding)
Tried both these two last but nothig works, I always get the same problem.
I just saw your comment on patched boot, can you elaborate a little bit on this?
I'm honestly very close to throw it in the trash
pocchio said:
Tried both these two last but nothig works, I always get the same problem.
I just saw your comment on patched boot, can you elaborate a little bit on this?
I'm honestly very close to throw it in the trash
Click to expand...
Click to collapse
which version of the firmware you are flashing? 10.0.9.0 or another version , so I can send you a link and walk you through the procedure.
And when you flashed the GM 1.1 the boot screen didn't changed from Android one? (the GM 1.1 version is a MIUI stock port and has to change your boot screen to black screen with white MI logo on it) It is very important to know
One of my friends told me to try this: just open the directory of the stock firmware , navigate to flash_all.bat and run the bat file (NOT THE FLASH_ALL_LOCK!!!) and wait for the end of the process. He had a similar problem , and it worked. He explained that for any reason , the recovery was the problem , because it was flashed in the boot partition. When you use flash_all.bat The file will erase all partitions and rewrite them. MiFlash won't , so try that
I will try to be as specific as possible. (I cant post links here yet)
My brother has a Redmi Note 5 Global, the one with Snapdragon 636, i think its the whyred codename. Few weeks ago, it randomly rebooted and got stuck at mi logo, he never unlocked bootloader or messed with anything.
At first i told him to look for a service center, but since we are at Brazil, there is no official one, so he sent to three different people, none of them was able to help.
He already bought a new phone, but i want to repair this one, started yesterday my research.
First thing that i tried was Test-point, and sucessfully flashed the anti_test_note5 rom with ARB removed(if you google this, it will be the first result). But it still got stuck at mi logo, absolutely nothing changed, so i tried to flash this rom: "whyred_global_images_V10.2.2.0.OEIMIXM_20190314.0000.00_8.1_global_b097ed1b3b.tgz"
But i don't have EDL auth, so i searched online and found a "firehose" that let me flash the rom without auth.
Sucessfully flashed the new rom, but its still stuck at mi logo.
The next step i am going to try is to flash this rom, that i think is the latest one: "whyred_global_images_V10.3.1.0.PEIMIXM_20190522.0000.00_9.0_global_8201319a7e.tgz"
Anyone here can help me?
If any information is missing, just ask
Thanks in advance
Edit: Tried the latest rom and it still wont work, can i try lineage os rom?
Clean flash it, wipe everything except internal
First flash the miui 10 with pie global then flash any custom rom, use orange fox twrp only
OrewaShinobi said:
First flash the miui 10 with pie global then flash any custom rom, use orange fox twrp only
Click to expand...
Click to collapse
I already tried the miui 10 rom, it didnt worked for me, the phone is still stuck at mi logo.
Edit: The last one that i tried was the miui 11 november patch, still wont work. "V11.0.3.0.PEIMIXM"
Yahyahyahcf said:
I already tried the miui 10 rom, it didnt worked for me, the phone is still stuck at mi logo.
Edit: The last one that i tried was the miui 11 november patch, still wont work. "V11.0.3.0.PEIMIXM"
Click to expand...
Click to collapse
Update: Asked the same question on a website, and some dude told me to try to flash TWRP, Magisk and Dm-verity disabler.
Did a little research about dm-verity, and maybe its it that is messing with this phone. To verify this, i booted into fastboot to see the device status through the command line: fastboot oem device-info
Got this result:
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
OKAY [ 0.008s]
finished. total time: 0.010s
Does that means that dm-verity is what preventing me to boot?
And if that is true, how can i circumvent this?
So, here's what happened. I had my Redmi note 8 unlock it's bootloader a year back and installed a custom rom corvus os. And since I the custom rom didn't came with the MI stock camera app and with lots of bugs and issues, I decided to re-flash it's stock rom instead(the latest MIUI). So, yesterday I tried to flash the stock rom using the Mi Flash Tool, while putting my Note 8 at fastboot mode. But then when I clicked on the "flash" button, It came with an error saying
[18:14:01]:1 973598ec 5.1235443s error:Writing 'imagefv' FAILED (remote: 'Check CRC failed')
This is the message on the log file.
After that I tried to restart my phone and fix this issue but what happened after that is that my phone just totally went dead. Like, there's not even the light indicator when I try to chrage my phone, can't boot into recovery, can't turn on, can't enter fastboot or EDL mode. (I've also heard that Xiaomi also locked EDL on their devices smh).
I've been desperate ever since to fix my phone. And I've been searching, reading and analyzing solutions but only came to conclusions that I should give it to Xiaomi servicing center. But the problem is that there is currently a lockdown around our area (of where I'm from) and idk when it's be lifted.
If anyone knows any way, solution or any advice or fixes, please help me.
You can still flash EDL via patched firehose binary.