Help! My touch flo has a mind of it's own. Often in Scenes or Contacts, the page simply won't stay put. Without me touching it, it shoots off to the right. Or sometimes to the bottom of the page in email view.
Any advice? I am using a screen protector and am running the new ROM.
Thanks!
You have to make sure your phone didn't repair before, I meant the hardware is stocked without any replacement, this method do not fix if you change the flash IC
1. Reboot see if it is fixed.
(if problem remains)
2. Boot into recovery (yea you need a rooted phone and custom recovery)
3. Connect the phone usb, via terminal / CMD
Code:
adb remount
cd data
cd misc
adb push AK8973Prms.txt /sdcard/
adb push AK8973Prms.txt.tmp /sdcard/
adb shell rm AK8973Prms.txt
adb shell rm AK8973Prms.txt.tmp
adb reboot
AK8973Prms.txt stores the setting of G-sensor, delete it and the phone will generating a new file automatically on reboot,this may help.
It's not Sense, it's the trackball!
Thanks for your reply- I think, however, the problem is the trackball, because it also affects non-sense screens like the program list.
So: Phantom, erratic trackball- any ideas?
Related
I'm hoping someone can help with a minor annoyance. Anytime I try to look up a page on wikipedia be it in an app or a browser the app/browser crashes once it loads abou 75%. This is with standard android settings and even when I go about:debug and select desktop.
Has anyone else had this problem and/or know how to fix it?
Found this.. haven't tried it yet..
http://forum.pocketables.net/showthread.php?t=9195
duckydan said:
I'm hoping someone can help with a minor annoyance. Anytime I try to look up a page on wikipedia be it in an app or a browser the app/browser crashes once it loads abou 75%. This is with standard android settings and even when I go about:debug and select desktop.
Has anyone else had this problem and/or know how to fix it?
Click to expand...
Click to collapse
The link Vince provided works. In case, you or anybody else looking to fix this haven't tried using adb before, my hard learnt steps are
1. Get the Android SDK for the platform tools
2. Extract the two libskia files into the same folder as the adb.exe (there are some older instructions that says adb.exe is in /tools but it's been moved to /platform-tools)
3. Put your Streak into "Recovery Mode" -> hold down both volume buttons while booting up.
- Then select option 2: Install an update package. I'm not sure what you will see next because I had StreakMod installed at this point but it shouldn't matter.
4. On your PC, follow the instructions in the pocketables post... but it might not work.
Remounting manually
5. On mine, adb remount does not work. So I had to remount manually. I'll recommend you use two command windows for the following. One for your PC/Mac shell and another for the Streak's shell through ADB.
5a. run "adb shell" to get into the Streak shell
5b. run "mkdir /tmp/system" to create a mount point
5c. run "mount -o rw -t yaffs2 /dev/block/mtdblock6 /tmp/system"
- Note: I think the mtdblock6 is the standard block device for the internal SD on the Streak but just in case, make sure that it's the correct by checking if the files are there by running "ls /tmp/system/libskia*", you should see two files listed.
5d. Exit the adb shell or switch to the PC window if you're using two windows.
5e. On your PC run "adb push libskia.so /tmp/system" and "adb push libskiagl.so /tmp/system"
5e. Back in the adb shell, verify that the files have been pushed correctly by running the ls command again. The two files should be dated around 2/3 Feb depending on your time zone I think. MOST importantly, check that libskiagl.so are all in small caps and NOT libskiaGL.so. Otherwise, you'll end up with a Streak that doesn't boot past the Dell logo.
5f. If you have the libskiaGL.so name instead. Rename the file properly by using the mv command "mv /tmp/system/libskiaGL.so /tmp/system/libskiagl.so". Double check the renaming worked.
5g. Reboot and it should work.
I am running bamf 1.6.3 remix.. I also am using Handcent sms.. I have synced and redownloaded handcent.. No matter how many times I try the sync won't catch.. The contact images remain little androids.
I Heard of a solution and tried to figure through it..
It appears the ROM Manager fix permissions script messed up the permissions on the thumbnails in the contacts folder. The files were mistakenly permissioned as 771 which meant the jpg thumbnail files were unreadable.
This is what I did to fix it:
1. Boot into clockworkmod recovery
2. Go into the mount/umount section
3. mount /system
4. mount /data
5. Connect usb data cable to computer from phone (I use linux so I don't need anything special in the way of drivers)
6. adb shell
7. mount /datadata
8. The above step may take a few seconds to mount
9. cd /datadata/com.android.providers.contacts
10. chmod og+rx *
11. cd files
12. chmod 664 *.jpg
13. cd /
14. umount /datadata
15. umount /data
16. exit
17. Reboot your phone
I ran into a problem at step 6...
I tried to access the adb shell from the command prompt on the computer I rooted my phone through..
When i typed adb shell into my prompt It could not recognize the device or the command.
-- Am I doing something wrong?? Is there Another solution? I love all the help everyone in forums give, it keeps a community running. I am just such a noob, one word lines never do me any good. A little explanation is GREATLY appreciated.
THANKS ALL.
Ok first things first : If you installed some launcher and your touch screen is not responding and you dont have USB debugging enabled then the only way to fix that is to install the original firmware, dload from here : http://www.androidtablets.net/forum...huawei-ideos-s7-slim-official-firmware-4.html check post 35 for the one i used
If you do have debugging enabled the download Superoneclick from below.
The super one click can aslo root the S7 slim and it has adb installed. Unxip it somewhere and go into the \adb folder. Open command prompt from there and run
Adb devices
If it doesnt show your device the either the debugging is not enabled or the right driver is not loaded. (Menu, Settings, Applications, Development, USB Debugging (Yes))
type adb shell
cd\data\app
rm *launcher*.apk
exit
adb reboot
This will remove the launchers thats faulty and touch screen will work again.
If you guys find a clockworkmod that works then leme know here cause i loaded the wrong one and its messed up.
Use psneuter to root and use the adb in the zip for the above
Cia
How to flash Recovery
Reserved for now
Use other Launchers
ADB remount
adb push c:\bluetooth_power.sh /system/etc/
unzip attached file to c:\
Swapping sdcard and sdcard2 around
adb remount
adb push vold.fstab /system/etc/vold.fstab
if you get permission denied error when doing adb remount then try the following instead :
adb push vold.fstab /sdcard/vold.fstab
adb shell
su
mount -o remount rw /system
cp /sdcard/vold.fstab /system/etc/vold.fstab
mount -o remount ro /system
exit
exit
reboot
Copy attached file into ur adb directory (and unzip it has the modified and original file in the zip) and do the above
Grumps said:
adb remount
adb push vold.fstab /system/etc/vold.fstab
if you get permission denied error when doing adb remount then try the following instead :
adb push vold.fstab /sdcard/vold.fstab
adb shell
su
mount -o remount rw /system
cp /sdcard/vold.fstab /system/etc/vold.fstab
mount -o remount ro /system
exit
exit
reboot
Copy attached file into ur adb directory (and unzip it has the modified and original file in the zip) and do the above
Click to expand...
Click to collapse
this works great - - i had a problem where i have not been able to recover my internal SD card - tried everything - even back to original eclair and all - now i just use the external sd (16gb) for everything. No problems with camera recognizing sd card or programs not downloading, etc, etc....
I'll still try to maybe swap out the internal card, or try to get it functional again somehow, but in the meantime, the S7 if again functional.
Rom
Im currently using this rom an dit works perfectly : http://www.androidtablets.net/forum...ical/15812-rom-tri_zet-ideos_s7-slim-mod.html
Only problem i had was updating google maps so i just loaded the new version via .apk manually
O yes If you load that rom and it comes on the first time the screen might not respond (stuck on lockscreen) but its busy loading software in the background. Mine came up on the lock screen saying connect charger although the battery wasnt low so i plugged the charge cable in. It then rebooted after a while and the touch screen is working perfectly.
http://forum.xda-developers.com/showthread.php?t=942166
Grumps said:
Im currently using this rom an dit works perfectly : http://www.androidtablets.net/forum...ical/15812-rom-tri_zet-ideos_s7-slim-mod.html
Only problem i had was updating google maps so i just loaded the new version via .apk manually
O yes If you load that rom and it comes on the first time the screen might not respond (stuck on lockscreen) but its busy loading software in the background. Mine came up on the lock screen saying connect charger although the battery wasnt low so i plugged the charge cable in. It then rebooted after a while and the touch screen is working perfectly.
http://forum.xda-developers.com/showthread.php?t=942166
Click to expand...
Click to collapse
I just got my Slim S7 yesterday, hated the launcher so I replaced it not thinking it would cause such a problem... long story short I tried installing the rom you linked hoping it would fix it(tried everything else) and the touch screen still is unresponsive and USB debugging is now disabled. Any ideas?
phxtravis said:
I just got my Slim S7 yesterday, hated the launcher so I replaced it not thinking it would cause such a problem... long story short I tried installing the rom you linked hoping it would fix it(tried everything else) and the touch screen still is unresponsive and USB debugging is now disabled. Any ideas?
Click to expand...
Click to collapse
well I finally got it working. I ended up doing multiple battery pulls and installed the geeksu recovery, and that's all I did. I'm up and running on that rom. Only thing is thatbi somehow lost root, but that was no biggy.
I've got a droid razr; rooted, stock rom
I broke the screen accidentally and now the screen isn't showing anything and touch isn't working.
I'd like to recover all the data off my device, but since it's locked, it won't budge. Drives won't mount when I plug it into my PC.
I've got a previous backup which is a little older, but i'm interested in backing up the actual databases (texts, call logs, etc) and system data too, along with my images and personal data.
Is there any way I can perform a whole backup while the system is locked like this?
I've already searched the forum for previous threads with similar issues, but I couldn't find one with a viable solution.
Any help is appreciated, thanks in advance.
Partial Update
Hey all-
I've partially solved my problem.
I was able to get ADB working miraculously. I downloaded the Motorola Device Manager and installed it, also downloaded the Android SDK/Java SDK;
Using the sdk manager i installed the google usb drivers (im not sure it helped any way, but just in case)
after that I ran through the process of adb
Code:
adb kill-server
adb start-server
**plug in device**
adb wait-for-device
adb get-serialno
From there I was able to use "adb shell" and navigate around the file system; used su, went to /data/system/ and did "mv gesture.key gesture.key.bak"
I then restarted my phone and did a repeat of wait-for-device, and get-serialno just to verify the phone was connecting properly.
I then browsed to my computer and amazingly, the drives mounted, my sdcard, and sdcard-ext as removable drives and I was able to view the contents.
-------
So now, I'm stuck here with a device that's NOT locked, I can view my files, and I can navigate the file system.
My end goal is to be able to copy everything from /data/ to /etc/ /system/ /root/ /sdcard*/ /vendor/ /xbin/ and any other system file that's not available through the mounted drives.
I'll keep this thread updated, and if anybody has any help or clue on how I'd do this, it'd be greatly appreciated.
So far I've tried variations on "adb pull" using / as a root dir; trying to find a way to use the shell to invoke scp, ssh, or some other file transfer, but I get no network connection. While in the adb shell and doing any file operations, I get an error stating that it's a read-only file system as well.
Fixed
I just wanted to let you all know that I've resolved my problem.
Let me state the issue again.
- Screen and touch broke.
- Device locked with pattern
- Rooted
- ICS - Stock Verizon ROM
- USB Mode was UMC, not PTP/MTP
- USB Debugging enabled
I used ADB to delete /data/system/gesture.key and rebooted, effectively removing the device lock, and allowing drives & data on my SD cards to show up in explorer after a reboot of the phone.
After futzing around for a bit, I realized the phone was tied to my Google account, and I remotely installed "Droid VNC Server" (app name org.onaips.vnc)
From there I found a way to activate the VNC server through the ADB command line
Source: android.stackexchange.com/a/31957
Code:
Application located in
/data/data/org.onaips.vnc/files
With a root shell, run this
chmod 766 /data/data/org.onaips.vnc/files/androidvncserver
Then you can execute the vnc server from the command line
/data/data/org.onaips.vnc/files/androidvncserver
Run this to forward the port
adb.exe forward tcp:5901 tcp:5901
On your VNC client, connect to localhost:5901
From there I was able to get access to my home screen and pulled the notification drop down and changed from USB Mass Storage to Camera/Media Mode
Rebooted the phone, started the vnc server again, connected to it and moved some files around to my SD Card
In another adb shell as root, I was able to copy files from /data/data/ (or anywhere else I wanted) and write them to anywhere on /sdcard-ext/
From there in another command shell, I ran adb pull /sdcard-ext/datafolderfile
=========================================================================
I believe this to be the overall gist of things, though I ran into hiccups along the way, while I was messing around, I changed some permissions which caused my su executable to break and only be allowed to run shortly after booting the phone; and also because of the broken screen, something would cause the phone to reboot every so often, breaking my connections, backups, file transfers, and etc
There's also a cool option in adb
Run
"adb backup" and it'll give you all the switches, you'll have to confirm the backup on your phone, so be sure to be running VNC and confirm it, but adb backup should be able to grab everything you need. Like I said it didn't work for me because my phone would reboot;
I hope everybody that sees this can benefit from it
Annafunny said:
So did you extract your data from your Razr with adb finally?
Click to expand...
Click to collapse
This thread is really old (4 years)... and the answer was provided.
To avoid further issues, closed.
So I've been tinkering around with CM12.1 on this watch for a while (since I switched my phone from the Samsung Galaxy Note 4 to the Xiaomi Mi Max) and yesterday decided to give Android Wear another try (note: I had the LG G Watch back in the really early Android Wear days) and there have been quite a few tweaks that I decided to apply so will share them all here as I remember them.
Android Wear:
Gaining root:
Since we can not use systemless SuperSU (because we can't edit the kernel on the go) like the other watches we need to use a system only root method so I will share how to do that:
You can do this either manually by creating a .supersu containing "SYSTEMLESS=false" file in /system/ before flashing Wear SuperSU or just flash the zip from here before the SuperSU Wear zip: https://forum.xda-developers.com/android/software-hacking/root-disabler-t3370794
Also here is the latest SuperSU Wear zip file: https://drive.google.com/file/d/0B3zB2zRyWlLBNmhwSmNBUEp1SVU/view
Note: you will have a Busybox app installed when you boot AW, you need to connect to Wi-Fi to be able to use it, otherwise it will crash.
Note 2: If you are connected to the phone via Bluetooth the Wi-Fi will automatically disconnect but you can disable this behavior in Developer Options on the watch.
Disabling touch to wake:
This was really annoying for me, I only want the device to wake by pressing the button not when I tilt the watch or touch the screen since that means the watch will be waking up uselessly a lot, tilt to wake can be disabled from the Android Wear app on the phone but for disabling touch to wake you need to edit some system files.
Note: this requires either having root or booting into TWRP and being connected to a PC using either Bluetooth ADB or the watch with the cradle and an USB cable.
AW+root method:
With the watch connected to the computer using either ADB over Bluetooth or the USB cable do the following in a shell:
Code:
adb pull /system/usr/idc/sec_touchscreen.idc
Now you will get the sec_touchscreen.idc file on your PC, open it using Notepad++/gedit/some other Linux EOF format compatible text editor (NOT NORMAL NOTEPAD OR ANY MICROSOFT OFFICE APP!!!!)
The last line should look like:
Code:
touch.wake=1
Just delete that line or set it to 0 and save the file.
Now back to the shell:
Code:
adb shell "mount -o remount,rw /system"
Code:
adb push sec_touchscreen.idc /system/usr/idc/
Code:
adb reboot
Done, now touching the screen will no longer wake up the device.
TWRP method:
Boot the watch in TWRP and connect it to the PC using the cradle and an USB cable then do these commands in a shell:
Code:
adb shell "twrp mount system"
Code:
adb pull /system/usr/idc/sec_touchscreen.idc
Now you will get the sec_touchscreen.idc file on your PC, open it using Notepad++/gedit/some other Linux EOF format compatible text editor (NOT NORMAL NOTEPAD OR ANY MICROSOFT OFFICE APP!!!!)
The last line should look like:
Code:
touch.wake=1
Just delete that line or set it to 0 and save the file.
Now back to the shell:
Code:
adb push sec_touchscreen.idc /system/usr/idc/
Code:
adb reboot
Done, now touching the screen will no longer wake up the device.
I am not sure if this is a problem with AW or the AW kernel with TWRP or it was just me but TWRP didn't display properly for me after I switched from CM12.1 to AW (it would only display till I clicked something then screen turns off) so I will post how to flash the zip files without being able to see TWRP:
You will need to be connected to a computer that has ADB setup for this.
The one thing you need to actually do on TWRP on the watch is select the "never ask again" and swipe to allow system modifications on the first run of TWRP. Note that after you click to tick the "never ask again" check box the screen will already go black so remember the layout so that you'll be able to swipe the slider.
Now you will open a shell on the PC and "adb shell" to the watch that is connected with an USB cable and the charging cradle.
Now you are in the TWRP shell so do these commands:
Code:
twrp mount system
Code:
twrp install /sdcard/disable_systemless_root.zip
Code:
twrp install /sdcard/SuperSU-2.78-wear.zip
Code:
twrp wipe cache
Code:
twrp wipe dalvik
Code:
reboot
NOTE: This assumes that you have put the zips from the first post in the internal storage of the device for which /sdcard/ is a mount point.
Will post more stuff soon, just wanted to post the tutorial on how to root AW for now, I'll be leaving home soon so I'll be back to post the rest of the stuff later today.
As a secondary note right now I am trying to port some AW 2.0 apps to work on 1.5 but we'll see how that goes, don't get your hopes up.
When i try push file adb say: read only file system
I write this and now it's ok:
adb shell
su
mount -o rw,remount /dev/block/mmcblk0p25 /system
exit
adb push sec_touchscreen.idc /system/usr/idc/
Thesebax4 said:
When i try push file adb say: read only file system
I write this and now it's ok:
adb shell
su
mount -o rw,remount /dev/block/mmcblk0p25 /system
exit
adb push sec_touchscreen.idc /system/usr/idc/
Click to expand...
Click to collapse
Why did you add that /dev/block/mmcblk0p25?
The right command is:
Code:
mount - o remount,rw /system
Also did you first root your device?
I never needed to add anything, that's why I'm asking?
I don't have root. TWRP ask me to make system writable, i try to swipe (yes) but screen goes black... Maybe this is fault. I search this in google https://forum.xda-developers.com/showthread.php?t=1749657 (second post) I change the partition from mmcblk0p1 to mmcblk0p25 because gear s have /system under mmcblk0p25. And this working for me.
Thesebax4 said:
I don't have root. TWRP ask me to make system writable, i try to swipe (yes) but screen goes black... Maybe this is fault. I search this in google https://forum.xda-developers.com/showthread.php?t=1749657 (second post) I change the partition from mmcblk0p1 to mmcblk0p25 because gear s have /system under mmcblk0p25. And this working for me.
Click to expand...
Click to collapse
Ah, I was thinking you were in AW not TWRP, as I said in the 2nd post you have to swipe on the black screen, you will feel a vibration, for me both methods work properly without the extra mounting.
I've installed recovery and Android wear os, but due to Heavy battery drainage and no phone audio I'm trying to Go back to stock.
I've tried flashing Stock firmware Using Odin but after flashing when the watch boot up, after Samsung gear s logo screen Goes blank and after few seconds Samsung animation comes Up but doesn't complete the animation anf Goes blank again.
I need help to fix this.
Thanks in advance