Related
Hey guys, I recently broke the LCD on my Note 3 running stock KitKat ( :crying: ) and realized I hadn't done a nandroid backup in quite some time...
I tried the obvious adb pull, but for some reason I couldn't even get into adb shell or see my device in the device list like I had previously.
I'm all out of ideas now...
Could somebody please throw some help my way?
Does your phone even boot up? Do you get sound, vibration, anything to indicate it's still working internally beside blank screen?
Are you going to try to fix it? buy new one? upgrade to Note 4? Me and my wife used to own GS3 and when she broke her screen, I swapped motherboard with mine to copy pictures mostly and some other stuff, but we werent going to fix it, since I decided to get her GS5.
pete4k said:
Does your phone even boot up? Do you get sound, vibration, anything to indicate it's still working internally beside blank screen?
Are you going to try to fix it? buy new one? upgrade to Note 4? Me and my wife used to own GS3 and when she broke her screen, I swapped motherboard with mine to copy pictures mostly and some other stuff, but we werent going to fix it, since I decided to get her GS5.
Click to expand...
Click to collapse
I'm getting a replacement through the phone insurance. It does turn on and function perfectly normal, the screen just has a tiny, tiny fracture point with a crack spanning across the screen horizontally, rendering the bottom half unusable. The top half is functioning though.
I cannot unlock my phone or make a backup with the bottom half not working.
Try using a bluetooth mouse or wired mouse with otg cable
Sent from my SM-N9005 using Tapatalk 2
http://forum.xda-developers.com/showthread.php?t=2786395
Could help, made for exactly your problem. If you manage to get it working download Nandroid Offline backup, which allows you to make a Nandroid backup from Android itself, rather than CWM/TWRP.
EDIT -- Just checked and it works an absolute treat. Providing you had USB Debugging enabled before your phone got broke, it should work fine. It even has the option to swipe to unlock or disable a pattern unlock if you had one enabled.
Pagnell said:
http://forum.xda-developers.com/showthread.php?t=2786395
Could help, made for exactly your problem. If you manage to get it working download Nandroid Offline backup, which allows you to make a Nandroid backup from Android itself, rather than CWM/TWRP.
EDIT -- Just checked and it works an absolute treat. Providing you had USB Debugging enabled before your phone got broke, it should work fine. It even has the option to swipe to unlock or disable a pattern unlock if you had one enabled.
Click to expand...
Click to collapse
Thank you for the link - it looks like it would be a great solution, but unfortunately I cannot enable USB debugging with the code given :\. I may be out of luck
Well, if nothing else works and data on the phone is that important, then you need to convince the insurance company to send you new Note 3 first and swap the MB as I suggested to retrieve the data, then put everything back to original. I have not done this on Note 3, but GS3 was probably one of easier electronics repairs I've done, just follow one of many youtube videos, to make sure you don't break some wire, before disconnecting. Possibly a shop could do that for you.
Well, freakin sweet deal. After being on the phone with the insurance company and US Cellular for two and a half hours and having them tell me everybody was out of Note 3's and they would only give me $400 bucks for my old phone minus my $175 deductible, I received another call from management at the insurance company apologizing and letting me know that they'd offer me $725.
It just so happens the new Note 4 is $770, so thank the Lord I'm in a good spot!
I have read every single thread that exists on the internet about this problem, the bootloops, the faulty bootloaders, the wrong rooting and image installations, every single posible way to brick this piece of device that everyone seems to have problems with. Yet none of them has gave me a solution. First of all, it's my girlfrinds tablet, she told me that one day, she tried to upgrade the android software and while it was installing it, the tablet bricked. She was able to go to fastload mode (power + volume up) we've tried recovery mode, factory reset, every option there, nothing. She gave me the tablet, I plugged it on my pc and used Nexus Root Kit to install a new android software to the device. After a painful search of how to make the Kit recognize the tablet because usb debugging was not on, I was able to start the process of installing the new software. Yet, in the middle of the installation, the micro-usb moved a little bit and the tablet got disconected. The process was cancelled and the tablet screen froze. I turned the tablet off and that was when it just bricked and never wanted to turn back on. Neither with any combination of the buttons, nor while leaving it charging a long time, nor any possible solution the internet may have about this. Just fully totally and simply bricked. Yet, when I connect it to my pc (windows 7 ultimate 64 bits) sometimes, it reads it as an unknown device, sometimes it reads it as a random APX device, and when I install any kind of drivers that already exist on every thread that there is about it, it reads it as an ASUS Transforme Prime APX Interface, yet the tablet never displays anything, and I'm not able to access it in any way nor make any changes to it whatsoever. I live in a country were there is no google or asus techical support, and third-party technical supporters are dumb as f***. My girlfrind took the tablet to 2 other places before giving it to me and they said to her that "it didn't have any software installed" (which was wrong) and that "it was beyond repair" (which was also wrong). The only thing I want to know is: is there any way to fix it now? or do I just have a very nice and fancy paperweight in my hands.
Makatown said:
I have read every single thread that exists on the internet about this problem, the bootloops, the faulty bootloaders, the wrong rooting and image installations, every single posible way to brick this piece of device that everyone seems to have problems with. Yet none of them has gave me a solution. First of all, it's my girlfrinds tablet, she told me that one day, she tried to upgrade the android software and while it was installing it, the tablet bricked. She was able to go to fastload mode (power + volume up) we've tried recovery mode, factory reset, every option there, nothing. She gave me the tablet, I plugged it on my pc and used Nexus Root Kit to install a new android software to the device. After a painful search of how to make the Kit recognize the tablet because usb debugging was not on, I was able to start the process of installing the new software. Yet, in the middle of the installation, the micro-usb moved a little bit and the tablet got disconected. The process was cancelled and the tablet screen froze. I turned the tablet off and that was when it just bricked and never wanted to turn back on. Neither with any combination of the buttons, nor while leaving it charging a long time, nor any possible solution the internet may have about this. Just fully totally and simply bricked. Yet, when I connect it to my pc (windows 7 ultimate 64 bits) sometimes, it reads it as an unknown device, sometimes it reads it as a random APX device, and when I install any kind of drivers that already exist on every thread that there is about it, it reads it as an ASUS Transforme Prime APX Interface, yet the tablet never displays anything, and I'm not able to access it in any way nor make any changes to it whatsoever. I live in a country were there is no google or asus techical support, and third-party technical supporters are dumb as f***. My girlfrind took the tablet to 2 other places before giving it to me and they said to her that "it didn't have any software installed" (which was wrong) and that "it was beyond repair" (which was also wrong). The only thing I want to know is: is there any way to fix it now? or do I just have a very nice and fancy paperweight in my hands.
Click to expand...
Click to collapse
Hello,
Thanks for using XDA Assist.
Your thread will be moved to Nexus 7 Q&A,Help and Troubleshooting.Experts there may be able to help you
___
v7
XDA Assist
Ha, yes...same boat and similar situation happened where USB became disconnected during bootloader flash. Surprised there haven't been any snarky comments made on your (and now my) situation. I have a totally non-responsive device now and Windows is also not recognizing the USB device (because it does not respond back when attempting to connect/mount). Looks like the only magic at this point would be cracking open and trying a completely different path to restoring, otherwise it is time to find a nice door needing a doorstop!
~Dubhead
Hi,
Not sure if it's a right place to ask, but let it be my first post here. I own an S5 device, and it's sort of crazy. Let me explain.
Three months ago my device suddenly rebooted and got almost-soft-bricked in sense of being unable to boot to the operating mode normally: its display just got black after the splash screen, however I could tap the display and watch 1 FPS "live stream" using `adb screencap` at my PC. So the device was not dead and I could take out all private not synced data I needed (it was really hard once for an application that has the backup facility disabled in its application manifest) -- blind tapping everywhere. My first attempt to fix the device was re-flashing another compatible ROM having all important data backed up. Well, I got it bricked and could not boot anymore. The recovery mode was not available (the device just frozen if trying to enter the recovery), however I could enter the download mode.
Unfortunately, no reflashing helped, so I decided to let it be fixed by a repaire service (since an official Samsung service center in my country has rejected the repair request _with payment_ because the device was not intended for sale here -- well, "thanks Samsung"). Ok, the alternative service took the device and asked almost a half of the device price for the display replace. Honestly, I forgot to ask why there was an idea to replace the display if it worked perfect while it was waiting in the Download mode. Again, it just got black after the splash screen, but the display worked fine in the Download mode until the device was powered off or reset. So after a few days they gave it back to me, and the device was really good now -- it worked fine. They also re-fllashed the device to Android 6 (previously Android 5) and the device was unrooted. Well, that's fine to me.
But after a few hours of rooting, testing and re-installing the software and migrating the data back to the device, the device rebooted again being unable to boot to the "operating mode". Now it just got stuck at the Samsung S5 splash screen or rebooted in a loop. But after a long time (it might took more than a day; the battery seems to be inserted in the device and not pulled off) the device was able to boot normally and (this might be odd) upgrade the installed apps. If I remember, this was a cyan screen with two or three animated white gears. So about 150 apps were upgraded and the normal "operating" mode activated -- so I could use the device. Now after working a few hours, the device falls into a reboot loop / splash freeze coma again for undetermined time, and then, for unknown to me reason, the device woke up.
In short:
1) The device reboots or shuts down suddenly.
2) Instant rebooting does not work for whatever reason.
3) Just wait for some undetermined time without the device battery pulled off.
4) ... It boots again.
5) The upgrading process starts after the boot.
6) Working with the device until paragraph 1: "The device reboots or shuts down suddenly".
Now I don't know if it's a hardware or a software issue: the repair service guys didn't explain much, and now I'm feeling cheated for the replacement of the display that worked perfect in the Download mode that I gave half device price just because it was an idea of theirs. Yes, I have the repair warranty paper for their service, but I just would like to know the real context.
What I could be deservedly blamed for:
* I rooted the device after their repair in a wrong way.
* When I rooted the device, I removed most Samsung bloatware I used to remove earlier. I don't tend to think that I could kill some important software, though. But, to me, it's hard to believe that a software issue might cause such an odd device behavior (I mean the booting just after a certain period of time).
So... I would really and really appreciate getting the real issue behind the symptoms or just a hint spark of light to reveal possible root causes. And was I really cheated by the repair service?
* My device: Samsung SM-G900P S5, Sprint
* Firmware before the repair: stock, Android 5.0.x (?), root, most Samsung bloatware removed
* Firmware after the repair: stock, Android 6.0.1, root, most Samsung bloatware removed (yes, the bloatware list difference is significant now)
* The battery: seems to work fine and does not get drained when the device is in coma
Thank you!
hurricane flow said:
Hi,
Not sure if it's a right place to ask, but let it be my first post here. I own an S5 device, and it's sort of crazy. Let me explain.
Three months ago my device suddenly rebooted and got almost-soft-bricked in sense of being unable to boot to the operating mode normally: its display just got black after the splash screen, however I could tap the display and watch 1 FPS "live stream" using `adb screencap` at my PC. So the device was not dead and I could take out all private not synced data I needed (it was really hard once for an application that has the backup facility disabled in its application manifest) -- blind tapping everywhere. My first attempt to fix the device was re-flashing another compatible ROM having all important data backed up. Well, I got it bricked and could not boot anymore. The recovery mode was not available (the device just frozen if trying to enter the recovery), however I could enter the download mode.
Unfortunately, no reflashing helped, so I decided to let it be fixed by a repaire service (since an official Samsung service center in my country has rejected the repair request _with payment_ because the device was not intended for sale here -- well, "thanks Samsung"). Ok, the alternative service took the device and asked almost a half of the device price for the display replace. Honestly, I forgot to ask why there was an idea to replace the display if it worked perfect while it was waiting in the Download mode. Again, it just got black after the splash screen, but the display worked fine in the Download mode until the device was powered off or reset. So after a few days they gave it back to me, and the device was really good now -- it worked fine. They also re-fllashed the device to Android 6 (previously Android 5) and the device was unrooted. Well, that's fine to me.
But after a few hours of rooting, testing and re-installing the software and migrating the data back to the device, the device rebooted again being unable to boot to the "operating mode". Now it just got stuck at the Samsung S5 splash screen or rebooted in a loop. But after a long time (it might took more than a day; the battery seems to be inserted in the device and not pulled off) the device was able to boot normally and (this might be odd) upgrade the installed apps. If I remember, this was a cyan screen with two or three animated white gears. So about 150 apps were upgraded and the normal "operating" mode activated -- so I could use the device. Now after working a few hours, the device falls into a reboot loop / splash freeze coma again for undetermined time, and then, for unknown to me reason, the device woke up.
In short:
1) The device reboots or shuts down suddenly.
2) Instant rebooting does not work for whatever reason.
3) Just wait for some undetermined time without the device battery pulled off.
4) ... It boots again.
5) The upgrading process starts after the boot.
6) Working with the device until paragraph 1: "The device reboots or shuts down suddenly".
Now I don't know if it's a hardware or a software issue: the repair service guys didn't explain much, and now I'm feeling cheated for the replacement of the display that worked perfect in the Download mode that I gave half device price just because it was an idea of theirs. Yes, I have the repair warranty paper for their service, but I just would like to know the real context.
What I could be deservedly blamed for:
* I rooted the device after their repair in a wrong way.
* When I rooted the device, I removed most Samsung bloatware I used to remove earlier. I don't tend to think that I could kill some important software, though. But, to me, it's hard to believe that a software issue might cause such an odd device behavior (I mean the booting just after a certain period of time).
So... I would really and really appreciate getting the real issue behind the symptoms or just a hint spark of light to reveal possible root causes. And was I really cheated by the repair service?
* My device: Samsung SM-G900P S5, Sprint
* Firmware before the repair: stock, Android 5.0.x (?), root, most Samsung bloatware removed
* Firmware after the repair: stock, Android 6.0.1, root, most Samsung bloatware removed (yes, the bloatware list difference is significant now)
* The battery: seems to work fine and does not get drained when the device is in coma
Thank you!
Click to expand...
Click to collapse
someone said after an OTA to 6.0.1 it borked the phone into a reboot loop too. I had mine rooted for maybe a week or 2 and now I have reboot Loops, not even twrp can fix this issue. I am trying a battery like this person said here http://forum.xda-developers.com/galaxy-s5/help/marshmallow-6-0-1-ota-update-boot-loop-t3425838,
spending 9 bux and change beats spending 250 for another Unlocked G900T
http://forum.xda-developers.com/galaxy-s5/help/marshmallow-6-0-1-ota-update-boot-loop-t3425838
eidairaman1 said:
someone said after an OTA to 6.0.1 it borked the phone into a reboot loop too. I had mine rooted for maybe a week or 2 and now I have reboot Loops, not even twrp can fix this issue. I am trying a battery like this person said here http://forum.xda-developers.com/galaxy-s5/help/marshmallow-6-0-1-ota-update-boot-loop-t3425838,
spending 9 bux and change beats spending 250 for another Unlocked G900T
http://forum.xda-developers.com/galaxy-s5/help/marshmallow-6-0-1-ota-update-boot-loop-t3425838
Click to expand...
Click to collapse
Hm, that's interesting, thank you. I also noticed that the loop happens after some time only, it's like the more you have your phone running in the normal mode, the more your phone can get into the loop again. However, I don't think it's a battery overheat issue or so (sorry, I may use silly terms not being an expert at all). So in short:
1) After some pretty long power-off time you power on the device. It's working really stable unless...
2) ... unless something happens (battery? some intricate software or hardware issue?) and the device gets rebooted.
3) Here comes the boot loop, and usually no reboot helps to get out of the reboot loop.
4) Just power off the device and let it just be alone for some time, and now you're back to the step 1 until the "unless..."
My coma device is powered off for long time (thus I think that the step 4 still works for me after that long time) and I'm going to give it to the repair service again, just comparing what the service guys say and what the forum folks say.
I will follow up on the battery swap when mine arrives.
hurricane flow said:
Hm, that's interesting, thank you. I also noticed that the loop happens after some time only, it's like the more you have your phone running in the normal mode, the more your phone can get into the loop again. However, I don't think it's a battery overheat issue or so (sorry, I may use silly terms not being an expert at all). So in short:
1) After some pretty long power-off time you power on the device. It's working really stable unless...
2) ... unless something happens (battery? some intricate software or hardware issue?) and the device gets rebooted.
3) Here comes the boot loop, and usually no reboot helps to get out of the reboot loop.
4) Just power off the device and let it just be alone for some time, and now you're back to the step 1 until the "unless..."
My coma device is powered off for long time (thus I think that the step 4 still works for me after that long time) and I'm going to give it to the repair service again, just comparing what the service guys say and what the forum folks say.
Click to expand...
Click to collapse
I received a battery yesterday, charged it up and started using it today, no reboots or bootloops so far.
The battery that came in my phone was made in china, the one I just got yesterday was made in Vietnam.
I'm wondering if Samsung really needs to stop using china to make batteries lol, Surefire flashlights state not to use batteries made in china lol.
eidairaman1 said:
I received a battery yesterday, charged it up and started using it today, no reboots or bootloops so far.
The battery that came in my phone was made in china, the one I just got yesterday was made in Vietnam.
I'm wondering if Samsung really needs to stop using china to make batteries lol, Surefire flashlights state not to use batteries made in china lol.
Click to expand...
Click to collapse
Hm, that's really interesting. It's hard to believe that replacing the old battery might affect it that much and get rid of bootloops -- I mean, I just thought that it might be a software/firmware failure (let's say I removed some system apps [actually Samsung bloatware] improperly), or something very core hardware might fail, but I have never thought of a batter as the root cause. Hard to say, sorry. But I'll take your solution into account. Thank you!
hurricane flow said:
Hm, that's really interesting. It's hard to believe that replacing the old battery might affect it that much and get rid of bootloops -- I mean, I just thought that it might be a software/firmware failure (let's say I removed some system apps [actually Samsung bloatware] improperly), or something very core hardware might fail, but I have never thought of a batter as the root cause. Hard to say, sorry. But I'll take your solution into account. Thank you!
Click to expand...
Click to collapse
I thought it was a bad rom flash as well or SuperSU causing it, well I found another article stating they replaced the battery and the issue went away. I think the phone was stating a bad POST so it would restart
Hi, so I recently smashed the H*** out of my Essential Phone. I put my sim in my wife's old Nexus to try and get back into the Gmail account I've had for 10+ years, and they've forced 2 step verification onto my account and will not let me use my number for recovery. The ONLY way to complete this verification is to use my Broken Essential Phone to accept screen prompt. So here's my question... I was rooted, with TWRP and Custom rom but do have Full Back ups on my computer, so if I were able to get another essential phone and root it, would I be able to then restore the factory image and back ups I had created for this old essential phone onto the new device and gain access to my Gmail account that way, or am I totally out of luck unless I fix my smashed phone enuf to get to the screen on to accept screen prompt to verify my identity....? Any insight here is greatly appreciated. I have 1000's of $$ invested in that Gmail and have been unable to access it for a week now. Google has been zero help. Sorry if. This is posted in the wrong space, I haven't been here in a while.
Kushmin05h said:
Hi, so I recently smashed the H*** out of my Essential Phone. I put my sim in my wife's old Nexus to try and get back into the Gmail account I've had for 10+ years, and they've forced 2 step verification onto my account and will not let me use my number for recovery. The ONLY way to complete this verification is to use my Broken Essential Phone to accept screen prompt. So here's my question... I was rooted, with TWRP and Custom rom but do have Full Back ups on my computer, so if I were able to get another essential phone and root it, would I be able to then restore the factory image and back ups I had created for this old essential phone onto the new device and gain access to my Gmail account that way, or am I totally out of luck unless I fix my smashed phone enuf to get to the screen on to accept screen prompt to verify my identity....? Any insight here is greatly appreciated. I have 1000's of $$ invested in that Gmail and have been unable to access it for a week now. Google has been zero help. Sorry if. This is posted in the wrong space, I haven't been here in a while.
Click to expand...
Click to collapse
A few years back you used to be able to get a new phone install TWRP create a backup on new phone and then copy the files from the old phones backup into the new backup folder (with the new unique file number). But think I read this doesn't work anymore on new version (but not sure you'll have to check yourself or hopefully someone here knows)
Even if that works what type of 2FA is it? Authenticator or SMS?
https://support.google.com/accounts/troubleshooter/4430955?hl=en
without a backup code it may not work anyhow
if you can see your screen but touch is not working just plug a mouse into the usb & click away! If screen is blacked out but rest of hardware good easiest to buy a replacement screen as cheap or use usb-hdmi hub to mirror screen (not sure if Essential phone requires any input to set up as haven't tried with this phone)
If other hardware damage it will depend, but as rooted you are in with a chance. Is usb debugging on?
Thanks for your response, Google has been zero help and I've definitely considered ordering a screen to see if I can get the old device to work, but the og screen is detached from the chip board, as far as I can tell it will power on with some serious prompting, but idk if it's actually trying to boot up or in some kind of safe mode detecting the screen is missing, or just wrecked completely...? Lol the notification Light stays red until the battery dies. I've considered maybe trying to clone the esn of my old essential phone to another phone to try to trick their servers that way but idk if they recognize the device via that (The ESN) or tokens generated locally on the device, and the more I think about it, the more I think the latter sounds more logical considering the nature of the beast I'm fighting here... Seems It would b wildly irresponsible of them to rely solely on esn to identify a "Trusted" device. Idk what to do, lol except cry... I'm basically at a loss at this point, so I will order a screen and go from there I guess, if the screen option doesn't work. You'd think with the money they have, they'd have some type of account recovery team, or a way to recover in the event something like this happens, or someone to speak to at the very least, the can verify my account in seconds over the phone, but do literally nothing for me, nor let me speak with or point me towards anyone who can.... And this is a pretty common issue it seems after lookin at their "Community help section" it's literally top to bottom ppl complaining about what I'm looking to "get help" with. There is zero reason they should be forcing 2fv on my account it's shut off in my account settings, I can get far enuf to c them, just doesn't let me change anything with out "Signing in" and verifying. Nor does it give me the option to use my only ACTUAL set up recovery option on the account, a code via text. It's almost like theyre protecting all my own s***, from me. The owner. Makes zero sense to me.
It sounds like when you setup the essential, you configured your Google account to use the *device* (via the Google app) for verification. I've done this also, but I have an old device also configured to authenticate. So the pop-up screen appears on both.
If you use a computer to log into your Google account (not gmail) on the screen that is waiting for verification, there should be a link to try a different method. Hopefully you setup a secondary email address in addition to the gmail account one.
Edit: start here https://support.google.com/accounts/answer/7682439?hl=en
OT: I realize you are frustrated, but it would be easier to pick out the relevant information in your posts if they were not one long paragraph.
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.