Develop Bugs

ADB: Permission denied...no matter what i do!!!

OK...I'm beginning to think that rooting is not for me!!!! Getting a bit frustrated!!!
OK, so I installed SDK on my pc (Win XP Ver 2002 SP3), and I cannot get it recognize the device.
I tried the guide for dummies here on XDA, and I follow all the indications, server starts up, I can kill it too....but every time I try to run it I get:
"error: device cannot be found"
The line that I am writing is as follows:
Code:
c:\android-sdk-windows\tools>adb shell
and I get the error above.
When I try to see if devices are connected, and Use this:
Code:
c:\android-sdk-windows\tools>adb devices
I get:
"List of Devices attached", but there is no list!!!!!
But I can see the SDCARD from my computer....I can access the files...
Maybe I can try to pull instead of push, but I'm not sure how that would be written (line wise), not if will work.
BTW...I have never done anything like this on android....very new to this!!!!
umm.. HELP!!!
OK changed pc's,....on this one it does recognize the device, but does not allow me to push anything.....when i try:
Code:
adb push su /sdcard/su
I get adb: permissions denied
------
I tried su +, and that got me to the # prompt. So I tried typing
Code:
# adb push su /sdcard/su
and I get adb: not found???
Running out of options here!
...
Thanks!

I think you are mounting the sdcard. You don't want to do that. Just connect your phone to the computer and run ADB. Don't click "USB Connected. Select to copy files to/from your computer" on your phone.

funkeee said:
I think you are mounting the sdcard. You don't want to do that. Just connect your phone to the computer and run ADB. Don't click "USB Connected. Select to copy files to/from your computer" on your phone.
Click to expand...
Click to collapse
Funkeeeeeee thank you for the reply.
OK...I am not getting an option when I connect to the pc..on the one I get it, I shose do nothing. I have also disabled mass storage on the device once loaded, adn I get the same error. Here is some of the code that I get thorught the PC's terminal:
C:\>cd android-sdk-windows\tools
C:\android-sdk-windows\tools>adb devices
List of devices attached
HT09YR200737 device
C:\android-sdk-windows\tools>adb shell
$ adb push su /sdcard/su
adb push su /sdcard/su
adb: permission denied
$ adb kill-server
adb kill-server
adb: permission denied
$
Click to expand...
Click to collapse
Notice that once I get the initial permission denied, the terminal seems to get locked up on that no matter what I type....see above...
Anything else to try??? AM I missing something here?

That's fine. There are a few things I can suggest for you to try..
First, I want you to enable USB debugging on your phone by going to Settings > Applications > Development and check that first option.
Then connect the phonoe, but don't use 'adb shell' before pushing files. It should look like this:
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Funkz>cd c:\g2
c:\g2>adb pull /system/build.prop
501 KB/s (3596 bytes in 0.007s)
c:\g2>
Click to expand...
Click to collapse
If you are trying to run it from within adb shell, it will spit back 'adb: not found.' That should do fix it for you.
If it does not, go to Control Panel > System > Advanced > Environment Variables. Then click on Path and Edit, then ";C:\android-sdk-windows\tools\" at the very end and try again.
By the way, you don't have to run adb from the installation directory. After adding the path I just mentioned, you should be able to run it from anywhere.

funkeee said:
That's fine. There are a few things I can suggest for you to try..
First, I want you to enable USB debugging on your phone by going to Settings > Applications > Development and check that first option.
Then connect the phonoe, but don't use 'adb shell' before pushing files. It should look like this:
If you are trying to run it from within adb shell, it will spit back 'adb: not found.' That should do fix it for you.
If it does not, go to Control Panel > System > Advanced > Environment Variables. Then click on Path and Edit, then ";C:\android-sdk-windows\tools\" at the very end and try again.
By the way, you don't have to run adb from the installation directory. After adding the path I just mentioned, you should be able to run it from anywhere.
Click to expand...
Click to collapse
Thanks.....I finally can run it without having to type the entire path!!!! That was great help!!!
AS for the permission denied.....still having that issue! The one thing I didn't understand was when you changed the path to >g2.....what do you mean???? path to be g2?
Thanks again for the help!
Just a note...I am trying to do this post OTA, which I downloaded, never got the push...Would having the OTA have any effect on this? DO I need to consider reverting to stock and trying from there? If so how? run recovery?
Dude thanks for the help!

did you try typing SU? IMO you cant tamper with ADB Shell if you dont have su access so try typing down SU to ask for permission.

Alright first things first. ADB requires special drivers to work. Which is probably why it didn't work on the original PC. If you download the PDANet client on the PC that you need to do adb it will install the necessary drivers and you can uninstall the program without losing the drivers.
Another ADB requirement is to enable USB Debugging. MENU>Settings>Applications>Development and check the USB Debugging Box.
I don't know about anyone else but with my phone will automount the card. It is recommended to pull down the notification bar and make sure that your SD card isn't mounted.
You need to navigate your command prompt to whatever folder you keep ADB.exe for me
Code:
C:\Users\etnie>cd C:\Users\etnie\Downloads\G2\Android\tools
for me this returns
Code:
C:\Users\etnie\Downloads\G2\Android\tools>
to confirm this
Code:
C:\Users\etnie\Downloads\G2\Android\tools>adb devices
I won't post all the code but it should start the daemon successfully and list your device.
to be able to push files to your phone they also need to be in the same folder as the ADB.exe ie the tools folder. of course you can push it from any folder if you type the full path
Code:
C:\Users\etnie\Downloads\G2\Android\tools>adb push C:\Users\etnie\Downloads\G2\bootanimation.zip /data/local
the above code would push the bootanimation.zip from my G2 folder located in my Downloads folder to /data/local on the phone. changing the boot screen animation when you turn on the phone. I actually have the BIOS one. Because I am huge nerd lol. Moving on...
I think I covered everything necessary....If you are still having problems either PM me or reply here.

Thanks guys for the replays...here are some comments...
Acid_Wir3 said:
did you try typing SU? IMO you cant tamper with ADB Shell if you dont have su access so try typing down SU to ask for permission.
Click to expand...
Click to collapse
I have tried SU, and it does grant access, BUT!!!! so here is what happens...
I get to .....\tools> adb shell ... then i get.... the $ prompt. At this point I type $su .... then my prompt changes from $ to #. I understand that it should be $ # In any case once I get to # it says adb: not found code looks like this:
Code:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\carlos>cd\
C:\>adb shell
$ su
su
# adb push su /sdcard/su
adb push su /sdcard/su
adb: not found
#
BTW, the path has been predfined to C:\android-sdk-windows\tools\
Not sure how to navigate from #prompt
RuncaProfundus said:
1Alright first things first. ADB requires special drivers to work. Which is probably why it didn't work on the original PC. If you download the PDANet client on the PC that you need to do adb it will install the necessary drivers and you can uninstall the program without losing the drivers.
2Another ADB requirement is to enable USB Debugging. MENU>Settings>Applications>Development and check the USB Debugging Box.
3I don't know about anyone else but with my phone will automount the card. It is recommended to pull down the notification bar and make sure that your SD card isn't mounted.
4 You need to navigate your command prompt to whatever folder you keep ADB.exe for me
Code:
C:\Users\etnie>cd C:\Users\etnie\Downloads\G2\Android\tools
for me this returns
Code:
C:\Users\etnie\Downloads\G2\Android\tools>
to confirm this
Code:
C:\Users\etnie\Downloads\G2\Android\tools>adb devices
I won't post all the code but it should start the daemon successfully and list your device.
to be able to push files to your phone they also need to be in the same folder as the ADB.exe ie the tools folder. of course you can push it from any folder if you type the full path
Code:
C:\Users\etnie\Downloads\G2\Android\tools>adb push C:\Users\etnie\Downloads\G2\bootanimation.zip /data/local
the above code would push the bootanimation.zip from my G2 folder located in my Downloads folder to /data/local on the phone. changing the boot screen animation when you turn on the phone. I actually have the BIOS one. Because I am huge nerd lol. Moving on...
I think I covered everything necessary....If you are still having problems either PM me or reply here.
Click to expand...
Click to collapse
Runca thanks for the detailed reply....going in order here:
1 - I did and I still have pdanet isntalled
2 - it's been like that since the first day I got the phone.
3 - How do I ensure??? you are talking about from the phone....I should turn off USB Storage? Will try this one.
UPDATE: tried unmounting and re running without success....
Code:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\carlos>cd\
C:\>adb shell
$ adb push su /sdcard/su
adb push su /sdcard/su
adb: permission denied
$
4 - It's pretty much what I have. Other that I'm not running su before doing so......
Any thoughts?

Crey23 said:
AS for the permission denied.....still having that issue! The one thing I didn't understand was when you changed the path to >g2.....what do you mean???? path to be g2?
Click to expand...
Click to collapse
The "g2> " bit is just his command prompt. He's changed directory to one called "g2" on his phone but that's nothing to do with how adb works etc (just that if he pushes or pulls files then that'll be the current directory on the PC for that).

Crey23 said:
Code:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\carlos>cd\
C:\>adb shell
$ su
su
# adb push su /sdcard/su
adb push su /sdcard/su
adb: not found
#
Click to expand...
Click to collapse
Those "adb push" commands should be done from your PC's command prompt, not from within an Android shell prompt on your phone.
"adb shell" starts a command shell on the phone. Which is fine for doing some stuff. But "adb" commands won't work because now you're issuing them to your phone, not your PC.

steviewevie said:
Those "adb push" commands should be done from your PC's command prompt, not from within an Android shell prompt on your phone.
"adb shell" starts a command shell on the phone. Which is fine for doing some stuff. But "adb" commands won't work because now you're issuing them to your phone, not your PC.
Click to expand...
Click to collapse
Thanks Steve.....that makes a lot of sense, and in part why i am a bit lost here....but knowing that....how can I get to "push" things to my phone?

Don't run the adb shell command. That takes you into the phone's prompt. Any commands you run from adb shell with $ or # are run within the phone. You want to run adb push from command prompt. Look at my previous post. It should look like:
C:/>adb push ...
not
#adb push...
Sent from my HTC Vision using XDA App

Funkeee,x thank you I will try that as soon as I can.
funkeee said:
Don't run the adb shell command. That takes you into the phone's prompt. Any commands you run from adb shell with $ or # are run within the phone. You want to run adb push from command prompt. Look at my previous post. It should look like:
C:/>adb push ...
not
#adb push...
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Sent from my T-Mobile G2 using XDA App

Finally progress
Guys thank you for your help!!!!!
I was finally able to push all the files to the phone. Now my problem has changed..., still dealing with Permission denied....when executing rage I get a buch of errors, please see image:
Code:
$ $su
# /data/local/tmp/rage
I get this.....
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I then figured that since I was temp rooted through Visionary r10, that was the reason for the errors above. I then proceeded to reboot without temp-rooting.
When I come up to the terminal I get:
Code:
export PATH=/data/local/bin:$PATH
$ $su
su: permission denied
$
SO if I understand this correctly, I need NOT be temp-rooted in order to run rage, but if I'm not temp-rooted, I don't have permissions to get to execute rage....there a chicken and egg story here somewhere! lol
Can I use a hybrid of the visionary temp root and perm root in that post?

From what I recall you need to uninstall visionary and reboot prior to using the rage method.
Sent from my HTC Vision using XDA App

Thanks funkeee...I will try in the morning.
But part of the problem is that without visionary I cannot get su access to run any of this. I'll backup VIS r10 before removing, and try again.
I post my results...goodnight and thanks!
funkeee said:
From what I recall you need to uninstall visionary and reboot prior to using the rage method.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Sent from my T-Mobile G2 using XDA App

I looked at the rage instructions and the prompt is misleading. You may forgetting to use chmod to change permssions. I've put my version of the instructions (just the start).
Uninstall visionary, reboot and from command prompt on your pc, navigate to the folder where you have these files and run:
c:/> adb push su /sdcard/su
c:/> adb push Superuser.apk /sdcard/Superuser.apk
c:/> adb push rage /data/local/tmp/rage
c:/> adb push busybox /data/local/tmp/busybox
c:/> adb push root /data/local/tmp/root
c:/> adb shell chmod 0755 /data/local/tmp/*
Don't forget the last entry, which changes the permissions.
Then on your phone, open terminal and put in:
$ /data/local/tmp/rage
It will say Forked Childs...
Then Menu > Reset Term. It will close, then launch terminal again, it will force close and then launch it again and you will have rage root.
If you get to there, you're in good shape. You can then follow those instructions to to push hboot and wpthis. Be careful with the dd command and be sure you have it exactly right. There are no do-overs with 'dd'.
http://forum.xda-developers.com/showthread.php?t=834228

Thanks man I will try it shortly.

funkeee said:
I looked at the rage instructions and the prompt is misleading. You may forgetting to use chmod to change permssions. I've put my version of the instructions (just the start).
Uninstall visionary, reboot and from command prompt on your pc, navigate to the folder where you have these files and run:
c:/> adb push su /sdcard/su
c:/> adb push Superuser.apk /sdcard/Superuser.apk
c:/> adb push rage /data/local/tmp/rage
c:/> adb push busybox /data/local/tmp/busybox
c:/> adb push root /data/local/tmp/root
c:/> adb shell chmod 0755 /data/local/tmp/*
Don't forget the last entry, which changes the permissions.
Click to expand...
Click to collapse
Up to here I am fine.
funkeee said:
Then on your phone, open terminal and put in:
$ /data/local/tmp/rage
It will say Forked Childs...
Then Menu > Reset Term. It will close, then launch terminal again, it will force close and then launch it again and you will have rage root.
If you get to there, you're in good shape. You can then follow those instructions to to push hboot and wpthis. Be careful with the dd command and be sure you have it exactly right. There are no do-overs with 'dd'.
http://forum.xda-developers.com/showthread.php?t=834228
Click to expand...
Click to collapse
But is with this part that I have issues with......
I uninstalled VISONary as suggested, and I got the same result as before.....error, error, error.....permission denied! Basically without visionary and su I cannot get access to the run rage. I gave me this error:
Code:
$ /data/local/tmp/rage
/data/local/tmp/rage: /data/local/tmp/busybox: permission denied
mount: Operation not permitted
mkdir failed for /system/xbin, Read-only file system
/data/local/tmp/rage: /data/local/tmp/busybox: permission denied
Unable to chmod /system/xbin/busybox: no such file or directory
/data/local/tmp/rage: /data/local/tmp/busybox: not found
cp: Permission denied
cp: Permission denied
Unable to chmod /system/xbin/su: no such file or directory
Mount: Operation not permitted
$
SO as i interpret this as I dont have the rights or permission to run the rage script. What puzzles me is the fact the it cannot "mount" the sdcard...after running this, I cannot take a picture (screenshot) bcs it does not recognize the sdcard. I have to Reboot.
Any ideas?
Thanks!

Crey23 said:
Up to here I am fine.
But is with this part that I have issues with......
Code:
$ /data/local/tmp/rage
/data/local/tmp/rage: /data/local/tmp/busybox: permission denied
mount: Operation not permitted
mkdir failed for /system/xbin, Read-only file system
/data/local/tmp/rage: /data/local/tmp/busybox: permission denied
Unable to chmod /system/xbin/busybox: no such file or directory
/data/local/tmp/rage: /data/local/tmp/busybox: not found
cp: Permission denied
cp: Permission denied
Unable to chmod /system/xbin/su: no such file or directory
Mount: Operation not permitted
$
Click to expand...
Click to collapse
I think there's something majorly wrong here. Funny, I saw someone else with a similar problem recently. It looks like when you're running "rage" it's actually running the "root" script that you use at a later stage, and not "rage" at all. Double check what you've got, I think "rage" is a binary and not a script. Are you sure you didn't push "root" to "rage" ?

[Q] Rooting Problem Please Help

so i have adb setup and have it adb.exe in the gfree folder so when i go to command prompt im permission denied after
su
cd /data/local
chmod 777 gfree
./gfree -f
sync
Click to expand...
Click to collapse
what am i doing wrong
heres a pic
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
after cd /data/local it says permission denied what do i do?

zbrah said:
so i have adb setup and have it adb.exe in the gfree folder so when i go to command prompt im permission denied after
what am i doing wrong
heres a pic
after cd /data/local it says permission denied what do i do?
Click to expand...
Click to collapse
are you working from this page? http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2
why are you cd'ing to data/local? what's in that folder? in the other thread you said you had your files in gfree_02??

http://forum.xda-developers.com/showthread.php?t=855764
im using this method

why would you cd to data/local? you need to put files there, not pull files from there...

martonikaj said:
why would you cd to data/local? you need to put files there, not pull files from there...
Click to expand...
Click to collapse
what should i do then
what commands do i do thanks for the help i appreciate it

On your computer's terminal/command line, navigate to where the gfree file is, and then...
Code:
adb push gfree /data/local
adb shell
This copies gfree to your phone, then puts you in your phone's terminal. Then do this:
Code:
su
cd /data/local
chmod 777 gfree
./gfree -f
sync
Click to expand...
Click to collapse
thats what is says on this thread http://forum.xda-developers.com/showthread.php?t=855764

zbrah said:
thats what is says on this thread http://forum.xda-developers.com/showthread.php?t=855764
Click to expand...
Click to collapse
Aren't you supposed to be running the commands:
Code:
su
cd /data/local
chmod 777 gfree
./gfree -f
sync
In terminal emulator on your phone? from what I remember this is the way I did it. Could be mistaken by the wording though... I just remember using ADB to push all the files then just running terminal emulator on my phone instead of running a shell. Worth a try if you can't get ADB shell to work properly.

zbrah said:
so i have adb setup and have it adb.exe in the gfree folder so when i go to command prompt im permission denied after
what am i doing wrong
heres a pic
after cd /data/local it says permission denied what do i do?
Click to expand...
Click to collapse
From the look of this you still have a $ sign this means you dont have root permission, it should be a # sign after typing su in adb shell . Looks like your temp root didn't work or your not allowing root user permission on your phone right after typing su in adb shell.

The guide you are trying to use specifically says "So we're assuming you've permarooted already and usb debugging is on" but from the thread title, it sounds like you are trying to get permanent root. The guide does not work if you don't already have root.
You should probably use the guide in the Wiki linked to earlier.

The problem is the very first command you type into the command prompt on your phone, i.e. "su", is giving you "permission denied". So as others have said, you are not getting root permissions. If you have rooted previously then the "Superuser" app pops up and asks for permissions the first time you try "su", check it's not coming up with a box on your phone which you're failing to see (then it times out after a few seconds and says "permission denied").

[Q] Deleted su file.. how can I restore..?

Hi,
I've been having problems with my root and superuser. I tried to install supersu also but was crashing every time. The superuser could not get the new su version and generally my A100 acted as not rooted. I tried to do the rooting process again and again with no luck. I downloaded the latest su version and tried the commands again.
Then it crossed my mind to remove the old su from xbin (since I got the new version) and give the commands. So I rm it but then I gave it a closer look and saw that the command did not copy the new su to xbin but was using the cat command. The commands I gave are
(The su version is supposed to be the latest one)
$ export PATH=/data/local/bin:$PATH
$ pwd
/
$ cd sdcard
$ /system/bin/cmdclient ec_micswitch '`mount -o remount,rw /system`'
$ /system/bin/cmdclient ec_micswitch '`cat /mnt/sdcard/su >/system/xbin/su`'
$ /system/bin/cmdclient ec_micswitch '`chmod 6755 /system/xbin/su`'
$ ls /system/xbin/su
/system/xbin/su
$ su --version
0.83:SUPERSU
$ /system/bin/cmdclient ec_micswitch '`mount -o remount,rw /system`'
$ /system/bin/cmdclient ec_micswitch '`cat /mnt/sdcard/su >/system/xbin/su`'
$ /system/bin/cmdclient ec_micswitch '`chmod 6755 /system/xbin/su`'
$ ls /system/xbin/su
/system/xbin/su
$ su --version
0.83:SUPERSU
$ rm /system/xbin/su
rm failed for /system/xbin/su, Permission denied
$ ls -al /system/xbin/su
-rwsr-sr-x root root 91980 2012-03-24 01:40 su
$ /system/bin/cmdclient ec_micswitch '`chmod 6777 /system/xbin/su`'
$ ls -al /system/xbin/su
-rwsrwsrwx root root 91980 2012-03-24 01:40 su
$ rm /system/xbin/su
rm failed for /system/xbin/su, Permission denied
$ mv /system/xbin/su /mnt/sdcard/temp
failed on '/system/xbin/su' - Cross-device link
$ /system/bin/cmdclient ec_micswitch '`rm /system/xbin/su`'
$ /system/bin/cmdclient ec_micswitch '`mount -o remount,rw /system`'
$ /system/bin/cmdclient ec_micswitch '`cat /mnt/sdcard/su >/system/xbin/su`'
$ /system/bin/cmdclient ec_micswitch '`chmod 6755 /system/xbin/su`'
$ ls /system/xbin/su
/system/xbin/su: No such file or directory
Now I have no su file... how can I restore it? Can anyone send me the su from their A100 (I guess it would be the same)
I can't understand why the rooting stopped. It use to work ok...maybe the interference of superuser and supersu caused this..
It happened after a restart...
Anyhow... how do I get my root back...? Any ideas...?
Sent from my A100 using Tapatalk

SuperSu and Superuser both use different su binaries. Which one are you going to use (it's not wise to have both or else they are going to interfere with each other).

The superuser stopped responding but I couldn't uninstall it. The posts I've for the supersu said that it dike not matter whether you have superuser isntalled,so I installed it.
I would prefer supersu I guess... but at the moment anything would be just fine....
Sent from my A100 using Tapatalk

dkaratasos said:
The superuser stopped responding but I couldn't uninstall it. The posts I've for the supersu said that it dike not matter whether you have superuser isntalled,so I installed it.
I would prefer supersu I guess... but at the moment anything would be just fine....
Sent from my A100 using Tapatalk
Click to expand...
Click to collapse
Are you running honeycomb or ICS?

Theonew said:
Are you running honeycomb or ICS?
Click to expand...
Click to collapse
Honeycomb
Sent from my A100 using Tapatalk

dkaratasos said:
Honeycomb
Sent from my A100 using Tapatalk
Click to expand...
Click to collapse
Try re-rooting using this method: http://forum.xda-developers.com/showthread.php?t=1472521.

Theonew said:
Try re-rooting using this method: http://forum.xda-developers.com/showthread.php?t=1472521.
Click to expand...
Click to collapse
I did but did not work
$ sh root.sh
Copying root file & changing permissions (making your tab super!) Please wait...
-rwsr-sr-x root root 22148 2012-04-01 01:45 su
If su is listed above with out errors and is bigger than 0 bytes... That's all folks!!
Now you need to install superuser and open it, then go to the wrench icon and tap it
Find the update area and tap it, tap update now to update the super user file that this script copied over earlier
Once its updated, install busybox from the market and your all set!
$
Both superuser and supersu could not gain root shell...
If you check the size of the su file in xbin now and initially you will see a big difference ...
Can someone upload their su file...? Isn't it the same...?
Sent from my A100 using Tapatalk

I opened the root.sh ...
It has the same commands as a script... it would not do anything different...
Root.sh:
echo "Copying root file & changing permissions (making your tab super!) Please wait..."
sleep 2
/system/bin/cmdclient ec_micswitch '`mount -o remount,rw /system`'
sleep 2
/system/bin/cmdclient ec_micswitch '`cat /mnt/sdcard/su >/system/xbin/su`'
sleep 2
/system/bin/cmdclient ec_micswitch '`chmod 6755 /system/xbin/su`'
sleep 1
rm /mnt/sdcard/su
echo " "
ls -l /system/xbin/su
echo " "
echo "If su is listed above with out errors and is bigger than 0 bytes... That's all folks!!"
echo " "
echo "Now you need to install superuser and open it, then go to the wrench icon and tap it"
echo "Find the update area and tap it, tap update now to update the super user file that this script copied over earlier"
echo "Once its updated, install busybox from the market and your all set!"
Sent from my A100 using Tapatalk

The only thing left to try is a factory reset (or update to ICS if you want to keep all your data) then re-root (that will work). In these cases, one would just flash superuser via recovery, but since you are on HC and have no custom recovery, that simple fix is not possible.

How about taking the su file from an other A100...? Even a non rooted A100.. won't that work...?
Sent from my A100 using Tapatalk

dkaratasos said:
How about taking the su file from an other A100...? Even a non rooted A100.. won't that work...?
Sent from my A100 using Tapatalk
Click to expand...
Click to collapse
A non-rooted device does not have a su binary. The su binary of a rooted one would be the same as the one here: http://goo-inside.me/superuser/su-bin-3.0.3.2-efghi-signed.zip (until there's an update at least ).

Theonew said:
A non-rooted device does not have a su binary. The su binary of a rooted one would be the same as the one here: http://goo-inside.me/superuser/su-bin-3.0.3.2-efghi-signed.zip (until there's an update at least ).
Click to expand...
Click to collapse
That confuses me.... but then why the rerooting process did not work,if there was not already a su file there...? And why the scripts use cat instead of the simple cp ...? Even more... why the size of the su I had before is different than the new one..? Are you sure there is no su file on a non rooted A100..?
Sent from my A100 using Tapatalk

I did it... I tried a few different su versions I had downloaded in the past and one worked... with superuser ... the supersu crashes....
I got rid of supersu and through superuser I updated the su file..it worked like a charm...
Thanx for your help...
Sent from my A100 using Tapatalk

dkaratasos said:
That confuses me.... but then why the rerooting process did not work,if there was not already a su file there...? And why the scripts use cat instead of the simple cp ...? Even more... why the size of the su I had before is different than the new one..? Are you sure there is no su file on a non rooted A100..?
Sent from my A100 using Tapatalk
Click to expand...
Click to collapse
1. Corruption.
2. That's the chosen "exploit".
3. SuperSu's su binary will be a different size than Superuser's su binary.
4. No non-rooted device has a su binary. The su binary allows root access (which a non-rooted device does not have). The rooting process places the su binary in a device.
dkaratasos said:
I did it... I tried a few different su versions I had downloaded in the past and one worked... with superuser ... the supersu crashes....
I got rid of supersu and through superuser I updated the su file..it worked like a charm...
Click to expand...
Click to collapse
Great.
P.S. - You should have said you still had SuperSu installed.

And u should recheck next time on supersu's description I'm pretty sure it says u can't b running both
Sent from my A100 using Tapatalk 2 Beta-4

raphsabb said:
And u should recheck next time on supersu's description I'm pretty sure it says u can't b running both
Sent from my A100 using Tapatalk 2 Beta-4
Click to expand...
Click to collapse
Well according to chainfire here
http://forum.xda-developers.com/showpost.php?p=23442897&postcount=43
Both can be installed and whichever you update the su file grants you the superuser ....
It crashes thought having both...
Sent from my A100 using Tapatalk

They can both be installed but not used together, I added a screenshot of the description in play store, hopefully u can see it from my screenshot
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my A100 using tapatalk

Hi,
I'm facing a similar but slightly different problem and looking for some help. Here's the situation:
- I have a rooted galaxy s2 running CM7
- I recently deleted the su binary (why I did that is another story)
- I don't have SuperSU
How can I get root back?
Thanks!

aharol said:
Hi,
I'm facing a similar but slightly different problem and looking for some help. Here's the situation:
- I have a rooted galaxy s2 running CM7
- I recently deleted the su binary (why I did that is another story)
- I don't have SuperSU
How can I get root back?
Thanks!
Click to expand...
Click to collapse
Try doing an advanced restore of system assuming you have a nandroid of that rom that's decently recent. Would also work for the a100 on ICS, but is dependant on having a nandroid of the current rom and is somewhat up to date. This will restore your busy box and super user and root. Don't restore system from another rom. Wipe cache and dalvik after restore. Other option, flash the rom directly over the current install, though I wouldn't suggest it.
Tapatalked from my Galaxy S II.

pio_masaki said:
Try doing an advanced restore of system assuming you have a nandroid of that rom that's decently recent. Would also work for the a100 on ICS, but is dependant on having a nandroid of the current rom and is somewhat up to date. This will restore your busy box and super user and root. Don't restore system from another rom. Wipe cache and dalvik after restore. Other option, flash the rom directly over the current install, though I wouldn't suggest it.
Click to expand...
Click to collapse
I'm a relative noob so let me restate to make sure I understand.
- do a reboot in recovery mode
- go to the .zip file of the current rom (CM7 --- the file I have is the latest) and run it
- AFTER that is done (and not before?), wipe the cache and dalvik cache
Is this correct. Any critical step that I'm missing?
Thanks

[How-To][tutorial]Non-tethered root/unlock for Softbank 201M (at LONG last!!!)

Can't believe I was FINALLY able to achive this! Most of the hard work was put in by others for the original root (although tethered), I just tweaked the process a bit to come up with a non-tethered root solution...no more PC is needed upon reboot!
Thx to lalaihvfivfi - hxxp://forum.xda-developers.com/showthread.php?t=2194770 for the original post
Sorry for the lack of real links, I don't have 10 posts yet so I am not allowed to provide proper links - mods, fix this if necessary!
Also, not sure how if this will work on other models or rom versions, and listed below are my phone's specs:
System Version: 9.3.102.201M.SBM.en.JP
Model Number: 201M
Android Version: 4.1.2
Baseband Version: SM_T_BP_1539.000.35.03P
Kernel Version: 3.0.42-g721d60d
Build Number: 9.8.2Q-34_SMJ-102
1)Prep
- Download the Android SDK and USB drivers from the motorola homepage
- Download the following files:
　 - XT902_SBM ( hxxp://www1.axfc.net/uploader/so/2991543)
　 - su（ hxxp://www1.axfc.net/uploader/so/2918729 password：f10d）
- Download Motopoclpyse ( hxxp://vulnfactory.org/blog/2013/04/08/motorola-bootloader-unlocking/ )
- Download the correct CWM for your phone from here --> ( hxxp://forum.xda-developers.com/showthread.php?t=2298521%E3%81%AE201M )
- Download the auto_root.sh file attached to this post
- Unzip the files and make note of the directory (I just dumped them all in the SDK > platform_tools folder as the adb files are newer than those contained in the zips above)
2) Plug the 201M in to the mac/win pc
3) Go to the directory where you Perform an adb push on the following files to the /data/local/tmp directory on the phone
- adb push su /data/local/tmp
- adb push Superuser.apk /data/local/tmp
- adb push busybox /data/local/tmp
- adb push auto_root.sh /data/local/tmp
- adb push unlock_security_module /data/local/tmp
- adb push break_setresuid /data/local/tmp/
- adb push mole-plough-ccsecurity.so /data/local/tmp/
- adb push mole-plough-lsm.so /data/local/tmp/
3) Use unlock_security_module to obtain temporary root
- adb shell
- [email protected]:/ $ cd /data/local/tmp/
- [email protected]:/data/local/tmp $ chmod 777 *
- [email protected]:/data/local/tmp $ ./unlock_security_module
- [email protected]:/data/local/tmp $ ./break_setresuid
4) You should see a stream of messages talking about the rooting process. If everything goes ok you should see:
- Unlocked LSM.
and
- Do setresuid...
Among the messages (sorry I don't remember the exact messages)
5) You should now be able to load su，Superuser.apk，busybox on to the system
- [email protected]:/data/local/tmp # mount -o rw,remount /system /system
- [email protected]:/data/local/tmp # cat /data/local/tmp/su > /system/xbin/su
- [email protected]:/data/local/tmp # cat /data/local/tmp/busybox > /system/xbin/busybox
- [email protected]:/data/local/tmp # cat /data/local/tmp/Superuser.apk > /system/app/Superuser.apk
- [email protected]:/data/local/tmp # chmod 644 /system/app/Superuser.apk
- [email protected]:/data/local/tmp # cd /system/xbin
- [email protected]:/system/xbin # chown root.root su
- [email protected]:/system/xbin # chown root.root busybox
- [email protected]:/system/xbin # chmod 6755 su
- [email protected]:/system/xbin # chmod 755 busybox
- [email protected]:/system/xbin # mount -o ro,remount /system /system
6) After the opperation is done it is ok to remove the cable from the pc. Check and see if SuperSU was installed. If it wasn't download Chainfire from the play store (which you should probably do anyway to update su)
7) Next, download Busybox from the playstore and run the updates
8) By this point you should have a fully upgraded Superuser, su, and busybox installation - however the access is only temporary and will be reset on reboot
9) Put the CWM.img you downloaded in motoapoclypse directory you created in step 10
10) Plug the 201M back in to the mac/win pc
11) Run the following commands to prepare for CWM install and reconfirm root is enabled
- adb push unlock /data/local/tmp/
- adb push cwm.img /data/local/tmp/cwm.img > nul
- adb shell chmod 755 /data/local/tmp/unlock
- adb shell
- [email protected]:/ $ cd /data/local/tmp/
- [email protected]:/ $ chmod 777 *
- [email protected]:/ $ ./unlock_security_module
- [email protected]:/ $ ./break_setresuid
- [email protected]:/ $ ./unlock
If you get a mention that the phone is already rooted, it's ok...these steps are just to make sure!
12) Inserting CWM
- [email protected]:/ $ su -c 'mount -o remount,rw /system'
- [email protected]:/ $ su -c 'mv /system/etc/install-recovery.sh /system/etc/install-recovery.bak'
- [email protected]:/ $ su -c 'mv /system/recovery-from-boot.p /system/recovery-from-boot.bak'
- [email protected]:/ $ su -c 'dd if=/data/local/tmp/cwm.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery'
- [email protected]:/ $ su -c 'rm /data/local/tmp/cwm.img'
- [email protected]:/ $ reboot recovery
13) Upon reboot, you should be in CWM!
14) Exit out of CWM and let the phone boot up normally - you will notice you no longer have root, but fortunately you do not have to go through the above process all over again
15) Renable root by running the following command (Thx to kprower - hxxp://forum.xda-developers.com/showpost.php?p=46842021&postcount=19)
- adb shell "./data/local/tmp/unlock_security_module"
16) Download Script Manager - S Manager ( hxxps://play.google.com/store/apps/details?id=os.tools.scriptmanager&hl=en ) or use your own preference
17) Download the script attached to the thread (feel free to read through it and make it better if you can! - Thx to Sepero for BootBuddy - hxxp://androidforums.com/rooted-devices-only/693743-bootbuddy-run-boot-scripts- as a base)
18) Using script manager, go to the /data/local/tmp directory and click on auto_root.sh and open as a Script/Executable
19) Toggle the Su picture to turn on the ability to run as SU, then click save, then run.
20) The script should run (hopefully w/o any errors) and create the necessary file with the proper permissions
21) At this point, shut down the phone and reboot....you should have permanent root!
Click to expand...
Click to collapse
Any questions or spot any mistakes? Please ask and/or feel free to modify and update as necessary!

how to update 4.1.2?

hungln03 said:
how to update 4.1.2?
Click to expand...
Click to collapse
I just did the OTA (over the air) update back in March under Settings -> About Phone --> System Update
Though, if you can install CWM using the method above, you should be able to update that way as well (just make sure you have the right rom)

Bootloader unlock? can update?
---------- Post added at 03:37 AM ---------- Previous post was at 03:10 AM ----------
step17 link die

hungln03 said:
Bootloader unlock? can update?
---------- Post added at 03:37 AM ---------- Previous post was at 03:10 AM ----------
step17 link die
Click to expand...
Click to collapse
Yes, the bootloader is unlocked! As far as update...no idea as I already had the newest rom...
And Step 17, don't download the link there --> download the attached file on the bottom of the original post called auto_lock.sh.zip -- don't go the the androidforum's link!
The zip attached to the this thread is ok, I just downloaded it! Good luck!

Will this root a phone that took the November OTA update and has locked bootloader?

wolfpack99 said:
Will this root a phone that took the November OTA update and has locked bootloader?
Click to expand...
Click to collapse
No idea...last update Softbank (Japan) models received was last March....give it a try as this method should allow you to unlock the bootloader as well, but not sure if it will work or not outside of the SB model

It won't work on the XT907 with 9.8.1Q-78 or 9.8.1Q-94, since the bugs were fixed here, so that "unlock_security_module" will cause a segfault.
It might work on 9.8.1Q-66 and older versions, but there you also have the regular motopocalypse. So it's really just for the 201M.

okay this is good news, but can anybody enlight me how execute those steps above since i'm new to this thing?
stuck on chmod777* can't go through

Congratulations about the Root & unlock!! Great Job LostInInaka!!
Is there a source for the latest SB xml?

SIM Free?
It may be a stupid question, but does unlocking the Bootloader and rooting the device make it SIM free?
Thanks for sharing all this exiting stuff.
:good::good::good:

root 201M
what am I doing wrong?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Sumkos said:
what am I doing wrong?
Click to expand...
Click to collapse
What you have to type in step 3 is:
adb shell
cd /data/local/tmp/
chmod 777 *
./unlock_security_module
./break_setresuid
No hostnames, no prompt sings.

root 201M
lem22 said:
What you have to type in step 3 is:
adb shell
cd /data/local/tmp/
chmod 777 *
./unlock_security_module
./break_setresuid
No hostnames, no prompt sings.
Click to expand...
Click to collapse
many thanks! deal with it, but now another problem:

You get a segfault, just like I mentioned in #8.
Do you really have a SoftBank 201M?

201M
lem22 said:
You get a segfault, just like I mentioned in #8.
Do you really have a SoftBank 201M?
Click to expand...
Click to collapse
in principle without difference already. the bootloader unlocked. recovery was flashed (TWRP) by fastboot comand. But sim lock didn't disappear. I flash different firmware (xt905, xt907, AOKP 4.4) and different radio. very sad

Bricked?
Hi guys. I got up to step 6 and after installing Chanfire and updating it rebooted my phone now I am stuck on the boot screen with only =SoftBank logo showing.
Help!:crying:

OMG!
After trying a few different things i am now completely stuck in the Fastboot Flash Mode.
at the bottom it says:
Fastboot Reason: Flash Failure
usb connected

Bricked
This is what I am currently seeing:
AP Fastboot Flash Mode (S)
10.9B(*) (sha-e92be7d, 2013-03-29 01:58:14)
eMMC Info: Size 8GB
Deivice is LOCKED, Status Code: 0
Battery OK
Transfer Mode:
USB Connected
Fastbook Reason: Flash Failure
usb connected
---------------------------------------update
From CMD i sent the following command: fastboot continue
Now it shows the Softbank logo but it doesn't seem to be going anywhere. However, Windows did suddenly notice the device as soon as the logo came up and started to install the MTP USB Device, Motorola Networking Interface, and Motorola ADB Interface which all failed.
---------------------------------------update 2
Whilst in the Softbank logo screen I was able to send ADM commands so I tried going through the steps again to see what would happen.
Now this is what I have:
AP Fastboot Flash Mode (S)
10.9B(*) (sha-e92be7d, 2013-03-29 01:58:14)
eMMC Info: Size 8GB
Deivice is UNLOCKED, Status Code: 3
Battery OK
Transfer Mode:
USB Connected
Fastbook Reason: Flash Failure
usb connected

Thank you so much!!!!
Thank you so much for this. After a month or so of tinkering with my 201m, I had resigned myself to a locked controlled Android phone. This makes it so much better. I really cannot thank you enough!!!!:laugh::laugh::laugh:

[GUIDE] Install and Uninstall APK on your Moto 360 (Via Bluetooth) | No Root

This is a basic guide for those who do not know how to install and uninstall APKs on your Moto 360 without an usb cable.
Prerequisites:
ADB drivers on your PC (Thanks @Snoop05)
Minimal ADB and Fastboot (Thanks @shimp208) or all Google SDK
PC and Moto 360??
Let's start:
Connect the watch to your PC:
1. On your Moto 360 go in settings > developer options* > Turn on ADB Debug and Bluetooth debug
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2. On your phone go in settings > developer options* and enable "USB Debug"
3. Connect your phone on your PC
4.In the android wear app go in settings (at the bottom) and enable "Bluetooth Debug"
You will see: Host: Disconnected Target: Connected
5. Open Minimal ADB and Fastboot in your PC and type:
HTML:
adb forward tcp:4444 localabstract:/adb-hub
adb connect localhost:4444
Now on your phone the voice "Disconnected" on the Host voice should be changed to "Connected"
Now your Moto 360 it's connect to your PC
*If you don't have "developer options" go on "info" and tap 7 times on "build number"
Install an APK:
Warning: Now every command for your watch must be in the following way:
HTML:
adb -s localhost:4444 <command>
(Without "<" and ">")
1. Procured the APK file
2. Place the APK file in the installation directory of "Minimal ADB and Fastboot"
3.In "Minimal ADB and Fastboot" type:
HTML:
adb -s localhost:4444 install nameoftheapk.apk
So if my apk name is "Game" you must type:
HTML:
adb -s localhost:4444 install game.apk
4. Wait patiently this will take a long time depending on the size of the file (About 5 minutes for 10mb file)
5. If the word "success" appears everything has been successful.
Uninstall an APK:
Warning: Now every command for your watch must be in the following way:
HTML:
adb -s localhost:4444 <command>
(Without "<" and ">")
1. For uninstall an apk su must know the package name, usually "com.nameofthedeveloper.nameoftheapp"
For a list of the app installed on your watch type:
HTML:
adb -s localhost:4444 shell
AND
HTML:
pm list packages –f
Not always work, but if it works you will see a list of package name. Installed app stay on "data/app/"
For example this is the game "Don't tap the white tile" and the package name is at the end: "com.umonistudio.tile"
2. Now that you say the package name on "Minimal ADB and Fastboot" type:
HTML:
adb -s localhost:4444 uninstall com.example.example
In case of that game:
HTML:
adb -s localhost:4444 uninstall com.umonistudio.tile
3.If the word "success" appears everything has been successful and the app is uninstalled properly.
End of the guide, sorry for my bad english, Thanks!
If your are italian or you understand Italian >>>this<<< is my video guide for this
Video: https://www.youtube.com/watch?v=kjIEJPqkLIQ

Great guide! Just an FYI, instead of running
Code:
adb -s localhost:4444 <command>
most users should be able to run
Code:
adb -e <command>
I would run adb -e shell to verify that it connects to your 360 and not your phone (it should say minnow for the device name).

Hello
Thank you for this guide !
This guide allow us to flash the ROM ? (withou modded cable)

gloops100 said:
Hello
Thank you for this guide !
This guide allow us to flash the ROM ? (withou modded cable)
Click to expand...
Click to collapse
Please read
This guide allow us to install apk (apps) without cable
For flashing a Rom you Need a cable !!!

gloops100 said:
Hello
Thank you for this guide !
This guide allow us to flash the ROM ? (withou modded cable)
Click to expand...
Click to collapse
As said by @leo91919 is only for install apks (sadly).

in step 1: "1. procured the APK file". Does the apk to install is on the phone or you have to pass it to the pc?
Sorry for the question but i don't know
Sorry for my English.

sanangel said:
in step 1: "1. procured the APK file". Does the apk to install is on the phone or you have to pass it to the pc?
Sorry for the question but i don't know
Sorry for my English.
Click to expand...
Click to collapse
You have to download it to the pc and put in on the install folder of "minimal adb and fastboot"

download,install , in cmd have Can't found localhots)
but i dont have android phone

timnwyatebe said:
download,install , in cmd have Can't found localhots)
but i dont have android phone
Click to expand...
Click to collapse
How can you use an android wear without an android phone?

hum just a question ... with this method .. you could push towelroot.apk to the moto360 to root it?

basti84 said:
hum just a question ... with this method .. you could push towelroot.apk to the moto360 to root it?
Click to expand...
Click to collapse
You can push towelroot but i don't know if it will root your watch

When I reset the watch (Factory Reset). Will my installed APK's be gone?

Thatgrass said:
When I reset the watch (Factory Reset). Will my installed APK's be gone?
Click to expand...
Click to collapse
Yes they will!

Just tried this on latest update LDZ220 (5.1.1) getting Failure [DELETE_FAILED_INTERNAL_ERROR] for uninstall command
and
Error: java.lang.SecurityException: Permission Denial: attempt to change component state from pid=9119, uid=2000, package uid=10009 for disable command
please help

thechamp007 said:
Just tried this on latest update LDZ220 (5.1.1) getting Failure [DELETE_FAILED_INTERNAL_ERROR] for uninstall command
and
Error: java.lang.SecurityException: Permission Denial: attempt to change component state from pid=9119, uid=2000, package uid=10009 for disable command
please help
Click to expand...
Click to collapse
I don't know :/ I still haven't received the 5.1.1 update, I will check when it will arrived.

simoneluconi said:
I don't know :/ I still haven't received the 5.1.1 update, I will check when it will arrived.
Click to expand...
Click to collapse
If you want to force the 5.1.1 update check out the portal post, worked for me.
http://www.xda-developers.com/moto-360-5-1-1-forced-ota-performance-impressions/
---------- Post added at 02:30 PM ---------- Previous post was at 01:55 PM ----------
thechamp007 said:
Just tried this on latest update LDZ220 (5.1.1) getting Failure [DELETE_FAILED_INTERNAL_ERROR] for uninstall command
and
Error: java.lang.SecurityException: Permission Denial: attempt to change component state from pid=9119, uid=2000, package uid=10009 for disable command
please help
Click to expand...
Click to collapse
Worked for me on LDZ220.
I used adb -e instead of adb -s localhost:4444
I got the Failure [DELETE_FAILED_INTERNAL_ERROR] error until I used the correct package name.
I got the correct package name by breaking this into two parts. adb -s localhost:4444 shell pm list packages –f
adb -e shell
pm list packages -f
then exit to get out of the shell.
I'm not sure about your install error, but I had to tap Allow bluetooth debugging on the watch, after I entered the install command.

fuzzybuffalo said:
Worked for me on LDZ220.
I used adb -e instead of adb -s localhost:4444
I got the Failure [DELETE_FAILED_INTERNAL_ERROR] error until I used the correct package name.
I got the correct package name by breaking this into two parts. adb -s localhost:4444 shell pm list packages –f
adb -e shell
pm list packages -f
then exit to get out of the shell.
I'm not sure about your install error, but I had to tap Allow bluetooth debugging on the watch, after I entered the install command.
Click to expand...
Click to collapse
OK let me articulate my steps, may be i am doing something wrong
NOTE : I have already authorize adb on both watch and phone to always allow debugging from my PC, so prompt is not there every time
1. adb forward tcp:4444 localabstract:/adb-hub
2. adb connect localhost:4444
3. adb -s localhost:4444 shell
4. pm uninstall com.motorola.targetnotif
ERROR : Failure [DELETE_FAILED_INTERNAL_ERROR]
5. pm disable com.motorola.targetnotif
ERROR : java.lang.SecurityException: Permission Denial: attempt to change component state from pid=11546, uid=2000, package uid=10009
Second attempt with -e
1. adb forward tcp:4444 localabstract:/adb-hub
2. adb connect localhost:4444
3. adb -e shell
4. pm uninstall com.motorola.targetnotif
ERROR : Failure [DELETE_FAILED_INTERNAL_ERROR]
5. pm disable com.motorola.targetnotif
ERROR : java.lang.SecurityException: Permission Denial: attempt to change component state from pid=11546, uid=2000, package uid=10009

thechamp007 said:
OK let me articulate my steps, may be i am doing something wrong
NOTE : I have already authorize adb on both watch and phone to always allow debugging from my PC, so prompt is not there every time
1. adb forward tcp:4444 localabstract:/adb-hub
2. adb connect localhost:4444
3. adb -s localhost:4444 shell
4. pm uninstall com.motorola.targetnotif
ERROR : Failure [DELETE_FAILED_INTERNAL_ERROR]
5. pm disable com.motorola.targetnotif
ERROR : java.lang.SecurityException: Permission Denial: attempt to change component state from pid=11546, uid=2000, package uid=10009
Second attempt with -e
1. adb forward tcp:4444 localabstract:/adb-hub
2. adb connect localhost:4444
3. adb -e shell
4. pm uninstall com.motorola.targetnotif
ERROR : Failure [DELETE_FAILED_INTERNAL_ERROR]
5. pm disable com.motorola.targetnotif
ERROR : java.lang.SecurityException: Permission Denial: attempt to change component state from pid=11546, uid=2000, package uid=10009
Click to expand...
Click to collapse
OK, well I am just learning, but isn't com.motorola.targetnotif a system app?
If it is I thought you had to be root to uninstall or disable a system app.
If you are rooted try su in between adb -e shell and your pm uninstall command.
Edit: I get the same errors, so I think you need root.

fuzzybuffalo said:
OK, well I am just learning, but isn't com.motorola.targetnotif a system app?
If it is I thought you had to be root to uninstall or disable a system app.
If you are rooted try su in between adb -e shell and your pm uninstall command.
Edit: I get the same errors, so I think you need root.
Click to expand...
Click to collapse
thechamp007 said:
OK let me articulate my steps, may be i am doing something wrong
NOTE : I have already authorize adb on both watch and phone to always allow debugging from my PC, so prompt is not there every time
1. adb forward tcp:4444 localabstract:/adb-hub
2. adb connect localhost:4444
3. adb -s localhost:4444 shell
4. pm uninstall com.motorola.targetnotif
ERROR : Failure [DELETE_FAILED_INTERNAL_ERROR]
5. pm disable com.motorola.targetnotif
ERROR : java.lang.SecurityException: Permission Denial: attempt to change component state from pid=11546, uid=2000, package uid=10009
Second attempt with -e
1. adb forward tcp:4444 localabstract:/adb-hub
2. adb connect localhost:4444
3. adb -e shell
4. pm uninstall com.motorola.targetnotif
ERROR : Failure [DELETE_FAILED_INTERNAL_ERROR]
5. pm disable com.motorola.targetnotif
ERROR : java.lang.SecurityException: Permission Denial: attempt to change component state from pid=11546, uid=2000, package uid=10009
Click to expand...
Click to collapse
Exactly, i think that "com.motorola.targetnotif" is a system app, so you have to be rooted to uninstall it.
EDIT: Is under "/system/priv-app/" so you have to be rooted for uninstall it.

For me it still says not connected for host...