Related
I've searched a lot, but did not find a solution.
When I connect my HTC Kaiser with Android Ion 1.5 on the top to my Linux box (all UDEV settings are as recommended), the adb utility (launched as root) does not recognize it correctly. It shows a set of questionmarks instead of the device name:
Code:
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
???????????? device
adb basic commands (pull/push/install/shell) work, though, but DDMS does not work and I can't debug my application when the device is attached.
Does somebody have a solution?
You need to run the adb server as root. Use su or sudo to run these:
Code:
./adb kill-server
./adb start-server
You can then use adb and ddms as a normal user. If you use fastboot, you may find you need to run that as root as well.
it is root
Super Jamie said:
You need to run the adb server as root. Use su or sudo to run these:
Code:
./adb kill-server
./adb start-server
You can then use adb and ddms as a normal user. If you use fastboot, you may find you need to run that as root as well.
Click to expand...
Click to collapse
Like I mentioned in my question - I do run adb as root.
When it's launched not as root, I can not even do "adb shell" and
"adb devices" shows:
"????????????? Permission denied". So, it is root, I assure.
BTW, on my work Windows 2k3 machine I can use ddms, but
"adb devices" still shows some garbage letters instead of the device name.
Sorry for my English, if my explanation is not clear.
Hey Guys,
I Clockwork3'd my Aria, but I wanted to update my sources (thread 730398) so I can get non market apps. When I follow the instructions in that post I get an error:
Code:
./adb remount
remount failed: operation not permitted
'adb devices' does show my Aria's SN, I'm su'd and I'm running in debug mode. I also chowned everything in the android sdk tools and its subdirectories.
Here's the question -
In searching, I found (thread 614645) that suggested ro.secure wasn't set properly, and sure enough if I do:
Code:
./adb shell
$ getprop ro.secure
1
$
Shouldn't applying clockwork have set that properly? Would the instructions at (thread 8041739 post 9 ) be the right steps to resolve this on an Aria?
Thanks!
PS - sorry I can't post direct links.
if you have all the drivers installed, it should work...
which OS are you using?? (Mac, Win7, etc)
dont rund SDK command in Clockwork, with phone on connect data cable and select "charge only" when asked.
the ./ command is used for Linux i think, i never got that command to work either. just go to the folder where SDK/Tools is located in CMD prompt or Terminal(depending on the OS) and run the following command:
adb remount
hope this helps a bit
I had a lot of issues with driver installs on Windows 7, so I'm doing this on a netbook with Ubuntu netbook remix. Also tried the reflash CD, similar issue.
Right, so with Ubuntu, and the cable my phone came with (have tried a few others just in case)
1. phone on and operational
2. plug in to laptop
3. phone gives happy USB connected and Charge Only notifications
4. fire up terminal window, and su
5. type ./adb remount
and I get the error above. If I do kill-server to refresh it, I get the demon starting successfully on port 5037.
Yeah, I was hoping I'd just missed something stupid. Should I need to modify the boot.img file outside of what Clockwork did?
My symptoms match those described in thread 685146 post #3, however, I've only applied Clockwork (which seems to work) not done anything else funky.
I have my windows 7 machine at the same point now -
adb remount gives 'remount failed: operation not permitted'
and
getprop ro.secure at the adb shell returns 1.
I think this means there's something wrong on the phone, if both machines act the same.
One other data point, I noticed the new Superuser Permissions app that installing clockwork gave me is asking to give superuser permissions to /system/bin/sh when I try to run the adb shell, but it doesn't trigger that when I do the adb remount.
Not sure what this means, any ideas most welcome - TIA!
steps here fixed it, thanks - http://forum.xda-developers.com/showthread.php?t=730398
I've been primarily following the instructions available at http://forum.xda-developers.com/showthread.php?t=1443071, however I've run into some basic issues.
When I run BurritoRoot3 (verified off the big red 3 in the app), the app does not give me a "root" option and immediately opens a dialog box requesting me to "run /data/local/tmp/BurritoRoot3.bin --root" through adb to start the process?"
I have the kindle device listing in "adb devices" as "7A7C002600000001 device"
I try to run the command listed and get an error that the bin file does not exist.
"adb reboot" does reboot the device
"adb root" gives me "adbd cannot run as root in production builds"
the one automatic script for mac & 6.2.2 keeps giving me "error: device not found" errors.
-----
Everything I can find to test the computers install of ADB seems to verify that its working correctly and my forum searching + google search skills are failing me: anyone know some forum threads that cover this?
- the app does not give you a root option - it only guides you what to do
- have you followed all steps ?
adb shell chmod 777 /data/local/tmp
adb install BurritoRoot3.apk
<go open the app now>
adb shell /data/local/tmp/BurritoRoot3.bin --root
adb shell /data/local/tmp/BurritoRoot3.bin --install
maybe you have to do the adb commands with ./ in front (eg ./adb whatever)
t4nn3d1n said:
I've been primarily following the instructions available at http://forum.xda-developers.com/showthread.php?t=1443071, however I've run into some basic issues.
When I run BurritoRoot3 (verified off the big red 3 in the app), the app does not give me a "root" option and immediately opens a dialog box requesting me to "run /data/local/tmp/BurritoRoot3.bin --root" through adb to start the process?"
I have the kindle device listing in "adb devices" as "7A7C002600000001 device"
I try to run the command listed and get an error that the bin file does not exist.
"adb reboot" does reboot the device
"adb root" gives me "adbd cannot run as root in production builds"
the one automatic script for mac & 6.2.2 keeps giving me "error: device not found" errors.
-----
Everything I can find to test the computers install of ADB seems to verify that its working correctly and my forum searching + google search skills are failing me: anyone know some forum threads that cover this?
Click to expand...
Click to collapse
You have to make sure that you do this command:
adb shell chmod 777 /data/local/tmp
Otherwise it will not make a "BurritoRoot3.bin" file, which means no root.
Install the BurritoRoot3.apk on your kindle, and go into the app.
After that is finished, input:
adb shell /data/local/tmp/BurritoRoot3.bin --root
Then:
adb shell /data/local/tmp/BurritoRoot3.bin --install
I found http://forum.xda-developers.com/showthread.php?t=1410223 which has that chmod command in it. Naturally I found that thread 10 minutes after I posted and was so dumbstruck with myself that I didn't post a reply to my own post.
The device is rooted now and I installed the Alpha Release of MIUI 4.0.? and naturally a few things don't work. Trying again with MIUI's 2.3 stable release (don't know the version number off the top of my head)
Thanks for the quick reply and looking out
Hello, recently I've ran into a stupid problem after unlocking bootloader on my M7. Here is what happened, after unlocking I was not able to use my phone in debugging mode, the authorization pop-up didn't show up wherever I connected my phone to PC in ADB mode. This was not Drivers fault I just lost RSA Key, I managed to get it back, I hope it will help you also.
To get RSA keys you need to do next thing.The trick is to create the .android directory elsewhere, for example on the SD Card:
You need Android Terminal Emulator and Root for this operation. ( Link to Android Terminal Emulator: https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=en )
Open Android Terminal Emulator and write:
adb kill-server
HOME=/sdcard adb start-server
At this point you should have /sdcard/.android and the 2 keys in it.
Then just copy adbkey from your phone to your computer into C:/Users/YOURNAME/.android then write in terminal.
stop adbd
start adbd
Then connect you phone in ADB mode Wifi or USB and check again:
adb kill-server
adb start-server
adb devices
Now authorization prompt should pop up!
This issue is also known as Unauthorized device in ADB mode.
Good luck!
I recently bought a Joying JY-HCS01P2 head unit. I am content with the general performance of the head unit for music, navi, etc. However, I cannot find any good options in terms of rooting the device. My primary interest is getting open access to the bluetooth settings. The unit only seems to allow pairing to a phone or certain obd2 adapters. I am trying to get it to function with a bluetooth adapter I use for datalogging and tuning on an aftermarket engine computer. The unit will find this BT adapter and say device connected, but no app will see it and the BT chain ICON shows as broken.
The info on the head unit is
PN JY-HCS01P2
CPU ARM Cortex-A53 eight core 2+32G PX5
MCU: JY_(R68)_26_C26_6026_CAN(All)
I have tried accessing the unit through both of the 2 USB connections with ADB, but have not had any success. The unit will not show up at all on the PC device manager. Doing an "ADB devices" search does not list any device. The USB connections are working as the phone will function over both.
Kingoroot will get to 90% then fail.
I have tried installing BT connection apps, but when accepting to allow the app to turn on BT, it just sits there attempting to turn it on, yet the head unit will not allow it.
I've been searching this forum for the last 2 days and tried a few of the suggestions but nothings works.
Look at this thread and then look at post 10.
No guarantees.
I've got that thread bookmarked. The problem is that I cannot even get the abd to connect. It seems I need to make at least the initial connection over USB, which also seems to be locked down per my experience. I did try a tcpip connection in hopes that the factory left that door open, but no luck.
Download a terminal app from google play like jackpal terminal.
Open it and on the prompt type:
Code:
setprop persist.adb.tcp.port 5555
exit and reboot.
Try if it works now.
This is what I get after the terminal input
D:\Downloads\platform-tools-latest-windows\platform-tools>adb connect tcpip 172.20.10.14
adb: usage: adb connect <host>[:<port>]
D:\Downloads\platform-tools-latest-windows\platform-tools>adb devices
List of devices attached
* daemon not running; starting now at tcp:5037
* daemon started successfully
D:\Downloads\platform-tools-latest-windows\platform-tools>adb ddevices
adb: usage: unknown command ddevices
D:\Downloads\platform-tools-latest-windows\platform-tools>adb devices
List of devices attached
D:\Downloads\platform-tools-latest-windows\platform-tools>adb connect 172.20.10.14
unable to connect to 172.20.10.14:5555: cannot connect to 172.20.10.14:5555: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. (10060)
D:\Downloads\platform-tools-latest-windows\platform-tools>
Used method for adb over wifi, root does not stick
I setup my working usb adb, and used your install.bat as a guide
Every command returned error free, root did not stick after reboot.
surfer63 said:
Download a terminal app from google play like jackpal terminal.
Open it and on the prompt type:
Code:
setprop persist.adb.tcp.port 5555
exit and reboot.
Try if it works now.
Click to expand...
Click to collapse
jon volk said:
This is what I get after the terminal input
D:\Downloads\platform-tools-latest-windows\platform-tools>adb connect tcpip 172.20.10.14
adb: usage: adb connect <host>[:<port>]
Click to expand...
Click to collapse
You need to execute my setprop command in the android terminal on your head unit. Did you do that?
And the scripts from your linux or windows pc.
I did execute the setprop command on the head unit. Should there have been a response after entering that command? I need to try it again when I have some more time to make sure everything is correct next time.
Tried it again a few times and no luck. I am finding it strange that i can’t even get it to show up on the drive manager on my pc over USB
jon volk said:
Tried it again a few times and no luck. I am finding it strange that i can’t even get it to show up on the drive manager on my pc over USB
Click to expand...
Click to collapse
I've got it to "work" but method does not result in root.
carter.w.jason said:
I've got it to "work" but method does not result in root.
Click to expand...
Click to collapse
Can you please open a terminal on the unit, or connect via adb (adb kill-server; adb connect w.x.y.z; adb shell)
and do on the prompt:
Code:
cat /system/bin/install-recovery.sh
ls -l /system/xbin/su*
ls -lr /system/app/Super*
Please post the results.
Edit: I forgot the 3rd command. Just added
surfer63 said:
Can you please open a terminal on the unit, or connect via adb (adb kill-server; adb connect w.x.y.z; adb shell)
and do on the prompt:
Code:
cat /system/bin/install-recovery.sh
ls -l /system/xbin/su*
ls -lr /system/app/Super*
Please post the results.
Edit: I forgot the 3rd command. Just added
Click to expand...
Click to collapse
"ls -lr" comes back as a unkown option. "ls -l" was used instead.
Code:
[email protected]:/ $ cat /system/bin/install-recovery.sh
#!/system/bin/sh
# This install-recovery.sh is installed here to start the
# seSuperuser su binary in daemon mode
/system/xbin/su --daemon &
[email protected]:/ $ ls -l /system/xbin/su*
-rwxr-xr-x root root 315940 2018-04-06 22:18 su
-rwxr-xr-x root root 0 2018-04-06 21:06 su.org
-rwxr-xr-x root root 0 2018-03-12 20:07 sugote
-rwxr-xr-x root root 289520 2018-03-12 20:07 sugote-mksh
lrwxrwxrwx root root 2018-03-17 17:44 sum -> /system/xbin/busybox
[email protected]:/ $ ls -l /system/app/Super*
-rw-r--r-- root root 1012569 2018-04-06 22:18 Superuser.apk
[email protected]:/ $
Thanks.
From the prompt ($) I can see that you are not root.
If you are in a terminal on the PX5 unit and you type "su" in the terminal :what do you get? Does the Superuser apk ask you to give root access?
do you get a "#" prompt?
surfer63 said:
Thanks.
From the prompt ($) I can see that you are not root.
If you are in a terminal on the PX5 unit and you type "su" in the terminal :what do you get? Does the Superuser apk ask you to give root access?
do you get a "#" prompt?
Click to expand...
Click to collapse
"Permission denied"
su would work when I had it rooted with kingoroot
carter.w.jason said:
"Permission denied"
Click to expand...
Click to collapse
See if you can install attached Superuser.apk and please try again.
surfer63 said:
See if you can install attached Superuser.apk and please try again.
Click to expand...
Click to collapse
Result is the exact same.
If I open Superuser, it is all blank except for "Superuser" and three menu icons at top. Older APK had the same behavior.
Root actions do not ask for any prompt
carter.w.jason said:
Result is the exact same.
If I open Superuser, it is all blank except for "Superuser" and three menu icons at top. Older APK had the same behavior.
Root actions do not ask for any prompt
Click to expand...
Click to collapse
I can't do anything further at the moment.
Do you want me to send you a script to undo it?
surfer63 said:
I can't do anything further at the moment.
Do you want me to send you a script to undo it?
Click to expand...
Click to collapse
No, that is ok. I can rerun kingoroot and get root if needed. Will probably just reflash and box it up.
I'll have my new Intel Sofia on Monday. Thanks for all the work!
I cant seems to connect. It say device not found. I have also setprop as well on my unit
GixxerRaider said:
I cant seems to connect. It say device not found. I have also setprop as well on my unit
Click to expand...
Click to collapse
Don't give incomplete statements like "I have also setprop as well". From that incomplete statement we can't see whether you used the right command and whether you did not make typos. Be complete.
It should be:
Code:
setprop persist.adb.tcp.port 5555
Did you reboot your unit afterwards? Did you also reboot your pc/laptop? Each time you do not get a connection you need to do a "adb kill-server" on your pc to make sure you initialize it again. It sometimes get "corrupted".