Related
I'm trying to start busybox's httpd at boot w/o success. However, I can start it manually post-boot w/o problems. Can I enable a syslog facility so I can see what happens when the bootup script calls it?
Code:
httpd -p 80 -u 80 -h /sdcard/www -c /etc/httpd.conf
I've tried running the process as -u 80 and as -u 0, both work post-boot, not before.
It's Linux - if there is an rc.local you should be able to drop a string in there to make it start.
KaiserLinux said:
It's Linux - if there is an rc.local you should be able to drop a string in there to make it start.
Click to expand...
Click to collapse
Not that simple
There is no rc.local, but I inserted
Code:
/sbin/syslogd -O /data/log/syslog
into the beginning of init.rc, but it logs nothing.
Go into applications and turn on debugging mode. Plug your phone into your computer and run 'adb logcat' or something to that effect. You can play around with your phone and watch the log scroll by.
Your gonna need the whole ADB setup. Go to the samsung epic 4G wiki and check the article about getting root and flashing a new kernel. This will have the instructions for getting ADB on your system as well.
KaiserLinux said:
Go into applications and turn on debugging mode. Plug your phone into your computer and run 'adb logcat' or something to that effect. You can play around with your phone and watch the log scroll by.
Your gonna need the whole ADB setup. Go to the samsung epic 4G wiki and check the article about getting root and flashing a new kernel. This will have the instructions for getting ADB on your system as well.
Click to expand...
Click to collapse
I've compiled my own rooted kernel and a new busybox with syslogd to see if I can diagnose why bb's httpd isn't starting at boot. As I mentioned, it starts manually w/o a problem. adb logcat isn't very useful in this particular situation. Thanks for the reply though.
jocala said:
There is no rc.local, but I inserted
Code:
/sbin/syslogd -O /data/log/syslog
into the beginning of init.rc, but it logs nothing.
Click to expand...
Click to collapse
I'm kind of a noob myself, but I recall reading that init.rc isn't really a shell script. It has a special syntax that is parsed by Android init, I'm not sure just throwing shell commands in there is going to work. I'd post a link to the doc but I can't post links yet
coldguy said:
I'm kind of a noob myself, but I recall reading that init.rc isn't really a shell script. It has a special syntax that is parsed by Android init, I'm not sure just throwing shell commands in there is going to work. I'd post a link to the doc but I can't post links yet
Click to expand...
Click to collapse
Weird, the first 500 lines of init.rc are nothing BUT shell commands.
i.e. chmod 0666 /dev/input/event0
Anyway, further along in init.rc the daemon processes are started up. syntax looks like:
Code:
service playlogo /system/bin/playlogo
user root
oneshot
I've tried setting up my programs (httpd,syslogd) as services, no joy.
jocala said:
Not that simple
There is no rc.local, but I inserted
Code:
/sbin/syslogd -O /data/log/syslog
into the beginning of init.rc, but it logs nothing.
Click to expand...
Click to collapse
sorry to hijack your post.
but i want to know how do you modify the /init.rc,
because when i reboot, the /init.rc will automatic recovery the old verison.
did you check the /init.rc, is it modified, after your phone reboot?
Does logcat not give you the info you want?
You can go here to find out how to redirect stdout and stderr to the logcat as well.
init.rc is part of the root fs, which is compiled into the kernel. So, a custom kernel is required. Search for custom kernel for details.
Hello,
Thanks for looking at this post! I wanted to post it to the rooting thread, but I'm too much of a noob to have access to developer threads. I searched around (both here and google), but couldn't find any useful info on my problem.
I'll get right to the point. I rooted my Acer A500 (after doing an OTA update to 4.0.3), as per the instructions on this thread:
http://forum.xda-developers.com/showthread.php?t=1546593
Everything seems to have worked well (I have root access, etc), but there is something quirky with Busybox. Every time I type a command in terminal (it doesn't matter which - I use both connectbot and terminal emulator), I get a "precmd: not found" message (even for simple things like directory changes). The odd thing is: the commands work, but I still get the message. For instance, if I ask for a directory listing, I'll get the listing, and at the end, it will say precmd: not found (usually with the name of the command it's referencing, e.g. bash: precmd: not found).
It seems to be looking for it in /system/xbin/bash, but bash is in /data/local; I tried creating a symlink but it didn't work ("link failed Cross-device link"). This is really a nuisance, and I'd like to try installing some linux user-land tools, but I fear the outcome might be disastrous if the busybox tools are misconfigured somehow.
I'd appreciate and help/suggestions. Many thanks.
mdhobbes said:
"precmd: not found" message
Click to expand...
Click to collapse
Connectbot seems to set shell variable 'PS1' to "$(precmd)[email protected]$HOSTNAME:${PWD:-?} $ ".
It means your shell (the busybox's ash applet) will try to use output from 'precmd' as a part of a command prompt.
So when 'precmd' was not provided, error messages will be generated wenever a prompt was to be shown.
Though the messages should be safe to ignore, you may get rid of them by setting something harmless to PS1 like:
PS1="> ", or reset PS1 by:
unset PS1from your (busybox) shell.
# The same method should work for terminal emulator.
precmd is a shell function.
To display it run this from the default shell:
Code:
typeset -f
You will see something like
Code:
function precmd {
typeset e=$?
let " e " && print -n "$e|"
}
If you add that to one of your shell's startup files (".profile", ".bashrc", etc.) you will have a working precmd.
It works (function runs), but shows nothing neither 0 or error code. What is it?
[edit]
Nvm, my fault, figured it out
Hi all,
I rooted my Nook Simple Touch via TouchNooter 2.1.31. No hitches aside from the Market giving me a Server Error just after installing, which cleared up the next day. Since now I have my email (and in the future other sensitive apps/info) on the Nook I would like to be able to lock the screen like a full Android phone or tablet. Is this possible? I don't necessarily mean having the exact same way of locking (i.e., press the power button and the screen locks) but at least an app for doing that would be great. Any ideas?
Thanks!
Set a PIN lock on your Nook.
In an ADB shell:
Code:
am start -n com.android.settings/.ChooseLockPin
Thanks! Now if I could only get adb to work... doing adb shell gives me "error: device not found", and turning on AdbWireless and trying to connect with adb connect just hangs.
Renate NST said:
Set a PIN lock on your Nook.
In an ADB shell:
Code:
am start -n com.android.settings/.ChooseLockPin
Click to expand...
Click to collapse
Ah... SUFBS to the rescue! Did it from the terminal. Works perfectly! Thanks!
mcamou said:
Thanks! Now if I could only get adb to work... doing adb shell gives me "error: device not found", and turning on AdbWireless and trying to connect with adb connect just hangs.
Click to expand...
Click to collapse
Renate NST said:
Set a PIN lock on your Nook.
In an ADB shell:
Code:
am start -n com.android.settings/.ChooseLockPin
Click to expand...
Click to collapse
How to remove the lock?
I don't know if there is an easy user way to do this, but:
Code:
sqlite3 settings.db
delete from system where name like 'lock%';
.q
Either do this on the Nook in /data/data/com.android.providers.settings/databases/
Or else adb pull it, sqlite3 it, adb push it.
Renate NST said:
Set a PIN lock on your Nook.
In an ADB shell:
Code:
am start -n com.android.settings/.ChooseLockPin
Click to expand...
Click to collapse
Hi, I'm very new to rooting and have managed to get tinynoot to root my UK Simple Touch Glowlight. I can use the adb install in my command prompt but when I copied your script into the command prompt I just got a list of commands. I have looked at the adb command instructions here http://developer.android.com/tools/help/adb.html#commandsummary but still can't work out what to do. Would you mind giving me some slightly more detailed instructions for adding the lockscreen from a windows command prompt?
Thanks
EDIT 1: Just brought myself up to speed on shell stuff. Thank you, thank you, thank you Renate NST!!!!
Hi, I know this thread is a bit old but I am having a problem and I am bit of a blind baboon in a maze with all this.
I followed the directions as best I could: connected rooted Nook, started adb shell then:
Code:
# am start -n com.android.settings/.ChooseLockPin 1111
am start -n com.android.settings/.ChooseLockPin 1111
Starting: Intent { act=android.intent.action.VIEW dat=1111 }
Error: Activity not started, unable to resolve Intent { act=android.intent.actio
n.VIEW dat=1111 flg=0x10000000 }
Tried other things too but I can't code for toffees so..
Can you help?
icouldntfindit said:
Hi, I know this thread is a bit old but I am having a problem and I am bit of a blind baboon in a maze with all this.
I followed the directions as best I could: connected rooted Nook, started adb shell then:
Code:
# am start -n com.android.settings/.ChooseLockPin 1111
am start -n com.android.settings/.ChooseLockPin 1111
Starting: Intent { act=android.intent.action.VIEW dat=1111 }
Error: Activity not started, unable to resolve Intent { act=android.intent.actio
n.VIEW dat=1111 flg=0x10000000 }
Tried other things too but I can't code for toffees so..
Can you help?
Click to expand...
Click to collapse
Presumably that's your desired PIN (i.e. 1111?)
You don't put it on the command line, am start -n com.android.settings/.ChooseLockPin starts the PIN chooser activity on your Nook and you enter it there, twice, to set it.
cowbutt said:
Presumably that's your desired PIN (i.e. 1111?)
You don't put it on the command line, am start -n com.android.settings/.ChooseLockPin starts the PIN chooser activity on your Nook and you enter it there, twice, to set it.
Click to expand...
Click to collapse
Lmao there's something I didn't try. Thank you for replying so fast!
cowbutt said:
Presumably that's your desired PIN (i.e. 1111?)
You don't put it on the command line, am start -n com.android.settings/.ChooseLockPin starts the PIN chooser activity on your Nook and you enter it there, twice, to set it.
Click to expand...
Click to collapse
I have to say thank you, first, for providing this information! It was exactly what I wanted.
Now, though, I've been locked out of my device. I think pressure from inside my bookbag created a bunch of readings that the nook took as attempts to access the system, and I'm locked out after 'too many pattern attempts.' It says: "to unlock, sign in with your Google account." But I do that, with no response. (This is without active wi-fi, which I can't activate anyway!)
I was hoping I could use ADB to reset the PIN again, but ADB doesn't appear to recognize the system; maybe it's not opening up the device to USB until it gets unlocked.
I'm currently on the road so I can't go back to my home wi-fi...
Any suggestions?
jasonmehmel said:
Any suggestions?
Click to expand...
Click to collapse
Well, on my Nook, I'd open up the Nook, hook into the console connector and do the SQLite solution to delete the lock and reboot.
You probably never got around to soldering a console connector to your Nook.
If you had access to ADB you could do the same.
Apparently you have ADB over WiFi and the WiFi is off.
I could also boot up on Clockwork Mod Recovery and use ADB over USB.
(I already have CWM as my recovery internally.)
You could put CWM on an SD card and boot that.
Renate NST said:
...
I could also boot up on Clockwork Mod Recovery and use ADB over USB.
(I already have CWM as my recovery internally.)
You could put CWM on an SD card and boot that.
Click to expand...
Click to collapse
I basically did that. Not CWM specifically, but factory resetting it and then re-rooting it. I'm getting a lot of practice at rooting the little son of a gun...
jasonmehmel said:
... factory resetting ...
Click to expand...
Click to collapse
I didn't say anything about factory resetting.
The only way to fix things is to know what's going on.
Why don't you get a console somehow going to your device and fix the settings database?
Hello,
I have just rooted my nook ST glowlight using Nook manager, and it is my first android device so I am not very familiar with this world. I have installed android SDK on my laptop and started an adb console. I can see my device connected when I list the devices but when I run
am start -n com.android.settings/.ChooseLockPin
it says that 'am' is not recongnized as a command.
Could you please help here?
Many thanks
MRXIII said:
it says that 'am' is not recognized as a command
Click to expand...
Click to collapse
Interesting. Try
Code:
ls -l /system/bin/am
ls -l /system/bin/pm
Did you accidentally delete something?
This is the NG1 (old black Nook Glow)?
Renate NST said:
Interesting. Try
Code:
ls -l /system/bin/am
ls -l /system/bin/pm
Did you accidentally delete something?
This is the NG1 (old black Nook Glow)?
Click to expand...
Click to collapse
Hi Renate
Thank you for your reply. I am using windows, is ls supposed to work with adb ? I have tried but it says the same :/
'ls' is not recognized...
I did not delete anything as far as I know. It is the nook Simple touch glowlight (black)
thanks
Ha, ha, the joke's on me.
That "am" command is supposed to be executed in a Linux shell running over ADB.
Code:
C:\>adb shell
# am start -n com.android.settings/.ChooseLockPin
# ^C
C:\>
Renate NST said:
Ha, ha, the joke's on me.
That "am" command is supposed to be executed in a Linux shell running over ADB.
Code:
C:\>adb shell
# am start -n com.android.settings/.ChooseLockPin
# ^C
C:\>
Click to expand...
Click to collapse
Hi Renate
Happy new year.!
Is there a way to achieve lock screen using a windows shell ?
Thank you
MRXIII said:
Is there a way to achieve lock screen using a windows shell?
Click to expand...
Click to collapse
Do you mean:
Code:
C:\>adb shell am start -n com.android.settings/.ChooseLockPin
I haven't found this posted anywhere so figured it might be useful to others as well.
When you reinstall Android it is set up as a new device with a new unique Android ID. This ID is often used by apps to identify the device - for example all my internet banking apps use it to register the device with the service. To avoid having to re-register after reinstall the ID can be changed to what it was previously.
The Android ID backup/restore function is included in Titanium Backup. However, the Settings Storage (com.android.providers.settings) doesn't seem to be backed by a traditional SQLite database in Android 6.0 Marshmallow - /data/data/com.android.providers.settings/databases/settings.db is empty (0 bytes) on my device. Therefore the Android ID cannot be restored/changed by the usual tools (including Titanium Backup).
I have found a way to query/update the settings database via adb though as follows:
Get current Android ID:
Code:
adb shell content query --uri content://settings/secure --where "name=\'android_id\'"
Normally, you would update the value as follows:
Code:
adb shell content update --uri content://settings/secure --bind value:s:<new_android_id> --where "name=\'android_id\'"
However, this wasn't working for me - I kept getting the same ID when querying after update. So, I tried removing the current record and re-inserting it with the new ID:
Code:
adb shell content delete --uri content://settings/secure --where "name=\'android_id\'"
adb shell content insert --uri content://settings/secure --bind name:s:android_id --bind value:s:<new_android_id>
Which worked just fine
Any idea if this works going from CM to Stock or the reverse? Or does it only work stock to stock?
I ask because my two factor auth token for work is on my CM, but if I restore it on stock using Titanium Backup, it works oddly. I wonder if changing the ID would make it work better on stock
Sweet. Any idea how to do this to get the device ID for exchange in gmail?
So were the SETTINGS.DB file gone?
For Windows, exclude escape characters
Simply perfect. I was worried when Titanium Backup couldn't restore old ID, but this worked like a beauty.
The only hitch was that the cmd.exe doesn't need escape characters for apostrophes.
So the code for me was just
Code:
adb shell content delete --uri content://settings/secure --where "name='android_id'"
adb.exe shell content insert --uri content://settings/secure --bind name:s:android_id --bind value:s:<newID>
edit: installing adbwireless and using that solved the problem. not sure why adb from my computer won't work though.
I have the latest SDK installed, have root, and have allowd adb shell root privileges and everytime i run a command I get:
tmp-mksh: adb: not found
Can anyone help me out? I'm using a Nexus 6.
edit: seems like no matter what command i type i get adb : not found. I get a response from the command adb devices when I don't have a shell open. running the abobe commands outside of a shell returns an error, and when i go into a shell no commands work. I always get the adb: not found response.
exactly what I just needed for my nexus 5, worked flawless... thanks a lot!
nyreyn said:
edit: installing adbwireless and using that solved the problem. not sure why adb from my computer won't work though.
I have the latest SDK installed, have root, and have allowd adb shell root privileges and everytime i run a command I get:
tmp-mksh: adb: not found
Can anyone help me out? I'm using a Nexus 6.
edit: seems like no matter what command i type i get adb : not found. I get a response from the command adb devices when I don't have a shell open. running the abobe commands outside of a shell returns an error, and when i go into a shell no commands work. I always get the adb: not found response.
Click to expand...
Click to collapse
Of course! This is a simple problem arising from the absence of the adb.exe executable from the system path being read by your shell or terminal program. You can either add your adb.exe to your system path or else navigate to the platform-tools directory and use the adb.exe from there:
Verify that adb.exe resides in %LOCALAPPDATA%\Android\sdk\platform-tools\
Set the path and restart the cmd or PowerShell and then try again.
I tried doing this, but my adb shell doesn't seem to have content in its sbin.
Nevermind.. it works now.
piit79 said:
I haven't found this posted anywhere so figured it might be useful to others as well.
When you reinstall Android it is set up as a new device with a new unique Android ID. This ID is often used by apps to identify the device - for example all my internet banking apps use it to register the device with the service. To avoid having to re-register after reinstall the ID can be changed to what it was previously.
The Android ID backup/restore function is included in Titanium Backup. However, the Settings Storage (com.android.providers.settings) doesn't seem to be backed by a traditional SQLite database in Android 6.0 Marshmallow - /data/data/com.android.providers.settings/databases/settings.db is empty (0 bytes) on my device. Therefore the Android ID cannot be restored/changed by the usual tools (including Titanium Backup).
I have found a way to query/update the settings database via adb though as follows:
Get current Android ID:
Code:
adb shell content query --uri content://settings/secure --where "name=\'android_id\'"
Normally, you would update the value as follows:
Code:
adb shell content update --uri content://settings/secure --bind value:s:<new_android_id> --where "name=\'android_id\'"
However, this wasn't working for me - I kept getting the same ID when querying after update. So, I tried removing the current record and re-inserting it with the new ID:
Code:
adb shell content delete --uri content://settings/secure --where "name=\'android_id\'"
adb shell content insert --uri content://settings/secure --bind name:s:android_id --bind value:s:<new_android_id>
Which worked just fine
Click to expand...
Click to collapse
Thanks! Thanks! Thanks! Thanks! Thanks! Thanks! Thanks!
Hi,
another way is :
to read Android ID:
Code:
adb shell settings get secure android_id
To write Android ID:
Code:
adb shell settings put secure android_id <new_android_id>
Tested on Android 6.0 Marshmallow.
Thanks! Thanks! Thanks! Thanks! Thanks! Thanks! Thanks!
Any way to get this done without pc access?
IparryU said:
Any way to get this done without pc access?
Click to expand...
Click to collapse
Sure. Just open Terminal Emulator as root and use the same commands as above but without "adb shell":
Code:
su
settings get secure android_id
settings put secure android_id <new_android_id>
I used it in my Nexus 5 (Marshmallow).
I'm already on Marshmallow, so I'm guessing that the "settings get secure android_id" will just tell me my current, new, unwanted android_id. Correct, or am I confused? Is there an easy way to find out what my previous android_id was so that I know what to restore it to? Perhaps Titanium Backup has it squirreled away somewhere?
Or do I need to follow this process?
1. Make nandroid of current Marshmallow setup.
2. Restore nandroid of prior Lollipop setup.
3. From terminal window, "settings get secure android_id" and write down the ID (e.g. "abcdef0123456789")
4. Restore Marshmallow nandroid
5. From terminal window, "settings put secure android_id abcdef0123456789"
There has to be a way to change the device ID for GMail but I haven't figure it out yet. There was an module on Xposed that claimed it could do it but I'm on 6.0 so that doesn't do me any good. Any one have ideas?
Hi!
I am trying adb shell settings but I get:
"/system/bin/sh: /system/bin/settings: /bin/sh: No such file or directory"
In other words the settings command is not found.
Am I missing something?
Thanks for the help!
Crios said:
Hi,
another way is :
to read Android ID:
Code:
adb shell settings get secure android_id
To write Android ID:
Code:
adb shell settings put secure android_id <new_android_id>
Tested on Android 6.0 Marshmallow.
Click to expand...
Click to collapse
MSKS said:
Hi!
I am trying adb shell settings but I get:
"/system/bin/sh: /system/bin/settings: /bin/sh: No such file or directory"
In other words the settings command is not found.
Am I missing something?
Thanks for the help!
Click to expand...
Click to collapse
Seems I'm not watching my own thread! Duh Lots of useful info here.
I was getting the same error message. The /system/bin/settings script is there but it's missing the "shebang" line at the beginning to specify what interpreter to use (e.g. #!/bin/bash). For some reason the system defaults to /bin/sh - which is not there.
You can get around it by running the scripts like so:
Code:
sh /system/bin/settings ...
Hope that helps.
Thanks a lot man! Appreciated.
piit79 said:
Seems I'm not watching my own thread! Duh Lots of useful info here.
I was getting the same error message. The /system/bin/settings script is there but it's missing the "shebang" line at the beginning to specify what interpreter to use (e.g. #!/bin/bash). For some reason the system defaults to /bin/sh - which is not there.
You can get around it by running the scripts like so:
Code:
sh /system/bin/settings ...
Hope that helps.
Click to expand...
Click to collapse
merouleau said:
I'm already on Marshmallow, so I'm guessing that the "settings get secure android_id" will just tell me my current, new, unwanted android_id. Correct, or am I confused? Is there an easy way to find out what my previous android_id was so that I know what to restore it to? Perhaps Titanium Backup has it squirreled away somewhere?
Or do I need to follow this process?
1. Make nandroid of current Marshmallow setup.
2. Restore nandroid of prior Lollipop setup.
3. From terminal window, "settings get secure android_id" and write down the ID (e.g. "abcdef0123456789")
4. Restore Marshmallow nandroid
5. From terminal window, "settings put secure android_id abcdef0123456789"
Click to expand...
Click to collapse
Did you try this and did it turn out? I'm about to do the same thing because it makes sense.
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".