I just updated from oos 10.3.2 to 10.3.3 and edxposed just completely broke. I was on yafa 4.6.3 and was working completely flawlessly now whenever I install riru core and yafa my phone starts flashing to lock screen while unlocked, losing status bar and nav bar and completely unresponsive for several seconds every several seconds and the phone is basically unusable. Any thoughts on running edxposed on 10.3.3?
Related
I installed GLtools and after completing, the screen stuck and it is always on (never sleeps or dims display). None of the buttons work. I waited till it used up all battery and then charged to 5% to turn on again. When I turn on, I see my launcher still the same (and the phone launcher desktopsetup pretty intact), but after a few seconds, screen stuck again, buttons not working again.
Is there a way to remove/uninstall GLtools through PC or whatever means to fix this?
Please help.
Did you flash it in stock recovery or TWRP?
Also next time you need to forcibly switch the phone off, do it by either holding the power button for 10secs, or all three button for 10secs (not sure which it is on the R9+), it's a lot quicker than trying to flatten the battery!
Lum_UK said:
Did you flash it in stock recovery or TWRP?
Also next time you need to forcibly switch the phone off, do it by either holding the power button for 10secs, or all three button for 10secs (not sure which it is on the R9+), it's a lot quicker than trying to flatten the battery!
Click to expand...
Click to collapse
I did not flash anything. It was in stock rom. Is there still a way to fix this (remove GLtools)? Is the GLtools running in background that's why I was still able to unlock my phone and use my phone for a few secs before screen hang again?
EDIT:
I got it to work long enough to uninstall GLtools but there is this loading bar that appears even after I had removed GLtools,
http://i.imgur.com/dN4HaZW.jpg
Is this from the phone? or from my root app?
My phone screen still hungs now. I think it's not GLtools issue.
That bar is a ColorOS thing that it does while your system is updating.
Can you re-flash the stock ROM?
Lum_UK said:
That bar is a ColorOS thing that it does while your system is updating.
Can you re-flash the stock ROM?
Click to expand...
Click to collapse
So I learned how to force close the phone from you (hold power button for 10 secs), then I turned it on normally, it worked fine as normal. I tried rooting with KingRoot and it rooted, tried to install Xposed Framework thru a method found in youtube because I don't have TWRP (method uses BusyBox Pro, Terminal Emulator to flash the zip). But Xposed modules download button don't download (button goes back to idle when I tap "download").
I also tried Lucky Patcher and other similar apps to convert or move user app to system app, after reboot, the converted app is gone (deleted). This bar also keeps appearing after I did this.
That bar keeps appearing and freezes the screen (whatever the screen is currently showing) both during and after the progress bar finishes. Tried to force close and turn it on again. Stuck on Oppo screen for 8+ hours (left it as is, I went to sleep). Decided to flash the stock rom (power + vol down) without wiping data. Worked and returned to normal desktop launcher setup but phone goes back to unrooted. Xposed Framework is gone too.
Is this bar meant to check if I am doing changes to the system like root, Xposed, converting user app to system app and prevent me from doing those? I really need those things on my phone! :crying:
the bar is just when ColorOS is updating itself or generally making changes. Presumably it doesn't like something you did.
I'd probably leave off GLTools and just go with KingRoot and Xposed. They both worked on my old R9. I think the latest version of the Xposed APK has the ability to install the framework itself, so maybe try that method?
ColorOS is heavily modified from stock android, so a lot of mods for it simply don't work, unfortunately.
Lum_UK said:
the bar is just when ColorOS is updating itself or generally making changes. Presumably it doesn't like something you did.
I'd probably leave off GLTools and just go with KingRoot and Xposed. They both worked on my old R9. I think the latest version of the Xposed APK has the ability to install the framework itself, so maybe try that method?
ColorOS is heavily modified from stock android, so a lot of mods for it simply don't work, unfortunately.
Click to expand...
Click to collapse
why did the download button of Xposed not work when I tap on it? it does nothing for me.
Which Xposed should I get? I saw 2 APKs, a 3.0 and 3.1.1 alpha 4.
I was actually rebooting after I checked XMultiWindow module in Xposed when it got into bootloop
Get 3.11a4
I have installed Xposed apk 3.1.5 from the official website. It installed without any issues. I am rooted with Magisk 16.0. The black navbar Xposed mod for the 5t works perfectly with OP6.
After first reboot the screen did not react to any touches, but after another reboot by holding down the power button everything worked as it should. Don't know exactly what caused this, but i'm happy with the result.
Hello,
I am having a problem where magisk stops working after a couple hours, and therefore causing my battery saver module to unload and stop working.
I am using magiskhide, but turning it off has no changes.
Currently on 9.5.10 magisk 19.3. I have tried 19.4 with no change.
I updated to the October update of android 11 and ever since then, my phone has what I can only describe as a hard crash. The power button won't turn on the screen. The finger print scanner in the back won't respond to unlock it.
I cannot recover from it unless I have a usb cable plugged into it with the other end plugged into a computer or charger, and then I'm able to hold down the power button to hard reboot it.
But if I'm unable to plug in a usb cable because it I'm out at the time, there's no way to hard reboot it.
It has happened twice so far. Second time was today. My battery was at 100% full charge at the time.
I am currently rooted using magisk 21.0 (21000) using the boot img patch method.
Is anyone else experiencing this with their pixel 3a? Is this a hardware problem? I've had it around 8 months. Never experienced this on Android 10.
I also read about the bug in Android 11 where it's slower in gpu intensive processes like when playing some games.
Yes I get that when launching any office365 apps, either from the full suite or individually
That's the only time that occurs though - if you hold down the power button for long enough it should reboot - I used to get a warning saying that android system was corrupt, try again or format user data but selecting try again would boot my phone.
Bit sh*t really but hey-ho
A11 October Factory Image
Magisk 21.10 Manager 8.10
ElementalX p3a-3.07
I'm having the exact same problems. Initially I thought this had to do with upgrading from Android 10 so I reinstalled fresh but the problem persisted. I have not found a solution and am currently unrooted. Magisk modules I had installe were
Active Edge Mod
Advanced Charging Controller
Cross Compiled Binaries
Daily Job Scheduler
F-Droid Privileged Extension
Disable systemless hosts.
https://github.com/topjohnwu/Magisk/issues/3171
going to remove the systemless hosts module.
I also just updated to the android 11 November release. It's fixed the slowdown issues in some games.
I'm also wondering, why does magisk manager release channel still have 20400 for the magisk release? I thought the magisk release 21000 was released on october 3rd.
xp99 said:
I'm also wondering, why does magisk manager release channel still have 20400 for the magisk release? I thought the magisk release 21000 was released on october 3rd.
Click to expand...
Click to collapse
You need to switch to the Beta channel on Magisk Manager
I'm still getting it randomly freezing where I have to hard boot it.
So summary
OOS 9
Magisk 19
Disabled I think is quickswitcher module
Now I just get animation going forever on booting, if I leave it long enough about 20 minutes or so, it reboots itself and goes back to loop.
TWRP is accessible.
I tried MM recovery tool in core only mode but still doesnt boot.
Ideally I need a solution that doesnt involve a factory reset.
Ok the core only mode didnt stick I think, so did it again and the phone is booted.
With no phone app , completely gone off the phone.
It shuts down after about 20 seconds after booting up.
Backing up what I can over USB from TWRP, and this might force me to migrate to my Oneplus 8 pro which has been sitting in its box, but I will still appreciate any input on how to get this running again without a reset so I can properly migrate app settings etc even if its losing magisk.
I managed to keep the phone bpoooted up for ages, and have done things like titanium backups, app setting backups etc.
I then tried to reinstall the phone app from the play store but got a vague "cannot install phone from google".
But at least now I can access settings etc. Take screenshots of settings also. So better baseline for the new phone.
Pretty crazy how all this broke so easily though.
So I dont know how this happened but I managed to recover the phone.
The xXx rom magisk module got wiped when I deactivated the recents module, this removed the google dialer framework and some build.prop changes the rom module puts on the phone.
I initially just added the framework magisk module which allowed the google phone app to reinstall, all my call logs were intact. But the phone was still unstable on booting so had to reinstall xXx which seems to have fixed that, albeit now with added lag.
But I have backed up everything now anyway so will migrate to my newer phone its long overdue, but this post is here now in case anyone else has the same issue.