Related
Looking for anyone who can help progress things further for this phone. No, I'm not a developer, but I'm learning what I can. Your advice and suggestions are most welcome.
Here's a quick run-down of the phone (as of 10/20/2011) :
Full Spec Sheet
Model No. - IS03
Android Version - 2.2.1 (Froyo)
Baseband/Build Number - 01.01.05 (.06 is available but it breaks the temp root)
Bootloader/Fastboot/Recovery modes are all inaccessible
Short history of root attempts by Build Number (click here)
Open Source files from the Sharp Developer website - (click here)
Checklist GREEN : DONE | RED : NOT DONE
Root - Temporary ONLY (click here or scroll below)
Unlock nand
Dumps - system / recovery
What am I missing from this checklist?
Temporary Rooting Guide (ISuhax306)
Thanks to cielavenir, goroh_kun, and love_marijuana for the work they've been putting in. This method works if your IS03 is on 2.2.1, with Baseband/Build at 01.01.05. If your Baseband/Build is at 01.01.06 or higher, THIS WILL NOT WORK.
You will need ISuhax306.7z, which is attached in this post.
Do this at your own risk. We are not responsible for any adverse effects that you may cause by attempting these methods.
### This is based on the idea that SuperOneClick is useful to make is03break stable. Thank you reporters. ###
1. prepare (on PC)
adb push data_local /data/local/
adb shell chmod 755 /data/local/is03break
adb shell chmod 755 /data/local/psneuter
adb shell chmod 755 /data/local/busybox
adb shell chmod 755 /data/local/lcd_density
adb shell chmod 755 /data/local/market.sh
adb shell chmod 755 /data/local/autoexec.sh
adb shell chmod 755 /data/local/exploit.sh
adb shell chmod 755 /data/local/finalize.sh
adb shell chmod 755 /data/local/pu
adb shell chmod 755 /data/local/pu.sh
adb shell chmod 755 /data/local/prepare_busybox.sh
adb shell chmod 755 /data/local/reboot
adb shell /data/local/prepare_busybox.sh
adb shell rm /data/local/prepare_busybox.sh
adb shell mkdir /data/local/tmp
adb shell chmod 777 /data/local/tmp
2. prepare su (on PC)
[3.0]
adb push su/30efgh/su /data/local
adb install ISuhax306.apk
[2.3.6.3]
adb push su/23efgh/su /data/local
adb install ISuhax2363.apk
3. exploit (on IS03)
$ /data/local/exploit.sh
---alternatively, on PC---
adb shell rm /data/local/tmp/sh
adb shell rm /data/local/tmp/boomsh
adb shell /data/local/psneuter
adb shell /data/local/psneuter
adb shell /data/local/is03break
---
4. finalize (on IS03)
$ /data/local/tmp/sh
# /data/local/finalize.sh
---alternatively, on PC---
adb shell
$ /data/local/tmp/sh
# cat /data/local/local.prop > /data/local.prop
---
5. reboot
6. utilize root
adb shell rm /data/local/psneuter
adb shell rm /data/local/is03break
adb shell rm /data/local/exploit.sh
adb shell rm /data/local/finalize.sh
adb shell
$ au
# cd /data
# ln -s local root
# chmod 777 local #sed requires directory write permission to change lcd_density.
* ISTweak - toggle /sbin/su http://marijuana.ddo.jp/is01/index.php?moddir=downloads&action=single&lid=19&cid=3
* jackpal.androidterm - Terminal
* revised busybox with wget: http://www.mediafire.com/?495qvu33lj6l8 see busybox.7z (use /data/local/prepare_busyboxciel.sh)
You are not alone!
I got my IS03 the first day it was out. Only got it, because it was the best Android phone on au so far. Even though the IS06 will be better. But I needed a contract as soon as possible. Kind of nice phone, but lots of things i don't like. Like the launcher (try ADW.Launcher - can be found in the android market - for home, is a lot faster and looking nicer).
I would love to root this IS03 device to get wifi tether so I can use my Nexus One with Gingerbread soon .
I have been in Android for a long time. Started with the ADP1, Nexus One and now IS03. As well I am working as an Android App Developer for tonchidot (creators of SekaiCamera). So I know my way around Android. But I am not sure how to root the IS03 or even how to try. And a little afraid of ruining my phone . Nexus One is a little different. because i don't depend on it. But I need the IS03 for calling. And can not use my Nexus One on au . If I could I would. That is why i need wifi tether as soon as possible .
Any recommendations on Rooting? Let me know and I will try!
Have you tried the regular rooting tools, just for kicks?
such as z4root and try both perm and temp root...
If you don't mind me borrowing some of your time to work out things, I could try out a few things with rooting, pm me your information(skype/gtalk/msn/aim/etc )
pboos said:
You are not alone!
I got my IS03 the first day it was out. Only got it, because it was the best Android phone on au so far. Even though the IS06 will be better. But I needed a contract as soon as possible. Kind of nice phone, but lots of things i don't like. Like the launcher (try ADW.Launcher - can be found in the android market - for home, is a lot faster and looking nicer).
I would love to root this IS03 device to get wifi tether so I can use my Nexus One with Gingerbread soon .
I have been in Android for a long time. Started with the ADP1, Nexus One and now IS03. As well I am working as an Android App Developer for tonchidot (creators of SekaiCamera). So I know my way around Android. But I am not sure how to root the IS03 or even how to try. And a little afraid of ruining my phone . Nexus One is a little different. because i don't depend on it. But I need the IS03 for calling. And can not use my Nexus One on au . If I could I would. That is why i need wifi tether as soon as possible .
Any recommendations on Rooting? Let me know and I will try!
Click to expand...
Click to collapse
Thank you for your response! I recognize you from twitter when I tried to google up information regarding the IS03. I'm trying ADW right now after you suggested it. I was using Launcher Pro, it was all right; however, ADW seems to be a little smoother.
I'm really scared to try to attempt any rooting procedure with my phone too. I do have a backup phone but I'd hate to brick my new purchase so I definitely need to do my research.
That's cool that you work with tonchidot, I've used Sekai Camera a couple times to test it out, but there really isn't too much activity around me other than a lot of landmarks.
Anyways, if I come up with any information I'll let you know on this thread.
razor950 said:
Have you tried the regular rooting tools, just for kicks?
such as z4root and try both perm and temp root...
If you don't mind me borrowing some of your time to work out things, I could try out a few things with rooting, pm me your information(skype/gtalk/msn/aim/etc )
Click to expand...
Click to collapse
I haven't tried any regular rooting tools just yet. I'm still just getting used to using it. As I find out more, especially in terms of bricking, booting into recovery, etc, I'll probably try some rooting tools.
Thanks for your response too, I will PM you with my information shortly.
just trying to boot into recovery mode...
I was trying to see if I could boot the phone into recovery mode in the first place, all my attempts have failed so far.
There's the power button, volume up and volume down buttons, and the camera button. Hidden from view (need to take off the back cover) is the reset button.
On a sidenote, I timed the startup process just for kicks:
~2 seconds - "Android au with Google" logo appears
~30 s - IS03 animation appears
~40 s - screen brightens slightly
~43 s - Monochromatic menu lights up, IS03 animation is still playing
~50 s - "Reading au card..." message replaces IS03 animation
~53 s - Home screen with Unlock pattern appears
Anyways, back to this recovery mode business: I tried a method that a couple of other websites suggested which was a combination of Vup and CAM being pressed while being powered on. That didn't work, so I tried all sorts of combinations:
Hold POWER throughout startup
Hold Vup only X
Hold Vdown only X
Hold CAM only X
Hold Vup and CAM X
Hold Vdown and CAM X
Hold ALL X
Power on and release power button but
Hold Vup only X
Hold Vdown only X
Hold CAM only X
Hold Vup and CAM X
Hold Vdown and CAM X
Hold ALL X
During Startup
Hold CAM, press HOME X
Hold Vup and CAM, press HOME X
At this point, I tried messing around with the reset button. All the reset button does is restart the phone while powered on. Nothing happens if the reset button is pressed while the phone is off. I still tried various combinations anyways but nothing worked.
After perusing some of the other threads, perhaps my phone has this recovery option disabled (likely), doesn't have such a mode (erm, unlikely?), or I just haven't found the right combination yet (also likely).
It's too bad this phone is only in Japan in the moment. I better brush up on my Japanese...
Tested some Android codes via this page
The only code that seems to work is *#*#4636#*#* which brings up general information that is otherwise easily accessible in the normal menus in this phone.
Hmmm.
z4root attempt
I've just successfully used z4root's temporary root feature to root the phone. <---- I jumped the gun when I ran z4root for the first time and it said it was successful, oops.
Now what? I don't want to try the permanent root solution yet, especially if I don't know how to get my phone into recovery mode yet.
At the moment:
1. z4root temporary root 'works' (USB debugging needs to be checked)
2. Superuser icon is in the drawer
3. BusyBox is not installed as z4root says it will do
4. Downloaded Titanium Backup, program doesn't work (asks to verify rom root and installation of BusyBox)
5. Installing BusyBox from Titanium Backup doesn't seem to work
6. Installed BusyBox installer from the Market, that works
7. Running the newly installed BusyBox installer, it tells me that I don't have root
Regarding step 7: I'm guessing that BusyBox failed to install during the z4root process even though z4root 'worked', plus trying to install via Titanium Backup didn't work as well. At this point, looks like the temporary root solution is a false positive pending further testing.
Universal Androot time.
That was quick. Attempting to install Superuser for Android 2.0-2.2 (or even 1.5-1.6) didn't work. Here's what I get:
*Rooting your device, please wait...
Generating exploit .. [OK]
Generating su .. [OK]
Generating Superuser.apk .. [OK]
Generating root script .. [OK]
*after about 10 seconds, changes to Installing toolkit ..
After roughly 20 seconds, I get this message:
Failed ! No ~~~ Fu goo ~~~
It looks like the process fails somewhere during the toolkit installation.
Boo.
ADB issues
Did it really take this long just to resolve all the ADB issues? All I wanted to do was take a simple screenshot of my phone
When I plugged my phone into my computer, all of the drivers EXCEPT the ADB installed just fine.
1. Install Android SDK and JRE SDK, Eclipse is optional since I'm not really a developer (link)
2. Install PDAnet for Android (link)
3. Ensure that your ADB files are in the correct folder (at least for the ddms.bat stuff...) (link)
So...I can take some screenshots now...yippee.
Trying SuperOneClick
Decided to give this program a chance too since I tried the other ones, and I was finally able to get the ADB driver to work.
First Method
1. Restarted the phone
2. USB Debugging is CHECKED
3. Plugged phone into the netbook
4. Started SuperOneClick, clicked Root
5. SuperOneClick will start looping after running RATC and trying to restart the ADB server. Left it like this for 5 minutes.
6a. IF I uncheck USB debugging while it says "Waiting for device" with the USB connection sound indicating a detected device, USB disconnection sound will play and program will wait. If I check USB DEBUGGING again then the program will resume looping
6b. IF I uncheck USB debugging at any time during the loop when the USB disconnection sound has already played (so before the starting up sound can play), the program will be unable to resume looping and just freeze despite shutting off any processes related to this procedure. At this point I need to restart both my netbook and my phone
7. Letting SOC loop for about 10 minutes will result in the program saying NOT RESPONDING and would then need a fresh restart
Code:
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Pushing rageagainstthecage...
21 KB/s (5392 bytes in 0.249s)
OK
chmod rageagainstthecage...
OK
Running rageagainstthecage...
OK
***IF IT KEEPS LOOPING, TRY DISABLING USB DEBUGGING NOW***
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Running rageagainstthecage...
OK
***IF IT KEEPS LOOPING, TRY DISABLING USB DEBUGGING NOW***
Second Method
1. Leave USB DEBUGGING unchecked
2. Plug phone in, start SOC, click Root
3. When SOC says "Waiting for device", check USB DEBUGGING
4. RATC should start
5. When SOC says "Starting ADB server", uncheck USB DEB, check USB DEB, uncheck USB DEB again before the "Waiting for device" message appears again
I usually can't get this timing right due to some lag on my phone. I got it right a couple of times and after about a minute, SOC will have the NOT RESPONDING indicator on again. At this point, I can check USB DEB and the program might start on a loop again, or I need to restart...again.
With either of the two methods, if I go into my Task Manager on my netbook and kill one of the two ADB.exe (usually the one with the lower memory value) processes, then the program will say FAILED, like so:
Code:
***IF IT KEEPS LOOPING, TRY DISABLING USB DEBUGGING NOW***
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Running rageagainstthecage...
FAILED
Third Method
1. Power off phone, restart netbook
2. Start SOC, click Root
3. When "Waiting for device" message appears, connect phone to netbook
4a. If USB DEB was checked before turning off the phone, SOC will do the looping thing again when the phone is finished turning on
4b. If USB DEB was unchecked before turning off the phone, nothing happens when the phone comes back online
== tl;dr ==
It looks like it's getting stuck at the RATC process and loops from there until it freezes. Range of problems may include: bad USB cables, bad USB ports, and/or this IS03 is one tough SOB.
z4root permanent root option
Just tried the permanent option with z4root.
Similar process that the temporary process did except the phone rebooted. After the reboot, everything seemed to be working as normal.
BusyBox, Titanium Backup, and Wireless Tether all say I am not rooted, though.
So much for that.
Safe Mode
My efforts to boot the phone into recovery mode have led me into Safe Mode instead.
No big deal.
I still haven't found a surefire way to get into Safe Mode except to keep mashing the Volume Up and Camera buttons while pressing the monochromatic buttons when they finally light up just before the home screen appears.
Universal Androot 1.6.2 beta 5, Recovery Mode
Interesting thing about this version is that it adds a Soft Root as well as logging to the SDCARD.
1. Uninstalled Universal Androot 1.6.1 (stable)
2. Installed Universal Androot 1.6.2 beta 5 from the SDCARD using App Install
3. Tried all options, including the option not to install Superuser
RESULT: Failed! No ~~~ Fu Goo ~~~
Would you look at that? I can put my phone into recovery mode through adb commands...huh.
I have a IS03 from au as well, so I appreciate your efforts in this. So far the phone will do, but I do find it strange that I can't use Skype over wifi, instead of 3g...
lundman said:
I have a IS03 from au as well, so I appreciate your efforts in this. So far the phone will do, but I do find it strange that I can't use Skype over wifi, instead of 3g...
Click to expand...
Click to collapse
Thanks for your comments. I feel I'm not really doing much except for poking around to see what kind of reaction I get from the IS03.
If I stumble on something worthwhile, it'll be posted here.
As far as your Skype problem is concerned, when you use Skype, it switches from your WiFi connection to 3g? I believe I can use Skype with my WiFi, but I'll have to pay closer attention to that.
Bootloader and Recovery reboot via ADB
Let's see what happens if I try to reboot my phone via ADB in either recovery or bootloader mode.
According to this site, if I'm not mistaken, I anticipate seeing some menu options pop up when I get into either recovery or bootloader mode.
Rebooting into Recovery Mode
1. Unmount SDCARD
2. USB DEBUG is checked
3. Plug the phone into the netbook
4. Windows+R 'cmd' to bring up the prompt
5. get to android-sdk-windows/tools directory
6. adb devices to ensure that the device is listed
7. adb reboot recovery to restart the phone into recovery
Phone reboots and shows a white triangle with a yellow exclamation mark with the green droid icon in front of it. What happens when I do some button combinations? Let's see...
VolUP + CAM = FAIL
VolDN + CAM = FAIL
POW + CAM = FAIL
POW + VolUP = FAIL
POW + VolDN = FAIL
POW + VolUP + CAM = FAIL
POW + VolDN + CAM = FAIL
VolDN + VolUP + CAM = FAIL
Randomly pressing all buttons = FAIL
I can't access any menu here...
Rebooting into Bootloader Mode
Same steps as before, except
7. adb reboot-bootloader to restart the phone into bootloader
The phone restarts and the Android AU with Google logo appears...and it seems to be stuck at this part. Button presses do nothing, no menu or text.
With either method, I have to take out the battery.
Mistaken, I am.
ADB Driver
Greetings!
It seems this is the only place I've seen for english speaking IS03 help. I saw that you were able to install the ADB drivers. Are you using a Japanese version of windows?
I was able to get the USB drivers from Sharp's site, but no luck in getting them to work...
I'm using Win 7 64bit, but it seems I can't get the ADB interface to be recognized.
Anyhow, any help would greatly appreciated.
adb reboot recovery
starts recovery.. but do not get the menu (no matter which buttons i press)
adb reboot bootloader => hangs in booting? or is that the bootloader?
fastboot devices => no devices.. well. it was worth a try
IS03 ADB Drivers
Well, strangely enough, the IS03 drivers wouldn't install for me, but these would:
sh-dev.sharp.co.jp/android/modules/driver/index.php?/003sh/download
(forum wouldn't let me post the link...)
When I have my phone plugged in and I have an emulator running, I get this:
List of devices attached
SSHEV080667 device
emulator-5554 device
I'm assuming the SSHEV device is my IS03, and the other is obvious...
I haven't gotten to much farther than this, but I thought I'd share...The drivers specific for the IS03 Win 7 64bit at this address:
k-tai.sharp.co.jp/support/a/is03/download/usb/index.html
...they didn't work for me. When trying to install the drivers, they weren't recognized.
I'll post more when I get a bit farther...
Upgraded to ICS 4.0.4 following Jim's instruction. Got stuck on the rooting step. In windows, the driver could be installed without USB debug turned on. And I can see the phone is mounted. Only when I turned on usb debugging, the driver couldn't not be installed properly and rooting script would freeze at damon started (something like that)
Tried it under Mac too. The phone can't even be recognized. Tried factory reset/reinstall newest driver/reboot millions of times, it just didn't help. The phone still can be seen using adb devices command. But I got the following errors while running the rooting script:
Unable to chmod /data/local/12m/debugfs^M: No such file or directory
Unable to chmod /data/local/12m/su^M: No such file or directory
Unable to chmod /data/local/12m/cmds^M: No such file or directory
failed on '/data/local/12m/batch' - No such file or directory
...
I can still log on to my phone by adb -s command and it turned out I don't have permission to write or list all the phone folders including data. No wonder. There is noway of changing the permission with chmod either since sudo does not work.
I came very close to fxz back to 2.3.6 because of the frustration, but still wanted to give it a final shot. Does anyone have any idea how to get my phone rooted in this case?
Questions should be posted in Q&A (Questions & Answers) Section.
I assume you're running the script as Administrator? Also, I'm not sure what you're getting at with the drivers not being able to install if the phone is in debugging mode. It has nothing to do with the phone, you just download the latest drivers and install to your PC, then enable debugging on the phone, connect via USB, and run the script as Administrator...
Sent from my fingers to your peepers
Hey folks,
Just wanted to share something I found that might be useful from time to time: how to send adb commands to android wear directly from your phone without any cables nor an extra PC.
This is a combination from different tutorials, made for different goals, so almost all credit goes to them
This worked from my Nexus 5 (4.4.4 stock, rooted) to a LG G Watch R (5.0.1)... but it should work with any combination as long as, your smartphone is rooted (but this is XDA so it has to be rooted )
First thing first, start bluetooth debugging in your android wear device (from the developer menu)
Now from your smartphone, start USB debugging (developer menu too)
At the bottom of the settings in the android wear app you should see a new option "Debugging over bluetooth", turn it on. You should get a message just below:
Host: disconnected
Target: connected
You will also get a permanent notification to remind you that debugging over bluetooth is active.
Disclaimer: su commands are powerful and with great powers comes great responsibility... so pay attention to what you do. In any case, I'm not responsable for any damage incurred to your phone, your android wear device, your cat, your home, your neighborhood, etc...
Open a terminal emulator in the smartphone paired to your wear device, where you can do "su" stuff, and run the following commands:
> su
> export HOME=/sdcard
> setprop service.adb.tcp.port 5555
> stop adbd
> start adbd
> adb devices <--- this should show you your own smartphone (with a emulator-5554, in my case)... you can actually shell into it if you like recursions .
SECURITY NOTE: This will allow the adb daemon to listen for tcp/ip connections from other machines connected to your wifi hotspot... I guess it will also allow machines sharing the same 4G cellular network you are using to connect, but what are the odds... In any case, and if I'm not wrong, any android version since 4.3 should give you a message telling you to accept the connection or not.... maybe in airplane mode with just bluetooth activated it would work and it would also be safer.
Continuing in terminal (the typical stuff we know already):
> adb forward tcp:4444 localabstract:/adb-hub
> adb connect localhost:4444
At this point your smartphone should buzz and ask you to allow a connection from your own phone. This time is the real deal, but just in case read carefully the message. It should say "Allow Wear Debugging?", so accept the connection and optionally mark the always accept option.
You will now have two emulated devices:
> adb devices
emulator-5554 device <--- the smartphone
localhost:4444 device <--- the android wear device
you need to specify for now on the target of your adb commands. For instance if you want to have a shell in the android wear device:
> adb -s localhost:4444 shell
That's it. Hope it works for everyone.
Ah! just one thing the value service.adb.tcp.port we set before disappears with a reboot (you can replace the word service with persist if you prefer to have it surviving the reboot... but I do not recommend it).
If you do not want to reboot but you want to disable it, run, as root:
> setprop service.adb.tcp.port -1
> stop adbd
> start adbd
to clean-up, from the terminal and as root:
> adb kill-server
You can also disable the adb debugging from the developer menu.
N.B. 1 . I guess the easiest thing to do would be to put all those commands in a script file and then just run as root:
> sh script_to_adb_wear.sh
N.B.2. I have not tried with fastboot... but that would surprise me if it works.... In any case, and IMHO, fastboot should only be used with the device connected to a computer via usb.
This isnt working for me on my OPO running CM12 unofficial... Running the commands gives me a blank adb devices window, any advice?
Hi,
I guess you get the empty device list after the "start adbd" command, right?
Just to be sure, before running the adb devices commad do "adb kill-server"
If adb devices still gives you an empty list of devices try with:
> adb connect localhost:5555
And check again. Usually, what should happen, the adb server detects a adbd listening in the port 5555 and it considers it is an android emulator and it connects to it automatically. Maybe in your case it is not connecting, so the connect command might help. Once you hace at least your phone showing you can run the other commands to access the watch.
Let me know if this helps
gusano38 said:
Hi,
I guess you get the empty device list after the "start adbd" command, right?
Just to be sure, before running the adb devices commad do "adb kill-server"
If adb devices still gives you an empty list of devices try with:
> adb connect localhost:5555
And check again. Usually, what should happen, the adb server detects a adbd listening in the port 5555 and it considers it is an android emulator and it connects to it automatically. Maybe in your case it is not connecting, so the connect command might help. Once you hace at least your phone showing you can run the other commands to access the watch.
Let me know if this helps
Click to expand...
Click to collapse
Works like a charm thanks for the help
Where is the adb binary? Adb isn't a recognized command
My binary is in /system/bin/adb
Sideloading...
Really great, all works... until I try to sideload an APK. I keep getting invalid apk file. I'm doing it by:
adb -s _____ install ____.apk
but it's not working. Any suggestions?
gusano38 said:
Hey folks,
Just wanted to share something I found that might be useful from time to time: how to send adb commands to android wear directly from your phone without any cables nor an extra PC.
This is a combination from different tutorials, made for different goals, so almost all credit goes to them
This worked from my Nexus 5 (4.4.4 stock, rooted) to a LG G Watch R (5.0.1)... but it should work with any combination as long as, your smartphone is rooted (but this is XDA so it has to be rooted )
First thing first, start bluetooth debugging in your android wear device (from the developer menu)
Now from your smartphone, start USB debugging (developer menu too)
At the bottom of the settings in the android wear app you should see a new option "Debugging over bluetooth", turn it on. You should get a message just below:
Host: disconnected
Target: connected
You will also get a permanent notification to remind you that debugging over bluetooth is active.
Disclaimer: su commands are powerful and with great powers comes great responsibility... so pay attention to what you do. In any case, I'm not responsable for any damage incurred to your phone, your android wear device, your cat, your home, your neighborhood, etc...
Open a terminal emulator in the smartphone paired to your wear device, where you can do "su" stuff, and run the following commands:
> su
> export HOME=/sdcard
> setprop service.adb.tcp.port 5555
> stop adbd
> start adbd
> adb devices <--- this should show you your own smartphone (with a emulator-5554, in my case)... you can actually shell into it if you like recursions .
SECURITY NOTE: This will allow the adb daemon to listen for tcp/ip connections from other machines connected to your wifi hotspot... I guess it will also allow machines sharing the same 4G cellular network you are using to connect, but what are the odds... In any case, and if I'm not wrong, any android version since 4.3 should give you a message telling you to accept the connection or not.... maybe in airplane mode with just bluetooth activated it would work and it would also be safer.
Continuing in terminal (the typical stuff we know already):
> adb forward tcp:4444 localabstract:/adb-hub
> adb connect localhost:4444
At this point your smartphone should buzz and ask you to allow a connection from your own phone. This time is the real deal, but just in case read carefully the message. It should say "Allow Wear Debugging?", so accept the connection and optionally mark the always accept option.
You will now have two emulated devices:
> adb devices
emulator-5554 device <--- the smartphone
localhost:4444 device <--- the android wear device
you need to specify for now on the target of your adb commands. For instance if you want to have a shell in the android wear device:
> adb -s localhost:4444 shell
That's it. Hope it works for everyone.
Ah! just one thing the value service.adb.tcp.port we set before disappears with a reboot (you can replace the word service with persist if you prefer to have it surviving the reboot... but I do not recommend it).
If you do not want to reboot but you want to disable it, run, as root:
> setprop service.adb.tcp.port -1
> stop adbd
> start adbd
to clean-up, from the terminal and as root:
> adb kill-server
You can also disable the adb debugging from the developer menu.
N.B. 1 . I guess the easiest thing to do would be to put all those commands in a script file and then just run as root:
> sh script_to_adb_wear.sh
N.B.2. I have not tried with fastboot... but that would surprise me if it works.... In any case, and IMHO, fastboot should only be used with the device connected to a computer via usb.
Click to expand...
Click to collapse
AJWizkid said:
Really great, all works... until I try to sideload an APK. I keep getting invalid apk file. I'm doing it by:
adb -s _____ install ____.apk
but it's not working. Any suggestions?
Click to expand...
Click to collapse
Adb -s localhost:4444 install my.apk
Where can I download the script?
¯\_(ツ)_/¯
thegrim11 said:
Where can I download the script?
¯\_(ツ)_/¯
Click to expand...
Click to collapse
Here's the script.
Using Root Explorer:
Create a folder under /system and copy adbgwrbt.sh there
Set permissions to 100 (execute for owner)
Tap script and hit execute
Profit
No credit. Just copied and pasted from OP. Thank you so much for this gusano!! Always find myself needing this . Now if you could just figure out fastboot [emoji57]
Oh my, thank you very much, I've been trying to do this ever since I got my watch but just didn't have the skills (still managed to fins an other way to send files from the phone to the watch and even install apk's), you're great man!
hatefuel19 said:
Now if you could just figure out fastboot [emoji57]
Click to expand...
Click to collapse
I'm pretty sure that in fastboot mode (bootloader) the bluetooth driver is not loaded, so I guess having fastboot with bluetooth is not possible. Furthermore, I would not trust a bluetooth connection to do things that could brick your watch... of course, the pogo pins is not what I call a super trustable connection either
The sarcasm was lost apparently ?
Grr. Got a replacement phone from insurance and the binary isn't there. Can someone please pm me the adb from system/bin?
Sent from my XT1060 using Tapatalk
gusano38 said:
Hey folks,
Just wanted to share something I found that might be useful from time to time: how to send adb commands to android wear directly from your phone without any cables nor an extra PC.
This is a combination from different tutorials, made for different goals, so almost all credit goes to them
This worked from my Nexus 5 (4.4.4 stock, rooted) to a LG G Watch R (5.0.1)... but it should work with any combination as long as, your smartphone is rooted (but this is XDA so it has to be rooted )
First thing first, start bluetooth debugging in your android wear device (from the developer menu)
Now from your smartphone, start USB debugging (developer menu too)
At the bottom of the settings in the android wear app you should see a new option "Debugging over bluetooth", turn it on. You should get a message just below:
Host: disconnected
Target: connected
You will also get a permanent notification to remind you that debugging over bluetooth is active.
Disclaimer: su commands are powerful and with great powers comes great responsibility... so pay attention to what you do. In any case, I'm not responsable for any damage incurred to your phone, your android wear device, your cat, your home, your neighborhood, etc...
Open a terminal emulator in the smartphone paired to your wear device, where you can do "su" stuff, and run the following commands:
> su
> export HOME=/sdcard
> setprop service.adb.tcp.port 5555
> stop adbd
> start adbd
> adb devices <--- this should show you your own smartphone (with a emulator-5554, in my case)... you can actually shell into it if you like recursions .
SECURITY NOTE: This will allow the adb daemon to listen for tcp/ip connections from other machines connected to your wifi hotspot... I guess it will also allow machines sharing the same 4G cellular network you are using to connect, but what are the odds... In any case, and if I'm not wrong, any android version since 4.3 should give you a message telling you to accept the connection or not.... maybe in airplane mode with just bluetooth activated it would work and it would also be safer.
Continuing in terminal (the typical stuff we know already):
> adb forward tcp:4444 localabstract:/adb-hub
> adb connect localhost:4444
At this point your smartphone should buzz and ask you to allow a connection from your own phone. This time is the real deal, but just in case read carefully the message. It should say "Allow Wear Debugging?", so accept the connection and optionally mark the always accept option.
You will now have two emulated devices:
> adb devices
emulator-5554 device <--- the smartphone
localhost:4444 device <--- the android wear device
you need to specify for now on the target of your adb commands. For instance if you want to have a shell in the android wear device:
> adb -s localhost:4444 shell
That's it. Hope it works for everyone.
Ah! just one thing the value service.adb.tcp.port we set before disappears with a reboot (you can replace the word service with persist if you prefer to have it surviving the reboot... but I do not recommend it).
If you do not want to reboot but you want to disable it, run, as root:
> setprop service.adb.tcp.port -1
> stop adbd
> start adbd
to clean-up, from the terminal and as root:
> adb kill-server
You can also disable the adb debugging from the developer menu.
N.B. 1 . I guess the easiest thing to do would be to put all those commands in a script file and then just run as root:
> sh script_to_adb_wear.sh
N.B.2. I have not tried with fastboot... but that would surprise me if it works.... In any case, and IMHO, fastboot should only be used with the device connected to a computer via usb.
Click to expand...
Click to collapse
Loved your post!
Thing is I get an error each time I try the script.
I own a rooted LG G3 ChupaChups 4.2 ROM and a LG G Watch R
Thanx in advance to your help.
setprop service.adb.tcp.port 5555
Sent from my HTC One_M8 using Tapatalk
Unauthorized
ADB tells me that my device has not authorized itself as an adb connection. The problem is since it's not actually a standard USB debugging connection I don't get a popup to mark my device as trusted. Is there anyway to work around this?
I always get the error from the pictures
N4 Android 6.0 Frank rooted xposed
LG g watch wear 5.1.1 rooted (no idea what adventages)
Gesendet von meinem Nexus 4 mit Tapatalk
---------- Post added at 07:10 AM ---------- Previous post was at 07:09 AM ----------
J0SH1X said:
I always get the error from the pictures
N4 Android 6.0 Frank rooted xposed
LG g watch wear 5.1.1 rooted (no idea what adventages)
Gesendet von meinem Nexus 4 mit Tapatalk
Click to expand...
Click to collapse
And yes I did enable all debugging setting in companion app on phone on wear
Gesendet von meinem Nexus 4 mit Tapatalk
i have this problem not connect to localhost 4444. i have cm13
adb commands won't work for me.
Hi
I have a old nexus with broken touchscreen . I want to use it via mirror on pc.
unfortunatly USB debuggin wasn't enable so i can't install any app.
any tips?
thanks
PS: i saw many use usb adapter to connect a mouse but i don't have it
EDIT: right now i just need a rom/kernel with USB debugging mode enabled by default
the screen still works , only the touch screen is broken
power , and volume bottons still work
the device is rooted
If it's only installing apps you could install them via recovery. (as zip)
Or you could check for a cheap replacement touchscreen.
nonameleft4me said:
If it's only installing apps you could install them via recovery. (as zip)
Or you could check for a cheap replacement touchscreen.
Click to expand...
Click to collapse
thanks for the answer!
sorry i forgot to mention that i need USB debuggin for make the app works correctly.
I'm trying now to find out what rom i have installed and maybe then find a kernel with OTG support . (yes i found a otg cable )
i'm not a expert of rooting
I think google has an app called voice control. Not sure how operational it is though. Supposedly you can control the entire system via voice.
nonameleft4me said:
I think google has an app called voice control. Not sure how operational it is though. Supposedly you can control the entire system via voice.
Click to expand...
Click to collapse
i need to unlock the phone and tap on the widget "search" to start voice command .
I think the best way is to find a way to enable OTG and then use a usb mouse
Boot into Recovery and mount*Data*partition.
Open a shell on PC and type:
adb pull /data/property/persist.sys.usb.config ~/
Repace*~/*with home directory of your OS.
Open that file in a text editor and you would possibly see*mtp*written there. Change it to*mtp,adb.
Note that sometimes Android doesn't understand the text file changes if the line terminator is "DOS Terminators" which Notepad would probably do on Windows (mine is Linux so no issue here).
In that case, I would suggest not using*adb pullbut doing:
adb shell echo 'mtp,adb' > /data/property/persist.sys.usb.config
You may verify that the*echo*command overwrote the file by using:
adb pull /data/property/persist.sys.usb.config ~/
and seeing the file's content in some text editor.
Unmount*Data*and reboot into Android OS. USB Debugging would probably be enabled.
Sent from my Aqua Trend using Tapatalk
Itzabhaysingj said:
Boot into Recovery and mount*Data*partition.
Open a shell on PC and type:
adb pull /data/property/persist.sys.usb.config ~/
Repace*~/*with home directory of your OS.
Open that file in a text editor and you would possibly see*mtp*written there. Change it to*mtp,adb.
Note that sometimes Android doesn't understand the text file changes if the line terminator is "DOS Terminators" which Notepad would probably do on Windows (mine is Linux so no issue here).
In that case, I would suggest not using*adb pullbut doing:
adb shell echo 'mtp,adb' > /data/property/persist.sys.usb.config
You may verify that the*echo*command overwrote the file by using:
adb pull /data/property/persist.sys.usb.config ~/
and seeing the file's content in some text editor.
Unmount*Data*and reboot into Android OS. USB Debugging would probably be enabled.
Sent from my Aqua Trend using Tapatalk
Click to expand...
Click to collapse
thanks!
i tryed
1) i went in recovery mode
2) i connect via usb the nexus4 to my pc
3)went in "mounts and storage"
4)then "mount /data"
5)in cmd i tryed your command "adb pull /data/property/persist.sys.usb.config" but i says i'm unauthorized
i checked via command "adb devices" and it return a alphanumerica string plus "unauthorized"
i tryed then to
Reboot your phone into recovery mode.
Connect it to your computer.
Open the terminal and type:
cd ~/.android
adb push adbkey.pub /data/misc/adb/adb_keys
adb shell reboot
but it still says error : device unauthorizated . please check the confirmation dialog on your device
i tryed also with a different version of adb and now gives me after "adb devices" an "offline" response
NB: if i connect the phone (not in recovery mode) via usb i can copy files in and out (i can explore onlyfew folders) , maybe this could help.
hartman11 said:
i tryed also with a different version of adb and now gives me after "adb devices" an "offline" response
NB: if i connect the phone (not in recovery mode) via usb i can copy files in and out (i can explore onlyfew folders) , maybe this could help.
Click to expand...
Click to collapse
Sorry but this could not help... Now only thing you can do is connect any USB mouse to your phone via otg cable (as it is not costly also), and you can also try USB gamepad. I also have used USB gamepad before when my touchscreen was not working.
Second thing you can do is download any android device manager for your PC like mobogenie or mobilego they directly install any app from play store to you android device, through USB.And I don't think they need USB debugging option to be enabled.
Sent from my Aqua Trend using Tapatalk
my problem is not installing an app (i could do it in recovery mode with a .zip) but enabling the USB debuggin
I have a otg cable but not the "Y" type ( the one with power source ) , also i don't know if OTG is supported by my kernel . I would like to install maybe another kernel which has OTG support and usb debuggin mode enable by default but i don't know what kind of rom i have D:
right now i just need a rom/kernel with USB debugging mode enabled by default
up
Hello,
today I was trying to save a file in system/vendor/lib/hw but it won't allow me to (permission denied), so I set chmod 755 to this folder and reboot. Now my phone can't turn on, my PC does not recognize it, so fastboot and adb don't work (even if the drivers are installed). When I put it to charge it doesn't do anything (led indicator is off and screen doesn't turn on).
Do you people kwow a way to unbrick an HTC U12+ hard bricked?
Thank you all.