Camera2Api disabled on reboot - Xiaomi Redmi Note 5 Pro Questions & Answers

I have a Redmi note 5 (whyred) arb4 with stock MIUI
Bootloader unlocked, TWRP recovery and magisk installed
The magisk module does nothing, I have it activated but it does nothing, the only way i've found to enable the gcam is flashing through recovery but it gets disabled on the next reboot.

Magsik module enabling Camera2 API is not working for me either. While other modules work.
I can enable it by flashing in recovery (OrangeFox), and after a reboot, it still works. Quite strange.

Related

I have problems with wifi and magisk in xiaomi rednote 4 snapdragon

I have problems with wifi. What I did before was the boot.img loaded by TWRP And then the magisk installed without problems. But I turned off the wifi, and I can not give you check because it is returned to off. What can be done?
I have installed the last TWRP and magisk, I occupy this rom "mido_global_images_V9.2.1.0.NCFMIEK_20180113.0000.00_7.0_global" and its boot.img to be able to load and install the magisk
Pd: My Phone is a Xiaomi redmi note 4 snapdragon.

Magisk not working on MIUI 8.3.22 Global Dev rom

I've upgraded from MIUI 8.3.8 to 8.3.22 Global Dev rom recently. Magisk v16 was working well before on 8.3.8. But after updating, it stuck on boot loading screen. I've tried to use magisk v14, v15.3 and even Danward's Magisk v16.3 and still no success. The only way for me to boot my device is by flashing the stock boot.img and use my device without root and magisk.
How do we get Magisk v16 working with MIUI 8.3.22 Global Dev?
vulturext said:
I've upgraded from MIUI 8.3.8 to 8.3.22 Global Dev rom recently. Magisk v16 was working well before on 8.3.8. But after updating, it stuck on boot loading screen. I've tried to use magisk v14, v15.3 and even Danward's Magisk v16.3 and still no success. The only way for me to boot my device is by flashing the stock boot.img and use my device without root and magisk.
How do we get Magisk v16 working with MIUI 8.3.22 Global Dev?
Click to expand...
Click to collapse
Boot after you've flashed the Rom without flashing magisk, then flash twrp by Fastboot again (will be lost), then flash magisk, will work, been there on mi5 and 6.
Regards.
Sent from my MI 6 using Tapatalk

Camera 2api

Hi,I want to enable camera2api from twrp and remove twrp after enabling camera2api and flash mi stock recovery it is possible

[ROOT] Working Magisk 18.2 for Mix 3

Just tried to Change my Update Channel in Magisk Manager to : "https://github.com/ianmacd/MagiskBuilds"
installed Manager 7.0.1 and flashed latest Magisk 18.2 build and finally its working with SafetyNet passed !
woif36 said:
Just tried to Change my Update Channel in Magisk Manager to : "https://github.com/ianmacd/MagiskBuilds"
installed Manager 7.0.1 and flashed latest Magisk 18.2 build and finally its working with SafetyNet passed !
Click to expand...
Click to collapse
What MIUI version are you on? Global/chinese/EU hardware and ROM?
I have installed the 18.1 version With Magisk 7.0 on EU Stable rom 10.2.2.0
Tested on EU Weekly 9.2.21 and it seems to work on that too, passes SafetyNet
anyone can send me the file in different way/different link from gifthub because proxy in my company block it? Thank you
Who bans github?! Anyway, here you go
by the way.. who is ianmacd?
what changed for 18.2? unofficially
Rockmadeofrock said:
What MIUI version are you on? Global/chinese/EU hardware and ROM?
Click to expand...
Click to collapse
Global Hardware and Xiaomi.eu ROM.
When hiding Magisk Manager in Settings and Reboot Jailbreak Detection of Apps seems bypassed. (tested on Paypal)
Hi
Maybe a noob question, but I'm new to Xiaomi and I can't find a proper response for the Mi Mix 3
If I want to Disable Dm-Verity and ForceEncryption, I found Disable_Dm-Verity_ForceEncrypt_02.04.2019
Also I download the new Magisk 18.2 that I found for the Mi Mix 3
I already unlocked the bootloader
I installed TWRP, Wiped (System, data, everything) then Flashed the newest rom with XiaoMIFlash, before it rebooted I reboot to fastboot, Installed TWRP, copied the files, installed first Disable_Dm-Verity_ForceEncrypt_02.04.2019, then Magisk, then I reboot to system, it starts the phone from the initial setup, after I setup everything I checked and no magisk was installed, and in Security Encryption is still enabled, I reboot again to recovery and again it asks for the decryption password, tried to install magisk still no luck after reboot
If I try to only install Magisk 18.2 it works, but how I can disable Force Encrypt
plz help
I have the Mi Mix 3 Global version with the lastest ROM
Anyone tried Chinese hardware with global rom?
Try the Canary builds, the even work with banking apps that usually do not work with root.
They can be unstable but worked with every Rom so far for me
If you install the latest EU stable ROM (10.3.1) you can simply update Magisk Manager and Magisk itself to the latest version (7.3.2 and 19.3) without any problems and it works like a charm

Camera2API Modules Not Applied on Boot

Hi,
I have a 'weird' problem:
I installed Magisk some time ago on my Redmi Note 5 Pro (Global).
Now I'm on version 19.3 (updated today).
I also installed two Magisk modules in order to unlock Camera2API and some stuff for the camera (nhappyman Camera patch).
I recently received and installed the latest global stable build, Android 8.1.
I reinstalled TWRP recovery in order to install also the Magisk zip.
BUT now I don't understand why I don't have Camera2API.
I see the modules activated;
I also see that Magisk is activated and it's on the latest version;
I disabled and enabled again the module but nothing changes.
The only thing I can do in order to make Camera2API work is:
Reboot into TWRP;
Install Magisk, AGAIN;
Wipe Dalvik and cache;
Reboot.
It will work until next reboot.
If I reboot the phone, Magisk modules will not work at all.
The problem is that Magisk modules seems working on Magisk but if I try to open GCam keeps crashing.
So, what can I do? Can you help me please?
P.S.: It was already unlocked when I bought it.
Thanks
-Alex
Download build prop editor and search for
persist.vendor.camera.HAL3.enabled
And change to 1
rounakr94 said:
Download build prop editor and search for
persist.vendor.camera.HAL3.enabled
And change to 1
Click to expand...
Click to collapse
I updated build.prop adding this line.
It works.
Thanks
-Alex

Categories

Resources