SuperSU Root Download v2.8.2 - Official SuperSU Download Links

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.
submitted by jayecal to MMXDive [link] [comments]

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.
echo "SYSTEMLESS=true" > /data/.supersu
You're Done! Go ahead and install your modules in the Material Xposed App. To enter Pokemom Go, toggle root switch within the app.
submitted by TheJakeGaming to TheSilphRoad [link] [comments]

[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

Removing root:

  1. Install the latest SuperSU from Google Play (or APKMirror, if you can't access Play), if you don't already have it.
  2. If you get prompts when launching the app, ignore/cancel them.
  3. Go to settings, scroll down to the "Full unroot" option and tap it.
  4. Press continue, wait until it's done.
  5. Reboot.

Removing Xposed:

Method I – Recovery mode
  1. Download the latest Xposed uninstaller .zip from here.
  2. Flash the .zip in your device's recovery mode.
  3. Reboot.
Method II – Xposed Installer
  1. 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.
  2. Find the tab that has your version of Xposed.
  3. Press the uninstall button, confirm.
  4. Wait until it's done.
  5. Reboot.
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.

I want to keep root

Method I – Magisk (Android 5.0+)

I have systemless SuperSU:
  1. Do a full unroot (steps above)
  2. Download the latest Magisk .zip from XDA.
  3. Flash the .zip in your device's recovery mode.
  4. Reboot.
  5. Install Magisk Manager from Google Play (removed from Google Play as of June 1st) from XDA.
  6. Go to the Settings section, enable Magisk Hide.
  7. Go to the Magisk Hide section, find FE: Heroes on the list and tick the checkbox.
I don't have systemless SuperSU:
  1. Install Magisk Manager from Google Play (or from XDA, if you can't access Play).
  2. Go to the Settings section, enable Magisk Hide.
  3. Go to the Install section, default settings should be fine.
  4. Tap Magiskify, choose "download & install".
  5. Wait until it's done.
  6. Reboot.
  7. 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+)

  1. Install the Root Switch 1.3.3.2 .apk from here (official thread is here, but I copied the file to Drive to save people from registering to the site).
  2. Enable "Stop all su daemons" & "Toggle USB debugging".
  3. 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

  1. Uninstall any Xposed version you may have on your device currently (steps above).
  2. Download the latest suhide & Xposed v86.2 by topjohnwu from here.
  3. In your device's recovery mode, flash the suhide .zip, then the Xposed .zip.
  4. Reboot (and hope for the best).

2 – Blacklisting the game:

  1. 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.
  2. 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.
  3. 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).
  4. Reboot.
OR
  1. Install this GUI from Google Play (or from GitHub, if you can't access Play).
  2. Find FE: Heroes from the list and tick the checkbox.
  3. Reboot.
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.
submitted by I_get_in to FireEmblemHeroes [link] [comments]

v4.0 for Android 6.0.1

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.
 
Kernel sources: https://github.com/mehrvarz/msm-marshmallow-tm-usbhost-charge
 
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.
 
INSTALLATION
 
REQUIRED FILES for Nexus 7 2013 Wifi-only / flo (razor):
 
REQUIRED FILES for Nexus 7 2013 LTE / deb (razorg):
 
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.
  1. 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.
  2. 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.
  3. 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.
  4. 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.
 
Post Installation
 
Before you install
ADB over USB connectivity
Make "adb" and "fastboot" tools available on your PC. You can do this, by installing the Android SDK:
https://developers.google.com/android/nexus/images#instructions
New: Alternatively, you can use the new standalone binaries provided by Google:
https://plus.google.com/+ElliottHughes/posts/U3B6H3Sejvv
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:
adb devices
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.
 
Release notes v4.0-RC2 + v4.0-RC3
build 105 "v4.0-Final" (aka "v4.0-RC3"):
build 104:
build 103:
build 100:
build 99:
build 98:
build 96 "v4.0-RC2":
 
Previous kernel release threads
I would suggest you read all of these posts.
 
submitted by timur-m to timurskernel [link] [comments]

[Guide] Here's My Attempt At A Rooting Guide For The S7/S7 Edge

Snapdragon S7/S7 Edge Root Guide

I recently moved from a Rooted + Xposed Nexus 6 to a Verizon S7, and wanted to figure out how I could install some of the same tweaks I had on my previous phone. After painful google-fu and combing this subreddit, I finally got my phone working the way I wanted. Here's how I did it, I hope I can help others avoid making some of the dumb mistakes I made.
ps, some of the stuff might seem like complete basics, but I'm covering it in detail to help out fellow noobs.
pps, most of these steps were stolen from this XDA post

Useful info:

What you'll need for root:

The actual root guide:

  1. Create a backup of your data.
  2. Install the Samsung USB Drivers.
  3. Install ADB systemwide. If you have problems with this, or your PC doesn't recognize ADB commands through the terminal, there are quick and dirty ways to get around it, message me for details.
  4. On your phone, go to Settings -> Lock screen and security. Turn off "Secure startup", because it prevents the su (Superuser) binary from providing root.
  5. Connect your phone to PC with a USB cable. Turn on USB Debugging in Developer Settings (if you don't have this, go to Settings About Phone tap the build number 7 times until it unlocks 'developer options'), and change the mode of USB from CHARGING to FILE TRANSFER (MTP).
  6. Create a directory somewhere on your PC where you'll keep all the S7 files (even if you're only keeping them temporarily) to stay organized.
  7. Create a subdirectory called 'odin', and download and extract Odin 3.12 into it. Source 2 for odin (some AT&T users reported that this version prevents bootloop).
  8. Download the rooted boot image for your phone: Boot image for S7 || Boot image for S7 Edge. Note that this download is a .TAR file and while it looks like an archive, you should not extract its contents.
  9. Power off your phone. After that, press and hold the 'Volume Down' and 'Home' buttons. While still holding those down, press and hold the power button as well. Your phone will boot into Download mode. Press 'Volume up' to confirm that you want to enter download mode.
  10. Right click on 'odin.exe', run as administrator.
  11. Click on checkbox next to the the 'AP' button. Then, click the actual 'AP' button, and locate the rooted boot image you downloaded in step 8. Click start to flash it.
  12. When the phone has rebooted, go back and make sure 'USB Debugging' is still enabled. Then, download the SU package and extract its contents.
  13. Start the SuperSU flash package by double-clicking 'root.bat'. If double-clicking 'root.bat' only briefly shows a command prompt that quickly disappears, then most likely your PC is not recognized/authorized for USB debugging, the USB cable isn't connected, or ADB isn't properly installed. Message me and I'll try to help out.
  14. When the phone reboots, CONGRATS, you're rooted. If the SU app asks you to update 'su' binary, dismiss this notice for now as Chainfire, the author of SU, has indicated that this build is unsupported and we shouldn't update.

Recommended Next Steps:

  1. Debloat and fix several issues with the phone (CPU lag issues, poor battery performance, phone becoming too hot, Wi-Fi not saving passwords, hotspot/tethering not working, searching for service issues, MMS not working, unauthorized security nag notification, etc.). I did install this script, but it had some unnecessary shit like call recording. While that's cool, and I might actually use it, it's not everyone's cup of tea. However, it also helped with battery life and some critical errors like the phone not remembering wifi passwords.
  2. Open the SuperSU app (installed during the root process) and tap on Settings Security "Enable su during boot". This will ensure that startup scripts get to do their job correctly.
  3. Install FlashFire. This lets you flash packages like the debloat script, which is the same package for either S7 or S7 edge: fixes only || fixes + debloat
  4. Launch FlashFire on the phone and click the (+) button in the lower right to add a step. Select a 'Flash ZIP or OTA' flash step. Locate the flashable ZIP package and select it. For options, check on 'Mount /system read/write' and leave the rest of the options unchecked. Scroll all the way down and click the 'Flash' lightning button in the lower left to commit this single step and wait a few moments. You should see the phone flash the package briefly before rebooting twice.
  5. Install Xposed. Don't install the normal Xposed from the Xposed site, because it tends to cause a bootloop. Wanam has created a custom build of v85 for the S7/S7 edge: Xposed v85 Wanam || Xposed uninstaller || Xposed Installer Wanam
  6. To install Xposed, launch FlashFire on the phone and click the (+) button in the lower right to add a step. Select a 'Flash ZIP or OTA' flash step. Locate the Xposed flashable ZIP package and select it. Check on 'Mount /system read/write' and leave the rest of the options unchecked. Click the (+) button again to add another step. Select Wipe and only choose to wipe the 'Dalvik cache' and the 'Cache partition'. Scroll down and click the 'Flash' lightning button and wait a few moments. You should see the phone flash the package briefly before rebooting twice. During the final reboot, you will see the animated boot screen appear for a very long time (three to five minutes or longer) before the screen changes to an 'Android is starting...' green screen with animated gears indicating that it is 'optimizing' apps. It is building a new Dalvik cache which should take several minutes. This is all normal; so no need to panic if it takes longer! Once the phone finally finishes booting, you can continue.
  7. Install busybox from the play store. This is a utility which adds a bunch of Unix tools to your phone, which can be useful and is required for certain other tools (like Titanium Backup) to work.
  8. That's it. You're done!

Unrooting:

  1. Check Settings About phone for the baseband version. Mine is G930VVRU4API3. (This matters because after a certain update (PH1?) Samsung changed the bootloader, so if you try to unroot and install any random stock firmware for your device, it might not flash correctly and give you an error. You'll need firmware of your current version or above to successfully flash stock.)
  2. Visit androidfilehost and search your baseband number. Find a result which matches, and download it.
  3. Extract the '.tar.md5' files which start with AP, CP, CSC, BL. Use HOME_CSC if you don't want to wipe the phone during this return to stock.
  4. Right click Odin and run as administrator
  5. Select each appropriate file (click AP, select AP file, etc.)
  6. Select each checkbox
  7. Click start, wait for it to finish
  8. You're done!
this is it! please comment/message me suggestions or edits I should add to make this guide more accurate and informative.
submitted by dangerousdesi221 to GalaxyS7 [link] [comments]

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!
submitted by d850help to LGG3 [link] [comments]

[Guide] Small, simple guide on how to root/flash custom kernel/use EX Kernel Manager/governor profiles

I originally posted this on the nexus5x sub, and I figured ya'll could use this information too. Link.
To start off, this is mainly for Nougat 7.0, but I'm sure the same steps would apply for MM. Not 100% sure on 7.1.1 as I haven't messed around on there much.
First things first, your bootloader must be unlocked. Sorry Android Pay users. Personally, I think an unlocked bootloader is nice to have because it makes recovering your device from a soft brick or whatever else that much easier.
Note: Unlocking your bootloader will wipe everything. Make your backups. I really only need to backup my texts and Nova settings, everything else is in the hands of Google.
Note 2.0: If you use Snapchat, rooting won't let you log-in. So...log-in BEFORE you root. (Do this AFTER unlocking bootloader but BEFORE rooting)
Rooting:
Now what the fuck do I do?
Well, you can now do shit like installing a custom kernel everyone seems to keep bringing up alllllllllllll the fucking time.
Installing Elemental X Kernel:
Before we begin, I should add that without the EX Kernel Manager app, a custom kernel will NOT be useful and you will NOT see improvement in battery life. The app is 4 bucks, it's on the Play Store. It's kinda pricey, I think anyways, but I do think it's worth it for the stuff it does. Now, there are other kernel manager apps, some are free, and they can absolutely be used for Elemental X, BUT I can't help you with that because I've never used them, and these profiles and settings are made specifically for EX. (I'm continuing the guide under the assumption you have the app)
Now what?
Now it's time for some funsies.
Open your EX Kernel Manager app, it may ask for permissions, grant it. Slide the menu from the left, go to CPU>Governor options>Load and see if you have "Glassfish 1.2" or "Hawktail 1.2" These are the only two I would recommend. If there isn't, just google them, it'll lead you to XDA, download them and follow instructions that should be in the post that you downloaded them from. They'll be downloaded as txt files, don't forget to delete the .txt extension.
Ok, so now comes the main part.
Touchboost is a stock kernel feature. What this does is that every time you touch yourself your phone, the CPU throttles way up to max and stays like that for some time. It's very unnecessary and it uses a LOT of power. This is turned off, and instead we have the other two options under CPU>CPU Boost options that compensate for that but use significantly less power and give the optimal level of smoothness.
Optional things you can do in EX Kernel Manager:
Will this break OTA's?
Yeah. But it's no biggie, because whenever there is a security update or version update, someone will usually post a link to the OTA in this sub. Download it (on your phone for maximum efficiency/laziness) then go to the play store and search for "Flashfire". Install it, open it, grant it permissions.
Installing OTA's
You will have to reinstall your kernel, which takes like 30 seconds.
You can also flash 7.1.1 this way, BUT you will need the kernel (if you want the EX kernel) specifically updated for 7.1.1 which just came out today (11/8/2016).
What if you wanna go back to stock? Don't worry, I gotchu.
Back to Stock:
Ok, I guess this wasn't all that short either. My bad.
CF.lumen
For those that opt to move to 7.1.1 (I would personally say go for it, it's fucking INSANE how smooth it is) and miss "Night Mode" well, now you have root which means you can use CF.Lumen (Play Store) and it is literally the same thing, but more customisable and can also be automated (I'm lazy). It's straightforward, download, grant SuperSU access (pop-up) and everything else is straightforward.
Adaway: Another plus of being rooted. Google "Adaway" and there'll be a link leading you to XDA, should be in the top 3-5 links on Google. Download the one that says "Adaway 3.2 Preview." Install it, open it, go to menu>enable systemless mode>enable. Go back to the main app screen and hit the download button. Reboot. Boom, done.
P.S: If anyone sees any mistakes, let me know. If you want me to add something, let me know and I'll see if it's something I know about that I can share.
A few notes:
Edit: If you want to try a different governor profile, I was told about Darkspice 7.5 (should be already on your app) and I've been using it and it's actually really really good. Super smooth, doze is excellent and active battery drain is noticeably lower and SoT is consistently higher. Don't forget to "apply on boot" on all the places I mentioned earlier. Thanks to u/happybanana92 for the suggestion.
submitted by MisterKrayzie to Nexus6P [link] [comments]

How to unlock/root your Nexus 4 with ADB. A tutorial aimed at those who know next to nothing.

edit: September 25, 2013: this guide is outdated, but 95% applicable, you just need to download updated files from the same sites I linked below. PM me for support! I respond very quickly and I will help you out with anything you need!
ASSUMPTIONS
  • You are using, or have access to, a computer with Windows
WARNINGS
  • BACK UP ANY IMPORTANT CONTENTS ON YOUR PHONE, AND MOVE THEM TO YOUR COMPUTER OR OTHER STORAGE DEVICE. UNLOCKING THE BOOTLOADER WILL WIPE ALL YOUR PHONE'S CONTENTS. Note that the data is recoverable, but the process isn't that pretty.
If you want to backup anything, here are some options for you:
1 2 3
  • Installing a custom recovery or custom ROM will prevent you from receiving OTA (over the air) updates. There is an alternative for those who ONLY wish to root but do not wish to load custom ROMs and still want to receive OTA updates. If you wish to receive OTA updates, make sure you follow the proper set of instructions during Part 5.
  • THIS MAY ALSO VOID YOUR MANUFACTURER WARRANTY (DEPENDING ON YOUR COUNTRY'S LAWS), CONTINUE AT YOUR OWN RISK. Note that this does not void any extra warranty you may purchase, such as from companies like Asurion.
PRELIMINARY STEP 1
1) Plug your device into your computer with the USB cable
  • If the USB drivers are already installed your device will pop up and you're ready for the next step
PRELIMINARY STEP 2
2)Enable USB debugging in Settings Developer Options. (If you do NOT see a "Developer Options" in Settings, then you must go to Settings About Phone, scroll down to the bottom, and tap on the "Build Number" section 7 times. A pop-up should show telling you that you are "now a developer." Yay!)
  • Wait for the appropriate drivers to install and you're ready to move to Part 1
===If your computer does not automatically install the drivers, follow these instructions===
3)
OR
3a)
  • Download the drivers by installing the desktop client for PDANet for Android.
  • Once the program is installed, you should select "LG" for the driver installation section. Note: the program itself is unnecessary and can be uninstalled once you are finished. Only the drivers are needed.
Some people have had trouble getting the USB drivers to install, and if you are one of those people make sure you have tried both methods.
PART 1: Download and install the Android SDK
1) Download the Android SDK (STRAIGHT FROM GOOGLE)
2) Once downloaded, install like you would anything else.
3) Be sure to record the destination folder, or choose where you would like it
  • Example: Mine is in
c:\android\android-sdk
4) Once installed, start SDK Manager (the checkbox will already be selected)
5) Once the SDK opens, check the first three (3) boxes; they are labeled "Tools," "Android SDK Tools," and "Android SDK Platform-tools"
6) Install these packages (they are the only ones necessary for unlocking/locking)
7) Once the packages have finished installing, you are done with the SDK. Close it out
PART 2: Gathering the Required Files
1) Download SuperSu (allows you to use root apps)
2) Download ClockworkMod Touch Recovery
3) Once both of these files are downloaded, place them in the Android SDK Platform-Tools folder
PART 3: Unlocking Your Phone
1) Turn on USB Debugging (Settings - Developer Options - USB Debugging) if it isn't already enabled
2) Connect your phone to the computer via USB
3) Open a command prompt window (click "Start button" and type "cmd" in the search bar)
4) Set the path to the platform-tools folder in the command prompt
  • For example: Mine is
cd c:\android\android-sdk\platform-tools
4a) ALTERNATE (EASIER) METHOD FOR OPENING THE COMMAND PROMPT
  • Open your platform-tools folder (C:\android\android-sdk\platform-tools)
  • Inside the folder, press and hold Shift and Right-click
  • A dialog box will popup, select "Open command window here"
5) Check the ADB connection status by typing
adb devices
into the command prompt and press enter
  • If a serial number is displayed, the connection is successful
6) Type
adb reboot bootloader
into the command prompt and press enter
  • This reboots the phone into "fastboot" mode (Big green Android guy with the green word "Start" at the top
7) Type
fastboot oem unlock
into the command prompt and press enter (If a FAILED message pops up like in the picture, just ignore it. Everything works just fine)
7a) You will then be prompted on your phone on whether or not to unlock the bootloader.
7b) Click yes if you want to continue (Volume Up/Down to highlight and Power to select)
7c) Once you’re back at the screen with the big green “Start,” press the power button to let it reboot.
Please note that it will take a while for your phone to reboot, it's normal.
DO NOT CLOSE THE COMMAND PROMPT
PART 4: Pushing the SuperSU File to Your Phone
1) Turn USB Debugging back on (Settings/Developer Options/USB Debugging) after completing the initial set-up
2) In the command prompt, type
adb push UPDATE-SuperSU-v1.10.zip /sdcard/
and press Enter
ALTERNATIVELY:
2a) If you do not wish to use the ADB Push method, you can simply drag the UPDATE-SuperSU-v1.10.zip into the root of your /sdcard folder like you would anything else.
PART 5: Loading A Custom Recovery
--------IF YOU WISH TO RECEIVE OTA UPDATES, DO STEP 2A INSTEAD OF STEP 2--------
1) In the command prompt, type
adb reboot bootloader
2) Once the phone has booted to the bootloader screen, type
fastboot flash recovery recovery-clockwork-touch-6.0.2.3-mako.img
2a) FOR THOSE WHO STILL WANT OTA UPDATES
Once the phone has booted to the bootloader screen, type
fastboot boot recovery-clockwork-touch-6.0.2.3-mako.img
Your phone will now boot into recovery, so you can go to step 4.
3) Press the volume down button on your phone until the "Recovery" option is selected. Press the power button to reboot into recovery mode.
4) If you were successful, your phone should have booted into Clockworkmod Touch Recovery (it will say so at the top!)
PART 6: Flashing the SuperSU file
1) Tap "install zip from sdcard"
2) Tap "choose zip from sdcard"
3) Tap "UPDATE-SuperSU-v1.10.zip"
4) Tap "Yes - Install UPDATE-SuperSU-v1.10.zip"
5) Once it finishes installing, tap "+++++Go Back+++++"
6) Tap "reboot system now"
7) Your phone will reboot
8) Once your phone is back on, open the app drawer and select SuperSU
9) Once the app opens, a dialog box may pop up saying "The SU binary needs to be updated. Continue?". If it does not then you are good to go!
9a) Press continue and it will say Installation Success once it's finished
YOU ARE NOW ROOTED, AND IF YOU WISH YOU CAN INSTALL A CUSTOM ROM
---OPTIONAL---PART 7: Flashing a custom ROM, kernel, mod, etc.
1) Download the custom ROM, kernel, mod, etc. of your choice. This XDA thread contains a nice index of things you can try out.
2) Copy the file you want to flash to your Nexus 4's storage (a simple drag-and-drop from the computer is sufficient).
3) Reboot into recovery. You have several options to do this.
3a) Download any root-enabled reboot app. This is one such example.
3b) With your phone plugged in, type
adb reboot recovery
3c) Power off your phone holding the power button. Then, power on your phone by holding the power button AND holding the volume down button. Your phone should boot into the bootloader. Next, you can boot into the recovery mode by pressing volume down and selecting "Recovery."
4) Once in the recovery, do the following sequence of steps (you will notice how repetitive it gets!):
-----IF FLASHING A NEW ROM, PLEASE DO A FACTORY RESET THEN DO THESE STEPS-----
4a) Tap "install zip from sdcard"
4b) Tap "choose zip from sdcard"
4c) FIND THE ZIP FILE YOU WANT TO FLASH AND TAP ON IT, ex. XXXXXXXX.zip
4d) Tap "Yes - Install XXXXXXXX.zip"
4e) Once it finishes installing, tap "+++++Go Back+++++"
4f) Repeat steps 4a-4e to install the Google Apps zip, or a custom kernel or other mod if you wish.
4g) Tap "reboot system now"
submitted by IAmAN00bie to nexus4 [link] [comments]

[Working][How To] Lollipop Root

This is not my exploit to take credit for in anyways; and as always do this at your OWN risk. Credits to the creator(s) (I don't know who it is), the finder jgkim, and the translator Unjustified Dev.
Original post here.
A translated post here.
The original posts do not talk about the G3, but it DOES work for the G3. See post #636 and on where it has worked for others besides myself (on this XDA thread.) Tested myself on the VS985 (Verizon G3) and it has worked flawlessly. Others have tested on AT&T G3 (D850) and it has apparently worked fine as well!
I noticed quite a few people upgrading who didn't know much about this, and also quite a few people NOT upgrading because of the lack of root access, well this easy to follow tutorial should help with that. I think the instructions on the XDA post are quite clear and easy to follow, but I decided to post one here out of boredom. Originally I was going to just share the link, but why not? Enjoy.
How to:
  • Install SuperSU from the Google Play store and install it.
  • Download these files and extract the contents. I redownloaded all files and packed them together right after to ensure this file is safe. The files are the original rooting-require files along with MFastBoot (Basically adb without the Android SDK installed, it's quick and easier for me since I have not installed the Android SDK). It also includes the latest SuperSU Binary zip straight from the Chainfire website.
  • Enable USB debugging on your device. (About Phone > Build Number (keep tapping it until it says you are a developer) and then go back to the main settings. Go into developer options and enable USB debugging.)
  • With your phone screen on: Connect it to your computer via USB cable and put it into PTP mode. (USB debugging should report as on in the status bar.)
  • With your phone screen on: Hold shift and right click in the folder you extracted and open a command window. (Your phone will soon ask you to allow the computer, hit remember and yes! It may have even asked your prior to this step, just allow it.)
  • Copy this:
    adb push g2_root.sh /data/local/tmp/
  • Right click in the command window and paste. Hit enter, and wait until it finishes (should take a second.) Now copy this:
    adb push busybox /data/local/tmp/
  • Paste it in the command window and hit enter. Copy this:
    adb push UPDATE-SuperSU-v2.46.zip /data/local/tmp/
  • Paste it in the command window and hit enter.
  • Leave the command window open and disconnect your device. Turn off the device completely. Hold volume up and connect the USB cable to your device without touching the power button; it will go into download mode.
  • Find which com port your device is connected to (Device Manager > Ports > Your phone will be there, COM(Number) is what you'll need.
  • Go back your command prompt, and copy this:
    Send_Command.exe \.\COM(CHANGEME)
  • Replace "(CHANGEME)" with the COM port number of your device. Now copy this:
    sh /data/local/tmp/g2_root.sh dummy 1 /data/local/tmp/UPDATE-SuperSU-v2.46.zip /data/local/tmp/busybox
  • Paste it into command prompt and hit enter.
  • Enjoy your root access! I don't think you can just do "adb reboot", so just disconnect your device and do a battery pull. Put the battery back in and boot up your device. Enjoy root!
submitted by ariac_konrel to LGG3 [link] [comments]

v3 beta-R4 for Android 5.1.0 flo + deb

The new kernel release has been in test-mode for 14 days (April 27 - May 11). 14 users participated in testing. During this time, this thread was set to non-public mode. All comments, that have been exchanged, are attached below. To make most sense of this info, you want to read the comments bottom-up (chronological order). Start with "Initial release April 27 2015".
May 11, 2015 - Today I handed out install images to another 16 users and made this thread accessible to all users. Now 30 people in total are using this kernel on Android 5.1.0.
May 12, 2015 - Handed out 12 copies on request and 20 copies to old users and previous testers. 62 copies now delivered in total.
To request your kernel install images for 5.1.0, please send an email with subject "request v3 beta-R4". You will find the two install images within 24 hrs (or so) in your personal folder. Please report you findings below. Thank you.
Safety exception: in the first week (until May 18), I will NOT deliver the new kernel to very new users (who have joined April 10 or after). (removed May 13.)
May 14, 2015 - Uploaded installers for all "deb" users.
May 18, 2015 - Uploaded installers for all "flo" users.
May 22, 2015 - 180+ users have downloaded R4 build 61 since April 27 .
Installation procedure is same as it ever was: after installing the target 5.1.0 Android release via factory image ("LMY47O"), you install a custom recovery (TWRP) via fastboot/bootloader. For this, your bootloader needs to be unlocked. You will then be able to install three files via recovery:
This is all you need to do.
Before you start upgrading, you should make a full backup of your current system in recovery. I strongly suggest you create your backup onto an external USB flash drive. TWRP can do this and it can also quickly and reliably restore from such a backup image. Please make use of this.
The new features are listed below (under "build 57").
Releases:
v3 beta-R4 build 61:
v3 beta-R4 build 58:
v3 beta-R4 build 57:
Android 5.1.0 improvements over 5.0.x:
Easycap drivers - old and new:
You need to edit your userinit.sh file (once), to tell the system which Easycap drivers to load. This way you can switch between the old and the new drivers.
To create userinit.sh for the old (legacy), single-file easycap driver:
su echo "insmod /system/vendoeasycap.ko" > /data/local/userinit.sh chmod 777 /data/local/userinit.sh
To create userinit.sh for the new easycap stk1160 driver:
su echo "insmod /system/vendostk1160.ko" > /data/local/userinit.sh chmod 777 /data/local/userinit.sh
The new EasyCap drivers support faster device initialization (cold start). However, the new EasyCap stk1160 driver does NOT seem to work with all stk1160-based devices.
The Sabrent Easycap and USBTV Easycap devices do NOT appear to be working well with the new drivers made available via this kernel release. You should consider getting a STK1160 based frame grabber device to use with this release. See my USBTV related remarks.
The new EasyCap drivers are using a different video pixel encoding compared to the old/legacy driver. As a result, when using the new drivers, you need to change the default video encoding in VCam from YUYV to UYVY (once).
On first run, VCam will start up in PAL mode. If you are using a NTSC camera, you will need to switch VCam from PAL to NTSC (once).
Read: Automatic rear camera: 3 options
On-power CPU Governor:
This setting allows you to select different power saving modes (aka CPU underclocking).
The ability to switch CPU modes is a standard Linux kernel feature.
Here you can find more detailed CPU Governor info.
If you don't care for underclocking, just leave the default "interactive" setting selected. Most people may not need to change this ever.
I make this functionality available, because what looks like a reliable fixed power line to the tablet, may not be so very constant and reliable, if you are using your tablet in the car (or something similar). The assumption (of stock Android), that you want to run interactive mode, only because there is external power available, may be wrong.
I am myself using "ondemand" mode for now and I really don't feel much of difference. However, I assume the CPU's to run a little cooler overall. And I expect the 3D-navigation app, that I run for hours, to eat up less power overall, etc.
The "powersave" setting will not be of much interest to most people. It may be useful on some very hot days, I don't know. This is something some people may want to try. But probably not.
The Nexus 7 kernel does not support "conservative" mode. This may be a Snapdragon thing, I'm not sure. I know that other Android chipset's do support "conservative" mode also.
"Performance" is also not supported - at all. This setting only makes sense on servers. But I'm not even sure about this.
It's called "On power CPU Governor", because this setting only affects the CPU mode, when external power is attached. The battery driven mode is not influenced by this setting. On battery power, the tablet will behave 100% stock.
Btw, my desktop PC is practically always running in "ondemand" mode.
Previous v3 features
Users who are upgrading from v2.0/4.4.4 straight to v3/5.1.0 should at least take a brief look at the top messages of previous v3 releases: v3 beta-R1, v3 beta-R2 and v3 beta-R3.
submitted by timur-m to timurskernel [link] [comments]

[Guide] Small, simple guide on how to root/flash custom kernel/use EX Kernel Manager/governor profiles

So, I'm bored and I usually get a lot of questions, thus I figured I'll do one of these.
To start off, this is mainly for Nougat 7.0, but I'm sure the same steps would apply for MM. Not 100% sure on 7.1.1 as I haven't messed around on there much. (Edit: Tested and works with 7.1.1)
First things first, your bootloader must be unlocked. Sorry Android Pay users. Personally, I think an unlocked bootloader is nice to have because it makes recovering your device from a soft brick or whatever else that much easier.
Note:
Rooting:
Now what the fuck do I do?
Well, you can now do shit like installing a custom kernel everyone seems to keep bringing up alllllllllllll the fucking time.
Installing Elemental X Kernel:
Before we begin, I should add that without the EX Kernel Manager app, a custom kernel will NOT be useful and you will NOT see improvement in battery life. The app is 4 bucks, it's on the Play Store. It's kinda pricey, I think anyways, but I do think it's worth it for the stuff it does. Now, there are other kernel manager apps, some are free, and they can absolutely be used for Elemental X, BUT I can't help you with that because I've never used them, and these profiles and settings are made specifically for EX. (I'm continuing the guide under the assumption you have the app)
Now what?
Now it's time for some funsies.
Open your EX Kernel Manager app, it may ask for permissions, grant it. Slide the menu from the left, go to CPU>Governor options>Load and see if you have "Glassfish 1.2" or "Hawktail 1.2" These are the only two I would recommend. If there isn't, just google them, it'll lead you to XDA, download them and follow instructions that should be in the post that you downloaded them from. They'll be downloaded as txt files, don't forget to delete the .txt extension.
Ok, so now comes the main part.
Touchboost is a stock kernel feature. What this does is that every time you touch yourself your phone, the CPU throttles way up to max and stays like that for some time. It's very unnecessary and it uses a LOT of power. This is turned off, and instead we have the other two options under CPU>CPU Boost options that compensate for that but use significantly less power and give the optimal level of smoothness.
As for Glassfish V Hawktail...well, it's entirely up to the user. Up until recently, I was a huge glassfish user, but the battery isn't as great as I get on hawktail. Hawktail was worse performance wise, but on paper it should've been better. So, I fixed that by the small alteration I made earlier going from 32ms to 300ms.
Optional things you can do in EX Kernel Manager:
Will this break OTA's?
Yeah. But it's no biggie, because whenever there is a security update or version update, someone will usually post a link to the OTA in this sub. Download it (on your phone for maximum efficiency/laziness) then go to the play store and search for "Flashfire". Install it, open it, grant it permissions.
Installing OTA's
You will have to reinstall your kernel, which takes like 30 seconds.
You can also flash 7.1.1 this way, BUT you will need the kernel (if you want the EX kernel) specifically updated for 7.1.1 which just came out today (11/8/2016).
What if you wanna go back to stock? Don't worry, I gotchu.
Back to Stock:
Ok, I guess this wasn't all that short either. My bad.
CF.lumen
For those that opt to move to 7.1.1 (I would personally say go for it, it's fucking INSANE how smooth it is) and miss "Night Mode" well, now you have root which means you can use CF.Lumen (Play Store) and it is literally the same thing, but more customisable and can also be automated (I'm lazy). It's straightforward, download, grant SuperSU access (pop-up) and everything else is straightforward.
Adaway: Another plus of being rooted. Google "Adaway" and there'll be a link leading you to XDA, should be in the top 3-5 links on Google. Download the one that says "Adaway 3.2 Preview." Install it, open it, go to menu>enable systemless mode>enable. Go back to the main app screen and hit the download button. Reboot. Boom, done.
P.S: If anyone sees any mistakes, let me know. If you want me to add something, let me know and I'll see if it's something I know about that I can share.
Edit: If you want to try a different governor profile, I was told about Darkspice 7.5 (should be already on your app, it's labeled as "Darkspice5x7.5") and I've been using it and it's actually really really good. Super smooth, doze is excellent and active battery drain is noticeably lower and SoT is consistently higher. Don't forget to "apply on boot" on all the places I mentioned earlier. Thanks to u/happybanana92 for the suggestion.
Edit2: Here's a link to the 7.1.1 OTA which you can flash via flashfire
submitted by MisterKrayzie to nexus5x [link] [comments]

Upgrade to 5.0.1 with Root! (VZWi545)

Alright, so this is huge, and I am very thankful I didn't upgrade using the ota. If you have already upgraded with ota, to the complete lollipop update (2nd part), then this does not apply to you as you now have an updated locked bootloader, and there is no way to downgrade back to nc5/nk1/etc as of right now. If you have ota'd, but only the first part of the update, you can still take advantage of this.
First of all, you will have to do a fresh factory wipe, losing everything not backed up. You will have to use odin, and the new app called flashfire, and I will provide the links below.
First of all, you'll have to flash to nc5, this is the link to the nc5 full-wipe tar and Here is the link for the odin download. You will load that into the AP slot, put your phone into download mode by turning it on holding volume down + Home button + Power button, then pressing up to continue. Load up the nc5.tar into the AP slot and flash it. Once it is done, boot it up and load everything up, as you wont have to do another factory reset (unless you mess something up).
Once you're all setup on your new stock nc5, go ahead and download Towelroot. You'll have to allow third party app installation. Just load it up and press Make It Rain!, no need to reboot. Now head to the playstore and install the supersu app, run it and update the su binary, and if given the chance, disable knox. You will have to restart after this, then we'll move onto getting flashfire installed.
To install flashfire, you will have to join the Google+ group. Once you have joined, you can go to this link, there you will click Become a Tester, which will give you a link to install flashfire. Go ahead and install it, but just push done and close the installer, we'll go back to it later.
Now, you'll want to go and download this lollipop rom, written by muniz_ti over at XDA. It is the stock rom, that allows you to keep the nk4 bootloader and root. By keeping the nk4 bootloader, youll be able to flash back to an older version (nc5/nk1). You will also want to download this tether addon .zip, just in case WiFi isn't working once you're on lollipop, although it seems it is fixed (working great for me). Once you have both files, move them to your external SD card, this is optional, but also the safer option.
Now you're all set to get on rooted lollipop, but follow the steps closely or you will have to reflash to stock nc5 and start over.
  1. Open up flashfire.
  2. Agree to terms and services.
  3. Press the + icon.
  4. Choose "Flash zip or ota".
  5. Navigate to the rom you downloaded and select it, leave automount UNCHECKED.
  6. Select the + icon again and select Wipe.
  7. Under the Wipe options, select everything except "internal storage".
  8. Leave all other options as default.
  9. Move the Wipe action to just above the flash action by holding and dragging it.
  10. Press the lightning bolt icon. This will start the process. Just set it down and let it do its thing, or watch all the fancy text scrolling by.
After it is done, you should be booted into your brand new rooted lollipop phone. Set everything up and enjoy this bad boy, it's as fast as lightning for me!
If, for whatever reason, your WiFi doesn't work, just redownload flashfire and flash only the tetheraddon.zip. Then you should be good to go.
Good luck and enjoy!
submitted by IINSULT to galaxys4 [link] [comments]

[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?
Preparation
Before you get started, make sure you have the following files:
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.
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.
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!
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.
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):
fastboot flash recovery openrecovery-twrp-2.7.1.1-ghost.img
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.
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!
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.
submitted by chrismith85 to MotoX [link] [comments]

What does wiping 'system' in TWRP do ?

well .. i have a problem of sorts .
I am using Galaxy Mega I9152 , CM13 (downloaded from here ; https://forum.xda-developers.com/galaxy-mega/orig-development/rom-cyanogenmod-13-t3297678)
now problem is , it was running smooth as ever until a few hours ago :'( . my phone all of a sudden got stuck in bootloop and my attempts to recharge it did not work. the Os stayed on for a few seconds before giving up and restarting. this continued for sometime before i tried to google online
this is what i did
booted into the TWRP recovery and went for the 'fix permissions' option. and at the end of the procedure TWRP asked me if i wanted to root my phone (i had disabled root early on , through SuperSU , through the application's settings) . BY MISTAKE , i swiped and rooted my phone
then instead of going into bootloop , the phone just stuck on the booting animation
i tried to clear dalvik cache and cache but to no avail.
my SD card was encrypted (formatted as internal) so i tried to access it through adb and other methods , but in vain :'(
next i tried to use another SD card i had , and after inserting it into the phone , i was able to transfer the SAME custom ROM i had used before , into it , through adb . i tired to reflash that rom on TOP of my CURRENT ROM , but to no avail.
i got error message "error executing binary" while trying to install the rom and also a statement saying " cannot install on top of incompatible data"
now i am very confused and i just want to save my pics and data from my phone and my ENCRYPTED sd card which i can't seem to be able to use in any other device (even TWRP doesn't recognise the SD card , because it's formatted as internal :/)
please help me out , i just want to save my pics and stuff.
my FINAL question is , that if i remove the 'system' through TWRP and install the EXACT same ROM again , will the SD card , that was encrypted during the PREVIOUS 'life' of the ROM in my mobile , work on the 'new' iteration of the SAME Rom in my mobile. please help me out.
EDIT : i dont want to lose my data , even if i have to lose my OS , so be it but PLEASE help me retain my pics ! My pics are in the SD card which i have TAKEN OUT of the phone , as it is UNREADABLE and i cannot reflash the device using it. so i'm using another SD card
EDIT 2 : i have tried looking up how to DECRYPT the Adoptive Storage (internally formatted SD cards) and have come across this ; http://android.stackexchange.com/questions/135803/corrupt-sd-card-formatted-as-internal-storage
also here's what i get , after i fit the SD card into card reader and run the # fdisk -l command ;
OUTPUT http://pasteboard.co/POGvyBOxO.png
MASSIVE UPDATE : i was able to retrieve the key by going into the /data/misc/vold folder ... I CAN SEE THE .KEY FILE.BUT only after i browsed the folder when the SD card was loaded INTO the laptop's card reader while the phone was booted into TWRP. i DID NOT retrieve the .key file through Linux terminal.
NOW WHAT DO I DO ! i am very confused , since i don't know what to make of the Linux Output of reading my SD CARD.
please help !
also , there's this trick ;
https://forum.xda-developers.com/moto-e/general/trick-switching-roms-loosing-adopted-sd-t3314647
submitted by yaxir to AndroidQuestions [link] [comments]

Standby Battery Drain Bug - Fixed!

Please note, I have yet to complete running all my tests so the actual numbers may change, pls dont kill me if i get ur hopes up too much

Setup:

Unlocked bootloader
TWRP 2.8.7.0
SlimLP Nightly 16-8-15
Gapps (This isn't part of stopping battery drain but you should install it anyway because... you know, google play?)
Xposed for Android 5.1 (It is imperative you download the x86 version from here and not another version of Xposed)

Apps

Xposed Installer (Contrary to the name, this is not an installer, but lets you activate Xposed modules)
SuperSU (Not required, but very highly recommended)
BetterBatteryStats (Very useful for seeing what's keeping your device awake/waking it up)
Greenify (Donator Package recommended, but not required)
Amplify (Donation Package required for what we're using it for)

Battery Fix

For the last few weeks I've been looking intently at what's using up my standby battery and I noticed that there were a huge amount of wakeups from components of the system as well as the Phone and Google Play Services. I'll be using Amplify to stop the system from being able to use up my battery, as well as Greenify to stop my messaging apps from doing this.
First, setup your apps. If you are using SuperSU, open the app and select to update the binary, with a normal install. Go into BetterBatteryStats and select to install as a system app (optional). Then go into Greenify, experimental features, set the working mode to 'Boost' (this will require you to activate the Xposed module and reboot). If you have the donator package activate it first by clicking the icon in the launcher. Open Amplify and set it up so that it can see stats about your device. Reboot.
The first thing to do after you install the apps is spend a day using your phone with everything turned on. Leave Location services, bluetooth, NFC and wifi on so Amplify can pick up on their wakelocks and wakeups. Once this is done disable Google Now if you have it turned on (sorry but takes too much battery), set location services to battery saving and turn off NFC (at least for now). I recommend checking BetterBatteryStats (especially the alarms section as this is the biggest culprit on the Zenfone 2)
Go into greenify and click the plus icon to select apps to greenify. I would recommend selecting your internet messaging apps (not SMS) such as Instagram, Facebook and kik (which by the way wakes up your device twice a minute!!!). You do not need to greenify WhatsApp, I have built management of WhatsApp into my Amplify profile Go into greenify, experimental features, and enable these options: Wakeup Timer Coalescing, Telephony Wakeup and Don't remove notifications. If you have the donator package, you may want to enable GCM push which will give more reliable notifications but I'm not sure how much this decreases battery life.
Now the real fun begins. Open up Amplify (Note, you need to buy the donator package) and start by going to the wakelocks section.
In here you want to manage the following (the name of the wakelock is followed by the number of seconds set):
NfcService:mRoutingWakeLock 4800 // Ignore this if you want to keep NFC on Icing 900 SyncLoopWakeLock 480 GCoreFlp 480 NetworkStats 240 Wakeful StateMachine: GeofencerStateMachine 240 // Or higher if you want NlpWakeLock 480 *alarm* 240 // 480 for much bettter battery life NlpCollectorWakeLock 600
Next you want to go to the Alarms section and repeat it again with the following:
com.android.internal.telephony.data-stall 480 com.whatsapp.messaging.MessageService.LOGOUT_ACTION 240 com.android.chrome/com.google.ipc.invalidation.external.client.contrib.AndroidListener$AlarmReceiver 480 com.android.chrome/com.google.ipc.invalidation.ticl.android2.AndroidInternalScheduler$AlarmReceiver 480 com.android.deskclock.ON_QUATER_HOUR 600 // As the name suggests, this should be called every 15 minutes. Except it's called every few minutes lolwut AlARM_WAKEUP_LOCATOR 480 com.google.android.intent.action.SEND_IDLE 480 com.whatsapp.alarm.CLIENT_PING_TIMEOUT 480 com.whatsapp.messaging.MessageService.CLIENT_PINGER_TIMEOUT 480 com.android.providers.calendar.intent.CalendarProvider2 240 com.facebook.rti.mqtt.c.b.ACTION_INEXACT_ALARM.11961 840 // This is actually from instagram, not facebook com.whatsapp.alarm.AVAILABLE_TIMEOUT 480 com.facebook.rti.mqtt.c.b.ACTION_INEXACT_ALARM.8844 480 ALARM_WAKEUP_ACTIVITY_DETECTION 480 ALARM_WAKEUP2275837 480 // 2275837 is unique, you should have one similar but with different numbers com.facebook.rti.mqtt.common.c.s.ACTION_ALARM.11961 480 com.facebook.tri.mqtt.c.b.ACTION_INEXACT_ALARM.3390 480 com.google.android.intent.action.MCS_HEARTBEAT 480
Lastly take a look at the Services section. In here I have disabled com.android.chrome/com.google.ipc.invalidation.ticl.android2.TiclService. You may also want to disable com.google.android.gms/.icing.service.IndexWorkerService but I have no idea what it actually is so I'm reluctant to. Reboot after this.
If you see anything else in these three sections that is using up a lot of battery, feel free to manage it as well.
You may also want to take a look at BetterBatteryStats afterwards. After leaving it on standby for a few hours, have a look at the Alarms section to see how much it's improved :)

Downsides

Notifications from apps that use push will be delayed. NFC will most likely be basically broken, but you can alleviate this by removing the Amplify setting for NfcService:mRoutingWakeLock and enabling NFC. Google Now and other 'always on' monitors won't work/will negate the effects of this fix, as they keep your device awake.

RESULTS

I'm gonna preface this with saying that my battery was on the shitty end of the spectrum before this fix. I used to get just 2.5 hours of SOT on stock and 3.5 hours of SOT on cyanogenmod/slimLP. On top of this, I only got around 15 hours of standby time on stock (lol) and 48 hours on CM12 with greenify. I'd also like to say that my slimLP has a bug which means that I don't get any battery stats inside settings, meaning that I can't verify whether this actually gets rid of the "Android OS" drain
With these adjustments my standby went from just 15 hours to 150 hours with WiFi, bluetooth (connected to my watch) and location services turned on which is easily enough for me. I got this number from a test I ran overnight for 6.5 hours, where I lost 4% battery. However, because 4% is so small, this number could be anywhere from 100 to 250 hours. I plan to run more "soon"
My SOT was unchanged however at 3.5 hours.

Tell me what you guys think :)

submitted by mikbob to zenfone2 [link] [comments]

Might have soft bricked my S3, could use some advice

Hi there, mega noob here :)
I tried to install this ROM on my Galaxy S3 Mini (GT-I8190) and I think I might have soft bricked my phone in the process. Not sure though. TTis is a wall of text describing my process as detailed as possible. Hopefully someone has the patience to help me out here because I'm totally lost and not sure what I should do from this point on.
Here is what I did: after reading through a lot of guides that where somewhat confusing, I decided to go for Odin since it sounded like I wouldn't have to root my phone doing it this way.
I downloaded the odin version (a .zip containing just a los14.1_golden.nova.20170610.ODIN_TWRP.tar.md5 file) from here and followed this guide. Everything seemed to work out fine until step 11. My S3 kept rebooting, ending up in this screen. Maybe I was too impatient and should have waited longer but after 15 minutes I decided to remove the battery and go into recovery, just like the tutorial suggested.
This is what my screen looked like, so I figured that I probably didn't really flash the ROM succesfully, despite Odin giving me a good to go all the time. I basically tried all kinds of things, like disconnecting the USB cable after Odin file transfer was done, disabling auto reboot, hitting the recovery button combination like crazy - but all the same. Either stuck with that loading screen or the stock android recovery (I assume it was that, since I didn't have the swipe option the guide was talking about).
So I then decided to use Odin to get TWRP on my S3. The guide did not mention this, nor was it mentioned in the release thread so maybe this was my first mistake to not have it on the phone in the first place. Went into download mode, loaded TWRP-2.6.3.0-golden.tar from here using this Odin install method.
Now I was able to enter TWRP recovery and had all the buttons. Wiped everything, rebooted, nothing. So for whatever reason it seemed that the ROM wasn't on my S3 yet after all, so I used the first guide from novafusion again, loading it up with Odin one more time. Same result: stuck in this loading screen with the circle moving from right to left. So I went into recovery again just like the guide suggested but when rebooting it tells me there is no OS installed at all.
Several youtube videos later it seemed everything looked a lot more easier and also different compared to my process. Since I'm not able to detect my phone via PC (Odin will detect it, but I can't access either internal nor external SD card), I removed my SD card, connected it directly to my PC and copied all kinds of .zip files I thought that might be handy.
1) the .zip with the los14.1_golden.nova.20170610.ODIN_TWRP.tar.md5 file
2) the other los14.1_golden.nova.20170610.zip from the same page found under recovery
3) a lineage-14.1-20170609-UNOFFICIAL-golden.zip downloaded from here (because this is what others used in their videos)
4) open_gapps-arm-7.1-nano-20170615.zip because I figured I might just install this as well afterwards
Put the SD card back in my phone, started TWRP recovery, mounted the SD card and then tried to install any of those .zip files. The flashing process always starts, but after some time an error message appears, telling me that the flashin has failed. I then have the option to wipe, reboot or go home and retry. For some reason my screen cuts off some parts of the log so I don't really know what it is saying, but this is what I basically get:
Updating partition details... Installing (external SD directory and name of the .zip) Checking for MD5 file Skipping MD5 check: No file_contexts Target: samsung/cm_golden/gilden: (some file name) detected filesystem ext4 for dev/block/mmcblk0p (rest ist cut off) detected filesystem ext4 for dev/block/mmcblk0p (rest ist cut off) ApplyParsedPerms: lsetfilecon of system/lost+fo (rest is cut off) set_metadata_recursive: some changes failed E:Error executing updater binary in zip (external SD directory and name of the .zip) Error flashing zip "(external SD directory and name of the .zip) Updating partition details
This pretty much happens with all .zip files I'm trying to install via TWRP.
Now here comes the interesting part: when rebooting, I don't get the message "No OS installed, still continue?" so it seems something has worked out. I figured I could install the TWRP recovery just for fun and it turns out I can install it, so I end up booting TWRP recovery automatically when starting the phone up as if it were an OS - despite the previous error messages that the install failed.
So with this "knowledge" I basically tried the actual ROMs again (same error output), but then I simply reboot the phone. A new message pops up:
Install SuperSU? YOur device does not appear to be rooted. Install SuperSU now? This will root your device.
I then swiped to install, it works, I reboot system and get stuck here again :(. So for some reason (and as far as I understand) I can install the ROM but something is corrupted, thus it is able to start booting but never really load the OS?
I don't know. This is were I'm stuck now. I can enter recovery, I can enter download mode, I can still use Odin, access my SD card with recovery (or take it out and directly mount to the PC) but I can't get the OS installed and running properly.
Maybe I'm doing this all wrong, maybe I have the wrong files. It also seems some people use a newer version of TWRP, however it looks like my S3 mini doesn't support those? I don't know. At this point, I just want to throw my phone out of the window because it has been almost seven hours without actual progress.
Please, if someone can help me out, that would really make my day.
ʕ༼◕ ౪ ◕✿༽ʔ
edit01: managed to make a log file, if this helps.
edit02: since I did not get anywhere I decided to give it a try and install a rooted 4.1.2 via Odin. This worked perfectly, so at least I'm back to where I started before messing around with LineageOS. I still could use some help to install that ROM because following instructions I end up having the same issues over and over.
submitted by Ord0c to GalaxyS3 [link] [comments]

Updating SuperSU binary and flashing in TWRP never works. (VS985)

TL;DR: I flash SuperSU (the filename is UPDATE-SuperSU-v2.76-20160630161323.zip) in TWRP and get a "error: boot certification verify" error message and flashing red/blue LED. Or I install SuperSU through the Play Store and update the binary through the app. Then, get an endless CM splash screen. I let it sit for 12 hours one time. It never went away.
I've been trying to figure out this problem for a few months off and on. I've got a Verizon LG G3 (VS985) with Android 6.0.1 (CyanogenMod 13.0-20160730-NIGHTLY-vs985) and TWRP 2.8.7.0. Thank God for removable batteries. I'd be lost without it.
It works fine if I do a factory reset and fresh install of CM and GApps. As long as I never update the SuperSU binary. I have decent backups that I can restore. But, I want to get this problem figured out.
Please help!
Here's the long version of what happens.
When I flash SuperSU in TWRP
  1. Boot into TWRP recovery.
  2. Choose Wipe > Advanced Wipe. Select only Dalvik Cache, System, Data, and Cache.
  3. Perform the factory reset. Finished with no errors.
  4. Flash the latest CyanogenMod zip file (the filename is cm-13.0-20160730-NIGHTLY-vs985.zip). Finished with no errors.
  5. Flash the GApps (the filename is open_gapps-arm-6.0-pico-20160726.zip). Finished with no errors.
  6. Flash the latest version of SuperSU (the filename is UPDATE-SuperSU-v2.76-20160630161323.zip) downloaded from here. Finished with no errors.
  7. Reboot.
  8. I immediately get this error message. After a few seconds, the screen turns off and the LED flashes red and blue.
When I update the SuperSU binary through the app.
  1. Boot into TWRP recovery.
  2. Choose Wipe > Advanced Wipe. Select only Dalvik Cache, System, Data, and Cache.
  3. Perform the factory reset. Finished with no errors.
  4. Flash the latest CyanogenMod zip file (the filename is cm-13.0-20160730-NIGHTLY-vs985.zip). Finished with no errors.
  5. Flash the GApps (the filename is open_gapps-arm-6.0-pico-20160726.zip). Finished with not errors.
  6. Reboot.
  7. CyanogenMod loads properly.
  8. I go through the setup process and download all my apps from the Play Store. Including SuperSU and SuperSU Pro apps from the Play Store. All apps install properly. I don’t open any apps or make any modifications within the apps.
  9. Enable Developer Options by going to Settings > About phone > Tap on “Build number” 8 times.
  10. Set “Root access” to “Apps and ADB” in Developer Options.
  11. Open SuperSU for the first time. It says that I need to update the binary.
  12. Tap “OK.”
  13. Select the “CWM/TWRP” method of rebooting.
  14. Grant SuperSU root access when prompted for it.
  15. The phone reboots into TWRP. It automatically installs what appears to be SuperSU binary. There’s no error messages, as far as I can tell.
  16. The phone automatically reboots.
  17. The CyanogenMod splash screen (i.e. the blue CM alien head logo and the expanding gray circle) comes up and never goes away. The animation doesn’t appear to freeze or stutter. I let it sit for 12 hours hoping that it would eventually load Android. The splash screen never went away.
Thank you for your help!
submitted by Dude_with_the_pants to cyanogenmod [link] [comments]

Rooting a fresh install of Marshmallow (howto)

In addition to the factory image, you'll need the following:
Do this:
If you get a 'Your device is corrupt' warning on boot, ignore it and let the phone keep booting.
Usual disclaimers apply. Do this at your own risk, don't poke around in the bootloader if you don't know what you're doing, etc. You should also know how to use adb push, in case you need to get the SuperSU and kernel zip files over to your phone.
edit: updated kernel link
submitted by jumper34017 to nexus6 [link] [comments]

stuck in bootloop , Please help me out :'(

I am using Galaxy Mega I9152 , CM13 (downloaded from here ; https://forum.xda-developers.com/galaxy-mega/orig-development/rom-cyanogenmod-13-t3297678)
now problem is , it was running smooth as ever until a few hours ago :'( . my phone all of a sudden got stuck in bootloop and my attempts to recharge it did not work. the Os stayed on for a few seconds before giving up and restarting. this continued for sometime before i tried to google online
this is what i did
  1. booted into the TWRP recovery and went for the 'fix permissions' option. and at the end of the procedure TWRP asked me if i wanted to root my phone (i had disabled root early on , through SuperSU , through the application's settings) . BY MISTAKE , i swiped and rooted my phone
then instead of going into bootloop , the phone just stuck on the booting animation
  1. i tried to clear dalvik cache and cache but to no avail.
  2. my SD card was encrypted (formatted as internal) so i tried to access it through adb and other methods , but in vain :'(
next i tried to use another SD card i had , and after inserting it into the phone , i was able to transfer the SAME custom ROM i had used before , into it , through adb . i tired to reflash that rom on TOP of my CURRENT ROM , but to no avail.
i got error message "error executing binary" while trying to install the rom
now i am very confused and i just want to save my pics and data from my phone and my ENCRYPTED sd card which i can't seem to be able to use in any other device (even TWRP doesn't recognise the SD card , because it's formatted as internal :/)
please help me out , i just want to save my pics and stuff.
my FINAL question is , that if i remove the 'system' through TWRP and install the EXACT same ROM again , will the SD card , that was encrypted during the PREVIOUS 'life' of the ROM in my mobile , work on the 'new' iteration of the SAME Rom in my mobile. please help me out.
EDIT : i dont want to lose my data , even if i have to lose my OS , so be it but PLEASE help me retain my pics ! My pics are in the SD card which i have TAKEN OUT of the phone , as it is UNREADABLE and i cannot reflash the device using it. so i'm using another SD card
EDIT 2 : i have tried looking up how to DECRYPT the Adoptive Storage (internally formatted SD cards) and have come across this ; http://android.stackexchange.com/questions/135803/corrupt-sd-card-formatted-as-internal-storage
also here's what i get , after i fit the SD card into card reader and run the # fdisk -l command ;
OUTPUT http://pasteboard.co/POGvyBOxO.png
MASSIVE UPDATE : i was able to retrieve the key by going into the /data/misc/vold folder ... I CAN SEE THE .KEY FILE. BUT only after i browsed the folder when the SD card was loaded INTO the laptop's card reader while the phone was booted into TWRP. i DID NOT retrieve the .key file through Linux terminal.
NOW WHAT DO I DO ! i am very confused , since i don't know what to make of the Linux Output of reading my SD CARD.
please help !
also , there's this trick ;
https://forum.xda-developers.com/moto-e/general/trick-switching-roms-loosing-adopted-sd-t3314647
submitted by yaxir to androidroot [link] [comments]

Trying to root a brand new 21A LGG3 (D855)

I can't believe, after 2 years with this phone I have to ask this, but here we go....
My previous D855 broke down like a month ago, but warranty changed the motherboard for a new one, so... now, I'm trying to root it again.
Before, I had TWRP, and cyanogenmod and I'm quite a flashaholic, but the first time you unlock this phone is a pain in the ass.... so.... this is what I did.
1: Rooted with this method: http://forum.xda-developers.com/lg-g3/general/guide-root-method-lg-devices-t3129197
2: Installed supersu from the play store, opened it and updated the su binary: Rebooted
3: Installed flashify and flashed twrp downloaded from here: https://dl.twrp.me/d855/
From flashify, I selected the "Reboot to recovery" Option, but before TWRP even appears, I get an error: "BOOT CERTIFICATION FAILURE, SECURE BOOT ... ETC (COULDN'T READ ALL) and the phone screen remains powered off and blue-red light blinking until I pull the battery......
What am I missing here?
submitted by jonandermb to LGG3 [link] [comments]

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!
submitted by eaking68 to AndroidQuestions [link] [comments]

Elephone P8000 bootloop - any fixes?

My friend recently got an elephone P8000, and asked me to do my magic and remove the ads and bloatware (and awful launcher). Knowing that Elephone usually ships their phones pre-rooted, I downloaded xposed installer, superSU and a root checker.
First sign was when the root checker said it didn't have root. I found it strange, but pushed it aside. Xposed installer (right arch, right OS version) installed, and so did SU. Tried to install/update SU binaries, but it failed. After a reboot, it bootloops.
I can get into recovery, and fastboot. Erasing cache and data and factory resetting didn't fix anything. adb devices doesn't pick the phone up while it's in the recovery either. I'd just oem unlock and flash a custom recovery and get it over with, but apparently there's a toggle to allow that command to work...hidden in the dev options, from the UI which I can't get to. I can't write the recovery with fastboot flash either, it says "FAILED: remote download for partition recovery is not allowed"
Anything else I can try? I really don't want to hand him back an expensive brick. I feel like with most of fastboot access I should be able to do something.
Any help is appreciated in advance!
PS: OH! Also somehow I got into a menu that had asian characters, and it told me it was seeing nearby WiFis (showed my neighbor's WiFi SID), and then it popped up a picture of a cat, promptly rebooting to bootloop a few seconds later.
submitted by octoshrimpy to AndroidQuestions [link] [comments]

How to fix the su binary update in supersu 100% works ... How to Solve Supersu binary occupied 100% work 2020 Free Download Binary Option Bot- Robot// Auto Trading ... How to install Supersu binaries on the HTC One M8 - YouTube SU BINARY OCCUPIED ANDROID ISSUE FIXED IN A MINUTE !!! [UPDATED]2015 How to Update Su Binary for SuperSu How to update su binary

Head over to SuperSU’s official website and download the latest SuperSU zip file on your device. 2. ... But it said Su binary occupied. So i download previous version of su file from this site and it asked for update the binary file. So i thought problem was solved. But Su binary not updated it just lording take too much time. Not happened anything. So i was restarted the phone and it still ... Download SuperSU ZIP & SuperSU Apk for Android. Super SU is one of the oldest and stable root solution for Android Devices. Rooting your Android phone with SuperSU gives you more abilities and access over your device. Through this page, you can download SuperSU and also get to learn about the rooting process. What is SuperSU How To Root. Main Content SuperSU ZIP and SuperSU APK v2.82 for ... Did you download SuperSU and tried many rooting methods and none worked out or tried many rooting your phone with the SuperSU zip file and it didn’t work? Today, I am going to fix it for you. Getting started, you should know what rooting is and what good and bad it might bring to you. You must have known what is SuperSU, what is SuperSU ZIP File, SuperSU Binary, SuperSU App, and lastly ... SuperSU download is a well-known root-only application that acts in the fashion of guard to your rooted Android device. That comes in a special frame of security in order to manage app permissions. And there is also the advantage of management on which app should take into the system and which apps are not. So if there is any malicious threat about taking various apps after root, SuperSU Root ... Latest- Official SuperSU Zip Flashable Zip file (v.2.82) and APK are now added (2020 -Latest Version). We have shared direct links as well as a detailed rooting guide using supersu and TWRP (or any custom recovery). The Super Su v2.82 is the newest official build of Chainfire’s SuperSu.Below we are going to share the direct download links of Latest SuperSU v2.82. Supersu Binary Zip Download Best Rooting Super Binary APK. Root Tools / By Natwar Roy. To use mobile phone with crazy speed, people are going to root it. Supersu Binary zip is such a software that can root mobile phone internally. It does not need the support of a computer or another device. Moreover, the same file can root in average all the device. But the computer needs framework and ... Supersu download binary option Get link; Facebook; Twitter; Pinterest; Email; Other Apps; October 12, 2019 Supersu download binary option November 30, 2017 Follow the below steps to fix “Unfortunately SuperSU has Stopped” Error: 1. Download the latest flashable SuperSU update package from the downloads section. 2. Copy the zip to your device and flash it using a custom recovery like CWM/TWRP/PhilZ. 3. In case you don’t have a custom recovery installed on your device, extract the SuperSU zip ... SuperSu App Screenshots Download SuperSu Apk SuperSu Apk runs on Su binary. A temporary unroot option permits you to unroot the device for a while and installed the third party application to view the features. With the help of Pre-app notification, this app will help you to completely unroot your device. Main point of this release is, they released it without modifying system partitions. Next ...

[index] [29418] [12590] [6862] [1429] [28383] [26565] [24724] [24293] [26763] [12889]

How to fix the su binary update in supersu 100% works ...

How To Connect Two Routers On One Home Network Using A Lan Cable Stock Router Netgear/TP-Link - Duration: 33:19. Richard Lloyd Recommended for you How to install Supersu binaries on the HTC One M8 - Duration: 3:08. ILIVE4HEAD 27,246 views. 3:08. How to use Super Su with kingroot - Duration: 7:54. Jonathan Wilbur 32,108 views. 7:54 . How To ... 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 ... su binary occupied samsung, su binary occupied supersu, su binary occupied fix, cara mengatasi su binary occupied, su binary occupied error, su binary occupied fix android, su binary occupied ... Supersu binaries zip.: http://download.chainfire.eu/supersu Busybox zip.: http://d-h.st/U7y based on - Free Download Binary Option Bot- Robot// Auto Trading Signal Software 2019 hindi -----... It is the fastest and the simplest way to get work supersu thank you any questions: [email protected]

#