Database Users

Retaining Root on 4.4

Well I flashed 4.4 successfully using TWRP. But some how or another I've unrooted myself. I've tried everything that I can (aside from messing with ADB and the SDK directly) and I can't figure out how to re-root the device.
Help!

Install TWRP again if it's gone and then flash SuperSU

tom1807 said:
Install TWRP again if it's gone and then flash SuperSU
Click to expand...
Click to collapse
No dice. Says I'm unrooted.
Managed to get it working. Koush's Superuser app doesn't work for some reason. SuperSU does. I just hope they fixed the glitches with it causing unnecessary battery drain.

What were your steps?
You can obtain the last flashable zip file from here
Ok, you edited your post, so my one is obsolete

SuperSU

I'm on a B09, bootloader unlocked and rooted with SuperSU 2.65 A2017G.
Except from the 2.65 version, is there another one working for the A2017G?
I want to get Xposed and if I do understand I need SuperSU 2.75 or above to get Xposed to work in systemless.
If there isn't another version could you guys help to get Xposed working on my phone?
That would be much appreciated.
EDIT: Well I'm dumb, I assumed Oki's guide only worked on the A2017U variant. Sorry guys :/

If you have the official version of TWRP you should be able to install the latest version of SuperSU.

Yeah I figured it out with the help of Oki's guide.
Thanks for the answer!

I'm having a problem where many apps do not get root unless I manually open SuperSU, which means that most root apps are not working properly because they can't work automatically. Is there another version of SuperSU or TWRP that I can flash to solve this problem?
I'm on A2017U B29 stock, SuperSU 2.79 flashed from TWRP 3.0.2-2

nuserame said:
I'm having a problem where many apps do not get root unless I manually open SuperSU, which means that most root apps are not working properly because they can't work automatically. Is there another version of SuperSU or TWRP that I can flash to solve this problem?
I'm on A2017U B29 stock, SuperSU 2.79 flashed from TWRP 3.0.2-2
Click to expand...
Click to collapse
Did you make sure to disable system write protection? Boot into TWRP, open up the terminal emulator, and issue the command: reboot disemmcwp

I'm having a similar problem while flashing superuser. The error happens after the "patching sepolicy" line runs. The error prevents SuperSU from being installed at all. Any suggestions?

You need to flash twrp 3.0.3 or above and flash SuperSU 2.79

Latest SuperSU Causes Endless Loops on the Axon 7
Literally, every time I install the latest version of SuperSU on my axon I get an endless bootloop. These are SuperSU files I get directly from chainfire's website. There must be something im missing, or maybe im downloading the wrong version? Im not sure i was hoping to get some help. I just tried installing: SR3-SuperSU-v2.79-SR3-20170114223742.
>> Can anyone point me in the right direction of the latest SuperSU that works with the Axon 7 that doesnt bootloop it.
I remember that the Pixel phones had SuperSUs that were made for it. I am wondering does the same thing apply here?
I have installed everything right on my phone to the T. Everything was brand new stock.
Kinanizer said:
If you have the official version of TWRP you should be able to install the latest version of SuperSU.
Click to expand...
Click to collapse

935F & Magisk

Hey,
I have an Exynos S7 Edge with G935FXXU1DQB3 (nougat) stock rom. It's unlocked, supersu 2.79 rooted systemless, and has TWRP.
I've been trying to install Magisk to no avail.
When I try to flash Magisk on top of supersu systemless, I get a "not enough space in the boot partition" error. If I flash the original boot image, flash phh's superuser, then I get no prompts for superuser requests for apps.
Another interesting thing, with phh's, magisk says the device is rooted, but no root access is authorized (Grey error box).
Regardless of this problem, if I flash magisk on top of phh's, then I end up with a boot loop.
In theory, magisk should work with systemless supersu.
Any ideas?

I think you need to install magisk first then install supersu or phh on top of it if you want.
Magisk have it's own root though if you don't know.
Sent from my SM-G935F using Tapatalk

I tried to flash magisk before all else, and still, bootloop.
I'm assuming this is an incompatibility with the stock rom and I just need to look into a custom rom.
Sent from my SM-G935F using XDA-Developers Legacy app

ScreAmeR01 said:
I tried to flash magisk before all else, and still, bootloop.
I'm assuming this is an incompatibility with the stock rom and I just need to look into a custom rom.
Click to expand...
Click to collapse
I am wondering could it be because stock rom has encryption enabled and custom roms dont perhaps?

simonbigwave said:
I am wondering could it be because stock rom has encryption enabled and custom roms dont perhaps?
Click to expand...
Click to collapse
I doubt that. A whole bunch of ROMs are encrypted, yet Magisk works on them. I'm thinking deoxed, but I can't be sure.
One thing I know is that I tried everything I could think of.
I'm going to try one of the super stock ROMs, and see how it goes. I'm weary though, people complain about WiFi issues, camera issues, mic issues... Don't know.
Sent from my SM-G935F using XDA-Developers Legacy app

NonXtreme said:
I think you need to install magisk first then install supersu or phh on top of it if you want.
Magisk have it's own root though if you don't know.
Click to expand...
Click to collapse
Noob question (I had a rooted S4 but new to G935F) , so if we install no need to root with Chainfires SuperSu then right? Then why flash SuperSu on top?

simonbigwave said:
Noob question (I had a rooted S4 but new to G935F) , so if we install no need to root with Chainfires SuperSu then right? Then why flash SuperSu on top?
Click to expand...
Click to collapse
Yes.
The reason why people flash supersu on top might be because of some compatibility issue that might rise from magiskSu since magisksu is still quite new but supersu have been exist for a long time.
I have never face any issue with magisksu though.
Sent from my SM-G935F using Tapatalk

Update: over the last 24 hours, I've been using SuperStock 2.5 ROM. I have to admit that I am pleasantly surprised. Here's a quick review, for those who might be interested:
1. I switched from stock. Flashed it dirty, meaning system partitions only. My data and apps were kept intact.
2. Aroma installer is cool, loved the options.
3. No camera issues, no Bluetooth issues, no WiFi issues, no mic issues. In fact, so far, no issues none whatsoever.
4. My accounts, WiFi passwords, and Bluetooth pairings were gone. I wasn't expecting that. I reversed back to my original stock (always back up), made titanium backups for those, switched back to the ROM, then restored them back.
5. Magisk and supersu is working fully. Android pay also works. I also installed Google assistant thru magisk. I'm loving it.
6. No xposed yet, since it's nougat. It sucks, but it's not the ROMs fault.
7. I did not flash the Bluetooth and modem. I like what I had, and I'm keeping them
8. I don't do GApps. I like the stock apps.
For those of you who are looking for a variety, I recommend SuperStock. I tried lineage, remix and a few others, SuperStock seems to fit me the most. Magisk is the obvious benefit, and battery seems to be the same as before.
Sent from my SM-G935F using XDA-Developers Legacy app

One more update: someone asked me about snapchat and Pokémon, whether they work. I have no idea, I'm too old for those things.
Sent from my SM-G935F using XDA-Developers Legacy app

ScreAmeR01 said:
One more update: someone asked me about snapchat and Pokémon, whether they work. I have no idea, I'm too old for those things.
Click to expand...
Click to collapse
i have also never ever used snapchat or pokemon .. lol.

Lost root after flashing 4.1.6, Please help.

Hi, Can someone please help, I must have done something wrong. Flashed official 4.1.6 update through twrp successfully, but lost root, tried to flash super su again (ver 2.86), but got stuck in boot, logo froze.
Flashed 4.1.6 again, phone works but no root still.
Is that a wrong super su version or did I do something else wrong?
Help will be really appreciated.
Regards

After flashing a full update you'll always have to reflash your root solution. I guess you mean SuperSU v2.82...
Use the official 2.82, found here (there's a link to the flashable zip). There's also a link to a version to try if you're experiencing bootloops.
You could also try the release candidate, found here.

Magisk all the way

1. Wipe data
2. Flash ROM
3. Flash root package, either SuperSU or Magisk
4. Reboot
I see no reason why wouldn't this work for you

Didgeridoohan said:
After flashing a full update you'll always have to reflash your root solution. I guess you mean SuperSU v2.82...
Use the official 2.82, found here (there's a link to the flashable zip). There's also a link to a version to try if you're experiencing bootloops.
You could also try the release candidate, found here.
Click to expand...
Click to collapse
Hi,
Many thanks.
Before proceeding, should the super su app also be removed from phone?
Regards

dua999 said:
Hi,
Many thanks.
Before proceeding, should the super su app also be removed from phone?
Regards
Click to expand...
Click to collapse
When you flash the rom it will already be uninstalled

sakumaxp said:
When you flash the rom it will already be uninstalled
Click to expand...
Click to collapse
I think, I was not able to explain, Rom is already there, but I just flashed 4.1.6 update, and root was gone.
Just wanna avoid all those data backup, restore, register all new banking apps etc, it time consuming and painful.
I am pretty sure, root can be restored, when I have an unlocked bootloader, twrp recovery working properly.
SuperSU is still there in apps but can't open as says, root not available. However, can uninstall this if that is required.
Cheers

dua999 said:
I think, I was not able to explain, Rom is already there, but I just flashed 4.1.6 update, and root was gone.
Just wanna avoid all those data backup, restore, register all new banking apps etc, it time consuming and painful.
I am pretty sure, root can be restored, when I have an unlocked bootloader, twrp recovery working properly.
SuperSU is still there in apps but can't open as says, root not available. However, can uninstall this if that is required.
Cheers
Click to expand...
Click to collapse
You can try to uninstall it through supersu app but make sure to keep you boot img. Then your phone will be fully unrooted, go into twrp and reflash supersu/magisk

sakumaxp said:
You can try to uninstall it through supersu app but make sure to keep you boot img. Then your phone will be fully unrooted, go into twrp and reflash supersu/magisk
Click to expand...
Click to collapse
Thanks all for help, all sorted

[Q] Successful rooted, but /system is read only?

Hi guys, I have successfully rooted using temporary TWRP + modded magisk method, but now I gain root and checked via Root checker. But the problem is most of the root functions don't work as /system is read-only. Any idea?

Ya i have an idea.. Happened to me as well. I tried almoat everything but system won't be accessible anywhere.. I followed the same tutorial and installed magisk 13.4.
The only solution i could find was flash the latest factory image, and root again using supersu. I used the AIO tool by ghpranav and have got my phone rooted with xposed working without any issues.

zazzy24 said:
Ya i have an idea.. Happened to me as well. I tried almoat everything but system won't be accessible anywhere.. I followed the same tutorial and installed magisk 13.4.
The only solution i could find was flash the latest factory image, and root again using supersu. I used the AIO tool by ghpranav and have got my phone rooted with xposed working without any issues.
Click to expand...
Click to collapse
I also fixed the issue. I flash the modified boot image and I am now gaining proper root access + Xposed. Get it working using Super SU, idk why Magisk keep failing thou. Was wanted to give Magisk a try, but it doesn't work properly on our device.

Cool:good:

Xposed isn't working with magisk? I was planning to install it

amithiel said:
Xposed isn't working with magisk? I was planning to install it
Click to expand...
Click to collapse
Only with SuperSU as I know.
Sent from my Mi A1 using Tapatalk

Guys, this is Magisk from Pixel. You can't expect that it is working. I wrote to MagiskDevs already, they are working on a own Version for Mi A1. Use for that time normal SuperSU (Xposed works normally )

how to??
soralz said:
I also fixed the issue. I flash the modified boot image and I am now gaining proper root access + Xposed. Get it working using Super SU, idk why Magisk keep failing thou. Was wanted to give Magisk a try, but it doesn't work properly on our device.
Click to expand...
Click to collapse
Hay how do you Fix the Read only Issue? can you please share the Modified Boot image and process for same, thanks

maxsan20 said:
Hay how do you Fix the Read only Issue? can you please share the Modified Boot image and process for same, thanks
Click to expand...
Click to collapse
https://desktop.firmware.mobi/device:1748
Just root with replacing the boot image then you are good to go.

soralz said:
https://desktop.firmware.mobi/device:1748
Just root with replacing the boot image then you are good to go.
Click to expand...
Click to collapse
Hi,
I have TWRP installed and unrooted, what I need to do please?

We7dy said:
Hi,
I have TWRP installed and unrooted, what I need to do please?
Click to expand...
Click to collapse
You need flash back stock boot image first, due to some limitations you can't have TWRP and SuperSU root at the same time. If you don't have the stock boot image. I suggest download the ROM from MIUI and then flash it. You can choose "flash_all_except_storage" option, this will keep your data.
http://en.miui.com/download-333.html
After flashing. Reboot back to fastboot and then:
Code:
fastboot oem unlock
After that just run root.bat from the cf-auto root folder you downloaded and wait for it to automatically reboot your phone. You should have root now, if you wish you can download SuperSU from the store.

soralz said:
You need flash back stock boot image first, due to some limitations you can't have TWRP and SuperSU root at the same time. If you don't have the stock boot image. I suggest download the ROM from MIUI and then flash it. You can choose "flash_all_except_storage" option, this will keep your data.
http://en.miui.com/download-333.html
After flashing. Reboot back to fastboot and then:
After that just run root.bat from the cf-auto root folder you downloaded and wait for it to automatically reboot your phone. You should have root now, if you wish you can download SuperSU from the store.
Click to expand...
Click to collapse
Ok, thanks. It's not possible to do that via TWRP? I don't have PC. Currently my bootloader is unlocked, I have TWRP and I'm unrooted.

We7dy said:
Ok, thanks. It's not possible to do that via TWRP? I don't have PC. Currently my bootloader is unlocked, I have TWRP and I'm unrooted.
Click to expand...
Click to collapse
I actually tried before, and I tell you the results:
Option 1 TWRP installed + Rooted with Magisk
= Pretty much useless as /system is read-only. Every root app doesn't function, unless it is system-less. But system-less modules nearly all doesn't work as the Magisk version too old. And this method won't trip safetynet
Option 2 no TWRP + Rooted with SuperSU (cf-root method) -- Currently using this state
= Got proper root access, Xposed works but will trip safetynet
Option 3 TWRP installed + Rooted with SuperSU (cf-root method)
= Don't try this, will cause your phone stuck in boot loop

soralz said:
I actually tried before, and I tell you the results:
Option 1 TWRP installed + Rooted with Magisk
= Pretty much useless as /system is read-only. Every root app doesn't function, unless it is system-less. But system-less modules nearly all doesn't work as the Magisk version too old. And this method won't trip safetynet
Option 2 no TWRP + Rooted with SuperSU (cf-root method) -- Currently using this state
= Got proper root access, Xposed works but will trip safetynet
Option 3 TWRP installed + Rooted with SuperSU (cf-root method)
= Don't try this, will cause your phone stuck in boot loop
Click to expand...
Click to collapse
So not possible via TWRP? Get root access and remove TWRP? I just need that... The root.

We7dy said:
So not possible via TWRP? Get root access and remove TWRP? I just need that... The root.
Click to expand...
Click to collapse
The best bet and possible trouble free is to first download the stock ROM from MIUI, reflash it and then root.

soralz said:
The best bet and possible trouble free is to first download the stock ROM from MIUI, reflash it and then root.
Click to expand...
Click to collapse
:/ Can't root with TWRP without system read only...

We7dy said:
:/ Can't root with TWRP without system read only...
Click to expand...
Click to collapse
It's possible to root without CF-Auto-Root? Why can't flash SuperSu directly with TWRP?

We7dy said:
It's possible to root without CF-Auto-Root? Why can't flash SuperSu directly with TWRP?
Click to expand...
Click to collapse
No, it will cause your phone stuck it boot loop if you try to flash the SuperSU zip directly from the official ChainFire site. I think probably is the AB partitioning problem or some sort (unsure). As I said you need to run CF-Auto root to get proper root access, otherwise flashing Magisk through TWRP will makes most of the root apps does not work properly unless it also uses system-less root function.

soralz said:
No, it will cause your phone stuck it boot loop if you try to flash the SuperSU zip directly from the official ChainFire site. I think probably is the AB partitioning problem or some sort (unsure). As I said you need to run CF-Auto root to get proper root access, otherwise flashing Magisk through TWRP will makes most of the root apps does not work properly unless it also uses system-less root function.
Click to expand...
Click to collapse
Ok I have TWRP installed can I use directly CF auto root?

We7dy said:
Ok I have TWRP installed can I use directly CF auto root?
Click to expand...
Click to collapse
No if you want proper root with CF-auto root you must not have TWRP installed. You either choose TWRP + Magisk (non-working root) or no TWRP but with SuperSU (working root, Xposed works too).
Follow the instruction here to get you on track:
https://forum.xda-developers.com/showpost.php?p=74326169&postcount=2