Database Users

[Q] Upgrading from CM6 to CM7 w/o a functioning power button

Hi,
A couple of months ago my power button completely stopped working on my Nexus One. After a bit of googling I saw this was a common problem for some users.
I worked around this problem by using the Trackball Wake feature in CM6 and when I actually need to turn on the device I use the "battery in & out while plugged in" hack.
I want to upgrade to CM7 and as usual I'll have to do a complete wipe. This will cause the "trackball wake" feature to go back to default which as I recall is off.
I'm also worried about various problems during the install that would require me to boot back into the bootloader which is impossible w/o a power button...
Any suggestions?
(Except "get a new phone". I'm in Israel and new phones here ain't cheap. a Nexus S for instance costs about 1000$ off contract.)
Thanks.

1) Buy a new power button board from eBay and fix the phone / give the phone to someone to fix.
2) Talk to HTC customer service in US (or where you bought the Nexus - I guess from Google?), open a ticket, ask for replacement phone, open account in advance on www.usaddress.com or such, give them the usaddress account address, send them the phone marked with your ticket number and S/N, document yourself sending the phone, wait till you get the phone by mail.
There is nothing much you can do. If you get your ROM to crash before ADB daemon starts running, you won't be able to get to recovery - and bootloader won't help you.
P.S. Don't upgrade to CM7 just yet. It's not nearly stable enough, and it causes most launchers to crawl.

There is a button to reboot into recovery directly on cm6

Booker-T said:
There is a button to reboot into recovery directly on cm6
Click to expand...
Click to collapse
He's talking about a case of FAILED installation.

I don't see how you can't do it, but in a very rare case, yes it could end up bad.
Just make sure you check md5, and most people have upgrade w/o wiping anything at all. Even if you do wipe it, just flash everything and the first time that you boot up, go straight to enable trackball wake.

You can get into fastboot no problem, and from fastboot you can boot into recovery:
fastboot boot recovery.img
(or whatever your recover file is named)
Sent from my Nexus One using XDA App

Yes, if he's fastboot-oem-unlocked, then it's a possibility.

Thanks a lot!
Fixing the power button is too much messing with hardware for me, and fixing it costs about 80$..
What I'm basically getting is that in the ****ti case I do have some error during installation I'm screwed but that it's a rare situation...
Would you risk it?
I'm seriously considering selling it (2nd hand hi-end phones go for about 400$ in Israel since buying a new one is much more expensive due to taxes) and having someone from my work bring me a new Nexus S (I work in a startup that also has an office in NY)
BTW, I called HTC regarding this problem and they've said that rooting / installing custom ROMs voided the warranty... Is that not the case?
Thanks.

If you ask me - CM7 is nowhere near completion state, and I kinda regret moving to it. Mostly because of launchers that don't support Gingerbread yet (both ADW and LauncherPro lag like hell with 7 screens), because of wonkiness (can be cured with Dewonkifier app, but still annoying), and because I need to compile it myself to get battery percentage. If you use GO Launcher or don't use many screens, don't mind installing Dewonkifier, and don't mind not having battery percentage - you can install it.
Read multiple threads about warranty on XDA. I've recently got my friend's phone exchanged, in exactly the same setup as you have (office in US).

You shouldn't need a power button using Clockwork recovery. Best method is to install Rom Manager. It will install the latest Clockwork 3.0.0.5 and allow you to download CM7 stable as well as GAPPS.
It is pretty fool-proof.
Later versions of Clockwork only use the trackball for selecting and use the back button; I think you can also use VOL+/- to go back also.
If you want to be safe, download several roms to your SD card. Perhaps CM6, CM7, and whatever else. That way if one rom fails, you have another option.
Clockwork also has the options to mount the SD card directly from the recovery menu, so you have the option of downloading roms on your PC and transfer them over to the phone.

[Q] I've bought an Ideos X5 but I have some questions :S

Hello Everyone,
Today I've bought an Ideos X5. It cost me 150€ at Ensitel in Portugal. And "almost" everything works like a charm.
The camera is not great but better that my old G1, the sound is better that my girlfriend's HTC Desire Z, and the multitouch works like a charm for me (comparing to my G1)... So it is a good buy.
But I have some questions, just to know if those are real problems (so I can go to the store and change the phone), or if it is just me :S...
1 - Bluetooth works very well (in the pocket, inside a box at 2 meters of distance from the other phone... and I can transfer files and receive... But I cannot receive apk files from my girlfriends HTC Desire Z (but with the same phone I can receive at least mp3 and pdf files).SOLVED : Using Bluetooth File Transfer from Medieval all works fine.
2 - Is it normal that the flash doesn't activate during a Video Recording ? But only when I take pictures ? (Can this be solved by installing another Camera App or a Custom Rom ?) And, is it normal that it takes so long to take a simple picture ?
3 - The last one. When my phone shutdowns because it doesn't have enough battery, and then I connect the cable (without booting the phone), the notification light is Green. But, the manual says that the Green light means Full Charged, the Orange light means Charging and the Red light means Low Battery. So it is normal that the light is Green when charging ?
Apart from that, I really love the phone, I can do all the stuff that I can't with my G1, I'm really happy to finally start developing games for Android (since that was a problem with the G1), and maybe, if the time and the knowledge allows, help improving Roms for this phone ^^
Thank in Advance
Luis Da Costa

Mine is China Unicon U8800 ,ROM versionB160.
1. This phone's bluetooth system is quite different from others.Files like apks,RARs...can not be transfered.My way is to change the file's name(like .mp3),then change it on the phone.
2.Don't understand.You can't record videos after you remove the TF card?
My phone doesn't have that problem.
When you revome TF card,the inside SD card's file will be renamed /mnt /,means the TF card.So everything wil be fine if you remove TF card,except softwares installed on the TF.
3.Very low----red; low----orange ; normal (above 60%)---yellow;full(above 90%)---green. I charge the battery by using charger,not the USB on the computer.
When you not sure those problems are really phone's problem,you can change another ROM from HUAWEI webside.To see if those still happen.
Bad English .......sorry

aliasbody said:
2 - Is it normal that the flash doesn't activate during a Video Recording ? And, is it normal that it takes so long to take a simple picture ?
Click to expand...
Click to collapse
If you activate the flash for video recording it is always on, so the behaviour of your ROM is not normal. It does not long to take a picture, no.
aliasbody said:
I connect the cable (without booting the phone), the notification light is Green. But, the manual says that the Green light means Full Charged, the Orange light means Charging and the Red light means Low Battery. So it is normal that the light is Green when charging
Click to expand...
Click to collapse
From my experience: When the light is green, the battery won't be charged. When I connect the charger it sometimes shows a green light for half a minute or so and then it starts charging (light turns a bit more yellow).
Did you install a custom ROM? Do not use the Froyo-ROMs provided by Huawei, they are just slow and have some bugs which won't be sorted out at all - the newer ROMs (void, Miui and Oxygen) work better. It is very easy to install a custom ROM so give it a shot. /Edit: Okay you already did that, forget what I said.

Might be too late but here are my answers :
- To use flash LED during video recording you must activate it from settings/config/(or whatever it is called) part of the camera software
- To be able to send and receive apk files, you can use third party software
Or I suspect there might be a setting to allow or disallow it, for all I know I can send and receive them but then again I'm using a heavily modified version of Oxygen ROM from dzo
- As for green light, if the phone is turned of, when I plug it in, mine turns green too. If it is turned on however, it changes the color.
- As for taking photos taking too much time, turn off steady image thingy. It waitstill your phone does not shake.

Samsung S5 reboots casually, and then does not boot for a certain period of time

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

SM-G935F data recovery

Hi Guys,
Today was my karma day. IDK what I did wrong, but my phone just stopped working and that just added a big problem to me.
So about the problem.
Short story - need to recover at least photos from the phone.
Long story - Today the phone just shut itself down and after trying to turn back it on it seems like it's in a boot loop or something similar to that. Video (BELOW) (sry for a long video, just wanted to capture it all). I can't start it normally nor my pc detects the phone... I tried a couple of recovery programs but A) They don't do **** B) They don't support S7 edge. So I tried to see if I could access the phone from called "odin screen" where you go when you root or mod your phone, but no luck there. So the only option I see is left to me, even that I don't want to, I need to somehow root the phone or do some "magic" that you guys know more about to access the phone memory and extract photos, if possible other data, to my pc. That is the main objective. The secondary is of course to fix the god damn phone, but even root kitty like me should handle that. P.S. Forgot to tell, but it's visible in the video - the LED is turned on with blue light all the time while it does that, even when I go to recovery screen or "odin screen".
Objectives:
MAIN:
A) Recover data.
Secondary:
B) Fix phone.
P.S. It's late for me, so I won't be able to try much today, so hopefully tomorrow after trying your suggestions something will work :good:
P.S.S. While making the video, I encountered a new bug, PHOTO (BELOW).
P.S.S.S. This phone was never rooted or moded, bought from a UK shop and used for 4 ish years.
P.S.S.S.S. As I'm new and can't post links... They are below:
Video - youtu.be/G5ru0VU3Epw
photo - imgur.com/KPTsNFW

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.