[Verizon Samsung Galaxy S III] n01ce:
Issue on Samsung Galaxy S

Hello, it doesn't work for me... can someone provide any help? :confused:

Note that "WARNING "EXPERIMENTAL METHOD You are using an OLD phone." is present on the debug log.

Environment:

Samsung Galaxy S (I9000)

PAC-man ROM 22.2.0 (Cyanogen 10.1.0-RC0-galaxysmtd)

microSD card 32GB formated in exfat (unpartitioned) under Windows

This exfat script v. 6.3 installed through CWM recovery (same issue with 6.4)

Debug log:

[fuse-mountsd v6.3] exFat+NTFS autorepair and mount script (HMkX2 CORE//XDA)
Automated mounting and repair of alternate SD fs on GS3 CM10.1 [+AOSP Roms!]

(1) Checking for MTDblock: (YES)
(2) Checking for mmcblk0: (YES)
(3) Checking for mmcblk1: (YES)
(4) Checking for SECONDARY_STORAGE: (YES)
(5) Checking for EXTERNAL_STORAGE: (YES)
(6) Checking for rw-able /storage: (YES)
(7) Checking for rw-able /: (no)

<<mmcblk1 exists..>>

You are running CM10.1 / 4.2+ ?
Enabling ADB code...

You have teh 4.2.2+ ADB RSA bug -- poor you.
Setting flag to apply the workaround...
31 0 7680 mtdblock0
31 1 7680 mtdblock1
31 2 432128 mtdblock2
31 3 17920 mtdblock3
31 4 12800 mtdblock4
31 5 16384 mtdblock5
31 6 11264 mtdblock6

=====================================
WARNING EXPERIMENTAL METHOD

You are using an OLD phone.
=====================================

major minor #blocks name

31 0 7680 mtdblock0
31 1 7680 mtdblock1
31 2 432128 mtdblock2
31 3 17920 mtdblock3
31 4 12800 mtdblock4
31 5 16384 mtdblock5
31 6 11264 mtdblock6
179 0 7880704 mmcblk0
179 1 5914592 mmcblk0p1
179 2 1966080 mmcblk0p2
179 16 1024 mmcblk0boot1
179 8 1024 mmcblk0boot0
254 0 409600 dm-0
254 1 1552384 dm-1
179 24 31166976 mmcblk1
179 25 31162880 mmcblk1p1
~~
rootfs / rootfs rw,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
tmpfs /storage tmpfs rw,relatime,mode=050,gid=1028 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/secure tmpfs rw,relatime,mode=700 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/fuse tmpfs rw,relatime,mode=775,gid=1000 0 0
/dev/block/mtdblock3 /cache yaffs2 rw,nosuid,nodev,relatime 0 0
/dev/block/mtdblock5 /radio yaffs2 rw,relatime 0 0
/dev/block/mtdblock2 /datadata yaffs2 rw,relatime 0 0
/dev/lvpool/system /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/lvpool/userdata /data ext4 rw,nosuid,nodev,noatime,errors=panic,barrier=1,nomblk_io_submit,data=ordered 0 0
/dev/block/mtdblock4 /efs yaffs2 rw,relatime 0 0
/dev/block/vold/179:1 /storage/sdcard0 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /storage/sdcard0/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
~~
/dev/mapper/lvpool-userdata: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/mapper/lvpool-system: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/mmcblk1p1: UUID="9606-8B98" TYPE="exfat"
/dev/block/vold/179:25: UUID="9606-8B98" TYPE="exfat"
/dev/block/vold/179:1: UUID="8719-1DEB" TYPE="vfat"
/dev/block/dm-1: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/dm-0: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/mmcblk0p1: UUID="8719-1DEB" TYPE="vfat"
~~

/dev/mapper/lvpool-system /system

NOGO Zone set as: ( -e mtdblock -e mmcblk0)
Analyzing /proc/partitions structure:
Index 0 is: 179 24 31166976 mmcblk1
Sub-partition detected at mmcblk1 / mmcblk1p1
Index 1 is: 179 25 31162880 mmcblk1p1

~~~~~~~~~ Beginning FS Logic ~~~~~~~~~
Index (0) - [/dev/block/mmcblk1p1	exfat	mount.exfat-fuse	-o rw,dirsync,noatime,umask=0	fixmyexfat.sh]

~~~~~~~~~ Beginning Test Mount/Repair ~~~~~~~~~
Scrub received for searchSTR ( /storage/sdcard1 )
===== [Cycling /dev/block/mmcblk1p1] =====
Scrub received for searchSTR (/dev/block/mmcblk1p1 )

Attempting test mount of /dev/block/mmcblk1p1 at /mnt/secure/staging:
(/dev/block/mmcblk1p1)(exfat) (mount.exfat-fuse) (-o rw,dirsync,noatime,umask=0) (fixmyexfat.sh)
FUSE exfat 1.0.1
ERROR: invalid VBR checksum 0xfb62032f (expected 0xfb620324).
Test mount failure, reason unknown. (Nonempty? Bad header? Wrong FS?)
BROKEN BROKEN BROKEN - Debug is enabled. Header is as follows:
00000000 eb 76 90 45 58 46 41 54 20 20 20 00 00 00 00 00 |.v.EXFAT .....|
00000010 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
00000040 00 20 00 00 00 00 00 00 00 04 b7 03 00 00 00 00 |. ..............|
00000050 00 08 00 00 c0 1d 00 00 00 28 00 00 70 db 0e 00 |.........(..p...|
00000060 07 00 00 00 98 8b 06 96 00 01 00 00 09 06 01 80 |................|
00000070 00 00 00 00 00 00 00 00 33 c9 8e d1 bc f0 7b 8e |........3.....{.|
00000080 d9 a0 fb 7d b4 7d 8b f0 ac 98 40 74 0c 48 74 0e |...}.}... [MENTION=4468206]t.ht[/MENTION].|
00000090 b4 0e bb 07 00 cd 10 eb ef a0 fd 7d eb e6 cd 16 |...........}....|
000000a0 cd 19 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
000000b0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
00000100 0d 0a 52 65 74 69 72 65 7a 20 6c 65 20 64 69 73 |..Retirez le dis|
00000110 71 75 65 ff 0d 0a 45 72 72 2e 20 64 69 73 71 75 |que...Err. disqu|
00000120 65 ff 0d 0a 50 72 65 73 73 65 7a 20 75 6e 65 20 |e...Pressez une |
00000130 74 6f 75 63 68 65 20 70 6f 75 72 20 72 65 64 82 |touche pour red.|
00000140 6d 61 72 72 65 72 0d 0a 00 00 00 00 00 00 00 00 |marrer..........|
00000150 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
000001b0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ff ff |................|
000001c0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff |................|
*
000001f0 ff ff ff ff ff ff ff ff ff ff ff 00 00 00 55 aa |..............U.|
00000200

Unmounting and running repair command [fixmyexfat.sh]
[fixmyexfat v6.2] exFat header repair tool for CM10.1 + AOSP ROMs (HMkX2 CORE//XDA)
Exponentially less fast and loose than anticipated
Usage: /system/xbin/fixmyexfat.sh <block device, eg /dev/block/mmcblk1p1>
[fixmyexfat] Manual target is /dev/block/mmcblk1p1
Segment 1 (0:4) [ID] -- [eb 76 90 45] -> (eb 76 90 45) (OK)
ff <- [SmartFill Successful!] -> ff
Segment 2 (484:4) [SmartFill] -- [ff ff ff ff] -> (ff ff ff ff) (OK)
[Attempting smartmount search..] -> 00 00 55 aa [00 lead]
Segment 3 (508:4) [Tail] -- [00 00 55 aa] -> (00 00 55 aa)FUSE exfat 1.0.1
ERROR: invalid VBR checksum 0xfb62032f (expected 0xfb620324).
(Fail!)
Segment 3 (508:4) [Tail] -- [1f 2c 55 aa] -> (00 00 55 aa)FUSE exfat 1.0.1
ERROR: invalid VBR checksum 0xfb62032f (expected 0xdb620333).
(Fail!)
Segment 3 (508:4) [Tail] -- [00 00 55 aa] -> (00 00 55 aa)FUSE exfat 1.0.1
ERROR: invalid VBR checksum 0xfb62032f (expected 0xfb620324).
(Fail!)
----> AUTOREPAIR FAILURE. 'I deed what I cood!' <----
Check complete!
Attempting (1) remount, else skipping entirely
FUSE exfat 1.0.1
ERROR: invalid VBR checksum 0xfb62032f (expected 0xfb620324).
I tried. It failed. Removing from mount queue.
Test mount/repair failure. Removing element.
Error! No FUNCTIONAL filesystems after test mounts!
Exiting!

Resetting ADB loopback connection/root security to PRIOR...

# echo $SECONDARY_STORAGE
/storage/sdcard1

Btw, I'm unable to write 00test in /etc/init.d even in root mode through ADB (but the script files are present since installed with CWM): read-only file system.

# blkied
blkied
/system/bin/sh: blkied: not found

EDIT:

Note that running fuse-mountsd.sh actually mangle the SD card (can be restored with chkdsk /f from Windows).

Not mangled Master Boot Record:

0x0000 eb 76 90 45 58 46 41 54-20 20 20 00 00 00 00 00 ëvEXFAT .....
0x0010 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
*
0x0040 00 00 00 00 00 00 00 00-00 1c b7 03 00 00 00 00 .........·.....
0x0050 00 08 00 00 c0 1d 00 00-00 28 00 00 d0 db 0e 00 ....À...(..ÐÛ..
0x0060 07 00 00 00 55 42 4d 72-00 01 00 00 09 06 01 80 ....UBMr.......€
0x0070 00 00 00 00 00 00 00 00-33 c9 8e d1 bc f0 7b 8e ........3ÉŽÑ¼ð{Ž
0x0080 d9 a0 fb 7d b4 7d 8b f0-ac 98 40 74 0c 48 74 0e Ù*û}´}‹ð¬˜ [MENTION=4468206]t.ht[/MENTION].
0x0090 b4 0e bb 07 00 cd 10 eb-ef a0 fd 7d eb e6 cd 16 ´.»..Íëï*ý}ëæÍ
0x00a0 cd 19 00 00 00 00 00 00-00 00 00 00 00 00 00 00 Í..............
0x00b0 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
*
0x0100 0d 0a 52 65 74 69 72 65-7a 20 6c 65 20 64 69 73 ..Retirez le dis
0x0110 71 75 65 ff 0d 0a 45 72-72 2e 20 64 69 73 71 75 queÿ..Err. disqu
0x0120 65 ff 0d 0a 50 72 65 73-73 65 7a 20 75 6e 65 20 eÿ..Pressez une
0x0130 74 6f 75 63 68 65 20 70-6f 75 72 20 72 65 64 82 touche pour red‚
0x0140 6d 61 72 72 65 72 0d 0a-00 00 00 00 00 00 00 00 marrer..........
0x0150 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
*
0x01b0 00 00 00 00 00 00 00 00-00 00 00 00 00 00 ff ff ..............ÿÿ
0x01c0 ff ff ff ff ff ff ff ff-ff ff ff ff ff ff ff ff ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ
*
0x01f0 ff ff ff ff ff ff ff ff-ff ff ff 00 14 22 55 aa ÿÿÿÿÿÿÿÿÿÿÿ."Uª

Mangled Master Boot Record (only the last line changes):

0x0000 eb 76 90 45 58 46 41 54-20 20 20 00 00 00 00 00 ëvEXFAT .....
0x0010 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
*
0x0040 00 00 00 00 00 00 00 00-00 1c b7 03 00 00 00 00 .........·.....
0x0050 00 08 00 00 c0 1d 00 00-00 28 00 00 d0 db 0e 00 ....À...(..ÐÛ..
0x0060 07 00 00 00 55 42 4d 72-00 01 00 00 09 06 01 80 ....UBMr.......€
0x0070 00 00 00 00 00 00 00 00-33 c9 8e d1 bc f0 7b 8e ........3ÉŽÑ¼ð{Ž
0x0080 d9 a0 fb 7d b4 7d 8b f0-ac 98 40 74 0c 48 74 0e Ù*û}´}‹ð¬˜ [MENTION=4468206]t.ht[/MENTION].
0x0090 b4 0e bb 07 00 cd 10 eb-ef a0 fd 7d eb e6 cd 16 ´.»..Íëï*ý}ëæÍ
0x00a0 cd 19 00 00 00 00 00 00-00 00 00 00 00 00 00 00 Í..............
0x00b0 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
*
0x0100 0d 0a 52 65 74 69 72 65-7a 20 6c 65 20 64 69 73 ..Retirez le dis
0x0110 71 75 65 ff 0d 0a 45 72-72 2e 20 64 69 73 71 75 queÿ..Err. disqu
0x0120 65 ff 0d 0a 50 72 65 73-73 65 7a 20 75 6e 65 20 eÿ..Pressez une
0x0130 74 6f 75 63 68 65 20 70-6f 75 72 20 72 65 64 82 touche pour red‚
0x0140 6d 61 72 72 65 72 0d 0a-00 00 00 00 00 00 00 00 marrer..........
0x0150 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
*
0x01b0 00 00 00 00 00 00 00 00-00 00 00 00 00 00 ff ff ..............ÿÿ
0x01c0 ff ff ff ff ff ff ff ff-ff ff ff ff ff ff ff ff ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ
*
0x01f0 ff ff ff ff ff ff ff ff-ff ff ff 00 00 00 55 aa ÿÿÿÿÿÿÿÿÿÿÿ...Uª

Mangled and non-mangled sector 11 and 23 (exfat checksum sector):

NB: This output has been generated with secinspect.exe. It can be downloaded from microsoft here (microsoft.com/en-us/download/details.aspx?id=19470). The command is (m: is the sdcard mounted in an USB hardware adapter):

secinspect -dsec \\.\m: 0 13 > sectordump.txt

LBN 11

0x0000 8f 26 64 fb 8f 26 64 fb-8f 26 64 fb 8f 26 64 fb Å&d¹Å&d¹Å&d¹Å&d¹
*
0x01f0 8f 26 64 fb 8f 26 64 fb-8f 26 64 fb 8f 26 64 fb Å&d¹Å&d¹Å&d¹Å&d¹

The repair of the MBR seems to work, as the debug log shows "14 22 55 aa".

NB: Something's odd when using secinspect: it indicates the MBR at "LBN 2048 [C 0, H 32, S 33]" but checking this sector in particular it is very different than the output. I think it's a bug of secinspect. The real VBR sector is in my opinion LBN 0.

I think where it's starting to bug is here:

Segment 3 (508:4) [Tail] -- [00 00 55 aa] -> (14 22 55 aa)FUSE exfat 1.0.1

ERROR: invalid VBR checksum 0xfb64268f (expected 0xfb642684).

(Fail!)

Segment 3 (508:4) [Tail] -- [1f 2c 55 aa] -> (14 22 55 aa)FUSE exfat 1.0.1

ERROR: invalid VBR checksum 0xfb64268f (expected 0xdb642693).

(Fail!)

Segment 3 (508:4) [Tail] -- [00 00 55 aa] -> (14 22 55 aa)FUSE exfat 1.0.1

ERROR: invalid VBR checksum 0xfb64268f (expected 0xfb642684).

(Fail!)

----> AUTOREPAIR FAILURE. 'I deed what I cood!' <----

This seems to be the checksum of the MBR, which is found in exfat sector 11 (it seems there's a display bug, the bytes order is inversed, but whatever).

Why does the checksums don't match? Windows has no issue with it.

What is the correct checksum ? (what's in the file or what's calculated in the debug info)

More info on checksum calculation here: forum.ntfs.com/discussion/675/exfat-vbr-checksum

It seems there's a patch for Fuse to ignore checksums (groups.google.com/d/msg/exfat/JkjAsCu4Cws/X8SkkeJ5iuIJ) still I've no idea how to apply it on Android and I'm not sure it's the best solution...