Challenge: Interesting Fastboot Output

All I did was fastboot -w = a factory reset. This is the output:

`C:\Users\tripleu>fastboot -w
Erasing 'userdata'                                 OKAY [  0.199s]

    F2FS-tools: mkfs.f2fs Ver: 1.16.0 (2023-04-11)

Info: Debug level = 1
Info: Trim is disabled
Info: Set conf for android
Info: Enable Project quota
Info: Segments per section = 1
Info: Sections per zone = 1
Info: sector size = 512
Info: total sectors = 23879640 (11659 MB)
Info: zone aligned segment0 blkaddr: 512
Info: add quota type = 0 => 4
Info: add quota type = 1 => 5
Info: add quota type = 2 => 6
Info: format version with
  ""
[f2fs_init_sit_area: 714]       Filling sit area at offset 0x00600000
[f2fs_init_nat_area: 748]       Filling nat area at offset 0x00a00000
[f2fs_add_default_dentry_root:1364]     Writing default dentry root, at offset 0x5c00
[f2fs_write_root_inode:1410]    Writing root inode (hot node), offset 0x5600
[f2fs_write_default_quota:1502]         Writing quota data, at offset 00005c01 (1/2)
[f2fs_write_default_quota:1502]         Writing quota data, at offset 00005c02 (2/2)
[f2fs_write_qf_inode:1553]      Writing quota inode (hot node), offset 0x5601
[f2fs_write_default_quota:1502]         Writing quota data, at offset 00005c03 (1/2)
[f2fs_write_default_quota:1502]         Writing quota data, at offset 00005c04 (2/2)
[f2fs_write_qf_inode:1553]      Writing quota inode (hot node), offset 0x5602
[f2fs_write_default_quota:1502]         Writing quota data, at offset 00005c05 (1/2)
[f2fs_write_default_quota:1502]         Writing quota data, at offset 00005c06 (2/2)
[f2fs_write_qf_inode:1553]      Writing quota inode (hot node), offset 0x5603
[f2fs_update_nat_default:1591]  Writing nat root, at offset 0x00000a00
Info: Overprovision ratio = 1.370%
Info: Overprovision segments = 85 (GC reserved = 79)
[f2fs_write_check_point_pack: 939]      Writing main segments, cp at offset 0x00000200
[f2fs_write_check_point_pack:1027]      Writing Segment summary for HOT/WARM/COLD_DATA, at offset 0x00000201
[f2fs_write_check_point_pack:1041]      Writing Segment summary for HOT_NODE, at offset 0x00000202
[f2fs_write_check_point_pack:1053]      Writing Segment summary for WARM_NODE, at offset 0x00000203
[f2fs_write_check_point_pack:1067]      Writing Segment summary for COLD_NODE, at offset 0x00000204
[f2fs_write_check_point_pack:1075]      Writing cp page2, at offset 0x00000205
[f2fs_write_check_point_pack:1095]      Writing NAT bits pages, at offset 0x000003ff
[f2fs_write_check_point_pack:1117]      Writing cp page 1 of checkpoint pack 2, at offset 0x00000400
[f2fs_write_check_point_pack:1136]      Writing cp page 2 of checkpoint pack 2, at offset 0x00000405
[f2fs_write_super_block:1169]   Writing super block, at offset 0x00000000
Info: format successful
libc++abi: terminating due to uncaught exception of type std::out_of_range: basic_string`

Whoever can decrypt the output gets a fastboot masters badge!

What device is this on?

Cat S22 flip

This is from AI…

The output you’re seeing is from the fastboot -w command, which erases and reformats the /data (userdata) partition on your CAT S22 Flip. Here’s a breakdown:

Key Stages in the Output:

  1. Erasing Userdata:
    Erasing 'userdata' OKAY confirms deletion of the previous data partition.

  2. F2FS Formatting:
    Your device uses F2FS (Flash-Friendly File System) for the /data partition, optimized for flash storage. The tool mkfs.f2fs (v1.16.0) is reformatting the partition:

    • Partition Size: 11.66 GB (11,659 MB).
    • Android-Specific Config: Project quotas enabled (for storage management).
    • Trim Disabled: Not critical here (trim optimizes flash memory wear).
  3. File System Structures:
    The tool creates essential F2FS structures:

    • SIT (Segment Information Table): Tracks data block status.
    • NAT (Node Address Table): Manages file/directory metadata.
    • Quota Setup: For Android’s storage limits (user/group/project quotas).
    • Checkpoint Pack: Ensures filesystem consistency.
    • Superblock: Critical metadata about the filesystem.
  4. Successful Format:
    Info: format successful confirms the F2FS partition was created correctly.


The Error at the End:

libc++abi: terminating due to uncaught exception of type std::out_of_range: basic_string

  • Cause: A bug in the fastboot tool itself (not your device or command).
  • Why it happens: The tool mishandles internal data after successful formatting (likely a string/index error).
  • Impact: Harmless since formatting completed (OKAY and format successful appeared first). Your /data partition is fully wiped and ready for use.

Recommended Actions:

  1. Reboot Your Device:
    Run fastboot reboot to restart the phone. The new F2FS partition will be initialized on boot.

  2. Update Platform-Tools:
    Download the latest Android SDK Platform-Tools to fix the fastboot bug.

  3. Verify Functionality:
    After reboot, your phone should behave like a factory-reset device (no OS damage). If issues persist, reflash the stock firmware.


Why fastboot -w Triggers This:

  • The -w flag specifically targets the userdata and cache partitions. Here, it successfully wiped /data and reinitialized F2FS. The exception is a cosmetic glitch in the fastboot binary.

then AI gets the badge…

2 Likes

:rofl: :rofl: :rofl:

And the brains one

lol