Just installed the new TB-J0606F_S320208_220719_ROW that was pushed to my P11 today. Now I've got another pre-installed app from Lenovo called “Tablet Center”. Of course, it can not be disabled and permissions can not be revoked.
Has anyone attempted to remove it via ADB as of yet?
On a p11 plus I have disabled it
ADB AppControl
great program
The new firmware seems to be causing issues - on my tablet at least. Won't wake from sleep and hard resets into factory bootloader all by itself.
Related
I was just wondering if anyone here has any experience with using Mobile Iron with a phone that has been rooted for a few small tweaks and then unrooted.. Does it work? Can Mobile Iron tell that you were once rooted but are no longer?
I've got an AT&T Galaxy S3 that was recently upgraded via OTG to Android 4.3 with Knox and the new bootloader, etc. Unfortunately, the 4.3 upgrade has disabled my ability to tether. I'd like to apply a mod that fixes that limitation, but I don't want to lose the ability to get work email and such on my phone via Mobile Iron.. Any thoughts on whether or not it should be possible to:
1. Temporarily uninstall Mobile Iron
2. Root my phone and apply the tether mod
3. Remove root from my phone
4. Reinstall Mobile Iron and have it work?
Any thoughts, suggestions, advice would be greatly appreciated!
Thanks
MrSimmonsSr
Sent from my Sero 7 Pro using Tapatalk 4
For the record, just wanted everyone to know this seems to have worked like I'd hoped! I used CF-Autoroot to root my S3 running 4.3.. (The first time I tried it I bricked my device because I didn't think to unencrypt it before I applied root. Don't do that! I had to flash the 4.3 update twice to get it all working again! )
But once I did that I was able to root the fresh install, remove tons of bloatware and apply a tether hack. Then I unrooted and reinstalled Mobile Iron and Touchdown.. So far no issues!
Sent from my Sero 7 Pro using Tapatalk 4
Hi Mr,
currently I am doing research on MDM solutions and I found some information about the detection methods MDMs use to detect root. The following four are commonly used (https://www.netspi.com/blog/entryid/209/android-root-detection-techniques):
1. Check default files and configs.
2. Check if there is a Superuser app.
3. Check permissions of some folders (i.e. /data)
4. Check is "su" commands can be executed.
I don't expect or expected it to cause any problems! Dependant on the security policy, installing some apps like thether hack, might cause a security alert though.
Sometimes applications that require root will trip the application that wants to ensure root doesn't exist. For example Citrix Home detected BusyBox existed on my system & thus flagged my phone as rooted.
There is also an Xposed Module which will attempt to hide root:
http://www.xda-developers.com/android/xposed-module-to-cloak-root-access-from-apps/
http://forum.xda-developers.com/showthread.php?t=2574647
I know there's a dedicated SuperSU thread but being a newbie on this forum I cannot post there.
I have Teclast P78HD tablet (A31 and Android 4.4.2) which I have rooted using Kingo. There is no custom recovery available for this model, AFAIK, so zip option is out of question I think. Kingo installed SuperSU 1.9.1 which does work, but as Play offered an update I accepted it, got 2.0.1. A big mistake.
The system still works, it prompts to grant root access when an app needs it. But I cannot run the SuperSU app anymore, it asks if I want to update. If I select yes after a while it fails and tells to reboot and try again. Which of course gives the same result. Selecting cancel closes the program. Uninstalling the update returns the system back to working 1.9.1. I have tried also Settings / Cleanup / Reinstall and Settings / Cleanup / Switch superuser app but both fail similarily. I also tried to replace the APK in /system/app using ES File Explorer but this method also makes an app to ask for update.
Any ideas how to update SuperSU on this tablet? Maybe I should just forget the problem and use the current one, but it is somewhat old and the changelog lists many, many changes. Plus Play keeps offering an update which is somewhat annoying
Boffortes said:
I know there's a dedicated SuperSU thread but being a newbie on this forum I cannot post there.
I have Teclast P78HD tablet (A31 and Android 4.4.2) which I have rooted using Kingo. There is no custom recovery available for this model, AFAIK, so zip option is out of question I think. Kingo installed SuperSU 1.9.1 which does work, but as Play offered an update I accepted it, got 2.0.1. A big mistake.
The system still works, it prompts to grant root access when an app needs it. But I cannot run the SuperSU app anymore, it asks if I want to update. If I select yes after a while it fails and tells to reboot and try again. Which of course gives the same result. Selecting cancel closes the program. Uninstalling the update returns the system back to working 1.9.1. I have tried also Settings / Cleanup / Reinstall and Settings / Cleanup / Switch superuser app but both fail similarily. I also tried to replace the APK in /system/app using ES File Explorer but this method also makes an app to ask for update.
Any ideas how to update SuperSU on this tablet? Maybe I should just forget the problem and use the current one, but it is somewhat old and the changelog lists many, many changes. Plus Play keeps offering an update which is somewhat annoying
Click to expand...
Click to collapse
uninstall supersu and try this one. some people have issues with supersu and have found superuser to work correctly.
hi, newbie here...
i bought this S8+ (SM-955FD) for my son, flashed latest TWRP, flashed latest stable Jesse's Kernel (Exynos) and rooted usning TWRP the latest Magisk.
am trying to install a monitoring app in this device (mainly to monitor my son) :angel: .
the problem is when ever I give a simple restart (reboot); this app disappears from device !!!!! like its being removed automatically.
what i have done is installed 3C toolbox and granted Root permissions and removed the following:
- device maintenance.
-device security.
-All KNOX.
further more; disabled Google play protect. device is working just fine with better battery life.
now every time a install the app and check that it's working and functioning fine. after a simple restart the app disappears or i can say deleted automatically.
what can delete the app (considering that its a malware)!! even though all security features are removed???!?!?
thanks in advance
This is downloading on my device? Is this going to brick it?
No it's fine. Lots of us received that update the days. I don't see anything new but the performance after the update seems very good.
Sent from my iPhone using Tapatalk
Why would you think it would brick your device?
Did any of the previous updates brick it?
I know the number looks strange - it really should be 5.6.... not 5.3, but that's a mistake on Amazon's end as the "Learn more" link to the User Guide has the correct number.
OP had probably downgraded his tablet to a earlier version of FireOS like I did and installed the play store and nova launcher. I havent used it in a few days but when i got it out today, it said it downloaded and installed 5.3.6.4 on 11/11/18 at 1:16am... which is weird because I had previously used this guide to downgrade to 5.4.0.0 ( https://forum.xda-developers.com/amazon-fire/help/fire-7-2017-7th-gen-downgrade-debloat-t3699937 ) and this "update" seems to have downgraded it even further. But nothing has changed except the version number. Lockscreen ads and all the bloat is still gone and nova is still my launcher, so having the update message appear is very head scratching...
BTW, i did the downgrade to 5.4.0.0 MONTHS ago, and have never seen an update message until today. In fact, if I went into the Device Options and selected System Update, it wouldn't allow me into the setting...it would just kick me back to the home screen. Now it DOES allow me into the setting. Very strange.
5.3.6.4 Update remove root?....
After receiving the 5.3.6.4 update on my HD 10 (11/15/18) -
Lock Screen Ads re-appeared on reboot
Titanium Backup - "no longer finds root" (and in turn, no longer works)
SuperSu - No longer works
Nova Launcher remains in-place oddly enough
I have since theoritically (read on) uninstalled all apps mentioned above and re-rooted via kingoroot and can access a root prompt via ADB (id reflects uid=0(root) gid=0(root) context=u:r:init:s0), however I have been unable to update the binaries for SuperSU despite multiple re-installs and reboots (I'm running the previously working v2.79 btw). Additionally, when I now run a fresh install of Titanium BackUp, all I get is an ongoing "Detecting SU & Busybox..." message onscreeen that leads to no where (I just re-installed BusyBox prior) AND when I run Root Checker, it relects no root as well, despite both kingoroot reflecting root within it's app and my ability to run su via an adb shell on my PC., though please also note that I am unable to run su via a shell/terminal emulater installed on the device ("su: not found").
Thoughts?....thanks in advance for the assist.
Peace.
Hello,
Actually I'm kinda new at root. I used to root phones that weren't too complicated to root, like the Samsung Galaxy W, so I have "pretty basic" rooting knowledge. I successfully rooted my phone this morning. There was no problem but in many modules and rooting applications it was not working properly because the system file was not read/write-able. I haven't been able to find any information, especially for Android 12, despite a lot of research. I was getting errors like "'
Code:
/dev/block/dm-0' is read-only
" and "
Code:
verity cannot be disabled/enabled - USER build
" when trying to grant write permission to the system file via adb. Eventually I came across this post on the forum: https://forum.xda-developers.com/t/fairphone-4-remove-google-apps-microg.4379791/post-86159173
I downloaded "NanoDroid-microG-23.1.2.20210117.zip" from here, then installed via Magisk app.
Actually I didn't know that this module removes Google apps. After I reboot, looks like my phone was completely broken. Not only Google apps, even the launcher crashes. Crash video here. After a while everything crashes, the phone automatically boots into Recovery mode.
I had a backup of Boot before. I first deactivated and then removed the last installed Magisk module via TWRP. I restored the Boot I backed up but the problem still persists. At the moment I have no idea of any solution other than a clean install on the phone but that would be the last thing I want. Is there any other way to solve this?
Thanks in advance.
bitblocksplicer said:
Hello,
Actually I'm kinda new at root. I used to root phones that weren't too complicated to root, like the Samsung Galaxy W, so I have "pretty basic" rooting knowledge. I successfully rooted my phone this morning. There was no problem but in many modules and rooting applications it was not working properly because the system file was not read/write-able. I haven't been able to find any information, especially for Android 12, despite a lot of research. I was getting errors like "'
Code:
/dev/block/dm-0' is read-only
" and "
Code:
verity cannot be disabled/enabled - USER build
" when trying to grant write permission to the system file via adb. Eventually I came across this post on the forum: https://forum.xda-developers.com/t/fairphone-4-remove-google-apps-microg.4379791/post-86159173
I downloaded "NanoDroid-microG-23.1.2.20210117.zip" from here, then installed via Magisk app.
Actually I didn't know that this module removes Google apps. After I reboot, looks like my phone was completely broken. Not only Google apps, even the launcher crashes. Crash video here. After a while everything crashes, the phone automatically boots into Recovery mode.
I had a backup of Boot before. I first deactivated and then removed the last installed Magisk module via TWRP. I restored the Boot I backed up but the problem still persists. At the moment I have no idea of any solution other than a clean install on the phone but that would be the last thing I want. Is there any other way to solve this?
Thanks in advance.
Click to expand...
Click to collapse
Which ROM are you actually running?