Remove red blinking warning - Realme 2 pro Questions & Answers

woah !! the stupidity of colorOS is just beyond imagination!!
have successfully rooted by installing official twrp and sideloading magisk without removing encryption.
Camera API2 also enabled via sideload zip.
root working perfectly.
BUT a nonsensical red bar keeps blinking on top saying = root detected , repair your device.
I beg to all senior developers to please find a way to remove this irritating red bar.
is it possible to use magisk hide feature and hide root from a system app that detectes the root and shows warning??
please help.
Much grateful to all the super people out there taking interest in developing for our beloved realme 2 pro (minus colorOS)

Is this what you're lookin' for? It's somewhere in realme 2 pro forum https://forum.xda-developers.com/realme-2-pro/development/app-remove-blinking-issue-t3892776

Related

Xposed - Chance of bricking mad etc. questions

Hi.
If I will follow the instructions for installing Xposed for my phone, what are the chances that it will go bricked? I heard that you must be very lucky to get it right. And is there a chance of hard brick or only normal? Thanks !
PS; Are all the modules working (f.e. Pixel navbar or status bar and notification bar in material style)
filiplongac said:
Hi.
If I will follow the instructions for installing Xposed for my phone, what are the chances that it will go bricked? I heard that you must be very lucky to get it right. And is there a chance of hard brick or only normal? Thanks !
PS; Are all the modules working (f.e. Pixel navbar or status bar and notification bar in material style)
Click to expand...
Click to collapse
I think actually bricking with xposed is impossible(can maybe cause bootloop though), and most theming modules won't work at all or work wrong. Also for some users normal xposed version breaks phone app.
I'm using this version made for odexed samsung roms(my phone is honor 4x which is same than p8lite) https://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960
This will keep phone app working.
Take TWRP backup of your whole device before installing and you will be safe.
Also the first boot can take 30mins. After that boot time goes to normal.
Guide tells you to use CWM recovery, but TWRP will work.
Thanks for the reply! I want to use Xposed mainly for theming... So in that case, most of them don't work?
I use this version of Xposed installer and it's working without any problem
https://forum.xda-developers.com/xposed/material-design-xposed-installer-t3137758
About modules most of them is not compatible with EMUI
Anyway this is my installed modules list and all of them are working (except gravity box, most of it's features is not working) and I can confirm that XStana is working too
Ok I'll try. Thanks m8s

"Battery level full" - Any solutions to disabling this notification?

I am running rooted Swift and Fast B170 ROM on one XT and stock B180 on another and have yet to find a way to disable this seemingly system based notification. On my rooted device I tried to install Xposed but ran into a boot loop issue after installing the framework so I am inclined to think that isn't a possible route to a solution. The OS notification center is pretty useless in managing app notifications and the battery notification doesn't seem to be tied to a specific app anyway.
Does anyone have any ideas how to disable the notification?
So I ended up disabling the System UI notifications all together. And that works but I'm pretty sure its going to disable other important notifications controlled by System UI. If anyone has any true solutions let me know.
Xposed can be installed on the Ascend XT. Search for my Xposed thread. I'm using Magisk Systemless Xposed v87.1.
Why not just swipe away the battery full notification. Yes, you've probably killed other things too by disabling SystemUI.
deuce300 said:
I am running rooted Swift and Fast B170 ROM on one XT and stock B180 on another and have yet to find a way to disable this seemingly system based notification. On my rooted device I tried to install Xposed but ran into a boot loop issue after installing the framework so I am inclined to think that isn't a possible route to a solution. The OS notification center is pretty useless in managing app notifications and the battery notification doesn't seem to be tied to a specific app anyway.
Does anyone have any ideas how to disable the notification?
Click to expand...
Click to collapse
Have you tried using an Xposed module to remove it, I recall using one to do that to remove the same notification on my S4.
divineBliss said:
Why not just swipe away the battery full notification. Yes, you've probably killed other things too by disabling SystemUI.
Click to expand...
Click to collapse
Because it's a nuisance, and I've notice with some games that notification (w/sound) will kill all in game sounds until the game is restarted. But that's just my 2ยข
Sent from my H1611 using Tapatalk
yes it can pop up at the most inopportune time and its honestly a useless notification in the bar that is distracting. notifications shouldnt be in the bar that i should ignore.
@mattzeller and like i said before i tried installing Xposed before i believe the regular installer and that went fine but when i installed the framework and rebooted it kept boot looping at the android logo and i had to reflash the Swift and Fast ROM.
I plan on exploring the Xposed install that divineBliss mentioned I just need to backup my current ROM first and then double check all of the steps required. I hope it works. cause it really is a distracting notification.
deuce300 said:
yes it can pop up at the most inopportune time and its honestly a useless notification in the bar that is distracting. notifications shouldnt be in the bar that i should ignore.
@mattzeller and like i said before i tried installing Xposed before i believe the regular installer and that went fine but when i installed the framework and rebooted it kept boot looping at the android logo and i had to reflash the Swift and Fast ROM.
I plan on exploring the Xposed install that divineBliss mentioned I just need to backup my current ROM first and then double check all of the steps required. I hope it works. cause it really is a distracting notification.
Click to expand...
Click to collapse
Using systemless Xposed is a fairly straightforward process. This is the way I got it working on mine since Magisk wouldn't flash because of the modified boot.img and would only modify stock, you don't have to flash the ROM like I did, but I was doing cleanup and reflash anyway.
1. Download all required files and put them on your external SD card.
a. Swift&Fast: https://forum.xda-developers.com/showthread.php?p=72258982
b. Magisk: https://forum.xda-developers.com/showthread.php?p=68966662
2. Make sure you have the correct boot.img for the firmware version you are using, can't use B160 boot.img on B170 ROM, it causes wifi problems. I extracted boot.img from @madvane20 's Swift&Fast ROM since that's what I am running.
3. Do all necessary wipes and flash ROM, do NOT reboot yet.
4. Flash extracted boot.img (select img in TWRP to show *.img files) do NOT reboot yet.
5. Flash Magisk (I'm using current/stable)
6. Wipe caches and reboot.
7. Boot your phone, open Magisk Manager and go to Downloads and install Xposed Framework (SDK 23). I got an error here trying to download and install. I fixed it by adding the folder Magiskmanager to internal sdcard.
8. Download and install latest Xposed installer for systemless Xposed. The link for that is in the Magisk module information for Xposed.
9. Reboot (got a kitK Kat? It's gonna be a while) and everything should be working.
Occasionally after a reboot you can't open settings(Xposed issue), just reboot again, should clear that up.
Sent from my H1611 using Tapatalk
Although I'm sure there's a way via xposed to disable the notification, I haven't found it yet. The xEMUI module has some nice tweaks, but nothing related to that.
Perhaps via appOpsXposed, or via stopReceiverBroadcasts... remove the ability for SystemUI to see the charging related events..?
-n0cturne- said:
Although I'm sure there's a way via xposed to disable the notification, I haven't found it yet. The xEMUI module has some nice tweaks, but nothing related to that.
Perhaps via appOpsXposed, or via stopReceiverBroadcasts... remove the ability for SystemUI to see the charging related events..?
Click to expand...
Click to collapse
once i get over pneumonia ill fix my b180 rom. however b180 in general has bad battery drain for me on stock or my rom. will help what i can once i feel better
Have you tried the NotifyClean module in Xposed?
Thanks -n0cturne- for the xEMUI tip. I have been dying to center the clock in EMUI w/o having to use FSBI. FSBI works really well, but slows everything down.
deuce300 said:
I am running rooted Swift and Fast B170 ROM on one XT and stock B180 on another and have yet to find a way to disable this seemingly system based notification. On my rooted device I tried to install Xposed but ran into a boot loop issue after installing the framework so I am inclined to think that isn't a possible route to a solution. The OS notification center is pretty useless in managing app notifications and the battery notification doesn't seem to be tied to a specific app anyway.
Does anyone have any ideas how to disable the notification?
Click to expand...
Click to collapse
Notifyclean will do what you ask, I have tested it and once I blocked that specific notification, no longer pops up or chimes that the battery is full
Sent from my H1611 using Tapatalk
NotifyClean only lets you disable the tray notification, not the pop up dropzone notification. . Unless I'm missing something?
-n0cturne- said:
NotifyClean only lets you disable the tray notification, not the pop up dropzone notification. . Unless I'm missing something?
Click to expand...
Click to collapse
It gets rid of the notification in the notification area and blocks the pop-up that occurs when it's full. Just not the "you just plugged your phone in" pop-up
Sent from my H1611 using Tapatalk

[FIX] Applying incompatible theme causing system ui stopping

Only tested in MIUI 9 oreo could work with nougat too
If your phone stopped working after applying a theme making your system ui stop and a black lockscreen you can easily fix it by doing what i found out as i didn't see anything on it anywhere else
Requirements
-unlocked bootloader
-TWRP recovery installed
Reboot to recovery then open file manager in advanced window
Go to /data/system/theme
Then delete the files with app names that stops
Like
com.android.systemui
Then just reboot and you're done ?
Nice
thanks, i wish i read this befoe reformatting my phone because of a theme i applied that made EVERYTHING dark and unusable. Xiaomi does fantastic hardware but the software side is pure ass.
Also forcing you to use their app to change themes is so greedy, at least make it work.
Same Problem with Miui 8
Hello i got this problem when installing third party theme on my redmi 3s with miui 8. But i dont have twrp installed and dont have unlocked bootloader. Can you help me?

need help for installing google pixel camera install on xiaomi A1

Hi everyone i know there are tons of videos on youtube for installing google pixel camera on Mi A1 without root method.
I dont know how risky of activity is but i dont want to stop security update,also if i uninstall pixel camera apo can i have install again directly or follow method
And what is bricks of mobile?is it useless or does not get recover from service centre?
Waiting for your answer and thanks in advance.
Magisk root is perfectly safe and doesn't break updates. It doesn't touch the system files. There are also magisk modules to enable the camera2 api and some permissions needed for Gcam, also systemless, so you don't mess with system files manually. You can uninstall everything back to stock in a few easy steps when you want to. This way, you will not break warranty, you still get the updates (following another really easy guide to disable root, update and re-enable root) and you may install any Gcam version you want like any other apk file (there are hundreds actually). There is no risk in this method and lots of benefits.

Luckypatcher Android 11 BOOTLOOP WARNING

I recently moved to OOS11 and had trouble rooting. Now that I have my phone rooted I can no longer restart it or it will bootloop. Does anyone have any idea why that would be?
This will be the 3rd time I have MSMed my phone in the last 3 days.
As many problems as I'm having I'm thinking of just going back to Android 10.
Thanks in advance.
night hawk said:
I recently moved to OOS11 and had trouble rooting. Now that I have my phone rooted I can no longer restart it or it will bootloop. Does anyone have any idea why that would be?
This will be the 3rd time I have MSMed my phone in the last 3 days.
As many problems as I'm having I'm thinking of just going back to Android 10.
Thanks in advance.
Click to expand...
Click to collapse
Can you provide a bit more background, do you have any Magisk modules installed, does your phone boot at all? Did you patch your own boot.img just so that we can help you out better
Shredz98 said:
Can you provide a bit more background, do you have any Magisk modules installed, does your phone boot at all? Did you patch your own boot.img just so that we can help you out better
Click to expand...
Click to collapse
I'm patching my own boot.img and I only have skyvalex call recorder installed as a module. When it happens I just get stuck in an infinite boot animation with the two dots circling continuously.
I think I may have narrowed down the problem by going through the steps that I normally go through after MSMing my phone (I've done it 4 times now lol) and rebooting after each step to see what triggers it. Here are the steps in order.
1. MSM the phone and do bare minimum to get to home screen so I can enable OEM ulocking and usb debugging. (rebooted just fine)
2. Unlock bootloader with adb. (rebooted just fine)
3. Install magisk manager, switch to beta update channel, patch boot.img, flash patched boot.img (rebooted just fine)
4. Setup up phone with google account, set up fingerprint, etc (rebooted just fine)
5. Enable magisk hide and systemless hosts (rebooted just fine)
6. Restore a backup using oneplus switch from before this all started happening. (rebooted just fine)
7. Use luckypatcher to remove ads from a few games (BOOTLOOP)
Well it would appear that luckypatcher is the problem. I'm wondering if the new "use magisk module" mode in the newest version is causing the problem. Maybe if I installed EdXposed and used that like I used to maybe it would remedy the problem. Or maybe I should just use an adblock magisk module. However its far passed my bedtime so I will confirm this tomorrow if possible.
Disable the modules you have installed.
Reboot, does it loop?
If no then it's a module
If it does then it's your boot img
I'd recommend booting your patched boot img then directly installing via magisk (do not reboot until you have)
Hope this helps
night hawk said:
I'm patching my own boot.img and I only have skyvalex call recorder installed as a module. When it happens I just get stuck in an infinite boot animation with the two dots circling continuously.
I think I may have narrowed down the problem by going through the steps that I normally go through after MSMing my phone (I've done it 4 times now lol) and rebooting after each step to see what triggers it. Here are the steps in order.
1. MSM the phone and do bare minimum to get to home screen so I can enable OEM ulocking and usb debugging. (rebooted just fine)
2. Unlock bootloader with adb. (rebooted just fine)
3. Install magisk manager, switch to beta update channel, patch boot.img, flash patched boot.img (rebooted just fine)
4. Setup up phone with google account, set up fingerprint, etc (rebooted just fine)
5. Enable magisk hide and systemless hosts (rebooted just fine)
6. Restore a backup using oneplus switch from before this all started happening. (rebooted just fine)
7. Use luckypatcher to remove ads from a few games (BOOTLOOP)
Well it would appear that luckypatcher is the problem. I'm wondering if the new "use magisk module" mode in the newest version is causing the problem. Maybe if I installed EdXposed and used that like I used to maybe it would remedy the problem. Or maybe I should just use an adblock magisk module. However its far passed my bedtime so I will confirm this tomorrow if possible.
Click to expand...
Click to collapse
The issue is definitely lucky patcher, I had the same problem and my phone was useless until I got rid of it. So it seems it's not playing well with A11 or OOS11 in any case do not use it or you'll end up in a boot loop.
Cheers!
Ah lucky patcher..oh dear, can't help you with that crap.
Best advice, get rid
Bummer about Lucky Patcher....
In b4 the lock.
I can confirm the same findings, lucky patcher seems to break reboots later.
Hopefully a new version will find and resolve the issue, but until then not much we can do but to wait.
Unfortunately doesn't appear to be any way to get around this or recover from the bootloops without a wipe/reimage. Can't get access for adb during bootanimation, cant boot from a boot img, just basically stuck.
@OP, perhaps you can put a message in your thread's title just warning against LP on A11 for the time being.
uaktags said:
Unfortunately doesn't appear to be any way to get around this or recover from the bootloops without a wipe/reimage. Can't get access for adb during bootanimation, cant boot from a boot img, just basically stuck.
@OP, perhaps you can put a message in your thread's title just warning against LP on A11 for the time being.
Click to expand...
Click to collapse
I changed the title. Do we know if LP can be used with xposed on Android 11 with success still?
night hawk said:
I changed the title. Do we know if LP can be used with xposed on Android 11 with success still?
Click to expand...
Click to collapse
Did xposed work on 11?
night hawk said:
...
7. Use luckypatcher to remove ads from a few games (BOOTLOOP)
Well it would appear that luckypatcher is the problem. ...
Click to expand...
Click to collapse
@night hawk
Hi!
You better read the XDA Forum Rules and refrain from such topics. We don't accept discussions about issues with warez!
6. Do not post or request warez.
If a piece of software requires you to pay to use it, then pay for it. We do not accept warez nor do we permit members to request, post, promote or describe ways in which warez, cracks, serial codes or other means of avoiding payment, can be obtained or used. This is a site of developers, i.e. the sort of people who create such software. When you cheat a software developer, you cheat us as a community.
Click to expand...
Click to collapse
THREAD CLOSED!

Categories

Resources