Lost Camera2API support after flasing new rom - Xiaomi Redmi Note 7 Pro Questions & Answers

I unlocked the bootloader on my RN7 Pro and installed Pixel Experience Q ROM, but to my shock, I discovered that the Camera2API support was lost! I am not able to enable it through magisk modules. This is a very weird issue I've faced, anyone have any solution to this? Help
Also, when I try to flash the ANX camera Utility, the phone get stucked in bootloop all the time! Can anyone provide me the solutions to both the problems above?

Related

OnePlus7 pro - issue since new beta version

So I updated my op7p to beta 19 and the issues I have are
Front and rear camera not working at at all (black screen not crashing)
teams call not connecting (which is the main deal breaker for me)
youtube keeps loading main page
flash not working
What I tried:
factory reset
switching between EU / Global different android 10 versions including 10.0.10.
Flashing from EDL /TWRP
With or without magisk
Different versions of kernels. (After/ stock)
Downgrading / updating camera and camera service apk.
Flashing hydrogenOS.
Custom ROMs..
Using adb logcat I found that the camera service isn't responding.
Notes:
I don't have warranty..
Device GM1913
The device works without selfie camera in android 9.5.1.
Let's try to debug this, comment your's ideas!
Thanks!
i too have these issues.
Get oxygenos

[Help Required] Need a camera fix for android 10 GSI

Hello, I have recently installed an android 10 gsi on my Huawei Honor 6x. The camera worked on emui 8 and after installation(which was hectic as I bricked my device and it took a lot of trials to get it out), the camera and flash just don't work.! Everything else works fine(except volte, which is a known issue).
So yeah, my camera and flash aren't working.. and whenever I power on my device, I get a warning "somethings wrong with the device, contact the manufacturer" (similar one).
Any ideas how to fix this?

Xiaomi redmi note 9s the system has been destroyed

I am trying to flash with another rom have tried two different ones global and eu both gave "mismatch image and device" i am confued since my phone wss eu now i cant find eu firmware that matches my phone i need help (i tried to root using magisk)
Re-flash Stock ROM to get rid off of all mods you applied so far: request it from OEM if you can't find it on Internet.
jwoegerbauer said:
Re-flash Stock ROM to get rid off of all mods you applied so far: request it from OEM if you can't find it on Internet.
Click to expand...
Click to collapse
I did it worked ... now my wifi and data dont work i know twrp will fix it but i dont know the excat steps if you can inform me them

Question Using wrong boot .image?

Booted up a oneplus 9 pro boot image, it fixed my phone being stuck in fastboot because I didn't have stock image.
Now updates don't work.
Oneplus 9 T-Mobile, stock rom, pro boot image, unlocked bootloader, unlocked sim - Any help would be appreciated.
Was thinking MSM tool but unsure what one to use.
I'm in a similar situation but I can't get out of fastboot. What OnePlus Pro boot image did you flash to your phone and what firmware are you on?
I gave the pro boot.img a try and it worked!
I grabbed it from this post: https://forum.xda-developers.com/t/...t-keep-root-oos-12-c-48.4252373/post-87096189
I want to back a few things up before tinkering anymore but will report back on how I try to fix it.
Thinking ahead, did Oxygen Updater not allow you to change your device back to a OnePlus 9, download the software update, flash and revert back?
Glad you could get your phone fixed...
I wish my system updates worked though lol ugh
Harley1979 said:
Glad you could get your phone fixed...
I wish my system updates worked though lol ugh
Click to expand...
Click to collapse
Are you using Oxygen Updater or the native update tool?
If the latter I would try the former.
Oxygen Updater - Apps on Google Play
Skip staged rollout queues and update your OnePlus device ASAP!
play.google.com
No I'm on a t-mobile oneplus 9 with android 12.
Soooo have you tried Oxygen Updater?
No it doesn't work for my version of this phone.
Thanks though
I wish I had a copy of the original boot image of my phone, T-Mobile variant boot.imge I'm guessing and for the non-pro version. I'm assuming that may fix my issue with the T-Mobile system updates and my incompatibility app issues with Google Play...
Harley1979 said:
I wish I had a copy of the original boot image of my phone, T-Mobile variant boot.imge I'm guessing and for the non-pro version. I'm assuming that may fix my issue with the T-Mobile system updates and my incompatibility app issues with Google Play...
Click to expand...
Click to collapse
If your bootloader is unlocked and Google Play is telling you that your device is not supported, it's because of the unlocked bootloader most likely. Are you successfully passing both basic and CTS safetynet profiles?
Not sure sry... Only few apps are incompatible.
This is what the OnePlus updater shows.
Harley1979 said:
Not sure sry... Only few apps are incompatible.
This is what the OnePlus updater shows.
Click to expand...
Click to collapse
I think your problem is that your bootloader is unlocked and it needs to be locked in order to pass safeynet. More and more apps are not allowing for detected unlocked bootloaders in which makes safetynet fail.
Wish I knew how to relock it... Little reluctant to use a random site's information... Xda probably has information on relocking it, wish I had a link to a good post.
Could it possibly brick my phone if I'm using a pro boot image an try to lock bootloader?
Any advice or help would be much appreciated thanks for your time.
I will follow-up more later as I'm walking out the door. I'm not convinced that we are on a different or should I say, incompatible boot.img. When I get home I need to do some research to see what is actually different in the boot.img when being compared each other (C.61 boot.img on OP9 and OP9 Pro).
Back history for anyone following along... I was unlocked, rooted, Google Play certified and on C.48. I upgraded via OTA, no reboot and chose an inactive slot. It did not work and soft bricked slot a. I lost root, was on C.48 still but on slot B. I successfully upgraded to C.61 but didn't have root. I could not find a good boot.img or patched_boot.img. I tried a stock OP9 Pro image and that got me working. That same user provided a patch img too so I tried that and obtained root as well.
Soooo what is the difference between the boot images on C.61 pro and non-pro OP9 models?
Stay tuned....!
Thanks I'll keep checking back on this
Unfortunately the difference is that the pro version is available to tinker with and the non pro version isn't. Sorry to state the obvious.
My phone so far is working fine on the OP9 Pro kernel. C.61 is rooted and Google Play is certified. All my previous Magisk config is there as well and modules. I'm not sure what the difference between the kernels are at this point but also not a kernel expert either.
Once the next full release comes out for OP9, I will swap it out.
@Harley1979 I got your PM and will follow-up with you there.

POCO X3 NFC - Bluetooth not working after Magisk

Hope everyone's well,
I rooted my colleague's poco x3 nfc on android 11 by unlocking the bootloader, flashing the twrp & installing magisk. Although after rooting, the phone loses bluetooth functionality which is very weird. Is there anyone who can help me out with this issue? I did get rid of magisk, did a factory reset and it was working again fine. But now after reflashing magisk, the bluetooth's lost again.
I would appreciate the help!

Categories

Resources