SuperSU APK Download For Android – Official Updated 2020
SuperSU APK Download For Android – Official Updated 2020
Android SuperSU APK Download
SuperSU for Android - APK Download
SuperSU APK + Mod - Download SuperSU 2.82 Latest Version ...
SuperSU 2.79 APK Download - softpedia
Download SuperSU APK Full ApksFULL.com
SuperSU 2.76 Apk - 4AppsApk
Recovering Accounts on Bluestacks
Ok, so when this update hit I thought my account was gone for good. But I figured out a way to transfer it. I'm not sure if this will work with other Android Emulators or not so use at your own caution. Before you begin, use google to search and download the following: - bstweaker - ES File explorer.apk (or your favourite fire explorer, needed in the second half aka the 64bit side) - SuperSu.apk (possibly needed in the second part) - F-droid.apk (you'll get oandbackup from inside F-droid) What I did was use a tool called BS tweaker to root the 32 bit version of Bluestacks. (To actually root it, Blustacks must be closed/not in background at all. Then click the unlock button. Start Bluestacks and then click "patch", "install SuperSU", "update binaries" in that order.) With that I was able to install F-droid. Using F-droid I was able to install OandBackup into a rooted version of Bluestacks. From here I was now able to back up the apk data from the old version using OandBackup. I exported the .zip file to Windows using Bluestack's built in media manager. I closed Bluestacks and switched the BStweaker program to Bluestacks 64bit. To switch it check the last tab marked "settings" and there will be a dropdown menu say "Bluestacks". Click that and choose Bluestacks 64bit. (Bluestacks 64 bit is the large number version mentioned in the other guide here about how to get around this issue.) As a heads up: It crashed the program for me when I switched to the 64 bit version, but that's ok. I reopened it and it was set for the 64 bit bluestacks. Now I repeated the process... Rooted the 64 bit Bluestacks. Now it failed to install the SuperSU for me so I had to install that manually. (Just google "SuperSU apk"). But after I installed the SuperSu manually I was able to install F-droid and Oandbackup on the 64 bit version. I then imported the zip files. I had to install ES Filemanager to move the zip file to the oandbackup's default folder. But once I did that I was able to restore the Rockman X dive apk save data to the file, complete the download and launch the app with my recovered save file that I'd spent a ton of time on. It was a bit of a lengthy process, but it did work for me. I make no guarantees that it'll work for you. But it's better than nothing I guess. I hope it works for you as well as it did for me. EDIT to add: Once you're in, if you haven't set it up a transfer account option or linked to another account... Do that first.
I may have found a work-around for the Pokémon Go root detection.
Why are you even trying anymore? SUHIDE Chainfire updated his SuHide program FOR ANDROID 6.0 AND ABOVE(For Android versions under 6.0, you're out of luck!). SuHide hides the root binary and passes Android Safety Net allowing you to play Pokemon Go with root. Not only is it working but it works with Xposed, so you can have all you Pokemon Go Xposed modules back. (I don't condone using spoofer modules) INSTALLING SUHIDE TWRP REQUIRED Remember this is only for Android 6.0 and newer. If you install it on the wrong software, your device could get bricked. If you don't know what a bricked device is, you probably shouldn't be doing this! Also, SUHide is highly experimental. If this doesn't work for you, don't be surprised. And don't be afraid to ask for help in the comments. :) Make sure you pass SafetyNet before doing this! You can check if you pass it or not with this app after done.
Step one (Optional, but highly recommended): Take a nandroid backup. (A full backup of your phone)
Step two: Uninstall Magisk, Xposed or any program that gets detected by safety net.
[Guide] How to bypass SafetyNet & Error 803-3001 (Android)
FE: Heroes uses Google's SafetyNet API, which checks your device's integrity; in other words, it checks if your device has been "tampered with or otherwise modified". This API is used for example in Android Pay, some banking apps and Pokémon GO. For Heroes, the purpose is most probably to block any kind of cheating in the game. If your device does not pass this check, the game won't even show up in Google Play when you search for it. You will get the error in the game after some time has passed after the initial installation. Now, some people may have encountered this error even if they haven't modified their phone in any way. Why? Because some devices (especially Chinese brands) have already been set up in the manufacturing process in a way that Google does not find OK. There's also apparently a known bug that causes the error code even for devices that pass SafetyNet. It is unknown if this bug has been fixed. For those who know that their device is modifed, here are some things you can try to get around SafetyNet:
I don't need root or Xposed
Install the latest SuperSU from Google Play (or APKMirror, if you can't access Play), if you don't already have it.
If you get prompts when launching the app, ignore/cancel them.
Go to settings, scroll down to the "Full unroot" option and tap it.
Press continue, wait until it's done.
Method I – Recovery mode
Download the latest Xposed uninstaller .zip from here.
Flash the .zip in your device's recovery mode.
Method II – Xposed Installer
Install the Xposed Installer .apk from here (Android 4.0.3—4.4) or here (Android 5.0/5.1/6.0), if you don't already have it.
Find the tab that has your version of Xposed.
Press the uninstall button, confirm.
Wait until it's done.
Still not passing? Make sure that your SELinux is set to enforcing (you can check this from Settings → About phone → SELinux status). Permissive SELinux is known to trigger SafetyNet. You may need to use a different ROM/kernel with enforcing SELinux. Also, make sure you don't have any su binaries left in /system/bin or /system/xbin.
Install Magisk Manager from Google Play (removed from Google Play as of June 1st) from XDA.
Go to the Settings section, enable Magisk Hide.
Go to the Magisk Hide section, find FE: Heroes on the list and tick the checkbox.
I don't have systemless SuperSU:
Install Magisk Manager from Google Play (or from XDA, if you can't access Play).
Go to the Settings section, enable Magisk Hide.
Go to the Install section, default settings should be fine.
Tap Magiskify, choose "download & install".
Wait until it's done.
Go to the Magisk Hide section, find FE: Heroes on the list and tick the checkbox.
If you don't know if you have systemless SuperSU or not, install Magisk Manager. It will tell you if you have it in the Status section. In the installation process, Magisk will automatically remove any existing root solutions and replace them with MagiskSU – unless you have systemless SuperSU, in which case Magisk will use it instead. But Magisk Hide only works with MagiskSU, so SuperSU first needs to be uninstalled. After installing Magisk, you won't need any external root manager apps you might have (like SuperSU or Superuser); Magisk Manager has a built-in superuser manager.
Method II – Root Switch (Android 4.4+)
Install the Root Switch 22.214.171.124 .apk from here (official thread is here, but I copied the file to Drive to save people from registering to the site).
Enable "Stop all su daemons" & "Toggle USB debugging".
Toggle root off.
Make sure to turn root on again whenever you're not playing the game – you may lose root if you have it turned off when you reboot your device!
I want to keep Xposed
Only for Android 6.0+. This method is unstable and is known to cause bootloops sometimes. There seems to be problems especially if your system's security patches are from November or later (you can check this from Settings → About phone → Android security patch level). Proceed with caution.
1 – Installing suhide
Uninstall any Xposed version you may have on your device currently (steps above).
Download the latest suhide & Xposed v86.2 by topjohnwu from here.
In your device's recovery mode, flash the suhide .zip, then the Xposed .zip.
Reboot (and hope for the best).
2 – Blacklisting the game:
Open a terminal of your choice and get root rights with the su command. You can also use the terminal in your recovery mode, if available.
Get the UID of FE: Heroes with the command ls -nld /data/data/com.nintendo.zaba. The UID is the second number displayed, usually in this format: 10xxx.
Add FE: Heroes to suhide's blacklist with the command su/suhide/add UID (replace UID with the number you got with the previous command).
Install this GUI from Google Play (or from GitHub, if you can't access Play).
Find FE: Heroes from the list and tick the checkbox.
And for all steps: remember to grant superuser rights whenever prompted. If you can't pass SafetyNet after these steps, it may be that your kernel does not hide an unlocked bootloader, which is known to trigger SafetyNet. You may need to switch to a different kernel. The most popular ROM, LineageOS, is known to not hide the bootloader status, since they want to comply with Google's security policies. Removing deviceAccount:.xml from /data/data/com.nintendo.zaba/shared_prefs/ or reinstalling the game also gets around the error, but only for a short time. Remember to link the game to your Nintendo Account before doing this, otherwise you will lose all progress in the game. User NeffeZz has also created a helper app for rooted devices, which automatically removes the .xml file and restarts the game, you can check it out in this thread. Unfortunately, there are some devices (again, usually from Chinese brands) which won't pass SafetyNet with any of these methods. For example, devices with built-in root which cannot be removed. Magisk Manager has a built-in SafetyNet checker, but if you don't use Magisk, you can install a separate app, e.g. this one. Results may not be 100 % correct. Also, keep in mind that the game might store the info that your device was not allowed once. Even if your device now passes SafetyNet, you may need to reinstall the game. If you know of any other methods or maybe find a mistake, please tell me on the comments and I will edit this post. I'll try to answer any questions about this, but I do have to work and sleep too! Disclaimer: I am not responsible for any data loss or damage on your device and I can't guarantee these methods will work for you.Always make sure to have a backup.
Timur's Kernel v4.0-Final b105 for Android 6.0.1 MOB30X
First the download link: New Download Location (md5sum 1b532a32dcbd518b3f0651a95393cc83) "timur-kernel-n7-2013-v4.0-final-flo-deb.zip" contains the installer files for both Nexus 7 2013 models: flo + deb.
Important: To enable the special features of this kernel, you need to use an "OTG charging Y adapter". And to keep your Nexus 7 2013 always charged, this needs to be a high-quality OTG adapter. Low-quality OTG adapters are often limited to 500mAh. This is not good enough to operate a Nexus 7 2013 and to keep it also fully charged at the same time. You need to use an OTG adapter capable of passing through 2000mAh. This link shows you the forum search results for "OTG". You may also want to search for "charge", etc.
REQUIRED FILES for Nexus 7 2013 Wifi-only / flo (razor):
USBHost kernel (deb601) + service installer (both in: timur-kernel-n7-2013-v4.0-final-deb.zip)
Here I describe how you can upgrade your tablet to Android 6.0.1 MOB30X, install Timur's Kernel v4.0 as well as root, without losing any apps or settings - and do so in under 20 minutes. To do this, your tablet bootloader needs to be unlocked once (see below: "Before you install"). If you already have a rooted Android 6.0.1 MOB30X with TWRP installed on your tablet, the kernel installation can be done in just a few minutes. In this case, reboot into TWRP and continue with step 4.
Unzip the target Android 6 MOB30X factory image on your PC. In order to prevent the factory image installation from wiping the data partition of your tablet (if you want to keep your installed apps, personal settings and custom data), you need to edit your flash-all script (.sh or .bat, depending on what OS you are using on your PC). To keep your apps and data, remove the "-w" parameter from the last line. However, if want to delete everything on the tablet (wipe) and fully start from scratch, do not modify the flash-all script (keep the "-w" parameter in). Before you continue, this is your last chance to create a full device backup of your tablet. For instance, you can create a full device backup in TWRP recovery.
To install the factory image, connect the tablet to a PC via USB and run the (modified) flash-all script. The installation process will take a couple of minutes. This is IMPORTANT: You need to watch the tablet screen closely, because you need to prevent the tablet from booting into Android automatically at the end of the installation process. As soon as you see the tablet screen turn off, you need to quickly press power + vol-down and keep both buttons pressed for about 15-20 seconds. This will abort the boot process and instead, the tablet will return to the bootloader menu. You need to keep pressing the two buttons until you actually see the bootloader menu. This is when you can release the buttons. The point of all this is, to install TWRP and SuperSU BEFORE the newly installed Android system boots up for the first time.
With the tablet in bootloader (you may need to disconnect/reconnect the PC-USB connection), you can now install TWRP recovery. You always need to do this, because flash-all will overwrite a previous instance of TWRP. To continue, enter in a command line window on your PC: "fastboot flash recovery twrp-3.0.2-0-flo.img" (if you have the LTE model, use the img-file of the deb variant). When done (only a second later), you should be able to launch the newly installed TWRP from bootloader menu. Use the volume keys to select "recovery" and then hit the power button to launch TWRP.
With TWRP recovery running, the tablet should now appear as a USB drive on your PC. This lets you copy the three zip archives required for the next step over: timur-services, timur-usbhost and SuperSU. Make sure these three files are available on the tablet's internal sdcard. Then install the three zip files (timur-services + timur-usbhost before SuperSU!), using the TWRP on-screen UI. Note that whenever you update the kernel (usbhost), you will also need to re-install SuperSU afterwards. - OK, done. You can now restart system and boot into Android OS.
On first boot after installation: Do not immediately open PowerEventMgr. Instead, let the system rest in Launcher for a minute. You should see a SuperSU permission dialog show up for PowerEventMgr (PEM). Grant root access to PowerEventMgr. You can now open PowerEventMgr and, for instance, enable FI-mode and fast charging.
VCam2 app will be installed (or updated) when you launch PowerEventMgr and click the "Launch VCam [Exec]" button. If you intend to use VCam2, you should click this button once, every time you have installed or upgraded the kernel (usbhost installer) via recovery system. Launching VCam2 for the first time will bring up a SuperSU permission dialog. It is necessary to grant VCam2 root permissions.
It is also possible to install VCam2 manually, by opening VCam2.apk from the /sdcard/ folder (say, using a file manager app). Once VCam2 has been installed (or updated), the file /sdcard/VCam2.apk can be deleted.
It is suggested you disable SuperSU toast messages for PowerEventMgr and VCam2. To do so, open SuperSU app, select PowerEventMgr and change the Notifications setting from "Global defaults" to "Disabled". Hit the check mark to store the modified settings. Now do the same for vcam2. And hit the check mark again to store the modified settings.
Once installed, you need to add the "adb" and "fastboot" tools to your PATH environment variable. So you can use these tools from anywhere and for the "flash-all" script to be able to find the fastboot tool. Now enable the "USB debugging" feature on your Android device. In order to do so, open Settings and then open "Developer options". If you cannot find "Developer options" in the list, go to "About tablet" and click the "Build number" five times in a row, until you see a toast message, telling you that: You are now a Developer. Now leave "About tablet" and you should be able to see and open "Developer options". Under "Developer options" you should now be able to enable "USB debugging". While you are in "Developer options", you may also want to enable "Stay awake". This feature is useful, if you want to use the FI-mode feature. With your tablet connected to the PC, you should now be able to open a command shell on your PC and run the following commands. This is for testing connectivity only:
adb shell date
This should display the current time and date of your Android device on your PC. If this doesn't work, try the following:
This should show the "List of attached Android devices" in the command shell on your PC. If this does not show at least one Android device (with a serial number and a name), you should try unplugging and reconnecting the USB cable. You may need to confirm ADB connectivity in a dialog box on your Android device. If you are not able to establish ADB-over-USB connectivity, google for "adb windows" and/or "adb windows usb drivers". And possibly install/update the required USB drivers. Continue only, if the adb tool is working properly.
Unlocking the bootloader If your tablet's bootloader is not yet unlocked, you need to unlock it now. This can be done in two quick steps by running the following commands in the command shell on your PC:
adb reboot bootloader
And then, when the tablet shows the bootloader screen, run:
fastboot oem unlock
NOTE: Unlocking the bootloader will fully wipe your device. You need to confirm the unlocking procedure on the device screen. As long as you don't lock your bootloader again, you only need to do this once.
umountAll() will now abort running mountAllBlkid()
mountAllBlkid() will wait up to 9000ms (from 20000ms) (TEST undone)
loss of ext-power will now abort waiting mountAllBlkid()
TEST: mountAllBlkid() will wait up to 20000ms (from 9000ms)
prevent early audiofocus release, if mountingFlag is set
audioFocus.releaseFocus() postpone by 800ms after mediaScannerRunningFlag turns off
mountAllBlkid() will wait up to 9000ms (from 8000ms)
moved audioFocus.releaseFocus() post drive mounting
FIX: on USB_DEVICE_ATTACHED during wake-from-suspend, even if isBootCompleted is (falsly) cleared due to process termination, we make sure that mustMountDrivesOnBootCompleted will be set and will be processed later, either on: 1. on BOOT_COMPLETED event, or 2. 8-sec post POWER_CONNECTED event
despite FI-mode suspend-transition being aborted, via OTG unplug (USB_DEVICE_DETACHED skip busy umount + POWER_DISCONNECTED), all mounted USB drives could stay listed in PEM as being attached/connected - FIXED
FIX: powerConnectedState now keeping correct state during BOOT_COMPLETED + USB_DEVICE_ATTACHED
build 96 "v4.0-RC2":
initial port of "v4.0-RC1 build 95" from "MOB30P" to "MOB30X"
Updated method to root, install TWRP, and CyanogenMod. (Or any custom ROM.)
I noticed the guide on the sidebar hasn't been updated in awhile, so I decided to make this post to help others. I hope this helps you guys, good luck! THIS GUIDE IS FOR ALL VARIANTS OF THE LG G3 Rooting: There are many methods that I have found that work on both Kitkat and Lollipop. Method 1 Method 2 LG has been patching exploits in the latest updates, so if the first 2 don't work, give this method (Method 3) a try. It's based on method 1 but modified a little bit. If you are experiencing difficulty in rooting, please try the "fix" below: This only applies to method 1 and 3. Step 1: Open the folder which contains the root, ADB drivers, etc. Step 2: Hold shift and right click on blank space of the folder, then click "Open CMD here". Step 3: Type "adb devices" to start the daemon process. See Note below Step 4: Unlock your phone. You should see a box with an MD5 number and a check box. Check "Always allow from this computer" and then hit "OK". Note: You may need to type this a few times. PLEASE READ:Many users are experiencing difficulty in rooting lately. I do not know why - It may be LG and/or their carrier has been patching exploits in the recent update, it may be the user did not follow the steps correctly, etc. Either way, I have found 2 new methods/tools. They are below: Method 4: I have not tried this, so please let me know if it works. Method 5 This is an apk file, which suprisingly works up to Android 5.1.1. Yes, it is an app that roots Lollipop! Virtually unheard of right? Chinese people are fantastic with electronics lol! For method 5, it installs there "KingUser" instead of SuperSU, HOWEVER, you can install SuperSU after rooting. Heres how: Step 1: Follow any of the methods for installig TWRP below. Step 2: Download SuperSU zip from here. Step 3: Reboot to TWRP using a reboot app or widget, etc. And flash the zip. Step 4: Reboot system, download system apl remover or a similar app, and unistall KingUser. Step 5: Go to SuperSU and update the binary if needed and reboot. Step 6: You should now have a working SuperSU application and root! Method 6 (For LS990ZVA) This method is for the LS990ZVA, as the other methods included in my guide aren't working for them. Thanks, Ferroseed :) In the unlikely case that not a single method above worked, don't worry my friend, you still have hope! Please note: The method below is a last resort, so please don't do this unless you absolutely can't root your phone and have already tried everything, as well as double, triple, or even quadrupole checked to make sure you are doing every step for every method word to word. YOU CAN ALSO USE THIS METHOD TO UNBRICK YOUR PHONE! Follow this guide to flash back to KitKat. Once done, go through the setup process, etc. and install Stump Root or Towelroot. This will root your phone. To install TWRP, use method 2 below or just download the image from here and install Flashify from the Play Store. Open Flashify, grant root access, chose "Flash Recovery", chose your file, select "Yup!", and reboot. Done! Note: If you're still on Kitkat, give Stump Root or Towelroot a try first. Rooted? Good, now let's move on to installing TWRP! Installing TWRP: There are currently two methods to flash TWRP. I tried method 1 and it worked without any issues, so I recommend it. Method 2 is currently causing issues for users, use method 1. Method 1: Step 1: Download Flashify from the Play Store. Step 2: Download the TWRP image for your device from here. Step 3: Open Flashify and grant it root access. Step 4: Select "Recovery Image" and select the "Chose File" option, select the image you just downloaded. Step 5: Chose "Yup!" and then reboot when it prompts you too. [Method 2 ](In my experience this Method has the highest chance of success and is the easiest.)](http://forum.xda-developers.com/lg-g3/general/apk-flash-twrp-autorec-thanks-to-t3081396) Warning: Users are reporting Security Error at boot after using the app to flash TWRP. Use method 1. Got TWRP installed? Fantastic! We're almost there! Installing CloudyG3 2.5 Step 1: Download CloudyG3 Step 2: Once downloaded, open TWRP manager and reboot to recovery. Step 3: Once in recovery, make a backup. (ALWAYS make a backup!!!) Step 4: Now hit back until you're at the home screen. Select wipe and then advanced wipe. Check the boxes for data, system, dalvik, cache. Hit wipe and wait until finished. Step 5: Now hit back until you're at the home screen. Hit install and navigate to the download folder. Select CloudyG3 and hit install. Step 6: CloudyG3 has an Aroma installer. Select your model and other preferred options. Once done check reboot now and wait for it to reboot. NOTE: CloudyG3 takes some time to boot up on the first boot, so don't worry. It will boot up. Flashing Gabriel Kernel (Stock-based ROMs only) and Tweaking the Kernel Step 1: Download Gabriel Kernel from here. Step 2: Once downloaded, reboot to recovery. Step 3: Navigate to install and select the Gabriel Kernel zip. Step 4: Swipe to install and reboot. Step 5: Download kernel auditor via the Play Store. Tweaking the Kernel To tweak Gabriel Kernel, AllSpark kernel settings must be applied first. Download and flash them in recovery here. Now that you have applied AllSpark settings, you can start to flash other settings. HotrodV1 (Performance with good battery) IronhideV2.1 (Very good battery, good performance) - This setting is my favorite. I get around 5-5 and a half hours with it, heavy usage. The performance is also very good. JetfireV1 (Performance with battery) OptimusPrimeV1.2 (Best all-rounder) build.prop tweaks This will add and tweak some things in your build.prop file to help battery life and performance a little. I did notice a slight difference. Original thread for kernel settings Original Gabriel Kernel thread Installing CyanogenMod Step 1: Download the latest Nightly for your devices model number from [here.](download.cyanogenmod.org) Step 2: Download the latest gapps from here (Google Apps. These are required if you want the Play Store, Gmail, etc.) Note: There are many other better Gapps out there, such as Banks Gapps, TK Gapps, etc. All of these can be found with a quick google search. Step 3: Use TWRP manager or a reboot manager such as Simple Reboot, quick reboot, etc., to reboot into recovery. Step 4: Once in recovery, select wipe, then advanced wipe. Check System, Data, Dalvik, Cache. Step 5: Go back to the home screen and select Install. Navigate to the Download folder and select the CyanogenMod zip. Step 6: Select "Add Another Zip" and navigate to the Download folder again. Select the gapps zip. Step 7: Select install now and wait for it to flash the Zips. Step 8: Select reboot now and then you're done! Flashing Nebula Kernel (CM/AOSP/Slim-Based ROMs Only) Step 1: Download Nebula Kernel from here. Step 2: Reboot to recovery and flash (no need to wipe anything). Step 3: Reboot and you're done! Tweaking the Kernel First and foremost, you'll need to download Kernel Aduitor from the Play Store. The best combination that I've found is the followimg:
CPU Governor set to zzmove.
Profile_Number set to 2 (ybat/yank battery) (Profile_Number is in "Governor Tunables)
These settings are a great performance/battery combination. Easiest way to install Xposed: Step 1: Download the apk from this link. Step 2: Grant it root access and hit the install button. (It takes a little time to respond so don't worry) Step 3: It will now automatically boot into TWRP. Wait for it to finish and now it will automatically reboot. Step 4: Wait for the optimization of the apps. That's it. Extremely easy, right? To thank bender_007 over at the XDA thread! EDIT:Kernel and guide to disbale over sharpening EDIT 2: CyanogenMod and CloudyG3 are now both in the guide! DISCLAIMER: I am NOT responsible for any damage that can/could be caused to your LG G3! You are doing these steps at your own risk! Doing these modifications to your device may void your warranty. I am NOT responsible for that either. However, if you follow these steps correctly, you should not receive any damage to your device. I hope this guide helped you and good luck!
[Guide] Updating your bootloader-unlocked Moto X to 4.4.4 via OTA
I've seen several posts over the last few days with people wondering how to upgrade their bootloader-unlocked Moto X to 4.4.4 using the over-the-air (OTA) update, so I figured I'd post a quick guide so that anyone in this situation can update their device with minimal hassle. The process is fairly straightforward, but some people may not have done it before, and even those who have may enjoy a refresher! This post is for devices with unlocked bootloaders -- I don't really have experience with the root methods used on locked Moto Xs, so I can't help anyone with that. These exact steps are also specific to the Verizon update rolling out now, but the same general process should apply to other OTAs and other carriers. I'm also assuming that you have a custom recovery and a rooted device and that you want to restore those after the upgrade -- if you haven't modified the recovery you can probably install the OTA as-is with no issues. What do I need to install the OTA? In order to install the OTA, your device needs to have the stock recovery and an unmodified /system partition. What does this mean?
If you've installed TWRP as your custom recovery, you'll need to revert to the stock recovery.
If you've installed the Xposed framework, you'll need to disable it (but you won't lose any modules or settings)
If you've made any other changes to files under /system, you'll need to revert those (an example would be the modified tethering check APK that was making the rounds a while back)
Preparation Before you get started, make sure you have the following files:
The OTA itself, either ready to install from the carrier or as a downloaded zip file. The Verizon Moto X 4.4.4 file can be found here if you haven't received the OTA push yet (scroll down to the first comment). Put this file on your phone.
The original 4.4.2 recovery.img. This can be obtained by downloading the 4.4.2 factory image either from Moto's site or from droid-developers.org. The factory image should be a zip file around 700MB; the recovery.img you need file will be found inside. This file needs to be on your PC as we'll be flashing it to the phone using fastboot.
The original 4.4.2 system.img, found in the same zip file, will also be handy if you know that you've made changes to /system or if you just want to make sure. Put this on your PC as well.
If you want to re-install a custom recovery (such as TWRP) after applying the update, have that image file ready to go on your PC too.
You will lose root by updating; assuming you plan on rooting again after installing the update, go ahead and make sure that the .zip for your su package of choice is on your phone. I prefer SuperSU.
You'll also need access to a PC with the android adb/fastboot tools and the drivers installed for your phone. I've found that the easiest way to make sure you have the right drivers for the Moto X is to install the Motorola Device Manager, which should set up the correct drivers during installation.
Finally, you will need the motorola-specific fastboot binary, also known as 'mfastboot', in order to flash the system.img file as the stock fastboot fails due to the image being too large. This file should be found within the factory image that you downloaded from Motorola, in the 'Windows' folder (or 'Linux' if that's your platform). Rename the fastboot.exe file in that directory to mfastboot.exe and put it in the same directory as your existing adb/fastboot executables. (If your image does not contain the fastboot file, you can find a copy on Google -- one link can be found on this page.)
And one final note, make a backup of any important files on your phone. If everything goes correctly you should not lose any data, but since we're messing around with system files on the phone there's always the chance that something catastrophic could happen resulting in the need to wipe the device. Better to be safe than sorry! The Process
If you're using Xposed, the first thing we need to do is disable it for the duration of the upgrade. To do this, boot into your recovery (probably TWRP), and install the 'Xposed-Recovery-Disabler.zip' file that you should find at the root of your storage. This file is created automatically during the Xposed installation process, and will disable the framework without removing any of your installed modules or settings. If you don't have the disabler zip or you're otherwise unable to flash it, you can also just hit the 'uninstall' button within the Xposed installer app to do the same thing.
Flash the stock recovery
Next, reboot your phone into the bootloader. You can do this by shutting down the phone and then holding the power + volume down buttons to power it back up. (The bootloader screen may not actually show until you release the buttons, so if you don't see anything for ~10 seconds just let them go and it should pop up.) If you were already in TWRP after the previous step, you can also just reboot to the bootloader from there. Once you're at the bootloader screen, plug your phone into your PC. Open a command prompt in the directory where your fastboot executable is located, and run the command 'fastboot devices'. The tool should print a line showing the serial number of your device and its current state, which is 'fastboot'. If you don't get any output from this command, then your drivers are probably not installed correctly -- check your device manager to see if you have any unrecognized devices, and try reinstalling the Moto device manager to get the proper drivers. Assuming fastboot recognizes your device, the next step is to flash the stock recovery. You need to tell fastboot where the recovery.img file is -- the easiest way is just to copy it into the current directory; alternately you can provide the full path to the image instead of just specifying 'recovery.img'. The command you need to run is:
fastboot flash recovery recovery.img
The phone will flash the stock recovery and let you know when it's done.
Flash the stock system image
This step is optional, but recommended. The OTA installer is going to verify a number of files on your device's /system partition, and if any of those files have been modified, the update will refuse to install. If you don't feel that you've made major changes to your device aside from rooting and installing Xposed, you can skip this step and hope for the best. If it turns out that you do have changes that conflict with the update, the OTA will fail to install and you'll need to either manually restore the modified files or come back to this step and flash the stock system image before trying again. If you want to be certain that the OTA will install without issues, I'd recommend flashing the stock system image now. Note that /system does not contain any user-space apps or data, so you shouldn't lose any information by resetting it. Just like flashing the recovery.img, you need to have your phone at the bootloader screen with fastboot ready to go, and you need to have the system.img file handy. This time, however, you'll need to use the Motorola fastboot utility since the system.img image is too large for the stock fastboot tool. The the command to run is:
mfastboot flash system system.img
The system image is fairly large (around a gigabyte) so it may take up to 10-15 minutes to completely install. Be patient!
Install the OTA
Now your device is ready to accept the OTA upgrade. If your phone has already prompted you to install it, then you can boot back up into Android and begin that process from the notification, which will reboot the phone into recovery and start the upgrade automatically. If you're using the downloaded .zip file instead, then select 'Recovery' from the bootloader menu to enter the stock recovery. (Remember that 'volume up' is the select key -- if you hit the power button instead your phone will just power off!) Now you should see a green android icon with a red triangle on it. This looks scary, but don't worry! If you press the power+volume up buttons, the actual recovery menu should pop up. Select the option to apply an update from your storage, then select the OTA zip file that you downloaded earlier. The install process should begin and will take several minutes.
Re-flash your custom recovery
Once the install process is complete, you'll be back at the recovery menu. Select the option to reboot the device, but hold down the power+volume down buttons as it restarts -- we're going straight back to the bootloader to flash our custom recovery. In the bootloader, make sure that the phone is plugged into your PC and that you have the custom recovery .img file handy, then run the command to flash the new recovery file (I'll assume most people are using TWRP, but substitute the name of your own image file if necessary):
Assuming you want to root the device as well, go ahead and enter the custom recovery you just flashed and install the SuperSU package or whatever you normally use.
Boot into Android
Now you're ready to boot the system up. It will take a little longer than normal, and you'll see the 'Optimizing apps' screen as the device rebuilds the dalvik cache files for each application. Once everything is up and running, head into the Settings -> About Phone menu and check your Android version. You should be on 4.4.4!
Re-enable Xposed (or other root applications)
The final step is to re-enable any root applications that you have installed. For Xposed, just open up the Xposed installer app and hit the 'install framework' button. You'll need to reboot in order to activate the framework, but afterwards you should find all of your modules and settings exactly how you left them. Other root apps may also need to be re-enabled or re-activated; check each one and make sure it's doing whatever it's supposed to do. For example, if you're using AdAway you'll need to re-apply the host file modifications. You're done! And that's it! The whole process should take no more than 20-30 minutes if you already have the files you need, and you shouldn't lose any data or settings during the upgrade. Now that you're on 4.4.4, check out the new dialer as well as the Motorola Alert app! Good luck to anyone upgrading, and let me know if there are any changes/updates that need to be made to the guide.
Visual Land Prestige Elite 10QL : Want to root, run Xposed Frameworks or custom ROM... Problems!
I would like to first root, then use Xposed Frameworks or a custom ROM on my recently purchased Visual Land Prestige Elite 10QL. I am trying to root it straight out of the box. Meaning I haven't even used it yet! :-) Why? Remove bloatware, move files/apps/etc. to SD card, CUSTOMIZE!!! I am running Lollipop 5.0. I am a novice android tinkerer. I am learning, so give me some slack for my learning curve here, please. :-) I got it to root using Kingo Root. Great... So, then I went to install Super Su, but it gets a pop-up stating "the su binary needs to be updated. Continue" If you pick the option to continue, you get "If you have a custom recovery like TRWP use to install the su binary. How would you like to install?" Options: normal or TRWP/CWM Soooo, I don't have a backup (I know, BUT like I said it is new and I don't have anything on it, so I did not do a nandroid or any other backup) or I pick Normal and it just tells me to reboot and try again. Having read everywhere about this issue... there are varying opinions. YES, I am rooted. I tried adding the binary apk file to my SD card, then opening in recovery mode to install the file. But no luck, Super Su won't install properly or at all, I guess. So, my issue is I am rooted, but without a program like Super Su to KEEP me rooted through updates. All else on my list is null and void w/o root. YAY! I just got the first problem SOLVED! Used an app called Super Sume, which replaces all of the Kingroot files with SuperSu files. Then SuperSu installed successfully and I am still rooted. Wow! I searched all around for a solution and found this in a forum, way, way down deep. Others with Kingroot/SuperSu/missing binary problems should use this app. Now, custom ROMs. Which allow most customization? Anyone know of any that are compatible with VL Prestige Elite 10 tablets? Xposed Frameworks, please explain what custom recovery is... do I do this by downloading an app like TRWP (is that an app?) or flash a file ? I just can't find what I need to get this started. All directions something similar to: You must have a rooted device with custom recovery installed in it to use this Official Xposed Framework...) Explain please.... I guess that is all, THAT is enough! LOL Sorry so long, just thought better explanation will help get answer. Thanks!
[HELP] After Lollipop ROM update, PAD won't start.
Pardon the upcoming text wall... Just trying to get as much info out here so maybe someone can have the best chance to help me. I have a Samsung Galaxy S5 (DoCoMo branded SC-04F/SM-G900D). I was using a stock rooted ROM on Android 4.4.2 and felt the need to upgrade. Backed up EVERYTHING with TiBackup and Dropboxed it so that's not a concern. Upgraded process went smoothly, but now my PAD opens to a black screen with a teal bar on top that says 'PAD'. Troubleshooting done so far, but to no effect * Cleared PAD cache and re-installed. * Cleared Google Play Store cache, uninstalled updates * Cleared Google Play Framework & Services cache (trying to reinstall G-services right now - slow mobile connection :-/ ) * Google Play app opens to a mostly gray screen with menu options. Cleared the cache on it as well. * Tried hiding the su binary with 'Hide my Root'. SpaceX has the SuperSU apk by default. (I've read online that I should also rename the Superuser.apk, but I'm not quite sure how to do that). If anyone has any tips or other things I can try, then I'd greatly appreciate it. Worse comes to worst, I guess I could always try upgrading my phone to the Stock Lollipop rom, root it and then manually remove all the DoCoMo bloatware (blah...). Many thanks in advance for any help! EDIT: More Details. I'm on the NA server. Google Play Services reinstall didn't help.
I have been trying for some time to mount my media share as a local drive on my NVidia Shield TV. I am in need of some expert help on the matter because I've had no success. I'm going to post the steps I've taken to get the job done and am hoping someone will be able to point out a missing step or tell me what I've done wrong. Thanks to anyone who takes the time to take a look at this. I realize that below is a pretty massive brain dump. Here's the steps I've taken to get this working:
I then used this app to set the SELinux mode to permissive.
Using CifsManager, I've made several attempts to save the mount settings so that I can mount my network share at will. I'll paste those attempts and their resulting error messages below.
*The above steps are in accordance with the tutorial on mounting network shares on nvidia shield TVs at https://forums.geforce.com/default/topic/856208/shield-android-tv/-guide-how-to-mount-a-network-share-into-the-filesystem-root-/. You probably don't need to do much research to see that I've also asked for help in the comments of aforementioned tutorial. Here are my CifsManager share configurations and the resulting messages I receive when I attempt to mount using those configurations: Share path: 192.168.2.1 Mount point: /data/media/0/external Username: guest Password: Options: rw,file_mode=0777,dir_mode=0777,iocharset=utf8,context=u:object_r:rootfs:s0 Result: Invalid argument Share path: 192.168.2.1/Public Mount point: /data/media/0/external Username: guest Password: Options: rw,file_mode=0777,dir_mode=0777,iocharset=utf8,context=u:object_r:rootfs:s0 Result: Cannot access a needed shared library Share path: 192.168.2.1/Public Mount point: /data/media/0/external Username: guest Password: Options: rw,file_mode=0777,dir_mode=0777,context=u:object_r:rootfs:s0 Result: Invalid argument Share path: 192.168.2.1/Public Mount point: /data/media/0/external Username: root Password: Options: rw,file_mode=0777,dir_mode=0777,context=u:object_r:rootfs:s0 Result: Invalid argument Share path: 192.168.2.1/Public Mount point: /data/media/0/external Username: root Password: Options: rw,file_mode=0777,dir_mode=0777,iocharset=utf8,context=u:object_r:rootfs:s0 Result: Cannot access a needed shared library Share path: 192.168.2.1/Public Mount point: /data/media/0/external Username: guest Password: Options: Result: Invalid argument I need to note a couple of things here before I finish this post:
192.168.2.1 is the correct IP for my network share. I can access it via ES File Explorer as an SMB share in this way.
I don't need a username or password to access my share, but CifsManager does not allow you to save a configuration without the username filled in. I don't know if that has anything to do with my problem.
My goal here is to be able to access the files on my share locally so that apps that cannot take advantage of SMB functionality can still access data on the share. The Dolphin GCN/Wii emulator is one such app.
My device: Samsung Galaxy S2 Duos TV S7273t (Brazil). Issue: Freezes at "connecting to the game server" (only Global server)
I did root on it, because i wanted to delete pre-installed apps. I used this chinese apk to do this, in one click: ROOT APK and video.
After that, everything worked properly, except SW. The game closes on the "Connecting to server game" screen. After that i tried:
Used an app to hide ROOT: Hide my ROOT, ROOTCLOAK,...(Nothing)
Intalled SuperSU, update the binary, and it asked if i want to delete chinese app, i accepted and rebooted. With SuperSU working, i tried the same apps to hide the root.....(Nothing)
In SuperSU there was an option called "Remove ROOT permanently". I did it. i did and wipe to the factory data, deleted all downloaded apps, and formated the SD....The phone was "NEW" again, installed SW....(Nothing)
Uninstalled SW, changed language to Korea (it was Portuguese), and installed SW...(Worked)
Even if i change SW and system language to Portuguese, English, or so, it still works, BUT I don´t want to play in Korea server. When i try to change to Global server, SW doesn´t open anymore. It freezes at "connecting to the game server".
Come2us didnt answer me yet. My account is not banned and my phone works well to play the game in another server. Can anyone tell me something i can try to do?
IF YOU DO NOT LIKE THE APP, DO *NOT* JUST UNINSTALL IT, YOU *WILL* LOSE ROOT.Superuser access management runs through a so called "su binary". There can be only one of these at a time. So if you install SuperSU, your previous superuser access management solution will no longer operate. So if you want to switch back: (1) Open that application, and search for an option for it to install/update ... Once you’ve taken that step, you can then start to use SuperSU, which comes with an abundance of features and other cool options. Rooting the phone or tablet extends the use of that device, but all that power also comes with great responsibility. A tool is needed to manage the increased rights on the phone, ... Android SuperSU Pro APK allows app management facility for rooted mobile devices with authorized app installing and system monitoring. SuperSU Root is the secure platform for Android-OS providing no modifications are applied to existing apps by various system changes. Download SuperSU apk for the mobile operating system and optimize the performances or buy Pro SuperSU download version from ... SuperSU Download is the best Superuser access management tool that developed for android devices. Clearly, Superuser access is similar to the administrator privilege on Windows computer. The users are allowed do almost anything on their Android smartphone or tablet under the root status. SuperSU Pro allows for ad advanced management of Superuser access rights for all the apps on your device ... 4AppsApk.com try to give the Latest Version of "SuperSU 2.76 Apk" for ... Superuser access management runs through a so called "su binary". There can be only one of these at a time. So if you install SuperSU, your previous superuser access management solution will no longer operate. So if you want to switch back: (1) Open that application, and search for an option for it to install/update/replace the "su binary". (2) Confirm root-using apps are using the superuser ... SuperSU APK. Rated 4.28892/5. SuperSU. 500305 votes, 4.28892 / 5. 84comments. 500,305views. Download APK Google Play Store. TAGS # supersu beta # supersu apk download for gear # supersu apk zippyshare # super suds # supersu apk 2.45 # supersu # supersu binary # supersu apk xda # supersu apk 4shared # supersu apk install on samsung s3. Free . Codingcode. Tools . 2.77. 6.18 MB. SuperSU. SuperSU ...
How to Solve Supersu binary occupied 100% work 2020
How to install Supersu binaries on the HTC One M8 - Duration: 3:08. ILIVE4HEAD 27,283 views. 3:08 . How to Replace Chinese (VRoot) Superuser with SuperSU - Duration: 2:00. MrW0lf 344,499 views. 2 ... Link supersu 2.65 apk: https://www.mediafire.com/file/6n9x79tu8bqz9y8/ Please subscribe 🙏🙏 ---The SuperSUMe app that i linked is old. It will most likely not work anymore. If you want the best results & support the app creator please download the p... Hello Guys Today I'm Going To Show You How To Fix SuperSu Binary Occupied. Note: This Problem Arises For Rooted Users Only. This Method Works For Android Dev... Simple Trick to Solve SuperSU Binary Occupied bug on BlueStacks. This problem is appeared after installing SuperSU latest version (v2.82) from Playstore or o... Fixed "SuperSu Binary Occupied" (Working 2020) - Duration: 3:27. ... SuperSU Me: Replace Kingroot with SuperSu app with one click - Duration: 2:31. Rootjunky.com 570,296 views. 2:31 . How to root ... Mengatasi SU Binary occupied , how to solve? caranya simple : - download SuperSU fix occupied.apk [link] https://goo.gl/W7Y3i2 - Uninstall SuperSU sebelumnya...