p2p-adb
p2p-adb copied to clipboard
cant figure some thing out
hey there i have got root shell, bussybox with root access and when i am in the shell and try to run the script i get a error saying "adb is not in your $path" "add it to path, or enable $tryStaticADB in run.sh plus i am doing in on a galaxy s3
dont worry didnt have it in the /data folder silly me
I tested it yesterday on my Galaxy S3 with CyanogenMod 10 and it worked. It's awesome :D
Yer it was my mistake haha forgot to put it in to the right file waiting for my otg cable from US now as over priced in nz
when i try to launch it on my nexus 7, i get:
: not found : not found : not found : not found : not found ' unexpectedsyntax error: 'in
What does that mean? What do I have to do?
@Knyk14 How are you launching it from the N7? Sounds like you might be invoking run.sh incorrectly. Do you have busybox installed?
When attacking nexus (non root) doesn't seem To work but works fine with a (non root) s3 But getting the pattern did not work every thing else did Tho Is it just me ??
To get the gesture pattern, you need to be root. It is stored in /data/system/gesture.key as a system readable only file.
Hey Kos, Im not sure if im noobing out but when I try to run sh ./run.sh im receiving a similar error to Kynk14. I am trying from a rooted Galazy S3. I have busybox and I put p2p-adb folder in the /data folder. Says :not found: :not found: :not found: ./run.sh[92]: syntax error: 'in^M' unexpected any help would be super appriciated. -Ace
I'm getting the same issue as Kynk14. I'm rooted, and running the commands from Terminal IDE.
Device: Samsung S2 Skyrocket (SGH-i727) Rooted: Yes SU: Superuser app
Actions performed: Launch Terminal IDE app from device, execute "su" command (and receive overlay notifier that Terminal IDE has been granted Superuser), "cd sdcard", "cd p2p-adb" (folder holding all .sh files and AntiGuard.apk), "sh ./run.sh", then the error fires off in the terminal.
Weird. Can you guys please post either a screenshot or a terminal dump of the output?
Sure thing. It's funny cause i took a screenshot as i made my previous comment, but figured you wouldn't want it. I'll give you both.
-Begin Dump- [email protected]:~$ su #cd sdcard #cd external_sd #cd p2p-adb #sh ./run.sh : not found : not found : not found : not found : not found ./run.sh: 92: Syntax error: expecting "in" #exit [email protected]:~$ -End Dump-
img: http://s10.postimage.org/o9urt1wd5/SC20121112_113454.png
I'm using stock Gingerbread 2.3.6, however i DID confirm that i could run in host mode using the OTG cable from Hak5: http://hakshop.myshopify.com/collections/accessory/products/micro-to-micro-otg
Hey guys mine is similar but a little different. Ive already ran Busybox to confirm installation.
#cd /data/p2p-adb/ #sh ./run.sh : not found: : not found: : not found: : not found:] : not found:] ./run.sh: 92:] Syntax error: 'in^M' unexpected 1|
On Mon, Nov 12, 2012 at 9:09 PM, cigaweed [email protected] wrote:
Sure thing. It's funny cause i took a screenshot as i made my previous comment, but figured you wouldn't want it. I'll give you both.
-Begin Dump- [email protected]:~$ su #cd sdcard #cd external_sd #cd p2p-adb #sh ./run.sh : not found : not found : not found : not found : not found ./run.sh: 92: Syntax error: expecting "in" #exit [email protected]:~$ -End Dump-
img: http://s10.postimage.org/o9urt1wd5/SC20121112_113454.png
I'm using stock Gingerbread 2.3.6, however i DID confirm that i could run in host mode using the OTG cable from Hak5: http://hakshop.myshopify.com/collections/accessory/products/micro-to-micro-otg
— Reply to this email directly or view it on GitHubhttps://github.com/kosborn/p2p-adb/issues/8#issuecomment-10313078.
Hi !
I've got the same thing that cigaweed got on a galaxy nexus rooted.
my phone (#1) detected another phone (#2) like camera. But the p2p-adb does not detect phone #2. My phone is Samsung S3 Android 4.0.4 (rooted, and busybox installed) :(. Missing something ?????????????
Hey Guys, Anyone have any insight as to what i might have done wrong? Is it because I'm on the stock ROM? Is there a specific version of busybox I need?
Did anyone get this to work or do we need to load more of the .sh files from the site i am getting the same
Hey guys, Total noob here. I see that this thread is kind of old, but I don't know etiquette of bumping threads, so let me know if I am messing up in that respect. I just cloned the repo onto my phone and I am getting the exact same error as gazzdingo. I see that gazz* resolved this error by moving ...something... into the data folder, but can someone be more specific on what was moved? I can move run.sh (as in the picture by kiddxx), or I can move the p2p-abd/ folder (as shown in ac3x04's description), or the contents of said folder, etc. I would love a more specific explanation of what files/folders should be in what locations.
I think the issue may be stemming from my environment. The noob in me has no idea how to describe this properly, but here is my best attempt. I have a pwn phone 2014 so when i open terminal emulator I can be greeted with one of 2 environments. One of which is root@hammerhead and that, I think is the stock android os. The other is root@localhost which is the pwnie side of things which I guess is a chrooted environment.
I can see that adb is installed on the hammerhead...terminal? environment? thingy? adb however is not installed on the localhost (pwnie)...version of the terminal thingy...
I have been trying to run this from the pwnie side, but it occurs to me that if adb isn't installed I cannot even hope for success. Should I install adb on that side, or should I just move the files over to hammerhead and try that?
Hardware explanation: Nexus 5 (pwnphone 2014), Rooted, Busybox 1.22.1, SuperUser app
Thanks for the help and I hope I haven't made myself look like too much of an arse.