Am I seeing things - there seems to be a /su folder in main internal storage.
This seems to trigger some apps to think the device is rooted.
Now I did EARLIER have SuperSU present - but cleaned it up to verify a few protected/root aware preventing apps.
su-mksh is the only file in that folder; timestamps assume it was factory installed?
NPS_CA said:
Am I seeing things - there seems to be a /su folder in main internal storage.
This seems to trigger some apps to think the device is rooted.
Now I did EARLIER have SuperSU present - but cleaned it up to verify a few protected/root aware preventing apps.
su-mksh is the only file in that folder; timestamps assume it was factory installed?
Click to expand...
Click to collapse
Wondering if this is the OTA protect from SuperSU?? Renaming it to SU2 seems to not hose anything and root still works on a reboot. If anyone has any info if the /SU folder is system ROM installed or if this is a SuperSU side effect would love to know. DO NOT see this on a 4.3 device at all. On a reboot though the renamed /SU2 is gone and replaced with /SU... hmmmm this smells like a system file
How did you unroot? Typically supersu leaves remnants if you try to clean it yourself. The supersu app has an unroot feature that works great.
Sent from my Nexus 5 using Tapatalk
Related
I was getting ready to update my tablet and try the official ICS as well as the CM9 builds. Just before getting ready, I was apparently bitten by a bug in the busybox installer (1.20.0) which disabled all network access from my device. I also tried the platform.xml permissions change to add sdcard_rw but apparently something went wrong and I was left with no write access to either /mnt/sdcard/ or /mnt/sdcard/extStorages/SdCard/. I was therefore unable to find a way to run TitaniumBackup to get a consistent backup (no network for external backup, no local storage for even root-requesting mode), but wanted some sort of backup before wiping my tablet. I ended up finding an rsync binary, and via an adb root shell rsynced all of /data/app, /data/app_private, /data/media, and the wpa_supplicant file for wifi to the internal sdcard.
I have since wiped and installed the 8/10 CM9 release, and have all of my apps available. I've also restored the data and run the fix_permissions script from the CWM recovery. What I did was copy /data/app and /data/data back at the same time via a recovery adb shell. What I ended up with though, is the lib directory from each of the copied data directories being symlinked to an invalid target (lib -> /mismatched_uid/settings_NNNNN/fs_0, where NNNNN is an app id, and differs for each data directory). What this causes is for apps not only not having write permissions, but those that require libs fail at startup to even load their expected libraries are terminate immediately.
I realize after doing this that one can't restore apps and data at the same time via recovery - the fix_permissions script won't work until at least one boot cycle so that the system can process the new apks and assign app ids. I've rerun the script and the permissions are set appropriately, however I am still stuck with the broken lib directories for each of the effected packages.
Since I don't have any important data changes since the load, what I'm going to try doing is wipe /data/data and reload the content in recovery since they have now been assigned app ids. However, as a point of question, what, and when do the /data/data/*/lib/ directories get replaced with the broken symlink, and if when that situation is encountered is there anything that can be done besides reloading the data properly (or an uninstall/reinstall)? I couldn't find any trace of the previous contents of the ./lib/ directories. I've tried with a couple test cases using Titanium Backup to backup the app (even with the broken symlink), then uninstall the app and reinstall the app plus the data. This works, I presume because the appid is managed appropriately.
I tried again and it didn't work as I expected above. I re-copied the /data/data/ contents via adb in recovery, ensured that the lib contents were correctly linked (./lib/ owned by system, other dirs owned by app_NNN). However, after booting the device, I had the /mismatched_uid/ links reappear.
Any pointers on how to bulk restore the data and tie it to the app properly?
mrjoel said:
I tried again and it didn't work as I expected above. I re-copied the /data/data/ contents via adb in recovery, ensured that the lib contents were correctly linked (./lib/ owned by system, other dirs owned by app_NNN). However, after booting the device, I had the /mismatched_uid/ links reappear.
Any pointers on how to bulk restore the data and tie it to the app properly?
Click to expand...
Click to collapse
I'm having a similar problem with no wifi, and mismatched uids (and consequently no /data/data access -> crashing apps) on another device. I've been searching (and learning) for about two weeks now. Did you ever figure this one out?
tonestertm said:
I'm having a similar problem with no wifi, and mismatched uids (and consequently no /data/data access -> crashing apps) on another device. I've been searching (and learning) for about two weeks now. Did you ever figure this one out?
Click to expand...
Click to collapse
Did u try flash Pit file?
Sent from my GT-P6200 using XDA Premium
tonestertm said:
I'm having a similar problem with no wifi, and mismatched uids (and consequently no /data/data access -> crashing apps) on another device. I've been searching (and learning) for about two weeks now. Did you ever figure this one out?
Click to expand...
Click to collapse
No, I didn't directly figure it out. I ended up doing the restore, and using TitaniumBackup to backup all apps with the broken ./lib/, then uninstalled them all and reinstalled them. When reinstalling, the lib directory was correctly generated with a [newly] associated uid.
Hey guys,
I've done a little Google-ing but I can't find an answer to this one...
So I rooted my new Nexus yesterday but today I started to create myself some backups of the stock ROM just in-case I ever need or want them.
While I was doing this I went through the following process:
1. Ran Google's Factory Image: https://developers.google.com/android/nexus/images#hammerhead.
2. Installed TWRP through Fastboot.
3. Rebooted my bootloader.
4. Opened TWRP's File Manager.
5. Noticed a weird folder...
So from the steps that I have listed above, I'm pretty sure that It's safe to say that the only data/software that is held on my device's storage at the particular point in time is Google's (excluding TWRP), correct?
So back to this weird folder... I noticed a folder in the following directory "/" and it was called "supersu". Is this folder something to do with the Stock Google OS or is this some kind of left-over folder from the ROM that I had used yesterday (unlikely seeing as I have just ran the factory image)?
Here is a DIR Listing of "/":
boot
cache
data
dev
etc
firmware
licence
persist
proc
recovery
res
root
sbin
sdcard
supersu (the folder which raised my suspicion)
sys
system
tmp
usb-otg
Am I in the wrong mindset? Does Google's Factory Image re-format the whole device including "/" or does it just do certain DIRs? Is that "supersu" folder mine or did Google already have that?
Thanks,
LewisD94
EDIT: I know what it is!
TWRP have a built-in service that allows you to install SuperSU to your device without having to download or flash it manually, I'm pretty sure that this folder would have landed it's self on my device when I installed the TWRP recovery through Fastboot... It's the only thing I can think of, testing it now but flashing the Factory Image without a custom recovery. Will report back with results.
FIXED: It must be something to do with TWRP's SuperSU service as I previously mentioned...
I have just ran Google's Factory Image: (https://developers.google.com/android/nexus/images#hammerhead) and installed ES File Explorer then navigated to "/" and I no longer have the folder in question...
New DIR listing of "/"
I don't have that folder. I have the latest TWRP installed. I really wouldn't worry about it though. Just delete it if you don't use Super SU
Sent from my Nexus 5
SuperSU is superuser which grants root access to apps. It was likely left over from a previous ROM because unless you completely wiped the SD card it remains inert.
When you return to completely stock like in the general sticky everything is going byebye.
There are stock ROMs hanging around development that are deodexed or odexed whatever you want. Some of them even have goodies inside.
When you root and unlock bootloader, the super user is installed during the process. Nothing to worry about. SU acts as your phones front door security screening any elevated/administrative task. This is what sprint personnel look for when excepting returns on devices. They know if your rooted and you try to say there is a issue with your device, if they see SU installed they'll know it was probably you who caused it. Besides the main fact but you have nothing to worry about. If you go completely stock and re lock your bootloader, just delete the folder off your SD card.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Must be a TWRP thing. I use CWM and I dont have a supersu folder.
Hi all,
I recently moved from Windows Phone to Android and have been enjoying fiddling with my phone. I rooted the phone using ODIN and CF Auto Root (CF-Auto-Root-herolte-heroltexx-smg930f.tar.md5). I used Titanium Backup to remove a lot of bloatware from my device, but ended up making a mess of things. I then flashed the stock firmware for my Telstra device from Sammobile (G930FXXU1APF2_G930FTEL1APF2_TEL).
Everything seemed fine, but I now cannot use Titanium Backup to integrate updates or move apps to the system partition. I have tried using ES File Explorer and an adb shell to do this also, but with no luck. The apps either do not work, or are installed back into /data/app. It seems to move the apk to /system/app (I can see it there), then removes the app from /data/app and then hangs. If I reboot the phone, the app is uninstalled (but the apk is still in /system/app). I have noticed via /proc/mounts that the /system partition is often mounted RO. Even when I remount RW after TB starts processing it immediately becomes RO.
I have set the TB to use indirect app loading, enabled USB debugging and unknown sources for apps.
Before I reflashed with the stock firmware I was able to move apps to the system partition (I did Gmail and Google Keyboard and they worked well). Could I have stuffed up my firmware flashing? I only used the AP file, not BL/CP/CSC/UMS that were included in the download.
I apologise in advance if I am all over the shop here with my description. I know enough to get myself into trouble but not enough to get out! And yes, first thing I did after flashing was to back everything up so I don't make the mistake again...
Hi All
I am hoping someone can help... I have the Galaxy S7 (SM-G930F / 6.0.1 / UK / EE) and have come up with an issue.
I use Cerberus Apps in case my phone is lost - you are able to install this into the system to avoid someone wiping the phone and removing the software. To do this the phone must be rooted and then I usually use Link2SD to transfer the app to make it a system app. This has always worked on my old phones - but alas not this time.
The problem is that the system partition (4Gb) is full!! I have deleted all the language packs to try and clear some space - but it is still full! Strangely enough I also uninstalled an "Amazon" app which was listed as being a system app and quite large (from memory I think it was just under 100Mb)... but when I removed it and rebooted the system partition free space remained unchanged! It's possible that Amazon was a user app and I mis-read it... but anyway - I thought that the only way to clear some space was to resize the system partition - so I installed TWRP (3.0.2), have done a complete backup (system/efs/etc) apart from \data as this showed 0Mb and "failed to mount" when I tried to back it up originally.
So, my question is - can anyone help me to free some space from the system partition to allow Cerberus App to be stored there? I did think about uninstalling the VR Gear files as I dont have a VR device and assumed I could re-load these from Google Play if needed - but I do have the Galaxy Gear watch - so decided not to remove these files in case it screwed this up. Not sure which Google Apps I can remove and re-install if needed... so if anyone knows this, then that would be a help too
I thought you could resize the partition in TWRP but cant find any clear details on how to do this, so thought I'd ask here before I screw the phone up :silly:
Any ideas/help greatly received.
TWRP doesn't support encryption so that's likely why /data won't mount. Resizing partitions is typically done via Odin with PIT files, but it's very dangerous, so I wouldn't recommend it.
Luxembourg ROMs have around 130mb free system space, so there must be a ton of carrier bloat in yours. This doesn't sound right though, it's required that there is some space for expansion. Could you run the following command in a root terminal and post the results please?
df -k | grep system
CurtisMJ said:
df -k | grep system
Click to expand...
Click to collapse
Thanks Curtis - I left my phone at home today, so will try this tonight and post results. After deleting all the unwanted language files I have about 40Mb space free, but this still doesnt seem to be enough as when I run Link2SD and reboot the phone, Cerberus has vanished and has to be re-installed... although when it re-installs it shows it as an "update" which would indicate that it is installed already - just 'lost' ???
Will update tonight when I get a moment.
Thanks
That's interesting actually. It seems to be indicative of permission issues. The app was successfully moved to the system, but the permissions on its files were wrong and the system refuses to load it(Link2SD's fault, essentially) . It's still acknowledged by the app manager though, which is why it can be "updated". Can you try move it with something apart from Link2SD? I recommend titanium backup.
CurtisMJ said:
Can you try move it with something apart from Link2SD? I recommend titanium backup.
Click to expand...
Click to collapse
Thanks Curtis - I have Titanium Backup (free version) installed already so can give it a go - I have only used it for backups (a long while ago) and have never used it to relocate an app... is it fairly self explanatory how to do it?
Will look tonight when I get in
Thanks
Just tried with titanium myself and it fails in a similar manner. Seems Marshmallow is a little fiddly and Link2SD puts out a generic message when it has issues. Titanium just freezes. You'll have to do it manually
First you'll need to clear the system of failed attempts. Look in the /system/app and /system/priv-app with a root Explorer for Cerberus apks or folders. Next, look in the /data/app folder and find the Cerberus folder. Take note of this path.
Next, fire up a root terminal and enter the following commands. In my case I was moving Greenify.
mount -o remount,rw /system
cp - a /data/app/com.oasisfeng.greenify-1 /system/app/Greenify
Replace the data folder with your noted path. The system path can be anything.
Then reboot and the app should be system.
Hi Curtis
Thanks for spending so much time on this.
OK, I skipped straight to the manual relocation method that you said. Whilst the app is Cerberus the APK etc is called System Framework as I have installed the 'hidden' version rather than the one which shows as Cerberus on the phone. However using OI File Manager, when I look in /system/app and /system/priv-app folders there is nothing called Cerberus or System Framework... so I am assuming that there are no orphaned APKs or other files.
But, this is where the strange thing starts, when I look in the /data/app folder, it is empty... so I am guessing I am looking in the wrong place as there are loads of apps! I am looking from home then selecting data, etc... any thoughts?
Oh, I have checked that hidden files are shown too!
Thanks again
i used to install the same app on my S7
please follow this guide & let me know the result.
1- uninstall Cerberus App, Link2SD, TTb, etc. and reboot
2- install SystemCleanup.
3- from the app SystemCleanup swip to tab apps and remove some bloatware like Google books, music, games, google TTS.
4- Reboot & install Cerberus App, do not run it.
5- from the app SystemCleanup go to apps tab and move Cerberus App to system/app & reboot again.
6- That's all.
Click to expand...
Click to collapse
Hi Abuzar
Thanks for the help... I tried using System Cleanup and initially it didn't work... it didn't show System Framework after cleaning up which made me think it was uninstalled properly. But when I tried to re-install it I got a message asking if I wanted to update the the built in application... so I said yes and re-checked in System Cleanup and it was visible, so I tried uninstalling it and after a couple of attempts it succeeded.
Then I re-installed and it installed it as a new app and it was visible in System Cleanup as installed in /data. So, I moved it to /system and configured it. It now lists in System Cleanup as being installed @auto system+data... so I am assuming it has installed properly... but not 100% sure as it lists some of it in data - so not sure if after a reset it will wipe the user profile from Cerberus or not.
I took a backup in TWRP and thought I would do a factory reset and test it... but on the S7 using factory reset in O/S it asks for my samsung password etc so looks like it may delete my Samsung/Google account's so didn't proceed as I didn't want to delete any online info. So... I tried factory wipe in TWRP but it just said failed "could not mount /data and unable to find crypto footer" and a few more "failed to mount /data" errors... so I gave up and will have to assume its installed properly as a system app
Thanks for all your help.
Just as a final note, the system+data combo sounds normal. Under regular conditions, the system partition is read only, so in order to install any updates to system apps, Android actually installs them as data apps, but cross-references them to system apps and gives them the relevant permissions. You can remove the data part by selecting "Uninstall Updates" in the app info page.
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.