yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Matty1993:
Dont flash anything thats android 8.1 i spent 3 days repairing all my binary fuses from -2 back to 2 i couldnt even get stock firmware to flash, that and TWRP will never work on oreo until ashyx the developer releases the updated version to support 8.1,

As for your region firmware you can actually flash any countries firmware successfully and it will work fine these T380 arent bound by country lock :) just make sure it is T380YDX "U1" for example and not T380YDX "U2",

U2 is 8.1 oreo and as i mentioned not compatible in any way shape or form if you want root use 7.1 or "u1" firmware, "U2" will brick it every time after flash of TWRP

You cannot roll the bootloader back on samsung devices though they are all controlled through 6 one time programmable efuses on your devices PCB (printed logic board) once a binary has been updated from U1-U2 for an example fuse 1 will blow to prevent any firmwares with U1 from being flashed back as the number 2 fuse now has current and 1 is blown & current is severed

Ive managed to roll a bootloader back on htc u11 but samsung it just cannot ever be done while they contain efuses

---------- Post added at 02:39 AM ---------- Previous post was at 02:14 AM ----------

Did it not have the OEM unlock in the developer options when your first turned it on ?

If not that is quite strange all models ive ever had new out of the box have automatically had OEM unlock option there as soon as i enabled developer options,

I dont quite like samsungs approach on the time lock myself ive been looking at samsung systems trying to figure out what they have done or changed within the firmwares to activate this time lock very very lengthy process ive had no luck yet but hopefuly it will be tucked away somewhere simple

Samsung have also launched new security called DEFEX to stop rooting or custom roms thats just a step way to far on samsung the amount of sales they will lose if they keep up with it, luckily s developer on xda here gas already managed to disable the new defex rolled out on some new devices using 8.1 oreo
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] powder_7:
My don't have the OEM unclock option. I can't do anything. I am not sure if the OEM unlock option will show after 7 days. Have to return it if the OEM option doesn't show.

---------- Post added at 02:39 AM ---------- Previous post was at 02:14 AM ----------

[/COLOR]

Did it not have the OEM unlock in the developer options when your first turned it on ?

If not that is quite strange all models ive ever had new out of the box have automatically had OEM unlock option there as soon as i enabled developer options,

I dont quite like samsungs approach on the time lock myself ive been looking at samsung systems trying to figure out what they have done or changed within the firmwares to activate this time lock very very lengthy process ive had no luck yet but hopefuly it will be tucked away somewhere simple

Samsung have also launched new security called DEFEX to stop rooting or custom roms thats just a step way to far on samsung the amount of sales they will lose if they keep up with it, luckily s developer on xda here gas already managed to disable the new defex rolled out on some new devices using 8.1 oreo[/QUOTE]
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] ptballer:
Got mine to OEM unlock by setting date to 1 month ago and clearing data in system app - under apps

and then got to install twrp and root
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] capriorn1971ad:
thank you for clarifying that.

knew it could be done.

the devil was in the exact details, which weren't available completely, but now they are, thank you again, many will find that very helpful.

you know, with that in mind, you might want to set the date back 2 months, install twrp after setting it back forward a month and then after installing root, auto-adjusting a month forward again..

by doing such you should be able to root on day 1, and then after rooting causing OEM unlock to reappear and the device to be rebootable without losing root on day 1 as well, as it has been we have had to wait for 7 days after rooting to reboot.. no more..
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] powder_7:
I can't find "system app" under apps. How do you clear the data in "system app"? Can you show a screen shot?

Thanks
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] ptballer:
under apps - 3 small dots top right "show system apps"

go to system

storage

clear data

back make sure internet not connected and date is set 2 months back - reboot device - click build number 5 times to re-enable developer mode - boom Oem lock should show
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] powder_7:
Strange, I don't have "system" under apps after I click "show system apps". Also, will this work because I already enable developer mode first then try the date changes method.

​
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] capriorn1971ad:
[MENTION=6167070]powder_7[/MENTION] it will still work, seems maybe the builds are actually quite different, or more than they seem to be anyways.

I can't locate the setting on my device either if it is any consolation, there has to be a second way, they always leave a backdoor open somewhere, i will continue searching. )on my device if you go to system and then storage there is no way to clear it, only to stop it, and i doubt you want that).

EDIT: under storage manager there IS a clear data button.

[MENTION=9405727]ptballer[/MENTION] is it storage manager or under storage? (on a sidenote when in storage manager it says "storage" up top, nothing more, easy to see through, pretty sure it is storage manager).

if you already enabled developer mode just move its slider to off, reset date. clean the settings out and re-enable by flipping its switch rather than by tapping 7 times on build (you only have to do that once).

seems it is almost time to write the idiots guide to rooting this model of tablet, most everything is in and complete now, BUT.. if the builds are different this could add to even more confusion..

well, were gonna have to do something and give ashyt his thread back..

this isn't really what he is here for, this thread is supposed to be strictly TWRP but lets be honest, this root on this tab is not simply put, it is kind of confusing, and even trying to alleviate the confusion will add to it because the builds are different enough that that in itself will cause it.

I think I will try to write one step by step while rooting one, but i think instead of starting correctly i will reroot and cause it to fail and start from failure on, kind of like a "pre-amble" to root just in case, that in itself should make the reader more at ease which will help as well.

[MENTION=4899305]ashyx[/MENTION] sorry about the mess we have made here, some of it you will find useful later though i think.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] capriorn1971ad:
use the above mentioned fix and you can root it today, I am pretty sure he meant storage manager and not just storage, in storage manager it says storage in the top of the screen and not storage manager, pretty sure thats what he means.

1) set your clock back two months.

2) go into settings, select apps

3) click on the three dots in the upper right and select "show system apps"

4) click on "storage manager"

5) under storage manager click on "storage"

6) select "clear data"

7) reboot the device.

8 go back into settings and select "general managment", select time and date and move it forward 1 of the 2 months (you should still be 1 month behind at this point).

9) while under system settings click on about tablet and select build number 7 times to eneable developer mode, IF it is already enabled (and it is) then simply turn off developer options and then reenable them by sliding its slider at the top of its screen.

10) look for the OEM unlock (it will be under the 4th entry in the list (Bluetooth HCI snoop log) and enable it.

11) root the device, after rooting it, clear storage data and set the clock forward another month (now the date should be right), and afterwrds go back into developer options and reenable the OEM unlock.

once you have the OEM unlock reenabled AFTER rooting it is safe to reboot the device, but not before. If it does't show afterwards, DO NOT reboot the device UNTIL it DOES.

if you do it this way you should be able to root and reboot the device on the same day and IF anything goes wrong you can reroot it again immediately after using such methods.

enjoy your rooted tablet.

PS. your english is fine, we don't have a grammer patrol here i don't think, if we did i would probably be the first one punished.

---------- Post added at 08:02 PM ---------- Previous post was at 07:17 PM ----------

@matty1993 is TWRP capable of wiping the entire storage so you could reflash the galaxy tab you have bricked?

there has to be a way of basically low level formatting these devices, thats where the solution to your bricked tablet would be.

there has to be a way to rollback somehow.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] duckredbeard:
Now that we have a working TWRP and root, I just wish we had more custom ROMs. Seems there is no real incentive to install TWRP if we can't flash a custom ROM. There are so many devices in this forum, there should be fewer. Why can't the SM-T3xx devices get their own forum, separate from the SM-T5xx devices. We have to sort through dozens of 5xx device topics to see a few 3xx threads.

I'm almost regretting buying this SM-T380 device because of so few options for ROMs. I know I'm gonna get flamed for not developing my own, but it is not my thing. I'd rather buy a device for a developer as an incentive.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] capriorn1971ad:
what about being able to use titanium back up now?

i see reasons for having one rooted myself.

but i have droid edit and other things that can work like "notepad" and a sqllite editor to boot, ftp software.. a mobile webdev device, one that can be backed up completely.

depends on your uses.

i like my T380 alot, suits my needs too well.

a stack of rouge-likes for in-between times and i am set.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Acogu:
What are you talking about? Where is the working TWRP for this tablet with OREO? Could you please point me to that, I am waiting like crazy to root the tablet again.

Or are you on Nougat still?

Cheers,
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] duckredbeard:
Nougat still
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Acogu:
Ohhh, I was getting exited... LOL

Thanks anyway!
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Matty1993:
There is absolutely no way to roll back the bootloader unfortunately,

Samsung have there own dedicated flash system that is seperate from the rest and as i mentioned the board use efuses once you upgrade it from T380YDX U1 to T380YDX U2 it blows Fuse 1 preventing any U1 firmware from being flashed,

These fuses are located directly under the Snapdragon processor or well at least some are, there is no other way its for security purposes,

This all used to be software flagged but since the release of the one time programmable fuse its become impossible to revert anything as its physically blown a fuse.

Unfortunate news but take it from me i run a phone repair shop guys if it could be done i would of found a way to do it by now :(

---------- Post added at 12:51 PM ---------- Previous post was at 12:48 PM ----------

Me to dude been waiting for it aswell i ended up recently aquiring one with oreo on it for $50 all it needed was a new battery im still waiting aswell hoepfully it wont be much longer till ashyx gets it finished been a while now
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] ptballer:
Did you root with Magisk or Super Su? You'll have to flash the no-encrypt file as mentioned if doing with versions of Magisk Older than 17 or along with Super Su.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] B1G7r33!:
Oem unlock

way i found to force oem unlocking

https://xdaforums.com/galaxy-tab-a/how-to/tab-2017-force-oem-unlock-t3874487
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Tami Andranunes:
I had rooted with super user and noencripty, however did not work very well when I restarted the tablet, appeared an error message that I can only solve by installing a new 7.1.1 original version.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] capriorn1971ad:
I used magisk and the no verify patch, waited 7 days to reboot and I was fine, but if you reboot before the Oem unlock reappears you lose root and get an exclamation mark and have to reinstall stock and root again.

They caught me up still and I lost root almost 2 1/2 weeks later, despite all of that, but I never bothered with hiding magisk either.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] powder_7:
Dang, after 7 days still no oem unlock so I did a factory reset. I had to connect to internet to setup the device. I follow the below instructions and still no oem unlock option. I am concerned and might return it if I can't oem unlock. This is a new system and I got in Nov 23. Anyway to check model or build or anything to confirm that it can be oem unlock?

My build number is NMF26X.T380DXU1ARB3

Thanks,
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Matty1993:
You dont need the No verity patch when using magisk all versions 17.0 and above have it built in,

Only time you should use no verity patch is with SU but i wouldnt advise using SU magisk is much better suited for samsung OS,

How did you lose root also ? You must of unrooted or done something as magisk doesn't unroot itself,

And you cant hide magisk also you use the magisk hide section in magisk menu to hide apps like banking apps or google apps and such that would give you the your device is rooted blah blah blah this stops it from happening by hiding root from the app that youve selected with magisk hide,
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] powder_7:
I am 80% certain my don't have OEM unlock option. I did a setup internet hack and still don't work.

1. Factory reset.

2. Connect to hotspot(one plus 5t) with no internet connection.

3. Click next and let it fail to connection once.

4. Enable internet connection on hotspot and click next.

5. Manually set date. I try to set back a few months and forward a few months. (This is first time setting the tablet).

6. Enable development option on.

8. Connect to internet and enable automatic date and time.

7. This should take care of the 7 days wait because the initial setup date was a few months ago or a few months forward.

Still no OEM unlock option. Can someone do a how to video? Seriously about to return it.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Matty1993:
Hmmm that is very strange indeed it should have shown up after 7 days,

However the 7 day wait requires you leave the OS on it for the 7 days without factory ressetting or flashing also, did you do this ?,

Also as for returning the TAB tbh i dont think they will take it back, you tripped the Warranty Bit and it now displays as 0×1 invalid from flashing TWRP therefore all warranty is null & Void gone, if you do take it back hopefully the rep will not look at the download mode on it,

But returning it due to the OEM Unlock not being there i dont think they will refund due to that even if they dont look to make sure youve not tripped it,

I cant even help unfortunately only tab ive got is 8.1 and cant install 7.1 back to check it,

I can confirm on oreo however the OEM unlock was still there on customers and my new one even after i reflashed it completely so theres no major changes to any of the systems so it is there i guess your just doing something wrong somewhere
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] powder_7:
I had to rest a few times because I was changing the dates. So my tablet was not on 7 days continuously.

The warranty bit 0x0 in download mode because I have not fastboot twrp or fastboot OEM unlock.

Also, their ads say CPU is exynos 5433 but my said Qualcomm APQ8017.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Matty1993:
Yeah it should be qualcomm someone probably listed it wrong as alot of samsung devices arw exynos,

Best way to double check however would be put a device info app on your tab and see what its running,

Anyhow yes id say its because your were changing dates and what not needs to stay on a consistent time frame without any interuptions power down and flat battery are ok but anything else such as flashing messing with date & time & the software flag will be set off and the 7 day wait will restart to 7 days once again if that makes sense,

So yeah dont flash it dont change date just leave for 7 days if nothing else is working,

After 7 days and still no OEM unlock option i would be considering taking it back since your knox warranty is still 0×0, every single samsung device ive ever worked on has had OEM unlock also as i mentioned ive got the OREO 8.1 T380 firmware on mine and OEM unlock is still there on 8.1 so will 100% be there on 7.1 :)
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] ashyx:
Ensure you disable developer options before embarking on the 7 day wait.

Also your device needs to connect with Samsungs servers to check RMM state.

So auto update must be enabled. Otherwise do a manual update check.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Acogu:
Hi mate, I know ETA's are not seen well here, but any chance for you to bring an updated TWRP for Oreo?

Cheers
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] ashyx:
I can't do anything until Samsung update their sources. I've been regularly checking, but still nothing.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] capriorn1971ad:
yeah, the forcing unlock is a hit and miss thing, works for some and not for others it seems, it is no solution if it doesn't work all the time.

if you give it the time naturally it will unlock, on the nearest 15 minute mark after the initial set up time.

you understand though that when i did the reset my time was rolled back already right? meaning before i even started i did a factory reset and before even that the date was rolled back, causing the installation time and date to have occured previous.

others have had similar solutions/workarounds which just goes to show it can be done.. BUT.. it really almost seems like a chance thing, and that is not good for a "solution".
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] powder_7:
OK, I am going to wait for 7 days straight without rest. I probably can't return it after this wait period. XDA community has been great and I have used many of their stuff. I'll report back with update. Hopefully it works, if not, at least someone got additional information.

Thank you.

---------- Post added at 10:26 AM ---------- Previous post was at 09:42 AM ----------

Ok, I did a factory rest and manual update check. I'll wait for 7 days then enable development option. I'll wait for up time to be 8 days just in case.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Acogu:
Is this what you are talking about?

http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=t380
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] ashyx:
I guess your trying to link to the sources at Samsung open source centre, however they are still not available
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] djb77:
I'll try and help you by requesting the source if you like.

Tell me which version / versions you want.

I'm also a Kernel dev on S7 / S8 / S9 so I may be able to help you if needed (maybe lol)

UPDATE: Just requested T380DXU2BRK3 for you,
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Matty1993:
Yep still not available ive been checking it too :( i wish theyd hurry up already lol i wonder whats taking them so long its been out for a while now

And yep T380 8.1 or U2 is the one Ashyx needs.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] djb77:
You can always help by requesting it yourself as well. The more people request it, the more of a push it gives them to release it. Request the T380DXU2BRK3 Kernel Source

Unfortunately, I've noticed that the T385 didnt get the Oreo update, weird.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Matty1993:
Yeah i did request an oreo kernel source when i first had a look few days ago,

I thought that to be strange aswell with T385 not having oreo support generally samsung realease updates for there entire series at a time rather than each model separately.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] djb77:
The only thing I'm guessing is the T385 won't get Oreo, because both devices would have received it around the same time. Its been well over 4 months since the last update for T385 as well, and by the looks of its update history on sammobile it doesn't get updated as much.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] ashyx:
I can pretty much guarantee it will get Oreo. Its Just a case of releasing the source code to carriers first then Samsung will release the international version.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Epixtruth:
Received 8.1 update the other day T380... anyone try to root yet?
[Galaxy S6 Edge Q&A, Help & Troubleshooting] Deutzz:
My S6 edge will not turn on, it got slightly wet today and now when I plug it in to charge and press the power button, it shows the charging screen and flashes for 2 seconds and turns back off.

Anyone know how to fix this?
[Xperia Z2 Q&A, Help & Troubleshooting] Hassan651:
Hi,

I broke the screen of my xperia. The display and touch doesn't work. It is rooted and BL is unlocked. I want to transfer all the data from my phone to pc. But I have a pattern lock on my device and USB debugging wasn't enabled if memory serves me right. Is there any way to pull the data from my device in fastboot mode. I tried flashing TWRP on it through fastboot but it does not let me enter recovery mode. Any help is greatly appreciated.

Thank you:)
[Huawei P9 Lite Questions & Answers] ToleX:
Hello

Thing is a few months ago, I've got this phone with broken screen and dead battery, so i've got those two few days ago, and fixed phone, but when i turn it on, it just restarts after HUAWEI logo.

I can enter recovery, tried factory data, but still same

I've tried dload metod with SD card with VNS-L21C432B131, it is updating, and i think it finish it, but again it won't start.

i can enter fastboot, bootloader is locked, and i'ts FRP locked, so can't realy unlock bootloader :/

I have downloaded this DC - Unlocker, and it gives me IMEI and Serial Nr, and also it says that now Firmware is VNS-L21C900B131

Has anyone had this situation? Can this be fixed?

Alsno, first time to see this DC-unlocker, is it sure that it would unlock FRP and Bootloader, maybe then i'll be able to fix?

Please help :)
[Huawei Mate 10  Guides, News, & Discussion] 0rigin:
Well, you read it. It's not a feature, it's a bug.

I like to keep my hands in my pockets because of reasons, and since this phones fingerprint sensor is so sensitive(well, good, actually), I'm constantly unlocking it, while in my pocket. Any solution to this? And no, I won't change my lock style, because this one is the fastest and most useful all around.
[Huawei Mate 10  Guides, News, & Discussion] DANIELWHITT:
Have you tried just putting your phone in your pocket screen side out, probably not the greatest idea without a tempered glass screen protector, but thought that may be a funnier answer.

One a more serious answer, isn't that what touch disable mode is used for in smart assistance. To stop random presses or functions when in a pocket or bag, I would assume that uses the proximity sensor to detect its in your pocket, I know my phone vibrates when I put my hand in my pocket and I touch the fingerprint sensor, but it never comes on until its out side the pocket.