Develop Bugs

Root for Stock 6.0.1

From rooted 6.0, I took the OTA and was stuck. Finally wiped everything and installed 6.0.1 fresh. flashed TWRP and supersu 2.60. But after boot, Supersu says binary needs to be updated - but fails to update.
TWRP works fine. Just can't root 6.0.1 with unlocked bootloader. Can anyone share the supersu that worked for 6.0.1? TIA

http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3

Root works with supersu version 2.62-3. Thanks

sam298 said:
From rooted 6.0, I took the OTA and was stuck. Finally wiped everything and installed 6.0.1 fresh. flashed TWRP and supersu 2.60. But after boot, Supersu says binary needs to be updated - but fails to update.
TWRP works fine. Just can't root 6.0.1 with unlocked bootloader. Can anyone share the supersu that worked for 6.0.1? TIA
Click to expand...
Click to collapse
That wasn't my experience. I took the 6.0.1 update and it failed. So I ran
Code:
fastboot flash system system.img
fastboot flash boot boot.img
using the system and boot images from the 6.0 update. And then I waited for the OTA again. It installed ok.
Using TWRP I installed SuperSU 2.60 for a systemless root of the boot image. Everything is fine.

i can't even get pass installing twrp. every time i flash twrp in fastboot mode it works but it wipes my entire device. booting into twrp shows "NO OS INSTALLED' and even the sd card storage is wiped. the only way to get it to boot is to flash back 6.0.1 full stock rom. any help???

Try nexus root toolkit.

tomxass said:
Try nexus root toolkit.
Click to expand...
Click to collapse
WugFresh did not work for me, after booting into TWRP and looking for the SuperSU and BusyBox they don not show up. Below is a post I have over on WugFresh Forum.
I’m having the same problem as everyone else. I’m using 6.0.1 MMB29K. It goes through the motions but when TWRP launches the /sdcard directory is empty. However, when I reboot and look at the files using an app called File Manager, I see them in /storage/emulated/0/!ReadyToFlash/Root_Files/. However, if I use a app called Root Browser I see a directory called sdcard and in there is !ReadyToFlash/Root_Files/ so they are being copied to the tablet but when you go into TWRP to install them they can’t be found. I tried to use the app Root Browser and make a directory called kiledl, this failed, probably because I do not have root access. Kind of a catch 22 here. I was just going to copy the files in sdcard to my directory and then try again. NO go!!! Anyone else have any ideas? I seems like this is some sort of permissions issue with the files but only from TWRP. I sure hope someone comes up with an answer, WugFresh and ideas?

tomxass said:
Try nexus root toolkit.
Click to expand...
Click to collapse
same result. twrp installed but can't detect my sd card or any files on the device

Download latest SuperSU 2.62-3.
Root via Nexus root toolkit.
Then copy SuperSu to nexus and flash, supersu not from NRT but downloaded latest 2.62-3, busybox and last rar.
Sorry for my English.

Found a solution, the version of TWRP that WugFresh NRT is using is not compatible with this version of the N7 seems as though these were made with a different MMC memory. Check you this link and download this modified version of TWRP. You can use the NRT Advance Utilities > fastboot flash > recovery > other and then point to this modified version of TWRP and install it. Then you can proceed with the install of SuperSU and BusyBox. They will show up in the !ReadyToFlash/Root_Files/ folder to install.
Check this link **UPDATE** Mounting Errors in Custom Recovery
**UPDATE** Mounting Errors in Custom Recover… | Nexus 7 (2013)

dlkile said:
Found a solution, the version of TWRP that WugFresh NRT is using is not compatible with this version of the N7 seems as though these were made with a different MMC memory. Check you this link and download this modified version of TWRP. You can use the NRT Advance Utilities > fastboot flash > recovery > other and then point to this modified version of TWRP and install it. Then you can proceed with the install of SuperSU and BusyBox. They will show up in the !ReadyToFlash/Root_Files/ folder to install.
Check this link **UPDATE** Mounting Errors in Custom Recovery
**UPDATE** Mounting Errors in Custom Recover… | Nexus 7 (2013)
Click to expand...
Click to collapse
noooo. That's not true. I just used NRT yesterday to upgrade to rooted 6.01.
EDIT: I think I misundersstood your post. This is only a problem if you try to install TWRP when upgrading right? If you just want to upgrade to 6.01 and keep stock recovery there is no issue.

aiiee said:
noooo. That's not true. I just used NRT yesterday to upgrade to rooted 6.01.
EDIT: I think I misundersstood your post. This is only a problem if you try to install TWRP when upgrading right? If you just want to upgrade to 6.01 and keep stock recovery there is no issue.
Click to expand...
Click to collapse
Yes it is true, it depends on what kind of eMMC chip is in it. I have a very new device and NRT would not root it. When it booted in TWRP it could not see the !ReadyToFlash/Root_Files/ folder to install the files. There was no files on SDCard at all unless you booted to Android to verify they were in fact there. I had to install the modified Recovery TWRP file first. Saying "noooo. That's not true." is a little harsh, kinda make me a liar, I think NOT. Just because the method worked for you does not mean it worked for me. Not all devices are the same. If you read other post here you will see lots of others are having the same problem.

aiiee said:
EDIT: I think I misundersstood your post. This is only a problem if you try to install TWRP when upgrading right? If you just want to upgrade to 6.01 and keep stock recovery there is no issue.
Click to expand...
Click to collapse
Correct only when using TWRP. However, I was using WugFresh NRT and it does a temporary install of TWRP then you install the SuperSU and BusyBox files. However, with the wrong version of TWRP you would not see the files in the SDCard folder, it would be empty. However, booting back to Android and using File Explorer the files where there. Using the modified version of TWRP would correct this.

interesting. i was wondering why some persons say it work and when i tried it, it wouldn't show anything in twp. can you point me to the link of the modified/correct version of twrp to use or help me by saying what to search. i don't want to sound lazy bu asking you for the link but i'm not sure as to what to google exactly to find the correct twrp to use. obviously i've been google wrong the pass few days because that hasn't come up for me in any of my past searches
Update: i found it and it works. thanks guys. now i can flash some custom roms. gonna try cm 13 tonight. thanks again

r.sorujlall said:
interesting. i was wondering why some persons say it work and when i tried it, it wouldn't show anything in twp. can you point me to the link of the modified/correct version of twrp to use or help me by saying what to search. i don't want to sound lazy bu asking you for the link but i'm not sure as to what to google exactly to find the correct twrp to use. obviously i've been google wrong the pass few days because that hasn't come up for me in any of my past searches
Update: i found it and it works. thanks guys. now i can flash some custom roms. gonna try cm 13 tonight. thanks again
Click to expand...
Click to collapse
Yes, here is the link you need to select the LTE or WiFi version depending on you device. I do not have enough post to be able post links, so try removing the "*" from the link below.
forum*.xda-developers*.com/nexus*-7-2013/nexus*-7-2013-qa/mount*-recovery*-t3064562

dlkile said:
Yes it is true, it depends on what kind of eMMC chip is in it. I have a very new device and NRT would not root it. When it booted in TWRP it could not see the !ReadyToFlash/Root_Files/ folder to install the files. There was no files on SDCard at all unless you booted to Android to verify they were in fact there. I had to install the modified Recovery TWRP file first. Saying "noooo. That's not true." is a little harsh, kinda make me a liar, I think NOT. Just because the method worked for you does not mean it worked for me. Not all devices are the same. If you read other post here you will see lots of others are having the same problem.
Click to expand...
Click to collapse
I sit corrected, sir. :good:
Just for my own edumacation, how old is your N7? I just bought two from Groupon and I wonder if they are affecteed? How can one tell ?

aiiee said:
I sit corrected, sir. :good:
Just for my own edumacation, how old is your N7? I just bought two from Groupon and I wonder if they are affecteed? How can one tell ?
Click to expand...
Click to collapse
You most have the same unit as I do. I just got mine a week ago from GroupOn as well.

i bought mine about a week ago off amazon. i had a gift card and had nothing to buy so i decided to get the N7 and give it a try

Issue rooting m9

So, this isn't my first time rooting a phone, I've done Samsung's, HTC one m8's. And trying my girlfriends m9. I've unlocked the bootloader, flashed the latest TWRP and done a full nandroid and now want to root, so I can s off. I grabbed the latest SuperSU at 2.66 and went to flash the zip. It gets to the restoring files step in the log and then the phone reboots. I've tried reinstalling TWRP, all different versions of SuperSU , betas, everything. I've tried adb sideload, still no go. I'm actually stumped and can't seem to find much information on this problem.thanks in advance for your help. Need any more info let me know.

krazydbiker said:
So, this isn't my first time rooting a phone, I've done Samsung's, HTC one m8's. And trying my girlfriends m9. I've unlocked the bootloader, flashed the latest TWRP and done a full nandroid and now want to root, so I can s off. I grabbed the latest SuperSU at 2.66 and went to flash the zip. It gets to the restoring files step in the log and then the phone reboots. I've tried reinstalling TWRP, all different versions of SuperSU , betas, everything. I've tried adb sideload, still no go. I'm actually stumped and can't seem to find much information on this problem.thanks in advance for your help. Need any more info let me know.
Click to expand...
Click to collapse
I hear ya. It took me a few tries before figuring out what worked.
This is what I did:
1) Made sure that my boot image was not previously patched;
2) Downloaded this version of SuperSU to your device: BETA-SuperSU-v2.65-20151226141550.zip
3) Flashed this recovery: twrp-2.8.7.1_CPTB-B1-hima.img
4) Booted into recovery and made sure that the option to mount system as read-only was checked;
5) Flashed SuperSU;
6) After SuperSU was flashed, made sure to prevent TWRP from installing SuperSU again if it asked;
7) Rebooted.

efrant said:
I hear ya. It took me a few tries before figuring out what worked.
This is what I did:
1) Made sure that my boot image was not previously patched;
2) Downloaded this version of SuperSU to your device: BETA-SuperSU-v2.65-20151226141550.zip
3) Flashed this recovery: twrp-2.8.7.1_CPTB-B1-hima.img
4) Booted into recovery and made sure that the option to mount system as read-only was checked;
5) Flashed SuperSU;
6) After SuperSU was flashed, made sure to prevent TWRP from installing SuperSU again if it asked;
7) Rebooted.
Click to expand...
Click to collapse
Awesome. Thanks for the help, gonna try it later on and see how it goes. Glad to know I'm not the only one haha. I'll post whether it worked or not!

And no go, installed the new TWRP, the supersu you gave me, made sure it was mounted read only, made sure the file was on the internal storage, flash supersu, crash and restart. This thing is driving me absolutely nuts.

krazydbiker said:
And no go, installed the new TWRP, the supersu you gave me, made sure it was mounted read only, made sure the file was on the internal storage, flash supersu, crash and restart. This thing is driving me absolutely nuts.
Click to expand...
Click to collapse
Did you flash the stock boot image and stock system image first? It's best to start from scratch. I was having issues until I started with a completely stock boot image and system image.

Problems post super su install

So I installed TWRP and then moved on to install super su which is where the problem started. First I attempted to install SR1-SuperSU-v2.78-SR1-20160915123031.zip. Everything ran but after it led to a boot loop. After that I realized I had tried to install the latest file but not the latest STABLE file, so I then tried to install UPDATE-SuperSU-v2.78-20160905010000.zip to no avail. I then noticed when I go in to download mode i get a "FILE /mnt/media_rw/ext_sd/OPJAIMG.zip File Not FOUND" error on the bottom. Any idea how i could sort this out? (like a fool I did not make a backup before doing this) I downloaded the RUU (RUU_HIMA_UL_M60_SENSE70_ATT_MR_Cingular_US_3.38.502.17) but I wanted some advice before i do that so i don't mess it up more.
ATT m9
os 3.38.502.21
s-on
TWRP 3.0.2-0

Download Mode checks for this file to update the Firmware. If you are not planning on updating that, you don't need that file on your Phone. It's more a notice that an actuall error

Alright, that's encouraging. Any idea why i would get a boot loop after trying to install super su though? That's where I'm stuck right now. I'm not opposed to going back to stock and starting over if that's the only option. I just want my phone to be usable again.

Well if it installed in Systemless mode, it can cause a bootloop for a while, you might just need to be patient. Otherwise, i would maybe try an older version of SuperSu. I think 2.76 was pretty safe to install

I let it boot loop over night so no dice there. I'll give the older version a try. Hopefully that works.

No luck with 2.76. It boot looped for a half hour. Any other thoughts?

erics87 said:
No luck with 2.76. It boot looped for a half hour. Any other thoughts?
Click to expand...
Click to collapse
Yes, don't flash any newer version than 2.65. Updating via the play store afterwards is safe, though.
Sent from my HTC One S using XDA Labs

I had the exact problem, lucky enough i could fetch some log files during boot and sent them to chainfire, maybe we will see a fix someday
SuperSU 2.65 seems to be the latest version working in system-less mode on the HTC One M9, updating through Google Play Store works fine tho.
I will look for the log in a couple minutes and post it here for all that are interested
But don't worry, atleast it didn't brick our phone

Phone is stuck in bootloop! [SOLVED]

Hi,
I understand this is probably a common problem with a simple fix, but this is my first attempt to root. My phone is unlocked and s-off, running 3.37.605.7. I used TWRP to install SuperSU and then after rebooting, it was stuck in a bootloop. After doing some research I think maybe I installed the wrong version of SuperSU, but I can't figure out how to fix it. I did a backup with adb beforehand, but when I tried restoring it said to unlock my phone and confirm, and I can't unlock my phone. I tried doing the restore command with TWRP open and it seemed to do something at first, but then nothing. I'm really stuck and would appreciate some help.
Thanks!

Are you wanting to keep the data you have on the phone or, would you be OK with starting fresh?

RoyalDrew said:
Are you wanting to keep the data you have on the phone or, would you be OK with starting fresh?
Click to expand...
Click to collapse
I'm fine with losing data. Actually I just flashed the RUU again and it's working again. I'll try to root again later.

jrzee45 said:
I'm fine with losing data. Actually I just flashed the RUU again and it's working again. I'll try to root again later.
Click to expand...
Click to collapse
After you get TWRP back, flash View attachment BETA-SuperSU-v2.65.zip to get root.
I just went through the same mess as you with the newer SuperSu versions. I read somewhere that 2.65 was the latest that would work and this is the zip I used.

RoyalDrew said:
After you get TWRP back, flash View attachment 4082602 to get root.
I just went through the same mess as you with the newer SuperSu versions. I read somewhere that 2.65 was the latest that would work and this is the zip I used.
Click to expand...
Click to collapse
Just flashed 2.65 and it worked! Thanks so much.

Unable to boot
Anyone having issues with this ROM. I flashed using TWRP 2.8.7.0, S-OFF and Unlocked, after flashing, phone reboots into aboot and i select reboot, and it rebots to aboot again without booting to the rom.

SuperSu Bricked - please help

Hi!
SuperSu requested an update of the binaries and I followed as instructed.
After the reboot phone did get into bootloop. Google showed me this thread:
https://forum.xda-developers.com/ap...78-release-t3452703/post72428986#post72428986
So I followed the instructions their and installed SR3-SuperSU-v2.79-SR3-20170114223742.zip
The bootloop didn't stopped now I'm kinda lost what todo.
Can you point me what to do to get the phone back to running? Thanks!!

From supersu.com/download, I installed "Recovery V2.79 Flashable.zip" which seemed to fix the problem. (I'm a new user and I can't post links)

C0qRouge said:
Hi!
SuperSu requested an update of the binaries and I followed as instructed.
After the reboot phone did get into bootloop. Google showed me this thread:
https://forum.xda-developers.com/ap...78-release-t3452703/post72428986#post72428986
So I followed the instructions their and installed SR3-SuperSU-v2.79-SR3-20170114223742.zip
The bootloop didn't stopped now I'm kinda lost what todo.
Can you point me what to do to get the phone back to running? Thanks!!
Click to expand...
Click to collapse
I've flashed that Supersu several times without issue.. Must be some other problem. What rom were you on, and what other mods, etc.?

rqpg said:
From supersu.com/download, I installed "Recovery V2.79 Flashable.zip" which seemed to fix the problem. (I'm a new user and I can't post links)
Click to expand...
Click to collapse
Hi!
I was running into the same trouble boot looping after upgrading to 2.82. I am on DStrikersZ1 SP007
Solved by entering recovery an flash "Recovery V2.79 Flashable.zip", but SU-GUI under settings - ROM Control is gone.
Root access is still possible (Titanium Backup still running smooth). Maybe try an older one and disable automatic update of superSU.
Maybe different on other ROMs.
Greets!

I fixed it by installing the Test1 zip of 28.04.2017 provided by Chainfire and also wiped Cache / Dalvik. Didn't checked if the gui is there, but Chainfire already said that this could happend and that you should uninstal it via adb and install the gui again.
I'm on stock btw. @levone1 I provided a link to the problem but you didn't care to check the link and instead wrote some .....

C0qRouge said:
I fixed it by installing the Test1 zip of 28.04.2017 provided by Chainfire and also wiped Cache / Dalvik. Didn't checked if the gui is there, but Chainfire already said that this could happend and that you should uninstal it via adb and install the gui again.
I'm on stock btw. @levone1 I provided a link to the problem but you didn't care to check the link and instead wrote some .....
Click to expand...
Click to collapse
Sorry, I just wanted to start from scratch... Glad it worked out.

hi
follow these steps
1 kernel flash .108
2 enters the recovery
3 installs supersu zip 4.79
4 installs rom [D5503] [Stock] [PRF + FTF] [Lollipop] 14.6.A.1.236
5 restart
I had the same problem and solved it

Update!
after downgrading to 2.79 i flashed new version from chainfire.
see https://www.xda-developers.com/supersu-v2-82-released-on-the-google-play-store/
No bootloop. But the gui was gone. Solved by installing supersu via Playstore.

Just got this sorted out...
Updated the binaries today and bootloop...
Recovery flash v2.79 helped.
Flashed from recovery. Reboot. The usual optimisation of apps.
Phone started normally after that.
No SuperSU after boot. Had to install from PlayStore, but didn't update the binaries though.
Root is working fine after that.
On Stock ROM .236

Installing the Test.zip file in TWRP solved my bootloop.
Thanks C0q

Going back back to v2.78..