Database Develop

Google Modded Camera; It works, but it doesn't.

I have 2 Xiaomi Redmi 4x's at home with the same Xiaomi.eu rom, same recovery, same kernel, same version.
I flashed the same ZIP to enable Camera2API through Magisk. And then I installed the same GCam on both devices.
I even installed a few Camera2Api check apps from the playstore and both report the same results.
Result:
It works on one of the devices but it keeps crashing on the other.
I've tried reinstalling, reflashing Camera2API zip, but all without result.
Any idea's.? (I'll post a screenshot of the crash log later on)
Rom: Latest Xiaomi.eu rom.
Magisk: 14.5 Beta
Recovery: Latest official TWRP
Kernel: Stock

Single_Core said:
I have 2 Xiaomi Redmi 4x's at home with the same Xiaomi.eu rom, same recovery, same kernel, same version.
I flashed the same ZIP to enable Camera2API through Magisk. And then I installed the same GCam on both devices.
I even installed a few Camera2Api check apps from the playstore and both report the same results.
Result:
It works on one of the devices but it keeps crashing on the other.
I've tried reinstalling, reflashing Camera2API zip, but all without result.
Any idea's.? (I'll post a screenshot of the crash log later on)
Rom: Latest Xiaomi.eu rom.
Magisk: 14.5 Beta
Recovery: Latest official TWRP
Kernel: Stock
Click to expand...
Click to collapse
the magic is to make the camera configs the best for your phone if it crashes qhen shows camera image, pixel experiemental features is the best option for me

Nautilus99 said:
the magic is to make the camera configs the best for your phone if it crashes qhen shows camera image, pixel experiemental features is the best option for me
Click to expand...
Click to collapse
But ... it's the same phone, same specs, same model, same rom, same everything. Why does it works for one and not the other?

Use this, 101% working guide. Thank me later
https://forum.xda-developers.com/showpost.php?p=74150927&postcount=26

Anyone had success with xposed on mi 8?

Has anyone got Xposed working yet? I've tried a few different methods of install. via magisk or a direct install through twrp but i end up in a bootloop

Worked fine with EU rom

ermacwins said:
Worked fine with EU rom
Click to expand...
Click to collapse
did you install via magisk? I get stuck in a bootloop and it loads into twrp after it tried to boot into android for 5 minutes. I'm on xiaomi.eu weekly atm

WakeUpFilthy said:
did you install via magisk? I get stuck in a bootloop and it loads into twrp after it tried to boot into android for 5 minutes. I'm on xiaomi.eu weekly atm
Click to expand...
Click to collapse
Oops sorry my mistake, I only flashed magisk not xposed.

i need xposed too

Are they the news? I have a global rom but I could not install xposed for magisk

Its not working yet on miui. Now the kernel is out maybe it will be made. I have xposed working on my mi 8 because I have installed a Treble rom. If you are willing to install a treble rom it works fine but the only problem is the treble roms themselves are filled with bugs. It just depends how much you want xposed. The problems I have with treble is bluetooth doesnt work in calls, Screen brightness control is broken and some apps the notch is covering somethings. I would probably wait for a official xiaomi custom rom then install xposed. Hopefully we will see one soon

any update on xposed + Mi8?

magisk 20.1 causes bootloop to recovery!

i run china k20 pro on indian miui 11.01.0
i installed twrp -21 version
installing magisk 20 provides root access however magisk manager asks to something which results in bootloop to recovery
ignoring that request, the module i wanted to install [energized ] asks for updating to magisk 20.1 which also leads to bootloop to recovery.
is there anything to do ? or just wait for magisk 20.2 to be released and then try it
p.s installing magisk was the only way to prevent redmi recovery from overwriting twrp, i don't know if this has any importance

i'm in kinda similar situation ,
installed magisk v20.1 and everything went fine , but when trying to install viper4android it asked me do install busybox , i did it within magisk now it only boots to fastboot , to fix it and make it boot agian i used magisk_uninstaller.zip
boots fine now but can't install magisk again if i do that it will stuck on fastboot screen .
so for your case i suggest using magisk uninstaller.zip
but hope that some one help to install magisk agian

eLcTrOn said:
i'm in kinda similar situation ,
installed magisk v20.1 and everything went fine , but when trying to install viper4android it asked me do install busybox , i did it within magisk now it only boots to fastboot , to fix it and make it boot agian i used magisk_uninstaller.zip
boots fine now but can't install magisk again if i do that it will stuck on fastboot screen .
so for your case i suggest using magisk uninstaller.zip
but hope that some one help to install magisk agian
Click to expand...
Click to collapse
yeah i used magisk uninstaller to make the phone work normally

Glad it worked . Are u able to install magisk again ?

eLcTrOn said:
i'm in kinda similar situation ,
installed magisk v20.1 and everything went fine , but when trying to install viper4android it asked me do install busybox , i did it within magisk now it only boots to fastboot , to fix it and make it boot agian i used magisk_uninstaller.zip
boots fine now but can't install magisk again if i do that it will stuck on fastboot screen .
so for your case i suggest using magisk uninstaller.zip
but hope that some one help to install magisk agian
Click to expand...
Click to collapse
Dont install Viper4android via magisk. Just download the package and install in via TWRP. Use this guide

I have this exact problem right now but even with other versions of magisk, I encounter the same issue. Any suggestions?

Same problem here with magisk I guess it is a compatibly issue with MIUI 11

Yep, it's a MIUI11 issue and the reason I haven't shifted over to it. I suspect whatever release of magisk is in the pipeline will fix it provided it's been reported.
In the meanwhile I've read 19.4 works; you could try the canary builds if that seems to old for your liking... just be careful.

Had the same problem, its because of data encryption.
You guys need to format data before installing magisk.

winesh said:
Had the same problem, its because of data encryption.
You guys need to format data before installing magisk.
Click to expand...
Click to collapse
Even with data formatting 20.1 causes issues: In fact, it seems latest Magisk build seems to be causing issues on all (or, many) builds of MIUI 11.
For k20 pro, 19.3/.4 seems smartest to install and then update via magisk manager
I believe other phones (mi 9?) need even older versions like 17.2, so I wouldn't be surprised if future updates continue to push the installation build back.

AvgZing said:
Even with data formatting 20.1 causes issues: In fact, it seems latest Magisk build seems to be causing issues on all (or, many) builds of MIUI 11.
For k20 pro, 19.3/.4 seems smartest to install and then update via magisk manager
I believe other phones (mi 9?) need even older versions like 17.2, so I wouldn't be surprised if future updates continue to push the installation build back.
Click to expand...
Click to collapse
I'm hoping the Magisk situation gets fixed. I checked the Magisk support thread and only saw one post about a bootloop with a Mi9T Pro (again, likely data encryption) so I'm given the impression MIUI might be off the radar for Magisk bug fixes.
I've had a couple of issues with Magisk 20.1 on MIUI10 - nothing critical but a couple times Magisk Manager has frozen (i.e. kill the process, relaunch and it works) and a couple hangs when root apps have been launched for the first time (again, kill + relaunch, a few times if necessary). Smooth sailing otherwise but gives me the impression that Magisk isn't without flaws on MIUI. One response was to dump MIUI altogether but I'd rather have a stable hardware experience for now. I tested a lot of custom ROMs on my last device and based on that, I'd like to stick to MIUI for a while.
Out of curiousity what are the other bugs with MIUI11 aside from it not working with encryption?

droident said:
I'm hoping the Magisk situation gets fixed. I checked the Magisk support thread and only saw one post about a bootloop with a Mi9T Pro (again, likely data encryption) so I'm given the impression MIUI might be off the radar for Magisk bug fixes.
I've had a couple of issues with Magisk 20.1 on MIUI10 - nothing critical but a couple times Magisk Manager has frozen (i.e. kill the process, relaunch and it works) and a couple hangs when root apps have been launched for the first time (again, kill + relaunch, a few times if necessary). Smooth sailing otherwise but gives me the impression that Magisk isn't without flaws on MIUI. One response was to dump MIUI altogether but I'd rather have a stable hardware experience for now. I tested a lot of custom ROMs on my last device and based on that, I'd like to stick to MIUI for a while.
Out of curiousity what are the other bugs with MIUI11 aside from it not working with encryption?
Click to expand...
Click to collapse
Other than standard app compatibility issues, I haven't heard of any major MIUI11 bugs, which is fantastic to hear.

I have tried all sorts. MI9T MIUI 11.0.1.0 and magisk just causes recovery bootloop . Gonna try magisk 19.4 if thats a thing mentioned in a previous reply

I use Miui 11.0.3 together with Magisk. I used the following procedure:
1. Copy Magisk 20.1 (for twrp) to your internal storage (e.g. downloads)
2. Install Magisk via TWRP
3. Don't reboot (it will cause bootloop).
4. Do factory reset (it will remove your Data). Your bootloader will remain patched.
5. Reboot your phone, do initial config.
6. Install Magisk Manager and run it so you will see that Magisk is installed.
7. DON'T install additional files suggested by Magisk Manager (or you will end up in bootloop again)
8. Enjoy your rooted K20Pro!

I got the same problem on my k20 pro (with MIUI EU).I try driffent ways provided by magisk official but no one works.I have to flash the system. It's not a good idea for intalling V4A on this phone

XedosMD said:
I use Miui 11.0.3 together with Magisk. I used the following procedure:
1. Copy Magisk 20.1 (for twrp) to your internal storage (e.g. downloads)
2. Install Magisk via TWRP
3. Don't reboot (it will cause bootloop).
4. Do factory reset (it will remove your Data). Your bootloader will remain patched.
5. Reboot your phone, do initial config.
6. Install Magisk Manager and run it so you will see that Magisk is installed.
7. DON'T install additional files suggested by Magisk Manager (or you will end up in bootloop again)
8. Enjoy your rooted K20Pro!
Click to expand...
Click to collapse
Does your phone remain encrypted after you do these steps? I doubt...
For some reasons, I wanna keep my phone encrypted.

OxygenOS 10.3.5 now live

OxygenOS 10.3.5
System
• Newly added user assistance feature to help user master usage skills quickly(Route: Settings>OnePlus Tips&Support)
• Optimized the power consumption performance of the system and improve user experience
• Fixed the flashback issue with some third-party apps
• Fixed known issues and improved system stability
• Updated Android Security Patch to 2020.09
Full Package
https://www.androidfilehost.com/?fid=8889791610682949950

I have root
I have rooted my op 7 pro,If I update it, will root work if I reinstall it?

MephoxSlam said:
I have rooted my op 7 pro,If I update it, will root work if I reinstall it?
Click to expand...
Click to collapse
U will have to root again.

Reboot to TWRP
Install update -- DONT REBOOT!
Install TWRP Installer
Reboot to recovery
Install Magisk
Done!
Thats the way it do it every time.

Psfanboy88 said:
Reboot to TWRP
Install update -- DONT REBOOT!
Install TWRP Installer
Reboot to recovery
Install Magisk
Done!
Thats the way it do it every time.
Click to expand...
Click to collapse
Can vouch for this method. I've used it every time to upgrade full OTA while rooted with magisk. 10/10
Only thing I would add is, when you install magisk, make sure to choose the 'inactive slot' option

Does someone have the EU version??

10.3.5 is working with data decrypted.

10.3.5 full OTA for gm21aa is up on oxygen updater

almightysiman said:
10.3.5 is working with data decrypted.
Click to expand...
Click to collapse
I don't do this since my OP5T days what procedure for OP7 PRO?

Mervingio said:
I don't do this since my OP5T days what procedure for OP7 PRO?
Click to expand...
Click to collapse
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389

EU version is now live

Android 10.0.8 - EU now on Oxygen Updater.
Mirrors :
Oxygen OS - Android 10.3.5 - Global - OnePlus 7 Pro (GM21AA) : https://www.androidfilehost.com/?fid=8889791610682950702
Oxygen OS - Android 10.0.8 - EU - OnePlus 7 Pro (GM21BA) : https://www.androidfilehost.com/?fid=8889791610682950715
My Android 10 Folder : https://www.androidfilehost.com/?w=files&flid=296897
(TWRP recovery 3.4.0-0 and Magisk 20.4 Superuser still working without issue)

Psfanboy88 said:
Reboot to TWRP
Install update -- DONT REBOOT!
Install TWRP Installer
Reboot to recovery
Install Magisk
Done!
Thats the way it do it every time.
Click to expand...
Click to collapse
With deactivated magisk modules?
Or does it matter if you update via twrp?

How can I switch from Beta 18 to 10.3.5 for 7 pro by keeping root and TWRP?

ghost323 said:
With deactivated magisk modules?
Or does it matter if you update via twrp?
Click to expand...
Click to collapse
I dont deinstall Magisk or any modules before doing it. So far no complications.

Psfanboy88 said:
I dont deinstall Magisk or any modules before doing it. So far no complications.
Click to expand...
Click to collapse
Cool, thx

Abdülcelil said:
How can I switch from Beta 18 to 10.3.5 for 7 pro by keeping root and TWRP?
Click to expand...
Click to collapse
Just the usual process :
Ensure you have all files on storage before you start
Reboot to TWRP
Flash the FULL rom package
Immediately (without reboot) flash TWRP again
Reboot back into TWRP recovery
Flash Magisk
Reboot back into recovery
Clear cache because you're moving between release rings
Reboot into System
If you notice root missing then reboot back into recovery and flash Magisk again as you might be on the other slot.
I have this as an emergency backup with a USB-C to USB-B converter to transfer from PC.

Anyone else having issue with alarm clock not working ? Vibration works but not audio

farhan20 said:
U will have to root again.
Click to expand...
Click to collapse
Hehe sorry im new,is run so good

dave2775 said:
Anyone else having issue with alarm clock not working ? Vibration works but not audio
Click to expand...
Click to collapse
Same here

Question I'm unable to flash ANX camera (or any other ZIP) after installing a custom ROM

Hi all
I recently got a Redmi Note 10 pro (sweetin) and after a long time, I'm back in the world of custom ROMs
I read up all the guides and managed to unlock my bootloader, install a custom recovery and flash a custom ROM (dotOS)
I don't want to install magisk as I'm planning to daily this phone and don't want to run into problems with safetynet
I got dotOS up and running, BUT I'm unable to flash ANX camera - all the guides instruct to flash ANX camera through magisk, but since I don't want to install magisk, I tried flashing through the recovery (orangefox) - but it's a no go - the recovery does not see the internal storage after the ROM is installed (internal storage comes up as 0 MB) - same issue on both orangefox and twrp
I tried few other ways
- placing the zip on SD card and then flashing - it ends up in the error E:Error creating fstab
- trying to ADB sideload the zip through recovery - but when I enter ADB mode in recovery, it gets stuck on "starting ADB sideload feature..." (tried this in both orange fox and twrp)
Any solutions for this?
Thank you for your help

Do you know why all the guides say to flash ANX Camera with Magisk? It's because you have to flash ANX Camera with Magisk. Period. It's like if the doctor told you to take your medicines with a meal, but you say no because you don't like eating meals with your medicine. So now you have ulcer. Dude, just follow the instructions. If you want ANX Camera, then you need to have Magisk, and if you don't want problems with SafetyNet, then there's a fix for that as well.
The issue with your recovery not seeing the internal storage is a different problem. The issue is that your storage is encrypted, and your recovery is not capable of decrypting it. You'll probably need the latest version of TWRP to be able to decrypt storage in recovery.
And no, fixing the recovery issue is still not going to let flash you ANX Camera with it. You still need Magisk.

Syd_M said:
fixing the recovery issue is still not going to let flash you ANX Camera with it. You still need Magisk.
Click to expand...
Click to collapse
thank you for the reply!
Noted. so magisk is an absolute must for ANXcamera for now
If I don't want to go the magisk route, the only alternative for a working camera will be a gcam port right?
Which approach would you recommend for daily driving? No magisk + gcam port - OR - magisk + ANX camera
Thanks again for your inputs

Depends on your preference, I guess. I haven't tried the Gcam port for this device, and I'm not sure if it completely supports 108MP yet. I usually prefer ANX Camera over GCam simply due to the native camera support, but some people prefer GCam. If you do decide to go with ANX Camera, you will need to install a few other things also: https://forum.xda-developers.com/t/miui-camera-in-custom-roms.4271037/post-84945231

Is Anx camera even compatible with the RN10Pro? It is nowhere mentioned on https://camera.aeonax.com/

Good question - I am also wondering. Did anyone try?