Related
while following these instructions in the youtube video named Moto G6 2018 Install Twrp & Root Easy Tutorial 757 or 12:44 at this part i must have downloaded the wrong file since my build model is XT1922-9 type M373B could someone help me resolve me issue so i can fix my phone and finish the root cause my phone refuses to boot
Provide more info about your device including device variant, os version. More info the better so we know how to help you.
Jleeblanch said:
Provide more info about your device including device variant, os version. More info the better so we know how to help you.
Click to expand...
Click to collapse
It's a moto g6 play android 8 or it still turns on but it's stuck on the bootloader screen and I need help fixing that and finishing the rooting of my phone
kc02141994 said:
It's a moto g6 play android 8 or it still turns on but it's stuck on the bootloader screen and I need help fixing that and finishing the rooting of my phone
Click to expand...
Click to collapse
I figured out that much from your first post, I was referring to which variant specifically (ex: 192x-x) and do you know what the stock factory firmware version is?
Jleeblanch said:
I figured out that much from your first post, I was referring to which variant specifically (ex: 192x-x) and do you know what the stock factory firmware version is?
Click to expand...
Click to collapse
i dont know but all i know is my phones build model is XT1922-9 TYPE M373B the phone still turns on but it goes to the bootloader menu with the error message start up failed your device didint start up successfully use the sofware repair assistant on your computer to repair your device connect your device to your computer to get the software repair assistant AP fastboot flash mode secure error failed to load kernal fastboot reason fall through from normal boot i want to fix my phone and finish rooting it so i can use the wifi tether app and i dont know what to do which is why im asking for help i followed the instructions from that video but i downloaded and put in the wrong file i think my phone can be finished rooting and fixed so if i could just get the file i need i can finish rooting and use my phone again
kc02141994 said:
i dont know but all i know is my phones build model is XT1922-9 TYPE M373B the phone still turns on but it goes to the bootloader menu with the error message start up failed your device didint start up successfully use the sofware repair assistant on your computer to repair your device connect your device to your computer to get the software repair assistant AP fastboot flash mode secure error failed to load kernal fastboot reason fall through from normal boot i want to fix my phone and finish rooting it so i can use the wifi tether app and i dont know what to do which is why im asking for help i followed the instructions from that video but i downloaded and put in the wrong file i think my phone can be finished rooting and fixed so if i could just get the file i need i can finish rooting and use my phone again
Click to expand...
Click to collapse
Hm, ok. If you're getting kernel failed to load errors from the bootloader, then maybe you flashed the wrong boot.img for your device?
Either way, try flashing the XT1922-9_no_dm-verity_boot.img.
To do so, make sure you have TWRP. You don't have to install it, but if you wanna root you can flash it...
So either do..
Code:
fastboot boot moto-g6-play-jeter-patched-twrp.img
Or do..
Code:
fastboot flash recovery moto-g6-play-jeter-patched-twrp.img
After you have TWRP running, then flash the boot.img by doing..
Code:
fastboot flash boot XT1922-9_no_dm-verity_boot.img
All of these instructions are found in the thread for your device [GUIDE][ROOT][Moto G6 Play][JETER] TWRP, Root, and magisk installation guide
There is also a step to flash a modified fstab.qcom file to remove forced encryption as well which you should look into. But honestly I would like to see you get outta this situation you're currently in then we'll get the rest done after
Jleeblanch said:
Hm, ok. If you're getting kernel failed to load errors from the bootloader, then maybe you flashed the wrong boot.img for your device?
Either way, try flashing the XT1922-9_no_dm-verity_boot.img.
To do so, make sure you have TWRP. You don't have to install it, but if you wanna root you can flash it...
So either do..
Code:
fastboot boot moto-g6-play-jeter-patched-twrp.img
Or do..
Code:
fastboot flash recovery moto-g6-play-jeter-patched-twrp.img
After you have TWRP running, then flash the boot.img by doing..
Code:
fastboot flash boot XT1922-9_no_dm-verity_boot.img
All of these instructions are found in the thread for your device [GUIDE][ROOT][Moto G6 Play][JETER] TWRP, Root, and magisk installation guide
There is also a step to flash a modified fstab.qcom file to remove forced encryption as well which you should look into. But honestly I would like to see you get outta this situation you're currently in then we'll get the rest done after
Click to expand...
Click to collapse
ok that problem solved now im stuck on an infinite bootloop after i do the parts where the guy says wipe then download those files from the sd card and when i reboot the phone it does says N/A on the top left and starts boot looping
Jleeblanch said:
Hm, ok. If you're getting kernel failed to load errors from the bootloader, then maybe you flashed the wrong boot.img for your device?
Either way, try flashing the XT1922-9_no_dm-verity_boot.img.
To do so, make sure you have TWRP. You don't have to install it, but if you wanna root you can flash it...
So either do..
Code:
fastboot boot moto-g6-play-jeter-patched-twrp.img
Or do..
Code:
fastboot flash recovery moto-g6-play-jeter-patched-twrp.img
After you have TWRP running, then flash the boot.img by doing..
Code:
fastboot flash boot XT1922-9_no_dm-verity_boot.img
All of these instructions are found in the thread for your device [GUIDE][ROOT][Moto G6 Play][JETER] TWRP, Root, and magisk installation guide
There is also a step to flash a modified fstab.qcom file to remove forced encryption as well which you should look into. But honestly I would like to see you get outta this situation you're currently in then we'll get the rest done after
Click to expand...
Click to collapse
i really need help on this i cant finish the root i dont know what im doing wrong im up to the part in the video i watched and after i finished doing that part it begins infinite rebooting and i dont know what to do i installed the right file did everything he did but instead of getting the message in the center i get N/A on the top left and then infinite reboots
Jleeblanch said:
Hm, ok. If you're getting kernel failed to load errors from the bootloader, then maybe you flashed the wrong boot.img for your device?
Either way, try flashing the XT1922-9_no_dm-verity_boot.img.
To do so, make sure you have TWRP. You don't have to install it, but if you wanna root you can flash it...
So either do..
Code:
fastboot boot moto-g6-play-jeter-patched-twrp.img
Or do..
Code:
fastboot flash recovery moto-g6-play-jeter-patched-twrp.img
After you have TWRP running, then flash the boot.img by doing..
Code:
fastboot flash boot XT1922-9_no_dm-verity_boot.img
All of these instructions are found in the thread for your device [GUIDE][ROOT][Moto G6 Play][JETER] TWRP, Root, and magisk installation guide
There is also a step to flash a modified fstab.qcom file to remove forced encryption as well which you should look into. But honestly I would like to see you get outta this situation you're currently in then we'll get the rest done after
Click to expand...
Click to collapse
new problem i cant install magiks and now it says theres no OS installed this phone is seriously screwed up and its one of my only sources of internet
kc02141994 said:
new problem i cant install magiks and now it says theres no OS installed this phone is seriously screwed up and its one of my only sources of internet
Click to expand...
Click to collapse
Ok, well we're getting somewhere at least. Sounds like you have the right boot.img at the very least. Now we need to find you the right stock firmware (or even at minimum a system.img and vendor.img from some else with the same device).
I'll look around to see what I can find.
Next thing I need from you is to connect your device to the computer and reboot to bootloader and get me the output of..
Code:
fastboot getvar all
and copy/paste it to https://hastebin.com or copy/paste it to a text file and upload the text file as an attachment here (or wherever you want and post the link) so I can review it. That should tell me what I need to know to help you a little better. Do NOT just copy/paste the output into a post please.
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 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
so my ginkgo got hardbricked today.. i couldn't access fastboot and recovery mode. but it does bootloop instead of getting the text "System got destroyed"...
Anybody got a solution for this? I tried to flash TWRP to wipe my data, and use MiFlashTool to relock the bootloader as well as flash MIUI stock rom.
hellohell0 said:
so my ginkgo got hardbricked today.. i couldn't access fastboot and recovery mode. but it does bootloop instead of getting the text "System got destroyed"...
Click to expand...
Click to collapse
"System got destroyed" does not display on all types of bricks
hellohell0 said:
Anybody got a solution for this? I tried to flash TWRP to wipe my data, and use MiFlashTool to relock the bootloader as well as flash MIUI stock rom.
Click to expand...
Click to collapse
make sure the power button is not stuck
do not relock your bootloader (you have no chance of fixing it while locked,beside EDL)
try flashing VBMETA first, then see with a custom recovery
loopypalm said:
"System got destroyed" does not display on all types of bricks
make sure the power button is not stuck
do not relock your bootloader (you have no chance of fixing it while locked,beside EDL)
try flashing VBMETA first, then see with a custom recovery
Click to expand...
Click to collapse
Hello. Sorry I couldn't reply quicker due to busy week. I tried to flash TWRP through fastboot mode but no luck. So, flashing VBMETA would be useless too, Since fastboot couldn't recognize my phone (
Code:
fastboot devices
). Please note that I've had the USB driver installed for my phone.
hellohell0 said:
Hello. Sorry I couldn't reply quicker due to busy week. I tried to flash TWRP through fastboot mode but no luck. So, flashing VBMETA would be useless too, Since fastboot couldn't recognize my phone (
Code:
fastboot devices
). Please note that I've had the USB driver installed for my phone.
Click to expand...
Click to collapse
i'm not sure what could be the problem here (no enough data)
could be the usb cable
could be the usb port
could be the windows version/drivers ...
if you are 100% sure those are not the cause then your only left option is EDL
loopypalm said:
i'm not sure what could be the problem here (no enough data)
could be the usb cable
could be the usb port
could be the windows version/drivers ...
if you are 100% sure those are not the cause then your only left option is EDL
Click to expand...
Click to collapse
Just got back from my friend's house. Yes, the solution is EDL
My phone is back to normal now, but this would happen again since my friend told me that the eMMC might be corrupted.
Thank you for the help! I thought it was impossible since my phone won't fully recognized in the PC (It was called Android but with question mark)
Case closed.
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?