Instructions do not work.

[dogzipp]

I've tried two computers, two SD cards, and two different USB cables. (using Macos)

I run through all the script commands, I allways end up with:

Can't load Android system. Your data may be corrupt. If you continue to get this message you may need to perform a factory reset and erase all user date stored on this device.

I do notice some errors toward the end of the script, not sure if perhaps that's the culprit:

fastboot format:ext4 userdata
Warning: userdata type is raw, but ext4 was requested for formatting.
/usr/local/bin/mke2fs failed with status 1
fastboot: error: Cannot generate image for userdata

fastboot format:ext4 metadata
Warning: metadata type is raw, but ext4 was requested for formatting.
/us/local/bin/mke2fs failed with status 1
fastboot: error: Cannot generate image for metadata

Any help appreciated.

[iKrushYou]

I am seeing the same issue here

on MacOS 12

➜  tesla-android-2022 fastboot devices
100000009102ee05	fastboot
➜  tesla-android-2022  fastboot flash gpt deploy-gpt.img
 fastboot flash bootloader bootloader-sd.img
 fastboot flash uboot-env  env.img
 fastboot reboot

Sending 'gpt' (128 KB)                             OKAY [  0.011s]
Writing 'gpt'                                      OKAY [  0.029s]
Finished. Total time: 0.088s
Invalid sparse file format at header magic
Sending sparse 'bootloader' 1/1 (9132 KB)          OKAY [  0.360s]
Writing 'bootloader'                               OKAY [  8.984s]
Finished. Total time: 9.470s
Sending 'uboot-env' (256 KB)                       OKAY [  0.017s]
Writing 'uboot-env'                                OKAY [  0.027s]
Finished. Total time: 0.085s
Rebooting                                          OKAY [  0.000s]
Finished. Total time: 0.000s
➜  tesla-android-2022  fastboot oem format
 fastboot flash bootloader      bootloader-sd.img
 fastboot flash uboot-env       env.img
 fastboot flash boot            boot.img
 fastboot flash vendor_boot     vendor_boot.img
 fastboot flash dtbo_a          boot_dtbo.img
 fastboot erase misc
 fastboot reboot-fastboot

OKAY [  0.019s]
Finished. Total time: 0.019s
Invalid sparse file format at header magic
Sending sparse 'bootloader' 1/1 (9132 KB)          OKAY [  0.349s]
Writing 'bootloader'                               OKAY [  9.498s]
Finished. Total time: 9.991s
Sending 'uboot-env' (256 KB)                       OKAY [  0.015s]
Writing 'uboot-env'                                OKAY [  0.027s]
Finished. Total time: 0.125s
Invalid sparse file format at header magic
Sending sparse 'boot_a' 1/2 (15276 KB)             OKAY [  0.597s]
Writing 'boot_a'                                   OKAY [  2.250s]
Sending sparse 'boot_a' 2/2 (2228 KB)              OKAY [  0.092s]
Writing 'boot_a'                                   OKAY [  3.468s]
Finished. Total time: 6.487s
Invalid sparse file format at header magic
Sending sparse 'vendor_boot_a' 1/1 (10716 KB)      OKAY [  0.403s]
Writing 'vendor_boot_a'                            OKAY [  2.921s]
Finished. Total time: 3.384s
Sending 'dtbo_a' (51 KB)                           OKAY [  0.007s]
Writing 'dtbo_a'                                   OKAY [  0.043s]
Finished. Total time: 0.159s
Erasing 'misc'                                     OKAY [  0.032s]
Finished. Total time: 0.140s
Rebooting into fastboot                            OKAY [  0.029s]
< waiting for any device >
Finished. Total time: 29.759s
➜  tesla-android-2022  fastboot flash super  super.img

Invalid sparse file format at header magic
Sending sparse 'super' 1/6 (262140 KB)             OKAY [  8.351s]
Writing 'super'                                    OKAY [ 10.151s]
Sending sparse 'super' 2/6 (262116 KB)             OKAY [  8.367s]
Writing 'super'                                    OKAY [ 10.071s]
Sending sparse 'super' 3/6 (236224 KB)             OKAY [  7.446s]
Writing 'super'                                    OKAY [  9.556s]
Sending sparse 'super' 4/6 (262140 KB)             OKAY [  8.296s]
Writing 'super'                                    OKAY [ 10.145s]
Sending sparse 'super' 5/6 (262140 KB)             OKAY [  8.304s]
Writing 'super'                                    OKAY [ 10.360s]
Sending sparse 'super' 6/6 (3028 KB)               OKAY [  0.102s]
Writing 'super'                                    OKAY [ 47.095s]
Finished. Total time: 139.878s
➜  tesla-android-2022  fastboot format:ext4 userdata

Warning: userdata type is raw, but ext4 was requested for formatting.
/usr/local/bin/mke2fs failed with status 1
fastboot: error: Cannot generate image for userdata

[iKrushYou]

I have resolved this issue

The problem was caused by how I made the platform-tools commands available to the system.
I had just created a symlink for both adb and fastboot but that doesn't include mke2fs which is the issue

So, as a solution:

1. remove all symlinks made (or any executables you put in your bin folder)
2. export PATH=$PATH:/Applications/platform-tools or wherever you have your platform-tools folder stored
3. try again fastboot format:ext4 userdata

➜  tesla-android-2022 fastboot format:ext4 userdata                   
Warning: userdata type is raw, but ext4 was requested for formatting.
mke2fs 1.46.2 (28-Feb-2021)
Creating filesystem with 14537211 4k blocks and 3637248 inodes
Filesystem UUID: 951ed8d3-22b3-4efe-88ae-7c0f586edb15
Superblock backups stored on blocks: 
	32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 
	4096000, 7962624, 11239424

Allocating group tables: done                            
Writing inode tables: done                            
Creating journal (65536 blocks): done
Writing superblocks and filesystem accounting information: done   

Sending 'userdata' (312 KB)                        OKAY [  0.017s]
Writing 'userdata'                                 OKAY [  0.048s]
Finished. Total time: 0.460s

[geog99]

Hello :) I had the same issue and I did follow the instructions of the solution and am still getting the mke2fs failed with Status 1 message. I have the most recent SDK platform tools and a M1 Mac running OSX 12.6. Any other tips?

[geog99]

Disregard.. apparently Mac defaults to not Terminal not having full disk access.. turned that on and voila :)