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.
Related
Anyone had any luck getting root on Stock marshmallow? I flashed 2.67 Super bu couldn't get past the splash screen
Moto G User said:
Anyone had any luck getting root on Stock marshmallow? I flashed 2.67 Super bu couldn't get past the splash screen
Click to expand...
Click to collapse
As suggested in this thread, I flashed superSu BETA v2.62-3 (zip format) with the TWRP (3.0.0r2.
After that, updated superSu (apk) from the play store.
Then launched the app, and let it update the su-binary.
And now, supersu v2.65 is working like a charm on my stock Marshmallow XT1541 rom (XT1541_OSPREY_RETEU_2GB_6.0_MPI24.65-33).
rom-g said:
As suggested in this thread, I flashed superSu BETA v2.62-3 (zip format) with the TWRP (3.0.0r2.
After that, updated superSu (apk) from the play store.
Then launched the app, and let it update the su-binary.
And now, supersu v2.65 is working like a charm on my stock Marshmallow XT1541 rom (XT1541_OSPREY_RETEU_2GB_6.0_MPI24.65-33).
Click to expand...
Click to collapse
Thanks for the help. Got it working
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
I have the Droid Turbo xt1254 and have been running CrDroid. Today I tried to flash SuperSU 2.76 so I could access the app but I'm getting stuck with a bootloop at the Motorola Disclaimer page. I tried to enter TWRP through recovery and it gives me the splash screen and then goes into a Motorola Disclaimer bootloop. I'm pretty stuck here, as I can't event get into TWRP to reformat my phone. Any help would be greatly appreciated.
mbguitarman said:
I have the Droid Turbo xt1254 and have been running CrDroid. Today I tried to flash SuperSU 2.76 so I could access the app but I'm getting stuck with a bootloop at the Motorola Disclaimer page. I tried to enter TWRP through recovery and it gives me the splash screen and then goes into a Motorola Disclaimer bootloop. I'm pretty stuck here, as I can't event get into TWRP to reformat my phone. Any help would be greatly appreciated.
Click to expand...
Click to collapse
You can get into TWRP through ADB fastboot commands.
When you do so, you would want to flash the NEWEST SuperSu that is compatible with Nougat ROMs. 2.76 is OLD. That incompatible older version of SuperSU is most likely the cause of your problem...
ChazzMatt said:
You can get into TWRP through ADB fastboot commands.
When you do so, you would want to flash the NEWEST SuperSu that is compatible with Nougat ROMs. 2.76 is OLD. That incompatible older version of SuperSU is most likely the cause of your problem...
Click to expand...
Click to collapse
Not quite correct, the newer versions, 2.79 or 2.79 SR1, cause the same issue too.
mangojain said:
Not quite correct, the newer versions, 2.79 or 2.79 SR1, cause the same issue too.
Click to expand...
Click to collapse
Those are old also. Nougat is now on 7.1.2.
When I wrote that and even today, SuperSU-v2.79-SR3 is the newest. But I didn't want to list a specific version because 2 or 3 months from now it also maybe outdated.
Flash the newest SuperSu. That's what I said.
Is that so hard?
Why do you keep trying to flash older ones? Are you trying each one up the steps or something? Just jump to the newest and stop complaining.
Right now this is the newest...
SR3-SuperSU-v2.79-SR3-20170114223742.zip
But 2 or 3 months from now don't complain if it doesn't work. Go find the NEWEST.
Thanks a lot @ChazzMatt this really helped me to recover my phone, just downloaded the latest SuperSU (2.82 at this moment) flashed it and load the full system again.
Cj Marquez said:
Thanks a lot @ChazzMatt this really helped me to recover my phone, just downloaded the latest SuperSU (2.82 at this moment) flashed it and load the full system again.
Click to expand...
Click to collapse
You're welcome!
Super SuperSu 2.82 SR5 I think is the latest. But of course that will change again.
Ok,
I have fastboot and adb working on my linux mint host. Can someone explain to me how to install ota updates on a rooted pixel phone? I tried installing it via the zip using twrp and that didn't work. It just unrooted my phone so I had to reroot it. I tried using Flashfire and downloading the ota update and then using flashfire to detect the ota update and flash it and everytime it doesn't work... errors and then unroots my phone.
I never succeeded in OTA on my rooted pixel. I always download the full image then do upgrading via fastboot or flashfire.
bush911 said:
I never succeeded in OTA on my rooted pixel. I always download the full image then do upgrading via fastboot or flashfire.
Click to expand...
Click to collapse
Ok, I downloaded the ota update via Google's webiste. Flashed it with flashfire. It asked if I would like to overwrite the boot and recovery. (said it would most likely fail if I didn't.) I told it ok. It flashed for a while. Rerooted automatically. It booted back up. It didn't update. Still prompting me to update ota.
I just tried the second method in this article
https://www.howtogeek.com/192402/why-androids-ota-updates-remove-root-and-how-to-keep-it/
sailfish-n2g47e-factory-00a46e7e.zip
Then used flashfire to flash it like the article states. No error but my phone is still prompting and trying to update via Ota.
Which version of SuperSU are you trying to use? Both of the following links discuss verified boot, which is one possible item you could be running into with the latest Pixel updates.
SuperSU v2.82-SR1 is the latest version, and it added boot signing.
https://plus.google.com/+Chainfire/posts/XikxTkhHpiG
If you are using an older version of SuperSU, then you will need to sign the boot image. I installed the latest Pixel update before v2.82-SR1 was available, so I just had FlashFire install the OTA, and then I added the following zip to the list of FlashFire actions immediately after it was set to root the phone again. FlashFire worked without issue to update to the latest release for June by adding the following before rebooting when using a version before SuperSU v2.82-SR1.
https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
I am attempting to flash 2.79. but immediately after, I flash the verifiedbootsignerv3.zip
How to root my phone"
Sent from my itel it1408 using XDA Free mobile app
yared1212 said:
How to root my phone"
Sent from my itel it1408 using XDA Free mobile app
Click to expand...
Click to collapse
Not sure what you mean here...
dorlow said:
sailfish-n2g47e-factory-00a46e7e.zip
Then used flashfire to flash it like the article states. No error but my phone is still prompting and trying to update via Ota.
Click to expand...
Click to collapse
That looks like an April update, and there are newer versions, so I'm not surprised the phone would try to update.
https://developers.google.com/android/ota
Three months ago was the first time I tried FlashFire, and I couldn't get it to use the OTA to the phone at that time. Some of the FlashFire instructions made me think I might need to use the backup option to get the OTA to work, but I was actually able to take the May and June OTAs using FlashFire without the backup option. I'm not sure why FlashFire didn't work for an OTA in April, while it did work with an OTA on the phone the past couple months. I think I may have ended up using a download from the Google site with FlashFire in April, so my only guess was that either using the Google download or a newer version of FlashFire is why I was later able to use the phone OTA with FlashFire for May and June.
SuperSU v2.79 SR3 with either the VerifiedBootSigner v3 or v8 has worked for me in May and June, and then I've taken the Play Store SuperSU update to v2.82. I don't have TWRP installed, and I get the impression there could be some extra steps for FlashFire when TWRP is installed, so I don't have to deal with that. Of course the only reason I switched to using FlashFire is because it seems like the quickest method to just take an OTA and update with SuperSU. If FlashFire didn't work so easily, I'd just go back to sideloading, or using one of the other update methods.
Hey everyone,
I have a Nexus 5 that I haven't updated in a long time that I'd like to get the latest possible OS for. The only modifications I've made which I think might be important are:
Unlocked bootloader
Rooted using SuperSU (v2.8.2 currently)
Installed XPosed (installer v2.6.1, not sure what version of the framework but it should be the latest supported by 4.4.4) with a few modules
Installed App Ops and removed permissions from some apps
Installed StickMount
I don't believe I have any custom recovery installed (I'd used a script to root and install XPosed originally and I don't know if it made any other changes). I'm comfortable using adb if needed but I'm cool with tools like FlashFire too.
My end goal is to have an updated OS with root and XPosed. I assume I'll need Magisk for XPosed, but not sure about root.
How should I go about doing this? I'm cool with losing all of my data (I'll be making backups with Titanium Backup) though knowing ahead of time if that'll be the case would be nice. If it's possible to update without losing data and without affecting anything that'd be nice, but maybe a clean start would be good? The OTA guide on this forum is only for 5, not 6, and most online guides start with 5. I don't want to mess up obviously. xD
Any advice/steps would be appreciated! Thanks!
Aecyl said:
Hey everyone,
Click to expand...
Click to collapse
You need TWRP. Then to install it. https://forum.xda-developers.com/go...om-android-m-preview-2-flashable-zip-t3157299
pavik62 said:
You need TWRP. Then to install it. https://forum.xda-developers.com/go...om-android-m-preview-2-flashable-zip-t3157299
Click to expand...
Click to collapse
The link you gave doesn't have the latest 6.0.1 build and it also says that it requires a minimum bootloader (HHZ12h) that I don't have (I have HHZ11k). Would it be possible to use the latest build from Google? What do I do about the bootloader? And would using TWRP as the recovery prevent me from passing SafetyNet?
Thanks for replying!
Could I follow this guide with the latest factory image and then install Magisk, root, and XPosed? https://android.gadgethacks.com/how...actory-images-android-using-fastboot-0175277/
If you're on stock, update using the built in updates. That'll get you all the latest firmware. I'm pretty sure the N5 goes up to 5.0 normally.
Roxasmaker said:
If you're on stock, update using the built in updates. That'll get you all the latest firmware. I'm pretty sure the N5 goes up to 5.0 normally.
Click to expand...
Click to collapse
Would I have to do anything to XPosed or supersu first? I'd like to update to 6.0.1, too. I've seen online that there are OTA updates for it too.
Nope. But you may have to reinstall root, which is very easy once you're updated. Just let the updates do their thing, and you'll be on your merry way! Hope I helped
I think what I'll do is flash stock 4.4.4 keeping user data and then use the OTAs to update to 6. That way I have a clean system install to use Magisk with without losing any user data. (If that doesn't work I'll just flash 6.0.1 for a clean install.)