Android Dual Boot Patcher: exFAT driver issue? about exfat HOT 9 CLOSED

To be honest, I have no idea what is Dual Boot Patcher. How exactly does it use fuse-exfat?

Could you get the log from fuse-exfat? It prints errors into syslog, but it seems that Android does not have it. Hint: make logging functions in libexfat/log.c use __android_log_vprint.

from exfat.

Here you can read about Dual Boot Patcher:
https://dbp.noobdev.io
It makes possible to install multiple ROMs onto the same Android phone.

One solution is to flash the ROM external sdcard. Since my sdcard is 64GB, it should use exFAT.
Well, if it is formatted to exFAT, then gives the errors above.
However, if I format to FAT32, then boots without problems.
This is why I thought, that exFAT driver may cause the problem.

Personally I don't develop in C++, so I don't know how to implement your suggestion.

But if I get exact code, I will implement into the Dual Boot Patcher code and compile it.

I know that I should place the debugging code into mount_fstab.cpp, under method mount_fstab():
https://github.com/chenxiaolong/DualBootPatcher/blob/e3366791f3ff06aa46a26f354e298fe43fc99ecb/mbtool/mount_fstab.cpp

from exfat.

The following issue is discussing the problem:
chenxiaolong/DualBootPatcher#375

from exfat.

Here you can read about Dual Boot Patcher: https://dbp.noobdev.io

There's zero info about its internals.

But if I get exact code, I will implement into the Dual Boot Patcher code and compile it.

Good time for you to start learning C. :) In libexfat/log.c:

• replace vsyslog(LOG_ERR, format, aq); with __android_log_vprint(ANDROID_LOG_ERROR, "exfat", fmt, aq);
• add #include <android/log.h>

from exfat.

@relan: I saw the android branch. Is it finished? Will it be merged into next release?

from exfat.

The external 64Gb sdcard now was formatted using TWRP v3.0.2 to exFAT.

Attaching logs about kernel booting process.

I see the following in /multiboot/sdcard/logs/kmsg.log:

<3>[    9.297454] mblog: 1 fstab entries for the external SD
<3>[    9.297576] mblog: [Attempt 1/10] Finding and mounting external SD
<3>[    9.297790] mblog: Matching devices against pattern: /devices/platform/msm_sdcc.2/mmc_host/mmc2*
<3>[    9.301574] mblog: /default.prop contains fuse-exfat override: false
<6>[    9.312347] synaptics_rmi4_i2c 3-0020: synaptics_init_power_on: until lcd does not turn on.
<3>[    9.391937] mblog: Using fuse-exfat: 0
<3>[    9.392089] mblog: Failed to mount /dev/block/mmcblk1p1 (exfat) at /raw/extsd: No such device
<3>[    9.395996] mblog: /default.prop contains fuse-exfat override: false
<3>[    9.482238] FAT-fs (mmcblk1): invalid media value (0x01)
<6>[    9.482330] FAT-fs (mmcblk1): Can't find a valid FAT filesystem
<3>[    9.482757] mblog: Failed to mount /dev/block/mmcblk1 (vfat) at /raw/extsd: Invalid argument
<6>[   10.312316] synaptics_rmi4_i2c 3-0020: synaptics_init_power_on: until lcd does not turn on.
<3>[   10.483032] mblog: [Attempt 2/10] Finding and mounting external SD
<3>[   10.483215] mblog: Matching devices against pattern: /devices/platform/msm_sdcc.2/mmc_host/mmc2*
<3>[   10.486938] mblog: /default.prop contains fuse-exfat override: false
<3>[   10.577423] mblog: Using fuse-exfat: 0
<3>[   10.577606] mblog: Failed to mount /dev/block/mmcblk1p1 (exfat) at /raw/extsd: No such device
<3>[   10.581420] mblog: /default.prop contains fuse-exfat override: false
<3>[   10.667724] FAT-fs (mmcblk1): invalid media value (0x01)
<6>[   10.667816] FAT-fs (mmcblk1): Can't find a valid FAT filesystem
<3>[   10.668151] mblog: Failed to mount /dev/block/mmcblk1 (vfat) at /raw/extsd: Invalid argument
<6>[   10.912353] max77693-muic max77693-muic: func:max77693_muic_usb_detect info->muic_data->sw_path:0
<6>[   11.312316] synaptics_rmi4_i2c 3-0020: synaptics_init_power_on: until lcd does not turn on. 

Does it help you?
kmsg.log.txt
20170328.084614.tar.gz

from exfat.

I saw the android branch. Is it finished?

It's a work-in-progress.

Will it be merged into next release?

It depends. I need to test those changes before I merge them.

Does it help you?

I'm afraid no. I don't see any error messages from fuse-exfat here.

from exfat.

No new info for over a year, closing.

from exfat.

I will reopen the issue if I will have time to test exFAT again.

from exfat.