[GUIDE] How to enable Camera2 API persistently and keep bootloader locked

[flex1911]

Hello everyone. I'm pretty sure that there are a plenty of people that are rooting and unlocking their A1 just to enable Camera2 API (just like me).
But formally you can enable and make it persistent without unlocking bootloader and rooting.
Why "formally"? Because you will actually need to unlock and root during the process, but then you can relock your bootloader and forget about it until you will wipe your /data. Yes, Camera2 API will remain enabled after relocking and will persist even after OTA updates.

1. If you already didn't, unlock the bootloader and root your phone by Magisk using this guide.
2. Enable ADB in the developer settings.
3. Assuming you already have platform-tools binaries, do this in your shell/cmd:

adb shell

Now, when you are in the device shell, type this:

su

The device will probably ask about root access, grant it.
Now, when you are in the root shell, type this:

setprop persist.camera.HAL3.enabled 1

4. Reboot and make sure that Camera2 API works for you now.
5. Go to Magisk manager and completely uninstall Magisk here.
6. Reboot and make sure that your system boots properly.
7. Reboot to bootloader:

adb reboot-bootloader

8. Relock your bootloader:

fastboot oem lock

Done! Now you have permanently enabled Camera2 API without messing OTA and security measures.

THIS DOESN'T TOUCH SYSTEM FILES AT ALL AND HAS NOTHING TO DO WITH BUILD.PROP

 

[Ammo thind]

Hello everyone. I'm pretty sure that there are a plenty of people that are rooting and unlocking their A1 just to enable Camera2 API (just like me).
But formally you can enable and make it persistent without unlocking bootloader and rooting.
Why "formally"? Because you will actually need to unlock and root during the process, but then you can relock your bootloader and forget about it until you will wipe your /data. Yes, Camera2 API will remain enabled after relocking and will persist even after OTA updates.

1. If you already didn't, unlock the bootloader and root your phone by Magisk using this guide.
2. Enable ADB in the developer settings.
3. Assuming you already have platform-tools binaries, do this in your shell/cmd:

adb shell

Now, when you are in the device shell, type this:

su

The device will probably ask about root access, grant it.
Now, when you are in the root shell, type this:

setprop persist.camera.HAL3.enabled 1

4. Reboot and make sure that Camera2 API works for you now.
5. Go to Magisk manager and uninstall Magisk here.
6. Reboot to bootloader:

adb reboot-bootloader

7. Relock your bootloader:

fastboot oem lock

Done! Now you have permanently enabled Camera2 API without messing OTA and security measures.

Is it true

Sent from my Mi A1 using Tapatalk

 

[AridaneAM]

Have you tried it? When updating the OTA build.prop in system is not rewrited? What is the difference with replace build.prop in twrp? When I tried it the OTA didn't upload because the edited system partition.

Enviado desde mi Mi A1 mediante Tapatalk

 

[dipakd]

Can you give me the platform-tools binaries? Or link for that

 

[Ammo thind]

Hello everyone. I'm pretty sure that there are a plenty of people that are rooting and unlocking their A1 just to enable Camera2 API (just like me).
But formally you can enable and make it persistent without unlocking bootloader and rooting.
Why "formally"? Because you will actually need to unlock and root during the process, but then you can relock your bootloader and forget about it until you will wipe your /data. Yes, Camera2 API will remain enabled after relocking and will persist even after OTA updates.

1. If you already didn't, unlock the bootloader and root your phone by Magisk using this guide.
2. Enable ADB in the developer settings.
3. Assuming you already have platform-tools binaries, do this in your shell/cmd:

adb shell

Now, when you are in the device shell, type this:

su

The device will probably ask about root access, grant it.
Now, when you are in the root shell, type this:

setprop persist.camera.HAL3.enabled 1

4. Reboot and make sure that Camera2 API works for you now.
5. Go to Magisk manager and uninstall Magisk here.
6. Reboot to bootloader:

adb reboot-bootloader

7. Relock your bootloader:

fastboot oem lock

Done! Now you have permanently enabled Camera2 API without messing OTA and security measures.

Editing prop file will make sure that there is no ota

Sent from my Mi A1 using Tapatalk

 

[flex1911]

Have you tried it? When updating the OTA build.prop in system is not rewrited? What is the difference with replace build.prop in twrp? When I tried it the OTA didn't upload because the edited system partition.

Enviado desde mi Mi A1 mediante Tapatalk

persist props are being stored in /data/property, so it doesn't touch build.prop at all.

 

[black_arashi]

Hello,

I doubt that this will work with funtional OTA, modificating the build.prop it's modificate system, so it should't have working OTA. If we use Magisk and the modules to enable camera2api and hal3 it's because it doesn't modify system. Anyway, if someone try it and corroborate it work great with OTA, I will retract my self.

Regards

 

[flex1911]

Hello,

I doubt that this will work with funtional OTA, modificating the build.prop it's modificate system, so it should't have working OTA. If we use Magisk and the modules to enable camera2api and hal3 it's because it doesn't modify system. Anyway, if someone try it and corroborate it work great with OTA, I will retract my self.

Regards

As I stated above, it doesn't modificate any system files at all.

 

[Apih95]

Welcome @flex1911 from zenfone 2 forum :fingers-crossed:

 

[Haizum74]

I am currently waiting for delivery of my Mi A1 (hopefully today) and will give this a go and report back.

For people questioning this, build.prop is only one of a number of read only files that are used when setting up after reboot so I can see why this would potentially work. Not a dev myself, but understand the basics.


PS Its modify not modificate

 

[unixbrain]

Step 5 should be only Magisk application uninstall and not a complete uninstall right?

 

[mahfoozceecy]

Removed.

 

[unixbrain]

It works but before locking back the bootloader you must let Android to boot the system.
If you lock the bootloader just after uninstalling Magisk it will end up with a "System has been destroyed" error

 

[flex1911]

The OP heading reads "How to enable HAL3 without unlocking and root". Then, in the post you are telling people to Unlock and Root via Magisk !

What's going on ?

Anyway, if someone knows how to Magisk and root, then for sure, he or she would know how to use a simple magisk module to enable HAL3.

You probably didn't get the point at all.

 

[Rajeev]

The OP heading reads "How to enable HAL3 without unlocking and root". Then, in the post you are telling people to Unlock and Root via Magisk !

What's going on ?

Anyway, if someone knows how to Magisk and root, then for sure, he or she would know how to use a simple magisk module to enable HAL3.

Whats going on with u too? Why quoting the full damn OP?

 

[flex1911]

It works but before locking back the bootloader you must let Android to boot the system.
If you lock the bootloader just after uninstalling Magisk it will end up with a "System has been destroyed" error

Yeah, thx. Updated the post to make it more obvious.

 

[Rajeev]

Yeah, thx. Updated the post to make it more obvious.

U mean complete uninstall Magisk or ?

 

[unixbrain]

Yes. You can completely uninstall Magisk.

Sent from my Mi A1 using Tapatalk

 

[mahfoozceecy]

You probably didn't get the point at all.

The OP Heading should have read "Enable HAL3 without Editing Build.prop and Keep the OTA" .. along those lines.

 

[joeyhuab]

The OP Heading should have read "Enable HAL3 without Editing Build.prop and Keep the OTA" .. along those lines.

The heading doesn't matter if you read the OP itself. It's simple reading comprehension to be honest. Basically you don't edit build.prop, still get the OTA and add Camera2 API.