Develop Bugs

[Q] Proper Way to Flash SuperSU.zip/Root N7 - Fresh Tablet 4.4.2??

Long story short, I was a victim of the bricked/unrecoverable OTA update situation that seems to be plaguing everyone lately. ASUS did repair my tablet, so it got back to me last week and it a fresh, untouched 4.4.2 as far as I can tell.
I am trying to get a better handle on the "proper", manual non-toolkit way of doing everything. I am up to the unlocked bootloader and have TWRP 2.8.4.0 flashed for recovery - now to root and updating.
My confusion with with flashing the SuperSU zip - should you just always us the most updated version (and where is the "proper" source everyone uses) or are there certain versions of SuperSU that pair correctly with different OS numbers (4.4.2, 4.4.4, 5.0.2, etc)? Is it always as simple as flashing the SuperSU.zip through TWRP after updating via factory image flash to a different OS version #? (Say from 4.4.2 now and flashing to 4.4.4 or 5.0.2)?
When I exited TWRP the first time after flashing it, it said I did not have superSU installed and did I want to - will that process auto-flash the zip and root the N7 with the correct superSU version (it is the latest TWRP release 2.8.4.0) or do I need to download the proper superSU.zip for TWRP to then find on my internal storage when that prompt comes up?
Thanks,

Norcalz71 said:
Long story short, I was a victim of the bricked/unrecoverable OTA update situation that seems to be plaguing everyone lately. ASUS did repair my tablet, so it got back to me last week and it a fresh, untouched 4.4.2 as far as I can tell.
I am trying to get a better handle on the "proper", manual non-toolkit way of doing everything. I am up to the unlocked bootloader and have TWRP 2.8.4.0 flashed for recovery - now to root and updating.
My confusion with with flashing the SuperSU zip - should you just always us the most updated version (and where is the "proper" source everyone uses) or are there certain versions of SuperSU that pair correctly with different OS numbers (4.4.2, 4.4.4, 5.0.2, etc)? Is it always as simple as flashing the SuperSU.zip through TWRP after updating via factory image flash to a different OS version #? (Say from 4.4.2 now and flashing to 4.4.4 or 5.0.2)?
When I exited TWRP the first time after flashing it, it said I did not have superSU installed and did I want to - will that process auto-flash the zip and root the N7 with the correct superSU version (it is the latest TWRP release 2.8.4.0) or do I need to download the proper superSU.zip for TWRP to then find on my internal storage when that prompt comes up?
Thanks,
Click to expand...
Click to collapse
You got it, flash recovery and select yes when it asks you if you want to install SU binary. If you plan on sticking with KitKat (that's what I'm doing, I hate Lollipop), then I recommend flashing the 4.4.4 system image via fastboot first, then flash recovery again, and then let TWRP install SU. I actually just did this yesterday. I dusted off my N7 after a year of not using it and it was still on 4.4.2 so yesterday I updated it to 4.4.4 by flashing a system image. Wanted a clean start.
I'm pretty sure it works the same for lollipop now too. Originally you needed to flash a special kernel, but I think now you can root it the same way as Kit Kat, ie. via recovery. Someone can correct me if I'm wrong but I don't think I am.

_MetalHead_ said:
You got it, flash recovery and select yes when it asks you if you want to install SU binary. If you plan on sticking with KitKat (that's what I'm doing, I hate Lollipop), then I recommend flashing the 4.4.4 system image via fastboot first, then flash recovery again, and then TWRP install SU. I did this yesterday. I dusted off my N7 after a year of not using it and it was still on 4.4.2 so yesterday I updated it to 4.4.4 by flashing a system image. Wanted a clean start.
Click to expand...
Click to collapse
10-4, thanks. So the 2.8.4.0 version of TWRP should already have that SU binary ready to roll (could either choose to flash it now and be rooted on 4.4.2, or fastboot flash the factory 4.4.4 and then reflash TWRP and flash the su zip?) No further superSU.zip/binary downloads, essentially?
I also think I will go with 4.4.4 for now, the 5.0.1 bricking my tablet left a bad aftertaste, it was OTA though. Perhaps fastboot factory image would have no issues.

Norcalz71 said:
10-4, thanks. So the 2.8.4.0 version of TWRP should already have that SU binary ready to roll (could either choose to flash it now and be rooted on 4.4.2, or fastboot flash the factory 4.4.4 and then reflash TWRP and flash the su zip?) No further superSU.zip/binary downloads, essentially?
I also think I will go with 4.4.4 for now, the 5.0.1 bricking my tablet left a bad aftertaste, it was OTA though. Perhaps fastboot factory image would have no issues.
Click to expand...
Click to collapse
It'll install the SU binary but then once you boot into the OS it prompts you to download SuperSU from the play store. Once you download it and open it, it'll prompt you to update the SU binary. Just hit yes and it'll do it for you, and then you reboot and you're done.

_MetalHead_ said:
It'll install the SU binary but then once you boot into the OS it prompts you to download SuperSU from the play store. Once you download it and open it, it'll prompt you to update the SU binary. Just hit yes and it'll do it for you, and then you reboot and you're done.
Click to expand...
Click to collapse
Awesome, thanks man. From all the various threads about how to root, it makes it seem WAY more involved than that.

Norcalz71 said:
Awesome, thanks man. From all the various threads about how to root, it makes it seem WAY more involved than that.
Click to expand...
Click to collapse
No prob bud. One of the big benefits of Nexus devices is that they are super simple to root. Heck, they are super simple to do pretty much anything on. That's the only reason why I decided to start from scratch yesterday, because it's like nothing to do. The longest part was re-downloading all my apps, but still the whole process took about 30 min start to finish. If you're not downloading a ton of apps, it'll take you 5 minutes.

m8 shows no root after update

after updating my m8 to lollipop, the device says unroot. software status is still unlocked, I went through the rooting process again,flashed twrp recovery. but cant install anything aa it says device is not rooted.

kalim_714 said:
after updating my m8 to lollipop, the device says unroot. software status is still unlocked, I went through the rooting process again,flashed twrp recovery. but cant install anything aa it says device is not rooted.
Click to expand...
Click to collapse
Hi there,
i have the same Problem.
after ota to 5.01 i rooted my m8 with toolkit , everything goes fine (also perm root and install superSu).
But after restart and automatical apps updates, the supersu app says that su files is missing and there ist no root anymore.
How can i solve that rpoblem? thanks alot
John

John-Wu said:
Hi there,
i have the same Problem.
after ota to 5.01 i rooted my m8 with toolkit , everything goes fine (also perm root and install superSu).
But after restart and automatical apps updates, the supersu app says that su files is missing and there ist no root anymore.
How can i solve that rpoblem? thanks alot
John
Click to expand...
Click to collapse
I've never used a toolkit on my HTC devices, so I can't speak to their effectiveness. Perhaps they need an update to work with Lollipop.
I recommend using TWRP recovery (just because it's the one I used and I know it worked for me. Can't speak to CWM or Philz)
Flash the SuperSU update zip found here: http://download.chainfire.eu/695/SuperSU/

craig0r said:
I've never used a toolkit on my HTC devices, so I can't speak to their effectiveness. Perhaps they need an update to work with Lollipop.
I recommend using TWRP recovery (just because it's the one I used and I know it worked for me. Can't speak to CWM or Philz)
Flash the SuperSU update zip found here: http://download.chainfire.eu/695/SuperSU/
Click to expand...
Click to collapse
hi,
thanks alot. that's it!!
with toolkit i've already installed TWRP and with the updated SuperSu (your link) i've root again.
once again, thanks!

Systemless OTA upgrade

I know there are several threads covering similar things, however I still can't find the relevant info for my specific question.
I am on 6.0 Build L
I rooted using systemless root - I have changed nothing in my system partition as far as I know as I wanted root for AdBlock and TitaniumBU.
I am using the stock kernel too.
TWRP 2.8.7.2
I now have a 6.0.1 OTA - but I'm 100pc confused as to exactly how to go about installing this.
Some people seem to say OTA on this setup will work fine on similar setups.
Others say I need to flash 101 things to get it working.
Literally no idea.

How I Did it...
From a site with this in the title:
can_i_manually_flash_601_also_does_ota_work_with
Systemless root doesn't break ota, non-stock recovery breaks OTA.
Unlock bootloader, flash 6.0.1, flash TWRP, flash systemless root...
I did this:
Went back to stock recovery, by flashing via ADB, rebooted downloaded and attempted to install OTA on phone. Process started, rebooted, proceeded and then failed with error . Rebooted, got Factory image.
Extracted and ran flash-all.bat ONLY AFTER Removing the -w from this line:
fastboot -w update image-bullhead-mmb29k.zip
Got latest SuperSU v2.61 zip with auto boot patcher:
See androiding.how/android-6-0-1-root
Copied this to Memory on phone.
Flashed/Installed TWRP Recovery using ADB.
Booted into TWRP Recovery and installed SuperSU.
So now I'm running systemless rooted 6.01 on a Nexus 5X with mmb29k and every thing is working.
I think even though I rooted systemless 6.0, the modified Boot Image was still not letting OTA work.
We shall have to wait and see on the next OTA. Maybe just going back to stock recovery will be all that's needed.
There are some ADB commands that allow you to temporarily select a recovery image, but I'm not sure how that works.
Good Luck!
teapea said:
I know there are several threads covering similar things, however I still can't find the relevant info for my specific question.
I am on 6.0 Build L
I rooted using systemless root - I have changed nothing in my system partition as far as I know as I wanted root for AdBlock and TitaniumBU.
I am using the stock kernel too.
TWRP 2.8.7.2
I now have a 6.0.1 OTA - but I'm 100pc confused as to exactly how to go about installing this.
Some people seem to say OTA on this setup will work fine on similar setups.
Others say I need to flash 101 things to get it working.
Literally no idea.
Click to expand...
Click to collapse

Rooting on Sense Marshmallow

Hi, I can't seem to be able to root my phone since I upgraded to Marshmallow.
Been using TWRP 2.8.7.0 and SuperSU v2.46. I get stuck on the HTC logo at boot after installing superSU.
Any ideas?

On Marshmallow you could try to use the beta 2.66. This version has a nice to accomplish systemless root, were root is written to boot.img and /data instead of system partition.
As I'm on Maximus HD which comes prerooted with v2.65 I can tell that this version works flawlessly on Marshmallow devices.
Send by the swarm intelligence of my coffee machine (AKA HTC One M9).

Freaksterz said:
Hi, I can't seem to be able to root my phone since I upgraded to Marshmallow.
Been using TWRP 2.8.7.0 and SuperSU v2.46. I get stuck on the HTC logo at boot after installing superSU.
Click to expand...
Click to collapse
Root on Marshmallow has been discussed quite a bit on this forum.
SuperSU 2.46 won't work, no way. Its not updated for MM.
SuperSU 2.51 Beta or higher versions should work. They will give you the option of systemless or traditional root methods (read up on existing threads to learn the difference/benefits of each).

redpoint73 said:
Root on Marshmallow has been discussed quite a bit on this forum.
SuperSU 2.46 won't work, no way. Its not updated for MM.
SuperSU 2.51 Beta or higher versions should work. They will give you the option of systemless or traditional root methods (read up on existing threads to learn the difference/benefits of each).
Click to expand...
Click to collapse
So let's say I'm in marshmallow with trwp 3.0.0
Which version of supersu should I flash and which MOD should I choose ?

ofir_a said:
Which version of supersu should I flash and which MOD should I choose ?
Click to expand...
Click to collapse
SuperSU 2.51 or later will work with MM, as I've already stated. As a number of updated SuperSU versions have been released since that post, so newer may/may not be better. Version 2.65 is the most recent to be labelled STABLE, so if it were me, I'd probably go with that.
The difference between systemless root versus "traditional" root is discussed in a number of places. For instance, you can look in the SuperSU forum section here on XDA. But here is some explanation of the "systemless" approach: http://forum.xda-developers.com/showpost.php?p=63197935
Alternately, I believe (although not sure) that TWRP 3.0.0.0 is updated to properly root MM on our device, using the built-in root option in TWRP. As always, make a TWRP backup before trying any of the above methods, just in case anything goes wrong!

redpoint73 said:
SuperSU 2.51 or later will work with MM, as I've already stated. As a number of updated SuperSU versions have been released since that post, so newer may/may not be better. Version 2.65 is the most recent to be labelled STABLE, so if it were me, I'd probably go with that.
The difference between systemless root versus "traditional" root is discussed in a number of places. For instance, you can look in the SuperSU forum section here on XDA. But here is some explanation of the "systemless" approach: http://forum.xda-developers.com/showpost.php?p=63197935
Alternately, I believe (although not sure) that TWRP 3.0.0.0 is updated to properly root MM on our device, using the built-in root option in TWRP. As always, make a TWRP backup before trying any of the above methods, just in case anything goes wrong!
Click to expand...
Click to collapse
Thanks a lot

redpoint73 said:
Root on Marshmallow has been discussed quite a bit on this forum.
SuperSU 2.46 won't work, no way. Its not updated for MM.
SuperSU 2.51 Beta or higher versions should work. They will give you the option of systemless or traditional root methods (read up on existing threads to learn the difference/benefits of each).
Click to expand...
Click to collapse
Thanks for the insights. I was trying to root my m8 after almost 2 years, I didn't know about the complexity of the SuperSu for marshmellow, finally figured that I flashed 2.37 version of SuperSu. No matter what I do I am stuck in the htc logo bootloop. I'm in desperation but I can't flash the updated version of SuperSu if it's not in the internal memory(or is there any way). And I can't put that file in the internal memory if i don't have an access to it. How do I go about it? I've been trying to find a solution for the last 4 hours, it's 3 in the morning. Help.

post.ratz said:
I was trying to root my m8 after almost 2 years, I didn't know about the complexity of the SuperSu for marshmellow, finally figured that I flashed 2.37 version of SuperSu.
Click to expand...
Click to collapse
Good rule of thumb, on any Android device, is that the root method almost always changes with major build updates (Lollipop, Marshmallow, etc.). So you always need to research for the most current root method for the specific Android build and the specific device.
As mentioned, you should flash SuperSU 2.51 or higher for MM. SuperSU 2.65 is recommended (latest "stable" version).
post.ratz said:
No matter what I do I am stuck in the htc logo bootloop
Click to expand...
Click to collapse
That statement tells us nothing about what you actually tried, nor the specific result for each attempted method.
post.ratz said:
I'm in desperation but I can't flash the updated version of SuperSu if it's not in the internal memory(or is there any way). And I can't put that file in the internal memory if i don't have an access to it.
Click to expand...
Click to collapse
If you made a TWRP backup before rooting (which you should always do before rooting, for this very reason) just restore the backup.
Otherwise, you can adb push the proper SuperSU file with the phone booted into TWRP recovery.
Or use a card reader connected to your computer, to put the file on a removable MicroSD card (then insert card into phone).
You may or may not also be able to mount internal storage (see it on your computer) while booted into TWRP; either in default MTP mode, or you can try to mount USB storage in the TWRP "Mount" options. But mounting storage in TWRP has always been a bit finicky and inconsistent for me.

redpoint73 said:
Good rule of thumb, on any Android device, is that the root method almost always changes with major build updates (Lollipop, Marshmallow, etc.). So you always need to research for the most current root method for the specific Android build and the specific device.
As mentioned, you should flash SuperSU 2.51 or higher for MM. SuperSU 2.65 is recommended (latest "stable" version).
That statement tells us nothing about what you actually tried, nor the specific result for each attempted method.
If you made a TWRP backup before rooting (which you should always do before rooting, for this very reason) just restore the backup.
Otherwise, you can adb push the proper SuperSU file with the phone booted into TWRP recovery.
Or use a card reader connected to your computer, to put the file on a removable MicroSD card (then insert card into phone).
You may or may not also be able to mount internal storage (see it on your computer) while booted into TWRP; either in default MTP mode, or you can try to mount USB storage in the TWRP "Mount" options. But mounting storage in TWRP has always been a bit finicky and inconsistent for me.
Click to expand...
Click to collapse
Hey, thanks for the reply. It probably was too late at night and my mind had stopped functioning, a little common sense was all that was needed. The bootloop had only occurred because of me flashing the lower version of SuperSu. The good rule of thumb, forgive my lack of knowledge, I had no idea that a rooting of a device may change with the upgraded version of the OS. Woke up, took my external memory card out, transferred the SuperSu 2.65 on it and later flashed it though recovery.
Rest assured, I'll never go for a phone that does not have expandable storage option.
Thanks

How to remove Root from Galaxy Tab S?

I bought a second hand Samsung Galaxy Tab S a few months ago and it has been working fine.
However, when I looked at version of Android then seems a bit old (5.0.2) and when I did a check for updates it said that it couldn't update because "The operating system on your device has been modified in an unauthorised way". When I checked then it seems that the device has been rooted.
A quick search suggested I should run SuperSU to remove the root. So, I had to download and install this, but, when I run it says "The SU binary needs to be updated. Continue?" - if I do then I get another message "If you have a custom recovery like TWRP or CWM that can be used to (try to) install the SU binary" and gives me a choice of Normal or TWRP/CWM. I am struggling to know how to proceed.
So, should it be possible to remove the root and still preserve all my data, apps, settings, etc?
If so, is SuperSu the way to go or are there other tools I should look at, such as Kingo Android Root?
Or, am I faced with rebuilding with a stock ROM?
Thanks

There is no update. 5.0.2 is the latest.

ashyx said:
There is no update. 5.0.2 is the latest.
Click to expand...
Click to collapse
OK, thanks for info.
However, I would still like to remove Root and would appreciate advice on this, please!

MysteryMan1 said:
OK, thanks for info.
However, I would still like to remove Root and would appreciate advice on this, please!
Click to expand...
Click to collapse
If your root manager is supersu then it has the option to unroot in it's settings.
Sent from my SM-T800 using XDA Premium HD app

3DSammy said:
If your root manager is supersu then it has the option to unroot in it's settings.
Sent from my SM-T800 using XDA Premium HD app
Click to expand...
Click to collapse
I've tried to fire up SuperSU, but, run into problems, as described in my initial post, and this is what I need to resolve.
Any ideas?

MysteryMan1 said:
... A quick search suggested I should run SuperSU to remove the root. So, I had to download and install this, but, when I run it says "The SU binary needs to be updated. Continue?" - if I do then I get another message "If you have a custom recovery like TWRP or CWM that can be used to (try to) install the SU binary" and gives me a choice of Normal or TWRP/CWM. I am struggling to know how to proceed.
...
Click to expand...
Click to collapse
I'm having a bit of trouble understanding the end goal. As stated Android v5.0.2 is the latest non-custom firmware available. As a previous owner has unlocked the bootloader and seems to have flashed a SuperSu version that modification is blocking any OTA update to v5.0.2. It is also clear your trying to avoid loosing user data.
Would it be acceptable to be rooted and use a different method to apply the latest Samsung stock firmware for your region? If the answer is yes install a TWRP recovery for your device model but you'll loose your warranty by tripping KNOX (you may already be in that state). Follow the instructions in the TabS TWRP thread.
Then finish the SuperSU install (where your stuck today). Then install Flashfire. With Flashfire and the downloaded latest Samsung firmware package you can flash the boot and system images to update your install then use ODIN to update the Bootloader image from that download firmware. You could also flash the recovery image but that would overwrite TWRP and in your case I don't see the point. Flashfire needs the whole Samsung firmware file to be available on the device itself unlike when using ODIN to flash the Bootloader image.
As I'm rooted but retained my warranty I use FlashFire and ODIN to update to the latest stock firmware and never loose user data. Unfortunately to root and not trip KNOX I did wipe my user data that first time so it does not seem to be an option for you.
Hope that gives you some ideas. In your current state it maybe as simple as completing the SuperSU install (assuming a custom recovery (TWRP/CM) is already installed) then using Flashfire and ODIN as described.
Good luck

3DSammy said:
I'm having a bit of trouble understanding the end goal. As stated Android v5.0.2 is the latest non-custom firmware available. As a previous owner has unlocked the bootloader and seems to have flashed a SuperSu version that modification is blocking any OTA update to v5.0.2. It is also clear your trying to avoid loosing user data.
Would it be acceptable to be rooted and use a different method to apply the latest Samsung stock firmware for your region? If the answer is yes install a TWRP recovery for your device model but you'll loose your warranty by tripping KNOX (you may already be in that state). Follow the instructions in the TabS TWRP thread.
Then finish the SuperSU install (where your stuck today). Then install Flashfire. With Flashfire and the downloaded latest Samsung firmware package you can flash the boot and system images to update your install then use ODIN to update the Bootloader image from that download firmware. You could also flash the recovery image but that would overwrite TWRP and in your case I don't see the point. Flashfire needs the whole Samsung firmware file to be available on the device itself unlike when using ODIN to flash the Bootloader image.
As I'm rooted but retained my warranty I use FlashFire and ODIN to update to the latest stock firmware and never loose user data. Unfortunately to root and not trip KNOX I did wipe my user data that first time so it does not seem to be an option for you.
Hope that gives you some ideas. In your current state it maybe as simple as completing the SuperSU install (assuming a custom recovery (TWRP/CM) is already installed) then using Flashfire and ODIN as described.
Good luck
Click to expand...
Click to collapse
Thank you for your very helpful and comprehensive reply. I can't profess to understanding all of it, but, I am sure I will get there eventually!
I shall follow your suggestion of trying to get get SuperSU installed first.
:good:

If you want to go back to stock just flash the latest firmware with odin.