Attempting to encrypt with modern mod - Motorola Photon Q 4G LTE
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...
Related
Need any help cm7 for t839
I try to port cm7 to T839。 the source from httpx://github.com/SunRain/android_device_samsung_sidekick4g.git yes the source can not run .so I fix(may be fixed) anything to build it. I use bali kernel 2.6.32 and modify init.rc but it can not run .no logo show. stat: Code: C:\Program Files\Android Commander\bin>adb logcat --------- beginning of /dev/log/main E/logwrapper( 2405): executing /system/bin/drexe failed: No such file or dir ry I/logwrapper( 2394): /system/bin/drexe terminated by exit(255) I/DEBUG ( 2392): debuggerd: Feb 18 2012 19:38:13 D/ ( 2397): agpsd.c : Child created, Parent exits : succes --------- beginning of /dev/log/system I/Vold ( 2387): Vold 2.1 (the revenge) firing up D/Vold ( 2387): Volume sdcard state changing -1 (Initializing) -> 0 (No-M ) D/Vold ( 2387): Volume sdcard state changing -1 (Initializing) -> 0 (No-M ) D/ ( 2417): agpsd.c : Child execution starts here I/Netd ( 2391): Netd 1.0 starting E/Netd ( 2391): Unable to start DnsProxyListener (No such file or directo E/SocketListener( 2391): Obtaining file descriptor socket 'dnsproxyd' failed such file or directory D/Vold ( 2387): Volume sdcard state changing 0 (No-Media) -> 2 (Pending) D/Vold ( 2387): Volume sdcard state changing 2 (Pending) -> 1 (Idle-Unmou ) I/app_process( 2395): link_image[1962]: 2406 could not load needed library android_runtime.so' for '/system/bin/app_process' (reloc_library[1311]: 240 nnot locate '_ZN7android6Camera13getCameraInfoEiPNS_10CameraInfoE'... I/app_process( 2395): )CANNOT LINK EXECUTABLE I/logwrapper( 2395): /system/bin/app_process terminated by exit(255) E/LcsClient( 2417): oem_send_ril_request: Connection Failed. (4) E/LcsClient( 2417): oem_send_ril_request: Connection Failed. (4) this log Code: I/app_process( 2395): link_image[1962]: 2406 could not load needed library android_runtime.so' for '/system/bin/app_process' (reloc_library[1311]: 240 nnot locate '_ZN7android6Camera13getCameraInfoEiPNS_10CameraInfoE'... Can not find the camera??
Try the t759 camera. or the 35 kernal Sent from my SGH-T839 using XDA App
D/AndroidRuntime( 2591): >>>>>> AndroidRuntime START com.android.internal.os.Run timeInit <<<<<< I/AndroidRuntime( 2591): Heap size: -Xmx40m D/AndroidRuntime( 2591): CheckJNI is ON D/dalvikvm( 2591): creating instr width table E/dalvikvm( 2591): Can't open dex cache '/cache/dalvik-cache/[email protected]@co [email protected]': Permission denied I/dalvikvm( 2591): Unable to open or create cache for /system/framework/core.jar (/cache/dalvik-cache/[email protected]@[email protected]) D/dalvikvm( 2591): Unable to process classpath element '/system/framework/core.j ar' E/dalvikvm( 2591): Can't open dex cache '/cache/dalvik-cache/[email protected]@bo [email protected]': Permission denied I/dalvikvm( 2591): Unable to open or create cache for /system/framework/bouncyca stle.jar (/cache/dalvik-cache/[email protected]@[email protected]) D/dalvikvm( 2591): Unable to process classpath element '/system/framework/bouncy castle.jar' E/dalvikvm( 2591): Can't open dex cache '/cache/dalvik-cache/[email protected]@ex [email protected]': Permission denied I/dalvikvm( 2591): Unable to open or create cache for /system/framework/ext.jar (/cache/dalvik-cache/[email protected]@[email protected]) D/dalvikvm( 2591): Unable to process classpath element '/system/framework/ext.ja r' E/dalvikvm( 2591): Can't open dex cache '/cache/dalvik-cache/[email protected]@fr [email protected]': Permission denied I/dalvikvm( 2591): Unable to open or create cache for /system/framework/framewor k.jar (/cache/dalvik-cache/[email protected]@[email protected]) D/dalvikvm( 2591): Unable to process classpath element '/system/framework/framew ork.jar' E/dalvikvm( 2591): Can't open dex cache '/cache/dalvik-cache/[email protected]@an [email protected]': Permission denied I/dalvikvm( 2591): Unable to open or create cache for /system/framework/android. policy.jar (/cache/dalvik-cache/[email protected]@[email protected]) D/dalvikvm( 2591): Unable to process classpath element '/system/framework/androi I think It's wrong of rfs filesystem.
[Q] system frozen by SD card unmount
Moin, my htc brave freezes often. Sometimes while making a backup with titanium. Now I discovers in the logs the following: Code: 04-08 09:32:36.780: D/StatusBarService(251): new notification: when=1333870356785 ongoing=true [email protected] 04-08 09:32:36.840: D/DirectVolume(94): Volume sdcard /mnt/sdcard partition 179:2 removed 04-08 09:32:36.850: D/DirectVolume(94): Volume sdcard /mnt/sdcard partition 179:1 removed 04-08 09:32:36.850: D/Vold(94): Volume sdcard state changing 4 (Mounted) -> 5 (Unmounting) 04-08 09:32:36.930: E/FrameworkListener(94): read() failed (Connection reset by peer) 04-08 09:32:37.851: I/Vold(94): /mnt/secure/staging/.android_secure sucessfully unmounted 04-08 09:32:37.851: I/Vold(94): /mnt/secure/asec sucessfully unmounted 04-08 09:32:37.851: I/Vold(94): /mnt/secure/staging sucessfully unmounted 04-08 09:32:37.851: I/Vold(94): /mnt/sdcard unmounted sucessfully 04-08 09:32:37.861: D/Vold(94): Volume sdcard state changing 5 (Unmounting) -> 1 (Idle-Unmounted) 04-08 09:32:37.861: D/DirectVolume(94): Crisis averted 04-08 09:32:37.861: D/DirectVolume(94): Volume sdcard /mnt/sdcard disk 179:0 removed 04-08 09:32:37.861: D/Vold(94): Volume sdcard state changing 1 (Idle-Unmounted) -> 0 (No-Media) 04-08 09:32:37.861: D/Vold(94): --------- beginning of /dev/log/main 04-08 09:32:54.607: I/dalvikvm(4187): Unknown chunk 0x00000000 ( What is Vold? Why is the SD card unmounted? (I use data2sd) Kind regards Thomas -- Model: Bravo HTC Desire PVT1 SHIP Activmatrix-OLED MICROP-031d Baseband/Radio: 32.56.00.32U_5.17.05.23 Software/ROM: GingerBurst_1.0.0.3.zip Boatloader/H-BOOT: 6.93.1002 Recovery: Revolutionary ClockworkMod Recovery v4.0.1.4 ROOTED: Revolutionary v4.0.1.4 S-OFF Kernel: 2.6.35.10-g308ba26 Data2SD: X21E Droidzone Provider: O2 Germany Android: 2.3.3 HTC Sense: 2.1
[Q] Tablet not booting (with log and video)
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?
[Q] Do I need these files for my port?
I am porting cm7 to my Samsung Conquer 4g. This is taken from the updater-script
Code:
ui_print("Checking state of BML/MTD...");
package_extract_file("modem.bin", "/tmp/modem.bin");
set_perm(0, 0, 0777, "/tmp/modem.bin");
package_extract_file("updater.sh", "/tmp/updater.sh");
set_perm(0, 0, 0777, "/tmp/updater.sh");
package_extract_file("make_ext4fs", "/tmp/make_ext4fs");
set_perm(0, 0, 0777, "/tmp/make_ext4fs");
package_extract_file("busybox", "/tmp/busybox");
set_perm(0, 0, 0777, "/tmp/busybox");
package_extract_file("flash_image", "/tmp/flash_image");
set_perm(0, 0, 0777, "/tmp/flash_image");
package_extract_file("erase_image", "/tmp/erase_image");
set_perm(0, 0, 0777, "/tmp/erase_image");
package_extract_file("bml_over_mtd", "/tmp/bml_over_mtd");
set_perm(0, 0, 0777, "/tmp/bml_over_mtd");
package_extract_file("bml_over_mtd.sh", "/tmp/bml_over_mtd.sh");
set_perm(0, 0, 0777, "/tmp/bml_over_mtd.sh");
Do I need these files? Also when I removed them and tried to boot it got stuck on the bootsplash. Here's my logcat.
Code:
--------- beginning of /dev/log/main
I/DEBUG ( 109): debuggerd: Mar 17 2012 16:39:00
E/macloader( 107): wifi.mac_addr: .mac.info already exist!
--------- beginning of /dev/log/system
I/Vold ( 106): Vold 2.1.1 (the revenge) firing up
I/Vold ( 106): Volume::setState -> Volume sdcard1 /mnt/sdcard state changed from -1 (Initializing) to 0 (No-Media)
I/Vold ( 106): NetlinkHandler::onEvent ->[block] from uevent
I/Vold ( 106): NetlinkHandler::onEvent ->[block] from uevent
I/Vold ( 106): NetlinkHandler::onEvent ->[block] from uevent
I/Vold ( 106): NetlinkHandler::onEvent ->[block] from uevent
I/Vold ( 106): NetlinkHandler::onEvent ->[block] from uevent
I/Vold ( 106): NetlinkHandler::onEvent ->[block] from uevent
I/Vold ( 106): NetlinkHandler::onEvent ->[block] from uevent
I/Vold ( 106): NetlinkHandler::onEvent ->[block] from uevent
I/Vold ( 106): NetlinkHandler::onEvent ->[block] from uevent
I/Vold ( 106): NetlinkHandler::onEvent ->[block] from uevent
I/Vold ( 106): NetlinkHandler::onEvent ->[block] from uevent
I/Vold ( 106): NetlinkHandler::onEvent ->[block] from uevent
I/Vold ( 106): NetlinkHandler::onEvent ->[block] from uevent
I/Vold ( 106): NetlinkHandler::onEvent ->[block] from uevent
I/Vold ( 106): NetlinkHandler::onEvent ->[block] from uevent
I/Vold ( 106): NetlinkHandler::onEvent ->[block] from uevent
I/Vold ( 106): NetlinkHandler::onEvent ->[block] from uevent
I/Vold ( 106): NetlinkHandler::onEvent ->[block] from uevent
I/Vold ( 106): NetlinkHandler::onEvent ->[block] from uevent
I/Vold ( 106): NetlinkHandler::onEvent ->[block] from uevent
I/Vold ( 106): NetlinkHandler::onEvent ->[block] from uevent
I/Vold ( 106): NetlinkHandler::onEvent ->[block] from uevent
I/Vold ( 106): NetlinkHandler::onEvent ->[block] from uevent
I/Vold ( 106): NetlinkHandler::onEvent ->[block] from uevent
I/Vold ( 106): NetlinkHandler::onEvent ->[block] from uevent
I/Vold ( 106): NetlinkHandler::onEvent ->[block] from uevent
I/Vold ( 106): NetlinkHandler::onEvent ->[block] from uevent
I/Vold ( 106): NetlinkHandler::onEvent ->[block] from uevent
I/Vold ( 106): NetlinkHandler::onEvent ->[block] from uevent
I/Vold ( 106): NetlinkHandler::onEvent ->[block] from uevent
D/DirectVolume( 106): DirectVolume::handleBlockEvent-> ::NlActionAdd:: major 179,minor 0 (disk)
D/DirectVolume( 106): DirectVolume::handleDiskAdded -> mDiskMajor 179, mDiskMinor 0, NPARTS:1
I/Vold ( 106): Volume::setState -> Volume sdcard1 /mnt/sdcard state changed from 0 (No-Media) to 2 (Pending)
I/Vold ( 106): NetlinkHandler::onEvent ->[block] from uevent
D/DirectVolume( 106): DirectVolume::handleBlockEvent-> ::NlActionAdd:: major 179,minor 1 (partition)
D/DirectVolume( 106): DirectVolume::handlePartitionAdded -> major 179, minor 1, PARTN 1
I/Vold ( 106): Volume::setState -> Volume sdcard1 /mnt/sdcard state changed from 2 (Pending) to 1 (Idle-Unmounted)
I/Vold ( 106): NetlinkHandler::onEvent ->[switch] from uevent
D/Vold ( 106): VolumeManager::handleSwitchEvent -> Changed USB status SWITCH_NAME(usb_mass_storage),SWITCH_STATE(online)
W/Vold ( 106): Ignoring unknown switch 'usb_mass_storage'
I/Vold ( 106): NetlinkHandler::onEvent ->[switch] from uevent
D/Vold ( 106): VolumeManager::handleSwitchEvent -> Changed USB status SWITCH_NAME(MSM72K_UDC),SWITCH_STATE(offline)
W/Vold ( 106): Ignoring unknown switch 'MSM72K_UDC'
I/Vold ( 106): NetlinkHandler::onEvent ->[switch] from uevent
D/Vold ( 106): VolumeManager::handleSwitchEvent -> Changed USB status SWITCH_NAME(MSM72K_UDC),SWITCH_STATE(online)
W/Vold ( 106): Ignoring unknown switch 'MSM72K_UDC'
I/Vold ( 106): NetlinkHandler::onEvent ->[switch] from uevent
D/Vold ( 106): VolumeManager::handleSwitchEvent -> Changed USB status SWITCH_NAME(usb_configuration),SWITCH_STATE(1)
W/Vold ( 106): Ignoring unknown switch 'usb_configuration'
I/Vold ( 106): NetlinkHandler::onEvent ->[switch] from uevent
D/Vold ( 106): VolumeManager::handleSwitchEvent -> Changed USB status SWITCH_NAME(MSM72K_UDC),SWITCH_STATE(offline)
W/Vold ( 106): Ignoring unknown switch 'MSM72K_UDC'
I/Vold ( 106): NetlinkHandler::onEvent ->[switch] from uevent
D/Vold ( 106): VolumeManager::handleSwitchEvent -> Changed USB status SWITCH_NAME(usb_connected),SWITCH_STATE(0)
D/Vold ( 106): USB disconnected
I/Vold ( 106): NetlinkHandler::onEvent ->[switch] from uevent
D/Vold ( 106): VolumeManager::handleSwitchEvent -> Changed USB status SWITCH_NAME(usb_configuration),SWITCH_STATE(0)
W/Vold ( 106): Ignoring unknown switch 'usb_configuration'
I/Vold ( 106): NetlinkHandler::onEvent ->[switch] from uevent
D/Vold ( 106): VolumeManager::handleSwitchEvent -> Changed USB status SWITCH_NAME(usb_mass_storage),SWITCH_STATE(offline)
W/Vold ( 106): Ignoring unknown switch 'usb_mass_storage'
I/Vold ( 106): NetlinkHandler::onEvent ->[switch] from uevent
D/Vold ( 106): VolumeManager::handleSwitchEvent -> Changed USB status SWITCH_NAME(usb_connected),SWITCH_STATE(1)
D/Vold ( 106): USB connected
D/Vold ( 106): Share method ums now available
I/Vold ( 106): NetlinkHandler::onEvent ->[switch] from uevent
D/Vold ( 106): VolumeManager::handleSwitchEvent -> Changed USB status SWITCH_NAME(usb_mass_storage),SWITCH_STATE(online)
W/Vold ( 106): Ignoring unknown switch 'usb_mass_storage'
I/Vold ( 106): NetlinkHandler::onEvent ->[switch] from uevent
D/Vold ( 106): VolumeManager::handleSwitchEvent -> Changed USB status SWITCH_NAME(MSM72K_UDC),SWITCH_STATE(online)
W/Vold ( 106): Ignoring unknown switch 'MSM72K_UDC'
I/Vold ( 106): NetlinkHandler::onEvent ->[switch] from uevent
D/Vold ( 106): VolumeManager::handleSwitchEvent -> Changed USB status SWITCH_NAME(usb_configuration),SWITCH_STATE(1)
W/Vold ( 106): Ignoring unknown switch 'usb_configuration'
Can you please tell me what I need to fix? Thanks!
CM11 weekly doesn't mount my SD card
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)