In preparation for the impending upgrade to Android 6 Marshmallow, I'm trying an experiment on my Android 5 based Zenfone 2. I'm going to see how annoying it is to give up root. The first thing I did on my first android phone was root it, so I've only every used rooted Android devices.
Prologue:
Root on Android 6 (usually) requires an unlocked bootloader, because root is achieved by modifying the boot image to inject su into the system. That way the system image is left unmodified and can continue to pass dm-verity checks.
At the moment, there does not appear to be anyway on the Zenfone 2 to unlock the Marshmallow beta bootloader, and it also appears to relock any unlocked bootloader. In fact, the droidboot binary in the droidboot.img of the Marshmallow beta contains the strings rm -rf /factory/asuskey and rm -rf /factory/asussignature. droidboot also contains the strings unlock successfully...reboot after 5 seconds and **** Unlock bootloader? **** as well as other strings referring to unlock (droidboot from the .184 Lollipop also has those strings). So, my hope is that there is a simple way to unlock the bootloader, which will be revealed by Asus, or discovered by somebody.
My thought is that worst case those of us who want root will use an unlockable Lollipop bootloader with a Cyanogenmod 13.1 based ROM created with updates from the Asus Marshmallow source code.
Experiment:
I've removed Xposed and SuperSU from my phone. Making it stock Android 5. I'm documenting here the functionality that I lose. The first goal is for my own amusement to keep a log of what I'm giving up.
The second goal, and probably the major one, is to solicit suggestions on what can be done to replace the functionality I'm losing.
What I'm giving up:
AdAway - No system wide ad blocking. Firefox with uBlock Origin should cover blocking ads on the web. I usually buy apps I use frequently, but I'll have to see which ones are annoying with ads. I'm aware of the VPN based ad blocking methods, but I'll have to wait and see if it comes to that.
AFWall+ - Using root to improve security... I mostly use this to prevent some apps from using mobile data, and to prevent some apps from gaining network access at all.
BetterBatteryStatus - It works in non-root mode, but not as well.
BusyBox - Without root, there isn't much need for this anyway.
Cryptfs Password - Once again, security is harmed by removing root. This allowed my encryption pin to be different (and much longer) than my screen lock pin. I don't want to type 10 digits to unlock my screen, but it's fine for booting.
Greenify - This definitely kept some aps in check, but perhaps Asus' Auto-Start Manager will be able to replace it.
GSam Battery Monitor - Like BetterBatteryStatus, this had a root component to provide more information.
Kernel Adiutor - For some reason my phone seemed to only go to 1.8ghz instead of 2.3ghz, so I used this to fix it.
Linux Deploy - I never used the Linux chroot image for much, but it was a cute toy.
Secure Settings - This let tasker automate adjusting some things which require root to change.
Titanium Backup - This is a massive loss in functionality. Simply having backups is tremendously important. The ability to freeze unwanted system apps is also nice. I can reload many of my apps from Google, but not all of them bother to save their settings in the Google backup. Ohh, the bloat!
Trimmer (fstrim) - Probably not really necessary, anyway.
Xposed
Amplify - It saved me lots of wakeups, but I don't know if it really did much to increase battery life.
Fix Lollipop Memory Leak - I don't know if this did anything, either.
GravityBox [LP] - I didn't tweak too much, but what I did change was really useful.
NetStrength - I like replacing my wifi bars with useful information.
ProtectMyPrivacy - The permission settings in Marshmallow would make this obsolete anyway.
YouTube AdAway - Nice, but not required.
What I'm gaining:
Android Pay - I guess I can play with this now.
AFWall+ - Using root to improve security... I mostly use this to prevent some apps from using mobile data, and to prevent some apps from gaining network access at all.
Click to expand...
Click to collapse
Asus has integrated a firewall iptables recent months.
Asus mobile manager -> User Data -> Restrict (bottom of screen)
For the rest, no root is to accept to take along twice monitoring tools of an advertising billboard.
Keep in mind that Google is an advertising agency that is desperate to earn money, including harassment to get the maximum information.
Its purpose, despite what he claims, is not to improve people's lives, but his bank account.
Android is a disguised tools for Google, not for the people who is a commodity to be exploited.
I'm gonna miss Adaway and Afwall+ the most. Afwall+ is much better than the Asus built in firewall. You can disable net access by default for newly installed app. You are notified to set firewall rules when you install an app. You can filter apps to be set. If only Asus could provide a such a bunch of feature for their firewall, I won't miss root so much.
Sent from my Asus Zenfone 2 using XDA Labs
IDEDALE said:
Asus has integrated a firewall iptables recent months.
Asus mobile manager -> User Data -> Restrict (bottom of screen)
Click to expand...
Click to collapse
Thanks for the info about the functionality in Asus Mobile Manager, I didn't know that.
As far as Adaway goes, try this https://block-this.com
Sent from my ASUS_Z00A using Tapatalk
IDEDALE said:
Asus has integrated a firewall iptables recent months.
Asus mobile manager -> User Data -> Restrict (bottom of screen)
For the rest, no root is to accept to take along twice monitoring tools of an advertising billboard.
Keep in mind that Google is an advertising agency that is desperate to earn money, including harassment to get the maximum information.
Its purpose, despite what he claims, is not to improve people's lives, but his bank account.
Android is a disguised tools for Google, not for the people who is a commodity to be exploited.
Click to expand...
Click to collapse
Agree with most of that... unfortunately the ASUS mobile manager "firewall" doesn't work any more on the current marshmallow beta.
It's still there, but it seems not to work for blocking apps.
The new app permission system in MM may be used to prevent apps from connecting around, in theory at least, but I'm not sure how effective that is.
This phone without root absolutely sucks. There's a thread on the ASUS forum, guy has links to pre rooted system images but I haven't tried it.
http://www.asus.com/zentalk/thread-39487-1-1.html
Sent from my ASUS_Z00AD using XDA-Developers mobile app
The thread mentioned was opened in September '15... Didn't try downloading the files but can't imagine that there's a pre-rooted file out there already. Somebody would have known and told us, I guess
If anyone tried and it works, may you leave a line!
sent from my Binford Z00AD using tapatalk
nfc expert said:
if you want stop ad without root, you can try this : https://block-this.com/
Click to expand...
Click to collapse
kenbo111 said:
As far as Adaway goes, try this https://block-this.com
Click to expand...
Click to collapse
There are several other VPN based ad blockers as well. AdClear, AdGuard, and I think some more.
I played with some of them when they first started coming out, but always returned to the host file based blocker, because it was easy and worked fine with root. I think the phone has plenty of RAM and CPU to run these VPN ones, but I haven't been annoyed to try them again. So far uBlock Origin in Firefox has been fine. In the almost two days since unrooting I've used one app which shows me ads.
IDEDALE said:
Asus has integrated a firewall iptables recent months.
Asus mobile manager -> User Data -> Restrict (bottom of screen)
Click to expand...
Click to collapse
Thanks for the tip, I didn't know about it. This was easy enough to setup, even if it doesn't have as many features as AFWall+. I haven't tested to make sure it works.
My idea to get root on Asus' Marshmallow release is to install just the system, but keep the unlocked bootloader and ifwi from Lollipop. It should be easy enough to modify the updater script to only flash the system and boot image, while leaving the bootloader and ifwi alone. I don't know if that will work, or if the system will crash when it finds an old ifwi, or if the bootloader will fail to load the new system. With an unlocked bootloader, root is trivial.
As long as the bootloader is in place, it should be easy to recover from a broken system.
Don't take my word for it though, these are just ideas, and I'm not ready to try them yet. My warranty is over at the end of the month, so I'll unlock my bootloader then.
Related
I don't know how I missed this!
Android Rootkit is just a phone call away
Now, hopefully after Defcon, the details will go public, and since the Rogers Dream won't be patched (that's what you get for never giving us OTA updates), I'm sure it'll be adapted into a local exploit as well.
"This could be done by building the rootkit into a rogue application sold via the Android Market, or by exploiting a new, unpatched bug in Android's Linux kernel that could allow the program to be installed."
** actually, it would require BOTH.
And at this time, there ARE NO known kernel bugs affecting Android's kernel.
The old "1-click-root" app demonstrated this kind of thing, and DID exploit a kernel bug, which HAS SINCE BEEN PATCHED.
This thing can ONLY hurt a ROOTED phone, and even then, the su app will pop up saying "gee, this app wants root, should we let him?"
lbcoder said:
"This could be done by building the rootkit into a rogue application sold via the Android Market, or by exploiting a new, unpatched bug in Android's Linux kernel that could allow the program to be installed."
** actually, it would require BOTH.
And at this time, there ARE NO known kernel bugs affecting Android's kernel.
The old "1-click-root" app demonstrated this kind of thing, and DID exploit a kernel bug, which HAS SINCE BEEN PATCHED.
This thing can ONLY hurt a ROOTED phone, and even then, the su app will pop up saying "gee, this app wants root, should we let him?"
Click to expand...
Click to collapse
I believe flashrec exploited the sock_sendpage() glitch. It may be possible that they have discovered a new exploit similar to the sock_sendpage, and simply haven't made it public. Remember, that one was present since 2001. It can be built into any apk, and instead of giving a shell root access, it can run background processes with a superuser permission.
Just food for thought.
Which will easily be fixed with a wipe and reflash if it -does- happen.
...right?
r3s-rt said:
Which will easily be fixed with a wipe and reflash if it -does- happen.
...right?
Click to expand...
Click to collapse
Yes, as long as the rootkit doesn't block fastboot and ADB
I'm pretty sure it can't stop you from getting to recovery, though? Either way - this would be just more of a pain in the ass for me.
However, some people are genius enough to store crucial information on their phone such as S.S. numbers and credit card numbers, and people are dumb enough to install this and give it su permissions. :/
Ok, they keep updating and breaking root. I hear droidwall will block it.
But what is the name I should be blocking?
Or is there a better way to stop auto updating?
Delete OTACERTS.zip in system/etc/security. You must enable r/w and have root.
When I did It, it downloaded the update in front of me but didn't update. Then I deleted the update. Now i'm still on 6.2.1 and Loving It.
Molinari said:
Ok, they keep updating and breaking root. I hear droidwall will block it.
But what is the name I should be blocking?
Or is there a better way to stop auto updating?
Click to expand...
Click to collapse
I did the otacerts.zip thing mentioned above (moved to sdcard and renamed to otacerts.bak).
However, just to be safe I am also using droidwall. With droidwall, I started out by blocking everything (default) and then unblocked things when they would not work (use the log to see what is being blocked). Be sure to actually enable the blocking and the logs (they are off by default). Some things you can be unblocked ahead of time like Market and Browser. The only potential issue with using droidblocker is that whatever is used for the OTA update might also be used by something else that needs to be unblocked.
mark_a_l said:
I did the otacerts.zip thing mentioned above (moved to sdcard and renamed to otacerts.bak).
However, just to be safe I am also using droidwall. With droidwall, I started out by blocking everything (default) and then unblocked things when they would not work (use the log to see what is being blocked). Be sure to actually enable the blocking and the logs (they are off by default). Some things you can be unblocked ahead of time like Market and Browser. The only potential issue with using droidblocker is that whatever is used for the OTA update might also be used by something else that needs to be unblocked.
Click to expand...
Click to collapse
Droidwall Doesnt work, I tried that on the 6.1 to 6.2 update because I did not want to risk a potential update. That was before we knew of the ota updates.
iroctheworld said:
Droidwall Doesnt work, I tried that on the 6.1 to 6.2 update because I did not want to risk a potential update. That was before we knew of the ota updates.
Click to expand...
Click to collapse
What were you blocking? I've only got about 6 things on my white list (not blocked). Half are market related. In any case even if it doesn't work for OTA updates, I find some apps to be a bit too 'chatty' (looking at the logs). So it does work at blocking 'unnecessary' wifi traffic.
Thanks for the rename tip!
I am still avoiding the 6.2.2 update (only time can tell, last time mine was updated about 1 week after the first posting about forced updates ...)
I am running the rooted version of 6.2.1. I flashed this after losing root from the 6.2.1 forced update.
This time I only did two "mods" for protection -
(1) un-register from Amazon (actually I never register during ROM installation)
(2) use Droidwall
I dunno which one will make me survive the forced update, but I suspect it may / will be #(1).
I only allow a few things to go through Droidwall, most of them are 3rd party apps' names. The only two additional processes necessary for normal functions are:
(1) downloads, media storage, DRM protected content storage, download manager (needed for Market downloads)
(2) search (for Google search)
The one I always worry about in Droidwall is obviously #(1). I certainly do not let things like Amazon device client platform (ADCP) to go through!
This is just my Droidwall setup. People using other apps may need to allow other Android processes through therefore I cannot guarantee Amazon update won't sneak through that way.
I only know about the otacerts.zip when I revisited the forum yesterday afte reading elsewhere about the new OTA update. This time I won't modify this file on purpose.
(fingers crossed for me, I am not out of the woods yet)
P.S. Feb 2nd and I am still clean, looks like I dodged it!
1. Is it possible
2. Do all users get root access? I assume SU would have to be installed for each user, if root access is desired, correct?
3. Does it cause issues?
4. Does the ADB Backup & Restore backup and restore ALL users?
....Anything I'm missing?
ShadowOf said:
1. Is it possible
2. Do all users get root access? I assume SU would have to be installed for each user, if root access is desired, correct?
3. Does it cause issues?
4. Does the ADB Backup & Restore backup and restore ALL users?
....Anything I'm missing?
Click to expand...
Click to collapse
In the words of Chainfire, author of SuperSU, as it pertains to SuperSU 0.98 and 0.99:
Chainfire said:
Preliminary update for Android 4.2's multi-user capabilities.
Only the main user can run the UI and gain root access.
Secondary user's apps will not be granted root, nor can
those users change SuperSU configuration.
This is all temporary. Proper multi-user support is being
worked on.
Note that if a non-user process (like ADB shell) needs to
prompt for root, that prompt will always appear on the
MAIN user's screen !
Click to expand...
Click to collapse
Source
Thanks that answers 1 & 2.
3. Any issues multi users are seeing after root?
4. Will ADB Backup & Restore handle my three current users?
Sent from my Nexus 7 using XDA Premium HD app
ShadowOf said:
Thanks that answers 1 & 2.
3. Any issues multi users are seeing after root?
4. Will ADB Backup & Restore handle my three current users?
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
I should have mentioned that my N7 is rooted with multiple users and I have not run in to any issues. I can't comment on the backup, however.
ShadowOf said:
Thanks that answers 1 & 2.
3. Any issues multi users are seeing after root?
4. Will ADB Backup & Restore handle my three current users?
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
I have not had any issues with root for main "owner" user. But as stated other users currently do not have root access.
Backup? Don't know yet?
Other users currently do not have access to all apps that the owner has access to. Example. Google wallet only works with owner. Google Talk only with Owner.
So I really hope that once they figure out how to get root to all users... than all users can use all apps.
Google has made a one stop forward.... but long ways to go on multi user system. IMO
Jack$on said:
So I really hope that once they figure out how to get root to all users... than all users can use all apps.
Google has made a one stop forward.... but long ways to go on multi user system. IMO
Click to expand...
Click to collapse
Completely agree on that one. Asked me to set up google wallet again for the second user (I had entered a different gmail id for the second user).
Had to install titanium backup separately for both the users. And apps installed for one user was not accessible to the other!! (from within titanium backup.)
However as the owner, I could see all the apps from under 'manage apps'. (Not visible from the normal drawer.) From manage apps, I can also see option to 'un-install for all users'.
As a owner, I wish, I could also install apps and control other user..
I have rooted my Nexus 7 in order to be able to use USB storage. It works fine-- I use "USB MassStrorage Watcher OTG" and can access my external 32GB Stick.
However, I added a second user (my Wife) and although I have use appshare to share all applications, I cannot read the USB stick when under her user name because it requires a rooted device and a second user system sees a non-rooted device.
The problem lies that Android N7 4.2.1 - does not have a facility to have a shared directory - so everything is hidden from one user to another: I had a plan that I could share books via the USB Stick and not waste the directories and memory space - but because the second user cannot access the USB stick it does not work like I planned.
Does anyone have a solution to:
1. Extend Root access to a second user
2. Create a shared directory that both (or multi) users can access?
3. Have USB access app that does not require root?
I am a first time Android user and the restrictions placed on the use of this device (Android in general) are pretty ridiculous - they make no sense!
Why do they (Google) want to cripple their own device? If the USB access is possible from hardware standpoint - why the intentionally block it and not make it part of the OS?
Why not allow shared directories ? I still copy from one user to another using computer - but it is convoluted and time/memory waste.
Hope there are good solutions out there that someone could direct me to.
Best regards
Vladimir
I tried Superuser 3.3 on my Nexus 7 but didn't work at least with cerberus. It just denies the root request
mjckt said:
I tried Superuser 3.3 on my Nexus 7 but didn't work at least with cerberus. It just denies the root request
Click to expand...
Click to collapse
I just tried that and it worked fine for me. I went into the prefrences and changed the multi user setting to user controlled and it worked just fine.
RobertsDF said:
I just tried that and it worked fine for me. I went into the prefrences and changed the multi user setting to user controlled and it worked just fine.
Click to expand...
Click to collapse
Thanks for the tip, I will try it myself
Sent from Droid
apologies for reviving a thread.
But I managed to get the multiple user working with SuperSU but not superuser (on 4.3)
The problem I have is for some reason every time I install SuperSU although it works fine, It stops App Ops (Permissions) from working.
and because I really like to use them (instead of a third party permission tool) I'd like to get superuser.
Any ideas?
** DISCLAIMER: I AM NOT A DEVELOPER. I DO THIS AS A HOBBY AND SHARE MY FINDINGS IN CASE SOMEONE ELSE FINDS THEM USEFUL. **
** THIS WORKED ON MY DEVICE BUT IT MAY NOT WORK ON YOURS. APPLY AT YOUR OWN RISK **** These scripts are written for Kitkat. Do not use on Lollipop. ** What is new (9/7/2014)
Version 4 provides more Samsung bloat removal, Google bloat removal, and as a bonus it can disable the power on sound.
Background
Samsung has a program running on most of its devices that pushes "Security Updates" onto the device. If you make the mistake of accepting this security update, even after you root your tablet, it will patch the hole and you will never be able to use towelroot or any other know exploit as of June 2014 to root your it again. So this must be immediately disabled after a successful rooting.
Your tablet is also equipped with Knox. One component of Knox is in the bootloader and checks the integrity of the recovery and kernel. If it sees anything has changed at that level it trips the knox flag immediately, which is irreversible. That component can almost never be touched. The second component runs when the OS is up and running and its main task is to monitor the activities of the apps in your system and shut them down if they act "suspiciously". When you are rooted and install SuperSU, this element of Knox keeps detecting the background root activities and shuts them down and gives you warnings. There is therefore a high level of risk there if you let root and knox exist concurrently. So after rooting, this second component of Knox should normally be disabled.
Finally, there are useless junk apps that most of us agree Samsung should have never shipped with the tablet, or even if they are useful we want them gone to get a better battery life.
I will call all of the above (updaters, Knox, and useles junk) bloatware. The scripts attached here can disable or enable the bloatware on your tablet, which comes in handy if you do not have Titanium Backup Pro to freeze or remove bloatware. And since someone will ask at some point, no, it won't trip your Knox!
Please read below and understand what this script disables before you use it. There may be an app on the list that you may actually want to keep.
Requirements:
Rooted Samsung Note Pro 12.2, SM-P905 international model.
Android Terminal Emulator: https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=en
The international version (P905) is tested with baseband P905XXUANA7, build P905XXUANC3 .
The ATT version (P907A) is tested with build KOT49H.P907AUCU1AND7 (thanks to @gerard0986 for testing the script)
Makes sure you download the version that is suitable for your tablet. It may work to varying extents for other models and firmwares.You try and tell me
If you are using models other than P905 or P907A, I can make a new script for you if you provide me with a "ls -R -l" dump of your /system, or even better, if you post your firmware somewhere online.
Download link:
Attached below
Instructions:
Generally speaking, you should always have a Nandroid backup before trying anything new. Also have a flashable ROM handy. I am not responsible if you brick your device while using these scripts.
To debloat:
1- Unzip the attachment and copy debloat.sh to your phone at /sdcard
2- Run the terminal emulator and type the following:
su
cd /sdcard
sh debloat.sh3- Choose what you want to disable, or exit.
4- If you choose not to exit, the code does its thing and reboots your tablet. The bloat is gone now
To restore the bloatware:
1- Unzip the attachment and copy enbloat.sh to your phone at /sdcard
2- Run the terminal emulator and type the following:
su
cd /sdcard
sh enbloat.sh3- The code will warn you:
Are you sure you want to restore the security/firmware/software updaters, and Knox?
They may immediately patch your system and make the existing root methods impossible to apply.
Then you can choose what to enable, or just exit.
4- If you choose not to exit, the code does its thing and reboots your tablet. The bloat is back now
Note that while running the debloat script you may get force-closing popups. This is normal; after all you are disabling these applications!
Limitations:
If you have previously removed bloat using other means this script CANNOT recover it for you. enbloat.sh can only restore what debloat.sh has disabled.
If you have debloated using an older version of this code and you want to try a newer version of it, first use enbloat from the older version to return everything to the original configuration and then use the newer version.
When you are restoring the bloat, it is best to enable "airplane mode" so that your tablet does not try to patch your system with a security update without your knowledge. You can disable the airplane mode after you debloat again.
Change log
V5:
Typos fixed.
=============
V4:
Option to disable all Google services except Youtube, search, map, and TTS
Option to disable/enable Power on sound
=============
V3:
The scripts give separate options to enable/disable these groups of bloatware:
1- Updater/knox
Firmware Upgrader, Local FOTA, Security Manager, FOTA Client, Security Update Client, Samsung Push Client, Samsung Software Update, Knox and its related apps
2- Samsung bloat
ANT, Blurb, ELM Agent, Samsung Apps apk and widget, Job Manager, Samsung cloud backup files, Context Provider, S Finder, S Voice, Samsung Account Service, aaIgnite_1.5.15_singtel, weplay_1.3.162, PCWClientS18
3- Other bloatware
Accuweather, Bloomberg, Dropbox, Evernote, Flipboard, NY Times, Remote PC, ,Travel Service, Twitter, WebEx, Line, Pinboard Scratch book, SNS, eMeeting
=============
V2:
The scripts give options to enable/disable updater/knox and other bloatware separately.
Added these to the disable list of V1:
SecurityManagerService, aaIgnite_1.5.15_singtel, weplay_1.3.162
=============
V1:
The script disables the following:
Firmware Upgrader, Local FOTA, FOTA Client, Security Update Client, Samsung Push Client, Samsung Software Update, Knox and related apps, ANT, Blurb, ELM Agent, Remote PC, Samsung Apps apk and widget,Travel Service, Twitter, WebEx, Line, Samsung cloud backup files
PCWClientS18, Scratch book, S Finder, SNS, Samsung Account, eMeeting
Would this work for the T-900 version too?
What do I need to get the info required to get a script made for the sm-p907a model? I read above post but the list of things required were above my head lol.
Sent from my SAMSUNG-SM-P907A using XDA Free mobile app
iNiREALiZED said:
What do I need to get the info required to get a script made for the sm-p907a model? I read above post but the list of things required were above my head lol.
Sent from my SAMSUNG-SM-P907A using XDA Free mobile app
Click to expand...
Click to collapse
1- What is your firmware version?
2- Open the terminal emulator and type the following commands in there:
su
cd /system
ls -R -l > /sdcard/sysdump.txt
Then pm the file sysdump.txt which is saved on your sdcard to me.
thank you
Thank you najoor for the neat script, it executed successfully on my sm-p905 (UANE1 rom) & removed the useless software, it saves a lot of time removing them manually.
Nice work
Hope to see a version for the SM-P907 soon.
Rockytop00 said:
Would this work for the T-900 version too?
Click to expand...
Click to collapse
I think the only existing models are SM-P900, SM-P905, SM-P907A and SM-P905V. I don't know what T-900 is.
If you are referring to model P900 (wifi only) this code may partially work but a lot of files are different between the two models so the outcome is a partial debloat. If you want, you can make a system dump file as I suggested in this post http://forum.xda-developers.com/showpost.php?p=55029414&postcount=5 and send it to me so I can make a custom code for you.
Edit: It appears that T900 is the Tab pro model which is a different device. This thread is for Note pro 12.2 and since I do not own a Tab Pro I cannot answer this question. Perhaps help can be found in the XDA's Tab Pro forum at http://forum.xda-developers.com/galaxy-tab-pro-12-10-8. or try these scripts as they are and see if it works for you.
Hey najoor, Im hoping that you can help me debloat my galaxy tab pro 12.2 sm-t900. I just bought it today and am shocked at the amount of bloatware thats included lol.
Basically I want everything removing that I can install through googleplay, leave the default browser.
Here is the log that you mentioned to the other guy also:-
View attachment sysdump.txt
Ill try to pm it also, really hope you can help out.
Pixel
Debloat method
I used this method but i accidentally uninstalled all google services, and google play store was apart of that, is that normal? And if it is are there ways to get it back?
stockerrodney said:
I used this method but i accidentally uninstalled all google services, and google play store was apart of that, is that normal? And if it is are there ways to get it back?
Click to expand...
Click to collapse
Yes, that is part of bloat removal. To get Google bloat back run the enbloat.sh script and hit y when it prompts you about restoring Google bloat.
stockerrodney said:
I used this method but i accidentally uninstalled all google services, and google play store was apart of that, is that normal? And if it is are there ways to get it back?
Click to expand...
Click to collapse
najoor said:
Yes, that is part of bloat removal. To get Google bloat back run the enbloat.sh script and hit y when it prompts you about restoring Google bloat.
Click to expand...
Click to collapse
If i do the enbloat method will i have to reinstall knox ? Or will i still be able to keep it off?
When you use the enbloat.sh you only restore the stuff you choose. You don't have to restore everything. In your case you leave knox and other things out and only answer yes when it asks you if you want Google bloat to be restored.
The script is very user friendly. Just run it and follow the instruction. And just to give you peace of mind, these scripts do not delete anything from your system permanently so don't worry about breaking your system.
Any chance you could add the option to remove individual items?
http://forum.xda-developers.com/android/software/debloater-remove-carrier-bloat-t2998294
Debloat v5.0 removed Scrapbook from Air Command
The debloat worked fine but the Scrapbook app in Air Command is now showing error "no application found to handle this actions".
Please advise.
mojoe said:
The debloat worked fine but the Scrapbook app in Air Command is now showing error "no application found to handle this actions".
Please advise.
Click to expand...
Click to collapse
Removing apps is what a debloating script does. If you want your app back just run the enbloat script. All the instruction you need is provided in the original post.
najoor said:
Removing apps is what a debloating script does. If you want your app back just run the enbloat script. All the instruction you need is provided in the original post.
Click to expand...
Click to collapse
Appreciated. I wanted to debloat but did not expect the scrapbook app to be debloated. Is there any way that I can retrieve this one app, without the rest of the garbage that will return if I "enbloat".
I recall finding the app the last time and renaming from .bak to .apk and it worked.
Can you tell me where to find the apk.
mojoe said:
Appreciated. I wanted to debloat but did not expect the scrapbook app to be debloated. Is there any way that I can retrieve this one app, without the rest of the garbage that will return if I "enbloat".
I recall finding the app the last time and renaming from .bak to .apk and it worked.
Can you tell me where to find the apk.
Click to expand...
Click to collapse
The app is either in /system/app or /system/priv-app. Rename app.apk.bac and app.odex.bac if it exists to app.apk and app.odex and reboot. I don't remember exactly which app is the one you need.
najoor said:
The app is either in /system/app or /system/priv-app. Rename app.apk.bac and app.odex.bac if it exists to app.apk and app.odex and reboot. I don't remember exactly which app is the one you need.
Click to expand...
Click to collapse
Thank you. I will return with the name once I find it.
Are you someone who just got their Fire TV rooted and don't know exactly what you can do with it being rooted? Or maybe you haven't rooted yet because you are unsure of what you can do with it rooted? Well hopefully i can shed some light on this with a little guide on things to do, along with some tips and tricks.
First let me get started by saying never forget to make a backup of your Fire TV via TWRP before making changes or tweaks. This is not to freak you out or disparage its just good practice ii have learned in rooting devices. I will cover TWRP later.
One of the best things to come along in the rooting world of android is Xposed installer. In short Xposed is a framework apk that allows users to modify/ customize their devices. This is not done by Xposed Installer per say but the modules that you download with in Xposed installer. So i will show how to install it, how to use and modules that will be beneficial use for Fire TV fyi mouse is need to navigate Xposed.
Xposed installation
1. We need to download the following BusyBox a program that most rooted apps are dependent on here Xposed Installer v3.1.5 here along with Xposed Framework x89 sdk22 arm64 here
2. Install BusyBox however you install side loaded apks. Open BusyBox and click the install button on bottom right. On SU prompt screen grant root access. As you should for root apps you install.
3. Install Xposed Installer, there is no need to open after install because without Xposed Framework installed it doesnt work.
4 Place the Xposed v89 zip onto Fire TV internal or external storage is your choice just remember where so you can point TWRP to it.
5 Reboot into TWRP recovery, choose install, point TWRP to the Xposed zip and on right side of options choose install zip. Let TWRP run its script when it says complete simply reboot and voila Xposed is installed. NOTE it is NORMAL for the first boot to take 10 min after Xposed is installed.
Xposed Tutorial and Modules
Open Xposed installer on be careful screen prompt click box to don't show again and ok. The 3 line icon on top left is menu button. Module option is where you can see and activate modules you install. Download option is where we search for and install modules. After you download a module Fire TV will prompt you to install. Note modules wont work until activated and a reboot.
Modules i find beneficial and know are SAFE are the followingBoot Manager- this allows for you to choose what apps start on boot.
RootCloak- this is designed to hide root app detection. Im assuming it still will hide root but could be wrong worth shot right
Xposed Edge- this is the FUN one that allows a fair share customs tweaks. My fav is remapping of remote buttons ie home button goes to alternative launcher, double tap home opens netflix. Which is great for 3rd party remotes that have a lot of buttons. NOTE There is a pro version as well Note- whenever you make changes in edge you may have to reboot for changes to effect.
DISCLAIMER be careful some modules may cause problems like bootloop and worse so research before you install modules to see if they are compatible
Other Apps
These are apps recommended or useful for rooted devices and for Fire TV useADBLink-allows you connect PC t to Fire TV via adb can install apks, push/pull files, run adb shell.
Easy Fire Tools- Android app that connects to Fire TV via adb can install apps from your android device onto Fire TV, transfer files and other features.
Root Explorer- these apps allow you to manage files but also a way to install side loaded apps, find one that is root friendly so you can access system folders if ever needed.
AdBlocker- we all know why we want one for all my rooted phones always been partial to adaway.
Alternative Home Launcher- who does like Fire TV launcher, really Karen of course you would!
TV App Repo and APK Editor- For those who do use alternative launcher i mention these because TV App Repo allows you to make bookmarks into apks. APK Editor to change the icon and name of TVApp Repo apks because the names and icons are generic.
TWRP
Finally the benefits and how to use TWRP. This allows users to make a backup images of device and ability to restore it when **** goes wrong. You can also do a factory reset.
Backup- after you choose backup from main screen choose select storage and choose storage then click swipe to backup. These can take a while to do seemed like 20 mins or so. Whatever storage you chose will be the default storage until you change it. Note- I have a backup image and its size is 4.5gb so id recommend you need some sort of external storage for these. If there is not enough space backup can not be performed.
Restore- performed same way as backup.
Factory Reset- Just wanted to mention don't forget if you do this and have a backup image on Fire TV internal storage you will lose it.
Hope this helps out
@g422
Thanks for the write up!!!
To be honest, the benefits of rooting appear to be somewhat underwhelming, at least, for the Fire TV. Not a single killer feature/application ...
I do know that it is more convenient to have root than not, but appears to be in pretty subtle ways.
My main use is between SmartYouTubeTV, and Netflix. If I fumble through the Amazon launcher, I am there, and life is good!
Am I missing something?
bibikalka said:
Am I missing something?
Click to expand...
Click to collapse
Yes, you didn't read the OP He gives many examples of use for root, if those aren't valuable to you, then root isn't for you.
ldeveraux said:
Yes, you didn't read the OP He gives many examples of use for root, if those aren't valuable to you, then root isn't for you.
Click to expand...
Click to collapse
Hmm, just for the record, pretty much every tablet or phone (except a couple of real cheap deals) I have in my household are rooted! So I do see good value in root on those devices.
It's just that I struggle with root utility on Fire TV devices. As in - "why bother?"
I see that the OP likes Xposed Edge for button remapping, so if that's your cup of tea, that's a killer feature to get root for. I myself religiously correct Chrome look on tablets using Xposed/App Settings (link), which very few others seem to care about. But I want to see more of these killer features for Fire TV! Suggestions?
Btw, I am not being adversarial or critical, just very curious. Which itch are people scratching with root on Fire TV???
bibikalka said:
Hmm, just for the record, pretty much every tablet or phone (except a couple of real cheap deals) I have in my household are rooted! So I do see good value in root on those devices.
It's just that I struggle with root utility on Fire TV devices. As in - "why bother?"
I see that the OP likes Xposed Edge for button remapping, so if that's your cup of tea, that's a killer feature to get root for. I myself religiously correct Chrome look on tablets using Xposed/App Settings (link), which very few others seem to care about. But I want to see more of these killer features for Fire TV! Suggestions?
Btw, I am not being adversarial or critical, just very curious. Which itch are people scratching with root on Fire TV???
Click to expand...
Click to collapse
I sort of see your point, but I think the root version of Mouse Toggle works, while the non-root doesn't. At least that's been my experience. Also, can you block updates without root?
I took no offense to your comments bibikalka. I am inclined to agree that there is a limit of what to do with rooted fire tv especially compared to a phone or tablet. I started this thread to give back to xda who has kept my multiple devices over years rooted. Thread was also done in hopes of getting ideas to do and/or sharing of apps that can be helpful especially now that rooting is allowed for the general masses just not those who were able to jump on board early.
ldeveraux said:
I sort of see your point, but I think the root version of Mouse Toggle works, while the non-root doesn't. At least that's been my experience. Also, can you block updates without root?
Click to expand...
Click to collapse
I used mouse toggle without rooted fire tv until i got air mouse remote. Yes you can block updates. If im not mistaken rbox prerooted roms block updates, go to check for system updates and should be stuck on checking for updates. If not go here.
#1 reason I root a fire TV box is so I can use large NTFS drives on the USB port.
Can someone point to me how to fix sd card write permissions. I tried xiinternalsd for xposed but when i open it goes to amazon home screen
g422 said:
I used mouse toggle without rooted fire tv until i got air mouse remote. Yes you can block updates. If im not mistaken rbox prerooted roms block updates, go to check for system updates and should be stuck on checking for updates. If not go here.
Click to expand...
Click to collapse
Right, so blocking updates only when rooted.
ldeveraux said:
Right, so blocking updates only when rooted.
Click to expand...
Click to collapse
yeah i just re read what ya posted i see what ya meant
Imho top reasons for it are Xposed Edge Pro, ad blocking via AdAway (if you use the browser) and finally, the updates issue. While unlikely, it's not impossible for Amazon to get crackin and stop the use of certain third-party apps (NIMH is a giveaway)
Edit: forgot one important one, "debloating" the OS, whether by blocking the startup or disabling packages you don't want/need to give more cpu and memory to apps you do
Without root access, it's Amazon's device; with root access, it's now your device.
g422 said:
I used mouse toggle without rooted fire tv until i got air mouse remote. Yes you can block updates. If im not mistaken rbox prerooted roms block updates, go to check for system updates and should be stuck on checking for updates. If not go here.
Click to expand...
Click to collapse
ldeveraux said:
Right, so blocking updates only when rooted.
Click to expand...
Click to collapse
g422 said:
yeah i just re read what ya posted i see what ya meant
Click to expand...
Click to collapse
For a while, updates could be blocked without root, but Amazon fixed that hole:
https://forum.xda-developers.com/fire-tv/general/disable-ota-fire-stick-t3667978
But! You want to block updates so you don't lose root, so it's a bit circular. If you don't have root, you don't care, and just update as per Amazon otas. Btw, I do have updates blocked on my fire sticks
Anyway, please keep the conversation going! We should develop a good set of must have features which are only available via root.
The main reason I root now is to debloat. Go as barebones as possible in order to improve performance. I kill all possible services that are absolutely unnecessary. I've removed Amazons GUI and use Appstarter. I just like a clean fast experience.
Thanks for this but u all do know u can connect to a PC wirelessly via adb without root. It's the only way I have ever added apps to my stick. Find your sticks individual ip. Open terminal on a pc, adb connect ipaddress. Then adb devices, a prompt will pop like on your phone asking to allow device or not. Click always or yes whatever. Then u do adb install draganddropwhateverapphere. Loads up in seconds depending on apk size. U can even use your phone if u have the adb platform tools magisk module installed on your phone. I install apps to my stick from my OnePlus 6t
fullofhell said:
Thanks for this but u all do know u can connect to a PC wirelessly via adb without root. It's the only way I have ever added apps to my stick. Find your sticks individual ip. Open terminal on a pc, adb connect ipaddress. Then adb devices, a prompt will pop like on your phone asking to allow device or not. Click always or yes whatever. Then u do adb install draganddropwhateverapphere. Loads up in seconds depending on apk size. U can even use your phone if u have the adb platform tools magisk module installed on your phone. I install apps to my stick from my OnePlus 6t
Click to expand...
Click to collapse
Ummm, or you know just use the Apps2Fire app lol. No magisk module or root needed. You're welcome.
JUSTINMARMER said:
Ummm, or you know just use the Apps2Fire app lol. No magisk module or root needed. You're welcome.
Click to expand...
Click to collapse
I am saying I never need root or anything to use adb and install apps wirelessly. I have done this for the past year with NO ROOT. Don't need it for sideloading apps. Adb connect ipaddress, then adb install dragdropapp from PC into terminal. No root or magisk needed. I always have a rooted phone and that's where the magisk module comes in. On a PC u can load them to a stick out of the box.
fullofhell said:
I am saying I never need root or anything to use adb and install apps wirelessly. I have done this for the past year with NO ROOT. Don't need it for sideloading apps. Adb connect ipaddress, then adb install dragdropapp from PC into terminal. No root or magisk needed. I always have a rooted phone and that's where the magisk module comes in. On a PC u can load them to a stick out of the box.
Click to expand...
Click to collapse
Yep, that's exactly what you said before. Not sure why you are repeating it.
JUSTINMARMER said:
Yep, that's exactly what you said before. Not sure why you are repeating it.
Click to expand...
Click to collapse
Cuz u aren't understanding. If u read your comments, then mine, you would see it seems u think I'm saying one would have to have root to use adb install. U do not.
fullofhell said:
Cuz u aren't understanding. If u read your comments, then mine, you would see it seems u think I'm saying one would have to have root to use adb install. U do not.
Click to expand...
Click to collapse
That is 100% incorrect. I see now you have a reading comprehension disability. I can't imagine how hard that must be for you and I empathize.
Obviously root is needed for magisk modules. I suggested an app to help all those without root.
Bless your heart.