Looking for Testers with the T817 model to test new root hack.(tested and working)

[graysooner]

I'll fix the Seandroid warning.

Does mean a new image file? Thanks.

 

[seven2099]

OP latest links to 2.65 and your guide doesnt work with latest SM-T817W update.

only this worked.

http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133

 

[harry_fine]

Hello Ashyx. Thanks for your work.

New Rogers Tab S2 T817W with MM 6.01. I've read this entire thread. A lot of it was written with Lollipop 5.1.1, so just wanted to make sure all the instructions and files still the same, and if it's safe to give it a go (I know, back up with TWRP before installing image).

Is this the TWRP version to download from the development section?: twrp_3.0.2-1_sm-t810.tar

I'm curious about one thing. Been rooting phones and tablets for years. I didn't know you could install a customer recovery before you rooted the device. How are you able to install TWRP first prior to new ROM image and root?

 

[ashyx]

OP latest links to 2.65 and your guide doesnt work with latest SM-T817W update.

only this worked.

http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133

Or specifically the security patch the Samsung recently released.
This only applies to MM.

 

[ashyx]

Hello Ashyx. Thanks for your work.

New Rogers Tab S2 T817W with MM 6.01. I've read this entire thread. A lot of it was written with Lollipop 5.1.1, so just wanted to make sure all the instructions and files still the same, and if it's safe to give it a go (I know, back up with TWRP before installing image).

Is this the TWRP version to download from the development section?: twrp_3.0.2-1_sm-t810.tar

I'm curious about one thing. Been rooting phones and tablets for years. I didn't know you could install a customer recovery before you rooted the device. How are you able to install TWRP first prior to new ROM image and root?

You have no need to use this guide.
All you need do is flash twrp then the latest supersu, as of now v2.74.

You do not need root to use a custom recovery.
Root is an OS based hack.

Recovery operates totally independent of the android OS. Recovery is in effect it's own mini OS.
All custom recoverys already have root access.

 

[harry_fine]

You have no need to use this guide.
All you need do is flash twrp then the latest supersu, as of now v2.74.

You do not need root to use a custom recovery.
Root is an OS based hack.

Recovery operates totally independent of the android OS. Recovery is in effect it's own mini OS.
All custom recoverys already have root access.

I'm confused ashyx. Why don't I need Tab_S2_t817T_boot.img, how is my configuration different from the situation in this thread?

And where is v2.74? The link in the OP points to v2.52.

 

[PDADoc]

Got my T817T rooted and working, but I did notice a couple of odd things: one, every time I reboot, it forgets my WiFi network and I have to reconnect it. Also, in TWRP 3.0.0-1 the backup went fine, but at the very beginning of the backup there's a message:

E: Unable to find partition size for '/hidden_image'

What does that mean?

 

[ashyx]

I'm confused ashyx. Why don't I need Tab_S2_t817T_boot.img, how is my configuration different from the situation in this thread?

And where is v2.74? The link in the OP points to v2.52.

This hack isn't really needed any more since chainfire introduced versions of SuperSU which can now automatically patch the stock boot image. Basically doing what I have done here.

You can simply flash the latest version of Supersu and it will do everything required.
https://download.chainfire.eu/964/SuperSU/BETA-SuperSU-v2.74-2-20160519174328.zip

 

[ashyx]

Got my T817T rooted and working, but I did notice a couple of odd things: one, every time I reboot, it forgets my WiFi network and I have to reconnect it. Also, in TWRP 3.0.0-1 the backup went fine, but at the very beginning of the backup there's a message:

E: Unable to find partition size for '/hidden_image'

What does that mean?

You don't need to tick everything in twrp to make a full backup.
The backup options ending in _image are for raw image backups.
The standard partition backup is enough unless you have a need for a raw partition backup.

 

[PDADoc]

You don't need to tick everything in twrp to make a full backup.
The backup options ending in _image are for raw image backups.
The standard partition backup is enough unless you have a need for a raw partition backup.

Thanks for responding. I didn't check anything, I just want with the default settings. So what should I look for in the settings, then? I just checked the backup options and the only things checked are boot, system and data.

Sent from my SM-N910T using Tapatalk

 

[PDADoc]

So, after reading the latest piece of information regarding the obviated need for the boot.img, I restored the TWRP backup I made before I began all this and flashed SuperSU 2.74, which cured my WiFi issue and I'm otherwise rooted, except for one thing: now I can't seem to alter any files in root because root explorer is saying I'm not rooted. And yes, it has superuser permissions.

 

[ashyx]

So, after reading the latest piece of information regarding the obviated need for the boot.img, I restored the TWRP backup I made before I began all this and flashed SuperSU 2.74, which cured my WiFi issue and I'm otherwise rooted, except for one thing: now I can't seem to alter any files in root because root explorer is saying I'm not rooted. And yes, it has superuser permissions.

Update Root Explorer and it will work.

 

[Crash27]

I have the 817w rooted with 5.1.1 and was wondering how to install the new MM firmware. And is there a way to root it yet? I also was wondering if this will remove the SEANDROID is not enforcing warning on boot? Can I install it with twrp?

 

[seven2099]

I have the 817w rooted with 5.1.1 and was wondering how to install the new MM firmware. And is there a way to root it yet? I also was wondering if this will remove the SEANDROID is not enforcing warning on boot? Can I install it with twrp?

Yes there is a way to root it and its much simpler than on 5.1.1

depending on how you rooted 5.1.1 you might need to reflash back to base stock completely or alternatively (if you're not a noob) could manually flash the stock recovery and boot images and then use the OTA update to update to MM.

then simply using the latest super SU beta, 2.75 zip, you could root the device in one click using the correct TWRP.

 

[Crash27]

Yes there is a way to root it and its much simpler than on 5.1.1

depending on how you rooted 5.1.1 you might need to reflash back to base stock completely or alternatively (if you're not a noob) could manually flash the stock recovery and boot images and then use the OTA update to update to MM.

then simply using the latest super SU beta, 2.75 zip, you could root the device in one click using the correct TWRP.

Hi, thanks for the reply, I rooted by flashing TWRP with odin, flashed the Tab_S2_t817T_boot image then flashed BETA-SuperSU-v2.52. I also did a backup in TWRP before I did all this. So what so you think is the best route to go back to stock to update to MM?

 

[Crash27]

Hi guys !! I am in need of some advice and help, I have my S2 817W that I rooted with the Boot.img/TWRP/SU way running 5.1.1. The tablet has been working great for awhile now, know issues beside the red "Seandroid Enforcing" text at bootup, well today I went to start my tablet and it only goes as far as the Samsung logo and reboots. I tried cleaning the cache but nothing would work, I luckily did a backup with TWRP before I began and I did a restore. Now the tablet is booting fine again and is back to my original stock OS. Now I have the TWRP installed and my question is when I boot into recovery it keeps asking if I want to install SuperSU, if I install this will I get root back? And what could have caused the boot loop? I didn't install anything new.


"Update" Just upgraded to 6.0.1 through Smart Switch, just need to figure out how to root now...lol

 

[ashyx]

You probably got the security policy update that Samsung has been pushing which causes bootloops on rooted devices.
Flash supersu v2.74 and you should be good.
This will disable any more policy updates.

 

[Crash27]

You probably got the security policy update that Samsung has been pushing which causes bootloops on rooted devices.
Flash supersu v2.74 and you should be good.
This will disable any more policy updates.

Thanks Ashyx:

Can I still flash supersu under TWRP now that I did the update to MM 6.0.1 ? Or is there another way to root it Now?
Thanks

 

[ashyx]

Thanks Ashyx:

Can I still flash supersu under TWRP now that I did the update to MM 6.0.1 ? Or is there another way to root it Now?
Thanks

Flash with twrp.

 

[Crash27]

Flash with twrp.

Ashyx
Hi, Ok I have no idea what is going on, after I updated to MM I had TWRP still as it wanted to flash the SuperSU, so I downloaded the new 2.74 version like you suggested and tried to boot into recovery but now I am getting the factory android recovery, TWRP is gone. How do I go about getting it back on the tablet with MM on it now? Do I just flash it with ODIN again or do I have to flash a boot.img again ?

Thanks