MTK META Utility V60
Added Samsung A32 5G (A326U) BIT 7 any Rev, fix bricked
(stuck at BROM port after service or try to unlock with other tool, (corrupted/damaged)
Primary Boot Region Container (LU-0) & USER_PART PMT (P-GPT).
3 files stored Inside software resources will be used to service your device (LU-0 & P-GPT & PIT).
This software is provided ‘as-is’, without any express or implied warranty.
In no event will the authors be held liable for any damages arising from the use of this software, and
can be only used for legal servicing and maintenance of mobile phones, and must not be used for illegal purposes.
-USE it at your own risk.
Note : It’s about VIVO September (BETA/TRAIL) update, not August update,
in August update there were some ways to get Boot-ROM port : D
– Regarding VIVO MTK devices with MT6765 chipset, they have rolled out an update,
which disable Boot-ROM completely by FUSE, same as recent (Samsung visible [SEC CTRL] flag case).
– Undoubtedly, the updates may not be without some (side effects/damages),
considering the Boot-ROM code set to be fundamentally and
definitively approved by the phones (manufacturers/after-sales services).
– As expected, we have seen they have the ability to change the registered DA signature in
preloader code by simple hot-patch, and maybe they will manage to do the same for Boot-ROM mode
(even after the exploitation and bypass vendor security step) in the near future maybe, just assuming
they’re considering the replacement for the already burned fuses and registers which affect the
(early registered op-code), and no way to replace it with (hot-patches), means in near future even
if you managed to get Boot-ROM (Emergency Download mode) somehow the
(Boot-ROM Auth vulnerability – voltage glitching) might be patched as well.
– The FUSE can’t be reverted, because it’s BIT registers & e-FUSES control the SoC with a
special flag SET by the (Manufacturer/OEM), to be (handled/controlled) by (RPMB/FUSE/SoC bounded)
MTK META Utility V60
It depends on many factors known to the (manufacturer/source code writer).
– We all know the idea of the HW TEST-POINT in general for mobile (phones/test-boards),
which is *preventing the CPU from detecting the MEMORY forced by shorting any of the
important data lines which used for data (transfer/connection/configure) to the Ground* for FPGA setup case,
so blocking the CPU from detecting the MEMORY wouldn’t help to get
(Boot-ROM/Preloader port – any U-ART configure/handler), means
TEST-POINT is useless in case if the e-FUSES were activated.
– The googled definition of the TEST-POINT is (In the world of electronics,
a TEST-POINT is a gate or point that has a vital function as a single track or point as a tester as well as a
protection key for the overall performance of the module or digital electronic device).
– All this information based on my recent research, and my little humble background
of hardware stuffs in general, and might be (right/wrong) in some cases, if so please correct me.
Just for Info :
August patch (01.08.2022) can be handled somehow by downgrading the security,
but September patch [(01.09.2022) – (06.09.2022)] no way to handle because of EFUSES,
no way to get bootrom port under any condition.