Database Info

external sdcard wont mount

Ok guys I know I'm behind the times, but I'm running Tiamat 3.2 (Xoom of course).
Suddenly my external sd card isnt mounting. I has previously mounted.
Firing up adb and looking at dmesg, I see the following:
mmcblk0: 14.9 Gb <---Which should be external sdcard
mmcblk1: 29.7 Gb <---Internal sdcard
mount only shows the following:
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/sdhci-tegra.3/by-name/system /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/block/platform/sdhci-tegra.3/by-name/userdata /data ext4 rw,relatime,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/platform/sdhci-tegra.3/by-name/cache /cache ext4 rw,nosuid,nodev,noatime,nodiratime,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/platform/sdhci-tegra.3/by-name/pdsb /pds ext2 ro,noatime,nodiratime,barrier=1,data=writeback 0 0
/dev/fuse /mnt/sdcard fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
I'm also finding this on searching dmesg:
sh-4.1# dmesg | grep mmc
dmesg | grep mmc
<5>[ 0.000000] Kernel command line: [email protected] [email protected]
00 video=tegrafb [email protected] console=ttyS0,115200n8 usbcore.old_scheme_fi
rst=1 tegraboot=sdmmc gpt gpt_sector=0x03b6efff mot_prod=1 androidboot.serialno=
170061c241615357 hw_rev=p3 androidboot.modelno=MZ604 product_type=w lp0_vec=8192
@0x1e7f1020 androidboot.bootloader=1045 androidboot.carrier=wifi-only lcd_manfid
=AUO mem_vid=0x101 mem_pid=0x5454 androidboot.carrier=wifi-only product_type=w
<4>[ 12.376571] mmc0: Invalid maximum block size, assuming 512 bytes
<6>[ 12.376592] mmc0: no vmmc regulator found
<7>[ 12.376680] Registered led device: mmc0::
<6>[ 12.376763] mmc0: SDHCI controller on tegra [sdhci-tegra.1] using ADMA
<4>[ 12.376835] mmc1: Invalid maximum block size, assuming 512 bytes
<6>[ 12.376856] mmc1: no vmmc regulator found
<7>[ 12.376943] Registered led device: mmc1::
<6>[ 12.377030] mmc1: SDHCI controller on tegra [sdhci-tegra.2] using ADMA
<4>[ 12.377141] mmc2: Invalid maximum block size, assuming 512 bytes
<6>[ 12.377158] mmc2: no vmmc regulator found
<7>[ 12.377243] Registered led device: mmc2::
<6>[ 12.377340] mmc2: SDHCI controller on tegra [sdhci-tegra.3] using ADMA
<6>[ 12.518127] mmc1: new high speed SDHC card at address b368
<6>[ 12.518364] mmcblk0: mmc1:b368 H1510 14.9 GiB
<6>[ 12.521455] mmcblk0: p1
<6>[ 12.620506] mmc2: new high speed MMC card at address 0001
<6>[ 12.620792] mmcblk1: mmc2:0001 SEM32G 29.7 GiB
<6>[ 12.627027] mmcblk1: p1 (ebb) p2 (pdsb) p3 (misc) p4 (logo.bin) p5 (kpani
c) p6 (recovery) p7 (boot) p8 (system) p9 (cache) p10 (userdata)
<6>[ 12.718736] EXT4-fs (mmcblk1p8): mounted filesystem with ordered data mode
. Opts: (null)
<7>[ 15.302617] EXT4-fs (mmcblk1p10): ext4_orphan_cleanup: deleting unreferenc
ed inode 5570874
<7>[ 15.302724] EXT4-fs (mmcblk1p10): ext4_orphan_cleanup: deleting unreferenc
ed inode 5570873
<7>[ 15.302760] EXT4-fs (mmcblk1p10): ext4_orphan_cleanup: deleting unreferenc
ed inode 5570851
<6>[ 15.302792] EXT4-fs (mmcblk1p10): 3 orphan inodes deleted
<6>[ 15.302805] EXT4-fs (mmcblk1p10): recovery complete
<6>[ 15.313298] EXT4-fs (mmcblk1p10): mounted filesystem with ordered data mod
e. Opts: noauto_da_alloc
<6>[ 20.318570] EXT4-fs (mmcblk1p9): recovery complete
<6>[ 20.319437] EXT4-fs (mmcblk1p9): mounted filesystem with ordered data mode
. Opts: noauto_da_alloc
<6>[ 20.324635] EXT4-fs (mmcblk1p2): mounted filesystem without journal. Opts:
(null)
<6>[ 42.616835] EXT4-fs (mmcblk1p8): re-mounted. Opts: (null)
<6>[ 45.213691] EXT4-fs (mmcblk1p8): re-mounted. Opts: (null)
<6>[ 45.215912] EXT4-fs (mmcblk1p10): re-mounted. Opts: (null)
<6>[ 46.020452] EXT4-fs (mmcblk1p8): re-mounted. Opts: (null)
<6>[ 46.054467] EXT4-fs (mmcblk1p8): re-mounted. Opts: (null)
<6>[ 46.085089] EXT4-fs (mmcblk1p8): re-mounted. Opts: (null)
<4>[ 119.330601] mmc0: queuing unknown CIS tuple 0x91 (3 bytes)
<6>[ 119.330686] mmc0: new high speed SDIO card at address 0001
<3>[ 125.914203] FAT: Filesystem error (dev mmcblk0p1)
<3>[ 1660.225502] FAT: Filesystem error (dev mmcblk0p1)
<3>[ 1665.431378] FAT: Filesystem error (dev mmcblk0p1)
<3>[ 1673.260399] FAT: Filesystem error (dev mmcblk0p1)
Obviously there is a Filesystem error on the device. What do I do to rectify the error?
I've tried to mount manually but this is what I get:
sh-4.1# mount -t vfat -o fmask=0000,dmask=0000,rw /dev/block/platform/sdhci-tegra.2/mmcblk0p1 /mnt/external1
<v/block/platform/sdhci-tegra.2/mmcblk0p1 /mnt/external1
mount: I/O error

Really, why don't you upgrade? I think you will be much happier. An upgrade to an EOS ICS build will probably fix your sd mounting problem, unless, of course, the sd card is bad or not seated properly.

[Q] Complete Linux Installer :: notePro 12.2

Hello everyone, first time poster but longer time lurker
Last week I treated myself with the new NotePro 12.2 tablet after dreaming what might cn be done with it once it runs a complete desktop :fingers-crossed:
Since last saturday I have been trying to no availe to get ubuntu running and about to go crazy with the amount of failed attempts.
My hopes are on the Complete Linux Installer as it is being actively developed but I ran into a weird issue with permissions when running the boot script.
I would post in the developer thread, but as a new user I will have to do it here (original thread http://forum.xda-developers.com/showthread.php?t=1585009 )
On with the info:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Device: Galaxy NotePro 12.2 (SM-P900)
Android 4.4.2
Kernel: 3.4.39-433754
Rooted
SuperSu Pro: passed root
Busybox Pro: passed root
Complete Linux Installer + key (ofcourse!)
Linux version: Ubuntu 13.10 Large
The issue:
When executing the bootscript.sh the error "operation is not permitted"
Code:
Checking loop device... MISSING
Creating loop device... mknod: /dev/block/loop255: Operation not permitted
Command: /system/xbin/busybox mknod /dev/block/loop255 b 7 255
FAILED
Error: Unable to create loop device!
Doing my homework for few hours and seeing more people have had this problem, but after some head scratching I simply tried the command manually to see if I am going crazy or not:
Code:
/system/xbin/busybox mknod /dev/block/loop255 b 7 255
v/block/ |grep loop <
brw------- root root 7, 0 2014-04-02 19:20 loop0
brw------- root root 7, 1 2014-04-02 19:20 loop1
brw------- root root 7, 2 2014-04-02 19:20 loop2
brw------- root root 7, 255 2014-04-02 19:59 loop255
brw------- root root 7, 3 2014-04-02 19:24 loop3
brw------- root root 7, 4 2014-04-02 19:20 loop4
brw------- root root 7, 5 2014-04-02 19:20 loop5
brw------- root root 7, 6 2014-04-02 19:20 loop6
brw------- root root 7, 7 2014-04-02 19:20 loop7
Success! :victory:
Launch the app for a retry:
Code:
Checking loop device... FOUND
Command: /system/xbin/busybox losetup /dev/block/loop255 /sdcard/ubuntu/ubuntu.img
mount: mounting /dev/block/loop255 on /data/local/mnt failed: Permission denied
So I keep getting permission denied error one after the other, but when I execute the commands directly in the terminal it`s all fine and dandy and the only thing that doesn`t show anything is when I try to chroot.
With a little bit of linux knowledge I dived into the bootscript and started to look where something goes wrong, I even downloaded 2 different scripts but none made a difference.
Code:
Checking loop device... FOUND
Command: /system/xbin/busybox losetup /dev/block/loop255 /sdcard/ubuntu/ubuntu.img
mount: mounting /dev/block/loop255 on /data/local/mnt failed: Permission denied
Command: /system/xbin/busybox mount -t ext4 /dev/block/loop255 /data/local/mnt
mount: mounting devpts on /data/local/mnt/dev/pts failed: No such file or directory
Command: /system/xbin/busybox mount -t devpts devpts /data/local/mnt/dev/pts
mount: mounting proc on /data/local/mnt/proc failed: No such file or directory
Command: /system/xbin/busybox mount -t proc proc /data/local/mnt/proc
mount: mounting sysfs on /data/local/mnt/sys failed: No such file or directory
Command: /system/xbin/busybox mount -t sysfs sysfs /data/local/mnt/sys
mount: mounting /sdcard on /data/local/mnt/sdcard failed: No such file or directory
Command: /system/xbin/busybox mount -o bind /sdcard /data/local/mnt/sdcard
mkdir failed for /data/local/mnt/root/cfg, No such file or directory
mount: mounting /sdcard/ubuntu on /data/local/mnt/root/cfg failed: No such file or directory
Command: /system/xbin/busybox mount -o bind /sdcard/ubuntu /data/local/mnt/root/cfg
mount: mounting /sys/fs/selinux on /data/local/mnt/selinux failed: No such file or directory
Command: /system/xbin/busybox mount -o bind /sys/fs/selinux /data/local/mnt/selinux
mount: mounting /storage on /data/local/mnt/external_sd failed: No such file or directory
No user defined mount points
net.ipv4.ip_forward = 1
bootscript.sh[234]: can't create /data/local/mnt/etc/resolv.conf: No such file or directory
Error: Unable to write resolv.conf file!
Having all commands echo`d in the terminal made the manual work abit easier:
Code:
/xbin/busybox losetup /dev/block/loop255 /sdcard/ubuntu/ubuntu.img <
xbin/busybox mount -t ext4 /dev/block/loop255 /data/local/mnt <
/xbin/busybox mount -t devpts devpts /data/local/mnt/dev/pts <
xbin/busybox mount -t proc proc /data/local/mnt/proc <
xbin/busybox mount -t sysfs sysfs /data/local/mnt/sys <
xbin/busybox mount -o bind /sdcard /data/local/mnt/sdcard <
xbin/busybox mount -o bind /sdcard/ubuntu /data/local/mnt/root/cfg <
xbin/busybox mount -o bind /sys/fs/selinux /data/local/mnt/selinux <
meserver 8.8.4.4" >> $mnt/etc/resolv.conf <
tmp-mksh: can't create /etc/resolv.conf: Read-only file system
27.0.0.1 localhost" > $mnt/etc/hosts <
tmp-mksh: can't create /etc/hosts: Read-only file system
Code:
ls -la /data/local/mnt/
al/mnt/ <
drwxr-xr-x root root 2013-10-09 12:19 android
drwxr-xr-x root root 2013-10-23 04:45 bin
drwxr-xr-x root root 2013-04-25 18:08 boot
drwxr-xr-x root root 2013-10-09 12:01 dev
drwxr-xr-x root root 2013-10-23 04:46 etc
drwxr-xr-x root root 2013-10-10 14:03 external_sd
drwxr-xr-x root root 2013-10-09 12:18 home
drwxr-xr-x root root 2013-10-10 18:35 lib
drwx------ root root 2013-10-09 11:51 lost+found
drwxr-xr-x root root 2013-10-09 11:54 media
drwxr-xr-x root root 2013-04-25 18:08 mnt
drwxr-xr-x root root 2013-10-09 11:54 opt
dr-xr-xr-x root root 1970-01-01 01:00 proc
drwx------ root root 2013-10-23 04:55 root
drwxr-xr-x root root 2013-10-23 04:55 run
drwxr-xr-x root root 2013-10-23 04:45 sbin
drwxrwx--x root sdcard_r 2014-04-01 19:49 sdcard
drwxr-xr-x root root 1970-01-01 01:00 selinux
drwxr-xr-x root root 2013-10-09 11:54 srv
dr-xr-xr-x root root 2014-04-02 19:20 sys
drwxrwxrwt root root 2013-10-23 04:55 tmp
drwxr-xr-x root root 2013-10-09 11:54 usr
drwxr-xr-x root root 2013-10-09 11:54 var
Looks very familiar :fingers-crossed:
Code:
Checking loop device... FOUND
Command: /system/xbin/busybox losetup /dev/block/loop255 /sdcard/ubuntu/ubuntu.img
mount: mounting /dev/block/loop255 on /data/local/mnt failed: Permission denied
Command: /system/xbin/busybox mount -t ext4 /dev/block/loop255 /data/local/mnt
mount: mounting devpts on /data/local/mnt/dev/pts failed: Permission denied
Command: /system/xbin/busybox mount -t devpts devpts /data/local/mnt/dev/pts
mount: mounting proc on /data/local/mnt/proc failed: Permission denied
Command: /system/xbin/busybox mount -t proc proc /data/local/mnt/proc
mount: mounting sysfs on /data/local/mnt/sys failed: Permission denied
Command: /system/xbin/busybox mount -t sysfs sysfs /data/local/mnt/sys
mount: mounting /sdcard on /data/local/mnt/sdcard failed: Permission denied
Command: /system/xbin/busybox mount -o bind /sdcard /data/local/mnt/sdcard
mount: mounting /sdcard/ubuntu on /data/local/mnt/root/cfg failed: Permission denied
Command: /system/xbin/busybox mount -o bind /sdcard/ubuntu /data/local/mnt/root/cfg
mount: mounting /sys/fs/selinux on /data/local/mnt/selinux failed: Permission denied
Command: /system/xbin/busybox mount -o bind /sys/fs/selinux /data/local/mnt/selinux
mount: mounting /storage on /data/local/mnt/external_sd failed: Permission denied
No user defined mount points
net.ipv4.ip_forward = 1
bootscript.sh[231]: can't create /data/local/mnt/etc/resolv.conf: Permission denied
bootscript.sh[232]: can't create /data/local/mnt/etc/hosts: Permission denied
chroot: can't change root directory to '/data/local/mnt': Operation not permitted
Command: /system/xbin/busybox chroot /data/local/mnt /root/init.sh ubuntu.img
Shutting down Linux ARM
umount: can't umount /data/local/mnt/root/cfg: Permission denied
umount: can't umount /data/local/mnt/sdcard: Permission denied
umount: can't umount /data/local/mnt/external_sd: Invalid argument
umount: can't umount /data/local/mnt/dev/pts: Permission denied
umount: can't umount /data/local/mnt/dev: Invalid argument
umount: can't umount /data/local/mnt/proc: Permission denied
umount: can't umount /data/local/mnt/sys: Permission denied
umount: can't umount /data/local/mnt/selinux: Permission denied
umount: can't umount /data/local/mnt: Permission denied
Still nothing and now it goes on to the shutdown section
Doing the chroot command does nothing and to be honest, I wouldn`t even know if it was supposed to do anything as this function is new for me.
Code:
/system/xbin/busybox chroot /data/local/mnt /root/init.sh ubuntu.img
All the commands work with just being root (command su) or through busybox.
All the files have root owner/group and they are executable.
Debug so far:
Rename supplied busybox version to busybox.org => removed it entirely with a fixed link to busybox itself.
3 different bootscript.sh
Changed ext2 to ext4, latest was ext4.
Reinstalled, rebooted, kicked it a few times.
Checked perms on everything and it *looks* all good.
All commands the bootscript.sh tries to call do work when doing it manually in the command shell, but even "sh bootscript.sh" fails on all.
Changed "setenforce 0" as some one has suggested.
Here is my butcherd bootscript.sh script that I try to run it with:
Code:
###########################################
# Linux boot script V8 for Android v4.3 #
# Built by Zachary Powell (zacthespack) #
# and Martin M..ller (Tuxling) #
# Thanks to: #
# Johan Vromans #
# Marshall Levin #
# Vaykadji #
# and to everyone at XDA! #
# Feel free to edit/use this script as you#
# like but credit Linuxonandroid.org #
###########################################
# $ver: V8 #
###########################################
###########################################
# This is a function we use to stop the #
# script in case of errors #
###########################################
error_exit() {
echo "Error: $1"
exit 1
}
###########################################
# Set up variables #
###########################################
export bbox=/system/xbin/busybox
# echo $bbox
export usermounts=android # Base folder all user mounts are done in, should be moved to app later
export imgfile=/sdcard/ubuntu/ubuntu.img # Default image file, another can be set by using an argument
export bin=/system/xbin9
export mnt=/data/local/mnt
export USER=root
if [[ ! -d $mnt ]]; then mkdir $mnt; fi
export PATH=$bin:/usr/bin:/usr/local/bin:/usr/sbin:/bin:/usr/local/sbin:/usr/games:$PATH
export TERM=linux
export HOME=/root
###########################################
# Handle arguments if present #
###########################################
if [ $# -ne 0 ]; then
if [ -f $1 ]; then # Is full path present?
imgfile=$1
elif [ -f $(dirname $0)/$1 ]; then # Is only a filename present?
imgfile=$(dirname $0)/$1
else
error_exit "Image file not found!($1)"
fi
fi
###########################################
# If a md5 file is found we check it here #
###########################################
#if [ -f $imgfile.md5 ]; then
# echo "MD5 file found, use to check .img file? (y/n)"
# read answer
# if [ $answer == y ]; then
# echo -n "Validating image checksum... "
# $bbox md5sum -c -s $imgfile.md5
# if [ $? -ne 0 ];then
# echo "FAILED!"
# error_exit "Checksum failed! The image is corrupted!"
# else
# echo "OK"
# rm $imgfile.md5
# fi
# fi
#
#fi
################################
# Find and read config file #
# or use defaults if not found #
################################
use_swap=no
cfgfile=$imgfile.config # Default config file if not specified
if [ -f $imgfile.config ]; then
source $imgfile.config
fi
###########################################
# Set Swap up if wanted #
# #
###########################################
if [ $use_swap == yes ]; then
if [ -f $imgfile.swap ]; then
echo "Swap file found, using file"
echo "Turning on swap (if it errors here you do not have swap support"
swapon $imgfile.swap
else
echo "Creating Swap file"
dd if=/dev/zero of=$imgfile.swap bs=1048576 count=1024
mkswap $imgfile.swap
echo "Turning on swap (if it errors here you do not have swap support"
swapon $imgfile.swap
fi
fi
###########################################
# Set up loop device and mount image #
###########################################
echo -n "Checking loop device... "
if [ -b /dev/block/loop255 ]; then
echo "FOUND"
else
echo "MISSING"
# Loop device not found so we create it and verify it was actually created
echo -n "Creating loop device... "
$bbox mknod /dev/block/loop255 b 7 255
echo -n "Command: $bbox mknod /dev/block/loop255 b 7 255 \n"
if [ -b /dev/block/loop255 ]; then
echo "OK"
else
echo "FAILED"
error_exit "Unable to create loop device!"
fi
fi
$bbox losetup /dev/block/loop255 $imgfile
echo -n "Command: $bbox losetup /dev/block/loop255 $imgfile \n"
if [ $? -ne 0 ];then error_exit "Unable to attach image to loop device! (Image = $imgfile)"; fi
$bbox mount -t ext4 /dev/block/loop255 $mnt
echo -n "Command: $bbox mount -t ext4 /dev/block/loop255 $mnt \n"
if [ $? -ne 0 ];then error_exit "Unable to mount the loop device! \n"; fi
###########################################
# Mount all required partitions #
###########################################
$bbox mount -t devpts devpts $mnt/dev/pts
echo -n "Command: $bbox mount -t devpts devpts $mnt/dev/pts \n"
if [ $? -ne 0 ];then $bbox mount -o bind /dev $mnt/dev; $bbox mount -t devpts devpts $mnt/dev/pts; fi
if [ $? -ne 0 ]; then error_exit "Unable to mount $mnt/dev/pts!"; fi
$bbox mount -t proc proc $mnt/proc
echo -n "Command: $bbox mount -t proc proc $mnt/proc \n"
if [ $? -ne 0 ];then error_exit "Unable to mount $mnt/proc!"; fi
$bbox mount -t sysfs sysfs $mnt/sys
echo -n "Command: $bbox mount -t sysfs sysfs $mnt/sys \n"
if [ $? -ne 0 ];then error_exit "Unable to mount $mnt/sys!"; fi
$bbox mount -o bind /sdcard $mnt/sdcard
echo -n "Command: $bbox mount -o bind /sdcard $mnt/sdcard \n"
if [ $? -ne 0 ];then error_exit "Unable to bind $mnt/sdcard!"; fi
if [[ ! -d $mnt/root/cfg ]]; then mkdir $mnt/root/cfg; fi
$bbox mount -o bind $(dirname $imgfile) $mnt/root/cfg
echo -n "Command: $bbox mount -o bind $(dirname $imgfile) $mnt/root/cfg \n"
$bbox mount -o bind /sys/fs/selinux $mnt/selinux
echo -n "Command: $bbox mount -o bind /sys/fs/selinux $mnt/selinux \n"
###########################################
# Checks if you have a external sdcard #
# and mounts it if you do #
###########################################
if [ -d /sdcard/external_sd ]; then
$bbox mount -o bind /sdcard/external_sd $mnt/external_sd
fi
if [ -d /Removable/MicroSD ]; then
$bbox mount -o bind /Removable/MicroSD $mnt/external_sd
fi
# This is for the HD version of the Archos 70 internet tablet, may be the same for the SD card edition but i dont know.
if [ -d /storage ]; then
$bbox mount -o bind /storage $mnt/external_sd
fi
###########################################
# Mount all user defined mounts if any #
###########################################
if [ -f $imgfile.mounts ]; then
olddir=$(pwd)
echo "Mounting user mounts"
cd $mnt
if [[ ! -d $mnt/$usermounts ]]; then $bbox mkdir -p $usermounts; fi
echo "# Script to unmount user defined mounts, do not delete or edit!" > $imgfile.shutdown
echo "cd $mnt/$usermounts" > $imgfile.shutdown
cd $mnt/$usermounts
for entry in $(cat "$imgfile.mounts"); do
ANDROID=${entry%;*}
LINUX=${entry#*;}
if [[ -d $ANDROID ]]; then
echo -n "Mounting $ANDROID to $usermounts/$LINUX... "
if [[ ! -d $mnt/$usermounts/$LINUX ]]; then $bbox mkdir -p $LINUX; fi
$bbox mount -o bind $ANDROID $mnt/$usermounts/$LINUX &> /dev/null
if [ $? -ne 0 ];then
echo FAIL
if [[ -d $mnt/$usermounts/$LINUX ]]; then $bbox rmdir -p $LINUX; fi
else
echo OK
echo "$bbox umount $mnt/$usermounts/$LINUX" >> $imgfile.shutdown
echo "$bbox rmdir -p $LINUX" >> $imgfile.shutdown
fi
else
echo "Android folder not found: $ANDROID"
fi
done
echo "cd $mnt" >> $imgfile.shutdown
echo "$bbox rmdir -p $usermounts" >> $imgfile.shutdown
cd $olddir
else
echo "No user defined mount points"
fi
###########################################
# Sets up network forwarding #
###########################################
$bbox sysctl -w net.ipv4.ip_forward=1
if [ $? -ne 0 ];then error_exit "Unable to forward network!"; fi
# If NOT $mnt/root/DONOTDELETE.txt exists we setup hosts and resolv.conf now
#if [ ! -f $mnt/root/DONOTDELETE.txt ]; then
# echo "nameserver 8.8.8.8" > $mnt/etc/resolv.conf
# if [ $? -ne 0 ];then error_exit "Unable to write resolv.conf file!"; fi
echo "nameserver 8.8.4.4" >> $mnt/etc/resolv.conf
echo "127.0.0.1 localhost" > $mnt/etc/hosts
# if [ $? -ne 0 ];then error_exit "Unable to write hosts file!"; fi
#fi
###########################################
# Chroot into ubuntu #
###########################################
$bbox chroot $mnt /root/init.sh $(basename $imgfile)
echo -n "Command: $bbox chroot $mnt /root/init.sh $(basename $imgfile) \n"
###########################################
# Shut down ubuntu #
###########################################
echo "Shutting down Linux ARM"
#for pid in `lsof | grep $mnt | sed -e's/ / /g' | cut -d' ' -f2`; do kill -9 $pid >/dev/null 2>&1; done
for pid in `$bbox lsof | $bbox grep $mnt | $bbox sed -e's/ / /g' | $bbox cut -d' ' -f2`; do $bbox kill -9 $pid >/dev/null 2>&1; done
sleep 5
###########################################
# Unmount all user defined mounts if any #
###########################################
if [ -f $imgfile.shutdown ]; then
echo "Unmounting user defined mounts"
sh $imgfile.shutdown
rm $imgfile.shutdown
fi
$bbox umount $mnt/root/cfg
$bbox umount $mnt/sdcard
$bbox umount $mnt/external_sd
$bbox umount $mnt/dev/pts
$bbox umount $mnt/dev
$bbox umount $mnt/proc
$bbox umount $mnt/sys
$bbox umount $mnt/selinux
$bbox umount $mnt
I am at my whips end, the 12.2 is an awsome device to finally run a desktop on as a tablet, my mom already calls it a "TabTop" tablet+laptop, all I see though is a hole in the wall that is the size of my head
Could anyone please assist me with this strange issue? Pretty please? :angel:
With the new beta coming soon™ for CLI and that there won`t be many people like me that buy this toy for fun, I also volunteer to help to make this app idiot proof (point to self) as the work is awsome, even if it didn`t run out of the box :highfive:

No one an idea?

Kamuchi said:
No one an idea?
Click to expand...
Click to collapse
I also have this problem... I think it's caused by the kernel that is set to enforcing... ; (
But you can use Debian no root it uses a fakechroot so you can use it without root and it uses the X server and you needn't to vnc in it. Hope I could help

prohackerbro said:
I also have this problem... I think it's caused by the kernel that is set to enforcing... ; (
But you can use Debian no root it uses a fakechroot so you can use it without root and it uses the X server and you needn't to vnc in it. Hope I could help
Click to expand...
Click to collapse
did you get debian to work ?

great!!

Startup speedup

Hi,
I've noticed that some apps uses the old "private apk" feature which requires a mountpoint for every app:
Code:
# grep dm- /proc/mounts
/dev/block/dm-0 /mnt/asec/com.melodis.midomiMusicIdentifier-2 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime 0 0
/dev/block/dm-1 /mnt/asec/com.wolfram.android.alpha-1 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime 0 0
/dev/block/dm-2 /mnt/asec/com.shinycore.picsaypro-1 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime 0 0
/dev/block/dm-3 /mnt/asec/com.tfiver.obd2sound-1 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime 0 0
/dev/block/dm-4 /mnt/asec/it.itentropy.fswidget-1 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime 0 0
/dev/block/dm-5 /mnt/asec/com.teslacoilsw.quicksshd-1 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime 0 0
/dev/block/dm-6 /mnt/asec/org.prowl.torque-1 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime 0 0
I wrote a script which reinstalles them in the common way, reducing the mountpoint, here is the source:
https://github.com/teknoraver/misc/blob/master/apkmove
after running it on the PC the mountpoints are 0:
Code:
# grep dm- /proc/mounts
#
and the boot is faster

[Q] Bricked Nexus 5 - Partition table missing

Hi all,
I think my wife's Nexus 5 is bricked... hoping it's not a hardware issue but I'm starting to think it is.
It started with the phone turning off when ever it felt like it... then one day it wouldn't boot completely and just be stuck on the flying google colors.
I called Google Support and they told me to wipe cache and wipe to factory defaults... It kinda didn't work and the support agent told me to reboot over and over again...
Now I'm trying to use fastboot to flash stock android and nothing seems to work... I'm getting write failures all over the place.
I then installed TWRP and booted to recovery and from there I can see that the NAND seems to be oddly small and with an invalid partition table...
dmesg | grep mmc
Code:
dmesg | grep mmc
<5>[ 0.000000] Kernel command line: console=ttyHSL0,115200,n8 androidboot.har
dware=hammerhead user_debug=31 maxcpus=2 msm_watchdog_v2.enable=1 uart_console=e
nable gpt=enable lge.kcal=0|0|0|x lge.rev=rev_11 androidboot.laf androidboot.emm
c=true fastboot=true androidboot.serialno=0315c2990934d564 androidboot.bootloade
r=HHZ12h androidboot.baseband=msm bootreason=power_on androidboot.hardware.sku=D
820 androidboot.hardware.ddr=hynix androidboot.hardware.display=orise
<6>[ 1.515883] mmc0: SDCC Version: 0x00000038
<6>[ 1.518998] mmc0: bam physical base=0xf9884000
<6>[ 1.519201] mmc0: bam virtual base=0xf0378000
<6>[ 1.519766] mmc0: BAM device registered. bam_handle=0xed541c00
<6>[ 1.522174] mmc0: Qualcomm MSM SDCC-BAM at [mem 0xf9884000-0xf988afff flag
s 0x200] [irq 252 flags 0x400]
<6>[ 1.522602] mmc0: Qualcomm MSM SDCC-DML [mem 0xf98a4800-0xf98a48ff flags 0
x200]
<6>[ 1.523032] mmc0: id 2, nonremovable 0
<6>[ 1.527101] mmc0: Qualcomm MSM SDCC-core [mem 0xf98a4000-0xf98a47ff flags
0x200] [irq 157 flags 0x400],0 dma -1 dmacrcri -1
<6>[ 1.527176] mmc0: Controller capabilities: 0x00003ffe
<6>[ 1.527269] mmc0: 8 bit data mode disabled
<6>[ 1.527341] mmc0: 4 bit data mode enabled
<6>[ 1.527380] mmc0: polling status mode disabled
<6>[ 1.527419] mmc0: MMC clock 400000 -> 200000000 Hz, PCLK 0 Hz
<6>[ 1.527490] mmc0: Slot eject status = 1
<6>[ 1.527529] mmc0: Power save feature enable = 1
<6>[ 1.527601] mmc0: SPS-BAM data transfer mode available
<6>[ 1.532221] mmc1: no vmmc regulator found
<7>[ 1.533705] Registered led device: mmc1::
<6>[ 1.535212] mmc1: SDHCI controller on msm_sdcc.1 [msm_sdcc.1] using ADMA
<6>[ 1.655859] mmc1: new MMC card at address 0001
<6>[ 1.657207] mmcblk0: mmc1:0001 SDM032 30.6 MiB
<6>[ 1.661766] mmcblk0: unknown partition table
/sbin # ←[6n
fdisk (take not that disk seems to be only 32MB instead of 32GB)
Code:
/sbin # ←[6nfdisk -ul /dev/block/mmcblk0
fdisk -ul /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 32 MB, 32096256 bytes
4 heads, 16 sectors/track, 979 cylinders, total 62688 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk /dev/block/mmcblk0 doesn't contain a valid partition table
mount
Code:
/sbin # ←[6nmount
mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
tmpfs on /tmp type tmpfs (rw,seclabel,relatime)
cat /proc/partitions
Code:
cat /proc/partitions
major minor #blocks name
179 0 31344 mmcblk0
Does anyone know what is going on?

Try locking the bootloader, fastboot oem lock, and rebooting. Does it stay locked, fastboot oem device-info? If it didn't it's a good sign the nand is bad.
Sent from my Nexus 9 using XDA Free mobile app

jd1639 said:
Try locking the bootloader, fastboot oem lock, and rebooting. Does it stay locked, fastboot oem device-info? If it didn't it's a good sign the nand is bad.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
it stays locked... is this something I can potentially fix then?
Code:
C:\Program Files\Android\android-sdk\platform-tools>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) off-mode-charge: true
OKAY [ 0.031s]
finished. total time: 0.031s
Any ideas how I can proceed?

flickers said:
Hi all,
I think my wife's Nexus 5 is bricked... hoping it's not a hardware issue but I'm starting to think it is.
It started with the phone turning off when ever it felt like it... then one day it wouldn't boot completely and just be stuck on the flying google colors.
I called Google Support and they told me to wipe cache and wipe to factory defaults... It kinda didn't work and the support agent told me to reboot over and over again...
Now I'm trying to use fastboot to flash stock android and nothing seems to work... I'm getting write failures all over the place.
I then installed TWRP and booted to recovery and from there I can see that the NAND seems to be oddly small and with an invalid partition table...
dmesg | grep mmc
Code:
dmesg | grep mmc
<5>[ 0.000000] Kernel command line: console=ttyHSL0,115200,n8 androidboot.har
dware=hammerhead user_debug=31 maxcpus=2 msm_watchdog_v2.enable=1 uart_console=e
nable gpt=enable lge.kcal=0|0|0|x lge.rev=rev_11 androidboot.laf androidboot.emm
c=true fastboot=true androidboot.serialno=0315c2990934d564 androidboot.bootloade
r=HHZ12h androidboot.baseband=msm bootreason=power_on androidboot.hardware.sku=D
820 androidboot.hardware.ddr=hynix androidboot.hardware.display=orise
<6>[ 1.515883] mmc0: SDCC Version: 0x00000038
<6>[ 1.518998] mmc0: bam physical base=0xf9884000
<6>[ 1.519201] mmc0: bam virtual base=0xf0378000
<6>[ 1.519766] mmc0: BAM device registered. bam_handle=0xed541c00
<6>[ 1.522174] mmc0: Qualcomm MSM SDCC-BAM at [mem 0xf9884000-0xf988afff flag
s 0x200] [irq 252 flags 0x400]
<6>[ 1.522602] mmc0: Qualcomm MSM SDCC-DML [mem 0xf98a4800-0xf98a48ff flags 0
x200]
<6>[ 1.523032] mmc0: id 2, nonremovable 0
<6>[ 1.527101] mmc0: Qualcomm MSM SDCC-core [mem 0xf98a4000-0xf98a47ff flags
0x200] [irq 157 flags 0x400],0 dma -1 dmacrcri -1
<6>[ 1.527176] mmc0: Controller capabilities: 0x00003ffe
<6>[ 1.527269] mmc0: 8 bit data mode disabled
<6>[ 1.527341] mmc0: 4 bit data mode enabled
<6>[ 1.527380] mmc0: polling status mode disabled
<6>[ 1.527419] mmc0: MMC clock 400000 -> 200000000 Hz, PCLK 0 Hz
<6>[ 1.527490] mmc0: Slot eject status = 1
<6>[ 1.527529] mmc0: Power save feature enable = 1
<6>[ 1.527601] mmc0: SPS-BAM data transfer mode available
<6>[ 1.532221] mmc1: no vmmc regulator found
<7>[ 1.533705] Registered led device: mmc1::
<6>[ 1.535212] mmc1: SDHCI controller on msm_sdcc.1 [msm_sdcc.1] using ADMA
<6>[ 1.655859] mmc1: new MMC card at address 0001
<6>[ 1.657207] mmcblk0: mmc1:0001 SDM032 30.6 MiB
<6>[ 1.661766] mmcblk0: unknown partition table
/sbin # ←[6n
fdisk (take not that disk seems to be only 32MB instead of 32GB)
Code:
/sbin # ←[6nfdisk -ul /dev/block/mmcblk0
fdisk -ul /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 32 MB, 32096256 bytes
4 heads, 16 sectors/track, 979 cylinders, total 62688 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk /dev/block/mmcblk0 doesn't contain a valid partition table
mount
Code:
/sbin # ←[6nmount
mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
tmpfs on /tmp type tmpfs (rw,seclabel,relatime)
cat /proc/partitions
Code:
cat /proc/partitions
major minor #blocks name
179 0 31344 mmcblk0
Does anyone know what is going on?
Click to expand...
Click to collapse
What is see is that the emmc turned into a 32 mb emmc. Which is interesting because your phone could not boot up if that happen.

Brainstorming: Could we, 1st, retrieve the partition table from another device, 2nd flash it back to this one?
What about LG flashtool? Would that try to restore partition table?
Or all of the above don't matter because the nand really fried?

beekay201 said:
Brainstorming: Could we, 1st, retrieve the partition table from another device, 2nd flash it back to this one?
What about LG flashtool? Would that try to restore partition table?
Or all of the above don't matter because the nand really fried?
Click to expand...
Click to collapse
Exactly what I was thinking...
I know about the LG Flashtool but as I'm not getting Qualcomm HS-USB QDLoader 9008 I'm avoiding that at the moment as I would rather not open the device...
I've also tried installing zip by copying it to /tmp in TWRP and installing from there... no success
I've tried parted and it's reporting pretty much the same as fdisk
I've tried blockdev
Code:
/sbin # ←[6nblockdev --getsize64 /dev/block/mmcblk0
blockdev --getsize64 /dev/block/mmcblk0
32096256
Code:
/sbin # ←[6nblockdev --getss /dev/block/mmcblk0
blockdev --getss /dev/block/mmcblk0
512
Code:
/sbin # ←[6nblockdev --getbsz /dev/block/mmcblk0
blockdev --getbsz /dev/block/mmcblk0
4096
I've tried stock recovery and CWM as well.. nothing is working as they can't mount anything
Any ideas?

This is a device you want to warranty and RUN not walk away from. You've corrupted blocks marked for your partition table (the very first blocks on the drive "physically" iirc) and that isn't going to change even if you can rebuild the file system through some voodoo blacksmith spell.
I only assume you're still in warranty because I notice you spoke with google support once already. If not... Well...
Once you've hurt flash memory bad enough that it starts losing blocks it only gets worse.

Unable to delete directory /sdcard/usbStorage/

Hello all. Long time lurker, occasional poster - hope you can help me out here.
So, I came from a stock rooted Pixel running the June security update, and recently moved everything over to a combo of Stock ROM + ElementalX kernel + Magisk v12 with some help from a handy guide here on the forums.
To my chagrin, I noticed that StickMount Pro no longer functioned with MagiskSU. Not that big of a deal - I learned to live without.
*However*
Now I seem to be unable to delete the sdcard directory tree starting at /sdcard/usbStorage/, regardless of what all I've thrown at it.
In the terminal, each folder/subfolder looks like this: (ls -al)
Code:
. . .
drwxrwx--x 2 root sdcard_rw 4096 2017-06-15 21:14 sda4
. . .
There's notably just sda4 - sda36, skipping a few between, then sdb1, sdc1, sdd2 - sdd 13.
There's these folders under /sdcard/usbStorage/ : (ls -al)
Code:
.
. .
drwxrwx--x 2 root sdcard_rw 4096 2017-06-15 21:13 00BC-614E
drwxrwx--x 2 root sdcard_rw 4096 2017-06-15 21:14 57f8f4bc-abf4-655f-bf67-946fc0f9f25b
drwxrwx--x 2 root sdcard_rw 4096 2017-06-15 21:14 _
. . .
One of those looks like a device's UUID.
I've tried:
- Removing with SolidExplorer, and as root.
- su rm -rf /sdcard/usbStorage (received permission denied errors)
- su; busybox rm -rf /sdcard/usbStorage (just for completeness)
- Reinstalling StickMount and trying the various unmount options, as well as unticking the "create /sdcard/ directories" option
Since these failed me, I began trying to change the folder/group permissions across adb:
- chown -R 777 /sdcard/usbStorage , then rm -rf (still permission denied)
- addgroup $(whoami) sdcard_rw (unknown user "root")
- addgroup root sdcard_rw (unknown user "root")
The `mount` command lists nothing related. Only the following:
Code:
rootfs on / type rootfs (rw,seclabel)
/dev/root on / type ext4 (ro,seclabel,relatime,data=ordered)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,size=1896652k,nr_inodes=474163,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)
proc on /proc type proc (rw,relatime,gid=3009,hidepid=2)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,seclabel,relatime)
none on /acct type cgroup (rw,relatime,cpuacct)
none on /dev/stune type cgroup (rw,relatime,schedtune)
tmpfs on /mnt type tmpfs (rw,seclabel,relatime,size=1896652k,nr_inodes=474163,mode=755,gid=1000)
none on /config type configfs (rw,relatime)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
none on /dev/cpuset type cgroup (rw,relatime,cpuset,noprefix,release_agent=/sbin/cpuset_release_agent)
pstore on /sys/fs/pstore type pstore (rw,seclabel,relatime)
/dev/block/dm-1 on /vendor type ext4 (ro,seclabel,relatime,discard,data=ordered)
/dev/block/sda25 on /firmware/radio type vfat (ro,context=u:object_r:firmware_file:s0,relatime,uid=1000,fmask=0337,dmask=0227,codepage=437,iocharset=iso8859-1,shortname=lower,errors=remount-ro)
/dev/block/sdd3 on /persist type ext4 (rw,seclabel,nosuid,nodev,relatime,data=ordered)
tmpfs on /storage type tmpfs (rw,seclabel,relatime,size=1896652k,nr_inodes=474163,mode=755,gid=1000)
adb on /dev/usb-ffs/adb type functionfs (rw,relatime)
/dev/block/sda35 on /data type ext4 (rw,seclabel,nosuid,nodev,noatime,noauto_da_alloc,data=ordered)
/dev/block/loop0 on /magisk type ext4 (rw,seclabel,noatime,data=ordered)
/dev/block/loop0 on /system/etc/hosts type ext4 (rw,seclabel,noatime,data=ordered)
tmpfs on /system/xbin type tmpfs (rw,seclabel,nosuid,relatime,size=1896652k,nr_inodes=474163,mode=755)
tmpfs on /sbin type tmpfs (rw,seclabel,nosuid,relatime,size=1896652k,nr_inodes=474163,mode=755)
/dev/fuse on /mnt/runtime/default/emulated type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /storage/emulated type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /mnt/runtime/read/emulated type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /mnt/runtime/write/emulated type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
Also, any attempt to mount/umount things throws the error:
Code:
mount: bad /etc/fstab: No such file or directory
etc...
I'm just hesitant to re-install SuperSU for fear of how it will clash with TWRP and Magisk *and* break SafetyNet just to try to remove this dir.
Could these somehow be related to the /dev/fuse filesystems?
Any help at all would be appreciated.
If I can't effectively chown / chmod them, I don't quite know how to proceed.