Database Info

[Q] Nexus 5 Recovery broken and OS is missing

Hello Everyone. Normally I´m the quiet Reader and not the Active Poster but I need your help guys.
I have a problem since yesterday and I tried to fix it by myself with searching everywhere but couldn´t do it by myself.
What I had before:
Optipop 5.0.2 with Racer Kernel (both had Builds from January) + TWRP 2.8.1
What I wanted to do:
Flash Grogg's AOSP 5.1 and newest Code Blue Kernel
What happenend:
I factory resetted and successfully flashed Grogg's AOSP 5.1 and Code Blue Kernel but had Problems with FCing Clock and Dialer so I tried to reflash both after wiping completely (even internal storage), mounted it and put the needed new files on the internal storage.
I reflashed the Custom Rom + Custom Kernel and the newest Radio, wiped Cache/Dalvik and rebooted. It booted and the notification screen with 'optimizing apps' appeared. After that that screen went black and nothing else.
It was lit so I´knew that the device wasn´t shut down and tried to rebbot sincee nothing happened. I noticed that it was possible to reboot or shut down the device normally so there might have been a Problem with the Rom.
I retried the whole procedure and this time the notification screen didn´t show up after the boot logo and went directly to the black blank screen but i still had the possibility to rebbot/shut down the device normally. This time I didn´t wipe the whole storage and this time it got stuck at the boot logo and the Custom Recovery seems to be broken, too. The screen shows the dead Android with the red triangle.
My Problem is that I can´t connect my device to the computer, find it with 'adb devices' and reflash the Recovery with fastboot. The device is shown as 'android' in device manager in Windows 7 and nothing else. I already tried to un- and reinstall the Google drivers and that whole stuff but it doesn´t work for God's sake. adb doesn´t list my device and the 'list of devices attached' is blank although my device is connected.
I know my phone is soft bricked and that it is possible to fix that although I don´t know why it even broke the OS and Custom Recovery.
Can anyone help me out with a step-for-step-guide to fix the adb Problem and explain me why that blank screen even happenend?
Edit: If I´m in fastboot mode the device is shown as >Android Bootloader Interface< and isn´t listed with 'adb devices'. If it is powered off it is shown as >Android Composite ADB Interface< but is listed with 'adb devices' but I can´t flash the Custom Recovery.

Beyazid said:
My Problem is that I can´t connect my device to the adb to reflash the Recovery.
Click to expand...
Click to collapse
You don't use adb to flash a custom recovery. You use fastboot. That's your first problem.

I actually meant that it isn´t shown with the command 'adb devices' I will change that in the text
Edit: I also noticed that the fastboot mode is always on in the bootloader although the device isn´t connected to the pc. Shouldn´t it only be active if it´s connected?

Beyazid said:
I actually meant that it isn´t shown with the command 'adb devices' I will change that in the text
Edit: I also noticed that the fastboot mode is always on in the bootloader although the device isn´t connected to the pc. Shouldn´t it only be active if it´s connected?
Click to expand...
Click to collapse
I see a couple problems here.
First one is use the newest version of TWRP. You can get that from my signature.
Second is Code_Blue may not be compatible with the ROM you are testing.
You don't need ADB at all for this, you need fastboot.

As I said. I just use adb to make sure that my device is found by and connected to the pc. I know that fastboot is used to flash everything but my Nexus 5 isn´t even shown. So how can I get my phone connected to flash the custom recovery?
And it seems like it is compatible since it worked the after the first installation and boot

FFS, XDA. I had just written a huge ass post on how to use fastboot properly, with the proper commands and ****, and you logged me out, making me lose all that. F U.
Beyazid said:
and the Custom Recovery seems to be broken, too. The screen shows the dead Android with the red triangle.
Click to expand...
Click to collapse
This is the stock recovery.
You need to put your device in fastboot mode, REFLASH TWRP again with fastboot, then STRAIGHT FROM FASTBOOT select (with vol keys and Power) "Restart recovery". When you're in TWRP, wipe data/factory reset, reflash rom, gapps, REBOOT, PROFIT.
`fastboot devices` and `adb devices` are two commands to check if an active connection exists, between the host interface (on the PC, look at it as servers) and the device interface (look at it as clients). both commands will only return your device's SN IF drivers are correctly installed (speaking on a basic level, and about Windows). If you execute those commands, no SN comes up, then you need to fix drivers FIRST. Not even worth trying to do other commands.
`fastboot devices` only works here -> http://bazalabs.com/wp-content/uploads/2014/07/20140705_215603.jpg
`adb devices` works in TWRP/CWM (NOT in stock recovery) and in Android itself (needs USB Debugging active).

Thanks for the help. I was able to flash the Custom Recovery and the Custom Rom with and without Code Blue Kernel but in both ways the phone loads, sets up at the boot logo and goes straight into the blank black screen which appears without the notification screen of the apps that get optimized.
I can manually turn off, reboot.or take a screenshot which clearly indicates that the Rom itself is installed.
How can I fix that problem?
Thanks in advance
Edit: Tried with the Blue Code Kernel which gave that blank screen and wiped everything but internal storage and reflashed just the Custom Rom which gave me the same result
Could it be because the system.img or boot.img are missing??

Beyazid said:
Thanks for the help. I was able to flash the Custom Recovery and the Custom Rom with and without Code Blue Kernel but in both ways the phone loads, sets up at the boot logo and goes straight into the blank black screen which appears without the notification screen of the apps that get optimized.
I can manually turn off, reboot.or take a screenshot which clearly indicates that the Rom itself is installed.
How can I fix that problem?
Thanks in advance
Edit: Tried with the Blue Code Kernel which gave that blank screen and wiped everything but internal storage and reflashed just the Custom Rom which gave me the same result
Could it be because the system.img or boot.img are missing??
Click to expand...
Click to collapse
Try another ROM.
System.img .. boot.img.. comes with the ROM you flashed (well, not exactly, but both partitions do get written to), so no, they're not missing.

I gave it another try and fixed it.
I'll write it down so anybody who ever faces that problem can solve that, too.
Follow that guide (http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701) step by step and after a few minutes of flashing and a few minutes of booting you should get a clean and fresh Android Version on your device. It removes all the old files and installs the newest files.
And thanks guys for helping me out with that adb/fastboot mistake. Kudos to you

Flashed stock recovery and thought I soft bricked my shield tablet.

First I'll give credit where it is due. From two threads on this site is where I got help with this issue:
I followed THIS guys steps for manually erasing and got the recovery images and lots of other useful information from HERE. Thank you guys very much!
OK, so, hopefully I can help someone with my little story as well. I was having issues with apps and programs crashing on me with lollipop and the new marshmallow update. The tablet just wasn't working properly and moving slow. I even had the SD card holding all my apps and larger files so I didn't overload the internal storage. So, I decided I wanted to flash back to factory/stock recovery and go from there. I did this using THIS method. I flashed via the "flash-all.bat" file (the command in fastboot is the same as the file name). I should note that there was one instance that failed during the install (I did try it again and got the same failure). Said something about “did you mean you wanted to flash this partition” or something, then showed it failed. After flashing I hit continue on the bootloader screen of the tablet and it said it was "cold booting." After about 5 minutes or so it started to boot but never made it past the NVidia screen. I tried wiping the phone with factory reset, wiping the cache, etc. and then re-flashing the recovery (again with the .bat file). I tried flashing TWRP but it didn't install apparently, because it still went to factory recovery. I even re-locked and then unlocked my bootloader to see if that would set everything straight. Nothing seemed to work. I knew I would eventually find a solution though so I kept looking. Stumbled on some other people that had the same issues but no solution (hope those people got it figured out). So here's what I did after some more research:
First, if you're in this situation and you did factory reset to try and resolve the problem, you may feel like you can no longer communicate with the device via fastboot/adb, but as long as you have the usb drive and your SDK tools installed (I used CodeWorks for Android all-in-one program) that shouldn't be a problem. You'll just have to be in the bootloader on the tablet.
-If for some reason you deleted or uninstalled your drivers and tools you'll have to download them again and then, the computer should still be able to communicate with the tablet. In the device manager under portable devices it will still show up as Module something or other. So the computer still sees the device but doesn't fully recognize it yet. Don't worry, this should still work! Just make sure you that fastboot is seeing the device by inputting "fastboot devices" in the command window and a 14 digit serial number should pop up. If it just says "list of devices" or there's nothing then you wont be communicating with the tablet.
Your device should be connected to your computer and started in bootloader mode. On your computer you should have the command prompt for adb/fastboot open. I just go to the folder where the .exe files are located and hold shift and right click in the white space of the folder, then select "open command window here."
From here follow the erase steps: stolen from manigault! :highfive:
fastboot erase system
fastboot erase userdata
fastboot erase boot
fastboot erase recovery
fastboot erase cache
Then flash your recovery MANUALLY:
fastboot flash recovery {dir}/recovery.img
fastboot flash boot {dir}/boot.img
fastboot flash system {dir}/system.img
fastboot flash userdata {dir}/userdata.img
fastboot flash staging {dir}/blob
fastboot flash dtb {dir}/tegra124-tn8-p1761-1270-a04-e-battery.dtb
You can download whatever recovery version you wish. I downloaded 2.2.2 because that's what my device came with out of the box on Christmas 2014. It will more then likely be a .zip file. To make this whole process a little easier simply extract the files in the .zip file where the adb.exe and fastboot.exe files are located (folder should be named platform-tools) and you can completely eliminate typing the whole directory before the file name. ***After your done flashing everything you can go back and delete those files if you want. Just double check that you're deleting the right files by looking at the original zip file. Not sure if it makes a difference but I deleted them anyway.
For example the commands in fastboot will look like this exactly :
(after extracting recovery files into platform-tools folder)
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash staging blob
fastboot flash dtb tegra124-tn8-p1761-1270-a04-e-battery.dtb
Note: Do NOT use the flash-all.bat command as this doesn't seem to work for this situation. Do it manually like shown above. And let each individual process complete before attempting to input another command.
After this step I didn't select continue on the bootloader. You can either select reboot or simply input "fastboot reboot" into the command window. It may take about 5 minutes to start installing everything but just be patient, it should start. Sometimes with these things you have to do things twice before it works. If for some reason it doesn't work the first time then start from the beginning and try it again. It took two times for me, but that's because I installed system.img twice and was getting double screen. Newb error... and I was a bit inebriated last night when I did this.
Hope this helps someone!
Thanks again to manigault and MidgetMob!
NVIDIA download files HERE!

i think i done the same thing
but the problem i now have is i cnt get tablet into fastboot on pc. i can load fastboot on tablet with power and volume down , but the tablet only shows as MTP device in device manager. i have downloaded drivers from nvidia and no matter what i try i cant install them i have been through all instructions but scince it went to mtp device i cant get device showing in adb. The only way i can get device showing in adb on pc ist to select apply update from adb ! but none of these commands listed in your post will work because its in sideload. is there anyway i cn reset , flash custom rom ect bu using commands while device is in adb sideload.
all i get is now send the package you want to apply to the device with "adb sideload <filename>".....
if you could shed any light on this it would be much appreciated , thanks , lester

did you update official android 6.0 before? then, not working stock recovery, stock boot...
If you can enter bootloader mode, download unofficial twrp 3.0.0.0 (here http://forum.xda-developers.com/shield-tablet/development/wip-twrp-2-8-0-1-unofficial-t2877117) and flash it.
i have a working boot.img file on marshmallow if you want.. please reply.

Sorry for the late response! I have no clue how you got into sideload??? Are you talking about through the recovery on your device? You're not able to get adb/ fastboot to recognize the device, right? It doesn't matter how you get the tablet into the bootloader. Whenever you have the phone in the bootloader then you'll use the fastboot command to "talk to" the device; i.e. "fastboot devices" without the quotes. That command should show your device if it shows as an MTP device whenever you open your "device manager" in windows. That's the same exact situation I was in. Download the codeworks from nvidia like I linked above. Hopefully then you should be able to recognize your device through the bootloader. If not DM me and I'll try to help you.

I'm having the exact problem as Lester. Tablet boots into bootloader but won't connect to computer. So I go into recovery mode and nothing works except apply update from adb. Which brings up the side load message that Lester quoted. And bootloader is showing "device=locked". I am attempting to fix this tablet for a friend that messed it up trying to flash a custom rom. Problem is he had no idea what he was doing and I'm not exactly sure what he did. I do however have a lot of experience with rooted android devices and flashing so any help would be GREATLY APPRECIATED!
---------- Post added at 05:59 PM ---------- Previous post was at 05:55 PM ----------
Also, I've already tried flashing stock rom back onto the tablet by applying update from sd card function in the recovery but when I try to do that the tablet for some reason can't mount the sd card.

rom fiend said:
Tablet boots into bootloader but won't connect to computer.
Click to expand...
Click to collapse
If you've got the device in bootloader then you need to use fastboot, not adb. Try the command 'fastboot devices' and see if the device id is listed. If so then grab a factory image, unzip it and use fastboot to flash the .img files using the commands 'fastboot flash system system.img'. Just make sure to match the partition names to the files.

Hello i have similar issue except when i try flash something i get this error ''remote: file write failed''
and i have to reboot into fastboot to get it flashing fully
but even though i managed to flash everything by rebooting when i boot system nothing shows up, i can just see the back light coming on and turning off after a while
Please help

Pixel 2 Magisk Bug won't take pin

Pixel 2 XL is soft bricked at the moment and I can't for the life of me think of what I need to do to recover it. I unlocked my bootloader and rooted when I switched to Pie, (I saw people we're already able to use Android pay on a rooted device again and I just couldn't help myself.) I installed twrp accidentally tried to flash TWRP not realizing I needed to temporary boot it and pushing the zip over erasing the recovery I proceeded to just fastboot it and carry on with the normal procedure with my phone. after getting Magisk installed I had my phone all set up until the next time I turned it on and back off again It said I forgot my PIN which I know I didn't I think this was because a glitch with smartlock I just setup so I go to my recovery and wipe the Dalvik cache, cache, Internal storage, and data and low and behold my phone bootloops never making past the final stage before it gets to the lockscreen. I go to Fastboot screen on my phone and my mac can't list my phone as a device in adb and now I am having issues getting back into recovery which I think might be because I am on the stock kernel my Fastboot screen on my phone says Product Name - Taimen, Variant - MSM USF:SAMSUNG(64gig) DDR:SAMSUNG, Bootloader version - TM220j, Baseband version - g899800253-1805232234, my Serial number, Serure boot - Yes, Device status - Unlocked, Vart console - Disabled, HW version - rev_10
I can't get it to stop bootlooping and just turn off.

bump

xda Zed said:
bump
Click to expand...
Click to collapse
Try flashing the stock boot.img with Fastboot. That might get you out of it. Since you did all the wiping I can't say for sure. However, when you were at the point where it wouldn't take your password, that's all that needed to be done. I ran into the same thing. It's a Magisk bug. Magisk gets flashed to the boot partition so flashing the factory boot.img will fix it. TWRP also gets flashed to the boot partition so if you flashed it too, flashing a factory boot image will get rid of that too. ADB won't see the phone while it's in fastboot mode. You need to use "fastboot devices". You can download a factory image if you don't have one and extract the boot.img from it. Put it in the folder your fastboot is in, and then open a command prompt (terminal? I'm not a MAC person) from that folder and type "fastboot flash boot boot.img" (without the quotes). Make sure you use download the factory image that's the same as what you currently have installed on the phone.

robocuff said:
Try flashing the stock boot.img with Fastboot. That might get you out of it. Since you did all the wiping I can't say for sure. However, when you were at the point where it wouldn't take your password, that's all that needed to be done. I ran into the same thing. It's a Magisk bug. Magisk gets flashed to the boot partition so flashing the factory boot.img will fix it. TWRP also gets flashed to the boot partition so if you flashed it too, flashing a factory boot image will get rid of that too. ADB won't see the phone while it's in fastboot mode. You need to use "fastboot devices". You can download a factory image if you don't have one and extract the boot.img from it. Put it in the folder your fastboot is in, and then open a command prompt (terminal? I'm not a MAC person) from that folder and type "fastboot flash boot boot.img" (without the quotes). Make sure you use download the factory image that's the same as what you currently have installed on the phone.
Click to expand...
Click to collapse
I stopped my endless bootloop! Now it says my device is corrupt and cannot be trusted and may not work properly when I tried to start it I couldn't get past the google screen. When I plug it into charge now it doesn't automatically going into a bootloop that can only be stoped by going into the fastboot mode or running out of battery, but the the charging symbol on the screen won't go away. I might have wiped system when I was in TWRP when I couldn't boot back after the first wipe. And I accidentally tried fastbooting Telstra img first. Anyway to get past this white Google screen? Also when I trey to go to recovery now it's the android laying on it's back with a red triangle and it says no command. Should I execute the flash-all script?

Downloaded the stock img files and ran the flash all .sh and now I am back in Android ready to mess something up again I could not thank you enough for your help I am so happy right now

xda Zed said:
Downloaded the stock img files and ran the flash all .sh and now I am back in Android ready to mess something up again I could not thank you enough for your help I am so happy right now
Click to expand...
Click to collapse
Glad to hear you got it working again. As for the recovery screen that say no command, that't the way it works with the stock recovery. When you see that screen, press and hold power and volume up. That will get you into recovery. If you happen to try rooting again and get stuck in a bootloop or some such thing, just flash the stock boot image.. That should get you going again.

Mi mix 3 Global ROM bootloop

I'll start by apologizing if this has been solved elsewhere I have searched but found no answers.
I have the global variant and was rooted with twrp. I wanted the ota update so I unrooted and updated. Today I had some time so I flashed twrp wiped and entered bootloop. I attempted a full factory reset through twrp but still bootlooped. I have fastboot rom and have attempted to use miflash to fix it but get the "cannot found lock.bat" error though when first starting miflash I get the "can't find flash script" error. The drivers are properly installed yet the error persists. I cannot get adb to sideload which is, I'm guessing because of the wipe removing debugging mode? Is there any way to get the ROM image to the phone(I tried adb push command but says no device. Yet flashing recovery works so I know it's connected and recognized) so I can flash it via TWRP or the stock recovery img to flash and work from there? I'm kind of at a loss here. Am I now the proud owner of a very neat paper weight? I seriously hope not as I'm not exactly made of money and I've only owned the phone for a couple months.
Any and all help is greatly appreciated.

Update
I have managed to get adb push to start sending global v10.2.2.0 to the root folder. I'm hoping this will allow me to flash from twrp.
Mota420 said:
I'll start by apologizing if this has been solved elsewhere I have searched but found no answers.
I have the global variant and was rooted with twrp. I wanted the ota update so I unrooted and updated. Today I had some time so I flashed twrp wiped and entered bootloop. I attempted a full factory reset through twrp but still bootlooped. I have fastboot rom and have attempted to use miflash to fix it but get the "cannot found lock.bat" error though when first starting miflash I get the "can't find flash script" error. The drivers are properly installed yet the error persists. I cannot get adb to sideload which is, I'm guessing because of the wipe removing debugging mode? Is there any way to get the ROM image to the phone(I tried adb push command but says no device. Yet flashing recovery works so I know it's connected and recognized) so I can flash it via TWRP or the stock recovery img to flash and work from there? I'm kind of at a loss here. Am I now the proud owner of a very neat paper weight? I seriously hope not as I'm not exactly made of money and I've only owned the phone for a couple months.
Any and all help is greatly appreciated.
Click to expand...
Click to collapse

Update 2 phone working but still confused.
Pushing the ROM via ADB did indeed allow me to flash from twrp and restore the phone. My question now is why did it happen? Is the new OTA MIUI 10.3... update incompatible with twrp or did something anomalous happen with the flash? I flashed exactly the same method I used with the 10.2.2 ROM a few weeks ago....

OTA's should only be used when completely stock! Even though you uninstalled root, there were still system modifications that more than likely caused your issues. The fastboot version of the firmware is different than the TWRP image. You can not flash a TWRP image via fastboot, hence the missing scripts and bat files. If you had actually downloaded the fastboot image, you would have had a flash_all.bat file that would have returned your device completely to stock with a single run of that file.

Thanks for the reply and information. I actually expected my issues to begin upon installing the ota update and was quite surprised that it updated without error. What confuses me is how flashing twrp after the update caused the issues. I went through the normal process when flashing twrp and still ended up bootlooped. I made the mistake of thinking boot.img was the old stock recovery i renamed when i first rooted and flashing that as recovery. Obviously this was not the recovery file but fastboot. It was then that panic mode kicked in and things went from bad to worse. I formatted planning to flash the stock rom via adb which didn't work. Given that I never touched the fastboot image on the phone I'm confused on how the bat files and scripts weren't found.
I'll admit I'm not extremely well versed in this area.
Is it possible that the ota update contained different bat files and scripts than the previous rom had? Which would cause miflash to not recognize them when attempting to flash an older rom? I'm sorry if my questions are ignorant lol. I'm a process guy and a troubleshooter by nature which means even though I've resolved the issue, I need to figure out what caused it.
Would flashing fastboot to the phone as the recovery image have screwed up the bat and scripts? Having two instances of boot.img on the partition messed it up maybe? Was it the formatting even though I was still able to boot into fastboot after? Or was it something that happened during the unrooting and updating that messed it up and it didn't manifest until I flashed twrp? Like I said the update worked fine and the phone was fully functional until I tried to reroot.
Thanks again for taking the time to help. It's definitely appreciated.

Mota420 said:
Thanks for the reply and information. I actually expected my issues to begin upon installing the ota update and was quite surprised that it updated without error. What confuses me is how flashing twrp after the update caused the issues. I went through the normal process when flashing twrp and still ended up bootlooped. I made the mistake of thinking boot.img was the old stock recovery i renamed when i first rooted and flashing that as recovery. Obviously this was not the recovery file but fastboot. It was then that panic mode kicked in and things went from bad to worse. I formatted planning to flash the stock rom via adb which didn't work. Given that I never touched the fastboot image on the phone I'm confused on how the bat files and scripts weren't found.
I'll admit I'm not extremely well versed in this area.
Is it possible that the ota update contained different bat files and scripts than the previous rom had? Which would cause miflash to not recognize them when attempting to flash an older rom? I'm sorry if my questions are ignorant lol. I'm a process guy and a troubleshooter by nature which means even though I've resolved the issue, I need to figure out what caused it.
Would flashing fastboot to the phone as the recovery image have screwed up the bat and scripts? Having two instances of boot.img on the partition messed it up maybe? Was it the formatting even though I was still able to boot into fastboot after? Or was it something that happened during the unrooting and updating that messed it up and it didn't manifest until I flashed twrp? Like I said the update worked fine and the phone was fully functional until I tried to reroot.
Thanks again for taking the time to help. It's definitely appreciated.
Click to expand...
Click to collapse
OTA's are not a complete image. It is a partial update that only replaces what it has to replace. If MiFlash dis not recognize the image, it was either the wrong image or a corrupt image.
Sometimes updates to the system and recovery partitions fix exploits that things like root and TWRP take advantage of.
Fastboot isn't something you flash to the phone. It is a command line used to flash a dull factory image to the device properly. You do not need MiFlash to flash a fastboot factory image. All you do is extract the full image to your ADB folder unless it is system wide, boot your device into the bootloader, connect ir to your PC, and run the flash_all.bat command contained in the folder you extracted. A command prompt window will open, everything will complete after about a few minutes the window will close, and your phone will reboot.

So the "fastboot" rom is a rom designed to be flashed using fastboot? The miflash error was given because the rom I was trying to flash was corrupted. That makes sense as I'd never known of a fastboot rom before. But it has been a few years since I rooted and romd my phone. I always did the typical flash from the rom image from twrp. I'm still not sure how I got myself in a boot loop unless when I wiped after flashing twrp I accidentally selected another option that erased more than I wanted.. Which makes perfect sense. I knew it had to be an ID10T error lol.
Thanks for the explanation.

Just bricked

Okay so yesterday I decided to finally try to install TWRP to flash a custom rom on the system, but never thought it would give so much headache. My drivers were bad, the system locked and android 11 updating making the phone all sorts of bugs, I was anxious to get rid of it, and I did somehow. I was unable to flash TWRP into the recovery as the system partition type is different than usual for it seems, but the recovery partition was all weird, "no command" was stuck in the screen even after a hard reset through there. So I got Magisk and got Root and used Smart Flash to install TWRP through the running system and it landed successful. But when going to the recovery the TWRP screen was flickering, but I could send ADB commands yet and boot normally, I just couldn't access the recovery functions yet. So I flashed a different version of the TWRP with the IMG and the zip folder and nothing worked then I realized that maybe I should erase the partition before flashing it and then the murder. I found a tutorial on erasing stuff, but the whole process cost me more than twelve hours as I messed with so many things and was kinda learning the hows and dos.
But then I saw the command "fastboot erase system -w" that was a shortcut for all cleanup processes and I was wanting to wipe it again even to recover my google backup and be able to use my messenger apps. But it did erase, of course, the whole system and everything, simply destroying everything, but yet stuck in the fastboot screen. What I did? Well, I downloaded the TGRZ of an older version of xiaomi mi a3 firmware, the android 10, as I was tired and thought that maybe if I downgraded it I would get my phone to get rid of android 11 bugs and sleep for good till tomorrow, that is today. I ran the script to wipe anything and install the system over it and it did successfully, then the message "successfully installed, press any key to finish" but then the prompt closed and the phone tried to reboot but fell into a hard brick. The computer recognizes the device as the name "QUSB_BULK_CID:0411_SN:EFCF04FD" and the hardware ID "USB\VID_05C6&PID_9008" matches the original.
So is there anything I could do yet? Phone warranty ended in january and that's why I tried that process, it is any worth?

BillyWroth said:
Okay so yesterday I decided to finally try to install TWRP to flash a custom rom on the system, but never thought it would give so much headache. My drivers were bad, the system locked and android 11 updating making the phone all sorts of bugs, I was anxious to get rid of it, and I did somehow. I was unable to flash TWRP into the recovery as the system partition type is different than usual for it seems, but the recovery partition was all weird, "no command" was stuck in the screen even after a hard reset through there. So I got Magisk and got Root and used Smart Flash to install TWRP through the running system and it landed successful. But when going to the recovery the TWRP screen was flickering, but I could send ADB commands yet and boot normally, I just couldn't access the recovery functions yet. So I flashed a different version of the TWRP with the IMG and the zip folder and nothing worked then I realized that maybe I should erase the partition before flashing it and then the murder. I found a tutorial on erasing stuff, but the whole process cost me more than twelve hours as I messed with so many things and was kinda learning the hows and dos.
But then I saw the command "fastboot erase system -w" that was a shortcut for all cleanup processes and I was wanting to wipe it again even to recover my google backup and be able to use my messenger apps. But it did erase, of course, the whole system and everything, simply destroying everything, but yet stuck in the fastboot screen. What I did? Well, I downloaded the TGRZ of an older version of xiaomi mi a3 firmware, the android 10, as I was tired and thought that maybe if I downgraded it I would get my phone to get rid of android 11 bugs and sleep for good till tomorrow, that is today. I ran the script to wipe anything and install the system over it and it did successfully, then the message "successfully installed, press any key to finish" but then the prompt closed and the phone tried to reboot but fell into a hard brick. The computer recognizes the device as the name "QUSB_BULK_CID:0411_SN:EFCF04FD" and the hardware ID "USB\VID_05C6&PID_9008" matches the original.
So is there anything I could do yet? Phone warranty ended in january and that's why I tried that process, it is any worth?
Click to expand...
Click to collapse
You should never try to install software for another board (mi mix 3 global is codenamed "perseus")...
If you are unable to reach fastboot and recovery, you may refer to this, since it sounds like your phone is in EDL mode:
Reboot to EDL mode from FASTBOOT!
Reboot to EDL mode from FASTBOOT! No more Test Point Method needed Technical Details: Redmi Note 3 support rebooting to EDL in Android Bootloader aboot module (the "reboot-edl" command) but fastboot utility doesn't recognize "reboot-edl" in the...
forum.xda-developers.com
I never encountered this issue so only do this if you're absolutely sure you have no other means of flashing anything on it (i.e. through fastboot), and use the appropriate firmware at all times for your specific model

CriGiu said:
You should never try to install software for another board (mi mix 3 global is codenamed "perseus")...
If you are unable to reach fastboot and recovery, you may refer to this, since it sounds like your phone is in EDL mode:
Reboot to EDL mode from FASTBOOT!
Reboot to EDL mode from FASTBOOT! No more Test Point Method needed Technical Details: Redmi Note 3 support rebooting to EDL in Android Bootloader aboot module (the "reboot-edl" command) but fastboot utility doesn't recognize "reboot-edl" in the...
forum.xda-developers.com
I never encountered this issue so only do this if you're absolutely sure you have no other means of flashing anything on it (i.e. through fastboot), and use the appropriate firmware at all times for your specific model
Click to expand...
Click to collapse
well it seems I recovered it back, I bricked it and somehow it just got into EDL mode without cable or opening it up. So I found a tutorial back on reddit showing how use GFIL to install the stock rom back. I used android 10 stock rom before bricking it, but as I just flashed everything on empty partitions it didn't work, it seems that the Qualcomm setup needs some kind of previous work to set everything up. Anyways I managed to boot it, but now I'm aware that I should use Lineage recovery instead of TWRP as Mi A3 support is lacking, that's why after installing it I got it flickering (no compatible version with the latest Android 11 firmware).

BillyWroth said:
well it seems I recovered it back, I bricked it and somehow it just got into EDL mode without cable or opening it up. So I found a tutorial back on reddit showing how use GFIL to install the stock rom back. I used android 10 stock rom before bricking it, but as I just flashed everything on empty partitions it didn't work, it seems that the Qualcomm setup needs some kind of previous work to set everything up. Anyways I managed to boot it, but now I'm aware that I should use Lineage recovery instead of TWRP as Mi A3 support is lacking, that's why after installing it I got it flickering (no compatible version with the latest Android 11 firmware).
Click to expand...
Click to collapse
hello, im having maybe a similiar case with my phone (in this case its a MI A3) i installed "succefully" evolution x 6.3 on my phone and everthing was ok with a few bugs, the only problem was that mi cannot connect to internet, so i decided to restart the phone and now my phone just don't turn on, the power button don't respond and i cannot start up my phone and its just a black screen, if u remeber ¿can u pass the tutorial that u saw on reddit? maybe it can help me