yashsingh1/xdaforums huggingface dataset:
[Google Pixel 4 XL Questions & Answers] Droff:
So you're saying that carrier activation definitely locks the phone, correct?

I'm wondering, because I can see that carrier activation can be handled in two different ways:

Scenario #1. I purchase phone (can even be unlocked version) and get additional $200 discount (or rebate) when I bring it to my carrier and "activate it" by signing service agreement to stay with the carrier for a certain period of time. I break the contract, I pay the high fee. This makes sense to me. Everyone wins. I pay $200 less for a phone that I can do whatever I want with and carrier gets me tied to their network for a certain period of time.

Scenario #2 Activation meaning purchasing carrier branded device fully locked for just additional $200 less. No thanks. If that's the case, then it's a lousy deal when same carriers offer discounts that are closer to $700 for fully locked phones (like BOGO deals on Samsung, Apple or LG). I'm definitely not falling for this.

If it's only $200 off for unlocked phone, it will be more difficult to decide between Pixel and Oneplus. But at least now Pixel will be priced closer to the competition. Decisions, decisions, decisions...
[Google Pixel 4 XL Questions & Answers] Droff:
Here is my reasoning to keep the hopes up for a sensible deal on an activated phone.

Images attached. Current promotion offers $50 discount for activation with carriers. It is still UNLOCKED phone with carrier activation. I think it is reasonable to hope for a carrier activation discount while retaining unlocked bootloader.

Last picture is what gives me pause. It lists $400 discount, but there is no UNLOCKED term there. So I'm guessing that additional discount is only for the branded locked phone. Bummer.

If it is $400 off for carrier activated phone (contract or not) with unlocked bootloader, then I would definitely go for Pixel, otherwise I'm not so sure.
[Google Pixel 4 XL Questions & Answers] ilal2ielli:
As I said earlier, buying a carrier locked phone means locked bootloader.

Buying an unlocked phone means bootloader can be unlocked.

If you take the $200 off deal with the unlocked phone and activate it on a carrier, they cannot block your bootloader unlockable status.

If you take the $400 off deal, those phones are carrier locked and you will most likely not be able to to bootloader unlock it unless you're lucky enough to get a phone that wasn't setup correctly from the factory. In this instance, even when you're out of the carrier's contract period, phone paid off, you will not be able to bootloader unlock, but they'll unlock the phone for use on other carriers if you ask.
[Google Pixel 4 XL Questions & Answers] jon198027:
Just buy the unlocked version at Best buy and you will be able to get the bootloader unlocked
[Google Pixel 4 XL Questions & Answers] bigmatt503:
If you do activate in best buy for the extra 50 off on Verizon it only ends up being 10 off because Verizon has that bull**** 40 dollar activation fee.

I'm going to buy mine from google around black Friday. Rumor has it will be 200 off. If not I'll buy it from best buy
[Google Pixel 4 XL Questions & Answers] dimm0k:
[MENTION=3285682]Droff[/MENTION] I've been wondering about your scenario 1 as well. Hoping someone can confirm the Sprint version from Best Buy wouldn't bootloader lock if you don't insert SIM by activating or some other method to get a Pixel from BestBuy that allows for a sweet $400 off
[Google Pixel 4 XL Questions & Answers] joeyddr:
it's locked with sim or not.
[Google Pixel 4 XL Questions & Answers] vinhraido:
I am also looking forward to this
[Google Pixel 4 XL Questions & Answers] lolprtom:
i can confirm the best buy variant has unlockable bootloader. you have to purchase the unlocked variant. purchasing a carrier variant from best buy will include a locked bootloader. I purchased an unlocked Pixel 4 XL from Best buy. My bootloader is unlocked and I'm rooted, I've also installed custom roms successfully. I have also activated it on Verizon. Hope this answer is helpful. :good:

The only reason to get a carrier variant is the reduced price. however if you want to unlock the bootloader and get root you'll have to pay the extra. For me it's definitely worth it, having all the control. I hate carrier locked bootloaders.
[Moto G5 Plus Questions & Answers] TargetedNuke:
Hi, I am currently on Arrow OS 9, and want to get back to stock 8.1, but I still want root access and unlocked bootloader. Does anyone know the easiest way to do this?
[Moto G5 Plus Questions & Answers] riyan65:
Flash flashable Oreo zip in twrp and then flash magisk manager, most easiest way to get stock+root.
[Moto G5 Plus Questions & Answers] Wolfcity:
This or fastboot flash a signed Motorola firmware and flash magisk after that.
[Redmi K20 / Xiaomi Mi 9T Questions & Answers] aribz144:
Help me, I want play game with ps3 stick way doesn't work? I have rooted my phone, and installed Selinux mode changer but still not working
[Redmi K20 / Xiaomi Mi 9T Questions & Answers] gazza1888:
I would say back up your phone, reflash the phone via fastboot. These files can be found at mifirm.net. Make sure that you flash the same ROM or above.
[Samsung Galaxy J3 (2017) Questions & Answers] michael730106:
hi i recently purchased this j3 from a friend and it worked fine all i had to do was have it unlocked to work with my carrier this is where everything went haywire . after several attempts i finally received the unlock code and then when i put my sim card in it said too many attempts and needed a puk number i called my carrier and got it and entered it and didnt work i thought maybe hard reseting the phone would reset the amount of times ur allowed to enter this number i was wrong. so after some frustration i hard reset the phone a few times and tried every option that can be done in that menu now my phone wont even connect to wifi at the beginning of set up because it needs to verify my identity thru google account which that info i dont have this has become a horrible cycle for me and would apreciate any help or advice with this issue if u could email me this might be better my email is goddam2469@yahoo.ca
[Touch Diamond, MDA Compact IV General] uaon99:
I use my diamond to play music, but I found that sound drop will happen

every 2 to 4 mins, it only happen when i use headphone (not BT one),

using speaker is OK. I also try to use different player to play, but just the same. I also try to disable touch flo, the problem is still there,

any idea?:(
[Touch Diamond, MDA Compact IV General] Simon D:
I've noticed this too, it drives me nuts!!!!

The Kaiser and Touch Dual also had this stutter/glitch, not sure if there's a fix out there - hope so??!!
[Google Pixel 2 XL Questions & Answers] ncsuwolfs:
Ive been out of this game for a while, and now im trying to install custom recovery and root my pixel 2 xl. Unfortunately i cant get any versionof twrp to work with encryption and with no touch screen issues. Any ideas?
[Google Pixel 2 XL Questions & Answers] Badger50:
Remove any lockscreen security you have first. Then fastboot the twrp version 3.3.0-0.img. Once in twrp, flash the twrp image, not the zip to the recovery ramdisk partition. Boot up, then enable your screen lock stuff again :good:
[Samsung Galaxy A50 Questions & Answers] DyretheStrange:
Hello I have been trying to RMM Unlock using Chimera and it keeps failing. I have tried the seven day trick in addition to using Chimera with no luck. I also tried KnoxGuard Unlock using Chimera and it failed as well. Please let me know if you can offer any assistance.

Edit: In download mode no RMM state appears and KG state is checking. Therefore I think OEM Unlock button should appear. But I still think the bootloader is locked because I could not successfully flash a combination AP into my device. I guess there is really no way around these features?

Edit2: I reflashed again and its now says KG state is prenormal. This probably has something to do with the fact i didn't reset factory settings before flashing. Anyways, KG state is prenormal and Chimera KG Unlock does not work.
[Samsung Galaxy A50 Questions & Answers] redymedan:
After reflashed the ROM, connect your phone to internet and wait a few minutes to prevent KG State status to be Prenormal. For A50 there is no RMM state but KG State.
[Redmi K20 / Xiaomi Mi 9T Questions & Answers] shivan.d:
I thought we can have a thread that follows this, as there seems to be some interest around it. None of the current versions out there seems to work properly on the 9T yet.

Please share your experiences and if you found a working APK/workaround.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] AndyYan:
Leaving my own donation link here if anyone's feeling like it: https://paypal.me/AndyCGYan

One thing to note: LineageOS includes LiveDisplay and Night Light which affect the tone of the display (I like colder displays), but on this device both features lag the UI horribly, probably due to lack of HW acceleration. In this case, try the build.prop trick here to make things perceptibly smooth.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] uknetfreak:
Gapps?

Thanks for this great ROM. I have managed to get it installed on my Black Friday purchased device. However, it would appear no to come with any Google stuff (which I would expect). Normally I would install from OpenGapps but it don't think any of those of suitable. Can anyone advise me what would be suitable. I was looking for the equivalent of the Full package on OpenGapps.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Magendanz:
Check out my Nexus Stock ROM.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Minekim09:
ahhhh how to install.. im first rooting,....(for galuxy tab a 10.1 rooting tutorial) :P
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Laykun:
#EDIT, wrong ROM
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] sc00bied00:
Fairly certain I followed all the steps but it has been a very long time since I've used Odin. Here's the failure log. Any idea where I'm going wrong? Tried running Odin as Administrator, same results. Thanks in advance for any help.

edit: Just tried your Nexus ROM and same results

<ID:0/004> Added!!

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<ID:0/004> Odin engine v(ID:3.1303)..

<ID:0/004> File analysis..

<ID:0/004> Total Binary size: 1487 M

<ID:0/004> SetupConnection..

<ID:0/004> Initialzation..

<ID:0/004> Get PIT for mapping..

<ID:0/004> Firmware update start..

<ID:0/004> NAND Write Start!!

<ID:0/004> SingleDownload.

<ID:0/004> boot.img

<ID:0/004> product.img

<ID:0/004> FAIL!

<ID:0/004>

<ID:0/004> Complete(Write) operation failed.

<OSM> All threads completed. (succeed 0 / failed 1)
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] demoneg:
Works like charm! thank you so much for the great work, are you going to release TWRP zip update files for coming version? also any idea why the tablet can't be encrypted? on other note, gsmarena mention that the CPU is Exynos 7904, which is not correct, mine is Exynos 7885! which isn't 64bit as far as I can tell, any idea of there was some versions with Exynos 7904 released?

---------- Post added at 05:46 PM ---------- Previous post was at 05:44 PM ----------

Had some issues with TWRP, turned out to be a bad cable, was crashing with Odin and heimdall on Linux, but at 85% changed the cable and everything worked fine :) also not USB-C to USB-C cable in my case it had to be USB-A to USB-C cable.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Hypfer:
Hi

I've flashed this Rom yesterday and it does seem to work relatively well.

There are some issues, though. Mostly stability. Also the Tablet thinks that it is a phone. How do I tell it that it's a Tablet?

So.. where do we go from here? What are the next steps? How is this Rom built? What is the process to build it?

Regards
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] sc00bied00:
Just tried with a brand new C -> A cable plugged into a USB 2.0 port and same error. I was originally using the cable that came with the tablet. Not sure what to try next.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] whoiswes:
I ran into this (the Odin error on product.img) on the 2 T510's I picked up for my kiddos. Both were initially running the November update, and both upon first boot and setup patched to the December update (this was before I realized there was a Lineage build available).

I was able to successfully flash this build by first downgrading to the September Samsung release (T510XXU2ASI4). I just pushed that through Odin, and immediately entered download mode again post-install, and then install Lineage without an issue. This worked on both of the tablets I have.

I ended up paying for a 3 day pass on samfrew.com because the download speeds are horribly crippled. I would be happy to upload/host the OEM firmware files somewhere to help others if it's not against the rules.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] sc00bied00:
OK, that's odd. I bought this one at Costco about a month ago and it shipped with and factory resets to September AS14 :/

I'd already downloaded that rom from samfrew and even tried to flash it after both this and the Nexus ROMS failed. Same results as those two and failed with the same error at product.img

I wonder if I'll need to roll back to an even earlier one, or would loading a ROM earlier than what's in the recovery be a bad thing?

FWIW, in order to unlock the bootloader I went through the "disable auto-updates, auto time adjust, set the time to the past/future manually" trick.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] whoiswes:
Odd. I didn't have any issues with applying the ASI4 updates (just the BG, AP, and CSC files) with Odin 3.14.1. I don't think OEM unlocking comes into play for this part.

What "KG STATE" in download mode showing? Prenormal means the knox protection got tripped which is probably (part of?) your issue. I can't say more because I honestly don't know (first Samsung device since the Galaxy Nexus). If you're at ASI4, and download mode shows KG STATE: checking, then you're in the same place I was for a successful flash of Lineage.

Sorry I can't be of more help.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] sc00bied00:
Whelp, thar's mah problem. KG state is Prenormal. No idea how I tripped it but this is my first sammy since the S2. I'll start googling and would welcome any advice on what to do to get to a better state.

Thanks! At least now I know what's borked :/

EDIT [SOLVED]: The clue was in Menendez's reply in post #6 of MossyT's guide where he indicates that wifi should be enabled on the restart immediately after the Volume Up long press to unlock, thus revealing OEM Unlock in developer options. The very first go around, I was able to see the option and must have borked a stdep before or during Odin. All subsequent attempts after doing factory resets, I failed to activate wifi on first boot and went straight to Odin. Until the OEM rom can phone home, KG will remain 'prenormal'. Simply turning wifi on and verifying OEM Unlock in devops, KG changed to 'checking' and the flash went through fine.

Thanks for pointing me in the right direction. My daily drivers are a Moto G5+ and X so I'm a bit rusty at the "samsung way" :)
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] dussl:
Any Chance to get double tap to wake (dt2w) running?

There seems to be a solution:

github.com /phhusson/treble_experimentations/issues/663
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Hypfer:
For now you can flash magisk and run those commands via adb as root on each reboot.

I suppose at some point we either fix the init.rc or phh extends the phh treble app to also run the connection check command.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] dcillusions77:
Is this ROM still being updated or worked on? Just curious been 2 months and nothing from the OP. Thanks.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Crashogre:
I am on T510xxu1ASEF. Am I correct to assume I need to upgrade the Firmware to the september release and then install the rom? Or is it as simple as flashing the new rom? I have unlocked the bootloader and have stopped until I find out what to do.

Edited because I'm an idiot and kept saying kernel when obviously the file I downloaded from Samsung was full rom not just kernel.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Magendanz:
I'll update it with the latest kernel source when I get back from holiday, but I wouldn't expect much because there haven't been any GSI updates from [MENTION=4467696]AndyYan[/MENTION].
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] dcillusions77:
Ok thanks for all your work much appreciated
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] ianrobbie:
Any plans to create a ROM for the SM-T515?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Magendanz:
No, since I don't have the device to test it. I released Nexus Stock builds for the T515 relying on beta testers to vet the builds, and it was a mistake. It's just incredibly awkward to troubleshoot that way.

The only thing I'm building for the T515 now is TWRP, and that probably won't last much longer.

And now there's also the SM-T517...
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Crashogre:
Thank you for the rom. Is there a way to change the bootanimation, not the initial boot animation but the Lineageos animation?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Magendanz:
Just replace /system/media/bootanimation.zip. More info here.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] coolgoose1:
The instructions do not say that multi_disabler should be installed. Hence I am assuming multi_disabler is built into the /vendor and /system image this tar provides. A post on multi_disabler original thread says that it is not needed if installing Magisk. And documentation on Magisk's site says that for system-as-root, the device could be running in system mode without Magisk. Should I be concerned about VaultKeeper coming back when not running system with Magisk enabled (but installed in recovery partition)
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Magendanz:
Yes, Multidisabler is only required if you're running an OEM release. It's already been run on this LineageOS build to make the necessary modifications to the vendor partition, and features like VaultKeeper are specific to Samsung's system partition...which is completely replaced by LineageOS.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] ernesto.martinez.mezquita:
Its possible to compile a twrp file to sm-t515 with your last version md5 released on september 19.?

Im lineage absoluty fan and i cant install using odin.

Im prefer LOS Rom without update with troubles before samsung OS ROM.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Andy1767:
My SM-T585 died recently and I had to buy a new Tab.

I was considering to buy a SM-T585 once again since the Lineage ROM was working well and I could keep my case also.

A new SM-T585 currently sells more expensive than a SM-T510/515 where I live. The SM-T510 has newer hardware and I found this Lineage build also.

So I went for a SM-T510. Installed this Lineage ROM and it works.

What I found out afterwards is that this ROM neither supports the f2fs file system nor exFAT. While the first is not that tragic, the latter one is quite bad for me. I wanted to use the 512GByte SDcard I’ve been using in the SM-T585 exFAT formatted without any problem, but it does not work. It’s possible to format it with VFAT/FAT32 but that file system is quite crippled since it does not support files bigger than 4 GByte. exFAT OTG USB sticks also do not work. I use these to exchange files with other devices.

It’s 2020 and even my old Galaxy Tab 2 from 2012 running Lineage 7.1 supports f2fs and exFat…

I did not even realize that nowadays there are ROMs that do not support these file systems.

So is there any chance for this ROM getting at least exFAT support so that SDcards can be decently used? Or someone knows a way to add exFAT support with an additional app/software?

Anyway: Thanks a lot to the developer for providing this ROM and all the hard work! With the exception of file system support, the ROM seems to be solid and working well.

One more thing I'm curious about is the message "! your bootloader is unlocked - blabla..." Is this normal now? My older Samsung devices do not have this. And there is probably no way to get rid of this, is there?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lewmur:
My SD card is only 32gb, so the format support isn't a problem. But I can say that new Samsung tablets all have a locked boot loader and that unlocking it will produce that message. But you can skip right by it by pressing the power button as soon as it appears. On my T720 I also get another nag screen saying my custom ROM may be dangerous. And you have to wait for that one.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] simon002:
Thank you so much for this. My Galaxy Tab A had lousy battery life. This ROM not only extended it to what can be expected of a 6000mA battery but went way beyond! Installation was a breeze and it is very snappy in use. I started out downgrading to the compatible stock ROM and unlocked the bootloader. Then Odin did the flash and twrp did the data formation.

Possibility the best experience I've had going from stock to custom ROM on any device.

Edit: I did read another guide on how to do all the above which in my opinion only muddied the process. I probably didn't have to downgrade.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] DKzVeNgEnS:
I've tried installing V4A without luck.. I uninstalled audiofx but that didn't help, any solution?

When I start playing music it just goes to abnormal and not supported
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] ibayibay1:
Filesystem read only?

I have followed the instructions. Thanks for your work. It seems that internal storage is mounted as read only? I cannot download anything except to the sd card, or make new folders. This is from inside the tablet, as well as from adb push on the command line. I have unchecked "mount read only" in TWRP. Any advice?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lewmur:
Did you format the data partition? Not just wipe, but format it?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] ibayibay1:
No I only did wipe, not format. I just formatted from TWRP and it works! Thanks a bunch.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Shinypika341:
i can teach you i have the same device :)
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Big_Brother_Is_Watching:
Downgrade for T510XXU2ASK5 update?

I just bough a refurbished 2019 Tab A that has the latest update ( December 2019 ) T510XXU2ASK5 on it. I want to install this version of lineage on my tab A, but I'm not sure if I need to downgrade since your version is based on ( September 2019 ) T510XXU2ASI4.

Should I downgrade to the September 2019 version? If so, could someone shoot me a link that points me in the right direction on how to downgrade?

If I don't need to downgrade, can I flash this version of lineage on the December update?

Thanks
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] CCivale:
Yup, I have the same question. Just received my T510 today and I'm on the December update as well.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Magendanz:
I was holding out for Samsung to post the T510XXU2ASK5 kernel source, but I'll probably build an update based on T510XXS2ASK1 this weekend just because they're taking so long. You should still always downgrade to the OEM release for that kernel version, though, since it's risky to run mismatched kernel/vendor combinations.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Big_Brother_Is_Watching:
I flashed the Nexus Rom to see if it would work and it did. Until the Lineage rom is updated, the Nexus rom is a great alternative. It also comes with TWRP pre installed.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] CCivale:
Thanks for the heads up. I installed the Nexus ROM this morning. It works great. ?