Hi there,
Could anyone help me, please?
adb shell fires up /system/bin/sh witch don't understand [tab] and [up_arrow]
tried this solution:
(in recovery)
cd /system/bin
mv sh sh.bak
ln -s bash sh
it works great, but my favorite ghost commander file manager don't work properly:
Error is:
"FIX ME! implement ttyname()
bionic/libc/bionic/stubs.c:360"
P.S.
I'm using stock ROM from Teppic with optional mods.
Hello
I've followed the hole tutorial from http://forum.xda-developers.com/showthread.php?t=2230250&page=16 but when i try to add the md5sum, i get:
bash: prerooted.tar: permission denied
even when i try to do:
sudo md5sum -t prerooted.tar >> prerooted.tar
What is going wrong and what can i do to make it work????
thanks
?????
got it!!!!
Don't sudo the command but login as root and then run it!!!
This topic can be closed..
The first question I am not sure can be done but if it can I would like to know how. When applying prerooted firmwares in cmw recovery is it possible for it to look on mounted usb storage? I see the usb storage folder but when I click it is always empty so to install new firmware I have to transfer it to the internal sd of the fire tv first.
Secondly there is an option in the adb fire program where it asks if the firmware you want to install is located on a usb storage. Everytime I try to use this feature it can't find the drive or it finds the drive but does not see the firmware I have on it and again I have to transfer it to the unit.
Thanks in advance for the help.
danknasty said:
The first question I am not sure can be done but if it can I would like to know how. When applying prerooted firmwares in cmw recovery is it possible for it to look on mounted usb storage? I see the usb storage folder but when I click it is always empty so to install new firmware I have to transfer it to the internal sd of the fire tv first.
Secondly there is an option in the adb fire program where it asks if the firmware you want to install is located on a usb storage. Everytime I try to use this feature it can't find the drive or it finds the drive but does not see the firmware I have on it and again I have to transfer it to the unit.
Thanks in advance for the help.
Click to expand...
Click to collapse
I'd be interested in knowing more about your issue with adbFire not finding a drive. This is the first report I've seen of that. Regarding firmware installs...From adbFire's Help system:
Install AFTV firmware
Install firmware to AFTV. Upgrade (or downgrade) your AFTV firmware. This works for firmware on a mounted USB drive/stick and for firmware on your PC. When updating firmware from USB storage, adbFire looks on all devices for files with an extension of ".bin" or ".zip" and presents them for your choice.
Installing firmware from a usb stick/drive is nearly twice as fast as installing a firmware file located on your PC or LAN.
Please note that installation of firmware via Amazon's Native Recovery (this method) has been effectively obsoleted with the availibility of ClockworkMod, compiled for the Fire TV by [email protected]
IMPORTANT: Do not attempt to install custom Clockwork Mod firmware via Amazon Native Recovery. It will not work!
Click to expand...
Click to collapse
jocala said:
I'd be interested in knowing more about your issue with adbFire not finding a drive. This is the first report I've seen of that. Regarding firmware installs...From adbFire's Help system:
Click to expand...
Click to collapse
Yes I have tried both .zip and .bin but had no luck. The farthest I have gotten is I mount the drives via adbfirm and it will recognize a drive then tell me there is no firmware on the drive. Could it be the brand of usb stick I am using or does it need to be a powered usb?
danknasty said:
Yes I have tried both .zip and .bin but had no luck. The farthest I have gotten is I mount the drives via adbfirm and it will recognize a drive then tell me there is no firmware on the drive. Could it be the brand of usb stick I am using or does it need to be a powered usb?
Click to expand...
Click to collapse
If the drive is mounted, the linux find command should locate any *.bin or *.zip files, your brand or hub won't have any effect. I'm mainly replying to let you know I've read your post -- I won't have access to my rooted ftv until Monday morning at the earliest. It would also be helpful to see a log captured after you attempt to find firmware on your mounted drive. You should see something in the log like this:
searching usb for files
"./adb" shell su -c find /storage/usb -name *.bin -o -name *.zip
Click to expand...
Click to collapse
Followed by other stuff.
jocala said:
If the drive is mounted, the linux find command should locate any *.bin or *.zip files, your brand or hub won't have any effect. I'm mainly replying to let you know I've read your post -- I won't have access to my rooted ftv until Monday morning at the earliest. It would also be helpful to see a log captured after you attempt to find firmware on your mounted drive. You should see something in the log like this:
Followed by other stuff.
Click to expand...
Click to collapse
How would I go about capturing a log for you. Also just curious about my first question I wasn't sure is it possible to read a mounted usb in the custom recovery menu or must the fire tv be fully booted.
Also.. not sure if this helps but when I mount the usb stick using stick mount on the fire tv it does not give me the error of nothing found but the select firmware menu comes up and this is the only choice I have available "sh: find: not found"
danknasty said:
How would I go about capturing a log for you. Also just curious about my first question I wasn't sure is it possible to read a mounted usb in the custom recovery menu or must the fire tv be fully booted.
Also.. not sure if this helps but when I mount the usb stick using stick mount on the fire tv it does not give me the error of nothing found but the select firmware menu comes up and this is the only choice I have available "sh: find: not found"
Click to expand...
Click to collapse
None of my comments apply when booted to a custom recovery, you need to check with rbox for that.
adbFire logs are found using the File-View Log menu command. The various non-Kodi commands also require my busybox and the various support scripts, aka System Tools; I don't support busybox from other sources. I also ask that you be using the current version of adbFire when seeking support, currently 1.22.
jocala said:
None of my comments apply when booted to a custom recovery, you need to check with rbox for that.
adbFire logs are found using the File-View Log menu command. The various non-Kodi commands also require my busybox and the various support scripts, aka System Tools; I don't support busybox from other sources. I also ask that you be using the current version of adbFire when seeking support, currently 1.22.
Click to expand...
Click to collapse
Ok here is my log I opened it up today and tried to install firmware from usb.
adbFire v1.22
031315120328
Windows
------------
server started
"./adb.exe" start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
starting server
initial open
192.168.0.36
server started
"./adb.exe" start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
connection attempt
"./adb.exe" connect 192.168.0.36:5555
unable to connect to 192.168.0.36:5555:5555
process time duration: 25 seconds
opening preferences dialog
Saving Device Record
updating database adbfire.db
server started
"./adb.exe" start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
connection attempt
"./adb.exe" connect 192.168.0.34:5555
connected to 192.168.0.34:5555
"./adb.exe" shell su -c ps | grep smbd
samba off!
process time duration: 5 seconds
firmware installation query
firmware installation started
"./adb.exe" shell su -c cp /sdcard/command /cache/recovery/
"./adb.exe" shell su -c chmod 777 /cache/recovery/command
searching usb for files
"./adb.exe" shell su -c find /storage/usb -name *.bin -o -name *.zip
sh: find: not found
opening adblog dialog
danknasty said:
"./adb.exe" shell su -c find /storage/usb -name *.bin -o -name *.zip
sh: find: not found
Click to expand...
Click to collapse
The various non-Kodi commands also require my busybox and the various support scripts, aka System Tools; I don't support busybox from other sources.
Click to expand...
Click to collapse
The find command is missing. Install System Tools. This will install busybox as mentioned above, which will give you find.
The Install Firmware command should check for System Tools and warn you if they are missing. That will be fixed in the next update.
jocala said:
The find command is missing. Install System Tools. This will install busybox as mentioned above, which will give you find.
The Install Firmware command should check for System Tools and warn you if they are missing. That will be fixed in the next update.
Click to expand...
Click to collapse
I installed system tools about 3 times as I am on the latest rooted firmware. But I just tried again and now and still no luck this is the log I get now.
opening adblog dialog
starting busybox install
"./adb.exe" push ./busybox /sdcard/
632 KB/s (1356524 bytes in 2.095s)
"./adb.exe" push ./install-recovery-2.sh /sdcard/
8 KB/s (62 bytes in 0.007s)
"./adb.exe" push ./install-recovery.sh /sdcard/
23 KB/s (630 bytes in 0.026s)
"./adb.exe" push ./xbin.tar /sdcard/
795 KB/s (2836480 bytes in 3.480s)
/system mounted rw
"./adb.exe" shell su -c mount -o remount,rw /system
"./adb.exe" shell su -c cp /sdcard/busybox /system/xbin
"./adb.exe" shell su -c chmod 0755 /system/xbin/busybox
"./adb.exe" shell su -c /system/xbin/busybox tar xf /sdcard/xbin.tar -C /system
"./adb.exe" shell su -c chmod 0755 /system/xbin/*.sh
"./adb.exe" shell su -c chmod 0755 /system/xbin/01mntdrives
"./adb.exe" shell su -c chmod 0755 /system/xbin/02sshd
"./adb.exe" shell su -c chmod 0755 /system/xbin/mount.exfat-fuse
"./adb.exe" shell su -c chmod 0755 /system/xbin/ntfs-3g
"./adb.exe" shell su -c /system/xbin/binstall.sh
rm failed for /sdcard/binstall.sh, No such file or directory
rm failed for /sdcard/buninstall.sh, No such file or directory
rm failed for /sdcard/ntfs-3g, No such file or directory
rm failed for /sdcard/mount.exfat-fuse, No such file or directory
rm failed for /sdcard/mntdrives.sh, No such file or directory
mount: Device or resource busy
"./adb.exe" shell ls /system/xbin/which
/system/xbin/which
"./adb.exe" shell su -c rm /sdcard/xbin.tar
"./adb.exe" shell su -c tar xf /sdcard/samba.tar -C /data/data
tar: can't open '/sdcard/samba.tar': No such file or directory
"./adb.exe" shell su -c rm /sdcard/samba.tar
rm failed for /sdcard/samba.tar, No such file or directory
"./adb.exe" shell su -c mkdir /system/etc/init.d
"./adb.exe" shell su -c chmod 777 /system/etc/init.d
"./adb.exe" shell su -c cp /sdcard/install-recovery* /system/etc/
"./adb.exe" shell su -c chmod 0755 /system/etc/install-recovery*
"./adb.exe" shell su -c rm /sdcard/install-recovery*
"./adb.exe" shell su -c cp /system/etc/init.bueller.sh /system/etc/init.bueller.sh.old
"./adb.exe" shell su -c cp /system/xbin/init.bueller.sh /system/etc/
"./adb.exe" shell ls /system/xbin/mntdrives.backup
/system/xbin/mntdrives.backup: No such file or directory
"./adb.exe" shell ls /system/xbin/mntdata.backup
/system/xbin/mntdata.backup: No such file or directory
"./adb.exe" shell ls /system/xbin/mntdata.backup
/system/xbin/mntdata.backup: No such file or directory
busybox installed!
/system mounted ro
"./adb.exe" shell su -c mount -o remount,ro /system
process time duration: 47 seconds
firmware installation query
firmware installation started
"./adb.exe" shell su -c cp /sdcard/command /cache/recovery/
"./adb.exe" shell su -c chmod 777 /cache/recovery/command
searching usb for files
"./adb.exe" shell su -c find /storage/usb -name *.bin -o -name *.zip
no files found
"./adb.exe" shell su -c /system/xbin/mntdrives.sh
USB drive(s) mounted
"./adb.exe" shell su -c /system/xbin/mntdrives.sh
"./adb.exe" shell su -c /data/data/com.funkyfresh.samba/files/samba-rc start
sh: /data/data/com.funkyfresh.samba/files/samba-rc: not found
"./adb.exe" shell su -c ps | grep smbd
samba off!
firmware installation query
firmware installation started
"./adb.exe" shell su -c cp /sdcard/command /cache/recovery/
"./adb.exe" shell su -c chmod 777 /cache/recovery/command
searching usb for files
"./adb.exe" shell su -c find /storage/usb -name *.bin -o -name *.zip
no files found
opening adblog dialog
searching usb for files
"./adb.exe" shell su -c find /storage/usb -name *.bin -o -name *.zip
no files found
Click to expand...
Click to collapse
I just noticed you're not using adbFire to mount your drive; I can't support stickmount, sorry. If you can change your mount location to be under /storage/usb it might work, idk. I know it does work with System Tools installed and adbFire mounting the usb drives.
I used adb Fire to mount my drive originally and it gives me the message that no firmwares are on the drive. Here is a log of me mounting in adb fire succesfully but then it unable to find the file.
"./adb.exe" shell su -c rm -r /storage/usb/*/
usb drive unmounted
"./adb.exe" shell su -c mount -o remount,ro /
/ mounted ro
"./adb.exe" shell su -c mount -o remount,ro /
process time duration: 2 seconds
"./adb.exe" shell su -c /system/xbin/mntdrives.sh
USB drive(s) mounted
"./adb.exe" shell su -c /system/xbin/mntdrives.sh
"./adb.exe" shell su -c /data/data/com.funkyfresh.samba/files/samba-rc start
sh: /data/data/com.funkyfresh.samba/files/samba-rc: not found
"./adb.exe" shell su -c ps | grep smbd
samba off!
firmware installation query
firmware installation started
"./adb.exe" shell su -c cp /sdcard/command /cache/recovery/
"./adb.exe" shell su -c chmod 777 /cache/recovery/command
searching usb for files
"./adb.exe" shell su -c find /storage/usb -name *.bin -o -name *.zip
no files found
opening adblog dialog
danknasty said:
I used adb Fire to mount my drive originally and it gives me the message that no firmwares are on the drive.
Click to expand...
Click to collapse
Sorry, I can't duplicate your error on a clean system, with System Tools installed , multiple drives mounted with firmware sitting on each, just for purposes of testing. All firmwares were found, every time. The find command is pretty straightforward.
You may have some weird edge case I've overlooked in code, but I'd need to see a log from a clean system w/o third-party busybox, mount tools, etc. If we can spotlight a bug, I'd be happy to fix it.
jocala said:
Sorry, I can't duplicate your error on a clean system, with System Tools installed , multiple drives mounted with firmware sitting on each, just for purposes of testing. All firmwares were found, every time. The find command is pretty straightforward.
You may have some weird edge case I've overlooked in code, but I'd need to see a log from a clean system w/o third-party busybox, mount tools, etc. If we can spotlight a bug, I'd be happy to fix it.
Click to expand...
Click to collapse
I tried this when i first unboxed the unit and was unable to get it to read anything could it be the way I have the usb stick formatted or the way the zip file is named?
danknasty said:
I tried this when i first unboxed the unit and was unable to get it to read anything could it be the way I have the usb stick formatted or the way the zip file is named?
Click to expand...
Click to collapse
adbFire drive mount supports vfat,ex-fat,ext2-4,hpfs+ and ntfs. Install Firmware will find files with embedded spaces ,e.g. "test file.zip" or "test file.bin" but not "test file zip" or "test file bin".
jocala said:
adbFire drive mount supports vfat,ex-fat,ext2-4,hpfs+ and ntfs. Install Firmware will find files with embedded spaces ,e.g. "test file.zip" or "test file.bin" but not "test file zip" or "test file bin".
Click to expand...
Click to collapse
my stick is a fat32 and the files is named update.zip so it should work?... The weird thing is it seems to get farther when I mount it using stick mount (it brings up a menu) then it does when I mount in adb fire although I have yet to get either method to work. I am gonna restore one a little later and do everything from adbfire and see if I can get you a log or mabye it will work.
Ok so I started from scratch and I am having the same issue here is the log.. I notice it saying the mount is busy I am not sure what that means.... I also installed es file explorer and I do not see the mounted usb storage anywhere on the sdcard even after it says it has mounted succesfully.
adbFire v1.22
031315181935
Windows
------------
server started
"./adb.exe" start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
starting server
initial open
192.168.0.34
server started
"./adb.exe" start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
connection attempt
"./adb.exe" connect 192.168.0.34:5555
unable to connect to 192.168.0.34:5555:5555
process time duration: 25 seconds
opening preferences dialog
Saving Device Record
updating database adbfire.db
server started
"./adb.exe" start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
connection attempt
"./adb.exe" connect 192.168.0.38:5555
connected to 192.168.0.38:5555
process time duration: 5 seconds
"./adb.exe" install -r ./tr.apk
pkg: /data/local/tmp/tr.apk
Success
573 KB/s (111652 bytes in 0.190s)
"./adb.exe" install -r ./su.apk
pkg: /data/local/tmp/su.apk
Success
558 KB/s (2336291 bytes in 4.082s)
Root software installed.
Run towelroot on the FireTV
to finish rooting process.
process time duration: 25 seconds
opening preferences dialog
Saving Device Record
updating database adbfire.db
Amazon update state toggled
amazon updates
"./adb.exe" shell su -c pm disable com.amazon.dcp
Package com.amazon.dcp new state: disabled
Amazon updates off, com.amazon.dcp disabled
"./adb.exe" shell pm list packages -d
package:com.amazon.dcp
starting busybox install
"./adb.exe" push ./busybox /sdcard/
702 KB/s (1356524 bytes in 1.885s)
"./adb.exe" push ./install-recovery-2.sh /sdcard/
6 KB/s (62 bytes in 0.009s)
"./adb.exe" push ./install-recovery.sh /sdcard/
30 KB/s (630 bytes in 0.020s)
"./adb.exe" push ./xbin.tar /sdcard/
689 KB/s (2836480 bytes in 4.018s)
/system mounted rw
"./adb.exe" shell su -c mount -o remount,rw /system
"./adb.exe" shell su -c cp /sdcard/busybox /system/xbin
"./adb.exe" shell su -c chmod 0755 /system/xbin/busybox
"./adb.exe" shell su -c /system/xbin/busybox tar xf /sdcard/xbin.tar -C /system
"./adb.exe" shell su -c chmod 0755 /system/xbin/*.sh
"./adb.exe" shell su -c chmod 0755 /system/xbin/01mntdrives
"./adb.exe" shell su -c chmod 0755 /system/xbin/02sshd
"./adb.exe" shell su -c chmod 0755 /system/xbin/mount.exfat-fuse
"./adb.exe" shell su -c chmod 0755 /system/xbin/ntfs-3g
"./adb.exe" shell su -c /system/xbin/binstall.sh
rm failed for /sdcard/binstall.sh, No such file or directory
rm failed for /sdcard/buninstall.sh, No such file or directory
rm failed for /sdcard/ntfs-3g, No such file or directory
rm failed for /sdcard/mount.exfat-fuse, No such file or directory
rm failed for /sdcard/mntdrives.sh, No such file or directory
mount: Device or resource busy
"./adb.exe" shell ls /system/xbin/which
/system/xbin/which
"./adb.exe" shell su -c rm /sdcard/xbin.tar
"./adb.exe" shell su -c tar xf /sdcard/samba.tar -C /data/data
tar: can't open '/sdcard/samba.tar': No such file or directory
"./adb.exe" shell su -c rm /sdcard/samba.tar
rm failed for /sdcard/samba.tar, No such file or directory
"./adb.exe" shell su -c mkdir /system/etc/init.d
"./adb.exe" shell su -c chmod 777 /system/etc/init.d
"./adb.exe" shell su -c cp /sdcard/install-recovery* /system/etc/
"./adb.exe" shell su -c chmod 0755 /system/etc/install-recovery*
"./adb.exe" shell su -c rm /sdcard/install-recovery*
"./adb.exe" shell su -c cp /system/etc/init.bueller.sh /system/etc/init.bueller.sh.old
"./adb.exe" shell su -c cp /system/xbin/init.bueller.sh /system/etc/
"./adb.exe" shell ls /system/xbin/mntdrives.backup
/system/xbin/mntdrives.backup: No such file or directory
"./adb.exe" shell ls /system/xbin/mntdata.backup
/system/xbin/mntdata.backup: No such file or directory
"./adb.exe" shell ls /system/xbin/mntdata.backup
/system/xbin/mntdata.backup: No such file or directory
busybox installed!
/system mounted ro
"./adb.exe" shell su -c mount -o remount,ro /system
process time duration: 29 seconds
"./adb.exe" shell su -c /system/xbin/mntdrives.sh
USB drive(s) mounted
"./adb.exe" shell su -c /system/xbin/mntdrives.sh
"./adb.exe" shell su -c /data/data/com.funkyfresh.samba/files/samba-rc start
sh: /data/data/com.funkyfresh.samba/files/samba-rc: not found
"./adb.exe" shell su -c ps | grep smbd
samba off!
stock recovery installation starts
recovery installation started
pushing C:/Users/1/Desktop/adbfw122/adbfw122/stkrecovery/recovery-stock-51.1.0.img to /sdcard/
"./adb.exe" push "C:/Users/1/Desktop/adbfw122/adbfw122/stkrecovery/recovery-stock-51.1.0.img" /sdcard/recovery.img
594 KB/s (10485760 bytes in 17.223s)
"./adb.exe" shell su -c dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
20480+0 records in
20480+0 records out
10485760 bytes transferred in 1.556 secs (6738920 bytes/sec)
"./adb.exe" shell rm /sdcard/recovery.img
process time duration: 29 seconds
firmware installation query
firmware installation started
"./adb.exe" shell su -c chmod 777 /cache/recovery
Unable to open /cache/recovery: No such file or directory
/cache/recovery/ not found
"./adb.exe" shell su -c mkdir -p /cache/recovery/
"./adb.exe" shell su -c chmod 777 /cache/recovery
"./adb.exe" shell su -c cp /sdcard/command /cache/recovery/
"./adb.exe" shell su -c chmod 777 /cache/recovery/command
searching usb for files
"./adb.exe" shell su -c find /storage/usb -name *.bin -o -name *.zip
no files found
opening adblog dialog
Hi there,
I'm having some difficulties in running some commands in userinit.sh due to SELinux.
system/etc/init.d/90userinit is invoking userinit.sh in /data/local/.
First they were blocked by SELinux. After running
Code:
chcon u:object_r:userinit_exec:s0 /system/etc/init.d/90userinit
chcon u:object_r:userinit_data_exec:s0 /data/local/userinit.sh
in Terminal, userinit.sh with the following content e.g.
Code:
#!/system/bin/sh
log -p i -t userinit "userinit start";
sysctl -w net.ipv6.conf.default.use_tempaddr=2
sysctl -w net.ipv6.conf.all.use_tempaddr=2
log -p i -t userinit "userinit end";
was executed, but sysctl -call within userinit.sh is blocked.
logcat:
Code:
avc: denied { net_admin } for pid=229 comm="sysctl" capability=12 scontext=u:r:sysinit:s0 tcontext=u:r:sysinit:s0 tclass=capability permissive=0
...
Q1: How do i properly set permissinons for sysctl now?
Q2: Is there a way to set proper permissions for all commands given in userinit.sh in generall?