Hello all, I've been having this problem with my Moto G4 Plus.
All of a sudden, my phone refuses to auto-rotate. I've only had this phone for nearly 3 weeks, and it's not even pre-owned. I've already disabled Xposed, removed any mods, wiped cache and davlink, and of course, rebooted. Is it time for a factory reset, this early in my phone's lifespan?
I'm running Android 6.0.1, stock rom and kernel, with Systemless Root and Xposed.
Thanks in advance.
Related
I have a friends S4 here that I rooted for them a while back and installed Xposes + Wanam to make their locked bootloader device a bit more useful. It worked perfectly for many months.
Recently they come back to me to tell me their phone dies very quickly when it is not in use and does get pretty warm. Battery panel shows that Android OS is using majority of percentage and not any more detailed. I realized that it was definitely OTA updated and that Xposed stated that modules were no longer installed nor did Superuser have root. I realized I made a mistake and forgot to disable OTA services.
What I have done so far: Re-rooted by flashing old kernel, flashed back to new kernel. Reinstalled Xposed modules and things SEEM to be perfectly fine. Two days later, the same thing is still happening. Android OS is definitely still hogging the CPU doing something in a loop.
I understand that a possible factory wipe from recovery MAY fix this issue unless System files are messed up and needing to use Odin to restore BUT I figure it'd be a great idea to come here and see if there's a quick fix that may be possible that could also help other readers that have run into the issue of accidentally receiving OTA while rooted.
Thanks for reading.
stevey500 said:
I have a friends S4 here that I rooted for them a while back and installed Xposes + Wanam to make their locked bootloader device a bit more useful. It worked perfectly for many months.
Recently they come back to me to tell me their phone dies very quickly when it is not in use and does get pretty warm. Battery panel shows that Android OS is using majority of percentage and not any more detailed. I realized that it was definitely OTA updated and that Xposed stated that modules were no longer installed nor did Superuser have root. I realized I made a mistake and forgot to disable OTA services.
What I have done so far: Re-rooted by flashing old kernel, flashed back to new kernel. Reinstalled Xposed modules and things SEEM to be perfectly fine. Two days later, the same thing is still happening. Android OS is definitely still hogging the CPU doing something in a loop.
I understand that a possible factory wipe from recovery MAY fix this issue unless System files are messed up and needing to use Odin to restore BUT I figure it'd be a great idea to come here and see if there's a quick fix that may be possible that could also help other readers that have run into the issue of accidentally receiving OTA while rooted.
Thanks for reading.
Click to expand...
Click to collapse
You could downgrade back to nc5 by flashing the tar file. Nc5 tends to be more stable and battery life is decent. I tried running nk1 for awhile, running into the same issues. I went back to nc5 running echoerom v39.1
I've got the moto e 4g variant eurpean, or XT1024, and yesterday i've unlocked my bootloader, rooted, instaled a custom recovery and kernel, but i've got a few doubts about this and that...
For example in Xposed, i've installed xposed, by flashing the zip and installing the apk manually, but now it says my system is out of space, even though the device was wiped clean, i've cleaned the cache and davlik as i've seen on the internet.(solved via this method)
But does the memory leak module work on moto e? And what other modules do work with moto e? like xstana, gravitybox and so on
Second doubt when the OTA comes out, I can just factory reset my device via TWRP, loosing root, and after that updating to 5.1?
I have a few other doubts regarding the custom roms, if they're good as daily drivers or not. And if the method of installing the 5.1 update manually does bring any bug and if it ends that crazy lag that appears sometimes.
Thanks a lot for your time
Filz0r said:
I've got the moto e 4g variant eurpean, or XT1024, and yesterday i've unlocked my bootloader, rooted, instaled a custom recovery and kernel, but i've got a few doubts about this and that...
For example in Xposed, i've installed xposed, by flashing the zip and installing the apk manually, but now it says my system is out of space, even though the device was wiped clean, i've cleaned the cache and davlik as i've seen on the internet.(solved via this method)
But does the memory leak module work on moto e? And what other modules do work with moto e? like xstana, gravitybox and so on
Second doubt when the OTA comes out, I can just factory reset my device via TWRP, loosing root, and after that updating to 5.1?
I have a few other doubts regarding the custom roms, if they're good as daily drivers or not. And if the method of installing the 5.1 update manually does bring any bug and if it ends that crazy lag that appears sometimes.
Thanks a lot for your time
Click to expand...
Click to collapse
I can only talk about 5.1 firmware, as I don't use Xposed. I manually flashed the 5.1 firmware for this phone and it's much better than before. Much faster, snappier, some bugs are not there anymore. There's no lag, well, I haven't experienced much. Something that annoys me is that Chrome takes about 4 seconds to start, it feels slow.
Hi everybody,
I'm using a Redmi Note2 Prime with MIUI 8 7.4.27 Beta (weekly). The phone was running very smooth, fast and reliable - battery life was always several days.
Yesterday I tried to root it using method 4 from here using recovery.img from TWRP 3.0.2-2.zip and UPDATE-SuperSU-v2.79-20161211114519.zip (SuperSU app was already installed). After several attempts (installed MI PC Suite twice until it worked on Win10) it finally worked.
I rooted since I wanted to try dual boot patcher and a MM ROM as second.
But after phone booted again it was nearly unusable. No smooth reaction I had to wait several seconds until screens changes when just scroll through them. Also apps and settings now need lots of time more before they start. Wifi is always turned off after reboot (while it was on during shutdown) and Google sync starts automatically after reboot while it is deactivated in all settings. Also background image of lock screen was changed. Google Play Services are now constantly crashing (need to click away these message requesters all the time) and Play Store does not even start anymore. Meanwhile I removed SuperSU app again since it never asked for granting root access while it was set to do so.
Installing a second ROM using Dual Boot Patcher finally also did not work (patching worked - installing not). Details are provided here.
I am still puzzled what happened here and do not have any clue since I rooted already several devices without any problems so far. Even this one some time ago IIRC.
Does anybody have any idea how I can get the phone back into a stable, usable mode? Do I have to completely reflash the MIUI8 ROM? Or do I have to use another SuperSU zip?
Any help is highly appreciated!
Thanks guys!
You can try wiping data/factory reset.
To easily install TWRP, you can use the Fastboot Install Method described here:
https://twrp.me/devices/xiaomiredminote2.html
Thanks. But doesn't this wipe/reset delete all apps and data (which I try to avoid)?
Would reflashing complete MIUI8 (version which I already have installed - without any system/data wipe) cure the problem?
TWRP app is already installed - but either TWRP recovery or SuperSU.zip crashed the Google Services (Play Services or even more) for whatever reason.
Does anybody have some idea why this might have happened? Maybe due to dalvik cache wipe which was requested?
I think that the phone become unusable a Google Services/Play Services is crashing because of wrong settings or data corruption.
That's why I said to do a factory reset.
You can try deleting just cache and data for Google Play Services and Google Play Store apps. Data are on cloud and should be restored automatically when needed.
Seems I got it working again - thanks to post #2. Used TWRP app to install another TWRP, afterwards I got a reboot loop. Then I deleted cache and dalvik cache and now everything works fine again!
Thank you!
Well Dual Boot still does not work but progressed a little bit further - but this is a different topic.
Try do delete your Rom (Backup all with Titanium backup before) and try to install latest Dev from mi-globe ! Prerootet and very smooth and good ROMs!
Thanks. But as said - got it working again (see above). The only thing which is not working is flashing a secondary ROM using Dual Boot Patcher (already opened another thread and posted it into the PATHCER thread - but seems nobody knows about some solution...).
Hi
After my last updates installing NOS and McAOSP separately
(now I am in Mcaosp ROM Oreo)
the phone goes into randomly reboots and keeps bootlooping once or two times after simple tasks such as playing a game or opening an app e.g root explorer
.but not all the time maybe now maybe after two days really unexpected.
Any fix?
I did factory reset
Wiped data's e.t.c
Restore
Nothing fix the my issue.
Update rom to newest version. try with custom kernals like "agni" or "radon" and magisk to root.
I am in last update. Also tried Agni latest.Magisk fan too. But no luck.
I am running lollipop 5.1.1 arm64v8 on my china tablet.
The OS came odexed and I plan on modifing the framework and system apks.
Thus I need it rooted to de-odex the tablet.
As soon as I rooted it (using chainfire's SuperSu), it optimizes apks every
time I boot.
I have tried clearing delvik-cache, and even went so far as factory reset.
Nothing seems to help.
I'm not sure how to install Magic since I have an off the wall brand and I'm not sure that would
even work.
Any help would be appreciated.
-Twilight Time-