I have installed CM 12.1 and I have no Supersu :( - Fire Q&A, Help & Troubleshooting

I'm in a pickle, I flash CM 12.1 with arm gapps pico using Flashfire 0.27. It booted up fine! But I noticed I have no gapps installed, I opened up flashfire to try to install gapps again, it said it need a rooted device. I don't know what to do!????

shawnsac2000 said:
I'm in a pickle, I flash CM 12.1 with arm gapps pico using Flashfire 0.27. It booted up fine! But I noticed I have no gapps installed, I opened up flashfire to try to install gapps again, it said it need a rooted device. I don't know what to do!????
Click to expand...
Click to collapse
CM12 has root built in, you just have to enable it in developer options or flash supersu

Thanks

wulfie66 said:
CM12 has root built in, you just have to enable it in developer options or flash supersu
Click to expand...
Click to collapse
I activated it but SuperSU is still unable to update it's binaries and titanium backup can't get access either.
What am I missing?
EDIT: Reboot did the trick

once its activated for ADB and Apps restart your tablet. You must restart. You dont need supersu when using cyanogonmod. Once your device is restarted open up flashfire, it should ask for root permission, then just click grant and you are good to go.

Related

Lg G3 (D855) CM13 Supersu

Hello Chainfire,
I have smartphone LG G3 32GB (D855), as custom rom I just installed the CM13. I tried to flash through recovery TWRP SuperSU-v2.62-3-20151211162651.zip, but when I restarted the device went into boot loop.
Can you tell me if I should try another version, or you have to wait ??
I have the same question
...
Currently the replacement kernel needs to be bumped (searching the beta thread will give you the instructions for this). I may have a different (easier) solution in a few days, though.
Chainfire said:
Currently the replacement kernel needs to be bumped (searching the beta thread will give you the instructions for this). I may have a different (easier) solution in a few days, though.
Click to expand...
Click to collapse
Same problem here with my ONEPLUS One... Updated to the latest CM 13.0 nightly everything was perfect. Installed SuperSU "UPDATE -SuperSU v2.46. System hang at the Android character during logon. I have reloaded the CM13.0 and Gapps, reflashed those two to restore system operation. Found SU v2.62-3 I'll hold off on flashing that SuperSU until a ".. different (easier) solution..." is available. Thanks Chainfire!!!
Happy to wait!
Sent from my LG G3 running cm 12.1
Same problem...
There are news? :crying:
Boot Error
@Chainfire
I've also got an Boot Error after flashing SuperSU 2.65 on my D855 using CandySIX with the 777Kernel for MM. I'l try it now with 2.52 and 2.63-3 maybe it works with them.
SkyDriver11 said:
@Chainfire
I've also got an Boot Error after flashing SuperSU 2.65 on my D855 using CandySIX with the 777Kernel for MM. I'l try it now with 2.52 and 2.63-3 maybe it works with them.
Click to expand...
Click to collapse
well! have you a news about this way?
ps. happy new year to everybody!!
Use SuperSU 2.52
Drago76 said:
well! have you a news about this way?
ps. happy new year to everybody!!
Click to expand...
Click to collapse
Yeah i've got it running with root access and also permissions to /system
Just use the SuperSU 2.52. What i think is that SuperSU 2.52 doesn't patches the boot.img. And thats the point of why 2.52 works.
Our LG G3 hates it when somebody touches the boot.img
SkyDriver11 said:
Yeah i've got it running with root access and also permissions to /system
Just use the SuperSU 2.52. What i think is that SuperSU 2.52 doesn't patches the boot.img. And thats the point of why 2.52 works.
Our LG G3 hates it when somebody touches the boot.img
Click to expand...
Click to collapse
I've tried to flash SuperSU 2.52 but the phone go to loop on the cm animation boot.. :crying:
CM12 & CM13 based roms don't need SuperSU. The su support is built into CyanogenMod. You have to enable developer options and find the included root under developer options.
gimli4711 said:
CM12 & CM13 based roms don't need SuperSU. The su support is built into CyanogenMod. You have to enable developer options and find the included root under developer options.
Click to expand...
Click to collapse
Everyone knows this, thanks..
the problem is that with cm13 root, some apps like Leandroid doesn't work, cause it wants only supersu.
for example, my friend with Nexus 5 cm13, has installed supersu 2.62 and he enjoys Leandroid perfectly.
nothing? :crying:
The way I got SuperSU to work on my phone was to use the SharpeningMod zip, which bumps the sytem img back for you. Just tried it on latest Cyanogenmod nightly and BETA-SuperSU-v2.66.zip.
Download the mod from http://forum.xda-developers.com/lg-g3/orig-development/fix-sharpening-mod-script-1-0-beta-t2957648
Latest version is 3.5
Boot into TWRP perform a back up of your curent system just incase,
flash the latest supersu zip then flash the sharpening modzip, I selected disabled in the list and then let it do its thing.
Rebooted and Cyanogen booted with no loops.
Hope this helps anyone who wants an easy way to install.
great solution!!! it's wonderful!!!
thanks!!
Inviato dal mio LG-D855 utilizzando Tapatalk
superSU 2.66 beta on lg g2 d802...
stoneblade said:
The way I got SuperSU to work on my phone was to use the SharpeningMod zip, which bumps the sytem img back for you. Just tried it on latest Cyanogenmod nightly and BETA-SuperSU-v2.66.zip.
Download the mod from http://forum.xda-developers.com/lg-g3/orig-development/fix-sharpening-mod-script-1-0-beta-t2957648
Latest version is 3.5
Boot into TWRP perform a back up of your curent system just incase,
flash the latest supersu zip then flash the sharpening modzip, I selected disabled in the list and then let it do its thing.
Rebooted and Cyanogen booted with no loops.
Hope this helps anyone who wants an easy way to install.
Click to expand...
Click to collapse
it worked perfectly on lg g2 d802 ...no bootloops !thanks a lot
stoneblade said:
The way I got SuperSU to work on my phone was to use the SharpeningMod zip, which bumps the sytem img back for you. Just tried it on latest Cyanogenmod nightly and BETA-SuperSU-v2.66.zip.
Download the mod from http://forum.xda-developers.com/lg-g3/orig-development/fix-sharpening-mod-script-1-0-beta-t2957648
Latest version is 3.5
Boot into TWRP perform a back up of your curent system just incase,
flash the latest supersu zip then flash the sharpening modzip, I selected disabled in the list and then let it do its thing.
Rebooted and Cyanogen booted with no loops.
Hope this helps anyone who wants an easy way to install.
Click to expand...
Click to collapse
Awesome!!! That was so painless...lol. Thank You! NOTE: I downloaded and installed a nightly update afterwards and ran into binary update problem again. I simply opened SuperSu settings, hit the cleanup option for new install, reboot to recovery, repeated flash of both and all went smooth. I now have SuperSu 2.62 on CM 13 NIGHTLY 01-19-16. Thanks again :cyclops:
jhtrades1 said:
Awesome!!! That was so painless...lol. Thank You! NOTE: I downloaded and installed a nightly update afterwards and ran into binary update problem again. I simply opened SuperSu settings, hit the cleanup option for new install, reboot to recovery, repeated flash of both and all went smooth. I now have SuperSu 2.62 on CM 13 NIGHTLY 01-19-16. Thanks again :cyclops:
Click to expand...
Click to collapse
You also can manually install update from TWRP, after than reinstall xposed Framework (if have it), supersu 2.66 and last reinstall "Sharpening-Mod-3.5".. now reboot.
enjoy!
Inviato dal mio LG-D855 utilizzando Tapatalk
stoneblade said:
The way I got SuperSU to work on my phone was to use the SharpeningMod zip, which bumps the sytem img back for you. Just tried it on latest Cyanogenmod nightly and BETA-SuperSU-v2.66.zip.
Download the mod from http://forum.xda-developers.com/lg-g3/orig-development/fix-sharpening-mod-script-1-0-beta-t2957648
Latest version is 3.5
Boot into TWRP perform a back up of your curent system just incase,
flash the latest supersu zip then flash the sharpening modzip, I selected disabled in the list and then let it do its thing.
Rebooted and Cyanogen booted with no loops.
Hope this helps anyone who wants an easy way to install.
Click to expand...
Click to collapse
It works thanks for this nice solution
stoneblade said:
The way I got SuperSU to work on my phone was to use the SharpeningMod zip, which bumps the sytem img back for you. Just tried it on latest Cyanogenmod nightly and BETA-SuperSU-v2.66.zip.
Download the mod from http://forum.xda-developers.com/lg-g3/orig-development/fix-sharpening-mod-script-1-0-beta-t2957648
Latest version is 3.5
Boot into TWRP perform a back up of your curent system just incase,
flash the latest supersu zip then flash the sharpening modzip, I selected disabled in the list and then let it do its thing.
Rebooted and Cyanogen booted with no loops.
Hope this helps anyone who wants an easy way to install.
Click to expand...
Click to collapse
It works on my LG G3 D855! Thank you! :victory::highfive:

Super SU on CM

I am running cm 13 on moto g 2. I installed the SuperSU app but it is unable to install the binary or update. I need the app can someone tell me how to get SuperSU on my phone that actually works step by step.
P.s. I know that cm has root facility through dev options but I still need the SuperSU functionality. So pls tell me how to go about it.
Search for the latest official zip and flash through recovery.
Make sure to uninstall the current one to avoid conflicts.
But...
So u mean that to install SuperSU I just need to flash zip and be over with it.
Also do I need to disble the root that is preinstalled in cm 13 throughdev options?
gauravmehta1998 said:
So u mean that to install SuperSU I just need to flash zip and be over with it.
Also do I need to disble the root that is preinstalled in cm 13 throughdev options?
Click to expand...
Click to collapse
Yes you need to flash this zip : Click Here
You need to diable the cm root in settings.
Remeber to flash the zip again after the update via twrp.
sagar846 said:
Remeber to flash the zip again after the update via twrp.
Click to expand...
Click to collapse
Or you can install the survival script in supersu settings

SuperSU & CM13

Is it actually possible to make SuperSU work on CM13 without bricking your device etc?
I have spent the last 2 days googling this and reading various (mostly old, outdated) posts about how it's a bad idea or maybe not, but they are typically from 2.5x or 2.6x or earlier SuperSU versions.
My tablet, the only actively developed non-stock rom available for it is CM13. That is literally it.
However, I would like to have SuperSU features, especially compatibility with SUhide etc.
So, I am wondering if it's possible?
Do the current (2.78+) SuperSU versions play nice with CM13?
Can I just flash it in from the SuperSU app (I have bought pro version if that matters)? or Flashfire? or from TWRP recovery, whichever way is best? And, do I need to do anything else first?
Wellll, I went ahead and did it. Happy to report everything's working fine. So that's that.
DryEagle said:
Wellll, I went ahead and did it. Happy to report everything's working fine. So that's that.
Click to expand...
Click to collapse
Wanna share how you did it ?
. . . I'm running the latest CyanogenMod 13 om my GT-N5100 ( Samsung galaxy note 8 ) and can't get i to work without bricking the device.
Warlock_SVG said:
Wanna share how you did it ?
. . . I'm running the latest CyanogenMod 13 om my GT-N5100 ( Samsung galaxy note 8 ) and can't get i to work without bricking the device.
Click to expand...
Click to collapse
Well, I downloaded the latest supersu zip (2.78), installed the supersu app from market, installed supersu pro from market (i already bought this long ago), then used flashfire to flash the zip. and it just worked. i'm using latest cm13 nightly on nvidia shield.
Got it working I downloaded "BETA-SuperSU-v2.77-20160827190633.zip" and Installed it in TWRP, systemless mode.
Warlock_SVG said:
Got it working I downloaded "BETA-SuperSU-v2.77-20160827190633.zip" and Installed it in TWRP, systemless mode.
Click to expand...
Click to collapse
you can download 2.78 zip here: https://download.chainfire.eu/1001/SuperSU/UPDATE-SuperSU-v2.78-20160905010000.zip the 2.76 or 2.77 had some problem, dont remember which one, but 2.78 is completely solid
How do I install SuperSU in "systemless mode"? I have a google nexus 10 running the latest CM13 Release + gapps.
[Lemmy] said:
How do I install SuperSU in "systemless mode"? I have a google nexus 10 running the latest CM13 Release + gapps.
Click to expand...
Click to collapse
I used supersu-v2.78-201609011115 for my CM13 devices http://forum.supersu.com/topic/152/supersu-v2-78-release/2 the installer decide if it needs to be installed in "systemless mode" so no need to worry about that
You might need to install the SupperSU app from the store yourself.
Warlock_SVG said:
I used supersu-v2.78-201609011115 for my CM13 devices http://forum.supersu.com/topic/152/supersu-v2-78-release/2 the installer decide if it needs to be installed in "systemless mode" so no need to worry about that
You might need to install the SupperSU app from the store yourself.
Click to expand...
Click to collapse
does that work with the "official cyanogen recovery" as well, or should I install TWRP first?
...ok with the cyanogen recovery it did _not_ work, the installer said something about "patching sepolicy failed".
Any other suggestions?
[Lemmy said:
;68885779]does that work with the "official cyanogen recovery" as well, or should I install TWRP first?
...ok with the cyanogen recovery it did _not_ work, the installer said something about "patching sepolicy failed".
Any other suggestions?
Click to expand...
Click to collapse
Install twrp.
Spent my 6 hours in trying this crap.....after installation, my phone doesn't reboot rather says "secure boot error" installed cm13 6 times and faced the same problem.....now I won't install it unless I get a tested and confirmed procedure
Will follow-up with you on the next post...
ALI EHTISHAM BUKHARI said:
Spent my 6 hours in trying this crap.....after installation, my phone doesn't reboot rather says "secure boot error" installed cm13 6 times and faced the same problem.....now I won't install it unless I get a tested and confirmed procedure
Click to expand...
Click to collapse
Here's what I do to get my S3 going...
With the latest TWRP as always since running into issues with flashing when i had CWM quite some time ago.
There are 3 files i place in my external MicroSD...
CM13, Open Gaaps for Android 6 (i use the pico) and the SuperSU 2.78 SR1 zip file directly from the official website (though 2.76 should work).
First, when in TWRP, select wipe then advanced then the top 5 selections leaving the bottom 2 alone. When completed, hit the bottom center home selection to go into the main menu. Again, select wipe then select the data option to the right of the advanced tab you were in before. It requires you to type yes then proceed. Once that is done, go back to the main menu and be sure you do this exactly! Select the reboot and then recovery. Once your back into the TWRP recovery then select install and go to the MicroSD card with the 3 files... Now select the order of files to flash beginning with CM13 then add zip then the GApps then add zip then the SuperSU then begin the flash process. Be sure to wipe the dalvik cache then reboot the system.
SuperSU reboots it again shortly afterwards as part of its installation process.
Once your all done setting up the initial system setup you should go directly to the SuperSU app to set up what you need to.
Though my personal procedure is a bit more involved, this is as basic as it gets.
For your specific system, i can't say that i have ever even used it so please pardon me deeply if I left anything out and if someone can chime in with anything else, I'm sure it would be much appreciated.
Good luck.

[GUIDE] [How To] Play Pokemon Go with Superuser (Root enabled)

How To Play Pokemon Go with Superuser (Root enabled)​
Note:
IT MIGHT CAUSE BOOTLOOP OR MIGHT BRICK YOUR DEVICE. MAKE SURE YOU HAVE A BACKUP.
Requirement:
Fresh Installation of Rom or Dirty Flash of your current rom (I tested it on CM and RR- Fresh.It might work on other custom roms.)
TWRP Recovery
Magisk: http://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
unSU Script : http://forum.xda-developers.com/attachment.php?attachmentid=3931994&d=1478779893
Steps:
1. Reboot into Recovery
2. Flash unSU Script and Magisk in order.
3. Reboot into System. (Mobile should boot without bootloop, otherwise you have to reinstall the ROM and try again)
4. Install Phh Superuser from here: https://play.google.com/store/apps/details?id=me.phh.superuser&hl=en.
4. Open Magisk Manager ( Update it,if it is asked) and it will ask you for SU permission. Allow it.
6. Go to Settings and Tick " Enable Magisk Hide " and Reboot your phone.
7. Once again Magisk Manager and it will show status of SafetyNet at 3rd row and It should Passed.
Install PokemonGo and Enjoy
Credits:
@topjohnwu
@phhusson
@Hw4ng3r
@Tikerz
Updates:
8/1/17
Updated the steps with New Magsik version 10.2
I did a clan flash. Booted and let everything settle. The rebooted into TWRP recovery. Mounted system, and deleted (or renamed) the Su files from system/bin and system/xbin. This removes root but I can play Pokémon.
Jowhee said:
I did a clan flash. Booted and let everything settle. The rebooted into TWRP recovery. Mounted system, and deleted (or renamed) the Su files from system/bin and system/xbin. This removes root but I can play Pokémon.
Click to expand...
Click to collapse
This guide is for keeping root AND passing SafetyNet.
BTW, this method also works on CM13 and OOS.
It didn't mention keeping root in the title.
Jowhee said:
It didn't mention keeping root in the title.
Click to expand...
Click to collapse
Sorry for the confusion.
Updated the thread.
SafetyNet Helper fails after following the steps:
SafetyNet request: success
Response Validation: success
CTS profile match: failure
Click to expand...
Click to collapse
Do we need to go back into fastboot and disabled the bootloader unlock?
nphillips said:
SafetyNet Helper fails after following the steps:
Do we need to go back into fastboot and disabled the bootloader unlock?
Click to expand...
Click to collapse
Not necessarily. Some kernels such as blu_kernel bypass the bootloader check. Try it out.
svprm said:
How To Play Pokemon Go with Superuser (Root enabled)​
Click to expand...
Click to collapse
can Xposed work along with PoGo ?
samnaction said:
can Xposed work along with PoGo ?
Click to expand...
Click to collapse
I'm not sure. I didn't test it.
But you can install the Xposed Framework module through Magisk Manager.
In CM builds you don't need all this you just need this simple app:
http://forum.xda-developers.com/android/apps-games/isu-simple-app-to-deactivate-activate-t3478348
I'm gonna assume this doesn't work with CM12.1 right?
Yepi69 said:
I'm gonna assume this doesn't work with CM12.1 right?
Click to expand...
Click to collapse
I didn't try.
But you can try and post the result here that would help others.
I followed the steps in the first post and everything went OK. I'm using oxygen Os nougat 0.9
Thanks for your tutorial.
Does this mean that CM14.1 passes safetynet now? I don't exactly need root but when I tried it a few weeks ago PKMN Go told me that the OS I had was not supported.
rdar_93 said:
Does this mean that CM14.1 passes safetynet now? I don't exactly need root but when I tried it a few weeks ago PKMN Go told me that the OS I had was not supported.
Click to expand...
Click to collapse
Yes, cm 14.1 could pass safety net with this.
This works for sure. But if you're running a secondary ROM using MultiROM the modified boot.img will cause safetynet to indeed fail. I hope they do bring an update soon to fix this though.
Daft question, but i'm unable to use an online banking app, due to being rooted. I know this relates to PokemonGo, but wondering if this could fool the banking app?
I am using H2OS beta (Nougat) and I followed the below steps, but safety net is failing.
1. Dirty flash current ROM
2. Flash UnSU.zip
3. Flash magisk and phh zips
4. Reboot
5. Install Magisk Manager and Phh superuser
6. check safety net
Is there anything which I'm doing wrong? Can you help me please. Thank you
Edit: A reboot and everything worked fine. Thank you so much
Sorry to disturb this thread, but I am a bit confused because the official Magisk thread nowhere mentions that phh's su would be the only working su solution:
topjohnwu said:
If you're using Magisk v7+ with Magisk version of phh's superuser , or rooted with Official Systemless SuperSU (Android 6.0+ only)
If you choose to use SuperSU (only support Android 6.0+)
Click to expand...
Click to collapse
So I am really wondering about your step 2 ...
svprm said:
2. Flash unSU Script, Magisk and phh's SuperUser Magisk.
Click to expand...
Click to collapse
pathologo said:
Sorry to disturb this thread, but I am a bit confused because the official Magisk thread nowhere mentions that phh's su would be the only working su solution:
So I am really wondering about your step 2 ...
Click to expand...
Click to collapse
Actually i didn't try with SuperSu.So i mentioned phh's SU.
It might work with SuperSu too.

After installing magisk, root not working

After installing the magisk as I was rooted, I installed 2-3 mods ie flashed in twrp but after I rebooted my root is gone. Magisk manager is showing not rooted and when I re flashed supersu in twrp, installation was successful but still no root. What happened I don't know. Also I didn't install any phh supersu or busybox. Please help me regain my root.
HELP
It was a known bug in Magisk that you would lose root.
Magisk
v10.2
- [Magic Mount] Remove apps/priv-app from whitelist, should fix all crashes
- [phh] Fix binary out-of-date issue
- [scripts] Fix root disappear issue when upgrading within Magisk Manager
Click to expand...
Click to collapse
So i'd make sure you flashed the latest version ? Pretty sure you have but if not might be worth flashing supersu then magisk over it again as it should recognise supersu and not modify it.
brichardson1991 said:
It was a known bug in Magisk that you would lose root.
So i'd make sure you flashed the latest version ? Pretty sure you have but if not might be worth flashing supersu then magisk over it again as it should recognise supersu and not modify it.
Click to expand...
Click to collapse
Yeah I just installed the latest version 10.2 via play Store. Help me regain my root
Vaibhunk786 said:
Yeah I just installed the latest version 10.2 via play Store. Help me regain my root
Click to expand...
Click to collapse
After installing from play store, did you "FLASH" magisk ?
brichardson1991 said:
After installing from play store, did you "FLASH" magisk ?
Click to expand...
Click to collapse
No I didn't flash anything. It was an automatic process which installed magisk and prompted me that installation success and reboot. Then I rebooted and root was gone
Now should I run magisk unstaller zip in twrp followed by supersu and then again flash magisk v10. 2 via twrp.. Should I follow these steps to gain my root again.. Anyone please help. I'm stuck @brichardson1991
Try installing PHH superuser from play store.
I had a similar experience. Having to reflash stock now to try a different tact. I'd rather use SuperSU to be honest, rather than PHH superuser.
Same problem here, have to investigate whats going on.
MattBooth said:
I had a similar experience. Having to reflash stock now to try a different tact. I'd rather use SuperSU to be honest, rather than PHH superuser.
Click to expand...
Click to collapse
yeah flashing the stock rom was the only viable option i think .
I have the same problem with latest magisk. After i installed mods root is gone and i can not root again. Only with supersu i have root. Magisk is very bugy.
Yeah it does appear the latest version now causes you to lose supersu
Same problem with me, on the OP3 running Open Beta 11. Reflashing SuperSU did not work. Rather than extract the boot.img to reflash that, I ended up reflashing the firmware (and ended up mistakenly using the 4.0.1 file instead of the OPB11 one!) ... Yet to try SuperSU and Magisk again on this, but figured better to investigate the issue before I attempt to reinstall.
From what I understand here, v10 won't have this problem, and its only on v11 that its cropped up again? Can anybody with v10 confirm this?

Categories

Resources