Hi,
Internation Pardus v15 image on rooted i9300, works very well except for this really odd USB connection error when connecting it to my Sony BT3900u car stereo, it was previously connecting without issue on the v15 Pardus build but for unknown reasons to myself now always presents an error.
Does anyone have any ideas as to what might be causing this issue? Any help would be greatly appreciated.
After getting this issue the first time, I ran through a full rebuild, wiped phone/cache/dalvick and error still persisted post rebuild.
Model:
GT-i9300
Android Version:
4.2.2
Baseband
I9300XXEMA5
Kernel version:
3.0.31-702147
Build Number:
Pardus HD Rom XV XXUDME7
Logcat:
E/MTPRx ( 8982): Read Error Came false
E/ ( 8982): read error [0] [Success]
E/MTPRx ( 8982): state from USB_STATE eventDISCONNECTED
E/MTPRx ( 8982): /data/data/com.samsung.android.MtpApplication/gadgetDisconnectAndConnect.txt: open failed: ENOENT (No such file or directory)
E/MTPRx ( 8982): stop observing and calling usbRemoved
E/MTPRx ( 8982): In usbRemoved Status bar enabled
E/MTPRx ( 8982): Sending Broadcast
E/MtpService( 8982): onDestroy.
E/MtpService( 8982): Unregister Mtp disable Receiver
E/MtpService( 8982): Receiver not registered: [email protected]
E/MtpService( 8982): unregistering mtpMediaReceiver in UnregisterAllIntent
E/MtpService( 8982): Receiver not registered: [email protected]
E/MTPJNIInterface( 8982): noti = 3
E/ ( 8982): ****** [mtp_usb_mtp_finalize] mtp_close_fd Calling
E/ ( 8982): [mtp_close_fd] fd = 50...
E/ ( 8982): [mtp_close_fd] USB endpoint [50] closed...
E/ ( 8982): ****** [mtp_usb_mtp_finalize] Updating the gInitializeFlag Flag to FALSE
E/ ( 8982): ****** [mtp_usb_mtp_finalize] Calling mtp_stop_io
E/SEC PowerHAL( 2447): sysfs_write : Error opening /sys/class/input/input1/enabled: No such file or directory
E/SEC PowerHAL( 2447): sysfs_write : Error opening /sys/class/input/input8/enabled: No such file or directory
E/videowall-TranscodeReceiver(10572): broadcastMSG : android.intent.action.ACTION_POWER_DISCONNECTED
E/MTPRx (10600): In MtpReceiverandroid.hardware.usb.action.USB_STATE
E/MTPRx (10600): check value of boot_completed is1
E/MTPRx (10600): check booting is completed_sys.boot_completed
E/MTPRx (10600): Sd-Card path/storage/extSdCard
E/MTPRx (10600): Status for mount/Unmount :mounted
E/MTPRx (10600): SDcard is available
E/MTPRx (10600): The value of first_boot is 1
E/MTPRx (10600): [ 662] The value of first_boot is 1NORMAL SEQUENCE
E/MTPRx (10600): Received USB_STATE with sdCardLaunch = 0
E/MTPRx (10600): configured is false
I'm guessing this is the correct part of the log that pretains to the MTP/USB part. If not I have attached a full log.
Try typing this in a terminal window or adb shell on your phone:
Code:
touch /data/data/com.samsung.android.MtpApplication/gadgetDisconnectAndConnect.txt
Or, make a txt file called gadgetDisconnectAndConnect and place it in /data/data/com.samsung.android.MtpApplication folder.
xpmode said:
Try typing this in a terminal window or adb shell on your phone:
Code:
touch /data/data/com.samsung.android.MtpApplication/gadgetDisconnectAndConnect.txt
Or, make a txt file called gadgetDisconnectAndConnect and place it in /data/data/com.samsung.android.MtpApplication folder.
Click to expand...
Click to collapse
Hi, thanks for the reply.
I did that as quoted, nothing seems to have changed, What should I be looking for?
Thanks!
I want to modify the Saihon X6 ROM, but the system.img is different from I've ever met, they put the system.img into 8 img, now do not know how to unpack/repack, I need help, need a detailed tutorial. Thank you
ht tp://pan.baidu.com/s/1pJAvLer
I tried this,and it not working
Run sudo mount -o loop system_1.img system
displays
Mount: wrong fs type, bad option, bad superblock on / dev/loop0,
Missing codepage or helper program, or Other Error
system log may have some important information,
try using dmesg | tail like a command.
Run dmesg | tail view LOG
display
[74.005499] audit_printk_skb: 18 callbacks suppressed
[74.005518] type = 1400 Audit (1360118240.727:23): AppArmor = "DENIED" operation = "capable" parent = 1 Profile = "/ usr / lib / Telepathy / mission-control-5 "pid = 1553 COMM =" mission-control "Capability = 23 capname =" sys_nice "
[74.415356] type = 1400 Audit (1360118241.135:24): AppArmor = "DENIED" operation = "Open" parent = 1 profile = "/ usr/lib/telepathy/mission-control-5" name = "/ usr / share / gvfs / remote-volume-monitors /" pid = 1553 comm = "mission-control" requested_mask = "r" denied_mask = "r" fsuid = 0 ouid = 0
[365.116251] EXT4-fs (loop0): bad geometry: Block count 97 656 Exceeds Size of device (32767 Blocks)
[579.113993] hrtimer: interrupt took 5,682,946 ns
[630.545278] EXT4-fs ( loop0): bad geometry: Block count ninety-seven thousand six hundred and fifty-six Exceeds Size of device (32767 Blocks)
[644.026965] EXT4-fs (loop0): Unrecognized Mount option "loop1" or Missing value
[670.312507] EXT4-fs (loop0): bad geometry: Block count ninety-seven thousand six hundred fifty-six Exceeds Size of device (32767 Blocks)
[788.599457] EXT4-fs (loop0): bad geometry: 76800 Block count Exceeds Size of device (1657 Blocks)
[1008.514549] EXT4-fs (loop0): bad geometry: Block count 97,656 exceeds size of device (32767 blocks)
file system_1.img
results
system_1.img: Linux rev 1.0 ext4 filesystem data, UUID = 57f8f4bc-abf4-655f-bf67-946fc0f9f25b (extents) (large files)
https://forum.xda-developers.com/an...ide-how-to-unpack-repack-system1-img-t3567741
I want to modify the Saihon X6 ROM, but the system.img is different from I've ever met, they put the system.img into 8 img, now do not know how to unpack/repack, I need help, need a detailed tutorial. Thank you
ht tp://pan.baidu.com/s/1pJAvLer
I tried this,and it not working
Run sudo mount -o loop system_1.img system
displays
Mount: wrong fs type, bad option, bad superblock on / dev/loop0,
Missing codepage or helper program, or Other Error
system log may have some important information,
try using dmesg | tail like a command.
Run dmesg | tail view LOG
display
[74.005499] audit_printk_skb: 18 callbacks suppressed
[74.005518] type = 1400 Audit (1360118240.727:23): AppArmor = "DENIED" operation = "capable" parent = 1 Profile = "/ usr / lib / Telepathy / mission-control-5 "pid = 1553 COMM =" mission-control "Capability = 23 capname =" sys_nice "
[74.415356] type = 1400 Audit (1360118241.135:24): AppArmor = "DENIED" operation = "Open" parent = 1 profile = "/ usr/lib/telepathy/mission-control-5" name = "/ usr / share / gvfs / remote-volume-monitors /" pid = 1553 comm = "mission-control" requested_mask = "r" denied_mask = "r" fsuid = 0 ouid = 0
[365.116251] EXT4-fs (loop0): bad geometry: Block count 97 656 Exceeds Size of device (32767 Blocks)
[579.113993] hrtimer: interrupt took 5,682,946 ns
[630.545278] EXT4-fs ( loop0): bad geometry: Block count ninety-seven thousand six hundred and fifty-six Exceeds Size of device (32767 Blocks)
[644.026965] EXT4-fs (loop0): Unrecognized Mount option "loop1" or Missing value
[670.312507] EXT4-fs (loop0): bad geometry: Block count ninety-seven thousand six hundred fifty-six Exceeds Size of device (32767 Blocks)
[788.599457] EXT4-fs (loop0): bad geometry: 76800 Block count Exceeds Size of device (1657 Blocks)
[1008.514549] EXT4-fs (loop0): bad geometry: Block count 97,656 exceeds size of device (32767 blocks)
file system_1.img
results
system_1.img: Linux rev 1.0 ext4 filesystem data, UUID = 57f8f4bc-abf4-655f-bf67-946fc0f9f25b (extents) (large files)
Hello!
Today I flashed the official CyanogenMod 12.1 Nightly Build (cm-12.1-20150902-NIGHTLY) ROM on my SII.
I am happy about the stagefright fixes but I can't encrypt the device anymore.
Logcat:
Code:
I/Cryptfs ( 1851): Check if PFE is activated on Boot
E/Cryptfs ( 1851): Cannot open footer file /efs/metadata for get
E/Cryptfs ( 1851): Error getting crypt footer and key
D/VoldCmdListener( 1851): cryptfs getpw
D/VoldCmdListener( 1851): cryptfs clearpw
E/Cryptfs ( 1851): Cannot open footer file /efs/metadata for get
D/Cryptfs ( 1851): Just asked init to shut down class main
D/Cryptfs ( 1851): unmounting /data succeeded
I/Cryptfs ( 1851): keymaster version is 2
I/Cryptfs ( 1851): Using scrypt for cryptfs KDF
E/Cryptfs ( 1851): Cannot open footer file /efs/metadata for put
E/Cryptfs ( 1851): Error writing the key to the end of the partition
E/Cryptfs ( 1851): Error enabling encryption after framework is shutdown, no data changed, restarting system
I checked the efs partition. It's good. I can even find my "old" metadata file since the phone was encrypted before.
When I set SELinux to permissive it's looks good till the reboot.
Logcat before the reboot:
Code:
E/Cryptfs ( 1850): not running with encryption, aborting
W/Cryptfs ( 1850): upgrading crypto footer to 1.3
D/Cryptfs ( 1850): Just asked init to shut down class main
D/Cryptfs ( 1850): unmounting /data succeeded
I/Cryptfs ( 1850): keymaster version is 2
I/Cryptfs ( 1850): Using scrypt for cryptfs KDF
D/Cryptfs ( 1850): Just triggered post_fs_data
D/Cryptfs ( 1850): post_fs_data done
D/Cryptfs ( 1850): Just triggered restart_min_framework
I/Cryptfs ( 1850): Using scrypt for cryptfs KDF
I/Cryptfs ( 1850): Enabling support for allow_discards in dmcrypt.
I/Cryptfs ( 1850): load_crypto_mapping_table: target_type = crypt
I/Cryptfs ( 1850): load_crypto_mapping_table: real_blk_name = /dev/block/mmcblk0p10, extra_params = 1 allow_discards
I/Cryptfs ( 1850): Encrypting ext4 filesystem in place...
I/Cryptfs ( 1850): Encrypting group 0
I/Cryptfs ( 1850): Encrypting from sector 0
I/Cryptfs ( 1850): Encrypted to sector 4526080
I/Cryptfs ( 1850): Encrypting from sector 4538368
I/Cryptfs ( 1850): Encrypted to sector 4579328
I/Cryptfs ( 1850): Encrypting from sector 4587008
...
I/Cryptfs ( 1850): Encrypting group 1
I/Cryptfs ( 1850): Encrypted to sector 16763904
I/Cryptfs ( 1850): Encrypting from sector 16777216
...
I/Cryptfs ( 1850): Encrypting group 2
I/Cryptfs ( 1850): Encrypted to sector 33861632
I/Cryptfs ( 1850): Encrypting from sector 33865728
...
I/Cryptfs ( 1850): Encrypting group 15
I/Cryptfs ( 1850): Encrypted to sector 235502592
I/Cryptfs ( 1850): Encrypting from sector 251658240
I/Cryptfs ( 1850): Encrypted to sector 251923456
Code:
D/CryptKeeper( 5706): Going into airplane mode.
D/CryptKeeper( 5706): Encryption progress screen initializing.
D/CryptKeeper( 5706): Acquiring wakelock.
V/CryptKeeper( 5706): Encryption progress: 100
After the reboot the device wants to be unlocked but after entering the password it tells me "your password is correct but your data is corrupt, you need to reset".
Am I right about SELinux being the problem?
How can I fix this?
Cheers s0r3_x
Update:
Same errors with cm-12.1-20150903-NIGHTLY.
Works with cm-12.1-20150904-NIGHTLY!
Maybe it's better post the problem in the developer thread. Lysergic and others developer can see the log. The link is: http://forum.xda-developers.com/galaxy-s2/orig-development/rom-cyanogenmod-12-1-nightly-builds-t3147661
@Lysergic Acid
minghi1 said:
Maybe it's better post the problem in the developer thread. Lysergic and others developer can see the log. The link is: http://forum.xda-developers.com/galaxy-s2/orig-development/rom-cyanogenmod-12-1-nightly-builds-t3147661
Click to expand...
Click to collapse
I made this account to post in that thread but the forum tells me that I need ten post before I am allowed to post in a developer thread.
But yes I agree it would be better to post there...
s0r3_x said:
I made this account to post in that thread but the forum tells me that I need ten post before I am allowed to post in a developer thread.
But yes I agree it would be better to post there...
Click to expand...
Click to collapse
No problem to post here, @king_ahmed already mentioned me to call my attention. Sir, if SELinux is blocking encryption I need a full logcat of the issue to see what's happening.
No problem to post here, @king_ahmed already mentioned me to call my attention. Sir, if SELinux is blocking encryption I need a full logcat of the issue to see what's happening.
Click to expand...
Click to collapse
Then a thanks @king_ahmed for getting @Lysergic Acid attention an thanks @Lysergic Acid for not ignoring me .
Here are the logs:
logcat_SELinux_enforce.log: pastebin.com/whxG3qTR
logcat_SELinux_permissive.log: pastebin.com/0FSYqRcc
s0r3_x said:
Then a thanks @king_ahmed for getting @Lysergic Acid attention an thanks @Lysergic Acid for not ignoring me .
Here are the logs:
logcat_SELinux_enforce.log: pastebin.com/whxG3qTR
logcat_SELinux_permissive.log: pastebin.com/0FSYqRcc
Click to expand...
Click to collapse
I've already fixed the SELinux issues present in your logs. Please try the latest nightly and report if the issue persists.
Lysergic Acid said:
I've already fixed the SELinux issues present in your logs. Please try the latest nightly and report if the issue persists.
Click to expand...
Click to collapse
The build installed on my SII is cm-12.1-20150903-NIGHTLY-i9100.
s0r3_x said:
The build installed on my SII is cm-12.1-20150903-NIGHTLY-i9100.
Click to expand...
Click to collapse
The denial present in your log is that: denied { search } for name="/" dev=mmcblk0p1 ino=2 scontext=u:r:vold:s0 tcontext=ubject_r:efs_device_file:s0 tclass=dir
On this commit: http://review.cyanogenmod.org/#/c/107862/ you can see me allowing vold to search in the /efs. It was merged on September 2nd. So how's that possible?
Lysergic Acid said:
The denial present in your log is that: denied { search } for name="/" dev=mmcblk0p1 ino=2 scontext=u:r:vold:s0 tcontext=ubject_r:efs_device_file:s0 tclass=dir
On this commit: review.cyanogenmod.org/#/c/107862/ you can see me allowing vold to search in the /efs. It was merged on September 2nd. So how's that possible?
Click to expand...
Click to collapse
I don't know sorry I really don't that is why I am posting here.
If you look at line 40 in the logcat_SELinux_enforce.log you see the build installed is cm-12.1-20150903.:
Code:
I/cm ( 1884): Welcome to Android 5.1.1 / CyanogenMod-12.1-20150903-NIGHTLY-i9100
Or line 13 in the logcat_SELinux_permissive.log:
Code:
I/cm ( 1880): Welcome to Android 5.1.1 / CyanogenMod-12.1-20150903-NIGHTLY-i9100
Update:
I flashed the new nightly (CyanogenMod-12.1-20150904-NIGHTLY-i9100) and tried again.
It worked!!!
Big thanks @Lysergic Acid !
Still I don't get it. It should have worked with yesterdays nightly.
@Lysergic Acid: Do you want the new logs?
Not sure where to write this, but i tried to encrypt phone several times and it failed, with todays night build (cm-12.1-20150905-NIGHTLY-i9100).
Same error: Cannot open footer file /efs/metadata. Tried both CWM and TWRP, also resized partition, to give it space for encryption key.
Code:
setprop vold.decrypt trigger_shutdown_framework
e2fsck -f /dev/block/mmcblk0p10
resize2fs /dev/block/mmcblk0p10 740000
Tried to give it 16kb and 180MB, it failed... goes into reboot. Same if done via adb
Code:
vdc cryptfs enablecrypto inplace password mypass
Any ideas?
Thank you
s0r3_x said:
Update:
I flashed the new nightly (CyanogenMod-12.1-20150904-NIGHTLY-i9100) and tried again.
It worked!!!
Big thanks @Lysergic Acid !
Still I don't get it. It should have worked with yesterdays nightly.
@Lysergic Acid: Do you want the new logs?
Click to expand...
Click to collapse
I'm glad it worked, no need for more logs then.
potentia said:
Not sure where to write this, but i tried to encrypt phone several times and it failed, with todays night build (cm-12.1-20150905-NIGHTLY-i9100).
Same error: Cannot open footer file /efs/metadata. Tried both CWM and TWRP, also resized partition, to give it space for encryption key.
Code:
setprop vold.decrypt trigger_shutdown_framework
e2fsck -f /dev/block/mmcblk0p10
resize2fs /dev/block/mmcblk0p10 740000
Tried to give it 16kb and 180MB, it failed... goes into reboot. Same if done via adb
Code:
vdc cryptfs enablecrypto inplace password mypass
Any ideas?
Thank you
Click to expand...
Click to collapse
Do you have anything under /efs/metadata? If not, this error is acceptable. Also, you don't need to resize the block of it, this is all wrong man, you're not resizing the /efs partition to be bigger, just the block of it, probably even making it smaller than the default.
Please give me a logcat of the problem when you try to encrypt the phone.
Lysergic Acid said:
Do you have anything under /efs/metadata? If not, this error is acceptable. Also, you don't need to resize the block of it, this is all wrong man, you're not resizing the /efs partition to be bigger, just the block of it, probably even making it smaller than the default.
Please give me a logcat of the problem when you try to encrypt the phone.
Click to expand...
Click to collapse
I was under impression that key was residing in the last 16KB of data partition, that's why I decreased mmcblk0p10 from 786432 to 786428 blocks, leaving 4 blocks (16KB) free.
There is no /efs/metadata file
logcat: s3.amazonaws.com/xda-share/logcat.txt
Thank you
@Lysergic Acid
Had a chance to look at log?
Thank you
Still cannot encrypt @Lysergic Acid
Updated to cm 13
adb log:
Code:
02-13 17:21:12.809 1844 1894 E Cryptfs : Bad magic for real block device /dev/block/mmcblk0p10
02-13 17:21:12.815 1844 1894 E Cryptfs : Orig filesystem overlaps crypto footer region. Cannot encrypt in place.
Hi,
Using aLogcat ROOT, I enabled the filter for radio and see a lot of messages like this
Code:
....
D(3232: 3232) [SubManager][getSubId)- fail, slotId:1, getSimCount():1
E(3232: 3232) getTelephonyProperty - subId is null!
D(22111:22111) [subManager] isValidSubId sub id = 1
....
These are very frequent and seems strange...
I didn't find any useful information about that on the web. Any idea?