[RECOVERY][ROOT]TWRP 3.2.1-1 Samsung Galaxy Tab S3 SM-T820/T825

[Knight1314]

No camera app works. I also found out auto rotate breaks too. What I have done is made whatever modifications I need/want rooted, then flash the original boot back, and camera and rotate is back, but obviously root is gone.

If you don't mind my asking, what mods did you make before flashing the original boot back?

 

[suzook]

If you don't mind my asking, what mods did you make before flashing the original boot back?

I will pm you, dont want to clog up the thread.

 

[ashyx]

No camera app works. I also found out auto rotate breaks too. What I have done is made whatever modifications I need/want rooted, then flash the original boot back, and camera and rotate is back, but obviously root is gone.

Try phh superuser instead.
Edit: actually I may have an inkling what the issue is.
Tell me what your exact firmware build is. You may need the firmware to match the kernel version.
If you can post the exact stock boot image you are using that works.

 

[suzook]

Try phh superuser instead.
Edit: actually I may have an inkling what the issue is.
Tell me what your exact firmware build is. You may need the firmware to match the kernel version.
If you can post the exact stock boot image you are using that works.

NRD90M.T820XXU1AQBB FW
I only have the orig boot from twrp....Will that work??

 

[ashyx]

NRD90M.T820XXU1AQBB FW
I only have the orig boot from twrp....Will that work??

If it's the stock one that came with your firmware that's fine x

 

[suzook]

If it's the stock one that came with your firmware that's fine x

https://drive.google.com

 

[ashyx]

https://drive.google.com/file/d/0BwPAGUQCA8FDVTY2SDlubUdpeVE/view?usp=sharing

Thanks, Im going to take a look at this. However in the mean time I've been looking at this issue with Supersu not finding the boot partition. I'm not happy with manually patching the boot image.
So further on to to this I have made some modifications to the TWRP init by symlinking the partition names to the block devices. Hopefully I can then use by-name partitions in the fstab.
Investigation of Chainfires supersu script should mean that supersu should now be able to find these partitions meaning no need to manually patch the boot image.
It also may fix the issues you are having with the camera etc.

If you could give this a try and if possible in TWRP give me the output of:

/dev/block/by-name

https://www.androidfilehost.com/?fid=457095661767150954

Thanks.

 

[suzook]

Thanks, Im going to take a look at this. However in the mean time I've been looking at this issue with Supersu not finding the boot partition. I'm not happy with manually patching the boot image.
So further on to to this I have made some modifications to the TWRP init by symlinking the partition names to the block devices. Hopefully I can then use by-name partitions in the fstab.
Investigation of Chainfires supersu script should mean that supersu should now be able to find these partitions meaning no need to manually patch the boot image.
It also may fix the issues you are having with the camera etc.

If you could give this a try and if possible in TWRP give me the output of:

/dev/block/by-name

https://www.androidfilehost.com/?fid=457095661767150954

Thanks.

Can I flash this over any kernel?

 

[ashyx]

Can I flash this over any kernel?

It's twrp not the boot image.
What you need to do is flash it then try and install SuperSU.
SuperSU SHOULD be able to patch your boot image now.
Which may fix your other issues.

 

[suzook]

It's twrp not the boot image.
What you need to do is flash it then try and install SuperSU.
SuperSU SHOULD be able to patch your boot image now.
Which may fix your other issues.

Good news, bad news...i have root, camera works, auto rotate works, but internal storage is NOT mountable in twrp
https://drive.google.com/file/d/0BwPAGUQCA8FDNmdrWi1UR1pVSTA/view?usp=drivesdk
Recovery log

 

[ashyx]

Good news, bad news...i have root, camera works, auto rotate works, but internal storage is NOT mountable in twrp
https://drive.google.com/file/d/0BwPAGUQCA8FDNmdrWi1UR1pVSTA/view?usp=drivesdk
Recovery log

Whoops my bad, typo in the partition names.
Should be fine now.
Remember though /data still needs to be unencrypted to mount in TWRP. Any time the stock boot image is flashed it will re-encrypt the /data partition if the boot image isnt patched first.

https://www.androidfilehost.com/?fid=745425885120721426

.

 

[suzook]

Whoops my bad, typo in the partition names.
Should be fine now.
Remember though /data still needs to be unencrypted to mount in TWRP. Any time the stock boot image is flashed it will re-encrypt the /data partition if the boot image isnt patched first.

https://www.androidfilehost.com/?fid=745425885120721426

.

Data mount works!!! I think we(you) have a winner! Camera works, rotate works,an supersu works,and flashes in twrp as it should. Great job, curious as to what the issue was.

 

[whitedragon33]

Confirmed, everything works! Data mount, camera, rotation, SuperSU flashes properly. Great work! :good::good::good::good:

 

[hurray]

I will pm you, dont want to clog up the thread.

Can you please pm me the mods you made also? I am interested in security things as xposed and xprivacy are not currently available for android 7.x. That is now the only thing which holds me back to buy the new Tab S3.

 

[whitedragon33]

suzook, could you also PM me the mods you made? Thanks!

 

[ashyx]

Data mount works!!! I think we(you) have a winner! Camera works, rotate works,an supersu works,and flashes in twrp as it should. Great job, curious as to what the issue was.

The issue, as I suspected, the kernel version was mismatched to the base firmware on the device.

This is why it was important to get supersu working correctly, so the stock boot.img on the device could be patched rather than providing pre-patched boot images. That would have turned into a real nightmare to provide for every device.

Anyway this is all fixed now on the latest posted TWRP and Chainfire is also implementing a fix to SuperSU.
Chainfire has also implemented my Encryption fix into SuperSU.

You've been a great help in all this, to me and Chainfire. Hope your wife understands

Chainfire has another request you may be able to help with in the Beta SuperSU thread.

 

[ashyx]

UPDATE: SM-T820 and SM-T825 fixed builds up.
SuperSU compatibility fixed.

 

[unti20]

Boot into recovery not possible

Hi All,

I am new in this forum, and I hope you can help me with my problem.
I tried flashing the following TWRP for my SM-T825: twrp_3.1.0-1_sm-t825_3417
But when i try to reboot into recovery there is only shown: "RECOVERY BOOTING....." and then its going to "ODIN MODE.....".
So i cant boot into twrp. I never saw this behavior after flashing a twrp version.
Boot into system is working, OEM lock is off and USB debugging is on.
I did everything how it should be done I think?

My installed version is: T825XXU1AQC1 - DBT

I hope you can help me. Thanks a lot!

Best regards

 

[suzook]

Hi All,

I am new in this forum, and I hope you can help me with my problem.
I tried flashing the following TWRP for my SM-T825: twrp_3.1.0-1_sm-t825_3417
But when i try to reboot into recovery there is only shown: "RECOVERY BOOTING....." and then its going to "ODIN MODE.....".
So i cant boot into twrp. I never saw this behavior after flashing a twrp version.
Boot into system is working, OEM lock is off and USB debugging is on.
I did everything how it should be done I think?

My installed version is: T825XXU1AQC1 - DBT

I hope you can help me. Thanks a lot!

Best regards

After you flash TWRP, you MUST reboot to recovery, otherwise it won't stick.

 

[unti20]

After you flash TWRP, you MUST reboot to recovery, otherwise it won't stick.

Hi, yes i did this, but it was the same result.
I unchecked "Auto Reboot", flashed the twrp...tar and tried booting to recovery from the "Downloading" screen with "Home+Vol.Up+Power", but here the same, i stick in this loop i mentioned above.