yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] vin_001:
I've got the twrp 3.2.0 image from the resurrection remix page that people have reported to have gotten working. I've downloaded multiple times and flashed with no luck... so that rules this out [MENTION=4899305]ashyx[/MENTION]
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] bluenote73:
That google drive link is a little wonky so I suggest you check the md5.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] alin919:
How did you try installing ? Did you flash twrp.img with twrp or odin ?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
That is exactly WHY I provided the number of bytes and md5.

If the two match, then it's likely the operator doing something wrong.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] bluenote73:
I know, but apparently some people don't..
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] vin_001:
3.1.1.1 was a tar.md5

The twrp that wont boot (3.2.1) I tried to flash with an img .
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] iesous-kurios:
New build up.

Thanks to elginsk8r, the sound and bluetooth is working. This ROM now has same bug as their though, chrome/clash, etc not being compatible with device.

( the apps work just fine, you just can't download them from playstore)
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
Thanks for working through this.

Downloading now.

I have a number of tests in mind to try and figure out the problem with device isn't compatible. Will report back later tonight.

elginsk8r commented at

https://xdaforums.com/showpost.php?p=79178983&postcount=147
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] alin919:
From 3.1.0 I got 3.2.3 installed thru twrp , flashing twrp.img .
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] vin_001:
Can you link me to both Twrps? That would be helpful!
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] alin919:
Use the tar one on odin , after booting in twrp , flash the recovery . img choosing img file instead zip flash .
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] alin919:
Unzip second file into img.zip .
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] vin_001:
None of these work. The first one boots to a black screen... the second one is for the t380, not the t350
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] alin919:
I just checked again in this morning , i did installed lineage on my t350 and both file working . So i dont know what else so say .......
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] vin_001:
I'm on stock 7.1.1 does that make a difference?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] alin919:
Might , try to flash recovery.img ( 3.2.3) and instead reboot , flash rom and gapps ( pie ) then reboot system .
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] vin_001:
Maybe you aren't comprehending, I cant install any twrps, not even 3.2.3-0.... I'm not sure why. Only 3.1.1.1 for the t355 works even though my tab is a t350

---------- Post added at 03:07 AM ---------- Previous post was at 03:07 AM ----------

[MENTION=4899305]ashyx[/MENTION] please help :crying:
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] ashyx:
TWRP for T350 has been updated, but seems to have issues with rebooting at the moment.

If you decide to try it, do not use any utilities to boot to recovery, hard keys combo only.

https://xdaforums.com/galaxy-tab-a/development/recovery-t3426560/page54
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] vin_001:
Viola!! Finally it works with this build! I'll keep the reboot issue in mind, but thank you [MENTION=4899305]ashyx[/MENTION] for your response and help!
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] ashyx:
Can you test something for me?

Boot to twrp and select reboot to system then report if it boots OK to system?

Thanks.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] vin_001:
When I dont have my charger plugged in it boots properly to the system, but when the charger is in, it boots to the battery charging spashscreen and not to system

Edit: installed this rom with gapps but is not booting, stuck on black screen

JUST KIDDING

Rom makes sounds, but I get no display. Somethings up there
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
I'm going to do a Magisk canary test later on since I have been doing some research on CTS.

I first did some battery sleep tests. I also posted this over at the evervolv thread.

https://xdaforums.com/showpost.php?p=79197948&postcount=157
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] bluenote73:
Hey RT, if you're going to do that, could you test without magisk as well?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] alin919:
I got chrome working . First time installed 02/16/19 lineage ROM with pico gaps , then set tablet and update/ downloaded apps .After I got whatever I need from play store , manual rebooted to twrp and update the ROM( dirty flash ) to last version 3/23 and magisk 18.1 , Now I got root and chrome working .
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] iesous-kurios:
The apps work with a clean flash of 3/23 too, but you can't download them from play store. There are other sites that let you download the apk files to install manually.

This will be helpful for when the apps are updated. You won't need to flash back to old build to update apps, just find the updated apk and download/install manually.

Working on a build which may let you download from play store, but just in case an app gets updated before I (or evervolv) figure out the problem, you can go this route.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
Evervolv has a patch. See

https://xdaforums.com/showpost.php?p=79198628&postcount=158
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] desmvp:
So I'm going to be upgrading my smt350.

What twrp r u using?

Dose the external speaker work?

I'm currently on android 5.0.

Twrp v

Thanks in advance.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] vin_001:
No roms are booting with display.... oreo and pie... so is this a problem with your recovery? Or is it something else? [MENTION=4899305]ashyx[/MENTION]
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] bluenote73:
Please start a new support thread somewhere else.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] ashyx:
Not sure how it would be twrp related. Twrp is lineage compatible as far as I know.

Seems to suggest your firmware needs to be updated.

Is your bootloader the latest, what are others using?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
[MENTION=1984568]Jfuginay[/MENTION], re your fixed build as per

https://xdaforums.com/showpost.php?p=79220833&postcount=178

I wonder if newbies downloading this rom will find it too difficult to download device id and register to get everything working?

I didn't have to do any of this registration with your Feb 23 build (no audio, but google play store works fine).

I also don't have to do those steps with evervolv or crdroid and I don't get the "error saying my device contains preinstalled google apps".

My standard procedure is to wipe dalvik, cache, data and system. Load the rom, reboot and let rom boot. Boot into recovery and then flash gapps pico. Reboot into system.

I would be happy to test your build to see if I get the same error message using the procedure above.

PS. I'm off to bed. If you upload anything, I will download it tomorrow to test. If not, no worries. No rush. Collectively, we are making good progress.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] iesous-kurios:
K, buenas noches.

Build is uploaded to afh now. But like you said, no rush, we are making good progress. Will make a couple edits right now and should wake up to a new build that I'll test tomorrow and hopefully it will not have that weird google device register bug.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] ashyx:
This is as per normal for custom roms. Had to do this on all devices running custom software if I want the device certified.

However just to note not having certification didn't prevent use of Google apps for me.

However Google may have changed things recently.

The device at least has to pass CTS. All mine do which is maybe why I do not have issues with Play store.

Does your device pass CTS? If it doesn't then this is likely why that warning is displayed as it likely checks CTS at initial set up.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
I think we have some miscommunication here? Sorry, I already downloaded and tested the March 23 build on afh. I didn't run into the problem that you had following my procedures with that error message.

If you have a newer build than March 23, I can download and retest, but if you are making changes trying to fix the bug, I can wait.

BTW, I also noticed you merged FlipFlap. Cool, I have a smart cover and can test that as well.

Thanks and sorry for the misunderstanding.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] iesous-kurios:
The problem started for me when I switched over to evervolv source code for device tree instead of galaxy-msm8916 code. I'm thinking there is a problem of left over evervolv code causing problems with lineage code so it makes me fail CTS.

I'm still new to ROM building and not sure where to start looking for an issue like this.

I think I found a section of my code that is calling in an aosp dependency, and there is are device specific build.prop settings in there, maybe my builds are trying to identify as lineage and evervolv and aosp so that could be making google freak out on me?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] iesous-kurios:
No misunderstanding, it was my fault. I uploaded new build but then deleted it after seeing that I had broken the camera.

I rebuilt and am running new build now with working camera but the CTS fail problem is still there.

It's the 3/30 build uploaded to afh
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
With the Mar 30, there definitely is a problem. As soon as I flash the rom and reboot, I get a popup saying

"Android System

There's an internal problem with your device. Contact your manufacturer for details."

I never had this before with your previous builds that were uploaded to afh, evervolv or crdroid.

After I install google pico, I then get that screen as shown by

https://www.xda-developers.com/how-to-fix-device-not-certified-by-google-error/

Right now, nubianprince's crdroid build seems to be the one that is fully working except it doesn't pass the ctsprofile in magisk. Maybe you can find clues at his github?

https://github.com/Nubianprince

I'm going to revert back to crdroid to see if the internal problem message goes away. If it does, I'll do some research on what might be causing the error.

---------- Post added at 12:03 PM ---------- Previous post was at 11:57 AM ----------

Yes, that internal problem message goes away when I reflash crdroid.

So definitely something wrong with the Mar 30 build.

---------- Post added at 12:21 PM ---------- Previous post was at 12:03 PM ----------

I have a Nexus 9. I had it running lineageos and then wanted to try unlegacy android which is based on aosp. As soon as I changed it, I got that

"Android System

There's an internal problem with your device. Contact your manufacturer for details."

I had to fix it by reflashing vendor.img if I remember correctly. Something about build.prop not matching in /system and /vendor. This was about 8 months ago so my recollection could be wrong?

So you could be on the right path of solving this issue.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
I compared the crdroid and lineageos /system/build.prop and /system/vendor/build.prop.

They are identical using diffuse.

I attached the files here in case I made a mistake

I put both roms into adb debugging and then enabled root access via adb only.

Then I did adb root, adb shell and looked at the files on both builds.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
Wait a minute, I'm redoing this test. I think I did something wrong.

---------- Post added at 05:24 PM ---------- Previous post was at 05:14 PM ----------

Yes, I did do something wrong. Going to test out a theory. Back with results later.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
Yes, I did do something wrong earlier with my comparison. I had multiple windows open and probably cut & paste the results from the wrong terminal window.

The lineageos /vendor build.prop and /system build.prop are different.

In particular, the fingerprint doesn't match along with the build date.

The crdroid build.prop fingerprint matches.

I tried hand editing the files, but each time, my tablet is hung and I have to disconnect the battery and go back into recovery. Not sure why, but I have given up hand editing.

I have uploaded the 4 files for comparison.

l = lineage, c = crdroid, v = /vendor, s = /system

PS. /vendor is link to /system/vendor according to ls -al.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
I found this

https://android.stackexchange.com/q...-your-device-and-it-might-be-unstable-until-y

Following the instructions at "runtime fix" and adding a

adb shell

before

mount -o rw,remount -t ext4 /system

and then exiting the shell with "exit"

the tablet no longer boots with that "internal problem" message.

This time I also used vi instead of leafpad in case leafpad was adding <CR> or <LF> screwing up the build.prop file.

While the "internal problem message is gone at bootup, google play still complains that the "device is not play protect certified". So obviously, more than just that one line fingerprint has to match. Thus, I tried match the date and utc, but still get the same "device is not play protect certified".

The thread also mentions a "compile time" fix, but having mismatched fingerprint, I think long term, is not the long term answer if google changes something at the play store. Personally, I would not consider the "compile time" fix as reliable.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] iesous-kurios:
Looks like you've just learned an important lesson about reading through a thread before flashing. You must have downloaded the 3/30 build, I didn't place that build inside the LineageOS folder for a reason. It is a test build for retiredtab to try out.

Nevertheless, I see value in your opinion to add this as a warning in OP. I've done so.

Registering the device on google is a very simple process (link to instructions on OP). 5 min max. After that is done all things work as they should.

About to start a new build that hopefully fixes this issue and removes the need to register your device with google. If it is fixed, I will upload that build into the Lineage OS folder for use by non-testers.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] elginsk8r:
Well maybe you should just stick to Official software from Samsung. XDA is a developer forum, get used to there being issues, bugs, non working features.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] iesous-kurios:
After some research I saw that there were some users building with aosp that encountered different times in their device and vendor build.prop files after a build failing and finally completing after fixing an issue. There is supposed to be code in the build/core/make file which will reset the build time upon an error and that may not be working for me.

Since there was an error with the build compiling now which I fixed then restarted my build from that point, I have decided to stop my build, run 'make clobber' to clear my build directory, and start the build again to see if the build completing in one shot with no errors in between will fix the issue.

Going to bed soon, so hoping to wake up to completed build with working play store right out the box.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] AndyYan:
Just asking, will P350 (the S-Pen variant) be supported some time in the future? Note that I don't own any of these Tab A variants right now, but I've been interested in the S-Pen variants for quite a while. P580 (2016 S-Pen variant) didn't get any AOSP love either, despite T580 development flourishing, so I'm guessing it'll be similar here.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] nubianprince:
For me these errors usually clear up with a clean build(make clean/clobber)

Depending on when the build was paused/stopped there is a mismatch with the prop fingerprint in system and vendor.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
I have a Samsung P550, the bigger brother. If you are expecting any custom rom for pen support, I think you will be disappointed from my research regardless of model and brand.

Developers likely need to own that exact model in order to support the pen feature. They are more likely to have the non pen version.

I did try various T550 (no pen) on my P550 and encountered not only ROM issues, but TWRP issues. See my post at

https://xdaforums.com/showpost.php?p=79018037&postcount=108

https://xdaforums.com/showpost.php?p=79120717&postcount=111

https://xdaforums.com/showpost.php?p=79190868&postcount=549

I suspect you might run into the same bugs with the P350 running T350 rom.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] iesous-kurios:
Ok, new build uploading to afh now.

The problem was in my build/core/makefile , after a few edits (really undoing some edits I had made in the past while trying to get build to complete on previous ROM) my latest build boots up, shows no internal errors, and doesn't require google registration.

Bluetooth, camera, speaker should all still work too.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] vin_001:
I'm on the latest bootloader.... perhaps this is why
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] AndyYan:
Totally expected, thanks for backing it up with your own experiences. Crossing it off my devices-to-get list then.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
Mar 31 build results.

1. Sound, camera, GPS and bluetooth work.

2. I can see Clash Royale, Clash of Clans and Chrome in the google play store. Playstore says "Device is not certified". It also fails ctsprofile in magisk.

You may want to spoof the fingerprint like nubianprince by using the original stock 7.1.1 fingerprint so your build shows up in the play store as "certified"?

This might be necessary in the future if play store tightens up its requirements?

3. Deep sleep works. I verified with BBS.

4. If you included FlipFlap in this Mar 31 build, it doesn't put the tablet to sleep when I close the cover.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] iesous-kurios:
New 4/1/19 build uploaded with everything working plus used build fingerprint code from nubianprince to make it pass safety net checks
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
Wow, 1 minute turn around time from my post. ;)
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] iesous-kurios:
I have ccache on and close to 100 gig limit. That, plus not doing a 'make clobber' made my build time for such a small change around five min. Went over to Nubians thread to see status of your tests and saw his fix for safety net so figured I'd incorporate that too.

Running on my tab now, feels pretty nice. Now to trouble shoot the flipflap issue. Also going to try troubleshooting the Bluetooth calls on my note 3. They've been broken since lineage 15.1

Flipflap works on my note 3 with lineage 16 so I wonder what about our tabs make it not work.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
Okay, so your Mar 31 included the flipflap apk? If yes, I will look through some logs and do some research.

I don't own a note 3, but looking at possible a working note 2 or 4 with bluetooth on lineage 15.1 might yield some clues?

Or looking at other platforms that use a Snapdragon 800?

I'll take a look over at your thread to see if I can spot anything?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] iesous-kurios:
Yes, all my builds have had flip flap apk.

Note 4 is probably closer to note 3. I think I've seen some xiomi note 3s have working Bluetooth calls, so I'll check them out too.

My specific one is hltetmo, but the same problem plagues hlte, hltekor and hltechn
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Florad77:
I need a tiny bit of help guys. I have TWRP 3.2.3-1 from here: https://xdaforums.com/galaxy-tab-a/development/recovery-t3426560/page54. It seems to work, I can boot into twrp. But when I follow all the instructions in this thread, after I hit reboot to system, it shows the samsung tab a splash screen and then just goes black and stays that way. I can't reboot or go to recovery, I can only go to download mode. I reflashed the recovery through odin and I can get into TWRP but no matter what I do there, when I reboot system it just goes black. Any advice?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] retiredtab:
I found 2 bugs in TWRP 3.2.3-1 and would not use that.

Use 3.2.3 as I wrote here

https://xdaforums.com/showpost.php?p=79146914&postcount=63
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Florad77:
Sorry, how would I use that? Flash through odin?

Edit: I flashed it to through TWRP but it does nothing. If hit reboot to recovery after flashing it, I get a black screen. I reflash 3.2.3-1 with odin and twrp works fine (but can't boot anything past that). I flash the image you linked, power off, then try booting to recovery or to system and get black screen both times. TWRP can't recognize my backup and samsung smart switch says unsupported device so can't even get back to stock, guess I'm stuck.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] iesous-kurios:
If you're flashing through twrp then make sure you extract the .img file first, then flash that.

Flashing through twrp requires extracting the img file, then there is a special section for flashing images in twrp which is different from flashing zip files such as ROMS and Gapps, etc.

Flash the working twrp through odin, boot into twrp, then unzip the other twrp on your PC, plug your tab (which is in recovery mode) into your pc and transfer extracted img file to your sd card. Then flash the img using the 'flash image' feature of twrp, reboot right into twrp again, and then try flashing this ROM.

Hope that helps.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Florad77:
Ok, I did exactly as you said, but when I try to reboot into twrp again at the end I just get the black screen. Thank you for trying though. Are there any other twrp versions I should try? Or should I try CWM (if that's even possible)?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] ashyx:
Post your recovery.log after installing the rom.

Go to Advanced>copy log.

Upload the txt file.

Also be aware Twrp 3.2.3-0 is likely using the same kernel as the actual ROM which is probably why you are experiencing a blank screen with both.

These devices are rather finicky. I have wrangled with this black screen issue several times on these Tab A devices.

I fix it, Samsung breaks it, I fix Samsung breaks it and that's how it goes each update.

Further to this it seems not all Samsung devices are created equal.

Same device, same specs, same bootloader, different behavior from one device to the next.

Had a similar issue with the Note 4. Some devices could not boot Lineage 15.1 no matter what. Others just fine.

Same goes for lineage TWRP builds. Didn't work for some, my builds did.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] bluenote73:
It's weird that it's not all devices though. That suggests to me it's some other differing remnant of firmware.

EDIT: And for anyone else interested, photolarry the jerk had his posts removed. I can only hope mods also messaged him about an attitude adjustment.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] vin_001:
Same with me! This is my issue :(
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] bluenote73:
Latest version is working out well for me so far, thanks jfuginay. What are the chances you might be able to pull in some overclocking? This tablet might last me a while yet if it was just a bit speedier.