Need assistance with SuperSU 2.52, TitaniumBackup, unencryption & WiFi Tethering - Nexus 6P Q&A, Help & Troubleshooting

Hey everyone, i've read through tons of threads and i know root isn't really fully implemented yet. My 6P is arriving today and i was hoping someone could assist with some light modifications.
1) Rooting:
- I am currently on a Nexus 6 running rooted stock marshmallow. It was a pain to get around the "red triangle" on boot. Will using Chainfires modified boot.img get rid of any of the "triangles" on boot?
- With SuperSU 2.52 beta, i had to do something funky by manually going into adb shell to allow r/w on the system. I have some messages saved, but those were fro the N6, not sure if it works the same way on the 6P
2) Does Chainfires boot.img un-encrypt the device? If not, how can i do this?
3) Enable Tethering: After manually adb shell i was able to modify build.prop to add one line of code to enable tethering.
4) TitaniumBackup: is this currently working with the root capabilites we have today? i currently use Google Authenticator & am unsure how to move the app data to a new device without rooting & using TiBu.
i know I'm asking for quite a bit here but i wont be home this weekend and want to take care of everything tonight and unfortunately wont have time to dig through the forums to find all these answers so im hoping one of the smart folks here can assist. If theres an easier way to do any of what i mentioned above please feel free to let me know.
Thanks all!

Related

12/25, what's the current root method?

Hi guys, I just got my Kindle Fire for xmas today. I want to root, but I've been reading the forum and see that a recent OTA update came out and there's been problems. I'm not super computer savy and I really don't want to mess it up. Do I have to wait for a new method to root? If someone wants to take a newb under their wing and tell me what roms etc I should get it would be much appreciated! Just a little overwhelmed with all the posts, not sure where to get consolidated current info.
I haven't even turned it on yet, I'm not sure if I should wait to turn it on, so that if it doesn't have the OTA update it doesn't send through as soon as I turn it on... whatever advice anyone can give would be much appreciated!
For Windows, Use this http://forum.xda-developers.com/showthread.php?t=1399889
Tired that version today works wel..
I haven't turned my Kindle on yet, can I avoid all the complications by somehow keeping it from getting the OTA update when it turns on? (I'm assuming it's not running 6.2.1 yet because that just came out?) I'm afraid to turn it on and I really want to play with it so if someone can let me know that would be great!
And if anyone wants to talk me through it, my screenname is Insidious Lily on aim, I need moral support/help, lol.
Just keep WiFi off until you are done... no issues.
Okay.. I'm a little overwhelmed by all the stuff in that post but I'll do my best. I'm in that IRC chat with another newb if you want to come help us, haha.
And high five, I have a HTC incredible too.
How about current method for Mac users?
ty!
So here's what I did...
(I have a Mac running snow leopard).
I downloaded the KindleFireRootMacLinux folder referenced in the old Mac root thread. This gets adb running on the mac. Use whatever system you need to get adb running on your PC. The command adb on the PC is replaced by ./adb-mac on the Mac.
Then I used the burrito root method and pushed super user to the kindle fire. using the adb commands from terminal.
Finally, I downloaded the google apps folder, installed Googleservicesframework *FIRST* and rebooted.
Then I installled the remainder of the apps EXCEPT market.
Then I used the ES Folder program with root explorer etc enabled to copy the market.apk file to system/app and changed permissions and ran it.
Everything worked fine.
THEN I installed DroidWall to take away the internet communication capabilities of all the Amazon apps (and browser) to try and keep another stealth push from Amazon from breaking root.
Someone else will have to link to the files because I haven't posted enough to include links.
Current root is BurritoRoot http://forum.xda-developers.com/showthread.php?t=1410223
if your particularly lazy Vashypooh's utility has been updated to use it here http://forum.xda-developers.com/showthread.php?t=1399889
I'll just join in to mention something the OP may not realize. Although I'm basically a newbie rooting the KF also, the current root method works with the new update from Amazon, so you don't have to worry about preventing the update to download. In fact, it's probably best to let it update first, otherwise you'll just have to repeat rooting it.
Anyone feel free to correct me if I have that wrong.
leebo said:
I'll just join in to mention something the OP may not realize. Although I'm basically a newbie rooting the KF also, the current root method works with the new update from Amazon, so you don't have to worry about preventing the update to download. In fact, it's probably best to let it update first, otherwise you'll just have to repeat rooting it.
Anyone feel free to correct me if I have that wrong.
Click to expand...
Click to collapse
Yep, but we did discover it doesnt work with 6.0 this morning. Seems what I used wasn't fully introduced until after 6.0

Nexus 7 2012 on 5.1.1 -- any way to root it?

Hi all, kinda new to this whole game.
Couldn't find anything about rooting 5.1.1, only 4.2.2.
If there's no way to root 5.1.1, would you recommend reverting to 4.2.2 and then rooting it? Are there any improvements from using that version over 5.1.1?
Rooting 5.1.1 is the same way as on 4.2.2, unlock bootloader, flash custom recovery and flash super su.
I would recommend you to revert to 4.2.2 if you want a better performance, but if you want to stay on 5.1.1 make sure to use parrotmod to increase performance
Nexus Root Toolkit make it very easy.
thanks for the tips. i was able to root it, but now i'm trying to install the Xposed framework and it's telling me
cp:write error: No space left on device
meanwhile there's about 5 gigs of space since i flashed it down to 5.0 from 5.1.1
interestingly enough, after i root it and try to install busybox, it tells me free space is unavailable for /system/xbin as well as all the other options i try to change it to (/su/xbin, etc).
anyone know if something went wrong at some point?
PlayerThirteen said:
thanks for the tips. i was able to root it, but now i'm trying to install the Xposed framework and it's telling me
cp:write error: No space left on device
meanwhile there's about 5 gigs of space since i flashed it down to 5.0 from 5.1.1
interestingly enough, after i root it and try to install busybox, it tells me free space is unavailable for /system/xbin as well as all the other options i try to change it to (/su/xbin, etc).
anyone know if something went wrong at some point?
Click to expand...
Click to collapse
Your /system partition is full, try to remove something you don't need
iwjosi said:
Your /system partition is full, try to remove something you don't need
Click to expand...
Click to collapse
Thanks for the advice. How do I know what i can remove? If i flashed the tablet multiple times (tried diff versions of android), would that have bloated the /system partition?
Is there something specific i should be careful to leave in?
PlayerThirteen said:
Thanks for the advice. How do I know what i can remove? If i flashed the tablet multiple times (tried diff versions of android), would that have bloated the /system partition?
Is there something specific i should be careful to leave in?
Click to expand...
Click to collapse
you can remove google apps like youtube, hangout, g+ etc
anyone know if the play store can detect that a device is rooted, and prevent pokemon go from showing up in the store?
or is it just not detecting on my tablet possibly from the model of tablet i have?
i checked the official requirements page and there's nothing 'targeting' specific devices, the device just needs to haev Android 4.4+, but i'm not seeing it in my play store for whatever reason.
(my device is a nexus 7, Android 5.0)
i do recall that, before rooting my device, i'm pretty sure i was able to see and DL pokemon go on this tablet when it was running 5.11 before the root was performed
nvm, i found a site hosting the apk for the app. now just trying to make all the pieces work together on the nexus 7
you need to install Magisk to play pogo on a rooted tablet. magisk will disable the root so pogo will load.
http://forum.xda-developers.com/android/software/mod-magisk-v1-universal-systemless-t3432382
Flash a custom rom and install the nano gapps from http://opengapps.org/ if you want to install more apps.
But I wouldn't recommend it since it lags a lot without parrotmod speeding things up. Use the N7 2013 instead.
Magisk will not install on a 5..1.1 ROM because it needs systemless root and this is availabe only on 6.0 or greater ...
Thanks for the added tips. It's too bad this Magisk program only works on 6.0+.
I've tried everything detailed in this guide, including hiding the root with modules in Xposed, but i can't get the logins i created for PoGo to authenticate. I think i'm going to have to throw in the towel on this one.
AndDiSa said:
Magisk will not install on a 5..1.1 ROM because it needs systemless root and this is availabe only on 6.0 or greater ...
Click to expand...
Click to collapse
you might want to rethink that. It works fine on my 5.1.1, as stated in the magisk post "Magisk supports all the way down to Android 5.0 (SDK 21+) (thanks to the new method and busybox environment)"
---------- Post added at 03:21 AM ---------- Previous post was at 03:01 AM ----------
PlayerThirteen said:
Thanks for the added tips. It's too bad this Magisk program only works on 6.0+.
I've tried everything detailed in this guide, including hiding the root with modules in Xposed, but i can't get the logins i created for PoGo to authenticate. I think i'm going to have to throw in the towel on this one.
Click to expand...
Click to collapse
Don't use xposed, either don't install or disable when you don't need it. Someone mentioned that pogo won't work if xposed was installed, but i didn't think twice about it since mine worked with xposed installed, until today. So today I disabled xposed, then restarted, and it works again.
oh, thanks man. i'll def try it out -- see if i cant get it to work with Magisk. I appreciate you pointing that out
g96818 said:
you might want to rethink that. It works fine on my 5.1.1, as stated in the magisk post "Magisk supports all the way down to Android 5.0 (SDK 21+) (thanks to the new method and busybox environment)"
---------- Post added at 03:21 AM ---------- Previous post was at 03:01 AM ----------
Don't use xposed, either don't install or disable when you don't need it. Someone mentioned that pogo won't work if xposed was installed, but i didn't think twice about it since mine worked with xposed installed, until today. So today I disabled xposed, then restarted, and it works again.
Click to expand...
Click to collapse
Pardon my newb, but this workaround method is what i'm trying to achieve through all this.
In short, rooting, then using Xposed modules to hide the fact that 'mock locations' is enabled and faking my GPS location with it. (we live in a tiny town and want the device location moved to a big city).
Without Xposed installed, is there any alternate way that I can hide from PoGo that mock locations is enabled? Per the method linked, that was the one way to make it work, at time of writing.
Or even better, since the linked method actually didn't work on my device (pogo account 'wouldnt authenticate' -- not sure why but assuming its caused by xposed or some kind of root detection), would you know of a different way to fake my GPS location and hide it from PoGo on a Nexus 7?
Just to clarify, I followed your advice and installed Magisk already.
So I have a Magisk-ready device, just not sure where to take things from here, since I realized my instructions uses Xposed specifically to circumvent PoGo
Help
I'm in the same position.
How to remove thee apps? nexus tab 7 2012 is rooted running 5.1.1
Whic ROM should i use?
PlayerThirteen said:
Pardon my newb, but this workaround method is what i'm trying to achieve through all this.
In short, rooting, then using Xposed modules to hide the fact that 'mock locations' is enabled and faking my GPS location with it. (we live in a tiny town and want the device location moved to a big city).
Without Xposed installed, is there any alternate way that I can hide from PoGo that mock locations is enabled? Per the method linked, that was the one way to make it work, at time of writing.
Or even better, since the linked method actually didn't work on my device (pogo account 'wouldnt authenticate' -- not sure why but assuming its caused by xposed or some kind of root detection), would you know of a different way to fake my GPS location and hide it from PoGo on a Nexus 7?
Click to expand...
Click to collapse
There is another way, but it will disable your ability to use gps . use lucky patcher to install your spoofing app as a system app, then you don't need to enable mock locations and don't need xposed since the xposed modules don't work anyways. after that, install an app called disableservice and disable the 3 locationsharing services in google play service. What this does is prevent your real gps to overwrite your mock gps data.
try at your own risk of being banned
g96818 said:
There is another way, but it will disable your ability to use gps . use lucky patcher to install your spoofing app as a system app, then you don't need to enable mock locations and don't need xposed since the xposed modules don't work anyways. after that, install an app called disableservice and disable the 3 locationsharing services in google play service. What this does is prevent your real gps to overwrite your mock gps data.
try at your own risk of being banned
Click to expand...
Click to collapse
Thanks mate, i'll give it a shot!

[GUIDE] Root/Kernel+ViPER/Dolby+Theme/Mods

Intro
I decided to put together this all-in-one guild compiling all the research and testing I've done. I've seen a lot of the same questions and misunderstandings come up over and over in the various threads, most of which I had myself. I've spent lots of time, since I got my new Google Pixel 2 XL, searching XDA, following all the guides the fine folks here put together, flashing, restoring, testing, etc. I've been using Android since my Google Nexus One, so I've been messing around with all this for quite some time now. The Android community is amazing and I've learned a lot over the years, so it's my turn to hopefully help someone out.
I'll also share some of the caveats, issues and fixes I had to do with this setup. This was all done with a Google Pixel 2 XL on Project Fi with an eSIM & physical SIM, so this guide was written and tested with that, however it should work the same in theory with other carriers, but your results may vary.
NOTE: I am not a developer by any means. I've toyed with creating my own custom ROM, but I'm not a ROM or Kernel developer. I just got really good at using the stuff the other amazing smart people here developed and shared with the community.
NOTE 2: Following these steps WILL wipe your device, so make backups if needed!
Thanks
I would like to give thanks to the following folks for the guides, development and help; @topjohnwu, @nathanchance, @Dees_Troy, @luciusfox, @thedude420, @Quinny899, @airmaxx23, @matt1313, @sharkie405, @Tulsadiver, and @zachman1750. Please forgive me if I forgot to mention you directly as I've gone through many threads and guides at this point. I also thank the community for helping each other out and providing their experiences and testing as well.
Why Root?
I get the same question from everybody all the time, "why do you root your phone?" Well, many reasons, which I'll list a few below, but because I spent a lot of money on my phone and I feel I should have full access to it. If your phone is leased or company owned, I understand why you wouldn't, but if you own it outright, why not have full access to do what you want with it? I mean, how would you feel if you purchased a computer (I'll use Windows in this analogy) and it came with one user account that was only part of the "Users" group, no local Administrator or account part of the Administrators group and no way to grant your one user account Admin rights? I'd be upset as I wouldn't be able to do much with it including; remove bloatware, install my own applications, replace the stock AV/Malware software, upgrade my video driver or even start from scratch. I mean the first thing I do when I get a new computer is format the HDD lol. I know it might be a silly analogy, but I don't see how it's any different than having root access on my phone.
- Remove bloatware (system apps you don't want/need)
- Custom Kernels (though the stock kernel on this phone is amazing out to the box, custom gives us more access to manage wakelocks, color control, vibrations, among other kernel items) (EXKM and Kernel Adiutor are a couple great apps to tweak your custom kernel)
- Customer recovery (easy backup/recovery, easy flashing of Zips, etc...)
- Untethered system theming including; custom fonts, launcher tweaks, status/navbar tweaks, etc...)
- System wide ad blocking
- Full system backup/restore (Titanium Backup is amazing for full system backups and then upload to cloud storage of your choice)
- Terminal root access (every have horrible battery drain and can't figure out exactly why quick and easy? Drop to terminal, elevate using su, then run top and and see what app is hogging the CPU)
- Xposed modules for system customizations (I've used a lot over the years, but not on this phone yet. You will also FAIL SafetyNet if you use the Xposed Framework.)
- AUDIO MODS! I honestly don't know how I lived my life without apps like ViPER and Dolby on my phone
A/B Partitions
To hopefully help clear up some confusion here, I'll list some important points to take note of.
- The whole point of the dual partition setup is to make OTA updating easier, allowing for updating the OS in the background
- There are two system, two boot and two vendor partitions, but only one data partition
- Only one system and its corresponding boot partition are active at one time
- Whichever system/boot partition is active will use the one data partition
- Flashing a custom kernel, mod zip or Magisk will flash to the current active slot from recovery, however flashing the Google Image or a custom rom will flash to the inactive slot
- The recovery is part of the boot partition, meaning anytime you flash the stock or custom kernel, for example, you'll need to reflash your custom recovery again (unless you install a kernel zip created with AnyKernel2 by @osm0sis)
My Build
Sharing these details as if you are on a different image, kernel, carrier, etc... your results may vary.
Phone: Google Pixel XL 2 Black 128GB - purchased from Google Store / Hardware Version: rev_10
Carrier: Project Fi with eSIM & physical SIM
Android Version: Official 8.1.0 / Security Patch Level: February 5, 2018
Build Number: OPM1.171019.018
Kernel: 4.4.119-FlashKernel-Taimen-v2.20 (clang version 6.0.0)
Root: Magisk Manager 5.6.1(105) (patched dtbo NOT preserving "force encryption" or "AVB2.0/dm-verity") & Magisk 16.0(1600) / Modules: Busybox for Android NDK 1.28.1, Magisk Manager for Recovery Mode (mm) 2018.1.31, Single User Mod 1.4, ViPER4Android FX Materialized 1.5.1 (2.5.0.5)
Recovery: TWRP 3.2.1-0
APKs: SELinuxModeChanger v11.0, AdAway 3.2-60, Dolby, MinitBatteryResrouces
Convenient Play Store Apps: 3Minit Battery Settings, FiSwitch, Kernel Adiutor, Light Manager, Root Explorer, substratum (Swift Black), TiBu Pro (I do scheduled backups of my phone to my Google Drive) & Terminal Emulator (great to use Busybox commands like "traceroute" or "top" to find that app killing your battery!)
Android Platform Tools Install
1. Download the latest version for your computer OS (PC/Mac/Linux) from Google: https://developer.android.com/studio/releases/platform-tools.html
2. Unzip the downloaded file to your hard drive somewhere and:
- Windows: add to your PATH (google "add adb to path")
- Mac/Linux: From terminal of your choice "sudo install adb /usr/local/bin && sudo install fastboot /usr/local/bin" (run from within the extracted directory and enter your password when prompted)
- Windows 10 & macOS High Sierra detect the phone automatically, but older versions you may need Android Device Drivers. Just Google what you might need and how to do it if your phone is not detected automatically.
Unlocking
1. Turn your phone off.
2. Press and hold Volume Down, then press and hold Power.
3. Plug your phone into your computer.
4. From command prompt/terminal on your computer (run Command Prompt as Admin in Windows throughout this guide):
- fastboot flashing unlock
- fastboot flashing unlock_critical
NOTE: I've read a lot of back and forth on if we should unlock_critial or not. This is just my opinion, but if you're here to do all this stuff to your phone, want complete access to do whatever you want to it, just do it. It's better to be ready now for the future because every time you unlock or relock, it will factory reset your phone. I've been unlocked both regular and critical since the first boot when I took my phone out of the box. I'll also mention, I’m not entirely sure what steps will work or not work in this guide if you don't since I've never not been unlocked with critical.
5. Follow the instructions on the phone screen to do the factory reset.
Clean Start
1. Download the "taimen" for Pixel 2 XL factory image [8.1.0 (OPM1.171019.018, Feb 2018)]: https://developers.google.com/android/images
2. Turn your phone off.
3. Press and hold Volume Down, then press and hold Power.
4. Plug your phone into your computer.
5. Unzip the downloaded file to your hard drive somewhere and from the directory you extracted the files (CMD/Terminal):
- Windows: flash-all.bat
- Mac/Linux: ./flash-all.sh
- Unplug your phone from your computer
Initial Config/Prep
1. Go through the initial phone setup steps.
- Make sure you setup your Google account so you have access to the Play Store and you can activate your eSIM if that's what you're using.
NOTE: When setting up with only an eSIM, I ran into some bugs and caveats I had to figure out on my own as Google support couldn't figure it out let alone understand what I was trying to explain to them. I ordered a physical SIM and now have both an eSIM and a physical SIM installed and can switch between them.
Verizon SIM: As @jrbxx7 was kind enough to share below; if running a Verizon SIM, wait till after setup is complete before inserting it. That way the vzw apps don't get installed on google setup.
eSIM Caveat: If you have 2 Step Authentication turned on for your Google account and your phone is your only device with the Google Authenticator App or Google Prompt, you will have to use one of your backup codes to log back into your account as your phone will not be activated until it's completed in the Project Fi application.
eSIM Bug: After you go through the initial phone setup, let Play Store finish its updates and don't reboot yet. Open Play Store and search for "Project Fi", then click "Enable", but DON'T update it. Just open Project Fi, complete the activation then reboot your phone. You can update the Project Fi app after the activation is successful. I've tested this through three factory restores and the result is the same every time.
Physical SIM: No issues since your phone will just be activated after boot so you can receive SMS codes.
2. Enable Developer Mode: tap "Build number" under "About phone" 7 times.
3. Under "Developer options", enable "USB debugging".
4. Download necessary files:
- Magisk 16.0(1600): https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
- SELinuxModeChanger 11.0: https://f-droid.org/en/packages/com.mrbimc.selinux/
- AdAway 3.2-60: https://f-droid.org/en/packages/org.adaway/
- Dolby: https://forum.xda-developers.com/pixel-2-xl/how-to/viper-dd-atom-t3724096
- Kernel. I use @nathanchance Flash Kernel: https://forum.xda-developers.com/pixel-2-xl/development/taimen-flash-kernel-1-00-t3702057
NOTE: You can use whatever kernel you want, but I've only used/tested with Flash. Flash Kernel also has the proper drives to resolve the TWRP touch issues. I've read other custom kernels do as well.
- TWRP 3.2.1-0 (image & installer): https://forum.xda-developers.com/pixel-2-xl/development/twrp-alpha-pixel-2-xl-t3698148
5. Plug your phone into your computer.
- If prompted on your phone, save and allow USB Authorization for your computer.
6. Push downloaded files to your phone (CMD/Terminal):
- adb push <path_to_Magisk_file>.zip /sdcard/Download
- adb push <path_to_SELinuxModeChanger_file>.apk /sdcard/Download
- adb push <path_to_AdAway_file>.apk /sdcard/Download
- adb push <path_to_Dolby_file>.zip /sdcard/Download
- adb push <path_to_Kernel_zip_file>.zip /sdcard/Download
- adb push <path_to_TWRP_image_file>.img /sdcard/Download
- adb push <path_to_TWRP_installer_file>.zip /sdcard/Download
Install Kernel & TWRP
NOTE: As of the Google February security image release, TWRP will no longer decrypt. You have three options to flash in TWRP until it's fixed; disable security before booting to TWRP, use USB storage via your OTG adapter, or put the files you need in the /data partition.
1. adb reboot bootloader (CMD/Terminal while your phone is still plugged into your computer)
2. Flash TWRP:
- fastboot boot <path_to_TWRP_image_file>.img
- Once in TWRP, install the TWRP_installer.zip file
- Reboot into TWRP
- Install Kernel.zip file
- Install the Magisk_16.0(1600).zip file
- Reboot to System.
3. Configure Magisk:
- Open Magisk Manager
- (OPTIONAL) Patch dtbo by unchecking both "force encryption" and "AVB2.0/dm-verity", tap "Install", tap "Install", tap "Direct Install (Recommended), then reboot
NOTE: By patching dtbo, you will receive a message on every boot that says something along the lines of "There's an internal problem with your device". This is perfectly normal when patching the dtbo and can be ignored as nothing is broken. Now, to be honest, I patch dtbo as I can't get certain things to work properly without, like Dolby, and the message doesn't bother me as it's only on boot up. I know patching dtbo is necessary for some things. For example, I don't think you can do manual build.prop edits without editing dtbo, if I'm not mistaken. I have had a few others on other threads say they were able to get Dolby to work without patching dtbo and just using SELinux in "permissive" mode, but I couldn't. Up to you, hence the "optional" part. If you decide to patch dtbo and want to go back, just flash the stock dtbo image file in fastboot or TWRP.
- Open Magisk Manager
- Goto Settings and tap "Hide Magisk Manager"
- Reopen Magisk after it's done
- Goto Settings and make sure "Magisk Hide" and "Systemless hosts" are both enabled
- Gogo Magisk Hide and check the applications you need to hide from Root (banking apps, authenticators, etc...)
4. If Play Store is not showing as "Certified" under Play Store Settings, clear Data and Cache on the Play Store under Phone Settings. Your Play Store will now be "Certified" under the Play Store Settings.
Install/Configure SELinuxModeChanger and AdAway
NOTE: It's my understanding that SELinux does not need to be set to "permissive" for ViPER and Dolby to work, but I can't get them to work otherwise. My Dolby will FC without setting SELinux to "permissive", which is why I'm adding it to my guide in case someone else is having the same issue. You can use the Magisk Module script if you want, but I like the convenience of the App to turn on and off easily.
1. Open "Downloads" from the App Launcher on your phone.
2. Install both SELinuxModeChanger.apk and AdAway.apk.
3. Open SELinuxModeChanger:
- Tap "Permissive"
- Tap "Automatically start on boot"
4. Open AdAway:
- Open Preferences and make sure "Enable systemless mode" is enabled". It's normal to be Greyed out. This is verification from the Magisk Settings you set above.
- Tap "Download files and apply ad blocking"
5. Reboot phone.
Install & Configure Magisk Modules / Dolby
1. Open Magisk Manager and go to Downloads:
- Download "Busybox for Android NDK" (some root apps need this, but it's also nice to have these utilities)
- Download "Single User Mod" (needed for latest TWRP install to my understanding, but it worked for me without. I like this anyway because I don't share my phone)
- Download "ViPER4Android FX" (make sure to get the v1.5.1(2.5.0.5) version) / during install you will be asked what version and theme, chose the 2.5.0.5 driver version and the Materialized version (needed for Dolby).
- Reboot Phone
2. Open ViPER 4 Android FX application:
- Under Settings tap "Turn on developer mode" then tap "Disable SELinux"
3. Reboot Phone.
- After reboot, open ViPER 4 Android FX application and enable/configure the effects you want.
NOTE: Be patient after a phone reboot. It sometimes takes a minute for the Magisk modules to load.
4. Reboot to TWRP.
- Install Dolby.zip file
- Reboot into System
5. Open Dolby, and if it force closes, make sure your SELinux is "permissive" first and if you still have force closes, patch dtbo following instructions above.
Themes & Mods - Screenshots attached below!
I use substratum and Swift Black from the Play Store for my system wide theme. I use Light Manager from the Play Store for custom status lights for applications, etc... You can also get more customization of what icons to show or not show on your status bar by pulling down the notifications at the top of the phone and holding down the Settings gear icon until you feel a vibrate. You'll now have "System UI Tuner" under Settings->System. I'm also using the following Mods:
- SearchLess Launcher: https://forum.xda-developers.com/pixel-2-xl/themes/mod-pixel-2-xl-launcher-mods-8-1-0-dp1-t3701939
- Rosemary Font: https://forum.xda-developers.com/pixel-2-xl/themes/font-flashable-ubuntu-font-zip-pixel-2-t3710892
- Various Mods Aroma w/ 3Minit Battery: https://forum.xda-developers.com/pixel-2-xl/themes/various-mods-8-1-december-update-t3721741
- Substatum /w Swift Black (I dont theme System UI or System UI Navigation as part of my setup with the Various Mods Aroma)
- ViPER w/ Audiophile X profile & Dolby using Music profile (Volume Leveler / Surround Virtualizer / Intelligent EQ: Open)
Updating
I'm going to keep these steps kind of generic and provide the order in which things have to be done (order is important), however for the details just follow the steps for each part above. You shouldn’t have to do the setup for Magisk Modules again unless:
- You ran into issues and needed to do a clean start with Magisk using the Magisk Uninstaller
- You are doing a Google Image update
Magisk - Push the updated Magisk Zip to your /sdcard/Download folder, boot into TWRP, flash new Magisk Zip, reboot into System, go through Magisk setup steps again.
Kernel – Push the updated Kernel Zip file to your /sdcard/Download folder, make sure you have the Magisk Zip file in your /sdcard/Download folder as well. Reboot to TWRP, flash new Kernel, flash Magisk, boot System and setup Magisk again.
TWRP – Push the updated TWRP Zip to your /sdcard/Download folder, reboot to TWRP, flash new TWRP Zip, boot into TWRP to test, boot System.
Google -
1. Disable any screen security you have.
2. Disable and uninstall Substratum themes, if you have any.
3. Full backup of some sort recommended!
4. Boot to Bootloader and do a flash-all (without -w) of 8.1 factory image, boot to System and allow the update to finish.
5. Boot back to Bootloader, boot TWRP, install TWRP, reboot to TWRP, install Kernel Zip file, install Magisk Zip file, boot back to System.
6. Complete Magisk setup steps (Magisk hide, App hide, systemless, etc..), check SafetyNet.
7. Apply any mods and themes in Substratum.
Have fun!
Right on brother. My own journey is pretty much a mirror of your write up and I can't think of a single thing to add. Nice work. We have the same setup. Lol
CyberpodS2 said:
Right on brother. My own journey is pretty much a mirror of your write up and I can't think of a single thing to add. Nice work. We have the same setup. Lol
Click to expand...
Click to collapse
Thanks man! Yeah, this stuff has always been fun to me. I don't mind "breaking" my phone so I have to figure out how to fix it. lol I lost count how many times I wiped, flashed, etc to come up with my list.
I've also updated the guide to include "updating" stuff.
felosisman said:
Thanks man! Yeah, this stuff has always been fun to me. I don't mind "breaking" my phone so I have to figure out how to fix it. lol I lost count how many times I wiped, flashed, etc to come up with my list.
I've also updated the guide to include "updating" stuff.
Click to expand...
Click to collapse
Exactly, I got really quick at starting from scratch... Lol
Nice write up! One note if u feel like adding it, if running a verizon sim, wait till after setup is complete before inserting it. That way the vzw apps dont get installed on google setup.
jrbxx7 said:
Nice write up! One note if u feel like adding it, if running a verizon sim, wait till after setup is complete before inserting it. That way the vzw apps dont get installed on google setup.
Click to expand...
Click to collapse
Thanks for the addition, I"ll add it now! I don't have a VZW SIM so I would never have known lol.
This is the best guide on XDA now! I've been reading 10 different threads to do stuff, but someone who understands how it all works together can make it so much easier... Thanks again [emoji106]
Sent from my [device_name] using XDA-Developers Legacy app
slaydog said:
This is the best guide on XDA now! I've been reading 10 different threads to do stuff, but someone who understands how it all works together can make it so much easier... Thanks again [emoji106]
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
You're welcome! I'm happy to know this is helpful to folks.
Sticky?
Mods,
Is there any way to make this thread a sticky so it's easier for everybody to find?
Thanks!
jrbxx7 said:
Nice write up! One note if u feel like adding it, if running a verizon sim, wait till after setup is complete before inserting it. That way the vzw apps dont get installed on google setup.
Click to expand...
Click to collapse
What exactly is installed for Verizon apps? I didn't notice them on my install. Not saying they are not there, just didn't notice the changes.
felosisman said:
Mods,
Is there any way to make this thread a sticky so it's easier for everybody to find?
Thanks!
Click to expand...
Click to collapse
I think this thread is worth a sticky because it covers a lot of stuff that other guides don't, and covers them well. TWRP wasn't even a viable option when other guides were made, and it has made things much simpler...
Sent from my [device_name] using XDA-Developers Legacy app
Thank you for the guide. So I assume that if I were to brick the device I could use the factory images and fastboot to restore? Does anyone know what would happen if you tried to flash an older factory image street upgrading through OTA?
Sent from my Pixel 2 XL using Tapatalk
andrewjt19 said:
Thank you for the guide. So I assume that if I were to brick the device I could use the factory images and fastboot to restore? Does anyone know what would happen if you tried to flash an older factory image street upgrading through OTA?
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
You should always be able to restore using the factory images from Google. In all the years I've been doing this, I've never once actually bricked a device to where is wouldn't work anymore. Just basically boot up to the bootloader and run the flash-all script. You can get the full Google images and instructions here: https://developers.google.com/android/images
As for downgrading, I've not personally done it. I know folks have gone from the 8.1 DPs back to 8.0, but if I'm not mistaken Google is making it hard to downgrade for security reasons. Once 8.1 is officially released, we may not be able to go back to 8.0, for example. I'll let others chime in with their experiences.
EDIT: After reading your post again, if you mean you took the November OTA you will be fine. The latest factory image from Google is the same as the Nov OTA.
please delete
felosisman said:
You should always be able to restore using the factory images from Google. In all the years I've been doing this, I've never once actually bricked a device to where is wouldn't work anymore. Just basically boot up to the bootloader and run the flash-all script. You can get the full Google images and instructions here: https://developers.google.com/android/images
As for downgrading, I've not personally done it. I know folks have gone from the 8.1 DPs back to 8.0, but if I'm not mistaken Google is making it hard to downgrade for security reasons. Once 8.1 is officially released, we may not be able to go back to 8.0, for example. I'll let others chime in with their experiences.
EDIT: After reading your post again, if you mean you took the November OTA you will be fine. The latest factory image from Google is the same as the Nov OTA.
Click to expand...
Click to collapse
Thanks buddy for the reply. That's what I figured but my personal policy had always been to "find" the fix before I tamper with anything. Once I unlock the bootloader I'm assuming I cannot take OTA's in typical fashion right? Also is relocking the bootloader the same as unlocking (obviously using the opposite command)? Thanks so much.
Sent from my Pixel 2 XL using Tapatalk
andrewjt19 said:
Thanks buddy for the reply. That's what I figured but my personal policy had always been to "find" the fix before I tamper with anything. Once I unlock the bootloader I'm assuming I cannot take OTA's in typical fashion right? Also is relocking the bootloader the same as unlocking (obviously using the opposite command)? Thanks so much.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
You're welcome! Absolutely, might as well be prepared just in case.
So, I've not tried it myself from "System Updates", but to my understanding you can still take OTA with the bootloader unlocked. I think the OTAs stop working when the System partition has been modified. But considering pretty much everything we do these days is Systemless, I think it'd be fine. I did manually install the November OTA from fastboot with my bootloader unlocked and it worked fine. To relock, yeah the command is pretty much just the opposite.
"fastboot flashing lock" would relock your device. Keep in mind though, every time you lock or relock it will wipe your device.
Sticky Request
I've done sone searching and can't figure it out, but does anybody know if there is an official way to request this to be a sticky?
felosisman said:
I've done sone searching and can't figure it out, but does anybody know if there is an official way to request this to be a sticky?
Click to expand...
Click to collapse
Your guide helped
Cheers ?
You using any other mods
Sent from my Google Pixel 2 XL using XDA Labs
Prattham said:
Your guide helped
Cheers
You using any other mods
Sent from my Google Pixel 2 XL using XDA Labs
Click to expand...
Click to collapse
Excellent, happy it was helpful!
No, I'm only using what I've got posted; ViPER, Single User and BusyBox.
I'll go ahead and ask this here since the Viper thread is so busy and I have seen a lot of answers and it's things that I've already tried over and over again. But, no matter which Viper version I download whether it be through magisk or a zip install via TWRP, I can never ever ever get the drivers to install. You got Viper in the title of your thread but I only seen one line of Viper in the op and that's to do with setting selinux to permissive, which I already have set to.
So does anybody have any out-of-the-box advice on what to do to get that Viper driver to install on a pixel 2 XL running 8.1 .0 DP2?
I'll spend all my 8 thanks for the day thanking somebody if they can help me figure this out.
Edit: I did just notice some more Viper instructions, my bad. I will try those out and report back
Edit 2: So I followed your instructions to the T, and the driver still won't install. Anyone got any ideas? It's not some sort of bug with the program is it where the driver has really been installed already but it's just saying that it's not?
Sent from my Pixel 2 XL using XDA Labs

WiFi Tether unlimited nougat (ROOT)

PLEASE NOTE:This is NOT a guide to root your phone but i did provide the links to the tools to do so for the Samsung j700p.
WARMING; Rooting a device may void the warranty on the device. It may also make the device unstable or if not done properly, may completely brick the device. Some methods may install additional apps/software on your device. XDA-Developers or the author does not take any responsibility for your device. Root at your own risk and only if you understand what you are doing! Additionally this may go against your service contract which I'm not responsible for as well.
Worked for my j700p running 7.1.1 stock rooted with TWRP/SUPERSU latest.
What you need to do to get tethering on Nougat is root the device (temporarily at least), enable tethering and then (if you want) unroot it so that everything is back to normal and you can take OTA updates and use Android Pay without any issues.
All you’ll need to enable tethering on Android nougat is TWRP recovery installed on your device and the latest systemless SuperSU zip to root the device. (Always remember to backup your system just in case)
How to Enable Tethering on Android Nougat
Root your android running nougat
Edit build.prop file: Add the
net.tethering.noprovisioning
line to the bottom of build.prop file on your Android device. (Download Build Prop Editor from the play store if you don't know how to get to this, I suggest Rom toolbox as it has build.prop included as well as terminal emulator which you will need for the next step. LINKS BELOW)
Reboot device after saving changes to build.prop file.
Download/install a Terminal emulator app from Play Store (I used the terminal emulator included in ROM toolbox but you can choose whichever you'd like.) You also you WILL need busy box installed to be able to execute this line.
Open Terminal emulator on your device and issue the following commands one-by-one:
su
settings put global tether_dun_required 0
exit
└ Grant root access to the app when asked.
Reboot device
DONE!
If you wish to unroot now you can. I have not tested this so can't confirm if works after unroot (since I love having ROOT) but jyst go to
SuperSu settings full unroot. Restart and you should be good. This should renable android pay. If not don't ask me to help as I don't use android pay nor wish to unroot my own device.
ALL CREDIT goes to Shivam Malani, Thank You!
Links;
Odin (for my j700p I used v.3.11.1)
https://samsungodin.com/download/
SUPERSU (latest)
http://www.supersu.com/download
TWRP (latest)
https://twrp.me
Busybox https://play.google.com/store/apps/details?id=com.jrummy.busybox.installer
Rom toolbox lite (for build.prop editor and terminal emulator)
https://play.google.com/store/apps/details?id=com.jrummy.liberty.toolbox
h3xkore said:
ALL CREDIT goes to Shivam Malani, Thank You!
PLEASE NOTE:Rooting a device may void the warranty on the device. It may also make the device unstable or if not done properly, may completely brick the device. Some methods may install additional apps/software on your device. XDA-Developers or the author does not take any responsibility for your device. Root at your own risk and only if you understand what you are doing! Additionally this may go against your service contract which I'm not responsible for as well.
Worked for my j700p running 7.1.1 stock rooted with TWRP/SUPERSU latest.
What you need to do to get tethering on Nougat is root the device (temporarily at least), enable tethering and then (if you want) unroot it so that everything is back to normal and you can take OTA updates and use Android Pay without any issues.
All you’ll need to enable tethering on Android nougat is TWRP recovery installed on your device and the latest systemless SuperSU zip to root the device. (Always remember to backup your system just in case)
How to Enable Tethering on Android Nougat
Root your android running nougat
Edit build.prop file: Add the
net.tethering.noprovisioning
line to the bottom of build.prop file on your Android device. Download Build Prop Editor from the play store if you don't know how to get to this, I suggest Rom toolbox as it has build.prop included as well as terminal emulator which you will need for the next step.
Reboot device after saving changes to build.prop file.
Download/install a Terminal emulator app from Play Store (I used the terminal emulator included in ROM toolbox but you can choose whichever you'd like.)
Open Terminal emulator on your device and issue the following commands one-by-one:
su
settings put global tether_dun_required 0
exit
└ Grant root access to the app when asked.
Reboot device
DONE!
If you wish to unroot now you can. I have not tested this so can't confirm if works after unroot (since I love having ROOT) but jyst go to
SuperSu settings full unroot. Restart and you should be good. This should renable android pay. If not don't ask me to help as I don't use it nor wish to unroot my own device.
Click to expand...
Click to collapse
I did as followed, didn't stick for some reason.
Sent from my SM-J700P using Tapatalk
dlinderaz said:
I did as followed, didn't stick for some reason.
Click to expand...
Click to collapse
Did you make sure u granted ROOT permission for the build prop and terminal apps? You also must restart in between the build prop and terminal commands. You also need busybox installed with root permission this was mist likely the reason it didn't stick. I've updated the OP along with links. Please let me know if that helps. Last note make sure everything is up to date.
h3xkore said:
Did you make sure u granted ROOT permission for the build prop and terminal apps? You also must restart in between the build prop and terminal commands. You also need busybox installed with root permission this was mist likely the reason it didn't stick. I've updated the OP along with links. Please let me know if that helps. Last note make sure everything is up to date.
Click to expand...
Click to collapse
It worked perfectly. Must have been the fact that I hadn't installed BusyBox. Thanks a million. I really appreciate your help.
Sent from my SM-J700P using Tapatalk
dlinderaz said:
It worked perfectly. Must have been the fact that I hadn't installed BusyBox. Thanks a million. I really appreciate your help.
Sent from my SM-J700P using Tapatalk
Click to expand...
Click to collapse
hey no problem im glad i could help and that it worked. i think if u pay for a service they shouldnt limit you so much on using it
I think I might have spoken too soon. Is this for the Virgin Mobile or Boost Mobile J700P? I have Virgin Mobile and I keep getting the "you have not subscribed to this service" window. It stayed on for a few minutes but the minute I went to go connect my smart TV to my hotspot, it turned it back off.
Sent from my SM-J700P using Tapatalk
dlinderaz said:
I think I might have spoken too soon. Is this for the Virgin Mobile or Boost Mobile J700P? I have Virgin Mobile and I keep getting the "you have not subscribed to this service" window. It stayed on for a few minutes but the minute I went to go connect my smart TV to my hotspot, it turned it back off.
Click to expand...
Click to collapse
Did you make sure with build.prop you entered the net.provisioning line in "value" and not name? I'm using boost unlimited $50 plan but should work for virgin as well. Did you unroot? Are you using magisk or supersu?
h3xkore said:
Did you make sure with build.prop you entered the net.provisioning line in "value" and not name? I'm using boost unlimited $50 plan but should work for virgin as well. Did you unroot? Are you using magisk or supersu?
Click to expand...
Click to collapse
I'm using SuperSU. Yes, everything as instructed. I was able to do it when I was still with Marshmallow (Using Sqlite editor) but after the update, I have not had any luck.
Sent from my SM-J700P using Tapatalk
dlinderaz said:
I'm using SuperSU. Yes, everything as instructed. I was able to do it when I was still with Marshmallow (Using Sqlite editor) but after the update, I have not had any luck.
Click to expand...
Click to collapse
Hmm try using a vpn. Nordvpn is having a 7day free trial right now. Reset your network settings, repeat the steps above. Before you turn on the hotspot shield turn on the vpn and after connect try it. If you still get the notification then its something installed on your phone from VM that's monitoring your usage which is most likely. I recommend switching to boost. Their 50$ plan is pretty good. Great coverage in my area and surroundings. I use about 200-300gb torrenting and tethering a month and they don't seem to care. Using a vpn I get about 2mb down consistently except during peak hours. Anyways let me know about the vpn working or not. Hopefully it's that simple.
h3xkore said:
Hmm try using a vpn. Nordvpn is having a 7day free trial right now. Reset your network settings, repeat the steps above. Before you turn on the hotspot shield turn on the vpn and after connect try it. If you still get the notification then its something installed on your phone from VM that's monitoring your usage which is most likely. I recommend switching to boost. Their 50$ plan is pretty good. Great coverage in my area and surroundings. I use about 200-300gb torrenting and tethering a month and they don't seem to care. Using a vpn I get about 2mb down consistently except during peak hours. Anyways let me know about the vpn working or not. Hopefully it's that simple.
Click to expand...
Click to collapse
Thank you. I'm definitely going to switch. I don't know why I'm paying $60 for "Unlimited" data to use only with the phone and they expect me to pay an additional $10 for only 2 Gigs of hotspot. I hardly use any of my phone data. LOL. Maybe I need to check prices of wifi internet for the home if they even have it in my neck of the woods. Thank you so very much for all your time and help. You're the bestest. Happy Holidays.
Sent from my SM-J700P using Tapatalk
dlinderaz said:
Thank you. I'm definitely going to switch. I don't know why I'm paying $60 for "Unlimited" data to use only with the phone and they expect me to pay an additional $10 for only 2 Gigs of hotspot. I hardly use any of my phone data. LOL. Maybe I need to check prices of wifi internet for the home if they even have it in my neck of the woods. Thank you so very much for all your time and help. You're the bestest. Happy Holidays.
Click to expand...
Click to collapse
Yea I hear you. My $50 plan comes with 8gb hotspot buti tend to go over that...WAY over that lol. Currently torrenting 8 pc games lol. Side note though on this plan. You get 23gb a month "prioritized" connection meaning full speeds always. After that your put on the back burner during peak times or in other words when your tower your connected to is busy. Doesn't happen often it seems and I live in the middle of a decent size city so if you're not in say Houston or new York I'd say you won't have anything to worry about. I'm sorry I didn't fix your problem and I wish you the best. Happy holidays to you as well.
Open Terminal emulator on your device and issue the following commands one-by-one:
su
settings put global tether_dun_required 0
exit
└ Grant root access to the app when asked.
Reboot device
Now I put su and entered the setting line but when I put exit nothing happen.... I did reboot... any way how to tell if I did this right and works fine?? I have j700t1 metro
h3xkore said:
PLEASE NOTE:This is NOT a guide to root your phone but i did provide the links to the tools to do so for the Samsung j700p.
WARMING; Rooting a device may void the warranty on the device. It may also make the device unstable or if not done properly, may completely brick the device. Some methods may install additional apps/software on your device. XDA-Developers or the author does not take any responsibility for your device. Root at your own risk and only if you understand what you are doing! Additionally this may go against your service contract which I'm not responsible for as well.
Worked for my j700p running 7.1.1 stock rooted with TWRP/SUPERSU latest.
What you need to do to get tethering on Nougat is root the device (temporarily at least), enable tethering and then (if you want) unroot it so that everything is back to normal and you can take OTA updates and use Android Pay without any issues.
All you’ll need to enable tethering on Android nougat is TWRP recovery installed on your device and the latest systemless SuperSU zip to root the device. (Always remember to backup your system just in case)
How to Enable Tethering on Android Nougat
Root your android running nougat
Edit build.prop file: Add the
net.tethering.noprovisioning
line to the bottom of build.prop file on your Android device. (Download Build Prop Editor from the play store if you don't know how to get to this, I suggest Rom toolbox as it has build.prop included as well as terminal emulator which you will need for the next step. LINKS BELOW)
Reboot device after saving changes to build.prop file.
Download/install a Terminal emulator app from Play Store (I used the terminal emulator included in ROM toolbox but you can choose whichever you'd like.) You also you WILL need busy box installed to be able to execute this line.
Open Terminal emulator on your device and issue the following commands one-by-one:
su
settings put global tether_dun_required 0
exit
└ Grant root access to the app when asked.
Reboot device
DONE!
If you wish to unroot now you can. I have not tested this so can't confirm if works after unroot (since I love having ROOT) but jyst go to
SuperSu settings full unroot. Restart and you should be good. This should renable android pay. If not don't ask me to help as I don't use android pay nor wish to unroot my own device.
ALL CREDIT goes to Shivam Malani, Thank You!
Links;
Odin (for my j700p I used v.3.11.1)
https://samsungodin.com/download/
SUPERSU (latest)
http://www.supersu.com/download
TWRP (latest)
https://twrp.me
Busybox https://play.google.com/store/apps/details?id=com.jrummy.busybox.installer
Rom toolbox lite (for build.prop editor and terminal emulator)
https://play.google.com/store/apps/details?id=com.jrummy.liberty.toolbox
Click to expand...
Click to collapse
xghostyxjokerx said:
Open Terminal emulator on your device and issue the following commands one-by-one:
su
settings put global tether_dun_required 0
exit
└ Grant root access to the app when asked.
Reboot device
Now I put su and entered the setting line but when I put exit nothing happen.... I did reboot... any way how to tell if I did this right and works fine?? I have j700t1 metro
Click to expand...
Click to collapse
Did you type each line and hit enter(return) each time? Such as "su[enter]" starts another line "settings put global blah blah[enter]" it will start another line "exit[enter]" u may need to type exit again after this. I had to. So 2 "exit[enter]"
I used an alternative method I found here awhile back.. install APN backup and restore, convert it to a system app (important, use apps2sd or the like), backup your apns then edit the backup file, add ",dun" to each apn in the APN backup xml in the "type" field. Then go back into the APN backup app, delete apns and restore the backup you edited. There's a full write up here around the just forum somewhere with more details. It works great, may have to restore your APN backup if you update prl.
xghostyxjokerx said:
Open Terminal emulator on your device and issue the following commands one-by-one:
su
settings put global tether_dun_required 0
exit
└ Grant root access to the app when asked.
Reboot device
Now I put su and entered the setting line but when I put exit nothing happen.... I did reboot... any way how to tell if I did this right and works fine?? I have j700t1 metro
Click to expand...
Click to collapse
Sorry so late on reply. I hope you figured this out already but your on a different and newer version of this phone.
fedaykinofdune said:
I used an alternative method I found here awhile back.. install APN backup and restore, convert it to a system app (important, use apps2sd or the like), backup your apns then edit the backup file, add ",dun" to each apn in the APN backup xml in the "type" field. Then go back into the APN backup app, delete apns and restore the backup you edited. There's a full write up here around the just forum somewhere with more details. It works great, may have to restore your APN backup if you update prl.
Click to expand...
Click to collapse
Does this method still work for you? Now when I use my WiFi after my 8gb limit it goes to boost homepage on connected device ?
Does this work on the j700t1.
I'm going to try it when I get home but I'm just curious if anyone got it working on the metro pcs variant.

Things to do with a rooted fire tv!!

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 following​Boot 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 use​ADBLink-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.

Categories

Resources