Related
Hi,
I flashed a wrong boot.img via fastboot, and done reboot.
Now the phone stuck in bootloop with no screen at all. no mi logo, just black screen (vibrate when it try to boot).
- Phone is Xiaomi Redmi 6, battery is not removable.
- Can't enter to fastboot mode (not either to TWRP recovery).
- Can't even turn the phone off (tried with pow + vol-up + vol-down, but didn't work).
- PC not recognize the phone (included miFlash and spFlashtool).
I have an unlocked bootloader if it make any different to this situation.
Please help :crying:
Thanks.
If need more details I would like to give it.
nikai said:
Hi,
I flashed a wrong boot.img via fastboot, and done reboot.
Now the phone stuck in bootloop with no screen at all. no mi logo, just black screen (vibrate when it try to boot).
- Phone is Xiaomi Redmi 6, battery is not removable.
- Can't enter to fastboot mode (not either to TWRP recovery).
- Can't even turn the phone off (tried with pow + vol-up + vol-down, but didn't work).
- PC not recognize the phone (included miFlash and spFlashtool).
I have an unlocked bootloader if it make any different to this situation.
Please help :crying:
Thanks.
If need more details I would like to give it.
Click to expand...
Click to collapse
try this. It worked for me when I had a simular issue.
set spflash tool up to flash correct boot.img. Press start.
Connect phone while holding the volume down button. Keep holding button. The phone is bootlooping, so it may eventually catch in preloader and get flashed.
mrmazak said:
try this. It worked for me when I had a simular issue.
set spflash tool up to flash correct boot.img. Press start.
Connect phone while holding the volume down button. Keep holding button. The phone is bootlooping, so it may eventually catch in preloader and get flashed.
Click to expand...
Click to collapse
Thanks, but I'm get the same error, STATUS_BROM_CMD_FAIL (0xC0060005)
same problem with me..haha :laugh:
folow these steps
the only way you flash your phone is by installing mtk (mediatek) drivers.
if you are using windows 10. Disable Driver Signature Enforcement
download MRT_V3.26
there you have MTK_driver.exe install it. than open folder MTK_CDC_Driver_for_imei right click on Android_Gadget_CDC_driver and install.
download Xiaomi_Flash_20181115.zip
and stable global fastboot rom V10.3.3.0.OCGMIXM
extract it
run mi flash and choose extracted folder, click refresh than flash.
THIS IS 100% TESTED by me.
mrmazak said:
try this. It worked for me when I had a simular issue.
set spflash tool up to flash correct boot.img. Press start.
Connect phone while holding the volume down button. Keep holding button. The phone is bootlooping, so it may eventually catch in preloader and get flashed.
Click to expand...
Click to collapse
Where can i get scatter file from?
edit: nevermind, found it, tried to flash boot.img but it never did anything
same
i have the same problem but with a redmi 6A, its stuck on a bootloop with the "the system has been destroyed" screen and unable to boot into fastboot, i alredy tried setting up sp flash and connecting the device pressing the vol+ button, but i always get the "STATUS_BROM_CMD_FAIL (0xC0060005)" error and i cant find anything about it.
https://forum.xda-developers.com/re...rick-stuck-da-mode-authorised-t4000433/page24 try this and let me know if its working for you guys also
samusamu2304 said:
Deleted
Click to expand...
Click to collapse
Pradeep1998 said:
https://forum.xda-developers.com/re...rick-stuck-da-mode-authorised-t4000433/page24 try this and let me know if its working for you guys also
Click to expand...
Click to collapse
The workaround doesn't support MT6762, which is the processor in the R6, sadly.
Immortal68 said:
The workaround doesn't support MT6762, which is the processor in the R6, sadly.
Click to expand...
Click to collapse
MT6765 supported and in Redmi 6
I Have A Problem That My Redmi Note 9 Is Struck On BootLoop It's Not Entering Recovery And Fastboot Mode Also It's Just Showing Redmi Logo Only How To Fix It Any One Help Me Plzzz....
BTS Arm said:
I Have A Problem That My Redmi Note 9 Is Struck On BootLoop It's Not Entering Recovery And Fastboot Mode Also It's Just Showing Redmi Logo Only How To Fix It Any One Help Me Plzzz....
Click to expand...
Click to collapse
Same problem here. I think I just got myself a brand new brick (Redmi k50)!
@BTS Arm, were you able to overcome this problem?
jholiveira said:
Same problem here. I think I just got myself a brand new brick (Redmi k50)!
@BTS Arm, were you able to overcome this problem?
Click to expand...
Click to collapse
Same problem, I'm trying right now with MiFlash as suggested by Tommy0412. The program detects the device and is in "flashing" from 500s to this moment. I'll let you know if it's working
Edit: Finished with "error: flash timout". I'm trying again, this time with very less hope. By the way my phone is a Redmi 9A (dandelion)
Edit 2: I fixed the problem without flashing (almost) anything. I used the Xiaomi ADB/Fastboot Tool (a simple .jar file) that allowed me to reboot in fastboot mode without doing anything strange. Then I flashed the correct recovery and everything is now back to normal. Thanks to whoever developed that java application. That saved my ass!
GiZeta said:
Same problem, I'm trying right now with MiFlash as suggested by Tommy0412. The program detects the device and is in "flashing" from 500s to this moment. I'll let you know if it's working
Edit: Finished with "error: flash timout". I'm trying again, this time with very less hope. By the way my phone is a Redmi 9A (dandelion)
Edit 2: I fixed the problem without flashing (almost) anything. I used the Xiaomi ADB/Fastboot Tool (a simple .jar file) that allowed me to reboot in fastboot mode without doing anything strange. Then I flashed the correct recovery and everything is now back to normal. Thanks to whoever developed that java application. That saved my ass!
Click to expand...
Click to collapse
Unfortunately, I no longer have access to recovery or fastboot. The phone is stuck in a loop and no longer offers those options. I need a tool that can recover it in BROM mode.
jholiveira said:
Unfortunately, I no longer have access to recovery or fastboot. The phone is stuck in a loop and no longer offers those options. I need a tool that can recover it in BROM mode.
Click to expand...
Click to collapse
If it keeps restarting, this may not help at all, but I'll leave the tool here for you (or whomever may need it) to maybe give it a try.
Hope you can recover it somehow, good luck and have a nice day
Yuhuu!
Try this up guys:
Fix HardBrick Redmi 6A (no recovery and no fastboot, only black screen)Fix without need Authotization stuff
----------------------------------------------------------------------- Finally I could fix my redmi 6A after suffering hardbrick. I couldnot enter to recovery neither to fastboot mode. My redmi 6A just give me a black screen with vibration on...
forum.xda-developers.com
hi Guys
I'm in the forum for a very long time as an assistant helper now it has got me hard I have an Axon 10 Pro with curly boot loader and trying to flash a TWRP I have somehow the device or SotA and SlotB have shrunk. The Axon Bootet permanently in 0.5 second cycle and also a FULL Restot or FULL Flash with EDL Tool has not changed anything. Likewise, a new flash about fastboot with the command (fastboot flash boot_a boot.img) the same for boot_b then try with fastboot command (fastboot boot twrp.img) Recovery to start without success fastboot erase boot_a and boot_b has also flashing new but it does not start. Always bootloop:crying::crying::crying::crying:
the Axon 10 pro is back because he had no backup of all we had from my Axon 10 pro made a backup with the edl tool (Backup all) and have then copied his efs backup purely and then this with then on the Axon 10 flashed the Axon 10 pro is now back
Where did you get the twrp from?
From udev
On his donload page
https://forum.xda-developers.com/showpost.php?p=80156866&postcount=3
I had a bootloop issue as well and even though I reflashed using the EDL tool, it doesn't erase and the errors remained, but when I entered EDL mode and reflashed using the Xiaomi Flash Tool, storage was completely erased and the device was flashed cleanly and booted correctly.
I've encountered a similar issue with my Axon (2020U version). I can boot into EDL but nothing else (no fastboot, recovery, etc.). I previously had TWRP up and running successfully, not sure what happened.
Is there a full EDL zip or similar that I can flash to return everything to stock? I tried restoring with the EDL tool but with no success
jbeaulieu said:
I've encountered a similar issue with my Axon (2020U version). I can boot into EDL but nothing else (no fastboot, recovery, etc.). I previously had TWRP up and running successfully, not sure what happened.
Is there a full EDL zip or similar that I can flash to return everything to stock? I tried restoring with the EDL tool but with no success
Click to expand...
Click to collapse
The reason the EDL tool may not work is that is doesn't have the capability to erase. The boot loop that occurs is usually due a corrupt bootfile. Use the MiFlash fastboot recovery tool. Make sure to select the clean all button at the bottom. Place your phone in EDL mode. Hit refresh to make sure your phone is detected. Select the EDL file and then hit flash.
jim262 said:
The reason the EDL tool may not work is that is doesn't have the capability to erase. The boot loop that occurs is usually due a corrupt bootfile. Use the MiFlash fastboot recovery tool. Make sure to select the clean all button at the bottom. Place your phone in EDL mode. Hit refresh to make sure your phone is detected. Select the EDL file and then hit flash.
Click to expand...
Click to collapse
Apologies for my ignorance - what exactly am I flashing? I see the "clean all" radio button, but I'm not sure what EDL package to flash after selecting that option - is there a 2020U package floating around that I'm not seeing?
jbeaulieu said:
Apologies for my ignorance - what exactly am I flashing? I see the "clean all" radio button, but I'm not sure what EDL package to flash after selecting that option - is there a 2020U package floating around that I'm not seeing?
Click to expand...
Click to collapse
The EDL package, use the same EDL package that you used with the EDL tool. Just select the "clean all" radio button. Select the path to the EDL , hit refresh once phone, in EDL mode, is detected, hit flash.
jim262 said:
The EDL package, use the same EDL package that you used with the EDL tool. Just select the "clean all" radio button. Select the path to the EDL , hit refresh once phone, in EDL mode, is detected, hit flash.
Click to expand...
Click to collapse
Okay, I'm trying to use MiFlash to restore the backup I took through the original EDL tool. The MiFLash tool is only timing out with a "cannot receive hello packet" - was this something you encountered as well?
jbeaulieu said:
Okay, I'm trying to use MiFlash to restore the backup I took through the original EDL tool. The MiFLash tool is only timing out with a "cannot receive hello packet" - was this something you encountered as well?
Click to expand...
Click to collapse
I did attempt to flash the wrong EDL file (They are region and device specific) and received that error. I have the Chinese version and once I downloaded the correct EDL file, I had no issues I have even maintained an unlocked boot loader, flashed Magisk and taken OTAs.
jim262 said:
I did attempt to flash the wrong EDL file (They are region and device specific) and received that error. I have the Chinese version and once I downloaded the correct EDL file, I had no issues I have even maintained an unlocked boot loader, flashed Magisk and taken OTAs.
Click to expand...
Click to collapse
Ah, okay. I have the US version - A2020U. Unless I'm mistaken, it looks like there isn't a full EDL zip file available for my version yet, so I might be stuck
There were EDL files up, but apparently they were taken down for some reason.
in the russians there are the 1.6 of the g model as edl (which one can use in a brick) but I do not know if this is synonymous with the u model as you would have to ask @Unjustified Dev or something
@MOD
I hope that the links are allowed here else delete please
1.6 g model edl
http://4pda.ru/forum/index.php?showtopic=965431&st=0#entry88768840
And the lonk too the forum
http://4pda.ru/forum/index.php?showtopic=965431
Chris axon 7 said:
in the russians there are the 1.6 of the g model as edl (which one can use in a brick) but I do not know if this is synonymous with the u model as you would have to ask @Unjustified Dev or something
@MOD
I hope that the links are allowed here else delete please
1.6 g model edl
http://4pda.ru/forum/index.php?showtopic=965431&st=0#entry88768840
And the lonk too the forum
http://4pda.ru/forum/index.php?showtopic=965431
Click to expand...
Click to collapse
Thanks for sharing these. @Unjustified Dev do you happen to know if the 1.6 2020G EDL would be able to be flashed to a 2020U model to recover from a brick? Or if not, is there a place to obtain the proper files, either here on the forums or via PM?
jim262 said:
I did attempt to flash the wrong EDL file (They are region and device specific) and received that error. I have the Chinese version and once I downloaded the correct EDL file, I had no issues I have even maintained an unlocked boot loader, flashed Magisk and taken OTAs.
Click to expand...
Click to collapse
Please share us the EDL file for the Chinese version.
has anyone found the US EDL file yet?
Futility's Forgotten Soldier said:
has anyone found the US EDL file yet?
Click to expand...
Click to collapse
Still waiting. I'm stuck on the EU version.
I tried to search regarding this issue but couldn't find a solution so I am posting this issue in hopes that someone can guide me to a solution.
I wanted to install pixel experience on my Redmi Note 7 Pro. My phone was successfully unlocked by myself and no issues were faced. First I tried to install Peter's TWRP but then can't go the recovery instead every time I was booted to fastboot menu. I then tried to just restart by holding the power button to boot straight to OS but instead I was again back to the fastboot menu.
I then downloaded the latest global ROM "violet_in_global_images_V11.0.5.0.PFHINXM_20191022.0000.00_9.0_in_9bff00d97f" for flashing using xiaomi flash tool and faced many errors but resolving one by one and then finally ROM was flashed but it only took 1 sec to complete and nothing happened on the phone. Then I searched around a bit more and tried to use CMD to flash "flash_all.bat" directly and got the error "Current Device Anti Rollback is greater than this Pkg". What I don't understand is that if I am using the latest global firmware then how the current device has a higher arb no. ?
I hope that I am able to explain the situation for other's to understand.
Any help will be appreciated.
TSKXDA said:
I tried to search regarding this issue but couldn't find a solution so I am posting this issue in hopes that someone can guide me to a solution.
I wanted to install pixel experience on my Redmi Note 7 Pro. My phone was successfully unlocked by myself and no issues were faced. First I tried to install Peter's TWRP but then can't go the recovery instead every time I was booted to fastboot menu. I then tried to just restart by holding the power button to boot straight to OS but instead I was again back to the fastboot menu.
I then downloaded the latest global ROM "violet_in_global_images_V11.0.5.0.PFHINXM_20191022.0000.00_9.0_in_9bff00d97f" for flashing using xiaomi flash tool and faced many errors but resolving one by one and then finally ROM was flashed but it only took 1 sec to complete and nothing happened on the phone. Then I searched around a bit more and tried to use CMD to flash "flash_all.bat" directly and got the error "Current Device Anti Rollback is greater than this Pkg". What I don't understand is that if I am using the latest global firmware then how the current device has a higher arb no. ?
I hope that I am able to explain the situation for other's to understand.
Any help will be appreciated.
Click to expand...
Click to collapse
Try the command "fastboot oem edl" in cmd of adb folder when device is in fastboot mode. Ur phone should go black but dont panic. Now open miflash tool and u see ur device is connected in edl mode as COMX ( X may be anything 10 or 20 like that). Now try to flash the lattest fastboot rom for over device. Remember to check the option in mi flash tool to not lock bl again. But this will wipe all your data.
Sent from my Redmi Note 7 Pro using XDA Labs
hackermssharma said:
Try the command "fastboot oem edl" in cmd of adb folder when device is in fastboot mode. Ur phone should go black but dont panic. Now open miflash tool and u see ur device is connected in edl mode as COMX ( X may be anything 10 or 20 like that). Now try to flash the lattest fastboot rom for over device. Remember to check the option in mi flash tool to not lock bl again. But this will wipe all your data.
Sent from my Redmi Note 7 Pro using XDA Labs
Click to expand...
Click to collapse
Thank you for taking time to reply to my query. I did what you suggested and got into EDL mode. Xiaomi Mi Flash picked up the device as COM10 but when I tried to flash it shows "sahara read end error with status:40" and nothing happens.
Any further idea?
TSKXDA said:
I tried to search regarding this issue but couldn't find a solution so I am posting this issue in hopes that someone can guide me to a solution.
I wanted to install pixel experience on my Redmi Note 7 Pro. My phone was successfully unlocked by myself and no issues were faced. First I tried to install Peter's TWRP but then can't go the recovery instead every time I was booted to fastboot menu. I then tried to just restart by holding the power button to boot straight to OS but instead I was again back to the fastboot menu.
I then downloaded the latest global ROM "violet_in_global_images_V11.0.5.0.PFHINXM_20191022.0000.00_9.0_in_9bff00d97f" for flashing using xiaomi flash tool and faced many errors but resolving one by one and then finally ROM was flashed but it only took 1 sec to complete and nothing happened on the phone. Then I searched around a bit more and tried to use CMD to flash "flash_all.bat" directly and got the error "Current Device Anti Rollback is greater than this Pkg". What I don't understand is that if I am using the latest global firmware then how the current device has a higher arb no. ?
I hope that I am able to explain the situation for other's to understand.
Any help will be appreciated.
Click to expand...
Click to collapse
I suggest you use the older variant of the MiFlash tool.
How did you flash Peter's? Did you use "fastboot flash recovery recovery.img"? That's the only right command.
Also are you sure you have the Indian variant of the phone? Another way to bypass anti roll back would be to clear all partitions, and then flash the required ROM.
Sorry if I'm not able to help you, I'll try having a look later on.
Thank you for your support. I had to go to the service center as no solution could be found.
Wait i know what happen... Ur phone has twrp and rom successfully installed don't worry about that. Just problem is ur phone has again locked the bootloader thats why its not able to boot os because it has twrp not the official recovery. U can verify that u have bootloader locked.. when ur phone starts when there is mi logo there will not be "unlocked" written in bottom.. see... That is very easy. Just try to unlock bootloader again with mi unlock tool.
And ur good to go. I got same errors on my friends redmi 6 pro. Service center will tell u to change motherboard as it cant be fixed with edl mode. JUST TRY TO UNLOCK AGAIN WITH MI UNLOCK TOOL.
dnyaneshmoh said:
Wait i know what happen... Ur phone has twrp and rom successfully installed don't worry about that. Just problem is ur phone has again locked the bootloader thats why its not able to boot os because it has twrp not the official recovery. U can verify that u have bootloader locked.. when ur phone starts when there is mi logo there will not be "unlocked" written in bottom.. see... That is very easy. Just try to unlock bootloader again with mi unlock tool.
And ur good to go. I got same errors on my friends redmi 6 pro. Service center will tell u to change motherboard as it cant be fixed with edl mode. JUST TRY TO UNLOCK AGAIN WITH MI UNLOCK TOOL.
Click to expand...
Click to collapse
Thank you for your feedback but the phone bootloader remained unlocked as when the phone starts there is "unlocked" written in bottom.
I got the phone back from Service Center. It's working fine but strangely still the bootloader is shown as unlocked in the start animation.
Hi,
My phone is actually dying and I don't know how to recover it this time.
I had a perfectly working setup with latest weekly update of Xiaomi eu MIUI , TWRP and magisk, and know even fastboot is not responding.
I usually don't like when people say that, but I think a malware did it, as my apps started not responding in a few minutes, and the reboot finished the job.
Now it won't boot anymore, when it's plug the notification led is red, and fastboot is detected but commands are stuck.
Also, TWRP is neither accessible from "power + vol up" since last miui eu update, nor from fastboot since the "accident"
If someone have any advice on how to unlock fastboot, flash back the rom or any other way to recover my phone, please help
Also, if you want to know the rest of the story, it's here...
I was using my phone as usual, trying to setup a bridge openvpn connection. (like everyone :laugh: )
The issue is that the only app claiming to do that isn't free, and I want to be sure I can make it work before spending any money.
So I tried to patch it and different apks (I know it's bad...), and while transferring an apk from my laptop to my phone, I noticed the transfer was kinda slow for a few seconds (nothing worrying, but unusual)
Then some of my apps didn't want to launch and, back to the app drawer, most of my apps had their package names, with no icons...
It was at this moment Jackson I knew I screwed up...
I then tried rebooting, and the phone stayed a few minutes on the MIUI screen, then shut off.
After a reboot, I noticed the red led, the absence of boot animation, and the bootloop.
Obviously, if I had a fastboot access, it would be easy to boot on TWRP and then flash back my rom properly but I can't...
EDIT: to make this clearer (I know the post above is a little bit messy), I have the following issues:
- No access to TWRP (for flashing)
- Fastboot is accessible but broken enough so flash/boot to twrp is not possible
- I just though of EDL mode, but "fastboot oem edl" doesn't seems to work
- I prefer to avoid opening my phone (to access to the EDL test points)
EDIT2: You can't flash anything in EDL mode without specific autorisations from xiaomi, so this mode becomes way more useless than on my previous Mi A1. I managed to miraculously flash some things by using miflash in fastboot mode. Maybe working on a windows os instead of gnu/linux helped somehow...
Thelm76 said:
Hi,
My phone is actually dying and I don't know how to recover it this time.
I had a perfectly working setup with latest weekly update of Xiaomi eu MIUI , TWRP and magisk, and know even fastboot is not responding.
I usually don't like when people say that, but I think a malware did it, as my apps started not responding in a few minutes, and the reboot finished the job.
Now it won't boot anymore, when it's plug the notification led is red, and fastboot is detected but commands are stuck.
Also, TWRP is neither accessible from "power + vol up" since last miui eu update, nor from fastboot since the "accident"
If someone have any advice on how to unlock fastboot, flash back the rom or any other way to recover my phone, please help
Also, if you want to know the rest of the story, it's here...
I was using my phone as usual, trying to setup a bridge openvpn connection. (like everyone :laugh: )
The issue is that the only app claiming to do that isn't free, and I want to be sure I can make it work before spending any money.
So I tried to patch it and different apks (I know it's bad...), and while transferring an apk from my laptop to my phone, I noticed the transfer was kinda slow for a few seconds (nothing worrying, but unusual)
Then some of my apps didn't want to launch and, back to the app drawer, most of my apps had their package names, with no icons...
It was at this moment Jackson I knew I screwed up...
I then tried rebooting, and the phone stayed a few minutes on the MIUI screen, then shut off.
After a reboot, I noticed the red led, the absence of boot animation, and the bootloop.
Obviously, if I had a fastboot access, it would be easy to boot on TWRP and then flash back my rom properly but I can't...
Click to expand...
Click to collapse
Hi
I had a similar situation
I comfigured an app and during configuration the phone start framing
I rebooted and stucked at miui screen
I tried to reboot in recovery ,nothing
I downloaded latest miui for europe 12.0.3 and mi flash
For me fastboot worked to flash latest firmware from xiaomi
And now is working and my bootloader is locked
Thelm76 said:
Hi,
My phone is actually dying and I don't know how to recover it this time.
[/hide]
Click to expand...
Click to collapse
Xiaomi.eu has TWRP issue...
Go to https://www.androidfilehost.com/?w=files&flid=50678 and find your recovery (lmi) and flash it with fastboot and boot to recovery.
fastboot flash recovery twrp.img
fastboot boot twrp.img
Now download the new ROM 20.10.16, push it to the internet storage and install it dirty... Wipe Cache and reboot....
My problem is almost same, i unlock the bootloader to flash xiaomi.eu rom from global rom, unlocking and flashing custom recovery was done smoothly, when i tried to flash xiaomi.eu rom version 12.0.8 it booted back to recovery, and i format the data partition and booted to system, and same result. I tried global its same result.
Then i tried miflash tool, " antirollback error ".
Now i don't know what to do. Hope my precious poco f2 pro is not bricked, coz i can still manage to boot in custom recovery, and can use miflash tool but error.
Can someone out there help me please. Thanks in advance.
Eldybug said:
My problem is almost same, i unlock the bootloader to flash xiaomi.eu rom from global rom, unlocking and flashing custom recovery was done smoothly, when i tried to flash xiaomi.eu rom version 12.0.8 it booted back to recovery, and i format the data partition and booted to system, and same result. I tried global its same result.
Then i tried miflash tool, " antirollback error ".
Now i don't know what to do. Hope my precious poco f2 pro is not bricked, coz i can still manage to boot in custom recovery, and can use miflash tool but error.
Can someone out there help me please. Thanks in advance.
Click to expand...
Click to collapse
Since you have access to a properly working fastboot and recovery, I believe there is always a way to recover your phone.
I'll be glad to help you but for now, I'm more focused on my issue.
Only thing, while using miflash, be careful to never lock your bootloader since you would have to open your phone to access EDL mode in case of bootloop
(but you can lock it afterwards if you want)
Enricosteph said:
Xiaomi.eu has TWRP issue...
Go to https://www.androidfilehost.com/?w=files&flid=50678 and find your recovery (lmi) and flash it with fastboot and boot to recovery.
fastboot flash recovery twrp.img
fastboot boot twrp.img
Now download the new ROM 20.10.16, push it to the internet storage and install it dirty... Wipe Cache and reboot....
Click to expand...
Click to collapse
Well, the main issue here is that fastboot seems to be broken too...
i found this for you on the LOS rom for poco f2 pro (am not the autor) this is for the "Anti-rollback error" (i hope that can help you):
romabah said:
Gentlemen with EU versions of Poco F2 pro, could you help me out?
Right now i am running 12.0.2.0 QJKEUXM.
To flash Lineage i first need to flash MIUI V12.0.3.0.QJKMIXM via MiFlash. I tried to do that but got an Anti-rollback error.
Checking via fastboot i saw that my phones anti rollback value is 1, but MIUI V12.0.3.0.QJKMIXM firmware has an anti rollback of 0.
Some folks say to delete first 5-6 lines in text editor from .bat file, but at the same time people tell everywhere to NOT flash firmware with lower value that your current anti rollback.
Any advice? How did other EU folks fix this?
Edit: I fixed it! I will NOT and cannot claim that this will fix all rollback error's, but it fixed mine.
0) This is applicable to fastboot version of MIUI V12.0.3.0.QJKMIXM (aka tgz file that you need to extract twice)
1) Move the extracted firmware directory imi_global_images_V12.0.3.......ets.ets. ( map with flash_all.bat, images ) to C: directory and rename to something short, like xiaomiFirm.
This will solve a lot of weird error's as MiFlash doesnt like long directories
2) Within the moved map open flash_all.bat with text editor and delete everything starting and including "::check anti_version" to and including "echo %..."
This removes the anti rollback check somehow. The reason for only editing flash_all.bat is because this is the .bat file that is run when you choose clean all option in MiFlash, i assume you dont want to clean all and lock now do you?
3) After finishing flashing mine gave error Not catch checkpoint flash is not done, but booted normally. Gave me a heart attack.
Sanity check: When running cmd "fastboot getvar anti" it returned "anti: 1"
Meaning i just flashed a ROM with anti of 0 on a phone with a anti value of 1. At least i believe so.
In any case, thank all for giving feedback for other ways of fixing this.
Click to expand...
Click to collapse
I'll try to make a type C deep flash cable to flash fastboot, and edit this message to explain if this works
Thelm76 said:
Well, the main issue here is that fastboot seems to be broken too...
Click to expand...
Click to collapse
Try to hold down only Vol Down and connect it to your computer
Enricosteph said:
Try to hold down only Vol Down and connect it to your computer
Click to expand...
Click to collapse
I don't know if this was my cable or fastboot oem edl, but windows recognised the phone as qualcomm qdloader 9008. I'll now try to update fastboot, install twrp and check the extent of the damages.
Fangstergangsta said:
i found this for you on the LOS rom for poco f2 pro (am not the autor) this is for the "Anti-rollback error" (i hope that can help you):
Click to expand...
Click to collapse
Indeed, OP, try to flash everything from the start thep by step.
You must stop therapeutic relentlessness!!!
Just plug out the charger and let him die softly...
Put him back in his sweet box after his last breathe
Bury him in your garden with a decent burial : he deserve it!!!!
It's HIS TIME, dude....
Regards
Mastakony said:
You must stop therapeutic relentlessness!!!
Just plug out the charger and let him die softly...
Put him back in his sweet box after his last breathe
Bury him in your garden with a decent burial : he deserve it!!!!
It's HIS TIME, dude....
Regards
Click to expand...
Click to collapse
Haha it's not therapeutic relentlessness when you're sure it will live again in a few days (and fully working!)
It just need a good memory wipe and android replacement
As I managed to get to emergency mode, I can now easily replace its software
EDIT: I didn't know that for these xiaomi devices, you need very specific autorisations to flash something with EDL... Fortunately, after messing around with miflash, I managed to unlock myself out of this infinite loop
As I managed to get to emergency mode, I can now easily replace its software
Click to expand...
Click to collapse
How are you going to flash the software?
Well,
By using edl mode and miflash, I got some errors as I was not authorised to do this operation, so I rebooted to fastboot, reused miflash, and I don't know which kind of magic did that but after some files flashed and an error, I was able to boot on TWRP. With this done, I tried to keep my data but didn't worked, and as I have everything constantly backup, I dicided to do a flashall.
now, I think I have a good MIUI base to flash MIUI EU back
Thelm76 said:
Well,
By using edl mode and miflash, I got some errors as I was not authorised to do this operation, so I rebooted to fastboot, reused miflash, and I don't know which kind of magic did that but after some files flashed and an error, I was able to boot on TWRP. With this done, I tried to keep my data but didn't worked, and as I have everything constantly backup, I dicided to do a flashall.
now, I think I have a good MIUI base to flash MIUI EU back
Click to expand...
Click to collapse
I have the same situation plus no fastboot or recovery at all.. Please tell me how did you resolve it?
ghannaiem said:
I have the same situation plus no fastboot or recovery at all.. Please tell me how did you resolve it?
Click to expand...
Click to collapse
Is the phone detected by the pc in usb?
And when you press power+ sound + or - What is happening?
NOSS8 said:
Is the phone detected by the pc in usb?
And when you press power+ sound + or - What is happening?
Click to expand...
Click to collapse
Yes , detected by usb but as qcom 9008,
And when holding down power button with + or - vol it restarts again to 9008 .
So it is not detected by any means, but only detected in edl mode
ghannaiem said:
Yes , detected by usb but as qcom 9008,
And when holding down power button with + or - vol it restarts again to 9008 .
So it is not detected by any means, but only detected in edl mode
Click to expand...
Click to collapse
how did it happen?
My imei got lost so I tried to flash eng rom through MI flash to fix it. It flashes all except certain file called (aop. Mbn) so I tried to flash it by cmd commands via fastboot and then the phone bricked.. No booting to fastboot anymore , no recovery. even with disconnecting battery and reconnecting again... Phone only recognized in Edl mode and when flashing through MI flash it asks for edl authorization... Account login successful but then flash fail cuz account is not authorized. So I think The only solution will be authorized account or patched prog_ufs file
Original Stock PRELOADER_MERLIN.BIN for MERLIN
Works with:
- Xiaomi Redmi 10X 4G
- Xiaomi Redmi Note 9
Firmware Versions:
- (Engineering) AL2522-Merlin-V039-Q-0513
- (Engineering) AL2522-Merlin-V044-Q-0920
- V12.5.1.0.RJOMIXM (FLASHING EDL only.)
- V12.0.1.0.RJOMIXM (FLASHING EDL only.)
- V12.0.8.0.QJOMIXM (FLASHING EDL only.)
- V12.0.7.0.QJOMIXM (FLASHING EDL only.)
- V12.0.6.0.QJOMIXM (FLASHING EDL only.)
- V12.0.5.0.QJOMIXM (FLASHING EDL only.)
- V12.0.4.0.QJOMIXM
- (China) V12.0.4.0.QJOCNXM
- V12.0.3.0.QJOMIXM
- V11.0.5.0.QJOMIXM
- V11.0.4.0.QJOMIXM
- V11.0.2.0.QJOMIXM
How to flash it?
Code:
fastboot flash preloader preloader_merlin.bin
MD5 hashes:
AL2522-Merlin-V039-Q-0513: bc7ebc0c2ca06b0d99856d595949e215
AL2522-Merlin-V044-Q-0920: d2c78e614adf75b98b2b6de74dfb4675
V12.5.1.0.RJOMIXM: 5db0756e0c2c0af508e5a823f204a6f1
V12.0.1.0.RJOMIXM: 1871c0dc6d8de2060175f8c90b133012
V12.0.8.0.QJOMIXM: d9a5ed36161265b61176178bebed8281
V12.0.7.0.QJOMIXM: 2124bb907077b745b8ada8d7108802f9
V12.0.6.0.QJOMIXM: 8c5d38f293d1609da6f79aa7d43b5c0b
V12.0.5.0.QJOMIXM: 27349a358cfd49f73ed3d31d423ca7fd
V12.0.4.0.QJOMIXM: 61ec78ae4a096c0b9f46cf814e5988c3
(China) V12.0.4.0.QJOCNXM: d06b365a15bc622327772586d3c54b18
V12.0.3.0.QJOMIXM: 9a14afee8301b12848ff8ec56c5aebbf
V11.0.5.0.QJOMIXM: 6fb0758e03bf1e43794f5a5273b627b8
V11.0.4.0.QJOMIXM: ea0e773af461a339b76907f94eff73c9
V11.0.2.0.QJOMIXM: d7d5c5b53817b4cc62accfe0eb0cabe3
Do you need help with your MERLIN device ?
Read this FAQ: https://forum.xda-developers.com/t/...for-merlin-redmi-10x-4g-redmi-note-9.4225177/
My device is on China version 12.0.8, will I get bricked if I flash preload 12.0.4 Global?
p233 said:
My device is on China version 12.0.8, will I get bricked if I flash preload 12.0.4 Global?
Click to expand...
Click to collapse
No.
It will works perfectly.
I've attached preloader of V12.0.4.0.QJOCNXM (China) too.
Enjoy
How do i flash is in EDL mode, what should i use because i am at miui 12.5 and i dont know how to make this into edl mode and flash it there
briangwapo81 said:
How do i flash is in EDL mode, what should i use because i am at miui 12.5 and i dont know how to make this into edl mode and flash it there
Click to expand...
Click to collapse
You can't. If you are at MIUI V12.0.5.0 or higher, ou need to flash in fastboot.
For EDL you need an authorized account for use EDL.
You need to go the service centre for professional assistance.
Read it: https://www.xda-developers.com/xiaomi-edl-unbrick-authorized-mi-accounts/
Do you need help with your MERLIN device ?
Read this FAQ: https://forum.xda-developers.com/t/...for-merlin-redmi-10x-4g-redmi-note-9.4225177/
VD171 said:
You can't. If you are at MIUI V12.0.5.0 or higher, ou need to flash in fastboot.
For EDL you need an authorized account for use EDL.
You need to go the service centre for professional assistance.
Read it: https://www.xda-developers.com/xiaomi-edl-unbrick-authorized-mi-accounts/
Click to expand...
Click to collapse
I made the way of VD171 and succeeded. Furthermore I can switch back to MIUI 11.0.5 Global. However, when I was in version 11.0.5, I installed TWRP, but Root didn't work.
p233 said:
I made the way of VD171 and succeeded. Furthermore I can switch back to MIUI 11.0.5 Global. However, when I was in version 11.0.5, I installed TWRP, but Root didn't work.
Click to expand...
Click to collapse
Here, you can see what is working for MERLIN: https://forum.xda-developers.com/t/...omi-redmi-10x-4g-xiaomi-redmi-note-9.4209269/
As you can see, MAGISK is working perfectly on V11.0.5.0.
Did you flash magisk using TWRP or did you flash magisk patched boot.img ?
Do you need help with your MERLIN device ?
Read this FAQ: https://forum.xda-developers.com/t/...for-merlin-redmi-10x-4g-redmi-note-9.4225177/
VD171 said:
Here, you can see what is working for MERLIN: https://forum.xda-developers.com/t/...omi-redmi-10x-4g-xiaomi-redmi-note-9.4209269/
As you can see, MAGISK is working perfectly on V11.0.5.0.
Did you flash magisk using TWRP or did you flash magisk patched boot.img ?
Click to expand...
Click to collapse
I flash magisk using TWRP.
p233 said:
I flash magisk using TWRP.
Click to expand...
Click to collapse
Try patching boot.img using magisk manager.
And then, flashing the magisk patched boot.img to boot partition.
Do you need help with your MERLIN device ?
Read this FAQ: https://forum.xda-developers.com/t/...for-merlin-redmi-10x-4g-redmi-note-9.4225177/
Good afternoon! I flashed my RN 9 with the version merlin_global_images_V12.0.1.0.RJOMIXM. Then I flashed LK from lk-V12.0.4.0.QJOMIXM. The result is this: the phone is loaded only in EDL mode. Now only carry it to the service center?
Gardlok said:
Good afternoon! I flashed my RN 9 with the version merlin_global_images_V12.0.1.0.RJOMIXM. Then I flashed LK from lk-V12.0.4.0.QJOMIXM. The result is this: the phone is loaded only in EDL mode. Now only carry it to the service center?
Click to expand...
Click to collapse
Just bypass the EDL authentication and flash the LK-V12.0.1.0.RJOMIXM.
I suggest you to flash the preloader-V12.0.4.0.QJOMIXM and then, you can flash in download mode and avoid the EDL authentication.
VD171 said:
Just bypass the EDL authentication and flash the LK-V12.0.1.0.RJOMIXM.
I suggest you to flash the preloader-V12.0.4.0.QJOMIXM and then, you can flash in download mode and avoid the EDL authentication.
Click to expand...
Click to collapse
After loading the DA, after 60 seconds (timeout), it returns an error: Error: "EXCEPTION STATUS_EXT_RAM_EXCEPTION". I am 100% sure that I did not click "format all". I have successfully bypassed authentication. I saw your post, it said that preloader_merlin-V12.0.1.0.RJOMIXM cannot load DA...
Gardlok said:
After loading the DA, after 60 seconds (timeout), it returns an error: Error: "EXCEPTION STATUS_EXT_RAM_EXCEPTION". I am 100% sure that I did not click "format all". I have successfully bypassed authentication. I saw your post, it said that preloader_merlin-V12.0.1.0.RJOMIXM cannot load DA...
Click to expand...
Click to collapse
You need to flash using the firmware upgrade mode, it will erase userdata and relock bootloader.
And then, you can restore your backup.
VD171 said:
You need to flash using the firmware upgrade mode, it will erase userdata and relock bootloader.
And then, you can restore your backup.
Click to expand...
Click to collapse
The switched-off phone is not detected by the computer in any way, only EDL mode is possible, I tried to flash in the "Firmware upgrade" mode, the error is the same...
Gardlok said:
The switched-off phone is not detected by the computer in any way, only EDL mode is possible, I tried to flash in the "Firmware upgrade" mode, the error is the same...
Click to expand...
Click to collapse
May you attach the screenshot, please?
VD171 said:
May you attach the screenshot, please?
Click to expand...
Click to collapse
Ok. In the settings, I put UART, 921600.
Gardlok said:
Ok. In the settings, I put UART, 921600.
Click to expand...
Click to collapse
The good news: your device is okay, just need some attention.
The bad news: you really need to do more tests.
Did you try another older MIUI version?
VD171 said:
The good news: your device is okay, just need some attention.
The bad news: you really need to do more tests.
Did you try another older MIUI version?
Click to expand...
Click to collapse
Yes, I tried it. I have tried many different versions of the firmware, both for Russia and for the whole world. I also tried the engineering firmware. I also tried to install various drivers, SPFT. I was booting using Live WinPE. Conclusion: there is always an error that is described above. I think the phone's memory has switched to read-only mode. My phone is under warranty, I will take it to the service... I was upset... eh...
Gardlok said:
Yes, I tried it. I have tried many different versions of the firmware, both for Russia and for the whole world. I also tried the engineering firmware. I also tried to install various drivers, SPFT. I was booting using Live WinPE. Conclusion: there is always an error that is described above. I think the phone's memory has switched to read-only mode. My phone is under warranty, I will take it to the service... I was upset... eh...
Click to expand...
Click to collapse
You just applied some change to the device, causing some brick.
SP Flash Tool is your best friend, certainly it can solve your problems.
Please help me, my phone comes with miui 12.5.X, I have unlocked the bootloader with "MediatekBootloaderUnlock" and I can use "MTK-bypas" to flash it using SP - TOOL, apparently the flashing is always successful, however the system won't boot , it only shows the android logo and I can't access the recovery menu, only fastboot. I tried with MIU 13, MIU 12.5.3 with the same results.
In the end I tried with MIU 12.0.1 (merlin_global_images_V12.0.1.0.RJOMIXM_20210520.0000.00_11.0_global):
1- Use EDL bypass and SPFLASH, it was successful, because fastboot now shows a different logo, but the system does not start and I cannot access the recovery menu either.
2- Use Mediatek Bootloader Unlock
3- Start fastboot and use: "fastboot flash preloader preloader_merlin--V12.0.1.0.RJOMIXM.bin" with apparent success.
4- I go back to SP-Flash and try to flash again MIU 12.0.1 (in theory it should no longer need EDL bypass), uncheck "preloader", I press download and connect my phone and it starts to turn itself on, if I press a key then I receive the authentication error.
If someone could give me a better guide on what to do, I would greatly appreciate it. I have tried formatting using SP-Flash and tried to flash by changing the preloader from "merlin_global_images_V12.0.1.0.RJOMIXM_20210520.0000.00_11.0_global" to "preloader_merlin--V12.0.1.0.RJOMIXM.bin", using "DA_VD171--3.3001 .2020-07-02020-07-14.bin" and "MT6768_Android_scatter--V12.0.1.0.RJOMIXM.txt" but I get the error, the screenshot is from this attempt.
Please help me