Phone info:
Off-brand chinese phone
MT6582
Android 4.4.2
Kernel 3.4.67
Capacitive home button
16MB recovery partition
Google play identifies the phone as "Alps"
I installed TWRP 2.8.2.0 on my phone using the MT TWRP installer http://forum.xda-developers.com/show....php?t=2798257 and when I boot into recovery, touch positions are messed up. (and only in recovery) I have not been able to identify an overall pattern for where the touches end up. I tried different touch orientations and was able to determine that the screen is not flipped and X and Y are not swapped. It seems like it is normal/no swap/no flip, and there is something else scrambling the touch locations - touches seemed to jump around, even within small sections of the display. I believe Carliv touch recovery had a similar/the same issue, but I didnt do much testing on that one.
Touching about 1/3 down the right side presses the back button, although touching a bit to the left correctly presses the Restore button. About 1/2" above that presses the Reboot button. Another 1/2" up presses the Settings button.
Touching the bottom right presses the Settings button. 1/2" up presses the Reboot button. Another 1/2" up presses the Wipe button.
The top half is pretty consistent in what button is pressed, but the bottom half seems to be a bit random, sometimes even pressing the left side.
How can I get touch working properly?
Can anyone suggest another method for booting to recovery? I have been using ADB, but that wont work if the phone ends up unbootable. Volume up + power boots normally, Volume down + power boots to a Chinese factory test mode (touch works fine in the touch tests), Volume up + volume down + power does nothing
I have been trying to install a custom ROM (ported http://forum.xda-developers.com/android/development/rom-cyanogenmod-13-0-mt6582-t3374016), but I get errors during installation. I originally got one error with set_metadata_recursive, searching suggested it was SELinux related. In the TWRP log, I see a line saying "Full SELinux support is present". The original issue was resolved when I copied file_contexts, property_contexts & seapp_contexts from stock recovery to TWRP. Now I get this error after a few minutes when trying to flash:
Code:
ApplyParsedPerms: lsetfilecon of /system/lost+found to u:object_r:system_file:s0 failed: Operation not supported on transport endpoint
set_metadata_recursive: some changes failed
What else do I need to do to get a ROM installed?
I managed to get TWRP 3.0.1 running on my phone, but it has similar touch issues. However, the scrambling seems to be different than what I get with 2.8.2.0. The version I ported seems to have flipped X, Is there a way to fix that at least, or do I need a different build?
I see TWRP has mouse support, but my phone doesnt support OTG. Is there a way to force the cursor to display? Or is there some recovery that has a drawing screen or other way to show where the touch ends up?
With 3.0.1, I was able to flash CM13, but either I ported it wrong, or it just wont work on my phone. It failed to boot, then booted into recovery. Are there any logs saved during boot?
Related
I just got my gtablet and was going to install the Gingerbread AOSP ROM on it. I installed clockwork successfully and was able to boot into it several times, including once to make a backup of my current ROM. After this, I created the ROMs directory on the internal storage and put the AOSP ROM in there and went to boot into cw recovery in order to flash it.
Now, whenever I press volume + and power, the tablet powers on for a second, I see the Viewsonic splash screen and then it powers off. It does not say "recovery detected" or whatever in the upper lefthand corner.
I tried removing the ROMs folder and undoing anything I did on the internal storage since it last worked, but nothing is fixing it. I am still able to boot into the stock OS just fine, I just cannot get into recovery in any way now.
Anyone have any ideas?
Are you sure you're hitting Volume + ? Sounds like it's going into APX mode (Volume -)
DOH! You are right. The volume buttons are oriented differently than my Evo...
We all make mistakes... ;-)
When I try to start my buddy's G tab in recovery mode (power button + volume up), it hangs on the "bird screen" / recovery key detected screen. The only way out is to manually shut it down with the power button.
The first time I started it in recovery I was attempting to install CWM, and the Android recovery screen came up. I couldn't get it to take any commands with home button or any other, so I shut it down manually and tried again. That's when it stopped giving me anything.
Mine didn't act that way ... did I do something wrong, or has VS changed something in their latest updates?
.
.
MikefromTX said:
When I try to start my buddy's G tab in recovery mode (power button + volume up), it hangs on the "bird screen" / recovery key detected screen. The only way out is to manually shut it down with the power button.
The first time I started it in recovery I was attempting to install CWM, and the Android recovery screen came up. I couldn't get it to take any commands with home button or any other, so I shut it down manually and tried again. That's when it stopped giving me anything.
Mine didn't act that way ... did I do something wrong, or has VS changed something in their latest updates?
.
.
Click to expand...
Click to collapse
NV-Flash your device back to a stock firmware and try again. Or you can just NV-Flash a new recovery file. That would also work.
If the stock recovery had a menu that you were trying to select a command from then the device has a ROM based on the 1.2 bootloader and there are a few things you should know.
1) The home key doesn't activate the selected command. It toggles the display. The power key activates the commands.
2) The standard CWM for 1.1 based ROMs doesn't work with 1.2 based ROMs
3) If the device has one of Roebeet's custom 1.2 based ROMs then you can use the built in recovery pack to flash between Stock Recovery and ClockworkMod with a simple command line script. It may even work to recover from the situation you're in now.
K J Rad said:
If the stock recovery had a menu that you were trying to select a command from then the device has a ROM based on the 1.2 bootloader and there are a few things you should know.
1) The home key doesn't activate the selected command. It toggles the display. The power key activates the commands.
2) The standard CWM for 1.1 based ROMs doesn't work with 1.2 based ROMs
3) If the device has one of Roebeet's custom 1.2 based ROMs then you can use the built in recovery pack to flash between Stock Recovery and ClockworkMod with a simple command line script. It may even work to recover from the situation you're in now.
Click to expand...
Click to collapse
Many thanks. I've learned tonight that his tablet has the new 4349 build, and that does have the 1.2 bootloader. That's apparently why CWM didn't load.
Where I am now, though, is that I can't get ANY recovery menu to come up. It merely sticks on the main screen with the recovery key detected message, and I have to manually turn it off to reboot. Therefore, loading anything from a zip would be difficult - which I guess might have saved us since I didn't realize VS had slipped in a new bootloader.
But for future use, I might need to get access to that recovery menu ... how do I do that?
.
.
Sounds like stock recovery got flashed over by cwm for 1.1 bootloader. You could try looking over at another site that is something like [email protected] d®∅¡d.com for the new cwm modified for 1.2 bootloader and load it through nvflash. Good luck.
Thanks!
.
.
Hey guys,
A few months ago I rooted my phone and put the Cyanogen Mod rom in it.
Everything was working perfectly..until recently.
My touchscreen is not responding...and the touch pad is also not working.
The phone boots fine but I can't click on anything because the touchscreen is not working.
Anyways, I decided to reflash the rom thinking its a software issue rather than hardware.
But, How do I get back into recovery again?
Usually I would just use Rom Manager to boot to recovery but I can't access this app because I can't navigate to it using my touchscreen or touchpad.
I read that its Vol down plus holding power. I did that but phone continues to just boot normally. Am i doing something wrong.
Please answer.....Thanks...
it is vol down plus power, but you got the order reversed. hold vol down, then press power. once that's done, select recovery.
I tried your method as well (Volume down + Power) but no luck. I think my volume key doesn't work or something.....any suggestions?
I made some progress
Instead of volume down + power (which didn't work) I used back button + power which got me into recovery.
Only problem now is that I need to select recovery. I cant seem to do that because my volume down button doesnt respond when I press it.
Is there any other way to go down in this menu screen....the keyboard is not working at this screen and also it says this message: touch screen - failed
please help
Perhaps android commander can get you to recovery. google android commander and install it on your computer, turn your phone normally and plug it into the computer after its done. Run android commander and select your app, i do recall an option for reboot to recovery.
Yes, thanks for the tip. Android commander is great.
I tried using it to get to recovery. It wouldnt work though. I get the red triangle.
Then I tried flashing a rom using android commander. It worked....the rom installed fine.
Problem now, though, is my touch panel, volume keys, and track pad don't work. They didnt work even before I reflashed this rom.
In Hboot it says touch screen: failed.
Im not sure whats going on.
Is there any way to fix my touch screen. Am i missing something?
edoble said:
Yes, thanks for the tip. Android commander is great.
I tried using it to get to recovery. It wouldnt work though. I get the red triangle.
Then I tried flashing a rom using android commander. It worked....the rom installed fine.
Problem now, though, is my touch panel, volume keys, and track pad don't work. They didnt work even before I reflashed this rom.
In Hboot it says touch screen: failed.
Im not sure whats going on.
Is there any way to fix my touch screen. Am i missing something?
Click to expand...
Click to collapse
This is a hardware issue. So no matter what you flash this is going to continue since its not software related
Sent from my fingertips using Android.
So i hoping someone could give me a hand i have exhausted all of my ideas
My Soft key buttons on the bottom of the phone (menu, home, back, search) have stopped working entirely phone is completely stock never rooted flashed or changed in anyway my first thought was maybe it was a software problem so i booted into recovery my holding vol +/- and power and tried to clear the cache (worth a shot right?) but in Samsung's infinite wisdom they use the Home soft key as select so i am unable to select wipe cache and naturally am unable to select Reboot system as well. i pull out the battery to restart the phone but to my horror the phone automatically reboots into the recovery screen... wtf! tried every combination of buttons physical and soft but i cant select anything in the recovery screen you name it i tried it short and long press of everything even tried booting holding different keys just for the sake of trying.
also tried to connect via adb while in recovery to send a "adb reboot" command but adb will not detect the device tried using every Samsung driver i could get my hands on maybe i am missing something here?
Next i tried rebooting with odin using an empty tar file as mentioned here http://forum.xda-developers.com/showthread.php?t=1766399 but it only restarts to the... recovery screen.... for the love of god.
I'm out of ideas and any help would be appreciated i have no insurance and i have another year before I'm up for a renewal.
your phone sounds broken. deactivate it with VZW and go buy something else on swappa/ebay. (i personally recommend the S3, Gnex, or, **** you get another fassy if you want)
Hey dude, I have the stock Verizon ROM and boot loaders installing those should fix your problem and if you don't want to lose what's in your phone I'm afraid friend you're **** out of luck. Pm or call 423 400 6484 I'll give you the pass to the Google drive I use to send ROMs and such. Good luck.
Sent from my SCH-I500 using xda app-developers app
Seeing as the buttons don't work in recovery, what do you think will be fixed by clearing a cache? It's called recovery because it doesn't use that stuff.
Best bet? Try flashing a custom rom which had soft key support and enable them right away. With this phone's penchant for phantom key presses you may have just improved your experience with this phone by having them die.
Time to pony up and flash a real rom
Use Odin to flash a custom recovery, As the last poster said, flash a custom ROM with on-screen key options and use that from now on.
I never use my soft keys in recovery as the power button selects all the options I've ever needed. Have you tried using the power button to select on your phone?
Fascinated by unicorn flavored jellybeans
So my tablet's model is Bluewave 8 HD + (Rockchip 33GT or something like that) and I decided to update my system through wireless update. So I downloaded it, and clicked update now. By that time I had 35% of battery left.
However, it says that it was an error. I think there were "Installation aborted" and "Error 7" and that stuff. It was on fastboot/recovery mode.
Now, I obviously couldn't select other options apart from reboot system now since my tablet doesn't have volume buttons. The buttons are on the screen. So my option is to reboot and go to the same process again— system update (Android is loading something like an object or stuff), error, and reboot.
I watched a video where clicking the reset button with the power button will move the selection down, so that it won't be reboot system now but it doesn't work for me. Whenever I do that (and as well as holding power and reset button {it is the little hole on the back where I need to poke it inside with a bent paperclip}, it just turns the screen off like a hard reset.
I can't also connect to a computer. Although my computer detects it as an "Android Phone and the Android Boot blah blah", software's doesn't detect the device.
I can't remove battery either because the back is inseparable.
Any fix? I really need to get it running well ASAP.
Thanks!
Ps: My tablet is Rooted.
halseynth said:
So my tablet's model is Bluewave 8 HD + (Rockchip 33GT or something like that) and I decided to update my system through wireless update. So I downloaded it, and clicked update now. By that time I had 35% of battery left.
However, it says that it was an error. I think there were "Installation aborted" and "Error 7" and that stuff. It was on fastboot/recovery mode.
Now, I obviously couldn't select other options apart from reboot system now since my tablet doesn't have volume buttons. The buttons are on the screen. So my option is to reboot and go to the same process againâ?? system update (Android is loading something like an object or stuff), error, and reboot.
I watched a video where clicking the reset button with the power button will move the selection down, so that it won't be reboot system now but it doesn't work for me. Whenever I do that (and as well as holding power and reset button {it is the little hole on the back where I need to poke it inside with a bent paperclip}, it just turns the screen off like a hard reset.
I can't also connect to a computer. Although my computer detects it as an "Android Phone and the Android Boot blah blah", software's doesn't detect the device.
I can't remove battery either because the back is inseparable.
Any fix? I really need to get it running well ASAP.
Thanks!
Ps: My tablet is Rooted.
Click to expand...
Click to collapse
Hey how did you enter recovery mode can you please tell me and are there custom recoveries available?
PS: you can scroll through the recovery mode by pressing the little button in the tiniest hole in your tablet so use a paper clip or something.