Hi guys,
I currently have to use my SPen to navigate my phone because my touch screen doesn't work.
Using TWRP is one of the biggest headaches in the world if you use an SPen to navigate because it's super sensitive and anything you hover your SPen over, will automatically open up and it happens in a blink of an eye.
I remember older versions of TWRP had a way to operate the phone via hardware keys (Volume Up and Down and Power).
I am not able to find much information about this anywhere online, I need this phone to last for another 2 months before I can replace it with something better.
Anyone have any idea how to get this version of TWRP without compromising having firmware issues by using something that is not meant for the Sprint Note 5?
Related
Well, I have a HipStreet Nova HS-7DTB1-4GB Chinese Tablet with Android v2.2 Froyo.
I don't know much about froyo but i think mine has stock rom with little modifications.
I am not getting any touch response from the phone. I faced this problem one before when i deleted the ILITEK Touch Utility (manages touch screen functions on my tablet) after rooting the phone, but physical buttons were working so i tried some combination of keys when powering on the tablet and one them worked and it said something like recovering your phone and it flashed back the original firmware back, so i think it has some kind of recovery mod.
But this time i was trying to manually update the ILITEK Touch Utility and the touch became immediately Irresponsive. now i cannot remember that combination of keys i used last time, i think i have tried all combinations but now it doesn't flash back the firmware, please help if you can.
The Tablet has A Power Button, Auto-Screen-Rotation Lock, Home Button, Menu Button, Volume Up and Down Buttons and A Back Button!
I am still new to android and don't know much about Android, So bear me if i look stupid to you
hey all, new moto g owner, great phone for the price and just unlocked the bootloader and rooted and I was wondering what recovery should i use cwm, twrp or just wait till the bugs get fixed?
CWM is the least buggy recovery at the moment and works well. The only bug people seem to be reporting is the date is incorrect on backups. The only downside is it is not yet CWM Touch. So you will need to use the volume rocker and power button to navigate the recovery menu.
TWRP is touch enabled at the moment, but it is nigh unusable as it stands. Touch inputs (tapping on a button) often times don't register and 9 times out of 10 when I was able to tap on something it just locked the screen again forcing me to spend another 2 minutes trying to unlock the damn thing.
That being said, once TWRP is made official or the touchscreen starts working it will be the recovery I'll be using. Backup sizes are smaller and the process is much faster. Not to mention the queue functionality is a big plus for me.
Yep, i second that, CWM is the best alternative for now.
Hi everybody! Hope someone can help me with this little problem.
A month ago I had a problem with the vibration on my One S, the engine was broken, so my uncle decided to change it by himself (the phone was bought via aliexpress). Then, there was a problem with the screen and he also changed it. At that moment the phone had CyanogenMod 11 installed.
The problem is that after reparing it, and when I change to a sense based rom, the optical keys for home, back and multitask aren't working, whereas those keys do work when I'm on TWRP or in CM 11.
Does anybody knows what may happen?
Hi guys, today my OnePlus broke, i think.
20 Minutes ago i was still using it normal.
Then, i turn the screen on and see this:
http://imgur.com/GP2563K
as you can see in the below video, the phone is completely operational, i can use whatsapp web from my pc and the colors of the stripes change according to what should be on the screen:
http://youtu.be/QlO-ttkmVms
i suspect that the gpu has a defect or maybe the connection to screen got loose, even though i did not drop the phone before this started.
the same thing is seen while booting and in the recovery, so it is not a problem with the os itself. what i need to know now, is:
-pictures of cwm so i can go to the backup menu and put a system backup on my pc and then wipe,
-how do i start an rma on the oneplus site? also i have rooted and unlocked the phone, how is one plus going to determine if that caused the error or not? (i know that is not the cause, but i want to be certain that i wont get denied my warranty)
-also if oneplus will send me a new phone, can i ask them to send one with the old backcover? i dont like the covers without the cyngn logo.
UPDATE: via https://code.google.com/p/androidscreencast/ i managed to start chromecast screenshare and now i can see the screen on tv. the image on tv and pc looks normal so maybe the screen is broken?
Hope you can get it fixed
Sent from my A0001 using XDA Free mobile app
~MaX~ said:
UPDATE: via https://code.google.com/p/androidscreencast/ i managed to start chromecast screenshare and now i can see the screen on tv. the image on tv and pc looks normal so maybe the screen is broken?
Click to expand...
Click to collapse
Try to going to fastboot (i know you see nothing but try it) and flash clean cm11s and then reboot the phone .....
Hope its not on HW ...
Strange...I heard about people who had problems with a green line which appeared random at the right / left side of the screen when they simply turned it on and that problem was something related to pixels and they solved it by playing a video (like this one https://www.youtube.com/watch?v=VN-KIlsxxOw ) for many hours. Try it and if this doesn't work then the only solution remaining before sending it to repair is a complete fastboot reflash of stock cm11s.
flash philz touch recovery which can be used with hardware buttons and to perform a backup do this:
1) press 3 times the back volume button (the button used to lower the volume when listening to music for example)
2) press home button (the soft-touch home button)
3) press again home button.
The recovery will start performig a backup...the phone will vibrate for 1-2 seconds when it will be done and it should last max 2 min (don't worry you will notice it). Anyway, since the philz touch recovery is cwm-based it could be that the buttons to press are the same for the original cwm recovery but it's a bit risky...
Now turn off the phone (keep the power button pressed for 10 seconds) then boot it again and plug it to to pc and you can find your backup files on the clockwormod folder.
Now you can perform the complete fastboot reflash. Good luck.
Hey guys,
strange and frustrating problem. I was using my phone pretty extensively today (although nothing crazy), mostly thanks to Pokemon Go. Tonight after using my phone normally, I went to press the power button to turn the screen off and nothing happened. I was able to reboot (by changing one of the long-press actions to bring up the power menu via GravityBox) and then was unable to power on the phone. It seems like my hardware power button has suddenly become unresponsive. This leaves me unable to power on/off the phone, including booting into the bootloader. Also, I seem to be unable to wake my phone up by double tapping the screen or swiping up.
The phone otherwise functions fine. If I get a notification, the screen wakes up and I can use the phone. Otherwise, the only way I've been able to get into the phone is by connecting it to a computer and issuing ADB commands. The IR blaster functions fine which makes me think it's not the hardware button?
Has this happened to anyone else before? Can the power button just break like that without any water / physical damage? The fact that I also can't wake the screen makes me think it's a software issue. One other thing I suspect is that my phone abruptly died yesterday (battery died despite software thinking it still had juice left). In the past, with the modified kernel / rom, this has resulted in some nasty issues, including 4G not working and the Android system process basically exploding. I thought I lucked out when I powered it on after that, but maybe it just took a day for this issue to manifest itself.
I'm going to make a NANDROID backup and try flashing a few different things to see if I can fix it. I'll post my progress here.
Current build:
- Verizon M8, S-OFF
- TWRP
- Android GPE 6.0 (MRA58K.H13)
Edit: I haven't been able to find a fix. I'm a bit afraid to try a full RUU since I can't use the hardware keys to reboot into the bootloader should something go wrong. It may just be that my PWR hardware button is f'd which really sucks. I'm not sure I'm up to cracking open the phone to fix it. In the meantime I downloaded an app called Gravity Screen On/Off which uses the phone's proximity sensor to wake the screen up and it seems to work ok for now.