I have a OnePlus3 running OxygenOS 5.0.1 based off of Android Oreo 8.0.0. My device is successfully rooted. I converted the system app as I should. I placed the app into /system/priv-app. The permissions on the app folder are as the should be, and the permissions on the base.apk are as they should be. While the phone is rooted, the app cannot be uninstalled. To me, that means a successful conversion of the app. It got weird though. I restarted the phone for the settings to take place. Then I went to fully unroot my device via SuperSU app, because I want a fully unrooted device. SuperSU asked me if I wanted to restore the stock boot image, I said yes. It then asked if I wanted to restore the stock recovery, I said no. The phone unrooted perfectly fine, and it was no longer rooted, however, my converted system app was missing. I rerooted so I could do the process again, but when my phone booted back up after SuperSU was flashed, the app was back! I went and checked its properties, it still has all of the correct permissions. It is still in /system/priv-app. I then tried the entire process again except I put the app into /system/app and literally the exact same thing happened. Then I fully removed the app from the phone, did a lot of cache wiping and rebooting. I then reinstalled the app and used Link2SD to convert it so a system app. Again, literally the exact same thing happened. This made me very confused, so I went to check the system apps, while the phone was still rooted. My converted app cannot be deleted, HOWEVER, it is listed under the general app list and not system apps, because the app is on the list of apps before I expand the list to display all of the system apps.
I have an LG G3 running Android 5.0.1 and I performed the exact same steps as above. The only difference is that SuperSU didnt ask me all of the questions when fully unrooting. It just unrooted when I clicked the fully unroot button. On the LG the app is listed under system apps, shows up upon reboot when there is no root, and it cannot be deleted....very obviously a system app.
Any pointers to help to get my OnePlus3 situated is greatly appreciated. Thanks!
Related
Ever since I upgraded to 2.2 I've been having issues with superuser. I always receive the notification when an app requests SU, and SU does list those items as having SU permissions, however - I'm having varying results;
Titanium backup - Can remove non system apps fine, can freeze system apps fine, but if I try to uninstall one (for example, stock MMS) it just hangs, and does nothing (I'm able to press home to get out but the process continues to run until I end it.) The rest of the app appears to function as normal.
Quickboot- works just fine (yet requires superuser)
Root Explorer- I'm able to delete system files but as soon as I refresh the folder where I deleted the app, it's still there. (And yes I'm mounted as R/W)
Flashing through recovery - works just fine, no issues.
So far this is what I've done that I thought would correct the issue;
(Firstly, I tried using superoneclick before PNP came out) Tried attempting with both ways and superoneclick advised that root was a success. After doing so, I still had the issues above.
Lastly, I decided to do a clean start when PNP came out so I went back and re-did the 2.2 leak (with odin) re-did CWM, re-flashed PNP (and a theme) yet I'm still in the same situation.
My question is, is anyone else having this issue?
If i'm the only one I will just try to start over again (this time using the updated leak that includes recovery)
I know Ti Backup had issues with removing system apps. As for root explorer I haven't tried to remove any system apps with it.
___________________________________
Just when you think you have it idiot proof, they come out with a better idiot.
bdemartino said:
Ever since I upgraded to 2.2 I've been having issues with superuser. I always receive the notification when an app requests SU, and SU does list those items as having SU permissions, however - I'm having varying results;
Titanium backup - Can remove non system apps fine, can freeze system apps fine, but if I try to uninstall one (for example, stock MMS) it just hangs, and does nothing (I'm able to press home to get out but the process continues to run until I end it.) The rest of the app appears to function as normal.
Quickboot- works just fine (yet requires superuser)
Root Explorer- I'm able to delete system files but as soon as I refresh the folder where I deleted the app, it's still there. (And yes I'm mounted as R/W)
Flashing through recovery - works just fine, no issues.
So far this is what I've done that I thought would correct the issue;
(Firstly, I tried using superoneclick before PNP came out) Tried attempting with both ways and superoneclick advised that root was a success. After doing so, I still had the issues above.
Lastly, I decided to do a clean start when PNP came out so I went back and re-did the 2.2 leak (with odin) re-did CWM, re-flashed PNP (and a theme) yet I'm still in the same situation.
My question is, is anyone else having this issue?
If i'm the only one I will just try to start over again (this time using the updated leak that includes recovery)
Click to expand...
Click to collapse
Has anyone figured out the deal woth TB? Ive been having the same issues.
nickrl said:
Has anyone figured out the deal woth TB? Ive been having the same issues.
Click to expand...
Click to collapse
Still doesn't work for me to uninstall apps. I just downloaded Uninstaller for Root from the market and it works fine. Do my backups in TB and uninstall from UfR.
akellar said:
Still doesn't work for me to uninstall apps. I just downloaded Uninstaller for Root from the market and it works fine. Do my backups in TB and uninstall from UfR.
Click to expand...
Click to collapse
I updated my root explorer and did a fresh install and it corrected the problem also.
Had same issue with TI, used Uninstaller for root but using pick'n'pack was pretty much the same experience
Dually noted on the uninstallation and reinstall of root explorer...
Morning all.
So i'm on a rooted 4.3 sense 5.5 Rom but can't seem to get rid of ads.
I've tried AdAway 2.8 and AdFree 0.8.66 but both work for a few hours then revert back. If I reboot as suggested my changes are reverted as if I never ran the program in the first place.
Any suggestions?
elmuziko said:
Morning all.
So i'm on a rooted 4.3 sense 5.5 Rom but can't seem to get rid of ads.
I've tried AdAway 2.8 and AdFree 0.8.66 but both work for a few hours then revert back. If I reboot as suggested my changes are reverted as if I never ran the program in the first place.
Any suggestions?
Click to expand...
Click to collapse
Which ROM are you running? Real stock, but rooted? Your problem is HTC system protection, it's reverts all system changes on boot or specific system events....
I'd recommend this ROM - choose the deodex ROM - the ROM includes a modded kernel which removes the protection.....
Or you could S-OFF, but read this first!
Have fun!
Any issues, let me know!
Morning,
Yeah the deox ROM is the one I'm on thanks to your recommendation.
Originally I could never get Xposed or SuperSU to work but ever since that ROM, and the SuperSU mentioned in the post and Xposed 2.4.1 these have been fine which is why I wondered if maybe there were updates available for the ad away apps.
Is there a way of re-flashing the kernal without taking the ROM back to the initial setup?
elmuziko said:
Morning,
Yeah the deox ROM is the one I'm on thanks to your recommendation.
Originally I could never get Xposed or SuperSU to work but ever since that ROM, and the SuperSU mentioned in the post and Xposed 2.4.1 these have been fine which is why I wondered if maybe there were updates available for the ad away apps.
Is there a way of re-flashing the kernal without taking the ROM back to the initial setup?
Click to expand...
Click to collapse
Before we go to flash city, try this version of adaway https://db.tt/nVzVc7m5
You may have to try and apply a few times, if it gets stuck on applying, reboot and try again
yeah that's the one i have.
Is it as easy to apply the host files from recovery or bootloader if flashing the kernal is tricky?
Thanks again for your help, you're becoming super helper guy for me!
elmuziko said:
yeah that's the one i have.
Is it as easy to apply the host files from recovery or bootloader if flashing the kernal is tricky?
Thanks again for your help, you're becoming super helper guy for me!
Click to expand...
Click to collapse
You could have the generated hosts file written to an alternative location by setting it in preferences - then move it manually.... BUT you shouldn't need to....
The kernel is integrated into the ROM, there isn't a custom ROM available to flash....
Can you screenshot the errors you get, and also go to supersu and select full logging for adaway, once done, try updating and applying.... Send the supersu logs please!
Sent by my favorite carrier pigeon.... hope he comes back.....
Eugh, now it appears ad-away has taken a turn for the worse.
Removed, rebooted, reinstalled.
See attached. Computer sez no.
Worth a complete re-install of ROM?
Do you have Titanium Backup Pro? If so.....
Remove the app from supersu.
Force Stop the app via apps in settings.
Convert the app to a system app using Titanium Backup (or an alternative app that converts apps system apps, search the store).
Start the app again, supersu will ask for permissions.
Restart your phone.
Try again!
Boy I am not having any luck with this whatsoever.
Ok so I reflashed my ROM with the one mentioned earlier.
Tried AdAway without any jiggery pokery and it applys successfully but then two hours later it's reverted back.
I tried full logging but then AdAway kept crashing.
I tried Titanium backup Pro and spent an hour watching it "Processing... Please wait".
I rebooted, Opened ESFileExplorer, mounted the System folder, copied AdAway into System\Apps, opened the app and it crashed.
Rebooted and AdAway is no longer installed. Slapped it in System\Apps again, managed to open with full logging and got the attached.
I think I'm just destined to have Ad's on a few apps. It just keeps reverting when I reboot.
elmuziko said:
Boy I am not having any luck with this whatsoever.
Ok so I reflashed my ROM with the one mentioned earlier.
Tried AdAway without any jiggery pokery and it applys successfully but then two hours later it's reverted back.
I tried full logging but then AdAway kept crashing.
I tried Titanium backup Pro and spent an hour watching it "Processing... Please wait".
I rebooted, Opened ESFileExplorer, mounted the System folder, copied AdAway into System\Apps, opened the app and it crashed.
Rebooted and AdAway is no longer installed. Slapped it in System\Apps again, managed to open with full logging and got the attached.
I think I'm just destined to have Ad's on a few apps. It just keeps reverting when I reboot.
Click to expand...
Click to collapse
Bizarre.....
Right, I now recommend this rom (sweet updates on the way to!!) http://forum.xda-developers.com/showthread.php?t=2616780
Install this from Play https://play.google.com/store/apps/details?id=stericson.busybox&hl=en
Install adaway....
I found the easiest solution was to install a custom /etc/hosts file, search google for "/etc/hosts adblock"
Try this: http://forum.xda-developers.com/showthread.php?t=2597332 , it works for me with xposed.I am on stock 4.3 rooted. I have tried adfree, adaway, manualy edited hosts but no succes.
Normally when you install BetterBatteryStats from either apk or Google Play, you'll need to launch the app and install it again but as a System app. After that's done, reboot the phone and it'll work.
However on my OPO, all I see is this after rebooting the phone:
http://s23.postimg.org/u5jyasu8b/Screenshot_2015_05_01_19_13_22.png
I've never had this issue before and I've only just had this phone recently. It's rooted and running Smoki's rom. Any ideas?
I had this issue a few weeks back. I believe that I uninstalled it, rebooted, reinstalled and it was fine. I did have to use titanium backup to uninstall, and then manually delete the all in the system/priv app folder.
Sent from my One+ 1
Dear community,
honestly I considered myself not a noob anymore when it comes to flashing, rooting and installing devices. But obviously I was wrong: Cyanogenmod, Titanium Backup and SuperSU are fooling me to madness. :silly: So I hope to find help here because all I want to do is to restore all apps' data. But I will start at the beginning:
I updated my rooted Nexus 7 LTE to CM 13.0-20151226-NIGHTLY-deb and it turned out that Google Play Services continue to crash, no PlayStore could be loaded and so on. I've searched for this issue and don't want to discuss this here as there are many threads for this already.
However, I deciced to switch to OpenGapps and downloaded the pico package for Android 6 on ARM.
By the way I also switched from CWM recovery to TWRP 2.8.7.1.
Finally, CM was running as expected and I danced my pants off!
During all this I formatted the device completely, but made a backup of all apps using Titanium Backup.
So, I re-installed Titanium Backup, copied the backup files to the device and started to "restore missing apps and data" from the bulk operations menu.
All selected apps were installed perfectly (danced again) but then I noticed that the apps' data was not restored.
I searched for this issue and found instructions saying that SuperSU is needed for Titanium Backup to restore data. That was new to me as TB worked fine without SuperSU on my device all the time.
However, I flashed the latest stable Version of SuperSU from chainfire.
After rebooting, the SuperSU app was installed and when it starts, an error popup appears saying that no su file is installed and this has to be done manually.
When I now start Titanium Backup, it prompts missing root access and consequently does not start up.
Furthermore CM is really unstable and freezes from time to time.
So, I lost root by flashing SuperSU? What irony!
Anyway, I am willing to format and re-install my device another time and I would gladly set SuperSU aside as I never needed it in the past. But I really need to get Titanium Backup working to restore the apps' data.
Can anyone of you help me on this, please? Is SuperSU really necessary or do you know a way to manage Titanium Backup without SuperSU on CM13?
cocororo said:
Dear community,
honestly I considered myself not a noob anymore when it comes to flashing, rooting and installing devices. But obviously I was wrong: Cyanogenmod, Titanium Backup and SuperSU are fooling me to madness. :silly: So I hope to find help here because all I want to do is to restore all apps' data. But I will start at the beginning:
I updated my rooted Nexus 7 LTE to CM 13.0-20151226-NIGHTLY-deb and it turned out that Google Play Services continue to crash, no PlayStore could be loaded and so on. I've searched for this issue and don't want to discuss this here as there are many threads for this already.
However, I deciced to switch to OpenGapps and downloaded the pico package for Android 6 on ARM.
By the way I also switched from CWM recovery to TWRP 2.8.7.1.
Finally, CM was running as expected and I danced my pants off!
During all this I formatted the device completely, but made a backup of all apps using Titanium Backup.
So, I re-installed Titanium Backup, copied the backup files to the device and started to "restore missing apps and data" from the bulk operations menu.
All selected apps were installed perfectly (danced again) but then I noticed that the apps' data was not restored.
I searched for this issue and found instructions saying that SuperSU is needed for Titanium Backup to restore data. That was new to me as TB worked fine without SuperSU on my device all the time.
However, I flashed the latest stable Version of SuperSU from chainfire.
After rebooting, the SuperSU app was installed and when it starts, an error popup appears saying that no su file is installed and this has to be done manually.
When I now start Titanium Backup, it prompts missing root access and consequently does not start up.
Furthermore CM is really unstable and freezes from time to time.
So, I lost root by flashing SuperSU? What irony!
Anyway, I am willing to format and re-install my device another time and I would gladly set SuperSU aside as I never needed it in the past. But I really need to get Titanium Backup working to restore the apps' data.
Can anyone of you help me on this, please? Is SuperSU really necessary or do you know a way to manage Titanium Backup without SuperSU on CM13?
Click to expand...
Click to collapse
lmao, your title is nice!
i believe your problem is you used the wrong su zip, you need the latest beta, not stable. should be .52 if im not mistaken. .52 is stable even though its not listed as, i have been using it for some time, and its whats needed for M. you may even find some .6 versions, dont use those, they are systemless, well you can if you want lol. i havent tried them yet, so i dont know what pitfalls may lurk.
Thank you for your help and I am happy to entertain
bweN diorD said:
i believe your problem is you used the wrong su zip, you need the latest beta, not stable. should be .52 if im not mistaken.
Click to expand...
Click to collapse
I will try to update SuperSU as soon as possible.
But sadly TWRP now freezes a few moments after I start the device in recovery mode. When the device starts normally, it freezes as well while showing the CM launcher screen. It stays animated but nothing happens. I will try to re-install TWRP via fastboot flash and then install SuperSU .52 and post my experiences here. :fingers-crossed:
Hi again bweN diorD,
bweN diorD said:
i believe your problem is you used the wrong su zip, you need the latest beta, not stable. should be .52 if im not mistaken.
Click to expand...
Click to collapse
Sorry to say so but SuperSU .52 does not solve the problem. In fact, after flashing the BETA-SuperSU-v2.52.zip using TWRP, CM does not start up anymore. The loading screen with the hypnotizing smiley appears and stays animated but even after 15 minutes CM does not start up. Even TWRP was freezing from time to time.
So I re-installed TWRP, CM and Gapps like in my first post again.
So, is the problem that my device is not rooted indeed? Could this be fixed with CF-autoroot or any tool like this?
I found this thread http://forum.xda-developers.com/showthread.php?t=2448352 although it is for the device deb-razor and my device's bootloader says it is a deb-zoo. By the way, the bootloader displays "LOCK STATE - unlocked".
cocororo said:
Hi again bweN diorD,
Sorry to say so but SuperSU .52 does not solve the problem. In fact, after flashing the BETA-SuperSU-v2.52.zip using TWRP, CM does not start up anymore. The loading screen with the hypnotizing smiley appears and stays animated but even after 15 minutes CM does not start up. Even TWRP was freezing from time to time.
So I re-installed TWRP, CM and Gapps like in my first post again.
So, is the problem that my device is not rooted indeed? Could this be fixed with CF-autoroot or any tool like this?
I found this thread http://forum.xda-developers.com/showthread.php?t=2448352 although it is for the device deb-razor and my device's bootloader says it is a deb-zoo. By the way, the bootloader displays "LOCK STATE - unlocked".
Click to expand...
Click to collapse
hmmm,
i havent used 2.52 on a cm rom, but i have used it on plenty aosp 6.0.* roms without issue.
clean things up so its booting again, then look in developer options and make sure root is turned on. i have seen a few times devs default it to off, but i have never seen a custom rom come not rooted at all.
bweN diorD said:
clean things up so its booting again, then look in developer options and make sure root is turned on.
Click to expand...
Click to collapse
Thanks for your support!
I cleaned everything up -- meaning re-installed everything -- so the device boots up. I checked the developer options and root is set to "apps only". That worked up to now.
Speaking of root: As I wrote I used to have CWM and switched to TWRP. Anyhow, CWM always asked to "fix root" when exiting. I think that's why things worked then and now with TWRP this "fix root" option is gone. But why is SuperSU not working for my Nexus 7 deb? I also tried to install older versions like advised in the Nexus 7 thread here but there was not even a SuperSU app.
So, I recap: CWM used to fix root, TWRP does not. That's why installing SuperSU seems to be a good idea. SuperSU's latest version freezes CM at start-up. Without SuperSU Titanium Backup does not restore app data while other apps do not have problems to get root access. I'm confused
cocororo said:
Thanks for your support!
I cleaned everything up -- meaning re-installed everything -- so the device boots up. I checked the developer options and root is set to "apps only". turn it on apps and adb and see if that helps, thats the preferred setting anywaysThat worked up to now.
Speaking of root: As I wrote I used to have CWM and switched to TWRP. Anyhow, CWM always asked to "fix root" when exiting. I think that's why things worked then and now with TWRP this "fix root" option is gone. its not gone in twrp, it sees that you have root and doesnt ask. really its unadvised to use the twrp generated root anyways But why is SuperSU not working for my Nexus 7 deb? I also tried to install older versions like advised in the Nexus 7 thread here but there was not even a SuperSU app.hmm, maybe thats the problem, maybe you need to install supersu to get things working properly. its on the play store, give it a shot
So, I recap: CWM used to fix root, TWRP does not. That's why installing SuperSU seems to be a good idea. SuperSU's latest version freezes CM at start-up. Without SuperSU Titanium Backup does not restore app data while other apps do not have problems to get root access. I'm confused
Click to expand...
Click to collapse
^^^^
so to clarify your last paragraph, when you say that installing supersu breaks things, were talking about the zip right?
i just want you to get the app from the play store, if you havent tried that alone yet. but change the root setting too.
bweN diorD said:
so to clarify your last paragraph, when you say that installing supersu breaks things, were talking about the zip right?
i just want you to get the app from the play store, if you havent tried that alone yet. but change the root setting too.
Click to expand...
Click to collapse
Correct, I was talking about the zip which is meant to be installed through TWRP.
So, I downloaded the SuperSU app after double-checking that root is set to "Apps & ADB" in the developer settings. Btw. debugging and installation from unknown sources (I hope this is the right translation for this feature) is enabled as well.
When I started the SuperSU app, it first says the binary SU needs an update and I could choose the installation method: When choosing "normal", the app tried to install but failed saying "Installation failed! Restart device and try again!" but even after restarting this was what the app gave me. When I chose "TWRP" the app rebooted the device to recovery but I assume this would end up in installing the zip file which crashed my CM.
Finally, I installed CF-autoroot for deb via the .bat file included in the CF-autoroot package. Now, SuperSU and Titanium Backup are not complaining anymore, so I think this root issue is fixed! :highfive: (couldn't find a dancing smiley).
However, Titanium Backup is not bringing back my app data The restore process seems good as Titanium Backup installs missing apps but even if I install an app the official way via PlayStore and then restore the app's data from my backup using Titanium Backup, there is no effect and the app acts like being installed freshly.
TB claims "restore successful" but the app's data is still missing. I will now check if the backup files are really sound and if I can get them to work on another device. The worst thing I could imagine is that TB did not backup data of apps which had been installed on sdcard. In that case, the data is lost, I'm afraid...
Do you have an idea how this could be or what I could try?
cocororo said:
Correct, I was talking about the zip which is meant to be installed through TWRP.
So, I downloaded the SuperSU app after double-checking that root is set to "Apps & ADB" in the developer settings. Btw. debugging and installation from unknown sources (I hope this is the right translation for this feature) is enabled as well.
When I started the SuperSU app, it first says the binary SU needs an update and I could choose the installation method: When choosing "normal", the app tried to install but failed saying "Installation failed! Restart device and try again!" but even after restarting this was what the app gave me. When I chose "TWRP" the app rebooted the device to recovery but I assume this would end up in installing the zip file which crashed my CM.
Finally, I installed CF-autoroot for deb via the .bat file included in the CF-autoroot package. Now, SuperSU and Titanium Backup are not complaining anymore, so I think this root issue is fixed! :highfive: (couldn't find a dancing smiley).
However, Titanium Backup is not bringing back my app data The restore process seems good as Titanium Backup installs missing apps but even if I install an app the official way via PlayStore and then restore the app's data from my backup using Titanium Backup, there is no effect and the app acts like being installed freshly.
TB claims "restore successful" but the app's data is still missing. I will now check if the backup files are really sound and if I can get them to work on another device. The worst thing I could imagine is that TB did not backup data of apps which had been installed on sdcard. In that case, the data is lost, I'm afraid...
Do you have an idea how this could be or what I could try?
Click to expand...
Click to collapse
sorry, i really dont know what happens as far as titanium when you put an app on the sd.
glad you got root working though, although i still dont understand why it wouldnt work the right way.
if you run into any more specific road blocks, ill try and help if i can, but this general problem with the data, i havent a clue the problem or solution, short of the data isnt there completely.
Hi again,
sorry for my late reply! I tried a couple of things but here's the most obvious one:
Apparently the backup files are kind of corrupt. I don't know what went wrong there but TB did not create a full backup. Indeed there is a .tar.gz file for every app but in fact none of these has more than 2 KB. So I strongly assume that this might be the mistake - which also means that all my app's data is lost.
bweN diorD said:
glad you got root working though
Click to expand...
Click to collapse
At least this is a success and I am happy to have TWRP, OpenGapps and Titanium Backup running on a fully rooted device :good:
Thank you for all your time and help! I really appreciate how supportive we "techies" are :highfive:
Have a great day and - a bit late but anyway - a happy new year!
I want to switch from supersu to superuser, and having an interesting problem that supersu somehow covered up. I have a Nexus 5x running the stock rom. With every months upgrade I would flash using fastboot, go into twrp recovery before first full boot and remove a bunch of unneeded applications in /system/app. When I would boot up those applications would be gone. Somehow this isn't the case with superuser. I can still go into recovery and remove them, but when I boot up all the applications are still in /system/app. If I go back into twrp they are still shown as being missing. I've tried installing es file explorer, but it's unable to delete the applications once the system is up. remounting /system doesn't work either. Any help?
Unrooting supersu caused all the applications to come back; so does supersu not really delete them either, but somehow prevents them from showing up following the recovery scheme or something?
bsd1101 said:
I want to switch from supersu to superuser, and having an interesting problem that supersu somehow covered up. I have a Nexus 5x running the stock rom. With every months upgrade I would flash using fastboot, go into twrp recovery before first full boot and remove a bunch of unneeded applications in /system/app. When I would boot up those applications would be gone. Somehow this isn't the case with superuser. I can still go into recovery and remove them, but when I boot up all the applications are still in /system/app. If I go back into twrp they are still shown as being missing. I've tried installing es file explorer, but it's unable to delete the applications once the system is up. remounting /system doesn't work either. Any help?
Unrooting supersu caused all the applications to come back; so does supersu not really delete them either, but somehow prevents them from showing up following the recovery scheme or something?
Click to expand...
Click to collapse
You aren't doing something right or you don't have something setup correctly. With root, you should be able to unintelligible them completely.
When you removed them, did you wipe cache and dalvik/ART cache before rebooting? If not then the system probably still thinks they are there because they still have data loaded into cache.
I recommend sticking with SuperSU, superuser doesn't work as well as SuperSU
Sent from my SM-S903VL using Tapatalk
I've been googling a bit more. As it turns out there are two system partitions for nougat; in nexus 5x and some other devices apparently. This became more apparent when the file recovery-from-boot.p; which I rename in order to prevent recovery from being overwritten is not renamed when booting the OS. Nougat apparently pulls the system files from somewhere else. So whatever Chainfire did makes it boot the same partition as visible in recovery. Fully unrooting brings all those apps/system partition back. Haven't been able to find a good post that tells me how to to circumvent this without SuperSU; or exactly how this works.