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.
Related
Had a previously rooted X2 that was upgraded to 2.3.4 OTA and lost root privileges.
I downloaded zdooder's adaptation of psouza4's Do-All One Click script for rooting at rootzwiki.com /topic/3216-rootunroot-droid-3-root-instructions-one-click-added-for-windows-linux-osx/page__p__74595#entry74595
Here is how I did it (your results may be catastrophic, so try this at your own risk):
1. Download the script from the link above and extract to a folder
2. Set USB Debugging on in your phone, attached my phone to the Linux box via the USB cable, and set the USB connection to PC Mode
3. Started a terminal and go to the folder where the script files are located:
./run_to_root_your_droid3.sh
4. The phone rebooted three times -- unlocked the phone after each reboot
Since I had previously been rooted, I needed to delete previous versions of Superuser:
5. Still in the command prompt --
./adb.linux
6. Entered the following commands:
mount -o remount,rw /dev/block/system /system
rm /system/bin/su
rm /system/xbin/su
exit
7. Ran the script again:
./run_to_root_your_droid3.sh
8. The phone rebooted three times -- unlocked the phone after each reboot
VICTORY!
Chris
iggyst00ge said:
Had a previously rooted X2 that was upgraded to 2.3.4 OTA and lost root privileges.
I downloaded zdooder's adaptation of psouza4's Do-All One Click script for rooting at rootzwiki.com /topic/3216-rootunroot-droid-3-root-instructions-one-click-added-for-windows-linux-osx/page__p__74595#entry74595
Here is how I did it (your results may be catastrophic, so try this at your own risk):
1. Download the script from the link above and extract to a folder
2. Set USB Debugging on in your phone, attached my phone to the Linux box via the USB cable, and set the USB connection to PC Mode
3. Started a terminal and go to the folder where the script files are located:
./run_to_root_your_droid3.sh
4. The phone rebooted three times -- unlocked the phone after each reboot
Since I had previously been rooted, I needed to delete previous versions of Superuser:
5. Still in the command prompt --
./adb.linux
6. Entered the following commands:
mount -o remount,rw /dev/block/system /system
rm /system/bin/su
rm /system/xbin/su
exit
7. Ran the script again:
./run_to_root_your_droid3.sh
8. The phone rebooted three times -- unlocked the phone after each reboot
VICTORY!
Chris
Click to expand...
Click to collapse
i used that method and the phone stays rooted after reboots.
Was this a problem in the past or something? I thought I saw another thread somewhere saying something about rooting in Linux also. The first time I ever rooted my phone was on Linux and I had no problems.
I used root explorer, made a copy of my original and named it original, then copied over another build.prop from my SGSII to play with MC3 and now the prime wont boot.
Im sure I will have to wait until i get home to use my USB cable but is this something I can fix through ADB?
how can i get the Prime into state that ADB can talk to it since now all i get is a black screen after the Eee pad splash screen?
Can you get into the recovery?
yes but it it shows the little android on his back with a red triangle.
is that because im rooted?
see if you can get adb access, if so push back an original build.prop...
note... never ever push a build.prop from a different device.. its the most stupid thing you can do.
yes i feel extremely stupid. i hope i didnt brick my prime doing something this retarded.
nextelbuddy said:
yes i feel extremely stupid. i hope i didnt brick my prime doing something this retarded.
Click to expand...
Click to collapse
i hope so to bro, although i did read someone messed up his build.prop before on his prime, dunno how that went afterwards... u might need to search for that
If you have access to either adb.. or maybe if you can flash zip files from your recovery you're good to go.
Using Adb:
Running "adb devices" should print your Device #, if it prints nothing, it won't work..
adb pull /system/build.prop build.prop.bootloop
adb pull /system/original.build.prop original.build.prop (>> Edited to original.build.prop as per your last post)
Then if you look at the files on your PC..
build.prop.bootloop would be the one you have right now that's causing loops
build.prop would be your backed up working build.prop.original
Then just push the good one:
adb push original.build.prop /system/build.prop
adb pull/push usage:
adb pull remotefile localfile
adb push localfile remotefile
You may be able to go this route and reflash the entire rom if you dont have adb access. From what I understand is you rename the update.zip file to whatever it says in the link to rename to and put on the root of sd card and do the power + volume and go into recovery.
http://forum.xda-developers.com/showthread.php?t=1492887&page=18
the latest asus update can be found here.
http://support.asus.com/Download.aspx?SLanguage=en&m=Eee+Pad+Transformer+Prime+TF201&p=20&s=16
thank you very much i will get to work on this when i get home with my cable. i was just about to post where can i get another one but you posted directions on how to pull my copy that i created which i renamed original.build.prop
Also might wanna take a look at this thread
http://forum.xda-developers.com/showthread.php?t=1514088
PM_mobile said:
If you have access to either adb.. or maybe if you can flash zip files from your recovery you're good to go.
Using Adb:
Running "adb devices" should print your Device #, if it prints nothing, it won't work..
adb pull /system/build.prop build.prop.bootloop
adb pull /system/original.build.prop original.build.prop (>> Edited to original.build.prop as per your last post)
Then if you look at the files on your PC..
build.prop.bootloop would be the one you have right now that's causing loops
build.prop would be your backed up working build.prop.original
Then just push the good one:
adb push original.build.prop /system/build.prop
adb pull/push usage:
adb pull remotefile localfile
adb push localfile remotefile
Click to expand...
Click to collapse
i can get the device into APX mode because i installed the APX driver and when i hold VOl UP and Power, my windows 7 computer shows Asus Prime APX under System Devices and it goes away if i unplug it and vice versa plugging it back in however ABD stil shows Blank for connected devices.
not sure what Im doing wrong so im uninstalling my OLD SDK from last year and reinstalling the latest SDK to see if that helps.
ok so my Prime boots into APX mode according to windows 7 Device manager. it shows APX not greyed out.
however despite this, in CMD when i type ADB Devices it shows BLANK and of course any adb commands return no device found.
if i let the Prime reboot into its Boot loop, then ADB Composite appears in Device manager.
if i go to CMD and type ADB Devices, it always says ADB Server out of date killing server and then it shows Daemon starting and then says Failed.
if i try 2 times back to back i eventually get the Device Serial number.
so then i try PULL command and that works no problem
when i try the PUSH command i get an error that says READ ONLY FILE SYSTEM and it fails.
i'm stuck now
nextelbuddy said:
ok so my Prime boots into APX mode according to windows 7 Device manager. it shows APX not greyed out.
however despite this, in CMD when i type ADB Devices it shows BLANK and of course any adb commands return no device found.
if i let the Prime reboot into its Boot loop, then ADB Composite appears in Device manager.
if i go to CMD and type ADB Devices, it always says ADB Server out of date killing server and then it shows Daemon starting and then says Failed.
if i try 2 times back to back i eventually get the Device Serial number.
so then i try PULL command and that works no problem
when i try the PUSH command i get an error that says READ ONLY FILE SYSTEM and it fails.
i'm stuck now
Click to expand...
Click to collapse
I think its bricked... because from the research Swift and I did on a battery mod, he tried a mod I don't remember what and it ended up in boot loop. ADB won't work because of the boot loop it doesn't stay long enough in a booted state for ADB to send/receive the commands. If your still in your return period try for exchange.
nextelbuddy said:
when i try the PUSH command i get an error that says READ ONLY FILE SYSTEM and it fails.
i'm stuck now
Click to expand...
Click to collapse
The file system will be read only by default. You need to remount /system as read/wrire.
Regards,
Dave
Sent from my GT-N7000 using Tapatalk
Had the same problem back then.
I did a search on the problem at the forum and found this:
"I did this and that worked for me : http://forum.xda-developers.com/show...4&postcount=21"
You need a micro sd and rename a file, easy, poof, fixed.
As far as adb goes
adb remount
or
adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
foxmeister said:
The file system will be read only by default. You need to remount /system as read/write.
Regards,
Dave
Sent from my GT-N7000 using Tapatalk
Click to expand...
Click to collapse
Unfortunately i can not remount the system. if i try to remount it says either device not found or error it can not.
its like it never listens long enough..
for example if i type ADB Devices, it will say "ADB Server out of date killing server and then it shows Daemon starting and then says Failed"
if i try that 2-3 times then it will eventually say Devices and list my Serial number.
if i try immediately after that to go to ADB SHELL, it starts and then i type:
adb push original.build.prop /system/build.prop
as soon as i hit enter it says Device not found.
even if i try that command 5 times in a row hoping that it takes one of the times, it does not.
Brollie said:
Had the same problem back then.
I did a search on the problem at the forum and found this:
"I did this and that worked for me : http://forum.xda-developers.com/show...4&postcount=21"
You need a micro sd and rename a file, easy, poof, fixed.
Click to expand...
Click to collapse
i cant look at that link, its truncated. can you post the full link please?
i tried downloading the .15 firmware from Asus site and pasting it on a micro SD card and putting it in the Prime and then booting into recovery mode but it always shows the android laying down with a red triangle.
PM_mobile said:
As far as adb goes
adb remount
or
adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
Click to expand...
Click to collapse
i cant remount, i can shell but if i do that then it says no devices connected.
wow, i royally screwed things up with this stupid build.prop like an idiot.
For the record, once in adb shell it's not adb push anymore..
That'd be
cp /system/original.build.prop /system/build.prop
I doubt this will do you any good, it seems you just can't stay in adb long enough because it reboots.
You don't gave a working custom recovery do you? (like clockwork mod)
I think I've seen people with custom recoveries on their primes.. that'd allow you to adb properly or flash a zip file with your build.prop..
Also, Did you look at this thread?
http://forum.xda-developers.com/showthread.php?t=1514088
They have a few unbrick solutions and something about getting adb to work from recovery. Recovery wouldn't bootloop while you're trying to adb..
aznmode said:
You may be able to go this route and reflash the entire rom if you dont have adb access. From what I understand is you rename the update.zip file to whatever it says in the link to rename to and put on the root of sd card and do the power + volume and go into recovery.
http://forum.xda-developers.com/showthread.php?t=1492887&page=18
the latest asus update can be found here.
http://support.asus.com/Download.aspx?SLanguage=en&m=Eee+Pad+Transformer+Prime+TF201&p=20&s=16
Click to expand...
Click to collapse
THIS!!!
i downloaded the latest stock firmware .15 from asus support site. renamed it to
EP201_SDUPDATE.zip and copied to a micdro SD card.
held VOL DOWN + Power and when i saw the white text hit VOL UP twice
and the recovery manager detected the file on the SD card and started flashing.
no more RED triangle android anymore.
im sooo excited this worked and will definitely take more caution in regards to the build.prop file. never realized how much of an integral role it played in the android OS.
thank you very much for all your help and to the others thanks for your help with ADB. even though it didnt work, i played with ADB so much last night and today that i feel much more comfortable with it.
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.
I was experiencing the wifi+bluetooth ship failure that I fixed once, twice, ..., but the fix didn't last
My last attemp to fix that resulted in a flex cable ribbon damage (bad move)
Power button and touch screen are now broken
Sounds like it's time to change phone :crying: I'm not willing to repair this time
I'm trying to access internal storage but I am stuck:
I can:
- access bootloader options (buy plug-in power or usb cable)
- go into recovery, but I can't validate my selection (no power button)
- go into fastboot, but it seems that mounting is not a fastboot possibility
- go into rom (fastboot reboot), but I need to touch screen to activate usb mount
Any idea ?
cailloup said:
I was experiencing the wifi+bluetooth ship failure that I fixed once, twice, ..., but the fix didn't last
My last attemp to fix that resulted in a flex cable ribbon damage (bad move)
Power button and touch screen are now broken
Sounds like it's time to change phone :crying: I'm not willing to repair this time
I'm trying to access internal storage but I am stuck:
I can:
- access bootloader options (buy plug-in power or usb cable)
- go into recovery, but I can't validate my selection (no power button)
- go into fastboot, but it seems that mounting is not a fastboot possibility
- go into rom (fastboot reboot), but I need to touch screen to activate usb mount
Any idea ?
Click to expand...
Click to collapse
Try this http://droid-at-screen.ribomation.com/installation/
Use a desktop window to access your phone. A long time back when my screen went off, i used this to access my phone.
guruzen said:
Try this http://droid-at-screen.ribomation.com/installation/
Use a desktop window to access your phone. A long time back when my screen went off, i used this to access my phone.
Click to expand...
Click to collapse
Thanks, one problem: USB debugging is not activated (what a noob I am not to have USB debugging check lol)
Do you have a custom recovery? If so, you should be able to access the shell through adb and USB while in recovery.
cailloup said:
Thanks, one problem: USB debugging is not activated (what a noob I am not to have USB debugging check lol)
Click to expand...
Click to collapse
If ravilov method works, write an android program that registers for onBootReceiver. In onReceive() have this code
Settings.Secure.putInt(context.getContentResolver(), Settings.Secure.ADB_ENABLED, 1)
Put the apk under /system/app and change the permission to rw-r-r
Restart your phone, the above app must run onBoot and u will have usb debugging enabled.
Lets see how things go.
ravilov said:
Do you have a custom recovery? If so, you should be able to access the shell through adb and USB while in recovery.
Click to expand...
Click to collapse
I have big part recovery V3 from Zn7mkUKzN1r8aCIV
So accessing shell would let me mount storage ?
How do I use adb from recovery ?
guruzen said:
If ravilov method works, write an android program that registers for onBootReceiver. In onReceive() have this code
Settings.Secure.putInt(context.getContentResolver(), Settings.Secure.ADB_ENABLED, 1)
Put the apk under /system/app and change the permission to rw-r-r
Restart your phone, the above app must run onBoot and u will have usb debugging enabled.
Lets see how things go.
Click to expand...
Click to collapse
So I won't be able to mount storage from shell, but I can write lines that will enable usb debugging so that I can use your first post ?
I
cailloup said:
I have big part recovery V3 from Zn7mkUKzN1r8aCIV
So accessing shell would let me mount storage ?
How do I use adb from recovery ?
So I won't be able to mount storage from shell, but I can write lines that will enable usb debugging so that I can use your first post ?
I
Click to expand...
Click to collapse
Looks like u cannot mount sdcard. I found something about adb enabling in init.rc that u can retrieve. Put your phone in recovery and connect to the system and do adb shell
You must be in # prompt. Pull out init.rc using the command "adb pull /init.rc ."
I am attaching my init.rc. diff it and you should find differences wrt to adb. Try replacing the adb differences and ensure the chmod is done for init.rc (initial permissions)
guruzen said:
Looks like u cannot mount sdcard. I found something about adb enabling in init.rc that u can retrieve. Put your phone in recovery and connect to the system and do adb shell
You must be in # prompt. Pull out init.rc using the command "adb pull /init.rc ."
I am attaching my init.rc. diff it and you should find differences wrt to adb. Try replacing the adb differences and ensure the chmod is done for init.rc (initial permissions)
Click to expand...
Click to collapse
adb device is ok
I got the init.rc with adb pull, it is exactly the same as yours
I tried adb pull emmc
pull sdcard
pull scard0
pull scard1
pull storage
etc
Some don't work, some work but I got only files from "sys" folder
I tried this
http://forum.xda-developers.com/showthread.php?t=2339530
Same folder issue
I tried adb shell su mount but I don't know what to do with it ^^
Since our init.rc are similar, I also tried [email protected] but I have nothing in the device list (while phone is on)
If you enabled root for adb inside the rom, you can use the following command in adb to mount the internal storage:
echo /dev/block/vold/179:97 > /sys/devices/virtual/android_usb/android0/f_mass_storage/lun0/file
That will mount internal storage as usb storage and you will be able to access the files from a computer.
Edit: I just read that you don't have it enabled >.< Another way would be to use "input tap x y" which does not require root but as you don't have it enable, something has to be done through recovery.
Second edit: Try this inside recovery:
adb shell
mkdir sdcard0
mount /dev/block/mmcblk0p18 sdcard0
Now that the internal storage is mounted on sdcard0, exit adb shell and use the following command:
adb pull /sdcard0 sdcard
This should copy all the files from the internal storage to a new folder called sdcard in your computer.
Reiki21 said:
Second edit: Try this inside recovery:
adb shell
mkdir sdcard0
mount /dev/block/mmcblk0p18 sdcard0
Now that the internal storage is mounted on sdcard0, exit adb shell and use the following command:
adb pull /sdcard0 sdcard
This should copy all the files from the internal storage to a new folder called sdcard in your computer.
Click to expand...
Click to collapse
Yeah that worked!
currently pulling everything, it's going to be long
Thanks all for help
Problem solved
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