Develop Bugs

[Q] Problems restoring nandroid in Rogue Recovery 1.1.1

ROM is Calkulin 2.0.1a, all EK02. MicroSD card is 32GB Class 10.
I was originally having headset jack issues (no ear speaker audio, no option to use speakers or bluetooth) that I thought were software related; I created a full nandroid backup, wiped all, and restored to clean 2.0.1a before I realized that the headset jack might have been stuck. Fixed the headset issue, booted into recovery to restore the nandroid, you can select Restore or Advanced Restore...
"Error opening directory.
No files found."
No option to select folder or anything like that, although going into the zip flash dialog shows the folder structure in whichever storage I select.
I've copied the recovery files between SD and internal, tried playing with the folder structure to see if I could get it to do something (including dumping the whole folder into the root)... I could understand if the recovery wasn't able to read from a 32gb card for one reason or another, but the fact that I can't get it to open anything at all is frustrating. Appreciate any help you have to give.
Tried updating to Desperado/1.1.2 after posting this thread - still no luck.
Oh, log:
Starting recovery on Sun Dec 11 01:58:41 2011
framebuffer: fd 4 (480 x 800)
Rogue ET Recovery 1.1.1 (CWM v5.0.2.7)
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /boot emmc /dev/block/mmcblk0p5 (null)
2 /recovery emmc /dev/block/mmcblk0p6 (null)
3 /efs ext4 /dev/block/mmcblk0p1 (null)
4 /cache ext4 /dev/block/mmcblk0p7 (null)
5 /system ext4 /dev/block/mmcblk0p9 (null)
6 /data ext4 /dev/block/mmcblk0p10 (null)
7 /sdcard vfat /dev/block/cyasblkdevblk0p1 /dev/block/cyasblkdevblk0
8 /emmc vfat /dev/block/mmcblk0p11 (null)
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
I:Completed outputting fstab.
Irocessing arguments.
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.service.adb.enable=1
ro.factorytest=0
ro.serialno=
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=unknown
ro.hardware=smdkc210
ro.revision=12
ro.emmc=0
dpm.allowpolicy=1
init.svc.recovery=running
init.svc.adbd=running
ro.build.product=smdkc210
ro.product.device=smdkc210
ro.radio.noril=yes
status.battery.state=Slow
status.battery.level=5
status.battery.level_raw=50
status.battery.level_scale=9
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
Error opening directory.
No files found.
Nandroid storage: internal storage
Nandroid storage: SD card
Error opening directory.
No files found.
Nandroid storage: internal storage
Error opening directory.
No files found.
Click to expand...
Click to collapse

[Q] How to mount ext partition ?

I used to edit fstab to add mount points, but there isn't inside the rom I'm using (AOKP) !
well, I used this then:
Code:
ls -l /dev/block/platform/omap/omap_hsmmc.0/by-name
and it works ... But my "sdcard" or better.. the internal memory.. has a partition in ext, done by CWM.
I don't know how to mount it!
this is my output:
Code:
lrwxrwxrwx root root 2012-01-31 12:26 boot -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2012-01-31 12:26 cache -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2012-01-31 12:26 dgs -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2012-01-31 12:26 efs -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2012-01-31 12:26 metadata -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2012-01-31 12:26 misc -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2012-01-31 12:26 param -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2012-01-31 12:26 radio -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2012-01-31 12:26 recovery -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2012-01-31 12:26 sbl -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2012-01-31 12:26 system -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2012-01-31 12:26 userdata -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2012-01-31 12:26 xloader -> /dev/block/mmcblk0p1
Any help?

Android does not utilize /etc/fstab to mount the file system during the init process. It's done in the init.rc file.
Can you better explain what you are trying to do here?

ok maybe he doesn't, but with cyanogenmod 5 (or 6, sorry dont remember) I used to see the content of this file (fstab), and there was the partition table with all the mount points.. sdext included.
I show you.
#CyanogenMod 5(or 6..I take this from an old thread of mine in another forum):
Code:
[B]#cat /etc/fstab[/B]
/dev/block/mtdblock3 /system yaffs2 rw
/dev/block/mtdblock4 /cache yaffs2 rw
/dev/block/mtdblock5 /data yaffs2 rw
/dev/block/mmcblk0p1 /sdcard vfat rw
/dev/block/mmcblk0p2 /sd-ext auto rw
#CyanogenMod 7 (the one I'm currently using on my HTC G1)
Code:
[B]#cat /etc/vold.fstab[/B]
# Copyright (C) 2009 The Android Open Source Project
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
## Vold 2.0 fstab for HTC Dream or Sapphire
#
## - San Mehat ([email protected])
##
#######################
## Regular device mount
##
## Format: dev_mount <label> <mount_point> <part> <sysfs_path1...>
## label - Label for the volume
## mount_point - Where the volume will be mounted
## part - Partition # (1 based), or 'auto' for first usable partition.
## <sysfs_path> - List of sysfs paths to source devices
######################
# Mounts the first usable partition of the specified device
dev_mount sdcard /mnt/sdcard auto /devices/platform/goldfish_mmc.0 /devices/platform/msm_sdcc.2/mmc_host/mmc1
With Cyano's 5(or 6) i had App2ext (so maybe i could see ext because of this)
With Cyano's 7 I haven't.. so ok, maybe that's why I can not see the de ext mount point and just the fat ..
And maybe I answered myself !!!!
because I don't have Apps2ext in my GN so I can't neither see the sdext partition because it is not mounted as well.
F***
Anyway... Is there a way to mount EXT anyway?
I just want to mount and use it, with my G1 I ran ubuntu putting an ubuntu image on ext and mounted on /sdcard/ubuntu

CyanogenMod contained a lot of non AOSP modifications - including "sdext".
You can run your mount commands by modifying the init.rc file. You can also use init.d as well in ROMs that have it enabled.
However I'm not sure why you think you have an EXT partition done by CWM though?

silow said:
However I'm not sure why you think you have an EXT partition done by CWM though?
Click to expand...
Click to collapse
Honestly ... me as well.. I just want to play around with it
the 1st month I bought the G1, I bricked it, I flashed thousand roms! changed all the spl, kernels, radios...
I.. like it.
anyway thank u it's clear now!

On the Galaxy Nexus the /sdcard mount is mounted on a sub directory (/data/media) not it's own partition - it's a "virtual sdcard". Thus the CWM partition options don't work here because it assumes the sdcard is it's own device/partition.
If you want a mountable block device you're going to have to modify the stock partitions or use some other means such as a loop device.
In any case if you need a hook into the init process to mount something you can use init.rc or init.d

SGN2 N7100 contents of efs

Using root explorer what are the files located within efs can anyone list it with its values, for example :- efs.tar 2MB
Just double checking to know wheather i still have the efs in my device after corrupting the efs when flashing back to stock 4.1.2 and this today after doing a cwm backup was reading the recovery log:
Recovery.log - (truncated)
Starting recovery on Sun Dec 8 01:26:19 2013 (UTC)
framebuffer: fd 4 (720 x 1280)
PhilZ Touch 5
CWM Base version: v6.0.3.7
I:Build version: 5.11.1 - n710x-i317M-T889
recovery filesystem table
==================
0 /tmp ramdisk (null) (null) 0
1 /efs ext4 /devblock/mmcblk0p3 (null) 0
2 /boot emmc /dev/block/mmcblk0p8 (null) 0
3 /recovery emmc /dev/block/mmcblk0p9 (null) 0
4 /cache ext4 /dev/block/mmcblk0p12 (null) 0
5 /system ext4 /dev/block/mmcblk0p13 (null) 0
6 /data ext4 /dev/block/mmcblk0p16 (null) -16384
7 /preload ext4 /dev/block/mmcblk0p14 (null) 0
8 /modem emmc /dev/block/mmcblk0p10 (null) 0
9 /sdcard datamedia /dev/null (null) 0
10 /external_sd auto /dev/block/mmcblk1p1 (null) 0
11 /sd-ext ext4 /dev/block/mmcblk1p2 (null) 0
and it goes on and on.......
But the above is the one bothering me showing null null and null..
Am able to use the phone now of course after flashing mf1 modem but the question is do i still have my efs.

[Q]kitchen setup

need help here to setup dsixda kitchen.how to configure edify_defs in kitchen directory?here the mounting.my device smt211
# mount point fstype device device2
/system ext4 /dev/block/mmcblk0p14
/cache ext4 /dev/block/mmcblk0p15
/data ext4 /dev/block/mmcblk0p17 length=-16384
/efs ext4 /dev/block/mmcblk0p6
/misc emmc misc
/boot emmc /dev/block/mmcblk0p9
/recovery emmc /dev/block/mmcblk0p10
/bootloader emmc /dev/block/mmcblk0p5
/modem emmc /dev/block/mmcblk0p8
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/preload ext4 /dev/block/mmcblk0p16
/custom ext4 /dev/block/mmcblk0p12

Invalid argument error when mounting /dev/block/sda1

I'm trying to follow this post: https://forum.xda-developers.com/showpost.php?p=59166089&postcount=124 to try to get link2sd up and running, I've followed the instructions until I encountered an issue:
mount -t ext4 /dev/block/sda1 /storage/usb
mount: '/dev/block/sda1'->'/storage/usb': Invalid argument
Click to expand...
Click to collapse
The device's name is valid, I've even tried umounting the usb drive in /storage, but it still gives me that error. Have I missed something? The post is quite old and some things might have changed since then.

/system/bin/mount -t ext4 /dev/block/sda1 /storage/usb

Child's Play said:
/system/bin/mount -t ext4 /dev/block/sda1 /storage/usb
Click to expand...
Click to collapse
same thing. I've run fsck on the usb drive, just to be sure, but it seems to work perfectly well.

dictorclef said:
same thing. I've run fsck on the usb drive, just to be sure, but it seems to work perfectly well.
Click to expand...
Click to collapse
Do
ls -l /dev/block/sda1
ls -l /storage/usb
to make sure both exist.

dcarvil said:
Do
ls -l /dev/block/sda1
ls -l /storage/usb
to make sure both exist.
Click to expand...
Click to collapse
they do
ls -l /dev/block/sda1
brw------- 1 root root 8, 1 1969-12-31 19:00 /dev/block/sda1
ls -l /storage/usb
total 0
Click to expand...
Click to collapse

Should have tried this already:
/system/bin/mount -vt ext4 /dev/block/sda1 /storage/usb
mount: '/dev/block/sda1'->'/storage/usb': Invalid argument
try '/dev/block/sda1' type 'ext4' on '/storage/usb'
Click to expand...
Click to collapse
It's as if it doesn't see ext4 in the command. I wonder if it could be a bug with this magisk module? https://forum.xda-developers.com/fire-tv/development/magisk-amazon-firetv4k-ntfs-f2fs-ext4-t3991981

dictorclef said:
Should have tried this already:
It's as if it doesn't see ext4 in the command. I wonder if it could be a bug with this magisk module? https://forum.xda-developers.com/fire-tv/development/magisk-amazon-firetv4k-ntfs-f2fs-ext4-t3991981
Click to expand...
Click to collapse
Did you read note 3 at that link?
"Note 3: Some EXT4 drives may fail to mount,most likely this is because e2fsck it's failing to check for errors. In the next version i will try to add a newer version of e2fsck.However, formatting to EXT4 directly on the device will fix the issue."
You can do "cat /proc/filesystems" to make sure you have ext4 support (should NOT have "nodev" before ext4), but you still may need to format the USB drive on your firestick.

dcarvil said:
Did you read note 3 at that link?
"Note 3: Some EXT4 drives may fail to mount,most likely this is because e2fsck it's failing to check for errors. In the next version i will try to add a newer version of e2fsck.However, formatting to EXT4 directly on the device will fix the issue."
You can do "cat /proc/filesystems" to make sure you have ext4 support (should NOT have "nodev" before ext4), but you still may need to format the USB drive on your firestick.
Click to expand...
Click to collapse
Device does have ext4 support:
cat /proc/filesystems
nodev sysfs
nodev rootfs
nodev ramfs
nodev bdev
nodev proc
nodev cgroup
nodev tmpfs
nodev configfs
nodev debugfs
nodev tracefs
nodev sockfs
nodev pipefs
nodev devpts
ext3
ext2
ext4
vfat
msdos
iso9660
fuseblk
nodev fuse
nodev fusectl
nodev selinuxfs
nodev functionfs
Click to expand...
Click to collapse
And I did try to format the drive using aparted on my firestick, still no luck.

I think I might actually be an idiot, /dev/block/sda1 was already mounted to /mnt/media_rw/[a bunch of numbers and letters]. Unmounted it and it will now mount where I want. Link2sd detects the partition just fine.