[RECOVERY][ROOT]TWRP 3.2.3-1 Galaxy Tab S4 - T830/T835

[konchog uma]

finally, success! like neuer31, I only had to use an older computer. followed instructions without problem (well had to sideload magisk APK after flash but no biggie) and have root. Thank you!

 

[pwnerast]

I followed the procedure using the TWRP+Encryption Disabler+Magisk option and my iris scanner did not work (unfortunately, I didn't verify if it worked before tripping KNOX). Face unlock still worked fine. Reflashed back to stock and the iris scanner still didn't work.

Can anybody confirm their wifi S4 iris scanner still works with encryption disabled and root?

I can't figure out if it was related to the KNOX trip, the disabled encryption, a bad camera/IR LED, or something else I haven't thought of.

I exchanged the tablet, but now I'm wary of rooting the new one. I don't care about S Heath and such, but I'd prefer not to permanently break the iris scanner and Intelligent Scan. Thank you.

 

[konchog uma]

Can anybody confirm their wifi S4 iris scanner still works with encryption disabled and root?

yes working fine in that state

 

[ianmacd]

yes working fine in that state

Indeed. No problem at all on my T830.

Sent from my SM-T830 using XDA Labs

 

[jagr]

i'm getting a notification to update twrp in the play store, should I ignore it or safe to update?

 

[konchog uma]

i'm getting a notification to update twrp in the play store, should I ignore it or safe to update?

Pretty sure that's just the TWRP app... Which is different than TWRP itself. TWRP itself is on recovery partition and you can't update that through play store. Check your apps for TWRP if you've an app called TWRP that's not TWRP itself. You could delete that app and still boot into TWRP recovery. App just manages DLs of new builds and other such tasks.

 

[ashyx]

Would anyone be able to test the builds below to see if either fixes the USB options such as ADB and MTP?
They should also auto boot to recovery after flashing with ODIN, so ensure AUTO-REBOOT is ticked.

https://androidfilehost.com/?fid=1395089523397899823

https://androidfilehost.com/?fid=1395089523397899897

https://androidfilehost.com/?fid=1395089523397900246

 

[Leeum]

Would anyone be able to test the builds below to see if either fixes the USB options such as ADB and MTP?
They should also auto boot to recovery after flashing with ODIN, so ensure AUTO-REBOOT is ticked.

https://androidfilehost.com/?fid=1395089523397899823

https://androidfilehost.com/?fid=1395089523397899897

https://androidfilehost.com/?fid=1395089523397900246

Will test now and report back

---------- Post added at 12:05 PM ---------- Previous post was at 11:48 AM ----------

Would anyone be able to test the builds below to see if either fixes the USB options such as ADB and MTP?
They should also auto boot to recovery after flashing with ODIN, so ensure AUTO-REBOOT is ticked.

I tried all 3 and it wouldn't allow me to mount system, cache, or internal storage. No MTP or ADB either

 

[ashyx]

Will test now and report back

---------- Post added at 12:05 PM ---------- Previous post was at 11:48 AM ----------

Would anyone be able to test the builds below to see if either fixes the USB options such as ADB and MTP?
They should also auto boot to recovery after flashing with ODIN, so ensure AUTO-REBOOT is ticked.

I tried all 3 and it wouldn't allow me to mount system, cache, or internal storage. No MTP or ADB either

Thanks for trying this out. Strange that no partitions are mounting, as nothing has changed there?
Will have to investigate this as there seems to be an issue building with 8.1 branch.

 

[Leeum]

Will test now and report back

Yeah tested each one. Same issue. Flashed back and they mounted

 

[ianmacd]

Will test now and report back

Yeah tested each one. Same issue. Flashed back and they mounted

I've been in transit for the last couple of days and am seeing this only now.

Given that the first user's results have already been verified by another user, I won't bother to test these particular builds on my device. When there are new builds to test, I will definitely give them a whirl.

Sent from my SM-T830 using XDA Labs

 

[dr460nf1r3]

Quick question, if i have unlocked the device the boot splash says unlocked, can this be removed by flashing stock firmware via odin again? want to get rid of this.

Sent from my Samsung SM-T835 using XDA Labs

 

[konchog uma]

Quick question, if i have unlocked the device the boot splash says unlocked, can this be removed by flashing stock firmware via odin again? want to get rid of this.

Sent from my Samsung SM-T835 using XDA Labs

about 99% sure the answer is no, but on other Samsung devices i have seen knox counter reset methods, and i have succeeded in resetting a friend's old sammy so he could sell it on eBay. I used the app at the this link to do that. In regards to the unlocked symbol and "custom" which appears on the boot screen, I think once the knox counter is tripped, that appears. You could try going into developer settings and ticking off OEM unlock... but i am almost certain its connected to knox being tripped.

 

[dr460nf1r3]

about 99% sure the answer is no, but on other Samsung devices i have seen knox counter reset methods, and i have succeeded in resetting a friend's old sammy so he could sell it on eBay. I used the app at the this link to do that. In regards to the unlocked symbol and "custom" which appears on the boot screen, I think once the knox counter is tripped, that appears. You could try going into developer settings and ticking off OEM unlock... but i am almost certain its connected to knox being tripped.

yeah im also trying to sell it on ebay. Custom doesnt help that so thats why i asked

Sent from my Samsung SM-T835 using XDA Labs

 

[ianmacd]

yeah im also trying to sell it on ebay. Custom doesnt help that so thats why i asked

Regardless of the cosmetic on-screen details, once KNOX is tripped, it stays tripped. You'd do well to list your device as having tripped KNOX. Failure to disclose that detail to potential buyers is a dubious practice.

Sent from my SM-T830 using XDA Labs

 

[ashyx]

Will test now and report back

Yeah tested each one. Same issue. Flashed back and they mounted

Ok have gone back to build ing with Android 6 branch for now.

Can you test this out and see if it has any positive results for USB options?

https://androidfilehost.com/?fid=1395089523397903404

 

[ianmacd]

Ok have gone back to build ing with Android 6 branch for now.

Can you test this out and see if it has any positive results for USB options?

No joy, I'm afraid. Not only did adb not work, but I couldn't mount the external SD card with this version, either.

 

[Ditzer]

RMM (Remote management monitoring) is dependent on connection to Samsung servers..

Put your device back to complete stock, factory reset from settings and ensure developer options is off.

Ensure your device has someway of remaining being connected to the network.
Around 7 days keep doing software update checks as this will force the device to connect to Samsungs servers.
Also ensure automatic downloading of updates is disabled.
Another thing to consider is to remain on the same firmware that caused the OEM_UNLOCK to go missing.
Do not update the firmware.

Hopefully this will bring OEM_UNLOCK back.
If it's not then disable Developer options after each check.
It should be OK to reboot the device.

As soon as it's back it is imperative to immediately flash the RMM bypass with TWRP before rebooting to the OS.

The above is only my suggested method after gathering information from various sources.

As regards booting to Download mode. Plug your USB cable in first to the PC and device then use the button combo.

Update to all this.

After following the above and waiting the 7 days..I did get the OEM unlock back. This was good advice.

It came back it was unlocked so I actually locked (7 days) then reunlocked (7 days again) just to make sure.

I still cant flash TWRP again though. No matter what I try I get:

"Only Official released binaries are allowed to be flashed" and it fails.

Which to me means its not really unlocked after all. It does state OEM Lock : OFF in the bootloader though.

Anyone see this or can offer any suggestions? Most of the things I see online about it talk about relocking and then unlocking again.

Since I already did that and it takes 14 days, id rather not go that way again if anyone else has any suggestions.

Thanks!

 

[ashyx]

Update to all this.

After following the above and waiting the 7 days..I did get the OEM unlock back. This was good advice.

It came back it was unlocked so I actually locked (7 days) then reunlocked (7 days again) just to make sure.

I still cant flash TWRP again though. No matter what I try I get:

"Only Official released binaries are allowed to be flashed" and it fails.

Which to me means its not really unlocked after all. It does state OEM Lock : OFF in the bootloader though.

Anyone see this or can offer any suggestions? Most of the things I see online about it talk about relocking and then unlocking again.

Since I already did that and it takes 14 days, id rather not go that way again if anyone else has any suggestions.

Thanks!

After you boot to Download mode does it still state Prenormal?

 

[Ditzer]

After you boot to Download mode does it still state Prenormal?

It does.