yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] andr01dfr3ak:
LineageOS is a free, community built, aftermarket firmware distribution of Android 8.1 (Oreo), which is designed to increase performance and reliability over stock Android for your device.

/*
* Your warranty is now void. Knox 0x1.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*/

LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.

WARNING:

This is not a stable version of LineageOS. If you run into problems (and you will), bring us a logcat so we can fix this quickly.

We provide no support for custom kernels, Xposed, or any other modifications made to the system.

Prerequisites:

Your Galaxy Tab A (2015) 8.0".

Odin (you will have to flash TWRP this way if you don't already have it, otherwise extract the img from the tar file and flash it in TWRP).

Downloads:

TWRP 3.2.0 (thanks Deadman for building, Austcool for uploading): [url]https://androidfilehost.com/?fid=962339331458992706[/URL]

Current builds: [url]https://www.androidfilehost.com/?w=files&flid=270958[/URL]

Source code:

Device trees: msm8916-common, gte-common, gt58wifi

Kernel tree: [url]https://github.com/Galaxy-MSM8916/android_kernel_samsung_msm8916[/URL]

LineageOS: GitHub

Support:

You can reach out to me via the official XDA Discord server.

XDA:DevDB Information

LineageOS, ROM for the Samsung Galaxy Tab A series

Contributors

andr01dfr3ak, deadman96385, Paradoxify, Austcool, Spaceminer

ROM OS Version: 8.x Oreo

ROM Kernel: Linux 3.10.x

Version Information

Status: Testing

Created 2018-05-17

Last Updated 2018-05-16
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] andr01dfr3ak:
Reserved

Instructions:

From custom ROMs (assuming you already have TWRP):

Download the latest build and TWRP from the links above.

Ensure these downloads are in your tablet.

Extract the img file from the TWRP tar file.

Reboot into TWRP.

Flash the img file you previously extracted into the recovery partition. (Yes, you can update TWRP this way, it is not dangerous).

Reboot recovery. Then flash the ROM.

Reboot into system. You should be good to go.

If you want any of Google's applications, you'll have to download that before rebooting into TWRP, and flash it after the ROM, but before rebooting.

For Google's applications, go to OpenGApps and select "ARM" and "8.1".
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] andr01dfr3ak:
Changelog:

5-16-2018:

This was released.

Issues:

Bluetooth is not working

Device can't play audio through speakers (but can through headphones)

Media process not doing its job for some reason

Can't access the camera

Major issue:

This ROM is a hit-and-miss, meaning on some devices, the ROM successfully flashes, and other times, it either doesn't boot or TWRP is unable to flash the ROM.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] RebuffedRacer13:
For Gapps, Install the arm version of Gapps.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] katochwa:
Test the rom, very smooth, hope the audio can fix soon.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] asislife20:
Doesnt work on sm-t350! You flash the recovery with odin, black screen. Flash recovery with twrp black screen. Flash rom with working twrp black screen!
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] maydemir:
Hello there. After that I restored the old backup from twrp again, but the device gave the error "efs invalid argument". I have tried many methods and now the device does not boot. Can you help me? I am sorry for my English. Thanks in advance.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Techguy777:
I got you boss I did the same thing and fixed it.

Boot into twrp go to advanced, click terminal and type

mke2fs /dev/block/mmcblk0p13 hit enter.

Then type

mount -w -t ext4 /dev/block/mmcblk0p13 hit enter.

Reboot

It will saying writing indon or something like that after hitting enter on the first command. Are efs is mmcblk0p13 It fixes the problem on reboot your device should boot again flashing stock with Odin doesn't work. I'm guessing you corrupted the data restoring efs and modem with twrp 3.2.1 right? That's how I did it you can't use 3.2.1 for efs or modem it's from lte source code and messes are efs up.hit thanks if it boots it will you just need to type it right. You can also boot into twrp and mount system and use adb to type same command only my adb wasn't working so twrp terminal worked.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] maydemir:
Thank you so much. It really worked. There were errors in the codes I used before. The code at the end of the 13 solved everything :)
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Techguy777:
Your welcome I made this account just to help you. I had that happen last week and thought my tablet was never going to work again except with nougat. So I dug for days and figured out how to do it.

Ls -l /dev/block/bootdevice/by-name/ hit enter command in terminal.

It will show the partition table or setup for are tablet and that's how I figured out we need to use 13. I'm glad I could help. Now everything will work again you can flash lineage 15.1 and it'll work freeze Bluetooth with titanium backup to stop error. YouTube pic in picture works just no sound through speaker but headphones work. Remember guys system ,data , and boot leave efs and modem alone with twrp 3.2.1 it screws it up also do a wipe first clean flash only.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] maydemir:
---------- Post added at 05:16 PM ---------- Previous post was at 04:47 PM ----------

[/COLOR]

There is another problem! I have reset my backup but this time the wifi is not turned on. When I try to open it, the key closes itself.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Techguy777:
Well you'd have to tell me what firmware you restored. Also when you did that command did you try other numbers first before 13? Because it might have to do with that. Explain in detail everything. But for wifi now you should be able to flash your stock firmware and get it back on. Try that let us Know Odin for that.

I did the same thing knocked my wifi and I don't believe restoring with twrp worked I did get it back with stock and Odin.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] maydemir:
I used version 3.1.1 of twrp. I have restored the 6.0.1 stock rooted software from the backup. but everything just works and wi-fi keeps shutting itself down.

---------- Post added at 07:01 PM ---------- Previous post was at 07:00 PM ----------

I used version 3.1.1 of twrp. I have restored the 6.0.1 stock rooted software from the backup. but everything just works and wi-fi keeps shutting itself down.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Techguy777:
Yes I don't have time to explain it but efs partition is wifi Bluetooth and other things you have to flash stock now to get wifi back you mounted so now stock firmware will fix it. Before it wasn't mounted so you wouldn't be able to write over it with rom. Flash stock with Odin your wifi won't come back if you don't.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Techguy777:
Once you flash stock and fix your wifi then you can go back to marshmallow with twrp and wifi working
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] bluenote73:
This is awesome, a bit early for me, but I look forward to running it when it's a bit more mature! Thank you!
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lmore377:
I tried to copy Bluetooth.apk and libbluetooth_jni.so from a stock rom. It didn't work but hey at least i don't get hundreds of popups saying bluetooth has stopped. What I love about this rom is how stable and fast it is. Boot up time is only like 20 seconds.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Xdevillived666:
What should I use to root? Magisk or Super and which version?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] temokk:
Dumb question can i use this on a sm t357t

T mobile tab a.. 8.0
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lmore377:
You can use either on the latest version, but Magisk seems to work better
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] andr01dfr3ak:
That's a bad idea, considering that's a gt58lte and I only have builds for gt58wifi. It's best not to.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] vin_001:
Is this rom still in active development?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] droidbot1337:
Any news on development??
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Techguy777:
There's a new thread with lineage 15.1 on XDA I think this one is dead. The new thread is working better Bluetooth works only external speakers and camera don't work. And the developer will be trying to fix those soon.

https://xdaforums.com/android/software/unofficial-lineageos-t3823960
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Techguy777:
https://xdaforums.com/galaxy-tab-a/development/rom-lineageos-t3826672

This is the new thread of lineage 15.1
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Nechash:
I can't get this to work. In TWRP is keeps giving me error 21.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Techguy777:
Go head and tell us more. What firmware were you on what twrp are using did you try messing with the efs restore. And I shouldn't have to ask but I do you are using a Smt350 right cause I've seen people on other models want to try rom. All the details you can.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] joam280:
I'm glad to see development for our little ??
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Techguy777:
Go look for Resurrection remix for this tablet it just got posted it's Oreo I'm using it works.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Ausint88:
Odd question flashed this rom to sm-t355y works fine wanted to know if its possible to add sim support to the rom or how to do it :)
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] joam280:
Could you post the link? Please

Enviado desde mi SM-T320 mediante Tapatalk
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Techguy777:
https://xdaforums.com/galaxy-tab-a/development/resurrectionremix-o-v6-2-1-20181202-t3874768

It's for smt350 I don't know if you are using a smt320 I don't think that works.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] joam280:
At the moment without audio on the speakers, I'll wait a bit. Thank you

Enviado desde mi SM-T320 mediante Tapatalk
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Techguy777:
I know it's the same thing really this is why coping source codes doesn't always work out lol. Honestly it probably won't be fixed either hopefully it will but who knows.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] bckps7336:
I successfully flashed this rom on my SM-P350 device, bluetooth doesnt work as mentioned, wifi however works in relative to other nougat roms for T350.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] prasmeno:
Is there a fix to the Bluetooth error ? "Bluetooth keeps stopping"
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
There are 3 working PIE (9.0) roms for the T350 now: crDroid, evervolv and lineageos unofficial.

Try one of those.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] gunmavisi:
Hi dear

Did you repaired?

I have same problem
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] finessefigure:
Its because the stock firmware you upgraded from. If you odin 6.0.1 then flash it probably will boot. In fact if you take a flashlight to it, its on and functioning. Something to do with 7.1.1 that doesn't work right that it doesn't activate the backlight. And to get passed the error code in twrp, remove the first 4 lines of the updater script I'm the meta/google/com file. Trust me, I went through barriers with this ROM. But after flashing from downgrading to 6.0.1 I had no issues . the best twrp to use is the lineage twrp from austin on amdroidfilehost. Well I maybe wasted my time explaining but hopefully lead someone in the right path.

---------- Post added at 08:26 PM ---------- Previous post was at 08:23 PM ----------

Thank you for this BTW and for whoever had trouble

You flash the recovery with odin, black screen. Flash recovery with twrp black screen. Flash rom with working twrp black screen

^ spent weeks amsd read through many t350 forums to get something to flash

Its because the stock firmware you upgraded from. If you odin 6.0.1 then flash it probably will boot. In fact if you take a flashlight to it, its on and functioning. Something to do with 7.1.1 that doesn't work right that it doesn't activate the backlight. And to get passed the error code in twrp, remove the first 4 lines of the updater script I'm the meta/google/com file. Trust me, I went through barriers with this ROM. But after flashing from downgrading to 6.0.1 I had no issues . the best twrp to use is the lineage twrp from austin on amdroidfilehost. Well I maybe wasted my time explaining but hopefully lead someone in the right path.
[Samsung Galaxy S8 Questions and Answers] dogpowerxx:
I tried rooting my phone (SM - G950U1). After it finished I was stuck on the Samsung logo, so I tried to enter recovery mode to reset the phone, and it did not work which put me into a loop that went from "installing system update" to "no command." I held the power button and press the up key once, and it gives me something like "failed to open recovery_cause (no such file or directory)."

I also tried to flash a stock firmware but Odin keeps failing.

Anything I can do or am I just screwed?
[Samsung Galaxy S8 Questions and Answers] StonebridgeGr:
how flashing stock firmware failing? you are doing something wrong with odin .. which guide you followed to flash the firmware?
[Samsung Galaxy S8 Questions and Answers] sofir786:
How did you try to root? The snapdragon method of root is not as straightforward as the exynos method, and which version of Odin are you using?

---------- Post added at 11:26 AM ---------- Previous post was at 11:23 AM ----------

https://xdaforums.com/galaxy-s8/how-to/tool-patched-odin-v3-13-1-sha256-error-t3775281

Try the above version of odin
[Samsung Galaxy S8 Questions and Answers] CSxKING_:
I know you've probably already gotten an answer, but if you were running Oreo, or are trying to flash stock Oreo, you'll need the latest version of odin, otherwise odin will either hang or fail on flash because of a new archive format Samsung started using. You'll need a truly untouched stock odin-flashable rom for flashing to succeed. Personally, I still use SamFIRM to get these files, even though its discontinued. Otherwise, you can use the website that replaces SamFIRM and that should get you the same thing. Then flash the files in the right spots in odin using Download mode (POWER + VOL DOWN + BIXBY while powered off). The flash may take some time, but in the end, if done correctly, Odin should say PASS, and the phone should begin to boot. Remember, first boot will take some time.
[Samsung Galaxy S8 Questions and Answers] dogpowerxx:
Now my phone boots into a blue screen that says "installing system update" then it would reboot and be stuck at that screen.

What should I do?
[Samsung Galaxy S8 Questions and Answers] StonebridgeGr:
get firmware from sammobile , install drivers download odin, flash stock firmware. again and again .. if it fails get it to service center.
[Samsung Galaxy S8 Questions and Answers] wolfquin:
dont use sammobile, use SamFirm.

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

its virtually impossible to soft brick a Samsung permanently now days, give us the log/output odin gives.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] andr01dfr3ak:
LineageOS is a free, community built, aftermarket firmware distribution of Android 8.1 (Oreo), which is designed to increase performance and reliability over stock Android for your device.

/*
* Your warranty is now void. Knox 0x1.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*/

LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.

WARNING:

This is not a stable version of LineageOS. If you run into problems (and you will), bring us a logcat so we can fix this quickly.

We provide no support for custom kernels, Xposed, or any other modifications made to the system.

Prerequisites:

Your Galaxy Tab A (2015) 8.0".

Odin (you will have to flash TWRP this way if you don't already have it, otherwise extract the img from the tar file and flash it in TWRP).

Downloads:

TWRP 3.2.0 (thanks Deadman for building, Austcool for uploading): https://androidfilehost.com/?fid=962339331458992706

Current builds: https://www.androidfilehost.com/?w=files&flid=270958

Source code:

Device trees: msm8916-common, gte-common, gt58wifi

Kernel tree: https://github.com/android_kernel_samsung_msm8916

LineageOS: GitHub

Support:

If you want to work with us and get any problems fixed, just click on the Discord link here. That way, we can keep the life of the Galaxy Tab A (2015) devices going until Android P comes out and kills off tablets.

XDA:DevDB Information

LineageOS, ROM for the Samsung Galaxy Tab A series

Contributors

andr01dfr3ak, deadman96385, Austcool, Paradoxify, Spaceminer

ROM OS Version: 8.x Oreo

ROM Kernel: Linux 3.10.x

Version Information

Status: Testing

Created 2018-05-17

Last Updated 2018-05-16
[Moto G5 Questions & Answers] rada80:
Like several others, I have been trying to recover a MotoG5 with BlankFlash, but all the files I tried gave an error, because I believe they were made based on different ROM distributions. I would like to know

how to develop

...

What exists in singleimage.bin

... how is "qboot.exe" done ...

Does anyone here have this knowledge to share? Someone who has done something like that?
[Moto G5 Questions & Answers] silasmvg:
I have two news for you!

First: Welcome to the group of fu** with Moto g5 xt1672 / 70 ... locked in the led.

Second: There is 1 whole month that I'm trying and neither jtag worked.

Here in Brazil I already took the device in several specialists and already tried several tutorials, all without success.

There is one I sent shortly to a member here on the forum.

This tutorial I enivei believe I did not understand right as it is done because the bastard of the videio does not know how to explain correctly or I'm kind of dumb to try.

I can not send links here because I am new to the forum, if you want you can send me an email in which I forward youtube links for you to try:

silasmvg@hotmail.com

good luck!! If you find out let us know!
[Moto G5 Questions & Answers] oxxo.andatti:
comment

I have an xt1671 device that suffered hardbrik if they manage to run the blankflash with success agalon know so I can revive my device thanks

tengo un dispositivo xt1671 que sufrio hardbrik si logran ejecutar el blankflash con exito agalon saber para que pueda revivir mi dispositivo gracias
[Moto G5 Questions & Answers] Exanneon:
There's a way to restore the bootloader, however, a very specific stock rom will have to be flashed from fastboot afterwards, which I don't know of.
[Moto G5 Questions & Answers] echo92:
To the best of my knowledge, I don't think you can develop blankflashes.

1)Blankflashes are digitally signed by the OEM, and likely are not usable if you edit them (as that breaks the signatures).

2)Singleimage.bin appears to contain the various bootloader images, with an accompanying XML file (I guess hex locations of the images in the singleimage.bin), and GPT.bin, whereas qboot.exe seems to handle the communication and verification (from looking at other blankflash logs).

a)Qboot.exe appears to contact your device via Sahara protocol (to attempt to reach the primary bootloader) https://github.com/openpst/sahara and seems to verify the CPU and device.

b)If the CPU and device are verified, the programmer is then loaded and sent to your device to verify the bootloader version on your device. Presumably, this step is to prevent you from flashing older bootloaders and possibly opening security holes https://xdaforums.com/showpost.php?p=62191317&postcount=2112 If the programmer is satisfied your bootloader is not newer than the blankflash bootloader, it then opens the firehose connection to begin downloading and flashing a new bootloader to your device.

It seems that from the blankflashes I've noted, most of the failures seem to happen with 2b) - i.e. the programmer verification or with 2a), the blankflash just can't communicate with your device. With 2b), that may fail if your corrupted bootloader is newer than the blankflash bootloader - it'll just reject the flash or hang at 'waiting for firehose'. As mentioned here, though, https://github.com/openpst/sahara you'd need updated/new blankflash files with an updated programmer specific to the Motorola MSM8937 platform. Getting those files is quite difficult - OEMs like Motorola do not like giving them out (most of the blankflashes we have on XDA are old leaks), presumably as having a signed blankflash that can access the bootloader may be a security risk (as this Aleph article may demonstrate https://alephsecurity.com/2018/01/22/qualcomm-edl-1/ ) However, without a proper programmer, then the bootloader images may not flash onto your device.

You may wish to look into either a G5S or G6 Play blankflash if they are around, as they are based on the Snapdragon 430. I do not know if their bootloaders are compatible with the G5, so I cannot recommend to flash/attempt to flash a blankflash not meant for your device. Failing that, your other options are to pay for a motherboard repair or to invest in a new device.
[Moto G5 Questions & Answers] silasmvg:
You are very correct and I agree with you! By the jtag I managed to do all this, but the error occurs in the signature and I do not know to do the correct programming.

The way I found it is to wait for the leak of this oem.