Database Users

[Q] Default CWM Compatible Zip

Has anybody got a default, empty, Nook compatible .zip I can work with?
By this I mean an updater.script with all the mounting block commands etc that I can modify.
Im working on a few things at the mo and struggle with little things like mounting commands
Once /system, /data and /sdcard are mounted properly Im ok with the scripting.
Or, alternatively, once rooted with NookManager, is busybox installed? I can work with busybox
Bear with me Im a NookNoob and still reading, NookST arrived yesterday and dived right in
:edit:
Ok, so Ive found these so far:
0 /tmp ramdisk (null) (null)
1 /boot vfat /dev/block/mmcblk0p1 (null)
2 /system ext2 /dev/block/mmcblk0p5 (null)
3 /cache ext3 /dev/block/mmcblk0p7 (null)
4 /data ext3 /dev/block/mmcblk0p8 (null)
5 /emmc vfat /dev/block/mmcblk0p6 (null)
6 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
7 /sd-ext ext3 /dev/block/mmcblk1p2 (null)
Could someone confirm they are right?

[Q] Have IMEI, SN, and I can backup /EFS. Still unable to mount /EFS (With CWM log)

Greetings,
Title says all, I'm posting the log from CWM.
I tried flashing lots of fw's. And this fix(http://forum.xda-developers.com/showthread.php?t=2507403)
before and after factory reset, removing battery between. Out of clues
Nothing seems to be working for me. Since I first flashed a ROM I could never get network/lockscreen back
Can anyone help me find whats happening with my device?
Starting recovery on Thu Jan 8 23:58:37 1970
framebuffer: fd 4 (1080 x 1920)
min_x_swipe_px=240,min_y_swipe_px=120
CWM-based Recovery v6.0.4.5
Compiled by Xiaolu(20131122)
rm: can't remove '/system/recovery-from-boot.p': No such file or directory
Swipe up/down to change selections.
Swipe to the right for enter.
Swipe to the left for back.
recovery filesystem table
=========================
0 /boot emmc /dev/block/platform/msm_sdcc.1/by-name/boot 0
1 /recovery emmc /dev/block/platform/msm_sdcc.1/by-name/recovery 0
2 /system ext4 /dev/block/platform/msm_sdcc.1/by-name/system 0
3 /data ext4 /dev/block/platform/msm_sdcc.1/by-name/userdata 0
4 /cache ext4 /dev/block/platform/msm_sdcc.1/by-name/cache 0
5 /efs ext4 /dev/block/platform/msm_sdcc.1/by-name/efs 0
6 /sdcard datamedia /dev/null 0
7 /external_sd auto /dev/block/mmcblk1 0
8 /storage/usbdisk1 auto /dev/block/sda 0
9 /storage/usbdisk2 auto /dev/block/sdb 0
10 /tmp ramdisk ramdisk 0
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /emmc during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
W:Unable to get recovery.fstab info for /preload during fstab generation!
I:Completed outputting fstab.
I:Connected to Vold..
I:110 0 sdcard /external_sd 0
I:110 0 sda /storage/usbdisk1 0
I:110 0 sdb /storage/usbdisk2 0
I:200 0 Volumes listed.
Irocessing arguments.
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
...
...
...
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
mount: mounting /dev/block/platform/msm_sdcc.1/by-name/efs on /efs failed: Invalid argument
W:failed to mount /dev/block/platform/msm_sdcc.1/by-name/efs (File exists)
Error mounting /efs!
mount: mounting /dev/block/platform/msm_sdcc.1/by-name/efs on /efs failed: Invalid argument
W:failed to mount /dev/block/platform/msm_sdcc.1/by-name/efs (File exists)
Error mounting /efs!
I:using /data/media/0 for /sdcard.
Any clues?

Install busybox to get EFS back via CWM.
user @brockyneo had the same issue a few days ago, couldn't restore EFS until he installed busybox
http://forum.xda-developers.com/showthread.php?t=2546724&page=3
It may help with the lockscreen issue.

radicalisto said:
Install busybox to get EFS back via CWM.
user @brockyneo had the same issue a few days ago, couldn't restore EFS until he installed busybox
http://forum.xda-developers.com/showthread.php?t=2546724&page=3
It may help with the lockscreen issue.
Click to expand...
Click to collapse
Thanks a lot, I have asked brock for more detailed information about his solution. I hate messing with EFS, before I restore I want to make one more backup via terminal, I don't know exactly if he did the backup via terminal in his case.

I fixed my phone after one sad week of no networks! I'm so happy!
I used the batch script to restore my EFS via ODIN. and in CWM i was able to mouunt /efs.
Then I did a reset flashed clean ROM and it showed the SIM dialog and lockscreen started to work.
Thanks a lot!

[Q] CWM can't boot it's nandroid backup

Hi Guys,
I'm using CWM v6.0.4.3 on my Grouper, and just made a nandroid with it of CM 12. Now the strange thing is that when restoring to this nandroid, it boots back to CWM Recovery. A nandroid I made from CM 11 boots fine however. Looks like something broke, CWM 6.0.4.3. isn't able to backup/restore CM 12? By the way, did all factory reset/cache/dalvik, etc. No error messages, except what I've found in the log below when making the backup.
Any ideas what causes this, or similar issues encountered? I'm opting to use TWRP, just checked that at least it's restoring CM 11 and 12 fine.
For those interested, here the log CWM made without individual file info:
Code:
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
Starting recovery on Mon Aug 3 14:21:31 2015
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (800 x 1280)
ClockworkMod Recovery v6.0.4.3
recovery filesystem table
=========================
0 /system ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP 0
1 /cache ext4 /dev/block/platform/sdhci-tegra.3/by-name/CAC 0
2 /data ext4 /dev/block/platform/sdhci-tegra.3/by-name/UDA 0
3 /misc emmc /dev/block/platform/sdhci-tegra.3/by-name/MSC 0
4 /boot emmc /dev/block/platform/sdhci-tegra.3/by-name/LNX 0
5 /recovery emmc /dev/block/platform/sdhci-tegra.3/by-name/SOS 0
6 /staging emmc /dev/block/platform/sdhci-tegra.3/by-name/USP 0
7 /storage/usbdisk vfat /devices/platform/tegra-ehci 0
8 /tmp ramdisk ramdisk 0
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /emmc during fstab generation!
W:Unable to get recovery.fstab info for /sdcard during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
W:Unable to get recovery.fstab info for /external_sd during fstab generation!
I:Completed outputting fstab.
I:Connected to Vold..
I:110 0 usbdisk /storage/usbdisk 0
I:200 0 Volumes listed.
I:Processing arguments.
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
...
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
I:using /data/media for /sdcard.
I:using /data/media for /sdcard/clockworkmod/backup/2015-08-03.14.21.48.
SD Card space free: 19236MB
Backing up boot image...
Backup of boot image completed.
Backing up recovery image...
Backup of recovery image completed.
Backing up system...
...
Backup of system completed.
Backing up data...
...
Backup of data completed.
No .android_secure found. Skipping backup of applications on external storage.
Backing up cache...
Backup of cache completed.
I:No sd-ext found. Skipping backup of sd-ext.
Generating md5 sum...

A500 dead internal SD card?

Hi guys, I'm a new poster but long time reader of these boards, which helped me a lot since I got my A500 and an Android phone years ago. So far I've always found a ready solution for my 'droid needs and wants here but this time I think I've hit a bricked (tablet) wall! :laugh::crying:
My A500 has Skrilax_CZ's bootloader v9 with CWM v6.0.4.5 on the secondary partition and for more than a year has been running HenrikE's Android 4.4.4 (OmniROM unofficial) from this thread: http://forum.xda-developers.com/showthread.php?t=2705989 The ROM has been going fine apart from a few random freezes but overall I like it.
Yesterday I was using the tablet to read a book and it started running Play store auto updates, I went to look at the store app to check which apps etc, then switched back to my book and the tablet froze. Normally I'd just long press the power button and then press it again to turn it on, so I did, only this time the ROM would not boot anymore and the tablet got stuck at the bootloader screen. I went into recovery and wiped cache and dalvik, no change. I went back to recovery and then I realized the partitions aren't mounting nor can be formatted! /system, /data, /cache, nothing:
E: format_volume: make_extf4fs failed on /dev/block/mmcblk0p3
Without much hope I reinstalled the ROM with a data/factory reset and that of course didn't fix it. Tried to erase userdata and cache with fastboot, no change. It looks like either my internal SD card is broken/not found or my partitions are horribly corrupted? mmcblk0 isn't showing on /dev, see below from adb shell:
/dev/block # ls
loop0 loop2 loop4 loop6 mmcblk0p5 zram0
loop1 loop3 loop5 loop7 vold
/dev/block # fdisk /dev/block/mmcblk0
fdisk: can't open '/dev/block/mmcblk0'
/dev/block # parted
Error: No device found
Retry/Cancel? c
c
/dev/block #
/etc # cat fstab
/dev/block/mmcblk0p4 /cache ext4 rw
/dev/block/mmcblk0p8 /data ext4 rw
/dev/block/mmcblk0p3 /system ext4 rw
/etc # mount -t ext4 /dev/block/mmcblk0p8 /data
mount: mounting /dev/block/mmcblk0p8 on /data failed: No such file or directory
/etc #
Looking at other threads I guess the next step would be to try an APX reinstall however I use Linux and don't have a Windows machine around. While I can certainly spend my Easter break setting up a Windows Virtualbox :crying: do you guys think this is a hardware fault or something that can be fixed? Many thanks for any input. Oh and yeah I do have the tablet's SBK number.
Edit:
I forgot to paste this:
/etc # cat recovery.fstab
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/dev/block/mmcblk0p3 /system ext4 ro,noatime wait
/dev/block/mmcblk0p4 /cache ext4 noatime,nosuid,nodev,errors=panic wait,check
/dev/block/mmcblk0p8 /data ext4 noatime,nosuid,nodev,errors=panic,discard,noauto_da_alloc wait,check
/dev/block/mmcblk0p2 /boot emmc defaults recoveryonly
/dev/block/mmcblk0p1 /recovery emmc defaults recoveryonly
/dev/block/mmcblk0p5 /misc emmc defaults recoveryonly
/dev/block/mmcblk0p3 /system ext4 defaults recoveryonly
/dev/block/mmcblk0p4 /cache ext4 defaults recoveryonly
/dev/block/mmcblk0p6 /flexrom ext4 defaults recoveryonly
/dev/block/mmcblk0p8 /data auto defaults recoveryonly
/dev/block/mmcblk1p1 /mnt/sdcard vfat defaults recoveryonly
# vold-managed volumes ("block device" is actually a sysfs devpath)
/devices/platform/sdhci-tegra.2/mmc_host/mmc1 /storage/sdcard1 auto defaults voldmanaged=sdcard:auto
/devices/platform/tegra-ehci.2 /storage/usbdisk0 auto defaults voldmanaged=sda:auto
/etc #

Hi all, I've narrowed it down to a bad sector on the tablet's internal storage and posted on this older thread about the same problem http://forum.xda-developers.com/showthread.php?t=1691729&page=5

i-tec USBOTG device with HDMI and storage devices (SCSI HDD/SSD, SDcard, USB-3 + USB-C connector)

Hi everybody,
I am looking for ways to mount storage devices with more than one partitions via usbotg and my i-tec 'docking station'.
That worked on my old MOTO G5 on LINEAGEOS17.1 with an USB Stick for vfat and ext4 partitions out of the box, but the luks partitions were not mounted.
WIth my LGV20 and LINEAGEOS18.1 only the first partitions are showing up. The 2nd and 3rd partition are not mounted.
-> I would like to mount an USB Stick with vfat, ext4 (boot) and a luks partition.
-> I would like to mount an HDD with a vfat and luks partition
I somehow feel and know that this should be an easy task, if you know how to mount partitions in android.
I am thinking about trying to mount the partitions in the TWRP terminal and then copy the command in /fstab.elsa
/fstab.elsa content:
# Android fstab file.
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
#TODO: Add 'check' as fs_mgr_flags with data partition.
# Currently we dont have e2fsck compiled. So fs check would failed.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
/dev/block/bootdevice/by-name/boot /boot emmc defaults recoveryonly
/dev/block/bootdevice/by-name/recovery /recovery emmc defaults recoveryonly
/dev/block/bootdevice/by-name/system /system ext4 ro,barrier=1,noatime wait
/dev/block/bootdevice/by-name/userdata /data ext4 discard,nosuid,nodev,barrier=1,noatime,noauto_da_alloc,errors=continue wait,check,encryptable=/dev/block/bootdevice/by-name/encrypt
/dev/block/bootdevice/by-name/cache /cache ext4 discard,nosuid,nodev,barrier=1,noatime,noauto_da_alloc,errors=continue wait,check
/dev/block/bootdevice/by-name/modem /firmware vfat ro,nosuid,nodev,context=u:object_r:firmware_file:s0 wait
/dev/block/bootdevice/by-name/misc /misc emmc defaults defaults
/devices/soc/74a4900.sdhci/mmc_host* auto auto nosuid,nodev wait,encryptable=/dev/block/bootdevice/by-name/encrypt
/devices/soc/6a00000.ssusb/6a00000.dwc3/xhci-hcd.0.auto/usb* auto auto defaults defaults
/devices/soc/6a00000.ssusb/6a00000.dwc3/xhci-hcd.1.auto/usb* auto auto defaults defaults
/dev/block/bootdevice/by-name/persist /persist ext4 nosuid,nodev,barrier=1,noatime,noauto_da_alloc,errors=continue wait
/etc/fstab content:
/dev/block/bootdevice/by-name/system /system_root ext4 rw 0 0
/dev/block/bootdevice/by-name/userdata /data ext4 rw 0 0
/dev/block/bootdevice/by-name/cache /cache ext4 rw 0 0
/dev/block/bootdevice/by-name/modem /firmware vfat rw 0 0
/dev/block/bootdevice/by-name/persist /persist ext4 rw 0 0
/external_sd vfat rw 0 0
/vendor ext4 rw 0 0
For the terminal mount /dev/sda1 didn't work.
Any ideas how I have to adress the USB device?