Hi Guys,
I have poco m2 pro and installed stock MIUI 12 rom via miflash. Earlier i was using pixel experience rom and orange fox recovery. When i was using pixel experience i check in oragefox terminal selinux status and it was showing permissive, so i decided to reflashed stock rom, as i wanted selinux mode enforcing.
Now i can't check selinux mode on my phone as its unrooted and locked. I installed Root Checker - Apps on Google Play to check selinux status and its showing permissive on stock unrooted phone. I suspect, its false status. I wanted to check is there any way i can check selinux status on stock MIUI 12 rom.
My phone is unrooted, i never rooted my phone.
Related
I have a T889 that retains the 4.1.2 bootloader.
Using Mobile Odin, I flashed the stock (from sammobile) 4.3 rom (T889UVUCMK7_T889TMBCMK7_T889UVUCMK7_HOME.tar.md5).
I then flashed the WIFI Patch as shown in various forums.
The phone is now at 4.3 (T889UVUCMK7), with the 4.1.2 bootloader (T889UVBMD1) as expected.
However, the phone shows the Custom Binary Download set to "Yes (1 counts)", and the Current Binary set to "Custom". The System Status still shows "Official".
Triangle Away sets it all back to No, Official, Official, but it doesn't "stick".
My question...
Is this to be expected, since I'm still on the 4.1.2 bootloader? I'm assuming the system scans and detects a non-standard kernel, thus flagging it as custom.
I don't want to flash to the 4.3 bootloader (I want to stay knox free).
BTW, I had Mobile Odin inject SuperSU.
Your feedback is appreciated.
Thanks.
it could be caused by keeping a non stock recovery flashed.... try flashing a stock recovery & check to see
fankoosh81 said:
it could be caused by keeping a non stock recovery flashed.... try flashing a stock recovery & check to see
Click to expand...
Click to collapse
Unfortunately, it's all stock (basically the official update with root injected).
Might have something to do with your SELinux state. Is it set to permissive or enforcing? SELinux causes all kinds of wacky behavior with root and certain status changes between boots.
I have an A5 2017 (SM-A520F), rooted, TWRP Recovery installed, running Android Nougat. Knox is tripped, Device Status was 'Custom' and if I checked for Software Updates in Settings it failed.
I installed Xposed, then Firefds Kit and used this to change the Status to Official. I can now download a Software Update (~50MB so probably not important - later updates may be). Knox is still triggered - this evidently doesn't matter. After downloading the update the phone boots from Recovery, i.e. boots TWRP and hence fails to install the update. I'd like to flash the stock Recovery to install the update then flash TWRP again. Anyone know where to acquire the stock Recovery? There are some iffy-looking sources I'd prefer to avoid.
Try updato.com or sammobile.com for the full stock ROM. You can extract the recovery and flash it in Odin.
After i root, and installing twrp recovery my s9 plus android pie, sistem showing custom status instead official
Guys, is there any way to enable the Camera2API in the stock ROM (in 3, 4, or whichever stock version) and keep the phone with locked bootloader and stock recovery? That is a complete stock ROM with only Camera2API enabled.
niyonsv said:
Guys, is there any way to enable the Camera2API in the stock ROM (in 3, 4, or whichever stock version) and keep the phone with locked bootloader and stock recovery? That is a complete stock ROM with only Camera2API enabled.
Click to expand...
Click to collapse
Theoretical answers
1. Install stock ROM by qfil , root it, flash oos hal.zip, again unroot completely and then flash stock qfil with skipping system partition.
2.modify system.img and replace camera libs from oos zip
And then flash stock. Problem with this is may be size of system.img would be changed and so the flashing with qfil will require changes in rawprogram XML files
Hey guys!
I'm rooted with magisk on this ROM - https://forum.xda-developers.com/oneplus-5t/development/rom-unofficial-aosip-aka-derpfest-t3978357/amp/
What would be the best way to downgrade/roll back to an Android 9 ROM? Safely.
Appreciate the help! Thanks.
I just did this process.
You just need to have your twrp updated and flash the stock rom (or other roms).
You'll lose your recovery, it goes to stock, and magisk.
I think flashing a non-stock android 9 ROM is way better, you won't lose your recovery.
If everything goes bad, you can try the unbricking tool for 5t.
pedrowood said:
I just did this process.
You just need to have your twrp updated and flash the stock rom (or other roms).
You'll lose your recovery, it goes to stock, and magisk.
I think flashing a non-stock android 9 ROM is way better, you won't lose your recovery.
If everything goes bad, you can try the unbricking tool for 5t.
Click to expand...
Click to collapse
So if I'm understanding correctly, it doesn't matter that I'm on the latest firmware as well? All I have to do is find a android 9 ROM (I'm probably going to do oos Aroma) and flash that in the latest recovery installed. Latest recovery being the one I'm currently on twrp 3.3
Yeah, that's it.
I was using aicp android 10 I just flashed lineageOS android 9, all worked well. I'm also using twrp 3.3 that should be OK.