[Q] Touch screen inop after boot - Nvidia Tegra Note 7

I restored my Advent vega note 7 using super tool 2.3 and i get no feedback from the screen, stylus doesnt work neither does my touch gestures, any reason why? Happens when i reboot the device from complete shutdown and occasionally i get lucky where everything works. PLEASE HELP.
Did notice when it powers up it boots twice flashing the Advent vega banner with nvidia animation. and after it boots (touch inop) I can put it to sleep twice and if I press the power button the third time it reboots.

Had a similar issue myself. Doing a soft reset via the backup and reset option in settings cured the issue, also make sure you are booting the tablet with the stylus in, only take it out once the tablet has booted. I've had strange behaviour if I boot with the stylus out.

Related

[Q] MIUI-1.6.10-demonSPEED-v1.1, WILL NOT BOOT

So as the title says i currently have MIUI 1.6.10 demonSPEED v1.1 ROM and it is not booting, just completely unresponsive to everything i could think of. Im just throwing this out there to see if this has happened to anyone before or if there is a way of fixing this issue. I don't believe it has anything to do with thederekjay's rom just some unfortunate event. Anyway i fear it is possibly bricked and that i am gonna have to shell out the $150 to get a new mt4g from the insurance. Details follow...
So have had this rom for about a week now and has been working great. However this morning i was on the browser reading the news and it became unresponsive. After i let its display turn off (i just left it alone) i used the track pad to wake it. It was slow but it did show me the lock screen. When i attempted to unlock with a swipe down i felt the vibrations but the slide lock didn't budge. I then tapped the power button to turn the display off and tapped the power button once again to turn it on but nothing, just stayed black. I tried a soft reset by removing the battery, placing it back in, and powering back up. When i did so the t-mobile mytouch 4g boot image w/ the white background came on then went to an android image (lighting up a through d, looping) but then it just remained at the android image for five minutes! So i tried a soft reset again but the same thing would happen, act like it was gonna boot up completely but then gets stuck at the android image. So then i tried removing the battery and booting into recovery (via power, vol down, trackpad) that time the t-mobile mytouch 4g image would appear but after that the screen went black and after that every attempt with either the soft reset or boot into recovery wouldn't do anything at all, just a black screen as if the battery wasn't in at all. Its been like that all day and i can't figure it out so if anyone knows some info i would greatly appreciate it thanx

Start problems in 3.2.1?

Hello xda people!!
After updating to 3.2.1 my 16 GB TF, I discovered having problems when trying to start the tablet in totally off mode, screen gets totally black but the system seems loading in background, after a while, I can push power button and the screen goes on, when I need to unlock screen to start working
I did a factory reset, turn on the tablet, left in standby mode and then, push the power button and nothing happens: screen dark, no matter how many times I pushed the button, so, I need to get pressed, power off and start again...
You're having problems like that because of the update? My tablet is broken and need fix?
I have restarted my tablet tree or four times after updating, bith before and after a factory reset, and haven't experienced this issue. Maybe a power button issue? Or just a SW issue. You could try flashing a custom ROM and see if the bug is still there.
Regards.

[Q] Boot issues (loop, power button not working)

Hey everyone,
My mother's HD2 is having some boot issues. She's running tytung's Nexus HD2 rom version 2.9.
Every once in a while, when she attempts to turn it back on, the power button will not do anything. I know the battery is not the issue, because when I get it turned on by plugging it into a charger/computer (causing MAGLDR to boot automatically).
However, when this happens (and I plug it in to boot it), I run into something of a boot loop. It runs through the initial T-mobile splash screen, through the MAGLDR boot screen, to the HTC boot screen - before I get to the Nexus boot animation, the phone starts back at the T-mobile splash screen again. And, whenever I disconnect the cable from the phone, the whole sequence stops, and the phone turns off, unresponsive to the power button.
If I take out the battery and put it back in, I can typically get it to work just fine. However, this does not always work.
Ideas? All help would be appreciated. Thanks!
I've heard about hardware issues with the power button, might be that.
In any case, I'd recommend backup and reflashing the rom. By that you can find out, if the issue is still there after reflash - whether it's software or hardware based.
Hope it helps.

[Q] turning screen off crashes phone

I have the strangest damn problem on my phone. Sometimes, when I press the power button to turn the screen off, the phone just shuts down completely and then when I try to reboot won't get past my splash screen. When this first happened I couldn't get the phone restarted at all, even by taking the battery out and waiting for over 10 minutes. Everytime I tried booting it would go to the splash screen and then blank back off. It would do this once and then I had to remove and replace the battery just to get it to boot to the splash screen again. I thought this might have something to do with having a custom rom installed (sacs custom), so I played around with the phone and managed to get it in Odin mode. I then brought the phone back to stock. Everything worked so I figured I had fixed it, but then after pressing the power button one time I got back the same problem. It shutdown and would not restart past the splash screen. In retrospect, I think when I pressed the power button the screen did not immediately go off and so I clicked it a couple times in a row before it crashed, that may be what triggers it, b/c sometimes i press the power/screen button and it goes off without incident.
So, now I had the phone back to stock and had the same problem. It turned off and would not boot past the splash screen. By a stroke of good fortune I figured out how to get the phone booting again past the splash screen. When the splash screen came up, I started repeatedly touching and swiping at the phone; drawing little circles tapping at it, etc... When I did this the phone continued to load and boot up normally.
I installed AVG antivirus, to see if maybe there was malware on my phone. Scans showed nothing. I updated all of the software as well. I now have an app installed for turning off the phone instead of using the power button. This of course is not an ideal situtation, why should pressing the power button crash my phone like this??

Phone crashes, reboots, and no longer displays anything on the screen when unlocked

Started happening yesterday:
1. Phone randomly rebooted
2. Once rebooted it shows the lock screen. When I try to unlock with pattern or fingerprint the unlock sound is made and the entire screen goes black.
3. I press the power button, and the screen turning off sound is played. I press it again, the lock screen comes back up.
4. Attempted resolutions:
Reboot - Didn't help
Plugged into power / PC - Didn't help
Safe mode - Didn't help
Reinstall Rom - Helped for ~12hrs the first time. Now, not helping
Any ideas on what this problem is?
Running Pure Nexus and Franco Kernel. Been on the same ROM version/Kernel for over a month with no issues. If it matters, both times this started happening my phone was in my pocket (Empty, nothing else in the pocket)
Could this be a third party app causing the problem? If so, wouldn't safe mode work then?
Thanks!
Logcat attached
Update: I waved a magnet over the bottom right corner of the phone and now it's working again. I use a magnetic car mount for my vehicle, is this breaking my phone?
Have you tried flashing to stock, including stock boot.img, to eliminate a hardware issue?

Categories

Resources