I am having a strange problem, one that I have never encountered before. I am on 38R and running ComaDose 3.5 mod (basically Crossbreeder with some extra tweaks) and a few Xposed modules. Stock kernel. I have used ComaDose on other devices with no issues, and it blocks ads very well. The other day I started seeing ads, so I uninstalled & reinstalled ComaDose. Still had ads. I uninstalled & reinstalled again, still had ads, and also lost root. I flashed SuperSu 2.13 in recovery, regained root, but still had ads. Reinstalled ComaDose, still had ads and lost root again. I figured ComaDose was the culprit and decided to flash Crossbreeder and SuperSu. Still had ads, still no root...really weird. I have used Crossbreeder on multiple devices with no issues. And now when I flash SuperSu 2.13 in recovery, it appears to succeeed, but when I reboot and open SuperSu app, it says device is not rooted. So I used OnePlus One Toolbox to revert to 33R, rooted, flashed the modified 38R update zip, and got a working "base" again. I flashed ComaDose and it worked for a while, then started gettings ads again. Wash, rinse, repeat. Now flashing SuperSu in recovery doesn't take (again). I am away from computer, so I can't re-root manually...I will have to wait until I get home. But this is the weirdest thing. I prefer ComaDose or Crossbreeder because they do not need updates, but I guess I'll go back to AdAway.
Update: I couldn't wait to get home so I flashed Calkulin's stock rooted 33R, finished the setup wizard, then went back to TWRP and flashed ComaDose. It seemed to work, because I didn't see ads in Chrome or apps, but I tried to install Xposed and it failed because no root access(?!). Uninstalled ComaDose, flashed SuperSu 2.13 zip, rebooted, had root again. Went back to TWRP, flashed Crossbreeder, tried to install Xposed and no go because no root again...FMR. Uninstalled Crossbreeder, flashed SuperSu zip (which appeared successful), rebooted, launched SuperSu app, and it said binary was not installed and not rooted. So I gave up on ComaDose and Crossbreeder. I reflashed Calkulin's stock rooted 33R, installed AdAway. So far, no ads and still rooted.
I have no idea what has changed, but my OPO does not like ComaDose or Crossbreeder any more. Oh well
Related
(Not sure if it is better to make a new thread or ask in the SuperSU thread...)
Hey all. I had previously been running the 7.1 OTA build with SuperSU installed. It seemed fine and I had done OTA updates with it installed with little issue. This was pre-2.78 SR3 builds of SuperSU, so I was using the boot-to-root. One day, I inexplicably noticed that root was gone. App too. I was very confused because to the best of my knowledge no OTA updates or security updates happened since I last rooted.
With that, I decided to sideload update to NMF26Q, which apparently was released about 12 hours earlier, and install TWRP since it was needed for newer SuperSU. TWRP installed fine and worked, but SuperSU did not seem to work. In fact, every time I attempted to flash SuperSU 2.78 SR5, I noticed it would remove the SuperSU app if it was installed via the Play Store. Finally, I noticed that it was installing in System mode.
I attempted to override this by running `echo "SYSTEMLESS=true" >> /data/.supersu`, but nothing I did worked. It did the same exact thing. Looking through the shell script, I'm entirely unsure how it is possible that my override did not work. I also reflashed the stock boot image to both slots and then reinstalled TWRP. This had no effect on installing SuperSU.
I try to do due diligence before turning to the internet for help, but I don't have any clue what's going on here. Maybe it is best if i reflash the entire stock ROM, but I'd love to avoid that if possible, as everything else seems to work great, and I have no idea why this in particular would be an issue.
Use alpha 2 of twrp and ask will be well
Yep, that worked great. Cheers.
http://forum.xda-developers.com/showpost.php?p=69626115&postcount=2
Earlier today i noticed i could not play super mario run because the game checks for root access. After trying it and failing, i decided to install magisk to cover up root. Booted in to TWRP Recovery and flashed magisk and rebooted. When prompted to install SU i accidently hit do not install and now the SU app keeps telling me to install SU. I tried updating the app and it tells me Su binary occupied. If i uninstall it it tells me that i need to update the binary then fails when i try it. Already tried flashing the update of SU through recovery and nothing. Tried removing all root access and it will not get removed. Even tried to root all over again through odin and still having the same issue. All root access apps tell me im not rooted. Anything i can try without getting rid of my apps and data? Only thing im thinking will be to fully unroot and install stock rom and wipe all data.
Im on a galaxy s5 from sprint, running stock deodexed rom 5.0 lollipop.
Crav3 said:
Earlier today i noticed i could not play super mario run because the game checks for root access. After trying it and failing, i decided to install magisk to cover up root. Booted in to TWRP Recovery and flashed magisk and rebooted. When prompted to install SU i accidently hit do not install and now the SU app keeps telling me to install SU. I tried updating the app and it tells me Su binary occupied. If i uninstall it it tells me that i need to update the binary then fails when i try it. Already tried flashing the update of SU through recovery and nothing. Tried removing all root access and it will not get removed. Even tried to root all over again through odin and still having the same issue. All root access apps tell me im not rooted. Anything i can try without getting rid of my apps and data? Only thing im thinking will be to fully unroot and install stock rom and wipe all data.
Im on a galaxy s5 from sprint, running stock deodexed rom 5.0 lollipop.
Click to expand...
Click to collapse
Its been a while since I used Magisk. But at that time, PHH superuser had to be used?? Not sure if that is still the case though. Sorry I could not be more help
Yes it does need to be used and it was already installed. But after rebooting the app was not in my app drawer and i had a notification to install SU through play store. But when i go to play store it says it is installed and needs an update. After updating it tells me su binary occupied and takes me to a page to help fix it but i already tried flashing superuser zip file through recovery and nothing changes
Similar Problem
Have you fixed it already because I am havibf the same problem here. I am usibg Samsung J7 Core
You can do what you said you would do (reinstall stock ROM) and then you can try again. Looks like thats the only thing you can do, unless you can somehow remove the root binary and the app using something like ES File Explorer (but again, it requires root) or you can try another root provider.
Hi,
I need some help. So basically what happened was I was rooted using the latest Supersu but was running 7.1.2 April patch on my Pixel. I stopped there since I read the May patch and supersu had issues. Now with the release of magisk for pixel I decided I wanted to update and change from supersu to magisk and here is what I did:
Went into TWRP and flashed unSU and then tried to flash magisk 14.2 but kept getting error 1 when trying to flash magisk. SuperSU was gone off my phone. I read that the issue with flashing magisk is I needed to flash the stock boot.img over the supersu patched one before I could flash magisk.
I wasn't sure how to get the stock boot.img so the next idea I had was to re-flash supersu, so I did that but the application didn't show up, so I remembered last time I did that that I had to delete the fstab.sailfish file. I did that then re-flashed supersu and it still wasn't there, so I downloaded the app from the playstore.
I went into the app and chose the full unroot option and said yes when asking if it wanted to restore the original boot.img.
After that I went back into TWRP and flashed magisk and it worked. I thought everything was good, when it booted all my root apps asked for permission.
Now the problems started , I kept getting the pop up that "android.process.media has stopped" working and also that gmail, calendar, photos, and the play movies app keep crashing.
I read that magisk can do OTA now without issues so I thought I would do the Android 7.1.2 to Anrdoid 8.0 jump using the OTA. I tried following this guide https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips.
I thought updating would solve my issues but it didn't upon reboot with 8.0 I am still having all those apps continuously crash. I noticed magisk isn't installed anymore even though i followed those steps regarding the OTA update and magisk.
I also noted that when I plug my phone to my computer and chose transfer files nothing happens, the phone doesn't come up under my computer so I can't transfer anything.
what are my options now without losing any of my data? I did make a TWRP backup before I started all this, should I restore that? Will I lose my photos if I do that?
Please help!
Edit: Tried going into TWRP and I got the "No Command" picture. I was able to boot back into normal boot and into the phone.
Edit: Since updating to Oreo the "android.process.media has stopped" doesn't seem to appear anymore not sure if still an issue but Gmail, Photos, Calendar, and Play Movies keep crashing.
For anyone else that runs across this issue, wipe data for com.android.providers.media
Have you installed official Xposed for Nougat?
Does it work fine on your MotoZ?
Any performance issues/lags?
Please add details on your ROM version, root method and if you have Magisk installed too or not...
Thank you.
I have this rom
Android Nougat on Moto Z (All Unlocked Versions) and rooted in the way that post says.
Installed xposed OK via TWRP, modules are correctly checked and enabled but didn't work, for example greenify didn't recognize that xposed is installed so didn't show the option.
Now I have missed data connection so am going to reinstall the same rom on the dirty way to not lose data and reinstall everything.
lilloscar said:
I have this rom
Android Nougat on Moto Z (All Unlocked Versions) and rooted in the way that post says.
Installed xposed OK via TWRP, modules are correctly checked and enabled but didn't work, for example greenify didn't recognize that xposed is installed so didn't show the option.
Now I have missed data connection so am going to reinstall the same rom on the dirty way to not lose data and reinstall everything.
Click to expand...
Click to collapse
Two things...
- Greenify needs to fix its compatibility with Nougat, it's a known bug
- It is *needed* to use new official Xposed apk v.3.1.2 to manage modules activation. I've seen that unofficial or old version aren't able to enable them properly...
Thanks I have just read that about greenify, the list of compatible modules with nougat is short at this time guess so
Sent from my XT1650 using Tapatalk
Mine doesn't boot with xposed installed.
Stock 7.1.1 with turboZ and magisk
I remember that installing magisk caused a bootloop on my stock 7.0
I had forgotten what modifications I did to my 7.0 stock (retus), trying to flash Xposed on it prevented it from booting (probably because of verity-dm) so I restarted from scratch.
1) Downloaded 7.1.1 stock from here and flashed it. Downloaded and installed 2 OTAs from system updates then.
2) Flashed latest TWRP (3.1.1-0).
3) I've read various reports of latest Magisk not working on Moto Z. Gave it a try though. Flashed Magisk v14.0, everything went well and I got back root access.
4) Tried installing systemless Xposed, however install failed from Magisk Manager, flashing the zip succeeded in recovery but Xposed wasn't recognized after reboot.
5) So I flashed classic Xposed (arm64) following these instructions, everything went fine (after one very long reboot).
Hi my fried. How long time this reboot in minuts?
Thanks
Ano59 said:
I had forgotten what modifications I did to my 7.0 stock (retus), trying to flash Xposed on it prevented it from booting (probably because of verity-dm) so I restarted from scratch.
1) Downloaded 7.1.1 stock from here and flashed it. Downloaded and installed 2 OTAs from system updates then.
2) Flashed latest TWRP (3.1.1-0).
3) I've read various reports of latest Magisk not working on Moto Z. Gave it a try though. Flashed Magisk v14.0, everything went well and I got back root access.
4) Tried installing systemless Xposed, however install failed from Magisk Manager, flashing the zip succeeded in recovery but Xposed wasn't recognized after reboot.
5) So I flashed classic Xposed (arm64) following these instructions, everything went fine (after one very long reboot).
Click to expand...
Click to collapse
josenilsantana said:
Hi my fried. How long time this reboot in minuts?
Thanks
Click to expand...
Click to collapse
It took maybe 15-20 minutes for the first reboot.
For me systemless Xposed install e worked properly too.
Ano59 said:
It took maybe 15-20 minutes for the first reboot.
Click to expand...
Click to collapse
Strange thing happened after flashing an update to stable 12.1.1.0 yesterday. As usual lost root, so then downloaded through Magisk Manager the 21.4 zip. Rebooted into TWRP and flashed, then had bootloop at the MIUI screen. I thought this was due to modules, so disabled them with Magisk Manager for Recovery Manager but no joy. I then downloaded 21.4 zip from web site (and uninstaller) and copied to phone, but still no joy with these (and no obvious errors).
In the end, I took the boot.img and patched using Magisk Manager, then flashed via TWRP. This took two attempts and then Magisk Manager said it 'needed to download' additional something or other. It was then I found that Magisk Manager had redownloaded and the 'hidden' version was not detecting root (however the one that just downloaded did). OK, so uninstalled the hidden one and went through setting up the new Magisk Manager again. I lost all modules and all settings for apps that were hidden from root, but got it all sorted pretty quickly.
My question is, has anybody else ended up in this bootloop, as I have never had any problems before reapplying the Magisk zip after getting the monthly stable update.....