I have problem with my a2 lite. Device sesnors like accelerometar, light sensor, proximity, screen rotate sensor etc. is not working after failed flash of android 10. I flashed stock rom through xiaomi flash tool but im thinking that partition may be corupted so i need to revert it back to stock. What do you guys think? Now im running latest october update and bootloder is unlocked. Plz help.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
hrvoje007 said:
I have problem with my a2 lite. Device sesnors like accelerometar, light sensor, proximity, screen rotate sensor etc. is not working after failed flash of android 10. I flashed stock rom through xiaomi flash tool but im thinking that partition may be corupted so i need to revert it back to stock. What do you guys think? Now im running latest october update and bootloder is unlocked. Plz help.
Click to expand...
Click to collapse
You can try flashing stock firmware in edl mode (fastboot OEM edl command via cmd on PC and you phone connected in fastboot mode) with MiFlash , if this doesn't help , pm me
nikoman1987 said:
You can try flashing stock firmware in edl mode (fastboot OEM edl command via cmd on PC and you phone connected in fastboot mode) with MiFlash , if this doesn't help , pm me
Click to expand...
Click to collapse
is there any other way than edl mode? Im not familiar with that metod
hrvoje007 said:
is there any other way than edl mode? Im not familiar with that metod
Click to expand...
Click to collapse
the method is simple , when you type the comand "fastboot OEM edl " in cmd.exe , that you have to open in your fastboot folder , your phone will turn the screen of like the phone is turned off , but actually it will be in edl mode , flash the stock firmware the same way you have flashed when your phone was in fastboot mode.
If you flashed Android 10 GSI version , you can try flash this zip via TWRP recovery, then flash stock firmware via miflash
Here is the link: https://drive.google.com/file/d/10o7WXe9YB31mvZBVVJtpINYQqpx4CH8D/view?usp=drivesdk
But I strongly recommend you to flash the stock firmware in EDL , there are many YouTube tutorials , and it's very simple , good luck!
nikoman1987 said:
the method is simple , when you type the comand "fastboot OEM edl " in cmd.exe , that you have to open in your fastboot folder , your phone will turn the screen of like the phone is turned off , but actually it will be in edl mode , flash the stock firmware the same way you have flashed when your phone was in fastboot mode.
If you flashed Android 10 GSI version , you can try flash this zip via TWRP recovery, then flash stock firmware via miflash
Here is the link: https://drive.google.com/file/d/10o7WXe9YB31mvZBVVJtpINYQqpx4CH8D/view?usp=drivesdk
But I strongly recommend you to flash the stock firmware in EDL , there are many YouTube tutorials , and it's very simple , good luck!
Click to expand...
Click to collapse
ok, thanks you first i thought i need to teardown my phone to do that, do you think this will fix sensors issue, becase my internet is painfully slow, everything will reset i need do download every single app i use again
hrvoje007 said:
ok, thanks you first i thought i need to teardown my phone to do that, do you think this will fix sensors issue, becase my internet is painfully slow, everything will reset i need do download every single app i use again
Click to expand...
Click to collapse
it will do the edl flash
I did edl flash but sensors stil not working at all. I really dont know what to do next
hrvoje007 said:
I did edl flash but sensors stil not working at all. I really dont know what to do next
Click to expand...
Click to collapse
Which rom version did you have before to flash?
Which rom version do you choose?
The result in MiFlash tool was suceed?
Do you choose Clean Flash option instead of Save User Data option?
Can you upload some screenie?
SubwayChamp said:
Which rom version did you have before to flash?
Which rom version do you choose?
The result in MiFlash tool was suceed?
Do you choose Clean Flash option instead of Save User Data option?
Can you upload some screenie?
Click to expand...
Click to collapse
i explained everything in original post. I tried to flash android 10, but something went wrong and device didnt boot up, so i did return to android 9 stock with xiaomi flash tool, and everything was working except device sensors. So i did again with EDL mode but didnt help. I choosed clean flash both times with regular fastboot before, and after with edl mode
hrvoje007 said:
i explained everything in original post. I tried to flash android 10, but something went wrong and device didnt boot up, so i did return to android 9 stock with xiaomi flash tool, and everything was working except device sensors. So i did again with EDL mode but didnt help. I choosed clean flash both times with regular fastboot before, and after with edl mode
Click to expand...
Click to collapse
Giving good information will help you to other members can help you too.
In OP is only explained what did you do to get this state but not any of the questions I did make before.
Why is important which version did you have before and which version did you "try" to flash after? It´s probably that trying to downgrading the issue won´t be solved. The firmware/rom version is for example v10.0.9.0 and not simply Pie.
The screenie doesn´t reflect any action but that was detected in EDL, it´s and advance but it would be the end a success?
Anyway try these steps:
- Go to stock recovery and formatdata/factory reset.
- Then In fastboot mode delete both modem partitions with
Code:
fastboot erase modem_a
and
Code:
fastboot erase modem_b
- Finally go to EDL and flash a newer rom version.
- Reboot and if needed apply the next OTA update eg. if you flashed through EDL v10.0.13.0 then apply the v10.0.14.0 (OTA package)
SubwayChamp said:
Giving good information will help you to other members can help you too.
In OP is only explained what did you do to get this state but not any of the questions I did make before.
Why is important which version did you have before and which version did you "try" to flash after? It´s probably that trying to downgrading the issue won´t be solved. The firmware/rom version is for example v10.0.9.0 and not simply Pie.
The screenie doesn´t reflect any action but that was detected in EDL, it´s and advance but it would be the end a success?
Anyway try these steps:
- Go to stock recovery and formatdata/factory reset.
- Then In fastboot mode delete both modem partitions with
Code:
fastboot erase modem_a
and
Code:
fastboot erase modem_b
- Finally go to EDL and flash a newer rom version.
- Reboot and if needed apply the next OTA update eg. if you flashed through EDL v10.0.13.0 then apply the v10.0.14.0 (OTA package)
Click to expand...
Click to collapse
i will try that in next couple of days, and i will let you know if problem is solved thank you, i can give any information you guys ask im not very experienced in this stuff like you but i appreciate your help.
SubwayChamp said:
Giving good information will help you to other members can help you too.
In OP is only explained what did you do to get this state but not any of the questions I did make before.
Why is important which version did you have before and which version did you "try" to flash after? It´s probably that trying to downgrading the issue won´t be solved. The firmware/rom version is for example v10.0.9.0 and not simply Pie.
The screenie doesn´t reflect any action but that was detected in EDL, it´s and advance but it would be the end a success?
Anyway try these steps:
- Go to stock recovery and formatdata/factory reset.
- Then In fastboot mode delete both modem partitions with
Code:
fastboot erase modem_a
and
Code:
fastboot erase modem_b
- Finally go to EDL and flash a newer rom version.
- Reboot and if needed apply the next OTA update eg. if you flashed through EDL v10.0.13.0 then apply the v10.0.14.0 (OTA package)
Click to expand...
Click to collapse
I tried these steps but still didnt solve the issue, do you have any other sugestions?
hrvoje007 said:
I tried these steps but still didnt solve the issue, do you have any other sugestions?
Click to expand...
Click to collapse
Your issues remain as described in OP?
Did you use EDL mode (not fastboot ) to flash the whole rom?
And also did you use Clean All (not save userdata) in MiFlash tool?
And which rom did you try of Android 10 firstly that caused this damage?
SubwayChamp said:
Your issues remain as described in OP?
Did you use EDL mode (not fastboot ) to flash the whole rom?
And also did you use Clean All (not save userdata) in MiFlash tool?
And which rom did you try of Android 10 firstly that caused this damage?
Click to expand...
Click to collapse
Yes i used EDL mode to falsh rom, and yes i pressed clean all.
Firstly i installed twrp, then i tried to instal android 10 pixel experience rom, but then i was stucked in bootlop, then i cleaned the storage from the rom and tried to install another version of android 10 which is GSI. But then also everything went wrong and my phone said "Your sistem is destroyed, press power button to shutdown" or something like that and that is it something went teribly wrong and i dont know what else i can do to fix this, it is very strange that everything works except sensors. I dont know what could be releated to this problem.
hrvoje007 said:
Yes i used EDL mode to falsh rom, and yes i pressed clean all.
Firstly i installed twrp, then i tried to instal android 10 pixel experience rom, but then i was stucked in bootlop, then i cleaned the storage from the rom and tried to install another version of android 10 which is GSI. But then also everything went wrong and my phone said "Your sistem is destroyed, press power button to shutdown" or something like that and that is it something went teribly wrong and i dont know what else i can do to fix this, it is very strange that everything works except sensors. I dont know what could be releated to this problem.
Click to expand...
Click to collapse
It seems that the GSI that you used before is the culprit.
Some things you can try:
- Try other firmware versions, probably a downgrade like v10.0.3.0
- Try to erasing first in fastboot as many as partitions you can in both slot before to flash through MiFlash tool. I know that MiFlash tool overwite them but just to be sure.
- Probably you might try flashing with other tool like QPST or other qualcomm flasher tool, I´m not sure which actually works for our device.
- If you resized some partitions to flash a GSI you have to restore them to the exact size that was before.
I was watching youtube tutorial from iboy editz and something i probably did wrong, but it doesnt matter anymore because i can lieve with this isuse it just iritating and always deleting everything from the phone and instaling again takes to much of my time, but anyways thank you for help
Related
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 have a Xiaomi Note 8 Pro initially came with China Stable Rom V11.0.3.0.PGGCNXM. It was also unlocked.
I accidentally flashed Global Stable ROMV11.0.6.0.PGGMIXM via MiFlashTool and while it was successful, it rebooted to Recovery Mode with the message "This MIUI version can't be installed on this device".
After that, I pressed "Wipe All Data", so now the device is also locked.
Since there is no OS installed, I cannot access the device and consiquently to use Mi Unlock Tool properly to Unlock it again.
The device is now locked, without OS installed. However I can access Fastboot menu and Recovery mode.
Is there anyway to unlock the device in this state and flash it's original Rom again?
Please if you have anything to suggest that might help me, answer my question. I'm desperate. :crying:
Hmmm. Can you still access fastboot mode? If yes I recommend using miflash pro and flashing the correct rom for your device, or manually flashing all images via fastboot.
You've likely selected Clean all and lock (default setting) which flashed MIUI and locked the bootloader afterwards which bricked the device because of cross-region ROM flashing. Since you can't flash it with locked bootloader your only option is to take it to the service center.
@JuanM2020 @n0b0dy666 First of all, thank you guys for your suggestions.
Update: I tried to flash it's original Rom via MiFlash Pro, however when I connected my device on the final step, as for the SP tool to flash the Rom, my pc couldn't detect it. I even risked and disassembled the device to remove the battery in order to turn off the device, but it didn't work either. (Cdc & Vcom Mediatek drivers both installed properly on my pc).
The device is recognized by my computer when in Flashboot menu. However for the SP tool to work, it should be turned off, but recognizable from computer.
Before posting here, of course I went to a service center, but they told me because I tried to install Global Rom 11.0.06, while it's original Rom was China Stable Rom 11.0.03, I should wait for the 11.0.06, as a downgrade is not possible (not sure if it's true). We don't have an official Xiaomi Center in my county, where I go was the best chance I had.
Any other recommendations?
RenginaP said:
@JuanM2020 @n0b0dy666 First of all, thank you guys for your suggestions.
Update: I tried to flash it's original Rom via MiFlash Pro, however when I connected my device on the final step, as for the SP tool to flash the Rom, my pc couldn't detect it. I even risked and disassembled the device to remove the battery in order to turn off the device, but it didn't work either. (Cdc & Vcom Mediatek drivers both installed properly on my pc).
The device is recognized by my computer when in Flashboot menu. However for the SP tool to work, it should be turned off, but recognizable from computer.
Before posting here, of course I went to a service center, but they told me because I tried to install Global Rom 11.0.06, while it's original Rom was China Stable Rom 11.0.03, I should wait for the 11.0.06, as a downgrade is not possible (not sure if it's true). We don't have an official Xiaomi Center in my county, where I go was the best chance I had.
Any other recommendations?
Click to expand...
Click to collapse
If you can still access fastboot mode flash correct images manually.
E.g.:
Fastboot flash system system.img
Fastboot flash vendor vendor.img
Fastboot flash recovery recovery.img
Etc etc
JuanM2020 said:
If you can still access fastboot mode flash correct images manually.
E.g.:
Fastboot flash system system.img
Fastboot flash vendor vendor.img
Fastboot flash recovery recovery.img
Etc etc
Click to expand...
Click to collapse
So sorry for my late response. Is there any guide about manual flashing which I can follow for that?
RenginaP said:
So sorry for my late response. Is there any guide about manual flashing which I can follow for that?
Click to expand...
Click to collapse
https://www.xiaomigeek.com/flash-miui-fastboot-rom-using-command.html
Could you fix it?
Greetings everyone!
I'll try to resume my case:
I unlocked the bootloader like 3 weeks ago, installed the eu rom and everything was working fine. Today I decided to flash Arrow OS and the process finished succesfully, but I was having a lot of reboots, so I decided to go back to stock.
I entered fastboot mode, and after that, launched xiaomitools (latest version), selected the "my device is bricked, fastbood mode" and then it started to download the latest firmware and then it tried to flash it.
It flashed some img's but it got stuck when the program tried to flash the "super" img, I got an error message, I choose the "try again" option, and left the phone for like 20 minutes, nothing happened, the program got stuck trying to flash the super.img.
After that, I downloaded the latest MiFlash and tried to flash the stock firmware, but it won't finish, after 1,200 seconds, it shows a timeot and an error:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Does anyone know what can I do in order to flash the stock rom again? D=
My device is unlocked:
Thank you guys!
have you tried a USB 2.0 port? can be fussy about the ports...
also, which rom version are you flashing, do you have the exact title?
Not sure why it's timing out offhand (i am not overly experienced with xiaomi either), but super.img does take quite some time... but not 20mins, strange
Have you tried clicking 'driver' tab in miflash and installing necessary drivers?
I like the title of your thread, seems like you did some searching on the forum for answers before you decided to make the post!
I'm pretty sure the experts on this forum will be able to provide you with some assistance.
Too bad I'm not much help in terms of unbricking steps, I don't have any experience with it since I've haven't bricked a device before.
Good luck!
deleted...
Thank you for your answers guys!
The exact version of the rom that im trying to flash is:
alioth_global_images_V12.0.3.0.RKHMIXM_20210416.0000.00_11.0_global_b716fd8a83
Also, I tried editing the flash_all.zip taking out the "crc" lines (2 lines) and after that I'm trying to flash the rom via cmd adb, so far it seems it's working, super just finished flashing and now the rest of the rom is also flashing.
I'll report back when it finishes!
Ok, the rom finished the flashing process:
The device rebooted, showed the initial logo and then it got into a bootloop.
After I don't know, 20 restarts from the bootloop, it entered in fastboot mode.
Meh, I don't know what to do anymore. D=
I don't know if this has something to do, but on the arrow os flashing instructions, you had to flash their boot and vendor images:
fastboot flash boot_ab boot_alioth.img
fastboot flash vendor_boot_ab vendor_boot_alioth.img
fastboot --set-active=a
I suposse that those images get replaced by the stock ones when you install the stock rom, am I right?
Also, when I restart the device, it goes directly into fastboot mode in like .5 seconds.
D=
If it fails for some reason.. could try what Dadovvv writes here
Kimbaroth said:
Ok, the rom finished the flashing process:
View attachment 5326777
The device rebooted, showed the initial logo and then it got into a bootloop.
After I don't know, 20 restarts from the bootloop, it entered in fastboot mode.
Meh, I don't know what to do anymore. D=
I don't know if this has something to do, but on the arrow os flashing instructions, you had to flash their boot and vendor images:
fastboot flash boot_ab boot_alioth.img
fastboot flash vendor_boot_ab vendor_boot_alioth.img
fastboot --set-active=a
I suposse that those images get replaced by the stock ones when you install the stock rom, am I right?
D=
Click to expand...
Click to collapse
yes, they all get replaced by stock again. see my post above, Dadovvv recommends to run flash_all.bat directly without miflash if you're having issues. kinda forces the flash i guess. up to you though
reg66 said:
yes, they all get replaced by stock again. see my post above, Dadovvv recommends to run flash_all.bat directly without miflash if you're having issues. kinda forces the flash i guess. up to you though
Click to expand...
Click to collapse
Yup, that's what I did, i ran the flash all script in order to flash everything, but when it finishes, it reboots and bootloops for like 20 loops and then enters fastboot mode.
If I try to enter recovery, it also goes straight to fastboot mode.
reg66 said:
have you tried a USB 2.0 port? can be fussy about the ports...
also, which rom version are you flashing, do you have the exact title?
Not sure why it's timing out offhand (i am not overly experienced with xiaomi either), but super.img does take quite some time... but not 20mins, strange
Have you tried clicking 'driver' tab in miflash and installing necessary drivers?
Click to expand...
Click to collapse
atm i changed the usb port from 3.0 to 2.0 and tried by 2ble clicking the flash_all.bat, it's flashing the rom again.
I'll report back when it finishes.
Kimbaroth said:
Yup, that's what I did, i ran the flash all script in order to flash everything, but when it finishes, it reboots and bootloops for like 20 loops and then enters fastboot mode.
If I try to enter recovery, it also goes straight to fastboot mode.
Click to expand...
Click to collapse
hmm. a couple more possible solutions...
1. try this tool, it includes an older version of miflash under one of the tabs (no need to sign in, just close the mi account box that opens) and try flashing from there. scrap that, i thought that tool linked to it's own older version of miflash, but it doesn't... my bad
2. it could be as simple as a factory reset that's needed... could fastboot boot twrp, factory reset typing 'yes', power off the device and try booting to system once more...
(sorry!) and a quick question, before flashing arrowOS, did you come from stock 12.0.3 like you said above or did you have a later version of stock or xiaomiEU?
---- i'm wondering if miflash is thinking you're trying to downgrade and won't flash because of ARB. (although i would have thought you would get and error message before the flash started if this was the case... anyhow, can't see how it would hurt to try without the ARB checks. i would advise checking your ARB (anti rollback) status before, just to be on the safe side... see my post here
I'm go
reg66 said:
hmm. a couple more possible solutions...
1. try this tool, it includes an older version of miflash under one of the tabs (no need to sign in, just close the mi account box that opens) and try flashing from there.
2. it could be as simple as a factory reset that's needed... could fastboot boot twrp, factory reset typing 'yes', power off the device and try booting to system once more...
(sorry!) and a quick question, before flashing arrowOS, did you come from stock 12.0.3 like you said above or did you have a later version of stock or xiaomiEU?
Click to expand...
Click to collapse
I'm gonna try your 2nd solution, lets see if it works, ifthat doesnt works i'll try the miflash solution.
And I was on the 12.0.3 firmware before flashing the latest eu rom, after that I just installed the rom with their instructions (using their recovery, not TWRP) and aaaaaafter that, i tried to go back to stock and this hell started =(
Kimbaroth said:
I'm go
I'm gonna try your 2nd solution, lets see if it works, ifthat doesnt works i'll try the miflash solution.
And I was on the 12.0.3 firmware before flashing the latest eu rom, after that I just installed the rom with their instructions (using their recovery, not TWRP) and aaaaaafter that, i tried to go back to stock and this hell started =(
Click to expand...
Click to collapse
ahh ok.... so yeah, try a factory reset in booted twrp. But, see my other post after regarding ARB. i suspect that's the issue. xiaomiEU is a later version than the stock you are trying to flash... you need to take out some lines in the flash_all.bat by changing the .bat to .txt
remove all lines near the top regarding ARB (but leave all fastboot lines intact), save, exit, change back to .bat and run it again in miflash
reg66 said:
ahh ok.... so yeah, try a factory reset in booted twrp. But, see my other post after regarding ARB. i suspect that's the issue. xiaomiEU is a later version than the stock you are trying to flash... you need to take out some lines in the flash_all.bat by changing the .bat to .txt
remove all lines near the top regarding ARB (but leave all fastboot lines intact), save, exit, change back to .bat and run it again in miflash
Click to expand...
Click to collapse
My ARB # is 1, the ARB # of 12.0.3 is 0 (lower than mine), so... just taking out the anti version lines from the .bat it will work?
Edit: I'm flashing the .bat without those lines, I'll report back.
Kimbaroth said:
My ARB # is 1, the ARB # of 12.0.3 is 0 (lower than mine), so... just taking out the anti version lines from the .bat it will work?
Click to expand...
Click to collapse
well sorry to report i can't say for certain. i had that issue but ended up flashing stock 12.0.5 rom (still lower than the xiaomiEU version i had before. all went fine. So yeah, basically i haven't tried on 12.0.3. But... i think the arb = 1 on your device simply means arb is not activated yet. so i would assume any version is fine to flash, just by removing said lines from the bat file...
sorry, no promises though. do so at your own risk hopefully someone else in the 'know' will be able to chip in...
DONT DO IT
not sure sure this applies to your/our device but for poco f1
'Don't flash a ARB 0 firmware/ROM onto an ARB 1 device. Even though some people disagree, they cannot link to success stories. Likely, this concerns very old firmware.' taken from here
One moment, i'll link you to 12.0.5 fw that has arb=1 which i've rolled back to myself...
reg66 said:
well sorry to report i can't say for certain. i had that issue but ended up flashing stock 12.0.5 rom (still lower than the xiaomiEU version i had before. all went fine. So yeah, basically i haven't tried on 12.0.3. But... i think the arb = 1 on your device simply means arb is not activated yet. so i would assume any version is fine to flash, just by removing said lines from the bat file...
sorry, no promises though. do so at your own risk hopefully someone else in the 'know' will be able to chip in...
Click to expand...
Click to collapse
OMG, it worked!
I removed the anti rollback comments and the crc check ones from the flash_all.bat, flashed the firmware via miflash and miflash showed an error:
But miui started booting on the phone! =D
THAAAAAAAAAANK YOU!!!!!!!!!
To flash the latest stable release (it was released today AFAIK, miui_ALIOTHGlobal_V12.5.1.0.RKHMIXM_e9845255d6_11.0) can I just flash it via TWRP, right?
THANK YOU THANK YOU THANK YOU!!!
Kimbaroth said:
OMG, it worked!
I removed the anti rollback comments and the crc check ones from the flash_all.bat, flashed the firmware via miflash and miflash showed an error:
View attachment 5326791
But miui started booting on the phone! =D
THAAAAAAAAAANK YOU!!!!!!!!!
To flash the latest stable release (it was released today AFAIK, miui_ALIOTHGlobal_V12.5.1.0.RKHMIXM_e9845255d6_11.0) can I just flash it via TWRP, right?
THANK YOU THANK YOU THANK YOU!!!
Click to expand...
Click to collapse
well thank FcK for that!!! so you flashed the 12.0.3 rom right?
and yeah... for 12.5.1 stable (at least what i did is...) fastboot boot twrp. copy twrp.img over to phone, go to advanced and select 'install to ramdisk' then flash your twrp.img. Reboot twrp, copy over rom and flash, factory reset after and boot (going from memory, but pretty sure that's it. back on arrowOS right now, so can't verify)
BTW, after flashing with miflash - it seems to always give that error at the end. i just assumed it's because the 'lock' cmd wasn't run/requested. maybe it's a bug, who knows!!
reg66 said:
well thank FcK for that!!! so you flashed the 12.0.3 rom right?
and yeah... for 12.5.1 stable (at least what i did is...) fastboot boot twrp. copy twrp.img over to phone, go to advanced and select 'install to ramdisk' then flash your twrp.img. Reboot twrp, copy over rom and flash, factory reset after and boot (going from memory, but pretty sure that's it. back on arrowOS right now, so can't verify)
BTW, after flashing with miflash - it seems to always give that error at the end. i just assumed it's because the 'lock' cmd wasn't run/requested. maybe it's a bug, who knows!!
Click to expand...
Click to collapse
Yeah, I flashed 12.0.3 taking out those lines (the anti rollback ones and the crc check ones), miflash gave me an error at the end, but it worked lol
I think i'm gonna stick with the latest stable firmware for a while. I really wanted to try Arrow OS, but as I said earlier, after flashing it it gave me a lot of crashes/reboots, do you know by any chance why that happened?
Thanks again man!!! I learned something new today thanks to you! =D
I was on 12.5.4 Global and wanted to switch to 12.5.6 EEA, and i've red here and there that was a "safe" operation. I've tried to unlock the bootloader and flash the rom, all the roms gave compatibility issues, so i flashed the 12.0.3 EEA, but it was stucked on the boot logo. I've read that boot into EDL mode and flash via MiFlash could resolve the thing.
I tried but MiFlash crashes everytime i try to flash a rom.
Could someone give an help?
UPDATE: Now is in fastboot, same problem with the stock roms.
Did you read any tutorial? For which reason you flash 12.0.3?
Looks like you triggered anti-rollback protection. Read here https://www.xda-developers.com/xiaomi-anti-rollback-protection-brick-phone/
You cannot install previous versions of miui.
If by some chance the phone still boots to fastboot mode, try to install the LATEST firmware for your phone via mi flash tool (make sure you check "clean all" option and NOT the "clean all and lock" which is default in the flash tool).
And no, you cannot use EDL with this phone. EDL is locked to regular users and can only be accessed by an authorized account.
If you ca access fastboot and the device is recognized by you computer in fastboot mode then you can flash Miui using MiFlash.EDL mode is when you dont have access to fastboot.
Read tutorials about flashing miui using miflash on youtube.
brescianienea said:
I was on 12.5.4 Global and wanted to switch to 12.5.6 EEA, and i've red here and there that was a "safe" operation. I've tried to unlock the bootloader and flash the rom, all the roms gave compatibility issues, so i flashed the 12.0.3 EEA, but it was stucked on the boot logo. I've read that boot into EDL mode and flash via MiFlash could resolve the thing.
I tried but MiFlash crashes everytime i try to flash a rom.
Could someone give an help?
UPDATE: Now is in fastboot, same problem with the stock roms.
Click to expand...
Click to collapse
If u are in fastboot mode, install this : https://www.mediafire.com/file/lv98wac50a2dexz/MiFlash20210226.zip/file. extract and launch the exe, click on install. wait a pop-up in chinese and close all. Then re-try to re flash the EEA (in CLEAN ALL) with this mi flash. Tell me if all works
X0PIRAT3 said:
If u are in fastboot mode, install this : https://www.mediafire.com/file/lv98wac50a2dexz/MiFlash20210226.zip/file. extract and launch the exe, click on install. wait a pop-up in chinese and close all. Then re-try to re flash the EEA (in CLEAN ALL) with this mi flash. Tell me if all works
Click to expand...
Click to collapse
Or install via any mi flash lol.
It sounds like normal thing...
Cross flashing global/EEA tends to fail for whatever reason ( Super doesn't flash correctly ) and you get stuck bootlooping or straight towards fastboot depending on how far the super flashed...
Go back to global ROM and sit there. It should flash alright.
Idk why it does this ... Something is not alright with this phone
{Mod edit: Quoted post has been deleted}
Yes it's always 604 or 606 seconds for mi flash no matter how good your PC is either because I have a good one it should be like 2 minutes.
Wtf? What do you guys mean edl mode you don't boot into edl mode that requires you to take the back off and jump it with wires or something. You boot into fastboot mode like you did to unlock bootloader and flash with miflash and you don't go from 12.5.6 to 12.0.3 normally downgrading will brick your device. Where the f did you get all of this from. If you can boot back into fastboot mode volume down and power key until it boots into fastboot than reflash the last working firmware you had with miflash and look at the video. I don't understand what all the countries believe they can do with a phone edl mode is like OEM type fixes not some kid on Xda
brescianienea said:
I was on 12.5.4 Global and wanted to switch to 12.5.6 EEA, and i've red here and there that was a "safe" operation. I've tried to unlock the bootloader and flash the rom, all the roms gave compatibility issues, so i flashed the 12.0.3 EEA, but it was stucked on the boot logo. I've read that boot into EDL mode and flash via MiFlash could resolve the thing.
I tried but MiFlash crashes everytime i try to flash a rom.
Could someone give an help?
UPDATE: Now is in fastboot, same problem with the stock roms.
Click to expand...
Click to collapse
Yes it's always 604 or 606 seconds for mi flash no matter how good your PC is either because I have a good one it should be like 2 minutes.
Wtf? What do you guys mean edl mode you don't boot into edl mode that requires you to take the back off and jump it with wires or something. You boot into fastboot mode like you did to unlock bootloader and flash with miflash and you don't go from 12.5.6 to 12.0.3 normally downgrading will brick your device. Where the f did you get all of this from. If you can boot back into fastboot mode volume down and power key until it boots into fastboot than reflash the last working firmware you had with miflash and look at the video. I don't understand what all the countries believe they can do with a phone edl mode is like OEM type fixes not some kid on Xda
You can always tell your on Xda when they offer help that is 1 link and try this is the only information they give. The reason you screwed up is because lazy people that don't leave full instructions. You never never never never need to worry about edl mode. Fast boot or bootloader mode as it's called is how you restore a soft bricked phone what did you do with edl mode I don't even understand what you tried to do.
brescianienea said:
I was on 12.5.4 Global and wanted to switch to 12.5.6 EEA, and i've red here and there that was a "safe" operation. I've tried to unlock the bootloader and flash the rom, all the roms gave compatibility issues, so i flashed the 12.0.3 EEA, but it was stucked on the boot logo. I've read that boot into EDL mode and flash via MiFlash could resolve the thing.
I tried but MiFlash crashes everytime i try to flash a rom.
Could someone give an help?
UPDATE: Now is in fastboot, same problem with the stock roms.
Click to expand...
Click to collapse
You thought this is something you needed to do? Edl mode is nothing that a regular soft brick would require
Here's another one edl mode I can't understand why you or anyone else would think this is how we restore a soft bricked phone lol this would be crazy I would be done. Your not even close to the first person to say this. Same with battery backup that doesn't make sense it's not battery backup you don't backup your battery it's battery life
good evening
I have been trying to return to stock miui from Pixel Experience since yesterday but get this error every time I try to flash the Firmware and do not know what I can do about it. I would be happy if somebody knew what this error is from and what might fix it.
Same problem. Don't try more things because you will brick your phone like mine.
Thanks for your reply. What did you do that bricked your Phonem? This way I know what to avoid. Thanks you in advance
As you are sure your device is a eea one, try with this last official stable firmware : Version: V13.0.7.0.SKHEUXM
You can find it here https://new.c.mi.com/global/miuidownload/detail/device/1900394
Fastboot version here at bottom : https://xiaomifirmwareupdater.com/miui/alioth/stable/V13.0.7.0.SKHEUXM/
Or https://bigota.d.miui.com/V13.0.7.0...EUXM_20220627.0000.00_12.0_eea_e461331a7d.tgz
Thanks you so much I will try that
and i did not mention this but I started this whole project of returning to miui because my poco was and still is in a bootloop and is only accessible over fastboot, not recovery and even though it sometimes gets to the system it almost instantly crashes and reboots
Still the Same Error unfortunatelly
nockcx said:
and i did not mention this but I started this whole project of returning to miui because my poco was and still is in a bootloop and is only accessible over fastboot, not recovery and even though it sometimes gets to the system it almost instantly crashes and reboots
Click to expand...
Click to collapse
Ok,
Do you have any idea what you did that may have caused this bootloop ?
Have you used any Qualcomm Tools or any soft in EDL mode ?
No, I did not do anything that would mess with the system to my knowledge . which is why i really do not know what to do. Can This Error occur because of a USB 3.0 used to flash? The Phone even tries to reboot when it is detected as a Fastboot device, maybe This has Something to do with it. Maybe it loses the Connection and therefore the flashing process stops. Are there possible ways to fix This?
Try with the latest android platform tools.
Put the content of platform tools archive in the fastboot folder and launch flash_all.bat don't use flash_all_lock
Still the Same Error . Can This be because of a Driver or a hardware issue?
i had similar issues but with the super partition when trying to flash from cmd.
flashing with miflash instead solved it.
It doesnt seem to make any difference to the error whether i flash it via cmd or miflash
nockcx said:
Still the Same Error . Can This be because of a Driver or a hardware issue?
Click to expand...
Click to collapse
Maybe : So as you can try with other PC, USB cable, USB connector, reinstall USB drivers...
I already tried with two Notebooks, I will try again tomorrow with another PC and installing USB drivers again. Thank you
You could try redownloading the MIUI ROM... you got it from xiaomifirmwareupdater.com right?
And yes ^^, try other PCs/laptops and other USB-cables.
Just please make sure
Unfortunately, Fastboot-Flashing is a gamble. It's not a solid protocol. It has zero protection against sudden USB-connection loss.
And manufacturers like Xiaomi go out of their way and block Qualcomm's EDL Mode, which is the only way to recover your phone in case Fastboot Mode stops working, because that Mode itself can also get damaged.
Fixed - first flash a miui recovery rom from twrp make sure the rom version lower than the latest one, now flash and boot miui , now just update from miui updater once you updated to the latest version , now try to flash the fastboot rom that you trying to flash, it should work.
I cant access a bootloader like TWRP because the phone still keeps rebooting after a couple of seconds in the bootloader so i cant really do much. I only have access to fastboot
nockcx said:
just flash a custom vbmeta and then install a custom recovery in to the boot partition like fastboot flash boot ....flash both the slots boot_a and boot_b the run fastboot reboot recovery do all this with latest platform tools
Click to expand...
Click to collapse
okay Im as far as I have never been with a very weird method, maybe somebody can explain. Because my poco always wants to reboot I found out a way to keep in in Fastboot mode. I repeatedly press the power and volume down button, This way it stays on for a lot longer, but it still is not enough to succeed at flashing the rom. It also lets me believe that my problem is not a software but probably a hardware problem, otherwise and cannot explain this suuuper weird behavior. what do you guys think? is there a possible fix you know?