lildebi icon indicating copy to clipboard operation
lildebi copied to clipboard

Fails to install on Samsung Galaxy ACE CyanogenMod 7.2

Open arthurlutz opened this issue 8 years ago • 1 comments

Install log says (snipped the rest)




+ losetup
BusyBox v1.22.1 (2015-01-26 17:29:04 UTC) multi-call binary.

Usage: losetup [-r] [-o OFS] {-f|LOOPDEV} FILE - associate loop devices
        losetup -d LOOPDEV - disassociate
        losetup -a - show status
        losetup -f - show next free loop device

        -o OFS  Start OFS bytes into FILE
        -r      Read-only
        -f      Show/use next free loop device

+ /system/xbin/losetup
+ /system/xbin/losetup /dev/block/loop0 /mnt/sdcard/debian.img
+ losetup
BusyBox v1.22.1 (2015-01-26 17:29:04 UTC) multi-call binary.

Usage: losetup [-r] [-o OFS] {-f|LOOPDEV} FILE - associate loop devices
        losetup -d LOOPDEV - disassociate
        losetup -a - show status
        losetup -f - show next free loop device

        -o OFS  Start OFS bytes into FILE
        -r      Read-only
        -f      Show/use next free loop device

+ /system/xbin/losetup
/dev/block/loop0: 0 /mnt/sdcard/debian.img
+ mount -o loop,noatime,errors=remount-ro /dev/block/loop0 /data/debian
+ [ 0 -ne 0 ]
+ cd /data/debian
+ tar xf /data/data/info.guardianproject.lildebi/app_bin/cdebootstrap.tar
tar: can't create directory 'usr/': Operation not permitted
tar: can't open 'usr/': Is a directory

It's failling to untar cdeboostrap to the mounted image. The rest fails obviously.

The reason is below : mounting /dev/block/loop0 seems to point to a j4fs with read only stuff (is it the recovery OS ?)

# mount -o loop,noatime,errors=remount-ro /dev/block/loop0 /data/debian
# ls /data/debian
ani_upload_1_kernel_panic.jpg       fota_reboot
ani_upload_2_cp_crash.jpg           jigusb_dl_flag
ani_upload_3_forced_upload.jpg      log_enable
ani_upload_4_hardware_reset.jpg     logo.jpg
ani_upload_4_unknown_reset.jpg      logo_kor.jpg
ani_upload_4_watchdog_reset.jpg     logo_lafleur.jpg
ani_upload_5_user_fault.jpg         logo_org.jpg
ani_upload_6_hsic_disconnected.jpg  logo_voda.jpg
charging.jpg                        nps_fail.jpg
charging_kor.jpg                    nps_status
debug_level.inf                     param.blk
droid.jpg                           sud_index
dummy.bin                           switch_sel
# mount
rootfs on / type rootfs (ro,relatime)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
tmpfs on /mnt/obb type tmpfs (rw,relatime,mode=755,gid=1000)
/dev/stl9 on /system type ext4 (rw,relatime,barrier=1,data=ordered)
/dev/stl10 on /cache type ext4 (rw,nosuid,nodev,relatime,barrier=1,data=ordered)
/dev/stl6 on /mnt/.lfs type j4fs (rw,relatime)
/dev/stl11 on /data type ext4 (rw,nosuid,nodev,relatime,barrier=1,data=ordered)
/dev/block/vold/179:1 on /mnt/sdcard type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0602,dmask=0602,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/vold/179:1 on /mnt/secure/asec type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0602,dmask=0602,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
tmpfs on /mnt/sdcard/.android_secure type tmpfs (ro,relatime,size=0k,mode=000)
/dev/block/loop0 on /data/debian type j4fs (rw,noatime)

I am available to debug if you can point me in the right direction. Or to give extra details about the phone setup.

arthurlutz avatar Apr 17 '16 20:04 arthurlutz

A tar command goes like this: tar xf file_to_extract.tar destination_folder

UMRnInside avatar Dec 07 '17 14:12 UMRnInside