Now you can unlock Galaxy Z Fold 3 bootloader without losing access to the camera

According to a recent report, Samsung will no longer block access to the camera for anyone trying to unlock the Galaxy z fold 3 bootloader in the latest beta of One UI 4.

Unlocking a mobile device’s bootloader is something curious technicians as well as software developers have been doing for a long time, as it gives them the ability to install alternative operating systems or manipulate the system’s software. ‘phone operation, creating their own personal settings and aftermarket developments.

Bootloaders are a part of any operating system across the board and are by no means exclusive to Android devices. However, each Android phone manufacturer develops their own bootloader, which is specific to the hardware range of each specific phone.
the The Galaxy Z Fold 3, like all interesting new flagships, has already attracted many budding and professional software developers to unlock its bootloader to play with and modify the software. But initially, they quickly found out that Samsung had some unusual safeguards in place to prevent this kind of exploration, blocking all access to the device’s camera features.
This turned out to be an annoying obstacle for a while, as the experimenters simply had no way to access or play with one of the coolest features of a phone, namely the camera. . It would just disappear from settings and lose all functionality when unlocking the device’s bootloader.
The welcome removal of this limitation, however, has just been discovered by a senior member of XDA, which revealed that starting with the second beta of One UI 4, bootloader unlocks will no longer lose camera functionality when they experience the Galaxy Z Fold 3.

However, this fix does not yet apply to all Galaxy Z Fold 3 users across the world, as it seems that US citizens are still facing the same issue, while many international owners are already enjoying the new found freedom. .

If you are currently experimenting with Galaxy Z Fold 3 bootloader, you can check out the XDA forum discussion if the fix has reached your region yet.


Source link

Comments are closed.