Related
Hi!
I have an Android 2.1 tablet model MID-7CS, and I have the following problem. It's compatible with the Huawei USB 3G stick. When I connect the stick to the USB port and make the 3G enable in settings it connects to network (I can see the signal bars and when I enter the APN I can see the 3G logo as well) but no data transfer. I open the browser or email client it cannot make any connection.
I used NE Debugger to see what could happen and seems like after authentication the modem hangup immediately?? I copy the log here:
Any suggestion?
Board: tcc8900_evm
Brand: telechips
Device: tcc8900
Build ID: MID-7CS 20110302 1299077295
Model: MID-7CS
Product: MID-7CS
Tags: test-keys
Release: 2.1-update1
SDK: 7
D/vold ( 825): MINOR=4
D/vold ( 825): No uevent handlers registered for 'usb_endpoint' subsystem
D/vold ( 825): [UEVENT] Sq: 979 S: usb_endpoint A: 0 P: /devices/platform/dwc_otg.0/usb2/2-1/2-1:1.0/usb_endpoint/usbdev2.5_ep82
D/vold ( 825): DEVPATH=/devices/platform/dwc_otg.0/usb2/2-1/2-1:1.0/usb_endpoint/usbdev2.5_ep82
D/vold ( 825): MAJOR=251
D/vold ( 825): MINOR=5
D/vold ( 825): No uevent handlers registered for 'usb_endpoint' subsystem
D/vold ( 825): [UEVENT] Sq: 980 S: usb_endpoint A: 0 P: /devices/platform/dwc_otg.0/usb2/2-1/2-1:1.0/usb_endpoint/usbdev2.5_ep01
D/vold ( 825): DEVPATH=/devices/platform/dwc_otg.0/usb2/2-1/2-1:1.0/usb_endpoint/usbdev2.5_ep01
D/vold ( 825): MAJOR=251
D/vold ( 825): MINOR=6
D/vold ( 825): No uevent handlers registered for 'usb_endpoint' subsystem
D/vold ( 825): [UEVENT] Sq: 981 S: usb A: 0 P: /devices/platform/dwc_otg.0/usb2/2-1/2-1:1.1
D/vold ( 825): DEVPATH=/devices/platform/dwc_otg.0/usb2/2-1/2-1:1.1
D/vold ( 825): DEVTYPE=usb_interface
D/vold ( 825): DEVICE=/proc/bus/usb/002/005
D/vold ( 825): PRODUCT=12d1/1003/0
D/vold ( 825): TYPE=0/0/0
D/vold ( 825): INTERFACE=255/255/255
D/vold ( 825): MODALIAS=usb:v12D1p1003d0000dc00dsc00dp00icFFiscFFipFF
D/vold ( 825): No uevent handlers registered for 'usb' subsystem
D/vold ( 825): [UEVENT] Sq: 982 S: usb-serial A: 0 P: /devices/platform/dwc_otg.0/usb2/2-1/2-1:1.1/ttyUSB1
D/vold ( 825): DEVPATH=/devices/platform/dwc_otg.0/usb2/2-1/2-1:1.1/ttyUSB1
D/vold ( 825): No uevent handlers registered for 'usb-serial' subsystem
D/vold ( 825): [UEVENT] Sq: 983 S: tty A: 0 P: /devices/platform/dwc_otg.0/usb2/2-1/2-1:1.1/ttyUSB1/tty/ttyUSB1
D/vold ( 825): DEVPATH=/devices/platform/dwc_otg.0/usb2/2-1/2-1:1.1/ttyUSB1/tty/ttyUSB1
D/vold ( 825): MAJOR=188
D/vold ( 825): MINOR=1
D/vold ( 825): No uevent handlers registered for 'tty' subsystem
D/vold ( 825): [UEVENT] Sq: 984 S: usb_endpoint A: 0 P: /devices/platform/dwc_otg.0/usb2/2-1/2-1:1.1/usb_endpoint/usbdev2.5_ep83
D/vold ( 825): DEVPATH=/devices/platform/dwc_otg.0/usb2/2-1/2-1:1.1/usb_endpoint/usbdev2.5_ep83
D/vold ( 825): MAJOR=251
D/vold ( 825): MINOR=7
D/vold ( 825): No uevent handlers registered for 'usb_endpoint' subsystem
D/vold ( 825): [UEVENT] Sq: 985 S: usb_endpoint A: 0 P: /devices/platform/dwc_otg.0/usb2/2-1/2-1:1.1/usb_endpoint/usbdev2.5_ep02
D/vold ( 825): DEVPATH=/devices/platform/dwc_otg.0/usb2/2-1/2-1:1.1/usb_endpoint/usbdev2.5_ep02
D/vold ( 825): MAJOR=251
D/vold ( 825): MINOR=8
D/vold ( 825): No uevent handlers registered for 'usb_endpoint' subsystem
D/vold ( 825): [UEVENT] Sq: 986 S: usb A: 0 P: /devices/platform/dwc_otg.0/usb2/2-1/2-1:1.2
D/vold ( 825): DEVPATH=/devices/platform/dwc_otg.0/usb2/2-1/2-1:1.2
D/vold ( 825): DEVTYPE=usb_interface
D/vold ( 825): DEVICE=/proc/bus/usb/002/005
D/vold ( 825): PRODUCT=12d1/1003/0
D/vold ( 825): TYPE=0/0/0
D/vold ( 825): INTERFACE=8/6/80
D/vold ( 825): MODALIAS=usb:v12D1p1003d0000dc00dsc00dp00ic08isc06ip50
D/vold ( 825): No uevent handlers registered for 'usb' subsystem
D/vold ( 825): [UEVENT] Sq: 987 S: usb_endpoint A: 0 P: /devices/platform/dwc_otg.0/usb2/2-1/2-1:1.2/usb_endpoint/usbdev2.5_ep84
D/vold ( 825): DEVPATH=/devices/platform/dwc_otg.0/usb2/2-1/2-1:1.2/usb_endpoint/usbdev2.5_ep84
D/vold ( 825): MAJOR=251
D/vold ( 825): MINOR=9
D/vold ( 825): No uevent handlers registered for 'usb_endpoint' subsystem
D/vold ( 825): [UEVENT] Sq: 988 S: usb_endpoint A: 0 P: /devices/platform/dwc_otg.0/usb2/2-1/2-1:1.2/usb_endpoint/usbdev2.5_ep03
D/vold ( 825): DEVPATH=/devices/platform/dwc_otg.0/usb2/2-1/2-1:1.2/usb_endpoint/usbdev2.5_ep03
D/vold ( 825): MAJOR=251
D/vold ( 825): MINOR=10
D/vold ( 825): No uevent handlers registered for 'usb_endpoint' subsystem
D/vold ( 825): [UEVENT] Sq: 989 S: usb A: 0 P: /devices/platform/dwc_otg.0/usb2/2-1/2-1:1.3
D/vold ( 825): DEVPATH=/devices/platform/dwc_otg.0/usb2/2-1/2-1:1.3
D/vold ( 825): DEVTYPE=usb_interface
D/vold ( 825): DEVICE=/proc/bus/usb/002/005
D/vold ( 825): PRODUCT=12d1/1003/0
D/vold ( 825): TYPE=0/0/0
D/vold ( 825): INTERFACE=8/6/80
D/vold ( 825): MODALIAS=usb:v12D1p1003d0000dc00dsc00dp00ic08isc06ip50
D/vold ( 825): No uevent handlers registered for 'usb' subsystem
D/vold ( 825): [UEVENT] Sq: 990 S: usb_endpoint A: 0 P: /devices/platform/dwc_otg.0/usb2/2-1/2-1:1.3/usb_endpoint/usbdev2.5_ep04
D/vold ( 825): DEVPATH=/devices/platform/dwc_otg.0/usb2/2-1/2-1:1.3/usb_endpoint/usbdev2.5_ep04
D/vold ( 825): MAJOR=251
D/vold ( 825): MINOR=11
D/vold ( 825): No uevent handlers registered for 'usb_endpoint' subsystem
D/vold ( 825): [UEVENT] Sq: 991 S: usb_endpoint A: 0 P: /devices/platform/dwc_otg.0/usb2/2-1/2-1:1.3/usb_endpoint/usbdev2.5_ep85
D/vold ( 825): DEVPATH=/devices/platform/dwc_otg.0/usb2/2-1/2-1:1.3/usb_endpoint/usbdev2.5_ep85
D/vold ( 825): MAJOR=251
D/vold ( 825): MINOR=12
D/vold ( 825): No uevent handlers registered for 'usb_endpoint' subsystem
D/vold ( 825): [UEVENT] Sq: 992 S: usb_device A: 0 P: /devices/platform/dwc_otg.0/usb2/2-1/usb_device/usbdev2.5
D/vold ( 825): DEVPATH=/devices/platform/dwc_otg.0/usb2/2-1/usb_device/usbdev2.5
D/vold ( 825): MAJOR=189
D/vold ( 825): MINOR=132
D/vold ( 825): No uevent handlers registered for 'usb_device' subsystem
D/vold ( 825): [UEVENT] Sq: 993 S: usb_endpoint A: 0 P: /devices/platform/dwc_otg.0/usb2/2-1/usb_endpoint/usbdev2.5_ep00
D/vold ( 825): DEVPATH=/devices/platform/dwc_otg.0/usb2/2-1/usb_endpoint/usbdev2.5_ep00
D/vold ( 825): MAJOR=251
D/vold ( 825): MINOR=13
D/vold ( 825): No uevent handlers registered for 'usb_endpoint' subsystem
I/ActivityManager( 900): Start proc com.android.vending for broadcast com.android.vending/.DeviceConfigurationReceiver: pid=1745 uid=10027 gids={3003}
D/MccTable( 956): updateMccMncConfiguration: mcc=216, mnc=30
D/MccTable( 956): locale set to null_hu
D/NetworkLocationProvider( 900): onCellLocationChanged [1200,35251]
D/TelephonyProvider( 956): Setting numeric '21630' to be the current operator
I/WindowManager( 900): Setting rotation to 0, animFlags=0
I/ActivityManager( 900): Config changed: { scale=1.0 imsi=216/30 loc=en_US touch=3 keys=1/1/2 nav=1/1 orien=2 layout=268435490}
I/ASK_KF ( 1151): Creating keyboards. I have 7 creators
I/UsageStats( 900): Unexpected resume of com.android.settings while already resumed in com.android.settings
D/G3ModeEnabler( 1493): ------------------------datastate changed ---------------------------1
D/G3ModeEnabler( 1493): ------------------------datastate changed ---------------------------1
D/G3ModeEnabler( 1493): ------------------------datastate changed ---------------------------1
D/G3ModeEnabler( 1493): ------------------------datastate changed ---------------------------1
D/SettingsWifiEnabler( 1493): Received wifi state changed from Disabling to Disabled
I/ActivityThread( 1745): Publishing provider com.android.vending.SuggestionsProvider: com.android.vending.SuggestionsProvider
D/NetworkLocationProvider( 900): onDataConnectionStateChanged 3
D/MobileDataStateTracker( 900): default Received state= CONNECTING, old= DISCONNECTED, reason= simLoaded, apnTypeList= *
D/NetworkStateTracker( 900): setDetailed state, old =DISCONNECTED and new state=CONNECTING
D/ConnectivityService( 900): ConnectivityChange for MOBILE: CONNECTING/CONNECTING
D/vending ( 1745): [1] VendingApplication.onCreate(): Resetting ServiceLocator from app
I/WindowManager( 900): Setting rotation to 3, animFlags=0
I/ActivityManager( 900): Config changed: { scale=1.0 imsi=216/30 loc=en_US touch=3 keys=1/1/2 nav=1/1 orien=1 layout=268435490}
I/UsageStats( 900): Unexpected resume of com.android.settings while already resumed in com.android.settings
I/ASK_KF ( 1151): Creating keyboards. I have 7 creators
D/vending ( 1745): [9] 1.run(): Clearing cache in response to android.intent.action.SIM_STATE_CHANGED
D/vending ( 1745): [10] 1.run(): Clearing cache in response to android.intent.action.SIM_STATE_CHANGED
D/vending ( 1745): [11] 1.run(): Clearing cache in response to android.intent.action.SIM_STATE_CHANGED
D/G3ModeEnabler( 1493): ------------------------datastate changed ---------------------------1
D/SettingsWifiEnabler( 1493): Received wifi state changed from Disabling to Disabled
I/pppd ( 1758): Serial connection established.
D/pppd ( 1758): using channel 3
D/vold ( 825): [UEVENT] Sq: 994 S: net A: 0 P: /devices/virtual/net/ppp0
D/vold ( 825): DEVPATH=/devices/virtual/net/ppp0
D/vold ( 825): INTERFACE=ppp0
D/vold ( 825): IFINDEX=6
D/vold ( 825): No uevent handlers registered for 'net' subsystem
I/pppd ( 1758): Using interface ppp0
I/pppd ( 1758): Connect: ppp0 <--> /dev/ttyUSB0
D/G3ModeEnabler( 1493): ------------------------datastate changed ---------------------------2
D/G3ModeEnabler( 1493): ------------------------datastate changed ---------------------------2
D/G3ModeEnabler( 1493): ------------------------datastate changed ---------------------------2
D/NetworkLocationProvider( 900): onDataConnectionStateChanged 3
D/G3ModeEnabler( 1493): ------------------------datastate changed ---------------------------2
D/G3ModeEnabler( 1493): ------------------------datastate changed ---------------------------2
D/MobileDataStateTracker( 900): default Received state= CONNECTED, old= CONNECTING, reason= simLoaded, apnTypeList= *
D/NetworkStateTracker( 900): setDetailed state, old =CONNECTING and new state=CONNECTED
D/ConnectivityService( 900): ConnectivityChange for MOBILE: CONNECTED/CONNECTED
D/MobileDataStateTracker( 900): replacing old mInterfaceName (gprs) with gprs for mms
D/MobileDataStateTracker( 900): replacing old mInterfaceName (gprs) with gprs for supl
D/MobileDataStateTracker( 900): replacing old mInterfaceName (gprs) with gprs for dun
D/MobileDataStateTracker( 900): replacing old mInterfaceName (gprs) with gprs for hipri
D/ConnectivityService( 900): erasing net.dns1
D/GpsLocationProvider( 900): updateNetworkState available info: NetworkInfo: type: MOBILE[UMTS], state: CONNECTED/CONNECTED, reason: simLoaded, extra: internet, roaming: false, failover: false, isAvailable: true
D/GpsLocationProvider( 900): NetworkThread wait for 9223372036854775807ms
I/MediaUploader( 1539): No need to wake up
D/pppd ( 1758): sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0x8ea85936> <pcomp> <accomp>]
D/pppd ( 1758): rcvd [LCP ConfReq id=0x0 <asyncmap 0x0> <auth chap MD5> <magic 0xf50f8e> <pcomp> <accomp>]
D/pppd ( 1758): sent [LCP ConfAck id=0x0 <asyncmap 0x0> <auth chap MD5> <magic 0xf50f8e> <pcomp> <accomp>]
D/pppd ( 1758): rcvd [LCP ConfAck id=0x1 <asyncmap 0x0> <magic 0x8ea85936> <pcomp> <accomp>]
D/pppd ( 1758): rcvd [LCP DiscReq id=0x1 magic=0xf50f8e]
D/pppd ( 1758): rcvd [CHAP Challenge id=0x1 <d278847ee263182b88a0454edc682ebd>, name = "UMTS_CHAP_SRVR"]
D/pppd ( 1758): sent [CHAP Response id=0x1 <82410fe241475112f2ef3fbd17e97688>, name = "any"]
D/pppd ( 1758): rcvd [CHAP Success id=0x1 ""]
I/pppd ( 1758): CHAP authentication succeeded
D/pppd ( 1758): sent [CCP ConfReq id=0x1 <deflate 15> <deflate(old#) 15> <bsd v1 15>]
D/pppd ( 1758): sent [IPCP ConfReq id=0x1 <compress VJ 0f 01> <addr 0.0.0.0> <ms-dns1 0.0.0.0> <ms-dns3 0.0.0.0>]
D/pppd ( 1758): rcvd [LCP ProtRej id=0x2 80 fd 01 01 00 0f 1a 04 78 00 18 04 78 00 15 03 2f]
D/pppd ( 1758): rcvd [IPCP ConfNak id=0x1 <ms-dns1 10.11.12.13> <ms-dns3 10.11.12.14> <ms-wins 10.11.12.13> <ms-wins 10.11.12.14>]
D/pppd ( 1758): sent [IPCP ConfReq id=0x2 <compress VJ 0f 01> <addr 0.0.0.0> <ms-dns1 10.11.12.13> <ms-dns3 10.11.12.14>]
D/pppd ( 1758): rcvd [IPCP ConfNak id=0x2 <ms-dns1 10.11.12.13> <ms-dns3 10.11.12.14> <ms-wins 10.11.12.13> <ms-wins 10.11.12.14>]
D/pppd ( 1758): sent [IPCP ConfReq id=0x3 <compress VJ 0f 01> <addr 0.0.0.0> <ms-dns1 10.11.12.13> <ms-dns3 10.11.12.14>]
I/pppd ( 1758): Modem hangup
I/pppd ( 1758): Connection terminated.
D/vold ( 825): [UEVENT] Sq: 995 S: net A: 1 P: /devices/virtual/net/ppp0
D/vold ( 825): DEVPATH=/devices/virtual/net/ppp0
D/vold ( 825): INTERFACE=ppp0
D/vold ( 825): IFINDEX=6
D/vold ( 825): No uevent handlers registered for 'net' subsystem
I/ActivityManager( 900): Starting activity: Intent { act=android.intent.action.MAIN cat=[android.intent.category.HOME] flg=0x10200000 cmp=com.android.launcher/.Launcher }
I/ASK ( 1151): onUnbindInput
I/ActivityManager( 900): Starting activity: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.android.browser/.BrowserActivity bnds=[265,653][340,733] }
I/ActivityManager( 900): Start proc com.android.browser for activity com.android.browser/.BrowserActivity: pid=1773 uid=10012 gids={3003, 1015}
I/ActivityThread( 1773): Publishing provider browser: com.android.browser.BrowserProvider
Hello,
My ZT-282 Tablet is having some troubles booting. It started when trying to flash the latest rom (0327). The installation went fine in the sense there were not error messages during the installation.
Here is a video of the upgrade and the problem that follows:
http://dl.dropbox.com/u/165691/video-2012-04-08-19-13-46.mp4
As you can see it first shows a logo, flashes for a second then shows the logo a second time. After that it freezes. I have left it alone in this state for an hour, but nothing happens.
Here is a log that I got via adb from the tablet. Does it give any clues?
Code:
--------- beginning of /dev/log/main
I/DEBUG ( 79): debuggerd: Feb 9 2012 19:41:11
D/Memsicd ( 91): search aac sensor: MXC622X
D/Memsicd ( 91): aac sensor MXC622X[0] communicate success
I//system/bin/set_display_mode.sh( 73): 1024,1200
D/sslib ( 91): sslib: ss_config file read succeed
D/sslib ( 91): sslib: entering ss_load_module_raw
D/sslib ( 91): Loading module /system/lib/sslib/inputraw_ss.so
I/logwrapper( 73): /system/bin/set_display_mode.sh terminated by exit(0)
D/sslib ( 91): mod_init of input raw
--------- beginning of /dev/log/system
I/Vold ( 75): Vold 2.1 (the revenge) firing up
I/Netd ( 101): Netd 1.0 starting
D/Vold ( 75): Volume sdcard state changing -1 (Initializing) -> 0 (No-Media)
D/Vold ( 75): Volume flash state changing -1 (Initializing) -> 0 (No-Media)
E/Netd ( 101): Unable to create netlink socket: Protocol not supported
E/Netd ( 101): Unable to open quota2 logging socket
D/Vold ( 75): Volume flash state changing 0 (No-Media) -> 2 (Pending)
E/NetlinkEvent( 75): NetlinkEvent::FindParam(): Parameter 'NPARTS' not found
D/Vold ( 75): Volume flash state changing 2 (Pending) -> 1 (Idle-Unmounted)
D/Vold ( 75): Volume flash state changing 1 (Idle-Unmounted) -> 2 (Pending)
E/NetlinkEvent( 75): NetlinkEvent::FindParam(): Parameter 'NPARTS' not found
D/Vold ( 75): Volume flash state changing 2 (Pending) -> 1 (Idle-Unmounted)
I/Netd ( 135): Netd 1.0 starting
E/Netd ( 135): Unable to create netlink socket: Protocol not supported
E/Netd ( 135): Unable to open quota2 logging socket
I/Netd ( 163): Netd 1.0 starting
E/Netd ( 163): Unable to create netlink socket: Protocol not supported
E/Netd ( 163): Unable to open quota2 logging socket
I/Netd ( 191): Netd 1.0 starting
E/Netd ( 191): Unable to create netlink socket: Protocol not supported
E/Netd ( 191): Unable to open quota2 logging socket
I/Netd ( 219): Netd 1.0 starting
E/Netd ( 219): Unable to create netlink socket: Protocol not supported
E/Netd ( 219): Unable to open quota2 logging socket
The messages about not being able to create a netlink socket goes on forever after this.
I'm having the same issue, did you know how to solve it yet?
I have bricked EMMC chip on my HTC Desire S, but bootloader and recovery working in readonly mode. I created the partition table on the external memory card (Micro SD), similar to the structure of internal memory in the extended partition. I modified the init.saga.rc in boot.img for using new partitions on sdcard. After booting over fastboot, I got a working phone
But i need help to configure the phone to use the internal memory, 1st partition on sdcard mmcblk1p1(vold/179:65 - fat32) or /data partition for DCIM, Music and etc.
I see several solutions, but do not know how to do:
1. "/data" partition, like /data/Documents...
2. Automounting through DirectVolume manager 1st partion on sd
3. Mount through init.rc, but system cant find STORAGE
4. Make 2nd storage like PHONE_STORAGE/INTERNAL_STORAGE
5. ?????
Code:
# logcat | grep Vold
logcat | grep Vold
I/Vold ( 1217): Vold 2.1 (the revenge) firing up
D/Vold ( 1217): Volume sdcard state changing -1 (Initializing) -> 0 (No-Media
)
D/Vold ( 1217): Volume sdcard state changing 0 (No-Media) -> 2 (Pending)
D/Vold ( 1217): USB connected
D/Vold ( 1217): Share method ums now available
D/Vold ( 1217): USB connected
D/VoldCmdListener( 1217): volume list
D/VoldCmdListener( 1217): share status ums
Code:
# logcat | grep Volume
logcat | grep Volume
D/Vold ( 1217): Volume sdcard state changing -1 (Initializing) -> 0 (No-Media
)
D/Vold ( 1217): Volume sdcard state changing 0 (No-Media) -> 2 (Pending)
W/DirectVolume( 1217): Invalid 'PARTN' value
W/DirectVolume( 1217): Invalid 'PARTN' value
W/DirectVolume( 1217): Invalid 'PARTN' value
W/DirectVolume( 1217): Invalid 'PARTN' value
W/DirectVolume( 1217): Invalid 'PARTN' value
W/DirectVolume( 1217): Invalid 'PARTN' value
W/DirectVolume( 1217): Invalid 'PARTN' value
W/DirectVolume( 1217): Invalid 'PARTN' value
Code:
# logcat | grep Mount
I/SystemServer( 1332): Mount Service
D/MountService( 1332): got storage path: /mnt/sdcard description: USB storage pr
imary: true removable: true emulated: false mtpReserve: 0 allowMassStorage: true
maxFileSize: 4294967296
E/MountService( 1332): Error processing initial volume state
E/MountService( 1332): java.lang.Exception: Unexpected state 2
E/MountService( 1332): at com.android.server.MountService$2.run(MountService.ja
va:656)
D/MountService( 1332): volume state changed for /mnt/sdcard (null -> removed)
Code:
# mount
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)
none on /acct type cgroup (rw,relatime,cpuacct)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
tmpfs on /mnt/obb type tmpfs (rw,relatime,mode=755,gid=1000)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
/dev/block/mmcblk1p8 on /system type ext4 (ro,relatime,barrier=1,data=ordered)
/dev/block/mmcblk1p9 on /data type ext4 (rw,nosuid,nodev,noatime,barrier=1,data=
ordered,noauto_da_alloc)
/dev/block/mmcblk1p10 on /cache type ext4 (rw,nosuid,nodev,noatime,barrier=1,dat
a=ordered)
/dev/block/mmcblk1p11 on /devlog type ext2 (rw,nosuid,nodev,noatime,barrier=1,da
ta=writeback)
/sys/kernel/debug on /sys/kernel/debug type debugfs (rw,relatime)
Code:
# ls -l dev/block/vold
brw-rw---- 1 root root 179, 64 Jul 3 11:09 179:64
brw-rw---- 1 root root 179, 65 Jul 3 11:09 179:65
brw-rw---- 1 root root 179, 66 Jul 3 11:09 179:66
brw-rw---- 1 root root 179, 69 Jul 3 11:09 179:69
brw-rw---- 1 root root 179, 70 Jul 3 11:09 179:70
brw-rw---- 1 root root 179, 71 Jul 3 11:09 179:71
brw-rw---- 1 root root 179, 72 Jul 3 11:09 179:72
brw-rw---- 1 root root 179, 73 Jul 3 11:09 179:73
brw-rw---- 1 root root 179, 74 Jul 3 11:09 179:74
brw-rw---- 1 root root 179, 75 Jul 3 11:09 179:75
brw-rw---- 1 root root 179, 76 Jul 3 11:09 179:76
Code:
# cat /etc/vold.fstab
# Mounts the first usable partition of the specified device
dev_mount sdcard /mnt/sdcard auto /devices/platform/msm_sdcc.4/mmc_host/mmc2
PS: Manual mount
Code:
mount /dev/block/mmcblk1p1 /mnt/sdcard
working, but system applications still want to EXTERNAL_STORAGE.
kibril said:
I have bricked EMMC chip on my HTC Desire S, but bootloader and recovery working in readonly mode. I created the partition table on the external memory card (Micro SD), similar to the structure of internal memory in the extended partition. I modified the init.saga.rc in boot.img for using new partitions on sdcard. After booting over fastboot, I got a working phone
But i need help to configure the phone to use the internal memory, 1st partition on sdcard mmcblk1p1(vold/179:65 - fat32) or /data partition for DCIM, Music and etc.
I see several solutions, but do not know how to do:
1. "/data" partition, like /data/Documents...
2. Automounting through DirectVolume manager 1st partion on sd
3. Mount through init.rc, but system cant find STORAGE
4. Make 2nd storage like PHONE_STORAGE/INTERNAL_STORAGE
5. ?????
Code:
# logcat | grep Vold
logcat | grep Vold
I/Vold ( 1217): Vold 2.1 (the revenge) firing up
D/Vold ( 1217): Volume sdcard state changing -1 (Initializing) -> 0 (No-Media
)
D/Vold ( 1217): Volume sdcard state changing 0 (No-Media) -> 2 (Pending)
D/Vold ( 1217): USB connected
D/Vold ( 1217): Share method ums now available
D/Vold ( 1217): USB connected
D/VoldCmdListener( 1217): volume list
D/VoldCmdListener( 1217): share status ums
Code:
# logcat | grep Volume
logcat | grep Volume
D/Vold ( 1217): Volume sdcard state changing -1 (Initializing) -> 0 (No-Media
)
D/Vold ( 1217): Volume sdcard state changing 0 (No-Media) -> 2 (Pending)
W/DirectVolume( 1217): Invalid 'PARTN' value
W/DirectVolume( 1217): Invalid 'PARTN' value
W/DirectVolume( 1217): Invalid 'PARTN' value
W/DirectVolume( 1217): Invalid 'PARTN' value
W/DirectVolume( 1217): Invalid 'PARTN' value
W/DirectVolume( 1217): Invalid 'PARTN' value
W/DirectVolume( 1217): Invalid 'PARTN' value
W/DirectVolume( 1217): Invalid 'PARTN' value
Code:
# logcat | grep Mount
I/SystemServer( 1332): Mount Service
D/MountService( 1332): got storage path: /mnt/sdcard description: USB storage pr
imary: true removable: true emulated: false mtpReserve: 0 allowMassStorage: true
maxFileSize: 4294967296
E/MountService( 1332): Error processing initial volume state
E/MountService( 1332): java.lang.Exception: Unexpected state 2
E/MountService( 1332): at com.android.server.MountService$2.run(MountService.ja
va:656)
D/MountService( 1332): volume state changed for /mnt/sdcard (null -> removed)
Code:
# mount
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)
none on /acct type cgroup (rw,relatime,cpuacct)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
tmpfs on /mnt/obb type tmpfs (rw,relatime,mode=755,gid=1000)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
/dev/block/mmcblk1p8 on /system type ext4 (ro,relatime,barrier=1,data=ordered)
/dev/block/mmcblk1p9 on /data type ext4 (rw,nosuid,nodev,noatime,barrier=1,data=
ordered,noauto_da_alloc)
/dev/block/mmcblk1p10 on /cache type ext4 (rw,nosuid,nodev,noatime,barrier=1,dat
a=ordered)
/dev/block/mmcblk1p11 on /devlog type ext2 (rw,nosuid,nodev,noatime,barrier=1,da
ta=writeback)
/sys/kernel/debug on /sys/kernel/debug type debugfs (rw,relatime)
Code:
# ls -l dev/block/vold
brw-rw---- 1 root root 179, 64 Jul 3 11:09 179:64
brw-rw---- 1 root root 179, 65 Jul 3 11:09 179:65
brw-rw---- 1 root root 179, 66 Jul 3 11:09 179:66
brw-rw---- 1 root root 179, 69 Jul 3 11:09 179:69
brw-rw---- 1 root root 179, 70 Jul 3 11:09 179:70
brw-rw---- 1 root root 179, 71 Jul 3 11:09 179:71
brw-rw---- 1 root root 179, 72 Jul 3 11:09 179:72
brw-rw---- 1 root root 179, 73 Jul 3 11:09 179:73
brw-rw---- 1 root root 179, 74 Jul 3 11:09 179:74
brw-rw---- 1 root root 179, 75 Jul 3 11:09 179:75
brw-rw---- 1 root root 179, 76 Jul 3 11:09 179:76
Code:
# cat /etc/vold.fstab
# Mounts the first usable partition of the specified device
dev_mount sdcard /mnt/sdcard auto /devices/platform/msm_sdcc.4/mmc_host/mmc2
PS: Manual mount
Code:
mount /dev/block/mmcblk1p1 /mnt/sdcard
working, but system applications still want to EXTERNAL_STORAGE.
Click to expand...
Click to collapse
hey, hey,,,, can u pls describe the following:
"I created
the partition table on the external
memory card (Micro SD), similar to
the structure of internal memory in
the extended partition. "
u r my new hope. I really need this. pls pls...can u put some attachments to help me??
All done, thanks for replays!
I'll build images ROM(CM7) on the weekend.
I'm very interested on this, same situation here, fried emmc chip but recovery and boot still workin on ro mode. I've been trying with fastboot for a while but all I can do is boot with a different recovery image.
Keep on this and please share all you can
Usb mass storage
Now from unresolved problems remained automounting via usb fat32 partition, ill try fix this.
PS: Somebody can up my rating for developer part of forum?!))
You need another 4 posts to be able to post there.
[GUIDE] How to run SD version of CM7.1 on HTC Desire S (fried emmc chips too).
I published a complete guide in "Desire S General":
http://forum.xda-developers.com/showthread.php?t=1756287
Logcat:
Code:
I/Vold ( 103): Vold 2.1 (the revenge) firing up
D/Vold ( 103): Volume sdcard0 state changing -1 (Initializing) -> 0 (No-Media)
D/Vold ( 103): Volume sdcard0 state changing 0 (No-Media) -> 2 (Pending)
D/DirectVolume( 103): DirectVolume::handlePartitionAdded -> MAJOR 179, MINOR 1, PARTN 1
D/DirectVolume( 103): DirectVolume::handlePartitionAdded -> MAJOR 179, MINOR 2, PARTN 2
D/Vold ( 103): Volume sdcard0 state changing 2 (Pending) -> 1 (Idle-Unmounted)
*snip*
D/DirectVolume( 103): Checking for bad partition major number
D/DirectVolume( 103): Checking for bad partition major number
I/Vold ( 103): /dev/block/vold/179:1 being considered for volume sdcard0
D/Vold ( 103): Volume sdcard0 state changing 1 (Idle-Unmounted) -> 3 (Checking)
D/Vold ( 103): Trying to get filesystem type for /dev/block/vold/179:1
D/MountService( 436): volume state changed for /storage/sdcard0 (unmounted -> checking)
D/MountService( 436): sendStorageIntent Intent { act=android.intent.action.MEDIA_CHECKING dat=file:///storage/sdcard0 (has extras) } to UserHandle{-1}
*snip*
D/Vold ( 103): Found vfat filesystem on /dev/block/vold/179:1
D/DirectVolume( 103): Volume sdcard0 /mnt/media_rw/sdcard0 partition 179:2 removed
D/DirectVolume( 103): Volume sdcard0 /mnt/media_rw/sdcard0 partition 179:1 removed
D/DirectVolume( 103): Volume sdcard0 /mnt/media_rw/sdcard0 disk 179:0 removed
D/Vold ( 103): Volume sdcard0 state changing 3 (Checking) -> 0 (No-Media)
V/KeyguardService( 525): onCreate()
I/fsck_msdos( 103): ** /dev/block/vold/179:1
I/fsck_msdos( 103): Can't open: No such device or address
I/fsck_msdos( 103): fsck_msdos terminated by exit(8)
E/Vold ( 103): Filesystem check failed (unknown exit code 8)
E/Vold ( 103): /dev/block/vold/179:1 failed FS checks (I/O error)
D/Vold ( 103): Volume sdcard0 state changing 0 (No-Media) -> 1 (Idle-Unmounted)
W/Vold ( 103): Returning OperationFailed - no handler for errno 0
D/MountService( 436): volume state changed for /storage/sdcard0 (checking -> unmounted)
I/PackageManager( 436): Updating external media status from unmounted to unmounted
D/MountService( 436): sendStorageIntent Intent { act=unmounted dat=file:///storage/sdcard0 (has extras) } to UserHandle{-1}
D/MountService( 436): volume state changed for /storage/sdcard0 (unmounted -> removed)
D/MountService( 436): sendStorageIntent Intent { act=android.intent.action.MEDIA_REMOVED dat=file:///storage/sdcard0 (has extras) } to UserHandle{-1}
E/VoldConnector( 436): NDC Command {3 volume mount /storage/sdcard0} took too long (3668ms)
E/MountService( 436): Boot-time mount failed (-1)
SD works in CM11 RC1, but not the weekly. The SD card is still found in recovery as well.
If I try and remove the SD card after it's booted it posts the "preparing SD card..." notification and then the "SD card safe to remove" notification.
forkbomb444 said:
Logcat:
Code:
I/Vold ( 103): Vold 2.1 (the revenge) firing up
D/Vold ( 103): Volume sdcard0 state changing -1 (Initializing) -> 0 (No-Media)
D/Vold ( 103): Volume sdcard0 state changing 0 (No-Media) -> 2 (Pending)
D/DirectVolume( 103): DirectVolume::handlePartitionAdded -> MAJOR 179, MINOR 1, PARTN 1
D/DirectVolume( 103): DirectVolume::handlePartitionAdded -> MAJOR 179, MINOR 2, PARTN 2
D/Vold ( 103): Volume sdcard0 state changing 2 (Pending) -> 1 (Idle-Unmounted)
*snip*
D/DirectVolume( 103): Checking for bad partition major number
D/DirectVolume( 103): Checking for bad partition major number
I/Vold ( 103): /dev/block/vold/179:1 being considered for volume sdcard0
D/Vold ( 103): Volume sdcard0 state changing 1 (Idle-Unmounted) -> 3 (Checking)
D/Vold ( 103): Trying to get filesystem type for /dev/block/vold/179:1
D/MountService( 436): volume state changed for /storage/sdcard0 (unmounted -> checking)
D/MountService( 436): sendStorageIntent Intent { act=android.intent.action.MEDIA_CHECKING dat=file:///storage/sdcard0 (has extras) } to UserHandle{-1}
*snip*
D/Vold ( 103): Found vfat filesystem on /dev/block/vold/179:1
D/DirectVolume( 103): Volume sdcard0 /mnt/media_rw/sdcard0 partition 179:2 removed
D/DirectVolume( 103): Volume sdcard0 /mnt/media_rw/sdcard0 partition 179:1 removed
D/DirectVolume( 103): Volume sdcard0 /mnt/media_rw/sdcard0 disk 179:0 removed
D/Vold ( 103): Volume sdcard0 state changing 3 (Checking) -> 0 (No-Media)
V/KeyguardService( 525): onCreate()
I/fsck_msdos( 103): ** /dev/block/vold/179:1
I/fsck_msdos( 103): Can't open: No such device or address
I/fsck_msdos( 103): fsck_msdos terminated by exit(8)
E/Vold ( 103): Filesystem check failed (unknown exit code 8)
E/Vold ( 103): /dev/block/vold/179:1 failed FS checks (I/O error)
D/Vold ( 103): Volume sdcard0 state changing 0 (No-Media) -> 1 (Idle-Unmounted)
W/Vold ( 103): Returning OperationFailed - no handler for errno 0
D/MountService( 436): volume state changed for /storage/sdcard0 (checking -> unmounted)
I/PackageManager( 436): Updating external media status from unmounted to unmounted
D/MountService( 436): sendStorageIntent Intent { act=unmounted dat=file:///storage/sdcard0 (has extras) } to UserHandle{-1}
D/MountService( 436): volume state changed for /storage/sdcard0 (unmounted -> removed)
D/MountService( 436): sendStorageIntent Intent { act=android.intent.action.MEDIA_REMOVED dat=file:///storage/sdcard0 (has extras) } to UserHandle{-1}
E/VoldConnector( 436): NDC Command {3 volume mount /storage/sdcard0} took too long (3668ms)
E/MountService( 436): Boot-time mount failed (-1)
SD works in CM11 RC1, but not the weekly. The SD card is still found in recovery as well.
If I try and remove the SD card after it's booted it posts the "preparing SD card..." notification and then the "SD card safe to remove" notification.
Click to expand...
Click to collapse
I am not a developer but these home remedies might help.
1} Format your SD card from PC. Format any sd-ext partitions if available. Then clean flash CM11
2} Try some other SD card. Your might not be bugged!
I've done some more research, and it looks a lot like a bug with vold, but I really would need someone like @thewisenerd to help out :fingers-crossed: Perhaps a more verbose version of vold might be needed? idk.
dmesg output from a boot (includes me pulling it in/out a few time) (only lines with 'sd' or 'mmc'): paste dot kde dot org/pyrxbgd9z/c5fjco (XDA won't let me put in external links)
It's not a hardware or partitioning issue. Running this bash script:
Code:
while true; do
if ls /dev/block | grep mmc; then
killall vold
fi
done
will cause the SD to appear in /dev/block and be mountable - and when I stop running the script, the blockfiles disappear but the card still remains mounted. fsck_msdos shows no errors when run outside of vold, TWRP works for the card, and it was working before.
Code:
E/Vold ( 103): /dev/block/vold/179:1 failed FS checks (I/O error)
Please mount the card somehow, and fsck it!
thewisenerd said:
Code:
E/Vold ( 103): /dev/block/vold/179:1 failed FS checks (I/O error)
Please mount the card somehow, and fsck it!
Click to expand...
Click to collapse
Without vold running (on the phone, in the weekly):
Code:
[email protected]:/ # fsck_msdos /dev/block/mmcblk0p1
** /dev/block/mmcblk0p1
** Phase 1 - Read FAT (compare skipped)
Attempting to allocate 6477 KB for FAT
** Phase 2 - Check Cluster Chains
** Phase 3 - Checking Directories
** Phase 4 - Checking for Lost Files
36 files, 1950664 free (1536242 clusters)
[email protected]:/ # mount -t vfat /dev/block/mmcblk0p1 /storage/sdcard0/
[email protected]:/ # ls /storage/sdcard0
Alarms
-snip-
[email protected]:/ #
Looks a lot like vold is doing something to cause it to error out...
forkbomb444 said:
Without vold running (on the phone, in the weekly):
Code:
[email protected]:/ # fsck_msdos /dev/block/mmcblk0p1
** /dev/block/mmcblk0p1
** Phase 1 - Read FAT (compare skipped)
Attempting to allocate 6477 KB for FAT
** Phase 2 - Check Cluster Chains
** Phase 3 - Checking Directories
** Phase 4 - Checking for Lost Files
36 files, 1950664 free (1536242 clusters)
[email protected]:/ # mount -t vfat /dev/block/mmcblk0p1 /storage/sdcard0/
[email protected]:/ # ls /storage/sdcard0
Alarms
-snip-
[email protected]:/ #
Looks a lot like vold is doing something to cause it to error out...
Click to expand...
Click to collapse
Really strange... Could you give some more info on which weekly you are on? I'll try to look through CM's system/vold changes, if anything is breaking stuff...
Also, in any case, did you try connecting the card to a sytem, while on recovery && mounted, and fsck it through Window's CMD, or fsck.msdos?
thewisenerd said:
Really strange... Could you give some more info on which weekly you are on? I'll try to look through CM's system/vold changes, if anything is breaking stuff...
Also, in any case, did you try connecting the card to a sytem, while on recovery && mounted, and fsck it through Window's CMD, or fsck.msdos?
Click to expand...
Click to collapse
I'm on the latest weekly with the latest aw3som3 kernel (July 2) installed. idk where my microsd adapter's gone, but I'll get one tomorrow and then I'll have some results.
@thewisenerd - chkdsk showed no errors, I also tried another SD card and that didn't work either.
forkbomb444 said:
@thewisenerd - chkdsk showed no errors, I also tried another SD card and that didn't work either.
Click to expand...
Click to collapse
Was it working in earlier builds?
edit: I'm assuming yes
please ask more support from the OP @kirmaniarslan
thewisenerd said:
Was it working in earlier builds?
Click to expand...
Click to collapse
It was working in CyanogenMod RC 1.
thewisenerd said:
Was it working in earlier builds?
edit: I'm assuming yes
please ask more support from the OP @kirmaniarslan
Click to expand...
Click to collapse
Doesn't work in Omni. Latest build bootloops because something's causing I/O errors... sd-ext is mounted as /data successfully, but then vold comes in and weird stuff happens.
Logcat: ix.io/dgE
Dmesg: ix.io/dgG (all those ext4 errors seem to be because the device has disappeared)
Oh, and CM RC1 has stopped mounting the card (oh joy)
Logcat: ix.io/dgH
Dmesg: ix.io/dgI
Well, weird. It's started working again
I reformatted the card to exfat rather than vfat and it's mounting properly now. Weird.
Thanks for your help, though
EDIT: For some reason exfat doesn't mount in aw3som3's TWRP @thewisenerd, it complains about missing tzinfo. Bug?
forkbomb444 said:
EDIT: For some reason exfat doesn't mount in aw3som3's TWRP @thewisenerd, it complains about missing tzinfo. Bug?
Click to expand...
Click to collapse
Ah, that! exFat is currently disabled in TWRP (in BoardConfig.mk). fixed that up with the current device tree (local), and will upload TWRP 2.7.1.0 soon.
About missing tzinfo, other people are reporting it too (other devices), and it doesn't seem to have any adverse side-effects, so, I'll choose to ignore it too (until it's (probably) fixed upstream)
I am attempting to encrypt the data partition using the "built in" support, but I am having issues getting it to work with any new mod and any new recovery images. With the newest unofficial carbon mod (CARBON-KK-UNOFFICIAL_f2fs-20150526-moto_msm8960) and newest CM 12 (cm-12.1-20150625-NIGHTLY-xt897.zip), I am able to attempt to start the encryption with the GUI button or with the console commands (trying both PIN and PASSWORD), but either after the first reboot I get a boot animation that lasts forever, or I get an error saying the encryption process was interrupted, and I would have to wipe the data partition and start over. I have tried some tricks I have seen online, including doing it in airplane mode, unplugging the charger, re-sizing the data partition to allow some room at the end for crypto info, and going between ext4 and e2fs manually. I have also used the stock rom to encrypt the partition successfully, but then I attempt to re-flash the new rom, but I get a failure as the recovery image cannot see the data partition. I have tried TWRP 2.8.5, TWRP 2.8.6, and Clockwork 6.0.1.3. I have also attempted this on three different XT897, so I do not believe this is a 1-off hardware issue.
I am hoping someone here has an encrypted partition working on a modern rom, preferably CM12.1.
Total data loss is okay, I can go through and reinstall everything. Also I do not need recovery based backups, I have another means to backing things up ... so encrypted partition recovery support isn't needed in the end.
It should work on the latest CM (I have not tried myself) but you will need to use TWRP, and the latest.
Make sure you are using the one which is recommended in the OP of the CM12.1 thread, 2.8.6.2.
arrrghhh said:
It should work on the latest CM (I have not tried myself) but you will need to use TWRP, and the latest.
Make sure you are using the one which is recommended in the OP of the CM12.1 thread, 2.8.6.2.
Click to expand...
Click to collapse
Thank you for pointing out the newest dev link to TWRP, I was a few ticks behind.
So I flashed recovery with TWRP 2.8.6.2 (I had previously 2.8.6.0). First time for the crypto was console based. It failed with no error. I tried again with a root enabled terminal, phone just reboots with nothing. I wait until it is well over 80% ... I click ENCRYPT and it is just a reboot.
Not to be disrespectful, but I would like to hear from someone who has encrypted, and not just "assume it works".
crankine3 said:
Not to be disrespectful, but I would like to hear from someone who has encrypted, and not just "assume it works".
Click to expand...
Click to collapse
Have you encrypted any device before?
arrrghhh said:
Have you encrypted any device before?
Click to expand...
Click to collapse
crankine3 said:
... I have also used the stock rom to encrypt the partition successfully ...
Click to expand...
Click to collapse
Stock rom works. I have had some modified stock roms work. I have never had a CM based mod to work.
This is what I have tried today .....
With TWRP 2.8.6.3 I wiped everything to start from scratch. I install cm-12.1-20150630-NIGHTLY-xt897.zip and gapps. Phone boots into the first boot stuff, and I just skip through what I can. With the phone plugged in and over 80%, I go straight to setting a pin and then click the encrypt button. Phone reboots normally, like nothing has happened. Next I enable debug, root, and terminal, and run "vdc cryptfs enablecrypto wipe pin XXXXX". Phone reboots and stays in the bootanimation for over 2 hours before I give up.
crankine3 said:
This is what I have tried today .....
With TWRP 2.8.6.3 I wiped everything to start from scratch. I install cm-12.1-20150630-NIGHTLY-xt897.zip and gapps. Phone boots into the first boot stuff, and I just skip through what I can. With the phone plugged in and over 80%, I go straight to setting a pin and then click the encrypt button. Phone reboots normally, like nothing has happened. Next I enable debug, root, and terminal, and run "vdc cryptfs enablecrypto wipe pin XXXXX". Phone reboots and stays in the bootanimation for over 2 hours before I give up.
Click to expand...
Click to collapse
I'll have to review the process myself, but is there any reason you take that last step and run that vdc command in the terminal? It seems extraneous to enabling encryption, and also seems to be the source of your issue.
arrrghhh said:
I'll have to review the process myself, but is there any reason you take that last step and run that vdc command in the terminal? It seems extraneous to enabling encryption, and also seems to be the source of your issue.
Click to expand...
Click to collapse
I run the android encryption program manually only because the GUI button isn't doing anything. I have tried it in the past with "inplace".
In the last hour or so I have reinstalled the stock rom, did a factory reset, and encrypted using the stock rom (via the GUI button). The newer TWRP allowed me to install CM12.1 even though it didn't have access to /data. Upon booting into the OS, I get the "Android is starting" box with apps counting only up to 14, as opposed to the usual 95+. I actually get to the Android 5.1 encryption unlock screen (first time I have ever seen it), and upon entering my pin, I get a new error message:
Decryption unsuccessful
The password you entered is correct, but unfortunately your data is corrupt.
To resume using your phone, you need to perform a factory reset. When you set up your phone after the reset, you'll have an opportunity to restore any data that was backed up to youe Google Account.
RESET PHONE
I click the reboot, and it looks like TWRP tries the factory wipe, and some other message comes up right at the end but goes away faster than I can read it. It boots into the OS, and the encryption prompt comes up, and I get the same Decryption unsuccessful message again. Just to see, I try restoring a CM12 backup, minus the /data, but same results.
I'll try another phone with the newer TWRP 2.8.6.2 to see what happens.
I had a similar issue, but I am not sure if that is the same problem.
When I tried to encrypt, there was no space left for the encrytion key (as far as I understood the encryption key is stored at the end of the partition). The device rebooted without encrypting, as your device did. I had flashed a modded recovery and formatted my userdata partition in order to get it working again.
It is possible that TWRP does not support encryption properly... but I am not sure, maybe your problem is something else.
Anyway, atm I do not use encryption because of the massive performance impact I had in CM11.
Loader009 said:
When I tried to encrypt, there was no space left for the encrytion key (as far as I understood the encryption key is stored at the end of the partition). The device rebooted without encrypting, as your device did. I had flashed a modded recovery and formatted my userdata partition in order to get it working again.
Click to expand...
Click to collapse
How did you know this was the problem? Was there an indication or log you read?
I tried it on another phone, I just had to wait for the battery to charge, no hardware mods, no gapps, just the latest build of CM12.1 and TWRP 2.8.6.2. Once going through the GUI encrypt button, the phone reboots, does an apps update for just 14 apps, then comes up to the special screen that looks like the default background but with the extra red strip. Some screen shifting, then within 30 seconds the "Encryption unsuccessful" message comes up. If I click the reset phone button here, it will bring me into TWRP to do a factory wipe.
logcat output for when I run "vdc cryptfs enablecrypto inplace password XXXXX" and have data formatted with f2fs
logcat *:S Cryptfs:V
--------- beginning of system
I/Cryptfs ( 183): Check if PFE is activated on Boot
E/Cryptfs ( 183): PFE not activated
--------- beginning of main
E/Cryptfs ( 183): Not a valid ext4 superblock
D/Cryptfs ( 183): Just asked init to shut down class main
E/Cryptfs ( 183): Error unmounting internal asecs
D/Cryptfs ( 183): unmounting /mnt/shell/emulated succeeded
D/Cryptfs ( 183): unmounting /data succeeded
I/Cryptfs ( 183): keymaster version is 2
I/Cryptfs ( 183): Using scrypt for cryptfs KDF
D/Cryptfs ( 183): Just triggered post_fs_data
D/Cryptfs ( 183): post_fs_data done
D/Cryptfs ( 183): Just triggered restart_min_framework
I/Cryptfs ( 183): Using scrypt for cryptfs KDF
I/Cryptfs ( 183): load_crypto_mapping_table: target_type = crypt
I/Cryptfs ( 183): load_crypto_mapping_table: real_blk_name = /dev/block/platform/msm_sdcc.1/by-name
/userdata, extra_params =
E/Cryptfs ( 183): Cannot load dm-crypt mapping table.
E/Cryptfs ( 183): Reading ext4 extent caused an exception
D/Cryptfs ( 183): cryptfs_enable_inplace_ext4()=-1
E/Cryptfs ( 183): Error writing crypto_blkdev /dev/block/dm-0 for f2fs inplace encrypt
E/Cryptfs ( 183): Error in running over f2fs blocks
E/Cryptfs ( 183): Failed to encrypt f2fs filesystem on /dev/block/platform/msm_sdcc.1/by-name/userd
ata
I/Cryptfs ( 183): Encrypted to block -1
D/Cryptfs ( 183): cryptfs_enable_inplace_f2fs()=-1
E/Cryptfs ( 183): Encrypting filesystem in place...
E/Cryptfs ( 183): Cannot seek to previously encrypted point on /dev/block/dm-0
D/Cryptfs ( 183): cryptfs_enable_inplace_full()=-1
E/Cryptfs ( 183): Not a valid ext4 superblock
D/Cryptfs ( 183): Just asked init to shut down class main
E/Cryptfs ( 183): Error unmounting internal asecs
D/Cryptfs ( 183): unmounting /mnt/shell/emulated succeeded
D/Cryptfs ( 183): unmounting /data succeeded
I/Cryptfs ( 183): keymaster version is 2
I/Cryptfs ( 183): Using scrypt for cryptfs KDF
D/Cryptfs ( 183): Just triggered post_fs_data
D/Cryptfs ( 183): post_fs_data done
D/Cryptfs ( 183): Just triggered restart_min_framework
I/Cryptfs ( 183): Using scrypt for cryptfs KDF
I/Cryptfs ( 183): load_crypto_mapping_table: target_type = crypt
I/Cryptfs ( 183): load_crypto_mapping_table: real_blk_name = /dev/block/platform/msm_sdcc.1/by-name
/userdata, extra_params =
E/Cryptfs ( 183): Cannot load dm-crypt mapping table.
E/Cryptfs ( 183): Reading ext4 extent caused an exception
D/Cryptfs ( 183): cryptfs_enable_inplace_ext4()=-1
E/Cryptfs ( 183): Error writing crypto_blkdev /dev/block/dm-0 for f2fs inplace encrypt
E/Cryptfs ( 183): Error in running over f2fs blocks
E/Cryptfs ( 183): Failed to encrypt f2fs filesystem on /dev/block/platform/msm_sdcc.1/by-name/userd
ata
I/Cryptfs ( 183): Encrypted to block -1
D/Cryptfs ( 183): cryptfs_enable_inplace_f2fs()=-1
E/Cryptfs ( 183): Encrypting filesystem in place...
E/Cryptfs ( 183): Cannot seek to previously encrypted point on /dev/block/dm-0
D/Cryptfs ( 183): cryptfs_enable_inplace_full()=-1
Click to expand...
Click to collapse
logcat output for when I run "vdc cryptfs enablecrypto inplace password XXXXX" and have data formatted with ext4
logcat *:S Cryptfs:V
--------- beginning of system
I/Cryptfs ( 186): Check if PFE is activated on Boot
E/Cryptfs ( 186): PFE not activated
--------- beginning of main
D/Cryptfs ( 186): Just asked init to shut down class main
E/Cryptfs ( 186): Error unmounting internal asecs
D/Cryptfs ( 186): unmounting /mnt/shell/emulated succeeded
D/Cryptfs ( 186): unmounting /data succeeded
I/Cryptfs ( 186): keymaster version is 2
I/Cryptfs ( 186): Using scrypt for cryptfs KDF
D/Cryptfs ( 186): Just triggered post_fs_data
D/Cryptfs ( 186): post_fs_data done
D/Cryptfs ( 186): Just triggered restart_min_framework
I/Cryptfs ( 186): Using scrypt for cryptfs KDF
I/Cryptfs ( 186): load_crypto_mapping_table: target_type = crypt
I/Cryptfs ( 186): load_crypto_mapping_table: real_blk_name = /dev/block/platform/msm_sdcc.1/by-name
/userdata, extra_params =
E/Cryptfs ( 186): Cannot load dm-crypt mapping table.
I/Cryptfs ( 186): Encrypting ext4 filesystem in place...
I/Cryptfs ( 186): Encrypting group 0
E/Cryptfs ( 186): Error writing crypto_blkdev /dev/block/dm-0 for inplace encrypt
I/Cryptfs ( 186): Encrypted to sector 0
E/Cryptfs ( 186): Error encrypting groups
D/Cryptfs ( 186): cryptfs_enable_inplace_ext4()=-1
E/Cryptfs ( 186): Failed to encrypt f2fs filesystem on /dev/block/platform/msm_sdcc.1/by-name/userd
ata
I/Cryptfs ( 186): Encrypted to block -1
D/Cryptfs ( 186): cryptfs_enable_inplace_f2fs()=-1
E/Cryptfs ( 186): Encrypting filesystem in place...
E/Cryptfs ( 186): Cannot seek to previously encrypted point on /dev/block/dm-0
D/Cryptfs ( 186): cryptfs_enable_inplace_full()=-1
D/Cryptfs ( 186): Just asked init to shut down class main
E/Cryptfs ( 186): Error unmounting internal asecs
D/Cryptfs ( 186): unmounting /mnt/shell/emulated succeeded
D/Cryptfs ( 186): unmounting /data succeeded
I/Cryptfs ( 186): keymaster version is 2
I/Cryptfs ( 186): Using scrypt for cryptfs KDF
D/Cryptfs ( 186): Just triggered post_fs_data
D/Cryptfs ( 186): post_fs_data done
D/Cryptfs ( 186): Just triggered restart_min_framework
I/Cryptfs ( 186): Using scrypt for cryptfs KDF
I/Cryptfs ( 186): load_crypto_mapping_table: target_type = crypt
I/Cryptfs ( 186): load_crypto_mapping_table: real_blk_name = /dev/block/platform/msm_sdcc.1/by-name
/userdata, extra_params =
E/Cryptfs ( 186): Cannot load dm-crypt mapping table.
I/Cryptfs ( 186): Encrypting ext4 filesystem in place...
I/Cryptfs ( 186): Encrypting group 0
E/Cryptfs ( 186): Error writing crypto_blkdev /dev/block/dm-0 for inplace encrypt
I/Cryptfs ( 186): Encrypted to sector 0
E/Cryptfs ( 186): Error encrypting groups
D/Cryptfs ( 186): cryptfs_enable_inplace_ext4()=-1
E/Cryptfs ( 186): Failed to encrypt f2fs filesystem on /dev/block/platform/msm_sdcc.1/by-name/userd
ata
I/Cryptfs ( 186): Encrypted to block -1
D/Cryptfs ( 186): cryptfs_enable_inplace_f2fs()=-1
E/Cryptfs ( 186): Encrypting filesystem in place...
E/Cryptfs ( 186): Cannot seek to previously encrypted point on /dev/block/dm-0
D/Cryptfs ( 186): cryptfs_enable_inplace_full()=-1
Click to expand...
Click to collapse
logcat output for when I try "vdc cryptfs enablecrypto wipe password XXXXX" with ext4 (and it stays locked up on the boot animation)
logcat *:S Cryptfs:V
--------- beginning of main
--------- beginning of system
I/Cryptfs ( 187): Check if PFE is activated on Boot
E/Cryptfs ( 187): PFE not activated
D/Cryptfs ( 187): Just asked init to shut down class main
E/Cryptfs ( 187): Error unmounting internal asecs
D/Cryptfs ( 187): unmounting /mnt/shell/emulated succeeded
D/Cryptfs ( 187): unmounting /data succeeded
I/Cryptfs ( 187): keymaster version is 2
I/Cryptfs ( 187): Using scrypt for cryptfs KDF
I/Cryptfs ( 187): Using scrypt for cryptfs KDF
I/Cryptfs ( 187): load_crypto_mapping_table: target_type = crypt
I/Cryptfs ( 187): load_crypto_mapping_table: real_blk_name = /dev/block/platform/msm_sdcc.1/by-name
/userdata, extra_params =
E/Cryptfs ( 187): Cannot load dm-crypt mapping table.
I/Cryptfs ( 187): Making empty filesystem with command /system/bin/mkfs.f2fs -t -d1 /dev/block/dm-0
9914815
E/Cryptfs ( 187): Error creating filesystem on /dev/block/dm-0, exit status 255
D/Cryptfs ( 187): Just asked init to shut down class main
E/Cryptfs ( 187): Error unmounting internal asecs
D/Cryptfs ( 187): unmounting /mnt/shell/emulated succeeded
D/Cryptfs ( 187): unmounting /data succeeded
I/Cryptfs ( 187): keymaster version is 2
I/Cryptfs ( 187): Using scrypt for cryptfs KDF
I/Cryptfs ( 187): Using scrypt for cryptfs KDF
I/Cryptfs ( 187): load_crypto_mapping_table: target_type = crypt
I/Cryptfs ( 187): load_crypto_mapping_table: real_blk_name = /dev/block/platform/msm_sdcc.1/by-name
/userdata, extra_params =
E/Cryptfs ( 187): Cannot load dm-crypt mapping table.
I/Cryptfs ( 187): Making empty filesystem with command /system/bin/mkfs.f2fs -t -d1 /dev/block/dm-0
9914815
E/Cryptfs ( 187): Error creating filesystem on /dev/block/dm-0, exit status 255
Click to expand...
Click to collapse
As least for using the total wipe method, the binary /system/bin/mkf2.f2fs doesn't exist, but it does exist in /sbin. I copied it over and tried the command again, and got similar output as before, with a little more info ...
I/Cryptfs ( 186): Making empty filesystem with command /system/bin/mkfs.f2fs -t -d1 /dev/block/dm-0
9914815
I/mkfs.f2fs( 186): F2FS-tools: mkfs.f2fs Ver: 1.4.0 (2014-10-18) [modified by Motorola to reser
ve space]
I/mkfs.f2fs( 186): Info: Trim is disabled
I/mkfs.f2fs( 186): total_sectors=009749bf (9914815 bytes)
I/mkfs.f2fs( 186): Info: sector size = 512
I/mkfs.f2fs( 186): Info: total sectors = 0 (in 512 bytes)
I/mkfs.f2fs( 186): Error: Min volume size supported is 104857600
I/mkfs.f2fs( 186): mkfs.f2fs terminated by exit(255)
E/Cryptfs ( 186): Error creating filesystem on /dev/block/dm-0, exit status 255
Click to expand...
Click to collapse
Interesting, that is quite broken.
Let's see if @kabaldan has any ideas...