I've got a H870 from Israel with locked bootloader that isn't going to be unlocked (thanks for nothing, LG).
Now I've downgraded it from Pie to Oreo, as the Oreo kernel is vulnerable to CVE-2019-2215; thanks to https://repo.or.cz/cve2019-2215-3.18.git I've got a working su binary that sets SElinux to permissive and gives me a root shell.
I'm looking for a way to integrate this with one of the usual root apps (ideally Magisk), but I'm somewhat at a loss as to how these do their magic, especially in a way that doesn't involve messing with /system (which cannot be mounted r/w and comes from a ramdisk anyway (as far as I understand it).
Does anybody have experience with this? Can Magisk do a systemless install, and can its su be substituted by my own su?
Thanks for any input
Related
I have been reading through previous threads but I cannot find anything that specifically answers the question I have.
I had stock Android 4.2.1 (which was rooted) and now that it has updated to version 4.2.2 I am unrooted (even though upon boot it still displays the unlocked padlock but I assume that is something different).
So my question is, is it possible to root my current stock 4.2.2 and keep all of my apps and data? or is the only solution to wipe it all and start again if I want root access?
As a side note and to anyone who is reading this if you are currently rooted install this https://play.google.com/store/apps/details?id=org.projectvoodoo.otarootkeeper&hl=en and hopefully that should be the end of having to worry about losing root but in hindsight it is obviously to late for myself.
Thank you very much to anyone who can help me!
You didn't read enough threads.
The bootloader has been replaced, but is still unlocked.
The OTA also overwrote your custom recovery with a new stock recovery, but that's only a temporary issue - read on.
Because the new bootloader is also unlocked, that means that you can re-install a custom recovery just the same way you did it originally (with fastboot or a toolkit which also uses fastboot), but without the unlocking step (which wipes everything).
After you have a custom recovery in place you are free to do whatever you want - you could just reinstall a minimal SuperSU/Superuser overflash. This leaves everything unmolested, and you have root back.
Note that the superuser software is still on your tab; it has been temporarily disabled because the 'su' binary got its' permissions reset by the OTA install. Without doing a new over flash you could simply perform (with the custom recovery booted)
adb shell mount /system
adb shell chmod 6755 /system/xbin/su /system/bin/su
adb shell ls -l /system/xbin/su /system/bin/su
(it's one or the other of those locations depending on whether you are using SuperSU or Superuser; in any event you should see "swxs-xr-x" if you have the correct setuid/setgid permissions set)
good luck
The unlocked padlock means you're bootloader is unlocked, which is fine.
Yes it is possible, I suggest reading the stickies which explain how to do this. Basically, you'll need to flash a custom recovery via fastboot, then download a SuperSU flashable zip file (or Superuser) to flash in the custom recovery, and that's all.
Beaten by bftb0.
Thank you both very much for your responses!
I feel like I can not ever find systemless root properly.
I recently reflashed the stock march security update factory image. I then reinstalled TWRP 3.0 and then flashed "BETA-SuperSU-v2.68-20160228150503.zip" found int eh thread below
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
however when i booted, I wasnt systemless I was full root with the SU app and everything. i was able to unroot and now android pay works.
i would like to install SYSTMLESS ROOT what ever the latest is so that i can remove the XBIN folder and use the CHMOD trick to get androidpay working but I just cant seem to find the actual systemless root.
i end up digging around like 3 or 4 different SU threads and its frustrating lol.
is the BETA-SuperSU-v2.68-20160228150503.zip the systemless version?
thanks!
2.68 is the one I flashed from TWRP,, but before I applied the zip I accessed the Terminal in TWRP and typed
echo "SYSTEMLESS=true" > /data/.supersu
Then I flashed the supersu.zip. Rebooted to system then used Root Explorer to change the permissions of /su/bin to 751. Removed the xbin_bind folder. Restarted and it was systemless root.
Just curious if anyone knows why we specifically need SuperSU 2.62-3 (at least for MM.) All others seem to cause a hang at the bootloader warning.
I saw in the TWRP output that this version makes a bunch of specific modifications to the system, it had a whole separate section of output with a bunch of detailed changes that I've never seen SuperSU do before. Anyone happen to know why this is necessary?
does 2.65 work?
Root needs to be systemless to work on 6.0
minimale_ldz said:
Root needs to be systemless to work on 6.0
Click to expand...
Click to collapse
All versions work. I use 2.65 and working fine. You first have to open the terminal command in twrp and type "echo SYSTEMLESS=true>>/data/.supersu"
After this you can flash supersu.
Another trick if you have a root app that's not working with systemless root is this command:
"echo BINDSYTEMXBIN=true>>/data/.supersu"
hope i am not violating any forum rules here, as i know how strict they can be. I am not a noob in this area, ive rooted and flashed all my phones since my droid x on. I miss my s-off HTC so bad. I did 5 minutes of research and thought all Galaxy S7s were bootloader/recovery unlockable...only to find out the american versions arent after im stuck with s Sprint SM-G930P. I was able to root and install xposed with the engineer boot.img and odin. Since TWRP or recovery isnt an option I have tried for months to systemless root this thing to hide root and pass safetynet. Ive tried flashfire to flash SU systemless 2.78SR5 and root switch and am on android 6.0.1 PE1 firmware following guides here: https://forum.xda-developers.com/sprint-galaxy-s7/how-to/sm-g930p-root-t3410604 but after factory reseting and trying Rootswitch (will hide exposed but not root with flashfire installing it since bootloader lock doesnt allow TWRP) I piddled with magisk but I am not on the Equinox unlockable s7 and am just at a loss here. Any one out there know of a way to hide root with this version of S7? Im out of ideas and any help here is appreciated. When i flashfire Supersu i get the locked out modified boot img error, but selecting AP and flashing the engineer boot img will get me back up rooted but root switch is a no go. I can use buildprop/rootzwitch to set selinux permissive sstatus but still fail. I refuse to let samsung not let me root my phone properly. I ser xposed modules like snorlax being updated so there seems to be a way to use xposed modules in PoGo while hiding root/xpised but every guide i see leads to TWRP instructions. Can i adb/terminal install magisk/rootswitch? and stiil use modules? (Cart before the horse question seeing as right now i cant bypass safetynet.) HELP!!
Have you made any more progress with this by chance?
I'm looking for a way to get "not systemless" root on MIUI Global Stable v10.3.9 with r/w access to /system. I've already tried SuperSU 2.82 and it doesn't work. Does anyone has any ideas how it could be done?
Have you tried Magisk?
I wouldn't use SuperSU now that the Chinese bought it.
nmkd said:
Have you tried Magisk?
I wouldn't use SuperSU now that the Chinese bought it.
Click to expand...
Click to collapse
Magisk is a "systemless" way to get root, so /system remains unmodified. I intend to install software which modifies /system and it requires system to be rooted with /system modification. I know, that Magisk is a good solution (especially when you use google pay and you want to keep your system up to date with OTA), but in my case Magisk is not an option.