Database Develop

Softbricked Phone Battery Too Low for RSD Lite, Won't Charge

I have searched around for a couple days, but there doesn't seem to be anyone who has posted about this issue with a Droid 4. So here is what I have.
I rooted my Droid 4 using the RazrBlade method without incident. Afterwards I wanted to flash Cyanogenmod onto it, but did not have a custom recovery like ClockworkMod or TWRP set up yet. So, looking around led me to download the latest safestrap .apk so I would have a recovery capable of flashing Cyanogenmod. The latest version of safestrap would not work for me because of a parsing error, I looked around and found that some people were having the same issue and fixed it by downloading an earlier version of safestrap to their Droid 4. So, I found a safestrap 2.x.x version, downloaded that and followed the directions accordingly. I now had a functional (to my knowledge) recovery that would allow me to flash CyanogenMod. So I downloaded the .zip file from the CyanogenMod website for Droid 4, and attempted to flash it using the recovery that safestrap 2.x.x set up.
Everything looked okay for the install, no errors were reported, phone was at least at 80% battery, but once the phone rebooted, after the Motorola spash screen, there was a blank screen. The phone is on, evidenced by the backlight being visibly seen, but otherwise there is no evidence that it is trying to boot up any ROM. There is no loop whatsoever, just a blank screen.
First, I thought it was a bad install, afterall, it wouldn't be the first time. But when I turned it off (only possible via PWR&Vol.- button combo) it did not give the option to go into the safestrap recovery mode upon booting back up.
But I am not without a working knowledge of how to pull a phone out of a softbrick state, so I quickly connected my phone to a computer set up to take adb commands and tried to reboot my phone into the recovery mode. I connected my phone to my PC, left it on the blank screen mode and typed the adb command [adb devices] to confirm that it was acknowledged by my computer, it was, and attempted to reboot it into the recovery mode with the command [fastboot reboot-recovery]. It responded by rebooting, but led back to the backlit blank screen. I thought that this might be an issue with the wires or drivers or something to that effect, so I reattempted with a usb cord that was supplied by Motorola, and reinstalled all the appropriate drivers. Nothing worked, so I moved everything to a new computer freshly set up to take adb commands. I connected my phone and it was immediately recognized by the new computer, but it still would not respond to any adb commands. Attempting to reboot into recovery yields a blank screen still.
By this point I do not care if my phone is rooted or if I have to restore it to factory settings. So I look up solutions that flash it back to the stock 4.1.2 ROM. I find one that does this, but it requires that I am in AP Fastboot Flash Mode. I put it in the aforementioned mode, but it is not recognized by the adb terminal. It is listed as an adb device if it is in "blank screen mode" but not while in AP Fastboot Flash Mode. Shortly after this the battery is too low to program anyway, so I turn it off and set it to charge. But instead of a "battery charging" screen, I am greeted with the Motorola splash screen for as long as the phone is connected to the charger. Every time the phone is removed from the charger it, immediately and without pause, loses power and cannot be powered on until placed back on a charger.
Looking around some more, because I am increasingly desperate to solve this problem, I find something called RSD Lite, which will reflash the stock firmware to the phone and it will behave as if it was reset to factory settings. I plug the phone up to the computer, it powers on, I boot it up to the AP Fastboot Flash Mode and RSD Lite sees the phone as a fastboot device, and is ready and willing to fix it, but the battery is too low to program.
The battery is incapable of being charged by a wall outlet by any means that I have tried (will list below), BUT... If I connect my phone to a computer, and after the phone is connected, turn the phone off, a little green LED light appears at the top left and stays for at least 15 minutes until the Motorola splash logo appears and my phone connects to the computer. The phone recieves power in this mode evidenced by the fact that it does not instantly power down after it is disconnected from the power source. But at this point in time, the battery does not charge enough to cause a change in the AP Fastboot Flash Mode to allow it to be OK to Program.
Here is some misc info that might be needed:
Modes that I have access to
1.) Motorola Splash Screen + "Blank Screen Mode": This mode connects to the computer and is registered by the device number XT894. After the Moto Splash Screen there is a backlit blank screen I call "Blank Screen Mode". This mode is recognized by adb commands but not by RSD Lite. Any time an adb command is used apart from rebooting, command prompt says <waiting for device> and the device does not respond.
2.) Motorola Splash Screen Only: This mode is only accessible by connecting the phone to a wall outlet. This mode does not charge the phone and if the phone does not have any power otherwise, will power down without warning upon being disconnected from the power source.
3.) Boot Mode Selection Menu: This mode provides various options that appear to do nothing. The "Recovery" option that is supposed to bring me to the default android recovery mode instead brings me to the Motorola Boot Logo and then to a green android laying down with a red triangle over it (with an exclamation point). I am able to access AP Fastboot Flash Mode from here.
4.) AP Fastboot Flash Mode: In this mode, the device is recognized by the computer as an adb fastboot device (not as an XT894 device). It does not respond to adb commands, and the adb terminal does not acknowledge the phone in this mode. RSD Lite does acknowledge the phone in this mode, but trying to begin the process to reflash the stock firmware causes the "Low Battery/ No Program" text on the phone to flicker and result in a failure in the RSD Lite program. It lists the reason as: Phone return(ed) Fail.
5.) Computer Charging Mode: When connected to a computer, and immidiately powered off, a green LED light turns on. After leaving the phone for some time, the phone can be disconnected and stands on it's own power without needing to be connected to a power source to remain on. In this mode, the screen is not on, and the phone is not recognized by the computer at all.
Methods I Have Attempted to Use to Charge Phone
1.) Plugging Moto Stock USB charging cable to computer and leaving it: This causes the 1st mode listed above to occur, and no charge is held. After 10 minutes of "charging" upon disconnecting cable, phone shuts off abruptly, and without any warning.
2.) Plugging Moto Stock USB into USB to Wall Outlet Plug: This causes 2nd Mode listed with similar results to above.
3.) Plugging Motorola Wall Outlet Charging Cable to Phone: See above
4.) ALL Above Methods + Boot Mode Selection Menu BD Tools Mode: I read that if you were to connect your phone to a wall outlet after booting it up into the Boot Mode Selection Menu, and selecting BD Tools, the phone would boot up to the Motorola Boot Logo screen, then show a battery charging similarly to how one does if you charge your phone after it shuts down from having 0% Battery. This was not the result I received. Similar results to #1
I apologize if there is some blatant simple answer here, but I have looked everywhere to find a solution to no avail. I included everything that occured between then and now so as to facilitate this process, and hope that I am not stepping on any toes with the wall of text I just posted.
Thanks in advance, if more info is needed (or if the post needs to be formatted in an easier to read way) just say so.

Sounds like you will need a motorola factory cable. I think that's what they are called. It provides power directly to the phone allowing you to fastboot. I know you can find them on ebay. I believe team black hat also sells an adapter to turn your regular OEM cable into a factory cable.
Your other alternative would be to sacrafice a usb cable and attach to the battery terminals directly to charge the battery. If you google it you should be able to find directions for how to do this. I believe someone posted a how to on youtube for the razr which should give you a good idea of what you would be getting into.
Good luck!
Droid 4 - Avatar

Fixed It
Thanks for the help.
I didn't feel like paying $12 dollars and waiting several days to purchase one of those special factory cables, so I ended up taking a non-USB charger, spicing it, and hooking it directly to the battery terminals like you said. After I did that, it automatically said that it was "OK to Program".
The only problem I had was that RSD Lite wasn't able to fix it, I had to download some other app that ran things through command prompt while the device was in AP Fastboot mode. But the end result was the same.
I found out that the problem that caused all this was me not flashing the CyanogenMod firmware into ROM Slot-1 while in the safestrap recovery mode. I flashed it to the "Stock" ROM Slot instead.
Thanks again for the help, I learned a lot, and I am glad I didn't have to shell out money for a new phone. :laugh:

[Q] Xperia T LT30at is stuck at Sony screen.[SOLVED]

The problem.
When I boot the device it just stays at the Sony screen and does not progress any further. I am still able to turn off the device by holding the power button and the volume up button, I can reset it by holding the button longer waiting for the vibration, and I can hard reset by waiting till the three vibrations.
What I was doing up to the point it happened.
I was trying to get a custom ROM on my device, I had it previously rooted so I thought I would go further. I installed CWM on my phone I wiped data, cache, and dalvick then I went to install the ROM from SD card. During the attempt at installation I got some symlink errors with a status of 7. Not sure what to do turned off the device when I decided to put back its previous I turned it back on and arrived at the problem.
What I have done to try and fix it.
I have done the soft and hard resets, I tried using the PC companions repair tool. When it asks me to turn the device off hold down the power button then plug in the device nothing happens(I have tried this several times.) I downloaded the flashtool and the correct ftf and tried using that, but it doesn't detect my device when I hold down the volume button and plug it in. So it seems that the flashboot is not working on my phone.
Any suggestions on what to try would be much appreciated and thanks in advanced.

tabersays said:
The problem.
When I boot the device it just stays at the Sony screen and does not progress any further. I am still able to turn off the device by holding the power button and the volume up button, I can reset it by holding the button longer waiting for the vibration, and I can hard reset by waiting till the three vibrations.
What I was doing up to the point it happened.
I was trying to get a custom ROM on my device, I had it previously rooted so I thought I would go further. I installed CWM on my phone I wiped data, cache, and dalvick then I went to install the ROM from SD card. During the attempt at installation I got some symlink errors with a status of 7. Not sure what to do turned off the device when I decided to put back its previous I turned it back on and arrived at the problem.
What I have done to try and fix it.
I have done the soft and hard resets, I tried using the PC companions repair tool. When it asks me to turn the device off hold down the power button then plug in the device nothing happens(I have tried this several times.) I downloaded the flashtool and the correct ftf and tried using that, but it doesn't detect my device when I hold down the volume button and plug it in. So it seems that the flashboot is not working on my phone.
Any suggestions on what to try would be much appreciated and thanks in advanced.
Click to expand...
Click to collapse
You probably didn't install the ADB drivers. Install them from the Flashtool folder (use the ones for TX) and then try flashing your stock FTF again. Remember to put the device into Flashmode.
Basically what happened was that while flashing your ROM the script that flashes everything deletes everything from the /system partition, then you got an error and the installation was incomplete, therefore there is no proper system to boot into. You could have easily avoided what happened by flashing a different ROM had you not powered off.

Antiga Prime said:
You probably didn't install the ADB drivers. Install them from the Flashtool folder (use the ones for TX) and then try flashing your stock FTF again. Remember to put the device into Flashmode.
Basically what happened was that while flashing your ROM the script that flashes everything deletes everything from the /system partition, then you got an error and the installation was incomplete, therefore there is no proper system to boot into. You could have easily avoided what happened by flashing a different ROM had you not powered off.
Click to expand...
Click to collapse
Thank you for response, I went and used the Flashtool-driver.exe and installed the Flashmode drivers, Fastboot drivers and the TX drivers. But it does not seem to have changed anything. To enter flash mode on the phone one has to hold down the volume down button while plugging the phone into the usb when it is powered off, right? Flash tool just sits at the instruction animation titled Wait for Flashmode. When I try to enter flashmode I do not get a response from either the program or the phone. Any more suggestions would be welcomed.
Thank you for taking the time to help.

tabersays said:
To enter flash mode on the phone one has to hold down the volume down button while plugging the phone into the usb when it is powered off, right? Flash tool just sits at the instruction animation titled Wait for Flashmode. When I try to enter flashmode I do not get a response from either the program or the phone. Any more suggestions would be welcomed.
Thank you for taking the time to help.
Click to expand...
Click to collapse
Yes, that is how you enter flashmode. Turn off phone, and keep volume down button pressed while you connect the USB cable; the LED light should turn on with a green light. If you're phone is not entering Flashmode, then you might have a faulty USB cable, or there might be problems with your USB ports, either on your computer or your phone (try with different cables/computers).
Also, check your Device Manager (while phone is connected) to make sure the drivers are properly installed. If you have Windows 8, you should have had to turn of Driver Signature Checking in order for the drivers to install properly.

Antiga Prime said:
Also, check your Device Manager (while phone is connected) to make sure the drivers are properly installed. If you have Windows 8, you should have had to turn of Driver Signature Checking in order for the drivers to install properly.
Click to expand...
Click to collapse
Yes, it's better to work on Windows 7 or lower....

Antiga Prime said:
Yes, that is how you enter flashmode. Turn off phone, and keep volume down button pressed while you connect the USB cable; the LED light should turn on with a green light. If you're phone is not entering Flashmode, then you might have a faulty USB cable, or there might be problems with your USB ports, either on your computer or your phone (try with different cables/computers).
Also, check your Device Manager (while phone is connected) to make sure the drivers are properly installed. If you have Windows 8, you should have had to turn of Driver Signature Checking in order for the drivers to install properly.
Click to expand...
Click to collapse
Yeah I turned off the Driver signature checking on my computer when I did it. I'll go buy a new cable and try a friends windows 7 computer. Hopefully there is nothing wrong with the USB port in my phone. Thank you for your help I'll let you know how it goes.

Thank you everybody for your support. My phone is now working. After my phones battery died I was able to get it charging, when it had enough energy it booted itself to the Sony screen so I turned it off and grabbed my new micro USB cable and was able to get it into flash mode. Everything is now working great. I wish a special thanks to Antiga Prime for taking the time to help me.

Have I hard-bricked my device?

Please excuse me if I'm repeating a prior question but it seems far too specific to trawl through pages of related threads to make sure.
I decided I was going to sit down and root my Xperia Z1....
Steps:
1. I installed ADB and Fastboot via the latest windows Android SDK (r23-.0.2), in fact I had to source a sony version of the fastboot driver in order to get it working but once I'd done that all went ahead as planned.
2. Generally followed this guide (wont let me post a link but google "honami cyanogenmod" and it's the 2nd result)
3. All was going swimmingly, I entered fastboot mode absolutely fine, flashed CWM using fastboot which all loaded up absolutely fine.
3. At this stage ADB was not picking up my device at all, tried different cables, ports, all of the usual. What I didn't do was make a backup, and then I wiped all of the things that it's possible to wipe thinking to myself that I was going to get Cyanogenmod on there so all would be fine...
4. Finally I (quite stupidly) restored from memory card (which had already been wiped) from inside CWM, the device restarted and now I am getting no response AT ALL.
5. Sometimes it will load the Sony 'splash' logo that first appears but sometimes not, when plugged in the device is recognised and ADB actually sees the device but lists it as offline... Interestingly at this stage windows device installer actually installs Sony ADB driver for me automatically.
6. All I'm getting at the moment is a red flashing LED although when I plug in via USB the device is again recognised when I type adb devices but again is offline...
If any more information is needed please, I will be more than happy to give a quick reply.
Thank you in advance

JJrmc said:
I decided I was going to sit down and root my Xperia Z1....
Steps:
1. I installed ADB and Fastboot via the latest windows Android SDK (r23-.0.2), in fact I had to source a sony version of the fastboot driver in order to get it working but once I'd done that all went ahead as planned.
2. Generally followed this guide (wont let me post a link but google "honami cyanogenmod" and it's the 2nd result)
Click to expand...
Click to collapse
Were you trying to root your phone or install cyanogenmod? You followed a guide to install cyanogenmod on xperia Z1.

AkiraProject said:
Were you trying to root your phone or install cyanogenmod? You followed a guide to install cyanogenmod on xperia Z1.
Click to expand...
Click to collapse
I was trying to end up with a rooted device running Cyanogenmod, I've been putting it off and off looking into the whole rooting scene and mistakenly dived in a little too quick without knowing what I was doing.

after that you move cm-11-20141112-SNAPSHOT-M12-honami.zip to your sd card. Now you have flashed boot.img you can't move zip to your sd card using z1 you had to do that before using fastboot. use some sd card adapter and do it. then put the sd card back in your phone. turn it on then enter the cwm recovery pressing Vol+ for a few seconds when the sony logo shows up. select full wipe data. then install from zip. choose cm-11-20141112-SNAPSHOT-M12-honami.zip. reboot. ADB won't work until you have installed cyanogenmod zip. You have only installed cyanogenmod kernel and custom recovery when you flashed the boot.img.

AkiraProject said:
after that you move cm-11-20141112-SNAPSHOT-M12-honami.zip to your sd card. Now you have flashed boot.img you can't move zip to your sd card using z1 you had to do that before using fastboot. use some sd card adapter and do it. then put the sd card back in your phone. turn it on then enter the cwm recovery pressing Vol+ for a few seconds when the sony logo shows up. select full wipe data. then install from zip. choose cm-11-20141112-SNAPSHOT-M12-honami.zip. reboot. ADB won't work until you have installed cyanogenmod zip. You have only installed cyanogenmod kernel and custom recovery when you flashed the boot.img.
Click to expand...
Click to collapse
Firstly AkiraProject thank you for your time on this.
I do realise that in my stupidity I could have loaded the cm-11-20141112-SNAPSHOT-M12-honami.zip to my SD card (if I'd had one or waited and gotten one).
What I did however was wipe everything I possibly could, and then hit restore from sdcard/0/ I believe - it may have been a different directory.
I believe what I have done is restored to a blank image......
WHen not plugged into usb I get a red blinking LED when just pressing the power button once.
When holding volume-up + Power the phone vibrates as if it is trying to boot but is unable to
If I leave it plugged into USB AND then press , the device shows the sony Logo and then proceeds to display a backlit but plain black screen, Sony PC Companion recognises the device as connected but is unable to interact with it. The output of "adb devices" shows my device but says "unauthorized" and windows is attempting to install MTB driver....
The behaviour doesnt seem to be quite the same every time.
I believe the device is soft bricked.... is this likely to be a case of a wiped partition table? Or at least loss of the boot partition?
If I leave the device plugged in via USB it periodically reboots itself, shows the Sony logo, remains on a bank screen then shuts itself down.
Shows in device manager as "USB Input Device" on win 7 x64 pro
Thanks in advance

Pretty certain it's not hard bricked, there will be instructions here you can follow:
http://forum.xda-developers.com/showthread.php?t=2574764
Sent from my C6903 using XDA mobile app

D33KK said:
Pretty certain it's not hard bricked, there will be instructions here you can follow:
http://forum.xda-developers.com/showthread.php?t=2574764
Sent from my C6903 using XDA mobile app
Click to expand...
Click to collapse
I have done quite a lot of reading etc on the subject....
according to This thread, Sony Xperias have the bootloader in non-writable mask ROM... so you should always be able to access Fastboot or Flash Mode?
The problem I am having is that I don't seem to be able to activate EITHER Fastboot OR Flash mode in order to flash some new firmware onto my device....
My device is recognized as a "USB Input Device" on Device Manager and windows tries to install MTP driver. I'm going to have a go at the process with a fresh install of windows 7 x64 and 'windows auto-install drivers' turned off.
What is the maximum damage I could have done here?
Thanks

Update
Hard reset (red button inside of the sim-card slot) resets the phone with three vibrates and it restarts.
The phone powers on and displays Sony splash screen and then displays a back-lit black screen.
The phone gets much hotter than normal and powers on to the blank back-lit screen when on charge.
I have NO ACCESS to flash mode or fast boot. Any combination of buttons leads to the same outcome: single vibrate, red LED and the phone shows the Sony splash screen then blank screen, as if the button combinations are just ignored...
Flashtool DOES NOT recognize the device, although it is recognized as C6903 in device manager (I have Sony adb driver installed and have disabled the MTP driver that windows recommends).
Flashtool gives me the red error text about making sure drivers are installed and making sure the device isn't in MTP mode.
I'm at an absolute loss as to what to try next, can somebody shed any light on this? There are plenty of guides but they all seem to rely on EITHER fastboot or flash mode and I can access neither although the phone powers on!
Thanks in advance!

Maybe the partition was corrupted when you flash "blank" image..........
So....JTAG....or send to Sony service....

Shutdown with power+vol up (will vibrate thrice) and see if it doesn't turn on automatically.
If it didn't turn on now check your task manager on windows, go to process tab, kill adb.exe (every adb.exe)
Back on phone connect usb holding down the vol down button (phone have to be off before you connect usb), if green led turns on and doesn't turn off you are on flashmode.
Check on flashtool or flashtool64 (for 64bits) and see if flashtool detects your device. If it detects and recognizes your phone flash the FTF for your device and let it do its job.
As you messed the phone Sony will charge for repairs.

[Q] XPERIA SP CAN'T DETECT ANY USB (PC or WALL CHARGER)

Good evening everyone!
I need help so bad, so urgent!
It was happen when i try to install TWRP on my SONY Xperia SP using an amazing stupid way, using flash boot command coz i cant install twrp using flash recovery command, but i dont know why that fastboot take so long time and just display <waiting for device>. So i decided to remove my USB and plug it once again. Suddenly, my laptop show a notif. "USB not recognized" and the blue LED is gone, then SONY logo appear and start to charging and u can hear connect-"Not recognized"-and disconnect sounds from laptop. But, when the display turn off, it's turn on again, and 5 seconds later u can hear disconnected sounds, then charging stopped. Few later, the logo come again and charging again, and the same thing happend. When i try to charge from the wall charger, it can charging normally, but I CAN'T TURN THE PHONE ON. It's like the power button has been disabled. So i unplug the charger and turn my XSP on, it can boot normally. But when i try to connect to charger, it wont charging. So on my laptop, even my laptop didnt notice any USB, and my XSP didn't show any LED.
Help me to fix this. I can't charge my phone except to turn it off T_T. Pls give me a way out T_T.
Status: Installed AOSP Oreo 8.0.0 huashan, not rooted and no cwm/twrp (this is what i need to install, so i can root my phone, the latest cwm i installed gone after flashing AOSP ROM), cant connect to any USB even in fastboot mode (i've installed the driver).

seems like you got dust in your usb port , it happened to me once , i freaked out real bad. just try clearing it with some needle or stuff , also you might wanna use emma to revert your phone back to its original stock firmware.

AsadXperia said:
seems like you got dust in your usb port , it happened to me once , i freaked out real bad. just try clearing it with some needle or stuff , also you might wanna use emma to revert your phone back to its original stock firmware.
Click to expand...
Click to collapse
what's emma? how to use that?

it's a sony developer tool. You can use it to install original os on your phone , you just need a pc and internet connection , here
https://talk.sonymobile.com/t5/Andr...ony-Flash-tool-for-Xperia-devices/td-p/307318
Also , just save the customization file and delete the rest , download emma sony flash tool from google ( latest version ) copy the customization file after installing it.
After it completes install , run it and wait for it to open , it may take some time during its first run.
Now plug in ur phone , while holding volume down button , you should see green light on bottom , that indicates you're on recovery mode or flashmode. The Emma tool will detect device and start installing original firmware on it.

AsadXperia said:
it's a sony developer tool. You can use it to install original os on your phone , you just need a pc and internet connection , here
Also , just save the customization file and delete the rest , download emma sony flash tool from google ( latest version ) copy the customization file after installing it.
After it completes install , run it and wait for it to open , it may take some time during its first run.
Now plug in ur phone , while holding volume down button , you should see green light on bottom , that indicates you're on recovery mode or flashmode. The Emma tool will detect device and start installing original firmware on it.
Click to expand...
Click to collapse
that was my problem. when i plug my phone in fastboot or bootloader, pc wont detect it, it says "USB not recognized". also when my phone is standby, it wont detect any usb i plugged in, wall charger or usb pc.
i've installed latest driver for XSP, and USB debugging's on.

have you read my first comment? , clear your phone's usb slot and then try replugging , if it fails try it on a different computer , the problems usually with windows 10 as it loses recognizing devices after some fail attempts.

(FIX)Press any key to shutdown, phone dead, fastboot not working, +2 days without it

I was texting, using xiaomi.eu rom stable lastest, stock kernel, no root.
Gallery stopped, then camera, whatsapp closed, instagram gave black screen...
I turned the phone off and then turned it on, bootlop, so I went to TWRP and wiped all partitions and also formatted data. I also did a selinux fix contents or something like that, I flashed another recovery, a custom one via zip and then phone died, mi logo and rebooted, only fastboot available.
When I use fastboot and connect it to my pc it gets detected as kedacom adb automatically, I tried lots of drivers, uninstalling any driver and installing google drivers and lots of things, got ADB and fastboot 15s installed, I also tried different cable, other pc, 2.0 ports, 3.0 ports, other Windows, virtualbox, doing fastboot flash recovery twrp.img with waiting device and then connecting...everything I've seen and know. I bricked my phone and other phones more than one time, and managed with almost no issue to fix it, but now i'm just lost.
I get Press any key to shutdown, on the left top corner of the phone, I do the following:
fastboot devices(gets detected by fastboot)
fastboot flash recovery twrp.img(instantly I get press any key to shutdown)
I can't do anything, it's dead, any tips or something? Thanks guys.
I needed 13h in total to fix it, so I wanna share what to do, the fix is in the post, scroll down a little bit and you'll see it. Hope it worked.

I fixed it finally, if anyone wants info, pm or reply

I need to tell this honestly, you should share what you did and how you did, so you can help anyone anytime if they encounter this problem anyhow. They can use this thread as a guide and don’t need to start a new topic and we save the forum from flood messages and topics. Thanks in advance.

THE FIX
It was very hard and tricky, but possible, you'll need a computer, usb data transfer cable, type c to usb, and a usb mouse, you'll need your device to be unlocked first, if it's not unlocked, I can't help you.
I used Tool All In One by Mauronofrio, installed drivers and with phone in fastboot connected it, if I press check, it will reboot and fail, you have to go to recovery flasher, if no recoveries are available, then download and put it on the same folder where the tool is. Go to recovery flasher(not zip one) select it, I recommend mauronofrio one, the lastest, and then select when going to flash flash and boot, it should be black screen with waiting devices and the phone with the press any key thing, then just disconnect the phone from the cable, restart it to fastboot and connect it, it should boot, you'll have mi logo or fastboot for a minute or 2 and then it will boot to twrp, but you may not have your touch working, just connect the type c to usb adapter and use a mouse, you should be able to use it, go to wipe, wipe all partitions, then format data and connect the phone back to computer, if it does get detected, you'll see the phone in file explorer, so you'll be able to move any files, move any rom to internal storage, use then the usb adapter and with the mouse, flash the rom, reboot and everything will work.
IF IT DOES NOT GET DETECTED, Go to recovery flasher(not zip one) select it, I recommend mauronofrio one, the lastest, and then select when going to flash flash and boot, it should be black screen with waiting devices and the phone with the press any key thing, then just disconnect the phone from the cable, restart it to fastboot and connect it, it should boot, you'll have mi logo or fastboot for a minute or 2 and then it will boot to twrp, but you may not have your touch working, just connect the type c to usb adapter and use a mouse, you should be able to use it, partitions allready wiped, so just put the rom file if it was deleted and flashbe sure that under partitions is MTP enabled, if it is and it still does not work, just go to reboot and select recovery, wait for it to boot to recovery. If it goes to fastboot and does not work, When booted, your twrp touch will be working again, if not, just flash another one.

There are other options, trying usb hub, 2.0 ports, a non amd pc, uninstall drivers and install google ones with internet disabled all time when flashing... But this is the one that worked, if anyone needs help, I can help you with Discord or pm.

Thanks for sharing the fix.