Sign in to follow this  
Followers 0
iR1O

Root [Solved]

19 posts in this topic

I wanted to start a thread as a placeholder for when/if root becomes available to us.

 

If anyone has ideas, news, theories, whatever - lemme know and I can test, but for now it seems that were kinda SOL.

 

EDIT

I see that in developer settings the Allow OEM Unlock is there, and you can turn it on - could that be a positive sign?

 

I still cant get it to show up in adb/fastboot devices - idk why.  I can control it via adb in recovery, but not in download mode, it's not seen at all.

Share this post


Link to post
Share on other sites

Allow OEM Unlock is available on any 5.0+ ROM in Dev Settings, but it's not necessarily an indication of the bootloader's ability to be unlocked.  Case in point:  Moto X 2014 on Verizon/AT&T


But I'm hopeful for ya!  It seems to be a popular device, maybe there'll be a workaround or backdoor.  Don't system update!  Often times devs can find exploits by comparing the patches that Sammy pushes to the old code.

Share this post


Link to post
Share on other sites
On 3/29/2016 at 10:11 AM, iRub1Out said:

I wanted to start a thread as a placeholder for when/if root becomes available to us.

 

If anyone has ideas, news, theories, whatever - lemme know and I can test, but for now it seems that were kinda SOL.

 

EDIT

I see that in developer settings the Allow OEM Unlock is there, and you can turn it on - could that be a positive sign?

 

I still cant get it to show up in adb/fastboot devices - idk why.  I can control it via adb in recovery, but not in download mode, it's not seen at all.

 

Unfortunately I do believe the OEM Unlocking is purely to disable the FRP Lock. Seeing as if you enable OEM Unlocking and boot into download mode you still see "Qualcom SecureBoot: Enabled." I know there was an exploit found, but it was in a kernel before ours. And seeing that we're getting monthly security updates now, I doubt a kernel exploit is going to be something to hope for. Of course I only mean a non-Knox tripping method. I don't have the balls to try a previously known methods that would trip Knox.

Edited by cPfeifer

Share this post


Link to post
Share on other sites

I tried it, it just fails in odin and you have to reboot.

 

But I'm afraid you're right. Probably isn't going to happen.

 

Sent from my Nexus 6P using Tapatalk

Share this post


Link to post
Share on other sites

I was curious about the other build versions I found on xda and gave those a run through odin on my s7. All produced a fail.

Share this post


Link to post
Share on other sites

Soon.... There are posts in both the Verizon and Sprint Variants that are showing root (as of 6/13/16).. Not unlocked bootloader though and is still not ready for prime time due to bugs.... But still... 

Soon (tm)

 

Share this post


Link to post
Share on other sites
On 6/13/2016 at 2:06 PM, Cythrawl said:

Soon.... There are posts in both the Verizon and Sprint Variants that are showing root (as of 6/13/16).. Not unlocked bootloader though and is still not ready for prime time due to bugs.... But still... 

Soon (tm)

 

http://forum.xda-developers.com/tmobile-s7-edge/help/world-galaxy-s7-root-t3396188

 

Here is a post on XDA of an S7 with right now to be believed only as a temporary root. But as it stands still a locked bootloader.

 

This is cool that people are working on this. I did skim almost all 17 pages and one thing I did pick up on that when root happens along with bootloader unlock it should work with all carriers and every S7 across the board.

Share this post


Link to post
Share on other sites
1 hour ago, Dalmus said:

Not sure if it will work on USC variant, but supposedly it works on Sprint and Verizon, do it should.

 

Check out the article.

 

NA S7 Root...Finally!

 

maybe someone can try this and report?

Share this post


Link to post
Share on other sites
 

maybe someone can try this and report?

I've thought about it. But I really don't need root at all..

Sent from my SM-G935R4 using Tapatalk

Share this post


Link to post
Share on other sites

I successfully rooted my SM-G930R4. I have been rooted for close to a week. I have Xposed installed as well with a few modules. I have debloated quite a bit with titanium backup up. The only issue is that battery suffers a bit.

Sent from my SM-G930R4 using Tapatalk

Share this post


Link to post
Share on other sites
I successfully rooted my SM-G930R4. I have been rooted for close to a week. I have Xposed installed as well with a few modules. I have debloated quite a bit with titanium backup up. The only issue is that battery suffers a bit.

Sent from my SM-G930R4 using Tapatalk

Care to share the process you used to get root?

Sent from my XT1575 using Tapatalk

Share this post


Link to post
Share on other sites

Also, as far as I can tell it does not trip Knox. Once rooted Samsung Pay no longer functions but will again with a full firmware restore as directed in that link.

Sent from my SM-G930R4 using Tapatalk

Share this post


Link to post
Share on other sites
On 7/20/2016 at 6:59 PM, BoгИX said:

 

 

Edited by vernw4

Share this post


Link to post
Share on other sites

the bloat is often times not running all the time.  It's impact on battery is extremely minimal, and storage space is also very minimal.

 

BUT, it's there, takes up some space and annoys me with it's icons in my drawer, so, yeah I hate it.  Even if the benefit is unnoticeable 

Share this post


Link to post
Share on other sites

I like no clutter. I wonder how well the battery saving patch and write up xda has makes a difference some. I still can't complain about the battery life on the s7 yet

Share this post


Link to post
Share on other sites

So has anyone else rooted the s7 for our us cellular? Tried tonight but still stuck at the us cellular screen everytime

 

Edit: Felt kinda stupid, factory reset fixed the issue sometimes I think the problem is more complicated than it is

Edited by Bumpindude
Figured out the issue

Share this post


Link to post
Share on other sites

I just went through the process on XDA and FlashFire says I did not have root. When I looked at the SuperSU settings it showed version 2.79, not 2.76 as stated in the thread and the downloaded file. I did as instructed and ignored the "supersu binary needs updated" when opening the app. Anyone else run into this?

Sent from my SM-G935R4 using Tapatalk

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0