Hi!
I've started to have problems with my home button sometimes not working. Also fingerprint sensor stops working same. This started to happen lately and it happens more every week. I've tried with many roms fully clean installed (also data formatted), with ob 28-30 and 9.0.4 firmwares. Now my fingerprint scanned doesn't work at all in crdroid. and in los it works for a few minutes. On omni and Aicp i haven't had any problems. On Oxygen roms it is fully random, sometimes work. It once happened on clean ob30 install so i fear it's a hardware based issue, but i still want to hear your opinions.
I tried unbrick tool that flashed stock 9.0.4. Fingerprint scanner and home button worked great until first reboot. After that, nothing. Tried another rom clean install, no go. Installed 9.0.4 clean from twrp. Fingerprint and home button worked, until first reboot. What is really going on?
Edit: When fp scanner and home button stops working after reboot, also self-test fails instantly in *#808#
Vika__ said:
I tried unbrick tool that flashed stock 9.0.4. Fingerprint scanner and home button worked great until first reboot. After that, nothing. Tried another rom clean install, no go. Installed 9.0.4 clean from twrp. Fingerprint and home button worked, until first reboot. What is really going on?
Edit: When fp scanner and home button stops working after reboot, also self-test fails instantly in *#808#
Click to expand...
Click to collapse
My opinion: More likely a hardware issue if self test fails.
That was my fear too, well. Have to rip few euros and buy a new fp scanner. Hopfully that one solves it
Interestingly, if i hold fingerprint scanner and press self test, it passes. After that home button and fp scanner works for a few minutes, but very slow. Have to hold button about 2 seconds to get home command
Related
A few months back, I broke the digitizer on my AT&T G2, and the bottom 5th of the screen stopped registering touches. Which sucks when you have on screen buttons. I was on CM11 at the time, so thankfully I was able to unlock the screen just fine and use screen rotation (combined with the Rotate app) to do almost everything I needed. One time I even did a wipe and clean install of CM11 and was able to use screen rotation to re-set up my phone to how I needed it.
Today I did a clean wipe and flashed CloudyProII 2.0 onto my phone, assuming I could do a similar set-up. Everything went well until the first screen, which has a next button at the bottom and doesn't rotate. I'm not able to pull down the menu bar, and since this is a clean install, ADB is off, and my google account isn't set up. So I decided to just reboot to recovery and re-flash CM11. Only for some reason the LG G2 button combo to reboot to recovery isn't working (maybe CloudyProII removed my custom recovery?), though the Download Mode combo is (and confirms I'm rooted still).
So now I'm stuck with a phone I can't use, and I'm sure there's an easy solution that will get me up and running again. If anyone can offer any advice, I'd be tremendously grateful!
EDIT: I was able to get into recovery and all is good now! Nevermind!
milespordeo said:
A few months back, I broke the digitizer on my AT&T G2, and the bottom 5th of the screen stopped registering touches. Which sucks when you have on screen buttons. I was on CM11 at the time, so thankfully I was able to unlock the screen just fine and use screen rotation (combined with the Rotate app) to do almost everything I needed. One time I even did a wipe and clean install of CM11 and was able to use screen rotation to re-set up my phone to how I needed it.
Today I did a clean wipe and flashed CloudyProII 2.0 onto my phone, assuming I could do a similar set-up. Everything went well until the first screen, which has a next button at the bottom and doesn't rotate. I'm not able to pull down the menu bar, and since this is a clean install, ADB is off, and my google account isn't set up. So I decided to just reboot to recovery and re-flash CM11. Only for some reason the LG G2 button combo to reboot to recovery isn't working (maybe CloudyProII removed my custom recovery?), though the Download Mode combo is (and confirms I'm rooted still).
So now I'm stuck with a phone I can't use, and I'm sure there's an easy solution that will get me up and running again. If anyone can offer any advice, I'd be tremendously grateful!
EDIT: I was able to get into recovery and all is good now! Nevermind!
Click to expand...
Click to collapse
you can always get a usb otg + mouse and us your phone like that or replace the screen
Hi,
I am having a kind of weird issue with my Oneplus 5.
At first I used LineageOS but decided to switch to OmniROM because of signature spoofing. That worked but OmniROM asked my for an encryption pattern right after the first boot and didnt accept the one I had before, so I googled and deleted the locksetting files in /system ( I am not sure if this is relevant for the problem). But when I rebooted OmniROM started but then it showed a black screen but the volume control overlay is visiable when I press the volume buttons and also the shutdown overly is functioning when I press the power button and the screen flashes and shows the real screen when I press the Back Button.
I tried wiping Chache (and System and data) and tried installing LineageOS and OmniROM several times but its always the same error.
Some people seemed to have similar problems but the suggestions didnt work for me:
https://forum.xda-developers.com/oneplus-5/help/black-screen-pin-code-t3654329
https://forum.xda-developers.com/oneplus-5/help/op5-dead-t3655315 ( I did not try to install the linked zip because I have no idea what it does)
Any suggestions for me, please?
thanks in advance
Sounds like the problem is the encryption of the internal storage, I'm not a pro, but it seems like a full wipe is the only way to go.
By that I mean everything, including the internal storage, but let's wait a little till others respond.
I fixed it. I did a a reset to HydrogenOS with the official Unbrick Tool and this guide:
http://www.droidviews.com/unbrick-oneplus-5-using-the-official-unbrick-tool/
This should be linked somewhere here on xda.
Hey guys,
So today I rooted my T580, 7.0 for the first time using this guide and I installed couple of apps I saw most people were using including some xposed modules.
Everything was working just fine til the moment I decided to add 'Draw unlock pattern' on my tablet to unlock it.
As soon as I put it to sleep and tried to unlock it, it just won't unlock, even though it recognizes the pattern is correct.
I draw the correct pattern, it hangs for about 2 seconds it puts the tablet to sleep again. I can't even shutdown the tablet because it asks me to draw the pattern.
What can I do to fix this?
jruivo said:
Hey guys,
So today I rooted my T580, 7.0 for the first time using this guide and I installed couple of apps I saw most people were using including some xposed modules.
Everything was working just fine til the moment I decided to add 'Draw unlock pattern' on my tablet to unlock it.
As soon as I put it to sleep and tried to unlock it, it just won't unlock, even though it recognizes the pattern is correct.
I draw the correct pattern, it hangs for about 2 seconds it puts the tablet to sleep again. I can't even shutdown the tablet because it asks me to draw the pattern.
What can I do to fix this?
Click to expand...
Click to collapse
Hold the Home, Vol down and Power buttons for about ten seconds. As soon as the screen goes black, switch your finger from the Vol down to the Vol up button. This should put you back into TWRP where you can reflash and start over. You have to be quick shifting from Vol down to Vol up or the tablet will boot to download mode instead of TWRP. If it does, then do the same thing again but switch faster.
jruivo said:
Hey guys,
So today I rooted my T580, 7.0 for the first time using this guide and I installed couple of apps I saw most people were using including some xposed modules.
Everything was working just fine til the moment I decided to add 'Draw unlock pattern' on my tablet to unlock it.
As soon as I put it to sleep and tried to unlock it, it just won't unlock, even though it recognizes the pattern is correct.
I draw the correct pattern, it hangs for about 2 seconds it puts the tablet to sleep again. I can't even shutdown the tablet because it asks me to draw the pattern.
What can I do to fix this?
Click to expand...
Click to collapse
If you have twrp installed its pretty easy to remove the pattern lock.
https://forum.xda-developers.com/redmi-note-4/themes/tool-remove-lockscreen-password-pin-t3692411
Thank you everyone, I was able to use the TWRP and restored a backup. I thought it was some app incompatibility but apparently none of the secure lock-screens work with SuperSU, they all mess it up and I end up restoring the tablet.
Hi
RP2, GSI roms (I tried three: LOS 17, NitrogenOS, RevenageOS), arter97-kernel-r12, Magisk-v20.3
I am installing a GSI ROM, the system is working. after the third or more reboot, the phone is booted to a black black screen.
Wipe all data, phone booted.
doing something simple (install software from google play,restore data from old device via google restore)
restart
phone booting to blank black screen with sound. computer (USB) recognized the phone.
Tried with Magisk, withour Magisk, restored vendor.img from origin (I was deleted the two apks for BT).
clear data
phone booted
restore
blank again
where to start debug it ?
Same problem with me, I had my phone on phhusson treble ROM (android 10) then went back stock and hated it....tried to flash the phhusson treble ROM again and she boots but to a black screen, you can hear via sound it's up just the screen is black....let me know if ya finger anything out
DaveyBoy2002 said:
Same problem with me, I had my phone on phhusson treble ROM (android 10) then went back stock and hated it....tried to flash the phhusson treble ROM again and she boots but to a black screen, you can hear via sound it's up just the screen is black....let me know if ya finger anything out
Click to expand...
Click to collapse
did you tried Android 9 ROMS or this is only 10 problem?
I was rooted and installed Magisk on the stock, I hate the stock like you but it works.
Haven't tried a android 9, I'm back at work and used 4gb of data screwing around yesterday trying to get things fixed so I gotta go easy today ?
moshe_lm said:
Hi
RP2, GSI roms (I tried three: LOS 17, NitrogenOS, RevenageOS), arter97-kernel-r12, Magisk-v20.3
I am installing a GSI ROM, the system is working. after the third or more reboot, the phone is booted to a black black screen.
Wipe all data, phone booted.
doing something simple (install software from google play,restore data from old device via google restore)
restart
phone booting to blank black screen with sound. computer (USB) recognized the phone.
Tried with Magisk, withour Magisk, restored vendor.img from origin (I was deleted the two apks for BT).
clear data
phone booted
restore
blank again
where to start debug it ?
Click to expand...
Click to collapse
Yea I've had the same results as well.
Try Havoc and PE from these links. They are phhusson based and work with some bugs but at least you can boot up after the third time
https://sourceforge.net/projects/expressluke-gsis/files/
moshe_lm said:
did you tried Android 9 ROMS or this is only 10 problem?
I was rooted and installed Magisk on the stock, I hate the stock like you but it works.
Click to expand...
Click to collapse
SO! got home from work, flashed the rom that i was having issues with (phhusson's android 10 build) BAM, booted just fine, did the whole big restore thing, figured this was going TOO well so i figured i better test a restart.....and BAM black screen, lock sounds, everything just nothing on the screen. so I volume down & powered till it reboot....and the screen is back!.. so why does it need this? idk but atleast it gets me workin with android 10 again!
DaveyBoy2002 said:
SO! got home from work, flashed the rom that i was having issues with (phhusson's android 10 build) BAM, booted just fine, did the whole big restore thing, figured this was going TOO well so i figured i better test a restart.....and BAM black screen, lock sounds, everything just nothing on the screen. so I volume down & powered till it reboot....and the screen is back!.. so why does it need this? idk but atleast it gets me workin with android 10 again!
Click to expand...
Click to collapse
It is working after second restart ? or one time ?
moshe_lm said:
It is working after second restart ? or one time ?
Click to expand...
Click to collapse
If you want/need to restart if you do it via the power button then hitting restart, it will boot to a black screen. But if you hold the power and volume down till it reboots, it'll boot perfectly. Happens every time for me
DaveyBoy2002 said:
If you want/need to restart if you do it via the power button then hitting restart, it will boot to a black screen. But if you hold the power and volume down till it reboots, it'll boot perfectly. Happens every time for me
Click to expand...
Click to collapse
volume down isn't go to fastboot mode ?
moshe_lm said:
volume down isn't go to fastboot mode ?
Click to expand...
Click to collapse
Not if you let go when you see the screen turn off, then it's just a dirty restart I guess?
In my case, it only happens when you use the Encrypt password to start the device.
So I suggest skipping the encrypt part on startup setting and the problem should gone.
*Sorry for my bad English.
In my case, Don't use the "Secure start-up" thing when you set up your phone in Android 10.
Nor It will mess and cause a black screen on your device.
I also tried several custom ROMs on the device. In most cases, after the device enters sleep mode (initially after 1 minute), it is no longer able to wake up with either the power button or the fingerprint reader. It doesn't matter if it's LineAgeOS or another ROM. If I remember correctly the xiaomi.eu ROM was a little better because it didn’t always do that.
I also tried several types of recovery ... TWRP, Orange Fox, etc ... different versions as well. If I want to turn on the display, nothing happens. Only the notification LED works. After a hard reset (8-10s power button press), I can only use the system until it goes back to sleep mode. Neither calls nor messages wake it up, and the device is not available during a call.
I just flashed the factory ROM, it works perfectly without error. So I don't think it's a hardware failure. The joke is that it don’t wake up the same way with Ubuntu Touch. Anyone have any ideas?
Have you tried to switch off "Prevent Accidental Wakeup" setting in whichever Custom ROM you have installed?
asifzbaig said:
Have you tried to switch off "Prevent Accidental Wakeup" setting in whichever Custom ROM you have installed?
Click to expand...
Click to collapse
Now this error also exists with the factory ROM. I will check this option. Thanks!