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
In January I installed SuperSU 2.6.2-3 in accordance with this forum. Interestingly, today I received notification from the Playstore to update SuperSU to 2.65 (dtd Feb 01, 2016). I don't know why I received this notification from the Playstore since I did not install from there and did not receive this notification much earlier. Also, I assume updating to 2.65 through the Playstore would not be a good idea.
Chainfire has recently decided that SuperSU 2.65 was Stable. Only Stable versions get pushed to the Play Store, so that's why you got an update. I believe it will be safe to install, but be sure to make a backup via TWRP first.
Funcionando en Moto g 2015 xt1543 México [MM]
Probé la actualización y todo bien ? OK
TVD1903 said:
Chainfire has recently decided that SuperSU 2.65 was Stable. Only Stable versions get pushed to the Play Store, so that's why you got an update. I believe it will be safe to install, but be sure to make a backup via TWRP first.
Click to expand...
Click to collapse
But my first SuperSU flash was 2.65. And like many others on this forum who did the same, this version soft bricked my phone (stuck on unlocked boot loader screen). Are you saying 2.65 is safe to install on top of 2.6.2-3 but not safe as an initial install?
MrTooPhone said:
But my first SuperSU flash was 2.65. And like many others on this forum who did the same, this version soft bricked my phone (stuck on unlocked boot loader screen). Are you saying 2.65 is safe to install on top of 2.6.2-3 but not safe as an initial install?
Click to expand...
Click to collapse
I think so yes, as the new version was designed as a version to be compatible with every version of Android an to be installed over older versions. Do make a backup though, and if you are afraid, just don't do it. It won't hurt to stay on an older version for a while. You can install the update to the app because that will not immediately install the actual SuperSU update. Do not accept the prompt when opening the app for updating the binary in that case though.
TVD1903 said:
I think so yes, as the new version was designed as a version to be compatible with every version of Android an to be installed over older versions. Do make a backup though, and if you are afraid, just don't do it. It won't hurt to stay on an older version for a while. You can install the update to the app because that will not immediately install the actual SuperSU update. Do not accept the prompt when opening the app for updating the binary in that case though.
Click to expand...
Click to collapse
So what version of SuperSU do you have installed? How did you install that version? On top of a previous version or a fresh TWRP flash?
MrTooPhone said:
So what version of SuperSU do you have installed? How did you install that version? On top of a previous version or a fresh TWRP flash?
Click to expand...
Click to collapse
I am using a Custom ROM with SuperSU built-in. I have however also used the Stock ROM with SuperSU v2.65, installed using TWRP.
Got the same notification, updated fine, updated also su binaries (asked by the app) and - everything works fine. Stock 6.0.
Well I was reluctant to try based on my first experience flashing 2.65. But I accepted the update via Playstore, SuperSU updated the binaries, rebooted, and all is still good.
I would assume all those rooting the G3 MM for the first time should use 2.62-3 then upgrade to 2.65.
MrTooPhone said:
I would assume all those rooting the G3 MM for the first time should use 2.62-3 then upgrade to 2.65.
Click to expand...
Click to collapse
This is how I did mine when following the thread :
[GUIDE] [OSPREY] [MM] Install TWRP, Root and Xposed successfully on 6.0
Installed 2.62-3, then just received the 2.65 from the app store. No problems here either. Not sure about the TWRP update from 2.8.7 r7 to the 3.x.x versions though, but I am getting the impression that due to extensive changes it is not a good idea.
pjc123 said:
This is how I did mine when following the thread :
[GUIDE] [OSPREY] [MM] Install TWRP, Root and Xposed successfully on 6.0
Installed 2.62-3, then just received the 2.65 from the app store. No problems here either. Not sure about the TWRP update from 2.8.7 r7 to the 3.x.x versions though, but I am getting the impression that due to extensive changes it is not a good idea.
Click to expand...
Click to collapse
I have had no issues backing up with twrp-osprey-3.0.0-r2.img. I have not tried restoring yet.
I see there was an update yesterday again from the play store (version 2.79). Has anyone tried it? I am on stock, root, with TWRP (3.0.2-r1). I see I am falling behind on TWRP as well, seeing it is at 3.0.2-r5.
pjc123 said:
I see there was an update yesterday again from the play store (version 2.79). Has anyone tried it? I am on stock, root, with TWRP (3.0.2-r1). I see I am falling behind on TWRP as well, seeing it is at 3.0.2-r5.
Click to expand...
Click to collapse
don'tn worry ... the update works perfectly ...
..::Matr!x::.. said:
don'tn worry ... the update works perfectly ...
Click to expand...
Click to collapse
Thanks.
pjc123 said:
I see there was an update yesterday again from the play store (version 2.79). Has anyone tried it? I am on stock, root, with TWRP (3.0.2-r1). I see I am falling behind on TWRP as well, seeing it is at 3.0.2-r5.
Click to expand...
Click to collapse
I have received several updates since 2.62-3. All have installed from playstore just fine including 2.79. As an initial installation, I think 2.62-3 was the only one that installed as systemless without forcing a systemless installation. Once you have a successful installation, all updates should be as well.
Sorry I'm not able to help you but you can help me. I soft brick my Moto g xt2541 twice due to different super su and wrong recoveries . Can you please provide me links u used to root. My issue is listed here. http://forum.xda-developers.com/2015-moto-g/help/unable-to-root-moto-g-2015-1-gb-model-t3523471 your help is much appriciated
Sent from my MotoG3 using Tapatalk
mirpuri said:
Sorry I'm not able to help you but you can help me. I soft brick my Moto g xt2541 twice due to different super su and wrong recoveries . Can you please provide me links u used to root. My issue is listed here. http://forum.xda-developers.com/2015-moto-g/help/unable-to-root-moto-g-2015-1-gb-model-t3523471 your help is much appriciated
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
I followed these directions eleven months ago for the initial unlock bootloader, TWRP recovery and root, using the versions of SuperSU and TWRP listed, however I did not install Xposed.
http://forum.xda-developers.com/201...twrp-root-xposed-t3294588:confused::confused:
I have since updated to:
SuperSU 2.79
TWRP 3.0.2-r1
Caveat: My phone is a XT1540.
So I've seen a few threads asking a similar thing but since they're quite old, I'd like to ask again.
Quick info about my setup:
running stock ROM, MOB30H
system-less root
system-less Xposed
kernel: ElementalX
TWRP recovery
I was hoping I'll be able to install OTAs with less hassle thanks to up-to-date SuperSU and a special version of Xposed. I indeed have received an OTA today - a small update, I believe 9 MB. When I tried to install it though, TWRP booted up and nothing happened.
Does someone run a similar setup? Have you been able to install an OTA after flashing stock recovery (which I guess is what needs to be done to install OTAs)? Would I have to reflash SuperSU and/or Xposed?
Hi,
I unlocked My bootloader successfully and installed twrp. Everythings fine so far.
Now I saw a thread mentioning a rollback to stock 6.0.0 is neccessary before installing cm13 because of the baseband. Do I still have to do that?
I also read about supersu. Do I have to install it before cm? In a rooted device? I thought supersu is for rooting the device?
And finally I thought cm13 is stable for My A9 but there are only nightly builds. Recommended for daily use?
Sry for all those noob questions, but I already read around for hours, without coming to a solution. Although flashing cm to My S5 Mini was alot easier.
I appreciate any help with that stuff.
?
Btw. I saw the supersu Thread and I found instructions on how to root the device.
The Instruction says I have to install supersu to root the device. In the supersu thread they say my device has to be rooted to install supersu.
Confusion is complete
On all devices I've had, never had to root (SuperSU) to install CyanogenMod. Just unlock bootloader and install twrp.
The SuperSU thread is wrong, I read the same thing when I had a nexus 5. I think it means just bootloader needs to be unlocked.
Only time I used SuperSU was if I was on stock rom. CM13 has root built in. Enable it in developer options.
As far as having to downgrade to 6.0, no idea if it's still needed. It's one of the reasons I'm still on stock. I don't like methods needed to downgrade.
thx
Thanks for your reply.
I installed CM13 nightly successfully on my A9.
No Rollback neccessary.
itsabrick said:
Thanks for your reply.
I installed CM13 nightly successfully on my A9.
No Rollback neccessary.
Click to expand...
Click to collapse
Really? Your phone had latest stock update and you installed cm13, and have no issues with it? No boot loops?
I've been using cm for some days. Some apps a crashing once a while, voice recording in whatsapp doesnt work without crashing the APP. AS far as I use My phone it is fine.
I booted the phone two times since I installed cm and no bootloops.
Bought it in germany.
Edit: Don't know it was the latest stock. I left the Version that was already installed on the phone. AS far as I remember it was 6.0.1
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