Database Users

XDA Mini S Screen problem - Photo's now available

I've got a problem with my XDA Mini S. It's been sitting in a box in my shed for about a year, before I got it out yesterday to have a play around with it, and possibly try some software I found on it.
I put my sim card in, plugged it in to charge, and turned it on. It worked absolutely fine.
I haven't done anything with it yet, but I've turned it on now, and the colours are messed up on the screen. For example there is a red hue over the today screen, and on certain screens (like in bootloader mode) the colours appear to be inverted (I will post pictures later if needed).
I've tried reformatting the device, but this has not fixed the problem. I thought I would try reflashing the rom on it. I used to have the original o2 rom on my old laptop, but lost that when I had to reload windows.
I downloaded the original rom from here, along with the Rom Update Utility, and attempted to reflash it. It gets as far as 'verifying the information on your PDA phone', then crashes with the error: Rom update utility MFC application has stopped working.
I'm running windows vista on my laptop, and read that the RUU won't work until the drivers are updated. Following the instructions on mrvanx.org, I have downloaded the driver for vista and installed it, but i'm still getting the problem when I try and reflash the device.
I've also tried running the RUU in compatibility mode for XP as it worked fine on my old laptop which was running xp, but it still crashes, every time.
I'm beginning to wonder if reflashing it will even work though, since the colours are messed up in bootloader mode as well, which leads me to think it may be a hardware problem.
I know next to nothing about repairing these though, and probably wouldn't bother if it's a hardware problem, but until I can reflash the firmware, I won't know whether this is a case.
I'll get the photo's of what the screen is like uploaded to my server later on, and post the links here, so you can see what the problem is.

Photo's now available
I've uploaded a couple of photo's to show what the screen is like:
http://csc2ya.co.uk/images/bootloader.jpg
http://csc2ya.co.uk/images/startup.jpg

Update
i've got my old laptop out, reloaded xp on that, and attempted the flash using that. However, I get the message 'rom update utility MFC has encountered an error and needs to close'
I just want to get it to reflash to see if it fixes the screen, but so far i'm having no luck at it.
I've sucessfully reflashed it in the past with the o2 rom using my old laptop, so I can't figure out why it isn't working now.
Update: I didn't have activesync installed on my laptop which was why the updater was crashing. I've installed activesync, but now i've got another problem that is preventing me from reflashing it. I start the updater, and click through the prompts. It gets to 'verifying the information on your pda phone', stays like that for about 30 seconds, then activesync disconnects, and I get the error: microsoft activesync cannot recognize this device for one of two reasons: then the other information that the dialog gives. I'm not going to bother typing it all out, as i'm sure nearly everyone has seen it at least once before.
Additional info: No idea if this is relevant or not, but the extended rom has been formatted using the service tool.
Another update: I have now managed to get the device to reflash, but it boots up afterwards as if I had just turned it off and back on again. I have tried a hard reset afterwards, but cannot seem to get any of the o2 stuff back. It appears that the screen problem is hardware related though, as it is still present even after reflashing.
I can also no longer get it to go into bootloader mode, but the phone will still boot normally.

csc2ya said:
It's been sitting in a box in my shed for about a year.
Click to expand...
Click to collapse
Not to be flippant, but there's your problem right there. Two things: extreme temperature, and moisture. Both are the enemy of electronics. Chances are very good that you're screwed.
The first thing I'd do is buy (or even better, borrow) a new battery. Yours is probably done for.
If that doesn't fix the problem, I recommend disassembly and thorough cleaning with isopropyl alcohol, followed by at least 24 hours of strong, dry airflow between 50-80 Fahrenheit. Any floor or desk fan would do. Reassemble and pray. If that doesn't do it, you're going to have to find your fun elsewhere, I'm guessing.

Myrddin Wyllt said:
Not to be flippant, but there's your problem right there. Two things: extreme temperature, and moisture. Both are the enemy of electronics. Chances are very good that you're screwed.
The first thing I'd do is buy (or even better, borrow) a new battery. Yours is probably done for.
If that doesn't fix the problem, I recommend disassembly and thorough cleaning with isopropyl alcohol, followed by at least 24 hours of strong, dry airflow between 50-80 Fahrenheit. Any floor or desk fan would do. Reassemble and pray. If that doesn't do it, you're going to have to find your fun elsewhere, I'm guessing.
Click to expand...
Click to collapse
The battery appears to be fine. I charged it overnight, and it still seems to hold a decent charge.
I haven't really got the tools to dissasemble it fully, but I will give it a go sometime in the next few weeks (i've got a copy of the service manual on my computer, so that shouldn't be a problem).
I only really got it out to play around with it again, and possibly try some apps on. It still appears to work fine apart from the screen (and the o2 applications now missing due the extended rom format, but i'm not bothered about those). I've installed the my mobiler screen program on my laptop so I can at least view the screen properly using that.
Thanks for the suggestions anyway.

csc2ya said:
I've installed the my mobiler screen program on my laptop so I can at least view the screen properly using that.
Click to expand...
Click to collapse
Well, this certainly changes things. You have a bad screen, or a bad connection to the screen. You can get replacement for around $100USD, or you can try to get a broken unit with a good screen for less (maybe). I'd still disassemble it first, though, in case it's just a weak connection.

[Q] URGENT HELP with a fully bricked defy

Hi Everybody,
I believe that I am now in serious trouble with my Motorola Defy. I have tried to look everywhere today to find a similar problem to what I am experiencing, and although I can find all the problems, I can't find anyone which has happened like this. It would be so great if someone could help me. I am so so desperate and in total panic right now. I need this phone to work which I had bought in Germany (where my home base is set up) but I am currently working in Estonia where salary really does not allow me to just go out and buy a new one - not even a cheap 20€ phone.
I originally bought the phone about 1 1/2 years ago with Android 2.1. After about 6 months I did the official update to Android 2.2. This is where a few things started to go wrong. Google maps would crash the phone so that I would have to take the battery out to restart it. The camera didn't work properly, and not at all with the flash, and the phone would quite often restart itself. I could however live with all this and just accepted it as I didn't want to do anything to make it worse - I trust myself 100% with computers and there isn't much that I can't do with them. But with phones, that's where I have to put my hands up as I really don't trust myself to do anything because of the fear of bricking one.
Anyway, today as I was using the phone after taking a few pictures the phone had frozen, so as always I took the battery out and turned it on again, when it loaded up and as soon after I put my pin and unlock number in, it restart itself, So I again I put my pin and unlock number in, and it restarted itself. After this I couldn't even put my pin number in.
I then did went into Bootloader to do a wipe and restore, This however, after taking two hours and just watching the yellow dots move along, was clear to me that this also wasn't working. After coming home from work I then copied the instructions found I think in the Beginners Defy Guide on this site for using RSD Lite and an SBF File. This then failed and in Bootloader it also then said Corrupt.
So I then started to watch a video on youtube for a complete guide from unbricking to installing CM10 (something I wanted to do the whole time and never trusted myself). Meanwhile, whilst everything was downloading, although the phone still had about 60% battery, I thought I would plug it in just to charge it for a bit, this however also did not work but I left it in just in case it was working.
After everything was finished downloading, I unplugged the phone from the wall and now it won't even turn on,, neither in Bootloader, or the screen. It does NOTHING! :crying::crying:
When I plug it into the computer the little white led light comes on (top left of the phone) and the computer makes the sound that something is plugged in. This is also recognised my RSD Lite, however once a file has been created it cannot be flashed. It's like the phone is there, but it isn't.
I am really desperate to get this working as I really need this phone for work, and like I said just cannot afford to run and buy anything.
I'm very sorry if I have posted this in a wrong area, but I honestly did try to find something. I just don't understand how plugging it in to charge can stop it from not even opening bootloader, It's like it's got a mind of it's own.
Thank you very very much for reading, and I apologise that it's so long,
Best Wishes,
Steve

To get into the bootloader , keep the volume up button pressed and then press the power button. Is this what you tried to do?
And I didn't get the part where you wiped through the bootloader. As far as I know there is no option there. Do you mean the stock recovery?( The yellow dots are there in the stock recovery)
Sent from my MB526 using xda app-developers app

wahat3 said:
Hi Everybody,
I believe that I am now in serious trouble with my Motorola Defy. I have tried to look everywhere today to find a similar problem to what I am experiencing, and although I can find all the problems, I can't find anyone which has happened like this. It would be so great if someone could help me. I am so so desperate and in total panic right now. I need this phone to work which I had bought in Germany (where my home base is set up) but I am currently working in Estonia where salary really does not allow me to just go out and buy a new one - not even a cheap 20€ phone.
I originally bought the phone about 1 1/2 years ago with Android 2.1. After about 6 months I did the official update to Android 2.2. This is where a few things started to go wrong. Google maps would crash the phone so that I would have to take the battery out to restart it. The camera didn't work properly, and not at all with the flash, and the phone would quite often restart itself. I could however live with all this and just accepted it as I didn't want to do anything to make it worse - I trust myself 100% with computers and there isn't much that I can't do with them. But with phones, that's where I have to put my hands up as I really don't trust myself to do anything because of the fear of bricking one.
Anyway, today as I was using the phone after taking a few pictures the phone had frozen, so as always I took the battery out and turned it on again, when it loaded up and as soon after I put my pin and unlock number in, it restart itself, So I again I put my pin and unlock number in, and it restarted itself. After this I couldn't even put my pin number in.
I then did went into Bootloader to do a wipe and restore, This however, after taking two hours and just watching the yellow dots move along, was clear to me that this also wasn't working. After coming home from work I then copied the instructions found I think in the Beginners Defy Guide on this site for using RSD Lite and an SBF File. This then failed and in Bootloader it also then said Corrupt.
So I then started to watch a video on youtube for a complete guide from unbricking to installing CM10 (something I wanted to do the whole time and never trusted myself). Meanwhile, whilst everything was downloading, although the phone still had about 60% battery, I thought I would plug it in just to charge it for a bit, this however also did not work but I left it in just in case it was working.
After everything was finished downloading, I unplugged the phone from the wall and now it won't even turn on,, neither in Bootloader, or the screen. It does NOTHING! :crying::crying:
When I plug it into the computer the little white led light comes on (top left of the phone) and the computer makes the sound that something is plugged in. This is also recognised my RSD Lite, however once a file has been created it cannot be flashed. It's like the phone is there, but it isn't.
I am really desperate to get this working as I really need this phone for work, and like I said just cannot afford to run and buy anything.
I'm very sorry if I have posted this in a wrong area, but I honestly did try to find something. I just don't understand how plugging it in to charge can stop it from not even opening bootloader, It's like it's got a mind of it's own.
Thank you very very much for reading, and I apologise that it's so long,
Best Wishes,
Steve
Click to expand...
Click to collapse
Check out this link all the best :good:

Bricked my new MK809IV Please help....

well Yeah.. so i bought this stick just now on ebay thinking it should be good enought to give away for streaming some live tv and so on, but
this had obviously the WIFI problem and there i was..
Not beeing able to use WIFI i started to search for different roms and after a couple days constantly searching HOW TO- and downloading different ROMS and watching youtube on how to flash i set up to the task once again..
Beeing able to flash both Nvidia tablets, Samsung Telephones, and Xiaomi i felt confident that i would be able to fix this..
But no, i had a couple different roms that started up With start screen but then that was it, nothing more i couldnt get past start boot logo on either of the 3 roms i thought was correct so i startd to search for same chip roms as this has the 3229 rockchip and the AS something number wifichip..
But then after flashing With a unknown rom it wouldnt start up again or even get recogniced by the computer usb again..
I tried the reset button, i tried shortcutting pin 6-7 and most likely all other as well but no Luck..
There is a blue light but its only halfway as Bright as when the stick was ON and working.
So its like its stuck in some low Power recovery or i dont know..
At least it lights up when i plug it in.
this is the stick With the red "plastic antenna"
Its not an antenne after all by lokking at it but maybe it serves some purpose of making People think its an antenna..
Any suggestions will be apreciated as now i consider it as Waste and after just spending 35 USD on it i would like it to at least get it back so i can sideload some games on it and give it away rather than putting it in the trashcan..
I attach link to the crap i bought so you get the idea of what it is and to also avoid..
Thank you all for all help!!
http://www.ebay.com/itm/252678580408

veralynn said:
well Yeah.. so i bought this stick just now on ebay thinking it should be good enought to give away for streaming some live tv and so on, but
this had obviously the WIFI problem and there i was..
Not beeing able to use WIFI i started to search for different roms and after a couple days constantly searching HOW TO- and downloading different ROMS and watching youtube on how to flash i set up to the task once again..
Beeing able to flash both Nvidia tablets, Samsung Telephones, and Xiaomi i felt confident that i would be able to fix this..
But no, i had a couple different roms that started up With start screen but then that was it, nothing more i couldnt get past start boot logo on either of the 3 roms i thought was correct so i startd to search for same chip roms as this has the 3229 rockchip and the AS something number wifichip..
But then after flashing With a unknown rom it wouldnt start up again or even get recogniced by the computer usb again..
I tried the reset button, i tried shortcutting pin 6-7 and most likely all other as well but no Luck..
There is a blue light but its only halfway as Bright as when the stick was ON and working.
So its like its stuck in some low Power recovery or i dont know..
At least it lights up when i plug it in.
this is the stick With the red "plastic antenna"
Its not an antenne after all by lokking at it but maybe it serves some purpose of making People think its an antenna..
Any suggestions will be apreciated as now i consider it as Waste and after just spending 35 USD on it i would like it to at least get it back so i can sideload some games on it and give it away rather than putting it in the trashcan..
I attach link to the crap i bought so you get the idea of what it is and to also avoid..
Thank you all for all help!!
http://www.ebay.com/itm/252678580408
Click to expand...
Click to collapse
Hi.
I think I have the same device as you. And also I tried to flash another rom without success, so until I find a good rom, its just a small brick.
I also been in the same situation as you, but you have to short pins 7-8 to revive. Its the pins facing the middle of the device, and counting from the device edge/side.
Good luck. If you find a working rom for it, let me know

No, i have had no luck. Piece of **** device.
Got 80% refund from seller after a couple weeks of complaining.
Just throw it away and buy a ZAPPATI media player or a Nvidia shield if you dont use any 3D.

veralynn said:
No, i have had no luck. Piece of **** device.
Got 80% refund from seller after a couple weeks of complaining.
Just throw it away and buy a ZAPPATI media player or a Nvidia shield if you dont use any 3D.
Click to expand...
Click to collapse
Hi again.
If you ever revive your dongle, you can get a working rom from the following link:
http://freaktab.com/forum/tv-player-support/rockchip-based-tv-players/rk3229-devices/firmware-roms-tools-bg/623420-mk809iv-rk3229-bricked-how-to-unbrick?p=646882#post646882
It worked for me

Thanks. I will try. Any tips in how to revive it??

I also have an mk809iv. I couldn't get developer options to show after tapping build number but it said "no need you are already a developer" (I assume its preunlocked?) I got bored and decided to flash a rom. I have the rockchip factory tool and rockchip batch tool. I tried flashing an update and the problems began lol
OK..... The stick now doesn't have a blue led on AT All. Tried original mains power source different USB cables different ports on laptop etc.
When I connect it to the TV it doesn't show up on the hdmi. Have I really fried it properly ?
Is there a way to use command on pc or adb shell or something to unlock the bootloader. In batch tool I can see the device after shorting pin 6/7 method but when I load firmware and start to flash then it comes up with failed at boot every time and on different versions of the tool.
I rooted the device before with King root (not king o root) and flashed supersu via rom installer app. Assuming that developer options are open by default, the device should be rooted now...... Right? ?
Anyway is there a way to uninstall all the software and reinstall the manufacturers firmware via the pc ? I have included pics of the board, but when looking at other people's pics the have a lot more chips and nand chips etc mine has one chip on the back and on the other side what I presume to be a heat sync (look like a bit of a tin can
Lol)
I have been on many forums for about 48hrs straight now ? and still can't find answers *sigh*
Recap:- 1 is it fried
2 if not can I sort it via pc
3 HOW?! lol
One last thing, would it run on cyanogenmod 11 ? it's an android device running kit kat and my gingerbread S2 is now on cm11 or are the internal "gibbons" different ?
Many thanks to anyone who can lend me a hand ??

Wet Phone, Won't Boot, Need to Recover Pics/Vids of Newborn Son

Long story short my phone was in a pool long enough to shut itself off. I assumed it would never come back to life but I got all the water out of it that I could by shacking it and such and then started the drying process.
The only reason I'm trying to recover the phone is because it appears I turned off Google Photos backup 4 months ago (it was trying to backup when I didn't want it to) and forgot to turn it back on and now I've got 4 months of pics/vids of my 8 month old son on there that are currently "lost". That's half of his life so clearly I'd like to recover these.
So I dried it for 3 days, charged it to 100%, and powered it up. Motorola logo displayed for a few seconds and then it went to a screen that said:
Your phone didn't start up successfully, use Software Repair Assistant on computer to repair your device.
Connector your device to your computer to get software repair assistant.
AP Fastboot Flash Mode (Secure)
Failed to verify hab image boot
Failed to validate boot image
ERROR: failed to pass validation. backup to fastboot
Fastboot reason: Fall-through from normal boot mode
I downloaded the software repair assistant and when I connect my phone to the computer it is recognized by the computer and the software also recognizes it and starts the "finding phone information" process where it identifies the phone type and such (presumably). Problem is it just sticks at this and never does anything else. I left it connected for over an hour while it did this. I tried a few more times with the same result.
So my questions are does anyone know what the errors mean, how do I fix them, and if they can't be fixed without a factory reset (or at all), what's the best path to trying to recover the pics/vids? I considered attempting a factory reset and then using a recovery program/app but if there are any methods that don't involve first deleting the files via a factory reset and then requiring a recovery attempt, I'd love to try that first.
Thanks for your time.

Stinger2300 said:
Long story short my phone was in a pool long enough to shut itself off. I assumed it would never come back to life but I got all the water out of it that I could by shacking it and such and then started the drying process.
The only reason I'm trying to recover the phone is because it appears I turned off Google Photos backup 4 months ago (it was trying to backup when I didn't want it to) and forgot to turn it back on and now I've got 4 months of pics/vids of my 8 month old son on there that are currently "lost". That's half of his life so clearly I'd like to recover these.
So I dried it for 3 days, charged it to 100%, and powered it up. Motorola logo displayed for a few seconds and then it went to a screen that said:
Your phone didn't start up successfully, use Software Repair Assistant on computer to repair your device.
Connector your device to your computer to get software repair assistant.
AP Fastboot Flash Mode (Secure)
Failed to verify hab image boot
Failed to validate boot image
ERROR: failed to pass validation. backup to fastboot
Fastboot reason: Fall-through from normal boot mode
I downloaded the software repair assistant and when I connect my phone to the computer it is recognized by the computer and the software also recognizes it and starts the "finding phone information" process where it identifies the phone type and such (presumably). Problem is it just sticks at this and never does anything else. I left it connected for over an hour while it did this. I tried a few more times with the same result.
So my questions are does anyone know what the errors mean, how do I fix them, and if they can't be fixed without a factory reset (or at all), what's the best path to trying to recover the pics/vids? I considered attempting a factory reset and then using a recovery program/app but if there are any methods that don't involve first deleting the files via a factory reset and then requiring a recovery attempt, I'd love to try that first.
Thanks for your time.
Click to expand...
Click to collapse
I can't help you with the problem of getting your pictures, but I can tell you the "Software Repair Assistant" isn't going to help... It hasn't been supported for years on any model, probably 5+ I guess. It is just left over code that Moto hasn't removed from current devices that's saying that.
Most likely you eMMC chip is corrupt, that's your internal storage... If it took a dip in a pool, that's the worst possible place it could happen to get wet, chlorine and other chemicals in the water literally eat away the silicon internals of the phone. You would have better if to drop it in a muddy River or lake than a "clean" pool.
Honestly, at this point if the device won't boot and the bootloader is locked, your chances of recovery if any data is near zero.

you could try booting into fastboot, go to stock recovery and then adb pull

munchy_cool said:
you could try booting into fastboot, go to stock recovery and then adb pull
Click to expand...
Click to collapse
Looks like you need to know the exact file name for each file for that. Is that correct or can you somehow view a list of available files to pull?

Stinger2300 said:
Looks like you need to know the exact file name for each file for that. Is that correct or can you somehow view a list of available files to pull?
Click to expand...
Click to collapse
if you have enough space on your computer and you do
adb pull /sdcard .
that should pull all contents of internal storage to computer

munchy_cool said:
if you have enough space on your computer and you do
adb pull /sdcard .
that should pull all contents of internal storage to computer
Click to expand...
Click to collapse
OK, I'll give that a try after I get the SDK Manager updated. Thanks.

Well, I can't believe it but I hadn't messed with the phone since Wednesday (when it wouldn't boot) and when I plugged it into the computer and turned it on today it booted!
I was able to pull 24gb of pics/vids/texts without any "tricks" and the only thing that doesn't seem to work on the phone (for now) is the camera (constantly get camera app has stopped errors and no camera apps will open) and the screen has some interesting artifacts like it's got a little water in between the screen layers. I'm using my old Moto X for now and I'm ordering a Moto X4 (waterproof) to replace it.
Either way, I can't believe it actually came back to life and I'm so damn happy right now! Thanks for your help even if I didn't end up needing to use it.

Stinger2300 said:
I was able to pull 24gb of pics/vids/texts without any "tricks" and the only thing that doesn't seem to work on the phone (for now) is the camera (constantly get camera app has stopped errors and no camera apps will open) and the screen has some interesting artifacts like it's got a little water in between the screen layers. I'm using my old Moto X for now and I'm ordering a Moto X4 (waterproof) to replace it.
Either way, I can't believe it actually came back to life and I'm so damn happy right now! Thanks for your help even if I didn't end up needing to use it.
Click to expand...
Click to collapse
awesome news. see you in the x4 forums

Stinger2300 said:
Well, I can't believe it but I hadn't messed with the phone since Wednesday (when it wouldn't boot) and when I plugged it into the computer and turned it on today it booted!
I was able to pull 24gb of pics/vids/texts without any "tricks" and the only thing that doesn't seem to work on the phone (for now) is the camera (constantly get camera app has stopped errors and no camera apps will open) and the screen has some interesting artifacts like it's got a little water in between the screen layers. I'm using my old Moto X for now and I'm ordering a Moto X4 (waterproof) to replace it.
Either way, I can't believe it actually came back to life and I'm so damn happy right now! Thanks for your help even if I didn't end up needing to use it.
Click to expand...
Click to collapse
That means it was still wet underneath/around the nand chip (where data is stored) causing the images from the stock firmware not to write (and subsequently fail) good thing you didn't fry it, anything less than a week of drying is pointless really and probably only survived due to the excessive shaking and such. Really the best thing to have done would have been to leave it on a car dash for a week. Camera would have dried out and still been working (betcha got what looks like stains on the sides/top/bottom of the screen)
In the future, non removable battery phones when dropped in water long enough to soak through, DO NOT CHARGE IT FOR AT LEAST A WEEK, DONT TURN IT ON FOR A WEEK. If you wanna be as safe as possible, that is.

Ae3NerdGod said:
That means it was still wet underneath/around the nand chip (where data is stored) causing the images from the stock firmware not to write (and subsequently fail) good thing you didn't fry it, anything less than a week of drying is pointless really and probably only survived due to the excessive shaking and such. Really the best thing to have done would have been to leave it on a car dash for a week. Camera would have dried out and still been working (betcha got what looks like stains on the sides/top/bottom of the screen)
In the future, non removable battery phones when dropped in water long enough to soak through, DO NOT CHARGE IT FOR AT LEAST A WEEK, DONT TURN IT ON FOR A WEEK. If you wanna be as safe as possible, that is.
Click to expand...
Click to collapse
Thanks for the info, hopefully I'll never have to use it!
Yes, it looks like stains on the bottom portion of the screen.

Screen dead + Front camera keeps trying to open

Hey!
While I was calibrating my fingerprint, phone suddenly turned off and went to recovery with screen off.
I managed to reflash stock rom through fastboot and it boots to system fine, but the screen stays off and the front camera keeps trying to open while playing the MIUI camera sound (sometimes, while booting, the camera does manage to open once, kinda like it's calibrating). Some playing around with ADB and it seems that the SIM isn't recognized either.. antenna maybe?
I opened the phone up and checked everything, there's no visible issues with the electronics, however it could just be the inside of a cable that died?
Does anyone know what this could be? I noticed the screen, fingerprint reader and antenna are all connected to the same removable PCB, but the camera isn't so that's odd.

Aren't we moving way too fast here? Like wtf is happening rn?
First: Explain in detail from the beginning please if you want help.
Second: Please state exactly what is your issue, and the ROM version of your device.
I don't think what you just did is the cause of whatever problem you're facing, do you mind telling me the source from which you got this phone? Otherwise you might want to send it to a service center.

XDHx86 said:
Aren't we moving way too fast here? Like wtf is happening rn?
First: Explain in detail from the beginning please if you want help.
Second: Please state exactly what is your issue, and the ROM version of your device.
I don't think what you just did is the cause of whatever problem you're facing, do you mind telling me the source from which you got this phone? Otherwise you might want to send it to a service center.
Click to expand...
Click to collapse
It's a bit of a long one, so I didn't want to bother too much with the details if anyone knew what those specific issues could be caused by, here goes though:
I am on a Mi 9T bought on Amazon Italy in July 2019. I cannot comfortably send it to a repair center due to every authorized shop around here is just a drop-off point for Xiaomi RMA. I talked to them and, due to (>6 months old) glass damage to the screen and back of the phone, they intended to charge me way more than I can afford, as "solving issues covered by the warranty would require us to replace the accidentally damaged components"
As for what happened:
I was running LOS 17.1 with no issues for a few months. I went to unlock the phone and I heard the reboot vibration, which sent me to recovery (softbricked) but with no screen signal. I assumed it was just a software problem, so I flashed MIUI 12 (global, V12.0.7.0.QFJMIXM) to see what would happen.
As it completed, the phone rebooted itself, the MIUI logo popped up and it went to system (seemingly) without any issues.
I went through the initial wizard and played around with it. everything seemed fine and I even made sure the screen did work in recovery and fastboot. Later, when I went to setup the fingerprint reader, the screen went blank for half a second when I first touched it, and then the same screen death -> reboot to recovery.
The phone was softbricked again, though, this time, reinstalling MIUI didn't yield the same success. Now:
MIUI boots "normally" again
The screen isn't working at all
The front camera opens, as if it's calibrating, when system boots up
The front camera randomly tries to open again every now and then, failing to do so as if the motor is stuck, while MIUI plays the camera closing sound.
Meddling through ADB, the antenna doesn't seem to be working, but I can't be 100% sure due to the methods used
The power and volume buttons, speakers, and the charging light all work.
I have opened the phone up myself, thoroughly checked every cable, connection and PCB, but there is no sign of damage. I put it back together and the same issue continued.
My best guess is that something inside the fingerprint reader went bad and shorted something else.
What that something else is, I couldn't find out. Given the antenna, screen and FOD are all connected to the same little PCB which then runs a couple cables to the motherboard, I am now in the process of finding a couple replacement cables to see if that fixes anything.
As I mentioned before, repair centers are not an option due to the lack of anyone who's willing to help me for less than a good chunk of the price of the phone.

Interesting. So basically what happened is due to the initial soft brick and accordingly you flashed a global MIUI 12 ROM, which in return brought you to the second soft brick which caused some issues within the hardware of the device.
Now you're stuck with a faulty screen, a faulty camera and a faulty antenna.
I don't have the skills to play around with the motherboard and the phone circuit. And I don't care which youtube tutorial you saw, you should have NEVER done that - Of course unless you're actually experienced in that manner, then I apologize for speaking with such prejudice -
I can't help you if you messed up your phone circuit since I have no knowledge about android hardware, however I can safely assume that what caused your issue isn't related to hardware.
I think the issue is caused by an incomplete flashing of a ROM (In this case MIUI 12 global) OR flashing a different variation from your device.
e.g. you flashed only the ROM, but didn't flash the other components of the ROM.
Needless to say, flashing a variation of the ROM that isn't meant for you device can be a disaster recipe.
I recommend flashing LOS again, since you can't go back on Xiaomi devices due to rollback protection.

XDHx86 said:
I don't have the skills to play around with the motherboard and the phone circuit. And I don't care which youtube tutorial you saw, you should have NEVER done that - Of course unless you're actually experienced in that manner, then I apologize for speaking with such prejudice -
Click to expand...
Click to collapse
I understand why you'd think that and have seen people do similar stupid things, however I didn't watch any youtube video and know what I'm doing quite well.
I made sure I flashed the correct rom through fastboot to restore everything to stock. I did try to reflash LOS and whatever else (though it's kind of a pain with adb shell), but it doesn't fix the problem, sadly.
That's why I'm betting on a HW issue.
The fingerprint reader and everything else worked flawlessly in LOS for months, but it made the screen go blank and bricked the device in both LOS and fully functional, stock MIUI.
Currently, I'm battling with this damn thing to get USB debugging working while booted to system, so I can do a few things like cast the screen to my PC and see what works from there.
I have access to fastboot and recovery, but everything I know (editing build.prop or patching the boot image) didn't work so far. Do you have any idea what I could do to get that done?

angometry said:
Currently, I'm battling with this damn thing to get USB debugging working while booted to system, so I can do a few things like cast the screen to my PC and see what works from there.
Click to expand...
Click to collapse
If the touch screen is dead then you can use mouse and OTG cable.
If it is completely black then you can get usb c to HDMI cable (Also usb c hub might work, like this one). Or you can use playstore on pc to download and install apps like (Screen stream over HTTP) on your device, just make sure your device is connected to the internet and you're signed in on your phone as well, you might have to type in the screen password if you have one.
angometry said:
I have access to fastboot and recovery, but everything I know (editing build.prop or patching the boot image) didn't work so far. Do you have any idea what I could do to get that done?
Click to expand...
Click to collapse
I don't know why bother with build.prop unless you have the wrong fingerprint prop. Then you can get the correct one from your device's stock ROM, though I think this is irrelevant to your issue.
All I can think of is:
Wiping dalvik cache, though you might have already done that.
Trying other custom ROMs from here.
You may try to get your device rollback index and installing a MIUI ROM that has index higher than it, and see if that works.
That is as far as I can help, unfortunately.
I have zero knowledge when it comes to hardware, so I can only help with software issues. If none of my solutions worked then sorry for wasting your time :/

XDHx86 said:
If it is completely black then you can get usb c to HDMI cable (Also usb c hub might work, like this one).
Click to expand...
Click to collapse
Wait, does it actually just automatically use it as a 2nd screen if I connect it via HDMI?
XDHx86 said:
I don't know why bother with build.prop unless you have the wrong fingerprint prop. Then you can get the correct one from your device's stock ROM, though I think this is irrelevant to your issue.
Click to expand...
Click to collapse
Sorry, I didn't explain myself, I'm looking for a way to enable USB Debugging without a screen. Thinking that using adb in twrp is the best way, but I can't manage to do it. Do you have any ideas?
If I can get it on, I can then use things like scrcpy to get screen signal through USB.
Main problem with everything else is that the screen is 100% dead. Even with usb otg I don't know how I could possibly get through the setup wizard haha

angometry said:
Wait, does it actually just automatically use it as a 2nd screen if I connect it via HDMI?
Click to expand...
Click to collapse
I haven't tried it myself, however it should detect it as a second monitor. Give it a try the cable isn't costly at all anyway.
angometry said:
I'm looking for a way to enable USB Debugging without a screen. Thinking that using adb in twrp is the best way, but I can't manage to do it. Do you have any ideas?
Click to expand...
Click to collapse
TWRP has debugging mode on by default, however that strictly applies to recovery and fastboot modes only as debugging mode is pretty powerful and can cause security issues. So you better forget about it.
I saw one of my friends who owns an authorized service center use some cable connections to get the screen to display on another touch screen. If you have the capabilities and resources I recommed trying it, though don't mess too much with the motherboard.
Just a question though, can you confirm if the touch is working? If not then there's a chance - Although slight - that this is just a UI problem (Which is pretty common in MIUI ROMs for some reason). In that case deleting dalvik cache or completely reflashing the ROM might solve the issue.
I may not do much help but certainly someone there can help so it's better if you include "usb debugging" in the title and/or the tags. Like changing the title to "Enabling usb debugging without screen" or "Screen is dead, need help to flash ROM"
Using proper title and proper tags can get the right person to help.