So my 10 was working fine yesterday on an older LinageOS release. However, today it had a software issue, so i thought it time to update and do a clean to the latest linage release and open gapps.
Now, i cannot swipe the notification bar down and using a screen test app, it appears the top of the touch screen is not registering touches.
I think it must be hardware, but thought id shout out here incase any one else has ever had this issue and managed to resolve in software?
As a work around, ive setup Nova and down swipe to open the notification bar, not great but at least its usable.
Mine is fixed yaaay
I had the same issue the upper 15% doesn't work...
A week ago I did a command from the PC to lower the screen so i can use the device:
adb shell wm overscan 0,0,0,260
Today I wanted to revert back to full screen instead of using only 85% so i did the command with default values:
adb shell wm overscan 0,0,0,0
Now it is working with no issues so i can confirm it is not hardware fault must be software.
If anyone has the same issue try the first command and reboot the phone the use the second command. (You need a PC with adb installed)
Good luck
Thanks, tried and it dosnt work on mine. Here is a image of a screen draw test, is this the same area that failed on yours?
best image host
Related
Hello,
I'm new to the Android scene and already I have a problem.
I successfully upgraded my HTC Magic with Cyanogenmod.
I did it exactly like it said in the instructions on cyanogenmod wiki.
Installed Android SDK R05 for Windows and used:
bc-4.2.15.1-ebi1-signed
recovery-RA-sapphire-v1.6.2H.img
update-cm-4.2.15.1-signed
DRC83_base_defanged
HTC_ADP_1.6_DRC83_rooted_base
So i did the magic on Magic and the CyanogenMod worked, at least until recently.
My co-worker asked me to lend him my sdcard so i opened the magic and took out the sdcard from my htc that was on while i did that.
Than the trouble came forth...After a reboot the phone started booting for a long time...than it showed an error that the sdcard wasn't unmounted properly, and it didn't go away even when i inserted the sdcard back in, even after a hundred or so reboots. Than it started to crash the processes (acore and such)
Than after a milionth reboot the screen and the accelerometer stoped working, soon after that the keys followed the screen and the acc. I was thinking maybe the screen and the keys stoped working permanently and wanted to throw the phone away. But after another optimistic restart the keys worked for some time than the ball when pressed stoped responding...so i could highlight an icon on the home screen but couldn't start it. Than i accidentaly pressed it on the screen and it worked, but shortly after that everything was dead again. Than the phone started rebooting on a low battery. When rebooting to bootloader (with the battery fully charged) the screen flashes and nothing responds. But it still shows in a flash those three androids on the skates. And i can't seem to adb push the recovery.img to the sdcard...states some Read only problem. Sdcard seems alright through the card reader. So that is about it of all the problems.
So i was hoping some experts on here could give me some feedback on the device. Is it finished or can I rescue it. I really fell in love with this phone so I would much rather here the second option. I'm attaching the log from adb logcat if it is for any use to any of you...
Thanks in advance
So, after 2,5 years of great joy of using my HOX, last weekend it fell down, and the screen broke.
I asked about the replacement, but it seems a bit costly (compared to the phone value), so I might as well forget about it.
I am already looking for a replacement.
The problem I have is that inside my HOX i have many very important as well as sensitive information. As the thread title say - could anyone help me with rescuing them?
The phone was running SlimKat 9, so maybe @teemo could have an idea
I remember @geko95gek, and @Goku80 used to deal very well with HOX.
Although I have some experience in flashing, this looks quite difficult, because ADB doesn't rcognize my phone in ON state. Fastboot commands work just fine in bootloader mode, but ADB refuses to cooperate.
What do I need:
- access to sdcard to take out some data.
- SMSes
Any help/advice/assistance is more than welcome.
Update - I managed to access sdcard through adb, so at least this part is put to sleep.
Still, ab is giving me "access denied" or something like that when I try to access data partition to extract mmssms.db and another file from an app that created it (AK Notepad notes which are of extreme importance to me).
I found some instructions that I should provide adb with root access, but I cannot as I can't recognize anything on my screen even though the touch is working.
Also, as I remember Slim KAT 9 has y default root access to adb and usb (@teemo could you confirm this, please?).
Any advices?
I have a bone stock 2013 Nexus 7 32 Gb Wifi, never had a problem with it. A few weeks ago, it notifies me of an update (Lollipop) so I apply it. Nothing but problems since then. It was very laggy and would glitch every few seconds while playing video (either local files or streamed over Plex, both had same issue). Sometimes when I'd wake it from sleep, the screen would look like an old CRT TV with static (except it wasn't moving, it was a fixed image). It would hang like this for seconds or sometimes minutes. Rebooting would usually resolve this for a while.
Tried a few 'lollipop tuning' tweaks, but when these failed to fix the video glitching and lagginess, I decided to revert to kitkat and followed an online tutorial (exactly like the one here except it had me install a standalone ADB/fastboot instead of full SDK) . No problem installing USB driver or setting nexus into USB mode. No problem getting it into fastboot mode and "fastboot devices" correctly listed the device, and "oem unlock" appeared to work fine as well. Running the flash-all batch file also seemed to go normally. But now my device is even worse than before:
- won't boot/run normally... no boot-up logo or video ever displays (or if it does, it's just a partial static image). Appears to get to a 'welcome' screen but the display is all messed (part of the screen is just repeated several times, so you can't see the entire screen). Unresponsive to touch, though it will make some sounds when you press in certain areas, but the display never changes. If I sleep it and wake it up, it shows the 'CRT static' mentioned above for many seconds before showing slowing showing the tiled/corrupted welcome screen. I can access the nexus' file system over USB on my PC even while it's in this borked state.
- display is now blank when getting into fastboot mode... i can time pushing the down-volume and power button so I know I am in fastboot mode ('fastboot devices' correctly lists the device) but the display is now completely black (not on, no backlight) in this mode.
I tried flashing to factory 4.4.4, 4.3, and 4.2 (always using 2013 wifi images) and it doesn't make a difference. Same results. Is there some bit of code that doesn't get reflashed during this reset that could explain why I'm having these issues? Any advice how to fix?
flyingsherpa said:
I have a bone stock 2013 Nexus 7 32 Gb Wifi, never had a problem with it. A few weeks ago, it notifies me of an update (Lollipop) so I apply it. Nothing but problems since then. It was very laggy and would glitch every few seconds while playing video (either local files or streamed over Plex, both had same issue). Sometimes when I'd wake it from sleep, the screen would look like an old CRT TV with static (except it wasn't moving, it was a fixed image). It would hang like this for seconds or sometimes minutes. Rebooting would usually resolve this for a while.
Tried a few 'lollipop tuning' tweaks, but when these failed to fix the video glitching and lagginess, I decided to revert to kitkat and followed an online tutorial (exactly like the one here except it had me install a standalone ADB/fastboot instead of full SDK) . No problem installing USB driver or setting nexus into USB mode. No problem getting it into fastboot mode and "fastboot devices" correctly listed the device, and "oem unlock" appeared to work fine as well. Running the flash-all batch file also seemed to go normally. But now my device is even worse than before:
- won't boot/run normally... no boot-up logo or video ever displays (or if it does, it's just a partial static image). Appears to get to a 'welcome' screen but the display is all messed (part of the screen is just repeated several times, so you can't see the entire screen). Unresponsive to touch, though it will make some sounds when you press in certain areas, but the display never changes. If I sleep it and wake it up, it shows the 'CRT static' mentioned above for many seconds before showing slowing showing the tiled/corrupted welcome screen. I can access the nexus' file system over USB on my PC even while it's in this borked state.
- display is now blank when getting into fastboot mode... i can time pushing the down-volume and power button so I know I am in fastboot mode ('fastboot devices' correctly lists the device) but the display is now completely black (not on, no backlight) in this mode.
I tried flashing to factory 4.4.4, 4.3, and 4.2 (always using 2013 wifi images) and it doesn't make a difference. Same results. Is there some bit of code that doesn't get reflashed during this reset that could explain why I'm having these issues? Any advice how to fix?
Click to expand...
Click to collapse
So your bootloader is blank right? I would flash a new bootloader asap! And see if that fixes anything
noahvt said:
So your bootloader is blank right? I would flash a new bootloader asap! And see if that fixes anything
Click to expand...
Click to collapse
I have to confess my ignorance here... I'm brand new to flashing android like this so I don't know the answer to your question. If part of tutorial I followed blanks out the bootloader (and doesn't write something in?)... then you're probably right. I shall look into this more tonight when I'm at home with the nexus. Thanks for at least giving me something to look into, that's exactly what I was hoping for!
This sounds more like a hardware issue than software to me. See if you can get a warranty repair or replacement.
From another thread by a user with a blank screen like yours:
Asus_USA said:
a7medmo7eb - We're very sorry to hear of this. Kindly email us at [email protected] with this copied problem description along with the serial number of your tablet and we will do our best to provide you with troubleshooting and servicing options.
If you have any further questions, comments or concerns please do not hesitate to let us know. We will be more than happy to assist you. Once again, thank you for choosing ASUS products and services.
Thank you.
-In Search of Incredible-
Technical Support Department
http://www.asus.com :: http://service.asus.com/
Click to expand...
Click to collapse
nhizzat said:
This sounds more like a hardware issue than software to me. See if you can get a warranty repair or replacement.
From another thread by a user with a blank screen like yours:
Click to expand...
Click to collapse
Thanks, you're probably right. I did read up to understand all this stuff a bit more, so I know it's not lack of a bootloader or anything. All img files install just fine, so my pc can talk to the nexus, just the screen is all wonky no matter what i do.
Unfortunately I bought this 1.5 years ago so I don't think it's under warranty anymore. Everything was fine until I updated to Lollipop! Seems a big coincidence that I had a hardware failure at the same time as that update... I feel like Google ruined my tablet...
There is a bug where sometimes when you unlock the bootloader it zeros out the data partition. This might be the cause of your problem. It happened to me when I unlocked mine and I got stuck in a bootloop where it kept booting into recovery then shutting off. I fixed the problem by using fastboot to format data. Also, the flashall script didnt work for me. I put all the .img files in the same folder as fastboot then used these commands.
fastboot format data
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
after this I booted into recovery and did a factory reset for good measure and the problem was fixed. This may solve your problem. It may also be possible that you got a bad download. I hope this helps you
Masterchief87 said:
There is a bug where sometimes when you unlock the bootloader it zeros out the data partition. This might be the cause of your problem. It happened to me when I unlocked mine and I got stuck in a bootloop where it kept booting into recovery then shutting off. I fixed the problem by using fastboot to format data. Also, the flashall script didnt work for me. I put all the .img files in the same folder as fastboot then used these commands.
fastboot format data
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
after this I booted into recovery and did a factory reset for good measure and the problem was fixed. This may solve your problem. It may also be possible that you got a bad download. I hope this helps you
Click to expand...
Click to collapse
Hmm, thanks for the idea, but fastboot wouldn't do "format data", giving me the error: Formatting is not supported for filesystem with type ' '
Googling that makes it not look good. Weird, thing is, it still technically boots up, just the screen is so wonky you can't see where you are or interact with it properly. Not sure what else to try (opening it up and re-seating touchscreen cables?).
For me and some users, while typing, or even scrolling up and down, time to time we see black virtual cursor for 0.5 sec
It's show ups for me about 10-100 times a day, very annoing!
I have seen this bug on every custom roms like RR 5.8.2, lineage os 14.1, Purenexus, etc, installed by TWRP 3.1.0-1 by nijel8/3.1.0.0 official one by strix
Changing different firmwares 7.2.9-7.3.16 - not helped.
Did a clean install throuth Mi flash tool - not helped.
Any ideas, how to fix this bastard?
Could it be recovery or even hardware problem?
If it were indeed a hardware issue, wouldn't we be seeing it on stock miui as well?
I suppose we need a common denominator - something that the custom roms have, but miui doesn't.
1) could it be related to root permissions? Has it been seen on both rooted and non-rooted devices?
2) Does it depend on how the ROM is flashed?
3) Has it been seen on other xiaomi phones? I assume both hydrogen and helium are impacted
just thinking out loud, what if we disable HID client drivers or the entire mouse support in kernel?
lukacsp said:
just thinking out loud, what if we disable HID client drivers or the entire mouse support in kernel?
Click to expand...
Click to collapse
Already tried and not helping.
Let start by taking some setup info and logs, guys. Make sure you have ran phone for a while and have seen cursor appearing at least few times. Run these commands on PC with phone USB connected:
Code:
adb shell dumpsys > c:\dumpsys.txt
Code:
adb shell dmesg > c:\dmesg.txt
Code:
adb shell logcat -d > c:\logcat.txt
or run their respective equivalents on phone terminal emulator...
Zip those files and post them here.
Haha I just saw the black mouse cursor pop up for a split second on my Helium running Pure Nexus. It's really not a big deal though. I'm sure it will eventually be fixed. It only pops up for like one tenth of a second. I'ts not even annoying but kind of funny.
Never seen it on my helium , on any Rom but then again i don't really stare at the screen looking for a cursor haha
Sent from my Mi Max using Tapatalk
Happening on Hydrogen RR5.8.2 - been happening on a few builds every now & again; annoying but not a deal breaker.
never seen on NitogenOS, but I saw it last day when I was trying nijie8's lineage, scroll up/down on the settings' About phone when back from about lineage.
Helium 3G/64G.
nijel8 said:
Already tried and not helping.
Let start by taking some setup info and logs, guys. Make sure you have ran phone for a while and have seen cursor appearing at least few times. Run these commands on PC with phone USB connected:
or run their respective equivalents on phone terminal emulator...
Zip those files and post them here.
Click to expand...
Click to collapse
I decided to clean flash your latest lineage 14.1 rom build 27.03.17 via your latest twrp 3.1.0-1, with latest firmware 23.03.17, and latest pico gapps 01.04.17
magic is happen, idk how, but for 3-4 days, I didn't see this mouse cursor bug at all... only one app that I didn't install is Google app for Google now (don't think that is a reason). BTW mb last kernel setup with hot plugging small cores give us instability and bugs ?
Will check for a while and get feedback if something changes.
It's a bug reported on Lineage's Jira. Here it is https://jira.lineageos.org/plugins/servlet/mobile#issue/REGRESSION-214
nijel8 said:
Already tried and not helping.
Let start by taking some setup info and logs, guys. Make sure you have ran phone for a while and have seen cursor appearing at least few times. Run these commands on PC with phone USB connected:
or run their respective equivalents on phone terminal emulator...
Zip those files and post them here.
Click to expand...
Click to collapse
After a free week of mouse cursor bag, I decided to reboot device..
After rebooting this bug coming back in 2-3 minute... WTF )
It happens to me on Pure Nexus which leads me to believe it's not a Lineage bug.
ajsmsg78 said:
It happens to me on Pure Nexus which leads me to believe it's not a Lineage bug.
Click to expand...
Click to collapse
We should to get some logs to nigel to fix this bastard
Get notice it on NitrogenOS v20170330...
Who used Android 7.1.2, bug still there ?) For a while, im coming back to MIUI Android 7, coz of this annoying bug
Resurrection Remix 7.1.2 Helium. BLACK VIRTUAL CURSOR CONFIRMED
Lineage OS 7.1.1-7.1.2 Helium. BLACK VIRTUAL CURSOR CONFIRMED
i noticed a battery drain since i first noticed the black cursor problem.
i started to think it is a stuck background process that kills battery. ( am i being so psychopath ? )
No cursor here. RR 5.8.3 on Helium. 7.4.13 firmware.
I have not seen the cursor in the last 11 days after enabling Settings -> Accessibility -> Large mouse pointer.
No i m not infected on any rom
I also occasionally see it. I am on stable MiUi 10 stock rom, but rooted with twrp & magisk
ETA: I don't see a way to delete this topic so I'm just updating it. I didn't want to risk waiting another day to not have an answer since I'd already posted other places over the weekend with no response and we need it working for tomorrow morning, so I just went ahead and flashed the factory image from here:
https://developers.google.com/android/images
Everything is in order now! Tips for anyone else doing this, don't skip the step of adding the platform tools to the path environment variables. I did the first time and the flash script wasn't able to find some files because of it and aborted. Everything pushed to the tablet and installed fine after I added the tools folder to system variables.
**********************************************************
This is the only place where I see detailed answers so I registered to ask this.
Status locked/not rooted, just however I bought it when it released plus whatever OTA updates before I stopped using it. Dead in a drawer for maybe two years, I got it powering on again by disconnecting/reconnecting the battery then charging on my PC overnight via USB, but it kept booting to a black screen, no logo, no splash.
I went into recovery mode and did the wipe data/factory reset. I can now get to the welcome setup screen but there are two problems:
1) Errors immediately pop up blocking the screen, making it hard to choose anything because as soon as I hit ok to make an error go away, another pops up. It bounces between "android.process.acore/gapps/media has stopped" with "calendar has stopped/email has stopped" sometimes appearing too but it's mainly the first ones.
2) If I'm fast enough after dismissing an error, I can click next from the language screen to the wifi connection screen. SKIP is greyed out. I can select my wifi but when the password prompt comes up, no keyboard appears after clicking the field to enter one. It's just the blinking cursor.
Keep in mind the errors are still popping up too so I don't know if they're blocking things. I sometimes used a bluetooth keyboard with it, so I grabbed that and tried typing with it just in case and no luck.
Attempts​
I found a fix to try sideloading a factory image via the apply update via adb option in recovery mode, but the google site said it's safer to try sideloading a whole image OTA, so I tried that instead using the zip file there for Nexus 7 2013 wifi (I have 1st Gen but don't see that anywhere so this may be the issue too). After it hit 100% it was aborted for some reason I can't remember now.
But I do remember when I looked up whatever it said, most responses were that sideloading a whole image OTA won't work on devices that haven't been "unlocked" or something.
I found another response to someone with my problem, not having a keyboard after resetting, which said to sideload a keyboard app through adb. I found some gboard apk listed as the version for the Nexus 7 but when I did the adb thing, it aborted because of something to do with e-signature not being verified.
Question​
I can figure out trying to copy over a factory image but since I suspect the main issue now is the Nexus not having wifi access to complete setup then update/install what it needs to stop those errors, I consider that a last resort. So my question for now is for further help on getting a keyboard app or another way so I can type. If I still can't get things working after that, then I'll ask about the factory image.
Thanks!