Upgrade to Monterey and failed to boot(MacBook Pro (16-inch, 2019)

Woohoo! After a beer during night, I decided to have another try. After a bit google, I found pdisk and gdisk. And gdisk is really what I need, it has t function to "change a partition's type code", I change my partition from AF00 to AF0A, my partition is back!

* https://sourceforge.net/projects/gptfdisk/

I think I know why fsck_hfs got called instead of fsck_apfs.

=====

sudo diskutil list /dev/disk2

/dev/disk2 (external):

   #:                       TYPE NAME                    SIZE       IDENTIFIER

   0:      GUID_partition_scheme                         1.0 TB     disk2

   1:                        EFI ⁨EFI⁩                     314.6 MB   disk2s1

   2:                  Apple_HFS ⁨⁩                        749.0 GB   disk2s2

                    (free space)                         251.2 GB   -

=====

Made a Ubuntu 21.10 USB bootable disk, it works fine with MacBook Pro 2015.

But on the broken MacBook Pro 2019 with T2(and Touch Bar), I can select the EFI Boot after Option boot, then it goes to black screen...

And Ubuntu 21.10 running on mbp2015 host, can't read Target Harddisk mode on mbp2019.

Is there anyone knows how to use diskutil or gpt or other tools on macOS to modify hard disk partition table, change the partition type from HFS partition to APFS Container? like fdisk/t things on Linux? Thanks a lot.

Thanks for Mike Boreham's suggestion.

I made a USB installer of Monterey. I can use it to boot into mbp 2019.

But it still considers that partition as a HFS partition instead of APFS containter. So not much difference with boot from Internet Recovery(Catalina).

* https://mrmacintosh.com/macos-12-monterey-full-installer-database-download-directly-from-apple/

* https://mrmacintosh.com/how-to-create-a-bootable-macos-12-beta-usb-drive-in-5-min/

BTW, This post synced with https://forums.macrumors.com/threads/upgrade-to-monterey-and-failed-to-boot-macbook-pro-16-inch-2019.2322174/

Have tried to call local telephone support yesterday, but didn't resolve yet...

Visited a local service provider yesterday, they can't give solution to fix it. Only said that I need to pay about 200$ to get the data back if possible.