Database Info

SUPERSU link for OPO COS 13 ( 6.0.1) ? help

Hello Friends,
I have tried to root my OPO running on cos 13 through TWRP. Unfortunately the rooting failed and the phone failed to start, It hangs in "cyanogen mod ready " boot animation screen. some how I have managed to flash the phone to stock OS and again updated it to COS 13.
Now I would like to root the phone , Please someone provide me the right SUPERSU link !
so that I can use it through TWRP.
P.S: The bootloader is already Unlocked.
Thanks in advance :good:

I'm dealing with the same problem, and I've had to flash the system partition back to 5.1.1 and then upgrade to 6.0.1 3 times. Each time I try installing different versions of SuperSU It hangs. Apparently you aren't supposed to install it, and enable root from the developer options, but I don't have any such option.

srink.007 said:
Hello Friends,
I have tried to root my OPO running on cos 13 through TWRP. Unfortunately the rooting failed and the phone failed to start, It hangs in "cyanogen mod ready " boot animation screen. some how I have managed to flash the phone to stock OS and again updated it to COS 13.
Now I would like to root the phone , Please someone provide me the right SUPERSU link !
so that I can use it through TWRP.
P.S: The bootloader is already Unlocked.
Thanks in advance :good:
Click to expand...
Click to collapse
squigley said:
I'm dealing with the same problem, and I've had to flash the system partition back to 5.1.1 and then upgrade to 6.0.1 3 times. Each time I try installing different versions of SuperSU It hangs. Apparently you aren't supposed to install it, and enable root from the developer options, but I don't have any such option.
Click to expand...
Click to collapse
You need to flash the beta sytemless SU, downloads are at the bottom of this post. Latest is BETA-SuperSU-v2.67-20160121175247.zip - http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3

Ok, so I found a Beta version of SuperSU 2.7.1, and it seems to have worked. It was a different install process, saying it detected a "systemless root" or something, and it needed to patch the boot image. After that I appear to have root access again..
https://download.chainfire.eu/932/SuperSU/BETA-SuperSU-v2.71-20160331103524.zip
Edit: Whoops, guess I should have refreshed the page before posting.. What you said is correct Ken.

Thank you
kenboyles72 said:
You need to flash the beta sytemless SU, downloads are at the bottom of this post. Latest is BETA-SuperSU-v2.67-20160121175247.zip - http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
Click to expand...
Click to collapse
thanks a lot

DONE
http://imgur.com/hh3qkdxGuys Finally I have done it. Yes the phone is rooted now
1. Flash Stock COS 12
2.Update Stock COS 13 using stock recovery
3. Installed SUPERSU (chainfire) from Play Store
3. Install TWRP
4. Create NANDROID BACKUP (optional , I have created since I doubted the rooting process on cos 13)
5. Installed Latest STABLE SUPERSU ( V 2.65 as of now) {my last attempt with beta 2.71 failed }
6. Done
http://imgur.com/hh3qkdx

[HELP] root problem

hello guys
i have a Samsung galaxy S6 g920F running on 6.0.1 with baseband G920FXXU3DPB6.
I have previously rooted my phone using CF-autoroot. Suddenly today when i tried to use superSU, it said "There is no SU binary installed, and superSU cannot install it. This is a problem!. If you have upgraded to Android 5.0, you need to manually re-root".
As i said above that i have rooted after i updated to 6.0.1 and was working till yesterday. i don't know what happen today that it started giving me this error.
I even downloaded latest cf-autoroot from its site and flash it through odin, but still no luck.
Can anyone please help me.
Thanks.

Flash a custom recovery and a kernel and then This
Had the same issue and doing this solved it. hope it helps

Here is how I get the root access back.
1. Copy to phone SuperSU 2.72
2. Flash with Odin arter97 kernel 13.1 (it has TWRP also)
3. Reboot in TWRP and flash SuperSU.
4. Reboot the phone

turulojko said:
Here is how I get the root access back.
1. Copy to phone SuperSU 2.72
2. Flash with Odin arter97 kernel 13.1 (it has TWRP also)
3. Reboot in TWRP and flash SuperSU.
4. Reboot the phone
Click to expand...
Click to collapse
can't we use on stock kernel only as it was before instead of flashing a custom kernel..?

Can't root stock Nougat (bootloaders unlocked)

Spend whole day browsing XDA, still can't get the thing done.
Running stock Nougat 39.2.A.0.361 with unlocked bootloaders and TWRP 3.0.2.0. Downloaded SuperSU 2.79, booted into recovery and flashed SuperSU. No errors, just a success message. However, after rebooting the phone, no sign of SuperSU exists. Flashtool also indicates root access is denied.
When installing custom ROM with SuperSU integrated ( http://forum.xda-developers.com/xperia-xz/development/rom-romaur-v1-0-fast-stable-t3486874 ) root works perfectly. Once custom ROM is installed, SuperSu icon is displayed and root access is OK.
I read that this problem might be because of incompatible kernel? I installed custom kernel (which was attached to RomAur - Stock_Kernel_f8331_fw.327-DRM FIX) before installing custom ROM, but I guess that re-flashing stock ROM later (using Flashtool) restored original kernel as well? If so, what exactly do I need to do in order to have rooted stock Nougat? Just flash some custom kernel (which one exactly?) and try flashing SuperSU again? Really don't want to brick anything.
P.S. Current kernel - 3.18.31-perf-g6af3ae9

if you are on stock nougat,
flash androplus kernel v18 from here:
https://kernel.andro.plus/tone2.html
after that,
flash supersu 2.78.

Thanks, will try. Is there any reason why using SuperSU 2.78 is needed? I see the latest one is 2.79?

manxp85 said:
Is there any reason why using SuperSU 2.78 is needed?
Click to expand...
Click to collapse
No - mine is running fine on 2.79SR1
BTW:
With stock kernel DM_Verity is ON
That detects any modification (e.g. installing SuperSU) in the non-USERDATA partitions via comparing signed checksums and if there is any modification found refuses to boot the device.

Well, my device boots perfectly, but SuperSu doesn't appear in apps list. Anyhow, I'll try with new kernel.
P.S. At the moment, phone runs androplus kernel v18 and custom ROM (Aura v4). After I will flash stock Nougat (using FTF file via Flashtool), will I need to re-flash androplus kernel v18 again?

manxp85 said:
Well, my device boots perfectly, but SuperSu doesn't appear in apps list. Anyhow, I'll try with new kernel.
P.S. At the moment, phone runs androplus kernel v18 and custom ROM (Aura v4). After I will flash stock Nougat (using FTF file via Flashtool), will I need to re-flash androplus kernel v18 again?
Click to expand...
Click to collapse
Welcome to the quirks of RomAur
It lasted less than a day on my device. I find the claims a bit overblown (did not notice them) and there were minor quirks/annoyances.
It needs time I suppose. But without the SONY sources auras76 can't do magic.
On my SAMSUNG G S5 I am on ResurrectionRom. THAT is an improvement over stock for me with LOTS of stuff I use and appreciate.
My Xperia XZ runs on stock ROM with AndroPlus Kernel v18 now. Do not forget to flash the Recovery too.
I am not sure if the SuperSU app is within the zip-file (80% positive it is). If not install it via Appstore.

Replaced RomAur with stock - works so much better. For some reason, root access on RomAur was lost every time after device was encrypted. No such problem with stock ROM.

[ROOT] [GUIDE] Root Moto G4 (Plus) with SuperSU on Android 7.0 (NPJ25.93-14)

Here are the steps to root the Moto G4 (Plus) on Android 7.0 with SuperSU.
1. Unlock your bootloader with the Code you can receive from Motorola. Further instructions: unlocking bootloader. You have to create a Motorola account first.
2. Flash TWRP 3.0.2.0 through bootloader. Download and how-to-flash: twrp athene
3. Backup partitons in TWRP (especially the boot-partition)
4. Flash Kernel ElementalX through TWRP. Download and further information: ElementalX
5. Wipe Cache and ART-Cache through TWRP (don't know if necessary but doesn't harm)
6. Flash SuperSU v2.79 SR3 through TWRP. Download SR3-SuperSU-v2.79-SR3-20170114223742.zip: SuperSUv2.79SR3.
SuperSU v2.79 SR3 (or newer) will flash as systemless by default on Motorola devices running Android 6+. Older versions of SuperSU won't do that without creating a config file .supersu in /data containing the line
Code:
SYSTEMLESS=true
So the best is to make sure you don't use an older version of SuperSU than 2.79 SR3!
That's it and it works. SuperSU.apk is going to be installed in step 6.
Successfully tested with XT1642, XT1622 (eta82), XT1643 (Adarsh balu), XT1644 (WTF?), XT1641 (EkisDeMX).

It's the same old guide man. Please see before posting if similar threads exist. XDA is getting confusing for the common non-techie person anyways.

Works perfect on Moto g4 (XT1622) :good:

I've tried to install SuperSU before and it didn't work on my device XT1640. I've got a bootloop and had to flash stock ROM (now I'm using another supersu). Does it really work now? Cuz I don't want to get a bootloop again and lose all my data.

Dex5er said:
I've tried to install SuperSU before and it didn't work on my device XT1640. I've got a bootloop and had to flash stock ROM (now I'm using another supersu). Does it really work now? Cuz I don't want to get a bootloop again and lose all my data.
Click to expand...
Click to collapse
You have to use SuperSU v2.79 SR3. If you use any older version, it won't install systemless and causes bootloops.
Which version of SuperSU did you flash?
And you have to flash ElementalX kernel before installing SuperSU. Otherwise you will get bootloop too.

tywinlannister7 said:
It's the same old guide man. Please see before posting if similar threads exist. XDA is getting confusing for the common non-techie person anyways.
Click to expand...
Click to collapse
Didn't find any thread which describes the method rooting with SuperSU in the first post and as its topic.
In some threads (with other topics like how to root with phh's SuperUser) there is in the discussion mentioned this method with SuperSU but nobody will ever find these posts...

disguisedview said:
You have to use SuperSU v2.79 SR3. If you use any older version, it won't install systemless and causes bootloops.
Which version of SuperSU did you flash?
And you have to flash ElementalX kernel before installing SuperSU. Otherwise you will get bootloop too.
Click to expand...
Click to collapse
I've installed ElementalX Kernel first then I installed SuperSU and I've got a bootloop. I used SuperSU v2.62 and got a bootloop, then I tried with SuperSU v2.74 and also got a bootloop.

Dex5er said:
I've installed ElementalX Kernel first then I installed SuperSU and I've got a bootloop. I used SuperSU v2.62 and got a bootloop, then I tried with SuperSU v2.74 and also got a bootloop.
Click to expand...
Click to collapse
Ok, seems to be the reason. You have to use version 2.79 SR3 or newer if available.
Otherwise it won't work without further modification...

disguisedview said:
Ok, seems to be the reason. You have to use version 2.79 SR3 or newer if available.
Otherwise it won't work without further modification...
Click to expand...
Click to collapse
Alright, is there any problem if I unroot my device with this supersu and root again with the SuperSU that you said, will I get any problem? Do I have to reinstall ElementalX Kernel and twrp again?

Dex5er said:
Alright, is there any problem if I unroot my device with this supersu and root again with the SuperSU that you said, will I get any problem? Do I have to reinstall ElementalX Kernel and twrp again?
Click to expand...
Click to collapse
I don't know. If you have backup of your partitions then flash your original system and boot partition and start from beginning (ElementalX and then SuperSU 2.79 SR3).
If you don't have backups then download (here on xda or somewhere else) stock firmware and flash system und boot partition.

I am currently using the resurrection remix ROM on my moto g4 plus....and my turbo charging is not working...is there anything that I can do to fix this

Asish.pradhan said:
I am currently using the resurrection remix ROM on my moto g4 plus....and my turbo charging is not working...is there anything that I can do to fix this
Click to expand...
Click to collapse
Is it really not working? Or it just doesn't show the popup "TurboPower connected"?

does it work on XT1643 Indian variant ?
---------- Post added at 04:44 PM ---------- Previous post was at 04:40 PM ----------
Asish.pradhan said:
I am currently using the resurrection remix ROM on my moto g4 plus....and my turbo charging is not working...is there anything that I can do to fix this
Click to expand...
Click to collapse
Turbo Power worked fine in my device when using the Ressuruction Rom. Probably restarting the device would solve the issue.

I checked the power input using ampere..its working fine..thnks every1

disguisedview said:
Here are the steps to root the Moto G4 (Plus) on Android 7.0 with SuperSU.
1. Unlock your bootloader with the Code you can receive from Motorola. Further instructions: unlocking bootloader. You have to create a Motorola account first.
2. Flash TWRP 3.0.2.0 through bootloader. Download and how-to-flash: twrp athene
3. Backup partitons in TWRP (especially the boot-partition)
4. Flash Kernel ElementalX through TWRP. Download and further information: ElementalX
5. Wipe Cache and ART-Cache through TWRP (don't know if necessary but doesn't harm)
6. Flash SuperSU v2.79 SR3 through TWRP. Download SR3-SuperSU-v2.79-SR3-20170114223742.zip: SuperSUv2.79SR3.
SuperSU v2.79 SR3 (or newer) will flash as systemless by default on Motorola devices running Android 6+. Older versions of SuperSU won't do that without creating a config file .supersu in /data containing the line
Code:
SYSTEMLESS=true
So the best is to make sure you don't use an older version of SuperSU than 2.79 SR3!
That's it and it works. SuperSU.apk is going to be installed in step 6.
Successfully tested with XT1642, XT1622 (eta82).
Click to expand...
Click to collapse
Does it work with XT1643 Indian variant ? Please do let me know .

arpith.pr said:
Here are the steps to root the Moto G4 (Plus) on Android 7.0 with SuperSU.
1. Unlock your bootloader with the Code you can receive from Motorola. Further instructions: unlocking bootloader. You have to create a Motorola account first.
2. Flash TWRP 3.0.2.0 through bootloader. Download and how-to-flash: twrp athene
3. Backup partitons in TWRP (especially the boot-partition)
4. Flash Kernel ElementalX through TWRP. Download and further information: ElementalX
5. Wipe Cache and ART-Cache through TWRP (don't know if necessary but doesn't harm)
6. Flash SuperSU v2.79 SR3 through TWRP. Download SR3-SuperSU-v2.79-SR3-20170114223742.zip: SuperSUv2.79SR3.
SuperSU v2.79 SR3 (or newer) will flash as systemless by default on Motorola devices running Android 6+. Older versions of SuperSU won't do that without creating a config file .supersu in /data containing the line
Does it work with XT1643 Indian variant ? Please do let me know .
Click to expand...
Click to collapse
Nobody confirmed it yet in this thread.
I could it only test with 1642.
But normally i would say it should also work on 1643 variant.

arpith.pr said:
Does it work with XT1643 Indian variant ? Please do let me know .
Click to expand...
Click to collapse
Yes it does work. It is the only way to root stock N on any of the models.

tywinlannister7 said:
Yes it does work. It is the only way to root stock N on any of the models.
Click to expand...
Click to collapse
Thanks

Working on XT1643....
Im making a video on how to do this to make it easier .... For others like me to understand

I can just Reboot to custom recovery, root and then still use my stock recovery?

Question Install official RUI updates from TWRP?

So, I rooted my phone, for which I needed to unlock the bootloader and install TWRP. Now, when I want to install an update on my phone, it downloads and when I want to install it, it jumps to TWRP recovery instead of the phone's recovery, so I can't update my phone. Does anyone know how can I install the updates from TWRP?
Else, reinstall the default recovery. (Only the recovery, not the entire OS since that would un-root my phone)
Thanks.
Edit: After it boots to TWRP, it apparently tries to install the update, since I can see it on the log, but when I reboot my phone it has not installed. It errors: "E3994: This package is for "2169B" devices; this is a "". Updater process ended with ERROR: 1. Error installing zip file '/data/ota_package/OTA/.otaPackage/my_manifest_RMX3370_11.F.04_3040_202302282047.44.36402b59_all.zip'
Edit 2: After failing to install it, it prompts me to re-download it and re-install it, but it jumped from ~500MB update to 4.76GB update.

( may loose data)
I read in telegram channels, this twrp: https://www.pling.com/p/1922292 support installation latest zip. but I haven't tried.
one more thing you can do is ( may loose data)
1. restore twrp backup for recovery partition ( if you don't have backup. search recovery.img in upgrade zip )
2. reboot to recovery to check stock recovery is installed
3. install update
4. then follow steps to install twrp and magisk ( root again )

SanOne+1 said:
( may loose data)
I read in telegram channels, this twrp: https://www.pling.com/p/1922292 support installation latest zip. but I haven't tried.
one more thing you can do is ( may loose data)
1. restore twrp backup for recovery partition ( if you don't have backup. search recovery.img in upgrade zip )
2. reboot to recovery to check stock recovery is installed
3. install update
4. then follow steps to install twrp and magisk ( root again )
Click to expand...
Click to collapse
Your guide is incorrect and will definitely put the device into bootloop.
** The twrp link that you shared doesn't allow system updates to install, it is just a A13 compatable twrp recovery.
1) What if that person has not created any twrp backup of all system partitions? According to his explanation, I'm pretty sure he has not created any backup of the partitions.
2) only flashing recovery image and installing the update will again put the device into bootloop because as confirmed by the OP that his device is rooted and due to root the boot image of the device gets modified so it will put the device into bootloop.
3) unless the OP has stock boot and recovery images at his disposal he should not attempt to install the update to avoid bootloop.
** Kindly avoid sharing incorrect information you aren't sure about the correct procedure.
procedure that I follow to flash updates :
1) in magisk - uninstall magisk - restore images
2) boot device into bootloader and flash stock boot and recovery.
3) boot device and install update.
4) put device again in bootloader and flash twrp and within twrp flash magisk and reboot.
I haven't found any easier way than this. If anyone has, kindly put it below.

There's a way
Rui 4.0 Android 13 f.02
So, any verdict on this new update for the people that did update to it?
forum.xda-developers.com

Recetly I succesfully updated my Realme GT Neo 2 5G via TWRP recovery, the latest version support OTA.
Attention! After update TWPR and Magisk gone. Just reflash twrp and flash magisk normally. No need to reflash modules etc. (Just update from settings, no need to manually flash ota package from TWRP)

Hello mate can u help me with something real quick. Y are there no recent updates for gt neo 2 and if u r using a custom rom based gt neo 2 hows ur experience so far. Thanks in advance
Xemi_KryTeT.pl said:
Recetly I succesfully updated my Realme GT Neo 2 5G via TWRP recovery, the latest version support OTA.
Attention! After update TWPR and Magisk gone. Just reflash twrp and flash magisk normally. No need to reflash modules etc. (Just update from settings, no need to manually flash ota package from TWRP)
Click to expand...
Click to collapse
Which rom r u running and is it good?

Sabirsayed09 said:
Hello mate can u help me with something real quick. Y are there no recent updates for gt neo 2 and if u r using a custom rom based gt neo 2 hows ur experience so far. Thanks in advance
Which rom r u running and is it good?
Click to expand...
Click to collapse
Latest stock (4.0), I'm not going to flash custom roms for now