How To Fix SuperUser Installed No Root Access Issue On Android

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]

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]

Might have soft bricked my S3 Mini, 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 s3mini [link] [comments]

Need help rooting

Recently I managed to flash CM 12.1 on my fire 7 following the instructions here:
http://www.overclockers.com/forums/showthread.php/777613-CyanogenMod-12-1-Android-5-1-1-on-Amazon-Fire-7-Tablet
After which I've been trying to root it, or rather update the SuperSU binaries but it constantly keeps failing. I know I gotta enable root first in the developer options and I have but I always end up with an 'installation failed' error from SuperSU.
I have no idea what else to do, I did sort help from the XDA forum but no one seemed to be able to solve me issue so I was just wondering if anyone over here maybe able to rectify it. I did set root access to 'apps only' as some people suggested but that made no difference, have also done a hundreds (I'm not kidding) of rebooting in between the changes of root access options but nothing helped.
Hopefully someone can help me out..
submitted by blakenator95 to kindlefire [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]

[Re-Root] H918 - Updated kdz to k, can't roll back to i/j to properly install TWRP and boot a ROM

Hi /lgv20!
I got a v20 earlier this year and I was able to use easyrecowvery to exploit, set selinux permission, install twrp, and start installing ROMs.
However at some point I decided to try the latest update since I was on NSS 6.5 and he's not going to be updating it for a while.
So I kdz'd with LGUP and the proper DLL to upgrade to the latest k kdz (i, j, k). (There may be more KDZs I haven't found).
Here's what happens:
And now I am totally lost. My phone's OK since I KDZ'd back to H91810k, but it's stock and full of bloat, and it had problems with my car bluetooth where tracks in GPMusic don't start playing until 3 seconds in and OK Google takes 3 seconds to ploink and prompt, so I can't even voice activate - and I have travel coming up
I seriously miss EmotionOS 'cause of the boss Equalizer it had that worked so very nicely on the phone.
I don't care about my second screen.
Can anyone help? I'm willing to send $25 paypal to someone who can help me make this work out very well. :)
submitted by lgvtwizzy to lgv20 [link] [comments]

Just rooted my Verizon s3, but I have questions about the bootloader, superSU, and ROMs.

OK, so I used towelroot.com to root my Verizon s3 and it worked fine but I have some questions that I want answers to before I proceed with flashing ROMs or anything like that since this is my first time rooting.
  1. When I go into SuperSU it says I need to update the binary file but and it prompts me with a question about custom recovery and if I have TWRP or CWM that can be used to install the SU binary. The two options I get are TWRP/CWM and "normal". I chose normal and it said "installation failed, please reboot and try again" and I did and it did the same thing. should I choose TWRP/CWM or will that do something bad?
  2. When I reboot my phone the first thing that comes up is a screen that says "custom" with an unlocked lock. Does this mean I've unlocked the bootloader or that I'm just rooted?
  3. Am I able to flash CM11 onto this phone (sch-i535)? The posts in /GalaxyS3 say that only touch wiz based ROMs are allowed but I found videos of s3's on 4.3 and 4.3.1 on CM11 like this one?
Thank you for any help you're able to give I'm sorry if this is simple stuff.
submitted by BlueSubaruCrew to AndroidQuestions [link] [comments]

[ROOT] Unable to update SuperSU binary on HTC One E8

Hi all,
I installed the latest Chainfire SuperSU (v 2.46), and flashed it with TWRP. The flashing was successful, but when I opened up SuperSU there was a popup that said "The SU binary needs to be updated. Continue?"
 
This is where the problem comes in. There are 2 options to update the binary - normal and TWRP/CWM. At first I tried TWRP, and to my understanding, the phone is supposed to automatically boot into recovery and install the binary update, but nothing happens. The popup just closes and that's it. SuperSU didn't even close. After rebooting, I tried the "normal" option, and after a while, it says "Installation failed! Please reboot and tried again." No mater how many times I reboot, the problem persists.
 
I've also tried reflashing TWRP, in case the problem was with the recovery. No luck there either. I'm also unable to use the "Full unroot" or any other related uninstallation/reinstallation of SuperSU. After the "Uninstalling..." message, nothing happens, and when i reboot my phone, SuperSU is still there.
I have already tried reflashing the SuperSU zip and rebooted many times, but nothing seems to work. I'm at my wits end. Any help is greatly appreciated.
submitted by whyw8 to AndroidQuestions [link] [comments]

Tried to install SuperSU on CM13 and stuck on bootanimation, any help?

I got frustrated of the # icon and tried to install SuperSU using some advice from XDA, I tried installing the Binaries in the "normal" mode and it failed, so I picked the TWRP option, it installed and rebooted but it's since been stuck on the bootanimation.
What's the quickest and easiest way to get out of this? Clean update to the newest nightly? Delete some files? Do you guys have any experience with this?
submitted by samewaterbottle to MotoG [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]

Do custom ROMs not automatically come rooted?

So I just installed SlimROM onto my S3. None of my root-apps can get superuser access. No superuser prompt shows up, they all get the message "Superuser access is needed but could not be acquired". There is a Superuser thingy in the Advanced Options, so I don't know why it isn't working. I tried installing SuperSU from the Play store, but it failed to "update the superuser binary".
What am I doing wrong?
submitted by moeburn to AndroidQuestions [link] [comments]

help with cyanogen 12.1 - how to root? (SGS2 plus/i9105p)

fair warning: wall of text ahead.
also, I know CM support for my phone is not official... but this is a broader question. :)
okay. so, for a start, I'm not usually much into roms (have been with stock a few years), but since the performance has been getting worse with time, I've decided to try and see if a custom rom fixes that. and since in my noob world, cyanogen is the most known one, I've decided to start with it.
so, I managed to install it (easy), tested it, and some of the features are indeed awesome, a big step up from the stock JB rom. thing is: I pretty much need root. and I can't for all that's holly figure out how to root it. the update (root installer) package (the one that you flash through the custom recovery) won't install the binary (but it does install the supersu app), and the other methods (including some apps, some desktop apps, and such), just won't work (I can't say how/why they fail 'cause they're opaque to the user).
I really love cyanogen 12.1, but alas, I really need a rooted phone. so, questions ahead:
submitted by niky45 to cyanogenmod [link] [comments]

Question about geohot's s5 root from a noobie

So I ran geohot's new s5 root on my s3 running 4.3 and it worked. So now I'm rooted (Sweeet!).
First question is, what does one do to fully unroot the phone?
Being a noob at this whole root thing, I'm told I need a superuser app to help with security, so I downloaded superSU and when prompted to update the binary file it reboots and fails to install. It will reboot in recovery with a few options but I'm not sure what they mean.
So does a SU app just not let any random application write/rewrite stuff to the /systemfile? I'm just trying to get my head around how it all works in the phone for this root method.
I know there a lot of people with some good knowledge of rooting on here so thought I'd ask for some guidance.
PS: I got xposed framework installed and tried for a few aesthetic mods, and upon changing those, it made me install an app called Busy box? What is this for?
Thanks in advance for any help! (on my phone for sorry for shit format)
submitted by Mr_Braaap to AndroidQuestions [link] [comments]

Update SU binaries without dual recovery?

Hey friends. I'm on the infamous z3v and I'm attempting to download dual recovery through nut's XDA tool. I rooted my phone using kingroot, so when I go to use the install dual recovery tool, it wants me to pick between SuperSU and Superuser, but to use either of those options I need to update my SU binaries. For some reason, when I try to update these in app, it fails. All solutions are pointing in the direction of installing an update through recovery...but I can't get a recovery mode without SU binaries...has anyone had any similar issues/know of any leads for a solution?
Thanks!
submitted by mrbriteside616 to SonyXperia [link] [comments]

The basics of binary options and what's in it for you 1 Minute 85% ITM Strategy for Binary Options 2,019 BINARY OPTIONS TRADING TUTORIAL #2 Binary Options 60 Seconds Indicator 99% Winning Live Trading Proof [2019] Fix

I then uninstalled the SuperSU app (from within the SuperSU app, "install other SU manager app" function) and installed this app. Can anyone help? Edit: it seems others have had success by manually updating the binary, presumably by unpacking the zip file and copying its contents to the right locations using their file manager that has root acess. SuperSU keeps saying SU Binary Occupied. very simple solution reflash kernel reboot go to app drawer unistall magisk long press icon back to twrp flash supersu wipe cache dalvik reboot <ID:0/009> Complete(Write) operation failed. <OSM> All threads completed. (succeed 0 / failed 1) Problem solved. Disconnected phone from computer. Overview- SuperSU is tradition way to root android but Magisk is the new tech which makes android rooting really easy and effective, you will learn to Install Magisk on both rooted and unrooted android device. Rooting an Android framework gives you access to multiple features that are not available in the default mode. Although the traditional ‘SuperSu‘ method of rooting has an established I have a lg optimus g pro f240 running on android os version 4.4.2. I recently rooted the phone using the software in This thread I have installed SuperSu though each time I try and open it, it te... SuperSU is a Superuser management tool for rooted devices . XDA’s Apps. Nav Gestures. Add swipe gestures to any Android, no root. One handed mode

[index] [7639] [3570] [5506] [14594] [7071] [29704] [19735] [17981] [3902] [31042]

The basics of binary options and what's in it for you

Chetu's capital markets, gaming, and binary options software development, integration, and implementation experts are fully compliant with strict regulatory standards inherent to the finance and ... Best Binary Options Strategy 2020 - 2 Min Strategy Live Session! - Duration: 13:35. BLW Online Trading 244,815 views. 13:35. 1 Minute Strategy 2,019! - Derivative Oscillator // 90% ITM! This method will show you how to fix root access problem we come across several devices while the process of rooting. This process supports almost all the Android devices and Android versions. If ... #binary_options_trading #binary_options_strategy_2020 #binary_options #binary_options_strategy #binary_options_strategies #binary_options_signals Loading... Autoplay When autoplay is enabled, a ... You've heard about binary options but you don't know if they're right for you. In this session you'll learn the basics of binary options: what are they, why you care, and how you could potentially ...

Flag Counter