adbd running on device, cannot connect from host - Android Software/Hacking General [Developers Only]

Hello all,
As per my previous thread, I now have a rooted nonsense free Android.
Now I'm trying to connect to it via adb which is proving tricky.
The device is rooted (unrevoked/clockwork mod) and in recovery mode it'll adb just like that. However, when the device is running, I can't pick it up. I get:
Code:
$ adb devices
List of devices attached
???????????? no permissions
Now I have the old superuser skull and crossbones app thingy on my phone running. I've also tried to connect locally using connectbot and this works, I get sh running just fine. I can also su and get root.
However, even if I stop and restart adbd it changes nothing from the pov of the host... in other words it's not letting me connect.
Specifically, I can see:
Code:
sh-3.2# ps
...
root 1978 1 3142 200 ffffffff 0000f474 /sbin/adbd
...
$ whoami
whoami: unknown uid 0
from connectbot on the device
A pointer in the right direction would be wonderful!
_glokta.

Related

Sharp IS01: introduce the root acquisition

Hi, I'm Japanese developer.
Please excuse my poor English.
I introduce the root acquisition these steps.
Take full responsibility for your actions.
Please download here and extract it.
root.7z: j.mp/fRq6Nr mirror: j.mp/eok7vq
Require: superuser.apk
Prepare:
Code:
$adb push install.tar.gz /sqlite_journals
$adb push busybox_s /sqlite_journals
$adb shell chmod 0755 /sqlite_journals/busybox_s
$adb shell
$cd /sqlite_journals
$./busybox_s tar xvzf install.tar.gz
Step1: Get root.
from IS01 Android Terminal,
Code:
$cd /sqlite_journals/install
$sh install.sh
Input install step [1/2/3/4/update/uninstall] : 1
If you become superuser, the dollar sign should change to a hash (or sharp) sign.
Success: $ → #
Step2: Install hack binaries at "/sqlite_journals/root".
from IS01 Android Terminal,
Code:
$cd /sqlite_journals/install
$sh install.sh
Input install step [1/2/3/4/update/uninstall] : 2
Enable iptables?[Y/n] : n
Enable samba?[Y/n] : n
Enter to reboot : Enter
Step3: Write Hacked kernel in recovery area.
from IS01 Android Terminal,
Code:
$/sqlite_journals/install/au
↑You have to get root.
Code:
#cd /sqlite_journals/install
#sh install.sh
Input install step [1/2/3/4/update/uninstall] : 3
Write kernel?[y/N] : y
Enter to reboot recovery
*UPDATE
You're free to do so. XD
Step4: Create symbolic links in system.
and replace libshsecure_jni.so.
from IS01 Android Terminal,
Code:
$/sqlite_journals/install/au
↑You have to get root.
Code:
#cd /sqlite_journals/install
#sh install.sh
Input install step [1/2/3/4/update/uninstall] : 4
Q. What is hacked kernel?
A. This kernel is release of the NAND lock.
You can write after mount system.
Q. What is /sqlite_journals/install/au?
A. It is su binary. But it became impossible to use the market when it was a name of su, it changed on purpose to the name of au.
Q. Why don't you write it at boot area?
A. Also there is no way to repair broken IS01 because blocked fastboot(cant use fastboot).
Q. So boot area?
A. NV softs built recovery_kit image.
recovery_kit_v130.7z: j.mp/hXEp7C mirror: j.mp/f4SHCq
Code:
$adb push recovery_kit.img /data/recovery_kit.img
from IS01 Android Terminal,
Code:
$/sqlite_journals/install/au
↑You have to get root.
Code:
#cd /sqlite_journals/install
#flash_image boot_wr /data/recovery_kit.img
Q. How to use recovery_kit?
A. When mirror recovery image is hidden, you input "Home+Power".
But if your PC is Windows, unplug USB cable.
Code:
HotKey:
Boot recovery partition: Home+Back
Boot boot partition: Home+Menu
Enable QXDM: Alt+Q
Start adbd recovery: Alt+A
Start recovery utility: Alt+R
Support command:
sh
toolbox
busybox
mount_system: Mount system partision to /system2
mount_data: Mount data partision to /data
Thanks, love_marijuana@twitter, MobileHackerz@twitter, goroh_kun@twitter, gcd_org@twitter, nvsofts@twitter, Yukto8492@twitter and more.
Wrote by DevRenax@twitter. j.mp/g0pDZz
P.S I am transplanting CM6 for IS01.
[: permission denied
Took the plunge and tried this...
Got stuck at step 1:
$ sh install.sh
sh install.sh
IS01 root installer ver0.1.0
Input install step [1/2/3/4/update/uninstall] : 1
1
[: permission denied
Install STEP1
[*] CVE-2010-EASY Android local root exploit (C) 2010 by 743C
[*] checking NPROC limit ...
[+] RLIMIT_NPROC={1856, 1856}
[*] Searching for adb ...
[+] Found adb as PID 31307
[*] Spawning children. Dont type anything and wait for reset!
[*]
[*] If you like what we are doing you can send us PayPal money to
[*] [email protected] so we can compensate time, effort and HW costs.
[*] If you are a company and feel like you profit from our work,
[*] we also accept donations > 1000 USD!
[*]
[*] adb connection will be reset. restart adb server on desktop and re-login.
[: permission denied
Shut down terminal and reexecute this script!
$
xxolloxx said:
Took the plunge and tried this...
Got stuck at step 1:
$ sh install.sh
sh install.sh
IS01 root installer ver0.1.0
Input install step [1/2/3/4/update/uninstall] : 1
1
[: permission denied
Install STEP1
[*] CVE-2010-EASY Android local root exploit (C) 2010 by 743C
[*] checking NPROC limit ...
[+] RLIMIT_NPROC={1856, 1856}
[*] Searching for adb ...
[+] Found adb as PID 31307
[*] Spawning children. Dont type anything and wait for reset!
[*]
[*] If you like what we are doing you can send us PayPal money to
[*] [email protected] so we can compensate time, effort and HW costs.
[*] If you are a company and feel like you profit from our work,
[*] we also accept donations > 1000 USD!
[*]
[*] adb connection will be reset. restart adb server on desktop and re-login.
[: permission denied
Shut down terminal and reexecute this script!
$
Click to expand...
Click to collapse
hmm...
ok, tell me the results
1: What is your baseband version?
2:
Code:
$adb shell uname -a
3: from android terminal. Try running a few times, about 10times?
Code:
$/sqlite_journals/install/rageagainstthecage
4: after running Step1: Get root,
from android terminal.
Code:
$id
Baseband: 1.00.05
adb shell uname -a
uname: permission denied
$id
id
uid=2000(shell) gid=2000(shell) groups=1003(graphics),1004(input),1007(log),1011
(adb),1015(sdcard_rw),3001(net_bt_admin),3002(net_bt),3003(inet)
I ran
$/sqlite_journals/install/rageagainstthecage
...about 7 times, $ changed to #
Then I got stuck at:
$ cd /sqlite_journals/install
cd /sqlite_journals/install
$ sh install.sh
sh install.sh
IS01 root installer ver0.1.0
Unable to chmod ./busybox: Operation not permitted
Input install step [1/2/3/4/update/uninstall] : 1
1
[: permission denied
Install STEP1
Unable to chmod ./rageagainstthecage: Operation not permitted
[*] CVE-2010-EASY Android local root exploit (C) 2010 by 743C
[*] checking NPROC limit ...
[+] RLIMIT_NPROC={1856, 1856}
[*] Searching for adb ...
[+] Found adb as PID 8052
[*] Spawning children. Dont type anything and wait for reset!
[*]
[*] If you like what we are doing you can send us PayPal money to
[*] [email protected] so we can compensate time, effort and HW costs.
[*] If you are a company and feel like you profit from our work,
[*] we also accept donations > 1000 USD!
[*]
[*] adb connection will be reset. restart adb server on desktop and re-login.
[: permission denied
Baseband: 1.00.05
Click to expand...
Click to collapse
No problem.
I ran
$/sqlite_journals/install/rageagainstthecage
...about 7 times, $ changed to #
Click to expand...
Click to collapse
You got root. Next, run this command after reboot Android Term.
Code:
$/sqlite_journals/install/su
If you got root and installed superuser.apk, it will auto start superuser.apk.
triangle and exclamation point on boot
I did the steps above and I see it boot the recovery image, then it transitions into a boot screen that has a triangle with exclamation point. What do I do now?
Thanks in advance
I got to the recovery screen and enabled adb recovery, but adb states the device is offline. How do I get it online or push a new image.
plenpak said:
I did the steps above and I see it boot the recovery image, then it transitions into a boot screen that has a triangle with exclamation point. What do I do now?
Thanks in advance
Click to expand...
Click to collapse
you, too.
Sorry, I did not explain qxdm...
Code:
from hacked kernel
#echo 1 > /sys/devices/platform/msm_hsusb_periphera/qxdm_enable
or
recovery_kit -> Enable QXDM
And recovery_kit is unstabled. Try running a few times.
Be all about timing.
ScreenShot(recovery_kit) j.mp/hbHiL9
Thanks. You were right. Timing was everything. I now have a rooted device. I did have to modify the install.sh script. It wasnt working for me intially.
Have you tried to load Froyo or Gingerbread on it yet? Have you tried Cyanogen mod? I have Cyanogen mod 7 running on my N1, and would like to attempt a port to the IS01.
I did have to modify the install.sh script. It wasnt working for me intially.
Click to expand...
Click to collapse
Actually, I did not created it, and I have not tried. XD
this script was created by love_marijuana@twitter.
If that's ok, upload modified scripts please?
Have you tried to load Froyo or Gingerbread on it yet? Have you tried Cyanogen mod? I have Cyanogen mod 7 running on my N1, and would like to attempt a port to the IS01.
Click to expand...
Click to collapse
Wow, you have nice device!
I transplanting CM6.
I have github acount. -> github.com/CM4IS01
But this rom is very buggy.
Not work:
Bluetooth, GPS, Accelerator Sensors, 3D Acceleration, Sound and more...
Sharp IS01
Hi Sharp IS01 users....don t waist your time with this device.....AU launch this month 04/2011...a HTC EVO 4G...with HDMI and WIMAX router mode for acess a internet from a notebook or others devices....GOOD DEAL...
Help me pls,
I'm stuck at Step1, too
$cd /sqlite_journals/install
$sh install.sh
IS01 root installer ver0.1.0
Unable to chmod .busybox: Operation not permitted
Input install step [1/2/3/4/update/uninstall] :
My phone's build number: 01.00.02
Model number: SH-01B
(Docomo)
Thanks much
@ DevRenax, I can't find this file, CM6byDevRenax-06242011-IS01.7z . Are you still working on it? I'd like to try it for my SH-10B device, base band 01.00.02. Could you post another link to it? Thanks
plenpak said:
I did the steps above and I see it boot the recovery image, then it transitions into a boot screen that has a triangle with exclamation point. What do I do now?
Thanks in advance
Click to expand...
Click to collapse
I skip all the way to flash recovery_kit.img since I didnt use the steps to get root. Now I am stuck at the triangle with exclamation point screen. How did you bypass it?
Edit: ok, the recovery_kit works with the hotkeys but, it still won't let my SH-10B boot the system. Does anyone have the ADB usb driver for win7-64? The one that came with the cd-rom and from Sharp's webite doesn't install on my computer. If I can use adb, I could probably fix this.
I'm very new to do rooting
I try to understand your description.
But i don't know how to start.
I have already download and try to use superuser but i don't know how to write the command line as you shown.
What program i need for writing command?
Actually I just want my LYNX SH-10B to read another language beside Jap and Eng.
If you have another easier way pls help......
BEN
Ok, I believe I know what screwed my system from booting. This;
Code:
#cd /sqlite_journals/install
#flash_image boot_wr /data/recovery_kit.img
From this code that I use the recovery_kit was flash to my boot partition and replaced the boot.img. That is why it goes from recovery-kit boot screen to recovery mode screen and does not start android as mentioned in my previous post. It should have been: flash_image recovery. So I've lost my boot.img for the stock android 1.6. Can anyone who has the device post it so I may flash it back on and get my SH-10B running again. Thanks

[Q] Can I adb localhost without root?

I have the XOOM wifi and not ready to root it yet. But I did want to get adb listening over tcp ip. I suspect this is where I'm failing.
I already tried this on my XOOM. Not getting any verbose feedback saying if anything failed or succeeded.
Code:
setprop service.adb.tcp.port 5555
stop adbd
start adbd
I just want to be able to run some adb commands locally from my terminal app on my XOOM.
Bump. Somewhere where I don't have PC access atm.

USCC Mesmerize Rooting on Official 2.2 (Froyo)

Okay, this was my first time trying to root my phone and it would figure that non of the automated methods worked for me. Still, I was able to get root on my US Cellular Samsung Galaxy S Mesmerize (SCH-i500 for the kids keeping track at home) and these are the steps that I took. I hope this helps others who may be scratching their head wondering what to do when the developers haven't gotten around to (read: forsaken) us.
The nice thing about this method is that it doesn't require Windows (though you still do download SuperOneClick).
NOTE: This is only for an officially updated Mesmerize. Rooting is unnecessary for the leaked version.
APOLOGY: I can't post any links to anything outside the forum as I am a newer member, so, sorry for not being able to post URLs.
1. Download the Android SDK from the Android developer website and install/unzip it. You may need to add the path to the adb tool (found under platform-tools for me) to your PATH variable.
2. Download the SuperOneClick tool and unzip it
3a. If you are using Windows, then make sure to install the drivers for your phone. I don't have Windows, so don't ask me which file to download. Sorry.
3b. Enable USB Debugging on your phone (Settings->Applications->Development->Check "USB Debugging").
4. Connect your phone to your computer using the USB cable
5. Open a shell (or command prompt on Windows) and change directories to where you unzipped SuperOneClick
6. Run the following commands to copy files to your device
A. adb push psneuter /data/local/tmp/psneuter
B. adb push busybox /sdcard/busybox
C. adb push su-v2 /sdcard/su
NOTE: A quick note of each of these files.
A. psneuter - an exploit to gain root access temporarily on your phone
B. busybox - a compilation of common unix commands to help you along the CLI world
C. su - the super-user command used to gain elevated privileges
7. Run the following command to get a command line interface to your device
adb shell
At this point, you should see a $ prompt indicating that you are on your phone.
From here, you will change directories to where you put the exploit, change the permissions so you can run it, copy over the files that we need to sustain root access, and finally, install the Superuser.apk app so that you can manage root access from the UI.
Execute the following commands:
$ cd /data/local/tmp
$ chmod 777 psneuter
$ ./psneuter
Here, you will be disconnected from your device. This is normal. Just run "adb shell" again to get back in, though now, you will notice that the prompt has changed to a #. The following commands will reflect that.
# mount -t rfs -o remount,rw /dev/block/st19 /system
# cd /system/xbin
# cat /sdcard/busybox > busybox
# cat /sdcard/su > su
# chmod 4755 busybox
# chmod 4755 su
# exit
Now, you will be back on your computer. Type the following to install the Superuser.apk app.
adb install Superuser.apk
That should do it! You now have root access. Go ahead and try to install Titanium Backup (requires root). You can also install a terminal app or anything else.
I hope this helps. Report your successes/failures in the comments.

[Q] Turning on Bluetooth in flight mode

Hi guys,
hope this is the right forum.
I switched from iPhone4 now to the new Samsung Galaxy S II with 2.3.3 and brought my bluetooth Sennheiser MM450 which I would like to use in flight.
Anyway when I turn on the flight mode I can't turn on Bluetooth anymore!?
On my iPhone this was possible.
Is there any way to get Bluetooth in flight mode working as I dont wanna have my phone searching for networks during flight.
Any other App/hint etc. for this?
My Samsung is rooted by the way...
Like this?
Otherwise, on a more serious note: http://code.google.com/p/android/issues/detail?id=3289, see comment 42 there.
doktornotor said:
Otherwise, on a more serious note: ... see comment 42 there.
Click to expand...
Click to collapse
Thanks.... maybe I am too rookie for that... I installed QuickSSHd and logged in from my Putty but can't issue these commands:
# id
uid=0(root) gid=0(root) groups=0(root)
# adb remount /data
adb: not found
# sqlite3 /data/data/com.android.providers.settings/databases/settings.db
sqlite3: not found
So I searched but following issue:
# find / -iname adb
/sys/devices/virtual/usb_composite/adb
/sys/class/usb_composite/adb
# /sys/class/usb_composite/adb
/sys/class/usb_composite/adb: permission denied
adb is supposed to be used from your PC, need to install Android SDK there, not try to run it from phone shell.
Thanks, will try that out now and just installing JDK and Android SDK R11...
Ok. If you get permissions denied stuff, I would suggest loosely following this one:
http://dylanmtaylor.com/2010/10/19/closer-to-a-proper-froyo-limit-removal-fix/
For the remount /system thing, you need to check the actual device being mounted by running something like:
Code:
$ mount | grep /system
as it differs from device to device.
(Other way would involve getting ro.secure=0 which might be more complex than needed here. You can check what you have by getprop | grep ro.secure)

help with Acer a200 auto root batch file...

hello,
I am trying to set up a simple batch/ script to "automate" the root process.
I am using the mempodroid exploit to gain root access. The problem is this:
I am using this in my script,
adb shell /data/local/mempodroid 0xd9f0 0xaf47 sh
when I use this I get a return of [email protected]:/ # and the cmd window locks up and I can not enter anything.
however if I manually enter this,
adb shell
I get back [email protected]:/ $
and then I enter,
/data/local/mempodroid 0xd9f0 0xaf47 sh
I get back [email protected]:/ #
and that is what I want.
I don't know how to automate it in a working way. Any thoughts?
finished this up and have a working simpleRoot! check it out at acertabletforums.com
and now i have compiled ClockWorkMod for A200 as well! check it out at the same spot!

Categories

Resources