Hello guys,
So, i have rooted my Device (BQ M5) 1 Month ago and installed Xposed on it. Everything was fine until yesterday, where i was underway and streaming via Chrome a video. I didn't close Chrome and simply locked my phone. Several minutes later, when I tried to unlock my phone, i directly noticed heavy lag (response 2seconds - 2min - locks device). I thought a reboot might solve this issue, but i was wrong. I started to uninstall several previously installed apps and tweaks (where the newest App/Tweak was 8 days "young".
After a reboot, still heavy lagging. I opened TWRP and Cleared Dalvik and Cache, did a reboot in System, Recovery and Bootloader. I even flashed the device with a complete fresh OS. The problem still remains. After several re-flashings, some cache clear, factory resets and SuperSu unrootement i somehow managed to get it to work again. So I started from 0 again, and installed all previous apps, and root apps. Everything was fine for several hours (connected to Wi-Fi), so i was installing Xposed again, with 2 apps/tweaks: Flat Style bar, youtube adaway. Everything was still allright untill i left the house. I unlocked my device 50min later (for the first time when i left my house) and boom, the lagging was back. (Don't have internet outside my house).
As soon as i came back, i retried everything to remove the lag, however I did now several things in addition for over 3h and the lagging sill remains. I down and upgraded the OS, formatted the data, did every clear in TWRP and Bootloaded that i could find. I reset it via Settings and flashing. I installed SuperSu and de-installed it.
I don't know what else i could do, to solve this issue. The lag remains when using TWRP, Bootloader, using the Device, or when the Booting animation of android appears (slow animation or with a "fps of 0,05").
Please help me!
Device: BQ M5
Had Android 5.1.1. on it and Installed xposed sdk22 arm, and installed SuperSu via TWRP.
All files were downloaded from official posts here on xda, or from the brands website.
p.s. Even the littlest information which could help, please share!
p.p.s Here's a video that shows whats going wrong. After the reboot the booting animation continues like this around 1-3min. and then at the unlock screen, the "lag" still remains. What i noticed too, is that the charging animation in the top right is running flawlessly, however opening apps and all the rest is really slow!
youtube(dot)com/watch?v=Htuhj8UzWs4
Related
I have a VF-895N (rooted and stock rom - update 130FFN2), yesterday I decided to update my phone from 5.0.2 120FFN2 to 5.0.2 130FFN2, I removed root and made a hard reset, started the update process but at the very end of the update, it said "error", then I got stuck into a bootloop " no command" but managed myself to re-flash stock rom already updated with the latest version. When it finished flashing, I booted up the phone, started to remove bloatware, rooted the phone and started to install apps like Facebook, Instagram and other stuff like that.
I finished installing all the apps I wanted but I noticed my battery was draining very fast and also my phone was overheating, I tried to open Instagram for the first time but it freezed, tried the same with Facebook, it freezed.
Overall the phone's performance was very bad comparing with the one I had before re-flashing.
Now I don't know what to do, some apps close or freeze, the phone does not overheat much now bcuz I installed setcpu and set the values to min.=240mhz and max.=980mhz tho I don't understand much of these things... (Initially the values were 1.020mhz of min. And 1.020mhz of max.
I did hard reset 3 times and I always got the same result and I also cleaned the cache too.
I can't downgrade bcuz there is no stock rom available anywhere except for a flash tool (Sugar QCT) that flashes the latest update, which I already have and seems to be broken.
Please help me.
I rooted my S6 Edge a couple of days ago with no problems. I later added xposed and a couple of modules, no problem (apart from swipeback needing removed after it disabled my camera/gallery). Last night I shut my phone down and put it on the charge for the night. Today after turning it on it was stuck in a boot loop. I have been searching for fixes but there seem to be many different scenarios. I have tried to boot to recovery multiple times to do a wipe partition cache as that seems to the general fix. Problem is I am only able to get into TWRP. So I tried to do a default wipe with TWRP (Says wipes Data, Cache, and Delvik (not including internal storage) ). My phone now only boots to logo before shutting back off. I assume anyway because it isn't boot looping anymore and holding the power button gets the same result, logo then black screen again.
I am able to get into TWRP menu though I should add just about any option I choose, after it executes/completes the phone freezes and needs to be forced off/restarted. It has done this since TWRP was installed.
I am also able to get to ODIN mode.
If I remember correctly it is the G925F Global model. Running 6.0.1 stock, rooted using SpaceX kernal.
This is the process I used to root: edit: Seems I cannot link until I have at least 10 posts. How to Root Galaxy S6/S6 Edge on Android 6.0.1 Marshmallow!
BY MAX LEE google that and top result should be the site I used.
Any help would be greatly appreciated. If you would need anymore info I will gladly do my best to give it. I would like to fix this without losing all my data, apps pics music etc. But if all else fails I am prepared for that.
My phone (Nexus 4) appears to be soft-bricked, and will not boot up. When I turn on the device, it appears to get part way through the boot process but it never completes, and the bootsplash just keeps spinning forever. The top of the phone where the radios/gps/etc are gets very hot during this time.
I've tried: clearing caches within TWRP, factory reset, loading a couple new ROMs, wiping all partitions and reformatting, updating TWRP. Nothing seems to help.
I'm starting to think it's a hardware problem, but I'm hoping that someone might be able to give me some ideas that I haven't tried yet. I can get into TWRP and can load ROMs.
Some background: My phone is a Nexus 4 (mako) and had Cyanogenmod 13.1 prior to the issues, which has been running fine since last year. Recently my phone was acting glitchy/slow, so I decided to clear the cache and dalvik cache a couple weeks ago. This worked great and got things working well again. When I set things up again I also decided to start using DroidWall, which was the only app on my phone using root. About a week ago I also replaced the battery inside the phone since my old battery was shot and could barely keep a charge. The new battery has been working well, and does not appear to be the part of the phone heating up when the phone is stuck booting.
An update. I found that with the Slim ROM loaded, I can run `adb logcat` while the phone is booting to see what's happening. Lineage OS does not seem to ever get far enough to be seen by adb.
When viewing the Slim logcat, there are a lot of logs generated. Within, there are some DEBUG and backtraces displayed. And, I think the phone may be stuck trying the same thing over and over again as I've seen a section appear about the camera several times.
Earlier today I opened up my phone again, and noticed some pressure contacts on the back cover of the case. I cleaned them all to make sure they were making good contact, but it hasn't helped.
Now this is the weirdest thing I've ever encountered! I have a Samsung Galaxy Note 8.0 tablet (n5110) which runs TWRP recovery and Resurrection-Remix-5.7.4 (CM13 based). Everything used to work beautifully until the end of July when an app called “EPB DVR Manager” (in the Play store) received an update. My tablet had to do a whole bunch of updates, so I gave it the “go” and Play Store started doing its thing, updating one app after the other.
At some point the tablet froze. Dead. Even the clock in the status bar stopped. I had to reset the device by pressing and holding power until it rebooted. The next thing was ... boot loop. It seemed to finish the boot animation and at the point when the main screen is supposed to show up it rebooted!
Tried to wipe dalvik & cache. No go, still boot loop. Had to format data to get the device back to life. From there it took me quite some hours of repeated tries of restoring 100+ apps and crashing the device all over until I figured out that it was this specific app - the “EPB DVR Manager”. After figuring out that this app causes the problem, I did two more attempts to confirm what is going on:
First, I did a wipe of dalvik, cache & data, reboot, android setup wizard (setup Google account). Then, as the first action at all, I tried to install the “EPB DVR Manager”. Boom - device messed up again.
Second, I reverted back to stock firmware (kitkat) and installed the “EPB DVR Manager” - no problem at all. So it has something to do with the Resurrection-Remix ROM, but here's the thing:
I have 3 different devices (a Moto G 3rd Gen, a LG GPAD 7.0 and that Samsung Note 8.0) and all three of them run Resurrection-Remix 5.7.4 and the Samsung is the only device which all in a sudden has these catastrophic problems with the latest version of this app (earlier versions installed/updated fine).
Now I understand that my devices run different kernels with different hardware drivers despite all of them running RR-5.7.4.
I would really like to get a clue about what the heck is going on here. Now before y'all are telling me that RR-5.7.4 is dead because it is based on CM13 - I know that. Still, RR-5.7.4 is a way better daily driver than the newer Nougat builds. So how should I try to get “live logs” because the problem always ends in a crashed installation and Android needs a full wipe to recover. I would like to find out what is going on to be able to let the app developer know about the problem (if the app's apk is at least partially to blame).
Even if it turns out that it is RR's fault (and therefore the bug will not be fixed because RR-5.7.4 is dead) I would still want to learn how such a simple transaction like installing an app can cause such a dramatic (and 100% reproducible) crash of Android's data partition.
Thanks for any suggestions on how to catch logging information for this kind of mystery.
Markus.
Well, this is puzzling. My V30+ is rooted using stock Oreo. Has been working just fine..until today, when I had GMail open trying to read some emails. They wouldn't fully open (spinning circle on screen), then I got an "Edge has stopped working, close app, report feedback". Huh..wasn't using it at the time. Tried a few more emails, same thing happened. Uninstalled Edge. I could open emails again. Decided to install Opera instead. And I rebooted the phone. Now I have had "android is restarting" loop for the last 15 minutes. Tried removing replacing the SIM card, no joy.
Booted to recovery wiped Dalvik & cache, restarted phone, same thing again. The GUI is not coming back on. I can pull down the Gmail icon at the top, read emails, even play YT video someone sent me, but no main screen, no access to anything.
And this is my work phone...
Gave up on trying to solve it. Tried dirty flashing, but cannot get back root (Magisk 18.1, same v I had before) Doing a clean flash now...and praying.
Weird ?
You shouldn't be having such issues
While you're at it, you could try magisk 20.4
That one should work fine
Do I need to uninstall 18.1 first? I know there used to be uninstall zips around matched to versions ...
I know this should have been easy peasy.
Ah, success! Found a 18.x uninstaller, ran that & then flashed 20.4. All bettah!
thanks