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
Related
I tested most Nougat custom roms. (except Oxygen 4.0.x)
However, none of them worked with Magisk + Phh Superuser. (can't get root access)
(data,cache filesystem : F2FS)
anyone else?
please help...
--
It worked on Sultan's CM13. (MM)
smk513 said:
I tested most Nougat custom roms. (except Oxygen 4.0.x)
However, none of them worked with Magisk + Phh Superuser. (can't get root access)
(data,cache filesystem : F2FS)
please help...
--
It worked on Sultan's CM13. (MM)
Click to expand...
Click to collapse
Magisk v9 + Phh was working fine a month ago when I was using CM14.1.
Don't know which custom roms you were using but many of them have root already included, so you'll have to remove the SU that's included in the ROM before you Magisk + Phh.
Order I've done it in the past:
1. Flash ROM
2. Flash GAPPS (if necessary)
3. Flash unSU Script link
4. Flash Magisk and Phh
5. Wipe Cache/Dalvik (just a habit and a damn good one)
and hopefully you know the rest of the steps.
Magisk v9 works fine with oxygen 3.2.8 (blue spark kernel and data and cache f2fs), but WiFi stops working if I flash v10.2.
Does someone know why? Thanks in advance
My config is a 4.0.1 OOS + 10.2 magisk + phh by topjohnwu v2. Working good so I dunno why you have some issues when we have same phones :/
Mine works with Open 10 beta and did you install the phh superuser app?
Hw4ng3r said:
Magisk v9 + Phh was working fine a month ago when I was using CM14.1.
Don't know which custom roms you were using but many of them have root already included, so you'll have to remove the SU that's included in the ROM before you Magisk + Phh.
Order I've done it in the past:
1. Flash ROM
2. Flash GAPPS (if necessary)
3. Flash unSU Script link
4. Flash Magisk and Phh
5. Wipe Cache/Dalvik (just a habit and a damn good one)
and hopefully you know the rest of the steps.
Click to expand...
Click to collapse
I tested it su removed, so I tried without remove su, but doesn't work.
(Magisk v10.2 + phh v2)
mucha.k1994 said:
My config is a 4.0.1 OOS + 10.2 magisk + phh by topjohnwu v2. Working good so I dunno why you have some issues when we have same phones :/
Click to expand...
Click to collapse
This problem occurs with custom ROMs. other than Oxygen 4.0.x.
adz3d said:
Mine works with Open 10 beta and did you install the phh superuser app?
Click to expand...
Click to collapse
Yes, installed the phh superuser app. I've been using phh since MM.
I read in another thread that on F2FS only the normal phh SuperUser works. I haven't tried it myself though. SuperSU has occasional issues on F2FS as well, irrespective of the ROM (OOS or Lineage based).
I have Magisk and Magisk's phh's superuser on 4.0.1 on F2FS (data partition). Using eng.stk's v11 TWRP, I:
1. Flashed OOS 4.0.1
2. Booted to system, installed some apps
3. Flashed Magisk 10.2, then topjohnwu's r2 phh superuser
4. Boot to system
All works fine.
ememeh said:
I have Magisk and Magisk's phh's superuser on 4.0.1 on F2FS (data partition). Using eng.stk's v11 TWRP, I:
1. Flashed OOS 4.0.1
2. Booted to system, installed some apps
3. Flashed Magisk 10.2, then topjohnwu's r2 phh superuser
4. Boot to system
All works fine.
Click to expand...
Click to collapse
This problem occurs with custom ROMs. other than Oxygen 4.0.x.
smk513 said:
This problem occurs with custom ROMs. other than Oxygen 4.0.x.
Click to expand...
Click to collapse
Okay. In the main Magisk thread someone recently mentioned that phh's r259 was working on DU on OP3. Could give that a bash
ememeh said:
Okay. In the main Magisk thread someone recently mentioned that phh's r259 was working on DU on OP3. Could give that a bash
Click to expand...
Click to collapse
Thanks for the information. i'll try it.
I think it's been well known for a while that phh superuser does not like F2FS. Since like August according to the topjohnwu phh superuser thread.
Hi,
After making a clean flash of the latest official global 8.7.26, I tried to flash magisk (it worked on my previous installation, 8.7.12), but I get a bootloop everytime.
Any ideas on how to fix that ?
Cheers
Edit: solved, see my solution 5 posts below.
i have 8.7.26 and magisk 16.7 everything ok
nelsonmenon said:
i have 8.7.26 and magisk 16.7 everything ok
Click to expand...
Click to collapse
So you flashed the rom, and then flashed magisk zip, and it worked ?
I wonder why it's not working for me
Edit: tried flashing uninstaller twice, then flashing magisk again, no success. Tried with lazy flasher, nothing. Same with 16.0 and 16.7
installed the Room, Reboot,installed magisk
Rip me then. Any other things I could try ?
All right I solved it, here's what I did:
- Go to settings -> About phone -> System update -> menu (3 dots) -> Download update
- Your phone will download something. (I was on the latest version available already, so my guess is it re-downloads the update package for the current version )
- Install the update (it did it in TWRP). The phone should reboot automatically.
- Boot back into TWRP, you can now flash magisk and boot without problems.
You can try Magisk 16.4. It works for me, but Xposed is still not working. Any Idea?
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
Please help me
Download Xposed installer from https://repo.xposed.info/module/de.robv.android.xposed.installer
Open it, approve for the permissions required and if it is available some zips will show up, else it will tell that it is incompatible
not supported , is there another way ?
Nope!
Except if you downgrade to android oreo, dont do it its not worth it
Also, if you want Xposed for Rootcloak and use magisk i have another solution.
Enable MagiskHide, install MagiskHide Props Config module and enjoy being rooted
what about edxposed, it can be installed from the magisk modules and should be the same. unless op doesn't want magisk installed at all!
I tried to install it but its failed riru-core required , and after i installed it too using magisk i got bootloop issue
I own a firetv stick 2nd gen (tank). I have unlocked the device and installed the Prerooted rom which requires you to install magisk after you install the rom
I just cant figure out which magisk version to use. I have tested 25.2, 25.1, 24.3 but in all these versions the manager just crashing once i press any button on my remote (It doesnt open, it only shows the logo)
I tested 20.03 which luckily works and i had not got time to test any other versions, but i thought i'd ask here if anyone know why this is happening or what magisk version is suggested
Lenicyl said:
i thought i'd ask here if anyone know why this is happening or what magisk version is suggested
Click to expand...
Click to collapse
It sounds like a signature mismatch. You can't mix and match official and unofficial Magisk versions.
If you try to install the official Magisk Manager, with a custom Magisk build, you will see what you are experiencing. Magisk Manager will close and the icon will revert to just Magisk text.
With Magisk 22+ the zip and manager are the same file. Whatever zip you used to patch your device, rename it to magisk.apk and install it as an app in FireOS.
I think a custom Magisk build is used with a couple of the FireSticks to protect the rooting method.
Finnzz said:
It sounds like a signature mismatch. You can't mix and match official and unofficial Magisk versions.
If you try to install the official Magisk Manager, with a custom Magisk build, you will see what you are experiencing. Magisk Manager will close and the icon will revert to just Magisk text.
With Magisk 22+ the zip and manager are the same file. Whatever zip you used to patch your device, rename it to magisk.apk and install it as an app in FireOS.
I think a custom Magisk build is used with a couple of the FireSticks to protect the rooting method.
Click to expand...
Click to collapse
hey! For all the versions i installed (which is from the original magisk repo itself), i used the same apk to install both the manager and Magisk itself, so i dont think its signature
mismatch.
I was not aware of any custom magisk builds for firetv until i read your reply. I found this but this has the same issue as normal magisk, the issue being the Manager not working.
Also i just tested Magisk v22 and it works !!
Im thinking ill just stay on this version and i think ill be fine for now ?