Database Users

Installing Debian on the HTC TATTOO / CLICK

i read here
http://android-dls.com/wiki/index.php?title=Installing_Debian
you can run debian on android whit installing it.
and dont loos your droid
first isseu i got. chmodding the thing
download and push debian to /sdcard/debian
Code:
cd /sdcard/debian
su
chmod 4755 *
Code:
# su
su
su: access granted, courtesy of www.magicandroidapps.com
# chmod 4755 /sdcard/debian/*
chmod 4755 /sdcard/debian/*
Unable to chmod /sdcard/debian/bootdeb: Operation not permitted
#
than whitout bootdeb is chmodded i tried the installer.sh
Code:
cd /sdcard/debian as root
sh ./installer.sh
it just say's
Code:
# sh ./installer.sh
sh ./installer.sh
su: access granted, courtesy of www.magicandroidapps.com
#
so ?
Code:
# exit
Code:
# exit
exit
modprobe: not found
clear: not found
rm failed for -f, No such file or directory
rm failed for -f, No such file or directory
rm failed for -f, No such file or directory
rm failed for -f, No such file or directory
rm failed for -f, No such file or directory
mkdir failed for /data/local/mnt, File exists
clear: not found
cp: not found
cp: not found
cp: not found
cp: not found
cp: not found
Unable to chmod bootdeb: Operation not permitted
clear: not found
VERSION 2.1
Custom Debian Bootloader is now installed! Quick huh?
This process does NO damage to your Android underlying OS!
Courtesy of http://www.androidfanatic.com
Installer by Mark Walker (ghostwalker)
To enter the Debian Linux console just type 'bootdeb'
PS: Be sure to run /scripts/onetime.sh as root from the shell after your FIRST
boot'.
??
Code:
# rm
rm
rm [-rR] <target>
availible
Code:
cp: not found
not availible.. Busybox availible only cp but the debian installer does not support the busybox way.
Code:
# busybox cp
busybox cp
BusyBox v1.8.1 (2007-11-14 10:11:37 EST) multi-call binary
Usage: cp [OPTION]... SOURCE DEST
enz.
Code:
#modprobe
not found
Code:
# busybox modprobe -h
busybox modprobe -h
modprobe: invalid option -- h
BusyBox v1.8.1 (2007-11-14 10:11:37 EST) multi-call bin
Usage: modprobe [-knqrsv] MODULE [symbol=value ...]
what to do to get this running?

Troubleshooting
Troubleshooting
If chmod 4755 * gives you an error stating that you do not have permissions, close Terminal Emulator and run su again, this time when SuperUserWhitelist asks for if you should give Terminal Emulator super user permissions hit yes instead of always.
If running installer.sh tells you that installer.sh could not be found, type su, followed by sh installer.sh
what whitelist?

I'm getting the same errors as u are. I belive the whitelist sugestion is only for those who have the app installed. The problem must lie somewhere else.

Have you done my busybox install (somewhere in this forum)? Looks like if you use stock ultities you don't have requirements...

bootdev.sh
keatonreckard said:
or you can simply rename the attached bootdev.sh.txt to bootdev.sh and put it in your debian folder and its good as new
Click to expand...
Click to collapse
these posts or were is that installer??

Yah I did have busybox installed.

superuser.apk
http://androidforums.com/all-things-root-behold-2/46137-how-root-apps-working-persistent-root.html
i think this is that superuser whitlist

I have fixed the bootdeb file, but im stuck at mounting the debian image...

Did anyone make any new progress on getting debian to work?

lgstoian said:
Did anyone make any new progress on getting debian to work?
Click to expand...
Click to collapse
I haven't made much progress...
But with Fyodor's 0.4.1 ROM modprobe works but i get this error when mounting the debian image:
ioctl: LOOP_SET_FD: Device or resource busy
Click to expand...
Click to collapse
And after that the rest ****s up...

Who can write a tutorial of Debian on TATTOO?

[Q] installing backtrack 5 with androidVNC

I am currently trying to install bt5 using the instructions I found here on xda.
I have successfully rooted the a500 tablet (or at least ever check I can perform says so)
I have busybox installed from the market
I have supersu (after starting with superuser)
I have ES File explorer and can even go root R/w with it
but when performing the steps in the aforementioned tutorial this is what happens
Code:
[email protected]:/ $ su
[email protected]:/ # cd sdcard/bt5
[email protected]:/sdcard/bt5 # sh bootbt
mount: permission denied (are you root?)
Loop device exists
mount: mounting devpts on /data/local/mnt/dev/pts failed: Input/output error
mount: mounting sysfs on /data/local/mnt/sys failed: Input/output error
net.ipv4.ip_forward = 1
chroot: can't execute '/bin/bash': Input/output error
Shutting down BackTrack ARM For Xoom
failed: I/O error
failed: I/O error
is there somthing I am not catching here, something I should be looking for

Strace and debugging commands help

I've like to know more in general about how to run strace and debug errors in the general.
Specifically, my device was having issues and I saw errors like these in the logs.
Code:
2016-03-15 02:46:37,ERROR,QC-QMI,com.android.sdm.plugins.diagmon,linux_qmi_qmux _io_wake_unlock: Err in writing wakelock=qmuxd_port_wl_0, error [1: eek: operation not permitted]
I flashed factory images for mhc19i. With my only mods being twrp 3.0.0.1 and su 2.67, I'm seeing a lot of these qmuxd errors.
Code:
03-26 17:37:09.597 512 512 E QC-QMI : qmuxd: RX on fd=16 returned error=0 errno[2:No such file or directory]
03-26 17:37:09.598 512 512 E QC-QMI : QMUX qmux_client_id=4a not found in qmux client list, unable to remove
I'm really curious what is going on with this and I'd like to learn how to dig deeper. I tried running strace on the pid, but it wouldn't find a process using the number from logcat and qmuxd wasn't listed when I ran ps. I tried stop stopping ril-daemon and qmuxd and using strace to run qmuxd as directed in an old post.
Code:
1|[email protected]:/ $ strace -ff -v -o /sdcard/straceqmuxd -s 256 /system/bin/qmuxd
strace: Can't stat '/system/bin/qmuxd': Permission denied
1|[email protected]:/ $ su strace -ff -v -o /sdcard/straceqmuxd -s 256 /system/bin/qmuxd
sush: sush: - : unknown option
Can anyone point out where I'm going wrong or where I can learn how to troubleshoot these things?

SuperSU not autostarting

Hello, I hope someone has seen this before. I am not sure how I managed to break S7, as it was working, initially. I am running PE1 firmware, and factory reset before following the root guide, in the verizon guide forums. But now I have the problem where supersu will not auto start on bootup. I have to connect the usb cable to my pc, and use adb and manually start it. Root and Supersu are loaded. The only thing I have to run is:
C:\adb\adb.exe shell /system/etc/launch_daemonsu.sh
Then disconnect the usb cable, and all is well. Everything seems to be correct. What am I missing? I really do not want to start completely over. I have run the verizon debloat v2 and v8. I had to manually start supersu to flashfire the v8 script. Also in the same guide. All the root checker apps will see that you have root, but they say you are missing a super user app.
C:\adb\adb.exe shell /system/etc/launch_daemonsu.sh
mkdir: '/su': File exists
cp: /cache/stock_boot_*: No such file or directory
cp: bad '/cache/stock_boot_*': No such file or directory
/data/su.img: recovering journal
ext2fs_close2 : fs->write_bitmaps is null
ext2fs_close2 : normal operation, return 0
skipping journal recoverybecause INCOMPAT_RECOVER was clear.
check whether gdt & bitmap free count is vaild
/data/su.img: clean, 25/2048 files, 1399/8192 blocks
ext2fs_close2 : fs->write_bitmaps is null
ext2fs_close2 : normal operation, return 0
mount: No such file or directory
mount: No such file or directory
supolicy v2.74 (ndk:arm64-v8a) - Copyright (C) 2014-2016 - Chainfire
Patching policy ...
(Android M policy compatibility mode)
- Success
<Then disconnect the usb cable, supersu will work fine now.>
C:\adb>adb shell cat /system/etc/init.sec.boot.sh
#!/system/bin/sh
echo "init.sec.boot.sh: start" > /dev/kmsg
# start deferred initcalls
cat /proc/deferred_initcalls
## strace for system_server
#str=""
#while [ "$str" = "" ]; do
# str=`ps | grep system_server`
# sleep 0.1
#done
#
#pid=${str:10:4}
#echo "init.sec.boot.sh: strace -tt -T -o /data/log/strace.txt -p ${pid}" > /dev/kmsg
#strace -tt -T -o /data/log/strace.txt -p ${pid}
/system/etc/launch_daemonsu.sh
/data/s7startup/startupscript.sh
C:\adb>adb shell ls -la /system/etc/launch_daemonsu.sh
-rwx------ root root 4686 2016-07-03 13:32 launch_daemonsu.sh
Thanks again.

Did you push the supersu app to you device?

Is that to say uve got supersu installed but it won't start? If that's so I would check the box for start supersu during bootup. Unless im just completely missing your issue and im sorry if I am.

Dumpsys command not working?

Hey all,
Recently I found out that the dumpsys command isn't working anymore. I can't delete the battery stats with command: dumpsys batterystats--reset. I'm getting an unknown error. I'm on 7.1.2 may patch with magisk installed. The command still works on my n5 running darkrom 7.1.2 with may patch and magisk installed. Any clue how to fix this?
Thanks in advance!

This is the exact error in the terminal:
angler:/ $ su
angler:/ # dumpsys batterystats --reset
Error dumping service info: (Unknown error -2147483646) batterystatsangler:/ #

swa100 said:
This is the exact error in the terminal:
angler:/ $ su
angler:/ # dumpsys batterystats --reset
Error dumping service info: (Unknown error -2147483646) batterystatsangler:/ #
Click to expand...
Click to collapse
Hi I have the same exact issue. Have you managed to find the root cause and fix?