I downloaded the oneplus 10.44? boot.img and patched it using Magisk. I then proceeded to flash it to my device using adb/fastboot.
I installed lsposed and some modules, root was working fine. The only thing I was worried about was the constant bootloops anytime I would restart my phone.
Yesterday, my phone's audio stopped working altogether. It seems like my device is stuck in vibration mode? Anyways, at the same time, I started getting this message: "the version of the google play services installed on this device is not authentic". I checked my root again and as it turns out I have no root access even though everything worked fine just as few hours earlier. Any ideas what might have happened?
I reflashed the patch and after 20 minutes of bootlooping my device is on again. SU works perfectly fine, passes basic safetynet check, still no audio, 3.5mm doesn't register anything, mic picks up no sound, background image doesn't wanna stay on.
Youtube videos play but don't have sound, all other videos behave as shown below:
Related
So I'm basically making this a "fix my problems" thread, because I've got a lot of problems, and no solutions.
My phone is rooted running Sense 6 on Android 4.4.2, and ever since I rooted it about a month ago it's been a little... quirky.
For one thing, the stock weather app is no longer animated for me. The scene changes accordingly, but is completely static and doesn't play any sound effects even when the option is checked on. I texted a friend who has the same phone and also has it rooted, and he said his is animated and works just fine. It's more of a minor inconvenience than anything and doesn't bug me too much, but it'd be nice to have it function properly.
A more problematic... problem is that I'm no longer receiving push notifications for Twitter, Snapchat or Instagram in the notification bar. I looked it up and tried revoking access to the Android Twitter app from the web and logging in again, and nothing happened. I'd like to think it's a bug in the newest versions of the apps, but I didn't see any mention of notification issues in the Play Store reviews and the fact that all three stopped working simultaneously seems abnormal to me.
My phone also seems to have picked up an annoying habit of getting itself stuck in a bootloop whenever I reboot the phone. Once it powers on, it will then proceed to reboot itself about four to five times and then continue to function like normal afterwards. The other night it did the same thing, except it rebooted about seven or eight times and THEN stopped.
I have a sneaking suspicion that all of this has something to do with SuperSU. Shortly after I rooted the phone, the app prompted me to update the binary, which I attempted to do using the "update with TWRP/SCM" option that, according to the app, is recommended for HTC devices. My phone then had one of its bootloop episodes, lost root access, and has been doing it ever since. A few days ago I downloaded the latest SuperSU update from the web, transferred it to my phone via USB and flashed it with TWRP. When I booted it back up, SuperSU had vanished from the phone entirely. I reinstalled it from the Play Store and that seemed to do the trick at the time, but now I've suddenly lost root access after not even having touched SuperSU at all. I'm wondering if this affects apps that previously had superuser permissions, such as Battery Doctor. It had been stable until shortly after the root, after which it started behaving erractically - sometimes it works, sometimes opening it from the app drawer will pull up a black screen, and in most cases the widget either doesn't work at all, is extremely delayed, or will simply give the "Battery Doctor has been given superuser permissions for an interactive shell" message and then do nothing. So my question is, are all these problems being caused by a conflicting Play Store and binary version? And if so, how do I update it without screwing my phone up even further?
JayWulf said:
So I'm basically making this a "fix my problems" thread, because I've got a lot of problems, and no solutions.
My phone is rooted running Sense 6 on Android 4.4.2, and ever since I rooted it about a month ago it's been a little... quirky.
For one thing, the stock weather app is no longer animated for me. The scene changes accordingly, but is completely static and doesn't play any sound effects even when the option is checked on. I texted a friend who has the same phone and also has it rooted, and he said his is animated and works just fine. It's more of a minor inconvenience than anything and doesn't bug me too much, but it'd be nice to have it function properly.
A more problematic... problem is that I'm no longer receiving push notifications for Twitter, Snapchat or Instagram in the notification bar. I looked it up and tried revoking access to the Android Twitter app from the web and logging in again, and nothing happened. I'd like to think it's a bug in the newest versions of the apps, but I didn't see any mention of notification issues in the Play Store reviews and the fact that all three stopped working simultaneously seems abnormal to me.
My phone also seems to have picked up an annoying habit of getting itself stuck in a bootloop whenever I reboot the phone. Once it powers on, it will then proceed to reboot itself about four to five times and then continue to function like normal afterwards. The other night it did the same thing, except it rebooted about seven or eight times and THEN stopped.
I have a sneaking suspicion that all of this has something to do with SuperSU. Shortly after I rooted the phone, the app prompted me to update the binary, which I attempted to do using the "update with TWRP/SCM" option that, according to the app, is recommended for HTC devices. My phone then had one of its bootloop episodes, lost root access, and has been doing it ever since. A few days ago I downloaded the latest SuperSU update from the web, transferred it to my phone via USB and flashed it with TWRP. When I booted it back up, SuperSU had vanished from the phone entirely. I reinstalled it from the Play Store and that seemed to do the trick at the time, but now I've suddenly lost root access after not even having touched SuperSU at all. I'm wondering if this affects apps that previously had superuser permissions, such as Battery Doctor. It had been stable until shortly after the root, after which it started behaving erractically - sometimes it works, sometimes opening it from the app drawer will pull up a black screen, and in most cases the widget either doesn't work at all, is extremely delayed, or will simply give the "Battery Doctor has been given superuser permissions for an interactive shell" message and then do nothing. So my question is, are all these problems being caused by a conflicting Play Store and binary version? And if so, how do I update it without screwing my phone up even further?
Click to expand...
Click to collapse
You need to start over from scratch
post your fastboot getvar all (minus you serial.no and IMEI)
Most likely your using AT&T so if you have s-off you can flash these two and get back two stock. take the OTA Update then re flash recovery and root.
flash this first
http://fs1.d-h.st/download/00101/a1w/4.18.502.7 Custom Firmware.zip
fastboot oem rebootRUU
fastboot flash zip 4.18.502.7 Custom Firmware.zip
fastboot flash zip 4.18.502.7 Custom Firmware.zip
fastboot reboot bootloader
now stay on the bootloader
and run this RUU from your PC > http://www.androidruu.com/getdownlo...09_10.26.1718.01L_release_356565_signed_2.exe
Take the Over the air update and your all set to start rooting again.
clsA said:
post your fastboot getvar all (minus you serial.no and IMEI)
Click to expand...
Click to collapse
What is this, and how do I do it?
JayWulf said:
What is this, and how do I do it?
Click to expand...
Click to collapse
go to the folder where fastboot and adb are
open a command window (right click / command prompt here)
with the phone plugged into the PC
Type fastboot getvar all
it will output all the specs for your phone
remove the serial no and IMEI when posting it
what if your s-on
I'm having all the exact same problems except I'm 4.3 and s-on. Help please!
Gonna kinda bump this thread a bit because I've got another question - what about the "full unroot" option within SuperSU? Will this help the situation at all, or make it worse?
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
Direct questions at the bottom...
I didn't see anything about 18.1 causing issues (still see some about 17 causing bootloops) so I figured I'd start here before reporting a bug with Magisk.
After hitting the Google Pay update (but before finding that thread) I figured it was time to move from Magisk v17.1 to v18.1. Unfortunately patching 20d with the new Magisk Manager v7/v18.1 didn't work. I flashed the patched 20d boot image (adb/fastboot - no TWRP for me) and the phone booted up just fine and I swiped to see that my launcher was working and then the touchscreen stopped responding. The power button continued to function (would bring up off/restart/airplane mode menu). After a few moments the phone 'rebooted' in that the LG logo came up and then I was presented with my start screen again. The phone didn't fully reboot as it didn't go through secure startup, but I did have to enter my passcode to unlock and again my launcher worked for a few seconds before the touchscreen freezing. Between this and a few hard restarts (pressing and holding power and voldown) I was able to start and get into Magisk Manager which prompted me 'Your phone needs some additional setup - do you want to download magisksetup now to finish setup?'* It was only one time as every other time I could not get Magisk Manager to start fast enough to prompt me such that I could accept the 'extra setup' before the touchscreen froze. I later did the whole song and dance after dirtyflashing 20g, rebooting after Android did it's 'upgrading' thing and flashing the patched 20g boot - same touchscreen freezing after a few seconds. (NB: if you need fastboot, press and hold voldown same as if you wanted download mode for LGUP with volup). I had ADB setup & my computer trusted throughout all this and adb would disconnect when the phone did its 'reboot' thing so even grabbing logs is tough.
I ended up writing a custom json file and pointing the update channel in Magisk Manager v6.1.0 (185) at it to get v17.3 (17302) installed which doesn't exhibit the behavior. Stock is fine, but I'm not missing out on root.
*: Only time I've seen this message in person or in other various threads.
1. Has anyone seen the touchscreen becoming completely unresponsive with or without soft bootloops using Magisk or similar? Maybe it's because of RCTD (never experienced it on LG and Sony's RIC I think just rebooted)?
2. Any idea on how to gather logs in this case so I could make a bug report?
I'm starting here as I don't want to blame this on Magisk alone just yet as long as I can't seem to gather logs and I haven't seen this weird half bootloop reported on other phones.
Hi, had the same problem with the touchscreen and Magisk 18.1, all was totally slow, apps needed seconds to respond and so on.
Bootloops never.
My solution: gone back to Magisk 18 and all problems are gone. So it seems, there is a Problem withe Magisk 18.1 and our phone. I have the European H930.
Regards
mkpcxxl
mkpcxxl said:
Hi, had the same problem with the touchscreen and Magisk 18.1, all was totally slow, apps needed seconds to respond and so on.
Bootloops never.
My solution: gone back to Magisk 18 and all problems are gone. So it seems, there is a Problem withe Magisk 18.1 and our phone. I have the European H930.
Regards
mkpcxxl
Click to expand...
Click to collapse
Owh, I thought that it was the gcam. I have been flashing the roms 21w for multiple times and still have the freeze sometimes. A force restart is needed everytime...
So I bought a new Poco F1 few days ago. And since I've been using it, I've been facing bugs.
So when I got the device it had Miui 9.6.14 installed on it. And I just wanted to unlock it and root it asap. As you know you have to wait 3 days to unlock it. But as soon as I put in the unlock request i.e by going to fastboot and on mi unlock it shows 99% complete then it says you have to wait for this much time.
As soon as I did that, I faced the first bug. That was related mobile network settings/usb tethering/*#*#4636#*#* code (engineering mode IDK). So when I clicked on usb tethering, turned off mobile data/wifi, or the phone lost signal, it rebooted, from boot splash (not boot logo). Maybe this was the ROM's way of preventing any big bugs why do I think that? I'll explain later. So after rebooting I could turn on/off usb tethering but not mobile data or wifi. I can turn them off as soon as the phone boots but if I do it later i.e. after unlocking the phone, it rebooted.
So this is one of the bugs that has been consistent, the one that never got away. Well sometimes it did went away but not for long. Like sometimes if I haven't turned off the internet in a long time or restarted the phone properly, the data turning on/off doesn't reboots the device, IF the device isn't connected in usb tethering. Like few days ago I discovered that usb debugging could fixed it, but that didn't lasted long either. Sometimes turning off usb tethering then mobile data very quickly afterwards worked, but didn't lasted long or only sometimes it would work.
So the advice I got earlier was that, just flash a new software. While I didn't technically flashed the new software, I flashed the similar software, deleting all user data & everything, but that didn't helped. As it seemed in the beginning, that bugs weren't there but they started appearing later on. Now IDK if I used a locked un-rooted device, these bugs wouldn't appear, not too sure about that.
And you maybe saying, well you didn't flashed the newer version of the rom, then that's the problem, Well IMO it isn't. Here's why - So when I flashed the same rom, the phone got locked cause I forgot to select the "clean all" option in MI flash instead of "clean all and lock". So I unlocked it again, flashed twrp and as you may know that when booting twrp for the first time it asks you two options, "allow system modifications" & "read only". And the last time I flashed it I chose the read only option. But this time it didn't asked me. Now do you understand? As I'm not an expert in this, the guy who gave me this solution said maybe the device tree wasn't cleared. So how does flashing a new version is gonna make a difference if all of the files don't get deleted? If it's not gonna start fresh? I also used the command "fastboot erase recovery" (as suggested by that fella), that didn't helped either, just an FYI.
So I decided to install other roms, thinking maybe that could help. It seemed like working in the beginning but soon it started to fall down. First OS I installed, Pixel Experience, didn't had such bugs earlier, but there was a little one. If I disconnected the phone while it was in usb tethering mode, it would reboot the same way it did with miui. If you turned usb-teth off first, it didn't rebooted. So I thought I could live with that. But later more bugs started to appear. The same thing, turn off the internet and the phone restarts.
Remember when I first said maybe it was OS's way of not having bigger bugs, So that happened this time. New bugs like when I try to get into an app's info, the settings would crash (stopped working). BTW you could getting into an app's info if you are able to find the said app, by going into storage, then to apps. Moreover sometimes when I'd try to open the camera it would just show blank, or very dark image of the environment, not moving though, and sometimes, it would just work.
Then I installed Lineage OS. Didn't find such bugs, but I'm pretty sure if I do all this usb tethering stuff in there as well, I'm gonna find these bugs.
Now you might be thinking that how am I installing all these roms, well that's cause of MultiROM. And if anyone here is gonna say well that's the problem. STOP! Stop right there. These bugs were present there before I even used MultiROM.
Some other bugs I'm facing RN in Miui -
Auto Rotate not working. If I want to go landscape, I'd have to open an app/game that opens in landscape and switch from there, cause it gets stuck, vice versa for portrait. And you can only view it in default position i.e. you can't rotate to other landscape position if you wanted.
Camera not working, showing "can't connect to camera" error.
When I play offline games while these bugs occur. When I connect the headphones, the audio also comes out of the speakers. After I restart the phone properly, that stops. (This bug was also present in earlier stages when MultiROM wasn't used)
When going into second space, I created a txt file in mixplorer and when I try to open it, the system reboots. And I just checked by installing a root checker in second space, it says not rooted, wow!
When going to default file manager and tapping on storage, it said "disconnected" and few seconds later saying something like "couldn't add error 10000". This used to happen before but not now, neither I use the default file manager anymore. Though if I'm too quick and unlock the phone, open a file manager or any app that uses storage, it would go blank. Don't know if the storage crashes or something else. But after a restart, it's fine.
One thing, after the phone restarts when these bugs happen, "Find My Device stopped working" or something similar always appear, I don't remember the exact message.
[*]There are somethings Gcam related but I don't think they're 100% bugs related. Cause I installed the latest version on Lineage OS and it works as far as I used it even features like Night Sight and Slo Motion. Now those errors could be related to older android versions or something else IDK. Things like camera lagging in picture mode not in video mode and some version just straight up not working even when they're supported by older android 8.1.
Now could it be a hardware problem, IDK as I said I'm not an expert. These other bugs could've appeared cause of MultiROM or me flashing a new firmware over older rom version in order to install PE, again IDK.
Fair warning : If you're just gonna come here and say, Oh! this all cause of MultiROM or cause you didn't installed newer miui, then don't waste your time, cause I'm not gonna read any arrogant answers. Neither if you say, try to do this or that. I'm not here for that either. Cause if I wanted to do hit and trial, I could've done it myself
But if you understand the situation and can provide expert help, then only please reply. So if you're willing to help & understand properly, and you want anything from me, like logs etc. just tell me how to do it, I'll provide. Or if you know some way to do proper fresh install, only if that can fix the bugs so that I don't have to deal with them anymore, I'm looking forward to your reply.
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